Resource allocation system and method based on hybrid cloud and network function virtualization

Abstract

The invention provides a resource allocation system and method based on hybrid cloud and network function virtualization, and the system comprises a hybrid cloud management platform and an infrastructure module, and the infrastructure module is used for accessing different types of cloud resource pools and managing the data of the different types of cloud resource pools; and the hybrid cloud management platform is used for receiving the cloud resource pool data through different interfaces, inputting virtual network element data through an NFV-MANO arrangement module, and performing resource matching degree calculation on the virtual network element data according to the different types of cloud resource pool data to obtain a matching result corresponding to the cloud resource pool data. By fusing an NFV-MANO system to a hybrid cloud management platform and cooperating with uniform resource access of private cloud and public cloud type resource pools, the problems of complex management, insufficient resource elasticity, low operation and maintenance efficiency and the like caused by multiple types of resource pools and multiple MANO systems in a distributed communication network element scene are solved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a resource allocation system and method based on hybrid cloud and network function virtualization. Background Art

[0002] As the de facto standard for network function virtualization, ETSI's NFV architecture virtualizes and cloudifies traditional communication equipment by introducing IT technology to meet the needs of digital and intelligent transformation and development in the communication field. Unlike the strong coupling of software and hardware in traditional physical devices, the concept of NFV is to virtualize standardized network functions into software entities running on general hardware. The NFV architecture consists of three parts: network function virtualization infrastructure NFVI, virtual network function VNF, and NFV management and orchestration system MANO. Among them, NFV-MANO is equivalent to the management plane of the NFV architecture, which uniformly manages and orchestrates the VNFs and NFVIs on the business plane.

[0003] At the same time, the cloud computing field has entered the era of hybrid cloud, which is the main choice for enterprises to go to the cloud. Hybrid cloud collaborates with private cloud and public cloud to improve the utilization rate of users' cross-cloud resources and is suitable for distributed business scenarios. In the field of communications, with the advent of the post-5G era, user-side services are sinking to the edge and showing distributed characteristics. As a result, operators gradually tend to move virtualized communication network element functions to hybrid cloud to meet the distributed deployment mode, such as deploying the user-side network elements of the 5G core network in the private cloud of the industrial park, and centrally deploying the control plane on the public cloud nodes of prefecture-level cities or provincial capitals.

[0004] Prior art 1, patent publication number CN117640423A proposes a NFV orchestration system and method in a distributed NFV scenario, which solves the security of information interaction between multiple MANO nodes by introducing blockchain technology in the lower layer of the MANO layer.

[0005] Prior art 2: ETSI's NFV architecture introduces a WIM management module, which mainly solves the connectivity and unified management issues between multiple NFVI equipment pools at POP points in a wide area network.

[0006] However, none of the above solutions can solve the problem that different types of distributed network elements in hybrid cloud scenarios have multiple MANO management systems, which causes complex operation and maintenance. Summary of the invention

[0007] The present application shows a resource allocation system and method based on hybrid cloud and network function virtualization.

[0008] In a first aspect, the present application shows a resource allocation system based on hybrid cloud and network function virtualization, the system comprising: a hybrid cloud management platform and an infrastructure module, the hybrid cloud management platform at least comprising an NFV-MANO orchestration module and a resource unified access management module, the NFV-MANO orchestration module and the resource unified access management module are connected, wherein the NFV-MANO orchestration module at least comprises an NFV orchestration unit, a VNF management unit and a virtual resource unified management unit;

[0009] The infrastructure module is used to access different types of cloud resource pools and manage their data, wherein the different types of cloud resource pool data at least include private cloud pools and public cloud pools;

[0010] The hybrid cloud management platform is used to receive the cloud resource pool data through different interfaces, and input virtual network element data through the NFV-MANO orchestration module, and calculate the resource matching degree of the virtual network element data according to the different types of cloud resource pool data to obtain a matching result corresponding to the cloud resource pool data.

[0011] Optionally, the unified resource access management module is used to: receive identification triplet data of the cloud resource pool sent by the infrastructure module, wherein the identification triplet data includes the cloud resource pool type, the cloud resource pool area and the number of cloud resources.

[0012] Optionally, the NFV orchestration unit is connected to an operation and business support system, and is used to receive request information for virtual network service resource orchestration sent by the operation and business support system.

[0013] Optionally, the VNF management unit is used to receive the request information sent by the NFV orchestration unit, and generate an instance corresponding to the VNF based on the request information.

[0014] Optionally, the VNF management unit is used to:

[0015] According to the preset virtual network element directory and deployment template, the network element identifier corresponding to the request information is determined and matched with the received cloud resource pools of different types.

[0016] Optionally, the VNF management unit is specifically used to:

[0017] Import all types of distributed network element deployment templates and software packages into the VNF management unit;

[0018] According to the number of resources, resource pool area and resource pool type required by the network element, virtual network element data is generated and stored in the network element directory;

[0019] According to the resource pool area and resource pool type, a corresponding relationship between the virtual network element data and different types of cloud resource pools is established to obtain a resource orchestration relationship;

[0020] The resource scheduling relationship is sent to the virtual resource unified management unit.

[0021] Optionally, the virtual resource unified management unit is used to: receive resource orchestration information sent by the VNF management unit, and match the corresponding resource pool according to the resource orchestration information.

[0022] Optionally, the virtual resource unified management unit is used to:

[0023] Obtain resource orchestration information sent by the VNF management unit;

[0024] According to the resource pool type, resource pool area and required number of virtual resources, a resource matching degree evaluation is performed to obtain a first target resource pool with the highest matching degree; if the first target resource pool does not exist, a resource pool with a second matching degree is determined;

[0025] Sending the resource orchestration information to the virtual resource manager of the target resource pool, generating a network element instance according to the deployment template resource logic and the software package image;

[0026] The generated network element instance and basic resource cloud product instance information are sent to the hybrid cloud unified management module.

[0027] In a second aspect, the present application shows a resource allocation method based on hybrid cloud and network function virtualization, the method comprising:

[0028] Access different types of cloud resource pools and manage their data, wherein the different types of cloud resource pool data include at least private cloud pools and public cloud pools;

[0029] The cloud resource pool data is received through different interfaces, and the virtual network element data is input through the NFV-MANO orchestration module. According to the different types of cloud resource pool data, the resource matching degree of the virtual network element data is calculated to obtain a matching result corresponding to the cloud resource pool data.

[0030] Optionally, the resource data in the cloud resource pool is triple data, wherein the triple data includes a cloud resource pool type, a cloud resource pool region, and a cloud resource identifier.

[0031] The technical solution provided by the present application may include the following beneficial effects: An embodiment of the present application provides a resource allocation system and method based on hybrid cloud and network function virtualization, including a hybrid cloud management platform and an infrastructure module, wherein the hybrid cloud management platform includes at least a NFV-MANO orchestration module and a resource unified access management module, and the NFV-MANO orchestration module is connected to the resource unified access management module, wherein the NFV-MANO orchestration module includes at least a NFV orchestration unit, a VNF management unit and a virtual resource unified management unit; the infrastructure module is used to access different types of cloud resource pools and manage their data, wherein the different types of cloud resource pool data include at least a private cloud pool and a public cloud pool; the hybrid cloud management platform is used to receive the cloud resource pool data through different interfaces, and input virtual network element data through the NFV-MANO orchestration module, and according to the different types of cloud resource pool data, calculate the resource matching degree of the virtual network element data to obtain a matching result corresponding to the cloud resource pool data. By integrating the NFV-MANO system into the hybrid cloud management platform and coordinating the unified resource access of private cloud and public cloud resource pools, problems such as complex management, insufficient resource elasticity, and low operation and maintenance efficiency caused by multiple types of resource pools and multiple MANO systems in distributed communication network element scenarios can be solved. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 It is a structural diagram of a resource allocation system based on hybrid cloud and network function virtualization of the present application;

[0033] Figure 2 It is a flow chart of a resource allocation method based on hybrid cloud and network function virtualization of the present application;

[0034] Figure 3 It is a VNF management module processing flow chart of the present application;

[0035] Figure 4 This is a processing flow chart of a virtualized resource unified management unit of the present application. DETAILED DESCRIPTION

[0036] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0037] Glossary:

[0038] NFV (Network Functions Virtualisation): Isolate the network functions of network devices from the hardware through a virtual hardware abstraction layer to achieve software and hardware decoupling. It is essentially a network architecture that enables CT services to be deployed on a cloud platform. The European Telecommunications Standards Institute (ETSI) organizes and formulates a number of related standards.

[0039] NFVI (Network Functions Virtualisation Infrastucture): Located at the bottom layer of the NFV architecture, it simulates and provides traditional hardware functions, including computing, storage, and network resources. The goal of this layer is to virtualize hardware resources so that they can be allocated to upper-layer virtual network functions (VNFs) in a flexible manner.

[0040] NFV-MANO (Management and Orchestration): A key part of the ETSI NFV architecture, a unified framework for managing VNFs and NFVI, ensuring that VNFs are deployed, operated, and managed on demand. It provides telecom operators and network service providers with flexibility and automation to meet changing network requirements.

[0041] VIM (Virtualised Infrastructure Manager): Responsible for controlling and managing the NFVI layer virtual resources required by VNFs, such as computing, storage, and networking.

[0042] VNF (Virtualised Network Function): Network function software running on the NFVI layer to realize the capabilities of service network elements.

[0043] Hybrid cloud: A cloud deployment model that unifies and coordinates private clouds, public clouds, and local data centers to help users manage cross-cloud and cross-region IT infrastructure.

[0044] Hybrid cloud management platform: also known as multi-cloud management platform, an integrated product for managing public cloud, private cloud and hybrid cloud environments, integrating multiple infrastructures and resources, realizing cross-platform orchestration, providing a self-service environment in the form of a service catalog, as well as resource access management, process configuration, resource statistics, metering and billing and other functions.

[0045] Reference Figure 1, shows a structural schematic diagram of a resource allocation system based on hybrid cloud and network function virtualization of the present application, including: a hybrid cloud management platform and an infrastructure module, the hybrid cloud management platform at least includes an NFV-MANO orchestration module and a resource unified access management module, the NFV-MANO orchestration module and the resource unified access management module are connected, wherein the NFV-MANO orchestration module at least includes an NFV orchestration unit, a VNF management unit and a virtual resource unified management unit;

[0046] The infrastructure module is used to access different types of cloud resource pools and manage their data, wherein different types of cloud resource pool data at least include private cloud pools and public cloud pools;

[0047] Specifically, the number of private cloud pools and public cloud pools is not specifically limited in this application.

[0048] The hybrid cloud management platform is used to receive the cloud resource pool data through different interfaces, and input the virtual network element data through the NFV-MANO orchestration module, and calculate the resource matching degree of the virtual network element data according to the different types of cloud resource pool data to obtain a matching result corresponding to the cloud resource pool data.

[0049] Virtual network element data is input. The administrator fills in the number of resources, resource pool area, and resource pool type required by the network element through the NFV-MANO orchestration management module to form virtual network element data, which is uniformly stored in the network element directory. After the virtual network element data is determined, it is matched with the cloud resource pool data.

[0050] Among them: NFV architecture is the key to realize network function virtualization. It includes multiple main components, two of which are virtual network function (VNF) and virtual network function manager (VNFM).

[0051] Virtual Network Function (VNF) is the basic building block of Network Function Virtualization. It represents a virtualized instance of traditional network devices such as routers, firewalls, load balancers, etc. Each VNF performs a specific network function and can be deployed on NFV Infrastructure (NFVI). VNF is part of the network service chain and can be combined together as needed to build a specific network service.

[0052] The Virtual Network Function Manager (VNFM) is the component responsible for the lifecycle management of VNFs. It includes the creation, configuration, monitoring, and destruction of VNFs. VNFM interacts with the NFV Management and Orchestration Architecture (NFV-MANO) to ensure that VNFs can be deployed and managed on demand. VNFM also handles the tasks of voluntarily stopping, scaling up, and scaling down VNFs to adapt to changes in network load.

[0053] In addition, NFV architecture also includes other components such as virtual network function connection point (VNF CP), virtualized infrastructure (NFVI) and virtual network function description (VNFD). These components work together to achieve the core concept of NFV: virtualization and decoupling of network functions.

[0054] Network Function Virtualization Infrastructure (NFVI) is a key element to support VNF ​​deployment and operation:

[0055] Computing resources: NFVI requires correspondingly rich computing resources to run VNFs in a virtualized environment. These resources are usually provided by virtual machines (VMs) or containers (such as Docker or Kubernetes), allowing VNFs to run independently in a virtual environment.

[0056] Storage resources: Storage resources are used to store VNF images, configurations, and data. NFVI requires a high-performance, scalable storage system to ensure efficient operation of VNFs.

[0057] Network resources: The network is the core of NFV because it connects various VNFs and data centers. Network resources include physical networks, virtual networks, network function connection points (VNF CPs), and virtual switches to route traffic to the correct VNF.

[0058] Management and Orchestration: NFVI requires management and orchestration components to ensure that VNFs are deployed and run as needed. These components include VNFM and NFV Management and Orchestration Architecture (NFV-MANO).

[0059] Security and isolation: Since multiple VNFs may run on the same NFVI, security and isolation are critical. The NFVI must provide isolation mechanisms to prevent one VNF from interfering with or accessing other VNFs.

[0060] NFV Management and Orchestration Architecture (NFV-MANO) is a key component to manage and coordinate the NFV lifecycle.

[0061] It consists of the following three main subcomponents:

[0062] NFV Orchestrator (NFVO): NFVO is the highest level component of NFV-MANO and is responsible for coordinating the deployment and management of VNFs. It interacts with the VNF Manager (VNFM) and Virtualization Infrastructure Manager (VIM) to ensure that VNFs are deployed and run as required. NFVO is also responsible for allocating resources, optimizing performance, and maintaining the lifecycle of VNFs.

[0063] VNF Manager (VNFM): VNFM is the component responsible for managing individual VNFs. It is responsible for the creation, configuration, monitoring, voluntary decommissioning, and maintenance of VNFs. VNFM works in conjunction with NFVO to achieve lifecycle management of VNFs.

[0064] Virtualized Infrastructure Manager (VIM): VIM is the component responsible for managing compute, storage, and network resources. It monitors and controls the resources on NFVI to ensure that they meet the needs of VNFs. VIM also provides resource allocation and isolation mechanisms to ensure that resources between different VNFs do not interfere with each other.

[0065] NFV-MANO is a key part of NFV architecture, ensuring VNFs are deployed, run and managed on demand. It provides telecom operators and network service providers with flexibility and automation to meet changing network requirements.

[0066] Another embodiment of the present application further supplements the resource allocation system based on hybrid cloud and network function virtualization provided in the above embodiment.

[0067] Optionally, the unified resource access management module is used to: receive identification triplet data of the cloud resource pool sent by the infrastructure module, wherein the identification triplet data includes the cloud resource pool type, the cloud resource pool region and the number of cloud resources.

[0068] Optionally, the NFV orchestration unit is connected to the operation and business support system, and is used to receive request information for virtual network service resource orchestration sent by the operation and business support system.

[0069] Figure 1 It is a structural diagram of a resource allocation system based on hybrid cloud and network function virtualization of the present application. The embodiment of the present application provides a NFV-MANO fusion system based on hybrid cloud, that is, a resource allocation system based on hybrid cloud and network function virtualization, the system comprising: adding a hybrid cloud resource pool including private cloud and public cloud to the infrastructure layer of the NFV architecture; integrating NFV-MANO into the hybrid cloud management platform, making the resource unified access management module the basic module of the two, realizing access to the resource pool, management of physical resources and virtualization layer; in the virtual resource unified management unit, realizing abstraction and unification of multiple virtualized infrastructure management systems, and the upper layer serves the VNF management module.

[0070] In one embodiment, the hybrid cloud management platform provides a unified portal, and the NFV-MANO system is integrated into it as a management component unit, which can simultaneously access components of the hybrid cloud management platform such as operation management, operation and maintenance management, and resource management.

[0071] In one embodiment, the resource unified access layer adapts and abstracts different types of cloud resource pools such as private clouds and public clouds. The resource pool SDK layer is responsible for the interaction between the resource pool and the unified resource management platform, realizing the decoupling of the unified resource management platform and the resource pool; the unified API layer provides a unified API for the upper management module by adapting and encapsulating the APIs of various heterogeneous cloud resource pools; the process processing layer is responsible for the life cycle management of cloud infrastructure resource services.

[0072] In one embodiment, the NFV-MANO orchestration module includes a virtual resource unified management unit, a VNF management unit and a NFV orchestration unit. The NFV orchestration unit can interact with the operation and business support system, receive the request information about VNF ​​and network service NS resource orchestration issued by it, and can also be directly managed and controlled on the hybrid cloud management platform; the VNF management unit mainly provides life cycle management for various virtual network elements, namely VNF services, is located in the middle layer, receives information about VNF ​​from the NFV orchestration unit, calls the virtual resource unified management unit downward to generate VNF instances, and is combined with the operation management and operation and maintenance management of the hybrid cloud management platform; the virtual resource unified management unit receives resource orchestration information from the VNF management unit, matches the specific resource pool downward, and specifically executes the instantiation of VNF through the API provided by the resource unified access management module.

[0073] Figure 2 This is a flow chart of a resource allocation method based on hybrid cloud and network function virtualization in the present application. Based on the above-mentioned fusion system, an orchestration management method is provided, including: based on the unified management of multi-cloud resource pools on the hybrid cloud management platform, a unique identification triplet of the cloud resource pool is formed (cloud_type cloud resource type, cloud_region cloud resource region, cloud_id cloud resource identifier), and placed in the unified resource access management module; the virtual resource unified management unit in the NFV-MANO orchestration module integrates the virtual infrastructure layer management capability (i.e. VIM) of the hybrid cloud management platform. Combined with the abstracted resource pool information and identification triplet of the hybrid element management platform, the API interface of the specified cloud pool is called to generate the product instance corresponding to the virtual network element; the VNF management unit in the NFV-MANO orchestration module provides a general virtual network element directory and deployment template (refer to the service orchestration of the cloud management). At the same time, before deployment, resource requirements, determine the identification of the network element, the specified cloud resource pool or automatically match to the VIM of other resource pools of the same type; send the created network element and its cloud product instance information to the unified operation and maintenance monitoring platform of the hybrid cloud management platform, and integrate the capabilities of the cloud management for management.

[0074] Figure 3This is a VNF management unit processing flow chart of the present application. Optionally, the VNF management unit is used to receive request information sent by the NFV orchestration unit and generate an instance corresponding to the VNF based on the request information.

[0075] Optionally, the VNF management unit is used to:

[0076] According to the preset virtual network element directory and deployment template, the network element identifier corresponding to the request information is determined and matched with the received cloud resource pools of different types.

[0077] Optionally, the VNF management unit is specifically used to: uniformly import various network element deployment templates and software packages of distributed deployment into the VNF management unit;

[0078] According to the number of resources required by the network element, the resource pool area and the resource pool type, virtual network element data is formed and uniformly stored in the network element directory; according to the resource pool area and resource pool type, the corresponding relationship between the virtual network element data and different types of cloud resource pools is established to obtain the resource orchestration relationship;

[0079] The resource orchestration relationship is sent to the virtual resource unified management unit.

[0080] like Figure 3 As shown, in one embodiment, the VNF management unit processing flow includes:

[0081] Step 1: Import all types of distributed network element deployment templates (information description files) and software packages into the VNF management unit;

[0082] Step 2: The administrator fills in the number of resources required by the network element, the resource pool area, and the resource pool type to form virtual network element data, which is uniformly stored in the network element directory;

[0083] The virtual network element data comes from the NFV-MANO orchestration module in the hybrid cloud management platform and is an input data. The core point of this patent is to abstract and unify the data of multiple cloud resource pools managed by the hybrid cloud management platform through a unified resource access management module, and then calculate the matching degree between the request data of the NFV-MANO orchestration module and the abstracted cloud resource pool data to match the optimal resource pool, and finally instantiate the requested virtual network element on the resource pool.

[0084] Step 3: Establish a correspondence between the network element and the deployable resource pool according to the resource pool area and type information;

[0085] Step 4: Send the network element resource orchestration information to be instantiated to the virtualized resource unified management unit.

[0086] Optionally, the virtual resource unified management unit is used to: receive resource orchestration information sent by the VNF management unit, and match the corresponding resource pool according to the resource orchestration information.

[0087] Optionally, the virtual resource unified management unit is used to:

[0088] Obtain resource orchestration information sent by the VNF management unit;

[0089] According to the resource pool type, resource pool area and required number of virtual resources, a resource matching degree evaluation is performed to obtain a first target resource pool with the highest matching degree; if the first target resource pool does not exist, a resource pool with a second matching degree is determined;

[0090] Send resource orchestration information to the virtual resource manager of the target resource pool, and generate network element instances according to the deployment template resource logic and software package image;

[0091] The generated network element instance and basic resource cloud product instance information are sent to the hybrid cloud unified management module.

[0092] like Figure 4 As shown, in one embodiment, the virtual resource unified management unit includes:

[0093] Step 1: Receive the call from the VNF management unit and obtain resource orchestration information;

[0094] Step 2: According to the resource pool type, resource pool area and required number of virtual resources, the resource matching degree is evaluated to obtain the optimal target resource pool; if there is no optimal matching value, a resource pool with a second matching degree is obtained; if there is no resource pool with a second matching degree, an error is returned to the VNF management unit;

[0095] Step 3: The resource orchestration information is sent to the virtual resource manager of the target resource pool, and a network element instance is generated according to the deployment template resource logic and software package image;

[0096] Step 4: Send the generated network element instance and basic resource cloud product instance information to the unified operation and maintenance management platform of the hybrid cloud management platform.

[0097] The benefits brought by the present invention include: by integrating the NFV-MANO system into the hybrid cloud management platform, coordinating the unified resource access of private cloud and public cloud type resource pools, solving the problems of complex management, insufficient resource elasticity and low operation and maintenance efficiency caused by multiple types of resource pools and multiple MANO systems in distributed communication network element scenarios.

[0098] It should be noted that each implementable method in this embodiment may be implemented separately, or may be implemented in combination in any combination without conflict, and this application is not limited thereto.

[0099] Another embodiment of the present application provides a resource allocation method based on hybrid cloud and network function virtualization, which is used to execute the resource allocation system based on hybrid cloud and network function virtualization provided by the above embodiment.

[0100] The present application shows a resource allocation method based on hybrid cloud and network function virtualization, the method comprising:

[0101] Access different types of cloud resource pools and manage their data, wherein the different types of cloud resource pool data include at least private cloud pools and public cloud pools;

[0102] The cloud resource pool data is received through different interfaces, and the virtual network element data is input through the NFV-MANO orchestration module. According to the different types of cloud resource pool data, the resource matching degree of the virtual network element data is calculated to obtain a matching result corresponding to the cloud resource pool data.

[0103] Optionally, the resource data in the cloud resource pool is triple data, wherein the triple data includes a cloud resource pool type, a cloud resource pool region, and a cloud resource identifier.

[0104] The embodiment of the present application provides a NFV-MANO system and method integrated on the basis of a hybrid cloud management platform, which is used to make up for the lack of a unified MANO management solution for various types of cloud resource pools in hybrid cloud scenarios. It is mainly proposed that after the cloud resource pool is uniformly managed, a triplet identifier is abstractly generated, and the network element metadata and identifier are configured to estimate the resource matching degree, and the best cloud resource pool is matched to form resource orchestration and generate a network element instance.

[0105] In the distributed communication network element scenario of the embodiment of the present application, the introduction of a hybrid cloud management platform can coordinate private cloud and public cloud resource pools to maximize the elasticity of different types of resources. Compared with the NFV-MANO products of equipment manufacturers, although they support unified resource management of multiple DCs, they cannot support the cloud deployment model of hybrid clouds to achieve access and management of public clouds.

[0106] Integrate NFV-MANO into the hybrid cloud management platform to achieve unified management of cloud resource pool and VNF in two dimensions, improve management efficiency and reduce operating costs. Compared with the independent mode of hybrid cloud management and NFV-MANO, although the hybrid cloud management platform has unified the multi-cloud resource pool, NFV-MANO is still independent, and a set of NFV-MANO needs to be deployed for the same type or the same cloud resource pool; in the ETSI NFV-MANO architecture, the wide area network infrastructure manager (WIM, WANInfrastructure Manager) is introduced, but this management module is limited to managing the connection between POP access points of different infrastructure layers through the wide area network or transmission network, and does not involve the resource integration of NFVI itself.

[0107] The unified identification of the cloud resource pool is established and mapped with the network element. By establishing the triplet identification of the cloud resource pool, the key information required for network element instantiation is effectively extracted, and the mapping between the two is done well. The efficiency of resource orchestration.

[0108] The resource matching degree between the network element and the cloud resource pool it carries is evaluated by requiring the resource requirement information of the network element to be filled in when the network element template is imported into the network element directory, and the resource matching degree is evaluated and calculated in the virtual resource unified management unit. This can determine in advance whether the network element can be instantiated, thereby improving delivery efficiency.

[0109] The embodiment of the present application provides a resource allocation system and method based on hybrid cloud and network function virtualization, including a hybrid cloud management platform and an infrastructure module, the hybrid cloud management platform at least includes an NFV-MANO orchestration module and a resource unified access management module, the NFV-MANO orchestration module and the resource unified access management module are connected, wherein the NFV-MANO orchestration module at least includes an NFV orchestration unit, a VNF management unit and a virtual resource unified management unit; the infrastructure module is used to access different types of cloud resource pools and manage their data, wherein different types of data at least include private cloud pools and public cloud pools; the hybrid cloud management platform is used to receive the cloud resource pool data through different interfaces, and input virtual network element data through the NFV-MANO orchestration module, and calculate the resource matching degree of the virtual network element data according to the different types of cloud resource pool data, and obtain the matching result corresponding to the cloud resource pool data. By integrating the NFV-MANO system into the hybrid cloud management platform, the unified resource access of private cloud and public cloud type resource pools is coordinated, and the problems of complex management, insufficient resource elasticity and low operation and maintenance efficiency caused by multiple types of resource pools and multiple MANO systems in distributed communication network element scenarios are solved.

[0110] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0111] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0112] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

[0113] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in the present application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0114] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0115] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0116] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0117] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0118] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0119] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A resource allocation system based on hybrid cloud and network function virtualization, characterized in that: The system at least includes: a hybrid cloud management platform and an infrastructure module, the hybrid cloud management platform at least includes an NFV-MANO orchestration module and a resource unified access management module, the NFV-MANO orchestration module is connected to the resource unified access management module, wherein the NFV-MANO orchestration module at least includes an NFV orchestration unit, a VNF management unit and a virtual resource unified management unit; The infrastructure module is used to access different types of cloud resource pools and manage their data, wherein the different types of cloud resource pools include at least private cloud pools and public cloud pools; The hybrid cloud management platform is used to receive the cloud resource pool data through different interfaces, and input virtual network element data through the NFV-MANO orchestration module, and calculate the resource matching degree of the virtual network element data according to the different types of cloud resource pool data to obtain a matching result corresponding to the cloud resource pool data.

2. The resource allocation system based on hybrid cloud and network function virtualization according to claim 1, characterized in that: The resource unified access management module is used to receive the identification triplet data of the cloud resource pool sent by the infrastructure module.

3. The resource allocation system based on hybrid cloud and network function virtualization according to claim 1, characterized in that: The NFV-MANO orchestration module is connected to the operation and business support system, and is used to receive request information for virtual network service resource orchestration sent by the operation and business support system.

4. The resource allocation system based on hybrid cloud and network function virtualization according to claim 3, characterized in that: The VNF management unit is used to receive the request information sent by the NFV orchestration unit, and generate an instance corresponding to the VNF according to the request information.

5. The resource allocation system based on hybrid cloud and network function virtualization according to claim 4, characterized in that: The VNF management unit is used to determine the network element identifier corresponding to the request information according to the preset virtual network element directory and deployment template, and match it with the different types of cloud resource pools received.

6. The resource allocation system based on hybrid cloud and network function virtualization according to claim 5, characterized in that: The VNF management unit is specifically used for: Import all types of distributed network element deployment templates and software packages into the VNF management unit; According to the number of resources, resource pool area and resource pool type required by the network element, virtual network element data is generated and stored in the network element directory; According to the resource pool area and resource pool type, a corresponding relationship between the virtual network element data and different types of cloud resource pools is established to obtain a resource orchestration relationship; The resource scheduling relationship is sent to the virtual resource unified management unit.

7. The resource allocation system based on hybrid cloud and network function virtualization according to claim 4, characterized in that: The virtual resource unified management unit is used for: Receive the resource orchestration information sent by the VNF management unit, and match the corresponding resource pool according to the resource orchestration information.

8. The resource allocation system based on hybrid cloud and network function virtualization according to claim 7, characterized in that: The virtual resource unified management unit is used for: Obtain resource orchestration information sent by the VNF management unit; According to the resource pool type, resource pool area and required number of virtual resources, a resource matching degree evaluation is performed to obtain a first target resource pool with the highest matching degree; if the first target resource pool does not exist, a resource pool with a second matching degree is determined; Sending the resource orchestration information to the virtual resource manager of the target resource pool, generating a network element instance according to the deployment template resource logic and the software package image; The generated network element instance and basic resource cloud product instance information are sent to the hybrid cloud unified management module.

9. A resource allocation method based on hybrid cloud and network function virtualization, characterized in that: Applied to the resource allocation system based on hybrid cloud and network function virtualization as claimed in any one of claims 1 to 8, the method comprising: Access different types of cloud resource pools and manage their data, wherein the different types of cloud resource pool data include at least private cloud pools and public cloud pools; The cloud resource pool data is received through different interfaces, and the virtual network element data is input through the NFV-MANO orchestration module. According to the different types of cloud resource pool data, the resource matching degree of the virtual network element data is calculated to obtain a matching result corresponding to the cloud resource pool data.

10. The resource allocation method based on hybrid cloud and network function virtualization according to claim 9, characterized in that: The resource data in the cloud resource pool is triple data, wherein the triple data includes a cloud resource pool type, a cloud resource pool region, and a cloud resource identifier.

Images