WO2017193810A1 - Software loading method, device and system - Google Patents

Abstract

A software loading method, device and system, the method comprising: receiving a service request sent by an NFVO and comprising an acceleration type and an acceleration capacity; according to the acceleration type and a software information library, determining a first storage link of first software having the acceleration type, processing capability information about the first software, a device type of a programmable device that can be loaded with the first software and first information about a manufacturer, and according to the first information, the processing capability information and the acceleration capacity, acquiring, from a device library, a first identifier of an idle programmable device needing to be loaded with the first software and a second identifier of a first server for managing the programmable device identified by the first identifier; sending the first storage link and the first identifier to the first server identified by the second identifier; and the first server downloading a data package of the first software from the first storage link, and loading the data package on the programmable device identified by the first identifier. The present invention can improve the flexibility of software loading on a programmable device.

Description

Software loading method, device and system

The present application claims priority to Chinese Patent Application No. 201610309117.7, entitled "A Software Loading Method, Apparatus and System", filed on May 10, 2016, the entire contents of which are incorporated herein by reference. In the application.

Technical field

The present invention relates to the field of communications technologies, and in particular, to a software loading method, device, and system.

Background technique

There is a programmable device in the hardware that can be loaded on these devices as needed and the software loaded can be upgraded. In the era of dedicated hardware, software is loaded onto programmable devices in the process of generating hardware according to the business plan. However, with the continuous development of Network Function Virtualization (NFV) technology, hardware in the field of Communication Technology (CT) is transformed from dedicated hardware to general-purpose hardware. In the era of general hardware, the acceleration type of each service may be different, and as the business continues to expand, the programmable devices allocated to the service may need to be increased or decreased, so that the software loaded on the programmable device needs to meet the business needs. The changes vary, but the method of loading software in dedicated hardware is no longer sufficient for the flexibility of software loading on programmable devices in general-purpose hardware.

Summary of the invention

The embodiment of the invention discloses a software loading method, device and system for improving the flexibility of software loading on a programmable device.

The first aspect discloses a software loading method. The Network Function Virtualization Orchestrator (NFVO) receives a service request including an acceleration type and an acceleration capacity, and according to the acceleration type and the software information base, the first type having the acceleration type can be determined. a first storage link of the software, processing capability information of the first software, and first information of the programmable device capable of loading the first software, and then acquiring from the first device library according to the first information, the processing capability information, and the acceleration capacity a first identifier of a Virtual Infrastructure Manager (VIM) for managing a programmable device capable of loading the first software and free, and the first storage link, the first information, and the The second information of the number of programmable devices of the software is sent to the first VIM identified by the first identifier; after receiving the first storage link, the first information, and the second information sent by the NFVO, the first VIM is based on the first information. And the second information from the second device library to obtain a second of the programmable devices that need to load the first software And a third identifier of the server for managing the programmable device identified by the second identifier, and transmitting the first storage link and the second identifier to the first server identified by the third identifier, which can be programmable according to service requirements Dynamic loading of the corresponding software on the device can increase the flexibility of software loading on the programmable device. The first information may include a device type and a manufacturer, the first storage link is configured to enable the first server to download the data packet of the first software from the first storage link, and the second identifier is used to enable the first server to load the data packet On the programmable device identified by the second identification.

In one embodiment, the NFVO determines the first software having the acceleration type based on the acceleration type and the software information base. When the first storage link, the processing capability information of the first software, and the first information of the programmable device capable of loading the first software, the first storage link of the first software having the acceleration type may be directly obtained from the software information repository. And processing capability information and first information of the programmable device capable of loading the first software, the storage link and processing capability information of the required loading software and the information of the programmable device capable of loading the software can be quickly obtained from the software information repository. Or the device type and manufacturer of the first programmable device can be obtained from the first device library, and the first programmable device can be loaded according to the device type of the first programmable device and the manufacturer obtains the first programmable device from the software information library. Software function of the software, when the software function includes the acceleration type, it can be determined that the software corresponding to the software function is the first software, the first programmable device is a programmable device capable of loading the first software, and the first programmable device The device type and the manufacturer are the first information, and then the first software is obtained from the software information library. Link information storage and processing power. Therefore, the software information library can be directly searched, or the first device library can be searched first, and then the software information library can be searched for the storage link and processing capability information of the required loading software and the information of the programmable device capable of loading the software. Wherein, the first programmable device is any idle programmable device in the first device library.

In one embodiment, when the second information is the number of devices of the programmable device that needs to load the first software, the NFVO further needs to determine the number of devices of the programmable device that needs to load the first software according to the acceleration capacity and the processing capability information. In this way, the number of devices of the programmable device that needs to load the software can be directly sent to the VIM, and the VIM processing can be reduced without reducing the processing of the VIM.

In an embodiment, when the second information includes the acceleration capacity and the processing capability information, the first VIM may first determine, according to the acceleration capacity and the processing capability information, the number of devices of the programmable device that needs to load the first software, and then The first server including the number of programmable devices corresponding to the idle first information is not less than the number of the devices, and the number of the devices is obtained from the programmable device managed by the first server in the second device library. The second identifier of the programmable device corresponding to the idle first information, and the third identifier of the first server is obtained from the second device library. Since the process of calculating the number of devices is performed by VIM, the processing of NFVO can be reduced.

In an embodiment, the service request may further include a computing resource, where the first VIM may first select an idle computing resource from the managed server, not less than the computing resource, and the number of programmable devices corresponding to the idle first information is not less than a first server of the number of programmable devices indicated by the second information, and then obtaining, from the programmable device managed by the first server in the second device library, the number of programmable devices indicated by the second information, corresponding to the idle first information a second identifier of the programmable device, and obtaining a third identifier of the first server from the second device library, so that the selected server can not only meet the service demand for the acceleration type and the acceleration capacity, but also can satisfy the service to the computing resource. demand.

In an embodiment, the service request may further include a storage resource, where the first VIM may first select an idle computing resource from the managed server, not less than the computing resource, the idle storage resource is not less than the storage resource, and include the idle a first server in which the number of programmable devices corresponding to the information is not less than the number of programmable devices indicated by the second information, and then the second information is obtained from the programmable device managed by the first server in the second device library. Programming the number of idle first information corresponding to the second identifier of the programmable device, and obtaining the third identifier of the first server from the second device library, so that the selected server can not only satisfy the service for the acceleration type and the acceleration capacity. Demand, but also to meet the business needs of computing resources and storage resources.

In one embodiment, the second server may send third information including the device type, manufacturer, and identification of the second programmable device to the second VIM, the second VIM establishing an identification including the third information and the second server The second device library and the identifier of the third information and the second server are sent to the NFVO, and the NFVO will establish a first device library according to the three information, the identifier of the second server, and the identifier of the second VIM, so that the NFVO and the VIM can be jointly managed. Programming the device. Among them, the second The server is a server for managing the second programmable device, and the second VIM is a VIM for managing the second server.

In one embodiment, the NFVO receives the software package and sends it to a third VIM or catalog, a third VIM or catalog storage package and sends a second storage link of the software package to the NFVO, the NFVO establishment including the second storage link and The software package includes software function information, software version information, processing capability information, and a software information library of the fourth information, so that NFVO can manage software that can be loaded on the programmable device. The fourth information may include a device type and a manufacturer of a programmable device capable of loading the software corresponding to the software package.

In one embodiment, before the second identifier causes the first server to load the data packet on the programmable device identified by the second identifier, it may first determine whether the programmable device identified by the second identifier in the first server is Loaded with software, when not loaded with software, the first server can directly load the data packet on the programmable device identified by the second identifier. When the software is loaded and the software does not have the acceleration type, Causing the first server to first unload the software on the programmable device identified by the second identifier, and then loading the data packet on the programmable device identified by the second identifier, thus, when the programmable device is not used (ie, When idle, that is, unassigned, the software to be loaded can be loaded on the programmable device regardless of whether the software is loaded or not, which can improve the flexibility of loading the software on the programmable device.

In one embodiment, the first information may further include a device model of a programmable device capable of loading the first software, and the third information may further include a device model of the second programmable device to enable device type and production of the programmable device. When the manufacturers are all the same, the device can be distinguished by the device model.

The second aspect discloses a software loading system, including NFVO and a first VIM, wherein:

The NFVO is configured to receive a service request including an acceleration type and an acceleration capacity, determine, according to the acceleration type and the software information library, a first storage link of the first software having the acceleration type, processing capability information of the first software, and loading the first First information of the programmable device of the software, obtaining, according to the first information, the processing capability information, and the acceleration capacity, a first identifier of a VIM for managing a programmable device capable of loading the first software and being idle from the first device library, And transmitting the first storage link, the first information, and the second information indicating the number of programmable devices that need to load the first software to the first VIM identified by the first identifier, the first information including the device type and the manufacturer;

a first VIM, configured to receive a first storage link, first information, and second information sent by the NFVO, and obtain, from the second device library, the second device that needs to load the first software according to the first information and the second information. And identifying a third identifier of the server for managing the programmable device identified by the second identifier, and transmitting the first storage link and the second identifier to the first server identified by the third identifier, the first storage link being used to enable The first server downloads the data packet of the first software from the first storage link, and the second identifier is used to cause the first server to load the data packet on the programmable device identified by the second identifier.

The third aspect discloses a software loading method, which is applied to a VIM, receives a service request including an acceleration type and an acceleration capacity sent by the NFVO, and determines a first software having the acceleration type according to the acceleration type and the software information base. Storing a link, processing capability information of the first software, and first information of the programmable device capable of loading the first software, acquiring, from the device library, the first software to be loaded and idle according to the first information, the processing capability information, and the acceleration capacity a first identifier of the programmable device and a second identifier of the server for managing the programmable device identified by the first identifier, and sending the first storage link and the first identifier to the first server identified by the second identifier, Dynamic loading of the software on the programmable device according to business needs can increase the flexibility of software loading on the programmable device. The first information includes a device type and a manufacturer, and the first storage link may cause the first server to download the data packet of the first software from the first storage link, where the first identifier may enable the first server to load the data packet in the first Identifies the identified programmable device.

As a possible implementation manner, the VIM may directly acquire the first storage link and processing capability information of the first software having the acceleration type from the software information base, and acquire the first programmable device capable of loading the first software. a message that can quickly obtain the storage link and processing capability information of the required loading software from the software information library and the information of the programmable device capable of loading the software; or the device type of the first programmable device can be obtained from the device library. And the manufacturer, and according to the device type of the first programmable device and the manufacturer obtains the software function of the software that the first programmable device can load from the software information library, when the software function includes the acceleration type, the software can be determined The software corresponding to the function is the first software, the first programmable device is the programmable device capable of loading the first software, and the device type and the manufacturer of the first programmable device are the first information, and then the first information is obtained from the software information library. The first storage link and processing capability information of the software. Therefore, the software information library can be directly searched, or the first device library can be searched first, and then the software information library can be searched for the storage link and processing capability information of the required loading software and the information of the programmable device capable of loading the software. Wherein, the first programmable device is any idle programmable device in the first device library.

In one embodiment, the service request further includes a computing resource, and the number of devices of the programmable device that needs to load the first software may be determined according to the acceleration capacity and the processing capability information, and the idle computing resource is selected from the managed server is not less than the The computing server and the first server including the number of programmable devices corresponding to the idle first information are not less than the number of the devices, and the first information corresponding to the number of idle devices of the device is obtained from the programmable device managed by the first server in the device library. The first identifier of the programmable device, and the second identifier of the first server is obtained from the device library, so that the selected server can not only meet the requirements of the service for the acceleration type and the acceleration capacity, but also meet the business requirements for the computing resources. .

In an embodiment, the service request may further include a storage resource, and the number of devices of the programmable device that needs to load the first software may be determined according to the acceleration capacity and the processing capability information, and the idle computing resource is selected from the managed server. a first server managed by the first server in the device library, which is smaller than the computing resource, the free storage resource is not less than the storage resource, and the number of programmable devices corresponding to the idle first information is not less than the number of the device. Obtaining a first identifier of the programmable device corresponding to the idle first information of the device, and acquiring a second identifier of the first server from the device library, so that the selected server can not only satisfy the service for the acceleration type and the acceleration capacity. Requirements, but also meet the business needs for computing resources and storage resources.

In one embodiment, the VIM can receive the second information sent by the second server and can establish a device library including the second information and the identity of the second server, so that the VIM uniformly manages the programmable device. The second information may include a device type, a manufacturer, and an identifier of the second programmable device, and the second server is a server managed by the VIM and used to manage the second programmable device.

In one embodiment, the VIM can also receive the software package and send it to the catalog, so that the catalog store stores the software package and returns a second storage link of the software package, and can receive the second storage link sent by the catalog. And a software information library including a second storage link and software function information, software version information, processing capability information, and third information included in the software package, so that the VIM manages software that can be loaded on the programmable device. The third information may include a device type and a manufacturer of a programmable device capable of loading software corresponding to the software package.

In one embodiment, before the first identifier causes the first server to load the data packet on the programmable device identified by the first identifier, it may first determine whether the programmable device identified by the first identifier in the first server is Loaded with software, when the software is not loaded, the first server can directly load the data packet on the programmable device identified by the first identifier. When the software is loaded and the software does not have the acceleration type, The first server first uninstalls the software on the programmable device identified by the first identifier, and then loads the data packet on the programmable device identified by the first identifier. When the programmable device is not in use, the software to be loaded can be loaded on the programmable device regardless of whether the software is loaded or not, which can improve the flexibility of loading the software on the programmable device.

In one embodiment, the first information may further include a device model of the programmable device capable of loading the first software, and the second information may further include a device model of the second programmable device for device type and production of the programmable device When the manufacturers are all the same, the device can be distinguished by the device model.

A fourth aspect discloses a VIM comprising means for performing the software loading method provided by the third aspect or any of the possible implementations of the third aspect.

A fifth aspect discloses a VIM that includes a processor, a memory, and a transceiver, wherein:

a transceiver, configured to receive, by the NFVO, a service request including an acceleration type and an acceleration capacity, and send the service request to the processor;

A set of program code is stored in the memory, and the processor is used to call the program code stored in the memory to perform the following operations:

Determining, according to the acceleration type and the software information library, a first storage link of the first software having the acceleration type, processing capability information of the first software, and first information of the programmable device capable of loading the first software, and according to the first information And the processing capability information and the acceleration capacity acquire, from the device library, a first identifier of the programmable device that needs to load the first software and is idle, and a second identifier of a server for managing the programmable device identified by the first identifier, first Information can include device type and manufacturer;

The transceiver is further configured to send the first storage link and the first identifier to the first server identified by the second identifier, where the first storage link is used to enable the first server to download the data packet of the first software from the first storage link, The first identification is for causing the first server to load the data packet on the programmable device identified by the first identification.

A sixth aspect discloses a readable storage medium storing program code for a software loading method disclosed by the VIM for performing the third aspect or any of the possible implementations of the third aspect.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings to be used in the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention, Those skilled in the art can also obtain other drawings based on these drawings without paying for creative labor.

1 is a schematic diagram of a network architecture disclosed in an embodiment of the present invention;

2 is a schematic structural diagram of a software loading system according to an embodiment of the present invention;

3 is a schematic structural diagram of a VIM according to an embodiment of the present invention;

4 is a schematic flowchart of a software loading method according to an embodiment of the present invention;

FIG. 5 is a schematic flowchart diagram of another software loading method according to an embodiment of the present disclosure;

6 is a schematic flowchart of still another software loading method according to an embodiment of the present invention;

7 is a schematic flowchart of still another software loading method according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of another VIM disclosed in an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other implementations obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts For example, all fall within the scope of protection of the present invention.

The embodiment of the invention discloses a software loading method, device and system for improving the flexibility of software loading on a programmable device. The details are described below separately.

For a better understanding of a software loading method, device and system disclosed in the embodiments of the present invention, the network architecture used in the embodiment of the present invention is described below. Please refer to FIG. 1. FIG. 1 is a schematic diagram of a network architecture disclosed in an embodiment of the present invention. As shown in FIG. 1, the network architecture may include NFV Management and Orchestration (NFV MANO), Virtual Network Function (VNF), and Network Function Virtualization Infrastructure (Network Function Virtualization Infrastructure, NFVI), Element Manager System (EMS) and Business Support Management System (ie OSS or Business Support System (BSS)). The NFV MANO includes an NFVO, at least one VNFM, at least one VIM, at least one server, and a catalog, and an agent is installed on each server. among them:

NFVO is used to implement network service (NS) lifecycle management (such as deployment/expansion/reduction/downline) in the carrier domain, NFVI resource scheduling, policy management, and network service description (Network Service). Descriptor, NSD) decomposes the need for each VNF and cooperates with VNFM to implement VNF deployment.

VNFM is used to implement VNF lifecycle management (such as deployment/expansion/reduction/downline automation). It needs to decompose virtual resources such as virtual machines according to template and VNF capacity requirements, and complete VNF with NFVO and VIM. Instantiation.

VIM is used to manage and monitor the entire infrastructure layer resources, including computing resources, storage resources, and network resources.

Based on the network architecture shown in FIG. 1, please refer to FIG. 2. FIG. 2 is a schematic structural diagram of a software loading system according to an embodiment of the present invention. Among them, the software loading system is NFV MANO. As shown in FIG. 2, the software loading system may include an NFVO 201, at least one VIM 202, at least one server 203, NFVO 201 managing at least one VIM 202, one VIM 202 may manage one or more servers 203, and one server 203 may manage one or more Programmable device, where:

The NFVO 201 is configured to receive a service request including an acceleration type and an acceleration capacity, determine a first storage link of the first software having an acceleration type, processing capability information of the first software, and a first software capable of loading the first software according to the acceleration type and the software information base. The first information of the programmable device acquires, from the first device library, a first identifier of the VIM 202 for managing the programmable device capable of loading the first software and is idle according to the first information, the processing capability information of the first software, and the acceleration capacity, And transmitting, to the first VIM 202 identified by the first identifier, the first storage link, the first information, and the second information indicating the number of programmable devices that need to load the first software, where the first information may include the device type and the manufacturer. ;

The first VIM 202 is configured to receive the first storage link, the first information, and the second information sent by the NFVO 201, and obtain, from the second device library, the second device that needs to load the first software according to the first information and the second information. And the third identifier of the server for managing the programmable device identified by the second identifier, and sending the first storage link and the second identifier to the first server 203 identified by the third identifier;

The first server 203 is configured to receive the first storage link and the second identifier sent by the first VIM 202, download the data packet of the first software from the first storage link, and load the data packet in the programmable identifier identified by the second identifier. On the device.

As a possible implementation, NFVO201 is used to determine the type of acceleration based on the type of acceleration and the software information base. The first storage link of the first software, the processing capability information of the first software, and the first information of the programmable device capable of loading the first software include:

NFVO201, configured to obtain, from a software information library, a first storage link of the first software having an acceleration type, processing capability information of the first software, and first information of a programmable device capable of loading the first software; or

NFVO201, for obtaining the device type and manufacturer of the first programmable device from the first device library, and obtaining the first programmable device capable of loading from the software information library according to the device type of the first programmable device and the manufacturer Software function of the software, when the software function includes an acceleration type, determining that the software corresponding to the software function is the first software, the first programmable device is a programmable device capable of loading the first software, and the device type of the first programmable device And the manufacturer is the first information, and the first storage link and processing capability information of the first software is obtained from the software information library, and the first programmable device is any idle programmable device in the first device library.

As a possible implementation manner, the second information is a number of devices of the programmable device that needs to load the first software;

The NFVO 201 is further configured to determine the number of devices of the programmable device that need to load the first software according to the acceleration capacity and the processing capability information of the first software.

As a possible implementation manner, the second information may include acceleration capacity and processing capability information of the first software;

The first VIM 202 is configured to acquire, from the second device library, a second identifier of the programmable device that needs to load the first software according to the first information and the second information, and a server that manages the programmable device identified by the second identifier The three logos include:

The first VIM 202 is configured to determine, according to the acceleration capacity and the processing capability information of the first software, the number of devices of the programmable device that needs to load the first software, and select, from the managed server, the number of programmable devices corresponding to the first information that is idle. a first server not less than the number of devices, obtaining a second identifier of the programmable device corresponding to the first information of the device from the programmable device of the first server in the second device library, and the second device from the second device The third identifier of the first server is obtained in the library.

As a possible implementation manner, the service request further includes a computing resource; the first VIM 202 is configured to obtain, from the second device library, the second identifier of the programmable device that needs to load the first software according to the first information and the second information, and A third identifier of a server for managing a programmable device identified by the second identifier includes:

The first VIM 202 is configured to select, from the managed server, that the idle computing resource is not less than the computing resource, and the first server that includes the number of programmable devices corresponding to the idle first information is not less than the number of programmable devices indicated by the second information. Obtaining, from the programmable device of the first server management in the second device library, the second identifier of the programmable device corresponding to the number of programmable devices indicated by the second information, and from the second device library Obtain a third identifier of the first server.

As a possible implementation, the service request may further include a computing resource and a storage resource. The first VIM 202 is configured to obtain, from the second device library, the programmable device that needs to load the first software according to the first information and the second information. The second identifier and the third identifier of the server for managing the programmable device identified by the second identifier include:

The first VIM 202 is configured to select, from the managed server, that the idle computing resource is not less than the computing resource, the storage resource is not less than the storage resource, and the number of programmable devices corresponding to the idle first information is not less than that indicated by the second information. The first server of the number of programmable devices, the second information indicated by the first server managed by the first server in the second device library, the number of programmable devices indicated by the idle first information corresponding to the second programmable device Identifying, and obtaining a third identity of the first server from the second device library.

As a possible implementation manner, the second server 203 is configured to send the third information to the second VIM 202, the second server is a server for managing the second programmable device, and the third information includes the second programmable device. Device type, Manufacturer and logo, the second VIM is a VIM for managing the second server;

The second VIM 202 is configured to receive the third information sent by the second server 203, establish a second device library including the third information and the identifier of the second server, and send the third information and the identifier of the second server to the NFVO 201;

The NFVO 201 is further configured to receive the third information sent by the second VIM 202 and the identifier of the second server, and establish a first device library according to the third information, the identifier of the second server, and the identifier of the second VIM.

As a possible implementation manner, the software loading system may further include a catalogue 204, wherein:

The NFVO 201 is further configured to receive the software package and send the software package to the third VIM or the directory, where the software package includes software function information, software version information, processing capability information, and fourth information, where the fourth information includes programmable software capable of loading the software package corresponding to the software package. Device type and manufacturer of the device;

The third VIM 202 or the catalogue 204 is configured to receive the software package sent by the NFVO 201, store the software package, and send the second storage link of the software package to the NFVO 201;

The NFVO 201 is further configured to receive a second storage link sent by the third VIM 202 or the catalogue 204, and establish software including the second storage link and software function information, software version information, processing capability information, and fourth information included in the software package. database.

As a possible implementation manner, the second identifier is used by the first server to load the data packet on the programmable device identified by the second identifier, including:

The second identifier is configured to, when the software identified by the second identifier in the first server is not loaded with software, cause the first server to load the data packet on the programmable device identified by the second identifier; or

The second identifier is configured to enable the first server to be identified by the second identifier when the second software is loaded on the programmable device identified by the second identifier in the first server, and the second software does not have the acceleration type The second software is unloaded on the programming device and loaded onto the programmable device identified by the second identification.

The first VIM, the second VIM, and the third VIM may be the same VIM, or may be different VIMs. When the first VIM, the second VIM, and the third VIM are different VIMs, they are used to manage different server. The first server and the second server may be the same server or different servers, and the programmable devices on different servers may be the same or different.

Please refer to FIG. 3. FIG. 3 is a schematic structural diagram of a VIM according to an embodiment of the present invention. As shown in FIG. 3, the VIM can include a processor 301, a memory 302, a transceiver 303, and a bus 304. The processor 301 can be a general purpose central processing unit (CPU), a plurality of CPUs, a microprocessor, an application-specific integrated circuit (ASIC), or one or more of the programs for controlling the execution of the program of the present invention. integrated circuit. The memory 302 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions. The dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this. The memory 302 can exist independently and the bus 304 is coupled to the processor 301. The memory 302 can also be integrated with the processor 301. The transceiver 303 is configured to communicate with other devices or communication networks, such as Ethernet, a radio access network (RAN), and a wireless local area network. (Wireless Local Area Networks, WLAN), etc. Bus 304 can include a path for communicating information between the components described above.

among them:

The transceiver 303 is configured to receive, by the NFVO, a service request including an acceleration type and an acceleration capacity, and send the service request to the processor 301;

The memory 302 stores a set of program codes, and the processor 301 is configured to call the program code stored in the memory 302 to perform the following operations:

Determining, according to the acceleration type and the software information library, a first storage link of the first software having the acceleration type, processing capability information of the first software, and first information of the programmable device capable of loading the first software, and according to the first information, Processing capability information and acceleration capacity of a software acquires, from a device library, a first identifier of a programmable device that needs to load the first software and is idle, and a second identifier of a server for managing the programmable device identified by the first identifier, first Information includes device type and manufacturer;

The transceiver 303 is further configured to send the first storage link and the first identifier to the first server identified by the second identifier, where the first storage link is used to enable the first server to download the data packet of the first software from the first storage link. The first identifier is configured to cause the first server to load the data packet on the programmable device identified by the first identifier.

As a possible implementation manner, the processor 301 determines, according to the acceleration type and the software information base, a first storage link of the first software having an acceleration type, processing capability information of the first software, and a programmable device capable of loading the first software. The first information includes:

Acquiring, from a software information repository, a first storage link of the first software having an acceleration type, processing capability information of the first software, and first information of a programmable device capable of loading the first software; or

Obtaining the device type and manufacturer of the first programmable device from the device library, and obtaining the software function of the software that the first programmable device can load according to the device type of the first programmable device and the manufacturer from the software information library. When the software function includes an acceleration type, the software corresponding to the software function is determined to be the first software, the first programmable device is a programmable device capable of loading the first software, and the device type and manufacturer of the first programmable device are the first Information, and obtaining a first storage link and processing capability information of the first software from the software repository, the first programmable device being any idle programmable device in the first device library.

As a possible implementation manner, the service request further includes a computing resource;

The processor 301 acquires, from the device library, the first identifier of the programmable device that needs to load the first software and is free according to the first information, the processing capability information of the first software, and the acceleration capacity, and the programmable device identified by the first identifier. The second identifier of the server includes:

Determining, according to the acceleration capacity and the processing capability information, the number of devices of the programmable device that needs to load the first software, and selecting the idle computing resource from the managed server is not less than the computing resource and the number of programmable devices corresponding to the first information that is idle is not a first server smaller than the number of devices, obtaining a first identifier of the programmable device corresponding to the first information of the device from the programmable device managed by the first server in the device library, and obtaining the first identifier from the device library The second identifier of the server.

As a possible implementation, the transceiver 303 is further configured to receive second information sent by the second server, where the second information includes a device type, a manufacturer, and an identifier of the second programmable device, where the second server is managed by the VIM. And a server for managing the second programmable device;

The processor 301 is further configured to call the program code stored in the memory 302 to perform the following operations:

A device library is created that includes the second information and the identity of the second server.

As a possible implementation, the transceiver 303 is further configured to receive the software package and send the software package to the directory, so that the directory library stores the software package and returns a second storage link of the software package, where the software package includes software function information and software. Version information, processing capability information, and third information, the third information includes a device type and a manufacturer of a programmable device capable of loading the software corresponding to the software package;

The transceiver 303 is further configured to receive the second storage link and send it to the processor 301;

The processor 301 is further configured to call the program code stored in the memory 302 to perform the following operations:

A software information library including a second storage link and software function information, software version information, processing capability information, and third information included in the software package is established.

As a possible implementation manner, the first identifier is used by the first server to load the data packet on the programmable device identified by the first identifier, including:

The first identifier is configured to, when the software identified by the first identifier in the first server is not loaded with software, cause the first server to load the data packet on the programmable device identified by the first identifier; or

The first identifier is configured to enable the first server to identify from the first identifier when the second software is loaded on the programmable device identified by the first identifier in the first server, and the second software does not have the acceleration type The second software is unloaded on the programming device and loaded onto the programmable device identified by the first identification.

In a specific implementation, as a possible implementation manner, the VIM may further include an input device 305 and an output device 306. The output device 306 is in communication with the processor 301, and the information may be displayed in various manners. For example, the output device 306 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait. Input device 305 is in communication with processor 301 and can accept user input in a variety of ways. For example, input device 305 can be a mouse, keyboard, touch screen device, or sensing device, and the like.

The structure of the NFVO and the server may be the same as the structure of the VIM shown in FIG. 3.

Based on the network architecture shown in FIG. 1 or FIG. 2, please refer to FIG. 4. FIG. 4 is a schematic flowchart of a software loading method according to an embodiment of the present invention. Among them, the software loading method is described from the perspective of NFVO, VIM and server. As shown in FIG. 4, the software loading method may include the following steps.

401. The NFVO receives a service request including an acceleration type and an acceleration capacity.

The service request may be sent by the OSS/BSS, or may be sent by the VNFM, or may be sent by a third-party device other than the OSS/BSS and the VNFM. The acceleration type can be encryption/decryption, audio transcoding, or video transcoding. The acceleration capacity can be 10M PPS, 100 channels/s, 200 channels/s, and the like.

In this embodiment, the service request may further include an IP address of the service request sender. After receiving the service request, the NFVO may first determine whether the IP address is an authorized IP address, and when the IP address is an authorized IP address, indicating the service. If the request is a legitimate request, the following steps will be performed; when the IP address is not an authorized IP address, indicating that the service request is an illegal request, the subsequent steps will not be performed.

402. The NFVO determines, according to the acceleration type and the software information base, a first storage link of the first software having the acceleration type, processing capability information of the first software, and first information of the programmable device capable of loading the first software, and according to the first Information, processing capability information of the first software, and acceleration capacity obtain a first identification of a virtualized infrastructure manager VIM for managing a programmable device capable of loading the first software and free from the first device library, and the first storage Links, first information, and use The second information indicating the number of programmable devices that need to load the first software is sent to the first VIM identified by the first identifier.

In this embodiment, after the NFVO receives the service request including the acceleration type and the acceleration capacity, the software having the acceleration type may be determined from the software information base, and the software having the acceleration type found for the first time may be used as the first Software, then obtaining first storage link and processing capability information of the first software from the software information repository, and first information of the programmable device capable of loading the first software, and then according to the first information, the processing capability information, and the acceleration capacity A first identification of a VIM for managing a programmable device capable of loading the first software and free is obtained directly from the first device library. When the second information is the number of devices of the programmable device that needs to load the first software, the NFVO may first determine the number of devices of the programmable device that needs to load the first software according to the acceleration capacity and the processing capability information of the first software, for example: The acceleration capacity is 250 channels/s, and the processing capacity of the first software is 100 channels/s. The number of devices that need to load the first software programmable device is 3, and then can be obtained from the first device library for management first. The first identifier of the VIM corresponding to the number of the devices is not less than the first identifier of the VIM of the programmable device in the first device library; When the number of programming devices is less than 1, the first identifier of at least two VIMs may be selected from the first device library, and the total number of programmable devices corresponding to the first information in the at least two VIMs and idle is not less than the number of the devices. . When the second information includes the acceleration capacity and the processing capability information, the NFVO directly acquires a first identifier of the VIM for managing the programmable device corresponding to the first information and is free from the first device library. The first information may include the device type and the manufacturer, as well as the device type, manufacturer, and device model.

In an embodiment, after the NFVO receives the service request including the acceleration type and the acceleration capacity, the software having the acceleration type and the processing capability not less than the acceleration capacity may be determined from the software information library as the first software, thereby reducing loading. The number of software programmable devices.

In this embodiment, the NFVO may also first obtain the device type and manufacturer (or device type, manufacturer, and device model) of the first programmable device from the first device library, and according to the device type of the first programmable device and The manufacturer obtains the software function of the software that the first programmable device can load from the software information library, and then determines whether the software function includes the acceleration type. When the software function includes the acceleration type, the software corresponding to the software function is determined to be The first software, the first programmable device is a programmable device capable of loading software with an acceleration type, and the device type and manufacturer of the first programmable device are the first information, and then the first software is obtained from the software information library. A storage link and processing capability information, and a first identification of the VIM for managing the first programmable device from the first device library. When the software function does not include the acceleration type, the above operation will be performed again for another programmable device in the first device library. Wherein, the first programmable device can be any idle programmable device in the first device library. Among them, the first device library and the software information library can be stored in NFVO or stored elsewhere.

In this embodiment, the service request may further include a computing resource and/or a storage resource. When the number of the first identifier is one, the idle computing resource of the VIM identified by the first identifier is not less than the computing resource and/or the idle storage resource. If the number of the first identifier is greater than one, the total idle computing resource of the VIM identified by the first identifier is not less than the computing resource and/or the total idle storage resource is not less than the storage resource. The first storage link, the first information, and the second information can be avoided from being sent to a VIM that does not have sufficient computing resources and/or storage resources, thereby avoiding loading the software on a programmable device that does not meet the business requirements.

In this embodiment, the NFVO may directly send the first storage link, the first information, and the second information to the first VIM identified by the first identifier, or firstly, the first identifier, the first storage link, the first information, and The second information is sent to the VNFM, and the first storage link, the first information, and the second information are sent by the VNFM to the first VIM identified by the first identifier.

In one embodiment, when a piece of software is loaded onto a programmable device, it can be recorded in the software repository. Which of the VIM-managed devices on the server is loaded with this software so that the programmable device loaded with the software can be quickly found.

In one embodiment, when software is loaded on a programmable device, the software functionality and processing capabilities of the software, or the memory connection of the software, can be recorded in the device library so that it can be quickly found through the device library. Information about the software loaded on the device.

403. The first VIM obtains, from the second device library, the second identifier of the programmable device that needs to load the first software according to the first information and the second information, and the server that manages the programmable device identified by the second identifier. And identifying the first storage link and the second identifier to the first server identified by the third identifier.

In this embodiment, after the first VIM receives the first storage link, the first information, and the second information, when the second information is the number of devices of the programmable device that needs to load the first software, the first VIM will directly go from the first A VIM-managed server selects a first server including a number of programmable devices corresponding to the idle first information, and the number of the devices is not less than the number of the devices, and obtains the number of devices from the programmable device managed by the first server in the second device library. The first identifier of the idle first information corresponds to the second identifier of the programmable device, and the third identifier of the first server is obtained from the second device library. When the second information includes the acceleration capacity and the processing capability information of the first software, the number of devices of the programmable device that needs to load the first software needs to be determined according to the acceleration capacity and the processing capability information of the first software.

In this embodiment, the service request may further include a computing resource and/or a storage resource, and the NFVO may also send the computing resource and/or the storage resource to the first VIM, and the first server selected by the first VIM from the server managed by the first VIM, The number of programmable devices corresponding to not only the first information to be free is not less than the number of the devices, and the idle computing resources are not less than the computing resources and/or the idle storage resources are not less than the storage resources.

404. The first server downloads the data packet of the first software from the first storage link, and loads the data packet on the programmable device identified by the second identifier.

In this embodiment, after receiving the first storage link and the second identifier sent by the first VIM, the first server downloads the data packet (ie, the installation package) of the first software from the first storage link, and then the second identifier. When the software is not loaded on the identified programmable device, the data packet is directly loaded on the programmable device identified by the second identifier; when the programmable device identified by the second identifier is loaded with the second software, and the When the software does not have the acceleration type, the second software needs to be unloaded from the programmable device identified by the second identifier, and then the data packet is loaded on the programmable device identified by the second identifier; If the second software is loaded on the programmable device identified by the second identifier, and the second software has the acceleration type, it is determined whether the capacity corresponding to the processing capability information of the second software is smaller than the capacity corresponding to the processing capability information of the first software. When less than, the second software needs to be unloaded from the programmable device identified by the second identifier, and then the data packet is loaded into the programmable device identified by the second identifier. On, when not less than the second software directly as the first software.

In this embodiment, after the first server loads the data packet on the programmable device identified by the second identifier, the NFVO may modify the usage status of the programmable device identified by the second identifier in the first device library to Use and add the software version information of the first software and modify the first software in the software repository to the list of software loaded with the programmable device. Similarly, the VIM can also modify the usage status of the programmable device identified by the second identifier in the first device library to be used, and add the storage connection of the first software, or the software function information and processing capability of the first software. information. Among them, the software function information is information of the acceleration type that the software has.

In the software loading method described in FIG. 4, when the NFVO receives the service request including the acceleration type and the acceleration capacity, the software having the acceleration type is obtained from the software information base and the device library according to the acceleration type and the acceleration capacity. Deposit Store link and processing capability information and information of a programmable device capable of loading the software, and load the software on the programmable device according to the storage link, processing capability information, and the information, and can dynamically be on the programmable device according to business needs Loading the appropriate software can increase the flexibility of software loading on programmable devices.

Based on the network architecture shown in FIG. 1 or FIG. 2, please refer to FIG. 5. FIG. 5 is a schematic flowchart diagram of another software loading method according to an embodiment of the present invention. Among them, the software loading method is described from the perspective of NFVO, VIM and server. As shown in FIG. 5, the software loading method may include the following steps.

501. The second server sends the third information to the second VIM.

In this embodiment, an interface is disposed on each programmable device in the second server, and the second programmable device in the second server can report the third information to the proxy on the second server through the interface, and then the second server The third information can be reported to the second VIM through the proxy. The second VIM is any VIM managed by the NFVO, the second server is any server managed by the second VIM, the second programmable device is any programmable device in the second server, and the third information may include the second The device type, manufacturer, and identification of the programmable device, and the second VIM is the VIM used to manage the second server. For example, the identifier of the programmable device, such as number-1, indicates FPGA-1, number-2 indicates FPGA-2, and number-3 indicates image processing unit (GPU)-1. The second server may send the third information to the second VIM, or the NFVO may send the programmable device information acquisition request to the second VIM. After the second VIM sends the programmable device information acquisition request to the second server, The second server sends to the second VIM. The third information may also include the device type of the second programmable device.

502. The second VIM establishes a second device library including the third information and the identifier of the second server, and sends the third information and the identifier of the second server to the NFVO.

In this embodiment, after the second VIM receives the third information sent by the proxy of the second server, a second device library including the identifier of the third information and the second server is established, and the second VIM may already exist in the second VIM. The device library simply adds the third information and the identifier of the second server to the second device library; or the second device library does not exist in the second VIM, the second device library is established, and the third information and the second information are The identity of the server is added to the second device library. The second device library can be as shown in Table 1:

index	Device type	Manufacturer	Location identifier	status of use	Software storage connection
1	FPGA	Vendor-A	Server 1+ number 1	Unallocated	......	......
2	FPGA	Vendor-A	Server 1+ number 2	Unallocated	......	......
3	FPGA	Vendor-B	Server 2+ number 1	allocated	Url-2	......
4	GPU	Vendor-C	Server 3+ number 1	Unallocated	......	......
5	......	......	......	......	......	......

Table 1 second device library

503. The NFVO establishes a first device library according to the third information, the identifier of the second server, and the identifier of the second VIM.

In this embodiment, after receiving the third information sent by the second VIM and the identifier of the second server, the NFVO may establish the first device library according to the third information, the identifier of the second server, and the identifier of the second VIM, which may be NFVO. When the first device already exists, only the third information, the identifier of the second server, and the identifier of the second VIM are added to the first device library; or the first device library does not exist in the second VIM, and the first device is established. Device library, and the third information, the identity of the second server, and The identity of the second VIM is added to the first device library. Among them, the first device library can be as shown in Table 2:

index	Device type	Manufacturer	VIM logo	Number of devices used	Number of unused devices
1	FPGA	Vendor-A	VIM1	0	1	...
2	FPGA	Vendor-A	VIM1	3	2	...
3	FPGA	Vendor-B	VIM2	1	2	...
4	GPU	Vendor-C	VIM3	0	1	...
5	...	...	...	...	...	...

Table 2 First device library

Wherein, when the software is loaded on the programmable device, the software function and processing capability information of the software, or the url connection may be stored in the first device library, so that the programmable device loaded with the software can be quickly found. Can reduce software load time.

In an embodiment, the second VIM may also send the third information and the identifier of the second server to the OSS/BSS, and the OSS/BSS may send the device identifier to the NFVO according to the information of the programmable device reported by the second VIM. The software operation instruction, the NFVO sends the software operation instruction to the programmable device corresponding to the device identifier, and the programmable device executes the software operation instruction. The software operation instruction may be a software load instruction, a software uninstallation instruction, a software update instruction, or a software upgrade instruction.

504. The NFVO receives the software package and sends it to the third VIM or the catalog.

The software package may include software function information, software version information, processing capability information, and fourth information, and the fourth information may include a device type and a manufacturer capable of loading a programmable device corresponding to the software corresponding to the software package, and the software function may be Decryption acceleration, or audio transcoding acceleration, etc., processing capability information is the maximum capacity that the software can handle the service, such as 6M PPS encryption and decryption acceleration.

The 505, the third VIM, or the directory repository stores the package and sends a second storage link of the package to the NFVO.

506. The NFVO establishes a software information library including a second storage link and software function information, software version information, processing capability information, and fourth information included in the software package.

In this embodiment, when the software information base already exists in the NFVO, the above information is added to the software information base. When the software information base does not exist in the NFVO, the software information base may be established first, and the above information may be added to the software information. In the library. The software repository can also include which programmable devices have been loaded to index to the device library to see if the software is being used. Among them, the software information base can be as shown in Table 3:

index	Software function	Software version	Processing capacity	Storage link	Device type	Manufacturer	...
1	Add and decrypt	Ver-1	10M PPS	Url-1	FPGA	Vendor-A	...
2	Audio transcoding	Ver-1	100 roads/s	Url-2	FPGA	Vendor-A	...
3	Mixing	Ver-1	100 roads/s	Url-3	FPGA	Vendor-B	...
4	Video transcoding	Ver-1	100 roads/s	Url-4	GPU	Vendor-C	...
5	...	...	...	...	...	...	...

Table 3 Software Information Library

The steps 507-510 are the same as the steps 401-404 in the previous embodiment, and are not described herein again.

In the software loading method described in FIG. 5, when the NFVO receives a service request including an acceleration type and an acceleration capacity, According to the acceleration type and the acceleration capacity, a storage link of the software having the acceleration type and a programmable device capable of loading the software are acquired from the software information base and the device library, and the software is loaded according to the storage link and the information. On the programmable device, the corresponding software can be dynamically loaded on the programmable device according to business needs, which can improve the flexibility of software loading on the programmable device.

Based on the network architecture shown in FIG. 1 or FIG. 2, please refer to FIG. 6. FIG. 6 is a schematic flowchart diagram of still another software loading method according to an embodiment of the present invention. Among them, the software loading method is described from the perspective of VIM. As shown in FIG. 6, the software loading method may include the following steps.

601. Receive a service request that is sent by the NFVO, including an acceleration type and an acceleration capacity.

The service request may be sent by the OSS/BSS to the NFVO, or may be sent by the VNFM to the NFVO, or may be sent to the NFVO by a third party device other than the OSS/BSS and the VNFM. The acceleration type can be encryption/decryption, audio transcoding, or video transcoding. The acceleration capacity can be 10M PPS, 100 channels/s, 200 channels/s, and the like.

Wherein, step 601 can be performed by a transceiver in the VIM.

602. Determine, according to the acceleration type and the software information repository, a first storage link of the first software having the acceleration type, processing capability information of the first software, and first information of the programmable device capable of loading the first software, and according to the first information. The processing capability information and the acceleration capacity of the first software acquire a first identifier of the programmable device that needs to load the first software and is free from the device library, and a second identifier of the server for managing the programmable device identified by the first identifier.

In this embodiment, after the VIM receives the service request including the acceleration type and the acceleration capacity, the software having the acceleration type may be determined from the software information base, and the software having the acceleration type found for the first time may be used as the first The software can also use software with a processing capacity greater than the acceleration capacity as the first software. And acquiring, from the software information library, a first storage link of the first software having the acceleration type, processing capability information of the first software, and first information of the programmable device capable of loading the first software, according to the acceleration capacity and the first software The processing capability information calculates the number of devices of the programmable device that need to load the first software and is idle, and selects, from the server managed by the VIM, the first server that includes the number of programmable devices corresponding to the idle first information, not less than the number of the devices. And obtaining, from the programmable device managed by the first server in the device library, a first identifier of the programmable device corresponding to the number of idle first information of the device, and acquiring a second identifier of the first server from the device library.

In this embodiment, after the VIM receives the service request including the acceleration type and the acceleration capacity, the device type and the manufacturer of the first programmable device may also be obtained from the device library, and according to the device type and production of the first programmable device. The manufacturer obtains the software function of the software that can be loaded by the first programmable device from the software information library, and then determines whether the software function includes the acceleration type. When the software function includes the acceleration type, determining that the software corresponding to the software function is the first a software, the first programmable device is a programmable device capable of loading the first software, and the device type and manufacturer of the first programmable device are the first information, and the first storage link of the first software is obtained from the software information library and Processing the capability information, and calculating, according to the acceleration capacity and the processing capability information of the first software, the number of devices that need to load the first software and the idle programmable device, when the first information that is idle in the server managing the first programmable device corresponds to When the number of programming devices is not less than the number of devices, the first programmable device will be directly managed. The identifier of the server is used as the first identifier; when the number of programmable devices corresponding to the first information idle in the server managing the first programmable device is less than the number of the device, the first information of the idle management of the VIM may be corresponding The number of programming devices is not less than the number of the device, and the identifier of the server is used as the first identifier; when the number of programmable devices corresponding to the first information that is idle in the server managed by the VIM is smaller than the number of the devices, the device library may be selected. a second identifier of at least two servers, the second of which is at least two servers The total number of programmable devices that correspond to one information and is idle is not less than the number of devices. The first information includes the device type and manufacturer. The first programmable device can be any free programmable device in the device library.

In this embodiment, the service request may further include a computing resource and/or a storage resource. When the number of the second identifier server is one, the idle computing resource of the server identified by the second identifier is not less than the computing resource and/or the idle storage resource. Not less than the storage resource; when the number of servers identified by the second identifier is greater than one, the total idle computing resource of the server identified by the second identifier is not less than the computing resource and/or the total idle storage resource is not less than the storage resource. You can avoid loading software on programmable devices that do not meet your business needs.

Wherein, step 602 can be performed by the processor in the VIM calling the program code stored in the memory.

603. Send the first storage link and the first identifier to the first server identified by the second identifier.

In this embodiment, the VIM may send the first storage link and the first identifier to the first server identified by the second identifier, so that the first server downloads the data packet (ie, the installation package) of the first software from the first storage link. Then, when the software is not loaded on the programmable device identified by the first identifier, the data packet is directly loaded on the programmable device identified by the first identifier, and the programmable device identified by the first identifier is loaded with When the second software does not have the acceleration type, the second software needs to be uninstalled from the programmable device identified by the first identifier, and then the data packet is loaded in the first identifier. On the programming device.

Wherein, step 603 can be performed by a transceiver in the VIM.

In the software loading method described in FIG. 6, when the VIM receives the service request including the acceleration type and the acceleration capacity, the software having the acceleration type is obtained from the software information base and the device library according to the acceleration type and the acceleration capacity. The storage link and the identifier of the programmable device capable of loading the software, so that the software is loaded on the programmable device according to the storage link and the information, and the corresponding software can be dynamically loaded on the programmable device according to business needs, Improve the flexibility of software loading on programmable devices.

Based on the network architecture shown in FIG. 1 or FIG. 2, please refer to FIG. 7. FIG. 7 is a schematic flowchart diagram of still another software loading method according to an embodiment of the present invention. Among them, the software loading method is described from the perspective of VIM. As shown in FIG. 7, the software loading method may include the following steps.

701. Receive second information sent by the second server, and establish a device library that includes the second information and the identifier of the second server.

The second information includes a device type, a manufacturer, and an identifier of the second programmable device, and the second server is a server managed by the VIM and used to manage the second programmable device.

The second information sent by the receiving second server in step 701 may be performed by a transceiver in the VIM, and the device library in step 701 for establishing the identifier of the second information and the second server may be a processor in the VIM. Called by the program code stored in the memory.

702. Receive a software package and send the same to the catalog, so that the catalog store stores the software package and returns a second storage link of the software package.

The software package may include software function information, software version information, processing capability information, and fifth information, and the third information may include a device type and a manufacturer of a programmable device capable of loading the software corresponding to the software package. The software package may be sent by NFVO or not by NFVO.

Among them, VIM can also store the software package directly in VIM.

Wherein, step 702 can be performed by a transceiver in the VIM.

703. Receive a second storage link, and establish a software information library including a second storage link and software function information, software version information, processing capability information, and third information included in the software package.

The receiving the second storage link in step 703 may be performed by a transceiver in the VIM, and the establishing in step 701 includes the second storage link and software function information, software version information, processing capability information, and the The three-information software information base may be executed by the program code stored in the processor call memory in the VIM.

The steps 704-706 are the same as the steps 601-603 in the previous embodiment, and are not described herein again.

In the software loading method described in FIG. 7, when the VIM receives the service request including the acceleration type and the acceleration capacity, the software having the acceleration type is obtained from the software information base and the device library according to the acceleration type and the acceleration capacity. The storage link and the identifier of the programmable device capable of loading the software, so that the software is loaded on the programmable device according to the storage link and the information, and the corresponding software can be dynamically loaded on the programmable device according to business needs, Improve the flexibility of software loading on programmable devices.

Based on the network architecture shown in FIG. 1 or FIG. 2, please refer to FIG. 8. FIG. 8 is a schematic structural diagram of another VIM according to an embodiment of the present invention. As shown in FIG. 8, the VIM may include:

The communication unit 801 is configured to receive a service request that is sent by the NFVO, including an acceleration type and an acceleration capacity.

a determining unit 802, configured to determine, according to an acceleration type and a software information base received by the communication unit 801, a first storage link of the first software having an acceleration type, processing capability information of the first software, and a programmable device capable of loading the first software First information, the first information includes the device type and the manufacturer;

The obtaining unit 803 is configured to acquire, from the device library, the first device that needs to load the first software and is idle according to the first information determined by the determining unit 802, the processing capability information determined by the determining unit 802, and the acceleration capacity received by the communication unit 801. And a second identifier of the server for managing the programmable device identified by the first identifier;

The communication unit 801 is further configured to send the first storage link determined by the determining unit 802 and the first identifier acquired by the obtaining unit 803 to the first server identified by the second identifier acquired by the obtaining unit 803, where the first storage link is used to enable The first server downloads the data packet of the first software from the first storage link, and the first identifier is used to cause the first server to load the data packet on the programmable device identified by the first identifier.

As a possible implementation manner, the communication unit 801 is further configured to receive second information sent by the second server, where the second information includes a device type, a manufacturer, and an identifier of the second programmable device, where the second server is managed by the VIM. And a server for managing the second programmable device;

VIM can also include:

The first establishing unit 804 is configured to establish a device library including the second information received by the communication unit and the identifier of the second server.

Specifically, the obtaining unit 803 acquires the first software that needs to be loaded and is idle according to the first information determined by the determining unit 802, the processing capability information determined by the determining unit 802, and the acceleration capacity received by the communication unit 801 from the device library established by the first establishing unit 804. a first identifier of the programmable device and a second identifier of a server for managing the programmable device identified by the first identifier

As a possible implementation manner, the communication unit 801 is further configured to receive the software package and send the file to the directory, so that the directory library stores the software package and returns a second storage link of the software package, where the software package includes software function information. , software version information, processing capability information, and third information, the third information includes a device type and a manufacturer of a programmable device capable of loading the software corresponding to the software package;

The communication unit 801 is further configured to receive a second storage link.

VIM can also include:

The second establishing unit 805 is configured to establish a software information library including the second storage link received by the communication unit 801 and the software function information, the software version information, the processing capability information, and the third information included in the software package.

Specifically, the determining unit 802 determines, according to the acceleration type received by the communication unit 801 and the software information base established by the second establishing unit 805, the first storage link of the first software having the acceleration type, the processing capability information of the first software, and the loadable The first information of a software programmable device.

In this embodiment, the VIM 800 is presented in the form of a functional unit. A "unit" herein may refer to an application-specific integrated circuit (ASIC), a processor and memory that executes one or more software or firmware programs, integrated logic circuits, and/or other devices that provide the functionality described above. . In a simple embodiment, those skilled in the art will appreciate that the VIM 800 can take the form shown in FIG. The communication unit 801 can be implemented by the processor and the memory of FIG. 3. The determining unit 802, the obtaining unit 803, the first establishing unit 804, and the second establishing unit 805 can be implemented by the processor and the memory of FIG.

The embodiment of the invention further discloses a readable storage medium storing program code of the VIM for executing the software loading method shown in FIG. 6 or FIG. 7.

A person skilled in the art may understand that all or part of the various steps of the foregoing embodiments may be performed by a program to instruct related hardware. The program may be stored in a computer readable storage medium, and the storage medium may include: Flash disk, read-only memory (ROM), random access memory (RAM), disk or optical disk.

Although the present invention has been described herein in connection with the embodiments of the present invention, it will be understood by those skilled in the <RTIgt; Other variations of the disclosed embodiments are achieved. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill several of the functions recited in the claims. Certain measures are recited in mutually different dependent claims, but this does not mean that the measures are not combined to produce a good effect.

The software loading method, device and system in the distributed system disclosed in the embodiments of the present invention are described in detail above. The principles and implementation manners of the present invention are described in the specific examples. The description of the above embodiments is only for helping. The method of the present invention and its core idea are understood; at the same time, for those skilled in the art, according to the idea of the present invention, there are changes in the specific embodiments and application scopes. It should be understood that the invention is limited.

Claims (26)

1. A software loading method, comprising:

   The network function virtualization orchestration NFVO receives a service request, and the service request includes an acceleration type and an acceleration capacity;

   Determining, by the NFVO, a first storage link of the first software having the acceleration type, processing capability information of the first software, and a programmable device capable of loading the first software according to the acceleration type and a software information base First information, and acquiring, from the first device library, a virtualized infrastructure management for managing a programmable device capable of loading the first software and being idle according to the first information, the processing capability information, and the acceleration capacity a first identifier of the VIM, the first information including a device type and a manufacturer;

   The NFVO sends the first storage link, the first information, and second information indicating the number of programmable devices that need to load the first software to the first VIM identified by the first identifier;

   Determining, by the first VIM, the second identifier of the programmable device that needs to load the first software from the second device library according to the first information and the second information, and for managing the identifier of the second identifier The third identifier of the server of the programmable device;

   Transmitting, by the first VIM, the first storage link and the second identifier to a first server identified by the third identifier, where the first storage link is used to make the first server from the first A storage link downloads a data packet of the first software, the second identifier being used to cause the first server to load the data packet on a programmable device identified by the second identifier.
2. The method according to claim 1, wherein the NFVO determines a first storage link of the first software having the acceleration type, and processing capability information of the first software according to the acceleration type and a software information base. And the first information of the programmable device capable of loading the first software includes:

   The NFVO acquires, from a software information repository, a first storage link of the first software having the acceleration type, processing capability information of the first software, and first information of a programmable device capable of loading the first software; or

   The NFVO acquires a device type and a manufacturer of the first programmable device from the first device library, and obtains the first programmable device from a software information base according to a device type of the first programmable device and a manufacturer a software function of the loadable software, when the software function includes the acceleration type, determining that the software corresponding to the software function is the first software, and the first programmable device is capable of loading the first software The device type and the manufacturer of the first programmable device are the first information, and the first storage link and the processing capability information of the first software are obtained from the software information library, the first The programming device is any free programmable device in the first device bank.
3. The method according to claim 1 or 2, wherein the second information is a number of devices of a programmable device that needs to load the first software;

   The method further includes:

   The NFVO determines the number of devices of the programmable device that need to load the first software based on the acceleration capacity and the processing capability information.
4. The method according to claim 1 or 2, wherein the second information comprises the acceleration capacity and the processing capability information;

   Determining, by the first VIM, the second identifier of the programmable device that needs to load the first software from the second device library according to the first information and the second information, and for managing the identifier of the second identifier The third identifier of the server of the programmable device includes:

   Determining, by the first VIM, the number of devices of the programmable device that needs to load the first software according to the acceleration capacity and the processing capability information, and selecting, from the managed server, the programmable corresponding to the first information that is idle a first server having a number of devices not less than the number of devices, and obtaining, from the programmable device managed by the first server in the second device library, the number of idle programmable devices corresponding to the first information a second identifier, and obtaining a third identifier of the first server from the second device library.
5. The method according to any one of claims 1 to 3, wherein the service request further comprises a computing resource;

   Determining, by the first VIM, the second identifier of the programmable device that needs to load the first software from the second device library according to the first information and the second information, and for managing the identifier of the second identifier The third identifier of the server of the programmable device includes:

   The first VIM selects, from the managed server, that the idle computing resource is not less than the computing resource, and the number of programmable devices corresponding to the idle first information is not less than the programmable device indicated by the second information. a quantity of the first server, obtaining, from the programmable device of the first server managed in the second device library, the number of programmable devices indicated by the second information, and the programmable device corresponding to the first information that is idle a second identifier, and obtaining a third identifier of the first server from the second device library.
6. The method according to any one of claims 1 to 5, wherein the method further comprises:

   The second VIM receives the third information sent by the second server, establishes a second device library including the third information and the identifier of the second server, and sends the identifier of the third information and the second server For the NFVO, the third information includes a device type, manufacturer, and identification of the second programmable device, the second server is a server for managing the second programmable device, and the second VIM is a VIM for managing the second server;

   The NFVO establishes a first device library according to the third information, the identifier of the second server, and the identifier of the second VIM.
7. The method according to any one of claims 1 to 6, wherein the method further comprises:

   The NFVO receives the software package and sends the software package to the third VIM or the directory, the software package includes software function information, software version information, processing capability information, and fourth information, where the fourth information includes Device type and manufacturer of software programmable devices;

   The third VIM or the directory library stores the software package, and sends a second storage link of the software package to the NFVO;

   The NFVO establishes a software information library including the second storage link and software function information, software version information, processing capability information, and fourth information included in the software package.
8. The method according to any one of claims 1 to 7, wherein the second identifier is for causing the first server to load the data packet on a programmable device identified by the second identifier include:

   The second identifier is configured to enable the first server to load the data packet in the second when software is not loaded on the programmable device identified by the second identifier in the first server Identifying the identified programmable device; or

   The second identifier is configured to: when the second software is loaded on the programmable device identified by the second identifier in the first server, and the second software does not have the acceleration type, The first server unloads the second software from the programmable device identified by the second identifier and loads the data packet on the programmable device identified by the second identifier.
9. A software loading method, the method being applied to a virtualized infrastructure manager VIM, comprising:

   The receiving network function virtualizes the service request sent by the NFVO including the acceleration type and the acceleration capacity;

   Determining, according to the acceleration type and the software information library, a first storage link of the first software having the acceleration type, processing capability information of the first software, and first information of a programmable device capable of loading the first software And acquiring, from the device library, a first identifier of the programmable device that needs to load the first software and is idle according to the first information, the processing capability information, and the acceleration capacity, and for managing the first identifier a second identifier of the server of the identified programmable device, the first information including the device type and the manufacturer;

   Sending the first storage link and the first identifier to a first server identified by the second identifier, the first storage link being used to download the first server from the first storage link a data packet of the first software, the first identifier being used to cause the first server to load the data packet on a programmable device identified by the first identifier.
10. The method according to claim 9, wherein the determining, according to the acceleration type and the software information base, a first storage link of the first software having the acceleration type, processing capability information of the first software, and The first information of the programmable device capable of loading the first software includes:

    Acquiring, from a software information repository, a first storage link of the first software having the acceleration type, processing capability information of the first software, and first information of a programmable device capable of loading the first software; or

    Obtaining a device type and a manufacturer of the first programmable device from the device library, and obtaining, according to the device type of the first programmable device, and the manufacturer, the software that can be loaded by the first programmable device from the software information library a software function, when the software function includes the acceleration type, determining that software corresponding to the software function is first software, the first programmable device is a programmable device capable of loading the first software, and The device type and manufacturer of the first programmable device are first information, and the first storage link and processing capability information of the first software is obtained from the software information library, the first programmable device is the Any free programmable device in the first device bank.
11. The method according to claim 9 or 10, wherein the service request further comprises a computing resource;

    And acquiring, from the device library, a first identifier of the programmable device that needs to load the first software and is idle according to the first information, the processing capability information, and the acceleration capacity, and for managing the first identifier The second identification of the server of the identified programmable device includes:

    Determining, according to the acceleration capacity and the processing capability information, a number of devices of the programmable device that need to load the first software, and selecting, from the managed server, that the idle computing resource is not less than the computing resource and including the idle a first server in which the number of programmable devices corresponding to the information is not less than the number of the devices, and the first information corresponding to the number of the devices is obtained from the programmable device managed by the first server in the device library. A first identification of the programmable device and obtaining a second identification of the first server from the library of devices.
12. The method of any of claims 9-11, wherein the method further comprises:

    Receiving second information sent by the second server, the second information including device type, production of the second programmable device a manufacturer and an identifier, the second server being a server managed by the VIM and configured to manage the second programmable device;

    A device library including the second information and the identity of the second server is established.
13. The method according to any one of claims 9 to 12, wherein the method further comprises:

    Receiving a software package and sending it to a catalog, such that the catalog store stores the software package and returns a second storage link of the software package, the software package including software function information, software version information, processing capability information, and Three information, the third information includes a device type and a manufacturer of a programmable device capable of loading the software corresponding to the software package;

    Receiving the second storage link, and establishing a software information library including the second storage link and software function information, software version information, processing capability information, and third information included in the software package.
14. The method according to any one of claims 9 to 13, wherein the first identifier is for causing the first server to load the data packet on a programmable device identified by the first identifier include:

    The first identifier is configured to enable the first server to load the data packet in the first when software is not loaded on the programmable device identified by the first identifier in the first server Identifying the identified programmable device; or

    The first identifier is configured to: when the second software is loaded on the programmable device identified by the first identifier in the first server, and the second software does not have the acceleration type, The first server unloads the second software from the programmable device identified by the first identifier and loads the data packet on the programmable device identified by the first identifier.
15. A software loading system, comprising: a network function virtualization orchestration NFVO and a first virtualization infrastructure manager VIM, wherein:

    The NFVO is configured to receive a service request including an acceleration type and an acceleration capacity, and determine, according to the acceleration type and the software information base, a first storage link of the first software having the acceleration type, and a processing capability of the first software. Information and first information of a programmable device capable of loading the first software, acquired from the first device library according to the first information, the processing capability information, and the acceleration capacity for managing loading the first a first identification of the VIM of the software and idle programmable device, and transmitting the first storage link, the first information, and second information indicating a number of programmable devices that need to load the first software to The first VIM identified by the first identifier, the first information includes a device type and a manufacturer;

    The first VIM, configured to receive the first storage link, the first information, and the second information sent by the NFVO, according to the first information and the second information, from a second device library Obtaining a second identifier of a programmable device that needs to load the first software and a third identifier of a server for managing a programmable device identified by the second identifier, and linking the first storage link and the Transmitting, to the first server identified by the third identifier, the first storage link is configured to enable the first server to download a data packet of the first software from the first storage link, The second identifier is for causing the first server to load the data packet on the programmable device identified by the second identifier.
16. The system according to claim 15, wherein said NFVO is configured to determine a first storage link of said first software having said acceleration type, said first software processing according to said acceleration type and software information base The first information of the capability information and the programmable device capable of loading the first software includes:

    The NFVO, configured to acquire, from a software information repository, a first storage link of the first software having the acceleration type, processing capability information of the first software, and a programmable device capable of loading the first software a message; or

    The NFVO is configured to obtain a device type and a manufacturer of the first programmable device from the first device library, and obtain the first from the software information library according to the device type of the first programmable device and the manufacturer. a software function of the software that can be loaded by the programmable device, when the software function includes the acceleration type, determining that the software corresponding to the software function is the first software, and the first programmable device is capable of loading the first The programmable device of the software and the device type and manufacturer of the first programmable device are first information, and the first storage link and processing capability information of the first software is obtained from the software information library, The first programmable device is any free programmable device in the first device bank.
17. The system according to claim 15 or 16, wherein said second information is a number of devices of a programmable device that needs to load said first software;

    The NFVO is further configured to determine, according to the acceleration capacity and the processing capability information, a number of devices of a programmable device that needs to load the first software.
18. The system according to claim 15 or 16, wherein said second information comprises said acceleration capacity and said processing capability information;

    The first VIM is configured to acquire, from the second device library, a second identifier of the programmable device that needs to load the first software according to the first information and the second information, and to manage the second identifier The third identifier of the server of the identified programmable device includes:

    The first VIM is configured to determine, according to the acceleration capacity and the processing capability information, a quantity of devices that need to load the programmable device of the first software, and select, from the managed server, the first information that includes the idle information. The first server of the number of programmable devices is not less than the number of the devices, and the first information corresponding to the number of devices is obtained from the programmable device managed by the first server in the second device library. Programming a second identification of the device and obtaining a third identification of the first server from the second library of devices.
19. The system according to any one of claims 15-17, wherein the service request further comprises a computing resource;

    The first VIM is configured to acquire, from the second device library, a second identifier of the programmable device that needs to load the first software according to the first information and the second information, and to manage the second identifier The third identifier of the server of the identified programmable device includes:

    The first VIM is configured to select, from the managed server, that the idle computing resource is not less than the computing resource, and the number of programmable devices corresponding to the idle first information is not less than that indicated by the second information. a first server of the number of programmable devices, wherein the number of programmable devices indicated by the second information is obtained from the programmable device managed by the first server in the second device library, and the first information corresponding to the first information is available Programming a second identification of the device and obtaining a third identification of the first server from the second library of devices.
20. A system according to any of claims 15-19, wherein the system further comprises a second VIM, wherein:

    The second VIM is configured to receive third information sent by the second server, establish a second device library including the third information and the identifier of the second server, and the third information and the first An identifier of the second server is sent to the NFVO, the third information includes a device type, a manufacturer, and an identifier of the second programmable device, and the second server is a server for managing the second programmable device, The second VIM is a VIM for managing the second server;

    The NFVO is further configured to receive the third information sent by the second VIM and the identifier of the second server, and according to the third information, the identifier of the second server, and the second VIM The identity identifies the first device library.
21. A system according to any one of claims 15 to 20, wherein the system further comprises a third VIM or catalog, wherein:

    The NFVO is further configured to receive a software package and send the software package to the third VIM or the directory, where the software package includes software function information, software version information, processing capability information, and fourth information, the fourth information. a device type and manufacturer including a programmable device capable of loading software corresponding to the software package;

    The third VIM or the directory library, configured to receive the software package sent by the NFVO, store the software package, and send a second storage link of the software package to the NFVO;

    The NFVO is further configured to receive the second storage link sent by the third VIM or the directory, and establish software function information and software version information included by the second storage link and the software package. A software information base for processing capability information and fourth information.
22. A virtualized infrastructure manager VIM, comprising:

    a communication unit, configured to receive, by the network function, a service request that includes an acceleration type and an acceleration capacity sent by the NFVO;

    a determining unit, configured to determine, according to an acceleration type and a software information library received by the communication unit, a first storage link of the first software having the acceleration type, processing capability information of the first software, and being capable of loading the first First information of the programmable device of the software, the first information including the device type and the manufacturer;

    An acquiring unit, configured to acquire, according to the first information determined by the determining unit, the processing capability information determined by the determining unit, and the acceleration capacity received by the communication unit, from the device library, to be programmable, that the first software needs to be loaded and idle a first identification of the device and a second identification of a server for managing the programmable device identified by the first identification;

    The communication unit is further configured to send the first storage link determined by the determining unit and the first identifier acquired by the acquiring unit to the first server identified by the second identifier acquired by the acquiring unit, where the a storage link for causing the first server to download a data packet of the first software from the first storage link, the first identifier being used to cause the first server to load the data packet in the The first identification is identified on the programmable device.
23. The VIM according to claim 22, wherein the determining unit is specifically configured to:

    Acquiring, from a software information repository, a first storage link of the first software having the acceleration type, processing capability information of the first software, and first information of a programmable device capable of loading the first software; or

    Obtaining a device type and a manufacturer of the first programmable device from the device library, and obtaining, according to the device type of the first programmable device, and the manufacturer, the software that can be loaded by the first programmable device from the software information library a software function, when the software function includes the acceleration type, determining that software corresponding to the software function is first software, the first programmable device is a programmable device capable of loading the first software, and The device type and manufacturer of the first programmable device are first information, and the first storage link and processing capability information of the first software is obtained from the software information library, the first programmable device is the Any free programmable device in the first device bank.
24. The VIM according to claim 22 or 23, wherein the service request further comprises a computing resource;

    The obtaining unit is specifically configured to:

    Determining, according to the acceleration capacity and the processing capability information, a number of devices of the programmable device that need to load the first software, and selecting, from the managed server, that the idle computing resource is not less than the computing resource and including the idle a first server in which the number of programmable devices corresponding to the information is not less than the number of the devices, and the first information corresponding to the number of the devices is obtained from the programmable device managed by the first server in the device library. A first identification of the programmable device and obtaining a second identification of the first server from the library of devices.
25. The VIM according to any one of claims 22 to 24, wherein the communication unit is further configured to receive second information sent by the second server, where the second information includes a device type of the second programmable device. a manufacturer and an identifier, the second server being a server managed by the VIM and configured to manage the second programmable device;

    The VIM also includes:

    And a first establishing unit, configured to establish a device library including the second information received by the communication unit and the identifier of the second server.
26. The VIM according to any one of claims 22-25, wherein the communication unit is further configured to receive a software package and send the software package to the directory library, so that the directory library stores the software package and returns the a second storage link of the software package, the software package including software function information, software version information, processing capability information, and third information, the third information including a device type of a programmable device capable of loading the software package corresponding software And the manufacturer;

    The communication unit is further configured to receive the second storage link;

    The VIM also includes:

    And a second establishing unit, configured to establish a software information library including the second storage link and software function information, software version information, processing capability information, and third information included in the software package.

Images