CN111726241A

CN111726241A - Network resource management method, system, network device and readable storage medium

Info

Publication number: CN111726241A
Application number: CN201910224234.7A
Authority: CN
Inventors: 谢宝国; 巨满昌
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2019-03-22
Filing date: 2019-03-22
Publication date: 2020-09-29
Anticipated expiration: 2039-03-22
Also published as: CN111726241B

Abstract

According to the network resource management method, the system, the network equipment and the readable storage medium provided by the embodiment of the invention, required container resources and/or virtual machine resources are calculated according to the lifecycle management task corresponding to the containerization VNF; performing resource authorization through the NFVO module, and selecting a corresponding CISM/VIM module; and processing container resources and/or virtual machine resources corresponding to the containerization VNF lifecycle management operation through a CISM/VIM module. Therefore, a way of managing container resources when VNF lifecycle management operation is carried out is provided, and the application of the NFV technology is improved.

Description

Network resource management method, system, network device and readable storage medium

Technical Field

Embodiments of the present invention relate to, but are not limited to, the field of communications, and in particular, but not limited to, a network resource management method, system, network device, and readable storage medium.

Background

Network Function Virtualization (NFV) is a software processing technology for carrying other Functions by using general hardware and Virtualization technology, and aims to reduce the cost of expensive equipment of a Network. The NFV decouples software and hardware and abstracts functions, so that functions of network equipment do not depend on special hardware any more, resources can be shared fully and flexibly, rapid development and deployment of new services are realized, and automatic deployment, elastic expansion, fault isolation, self-healing and the like are carried out based on actual service requirements.

As shown in fig. 1, the NFV system architecture defined by the European Telecommunications Standards Institute (ETSI) mainly includes: service Operation Support systems and Management Support platforms (OSS/BSS, Operation-Support System/Business Support System), Virtualized Network Functions (VNF), Network Function Virtualization Infrastructure (NFVI), and Network Function virtualization Management and Orchestration systems (NFV-MANO, VNF-Management and organization). The NFVI is mainly responsible for comprehensively virtualizing hardware resources such as calculation, storage and network and mapping the hardware resources into virtual resources; the VNF implements various conventional physical network functions by using software, runs on the NFVI, and uses virtual resources virtualized by the NFVI. The NFV-MANO is responsible for managing and orchestrating the relationships between VNFs and NFVI and the connectivity between VNFs and/or with other Physical Network Functions (PNFs).

The NFV-MANO includes: a Virtualized Infrastructure Manager (VIM), a Virtual Network Function Manager (VNFM), and a Network Virtualization Function Orchestrator (NFVO). The VIM is responsible for controlling and managing virtualized resources; the VNFM is responsible for lifecycle management of the VNF; NFVO is responsible for orchestration and management of virtual infrastructure, as well as lifecycle management for Network Services (NS).

The micro-service architecture is the development and evolution direction of the NFV technology, and is based on the application of the cloud native technology and the container technology. The container is used as an application packaging technology, defines a standardized application publishing format, and greatly facilitates development, deployment and transplantation of the application. The container adopts technologies such as layered mirror image and centralized mirror image warehouse, which promotes the micro-service transformation of network elements and can accelerate the software development and deployment. The container is introduced, so that the requirement of rapid deployment of the edge computing service can be met, the requirement of the edge computing network element for improving the resource utilization rate can be met, and the requirement of the 5G control plane network for deployment by adopting the container can be met.

Currently, in the NFV standard, how to manage Virtual Machine (VM) resources, such as quota and limit management, resource authorization management, resource allocation and recycling management, etc., during a VNF lifecycle management process, such as instantiation, elastic expansion, self-healing, termination, etc., is defined. After the container is introduced in the NFV standard, the container virtual resources include a container object resource (e.g., POD), a virtual machine resource VM required by the container object resource, and a network resource and a storage resource required by the container object resource. How container virtual resources are managed in the VNF lifecycle management process needs to be specified and defined, but there is no mechanism for managing container resources in the relevant specification.

Disclosure of Invention

The technical problem mainly solved by the network resource management method, system, network device and readable storage medium provided by the embodiments of the present invention is to provide a mechanism for managing container virtual resources in a VNF lifecycle.

To solve the foregoing technical problem, an embodiment of the present invention provides a network resource management method, including:

calculating required container resources and/or virtual machine resources according to the life cycle management task corresponding to the Virtual Network Function (VNF);

the network virtualization function orchestrator NFVO module authorizes resources required during the life cycle management operation of the containerized VNF, and selects a corresponding container management function CISM/virtualization base setting manager VIM module to perform resource operation;

and the CISM/VIM module is used for processing container resources and/or virtual machine resources corresponding to the containerization VNF lifecycle management operation.

An embodiment of the present invention further provides a network resource management system, including:

the resource calculation module is used for calculating required container resources and/or virtual machine resources according to the lifecycle management tasks corresponding to the containerization VNFs;

the NFVO module is used for carrying out resource authorization and selecting a corresponding CISM/VIM module;

The embodiment of the invention also provides network equipment, which comprises a processor, a memory and a communication bus;

the communication bus is used for realizing connection communication between the processor and the memory;

the processor is configured to execute one or more computer programs stored in the memory to implement the steps of the network resource management method described above.

Embodiments of the present invention also provide a computer storage medium, where one or more programs are stored in the computer storage medium, and the one or more programs are executable by one or more processors to implement the steps of the network resource management method.

The invention has the beneficial effects that:

Additional features and corresponding advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.

Drawings

FIG. 1 is a diagram of an ETSI NFV system architecture in the related art;

FIG. 2 is a diagram of an extended ETSI NFV system architecture after adding a CISM;

fig. 3 is a general schematic diagram of supporting management of container virtual resources in a scenario of a common ETSI NFV architecture according to an embodiment of the present invention;

fig. 4 is a general schematic diagram of supporting management of container virtual resources in an extended ETSI NFV architecture scenario according to an embodiment of the present invention;

fig. 5 is a flowchart of a network resource management method according to an embodiment of the present invention;

fig. 6 is a schematic view of container resource management in a VNF instantiation operation process in a CISM-free scenario according to a second embodiment of the present invention;

fig. 7 is a schematic view of container resource management in a VNF instantiation operation process in a CISM scenario according to a third embodiment of the present invention;

fig. 8 is a schematic view of container resource management in a VNF retraction operation process in a CISM-free scenario according to a fourth embodiment of the present invention;

fig. 9 is a schematic view of container resource management in a VNF retraction operation process in a CISM scenario according to a fifth embodiment of the present invention;

fig. 10 is a schematic view of container resource management in a VNF self-healing operation process in a CISM-free scenario according to a sixth embodiment of the present invention;

fig. 11 is a schematic view of container resource management in a VNF self-healing operation process in a scenario with CISM according to a seventh embodiment of the present invention;

fig. 12 is a schematic view of container resource management in a VNF deletion operation process in a CISM-free scenario according to an eighth embodiment of the present invention;

fig. 13 is a schematic view of container resource management in a VNF deletion operation process in a CISM scenario according to a ninth embodiment of the present invention;

fig. 14 is a schematic diagram illustrating a network resource management system according to a tenth embodiment of the present invention;

fig. 15 is a schematic structural diagram of a network device according to an eleventh embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention are described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The embodiment of the present invention provides a method and a system for managing container resources, so that when a containerized VNF performs a lifecycle management operation, needed container resources can be managed without being limited to operations of creating, increasing, decreasing, migrating, and releasing container resources for the containerized VNF, so that the VNF can perform lifecycle management by using the container resources, and a goal of introducing a container into an NFV system is achieved.

The embodiment of the invention corresponds to the first scenario: container resource management without CISM function

The embodiment of the present invention is applied under the NFV architecture to describe how a MANO enhances supported container resource management, please refer to fig. 3. Wherein the NFVO comprises an enhanced NFVO container function module for: 1 container virtual resource authorization; 2, serving as a container virtual machine mapping agent, calculating needed virtual machine resources for container object resources;

the VNFM includes an enhanced VNFM container function module to: 1, serving as a container virtual machine mapping agent, calculating needed virtual machine resources for container object resources; 2, generating a container virtual resource list; 3 container virtual resource request and notification; 4: association of container object resources and virtual machine resources under the same VNF;

the VIM includes an enhanced VIM container function module for: 1 container object resource allocation; 2, the storage resources and the network resources required by the container object resource binding are obtained;

the EM contains an enhanced EM vessel function module for: container application configuration and management;

the second scenario corresponding to the embodiment of the invention: container resource management under CISM function

The embodiment of the present invention is applied to the NFV architecture enhancement scenario, and describes how a MANO enhances supported container resource management in the presence of a CISM container management function, please refer to fig. 4.

Wherein: the NFVO comprises an enhanced NFVO container function module for: 1 container virtual resource authorization; 2, serving as a container virtual machine mapping agent, calculating needed virtual machine resources for container object resources; 3, selecting CISM for VNF life cycle management operation and providing CISMID;

the VNFM includes an enhanced VNFM container function module to: 1 container object and network, storage resource request authorization, allocation and notification; 2, generating a container virtual resource demand;

a CISM function to: 1 container object resource allocation; 2, serving as a container virtual machine mapping agent, calculating needed virtual machine resources for container object resources; 3 association of container object resources and virtual machine resources in the same VNF; 4, the storage resources and the network resources required by the container object resource binding are obtained;

a VIM container function module to: 1, creating virtual machine resources, storage resources and network resources requested by the CISM;

according to the enhancement of the MANO function of the scene, the effective management of the container virtual resources can be supported when the life cycle management of the containerized VNF is carried out, and the life cycle management operation of the containerized VNF is realized.

How to manage the container virtual resources in the containerization VNF lifecycle management process is described below by specific embodiments.

The first embodiment is as follows:

the present embodiment provides a method for managing network resources, please refer to fig. 5, where the method includes:

s11, calculating needed container resources and/or virtual machine resources according to the life cycle management tasks corresponding to the containerization VNFs;

s12, authorizing resources required by the life cycle management operation of the containerized VNF through the NFVO module, and selecting a corresponding CISM/VIM module for resource operation;

and S13, processing container resources and/or virtual machine resources corresponding to the containerization VNF lifecycle management operation through the CISM/VIM module.

In some embodiments, the resources required for the computation may include, according to the lifecycle management task corresponding to the containerized VNF:

and calculating the needed virtual machine resources for the container object resources by using the NFVO module as a container virtual machine mapping agent.

In some embodiments, when in a scenario without CISM functionality, according to the lifecycle management task corresponding to the containerized VNF, calculating the required resources may further include:

and calculating virtual machine resources required by the container object resources through the VNFM module, and generating a container virtual resource list.

In some embodiments, after generating the container virtual resource list, the method may further include:

the VNFM module requests the NFVO module for container virtual resource authorization, carrying a container virtual resource list.

In some embodiments, processing container resources and/or virtual machine resources corresponding to the containerized VNF lifecycle management operations may include:

and the VIM module creates, updates or releases at least one of the container object resource, the virtual machine resource, the storage resource and the network resource according to the container resource list.

In some embodiments, when in a CISM functional scenario, before calculating the required resources according to the lifecycle management task corresponding to the containerized VNF, the method may further include:

selecting a corresponding CISM through an NFVO module;

and the VNFM module sends a request to the CISM, wherein the request carries the container resource requirement.

In some embodiments, selecting, by the NFVO module, a corresponding CISM includes:

the NFVO module selects CISM and provides a corresponding CISMID.

the CISM calculates the needed virtual machine resources according to the needed container object resources;

the CISM requests at least one of the required virtual machine resources, network resources, and storage resources from the VIM module.

In some embodiments, after the VIM receives the CISM-initiated request, at least one of: creating/updating/releasing resources requested by the CISM; wherein, the resources requested by the CISM include at least one of virtual machine resources, storage resources and network resources.

In some embodiments, after the CISM sends the request to the VIM, the method may further include:

the CISM module creates the required container object resources.

In some embodiments, after creating the required resource through the VIM module, the method may further include:

and binding the distributed network resources and/or storage resources with the container object resources through a CISM or VIM module.

In some embodiments, it may further include:

and associating the container object resources under the same VNF with the allocated virtual machine resources through a VNFM module or a CISM module.

In some embodiments, further comprising:

and the container application configuration and management are carried out through the EM module.

In this embodiment, the lifecycle management tasks can include new creation, addition, subtraction, release, and the like.

In some embodiments, based on the instantiation operation, initiating the VNF instantiation request may include:

and verifying the validity of the VNFD packet and the instantiation parameters, and after the verification is passed, initiating a VNF instantiation request.

In some embodiments, before requesting the VNF container resource based on the required container resource, the method may further include:

and analyzing the VNFD and the instantiation parameters, determining the required container resources, and generating a container resource list of the VNF instance.

In some embodiments, parsing the VNFD and instantiation parameters, determining the required container resources may include:

if the instantiation parameters have corresponding VNF resource plans, determining required container resources according to the VNF resources;

and if the instantiation parameters only have container resource requirements, calculating the required container resources according to the container resource requirements.

In some embodiments, after establishing a connection with the VNF in the instantiation, the method may further include:

the VNF is configured and instantiation progress is returned.

In some embodiments, it may further include:

receiving a resilient telescoping operation of the containerized VNF;

initiating a VNF capacity reduction request;

based on the current resource condition, judging whether the VNF is allowed to be subjected to capacity reduction and expansion;

and selecting to execute or not execute the capacity reduction operation on the VNF based on the judgment result.

In some embodiments, determining whether to allow the scaling of the VNF based on the current resource situation may include:

if the contraction and expansion request carries the container virtual resource information, calculating the needed increased or decreased container object resources according to the container virtual resource information, and determining the change condition of the needed virtual machine resources;

if the contraction and expansion request does not carry the container virtual resource information, calculating the container object resources which need to be increased or decreased by the contraction and expansion VNF according to the container resource requirement of elastic expansion, and determining the change condition of the needed virtual machine resources.

In some embodiments, before determining whether to allow the scaling down of the VNF based on the current resource situation, the method may further include:

a VNF companding task is created.

In some embodiments, it may further include:

initiating a VNF self-healing request;

determining resources required by self-healing according to the self-healing request;

and creating container virtual resources required by the VNF self-healing, and performing self-healing operation.

In some embodiments, performing the self-healing operation may further include:

and after the container virtual resource is successfully created, initiating a VNF self-healing resource creation success message, and returning the allocated container virtual resource.

In some embodiments, it may further include:

initiating a VNF termination request;

establishing a VNF termination task and requesting resource authorization for performing VNF termination operation;

and deleting the container virtual resource occupied by the VNF.

According to the network resource management method provided by the embodiment, required resources are calculated according to the corresponding life cycle management task; authorization is carried out through the NFVO module, and a corresponding VIM module is selected; through the VIM module, the required resources are created. Therefore, a way of managing container resources when VNF lifecycle management operation is carried out is provided, and the application of the NFV technology is improved.

Example two

Containerization VNF instantiation (without CISM)

Fig. 6 is a schematic diagram corresponding to an embodiment of the present invention, which mainly describes a process of instantiating a containerized VNF, where when an operator initiates a containerized VNF instantiation operation, NFVO needs to perform an authorization operation on a container virtual resource, and if there is an explicit VNF resource plan, a VNFM needs to generate a container virtual resource list according to the VNF resource plan, where the container virtual resource list includes information of a container object resource, a virtual machine resource, a network resource and a storage resource required by the container object resource. If the instantiation parameters of the VNF only have the requirements of container object resources, storage resources and network resources, the VNFM needs to calculate needed virtual machine resources for the container object resources according to the requirements of the container object resources, and then generates the container virtual resource list. The VIM needs to create a virtual machine resource VM, a storage resource, and a network resource according to the container resource list, then create a container object resource POD, and bind the allocated storage resource and the network resource to the container object resource POD. The VIM returns the allocated container virtual resources to the VNFM, which associates the container object resources and virtual machine resources created for the VNF.

FIG. 6 has the following process flow:

s101: an operator initiates containerization VNF instantiation operation on an operation interface of the NFVO;

s102: the NFVO verifies the validity of the VNFD packet and the instantiation parameters, and after the verification is passed, the NFVO initiates a VNF instantiation request to the VNFM, wherein the VNF instantiation request carries the instantiation parameters and the VNFDID;

s103: the VNFM creates VNF instantiation tasks. The VNFM parses the VNFD and the instantiation parameters, calculates required resources according to VNF resource plans or container resource requirements in the instantiation parameters, and generates a container resource list of the VNF instance, where the container resource list is not limited to include container object resources (such as POD), virtual machine resources (virtual machine specifications, virtual machine number) required by the container object resources, bare machine computing resources, storage resources, network resources, and the like.

If the instantiation parameter has a definite VNF resource plan, the VNFM needs to generate a container virtual resource list according to the VNF resource plan, including information such as container object resources, virtual machine resources, network resources and storage resources required by the container object resources. If the instantiation parameter only has container resource requirements, the VNFM needs to calculate the required container object resources (e.g., POD), the virtual machine resources (virtual machine specifications, virtual machine number) required by the container object resources, the network resources and the storage resources required by the container object resources according to the container object resource requirements, and then generate the container virtual resource list.

S104: the VNFM requests the NFVO to perform container virtual resource authorization, and carries the container virtual resource list in S103;

s105: the NFVO authorizes the container virtual resource, and in an authorization response, the NFVO selects the VIM for the instantiation operation according to the MANO strategy, and returns the VIMID and the TennantID to the VNFM.

S106: the VNFM sends a request for creating VNF container virtual resources to the NFVO;

s107: the NFVO requests the VIM to create container virtual resources required in the container virtual resource list, including creation of container object resources (POD), virtual machine resources (VM), virtual storage, a virtual network card, and a virtual network, mounts the virtual storage and the virtual network card to the container object, connects the virtual network card to the virtual network, and performs operations such as affinity and anti-affinity between different virtual machines.

S108: the VIM creates a virtual machine resource VM, a storage resource and a network resource according to the container virtual resource request of the NFVO, creates a container object resource POD on the virtual machine resource, and then binds the allocated storage resource and the network resource to the container object resource POD.

And the VIM detects that the creation of the container virtual resource is successful, informs the NFVO of a successful creation message, and returns the allocated container virtual resource. The NFVO notifies a successful creation message to the VNFM, and the VNFM associates the container object resource and the virtual machine resource created for the VNF;

s109: the VNFM establishes connection with the VNF in instantiation, the VNF feeds back token to the VNFM, and the VNFM configures instantiation-related business parameters to the VNF; the VNF feeds back the instantiation progress to the VNFM. After the VNF instantiation progress is 100%, the VNF instantiation success is indicated.

S110: after the VNF is successfully instantiated, the VNFM sends a VNF instantiation success message to the NFVO, informs the container virtual resource contained in the VNF, and the NFVO responds.

S111: the NFVO notifies the operator of the instantiation complete message.

S112: after VNF instantiation is completed, the EMS is notified that containerized VNF instantiation is complete. The EMS adds the newly instantiated containerized VNF to the management object, and configures and manages the containerized VNF.

In this flow, when the VNF performs instantiation operation, the VNFM requests container virtual resource authorization from the NFVO, calculates container object resources and virtual machine resources required by the container object resources according to resource requirements in instantiation parameters, and generates a container virtual resource list. The VIM creates virtual machine resources, container object resources, network resources and storage resources, and binds the network resources and the storage resources on the container object resources. After the container virtual resource is successfully created, the VNFM associates the container object resource and the virtual machine resource under the same VNF.

EXAMPLE III

Containerization VNF instantiation (with CISM)

Fig. 7 is a schematic diagram corresponding to a third embodiment of the present invention, which mainly describes a process of instantiating a containerized VNF, where when an operator initiates a containerized VNF instantiation operation, NFVO needs to perform an authorization operation on a container virtual resource, and if there is an explicit VNF resource plan, a VNFM needs to generate a container virtual resource list according to the VNF resource plan, where the container virtual resource list includes information of a container object resource, a virtual machine resource, a network resource and a storage resource required by the container object resource. If only container resource requirements exist, for example, VNF instantiation parameters only include container object resources, storage resources, and network resource requirements, the VNFM needs to send the container resource requirements to the CISM, and the CISM needs to calculate virtual machine resources required for the container object resources according to the container object resource requirements, and then generates the container virtual resource list. And the VIM establishes the needed virtual machine resource VM, storage and network resource according to the CISM requirement and returns a successful establishing message. The CISM needs to create a container object resource POD, bind the allocated storage resource and the network resource to the container object resource POD, and associate the container object resource under the VNF with the virtual machine resource.

Fig. 7 has the following steps:

s201: an operator initiates containerization VNF instantiation operation on an operation interface of the NFVO;

s202: the NFVO verifies the validity of the VNFD packet and the instantiation parameters, and after the verification is passed, the NFVO initiates a VNF instantiation request to the VNFM, wherein the VNF instantiation request carries the instantiation parameters and the VNFDID;

s203: the VNFM creates VNF instantiation tasks. The VNFM analyzes the VNFD and the instantiation parameters, obtains container resource requirements from the instantiation parameters (the VNF resource plans or the container resource requirements can be carried in the instantiation parameters), and sends the container resource requirements to the CISM.

The CISM calculates container object resources (e.g., POD) required by the VNF instance, virtual machine resources (virtual machine specification, virtual machine number) required by the container object resources, and required storage resources and network resources according to the container resource requirements, and generates a container virtual resource list required by the VNF instantiation, where the container virtual resource list is not limited to include the container object resources (e.g., POD), the virtual machine resources (virtual machine specification, virtual machine number) required by the container object resources, bare machine computing resources, storage resources, network resources, and the like. And the CISM returns the generated container virtual resource list to the VNFM.

S204: the VNFM requests the NFVO to perform resource authorization, and carries the container virtual resource list in S203;

s205: and the NFVO authorizes the container resource, selects CISM and VIM for the instantiation operation according to the MANO strategy in the authorization response, and returns CISMID, VIMID and TennantID to the VNFM.

S206: the VNFM sends a request for creating VNF container virtual resources to the NFVO;

s207: the NFVO requests the CISM to create required container virtual resources, including operations of creating a container object (POD), a Virtual Machine (VM), virtual storage, a virtual network card and a virtual network, mounting the virtual storage and the virtual network card to the container object, connecting the virtual network card to the virtual network, and performing affinity and anti-affinity between different virtual machines.

S208: the CISM requests the VIM to create virtual machine resources, storage resources and network resources required by VNF instantiation;

s209: the VIM establishes the needed VM resources, allocates storage resources and network resources, and returns the established virtual resource information to the CISM;

s210: the CISM creates required container object resources on the virtual machine resources, associates the container object resources of the same VNF with the virtual machine resources, and binds the allocated storage resources and the network resources to container object resources POD.

S211: after the container virtual resource is successfully created, the CISM informs the NFVO of a successful creation message, and the NFVO informs the VNFM of the successful creation message;

s212: the VNFM establishes connection with the VNF in instantiation, the VNF feeds back token to the VNFM, and the VNFM configures instantiation-related business parameters to the VNF; the VNF feeds back the instantiation progress to the VNFM. After the VNF instantiation progress is 100%, the VNF instantiation success is indicated.

S213: after the VNF is successfully instantiated, the VNFM sends a VNF instantiation success message to the NFVO, informs the container virtual resource contained in the VNF, and the NFVO responds.

S214: and after the VNF instantiation is completed, informing the EMS of the completion of the instantiation. And the EMS adds the newly instantiated containerized VNF to the management object, and performs service configuration and management on the containerized VNF.

In the process, when the containerization VNF performs instantiation operation, the CISM calculates a container object resource and virtual resources required by the container object resource according to the container resource requirement of the VNFM, and generates a container virtual resource list. The VNFM requests the NFVO for container virtual resource authorization and requests the CISM for creating a container virtual resource. The CISM requests the VIM to create virtual machine resources, storage resources and network resources, then creates container object resources on the basis of the virtual machine resources, and associates the container object resources and the virtual machine resources created for the same VNF.

Example four

Containerized VNF elastic expansion (without CISM)

Fig. 8 is a schematic diagram corresponding to a fourth embodiment of the present invention, which mainly describes an operation process of elastic expansion and contraction of a containerized VNF, where the NFVO or VNFM needs to calculate new or reduced virtual machine resources (VM specifications and quantities) required for new or reduced container object resources according to a requirement of the elastically expanded and contracted container resources. When the VNFM requests the NFVO to newly add or reduce the virtual machine resources and container object resources required to be newly added or reduced to bounce the VNF, the NFVO needs to perform an authorization operation on the container virtual resources that apply for updating. The EMS needs to decide whether to allow containerized VNF shrink operations and update the management object to the containerized VNF.

Fig. 8 has the following steps:

s301: an operator initiates containerization VNF capacity reduction and expansion operation on an operation interface of the NFVO;

s302: the NFVO initiates a VNF capacity reduction request to the VNFM, and can carry the container virtual resources required by capacity reduction. If the NFVO carries the container resource information of the scaling, the NFVO needs to calculate the container object resources that need to be added or subtracted by the scaling VNF, and calculate the change of the virtual machine resources (the information of adding or subtracting VM resources) according to the change information of the container object resources. And then sending the container computing resource POD needing to be changed, the virtual machine resource VM needing to be changed, the corresponding storage resource, the network resource and other resource information to the VNFM.

S303: the VNFM creates a VNF companding task. If the NFVO does not carry the container virtual resource information, in this scenario, the VNFM needs to calculate the container object resources that the scaling VNF needs to increase or decrease according to the requirement of the scaled container resources, and calculates the change of the needed virtual machine resources (the information about increase and decrease of VM resources) according to the change information of the container object resources. Then calculating resource POD of the container to be changed, virtual machine resource VM to be changed, and corresponding resource information such as storage resource and network resource;

the VNFM generates a list of the virtual resources of the shrinkages container for VNF shrinkages, including but not limited to information of the container resources (e.g., POD) added or subtracted, virtual machine resources (virtual machine specification, virtual machine number) corresponding to the container resources, bare computer computing resources, storage resources, network resources, and the like.

S304: the VNFM requests the NFVO to perform resource authorization for scaling and expansion, and carries the list of container virtual resources for VNF zooming in S303, and the authorization request also carries the VIMID where the VNF is located;

s305: and the NFVO checks whether the VIM has enough resources according to the VIMID where the VNF is located and carried in the authorization request. If the resources are sufficient, the same VIMID is returned. If the resource is insufficient, authorization to authorize the container resource is denied.

S306: and the VNFM informs the EMS to perform capacity reduction and expansion, and the EMS determines whether to allow the VNFM to perform the capacity reduction and expansion on the VNF according to the condition that the EMS operates the VNF, the consideration that the service is not influenced and the requirement of avoiding operation conflict.

S307: the VNFM sends a request for creating new VNF container virtual resources or releasing existing VNF container virtual resources to the NFVO according to the VNF zooming operation;

s308: the NFVO requests to create new or release container virtual resources needing to be shrinked and contracted in the VIM, wherein the container virtual resources comprise a container object (POD), a Virtual Machine (VM), virtual storage, a virtual network card and the creation or release of a virtual network, and the binding relationship between the virtual storage, the virtual network card and the container object is updated.

S309: the VIM needs to create or release the container object resource POD, the virtual machine resource VM, the storage resource and the network resource according to the flexible container resource list, and update the binding relationship between the storage resource, the network resource and the container object resource POD. The VIM detects that the virtual resources of the elastic container are successfully created or released, notifies the NFVO of a successful elastic operation message, the NFVO notifies the VNFM of a successful elastic operation message, and the VNFM updates the binding relationship between the container object resources of the VNF and the virtual machine resources;

s310: and the VNFM establishes connection with the VNF in the instantiation, notifies the VNF of the completion of resource processing, configures related parameters of the capacity reduction and expansion, and returns a response to the VNFM. And feeding back an expansion progress to the VNFM, and when the contraction and expansion progress fed back by the VNF is 100%, indicating that the VNF contracts and expands successfully.

S311: after successful VNF scaling, the VNFM sends VNF scaling success message to the NFVO to inform the VNF of virtual resource change and the NFVO responds.

S312: the operator can see the contraction and expansion result on the NFVO interface

S313: and after the VNF finishes the capacity reduction and expansion, informing the EMS that the capacity reduction and expansion is finished. The EMS will update the management object corresponding to the VNF and configure new application parameters according to the architecture needs.

In this process, when the VNF performs a collapsing operation, the VNFM calculates new or reduced container object resources according to the requirement of the collapsing operation on the container object resources, calculates virtual machine resources required to be newly increased or reduced according to a change condition of the container object resources, and generates a collapsed container virtual resource list to request authorization of the collapsed container virtual resources to the NFVO. And the VIM creates or releases the container object resource, the virtual machine resource, the storage resource and the network resource according to the request of the flexible container resource, updates the binding relationship between the container object resource and the storage resource as well as between the container object resource and the virtual machine resource, and updates the association relationship between the container object resource and the virtual machine resource of the VNF by the VNFM.

EXAMPLE five

Containerized VNF elastic expansion (with CISM)

Fig. 9 is a schematic diagram corresponding to the fifth embodiment of the present invention, which mainly describes an operation process of flexible scaling of the containerized VNF, where the NFVO or CISM needs to calculate new or reduced virtual machine resources (VM specifications and quantities) needed for new or reduced container object resources according to the requirement of the flexible scaled container resources. When the VNFM requests the NFVO to newly add or reduce the virtual machine resources and container object resources required to be newly added or reduced to bounce the VNF, the NFVO needs to perform an authorization operation on the container virtual resources that apply for updating. The EMS needs to decide whether to allow containerized VNF shrink operations and update the management object to the containerized VNF.

Fig. 9 has the following steps:

s401: an operator initiates containerization VNF capacity reduction and expansion operation on an operation interface of the NFVO;

s402: the NFVO initiates a VNF capacity reduction request to the VNFM, and can carry the container virtual resources required by capacity reduction. If the NFVO carries the container resource information of the scaling, the NFVO needs to calculate the container object resources that need to be added or subtracted by the scaling VNF, and calculate the change of the virtual machine resources (the information of adding or subtracting VM resources) according to the change information of the container object resources. And then sending the container computing resource POD needing to be changed, the virtual machine resource VM needing to be changed, the corresponding storage resource, the network resource and other resource information to the VNFM.

S403: the VNFM creates a VNF companding task. How to make the NFVO not carry the container virtual resource information, in this scenario, the VNFM needs to generate a container resource change requirement required by VNF retraction, and send the requirement to the CISM.

According to the container resource change requirement, the CISM needs to calculate the container object resources needed to be increased or decreased by the capacity-reducing VNF, and calculates the change of the needed virtual machine resources (the information about the increase and decrease of VM resources) according to the change information of the container object resources. Then calculating resource POD of the container to be changed, virtual machine resource VM to be changed, and corresponding resource information such as storage resource and network resource;

the CISM generates a list of the virtual resources of the shrinkages container for VNF shrinkages, including but not limited to the new or reduced container resource information (such as POD), virtual machine resources (virtual machine specification, virtual machine number) corresponding to the container resources, bare computer computing resources, storage resources, network resources, etc., and then sends the list to the VNFM.

S404: the VNFM requests the NFVO to perform resource authorization for expansion and contraction, and the VNFM carries the newly added container resource list in S403, and the authorization request also carries the cimid and VIMID where the VNF is located;

s405: and the NFVO checks whether the CISM and the VIM have enough resources according to the CISMID and the VIMID where the VNF is located carried in the authorization request. If the resources are sufficient, the same CISMID and VIMID are returned. And if the resources are insufficient, refusing to authorize the newly added container resources.

S406: and the VNFM informs the EMS to perform capacity reduction and expansion, and the EMS determines whether to allow the VNFM to perform the capacity reduction and expansion on the VNF according to the condition that the EMS operates the VNF, the consideration that the service is not influenced and the requirement of avoiding operation conflict.

S407: the VNFM sends a request for zooming VNF container virtual resources to the NFVO;

s408: the NFVO requests the CISM to create new or release container virtual resources which need to be shrinked, wherein the container virtual resources comprise a container object (POD), a Virtual Machine (VM), virtual storage, a virtual network card and the creation or release of a virtual network, and the binding relationship between the virtual storage, the virtual network card and the container object is updated.

S409: the CISM requests virtual machine resources, network resources and storage resources needing to be shrinked from the VIM;

s410: the VIM creates needed VM resources or releases the existing VM resources, updates storage resources and network resources, and then returns a resource shrinking completion message to the CISM;

s411: and the CISM creates or releases the container object resource POD which needs to be shrinked, updates the association relation between the container object resource and the virtual machine resource of the same VNF, and updates the binding relation between the storage resource, the network resource and the container object resource POD.

S412: after the CISM zooming operation is completed, informing the NFVO of a successful resource zooming and expanding message, and informing the VNFM of a successful resource zooming and expanding message by the NFVO;

s413: and the VNFM establishes connection with the VNF in the instantiation, notifies the VNF of the completion of resource processing, configures related capacity expansion parameters, and returns a response to the VNFM. And feeding back a contraction and expansion progress to the VNFM, and when the expansion progress fed back by the VNF is 100%, indicating that the VNF is successfully expanded.

S414: after successful VNF scaling, the VNFM sends VNF scaling success message to the NFVO to inform the VNF of virtual resource change and the NFVO responds.

S415: the operator can see the contraction and expansion result on the NFVO interface

S416: and after the VNF finishes the capacity reduction and expansion, informing the EMS that the capacity reduction and expansion is finished. The EMS will update the management object corresponding to the VNF and configure new application parameters according to the architecture needs.

In this flow, when the VNF performs a collapsing operation, the VNFM requests the NFVO for authorization of the container virtual resource that needs to be collapsed, and requests the CISM to create or release the container virtual resource for collapsing. And the CISM calculates virtual machine resources required to be newly added or released according to the requirements of the zooming operation on the container object resources, generates a container virtual resource list, requests the VIM to create or release the container object resources, the virtual machine resources required to be created or released, the storage resources and the network resources, and re-associates the mapping relation between the container object resources and the created virtual machine resources.

When the VNF carries out the zooming operation, the CISM calculates new or reduced container object resources according to the requirements of the zooming operation on the container object resources, calculates new or reduced virtual machine resources according to the change condition of the container object resources, and generates a virtual resource list of a zooming container to request the NFVO for authorizing the zoomed container virtual resources. And the VIM creates or releases virtual machine resources, storage resources and network resources according to the resource request of the elastic container. After the VIM resource retraction is completed, the CISM creates or releases the container object resources required by the retraction, updates the binding relationship between the container object resources and the storage resources and the network resources, and updates the association relationship between the container object resources of the VNF and the virtual machine resources.

EXAMPLE six

Containerized VNF self-healing (without CISM)

Fig. 10 is a schematic diagram corresponding to a sixth embodiment of the present invention, which mainly describes an operation process of containerized VNF self-healing, where when a resource occupied by a VNF fails, service performance of the VNF may be degraded, and an EMS and the VNF may initiate a VNF self-healing process. In the VNF self-healing operation, the VNFM needs to calculate the required container object resources POD and virtual machine resources (VM specifications and quantities) required by the container object resources according to container resource requirements of the VNF self-healing, and generate a container virtual resource list of the VNF self-healing. The container resource list is not limited to include the container object resource POD, the VM resource required by the POD, the storage resource, the network resource, and the like. When the VNFM requests the NFVO for authorization of virtual machine resources and container object resources required for VNF self-healing, the NFVO needs to perform authorization operation on the applied resources, and requests the VIM to allocate resources in the container virtual resource list. The VIM establishes virtual machine resources, network resources and storage resources required by the VNF self-healing, establishes container object resources required by the VNF self-healing, binds the distributed storage resources, network resources and container object resources, informs VNFM and NFVO of successful VNF self-healing resource establishment results, and associates the container object resources and the virtual machine resources under the self-healing VNF by the VNFM to complete the VNF self-healing operation.

Fig. 10 has the following steps:

s501: the VNF or the EMS judges whether to initiate a VNF self-healing request according to the basis of the service, the performance index and the like;

s502: the VNF or the EMS carries out self-healing operation on the request VNFM, and the VNFM returns a self-healing VNF operation response;

s503: the VNFM informs the NFVO that the VNF is about to be self-healed, and the NFVO responds;

s504: the VNFM creates a VNF self-healing task. The VNFM needs to calculate container computing resources (POD) required by the self-healing operation of the VNF, virtual machine resources required by the POD, corresponding storage resources and network resources, and forms a container resource list for the self-healing of the VNF; the container resource list is not limited to include container object resources (such as POD), virtual machine resources (virtual machine specification, virtual machine number) required by the container object resources, bare computer computing resources, storage resources, network resources, and the like.

S505: the VNFM requests the NFVO to perform resource authorization of the VNF self-healing operation, and the VNFM carries the container resource list in S504, and the authorization request also carries the VIMID where the VNF is located;

s506: and the NFVO checks whether the VIM has enough resources according to the VIMID where the VNF is located and carried in the authorization request. If the resources are sufficient, the same VIMID is returned. If the resources are not sufficient, authorization is denied for container resources needed for VNF self-healing.

S507: the VNFM initiates a request of VNF self-healing operation to the NFVO;

s508: the NFVO requests the creation of container virtual resources required by the VNF self-healing from the VIM, including the creation of a container (POD), a Virtual Machine (VM), virtual storage, a virtual network card, and a virtual network, mounts the virtual storage and the virtual network card to a container object, connects the virtual network card to the virtual network, and performs operations such as affinity and anti-affinity between different virtual machines.

S509: the VIM creates a virtual machine resource VM, a storage resource and a network resource according to the container virtual resource request of the NFVO, creates a container object resource POD on the virtual machine resource, and then binds the allocated storage resource and the network resource to the container object resource POD.

And the VIM detects that the creation of the container virtual resources is successful, informs the NFVO of a VNF self-healing resource creation success message, and returns the allocated container virtual resources. The NFVO notifies a successful creation message to the VNFM, and the VNFM associates the container object resource and the virtual machine resource created for the VNF;

s510: after the VNF self-healing operation is successful, the VNFM sends a VNF self-healing success message to the NFVO to notify the NFVO that the container virtual resources included in the VNF self-healing are allocated, and the NFVO responds.

S511: the VNFM establishes connection with the VNF and the EMS, and informs the VNF of successful self-healing.

In this process, when the VNF performs self-healing operation, the container object resource and the virtual machine resource required by the container object resource are calculated according to the VNF self-healing resource requirement, and a container virtual resource list for VNF self-healing is generated. The VIM creates virtual machine resources, container object resources, network resources and storage resources required by the VNF self-healing, and binds the network resources and the storage resources on the container object resources. After the container virtual resource is successfully created, the VNFM associates the container object resource and the virtual machine resource under the same VNF.

EXAMPLE seven

Containerized VNF self-healing (with CISM)

Fig. 11 is a schematic diagram corresponding to the seventh embodiment of the present invention, which mainly describes an operation process of elastic scaling of a containerized VNF, where when a failure occurs in a resource occupied by the VNF, service performance of the VNF may be degraded, and the EMS and the VNF may initiate a self-healing process of the VNF. In the VNF self-healing operation, the VNFM requests the CISM for the container resource of the VNF self-healing, and carries the container resource requirement of the VNF self-healing. The CISM needs to calculate the required container object resource POD and the virtual machine resource (VM specification and quantity) required by the container object resource according to the container resource requirement of the VNF self-healing, and generate a container virtual resource list of the VNF self-healing. The container resource list is not limited to include the container object resource POD, the VM resource required by the POD, the storage resource, the network resource, and the like. When the VNFM requests the NFVO for authorization of virtual machine resources and container object resources required for VNF self-healing, the NFVO needs to perform authorization operation on the applied resources, and requests the CISM to allocate resources in the container virtual resource list. The CISM requests the VIM to allocate virtual machine resources, network resources and storage resources required by the VNF self-healing, allocates container object resources required by the VNF self-healing, binds the storage resources, the network resources and the container object resources allocated by the VIM, and associates the container object resources and the virtual machine resources under the VNF self-healing. And the CISM informs the successful resource creation result of the VNF resource to the VNFM and the NFVO to complete the self-healing operation of the VNF.

FIG. 11 has the following process flow:

s601: the VNF or the EMS judges whether a VNF self-healing request is initiated;

s602: the VNF or the EMS requests the VNFM to perform self-healing operation, and the VNFM returns a self-healing VNF operation response;

s603: the VNFM informs the NFVO that the VNF is about to be self-healed, and the NFVO responds;

s604: the VNFM creates a VNF self-healing task. The VNFM needs to calculate a container computing resource POD required by the VNF self-healing operation, virtual machine resources required by the container POD, corresponding storage resources and network resources, and forms a container resource list;

s605: the VNFM requests the NFVO to perform resource authorization of the VNF self-healing operation, and carries the container resource list in S404, and the authorization request also carries the cimid and VIMID where the VNF is located;

s606: and the NFVO checks whether the CISM and the VIM have enough resources according to the CISMID and the VIMID where the VNF is located carried in the authorization request. If the resources are sufficient, the same CISMID and VIMID are returned. If the resources are not sufficient, authorization is denied for container resources needed for VNF self-healing.

S607: the VNFM initiates a request of VNF self-healing operation to the NFVO;

s608: the NFVO requests the creation of container virtual resources required by the VNF self-healing from the VIM, including the creation of a container (POD), a Virtual Machine (VM), virtual storage, a virtual network card, and a virtual network, the virtual storage and the virtual network card are mounted to the virtual machine, the virtual network card is connected to the virtual network, and the affinity and the anti-affinity between different virtual machines are performed.

S609: the CISM needs to create a container object resource POD according to the container resource list, calculate required VM resources, update the container resource list, add virtual machine resources in the container resource list and then send the virtual machine resources to the VIM;

s610: the VIM establishes needed VM resources and allocates storage resources and network resources;

s611: the CISM uses the VM resources to create the required container object resources, associates the container object resources of the same VNF with the virtual machine resources, and binds the allocated storage resources and the network resources to the container object resources POD.

S612: the VIM detects that the creation of the virtual resource of the newly added container is successful, informs the NFVO of a successful creation message, and the NFVO informs the NFVM of the successful creation message;

s613: after the VNF is successfully self-healed, the VNFM sends a VNFVNF self-healing success message to the NFVO to notify the NFVO that the container virtual resources included in the VNF self-healing are allocated, and the NFVO responds.

S614: the VNFM establishes connection with the VNF and the EMS, and informs the VNF of successful self-healing.

In this flow, when the VNF performs the self-healing operation, the VNFM requests the CISM for the container virtual resource required by the VNF for self-healing according to the container resource requirement of the VNF for self-healing. And the CISM calculates the container object resources and the virtual machine resources required by the container object resources according to the VNF self-healing resource requirements, and generates a container virtual resource list for VNF self-healing. And the VIM establishes virtual machine resources, network resources and storage resources required by the VNF self-healing, and binds the network resources and the storage resources on the container object resources. And after the virtual machine resources are successfully established, the CISM establishes the container object resources on the virtual machine. After the container virtual resource is successfully created, the VNFM associates the container object resource and the virtual machine resource under the same VNF.

Example eight

Containerized VNF termination (without CISM)

Fig. 12 is a schematic diagram corresponding to an eighth embodiment of the present invention, which mainly describes an operation process of a containerization VNF termination flow. In the VNF instance deletion operation, the VNFM needs to notify the NFVO of the container virtual resource list of the VNF instance, and apply for a container resource deletion authorization to the NFVO. The container resource list includes container object resources POD, VM resources required by POD. Storage resources, network resources, and the like. The NFVO needs to perform authorization operation on the released resources, and requests the VIM to release the resources in the container virtual resource list. The VIM executes the release of the container virtual resource occupied by the VNF instance, and notifies the release result to the VNFM and the NFVO.

Fig. 12 has the following steps:

s702: the NFVO initiates a VNF termination request to the VNFM.

S703: and the VNFM creates a VN termination task, generates a task ID and returns a response message to the NFVO. (ii) a

S704: the VNFM requests the NFVO to perform resource authorization of VNF termination operation, the VNFM carries the container virtual resource list occupied by the VNF, and the authorization request also carries the VIMID where the VNF is located;

s705: and the NFVO authorizes the VNF resource to terminate according to the resource current state in the VIM according to the VIMID where the VNF is located and carried in the authorization request.

S706: the VNFM informs the EMS of carrying out VNF termination operation, and the EMS determines whether to allow the VNFM to terminate the VNF or not on the premise of not influencing the service according to the condition that the EMS operates the VNF and the requirement of avoiding operation conflict.

S707: the VNFM sends a request for deleting the VNF container virtual resources to the NFVO;

s708: the NFVO requests the VIM to delete the virtual resources of the container occupied by the VNF, including virtual resources such as a container object resource (POD), a Virtual Machine (VM), virtual storage, a virtual network card, and a virtual network.

S709: and the VIM executes resource deletion, releases the virtual machine resources, the storage resources and the network resources occupied by the VNF instance, and releases the container object resources. After detecting that the VNF container virtual resources are successfully deleted, the VIM notifies the NFVO of a VNF container virtual resource deletion success message, the NFVO notifies the VNFM of a deletion success message, and the VNFM deletes the association relationship between the VNF container object resources and the virtual machine resources;

s710: after the VNF instance is successfully deleted, the VNFM sends a VNF instance deletion success message to the NFVO to notify that the container virtual resource occupied by the VNFI has been successfully deleted, and the NFVO responds.

S711: the operator can see the successful result of VNFI deletion on the NFVO interface

S712: after the deletion of the VNF instance is completed, the VNFM notifies the EMS VNFI of the completion of the deletion. The EMS will update the management object and delete the VNFI in the management object.

In this flow, when the VNF performs the deletion operation, the VNFM requests the NFVO for container virtual resource authorization, and the VNFM requests the NFVO for deletion of the container virtual resource occupied by the VNF instance. And after receiving the VNF resource deletion request of the NFVO, the VIM deletes the container object resource, the virtual machine resource, the network resource and the storage resource occupied by the VNF instance, and notifies the NFVO and the VNFM. And the VNFM deletes the association relation between the container object resource and the virtual machine resource under the VNF.

Example nine

Containerized VNF termination (with CISM)

Fig. 13 is a diagram illustrating a ninth embodiment of the present invention, which mainly describes an operation process of a containerization VNF termination procedure. In the VNF instance deletion operation, the VNFM needs to notify the NFVO of the container virtual resource list of the VNF instance, and apply for a container resource deletion authorization to the NFVO. The container resource list comprises container object resources POD, VM resources, storage resources, network resources and the like required by the POD. The NFVO needs to perform authorization operation on the released resources, and requests the CISM to release the resources in the container virtual resource list. The CISM releases the container object resource POD occupied by the VNF, and then requests the VIM to release the virtual resource occupied by the VNF instance. And the VIM executes the release of the container virtual resource occupied by the VNF instance and notifies the release result to the CISM, the VNFM and the NFVO.

Fig. 13 has the following S:

s801: the operator creates a VNF termination request at the NFVO interface.

S802: the NFVO initiates a VNF termination request to the VNFM.

S803: and the VNFM creates a VN termination task, generates a task ID and returns a response message to the NFVO. (ii) a

S804: the VNFM requests the NFVO to perform resource authorization of VNF termination operation, the VNFM carries the container resource list occupied by the VNF, and the authorization request also carries CISMID and VIMID where the VNF is located;

s805: and the NFVO authorizes the VNF resources to terminate according to the CISMMID where the VNF is located and the current resource status in the CISM and the VIM, wherein the CISMMID is carried in the authorization request.

S806: the VNFM informs the EMS of carrying out VNF termination operation, and the EMS determines whether to allow the VNFM to terminate the VNF or not on the premise of not influencing the service according to the condition that the EMS operates the VNF and the requirement of avoiding operation conflict.

S807: the VNFM sends a request for deleting the VNF container virtual resources to the NFVO;

s808: the NFVO requests the CISM to delete the container virtual resources occupied by the VNF, including virtual resources such as a container (POD), a Virtual Machine (VM), virtual storage, a virtual network card, and a virtual network.

S809: and the CISM executes the deletion of the container object resources occupied by the VNF and then notifies the VIM to delete the virtual machine resources, the storage resources and the network resources occupied by the VNF instance. And notifying the CISM after the VIM is deleted.

S810: after the deletion of the container virtual resources occupied by the VNF instance is successful, the CISM informs the NFVO of a successful deletion message of the VNF container virtual resources, the NFVO informs the VNFM of the successful deletion message, and the VNFM deletes the association relationship between the container object resources and the virtual resources under the VNF;

s811: after the VNF instance is successfully deleted, the VNFM sends a VNF instance deletion success message to the NFVO to notify that the container virtual resource occupied by the VNF instance is successfully deleted, and the NFVO responds.

S812: the operator can see the successful result of VNFI deletion on the NFVO interface

S813: after the deletion of the VNF instance is completed, the VNFM notifies the EMS VNFI of the completion of the deletion. The EMS will update the management object and delete the VNFI in the management object.

In this flow, when the VNF performs the deletion operation, the VNFM requests the NFVO for a container virtual resource deletion authorization, and the VNFM requests the NFVO for deletion of the container virtual resource occupied by the VNF instance. After receiving the VNF resource deletion request of the NFVO, the CISM deletes the container object resource occupied by the VNF instance, notifies the VIM to delete the virtual machine resource, the network resource, and the storage resource occupied by the VNF instance, and then notifies the NFVO and the VNFM. And the VNFM deletes the association relation between the container object resource and the virtual machine resource under the VNF.

Example ten

Referring to fig. 14, the present embodiment provides a network resource management system, including:

the NFVO module 141 is configured to authorize a resource required for the life cycle management operation of the containerized VNF, and select a corresponding container management function CISM/virtualization infrastructure setup manager VIM module to perform the resource operation;

the CISM144/VIM module 142 is configured to process container resources and/or virtual machine resources corresponding to the containerization VNF lifecycle management operation.

In some embodiments, the resource computation module includes NFVO module 141, and NFVO module 141 is further to: as a container virtual machine mapping agent, needed virtual machine resources are calculated for container object resources. In this embodiment, the resource calculation module includes an NFVO module 141, which indicates that the NFVO module 141 can implement functions of the resource calculation module, but does not indicate a dependency relationship between the resource calculation module and the NFVO module 141, and this embodiment is not limited thereto; the same is true of the resource calculation modules hereinafter including the VNFM module 143.

In some embodiments, the resource calculation module further includes a VNFM module 143 for calculating virtual machine resources required for the container object resources and generating a container virtual resource list when in the CISM-less functional scenario.

In some embodiments, the VNFM module 143 is further configured to request a container virtual resource authorization from the NFVO module 141, carrying a list of container virtual resources.

In some embodiments, VIM module 142 is further configured to create, update, or release at least one of a container object resource, a virtual machine resource, a storage resource, and a network resource from the list of container resources.

In some embodiments, when in a CISM functional scenario, NFVO module 141 is further configured to select a corresponding CISM;

the VNFM module 143 is further configured to send a request to the CISM144, where the request carries a container resource requirement.

In some embodiments, NFVO module 141 may also be used to: the CISM is selected and the corresponding cimid is provided.

In some embodiments, CISM144 may also be used to:

calculating needed virtual machine resources according to needed container object resources;

at least one of the required virtual machine resources, network resources, and storage resources are requested from the VIM module 142.

In some embodiments, the VIM may also be used to: after receiving the request initiated by the CISM144, at least one of: creating/updating/releasing resources requested by the CISM; wherein, the resources requested by the CISM include at least one of virtual machine resources, storage resources and network resources.

In some embodiments, the CISM module 144 is further configured to: the required container object resources are created.

In some embodiments, it may further include:

the allocated network resources and/or storage resources are bound with the container object resources by the CISM144 or VIM module 142.

In some embodiments, it may further include:

and associating the container object resource under the same VNF with the allocated virtual machine resource through the VNFM module 143 or the CISM 144.

In some embodiments, an EM module 145 may also be included for container application configuration and management. According to the network resource management method provided by the embodiment, required resources are calculated according to the corresponding life cycle management task; authorization is carried out through the NFVO module, and a corresponding VIM module is selected; through the VIM module, the required resources are created. Therefore, a way of managing container resources when VNF lifecycle management operation is carried out is provided, and the application of the NFV technology is improved.

EXAMPLE eleven

The present embodiment further provides a network device, as shown in fig. 15, which includes a processor 151, a memory 152, and a communication bus 153, where:

the communication bus 153 is used for realizing connection communication between the processor 151 and the memory 152;

the processor 151 is configured to execute one or more computer programs stored in the memory 152 to implement the steps of the network resource management method in the foregoing embodiments, which are not described herein again.

The present embodiments also provide a computer-readable storage medium including volatile or non-volatile, removable or non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, computer program modules or other data. Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash Memory or other Memory technology, CD-ROM (Compact disk Read-Only Memory), Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage systems, or any other medium which can be used to store the desired information and which can be accessed by a computer.

The computer readable storage medium in this embodiment may be used to store one or more computer programs, and the stored one or more computer programs may be executed by a processor to implement at least one step of the network resource management method in the embodiments described above.

The present embodiment also provides a computer program (or computer software), which can be distributed on a computer-readable medium and executed by a computing system to implement at least one step of the network resource management method in the foregoing embodiments.

The present embodiments also provide a computer program product comprising a computer readable system having stored thereon a computer program as shown above. The computer-readable system in this embodiment may include a computer-readable storage medium as shown above.

It will be apparent to those skilled in the art that all or some of the steps of the methods, systems, functional modules/units in the systems disclosed above may be implemented as software (which may be implemented in computer program code executable by a computing system), firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit.

In addition, communication media typically embodies computer readable instructions, data structures, computer program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to one of ordinary skill in the art. Thus, the present invention is not limited to any specific combination of hardware and software.

The foregoing is a more detailed description of embodiments of the present invention, and the present invention is not to be considered limited to such descriptions. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.

Claims

1. A network resource management method, comprising:

2. The method according to claim 1, wherein the calculating the required resources according to the lifecycle management task corresponding to the containerized VNF comprises:

3. The method of claim 1, wherein when in a scenario without CISM functionality, the calculating the required resources according to the lifecycle management task corresponding to the containerized VNF further comprises:

and calculating virtual machine resources required by the container object resources through a VNFM module of the virtual network function manager, and generating a container virtual resource list.

4. The network resource management method of claim 3, after said generating a list of container virtual resources, further comprising:

and the VNFM module requests the NFVO module for authorization of the container virtual resources, and carries the container virtual resource list.

5. The method according to claim 4, wherein processing the container resource and/or virtual machine resource corresponding to the containerized VNF lifecycle management operation comprises:

6. The method of claim 3, wherein when in a CISM functional scenario, before the computing the required resources according to the lifecycle management task corresponding to the containerized VNF, further comprises:

selecting a corresponding CISM through the NFVO module;

7. The method according to claim 6, wherein the selecting, by the NFVO module, the corresponding CISM comprises:

and the NFVO module selects CISM and provides corresponding CISMID.

8. The method of claim 6, wherein computing the required resources according to the corresponding containerized VNF lifecycle management tasks comprises:

the CISM calculates the needed virtual machine resource according to the needed container object resource;

the CISM requests at least one of required virtual machine resources, network resources, and storage resources from the VIM module.

9. The method of network resource management of claim 8, wherein the VIM, after receiving the CISM-initiated request, performs at least one of: creating/updating/releasing resources requested by the CISM; wherein the resources requested by the CISM include at least one of virtual machine resources, storage resources and network resources.

10. The method of network resource management according to claim 8, wherein after the CISM sends the request to the VIM, further comprising:

the CISM module creates the required container object resources.

11. The method according to any one of claims 4 and 9 to 10, wherein after the creating, by the CISM/VIM module, the required resources, further comprising:

12. The network resource management method according to any one of claims 4 and 9 to 10, further comprising:

13. The network resource management method of any one of claims 1-10, further comprising:

14. A network resource management system comprising:

the NFVO module (141) is used for carrying out resource authorization and selecting a corresponding CISM/VIM module;

and the CISM (144)/VIM (142) module is used for processing container resources and/or virtual machine resources corresponding to the containerization VNF lifecycle management operation.

15. The network resource management system of claim 14, wherein the resource computation module comprises the NFVO module (141), the NFVO module (141) further to: as a container virtual machine mapping agent, needed virtual machine resources are calculated for container object resources.

16. The network resource management system of claim 14, wherein the resource calculation module further comprises a VNFM module (143) for calculating virtual machine resources required for container object resources and generating a container virtual resource list when in a CISM-less functional scenario.

17. The network resource management system of claim 16 wherein the VNFM module is further configured to request a container virtual resource authorization from the NFVO module (141), carrying the list of container virtual resources.

18. The network resource management system of claim 17 wherein the VIM module (142) is further configured to create, update, or release at least one of a container object resource, a virtual machine resource, a storage resource, and a network resource from a list of container resources.

19. The network resource management system of claim 16, wherein the NFVO module (141), when in a CISM functional scenario, is further configured to select a corresponding CISM;

the VNFM module (143) is further configured to send a request to the CISM (144), where the request carries a container resource requirement.

20. The network resource management system of claim 19, wherein the NFVO module (141) is further configured to: the CISM is selected and the corresponding cimid is provided.

21. The network resource management system of claim 19 wherein the CISM module (144) is further configured to:

requesting at least one of required virtual machine resources, network resources, and storage resources from the VIM module (142).

22. The network resource management system of claim 19 wherein the VIM is further configured to: upon receipt of the CISM (144) -initiated request, performing at least one of: creating/updating/releasing resources requested by the CISM; wherein the resources requested by the CISM include at least one of virtual machine resources, storage resources and network resources.

23. The network resource management system of claim 21 wherein the CISM module (144) is further configured to: the required container object resources are created.

24. The network resource management system of any one of claims 14-23 further comprising:

the allocated network resources and/or storage resources are bound to container object resources by a CISM (144) or VIM module (142).

25. The network resource management system of any one of claims 14-23 further comprising:

and associating the container object resources under the same VNF with the allocated virtual machine resources through a VNFM module (143) or a CISM module (144).

26. A network resource management system according to claims 14-23 further comprising an EM module (145) for container application configuration and management.

27. A network device comprising a processor (151), a memory (152), and a communication bus (153);

the communication bus (153) is used for realizing connection communication between the processor (151) and the memory (152);

the processor (151) is configured to execute one or more computer programs stored in the memory (152) to implement the steps of the network resource management method according to any of claims 1-13.

28. A computer-readable storage medium, having one or more computer programs stored thereon, the one or more computer programs being executable by one or more processors to perform the steps of the network resource management method according to any one of claims 1-13.