A coal mine monitoring data synchronization method, device and equipment

Abstract

The embodiment of the specification provides a coal mine monitoring data synchronization method, device and equipment. The scheme comprises the following steps: acquiring coal mine monitoring data collected by a downhole data collection device; grouping each monitoring data according to a monitoring point identifier in the monitoring data to obtain each cache data set; determining a to-be-written cache data set in an idle state based on a synchronization state of each cache data set; judging whether there is safety early warning data in each to-be-written cache data set; if there is, generating early warning shadow data based on the safety early warning data, and writing the early warning shadow data into an early warning table at a ground monitoring platform, wherein original coal mine monitoring data corresponding to the early warning shadow data is retained in a target cache data set, and a write operation is performed on the original coal mine monitoring data according to a data synchronization queue corresponding to each data in the target cache data set. The scheme can take into account both timely reporting of safety early warning data and orderly writing of historical monitoring data.

Description

Technical Field

[0001] This application relates to the field of intelligent processing technology in the coal mining industry, and in particular to a method for synchronizing coal mine monitoring data. This application also relates to a coal mine monitoring data synchronization device and a computing device. Background Technology

[0002] During coal mining, various monitoring devices are typically deployed underground to collect real-time coal mine monitoring data such as production output, equipment operating conditions, and safety environment. The collected monitoring data is then synchronized to the ground monitoring platform so that ground personnel can promptly grasp the underground production status and make decisions.

[0003] Currently, the synchronization of underground coal mine monitoring data to the surface monitoring platform typically employs streaming data synchronization, transmitting the coal mine monitoring data as a continuous data stream to the surface monitoring platform. However, during streaming data synchronization, if data from a particular monitoring point fails to be written successfully, the synchronization of that data stream will be blocked and repeatedly retried. Consequently, data from other monitoring points will also be unable to be transmitted, causing the entire data synchronization process to stall. In other words, in the current streaming data synchronization method, a write failure at a single monitoring point will affect the normal synchronization of data from other monitoring points, making it difficult to guarantee the timeliness of overall data synchronization.

[0004] Furthermore, some data in coal mine monitoring may be safety warning data, such as data on excessive gas levels, excessive carbon monoxide levels, or fan shutdown data. This type of data is directly related to the safety of underground personnel and needs to be detected promptly by the surface monitoring platform. However, in the current data synchronization method, safety warning data is transmitted sequentially in a queue, just like other monitoring data. When there is a large amount of data waiting to be transmitted ahead of the queue containing safety warning data, the safety warning data cannot be reported in a timely manner, which will lead to safety hazards not being detected and dealt with in a timely manner. At the same time, the raw monitoring data needs to be written into the database in an orderly manner according to the collection time sequence to ensure the temporal integrity of the coal mine monitoring data and facilitate subsequent viewing. Therefore, the writing order of coal mine monitoring data should not be disrupted in order to ensure the timely reporting of safety warning data.

[0005] Therefore, how to balance the timely reporting of safety early warning data with the orderly writing of coal mine monitoring data has become an urgent technical problem to be solved. Summary of the Invention

[0006] In view of this, embodiments of this application provide a method, apparatus, and equipment for synchronizing coal mine monitoring data, so as to balance the timely reporting of safety early warning data and the orderly writing of coal mine monitoring data.

[0007] According to a first aspect of the embodiments of this application, a method for synchronizing coal mine monitoring data is provided, characterized in that the method includes: Acquire coal mine monitoring data collected by underground data acquisition equipment, wherein the coal mine monitoring data includes at least monitoring point identifiers; Based on the monitoring point identifiers, the monitoring data of each coal mine are grouped to obtain each cached data set. Determine the synchronization state of each of the cached data sets. The synchronization state includes an idle state and a non-idle state. The idle state indicates that the corresponding cached data set is not currently being synchronously written and no data blocking has occurred. Based on the synchronization state, determine the set of cached data to be written that is in the idle state; Determine whether there is security warning data in each of the sets of data to be written to the cache, and obtain a first determination result. The security warning data is monitoring data that indicates that there is a safety risk in the coal mining process. If the first determination result indicates that the security warning data exists in the target cache data set in each of the cache data sets to be written, then warning shadow data is generated based on the security warning data; The early warning shadow data is written into the early warning table at the ground monitoring platform. The original coal mine monitoring data corresponding to the early warning shadow data is retained in the target cache data set, and the original coal mine monitoring data is written according to the data synchronization queue corresponding to each data in the target cache data set.

[0008] According to a second aspect of the embodiments of this application, a coal mine monitoring data synchronization device is provided, characterized in that the device comprises: The data acquisition module is used to acquire coal mine monitoring data collected by underground data acquisition equipment, wherein the coal mine monitoring data includes at least monitoring point identifiers; The grouping processing module is used to group the monitoring data of each coal mine according to the monitoring point identifier to obtain each cached data set; The state determination module is used to determine the synchronization state of each of the cached data sets. The synchronization state includes an idle state and a non-idle state. The idle state indicates that the corresponding cached data set is not currently being synchronously written and no data blocking has occurred. The module for determining the set of cached data to be written is used to determine the set of cached data to be written that is in the idle state based on the synchronization state. The judgment module is used to determine whether there is security warning data in each of the sets of cached data to be written, and to obtain a first judgment result. The security warning data is monitoring data that indicates that there is a safety risk in the coal mining process. The warning shadow data generation module is used to generate warning shadow data based on the security warning data if the first judgment result indicates that the security warning data exists in the target cache data set in each of the cache data sets to be written. The early warning shadow data writing module is used to write the early warning shadow data into the early warning table at the ground monitoring platform. The original coal mine monitoring data corresponding to the early warning shadow data is stored in the target cache data set, and the original coal mine monitoring data is written according to the data synchronization queue corresponding to each data in the target cache data set.

[0009] According to a third aspect of the embodiments of this application, a computing device is provided, characterized in that it includes: Memory and processor; The memory is used to store computer programs or instructions, and the processor is used to execute the computer programs or instructions. When the computer programs or instructions are executed by the processor, they implement the steps of the above-described coal mine monitoring data synchronization method.

[0010] At least one embodiment in this specification achieves the following beneficial effects: When underground coal mine monitoring data is synchronized to the ground monitoring platform, the coal mine monitoring data is grouped according to the monitoring point identifier to obtain various cached data sets. The system then checks for the presence of safety warning data in the selected cached data sets to be written. When safety warning data is detected in the target cached data set, warning shadow data is generated based on the safety warning data, and this shadow data is preferentially written to the warning table on the ground monitoring platform. This ensures that the safety warning data can be promptly reported to the ground monitoring platform without waiting for the original cached data set to be scheduled. Simultaneously, the original coal mine monitoring data corresponding to the safety warning data remains in the original cached data set, and a write operation is performed on this original coal mine monitoring data according to the data synchronization queue, thereby ensuring the temporal integrity of historical monitoring data. This approach guarantees both the timely reporting of safety warning data and the orderly writing of historical monitoring data, thus achieving a balance between timely response to warning information and orderly synchronization of coal mine monitoring data without interference.

[0011] Furthermore, by grouping coal mine monitoring data according to monitoring point identifiers and maintaining an independent synchronization state for each group, write operations are only performed on the idle cached data set. This ensures that when data writing to a group corresponding to a certain monitoring point is blocked, other idle groups can still synchronize data normally because the synchronization states of each group are independent of each other. This avoids the impact of a single monitoring point's write failure on the overall timeliness of data synchronization, thereby improving the reliability of coal mine monitoring data synchronization. Attached Figure Description

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

[0013] Figure 1 This is a flowchart illustrating a coal mine monitoring data synchronization method provided in the embodiments of this specification; Figure 2 This is a schematic diagram of the structure of a coal mine monitoring data synchronization device provided in the embodiments of this specification; Figure 3 This is a structural block diagram of a computing device provided in the embodiments of this specification. Detailed Implementation

[0014] Numerous specific details are set forth in the following description to provide a full understanding of this application. However, this application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this application. Therefore, this application is not limited to the specific embodiments disclosed below.

[0015] The terminology used in one or more embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the scope of one or more embodiments of this application. The singular forms “a,” “the,” and “the” used in one or more embodiments of this application and in the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” used in one or more embodiments of this application refers to and includes any or all possible combinations of one or more associated listed items.

[0016] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this application, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this application, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0017] 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. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0018] The technical solutions provided in the various embodiments of this specification are described in detail below with reference to the accompanying drawings.

[0019] Figure 1 This is a flowchart illustrating a coal mine monitoring data synchronization method provided in the embodiments of this specification.

[0020] From a procedural perspective, the executor of the process can be a program mounted on the equipment used for synchronizing coal mine monitoring data. It can be understood that this method can be executed by any device, equipment, platform, or cluster of devices with computing and processing capabilities.

[0021] Figure 1 The method described above can be applied to a coal mine monitoring data synchronization system. The system may include underground data acquisition equipment, a streaming data transmission channel, an early warning information transmission channel, and a ground monitoring platform. The ground monitoring platform is equipped with a pre-writing program, and both the streaming data transmission channel and the early warning information transmission channel can communicate with the pre-writing program.

[0022] In one or more embodiments of this specification, the underground data acquisition equipment can refer to various sensors or data acquisition terminals deployed in the underground working area of ​​a coal mine. These devices are mainly used to sense environmental parameters or equipment operating parameters during the coal mining process in real time and output the sensed data to a streaming data transmission channel. For example, the underground data acquisition equipment may include a gas concentration sensor, a temperature sensor, a humidity sensor, an equipment vibration sensor, or a belt conveyor speed sensor, etc.

[0023] A streaming data transmission channel refers to a data processing and transmission middleware located between underground data acquisition equipment and a surface monitoring platform. This channel primarily receives coal mine monitoring data collected by the underground data acquisition equipment, performs data caching, grouping, and synchronization status management, and transmits the data to the surface monitoring platform according to the synchronization status—a pre-programming mechanism. As one implementation method, the streaming data transmission channel can be implemented using a message queue. For example, it can be based on a distributed message queue. The underground data acquisition equipment can publish data to topics in the message queue, and the streaming data transmission channel can subscribe to and consume data from these topics, subsequently performing caching, grouping, and synchronization processing operations.

[0024] The early warning information transmission channel can be a dedicated transmission channel independent of the streaming data transmission channel. This channel can be specifically designed for the transmission of early warning shadow data. When early warning shadow data is transmitted through this channel, it does not need to wait for the cached data set to be scheduled, thus reducing the latency from the generation of early warning shadow data to its writing to the early warning table.

[0025] A ground-based monitoring platform refers to a monitoring and management system deployed on the ground. This platform primarily receives coal mine monitoring data transmitted via streaming data transmission channels and early warning shadow data transmitted via early warning information transmission channels, and persistently stores the data for ground personnel to monitor underground production conditions in real time and make decisions. As one implementation method, a ground-based monitoring platform may include a database server, a monitoring display interface, and an alarm module. For example, the ground-based monitoring platform can store received gas concentration data in a time-series database and present it as a real-time curve on the monitoring display interface, triggering an alarm when the gas concentration exceeds a safety threshold.

[0026] The pre-writing program refers to a data writing agent deployed on the ground monitoring platform. This program can establish a communication connection with the streaming data transmission channel, primarily to receive the cached data set transmitted by the streaming data transmission channel after being filtered according to the synchronization status, and write the received data into the database of the ground monitoring platform. It can also establish a communication connection with the early warning information transmission channel to transmit early warning shadow data to the early warning table of the ground monitoring platform. In practical applications, a maximum number of connections can be set for the pre-writing program. When the number of connections between the pre-writing program and the streaming data transmission channel is less than the maximum number of connections, a new connection can be established to request the processing of new data; after the synchronization of the current data is completed, the current connection can be destroyed to release resources. For example, the maximum number of connections set for the pre-writing program can be 10. If 6 connections have already been established, 4 more connections can be established to concurrently receive data; once the cached data set corresponding to a certain connection has been written, that connection can be destroyed.

[0027] like Figure 1 As shown, the process may include the following steps.

[0028] Step 102: Obtain coal mine monitoring data collected by the underground data acquisition equipment.

[0029] The coal mine monitoring data includes at least the monitoring point identifiers.

[0030] In one or more embodiments of this specification, coal mine monitoring data may include monitoring point identifiers, data parameter values, and data acquisition timestamps. The monitoring point identifier uniquely identifies the monitoring point that generated the data, the data parameter values ​​represent the physical or state quantities collected by the monitoring point, and the data acquisition timestamp indicates the time the data was collected.

[0031] As one implementation method, the monitoring point identifier can be a monitoring point number, monitoring point name, or monitoring point location, etc. Data parameter values ​​can include the previously collected value and the current collected value, and the collection timestamp can be the timestamp of the current collected value. Including both the previously collected value and the current collected value in the data parameter values ​​allows the ground monitoring platform to determine the data change trend of the monitoring point within two adjacent collection intervals based on the difference between the previously collected value and the current collected value after receiving the data. This helps ground personnel to promptly detect abnormal fluctuations in the monitoring data.

[0032] In practical applications, after receiving coal mine monitoring data collected by underground data acquisition equipment, the streaming data transmission channel can store the received data into a buffer queue, forming a buffer data queue. This buffer data queue can contain multiple coal mine monitoring data entries that have not yet been synchronized. The streaming data transmission channel can set a buffer capacity limit. When the amount of data in the buffer data queue reaches the limit, it can temporarily suspend reading new data from the underground data acquisition equipment or accepting data reported by the equipment, until the data in the buffer data queue is consumed and the buffer space is released.

[0033] As one implementation method, the cached data queue can be implemented using a queue data structure. Newly arrived coal mine monitoring data can be enqueued from the tail of the queue, while data to be synchronized can be dequeued from the head of the queue. The maximum cache capacity can be set based on the available memory resources of the streaming data transmission channel and the data synchronization rate.

[0034] Step 104: Based on the monitoring point identifier, group the monitoring data of each coal mine to obtain each cached data set.

[0035] In one or more embodiments of this specification, the streaming data transmission channel can group the monitoring data of each coal mine according to the monitoring point identifier, and group data with the same monitoring point identifier into the same cached data set, thereby obtaining various cached data sets. Each cached data set can correspond to one monitoring point, and the cached data set can contain the monitoring data of each coal mine generated by that monitoring point.

[0036] Step 106: Determine the synchronization status of each of the cached data sets.

[0037] The synchronization state includes an idle state and a non-idle state. The idle state indicates that the corresponding cached data set is not currently being synchronously written and no data blocking has occurred.

[0038] In one or more embodiments of this specification, the streaming data transmission channel can maintain the synchronization state of each cached data set. The synchronization state can include an idle state and a non-idle state. An idle state indicates that the corresponding cached data set is not currently undergoing synchronous write processing and no data blocking has occurred; in this case, the data in the cached data set can be transmitted to the pre-write program for writing. A non-idle state indicates that the corresponding cached data set is currently undergoing synchronous write processing or has experienced data blocking; in this case, the data in the cached data set is temporarily unsuitable for further write operations. Because the synchronization state of each cached data set is maintained independently, the non-idle state of one cached data set does not affect the synchronization state determination of other cached data sets. This allows the cached data sets to be isolated from each other in terms of synchronization state, enabling other cached data sets to continue writing normally even if one cached data set experiences a write failure, thereby reducing the impact of local data write failures on the overall timeliness of data synchronization.

[0039] Step 108: Based on the synchronization state, determine the set of cached data to be written that is in the idle state.

[0040] In one or more embodiments of this specification, after determining the synchronization status of each cached data set, the streaming data processing channel can select cached data sets that are in an idle state as a cached data set to be written. The cached data set to be written refers to the cached data set that can currently be synchronously written.

[0041] In practical applications, since the synchronization state of each cached data set is maintained independently, some cached data sets may be in the process of being written or have experienced data blocking. These cached data sets are in a non-idle state and are not suitable for further write operations. On the other hand, cached data sets in an idle state indicate that they are not currently undergoing synchronous write processing and are not experiencing data blocking, and can be scheduled for write operations.

[0042] In one or more embodiments of this specification, by filtering out the set of cached data to be written that is in an idle state according to the synchronization status, it can be ensured that subsequent scheduling is only performed on the set of cached data that can be written normally, avoiding repeated write operations on the set of cached data that is being written or is blocked, thereby improving the efficiency and reliability of data synchronization.

[0043] Step 110: Determine whether there is security warning data in each of the sets of cached data to be written, and obtain the first judgment result.

[0044] The safety early warning data refers to monitoring data that indicates safety risks in the coal mining process.

[0045] In one or more embodiments of this specification, safety early warning data can refer to monitoring data collected by underground data acquisition equipment during coal mining that indicates the existence of safety risks underground. For example, safety early warning data may include monitoring data closely related to the safety status of underground coal mines, such as data on excessive methane levels, excessive carbon monoxide levels, fan shutdowns, or conveyor belt jams.

[0046] In practical applications, during the synchronization and data transmission of various cached data sets to be written, streaming data processing channels can detect in real time whether there is any safety warning data in each cached data set to be written. Detection methods may include, but are not limited to: determining whether data parameter values ​​exceed preset safety thresholds, or determining whether the equipment status reflected by the data is abnormal. For example, for a gas concentration monitoring point, if the current collected value in the data parameter exceeds the gas concentration safety threshold (e.g., 1.0%), then the coal mine monitoring data can be determined to be safety warning data.

[0047] Step 112: If the first judgment result indicates that the security warning data exists in the target cache data set of each of the cache data sets to be written, then generate warning shadow data based on the security warning data.

[0048] In one or more embodiments of this specification, the early warning shadow data can be a summary record generated by the streaming data processing channel based on the security early warning data when the existence of security early warning data is detected in the cached data set. The data volume of the early warning shadow data can be much smaller than the corresponding original coal mine monitoring data, so that the early warning shadow data can be quickly written into the early warning table of the ground monitoring platform.

[0049] Optionally, generating warning shadow data based on the security warning data may include: extracting warning type, monitoring point identifier, warning parameter value, and warning trigger timestamp from the security warning data; and generating the warning shadow data based on the warning type, the monitoring point identifier, the warning parameter value, and the warning trigger timestamp.

[0050] As one implementation method, the early warning shadow data can include key fields such as early warning type, monitoring point identifier, early warning parameter value, and early warning trigger timestamp. The early warning type can characterize the early warning category to which the safety early warning data belongs, such as gas over-limit early warning, carbon monoxide over-limit early warning, and wind turbine shutdown early warning; the monitoring point identifier can identify the monitoring point that generated the early warning; the early warning parameter value can be the data parameter value that triggered the early warning; and the early warning trigger timestamp can be the data collection timestamp corresponding to the safety early warning data.

[0051] In practical applications, if security alert data is detected in the target cached data set, the streaming data processing channel can immediately extract key fields from the security alert data to generate alert shadow data, regardless of the priority of the target cached data set. By generating alert shadow data, the key information of the security alert can be encapsulated in a smaller amount of data, thereby enabling the alert information to be transmitted and written quickly.

[0052] Step 114: Write the warning shadow data into the warning table at the ground monitoring platform.

[0053] The original coal mine monitoring data corresponding to the early warning shadow data is stored in the target cache data set, and the original coal mine monitoring data is written according to the data synchronization queue corresponding to each data in the target cache data set.

[0054] Optionally, writing the early warning shadow data into the early warning table at the ground monitoring platform may include: writing the early warning shadow data into the early warning table through an early warning information transmission channel; wherein the early warning information transmission channel is independent of the streaming data transmission channel used to write the target cache data set.

[0055] In one or more embodiments of this specification, after generating early warning shadow data, the streaming data processing channel can transmit the early warning shadow data to a pre-writing program via an independent early warning information transmission channel. The pre-writing program then writes the early warning shadow data into the early warning table at the ground monitoring platform. The early warning information transmission channel can be a dedicated transmission channel independent of the streaming data transmission channel used for writing the cached data set. When the early warning shadow data is transmitted via this channel, it does not need to wait for the original cached data set to be scheduled, thereby reducing the latency from detection to writing of the early warning information, improving the timeliness of the early warning shadow data, and ultimately enhancing the safety of the mine environment.

[0056] Meanwhile, the original coal mine monitoring data that generated the safety warning can remain in the cached data set of its respective monitoring point. The original coal mine monitoring data is then written to according to the data synchronization queue corresponding to each data point in the cached data set. This data synchronization queue is generated based on the data acquisition timestamps of each data point in the cached data set. In this way, the transmission and writing process of the original coal mine monitoring data is not affected by the transmission of the warning shadow data, thus ensuring the temporal integrity of the data in the database.

[0057] It should be understood that the order of some steps in the methods described in one or more embodiments of this specification may be interchanged according to actual needs, or some steps may be omitted or deleted.

[0058] Figure 1 The method described above generates warning shadow data immediately upon detecting safety warning data, regardless of which cache data set it is in, and sends it to the warning table through an independent warning information transmission channel. This eliminates the need for safety warning data to queue in the original cache data set's data synchronization queue, improving the timeliness of warning information. Simultaneously, since the original coal mine monitoring data remains in the original cache data set and is written according to the data synchronization queue, the temporal integrity of the data in the database is guaranteed, preventing the problem of data timing disorder caused by safety warning data being written in a queue. This ensures that the timely reporting of warning information and the orderly writing of monitoring data do not interfere with each other.

[0059] In addition, coal mine monitoring data is grouped according to monitoring point identifiers through streaming data transmission channels to obtain various cached data sets, and the synchronization status of each cached data set is maintained independently. Subsequently, a target cached data set in an idle state can be selected for synchronous writing operations. This ensures that the synchronization processing between different cached data sets does not interfere with each other. When the data writing of a cached data set corresponding to a certain monitoring point is blocked, other cached data sets in an idle state can still synchronize data normally. This avoids the impact of a single monitoring point's write failure on the overall data synchronization timeliness, thereby improving the reliability of coal mine monitoring data synchronization.

[0060] based on Figure 1 In addition to the method described herein, this specification also provides some specific implementation methods of the method, which will be described below.

[0061] To save data synchronization resources, in addition to grouping the data in the cached data queue according to the monitoring point identifier, coal mine monitoring data with the same collection timestamp at the same monitoring point can be further merged to avoid wasting data synchronization resources by repeatedly synchronizing the same coal mine monitoring data.

[0062] Optionally, the coal mine monitoring data may further include a collection timestamp. The step of grouping the coal mine monitoring data according to the monitoring point identifier to obtain various cached data sets may include: grouping coal mine monitoring data with the same monitoring point identifier into the same cached data set; sorting the coal mine monitoring data in any cached data set according to the collection timestamp; and merging the coal mine monitoring data with the same collection timestamp in the sorted cached data sets to obtain the merged cached data set.

[0063] In one or more embodiments of this specification, the streaming data transmission channel can traverse the monitoring data of each coal mine in the cached data queue, classify them according to the monitoring point identifier, and group data with the same monitoring point identifier into the same cached data set. After the division, each cached data set can correspond to a monitoring point identifier, and there is no overlapping data between the cached data sets. For each cached data set obtained by the division, the streaming data transmission channel can sort the data in each cached data set separately according to the collection timestamp. The sorting method can be arranged from earliest to latest according to the collection timestamp, so that the data in the cached data set can be arranged in the order of collection time, so as to facilitate sequential processing during subsequent merging and synchronous transmission.

[0064] In practical applications, multiple data points may be generated at the same monitoring point at the same acquisition time. This could be due to sensors repeatedly reporting data within a short period or data duplication occurring during forwarding through intermediate nodes. Streaming data transmission channels can merge coal mine monitoring data with the same acquisition timestamp within the sorted cached dataset, combining multiple data points from the same acquisition time into a single data point, thereby reducing the amount of redundant data in the cached dataset.

[0065] As one implementation method, the merging process can include retaining the latest data parameter value among coal mine monitoring data with the same collection timestamp, or averaging the data parameter values ​​among coal mine monitoring data with the same collection timestamp and merging them into one data point. For example, in the cached data set with monitoring point identifier "GAS_01", there are two data points with the same collection timestamp "08:30", and their data parameter values ​​are assumed to be "0.35%" and "0.36%" respectively. The merging result can either retain the data point with the data parameter value of "0.36%", or average the two data points and merge them into "0.355%".

[0066] In one or more embodiments of this specification, based on grouping according to monitoring point identifiers, the data in each cached data set is further sorted by collection timestamp and redundant data at the same time is merged. This can reduce the amount of duplicate data in each cached data set, thereby reducing the amount of data transmitted in subsequent synchronization and the writing pressure on the ground monitoring platform. At the same time, the sorted data is also easier for the front-end writing program to write data in chronological order, so as to improve the timeliness of the synchronization data.

[0067] To prevent the failure from escalating when an anomaly occurs during data writing, the cached data set that fails to write synchronously can be marked as blocked and circuit-breaker-enabled to reduce the impact of write failures on overall data synchronization.

[0068] Optionally, the non-idle state includes at least a blocked state and a circuit breaker state. After performing a write operation on the target coal mine monitoring data in the target cache data set, the process may further include: if the write operation on the target coal mine monitoring data fails, setting the synchronization state of the target cache data set to the blocked state, and performing a retry write operation on the target coal mine monitoring data; accumulating the number of synchronization failures of the retry write operation; and if the number of synchronization failures reaches a preset threshold, setting the synchronization state of the target cache data set to the circuit breaker state, wherein, in the circuit breaker state, the write operation on the target cache data set is suspended.

[0069] In one or more embodiments of this specification, the blocking state can refer to the state entered by the cached data set after a write failure occurs during the synchronous write process. It can indicate that there is currently data in the cached data set that has failed to be written successfully and a write retry is required. The circuit breaker state can refer to the state entered by the cached data set after multiple retry writes have continued to fail. It can indicate that the write failure of the cached data set is relatively serious and its synchronization operation needs to be suspended to avoid continuously occupying synchronization resources.

[0070] In practical applications, if the write operation fails when the pre-write program writes target coal mine monitoring data from the target cache dataset to the ground monitoring platform, the streaming data transmission channel can switch the synchronization state of the target cache dataset from idle to blocked. Simultaneously, the streaming data transmission channel can retry the write operation on the failed target coal mine monitoring data. Reasons for write operation failure may include database connection timeouts on the ground monitoring platform, excessive database write pressure causing write rejection, or network transmission interruptions.

[0071] During the retry write operation, the streaming data transmission channel accumulates the number of synchronization failures. Each time a retry write operation fails, the synchronization failure count is incremented by 1. If a retry write operation succeeds, the synchronization failure count can be cleared to zero, and the synchronization state of the set can be restored from the blocked state to the idle state.

[0072] When the cumulative number of synchronization failures reaches a preset threshold, it indicates that the write failure of the target coal mine monitoring data is not an isolated incident, but a persistent and serious failure. At this point, the streaming data transmission channel can switch the synchronization status of the target cached data set from blocked to circuit breaker mode. In circuit breaker mode, the streaming data transmission channel can suspend the data synchronization operation of the target cached data set, meaning it will no longer transmit data from the target cached data set to the front-end writing program, thus preventing the target cached data set from continuously occupying the connection resources of the front-end writing program.

[0073] In one or more embodiments of this specification, if the target coal mine monitoring data fails to be written after multiple retries, the cached data set containing the target coal mine monitoring data is set to a circuit breaker state, and the writing operation of other data in the cached data set is suspended. This can prevent the problem of other data with a later time sequence being written before the target coal mine monitoring data has been successfully written, thereby preventing data timing disorder and preventing the destruction of the dependency relationship between data before and after.

[0074] In one or more embodiments of this specification, after the target coal mine monitoring data writing fails, the cached data set is marked as blocked and the target coal mine monitoring data is retried for writing. At the same time, when the retry continues to fail and the cumulative number of failures reaches a preset threshold, the synchronization state of the cached data set is switched to a circuit breaker state and the synchronization operation on the cached data set is suspended. This can prevent the faulty set from continuously occupying the connection resources of the preceding writing program, thereby ensuring that the synchronization resources of other cached data sets are not squeezed out, thus improving the overall stability of data synchronization.

[0075] To ensure that cached data sets in a circuit breaker state can be restored to normal in a timely manner after the write failure is cleared, a liveness detection operation can be performed on the cached data sets in a circuit breaker state at preset time intervals to check whether their write capability has been restored to normal.

[0076] Optionally, the method may further include: performing a liveness detection operation on the target cached data set in the circuit breaker state at a preset time interval; if the liveness detection is successful, restoring the synchronization state of the target cached data set to the idle state.

[0077] In one or more embodiments of this specification, a liveness detection operation can refer to the streaming data transmission channel sending a probe request to the pre-writing program for a cached data set in a circuit-broken state to detect whether the write state of the cached data set in a circuit-broken state has returned to normal. The liveness detection operation can be implemented by selecting data from the cached data set in the circuit-broken state that failed to be written previously and attempting to write it. If the liveness detection operation is successful, it indicates that the write state of the cached data set has returned to normal. The streaming data transmission channel can restore the synchronization state of the target cached data set from a circuit-broken state to an idle state. After restoring to an idle state, the data in the cached data set can be retransmitted to the pre-writing program for normal writing. Because the liveness detection operation is automatically performed on the cached data set in a circuit-broken state at preset time intervals, and its synchronization state is promptly restored to an idle state upon successful liveness detection to restore data synchronization, the cached data set that was circuit-broken due to a temporary fault can automatically resume synchronous writing operations after the fault is eliminated, thereby improving the self-healing capability and synchronization efficiency of the coal mine monitoring data synchronization system.

[0078] To ensure the timely synchronization of more important monitoring data when multiple cached datasets are idle at the same time, different priorities can be set for different types of monitoring points, and data synchronization can be performed in descending order of priority.

[0079] Optionally, the monitoring points may include production monitoring points, equipment operating condition monitoring points, and environmental safety monitoring points. The production monitoring points correspond to a first priority, the equipment operating condition monitoring points correspond to a second priority, and the environmental safety monitoring points correspond to a third priority, wherein the first priority is higher than the second priority, and the second priority is higher than the third priority.

[0080] Correspondingly, after determining the set of cached data to be written that is in the idle state based on the synchronization state, the process may further include: determining the set synchronization queue corresponding to each set of cached data to be written in descending order of priority; and performing write operations on each set of cached data to be written sequentially according to the set synchronization queue.

[0081] In one or more embodiments of this specification, the production monitoring point can be a monitoring point used to monitor coal production-related data during coal mining, such as a monitoring point equipped with a belt scale sensor or a coal mining machine cutting power sensor, and the production monitoring point can correspond to the first priority.

[0082] Equipment condition monitoring points can be monitoring points used to monitor data related to the operating status of coal mining equipment, such as monitoring points for equipment such as main ventilation fan vibration sensors, water pump pressure sensors, or belt conveyor temperature sensors. Equipment condition monitoring points can be assigned to the second priority.

[0083] Environmental safety monitoring points can be used to monitor data related to the safety environment in coal mines, such as monitoring points equipped with gas concentration sensors, carbon monoxide concentration sensors, or wind speed sensors. Environmental safety monitoring points can be classified as the third priority.

[0084] In practical applications, the criteria for setting priorities can include the degree of impact of this type of monitoring data on coal mine production decisions, or the urgency of data timeliness requirements. Since production data directly reflects the output of coal mining and has the most direct impact on production scheduling decisions, it can be given the highest priority. Equipment condition data reflects the health status of equipment and is important for equipment maintenance decisions, so it can be given the second highest priority. Environmental safety data is used for routine environmental monitoring and can be given the third priority. The first priority can be higher than the second priority, and the second priority can be higher than the third priority.

[0085] In practical applications, the streaming data transmission channel can query the synchronization status of various cached data sets and filter out those currently in an idle state. After filtering out the idle cached data sets, the streaming data transmission channel does not perform synchronous write processing randomly. Instead, it sorts the cached data sets to be written from high to low priority according to the priority of the monitoring points corresponding to each set, thus obtaining a set synchronization queue. Based on this set synchronization queue, the idle sets corresponding to production monitoring points are transmitted to the pre-writing program first, followed by the idle sets corresponding to equipment operating condition monitoring points, and finally the idle sets corresponding to environmental safety monitoring points. By setting differentiated priorities for different types of monitoring points and synchronizing data in the idle cached data sets in descending order of priority, production monitoring data, which has a more direct impact on coal mine production decisions, can be synchronized first, followed by equipment operating condition data and environmental safety data. This allows for the rational allocation of synchronization resources, improving the synchronization efficiency and timeliness of important monitoring data.

[0086] In order to respond promptly to coal mine monitoring data that poses safety risks while synchronizing data according to priority, safety early warning detection can be performed on data in the low-priority cache data set before data synchronization.

[0087] Optionally, the step of sequentially performing write operations on each of the sets of cached data to be written according to the set synchronization queue may include: detecting whether the security warning data exists in the low-priority sets of cached data to be written; if the security warning data does not exist in the low-priority sets of cached data to be written, then sequentially performing write operations on each of the sets of cached data to be written according to the set synchronization queue; if the security warning data exists in the low-priority sets of cached data to be written, then prioritizing the performance of write operations on the low-priority sets of cached data to be written.

[0088] In one or more embodiments of this specification, before scheduling idle cached data sets to be written in descending priority order, the streaming data transmission channel first checks whether there is safety warning data in the low-priority cached data sets to be written. The detection method may involve comparing the data parameter values ​​of coal mine monitoring data in the low-priority cached data sets to be written with a preset safety threshold. If the data parameter value reaches or exceeds the safety threshold, the data is determined to be safety warning data.

[0089] A low-priority set of cached data to be written can refer to a set with a lower priority than the cached data set to be scheduled based on priority. For example, if the cached data set to be scheduled is the cached data set corresponding to production monitoring points, then the low-priority set could include the cached data sets corresponding to equipment condition monitoring points and environmental safety monitoring points. As another example, if the cached data set to be scheduled is the cached data set corresponding to equipment condition monitoring points, then the low-priority set could include the cached data set corresponding to environmental safety monitoring points.

[0090] For example, assuming that the cached data set corresponding to the environmental safety monitoring point "GAS_03" is a low-priority cached data set, the streaming data transmission channel can detect whether there is any data in the set whose gas concentration exceeds the safety threshold. If there is a data set in the set with a gas concentration value of "1.2%" and the gas concentration safety threshold is "1.0%", then this data can be regarded as a safety warning data.

[0091] If the detection results indicate that there is no safety warning data in the low-priority cache data set, it means that the environmental parameters and equipment operating parameters of each monitoring point in the coal mine are within a safe range. In this case, the streaming data transmission channel can normally schedule each idle cache data set to be written in order of priority from high to low.

[0092] If the detection results indicate that there is safety warning data in the low-priority cached data set, it means that there is a safety risk in the coal mine. The original safety warning data needs to be synchronized to the ground monitoring platform as soon as possible. At this time, the streaming data transmission channel does not need to synchronize data according to the scheduling order from high to low priority. Instead, it can prioritize transmitting the low-priority cached data set containing safety warning data to the pre-writing program so that ground personnel can be informed of the underground safety risks in a timely manner and take countermeasures, thereby improving the safety of coal mine production.

[0093] In one or more embodiments of this specification, before scheduling each idle cache data set to be written in descending order of priority, security warning data detection can be performed on the low-priority cache data sets to be written. When no security warning data exists, data synchronization can be performed in the normal order of descending priority. When security warning data exists, data synchronization can be performed on the cache data set to be written containing security warning data first, thereby enabling the data synchronization strategy to be flexibly adapted between normal production scenarios and security emergency scenarios.

[0094] To avoid the impact of false alarms in security alert data on the data synchronization strategy, after detecting the presence of security alert data in a low-priority cached data set, the credibility of the security alert data can be verified first.

[0095] Optionally, after detecting whether security warning data exists in the low-priority cache data set, the method may further include: if the security warning data exists in the low-priority cache data set, then the cache data set in an idle state containing the security warning data is preferentially transmitted to the pre-writing program.

[0096] Optionally, if the security warning data exists in the low-priority cached data set, then the idle cached data set containing the security warning data is preferentially transmitted to the pre-writing program. This may include: verifying the credibility of the security warning data; if the credibility verification of the security warning data passes, then the idle cached data set containing the security warning data is preferentially transmitted to the pre-writing program; if the credibility verification of the security warning data fails, then each idle cached data set is transmitted to the pre-writing program in descending order of priority.

[0097] In one or more embodiments of this specification, after detecting the presence of security warning data in a low-priority cached data set, the credibility of the security warning data is also verified. Only when the credibility verification passes will the cached data set containing the security warning data be synchronized first. If the credibility verification fails, the data will still be synchronized in the normal order from high to low priority. This can avoid the priority synchronization order being broken due to false alarms caused by sensor failure or abnormal data acquisition. In this way, the data synchronization strategy can ensure the timeliness of security emergency response while reducing the interference of false alarms on the normal priority synchronization order, thereby improving the stability and accuracy of data synchronization.

[0098] In one or more embodiments of this specification, a method for verifying the credibility of security warning data is also proposed.

[0099] Optionally, the method for verifying the credibility of safety warning data may include: obtaining historical coal mine monitoring data collected by the target monitoring point corresponding to the safety warning data within a preset historical time period; verifying the credibility of the safety warning data based on the changing trend of the data parameter values ​​of the historical coal mine monitoring data; if the changing trend of the data parameter values ​​of the historical coal mine monitoring data is a normal changing trend, it indicates that the credibility verification of the safety warning data has passed; if the changing trend of the data parameter values ​​of the historical coal mine monitoring data is an abnormal changing trend, it indicates that the credibility verification of the safety warning data has failed.

[0100] In one or more embodiments of this specification, after detecting a safety warning data, the streaming data transmission channel can obtain historical coal mine monitoring data collected by the target monitoring point within a preset historical time period based on the monitoring point identifier of the safety warning data. The preset historical time period can be set according to the actual scenario, such as the past 5 minutes or the past 10 minutes. The historical coal mine monitoring data may include the data parameter values ​​of each data point of the target monitoring point within the preset historical time period and the corresponding collection timestamps. Based on the obtained historical coal mine monitoring data, the streaming data transmission channel can observe the changing trend of the data parameter values ​​of the target monitoring point within the preset historical time period and verify the credibility of the safety warning data based on the changing trend.

[0101] In practical applications, a normal trend of change can refer to the trend of data parameter values ​​showing a continuous increase or a gradual decrease over a preset historical period. If the safety warning data is a continuation of this change process rather than a sudden change, it can be said that the safety warning data is consistent with the historical trend of change and belongs to a real safety risk.

[0102] For example, suppose the data parameter values ​​of a gas concentration monitoring point within a preset historical period are "0.3%, 0.5%, 0.8%, 1.1%, 1.5%" respectively, showing a continuous upward trend. The current data parameter value of 1.5% is a natural continuation of this upward trend. Therefore, it can be said that the data parameter value of 1.5% is a reliable verification of the safety warning data.

[0103] In practical applications, an abnormal trend can refer to a situation where data parameter values ​​fluctuate slightly within a normal range over a preset historical period, but a particular value experiences a large change without a gradual transition. If the safety warning data is a sudden, large jump in historical data without a gradual transition, it indicates that the safety warning data is inconsistent with the historical trend and may be a false alarm caused by sensor malfunction or abnormal data acquisition.

[0104] For example, suppose the data parameter values ​​of a gas concentration monitoring point within a preset historical time period are "0.3%, 0.32%, 0.29%, 0.31%, 1.5%" respectively. The first four parameter values ​​fluctuate slightly within the normal range, while the last parameter value suddenly jumps sharply above the safety threshold without a gradual change in between. This can be regarded as an abnormal trend, indicating that the reliability verification of the data parameter value of 1.5% as a safety warning data has failed.

[0105] In practical applications, abnormal trends do not necessarily mean that security alert data is a false alarm. To improve the accuracy of verifying the credibility of security alert data, it can be further verified by combining it with related events.

[0106] Optionally, if the trend of the data parameter values ​​in the historical coal mine monitoring data is an abnormal trend, it indicates that the credibility verification of the safety warning data has failed. This can include: determining whether there is a related event in the area where the target detection point is located that would cause a sudden change in the data parameter values; if the related event exists, then the credibility verification of the safety warning data is determined to be successful; if the related event does not exist, then the credibility verification of the safety warning data is determined to be unsuccessful.

[0107] In one or more embodiments of this specification, a related event may refer to an event that occurs in the area where the target monitoring point is located, which may cause a significant jump in the value of the monitoring data parameters within a short period of time.

[0108] In practical applications, if the safety warning data indicates that the gas concentration in the coal mine exceeds the standard, the associated events may include: the shutdown of a local ventilation fan causing ventilation interruption in that area, the coal mining machine cutting into a gas-rich area causing a sudden gas outburst, or blasting operations causing a concentrated release of harmful gases.

[0109] If a correlated event exists in the area where the target monitoring point is located, causing a sudden change in the data, it indicates that although the data parameter values ​​of the safety warning data are inconsistent with historical trends, the credibility of the safety warning data can be verified because of the existence of a reasonable correlated event. Continuing with the example above, in the trend of gas concentration changes of "0.3%, 0.32%, 0.29%, 0.31%, 1.5%", although the gas concentration of 1.5% is a sudden change, if it is detected that the local ventilation fan in the area where the monitoring point is located had stopped at the last time of data collection, and the ventilation interruption caused the gas to accumulate rapidly in a short period of time, it indicates that the sudden change in gas concentration of 1.5% has a reasonable correlated event, and the credibility of the gas concentration of 1.5% as a safety warning data point is verified.

[0110] If there are no associated events in the area where the target monitoring point is located that would cause a sudden change in the data, it can be said that the sudden change in the data parameter value of the safety warning data lacks reasonable associated event support. This sudden change may be a false alarm caused by sensor failure or abnormal data acquisition. Therefore, it can be determined that the credibility verification of the safety warning data has failed.

[0111] In one or more embodiments of this specification, before scheduling the idle cached data set for write operations using priority order, it is first detected whether there is security warning data in the low-priority cached data set. If security warning data exists, the original priority scheduling strategy can be broken to prioritize synchronizing the cached data set containing the security warning data, thereby ensuring the timeliness of security warning data synchronization in security emergency scenarios. At the same time, after detecting security warning data, the credibility of the security warning data can be further verified. In the process of verifying credibility, the change trend of historical data is first used to determine whether the security warning data matches the historical change process. If the change trend of historical data is determined to be an abnormal change trend, a secondary verification can be performed by combining whether there are related events. This can avoid breaking the priority scheduling order due to false alarms caused by sensor failure or abnormal data acquisition. In this way, the data synchronization strategy can be flexibly adapted between normal production scenarios and security emergency scenarios, so as to ensure timely response to security warning data while reducing the interference of false alarms on the normal scheduling order.

[0112] In the actual working environment of underground coal mines, the communication network between underground data acquisition equipment and the ground monitoring platform may be interrupted due to changes in underground geological conditions, equipment failure, or power outages. During the network interruption, the streaming data transmission channel cannot transmit coal mine monitoring data from each cached data set to the pre-writing program, resulting in a data blockage in the synchronization state of each cached data set. During this period, coal mine monitoring data continuously collected by the underground data acquisition equipment will continue to be stored in the corresponding cached data sets, causing a large backlog of monitoring data awaiting synchronization in each cached data set. If all the backlogged data is directly transmitted in its original order after the network is restored, on the one hand, the lack of updated safety-related data for a long time will prevent users from timely understanding the underground safety situation; on the other hand, if new safety warning data appears during the recovery process and cannot be reported in a timely manner, it may also cause safety hazards. Therefore, a reasonable recovery strategy needs to be designed for network recovery scenarios.

[0113] In order to ensure that the ground monitoring platform can prioritize the acquisition of backlogged safety warning data and orderly synchronize and write the backlogged historical monitoring data during the interruption after the underground network is restored, the data synchronization after network restoration can be carried out according to the strategy of "prioritizing safety-related data and replenishing historical monitoring data according to the water level line".

[0114] Optionally, the method may further include: after detecting that the communication connection between the underground data acquisition device and the ground monitoring platform has been restored from an interrupted state to a normal state, determining whether the underground data acquisition device acquired the safety warning data during the network interruption, and obtaining a second determination result; if the second determination result indicates that the safety warning data was acquired, then preferentially writing the warning shadow data corresponding to the safety warning data into the warning table; determining other coal mine monitoring data to be synchronized based on the water level lines of the monitoring points corresponding to each underground data acquisition device, wherein the water level lines are used to reflect the location information of the data that has been successfully written into the ground monitoring platform in the cached data set corresponding to the monitoring point; Write operations are performed on the monitoring data of each of the other coal mines.

[0115] In one or more embodiments of this specification, after the network between the downhole data acquisition device and the ground monitoring platform is restored from an interruption, the safety warning data (safety-related data) collected by the downhole data acquisition device during the network interruption can be preferentially transmitted to the pre-writing program. Then, based on the water level lines of each monitoring point, other historical monitoring data (non-safety-related data) to be replenished are determined. The water level line is the location information of the data that has been successfully written to the ground monitoring platform in the cache data set of the corresponding monitoring point. The historical cache data to be replenished is the coal mine monitoring data accumulated after the water level line and before the network restoration time. The other historical cache data to be replenished is divided into multiple batches, wherein the principle of batch division can be based on the above priority. The data of each batch is transmitted to the pre-writing program in batches according to the order of the divided batches. After each batch of data is successfully written, the water level line of the corresponding monitoring point is updated in real time. In practical applications, if new security alert data is detected during the replenishment of other historical cached data, the replenishment operation of other historical cached data is paused, and the alert shadow data corresponding to the new security alert data is transmitted to the pre-writing program first. After the alert shadow data transmission is completed, the replenishment operation of other historical cached data continues.

[0116] In one or more embodiments of this specification, safety-related data may include early warning data such as methane concentration, carbon monoxide concentration, conveyor belt operating status, or fan operating status. Since this type of data is directly related to the safety of personnel underground in coal mines, it is necessary to prioritize transmitting this data to the ground monitoring platform after network recovery so that monitoring personnel can quickly grasp the current safety situation underground. Furthermore, by using water level lines to determine the start position of data re-upload for each monitoring point, the risk of duplicate writing or omission of historical monitoring data can be avoided; and when new safety early warning data is detected during the re-upload process, re-upload will be immediately paused and switched to the real-time safety channel to prioritize the reporting of safety early warning data, thereby improving the security and orderliness of data synchronization after network recovery.

[0117] To achieve load balancing among the write threads participating in data writing in the pre-writing process, the number of threads participating in writing can be determined based on the amount of coal mine monitoring data contained in the target cache data set.

[0118] Optionally, the pre-writing program may include multiple writing threads, the target cache data set includes a first cache data set, and the pre-writing program writes data from the target cache data set to the ground monitoring platform, which may include: counting the number of coal mine monitoring data entries contained in the first cache data set to obtain a first quantity value; selecting a writing thread with a second quantity value from the multiple writing threads, wherein the quotient of the first quantity value and the second quantity value is an integer; and using the writing thread with the second quantity value to write data from the first cache data set to the ground monitoring platform.

[0119] In one or more embodiments of this specification, a write thread is a thread in the pre-writing program used to perform data writing operations. Multiple write threads can write data to the database of the ground monitoring platform in parallel, thereby improving the throughput efficiency of data writing. In practical applications, the total number of write threads can be reasonably configured according to the computing resources of the server where the pre-writing program is located and the write capacity of the ground monitoring platform database.

[0120] In practical applications, after receiving the first cached data set from the streaming data transmission channel, the pre-writing program counts the number of coal mine monitoring data entries in the set, obtaining a first quantity value. Subsequently, based on this first quantity value, the pre-writing program selects a second quantity of writing threads from a configured pool of multiple writing threads to participate in the current write operation. The selection principle is that the quotient of the first and second quantities must be an integer, ensuring that the data in the first cached data set is evenly distributed among the selected writing threads. The pre-writing program then distributes the coal mine monitoring data in the first cached data set evenly among the selected writing threads, allowing each thread to write its assigned data to the ground monitoring platform in parallel.

[0121] In one or more embodiments of this specification, before writing data to the first cached data set, the number of data entries to be written is counted, and an appropriate number of writing threads are started to participate in the writing based on this number. This ensures that each participating thread is allocated the same number of data entries, thus avoiding the disadvantage of some participating threads being allocated too little data while others are allocated too much data. This achieves load balancing among the participating threads and prevents some writing threads from being idle while others are constantly busy during the data writing process, thereby improving the utilization rate of the writing threads participating in the writing operation.

[0122] In order to ensure that the data in the second cache data set can also be evenly distributed among the writing threads and achieve overall load balancing of the target cache data set, it is necessary to determine whether the remaining idle writing threads can evenly distribute the data volume of the second cache data set before performing write operations on the first cache data set.

[0123] Optionally, the target cached data set may further include a second cached data set. The step of using the writing thread of the second quantity value to write the data in the first cached data set to the ground monitoring platform may include: determining a third quantity value of the remaining idle writing threads in the pre-writing program other than the writing thread of the second quantity value; counting the number of coal mine monitoring data entries contained in the second cached data set to obtain a fourth quantity value; determining whether the quotient between the fourth quantity value and the third quantity value is an integer to obtain a determination result; if the determination result indicates that the quotient between the fourth quantity value and the third quantity value is an integer, then using the writing thread of the second quantity value to write the data in the first cached data set to the ground monitoring platform.

[0124] In one or more embodiments of this specification, after the pre-writing program selects a second number of writing threads from multiple writing threads to handle the writing operations of the first cached data set, it needs to determine a third number of the remaining idle writing threads. This third number reflects the idle writing thread resources in the pre-writing program that can still be used to write to the second cached data set during the writing process of the first cached data set. Subsequently, the pre-writing program can calculate a fourth number of coal mine monitoring data contained in the second cached data set within the target cached data set. The second cached data set can be the data set to be written following the first cached data set in the target cached data set, and the fourth number reflects the total amount of data to be written in the second cached data set. The pre-writing program can determine whether the fourth number is divisible by the third number, i.e., whether the quotient of the fourth number and the third number is an integer. The purpose of this determination is to confirm whether the remaining idle writing threads can evenly distribute the data in the second cached data set so that each remaining idle writing thread is allocated the same amount of data. When the quotient of the fourth and third quantities is an integer, it indicates that the remaining idle write threads can evenly distribute the data in the second cache data set. This means that each of the idle write threads in the third quantity can be allocated the same amount of data, preventing some threads from being idle while others are overloaded. Under this condition, the pre-writing program uses the selected second quantity of write threads to evenly write the data in the first cache data set to the ground monitoring platform. Simultaneously, the remaining third quantity of idle write threads can be used to evenly write the data in the second cache data set to the ground monitoring platform as well.

[0125] In one or more embodiments of this specification, by further determining whether the second cached data set can also be evenly written by the remaining idle write threads, the write operation on the first cached data set using the second number of write threads will be executed only when the even writing condition is met. This allows the first cached data set and the second cached data set in the target cached data set to achieve load balancing, thereby improving the utilization rate of the write threads assigned to execute the write operation on the first cached data set and the write threads assigned to execute the write operation on the second cached data set, and ultimately improving the utilization rate of each write thread in the pre-writing program.

[0126] Based on the same idea, embodiments of this specification also provide apparatus corresponding to the above methods.

[0127] Figure 2 This is a schematic diagram of the structure of a coal mine monitoring data synchronization device provided in the embodiments of this specification. Figure 2 As shown, the device may include: Data acquisition module 202 is used to acquire coal mine monitoring data collected by underground data acquisition equipment, wherein the coal mine monitoring data includes at least monitoring point identifiers; The grouping processing module 204 is used to group the monitoring data of each coal mine according to the monitoring point identifier to obtain each cached data set; The state determination module 206 is used to determine the synchronization state of each of the cached data sets. The synchronization state includes an idle state and a non-idle state. The idle state indicates that the corresponding cached data set is not currently being synchronously written and no data blocking has occurred. The module 208 for determining the set of cached data to be written is used to determine the set of cached data to be written that is in the idle state based on the synchronization state. The judgment module 210 is used to determine whether there is security warning data in each of the sets of cached data to be written, and to obtain a first judgment result. The security warning data is monitoring data that indicates that there is a safety risk in the coal mining process. The warning shadow data generation module 212 is used to generate warning shadow data based on the security warning data if the first judgment result indicates that the security warning data exists in the target cache data set in each of the cache data sets to be written. The early warning shadow data writing module 214 is used to write the early warning shadow data into the early warning table at the ground monitoring platform. The original coal mine monitoring data corresponding to the early warning shadow data is stored in the target cache data set, and the original coal mine monitoring data is written according to the data synchronization queue corresponding to each data in the target cache data set.

[0128] based on Figure 2 The embodiments of this specification also provide some specific implementation schemes of the method, which are described below.

[0129] Optionally, the early warning shadow data generation module 212 may include: The extraction unit is used to extract the warning type, monitoring point identifier, warning parameter value, and warning trigger timestamp from the security warning data. The generation unit is used to generate the warning shadow data based on the warning type, the monitoring point identifier, the warning parameter value, and the warning trigger timestamp; The warning shadow data writing module 214 may include: The writing unit is used to write the warning shadow data into the warning table through the warning information transmission channel; wherein the warning information transmission channel is independent of the streaming data transmission channel used to write the target cache data set.

[0130] Optionally, the coal mine monitoring data may also include a collection timestamp.

[0131] Optionally, the group processing module 204 may include: The partitioning unit is used to group coal mine monitoring data with the same monitoring point identifier into the same cached data set; The sorting unit is used to sort the coal mine monitoring data in any cached data set according to the collection timestamp. The merging unit is used to merge coal mine monitoring data with the same collection timestamp in any of the sorted cached data sets to obtain the merged cached data set.

[0132] Optionally, the non-idle state includes at least a blocked state and a circuit breaker state.

[0133] Optionally, after performing a write operation on the target coal mine monitoring data in the target cache data set, the process may further include: if the write operation on the target coal mine monitoring data fails, setting the synchronization state of the target cache data set to the blocked state, and performing a retry write operation on the target coal mine monitoring data; accumulating the number of synchronization failures of the retry write operation; and when the number of synchronization failures reaches a preset threshold, setting the synchronization state of the target cache data set to the circuit breaker state, wherein, in the circuit breaker state, the write operation on the target cache data set is suspended.

[0134] Optionally, the device may further include: The liveness detection unit is used to perform liveness detection operations on the target cached data set in the circuit breaker state at preset time intervals.

[0135] The recovery unit is used to restore the synchronization state of the target cached data set to the idle state if the liveness detection is successful.

[0136] Optionally, the monitoring points include production monitoring points, equipment operating condition monitoring points, and environmental safety monitoring points. The production monitoring points correspond to a first priority, the equipment operating condition monitoring points correspond to a second priority, and the environmental safety monitoring points correspond to a third priority, wherein the first priority is higher than the second priority, and the second priority is higher than the third priority.

[0137] The device may further include: The set synchronization queue determination module is used to determine the set synchronization queue corresponding to each set of cached data to be written in descending order of priority.

[0138] The first monitoring data writing module is used to perform writing operations on each of the cached data sets to be written in sequence according to the set synchronization queue.

[0139] Optionally, the first monitoring data writing module may include: The detection unit is used to detect whether the security warning data exists in the low-priority cache data set to be written; The first monitoring data writing unit is used to perform writing operations on each of the low-priority cache data sets to be written in sequence according to the set synchronization queue if the security warning data does not exist in the low-priority cache data set to be written. The second monitoring data writing unit is used to perform a write operation on the low-priority cache data set if the security warning data exists in the low-priority cache data set to be written.

[0140] Optionally, the device further includes: The second judgment module is used to determine whether the downhole data acquisition device acquired the safety warning data during the network interruption after detecting that the communication connection between the downhole data acquisition device and the ground monitoring platform has been restored from the interrupted state to the normal state, and to obtain the second judgment result. The second early warning shadow data writing module is used to write the early warning shadow data corresponding to the security early warning data into the early warning table if the second judgment result indicates that the security early warning data has been collected. The monitoring data determination module is used to determine other coal mine monitoring data to be synchronized based on the water level lines of the monitoring points corresponding to each of the underground data acquisition devices. The water level lines are used to reflect the location information of the data that has been successfully written into the ground monitoring platform in the cached data set corresponding to the monitoring point. The second monitoring data writing module is used to perform writing operations on the monitoring data of each of the other coal mines.

[0141] Based on the same idea, this specification also provides devices corresponding to the above methods in its embodiments.

[0142] Figure 3 This is a structural block diagram of a computing device provided in one embodiment of this specification.

[0143] The computing device 300 includes: Memory 310 and processor 320; The memory 310 is used to store computer programs / instructions, and the processor 320 is used to execute the computer programs / instructions. When the computer programs / instructions are executed by the processor 320, they implement the steps of the above-described coal mine monitoring data synchronization method.

[0144] Specifically, the components of the computing device 300 include, but are not limited to, a memory 310 and a processor 320. The processor 320 is connected to the memory 310 via a bus 330, and the database 350 is used to store data.

[0145] The computing device 300 also includes an access device 340, which enables the computing device 300 to communicate via one or more networks 360. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. The access device 340 may include one or more of any type of wired or wireless network interface (e.g., a network interface card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and so on.

[0146] In one embodiment of this specification, the above-described components of the computing device 300 and Figure 3 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 3 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this application. Those skilled in the art can add or replace other components as needed.

[0147] The computing device 300 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). The computing device 300 can also be a mobile or stationary server.

[0148] The processor 320 executes the computer instructions to implement the steps of the above-mentioned coal mine monitoring data synchronization method.

[0149] The above is a schematic diagram of a computing device according to this embodiment. It should be noted that the technical solution of this computing device and the technical solution of the above-described coal mine monitoring data synchronization method belong to the same concept. For details not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of the above-described coal mine monitoring data synchronization method.

[0150] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0151] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0152] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0153] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0154] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0155] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0156] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0157] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0158] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0159] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0160] Computer-readable media include both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0161] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0162] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0163] This application can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0164] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for synchronizing coal mine monitoring data, characterized in that, The method includes: Acquire coal mine monitoring data collected by underground data acquisition equipment, wherein the coal mine monitoring data includes at least monitoring point identifiers; Based on the monitoring point identifiers, the monitoring data of each coal mine are grouped to obtain each cached data set. Determine the synchronization state of each of the cached data sets. The synchronization state includes an idle state and a non-idle state. The idle state indicates that the corresponding cached data set is not currently being synchronously written and no data blocking has occurred. Based on the synchronization state, determine the set of cached data to be written that is in the idle state; Determine whether there is security warning data in each of the sets of data to be written to the cache, and obtain a first determination result. The security warning data is monitoring data that indicates that there is a safety risk in the coal mining process. If the first determination result indicates that the security warning data exists in the target cache data set in each of the cache data sets to be written, then warning shadow data is generated based on the security warning data; The early warning shadow data is written into the early warning table at the ground monitoring platform. The original coal mine monitoring data corresponding to the early warning shadow data is retained in the target cache data set, and the original coal mine monitoring data is written according to the data synchronization queue corresponding to each data in the target cache data set.

2. The coal mine monitoring data synchronization method according to claim 1, characterized in that, The generation of early warning shadow data based on the security early warning data includes: Extract the warning type, monitoring point identifier, warning parameter value, and warning trigger timestamp from the security warning data; The warning shadow data is generated based on the warning type, the monitoring point identifier, the warning parameter value, and the warning trigger timestamp. The step of writing the early warning shadow data into the early warning table at the ground monitoring platform includes: The warning shadow data is written into the warning table through the warning information transmission channel; wherein, the warning information transmission channel is independent of the streaming data transmission channel used to write the target cache data set.

3. The coal mine monitoring data synchronization method according to claim 1, characterized in that, The coal mine monitoring data also includes a collection timestamp. Based on the monitoring point identifier, the coal mine monitoring data is grouped to obtain various cached data sets, including: Coal mine monitoring data with the same monitoring point identifier are grouped into the same cached data set; For any cached data set, sort the coal mine monitoring data in the cached data set according to the collection timestamp; The coal mine monitoring data with the same collection timestamp in any of the sorted cached data sets are merged to obtain the merged cached data set.

4. The coal mine monitoring data synchronization method according to claim 1, characterized in that, The non-idle state includes at least a blocked state and a circuit breaker state. After performing a write operation on the target coal mine monitoring data in the target cache data set, it also includes: If the write operation for the target coal mine monitoring data fails, the synchronization state of the target cache data set is set to the blocked state, and a retry write operation is performed on the target coal mine monitoring data. The cumulative number of synchronization failures in the retry write operation; If the number of synchronization failures reaches a preset threshold, the synchronization status of the target cache data set is set to the circuit breaker status, wherein writing operations to the target cache data set are suspended in the circuit breaker status.

5. The coal mine monitoring data synchronization method according to claim 4, characterized in that, The method further includes: A liveness detection operation is performed on the target cached data set in the circuit breaker state at preset time intervals; If the liveness detection is successful, the synchronization state of the target cached data set will be restored to the idle state.

6. The coal mine monitoring data synchronization method according to claim 1, characterized in that, The monitoring points include production monitoring points, equipment operating condition monitoring points, and environmental safety monitoring points. The production monitoring points correspond to the first priority, the equipment operating condition monitoring points correspond to the second priority, and the environmental safety monitoring points correspond to the third priority, wherein the first priority is higher than the second priority, and the second priority is higher than the third priority. After determining the set of cached data to be written that is in the idle state based on the synchronization state, the method further includes: The corresponding set synchronization queues for each set of cached data to be written are determined in descending order of priority. Write operations are performed sequentially on each of the sets of cached data to be written, according to the set synchronization queue.

7. The coal mine monitoring data synchronization method according to claim 6, characterized in that, The step of sequentially performing write operations on each of the sets of cached data to be written according to the set synchronization queue includes: Detect whether the security warning data exists in the low-priority cache data set to be written; If the security warning data is not present in the low-priority cache data set to be written, then write operations are performed sequentially on each of the cache data sets to be written according to the set synchronization queue. If the security warning data exists in the low-priority cache data set to be written, then the write operation will be performed on the low-priority cache data set to be written first.

8. The coal mine monitoring data synchronization method according to claim 1, characterized in that, The method further includes: After detecting that the communication connection between the downhole data acquisition device and the ground monitoring platform has been restored from an interrupted state to a normal state, it is determined whether the downhole data acquisition device acquired the safety warning data during the network interruption, and a second determination result is obtained. If the second judgment result indicates that the security warning data has been collected, then the warning shadow data corresponding to the security warning data shall be written into the warning table first. Based on the water level lines of the monitoring points corresponding to each of the underground data acquisition devices, other coal mine monitoring data to be synchronized are determined. The water level lines are used to reflect the location information of the data that has been successfully written into the ground monitoring platform in the cached data set corresponding to the monitoring point. Write operations are performed on the monitoring data of each of the other coal mines.

9. A coal mine monitoring data synchronization device, characterized in that, The device includes: The data acquisition module is used to acquire coal mine monitoring data collected by underground data acquisition equipment, wherein the coal mine monitoring data includes at least monitoring point identifiers; The grouping processing module is used to group the monitoring data of each coal mine according to the monitoring point identifier to obtain each cached data set; The state determination module is used to determine the synchronization state of each of the cached data sets. The synchronization state includes an idle state and a non-idle state. The idle state indicates that the corresponding cached data set is not currently being synchronously written and no data blocking has occurred. The module for determining the set of cached data to be written is used to determine the set of cached data to be written that is in the idle state based on the synchronization state. The judgment module is used to determine whether there is security warning data in each of the sets of cached data to be written, and to obtain a first judgment result. The security warning data is monitoring data that indicates that there is a safety risk in the coal mining process. The warning shadow data generation module is used to generate warning shadow data based on the security warning data if the first judgment result indicates that the security warning data exists in the target cache data set in each of the cache data sets to be written. The early warning shadow data writing module is used to write the early warning shadow data into the early warning table at the ground monitoring platform. The original coal mine monitoring data corresponding to the early warning shadow data is stored in the target cache data set, and the original coal mine monitoring data is written according to the data synchronization queue corresponding to each data in the target cache data set.

10. A computing device, characterized in that, include: Memory and processor; The memory is used to store computer programs or instructions, and the processor is used to execute the computer programs or instructions, wherein when the computer programs or instructions are executed by the processor, they implement the steps of the method according to any one of claims 1 to 8.

Images