A data-driven network topology dynamic display method

Abstract

The application discloses a data-driven network topology dynamic display method, which comprises the following steps: drawing a machine box frame according to the physical characteristics of a voice service machine box; obtaining a board card information list of the voice service machine box, and drawing board cards on the slots of the machine box according to the board card information list data; obtaining a channel device information list, and drawing channel device nodes according to the channel device information list data; connecting the interface nodes in all the board card nodes with the channel device nodes, and forming a network topology. The application can dynamically and timely display the connection relationship between the board card interfaces of the voice service machine box and the channel device network topology, the board card state and the channel device state, and can dynamically update the connection relationship and the device state on the network topology diagram according to the rear-end data, so that the user can obtain the device network topology relationship and the device state.

Description

Technical Field

[0001] This invention relates to the field of network management technology for communication system equipment, and in particular to a data-driven method for dynamically displaying network topology. Background Technology

[0002] The voice communication system consists of voice service cabinets, channel equipment, telephones, etc. The voice network management system needs to manage and configure the parameters and status of all devices in the voice communication system. For channel equipment management, the system can display information such as channel equipment number, channel unit type, channel unit address, channel equipment name, affiliated private network, subnet, connected card slot number, interface number, device status, service status, and alarm status in a tabular format. Channel equipment can be added through the network management interface. For voice service cabinet management, the system can display information such as card name, slot number, card status, and interface list for all cards in the cabinet in a tabular format. Card parameters can be modified through the network management interface.

[0003] Existing tabular displays and parameter modifications provide a static representation, making it difficult for users to easily and intuitively obtain an overall framework diagram of the connection relationship between voice service chassis card interfaces and channel equipment, or to dynamically update and monitor the connection relationship between the card interfaces and equipment. Therefore, there is an urgent need to research a dynamic network topology display and modification method that can dynamically and in real-time display the network topology connection relationship between voice service chassis card interfaces and channel equipment, and dynamically update the connection relationship and device status on the network topology diagram based on backend data, enabling a systematic, intuitive, and dynamic display and modification of the device network topology relationship and device status. Summary of the Invention

[0004] The purpose of this invention is to provide a network topology display method that can systematically, intuitively, dynamically, and in real-time display the network topology, board status, and channel device status of voice chassis board interface nodes and channel devices.

[0005] The technical solution to achieve the purpose of this invention is: a data-driven method for dynamically displaying network topology, comprising the following steps: Step 1: Draw the chassis frame based on the physical characteristics of the voice service chassis; Step 2: Obtain the list of board information for the voice service chassis; Step 3: Draw the boards in the chassis slots based on the board information list data; Step 4: Obtain the list of channel device information; Step 5: Draw the channel device nodes based on the channel device information list data; Step 6: Connect the interface nodes and channel device nodes in all the board nodes to form a network topology.

[0006] Compared with the prior art, the present invention has the following significant advantages: (1) The present invention can dynamically and in real time display the network topology connection relationship between the voice service chassis board interface and the channel equipment, and can dynamically update the connection relationship and the status of the equipment on the network topology map according to the backend data; (2) It can display the board status and the channel equipment status in real time, which makes it convenient for users to obtain the network topology relationship and the status of the equipment in the voice communication system. Attached Figure Description

[0007] Figure 1 This is a flowchart illustrating a data-driven method for dynamically displaying network topology according to the present invention.

[0008] Figure 2 This is a structural framework diagram of the voice service chassis in this invention.

[0009] Figure 3 This is a structural framework diagram of the voice service chassis board in this invention.

[0010] Figure 4 This is a flowchart illustrating the drawing process of the voice service chassis board in this invention.

[0011] Figure 5 This is a dynamic display diagram of the network topology after the voice service chassis board interface and channel equipment are connected in this invention. Detailed Implementation

[0012] A data-driven method for dynamically displaying network topology includes the following steps: Step 1: Draw the chassis frame based on the physical characteristics of the voice service chassis; Step 2: Obtain the list of board information for the voice service chassis; Step 3: Draw the boards in the chassis slots based on the board information list data; Step 4: Obtain the list of channel device information; Step 5: Draw the channel device nodes based on the channel device information list data; Step 6: Connect the interface nodes and channel device nodes in all the board nodes to form a network topology.

[0013] Furthermore, the step 1, which involves drawing the chassis frame based on the physical characteristics of the voice service chassis, is as follows: Using jtopo technology, the chassis frame is drawn based on the physical characteristics of the voice service chassis, namely the number of slots customized at the factory, including the chassis name and the slots inside the chassis.

[0014] Furthermore, the process of obtaining the list of board information for the voice service chassis in step 2 is as follows: The system uses axios technology to send network requests to the backend to obtain a list of board information for the chassis. This list represents the actual board information installed in the chassis during its operational use. The functions and quantities of the service boards installed in the chassis vary depending on the application scenario, therefore the board information list needs to be dynamically retrieved from the backend. The board information in the chassis's board information list includes the board name, the slot number (slot_id), the board status, and a list of interfaces on the board. The interface information in the list of interfaces on the board includes the interface number (interface_id), the channel device number (cu_id) connected to the interface, the interface name, and the connection status.

[0015] Furthermore, the list of board information obtained from the backend is dynamically variable. Based on this real-time board information list, the network topology is dynamically drawn, and the board status and channel device status are dynamically displayed.

[0016] Furthermore, step 3, which involves drawing the boards on the chassis slots based on the board information list data, includes drawing the board names and drawing the board interfaces.

[0017] Furthermore, the name of the drawing board is as follows: Iterate through all chassis slots to draw. For each slot number (slot_id), search for the board information for that slot in the chassis board information list. If no board information is found for that slot, do not draw the board for that slot. If the board information is found, draw the found board node in that slot, save the slot number (slot_id) to the board node object, draw the name of the board from the board information list onto the board frame, and then add the drawn board node object to the global variable board node list.

[0018] Furthermore, the drawing board interface is specifically as follows: Iterate through the global variable board node list. For each board node object, search for the board information for that slot in the chassis board information list based on the recorded slot number (slot_id) to obtain the interface list. Iterate through the interface list and draw the interface node of the board based on the interface information in the interface list. Record the interface information, including the interface number (interface_id) and the channel device number (cu_id) connected to the interface, into the interface node. Then draw the interface node onto the board and add the interface node to the interface node list. Finally, save the interface node list into the board node list.

[0019] Furthermore, the acquisition of the channel device information list in step 4 is as follows: The axios technology is used to send network requests to the backend to obtain the channel device information connected to the chassis board interface. The channel device information in the channel device list includes the channel device number cu_id, device type, device name, subnet where the device is located, device status, slot number (slot_id) of the board connected to this channel device, and physical interface number (interface_id) on the board connected to this channel device.

[0020] Furthermore, step 5, which involves drawing the channel device nodes based on the channel device information list data, is as follows: The channel device nodes are drawn based on the channel device information list data. This includes drawing the device name and device status of the channel device nodes. First, the device name node is drawn into the device node frame. Then, different background colors of the device nodes are used to represent the device status. Finally, the device nodes are saved to the global variable device node list.

[0021] Furthermore, step 6 involves connecting the interface nodes and channel device nodes in all the board nodes to form a network topology, as detailed below: Iterate through the global variable list of chassis board nodes, then iterate through the list of interface nodes for adding attributes to the board nodes. For each interface node in the list of interface nodes, find the corresponding channel device in the global variable list of device nodes based on the device number cu_id of the channel device stored in the interface node, and connect the interface node to the channel device node.

[0022] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. Example

[0023] Combination Figure 1 This embodiment of a data-driven method for dynamically displaying network topology includes the following steps: Step 1: Draw the chassis frame based on the physical characteristics of the voice service chassis, as follows: Using jtopo technology, the chassis frame is drawn based on the physical characteristics of the voice service chassis, i.e., the number of slots customized at the factory. This includes the chassis name and the slots within the chassis, such as... Figure 2 As shown.

[0024] Step 2: Obtain the list of board information for the voice service chassis, as follows: The system uses axios technology to send network requests to the backend to obtain a list of board information for the chassis. This list represents the actual board information installed in the chassis for a specific work scenario. The functions and quantities of the service boards installed in the chassis differ across application scenarios, therefore the board information list needs to be dynamically retrieved from the backend. The board information in the chassis's board information list includes the board name, the slot number (slot_id), the board status, and a list of interfaces on the board. The interface information in the list of interfaces on the board includes the interface number (interface_id), the channel device number (cu_id) connected to the interface, the interface name, and the connection status.

[0025] The list of board information obtained from the backend is dynamic and variable. Based on this real-time board information list, the network topology is dynamically drawn, and the board status and channel device status are dynamically displayed.

[0026] Step 3: Draw the boards in the chassis slots based on the board information list data, including drawing the board names and interfaces, such as... Figure 3 As shown, the specific implementation is as follows: The names of the drawing boards are as follows: Iterate through all chassis slots to draw. For each slot_id, search for the board information for that slot in the chassis board information list. If no board information is found for that slot, do not draw the board for that slot. If the board information is found for that slot, draw the found board node in that slot, save the slot number (slot_id) to the board node object, draw the name of the board from the board information list onto the board frame, and then add the drawn board node object to the global variable board node list.

[0027] The drawing board interface is as follows: The process iterates through the global variable list of board nodes. For each board node object, it searches for the board information for that slot in the chassis board information list based on the recorded slot number (slot_id), obtaining its interface list. It then iterates through this interface list, drawing the board's interface node based on the interface information in the list. The interface information, including the interface number (interface_id) and the channel device number (cu_id) connected to the interface, is recorded in the interface node. Next, the interface node is drawn onto the board, added to the interface node list, and finally, the interface node list is saved back to the board node list. The specific process is as follows: Figure 4 As shown.

[0028] Step 4: Obtain the list of channel device information, as follows: The axios technology is used to send network requests to the backend to obtain the channel device information connected to the chassis board interface. The channel device information in the channel device list includes the channel device number cu_id, device type, device name, subnet where the device is located, device status, slot number (slot_id) of the board connected to this channel device, and physical interface number (interface_id) on the board connected to this channel device.

[0029] Step 5: Draw the channel device nodes based on the channel device information list data, as follows: The channel device nodes are drawn based on the channel device information list data. This includes drawing the device name and device status of the channel device nodes. First, the device name node is drawn into the device node frame. Then, different background colors of the device nodes are used to represent the device status. Finally, the device nodes are saved to the global variable device node list.

[0030] Step 6: Connect the interface nodes and channel device nodes in all the board nodes to form the network topology, as follows: Iterate through the global variable list of chassis board nodes, then iterate through the list of interface nodes for adding attributes to the board nodes. For each interface node in the interface node list, find the corresponding channel device in the global variable list of device nodes based on the device number (cu_id) of the channel device stored in the interface node, and connect the interface node to the channel device node. Figure 5 As shown, the total number of chassis slots is fixed, the number of boards that can be inserted into the chassis slots is variable, the number of interfaces of different boards is variable, and the channel devices connected to each board are dynamically variable. In addition, this diagram can also dynamically display the board status and channel device status, and can dynamically display the background color of the board or device based on the status data of the backend device.

[0031] This invention provides a data-driven method for dynamically displaying network topology, ensuring the dynamic realization of the network topology between voice chassis board interface nodes and channel devices, as well as the dynamic real-time updating and display of board status and channel device status.

[0032] The above are merely preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A data-driven method for dynamically displaying network topology, characterized in that, Includes the following steps: Step 1: Draw the chassis frame based on the physical characteristics of the voice service chassis; Step 2: Obtain the list of board information for the voice service chassis; Step 3: Draw the boards in the chassis slots based on the board information list data; Step 4: Obtain the list of channel device information; Step 5: Draw the channel device nodes based on the channel device information list data; Step 6: Connect the interface nodes and channel device nodes in all the board nodes to form the network topology; Step 1 involves drawing the chassis frame based on the physical characteristics of the voice service chassis, as detailed below: Using jtopo technology, the chassis frame is drawn based on the physical characteristics of the voice service chassis, namely the number of slots customized at the factory, including the chassis name and the slots inside the chassis; Step 2, which involves obtaining the list of board information for the voice service chassis, is detailed below: The axios technology is used to send network requests to the backend to obtain the list of board information of the chassis. The list of board information is a list of the actual boards inserted in the chassis when it is used in the working scenario. In different application scenarios, the functions and number of service boards inserted in the chassis are different. Therefore, it is necessary to dynamically obtain the list of board information of the chassis from the backend. The board information list of the chassis includes the board name, the slot number (slot_id) where the board is located, the board status, and the interface list on the board; the interface information in the interface list on the board includes the interface number (interface_id), the channel device number (cu_id) connected to the interface, the interface name, and the connection status. The list of board information obtained from the backend is dynamic and variable. Based on this real-time board information list, the network topology is dynamically drawn, and the board status and channel device status are dynamically displayed. Step 3 involves drawing the boards on the chassis slots based on the board information list data, including drawing the board name and drawing the board interface; The names of the drawing boards are as follows: Iterate through all the chassis slots to be drawn. For each slot number (slot_id), search for the board information for that slot in the chassis board information list. If the board information for that slot is not found, then the board for that slot is not drawn. If the board information for the slot is found, the found board node is drawn in the slot, the slot number slot_id is saved to the board node object, the name of the board from the board information list is drawn into the board frame, and then the drawn board node object is added to the global variable board node list. The drawing board interface is as follows: Iterate through the global variable board node list. For each board node object, search for the board information of the slot in the chassis board information list based on the recorded slot number (slot_id) to obtain the interface list. Iterate through the interface list and draw the interface node of the board based on the interface information in the interface list. Record the interface information, including the interface number (interface_id) and the channel device number (cu_id) connected to the interface, into the interface node. Then draw the interface node onto the board and add the interface node to the interface node list. Finally, save the interface node list into the board node list. Step 4, which involves obtaining the list of channel device information, is as follows: The axios technology is used to send network requests to the backend to obtain the channel device information connected to the chassis board interface. The channel device information in the channel device list includes the channel device number cu_id, device type, device name, subnet where the device is located, device status, slot number of the board connected to this channel device slot_id, and physical interface number interface_id on the board connected to this channel device. Step 5, which involves drawing the channel device nodes based on the channel device information list data, is as follows: The channel device nodes are drawn based on the channel device information list data, including drawing the device name and device status of the channel device nodes. First, the device name node is drawn into the device node frame, then the device status is represented by different background colors of the device nodes, and finally the device nodes are saved to the global variable device node list. Step 6 involves connecting the interface nodes and channel device nodes in all the board nodes to form a network topology, as detailed below: Iterate through the global variable list of chassis board nodes, then iterate through the list of interface nodes for adding attributes to the board nodes. For each interface node in the list of interface nodes, find the corresponding channel device in the global variable list of device nodes based on the device number cu_id of the channel device stored in the interface node, and connect the interface node to the channel device node.

Images