Equipment information display method and device, equipment, medium and product

By building microservice architecture and performance prediction components, using network planner and front-end platform to integrate and display network device information, the problem of different manufacturers and types of devices cannot be managed uniformly, and efficient device information display and intelligent operation and maintenance are achieved.

CN120434141APending Publication Date: 2025-08-05WUHAN FS COM TECHNOLOGY CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202510693336.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-05-27
Publication Date
2025-08-05

AI Technical Summary

Technical Problem

The existing network management platform cannot effectively integrate network equipment of different manufacturers and types, resulting in the inability to display equipment information efficiently, the management efficiency is inefficient, and the collaboration and intelligent operation and maintenance between devices are limited.

Method used

By receiving equipment information of newly added network equipment, using the network planner and front-end platform for integration and visual display, building microservice architecture, performance prediction components and alarm rules, optimizing management platform and control platform, and realizing unified display of equipment information.

Benefits of technology

It improves the efficiency of equipment information display, reduces the dispersion of operation and maintenance resources, improves the automation and intelligence level of network management, and supports cross-device linkage and efficient troubleshooting.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120434141A_ABST
    Figure CN120434141A_ABST
Patent Text Reader

Abstract

The invention discloses an equipment information display method and device, equipment, a medium and a product, and relates to the technical field of equipment operation and maintenance management, and the method comprises the steps: receiving equipment information of newly-added network equipment; integrating the newly added network equipment to a pre-constructed network planner based on the equipment information; and under the condition that an equipment visualization request is received, equipment information display is performed through the network planner and the front-end platform based on the equipment visualization request, and a display result is obtained. Therefore, the problem that various types of devices cannot be integrated in the same management system, so that the device information cannot be efficiently displayed to managers for viewing is solved, and the efficiency of device information display is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the technical field of equipment operation and maintenance management, and in particular to a method, apparatus, equipment, medium, and product for displaying equipment information. Background Art

[0002] Currently, in network and IoT device management, the network management platforms provided by most suppliers only support the management and monitoring of devices of the same manufacturer and type. Network management platforms for different device types cannot be used interchangeably due to problems such as protocol incompatibility, inconsistent interfaces, and differences in data formats. The root cause is the lack of unified technical standards in the industry. Manufacturers use proprietary protocols based on business strategies to build a closed ecosystem, further exacerbating the isolation between platforms.

[0003] This situation requires users to deploy multiple independent network management systems (such as switch network management, industrial PLC network management, etc.) for equipment from different manufacturers and types. Operation and maintenance resources are scattered, and troubleshooting requires frequent switching between multiple platforms, resulting in low management efficiency and high time costs. At the same time, the ability to collaborate between devices is limited, and high-level functions such as cross-device linkage and intelligent operation and maintenance (such as performance prediction based on multi-device data) are difficult to achieve, which restricts technological innovation and ecological coordinated development. In addition, the phenomenon of users being bound to a single brand ecosystem inhibits market competition and weakens the manufacturer's motivation for technological iteration.

[0004] In summary, the lack of versatility of existing network management platforms has become a key technical obstacle hindering the improvement of IoT management efficiency and intelligent upgrades.

[0005] The above content is only used to assist in understanding the technical solution of this application and does not constitute an admission that the above content is prior art. Summary of the Invention

[0006] The main purpose of this application is to provide a device information display method, apparatus, equipment, medium and product, aiming to solve the technical problem that various types of equipment cannot be integrated into the same management system, resulting in the inability to efficiently display device information to managers for viewing.

[0007] To achieve the above objectives, the present application proposes a device information display method, which is applied to a device management system. The device management system includes a front-end platform. The device information display method includes:

[0008] Receive device information of newly added network devices;

[0009] Integrating the newly added network device into a pre-built network planner based on the device information;

[0010] When a device visualization request is received, device information is displayed based on the device visualization request through the network planner and the front-end platform to obtain a display result.

[0011] In one embodiment, before the step of receiving device information of a newly added network device, the method further includes:

[0012] Collect network equipment operation and maintenance information;

[0013] Based on the network equipment operation and maintenance information, containerized segmentation is performed through containerized applications to obtain a microservice architecture;

[0014] Based on the microservice architecture, control and management are separated to obtain a management platform and a control platform;

[0015] An initial user interface library is constructed based on the network device operation and maintenance information, and a service interaction working mode is established through the network device operation and maintenance information and the initial user interface library;

[0016] Collecting performance indicators of the equipment management system through a telemetry platform, and constructing a performance prediction component based on the performance indicators and a performance prediction algorithm;

[0017] According to the management platform, control platform, service interaction working mode and performance prediction components, a network planner is constructed by using a network performance modeling tool.

[0018] In one embodiment, the step of integrating the newly added network device into a pre-built network planner based on the device information includes:

[0019] Parsing the device information to obtain the device type and device parameters of the newly added network device;

[0020] Determining the service configuration logic of the newly added network device based on the device type and device parameters;

[0021] Integrate the newly added devices into the microservice architecture according to the business configuration logic to obtain a final microservice architecture;

[0022] Optimize the business interaction working mode, management platform, control platform, and performance prediction component according to the final microservice architecture to obtain optimization results;

[0023] When the optimization result indicates that the optimization is completed, performing performance verification on the network planner to obtain a verification result;

[0024] If the verification result is that the verification is passed, the integration result is that the integration is successful.

[0025] In one embodiment, after the step of integrating the newly added network device into a pre-built network planner based on the device information, the method further includes:

[0026] Performing performance evaluation on the newly added network equipment by the network planner to obtain performance parameters of the newly added network equipment;

[0027] According to the performance parameters, rule configuration is performed through the performance prediction component to obtain alarm rules;

[0028] Based on the alarm rules, the management platform performs alarm detection on the newly added network device, and generates an alarm record when the newly added network device triggers an alarm.

[0029] In one embodiment, the step of displaying device information based on the device visualization request through the network planner and the front-end platform to obtain a display result includes:

[0030] Determining a device to be displayed based on the device visualization request;

[0031] According to the device to be displayed, data query is performed through the network planner to obtain the operating data and configuration parameters of the display device;

[0032] Based on the operating data and configuration parameters, device information is displayed through the front-end platform to obtain a display result.

[0033] In one embodiment, the step of displaying device information based on the operating data and configuration parameters through the front-end platform to obtain a display result includes:

[0034] Converting the operating data and configuration parameters into rendering data through the front-end platform;

[0035] Perform visual rendering based on the rendering data through the data binding mechanism of the front-end platform to obtain a rendering interface;

[0036] The device information is displayed through the rendering interface to obtain a display result.

[0037] In addition, to achieve the above-mentioned purpose, the present application also proposes a device information display device, wherein the device information display method is applied to a device management system, wherein the device management system includes a front-end platform, and the device information display device includes:

[0038] A receiving module, used to receive device information of newly added network devices;

[0039] An integration module, configured to integrate the newly added network device into a pre-built network planner based on the device information;

[0040] The display module is used to display device information based on the device visualization request through the network planner and the front-end platform to obtain a display result when a device visualization request is received.

[0041] In addition, to achieve the above-mentioned purpose, the present application also proposes a device information display device, which includes: a memory, a processor, and a computer program stored on the memory and runnable on the processor, and the computer program is configured to implement the steps of the device information display method described above.

[0042] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium. A computer program is stored on the storage medium, and when the computer program is executed by the processor, the steps of the device information display method described above are implemented.

[0043] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the steps of the device information display method described above.

[0044] One or more technical solutions proposed in this application have at least the following technical effects:

[0045] The embodiment of the present application proposes a device information display method, apparatus, equipment, medium and product, which receives the device information of a newly added network device; integrates the newly added network device into a pre-built network planner based on the device information; and upon receiving a device visualization request, displays the device information through the network planner and the front-end platform based on the device visualization request to obtain a display result. Thus, after receiving the device information of the newly added network device, the device management system integrates the newly added network device into the pre-built network planner based on the device information, and then upon receiving a device visualization request, displays the device information through the network planner and the front-end platform to obtain a display result, thereby solving the problem that various types of equipment cannot be integrated into the same management system, resulting in the inability to efficiently display the device information to management personnel for viewing, and improving the efficiency of device information display. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

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

[0048] Figure 1 A flowchart of the first embodiment of the device information display method of this application is provided;

[0049] Figure 2 This is a simplified architecture diagram of the device management system involved in the device information display method of this application;

[0050] Figure 3 A flowchart of the second embodiment of the device information display method of this application is provided;

[0051] Figure 4 The device information display method of this application involves a first system functional structure diagram;

[0052] Figure 5 The device information display method of this application involves a second system functional structure diagram;

[0053] Figure 6 A schematic diagram of the system structure of the device information display method provided in Example 2 of this application;

[0054] Figure 7 This is a schematic diagram of the module structure of the device information display device according to an embodiment of the present application;

[0055] Figure 8 This is a schematic diagram of the device structure of the hardware operating environment involved in the device information display method in the embodiment of the present application.

[0056] The purpose, features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0057] It should be understood that the specific embodiments described herein are merely used to explain the technical solutions of the present application and are not intended to limit the present application.

[0058] In order to better understand the technical solution of this application, the following will be described in detail with reference to the accompanying drawings and specific implementation methods. The main solutions of the embodiments of this application are: collecting network equipment operation and maintenance information; based on the network equipment operation and maintenance information, performing containerized segmentation through containerized applications to obtain a microservice architecture; performing management and control separation based on the microservice architecture to obtain a management platform and a control platform; constructing an initial user interface library based on the network equipment operation and maintenance information, and building a business interaction working mode through the network equipment operation and maintenance information and the initial user interface library; collecting the performance indicators of the equipment management system through the telemetry platform, and constructing a performance prediction component based on the performance indicators and the performance prediction algorithm; constructing a network planner through a network performance modeling tool based on the management platform, control platform, business interaction working mode and performance prediction component. Parse the device information to obtain the device type and device parameters of the newly added network device; determine the business configuration logic of the newly added network device based on the device type and device parameters; integrate the newly added device into the microservice architecture according to the business configuration logic to obtain the final microservice architecture; optimize the business interaction working mode, management platform, control platform and performance prediction component according to the final microservice architecture to obtain an optimization result; if the optimization result is that the optimization is completed, perform performance verification on the network planner to obtain a verification result; if the verification result is that the verification is passed, then the integration result is that the integration is successful. Perform performance evaluation on the newly added network device through the network planner to obtain the performance parameters of the newly added network device; according to the performance parameters, perform rule configuration through the performance prediction component to obtain alarm rules; based on the alarm rules, perform alarm detection on the newly added network device through the management platform, and generate an alarm record when the newly added network device triggers an alarm. Based on the device visualization request, the device to be displayed is determined; based on the device to be displayed, data query is performed through the network planner to obtain the operating data and configuration parameters of the displayed device; based on the operating data and configuration parameters, the device information is displayed through the front-end platform to obtain a display result. The operating data and configuration parameters are converted into rendering data through the front-end platform; based on the rendering data, visual rendering is performed through the data binding mechanism of the front-end platform to obtain a rendering interface; the device information is displayed through the rendering interface to obtain a display result. This solves the problem that various types of equipment cannot be integrated into the same management system, resulting in the inability to efficiently display device information to management personnel for viewing, realizes the display of device information, and improves the efficiency of device information display.Based on the solution of the present invention, a device information display method is designed based on the fact that in reality, most suppliers' network management only supports the management and monitoring of the same type of equipment from the same manufacturer, and the network management platforms of different equipment types are not universal, which results in more resources and time being required to manage the equipment separately, thus causing low efficiency. The effectiveness of the device information display method of the present invention is verified when displaying the device information, and finally, the efficiency of device information display is significantly improved through the method of the present invention.

[0059] In this embodiment, for ease of description, the following description is made with the device information display apparatus as the execution subject.

[0060] In existing technologies, most network and IoT device management vendors provide network management platforms that only support the management and monitoring of devices of the same manufacturer and type. Network management platforms for different device types cannot be used interchangeably due to protocol incompatibility, inconsistent interfaces, and differences in data formats. The root cause lies in the industry's lack of unified technical standards. Manufacturers use proprietary protocols based on their business strategies to build a closed ecosystem, further exacerbating the isolation between platforms. This situation requires users to deploy multiple independent network management systems (such as switch network management, industrial PLC network management, etc.) for devices of different manufacturers and types. Operation and maintenance resources are dispersed, and troubleshooting requires frequent switching between multiple platforms, resulting in low management efficiency and high time costs. Users also need to switch between multiple systems to view device information, which reduces efficiency.

[0061] This application provides a solution that receives device information of newly added network devices in a device management system, integrates the newly added network devices into a network planner based on the device information, and at the same time, when a device visualization request is received, displays the device information through the network planner and the front-end platform to obtain display results, thereby providing users with better services.

[0062] As can be seen from the above embodiments, the present application receives the device information of the newly added network device; integrates the newly added network device into a pre-built network planner based on the device information; and upon receiving a device visualization request, displays the device information through the network planner and the front-end platform based on the device visualization request to obtain a display result. Thus, after receiving the device information of the newly added network device, the device management system integrates the newly added network device into the pre-built network planner based on the device information, and then upon receiving a device visualization request, displays the device information through the network planner and the front-end platform to obtain a display result. This solves the problem that various types of devices cannot be integrated into the same management system, resulting in the inability to efficiently display device information to management personnel for viewing, thereby improving the efficiency of device information display.

[0063] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, mobile phone, etc., or an electronic device capable of implementing the above functions, a device information display device, etc. The following uses the device information display device as an example to illustrate this embodiment and the following embodiments.

[0064] Based on this, the embodiment of the present application provides a device information display method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the device information display method of this application.

[0065] In this embodiment, the device information display method is applied to a device management system, which includes a front-end platform. The device information display method includes steps S01 to S03:

[0066] Step S01, receiving device information of a newly added network device;

[0067] It should be clear that the problem faced by this embodiment is that most network management platforms only support the management of devices of the same manufacturer and type. Due to protocol incompatibility, inconsistent interfaces and differences in data formats, different devices cannot communicate with each other. Due to the lack of unified technical standards, manufacturers use proprietary protocols to build a closed ecosystem, resulting in isolation between platforms. Users need to deploy multiple independent management systems for different devices, increasing operation and maintenance costs and time, and at the same time limiting the collaboration and intelligent operation and maintenance between devices. This results in an enterprise being unable to view and manage devices through a single system when managing multiple devices, resulting in low management efficiency.

[0068] Therefore, in this embodiment, the enterprise's network equipment management is used as an example. After an enterprise introduces new network equipment, the device information of the newly added network equipment is received through the device management system. The newly added network equipment includes but is not limited to routers, switches, load balancers, gateways, and network monitoring equipment, etc. At the same time as the introduction, the device information of the device will be synchronously input into the device management system.

[0069] Step S02: Integrate the newly added network device into a pre-built network planner based on the device information;

[0070] After receiving the device information of the newly added network devices, the newly added network devices are integrated into the pre-built network planner based on the device information. The network planner is a tool or software used to design, optimize, and manage computer networks. It helps network administrators and engineers effectively plan and layout network architecture to meet specific performance, security, reliability, and scalability requirements. Network planners typically have the following functions: network topology design (helping to design the network structure, including device layout, connection methods, and data flow paths to ensure network efficiency and stability), bandwidth analysis and allocation (analyzing traffic based on network requirements and reasonably allocating bandwidth resources to optimize network performance), IP address planning (managing and allocating IP addresses to ensure that the addresses of each device in the network are reasonable and valid to avoid conflicts), security design (planning network security policies, including firewalls, intrusion detection systems, VPNs, etc., to ensure the security of data transmission), performance simulation and optimization (predicting network performance by simulating network traffic and load, and optimizing the design to meet future needs), and device configuration and compatibility assessment (assessing the compatibility between different devices, such as switches and routers, to ensure the stability of the overall network architecture).

[0071] Step S03: upon receiving a device visualization request, displaying device information based on the device visualization request through the network planner and the front-end platform to obtain a display result.

[0072] After the integration of the equipment is completed, it means that the newly added network equipment is available for users to display the equipment information. Therefore, when a device visualization request is received, the device management system can display the device information based on the device visualization request through the network planner and the front-end platform to obtain the display results. Among them, the device information display in this embodiment can be an alarm panel, performance analysis, full network topology view, and real-time perception of device failures. It should be displayed according to actual user needs. In addition, the device management system of this embodiment also provides scenario-based monitoring, that is, using a scenario-based dashboard (Dashboard) and large-screen monitoring to fully grasp the status of the information and communication technology (ICT) system.

[0073] The above steps improve the automation, visualization, and intelligence of network management through integration and visualization. This not only solves the problem of multiple devices being unable to be integrated into the same system, but also reduces manual intervention, improves efficiency and reliability, and provides stronger support for network planning, troubleshooting, resource optimization, and decision-making.

[0074] Specifically, before displaying the device information, this embodiment also requires pre-building a network planner to manage the devices. Therefore, before step S01, the step of receiving the device information of the newly added network device, the method further includes:

[0075] Step S0101, collecting network equipment operation and maintenance information;

[0076] Step S0102: Based on the network device operation and maintenance information, containerized segmentation is performed through containerized applications to obtain a microservice architecture;

[0077] Step S0103: performing control separation based on the microservice architecture to obtain a management platform and a control platform;

[0078] Step S0104: constructing an initial user interface library based on the network device operation and maintenance information, and establishing a business interaction working mode through the network device operation and maintenance information and the initial user interface library;

[0079] Step S0105: collecting performance indicators of the equipment management system through a telemetry platform, and constructing a performance prediction component based on the performance indicators and a performance prediction algorithm;

[0080] Step S0106: Based on the management platform, control platform, service interaction working mode and performance prediction component, a network planner is constructed by a network performance modeling tool.

[0081] First, it is necessary to collect operation and maintenance information of network equipment, which includes equipment status, performance indicators, configuration changes, etc. The collection of this data provides basic data support for subsequent decision-making and optimization. In this embodiment, the equipment status, operation data and logs are automatically collected by deploying sensors and telemetry tools to ensure the real-time and accuracy of the data. Subsequently, containerized applications (i.e., Docker and Docker Compose tools) are used to decompose the system into multiple functional modules. Each module runs in an independent container, and each container executes specific functional services (i.e., microservice architecture) to ensure decoupling between services. In this embodiment, the microservice architecture can improve the maintainability and scalability of the system. At the same time, containerized segmentation can reduce the complexity of application deployment and updates, and improve development and operation and maintenance efficiency.

[0082] In order to improve the flexibility and stability of the system, based on the microservice architecture, the management platform (responsible for data management and business logic) and the control platform (responsible for equipment control and operation) are separated. The management platform is responsible for system-level management, while the control platform focuses on equipment operation and control, which helps to improve the scalability, maintainability and security of the system, and is also conducive to the independent upgrade and maintenance of each platform. In order to optimize the user experience and ensure that managers can interact with business through an intuitive interface to improve the efficiency and accuracy of operations, this embodiment builds an initial UI library, quickly builds and iterates the user interface, and then updates and iterates the UI style library. It adopts multi-view design and workflow mode (Workflow) to realize the interaction between users and the system. Through data interaction with the device management system, the interface can dynamically display the status and control of network devices.

[0083] At the same time, the telemetry platform collects device performance data (such as network traffic, latency, bandwidth, etc.) in real time, analyzes this data through predictive algorithms, and builds performance prediction components. Based on this data, it can predict future network performance bottlenecks and conduct early warnings and adjustments. Through the performance prediction components, the ability to predict network performance is improved, performance bottlenecks can be discovered in advance, network overload or failure can be avoided, and network reliability and stability can be improved.

[0084] Finally, based on the GNPy open source system, the Gaussian model is used for network planning and optimization. The network planner will model the network topology based on performance data and prediction results and provide optimization suggestions. Through scientific network modeling and planning, the use of network resources can be optimized, the utilization rate of network capacity can be improved, performance bottlenecks can be avoided, and the efficient operation of the network can be guaranteed.

[0085] In the above process, each link from equipment information collection to network planning is gradually improved, and finally the following is obtained: Figure 2 The software architecture shown mainly adopts the service-oriented SOA software architecture. The logical architecture mainly includes operation and maintenance management services, business management services, and basic management services. The specific architecture content includes:

[0086] (1) Front-end (Browser): HTML (used to build the basic structure of web pages), Bootstrap (a popular front-end framework for quickly designing and customizing responsive layouts), ElementUI (a component library based on Vue.js for building user interfaces), jQuery (a fast and concise JavaScript library for simplifying HTML document traversal, event handling, animation, and other operations), and JavaScript (a scripting language for adding interactivity and dynamic features to web pages).

[0087] (2) Proxy layer: Gunicorn (+gevent)) a Python WSGI HTTP server for handling concurrent requests).

[0088] (3) Interface layer (Authentication): Tacas Auth (module for identity authentication), LocalAuth (local authentication module).

[0089] (4) Flask APP (application layer): Automation API (automation-related API), Config API (configuration-related API), DashBoard API (dashboard-related API), Inventory API (inventory management-related API), Tornado SSH Server (Tornado-based SSH server), Lifecycle API (lifecycle management-related API), Management API (management-related API), monitor API (monitoring-related API), AnsiblePlayBook (Ansible script for automation tasks), User API (user management-related API), VtepManagement API (virtual tunnel endpoint, VTEP, for management-related API), Template API (template management-related API) and WebSSH (web-based SSH client).

[0090] (5) Basic service layer: SDN Application (software-defined network application), Celery Queue (message queue for processing asynchronous tasks), Rabbitmq (an open source message broker for transmitting messages between different applications), Mysql (a relational database management system for storing and managing data), and File System (file system for storing and managing files).

[0091] In this embodiment, the overall system architecture diagram of the present application is explained, which uses a network planner for centralized resource management and unified monitoring of equipment health status to enhance the overall coordination and flexibility of the system, ensure that the network management system can respond to various network conditions in real time, and ensure the efficient, stable and sustainable development of the network.

[0092] More specifically, when a new network device is received, it is also necessary to integrate it into the network planner for subsequent management. Therefore, the above step S02, the step of integrating the new network device into the pre-built network planner based on the device information, includes:

[0093] Step S021, parsing the device information to obtain the device type and device parameters of the newly added network device;

[0094] Step S022: determining the service configuration logic of the newly added network device based on the device type and device parameters;

[0095] Step S023: Integrate the newly added device into the microservice architecture according to the business configuration logic to obtain a final microservice architecture;

[0096] Step S024: Optimizing the business interaction working mode, management platform, control platform, and performance prediction component according to the final microservice architecture to obtain an optimization result;

[0097] Step S025: If the optimization result is that the optimization is completed, the network planner is subjected to performance verification to obtain a verification result;

[0098] Step S026: If the verification result is that the verification is passed, the integration result is that the integration is successful.

[0099] In order to integrate the newly added devices into the network planner, this embodiment prioritizes parsing the device information to obtain the device type and device parameters of the newly added network devices. This step prepares for subsequent device configuration and integration, ensures that the basic information of the device is accurately extracted, and provides the necessary basic data for its subsequent configuration. Subsequently, based on the specific type of the device (for example, switch, router, etc.) and its performance parameters (such as bandwidth, processing power, etc.), appropriate business configuration logic is defined for the device. This configuration logic typically includes how the device participates in forwarding network traffic, how to perform traffic control, load balancing configuration, etc.

[0100] The device's business configuration logic is then converted into a service module in the microservice architecture. Using Docker containerization technology, the device functions are encapsulated into independent microservices, which are managed and deployed according to container orchestration tools (such as Docker Compose). This allows the device to communicate and interact with other microservice modules, ultimately forming a dynamic and scalable microservice architecture that can flexibly manage and expand devices and their functions through containerization, ensuring that the architecture can flexibly respond to new devices and future changes. Subsequently, the business interaction working mode is optimized (i.e., the interaction process and UI design are adjusted to make the system interface more user-friendly and the operation more efficient), the management platform and control platform are optimized (i.e., the functions of the management platform and control platform can work together to improve the system's management efficiency and control capabilities), and the performance prediction component is optimized (i.e., based on the collected performance data and prediction algorithm, the accuracy of performance prediction is further improved to identify potential performance bottlenecks in advance). After the above optimization, the overall performance, stability, and scalability of the system are improved, business interaction is smoother, and device management and control are more efficient.

[0101] To ensure the proper functioning of the network planner, even if the optimization result is complete, performance verification of the network planner is required. Using a pre-set performance testing tool, based on a real network environment or simulated data, the network planner's performance is verified. This includes testing key performance indicators such as network capacity, bandwidth utilization, and latency, and comparing them with the expected optimization targets. Ultimately, verification results are obtained. If the verification test passes, the system can enter the production environment or implementation phase. At this point, all newly added devices have been fully integrated into the microservices architecture and are able to work together, thus completing the integration of the newly added network devices, ensuring the system operates as expected, and providing a reliable foundation for subsequent network management and optimization.

[0102] The core purpose of the above steps is to ensure that new equipment can be smoothly integrated into the system through a dynamic and flexible microservice architecture and intelligent performance optimization methods, optimize business interactions, control platforms, management platforms and performance prediction capabilities, and ultimately ensure that system performance meets expectations through verification. This process not only ensures the efficient integration of network equipment, but also improves the reliability and flexibility of the entire system, laying a solid foundation for subsequent network planning and management.

[0103] Furthermore, the system also adds corresponding alarm configurations for the devices in the network planner. In this embodiment, a newly added network device is used as an example. Therefore, after the above step S02, which integrates the newly added network device into the pre-built network planner based on the device information, the method further includes:

[0104] Step S0201, performing performance evaluation on the newly added network device through the network planner to obtain performance parameters of the newly added network device;

[0105] Step S0202: configuring rules through the performance prediction component according to the performance parameters to obtain alarm rules;

[0106] Step S0203: Based on the alarm rule, the management platform performs alarm detection on the newly added network device, and generates an alarm record when the newly added network device triggers an alarm.

[0107] After completing the integration of the new network device, it is necessary to configure the alarm rules for it and generate an alarm record when the alarm is triggered so that the user can know as soon as possible when making subsequent inquiries. In this embodiment, a network performance testing tool (such as Iperf, Ping, Traceroute, etc.) is used to conduct a comprehensive performance evaluation of the new device. The test content includes but is not limited to bandwidth, throughput, delay, packet loss rate, CPU usage, memory usage, etc. Then, through the device management interface (such as SNMP, CLI, etc.), the device operation data is collected regularly or in real time, including performance indicators such as traffic, load, interface status, CPU and memory usage. Finally, the evaluation results and the device performance data are integrated into a set of parameters. These performance parameters include specific values (for example, bandwidth is 1Gbps, CPU load is 70%, etc.).

[0108] The performance parameters are then analyzed and configured through the performance prediction component to generate relevant alarm rules to promptly detect anomalies or potential problems in device operation. Specifically, the performance prediction component can automatically analyze the performance trends of the device based on machine learning or historical data analysis, predict device performance changes, especially the risks of bottlenecks and overloads, and configure alarm rules based on the range of performance parameters and the baseline values during normal device operation. For example, if the CPU usage exceeds 90% or the bandwidth usage exceeds 80%, the system will trigger an alarm.

[0109] In this embodiment, customized alarm thresholds are also set for different performance parameters. Users can flexibly adjust the alarm rules based on factors such as the importance of the device and the network type. Finally, the management platform monitors the various performance indicators of the newly added devices in real time according to the preset alarm rules. It can determine whether the device has triggered an alarm by regularly polling the device's status information (such as SNMP capture data) or real-time data flow monitoring (such as collecting data through a traffic analysis engine).

[0110] If the performance parameters of the device exceed the preset alarm threshold (such as CPU usage exceeding the threshold, bandwidth usage is too high, etc.), an alarm is triggered. The alarm can be classified according to the device type and alarm level (such as information, warning, and severe alarm). Once the alarm is triggered, the system will automatically generate a detailed alarm record, which includes: alarm occurrence time, alarm type, alarm level, triggering device, triggering conditions, and alarm description. The alarm record can be stored in the log management system or database and provide a visual display.

[0111] In this embodiment, by enhancing device performance monitoring, alarm automation, and data-driven decision support, more efficient, stable, and flexible network management is achieved. These effects not only improve system stability and business continuity, but also greatly reduce the risk of failures, ensuring that the network can operate smoothly even in complex environments.

[0112] This embodiment adopts the above-mentioned scheme, specifically by receiving the device information of the newly added network device; integrating the newly added network device into a pre-built network planner based on the device information; and upon receiving a device visualization request, displaying the device information through the network planner and the front-end platform based on the device visualization request to obtain a display result. Thus, after receiving the device information of the newly added network device, the device management system integrates the newly added network device into the pre-built network planner based on the device information, and then upon receiving a device visualization request, displays the device information through the network planner and the front-end platform to obtain a display result. This solves the problem that various types of devices cannot be integrated into the same management system, resulting in the inability to efficiently display device information to management personnel for viewing, thereby improving the efficiency of device information display.

[0113] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the first embodiment can be referred to the above introduction and will not be described in detail later. Figure 3 In step S03, the device information display method further includes steps S031 to S033:

[0114] Step S031, determining a device to be displayed based on the device visualization request;

[0115] Step S032: performing data query on the network planner according to the device to be displayed to obtain the operating data and configuration parameters of the device to be displayed;

[0116] Step S033: Based on the operating data and configuration parameters, device information is displayed through the front-end platform to obtain a display result.

[0117] When a user or system issues a device visualization request, the system determines the list of devices that need to be displayed based on the conditions in the request (such as device type, location, status, etc.). It is clear that after receiving the visualization request, the system can identify the filtering conditions in the request, and then search for devices that meet the conditions in the device database based on the conditions, and determine the devices to be displayed (such as device ID, device name, device location, etc.).

[0118] Then, based on the devices to be displayed, the network planner is used to perform data queries to obtain the relevant operating data and configuration parameters of the devices. After receiving the device list, the network planner starts the data query process, including querying the real-time operating data of the devices (performance parameters, traffic, bandwidth, and load, etc.) and querying the configuration parameters of the devices (hardware configuration, software version, and network connection settings, etc.). In this process, the network planner can ensure the accuracy and real-time nature of the queried data and avoid outdated or incomplete data.

[0119] The device operation data and configuration parameters obtained from the query are then displayed through the front-end platform to form the final display results. After receiving the data provided by the network planner, the front-end platform appropriately formats and processes it. The final display interface provides interactive functions, allowing users to view detailed data, switch views, or perform other operations (such as viewing historical data for different time periods or changing device configurations).

[0120] The above steps ensure that the device's operating status and configuration information are clearly and accurately displayed to users, while supporting real-time monitoring and management.

[0121] More specifically, in step S033, the steps of displaying device information through the front-end platform based on the operating data and configuration parameters and obtaining the display results include:

[0122] Step S0331, converting the operating data and configuration parameters into rendering data through the front-end platform;

[0123] Step S0332: performing visual rendering according to the rendering data through the data binding mechanism of the front-end platform to obtain a rendering interface;

[0124] Step S0333: Display device information through the rendering interface to obtain a display result.

[0125] After the front-end platform receives the device's operating data and configuration parameters, it converts this information into rendering data to facilitate subsequent visualization operations. First, the original device operating data and configuration parameters (such as device status, performance indicators, configuration settings, etc.) are converted into data formats that can be used for front-end rendering (such as JSON, arrays, objects, etc.). The original data is then processed, such as calculation summary, sorting, filtering or aggregation, to ensure that only useful information is displayed during rendering. Finally, the data format is unified to ensure that all device data meets the display requirements and avoid display errors due to inconsistent data formats.

[0126] After the data conversion is completed, the data binding mechanism of the front-end platform is used to bind the rendering data to the user interface (UI) elements, and finally generate a rendering interface. In this embodiment, the converted rendering data is bound to HTML elements, charts, dashboards and other UI components through the data binding mechanism. Common technologies include data binding functions in frameworks such as Vue.js and React.js. After the binding is completed, any changes in the rendering data (such as real-time data updates) can be automatically synchronized to the front-end interface without the need to manually refresh the page. In this way, the rendering data is rendered through the template engine or components in the framework to generate the final interface content. For example, the device's operating status diagram, load diagram, performance curve diagram, etc. can be displayed.

[0127] The rendered interface is presented to the user and may include graphics, text, tables, and other forms to display the real-time status, configuration details, and historical data of the device, and provide user interaction functions. For example, the user can click on the chart to view detailed data, switch the displayed time range, and view information of different devices. If the device data is updated in real time, the front-end interface should be able to dynamically update the display content to reflect the latest device status or configuration changes.

[0128] These steps ensure that device information can be presented to users in an intuitive, clear, and interactive manner, facilitating real-time monitoring and management of devices.

[0129] Furthermore, in a static environment, that is, when the user does not view specific device information, in order to facilitate the user to open the operating system, this embodiment also provides the following Figure 4 The architecture function interface shown:

[0130] First, the device management system interface of this embodiment provides a dashboard tool, including:

[0131] (1) Global overview, which allows you to browse views (view the overall system view information), query views (query the required view information based on specific conditions), create new views (create new views for specific management and viewing), and cancel views (cancel the currently operating or unnecessary views).

[0132] (2) View and browse the switch, optical transport network (OTN), and passive optical network (PON). Browse the switch, OTN, and PON respectively to view their relevant information.

[0133] The device management system interface also provides resource management functions, including:

[0134] (1) For the management of device views, the operation interface of the network element list can be used to achieve: expand / contract the network element list (the network element list can be expanded or contracted for easy viewing), search for network elements (search for required network elements according to specific conditions), add groups / network elements (add new groups or network elements to the system), delete groups / network elements (delete unnecessary groups or network elements) and modify groups / network elements (modify existing group or network element information). The map operation can be implemented: edit (edit relevant information), save view (save the current view settings for subsequent use), switch maps (switch between different map views) and locate (locate specific devices). The alarm interface can be implemented: filter alarms (filter relevant alarm information according to conditions) and view alarms (view alarm information generated in the system), events (log records of various operations during the device management process). The resource operation interface includes: view resources (view various resource information in the system) and filter resources (filter resources according to specific conditions). Finally, fiber connection operations can also be performed (mainly involving fiber connection related operations and management).

[0135] (2) Management of equipment upgrades, providing management of network element or device versions, including: adding network element or device versions (adding new network element or device version information to the system), deleting network element or device versions (deleting unnecessary network element or device versions), refreshing version information (updating version information to obtain the latest data), and viewing network element or device versions (viewing existing network element or device versions). In addition, a more intuitive network element or device list is provided, including: viewing the network element or device list (viewing the list of all network elements or devices in the system), upgrading network elements or devices (upgrading specified network elements or devices), and refreshing network element or device information (updating network element or device information to obtain the latest data).

[0136] (3) The function of managing the database provides management of database files, including: adding data files (adding new data files to the database) and deleting data files (deleting unnecessary data files). In addition, it provides management of network elements or devices, including: selecting network element / device data (selecting the required network element or device data from a large number of data) and backing up network element / device data (backing up important network element or device data).

[0137] The system also provides business management functions, including:

[0138] Optical Transport Network (OTN) services and Switch services involve operations and management related to OTN and Switch services, respectively.

[0139] Furthermore, in addition to providing management of various devices and network elements, this embodiment also provides Figure 5 The device monitoring and maintenance interface shown:

[0140] The device management system of this embodiment also provides monitoring functions, including:

[0141] (1) Alarm monitoring can be used to view alarms or historical alarms (used to view current or past alarm information to help operation and maintenance personnel promptly understand problems or abnormal situations in the system) and clear alarms or historical alarms (after handling the corresponding alarm problem, this function can be used to clear the resolved alarms or historical alarm records to keep the alarm information neat and real-time).

[0142] (2) The performance monitoring function can realize monitoring point management: viewing performance monitoring points (you can view the relevant information of the performance monitoring points set in the system, such as location, monitored indicators, etc.), searching performance monitoring points (quickly searching for specific performance monitoring points through keywords, etc.) and enabling performance monitoring points (turning on or off the monitoring function of specific performance monitoring points to flexibly control the monitoring scope and resource usage). It can also realize performance data management: searching performance data (used to search and locate the required performance data, such as bandwidth utilization and packet loss rate within a specific time period) and viewing performance trend charts (displaying the performance trend in the form of charts). The system can also display performance data trends over time, facilitating analysis of performance change patterns and prediction of potential problems. Furthermore, it can implement threshold management, including viewing thresholds (viewing the set thresholds for various performance indicators, such as CPU usage exceeding 80%), filtering thresholds (filtering relevant thresholds based on specific conditions for viewing or management), editing thresholds (modifying and adjusting existing thresholds to suit different operating environments and requirements), and clearing TCA alarms (when a threshold-based performance alarm, such as a TCA alarm, occurs and the problem is resolved, this function can be used to clear the corresponding alarm).

[0143] (3) For the subscription function that needs to detect performance, monitoring group management can be realized: creating a new monitoring group (a new monitoring group can be created to group and manage related performance monitoring points and other resources for unified viewing and configuration) and deleting a monitoring group (deleting a monitoring group that is no longer needed), receiving group management: creating a new receiving group (creating a new receiving group to specify which users or system modules receive specific alarms or performance data and other information) and deleting a receiving group (deleting useless receiving groups), subscription: creating a new subscription (a new performance data subscription can be created to obtain relevant performance data regularly according to specific needs), deleting a subscription (deleting an existing performance data subscription) and entering text (can be used to enter text descriptions or conditions related to performance subscriptions, etc.).

[0144] In addition, the system provides maintenance functions, including:

[0145] (1) Link measurement function (used to measure the performance of links in the system, such as link bandwidth, delay, and other indicators, to evaluate link quality and performance);

[0146] (2) Automated playbook operation function (some routine maintenance operations can be performed through predefined automated scripts or playbooks to improve maintenance efficiency and accuracy);

[0147] (3) Command line interface (CLI) configuration function (performing system-related configuration operations through the command line interface, such as network interface configuration, routing configuration, etc.).

[0148] This embodiment uses the above-mentioned solution to specifically determine the device to be displayed based on the device visualization request; based on the device to be displayed, perform data query through the network planner to obtain the operating data and configuration parameters of the displayed device; based on the operating data and configuration parameters, perform device information display through the front-end platform to obtain the display result. As a result, after receiving the device information of the newly added network device, the device management system integrates the newly added network device into the pre-built network planner based on the device information. Subsequently, when receiving the device visualization request, the device information is displayed through the network planner and the front-end platform to obtain the display result. This solves the problem that various types of devices cannot be integrated into the same management system, resulting in the inability to efficiently display device information to management personnel for viewing, thereby improving the efficiency of device information display.

[0149] For example, in order to help understand the implementation process of the device information display method obtained by combining this embodiment with the above embodiment 1, please refer to Figure 6 , Figure 6 A system architecture diagram of a device information display method is provided, specifically:

[0150] The system of this embodiment includes a front-end layer (Browser) that mainly uses technologies such as ElementUI, JavaScript, HTML, and Bootstrap to build a user interface and provide a friendly interactive experience.

[0151] There is also an interface layer, including a northbound interface, which provides SNMP and Restful interfaces for interacting with external systems to achieve functions such as information acquisition and control, remote notification via email, and timely sending system status, alarm and other information to relevant personnel. TACACS+ is also used for AAA (authentication, authorization, and billing) authentication to ensure system security and authority management.

[0152] In addition, there is a functional management layer, which includes:

[0153] (1) Operation and maintenance management: link measurement (used to measure and evaluate the performance of network links, etc.), Playbook (involving the management of some automated operation and maintenance scripts or processes), device upgrade (responsible for operations such as upgrading the software version of network devices), data backup (backing up important data to prevent data loss), CLI configuration (configuration management of the device's command line interface, CLI), and Dashboard view (providing a visual display interface for the overall system status, etc.).

[0154] (2) Service management: This includes management functions related to services such as OTN (Optical Transport Network), Switch, and PON (Passive Optical Network), which may involve service configuration and monitoring.

[0155] The system also has a basic management layer, including: security management (responsible for the system's security policy formulation, access control, etc.), log management (recording and managing various logs generated by system operation), alarm management (processing and displaying various alarm information generated by the system), topology management (managing network topology structure and providing a visual network topology view), performance management (monitoring and analyzing the performance of the system and network equipment) and licenses management (managing various licenses used by the system).

[0156] In addition to the northbound interface layer, there is also a southbound interface layer, which uses NetConf (used for interaction with network devices for configuration and other aspects), SSH (remote management and operation of devices through the SSH protocol) and SNMP (using the SNMP protocol to obtain information such as the status of network devices).

[0157] Furthermore, a data storage layer is obtained by using multiple data storage technologies such as MySQL, Redis, and MQ (message queue). MySQL is used to store structured data, Redis is used for caching, and MQ is used for messaging to meet different data storage and processing requirements.

[0158] Finally, there is the network device layer: including various network devices such as servers, switches, wireless devices, etc. These devices interact with the system through southbound interfaces, and the system manages and monitors them.

[0159] The architecture of this embodiment realizes comprehensive management of front-end display, interface interaction, function management, data storage and other aspects through layered design, which can effectively support the needs of network operation and maintenance and business management.

[0160] It should be noted that the above examples are only used to understand this application and do not constitute a limitation on the device information display method of this application. More simple transformations based on this technical concept are all within the scope of protection of this application.

[0161] This application also provides a device information display device, please refer to Figure 7 The device information display method is applied to a device management system, the device management system includes a front-end platform, and the device information display device includes:

[0162] Receiving module 10, used to receive device information of newly added network devices;

[0163] An integration module 20, configured to integrate the newly added network device into a pre-built network planner based on the device information;

[0164] The display module 30 is used to display device information based on the device visualization request through the network planner and the front-end platform to obtain a display result when a device visualization request is received.

[0165] The device information display device provided in this application, which utilizes the device information display method of the aforementioned embodiment, can resolve the technical issue of various types of equipment being unable to be integrated into the same management system, resulting in the inability to efficiently display device information to management personnel for review. Compared to the prior art, the beneficial effects of the device information display device provided in this application are the same as those of the device information display method provided in the aforementioned embodiment, and the other technical features of the device information display device are the same as those disclosed in the aforementioned embodiment method, and are not further described here.

[0166] The present application provides a device information display device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the device information display method in the above-mentioned embodiment one.

[0167] Reference below Figure 8 , which shows a schematic diagram of the structure of a device information display device suitable for implementing the embodiments of the present application. The device information display device in the embodiments of the present application may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), in-vehicle terminals (such as in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 8 The device information display device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0168] like Figure 8 As shown, the device information display device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes based on programs stored in a read-only memory 1002 or programs loaded from a storage device 1003 into a random access memory 1004. The random access memory 1004 also stores various programs and data required for the operation of the device information display device. The processing device 1001, the read-only memory 1002, and the random access memory 1004 are connected to each other via a bus 1005. An input / output interface 1006 is also connected to the bus. Typically, the following systems can be connected to the input / output interface 1006: an input device 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the device information display device to communicate with other devices wirelessly or wired to exchange data. Although the figure shows a device information display device with various systems, it should be understood that it is not required to implement or have all of the systems shown. More or fewer systems can be implemented or have alternatively.

[0169] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program comprising program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device 1003, or installed from a read-only memory 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are performed.

[0170] The device information display device provided in this application, using the device information display method in the above-described embodiment, can resolve the technical problem of various types of devices being unable to be integrated into the same management system, resulting in the inability to efficiently display device information to management personnel for review. Compared to the prior art, the beneficial effects of the device information display device provided in this application are the same as those of the device information display method provided in the above-described embodiment, and the other technical features of the device information display device are the same as those disclosed in the method in the previous embodiment, and are not further described here.

[0171] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0172] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

[0173] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, a computer program) stored thereon, wherein the computer-readable program instructions are used to execute the device information display method in the above-mentioned embodiment.

[0174] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0175] The computer-readable storage medium may be included in the device information display device, or may exist independently without being assembled into the device information display device.

[0176] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the device information display device, the device information display device: receives device information of a newly added network device; integrates the newly added network device into a pre-built network planner based on the device information; and, upon receiving a device visualization request, displays the device information through the network planner and the front-end platform based on the device visualization request to obtain a display result.

[0177] Computer program code for performing the operations of the present application may be written in one or more programming languages, or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0178] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, program segment or a part of code, and the module, program segment or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented by a dedicated hardware-based system that performs the specified function or operation, or can be implemented by a combination of dedicated hardware and computer instructions.

[0179] The modules described in the embodiments of the present application may be implemented in software or hardware, wherein the name of a module does not necessarily limit the unit itself.

[0180] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described device information display method. This computer-readable storage medium can resolve the technical problem that various types of devices cannot be integrated into the same management system, resulting in the inability to efficiently display device information to management personnel for review. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the device information display method provided in the above-described embodiment, and are not further elaborated here.

[0181] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned device information display method when executed by a processor.

[0182] The computer program product provided in this application can resolve the technical problem of various types of devices being unable to be integrated into a single management system, resulting in an inefficient display of device information for management personnel. Compared to the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the device information display method provided in the aforementioned embodiment, and are not further elaborated here.

[0183] The above description is only part of the embodiments of the present application and does not limit the patent scope of the present application. All equivalent structural transformations made by using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect application in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A device information display method, characterized in that: The device information display method is applied to a device management system, which includes a front-end platform. The device information display method includes: Receive device information of newly added network devices; Integrating the newly added network device into a pre-built network planner based on the device information; When a device visualization request is received, device information is displayed based on the device visualization request through the network planner and the front-end platform to obtain a display result.

2. The device information display method according to claim 1, wherein: Before the step of receiving device information of a newly added network device, the method further includes: Collect network equipment operation and maintenance information; Based on the network equipment operation and maintenance information, containerized segmentation is performed through containerized applications to obtain a microservice architecture; Based on the microservice architecture, control and management are separated to obtain a management platform and a control platform; An initial user interface library is constructed based on the network device operation and maintenance information, and a service interaction working mode is established through the network device operation and maintenance information and the initial user interface library; Collecting performance indicators of the equipment management system through a telemetry platform, and constructing a performance prediction component based on the performance indicators and a performance prediction algorithm; According to the management platform, control platform, service interaction working mode and performance prediction components, a network planner is constructed by using a network performance modeling tool.

3. The device information display method according to claim 2, wherein: The step of integrating the newly added network device into a pre-built network planner based on the device information includes: Parsing the device information to obtain the device type and device parameters of the newly added network device; Determining the service configuration logic of the newly added network device based on the device type and device parameters; Integrate the newly added devices into the microservice architecture according to the business configuration logic to obtain a final microservice architecture; Optimize the business interaction working mode, management platform, control platform, and performance prediction component according to the final microservice architecture to obtain optimization results; When the optimization result indicates that the optimization is completed, performing performance verification on the network planner to obtain a verification result; If the verification result is that the verification is passed, the integration result is that the integration is successful.

4. The device information display method according to claim 2, wherein: After the step of integrating the newly added network device into a pre-built network planner based on the device information, the method further includes: Performing performance evaluation on the newly added network equipment by the network planner to obtain performance parameters of the newly added network equipment; According to the performance parameters, rule configuration is performed through the performance prediction component to obtain alarm rules; Based on the alarm rules, the management platform performs alarm detection on the newly added network device, and generates an alarm record when the newly added network device triggers an alarm.

5. The device information display method according to claim 1, wherein: The step of displaying device information based on the device visualization request through the network planner and the front-end platform to obtain a display result includes: Determining a device to be displayed based on the device visualization request; According to the device to be displayed, data query is performed through the network planner to obtain the operating data and configuration parameters of the display device; Based on the operating data and configuration parameters, device information is displayed through the front-end platform to obtain a display result.

6. The device information display method according to claim 5, wherein: The step of displaying device information based on the operating data and configuration parameters through the front-end platform to obtain a display result includes: Converting the operating data and configuration parameters into rendering data through the front-end platform; Perform visual rendering based on the rendering data through the data binding mechanism of the front-end platform to obtain a rendering interface; The device information is displayed through the rendering interface to obtain a display result.

7. A device information display device, characterized in that: The device information display method is applied to a device management system, wherein the device management system includes a front-end platform, and the device information display device includes: A receiving module, used to receive device information of newly added network devices; An integration module, configured to integrate the newly added network device into a pre-built network planner based on the device information; The display module is used to display device information based on the device visualization request through the network planner and the front-end platform to obtain a display result when a device visualization request is received.

8. A device information display device, characterized in that: The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the device information display method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the device information display method according to any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product includes a computer program, and when the computer program is executed by a processor, the steps of the device information display method according to any one of claims 1 to 6 are implemented.

Citation Information

Patent Citations

  • Cross-device and cross-protocol EPON element management system

    CN104079436A

  • Method and device for standardizing network equipment configuration

    CN112737852A

  • Multi-platform unified cloud management system supporting global setting of application resource quotas of tenants

    CN116055283A