Resource switching method, device and system

Abstract

The invention relates to the technical field of communication, in particular to a method, a device and a system for switching resources, which are used for flexibly providing infrastructure resources which most meet user requirements so as to improve the working efficiency of a VNF (Virtual Network Function) or save the user cost. The method is applied to a first manager. The method provided by the embodiment of the invention comprises the steps that the first manager obtains a switching judgment strategy used for judging whether to switch a VNF instance of a virtual network function VNF or not; and after the first manager instantiates a virtualized network function VNF by adopting the first infrastructure resource, monitoring whether a second infrastructure resource conforming to a switching judgment strategy exists in the NFV system for the VNF instance. In a case where a second infrastructure resource is included in the NFV system, the first manager switches an infrastructure resource of a virtualized network function (VNF) instance of a VNF to the second infrastructure resource. The second infrastructure resources are infrastructure resources conforming to the switching judgment strategy.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus and system for switching resources. Background Technology

[0002] Network function virtualization (NFV) technology refers to the instantiation of virtualized network functions (VNFs) so that the VNFs can run on general-purpose physical devices, thereby enabling the implementation of the functions of a network element device through the general-purpose physical devices.

[0003] The current NFV operating mode involves selecting appropriate infrastructure resources based on the user's resource requirements, instantiating the VNF on those resources using the user-provided image, and then distributing configurations. The user includes their resource requirements in a Virtual Network Function Descriptor (VNFD) and provides the VNFD along with the software package to the NFV system. When the user subsequently triggers an instantiation operation, the NFV system allocates available infrastructure resources to the VNF based on the resource description in the user's VNFD, completing the virtual network function instantiation process. Once completed, the VNF instance enters a running state.

[0004] Once a VNF is allocated to the corresponding infrastructure resources, it enters a stable operating state. Aside from scaling up or down, the relationship between the VNF and the infrastructure resources typically remains unchanged.

[0005] However, in practice, the available infrastructure resources allocated to a VNF during instantiation may not be the most suitable infrastructure resources. In this case, continuing to use the available infrastructure resources to instantiate the VNF may result in low VNF efficiency or failure to save costs for the user. Summary of the Invention

[0006] This application provides a method, apparatus, and system for switching resources to flexibly provide infrastructure resources that best meet user needs, thereby improving the efficiency of VNFs or saving user costs.

[0007] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0008] Firstly, embodiments of this application provide a method for switching resources. This method is applied in a first manager and includes: the first manager acquiring a switching decision policy for determining whether to switch a Virtualized Network Function (VNF) instance. After the first manager instantiates the VNF using first infrastructure resources, it monitors whether a second infrastructure resource conforming to the switching decision policy exists for the VNF instance in the NFV system. If the NFV system includes a second infrastructure resource, the first manager switches the infrastructure resource of the VNF instance to the second infrastructure resource. The second infrastructure resource is an infrastructure resource conforming to the switching decision policy.

[0009] In the method provided in this application embodiment, after the first manager instantiates the VNF using the first infrastructure resource, the first manager can monitor whether there is a second infrastructure resource in the NFV system that meets the handover judgment policy for the VNF instance. If there is a second infrastructure resource in the NFV system that meets the handover judgment policy, the first manager can switch the infrastructure resource of the VNF instance from the first infrastructure resource to the second infrastructure resource by switching the infrastructure resource of the VNF instance, so that the VNF runs using the infrastructure resource that meets the user's needs for instantiation, thereby improving the working efficiency of the VNF or saving user costs.

[0010] One possible implementation, in the case of a second infrastructure resource in the NFV system, involves the first manager switching the infrastructure resource of a VNF instance of a Virtualized Network Function (VNF) to the second infrastructure resource. This includes: if the second infrastructure resource exists in the NFV system, the first manager instantiates the VNF using the second infrastructure resource to obtain one or more second VNF instances. The first manager then restores backup information of one or more first VNF ​​instances on the one or more second VNF instances. For example, the backup information includes at least the working progress of one or more first VNF ​​instances. The one or more first VNF ​​instances are VNF instances obtained by instantiating the VNF using the first infrastructure resource.

[0011] One possible implementation involves a first manager instantiating a Virtualized Network Function (VNF) using second infrastructure resources to obtain one or more second VNF instances. This includes: the first manager sending a resource authorization operation request to a second manager. The resource authorization operation request requests authorization to use the second infrastructure resources to instantiate the VNF. The first manager receives a resource authorization operation response from the second manager. The resource authorization operation response instructs the first manager to use the second infrastructure resources to instantiate the VNF. In response to the resource authorization operation response, the first manager instantiates the VNF using the second infrastructure resources to obtain one or more second VNF instances.

[0012] One possible implementation is that the resource authorization operation request includes: the identifier of the second infrastructure resource, the resource information of the second infrastructure resource, the identifier of one or more first VNF ​​instances, and the resource information of the first infrastructure resource.

[0013] In one possible implementation, the method provided in this application embodiment further includes, before the first manager monitors the NFV system for information regarding the existence of a second infrastructure resource for a VNF instance: the first manager obtains first indication information, which indicates the resource matching status of the VNF instance being monitored. After instantiating a VNF using the first infrastructure resource, the first manager subscribes to resource changes in the NFV system from a third manager based on the first indication information. The first manager receives resource change information reported by the third manager. The resource change information is used to indicate the currently available infrastructure resources in the NFV system. The resource change information is used by the first manager to determine whether the NFV system has a second infrastructure resource that meets the handover determination strategy.

[0014] As an example, the first manager can obtain first indication information and a switching decision strategy before instantiating the VNF. For instance, in one possible implementation, before the first manager instantiates the VNF using the first infrastructure resource, the method provided in this application embodiment further includes: the first manager receiving an instantiation request message or a task request message from the second manager or obtaining the VNFD of the VNF, wherein the VNFD and / or the instantiation request message includes a switching decision strategy and the first indication information. The instantiation request message also includes the instantiation information of the VNF. The task request message includes a target task to be executed, and the VNFD includes a switching decision strategy and the first indication information. The target task is used to describe the VNF. The first manager obtains the first infrastructure resource from the third manager according to the instantiation request message or the task request message.

[0015] As an example, after the first manager instantiates the VNF, it can obtain the first indication information and the switching judgment strategy. For example, in one possible implementation, after the first manager instantiates the VNF using the first infrastructure resource, the method provided in this application embodiment further includes: the first manager receiving an update VNF instance request or update task request from the second manager, wherein the update VNF instance request or update task request carries the switching judgment strategy and the first indication information.

[0016] Secondly, embodiments of this application provide a management device that can implement the methods in the first aspect or any possible implementation of the first aspect, and thus also achieve the beneficial effects of the first aspect or any possible implementation of the first aspect. The management device can be a first manager, or an apparatus that supports the first manager in implementing the methods in the first aspect or any possible implementation of the first aspect, such as a chip applied in the first manager. The management device can implement the above methods through software, hardware, or by hardware executing corresponding software.

[0017] As an example, the management device may include a processing module and a communication module, wherein the communication module is used to perform the receiving / transmitting related steps performed by the first manager in the first aspect or any possible implementation of the first aspect described above. The processing module is used to perform the processing related steps performed by the first manager in the first aspect or any possible implementation of the first aspect described above.

[0018] For example, when the management device is a chip or chip system within the first manager, the processing module can be a processor, and the communication module can be a communication interface. For example, the communication interface can be an input / output interface, pins, or circuits. The processing module executes instructions stored in the storage unit to enable the first implementation of a method for switching instance running infrastructure resources as described in the first aspect or any possible implementation of the first aspect. The storage unit can be a storage unit within the chip (e.g., registers, caches, etc.) or a storage unit located outside the chip within the first device (e.g., read-only memory, random access memory, etc.).

[0019] Thirdly, embodiments of this application provide an NFV system, comprising: a first manager and a second manager. The first manager is used to execute a resource switching method described in the first aspect or various possible implementations of the first aspect. The second manager is used to provide a switching decision strategy to the first manager.

[0020] Optionally, the NFV system may also include a third manager, which provides the first manager with information on available infrastructure resources in the NFV system.

[0021] Optionally, the second manager can also provide first instruction information to the first manager. For example, the second manager can carry the first instruction information and / or switch the judgment strategy in the instantiation request message or task request message.

[0022] For example, the first manager could be a VNF manager (VNFM). The second manager could be an NFV orchestrator (NFVO). The third manager could be a virtualized infrastructure manager (VIM), PIM, or CISM.

[0023] Fourthly, embodiments of this application provide a computer program product including instructions that, when executed on a computer, cause the computer to perform a resource switching method described in the first aspect or various possible implementations of the first aspect.

[0024] Fifthly, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, cause the computer to perform a resource switching method as described in any of the possible implementations of the first aspect. The computer may be a first manager.

[0025] In a sixth aspect, embodiments of this application provide a management device for implementing various methods in various possible designs of the first aspect or any of the first aspects described above. The management device may be the first manager described above, or a device containing the first manager, or a component (e.g., a chip) applied to the first manager. The management device includes modules and units corresponding to the methods described above; these modules and units may be implemented in hardware, software, or by hardware executing corresponding software implementations. The hardware or software includes one or more modules or units corresponding to the functions described above. It should be understood that the management device described in the sixth aspect may further include a bus and a memory, the memory being used to store code and data. Optionally, at least one processor communication interface and the memory are coupled to each other.

[0026] It should be understood that the management device described in the sixth aspect above may further include: a bus and a memory, the memory being used to store code and data. Optionally, at least one processor communication interface and the memory are coupled to each other.

[0027] In a seventh aspect, embodiments of this application provide a chip including at least one processor, the processor being configured to read and execute a computer program stored in a memory to perform the method in the first aspect or any possible implementation thereof.

[0028] Optionally, the chip also includes a memory, which is connected to the processor via circuitry or wires.

[0029] Alternatively, the chip may also include a communication interface. The communication interface is used to communicate with other modules outside the chip.

[0030] Any of the devices, computer storage media, computer program products, chips, or communication systems provided above are used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects of the corresponding solutions in the corresponding methods provided above, and will not be repeated here. Attached Figure Description

[0031] Figure 1 This is an NFV system architecture diagram provided in an embodiment of this application;

[0032] Figure 2 This is a flowchart illustrating a method for switching resources provided in an embodiment of this application;

[0033] Figure 3 This is a schematic flowchart illustrating a method for switching resources provided in an embodiment of this application;

[0034] Figure 4 This is a schematic flowchart illustrating another method for switching resources provided in an embodiment of this application;

[0035] Figure 5 This is a schematic diagram of the structure of a management device provided in an embodiment of this application;

[0036] Figure 6 A schematic diagram of the structure of a management device provided in an embodiment of this application;

[0037] Figure 7 This is a schematic diagram of the structure of a chip provided in an embodiment of this application. Detailed Implementation

[0038] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; "and / or" in this text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0039] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0040] Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0041] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0042] It should be understood that in this application, "at least one (item)" means one or more. "More than one" means two or more. "At least two (items)" means two or three or more. "And / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural.

[0043] The character " / " generally indicates that the preceding and following objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any single or multiple items. For example, "at least one of a, b, or c" can be expressed as: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0044] Both "...when" and "if" indicate that a corresponding action will be taken under certain objective circumstances. They are not time limits, nor do they require a judgment action to be taken when the action is taken, nor do they imply any other limitations.

[0045] Before introducing the method for switching infrastructure resources for instance operation provided in the embodiments of the present invention, a brief introduction to the NFV system involved in the resource switching method provided in the embodiments of the present invention will be given first. For example... Figure 1 As shown, Figure 1 This is a block diagram of an NFV system provided in an embodiment of this application.

[0046] like Figure 1 As shown, the NFV system reference architecture involved in the embodiments of this application may include an NFV management and orchestration system (NFV-MANO), one or more operation support systems / business support systems (OSS / BSS) 120, multiple element managers (EM) 130, multiple VNFs 140, and NFV infrastructure (NFVI) 150.

[0047] NFV-MANO 110 may include an NFV orchestrator (NFVO) 111, one or more VNF managers (VNFM) 112, and a VIM 113.

[0048] Optionally, the OSS / BSS may include a network manager (NM) unit. For ease of description, the network management unit may be referred to as an NM unit or NM in the following text. The OSS / BSS is the operator's original management device used to manage various network elements in the network. The various network elements in the network realize network function virtualization through EM, VNF, NFVI, NFVO, VNFM, and VIM.

[0049] OSS / BSS is primarily geared towards telecommunications service operators, providing comprehensive network management and business operation functions, including network management (such as fault monitoring and network information collection), billing management, and customer service management.

[0050] The NFVO (Network Functions Entity) is responsible for deploying, operating, managing, and coordinating VNFs and their corresponding NFVIs, and also manages the lifecycle of NS (Network Nodes). The NFVO has interfaces with VIM (Virtual Instantaneous ...

[0051] VIM serves as the management portal for infrastructure and resources, providing functions such as configuration and maintenance, resource monitoring, alarms, and performance management for infrastructure-related hardware and virtualized resources.

[0052] NFVI is a collective term for the computing, storage, and network resources required for Network Functions Virtualization.

[0053] VNFM enables VNF lifecycle management, including VNF descriptor (VNFD) management, VNF instantiation, VNF instance elastic scaling (including scaling out / up and scaling in / down), VNF instance healing, and VNF instance termination. VNFM also supports receiving elastic scaling policies from NFVO, enabling automated VNF elastic scaling. VNFM manages the lifecycle of each VNF, including invoking VIM and creating, maintaining, or terminating VNFs based on VNFDs; monitoring VNFs; performing network element self-healing and scaling up / down, etc. NFVO connects to VNFM and VIM, and also connects to OSS / BSS via a message bus. NFVO sends configuration information to VNFM based on information sent by OSS / BSS to control VNFM's lifecycle management, and sends configuration information to VIM to control VIM's management of NFVIs. NFVO runs on the NSD (NSDescriptor) of NS (Network Service, not shown in the diagram).

[0054] VIM is primarily responsible for the management of infrastructure layer hardware resources and virtualization resources (including reservation and allocation), monitoring of virtual resource status and fault reporting, and providing a virtualization resource pool for upper-layer applications.

[0055] VNFM has interfaces with EM, VNF, NFVO and VIM, and can communicate directly.

[0056] It should be noted that an NFV system can set up M (M≥1) VNFMs, and each VNFM is responsible for managing the lifecycle of one or more VNFs. Furthermore, the instantiated VNF mentioned in this embodiment of the invention refers to a VNF node that can perform the corresponding functions, such as a node with central processing unit (CPU) resources or graphics processing unit (GPU) resources for AI training.

[0057] EM is used to configure application-related parameters for all VNFs in the NFV system.

[0058] NM is used to manage the lifecycle of NS, such as instantiation, expansion / shrinkage, querying, updating, and termination.

[0059] A VNF can be composed of one or more lower-level VNF components (VNFCs). Therefore, a VNF can be deployed on multiple virtual machines (VMs), with each VM hosting the functionality of one VNFC, or a VNF can be deployed on a single VM.

[0060] NFVI can include a virtual resource layer, a virtualization layer, and a hardware resource layer. The virtual resource layer can include multiple virtual machines (VMs), and may also include virtual storage and virtual networks, etc. Figure 1 (Not shown in the image). The hardware resource layer may include computing hardware, storage hardware, and network hardware, etc. (in...) Figure 1 (Not shown in the image). NFVI connects upwards to VNF, and VNF operates based on the virtual resources contained in NFVI to implement the corresponding network functions. There can be multiple VNFs, and each VNF has a corresponding VNFD (VNF Descriptor), which contains all the information of the VNF.

[0061] The hardware in the hardware resource layer may include dedicated processors or general-purpose processors for providing processing and computing functions, such as CPUs; devices for providing storage capabilities, such as disks or network attached storage (NAS); and switches, routers and / or other network devices.

[0062] The virtual resource layer can be provided to VNFs in the form of virtual machines; for example, one or more virtual machines can form a VNF. The virtualization layer forms a virtual network through the hardware in the hardware resource layer to enable communication between multiple virtual machines. For example, this virtual network can be implemented using technologies such as Virtual Local Area Network (VLAN), Virtual Private LAN service (VPLS), Virtual Extensible Local Area Network (VxLAN), or Network Virtualization Using Generic Routing Encapsulation (NVGRE). The virtualization layer in NFVI abstracts the hardware resources of the hardware resource layer, decoupling the VNF from the physical layer to which the hardware resources belong, and providing virtual resources to the VNF.

[0063] NFV-MANO can be used to monitor and manage VNFs and NFVIs. NFVO can communicate with one or more VNFMs to make resource-related requests, send configuration information to the VNFMs, and collect VNF ​​status information. Additionally, NFVO can communicate with VIMs to allocate resources and / or reserve and exchange configuration and status information for virtualized hardware resources. VNFMs can manage one or more VNFs, performing various management functions such as initializing, updating, querying, and / or terminating VNFs. VIMs can control and manage the interaction of virtual and hardware resources within VNFs and NFVIs. For example, VIMs can perform resource allocation operations to VNFs. VNFMs and VIMs can communicate with each other to exchange virtualized hardware resource configuration and status information.

[0064] It should be noted that in the embodiments of the present invention, NM can specifically be OSS / BSS, or the user interface of OSS / BSS.

[0065] In an NFV system, the party that can receive virtualization requests and perform virtualization processing on the corresponding network services according to the virtualization requests is called the virtualization service provider, and the party that initiates the virtualization request is called the virtualization service requester. The virtualization services can be Internet Protocol Multimedia Subsystem (IMS) network services, Evolved Packet Core (EPC) services, etc., and this application embodiment does not limit this to any particular type.

[0066] The aforementioned virtualization request may include network service descriptor (NSD, also known as NS deployment template) information corresponding to the requested virtualization service. The NSD describes the topology of the network service and the VNFD for each included VNF. Virtual link descriptor (VLD) information is used in the topology information to describe the connections between VNFs. VNFD may include the following information: descriptions of one or more VDUs, descriptions of one or more internal and / or external connection points (CPs), and descriptions of one or more virtual links (VLs). A VDU can be considered a virtual machine with application software installed. The VDU description includes a description of all virtual resources required by that virtual machine. CPs represent connection information on the virtual machine, such as virtual network interface card (vNIC) information, which can be represented using an Internet Protocol (IP) address or a Media Access Control (MAC) address. A VL is a virtual connection within a VNF that connects multiple VDUs, and can be represented by information such as connection type and bandwidth. NFVO can instantiate a VNF based on a VNFD request to a VNFM, such as Figure 1 The VNF shown is shown.

[0067] In this embodiment of the application, "instantiate" and "establish" have the same meaning, both referring to the creation of a network entity. For example, instantiating a VNF means creating a VNF entity.

[0068] With the rise of large-scale Artificial Intelligence (AI) models such as chatGPT, Gemini, and Sora, various industries are hoping to leverage AI for intelligent transformation and improved work efficiency. The construction goals of large-scale intelligent computing centers have reached tens of thousands or even hundreds of thousands of GPUs. Besides basic large-scale models, many application-oriented large or small models have also emerged. These trends have led to a surge in demand for GPUs / DPUs, creating an urgent need to improve computing power utilization given limited computing capacity. Currently, NFV operates by selecting appropriate infrastructure resources based on user resource requirements, instantiating the infrastructure based on the user-provided image, and distributing configurations. Users include their resource requirements in a Virtualized Network Function Descriptor (VNFD) and provide the VNFD along with the software package to the NFV system. When a user subsequently triggers an instantiation operation, the NFV system allocates available resources based on the resource description in the user's VNFD, completing the VNF instantiation process. After completion, the VNF instance enters a running state, and the mapping between instances and resources is not adjusted further. However, in practice, the following scenarios may exist: Suppose a VNF can be instantiated using different infrastructure resources, and the efficiency, cost, etc., of instantiation using different infrastructure resources usually vary. However, during instantiation, it is possible that the data center does not currently have the most suitable infrastructure resource, and other infrastructure resources are used to instantiate the VNF.

[0069] Because the infrastructure resources in the NFV system are constantly changing—for example, new resources may be built or other terminals may release some infrastructure resources—if the original infrastructure resources are continued to be used to instantiate the VNF, it may lead to low VNF efficiency or failure to save costs for users.

[0070] Based on this, this application provides a method for switching resources. In this method, after instantiating a VNF, if it is found that there is a second infrastructure resource in the NFV system that meets the switching judgment policy for the VNF, the first infrastructure resource of the VNF instance of the virtualized network function VNF will be switched to the second infrastructure resource, thereby enabling the VNF to run on a suitable infrastructure resource, improving the efficiency of the VNF or saving costs for the user.

[0071] In this application embodiment, the specific structure of the execution entity of the resource switching method is not particularly limited, as long as it can communicate according to the resource switching method of this application embodiment by running a program that records the code of the resource switching method of this application embodiment. For example, the execution entity of the resource switching method provided in this application embodiment can be a functional module in the first manager that can call and execute the program, or it can be a device applied in the first manager, such as a chip, chip system, integrated circuit, etc. These chips, chip systems, and integrated circuits can be located inside the first manager or can be independent of the first manager, and this application embodiment does not impose any restrictions.

[0072] like Figure 2 As shown, Figure 2 A method for switching resources is provided in an embodiment of this application. The method is applied in a first manager and includes:

[0073] Step 201: The first manager obtains the switching judgment strategy.

[0074] For example, a switching decision policy is used to determine whether to switch the VNF instance of a VNF. For instance, a switching decision policy is used to indicate that if a second infrastructure resource conforming to the switching decision policy exists for the VNF in the NFV system, the infrastructure resource of the VNF instance should be switched. In this embodiment, for ease of description, the infrastructure resource conforming to the switching decision policy is referred to as the second infrastructure resource. The infrastructure resources involved in this embodiment may include hardware resources and / or software infrastructure resources.

[0075] As an example, a VNF can be any network function in an NFV system. The handover determination strategy can be a handover determination strategy specific to the virtualized network function VNF, or the handover determination strategy can be a default general handover determination strategy in an NFV system. This application embodiment does not limit this.

[0076] For example, the switching decision-making strategy can include a time-priority strategy and / or a cost-priority strategy. The time-priority strategy refers to selecting the infrastructure resources that can support faster task completion. For example, using the most energy-intensive and computationally powerful single-board computer to quickly complete AI training tasks.

[0077] Cost-first strategy: This strategy will select more economical infrastructure, such as using CPU resources or GPU resources with lower computing power, while still ensuring that the task can be completed within the target time provided by the user.

[0078] The switching decision strategy may also include necessary information to describe the resources the user expects, such as the expected task completion time and the type of resource board the user expects to use. This information can assist the system in making switching decisions.

[0079] For example, the first manager can obtain the switching decision policy from the second manager. Alternatively, the first manager can obtain the switching decision policy from the VNFD corresponding to the VNF.

[0080] For example, the first manager could be VNFM, and the second manager could be NFVO.

[0081] As an example, the second manager can send a handover decision policy to the first manager before the first manager instantiates the VNF. For instance, the second manager can send an instantiation request message or a task request message to the first manager before the first manager instantiates the VNF. The instantiation request message or task request message includes the handover decision policy, and the instantiation request message also includes the VNF's instantiation information. The task request message includes the target task to be executed, which describes the VNF. The instantiation request message requests the instantiation of the VNF. The VNF's instantiation information may include, for example, the VNF's identifier, the VNFD corresponding to the Virtualized Network Function VNF, etc. Alternatively, the first manager can determine the VNFD based on the VNF's identifier to obtain the handover decision policy.

[0082] As another example, the second manager can send a handover decision policy to the first manager after the first manager instantiates the VNF. For instance, the second manager can send an update VNF instance request or an update task request to the first manager after the first manager instantiates the VNF. The update VNF instance request or update task request carries the handover decision policy. The update VNF instance request or update task request requests to update the infrastructure resources of the VNF instance. The update task request requests to update the VNF instance corresponding to the target task. It is worth noting that the second manager can send the handover decision policy to the first manager both before and after the first manager instantiates the VNF. In this scenario, the handover decision policy sent by the second manager to the first manager before the first manager instantiates the VNF can be the same as or different from the handover decision policy sent by the second manager to the first manager after the first manager instantiates the VNF; this embodiment of the application does not limit this.

[0083] Step 202: After the first manager instantiates the Virtualized Network Function (VNF) using the first infrastructure resource, the first manager monitors whether a second infrastructure resource exists for the VNF instance for the VNF in the NFV system. The second infrastructure resource is an infrastructure resource that meets the handover judgment policy.

[0084] For example, after the first manager instantiates a virtualized network function (VNF) using the first infrastructure resource, the first manager can subscribe to the third manager (e.g., VIM / PIM / CISM) for changes in the infrastructure resources in the NFV system to determine whether a second infrastructure resource exists for the VNF instance for the virtualized network function (VNF) in the NFV system.

[0085] Understandably, after receiving a subscription from the first manager, the third manager can send resource change information to the first manager when infrastructure resources in the NFV system change (new infrastructure resources are added or released). For example, resource change information indicates the availability of infrastructure resources in the NFV system after the change. It is understood that available infrastructure resources are those newly added or released in the NFV system. If the available infrastructure resources include a second infrastructure resource, the first manager determines that the NFV system includes the second infrastructure resource. If the available infrastructure resources do not include the second infrastructure resource, the first manager determines that the second infrastructure resource does not exist in the NFV system.

[0086] As an example, after the first manager instantiates a Virtualized Network Function (VNF) using the first infrastructure resource, if the first manager determines that the first infrastructure resource is not the most suitable infrastructure resource for instantiating the VNF, then the first manager monitors whether there is a second infrastructure resource in the NFV system that meets the handover judgment policy for the VNF instance for the VNF. The first manager's monitoring of whether there is a second infrastructure resource in the NFV system that meets the handover judgment policy can refer to the first manager subscribing to resource changes in the NFV system from the third manager. This allows the third manager to send information about available infrastructure resources to the first manager when it determines that infrastructure resources in the NFV system have changed (new infrastructure resources added or released). It is understood that available infrastructure resources are those newly added or released infrastructure resources in the NFV system.

[0087] It's worth noting that the first infrastructure resource refers to the infrastructure resources allocated by the third manager to the virtualized network function (VNF) when it is initially instantiated. While using the first infrastructure resource to instantiate the VNF can achieve the same functionality, the second infrastructure resource better meets user expectations.

[0088] For example, the first manager typically receives an instantiation request message or task request message from the second manager before instantiating a Virtualized Network Function (VNF). This instantiation request message usually carries the infrastructure resources desired by the user. After receiving the instantiation request message, the first manager can request authorization from the second manager for the instantiation operation. If the first manager receives authorization from the second manager, the second manager sends a resource allocation request to the third manager based on the instantiation request message to request the infrastructure resources for instantiation. At this point, the third manager can allocate infrastructure resources to the VNF according to the resource allocation request from the first manager. However, the NFV system may not currently have the infrastructure resources that meet the user's expectations, but rather have first infrastructure resources. In this case, the third manager can allocate the first infrastructure resources to the VNF. After receiving the first infrastructure resources, the first manager can use them to instantiate the VNF. If the first manager determines that the first infrastructure resource allocated to the Virtualized Network Function (VNF) does not match the infrastructure resource expected by the user, it can be determined that the first infrastructure resource is not the most suitable infrastructure resource for instantiating the VNF. Alternatively, the first manager can also determine through other means that the first infrastructure resource is not the most suitable infrastructure resource for instantiating the VNF. For example, before instantiating the VNF, the first manager may receive a task request message requesting the execution of a target task. In this case, the first manager can also request infrastructure resources from the third manager to instantiate the VNF described by the target task based on the user's request. Suppose that after the third manager selects the first infrastructure resource for the VNF, if the first manager determines that instantiating the VNF using the first infrastructure resource results in a time-consuming VNF runtime, it can be determined that the first infrastructure resource is not the most suitable infrastructure resource for that VNF.

[0089] Step 203: In the case that the NFV system includes a second infrastructure resource, the first manager switches the first infrastructure resource of the VNF instance of the Virtualized Network Function VNF to the second infrastructure resource.

[0090] For example, a user instructs to perform AI training, which requires significant computing power. In this case, the user can send an instantiation request message to the first manager via the second manager to instantiate the Virtualized Network Function (VNF). This instantiation request message specifies that GPUs should be used for instantiation. Upon receiving this request, the first manager can request GPU resources from the third manager for instantiation. However, if the third manager determines that the data center lacks a suitable GPU resource pool, but a CPU resource pool exists for instantiation, the third manager selects a CPU resource pool for the VNF and sends it to the first manager. The first manager can then choose to use the CPU resource pool to instantiate the VNF. After instantiating the VNF using the CPU resource pool as the primary infrastructure resource, the first manager can monitor the NVF system for the emergence of a more suitable secondary infrastructure resource, such as a GPU resource pool (newly built or provided by another user). If a more suitable secondary infrastructure resource appears in the NFF system, the first manager can use the secondary infrastructure resource to re-instantiate the VNF, thus switching the VNF instance.

[0091] In the method provided in this application embodiment, after the first manager instantiates a Virtualized Network Function (VNF) using the first infrastructure resource, the first manager can monitor whether there is a second infrastructure resource in the NFV system that meets the handover judgment policy for the VNF instance. If there is a second infrastructure resource in the NFV system that meets the handover judgment policy, the first manager can switch the infrastructure resource of the VNF instance from the first infrastructure resource to the second infrastructure resource by switching the infrastructure resource of the VNF instance. This allows the VNF to be instantiated using infrastructure resources that meet user needs, thereby improving VNF efficiency or saving user costs.

[0092] In one possible implementation of this application, the process of the first manager instantiating a VNF can be as follows: The VNFM receives a VNF instantiation request message or a task request message; the VNFM begins parsing the Virtualized Network Function Descriptor (VNFD) and obtaining the infrastructure resources required to deploy the VNF. Next, the VNFM sends a Virtual Resource Allocation Request message to the Virtualization Infrastructure Manager (VIM). This message requests the allocation of infrastructure resources for deploying the VNF instance. The message carries instantiation information for the VNF, such as the resource information required to instantiate the VNF. For example, the resource information may include the required number of cores, memory size, chip type, etc. Specifically, the VNFM converts computational information (e.g., computational data volume, data type) into resource information and then sends this information to the VIM. After receiving the Virtual Resource Request message from the VNFM, the VIM generates virtual resource allocation information for the VNFM based on the instantiation information. This information includes information about the virtual resources allocated by the VIM for the VNF instantiation, such as the size of the allocated virtual machine memory. The Virtual Information Modeling (VIM) sends virtual resource allocation information to the Network Functions Virtualization Infrastructure (NFVI), so that the NFVI can provide virtual resources (i.e., first infrastructure resources) for the VNFM to instantiate the VNF. Afterwards, the VIM sends a virtual resource allocation response message to the VNFM. The VNFM receives this virtual resource allocation response message. This message indicates the first infrastructure resource information for the VNF instance where the VNF is deployed. Alternatively, after receiving a VNF instantiation request message or task request message, the VNFM begins parsing the Virtualized Network Function Descriptor (VNFD) to obtain a resource list of virtual resources required for deploying the VNF. Next, the VNFM sends the resource list to the NFVO, and the NFVO sends a virtual resource allocation request message to the VIM based on the resource list. This request message requests the allocation of infrastructure resources for the VNF instance where the VNF is deployed. This request message carries instantiation information for the VNF, such as the resource information required to instantiate the VNF, including the size and data type of the data running the VNF. After receiving the virtual resource request message from the NFVO, the VIM generates virtual resource allocation information based on the instantiation information mentioned above. This virtual resource allocation information includes information about the virtual resources allocated by the VIM for the VNF instantiated by the VNFM, such as the size of the allocated virtual machine memory. The VIM then sends the virtual resource allocation information to the Network Functions Virtualization Infrastructure (NFVI) so that the NFVI can provide virtual resources (i.e., first infrastructure resources) for the VNF instantiated by the VNFM based on the virtual resource allocation information. Afterwards, the VIM sends a virtual resource allocation response message to the NFVO.Upon receiving the virtual resource allocation response message, the NFVO instructs the VNFM to provide information on the first infrastructure resource to be deployed for the VNF instance. This virtual resource allocation response message provides information on the first infrastructure resource to be deployed for the VNF instance.

[0093] VNF Configuration: VNFM configures the VNF according to the template requirements and notifies the Environment Management System (EMS) to manage the VNF. EMS then configures the relevant application parameters for the VNF to ensure its proper functioning. Instantiation Completion: Finally, VNFM notifies NFVO to complete the VNF instantiation process, marking the end of the entire instantiation process.

[0094] In one possible embodiment of this application, the first manager can directly switch the first infrastructure resource of the VNF instance of the Virtualized Network Function (VNF) to the second infrastructure resource after determining that a second infrastructure resource exists.

[0095] In one possible embodiment of this application, after determining the existence of a second infrastructure resource, the method provided in this embodiment may further include: the first manager sending a resource authorization operation request to a second manager. The resource authorization operation request requests authorization to use the second infrastructure resource to instantiate the virtualized network function (VNF). The first manager receives a resource authorization operation response from the second manager, wherein the resource authorization operation response indicates authorization for the first manager to use the second infrastructure resource to instantiate the virtualized network function (VNF). In response to the resource authorization operation response, the first manager instantiates the virtualized network function (VNF) according to the second infrastructure resource to obtain one or more second VNF instances.

[0096] In one possible implementation of this application, after determining the existence of a second infrastructure resource, the first manager may send a resource reservation request to the third manager. The resource reservation request includes a second resource identifier. The resource reservation request requests the third manager to reserve the second infrastructure resource identified by the second resource identifier.

[0097] One possible implementation is that the first instantiation request message includes an identifier of the second infrastructure resource, resource information of the second infrastructure resource, an identifier of one or more first VNF ​​instances, and resource information of the first infrastructure resource.

[0098] For example, the resource information of the primary infrastructure resource could refer to its type, size, and other information. Similarly, the resource information of the secondary infrastructure resource could refer to its type, size, and other information. For instance, taking a C-type board as the primary infrastructure resource, the type of the primary infrastructure resource could refer to whether the board is a CPU or a GPU. Resource information could also include whether the hardware resource uses DPDK or RDMA technologies, such as the GPU's computing power (FLOPS) and the memory's read / write speed.

[0099] In one possible implementation, the resource authorization operation request may also include a second instruction message that indicates the infrastructure resources of the VNF instance for switching virtualized network functions (VNFs).

[0100] One possible implementation is that if the first manager sends a resource authorization operation request to the second manager and receives a resource authorization operation response from the second manager indicating that the infrastructure resources of the VNF instance are refused to be switched, then the first manager will not switch the first infrastructure resource of the VNF instance of the Virtualized Network Function (VNF) to the second infrastructure resource.

[0101] Understandably, after receiving the resource authorization operation request, the second manager can send a first notification message to the first address or OSS. This first notification message is used to prompt whether to switch the infrastructure resources of the VNF instance of the Virtualization Network Function (VNF).

[0102] If the second manager receives a user instruction or an OSS instruction to agree to switch the infrastructure resources of a VNF instance of a Virtualized Network Function (VNF), the second manager sends a resource authorization operation response to the first manager indicating agreement to the switch. If the second manager receives a user instruction not to agree to switch the infrastructure resources of a VNF instance of a Virtualized Network Function (VNF), the second manager sends a resource authorization operation response to the first manager indicating rejection of the switch.

[0103] Optionally, the first notification message may also carry indication information indicating whether to switch the VNF instance of the Virtualized Network Function (VNF).

[0104] In one possible implementation of this application, step 203 can be implemented in the following way:

[0105] When a second infrastructure resource exists in the NVF system, the first manager instantiates a Virtualized Network Function (VNF) based on the second infrastructure resource to obtain one or more second VNF instances. The first manager restores backup information of one or more first VNF ​​instances on the one or more second VNF instances. This backup information includes at least the working progress of the one or more first VNF ​​instances, which are VNF instances obtained by instantiating the Virtualized Network Function (VNF) using the first infrastructure resource.

[0106] Understandably, when the first manager instantiates a Virtualized Network Function (VNF) using the first infrastructure resources, it can obtain one or more first VNF ​​instances. When the first manager instantiates a VNF based on the second infrastructure resources to obtain one or more second VNF instances, the first manager can also back up the working progress of one or more first VNF ​​instances to obtain backup information of one or more first VNF ​​instances.

[0107] Each of the one or more first VNF ​​instances represents a VNF instance that constitutes a virtualized network function VNF or implements a target task. Each of the one or more second VNF instances represents a VNF instance that constitutes a virtualized network function VNF or implements a target task.

[0108] In one possible embodiment of this application, after the first manager restores the backup information of one or more VNF instances on one or more second VNF instances, the method provided in this application may further include: the first manager deleting one or more first VNF ​​instances and releasing first infrastructure resources.

[0109] Specifically, the first manager performs a new instantiation process based on the second infrastructure resources, backing up one or more currently running first VNF ​​instances using a snapshot (used to save the current instance's progress and restore it on one or more second VNF instances), and restoring the snapshot on one or more second VNF instances. Finally, the first infrastructure resources are released.

[0110] In one possible embodiment of this application, before the first manager monitors whether a second infrastructure resource exists for the VNF instance of the Virtualized Network Function (VNF) in the NFV system, the method provided in this application may further include: the first manager obtaining first indication information. The first indication information indicates the resource matching status of the VNF instance being monitored.

[0111] Accordingly, after the first manager instantiates a Virtualized Network Function (VNF) using the first infrastructure resource, it subscribes to the third manager for resource changes within the NFV system based on the first instruction information. For example, the first manager can send a resource subscription request to the third manager. Upon receiving the resource subscription request, the third manager can report the resource change information to the first manager when resources in the NFV system change (e.g., other users release infrastructure resources or new infrastructure resources are added to the NFV system). For example, the resource change information indicates the currently available infrastructure resources in the NFV system. For example, the resource subscription request can carry the demand information for the infrastructure resources to be subscribed, so that the third manager can notify the first manager when it determines that there are infrastructure resources that meet the demand.

[0112] For example, the first manager can obtain the first instruction information by obtaining it from the second manager. For instance, the first instruction information can be carried in an instantiation request message or a task request message, or it can be updated in an instantiation request message or a task request message.

[0113] Alternatively, the first manager reads the first instruction information from the VNF descriptor file (VNFD). The VNFD mainly describes the resource information required to instantiate the VNF, including the VNF's internal connections, deployment model, etc.

[0114] In one possible embodiment of this application, before the first manager instantiates the Virtualized Network Function (VNF) using the first infrastructure resources, the method provided in this application may further include: the first manager receiving a first request message from a second manager. The first request message includes a switching determination policy. Alternatively, the switching determination policy and the first indication information may be carried in the descriptor file (VNFD) of the VNF to be instantiated.

[0115] For example, the second manager can be NFVO.

[0116] For example, the first request message can be an instantiation request message or a task request message. The instantiation request message or task request message includes instantiation information for the Virtualized Network Function (VNF). For instance, the instantiation request message includes the identifier of the VNF instance. The first manager can access the descriptor file (VNFD) of the VNF to be instantiated based on the VNF instance identifier, and read the handover decision policy and first indication information from the VNFD.

[0117] This embodiment does not limit the way the NFVO is triggered to execute the VNF instantiation process. For example, the upper layer (such as the OSS / BSS system) can trigger the NFVO to execute the VNF instantiation process, that is, trigger the NFVO to send a VNF instantiation request message to the VNFM.

[0118] The task request message carries information about the target task, which indicates one or more network functions that implement that target task. This allows the first manager to request the third manager to allocate infrastructure resources to implement those one or more network functions for the target task.

[0119] For example, the first request message could be any message other than an instantiation request message or a task request message. For instance, after determining that the NFV system uses the first infrastructure resources to instantiate a Virtualized Network Function (VNF), the user could trigger the first request message again, which includes a switching decision strategy.

[0120] Optionally, the first request message may also include first instruction information.

[0121] In one possible embodiment of this application, after the first manager instantiates a Virtualized Network Function (VNF) using first infrastructure resources, the method provided in this application can further send a VNF instantiation response message to a second manager. Correspondingly, the second manager receives the VNF instantiation response message. This VNF instantiation response message indicates that the deployment of the VNF instance has been completed.

[0122] In another possible embodiment of this application, after the first manager instantiates the Virtualized Network Function (VNF) using the first infrastructure resources, the method provided in this application involves the first manager obtaining a handover determination policy. For example, after the first manager instantiates the VNF using the first infrastructure resources, the first manager receives a second request message from the second manager, wherein the second request message includes the handover determination policy.

[0123] For example, the second request message could be an update instantiation request message or an update task request message.

[0124] For example, the second request message may be a different request message from the update instantiation request message or the update task request message, such as an update message for the update switching judgment strategy. This application embodiment does not limit this.

[0125] For example, the second request message may also include the first instruction information.

[0126] It is understood that the second manager can send a first request message to the first manager before requesting the instantiation of a Virtualized Network Function (VNF), so that the first manager can obtain the first request message carrying the handover determination policy. After the first manager instantiates the VNF, the second manager can then re-trigger the second request message carrying the handover determination policy. The handover determination policies carried in the first and second request messages can be the same or different; this embodiment does not limit this. When the handover determination policies in the first and second request messages are different, the first manager can determine the infrastructure resources suitable for the VNF instance based on the handover determination policy carried in the second request message.

[0127] As an example, the instantiation request message or task request message may also include address information, which is used to receive notifications sent by the first manager. For instance, the first manager can send a request message requesting authorization for instantiation to the address indicated by the address information.

[0128] For example, when a user determines that they need to instantiate a Virtualized Network Function (VNF) or a target task, the user can send a VNF instantiation request / task request to the NFVO via OSS / BSS.

[0129] Users can add parameter identifiers (i.e., first indication information to indicate the monitoring infrastructure resources) to the VNF instantiation request message / task request message issued by OSS / BSS to indicate the matching status of the monitoring infrastructure resources required for the VNF instance. Add a switching judgment strategy to assist the system in deciding when to switch. Add a URL to receive system resource change notifications.

[0130] In the method provided in this application embodiment, after the first manager instantiates the virtualized network function (VNF) using the first infrastructure resources, it may further include: the first manager sending an instantiation completion response message to the second manager to indicate that the instantiation operation of the virtualized network function (VNF) has been completed.

[0131] In the method provided in this application embodiment, after instantiating the Virtualized Network Function (VNF), the method may further include: a first network element sending an instantiation completion message, the instantiation completion message indicating that the instantiation of the VNF has been completed. Optionally, the instantiation completion message may also carry resource information of a first infrastructure resource and / or identifiers of one or more first VNF ​​instances.

[0132] This allows users to identify the resource information of the first infrastructure resource instantiated by the Virtualized Network Function (VNF) and / or one or more first VNF ​​instances associated with the VNF.

[0133] For example, after a user receives an instantiation completion message, they can trigger a first instruction message to instruct the first manager to monitor the resource matching status of one or more VNF instances identified by the first VNF ​​instance's identifier. Before the first manager instantiates a VNF, the first instruction message instructs the first manager to monitor the VNF instances within the VNF instances of the Virtualized Network Function VNF. This "VNF instance" is a generic concept; that is, if the first manager receives the first instruction message, it can determine that it needs to monitor the resource matching status of the VNF instances after the Virtualized Network Function VNF has been instantiated.

[0134] Understandably, when the first manager instantiates a Virtualized Network Function (VNF) using the first infrastructure resource, the first infrastructure resource may be the infrastructure resource currently available in the NFV system. However, the first infrastructure resource may not be the most suitable infrastructure resource for the Virtualized Network Function (VNF). Therefore, after obtaining one or more first VNF ​​instances, the first manager can monitor whether there is a second infrastructure resource in the NFV system that is more suitable for the Virtualized Network Function (VNF).

[0135] like Figure 3 As shown, Figure 3 A detailed flowchart illustrating a method for switching infrastructure resources during instance execution, provided in this application embodiment, includes:

[0136] Step 301: VNFM obtains the instantiation request message or the compute task request message.

[0137] The instantiation request message or computing task request message carries a monitoring identifier (i.e., the first indication information mentioned above) and a switching judgment strategy.

[0138] The instantiation request message also carries instantiation information for Virtualized Network Functions (VNFs). This VNF instantiation information may include: VNF identifier, VNF instantiation description, and corresponding VNFD parameters. The instantiation request message requests the instantiation of the Virtualized Network Function (VNF). The monitoring identifier is used to indicate the matching status of infrastructure resources for the VNF instance after instantiation. The task request message also carries instantiation information for the target task. The computation task request message is used to indicate the instantiation of one or more network functions associated with the target task. The monitoring identifier is used to indicate the matching status of infrastructure resources for one or more VNF instances after instantiation of one or more network functions associated with the target task.

[0139] Optionally, the instantiation request message or compute task request message may include a VNFD. The VNFD carries a monitoring identifier and a switching decision policy.

[0140] For example, when OSS needs to instantiate a new VNF, it sends an instantiation request message or a compute task request message to VNFM. Furthermore, the sender of the instantiation request message or compute task request message can also be OSS / BSS, EM, NFVO, etc. There is no limitation on who sends the instantiation request message or compute task request message.

[0141] As an example, the method provided in this application embodiment may further include, before step 301: NFVO obtaining an instantiation request message or a computation task request message.

[0142] This embodiment does not limit the method of triggering NFVO to execute the VNF instantiation process. For example, the upper layer (such as OSS / BSS system) can trigger NFVO to execute the VNF instantiation process. As an example, when the OSS / BSS system triggers NFVO to execute the VNF instantiation process, it can also provide an address to receive notifications sent by NFVO.

[0143] VNFM can obtain instantiation request messages or compute task request messages from NFVO. Of course, instantiation request messages or compute task request messages can also be sent by other NFV entities (e.g., received from OSS, EM, or NFVO).

[0144] Step 302: The VNFM sends an authorization instantiation operation request to the NFVO. Correspondingly, the NFVO receives the authorization instantiation operation request from the VNFM.

[0145] For example, the authorization instantiation operation request NFVO authorizes the instantiation operation.

[0146] Step 303: NFVO sends an authorization instantiation operation response to VNFM. Correspondingly, VNFM receives the authorization instantiation operation response.

[0147] After obtaining authorization from NFVO, VNFM directly performs virtual resource scheduling (such as allocation, modification, and authorization of virtual resources) with VIM.

[0148] The automatic creation, monitoring, and scaling of virtual machines support two modes: direct mode and indirect mode. In direct mode, the VNFM directly requests infrastructure resources from the VIM, requiring a direct connection between the VNFM and the VIM. In indirect mode, the VNFM requests infrastructure resources from the VIM through the NFVO. In indirect mode, the NFVO is connected to the VIM, and the VNFM does not need a direct connection. In direct mode, the VNFM calls resources from the VIM; for the NFVO, resource calls are obtained through the VNFM, and it cannot obtain the original information about resource calls itself. In indirect mode, the NFVO calls resources from the VIM; the NFVO can directly obtain resource call information and globally control resource allocation. For NFV deployments in carrier networks, indirect mode is more suitable for the requirements.

[0149] Steps 302 and 303 are optional. In direct mode, after step 303, the NFVO can communicate with the VIM, requesting the VIM to check the availability of the infrastructure resources required by the VNF instance and reserve those resources. For example, the NFVO can generate a resource reservation operation through the Virtual Resource Management Interface. Then, the NFVO sends a resource reservation request to the VIM, requesting the VIM to check the availability of the infrastructure resources required by the VNF instance and reserve those resources. After receiving the request, the VIM checks the availability of the infrastructure resources required by the VNF instance, completes the reservation, and then returns the resource reservation result to the NFVO. The NFVO can inform the VNFM of the successful resource reservation and the specific resource information, such as the information of the first infrastructure resource, through step 303. Next, the VNFM executes step 304 below.

[0150] As an example, steps 302 and 303 above can also be omitted. When executing steps 302 and 303, VNFM can execute step 304 after receiving the authorization instantiation operation response.

[0151] Understandably, in direct mode, after step 303, the VNFM executes step 304 below. In indirect mode, the NFVO requests the VIM to allocate the first infrastructure resources for creating the VNF instance, which are then provided to the VNFM.

[0152] Step 304: VNFM requests VIM / PIM / CISM to allocate the first infrastructure resources for creating the VNF instance.

[0153] For example, the VNFM calls the resource allocation API to request the VIM to allocate the first infrastructure resources for creating the VNF instance. Specifically, the VNFM calls the resource allocation API to send a virtual resource allocation request to the VIM. This virtual resource allocation request is used to request the VIM to allocate the necessary infrastructure resources for creating the VNF instance.

[0154] Before requesting the VIM to allocate the first infrastructure resources for creating the VNF instance, the VNFM can obtain the Virtualized Network Function Description Template (VNFD) of the VNF instance; the VNFM parses the VNFD to determine the virtual resources (e.g., the first infrastructure resources) required to deploy the VNF instance.

[0155] The VNFM can determine the primary infrastructure resources it needs to request based on information about the primary infrastructure resources in the VNFD, such as CPU resources and memory resources, and then send a virtual resource request to the VIM. This virtual resource request to the VIM includes the primary infrastructure resources required to create the VNF instance.

[0156] Specifically, before sending a virtual resource allocation request to the VIM, the VNFM sends a virtual resource query request to the VIM to check if there are any primary infrastructure resources required by the VNFM. Based on the received virtual resource query request, the VIM determines whether it supports the primary infrastructure resources required by the VNFM. If it does, it sends a virtual resource confirmation response message to the VNFM, confirming that it can provide the primary infrastructure resources required by the VNFM. Alternatively, before sending a virtual resource request to the VIM, the VNFM sends a resource reservation request. Upon receiving the resource reservation request from the VNFM, the VIM performs a resource reservation operation and sends a virtual resource reservation response to the VNFM. Or, the VNFM first sends a virtual resource query request to the VIM, and then sends a resource reservation request after receiving a virtual resource confirmation response from the VIM.

[0157] As an example, the above example of VNFM requesting VIM to allocate the first infrastructure resources for creating a VNF instance can also be used in practice. In practice, NFVO can request VIM to allocate the first infrastructure resources for creating a VNF instance, and then NFVO can provide VNFM with the information of the first infrastructure resources.

[0158] Specifically, the VNFM parses the VNFD to determine the virtual resources required to deploy the VNF instance. The VNFM returns a list of virtual resources for deploying the VNF instance to the NFVO; the NFVO determines the virtual resources needed to create the VNF instance based on the virtual resource list and requests the VIM to allocate virtual resources for creating the VNF instance; the VIM allocates the virtual resources needed to create the VNF instance and sends virtual resource information corresponding to the allocated virtual resources to the NFVO; the NFVO sends the virtual resource information to the VNFM to notify the VNFM that the virtual resource configuration is complete; the VNFM creates the VNF instance based on the information obtained from the NFVO that requires the creation of the VNF instance.

[0159] For example, NFVO checks if there are sufficient free resources in the NFV system. NFVO sends a create resource reservation message to VIM. VIM sends a result of reservation message to NFVO. NFVO sends an acknowledgement message (ACK) to VNFM. Optionally, in this step, the acknowledgement message includes the identifier of the VIM that can allocate resources. VNFM sends a resource allocation request message to VIM. This resource allocation request message requests VIM to create and start a virtual machine (VM) according to NFVO's instructions; it carries the VIM identifier and VM parameters. VIM sends an acknowledgement message to VNFM.

[0160] Step 305: VNFM receives information from the first infrastructure resource from VIM / PIM / CISM and instantiates VNF based on the first infrastructure resource to obtain one or more first VNF ​​instances.

[0161] It is worth noting that, in the above embodiment, the example of VNFM requesting VIM to allocate the first infrastructure resources for creating a VNF instance is used as an example. In actual process, NFVO can also request VIM to allocate the first infrastructure resources for creating a VNF instance, and then NFVO provides VNFM with the information of the first infrastructure resources.

[0162] Specifically, VNFM allocates and deploys the virtual resources required for the created VNF instance based on the VNFD corresponding to the VNF instance. This includes allocating virtual storage resources, creating and enabling virtual machines, and establishing connections between virtual machines. After the virtual resource allocation and deployment are completed, the virtual machine guest operating system and VNF application software are installed, loaded, and run according to the VNF package, ultimately realizing the creation of the VNF instance.

[0163] Step 306: The VNFM sends a first response message. This first response message indicates that the instantiation of the VNF has been completed.

[0164] After successfully creating and starting the VNF instance, the VNFM sends a VNF instantiation success response to the EM / NFVO. The EM then configures the VNF instance, that is, it configures information such as business parameters into the instantiated VNF.

[0165] Specifically, after obtaining the first infrastructure resource from the VIM, the VNFM configures the instantiation-related parameters based on the first infrastructure resource. After completing the VNF deployment parameter configuration according to the template, the VNFM notifies the EMS. The EMS adds the VNF as a manageable object, and the EMS configures the application parameters for the VNF. The VNFM queries whether the VNF is available. After the VNFM determines that the VNF is running and can provide services, the VNFM sends the VNF instantiation completion result to the NFVO, carrying the VNF instance identifier and information about the first infrastructure resource occupied by the VNF. The NFVO can return the VNF instantiation completion result to a specified address (for example, when the NFVO receives an instantiation request message or task request message, this message can carry an address) or OSS.

[0166] Through steps 301 to 306 described above, VNFM can obtain one or more first VNF ​​instances of VNF. Afterwards, VNFM can perform the following steps.

[0167] Step 307: Based on the switching judgment strategy and the first indication information, VNFM determines the resource matching status of one or more first VNF ​​instances that need to be monitored.

[0168] For example, after instantiating a VNF using the first infrastructure resource, the VNFM can determine the infrastructure resource matching status of the VNF instance based on the first indication information. If the VNFM determines that the VNF instance is not running on a suitable infrastructure resource, that is, the first infrastructure resource is not the most suitable infrastructure resource for the VNF, then the VNFM monitors whether there are available infrastructure resources in the NFV system.

[0169] Step 308: VNFM can subscribe to VIM for changes in infrastructure resources in the NFV system.

[0170] In this way, once the infrastructure resources in the NFV system change, VIM can report the information of the currently available infrastructure resources in the changed NFV system to VNFM.

[0171] Step 309: VIM reports resource change information to VNFM. VNFM receives resource change information from VIM. This resource change information includes information about the changed available infrastructure resources in the NFV system.

[0172] For example, information about available infrastructure resources could include identifiers of those resources. As an example, for changes to hardware resources, such as additions, reductions, or alterations, VIM supports reporting this information to VNFM. Similarly, for changes to virtual resources, VIM supports reporting this information to VNFM.

[0173] Step 310: VNFM sends a resource reservation request to VIM / PIM / CISM. VIM / PIM / CISM receives the resource reservation request from VNFM.

[0174] The resource reservation request includes an identifier for the infrastructure resource to be reserved. For example, the infrastructure resource to be reserved is the second infrastructure resource that meets the handover judgment strategy.

[0175] Step 311: The VNFM sends a GrantVnfLifecycleOperationRequest to the NFVO. Correspondingly, the NFVO receives the GrantVnfLifecycleOperationRequest from the VNFM.

[0176] For example, VNFM uses the resource granting interface GrantVnfLifecycle to request resource grants from NFVO.

[0177] The resource authorization request includes resource information of the second infrastructure resource, the identifier of the VNF instance, and resource information of the first infrastructure resource.

[0178] Optionally, the resource authorization operation request may also include indication information, which indicates the infrastructure resources of the VNF instance being switched. For example, the lifecycleOperation in the resource authorization operation request is such indication information.

[0179] Optionally, after step 311, the method provided in this application embodiment may further include: Step 311-1, the NFVO may report a resource authorization operation request to the user, OSS, or BSS, so that the user, OSS, or BSS may determine whether to switch the VNF's infrastructure resource to the second infrastructure resource. Step 311-2, the user, OSS, or BSS responds to the resource authorization operation request, for example, by sending a resource authorization operation response to the NFVO, which indicates whether to switch the VNF's infrastructure resource to the second infrastructure resource. Next, the NFVO may perform the following step 312.

[0180] Step 312: NFVO sends a resource grant operation response (GrantVnfLifecycleOperationResponse) to VNFM. Correspondingly, VNFM receives the resource grant operation response from NFVO.

[0181] For example, a resource authorization operation response is used to indicate whether a switchover is allowed or not. For instance, if the resource authorization operation response indicates that a switchover is allowed, it includes the identifier of the VNF instance and the identifier of the second infrastructure resource. Optionally, when the resource authorization operation response indicates that a switchover is allowed, it may also carry a permission indication. When the resource authorization operation response indicates that a switchover is not allowed, it carries information indicating that a switchover is not allowed.

[0182] Step 313: If the resource authorization operation response indicates that it is permissible, VNFM performs a new instantiation operation on the second infrastructure resource to obtain one or more second VNF instances of VNF.

[0183] Understandably, when VNFM performs a new instantiation operation based on the second infrastructure resource, VNFM simultaneously performs a snapshot backup to back up the working progress of one or more first VNF ​​instances. After obtaining one or more second VNF instances by performing a new instantiation operation based on the second infrastructure resource, the working progress of one or more first VNF ​​instances is restored on the one or more second VNF instances, the first infrastructure resource is released, and one or more first VNF ​​instances are deleted.

[0184] For details on Snapshot operations, please refer to the description in ETSI GR NFV-TST 005clause 6.5, which will not be repeated here.

[0185] like Figure 4 As shown, Figure 4 A detailed flowchart illustrating another method for switching the infrastructure resources of an instance, provided in this application embodiment, is shown below. The method includes:

[0186] Steps 401 to 406 can be referred to the descriptions in steps 301 to 306, the difference being that the instantiation request message or task request message in step 401 does not carry the switching judgment strategy and the first indication information.

[0187] Step 407: VNFM receives an update instance message or an update compute task message. The update instance message or update compute task message carries a monitoring identifier and a switchover decision strategy.

[0188] Steps 408 to 414 are described in the same way as steps 307 to 313, and will not be repeated here.

[0189] Optionally, after step 412, the method provided in this embodiment may further include: Step 412-1: The NFVO may report a resource authorization operation request to the user, OSS, or BSS, so that the user, OSS, or BSS may determine whether to switch the VNF's infrastructure resource to the second infrastructure resource. Step 412-2: The user, OSS, or BSS responds to the resource authorization operation request, for example, by sending a resource authorization operation response to the NFVO, which indicates whether to switch the VNF's infrastructure resource to the second infrastructure resource. Next, the NFVO may perform the following step 413.

[0190] It is worth noting that, Figure 3 and Figure 4 The difference is: Figure 3 The instantiation request message / computation task request information / VNFD carries a monitoring identifier and a handover judgment policy. This allows the NFV system to determine whether a new, more suitable secondary infrastructure resource has emerged after the virtualized network function (VNF) has been instantiated. If a more suitable secondary infrastructure resource is found, the system can then re-instantiate the VNF based on that resource. Figure 4 The core idea is that after instantiation or during the execution of a computation task, the user can start monitoring the infrastructure resources by updating the instance / task operation, and re-instantiate based on the second infrastructure resource when a more suitable second infrastructure resource appears.

[0191] The above mainly describes the solutions of the embodiments of this application from the perspective of interaction between various network elements. It is understood that each network element, such as the first manager, includes corresponding structures and / or software modules to execute the above functions in order to achieve them. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0192] This application embodiment can divide functional units according to the first manager in the above-described method example. For example, each function can be divided into its own functional unit, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional unit. It should be noted that the unit division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0193] The above combination Figures 2-4 The methods described in the embodiments of this application have been explained. The management apparatus for executing the above methods, provided in the embodiments of this application, is described below. Those skilled in the art will understand that the methods and apparatus can be combined with and referenced in each other, and the management apparatus provided in the embodiments of this application can execute the steps performed by the first manager in the above analysis method.

[0194] When using integrated units Figure 5 The management device described in the above embodiments is illustrated. The management device may include a communication module 513 and a processing module 512. In an optional implementation, the management device may further include a storage module 511 for storing the program code and data of the management device.

[0195] In one example, the management device is a first manager, or a chip applied within the first manager. In this case, the communication module 513 is used to support communication between the management device and external network elements (e.g., a second manager or a third manager). For example, the communication module 513 is used to perform signal transmission and reception operations of the first manager in the above method embodiments. The processing module 512 is used to perform signal processing operations of the first manager in the above method embodiments.

[0196] In one embodiment of this application, the communication module 513 is used to perform the above embodiments. Figure 2Step 201. Processing module 512, used to support the management device in performing... Figure 2 Steps 202 and 203 in the process.

[0197] The processing module 512 can be a processor or controller, such as a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computational functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, etc. The communication module can be a transceiver, transceiver circuitry, or communication interface, etc. The storage module can be a memory.

[0198] When the processing module 512 is a processor 601 or a processor 605, the communication module 513 is a communication interface 603, and the storage module 511 is a memory 602, the management device involved in this application can be... Figure 6 The management equipment shown.

[0199] Figure 6 The diagram shown is a hardware structure diagram of the management device provided in an embodiment of this application. The structure of the first manager in the embodiments of this application can be referred to as follows. Figure 6 The diagram shows the structure of the management device. The communication device includes a processor 601, a communication line 604, and at least one communication interface. Figure 6 (The example provided uses communication interface 603 as an example.)

[0200] The processor 601 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.

[0201] Communication line 604 may include a path for transmitting information between the aforementioned components.

[0202] Communication interface 603 is used to exchange information with other devices, such as transceivers, for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.

[0203] Optionally, the communication device may also include a memory 602.

[0204] The memory 602 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory may exist independently and be connected to the processor via communication line 604. The memory may also be integrated with the processor.

[0205] The memory 602 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 601. The processor 601 executes the computer execution instructions stored in the memory 602, thereby implementing a resource switching method provided in the following embodiments of this application.

[0206] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0207] In a specific implementation, as one embodiment, the processor 601 may include one or more CPUs, for example... Figure 6 CPU0 and CPU1 in the CPU.

[0208] In a specific implementation, as one example, the communication device may include multiple processors, for example... Figure 6 Processors 601 and 605 are described herein. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor here may refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0209] The steps performed by processors 601 and 605 can refer to the steps performed by processing module 512 described above. The steps performed by communication interface 603 can refer to the steps performed by communication module 513 described above.

[0210] Figure 7 This is a schematic diagram of the structure of chip 70 provided in an embodiment of this application. Chip 70 includes one or more (including two) processors 710 and communication interfaces 730.

[0211] Optionally, the chip 70 also includes a memory 740, which may include read-only memory and random access memory, and provides operation instructions and data to the processor 710. A portion of the memory 740 may also include non-volatile random access memory (NVRAM).

[0212] In some implementations, memory 740 stores elements such as execution modules or data structures, or subsets thereof, or extended sets thereof.

[0213] In this embodiment of the application, the corresponding operation is executed by calling the operation instructions stored in the memory 740 (the operation instructions may be stored in the operating system).

[0214] One possible implementation is that the structure of the first manager is similar, and different devices can use different chips to achieve their respective functions.

[0215] Processor 610 controls the processing operations of the first manager; processor 610 can also be called a central processing unit (CPU).

[0216] Memory 640 may include read-only memory and random access memory, and provides instructions and data to processor 610. A portion of memory 640 may also include NVRAM. For example, in an application, memory 740, communication interface 730, and memory 740 are coupled together via bus system 720, which may include, in addition to data bus, power bus, control bus, and status signal bus, etc. However, for clarity, in Figure 7 The general labeled all buses as Bus System 720.

[0217] The methods disclosed in the embodiments of this application can be applied to or implemented by the processor 710. The processor 710 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in the processor 710 or by instructions in the form of software. The processor 710 may be a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 740. Processor 710 reads the information in memory 740 and, in conjunction with its hardware, completes the steps of the above method.

[0218] In one possible implementation, the communication interface 730 is used to perform... Figure 2 The illustrated embodiment shows the receiving and sending steps of the first manager. Processor 710 is used to execute... Figure 2 The steps of the first manager's processing in the illustrated embodiment.

[0219] On the one hand, a computer-readable storage medium is provided, in which instructions are stored, which, when executed, implement as follows: Figure 2 The functions performed by the first manager.

[0220] On the one hand, a computer program product including instructions is provided, wherein the computer program product includes instructions that, when executed, implement such... Figure 2 The functions performed by the first manager.

[0221] On one hand, a chip is provided for use in a first manager. The chip includes at least one processor and a communication interface, the communication interface and the at least one processor being coupled together. The processor is used to execute instructions to achieve, for example... Figure 2 The functions performed by the first manager.

[0222] This application provides a communication system, which includes a VNFM, an NFVO, and a third manager. The VNFM is used to perform actions such as... Figure 2 The functions performed by the first manager include NFVO, which authorizes the VNFM to instantiate the VNF using either the first or second infrastructure resource. The third manager is used to allocate the first and second infrastructure resources for instantiation of the VNF based on the resource allocation request from the WNFM or NFVO.

[0223] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video disc (DVD); or it can be a semiconductor medium, such as a solid-state drive (SSD).

[0224] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, the disclosure, and the appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0225] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A resource switching method, characterized in that, The method is applied in the first manager, and the method includes: Obtain the switching judgment policy, which is used to determine whether to switch the VNF instance of the Virtualized Network Function (VNF); After instantiating the Virtualized Network Function (VNF) using the first infrastructure resource, monitor whether there is a second infrastructure resource for the VNF instance of the Virtualized Network Function (VNF) in the NFV system. The second infrastructure resource is an infrastructure resource that conforms to the handover judgment strategy. If the second infrastructure resource exists in the NFV system, the infrastructure resource of the VNF instance of the Virtualized Network Function (VNF) is switched to the second infrastructure resource.

2. The method according to claim 1, characterized in that, When the second infrastructure resource exists in the NFV system, switching the infrastructure resource of the VNF instance of the Virtualized Network Function (VNF) to the second infrastructure resource includes: If the second infrastructure resource exists in the NFV system, the virtualized network function (VNF) is instantiated using the second infrastructure resource to obtain one or more second VNF instances of the virtualized network function (VNF). Restore backup information of one or more first VNF ​​instances on the one or more second VNF instances. The backup information includes at least the working progress of the one or more first VNF ​​instances, which are VNF instances obtained by instantiating the virtualized network function VNF using the first infrastructure resources.

3. The method according to claim 2, characterized in that, Before instantiating the Virtualized Network Function (VNF) using the second infrastructure resource to obtain one or more second VNF instances of the VNF, the method further includes: Send a resource authorization operation request to the second manager, the resource authorization operation request requesting authorization to use the second infrastructure resources to instantiate the virtualized network function (VNF); A resource authorization operation response is received from the second manager, the resource authorization operation response instructing the first manager to instantiate the virtualized network function (VNF) using the second basic implementation resource.

4. The method according to claim 3, characterized in that, The resource authorization operation request includes the identifier of the second infrastructure resource, the resource information of the second infrastructure resource, the identifier of the one or more first VNF ​​instances, and the resource information of the first infrastructure resource.

5. The method according to any one of claims 1 to 4, characterized in that, Before monitoring whether a second infrastructure resource exists for the VNF instance of the Virtual Network Function (VNF) in the NFV system, the method further includes: Obtain first indication information, which indicates the resource matching status of the VNF instance of the virtualized network function (VNF) being monitored; Monitoring whether a second infrastructure resource exists for the VNF instance of the Virtualized Network Function (VNF) in the NFV system includes: Based on the first instruction information, subscribe to the resource changes in the NFV system from the third manager; The system receives resource change information from the third manager, which is used to determine whether the NFV system has a second infrastructure resource.

6. The method according to any one of claims 1 to 5, characterized in that, Before instantiating the virtualized network function (VNF) using the first infrastructure resources, the method further includes: The system receives an instantiation request message or a task request message from a second manager, or acquires a VNFD of a Virtualized Network Function (VNF). The instantiation request message includes the handover decision policy and first indication information, and the VNFD includes the handover decision policy and first indication information. The VNFD and / or the instantiation request message also includes instantiation information of the Virtualized Network Function (VNF). The task request message includes a target task to be executed, and the target task is used to describe the Virtualized Network Function (VNF). Based on the instantiation request message or task request message, obtain information about the first infrastructure resource.

7. The method according to claim 5 or 6, characterized in that, After instantiating the Virtualized Network Function (VNF) using the first infrastructure resources, the method further includes: Receive an update VNF instance request or update task request from the second manager, wherein the update VNF instance request or update task request carries the switching judgment strategy and the first indication information.

8. A management device, characterized in that, The management device includes: a communication module and a processing module. The processing module is used to perform the processing action in the method according to any one of claims 1 to 7, and the communication module is used to perform the receiving or sending action in the method according to any one of claims 1 to 7.

9. A management device, characterized in that, The management unit includes a memory and a processor. The memory is used to store instructions, and the processor is used to execute the instructions stored in the memory. Execution of the instructions stored in the memory causes the processor to perform the method according to any one of claims 1 to 7.

10. A chip, characterized in that, The chip includes at least one processor and a communication interface, the communication interface being coupled to the at least one processor, the at least one processor being configured to run computer programs or instructions to implement the method as described in any one of claims 1 to 7, and the communication interface being configured to communicate with other modules outside the chip.

11. An NFV system, characterized in that, include: The system comprises a first manager, a second manager, and a third manager, wherein the first manager is used to execute the method of any one of claims 1 to 7, the second manager is used to provide a switching decision strategy to the first manager, and the third manager is used to report information on available infrastructure resources in the NFV system to the first manager.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed, implement the method of any one of claims 1 to 7.

Images