Equipment maintenance methods, systems, equipment and media for underground engineering networks

Abstract

This application provides a method, system, equipment, and medium for the operation and maintenance of equipment in underground engineering networks. By constructing a modular network architecture with one master and multiple slaves and a network operation and maintenance management software system, it achieves unified management, dynamic expansion, and proactive operation and maintenance of heterogeneous equipment in the underground engineering network. Specifically, the method includes: acquiring the equipment information set and network operation dataset of each device in the underground engineering network, wherein the underground engineering network adopts a modular network architecture with one master and multiple slaves; mapping the devices to logical resource entities based on the equipment information set; subsequently, generating a network topology diagram corresponding to the underground engineering network based on each logical resource entity; and finally, generating an equipment operation and maintenance diagram of the underground engineering network based on the network operation dataset and the network topology diagram. This method aims to improve the efficiency of equipment operation and maintenance in underground engineering networks.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, system, equipment and medium for the operation and maintenance of underground engineering networks. Background Technology

[0002] In underground engineering construction scenarios such as tunnels, the supporting networks are generally characterized by wide coverage, dispersed node deployment, and complex equipment types due to the narrow and enclosed space environment. These networks include various communication devices such as switches, routers, and wireless base stations.

[0003] Currently, underground engineering networks often connect to heterogeneous devices from different manufacturers. Due to significant differences in the communication protocols of devices from different manufacturers, maintenance personnel need to perform differentiated operations for different devices. At the same time, basic equipment information relies on manual registration ledgers.

[0004] Currently, the overall operation and maintenance mode of underground engineering networks is still mainly based on manual inspection and decentralized management. This not only makes it difficult to cope with the complex management needs of heterogeneous equipment, but also fails to achieve global awareness of network status and rapid fault handling, resulting in low efficiency in the operation and maintenance management of underground engineering networks. Summary of the Invention

[0005] This application provides a method, system, equipment, and medium for the operation and maintenance of equipment in underground engineering networks, in order to improve the efficiency of equipment operation and maintenance in underground engineering networks.

[0006] In a first aspect, embodiments of this application provide a method for the operation and maintenance of equipment in an underground engineering network. This underground engineering network adopts a modular network architecture with one master and multiple slave stations. The master station is communicatively connected to the first slave station, each slave station is communicatively connected to its adjacent slave station, and each slave station is connected to multiple devices. The method is applied to the master station and includes:

[0007] Obtain the equipment information set and network operation dataset of each device in the underground engineering network.

[0008] Based on the device information set, the device is mapped to a logical resource entity.

[0009] Generate a network topology diagram corresponding to the underground engineering network based on each logical resource entity.

[0010] Based on the network operation dataset and network topology diagram, an equipment operation and maintenance diagram of the underground engineering network is generated; the equipment operation and maintenance diagram represents the connection relationship between equipment and the real-time operation status of the underground engineering network.

[0011] In one possible implementation, in conjunction with the first aspect, a device operation and maintenance diagram of the underground engineering network is generated based on the network operation dataset and the network topology diagram, including:

[0012] Based on the network operation dataset, determine the security status of each logical resource entity in the network topology diagram; the security status represents the fault status of the device.

[0013] Based on the security status, network operation dataset, and network topology diagram, generate an equipment operation and maintenance diagram for the underground engineering network.

[0014] In one possible implementation, after generating the network topology diagram corresponding to the underground engineering network based on each logical resource entity, in conjunction with the first aspect, the method further includes:

[0015] Newly added network nodes can be identified by real-time monitoring of network node interaction data in the underground engineering network.

[0016] Update the network topology based on the newly added network nodes.

[0017] In one possible implementation, in conjunction with the first aspect, updating the network topology based on the addition of network nodes includes:

[0018] Obtain the device identification information of the newly added network node.

[0019] Based on the device identification information, the virtual digital model of the newly added network node is matched from the preset virtual digital model library.

[0020] New network nodes are registered and added to the network based on device identification information and virtual digital models of the devices.

[0021] Update the network topology based on newly added network nodes after registration.

[0022] In one possible implementation, after generating an equipment maintenance diagram of the underground engineering network based on the security status, network operation dataset, and network topology diagram, in conjunction with the first aspect, the method further includes:

[0023] Determine the alarm level based on the security status of the logical resource entity.

[0024] When the alarm level meets the preset alarm conditions, the corresponding alarm notification operation is executed according to the alarm level.

[0025] In one possible implementation, in conjunction with the first aspect, acquiring the equipment information set and network operation dataset of each device in the underground engineering network includes:

[0026] The system uses a multi-protocol acquisition engine to obtain raw equipment information and operational status data of each device in the underground engineering network.

[0027] The original equipment information is standardized to obtain the equipment information set.

[0028] The operational status data is standardized to obtain the network operational dataset.

[0029] In one possible implementation, in conjunction with the first aspect, the method further includes:

[0030] Obtain sample data for operation and maintenance analysis of underground engineering networks.

[0031] An operation and maintenance prediction model is constructed based on operation and maintenance analysis sample data.

[0032] Input the network topology diagram and network operation dataset into the operation and maintenance prediction model to generate proactive operation and maintenance strategies.

[0033] Secondly, this application provides an equipment operation and maintenance system for an underground engineering network. The underground engineering network adopts a modular network architecture with one master and multiple slaves, consisting of a master station and multiple slave stations. The master station is communicatively connected to the first slave station, each slave station is communicatively connected to its adjacent slave station, and each slave station is connected to multiple devices. The system is deployed at the master station and includes at least a data acquisition and processing engine module, a network operation overview module, and a network topology overview module.

[0034] The data acquisition and processing engine module is used to acquire equipment information sets and network operation datasets for each device in the underground engineering network.

[0035] The network operation overview module is used to map devices to logical resource entities based on the device information set; and to generate a network topology diagram corresponding to the underground engineering network based on each logical resource entity.

[0036] The network topology overview module is used to generate an equipment operation and maintenance diagram of the underground engineering network based on the network operation dataset and network topology diagram. The equipment operation and maintenance diagram represents the connection relationship between devices and the real-time operating status of the underground engineering network.

[0037] In one possible implementation, in conjunction with the second aspect, the network topology overview module is specifically used for:

[0038] Based on the network operation dataset, determine the security status of each logical resource entity in the network topology diagram; the security status represents the fault status of the device.

[0039] Based on the security status, network operation dataset, and network topology diagram, generate an equipment operation and maintenance diagram for the underground engineering network.

[0040] In one possible implementation, in conjunction with the second aspect, the system also includes an equipment information management module for identifying newly added network nodes by real-time monitoring of network node interaction data in the underground engineering network.

[0041] Correspondingly, the network operation overview module is also used to update the network topology map based on newly added network nodes.

[0042] In one possible implementation, in conjunction with the second aspect, the equipment information management module is specifically used for:

[0043] Obtain the device identification information of the newly added network node.

[0044] Based on the device identification information, the virtual digital model of the newly added network node is matched from the preset virtual digital model library.

[0045] New network nodes are registered and added to the network based on device identification information and virtual digital models of the devices.

[0046] Correspondingly, the network operation overview module is also used to update the network topology map based on newly added network nodes after registration and joining the network.

[0047] In one possible implementation, in conjunction with the second aspect, the system further includes an alarm information management module, which is used to determine the alarm level based on the security status of the logical resource entity; and when the alarm level meets the preset alarm conditions, to perform the corresponding alarm notification operation based on the alarm level.

[0048] In one possible implementation, in conjunction with the second aspect, the data acquisition and processing engine module is specifically used for:

[0049] The system uses a multi-protocol acquisition engine to obtain raw equipment information and operational status data of each device in the underground engineering network.

[0050] The original equipment information is standardized to obtain the equipment information set.

[0051] The operational status data is standardized to obtain the network operational dataset.

[0052] In one possible implementation, in conjunction with the second aspect, the system further includes a fault knowledge base module for acquiring operation and maintenance analysis sample data of the underground engineering network; constructing an operation and maintenance prediction model based on the operation and maintenance analysis sample data; and inputting the network topology diagram and network operation dataset into the operation and maintenance prediction model to generate proactive operation and maintenance strategies.

[0053] Thirdly, embodiments of this application provide an electronic device, including: a processor, and a memory communicatively connected to the processor.

[0054] The memory stores the instructions that the computer executes.

[0055] The processor executes computer execution instructions stored in memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0056] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0057] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0058] This application provides a method, system, equipment, and medium for the operation and maintenance of equipment in an underground engineering network. The underground engineering network adopts a modular network architecture with one master and multiple slave stations. The master station communicates with the first slave station, each slave station communicates with its adjacent slave station, and each slave station connects to multiple devices. By acquiring the device information set and network operation dataset of each device in the underground engineering network, and mapping the devices to logical resource entities based on the device information set, a network topology diagram corresponding to the underground engineering network is generated based on each logical resource entity. This hides the differences between devices from multiple vendors at the logical layer, reducing the complexity of heterogeneous device management. Finally, based on the network operation dataset and network topology diagram, an equipment operation and maintenance diagram of the underground engineering network is generated. This diagram allows maintenance personnel to centrally monitor all network devices in a unified interface, thereby improving the efficiency of equipment operation and maintenance in the underground engineering network. Attached Figure Description

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

[0060] Figure 1 A schematic diagram illustrating a scenario for an equipment operation and maintenance method for an underground engineering network provided in this application;

[0061] Figure 2 A flowchart illustrating an equipment operation and maintenance method for an underground engineering network provided in this application. Figure 1 ;

[0062] Figure 3 A flowchart illustrating an equipment operation and maintenance method for an underground engineering network provided in this application. Figure 2 ;

[0063] Figure 4 A flowchart illustrating an equipment operation and maintenance method for an underground engineering network provided in this application. Figure 3 ;

[0064] Figure 5 A specific example diagram illustrating a method for the operation and maintenance of equipment in an underground engineering network provided in this application;

[0065] Figure 6 A schematic diagram of the functional modules of the network operation and maintenance management software system provided in this application;

[0066] Figure 7 A schematic diagram of the access configuration for the newly added network nodes provided in this application;

[0067] Figure 8 This application provides an architectural diagram of a network device operation and maintenance management system.

[0068] Figure 9 A schematic diagram of the equipment operation and maintenance system for an underground engineering network provided in this application;

[0069] Figure 10 A schematic diagram of the structure of the electronic device provided in this application.

[0070] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0071] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of systems and methods consistent with some aspects of this application as detailed in the appended claims.

[0072] First, the terms used in this application will be explained:

[0073] Master station: refers to the device that acts as the core control node, integrating core network equipment (such as switches and servers) and computing resources, and is used to aggregate and manage the data and resources of slave stations.

[0074] Slave station: refers to a standardized access unit deployed in a distributed manner, used to provide terminal access, regional wireless coverage and regional power supply functions.

[0075] Secondly, the application background of the embodiments of this application will be explained:

[0076] In underground engineering construction scenarios such as tunnels, the narrow and enclosed spatial environment necessitates networks characterized by wide coverage, dispersed node deployment, and diverse equipment types, encompassing various communication devices such as switches, routers, and wireless base stations. Currently, underground engineering networks often connect heterogeneous devices from different manufacturers. Due to significant differences in communication protocols among these manufacturers, maintenance personnel must perform differentiated operations for each device. Furthermore, basic equipment information relies on manual record-keeping. The current overall operation and maintenance model for underground engineering networks remains primarily based on manual inspection and decentralized management. This not only struggles to address the complex management needs of heterogeneous equipment but also fails to achieve global network status awareness and rapid fault handling, resulting in low efficiency in the operation and maintenance management of underground engineering networks.

[0077] To address the aforementioned issues, the inventors propose a method for the operation and maintenance of equipment in underground engineering networks. This network employs a modular network architecture with one master and multiple slave stations. The master station communicates with the first slave station, each slave station communicates with its adjacent slave station, and each slave station connects to multiple devices. By acquiring device information sets and network operation datasets for each device in the underground engineering network, and mapping devices to logical resource entities based on the device information sets, a network topology diagram corresponding to the underground engineering network is generated based on each logical resource entity. This hides the differences between devices from multiple vendors at the logical layer, reducing the complexity of heterogeneous device management. Finally, based on the network operation dataset and network topology diagram, an equipment operation and maintenance diagram for the underground engineering network is generated. This diagram allows maintenance personnel to centrally monitor all network devices in a unified interface, thereby improving the efficiency of equipment operation and maintenance in underground engineering networks.

[0078] Taking network equipment operation and maintenance in tunnel construction scenarios as an example, combined with Figure 1 This illustrates the specific application scenarios of the equipment operation and maintenance method for underground engineering networks provided in this application. For example... Figure 1 As shown, the specific application scenario of this application includes a master station 101, multiple slave stations 102 and multiple devices 103. The master station 101 is connected to the first slave station 102 via an optical fiber link, and each slave station 102 is connected to its adjacent slave station 102 via an optical fiber link. The slave stations are distributed along the tunnel excavation direction toward the tunnel face. Each slave station 102 is connected to multiple devices 103 via wireless communication.

[0079] The main station 101 is deployed at the tunnel entrance or in a fixed equipment room outside the tunnel. It obtains equipment information sets and network operation datasets from each device 103 through the slave station 102, and generates an equipment operation and maintenance diagram based on the equipment information sets and network operation datasets. This equipment operation and maintenance diagram represents the connection relationship between devices 103 and the real-time operating status of the underground engineering network, and can be used for centralized monitoring of all devices 103 and rapid fault location.

[0080] The slave stations 102 are distributed along the tunnel excavation direction and adopt a standardized access unit design. When the construction face advances, the newly added slave stations 102 only need to be connected to the reserved optical ports to achieve seamless network expansion.

[0081] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0082] Figure 2 A flowchart illustrating an equipment operation and maintenance method for an underground engineering network provided in this application. Figure 1 The underground engineering network adopts a modular network architecture with one master and multiple slave stations. The master station communicates with the first slave station, each slave station communicates with its adjacent slave station, and each slave station connects to multiple devices. This method is applied to the master station, such as... Figure 2 As shown, it includes:

[0083] S201. Obtain the equipment information set and network operation dataset of each device in the underground engineering network. The underground engineering network adopts a modular network architecture with one master and multiple slaves.

[0084] Among them, the equipment information set is a collection of static basic attributes of each device in the underground engineering network. For example, it may include fixed core information such as the device's unique identifier, manufacturer model, IP address, port configuration, slave station level, and deployment location. It is the basic data for device identification and network topology construction.

[0085] The network operation dataset is a collection of dynamic time-series data generated by each device during operation, used for real-time monitoring, performance analysis, and fault diagnosis.

[0086] In this step, a multi-protocol acquisition engine is used to acquire raw device information and operational status data of each device in the underground engineering network. The raw device information is then standardized to obtain a device information set; and the operational status data is standardized to obtain a network operation dataset. The multi-protocol acquisition engine is a data acquisition module that supports multiple industrial protocols; the operational status data includes CPU utilization, memory usage, port traffic, packet loss rate, and other key performance indicators.

[0087] In one possible implementation, a multi-protocol acquisition engine is used to collect real-time device operating status data. This engine supports multiple protocols, including Simple Network Management Protocol (SNMP), Message Queuing Telemetry Transport (MQTT), and Modbus Transmission Control Protocol (Modbus TCP). The operating status data is then parsed and cleaned, and converted into standardized data in a unified format to generate a network operating dataset.

[0088] S202. Based on the device information set, map the device to a logical resource entity.

[0089] In this step, based on the device information set, we first construct the identity tags and attribute tags of logical resource entities, then construct the topological association relationships between each logical resource entity, and finally integrate the above identity tags, attribute tags and topological association relationships into a complete logical resource entity.

[0090] S203. Generate a network topology diagram corresponding to the underground engineering network based on each logical resource entity.

[0091] In this step, the hierarchical network relationship between logical resource entities is determined by parsing the topological association between them, and a three-level network logical skeleton adapted to the underground engineering scenario is constructed. Then, the identity tags and attribute tags of each logical resource entity are combined for visualization mapping to generate the network topology diagram corresponding to the underground engineering network.

[0092] S204. Based on the network operation dataset and network topology diagram, generate the equipment operation and maintenance diagram of the underground engineering network.

[0093] In this step, the security status of each logical resource entity in the network topology diagram is determined based on the network operation dataset. Then, based on the security status, the network operation dataset, and the network topology diagram, an equipment operation and maintenance diagram of the underground engineering network is generated. The security status represents the fault state of the equipment, while the equipment operation and maintenance diagram represents the connection relationships between the equipment and the real-time operating status of the underground engineering network.

[0094] In one possible implementation, the method provided in this embodiment is applied based on a modular master-slave physical network architecture for underground engineering networks.

[0095] Specifically, for underground engineering networks in tunnel construction scenarios, a master station is deployed at the tunnel entrance or a stable area, and slave stations are distributed along the tunnel's depth, connected to the master station via fiber optic or wireless bridging. As construction progresses, newly added slave stations connect via reserved optical ports or wireless links, achieving seamless expansion of the underground engineering network. Through this method, a modular one-master-multiple-slave physical network architecture for this underground engineering network is constructed.

[0096] The master station is the core control node, responsible for data aggregation and computation, and integrates core network equipment, servers, and uninterruptible power supplies. The slave stations, as standardized access units, provide terminal access and wireless network coverage in the vicinity. Devices in the vicinity can communicate and connect to the slave stations via the wireless network.

[0097] This application provides a method for the operation and maintenance of equipment in an underground engineering network. The underground engineering network adopts a modular network architecture with one master and multiple slave stations. The master station communicates with the first slave station, each slave station communicates with its adjacent slave station, and each slave station connects to multiple devices. By acquiring the device information set and network operation dataset of each device in the underground engineering network, and mapping the devices to logical resource entities based on the device information set, a network topology diagram corresponding to the underground engineering network is generated based on each logical resource entity. This hides the differences between devices from multiple vendors at the logical layer, reducing the complexity of heterogeneous device management. Finally, based on the network operation dataset and network topology diagram, an equipment operation and maintenance diagram of the underground engineering network is generated. This diagram allows maintenance personnel to centrally monitor all devices in the network through a unified interface, thereby improving the efficiency of equipment operation and maintenance in the underground engineering network.

[0098] Figure 3 A flowchart illustrating an equipment operation and maintenance method for an underground engineering network provided in this application. Figure 2 ,like Figure 3 As shown, in this embodiment... Figure 2 Based on the embodiments, a method for the operation and maintenance of equipment in an underground engineering network is described in detail. The method includes:

[0099] S301. Obtain the equipment information set and network operation dataset of each device in the underground engineering network. The underground engineering network adopts a modular network architecture with one master and multiple slaves.

[0100] For a detailed description of this step, please refer to the relevant content of S201 in the above embodiment, which will not be repeated here.

[0101] S302. Based on the equipment information set, generate the network topology diagram corresponding to the underground engineering network.

[0102] In this step, the devices are mapped to logical resource entities based on the device information set, and then a network topology diagram corresponding to the underground engineering network is generated based on each logical resource entity.

[0103] Specifically, the device information set is first parsed to extract the static basic attributes of each device. Based on these static basic attributes, each device is mapped to a standardized logical resource entity, and a unique identifier is assigned to each logical resource entity, along with hierarchical and attribute tags. This completes the conversion from physical devices to digital objects. Then, based on the hierarchical and link association information of each logical resource entity, a network topology diagram is constructed. The hierarchical tag indicates whether the device belongs to the master station level, slave station level, or access device level.

[0104] S303. By monitoring the network node interaction data in the underground engineering network in real time, newly added network nodes can be identified.

[0105] S304. Update the network topology based on the newly added network nodes.

[0106] In this step, the device identification information of the newly added network node is first obtained. Then, based on the device identification information, the virtual digital model of the device corresponding to the newly added network node is matched from the preset virtual digital model library. Subsequently, based on the device identification information and the virtual digital model of the device, the newly added network node is registered and connected to the network. Based on the newly added network node after registration and connection, the network topology map is updated.

[0107] In one possible implementation, for each known heterogeneous network device, a corresponding virtual digital model is constructed. These virtual digital models are then integrated, categorized, and stored to form a pre-defined virtual digital model library. This library provides standardized model support for the rapid network registration of newly connected devices or added network nodes. The virtual digital model includes, but is not limited to, a unique identifier within the network, brand, model, data protocol, various performance indicators, and connection relationships within the physical network. When a new slave station or network device connects to the system, the system automatically discovers the device using the Link Layer Discovery Protocol (LLDP) and automatically associates the correct virtual digital model based on the device's unique identifier or brand and model information. Further association retrieves configuration information such as manufacturer, model, communication protocol, communication messages, and network connection relationships. Maintenance personnel then assign IP addresses, specify their respective sites, bind monitoring templates, and data collection protocols to the device on the system interface. The device information is then registered in the central database, completing the logical network registration.

[0108] S305. Based on the network operation dataset, determine the security status of each logical resource entity in the network topology diagram.

[0109] Among them, the safety status characterizes the fault status of the equipment.

[0110] In this step, dynamic operational metrics corresponding to each logical resource entity are first extracted from the network operation dataset. Then, based on preset threshold rules and dynamic operational metrics, the security status is determined. For example, based on preset threshold rules, each dynamic operational metric is judged to classify three levels of security status: normal, alarm, and fault, thus obtaining the security status result of each logical resource entity.

[0111] S306. Based on the security status, network operation dataset, and network topology diagram, generate an equipment operation and maintenance diagram for the underground engineering network.

[0112] Among them, the equipment operation and maintenance diagram represents the connection relationship between equipment and the real-time operating status of the underground engineering network.

[0113] In this step, the security status is mapped to the network topology diagram. Nodes and links can be marked with different colors or styles to visually present the security status of each logical resource entity, facilitating rapid risk identification by operations and maintenance personnel. The security status of each logical resource entity is mapped to the network topology diagram, with different colors marking logical resource entity nodes and different line types marking links, visually presenting the security status of each logical resource entity; for example, gray represents offline nodes, red represents faulty nodes, and green represents normal nodes; solid lines represent stable communication links, dashed lines represent fluctuating communication links, and thick red lines represent interrupted links. Simultaneously, by linking to the network operation dataset, real-time operational data details for corresponding nodes or links can be viewed in the device operation and maintenance diagram, facilitating rapid risk identification and fault tracing by operations and maintenance personnel.

[0114] In one possible implementation, maintenance personnel can click on any device in the device maintenance diagram to directly view its real-time performance curves, historical data, and alarm list, enabling rapid drill-down from macro to micro levels.

[0115] In one possible implementation, when a network outage occurs, the fault source (such as a common uplink device or optical cable fault) can be quickly located by automatically analyzing the topology connectivity, and suspected faulty nodes can be highlighted, greatly improving troubleshooting efficiency.

[0116] S307. Based on the security status of the logical resource entity, execute the corresponding alarm notification operation.

[0117] In this step, the alarm level is determined based on the security status of the logical resource entity. When the alarm level meets the preset alarm conditions, the corresponding alarm notification operation is executed according to the alarm level.

[0118] In one possible implementation, alarm notifications are sent in two ways: a passive reception mode, which receives abnormal alarm information from various devices (logical resource entities) in real time; and an active generation mode, which, based on custom alarm rules, performs real-time judgments on dynamic operating indicators and actively generates and triggers alarm notification operations. Different alarm notification operations are executed according to the alarm level, which includes urgent, severe, minor, and alert levels. Each alarm level corresponds to a different notification strategy to ensure timely response from relevant maintenance personnel.

[0119] S308: Based on network topology diagrams and network operation datasets, proactive operation and maintenance strategies are generated through model prediction.

[0120] Among them, proactive maintenance strategies refer to preventative maintenance measures generated based on predictive analytics. For example, replacing aging equipment in advance or activating backup links.

[0121] In this step, the network topology diagram and network operation dataset are input into the operation and maintenance prediction model to generate proactive operation and maintenance strategies. This operation and maintenance prediction model is constructed based on operation and maintenance analysis sample data obtained from underground engineering networks.

[0122] This application provides a method for the operation and maintenance of equipment in an underground engineering network. The network adopts a modular network architecture with one master and multiple slave stations. The master station communicates with the first slave station, each slave station communicates with its adjacent slave station, and each slave station connects to multiple devices. By acquiring the device information set and network operation dataset of each device in the underground engineering network, and generating a network topology map corresponding to the underground engineering network based on the device information set, the complexity of managing heterogeneous devices is reduced. Furthermore, by real-time monitoring of network node entry interaction data in the underground engineering network, newly added network nodes are identified, and the network topology map is updated based on these new nodes, enabling maintenance personnel to promptly grasp changes in network equipment. Finally, based on the network operation dataset, the security status of each logical resource entity in the network topology diagram is determined. Then, based on the security status, the network operation dataset, and the network topology diagram, a device operation and maintenance diagram of the underground engineering network is generated, allowing maintenance personnel to intuitively understand the security status and operational status of all network devices. According to the security status of logical resource entities, corresponding alarm notification operations are executed, ensuring that maintenance personnel receive immediate notifications and respond quickly when device security status is abnormal. Furthermore, based on the network topology diagram and network operation dataset, proactive operation and maintenance strategies are generated through model prediction, changing the traditional passive operation and maintenance model by predicting potential device problems in advance, allowing for proactive scheduling of maintenance work. These technical measures comprehensively improve the operation and maintenance efficiency of underground engineering network equipment, ensuring stable network operation.

[0123] Figure 4A flowchart illustrating an equipment operation and maintenance method for an underground engineering network provided in this application. Figure 4 ,like Figure 4 As shown, this embodiment provides a detailed description of S304 based on any of the above embodiments. This step includes:

[0124] S401. Obtain the device identification information of the newly added network node.

[0125] In this step, new network nodes can be discovered by scanning using a network node auto-discovery protocol, and their static basic attributes can be identified and extracted. These static basic attributes include at least device identification information; the new network node can be a newly added slave station or a device newly connected to an existing slave station; and the network node auto-discovery protocol can be the LLDP protocol.

[0126] S402. Based on the device identification information, match the virtual digital model of the newly added network node from the preset virtual digital model library.

[0127] S403. Based on the device identification information and the device virtual digital model, register the newly added network node to the network.

[0128] In this step, based on the device identification information and the matching virtual digital model of the device, the registration and network access of the new network node is completed. Registration and network access may include: creating basic device information, binding IP address, manufacturer and model, configuring link relationships and hierarchical labels, setting data collection protocols and alarm rules, and achieving full configuration registration of the device.

[0129] S404. Update the network topology based on newly added network nodes after registration and network access.

[0130] In this step, after the newly added network node completes its registration and joins the network, it is incorporated into the existing network topology based on its link association and hierarchical label, and an underground engineering network topology map containing the newly added node is generated.

[0131] This application provides a method for the operation and maintenance of equipment in an underground engineering network. By acquiring the equipment identification information of newly added network nodes, and matching the corresponding virtual digital model of the newly added network node from a preset virtual digital model library based on the equipment identification information, the newly added network node is registered and added to the network based on the equipment identification information and the virtual digital model of the device. Then, the network topology is updated based on the newly added network nodes after registration and addition, so that operation and maintenance personnel can keep abreast of changes in network equipment and improve the operation and maintenance efficiency of underground engineering network equipment.

[0132] Based on any of the above embodiments, the following, in conjunction with Figure 5This paper provides a detailed explanation of an equipment operation and maintenance method for underground engineering networks through a specific example. To facilitate understanding of the example, its application scenario is first explained:

[0133] The application scenario includes one master station and multiple slave stations. The master station and the first slave station are connected via a communication link, and each slave station is connected to its adjacent slave stations. The slave stations provide wireless network coverage in the vicinity, and devices in the area where the slave stations are located access the slave stations via the wireless network. The master station is equipped with a network operation and maintenance management software system, which is used to execute the equipment operation and maintenance method for an underground engineering network proposed in this embodiment. Figure 6 This is a schematic diagram of the functional modules of the network operation and maintenance management software system described above. Figure 6 As shown, the aforementioned network operation and maintenance management software system includes functional modules such as device information management, network operation overview, data acquisition and processing engine, real-time data monitoring, alarm information management, network topology overview, and fault knowledge base.

[0134] Based on the above application scenario, this specific example of an equipment operation and maintenance method for an underground engineering network includes the following steps:

[0135] S501: The data acquisition and processing engine module obtains the device information set and network operation dataset of each device and distributes them to the downstream functional modules.

[0136] In this step, the data acquisition and processing engine module has the same function as the multi-protocol acquisition engine in the previous embodiment. Specifically, the data acquisition and processing engine module acts as the data hub of the system, receives instructions from the network operation and maintenance management software system, collects the original equipment information and operating status data of each device from the underground engineering network, and generates equipment information set and network operation dataset after data cleaning and standardization transformation. These datasets are then distributed to downstream functional modules to ensure that each module obtains valid data in a unified format.

[0137] S502. The device information management module stores the device information set.

[0138] In this step, the equipment information management module stores, updates, and queries the equipment information set of all network nodes (master station, slave station, and equipment) in the underground engineering network, providing equipment information data support for other modules.

[0139] S503 monitors the safety status of equipment and newly added network nodes through a real-time data monitoring module.

[0140] In this step, the network operation dataset is analyzed through the real-time data monitoring module to determine the safety status of each device, and the network node access interaction data in the underground engineering network is monitored in real time to identify newly added network nodes (new devices or new slave stations).

[0141] In one possible implementation, the access configuration of the newly added network node (new device) is as follows: Figure 7 As shown, the entire process of new devices in an underground engineering network from discovery to completion of access configuration is divided into three core stages: device discovery, device registration, and engine activation. The specific steps are as follows:

[0142] The first step is the device discovery phase. By scanning the underground engineering network using the LLDP protocol, newly connected network devices are automatically discovered, and their manufacturers, models, and link connections with other devices are identified, completing the initial identification and location of the devices.

[0143] The second step is the device registration phase. After discovering the newly connected network device, the standardized registration configuration process begins. First, a basic information profile is created for the device, binding a unique IP address and associating it with the identified manufacturer and model information. Next, the device's link connection relationships are bound, and the master / slave hierarchy is configured, clarifying its position in the three-tier network. Then, the data acquisition protocol and message format adapted to the device are configured to ensure compatibility for subsequent data acquisition. Finally, the device's alarm triggering rules are configured, defining the criteria for judging abnormal states, completing the full information registration of the device.

[0144] The third step is the engine activation phase. After device registration is complete, the data acquisition and alarm linkage mechanism is officially launched: the data acquisition engine is triggered, and the engine begins to collect the device's real-time operating data based on the device's IP address and the configured acquisition protocol; it also parses the collected raw messages, extracts valid data, and stores it in the corresponding database; then it determines in real time whether an alarm message has been triggered or received: if an alarm message has been triggered or received, the alarm message is stored in the alarm database; if no alarm message has been triggered, the process directly enters the termination phase.

[0145] S504. Generate device operation and maintenance diagrams through the network topology overview module.

[0146] In this step, based on the device information set, the physical connections between devices and between devices and slave stations are determined. Then, based on the device information set and physical connections, a network topology map is constructed. When a new network node is identified, the network topology map is updated in real time to maintain consistency between the network topology map and the physical network architecture. Finally, based on the network topology map, device security status, and network operation dataset, a device maintenance map is generated.

[0147] Specifically, the network topology map and real-time network operation dataset are merged, and the device status is dynamically rendered using preset status rendering rules (e.g., gray indicates offline devices, red indicates high load) to generate a device operation and maintenance map. This map allows maintenance personnel to perform penetrating queries on devices, retrieve device details (such as device performance curves and historical alarm records) from the device information management module, and quickly locate the root cause of network failures (such as uplink device failures or fiber optic communication failures).

[0148] S505. Through the alarm information management module, corresponding alarm events are generated based on the equipment safety status.

[0149] In this step, the alarm information management module analyzes the security status of the device, generates, stores, and processes various network alarm events (such as device offline, link interruption, and excessive load), and supports alarm rule customization, alarm suppression, alarm tracing, and historical alarm query.

[0150] S506. Intelligent prediction and proactive operation and maintenance are achieved through the fault knowledge base module.

[0151] In this step, historical data is obtained through the fault knowledge base module. This historical data is used as sample data for operation and maintenance analysis. An operation and maintenance prediction model is constructed based on the sample data. Based on this model, proactive operation and maintenance strategies (such as equipment replacement warnings and bandwidth expansion suggestions) are generated to support operation and maintenance personnel in taking early intervention measures to prevent faults from occurring.

[0152] It should be noted that, in Figure 5 The processing steps S501-S506 shown in the embodiments do not constitute a specific limitation on a method for the operation and maintenance of equipment in an underground engineering network. In other embodiments of this application, a method for the operation and maintenance of equipment in an underground engineering network may include more than Figure 5 The embodiments may include more or fewer steps; for example, a method for the operation and maintenance of equipment in an underground engineering network may include... Figure 5 Some steps in the embodiments, or, Figure 5 Some steps in the embodiments can be replaced by steps with the same function, or, Figure 5 Some steps in the embodiments can be broken down into multiple steps, etc.

[0153] Figure 8 This application provides an architectural diagram of a network device operation and maintenance management system, such as... Figure 8 As shown in the figure, the network device operation and maintenance management system provided in this embodiment adopts a layered architecture design, which includes, from bottom to top, a device layer, a transmission layer, a data acquisition layer, a storage layer, a platform layer, and an application layer. Each layer achieves integrated operation and maintenance management through data interaction, as detailed below:

[0154] The equipment layer adopts a master-slave chain network structure, which includes 1 master station and n slave stations (slave station 1, slave station 2, ..., slave station n). The master station communicates with the first slave station, and each slave station communicates with its adjacent slave station in sequence, forming a chain transmission link adapted to the tunnel construction scenario, providing the underlying equipment nodes for the entire system.

[0155] The transmission layer includes various transmission methods such as fiber optic ring networks, chain networks, and wireless networking. As a communication bridge between the device layer and the acquisition layer, it adapts to the data transmission needs of multiple scenarios in the complex environment of underground engineering, ensuring that data from the device layer is stably uploaded to the acquisition layer.

[0156] The acquisition layer, with a multi-protocol data acquisition engine at its core, incorporates multiple communication protocols such as SNMP, MQTT, and HTTP. It actively collects raw device information and real-time operating status data from the device layer through the transmission layer, and then standardizes the collected heterogeneous data before transmitting it to the storage layer.

[0157] The storage layer includes three types of storage units: relational databases, time-series databases, and file systems. After receiving standardized data from the acquisition layer, it stores the data according to its data type.

[0158] The platform layer includes a network operation and maintenance management software system, a data analysis and processing engine, and a topology dynamic generation engine. The network operation and maintenance management software system, as the core hub of the platform layer, connects to the storage layer to obtain data, calls the data analysis and processing engine and the topology dynamic generation engine to process the data, and outputs the processed data to the application layer.

[0159] At the application layer, through six functional modules—network topology visualization, fault root cause analysis, performance trend prediction, alarm management center, real-time data monitoring, and device management—the data output by the network operation and maintenance management software system in the platform layer is visualized and interactive.

[0160] The specific implementation process of the network operation and maintenance management software system can be found in the above method embodiments. The implementation principle and technical effect are similar, and will not be repeated here.

[0161] Figure 9 This application provides a schematic diagram of the equipment operation and maintenance system for an underground engineering network. The underground engineering network adopts a modular network architecture with one master and multiple slave stations. The master station communicates with the first slave station, each slave station communicates with its adjacent slave station, and each slave station connects to multiple devices. The system is deployed at the master station, such as... Figure 9 As shown, the equipment operation and maintenance system 90 for an underground engineering network provided in this embodiment includes at least a data acquisition and processing engine module 901, a network operation overview module 902, and a network topology overview module 903.

[0162] Among them, the data acquisition and processing engine module 901 is used to acquire the equipment information set and network operation dataset of each device in the underground engineering network.

[0163] The network operation overview module 902 is used to map devices to logical resource entities based on the device information set; and to generate a network topology diagram corresponding to the underground engineering network based on each logical resource entity.

[0164] The network topology overview module 903 is used to generate an equipment operation and maintenance diagram of the underground engineering network based on the network operation dataset and the network topology diagram; the equipment operation and maintenance diagram represents the connection relationship between devices and the real-time operating status of the underground engineering network.

[0165] In one possible implementation, the network topology overview module 903 is specifically used for:

[0166] Based on the network operation dataset, determine the security status of each logical resource entity in the network topology diagram; the security status represents the fault status of the device.

[0167] Based on the security status, network operation dataset, and network topology diagram, generate an equipment operation and maintenance diagram for the underground engineering network.

[0168] In one possible implementation, the system also includes an equipment information management module, which is used to identify newly added network nodes by monitoring the network node access interaction data in the underground engineering network in real time.

[0169] Correspondingly, the network operation overview module 902 is also used to update the network topology map based on newly added network nodes.

[0170] In one possible implementation, the device information management module is specifically used for:

[0171] Obtain the device identification information of the newly added network node.

[0172] Based on the device identification information, the virtual digital model of the newly added network node is matched from the preset virtual digital model library.

[0173] New network nodes are registered and added to the network based on device identification information and virtual digital models of the devices.

[0174] Correspondingly, the network operation overview module 902 is also used to update the network topology based on newly added network nodes after registration and joining the network.

[0175] In one possible implementation, the system further includes an alarm information management module, which is used to determine the alarm level based on the security status of the logical resource entity; and to perform the corresponding alarm notification operation according to the alarm level when the alarm level meets the preset alarm conditions.

[0176] In one possible implementation, the data acquisition and processing engine module 901 is specifically used for:

[0177] The system uses a multi-protocol acquisition engine to obtain raw equipment information and operational status data of each device in the underground engineering network.

[0178] The original equipment information is standardized to obtain the equipment information set.

[0179] The operational status data is standardized to obtain the network operational dataset.

[0180] In one possible implementation, the system further includes a fault knowledge base module for acquiring operation and maintenance analysis sample data of the underground engineering network; constructing an operation and maintenance prediction model based on the operation and maintenance analysis sample data; and inputting the network topology diagram and network operation dataset into the operation and maintenance prediction model to generate proactive operation and maintenance strategies.

[0181] This embodiment provides an equipment operation and maintenance system for underground engineering networks, which can execute the methods provided in the above-described method embodiments. Its implementation principle and technical effects are similar, and will not be described in detail here.

[0182] Figure 10 A schematic diagram of the structure of the electronic device provided in this application. Figure 10 As shown, the electronic device 100 provided in this embodiment includes at least one processor 1001 and a memory 1002. Optionally, the device 100 further includes a communication component 1003. The processor 1001, memory 1002, and communication component 1003 are connected via a bus 1004.

[0183] In a specific implementation, at least one processor 1001 executes computer execution instructions stored in memory 1002, causing at least one processor 1001 to perform the above-described method.

[0184] The specific implementation process of processor 1001 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0185] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0186] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0187] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0188] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0189] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0190] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0191] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0192] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0193] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0194] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0195] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0196] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0197] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A device operation and maintenance method of an underground engineering network, characterized by, The underground engineering network adopts a modular network architecture with one master and multiple slave stations, consisting of a master station and multiple slave stations. The master station is communicatively connected to the first slave station, each slave station is communicatively connected to its adjacent slave station, and each slave station is connected to multiple devices. The method is applied to the master station and includes: Obtain the equipment information set and network operation dataset of each device in the underground engineering network; Based on the device information set, the device is mapped to a logical resource entity; Based on each of the logical resource entities, generate a network topology diagram corresponding to the underground engineering network; Based on the network operation dataset and the network topology diagram, an equipment operation and maintenance diagram of the underground engineering network is generated; the equipment operation and maintenance diagram represents the connection relationship between the devices and the real-time operating status of the underground engineering network.

2. The method of claim 1, wherein, The step of generating the equipment operation and maintenance diagram of the underground engineering network based on the network operation dataset and the network topology diagram includes: Based on the network operation dataset, the security status of each logical resource entity in the network topology diagram is determined; the security status represents the fault status of the device. Based on the security status, the network operation dataset, and the network topology diagram, an equipment operation and maintenance diagram of the underground engineering network is generated.

3. The method according to claim 1, characterized in that, After generating the network topology diagram corresponding to the underground engineering network based on each of the logical resource entities, the method further includes: New network nodes are identified by real-time monitoring of network node interaction data in the underground engineering network. The network topology is updated based on the newly added network nodes.

4. The method according to claim 3, characterized in that, The step of updating the network topology map based on the newly added network nodes includes: Obtain the device identification information of the newly added network node; Based on the device identification information, the virtual digital model of the device corresponding to the newly added network node is matched from the preset virtual digital model library of devices; Based on the device identification information and the device virtual digital model, the newly added network node is registered and connected to the network. The network topology is updated based on the newly added network nodes after registration.

5. The method according to claim 2, characterized in that, After generating the equipment operation and maintenance diagram of the underground engineering network based on the security status, the network operation dataset, and the network topology diagram, the method further includes: Determine the alarm level based on the security status of the logical resource entity; When the alarm level meets the preset alarm conditions, the corresponding alarm notification operation is executed according to the alarm level.

6. The method according to claim 1, characterized in that, The acquisition of the device information set and network operation dataset of each device in the underground engineering network includes: The original equipment information and operating status data of each device in the underground engineering network are obtained through a multi-protocol acquisition engine. The original equipment information is standardized to obtain the equipment information set; The operational status data is standardized to obtain the network operational dataset.

7. The method according to claim 1, characterized in that, The method further includes: Obtain operation and maintenance analysis sample data of the underground engineering network; Based on the aforementioned operation and maintenance analysis sample data, an operation and maintenance prediction model is constructed; The network topology map and the network operation dataset are input into the operation and maintenance prediction model to generate proactive operation and maintenance strategies.

8. An equipment operation and maintenance system for an underground engineering network, characterized in that, The underground engineering network adopts a modular network architecture with one master and multiple slaves, consisting of a master station and multiple slave stations. The master station is communicatively connected to the first slave station, each slave station is communicatively connected to its adjacent slave station, and each slave station is connected to multiple devices. The system is deployed at the main station and includes at least a data acquisition and processing engine module, a network operation overview module, and a network topology overview module. The data acquisition and processing engine module is used to acquire the equipment information set and network operation dataset of each device in the underground engineering network. The network operation overview module is used to map the devices as logical resource entities according to the device information set; and to generate a network topology diagram corresponding to the underground engineering network according to each logical resource entity. The network topology overview module is used to generate an equipment operation and maintenance diagram of the underground engineering network based on the network operation dataset and the network topology diagram; the equipment operation and maintenance diagram represents the connection relationship between the devices and the real-time operating status of the underground engineering network.

9. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 7.

Images