Power plant slave station communication monitoring system and method

Abstract

The embodiment of the invention provides a power plant slave station communication monitoring system and method, and relates to the technical field of electric power automation and industrial communication. The system comprises a master station, a communication server and a remote management device. Wherein the remote management equipment forms a front-end operation entrance by operating a data service remote management application, and is used for receiving interactive operation of a user. The communication server comprises a slave station management module and a plurality of slave station process modules. When communication monitoring is carried out, the slave station management module can obtain slave station communication data and execute a core task according to the slave station communication data. The system adopts a framework of a front-end desktop application and a rear-end communication management service, the front end takes the desktop application as an operation entrance, and the rear end realizes core tasks such as data forwarding, process control and fault diagnosis by establishing connection, so that a communication monitoring system with centralized control and distributed deployment is formed, and the communication management service is realized. The requirement for convenience of operation and maintenance operation is met, the operation and maintenance efficiency is improved, and stability and reliability of power plant communication are guaranteed.

Description

Technical Field

[0001] This application relates to the fields of power automation and industrial communication technology, and in particular to a power plant slave communication monitoring system and method. Background Technology

[0002] IEC 104 is a communication protocol standard in the field of power automation, used for data communication between power system substation computer monitoring systems or remote terminal units (RTUs) and the master station system. The data communication process can adopt a client-server model, with the power plant master station acting as the client and the remote station as the server. The master station can send control commands to the remote station and receive real-time data from the remote station. The network communication between the master station and the remote station uses the TCP / IP protocol at the underlying layer and the IEC 104 transmission protocol at the application layer, suitable for computer network environments.

[0003] Power communication monitoring systems based on the IEC 104 protocol often employ a single-tool and isolated server architecture, using a single-link network connection and TCP / IP protocol for master-slave data interaction. During configuration and maintenance, each communication server must be accessed individually via local external devices or remote login tools to perform operations such as configuring IEC 104 protocol parameters and modifying point table files. Single-server communication status monitoring and basic message capture are supported, with logs stored locally in offline mode.

[0004] However, since power plant communication servers are mostly deployed in racks without local displays and lack a centralized management architecture, they are not adapted to the distributed deployment of multiple servers in power plants. Operating each server individually on-site or remotely logging in separately leads to cumbersome workflows for configuration, debugging, and program upgrades, reducing operational efficiency. Furthermore, due to the single-link transmission mode, a link failure will directly cause a communication interruption between the master and slave stations, affecting the continuity of power production. Summary of the Invention

[0005] In view of this, embodiments of this application provide a power plant slave communication monitoring system and method to solve the problem of low operation and maintenance efficiency of power communication monitoring systems.

[0006] According to a first aspect of this application, a power plant slave station communication monitoring system is provided, the system comprising: a master station, a communication server, and remote management devices; the master station establishes a network communication connection with the communication server; the communication server establishes a network communication connection with at least one of the remote management devices; The remote management device is equipped with a data service remote management application; the remote management device is configured to form a front-end operation entry by running the data service remote management application, and to receive user interaction operations through the front-end operation entry. The communication server includes a slave station management module and multiple slave station process modules; the slave station management module has a built-in dual-server architecture, including a local communication server and a remote communication server; the local communication server is used to establish connections with the multiple slave station process modules within the communication server to achieve centralized management and control; the remote communication server is used to interface with the data service remote management application. The slave process module adopts a dual-end architecture; the slave process module includes a master station communication server and a local management client; the master station communication server is used to communicate with the master station in accordance with the communication protocol standard; the local management client is used to establish a persistent connection with the slave management module through a local link to realize process status reporting and command reception. The slave station management module is configured as follows: Acquire slave communication data, which includes instruction data obtained through a remote communication server and monitoring data obtained through a local communication server; The core tasks are performed based on the slave communication data, and the core tasks include at least one of data forwarding, process management, and fault diagnosis.

[0007] In some embodiments, the remote management device is further configured to: The interface displays a visual interactive interface, which includes a communication process list. The communication process list is used to display at least one of the following: process ID, running status, associated master station, and master / standby status information. Receive interactive operations input by the user based on the visual interactive interface; In response to the interaction operation, operation information is extracted from the interaction operation, the operation information including operation type and operation object; The backend network connection and interface response are executed based on the operation information.

[0008] In some embodiments, the remote management device, which performs backend network connection and interface response based on the operation information, is further configured to: The communication target information is obtained based on the operation information. The communication target information is the information input by the user when performing the interactive operation. The communication target information includes the IP address of the target communication server, the target domain number, and the target station number. The communication target information is sent to the slave station management module to trigger the slave station management module to select the slave station process module according to the communication target information, and to establish a network communication connection with the master station through the slave station process module; After establishing a network communication connection, the connection result display interface is shown.

[0009] In some embodiments, the slave station management module is further configured to: The remote communication server listens to a fixed port to establish a network communication connection with the data service remote management application based on a dual-network redundant link; Obtain the process control instructions uploaded by the remote management device; In response to the process control command, the process control command is parsed, and a process control signal recognizable by the slave process module is generated based on the process control command; Based on the process control signal, the local communication server collects and summarizes process data of multiple slave process modules. The process data includes at least one of process running status, master station interaction data, and log information. The process data is standardized to generate control feedback information; The control feedback information is sent to the data service remote management application via the remote communication server.

[0010] In some embodiments, the slave station management module is further configured to: Obtain master station communication requirement information, wherein the master station communication requirement information includes communication requirements for at least one of the master stations; The number of communication requests is parsed from the main station's communication request information; The slave process module is created according to the number of communication requirements, and each slave process module corresponds to one communication requirement of the master station.

[0011] In some embodiments, the slave station management module is further configured to obtain master station communication requirement information as follows: Read the control target from the process control instruction, the control target including at least one of the process to be created and the process to be deleted; If the control target includes the process to be created, the slave process module is set based on the process to be created, and a persistent connection relationship is established between the newly set slave process module and the local communication server. If the control target includes the process to be deleted, shut down the slave process module corresponding to the process to be deleted.

[0012] In some embodiments, the slave station management module is further configured to: Receive the data forwarding instruction reported by the remote management device; In response to the data forwarding instruction, monitoring data is acquired, wherein the monitoring data includes at least one of remote signaling data, telemetry data, and remote control instructions; The monitoring data is sent to the local management client through the local communication server, and then reported to the main station through the main station communication server.

[0013] In some embodiments, the system further includes a communication network device; the master station establishes a network communication connection with the communication server through the communication network device; the remote management device establishes a network communication connection with the communication server through the communication network device; The network communication connection established based on the communication network device includes a primary path and at least one backup path; the communication network device is configured with multi-network redundancy functionality; the slave station management module is further configured to: Receive fault diagnosis instructions reported by the remote management device; In response to the fault diagnosis command, the communication connection status of the main path is detected; When the communication connection status of the primary path is in failure, a path switching command is sent to the communication network device to control the communication network device to switch to the backup path.

[0014] In some embodiments, the system further includes a data storage device connected to the communication server; the slave management module is further configured to: Acquire the data to be stored, which includes system running data, log files, and configuration files; The data to be stored is sent to the data storage device to store the data.

[0015] According to a second aspect of this application, a power plant slave communication monitoring method is provided, applied to the system described in the first aspect; the method includes: Acquire slave communication data, which includes instruction data obtained through a remote communication server and monitoring data obtained through a local communication server; The core tasks are performed based on the slave communication data, and the core tasks include at least one of data forwarding, process management, and fault diagnosis.

[0016] According to a third aspect of this application, a computer device is provided, including a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein the processor executes the program to implement the above-described power plant slave communication monitoring method.

[0017] According to a fourth aspect of this application, a storage medium is provided that stores a computer program thereon, which, when executed by a processor, implements the above-described power plant slave communication monitoring method.

[0018] Based on the above technical solutions, this application provides a power plant slave communication monitoring system and method. The system includes a master station, a communication server, and remote management equipment. The remote management equipment forms a front-end operation entry point by running a data service remote management application, used to receive user interaction operations. The communication server includes a slave management module and multiple slave process modules. The slave management module adopts a dual-server architecture; the slave process modules adopt a dual-end architecture. During communication monitoring, the slave management module can acquire slave communication data and execute core tasks based on the slave communication data. The system adopts a front-end desktop application and a back-end communication management service architecture. The front-end uses the desktop application as the operation entry point, providing a visual interface for power plant operation and maintenance, supporting operations such as viewing communication status, modifying configuration parameters, and retrieving logs. The back-end establishes connections with the communication servers of each power plant slave station to realize core tasks such as data forwarding, process control, and fault diagnosis, forming a centralized control and distributed deployment communication monitoring system. This satisfies the need for convenient operation and maintenance, improves operation and maintenance efficiency, and ensures the stability and reliability of power plant communication.

[0019] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0020] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 This is a schematic diagram of the power plant slave communication monitoring system provided in an embodiment of this application; Figure 2 This is a schematic flowchart of a power plant slave communication monitoring method provided in an embodiment of this application; Figure 3 This is a schematic diagram of the process management task flow provided in an embodiment of this application; Figure 4 This is a schematic diagram of the creation and deletion process provided in the embodiments of this application; Figure 5 This is a schematic diagram of the data forwarding task process provided in an embodiment of this application; Figure 6 This is a schematic diagram of the fault diagnosis task process provided in an embodiment of this application. Detailed Implementation

[0021] The present application will be described in detail below with reference to the accompanying drawings and embodiments. It should be noted that, unless otherwise specified, the embodiments and features described in the embodiments of the present application can be combined with each other.

[0022] In this embodiment, the power plant slave communication monitoring system and method can be used to perform communication monitoring on substations within a power system. A power system refers to a system composed of equipment for power generation, transmission, transformation, distribution, and consumption, used for the production, transmission, distribution, and use of electrical energy. Within a power system, multiple power devices with communication functions can be applied; therefore, communication monitoring refers to monitoring functions such as collecting and monitoring communication-related data, transmitting control commands, and monitoring the status of communication links, and performing anomaly detection and processing based on the monitoring data.

[0023] Power equipment with communication capabilities in a power system can achieve communication based on specific communication protocols. These communication protocols include, but are not limited to, Modbus, IEC 60870-5-104 (IEC 104), and Profibus.

[0024] Taking the IEC 104 protocol as an example, IEC 104 is one of the communication protocol standards in the field of power automation, used for data communication between the computer monitoring system of power substation or the remote terminal unit (RTU) and the master station system.

[0025] The data communication process can adopt a client-server model, with the power plant master station acting as the client and the remote station acting as the server. The master station can send control commands to the remote station and receive real-time data from the remote station. The network communication between the master station and the remote station uses the TCP / IP protocol at the underlying layer and the IEC 104 transmission protocol at the application layer to be suitable for computer network environments.

[0026] In some embodiments, power communication monitoring systems based on the IEC 104 protocol can adopt a single-tool and isolated server architecture, using a single-link network connection and TCP / IP protocol for master-slave data interaction. During configuration and maintenance, the communication monitoring system can access the communication server individually via local external devices or remote login tools to perform operations such as configuring IEC 104 protocol parameters and modifying point table files. It supports single-server communication status monitoring and basic message capture, with logs stored locally in offline mode.

[0027] However, due to the lack of a centralized management and control architecture in the aforementioned communication monitoring system, it is not adapted to the characteristics of the distributed deployment of multiple servers in power plants. Power plant communication servers are mostly deployed on racks and have no local monitors. Each server needs to be operated on-site or remotely logged in individually, resulting in cumbersome workflows such as configuration debugging and program upgrades. Therefore, the operation and maintenance efficiency of the aforementioned communication monitoring system is low and the operating cost is high.

[0028] Furthermore, since the aforementioned communication monitoring system does not have a redundant backup mechanism designed for the high security requirements of power plants, it only meets the basic data transmission requirements and adopts a single-link transmission mode. Once the link fails, it will directly lead to the interruption of communication between the master and slave stations, affecting the continuity of power production. Therefore, the aforementioned communication monitoring system is prone to insufficient communication reliability and has the risk of interruption.

[0029] The aforementioned communication monitoring system lacks a global management design, supporting only isolated operation of a single server. It fails to consider the need for collaborative management of multiple devices and cannot uniformly manage multiple communication servers and their associated communication processes. Operations such as starting and stopping processes and viewing data must be performed one by one, which can easily lead to inconsistencies in configuration and omissions in operations. Therefore, the management of the aforementioned communication monitoring system is fragmented and lacks coordination.

[0030] Furthermore, since the aforementioned communication monitoring system focuses on basic monitoring and has not optimized the log function design for the fault diagnosis needs of power plant operation and maintenance, the logs are only stored locally and cannot be remotely downloaded and analyzed in real time, resulting in slow log management and communication fault location and difficulty in tracing.

[0031] To address the problem of low operation and maintenance efficiency in power communication monitoring systems, some embodiments of this application provide a power plant slave communication monitoring system. For example... Figure 1 As shown, the power plant slave station communication monitoring system includes: a master station, a communication server, and remote management equipment. The master station establishes a network communication connection with the communication server; the communication server establishes a network communication connection with at least one remote management device.

[0032] In this context, the master station refers to the control center in a power system used to implement communication and monitoring functions. It is responsible for managing and coordinating the communication and control operations of the entire system. The master station can be deployed in the power system's main server to form a cloud-based control service.

[0033] In some embodiments, a power system may include multiple master stations, each deployed on different servers or within different power supply areas, each responsible for implementing different communication monitoring functions or monitoring communication in different areas. Different master stations can also communicate with power equipment in the power system based on different communication protocols. For example, a master station that communicates using the IEC 104 protocol or monitors communication using the IEC 104 protocol is called an IEC104 master station system, or simply a 104 master station.

[0034] Remote management equipment is a terminal device used for interaction and communication with users. As the core management platform of the power plant slave communication monitoring system, remote management equipment can be used to manage and monitor the slave communication status and realize remote operation.

[0035] Remote management devices can be servers, workstations, or combinations thereof, and are equipped with the computing resources required to run the management system. For example, the operating system of the remote management device may be Windows or Linux. In terms of software support, it can run applications for the power plant monitoring system. Furthermore, the remote management device has a visual interactive function; it can be a visual display device equipped with a monitor, keyboard, and mouse, allowing engineers to interact with the management system and enabling users to view communication status, configuration parameters, and operate communication processes. In addition, the remote management device can provide a network interface, supporting multiple network interface card (NIC) connections, such as network A and network B, to ensure communication redundancy with the target site.

[0036] To enable communication monitoring, a data service remote management application is deployed in the remote management device. The remote management device is configured to form a front-end operation entry by running the data service remote management application, and to receive user interaction operations through the front-end operation entry.

[0037] The data service remote management application is a type of data service remote management application. Its deployment can be as a desktop client program, installed on the operation and maintenance terminal in the power plant control room or on any server with network access, and it does not require a fixed deployment location. The data service remote management application can be used to implement communication connection management and visual interface interaction.

[0038] For visual interface interaction, in some embodiments, the remote management device is configured to display a visual interactive interface. This visual interactive interface includes a communication process list; the communication process list is used to display at least one of the following: process ID, running status, associated master station, and master / standby status information.

[0039] For example, the visual interactive interface can display a list of communication processes on the homepage, showing information such as process ID, running status, associated master station, and master / slave status. Users can double-click a communication process in the list to navigate to a tab. This tab provides a table showing the master station connection status, including startup time, local IP, master station IP, connection time, and master station task name. The tab may also include a dot table configuration editor, supporting dot table import / export, field modification, validation, and saving. Furthermore, the tab may include a real-time log viewing window and a log download module for real-time logging and parsing. The log download module can retrieve all 104 message logs stored on the communication server and filter logs by master station or time.

[0040] During the display of the visual interactive interface, the remote management device can receive interactive operations input by the user based on the visual interface by running a data service remote management application. For example, the data service remote management application can support users to manually enter the target communication server IP address, select the target domain number and target station number, thereby establishing a TCP connection with the backend program. Therefore, users can input information based on the visual interactive interface, i.e., obtain interactive operations for entering the target communication server IP address and selecting the target domain number and target station number.

[0041] After obtaining the interaction, the system can respond to the interaction and extract operation information from it. This operation information includes the operation type and the operation object. The operation type refers to the specific type of interaction action performed by the user; the operation object refers to the target on which the interaction is directed.

[0042] For example, users can perform interactive actions such as information input, long press, single click, and double click in a visual interactive interface. The operation type refers to the specific information input action, long press action, single click action, double click action, etc., while the operation object refers to the input information, the target of the long press, the target of the single click, and the target of the double click, etc.

[0043] After extracting operation information from the interactive operation, the remote management device can also execute backend network connection and interface response based on the operation information. In some embodiments, to achieve communication connection management, the remote management device is also configured to obtain communication target information based on the operation information when executing backend network connection and interface response based on the operation information. The communication target information is the information input by the user when performing the interactive operation; the communication target information includes the IP address of the target communication server, the target domain number, and the target station number.

[0044] The communication target information is then sent to the slave station management module to trigger the slave station management module to select the slave station process module based on the communication target information, and to establish a network communication connection with the master station through the slave station process module. After the network communication connection is established, the connection result display interface is shown.

[0045] For example, when managing communication connections, the remote management device can remotely manage applications by running data services. It supports manually inputting the target communication server IP address and, after the user selects the target domain number and target station number, establishes a TCP connection with the backend slave station management module. It also supports connecting to multiple target servers simultaneously and switching between them for management, thus achieving communication connection management. After the communication connection is completed, the connection result can be displayed through a visual interactive interface, such as "104SM program" connected.

[0046] It should be noted that the remote management device, as the front-end of the system, can also use a web browser, mobile app, or dedicated industrial tablet client instead of the desktop application, all of which provide a visual operation interface and data display functionality. Furthermore, it supports remote control, such as remote login via SSH / Telnet command line, VNC remote desktop control, or third-party remote maintenance tools for remote configuration, enabling server parameter modification and process management.

[0047] The communication server includes a slave management module (Slave Manager) and multiple slave process modules (SlaveComm). The slave management module, as the core middleware, is responsible for coordinating the management of multiple slave process modules, namely the communication server slave processes and their interaction with the front-end application.

[0048] For example, the data service remote management application can be started on any server. After startup, it selects the target domain number and target station number in the power plant monitoring system through the local communication server, and establishes a connection with the slave management module (IEC 60870-5-104 Slave Manager, 104SM) program based on the ICE104 protocol on the target server using the local IP address. After the connection is established, remote control of the 104 communication process of the target server can be achieved through 104SM, including real-time display of the master station connection status, online configuration of point table parameters, querying and exporting logs, and other operations.

[0049] The slave station management module features a dual-server architecture, comprising a local communication server and a remote communication server. The local communication server establishes connections with multiple slave process modules within the communication server for centralized management; the remote communication server interfaces with remote data service management applications.

[0050] For example, as the core middleware layer, the slave station management module has a dual-server architecture consisting of a local communication server and a remote communication server. The local communication server is used to establish connections with the communication processes of each of the 104 slave stations on the local machine and to achieve centralized management. The remote communication server is used to interface with the data service remote management application, undertaking the tasks of command forwarding and data interaction.

[0051] The slave management module can also be deployed on specific electronic devices to form a slave management device. For example, a 104Slave Manager device, acting as an intermediate management module, can coordinate communication between the local communication process and the remote management application for data services. To this end, the 104Slave Manager device can be an embedded or standard industrial computing device, running operating systems such as Linux or Windows, to support dual servers—that is, it includes two independent network servers, one for connecting to the local communication process and the other for connecting to the integrated communication management system. The 104Slave Manager device can also provide a fixed port and support remote TCP connections.

[0052] The 104Slave Manager device may also include a storage module for storing log files, configuration files, and communication task status, and may support hot-swappable SD cards or hard drives for easy maintenance. For communication interfaces, it may support a wired network interface with TCP / IP protocol to ensure stable communication with local processes and remote systems.

[0053] The slave process module adopts a dual-end architecture, consisting of a master station communication server and a local management client. The master station communication server communicates with the master station according to communication protocol standards; the local management client establishes a persistent connection with the slave management module via a local link to report process status and receive commands.

[0054] For example, by embedding multiple slave process modules within the communication server, multiple independent 104Slave communication processes can be formed on the communication server. Each process adopts a dual-end module architecture of a local management client and a master communication server. Each communication process runs independently, achieving process isolation characteristics, meaning that the failure of a single process does not affect the normal communication of other processes, thus improving the overall stability of the system.

[0055] The main station communication server follows the IEC 104 protocol standard to communicate with different external 104 main stations. The local management client establishes a connection with the 104SM through a local link to report process status and receive control commands, ensuring that front-end operations can directly affect the underlying communication links.

[0056] It should be noted that data can also be exchanged between the master and slave stations via shared folders or FTP services, replacing real-time communication protocols. Furthermore, for the communication protocol, the IEC 61850, DNP3, or OPC UA protocols can be used instead of the IEC 104 protocol to achieve control command transmission and data interaction between the power plant master and slave stations. Among these, IEC 61850 supports object-oriented modeling and high-speed real-time communication, the DNP3 protocol has stronger error detection and recovery capabilities, and the OPC UA protocol focuses on secure cross-platform data transmission.

[0057] Similarly, slave process modules can also be deployed in electronic devices to form slave process devices. For example, a slave process device is a 104Slave slave communication process device, which is responsible for communicating with the master station and interacting locally with the 104 Slave Manager.

[0058] The 104Slave slave communication process device can be an industrial communication module that runs slave communication process applications and features a dual-role communication interface. The server interface processes communication commands from the master station, while the client interface actively reports communication status to the 104Slave Manager. The network interface of the 104Slave slave communication process device supports Ethernet, serial ports, or fieldbus interfaces such as RS485 and PROFIBUS to accommodate different communication protocol requirements. Furthermore, the 104Slave slave communication process device can also incorporate a real-time monitoring module to support real-time output of task running status and log information, as well as self-checking functions for abnormal states.

[0059] Based on the communication server described in the above embodiments, the system can monitor slave communication through a slave management module and multiple slave process modules. In some embodiments, the slave management module is configured to execute a power plant slave communication monitoring method to enable the backend to establish a connection with each power plant slave communication server through a dual-network redundant communication link, undertake core tasks such as data forwarding, process management, and fault diagnosis, and form a centralized management and distributed deployment communication monitoring system. This not only meets the needs of convenient operation and maintenance and improves operation and maintenance efficiency, but also ensures the stability and reliability of the power plant communication system.

[0060] The power plant slave communication monitoring method described above can be applied to electronic devices with data processing capabilities. These electronic devices include, but are not limited to, computers, servers, mobile terminals, smart wearable devices, and industrial control computers. For ease of description, this application embodiment uses a communication server or slave management module as the execution subject of the method. It should be understood that the method can also be applied to other types of execution subjects, which are not shown one by one in this application embodiment. Figure 2As shown, the method includes: S101, Obtain slave station communication data; During communication monitoring, the slave station management module can first acquire slave station communication data. This slave station communication data includes instruction data obtained through a remote communication server and monitoring data obtained through a local communication server.

[0061] Command data refers to control commands or sets of control commands sent by remote management devices to the communication server, or by the master station to the communication server. Command data can be generated based on user-executed interactive operations. Depending on the interactive operation performed, command data can include at least one of the following: data conversion commands, process control commands, and fault diagnosis commands. Clearly, different command data can correspond to different interactive operation methods to control the communication server to achieve different communication monitoring functions.

[0062] Monitoring data refers to communication data sent from remote management devices to a communication server, or from the master station to a communication server. Monitoring data can include data collected by various data acquisition devices in the power system, data generated by various data processing devices, and data input by users. For example, monitoring data can include at least one of remote signaling data, telemetry data, and remote control commands.

[0063] S102. Execute core tasks based on slave communication data.

[0064] After acquiring slave station communication data, the slave station management module can execute core tasks based on this data. These core tasks include at least one of data forwarding, process control, and fault diagnosis. The specific core task executed by the slave station management module can be determined based on the slave station communication data. For example, when the slave station communication data is a data conversion instruction, the core task executed by the slave station management module is data forwarding. Similarly, when the slave station communication data is a process control instruction, the core task executed by the slave station management module is process control; and when the slave station communication data is a fault diagnosis instruction, the core task executed by the slave station management module is fault diagnosis.

[0065] As can be seen, the system described in the above embodiments includes a master station, a communication server, and remote management equipment. The remote management equipment forms a front-end operation entry point by running a data service remote management application, used to receive user interaction operations. The communication server includes a slave station management module and multiple slave station process modules. The slave station management module adopts a dual-server architecture; the slave station process modules adopt a dual-end architecture. During communication monitoring, the slave station management module can obtain slave station communication data and execute core tasks based on this data. The system adopts an architecture of a front-end desktop application and a back-end communication management service. The front-end uses the desktop application as the operation entry point, providing a visual interface for power plant operation and maintenance, supporting operations such as viewing communication status, modifying configuration parameters, and retrieving logs. The back-end establishes connections with the communication servers of each power plant slave station to realize core tasks such as data forwarding, process control, and fault diagnosis, forming a centralized control and distributed deployment communication monitoring system. This satisfies the need for convenient operation and maintenance, improving efficiency, while ensuring stable and reliable power plant communication.

[0066] like Figure 3 As shown, for process control tasks, in some embodiments, the slave management module can adopt a lightweight service program, independently deployed locally on each power plant slave communication server, and automatically start with the server upon power-on. Therefore, the slave management module is also configured to listen on a fixed port via a remote communication server to establish a network communication connection with the remote management application based on a dual-network redundant link, and to obtain process control instructions uploaded by the remote management device.

[0067] In response to process control commands, the system parses these commands and generates process control signals recognizable by the slave process modules. Based on these signals, it collects and aggregates process data from multiple slave process modules via a local communication server. This process data includes at least one of the following: process running status, master station interaction data, and log information. The process data is then standardized to generate control feedback information. Finally, this control feedback information is sent to the data service remote management application via a remote communication server.

[0068] For example, the slave management module is 104Slave Manager (104SM), which is independently deployed on the local IEC 104 slave communication server of each power plant. It adopts a dual-server design. The local communication server uses a local TCP port to establish persistent connections with all 104Slave slave communication processes on the local machine. It is responsible for collecting the running status of each process, master station interaction data, and log information, while receiving and executing process control instructions issued by the front end.

[0069] The remote communication server can establish a connection with the remote management application of the data service through a dual-network redundant link, based on a fixed listening port, to achieve command forwarding, data uploading, and configuration file transmission. As the intermediate hub between the front-end and slave communication processes, the 104SM can parse front-end commands and convert them into control signals recognizable by the local processes. Simultaneously, it aggregates data from various local processes, standardizes and encapsulates it, and uploads it to the front-end, achieving one-to-many centralized management.

[0070] It should be noted that the dual-network redundancy architecture in the above example is used to illustrate network communication connection. A single-network dual-link bonding architecture, such as LACP link aggregation, and a ring redundancy network architecture, such as PROFINET MRP, can also be used. A combination architecture of dual power supply redundancy and single network backup can also be used to achieve redundancy protection for communication links or power supply.

[0071] In some embodiments, the slave process module can run in parallel on each communication server, with each process corresponding to the communication needs of one master station. Process creation and deletion can be flexibly implemented through front-end process management commands. Correspondingly, the slave management module is also configured to obtain master station communication requirement information, which includes communication requirements for at least one master station.

[0072] like Figure 4 As shown, when the slave station management module obtains the master station's communication requirement information, it can read the control target from the process control instructions. The control target includes at least one of a process to be created and a process to be deleted. If the control target includes a process to be created, the slave station process module is configured based on the process to be created, and a persistent connection is established between the newly configured slave station process module and the local communication server. If the control target includes a process to be deleted, the slave station process module corresponding to the process to be deleted is closed.

[0073] After obtaining the master station's communication requirements information, the slave station management module can parse the number of communication requirements from the master station's communication requirements information and create slave station process modules based on the number of communication requirements. Each slave station process module corresponds to one master station's communication requirement.

[0074] For example, the slave process module can be deployed locally on each communication server in a multi-process parallel running deployment mode, forming a 104Slave slave communication process. Each process corresponds to the communication needs of a 104 master station and can be flexibly created or deleted through the front end.

[0075] like Figure 5As shown, for data forwarding tasks, in some embodiments, the slave station management module is further configured to receive and respond to data forwarding instructions reported by the remote management device. The acquisition of monitoring data includes at least one of remote signaling data, telemetry data, and remote control instructions. The monitoring data is then sent to the local management client via the local communication server, so that the monitoring data can be reported to the master station via the master station communication server.

[0076] For example, the master station communication server in the slave station process module can strictly follow the IEC 104 protocol standard to establish communication connections with different master stations in the power plant, such as the dispatch master station and the plant-level monitoring master station, so as to realize the transmission of remote signaling and telemetry data, and the reception and execution of remote control or remote adjustment commands. In addition, the master station communication server can also support message encryption and integrity verification.

[0077] The local management client in the slave process module establishes a persistent connection with the local communication server of the local 104SM to report its own running status (such as start, stop, and abnormal running status), master station interaction data (such as the number of bytes sent and the number of control commands sent), and protocol message logs. The local management client can also receive front-end control commands forwarded by 104SM, such as restarting processes and updating point tables.

[0078] like Figure 6 As shown, for fault diagnosis tasks, in some embodiments, the system further includes a communication network device. The master station can establish a network communication connection with the communication server through the communication network device, and the remote management device can also establish a network communication connection with the communication server through the communication network device. The network communication connection established based on the communication network device includes a primary path and at least one backup path. The communication network device is configured with multi-network redundancy, enabling it to diagnose network communication faults by executing fault diagnosis tasks. For this purpose, the slave station management module is also configured to receive fault diagnosis instructions reported by the remote management device and, in response to the fault diagnosis instructions, detect the communication connection status of the primary path. When the communication connection status of the primary path indicates a fault, a path switching instruction is sent to the communication network device to control the communication network device to switch to the backup path.

[0079] For example, communication network equipment can be used to provide data transmission channels between devices. To this end, communication network equipment can be switches or routers, supporting industrial Ethernet communication to provide stable network connectivity. Communication network equipment can be configured with multi-network redundancy functions, such as RSTP and VRRP protocols. Furthermore, it supports network redundancy switching devices, automatically switching to a backup path when the primary path fails.

[0080] Communication network equipment can also support wireless communication, meaning that the communication network equipment includes a wireless communication module for backup communication channels in certain scenarios, such as 4G or 5G communication modules.

[0081] In some embodiments, the system further includes a data storage device connected to a communication server. To achieve data storage, the slave management module is further configured to acquire data to be stored, which includes system runtime data, log files, and configuration files. The data to be stored is then sent to the data storage device for storage.

[0082] For example, data storage devices are used to store system operation data, log files, configuration files, etc. Data storage devices can be local storage devices, with each communication device (slave or 104Slave Manager) equipped with local storage to save operation logs and configuration files. Data storage devices can also be remote storage servers, used to centrally store communication data from all slave and master stations for unified analysis and management.

[0083] Furthermore, in some embodiments, the system may also include redundant power supplies and protection devices to ensure continued operation during power fluctuations or failures. The redundant power supplies and protection devices may be uninterruptible power supplies (UPS) that provide backup power for critical equipment such as 104 communication servers. The redundant power supplies and protection devices may also have built-in overvoltage protection modules to prevent damage to communication equipment due to power problems.

[0084] By applying the technical solutions of the above embodiments, the power plant slave communication monitoring system described in the above embodiments can simplify the configuration and debugging process of plant communication for engineers, while facilitating real-time monitoring of communication status by operators. It not only effectively saves labor costs but also further improves the communication efficiency between the master station and the power plant, demonstrating significant application value.

[0085] Furthermore, relying on a centralized management system for both the "front-end" and "back-end," remote unified management of multiple communication servers can be achieved. Operations such as downloading and modifying configuration files, upgrading programs, and starting and stopping processes can be completed without on-site access. The visual front-end interface intuitively presents communication status and data details, improving debugging efficiency and significantly optimizing operation and maintenance efficiency. Remote maintenance also reduces on-site transportation and labor costs, while redundant architecture and fault warning mechanisms reduce production losses caused by communication failures. Standardized management processes and log traceability reduce equipment damage caused by operational errors, extend the lifespan of the communication system, and achieve full lifecycle cost optimization.

[0086] The system also allows for enhanced management precision, supporting tiered log printing by master station and time, and enabling remote real-time viewing and downloading of communication message logs. It centrally collects and processes master station information and uplink / downlink data from multiple servers, achieving standardized configuration and global status monitoring, thus avoiding operational omissions and configuration inconsistencies caused by decentralized management.

[0087] Furthermore, the system boasts strong scalability and compatibility. The backend communication management server reserves interfaces with power plant systems such as Distributed Control Systems (DCS), allowing for flexible integration of new communication servers and equipment to meet power plant expansion needs. It is compatible with multiple power communication protocols, primarily IEC 104, enabling adaptation to different brands of equipment and distributed deployment scenarios, thus reducing system upgrade and integration costs.

[0088] This application also provides a computer device, specifically a personal computer, server, network device, etc. The computer device includes a bus, processor, memory, and communication interface, and may also include input / output interfaces and a display device. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database of the computer device stores location information. The network interface of the computer device is used for communication with external terminals via a network connection. When the computer program is executed by the processor, it implements the steps in the various method embodiments.

[0089] Those skilled in the art will understand that the structure of the computer device described above is only a partial structure related to the solution of this application, and does not constitute a limitation on the computer device to which the solution of this application is applied. A specific computer device may include more or fewer components, or combine certain components, or have different component arrangements.

[0090] In one embodiment, a computer-readable storage medium is also provided, which may be non-volatile or volatile, and a computer program is stored thereon, which, when executed by a processor, implements the steps in the above method embodiments.

[0091] In one embodiment, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0092] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0093] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods.

[0094] Any references to memory, database, or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc.

[0095] Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can take many forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0096] The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchain. The processors involved in the embodiments provided in this application may be, but are not limited to, general-purpose processors, graphics processors, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc.

[0097] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0098] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A power plant slave communication monitoring system, characterized in that, The system includes: a main station, a communication server, and remote management devices; the main station establishes a network communication connection with the communication server; the communication server establishes a network communication connection with at least one of the remote management devices; The remote management device is equipped with a data service remote management application; the remote management device is configured to form a front-end operation entry by running the data service remote management application, and to receive user interaction operations through the front-end operation entry. The communication server includes a slave station management module and multiple slave station process modules; the slave station management module has a built-in dual-server architecture, including a local communication server and a remote communication server; the local communication server is used to establish connections with the multiple slave station process modules within the communication server to achieve centralized management and control; the remote communication server is used to interface with the data service remote management application. The slave process module adopts a dual-end architecture; the slave process module includes a master station communication server and a local management client; the master station communication server is used to communicate with the master station in accordance with the communication protocol standard; the local management client is used to establish a persistent connection with the slave management module through a local link to realize process status reporting and command reception. The slave station management module is configured as follows: Acquire slave communication data, which includes instruction data obtained through a remote communication server and monitoring data obtained through a local communication server; The core tasks are performed based on the slave communication data, and the core tasks include at least one of data forwarding, process management, and fault diagnosis.

2. The system according to claim 1, characterized in that, The remote management device is also configured to: The interface displays a visual interactive interface, which includes a communication process list. The communication process list is used to display at least one of the following: process ID, running status, associated master station, and master / standby status information. Receive interactive operations input by the user based on the visual interactive interface; In response to the interaction operation, operation information is extracted from the interaction operation, the operation information including operation type and operation object; The backend network connection and interface response are executed based on the operation information.

3. The system according to claim 2, characterized in that, The remote management device is configured to perform backend network connection and interface response based on the operation information, and is also configured to: The communication target information is obtained based on the operation information. The communication target information is the information input by the user when performing the interactive operation. The communication target information includes the IP address of the target communication server, the target domain number, and the target station number. The communication target information is sent to the slave station management module to trigger the slave station management module to select the slave station process module according to the communication target information, and to establish a network communication connection with the master station through the slave station process module; After establishing a network communication connection, the connection result display interface is shown.

4. The system according to claim 1, characterized in that, The slave station management module is also configured as follows: The remote communication server listens to a fixed port to establish a network communication connection with the data service remote management application based on a dual-network redundant link; Obtain the process control instructions uploaded by the remote management device; In response to the process control command, the process control command is parsed, and a process control signal recognizable by the slave process module is generated based on the process control command; Based on the process control signal, the local communication server collects and summarizes process data of multiple slave process modules. The process data includes at least one of process running status, master station interaction data, and log information. The process data is standardized to generate control feedback information; The control feedback information is sent to the data service remote management application via the remote communication server.

5. The system according to claim 4, characterized in that, The slave station management module is also configured as follows: Obtain master station communication requirement information, wherein the master station communication requirement information includes communication requirements for at least one of the master stations; The number of communication requests is parsed from the main station's communication request information; The slave process module is created according to the number of communication requirements, and each slave process module corresponds to one communication requirement of the master station.

6. The system according to claim 5, characterized in that, The slave station management module is configured to retrieve the master station's communication requirements information and is also configured to: Read the control target from the process control instruction, the control target including at least one of the process to be created and the process to be deleted; If the control target includes the process to be created, the slave process module is set based on the process to be created, and a persistent connection relationship is established between the newly set slave process module and the local communication server. If the control target includes the process to be deleted, shut down the slave process module corresponding to the process to be deleted.

7. The system according to claim 1, characterized in that, The slave station management module is also configured as follows: Receive the data forwarding instruction reported by the remote management device; In response to the data forwarding instruction, monitoring data is acquired, wherein the monitoring data includes at least one of remote signaling data, telemetry data, and remote control instructions; The monitoring data is sent to the local management client through the local communication server, and then reported to the main station through the main station communication server.

8. The system according to claim 1, characterized in that, The system also includes communication network equipment; the main station establishes a network communication connection with the communication server through the communication network equipment; the remote management device establishes a network communication connection with the communication server through the communication network equipment; The network communication connection established based on the communication network device includes a primary path and at least one backup path; the communication network device is configured with multi-network redundancy functionality; the slave station management module is further configured to: Receive fault diagnosis instructions reported by the remote management device; In response to the fault diagnosis command, the communication connection status of the main path is detected; When the communication connection status of the primary path is in failure, a path switching command is sent to the communication network device to control the communication network device to switch to the backup path.

9. The system according to claim 1, characterized in that, The system also includes a data storage device connected to the communication server; the slave station management module is further configured to: Acquire the data to be stored, which includes system running data, log files, and configuration files; The data to be stored is sent to the data storage device to store the data.

10. A power plant slave station communication monitoring method, characterized in that, Applied to the system according to any one of claims 1-9; the method comprises: Acquire slave communication data, which includes instruction data obtained through a remote communication server and monitoring data obtained through a local communication server; The core tasks are performed based on the slave communication data, and the core tasks include at least one of data forwarding, process management, and fault diagnosis.

Images