Network equipment self-adaptive management method based on reference template and dynamic capability value

Abstract

The invention relates to a network equipment self-adaptive management method based on a reference template and a dynamic capability value, and the method is applied to the technical field of network management, and comprises the steps: obtaining the dynamic capability value after equipment is on line, matching a corresponding template in a reference function template library, carrying out the dynamic operation of the template according to the difference between the template and the dynamic capability value, and obtaining the dynamic capability value. According to the method, a global capability view is obtained to serve as a basis for generating a front-end equipment management interface, and the method covers the certainty of'pre-definition 'of a reference function template and the flexibility of'dynamic transmission'. The reference function template ensures the stability of the system architecture and the predictability of front-end rendering; and the dynamic capability value endows the system with the flexibility of coping with equipment diversity and function iteration. Through the method, real-time, dynamic and automatic adaptation of the network management front end to multiple types of equipment is realized, so that developers are liberated from endless adaptation work, the development and maintenance costs are remarkably reduced, and the agility of network management services is greatly improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of network management, in particular to a network device adaptive management method based on benchmark templates and dynamic capability values. BACKGROUND

[0002] Traditional network management systems usually need to develop special codes for each device model and even each device function point. However, in the current technical environment, it is difficult to adapt to the rapid innovation and dynamic expansion of network devices, resulting in a huge development, testing and maintenance burden. Therefore, the current technology has the problems of huge development workload and repetition, system rigidity and poor scalability. SUMMARY

[0003] In order to overcome the problems of large development workload and poor system scalability of the prior art, the present application provides a network device adaptive management method based on benchmark templates and dynamic capability values. The technical method of the present application is as follows: A network device adaptive management method based on benchmark templates and dynamic capability values, comprising the following steps: 1.1: After the device is online, the dynamic capability value of the device is obtained; 1.2: According to the dynamic capability value of the device, the preset benchmark function template library is matched to obtain the benchmark function template corresponding to the device type of the device; 1.3: According to the dynamic capability value of the device and the benchmark function template, comparison is performed; 1.4: According to the comparison result, the benchmark function template is dynamically operated to obtain a global capability view.

[0004] In some embodiments, the benchmark function template library includes a benchmark function template corresponding to each device type, and the benchmark function template corresponding to each device type includes a declaration of all function modules that the device type may support and default parameters or default states of each capability in each function module. In some embodiments, the dynamic capability value includes a device type, a function module actually supported by a current device, and a first object, wherein the first object covers or supplements the default parameters or default states of each capability in a first function module in the benchmark function template, and the first function module is part of the function modules in the benchmark function template.

[0005] In some embodiments, the benchmark function template matching includes: According to the device type, the benchmark function template corresponding to the current device is matched from the benchmark function template library.

[0006] In some embodiments, the comparing the dynamic capability value of the device with the benchmark function template comprises: comparing the actually supported function modules in the dynamic capability value of the device with all the possibly supported function modules in the benchmark function template; finding the function modules in the benchmark function template that are different from the actually supported function modules in the dynamic capability value of the device, as the first comparison result; finding the function modules in the benchmark function template that are the same as the actually supported function modules in the dynamic capability value of the device, as the second comparison result.

[0007] In some embodiments, the dynamic operation comprises: deleting the first comparison result from the benchmark function template; covering the default parameters or default states of the second comparison result with the first object in the dynamic capability value of the device, to obtain the global capability view.

[0008] In some embodiments, the comparing the dynamic capability value of the device with the benchmark function template further comprises: finding the function modules in the actually supported function modules in the dynamic capability value of the device that are different from all the possibly supported function modules in the benchmark function template, as the third comparison result.

[0009] In some embodiments, the dynamic operation further comprises: adding the third comparison result to the benchmark function template.

[0010] In some embodiments, the benchmark function template further comprises rules for mapping front-end page components or routes.

[0011] In some embodiments, after obtaining the global capability view, the method further comprises the following steps: performing front-end rendering on the global capability view according to the mapping rules of the benchmark function template, to obtain the customized device management interface.

[0012] Compared with the prior art, the technical scheme of the present application has the following beneficial effects: The network management system's adaptation to new devices and functions has been shortened from a lengthy "development-testing-release" cycle to a simple "define capability values-instant effect" configuration operation, greatly reducing development and maintenance costs. This invention uses a defined "baseline function template" to ensure architectural stability and "dynamic capability values" to provide flexibility, allowing the system to easily cope with a massive number of device models and frequent function iterations, exhibiting extremely high scalability. Furthermore, it interacts with dynamically generated global capability views, allowing for customized global capability views to be generated for each different device, thus improving system development efficiency. Attached Figure Description

[0013] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is a flowchart illustrating the steps of a network device adaptive management method based on a baseline template and dynamic capability values, as provided in an embodiment of this application.

[0015] Figure 2 This document provides a flowchart illustrating the specific operation of a network device adaptive management method based on a baseline template and dynamic capability values, as illustrated in an embodiment of this application. Detailed Implementation

[0016] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. It should be noted that the terms "first," "second," etc., used in the specification and claims of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of the methods of this disclosure as detailed in the appended claims. The accompanying drawings are for illustrative purposes only and should not be construed as limiting this patent.

[0017] The first embodiment of the present invention provides a network device adaptive management method based on a baseline template and dynamic capability values, the specific technical method of which is as follows: Combination Figure 1 Explanation: In step S110, after the device goes online, the dynamic capability value of the device is obtained; The dynamic capability value includes device type, functional modules actually supported by the current device, and a first object. The first object covers or supplements the default parameters or default states of each capability in the first functional module of the benchmark functional template. The first functional module is a part of the functional modules in the benchmark functional template.

[0018] Specifically, dynamic capability values ​​define the incremental data format passed to the network management system when a device comes online. It is a lightweight JSON object containing the following three data formats: deviceType: Device type, used to match the baseline function template.

[0019] supportedFeatures: A list or key-value pairs that explicitly declare which feature modules the current device instance actually supports.

[0020] capabilityOverrides: A data object used to override or supplement defaultCapabilities in the baseline capability template. For example, {"vlan": {"maxVlans": 4096}, "acl": {"hiddenColumns": ["sourcePort"]}}.

[0021] In step S120, the dynamic capability value of the device is matched with a preset benchmark function template library to obtain a benchmark function template corresponding to the device type of the device. The baseline function template library includes baseline function templates corresponding to each device type. Each baseline function template includes declarations of all function modules that the device type may support, as well as default parameters or default states of each function module. The matching is the process of matching the device type with the baseline function template library to obtain the baseline function template corresponding to the current device.

[0022] Specifically, the baseline function template library predefines a baseline function template for each type of device (such as OLT and switch). This template is a structured data object (such as a JSON Schema) containing the following two data objects: functionalBlocks: A declaration of all functional modules that this type of device may support (such as "VLAN management", "ACL policy", "PON configuration", "system upgrade").

[0023] defaultCapabilities: The default parameters or default states of each capability under each functional module (e.g., the default columns displayed in a table, the default values ​​of form fields).

[0024] Characteristics of this data object: This baseline feature template is relatively stable and defines the "capabilities cap" and UI framework for this device type.

[0025] In addition, it should be noted that the baseline function template library and dynamic capability values ​​are two layers within the hierarchical metadata definition module. This module is responsible for defining and storing metadata describing device functions. The corresponding matching templates are generated by the backend dynamic adaptation engine.

[0026] In step S130, the dynamic capability value of the device is compared with the baseline function template; include: The actual supported functional modules in the dynamic capability value of the device are compared with all possible supported functional modules in the benchmark functional template; Identify the functional modules that are different from the actual functional modules supported in the dynamic capability value of the device among all possible functional modules in the benchmark functional template, and use them as the first comparison result; Identify the functional modules that are the same as the functional modules actually supported in the dynamic capability value of the device among all possible functional modules in the benchmark functional template, and use them as the second comparison result.

[0027] The comparison process is performed in the backend dynamic adaptation engine. Specifically, this dynamic adaptation engine has the following three functions: including: Template matching: Load the corresponding template from the baseline function template library based on the device type reported by the device.

[0028] Capability negotiation includes the following two operations: Function trimming: Compare the explicitly supported function modules reported by the device with all potentially supported function modules in the template, and automatically hide functions that are in the template but not supported by the device.

[0029] Parameter Override: Uses a data object reported by the device to override or supplement the default parameters or default states of various capabilities in the benchmark function template.

[0030] Global capability view construction: The engine deeply merges the baseline function templates and dynamic capabilities to generate a complete global capability view for the device instance.

[0031] In step S140, the baseline function template is dynamically manipulated based on the comparison results to obtain a global capability view.

[0032] In some embodiments, the dynamic operation includes: Remove the first comparison result from the benchmark function template; The default parameters or default state of the second comparison result are overwritten using the first object in the dynamic capability value of the device to obtain a global capability view.

[0033] The two operations mentioned above for capability negotiation constitute the process of the dynamic operation.

[0034] Specifically, the dynamic operation involves performing two capability negotiation operations on the baseline function template after device matching in the dynamic adaptation engine, and then executing the global capability view construction function in the engine to obtain a complete global capability view for the corresponding device.

[0035] The second embodiment of the present invention also provides a network device adaptive management method based on a baseline template and dynamic capability values, the specific technical method of which is as follows: In step S210, after the device goes online, the dynamic capability value of the device is obtained; The dynamic capability value includes device type, functional modules actually supported by the current device, newly added functions not defined in the baseline functional template, and a first object. The first object covers or supplements the default parameters or default states of each capability in the first functional module in the baseline functional template. The first functional module is a part of the functional modules in the baseline functional template.

[0036] Specifically, dynamic capability values ​​define the incremental data format passed to the network management system when a device comes online. It is a lightweight JSON object containing the following four data formats: deviceType: Device type, used to match the baseline function template.

[0037] supportedFeatures: A list or key-value pairs that explicitly declare which feature modules the current device instance actually supports.

[0038] capabilityOverrides: A data object used to override or supplement defaultCapabilities in the baseline capability template. For example, {"vlan": {"maxVlans": 4096}, "acl": {"hiddenColumns": ["sourcePort"]}}.

[0039] extendedCapabilities: (optional) Used to declare new capabilities not defined in the baseline capability template, which the system can use to dynamically expand the management interface.

[0040] In step S220, the dynamic capability value of the device is matched against a preset benchmark function template library to obtain a benchmark function template corresponding to the device type of the device. The baseline function template library includes baseline function templates corresponding to each device type. Each baseline function template for each device type includes declarations of all function modules that the device type may support, as well as default parameters or default states of each function module's capabilities. It also includes rules for mapping front-end page components or routes. The matching is the process of matching the device type from the baseline function template library to obtain the baseline function template corresponding to the current device.

[0041] Specifically, the baseline function template library predefines a baseline function template for each type of device (such as OLT and switch). This template is a structured data object (such as a JSON Schema) containing the following three data objects: functionalBlocks: A declaration of all functional modules that this type of device may support (such as "VLAN management", "ACL policy", "PON configuration", "system upgrade").

[0042] uiMapping: Rules for mapping each functional module to a specific page component or route on the front end.

[0043] defaultCapabilities: The default parameters or default states of each capability under each functional module (e.g., the default columns displayed in a table, the default values ​​of form fields).

[0044] Characteristics of this data object: This baseline feature template is relatively stable and defines the "capabilities cap" and UI framework for this device type.

[0045] In addition, it should be noted that the baseline function template library and dynamic capability values ​​are two layers within the hierarchical metadata definition module. This module is responsible for defining and storing metadata describing device functions. The corresponding matching templates are generated by the backend dynamic adaptation engine.

[0046] In step S230, the dynamic capability value of the device is compared with the baseline function template; include: The actual supported functional modules in the dynamic capability value of the device are compared with all possible supported functional modules in the benchmark functional template; Identify the functional modules that are different from the actual functional modules supported in the dynamic capability value of the device among all possible functional modules in the benchmark functional template, and use them as the first comparison result; Identify the functional modules that are the same as the functional modules actually supported in the dynamic capability value of the device among all possible functional modules in the benchmark functional template, and use them as the second comparison result.

[0047] Identify the functional modules that are not the same as all the functional modules that may be supported in the benchmark functional template among the functional modules actually supported in the dynamic capability value of the device, and use them as the third comparison result.

[0048] The comparison process is performed in the backend dynamic adaptation engine. Specifically, this dynamic adaptation engine has the following three functions: including: Template matching: Load the corresponding template from the baseline function template library based on the device type reported by the device.

[0049] Capability negotiation includes the following three operations: Function trimming: Compare the explicitly supported function modules reported by the device with all potentially supported function modules in the template, and automatically hide functions that are in the template but not supported by the device.

[0050] Parameter Override: Uses a data object reported by the device to override or supplement the default parameters or default states of various capabilities in the benchmark function template.

[0051] Functionality Expansion: If there are new functions in the dynamic capability values ​​that are not defined in the baseline capability template, the engine will match or record them with known UI components for future expansion.

[0052] Global capability view construction: The engine deeply merges the baseline function templates and dynamic capabilities to generate a complete global capability view for the device instance.

[0053] In step S240, based on the comparison results, the baseline function template is dynamically manipulated to obtain a global capability view.

[0054] In some embodiments, the dynamic operation includes: Remove the first comparison result from the benchmark function template; The default parameters or default state of the second comparison result are overwritten using the first object in the dynamic capability value of the device to obtain a global capability view.

[0055] Add the third comparison result to the benchmark function template.

[0056] The three operations mentioned above for capability negotiation constitute the process of the dynamic operation.

[0057] Specifically, the dynamic operation involves performing three operations in the capability negotiation process within the dynamic adaptation engine on the baseline function template after device matching, and then executing the global capability view construction function in the engine to obtain a complete global capability view for the corresponding device. This view is the unique and authoritative data source for front-end rendering.

[0058] In step S250, front-end rendering is performed based on the global capability view to obtain a customized device management interface.

[0059] The front-end rendering is performed according to the rules of mapping front-end page components or routes of the baseline functional template.

[0060] Specifically, front-end rendering is performed in a front-end metadata-driven rendering engine and includes the following three operations: Routing and Menu Generation: The engine parses the declarations of all functional modules that this type of device may support in the global capability view and the rules for mapping each functional module to which page component or route in the front end, and dynamically generates navigation menus and route structures.

[0061] Dynamic loading and configuration of components: When a user accesses a function page, the engine dynamically loads the corresponding UI component (such as the VLAN configuration component) according to the above mapping rules; when the component is initialized, it receives capability value data from the corresponding module in the global capability view; the component configures itself according to these capability values, such as: hiding / showing certain table columns, disabling certain input boxes, setting the range of parameters, etc.

[0062] Unified data source: The rendering and behavior of all components depend on the global capability view, achieving complete decoupling between the front-end and back-end business logic.

[0063] The third embodiment of the present invention provides a method for generating a customized management interface for a new type of OLT device; Next, combine Figure 2 Explanation of how to implement the method of this invention: Before setting up a new OLT device (e.g., VOLT-9000), the network management system administrator needs to perform a one-time pre-configured template setup. Additionally, it should be noted that the baseline function template library and dynamic capability values ​​are two layers within the hierarchical metadata definition module. This module is responsible for defining and storing metadata describing device functions.

[0064] First, the layered metadata definition module is used to define two levels: the baseline function template and the dynamic capability values ​​of the device are obtained and reported.

[0065] Since VOLT-9000 belongs to the OLT category, we use or create a baseline function template for the OLT type. This template is defined in JSON Schema format, and defining the baseline function template is specifically implemented through the following operations: / / benchmark_template_olt.json { "deviceType": "OLT", "version": "1.0", "functionalBlocks": [ { "id": "pon_management", "name": "PON Port Management", "uiComponent": "PonManagementPanel.vue", / / Mapped front-end component "defaultCapabilities": { "maxPorts": 16, "supportedModes": ["GPON", "XG-PON"], "hiddenColumns": ["fecStatus"] } }, { "id": "vlan_management", "name": "VLAN Configuration", "uiComponent": "VlanManagementPanel.vue", "defaultCapabilities": { "maxVlans": 4094, "supportVlanStacking": true } }, { "id": "system_upgrade", "name": "System Upgrade", "uiComponent": "SystemUpgradeWizard.vue", "defaultCapabilities": { "supportedProtocols": ["TFTP", "SFTP"] } } / / ... Other functional modules such as ACL, mirroring, etc. ] In this way, the template has completely defined the full set of functions that all OLT devices may have.

[0066] Furthermore, the VOLT-9000 device powers on, connects to the network management system, obtains and reports the device's dynamic capability values, and sends an HTTP POST request to the network management system's backend interface. The message body contains its "dynamic capability values," which is a lightweight JSON data. The detailed operation is as follows: / / Dynamic capability values ​​from VOLT-9000 { "deviceType": "OLT", "firmwareVersion": "V2.1.5", "supportedFeatures": ["pon_management", "vlan_management"], / / Declares support for only PON and VLAN management "capabilityOverrides": { "pon_management": { "maxPorts": 32, / / This model supports 32 PON ports, overriding the default value of 16. "supportedModes": ["GPON", "XG-PON", "XGS-PON"] / / Added XGS-PON mode }, "vlan_management": { "supportVlanStacking": false / / This model does not support VLAN Stacking } }, "extendedCapabilities": { "energy_saving": { / / This is a new feature not present in the baseline template. "name": "Energy Saving Strategy", "uiComponent": "EnergySavingPanel.vue", / / Associated with a new front-end component "config": { "sleepMode": true } } } } The dynamic capability values ​​are reported to the backend dynamic adaptation engine for further processing.

[0067] Specifically, perform the following three steps: Template matching: The engine loads benchmark_template_olt.json based on deviceType: "OLT".

[0068] Capability negotiation includes the following three aspects: Feature trimming: The system_upgrade module in the template does not exist in the supportedFeatures list, so it will be marked as "visible": false.

[0069] Parameter overrides: maxPorts for pon_management has been updated to 32, and "XGS-PON" has been added to supportedModes. supportVlanStacking for vlan_management has been set to false.

[0070] Feature extension: A new feature, energy_saving, was discovered in extendedCapabilities, and the engine added it as a new feature module to the final output.

[0071] Generate a unique global capability view for this device instance: The engine deeply merges the device's dynamic capability values ​​with the baseline function template. This generates a complete global capability view specific to this device instance. Detailed steps are as follows: { "deviceId": "VSG-9000-001", "resolvedView": { "functionalBlocks": [ { "id": "pon_management", "name": "PON Port Management", "uiComponent": "PonManagementPanel.vue", "capabilities": { / / Note: This is the final capability value after merging. "maxPorts": 32, "supportedModes": ["GPON", "XG-PON", "XGS-PON"], "hiddenColumns": ["fecStatus"] }, "visible": true }, { "id": "vlan_management", "name": "VLAN Configuration", "uiComponent": "VlanManagementPanel.vue", "capabilities": { "maxVlans": 4094, "supportVlanStacking": false }, "visible": true }, { "id": "system_upgrade", "name": "System Upgrade", "uiComponent": "SystemUpgradeWizard.vue", "capabilities": { "supportedProtocols": ["TFTP", "SFTP"] }, "visible": false / / The content is cropped and not displayed on the interface. }, { "id": "energy_saving", / / New feature "name": "Energy Saving Strategy", "uiComponent": "EnergySavingPanel.vue", "capabilities": { "sleepMode": true }, "visible": true } ] } } After obtaining the global capability view, the network management front-end retrieves the global capability view generated by the device from the back-end.

[0072] The global capability view is rendered using a front-end-metadata-driven rendering engine, resulting in a customized device management interface.

[0073] Specifically, perform the following two operations: Dynamic navigation bar generation: The front-end engine parses resolvedView.functionalBlocks and only generates navigation menu items for modules with visible: true (i.e., "PON Port Management", "VLAN Configuration", and "Energy Saving Policy"). Users will not see the "System Upgrade" function.

[0074] Dynamic loading and configuration of feature pages: When a user clicks "PON Port Management", the front end dynamically loads the PonManagementPanel.vue component.

[0075] During initialization, this component receives capabilities data from the global capabilities view: { "maxPorts": 32, "supportedModes": ["GPON", "XG-PON", "XGS-PON"], ...}.

[0076] The component internally uses this data for self-configuration: based on maxPorts: 32, it generates a configuration interface for 32 PON ports. Based on supportedModes, it displays three options in the drop-down list: GPON, XG-PON, and XGS-PON. Similarly, the new "Energy Saving Strategy" function page is dynamically loaded and displayed correctly.

[0077] Obviously, the above embodiments of the present invention are merely examples for clearly illustrating the present invention, and are not intended to limit the implementation of the present invention. Those skilled in the art can make other variations or modifications based on the above description. It is neither necessary nor possible to exhaustively describe all embodiments here. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the scope of protection of the claims of the present invention.

Claims

1. A network device adaptive management method based on a baseline template and dynamic capability values, characterized in that: Includes the following steps: 1.1: After the device goes online, obtain the dynamic capability value of the device; 1.2: Match the dynamic capability value of the device with a preset benchmark function template library to obtain a benchmark function template corresponding to the device type; 1.3: Compare the dynamic capability value of the device with the baseline function template; 1.4: Based on the comparison results, the baseline function template is dynamically manipulated to obtain a global capability view.

2. The network device adaptive management method based on baseline templates and dynamic capability values ​​according to claim 1, characterized in that: The baseline function template library includes baseline function templates corresponding to each device type. Each baseline function template for each device type includes declarations of all function modules that the device type may support, as well as default parameters or default states of each capability in each function module.

3. The network device adaptive management method based on benchmark templates and dynamic capability values ​​according to claim 2, characterized in that: The dynamic capability value includes the device type, the functional modules actually supported by the current device, and a first object. The first object covers or supplements the default parameters or default states of each capability in the first functional module of the benchmark functional template. The first functional module is a part of the functional modules in the benchmark functional template.

4. The network device adaptive management method based on baseline templates and dynamic capability values ​​according to claim 1, characterized in that: The template matching includes: Based on the device type, the baseline function template corresponding to the current device is obtained by matching from the baseline function template library.

5. The network device adaptive management method based on baseline templates and dynamic capability values ​​according to claim 3, characterized in that: The dynamic capability value of the device is compared with the baseline functional template, including: The actual supported functional modules in the dynamic capability value of the device are compared with all possible supported functional modules in the benchmark functional template; Identify the functional modules that are different from the actual functional modules supported in the dynamic capability value of the device among all possible functional modules in the benchmark functional template, and use them as the first comparison result; Identify the functional modules that are the same as the functional modules actually supported in the dynamic capability value of the device among all possible functional modules in the benchmark functional template, and use them as the second comparison result.

6. The network device adaptive management method based on benchmark templates and dynamic capability values ​​according to claim 5, characterized in that: The dynamic operations include: Remove the first comparison result from the benchmark function template; The default parameters or default state of the second comparison result are overwritten using the first object in the dynamic capability value of the device to obtain a global capability view.

7. The network device adaptive management method based on baseline templates and dynamic capability values ​​according to claim 6, characterized in that: The comparison between the device's dynamic capability value and the baseline function template also includes: Identify the functional modules that are not the same as all the functional modules that may be supported in the benchmark functional template among the functional modules actually supported in the dynamic capability value of the device, and use them as the third comparison result.

8. The network device adaptive management method based on baseline templates and dynamic capability values ​​according to claim 7, characterized in that: The dynamic operation also includes: Add the third comparison result to the benchmark function template.

9. The network device adaptive management method based on baseline templates and dynamic capability values ​​according to claim 8, characterized in that: The baseline functional template also includes rules for mapping front-end page components or routes.

10. The network device adaptive management method based on a baseline template and dynamic capability values ​​according to claim 9, characterized in that: After obtaining the global capability view, the following steps are also included: Based on the mapping rules of the baseline function template, the global capability view is rendered on the front end to obtain a customized device management interface.

Images