TW202121869A - Management system and management method of vnf - Google Patents

Abstract

A management system and management method of VNF adapted for instantiating a VNF are provided. The management method includes: obtaining a VNF descriptor corresponding to the VNF form a business and operation support system (BOSS); obtaining an optional parameter from the VNF descriptor; feedbacking the optional parameter to the BOSS; receiving a generic heat orchestration template (HOT) and an user parameter corresponding to the optional parameter from the BOSS; updating, according to the user parameter and the VNF descriptor, the generic HOT to generate a HOT and VNF metadata corresponding to the VNF; and storing the HOT and the VNF metadata to complete onboarding of the VNF. Configurations of network/computing resources such as NUMA or a network card can be optimized according to to the VNF metadata to update the HOT of the VNF. Accordingly, the resource configuration of the VNF can be optimized and the performance of the VNF can be improved.

Description

Virtual network function management system and management method

This disclosure relates to a management system and management method, and in particular, to a management system and management method of a virtual network function (VNF).

At present, the existing technology often adopts the network function virtualization management and orchestration (NFV MANO) framework formulated by the European Telecommunications Standard Institute (ETSI) to implement the cloud management system. After the VNF is on the shelf, the NFV MANO framework can instantiate the VNF on the shelf in response to the customer's request, so that the customer can use the network resources related to the VNF.

However, VNF descriptors of different vendors cannot be shared, so VNFs of different vendors can only be put on the vendor's NFV MANO system. VNF service providers cannot support different brands/types of VNF services.

This disclosure provides a virtual network function management system and management method, which can generate VNF interpretation data and general installation templates after VNF descriptors of different vendors are put on the shelf, so that VNFs of different vendors can be applied to the NFV MANO system. In addition, this disclosure can optimize the configuration of network and computing resources such as non-uniform memory architecture (NUMA) or network cards through the content in the VNF metadata (metadata), and then re-assemble the area to generate this area. The VNF is provided with a template to enable the VNF to have a better resource classification and to improve the performance of the VNF.

The virtual network function management system disclosed in this disclosure is suitable for instantiating virtual network functions, including network function virtualization orchestrator (NFVO) general framework modules and virtual network function management (virtual network function management). function manager, VNFM) general framework module. NFVO general framework modules include: generic virtual network function manager (G-VNFM) northbound API interface module, G-VNFM shelf module, data storage module, interpretation data processing module, and G-VNFM VNFM instantiates the core module. The G-VNFM northbound API interface module obtains the VNF descriptor corresponding to the VNF from the telecom operation support system, where the VNF includes multiple virtual network function components (VNF components, VNFC). G-VNFM mounts the module, obtains the optional parameters in the VNF descriptor, sends the optional parameters back to the telecom operation support system, and receives the general installation template and user parameters corresponding to the optional parameters from the telecom operation support system, and According to the user parameters and the VNF descriptor, the general installation template is updated to generate the installation template corresponding to the VNF and the VNF interpretation data. The data storage module stores the installation template and VNF interpretation data to complete the VNF shelf. The interpretation data processing module generates the network resource configuration used to instantiate the VNF. G-VNFM instantiates the core module and instantiates the VNF. VNFM general framework modules, including: G-VNFM resource configuration module, G-VNFM instantiation template replacement module, and G-VNFM southbound general interface module. The G-VNFM resource configuration module selects network resources according to the network resource configuration. The G-VNFM instantiation template replacement module updates the installation template according to the network resource configuration. The G-VNFM southbound universal interface module communicates with at least one virtualized infrastructure manager (VIM), where the G-VNFM instantiated core module transmits data through the G-VNFM southbound universal interface module Install the template to at least one VIM to instantiate the VNF, so that multiple VNFCs are respectively configured to multiple virtual data centers managed by the at least one VIM.

In an embodiment of the present disclosure, the aforementioned NFVO general framework module further includes an interpretive data flow control module. The interpretation data process control module obtains at least one resource specification from the service specifications in the VNF interpretation data according to the order request corresponding to the VNF, wherein the interpretation data processing module generates the network resource configuration for instantiating the VNF according to the at least one resource specification , Where the G-VNFM instantiation core module instantiates the VNF in response to the order request.

In an embodiment of the present disclosure, the aforementioned VNFM general framework module further includes: a northbound API interface module and a G-VNFM resource configuration module. The northbound API interface module is coupled to the G-VNFM northbound API interface module, wherein the northbound API interface module receives network resource configuration from the G-VNFM northbound API interface module.

In an embodiment of the present disclosure, the aforementioned VMFM universal framework module further includes a second data storage module. The second data storage module receives the installation template and VNF interpretation data through the northbound API interface module, and stores the installation template and VNF interpretation data, so as to synchronize the NFVO general framework module and the VNFM general framework module.

In an embodiment of this disclosure, the aforementioned G-VNFM southbound universal interface module monitors at least one VIM to obtain a completion event message indicating that the instantiation of the VNF has been completed, wherein the northbound API interface module sends a completion event message to G- VNFM instantiates the core module.

In an embodiment of the present disclosure, the aforementioned G-VNFM instantiation core module instantiates the multiple virtual network function elements according to one of a user command, a resource pool state, and an application category.

In an embodiment of the present disclosure, the above-mentioned universal installation template corresponds to network functions virtualization infrastructure (NFVI), and the optional parameters correspond to the network environment of NFVI.

In an embodiment of the present disclosure, the aforementioned NFVO general framework module determines that the order request is valid according to the VNF has been put on the shelf.

In an embodiment of the present disclosure, the above-mentioned VNF descriptor includes at least one of the following: VNF type, VNF brand, protocol for installation template, and description of network function configuration.

A VNF management method disclosed in this disclosure is suitable for instantiating VNFs, including: obtaining a VNF descriptor corresponding to a VNF from a telecom operation support system, where the VNF includes multiple VNFCs; obtaining optional parameters in the VNF descriptor; giving feedback Optional parameters are sent to the telecom operation support system; the universal supply template and user parameters corresponding to the optional parameters are received from the telecom operation support system; the universal supply template is updated according to the user parameters and the VNF descriptor to generate the supply corresponding to the VNF Install the template and VNF interpretation data; store the install template and VNF interpretation data to complete the VNF shelf; generate the network resource configuration used to instantiate the VNF; select the network resource according to the network resource configuration; update according to the network resource configuration Provide the installation template; and send the installation template at least one VIM to instantiate the VNF, thereby respectively configuring the VNFC to multiple virtual data centers managed by the at least one VIM.

Based on the above, the virtual network function management system and management method disclosed in this disclosure provide a general VNF descriptor listing method, and provide a VNF orchestrator to instantiate the VNF by using the VNF metadata file. It requires a method of synchronizing network resource configuration information to the management system, integrating VNFs from different vendors through VNF interpretation data, flexibly interfacing with VNFs, and reducing the cost of customized development and information transmission.

FIG. 1 shows a schematic diagram of a VNF management system 10 according to an embodiment of the disclosure. The management system 10 includes an NFVO general framework module 13 and a VNFM general framework module 14. The NFVO general framework module 13 and the VNFM general framework module 14 are implemented by hardware/software, for example, but the disclosure is not limited thereto. For example, the NFVO general framework module 13 and the VNFM general framework module 14 can be implemented by a server with networking and computing capabilities.

The NFVO general framework module 13 includes an interpretive data flow control module 131, an interpretive data processing module 132, a data storage module 133, a G-VNFM northbound API interface module 134, a G-VNFM shelf module 135, and a G-VNFM instance The core module 136. The VNFM general framework module 14 includes a northbound API interface module 141, a G-VNFM instantiation template replacement module 142, a G-VNFM resource configuration module 143, a G-VNFM southbound general interface module 144, and a data storage module 145 .

FIG. 2 illustrates a schematic diagram of using the management system 10 to launch and instantiate the VNF 18 according to an embodiment of the present disclosure. The user 11 (or the manager of the management system 10) can use the telecommunication operation support system (business and operation support system) including the operations support system (OSS) and/or the business support system (BSS) 12 , BOSS) to launch and instantiate VNF 18. As shown in FIG. 2, the management system 10 of the present disclosure can be combined with OSS and/or BSS 12, VIM 15, NFVI 16 and element management system (element management system, EMS) 17 to compose the NFV MANO framework formulated by ETSI. VNF 18 is listed or instantiated. The management system 10 can communicate with OSS and/or BSS 12, VIM 15, EMS 170 and/or instantiated VNF 18 and exchange information. It is worth noting that OSS and/or BSS 12, VIM 15, NFVI 16 or EMS 17 can be implemented by servers with networking and computing capabilities, respectively, but the disclosure is not limited to this. In one embodiment, VIM 15 is, for example, an underlying management system established by an OpenStack open source project, and NFVI 16 is associated with different virtualization underlying technologies including VMware, vSphere/NSX, KVM, or Xen/XenServer.

Specifically, the user 11 can encode for NFVI 16 to generate a corresponding universal installation template, encode for VNF 18 to generate a corresponding VNF descriptor, and use the human machine interface (human machine interface) of OSS and/or BSS 12. interface (HMI) to send the VNF descriptor and the universal installation template to the G-VNFM northbound API interface module 134, where the VNF descriptor can include the VNF type, VNF brand, the agreement of the installation template (for example: TOSCA), and the network Information such as descriptions of road function configurations, but this disclosure is not limited to this.

After the G-VNFM northbound API interface module 134 obtains the VNF descriptor and the universal installation template, the G-VNFM shelf module 135 can obtain the VNF descriptor and the universal installation template from the G-VNFM northbound API interface module 134, and Analyze the VNF descriptor to obtain relevant information about optional parameters from the VNF descriptor. The optional parameters are related to the current network environment of NFVI 16, for example. For example, the optional parameters are the number of virtual local area networks (virtual local area network, VLAN) that can be used for NFVI 16, the number of VLANs that can be used for VNF 18, and the system pre-built resources that can be used for VIM 15 (including: network ID, etc.) or system assignment resources that can be used for VIM 15 (including: VLAN ID, subnet ID, etc.), which need to be filled in by the user 11 considering the current network environment of NFVI 16, but this disclosure does not Limited to this.

After obtaining the relevant information about the optional parameters, the G-VNFM shelf module 135 can give back the optional parameters to OSS and/or BSS 12, so that the user 11 can perform parameter configuration settings, data format or type selection, and generate User parameters corresponding to optional parameters. Then, the user 11 can send the user parameters to the G-VNFM northbound API interface module 134 through the OSS and/or the BSS 12. The G-VNFM shelf module 135 can obtain user parameters from the G-VNFM northbound API interface module 134, and update the general installation template corresponding to NFVI 16 according to the user parameters and the previously received VNF descriptor to generate a VNF corresponding to the VNF. 18 for the installation template (heat orchestration template, HOT) and VNF interpretation data. The data storage module 133 stores the installation template and VNF interpretation data corresponding to the VNF 18, and transmits the installation template and VNF interpretation data through the G-VNFM northbound API interface module 134 (for example, sending messages through Restful API) After the data storage module 145 of the VNFM universal framework module 14, the data storage module 145 can store the installation template and VNF interpretation data, so as to synchronize the NFVO universal framework module 13 and the VNFM universal framework module 14, thereby maintaining the universality of NFVO The data consistency of the framework module 13 and the VNFM general framework module 14 is completed and the VNF 18 is put on the shelf.

In one embodiment, the data storage module 133 and/or the data storage module 145 uses MariaDB as a relational database to store the installation template and the VNF interpretation data.

After the completion of VNF 18 on the shelves, customers can begin to apply for the services provided by VNF 18. The user 11 can send the order request corresponding to the VNF 18 to the NFVO general framework module 13 through the OSS and/or BSS 12 after the customer applies for the service of the VNF 18. In some embodiments, the order request can be associated with the VNF descriptor of the VNF 18 and the parameters required to instantiate the VNF 18 (for example, user parameters or network resource configuration, etc.), and the NFVO general framework module 13 can be based on the VNF 18 has been put on the shelf and it is judged that the order request sent by OSS and/or BSS 12 is valid.

The interpretation data flow control module 131 can access the supply template corresponding to the VNF 18 and the VNF interpretation data stored in the data storage module 133 in response to the order request. The interpretation data flow control module 131 can obtain relevant information corresponding to the service specification of the VNF 18 from the order request. The service specification may include information about one or more resource specifications. Therefore, the interpretive data flow control module 131 may further extract information related to one or more resource specifications from the service specification.

Then, the interpretation data processing module 132 can analyze the resource specifications to generate a network resource configuration for instantiating the network resources used by the VNF 18 according to the resource specifications. The G-VNFM northbound API interface module 134 can be coupled to the northbound API interface module 141 to transmit network resource configuration to the G-VNFM resource configuration module 143. The G-VNFM resource configuration module 143 can configure the network resources associated with the VNF 18 according to the network resource configuration (for example: VLAN, network port, IP configuration and/or spine-leaf switch architecture, etc.) and/or Hardware resources (for example: set dedicated CPU pinning, random access memory and/or standard huge pages for VNF 18, etc.). For example, the G-VNFM resource allocation module 143 can find from the existing network resources and/or hardware resources the network resources and/or hardware resources that meet the specifications recorded in the network resource configuration and can be used for the VNF 18 Physical resources.

On the other hand, the G-VNFM instantiation template replacement module 142 can update the supply of the VNF 18 according to the network resource configuration and the result of the G-VNFM resource configuration module 143 setting network resources and/or hardware resources. Template. In an embodiment, the G-VNFM instantiation template replacement module 142 may also update the provisioning template of the VNF 18 based on the use requirements according to the new VNF descriptor and/or the new user parameters. For example, the G-VNFM instantiation template replacement module 142 can give back optional parameters to the OSS and/or BSS 12, so that the user 11 can perform parameter configuration settings, data format or type selection, and generate corresponding optional parameters. The user parameter of the parameter. After updating the supply template of the VNF 18, the northbound API interface module 141 can send the updated supply template to the G-VNFM northbound API interface module 134 for use by the G-VNFM instantiated core module 136.

The G-VNFM instantiation core module 136 can instantiate the VNF 18 according to the installation template corresponding to the VNF 18 to satisfy the order request of the VNF 18. Specifically, the G-VNFM instantiation core module 136 can be connected to the G-VNFM southbound universal interface module 144 to transmit the installation template of the VNF 18 to the VIM 15 through the G-VNFM southbound universal interface module 144, so that The VIM 15 can instantiate the VNF 18 according to the installation template. The G-VNFM southbound general interface module 144 can monitor the VIM 15 to observe the instantiation and supply progress of the VNF 18. After the instantiation and supply of the VNF 18 are completed, the VIM 15 may send a completion event message indicating that the instantiation and supply of the VNF 18 have been completed to the G-VNFM southbound general interface module 144. Then, the northbound API interface module 141 can send the completion event message to the G-VNFM instantiation core module 136 to notify the G-VNFM instantiation core module 136 that the VNF 18 has been instantiated and installed. The G-VNFM instantiation core module 136 can send information about the VNF 18 to the G-VNFM instantiation template replacement module 142 through the G-VNFM northbound API interface module 134 to instruct the G-VNFM instantiation template replacement module 142 Carry out the life cycle management of VNF 18.

The VNF 18 may include multiple VNFCs. The G-VNFM instantiation core module 136 can instantiate multiple VNFCs of the VNF 18 in different ways. Specifically, the G-VNFM instantiation core module 136 can choose to instantiate part of the VNFC at the local end, and instantiate another part of the VNFC at the remote end (for example, the user end), so as to achieve multiple VNFC partitions for installation. , So as to maximize the execution efficiency of VNF 18. For example, the G-VNFM instantiation core module 136 can send the installation template of the VNF 18 to the VIM 15 through the G-VNFM southbound general interface module 144 to instantiate the VNF 18, thereby separating the multiple VNFCs of the VNF 18 It is configured to multiple virtual data centers (VDB) managed by VIM 15, so as to achieve multiple VNFC partitions for installation.

In an embodiment, the G-VNFM instantiation core module 136 may instantiate the multiple VNFCs according to the resource pool status or application category. For example, the G-VNFM instantiation core module 136 may choose to use network resources in a resource pool with a small load to instantiate VNFC, so as to avoid insufficient network resources when the VNF 18 is executed. For another example, the G-VNFM instantiation core module 136 can choose to use the same resource pool or network resources to instantiate VNFCs with similar attributes. The user can also actively decide how to instantiate multiple VNFCs of the VNF 18. For example, the G-VNFM instantiation core module 136 may receive a user command issued by the user, so as to instantiate the plurality of VNFCs according to the user command.

FIG. 3 shows a flowchart of a VNF management method according to an embodiment of the present disclosure, wherein the management method can be implemented by the management system 10 shown in FIG. 1. In step S301, a virtual network function descriptor corresponding to the virtual network function is obtained from the telecommunication operation support system. In step S302, the optional parameters in the virtual network function descriptor are obtained. In step S303, the optional parameters are given back to the telecom operation support system. In step S304, the universal installation template and user parameters corresponding to the optional parameters are received from the telecommunication operation support system. In step S305, the universal installation template is updated according to the user parameters and the virtual network function descriptor to generate the installation template corresponding to the virtual network function and the VNF interpretation data. In step S306, the installation template and VNF interpretation data are stored to complete the virtual network function.

FIG. 4 shows a flowchart of a method for instantiating a VNF according to an embodiment of the present disclosure, wherein the instantiation method may be implemented by the management system 10 shown in FIG. 1. In step S401, the order request corresponding to the VNF is transmitted to the NFVO general framework module through the OSS and/or BSS. In step S402, the related information corresponding to the service specification of the VNF is obtained from the order request, and the related information of one or more resource specifications is retrieved from the service specification. In step S403, the resource specifications are parsed to generate a network resource configuration for instantiating the network resources used by the VNF according to the resource specifications. In step S404, the VNF installation template is updated according to the network resource configuration and the setting result of the network resource and/or hardware resource. In step S405, the VNF is instantiated according to the installation template corresponding to the VNF, so that multiple VNFCs of the VNF are respectively configured to multiple virtual data centers managed by the VIM to satisfy the VNF order request and reach the VNFC partition For installation. In step S406, it is notified that the instantiation of the VNF has been completed, and the life cycle management of the VNF is performed.

In summary, the virtual network function management system and management method disclosed in this disclosure can be used to form a universal NFV MANO system, which can retain the advantages of the NFV MANO framework formulated by ETSI, and can enable a universal NFV MANO system The framework is automated. The VNF shelf method implemented by the NFVO general framework module of this disclosure can avoid the situation where the NFV MANO system needs to be customized according to different VNF vendors, and allows users to dynamically change the optional parameters in the VNF descriptor to adapt to different Network environment. This disclosure also provides a method for instantiating VNFs. The software is decoupled through the general NFVO general framework module and the VNFM general framework module so that it can receive independent supply order requests, so that the VNF service that the customer wants to apply for does not depend on OSS and/or BSS or customized orchestrator. This disclosure uses a common VNF descriptor to put the VNF on the shelf to manage VNF network resources/equipment of different brands, achieve the purpose of flexibly integrating the NFV MANO system, and provide NFV MANO system scalability.

10: Management system 11: User 12: Operation support system and/or business support system 13: Network function virtualization orchestrator general framework module 131: Interpretation data flow control module 132: Interpretation Data Processing Module 133, 145: Data storage module 134: General virtual network function management northbound API interface module 135: General virtual network function management shelf module 136: General virtual network function management instantiation core module 14: Virtual network function management general framework module 141: Northbound API interface module 142: General virtual network function management instantiation template replacement module 143: General virtual network function management resource configuration module 144: Universal virtual network function management southbound universal interface module 15: Virtualization Infrastructure Manager 16: Network function virtualization infrastructure 17: Component Management System 18: Virtual network function S301, S302, S303, S304, S305, S306, S401, S402, S403, S404, S405, S406: steps

Fig. 1 illustrates a schematic diagram of a VNF management system according to an embodiment of the disclosure. Fig. 2 illustrates a schematic diagram of using a management system to launch and instantiate a VNF according to an embodiment of the disclosure. FIG. 3 shows a flowchart of a method for managing VNF according to an embodiment of the disclosure. Fig. 4 shows a flow chart of instantiating a VNF according to an embodiment of the disclosure.

S301, S302, S303, S304, S305, S306: steps

Claims (10)

A management system for virtual network functions, suitable for instantiating virtual network functions, including: General framework modules of network function virtualization orchestrator, including: The general virtual network function management (G-VNFM) northbound API interface module obtains the virtual network function descriptor corresponding to the virtual network function from the telecom operation support system, wherein the virtual network function includes a plurality of virtual network functions. Network functional components; G-VNFM mounts the module, obtains the optional parameters in the virtual network function descriptor, feeds back the optional parameters to the telecom operation support system, receives the general installation template from the telecom operation support system, and Corresponding to the user parameters of the optional parameters, and update the universal installation template according to the user parameters and the virtual network function descriptor to generate the installation template corresponding to the virtual network function, and Virtual network function interpretation data; A data storage module that stores the installation template and the interpretation data of the virtual network function to complete the virtual network function's shelf; Interpret the data processing module to generate the network resource configuration used to instantiate the virtual network function; and G-VNFM instantiates the core module and instantiates the virtual network function; and General framework modules for virtual network function management, including: The G-VNFM resource configuration module selects network resources according to the network resource configuration; G-VNFM instantiates a template replacement module, and updates the installation template according to the network resource configuration; and The G-VNFM southbound universal interface module is communicatively connected to at least one virtualized infrastructure manager, wherein the G-VNFM instantiated core module transmits the provision for installation through the G-VNFM southbound universal interface module Template to the at least one virtualized infrastructure manager to instantiate the virtual network function, so that the multiple virtual network function elements are respectively configured to be managed by the at least one virtualized infrastructure manager Multiple virtual data centers. As the management system described in item 1 of the scope of patent application, the general framework module of the network function virtualization orchestrator further includes: The interpretation data flow control module obtains at least one resource specification from the service specifications in the virtual network function interpretation data according to the order request corresponding to the virtual network function, where The interpretation data processing module generates a network resource configuration for instantiating the virtual network function according to the at least one resource specification, wherein The G-VNFM instantiation core module instantiates the virtual network function in response to the order request. As the management system described in item 2 of the scope of patent application, the virtual network function management general framework module further includes: The northbound API interface module is coupled to the G-VNFM northbound API interface module, wherein the northbound API interface module receives the network resource configuration from the G-VNFM northbound API interface module. As the management system described in item 3 of the scope of patent application, the virtual network function management general framework module further includes: The second data storage module receives the installation template and the virtual network function interpretation data through the northbound API interface module, and stores the installation template and the virtual network function interpretation data for synchronization The general framework module of the network function virtualization orchestrator and the general framework module of the virtual network function management. The management system according to item 3 of the scope of patent application, wherein the G-VNFM southbound general interface module monitors the at least one virtualized infrastructure manager to obtain an indication that the virtual network function has been instantiated A completion event message, wherein the northbound API interface module transmits the completion event message to the G-VNFM instantiation core module. The management system according to the second item of the scope of patent application, wherein the G-VNFM instantiation core module instantiates the multiple virtual network function elements according to one of user commands, resource pool status, and application category. The management system according to item 1 of the scope of patent application, wherein the universal installation template corresponds to a network function virtualization infrastructure, and wherein the optional parameters correspond to the network function of the network function virtualization infrastructure surroundings. According to the management system described in item 2 of the scope of patent application, the general framework module of the network function virtualization orchestrator determines that the order request is valid according to the virtual network function has been put on the shelf. For example, the management system described in item 1 of the scope of patent application, wherein the virtual network function descriptor includes at least one of the following: the type of virtual network function, the brand of virtual network function, the agreement for the installation template, and the network Description of the configuration of the road function. A method for managing virtual network functions, suitable for instantiating virtual network functions, including: Obtaining a virtual network function descriptor corresponding to the virtual network function from the telecommunications operation support system, wherein the virtual network function includes a plurality of virtual network function elements; Obtaining optional parameters in the virtual network function descriptor; Feedback the optional parameters to the telecom operation support system; Receiving a universal installation template and user parameters corresponding to the optional parameters from the telecom operation support system; Updating the universal installation template according to the user parameters and the virtual network function descriptor to generate an installation template corresponding to the virtual network function and virtual network function interpretation data; Storing the installation template and the interpretation data of the virtual network function to complete the virtual network function on the shelf; Generating a network resource configuration for instantiating the virtual network function; Selecting network resources according to the network resource configuration; Update the installation template according to the network resource configuration; and Send the installation template to at least one virtualized infrastructure manager to instantiate the virtual network function, so that the plurality of virtual network function elements are respectively configured to the at least one virtualized infrastructure manager Multiple virtual data centers managed.

Images