Patent Description:
Embodiments of this application relate to communications technologies, and in particular, to a VNF instantiation method, an NFVO, a VIM, a VNFM, and a system.

Network function virtualization (network function virtualization, NFV) refers to implementing some network functions (for example, a core network function) through software on IT devices, such as a general server unit, a switch, and a memory, by using a virtualization technology in the information technology (information technology, IT) field. In an NFV technology, software and hardware may be decoupled for a network function, so that the network function can be implemented through software and run on a general-purpose IT device. In this way, a user may deploy, instantiate, and migrate a network function to different physical locations of a network according to an actual requirement, without installing a new device, thereby improving deployment and operating efficiency of a network service (network service, NS), and reducing capital expenditures (capital expenditure, CAPEX) and operational expenses (operational expense, OPEX) of the network. It should be understood that the NS is a service provided by a plurality of network functions cooperating with each other. For example, a plurality of core network functions may cooperate with each other to provide a core network service.

Currently, the Interfaces and Architecture (interface and architecture, IFA) Working Group of the NFV Industry Standard Group of the European Telecommunications Standards Institute (european telecommunications standards institute, ETSI) has developed a network functions virtualization management and orchestration (network functions virtualization management and orchestration, NFV-MANO) system structure framework. When a communications operator deploys an NS of a communications network in a cloud data center by using the NFV-MANO system structure framework, in a process in which a network functions virtualization orchestrator (network functions virtualization orchestrator, NFVO) and a virtualized network function manager (virtualized network function manager, VNFM) in the NFV-MANO system structure framework cooperate with each other to implement virtualized network function (virtualized network function, VNF) instantiation, a location of a virtual resource on which a VNF instance is to be deployed may be determined by using an affinity/anti-affinity rule between VNF instances in a network service NS instance and by using a constraint on a geographical location at which the VNF instance is to be deployed.

With the arrival of the <NUM> and internet of things era and an increasing quantity of cloud computing applications, conventional cloud computing technologies cannot meet requirements of "massive connection, low latency, and high bandwidth" on a terminal side. With emergence of an edge computing technology, a concept of an edge cloud emerges, to extend a cloud computing power to an edge side closest to a terminal. Currently, a VNF instance may be deployed on an edge cloud, to implement a function of a multi-access edge computing (multi-access edge computing, MEC) application (edge application for short) by using a VNF. However, the edge application does not need to be combined with another edge application to form a network service, and does not need to be split into functional components or services with a finer granularity either. Therefore, when a management and orchestration capability of NFV is directed from a central cloud to the edge cloud, an existing affinity/anti-affinity rule used for deploying a VNF instance in an NS is not applicable to deploying a VNF instance on the edge cloud. Therefore, how to determine a deployment location of an edge application on an edge cloud is a problem that urgently needs to be resolved.

<NPL> discloses a study on how the 3GPP management system can support the management of edge computing.

<NPL> discloses a report on the functional architecture necessary to provision and manage multi-site network services wherein a set of multi-site use cases are described, analysed and used to produce a set of recommendations for normative work.

<NPL> discloses VNF placement and provisioning optimization strategies over an edge-central carrier cloud infrastructure taking into account Quality of Service (QoS) requirements (i.e., response time, latency constraints and real-time requirements) and using queuing and QoS models.

Embodiments of this application provide a VNF instantiation method, an NFVO, a VIM, a VNFM, and a system, to resolve a technical problem of how to determine a deployment location of an edge application on an edge cloud.

A first aspect and a second aspect relate to the following: A VNFM dynamically matches, based on a QoS attribute of a VNF, a location area that meets the QoS attribute of the VNF for the VNF, so that a QoS requirement of a VNF instance can be met after the VNF instance is deployed in the virtual resource location area. Details are as follows:
According to the first aspect, an embodiment of this application provides a VNF instantiation method in accordance with appended claim <NUM>.

In a possible implementation, the VNFM may further receive a VNF instantiation request message from a network functions virtualization orchestrator NFVO before determining the target virtual resource location area in which the VNF instance is to be deployed. The VNF instantiation request message requests to instantiate the VNF. In this implementation, the VNFM may obtain the QoS attribute of the VNF in the following two manners: In a first manner, the VNF instantiation request message carries the QoS attribute of the VNF; or, the VNF instantiation request message may not carry the QoS attribute of the VNF, and the VNFM obtains the QoS attribute of the VNF from a virtualized network function descriptor (virtualised network function descriptor, VNFD) file. In this way, the VNFM can obtain the QoS attribute of the VNF in flexible and diverse manners.

According to the second aspect, an embodiment of this application provides a VNF instantiation method in accordance with appended claim <NUM>.

According to the methods provided in the first aspect and the second aspect, a mapping relationship between a different virtual resource location area and a QoS attribute is established, so that the VNFM can dynamically match, based on the QoS attribute of the VNF, a virtual resource location area that meets the QoS attribute of the VNF for the VNF. In this way, after the VNF instance is deployed in the virtual resource location area, a QoS requirement of the VNF instance can be met, to ensure user experience when a user accesses the VNF instance.

According to a third aspect, an embodiment of this application provides a VNFM in accordance with appended claim <NUM>.

In a possible implementation, the receiving unit is further configured to receive a VNF instantiation request message from an NFVO before the processing unit determines the target virtual resource location area in which the VNF instance is to be deployed. The VNF instantiation request message requests to instantiate the VNF. In this implementation, the QoS attribute of the VNF may be obtained in the following two manners: The VNF instantiation request message carries the QoS attribute of the VNF. Alternatively, the processing unit is further configured to obtain the QoS attribute of the VNF from a VNFD before determining the target virtual resource location area in which the VNF instance is to be deployed.

According to a fourth aspect, an embodiment of this application provides a VIM in accordance with appended claim <NUM>.

For beneficial effects of the VNFM and the VIM provided in the third aspect to the fourth aspect, refer to the beneficial effects of the first aspect and the second aspect.

In the first aspect to the fourth aspect, the VNF instantiation request message does not carry an affinity rule and/or an anti-affinity rule for deploying the VNF. In other words, the VNF instantiation request message does not trigger a VNF lifecycle management granting request message. In the foregoing manner, a process of instantiating the VNF can be simplified.

In an example not claimed the VNF is a virtualized multi-access edge application, the QoS attribute is a QoS attribute of the multi-access edge application, the VNF is instantiated in a predetermined edge data center, and the target virtual resource location area is located in the predetermined edge data center. In this example, the QoS attribute may include at least one of the following: a network latency, a throughput, a jitter, and a packet loss rate. According to the methods provided in the embodiments, a virtual resource location area that meets a QoS attribute of a virtualized multi-access edge application can be dynamically matched for the virtualized multi-access edge application based on the QoS attribute of the virtualized multi-access edge application. In this way, after the virtualized multi-access edge application instance is deployed in the virtual resource location area, a QoS requirement of the virtualized multi-access edge application instance can be met, to ensure user experience when a user accesses the virtualized multi-access edge application.

According to a fifth aspect, an embodiment of this application provides a communications system, including a VNFM, and a VIM. The VNFM is configured to perform the method for the VNFM in the any one of possible implementations of the first aspect and the second aspect. The VIM is configured to perform the method for the VIM in any one of the possible implementations of the first aspect and the second aspect.

According to the VNF instantiation method, the VIM, the VNFM, and the system provided in the embodiments of this application, a mapping relationship between a different virtual resource location area on an edge cloud and the QoS attribute is established, so that a virtual resource location area that meets a QoS attribute of a VNF can be dynamically matched for the VNF based on the QoS attribute of the VNF. In this way, after a VNF instance is deployed in the virtual resource location area, a QoS requirement of the VNF instance can be met, to ensure user experience when a user accesses the VNF instance.

<FIG> is a schematic diagram of an ETSI NFV-MANO system structure framework. As shown in <FIG>, the NFV-MANO system structure framework may include a network functions virtualization orchestrator (network functions virtualization orchestrator, NFVO), a virtualized network function manager (virtualized network function manager, VNFM), a virtualized infrastructure manager (virtualized infrastructure manager, VIM), a network functions virtualization infrastructure (network functions virtualization Infrastructure, NFVI), operations and business support systems (operations and business support systems, OSSBSS), and an element manager (element manager, EM). A person skilled in the art can understand that the NFV-MANO system structure framework shown in <FIG> is not construed as a limitation on the structure framework. During specific implementation, the NFV-MANO system structure framework may include more or fewer functional modules than those shown in the figure, or some functional modules may be combined, or the like.

A virtualized network function (virtualized network function, VNF) corresponds to a physical network function (physical network function, PNF) in a conventional non-virtualized network, and is configured to implement the physical network function. It should be understood that a functional behavior and a status of a network function are irrelevant to whether the network function is virtualized, and an NFV technology can enable the VNF and the PNF to have a same functional behavior and a same external interface. Using a <NUM> core network (evolved packet core, EPC) as an example, the VNF may be a network element in a virtualized EPC, for example, a virtualized mobility management entity (Mobility Management Entity, MME), a virtualized serving gateway (serving gateway, SGW), or a virtualized public data network gateway (public data network gateway, PGW).

The NFVI is an infrastructure layer of an NFV function, and includes a hardware (hardware, HW) resource, a virtual resource, and a virtualization layer. The hardware resource includes a plurality of pieces of HW. Each HW may be a hardware entity capable of running at least one virtual machine (Virtual Machine, VM). For example, one piece of HW may be an IT device (for example, a general-purpose server, switch, or memory). The virtualization layer is configured to virtualize the HW to form at least one virtual machine (Virtual Machine, VM). One VNF instance can be run on each VM. It should be understood that, from a perspective of the VNF, the virtualization layer and the hardware resource may be considered as a complete entity capable of providing a virtual resource required by a VNF instance. The VNF instance herein is a result of instantiating the VNF. It should be noted that a quantity of pieces of HW included in the hardware resource and a quantity of VMs that can be run on one piece of HW in <FIG> are merely examples. This is not limited in this embodiment of this application.

The NFVO is configured to manage and process a network service descriptor (network service descriptor, NSD) and a virtualized network function forwarding graph (virtualized network function forwarding graph, VNFFG), manage a lifecycle of an NS, and cooperate with the VNFM to manage a lifecycle of a VNF, and has a global view function for virtual resources, and the like.

The VNFM is configured to manage a lifecycle of a VNF and manage a virtualized network function descriptor (virtualised network function descriptor, VNFD). The VNFD describes configuration information of a VNF in a deployment phase and an operating phase. It should be understood that the managing the lifecycle of the VNF herein includes a series of management operations in the entire lifecycle from creation of a VNF instance to termination of the VNF instance, for example, instantiation of the VNF, elastic scaling (for example, scaling out/up (scaling out/up) or scaling in/down (scaling in/down)) of the VNF instance, healing (healing) of the VNF instance, updating of the VNF instance, and termination of the VNF instance.

The VIM is configured to manage (for example, reserve resources and allocate resources) virtualized resources (for example, virtual computing resources, storage resources, and network resources) at the infrastructure layer, monitor a virtual resource status, report a virtual resource failure, provide a virtualized resource pool for an upper-layer application, and the like.

The operations and business support systems (operations and business support systems, OSSBSS) are integrated support systems of a telecommunications operator for sharing information resources, and mainly include the following parts: network management, system management, charging, business, accounting, customer services, and the like. In the architecture shown in <FIG>, the OSS/BSS is configured to manage a network.

The element manager (element manager, EM) is configured to perform conventional fault, configuration, account, performance, and security management (fault management, configuration management, account management, performance management, security management, FCAPS) and the like for a VNF.

It should be understood that, in the NFV-MANO system structure framework shown in <FIG>, the NFVO, the VNFM, and the VIM may be separately deployed on different hardware entities, or may be deployed on one hardware entity, or some of the NFVO, the VNFM, and the VIM may be deployed on one hardware entity. This may be specifically arranged according to a requirement. This is not limited in this embodiment of this application. In some embodiments, the NFVO, the VNFM, and the VIM may be alternatively referred to as an NFVO entity, a VNFM entity, and a VIM entity. The entity may be a logical entity, a hardware entity, or the like.

Currently, a communications operator may deploy an NS of a communications network in a data center by using the NFV-MANO system structure framework shown in <FIG> in the foregoing manner, to improve deployment and operating efficiency of the NS, and reduce a CAPEX and an OPEX of the network. When the NS is deployed in the data center, in a process in which the NFVO and the VNFM cooperate to implement VNF instantiation, a virtual resource location constraint mechanism for deploying a VNF instance mainly includes the following two aspects.

An affinity/anti-affinity rule between a plurality of VNF instances in an NS instance is defined in an NSD. The rule is used to indicate to deploy newly deployed VNF instances in the NS instance to a same location area or different location areas, and deploy a newly deployed VNF instance to a location area that is the same as or different from that of an already deployed VNF instance in the NS instance (a location area may also be referred to as a virtual resource location area, and this is not distinguished in this embodiment of this application). For example, when two VNF instances meet an affinity rule, the two VNF instances may be deployed in a same location area; or when two VNF instances meet an anti-affinity rule, the two VNF instances need to be deployed in different location areas. It should be understood that the foregoing location area includes but is not limited to a network function virtualization infrastructure point of presence (network function virtualization infrastructure point of presence, NFVI-PoP), a network function virtualization infrastructure zone (network function virtualization infrastructure zone, NFVI-Zone), a network function virtualization infrastructure zone group (network function virtualization infrastructure zone group, NFVI-Zone Group), a network function virtualization infrastructure node (network function virtualization infrastructure node, NFVI-node), and the like.

A geographical location constraint for deploying a VNF instance is defined in an NS lifecycle management operation. For example, the VNF instance needs to be deployed on a virtual resource of a specified NFVI-PoP.

It should be understood that, when a network function of the communications network is implemented by a VNF, because there is an explicit dependency relationship or association relationship between network functions and between components in one network function, with the foregoing location constraint mechanism (the aspect <NUM> and the aspect <NUM>) for deploying a VNF instance, reliability and robustness of an NS including network functions that serves as an operating entity can be ensured.

<FIG> is a schematic diagram of a data center according to an embodiment of this application. As shown in <FIG>, with the arrival of the <NUM> and internet of things era and an increasing quantity of cloud computing applications, conventional cloud computing technologies cannot meet requirements of "massive connection, low latency, and high bandwidth" on a terminal side. With emergence of a multi-access edge computing technology, a concept of an edge data center emerges, to extend a cloud computing power to an edge side closest to a terminal. The edge data center is a concept proposed with respect to a conventional data center, is a data center built on edge infrastructure based on a core of a cloud computing technology and a capability of multi-access edge computing, and forms an elastic cloud platform of computing, network, storage, security, and other capabilities at an edge location. In this scenario, the conventional data center may be referred to as a central data center or a central cloud, and the edge data center may be referred to as an edge cloud. A central cloud may be connected to a plurality of edge clouds distributed in different locations by using a provider edge (provider edge, PE) of a wide area network. <FIG> is a schematic diagram of an example in which a central cloud is connected to one edge cloud. With network forwarding, storage, computing, and other operations performed on the edge cloud, a response latency, a load on a cloud, and bandwidth costs can be reduced, and cloud services such as network-wide scheduling and computing power distribution can be provided. It should be understood that, in this embodiment of this application, the concept of the edge cloud is equivalent to the concept of the edge data center. This is not distinguished in this embodiment of this application.

Currently, a VNF instance may be deployed on the edge cloud, to implement a function of an edge application by using a VNF. Then, the edge application does not need to be combined with another edge application into a network service, and does not need to be split into functional components or services with a finer granularity either. Therefore, when a management and orchestration capability of NFV is directed from the central cloud to the edge cloud, the existing affinity/anti-affinity rule in the location constraint mechanism used for deploying a VNF instance in an NS is not applicable to deploying a VNF instance on the edge cloud. For example, the edge application is a high-definition video application. If a location of a "VNF instance for implementing the application" is determined still by using the foregoing affinity/anti-affinity rule, because the rule focuses only on a dependency relationship or an association relationship between VNF instances and between components in a VNF instance, but does not focus on characteristics of a VNF instance itself, network characteristics of the determined location at which the VNF instance is to be deployed may not be able to meet QoS attributes of high bandwidth and low latency of the application. In this case, after the VNF instance is deployed at the location, the VNF instance cannot meet network characteristics of high bandwidth and low latency, and consequently, user experience is poor when a user accesses the high-definition video application by using a terminal.

Therefore, how to determine a deployment location of an edge application on an edge cloud is a problem that urgently needs to be resolved.

An edge application can independently provide a service, and different edge applications have different QoS attributes (that is, there are different QoS requirements for an edge network). Therefore, the embodiments of this application provide a VNF instantiation method. When a VNF instance for implementing a function of an edge application is deployed on an edge cloud by using the NFV-MANO system structure framework shown in <FIG>, a location of the "VNF instance for implementing the application" is no longer determined according to the foregoing affinity/anti-affinity rule. Instead, a mapping relationship between a different virtual resource location area on the edge cloud and a QoS attribute is established, so that a virtual resource location area that meets a QoS attribute of a VNF can be dynamically matched for the VNF based on the QoS attribute of the VNF. In this way, after a VNF instance is deployed at a target virtual resource location in the virtual resource location area, a QoS requirement of the VNF instance can be met, to ensure user experience when a user accesses the VNF instance.

It should be understood that the foregoing VNF for implementing the edge application may be referred to as a virtualized edge application. Correspondingly, the QoS attribute of the VNF herein may be a QoS attribute of the edge application. For example, the QoS attribute may include at least one of the following: a network latency (latency), a throughput (throughput), a jitter (jitter), a packet loss rate, and the like. The foregoing edge cloud may be a predetermined edge cloud on which the VNF is to be deployed, that is, the VNF is instantiated on the predetermined edge cloud. That is, the foregoing target virtual resource location area is located on the predetermined edge cloud.

In addition, the VNF instantiation method provided in the embodiments of this application includes but is not limited to the foregoing scenario in which an edge application is deployed on an edge cloud, and is also applicable to a scenario in which another VNF instance with a QoS attribute is deployed on an edge cloud, a scenario in which a VNF instance with a QoS attribute is deployed on another cloud (for example, a central cloud), and the like.

The following describes in detail technical solutions of embodiments of this application with reference to specific embodiments. The following several specific embodiments may be combined with each other, and same or similar concepts or processes may not be described in detail in some embodiments.

<FIG> is a schematic flowchart of a VNF instantiation method according to an embodiment of this application. As shown in <FIG>, this embodiment relates to a process in which a VNFM dynamically matches, based on a QoS attribute of a VNF, a location area that meets the QoS attribute of the VNF for the VNF.

S101: A VNFM determines, based on a QoS attribute of a to-be-instantiated VNF and a preset mapping relationship between a QoS attribute and a virtual resource location area, a target virtual resource location area in which a VNF instance is to be deployed.

S102: The VNFM sends a virtual resource allocation request message to a VIM.

Correspondingly, the VIM receives the virtual resource allocation request message. The virtual resource allocation request message requests to allocate a virtual resource on which the VNF instance is to be deployed. The virtual resource allocation request message carries information about the target virtual resource location area.

S103: The VIM sends a virtual resource allocation response message to the VNFM.

The VNFM receives the virtual resource allocation response message. The virtual resource allocation response message indicates information about a target virtual resource on which the VNF instance is to be deployed. The target virtual resource is located in the target virtual resource location area determined by the VNFM.

S104: The VNFM instantiates the VNF on the target virtual resource based on the information about the target virtual resource.

Optionally, before step S101, the method may further include the following step:
Step S100: An NFVO sends a VNF instantiation request message to the VNFM.

Correspondingly, the VNFM receives the VNF instantiation request message. The VNF instantiation request message requests to instantiate the VNF. In this embodiment, a manner of triggering the NFVO to perform a VNF instantiation procedure is not limited. For example, an upper layer (for example, an OSSBSS system) may trigger the NFVO to perform the VNF instantiation procedure, that is, trigger the NFVO to send the VNF instantiation request message to the VNFM.

Optionally, the VNF instantiation request message may carry an identifier of the to-be-instantiated VNF, an identifier of a VNF deployment flavor (flavor), external virtual link information of the VNF, and the like. It should be understood that, because a VNF instance on an edge cloud no longer belongs to an NS instance, the VNF instantiation request message does not trigger a VNF lifecycle management granting request message, that is, the VNFM does not allow or reject a to-be-performed VNF lifecycle management operation by using the NFVO based on a dependency relationship between members in an NS instance, in other words, the VNF instantiation request message does not carry an affinity rule and/or an anti-affinity rule required for deploying the VNF.

In this implementation, after step S104, the method may further include the following step:
Step S105: The VNFM sends a VNF instantiation response message to the NFVO.

Correspondingly, the NFVO receives the VNF instantiation response message. The VNF instantiation response message indicates that deployment of the VNF instance is completed.

In this embodiment, the preset mapping relationship between a QoS attribute and a virtual resource location area may be a mapping relationship between a QoS attribute and a virtual resource location area on an edge cloud on which the VNF instance is to be deployed. The mapping relationship is pre-established, so that different virtual resource location areas on the edge cloud can have different network characteristics, to meet QoS requirements of VNF instances deployed in the location areas. In a possible implementation, for example, the foregoing preset mapping relationship between a QoS attribute and a virtual resource location area may be shown in Table <NUM>.

Both n and m are positive integers. Each resource location area may correspond to at least one QoS attribute. A value range of each QoS attribute includes a value range of each parameter included in the QoS attribute. The value range of each parameter may be continuous or discontinuous. When one resource location area corresponds to a plurality of QoS attributes, all parameters included in the QoS attributes are different; or some parameters included in the QoS attributes are different, and value ranges of same parameters are the same or different.

For example, the QoS attribute <NUM> and the QoS attribute <NUM> are used as examples. It is assumed that parameters included in a QoS attribute include a network latency, a throughput, a jitter, and a packet loss rate. The QoS attribute <NUM> includes two parameters: a network latency and a throughput; and the QoS attribute <NUM> includes two parameters: a jitter and a packet loss rate. Alternatively, the QoS attribute <NUM> includes three parameters: a network latency, a throughput, and a jitter; and the QoS attribute <NUM> includes three parameters: a throughput, a jitter, and a packet loss rate. A value range of the throughput in the QoS attribute <NUM> is the same as or different from a value range of the throughput in the QoS attribute <NUM>.

It should be understood that one virtual resource location area described in this embodiment of this application may include at least one virtual resource on which a VNF instance can be deployed. For descriptions of the virtual resource location area, refer to the foregoing descriptions of the location area.

In this embodiment, the VNFM stores the preset mapping relationship between a QoS attribute and a virtual resource location area; or the VNFM may obtain the preset mapping relationship between a QoS attribute and a virtual resource location area from a side of another functional module (for example, the NFVO) in an NFV-MANO system structure framework. When the VNFM needs to instantiate a VNF, the VNFM may select, from the preset mapping relationship between a QoS attribute and a virtual resource based on a QoS attribute of the to-be-instantiated VNF and the mapping relationship, a virtual resource location area that meets the QoS attribute of the to-be-instantiated VNF, and use the virtual resource location area as a target virtual resource location area in which a VNF instance is to be deployed.

In this way, after the VNFM adds information about the target virtual resource location area to a virtual resource allocation request message and sends the virtual resource allocation request message to the VIM, the VIM may select, from the target virtual resource location area, a target virtual resource on which the VNF instance is to be deployed, so that the VNFM can instantiate the VNF on the target virtual resource. In this manner, the VNF instance can be deployed on the target virtual resource that can meet the QoS attribute of the VNF, so that user experience can be ensured when a user accesses the VNF instance.

A manner of obtaining the QoS attribute of the to-be-instantiated VNF by the VNFM is not limited in this embodiment. For example, the VNF instantiation request message from the NFVO may carry the QoS attribute of the to-be-instantiated VNF. For another example, the QoS attribute of the VNF is added to a VNFD. In this way, the VNFM may obtain the QoS attribute of the VNF from the VNFD. In this implementation, the VNF instantiation request message from the NFVO may not carry the QoS attribute of the to-be-instantiated VNF.

In a possible implementation, the VNF instantiation request message from the NFVO may further carry indication information. The indication information is used to indicate to determine a target virtual resource location area for the to-be-instantiated VNF in a best effort (best effort) manner when there is no virtual resource location area that meets the QoS attribute of the to-be-instantiated VNF. In this implementation, in the following cases, the VNFM may determine a target virtual resource location area for the to-be-instantiated VNF in the following manners. Details are as follows.

In a first case, when the VNFM does not find, from the preset mapping relationship between a QoS attribute and a virtual resource location area, a virtual resource location area that matches the QoS attribute of the to-be-instantiated VNF, downgrade processing (for example, downgrade by one order or two orders) may be performed on the QoS attribute of the to-be-instantiated VNF, to search the preset mapping relationship between a QoS attribute and a virtual resource location area for a virtual resource location area that matches a QoS attribute obtained through downgrade processing, and use the virtual resource location area as a target virtual resource location area in which the VNF instance is to be deployed. It should be understood that the downgrade herein may be downgrading an insignificant parameter in the QoS attribute, for example, downgrading a packet loss rate from <NUM>% to <NUM>%; or downgrading all parameters in the QoS attribute.

Alternatively, when the VNFM does not find, from the preset mapping relationship between a QoS attribute and a virtual resource location area, a virtual resource location area that matches the QoS attribute of the to-be-instantiated VNF, upgrade processing (for example, upgrade by one order or two orders) may be performed on the QoS attribute of the to-be-instantiated VNF, to obtain a target virtual resource location area in which the VNF instance is to be deployed. The implementation and technical means are similar to those of the downgrade processing.

In a second case, after the VNFM determines a target virtual resource location area from the preset mapping relationship between a QoS attribute and a virtual resource location area, if the VNFM finds, in a process of interacting with the VIM, that no available resource in the target virtual resource location area can be used to deploy the VNF instance, the VNFM may further redetermine a target virtual resource location area in the foregoing downgrade or upgrade manner, and interact with the VIM based on the redetermined target virtual resource location area to determine a target virtual resource location at which the VNF instance is to be deployed.

In the foregoing manners, when there is no virtual resource location area that meets the QoS attribute of the to-be-instantiated VNF, a virtual resource location area corresponding to a QoS attribute that is not greatly different from the QoS attribute of the VNF may be allocated to the to-be-instantiated VNF. In this way, after the VNF instance is deployed in the virtual resource location area, actual experience of accessing the VNF instance by a user does not greatly deviate from QoS of the VNF instance, thereby ensuring user experience.

According to the VNF instantiation method provided in this embodiment of this application, a mapping relationship between a different virtual resource location area on an edge cloud and the QoS attribute is established, so that a virtual resource location area that meets a QoS attribute of a VNF can be dynamically matched for the VNF based on the QoS attribute of the VNF. In this way, after a VNF instance is deployed in the virtual resource location area, a QoS requirement of the VNF instance can be met, to ensure user experience when a user accesses the VNF instance.

<FIG> is a schematic flowchart of another VNF instantiation method according to an embodiment not claimed of this application. This embodiment relates to a process in which an NFVO dynamically matches, based on a QoS attribute of a VNF, a location area that meets the QoS attribute of the VNF for the VNF.

S201: An NFVO determines, based on a QoS attribute of a to-be-instantiated VNF and a preset mapping relationship between a QoS attribute and a virtual resource location area, a target virtual resource location area in which a VNF instance is to be deployed.

In this embodiment, a manner of triggering the NFVO to perform a VNF instantiation procedure is not limited. For example, an upper layer (for example, an OSSBSS system) may trigger the NFVO to perform the VNF instantiation procedure.

S202: The NFVO sends a virtual resource allocation request message to a VIM.

Correspondingly, the VIM receives the virtual resource allocation request message. The virtual resource allocation request message requests to allocate a virtual resource on which the VNF instance is to be deployed. The virtual resource allocation request message carries information about the target virtual resource location area determined by the NFVO.

S203: The VIM sends a virtual resource allocation response message to the NFVO.

Correspondingly, the NFVO receives the virtual resource allocation response message. The virtual resource allocation response message indicates information about a target virtual resource on which the VNF instance is to be deployed. The target virtual resource is located in the target virtual resource location area.

S204: The NFVO sends a VNF instantiation request message to a VNFM.

Correspondingly, the VNFM receives the VNF instantiation request message. The VNF instantiation request message requests to instantiate the VNF. The VNF instantiation request message carries the information about the target virtual resource.

Optionally, the VNF instantiation request message may further carry an identifier of the to-be-instantiated VNF, an identifier of a VNF deployment flavor (flavor), external virtual link information of the VNF, and the like. It should be understood that, because a VNF instance on an edge cloud no longer belongs to an NS instance, the VNF instantiation request message does not trigger a VNF lifecycle management granting request message, that is, the VNFM does not allow or reject a to-be-performed VNF lifecycle management operation by using the NFVO based on a dependency relationship between members in an NS instance, in other words, the VNF instantiation request message does not carry an affinity rule and/or an anti-affinity rule required for deploying a VNF.

S205: The VNFM instantiates the VNF on the target virtual resource based on the information about the target virtual resource.

In a possible implementation, after step S205, the method may further include the following step:
Step S206: The VNFM sends a VNF instantiation response message to the NFVO.

In this embodiment, the NFVO stores the preset mapping relationship between a QoS attribute and a virtual resource location area; or the NFVO may obtain the preset mapping relationship between a QoS attribute and a virtual resource location area from a side of another functional module (for example, the VNFM) in an NFV-MANO system structure framework. When the NFVO triggers instantiation of a VNF, the NFVO may select, from the preset mapping relationship between a QoS attribute and a virtual resource based on a QoS attribute of the to-be-instantiated VNF and the mapping relationship, a virtual resource location area that meets the QoS attribute of the to-be-instantiated VNF, and use the virtual resource location area as a target virtual resource location area in which a VNF instance is to be deployed. For how the NFVO selects, from the preset mapping relationship between a QoS attribute and a virtual resource based on the QoS attribute of the to-be-instantiated VNF and the mapping relationship, a virtual resource location area that meets the QoS attribute of the to-be-instantiated VNF, refer to the descriptions of determining the target virtual resource location area by the VNFM based on the mapping relationship in the embodiment in <FIG>.

In this way, after the NFVO adds information about the target virtual resource location area to a virtual resource allocation request message and sends the virtual resource allocation request message to the VIM, the VIM may select, from the target virtual resource location area, a target virtual resource on which the VNF instance is to be deployed, so that the NFVO can trigger, by using a VNF instantiation request message, the VNFM to instantiate the VNF on the target virtual resource. In this manner, the VNF instance can be deployed on the target virtual resource that can meet the QoS attribute of the VNF, so that user experience can be ensured when a user accesses the VNF instance.

A manner of obtaining the QoS attribute of the to-be-instantiated VNF by the NFVO is not limited in this embodiment. For example, the QoS attribute of the VNF may be added to a VNFD/NSD. In this way, the NFVO may obtain the QoS attribute of the VNF from the VNFD/NSD.

In a possible implementation, when the NFVO determines a target virtual resource location area for the to-be-instantiated VNF, if the first case and the second case described in the embodiment of <FIG> occur, the NFVO may also determine a target virtual resource location area for the to-be-instantiated VNF in a best effort manner. The implementation is similar, and details are not described herein again. In this manner, when there is no virtual resource location area that meets the QoS attribute of the to-be-instantiated VNF, a virtual resource location area corresponding to a QoS attribute that is not greatly different from the QoS attribute of the VNF may be allocated to the to-be-instantiated VNF. In this way, after the VNF instance is deployed in the virtual resource location area, actual experience of accessing the VNF instance by a user does not greatly deviate from QoS of the VNF instance, thereby ensuring user experience.

<FIG> is a schematic flowchart of still another VNF instantiation method according to an embodiment not claimed of this application. This embodiment relates to a process in which a VIM dynamically matches, based on a QoS attribute of a VNF, a location area that meets the QoS attribute of the VNF for the VNF.

S301: A VNFM sends a virtual resource allocation request message to a VIM.

Correspondingly, the VIM receives the virtual resource allocation request message. The virtual resource allocation request message requests to allocate a virtual resource on which a VNF instance is to be deployed. The virtual resource allocation request message carries a QoS attribute of a VNF.

S302: The VIM determines, based on the QoS attribute of the VNF and a preset mapping relationship between a QoS attribute and a virtual resource location area, a target virtual resource location area in which the VNF instance is to be deployed.

S303: The VIM sends a virtual resource allocation response message to the VNFM.

Correspondingly, the VNFM receives the virtual resource allocation response message. The virtual resource allocation response message indicates information about a target virtual resource on which the VNF instance is to be deployed. The target virtual resource is located in the target virtual resource location area.

S304: The VNFM instantiates the VNF on the target virtual resource based on the information about the target virtual resource.

Optionally, before step S301, the method may further include the following step:
S300: An NFVO sends a VNF instantiation request message to the VNFM.

Optionally, the VNF instantiation request message may carry an identifier of the to-be-instantiated VNF, an identifier of a VNF deployment flavor (flavor), external virtual link information of the VNF, and the like. It should be understood that, because a VNF instance on an edge cloud no longer belongs to an NS instance, the VNF instantiation request message does not trigger a VNF lifecycle management granting request message, that is, the VNFM does not allow or reject a to-be-performed VNF lifecycle management operation by using the NFVO based on a dependency relationship between members in an NS instance, in other words, the VNF instantiation request message does not carry an affinity rule and/or an anti-affinity rule required for deploying a VNF.

In this implementation, after step S304, the method may further include the following step:
Step S305: The VNFM sends a VNF instantiation response message to the NFVO.

In this embodiment, the VIM stores the preset mapping relationship between a QoS attribute and a virtual resource location area; or the VIM may obtain the preset mapping relationship between a QoS attribute and a virtual resource location area from a side of another functional module (for example, the VNFM) in an NFV-MANO system structure framework. When receiving the virtual resource allocation request message from the VNFM, the VIM may select, from the preset mapping relationship between a QoS attribute and a virtual resource based on the QoS attribute of the to-be-instantiated VNF and the mapping relationship, a virtual resource location area that meets the QoS attribute of the to-be-instantiated VNF, and use the virtual resource location area as a target virtual resource location area in which the VNF instance is to be deployed. For how the VIM selects, from the preset mapping relationship between a QoS attribute and a virtual resource based on the QoS attribute of the to-be-instantiated VNF and the mapping relationship, a virtual resource location area that meets the QoS attribute of the to-be-instantiated VNF, refer to the descriptions of determining the target virtual resource location area by the VNFM based on the mapping relationship in the embodiment in <FIG>.

In this way, after determining the target virtual resource location area in which the VNF instance is to be deployed, the VIM may select, from the target virtual resource location area, a target virtual resource on which the VNF instance is to be deployed, and feed back the target virtual resource to the VNFM, so that the VNFM instantiates the VNF on the target virtual resource. In this manner, the VNF instance can be deployed on the target virtual resource that can meet the QoS attribute of the VNF, so that user experience can be ensured when a user accesses the VNF instance.

In a possible implementation, when the VIM determines a target virtual resource location area for the to-be-instantiated VNF, if the first case and the second case described in the embodiment of <FIG> occur, the VIM may also determine a target virtual resource location area for the to-be-instantiated VNF in a best effort manner. An implementation thereof is similar, and details are not described herein again. In this manner, when there is no virtual resource location area that meets the QoS attribute of the to-be-instantiated VNF, a virtual resource location area corresponding to a QoS attribute that is not greatly different from the QoS attribute of the VNF may be allocated to the to-be-instantiated VNF. In this way, after the VNF instance is deployed in the virtual resource location area, actual experience of accessing the VNF instance by a user does not greatly deviate from QoS of the VNF instance, thereby ensuring user experience.

<FIG> is a schematic flowchart of still another VNF instantiation method according to an embodiment not claimed of this application. This embodiment relates to a process in which a VIM dynamically matches, based on a QoS attribute of a VNF, a location area that meets the QoS attribute of the VNF for the VNF. A difference between this embodiment and the embodiment shown in <FIG> lies in that an NFVO triggers the VIM to perform the procedure.

S401: An NFVO sends a virtual resource allocation request message to a VIM.

It should be understood that, in this embodiment, a manner of triggering the NFVO to perform a VNF instantiation procedure is not limited. For example, an upper layer (for example, an OSSBSS system) may trigger the NFVO to perform the VNF instantiation procedure.

S402: The VIM determines, based on the QoS attribute of the VNF and a preset mapping relationship between a QoS attribute and a virtual resource location area, a target virtual resource location area in which the VNF instance is to be deployed.

S403: The VIM sends a virtual resource allocation response message to the NFVO.

S404: The NFVO sends a VNF instantiation request message to a VNFM.

S405: The VNFM instantiates the VNF on the target virtual resource based on the information about the target virtual resource.

In a possible implementation, after step S405, the method may further include the following step:
Step S406: The VNFM sends a VNF instantiation response message to the NFVO.

In this embodiment, the VIM stores the preset mapping relationship between a QoS attribute and a virtual resource location area; or the VIM may obtain the preset mapping relationship between a QoS attribute and a virtual resource location area from a side of another functional module (for example, the VNFM) in an NFV-MANO system structure framework. When receiving the virtual resource allocation request message from the NFVO, the VIM may select, from the preset mapping relationship between a QoS attribute and a virtual resource based on the QoS attribute of the to-be-instantiated VNF and the mapping relationship, a virtual resource location area that meets the QoS attribute of the to-be-instantiated VNF, and use the virtual resource location area as a target virtual resource location area in which the VNF instance is to be deployed. For how the VIM selects, from the preset mapping relationship between a QoS attribute and a virtual resource based on the QoS attribute of the to-be-instantiated VNF and the mapping relationship, a virtual resource location area that meets the QoS attribute of the to-be-instantiated VNF, refer to the descriptions of determining the target virtual resource location area by the VNFM based on the mapping relationship in the embodiment in <FIG>.

In this way, after determining the target virtual resource location area in which the VNF instance is to be deployed, the VIM may select, from the target virtual resource location area, a target virtual resource on which the VNF instance is to be deployed, and feed back the target virtual resource to the NFVO, so that the NFVO triggers the VNFM to instantiate the VNF on the target virtual resource. In this manner, the VNF instance can be deployed on the target virtual resource that can meet the QoS attribute of the VNF, so that user experience can be ensured when a user accesses the VNF instance.

It should be understood that, in the foregoing method embodiments, interaction between the NFVO, the VNFM, and the VIM in the NFV-MANO system structure framework shown in <FIG> is used as an example to describe the VNF instantiation method provided in the embodiments of this application. However, a person skilled in the art can understand that, with evolution of the NFV-MANO system structure framework, any functional module capable of triggering VNF instantiation, for example, a multi-access edge platform manager-NFV (multi-access edge platform manager-NFV, MEPM-V) on an edge cloud, may implement the foregoing embodiments in the foregoing manners. Because a function of the MPEM-V is similar to that of the VNFM, in the foregoing method embodiments, the MEPM-V, instead of the VNFM, may be alternatively used to interact with the NFVO and the VIM to implement the foregoing method embodiments. A principle and a technical effect thereof are similar, and details are not described herein again.

<FIG> is a schematic diagram of a structure of a VNFM according to an embodiment of this application. As shown in <FIG>, the VNFM may include a processing unit <NUM>, a sending unit <NUM>, and a receiving unit <NUM>.

The processing unit <NUM> is configured to determine, based on a quality of service QoS attribute of a to-be-instantiated virtualized network function VNF and a preset mapping relationship between a QoS attribute and a virtual resource location area, a target virtual resource location area in which a VNF instance is to be deployed.

The sending unit <NUM> is configured to send a virtual resource allocation request message to a virtualized infrastructure manager VIM. The virtual resource allocation request message requests to allocate a virtual resource on which the VNF instance is to be deployed. The virtual resource allocation request message carries information about the target virtual resource location area.

The receiving unit <NUM> is configured to receive a virtual resource allocation response message from the VIM. The virtual resource allocation response message indicates information about a target virtual resource on which the VNF instance is to be deployed. The target virtual resource is located in the target virtual resource location area.

The processing unit <NUM> is further configured to instantiate the VNF on the target virtual resource based on the information about the target virtual resource.

In a possible implementation, the receiving unit <NUM> is further configured to receive a VNF instantiation request message from an NFVO before the processing unit <NUM> determines the target virtual resource location area in which the VNF instance is to be deployed. The VNF instantiation request message requests to instantiate the VNF. In this implementation, the QoS attribute of the VNF may be obtained in the following two manners: The VNF instantiation request message carries the QoS attribute of the VNF. Alternatively, the processing unit <NUM> is further configured to obtain the QoS attribute of the VNF from a VNFD before determining the target virtual resource location area in which the VNF instance is to be deployed.

In a possible implementation, the VNF instantiation request message does not trigger a VNF lifecycle management granting request message, or does not carry an affinity rule and/or an anti-affinity rule for deploying the VNF.

In a possible implementation, the VNF is a virtualized multi-access edge application, the QoS attribute is a QoS attribute of the multi-access edge application, the VNF is instantiated in a predetermined edge data center, and the target virtual resource location area is located in the predetermined edge data center. In this example, the QoS attribute may include at least one of the following: a network latency, a throughput, a jitter, and a packet loss rate.

The VNFM provided in this embodiment of this application is capable of performing the actions of the VNFM in the method embodiment shown in <FIG>. An implementation principle and a technical effect thereof are similar, and details are not described herein again.

According to another aspect, an embodiment of this application further provides an NFVO. The NFVO includes a sending unit. The sending unit is configured to send a VNF instantiation request message to a VNFM. The VNF instantiation request message requests to instantiate a VNF.

In a possible implementation, the VNF instantiation request message may carry a quality of service QoS attribute of the VNF.

The NFVO provided in this embodiment of this application is capable of performing the actions of the NFVO in the method embodiment shown in <FIG> or <FIG>. An implementation principle and a technical effect thereof are similar, and details are not described herein again.

<FIG> is a schematic diagram of a structure of a VIM according to an embodiment of this application. As shown in <FIG>, the VIM may include a receiving unit <NUM> and a sending unit <NUM>.

The receiving unit <NUM> is configured to receive a virtual resource allocation request message from a virtualized network function manager VNFM. The virtual resource allocation request message requests to allocate a virtual resource on which a virtualized network function VNF instance is to be deployed. The virtual resource allocation request message carries information about a target virtual resource location area. The target virtual resource location area is a virtual resource location area corresponding to a quality of service QoS attribute of a VNF.

The sending unit <NUM> is configured to send a virtual resource allocation response message to the VNFM. The virtual resource allocation response message indicates information about a target virtual resource. The target virtual resource is located in the target virtual resource location area.

The VIM provided in this embodiment of this application is capable of performing the actions of the VIM in the method embodiment shown in <FIG>. An implementation principle and a technical effect thereof are similar, and details are not described herein again.

<FIG> is a schematic diagram of a structure of an NFVO according to an embodiment of this application. As shown in <FIG>, the NFVO may include a sending unit <NUM> and a receiving unit <NUM>. Optionally, the NFVO may further include a processing unit <NUM>.

In a possible implementation, the sending unit <NUM> is configured to send a virtual resource allocation request message to a virtualized infrastructure manager VIM, where the virtual resource allocation request message requests to allocate a virtual resource on which a VNF instance is to be deployed, and the virtual resource allocation request message carries a QoS attribute of a VNF;.

Alternatively, the processing unit <NUM> is configured to determine, based on a quality of service QoS attribute of a to-be-instantiated virtualized network function VNF and a preset mapping relationship between a QoS attribute and a virtual resource location area, a target virtual resource location area in which a VNF instance is to be deployed;.

In a possible implementation, the processing unit <NUM> is further configured to obtain the QoS attribute of the VNF from a VNFD.

<FIG> is a schematic diagram of a structure of another VNFM according to an embodiment of this application. As shown in <FIG>, the VNFM may include a receiving unit <NUM> and a processing unit <NUM>.

The receiving unit <NUM> is configured to receive a virtualized network function VNF instantiation request message from a network functions virtualization orchestrator NFVO. The VNF instantiation request message requests to instantiate a VNF. The VNF instantiation request message carries information about a target virtual resource. The target virtual resource is located in a target virtual resource location area. The target virtual resource location area is a virtual resource location area corresponding to a QoS attribute of the VNF.

The processing unit <NUM> is configured to instantiate the VNF on the target virtual resource based on the information about the target virtual resource.

The VNFM provided in this embodiment of this application is capable of performing the actions of the VNFM in the method embodiment shown in <FIG> or <FIG>. An implementation principle and a technical effect thereof are similar, and details are not described herein again.

<FIG> is a schematic diagram of a structure of another VIM according to an embodiment of this application. As shown in <FIG>, the VIM may include a sending unit <NUM> and a receiving unit <NUM>.

The receiving unit <NUM> is configured to receive a virtual resource allocation request message from a network functions virtualization orchestrator NFVO. The virtual resource allocation request message requests to allocate a virtual resource on which a virtualized network function VNF instance is to be deployed. The virtual resource allocation request message carries information about a target virtual resource location area. The target virtual resource location area is a virtual resource location area corresponding to a quality of service QoS attribute of a VNF.

The sending unit <NUM> is configured to send a virtual resource allocation response message to the NFVO. The virtual resource allocation response message indicates information about a target virtual resource. The target virtual resource is located in the target virtual resource location area.

<FIG> is a schematic diagram of a structure of still another VIM according to an embodiment of this application. As shown in <FIG>, the VIM may include a processing unit <NUM>, a sending unit <NUM>, and a receiving unit <NUM>.

The receiving unit <NUM> is configured to receive a virtual resource allocation request message sent by a virtualized network function manager VNFM. The virtual resource allocation request message requests to allocate a virtual resource on which a virtualized network function VNF instance is to be deployed. The virtual resource allocation request message carries a quality of service QoS attribute of a VNF.

The processing unit <NUM> is configured to determine, based on the QoS attribute of the VNF and a preset mapping relationship between a QoS attribute and a virtual resource location area, a target virtual resource location area in which the VNF instance is to be deployed.

The sending unit <NUM> is configured to send a virtual resource allocation response message to the VNFM. The virtual resource allocation response message indicates information about a target virtual resource on which the VNF instance is to be deployed. The target virtual resource is located in the target virtual resource location area.

Alternatively, the receiving unit <NUM> is configured to receive a virtual resource allocation request message sent by an NFVO. The virtual resource allocation request message requests to allocate a virtual resource on which a virtualized network function VNF instance is to be deployed. The virtual resource allocation request message carries a quality of service QoS attribute of a VNF. Correspondingly, the sending unit <NUM> is configured to send a virtual resource allocation response message to the NFVO. The virtual resource allocation response message indicates information about a target virtual resource on which the VNF instance is to be deployed. The target virtual resource is located in the target virtual resource location area.

The VIM provided in this embodiment of this application is capable of performing the actions of the VIM in the method embodiment shown in <FIG> or <FIG>. An implementation principle and a technical effect thereof are similar, and details are not described herein again.

<FIG> is a schematic diagram of a structure of still another VNFM according to an embodiment of this application. As shown in <FIG>, the VNFM may include a processing unit <NUM>, a sending unit <NUM>, and a receiving unit <NUM>.

The sending unit <NUM> is configured to send a virtual resource allocation request message to a virtualized infrastructure manager VIM. The virtual resource allocation request message requests to allocate a virtual resource on which a virtualized network function VNF instance is to be deployed. The virtual resource allocation request message carries a quality of service QoS attribute of a VNF.

The receiving unit <NUM> is configured to receive a virtual resource allocation response message from the VIM. The virtual resource allocation response message indicates information about a target virtual resource on which the VNF instance is to be deployed. The target virtual resource is located in a target virtual resource location area. The target virtual resource location area is a virtual resource location area corresponding to the QoS attribute of the VNF.

In a possible implementation, the receiving unit <NUM> is further configured to receive a VNF instantiation request message from a network functions virtualization orchestrator NFVO before the sending unit <NUM> sends the virtual resource allocation request message to the virtualized infrastructure manager VIM. The VNF instantiation request message requests to instantiate the VNF. In this implementation, the QoS attribute of the VNF may be obtained in the following two manners: The VNF instantiation request message carries the QoS attribute of the VNF. Alternatively, the processing unit <NUM> is further configured to obtain the QoS attribute of the VNF from a VNFD before the sending unit <NUM> sends the virtual resource allocation request message to the virtualized infrastructure manager VIM.

An embodiment of this application further provides a communications system, including an NFVO, a VNFM, and a VIM. The NFVO is configured to perform the actions of the NFVO in the foregoing method embodiments, the VNFM is configured to perform the actions of the VNFM in the foregoing method embodiments, and the VIM is configured to perform the actions of the VIM in the foregoing method embodiments. An implementation principle and a technical effect thereof are similar, and details are not described herein again.

It should be noted that, it should be understood that the receiving unit may be a receiver during actual implementation, and the sending unit may be a transmitter during actual implementation. The processing unit may be implemented in a form of software invoked by a processing element, or may be implemented in a form of hardware. For example, the processing unit may be a separately disposed processing element, or may be integrated into a chip of the foregoing apparatus for implementation. In addition, the processing unit may alternatively be stored in a memory of the foregoing apparatus in a form of program code, and is invoked by a processing element of the foregoing apparatus to perform a function of the processing unit. In addition, all or some of the units may be integrated, or may be implemented independently. The processing element herein may be an integrated circuit and has a signal processing capability. In an implementation process, steps of the foregoing method or the foregoing units may be implemented by using a hardware integrated logical circuit in the processing element, or by using instructions in a form of software.

For example, the foregoing units may be one or more integrated circuits configured to implement the foregoing method, for example, one or more application-specific integrated circuits (application-specific integrated circuits, ASICs), one or more microprocessors (digital signal processors, DSPs), or one or more field programmable gate arrays (field programmable gate arrays, FPGAs). For another example, when one of the units is implemented in a form of scheduling program code by a processing element, the processing element may be a general-purpose processor, for example, a central processing unit (central processing unit, CPU) or another processor that can invoke the program code. For still another example, the units may be integrated and implemented in a form of a system-on-a-chip (system-on-a-chip, SoC).

<FIG> is a schematic diagram of a structure of a communications apparatus according to an embodiment of this application. As shown in <FIG>, the communications apparatus may include a processor <NUM> (for example, a CPU) and a memory <NUM>. The memory <NUM> may include a high-speed random access memory (random access memory, RAM), and may further include a non-volatile memory (non-volatile memory, NVM), for example, at least one disk memory. The memory <NUM> may store various instructions to complete various processing functions and implement the method steps of this application. Optionally, the communications apparatus in this application may further include a power supply <NUM>, a communications bus <NUM>, and a communications port <NUM>. The communications bus <NUM> is configured to implement a communication connection between components. The communications port <NUM> is configured to implement connection and communication between the communications apparatus and other peripherals.

In this embodiment of this application, the memory <NUM> is configured to store computer-executable program code. The program code includes instructions. When the processor <NUM> executes the instructions, the instructions enable the processor <NUM> of the communications apparatus to perform the actions of the NFVO in the foregoing method embodiments. An implementation principle and a technical effect thereof are similar, and details are not described herein again.

Alternatively, when the processor <NUM> executes the instructions, the instructions enable the processor <NUM> of the communications apparatus to perform the actions of the VNFM in the foregoing method embodiments. An implementation principle and a technical effect thereof are similar, and details are not described herein again.

Alternatively, when the processor <NUM> executes the instructions, the instructions enable the processor <NUM> of the communications apparatus to perform the actions of the VIM in the foregoing method embodiments. An implementation principle and a technical effect thereof are similar, and details are not described herein again.

All or some of the foregoing embodiments may be implemented by using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, all or some of the embodiments may be implemented in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or the functions according to embodiments of this application are completely or partially generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or another programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (DSL)) or wireless (for example, infrared, radio, or microwave) manner. The computer-readable storage medium may be any usable medium accessible by a computer, or a data storage device, for example, a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a solid-state drive Solid State Disk (SSD)), or the like.

Claim 1:
A VNF instantiation method, wherein the method comprises:
determining (S101), by a virtualized network function manager, VNFM, based on a quality of service, QoS, attribute of a to-be-instantiated virtualized network function, VNF, and a preset mapping relationship between a QoS attribute and a virtual resource location area, a target virtual resource location area comprising target virtual resources in which a VNF instance is to be deployed;
sending (S102), by the VNFM, a virtual resource allocation request message to a virtualized infrastructure manager, VIM, wherein the virtual resource allocation request message requests to allocate a virtual resource on which the VNF instance is to be deployed, and the virtual resource allocation request message carries information about the target virtual resource location area;
receiving (S <NUM>), by the VNFM, a virtual resource allocation response message from the VIM, wherein the virtual resource allocation response message indicates information about a target virtual resource on which the VNF instance is to be deployed, and the target virtual resource is located in the target virtual resource location area; and
instantiating (S <NUM>), by the VNFM, the VNF on the target virtual resource based on the information about the target virtual resource.