Controller plug-in management method and device, storage medium
By designing the controller plug-in based on PSR layered decoupling, the problem of poor plug-in adaptation and reusability in the existing technology is solved, and efficient maintainability and rapid service activation of cloud network atomic services are achieved.
Patent Information
- Application Number
- CN202211110124.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-09-13
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2042-09-13
AI Technical Summary
The tiled adaptation of controller plug-ins in the existing business activation makes it difficult to reuse product information, customer information and order information, affects the efficiency of business activation, and is difficult to completely decouple from application scenarios.
Using a PSR layered decoupling method to design controller plug-ins, register the first type of plug-ins, second type of plug-ins and third type of plug-ins to the plug-in design management framework module through plug-in editor, compiler and register to realize the plug-in's Flexible combination and device adaptation, and functional configuration using RESTCONF and NETCONF protocols.
It improves the reusability and maintainability of cloud network atomic services, simplifies the business activation process, is suitable for a variety of front-end products, and improves the business activation efficiency.
Smart Images

Figure CN115357307B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of network technology, and in particular to a controller plug-in management method and device, and a storage medium. Background Art
[0002] The new generation of cloud network operation systems needs to achieve the goal of decoupling network services, so as to realize the standardized opening of operators' cloud network resource service capabilities. As the foundation of the new generation of cloud network operation systems, SDN (Software Defined Network) collaborative controllers need to support the standardized encapsulation of cloud network atomic service capabilities, so as to have the ability to flexibly orchestrate and intelligently schedule cloud network resources. The controller plug-ins involved in the existing service activation are generally adapted in a flat-type plug-in manner. Summary of the invention
[0003] The inventor noticed that in the related art, the controller plug-in involved in the service activation generally performs flat-type plug-in adaptation, which may contain more product information, customer information, order information, etc., which is not conducive to improving the reusability of atomic service capabilities and is difficult to achieve full decoupling from the application scenario. When the product information on the front end changes, the controller plug-in needs to be adjusted synchronously, affecting the efficiency of service activation.
[0004] Based on this, the present disclosure provides a controller plug-in management solution, which manages the SDN collaborative controller plug-in by adopting a PSR (Product-Service-Resource) (layered decoupling) method, so that the cloud network atomic service capabilities have good reusability and maintainability.
[0005] According to a first aspect of an embodiment of the present disclosure, a controller plug-in management method is provided, comprising: using a plug-in editor to design a first type of plug-in, a second type of plug-in, and a third type of plug-in, wherein the first type of plug-in belongs to a customer-oriented service CFS service level, the second type of plug-in belongs to a resource-oriented service RFS function level, and the third type of plug-in belongs to a resource RES instruction level; using a plug-in compiler to compile the first type of plug-in, the second type of plug-in, and the third type of plug-in to generate a plug-in code file; a plug-in registrar uses the plug-in code file to register the first type of plug-in, the second type of plug-in, and the third type of plug-in to a plug-in design management framework module; the plug-in design management framework module stores the first type of plug-in, the second type of plug-in, and the third type of plug-in, and performs device adaptation for the first type of plug-in, the second type of plug-in, and the third type of plug-in.
[0006] In some embodiments, the first type of plug-in is used to call the second type of plug-in to complete the activation or operation and maintenance of the service according to the network scenario; the second type of plug-in is used to call the third type of plug-in to complete the activation or operation and maintenance of a specified functional module in a specified device; the third type of plug-in is used to complete the activation or operation and maintenance of a specified functional point in a specified functional module.
[0007] In some embodiments, designing a first type of plug-in using a plug-in editor includes: using a plug-in design management framework module to select a second type of plug-in or a third type of plug-in from existing plug-ins as a plug-in to be processed; orderly combining the plug-ins to be processed, and adding corresponding functions as needed to generate a first type of plug-in.
[0008] In some embodiments, designing the second type of plug-in using the plug-in editor includes: using the plug-in design management framework to select the third type of plug-in from the existing plug-ins as the plug-in to be processed; orderly combining the plug-ins to be processed, and adding corresponding functions as needed to generate the second type of plug-in.
[0009] In some embodiments, the plugin registrar exports Representational State Transfer Configuration Protocol RESTCONF resources.
[0010] In some embodiments, the RESTCONF protocol framework module determines to call the corresponding first-class plug-in, second-class plug-in or third-class plug-in based on the configuration request sent by the user and the RESTCONF resource, and sends the corresponding plug-in call request to the plug-in instance verification module; the plug-in instance verification module performs data consistency verification on the plug-in call request, and if the verification is successful, sends the plug-in call request to the plug-in loading management framework module; the plug-in loading management framework module queries the plug-in that matches the plug-in call request, and loads the plug-in instance for the queried plug-in; the plug-in instance encoding module encodes the plug-in instance into network configuration protocol NETCONF request data; the NETCONF protocol framework module completes the interaction with the device according to the NETCONF request data to realize the configuration of the specified function.
[0011] In some embodiments, the plug-in loading management framework module performs plug-in instance loading on the queried plug-in, including: if the queried plug-in is a first-category plug-in or a second-category plug-in, all sub-plug-ins contained in the queried plug-in are instantiated through recursive processing to complete the plug-in instance loading of the queried plug-in.
[0012] According to a second aspect of an embodiment of the present disclosure, a controller plug-in management device is provided, comprising: a plug-in editor, configured to design a first type of plug-in, a second type of plug-in and a third type of plug-in, wherein the first type of plug-in belongs to a customer-oriented service CFS service level, the second type of plug-in belongs to a resource-oriented service RFS function level, and the third type of plug-in belongs to a resource RES instruction level; a plug-in compiler, configured to compile the first type of plug-in, the second type of plug-in and the third type of plug-in to generate a plug-in code file; a plug-in registrar, configured to register the first type of plug-in, the second type of plug-in and the third type of plug-in to a plug-in design management framework module using the plug-in code file; and a plug-in design management framework module, configured to store the first type of plug-in, the second type of plug-in and the third type of plug-in, and perform device adaptation for the first type of plug-in, the second type of plug-in and the third type of plug-in.
[0013] In some embodiments, the first type of plug-in is used to call the second type of plug-in to complete the activation or operation and maintenance of the service according to the network scenario; the second type of plug-in is used to call the third type of plug-in to complete the activation or operation and maintenance of a specified functional module in a specified device; the third type of plug-in is used to complete the activation or operation and maintenance of a specified functional point in a specified functional module.
[0014] In some embodiments, the plug-in editor is configured to utilize a plug-in design management framework module to select a second-class plug-in or a third-class plug-in from existing plug-ins as a plug-in to be processed, orderly combine the plug-ins to be processed, and add corresponding functions as needed to generate a first-class plug-in.
[0015] In some embodiments, the plug-in editor is configured to utilize a plug-in design management framework to select a third type of plug-in from existing plug-ins as a plug-in to be processed, orderly combine the plug-ins to be processed, and add corresponding functions as needed to generate a second type of plug-in.
[0016] In some embodiments, the plugin registrar is configured to export Representational State Transfer Configuration Protocol RESTCONF resources.
[0017] In some embodiments, the above-mentioned device also includes: a RESTCONF protocol framework module, which is configured to determine to call the corresponding first-class plug-in, second-class plug-in or third-class plug-in based on the configuration request sent by the user and the RESTCONF resource, and send the corresponding plug-in call request to the plug-in instance verification module; the plug-in instance verification module is configured to perform data consistency verification on the plug-in call request, and if the verification is successful, send the plug-in call request to the plug-in loading management framework module; the plug-in loading management framework module is configured to query the plug-in that matches the plug-in call request and load the plug-in instance for the queried plug-in; the plug-in instance encoding module is configured to encode the plug-in instance into network configuration protocol NETCONF request data; the NETCONF protocol framework module is configured to complete the interaction with the device according to the NETCONF request data to realize the configuration of the specified function.
[0018] In some embodiments, the plug-in loading management framework module is configured to instantiate all sub-plug-ins contained in the queried plug-in through recursive processing if the queried plug-in is a first-category plug-in or a second-category plug-in, so as to complete the plug-in instance loading of the queried plug-in.
[0019] According to a third aspect of an embodiment of the present disclosure, a controller plug-in management device is provided, comprising: a memory configured to store instructions; a processor coupled to the memory, the processor being configured to execute a method as described in any of the above embodiments based on the instructions stored in the memory.
[0020] According to a fourth aspect of an embodiment of the present disclosure, a non-volatile computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the method described in any of the above embodiments is implemented.
[0021] Other features and advantages of the present disclosure will become apparent from the following detailed description of exemplary embodiments of the present disclosure with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.
[0023] Figure 1 A flowchart of a controller plug-in management method according to an embodiment of the present disclosure;
[0024] Figure 2A schematic diagram of a PSR model according to an embodiment of the present disclosure;
[0025] Figure 3 A flowchart of a controller plug-in management method according to another embodiment of the present disclosure;
[0026] Figure 4 A schematic diagram of the structure of a controller plug-in management device according to an embodiment of the present disclosure;
[0027] Figure 5 A schematic diagram of the structure of a controller plug-in management device according to another embodiment of the present disclosure;
[0028] Figure 6 A schematic diagram of the structure of a controller plug-in management device according to another embodiment of the present disclosure;
[0029] Figure 7 A schematic diagram of a plug-in control framework according to an embodiment of the present disclosure;
[0030] Figure 8 A schematic diagram of creating a plug-in design for an MPLS L3VPN according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0031] The following will be combined with the drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all of the embodiments. The following description of at least one exemplary embodiment is actually only illustrative and is by no means intended to limit the present disclosure and its application or use. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.
[0032] Unless specifically stated otherwise, the relative arrangement of components and steps, the numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present disclosure.
[0033] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.
[0034] Technologies, methods, and apparatus known to ordinary technicians in the relevant field may not be discussed in detail, but where appropriate, such technologies, methods, and apparatus should be considered part of the authorization specification.
[0035] In all examples shown and discussed herein, any specific values should be interpreted as merely exemplary and not as limiting. Therefore, other examples of the exemplary embodiments may have different values.
[0036] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.
[0037] Figure 1 The following is a flow chart of a controller plug-in management method according to an embodiment of the present disclosure. In some embodiments, the following controller plug-in management method is executed by a controller plug-in management device.
[0038] In step 101, a first type of plug-in, a second type of plug-in, and a third type of plug-in are designed using a plug-in editor.
[0039] For example, Figure 2 As shown, the PSR model includes:
[0040] ■CFS (Customer Facing Services): End-to-end network communication capabilities that are perceived by customers;
[0041] ■RFS (Resource Facing Services): The communication capabilities provided by various professional communication networks can be assembled into customer-oriented services and provided externally;
[0042] ■RES (Resource): Cloud network infrastructure, RFS completes assembly by operating or scheduling resources.
[0043] In some embodiments, the first type of plug-in, the second type of plug-in, and the third type of plug-in are as follows:
[0044] ■The first type of plug-in belongs to the CFS service level and is used to call the second type of plug-in to complete the service provisioning or operation and maintenance according to the network scenario;
[0045] ■The second type of plug-in belongs to the RFS function level and is used to call the third type of plug-in to complete the activation or operation and maintenance of the specified functional module in the specified device;
[0046] ■The third type of plug-in belongs to the RES instruction level and is used to complete the activation or operation and maintenance of specified function points in specified function modules.
[0047] In some embodiments, for the first type of plug-in or the second type of plug-in, a plug-in design management framework module can be used to select plug-ins of corresponding categories from existing plug-ins for orderly combination, and add functions as needed to complete the design.
[0048] For example, for the first type of plug-in, the plug-in design management framework module is used to select the second type of plug-in or the third type of plug-in from the existing plug-ins as the plug-ins to be processed, the plug-ins to be processed are combined in order, and corresponding functions are added as needed to generate the first type of plug-in.
[0049] For another example, for the second type of plug-in, the plug-in design management framework is used to select the third type of plug-in from the existing plug-ins as the plug-in to be processed, the plug-ins to be processed are combined in order, and corresponding functions are added as needed to generate the second type of plug-in.
[0050] In step 102, the first type of plug-in, the second type of plug-in and the third type of plug-in are compiled using a plug-in compiler to generate a plug-in code file.
[0051] In step 103, the plug-in registrar registers the first type of plug-in, the second type of plug-in and the third type of plug-in into the plug-in design management framework module using the plug-in code file.
[0052] In some embodiments, the plugin registrar exports Representational State Transfer Configuration Protocol (RESTCONF) resources.
[0053] In step 104, the plug-in design management framework module stores the first type of plug-ins, the second type of plug-ins, and the third type of plug-ins, and performs device adaptation for the first type of plug-ins, the second type of plug-ins, and the third type of plug-ins.
[0054] The controller plug-in management method provided in the above embodiment of the present disclosure manages the SDN collaborative controller plug-in by adopting a PSR-based hierarchical decoupling method, so that the cloud network atomic service capability has good reusability and maintainability.
[0055] Figure 3 The following is a flowchart of a controller plug-in management method according to another embodiment of the present disclosure. In some embodiments, the following controller plug-in management method is executed by a controller plug-in management device.
[0056] In step 301, the RESTCONF protocol framework module determines to call the corresponding first-class plug-in, second-class plug-in or third-class plug-in based on the configuration request sent by the user and the RESTCONF resource exported by the plug-in registrar, and sends a corresponding plug-in call request to the plug-in instance verification module to configure the specified function of the device.
[0057] In step 302, the plug-in instance verification module performs data consistency verification on the plug-in call request, and if the verification succeeds, the plug-in call request is sent to the plug-in loading management framework module.
[0058] In some embodiments, if the verification fails, the plug-in instance verification module sends an error message and ends the process.
[0059] In step 303, the plug-in loading management framework module searches for a plug-in that matches the plug-in calling request, and loads a plug-in instance for the searched plug-in.
[0060] In some embodiments, if the queried plug-in is a first-category plug-in or a second-category plug-in, all sub-plug-ins included in the queried plug-in are instantiated through recursive processing to complete plug-in instance loading for the queried plug-in.
[0061] In step 304, the plug-in instance encoding module encodes the plug-in instance into NETCONF (Network Configuration Protocol) request data.
[0062] In step 305, the NETCONF protocol framework module completes the interaction with the device according to the NETCONF request data to implement the configuration of the specified function.
[0063] Figure 4 FIG. 1 is a schematic diagram of the structure of a controller plug-in management device according to an embodiment of the present disclosure. Figure 4 As shown, the controller plug-in management device includes a plug-in editor 41, a plug-in compiler 42, a plug-in registrar 43 and a plug-in design management framework module 44.
[0064] The plug-in editor 41 is configured to design a first type plug-in, a second type plug-in, and a third type plug-in.
[0065] In some embodiments, the first type of plug-in, the second type of plug-in, and the third type of plug-in are as follows:
[0066] ■The first type of plug-in belongs to the CFS service level and is used to call the second type of plug-in to complete the service provisioning or operation and maintenance according to the network scenario;
[0067] ■The second type of plug-in belongs to the RFS function level and is used to call the third type of plug-in to complete the activation or operation and maintenance of the specified functional module in the specified device;
[0068] ■The third type of plug-in belongs to the RES instruction level and is used to complete the activation or operation and maintenance of specified function points in specified function modules.
[0069] In some embodiments, the plug-in editor 41 can utilize the plug-in design management framework module for the first type of plug-ins or the second type of plug-ins, select plug-ins of corresponding categories from existing plug-ins for orderly combination, and add functions as needed to complete the design.
[0070] For example, the plug-in editor 41 uses the plug-in design management framework module for the first type of plug-in, selects the second type of plug-in or the third type of plug-in from the existing plug-ins as the plug-ins to be processed, combines the plug-ins to be processed in an orderly manner, and adds corresponding functions as needed to generate the first type of plug-in.
[0071] For another example, the plug-in editor 41 uses the plug-in design management framework for the second type of plug-ins, selects the third type of plug-ins from the existing plug-ins as the plug-ins to be processed, combines the plug-ins to be processed in an orderly manner, and adds corresponding functions as needed to generate the second type of plug-ins.
[0072] The plug-in compiler 42 is configured to compile the first type of plug-in, the second type of plug-in, and the third type of plug-in to generate plug-in code files.
[0073] The plug-in registrar 43 is configured to register the first type of plug-in, the second type of plug-in and the third type of plug-in into the plug-in design management framework module using the plug-in code file.
[0074] In some embodiments, plugin registrar 43 is also configured to export RESTCONF resources.
[0075] The plug-in design management framework module 44 is configured to store the first type of plug-ins, the second type of plug-ins and the third type of plug-ins, and perform device adaptation for the first type of plug-ins, the second type of plug-ins and the third type of plug-ins.
[0076] Figure 5 FIG. 1 is a schematic diagram of the structure of a controller plug-in management device according to another embodiment of the present disclosure. Figure 5 As shown, the controller plug-in management device includes a RESTCONF protocol framework module 51, a plug-in instance verification module 52, a plug-in loading management framework module 53, a plug-in instance encoding module 54 and a NETCONF protocol framework module 55.
[0077] The RESTCONF protocol framework module 51 is configured to determine to call the corresponding first-class plug-in, second-class plug-in or third-class plug-in according to the RESTCONF resource based on the configuration request sent by the user, and send the corresponding plug-in call request to the plug-in instance verification module 52.
[0078] The plug-in instance verification module 52 is configured to perform data consistency verification on the plug-in call request, and if the verification succeeds, the plug-in call request is sent to the plug-in loading management framework module 53 .
[0079] The plug-in loading management framework module 53 is configured to query a plug-in that matches the plug-in calling request, and load a plug-in instance for the queried plug-in.
[0080] In some embodiments, the plug-in loading management framework module 53 is configured to instantiate all sub-plug-ins contained in the queried plug-in through recursive processing if the queried plug-in is a first-category plug-in or a second-category plug-in, so as to complete the plug-in instance loading of the queried plug-in.
[0081] The plug-in instance encoding module 54 is configured to encode the plug-in instance into NETCONF request data.
[0082] The NETCONF protocol framework module 55 is configured to complete interaction with the device according to the NETCONF request data to implement configuration of the specified function.
[0083] Figure 6 FIG. 1 is a schematic diagram of the structure of a controller plug-in management device according to another embodiment of the present disclosure. Figure 6 As shown, the controller plug-in management device includes a memory 61 and a processor 62 .
[0084] The memory 61 is used to store instructions. The processor 62 is coupled to the memory 61. The processor 62 is configured to execute the instructions stored in the memory to implement the following. Figure 1 , 3 The method of any one of the embodiments.
[0085] like Figure 6 As shown, the controller plug-in management device also includes a communication interface 63 for information exchange with other devices. At the same time, the controller plug-in management device also includes a bus 64, through which the processor 62, the communication interface 63, and the memory 61 communicate with each other.
[0086] The memory 61 may include a high-speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory. The memory 61 may also be a memory array. The memory 61 may also be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules.
[0087] In addition, the processor 62 may be a central processing unit (CPU), or may be an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present disclosure.
[0088] The present disclosure also relates to a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, which are executed by a processor to implement the following Figure 1 , 3 The method of any one of the embodiments.
[0089] Figure 7 FIG. 1 is a schematic diagram of a plug-in control framework according to an embodiment of the present disclosure. Figure 7 The framework shown adopts a PSR-based layered decoupling method to design and load SDN collaborative controller plug-ins, making the cloud network atomic service capabilities have good reusability and maintainability.
[0090] Figure 8A schematic diagram of a plug-in design is created for an MPLS (Multi-Protocol Label Switching) L3VPN (Layer 3 Virtual Private Network) according to an embodiment of the present disclosure.
[0091] exist Figure 8 In the example, the first row represents the first type of plug-in, the second row represents the second type of plug-in, and the third row represents the third type of plug-in. The MPLS L3VPN creation plug-in includes an interface creation plug-in, a QoS (Quality of Service) creation plug-in, a VPN-Instance (instance) creation plug-in, a BGP (Border Gateway Protocol) creation plug-in, and a Routing (routing) creation plug-in, wherein the QoS creation plug-in includes a QoS-Profile creation plug-in, a QoS-Policy creation plug-in, and a QoS-Apply creation plug-in, and the BGP creation plug-in includes a BGP-Instance creation plug-in.
[0092] By implementing the above embodiments of the present disclosure, the following beneficial effects can be obtained:
[0093] 1) As the foundation of the new generation of cloud network operation system, SDN collaborative controller needs to support the standardized encapsulation of cloud network atomic service capabilities. This paper designs the SDN collaborative controller plug-in based on the PSR model, so that the cloud network atomic service capabilities have good reusability and maintainability.
[0094] 2) In view of the problems of poor reusability, complex maintenance, and difficulty in achieving full decoupling from application scenarios in controller plug-ins used in existing business activation, the present invention constructs a plug-in control framework based on layered decoupled plug-ins, which can be applied to a variety of front-end products and help to quickly activate services.
[0095] In some embodiments, the functional unit described above can be implemented as a general-purpose processor, a programmable logic controller (PLC), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component or any appropriate combination thereof for performing the functions described in the present disclosure.
[0096] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.
[0097] The description of the present disclosure is given for the purpose of illustration and description, and is not intended to be exhaustive or to limit the present disclosure to the disclosed form. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiments are selected and described in order to better illustrate the principles and practical applications of the present disclosure, and to enable those of ordinary skill in the art to understand the present disclosure and thereby design various embodiments with various modifications suitable for specific uses.
Claims
1. A controller plug-in management method, comprising: Designing a first type of plug-in, a second type of plug-in and a third type of plug-in by using a plug-in editor, wherein the first type of plug-in belongs to a customer-oriented service CFS service level, the second type of plug-in belongs to a resource-oriented service RFS function level, and the third type of plug-in belongs to a resource RES instruction level; Compiling the first type of plug-in, the second type of plug-in and the third type of plug-in using a plug-in compiler to generate a plug-in code file; The plug-in registrar registers the first type of plug-in, the second type of plug-in and the third type of plug-in into the plug-in design management framework module by using the plug-in code file; The plug-in design management framework module stores the first type of plug-ins, the second type of plug-ins and the third type of plug-ins, and performs device adaptation for the first type of plug-ins, the second type of plug-ins and the third type of plug-ins; The plugin registrar exports the Representation State Transfer Configuration Protocol RESTCONF resources; The RESTCONF protocol framework module determines to call the corresponding first-class plug-in, second-class plug-in or third-class plug-in according to the RESTCONF resource based on the configuration request sent by the user, and sends the corresponding plug-in call request to the plug-in instance verification module; The plug-in instance verification module performs data consistency verification on the plug-in call request, and if the verification succeeds, sends the plug-in call request to the plug-in loading management framework module; The plug-in loading management framework module queries for a plug-in that matches the plug-in call request, and performs plug-in instance loading on the queried plug-in, wherein if the queried plug-in is a first-category plug-in or a second-category plug-in, all sub-plug-ins contained in the queried plug-in are instantiated through recursive processing, so as to complete the plug-in instance loading of the queried plug-in; The plug-in instance encoding module encodes the plug-in instance into network configuration protocol NETCONF request data; The NETCONF protocol framework module completes the interaction with the device according to the NETCONF request data to implement the configuration of the specified function.
2. The method according to claim 1, wherein: The first type of plug-in is used to call the second type of plug-in to complete the opening or operation and maintenance of the service according to the network scenario; The second type of plug-in is used to call the third type of plug-in to complete the activation or operation and maintenance of a specified functional module in a specified device; The third type of plug-in is used to complete the activation or operation and maintenance of specified function points in specified function modules.
3. The method according to claim 1, wherein: The first type of plugins designed using the plugin editor include: Using the plug-in design management framework module, select the second type of plug-in or the third type of plug-in from the existing plug-ins as the plug-in to be processed; The to-be-processed plug-ins are combined in order, and corresponding functions are added as required to generate a first type of plug-in.
4. The method according to claim 1, wherein: The second type of plug-in designed using the plug-in editor includes: By utilizing the plug-in design management framework, a third type of plug-in is selected from existing plug-ins as a plug-in to be processed; The to-be-processed plug-ins are combined in order, and corresponding functions are added as required to generate a second type of plug-in.
5. A controller plug-in management device, comprising: A plug-in editor is configured to design a first type of plug-in, a second type of plug-in and a third type of plug-in, wherein the first type of plug-in belongs to the customer-oriented service CFS service level, the second type of plug-in belongs to the resource-oriented service RFS function level, and the third type of plug-in belongs to the resource RES instruction level; A plug-in compiler is configured to compile the first type of plug-ins, the second type of plug-ins and the third type of plug-ins to generate plug-in code files; A plug-in registrar is configured to register the first type of plug-in, the second type of plug-in and the third type of plug-in into the plug-in design management framework module by using the plug-in code file, and is also configured to export a Representation State Transfer Configuration Protocol RESTCONF resource; A plug-in design management framework module is configured to store the first type of plug-ins, the second type of plug-ins and the third type of plug-ins, and perform device adaptation for the first type of plug-ins, the second type of plug-ins and the third type of plug-ins; The RESTCONF protocol framework module is configured to determine, based on the configuration request sent by the user, to call the corresponding first-class plug-in, second-class plug-in or third-class plug-in according to the RESTCONF resource, and send a corresponding plug-in call request to the plug-in instance verification module; A plug-in instance verification module is configured to perform data consistency verification on the plug-in call request, and if the verification succeeds, send the plug-in call request to the plug-in loading management framework module; A plug-in loading management framework module is configured to query a plug-in matching the plug-in call request and load a plug-in instance for the queried plug-in, wherein if the queried plug-in is a first-category plug-in or a second-category plug-in, all sub-plug-ins contained in the queried plug-in are instantiated through recursive processing to complete the plug-in instance loading for the queried plug-in; A plug-in instance encoding module, configured to encode the plug-in instance into network configuration protocol NETCONF request data; The NETCONF protocol framework module is configured to complete interaction with the device according to the NETCONF request data to implement configuration of the specified function.
6. The device according to claim 5, wherein: The first type of plug-in is used to call the second type of plug-in to complete the opening or operation and maintenance of the service according to the network scenario; The second type of plug-in is used to call the third type of plug-in to complete the activation or operation and maintenance of a specified functional module in a specified device; The third type of plug-in is used to complete the activation or operation and maintenance of specified function points in specified function modules.
7. The device according to claim 5, wherein: The plug-in editor is configured to utilize the plug-in design management framework module to select the second type plug-in or the third type plug-in from the existing plug-ins as the plug-ins to be processed, orderly combine the plug-ins to be processed, and add corresponding functions as needed to generate the first type plug-in.
8. The device according to claim 5, wherein: The plug-in editor is configured to utilize the plug-in design management framework to select the third type of plug-ins from the existing plug-ins as the plug-ins to be processed, orderly combine the plug-ins to be processed, and add corresponding functions as needed to generate the second type of plug-ins.
9. A controller plug-in management device, comprising: a memory configured to store instructions; A processor is coupled to the memory, and the processor is configured to execute the method according to any one of claims 1 to 4 based on instructions stored in the memory.
10. A non-transitory computer-readable storage medium, wherein: The computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the method according to any one of claims 1 to 4 is implemented.
