CN111726241B

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

Info

Publication number: CN111726241B
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: 2023-05-19
Anticipated expiration: 2039-03-22
Also published as: CN111726241A

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, according to the life cycle management task corresponding to the containerized VNF, the needed container resource and/or virtual machine resource are calculated; resource authorization is carried out through the NFVO module, and a corresponding CISM/VIM module is selected; and processing container resources and/or virtual machine resources corresponding to the life cycle management operation of the containerized VNF through the CISM/VIM module. Therefore, the method for managing the container resources in the VNF life cycle management operation is provided, and the application of the NFV technology is perfected.

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, network resource management methods, systems, network devices, and readable storage media.

Background

Network function virtualization (NFV, network Functions Virtualization) is a software processing technology that uses general-purpose hardware and virtualization technology to carry other functions in order to reduce the expensive equipment cost of the network. The NFV enables the network equipment function to be independent of the special hardware through software and hardware decoupling and function abstraction, resources can be fully and flexibly shared, rapid development and deployment of new services are realized, and automatic deployment, elastic expansion, fault isolation, self-healing and the like are performed based on actual service requirements.

As shown in fig. 1, the NFV system architecture defined by the european telecommunications standards institute (ETSI, european Telecommunications Standards Institute) mainly includes: a business operations Support System and management Support platform (OSS/BSS, operation-Support System/Business Support System), virtualized network functions (VNF, virtualized Network Function), network function virtualization infrastructure (NFVI, network Functions Virtualization Infrastructure), and network function virtualization management and orchestration System (NFV-MANO, VNF-Management and Orchestration). The NFVI is mainly responsible for comprehensively virtualizing hardware resources such as computation, storage, network and the like and mapping the hardware resources into virtual resources; the VNF is implemented by using software to implement various traditional physical network functions, and the VNF operates on the NFVI and uses virtual resources virtualized by the NFVI. NFV-MANO is responsible for managing and orchestrating the relationship between VNFs and NFVI and the connectivity relationship between VNFs and/or with other physical network functions (PNFs, physical Network Functions).

NFV-MANO includes: a virtualized base settings manager (VIM, virtualized Infrastructure Manager), a virtual network functions manager (VNFM, virtualized Network Function Manager), and a network virtualization functions orchestrator (NFVO, network Function Virtualization Orchestrator). The VIM is responsible for controlling and managing virtualized resources; the VNFM is responsible for life cycle management of the VNF; NFVO is responsible for orchestration and management of virtual infrastructure, as well as lifecycle management of Network Services (NS).

The micro-service architecture is the development and evolution direction of NFV technology, and is based on the application of cloud native technology and container technology. The container is used as an application packaging technology, defines a standardized application release format, and greatly facilitates development, deployment and migration of applications. The container adopts the techniques of layered mirror image, centralized mirror image warehouse and the like, so that the micro-servitization transformation of the network element is promoted, and the software development and deployment can be accelerated. The container is introduced, so that the requirements of rapid deployment of edge computing services, improvement of resource utilization rate of edge computing network elements and deployment of 5G control surface networks by the container can be met.

At present, NFV standards have already defined how to manage Virtual Machine (VM) resources, such as quota and quota management, resource authorization management, resource allocation and recovery management, of Virtual Machine resources, during life cycle management operations, such as instantiation, elastic extension, self-healing, termination, and the like, of VNF. After the container is introduced into the NFV standard, the container virtual resources include container object resources (such as PODs), virtual machine VM resources required by the container object resources, network resources required by the container object resources, and storage resources. How the container virtual resources are managed in the VNF lifecycle management process requires specification and definition, but there is no mechanism for container resource management in the related specification.

Disclosure of Invention

The embodiment of the invention provides a network resource management method, a system, network equipment and a readable storage medium, which mainly solve the technical problem of providing a management mechanism of a container virtual resource in a VNF life cycle.

In order to solve the above technical problems, an embodiment of the present invention provides a network resource management method, including:

according to the life cycle management task corresponding to the virtualized network function VNF of the container, calculating required container resources and/or virtual machine resources;

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 processes container resources and/or virtual machine resources corresponding to the life cycle management operation of the containerized VNF.

The embodiment of the invention also provides a network resource management system, which comprises:

the resource calculation module is used for calculating required container resources and/or virtual machine resources according to the life cycle management tasks corresponding to the containerized VNF;

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

The CISM/VIM module is used for processing container resources and/or virtual machine resources corresponding to the life cycle management operation of the containerized VNF.

The embodiment of the invention also provides a network device, 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.

The embodiment of the invention also provides a computer storage medium, and the computer readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of the network resource management method.

The beneficial effects of the invention are as follows:

Additional features and corresponding advantages of the invention will be set forth in the description which follows, and in part will be apparent 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 CISM addition;

FIG. 3 is a general diagram of supporting container virtual resource management in a common ETSI NFV architecture scenario;

FIG. 4 is a general diagram of supporting container virtual resource management in an extended ETSI NFV architecture scenario;

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

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

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

fig. 8 is a schematic diagram of container resource management in the process of VNF shrinking operation in a CISM-free scenario provided in the fourth embodiment of the present invention;

fig. 9 is a schematic diagram of container resource management in a VNF scaling operation in a CISM-enabled scenario provided in a fifth embodiment of the present invention;

Fig. 10 is a schematic diagram of container resource management in the VNF self-healing operation process in the CISM-free scenario provided in the sixth embodiment of the present invention;

fig. 11 is a schematic diagram of container resource management in a VNF self-healing operation process in a CISM-enabled scenario provided in the seventh embodiment of the present invention;

fig. 12 is a schematic diagram of container resource management during VNF deletion operation in a CISM-free scenario provided in embodiment eight of the present invention;

fig. 13 is a schematic diagram of container resource management in a VNF deletion operation in a CISM-enabled scenario provided in embodiment nine of the present invention;

fig. 14 is a schematic diagram of 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, the following detailed description of the embodiments of the present invention is given with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.

The present NFV system cannot support resource management of a container, and the embodiments of the present invention provide a method and a system for managing container resources, so that when a containerized VNF performs life cycle management operation, required container resources can be managed, and the method and the system are not limited to operations of creating, adding, reducing, migrating, and releasing container resources for the containerized VNF, so that the VNF can use the container resources to perform life cycle management, and achieve a goal of introducing a container into the NFV system.

Scene one corresponding to the embodiment of the invention: container resource management without CISM function

The embodiment of the present invention is applied in the NFV architecture, describing how MANO enhances supported container resource management, see fig. 3. Wherein the NFVO comprises an enhanced NFVO container functional module for: 1, virtual resource authorization of a container; 2, taking the virtual machine as a container virtual machine mapping agent, and calculating needed virtual machine resources for the container object resources;

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

the VIM contains an enhanced VIM container function module for: 1, allocating container object resources; 2 is a storage resource and a network resource required by the binding of the container object resource;

the EM contains an enhanced ElEMent Manager (EM) container function module for: configuration and management of container applications;

scene two corresponding to the embodiment of the invention: container resource management under CISM function

The embodiment of the invention is applied to the scene of NFV architecture enhancement, and describes how MANO enhances the supported container resource management under the condition that CISM container management functions exist, and refer to FIG. 4.

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

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

CISM function for: 1, allocating container object resources; 2, taking the virtual machine as a container virtual machine mapping agent, and calculating needed virtual machine resources for the container object resources; 3 association of container object resources and virtual machine resources in the same VNF; 4 is the storage resource and network resource needed by the binding of the container object resource;

VIM container function module for: 1, creating virtual machine resources, storage resources and network resources of a CISM request;

the EM contains enhanced EM container functional modules for: configuration and management of container applications;

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

In the following, by means of specific embodiments, how to manage the container virtual resources during the management of the life cycle of the containerized VNF is described.

Embodiment one:

the present embodiment provides a network resource management method, please refer to fig. 5, which includes:

s11, calculating required container resources and/or virtual machine resources according to life cycle management tasks corresponding to the containerized VNF;

s12, authorizing resources required during the management operation of the life cycle of the containerized VNF through the NFVO module, and selecting a corresponding container management function CISM/virtualization base setting manager VIM module to perform the resource operation;

s13, processing container resources and/or virtual machine resources corresponding to the life cycle management operation of the containerized VNF through the CISM/VIM module.

In some embodiments, according to the lifecycle management tasks corresponding to the containerized VNFs, the computing resources required may include:

and calculating 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 the CISM-free functional scenario, calculating the required resources may further include:

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

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

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

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

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

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

selecting a corresponding CISM through the NFVO module;

the VNFM module sends a request to the CISM, the request carrying the container resource requirements.

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

the NFVO module selects CISM and provides the corresponding cisid.

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 the following may be performed: creating/updating/releasing CISM requested resources; 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, it may further include:

the CISM module creates the required container object resources.

In some embodiments, after creating the required resources by the VIM module, it may further include:

and binding the allocated network resources and/or storage resources with the container object resources through the 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 the VNM module or the CISM module.

In some embodiments, further comprising:

container application configuration and management is performed by the EM module.

In this embodiment, the lifecycle management tasks may include new creation, addition, subtraction, release, and so on.

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

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

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

and analyzing the VNFD and the instantiation parameters, determining 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 parameter has a corresponding VNF resource planning, determining required container resources according to the VNF resources;

if only the container resource needs exist in the instantiation parameters, the needed container resources are calculated according to the container resource needs.

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

the VNF is configured and the instantiation progress is returned.

In some embodiments, it may further include:

receiving an elastic telescoping operation on the containerized VNF;

initiating a VNF (virtual network function) shrinking and expanding request;

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

and selecting to execute or not execute the capacity-shrinking and expanding operation of the VNF based on the judging result.

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

If the container virtual resource information is carried in the contraction and expansion request, calculating the required increased or decreased container object resources according to the container virtual resource information, and determining the change condition of the required virtual machine resources;

if the container virtual resource information is not carried in the capacity-shrinking and expanding request, the container object resources which are required to be increased or reduced by the capacity-shrinking and expanding VNF are calculated according to the container resource requirement of elastic expansion, and the change condition of the required virtual machine resources is determined.

In some embodiments, before determining whether to allow the VNF to be scaled up or down based on the current resource situation, the method may further include:

and creating a VNF capacity-shrinking and expanding task.

In some embodiments, it may further include:

initiating a VNF self-healing request;

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

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

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

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

In some embodiments, it may further include:

initiating a VNF termination request;

creating a VNF termination task and requesting resource authorization for carrying out VNF termination operation;

And deleting the virtual resources of the container occupied by the VNF.

According to the network resource management method provided by the embodiment, the required resources are calculated according to the corresponding life cycle management tasks; authorizing through the NFVO module, and selecting a corresponding VIM module; the required resources are created by the VIM module. Therefore, the method for managing the container resources in the VNF life cycle management operation is provided, and the application of the NFV technology is perfected.

Example two

Containerized VNF instantiation (without CISM)

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

Fig. 6 has the following steps flow:

s101: an operator initiates a containerized VNF instantiation operation at an operation interface of the NFVO;

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

s103: the VNFM creates VNF instantiation tasks. The VNFM parses the VNFD and the instantiation parameters, calculates the required resources according to the VNF resource plan or the container resource requirement 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 specification, virtual machine number), bare machine computing resources, storage resources, network resources, and the like, which are required by the container object resources.

If the instantiation parameter has an explicit VNF resource plan, the VNFM needs to generate a container virtual resource list according to the VNF resource plan, which includes information such as a container object resource, a virtual machine resource, a network resource and a storage resource required by the container object resource. If the instantiation parameter is only the container resource requirement, the VNFM needs to calculate the required container object resource (such as POD) according to the container object resource requirement, virtual machine resource (virtual machine specification, virtual machine number) required by the container object resource, network resource and storage resource required by the container object resource, and then generate the container virtual resource list.

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

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

S106: the VNFM sends a request to NFVO to create virtual resources of the VNF container;

s107: NFVO requests in VIM the creation of container virtual resources required in the list of container virtual resources, including the creation of container object resources (POD), virtual Machine (VM) resources, virtual storage, virtual network cards, virtual networks, mounting virtual storage, virtual network cards to container objects, connecting virtual network cards to virtual networks, and affinity and anti-affinity between different virtual machines.

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

The VIM detects that the container virtual resource creation is successful, notifies the NFVO of the creation success message, and returns the allocated container virtual resource. NFVO informs VNFM of the creation success message, VNFM associating container object resources created for the VNF with virtual machine resources;

S109: the VNFM establishes connection with the VNF in the instantiation, the VNFM feeds back a token to the VNFM, and the VNFM configures the instantiation related service parameters to the VNFM; the VNF feeds back the instantiation progress to the VNFM. After the VNF instantiation progress is 100%, the VNF instantiation is indicated to be successful.

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

S111: the NFVO informs the operator of the instantiation completion message.

S112: after VNF instantiation is completed, the EMS is notified that the containerized VNF instantiation is completed. 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 an instantiation operation, the VNFM requests the NFVO for container virtual resource authorization, calculates a container object resource according to a resource requirement in an instantiation parameter, calculates a virtual machine resource required by the container object resource, and generates a container virtual resource list. The VIM creates virtual machine resources, container object resources, network resources, storage resources, and binds the network resources and the storage resources to the container object resources. After the container virtual resource is successfully created, the VNFM associates the container object resource with the virtual machine resource under the same VNF.

Example III

Containerized VNF instantiation (with CISM)

Fig. 7 is a schematic diagram corresponding to the third embodiment of the present invention, where the embodiment mainly describes a process of instantiation of a containerized VNF, when an operator initiates an instantiation operation of the containerized VNF, the NFVO needs to perform an authorization operation for a virtual container resource, and if there is an explicit VNF resource plan, the VNFM needs to generate a virtual container resource list according to the VNF resource plan, including information such as a container object resource, a virtual machine resource, a network resource and a storage resource required by the container object resource. If there is only a container resource requirement, for example, the VNF instantiation parameter is only a container object resource, a storage resource, and a network resource requirement, the VNFM needs to send the container resource requirement to the CISM, and the CISM needs to calculate a required virtual machine resource for the container object resource according to the container object resource requirement, and then generate the container virtual resource list. The VIM creates the needed virtual machine VM resources, storage resources and network resources according to CISM requirements, and returns a successful creation 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 a containerized VNF instantiation operation at an operation interface of the NFVO;

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

s203: the VNFM creates VNF instantiation tasks. The VNFM parses the VNFD and instantiation parameters, obtains container resource requirements from the instantiation parameters (the instantiation parameters may carry VNF resource planning or container resource requirements), and sends the container resource requirements to the CISM.

The CISM calculates, according to the container resource requirement, the container object resources (such as POD) required by the VNF instance, virtual machine resources (virtual machine specification, virtual machine number) required by the container object resources, and the required storage resources and network resources, 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 (such as POD), 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 VNM.

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

S205: the NFVO grants the container resources, selects CISM and VIM for this instantiation operation according to the MANO policy in the grant response, and returns CISMID, VIMID and TenantID to the VNFM.

S206: the VNFM sends a request to NFVO to create virtual resources of the VNF container;

s207: NFVO requests to CISM for creation of container virtual resources required for creation, including operations such as container object (POD), virtual Machine (VM), virtual storage, virtual network card, creation of virtual network, mounting of virtual storage, virtual network card to container object, connection of virtual network card to virtual network, and affinity and counteraffinity between different virtual machines.

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

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

s210: the CISM creates needed 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 network resources to the container object resources PODs.

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

S212: the VNFM establishes connection with the VNF in the instantiation, the VNFM feeds back a token to the VNFM, and the VNFM configures the instantiation related service parameters to the VNFM; the VNF feeds back the instantiation progress to the VNFM. After the VNF instantiation progress is 100%, the VNF instantiation is indicated to be successful.

After the VNF is successfully instantiated, the VNFM sends a VNF instantiation success message to the NFVO, informing the NFVO of the container virtual resources contained in the VNF, and the NFVO responds.

After the VNF instantiation is completed, the EMS is notified that the instantiation is completed. The EMS adds the newly instantiated containerized VNF to the management object, and performs service configuration and management on the containerized VNF.

In this process, when the containerized VNF performs an instantiation operation, the CISM calculates, according to the container resource requirement of the VNFM, container object resources and virtual resources required by the container object resources, and generates a container virtual resource list. The VNFM requests container virtual resource authorization from the NFVO and requests creation of container virtual resources from the CISM. 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 created for the same VNF with the virtual machine resources.

Example IV

Containerized VNF elastic telescoping (CISM free)

Fig. 8 is a schematic diagram corresponding to the fourth embodiment of the present invention, which mainly describes the operation process of elastic stretching of the containerized VNF, where NFVO or VNFM needs to calculate new added or reduced virtual machine resources (VM specification and number) for the new added or reduced container object resources according to the elastic stretching container resource requirement. When the VNFM requests the NFVO for the new or reduced virtual machine resources and container object resources required for the new or reduced scaling VNF, the NFVO needs to perform an authorization operation on the container virtual resources for which update is applied. The EMS needs to decide whether to allow the containerized VNF to shrink and update the management object for the containerized VNF.

Fig. 8 has the following steps:

s301: an operator initiates containerized VNF contraction and expansion operation on an operation interface of the NFVO;

s302: the NFVO initiates a VNF contraction and expansion request to the VNFM, and may carry container virtual resources required for contraction and expansion. If the NFVO carries the container resource information of the shrink and expansion, the NFVO needs to calculate the container object resource that needs to be increased or decreased by the shrink and expansion VNF, and calculate the change of the virtual machine resource (the information of increase and decrease of the VM resource) according to the change information of the container object resource. And then, the container computing resource POD which needs to be changed, the virtual machine VM resource which needs to be changed, and corresponding resource information such as storage resources, network resources and the like are sent to the VNM.

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

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

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

s305: the NFVO checks whether there are enough resources in the VIM according to the VIMID in which the VNF is carried in the authorization request. If the resources are sufficient, the same VIMID is returned. If the resources are insufficient, authorization is denied for the container resources.

S306: the VNM informs the EMS to perform volume reduction and expansion, and the EMS decides whether to allow the VNM to perform volume reduction and expansion on the VNF according to the situation of the operation of the VNM on the VNF and the consideration of no influence on the service and the need of avoiding operation conflict.

S307: the VNFM sends a request for creating newly added VNF container virtual resources or releasing the existing VNF container virtual resources to the NFVO according to the operation of the VNF shrink;

s308: the NFVO requests to create newly added or released container virtual resources needing to be shrunken in the VIM, including creation or release of container objects (POD), virtual Machines (VM), virtual storage, virtual network cards, and virtual networks, and updates binding relations between the virtual storage, the virtual network cards, and the virtual networks and the container objects.

S309: the VIM needs to create or release the container object resource POD, the virtual machine VM resource, the storage resource, and the network resource according to the shrunken 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 resource of the flick container is successfully created or released, notifies the NFVO of a flick operation success message, and the NFVO notifies the VNFM of the flick operation success message, and the VNFM updates the binding relation between the container object resource and the virtual machine resource of the VNF;

s310: and the VNFM establishes connection with the instantiated VNF, informs the VNF of finishing the resource processing, configures the parameters related to the contraction and expansion, and returns a response to the VNFM. And feeding back the expansion progress to the VNFM, and indicating that the VNF is successful in expansion and contraction after the expansion and contraction progress fed back by the VNF is 100%.

S311: after the VNF is successfully scaled up and scaled up, the VNFM sends a VNF scaling up success message to the NFVO, informing the NFVO of the change of virtual resources included in the VNF, and the NFVO responds.

S312: the operator can see the shrinking and expanding result at the NFVO interface

S313: and after the VNF is completed, notifying the EMS of the completion of the volume reduction and expansion. The EMS will update the management object corresponding to the VNF and configure new application parameters according to the architecture requirement.

In this flow, when the VNF performs the scaling operation, the VNFM calculates the newly added or reduced container object resources according to the requirement of the scaling operation on the container object resources, calculates the virtual machine resources required to be newly added or reduced according to the changing condition of the container object resources, and generates a scaling container virtual resource list to request authorization to the NFVO for the scaling container virtual resources. The VIM creates or releases the container object resource, the virtual machine resource, the storage resource and the network resource according to the flick container resource request, and updates the binding relation between the container object resource and the storage resource as well as between the storage resource and the network resource, and the VNM updates the association relation between the container object resource and the virtual machine resource of the VNF.

Example five

Containerized VNF elastic telescoping (with CISM)

Fig. 9 is a schematic diagram corresponding to the fifth embodiment of the present invention, which mainly describes the operation process of the elastic scaling of the containerized VNF, where NFVO or CISM needs to calculate new added or reduced virtual machine resources (VM specification and number) for the new added or reduced container object resources according to the elastic scaling container resource requirement. When the VNFM requests the NFVO for the new or reduced virtual machine resources and container object resources required for the new or reduced scaling VNF, the NFVO needs to perform an authorization operation on the container virtual resources for which update is applied. The EMS needs to decide whether to allow the containerized VNF to shrink and update the management object for the containerized VNF.

Fig. 9 has the following steps:

s401: an operator initiates containerized VNF contraction and expansion operation on an operation interface of the NFVO;

s402: the NFVO initiates a VNF contraction and expansion request to the VNFM, and may carry container virtual resources required for contraction and expansion. If the NFVO carries the container resource information of the shrink and expansion, the NFVO needs to calculate the container object resource that needs to be increased or decreased by the shrink and expansion VNF, and calculate the change of the virtual machine resource (the information of increase and decrease of the VM resource) according to the change information of the container object resource. And then, the container computing resource POD which needs to be changed, the virtual machine VM resource which needs to be changed, and corresponding resource information such as storage resources, network resources and the like are sent to the VNM.

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

The CISM calculates the container object resources that are required to be increased or decreased by the VNF according to the container resource change requirement, and calculates the change of the required virtual machine resources (the increase and decrease information of the VM resources) according to the change information of the container object resources. Then calculating resource POD of the container to be changed, virtual machine VM resource to be changed, and corresponding resource information such as storage resource and network resource;

The CISM generates a shrunken container virtual resource list for VNF shrunken, including, but not limited to, newly added or reduced container resource information (e.g., POD), virtual machine resources (virtual machine specification, virtual machine number) corresponding to the container resources, bare machine computing resources, storage resources, network resources, and the like, and then sends the virtual machine resource list to the VNFM.

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

s405: NFVO checks whether there are enough resources in CISM and VIM according to cisid and vimd where VNF is carried in the authorization request. If the resources are sufficient, the same CISMID and VIMID are returned. If the resources are insufficient, the authorization is refused to authorize the newly added container resources.

S406: the VNM informs the EMS to perform volume reduction and expansion, and the EMS decides whether to allow the VNM to perform volume reduction and expansion on the VNF according to the situation of the operation of the VNM on the VNF and the consideration of no influence on the service and the need of avoiding operation conflict.

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

s408: NFVO requests to CISM to create newly added or released container virtual resources to be shrunken, including creation or release of container objects (POD), virtual Machines (VM), virtual storage, virtual network cards, virtual networks, and update binding relations between virtual storage, virtual network cards, virtual networks, and container objects.

S409: the CISM requests virtual machine resources, network resources and storage resources which need to be shrunken to the VIM;

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

s411: the CISM creates or releases the needed shrunken container object resources POD, updates the association relation between the container object resources and virtual machine resources of the same VNF, and updates the binding relation between the storage resources, the network resources and the container object resources POD.

S412: after CISM flick operation is completed, notifying the NFVO of a successful message of resource contraction and expansion, and notifying the VNM of the successful message of resource contraction and expansion by the NFVO;

s413: the VNFM establishes connection with the instantiated VNF, informs the VNF of finishing the processing of the resources, configures the expansion related parameters, and returns a response to the VNFM. And feeding back the capacity shrinkage and expansion progress to the VNFM, and indicating that the VNF is successful in capacity expansion after the capacity expansion progress fed back by the VNF is 100%.

S414: after the VNF is successfully scaled up and scaled up, the VNFM sends a VNF scaling up success message to the NFVO, informing the NFVO of the change of virtual resources included in the VNF, and the NFVO responds.

S415: the operator can see the shrinking and expanding result at the NFVO interface

S416: and after the VNF is completed, notifying the EMS of the completion of the volume reduction and expansion. The EMS will update the management object corresponding to the VNF and configure new application parameters according to the architecture requirement.

In this flow, when the VNF performs the scaling operation, the VNFM requests the NFVO for authorization of the container virtual resource that needs to be scaled, and requests the CISM to create or release the container virtual resource for scaling. The CISM calculates the virtual machine resources which are needed to be newly added or released according to the requirements of the flicking operation on the container object resources, generates a container virtual resource list, requests to the VIM to create or release the container object resources, the virtual machine resources which are needed 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 performs the scaling operation, the CISM calculates a new added or reduced container object resource according to a requirement of the scaling operation on the container object resource, calculates a virtual machine resource required to be added or reduced according to a change condition of the container object resource, and generates a scaling container virtual resource list to request authorization to the NFVO for the scaling container virtual resource. The VIM creates or releases virtual machine resources, storage resources and network resources according to the resource request of the flick container. After VIM resource shrinking is completed, the CISM creates or releases container object resources required by the shrinking, updates binding relations between the container object resources and storage resources and between the container object resources and network resources, and updates association relations between the container object resources and virtual machine resources of the VNF.

Example six

Containerized VNF self-healing (without CISM)

Fig. 10 is a schematic diagram corresponding to a sixth embodiment of the present invention, where the embodiment mainly describes an operation process of self-healing of a containerized VNF, and when a resource occupied by the VNF fails, the VNF service performance is degraded, and the EMS and the VNF may initiate a self-healing process of the VNF. In the VNF self-healing operation, the VNFM needs to calculate the required container object resources POD and virtual machine resources (VM specification and number) required by the container object resources according to the 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 container object resources POD, VM resources required for POD, storage resources, network resources, and the like. When the VNFM requests the NFVO to authorize 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 the resources in the container virtual resource list. The VIM creates virtual machine resources, network resources and storage resources required by the self-healing of the VNF, creates container object resources required by the self-healing of the VNF, binds the allocated storage resources, network resources and the container object resources, then informs the VNF of the successful creation result of the self-healing resources to the VNFM and the NFVO, and the VNFM associates the container object resources under the self-healing VNF with the virtual machine resources to complete the self-healing operation of the VNF.

Fig. 10 has the following steps:

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

s502: the VNF or the EMS performs self-healing operation to 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-healing, the NFVO responds;

s504: the VNFM creates VNF self-healing tasks. The VNM needs to calculate the container calculation 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 contain container object resources (such as POD), 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.

S505: the VNFM requests the NFVO to perform resource authorization for VNF self-healing operation, carrying the container resource list in S504, and the authorization request further carries the VIMID in which the VNF is located;

s506: the NFVO checks whether there are enough resources in the VIM according to the VIMID in which the VNF is carried in the authorization request. If the resources are sufficient, the same VIMID is returned. If the resources are insufficient, the authorization is refused to authorize the container resources required for VNF self-healing.

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

s508: NFVO requests in VIM the creation of container virtual resources required for VNF self-healing, including operations such as container (POD), virtual Machine (VM), virtual storage, virtual network card, creation of virtual network, mounting virtual storage, virtual network card to container object, connecting virtual network card to virtual network, and affinity and counteraffinity between different virtual machines.

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

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

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

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

In this flow, when the VNF performs the self-healing operation, the container object resources are calculated according to the VNF self-healing resource requirements, virtual machine resources required by the container object resources, 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 for VNF self-healing, and binds the network resources and the storage resources to the container object resources. After the container virtual resource is successfully created, the VNFM associates the container object resource with the virtual machine resource under the same VNF.

Example seven

Containerized VNF self-healing (with CISM)

Fig. 11 is a schematic diagram corresponding to a seventh embodiment of the present invention, where the embodiment mainly describes an operation process of elastic scaling of a containerized VNF, and when a resource occupied by the VNF fails, the VNF service performance is degraded, and the EMS and the VNF may initiate a VNF self-healing procedure. In the VNF self-healing operation, the VNFM requests the CISM for the VNF self-healed container resources, carrying the VNF self-healed container resource requirements. The CISM needs to calculate the required container object resources POD and virtual machine resources (VM specification and number) required by the container object resources according to the self-healing container resource requirements of the VNF, and generate a container virtual resource list of the self-healing VNF. The container resource list is not limited to include container object resources POD, VM resources required for POD, storage resources, network resources, and the like. When the VNFM requests the NFVO to authorize 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 self-healing of the VNF, allocates container object resources required by the self-healing of the VNF, binds the storage resources, the network resources and the container object resources allocated by the VIM, and associates the container object resources under the self-healing VNF with the virtual machine resources. And the CISM informs the VNM and the NFVO of the successful resource creation result of the VNF resources, and completes the self-healing operation of the VNF.

Fig. 11 has the following steps:

s601: the VNF or the EMS judges whether to initiate a VNF self-healing request or not;

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

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

s604: the VNFM creates VNF self-healing tasks. The VNM needs to calculate the container calculation resources 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 for VNF self-healing operation, carrying the container resource list in S404, and the authorization request further carries cimid and VIMID where the VNF is located;

s606: NFVO checks whether there are enough resources in CISM and VIM according to cisid and vimd where VNF is carried in the authorization request. If the resources are sufficient, the same CISMID and VIMID are returned. If the resources are insufficient, the authorization is refused to authorize the container resources required for VNF self-healing.

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

s608: NFVO requests to CISM for creating container virtual resources required for VNF self-healing, including operations such as creation of container (POD), virtual Machine (VM), virtual storage, virtual network card, virtual network, mounting virtual storage, virtual network card to virtual machine, connecting virtual network card to virtual network, and affinity and counteraffinity between different virtual machines.

S609: the CISM needs to create container object resources POD according to the container resource list, calculates required VM resources, updates the container resource list, adds virtual machine resources in the container resource list, and then sends the virtual machine resources to the VIM;

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

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

S612: the CISM detects that the virtual resource of the newly added container is successfully created, notifies the NFVO of a creation success message, and the NFVO notifies the NFVM of the creation success message;

s613: after the VNF self-healing succeeds, the VNFM sends a vnfvnnf self-healing success message to the NFVO, informing that the container virtual resources contained in the VNF self-healing are allocated, and the NFVO responds.

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

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

Example eight

Containerized VNF termination (no CISM)

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

Fig. 12 has the following steps:

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

S703: the VNFM creates a VN terminating task, generates a task ID, and returns a response message to the NFVO. The method comprises the steps of carrying out a first treatment on the surface of the

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

s705: the NFVO terminates the VNF resources according to the current resource status authorization in the VIM, where the VNF is carried in the authorization request.

S706: the VNM informs the EMS of the termination operation of the VNF, and the EMS decides whether the VNM is allowed to terminate the VNF or not on the premise of not affecting the service according to the condition of the operation of the VNF and the requirement of avoiding operation conflict.

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

s708: NFVO requests to VIM to delete container virtual resources occupied by VNF, including virtual resources such as container object resources (POD), virtual Machines (VM), virtual storage, virtual network cards, virtual networks, and the like.

S709: the VIM performs resource deletion, releases virtual machine resources, storage resources and network resources occupied by the VNF instance, and releases container object resources. After the VIM detects that the virtual resources of the VNF container are successfully deleted, notifying the NFVO of a successful message of the deletion of the virtual resources of the VNF container, notifying the VNFM of a successful message of the deletion of the virtual resources of the VNF, and deleting the association relation between the virtual machine resources and the container object resources under the VNF by the VNFM;

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

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

S712: after the VNF instance deletion is completed, the VNFM notifies the EMS that VNFI has been deleted. 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 deleting the container virtual resource occupied by the VNF instance. After receiving the VNF resource deletion request of the NFVO, the VIM deletes the container object resource, virtual machine resource, network resource and storage resource occupied by the VNF instance, and notifies the NFVO and the VNFM. The VNFM deletes the association relationship between the container object resource and the virtual machine resource under the VNF.

Example nine

Containerized VNF termination (with CISM)

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

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: the VNFM creates a VN terminating task, generates a task ID, and returns a response message to the NFVO. The method comprises the steps of carrying out a first treatment on the surface of the

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

s805: the NFVO terminates the VNF resources according to the current status authorizations of the resources in the CISM and VIM, according to the cismid in which the VNF is carried in the authorization request.

S806: the VNM informs the EMS of the termination operation of the VNF, and the EMS decides whether the VNM is allowed to terminate the VNF or not on the premise of not affecting the service according to the condition of the operation of the VNF and the requirement of avoiding operation conflict.

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

s808: NFVO requests deletion of container virtual resources occupied by VNF in CISM, including virtual resources such as container (POD), virtual Machine (VM), virtual storage, virtual network card, virtual network, etc.

S809: the CISM performs 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. The CISM is notified after the VIM is deleted.

S810: after the deletion of the container virtual resources occupied by the VNF instance is successful, the CISM notifies the NFVO of a successful deletion message of the container virtual resources of the VNF, the NFVO notifies the VNFM of a 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, informing that the container virtual resources occupied by the VNF instance have been successfully deleted, and the NFVO responds.

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

S813: after the VNF instance deletion is completed, the VNFM notifies the EMS that VNFI has been deleted. 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 the container virtual resource deletion authorization, and the VNFM requests the NFVO for deleting the container virtual resource occupied by the VNF instance. After the CISM receives the VNF resource deleting request of the NFVO, deleting the container object resources occupied by the VNF instance, informing the VIM to delete the virtual machine resources, the network resources and the storage resources occupied by the VNF instance, and then informing the NFVO and the VNFM by the CISM. The VNFM deletes the association relationship between the container object resource and the virtual machine resource under the VNF.

Examples ten

The present embodiment provides a network resource management system, please refer to fig. 14, which includes:

NFVO module 141, configured to authorize resources required for the management operation of the lifecycle of the containerized VNF, and select a corresponding container management function CISM/virtualization base setting 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 containerized VNF lifecycle management operation.

In some embodiments, the resource calculation module includes an NFVO module 141, where the NFVO module 141 is further configured to: as a container virtual machine mapping agent, the required virtual machine resources are calculated for the container object resources. In this embodiment, the resource calculation module includes the NFVO module 141, which indicates that the NFVO module 141 can implement the function of the resource calculation module, but does not indicate the dependency between the resource calculation module and the NFVO module 141, which is not limited in this embodiment; the resource calculation module hereinafter includes 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 when in the CISM-free functional scenario, and generating a container virtual resource list.

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

In some embodiments, VIM module 142 is also configured to create, update, or release at least one of container object resources, virtual machine resources, storage resources, and network resources 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 the container resource requirement.

In some embodiments, NFVO module 141 may also be used to: selecting a CISM and providing a corresponding cisid.

In some embodiments, CISM144 may also be used to:

calculating required virtual machine resources according to the required container object resources;

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

In some embodiments, VIM may also be used to: after receiving the CISM 144-initiated request, at least one of: creating/updating/releasing CISM requested resources; 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 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 to the container object resources by the CISM144 or the VIM module 142.

In some embodiments, it may further include:

through the VNFM module 143 or the CISM144, the allocated virtual machine resources are associated with the container object resources under the same VNF.

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, the required resources are calculated according to the corresponding life cycle management tasks; authorizing through the NFVO module, and selecting a corresponding VIM module; the required resources are created by the VIM module. Therefore, the method for managing the container resources in the VNF life cycle management operation is provided, and the application of the NFV technology is perfected.

Example eleven

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

a communication bus 153 for enabling 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 above embodiments, which are not described herein.

The present embodiments also provide a computer-readable storage medium including volatile or nonvolatile, 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 includes, but is not limited to, RAM (Random Access Memory ), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory, charged erasable programmable Read-Only Memory), flash Memory or other Memory technology, CD-ROM (Compact Disc 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, where 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 each embodiment described above.

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

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

It will be apparent to one 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 in 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 the 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 cooperatively by several physical components. 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.

Furthermore, as is well known to those of ordinary skill in the art, 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 may include any information delivery media. Therefore, the present invention is not limited to any specific combination of hardware and software.

The foregoing is a further detailed description of embodiments of the invention in connection with the specific embodiments, and it is not intended that the invention be limited to the specific embodiments described. It will be apparent to those skilled in the art that several simple deductions or substitutions may be made without departing from the spirit of the invention, and these should be considered to be within the scope of the invention.

Claims

1. A method for managing network resources, comprising:

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 to perform resource operation;

And the CISM module is used for processing container resources and/or virtual machine resources corresponding to the life cycle management operation of the containerized VNF.

2. The network resource management method of claim 1, wherein calculating the required resources according to the lifecycle management tasks corresponding to the containerized VNFs comprises:

3. The network resource management method of claim 1, wherein when in a CISM functional scenario, before the computing the required resources according to the lifecycle management tasks corresponding to the containerized VNFs, further comprising:

selecting a corresponding CISM through the NFVO module;

and the virtual network function manager VNM module sends a request to the CISM, wherein the request carries the container resource requirement.

4. The network resource management method of claim 3, wherein the selecting, by the NFVO module, the corresponding CISM comprises:

the NFVO module selects CISM and provides a corresponding cisid.

5. The network resource management method of claim 3, wherein calculating the required resources according to the lifecycle management tasks corresponding to the containerized VNFs comprises:

The CISM calculates required virtual machine resources according to the required container object resources;

the CISM requests at least one of a virtual machine resource, a network resource, and a storage resource, as needed, from a virtualization infrastructure setup manager (VIM) module.

6. The network resource management method of claim 5, wherein after the VIM receives the CISM-initiated request, at least one of: creating/updating/releasing CISM requested resources; wherein the CISM requested resources comprise at least one of virtual machine resources, storage resources and network resources.

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

the CISM module creates the required container object resources.

8. The network resource management method according to claim 6 or 7, further comprising, after creating the required resources by the CISM/VIM module:

9. The network resource management method according to claim 6 or 7, further comprising:

10. The network resource management method according to any one of claims 1 to 7, further comprising:

and carrying out container application configuration and management through a network element management device EM module.

11. A network resource management system, comprising:

the resource calculation module is used for calculating required container resources and/or virtual machine resources according to life cycle management tasks corresponding to the containerized Virtualized Network Function (VNF);

a network virtualization function orchestrator NFVO module (141) for performing resource authorization and selecting a corresponding container management function CISM module (144);

the CISM (144) is configured to process container resources and/or virtual machine resources corresponding to the containerized VNF lifecycle management operation.

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

13. The network resource management system of claim 11, wherein the resource calculation module further comprises a virtual network function manager VNFM module (143), the NFVO module (141) further configured to select a corresponding CISM when in a CISM functional scenario;

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

14. The network resource management system of claim 13, wherein the NFVO module (141) is further configured to: selecting a CISM and providing a corresponding cisid.

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

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

16. The network resource management system of claim 15, wherein the VIM is further to: after receiving the CISM (144) initiated request, at least one of: creating/updating/releasing CISM requested resources; wherein the CISM requested resources comprise at least one of virtual machine resources, storage resources and network resources.

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

18. The network resource management system of any one of claims 11-17,

The CISM (144) or VIM module (142) is also configured to bind the allocated network resources and/or storage resources with the container object resources.

19. The network resource management system of any of claims 11-17, further comprising:

the VNFM module (143) or the CISM module (144) is further configured to associate the container object resource under the same VNF with the allocated virtual machine resource.

20. The network resource management system according to any of claims 11-17, further comprising a network element management device EM module (145) for container application configuration and management.

21. A network device, characterized in that the network device comprises 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 one of claims 1-10.

22. A computer readable storage medium storing one or more computer programs executable by one or more processors to implement the steps of the network resource management method of any of claims 1-10.