Operation and maintenance system and method for mine program management and state monitoring

By deploying the operation and maintenance system at the mine site, the difficulties in operation and maintenance caused by the diversification of components were solved, and efficient operation and maintenance of program management and status monitoring were achieved, thereby improving the stability of the system and the efficiency of fault diagnosis.

CN121029455APending Publication Date: 2025-11-28CHANGZHOU RES INST OF CHINA COAL TECH & ENG GRP +1
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202511029530.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-07-25
Publication Date
2025-11-28

AI Technical Summary

Technical Problem

Due to the diversity of program components at the mine site and the inconsistent ownership of each component, information gaps exist, leading to mutual interference and even errors between programs, which brings great difficulties to on-site operation and maintenance personnel.

Method used

An operation and maintenance system for mine program management and status monitoring is provided, including a database operation and maintenance module, a port monitoring module, a service management module, a system diagnostic module, a subscription data publishing and tracking module, and a distributed service detection module. These modules enable the installation, operation monitoring, updating, and data diagnosis of program components. Combined with the diagnostic data feedback module, the system sends the field status data back to the development team.

Benefits of technology

It enables efficient management and status monitoring of mining programs, reduces operational and maintenance pressure, mitigates the adverse consequences of component conflicts, and improves troubleshooting efficiency and system stability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121029455A_ABST
    Figure CN121029455A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of computer and intelligent mine program operation and maintenance, in particular to an operation and maintenance system and method for mine program management and state monitoring. A database operation and maintenance module, a port monitoring module, a service management module, a system diagnosis module, a subscription data publishing and tracking module, a distributed service detection module and a data management module are fused, so that the capability of monitoring general configuration or states of machines and services is realized, and data formats are unified; and fault diagnosis and troubleshooting are carried out on modules with problems rapidly. According to the application, various operations of related applications of the intelligent mine platform in a whole business process period such as deployment, updating, troubleshooting and configuration information updating are fused, and the method is very suitable for deployment maintenance and troubleshooting operation and maintenance of deployment personnel and developers on the intelligent mine application in a mine scene.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of computer and intelligent mine program operation and maintenance technology, specifically to an operation and maintenance system and method for mine program management and status monitoring. Background Technology

[0002] To adapt to the trend of informatization and implement national policies guiding the informatization of coal mining enterprises, over the years, coal mining enterprises have connected to various program component services. The deployment and management of each component service are independent, requiring on-site maintenance personnel to understand the deployment and maintenance details of components from different vendors. This undoubtedly brings a huge workload to on-site maintenance personnel and is also very prone to errors. For component developers, due to the diversity of on-site components, potential conflicts in ports, service names, and other aspects are inevitable. Therefore, in the context of the large-scale integration of coal industry systems and the construction of smart mines, in order to reduce maintenance pressure and mitigate the possibility of adverse consequences caused by on-site component conflicts, there is an urgent need for an operation and maintenance method for mine program management and status monitoring. Summary of the Invention

[0003] The technical problem to be solved by this invention is that due to the diversity of program components in the mine site and the inconsistent ownership of each component, there is an information gap, which leads to mutual influence and even errors between programs, and also brings great operation and maintenance difficulties to the on-site engineering implementation and component technicians.

[0004] Therefore, the present invention provides an operation and maintenance system and method for mine program management and status monitoring.

[0005] The technical solution adopted by this invention to solve its technical problem is:

[0006] An operation and maintenance system for mine program management and status monitoring includes a database operation and maintenance module, a port monitoring module, a service management module, a system diagnostic module, a subscription data publishing and tracking module, a distributed service detection module, and a data management module. The data management module is used for diagnosing and troubleshooting problems during program component operation; whenever data-related issues arise, this tool can be used to determine the diagnostic direction and eliminate possibilities. The database operation and maintenance module provides various efficient and easy-to-use operation and maintenance operations. The port monitoring module is used to resolve port conflicts in multi-service scenarios on a single machine, as well as performance issues caused by excessive port usage in extreme cases. The system diagnostic module provides monitoring capabilities for the general configuration or status of machines and services. The data subscription and publishing and tracking module provides a visual interface for data flow to developers when handling complex problems. The distributed service monitoring module is used to identify whether the current platform is in single-machine or dual-machine mode, and provides primary and backup machine identifiers in dual-machine mode.

[0007] An operation and maintenance method for mine process management and status monitoring includes,

[0008] Step 1: Check port usage and service name usage;

[0009] Step 2: Upload the database table structure file to the table structure synchronization page and perform table structure synchronization;

[0010] Step 3: Copy the program component files to the operation and maintenance tool, start the service in the service management module, and observe its running status;

[0011] Step 4: Investigate and resolve issues such as data backlog and data errors that occur during service operation;

[0012] Step 5: After all issues have been identified, modify the code and update the program components. Then, check the cache monitoring module or database module to see if there is data backlog and whether the cache and database are consistent.

[0013] Step six: Provide a diagnosis and send the data back.

[0014] Furthermore, in step four, the troubleshooting steps include: first, going to the cache consistency detection page of the database module to check which data is inconsistent, or checking whether there is data inconsistency through the cache monitoring module; if inconsistency exists, the data inconsistency should be dealt with first.

[0015] Furthermore, in step four, when an unexpected large number of requests occur and the direct caller cannot be found or the source cannot be traced, the subscription and release tracking module is checked to see if there are any new published or subscribed services, in order to determine whether a new, unknown service is causing the large number of requests.

[0016] Furthermore, in step four, when memory usage or a large backlog of data occurs, the cache monitoring module is checked first to determine if the cache size of the core service is abnormal, in order to quickly determine if the problem occurs in the core service. Afterwards, other caches are investigated in detail to uncover the specific structure.

[0017] Furthermore, in step six, the diagnostic data feedback specifically includes:

[0018] S6.1 Data Acquisition: The data acquisition structure adopts a unified input parameter format, and the caller organizes the data collection format according to the protocol.

[0019] S6.2 Data splitting, storing each indicator as a row, generating an initial SQLite indicator table;

[0020] S6.3 periodically polls and retrieves raw metrics, groups them by DataSource, and concatenates the data packets.

[0021] S6.4 encrypts the data and divides it into packets. After being divided into packets, an SQLite data packet table to be sent is formed, and the SQLite initial index table is updated.

[0022] S6.5 retrieves a batch of packets from the SQLite pending data packet table and sends them to the sending terminal. The sending terminal transmits the packets to the diagnostic data feedback module. The diagnostic data feedback module processes the packets and finally feeds back the diagnostic results to the sending terminal. If the diagnostic result indicates a successful update, the transmission status is updated in the pending data packet table.

[0023] Furthermore, in step S6.2, the data metadata + protocol data pattern is adopted when defining the fields of the table, and the database is SQLite. The final row in the database includes DataId, Time, DataSource, MetricCode, and Data. The protocol data defines the relevant information of MetriCode.

[0024] Furthermore, in step S6.3, concatenating the data packets involves piecing together the original data in batches to achieve compression and encoding, specifically including:

[0025] Filter out DataSoruce data with the same fixed number of records (or data that has timed out);

[0026] After conversion: First, obtain the protocol content by retrieving the MetricCode. Based on the Standard field in the protocol, determine that it is standard data. Then, convert the Time, MetricCode, and Data in the line into byte arrays and concatenate them in order.

[0027] If it is non-standard data, it is concatenated in the order of Time, MetricCode, DataLength, and Data. Here, DataLength occupies 2 bytes. The byte array data of each row is assembled into a byte string, and 1 byte (or 1 bit) is added before the above byte string to indicate whether it is standard data.

[0028] Furthermore, in step S6.5, the main function of the diagnostic data feedback module is to parse the incoming data, write it into the database, and then return the execution result. The data parsing process is as follows: after receiving the data, it first assembles the packets according to the packet sequence number and the total number of packets; after assembling the packets, it decrypts them; after decryption, it restores the data according to the protocol, classifies the restored data, writes it into ClickHouse, and then performs internal monitoring and analysis.

[0029] Furthermore, the data parsing process includes: first, determining whether it is standard data based on the first byte; if it is standard data, then reading 2 bytes to obtain the DataSource of the batch of data; then processing each metric; for each metric, first reading 8 bytes to obtain the metric occurrence time, then reading 2 bytes or the metric name MetricName; finding the value type and byte length in the protocol based on MetricName; then reading a specified number of bytes to convert it to the corresponding type, thus obtaining the metric value; subsequent metrics can be read in this manner until all reading is completed.

[0030] The beneficial effect of this invention is that it integrates various operations in the entire business process cycle of intelligent mining platform related applications, such as deployment, updates, troubleshooting, and configuration information updates. It is very suitable for deployment personnel and developers in mining scenarios to deploy, maintain, troubleshoot, and operate intelligent mining applications. Attached Figure Description

[0031] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0032] Figure 1 This is a schematic diagram illustrating the functional implementation of the service management module in this invention.

[0033] Figure 2 This is a schematic diagram illustrating the implementation of the data subscription and publishing tracking module function in this invention.

[0034] Figure 3 This is a flowchart illustrating the general steps of the operation and maintenance method for mine program management and status monitoring in this invention.

[0035] Figure 4 This is a flowchart of the service configuration update process in this invention.

[0036] Figure 5 This is a flowchart of the diagnostic data feedback module in this invention.

[0037] Figure 6 This is a flowchart of the data packet table update process of the present invention. Detailed Implementation

[0038] The present invention will now be described in further detail with reference to the accompanying drawings. These drawings are simplified schematic diagrams, illustrating only the basic structure of the invention, and therefore only show the components relevant to the invention.

[0039] In the description of this invention, it should be understood that the terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "radial," and "circumferential," etc., indicating orientation or positional relationships, are based on the orientation or positional relationships shown in the accompanying drawings and are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Furthermore, features defined with "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this invention, unless otherwise stated, "a plurality of" means two or more.

[0040] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0041] An operation and maintenance system for mine program management and status monitoring includes a service operation and maintenance module and a data management module.

[0042] The program component service operation and maintenance module includes a database operation and maintenance module, a port monitoring module, a service management module, a system diagnostic module, a subscription data publication tracking module, and a distributed service detection module. The program component service operation and maintenance module is primarily responsible for checking whether the port is occupied before installing the component program, checking whether the component is running normally after successful installation, and synchronizing the database table structure and modifying configuration files before updating the component to ensure correct updates. The data management module is used for diagnosing and troubleshooting problems during program component operation. Whenever data-related issues occur, this tool can be used to determine the direction of diagnosis and troubleshooting.

[0043] Specifically, the database operation and maintenance module provides a variety of efficient and easy-to-use operation and maintenance operations.

[0044] 1. Regarding MySQL data, it provides visualized DDL and DML operations, reducing the difficulty for operations and maintenance personnel in querying and managing data;

[0045] 2. For mines that require master-slave database configuration, a visual configuration interface will be provided, eliminating the need for operations and maintenance personnel to find the MySQL installation directory and modify configuration files. They can simply fill in the information on the configuration page according to the prompts.

[0046] 3. It provides a table structure synchronization function, which can provide a more convenient upgrade method during subsequent application service upgrades and deployments;

[0047] 4. Backup and recovery functions are provided to prevent database crashes and data corruption. Even in the event of irreversible data problems, non-technical personnel can use maintenance tools to restore the data to its normal operating state.

[0048] The port monitoring module aims to resolve port conflicts in multi-service scenarios on a single machine, as well as performance issues caused by excessive port usage in extreme cases. The module offers the following functionalities:

[0049] 1. Search for a specified port to check if the corresponding port is in use;

[0050] 2. Input the range port to query the number of ports in use;

[0051] 3. The search results can be categorized by service.

[0052] The system diagnostic module provides the ability to monitor the general configuration and status of machines and services. It offers an automated monitoring process that monitors process liveness, database connectivity, configuration file integrity, table structure and data validity, network connectivity, and whether memory and disk resources meet minimum requirements.

[0053] Typically, the management of services on a machine is done through command lines and task managers, but both require certain technical knowledge and the ability to identify which specific services belong to the intelligent mining application. (See reference...) Figure 1 The service management module addresses these two shortcomings by providing service management and service configuration:

[0054] 1. Service Management Functions: Provides status monitoring, version notifications, and operations such as stopping, running, restarting, and disabling specified services;

[0055] 2. Service configuration function: Allows modification of configuration files for each service and provides the function to restart services.

[0056] To handle the massive data processing required in intelligent mining systems, caching is widely used in general services. However, caching can lead to inconsistencies with the database. Therefore, a cache monitoring module can help quickly locate problems when data issues arise. The cache monitoring module provides retrieval based on both data type and data key, as well as retrieval response time.

[0057] Reference Figure 2 The data subscription and publish tracking module aims to provide developers with a visual interface for data flow when dealing with complex issues, thereby improving troubleshooting speed. Imagine this scenario: one day, a report comes in that a service has excessively high CPU utilization, and an interface is responding too slowly. After investigation, it's suspected that a related function subscription module is making a large number of calls to this interface. However, based on experience, it's inappropriate for this subscription service to handle such a large volume of data, and checking known publishers hasn't revealed any significant data publishing. Without this module, unless precise logging is pre-set, the only option is to add log traces to find the publishing source. However, with the publish-subscribe tracking module, developers can quickly identify all publishers and then rapidly pinpoint the problematic module for fault diagnosis and troubleshooting, greatly improving the efficiency of problem finding.

[0058] The distributed service monitoring module, here is different from the distributed in the Internet concept. It is more accurately described as service monitoring under dual-machine hot standby. This module can identify whether the current platform is in single-machine mode or dual-machine mode. In dual-machine mode, it provides primary and standby machine identifiers.

[0059] The diagnostic data feedback module is currently deployed in mines almost entirely on-site, with each site storing all diagnostic data locally and not sharing it with the development team. This makes it impossible to track the system's performance and functionality on-site; otherwise, the data would be lost without a trace, and the application's status would be unknown or unknowable after installation. Furthermore, unstable on-site networks and multiple parties occupying remote machines further complicate troubleshooting and analysis of on-site systems.

[0060] To address this issue, this module will establish a diagnostic data feedback system to send system status data such as CPU utilization and memory usage, as well as critical business error logs, back to the development team. With this data, problems can be quickly identified and diagnosed. Furthermore, an analysis and diagnostic system can be built later to continuously optimize and improve the service system.

[0061] An operation and maintenance method for mine program management and status monitoring, which realizes program component installation, operation monitoring, updates, and data diagnosis, such as... Figure 3 As shown, the general steps of this operation and maintenance method include:

[0062] Step one: Before deploying a new program component, check the port detection module to see if the port of the current component is already in use. If it is, you need to switch to an unused port. Similarly, check the service management module to see if the service name is in use. If it is, you need to change it. Figure 4 As shown.

[0063] Step two: Open the database management module, upload the database table structure file to the table structure synchronization page, and execute the table structure synchronization. Additionally, if it's a dual-machine hot standby mode, you also need to enter the host IP address on the MySQL synchronization page and execute the data synchronization operation.

[0064] Step three: After preparing the prerequisites, copy the program component files to the operation and maintenance tool, start the service in the service management module, and observe its running status. The service installation is now complete.

[0065] Step four: During service operation, issues such as data backlog and data errors occurred. For data errors, first check the cache consistency check page of the database module to see which data is inconsistent, or check the cache monitoring module for inconsistencies. If inconsistencies are found, address them first before proceeding with further processing. Subsequent investigation can begin with checking the logs.

[0066] When an unexpected surge in requests occurs, and the direct caller cannot be found or the source cannot be traced, check the publish / subscribe tracking module for any new published or subscribed services to determine if a new, unknown service is causing the surge in requests.

[0067] When memory usage or a large backlog of data occurs, the cache monitoring module should be checked first to see if the cache size of the core service is abnormal, in order to quickly determine if the problem is occurring in the core service. Then, other caches should be investigated in detail to determine the specific structure.

[0068] Step five: After all issues have been identified, the code needs to be modified before updating the program components. At this point, the corresponding service needs to be stopped in the service management module, the program updated, and the configuration information updated through the service configuration page. Finally, the service is started in the service management module. Afterwards, the cache monitoring module or database module is used to observe whether data is backlogged and whether the cache and database are consistent.

[0069] Step six: Provide a diagnosis and return the data, refer to... Figure 5 The diagnostic data feedback specifically includes:

[0070] S6.1 Data Acquisition

[0071] The data acquisition structure adopts a unified input parameter format, which is organized by the caller according to the protocol. The protocol includes custom metricCode and dataSource, as shown below:

[0072]

[0073] S6.2 data splitting, storing each indicator as a row, generating an initial SQLite indicator table.

[0074] Considering future expansion and to simplify the design and development process while ensuring data order, a metadata + protocol data model is adopted when defining table fields, and SQLite is used as the database.

[0075] The example below shows a single row that ultimately ends up in the database. Each row includes a unique data identifier (DataId), a millisecond-level timestamp (Time), a data source (DataSource), a metric code (MetricCode), and a byte array identifier (Data) for the specific metric data. The metric code can be a system metric such as CPU, network, or hard disk, or it can be a business-defined metric.

[0076] Table 1 contains a row of data from the database.

[0077] DataId Time DataSource MetricCode Data 1242342352352 322340000 1 1 0x0008

[0078] The protocol data defines relevant information about the MetriCode, such as the metric name, data type, data length, etc., as shown below:

[0079]

[0080]

[0081] S6.3 periodically polls and retrieves raw metrics, groups them according to DataSource, and concatenates the data packets.

[0082] Data packet splicing involves combining raw data in batches to achieve compression and encoding. The data transformation is as follows:

[0083] Before conversion: Filter out DataSoruces with the same fixed number of records (or expired data), as shown in the two rows of data in the table below, which have the same number of records.

[0084] Table 2 shows the results of filtering data from DataSoruce with the same number of records.

[0085]

[0086] After conversion:

[0087] 1. First, obtain the MetricCode to get the protocol content. Based on the Standard field in the protocol, if it is standard data, convert the Time, MetricCode, and Data in that line into byte arrays and concatenate them in order. For example, the first line can be concatenated as 0x000000000000000100010008, denoted as Datai.

[0088] If the data is non-standard, it is concatenated in the order of Time, MetricCode, DataLength, and Data. Here, DataLength occupies 2 bytes.

[0089] 2. Assemble the byte array data from each row to obtain [Data1Data2Data3...Datan]

[0090] 0x000000000000000100010008 000000000000000200020010

[0091] Add 1 byte (or 1 bit) before the byte string to indicate whether it is standard data (this is not needed if there is a protocol identifier), and 2 bytes to identify the data source, as shown below:

[0092] 0x0 0001 000000000000000100010008 000000000000000200020010...

[0093] For non-standard data, the first byte is 1. In this case, the two bytes after MetricName in the byte array originally constructed in the order of Time, MetricName, and Data indicate the length of the data. It should be noted that with the Standard protocol, the header bytes are no longer needed.

[0094] S6.4 uses a Go language encryption program to encrypt the data and divide it into packets. After being divided into packets, an SQLite data packet table to be sent is formed, and the SQLite initial indicator table is updated, while the corresponding indicators before the update are deleted.

[0095] After concatenating the data, it needs to be encrypted. To avoid excessive data volume and facilitate the management of the return progress, the encrypted data needs to be divided according to its size. By default, it is divided into 5M packets, as shown in the table below. The same dataid belongs to the same packet. After receiving the data, the receiver will reassemble it as needed according to PackSeq.

[0096] Table 3. Data Packaging Illustration

[0097]

[0098] It should be noted that the system periodically deletes successfully sent data packets, resets data packets that have been in the sending process for a long time, and deletes old data if the data packet waiting list becomes too large. Figure 6 As shown, by comparing the old and new data report structures, the structure that needs to be changed is identified. If a structure that needs to be changed exists, the change SQL is generated and executed to complete the update; otherwise, the state before the change is saved.

[0099] S6.5 terminal processing flow:

[0100] First, check the external network connectivity and test the current platform performance. If the performance allows, proceed with the execution. The platform performance can be easily judged based on the maximum HTTP latency.

[0101] A batch of packets (batch size is configurable) is retrieved from the SQLite pending data packet table and sent to the sending terminal (such as a browser, APP, etc.). The transmission status is updated to "sending". The sending terminal transmits the packets to the diagnostic data feedback module via HTTP. The diagnostic data feedback module reassembles, decrypts, and parses the data according to the protocol, then writes it to ClickHouse. Finally, the diagnostic results are fed back to the sending end. If the diagnostic result is "update successful", the transmission status is updated to the pending data packet table.

[0102] Specifically, the diagnostic data feedback module mainly parses the incoming data, writes it into the database, and then returns the execution result.

[0103] 1. Specifically, after receiving data, the packets are first assembled based on their sequence number and total number.

[0104] 2. Decrypt the package after it is assembled;

[0105] 3. After decryption, restore the data according to the protocol (or perhaps a version concept). For example, if you receive the following data: 0x0 0001 000000000000000100010008 000000000000000200020010... First, determine if it is standard data based on the first byte (this step is omitted if the Standard identifier in the protocol is present). If it is standard data, read the next 2 bytes to obtain the DataSource for this batch of data. Then process each metric. For each metric, first read 8 bytes to obtain the metric occurrence time T, then read 2 bytes or the metric name MetricName. Based on MetricName, find the value type and byte length in the protocol, then read the specified number of bytes to convert it to the corresponding type, thus obtaining the metric value. Subsequent metrics can be read continuously in this way until all data is read. The data is then categorized, written to ClickHouse, and then monitored and analyzed internally.

[0106] Based on the above-described preferred embodiments of the present invention, and through the foregoing description, those skilled in the art can make various changes and modifications without departing from the inventive concept. The technical scope of this invention is not limited to the contents of the specification, but must be determined by the scope of the claims.

Claims

1. An operation and maintenance system for mine process management and status monitoring, characterized in that, The system includes a database operation and maintenance module, a port monitoring module, a service management module, a system diagnostics module, a subscription data publishing and tracking module, a distributed service detection module, and a data management module. The data management module is used for troubleshooting and diagnosing problems during program component operation; whenever data-related issues arise, this tool can be used to determine the diagnostic direction and eliminate possibilities. The database operation and maintenance module provides various efficient and easy-to-use operation and maintenance operations. The port monitoring module resolves port conflicts in multi-service scenarios on a single machine, as well as performance issues caused by excessive port usage in extreme cases. The system diagnostics module provides monitoring capabilities for the general configuration or status of machines and services. The data subscription and publishing and tracking module provides developers with a visual interface for data flow when handling complex problems. The distributed service monitoring module identifies whether the current platform is in single-machine or dual-machine mode, and provides primary and backup machine identifiers in dual-machine mode.

2. A method for operation and maintenance of mine processes and status monitoring, characterized in that, include, Step 1: Check port usage and service name usage; Step 2: Upload the database table structure file to the table structure synchronization page and perform table structure synchronization; Step 3: Copy the program component files to the operation and maintenance tool, start the service in the service management module, and observe its running status; Step 4: Investigate and resolve issues such as data backlog and data errors that occur during service operation; Step 5: After all issues have been identified, modify the code and update the program components. Then, check the cache monitoring module or database module to see if there is data backlog and whether the cache and database are consistent. Step six: Provide a diagnosis and send the data back.

3. The operation and maintenance method for mine program management and status monitoring according to claim 2, characterized in that, In step four, the troubleshooting steps include: first, going to the cache consistency detection page of the database module to see which data is inconsistent, or checking whether there is data inconsistency through the cache monitoring module; if inconsistency exists, the data inconsistency should be dealt with first.

4. The operation and maintenance method for mine program management and status monitoring according to claim 2, characterized in that, In step four, when an unexpected large number of requests occur and the direct caller cannot be found or the source cannot be traced, check the subscription and publication tracking module to see if there are any new published or subscribed services, in order to determine whether a new, unknown service is causing the large number of requests.

5. The operation and maintenance method for mine program management and status monitoring according to claim 2, characterized in that, In step four, when memory usage or a large amount of data backlog occurs, the cache monitoring module is checked first to see if the cache quantity of the core service is abnormal, so as to quickly determine whether the problem occurs in the core service. Then, other caches are investigated in detail to find out the specific structure.

6. The operation and maintenance method for mine program management and status monitoring according to claim 2, characterized in that, In step six, the diagnostic data feedback specifically includes: S6.1 Data Acquisition: The data acquisition structure adopts a unified input parameter format, and the caller organizes the data collection format according to the protocol. S6.2 Data splitting, storing each indicator as a row, generating an initial SQLite indicator table; S6.3 periodically polls and retrieves raw metrics, groups them by DataSource, and concatenates the data packets. S6.4 encrypts the data and divides it into packets. After being divided into packets, an SQLite data packet table to be sent is formed, and the SQLite initial index table is updated. S6.5 retrieves a batch of packets from the SQLite pending data packet table and sends them to the sending terminal. The sending terminal transmits the packets to the diagnostic data feedback module. The diagnostic data feedback module processes the packets and finally feeds back the diagnostic results to the sending terminal. If the diagnostic result indicates a successful update, the transmission status is updated in the pending data packet table.

7. The operation and maintenance method for mine program management and status monitoring according to claim 6, characterized in that, In step S6.2, the fields of the table are defined using a metadata + protocol data model, and the database is SQLite. The final row in the database includes a unique data identifier DataId, a millisecond-level timestamp Time, a data source DataSource, a metric code MetricCode, a byte array identifier Data for the specific metric data, and the protocol data defines the relevant information of MetriCode.

8. The operation and maintenance method for mine program management and status monitoring according to claim 6, characterized in that, In step S6.3, data packet splicing involves concatenating the original data in batches to achieve compression and encoding, specifically including: Filter out DataSoruce data with the same fixed number of records (or data that has timed out); After conversion: First, obtain the protocol content by retrieving the MetricCode. Based on the Standard field in the protocol, determine that it is standard data. Then, convert the Time, MetricCode, and Data in the line into byte arrays and concatenate them in order. If it is non-standard data, it is concatenated in the order of Time, MetricCode, DataLength, and Data. Here, DataLength occupies 2 bytes. The byte array data of each row is assembled into a byte string, and 1 byte (or 1 bit) is added before the above byte string to indicate whether it is standard data.

9. The operation and maintenance method for mine program management and status monitoring according to claim 6, characterized in that, In step S6.5, the main function of the diagnostic data feedback module is to parse the incoming data, write it into the database, and then return the execution result. The data parsing process is as follows: after receiving the data, it first assembles the packets according to the packet sequence number and the total number of packets; after assembling the packets, it decrypts them. After decryption, the data is restored according to the protocol, categorized based on the restored data, written to ClickHouse, and then monitored and analyzed internally.

10. The operation and maintenance method for mine program management and status monitoring according to claim 9, characterized in that, The data parsing process includes: first, determining whether it is standard data based on the first byte; if it is standard data, then reading 2 bytes to obtain the DataSource of the batch of data; then processing each metric; for each metric, first reading 8 bytes to obtain the metric occurrence time, then reading 2 bytes or the metric name (MetricName); finding the value type and byte length in the protocol based on the MetricName; then reading a specified number of bytes to convert it to the corresponding type, thus obtaining the metric value; subsequent metrics can be read in the same way until all data is read.

Citation Information

Cited By

  • Operation and maintenance state monitoring method and system applied to bucket wheel machine unattended system

    CN121084992A