WO2021063130A1 - 网络资源管理方法、系统、网络设备和可读存储介质 - Google Patents

网络资源管理方法、系统、网络设备和可读存储介质 Download PDF

Info

Publication number
WO2021063130A1
WO2021063130A1 PCT/CN2020/110349 CN2020110349W WO2021063130A1 WO 2021063130 A1 WO2021063130 A1 WO 2021063130A1 CN 2020110349 W CN2020110349 W CN 2020110349W WO 2021063130 A1 WO2021063130 A1 WO 2021063130A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnf
container
virtual machine
deployment
life cycle
Prior art date
Application number
PCT/CN2020/110349
Other languages
English (en)
French (fr)
Inventor
谢宝国
巨满昌
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US17/764,158 priority Critical patent/US12034608B2/en
Priority to EP20872299.1A priority patent/EP4044507A4/en
Priority to KR1020227014166A priority patent/KR102674017B1/ko
Priority to JP2022519759A priority patent/JP7377965B2/ja
Publication of WO2021063130A1 publication Critical patent/WO2021063130A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • the embodiments of the present invention relate to, but are not limited to, the field of communications, and specifically, to, but are not limited to, network resource management methods, systems, network devices, and readable storage media.
  • NFV Network Functions Virtualization
  • the NFV system architecture defined by the European Telecommunications Standards Institute mainly includes: business operation support system and management support platform (OSS/BSS, Operation-Support System/Business Support System), virtual 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).
  • OSS/BSS Operation-Support System/Business Support System
  • VNF virtual Network functions
  • NFVI Virtualized Network Function
  • NFVI Network Functions Virtualization Infrastructure
  • NFV-MANO VNF-Management and Orchestration
  • NFVI is mainly responsible for comprehensively virtualizing hardware resources such as computing, storage, and networks, and mapping them into virtual resources
  • VNF uses software to implement various traditional physical network functions.
  • VNF runs on NFVI and uses process Virtual resources after NFVI virtualization.
  • NFV-MANO is responsible for managing and orchestrating the relationship between VNF and NFVI and the connection relationship between V
  • NFV-MANO includes: Virtualized Infrastructure Manager (VIM, Virtualized Infrastructure Manager), Virtual Network Function Manager (VNFM, Virtualized Network Function Manager), and Network Virtualization Function Orchestrator (NFVO, Network Function Virtualization Organizer).
  • VIM is responsible for the control and management of virtualized resources
  • VNFM is responsible for the life cycle management of VNF
  • NFVO is responsible for the orchestration and management of virtual infrastructure, and the life cycle management of network services (NS, Network Service).
  • the microservice architecture is the development and evolution direction of NFV technology, and the microservice architecture is based on the application of cloud native technology and container technology.
  • the container defines a standardized application release format, which greatly facilitates application development, deployment, and transplantation.
  • Technologies such as hierarchical mirroring and centralized mirroring warehouses adopted by containers promote the transformation of network elements into microservices and speed up software development and deployment.
  • the introduction of containers can meet the needs for rapid deployment of edge computing services, the need for edge computing network elements to improve resource utilization, and the need for 5G control plane networks to use containers for deployment.
  • the NFV standard has defined how to manage virtual machine (VM) resources in the VNF lifecycle management process, such as instantiation, elastic scaling, self-healing, termination, and other lifecycle management operations, such as virtual machines Operations such as resource quota and quota management, resource authorization management, resource allocation and recycling management.
  • VM virtual machine
  • NFV MANO, NFVO, VNFM, and VIM can enhance the support for containers, and in the lifecycle management operations of NS or VNF, the same network service
  • multiple VNFs in (NS, Network Service) distinguish and execute life cycle management operations using virtual machine resources, container resources are still used for life cycle management operations.
  • NS Network Service
  • the network resource management method, system, network device, and readable storage medium provided by the embodiments of the present invention solve the technical problem to a certain extent at least to provide that the virtual machine mode and the container mode can be arranged during life cycle management operations. Managed programs.
  • an embodiment of the present invention provides a network resource management method, including: a network virtualization function orchestrator NFVO module obtains a network service descriptor NSD and/or a virtual service descriptor from an OSS module of a business operation support system Network function descriptor VNFD, where VNFD includes descriptions of virtual machine resources and container resources; network function management and orchestration system MANO is deployed according to the life cycle strategy of NS or VNF, according to one of virtual machine mode, container mode, and mixed mode Perform life cycle management operations on NS or VNF.
  • the embodiment of the present invention also provides a network resource management system, including: an OSS module for sending NSD and/or VNFD to the NFVO module, where the VNFD includes descriptions of virtual machine resources and container resources; MANO, used for NS or
  • the life cycle deployment strategy of VNF is to perform life cycle management operations on NS or VNF according to one of virtual machine mode, container mode, and mixed mode.
  • the embodiment of the present invention also provides a network device, the network device includes a processor, a memory, and a communication bus; the communication bus is used to implement connection and communication between the processor and the memory; the processor is used to execute one or more computers stored in the memory Program to implement the steps of the above-mentioned network resource management method.
  • the embodiment of the present 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 above-mentioned network resource management method. .
  • Figure 1 is a diagram of the ETSI NFV system architecture in related technologies
  • Figure 2 is a functional block diagram of NFV MANO enhancement in an embodiment of the present invention.
  • Embodiment 3 is a flowchart of a network resource management method provided by Embodiment 1 of the present invention.
  • FIG. 4 is a block diagram of a virtual network function description VNFD provided by Embodiment 2 of the present invention.
  • FIG. 5 is a signal flow diagram of a network resource management method using virtual machines and container orchestration for different VNFs in the same NS according to the second embodiment of the present invention
  • FIG. 6 is a signal flow diagram of a network resource management method in which different VNFCs in the same VNF adopt the orchestration of virtual machines and containers according to Embodiment 3 of the present invention
  • FIG. 7 is a signal flow diagram of a network resource management method in which a VNF in the same NS adopts virtual machine, container, and mixed operations provided by the fourth embodiment of the present invention
  • Embodiment 8 is a schematic diagram of the composition of a network resource management system provided by Embodiment 5 of the present invention.
  • FIG. 9 is a schematic structural diagram of a network device according to Embodiment 6 of the present invention.
  • the current NFV system cannot support the orchestration of containers, so the container method cannot be introduced to perform life cycle management operations on NS/VNF.
  • the embodiments of the present invention propose a network resource management method and system, so that when the NS/VNF is performing life cycle management operations, it is possible to perform a hybrid orchestration of virtual machines and containers according to deployment, scenarios, and function realization needs.
  • Some network service realization scenarios require Orchestration using containers, such as URLLC ultra-low latency services; some location deployment scenarios require the use of containers for deployment, such as VNF or VNFC deployment to edge DCs.
  • VNF or VNFC deployment deployment to edge DCs.
  • virtual machines or containers can be deployed in a single or mixed deployment, so as to realize the ability of NFV to support containers.
  • NFV needs to be enhanced to adopt the VNFD (Virtualized Network Function Descriptor) data model description that supports the hybrid orchestration of virtual machine containers.
  • the VNFD includes both descriptions of virtual machine resources.
  • VDU-m also contains VDU-c describing container resources.
  • the enhanced VNFD can support single virtual machine orchestration, single container orchestration, and mixed orchestration of virtual machines and containers.
  • the deployment method of NS or VNF according to the network strategy and third-party requirements, there are three deployment methods of NS or VNF for virtual machine and container deployment for NS or VNF.
  • NS includes three deployment methods: virtual machine deployment, container deployment, and hybrid deployment of virtual machine containers;
  • NS virtual machine deployment mode that is, all VNFs in NS are deployed in virtual machine mode
  • VNFD uses VNFD-m.
  • the second type NS container deployment method, which expands the existing NFV's ability to support container deployment, and VNFD adopts the expanded VNFD-c for deployment.
  • the third type NS virtual machine container deployment method, which expands the existing NFV's ability to support container deployment.
  • different VNFs can use VNFD-m or VNFD-c to deploy VNF-m or VNF according to the deployment strategy. -c.
  • VNF virtual machine deployment, container deployment, and container-virtual machine hybrid deployment
  • VNF virtual machine deployment that is, all VNFCs in the VNF are deployed in the virtual machine mode, and the virtualized VNFCs are deployed using the VDU-m in the existing VNFD.
  • VNF container deployment method which expands the existing NFV's ability to support container deployment. All VNFCs in the VNF are deployed in the container method, and the containerized VNFCs are deployed using the VDU-c in the existing VNFD.
  • VNFC virtual machine container deployment method which expands the existing NFV's ability to support container deployment.
  • different VNFCs can use VDU-m or VDU-c to deploy virtualized VNFC according to the deployment strategy. Or containerized VNFC.
  • the embodiments of the present invention enhance the existing NFV MANO network elements and EMS to support the mixed orchestration function of virtual machines and containers, as shown in FIG. 2.
  • NS/VNF deployment strategies need to be formulated in NFVO and VNFM, and the VNF in NS should be decided to adopt virtual machine mode, container mode or a mixture of virtual machine and container
  • the orchestration method operates the life cycle management of VNF (such as instantiation, self-healing, shrinkage, termination), and downloads virtual machine images or container images according to the deployment strategy;
  • VNFM needs to execute the life cycle of the VNF according to the NS/VNF deployment strategy Manage operations, and decide that the VNFC in the same VNF adopts the virtual machine method, the container method, or the virtual machine and container hybrid orchestration method, and then performs the virtual machine or container resource calculation and generates the resource list;
  • VIM needs to support the creation of virtual machines while enhancing It supports the allocation
  • This embodiment provides a network resource management method. Please refer to FIG. 3.
  • the method includes:
  • the NFVO module of the network virtualization function orchestrator obtains the network service descriptor NSD and/or the virtualized network function descriptor VNFD from the OSS module of the business operation support system;
  • the network function management and orchestration system MANO performs life cycle management operations on the NS or VNF according to one of the virtual machine mode, container mode, and hybrid mode according to the life cycle deployment strategy of the NS or VNF.
  • the network function management and orchestration system MANO performs life cycle management operations on the NS or VNF in one of the virtual machine mode, container mode, and hybrid mode according to the life cycle deployment strategy of the NS or VNF.
  • the specific operations include: according to the NFVO module itself.
  • the NFVO module initiates a life cycle management service operation request to the virtual network function manager VNFM according to the life cycle deployment strategy and the corresponding life cycle management service;
  • the VNFM module executes the life cycle deployment strategy, and requests the VIM module of the virtualization basic setting manager to allocate resources.
  • the MANO general deployment strategy of the NFVO module itself is configured according to the requirements of operators and/or third parties.
  • the NSD carries the network service NS deployment strategy; and/or the VNFD carries the virtualized network function VNF deployment strategy.
  • generating the lifecycle deployment strategy includes:
  • NS deployment strategy in NSD and the MANO general deployment strategy configured in the NFVO module, generate an NS life cycle deployment strategy;
  • VNF life cycle deployment strategy is generated.
  • the NS life cycle deployment strategy includes any one of a virtual machine deployment strategy, a container deployment strategy, and a virtual machine container hybrid deployment strategy;
  • the VNF lifecycle deployment strategy includes any one of a virtual machine deployment strategy, a container deployment strategy, and a hybrid deployment strategy for virtual machine containers.
  • the composition of the VNFD includes at least one VDU-m for describing virtual machine resources and at least one VDU-c for describing container resources;
  • VDU-m includes the connection point CP-m description, the virtual computing node Computer-m description, and the virtual storage Storage-m description, corresponding to a virtual machine VM specification;
  • VDU-c contains the description of the connection point CP-c, the description of the virtual computing node Computer-c, and the description of the virtual storage Storage-c, corresponding to a container specification.
  • Figure 4 is an enhanced VNFD data model description that supports the description of mixed orchestration of virtual machine resources and container resources.
  • the left block diagram in Figure 4 shows the relationship between VNFD and VDU-m, VDU-c, VM, and Container template descriptions in the enhanced VNFD model in the design state.
  • VDU-m corresponds to the description of virtual machine resources
  • VDU-c corresponds to the container.
  • the description of the resource among them:
  • Each VNFD contains one or more VDU-m describing virtual machine resources, and one or more VDU-c describing container resources;
  • Each VDU-m contains a description of the connection point CP-m, a description of the virtual computing node Computer-m, and a description of the virtual storage Storage-m, corresponding to a VM virtual machine specification;
  • Each VDU-c contains a description of the connection point CP-c, a description of the virtual computing node Computer-c, and a description of the virtual storage Storage-c, corresponding to a Container container specification;
  • the right block diagram in Figure 4 shows the composition structure of the VNF configuration data in the running state (after instantiation), in which:
  • Each virtualized VNF-m is composed of one or more VNFCs running on the virtual machine;
  • Each containerized VNF-c is composed of one or more VNFCs running on the container;
  • Each VNFC has the attribute VDUID, which points to the VDU model in the VNFD, indicating that this VNFC is created based on the VDU-c and VDU-m;
  • Each VNFC instance corresponds to a virtual machine (VM), or a container group (POD).
  • VM virtual machine
  • POD container group
  • the enhanced VNFD supports virtual machine resource description (VDU-m) and container resource description (VDU-c), and supports mixed orchestration of VNF/VNFC.
  • VDU-m virtual machine resource description
  • VDU-c container resource description
  • MANO can use virtual machine mode and container mode to compare VNF/ VNFC performs life cycle management operations.
  • the VNFM module executing the life cycle deployment strategy and requesting the VIM to allocate resources includes:
  • the VNFM module generates the virtual machine resource list and/or container resource list required by the respective life cycle management services of the VNF according to the method adopted by the life cycle deployment strategy, and initiates resource authorization requirements to the VNFO;
  • a resource allocation request is initiated to the corresponding VIM; among them, the VIM module responsible for virtual machine resources allocates virtual machine resources and creates virtual machines; the VIM responsible for container resources Carry out the allocation of container resources, create a container, and download the image.
  • the lifecycle management service includes a VNF elasticity service
  • the containerized VNF is deployed on a virtual machine
  • the virtual machine is first elasticized and then the container is elasticized.
  • the method further includes:
  • the VNFM module configures the parameters of the life cycle management service of the VNF.
  • the method further includes:
  • the NFVO module obtains the NSD and/or VNFD from the OSS module; according to the MANO general deployment strategy configured by the NFVO module itself, and the deployment strategy carried in the NSD and/or VNFD, a life cycle is generated
  • Deployment strategy The NFVO module initiates a lifecycle management service operation request to the VNFM according to the lifecycle deployment strategy and the corresponding lifecycle management service; the VNFM module executes the lifecycle deployment strategy and requests the VIM module to allocate resources.
  • FIG. 5 is a signal flow diagram of a network resource management method provided by Embodiment 2 of the present invention.
  • This embodiment mainly describes the process of MANO supporting VNF hybrid orchestration in an NS deployment scenario.
  • NFVO After receiving the downloaded NSD/VNFD-m&c, NFVO generates an NS lifecycle deployment strategy based on the NS deployment strategy in the NSD and the MANO general deployment strategy configured by NFVO, and sends it to the VNFM.
  • VNFM deploys VNFs in different deployment locations and deployment scenarios in virtual machine mode or container mode, and completes life cycle management operations such as VNF instantiation.
  • NFVO finally completes the deployment of the entire NS.
  • the VNFs that make up the NS can be deployed in three ways: all deployed in a virtual machine mode, all deployed in a container mode, and deployed in a mixed mode of container and virtual machine.
  • FIG. 5 has the following steps:
  • S201 OSS performs on-boarding to NFVO, downloads NSD and each VNFD-m&c data model file, where NSD contains the VNFD-m&c id identification required by each VNF that composes NS, and in some examples, it may also include NS deployment strategy .
  • the NFVO side is also configured with a general MANO deployment strategy, so the NS deployment strategy can come from either the operator or a third party;
  • NS three deployment methods virtual machine deployment, container deployment, and virtual machine container hybrid deployment (this example only refers to a single hybrid deployment);
  • NS virtual machine deployment that is, the existing deployment method. All VNFs in NS are deployed in virtual machine mode, and VNFD uses the existing VNFD-m.
  • the second type NS container deployment method, which expands the existing NFV's ability to support container deployment, and VNFD adopts the expanded VNFD-c for deployment.
  • the third type NS virtual machine container hybrid deployment method, which expands the existing NFV's ability to support container deployment.
  • different VNFs can use VNFD-m or VNFD-c to deploy VNF-m or VNF according to requirements. -c.
  • NS deployment type decision NFVO generates an NS life cycle deployment strategy according to the NS deployment strategy in the NSD and the MANO general deployment strategy configured by itself. In the NS life cycle deployment strategy, decide which scenario and deployment location of the different VNFs that make up the NS to adopt container deployment, virtual machine deployment, and hybrid deployment of virtual machines and containers;
  • S203 OSS initiates an NS instantiation request to NFVO, and NFVO informs VNFM to initiate all VNF instantiation requests that make up NS according to the description of different types of VNFs contained in NSD (taking instantiation request as an example, it can be the life cycle management of other VNFs) Operations, such as VNF instantiation, shrinking, self-healing, termination, etc.), carrying NS instantiation deployment strategy (a type of NS life cycle deployment strategy, or other NS life cycle operation deployment strategies, such as shrinking deployment strategy) , Termination of deployment strategy, etc.), the strategy includes whether different VNF instantiations are deployed in virtual machine mode or container mode, and the method of obtaining virtual machine images and container images. If deployed in a virtual machine mode, the VNF needs to be instantiated with virtual machine resources; if deployed in a container mode, the VNF needs to be instantiated with container resources;
  • VNFM needs to be extended to support containers.
  • VNFs are deployed in different locations or different scenarios, and the virtual machine mode or container mode specified in the policy is used for deployment.
  • the VNF deployed in the edge DC is deployed in a container mode, and the VNF deployed in the central DC is deployed in the virtual machine mode;
  • the VNF used in the 5G URLLC scenario is deployed in the container mode, and the VNF deployed in the 5G eMBB scenario Deployed in a virtual machine mode; certain types of VNFs that support MTC services are deployed in containers, etc.
  • VNFM adopts virtual machine instantiation method or container instantiation method for VNF.
  • VNFD-m is used for VNF instantiation
  • VNFD-c is used for VNF instantiation, which is called virtualized VNF or containerized VNF.
  • the VNFM generates the virtual machine resource list or container resource list required for the respective instantiation of the VNF according to whether the virtual machine mode or the container mode is adopted for the VNF instantiation, and then initiates a resource authorization request to the NFVO.
  • the VNFM After NFVO is authorized, according to the VIM id in charge of virtual machine resources and the VIM id in charge of container resources indicated by NFVO, the VNFM initiates a resource allocation request to the VIM, and the VIM in charge of virtual machine resources allocates virtual machine resources and creates Virtual machine; the VIM responsible for container resources is responsible for the allocation of container resources and the creation of the container, and then downloads the image according to the image acquisition method in the NS instantiation deployment strategy. After the VIM resource allocation is completed, the VNFM configures the instantiated service parameters of the VNF.
  • VNF shrinkage In the life cycle management operation of VNF shrinkage, when the VNF or EM can initiate a VNF shrinkage request, it is necessary to perform different shrinkage for the virtualized VNF and the containerized VNF according to the NS elasticity deployment strategy.
  • the virtual machine When the container of the containerized VNF is deployed on a virtual machine (the virtual machine is used as the infrastructure), the virtual machine needs to be shrunk first, and then the container is shrunk (if the container is deployed on a bare metal server, this problem does not exist) ;
  • the VNFM can alert the NFVO, and the NFVO reassigns the VIM to allocate resources;
  • VNFs that make up the NS can be deployed in three ways: all deployed in a virtual machine mode, all deployed in a container mode, and deployed in a mixed mode of container and virtual machine.
  • VNFM selectively adopts virtual machine mode or container mode for VNF deployed in different scenarios and different regions Deploy, generate respective virtual machine resource lists or container resource lists and obtain NFVO resource authorization, and then apply for virtual machine resources and container resources to the corresponding VIM.
  • the image is downloaded according to the image access method in the policy, and service data is configured for the instantiated VNF.
  • the EMS is responsible for service configuration and management of the instantiated VNF.
  • CP connections and network topologies are created for the virtualized VNFs and containerized VNFs, and the NS instantiation operation is finally completed.
  • FIG. 6 is a signal flow diagram of a network resource management method provided by Embodiment 3 of the present invention.
  • This embodiment mainly describes the process of MANO supporting VNFC hybrid orchestration in a VNF deployment scenario.
  • VNFM When VNF is instantiated, after receiving VNFD-m&c and MANO general deployment strategy issued by NFVO, VNFM generates a VNF lifecycle deployment strategy according to the VNF deployment strategy and MANO general deployment strategy in VNFD-m&c.
  • the VNFM deploys VNFCs with different deployment locations and capabilities in a virtual machine mode or a container mode, and completes life cycle management operations such as VNFC instantiation.
  • VNFM After VNFC is instantiated, VNFM finally completes the deployment of the entire VNF.
  • the VNFCs that make up the VNF can be deployed in three ways: all deployed in a virtual machine mode, all deployed in a container mode, and deployed in a hybrid mode of container and virtual machine.
  • S301 OSS performs on-boarding to NFVO and downloads the VNF Package file.
  • the package file contains the VNFD-M&C data model file.
  • the VNFD-M&C may contain the VNF deployment strategy.
  • the NFVO side is also equipped with MANO general deployment strategies;
  • OSS initiates a VNF instantiation operation request to NFVO (taking an instantiation request as an example, it can be other VNF lifecycle management operations, such as VNF instantiation, shrinkage, self-healing, termination, etc.), carrying a certain VNFD- M&C id.
  • NFVO initiates VNF instantiation operation request to VNFM, and sends VNFD-M&C data model file and MANO general policy to VNFM.
  • VNFM needs to be expanded to support container deployment.
  • VNFM generates a VNF lifecycle deployment strategy based on the VNF deployment strategy in VNFD-C&M and the MANO general deployment strategy (this strategy includes VNF instantiation strategy, elasticity strategy, self-healing strategy, termination strategy, etc.).
  • this strategy includes VNF instantiation strategy, elasticity strategy, self-healing strategy, termination strategy, etc.
  • the VNF lifecycle deployment strategy it is decided in which scenario and under what capabilities the different VNFCs that make up the VNF adopt container deployment, virtual machine deployment, virtual machine and container hybrid deployment, and the method of obtaining virtual machine images and container images, etc. .
  • VNF virtual machine deployment, container deployment, and container-virtual machine hybrid deployment
  • VNF virtual machine deployment method that is, existing deployment method. All VNFCs in the VNF are deployed in the virtual machine method, and the virtualized VNFC adopts the VDU-m in the existing VNFD. Deploy.
  • VNF container deployment method which expands the existing NFV's ability to support container deployment. All VNFCs in the VNF are deployed in the container method, and the containerized VNFCs are deployed using the VDU-c in the existing VNFD.
  • VNFC virtual machine container deployment method which expands the existing NFV's ability to support container deployment. In the same VNF, different VNFs can use VDU-m or VDU-c to deploy virtualized VNFC or Containerize VNFC.
  • the VNFM adopts the virtual machine mode or container mode specified in the policy for deployment according to the VNF instantiation deployment strategy, the different capabilities of the VNFC or the different deployment locations.
  • the VNF instantiation deployment strategy the VNFC deployed in the edge DC is deployed in a container mode, and the VNFC deployed in the central DC is deployed in the virtual machine mode; the VNF with low latency and high reliability is deployed in a container mode, with high bandwidth and large capacity VNFs with processing capabilities are deployed in virtual machines; certain types of VNFCs that support MTC services are deployed in containers.
  • VNFM uses a virtual machine instantiation method or a container instantiation method for VNFC, corresponding to whether the VDU-m type in VNFD-M&C or the VDU-c type is used for VNF instantiation, which is called virtualized VNFC or containerized VNFC.
  • the VNFM calculates the virtual machine resources and container resources required by the VNF according to the virtual machine mode or the container mode according to the VNFC instantiation, and generates a unified VNF virtual resource list, where the VNF virtual resource list contains the virtual machines required by each VNFC Resource list or container resource list, and then initiate a resource authorization request to NFVO.
  • the VNFM After the NFVO is authorized, according to the VIM id responsible for the virtual machine resources and the VIM id responsible for the container resources indicated by the NFVO, the VNFM initiates a resource allocation request to the VIM, carrying a VNF virtual resource list.
  • the VIM responsible for virtual machine resources allocates the resources of the virtual machine according to the list of virtual machine resources in the list, and creates the virtual machine;
  • the VIM responsible for container resources allocates the resource of the container according to the list of container resources in the list, creates the container, and instantiates it according to the VNF
  • the image acquisition method in the deployment strategy is to download the respective virtual machine image or container image.
  • the VNFM creates a VNF topology and configures the parameters of the VNF instantiation service.
  • VNF Voice over IP
  • EMS needs to support VNF service configuration and management of the hybrid orchestration of virtual machines and containers, and add the newly instantiated VNF of the hybrid orchestration of virtual machines and containers to the management object to perform service configuration and management on the VNF.
  • the VNFCs that make up the VNF instance can be deployed in three ways: all deployed in a virtual machine mode, all deployed in a container mode, and deployed in a hybrid mode of container and virtual machine.
  • VNFM generates VNF lifecycle operation deployment strategies (instantiated deployment, flexible deployment, self-healing deployment, etc.).
  • VNFM selectively uses virtual machines or VNFCs for VNFCs with different capabilities or VNFCs deployed in different regions.
  • the VNF virtual resource list contains the virtual machine resource list or container resource list required by the VNFC and obtains the NFVO resource authorization, and then applies for the virtual machine resource and container resource to the corresponding VIM.
  • the virtual machine and container After the virtual machine and container are created, download the virtual machine image or container image according to the mirror access method in the policy, and configure service data for the instantiated VNF.
  • the EMS is responsible for business configuration and management of the instantiated virtual machine and container hybrid orchestration VNF.
  • FIG. 7 is a signal flow diagram of a network management method provided by Embodiment 4 of the present invention.
  • This embodiment mainly describes the process of MANO supporting VNF&VNFC hybrid orchestration in an NS deployment scenario.
  • NFVO After receiving the downloaded NSD/VNFD-m&c, NFVO generates an NS lifecycle deployment strategy based on the NS deployment strategy in NSD and the MANO general deployment strategy configured by NFVO, and sends it to VNFM;
  • VNFM receives NSD/VNFD-m&c Afterwards, the VNF life cycle deployment strategy is generated according to the VNF deployment strategy in the VNFD and the MANO general deployment strategy.
  • the VNFM deploys the VNF forming the NS in a virtual machine mode, a container mode, or a hybrid mode.
  • Figure 7 has the following steps:
  • S401 OSS performs on-boarding to NFVO, downloads NSD and each VNFD-M&C data model file.
  • the NSD contains the VNFD-M&C id identifiers required by each VNF constituting the NS. In some examples, it may include the NS deployment strategy.
  • the NFVO side On the NFVO side, according to the needs of the operator or a third party, the NFVO side also has its own MANO general deployment strategy, so the NS deployment strategy can come from the operator or a third party;
  • NS three deployment methods virtual machine deployment, container deployment, and virtual machine container hybrid deployment (including single hybrid deployment and complex hybrid deployment);
  • NS virtual machine deployment that is, the existing deployment method. All VNFs in NS are deployed in virtual machine mode, and VNFD uses the existing VNFD-m.
  • the second type NS container deployment method, which expands the existing NFV's ability to support container deployment, and VNFD adopts the expanded VNFD-c for deployment.
  • the third type NS virtual machine container deployment method, which expands the existing NFV's ability to support container deployment.
  • different VNFs can use VNFD-m or VNFD-c to deploy VNF-m or VNF- according to requirements. c.
  • a single hybrid deployment method indicates that a VNF can only be deployed using the same resource; a complex hybrid deployment method indicates that a VNF can be deployed using multiple resources. For example, different VNFCs in a VNF can be deployed using virtual machine resources or container resources. .
  • NS deployment type decision NFVO generates an NS life cycle deployment strategy according to the NS deployment strategy in the NSD and the MANO general deployment strategy configured by itself. In the NS life cycle deployment strategy, decide which scenario and deployment location of the different VNFs that make up the NS to adopt container deployment, virtual machine deployment, virtual machine and container hybrid deployment (single mode or complex mode);
  • OSS initiates an NS instantiation request to NFVO, and NFVO informs VNFM to initiate all VNF instantiation requests that make up NS according to the description of different types of VNFs contained in NSD (taking instantiation request as an example, it can be the life cycle management of other VNFs) Operations, such as VNF instantiation, shrinking, self-healing, termination, etc.), carrying NS instantiation deployment strategy (a type of NS life cycle deployment strategy, or other NS life cycle operation deployment strategies, such as shrinking deployment strategy) , Termination of deployment strategy, etc.), the strategy includes different VNF instantiation deployments in virtual machine mode, container mode deployment, hybrid deployment (referring to the complex deployment mode in hybrid orchestration), virtual machine image and container image acquisition methods, etc.
  • VNF needs to be instantiated with virtual machine resources; if deployed in container mode, VNF needs to be instantiated with container resources; if deployed in mixed mode, VNF needs to be instantiated with virtual machine resources and machine resources at the same time;
  • VNFM needs to be extended to support containers.
  • VNFs are deployed in different locations or different scenarios, and the virtual machine mode or container mode specified in the policy is used for deployment.
  • the VNF deployed in the edge DC is deployed in a container mode, and the VNF deployed in the central DC is deployed in the virtual machine mode;
  • the VNF used in the 5G URLLC scenario is deployed in the container mode, and the VNF deployed in the 5G eMBB scenario Deployed in a virtual machine mode; certain types of VNFs that support MTC services are deployed in containers, etc.
  • VNFM adopts virtual machine instantiation method or container instantiation method for VNF.
  • VNFD-m is used for VNF instantiation
  • VNFD-c is used for VNF instantiation, which is called virtualized VNF or containerized VNF.
  • VNFM generates a VNF lifecycle deployment strategy based on the VNF deployment strategy in VNFD-C&M and the MANO general deployment strategy (this strategy includes VNF instantiation strategy, elasticity strategy, self-healing strategy, termination strategy, etc.).
  • this strategy includes VNF instantiation strategy, elasticity strategy, self-healing strategy, termination strategy, etc.
  • VNF lifecycle deployment strategy it is decided in which scenario and under what capabilities the different VNFCs that make up the hybrid VNF adopt container deployment and virtual machine deployment, and how to obtain virtual machine images and container images.
  • VNF mixed deployment mode In the same VNF, different VNFCs that make up the VNF can be instantiated by using VDU-m or VDU-c according to the strategy, and deployed as a virtualized VNFC or a containerized VNFC.
  • VNFM uses virtual machine mode, container mode, and mixed mode to calculate the virtual machine resources, container resources, and mixed resources of virtual machine containers required by the VNF, and generate the virtual machine resources required for the respective instantiation of the VNF List, container resource list, or mixed resource list, and then initiate a resource authorization request to NFVO.
  • VNFM After NFVO is authorized, according to the VIM id in charge of virtual machine resources and the VIM id in charge of container resources indicated by NFVO, the VNFM initiates a resource allocation request to the VIM, and the VIM in charge of virtual machine resources allocates virtual machine resources and creates Virtual machine:
  • the VIM responsible for container resources is responsible for the allocation of container resources and the creation of the container, and then downloads the virtual machine image or container image according to the image acquisition method in the NS instantiation deployment strategy or the VNF instantiation deployment strategy.
  • the VNFM configures the instantiated service parameters of the VNF.
  • VNF creates a virtual machine.
  • EMS needs to support containerized and hybridized VNF service configuration and management, and add newly instantiated virtualized VNFs, containerized VNFs, and hybridized VNFs to management objects, and add new containerized VNFs and hybridized VNFs
  • the VNFs that make up the NS can be deployed in three ways: all deployed in a virtual machine mode, all deployed in a container mode, and deployed in a mixed mode of container and virtual machine.
  • VNFM selectively deploys VNFs deployed in different scenarios and regions in virtual machine mode, container mode or mixed mode.
  • VNFs in mixed mode are deployed according to the different capabilities of VNFC. Different deployment locations use different virtual machine methods or container methods for deployment.
  • VNFM generates its own virtual machine resource list, container resource list, or mixed resource list, and obtains NFVO resource authorization, and then applies for virtual machine resources and container resources to the corresponding VIM.
  • the image is downloaded according to the image access method in the policy, and service data is configured for the instantiated VNF.
  • the EMS is responsible for service configuration and management of the instantiated VNF.
  • CP connections and network topologies are created for the virtualized VNF, containerized VNF, and hybridization, and finally the NS instantiation operation is completed.
  • This embodiment provides a network resource management system. Please refer to FIG. 8.
  • the system includes:
  • the OSS module 81 is used to send the NSD and/or VNFD to the NFVO module 82, where the VNFD includes descriptions of virtual machine resources and container resources;
  • MANO82 is used to perform life cycle management operations on NS or VNF in one of virtual machine mode, container mode, and hybrid mode according to the life cycle deployment strategy of NS or VNF.
  • the NFVO module 83 is used to obtain the NSD and/or VNFD, and generate the life cycle deployment strategy according to the MANO general deployment strategy configured by itself, and the deployment strategy carried in the NSD and/or VNFD, and according to the life cycle deployment strategy, and corresponding Life cycle management business, initiate life cycle management business operation request to VNFM;
  • the VNFM module 84 is used to execute the life cycle deployment strategy and request the VIM to allocate resources;
  • the VIM module 85 is used for resource allocation.
  • the MANO general deployment strategy of the NFVO module 83 itself is configured according to the requirements of the operator and/or the third party.
  • the NSD carries the network service NS deployment strategy; and/or the VNFD carries the virtualized network function VNF deployment strategy.
  • generating the lifecycle deployment strategy includes:
  • NS deployment strategy in NSD and the MANO general deployment strategy configured in NFVO module 83, generate an NS life cycle deployment strategy;
  • VNF life cycle deployment strategy is generated.
  • the NS lifecycle deployment strategy includes any one of a virtual machine deployment strategy, a container deployment strategy, and a virtual machine container hybrid deployment strategy;
  • the VNF lifecycle deployment strategy includes any one of a virtual machine deployment strategy, a container deployment strategy, and a hybrid deployment strategy for virtual machine containers.
  • the composition of the VNFD includes at least one VDU-m for describing virtual machine resources and at least one VDU-c for describing container resources;
  • VDU-m includes the connection point CP-m description, the virtual computing node Computer-m description, and the virtual storage Storage-m description, corresponding to a virtual machine VM specification;
  • VDU-c contains the description of the connection point CP-c, the description of the virtual computing node Computer-c, and the description of the virtual storage Storage-c, corresponding to a container specification.
  • the VNFM module 84 executing the life cycle deployment strategy and requesting the VIM to allocate resources includes:
  • the VNFM module 84 generates the virtual machine resource list and/or container resource list required by the respective life cycle management services of the VNF according to the method adopted by the life cycle deployment strategy, and initiates resource authorization requirements to the VNFO;
  • the VIM module 85 responsible for virtual machine resources allocates virtual machine resources and creates virtual machines; responsible for container resources The VIM allocates container resources to create a container and download the image.
  • the lifecycle management service includes a VNF elasticity service
  • the containerized VNF is deployed on a virtual machine
  • the virtual machine is first elasticized and then the container is elasticized.
  • the VNFM module 84 is further used to configure the parameters of the life cycle management service of the VNF after the VIM performs resource allocation.
  • the method further includes:
  • the network resource management system includes an OSS module 81, used to send NSD and/or VNFD to NFVO module 83; NFVO module 83, used to obtain NSD and/or VNFD, according to its own configured MANO general deployment Strategy, and deployment strategy carried in NSD and/or VNFD, generate life cycle deployment strategy, and according to life cycle deployment strategy and corresponding life cycle management service, initiate life cycle management service operation request to VNFM; VNFM module 84, It is used to execute the life cycle deployment strategy and request VIM to allocate resources; the VIM module 85 is used to allocate resources.
  • This provides a solution for orchestrating and managing the virtual machine mode and the container mode when performing life cycle management operations, and improves its application.
  • This embodiment also provides a network device, as shown in FIG. 9, which includes a processor 91, a memory 92, and a communication bus 93, where:
  • the communication bus 93 is used to implement connection and communication between the processor 91 and the memory 92;
  • the processor 91 is configured to execute one or more computer programs stored in the memory 92 to implement the steps of the network resource management method in the foregoing embodiments, and details are not described herein again.
  • This embodiment also provides a computer-readable storage medium, which is included in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules, or other data). Volatile or non-volatile, removable or non-removable media.
  • Computer-readable storage media include but are not limited to RAM (Random Access Memory), ROM (Read-Only Memory, read-only memory), EEPROM (Electrically Erasable Programmable read only memory, charged Erasable Programmable Read-Only Memory) ), flash memory or other storage technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage systems, Or any other medium that can be used to store desired information and that can be accessed by a computer.
  • the computer-readable storage medium in this embodiment can be used to store one or more computer programs, and the stored one or more computer programs can be executed by a processor to implement at least one of the network resource management methods in the foregoing embodiments. step.
  • This embodiment also provides a computer program (or computer software).
  • the computer program can be distributed on a computer-readable medium and executed by a computable system to implement at least the network resource management methods in the foregoing embodiments.
  • This embodiment also provides a computer program product, including a computer readable system, on which the computer program as shown above is stored.
  • the computer-readable system in this embodiment may include the computer-readable storage medium as shown above.
  • the network virtualization function orchestrator NFVO module obtains the network service descriptor NSD and/or virtualized network function from the OSS module of the business operation support system Descriptor VNFD, where VNFD includes descriptions of virtual machine resources and container resources; network function management and orchestration system MANO according to the NS or VNF life cycle deployment strategy, according to one of the virtual machine mode, container mode, mixed mode to NS or VNF performs life cycle management operations.
  • VNFD includes descriptions of virtual machine resources and container resources
  • network function management and orchestration system MANO according to the NS or VNF life cycle deployment strategy, according to one of the virtual machine mode, container mode, mixed mode to NS or VNF performs life cycle management operations.
  • communication media usually contain computer-readable instructions, data structures, computer program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery medium. Therefore, the present invention is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Stored Programmes (AREA)

Abstract

一种网络资源管理方法、系统、网络设备和可读存储介质，方法包括：网络虚拟化功能编排器NFVO模块从业务运营支撑系统OSS模块获取网络服务描述符NSD和/或虚拟化网络功能描述符VNFD，其中VNFD中包括虚机资源及容器资源的描述(S11)；网络功能管理和编排系统MANO根据NS或VNF的生命周期部署策略，按虚机方式、容器方式、混编方式之一对NS或VNF进行生命周期管理操作(S12)。

Description

网络资源管理方法、系统、网络设备和可读存储介质
相关申请的交叉引用
本申请基于申请号为201910944775.7、申请日为2019年9月30日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本发明实施例涉及但不限于通信领域，具体而言，涉及但不限于网络资源管理方法、系统、网络设备和可读存储介质。
背景技术
网络功能虚拟化(NFV，Network Functions Virtualization)是一种通过使用通用硬件以及虚拟化技术来承载其他功能的软件处理技术，旨在降低网络昂贵的设备成本。NFV通过软硬件解耦及功能抽象，使网络设备功能不再依赖于专用硬件，资源可以充分灵活共享，实现新业务的快速开发和部署，并基于实际业务需求进行自动部署、弹性伸缩、故障隔离和自愈等。
如图1所示，欧洲电信标准协会(ETSI，European Telecommunications Standards Institute)定义的NFV系统架构主要包含：业务运营支撑系统和管理支撑平台(OSS/BSS，Operation-Support System/Business Support System)、虚拟化的网络功能(VNF，Virtualized Network Function)、网络功能虚拟化基础设施(NFVI，Network Functions Virtualization Infrastructure)和网络功能虚拟化管理和编排系统(NFV-MANO，VNF-Management and Orchestration)。其中，NFVI主要负责将计算、存储以及网络等硬件资源全面虚拟化，并映射成虚拟资源；VNF则是利用软件来实现各种传统的物理网络功能，VNF运行在NFVI之上，使用的是经过NFVI虚拟化后的虚拟资源。NFV-MANO负责管理和编排VNF和NFVI之间的关系以及VNF之间和\或与其他物理网络功能(PNF，Physical Network Functions之间的连接关系。
NFV-MANO中包含：虚拟化基础设置管理器(VIM，Virtualized Infrastructure Manager)、虚拟网络功能管理器(VNFM，Virtualized Network Function Manager)和网络虚拟化功能编排器(NFVO，Network Function Virtualization Orchestrator)。VIM负责控制和管理虚拟化资源；VNFM负责VNF的生命周期管理；NFVO负责对虚拟基础设施的编排和管理，以及对网络服务(NS，Network Service)的生命周期管理。
微服务架构是NFV技术的发展与演进方向，微服务架构又基于云原生技术与容器技术的应用。容器作为一种应用打包的技术，定义了标准化的应用发布格式，极大方便了应用的开发、部署和移植。容器采用的分层镜像、集中式镜像仓库等技术，促进网元的微服务化改造，可加快软件开发部署。引入容器，可以满足边缘计算类业务快速部署的需求，以及边缘计算类网元提高资源利用率的需求，及5G控制面网络采用容器进行部署的需求。
目前NFV标准中已经定义在VNF生命周期管理过程中，如在实例化，弹性伸缩，自愈，终止等生命周期管理操作时，如何对虚机(VM，Virtual Machine)资源进行管理，如虚机资源的配额与限额管理、资源授权管理、资源分配与回收管理等操作。如果在NFV标准中引入容器，涉及虚机及容器的混合编排，需要解决NFV MANO的不同实体NFVO、VNFM、VIM如何增强支持容器，以及在NS或VNF的生命周期管理操作中，同一个网络服务(NS，Network Service)中的多个VNF如果区分及执行采用虚机资源进行生命周期管理操作，还是采用容器资源进行生命周期管理操作。但相关规范中还没有容器及虚机混合编排的机制。
发明内容
本发明实施例提供的网络资源管理方法、系统、网络设备和可读存储介质，至少在一定程度上解决的技术问题是提供在进行生命周期管理操作时，能对虚机方式和容器方式进行编排管理的方案。
为至少在一定程度上解决上述技术问题，本发明实施例提供一种网络资源管理方法，包括：网络虚拟化功能编排器NFVO模块从业务运营支撑系统OSS模块获取网络服务描述符NSD和/或虚拟化网络功能描述符VNFD，其中VNFD中包括虚机资源及容器资源的描述；网络功能管理和编排系统MANO根据NS或VNF的生命周期部署策略，按虚机方式、容器方式、混编方式之一对NS或VNF进行生命周期管理操作。
本发明实施例还提供一种网络资源管理系统，包括：OSS模块，用于发送NSD和/或VNFD至NFVO模块，其中VNFD中包括虚机资源及容器资源的描述；MANO，用于根据NS或VNF的生命周期部署策略，按虚机方式、容器方式、混编方式之一对NS或VNF进行生命周期管理操作。
本发明实施例还提供一种网络设备，网络设备包括处理器、存储器及通信总线；通信总线用于实现处理器和存储器之间的连接通信；处理器用于执行存储器中存储的一个或者多个计算机程序，以实现上述的网络资源管理方法的步骤。
本发明实施例还提供一种计算机存储介质，计算机可读存储介质存储有一个或者多个程序，一个或者多个程序可被一个或者多个处理器执行，以实现上述的网络资源管理方法的步骤。
本发明其他特征和相应的有益效果在说明书的后面部分进行阐述说明，且应当理解，至少部分有益效果从本发明说明书中的记载变的显而易见。
附图说明
图1为相关技术中ETSI NFV系统架构图；
图2为本发明实施例中的NFV MANO增强的功能框图；
图3为本发明实施例一提供的网络资源管理方法流程图；
图4为本发明实施例二提供的虚拟网络功能描述VNFD框图；
图5为本发明实施例二提供的同一NS中的不同VNF采用虚机、容器编排的网络资源管理方法信号流图；
图6为本发明实施例三提供的同一VNF中的不同VNFC采用虚机、容器的编排的网络资源管理方法信号流图；
图7为本发明实施例四提供的同一NS中的VNF采用虚机、容器、混编的操作的网络资源管理方法信号流图；
图8为本发明实施例五提供的一种网络资源管理系统组成示意图；
图9为本发明实施例六提供的一种网络设备结构示意图。
具体实施方式
为了使本发明的目的、技术方案及优点更加清楚明白，下面通过具体实施方式结合附图对本发明实施例作进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本发明，并不用于限定本发明。
当前NFV系统不能支持容器的编排，因此无法引入容器方式对NS/VNF进行生命周期管理操作。本发明各实施例提出网络资源管理方法和系统，使得在NS/VNF进行生命周期管理操作时，能根据部署、场景、功能实现需要进行虚机及容器的混合编排，有的网络业务实现场景需要采用容器方式进行编排，如URLLC超低时延业务；有的位置部署场景需要采用容器进行部署，如VNF或VNFC部署到边缘DC。不特定需要采用容器部署或业务实现的场景，根据第三方需求可采用虚机或容器单一部署，或进行混合部署，从而实现NFV支持容器的能力。
根据下文的不同的实施例，给出了NFV需要增强采用支持虚机容器混合编排的VNFD(Virtualized Network Function Descriptor，虚拟化网络功能描述符)数据模型描述，在VNFD中既包含描述虚机资源的VDU-m，也包含描述容器资源的VDU-c。采用增强的VNFD，可以支持单一虚机的编排、单一容器的编排、虚机及容器的混合编排。
NS或VNF的部署方式，根据网络策略及第三方需求，对NS或VNF采用虚机及容器部署有NS三种部署方式，VNF三种部署方式。
NS包括三种部署方式：虚机部署，容器部署，虚机容器混合部署；
NS的三种部署方式中，第一种：NS虚机部署方式，即NS中所有的VNF采用虚机方式进行部署，VNFD采用VNFD-m。第二种：NS容器部署方式，扩展了已有NFV支持容器部署的能力，VNFD采用扩展的VNFD-c进行部署。第三种：NS虚机容器部署方式，扩展了已有NFV支持容器部署的能力，在一个NS中，不同的VNF可根据部署策略，采用VNFD-m或VNFD-c来部署VNF-m或VNF-c。
VNF三种部署方式：虚机部署，容器部署，容器虚机混合部署；
VNF的三种部署方式中，第一种：VNF虚机部署方式，即VNF中所有的VNFC采用虚机方式进行部署，虚机化VNFC采用已有的VNFD中的VDU-m进行部署。第二种：VNF容器部署方式，扩展了已有NFV支持容器部署的能力，VNF中所有的VNFC采用容器方式进行部署，容器化VNFC采用已有的VNFD中的VDU-c进行部署。第三种：VNFC虚机容器部署方式，扩展了已有NFV支持容器部署的能力，在同一个VNF中，不同的VNFC可根据部署策略，采用VDU-m或VDU-c来部署虚机化VNFC或容器化VNFC。
本发明各实施例对已有NFV MANO各网元以及EMS的进行了增强，以支持虚机及容器混合编排功能，参见图2所示。如果要支持虚机容器混合编排，除了VNFD需要增强支持容器参数外，在NFVO及VNFM还需要制定NS/VNF部署策略，并决策NS中的VNF采用虚机方式、容器方式或虚机及容器混合编排方式对VNF的生命周期管理(如实例化、自愈、弹缩、终止)进行操作，并根据部署策略下载虚机镜像或容器镜像；VNFM需要根据NS/VNF部署策略，执行VNF的生命周期管理操作，并决策同一VNF中的VNFC采用虚机方式、容器方式或虚机及容器混合编排方式，然后进行虚机或容器资源计算、生成资源列表；VIM需要在支持创建虚机的同时，增强支持基于容器的计算资源、存储资源、网络资源分配，并创建容器。
下面通过具体的实施例，来描述如何在容器化VNF生命周期管理过程中，对网络资源进行管理。
实施例一：
本实施例提供了一种网络资源管理方法，请参考图3，该方法包括：
S11、网络虚拟化功能编排器NFVO模块从业务运营支撑系统OSS模块获取网络服务描述符NSD和/或虚拟化网络功能描述符VNFD；
S12、网络功能管理和编排系统MANO根据NS或VNF的生命周期部署策略，按虚机方式、容器方式、混编方式之一对NS或VNF进行生命周期管理操作。
其中，网络功能管理和编排系统MANO根据NS或VNF的生命周期部署策略，按虚机方式、容器方式、混编方式之一对NS或VNF进行生命周期管理操作具体可以包括：根据NFVO模块自身已配置的MANO通用部署策略，以及NSD和/或VNFD中携带的部署策略三种中的至少一种，生成NS或VNF的生命周期部署策略；
S13、NFVO模块根据生命周期部署策略，以及对应的生命周期管理业务，向虚拟网络功能管理器VNFM发起生命周期管理业务的操作请求；
S14、VNFM模块执行生命周期部署策略，并请求虚拟化基础设置管理器VIM模块进行资源分配。
在一些实施例中，NFVO模块自身的MANO通用部署策略为根据运营商和/或第三方需求而配置。
在一些实施例中，NSD中，携带网络服务NS部署策略；和/或VNFD中，携带虚拟化网络功能VNF部署策略。
在一些实施例中，根据NFVO模块自身已配置的MANO通用部署策略，以及NSD和/或VNFD中携带的部署策略，生成生命周期部署策略包括：
根据NSD中的NS部署策略，以及NFVO模块中配置的MANO通用部署策略，生成NS生命周期部署策略；或，
根据VNFD中的VNF部署策略，以及NFVO模块中配置的MANO通用部署策略，生成VNF生命周期部署策略。
在一些实施例中，NS生命周期部署策略中，包括虚机部署策略、容器部署策略以及 虚机容器混合部署策略中的任意一种；
VNF生命周期部署策略中，包括虚机部署策略、容器部署策略以及虚机容器混合部署策略中的任意一种。
在一些实施例中，VNFD的组成中，包括至少一个用于描述虚机资源的VDU-m，以及至少一个用于描述容器资源的VDU-c；
VDU-m中包括连接点CP-m描述，虚拟计算节点Computer-m描述以及虚拟存储Storage-m描述，对应于一种虚机VM规格；
VDU-c中包含连接点CP-c描述，虚拟计算节点Computer-c描述以及虚拟存储Storage-c描述，对应一种容器Container规格。
其中，请参考图4，图4是增强的VNFD数据模型描述，支持虚机资源及容器资源混合编排的描述。图4中左侧框图中为设计态下增强的VNFD模型中VNFD与VDU-m、VDU-c及VM、Container模板描述的关联关系，VDU-m对应虚机资源的描述，VDU-c对应容器资源的描述。其中：
每个VNFD中包含一个或多个描述虚机资源的VDU-m，以及一个或多个描述容器资源的VDU-c；
每个VDU-m中包含连接点CP-m描述，虚拟计算节点Computer-m描述以及虚拟存储Storage-m描述，对应一种VM虚机规格；
每个VDU-c中包含连接点CP-c描述，虚拟计算节点Computer-c描述以及虚拟存储Storage-c描述，对应一种Container容器规格；
图4中右侧框图为运行态(实例化后)下VNF配置数据的组成结构，其中：
每个虚机化VNF-m由一个或者多个运行在虚机上的VNFC组成；
每个容器化VNF-c由一个或者多个运行在容器上的VNFC组成；
每个VNFC都具有属性VDUID，指向VNFD中VDU模型，表明此VNFC是根据该VDU-c、VDU-m进行创建的；
每个VNFC实例对应一个虚拟机(VM)，或一个容器组(POD)。
在本实施例中，增强的VNFD支持虚机资源描述(VDU-m)及容器资源描述(VDU-c)，支持VNF/VNFC的混合编排，MANO可分别采用虚机方式及容器方式对VNF/VNFC进行生命周期管理操作。
在一些实施例中，VNFM模块执行生命周期部署策略，并请求VIM进行资源分配包括：
VNFM模块根据生命周期部署策略采用的方式，生成VNF各自的生命周期管理业务所需的虚机资源列表和/或容器资源列表，并向VNFO发起资源授权要求；
根据NFVO模块在授权后所指示的负责相应方式的VIM id，向相应的VIM发起资源分配请求；其中，负责虚机资源的VIM模块进行虚机资源的分配，创建虚机；负责容器资源的VIM进行容器资源的分配创建容器，并下载镜像。
在一些实施例中，当生命周期管理业务包括VNF弹缩业务时，若容器化VNF部署在虚机之上，则先进行虚机的弹缩，再进行容器的弹缩。
在一些实施例中，在VIM模块进行资源分配之后，还包括：
VNFM模块对VNF进行生命周期管理业务的参数配置。
在一些实施例中，在VNFM模块对VNF进行生命周期管理业务的参数配置之后，还包括：
通知NFVO模块以及EMS模块生命周期管理业务完成。
根据本实施例提供的网络资源管理方法，NFVO模块从OSS模块获取NSD和/或VNFD；根据NFVO模块自身已配置的MANO通用部署策略，以及NSD和/或VNFD中携带的部署策略，生成生命周期部署策略；NFVO模块根据生命周期部署策略，以及对应的生命周期管理业务，向VNFM发起生命周期管理业务的操作请求；VNFM模块执行生命周期部署策略，并请求VIM模块进行资源分配。从而提供了一种在进行生命周期管理操作时，能对虚机方式和容器方式进行编排管理的方案，完善了其应用。
实施例二
图5为本发明的实施例二提供的网络资源管理方法信号流图，该实施例主要描述NS部署场景下，MANO支持VNF混合编排的流程。NFVO在收到下载的NSD/VNFD-m&c后，根据NSD中的NS部署策略及NFVO配置的MANO通用部署策略生成NS生命周期部署策略，并下发给VNFM。VNFM根据所述部署策略，对不同部署位置及部署场景的VNF采用虚机方式或容器方式进行部署，并完成VNF实例化等生命周期管理操作，NFVO最终完成整个NS的部署操作。在该NS部署操作中，组成NS的VNF可以是全部按虚机方式部署、全部按容器方式部署、按容器及虚机混合方式部署这三种方式进行部署。
图5具有如下步骤：
S201：OSS向NFVO进行on-boarding，下载NSD及各个VNFD-m&c数据模型文件，其中NSD中包含组成NS的各VNF所需的VNFD-m&c id标识，在一些示例中，还可以包含NS部署策略。
在NFVO侧，根据运营商或第三方需求，NFVO侧也自身配置有MANO通用部署策略，因此NS部署策略既可来自运营商，也可以来自第三方；
NS三种部署方式：虚机部署，容器部署，虚机容器混合部署(该实例例仅指单一混合部署)；
NS的三种部署方式中，第一种：NS虚机部署方式，即已有部署方式，NS中所有的VNF采用虚机方式进行部署，VNFD采用已有的VNFD-m。第二种：NS容器部署方式，扩展了已有NFV支持容器部署的能力，VNFD采用扩展的VNFD-c进行部署。第三种：NS虚机容器混合部署方式，扩展了已有NFV支持容器部署的能力，在一个NS中，不同的VNF可根据需求，采用VNFD-m或VNFD-c来部署VNF-m或VNF-c。
S202：NS部署类型决策：NFVO根据NSD中的NS部署策略及自身配置的MANO通用部署策略，生成NS生命周期部署策略。在NS生命周期部署策略中，决策组成NS的不 同VNF在何种场景、何种部署位置采用容器部署、虚机部署、虚机及容器混合部署；
S203：OSS向NFVO发起NS实例化请求，NFVO根据NSD中包含的不同类型VNF描述，向VNFM通知发起组成NS的所有VNF实例化请求(以实例化请求为例，可以是其他VNF的生命周期管理操作，如VNF实例化、弹缩、自愈、终止等操作)，携带NS实例化部署策略(NS生命周期部署策略的一种，也可以是NS其他生命周期操作部署策略，如弹缩部署策略，终止部署策略等)，策略中包含不同的VNF实例化采用虚机方式部署还是容器方式部署，虚机镜像及容器镜像的获取方式等。如果虚机方式部署，VNF需要采用虚机资源进行实例化，如果容器方式部署，VNF需要采用容器资源进行实例化；
S204：VNFM需要扩展支持容器，根据NS实例化部署策略，VNF部署在不同位置或不同场景，就采用策略里规定的虚机方式或容器方式进行部署。如根据NS实例化部署策略，部署在边缘DC的VNF采用容器方式部署，部署在中心DC的VNF采用虚机方式部署；用于5G URLLC场景的VNF采用容器方式部署，用于5G eMBB场景的VNF采用虚机方式进行部署；某类支持MTC业务的VNF采用容器部署等。
VNFM针对VNF采用虚机实例化方式，还是容器实例化方式，对应采用VNFD-m来进行VNF实例化，还是VNFD-c来进行VNF实例化，称作虚机化VNF或容器化VNF。
S205：VNFM根据VNF实例化采用虚机方式还是容器方式，生成VNF各自的实例化所需的虚机资源列表或容器资源列表，然后向NFVO发起资源授权请求。
S206：NFVO授权后，根据NFVO指示的负责虚机资源的VIM id，以及负责容器资源的VIM id，VNFM向所述VIM发起资源分配请求，负责虚机资源的VIM进行虚机资源的分配，创建虚机；负责容器资源的VIM负责容器资源的分配并创建容器，然后根据NS实例化部署策略中的镜像获取方式去下载镜像。VIM资源分配完成后，VNFM对VNF进行实例化业务参数配置。
在VNF弹缩的生命周期管理操作中，当VNF或EM可以发起VNF弹缩请求需要根据NS弹缩部署策略，对虚机化VNF及容器化VNF执行不同的弹缩。
当容器化VNF的容器部署在虚机之上时(虚机作为基础设施)，先要进行虚机的弹缩，然后再进行容器的弹缩(若容器部署在裸机服务器，不存在此问题)；
但弹缩资源不足时，VNFM能向NFVO进行告警，由NFVO重新指定VIM分配资源；
S207：VNF实例化完成后，通知NFVO及EMS实例化完成。EMS需要支持容器化的VNF业务配置及管理，并将新实例化的虚机化VNF及容器化VNF添加到管理对象，对容器化VNF进行业务配置及管理。在该NS部署操作中，组成NS的VNF可以是全部按虚机方式部署、全部按容器方式部署、按容器及虚机混合方式部署这三种方式进行部署。
S208：NS中的所有VNF实例化完成后，对NS中所有的VNF进行CP点连接及拓扑创建，最终完成NS的实例化操作。
在本流程中，根据NFVO的NS生命周期操作部署策略(实例化部署、弹缩部署、自愈部署等)，VNFM对部署在不同场景、不同区域的VNF选择性的采用虚机方式或容器方式进行部署，生成各自的虚机资源列表或容器资源列表并获得NFVO资源授权，然后向相应的VIM申请虚机资源及容器资源。虚机及容器创建后，根据策略中的镜像访问方式下载 镜像，并为实例化的VNF配置业务数据。VNF实例化完成后，EMS负责对实例化后的VNF进行业务配置及管理。当所有的VNF实例化后，对虚机化VNF、容器化VNF创建CP连接及网络拓扑，最终完成NS实例化操作。
实施例三
图6为本发明的实施例三提供的网络资源管理方法信号流图，该实施例主要描述VNF部署场景下，MANO支持VNFC混合编排的流程。VNF实例化时，VNFM在收到NFVO下发的VNFD-m&c及MANO通用部署策略后，根据VNFD-m&c中的VNF部署策略及MANO通用部署策略生成VNF生命周期部署策略。VNFM根据所述部署策略，对不同部署位置及能力的VNFC采用虚机方式或容器方式进行部署，并完成VNFC实例化等生命周期管理操作。VNFC实例化完成后，VNFM最终完成整个VNF的部署操作。在该VNF部署操作中，组成VNF的VNFC可以是全部按虚机方式部署、全部按容器方式部署、按容器及虚机混合方式部署这三种方式进行部署。
图6具有如下步骤：
S301：OSS向NFVO进行on-boarding，下载VNF Package包文件，包文件中包含VNFD-M&C数据模型文件，在一些示例中，VNFD-M&C中可包含VNF部署策略。
在NFVO侧，根据运营商或第三方需求，NFVO侧也自身配置有MANO通用部署策略；
S302：OSS向NFVO发起VNF实例化操作请求(以实例化请求为例，可以是其他VNF的生命周期管理操作，如VNF实例化、弹缩、自愈、终止等操作)，携带某个VNFD-M&C id。NFVO向VNFM发起VNF实例化操作请求，并将VNFD-M&C数据模型文件以及MANO通用策略发送给VNFM。
S303：VNF部署类型决策：VNFM需要扩展支持容器部署方式。VNFM根据VNFD-C&M中的VNF部署策略及MANO通用部署策略，生成VNF生命周期部署策略(该策略中包含VNF实例化策略、弹缩策略、自愈策略、终止策略等)。在VNF生命周期部署策略中，决策组成VNF的不同VNFC在何种场景、何种能力状况下采用容器部署、虚机部署、虚机及容器混合部署，以及虚机镜像及容器镜像的获取方式等。
VNF三种部署方式：虚机部署，容器部署，容器虚机混合部署；
VNF的三种部署方式中，第一种：VNF虚机部署方式，即已有部署方式，VNF中所有的VNFC采用虚机方式进行部署，虚机化VNFC采用已有的VNFD中的VDU-m进行部署。第二种：VNF容器部署方式，扩展了已有NFV支持容器部署的能力，VNF中所有的VNFC采用容器方式进行部署，容器化VNFC采用已有的VNFD中的VDU-c进行部署。第三种：VNFC虚机容器部署方式，扩展了已有NFV支持容器部署的能力，在同一个VNF中，不同的VNF可根据需求，采用VDU-m或VDU-c来部署虚机化VNFC或容器化VNFC。
S304：VNFM根据VNF实例化部署策略，VNFC的不同能力或部署的不同位置，采用策略里规定的虚机方式或容器方式进行部署。如根据VNF实例化部署策略，部署在边缘DC的VNFC采用容器方式部署，部署在中心DC的VNFC采用虚机方式部署；具有低时延高可靠能力的VNF采用容器方式部署，具有高带宽大容量处理能力的VNF采用虚机 方式进行部署；某类支持MTC业务的VNFC采用容器部署等。
VNFM针对VNFC采用虚机实例化方式，还是容器实例化方式，对应采用VNFD-M&C中的VDU-m类型，还是VDU-c类型来进行VNF实例化，称作虚机化VNFC或容器化VNFC。
S305：VNFM根据VNFC实例化采用虚机方式还是容器方式，计算VNF所需的虚机资源、容器资源，生成统一的VNF虚拟资源列表，其中VNF虚拟资源列表中包含了各个VNFC所需的虚机资源列表或容器资源列表，然后向NFVO发起资源授权请求。
S306：NFVO授权后，根据NFVO指示的负责虚机资源的VIM id，以及负责容器资源的VIM id，VNFM向所述VIM发起资源分配请求，携带VNF虚拟资源列表。负责虚机资源的VIM根据列表中的虚机资源列表进行虚机的资源分配，创建虚机；负责容器资源的VIM根据列表中的容器资源列表进行容器的资源分配，创建容器，根据VNF实例化部署策略中的镜像获取方式去下载各自的虚机镜像或容器镜像。
各个VNFC实例化完成后，VNFM创建VNF拓扑，并对VNF进行实例化业务参数配置。
S307：VNF实例化完成后，通知NFVO及EMS实例化完成。EMS需要支持虚机及容器混合编排的VNF业务配置及管理，并将新实例化的虚机及容器混合编排的VNF添加到管理对象，对该VNF进行业务配置及管理。在该VNF部署操作中，组成VNF实例的VNFC可以全部按虚机方式部署、全部按容器方式部署、按容器及虚机混合方式部署这三种方式进行部署。
在本流程中，VNFM生成VNF生命周期操作部署策略(实例化部署、弹缩部署、自愈部署等)，VNFM对不同能力的VNFC，或部署在不同区域的VNFC选择性的采用虚机方式或容器方式进行部署，在VNF虚拟资源列表中包含了VNFC所需的虚机资源列表或容器资源列表并获得NFVO资源授权，然后向相应的VIM申请虚机资源及容器资源。虚机及容器创建后，根据策略中的镜像访问方式下载虚机镜像或容器镜像，并为实例化的VNF配置业务数据。VNF实例化完成后，EMS负责对实例化后的虚机及容器混合编排的VNF进行业务配置及管理。
实施例四
图7为本发明的实施例四提供的网络管理方法信号流图，该实施例主要描述NS部署场景下，MANO支持VNF&VNFC混合编排的流程。NFVO在收到下载的NSD/VNFD-m&c后，根据NSD中的NS部署策略及NFVO配置的MANO通用部署策略生成NS生命周期部署策略，并下发给VNFM；VNFM在收到NSD/VNFD-m&c后，根据VNFD中的VNF部署策略及MANO通用部署策略生成VNF生命周期部署策略。VNFM根据所述NS部署策略及VNF部署策略，对组成NS的VNF采用虚机方式、容器方式或混编方式进行部署。
图7具有如下步骤：
S401：OSS向NFVO进行on-boarding，下载NSD及各个VNFD-M&C数据模型文件，NSD中包含组成NS的各VNF所需的VNFD-M&C id标识，在一些示例中，可包含NS部署策略。
在NFVO侧，根据运营商或第三方需求，NFVO侧也自身配置有MANO通用部署策 略，因此NS部署策略既可来自运营商，也可以来自第三方；
NS三种部署方式：虚机部署，容器部署，虚机容器混合部署(包含单一混合部署、复杂混合部署两种模式)；
NS的三种部署方式中，第一种：NS虚机部署方式，即已有部署方式，NS中所有的VNF采用虚机方式进行部署，VNFD采用已有的VNFD-m。第二种：NS容器部署方式，扩展了已有NFV支持容器部署的能力，VNFD采用扩展的VNFD-c进行部署。第三种：NS虚机容器部署方式，扩展了已有NFV支持容器部署的能力，在一个NS中，不同的VNF可根据需求，采用VNFD-m或VNFD-c来部署VNF-m或VNF-c。其中，单一混合部署方式，表明一个VNF只能使用同一种资源部署；复杂混合部署方式，表明一个VNF可以使用多种资源进行部署，如VNF中的不同VNFC可以使用虚机资源或容器资源进行部署。
S402：NS部署类型决策：NFVO根据NSD中的NS部署策略及自身配置的MANO通用部署策略，生成NS生命周期部署策略。在NS生命周期部署策略中，决策组成NS的不同VNF在何种场景、何种部署位置采用容器部署、虚机部署、虚机及容器混合部署(单一模式还是复杂模式)；
S403：OSS向NFVO发起NS实例化请求，NFVO根据NSD中包含的不同类型VNF描述，向VNFM通知发起组成NS的所有VNF实例化请求(以实例化请求为例，可以是其他VNF的生命周期管理操作，如VNF实例化、弹缩、自愈、终止等操作)，携带NS实例化部署策略(NS生命周期部署策略的一种，也可以是NS其他生命周期操作部署策略，如弹缩部署策略，终止部署策略等)，策略中包含不同的VNF实例化采用虚机方式部署、容器方式部署、混编方式部署(指混合编排里的复杂部署模式)，虚机镜像及容器镜像的获取方式等。如果虚机方式部署，VNF需要采用虚机资源进行实例化；如果容器方式部署，VNF需要采用容器资源进行实例化；如果混编方式部署，VNF需要同时采用虚机资源及器资源进行实例化；
S404：VNFM需要扩展支持容器，根据NS实例化部署策略，VNF部署在不同位置或不同场景，就采用策略里规定的虚机方式或容器方式进行部署。如根据NS实例化部署策略，部署在边缘DC的VNF采用容器方式部署，部署在中心DC的VNF采用虚机方式部署；用于5G URLLC场景的VNF采用容器方式部署，用于5G eMBB场景的VNF采用虚机方式进行部署；某类支持MTC业务的VNF采用容器部署等。
VNFM针对VNF采用虚机实例化方式，还是容器实例化方式，对应采用VNFD-m来进行VNF实例化，还是VNFD-c来进行VNF实例化，称作虚机化VNF或容器化VNF。
如果VNF采用混编方式进行实例化，需要进行VNF部署类型决策。VNFM根据VNFD-C&M中的VNF部署策略及MANO通用部署策略，生成VNF生命周期部署策略(该策略中包含VNF实例化策略、弹缩策略、自愈策略、终止策略等)。在VNF生命周期部署策略中，决策组成混编VNF的不同VNFC在何种场景、何种能力状况下采用容器部署及虚机部署，以及虚机镜像及容器镜像的获取方式等。
VNF混编部署方式：在同一个VNF中，组成VNF的不同VNFC可根据策略，采用VDU-m或VDU-c来进行实例化，部署为虚机化VNFC或容器化VNFC。
S405：VNFM根据VNF实例化采用虚机方式、容器方式及混编方式，计算VNF所需虚机资源、容器资源、虚机容器的混编资源，生成VNF各自的实例化所需的虚机资源列表、容器资源列表或混编资源列表，然后向NFVO发起资源授权请求。
S406：NFVO授权后，根据NFVO指示的负责虚机资源的VIM id，以及负责容器资源的VIM id，VNFM向所述VIM发起资源分配请求，负责虚机资源的VIM进行虚机资源的分配，创建虚机；负责容器资源的VIM负责容器资源的分配并创建容器，然后根据NS实例化部署策略或VNF实例化部署策略中的镜像获取方式去下载虚机镜像或容器镜像。VIM资源分配完成后，VNFM对VNF进行实例化业务参数配置。
S407：VNF实例化完成后，通知NFVO及EMS实例化完成。EMS需要支持容器化、混编化的VNF业务配置及管理，并将新实例化的虚机化VNF、容器化VNF、混编化VNF添加到管理对象，新增对容器化VNF、混编化VNF进行业务配置及管理的能力。在该NS部署操作中，组成NS的VNF可以是全部按虚机方式部署、全部按容器方式部署、按容器及虚机混合方式部署这三种方式进行部署。
S408：NS中的所有VNF实例化完成后，对NS中所有的VNF进行CP点连接及拓扑创建，最终完成NS的实例化操作。
在本流程中，根据NFVO的NS生命周期操作部署策略(NS实例化部署、NS弹缩部署、NS自愈部署等)，以及VNFM的VNF生命周期操作部署策略(VNF实例化部署、VNF弹缩部署、VNF自愈部署等)，VNFM对VNF部署在不同场景、不同区域的VNF选择性的采用虚机方式、容器方式或混编方式进行部署，对混编方式的VNF根据VNFC的不同能力、不同部署位置采用不同的虚机方式或容器方式进行部署。VNFM生成各自的虚机资源列表、容器资源列表或混编资源列表，并获得NFVO资源授权，然后向相应的VIM申请虚机资源及容器资源。虚机及容器创建后，根据策略中的镜像访问方式下载镜像，并为实例化的VNF配置业务数据。VNF实例化完成后，EMS负责对实例化后的VNF进行业务配置及管理。当所有的VNF实例化后，对虚机化VNF、容器化VNF、混编化创建CP连接及网络拓扑，最终完成NS实例化操作。
实施例五
本实施例提供了一种网络资源管理系统，请参考图8，该系统包括：
OSS模块81，用于发送NSD和/或VNFD至NFVO模块82，其中VNFD中包括虚机资源及容器资源的描述；
MANO82，用于根据NS或VNF的生命周期部署策略，按虚机方式、容器方式、混编方式之一对NS或VNF进行生命周期管理操作。
NFVO模块83，用于获取NSD和/或VNFD，根据自身已配置的MANO通用部署策略，以及NSD和/或VNFD中携带的部署策略，生成生命周期部署策略，以及根据生命周期部署策略，以及对应的生命周期管理业务，向VNFM发起生命周期管理业务的操作请求；
VNFM模块84，用于执行生命周期部署策略，并请求VIM进行资源分配；
VIM模块85，用于资源分配。
在一些实施例中，NFVO模块83自身的MANO通用部署策略为根据运营商和/或第三方需求而配置。
在一些实施例中，NSD中，携带网络服务NS部署策略；和/或VNFD中，携带虚拟化网络功能VNF部署策略。
在一些实施例中，根据NFVO模块83自身已配置的MANO通用部署策略，以及NSD和/或VNFD中携带的部署策略，生成生命周期部署策略包括：
根据NSD中的NS部署策略，以及NFVO模块83中配置的MANO通用部署策略，生成NS生命周期部署策略；或，
根据VNFD中的VNF部署策略，以及NFVO模块83中配置的MANO通用部署策略，生成VNF生命周期部署策略。
在一些实施例中，NS生命周期部署策略中，包括虚机部署策略、容器部署策略以及虚机容器混合部署策略中的任意一种；
VNF生命周期部署策略中，包括虚机部署策略、容器部署策略以及虚机容器混合部署策略中的任意一种。
在一些实施例中，VNFD的组成中，包括至少一个用于描述虚机资源的VDU-m，以及至少一个用于描述容器资源的VDU-c；
VDU-m中包括连接点CP-m描述，虚拟计算节点Computer-m描述以及虚拟存储Storage-m描述，对应于一种虚机VM规格；
VDU-c中包含连接点CP-c描述，虚拟计算节点Computer-c描述以及虚拟存储Storage-c描述，对应一种容器Container规格。
在一些实施例中，VNFM模块84执行生命周期部署策略，并请求VIM进行资源分配包括：
VNFM模块84根据生命周期部署策略采用的方式，生成VNF各自的生命周期管理业务所需的虚机资源列表和/或容器资源列表，并向VNFO发起资源授权要求；
根据NFVO模块83在授权后所指示的负责相应方式的VIM id，向相应的VIM发起资源分配请求；其中，负责虚机资源的VIM模块85进行虚机资源的分配，创建虚机；负责容器资源的VIM进行容器资源的分配创建容器，并下载镜像。
在一些实施例中，当生命周期管理业务包括VNF弹缩业务时，若容器化VNF部署在虚机之上，则先进行虚机的弹缩，再进行容器的弹缩。
在一些实施例中，VNFM模块84还用于：在VIM进行资源分配之后，对VNF进行生命周期管理业务的参数配置。
在一些实施例中，在VNFM模块84对VNF进行生命周期管理业务的参数配置之后，还包括：
通知NFVO模块83以及EMS模块生命周期管理业务完成。
根据本实施例提供的网络资源管理系统，包括OSS模块81，用于发送NSD和/或VNFD 至NFVO模块83；NFVO模块83，用于获取NSD和/或VNFD，根据自身已配置的MANO通用部署策略，以及NSD和/或VNFD中携带的部署策略，生成生命周期部署策略，以及根据生命周期部署策略，以及对应的生命周期管理业务，向VNFM发起生命周期管理业务的操作请求；VNFM模块84，用于执行生命周期部署策略，并请求VIM进行资源分配；VIM模块85，用于资源分配。从而提供了一种在进行生命周期管理操作时，能对虚机方式和容器方式进行编排管理的方案，完善了其应用。
实施例六
本实施例还提供了一种网络设备，参见图9所示，其包括处理器91、存储器92及通信总线93，其中：
通信总线93用于实现处理器91和存储器92之间的连接通信；
处理器91用于执行存储器92中存储的一个或者多个计算机程序，以实现上述各实施例中的网络资源管理方法的步骤，这里不再赘述。
本实施例还提供了一种计算机可读存储介质，该计算机可读存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、计算机程序模块或其他数据)的任何方法或技术中实施的易失性或非易失性、可移除或不可移除的介质。计算机可读存储介质包括但不限于RAM(Random Access Memory，随机存取存储器)，ROM(Read-Only Memory，只读存储器)，EEPROM(Electrically Erasable Programmable read only memory，带电可擦可编程只读存储器)、闪存或其他存储器技术、CD-ROM(Compact Disc Read-Only Memory，光盘只读存储器)，数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储系统、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。
本实施例中的计算机可读存储介质可用于存储一个或者多个计算机程序，其存储的一个或者多个计算机程序可被处理器执行，以实现上述各实施例中的网络资源管理方法的至少一个步骤。
本实施例还提供了一种计算机程序(或称计算机软件)，该计算机程序可以分布在计算机可读介质上，由可计算系统来执行，以实现上述各实施例中的网络资源管理方法的至少一个步骤。
本实施例还提供了一种计算机程序产品，包括计算机可读系统，该计算机可读系统上存储有如上所示的计算机程序。本实施例中该计算机可读系统可包括如上所示的计算机可读存储介质。
本发明实施例的有益效果是：
根据本发明实施例提供的网络资源管理方法、系统、网络设备和可读存储介质，网络虚拟化功能编排器NFVO模块从业务运营支撑系统OSS模块获取网络服务描述符NSD和/或虚拟化网络功能描述符VNFD，其中VNFD中包括虚机资源及容器资源的描述；网络功能管理和编排系统MANO根据NS或VNF的生命周期部署策略，按虚机方式、容器方式、混编方式之一对NS或VNF进行生命周期管理操作。从而提供了一种在进行生命周期管理操作时，能对虚机方式和容器方式进行编排管理的方案。
可见，本领域的技术人员应该明白，上文中所公开方法中的全部或某些步骤、系统、 系统中的功能模块/单元可以被实施为软件(可以用计算系统可执行的计算机程序代码来实现)、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。
此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、计算机程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。所以，本发明不限制于任何特定的硬件和软件结合。
以上内容是结合具体的实施方式对本发明实施例所作的进一步详细说明，不能认定本发明的具体实施只局限于这些说明。对于本发明所属技术领域的普通技术人员来说，在不脱离本发明构思的前提下，还可以做出若干简单推演或替换，都应当视为属于本发明的保护范围。

Claims (15)

  1. 一种网络资源管理方法，包括：
    网络虚拟化功能编排器NFVO模块从业务运营支撑系统OSS模块获取网络服务描述符NSD和/或虚拟化网络功能描述符VNFD，其中VNFD中包括虚机资源及容器资源的描述；
    网络功能管理和编排系统MANO根据NS或VNF的生命周期部署策略，按虚机方式、容器方式、混编方式之一对NS或VNF进行生命周期管理操作。
  2. 如权利要求1所述的网络资源管理方法，其中，所述网络功能管理和编排系统MANO根据NS或VNF的生命周期部署策略，按虚机方式、容器方式、混编方式之一对NS或VNF进行生命周期管理操作包括：
    根据所述NFVO模块自身已配置的MANO通用部署策略，以及所述NSD和/或VNFD中携带的部署策略三种中的至少一种，生成所述NS或VNF的生命周期部署策略；
    所述NFVO模块根据所述生命周期部署策略，以及对应的生命周期管理服务，向虚拟网络功能管理器VNFM模块发起所述生命周期管理业务的操作请求；
    VNFM模块执行所述生命周期部署策略，并请求虚拟化基础设置管理器VIM模块进行资源分配。
  3. 如权利要求2所述的网络资源管理方法，其中，所述NFVO模块自身的MANO通用部署策略为根据运营商和/或第三方需求而配置。
  4. 如权利要求2所述的网络资源管理方法，其中，所述NSD中，携带网络服务NS部署策略；和/或所述VNFD中，携带虚拟化网络功能VNF部署策略。
  5. 如权利要求4所述的网络资源管理方法，其中，所述根据所述NFVO模块自身已配置的MANO通用部署策略，以及所述NSD和/或VNFD中携带的部署策略，生成生命周期部署策略包括：
    根据NSD中的NS部署策略，以及所述NFVO模块中配置的MANO通用部署策略，生成NS生命周期部署策略；或，
    根据VNFD中的VNF部署策略，以及所述NFVO模块中配置的MANO通用部署策略，生成VNF生命周期部署策略。
  6. 如权利要求5所述的网络资源管理方法，其中，所述NS生命周期部署策略中，包括虚机部署策略、容器部署策略以及虚机容器混合部署策略中的任意一种；
    所述VNF生命周期部署策略中，包括虚机部署策略、容器部署策略以及虚机容器混合部署策略中的任意一种。
  7. 如权利要求1-6任一项所述的网络资源管理方法，其中，所述VNFD的组成中，包括至少一个用于描述虚机资源的VDU-m，以及至少一个用于描述容器资源的VDU-c；
    所述VDU-m中包括连接点CP-m描述，虚拟计算节点Computer-m描述以及虚拟存储Storage-m描述，对应于一种虚机VM规格；
    所述VDU-c中包含连接点CP-c描述，虚拟计算节点Computer-c描述以及虚拟存储Storage-c描述，对应一种容器Container规格。
  8. 如权利要求2所述的网络资源管理方法，其中，所述VNFM模块执行所述生命周期部署策略，并请求VIM进行资源分配包括：
    VNFM模块根据所述生命周期部署策略采用的方式，生成VNF各自的生命周期管理业务所需的虚机资源列表和/或容器资源列表，并向VNFO发起资源授权要求；
    根据NFVO模块在授权后所指示的负责相应方式的VIM id，向相应的VIM发起资源分配请求；其中，负责虚机资源的VIM模块进行虚机资源的分配，创建虚机；负责容器资源的VIM进行容器资源的分配创建容器，并下载镜像。
  9. 如权利要求8所述的网络资源管理方法，其中，当所述生命周期管理业务包括VNF弹缩业务时，若容器化VNF部署在虚机之上，则先进行虚机的弹缩，再进行容器的弹缩。
  10. 如权利要求2所述的网络资源管理方法，其中，在所述VIM模块进行资源分配之后，还包括：
    所述VNFM模块对VNF进行生命周期管理业务的参数配置。
  11. 如权利要求10所述的网络资源管理方法，其中，在所述VNFM模块对VNF进行生命周期管理业务的参数配置之后，还包括：
    通知NFVO模块以及EMS模块所述生命周期管理业务完成。
  12. 一种网络资源管理系统，包括：
    OSS模块，用于发送NSD和/或VNFD至NFVO模块，其中VNFD中包括虚机资源及容器资源的描述；
    MANO，用于根据NS或VNF的生命周期部署策略，按虚机方式、容器方式、混编方式之一对NS或VNF进行生命周期管理操作。
  13. 如权利要求11所述的网络资源管理系统，其中，所述VNFM模块还用于：在所述VIM进行资源分配之后，对VNF进行生命周期管理业务的参数配置。
  14. 一种网络设备，包括：处理器、存储器及通信总线；其中：
    所述通信总线用于实现处理器和存储器之间的连接通信；
    所述处理器用于执行存储器中存储的一个或者多个计算机程序，以实现如权利要求1-11中任一项所述的网络资源管理方法的步骤。
  15. 一种计算机可读存储介质，存储有一个或者多个计算机程序，其中所述一个或者多个计算机程序可被一个或者多个处理器执行，以实现如权利要求1-11中任一项所述的网络资源管理方法的步骤。
PCT/CN2020/110349 2019-09-30 2020-08-20 网络资源管理方法、系统、网络设备和可读存储介质 WO2021063130A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US17/764,158 US12034608B2 (en) 2019-09-30 2020-08-20 Network resource management method and system, network equipment and readable storage medium
EP20872299.1A EP4044507A4 (en) 2019-09-30 2020-08-20 NETWORK RESOURCE MANAGEMENT METHOD AND APPARATUS, NETWORK EQUIPMENT AND READABLE STORAGE MEDIUM
KR1020227014166A KR102674017B1 (ko) 2019-09-30 2020-08-20 네트워크 자원 관리 방법, 시스템, 네트워크 디바이스 및 판독 가능한 저장 매체
JP2022519759A JP7377965B2 (ja) 2019-09-30 2020-08-20 ネットワークリソース管理方法、システム、ネットワーク機器と可読記憶媒体

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910944775.7A CN112583625B (zh) 2019-09-30 2019-09-30 网络资源管理方法、系统、网络设备和可读存储介质
CN201910944775.7 2019-09-30

Publications (1)

Publication Number Publication Date
WO2021063130A1 true WO2021063130A1 (zh) 2021-04-08

Family

ID=75117312

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/110349 WO2021063130A1 (zh) 2019-09-30 2020-08-20 网络资源管理方法、系统、网络设备和可读存储介质

Country Status (5)

Country Link
EP (1) EP4044507A4 (zh)
JP (1) JP7377965B2 (zh)
KR (1) KR102674017B1 (zh)
CN (1) CN112583625B (zh)
WO (1) WO2021063130A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113472848A (zh) * 2021-05-31 2021-10-01 济南浪潮数据技术有限公司 一种虚拟机和容器的网络融合方法、装置及相关设备
CN114143181B (zh) * 2021-10-23 2023-02-07 西安电子科技大学 一种意图驱动的空间信息网络编排系统及方法
CN117675439A (zh) * 2022-08-31 2024-03-08 华为技术有限公司 创建虚拟网络的方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106533935A (zh) * 2015-09-14 2017-03-22 华为技术有限公司 一种在云计算系统中获取业务链信息的方法和装置
WO2017166136A1 (zh) * 2016-03-30 2017-10-05 华为技术有限公司 一种vnf的资源分配方法及装置
WO2018174897A1 (en) * 2017-03-24 2018-09-27 Nokia Technologies Oy Methods and apparatuses for multi-tiered virtualized network function scaling
CN109885377A (zh) * 2018-11-23 2019-06-14 中国银联股份有限公司 统一资源调度协调器及其创建虚拟机和/或容器的方法、统一资源调度系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2017378718B2 (en) * 2016-12-22 2021-01-28 Nicira, Inc. Collecting and processing context attributes on a host
US11070432B2 (en) * 2017-07-20 2021-07-20 Cisco Technology, Inc. Dynamic and customizable virtual network functions
CN111385114B (zh) * 2018-12-28 2022-04-26 华为技术有限公司 Vnf服务实例化方法及装置
US10931507B2 (en) * 2019-06-25 2021-02-23 Vmware, Inc. Systems and methods for selectively implementing services on virtual machines and containers

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106533935A (zh) * 2015-09-14 2017-03-22 华为技术有限公司 一种在云计算系统中获取业务链信息的方法和装置
WO2017166136A1 (zh) * 2016-03-30 2017-10-05 华为技术有限公司 一种vnf的资源分配方法及装置
WO2018174897A1 (en) * 2017-03-24 2018-09-27 Nokia Technologies Oy Methods and apparatuses for multi-tiered virtualized network function scaling
CN109885377A (zh) * 2018-11-23 2019-06-14 中国银联股份有限公司 统一资源调度协调器及其创建虚拟机和/或容器的方法、统一资源调度系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4044507A4 *

Also Published As

Publication number Publication date
US20220329495A1 (en) 2022-10-13
KR102674017B1 (ko) 2024-06-12
KR20220070020A (ko) 2022-05-27
CN112583625B (zh) 2023-12-08
JP7377965B2 (ja) 2023-11-10
JP2022550402A (ja) 2022-12-01
EP4044507A1 (en) 2022-08-17
EP4044507A4 (en) 2023-10-11
CN112583625A (zh) 2021-03-30

Similar Documents

Publication Publication Date Title
US10701139B2 (en) Life cycle management method and apparatus
US11960915B2 (en) Method and apparatus for creating virtual machine based on parameter information of a virtual network interface card
WO2021063130A1 (zh) 网络资源管理方法、系统、网络设备和可读存储介质
JP6834033B2 (ja) ネットワークスライス管理方法、ユニット、及びシステム
US20220075666A1 (en) Containerized vnf deployment method and related device
US20240031309A1 (en) Data Processing Method, Apparatus, Device and Storage Medium
WO2017080391A1 (zh) 一种网络服务部署方法和装置
EP3839726B1 (en) Software modification initiation method and apparatus
WO2017185303A1 (zh) 一种nfv mano策略描述符的管理方法及装置
CN109428764B (zh) 虚拟网络功能的实例化方法
WO2020103925A1 (zh) 一种容器化虚拟网络功能的部署方法和装置
US20230261950A1 (en) Method of container cluster management and system thereof
US20220225170A1 (en) VNF Instantiation Method, NFVO, VIM, VNFM, and System
KR20220104241A (ko) 네트워크 작업 방법, 장치, 설비 및 저장매체
EP4177742A1 (en) Multitenancy management method and apparatus
WO2020108443A1 (zh) 一种虚拟化管理方法及装置
CN113342456A (zh) 一种连接方法、装置、设备和存储介质
WO2023046026A1 (zh) 一种容器化vnf的部署方法及装置
CN112015515B (zh) 一种虚拟网络功能的实例化方法及装置
WO2021004320A1 (zh) 服务资源许可管理方法和相关设备
US12034608B2 (en) Network resource management method and system, network equipment and readable storage medium
WO2019011180A1 (zh) 一种License的发送方法和装置
WO2021129520A1 (zh) 网络业务的生命周期管理的授权方法及装置
JP2024524398A (ja) コンテナクラスタのストレージリソースを管理するための方法および装置、ならびにシステム
CN117201336A (zh) 一种边缘用户服务切片生成方法、装置、设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20872299

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022519759

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20227014166

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020872299

Country of ref document: EP

Effective date: 20220502