WO2017076078A1 - Vnf实例的伸缩方法及装置 - Google Patents

Vnf实例的伸缩方法及装置 Download PDF

Info

Publication number
WO2017076078A1
WO2017076078A1 PCT/CN2016/092721 CN2016092721W WO2017076078A1 WO 2017076078 A1 WO2017076078 A1 WO 2017076078A1 CN 2016092721 W CN2016092721 W CN 2016092721W WO 2017076078 A1 WO2017076078 A1 WO 2017076078A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnf instance
scaling
ems
scaled
deployment specification
Prior art date
Application number
PCT/CN2016/092721
Other languages
English (en)
French (fr)
Inventor
祝伟宏
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017076078A1 publication Critical patent/WO2017076078A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks

Definitions

  • the present application relates to, but is not limited to, the field of communications, and in particular, to a method and apparatus for scaling a VNF instance.
  • the interface between the Network Management System (NMS) and the Element Management System (EMS) is called the northbound interface (Itf-N).
  • EMS mainly completes the Element Management Layer (EML) function in the International Telecommunication Union (ITU) Telecommunications Management Network (TMN), that is, completes the management functions of one or more mobile communication devices.
  • ITU International Telecommunication Union
  • Telecommunications Management Network Telecommunications Management Network
  • EMS between different device vendors cannot be universal.
  • the NMS mainly performs the Network Management Layer (NML) function in the ITU TMN and is responsible for the management of all network elements in a managed network.
  • NML Network Management Layer
  • the entire subnet can be managed through its own EMS management.
  • FIG. 1 is a reference diagram of the network function virtualization reference architecture in the related art, and the VNF and the underlying network function virtual Network Functions Virtualization Infrastructure (NFVI) isolation.
  • VNF Network Functions Virtualization Infrastructure
  • the traditional maintenance management function of the VNF instance is performed by the EMS, and the life cycle management function of the VNF is completed by the VNF manager VNFM.
  • the underlying virtual infrastructure is managed by the Virtual Infrastructure Manager (VIM).
  • VIM Virtual Infrastructure Manager
  • the specific network service is generally completed by one or more VNF instances.
  • the management of the network service is carried out by the NFV arranger NFVO.
  • a network service instance is provided to provide network services through network service instances.
  • One of the advantages of the virtualization of the network function is that the resources used by the VNF instance that constitutes the network service can be dynamically adjusted, that is, the VNF instance is scaled to provide resource utilization and reach The purpose of energy saving.
  • the scaling of the VNF instance includes scale out or scale up and scale in or scale down.
  • the expansion includes two cases: scale out: when the VNF is composed of multiple Virtualization Deployment Units (VDUs), the VDU instances that form the VNF instance are added to increase the capability of the VNF instance.
  • Scale up Increases the configuration of a virtual machine (VM) running a VNF instance, such as adding a Central Processing Unit (CPU), memory, network ports, etc. to increase the capabilities of the VNF instance.
  • VM virtual machine
  • CPU Central Processing Unit
  • memory network ports, etc.
  • the reduction also includes two cases: scale in: that is, when the VNF can be composed of multiple VDUs, reduce the VDU instances that make up the VNF instance to reduce the ability of the VNF instance; scale down: That is, reduce the configuration of virtual machines (VMs) running VNF instances, such as reducing CPU, memory, network ports, etc., to reduce the ability of VNF instances; at present, there is a preliminary study on how to scale (expand and shrink) VNF instances. And gives the overall flow of VNF instance scaling. However, the current research does not specify how to use the EMS to trigger the scaling of the VNF instance.
  • VMs virtual machines
  • VNFM Virtual Network Function Manager
  • Embodiments of the present invention provide a method and an apparatus for scaling a VNF instance.
  • a method for scaling a VNF instance including: determining, by an EMS, a VNF instance that needs to be scaled, and a desired deployment specification that the VNF instance needs to be scaled to; the EMS identifies the VNF instance and according to the The scaling information determined by the deployment specification is sent to the VNFM, where the identifier of the VNF instance and the scaling information are used to indicate the VNFM The VNF instance is scaled according to the scaling information.
  • the determining, by the EMS, the VNF instance that needs to be scaled includes: determining, by the EMS, the processing performance of the one or more VNF instances for performing service processing according to performance data of the collected one or more VNF instances; Determining, by the EMS, a VNF instance whose processing performance is lower than the first performance threshold or a VNF instance whose processing performance is higher than the second performance threshold is the VNF instance that needs to be scaled; and/or, the EMS determines that the VNF instance needs
  • the desired deployment specifications that are scaled to include: the EMS determines the desired deployment specification according to a preset deployment specification of the VNF instance that needs to be scaled and a capability that the VNF instance is expected to reach.
  • the EMS obtains a preset deployment specification of the VNF instance by using one of the following manners: the EMS obtains the preset deployment specification from the VNF instance; and the EMS obtains through a private interface with a database.
  • the preset deployment specification where the database stores the information of the preset deployment specification; the EMS obtains the preset deployment specification from the VNFM; and the EMS obtains the preset from the NMS Set deployment specifications.
  • the EMS determines that the VNF instance that needs to be scaled and the desired deployment specification that the VNF instance needs to be scaled to include: the EMS receives a first extension that is sent by the NMS to indicate that the VNF instance is scaled.
  • the command wherein the first scaling command carries an identifier of the VNF instance and an identifier of the desired deployment specification; the EMS determines the VNF instance and the desired deployment specification according to the first scaling command; Or the EMS receives the second retracting command that is sent by the NMS to indicate that the VNF instance is to be scaled, where the identifier of the VNF instance and the VNF instance need to be expanded and contracted.
  • the scaling information includes one of the following: the identifier information of the desired deployment specification, and the scaling type information and the scaling level information determined according to the expected deployment specification and an actual deployment specification of the VNF instance.
  • a method for scaling a VNF instance including: determining, by the NMS, that the VNF instance needs to be scaled; the NMS sending, to the EMS, a scaling command for instructing the VNF instance to perform scaling processing; wherein the scaling Command is used to instruct the EMS to implement the VNF.
  • the NMS sends the retracting command to the EMS to indicate that the VNF instance that needs to be scaled is subjected to a scaling process, where the NMS sends a first retracting command to the EMS, where The command of the VNF instance carries the identifier of the VNF instance and the expected deployment specification; or the NMS sends a second retracting command to the EMS, where the second retracting command carries the VNF instance.
  • the scaling information includes one of the following: the identifier information of the desired deployment specification, and the scaling type information and the scaling level information determined according to the expected deployment specification and an actual deployment specification of the VNF instance.
  • a method for scaling a VNF instance including: the VNFM receives the identifier and the extension information of the VNF instance that needs to be scaled from the EMS, where the scaling information is that the EMS needs to be expanded according to the VNF instance.
  • the scaling information determined by the desired deployment specification is obtained; the VNFM performs scaling processing on the VNF instance according to the scaling information.
  • the scaling information includes one of the following: the identifier information of the desired deployment specification, and the scaling type information and the scaling level information determined according to the expected deployment specification and an actual deployment specification of the VNF instance.
  • a scalable apparatus for a VNF instance including: a first determining module, configured to determine a VNF instance that needs to be scaled, and a desired deployment specification that the VNF instance needs to be scaled to
  • the first sending module is configured to send the identifier of the VNF instance and the scaling information determined according to the expected deployment specification to the VNFM, where the identifier of the VNF instance and the scaling information are used to indicate that the VNFM is configured according to the VNFM.
  • the scaling information performs scaling processing on the VNF instance.
  • the first determining module when determining the VNF instance that needs to be scaled, includes: a first determining unit, configured to determine the one or more VNF instances according to performance data of the collected one or more VNF instances. Processing performance for business processing; second determination a VNF instance that is set to determine that the processing performance is lower than the first performance threshold or that is higher than the second performance threshold is the VNF instance that needs to be scaled; and/or, in determining that the VNF instance needs to be scaled And the first determining module includes: a third determining unit, configured to determine the desired deployment according to a preset deployment specification of the VNF instance that needs to be scaled according to requirements and an ability that the VNF instance is expected to reach specification.
  • the preset deployment specification of the VNF instance is obtained by acquiring the preset deployment specification from the VNF instance, and obtaining the preset deployment specification by using a private interface with the database, where The information about the preset deployment specification is stored in the database; the preset deployment specification is obtained from the VNFM; and the preset deployment specification is obtained from the NMS.
  • the first determining module includes: a first receiving unit, configured to receive a first telescopic command sent by the NMS to indicate that the VNF instance is subjected to a scaling process, where the first telescopic command is carried An identifier of the VNF instance and an identifier of the desired deployment specification; a fourth determining unit configured to determine the VNF instance and the desired deployment specification according to the first scaling command; or, the second receiving unit, setting And a second telescopic command sent by the NMS to indicate that the VNF instance is to be scaled, where the second retractable command carries the identifier of the VNF instance and the capability of the VNF instance to be scaled to
  • the fifth determining unit is configured to determine the VNF instance according to the first scaling command, and the EMS determines, according to the capability that the VNF instance needs to be scaled and the preset deployment specification of the VNF instance. Expect to deploy specifications.
  • the scaling information includes one of the following: the identifier information of the desired deployment specification, and the scaling type information and the scaling level information determined according to the expected deployment specification and an actual deployment specification of the VNF instance.
  • a scalable apparatus for a VNF instance comprising: a second determining module configured to determine that a VNF instance needs to be scaled; and a second sending module configured to send to the EMS And a scaling command for instructing the VNF instance to be scaled; wherein the scaling command is used to instruct the EMS to determine an identifier of the VNF instance and a desired deployment specification that the EMS needs to scale according to the VNF instance.
  • the scaling information is sent to the VNFM, and the identifier of the VNF instance and the scaling information are used to instruct the VNFM to perform scaling processing on the VNF instance according to the scaling information.
  • the second sending module includes: a first sending unit, configured to send a first telescopic command to the EMS, where the retractable command carries an identifier of the VNF instance and the desired deployment
  • the second sending unit is configured to send a second scaling command to the EMS, where the second scaling command carries the identifier of the VNF instance and the capability that the VNF instance needs to be scaled, wherein
  • the EMS determines the desired deployment specification according to the capability that the VNF instance needs to be scaled to and the preset deployment specification of the VNF instance.
  • the scaling information includes one of the following: the identifier information of the desired deployment specification, and the scaling type information and the scaling level information determined according to the expected deployment specification and an actual deployment specification of the VNF instance.
  • a scaling device of a VNF instance is provided, and the device is applied to a VNFM, and includes: a receiving module, configured to receive identifiers and extension information of a VNF instance that needs to be scaled from an EMS, where the scaling The information is the scaling information determined by the EMS according to the desired deployment specification that the VNF instance needs to be scaled to; the processing module is configured to perform scaling processing on the VNF instance according to the scaling information.
  • the scaling information includes one of the following: the identifier information of the desired deployment specification, and the scaling type information and the scaling level information determined according to the expected deployment specification and an actual deployment specification of the VNF instance.
  • a storage medium configured to store program code for performing the following steps:
  • the NE management system EMS determines the VNF instance that needs to be scaled and the expected deployment specifications that the VNF instance needs to scale to;
  • the EMS sends the identifier of the VNF instance and the scaling information determined according to the foregoing deployment specification to the VNFM, where the identifier and the scaling information of the VNF instance are used to instruct the VNFM to perform the scaling processing on the VNF instance according to the scaling information.
  • the storage medium is further configured to store program code for performing the following steps:
  • the NMS determines that a VNF instance needs to be scaled
  • the NMS sends a telescopic command for instructing the VNF instance to perform the scaling process to the EMS, where the scaling command is used to instruct the EMS to identify the VNF instance and the EMS according to the foregoing EMS.
  • the scaling information determined by the desired deployment specification of the VNF instance is sent to the VNFM.
  • the identifier and the scaling information of the VNF instance are used to instruct the VNFM to perform scaling processing on the VNF instance according to the scaling information.
  • the storage medium is further configured to store program code for performing the following steps:
  • the VNFM receives the identification and scaling information of the VNF instance that needs to be scaled from the EMS, where the scaling information is the scaling information determined by the EMS according to the desired deployment specification that the VNF instance needs to be scaled to;
  • the VNFM performs a scaling process on the VNF instance according to the scaling information.
  • the ENF is used to determine the VNF instance that needs to be scaled and the desired deployment specification that the VNF instance needs to be scaled to; the EMS sends the identifier of the VNF instance and the scaling information determined according to the expected deployment specification.
  • the VNFM is configured to indicate that the VNFM performs scaling processing on the VNF instance according to the scaling information.
  • the problem of the VNF expansion that cannot be triggered by the EMS is solved in the related art.
  • the scaling of the VNF instance is implemented by the EMS triggering, and the triggering speed of the VNF instance scaling is improved.
  • FIG. 1 is a reference diagram of a network function virtualization reference architecture in the related art
  • FIG. 2 is a flowchart of a method for scaling a first VNF instance according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for scaling a second VNF instance according to an embodiment of the present invention
  • FIG. 4 is a flowchart of a method for scaling a third VNF instance according to an embodiment of the present invention
  • FIG. 5 is an overall flowchart of a VNF instance expansion according to an embodiment of the present invention.
  • FIG. 6 is a structural block diagram of a telescopic device of a first VNF example according to an embodiment of the present invention.
  • FIG. 7 is a structural block diagram 1 of a first determining module 62 in a telescopic device of a first VNF example according to an embodiment of the present invention
  • FIG. 8 is a first determining module in a telescopic device of a first VNF example according to an embodiment of the present invention.
  • FIG. 9 is a structural block diagram of a telescopic device of a second VNF example according to an embodiment of the present invention.
  • FIG. 10 is a structural block diagram of a second transmitting module 94 in a telescopic device of a second VNF instance according to an embodiment of the present invention
  • FIG. 11 is a block diagram showing the structure of a telescopic device of a third VNF example according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of a method for scaling a first VNF instance according to an embodiment of the present invention. As shown in FIG. 2, the process includes the following steps:
  • Step S202 the EMS determines the VNF instance that needs to be scaled and the desired deployment specification that the VNF instance needs to be scaled to;
  • Step S204 The EMS sends the identifier of the VNF instance and the scaling information determined according to the foregoing deployment specification to the VNFM, where the identifier and the scaling information of the VNF instance are used to instruct the VNFM to perform the scaling processing on the VNF instance according to the scaling information.
  • the EMS sends the VNF instance identifier and the scaling information determined according to the expected deployment specification that the VNF instance needs to be scaled to the VNFM for performing the VNF instance scaling process.
  • the process of triggering and implementing the scaling process of the VNF instance through the EMS is implemented, and the specific content included in the parameters sent by the EMS to the VNFM is clarified, and the problem that the VNF cannot be triggered by the EMS trigger in the related technology is solved.
  • the ENF triggers the scaling of the VNF instance to improve the trigger speed of the VNF instance scaling.
  • the EMS determines the VNF instance package that needs to be scaled.
  • the EMS determines the processing performance of the one or more VNF instances for performing the service processing according to the collected performance data of the one or more VNF instances; the EMS determines that the processing performance is lower than the first performance threshold of the VNF instance or the processing performance is high.
  • the VNF instance of the second performance threshold is a VNF instance that needs to be scaled.
  • the foregoing EMS determines that the desired deployment specification of the VNF instance needs to be scaled to include:
  • the deployment specifications and the capabilities expected of the VNF instance are determined to determine the desired deployment specifications described above.
  • the preset deployment specification of the VNF instance herein may be preset in the VNFD corresponding to the VNF instance. Multiple different levels of deployment specifications are typically preset in VNFD.
  • the EMS can obtain the preset deployment specifications of the VNF instance.
  • the EMS can obtain the preset deployment specifications of the VNF instance in one of the following ways: EMS is from the VNF instance. Obtaining the foregoing preset deployment specification; the EMS obtains the preset deployment specification by using a private interface with the database, where the database stores the information of the preset deployment specification; the EMS obtains the preset deployment specification from the VNFM; The above preset deployment specifications are obtained in the NMS.
  • the EMS and VNF instances may be provided by the same vendor when the EMS obtains the preset deployment specifications through the private interface.
  • the foregoing methods for obtaining the preset deployment specifications are only a few examples, and the preset deployment specifications may be obtained in other manners, which are not enumerated here.
  • the scaling process of the VNF instance is triggered and implemented by the EMS.
  • the scaling process of the VNF instance may also be triggered and implemented by other network elements.
  • the EMS determines that the VNF instance and the VNF instance that needs to be scaled need to be scaled to include: the EMS receives the first extension command sent by the NMS to indicate that the VNF instance is scaled.
  • the first telescopic command carries an identifier of the VNF instance and an identifier of the foregoing deployment specification; the EMS determines the VNF instance and the foregoing desired deployment specification according to the first telescopic command; in another optional embodiment, the foregoing
  • the EMS receives the second telescopic command that is sent by the NMS to indicate that the VNF instance is to be scaled.
  • the second retracting command carries the identifier of the VNF instance and the capability of the VNF instance to be scaled.
  • the EMS is based on the first The scaling command determines the VNF instance, and the foregoing EMS needs to be scaled according to the VNF instance and the preset deployment specifications of the VNF instance. Set the above expected deployment specifications.
  • the first telescopic command and the second telescopic command received by the EMS may be from an Operation-Support System (OSS) or a Business Support System (BSS).
  • OSS Operation-Support System
  • BSS Business Support System
  • the scaling information may include one of the following: the identifier information of the foregoing deployment specification, the scaling type information and the scaling level information determined according to the expected deployment specification and the actual deployment specification of the VNF instance.
  • the VNFM can determine the desired deployment specification according to the identifier of the desired deployment specification, so that the VNF instance can be scaled and reduced or expanded to the desired deployment specification;
  • the VNFM can determine whether to perform the shrinking process or the capacity expansion according to the scaling information.
  • the VNFM can determine the degree of the shrinking or expansion based on the scaling information, and implement the scaling processing of the VNF instance.
  • FIG. 3 is a flowchart of a method for scaling a second VNF instance according to an embodiment of the present invention. As shown in FIG. 3, the process includes the following steps:
  • Step S302 the NMS determines that the VNF instance needs to be extended
  • the NMS sends a telescopic command to the EMS to indicate that the VNF instance is to be scaled.
  • the eSight command is used to instruct the EMS to determine the identifier of the VNF instance and the expected deployment specification that the EMS needs to scale according to the VNF instance.
  • the scaling information is sent to the VNFM.
  • the identifier and the scaling information of the VNF instance are used to instruct the VNFM to perform scaling processing on the VNF instance according to the scaling information.
  • the NMS instructs the EMS to perform the scaling process of the VNF instance.
  • the EMS sends the VNF instance ID to the VNFM according to the NMS indication and the desired deployment according to the VNF instance.
  • the scaling information determined by the specification implements the process of scaling the VNF instance through the EMS, clarifies the specific content contained in the parameters sent by the EMS to the VNFM, and solves the problem that the VNF cannot be triggered by the EMS trigger in the related art.
  • the problem in turn, achieves the effect of triggering the scaling of the VNF instance through EMS triggering, and improving the triggering speed of the VNF instance scaling.
  • the NMS is sent to the EMS to indicate that the need is extended.
  • the scaling command of the shrinking VNF instance to be scaled includes: the NMS sends a first scaling command to the EMS, where the first scaling command carries the identifier of the VNF instance and the expected deployment specification; or the NMS sends the second scaling command to the EMS.
  • the second telescopic command carries the identifier of the VNF instance and the capability of the VNF instance to be scaled.
  • the EMS determines the expected deployment specification according to the capability of the VNF instance to be scaled and the preset deployment specification of the VNF instance.
  • monitoring_parameter which is used to describe which parameters in the VNF instance are monitored, and one or more parameters may be used for Determining the deployment specification of the VNF instance also indicates the capabilities that the VNF instance can provide. Examples of such parameters include, but are not limited to, calls-per second (cps), flows per-second, number-of-subscribers, and the like.
  • the deployment specifications of the VNF instance are involved in the deployment specifications and the default deployment specifications.
  • a VNF instance has multiple VNF deployment specifications. Describes the resources owned by the VNF instance under this specification, such as how many VDUs are included, the configuration of each VDU (such as CPU, memory, network, etc.), which also describes how much processing power the VNF type can provide.
  • the deployment specification of the VNF utilizes one or more of the above monitoring parameters as its deployment specification key indicator (flavour_key) to indicate different deployment specifications. For example, when the number of calls per second (cps) is used as a key indicator, different values of calls-per second can be used to indicate different deployment specifications of the VNF. For example, the deployment specification can be expressed as 10,000 calls per second. 50,000 calls per second, 100,000 calls per second, etc.
  • Each deployment specification also contains an identification (ID).
  • the scaling information may include one of the following: the identifier information of the foregoing deployment specification, the scaling type information and the scaling level information determined according to the expected deployment specification and the actual deployment specification of the VNF instance.
  • the VNFM can determine the desired deployment specification according to the identifier of the desired deployment specification, so that the VNF instance can be scaled and reduced or expanded to the desired deployment specification;
  • the VNFM can determine whether to perform the reduction processing or the expansion processing according to the information about the scaling type.
  • the VNFM can determine the volume reduction based on the scaling information. The extent of the expansion, and thus the scaling of the VNF instance.
  • FIG. 4 is a flowchart of a method for scaling a third VNF instance according to an embodiment of the present invention. As shown in FIG. 4, the process includes the following steps:
  • Step S402 the VNFM receives the identifier and the extension information of the VNF instance that needs to be scaled from the EMS, where the extension information is the extension information determined by the EMS according to the desired deployment specification that the VNF instance needs to be scaled to;
  • Step S404 the VNFM performs a scaling process on the VNF instance according to the scaling information.
  • the VNFM can receive the identifier of the VNF instance from the EMS and the scaling information determined according to the desired deployment specification that the VNF instance needs to be scaled to, thereby implementing the process of triggering and implementing the scaling process of the VNF instance through the EMS.
  • the specific content contained in the parameters sent by the EMS to the VNFM solves the problem that the VNF cannot be triggered by the EMS trigger in the related art, thereby achieving the scaling of the VNF instance triggered by the EMS, and improving the triggering speed of the VNF instance expansion. Effect.
  • the scaling information may include one of the following: the identifier information of the foregoing deployment specification, the scaling type information and the scaling level information determined according to the expected deployment specification and the actual deployment specification of the VNF instance.
  • the VNFM can determine the desired deployment specification according to the identifier of the desired deployment specification, so that the VNF instance can be scaled and reduced or expanded to the desired deployment specification;
  • the VNFM can determine whether to perform the shrinking process or the capacity expansion according to the scaling information.
  • the VNFM can determine the degree of the shrinking or expansion based on the scaling information, and implement the scaling processing of the VNF instance.
  • FIG. 5 is an overall flowchart of a VNF instance scaling according to an embodiment of the present invention. As shown in FIG. 5, the process includes the following steps:
  • the EMS obtains information about a VNF deployment specification (that is, an actual deployment specification) corresponding to the VNF instance.
  • step S504 the EMS determines whether the VNF instance needs to be scaled; if the expansion and contraction is required, the process goes to step S506, otherwise the process ends;
  • the EMS determines which deployment specification the VNF instance should scale to (ie, the desired deployment specification) grid);
  • the EMS sends a request for the VNF instance to be extended to the VNFM.
  • the parameter included in the request may include: a unique identifier of the VNF instance that needs to be scaled, and a deployment specification that the determined VNF instance needs to be scaled to;
  • the VNFM After receiving the request for scaling the VNF instance, the VNFM performs a scaling operation on the corresponding VNF instance.
  • S512 The EMS receives the message that the VNF instance returned by the VNFM is expanded.
  • the method for obtaining the specification information of the VNF by the EMS in the foregoing step S502 includes, but is not limited to, the following methods:
  • the EMS can obtain the VNF specification information through the private interface
  • the EMS determines whether the VNF instance needs to be scaled according to the performance data of the VNF instance.
  • the EMS determines, according to the VNF deployment specification information corresponding to the VNF instance, and the capability that the VNF instance needs to reach, to determine which deployment specification the VNF instance should be scaled to;
  • the specific steps of the VNFM performing the scaling operation on the corresponding VNF instance may include:
  • the VNFM sends a request to the NFVO to approve the scaling of the VNF instance
  • the NFVO checks whether the existing resources can satisfy the applied VNF instance scaling and the related resources are subscribed from the VIM (where the operation of subscribing to the related resources is optional);
  • VIM returns inspection and booking results to NFVO. If the resource meets the demand and the reservation is successful, go to the next step, otherwise the process ends;
  • NFVO returns a response message to the VNFM to approve the scaling of the VNF instance
  • the VNFM requests the VIM to allocate corresponding resources
  • the VIM After the VIM allocates the corresponding resources, it returns an acknowledgement message to the VNFM.
  • the scaling of the VNF instance may also be initiated by the NMS through the EMS. In this embodiment, the following steps may be included:
  • the NMS sends the VNF instance scaling command to the EMS.
  • the command parameters include the unique identifier of the VNF instance and the deployment specifications that the VNF instance needs to be scaled to.
  • the EMS sends a VNF instance scaling request to the VNFM.
  • the parameters included in the request include: a unique identifier of the VNF to be scaled, and a deployment specification that the VNF instance needs to be scaled to;
  • the VNFM After receiving the VNF instance scaling request, the VNFM performs a scaling operation on the corresponding VNF instance.
  • the VNFM After the VNFM completes the scaling of the VNF instance, it returns a message to the EMS to complete the scaling.
  • VNF instance scaling initiated by the NMS through the EMS can also be implemented by the following steps:
  • the NMS sends the VNF instance scaling command to the EMS.
  • the command parameters in the scaling command include the unique identifier of the VNF instance and the ability of the VNF instance to be scaled.
  • the EMS After receiving the scaling command, the EMS determines the deployment specifications of the VNF instance to be scaled according to the capability parameters that the VNF instance needs to be scaled to, and the VNF deployment specification information corresponding to the VNF instance.
  • the EMS sends a VNF instance scaling request to the VNFM.
  • the parameters included in the request include: a unique identifier of the VNF to be scaled, and a deployment specification that the determined VNF instance needs to be scaled to;
  • the VNFM After receiving the VNF instance scaling request, the VNFM performs a scaling operation on the corresponding VNF instance.
  • the VNFM After the VNFM completes the scaling of the VNF instance, it returns a message to the EMS to complete the scaling.
  • CPS calls per second
  • the VNF supported by the VNFD supports deployment specifications of CK of 1K, 5K, and 10K, respectively.
  • the VNF instance extension command initiated by the NMS may also be initiated by an Operation-Support System (OSS) or a Business Support System (BSS).
  • OSS Operation-Support System
  • BSS Business Support System
  • the deployment specifications may be specified.
  • a virtualized network function scaling method is provided, and the steps are as follows:
  • the EMS obtains the VNF specification information corresponding to the VNF instance (that is, the information about the preset deployment specifications of the VNF instance).
  • the EMS determines whether the VNF instance needs to be scaled. If it needs to be scaled, go to the next step. Otherwise, this process is introduced.
  • the EMS determines which specification the VNF instance should scale to
  • the EMS sends a VNF instance extension request to the VNFM.
  • the parameters included in the request include: the unique identifier of the VNF to be scaled, and the specified VNF instance needs to be scaled to;
  • the VNFM After receiving the VNF instance scaling request, the VNFM performs a scaling operation on the corresponding VNF instance.
  • the EMS receives the message that the VNF instance returned by the VNFM is expanded.
  • the specific steps of the VNFM performing the scaling operation on the corresponding VNF instance include:
  • the VNFM sends a request to the NFVO to approve the scaling of the VNF instance
  • NFVO checks whether the existing resources can satisfy the applied VNF instance scaling from the VIM and performs the subscription of related resources (subscription of related resources is an optional solution);
  • VIM returns inspection and booking results to NFVO. If the resource meets the demand and the reservation is successful, go to the next step, otherwise the process ends;
  • NFVO returns a response message to the VNFM to approve the scaling of the VNF instance
  • the VNFM requests the VIM to allocate corresponding resources
  • the VIM After the VIM allocates the corresponding resources, it returns an acknowledgement message to the VNFM.
  • the EMS obtains the VNF specification information corresponding to the VNF instance from the system database through the private interface.
  • the EMS determines whether the VNF instance needs to be scaled according to the performance data of the VNF and the preset performance threshold. If it needs to be scaled, go to the next step. Otherwise, the process is introduced.
  • the EMS determines, according to the VNF specification information corresponding to the VNF instance and the capability that the VNF instance needs to reach, to which specification the VNF instance should be scaled;
  • the EMS sends a VNF instance extension request to the VNFM.
  • the parameters included in the request include: the unique identifier of the VNF to be scaled, and the specified VNF instance needs to be scaled to;
  • the VNFM After receiving the VNF instance scaling request, the VNFM performs a scaling operation on the corresponding VNF instance.
  • the EMS receives the message that the VNF instance returned by the VNFM is expanded.
  • the EMS obtains the VNF specification information corresponding to the VNF instance from the database through the private interface.
  • the EMS receives the "VNF scaling" command from the NMS.
  • the parameters of the command include the “identity of the VNF instance to be scaled” (vnfr_id) and the “capability to reach after VNF scaling” (deployment_flavour-flavour_key) parameter.
  • the EMS determines the capability of the VNF instance to be retracted after the VNF instance is scaled, for example, when the VNF instance is a vPGW (Packet Data Network Gateway).
  • the "capability to reach after VNF scaling" is that the number of calls per second (calls per second) is 10K, which is the maximum. Support 10,000 calls per second.
  • the EMS sends a VNF instance extension request to the VNFM.
  • the parameters included in the request include: the unique identifier of the VNF to be scaled, and the specified VNF instance needs to be scaled to;
  • the VNFM After receiving the VNF instance scaling request, the VNFM performs a scaling operation on the corresponding VNF instance.
  • the EMS receives the message that the VNF instance returned by the VNFM is completed.
  • the EMS sends a message to the NMS that the VNF instance is extended.
  • the EMS obtains the VNF specification information corresponding to the VNF instance from the NMS.
  • the EMS receives the "VNF scaling" command from the NMS.
  • the parameters of the command include the “identity of the VNF instance to be scaled” (vnfr_id) and the “Specification ID corresponding to the specification to be reached after the VNF is expanded” (deployment_flavour-flavour_key).
  • the EMS sends a VNF instance extension request to the VNFM.
  • the parameters included in the request include: a unique identifier of the VNF to be scaled, and a specification ID corresponding to the specification to which the VNF instance needs to be scaled.
  • the VNFM After receiving the VNF instance scaling request, the VNFM performs a scaling operation on the corresponding VNF instance.
  • the EMS receives the message that the VNF instance returned by the VNFM is completed.
  • the EMS sends a message to the NMS that the VNF instance is extended.
  • the EMS obtains the VNF specification information corresponding to the VNF instance from the VNF instance.
  • the EMS receives the "VNF scaling" command from the OSS.
  • the parameters of the command include the “identity of the VNF instance to be scaled” (vnfr_id) and the “Specification ID corresponding to the specification to be reached after the VNF is expanded” (deployment_flavour-flavour_key).
  • the EMS sends a VNF instance extension request to the VNFM.
  • the parameters included in the request include: a unique identifier of the VNF to be scaled, and a specification ID corresponding to the specification to which the VNF instance needs to be scaled.
  • the VNFM After receiving the VNF instance scaling request, the VNFM performs a scaling operation on the corresponding VNF instance.
  • the EMS receives the message that the VNF instance returned by the VNFM is completed.
  • the EMS sends a message to the OSS that the VNF instance is expanded.
  • the information carried in the instruction sent by the OSS to the EMS may also be the “identity of the VNF instance to be scaled” (vnfr_id) and the “capability of reaching the VNF after deployment” (deployment_flavour-flavour_key) parameter.
  • vnfr_id the “identity of the VNF instance to be scaled”
  • deployment_flavour-flavour_key the “capability of reaching the VNF after deployment”
  • a virtualized network function is provided in the case that the current deployment specification of the VNF instance is known or can be obtained, and the preset deployment specifications corresponding to the VNF instance are sorted according to the capability from small to large.
  • the scaling method is as follows:
  • the EMS obtains the VNF specification information corresponding to the VNF instance (that is, the information about the preset deployment specifications of the VNF instance) and the current actual deployment specifications of the VNF instance.
  • the EMS determines whether the VNF instance needs to be scaled. If it needs to be scaled, go to the next step. Otherwise, this process is introduced.
  • the EMS determines which specification the VNF instance should scale to, that is, the expected deployment specification of the VNF instance;
  • the EMS compares the expected deployment specifications of the VNF instance with the current actual deployment specifications to determine the parameters for the VNF instance to be scaled: 1) If the expected deployment specification is higher than the actual deployment specification (that is, the corresponding capability is greater than the actual deployment specification) Then, it is determined that the scaling action to be performed is expansion, otherwise it is volume reduction; 2) calculating the absolute value of the difference between the level of the desired deployment specification and the actual deployment specification, as the level of capacity expansion or contraction.
  • the EMS sends a request to the VNFM for the VNF instance to be scaled.
  • the parameters included in the request include the unique identifier of the VNF instance to be scaled, the type of the scaling action to be performed by the VNF instance (expansion or reduction), and the level of capacity expansion or reduction.
  • the VNFM After receiving the VNF instance scaling request, the VNFM performs a scaling operation on the corresponding VNF instance.
  • the EMS receives the message that the VNF instance returned by the VNFM is expanded.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
  • a telescopic device of the VNF example is also provided in the embodiment, and the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 6 is a structural block diagram of a telescopic apparatus of a first VNF example according to an embodiment of the present invention.
  • the apparatus may be applied to an EMS.
  • the first determining module 62 and the first sending module 64 are provided. The device is described.
  • the first determining module 62 is configured to determine a VNF instance that needs to be scaled and a desired deployment specification that the VNF instance needs to be scaled to; the first sending module 64 is connected to the first determining module 62, and is configured to identify the VNF instance. And the scaling information determined according to the foregoing deployment specification is sent to the VNFM, where the identifier and the scaling information of the VNF instance are used to instruct the VNFM to perform the scaling processing on the VNF instance according to the scaling information.
  • FIG. 7 is a first determining module in a telescopic device of a first VNF example according to an embodiment of the present invention.
  • Structural Block Diagram 1 of FIG. 62, the first determining module 62 will be described below with reference to FIG.
  • the first determining module 62 includes: a first determining unit 72, configured to determine, according to performance data of the collected one or more VNF instances, one or more VNF instances for performing services Processing performance of the processing; the second determining unit 74 is connected to the first determining unit 72, and is configured to determine that the VNF instance whose processing performance is lower than the first performance threshold or the VNF instance whose processing performance is higher than the second performance threshold is required to be expanded and contracted.
  • a first determining unit 72 configured to determine, according to performance data of the collected one or more VNF instances, one or more VNF instances for performing services Processing performance of the processing
  • the second determining unit 74 is connected to the first determining unit 72, and is configured to determine that the VNF instance whose processing performance is lower than the first performance threshold or the VNF instance whose processing performance is higher than the second performance threshold is required to be expanded and contracted.
  • the first determining module 62 includes: a third determining unit 76 configured to preset the deployment specification of the VNF instance that needs to be scaled according to requirements and the capability that the VNF instance is expected to reach. Determine the above expected deployment specifications.
  • the EMS can obtain the preset deployment specification of the VNF instance by obtaining the preset deployment specification from the VNF instance, and obtaining the preset deployment specification by using a private interface with the database, where The database stores the preset deployment specifications.
  • the preset deployment specifications are obtained from the VNFM.
  • the preset deployment specifications are obtained from the NMS.
  • FIG. 8 is a structural block diagram 2 of a first determining module 62 in a telescopic device of a first VNF example according to an embodiment of the present invention.
  • the first determining module 62 includes a first receiving unit 82 and a fourth determining.
  • the unit 84, or the first determining module 62 includes a second receiving unit 86 and a fifth determining unit 88, which will be described below.
  • the first receiving unit 82 is configured to receive a first telescopic command sent by the NMS to indicate that the VNF instance is subjected to the scaling process, where the first retracting command carries the identifier of the VNF instance and the identifier of the desired deployment specification.
  • the determining unit 84 is connected to the first receiving unit 82, and configured to determine the VNF instance and the foregoing deployment specification according to the first scaling command;
  • the second receiving unit 86 is configured to receive a second telescopic command that is sent by the NMS and is used to perform the scaling process on the VNF instance, where the second telescopic command carries the identifier of the VNF instance and the VNF instance needs to be expanded and contracted.
  • the fifth determining unit 88 is connected to the second receiving unit 86, and is configured to determine the VNF instance according to the first scaling command, and the EMS needs to be expanded according to the foregoing VNF instance and the preset of the VNF instance.
  • the deployment specification determines the above expected deployment specifications.
  • the foregoing scaling information includes one of the following: the identification information of the foregoing required deployment specification; the extension type information and the scaling level information determined according to the expected deployment specification and the actual deployment specification of the VNF instance.
  • FIG. 9 is a structural block diagram of a telescopic apparatus of a second VNF example according to an embodiment of the present invention.
  • the apparatus may be applied to an NMS.
  • the apparatus includes a second determining module 92 and a second sending module 94. The device will be described below.
  • the second determining module 92 is configured to determine that the VNF instance needs to be extended; the second sending module 94 is connected to the second determining module 92, and is configured to send a telescopic command for instructing the VNF instance to perform the scaling process to the EMS.
  • the scaling command is used to instruct the EMS to send the identifier of the VNF instance and the scaling information determined by the EMS according to the desired deployment specification that the VNF instance needs to be scaled to the VNFM.
  • the identifier and the scaling information of the VNF instance are used to indicate that the VNFM is in accordance with the foregoing scaling information.
  • the VNF instance is scaled.
  • FIG. 10 is a structural block diagram of a second sending module 94 in a telescopic device of a second VNF instance according to an embodiment of the present invention.
  • the second sending module 94 includes a first sending unit 102 or a second sending unit. 104.
  • the second transmitting module 94 will be described below.
  • the first sending unit 102 is configured to send a first telescopic command to the EMS, where the retractable command carries the identifier of the VNF instance and the foregoing deployment specification.
  • the second sending unit 104 is configured to send a second scaling command to the EMS, where the second scaling command carries the identifier of the VNF instance and the capability of the VNF instance to be scaled, wherein the EMS needs to be expanded according to the VNF instance.
  • the capabilities and the default deployment specifications of the VNF instance determine the desired deployment specifications above.
  • the foregoing scaling information includes one of the following: the identification information of the foregoing required deployment specification; the extension type information and the scaling level information determined according to the expected deployment specification and the actual deployment specification of the VNF instance.
  • FIG. 11 is a structural block diagram of a telescopic apparatus of a third VNF example according to an embodiment of the present invention.
  • the apparatus may be applied to a VNFM.
  • the apparatus includes a receiving module 112 and a processing module 114. Description of the device:
  • the receiving module 112 is configured to receive a label of the VNF instance from the EMS that needs to be scaled And the scaling information, wherein the scaling information is the scaling information determined by the EMS according to the desired deployment specification that the VNF instance needs to be scaled to; the processing module 114 is connected to the receiving module 112, and configured to perform the scaling processing on the VNF instance according to the scaling information. .
  • the foregoing scaling information includes one of the following: the identification information of the foregoing required deployment specification; the extension type information and the scaling level information determined according to the expected deployment specification and the actual deployment specification of the VNF instance.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.
  • the embodiment of the invention further provides a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the EMS determines a VNF instance that needs to be scaled, and a desired deployment specification that the VNF instance needs to be scaled to;
  • the EMS sends the identifier of the VNF instance and the scaling information determined according to the foregoing deployment specification to the VNFM, where the identifier and the scaling information of the VNF instance are used to instruct the VNFM to perform the scaling processing on the VNF instance according to the scaling information.
  • the storage medium is further arranged to store program code for performing the following steps:
  • S21 The NMS determines that the VNF instance needs to be extended.
  • the NMS sends a telescopic command to the EMS to indicate that the VNF instance is to be scaled.
  • the eSight command is used to instruct the EMS to determine the identifier of the VNF instance and the expected deployment specification that the EMS needs to scale according to the VNF instance.
  • the scaling information is sent to the VNFM.
  • the identifier and the scaling information of the VNF instance are used to instruct the VNFM to perform scaling processing on the VNF instance according to the scaling information.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the VNFM receives the identifier and the scaling information of the VNF instance that needs to be scaled from the EMS, where the scaling information is the scaling information determined by the EMS according to the desired deployment specification that the VNF instance needs to be scaled to;
  • the VNFM performs scaling processing on the VNF instance according to the scaling information.
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, and a magnetic
  • ROM read-only memory
  • RAM random access memory
  • mobile hard disk a magnetic
  • magnetic A variety of media that can store program code, such as a disc or a disc.
  • the processor executes steps S11-S12 according to the stored program code in the storage medium.
  • the processor performs steps S21-S22 according to the stored program code in the storage medium.
  • the processor executes steps S31-S32 according to the stored program code in the storage medium.
  • the method for obtaining the VNF specification information by using the EMS in the embodiment of the present invention directly provides the VNFM with the specification of the VNF instance to be scaled when the VNF expansion command is initiated, and the VNFM performs the scaling operation on the corresponding VNF instance after receiving the instruction.
  • the goal of how to efficiently initiate VNF instance scaling operations between EMS and VNFM is achieved.
  • modules or steps of the present application can be implemented by a general computing device, which can be concentrated on a single computing device or distributed in a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the application is not limited to any particular combination of hardware and software.
  • the application provides a scaling method of a VNF instance and a scaling device of the VNF instance, the method may include: determining, by the EMS, a VNF instance that needs to be scaled and a desired deployment specification that the VNF instance needs to be scaled to; the EMS will The identifier of the VNF instance and the scaling information determined according to the expected deployment specification are sent to the VNFM, where the identifier of the VNF instance and the scaling information are used to instruct the VNFM to scale the VNF instance according to the scaling information. deal with.
  • the present application further provides an extension method and a scaling device of another VNF instance, the method includes: the NMS determines that the VNF instance needs to be scaled; and the NMS sends a telescopic command to the EMS to indicate that the VNF instance is scaled.
  • the scaling command is used to instruct the EMS to send the identifier of the VNF instance and the scaling information determined by the EMS according to a desired deployment specification that the VNF instance needs to be scaled to, and the identifier of the VNF instance.
  • the scaling information is used to instruct the VNFM to perform scaling processing on the VNF instance according to the scaling information.
  • the present application further provides another VNF instance scaling method and a scaling device, the method comprising: the VNFM receiving the identification and scaling information of the VNF instance that needs to be scaled from the EMS, wherein the scaling information is the EMS according to the The VNF instance needs to be scaled to the scaling information determined by the desired deployment specification.
  • the VNFM performs scaling processing on the VNF instance according to the scaling information.
  • the embodiment of the present invention solves the problem that the VNF cannot be triggered by the EMS triggering in the related art, and the scaling of the VNF instance is implemented by the EMS triggering, and the triggering speed of the VNF instance scaling is improved.

Landscapes

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

Abstract

本文公布一种VNF实例的伸缩方法及装置，其中，该方法包括：EMS确定需要进行伸缩的VNF实例和该VNF实例需要伸缩到的期望部署规格；上述EMS将VNF实例的标识和根据上述期望部署规格确定的伸缩信息发送给VNFM，其中，该VNF实例的标识和伸缩信息设置为指示VNFM按照上述伸缩信息对VNF实例进行伸缩处理。通过本文，解决了相关技术中存在的无法通过EMS触发实现VNF的伸缩的问题，进而达到了通过EMS触发实现VNF实例的伸缩，提高VNF实例伸缩的触发速度的效果。

Description

VNF实例的伸缩方法及装置 技术领域
本申请涉及但不限于通信领域，具体而言，涉及一种VNF实例的伸缩方法及装置。
背景技术
在无线通讯系统的管理领域，网络管理系统(Network Management System，NMS)与网元管理系统(Element Management System，EMS)之间的接口称为北向接口(Itf-N)。EMS主要完成国际电信联盟(International Telecommunication Union，ITU)电信管理网络(Telecommunications Management Network，TMN)中的网元管理层(Element Management Layer，EML)功能，即完成一个或多个移动通信设备的管理功能，通常不同设备供应商之间的EMS无法通用。NMS主要完成ITU TMN中的网络管理层(Network Management Layer，NML)功能，负责一个被管网络内所有网元的管理。对于被管网络(称为子网)内存在多个设备供应商的情况，可以通过各自的EMS管理达到管理整个子网的目的。
目前，为了提高通讯网络的灵活性，降低管理成本，由运营商发起提出了网络功能虚拟化(Network Functions Virtualization，NFV)概念，在使用NFV技术的情况下，原来的物理网元设备由虚拟化网络功能(Virtualized Network Function，VNF)代替，使得网络功能与具体硬件解耦，如图1所示，其中，图1是相关技术中的网络功能虚拟化参考架构图，VNF与底层的网络功能虚拟化基础架构(Network Functions Virtualization Infrastructure，NFVI)隔离。对于VNF的管理，通过EMS对VNF实例进行传统的维护管理功能，而VNF的生命周期管理功能则通过VNF管理器VNFM完成。底层的虚拟基础架构由虚拟基础架构管理器(Virtualised Infrastructure Manager，VIM)进行管理。而具体的网络业务，则一般通过一个或多个VNF实例来完成。对网络业务的管理，则通过NFV编排器NFVO来进行。
实现网络功能虚拟化后，从应用层面来看，要建立一个网络业务实例时，需要先生成网络业务需要的VNF的实例，再由一个或多个VNF实例组 成一个网络业务实例，通过网络业务实例来提供网络业务。而网络功能虚拟化后的一个好处是，随着网络的使用情况的变化，可以动态调整组成网络业务的VNF实例所使用的资源，即对VNF实例进行伸缩，以提供资源的利用率，并达到节能的目的。其中，VNF实例的伸缩包括扩容(scale out或scale up)和缩容(scale in或scale down)。扩容包括两种情况：扩展(scale out)：即当VNF是可以由多个虚拟化部署单元(Virtualization Deployment Unit，VDU)组成的时候，增加组成VNF实例的VDU实例，以增加VNF实例的能力；放大(scale up)：即增加运行VNF实例的虚拟机(Virtual Machine，VM)的配置，如增加中央处理器(Central Processing Unit，CPU)、内存、网络端口等，以增加VNF实例的能力。同样，缩容也包括两种情况：收缩(scale in)：即当VNF是可以由多个VDU组成的时候，减少组成VNF实例的VDU实例，以减少VNF实例的能力；缩小(scale down)：即减少运行VNF实例的虚拟机(VM)的配置，如减少CPU、内存、网络端口等，以减少VNF实例的能力；目前，对于如何进行VNF实例的伸缩(扩展和收缩)有了初步的研究，并给出了VNF实例伸缩的总体流程。但目前的研究，并没有明确如何利用EMS触发VNF实例的伸缩，即没有明确EMS通过虚拟化网络功能管理器(VNFM)发起VNF实例伸缩时应该提供什么样的参数来告诉VNFM如何进行VNF实例的伸缩，也没有明确向VNFM提供的参数如何而来，因此，相关技术中无法实现通过EMS触发实现VNF实例的伸缩的方案。
针对相关技术中存在的无法通过EMS触发实现VNF实例的伸缩的问题，目前尚未提出有效的解决方案。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保围。
本发明实施例提供了一种VNF实例的伸缩方法及装置。
一个方面，提供了一种VNF实例的伸缩方法，包括：EMS确定需要进行伸缩的VNF实例和所述VNF实例需要伸缩到的期望部署规格；所述EMS将所述VNF实例的标识和根据所述期望部署规格确定的伸缩信息发送给VNFM，其中，所述VNF实例的标识和所述伸缩信息用于指示所述VNFM 按照所述伸缩信息对所述VNF实例进行伸缩处理。
可选地，所述EMS确定需要进行伸缩的VNF实例包括：所述EMS根据收集的一个或多个VNF实例的性能数据确定所述一个或多个VNF实例的用于进行业务处理的处理性能；所述EMS确定处理性能低于第一性能阈值的VNF实例或者处理性能高于第二性能阈值的VNF实例为需要进行伸缩的所述VNF实例；和/或，所述EMS确定所述VNF实例需要伸缩到的期望部署规格包括：所述EMS根据需要进行伸缩的所述VNF实例的预设部署规格和期望所述VNF实例达到的能力确定所述期望部署规格。
可选地，所述EMS通过如下方式之一获取所述VNF实例的预设部署规格：所述EMS从所述VNF实例中获取所述预设部署规格；所述EMS通过与数据库的私有接口获取所述预设部署规格，其中，所述数据库中存储有所述预设部署规格的信息；所述EMS从所述VNFM中获取所述预设部署规格；所述EMS从NMS中获取所述预设部署规格。
可选地，所述EMS确定需要进行伸缩的VNF实例和所述VNF实例需要伸缩到的期望部署规格包括：所述EMS接收NMS发送的用于指示对所述VNF实例进行伸缩处理的第一伸缩命令，其中，所述第一伸缩命令中携带有所述VNF实例的标识和所述期望部署规格的标识；所述EMS根据所述第一伸缩命令确定所述VNF实例和所述期望部署规格；或者，所述EMS接收NMS发送的用于指示对所述VNF实例进行伸缩处理的第二伸缩命令，其中，所述第二伸缩命令中携带有所述VNF实例的标识和所述VNF实例需要伸缩到的能力的信息；所述EMS根据所述第一伸缩命令确定所述VNF实例，并且，所述EMS根据所述VNF实例需要伸缩到的能力和所述VNF实例的预设部署规格确定所述期望部署规格。
可选地，所述伸缩信息包括以下之一：所述期望部署规格的标识信息；根据所述期望部署规格和所述VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。
另一方面，提供了一种VNF实例的伸缩方法，包括：NMS确定需要进行伸缩VNF实例；所述NMS向EMS发送用于指示对所述VNF实例进行伸缩处理的伸缩命令；其中，所述伸缩命令用于指示所述EMS将所述VNF实 例的标识和由所述EMS根据所述VNF实例需要伸缩到的期望部署规格确定的伸缩信息发送给VNFM，所述VNF实例的标识和所述伸缩信息用于指示所述VNFM按照所述伸缩信息对所述VNF实例进行伸缩处理。
可选地，所述NMS向所述EMS发送用于指示对需要进行伸缩的所述VNF实例进行伸缩处理的所述伸缩命令包括：所述NMS向所述EMS发送第一伸缩命令，其中，所述一伸缩命令中携带有所述VNF实例的标识和所述期望部署规格；或者，所述NMS向所述EMS发送第二伸缩命令，其中，所述第二伸缩命令中携带有所述VNF实例的标识和所述VNF实例需要伸缩到的能力，其中，所述EMS根据所述VNF实例需要伸缩到的能力和所述VNF实例的预设部署规格确定所述期望部署规格。
可选地，所述伸缩信息包括以下之一：所述期望部署规格的标识信息；根据所述期望部署规格和所述VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。
另一方面，提供了一种VNF实例的伸缩方法，包括：VNFM接收来自EMS的需要进行伸缩的VNF实例的标识和伸缩信息，其中，所述伸缩信息为所述EMS根据所述VNF实例需要伸缩到的期望部署规格确定的伸缩信息；所述VNFM根据所述伸缩信息对所述VNF实例进行伸缩处理。
可选地，所述伸缩信息包括以下之一：所述期望部署规格的标识信息；根据所述期望部署规格和所述VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。
另一方面，提供了一种VNF实例的伸缩装置，所述装置应用于EMS中，包括：第一确定模块，设置为确定需要进行伸缩的VNF实例和所述VNF实例需要伸缩到的期望部署规格；第一发送模块，设置为将所述VNF实例的标识和根据所述期望部署规格确定的伸缩信息发送给VNFM，其中，所述VNF实例的标识和所述伸缩信息用于指示所述VNFM按照所述伸缩信息对所述VNF实例进行伸缩处理。
可选地，在确定需要进行伸缩的VNF实例时，所述第一确定模块包括：第一确定单元，设置为根据收集的一个或多个VNF实例的性能数据确定所述一个或多个VNF实例的用于进行业务处理的处理性能；第二确定单 元，设置为确定处理性能低于第一性能阈值的VNF实例或者处理性能高于第二性能阈值的VNF实例为需要进行伸缩的所述VNF实例；和/或，在确定所述VNF实例需要伸缩到的期望部署规格时，所述第一确定模块包括：第三确定单元，设置为根据需要进行伸缩的所述VNF实例的预设部署规格和期望所述VNF实例达到的能力确定所述期望部署规格。
可选地，通过如下方式之一获取所述VNF实例的预设部署规格：从所述VNF实例中获取所述预设部署规格；通过与数据库的私有接口获取所述预设部署规格，其中，所述数据库中存储有所述预设部署规格的信息；从所述VNFM中获取所述预设部署规格；从NMS中获取所述预设部署规格。
可选地，所述第一确定模块包括：第一接收单元，设置为接收NMS发送的用于指示对所述VNF实例进行伸缩处理的第一伸缩命令，其中，所述第一伸缩命令中携带有所述VNF实例的标识和所述期望部署规格的标识；第四确定单元，设置为根据所述第一伸缩命令确定所述VNF实例和所述期望部署规格；或者，第二接收单元，设置为接收NMS发送的用于指示对所述VNF实例进行伸缩处理的第二伸缩命令，其中，所述第二伸缩命令中携带有所述VNF实例的标识和所述VNF实例需要伸缩到的能力的信息；第五确定单元，设置为根据所述第一伸缩命令确定所述VNF实例，并且，所述EMS根据所述VNF实例需要伸缩到的能力和所述VNF实例的预设部署规格确定所述期望部署规格。
可选地，所述伸缩信息包括以下之一：所述期望部署规格的标识信息；根据所述期望部署规格和所述VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。
另一方面，提供了一种VNF实例的伸缩装置，所述装置应用于NMS中，包括：第二确定模块，设置为确定需要进行伸缩VNF实例；第二发送模块，设置为向EMS发送用于指示对所述VNF实例进行伸缩处理的伸缩命令；其中，所述伸缩命令用于指示所述EMS将所述VNF实例的标识和由所述EMS根据所述VNF实例需要伸缩到的期望部署规格确定的伸缩信息发送给VNFM，所述VNF实例的标识和所述伸缩信息用于指示所述VNFM按照所述伸缩信息对所述VNF实例进行伸缩处理。
可选地，所述第二发送模块包括：第一发送单元，设置为向所述EMS发送第一伸缩命令，其中，所述一伸缩命令中携带有所述VNF实例的标识和所述期望部署规格；或者，第二发送单元，设置为向所述EMS发送第二伸缩命令，其中，所述第二伸缩命令中携带有所述VNF实例的标识和所述VNF实例需要伸缩到的能力，其中，所述EMS根据所述VNF实例需要伸缩到的能力和所述VNF实例的预设部署规格确定所述期望部署规格。
可选地，所述伸缩信息包括以下之一：所述期望部署规格的标识信息；根据所述期望部署规格和所述VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。
另一方面，提供了一种VNF实例的伸缩装置，所述装置应用于VNFM中，包括：接收模块，设置为接收来自EMS的需要进行伸缩的VNF实例的标识和伸缩信息，其中，所述伸缩信息为所述EMS根据所述VNF实例需要伸缩到的期望部署规格确定的伸缩信息；处理模块，设置为根据所述伸缩信息对所述VNF实例进行伸缩处理。
可选地，所述伸缩信息包括以下之一：所述期望部署规格的标识信息；根据所述期望部署规格和所述VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。
另一个方面，还提供了一种存储介质，被设置为存储用于执行以下步骤的程序代码：
网元管理系统EMS确定需要进行伸缩的VNF实例和该VNF实例需要伸缩到的期望部署规格；
所述EMS将VNF实例的标识和根据上述期望部署规格确定的伸缩信息发送给VNFM，其中，所述VNF实例的标识和伸缩信息用于指示VNFM按照上述伸缩信息对VNF实例进行伸缩处理。
其中，所述存储介质还被设置为存储用于执行以下步骤的程序代码：
NMS确定需要进行伸缩VNF实例；
所述NMS向EMS发送用于指示对上述VNF实例进行伸缩处理的伸缩命令；其中，该伸缩命令用于指示EMS将VNF实例的标识和由上述EMS根据 VNF实例需要伸缩到的期望部署规格确定的伸缩信息发送给VNFM，该VNF实例的标识和伸缩信息用于指示VNFM按照上述伸缩信息对VNF实例进行伸缩处理。
其中，所述存储介质还被设置为存储用于执行以下步骤的程序代码：
VNFM接收来自EMS的需要进行伸缩的VNF实例的标识和伸缩信息，其中，所述伸缩信息为EMS根据VNF实例需要伸缩到的期望部署规格确定的伸缩信息；
所述VNFM根据伸缩信息对VNF实例进行伸缩处理。
通过本发明实施例，采用EMS确定需要进行伸缩的VNF实例和所述VNF实例需要伸缩到的期望部署规格；所述EMS将所述VNF实例的标识和根据所述期望部署规格确定的伸缩信息发送给VNFM，其中，所述VNF实例的标识和所述伸缩信息用于指示所述VNFM按照所述伸缩信息对所述VNF实例进行伸缩处理。解决了相关技术中存在的无法通过EMS触发实现VNF的伸缩的问题，通过EMS触发实现了VNF实例的伸缩，提高了VNF实例伸缩的触发速度。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
在附图中：
图1是相关技术中的网络功能虚拟化参考架构图；
图2是根据本发明实施例的第一种VNF实例的伸缩方法的流程图；
图3是根据本发明实施例的第二种VNF实例的伸缩方法的流程图；
图4是根据本发明实施例的第三种VNF实例的伸缩方法的流程图；
图5是根据本发明实施例的VNF实例伸缩的整体流程图；
图6是根据本发明实施例的第一种VNF实例的伸缩装置的结构框图；
图7是根据本发明实施例的第一种VNF实例的伸缩装置中第一确定模块62的结构框图一；
图8是根据本发明实施例的第一种VNF实例的伸缩装置中第一确定模块 62的结构框图二；
图9是根据本发明实施例的第二种VNF实例的伸缩装置的结构框图；
图10是根据本发明实施例的第二种VNF实例的伸缩装置中第二发送模块94的结构框图；
图11是根据本发明实施例的第三种VNF实例的伸缩装置的结构框图。
本发明的实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本实施例中提供了一种VNF实例的伸缩方法，图2是根据本发明实施例的第一种VNF实例的伸缩方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，EMS确定需要进行伸缩的VNF实例和该VNF实例需要伸缩到的期望部署规格；
步骤S204，上述EMS将VNF实例的标识和根据上述期望部署规格确定的伸缩信息发送给VNFM，其中，该VNF实例的标识和伸缩信息用于指示VNFM按照上述伸缩信息对VNF实例进行伸缩处理。
通过上述步骤，EMS在确定需要进行伸缩的VNF实例后，将该VNF实例的标识和根据该VNF实例需要伸缩到的期望部署规格确定的伸缩信息发送给用于执行VNF实例伸缩处理的VNFM，从而实现了通过EMS触发并实现VNF实例的伸缩处理的流程，明确了EMS发送给VNFM的参数中所包含的具体内容，解决了相关技术中存在的无法通过EMS触发实现VNF的伸缩的问题，进而达到了通过EMS触发实现VNF实例的伸缩，提高VNF实例伸缩的触发速度的效果。
在一个可选的实施例中，上述EMS确定需要进行伸缩的VNF实例包 括：EMS根据收集的一个或多个VNF实例的性能数据确定上述一个或多个VNF实例的用于进行业务处理的处理性能；EMS确定处理性能低于第一性能阈值的VNF实例或者处理性能高于第二性能阈值的VNF实例为需要进行伸缩的VNF实例；在另一个可选的实施例中，上述EMS确定VNF实例需要伸缩到的期望部署规格包括：EMS根据需要进行伸缩的VNF实例的预设部署规格和期望VNF实例达到的能力确定上述期望部署规格。其中，这里的VNF实例的预设部署规格可以是在VNF实例对应的VNFD中预先设定的。在VNFD中一般会预设多个不同级别的部署规格。
EMS在获取VNF实例的预设部署规格时，可以有多种获取方式，在一个可选的实施例中，上述EMS可以通过如下方式之一获取VNF实例的预设部署规格：EMS从VNF实例中获取上述预设部署规格；EMS通过与数据库的私有接口获取上述预设部署规格，其中，该数据库中存储有所述预设部署规格的信息；EMS从VNFM中获取上述预设部署规格；EMS从NMS中获取上述预设部署规格。其中，当EMS通过私有接口获取上述预设部署规格时，EMS与VNF实例可以是由同一个厂商提供的。当然，上述的获取预设部署规格的方式仅是几种实例，还可以通过其他的方式获取预设部署规格，在此不一一列举。
在上述的各实施例中，VNF实例的伸缩处理是有EMS主动触发并实现的，VNF实例的伸缩处理也可以是由其他的网元触发并实现，下面对其进行说明：
在一个可选的实施例中，上述EMS确定需要进行伸缩的VNF实例和VNF实例需要伸缩到的期望部署规格包括：EMS接收NMS发送的用于指示对上述VNF实例进行伸缩处理的第一伸缩命令，其中，该第一伸缩命令中携带有VNF实例的标识和上述期望部署规格的标识；上述EMS根据第一伸缩命令确定VNF实例和上述期望部署规格；在另一个可选的实施例中，上述EMS接收NMS发送的用于指示对VNF实例进行伸缩处理的第二伸缩命令，其中，该第二伸缩命令中携带有VNF实例的标识和VNF实例需要伸缩到的能力的信息；上述EMS根据第一伸缩命令确定上述VNF实例，并且，上述EMS根据VNF实例需要伸缩到的能力和该VNF实例的预设部署规格确 定上述期望部署规格。
其中，上述的EMS接收的第一伸缩命令、第二伸缩命令也可以是来自由运营支撑系统(Operation-Support System，OSS)或者业务支撑系统(Business Support System，BSS)的。
在一个可选的实施例中，上述的伸缩信息可以包括以下之一：上述期望部署规格的标识信息，根据上述期望部署规格和VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。当伸缩信息为期望部署规格的标识信息时，VNFM可以根据该期望部署规格的标识确定期望部署规格，从而可以对VNF实例进行伸缩处理，将其缩容或者扩容至期望部署规格；当伸缩信息为伸缩类型信息和伸缩级别信息时，VNFM可以根据该伸缩类型信息确定是执行缩容处理，还是扩容处理，VNFM可以根据伸缩级别信息确定缩容或者扩容的程度，进而实现对VNF实例的伸缩处理。
图3是根据本发明实施例的第二种VNF实例的伸缩方法的流程图，如图3所示，该流程包括如下步骤：
步骤S302，NMS确定需要进行伸缩VNF实例；
步骤S304，上述NMS向EMS发送用于指示对上述VNF实例进行伸缩处理的伸缩命令；其中，该伸缩命令用于指示EMS将VNF实例的标识和由EMS根据VNF实例需要伸缩到的期望部署规格确定的伸缩信息发送给VNFM，该VNF实例的标识和伸缩信息用于指示VNFM按照上述伸缩信息对VNF实例进行伸缩处理。
通过上述步骤，NMS在确定了需要进行伸缩处理的VNF实例后，会指示EMS执行VNF实例的伸缩处理，EMS会根据NMS的指示向VNFM发送VNF实例的标识和根据VNF实例需要伸缩到的期望部署规格确定的伸缩信息，从而实现了通过EMS实现VNF实例的伸缩处理的流程，明确了EMS发送给VNFM的参数中所包含的具体内容，解决了相关技术中存在的无法通过EMS触发实现VNF的伸缩的问题，进而达到了通过EMS触发实现VNF实例的伸缩，提高VNF实例伸缩的触发速度的效果。
在一个可选的实施例中，上述NMS向EMS发送用于指示对需要进行伸 缩的VNF实例进行伸缩处理的伸缩命令包括：NMS向EMS发送第一伸缩命令，其中，该第一伸缩命令中携带有VNF实例的标识和期望部署规格；或者，NMS向EMS发送第二伸缩命令，其中，该第二伸缩命令中携带有VNF实例的标识和VNF实例需要伸缩到的能力，其中，该EMS根据VNF实例需要伸缩到的能力和VNF实例的预设部署规格确定上述期望部署规格。
其中，在确定需要进行伸缩处理的VNF实例时，可以根据监控参数(monitoring_parameter)来确定，该监控参数用于描述对VNF实例中的哪些参数进行监测，其中的1个或多个参数可以用于确定该VNF实例的部署规格，也表示了该VNF实例可以提供的能力。这些参数的例子包括但不限于：每秒呼叫数量(calls-per second，cps)、每秒流量(flows per-second)、用户数量(number-of-subscribers)等。
上述的期望部署规格(deployment flavor)、预设部署规格中均涉及到了VNF实例的部署规格，下面对该部署规格进行说明：一般一个VNF实例会有多个VNF的部署规格，每个部署规格描述了在此规格下VNF实例所拥有的资源，如包含多少个VDU，每个VDU的配置(如CPU、内存、网络等参数)，从而也描述了该VNF类型可以提供多少级别的处理能力。VNF的部署规格(deployment flavor)利用上述监测参数中的1个或多个作为其部署规格关键指标(flavour_key)，来表示不同的部署规格。比如当用每秒呼叫数量(calls-per second，cps)作为关键指标时，可以用calls-per second的不同取值来表示VNF的不同部署规格，如部署规格可以表示为每秒1万个呼叫、每秒5万个呼叫、每秒10万个呼叫等；每个部署规格也包含一个标识(Identification，ID)。
在一个可选的实施例中，上述的伸缩信息可以包括以下之一：上述期望部署规格的标识信息，根据上述期望部署规格和VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。当伸缩信息为期望部署规格的标识信息时，VNFM可以根据该期望部署规格的标识确定期望部署规格，从而可以对VNF实例进行伸缩处理，将其缩容或者扩容至期望部署规格；当伸缩信息为伸缩类型信息和伸缩级别信息时，VNFM可以根据该伸缩类型信息确定是执行缩容处理，还是扩容处理，VNFM可以根据伸缩级别信息确定缩容或 者扩容的程度，进而实现对VNF实例的伸缩处理。
图4是根据本发明实施例的第三种VNF实例的伸缩方法的流程图，如图4所示，该流程包括如下步骤：
步骤S402，VNFM接收来自EMS的需要进行伸缩的VNF实例的标识和伸缩信息，其中，该伸缩信息为EMS根据VNF实例需要伸缩到的期望部署规格确定的伸缩信息；
步骤S404，上述VNFM根据伸缩信息对VNF实例进行伸缩处理。
通过上述步骤，VNFM可以接收到来自EMS的VNF实例的标识和根据该VNF实例需要伸缩到的期望部署规格确定的伸缩信息，从而实现了通过EMS触发并实现VNF实例的伸缩处理的流程，明确了EMS发送给VNFM的参数中所包含的具体内容，解决了相关技术中存在的无法通过EMS触发实现VNF的伸缩的问题，进而达到了通过EMS触发实现VNF实例的伸缩，提高VNF实例伸缩的触发速度的效果。
在一个可选的实施例中，上述的伸缩信息可以包括以下之一：上述期望部署规格的标识信息，根据上述期望部署规格和VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。当伸缩信息为期望部署规格的标识信息时，VNFM可以根据该期望部署规格的标识确定期望部署规格，从而可以对VNF实例进行伸缩处理，将其缩容或者扩容至期望部署规格；当伸缩信息为伸缩类型信息和伸缩级别信息时，VNFM可以根据该伸缩类型信息确定是执行缩容处理，还是扩容处理，VNFM可以根据伸缩级别信息确定缩容或者扩容的程度，进而实现对VNF实例的伸缩处理。
图5是根据本发明实施例的VNF实例伸缩的整体流程图，如图5所示，该流程包括如下步骤：
S502，EMS获取VNF实例对应的VNF部署规格(即，实际部署规格)的信息；
S504，EMS判断VNF实例是否需要伸缩；若需要伸缩，则转至步骤S506，否则本流程结束；
S506，EMS确定VNF实例应该伸缩到哪个部署规格(即，期望部署规 格)；
S508，EMS给VNFM发送VNF实例伸缩的请求，该请求中包含的参数可以包括：需要伸缩的VNF实例的唯一标识，确定的VNF实例需要伸缩到的部署规格；
S510，VNFM接收到VNF实例伸缩的请求后，对相应的VNF实例执行伸缩操作；
S512，EMS接收VNFM返回的VNF实例伸缩完成的消息。
其中，上述步骤S502中，EMS获取VNF的规格信息的方法包括但不限于如下几种方式：
通过VNF实例获取；
当EMS和VNF是同一个厂商提供时，EMS可通过私有接口获取VNF规格信息；
从VNFM获取；
从NMS获取；
上述步骤S504中，EMS判断VNF实例是否需要伸缩时，可以是根据VNF实例的性能数据判断VNF实例是否需要伸缩；
上述步骤S506中，EMS确定VNF实例应该伸缩到哪个部署规格时，可以是根据VNF实例对应的VNF部署规格的信息和希望VNF实例达到的能力确定的；
上述步骤S510中，VNFM对相应的VNF实例执行伸缩操作的具体步骤可以包括：
VNFM向NFVO发送批准VNF实例伸缩的请求；
NFVO从VIM检查现有资源是否可以满足申请的VNF实例伸缩，并进行相关资源的预订(其中，订阅相关资源的操作是可选的)；
VIM向NFVO返回检查及预订结果。如果资源满足需求并预订成功，则转下一步，否则本流程结束；
NFVO向VNFM返回批准VNF实例伸缩的应答消息；
VNFM向VIM请求分配相应的资源；
VIM分配相应的资源后，向VNFM返回确认消息。
在一个可选的实施例中，VNF实例的伸缩也可以由NMS通过EMS发起，在该实施例中，可以包括如下步骤：
NMS给EMS下发VNF实例伸缩命令，命令参数包括VNF实例的唯一标识和VNF实例需要伸缩到的部署规格；
EMS给VNFM发送VNF实例伸缩的请求，请求中包含的参数包括：需要伸缩的VNF的唯一标识，VNF实例需要伸缩到的部署规格；
VNFM接收到VNF实例伸缩的请求后，对相应的VNF实例执行伸缩操作；
VNFM完成VNF实例的伸缩后，给EMS返回伸缩完成的消息。
在另一个可选的实施例中，由NMS通过EMS发起的VNF实例伸缩，还可以通过如下步骤实现：
NMS给EMS下发VNF实例伸缩命令，该伸缩命令中的命令参数包括VNF实例的唯一标识和VNF实例需要伸缩到的能力；
EMS接收到伸缩命令后，根据其中的VNF实例需要伸缩到的能力参数，及VNF实例对应的VNF部署规格信息，确定VNF实例需要伸缩到的部署规格；
EMS给VNFM发送VNF实例伸缩的请求，请求中包含的参数包括：需要伸缩的VNF的唯一标识，确定的VNF实例需要伸缩到的部署规格；
VNFM接收到VNF实例伸缩的请求后，对相应的VNF实例执行伸缩操作；
VNFM完成VNF实例的伸缩后，给EMS返回伸缩完成的消息。
具体地，上述步骤中，根据VNF实例进行伸缩后需要到达的能力，确定该VNF实例应伸缩到哪个部署规格，是指根据“VNF伸缩后要到达的能力”参数的值，比如calls per second(CPS)＝3K，对照该VNF实例对应的VNFD中VNF部署规格(deployment flavor)定义，取能满足该能力要求的最 小规格，比如该VNF实例对应的VNFD中VNF支持的部署规格可提供的能力分别为CPS为1K、5K、10K，则这里确定的部署规格为CPS＝5K对应的规格。
在一个可选的实施例中，上述由NMS发起的VNF实例伸缩指令也可以是由运营支撑系统(Operation-Support System，OSS)、业务支撑系统(Business Support System，BSS)发起。
下面结合具体实施例对本申请进行说明，在以下实施例中，部署规格可以规格。
实施例1：
在该实施例中，提供了一种虚拟化网络功能伸缩方法，步骤如下：
EMS获取VNF实例对应的VNF规格信息(即，VNF实例的预设部署规格的信息)；
EMS判断VNF实例是否需要伸缩；若需要伸缩，则转下一步，否则本流程介绍；
EMS确定VNF实例应该伸缩到哪个规格；
EMS给VNFM发送VNF实例伸缩的请求，请求中包含的参数包括：需要伸缩的VNF的唯一标识，确定的VNF实例需要伸缩到的规格；
VNFM接收到VNF实例伸缩的请求后，对相应的VNF实例执行伸缩操作；
EMS接收VNFM返回的VNF实例伸缩完成的消息。
上述的VNFM对相应的VNF实例执行伸缩操作的具体步骤包括：
VNFM向NFVO发送批准VNF实例伸缩的请求；
NFVO从VIM检查现有资源是否可以满足申请的VNF实例伸缩，并进行相关资源的预订(进行相关资源的预订是一个可选的方案)；
VIM向NFVO返回检查及预订结果。如果资源满足需求并预订成功，则转下一步，否则本流程结束；
NFVO向VNFM返回批准VNF实例伸缩的应答消息；
VNFM向VIM请求分配相应的资源；
VIM分配相应的资源后，向VNFM返回确认消息。
实施例2：
在本实施例中提供了另一种虚拟化网络功能伸缩方法，步骤如下：
EMS通过私有接口从系统数据库获取VNF实例对应的VNF规格信息；
EMS根据VNF的性能数据及预设的性能阈值判断VNF实例是否需要伸缩；若需要伸缩，则转下一步，否则本流程介绍；
EMS根据VNF实例对应的VNF规格信息和希望VNF实例达到的能力确定VNF实例应该伸缩到哪个规格；
EMS给VNFM发送VNF实例伸缩的请求，请求中包含的参数包括：需要伸缩的VNF的唯一标识，确定的VNF实例需要伸缩到的规格；
VNFM接收到VNF实例伸缩的请求后，对相应的VNF实例执行伸缩操作；
EMS接收VNFM返回的VNF实例伸缩完成的消息。
实施例3：
本实施例中提供的虚拟化网络功能伸缩的方法，包括如下步骤：
EMS通过私有接口从数据库获取VNF实例对应的VNF规格信息；
EMS从NMS接收到“进行VNF伸缩”的指令，指令的参数包括“要伸缩的VNF实例的标识”(vnfr_id)、“VNF伸缩后要到达的能力”(deployment_flavour-flavour_key)参数。
EMS根据“VNF伸缩后要到达的能力”(deployment_flavour-flavour_key)参数确定所述VNF实例进行伸缩后需要到达的能力，比如对于VNF实例是一个vPGW(虚拟PDN网关-Packet Data Network Gateway)时，这里的“VNF伸缩后要到达的能力”就是每秒呼叫次数(calls per second)为10K，即最大 支持每秒1万次呼叫。然后根据所述VNF实例进行伸缩后需要到达的能力及上述第1步获得的VNF实例对应的VNF规格信息确定VNF实例伸缩后要达到的规格对应的规格ID；
EMS给VNFM发送VNF实例伸缩的请求，请求中包含的参数包括：需要伸缩的VNF的唯一标识，确定的VNF实例需要伸缩到的规格；
VNFM接收到VNF实例伸缩的请求后，对相应的VNF实例执行伸缩操作；
EMS接收VNFM返回的VNF实例伸缩完成的消息；
EMS向NMS发送VNF实例伸缩完成的消息。
实施例4：
本实施例中的虚拟化网络功能伸缩的方法，包括如下步骤：
EMS从NMS获取VNF实例对应的VNF规格信息；
EMS从NMS接收到“进行VNF伸缩”的指令，指令的参数包括“要伸缩的VNF实例的标识”(vnfr_id)、“VNF伸缩后要到达的规格对应的规格ID”(deployment_flavour-flavour_key)参数；
EMS给VNFM发送VNF实例伸缩的请求，请求中包含的参数包括：需要伸缩的VNF的唯一标识、VNF实例需要伸缩到的规格对应的规格ID；
VNFM接收到VNF实例伸缩的请求后，对相应的VNF实例执行伸缩操作；
EMS接收VNFM返回的VNF实例伸缩完成的消息；
EMS向NMS发送VNF实例伸缩完成的消息。
实施例5：
本实施例中提供的虚拟化网络功能伸缩的方法，包括如下步骤：
EMS从VNF实例获取VNF实例对应的VNF规格信息；
EMS从OSS接收到“进行VNF伸缩”的指令，指令的参数包括“要伸缩的VNF实例的标识”(vnfr_id)、“VNF伸缩后要到达的规格对应的规格ID”(deployment_flavour-flavour_key)参数。
EMS给VNFM发送VNF实例伸缩的请求，请求中包含的参数包括：需要伸缩的VNF的唯一标识、VNF实例需要伸缩到的规格对应的规格ID；
VNFM接收到VNF实例伸缩的请求后，对相应的VNF实例执行伸缩操作；
EMS接收VNFM返回的VNF实例伸缩完成的消息；
EMS向OSS发送VNF实例伸缩完成的消息。
需要说明的是，上述OSS发送给EMS的指令中携带的信息也可以是“要伸缩的VNF实例的标识”(vnfr_id)、“VNF伸缩后要到达的能力”(deployment_flavour-flavour_key)参数，具体操作可以参照实施例3。
实施例6：
在该实施例中，在假设EMS已知或可以获取VNF实例当前的部署规格，且VNF实例对应的预设的部署规格是按能力从小到大排序的情况下，提供了一种虚拟化网络功能伸缩方法，步骤如下：
EMS获取VNF实例对应的VNF规格信息(即，VNF实例的预设部署规格的信息)和VNF实例当前的实际部署规格；
EMS判断VNF实例是否需要伸缩；若需要伸缩，则转下一步，否则本流程介绍；
EMS确定VNF实例应该伸缩到哪个规格，即VNF实例的期望部署规格；
EMS比较VNF实例的期望部署规格和当前的实际部署规格，从而确定VNF实例需要伸缩的参数：1)如果期望部署规格比实际部署规格高(即对应的能力比实际部署规格对应的能力要大)，则确定要执行的伸缩动作是扩容，否则就是缩容；2)计算期望部署规格和实际部署规格对应的级别的差值的绝对值，作为扩容或缩容的级别。
EMS给VNFM发送VNF实例伸缩的请求，请求中包含的参数包括：需要执行伸缩的VNF实例的唯一标识，VNF实例需要执行的伸缩动作的类型(扩容或缩容)，扩容或缩容的级别；
VNFM接收到VNF实例伸缩的请求后，对相应的VNF实例执行伸缩操作；
EMS接收VNFM返回的VNF实例伸缩完成的消息。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
在本实施例中还提供了一种VNF实例的伸缩装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图6是根据本发明实施例的第一种VNF实例的伸缩装置的结构框图，该装置可以应用于EMS，如图6所示，包括第一确定模块62和第一发送模块64，下面对该装置进行说明。
第一确定模块62，设置为确定需要进行伸缩的VNF实例和该VNF实例需要伸缩到的期望部署规格；第一发送模块64，连接至上述第一确定模块62，设置为将上述VNF实例的标识和根据上述期望部署规格确定的伸缩信息发送给VNFM，其中，该VNF实例的标识和伸缩信息用于指示VNFM按照上述伸缩信息对VNF实例进行伸缩处理。
图7是根据本发明实施例的第一种VNF实例的伸缩装置中第一确定模块 62的结构框图一，下面结合图7对该第一确定模块62进行说明。
在确定需要进行伸缩的VNF实例时，该第一确定模块62包括：第一确定单元72，设置为根据收集的一个或多个VNF实例的性能数据确定一个或多个VNF实例的用于进行业务处理的处理性能；第二确定单元74，连接至上述第一确定单元72，设置为确定处理性能低于第一性能阈值的VNF实例或者处理性能高于第二性能阈值的VNF实例为需要进行伸缩的上述VNF实例；和/或，
在确定上述VNF实例需要伸缩到的期望部署规格时，该第一确定模块62包括：第三确定单元76，设置为根据需要进行伸缩的VNF实例的预设部署规格和期望该VNF实例达到的能力确定上述期望部署规格。
在一个可选的实施例中，EMS可以通过如下方式之一获取VNF实例的预设部署规格：从上述VNF实例中获取预设部署规格；通过与数据库的私有接口获取上述预设部署规格，其中，该数据库中存储有预设部署规格的信息；从上述VNFM中获取上述预设部署规格；从NMS中获取上述预设部署规格。
图8是根据本发明实施例的第一种VNF实例的伸缩装置中第一确定模块62的结构框图二，如图8所示，该第一确定模块62包括第一接收单元82和第四确定单元84，或者，该第一确定模块62包括第二接收单元86和第五确定单元88，下面对该第一确定模块62进行说明。
第一接收单元82，设置为接收NMS发送的用于指示对VNF实例进行伸缩处理的第一伸缩命令，其中，该第一伸缩命令中携带有VNF实例的标识和期望部署规格的标识；第四确定单元84，连接至上述第一接收单元82，设置为根据上述第一伸缩命令确定VNF实例和上述期望部署规格；
第二接收单元86，设置为接收NMS发送的用于指示对上述VNF实例进行伸缩处理的第二伸缩命令，其中，该第二伸缩命令中携带有VNF实例的标识和该VNF实例需要伸缩到的能力的信息；第五确定单元88，连接至上述第二接收单元86，设置为根据上述第一伸缩命令确定VNF实例，并且，该EMS根据上述VNF实例需要伸缩到的能力和VNF实例的预设部署规格确定上述期望部署规格。
在一个可选的实施例中，上述的伸缩信息包括以下之一：上述期望部署规格的标识信息；根据上述期望部署规格和VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。
图9是根据本发明实施例的第二种VNF实例的伸缩装置的结构框图，该装置可以应用于NMS中，如图9所示，该装置包括第二确定模块92和第二发送模块94，下面对该装置进行说明。
第二确定模块92，设置为确定需要进行伸缩VNF实例；第二发送模块94，连接至上述第二确定模块92，设置为向EMS发送用于指示对VNF实例进行伸缩处理的伸缩命令；其中，该伸缩命令用于指示EMS将VNF实例的标识和由EMS根据VNF实例需要伸缩到的期望部署规格确定的伸缩信息发送给VNFM，该VNF实例的标识和伸缩信息用于指示VNFM按照上述伸缩信息对VNF实例进行伸缩处理。
图10是根据本发明实施例的第二种VNF实例的伸缩装置中第二发送模块94的结构框图，如图10所示，该第二发送模块94包括第一发送单元102或者第二发送单元104，下面对该第二发送模块94进行说明。
第一发送单元102，设置为向EMS发送第一伸缩命令，其中，该一伸缩命令中携带有VNF实例的标识和上述期望部署规格；
第二发送单元104，设置为向上述EMS发送第二伸缩命令，其中，该第二伸缩命令中携带有VNF实例的标识和VNF实例需要伸缩到的能力，其中，该EMS根据VNF实例需要伸缩到的能力和VNF实例的预设部署规格确定上述期望部署规格。
在一个可选的实施例中，上述的伸缩信息包括以下之一：上述期望部署规格的标识信息；根据上述期望部署规格和VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。
图11是根据本发明实施例的第三种VNF实例的伸缩装置的结构框图，该装置可以应用于VNFM中，如图11所示，该装置包括接收模块112和处理模块114，下面对该装置进行说明：
接收模块112，设置为接收来自EMS的需要进行伸缩的VNF实例的标 识和伸缩信息，其中，该伸缩信息为EMS根据VNF实例需要伸缩到的期望部署规格确定的伸缩信息；处理模块114，连接至上述接收模块112，设置为根据上述伸缩信息对VNF实例进行伸缩处理。
在一个可选的实施例中，上述的伸缩信息包括以下之一：上述期望部署规格的标识信息；根据上述期望部署规格和VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述模块分别位于多个处理器中。
本发明实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S11，EMS确定需要进行伸缩的VNF实例和该VNF实例需要伸缩到的期望部署规格；
S12，上述EMS将VNF实例的标识和根据上述期望部署规格确定的伸缩信息发送给VNFM，其中，该VNF实例的标识和伸缩信息用于指示VNFM按照上述伸缩信息对VNF实例进行伸缩处理。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
S21，NMS确定需要进行伸缩VNF实例；
S22，上述NMS向EMS发送用于指示对上述VNF实例进行伸缩处理的伸缩命令；其中，该伸缩命令用于指示EMS将VNF实例的标识和由上述EMS根据VNF实例需要伸缩到的期望部署规格确定的伸缩信息发送给VNFM，该VNF实例的标识和伸缩信息用于指示VNFM按照上述伸缩信息对VNF实例进行伸缩处理。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
S31，VNFM接收来自EMS的需要进行伸缩的VNF实例的标识和伸缩信息，其中，该伸缩信息为EMS根据VNF实例需要伸缩到的期望部署规格确定的伸缩信息；
S32，上述VNFM根据伸缩信息对VNF实例进行伸缩处理。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行步骤S11-S12。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行步骤S21-S22。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行步骤S31-S32。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
通过本发明实施例中提出的通过EMS先获取VNF规格信息，在发起VNF伸缩指令时给VNFM直接提供VNF实例要伸缩到的规格，VNFM在收到指令后对相应的VNF实例进行伸缩操作的方法，从而实现了明确EMS和VNFM之间如何高效地发起VNF实例伸缩操作的目标。
显然，本领域的技术人员应该明白，上述的本申请的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本申请不限制于任何特定的硬件和软件结合。
以上所述仅为本申请的优选实施例而已，并不用于限制本申请，对于本领域的技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。
工业实用性
本申请提供了一种VNF实例的伸缩方法及VNF实例的伸缩装置，该方法可包括：EMS确定需要进行伸缩的VNF实例和所述VNF实例需要伸缩到的期望部署规格；所述EMS将所述VNF实例的标识和根据所述期望部署规格确定的伸缩信息发送给VNFM，其中，所述VNF实例的标识和所述伸缩信息用于指示所述VNFM按照所述伸缩信息对所述VNF实例进行伸缩处理。
本申请还提供了另一种VNF实例的伸缩方法及伸缩装置，该方法包括：NMS确定需要进行伸缩VNF实例；所述NMS向EMS发送用于指示对所述VNF实例进行伸缩处理的伸缩命令；其中，所述伸缩命令用于指示所述EMS将所述VNF实例的标识和由所述EMS根据所述VNF实例需要伸缩到的期望部署规格确定的伸缩信息发送给VNFM，所述VNF实例的标识和所述伸缩信息用于指示所述VNFM按照所述伸缩信息对所述VNF实例进行伸缩处理。
本申请还提供了另一种VNF实例的伸缩方法及伸缩装置，该方法包括：VNFM接收来自EMS的需要进行伸缩的VNF实例的标识和伸缩信息，其中，所述伸缩信息为所述EMS根据所述VNF实例需要伸缩到的期望部署规格确定的伸缩信息；所述VNFM根据所述伸缩信息对所述VNF实例进行伸缩处理。
本发明实施例解决了相关技术中存在的无法通过EMS触发实现VNF的伸缩的问题，通过EMS触发实现了VNF实例的伸缩，提高了VNF实例伸缩的触发速度。

Claims (23)

  1. 一种虚拟化网络功能VNF实例的伸缩方法，包括：
    网元管理系统EMS确定需要进行伸缩的VNF实例和所述VNF实例需要伸缩到的期望部署规格；
    所述EMS将所述VNF实例的标识和根据所述期望部署规格确定的伸缩信息发送给虚拟化网络功能管理器VNFM，其中，所述VNF实例的标识和所述伸缩信息用于指示所述VNFM按照所述伸缩信息对所述VNF实例进行伸缩处理。
  2. 根据权利要求1所述的方法，其中，
    所述EMS确定需要进行伸缩的VNF实例包括：所述EMS根据收集的一个或多个VNF实例的性能数据确定所述一个或多个VNF实例的用于进行业务处理的处理性能；所述EMS确定处理性能低于第一性能阈值的VNF实例或者处理性能高于第二性能阈值的VNF实例为需要进行伸缩的所述VNF实例；和/或，
    所述EMS确定所述VNF实例需要伸缩到的期望部署规格包括：所述EMS根据需要进行伸缩的所述VNF实例的预设部署规格和期望所述VNF实例达到的能力确定所述期望部署规格。
  3. 根据权利要求2所述的方法，其中，所述EMS通过如下方式之一获取所述VNF实例的预设部署规格：
    所述EMS从所述VNF实例中获取所述预设部署规格；
    所述EMS通过与数据库的私有接口获取所述预设部署规格，其中，所述数据库中存储有所述预设部署规格的信息；
    所述EMS从所述VNFM中获取所述预设部署规格；
    所述EMS从网络管理系统NMS中获取所述预设部署规格。
  4. 根据权利要求1所述的方法，其中，所述EMS确定需要进行伸缩的VNF实例和所述VNF实例需要伸缩到的期望部署规格包括：
    所述EMS接收NMS发送的用于指示对所述VNF实例进行伸缩处理的第 一伸缩命令，其中，所述第一伸缩命令中携带有所述VNF实例的标识和所述期望部署规格的标识；所述EMS根据所述第一伸缩命令确定所述VNF实例和所述期望部署规格；或者，
    所述EMS接收NMS发送的用于指示对所述VNF实例进行伸缩处理的第二伸缩命令，其中，所述第二伸缩命令中携带有所述VNF实例的标识和所述VNF实例需要伸缩到的能力的信息；所述EMS根据所述第一伸缩命令确定所述VNF实例，并且，所述EMS根据所述VNF实例需要伸缩到的能力和所述VNF实例的预设部署规格确定所述期望部署规格。
  5. 根据权利要求1所述的方法，其中，所述伸缩信息包括以下之一：
    所述期望部署规格的标识信息；
    根据所述期望部署规格和所述VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。
  6. 一种虚拟化网络功能VNF实例的伸缩方法，包括：
    NMS确定需要进行伸缩VNF实例；
    所述NMS向网元管理系统EMS发送用于指示对所述VNF实例进行伸缩处理的伸缩命令；
    其中，所述伸缩命令用于指示所述EMS将所述VNF实例的标识和由所述EMS根据所述VNF实例需要伸缩到的期望部署规格确定的伸缩信息发送给虚拟化网络功能管理器VNFM，所述VNF实例的标识和所述伸缩信息用于指示所述VNFM按照所述伸缩信息对所述VNF实例进行伸缩处理。
  7. 根据权利要求6所述的方法，其中，所述NMS向所述EMS发送用于指示对需要进行伸缩的所述VNF实例进行伸缩处理的所述伸缩命令包括：
    所述NMS向所述EMS发送第一伸缩命令，其中，所述一伸缩命令中携带有所述VNF实例的标识和所述期望部署规格；或者，
    所述NMS向所述EMS发送第二伸缩命令，其中，所述第二伸缩命令中携带有所述VNF实例的标识和所述VNF实例需要伸缩到的能力，其中，所述EMS根据所述VNF实例需要伸缩到的能力和所述VNF实例的预设部署规格确定所述期望部署规格。
  8. 根据权利要求6所述的方法，其中，所述伸缩信息包括以下之一：
    所述期望部署规格的标识信息；
    根据所述期望部署规格和所述VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。
  9. 一种虚拟化网络功能VNF实例的伸缩方法，包括：
    虚拟化网络功能管理器VNFM接收来自网元管理系统EMS的需要进行伸缩的VNF实例的标识和伸缩信息，其中，所述伸缩信息为所述EMS根据所述VNF实例需要伸缩到的期望部署规格确定的伸缩信息；
    所述VNFM根据所述伸缩信息对所述VNF实例进行伸缩处理。
  10. 根据权利要求9所述的方法，所述伸缩信息包括以下之一：
    所述期望部署规格的标识信息；
    根据所述期望部署规格和所述VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。
  11. 一种虚拟化网络功能VNF实例的伸缩装置，应用于网元管理系统EMS中，包括：
    第一确定模块，设置为确定需要进行伸缩的VNF实例和所述VNF实例需要伸缩到的期望部署规格；
    第一发送模块，设置为将所述VNF实例的标识和根据所述期望部署规格确定的伸缩信息发送给虚拟化网络功能管理器VNFM，其中，所述VNF实例的标识和所述伸缩信息用于指示所述VNFM按照所述伸缩信息对所述VNF实例进行伸缩处理。
  12. 根据权利要求11所述的装置，其中，
    在确定需要进行伸缩的VNF实例时，所述第一确定模块包括：第一确定单元，设置为根据收集的一个或多个VNF实例的性能数据确定所述一个或多个VNF实例的设置为进行业务处理的处理性能；第二确定单元，设置为确定处理性能低于第一性能阈值的VNF实例或者处理性能高于第二性能阈值的VNF实例为需要进行伸缩的所述VNF实例；和/或，
    在确定所述VNF实例需要伸缩到的期望部署规格时，所述第一确定模块包括：第三确定单元，设置为根据需要进行伸缩的所述VNF实例的预设部署规格和期望所述VNF实例达到的能力确定所述期望部署规格。
  13. 根据权利要求11所述的装置，其中，通过如下方式之一获取所述VNF实例的预设部署规格：
    从所述VNF实例中获取所述预设部署规格；
    通过与数据库的私有接口获取所述预设部署规格，其中，所述数据库中存储有所述预设部署规格的信息；
    从所述VNFM中获取所述预设部署规格；
    从网络管理系统NMS中获取所述预设部署规格。
  14. 根据权利要求11所述的装置，其中，所述第一确定模块包括：
    第一接收单元，设置为接收NMS发送的用于指示对所述VNF实例进行伸缩处理的第一伸缩命令，其中，所述第一伸缩命令中携带有所述VNF实例的标识和所述期望部署规格的标识；第四确定单元，设置为根据所述第一伸缩命令确定所述VNF实例和所述期望部署规格；或者，
    第二接收单元，设置为接收NMS发送的用于指示对所述VNF实例进行伸缩处理的第二伸缩命令，其中，所述第二伸缩命令中携带有所述VNF实例的标识和所述VNF实例需要伸缩到的能力的信息；第五确定单元，设置为根据所述第一伸缩命令确定所述VNF实例，并且，所述EMS根据所述VNF实例需要伸缩到的能力和所述VNF实例的预设部署规格确定所述期望部署规格。
  15. 根据权利要求11所述的装置，其中，所述伸缩信息包括以下之一：
    所述期望部署规格的标识信息；
    根据所述期望部署规格和所述VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。
  16. 一种虚拟化网络功能VNF实例的伸缩装置，应用于网络管理系统NMS中，包括：
    第二确定模块，设置为确定需要进行伸缩VNF实例；
    第二发送模块，设置为向网元管理系统EMS发送用于指示对所述VNF实例进行伸缩处理的伸缩命令；
    其中，所述伸缩命令用于指示所述EMS将所述VNF实例的标识和由所述EMS根据所述VNF实例需要伸缩到的期望部署规格确定的伸缩信息发送给虚拟化网络功能管理器VNFM，所述VNF实例的标识和所述伸缩信息用于指示所述VNFM按照所述伸缩信息对所述VNF实例进行伸缩处理。
  17. 根据权利要求16所述的装置，其中，所述第二发送模块包括：
    第一发送单元，设置为向所述EMS发送第一伸缩命令，其中，所述一伸缩命令中携带有所述VNF实例的标识和所述期望部署规格；或者，
    第二发送单元，设置为向所述EMS发送第二伸缩命令，其中，所述第二伸缩命令中携带有所述VNF实例的标识和所述VNF实例需要伸缩到的能力，其中，所述EMS根据所述VNF实例需要伸缩到的能力和所述VNF实例的预设部署规格确定所述期望部署规格。
  18. 根据权利要求16所述的装置，其中，所述伸缩信息包括以下之一：
    所述期望部署规格的标识信息；
    根据所述期望部署规格和所述VNF实例的实际部署规格确定的伸缩类型信息和伸缩级别信息。
  19. 一种虚拟化网络功能VNF实例的伸缩装置，其特征在于，应用于虚拟化网络功能管理器VNFM中，包括：
    接收模块，设置为接收来自网元管理系统EMS的需要进行伸缩的VNF实例的标识和伸缩信息，其中，所述伸缩信息为所述EMS根据所述VNF实例需要伸缩到的期望部署规格确定的伸缩信息；
    处理模块，设置为根据所述伸缩信息对所述VNF实例进行伸缩处理。
  20. 根据权利要求19所述的装置，其中，所述伸缩信息包括以下之一：
    所述期望部署规格的标识信息；
    根据所述期望部署规格和所述VNF实例的实际部署规格确定的伸缩类 型信息和伸缩级别信息。
  21. 一种存储介质，被设置为存储用于执行以下步骤的程序代码：
    网元管理系统EMS确定需要进行伸缩的虚拟化网络功能VNF实例和该VNF实例需要伸缩到的期望部署规格；
    所述EMS将VNF实例的标识和根据上述期望部署规格确定的伸缩信息发送给虚拟化网络功能管理器VNFM，其中，所述VNF实例的标识和伸缩信息用于指示VNFM按照上述伸缩信息对VNF实例进行伸缩处理。
  22. 根据权利要求21所述的存储介质，还被设置为存储用于执行以下步骤的程序代码：
    NMS确定需要进行伸缩VNF实例；
    所述NMS向EMS发送用于指示对上述VNF实例进行伸缩处理的伸缩命令；其中，该伸缩命令用于指示EMS将VNF实例的标识和由上述EMS根据VNF实例需要伸缩到的期望部署规格确定的伸缩信息发送给VNFM，该VNF实例的标识和伸缩信息用于指示VNFM按照上述伸缩信息对VNF实例进行伸缩处理。
  23. 根据权利要求21所述的存储介质，还被设置为存储用于执行以下步骤的程序代码：
    VNFM接收来自EMS的需要进行伸缩的VNF实例的标识和伸缩信息，其中，所述伸缩信息为EMS根据VNF实例需要伸缩到的期望部署规格确定的伸缩信息；
    所述VNFM根据伸缩信息对VNF实例进行伸缩处理。
PCT/CN2016/092721 2015-11-05 2016-08-01 Vnf实例的伸缩方法及装置 WO2017076078A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510749932.0 2015-11-05
CN201510749932.0A CN106685784A (zh) 2015-11-05 2015-11-05 虚拟化网络功能vnf实例的伸缩方法及装置

Publications (1)

Publication Number Publication Date
WO2017076078A1 true WO2017076078A1 (zh) 2017-05-11

Family

ID=58661548

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/092721 WO2017076078A1 (zh) 2015-11-05 2016-08-01 Vnf实例的伸缩方法及装置

Country Status (2)

Country Link
CN (1) CN106685784A (zh)
WO (1) WO2017076078A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190026168A1 (en) * 2017-07-24 2019-01-24 At&T Intellectual Property I, L.P. Geographical Redundancy and Dynamic Scaling for Virtual Network Functions
US10826789B2 (en) 2018-12-27 2020-11-03 At&T Intellectual Property I, L.P. Adjusting triggers for automatic scaling of virtual network functions
US11388109B2 (en) 2019-12-05 2022-07-12 At&T Intellectual Property I, L.P. Hierarchical capacity management in a virtualization environment

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106685683A (zh) * 2015-11-11 2017-05-17 中兴通讯股份有限公司 管理指示发送、vnf自动伸缩功能的管理方法及装置
CN110830272B (zh) * 2018-08-07 2022-09-13 中国移动通信有限公司研究院 一种虚拟网元vnf的操作控制方法、装置及设备
CN111130834B (zh) * 2018-11-01 2021-05-07 大唐移动通信设备有限公司 一种网络弹性策略的处理方法及装置
JP2023548783A (ja) * 2020-10-28 2023-11-21 テレフオンアクチーボラゲット エルエム エリクソン（パブル） Ｎｓまたはｖｎｆのインスタンス化のための方法および装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014110453A1 (en) * 2013-01-11 2014-07-17 Huawei Technologies Co., Ltd. Network function virtualization for a network device
CN104050045A (zh) * 2014-06-27 2014-09-17 华为技术有限公司 基于磁盘io的虚拟资源分配方法及装置
CN104980297A (zh) * 2014-04-14 2015-10-14 中兴通讯股份有限公司 虚拟机资源的变更方法、装置及虚拟网络功能设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105490908A (zh) * 2014-09-16 2016-04-13 中兴通讯股份有限公司 目标资源占用情况的处理方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014110453A1 (en) * 2013-01-11 2014-07-17 Huawei Technologies Co., Ltd. Network function virtualization for a network device
CN104980297A (zh) * 2014-04-14 2015-10-14 中兴通讯股份有限公司 虚拟机资源的变更方法、装置及虚拟网络功能设备
CN104050045A (zh) * 2014-06-27 2014-09-17 华为技术有限公司 基于磁盘io的虚拟资源分配方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ETSI: "NETWORK FUNCTIONS VIRTUALISATION (NFV); MANAGEMENT AND ORCHESTRATIOn", ETSI GS NFV-MAN 001 V1.1.1, 31 December 2014 (2014-12-31), pages 1 - 184, XP055383931 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190026168A1 (en) * 2017-07-24 2019-01-24 At&T Intellectual Property I, L.P. Geographical Redundancy and Dynamic Scaling for Virtual Network Functions
US11003516B2 (en) * 2017-07-24 2021-05-11 At&T Intellectual Property I, L.P. Geographical redundancy and dynamic scaling for virtual network functions
US10826789B2 (en) 2018-12-27 2020-11-03 At&T Intellectual Property I, L.P. Adjusting triggers for automatic scaling of virtual network functions
US11356336B2 (en) 2018-12-27 2022-06-07 At&T Intellectual Property I, L.P. Adjusting triggers for automatic scaling of virtual network functions
US11671332B2 (en) 2018-12-27 2023-06-06 At&T Intellectual Property I, L.P. Adjusting triggers for automatic scaling of virtual network functions
US11388109B2 (en) 2019-12-05 2022-07-12 At&T Intellectual Property I, L.P. Hierarchical capacity management in a virtualization environment

Also Published As

Publication number Publication date
CN106685784A (zh) 2017-05-17

Similar Documents

Publication Publication Date Title
WO2017076078A1 (zh) Vnf实例的伸缩方法及装置
EP3745645B1 (en) Method, device, and system for guaranteeing service level agreement of application
US20200275321A1 (en) Session Management Function Entity Selection Method, Apparatus, and System
EP3800926B1 (en) Alarm method and device
US20190281541A1 (en) Network slice selection method and apparatus
US20170289791A1 (en) Communication method and apparatus using network slice
CN106464534B (zh) 配设和管理用户驻地设备装置的片
WO2019007345A1 (zh) 网络切片的选择方法、装置及系统、存储介质
WO2018028342A1 (zh) 业务处理方法、装置、系统、基站、终端及核心网网元
US20200296170A1 (en) Communication method and apparatus
US11240198B2 (en) Session management method and apparatus
CN110535676B (zh) Smf动态容灾的实现方法、装置、设备及存储介质
WO2019134648A1 (zh) 一种控制面资源迁移的实现方法、装置及网络功能实体
WO2019158010A1 (zh) 资源管理的方法、设备及系统
US9804867B2 (en) Apparatus and method for managing virtual machine in mobile communication system using an edge cloud management controller
US10587462B2 (en) Method and apparatus for deploying virtual operation, administration and maintenance, and virtualized network system
US9445440B2 (en) Method for controlling wireless network devices and control device with wireless network function
WO2016155291A1 (zh) 一种虚拟化网络功能伸缩的管理方法及装置
WO2019029310A1 (zh) 网络管理方法和系统
WO2019057011A1 (zh) 一种网络切片模板的处理方法及管理设备
WO2018171392A1 (zh) 一种虚拟机扩缩容方法及虚拟管理设备
US11490353B2 (en) Path processing method and apparatus, and terminal
US20180062946A1 (en) Method and Apparatus for Establishing Network Service Instance
CN112218342A (zh) 一种实现核心网子切片容灾的方法、装置和系统
WO2019019037A1 (zh) 一种网络注册的方法、相关设备及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16861348

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16861348

Country of ref document: EP

Kind code of ref document: A1