Drive management method, device, system and computer readable storage medium

Abstract

The present invention discloses a driver management method, device, system and computer-readable storage medium, and relates to the field of computer technology. The driver management method includes: a management device obtains a version specification requirement description of a driver from a VNF library; the management device sends a query request including the version specification requirement description of the driver to a VIM, so that the VIM queries whether the NFVI has a driver corresponding to the version specification requirement description, and queries whether the driver library has a driver corresponding to the version specification requirement description if it does not have one; the management device obtains the query result sent by the VIM; if the management device does not have a driver corresponding to the version specification requirement description in both the NFVI and the driver library, the management device sends an instruction to the driver library to obtain the corresponding driver. Thereby, the VNF deployment efficiency and automation level are improved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a drive management method, device, system and computer-readable storage medium. Background Art

[0002] In a Network Function Virtualization (NFV) environment, various virtualized network functions (VNFs) from different vendors run on the Network Function Virtualization Infrastructure (NFVI). This raises the issue of matching different VNFs with different underlying physical devices (such as network interface cards). The proper operation of VNFs depends on the proper functioning of the associated physical devices, and requires the correct device drivers at the virtualization layer and below. Currently, this matching relies on manual inspection and intervention. In large-scale applications, manual intervention is inefficient and prone to errors. Summary of the Invention

[0003] A technical problem to be solved by the embodiments of the present invention is: how to improve the deployment and operation efficiency of VNF.

[0004] According to a first aspect of some embodiments of the present invention, a driver management method is provided, including: a management device obtains a version specification requirement description of a driver from a VNF library; the management device sends a query request including the version specification requirement description of the driver to a VIM, so that the VIM queries whether the NFVI has a driver corresponding to the version specification requirement description, and if not, queries whether the driver library has a driver corresponding to the version specification requirement description; the management device obtains the query result sent by the VIM; and if the NFVI and the driver library do not have a driver corresponding to the version specification requirement description, the management device sends an instruction to the driver library to obtain the corresponding driver.

[0005] In some embodiments, the management device obtains the version specification requirement description of the driver from the VNF library, including: the management device obtains the VNF package from the VNF library; the management device obtains the VNFD in the VNF package; the management device parses the VNFD to obtain the version specification requirement description of the driver.

[0006] In some embodiments, the management device is at least one of an NFVO and a VNFM.

[0007] In some embodiments, when the management device includes NFVO and VNFM: NFVO obtains a VNF package from a VNF library; NFVO parses an NSD template in the VNF package to obtain a VNFD, wherein the NSD template includes one or more VNFDs; VNFM parses the VNFD to obtain a version specification requirement description of the driver.

[0008] In some embodiments, when the management device includes an NFVO: the NFVO obtains a VNF package from a VNF library; the NFVO parses an NSD template in the VNF package to obtain a VNFD, wherein the NSD template includes one or more VNFDs; the NFVO parses the VNFD to obtain a version specification requirement description of the driver.

[0009] In some embodiments, when the management device does not have a driver corresponding to the version specification requirement description in both the NFVI and the driver library, it sends an instruction to the driver library to upgrade or downgrade the existing driver so that the driver meets the version specification requirement description.

[0010] In some embodiments, when the management device does not have a driver corresponding to the version specification requirement description in both the NFVI and the driver library, it sends an instruction to the driver library to download a driver that meets the version specification requirement description.

[0011] In some embodiments, in response to a VNF instance being created, the management device obtains a version specification requirement description of the driver from the VNF library.

[0012] According to a second aspect of some embodiments of the present invention, a driver management device is provided, including: a description acquisition module, configured to obtain a version specification requirement description of a driver from a VNF library; a query module, configured to cause the management device to send a query request including the version specification requirement description of the driver to the VIM, so that the VIM queries whether the NFVI has a driver corresponding to the version specification requirement description, and if not, queries whether the driver library has a driver corresponding to the version specification requirement description; a query result acquisition module, configured to cause the management device to obtain the query result sent by the VIM; and an indication module, configured to cause the management device to send an indication to the driver library to obtain the corresponding driver if the NFVI and the driver library do not have a driver corresponding to the version specification requirement description.

[0013] According to a third aspect of some embodiments of the present invention, a driver management device is provided, comprising: a memory; and a processor coupled to the memory, wherein the processor is configured to execute any one of the aforementioned driver management methods based on instructions stored in the memory.

[0014] According to a fourth aspect of some embodiments of the present invention, a driver management system is provided, comprising: any one of the aforementioned driver management devices; and a VIM, configured to query whether the NFVI has a driver corresponding to the version specification requirement description, and if not, query whether the driver library has a driver corresponding to the version specification requirement description.

[0015] In some embodiments, the driver management system further includes: a VNF library storing a description of driver version specifications.

[0016] In some embodiments, the driver management system further includes: a driver library configured to obtain corresponding drivers according to instructions sent by the driver management device.

[0017] In some embodiments, the driver management system further includes NFVI.

[0018] In some embodiments, the driver management device includes at least one of NFVO and VNFM.

[0019] According to a fifth aspect of some embodiments of the present invention, there is provided a computer-readable storage medium having a computer program stored thereon, which implements any one of the aforementioned drive management methods when executed by a processor.

[0020] Some embodiments of the aforementioned inventions have the following advantages or beneficial effects: These embodiments introduce driver management at the NFVI level in the field of network virtualization, strengthening the management of infrastructure device usage, reducing manual operations, and improving VNF deployment efficiency and automation, further aligning with the efficiency and flexibility goals advocated by network virtualization. Furthermore, they increase overall NFVI utilization and eliminate the lock-in relationship between specific devices and specific network elements, further aligning with the hierarchical decoupling goals advocated by network virtualization.

[0021] Further features and advantages of the present invention will become apparent from the following detailed description of exemplary embodiments of the present invention with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0023] Figure 1 1 is a flow chart of a drive management method according to some embodiments of the present invention.

[0024] Figure 21 is a flow chart of a driver acquisition method according to some embodiments of the present invention.

[0025] Figure 3 1 is a flow chart of a driver acquisition method according to some embodiments of the present invention.

[0026] Figure 4 1 is a flowchart of a drive management method according to some other embodiments of the present invention.

[0027] Figure 5 Schematic diagram of the structure of a drive management device according to some embodiments of the present invention.

[0028] Figure 6 Schematic diagram of the structure of a drive management system according to some embodiments of the present invention.

[0029] Figure 7 Schematic diagram of the structure of a drive management device according to some other embodiments of the present invention.

[0030] Figure 8 Schematic diagram of the structure of a drive management device according to some other embodiments of the present invention. DETAILED DESCRIPTION

[0031] The following will be combined with the accompanying drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, rather than all the embodiments. The following description of at least one exemplary embodiment is actually only illustrative and is in no way intended to limit the present invention and its application or use. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0032] Unless otherwise specifically stated, the relative arrangement of components and steps, the numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present invention.

[0033] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

[0034] Technologies, methods and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, such technologies, methods and equipment should be considered part of the authorization specification.

[0035] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0036] It should be noted that like reference numerals and letters refer to like items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0037] Figure 1 FIG. 1 is a flow chart of a drive management method according to some embodiments of the present invention. Figure 1 As shown, the drive management method of this embodiment includes steps S102 to S110.

[0038] In step S102, the management device obtains the version specification requirement description of the driver from the VNF library.

[0039] In some embodiments, in response to a VNF instance being created, the management device obtains a version specification requirement description of the driver from the VNF library.

[0040] In some embodiments, a management device obtains a VNF package from a VNF library; obtains a VNFD (Virtualized Network Function Descriptor) from the VNF package; and parses the VNFD to obtain a driver version specification description. A VNF package typically includes the VNFD, VNF images, and other files. The VNFD specifies the internal structure of the VNF and its external connections, and can be represented using JSON (JavaScript Object Notation) or YAML (Yet Another Markup Language) formats.

[0041] In some embodiments, the VNFD may be provided by a network element provider and packaged in a VNFPackage. Operators can store the VNFD in package form in the network element library before using it, or, when the VNFD is in use, have the administrator upload the VNFD in package form to a VNFM (Network Functions Virtualisation Manager) or NFVO (Network Functions Virtualisation Orchestrator) system.

[0042] In step S104 , the management device sends a query request including a description of the driver version specification requirements to a VIM (Virtualised Infrastructure Manager).

[0043] In step S106 , the VIM queries whether the NFVI has a driver corresponding to the version specification requirement description, and if not, queries whether the driver library has a driver corresponding to the version specification requirement description.

[0044] In step S108 , the management device obtains the query result sent by the VIM.

[0045] In step S110 , when neither the NFVI nor the driver library has a driver corresponding to the version specification description, the management device sends an instruction to the driver library to obtain the corresponding driver.

[0046] The above-described embodiments introduce driver management at the NFVI level within network virtualization, strengthening the management of infrastructure device usage. This reduces manual operations, improves VNF deployment efficiency and automation, and further aligns with the efficiency and flexibility advocated by network virtualization. Furthermore, they increase overall NFVI utilization and eliminate the lock-in relationship between specific devices and specific network elements, further aligning with the layered decoupling advocated by network virtualization.

[0047] When obtaining the driver, you can modify the existing driver by upgrading or downgrading it, or you can download it again. Figure 2 and Figure 3 An embodiment of a drive acquisition method is described.

[0048] Figure 2 FIG. 1 is a flow chart of a drive acquisition method according to some embodiments of the present invention. Figure 2 As shown, the drive acquisition method of this embodiment includes steps S202 to S204.

[0049] In step S202, when the management device does not have a driver corresponding to the version specification description in both the NFVI and the driver library, the management device sends an instruction to the driver library to upgrade or downgrade the existing driver.

[0050] In step S204 , the driver library upgrades or downgrades the existing driver according to the instruction so that the driver meets the version specification requirement description.

[0051] In this way, the number of existing drivers in the system remains unchanged, thus saving storage space while ensuring automatic and efficient deployment of VNFs.

[0052] Figure 3 FIG. 1 is a flow chart of a driver acquisition method according to some embodiments of the present invention. Figure 3 As shown, the drive acquisition method of this embodiment includes steps S302 to S304.

[0053] In step S302, when the management device does not have a driver corresponding to the version specification requirement description in both the NFVI and the driver library, it sends an instruction to the driver library to download a driver that meets the version specification requirement description.

[0054] In step S304, the driver library downloads the driver that meets the version specification requirements according to the instruction.

[0055] In this way, when the system requires different versions of the same driver, the system's usage requirements can be met, thereby improving the execution efficiency of the VNF.

[0056] At present, the management system for network virtualization is mainly implemented by Management and Orchestration (MANO), which consists of NFVO, VNFM and VIM. The role of MANO is to manage the life cycle of virtual network elements and network services. However, its functional standards do not involve the management and matching of drivers. After research, the inventors used at least one of the NFVO and VNFM in MANO as a management device to realize automated driver management. Figure 4 An embodiment of the drive management method of the present invention is described.

[0057] Figure 4 FIG. 1 is a flow chart of a drive management method according to some other embodiments of the present invention. Figure 4 As shown, the drive management method of this embodiment includes steps S402 to S410.

[0058] In step S402, the NFVO / VNFM obtains the driver version specification description from the VNF library. In this embodiment, "NFVO / VNFM" refers to at least one of NFVO and VNFM.

[0059] In some embodiments, the NFVO may be responsible for parsing the Network Service Descriptor (NSD) template in the VNF package. The NSD template includes one or more VNFDs. The VNFM then parses the VNFDs. For example, the NFVO obtains the VNF package from the VNF library; the NFVO parses the NSD template in the VNF package to obtain the VNFD; and the VNFM parses the VNFD to obtain the driver version specification requirements.

[0060] In some embodiments, the NFVO can also obtain a VNF package from the VNF library, parse the NSD template in the VNF package to obtain the VNFD, and then parse the VNFD to obtain the driver version specification description. This approach can be used, for example, when the NFVO has strong performance, the NSD structure is relatively simple, or when the NFVO needs to control resources.

[0061] In step S404, the NFVO / VNFM sends a query request including a description of the driver version specification requirements to the VIM.

[0062] In step S406, the VIM queries whether the NFVI has a driver corresponding to the version specification requirement description, and if not, queries whether the driver library has a driver corresponding to the version specification requirement description.

[0063] In step S408, the NFVO / VNFM obtains the query result sent by the VIM.

[0064] In step S410, when neither the NFVI nor the driver library has a driver corresponding to the version specification description, the NFVO / VNFM sends an instruction to the driver library to obtain the corresponding driver.

[0065] Through the method of the above embodiment, the management and matching of the drivers can be achieved with the help of MANO.

[0066] Reference below Figure 5 An embodiment of a drive management device according to the present invention is described.

[0067] Figure 5 FIG. 1 is a schematic diagram of the structure of a drive management device according to some embodiments of the present invention. Figure 5 As shown, the driver management device 500 of this embodiment includes: a description acquisition module 5100, configured to obtain a version specification requirement description of a driver from a VNF library; a query module 5200, configured to enable the management device to send a query request including a version specification requirement description of the driver to the VIM, so that the VIM queries whether the NFVI has a driver corresponding to the version specification requirement description, and if not, queries whether the driver library has a driver corresponding to the version specification requirement description; a query result acquisition module 5300, configured to enable the management device to obtain the query result sent by the VIM; and an indication module 5400, configured to enable the management device to send an indication to the driver library to obtain the corresponding driver if the NFVI and the driver library do not have a driver corresponding to the version specification requirement description.

[0068] In some embodiments, the description acquisition module 5100 is further configured to obtain a VNF package from a VNF library; obtain a VNFD in the VNF package; and parse the VNFD to obtain a version specification requirement description of the driver.

[0069] In some embodiments, the driver management device 500 includes at least one of NFVO and VNFM.

[0070] In some embodiments, the description acquisition module 5100 is further configured to parse the NSD template in the VNF package and obtain the VNFD, wherein the NSD template includes one or more VNFDs; parse the VNFD to obtain the version specification requirement description of the driver.

[0071] In some embodiments, the indication module 5400 is further configured to send an indication to the driver library to upgrade or downgrade the existing driver so that the driver meets the version specification requirements when neither the NFVI nor the driver library has a driver corresponding to the version specification requirements.

[0072] In some embodiments, the indication module 5400 is further configured to send an indication to the driver library to download a driver that meets the version specification requirements when neither the NFVI nor the driver library has a driver that meets the version specification requirements.

[0073] In some embodiments, the description acquisition module 5100 is further configured to obtain a version specification requirement description of the driver from the VNF library in response to the VNF instance being created.

[0074] Reference below Figure 6 An embodiment of the drive management system of the present invention is described.

[0075] Figure 6 FIG. 1 is a schematic diagram of the structure of a drive management system according to some embodiments of the present invention. Figure 6 As shown, the driver management system 60 of this embodiment includes: a driver management device 610, whose specific implementation method can refer to the driver management device 500; VIM620, which is configured to query whether the NFVI has a driver corresponding to the version specification requirement description, and if not, query whether the driver library has a driver corresponding to the version specification requirement description.

[0076] In some embodiments, the driver management system 60 further includes: a VNF library 630 storing a description of driver version specifications.

[0077] In some embodiments, the driver management system 60 further includes a driver library 640 configured to obtain corresponding drivers according to instructions sent by the driver management device.

[0078] In some embodiments, the driver management system 60 also includes an NFVI 650 .

[0079] Figure 7FIG. 1 is a schematic diagram of the structure of a drive management device according to some other embodiments of the present invention. Figure 7 As shown, the driver management device 70 of this embodiment includes: a memory 710 and a processor 720 coupled to the memory 710 , and the processor 720 is configured to execute the driver management method in any of the aforementioned embodiments based on instructions stored in the memory 710 .

[0080] The memory 710 may include, for example, a system memory, a fixed non-volatile storage medium, etc. The system memory may store, for example, an operating system, application programs, a boot loader, and other programs.

[0081] Figure 8 FIG. 1 is a schematic diagram of the structure of a drive management device according to some embodiments of the present invention. Figure 8 As shown, the drive management device 80 of this embodiment includes: a memory 810 and a processor 820, and may also include an input / output interface 830, a network interface 840, a storage interface 850, etc. These interfaces 830, 840, 850 and the memory 810 and processor 820 can be connected, for example, via a bus 860. Among them, the input / output interface 830 provides a connection interface for input / output devices such as a display, mouse, keyboard, and touch screen. The network interface 840 provides a connection interface for various networked devices. The storage interface 850 provides a connection interface for external storage devices such as SD cards and USB flash drives.

[0082] An embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, wherein the program is characterized in that when executed by a processor, any one of the aforementioned drive management methods is implemented.

[0083] It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable non-transitory storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0084] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0085] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0086] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The steps for the function specified in one or more boxes.

[0087] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A drive management method, include: The management device obtains the version specification requirement description of the driver from the virtual network element VNF ​​library; The management device sends a query request including the version specification requirement description of the driver to the virtualization infrastructure manager VIM, so that the VIM queries whether the network function virtualization infrastructure NFVI has the driver corresponding to the version specification requirement description, and if not, queries whether the driver library has the driver corresponding to the version specification requirement description; The management device obtains the query results sent by the VIM; When the management device does not have the driver corresponding to the version specification requirements in both the NFVI and the driver library, the management device sends an instruction to the driver library to obtain the corresponding driver, including: sending an instruction to the driver library to upgrade or downgrade the existing driver, or sending an instruction to the driver library to download a driver that meets the version specification requirements.

2. The drive management method according to claim 1, in, The management device obtains the driver version specification requirement description from the VNF library including: The management device obtains the VNF package from the VNF library; The management device obtains the virtualized network function module descriptor VNFD in the VNF package; The management device parses the VNFD and obtains the version specification description of the driver.

3. The drive management method according to claim 1 or 2, in, The management device includes at least one of a network function virtualization orchestrator NFVO and a network function virtualization manager VNFM.

4. The drive management method according to claim 2, in, In the case where the management device includes NFVO and VNFM: NFVO obtains the VNF package from the VNF library; The NFVO parses the network service descriptor NSD template in the VNF package and obtains the VNFD, wherein the NSD template includes one or more VNFDs; VNFM parses VNFD to obtain the version specification description of the driver.

5. The drive management method according to claim 2, in, In the case where the management device includes NFVO: NFVO obtains the VNF package from the VNF library; The NFVO parses the NSD template in the VNF package and obtains the VNFD, wherein the NSD template includes one or more VNFDs; NFVO parses VNFD and obtains the version specification description of the driver.

6. The drive management method according to claim 1, in, In response to the VNF instance being created, the management device obtains the version specification requirement description of the driver from the VNF library.

7. A drive management device, include: A description acquisition module is configured to obtain a version specification requirement description of the driver from the VNF library; A query module is configured to manage the device to send a query request including the version specification requirement description of the driver to the VIM, so that the VIM queries whether the NFVI has the driver corresponding to the version specification requirement description, and if not, queries whether the driver library has the driver corresponding to the version specification requirement description; A query result acquisition module, configured to manage the device to acquire the query result sent by the VIM; The indication module is configured to send an indication to the driver library to obtain the corresponding driver when the management device does not have the driver corresponding to the version specification requirement description in both the NFVI and the driver library, including: sending an indication to the driver library to upgrade or downgrade the existing driver, or sending an indication to the driver library to download the driver that meets the version specification requirement description.

8. A drive management device, include: Memory; as well as A processor coupled to the memory, the processor being configured to execute the drive management method according to any one of claims 1 to 6 based on instructions stored in the memory.

9. A drive management system, include: The drive management device according to claim 7 or 8; as well as The VIM is configured to query whether the NFVI has a driver corresponding to the version specification requirement description, and if not, query whether the driver library has a driver corresponding to the version specification requirement description.

10. The drive management system according to claim 9, further comprising: include: The VNF library stores the version specification requirements of the driver.

11. The drive management system according to claim 9, further comprising: include: The driver library is configured to obtain the corresponding driver according to the instruction sent by the driver management device.

12. The drive management system according to claim 9, further comprising: include: NFVI.

13. The drive management system according to claim 9, in, The management device includes at least one of NFVO and VNFM.

14. A computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the drive management method according to any one of claims 1 to 6 is implemented.

Images