CN112306625B

CN112306625B - Method and related device for deploying virtual machine

Info

Publication number: CN112306625B
Application number: CN201910713371.7A
Authority: CN
Inventors: 李世涛
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-08-02
Filing date: 2019-08-02
Publication date: 2023-02-03
Anticipated expiration: 2039-08-02
Also published as: CN112306625A; WO2021022947A1

Abstract

A method for deploying a virtual machine and a related device are disclosed, which relate to the field of network function virtualization. The method comprises the following steps: at least two virtual resource templates are set in the VNFD. The VNFM sends a virtual resource authorization request to the NFVO to request virtual resource authorization of different processor architectures, and the NFVO can flexibly select a remaining virtual resource from the remaining virtual resources of the different processor architectures, and the remaining virtual resource satisfies a virtual resource required for deploying the virtual machine. Subsequently, the NFVO sends the first virtual resource authorization response or the second virtual resource authorization response to the VNFM to authorize the VNFM to deploy the virtual resource required by the first virtual machine or the virtual resource required by the second virtual machine, and the VNFM may deploy the first virtual machine or the second virtual machine on the server corresponding to the remaining virtual resource of the processor architecture. Compared with the prior art that the virtual machine can be deployed on the residual virtual resources of only one processor architecture, the method and the device for deploying the virtual machine can effectively improve the success rate and efficiency of deploying the virtual machine.

Description

Method and related device for deploying virtual machine

Technical Field

The present application relates to the field of network function virtualization, and in particular, to a method and a related apparatus for deploying a virtual machine.

Background

Network Function Virtualization (NFV) technology is a virtualization technology that virtualizes functions of dedicated devices in a conventional network into independent applications, and is flexibly deployed on a unified infrastructure platform constructed based on other devices such as standard computing hardware, storage hardware, and network hardware. In the NFV system, a party that initiates a Virtual Network Function (VNF) request may be referred to as a virtualized service requester. The party receiving the instantiated VNF request and deploying the VNF according to the instantiated VNF request may be referred to as a virtualized service provider. After the virtualized service provider receives the request for instantiating the VNF, the VNF template (VNF descriptor, VNFD) needs to be obtained. The VNFD includes a Virtual Deployment Unit (VDU). The VDU includes a description of virtual resources required for deploying a Virtual Machine (VM). For example, the virtual resource description includes a processor architecture, a number of processors, a processor frequency, and the like.

In the conventional technology, when the remaining virtual resources in the data center corresponding to the processor architecture in the virtual resource description cannot satisfy the virtual resources required for deploying the virtual machine, a failure in deploying the virtual machine is caused.

Disclosure of Invention

The application provides a method and a related device for deploying a virtual machine, which can effectively improve the success rate of deploying the virtual machine.

In order to achieve the purpose, the technical scheme is as follows:

in a first aspect, a method for deploying a virtual machine is provided, and the method is applicable to a Network Function Virtualization Orchestrator (NFVO) device. The method comprises the following steps: the method comprises the steps that an NFVO receives a virtual resource authorization request, obtains the remaining virtual resources of a first processor architecture and the remaining virtual resources of a second processor architecture in a Virtualized Infrastructure Manager (VIM), and if the NFVO determines that the remaining virtual resources of the first processor architecture meet the virtual resource requirement of a first virtual machine, sends a first virtual resource authorization response to a VNF manager (VNF manager, VNFM) to authorize the VNFM to deploy the virtual resources required by the first virtual machine, wherein the first virtual resource authorization response comprises identification of a first virtual resource template and address information of a first server, and the processor architecture of the first server is the same as the first processor architecture. If the NFVO determines that the remaining virtual resources of the second processor architecture meet the virtual resource requirement of the second virtual machine, sending a second virtual resource authorization response to the VNFM to authorize the VNFM to deploy the virtual resources required by the second virtual machine, wherein the second virtual resource authorization response includes an identifier of a second virtual resource template and address information of a second server, and the processor architecture of the second server is the same as the processor architecture of the second server.

The virtual resource authorization request is used for requesting to authorize the virtual resource required by the first virtual machine or the virtual resource required by the second virtual machine. In some embodiments, the virtual resource authorization request includes an identification of the first virtual resource template and an identification of the second virtual resource template. The first virtual resource template is used to describe virtual resources required for deploying the first virtual machine, and the first virtual resource template includes an identification of the first processor architecture. The second virtual resource template is used to describe virtual resources required for deploying the second virtual machine, and the second virtual resource template includes an identification of the second processor architecture. The first processor architecture is different from the second processor architecture.

According to the method for deploying the virtual machine, the NFVO can flexibly select the residual virtual resources from the residual virtual resources of different processor architectures, and the residual virtual resources meet the virtual resources required by deploying the virtual machine. Subsequently, the NFVO sends the first virtual resource authorization response or the second virtual resource authorization response to the VNFM to authorize the VNFM to deploy the virtual resource required by the first virtual machine or the virtual resource required by the second virtual machine, and the VNFM may deploy the first virtual machine or the second virtual machine on the server corresponding to the remaining virtual resource of the processor architecture. Compared with the prior art that the virtual machine can be deployed on the residual virtual resources of only one processor architecture, the method and the device for deploying the virtual machine can effectively improve the success rate and efficiency of deploying the virtual machine.

In one possible design, after the NFVO receives the virtual resource authorization request, the method further includes: the NFVO acquires a first virtual resource template according to an identifier of the first virtual resource template included in the virtual resource authorization request, acquires a second virtual resource template according to an identifier of the second virtual resource template included in the virtual resource authorization request, acquires a virtual resource requirement of the first virtual machine from the first virtual resource template, and acquires a virtual resource requirement of the second virtual machine from the second virtual resource template. Thus, the NFVO determines whether the remaining virtual resources of the first processor architecture satisfy the virtual resource requirements of the first virtual machine, and the NFVO determines whether the remaining virtual resources of the second processor architecture satisfy the virtual resource requirements of the second virtual machine.

In another possible design, when the remaining virtual resources of the first processor architecture satisfy the virtual resource requirements of the first virtual machine and the remaining virtual resources of the second processor architecture satisfy the virtual resource requirements of the second virtual machine, the method further includes: determining that a priority of the first processor architecture is higher than a priority of the second processor architecture, and sending the first virtual resource authorization response to the VNFM; or, determining that the priority of the first processor architecture is lower than the priority of the second processor architecture, and sending the second virtual resource authorization response to the VNFM. Therefore, the NFVO can flexibly select the remaining virtual resources from the remaining virtual resources of different processor architectures, and the remaining virtual resources meet the virtual resources required for deploying the virtual machine. Subsequently, the NFVO sends the first virtual resource authorization response or the second virtual resource authorization response to the VNFM to authorize the VNFM to deploy the virtual resource required by the first virtual machine or the virtual resource required by the second virtual machine, and the VNFM may deploy the first virtual machine or the second virtual machine on the server corresponding to the remaining virtual resource of the processor architecture. Compared with the prior art that the virtual machine can be deployed on the residual virtual resources of only one processor architecture, the method and the device for deploying the virtual machine can effectively improve the success rate and efficiency of deploying the virtual machine.

In another possible design, the virtual resource authorization request further includes an identification of the VDU so that the NFVO may determine that the first virtual resource template and the second virtual resource template are both associated with the VDU. The VDU may include general parameters. Such as: name (name), description (description), configurable properties (configurable _ properties), VDU profile (vddu _ profile), and the like. VNFD may also include input parameters and the like. Thus, the VNFM can be made to deploy the VDU on the first virtual machine or the second virtual machine.

In a second aspect, a method for deploying a virtual machine is provided, and the method is applicable to an application deployment server. In some embodiments, the application deployment server may be a VNFM device. The method comprises the following steps: after the VNFM receives the VNFD, a virtual resource authorization request is sent to the NFVO requesting authorization for deploying the virtual resources needed by the first virtual machine or the virtual resources needed by the second virtual machine. After the VNFM receives the first virtual resource authorization response, the VNFM deploys the first virtual machine on the first server according to the first virtual resource template indicated by the identifier of the first virtual resource template, the first virtual resource authorization response includes the identifier of the first virtual resource template and address information of the first server, and a processor architecture of the first server is the same as that of the first processor architecture; or after the VNFM receives a second virtual resource authorization response, the VNFM deploys a second virtual machine on the second server according to the second virtual resource template indicated by the identifier of the second virtual resource template, the second virtual resource authorization response includes the identifier of the second virtual resource template and address information of the second server, and a processor architecture of the second server is the same as a processor architecture of the second server.

The VNFD comprises a VDU, a first virtual resource template and a second virtual resource template. The first virtual resource template is used for describing virtual resources required for deploying the first virtual machine, and the first virtual resource template comprises an identifier of the first virtual resource template and an identifier of the first processor architecture. The second virtual resource template is used for describing virtual resources required for deploying the second virtual machine, and the second virtual resource template comprises an identifier of the second virtual resource template and an identifier of the second processor architecture. The first processor architecture is different from the second processor architecture. The virtual resource authorization request includes an identification of the first virtual resource template and an identification of the second virtual resource template.

In the method for deploying a virtual machine provided in the embodiment of the present application, the virtual resource authorization request sent by the VNFM to the NFVO is used to request authorization of virtual resources of different processor architectures, and the NFVO may flexibly select a remaining virtual resource from remaining virtual resources of different processor architectures, where the remaining virtual resource satisfies virtual resources required for deploying the virtual machine. Subsequently, the NFVO sends the first virtual resource authorization response or the second virtual resource authorization response to the VNFM to authorize the VNFM to deploy the virtual resource required by the first virtual machine or the virtual resource required by the second virtual machine, and the VNFM may deploy the first virtual machine or the second virtual machine on the server corresponding to the remaining virtual resource of the processor architecture. Compared with the prior art that the virtual machine can be deployed on the residual virtual resources of only one processor architecture, the method and the device for deploying the virtual machine can effectively improve the success rate and efficiency of deploying the virtual machine.

In one possible design, the first virtual resource template further includes a first instance number instruction, the first instance number instruction being used to indicate a number of deploying the first virtual machine, and the second virtual resource template further includes a second instance number instruction, the second instance number instruction being used to indicate a number of deploying the second virtual machine. The value of the number of the first virtual machines and/or the value of the number of the second virtual machines may be carried in the VNF instantiation request and notified to the VNFM. Therefore, after one virtual machine fails, other virtual machines can continue to provide support for the running of software, and the reliability of the virtual machines is improved.

In another possible design, the virtual resource authorization request further includes an identification of the virtual deployment unit VDU. The VDU includes a first deployment condition and a second deployment condition.

Wherein the first deployment condition indicates a corresponding relationship between the VDU and the first virtual resource template. Understandably, when the remaining resources of the server based on the first processor architecture satisfy the virtual resource requirement of the first virtual machine, the VNFM determines that a first deployment condition is satisfied, associates the VDU with the first virtual resource template using the first deployment condition, and deploys the first virtual machine on the first server according to the first virtual resource template indicated by the identifier of the first virtual resource template.

The second deployment condition indicates a correspondence of the VDU with the second virtual resource template. Understandably, when the remaining resources of the server based on the second processor architecture satisfy the virtual resource requirement of the second virtual machine, the VNFM determines that a second deployment condition is satisfied, associates the VDU with a second virtual resource template by using the second deployment condition, and deploys the second virtual machine on the second server according to the second virtual resource template indicated by the identifier of the second virtual resource template.

Thus, a VDU can be associated with a first virtual resource template by a first deployment condition and a VDU can be associated with a second virtual resource template by a second deployment condition.

In some embodiments, the VNFM deploys the first virtual machine on the first server according to the first virtual resource template indicated by the identification of the first virtual resource template, including: when the VNFM determines that a first deployment condition is met, the VNFM deploys a first virtual machine on a first server according to a first virtual resource template indicated by the identifier of the first virtual resource template, and the first deployment condition indicates the corresponding relation between the VDU and the first virtual resource template; or, the deploying, by the VNFM, the second virtual machine on the second server according to the second virtual resource template indicated by the identifier of the second virtual resource template, includes: and when the VNFM determines that the second deployment condition is met, the VNFM deploys a second virtual machine on the second server according to the second virtual resource template indicated by the identifier of the second virtual resource template, and the second deployment condition indicates the corresponding relationship between the VDU and the second virtual resource template.

In another possible design, the VDU also includes operational instructions. The operation instruction is used for indicating that a first virtual machine is deployed when the first deployment condition is met or a second virtual machine is deployed when the second deployment condition is met, wherein the first virtual machine is a virtual machine which is indicated by the first deployment condition and is associated with the first virtual resource template, and the second virtual machine is a virtual machine which is indicated by the second deployment condition and is associated with the second virtual resource template.

In another possible design, the first virtual resource template further includes a first deployment instruction, where the first deployment instruction is used to indicate that the first virtual machine is optionally deployed, and the second virtual resource template further includes a second deployment instruction, where the second deployment instruction is used to indicate that the second virtual machine is optionally deployed.

Thus, the VNFM may deploy the first virtual machine or the second virtual machine on servers corresponding to the remaining virtual resources of the processor architecture. Compared with the prior art that the virtual machine can be deployed on the residual virtual resources of only one processor architecture, the method and the device for deploying the virtual machine can effectively improve the success rate and efficiency of deploying the virtual machine.

In a third aspect, a method for deploying a virtual machine is provided, which is applicable to a network function virtualization orchestrator device. The method comprises the following steps: the NFVO receives the virtual resource authorization request and sends a virtual resource authorization response to the VNFM, wherein the virtual resource authorization response comprises an identifier of the first virtual resource template, an identifier of the second virtual resource template, address information of the first server and address information of the second server, a processor architecture of the first server is the same as that of the first processor, and a processor architecture of the second server is the same as that of the second processor.

The virtual resource authorization request is used for requesting to authorize the virtual resource required by the first virtual machine and the virtual resource required by the second virtual machine. In some embodiments, the virtual resource authorization request includes an identification of the first virtual resource template and an identification of the second virtual resource template. The first virtual resource template is used to describe virtual resources required to deploy the first virtual machine, and the first virtual resource template includes an identification of the first processor architecture. The second virtual resource template is used to describe virtual resources required for deploying the second virtual machine, and the second virtual resource template includes an identification of the second processor architecture. The first processor architecture is different from the second processor architecture.

In the method for deploying a virtual machine provided in the embodiment of the present application, the NFVO authorizes the remaining virtual resources of different processor architectures, and the remaining virtual resources all satisfy the virtual resources required for deploying the virtual machine. Subsequently, the NFVO sends a first virtual resource authorization response to the VNFM to authorize the VNFM to deploy the virtual resource required for the first virtual machine and the virtual resource required for deploying the second virtual machine, and the VNFM may deploy the first virtual machine and the second virtual machine on the server corresponding to the remaining virtual resource of the processor architecture. Compared with the prior art that the virtual machine can be deployed on the residual virtual resources of only one processor architecture, the method and the device for deploying the virtual machine can effectively improve the success rate and efficiency of deploying the virtual machine.

In one possible design, the virtual resource authorization request also includes an identification of the VDU so that the NFVO may determine that the first virtual resource template and the second virtual resource template are both associated with the VDU. The VDU may include general parameters. Such as: name, description, configurable attributes, VDU profile, etc. VNFD may also include input parameters and the like. Thus, the VNFM can be made to deploy the VDU on the first virtual machine or the second virtual machine.

In a fourth aspect, a method for deploying a virtual machine is provided, which is applicable to an application deployment server. In some embodiments, the application deployment server may be a VNFM device. The method comprises the following steps: the VNFM receives the VNFD, sends a virtual resource authorization request to the NFVO, and requests to authorize the virtual resources required by the first virtual machine and the virtual resources required by the second virtual machine. After the VNFM receives the virtual resource authorization response, the VNFM deploys a first virtual machine on the first server according to the first virtual resource template indicated by the identifier of the first virtual resource template; and the VNFM deploys a second virtual machine on the second server according to the second virtual resource template indicated by the identification of the second virtual resource template.

The VNFD comprises a VDU, a first virtual resource template and a second virtual resource template. The first virtual resource template is used for describing virtual resources required for deploying the first virtual machine, and the first virtual resource template comprises an identifier of the first virtual resource template and an identifier of the first processor architecture. The second virtual resource template is used for describing virtual resources required for deploying the second virtual machine, and the second virtual resource template comprises an identifier of the second virtual resource template and an identifier of the second processor architecture. The first processor architecture is different from the second processor architecture. The virtual resource authorization request includes an identification of the first virtual resource template and an identification of the second virtual resource template. The virtual resource authorization response comprises the identification of the first virtual resource template, the identification of the second virtual resource template, the address information of the first server and the address information of the second server, wherein the processor architecture of the first server is the same as that of the first processor, and the processor architecture of the second server is the same as that of the second processor.

In the method for deploying a virtual machine provided in the embodiment of the present application, a virtual resource authorization request sent by a VNFM to an NFVO is used to request authorization of virtual resources of different processor architectures, the NFVO authorizes different remaining virtual resources, and the remaining virtual resources all satisfy virtual resources required for deploying the virtual machine. Subsequently, the NFVO sends the first virtual resource authorization response or the second virtual resource authorization response to the VNFM to authorize the VNFM to deploy the virtual resource required by the first virtual machine or the virtual resource required by the second virtual machine, and the VNFM may deploy the first virtual machine or the second virtual machine on the server corresponding to the remaining virtual resource of the processor architecture. Compared with the prior art that the virtual machine can be deployed on the residual virtual resources of only one processor architecture, the method and the device for deploying the virtual machine can effectively improve the success rate and efficiency of deploying the virtual machine.

In one possible design, the VDU includes a node requirement parameter, the first virtual resource template further includes a node type, the second virtual resource template further includes a node type, and the method further includes: the VNFM determines that the value of the node type of the first virtual resource template and the value of the node type of the second virtual resource template are both node demand parameters in the VDU; the VNFM deploys VDUs on the first virtual machine and the second virtual machine. Thus, the VDU may be associated with the first and second virtual resource templates by the node type, and the VNFM deploys the VDU on the first and second virtual machines.

In another possible design, the first virtual resource template further includes a first instance number instruction, where the first instance number instruction is used to indicate the number of deployed first virtual machines, and the second virtual resource template further includes a second instance number instruction, where the second instance number instruction is used to indicate the number of deployed second virtual machines. The value of the number of the first virtual machines and/or the value of the number of the second virtual machines may be carried in the VNF instantiation request and notified to the VNFM. Therefore, after one virtual machine fails, other virtual machines can continue to provide support for the running of software, and the reliability of the virtual machines is improved.

In a fifth aspect, a communication device is provided for implementing the method described in the first or third aspect. The communication means may virtualize the orchestrator device for network functions. For example, an apparatus includes: the device comprises a receiving unit, a processing unit and a sending unit. The receiving unit is configured to receive a virtual resource authorization request, where the virtual resource authorization request is used to request to authorize a virtual resource required by deploying a first virtual machine or a virtual resource required by a second virtual machine, and the virtual resource authorization request includes an identifier of a first virtual resource template and an identifier of a second virtual resource template. The processing unit is configured to determine that the remaining virtual resources of the first processor architecture in the VIM meet the virtual resource requirement of the first virtual machine, and the sending unit is configured to send a first virtual resource authorization response to the VNFM, where the first virtual resource authorization response includes an identifier of the first virtual resource template and address information of the first server, and the processor architecture of the first server is the same as the first processor architecture; in further embodiments, the first virtual resource authorization response includes an identification of the first virtual resource template, an identification of the second virtual resource template, address information of the first server, and address information of the second server, the processor architecture of the first server is the same as the first processor architecture, and the processor architecture of the second server is the same as the second processor architecture; or, the processing unit is configured to determine that the remaining virtual resources of the second processor architecture in the VIM satisfy the virtual resource requirement of the second virtual machine, and the sending unit is configured to send a second virtual resource authorization response to the VNFM, where the second virtual resource authorization response includes an identifier of the second virtual resource template and address information of the second server, and the processor architecture of the second server is the same as the processor architecture of the second processor.

For a specific implementation of the method for deploying the virtual machine, reference may be made to the description of the first aspect or the third aspect, and details are not repeated.

In a sixth aspect, a communication device is provided for implementing the method described in the second or fourth aspect. The communication device is an application deployment server. For example, the communication apparatus includes: the device comprises a receiving unit, a sending unit and a processing unit. The receiving unit is configured to receive a VNFD, where the VNFD includes a meta VDU, a first virtual resource template, and a second virtual resource template, where the first virtual resource template is used to describe a virtual resource required for deploying a first virtual machine, the first virtual resource template includes an identifier of the first virtual resource template and an identifier of a first processor architecture, the second virtual resource template is used to describe a virtual resource required for deploying a second virtual machine, the second virtual resource template includes an identifier of the second virtual resource template and an identifier of a second processor architecture, and the first processor architecture is different from the second processor architecture; the sending unit is configured to send a virtual resource authorization request to the NFVO, where the virtual resource authorization request is used to request to authorize a virtual resource required by deploying a first virtual machine or a virtual resource required by a second virtual machine, and the virtual resource authorization request includes an identifier of a first virtual resource template and an identifier of a second virtual resource template; the receiving unit is further configured to receive a first virtual resource authorization response, where the first virtual resource authorization response includes an identifier of the first virtual resource template and address information of the first server, and a processor architecture of the first server is the same as the processor architecture of the first server; the processing unit is used for deploying a first virtual machine on the first server according to the first virtual resource template indicated by the identifier of the first virtual resource template; or, the receiving unit is further configured to receive a second virtual resource authorization response, where the second virtual resource authorization response includes an identifier of a second virtual resource template and address information of a second server, and a processor architecture of the second server is the same as that of the second processor; the processing unit is used for deploying a second virtual machine on a second server according to a second virtual resource template indicated by the identifier of the second virtual resource template; or the first virtual resource authorization response comprises the identification of the first virtual resource template, the identification of the second virtual resource template, the address information of the first server and the address information of the second server, wherein the processor architecture of the first server is the same as that of the first processor, and the processor architecture of the second server is the same as that of the second processor; the processing unit is used for deploying a first virtual machine on the first server according to the first virtual resource template indicated by the identifier of the first virtual resource template; the processing unit is further configured to deploy a second virtual machine on the second server according to the second virtual resource template indicated by the identifier of the second virtual resource template.

For a specific implementation manner of the method for deploying the virtual machine, reference may be made to the description of the second aspect or the fourth aspect, and details are not repeated.

The functional modules in the fifth aspect and the sixth aspect may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above. E.g. a transceiver for performing the functions of the receiving unit and the transmitting unit, a processor for performing the functions of the processing unit, a memory for the processor to process the program instructions of the methods of the present application. The processor, transceiver and memory are connected by a bus and communicate with each other. Specifically, reference may be made to the functions of the behaviors of the application deployment server or the NFVO device in the method of the first aspect to the method of the fourth aspect.

In a seventh aspect, the present application further provides a communication apparatus for implementing the method described in the first aspect or the third aspect. The communication device includes a system-on-chip. For example the communication device comprises a processor for implementing the functions in the methods described in the first or third aspect above. The communication device may also include a memory for storing program instructions and data. The memory is coupled to the processor, and the processor can call and execute the program instructions stored in the memory to implement the functions in the method described in the first aspect or the third aspect. The communication device may further comprise a communication interface for the communication device to communicate with other devices. Exemplarily, the communication device is an NFVO device.

In one possible arrangement, the communication interface may be a transceiver. A transceiver for transmitting a virtual resource authorization request and receiving a virtual resource authorization response. Reference may be made in detail to the above description of the various aspects, which is not repeated.

In an eighth aspect, the present application further provides a communication apparatus for implementing the method described in the second or fourth aspect. The communication device is an application deployment server. For example, the communication device comprises a processor for implementing the functions in the method described in the second or fourth aspect above. The communication device may also include a memory for storing program instructions and data. The memory is coupled to the processor, and the processor may call and execute the program instructions stored in the memory to implement the functions in the method described in the second or fourth aspect. The communication apparatus may further include a communication interface for the communication apparatus to communicate with other devices. Illustratively, if the communication device is an application deployment server, the other device is an NFVO device.

In one possible arrangement, the communication interface may be a transceiver. And the processor is used for deploying the first virtual machine on the first server according to the first virtual resource template indicated by the identifier of the first virtual resource template, or deploying the second virtual machine on the second server according to the second virtual resource template indicated by the identifier of the second virtual resource template.

In a ninth aspect, the present application further provides a computer-readable storage medium comprising: computer software instructions; the computer software instructions, when executed in the communication device, cause the communication device to perform the method of any one of the first to fourth aspects described above.

In a tenth aspect, the present application also provides a computer program product comprising instructions that, when run in a communication apparatus, cause the communication apparatus to perform the method of any of the first to fourth aspects described above.

In an eleventh aspect, the present application provides a chip system, where the chip system includes a processor and may further include a memory, and is configured to implement the function of the application deployment server or the NVFO device in the foregoing method. The chip system may be formed by a chip, and may also include a chip and other discrete devices.

In a twelfth aspect, the present application further provides a communication system, where the communication system includes the NFVO device described in the fifth aspect and the application deployment server described in the sixth aspect; or the communication system includes the NFVO device described in the seventh aspect and the application deployment server described in the eighth aspect.

In addition, the technical effects brought by the design manners of any aspect can be referred to the technical effects brought by different design manners in the first aspect and the fourth aspect, and are not described herein again.

In the technical solution of any of the above aspects, the VDU further includes link point information and a virtual network.

In the technical solution of any one of the above aspects, the VNFD is described using a TOSCA model language.

In the technical solution of any of the above aspects, the virtual resource authorization request carries an identifier of a VDU. The identification of the VDU is associated with the first virtual resource template and the first virtual resource template.

Drawings

Fig. 1 is a diagram illustrating an example of an NFV system architecture according to an embodiment of the present application;

FIG. 2A is a schematic diagram of a VNFD according to the present application;

fig. 2B is a schematic structural diagram of a VNF obtained after deployment according to the VNFD described above;

FIG. 3 is a flow chart of a method for deploying virtual machines provided herein;

FIG. 4A is a schematic diagram of another VNFD provided herein;

fig. 4B is a schematic structural diagram of a VNF obtained after deployment according to the VNFD described above;

FIG. 5 is a flow chart of another method for deploying virtual machines provided herein;

fig. 6 is a schematic diagram illustrating a communication apparatus according to the present application;

fig. 7 is a schematic diagram of another communication device provided in the present application.

Detailed Description

The terms "first," "second," and "third," etc. in the description and claims of this application and the above-described drawings are used for distinguishing between different objects and not for limiting a particular order.

In the embodiments of the present application, the words "exemplary" or "such as" are used herein to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

For clarity and conciseness of the following description of various embodiments, a brief introduction to the related art is first given:

conventional telecommunication systems are made up of various dedicated hardware devices, with different functions using different hardware devices. As the size of networks grows, telecommunication systems become more complex, presenting a number of challenges. For example, the development of the new service is online, and the operation and maintenance of the system and the resource utilization rate are used. In order to meet these challenges and utilize virtualization technology and cloud computing technology in the Internet Technology (IT) industry, 13 major telecommunications carriers worldwide jointly release a Network Function Virtualization (NFV) white paper, and announces that the European Telecommunications Standards Institute (ETSI) establishes an NFV Industry Specification Group (ISG), establishes requirements and a technical framework of NFV, and promotes the development of NFV.

The NFV technology utilizes virtualization technology to pool and virtualize resources of infrastructure hardware devices (e.g., computing devices, storage devices, network devices), provide virtual resources for upper layer applications, and implement software and hardware decoupling. When a new service is developed, hardware equipment does not need to be deployed independently, and the service is virtualized into an independent application (such as VNF) by adopting a virtualization technology, so that the online time of the new service is greatly shortened, and the virtual resource supply speed is greatly increased.

The NFV technology utilizes the cloud computing technology, can realize elastic expansion of application, realizes matching of virtual resources and service loads, improves utilization efficiency of the virtual resources, and improves response rate of an NFV system.

Fig. 1 is a diagram illustrating an NFV system architecture according to an embodiment of the present disclosure. The NFV system may be used in various networks, for example implemented in a data center network, operator network, or local area network. The NFV system includes an NFV management and orchestration system (NFV MANO) 101, an NFV infrastructure layer (NFVI) 102, a plurality of Virtual Network Functions (VNFs) 103, a plurality of Element Management (EM) 104, and an operation support system (operation-support system/business support system (OSS/BSS) 105.

Among other things, NFV MANO 101 is used to perform monitoring and management of NFVI 102 and VNF 103. The NFV management and orchestration system 101 includes an NFV orchestrator (NFV orchestrator, NFVO) 1011, one or more VNF managers (VNFM) 1012, and a Virtualized Infrastructure Manager (VIM) 1013.

NFVO 1011 is mainly responsible for handling lifecycle management of virtualization services, allocation and scheduling of virtual resources in the virtual infrastructure and NFVI, etc. NFVO 1011 may also perform resource-related requests (e.g., requests to obtain VNFDs) from one or more VNFMs 1012, send configuration information (e.g., VNFDs, VNF modification information requests, and VNF instantiation requests) to VNFM 1012, and collect status information of VNF 103. The VNFD may be stored on the NFVO, or may be stored in a database managed by the NFVO, so that the NFVO may obtain the VNFD and feed back the VNFD to the VNFM, and the VNFM deploys the VNF according to the VNFD. The NFVO may store VNFDs corresponding to VNFs of multiple functions. Additionally, NFVO 1011 may communicate with VIM 1013 to enable allocation and/or reservation of resources and to exchange configuration and status information for virtualized hardware resources.

VNFM 1012 is primarily responsible for lifecycle management of one or more VNFs 103. Such as instantiating (updating), updating (updating), querying, scaling (scaling), terminating (terminating) VNF 103, etc. VNFM 1012 may communicate with VNF 103 to complete VNF 103 lifecycle management and exchange configuration and status information. There may be multiple VNFMs 1012 in the NFV system, which are responsible for lifecycle management for different types of VNFs.

The VIM 1013 may perform functions for resource management, such as managing allocation of infrastructure resources (e.g., adding resources to virtual containers) and operational functions (e.g., collecting NFVI fault information). VNFM 1012 and VIM 1013 may communicate with each other for resource allocation and exchange configuration and status information for virtualized hardware resources. For example, VNF 103 interacts with computing hardware 1021, storage hardware 1022, networking hardware 1023, virtual computing (virtual computing) 1024, virtual storage 1025, and virtual network 1026.

NFVI 102 includes a hardware resource layer, a virtualization layer (virtualization layer), and a virtual resource layer. NFVI 102 includes hardware resources, software resources, or a combination of both to complete the deployment of the virtualized environment. In other words, the hardware resources and virtualization layer are used to provide virtualized resources, e.g., as virtual machines and other forms of virtual containers, for VNF 103. The hardware resource layer includes computing hardware 1021, storage hardware 1022, and networking hardware 1023. The computing hardware 1021 may be commercially available hardware and/or custom hardware to provide processing and computing resources. The storage hardware 1022 may be storage capacity provided within a network or storage capacity resident on the storage hardware 1022 itself (local storage located within a server). In one implementation, the resources of computing hardware 1021 and storage hardware 1022 may be pooled together. Network hardware 1023 may be a switch, router, and/or any other network device configured with switching functionality. Network hardware 1023 may span multiple domains and may include multiple networks interconnected by one or more transport networks. A virtualization layer inside NFVI 102 may abstract hardware resources from the physical layer and decouple VNF 103 in order to provide virtualized resources to VNF 103. Virtual resource layers include virtual compute 1024, virtual storage 1025, and virtual network 1026. Virtual compute 1024 and virtual storage 1025 may be provided to VNF 103 in the form of virtual machines, and/or other virtual containers. For example, one or more VNFs 103 may be deployed on one Virtual Machine (VM). Virtualization layer abstracts the network hardware 1023 to form a virtual network 1026, which may include a virtual switch (virtual switch) to provide connectivity between the virtual machine and other virtual machines. In addition, the transport network in the network hardware 1023 can be virtualized using a centralized control plane and a separate forwarding plane (e.g., a software defined network).

In hardware, the computing hardware 1021, storage hardware 1022, and networking hardware 1023 may comprise multiple subracks, or multiple racks, or even multiple rooms. There may be one VIM 1013 or multiple VIMs in software, each managing different hardware resources.

VNF 103 is a virtualized network function instance.

The device management system (EM) 104 is a system for configuring and managing devices in a conventional network, and in the NFV system, the EM 104 may also be used to configure and manage the VNF 103, and initiate lifecycle management operations such as instantiation of a new VNF 103 to the VNFM 1012.

An operation Support System (Operations Support System and Business Support System, OSS/BSS) 105 supports various end-to-end telecommunication services. The management functions supported by OSS include: network configuration, service provisioning, fault management, etc. The BSS processes orders, pays, revenues, etc., supporting product management, order management, revenue management, and customer management.

In the NFV system, the virtualized Network Service (NS) may be an IP Multimedia Subsystem (IMS) Network Service, or an Evolved Packet Core (EPC) Network Service. Several VNFs may be included in one NS. When performing virtualization deployment on an NS, a virtualization Service provider needs to obtain description information of the Service, i.e., a Network Service template (NSD), from a virtualization Service requester. The NSD mainly describes topology information of the service and description information of each VNF included, i.e., VNFD. In the topology information, a Virtual Link Descriptor (VLD) may be used to describe the connection between VNFs. The virtualized service requestor may be an NFVO or sender (sender). The sender may specifically be an OSS/BSS.

Fig. 2A is a schematic structural diagram of a VNFD provided in the present application. Fig. 2B is a schematic structural diagram of a VNF obtained after deployment according to the VNFD described above.

As shown in fig. 2A, the VNFD includes information such as a Virtual Deployment Unit (VDU) 1, a VDU2, a Connection Point (CP) _ a, a CP _ B, and a Virtual Link (VL). The VDU represents application software that needs to be deployed onto a virtual machine. The CP represents connection information of the VNF, such as virtual network card information, which may be represented by an IP address or a MAC address. VL is a virtual connection connecting multiple VDUs within the VNF, and may be represented by information such as connection type and bandwidth.

As shown in fig. 2B, the VNFM is deployed by using the VNFD, and the VNF obtained after the deployment includes a Virtualized Network Function Component (VNFC) 1, a VNFC2, a CP _ a instance, a CP _ B instance, and a VL instance. The VDU1 in the VNFD generates the VNFC1 after deployment, and the VDU2 in the VNFD generates the VNFC2 after deployment.

It should be noted that the functions implemented by different VNFs are different. For a VNF with simple function, it may be described by using one VDU, and the deployed VNF includes one VNFC. For a VNF with complex functions, more than two VDU descriptions may be used, and the deployed VNF includes more than two VNFCs. Thus, multiple VDUs may be included in one VNFD.

In the present application, the VNFD may be described using Topology and Organizational Specification for Cloud Applications (TOSCA). TOSCA is a description specification set by the Open Standards Organization (OASIS).

In some embodiments, the information needed to deploy an application may be described in an application deployment package. The application deployment package at least comprises an application deployment description file with a suffix of YAML, wherein the application deployment description file of YAML can describe deployment information of the application by using YAML language, and a root element of the application deployment description file of YAML is an application Template (Service Template). That is to say, in the embodiment of the present application, the information of the application to be deployed may be completely described by using the application template. * Sub-elements of the application deployment description file of yaml include topology template (TopologyTemplate), node type (NodeType), node template (NodeTemplate), relationship type (relationship), relationship template (relationship definitions), boundary definitions (boundarydydefinitions), and the like.

As an example, an example of a VNFD defined by conventional techniques is as follows:

the VNFD defines a deployment template of vCPE services. The VDU _1 comprises a description of virtual resources required for deploying the virtual machine. Such as: the processor architecture is x86, the number of processors is 2, the processor frequency is 1800MHz, and the memory is 8192M. The deployed software image is described in the artifact in VDU _1, i.e. in the maria.db.image.v2.0.qcow2 file.

Currently, servers mainly include servers based on an x86 processor architecture and servers based on an Advanced reduced instruction set processor (ARM) processor architecture. Servers of different processor architectures differ in performance. The performance of the servers with different processor architectures also varies for the same application software, so that it is generally necessary for software developers to develop different software versions for servers based on the x86 processor architecture or servers based on the ARM processor architecture. The same is true for virtual machines, and the deployed virtual machines are installed on servers of an x86 processor architecture and servers of an ARM processor architecture to perform different performances for the same VDU in the VNFD. Therefore, there is a need to specify the processor architecture of the virtual machine in the VDU.

Typically, the hardware resources of the x86 processor architecture based servers and the hardware resources of the ARM processor architecture based servers are managed by a data center (e.g., VIM). However, the servers of the two processor architectures are not always available for allocation of idle resources, so that when one virtual machine is deployed, a certain VDU in the VNFD is required to be deployed on the server based on the x86 processor architecture, and when the servers based on the x86 processor architecture in the data center are all busy at this time, no idle resources may be allocated to the VDU deployment, which results in failure in deploying the virtual machine, or it is necessary to wait for a long time until there are available idle resources to provide a redeployed virtual machine. Alternatively, a server based on the ARM processor architecture may be used in the data center, and the virtual machine may be deployed on the server based on the ARM processor architecture, but may affect the performance of the VNF.

The embodiment of the application provides a method for deploying a virtual machine, which comprises the following steps: in the VNFD, at least two virtual resource templates are set, each virtual resource template being used to describe a virtual resource required for deploying a virtual machine, where processor architectures of the at least two virtual machines are different. The NFVO may select between servers corresponding to at least two processor architectures, when there is a remaining virtual resource of a server of one processor architecture that satisfies a virtual resource required for deploying a virtual machine of the corresponding processor architecture, the remaining virtual resource of the server of the processor architecture is authorized, and the VNFM deploys the virtual machine on the server according to a virtual resource template indicated by an identifier of the virtual resource template, where the processor architecture of the server is the same as the processor architecture of the deployed virtual machine.

In the method for deploying a virtual machine provided in the embodiment of the present application, a virtual resource authorization request sent by a VNFM to an NFVO is used to request virtual resource authorization for different processor architectures, and the NFVO can flexibly select a remaining virtual resource from remaining virtual resources of different processor architectures, where the remaining virtual resource satisfies virtual resources required for deploying the virtual machine. Subsequently, the NFVO sends the first virtual resource authorization response or the second virtual resource authorization response to the VNFM to authorize the VNFM to deploy the virtual resource required by the first virtual machine or the virtual resource required by the second virtual machine, and the VNFM may deploy the first virtual machine or the second virtual machine on the server corresponding to the remaining virtual resource of the processor architecture. Compared with the prior art that the virtual machine can be deployed on the residual virtual resources of only one processor architecture, the method and the device for deploying the virtual machine can effectively improve the success rate and efficiency of deploying the virtual machine.

In the present application, the virtualized service requestor may be an NFVO or sender (sender). The sender may specifically be an OSS/BSS. The virtualized service provider may be an application deployment server. For example, the virtualized service provider may be a VNFM.

The following describes in detail an implementation of the embodiment of the present application with reference to the accompanying drawings, taking a virtualization service requester as NFVO and a virtualization service provider as VNFM as examples.

Fig. 3 is a flowchart of a method for deploying a virtual machine according to an embodiment of the present application. As shown in fig. 3, the method may include:

s301, obtaining the VNFD by the VNFM.

The VNFM can receive the VNFD sent by the NFVO, parse the VNFD, and obtain the content of the VNFD. In some embodiments, the VDU and at least two virtual resource templates associated with the VDU are included in the VNFD. For example, a first virtual resource template and a second virtual resource template.

The first virtual resource template is used for describing virtual resources required by deployment of the first virtual machine. For example, the first virtual resource template includes an identification of the first virtual resource template, an identification of the first processor architecture, a number of first processors, a frequency of the first processors, a number of memories, and first software image information. In some embodiments, the identification of the first virtual resource template may be an identification of the first virtual machine. The first software image information may include location information of a software image required for VNF deployment.

The second virtual resource template is used for describing virtual resources required for deploying the second virtual machine. For example, the second virtual resource template includes an identification of the second virtual resource template, an identification of the second processor architecture, a number of the second processors, a frequency of the second processors, a number of memories, and second software image information.

In an embodiment of the present application, the first processor architecture is different from the second processor architecture. For example, the first processor architecture may be referred to as an x86 processor architecture and the second processor architecture may be referred to as an ARM processor architecture. Alternatively, the first processor architecture may be referred to as an ARM processor architecture and the second processor architecture may be referred to as an x86 processor architecture.

The VDU includes a first deployment condition and a second deployment condition.

The first deployment condition indicates a correspondence of the VDU with the first virtual resource template. Understandably, when the remaining resources of the server based on the first processor architecture satisfy the virtual resource requirement of the first virtual machine, the VNFM determines that a first deployment condition is satisfied, associates the VDU with the first virtual resource template by using the first deployment condition, and deploys the first virtual machine on the first server according to the first virtual resource template indicated by the identifier of the first virtual resource template.

The second deployment condition indicates a correspondence of the VDU with the second virtual resource template. Understandably, when the remaining resources of the server based on the second processor architecture satisfy the virtual resource requirement of the second virtual machine, the VNFM determines that a second deployment condition is satisfied, associates the VDU with the second virtual resource template by using the second deployment condition, and deploys the second virtual machine on the second server according to the second virtual resource template indicated by the identifier of the second virtual resource template.

It should be noted that the VDU may also include general parameters. Such as: name (name), description (description), configurable properties (configurable _ properties), VDU profile (vddu _ profile), and the like. VNFD may also include input parameters and the like.

In some embodiments, after the VNFM receives the VNF instantiation request sent by the NFVO, the VNFM may send a VNFD acquisition request to the NFVO, the VNFD acquisition request including an identification of the VNFD. The identity of VNFD is used to indicate VNFD. The identity of VNFD may be that VNFM is informed by NFVO in advance. After receiving the VNFD acquisition request, the NFVO acquires the VNFD according to the VNFD identifier, and sends a VNFD response to the VNFM, where the VNFD response includes the VNFD. After obtaining the VNFD, the VNFM sends a receive response to the NFVO to inform the NFVO that the VNFD has been successfully received.

S302, the VNFM sends a virtual resource authorization request to the NFVO.

And after the VNFM receives the VNFD sent by the NFVO and analyzes the VNFD, the identifier of the first virtual resource template and the identifier of the second virtual resource template are sent to the NFVO, and the authorization of the virtual resources required for deploying the first virtual machine or the authorization of the virtual resources required for deploying the second virtual machine is requested.

Wherein the virtual resource authorization request includes an identification of the first virtual resource template and an identification of the second virtual resource template.

In some embodiments, the virtual resource authorization request further includes an identification of the VDU, such that the NFVO may determine that the first virtual resource template and the second virtual resource template are both associated with the VDU, and the NFVO may select one of the virtual resource templates.

By way of example, an example of a procedure for a virtual resource authorization request is shown below:

as can be seen from this example, the identity of the VDU and the identity of the first virtual resource template can be the content of the first resource definition. The identity of the VDU and the identity of the second virtual resource template can be the content of the second resource definition. The first virtual resource template and the second virtual resource template are both nodes associated with VDU1, and NFVO may select one virtual resource template from them.

In other embodiments, the virtual resource authorization request need not contain the identity of VDU 1. At this point, the implication is that VM _1 and VM _2 are either alternatives.

S303, the NFVO receives the virtual resource authorization request sent by the VNFM.

And after receiving the virtual resource authorization request, the NFVO analyzes the virtual resource authorization request to obtain the identifier of the first virtual resource template and the identifier of the second virtual resource template. The NFVO can acquire a first virtual resource template according to the identifier of the first virtual resource template, wherein the first virtual resource template comprises the identifier of a first processor architecture, the number of first processors, the frequency of the first processors, the number of memories and first software mirror image information; and the NFVO acquires a second virtual resource template according to the identifier of the second virtual resource template, wherein the second virtual resource template comprises the identifier of the second processor architecture, the number of the second processors, the frequency of the second processors, the number of the memories and second software mirror image information. The NFVO may determine that virtual resources of the first processor architecture or virtual resources of the second processor architecture need to be used. In some embodiments, the NFVO may obtain, from the data center, remaining virtual resource information for the first processor architecture based server and remaining virtual resource information for the second processor architecture based server. Herein, a data center may refer to a VIM. The NFVO may obtain the first virtual resource template and the second virtual resource template locally.

After the NFVO acquires the information of the remaining virtual resources of the first processor architecture, determining whether the remaining virtual resources of the first processor architecture meet the virtual resource requirement of the first virtual machine, and determining whether the remaining virtual resources of the second processor architecture meet the virtual resource requirement of the second virtual machine.

It should be noted that "whether the remaining virtual resources of the first processor architecture satisfy the virtual resource requirement of the first virtual machine" may also be alternatively described as "whether the remaining virtual resources of the server based on the first processor architecture satisfy the virtual resource requirement of the first virtual machine". Whether the remaining virtual resources of the second processor architecture satisfy the virtual resource requirements of the second virtual machine may alternatively be described as whether the remaining virtual resources of the server based on the second processor architecture satisfy the virtual resource requirements of the second virtual machine.

When the remaining virtual resources of the first processor architecture satisfy the virtual resource requirement of the first virtual machine and the remaining virtual resources of the second processor architecture do not satisfy the virtual resource requirement of the second virtual machine, S304a to S306a are executed.

And executing S304 b-S306 b when the remaining virtual resources of the first processor architecture do not satisfy the virtual resource requirement of the first virtual machine and the remaining virtual resources of the second processor architecture satisfy the virtual resource requirement of the second virtual machine.

In other embodiments, when the remaining virtual resources of the first processor architecture satisfy the virtual resource requirements of the first virtual machine and the remaining virtual resources of the second processor architecture also satisfy the virtual resource requirements of the second virtual machine, the NFVO may freely select the remaining virtual resources of one of the architectures to deploy the corresponding virtual machine.

In other embodiments, the virtual resources may be authorized according to the priorities of the processor architectures when the remaining virtual resources of the first processor architecture satisfy the virtual resource requirements of the first virtual machine and the remaining virtual resources of the second processor architecture satisfy the virtual resource requirements of the second virtual machine. When the NFVO determines that the priority of the first processor architecture is higher than the priority of the second processor architecture, S304a to S306a are performed. When the NFVO determines that the priority of the first processor architecture is lower than the priority of the second processor architecture, S304 b-S306 b are performed.

In the embodiment of the present application, the priority of the first processor architecture is higher than that of the second processor architecture.

In some embodiments, the virtual resource authorization request further includes an identification of the VDU. The NFVO may determine to select one virtual resource template from the two virtual resource templates according to the identifier of the VDU, and authorize the resource corresponding to the virtual resource template.

It should be noted that, when the remaining virtual resources of the first processor architecture do not satisfy the virtual resource requirement of the first virtual machine and the remaining virtual resources of the second processor architecture do not satisfy the virtual resource requirement of the second virtual machine, the NFVO sends a virtual resource authorization failure response to the VNFM, and at this time, it indicates that the VNFM fails to deploy the virtual machine.

S304a, the NFVO sends a first virtual resource authorization response to the VNFM.

In some embodiments, the first virtual resource authorization response includes an identification of the first virtual resource template and address information of the first server. Wherein, the NFVO may obtain address information of a first server in the data center. The first virtual resource authorization response may also include an identification of the VDU. The VNFM can know from the content contained in the first virtual resource authorization response, which is feedback to the VDU, that the virtual resource required by the first virtual machine is authorized. The VNFM can deploy the first virtual machine on remaining virtual resources of the first server having a processor architecture that is the same as the first processor architecture.

By way of example, an example of a procedure for a first virtual resource authorization response is shown below:

response:

addResource:

identification of resource definition _1# first resource definition

vim connectionid: address information of # 10.12.13.00 first server

As can be seen from this example, the first virtual resource authorization response includes an identification of the first resource definition and address information of the first server. The first resource definition includes an identification of the VDU and an identification of the first virtual resource template.

S305a, the VNFM receives the first virtual resource authorization response sent by the NFVO.

S306a, the VNFM deploys the first virtual machine on the first server according to the first virtual resource template indicated by the identifier of the first virtual resource template.

In some embodiments, the VNFM can determine that the first virtual resource authorization response is feedback for the VDU based on the identification of the VDU and determine that the virtual resource corresponding to the first virtual resource template is authorized based on the identification of the first virtual resource template. For example, the first deployment condition is that the architecture of the processor is a first processor architecture. Since the first deployment condition indicates a corresponding relationship between the VDU and the first virtual resource template, the VNFM deploys the first virtual machine on the first server according to the first virtual resource template indicated by the identifier of the first virtual resource template.

The VNFM sends a virtual resource application request to the data center, where the virtual resource application request includes address information of the first server, the data center authorizes resources of the first server, and the VNFM may deploy the first virtual machine on the first server according to virtual resources described by the first virtual resource template. Subsequently, the VNFM may also deploy the general parameters, the software image, and the like of the VDU on the first virtual machine, and the specific deployment process may refer to related explanations in the prior art and is not described in detail.

S304b, the NFVO sends a second virtual resource authorization response to the VNFM.

In some embodiments, the second virtual resource authorization response includes an identification of the second virtual resource template and address information of the second server. Wherein the NFVO may obtain address information of a second server in the data center. The second virtual resource authorization response can also include an identification of the VDU. The VNFM can know from the content contained in the second virtual resource authorization response, which is feedback to the VDU, that the virtual resource required by the second virtual machine is authorized. The NFVO may deploy the second virtual machine on the remaining virtual resources of the second server, the processor architecture of the second server being the same as the second processor architecture.

As an example, an example of a procedure for the second virtual resource grant response is shown below:

response:

addResource:

identification of resource definition _2# second resource definition

vim connection id: address information of 10.11.12.00# second server

As can be seen from this example, the second virtual resource authorization response includes an identification of the second resource definition and address information of the second server. The second resource definition includes an identification of the VDU and an identification of the second virtual resource template.

S305b, the VNFM receives the second virtual resource authorization response sent by the NFVO.

And S306b, the VNFM deploys a second virtual machine on the second server according to the second virtual resource template indicated by the identifier of the second virtual resource template.

In some embodiments, the VNFM can determine that the second virtual resource authorization response is feedback for the VDU based on the identity of the VDU and determine that the virtual resource corresponding to the second virtual resource template is authorized based on the identity of the second virtual resource template. For example, the second deployment condition is that the architecture of the processor is a second processor architecture. Since the second deployment condition indicates a corresponding relationship between the VDU and the second virtual resource template, the VNFM deploys the second virtual machine on the second server according to the second virtual resource template indicated by the identifier of the second virtual resource template. Specifically, the VNFM sends a virtual resource application request to the data center, where the virtual resource application request includes address information of the second server, the data center authorizes resources of the second server, and the VNFM may deploy the second virtual machine on the second server according to the virtual resources described by the second virtual resource template. Subsequently, the VNFM may also deploy general parameters, software images, and the like of the VDU on the second virtual machine, which may specifically refer to related explanations of the prior art and will not be described in detail.

In some embodiments, the VDU further includes an operation instruction, where the operation instruction is configured to instruct to deploy a first virtual machine when the first deployment condition is satisfied or to deploy a second virtual machine when the second deployment condition is satisfied, where the first virtual machine is a virtual machine that is indicated by the first deployment condition and is associated with the first virtual resource template, and the second virtual machine is a virtual machine that is indicated by the second deployment condition and is associated with the second virtual resource template.

In the case that the VNFM receives a first virtual resource authorization response sent by the NFVO, the first virtual resource authorization response includes an identifier of the first virtual resource template, which indicates that the NFVO authorizes a virtual resource described in the first virtual resource template and required for deploying the first virtual machine, and the VNFM may deploy the first virtual machine on the first server according to the first virtual resource template indicated by the identifier of the first virtual resource template, where at this time, the operation instruction is used to indicate that the first virtual machine is deployed when the first deployment condition is satisfied.

In the case that the VNFM receives a second virtual resource authorization response sent by the NFVO, the second virtual resource authorization response includes an identifier of the second virtual resource template, which indicates that the NFVO authorizes the virtual resource described by the second virtual resource template, where the virtual resource is required for deploying the second virtual machine, and the VNFM may deploy the second virtual machine on the second server according to the second virtual resource template indicated by the identifier of the second virtual resource template, where at this time, the operation instruction is used to indicate that the second virtual machine is deployed when the second deployment condition is satisfied.

In some embodiments, the first virtual resource template further includes a first deployment instruction indicating that the first virtual machine is optionally deployed. The second virtual resource template further comprises a second deployment instruction, wherein the second deployment instruction is used for indicating that the second virtual machine is optionally deployed. When the VNFM deploys the first virtual machine, the second virtual machine may not need to be deployed. When the VNFM deploys the second virtual machine, the first virtual machine may not need to be deployed.

In some embodiments, the first virtual resource template further includes a first instance count instruction, the first instance count instruction to indicate a number of deployments of the first virtual machine. The second virtual resource template further includes a second instance count instruction for indicating a number of deploying second virtual machines.

When the first virtual machine is deployed, the VNFM can deploy a plurality of first virtual machines according to the first instance number instruction, thereby improving reliability of the first virtual machine. The NFVO may notify the VNFM of a value of the number of the first virtual machines through the VNF instantiation request.

When the second virtual machine is deployed, the VNFM may deploy a plurality of second virtual machines according to the second instance number instruction, thereby improving reliability of the second virtual machine. The NFVO may notify the VNFM of a value of the number of second virtual machines through the VNF instantiation request.

In the method for deploying a virtual machine provided in the embodiment of the present application, the virtual resource description of the virtual machine included in the VDU is separated into separate descriptions, that is, two different virtual resource templates of a processor architecture are formulated in the VNFD. The VNFM sends a virtual resource authorization request to the NFVO to request virtual resource authorization of different processor architectures, and the NFVO can flexibly select a remaining virtual resource from the remaining virtual resources of the different processor architectures, and the remaining virtual resource satisfies a virtual resource required for deploying the virtual machine. Subsequently, the NFVO sends the first virtual resource authorization response or the second virtual resource authorization response to the VNFM to authorize the VNFM to deploy the virtual resource required by the first virtual machine or the virtual resource required by the second virtual machine, and the VNFM may deploy the first virtual machine or the second virtual machine on the server corresponding to the remaining virtual resource of the processor architecture. Compared with the prior art that the virtual machine can be deployed on the residual virtual resources of only one processor architecture, the method and the device for deploying the virtual machine can effectively improve the success rate and efficiency of deploying the virtual machine.

By way of example, an example of a topology template in a VNFD defined by an embodiment of the present application:

as can be seen from the above example, the description of the virtual resources of the VDU1 node is separated out to be used as the separate description of the new virtual machine node (e.g., VM _1 and VM _ 2). Where VM _1 describes the requirements of virtual resources based on the x86 processor architecture, and the corresponding software images. VM _2 describes the requirements of virtual resources based on the ARM processor architecture, and the corresponding software image. The VDU1 node describes in this example the information of the general parameters of the virtual deployment unit. Such as: name, minimum number of instantiations, maximum number of instantiations, etc. Requirements (requirements) are also employed in the VDU1 to describe the requirements for virtual resources. The syntax structure of requirement is the syntax supported by the existing TOSCA. The requirement description is as follows:

requirements:

-host:

node:tosca.node.nfv.virtualComputeDesc

node_filter:

wherein, the node is used to describe that the VDU1 needs to be deployed on a node with type (type) of tosca. The node _ filter is used to describe the specific requirements for virtual resources. The node _ filter description is as follows:

wherein, condition and or are used to describe the optional requirement, and the following two-and respectively represent different requirement information. For example, the first-and corresponding requirement is "cpu _ architecture: [ equivalent: x86]", which indicates that VDU1 has a corresponding relationship with a virtual resource template with a processor architecture of x86, i.e., VDU1 has a corresponding relationship with VM _1. When the remaining resources of the server based on the x86 processor architecture satisfy the virtual resources required to deploy VM _1, VM _1 is deployed according to the requirements indicated by the first-and.

The second-and corresponds to the requirement "cpu _ architecture: [ equal: ARM ]", which indicates that the VDU1 and the virtual resource template with the processor architecture of ARM have a corresponding relationship, i.e. the VDU1 and VM _2 have a corresponding relationship. When the remaining resources of the server based on the ARM processor architecture satisfy the virtual resources required to deploy VM _2, VM _2 is deployed according to the requirements indicated by the second-and.

Additionally, action is used to describe a specific action, i.e., an action when either the first-and or the second-and is satisfied. In this example, the action is to perform a deployment operation, i.e., deploy a VM _1 node or a VM _2 node.

In the VM _1 node and the VM _2 node, a directive value is also set, and the directive value is optional _ deployment, which is used for indicating that the node is optionally deployed and can be deployed only when the condition is met. In this example, only the VM node selected in the condition of VDU1 will be deployed.

In other embodiments, the VDU may not include the first deployment condition and the second deployment condition. For example, the node _ filter description may not be included in the requirement description. The first virtual resource template includes first deployment instructions for indicating that the first virtual machine is optionally deployed. The second virtual resource template includes second deployment instructions for indicating that the second virtual machine is optionally deployed. The VNFM may determine which virtual resource template to select to deploy the virtual machine according to the identifier of the virtual resource template included in the received virtual resource authorization response. For example, if the VNFM receives a first virtual resource authorization response, the first virtual resource authorization response includes an identifier of the first virtual resource template, and the VNFM deploys the first virtual machine according to the first virtual resource template. If the VNFM receives a second virtual resource authorization response, the second virtual resource authorization response includes an identifier of the second virtual resource template, and the VNFM deploys the second virtual machine according to the second virtual resource template. Other related explanations can refer to the explanations of the above embodiments, and are not repeated.

In the above embodiments, two virtual resource templates are taken as an example for illustration, in some embodiments, at least two or more (for example, three or more) virtual resource templates may be set, where processor architectures in the at least two virtual resource templates are different, and meanwhile, a deployment condition is set for each virtual machine in the VDU, so that a success rate of deploying the virtual machine is further improved.

In some embodiments, multiple VDU descriptions are required because the VNF implementation is complex. Therefore, a plurality of VDUs may be included in a VNFD, one VDU is used to describe a partial function of a VNF, and the plurality of VDUs included in the VNFD collectively implement a VNF. The virtual resource description included in each VDU can be separated, at least two virtual resource templates are set, the virtual machines are deployed according to the method for deploying the virtual machines, and each VDU is associated with the corresponding virtual resource template. Reference may be made to the description of the above embodiments, which are not repeated herein.

Fig. 4A is a schematic structural diagram of another VNFD provided in the present application. Fig. 4B is a schematic structural diagram of a VNF obtained after deployment according to the VNFD described above.

As shown in fig. 4A, the VNFD includes VDU1, VDU2, CP _ a, CP _ B, VL, a virtual resource template with x86_ a processor architecture, a virtual resource template with ARM _ a processor architecture, a virtual resource template with x86_ B processor architecture, and a virtual resource template with ARM _ B processor architecture. VDU1 is associated with a virtual resource template for the x86_ A virtual machine and a virtual resource template for the ARM _ A virtual machine. VDU2 is associated with a virtual resource template for the x86_ B virtual machine and a virtual resource template for the ARM _ B virtual machine.

As shown in fig. 4B, the VNFM is deployed using the VNFD, and the VNF obtained after deployment includes VNFC1, VNFC2, CP _ a instance, CP _ B instance, and VL instance. After being deployed, the VDU1 in the VNFD generates VNFC1, and VNFC1 is deployed on a virtual machine with a processor architecture of x86_ a. After being deployed, the VDU2 in the VNFD generates VNFC2, and the VNFC2 is deployed on a virtual machine with a processor architecture of ARM _ B.

In some embodiments, when the virtualized service provider knows the resource usage of the servers in the data center, it may be specified to deploy virtual machines on the servers of two different processor architectures, respectively, so as to implement the VDU deployment on the servers of two different processor architectures, reduce the load of a single server, and implement load sharing. In addition, the number of the deployed virtual machines can be specified through the VNF instantiation request, so that the reliability of the virtual machines is improved.

Fig. 5 is a flowchart of a method for deploying a virtual machine according to an embodiment of the present application, where as shown in fig. 5, the method may include:

s501, obtaining the VNFD by the VNFM.

The VNFM can receive the VNFD sent by the NFVO, parse the VNFD, and obtain the content of the VNFD. In some embodiments, the VNFD comprises a first virtual resource template and a second virtual resource template. Wherein, the VDU further comprises a node requirement parameter. The first virtual resource template includes a node type and the second virtual resource template includes a node type. When the VNFM determines that the value of the node type of the first virtual resource template and the value of the node type of the second virtual resource template are both node demand parameters in the VDU, the VNFM deploys the VDU on the first virtual machine and the second virtual machine.

For other explanations of the first virtual resource template, the second virtual resource template and the VDU, reference may be made to the description of S301, and details are not repeated.

S502, the VNFM sends a virtual resource authorization request to the NFVO.

S503, the NFVO receives the virtual resource authorization request sent by the VNFM.

In some embodiments, after receiving the virtual resource authorization request sent by the VNFM, the NFVO may obtain the virtual resource requirement of the first virtual machine and the virtual resource requirement of the second virtual machine according to an identifier of the first virtual resource template and an identifier of the second virtual resource template included in the virtual resource authorization request.

In this embodiment, the NFVO may obtain a corresponding first virtual resource template according to an identifier of the first virtual resource template, obtain a corresponding second virtual resource template according to an identifier of the second virtual resource template, and then obtain a virtual resource requirement of the first virtual machine and a virtual resource requirement of the second virtual machine from the first virtual resource template and the second virtual resource template, respectively. Virtual resource requirements may also be referred to as virtual hardware requirements or resource requirements. The virtual resource requirements include memory requirements and processor requirements.

For example, the virtual resource requirements of the first virtual machine are:

the virtual resource requirements of the second virtual machine are as follows:

the first virtual resource template and the second virtual resource template acquired locally by the NFVO are consistent with the first virtual resource template and the second virtual resource template in the VDU received by the VNFM, so that the virtual resource demand of the first virtual machine and the virtual resource demand of the second virtual machine and the resource requested by the VNFM acquired by the NFVO are also consistent.

Subsequently, the NFVO obtains, from the data center, remaining virtual resource information of the server based on the first processor architecture and remaining virtual resource information of the server based on the second processor architecture. The data center may be referred to as a VIM.

When the NFVO determines that the remaining virtual resources of the first processor architecture satisfy the virtual resource requirement of the first virtual machine, and the remaining virtual resources of the second processor architecture satisfy the virtual resource requirement of the second virtual machine, S504 is executed.

For other explanations of S502 and S503, reference may be made to the descriptions of S302 to S303, which are not repeated.

S504, the NFVO sends a first virtual resource authorization response to the VNFM.

In some embodiments, the first virtual resource authorization response includes an identification of the first virtual resource template, an identification of the second virtual resource template, address information of the first server, and address information of the second server. The NFVO may obtain address information of a first server and address information of a second server in the data center. The first virtual resource authorization response can also include an identification of the VDU. The VNFM can be known from the content contained in the first virtual resource authorization response, which is feedback to the VDU, and grants authorization to the virtual resources required by the first virtual machine and grants authorization to the virtual resources required by the second virtual machine. The VNFM can deploy a first virtual machine on the remaining virtual resources of the first server and a second virtual machine on the remaining virtual resources of the second server. The processor architecture of the first server is the same as the processor architecture of the first server. The processor architecture of the second server is the same as the second processor architecture.

S505, the VNFM receives a first virtual resource authorization response sent by the NFVO.

S506, the VNFM deploys the first virtual machine on the first server according to the first virtual resource template indicated by the identification of the first virtual resource template.

And S507, deploying the second virtual machine on the second server by the VNFM according to the second virtual resource template indicated by the identifier of the second virtual resource template.

In some embodiments, the VNFM may determine that the first virtual resource authorization response is feedback for the VDU according to the identifier of the VDU, determine that the virtual resource corresponding to the first virtual resource template is authorized according to the identifier of the first virtual resource template, determine that the virtual resource corresponding to the second virtual resource template is authorized according to the identifier of the second virtual resource template, and deploy, by the VNFM, the first virtual machine according to the first virtual resource template and deploy the second virtual machine according to the second virtual resource template.

Specifically, the VNFM sends a virtual resource application request to the data center, where the virtual resource application request includes address information of the first server and address information of the second server, and the data center authorizes resources of the first server and resources of the second server, and the VNFM may deploy the first virtual machine on the first server according to the virtual resources described by the first virtual resource template and deploy the second virtual machine on the second server according to the virtual resources described by the second virtual resource template. Subsequently, the VNFM determines that the value of the node type of the first virtual resource template and the value of the node type of the second virtual resource template are both node requirement parameters in the VDU, and deploys the common parameters, the software mirror image, and the like of the VDU on the first virtual machine and the second virtual machine, which may specifically refer to related explanations of the prior art and are not described herein.

In the method for deploying a virtual machine provided in the embodiment of the present application, the virtual resource description of the virtual machine included in the VDU is separated into separate descriptions, that is, two different virtual resource templates of a processor architecture are formulated in the VNFD. The virtual resource authorization request sent by the VNFM to the NFVO is used to request to authorize virtual resources of different processor architectures, and the NFVO authorizes different remaining virtual resources, and the remaining virtual resources all satisfy virtual resources required for deploying the virtual machine. Subsequently, the NFVO sends the first virtual resource authorization response or the second virtual resource authorization response to the VNFM to authorize the VNFM to deploy the virtual resource required by the first virtual machine or the virtual resource required by the second virtual machine, and the VNFM may deploy the first virtual machine or the second virtual machine on the server corresponding to the remaining virtual resource of the processor architecture. Compared with the prior art that the virtual machine can be deployed on the residual virtual resources of only one processor architecture, the method and the device for deploying the virtual machine can effectively improve the success rate and efficiency of deploying the virtual machine.

As an example, an example of VNFD defined in the embodiments of the present application is as follows:

as can be seen from the above example, the values of the node types in the template of VM _1 and the template of VM _2 are both the node requirement parameters in VDU1, so that VDU1 can be deployed on VM _1 and VM _2. In addition, the instance _ count value in the template of VM _1 and the template of VM _2 comes from get _ input, that is, the value is obtained from the VNF instantiation request.

In this example, if the input x86_ num is 0 and the ARM_num is 10, it indicates that 10 instances of this VDU1 all need to be deployed on VM _2 node of the ARM based server; if x86_ num is 5 and ARM _numis 5, it means that 5 instances of the VDU need to be deployed in the VM _1 node of the x 86-based server and another 5 instances need to be deployed in the VM _2 node of the ARM-based server.

In the embodiments provided in the present application, the method provided in the embodiments of the present application is introduced from the perspective of interaction between nodes (VNFM, NFVO), respectively. It is understood that, for each network element, for example, VNFM or NFVO, to implement each function in the method provided in the embodiment of the present application, VNFM or NFVO includes a hardware structure and/or a software module corresponding to each function. Those of skill in the art will readily appreciate that the various illustrative algorithmic steps described in connection with the embodiments disclosed herein may be embodied in hardware or in a combination of hardware and computer software. Whether a function is performed in hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution.

In the embodiment of the present application, functional modules of VNFM and NFVO may be divided according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.

In the case of dividing the functional modules according to their respective functions, fig. 6 shows a schematic diagram of a possible configuration of the communication device according to the above and the embodiments, which is capable of executing the steps performed by VNFM, NFVO according to the method embodiments of the present application. The communication apparatus may include: receiving section 601, processing section 602, and transmitting section 603.

When the communication device is a VNFM, the receiving unit 601 is configured to support the VNFM to perform the method described in the embodiment of the present application. For example, the receiving unit 601 is configured to perform or support the communication device to perform S301, S305a and S305b in the method shown in fig. 3, and S501 and S505 in the method shown in fig. 5.

A processing unit 602 for performing or for supporting the VNFM to perform S306a and S306b in the method shown in fig. 3, S506 and S507 in the method shown in fig. 5.

A sending unit 603 configured to perform or be configured to support the VNFM to perform S302 in the method shown in fig. 3, and S502 in the method shown in fig. 5.

When the communication device is an NFVO, the receiving unit 601 is configured to support the NFVO to execute the method described in the embodiment of the present application. For example, the receiving unit 601 is configured to execute or support NFVO to execute S303 in the method shown in fig. 3 and S503 in the method shown in fig. 5.

A sending unit 603, configured to perform or be used to support the NFVO to perform S304a and S304b in the method shown in fig. 3, or S504 in the method shown in fig. 5.

It should be noted that all relevant contents of each step related to the above method embodiment may correspond to the functional description of the corresponding functional module, and are not described herein again.

The communication device provided by the embodiment of the application is used for executing the method of any embodiment, so that the same effect as the method of the embodiment can be achieved.

Fig. 7 shows a communication apparatus 700 provided in the embodiment of the present application, which is used for implementing the function of the VNFM in the above method. The communication device 700 may be a VNFM or a device in a VNFM. Further, the communication device 700 may be a system on a chip. In the embodiment of the present application, the chip system may be formed by a chip, and may also include a chip and other discrete devices. Alternatively, the communication device 700 is configured to implement the function of NFVO in the above method. The communication device 700 may be an NFVO or a device in an NFVO. The communication device 700 may be a system on a chip.

The communication device 700 includes at least one processor 701, which is configured to implement the functions of VNFM or NFVO in the method provided in the embodiment of the present application. For example, the processor 701 may be configured to deploy a virtual machine according to a virtual resource template indicated by the deployment condition, which is specifically described in the detailed description of the method example and is not described herein again.

The communications apparatus 700 can also include at least one memory 702 for storing program instructions and/or data. A memory 702 is coupled to the processor 701. The coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, and may be an electrical, mechanical or other form for information interaction between the devices, units or modules. The processor 701 may cooperate with the memory 702. The processor 701 may execute program instructions stored in the memory 702. At least one of the at least one memory may be included in the processor.

The processor 701 and the memory 702 may also be virtualized processors and virtualized memories.

The communications apparatus 700 can also include a communication interface 703 for communicating with other devices over a transmission medium such that the apparatus used in the communications apparatus 700 can communicate with other devices. Exemplarily, if the communication device is a VNFM, the other device is an NFVO device. If the communication device is an NFVO device, the other device is a VNFM device. The processor 701 transmits and receives data using the communication interface 703, and is configured to implement the method performed by the VNFM or NFVO described in the embodiments corresponding to fig. 3 and 5.

In addition, the communication device 700 may further include a network interface for communicating with an external device. For example, a network interface is used to communicate with a VIM or the like.

In the embodiment of the present application, a specific connection medium among the communication interface 703, the processor 701, and the memory 702 is not limited. In the embodiment of the present application, the communication interface 703, the processor 701, and the memory 702 are connected by a bus 704 in fig. 7, the bus is represented by a thick line in fig. 7, and the connection manner between other components is merely schematic illustration and is not limited thereto. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 7, but this is not intended to represent only one bus or type of bus.

In the embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic blocks disclosed in the embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor.

In the embodiment of the present application, the memory may be a nonvolatile memory, such as a Hard Disk Drive (HDD) or a solid-state drive (SSD), and may also be a volatile memory (RAM), for example. The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data.

Through the description of the foregoing embodiments, it will be clear to those skilled in the art that, for convenience and simplicity of description, only the division of the functional modules is illustrated, and in practical applications, the above function distribution may be completed by different functional modules as needed, that is, the internal structure of the apparatus may be divided into different functional modules to complete all or part of the above described functions.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical functional division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, that is, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or may also be implemented in the form of a software functional unit.

The method provided by the embodiment of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to be performed in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, a network appliance, a terminal, or other programmable apparatus. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital Video Disk (DVD)), or a semiconductor medium, among others.

Claims

1. A method for deploying a virtual machine, comprising:

the method comprises the steps that a Network Function Virtualization Orchestrator (NFVO) device receives a virtual resource authorization request, wherein the virtual resource authorization request is used for requesting to authorize virtual resources required by deployment of a first virtual machine or virtual resources required by deployment of a second virtual machine, the virtual resource authorization request comprises an identifier of a first virtual resource template and an identifier of a second virtual resource template, the first virtual resource template is used for describing the virtual resources required by deployment of the first virtual machine, the first virtual resource template comprises an identifier of a first processor architecture, the second virtual resource template is used for describing the virtual resources required by deployment of the second virtual machine, the second virtual resource template comprises an identifier of a second processor architecture, and the first processor architecture is different from the second processor architecture;

the NFVO device determines that the remaining virtual resources of the first processor architecture in a Virtualization Infrastructure Manager (VIM) meet the virtual resource requirement of the first virtual machine, and sends a first virtual resource authorization response to a Virtual Network Function Management (VNFM) device to authorize the VNFM to deploy the virtual resources required by the first virtual machine, wherein the first virtual resource authorization response comprises an identification of the first virtual resource template and address information of a first server, and the processor architecture of the first server is the same as the first processor architecture; alternatively, the first and second electrodes may be,

the NFVO device determines that the remaining virtual resources of the second processor architecture in the VIM meet the virtual resource requirement of the second virtual machine, and sends a second virtual resource authorization response to the VNFM device to authorize the VNFM to deploy the virtual resources required by the second virtual machine, where the second virtual resource authorization response includes an identifier of the second virtual resource template and address information of a second server, and a processor architecture of the second server is the same as the second processor architecture.

2. The method of claim 1, when the NFVO device determines that the remaining virtual resources of the first processor architecture satisfy the virtual resource requirements of the first virtual machine and the remaining virtual resources of the second processor architecture satisfy the virtual resource requirements of the second virtual machine, the method further comprising:

determining that the first processor architecture has a higher priority than the second processor architecture, sending the first virtual resource authorization response to the VNFM device; or

Determining that the priority of the first processor architecture is lower than the priority of the second processor architecture, and sending the second virtual resource authorization response to the VNFM device.

3. The method according to claim 1 or 2, characterized in that the virtual resource authorization request further comprises an identification of a virtual deployment unit VDU.

4. A method for deploying a virtual machine, comprising:

a Virtual Network Function Management (VNFM) device receives a virtual network function template (VNFD), wherein the VNFD comprises a Virtual Deployment Unit (VDU), a first virtual resource template and a second virtual resource template, the first virtual resource template is used for describing virtual resources required for deploying a first virtual machine, the first virtual resource template comprises an identification of the first virtual resource template and an identification of a first processor architecture, the second virtual resource template is used for describing virtual resources required for deploying a second virtual machine, the second virtual resource template comprises an identification of the second virtual resource template and an identification of a second processor architecture, and the first processor architecture is different from the second processor architecture;

the VNFM device sends a virtual resource authorization request to a Network Function Virtualization Orchestrator (NFVO) device to request authorization for deployment of virtual resources required by the first virtual machine or virtual resources required by the second virtual machine, wherein the virtual resource authorization request comprises an identification of the first virtual resource template and an identification of the second virtual resource template;

the VNFM device receiving a first virtual resource authorization response, the first virtual resource authorization response including an identification of the first virtual resource template and address information of a first server having a processor architecture that is the same as the first processor architecture; deploying, by the VNFM, the first virtual machine on the first server according to the first virtual resource template indicated by the identification of the first virtual resource template; alternatively, the first and second electrodes may be,

the VNFM device receives a second virtual resource authorization response, wherein the second virtual resource authorization response comprises an identification of the second virtual resource template and address information of a second server, and a processor architecture of the second server is the same as the second processor architecture; the VNFM equipment deploys the second virtual machine on the second server according to the second virtual resource template indicated by the identifier of the second virtual resource template.

5. The method of claim 4, wherein the first virtual resource template further comprises a first number of instances instruction, wherein the first number of instances instruction is used to indicate a number of deployments of the first virtual machine, and wherein the second virtual resource template further comprises a second number of instances instruction, wherein the second number of instances instruction is used to indicate a number of deployments of the second virtual machine.

6. The method of claim 5, further comprising:

the VNFM device receives a VNF instantiation request, wherein the VNF instantiation request comprises a value of the number of the first virtual machines and/or a value of the number of the second virtual machines.

7. A method for deploying a virtual machine, comprising:

the method comprises the steps that a Network Function Virtualization Orchestrator (NFVO) device receives a virtual resource authorization request, wherein the virtual resource authorization request is used for requesting to authorize virtual resources required by deployment of a first virtual machine and virtual resources required by deployment of a second virtual machine, the virtual resource authorization request comprises an identifier of a first virtual resource template and an identifier of a second virtual resource template, the first virtual resource template is used for describing the virtual resources required by deployment of the first virtual machine, the first virtual resource template comprises an identifier of a first processor architecture, the second virtual resource template is used for describing the virtual resources required by deployment of the second virtual machine, the second virtual resource template comprises an identifier of a second processor architecture, and the first processor architecture is different from the second processor architecture;

the NFVO device sends a virtual resource authorization response to a Virtual Network Function Management (VNFM) device to authorize the VNFM to deploy virtual resources required by the first virtual machine and virtual resources required by the second virtual machine, wherein the virtual resource authorization response comprises an identifier of the first virtual resource template, an identifier of the second virtual resource template, address information of a first server and address information of a second server, a processor architecture of the first server is the same as the first processor architecture, and a processor architecture of the second server is the same as the second processor architecture.

8. The method of claim 7, wherein the virtual resource authorization request further comprises an identification of a Virtual Deployment Unit (VDU).

9. A method for deploying a virtual machine, comprising:

the VNFM device sends a virtual resource authorization request to a Network Function Virtualization Orchestrator (NFVO) device to request authorization for deployment of virtual resources required by the first virtual machine and virtual resources required by the second virtual machine, wherein the virtual resource authorization request comprises an identification of the first virtual resource template and an identification of the second virtual resource template;

the VNFM device receiving a virtual resource authorization response, the virtual resource authorization response including an identification of the first virtual resource template, an identification of the second virtual resource template, address information of a first server, and address information of a second server, a processor architecture of the first server being the same as the first processor architecture, a processor architecture of the second server being the same as the second processor architecture;

deploying, by the VNFM device, the first virtual machine on the first server according to the first virtual resource template indicated by the identification of the first virtual resource template; the VNFM equipment deploys the second virtual machine on the second server according to the second virtual resource template indicated by the identifier of the second virtual resource template.

10. The method of claim 9, wherein the VDU comprises a node requirement parameter, wherein the first virtual resource template further comprises a node type, wherein the second virtual resource template further comprises the node type, and wherein the method further comprises:

the VNFM equipment determines that the value of the node type of the first virtual resource template and the value of the node type of the second virtual resource template are both node demand parameters in the VDU;

the VNFM device deploys VDUs on the first virtual machine and the second virtual machine.

11. The method of claim 10, wherein the first virtual resource template further comprises a first number of instances instruction indicating a number of deployments of the first virtual machine, and wherein the second virtual resource template further comprises a second number of instances instruction indicating a number of deployments of the second virtual machine.

12. The method of claim 11, further comprising:

13. A communications apparatus, comprising:

a receiving unit, configured to receive a virtual resource authorization request, where the virtual resource authorization request is used to request to authorize a virtual resource required to deploy a first virtual machine or a virtual resource required to deploy a second virtual machine, the virtual resource authorization request includes an identifier of a first virtual resource template and an identifier of a second virtual resource template, the first virtual resource template is used to describe a virtual resource required to deploy the first virtual machine, the first virtual resource template includes an identifier of a first processor architecture, the second virtual resource template is used to describe a virtual resource required to deploy the second virtual machine, the second virtual resource template includes an identifier of a second processor architecture, and the first processor architecture is different from the second processor architecture;

a processing unit configured to determine that remaining virtual resources of the first processor architecture in a virtualized infrastructure manager, VIM, satisfy a virtual resource requirement of the first virtual machine, a sending unit configured to send a first virtual resource authorization response to a virtual network function management, VNFM, device, the first virtual resource authorization response including an identification of the first virtual resource template and address information of a first server, a processor architecture of the first server being the same as the first processor architecture; alternatively, the first and second electrodes may be,

the processing unit is configured to determine that the remaining virtual resources of the second processor architecture in the VIM satisfy the virtual resource requirement of the second virtual machine, and the sending unit is configured to send a second virtual resource authorization response to the VNFM device, where the second virtual resource authorization response includes an identifier of the second virtual resource template and address information of a second server, and a processor architecture of the second server is the same as the second processor architecture.

14. The apparatus of claim 13, wherein when the remaining virtual resources of the first processor architecture satisfy the virtual resource requirements of the first virtual machine and the remaining virtual resources of the second processor architecture satisfy the virtual resource requirements of the second virtual machine,

the processing unit is further configured to determine that a priority of the first processor architecture is higher than a priority of the second processor architecture, and the sending unit is configured to send the first virtual resource authorization response to the VNFM device; or

The processing unit is further configured to determine that the priority of the first processor architecture is lower than the priority of the second processor architecture, and the sending unit is configured to send the second virtual resource authorization response to the VNFM device.

15. The apparatus according to claim 13 or 14, wherein the virtual resource authorization request further comprises an identification of a Virtual Deployment Unit (VDU).

16. A communications apparatus, comprising:

a receiving unit, configured to receive a virtual network function template VNFD, where the VNFD includes a virtual deployment unit VDU, a first virtual resource template, and a second virtual resource template, where the first virtual resource template is used to describe a virtual resource required to deploy a first virtual machine, the first virtual resource template includes an identifier of the first virtual resource template and an identifier of a first processor architecture, the second virtual resource template is used to describe a virtual resource required to deploy a second virtual machine, the second virtual resource template includes an identifier of the second virtual resource template and an identifier of a second processor architecture, and the first processor architecture is different from the second processor architecture;

a sending unit, configured to send a virtual resource authorization request to a network function virtualization orchestrator NFVO device, where the virtual resource authorization request is used to request to authorize a virtual resource required to deploy the first virtual machine or a virtual resource required to deploy the second virtual machine, and the virtual resource authorization request includes an identifier of the first virtual resource template and an identifier of the second virtual resource template;

the receiving unit is further configured to receive a first virtual resource authorization response, where the first virtual resource authorization response includes an identifier of the first virtual resource template and address information of a first server, and a processor architecture of the first server is the same as the first processor architecture; the processing unit is used for deploying the first virtual machine on the first server according to the first virtual resource template indicated by the identifier of the first virtual resource template; alternatively, the first and second liquid crystal display panels may be,

the receiving unit is further configured to receive a second virtual resource authorization response, where the second virtual resource authorization response includes an identifier of the second virtual resource template and address information of a second server, and a processor architecture of the second server is the same as the second processor architecture; the processing unit is configured to deploy the second virtual machine on the second server according to the second virtual resource template indicated by the identifier of the second virtual resource template.

17. The apparatus of claim 16, wherein the first virtual resource template further comprises a first number of instances instruction, wherein the first number of instances instruction is configured to indicate a number of deployments of the first virtual machine, and wherein the second virtual resource template further comprises a second number of instances instruction, wherein the second number of instances instruction is configured to indicate a number of deployments of the second virtual machine.

18. The apparatus of claim 17,

the receiving unit is further configured to receive a VNF instantiation request, where the VNF instantiation request includes a value of the number of the first virtual machine and/or a value of the number of the second virtual machine.

19. A communications apparatus, comprising:

a receiving unit, configured to receive a virtual resource authorization request, where the virtual resource authorization request is used to request to authorize a virtual resource required to deploy a first virtual machine and a virtual resource required to deploy a second virtual machine, the virtual resource authorization request includes an identifier of a first virtual resource template and an identifier of a second virtual resource template, the first virtual resource template is used to describe a virtual resource required to deploy the first virtual machine, the first virtual resource template includes an identifier of a first processor architecture, the second virtual resource template is used to describe a virtual resource required to deploy the second virtual machine, the second virtual resource template includes an identifier of a second processor architecture, and the first processor architecture is different from the second processor architecture;

a sending unit, configured to send a virtual resource authorization response to a virtual network function management VNFM device, where the virtual resource authorization response includes an identifier of the first virtual resource template, an identifier of the second virtual resource template, address information of a first server, and address information of a second server, and a processor architecture of the first server is the same as the first processor architecture, and a processor architecture of the second server is the same as the second processor architecture.

20. The apparatus as recited in claim 19, wherein the virtual resource authorization request further comprises an identification of a Virtual Deployment Unit (VDU).

21. A communications apparatus, comprising:

a sending unit, configured to send a virtual resource authorization request to a network function virtualization orchestrator NFVO device, where the virtual resource authorization request is used to request to authorize a virtual resource required to deploy the first virtual machine and a virtual resource required to deploy the second virtual machine, and the virtual resource authorization request includes an identifier of the first virtual resource template and an identifier of the second virtual resource template;

the receiving unit is further configured to receive a virtual resource authorization response, where the virtual resource authorization response includes an identifier of the first virtual resource template, an identifier of the second virtual resource template, address information of a first server, and address information of a second server, a processor architecture of the first server is the same as the processor architecture of the first server, and a processor architecture of the second server is the same as the processor architecture of the second server;

the processing unit is used for deploying the first virtual machine on the first server according to the first virtual resource template indicated by the identification of the first virtual resource template; the processing unit is further configured to deploy the second virtual machine on the second server according to the second virtual resource template indicated by the identifier of the second virtual resource template.

22. The apparatus of claim 21, wherein the VDU comprises a node requirement parameter, wherein the first virtual resource template further comprises a node type, wherein the second virtual resource template further comprises the node type,

the processing unit is further configured to determine that a value of the node type of the first virtual resource template and a value of the node type of the second virtual resource template are both node requirement parameters in the VDU;

the processing unit is further configured to deploy a VDU on the first virtual machine and the second virtual machine.

23. The apparatus of claim 22, wherein the first virtual resource template further comprises a first number of instances instruction that indicates a number of deployments of the first virtual machine, and wherein the second virtual resource template further comprises a second number of instances instruction that indicates a number of deployments of the second virtual machine.

24. The apparatus of claim 23,

25. A communications apparatus, comprising: at least one processor, a memory, a bus and a transceiver, wherein the memory is for storing a computer program such that the computer program, when executed by the at least one processor, implements the method of any one of claims 1 to 3 or implements the method of any one of claims 7 to 8.

26. An application deployment server, comprising: at least one processor, a memory, a bus and a transceiver, wherein the memory is for storing a computer program such that the computer program, when executed by the at least one processor, implements the method of any one of claims 4 to 6 or implements the method of any one of claims 9 to 12.

27. A computer-readable storage medium, comprising: computer software instructions;

the computer software instructions, when run in a communication device or a chip built in a communication device, cause the communication device apparatus to perform the method of any of claims 1 to 12.