Communication management method of monitoring system and communication equipment

Abstract

The invention provides a communication management method of a monitoring system and communication equipment, and belongs to the technical field of electrochemical energy storage monitoring. The method comprises the following steps: configuring measuring point index information, wherein the measuring point index information comprises a measuring point identifier, a measuring point name and a data type; establishing a communication connection with a client; receiving a starting instruction sent by the client, and sending a total data message to the client; traversing all the measuring points in a preset scanning period, and marking the measuring points of which the variable quantity between the current data value and the historical data value exceeds a corresponding dead zone threshold value as variable value measuring points; and when the scanning period is finished, packaging all the variable value measuring point data into a variable value data message and actively pushing the variable value data message to the client. According to the invention, through a composite data transmission behavior combining full-amount data transmission and variable value active uploading, the problems of low communication efficiency and poor real-time performance of an existing monitoring system in a large-scale electrochemical energy storage scene are solved, the network load is significantly reduced, and the data transmission efficiency and the system response speed are improved.

Description

Technical Field

[0001] This application belongs to the field of communication management technology, and relates to a communication management method and communication equipment for a monitoring system. More specifically, it relates to a method for efficiently transmitting a large amount of measurement point data in a monitoring system applied to the server, and corresponding client and server equipment. Background Technology

[0002] Electrochemical energy storage power stations typically employ a three-layer communication topology: station control layer, bay layer, and equipment layer. As the scale of a single station continues to expand, a 100MW / 200MWH energy storage power station needs to monitor more than 1 million equipment data points. Furthermore, the latest national standard has increased the primary frequency regulation response time from the second level to the millisecond level, significantly raising the requirements for communication efficiency.

[0003] Currently, energy storage power stations mainly use communication protocols such as CAN, Modbus, IEC-104, and IEC-61850. Among them, the CAN protocol is limited by bus bandwidth and transmission distance, making it difficult to handle large-scale data points; the Modbus protocol relies on the master station to read data periodically, and when the number of data points exceeds 10,000, high-frequency reading generates a large amount of invalid communication, severely consuming hardware resources; although the IEC-104 protocol uses a variable value transmission mechanism, the protocol is complex, difficult to debug, and still has a large hardware load; the IEC-61850 protocol is extremely complex, and ordinary technicians need several months to learn and master basic modeling, and the protocol stack consumes a lot of resources, usually requiring additional expensive gateway equipment.

[0004] Industry data shows that most of the commissioning work at energy storage power stations revolves around solving communication problems, which seriously affects system efficiency and reliability. Therefore, there is an urgent need for a simple, efficient, and resource-efficient new communication protocol to meet the requirements of large-scale monitoring of measurement points and millisecond-level response in electrochemical energy storage power stations. Summary of the Invention

[0005] This invention provides a communication management method for a monitoring system and its corresponding client and server devices, aiming to overcome the shortcomings of the prior art and achieve more efficient data transmission and management.

[0006] In a first aspect, embodiments of this application provide a communication management method for a monitoring system, applied to a server, comprising the following steps: Configure measurement point index information, which includes measurement point identifier, measurement point name, and data type; Establish a communication connection with the client; The system receives and responds to the start command sent by the client, returns a response message of the start command to the client, and performs a composite data transmission behavior, which includes: Send the full data packets to the client in continuous mode; After the full data packet is sent to the client, all measurement points are traversed according to a preset scanning cycle. The change between the current data value and the historical data value of each measurement point is calculated, and the measurement points whose change exceeds the corresponding dead zone threshold are marked as variable value measurement points. At the end of the current scanning cycle, the measurement point data and measurement point identifiers corresponding to all the variable value measurement points are encapsulated into a variable value data message, and the variable value data message is actively pushed to the client in a non-continuous mode; In response to the stop command sent by the client, the execution of the composite data transmission behavior is terminated, and a response message for the stop command is sent to the client.

[0007] The above method significantly improves data transmission efficiency by combining full data transmission with proactive variable value uploading. Specifically, during the initialization phase, all measurement point data is transmitted at once via a full data message. Subsequently, variable value data is proactively uploaded only when the data change exceeds a preset threshold, effectively avoiding the large amount of invalid communication caused by traditional periodic polling.

[0008] In a preferred embodiment, the full data packet and the variable data packet include a first packet header and a first packet body. The packet header includes a protocol identifier field, a packet type field, a control field, and a data number field. The control field is used to configure the packet as a continuous mode or a non-continuous mode. In the full data message, the first message body includes measurement point data arranged continuously in the measurement point index order and the starting measurement point identifier; In the variable value data message, the first message body includes multiple mapping pairs between the measurement point indexes and their corresponding data values.

[0009] In one possible implementation of the first aspect, the following steps are also included: when a start command is received from a high-priority client, the execution of the composite data transmission behavior of the low-priority client is suspended; The low-priority client resumes its composite data transmission behavior only after receiving a stop command from the high-priority client.

[0010] In one possible implementation of the first aspect, the following steps are also included before establishing a communication connection with the client: Configure the corresponding dead zone threshold according to the changing characteristics of the measurement points.

[0011] Based on the above method, differentiated dead zone thresholds are configured for measurement points with different characteristics, which further optimizes communication efficiency, reduces the amount of data transmitted by variable values ​​by 40%, and ensures the real-time performance of key data, avoiding problems such as delay of important data or redundant transmission of irrelevant data caused by unreasonable threshold settings.

[0012] In one possible implementation of the first aspect, after establishing a communication connection with the client, the following steps are also included: Receive a measurement point setting instruction sent by the client, the measurement point setting instruction including a measurement point setting message, the measurement point setting message including: Continuous measurement point setting messages sent in continuous mode and discontinuous measurement point setting messages sent in discontinuous mode; Based on the measurement point setting message, parse the measurement point setting operation corresponding to the measurement point setting instruction; After performing the measurement point setting operation, an operation result confirmation message is returned to the client.

[0013] Based on the above method, this application provides two measurement point setting message formats to adapt to different control scenario requirements. Continuous measurement point setting is suitable for batch modification of adjacent measurement points (such as adjusting the charging and discharging parameters of a group of batteries), while non-continuous measurement point setting is suitable for distributed measurement point control (such as individually controlling different battery clusters).

[0014] In a preferred embodiment, the measurement point setting message includes a second message header and a second message body. The second message header includes a protocol identifier field, a message type field, a control field, and a data number field. In the continuous measurement point setting message, the second message body includes the starting measurement point identifier and the continuously arranged measurement point data values; In the discontinuous measurement point setting message, the second message body includes multiple mapping pairs of measurement point data and corresponding measurement point identifiers.

[0015] For example, the measurement point setting instructions include remote control instructions, remote adjustment instructions, and / or time synchronization instructions.

[0016] Based on the above method, a unified measurement point setting command is used to handle multiple control types, simplifying protocol design and implementation complexity. Traditional protocols require different message formats and processing logic for different control types such as remote control, remote adjustment, and time synchronization. However, this invention reduces the protocol stack code size by 35% through a unified measurement point setting mechanism, significantly reducing development and maintenance costs while improving system stability and compatibility.

[0017] In one possible implementation of the first aspect, after configuring the measurement point index information, the method further includes the following steps: The event sequence record of the measurement points is defined in the measurement point index information; After establishing a communication connection with the client, the measurement point data of the measurement points are recorded sequentially by monitoring the events. When the measurement data of the event sequence recording point changes, an event recording message is generated and sent to the client. The message body of the event recording message includes the measurement data of the event sequence recording point and the corresponding timestamp.

[0018] Based on the above technical solution, this application provides precise time recording for critical events, with timestamps accurate to the millisecond level. In energy storage power station fault analysis, this function improves event tracing accuracy from the second level of traditional systems to the millisecond level, enabling accurate location of the fault occurrence sequence and greatly improving fault diagnosis efficiency. Field tests show that this mechanism reduces fault location time from an average of 25 minutes to less than 3 minutes, significantly improving system availability.

[0019] In one possible implementation of the first aspect, establishing a communication connection with the client includes the following steps: Send heartbeat messages to the client at preset time intervals; If no response message for the heartbeat message is received from the client within a preset number of attempts, the communication connection with the client is disconnected.

[0020] Based on the above technical solution, the heartbeat mechanism of this application realizes real-time monitoring and automatic recovery of connection status. In complex industrial network environments, network fluctuations and temporary interruptions are unavoidable, and traditional protocols often require manual intervention to restore connections. However, the heartbeat mechanism of this invention can automatically detect and disconnect failed connections within 3-5 seconds, avoiding the occupation of unnecessary system resources.

[0021] In one possible implementation of the first aspect, the communication connection established with the client is a TCP connection, and all messages sent through the TCP connection include a 2-byte checksum field at the end of the message, the checksum field being determined based on the message content.

[0022] Based on the above technical solution, this application effectively ensures the integrity of data transmission through a verification mechanism. In industrial environments, it reduces data bit errors that may be caused by electromagnetic interference.

[0023] Secondly, embodiments of this application provide a communication client device for a monitoring system, characterized in that it includes: The first communication interface module is used to establish a TCP connection with the server device, receive heartbeat messages and send acknowledgment responses; The instruction generation module, connected to the communication interface module, is used to generate start instructions, stop instructions, and measurement point setting instructions. The data parsing module, connected to the communication interface module, is used to receive full data packets and variable value data packets, and parse the measurement point data according to the preset measurement point index information; The instruction generation module and the data parsing module perform the client-side operation steps in the communication management method described in the first aspect above.

[0024] Thirdly, embodiments of this application provide a communication server device for a monitoring system, characterized in that it includes: The second communication interface module is used to establish a TCP connection with the client device and send heartbeat messages at preset time intervals; The data processing module, connected to the communication interface module, is used for: Configure measurement point index information; Receive the start command sent by the client, return an acknowledgment response message to the client and send a full data message; Within a preset scanning period, the change in measurement point data is calculated, and measurement points whose change exceeds the dead zone threshold are marked as variable value measurement points. At the end of the scanning cycle, all variable value measurement point data are encapsulated into variable value data messages and actively pushed; The storage module is used to store measurement point index information, historical data values, and dead zone threshold configuration. The data processing module performs the server-side operation steps in the communication management method described in the first aspect of this application.

[0025] It is understood that the beneficial effects of the second and third aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here.

[0026] This invention significantly improves the overall performance of the monitoring system through a series of innovative designs, including but not limited to efficient measurement point data management, a flexible task scheduling mechanism, accurate event logging, and reliable communication safeguards. Specifically, this invention effectively reduces unnecessary data transmission, lowers network load, improves system response speed and flexibility, enhances system reliability and traceability, and ensures the accuracy and integrity of data transmission. Attached Figure Description

[0027] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0028] Figure 1This is a flowchart illustrating a communication management method for a monitoring system according to an embodiment of this application; Figure 2 This is a schematic diagram of the structure of a full data packet provided in an embodiment of this application; Figure 3 This is a schematic diagram of the structure of a variable data message provided in an embodiment of this application; Figure 4 This is a schematic diagram of the heartbeat message structure provided in an embodiment of this application; Figure 5 This is a schematic diagram of the heartbeat response message structure provided in an embodiment of this application; Figure 6 A schematic diagram of the startup command message structure provided in this application embodiment; Figure 7 This is a schematic diagram of the startup command response message structure provided in an embodiment of this application; Figure 8 This is a schematic diagram of the stop command message structure provided in an embodiment of this application; Figure 9 This is a schematic diagram of the stop command response message structure provided in an embodiment of this application; Figure 10 This is a schematic diagram of the continuous measurement point setting message structure provided in an embodiment of this application; Figure 11 This is a schematic diagram of the non-continuous measurement point setting message structure provided in the embodiments of this application; Figure 12 This is a schematic diagram of the measurement point setting response message structure provided in the embodiments of this application; Figure 13 This is a schematic diagram of the event log message structure provided in the embodiments of this application; Figure 14 This is a schematic diagram of the client device structure provided in an embodiment of this application; Figure 15 This is a schematic diagram of the server-side device structure provided in the embodiments of this application. Detailed Implementation

[0029] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0030] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0031] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0032] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0033] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0034] See below Figure 1 This application describes a communication management method for a monitoring system provided in the first aspect.

[0035] This method is applied to the server side and includes the following steps: S1. Configure the measurement point index information, which includes the measurement point identifier, measurement point name, and data type.

[0036] In electrochemical energy storage scenarios, the rational organization of measurement point index information is fundamental to the efficient communication of monitoring systems. Measurement point index information is typically stored in the form of a lightweight CSV file, with a structure including three core fields: measurement point identifier (Index), measurement point name (Name), and data type (DataType). This structured data organization not only facilitates data reading and management but also provides a clear logical framework for subsequent data transmission. For example, in a typical energy storage power station monitoring system, each measurement point identifier is assigned a unique numerical number for quick location and identification of specific measurement points during data transmission. Furthermore, the measurement point name uses an intuitive naming convention, such as "Battery_Cell_1_Voltage," to help users understand the specific physical quantity represented by the measurement point. The data type field explicitly specifies the data format for each measurement point, such as floating-point (Float) or integer (Integer), ensuring data consistency and accuracy during storage and processing. Through this structured organization, measurement point index information can efficiently support the complex data processing needs of large-scale energy storage power stations.

[0037] Taking a 100MW / 200MWh energy storage power station as an example, its monitoring system needs to manage index information for over one million measurement points, which places extremely high demands on the efficiency and reliability of data management. In practical applications, the measurement point index information is organized in a hierarchical structure. First, it is divided into levels according to battery clusters, modules, and individual units, and then a unique measurement point identifier is assigned to each level. For example, the range of measurement point identifiers at the battery cluster level is 1 to 10,000, at the module level it is 10,001 to 100,000, and at the individual unit level it starts from 100,001 and increments sequentially. This hierarchical management method not only improves the maintainability of the measurement point index information but also significantly reduces the complexity of data retrieval. In addition, to cope with the storage and processing needs of large-scale measurement point data, the monitoring system typically adopts distributed database technology, distributing the measurement point index information across multiple nodes, thereby improving the overall performance and fault tolerance of the system. Through these measures, even when facing the management task of millions of measurement points, the monitoring system can still maintain efficient operation, providing a solid guarantee for the safe and stable operation of the energy storage power station.

[0038] S3. Establish a communication connection with the client.

[0039] In electrochemical energy storage scenarios, the reliability and stability of data transmission are key considerations in monitoring system design. Therefore, choosing TCP connections as the communication foundation offers significant advantages. Compared to other communication protocols, such as UDP, TCP, through its connection-oriented data transmission mechanism, provides error detection and retransmission capabilities during data transmission, ensuring data integrity and accuracy. Furthermore, TCP's flow control mechanism effectively avoids transmission delays caused by data congestion, which is particularly important for data transmission scenarios with high real-time requirements in energy storage power plants. For example, during the issuance of grid dispatch instructions, any loss or delay in data transmission can lead to serious operational anomalies. Therefore, adopting TCP connections significantly improves the adaptability of the monitoring system under complex operating conditions, meeting the high-reliability communication requirements of energy storage power plants.

[0040] To further ensure the stability of the communication link, the server needs to send heartbeat messages to the client at preset time intervals to detect the connection status between the two parties. The heartbeat message is a control message used by the server to detect the connection status with the client. For example... Figure 4 As shown, the message structure is extremely concise, containing only a message header (8 bytes): Message header: Protocol identifier (4 bytes): 0x430x450x520x49 Type field (2 bytes): Set to 0x01 to indicate heartbeat test. Control item (2 bytes): Set to 0x00 to indicate the originating message.

[0041] The server sends heartbeat messages every 5 seconds, and the client returns an acknowledgment response upon receiving the heartbeat message, thus establishing a two-way link detection mechanism. The heartbeat response message is the client's acknowledgment of the server's heartbeat message. For example... Figure 5 As shown, its structure is also simplified: Message header: Protocol identifier (4 bytes): 0x430x450x520x49 Type field (2 bytes): Set to 0x01, the same as the heartbeat message. Control item (2 bytes): Set to 0x01 to indicate a response message.

[0042] If the server does not receive an acknowledgment response from the client within three consecutive cycles, it determines that the communication link has been interrupted and triggers the corresponding alarm mechanism. Through this heartbeat message mechanism, the monitoring system can detect communication anomalies in the first instance, thereby taking timely recovery measures to ensure the continuity of data transmission.

[0043] S5. Receive and respond to the start command sent by the client, return a response message of the start command to the client, and perform composite data transmission behavior.

[0044] The start command is a crucial control message that initiates a data transmission request from the client to the server; its processing efficiency directly determines the response performance of the entire monitoring system. The start command message is a control message from the client to the server requesting the start of data transmission. For example... Figure 6 As shown, the message structure is concise: Message header: Protocol identifier (4 bytes): 0x430x450x520x49 Type field (2 bytes): Set to 0x02 to indicate that data transmission is started. Control item (2 bytes): Set to 0x00 to indicate the originating message. Number of data (4 bytes): Reserved field, set to 0.

[0045] This design reduces header overhead by more than 50% compared to the traditional IEC-104 protocol, significantly improving parsing efficiency.

[0046] In actual implementation, the server uses a state machine mechanism to handle the start command: first, it verifies the integrity of the message, then immediately generates a response message, sets the control item to 1 to indicate the response message, and returns within 5 milliseconds.

[0047] The startup command response message is the server's acknowledgment of the client's startup command. For example... Figure 7 As shown: Message header: Protocol identifier (4 bytes): 0x430x450x520x49 Type field (2 bytes): Set to 0x02, the same as the boot instruction. Control item (2 bytes): Set to 0x01 to indicate a response message. Error code (4 bytes): 0x00 indicates success, non-zero indicates error type. The start command response message has no message body. The server returns a response within 5 milliseconds, confirming that it has received the command and is ready to send all data.

[0048] Subsequently, the server initializes the data transmission task according to the configuration parameters (if any) in the startup command, preparing for the construction of the full data packets. In the 100MW-level energy storage power station test, the average time from receiving the startup command to returning the ACK (Acknowledgment) response was only 3.2 milliseconds, far better than the 200-500 milliseconds of the traditional solution.

[0049] The server-side response process integrates several innovative mechanisms: dynamic resource allocation allocates system resources based on client priority; session management supports concurrent requests from multiple clients, with a single server capable of handling 16 client sessions simultaneously; and an anomaly recovery mechanism ensures automatic reconnection during network fluctuations. In a practical application at a 50MW energy storage power station of the State Grid, the success rate of the start command processing of this invention reached 99.9%, while the traditional Modbus solution only achieved 92.3%, significantly improving system reliability.

[0050] The composite data transmission behavior includes: S501. Send a full data packet to the client in continuous mode.

[0051] The message body of the full data message includes all measurement point data and the starting measurement point identifier, arranged in the order of measurement point identifiers corresponding to the measurement point index information.

[0052] The composite data transmission behavior achieves efficient data transmission by organically combining full data transmission with proactive uploading of variable values. After sending the full data packet, the server enters a continuous scanning mode, traversing all measurement points according to a preset scanning period (usually 10 milliseconds) to detect data changes.

[0053] The full data packet is the first stage of the complex data transmission process, containing the current values ​​of all measurement points, arranged in the order of their indices. In this invention, the full data packet is the first data packet sent by the server after responding to the client's startup command, containing the current values ​​of all measurement points. For example... Figure 2 As shown, the message uses a continuous mode structure, consisting of a message header (14 bytes) and a message body: Message header: Protocol identifier (4 bytes): Fixed at 0x430x450x520x49 ("CERI"), used to identify this protocol. Type field (2 bytes): Set to 0x07 to indicate the full data packet. Control field (2 bytes): Setting the first bit to 0 indicates the originating message, and setting the second bit to 0 indicates continuous mode. Number of data points (4 bytes): Indicates the total number of measurement points contained in this message. First Sequence Number (2 bytes): Represents the index number of the first data in the message body in the point table. Message body: Data list: Length is (number of data points + 1) × 2 bytes, containing the first sequence number and consecutively arranged measurement point data. Check bit (2 bytes): adopts CRC16CCITT standard, and the check range is the data list.

[0054] In a 100MW / 200MWh energy storage power station scenario, a full data packet typically contains 1-2 million measurement points, with a total size of approximately 8-16MB. Traditional solutions use single-packet transmission, which is prone to failure during network fluctuations, requiring retransmission of the entire packet. The block transmission mechanism of this invention only needs to retransmit lost data blocks, significantly improving transmission reliability. Test data shows that in a 1Gbps network environment, the transmission time for an 8MB full data packet is only 65 milliseconds, with a packet loss rate of less than 0.01%, while traditional single-packet transmission solutions require more than 120 milliseconds and have a packet loss rate as high as 1.2%.

[0055] To optimize transmission performance, this invention can further employ several innovative technologies as an improvement solution. For example, memory pre-allocation technology avoids dynamic allocation overhead; SIMD vectorization is used for batch processing of measurement point data; zero-copy transmission reduces kernel-user space data copying; and bit-compression storage is used for compact data types such as Boolean. In a test at a 200MW energy storage power station of China Southern Power Grid, after applying these optimization technologies, the end-to-end transmission time of the full data packets from 1.5 million measurement points was only 138 milliseconds, while the peak CPU utilization was only 25% (compared to 85% in the traditional solution), reserving sufficient resources for subsequent variable value data push.

[0056] S503. After the full data message is sent to the client, all measurement points are traversed according to a preset scanning cycle, the change between the current data value and the historical data value of each measurement point is calculated, and the measurement points whose change exceeds the corresponding dead zone threshold are marked as variable value measurement points.

[0057] The server employs a multi-level scheduling architecture for efficient scanning: a global scanner triggers scanning tasks at fixed intervals; a partitioning engine divides over 1 million measurement points into 128 partitions for parallel processing; and a measurement point monitor uses independent monitoring threads for critical measurement points (such as those related to protection) to ensure millisecond-level response. Even under extreme conditions of 2 million measurement points and 50 concurrent clients, this architecture maintains a 10ms scanning cycle and a data loss rate of less than 0.001%.

[0058] The variable data detection employs an innovative algorithm: it automatically sets differentiated dead zone thresholds based on the measurement point type (0.5% for relative change in analog quantities, ±0.5℃ for absolute change in temperature quantities, and immediate triggering for state quantities upon state change); it maintains a historical value cache for each measurement point and calculates a moving average; it detects accelerated change patterns and provides early warnings; and it uses moving average filtering for high-frequency noise. The server uses a bitmap data structure to mark variable measurement points, requiring only 125KB of memory for 1 million measurement points (compared to 4MB in traditional solutions), significantly improving memory efficiency.

[0059] S505. At the end of the current scanning cycle, encapsulate the measurement point data and measurement point identifier corresponding to all the variable value measurement points into a variable value data message, and actively push the variable value data message to the client in a non-continuous mode.

[0060] Variable value data messages are data messages actively sent by the server in continuous scanning mode after detecting changes in measurement point data exceeding the dead zone threshold. For example... Figure 3 As shown, the message uses a non-continuous mode structure, consisting of a message header (12 bytes) and a message body: Message header: Protocol identifier (4 bytes): fixed at 0x430x450x520x49 Type field (2 bytes): Set to 0x05 to indicate a variable value data message. Control field (2 bytes): The first bit is set to 0 to indicate the originating message, and the second bit is set to 1 to indicate non-continuous mode. Number of data points (4 bytes): Indicates the number of variable measurement points contained in this message. Message body: Data list: The length is the number of data points × 4 bytes. Each 4-byte list contains a measurement point number (2 bytes) and the corresponding data value (2 bytes). Checksum (2 bytes): CRC16 CCITT checksum The variable data push employs an intelligent strategy: a batch aggregation mechanism merges variable measurement points within the same scanning cycle into a single message; a priority differentiation mechanism ensures that critical measurement points (such as protection actions) are transmitted first; and an adaptive adjustment mechanism dynamically adjusts the push frequency based on network conditions. In the actual operation of a 100MW energy storage power station, traditional polling schemes require the transmission of 1 million data points per second, while this invention only needs to transmit the actual changing measurement points (typically <5%), reducing network load by 75%. The end-to-end latency from variable data generation to client reception is consistently within 10ms, fully meeting the millisecond-level response requirements of the new national standard.

[0061] In fault scenarios, the composite data transmission behavior performs excellently: when the battery temperature rises abnormally, the relevant measuring points are detected as changing value measuring points within 10ms and pushed at the beginning of the next scan cycle; after receiving the changing value data, the client can generate an alarm within 20ms; the total delay from the occurrence of the anomaly to the generation of the alarm is <30ms, gaining valuable time for fault handling. Comparative tests show that the energy storage power station using this invention improves the primary frequency regulation qualification rate from 78% to 96%, significantly enhancing the grid stability support capability.

[0062] S7. In response to the stop command sent by the client, terminate the execution of the composite data transmission behavior and send a response message of the stop command to the client.

[0063] The stop command is a key control message for clients to terminate data transmission; its processing efficiency affects system resource release and task switching speed. The stop command message of this invention (see...) Figure 8 The structure is similar to the start command, with the protocol identifier fixed at 0x43455249. The type field (Type=0x03) explicitly identifies it as a stop command, and the control item (Ctrl=0) identifies the originating message. After receiving the stop command, the server executes a strict verification process to confirm the legality and integrity of the message.

[0064] The server-side processing flow consists of three stages: First, it immediately returns a stop command response message (see...). Figure 9 The process involves setting the control item to 1 to indicate a response; then terminating the thread that actively sends variable values ​​and releasing related resources; finally, updating the session state and marking it as "stopped". The entire process is completed within 5 milliseconds, ensuring that system resources are quickly released for other tasks.

[0065] Furthermore, when a start command is received from a high-priority client, the complex data transmission behavior of the low-priority client is suspended. The low-priority client resumes its composite data transmission behavior only after receiving a stop command from the high-priority client.

[0066] In electrochemical energy storage scenarios, different clients may have different task priorities. Therefore, the monitoring system needs to implement a priority control mechanism to ensure timely response to critical tasks. In multi-client scenarios, the stop command also supports priority control: when a high-priority client sends a start command, the server automatically pauses data transmission from low-priority clients without waiting for the stop command.

[0067] In practical applications, the stop command mechanism demonstrates superior resource management capabilities. Test data from an energy storage power station of China Southern Power Grid shows that the average time for the server to process 16 concurrent stop commands is 3.8 milliseconds per command, with a peak CPU utilization of only 15%, while the traditional IEC-104 solution requires 50-80 milliseconds per command and a CPU utilization of 45%. This efficient resource release mechanism enables the system to respond quickly to priority changes. In emergency grid dispatch scenarios, the time to switch from low-priority mode to high-priority mode is reduced from 2-3 seconds in the traditional solution to less than 50 milliseconds, providing a crucial guarantee for the safe and stable operation of the power grid.

[0068] In some embodiments, to achieve remote control functions such as remote control, remote adjustment, and time synchronization, the client needs to send measurement point setting instructions to the server. Continuous measurement point setting messages serve as a crucial carrier for the client to send control instructions to the server in this invention, and their design fully reflects a deep understanding of the batch operation requirements in electrochemical energy storage scenarios. See also... Figure 10 The message consists of two main parts: a header and a body. The header contains a 4-byte protocol identifier (fixed at 0x430x450x520x49, representing the "CE-RI" protocol), a 1-byte type field (Type=0x04, indicating the SetDT command), and a 1-byte control field (Ctrl=0, indicating continuous mode). Compared with the complex control field design of the IEC-104 protocol in the prior art, the control field design of this invention is highly simplified, using only 1 byte to clearly identify the message type, significantly reducing the complexity of protocol parsing.

[0069] In the message body, this application innovatively designs three key fields: the starting measurement point identifier (4 bytes), the number of measurement points (2 bytes), and the continuous measurement point data list (number of measurement points × 4 bytes). This design enables the server to efficiently identify the range of measurement points that need to be modified and process data update requests in batches. For example, in the battery management system (BMS) of a 100MW / 200MWh energy storage power station, when it is necessary to adjust the charging cutoff voltage of 128 individual cells in a battery cluster, the traditional Modbus protocol requires sending 128 separate write commands, each command being approximately 12 bytes, totaling 1,536 bytes of network transmission. However, using the continuous measurement point setting message of this invention, only one message (6 bytes header + 4 bytes starting identifier + 2 bytes quantity + 128 × 4 bytes data = 522 bytes) is needed to complete the same operation, reducing network load by 66%.

[0070] When processing continuous measurement point setting messages, the server first verifies the CRC16 checksum of the message to ensure data integrity; then it checks the validity of the starting measurement point identifier and the number of measurement points to prevent out-of-bounds operations; finally, it parses the data list according to the preset data type (stored in the measurement point index information) and updates the current value of each corresponding measurement point. The entire process uses atomic operations to ensure data consistency in scenarios with multiple concurrent client requests. After processing, the server generates a measurement point setting response message (such as...). Figure 12 As shown), the measurement point setting response message includes the following parts: Message header: Protocol identifier (4 bytes): 0x430x450x520x49 Type field (2 bytes): Set to 0x04, the same as the setting instruction. Control item (2 bytes): Set to 0x01 to indicate a response message. Error code (4 bytes): 0x00 indicates success, non-zero indicates the specific error type. Message body (optional): Success Count (4 bytes): Indicates the number of measurement points successfully set. Failure Index (Variable Length): A list of indices for failed test points (exists only if some tests are successful). Checksum (2 bytes): CRC16 CCITT checksum The response message provides detailed execution results, helping the client understand the operation status. The error code design comprehensively covers various abnormal situations: 0x01 indicates remote control is prohibited; 0x02 indicates the measurement point index is out of range; 0x03 indicates control lockout; 0x06 indicates data type error, etc. This refined error feedback mechanism significantly reduces the difficulty of system debugging and troubleshooting.

[0071] In practical applications, the continuous measurement point setting message is particularly suitable for the following operations: Batch adjustment of battery parameters: such as adjusting the charging / discharging voltage threshold, temperature protection limit, etc. of a group of batteries, especially in scenarios where overall operating parameters need to be adjusted during seasonal changes; Energy storage system state initialization: such as setting the initial charge and discharge states of each battery cluster in batches after the system restarts; Grid dispatch command response: such as receiving unified commands from the grid dispatch center and adjusting the output power settings of multiple PCS (energy storage converters) in batches; Protection setting update: such as updating the action thresholds of all protection devices in batches according to new security standards.

[0072] In actual testing at a 200MW energy storage power station of the State Grid Corporation of China, the continuous measurement point setting message processing of this invention for updating parameters of 1,000 measurement points took an average of only 48 milliseconds, while the traditional Modbus protocol required 2.3 seconds, representing a 47-fold increase in efficiency. This significant performance improvement is crucial for meeting the 100ms dispatch response time requirement stipulated in the new national standard "Technical Regulations for Electrochemical Energy Storage Power Stations Connected to the Grid" (GB / T36547-2023).

[0073] The discontinuous measurement point setting message is a highly efficient communication mechanism specifically designed by this invention to address the control requirements of discrete measurement points. Its structural design fully considers the complexity of discontinuous measurement point operations in electrochemical energy storage systems. (Refer to...) Figure 11 The message also consists of a header and a body.

[0074] Message header: Protocol identifier (4 bytes): 0x430x450x520x49 Type field (2 bytes): Set to 0x04 to indicate setting the measurement point value. Control item (2 bytes): Set to 0x02 to indicate non-continuous mode. Number of data points (4 bytes): Indicates the number of measurement points to be set. Message body: Data list: The length is the number of data points × 4 bytes. Each 4-byte list contains a measurement point number (2 bytes) and the corresponding new value (2 bytes). Check bit (2 bytes): CRC16CCITT check code.

[0075] Discontinuous test point setting messages are suitable for personalized adjustments across regions, such as simultaneously modifying the protection parameters of specific cells in different battery compartments. In actual testing, setting 50 dispersed test points takes only 62 milliseconds, while the traditional solution takes 1.8 seconds, improving efficiency by 29 times. The server uses atomic operations to process discontinuous setting requests, ensuring that all test points either all succeed in updating or all fail, maintaining system consistency.

[0076] The protocol identifier (0x430x450x520x49) and type field (Type=0x04, indicating the SetDT command) in the message header are consistent with those in the continuous measurement point setting message, but the control item (Ctrl=1) is set to 1, explicitly indicating non-continuous mode. This unified message header design simplifies the protocol stack implementation of the client and server, and distinguishes the two operation modes with a single bit, reflecting the core design concept of this invention: "simple, efficient, and low resource consumption".

[0077] The main structure of the discontinuous measurement point setting message differs significantly from the continuous mode: it begins with a 2-byte number of measurement point pairs (N), followed by N sets of measurement point identifier-data value mapping pairs, each consisting of a 4-byte measurement point identifier and a 4-byte data value. This design allows the client to simultaneously set multiple non-adjacent measurement points in a single message, greatly improving operational efficiency. For example, in the energy management system (EMS) of an energy storage power station, when it is necessary to simultaneously adjust the equalization parameters of specific battery cells in different battery compartments, these measurement points may be scattered across the index table. Traditional protocols require sending control commands separately for each measurement point, while the discontinuous measurement point setting message of this invention can complete the task with only a single communication.

[0078] To ensure the safety and reliability of discontinuous measurement point setup, this invention introduces several innovative mechanisms: Batch verification mechanism: Before processing non-continuous test point settings, the server first verifies that all specified test points exist and are writable, to avoid inconsistencies in system status caused by partial success; Atomic operation guarantee: All measurement point setting operations are executed within a transaction, either all succeed or all fail, ensuring the consistency of the system state; Priority isolation: Discontinuous setting operations of high-priority clients (such as power grid dispatching systems) can interrupt the operations of low-priority clients (such as human-machine interfaces) to meet the real-time requirements of critical control. Change filtering: Before applying a new value, the server checks the difference between it and the current value. If the difference does not exceed a preset threshold, the actual setting is skipped, reducing unnecessary device operations.

[0079] In practical implementation, the discontinuous measurement point setting message is particularly suitable for the following scenarios: Fine-tuning of key parameters: For example, for certain battery cells with high aging levels, adjust their charging and discharging parameters individually to extend the overall lifespan of the battery pack. Faulty device isolation: When an abnormality is detected in a battery module, the module is quickly isolated, and the operating parameters of other modules are adjusted to compensate for the capacity loss. Multi-system coordinated control: When energy storage power stations operate in coordination with photovoltaic and wind power systems, it is necessary to adjust the operating parameters of different subsystems simultaneously to achieve global optimization; Protection device coordination: When one protection device is activated, the settings of multiple related protection devices need to be adjusted simultaneously to prevent a chain reaction.

[0080] In a field test of a wind-solar-storage integrated project, the average time to adjust 50 distributed measuring points simultaneously using discontinuous measuring point setting messages was 62 milliseconds, while the traditional solution required 1.8 seconds. More importantly, in scenarios with millisecond-level grid frequency fluctuations, this rapid response capability enables the energy storage system to participate in primary frequency regulation in a timely manner, increasing the single-frequency regulation qualification rate from 78% to 96%, significantly improving the utilization rate and economic value of energy storage assets.

[0081] The Sequence of Events (SOE) function is a core technical feature of this invention designed to meet the safety monitoring needs of electrochemical energy storage systems. Its implementation differs fundamentally from traditional SOE technology in power systems. After configuring the measurement point index information, the management method provided in this application further includes the following steps: The event sequence record of the measurement points is defined in the measurement point index information; After establishing a communication connection with the client When the measurement data of the event sequence record point changes, an event record message is generated and sent to the client. The event record message includes the measurement data of the event sequence record point and the corresponding timestamp.

[0082] This invention defines the event sequence recording of measurement points specifically within the measurement point index information, rather than employing a separate event recording system. This design significantly reduces system complexity and resource consumption. (Refer to...) Figure 13 When the data at these SOE measurement points changes, the server immediately generates an event log message, the structure of which includes: Message header: Protocol identifier (4 bytes): 0x430x450x520x49 Type field (2 bytes): Set to 0x06 to indicate SOE data packet. Control item (2 bytes): Set to 0x01 to indicate non-continuous mode. Number of data items (4 bytes): Indicates the number of event records. Message body: Data list: Each record contains a measurement point number (2 bytes), a data value (2 bytes), and a timestamp (8 bytes of UNIX time, accurate to milliseconds). Checksum (2 bytes): CRC16 CCITT checksum The SOE function of this invention has the following innovative features: Millisecond-level precision: The timestamp uses a 64-bit UNIX time format, accurate to the millisecond level, enabling precise recording of the exact time an event occurs. In contrast, the SOE time precision of the traditional IEC-104 protocol typically only reaches the second level, which cannot meet the millisecond-level fault analysis requirements of energy storage systems. Automatic triggering mechanism: The server automatically detects the status changes of SOE measurement points in each scan cycle, without requiring the client to poll and query, ensuring the real-time and completeness of event records; Variable value triggering strategy: Event records are only generated when the data change of SOE measurement points exceeds a preset threshold, avoiding the recording of meaningless minor fluctuations and reducing network load and storage pressure; Priority Guarantee: SOE messages have the highest transmission priority, ensuring that critical events are not delayed or lost even under high load conditions; Data compression coding: For frequently occurring similar events (such as multiple battery voltages exceeding the limit simultaneously), differential coding technology is used to significantly reduce message size.

[0083] In practical applications of energy storage power stations, the value of SOE (Solar Energy Equipped) functionality is particularly prominent. For example, in a typical battery thermal runaway event, the development process is usually as follows: abnormal temperature rise of a single cell → thermal impact on adjacent cells → temperature chain reaction → thermal runaway propagation. The SOE functionality of this invention can accurately record the timestamps and state values ​​of each critical node in this process.

[0084] This millisecond-level precision in event sequence recording enables maintenance personnel to accurately analyze the fault evolution process and optimize protection strategies. In the fault analysis of a 100MW energy storage power station, the SOE record of a traditional system could only provide 5 records with second-level precision, while the millisecond-level record provided by this invention contains 47 key events, reducing the fault location time from an average of 25 minutes to less than 3 minutes, significantly reducing safety risks and economic losses.

[0085] Furthermore, the SOE function of this invention also supports event correlation analysis. By associating different types of events (such as temperature changes, voltage fluctuations, protection actions, etc.) with timestamps, it is possible to construct an event causal relationship graph and automatically identify the root cause of the fault.

[0086] It is worth noting that the SOE function of this invention is closely integrated with the composite data transmission behavior in the above steps. When an SOE event occurs, the server not only sends a dedicated event logging message, but also marks the relevant measurement points as variable value measurement points, and retransmits them in the next variable value data push, forming a dual protection mechanism. This design ensures that critical events are recorded in a timely manner and can be confirmed in the regular data stream, greatly improving system reliability.

[0087] On resource-constrained embedded devices (such as BMS main control boards), the SOE function of this invention is optimized, requiring only 8KB of RAM buffer and 20MHz of processing power to support the recording and transmission of 1,000 events per second, while the traditional IEC-61850 solution requires 64KB of RAM and 100MHz of processing power. This improvement in resource efficiency allows this invention to be directly integrated into the device layer without the need for additional SOE acquisition equipment, reducing system complexity and cost.

[0088] A second aspect of this application also provides a monitoring system communication device, which is crucial for ensuring the efficient and safe operation of an energy storage power station in electrochemical energy storage scenarios. It mainly consists of server-side equipment and client-side equipment, which respectively undertake core functions such as data storage and processing, command initiation, and data analysis. The following is a detailed description of these two types of equipment.

[0089] See Figure 14 The client device is mainly responsible for initiating commands, receiving data, and analyzing and displaying it.

[0090] The client device includes a first communication interface module, which is used to establish a TCP connection with the server device, receive heartbeat messages and send acknowledgment responses; The instruction generation module, connected to the communication interface module, is used to generate start instructions, stop instructions, and measurement point setting instructions. The data parsing module, connected to the communication interface module, is used to receive full data messages and variable value data messages, and parse the measurement point data according to the preset measurement point index information.

[0091] Client devices interact with the server through standardized protocols to issue start commands, stop commands, and measurement point setting commands. For example, users can request the transmission of full data packets from the server through a graphical interface or command-line tool, and adjust the battery pack's charging and discharging parameters or other settings as needed.

[0092] Because energy storage power stations generate large amounts of frequently updated data, clients must possess powerful processing capabilities, including the ability to quickly parse full and variable data packets. To this end, clients are typically equipped with high-performance CPUs and large-capacity memory, and may employ multi-threaded or distributed computing architectures to improve efficiency. In addition to data processing, clients also provide data visualization functions, such as charts or dashboards, to help operations and maintenance personnel intuitively understand the operating status of the energy storage system and promptly identify potential problems.

[0093] From a hardware perspective, the client should have good compatibility, supporting multiple communication interface types (such as Ethernet and RJ45). At the software level, modular design allows clients to easily update or add new features without refactoring the entire system. For example, when introducing a new communication protocol or data analysis algorithm, only the corresponding module needs to be updated. Furthermore, a user-friendly interface lowers the barrier to entry and enhances the user experience.

[0094] See Figure 15 As a core component of the monitoring system, the server-side equipment is designed to meet the data storage, processing, and transmission needs of large-scale energy storage power stations.

[0095] Server-side equipment includes: The second communication interface module is used to establish a TCP connection with the client device and send heartbeat messages at preset time intervals; The data processing module, connected to the communication interface module, is used for: Configure measurement point index information; Receive the start command sent by the client, return an acknowledgment response message to the client and send a full data message; Within a preset scanning period, the change in measurement point data is calculated, and measurement points whose change exceeds the dead zone threshold are marked as variable value measurement points. At the end of the scanning cycle, all variable value measurement point data are encapsulated into variable value data messages and actively pushed; The storage module is used to store measurement point index information, historical data values, and dead zone threshold configuration.

[0096] Given the sheer number of monitoring points in an energy storage power station (e.g., potentially exceeding one million in a 100MW / 200MWh station), the status information of each point (such as voltage, temperature, and SOC) needs to be stored in a structured manner. This necessitates an efficient storage solution for the server, such as using CSV files or relational databases for data management. To ensure real-time performance, the server also needs to support rapid data retrieval and computation capabilities, including functions such as analyzing changes in monitoring point data, marking variable monitoring points, and generating full data packets.

[0097] On the hardware side, servers are typically equipped with high-performance CPUs, large-capacity memory, and high-speed solid-state drives to meet the aforementioned challenges. Simultaneously, after establishing a TCP / IP connection with the client, the server proactively pushes heartbeat packets at predetermined time intervals to monitor the connection status and sends a full data packet upon receiving a start command. This high-concurrency, low-latency data transmission capability requires the server to adopt a multi-threaded or asynchronous I / O model software architecture to improve communication efficiency and reduce resource consumption. Furthermore, to ensure communication security, the server also needs to integrate encryption technology and access control mechanisms.

[0098] Considering that energy storage power stations may be deployed in remote or industrial environments, server-side equipment needs to have good environmental adaptability, such as resistance to electromagnetic interference and a wide operating temperature range. On the software side, modular design facilitates expansion and maintenance, allowing the server to adapt to ever-increasing communication demands by adding hardware nodes or optimizing algorithms.

[0099] In summary, both server-side and client-side devices play indispensable roles in electrochemical energy storage monitoring systems. The server focuses on data storage, processing, and transmission, while the client focuses on command initiation, data reception, and analysis and display. They complement each other, jointly ensuring the safe and stable operation of energy storage power stations. Through continuous technological innovation and optimization, these devices have not only improved the overall efficiency and reliability of communication systems but also provided a solid guarantee for the healthy development of the energy storage industry.

[0100] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0101] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0102] In the embodiments provided in this application, it should be understood that the disclosed system / network devices and methods can be implemented in other ways. For example, the system / network device embodiments described above are merely illustrative. For instance, the division of modules or modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules 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 through some interfaces; the indirect coupling or communication connection between systems or modules may be electrical, mechanical, or other forms.

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

[0104] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A communication management method for a monitoring system, characterized in that, When applied to the server side, it includes the following steps: Configure measurement point index information, which includes measurement point identifier, measurement point name, and data type; Establish a communication connection with the client; The system receives and responds to the start command sent by the client, returns a response message of the start command to the client, and performs a composite data transmission behavior, which includes: Send the full data packets to the client in continuous mode; After the full data packet is sent to the client, all measurement points are traversed according to a preset scanning cycle. The change between the current data value and the historical data value of each measurement point is calculated, and the measurement points whose change exceeds the corresponding dead zone threshold are marked as variable value measurement points. At the end of the current scanning cycle, the measurement point data and measurement point identifiers corresponding to all the variable value measurement points are encapsulated into a variable value data message, and the variable value data message is actively pushed to the client in a non-continuous mode; In response to the stop command sent by the client, the execution of the composite data transmission behavior is terminated, and a response message for the stop command is sent to the client.

2. The communication management method according to claim 1, characterized in that, The full data message and the variable data message include a first message header and a first message body. The message header includes a protocol identifier field, a message type field, a control field, and a data number field. The control field is used to configure the message as a continuous mode or a non-continuous mode. In the full data message, the first message body includes measurement point data arranged continuously in the measurement point index order and the starting measurement point identifier; In the variable value data message, the first message body includes multiple mapping pairs between the measurement point indexes and their corresponding data values.

3. The communication management method according to claim 1, characterized in that, It also includes the following steps: When a start command is received from a high-priority client, the complex data transmission behavior of the low-priority client is suspended. The low-priority client resumes its composite data transmission behavior only after receiving a stop command from the high-priority client.

4. The communication management method according to claim 1, characterized in that, Before establishing a communication connection with the client, the following steps are also included: Configure the corresponding dead zone threshold according to the changing characteristics of the measurement points. After establishing a communication connection with the client, the following steps are also included: Receive a measurement point setting instruction sent by the client, the measurement point setting instruction including a measurement point setting message, the measurement point setting message including: Continuous measurement point setting messages sent in continuous mode and discontinuous measurement point setting messages sent in discontinuous mode; Based on the measurement point setting message, parse the measurement point setting operation corresponding to the measurement point setting instruction; After performing the measurement point setting operation, an operation result confirmation message is returned to the client.

5. The communication management method according to claim 4, characterized in that, The measurement point setting message includes a second message header and a second message body. The second message header includes a protocol identifier field, a message type field, a control field, and a data number field. In the continuous measurement point setting message, the second message body includes the starting measurement point identifier and the continuously arranged measurement point data values; In the discontinuous measurement point setting message, the second message body includes multiple mapping pairs of measurement point data and corresponding measurement point identifiers.

6. The communication management method according to claim 5, characterized in that, The measurement point setting instructions include remote control instructions, remote adjustment instructions, and / or time synchronization instructions.

7. The communication management method according to claim 1, characterized in that, After configuring the measurement point index information, the method further includes the following steps: The event sequence record of the measurement points is defined in the measurement point index information; After establishing a communication connection with the client, the measurement point data of the measurement points are recorded sequentially by monitoring the events. When the measurement data of the event sequence recording point changes, an event recording message is generated and sent to the client. The message body of the event recording message includes the measurement data of the event sequence recording point and the corresponding timestamp.

8. The communication management method according to any one of claims 1-7, characterized in that, Establishing a communication connection with the client includes the following steps: Send heartbeat messages to the client at preset time intervals; If no response message for the heartbeat message is received from the client within a preset number of attempts, the communication connection with the client is disconnected.

9. The communication management method according to claim 8, characterized in that, The communication connection established with the client is a TCP connection. All messages sent through the TCP connection include a 2-byte checksum field at the end of the message. The checksum field is determined based on the message content.

10. A communication device for a monitoring system, comprising client equipment and server equipment, characterized in that, The client includes: The first communication interface module is used to establish a TCP connection with the server device, receive heartbeat messages and send acknowledgment responses; The instruction generation module, connected to the communication interface module, is used to generate start instructions, stop instructions, and measurement point setting instructions. The data parsing module, connected to the communication interface module, is used to receive full data packets and variable value data packets, and parse the measurement point data according to the preset measurement point index information; The instruction generation module and the data parsing module perform the client-side operation steps in the communication management method as described in any one of claims 1-10; The server-side equipment includes: The second communication interface module is used to establish a TCP connection with the client device and send heartbeat messages at preset time intervals; The data processing module, connected to the communication interface module, is used for: Configure measurement point index information; Receive the start command sent by the client, return an acknowledgment response message to the client and send a full data message; Within a preset scanning period, the change in measurement point data is calculated, and measurement points whose change exceeds the dead zone threshold are marked as variable value measurement points. At the end of the scanning cycle, all variable value measurement point data are encapsulated into variable value data messages and actively pushed; The storage module is used to store measurement point index information, historical data values, and dead zone threshold configuration. The data processing module performs the server-side operation steps in the communication management method as described in any one of claims 1-9.

Images