Coal mine disaster monitoring data acquisition system

Abstract

The invention relates to a coal mine disaster monitoring data acquisition system, and belongs to the technical field of coal mine disaster monitoring. The system aims to solve the problems of data islands, lack of collaborative linkage among equipment systems, untimely abnormal alarm processing and the like in coal mine safety management, and comprises a data center and a data acquisition and transmission software platform, and the data center is responsible for data storage, processing and service; and the data acquisition and transmission software platform is responsible for data acquisition, transmission and processing. The system realizes flexible integration of different monitoring subsystems through plug-in design, supports multiple data acquisition modes, and ensures timeliness, accuracy and reliability of data. Besides, strict information resource management and information safety guarantee management are set in the system, comprehensive and detailed data support is provided for coal mine disaster analysis and early warning, and the coal mine safety guarantee level is effectively improved.

Description

Technical Field

[0001] This invention belongs to the field of coal mine disaster monitoring and control technology, and relates to a coal mine disaster monitoring data acquisition system. Background Technology

[0002] Coal is my country's primary energy source, and coal mine safety is crucial to the sustainable development of the coal industry, national energy security, and the lives and property of millions of miners. In recent years, through the concerted efforts of all parties, the coal mine safety situation has steadily improved, but some prominent problems still exist in coal mine safety management. The informatization process in coal mines has completed the construction of systems such as safety monitoring systems, personnel positioning systems, roof monitoring systems, fiber optic temperature measurement systems, and major electromechanical equipment monitoring systems. Although the overall automation level of coal mines is relatively high, there is a lack of unified data integration, monitoring, and early warning systems for coal mine disasters such as gas, water, fire, dust, and roof falls. Data silos still exist, and there is a lack of coordinated control between equipment systems. Problems such as untimely handling of abnormal alarms are prominent. There is an urgent need to break down information silos and build a coal mine disaster monitoring, analysis, and early warning system to achieve deep information integration, automatic anomaly identification, hierarchical dynamic early warning, and real-time multi-terminal dissemination, thereby improving the level of coal mine safety assurance. Summary of the Invention

[0003] In view of this, the purpose of this invention is to provide a coal mine disaster monitoring data acquisition system. By utilizing the gas, wind speed, dust, delamination, fiber optic temperature measurement, bundled tube monitoring, hydrology, microseismic, and stress sensors already deployed in the coal mine, and based on the existing intelligent safety production centralized control platform, the system enables the centralized acquisition and analysis of coal mine monitoring and safety production data. After processing, the data is stored in the disaster monitoring and early warning system data center according to a unified and standardized data standard, providing detailed data support for coal mine disaster analysis and early warning.

[0004] To achieve the above objectives, the present invention provides the following technical solution:

[0005] A coal mine disaster monitoring data acquisition system includes at least a data center and a data acquisition and transmission software platform. The data center includes a data resource layer, a data processing layer, a thematic data layer, a management layer, and a service layer. The data acquisition and transmission software platform includes a file generator, a file uploader, a file parser, and a data importer. The data information acquired by the data acquisition and transmission software platform is transmitted to the database of the data center.

[0006] The data center also includes several databases, which are divided into basic information databases, monitoring databases, and business databases, each used to store corresponding information.

[0007] In the data acquisition and transmission software platform, the data exchange file format is first defined in the file generator. Data exchange is performed according to the defined data exchange file format, and the data information is classified. Data files and attachments are generated according to the protocol, and the data files are stored in the specified upload directory. The file uploader scans the upload directory and processes the data files of each mine in a multi-threaded manner, and uploads the upload directory to the file parser. The file parser parses, stores, backs up, and cleans the uploaded files. The uploaded attachments are synchronized to the web server, and other data is manually entered through the data importer.

[0008] The data acquisition and transmission software platform is also designed with different acquisition methods for different types of data to be collected, and data is collected according to the corresponding designed acquisition methods for different types of data.

[0009] Furthermore, the data resource layer stores basic and monitoring data collected from the mining end, shared data collected from third parties, log data automatically generated by the data center, and result data generated by the application system;

[0010] The data processing layer utilizes the raw data from the mining end and the result data generated by cloud applications, and stores the data in the data topic library through data extraction, data transformation, data cleaning, and data loading.

[0011] After being processed by the data processing layer, the thematic data layer extracts thematic data from different dimensions and stores the thematic data in the thematic data layer.

[0012] Management personnel should set general data management indicators and methods;

[0013] The service layer is used to provide data service interfaces to the outside world for cloud applications and systems to call and interact with;

[0014] It also includes information resource management and information security assurance management. Data resource management provides auxiliary functions for data resource planning, while information security assurance management provides security assurance.

[0015] Furthermore, the basic information database refers to the coal mine basic information database, which includes at least basic information, license information, mining information, personnel information, disaster factor information, safety status information, and mine map information. For each type of information, a corresponding information table is established, and each data table specifies the attribute name, data type and length, as well as relevant remarks.

[0016] The monitoring database includes a safety environment monitoring information database, an underground worker information database, an electromechanical equipment monitoring information database, and an equipment information database. Among them, the safety monitoring information database includes real-time information, data acquisition status information, substation equipment information, alarm information, statistical information, and configuration information. The configuration information is divided into analog quantity configuration information, switch quantity configuration information, and cumulative quantity configuration information, and corresponding information tables are also established.

[0017] The underground worker information database includes real-time / historical information, alarm information, and statistical information. The real-time information and historical information include real-time / historical mine information and real-time / historical personnel location information, and corresponding information tables are also established.

[0018] The electromechanical equipment monitoring information database includes equipment parameter definition information, extended information, and real-time / historical information of electromechanical equipment. Among them, the extended information includes analog quantity extended information and digital quantity extended information, and corresponding information tables are also established.

[0019] The equipment information database includes operating status data of major equipment in the production process, operating status data of major equipment in coal mining faces, power supply system data, transportation monitoring, ventilation fan monitoring system data, water supply and drainage system data, air compressor monitoring data, and hoisting system data. Corresponding information tables are also established.

[0020] The management business databases include the coal mine safety production inspection information database and the coal mine risk analysis database. The coal mine safety production inspection information database includes abnormal alert information and inspection record information; the coal mine risk analysis database includes accident information, gas over-limit information, and hidden danger information, and corresponding information tables are also established.

[0021] Furthermore, in the data acquisition and transmission software platform, the acquired basic data and business data are processed by the file generator to obtain data files and attachments, and the data files are packaged according to the set format; the file uploader uploads the data files and attachments packaged by the file generator to the file parser, and the file parser completes the parsing, storage, backup and cleanup of the uploaded files.

[0022] Furthermore, the file generator defines the data exchange file format, whose format requirements include:

[0023] (1) All data exchange files are plain text files in UTF-8 encoding format with the extension .txt;

[0024] (2) All data exchange files in this agreement will be generated with the extension .tmp, and then changed to the formal .txt extension after the data exchange files are generated.

[0025] (3) The directory for storing data exchange files is generated by the file generator as required, and the data transfer program is ensured to have access permissions to the folder.

[0026] (4) The data exchange file is generated by the file generator and cleaned up by the file uploader after successful transmission. The file uploader is responsible for data cleanup.

[0027] (5) When generating a data exchange file, the file is generated even if no new data is generated for that item, and the number of data records in its header is 0.

[0028] The file naming rules for data exchange filename format are as follows:

[0029] Coal mine code + business data code + data type identifier + yyyyMMddHHmmss.txt

[0030] Among them, the coal mine code is a string of preset length, the business data code is a string of preset length, yyyyMMddHHmmss is the time when the file was generated; the data type identifier is used to distinguish different data categories;

[0031] For the content of data exchange files, all data exchange files include a data header and a data body. The data header is located on the first line of the entire document; the data body begins from the second line. The data header includes the coal mine code, business data code, data type identifier, and generation time. The data body consists of multiple data records, each occupying one line, and each data record consists of multiple fields. The constraints on the data body are as follows:

[0032] Each data record occupies one line and ends with a newline character (\r\n). Each line corresponds to a unique record; newline characters are not allowed within each data record.

[0033] Numbers must be formatted in English half-width mode; each data record contains multiple fields, separated by English half-width semicolons ";", and the number of semicolons ";" in each data record line must be one less than the number of fields.

[0034] The semicolon ";" is not allowed in the field values ​​of record fields. If it is necessary to use this delimiter field, use the semicolon ";" in Chinese input mode instead.

[0035] The date and time format is uniformly defined as "yyyy-MM-dd HH:mm:ss". If the month, day, hour, minute, or second is less than two digits, it should be padded with "0" at the beginning.

[0036] Information is categorized in the data acquisition and transmission software platform, and the categorized data is stored in the corresponding database tables. All data is divided into personnel data, equipment data, environmental data, safety management data, production management data, and comprehensive management data.

[0037] The data files generated by the aforementioned file generator, as well as some data attachment files, use the .tmp extension for the data files. After closing the file, the official files, renamed with the .txt extension, are stored in a designated directory called the upload directory. The upload directory has four levels of subdirectories: the first level is UploadSAWS, the second level is Mine Code, the third level is Business Data System Code, and the fourth level is Data Category. Among these, Realtime is the real-time data directory, History is the historical data directory, Attachment is the attachment file directory, and Backup is the backup file directory.

[0038] Furthermore, the file uploader scans the upload directory at configured intervals. If a file with a .txt extension is generated, it uses multi-threading to process the data files of each mine in parallel. It traverses all business system directories in sequence, using the FTP / TCP interface to first upload the Realtime directory file, then the Attachment directory file, and finally the History directory file. The uploaded file directory remains consistent with the original directory. During the file upload process, filenames with the .tmp extension are used. After the upload is complete, the filename is renamed to the official filename. After a successful file upload, the file is moved to the backup directory, and a file upload verification record is generated, recording the uploaded filename, file size, and upload time.

[0039] The file uploader also has a function to clean up backup directory files, which is enabled by default; the file cleanup function automatically cleans up backup files older than the configured time period.

[0040] Furthermore, the file parser scans the local upload directory at configured intervals. If a file with the .txt extension is generated, it uses a multi-threaded approach to process the data files of various business systems in the mine in parallel. It traverses all business system directories in sequence and performs data verification according to the data exchange specifications. It verifies whether the file name, file header, and file fields conform to the specifications. If the data has an attachment file but the corresponding attachment cannot be found, the verification is considered to have failed. Files that fail verification are stored in the CheckError directory. After successful verification, the data is processed for storage. Real-time data is processed first, followed by historical data files.

[0041] The file parser's data entry module has a data caching function. When the number of records in the cache queue is greater than the record quantity threshold, the batch data entry interface is used to perform data entry. When the number of records in the cache queue is less than the record quantity threshold, the insert statement is used directly to perform data entry. The data entry interval is configured according to a preset time.

[0042] After the file parsing is complete, the data file is moved to the backup directory, and a file parsing verification record is generated, which records the file name, the number of file records, the file verification result, and the file processing time.

[0043] The file parser also supports the function of cleaning up backup directory files, automatically cleaning up backup files older than a configured time period;

[0044] The attachments and drawing files in the Attachment directory, as well as the verification error files in the CheckError directory, including the file parsing and verification record files, are synchronized to the web server through the "drawing synchronization function".

[0045] Furthermore, the system also includes data acquisition plugins for connecting various data subsystems, and a plugin manager for uniformly loading, starting, updating, and stopping various data acquisition plugins. The plugin manager is integrated into the data acquisition and transmission software platform. The final implementation class DataAdapter inherits the IDataAdapter interface through an extended interface. The DataAdapter class first inherits the general data adaptation template defined by the abstract class DANormalTemplet, then inherits the base class for generating data in the acquisition module defined by the abstract class DABase, and then connects to the IDataAdapter interface.

[0046] The IDataAdapter interface synchronously connects to the IConfigWnd interface, the ISerializeXmlX interface, and the IDevice interface. The IConfigWnd interface defines the display and operation related to the user interface, the ISerializeXmlX interface is used to save XML format data to a file or database, and the IDevice interface is used to abstractly define the data acquisition plugin.

[0047] The DataAdapter class performs the final data reading and message queue generation, and transmits the data to the server itself. The DataAdapter class contains a DataManager object instance, which includes several functions: GetDIDA (analog quantity definition information), GetDIDD (digital quantity definition information), GetDICR (control relationship definition information), GetReal (real-time data information), GetRealAlarm (real-time alarm information), GetRealCut (real-time power outage information), GetFiveStc (minute statistics information), GetAStatusRecord (analog quantity status change record), GetDStatusRecord (digital quantity status change record), GetDRunRecord (digital quantity operation record), GetFBRecord (power supply record information), IsWarring (alarm detection), IsCut (power outage detection), GetStatus (status conversion), and GetTypeID (measuring point type encoding conversion).

[0048] Furthermore, the system also includes a flat file data source subsystem. The flat file data source subsystem refers to storing relevant data in flat files or in a database server, but without providing a direct database service access mechanism. Instead, it provides the data to third-party integrators in the same read-only flat file manner. The integrators then convert the flat files into standard data files, and the acquisition module reads the data and uploads it to the message sequence.

[0049] Furthermore, the system also includes an OPC-type data source subsystem. Multiple subsystems of the coal mine production control class collect data based on the OPC-type data source system. The multiple subsystems of the coal mine production control class or the integrated configuration system provide an OPC Server to provide system data acquisition services to third parties. During integration, the system directly obtains real-time system data and equipment status information from the OPC Server through the OPC-type data source subsystem and converts it into a standard format for use in message sequences.

[0050] The beneficial effects of this invention are as follows:

[0051] This system, through a unified data acquisition and transmission software platform, enables centralized collection, processing, and storage of various monitoring and control data from coal mines, breaking down previous data silos and promoting deep information integration. This provides comprehensive and detailed data support for subsequent disaster analysis and early warning.

[0052] This system employs multi-threaded processing and batch data import techniques, significantly improving data processing efficiency. The file uploader and file parser process data files in parallel using multi-threading, ensuring data timeliness and accuracy. Simultaneously, the use of the batch data import interface reduces the time consumed during the data import process.

[0053] This system supports different acquisition methods for different categories of data and provides a plug-in-based data acquisition plugin design. This design allows the system to flexibly adapt to the data acquisition needs of different subsystems, improving the system's compatibility and scalability.

[0054] This system employs rigorous management of data resources, incorporating information resource management and information security assurance modules to ensure data security and integrity. Furthermore, features such as file cleanup and backup effectively prevent the risk of data loss and leakage.

[0055] The modular design and plug-in data acquisition modules of this system make it easy to maintain and expand. When new data acquisition points need to be added, only the corresponding data acquisition module needs to be developed and integrated into the system, without the need for large-scale modifications to the system.

[0056] Other advantages, objectives, and features of the invention will be set forth in part in the description which follows, and in part will be apparent to those skilled in the art from the following examination, or may be learned from practice of the invention. The objectives and other advantages of the invention can be realized and obtained through the following description. Attached Figure Description

[0057] To make the objectives, technical solutions, and advantages of the present invention clearer, the preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings, wherein:

[0058] Figure 1 This is a schematic diagram of the data center architecture according to an embodiment of the present invention;

[0059] Figure 2 This is a data acquisition topology diagram according to an embodiment of the present invention;

[0060] Figure 3 This is a schematic diagram of the interface connection relationship for data acquisition and transmission in an embodiment of the present invention;

[0061] Figure 4 This is a schematic diagram of the functional architecture of the file uploader according to an embodiment of the present invention;

[0062] Figure 5 This is a schematic diagram of the standard interface structure in an embodiment of the present invention;

[0063] Figure 6This is a schematic diagram illustrating the inheritance relationship of the DataAdapter class in the security monitoring system according to an embodiment of the present invention;

[0064] Figure 7 This is a schematic diagram of the structure of the DataManager class in the security monitoring system according to an embodiment of the present invention;

[0065] Figure 8 This is a schematic diagram illustrating the inheritance relationship of the DataAdapter class in the personnel positioning system according to an embodiment of the present invention;

[0066] Figure 9 This is a schematic diagram of the structure of the DataManager class in the personnel positioning system according to an embodiment of the present invention;

[0067] Figure 10 This is a schematic diagram of the structure of an OPC-type system plugin according to an embodiment of the present invention. Detailed Implementation

[0068] The following specific examples illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0069] The accompanying drawings are for illustrative purposes only and are schematic diagrams, not actual pictures. They should not be construed as limiting the invention. To better illustrate the embodiments of the invention, some parts in the drawings may be omitted, enlarged, or reduced, and do not represent the actual product dimensions. It is understandable to those skilled in the art that some well-known structures and their descriptions may be omitted in the drawings.

[0070] In the accompanying drawings of the embodiments of the present invention, the same or similar reference numerals correspond to the same or similar components. In the description of the present invention, it should be understood that if terms such as "upper," "lower," "left," "right," "front," and "rear" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, they are only for the convenience of describing the present 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. Therefore, the terms used to describe positional relationships in the drawings are only for illustrative purposes and should not be construed as limiting the present invention. For those skilled in the art, the specific meaning of the above terms can be understood according to the specific circumstances.

[0071] Please see Figures 1-10This is a coal mine disaster monitoring data acquisition system.

[0072] Example 1

[0073] This embodiment describes in detail a coal mine disaster monitoring data acquisition system, which includes at least a data center and a data acquisition and transmission software platform. The data center includes a data resource layer, a data processing layer, a thematic data layer, a management layer, and a service layer. The data acquisition and transmission software platform includes a file generator, a file uploader, a file parser, and a data importer. The data information acquired by the data acquisition and transmission software platform is transmitted to the database of the data center.

[0074] The data center also includes several databases, which are divided into basic information databases, monitoring databases, and business databases, each used to store corresponding information.

[0075] In the data acquisition and transmission software platform, the data exchange file format is first defined in the file generator. Data exchange is performed according to the defined data exchange file format, and the data information is classified. Data files and attachments are generated according to the protocol, and the data files are stored in the specified upload directory. The file uploader scans the upload directory and processes the data files of each mine in a multi-threaded manner, and uploads the upload directory to the file parser. The file parser parses, stores, backs up, and cleans the uploaded files. The uploaded attachments are synchronized to the web server, and other data is manually entered through the data importer.

[0076] The data acquisition and transmission software platform is also designed with different acquisition methods for different types of data to be collected, and data is collected according to the corresponding designed acquisition methods for different types of data.

[0077] In this embodiment, the overall architecture of the data center is as follows: Figure 1 As shown, the data resource layer stores basic data and monitoring data collected from the mine, shared data collected from third parties, log data automatically generated by the data center, and result data generated by application systems. The data processing layer utilizes the raw data from the mine and the result data generated by cloud applications, extracting, transforming, cleaning, and loading data to further extract data into a thematic data repository (data warehouse), providing high-quality data sources for regulatory and supervisory departments for data analysis and monitoring decision-making. The thematic data layer, after being processed by the data processing layer, stores highly refined data from different dimensions for business systems to access and display to users. The management layer mainly specifies the data management indicators and methods. The service layer primarily provides data service interfaces for external communication and interaction with cloud applications and systems.

[0078] Additional information resource management and information security assurance management are also included. Data resource management serves as a support system for data resource planning and provides a platform for ordinary users to utilize and maintain planning outcomes and data. Information security assurance management emphasizes the necessity of prioritizing information security in data center construction and specifies the methods for providing security assurance capabilities.

[0079] More specifically, the data resource layer includes basic data, monitoring data, operational data, thematic data, and shared data. Basic data includes basic information, mining information, safety permit information, mine map information, safety status information, disaster information, and organizational information; monitoring data includes environmental safety, personnel location, disaster data, and equipment operation data; operational data includes inspection data, safety hazard data, and quality standardization data; thematic data includes early warning data, KPI indicator data, safety evaluation data, and analytical model library data; and shared data refers to data from other systems.

[0080] The data processing layer integrates real-time data through ECA, including performance analysis, proactive control, secondary calculation, and intelligent alarms; then it uses ETL to organize the data, including data extraction, data clarification, data transformation, and data loading; finally, it performs data processing, including indicator merging, data aggregation, business analysis, and data organization.

[0081] The thematic data layer stores thematic data, including statistical data, early warning data, accident case database, expert model database, and policy and regulatory data.

[0082] The management layer is used for metric monitoring, quality management, access control, and data maintenance; the service layer provides directory services, storage services, exchange services, log services, and retrieval services.

[0083] In more detail, the design of the data center for the database and corresponding tables follows the principles of data integrity, distributed processing, interoperability, optimization, data location, transparency of the actual data storage format and the methods used to store the data to the user, simplicity, scalability, and advanced technology.

[0084] The databases mainly consist of three categories: basic information databases, monitoring databases, and business databases. Details are as follows:

[0085] The basic information database mainly refers to the coal mine basic information database. The coal mine basic information database consists of eight types of data tables, namely basic information, license information, mining information, personnel information, disaster factor information, safety status information, mine map information, and other information, as shown in Tables 1-8.

[0086] The basic information table shown in Table 1 below includes the following information: number, attribute name, data type and length, and remarks.

[0087] Table 1

[0088]

[0089]

[0090] Table 2 below shows the document information table, including document name, document number, issuing authority, validity start date, and validity end date:

[0091] Table 2

[0092] serial number Data item name Type, Length Remark 1 ID Number Character type (10) primary key 2 Document Name Character type (20) 3 Issuing authority name Character type (20) 4 Issuance time Date type Date: Year Month Day 5 Validity period start date Date type 6 Expiry date Date type

[0093] Table 3 below shows the mining information table, which includes data item names, data types and lengths, and remarks:

[0094] Table 3

[0095] serial number Data item name Type, Length Remark 1 Approved mining areas (number): Numerical 2 Number of coal mining faces approved: Numerical 3 Number of approved tunneling faces: Numerical 4 Coal mining methods: Numerical 5 Number of fully mechanized mining faces: Numerical 6 Number of mechanized mining faces: Numerical 7 Number of blasting working faces: Numerical

[0096] The personnel information table is shown in Table 4 below:

[0097] Table 4

[0098] serial number Data item name Type, Length Remark 1 Total number of registered employees in coal mines Numerical 2 Number of people working underground Numerical 3 Number of inspectors Numerical 4 Number of security inspectors Numerical 5 Number of leaders on duty Numerical 6 Maximum number of workers in an underground shift Numerical 7 Number of blasters Numerical 8 Number of managers Numerical 9 Labor organization methods Character type (20)

[0099] Table 5 below shows the disaster factor information table:

[0100] Table 5

[0101]

[0102]

[0103] Table 6 below shows the safety status information:

[0104] Table 6

[0105] serial number Data item name Type, Length Remark 1 Safety assessment level Character type (2) 2 Assessment time Date type Date: Year Month Day 3 Last accident time Date type Date: Year Month Day 4 Last accident type Character type (12) 5 The number of deaths in the last accident Numerical 6 Safe production days Numerical 7 Reporter Character type (10) 8 Contact information of the person who submitted the report Numerical 9 Reviewer Character type (10) 10 Reviewer's contact information Numerical

[0106] Table 7 below shows the mineral map information:

[0107] Table 7

[0108] serial number Data item name Type, Length Remark 1 Mine map number Numerical type (10) 2 Mine map name Character type (30) 3 Mineral map type Character type (20) 4 Attachment information Character type (50)

[0109] In this embodiment, in addition to the basic information database mentioned above, the monitoring database includes a safety environment monitoring information database, an underground worker information database, an electromechanical equipment monitoring information database, and an equipment information database. The safety monitoring information database consists of six types of data tables: real-time information, data acquisition status information, substation equipment information, alarm information, statistical information, and configuration information. Specifically:

[0110] The real-time information table is shown in Table 8 below:

[0111] Table 8

[0112] serial number Attribute Name Type, Length Remark 1 Coal Mine Number Character type (9) 2 Substation Number Character type (6) 3 Sensor number Character type (10) 4 Place Character type (80) 5 Sensor type Character type (5) 6 Monitoring values Numerical 7 time Date type Year Month Day Hour Minute Second

[0113] Table 9 below shows the data acquisition status information:

[0114] Table 9

[0115]

[0116]

[0117] Table 10 below shows the substation equipment information table:

[0118] Table 10

[0119] serial number Attribute Name Type, Length Remark 1 Coal Mine Number Character type (9) 2 Substation Number Character type (6) 3 Place Character type (40) 4 Substation Status Character type (4)

[0120] The alarm information table is shown in Table 11 below:

[0121] Table 11

[0122] serial number Attribute Name Type, Length Remark 1 Coal Mine Number Character type (9) 2 Substation Number Character type (6) 3 Sensor number Character type (10) 4 Sensor type Character type (5) 5 Alarm Types Character type (1) 6 abnormal power supply Character type (1) 7 Place Character type (80) 8 Monitoring values Numerical 9 Start time Date type Year Month Day Hour Minute Second 10 End time Date type Year Month Day Hour Minute Second 11 Duration Numerical 12 Maximum value Numerical 13 Maximum moment Date type Date: Year Month Day 14 Minimum value Numerical 15 Minimum time Date type 16 alarm value Numerical 17 Power outage value Numerical

[0123] The statistical information table is shown in Table 12 below:

[0124] Table 12

[0125]

[0126]

[0127] The configuration information table is shown in Table 13 below:

[0128] Table 13

[0129] serial number Attribute Name Type, Length Remark 1 username Character type (30) 2 Should we call the police? Character type (1) 3 Alarm Types Character type (400) 4 Delay time Numerical

[0130] Table 14 below shows the analog quantity configuration information table.

[0131] Table 14

[0132] serial number Attribute Name Type, Length Remark 1 Coal Mine Number Character type (9) 2 Substation Number Character type (6) 3 Sensor number Character type (10) 4 Sensor type Character type (5) 5 unit Character type (6) 6 Place Character type (80) 7 Power outage area Character type (10) 8 alarm value Numerical 9 Power outage value Numerical 10 Restored power value Numerical 11 Lower limit of measurement range Numerical 12 upper limit of measuring range Numerical

[0133] Table 15 below shows the switch configuration information:

[0134] Table 15

[0135] serial number Attribute Name Type, Length Remark 1 Coal Mine Number Character type (9) 2 Substation Number Character type (6) 3 Sensor number Character type (10) 5 Sensor type Character type (5) 6 Place Character type (80) 7 Power outage area Character type (10) 8 0 represents Character type (10) 9 1 represents Character type (10)

[0136] Table 16 below shows the cumulative quantity configuration information:

[0137] Table 16

[0138]

[0139]

[0140] The underground worker information database consists of three types of data tables: real-time / historical information, alarm information, and statistical information. Real-time and historical information include the mine real-time / historical information table and the personnel location real-time / historical information table, respectively. Specifically, Table 17 below shows the mine real-time / historical information table:

[0141] Table 17

[0142] serial number Attribute Name Type, Length Remark 1 Coal Mine Number Character type (9) 2 Coal Mine Name Character type (50) 2 main body Character type (9) 3 Number of people underground Numerical 4 Number of followers Numerical 5 Number of timeout exceptions Numerical 6 Number of people entering restricted areas Numerical 7 Overcrowding ratio Numerical 8 Number of people seeking help Numerical 9 Abnormal number of special personnel Numerical 10 System anomaly count Numerical 11 Update time Date type Year Month Day Hour Minute Second

[0143] Table 18 below shows the real-time / historical information on personnel location:

[0144] Table 18

[0145] serial number Attribute Name Type, Length Remark 1 Coal Mine Number Character type (9) 2 Coal Mine Name Character type (50) 3 Personnel Card Code Character type (5) 4 Name Character type (10) 5 post Character type (10) 6 Job or position Character type (20) 7 Team / Department Character type (30) 8 Train number Character type (2) 9 Well entry time Date type Year Month Day Hour Minute Second 10 Entry time to personnel management area Date type Year Month Day Hour Minute Second 11 Personnel Management Area Code Character type (4) 12 Personnel Management Area Name Character type (60) 13 Location monitoring substation code Character type (6) 14 Location monitoring substation name Character type (60) 15 Location monitoring substation installation location Character type (60) 16 Entry time of location monitoring substation Date type Year Month Day Hour Minute Second 17 Data generation time Date type Year Month Day Hour Minute Second 18 Is there any abnormal well discharge? Character type (1)

[0146] The alarm information table is shown in Table 19 below:

[0147] Table 19

[0148]

[0149]

[0150] The following table shows the statistical information:

[0151] Table 20

[0152] serial number Attribute Name Type, Length Remark 1 Coal Mine Number Character type (9) 2 Number of people entering the well Numerical 3 Number of people leaving the well Numerical 4 Number of mine leaders entering the mine Numerical 5 Number of mine leaders leaving the mine Numerical 6 Number of special personnel entering the well Numerical 7 Number of special personnel leaving the well Numerical 8 Number of timeout exceptions Numerical 9 Number of people entering restricted areas Numerical 10 Number of people seeking help Numerical 11 Abnormal number of special personnel Numerical 12 System anomaly count Numerical 13 Statistical time Date type Date

[0153] The electromechanical equipment monitoring information database consists of three types of data tables: equipment parameter definition information, extended information tables, and real-time / historical information of electromechanical equipment. Specifically, Table 21 shows the equipment parameter definition information table:

[0154] Table 21

[0155] serial number Attribute Name Type, Length Remark 1 Coal Mine Number Character type (9) 2 Monitoring parameter number Numerical 3 Subsystem Number Numerical 4 Home device ID Numerical 5 Monitoring parameter coding Character type (9) 6 Monitoring parameter name Character type (9) 7 Monitoring parameter code value Character type (9) 8 Monitoring parameter units Character type (9) 9 Define start time Date type 10 Define end time Date type 11 Last updated Date type Year Month Day Hour Minute Second

[0156] Table 22 below shows the analog quantity extended information table:

[0157] Table 22

[0158]

[0159]

[0160] Table 23 below shows the extended information table for switch quantities:

[0161] Table 23

[0162] serial number Attribute Name Type, Length Remark 1 Home device ID Numerical 2 Monitoring parameter number Numerical 3 Switch status number Numerical 4 Status Description Character type (9) 5 State value Numerical 6 Last updated Date type Year Month Day Hour Minute Second

[0163] Table 24 below shows the real-time / historical information table for monitoring electromechanical equipment:

[0164] Table 24

[0165] serial number Attribute Name Type, Length Remark 1 Coal Mine Number Character type (9) 2 Subsystem coding Numerical 3 Parameter encoding Numerical 4 Real-time value Numerical 5 Value Display Text Numerical 6 Data generation time Date type 7 Data collection time Date type 8 Maximum value during state Numerical 9 Last updated Date type Year Month Day Hour Minute Second

[0166] The equipment information database mainly includes data tables on the operating status of major equipment in the production process, data tables on the operating status of major equipment in coal mine mining faces, data tables on the power supply system, data tables on transportation monitoring, data tables on the ventilation fan monitoring system, data tables on the water supply and drainage system, data tables on the air compressor monitoring system, and data tables on the hoisting system.

[0167] The main equipment operation status data table for the production process mainly includes information on the status of major ventilation fans, belt conveyors, coal bunker levels, coal mining machines, scraper conveyors, transfer conveyors, crushers, etc., during coal mine production. Specifically, Table 25 below shows the main equipment operation status data table for the production process:

[0168] Table 25

[0169]

[0170]

[0171] Table 26 below shows the operating status data of the main equipment in the coal mine working face:

[0172] Table 26

[0173] serial number Attribute Name Type, Length Remark 1 coal mine (abbreviation) Character (10) 2 Coal Mine Number Character (9) 3 Coal mining machine operating status numerical values 4 Scraper conveyor operating status numerical values 5 Transfer machine operating status numerical values 6 Crusher operating status numerical values 7 Ventilation fan status numerical values 8 Belt running time numerical values 9 Belt status numerical values 10 Coal bunker coal level numerical values

[0174] The power supply system data table is shown in Table 27 below:

[0175] Table 27

[0176] serial number Attribute Name Type, Length Remark 1 coal mine (abbreviation) Character (10) 2 Coal Mine Number Character (9) 3 Voltage numerical values 4 Current numerical values 5 Fault numerical values 6 Start and stop numerical values 7 power numerical values 8 High voltage switch numerical values 9 Feeder switch numerical values

[0177] Table 28 below shows the data table of the transportation monitoring system:

[0178] Table 28:

[0179] serial number Attribute Name Type, Length Remark 1 coal mine (abbreviation) Character (10) 2 Coal Mine Number Character (9) 3 On / off status numerical values 4 Belt speed numerical values 5 Control modes (local, remote, linked) character 6 smoke character 7 coal pile character 8 Vertical tear character 9 veering off course character 10 temperature character 11 Underspeed and overspeed alarms character 12 underspeed and speeding stop character 13 atresia character 14 Startup failure character 15 Variable frequency drive failure character

[0180] Table 29 below shows the ventilation fan monitoring system:

[0181] Table 29

[0182] serial number Attribute Name Type, Length Remark 1 coal mine (abbreviation) Character (10) 2 Coal Mine Number Character (9) 3 Inlet static pressure numerical values 4 air volume numerical values 5 wind speed numerical values 6 efficiency numerical values 7 Atmospheric pressure numerical values 8 temperature numerical values

[0183] Table 30 below shows the water supply and drainage system data:

[0184] Table 30

[0185] serial number Attribute Name Type, Length Remark 1 coal mine (abbreviation) Character (10) 2 Coal Mine Number Character (9) 3 water level numerical values 4 On / off status numerical values 5 System voltage numerical values 6 Current numerical values 7 Winding temperature numerical values 8 bearing temperature numerical values

[0186] Table 31 below shows the data table of the air compressor monitoring system:

[0187] Table 31

[0188] serial number Attribute Name Type, Length Remark 1 coal mine (abbreviation) Character (10) 2 Coal Mine Number Character (9) 3 On / off status numerical values 4 Voltage numerical values 5 Current numerical values 6 Runtime date Date: Year Month Day 7 Power frequency numerical values 8 Active power numerical values 9 reactive power numerical values 10 Power factor numerical values 11 Active power numerical values 12 reactive power numerical values 13 bearing temperature numerical values 14 Stator temperature numerical values

[0189] Table 32 below shows the system data table:

[0190] Table 32

[0191]

[0192]

[0193] In this embodiment, a management business database is also set up, which includes a coal mine safety production inspection information database and a coal mine risk analysis database. Specifically, the coal mine safety production inspection information database mainly includes anomaly alert tables, inspection record tables, etc.

[0194] The following table, 33, shows the exception message table:

[0195] Table 33

[0196] serial number Attribute Name Type, Length Remark 1 Error number Value (10) 2 System Name Character (20) 3 Exception types Character (10) 4 Duration Value (10) 5 Prompt method Character (20)

[0197] The inspection record form is shown in Table 34 below:

[0198] Table 34

[0199] serial number Attribute Name Type, Length Remark 1 System error number Value (10) 2 Inspection Record Character (20) 3 Inspection results Character (10) 4 Inspection time date 5 System abnormal status Character (10)

[0200] The coal mine risk analysis database mainly includes data tables such as accident information, gas exceedance information, and hazard information. Additionally, the risk analysis data also originates from thematic databases, which have undergone data analysis to form thematic data. Table 35 below shows an accident information table:

[0201] Table 35

[0202] serial number Attribute Name Type, Length Remark 1 Accident Number Value (10) primary key 2 Accident Types Character (10) 3 Accident level Character (10) 4 Time of the accident date 5 Location of the accident Character (20) 6 Cause of accident Character (20) 7 Accident handling results Character (10)

[0203] The following table, 36, shows the gas over-limit information:

[0204] Table 36

[0205] serial number Attribute Name Type, Length Remark 1 Number of gas over-limit alarms numerical values 2 Cumulative duration of gas over-limit alarm numerical values 3 alarm maximum value numerical values 4 Excessive type Character (10) 5 Exceeding the limit location Character (20) 6 Over-limit alarm occurrence time date

[0206] Table 37 below shows the hazard information table:

[0207] Table 37

[0208]

[0209]

[0210] On the other hand, in the data acquisition and transmission software platform of this embodiment, the platform mainly realizes the data acquisition and connection of various business subsystems in the coal mine, ensuring that the required coal mine disaster monitoring data and major electromechanical equipment monitoring data can be collected, transmitted, and processed in accordance with relevant standards. Each mine adopts a dedicated line access method, with a bandwidth of 10M as needed, to realize the sharing and exchange of business data. Its network structure is as follows: Figure 2 As shown.

[0211] The data acquisition and transmission software platform enables bidirectional data interaction between the various business subsystems of Chahasu Coal Mine and the disaster early warning data center. The platform collects, transmits, and processes data according to the relevant standards defined by the platform, ensuring the timeliness, accuracy, and reliability of the data and guaranteeing the normal operation of the platform's various systems.

[0212] The data collected by the data acquisition and transmission software platform can be mainly divided into the following three categories:

[0213] (1) Data collection for coal mine disaster monitoring:

[0214] Coal mine disaster monitoring data includes gas disaster monitoring data (safety monitoring), roof monitoring data, personnel positioning monitoring data, microseismic monitoring data, bundled pipe monitoring data, hydrological monitoring data, dust monitoring data, etc.

[0215] (2) Data collection for monitoring major electromechanical equipment:

[0216] The data on major mechanical and electrical equipment includes monitoring data for the main ventilation fan, auxiliary shaft hoist, main coal flow belt conveyor, air compressor, and power monitoring.

[0217] like Figure 3The diagram illustrates the data acquisition and transmission interface. The data acquisition and transmission software platform consists of a file generator, a file uploader, a file parser, and a data importer. The file generator, provided by each business subsystem, generates data files and related attachments according to the protocol requirements. The file uploader uploads the data files and attachments. The file parser and data importer are deployed on the parsing server, performing functions such as parsing, storing, backing up, and cleaning the uploaded files. The data importer imports and enters the basic configuration data and spatial data required by the entire system.

[0218] In this embodiment, the data exchange file format is defined by the file generator, and the data exchange file conventions require:

[0219] (1) All data exchange files are plain text files in UTF-8 encoding format with the extension txt.

[0220] (2) All data exchange files in this agreement should be generated with the extension .tmp first, and then changed to the formal .txt extension after the data exchange files are generated. This method ensures that the content of the transmitted data exchange files is complete.

[0221] (3) The directory for storing data exchange files is generated by the file generator as required, and the data transfer program is ensured to have access permissions to the folder.

[0222] (4) The data exchange file is generated by the file generator and cleaned up by the file uploader after successful transmission. The file uploader is responsible for data cleanup.

[0223] (5) When generating a data exchange file, if no new data is generated for this item, the file should still be generated (the number of data records in the data header will be 0) to indicate that the file generation module is running normally.

[0224] The file naming rules for data exchange filename format are as follows:

[0225] Coal mine code + business data code + data type identifier + yyyyMMddHHmmss.txt

[0226] The coal mine code is a 4-string string, the business data code is a 4-string string, and yyyyMMddHHmmss represents the time the file was generated. Data type identifiers are used to distinguish different data categories. For detailed definitions, please refer to the "Qinghai Coal Mine Safety Monitoring Bureau Accident Risk Analysis Platform Exchange Protocol".

[0227] For the content of data exchange files, all data exchange files consist of two parts: a data header and a data body. The data header is located on the first line of the entire document (the line ends with a newline character [\r\n]), and the data body begins from the second line.

[0228] (1) Data header format

[0229] The data header is located on the first line of the document, and its content is shown in Table 38 below:

[0230] Table 38

[0231] Serial Number Data Items necessity type Remark 1 Coal Mine Code must Conventional value 4-character string 2 Business data coding must Conventional value 4-character string 3 Data type identifier must String Distinguish between different data categories 4 Number of data records must number The number of records in the data body 5 Generation time must Full time The file's creation time is in the format yyyy-MM-dd HH:mm:ss

[0232] (2) Data format

[0233] The data body consists of multiple data records, each occupying one line. Each data record consists of multiple fields (defined in each data exchange file). The constraints on the data body are as follows:

[0234] Each data record occupies one line and ends with a newline character (\r\n). Each line corresponds to a unique record. Newline characters (\r\n) are not allowed in the data body.

[0235] Numbers are uniformly formatted as half-width characters in English mode.

[0236] Each data record contains multiple fields, separated by semicolons (;). It is essential to ensure that the number of semicolons (;) in each data record row is one less than the number of fields.

[0237] The semicolon ";" is not allowed in the field values ​​of record fields (unless otherwise specified). If you must use this separator field, please use the semicolon (;) in Chinese input mode instead.

[0238] The date and time format is uniformly defined as "yyyy-MM-dd HH:mm:ss" (unless otherwise specified). If the month, day, hour, minute, or second is less than two digits, add "0" in front. The total character length is 19 characters, such as "2013-06-05 13:01:02".

[0239] The data acquisition and transmission software platform categorizes information, and the categorized data is stored in corresponding database tables. All data is divided into personnel data, equipment data, environmental data, safety management data, production management data, and comprehensive management data.

[0240] Personnel data includes:

[0241] Personnel Basic Information: Name, ID Number, Gender, Date of Birth, Blood Type, Education, Marital Status, Personal Contact Number, Emergency Contact Number, Home Address, Position, Job Type or Title, Team / Department, Main Work Location, Job Certificate Name, Job Certificate Number, Job Certificate Validity Period, Current Location (Location after entering the mine / Location after exiting the mine), Time of Entering the Mine, Time of Exiting the Mine, Required Location (Specific Personnel).

[0242] Personnel statistics: Total number of registered personnel in the mine, number of personnel approved to go down the mine, number of personnel currently working underground, number of gas inspectors underground / total number, number of safety inspectors underground / total number, number of leaders on duty underground / total number, number of blasters underground / total number, number of management personnel underground / total number.

[0243] Abnormal personnel situations: information on personnel entering restricted areas, information on personnel exceeding time limits, information on overcrowding in mines, and abnormal information on specific personnel.

[0244] Equipment information includes:

[0245] Coal mining equipment: basic information on coal mining machines, scraper conveyors, transfer conveyors, and crushers; motor monitoring information and reducer monitoring information; basic information on hydraulic supports and support monitoring information; basic information on emulsion pumps, emulsion monitoring information, gearbox monitoring information, crankcase monitoring information, and cooling system monitoring information.

[0246] Tunneling equipment: basic information about the tunneling machine, motor monitoring information, and reducer monitoring information.

[0247] Electromechanical equipment: Basic information on compressed air equipment, compressed air compressor monitoring information, motor monitoring information, air tank monitoring information, and water supply pump; basic information on lifting equipment, motor monitoring information, drum monitoring information, reducer monitoring information, cooling system monitoring information, hydraulic station monitoring information, and lubrication pump station monitoring information; basic information on drainage equipment, motor monitoring information, and water pump monitoring information; substation equipment information, power supply switch monitoring information, and mobile substation monitoring information.

[0248] Transportation equipment: Basic information on belt conveyors, motor monitoring information, reducer monitoring information, and belt monitoring information; basic information on electric locomotive transportation equipment; basic information on rubber-tired vehicle transportation equipment.

[0249] Ventilation equipment: Basic equipment information, monitoring information of main (auxiliary) ventilation fans

[0250] Communication equipment: Dispatch communication equipment information, underground broadcast information, underground wireless communication equipment information

[0251] Personnel positioning equipment: personnel positioning system information, personnel positioning substation information

[0252] Safety monitoring equipment: Safety monitoring system information; sensor information; analog quantity, digital quantity, and cumulative quantity type information; sensor status information.

[0253] Emergency escape equipment: information on mobile life-saving capsules.

[0254] Image surveillance equipment: equipment specifications, manufacturer, installation location, standard resolution (dpi), access method, access address, etc.

[0255] Environmental information includes:

[0256] Water: Types of water hazards, hydrogeological conditions, normal water inflow in the mine, maximum water inflow in the mine, water level in the observation well, and water level in the water tank.

[0257] Fire: Spontaneous ignition rating, shortest ignition period, main fire prevention and extinguishing measures, temperature, carbon monoxide concentration.

[0258] Gas: Gas level, relative gas emission, absolute gas emission, gas monitoring information.

[0259] High temperature (geothermal): High temperature mine, mining depth, tunnel temperature.

[0260] Roof: Geological conditions, rockburst level, and roof pressure monitoring information.

[0261] Coal dust: Coal dust explosion index, coal dust monitoring information.

[0262] Security management information includes:

[0263] Hazard information: Hazard type, hazard description, hazard location, hazard specialty, hazard level, rectification method, rectification time, rectification status, re-inspection status, hazard condition.

[0264] Accident information: accident type, accident description, accident location, level, number of casualties, cause of accident, handling process, handling results, and handling decisions.

[0265] Hazard information: the specialty of the hazard, the type of hazard, the content of the hazard, and the location where the hazard was discovered.

[0266] Production management information includes:

[0267] Production technology information: mining information, mine map information, shaft information, and coal seam information.

[0268] Production status: output, progress, loading, sales.

[0269] General management information includes:

[0270] Basic information about a coal mine includes: mine name, original mine name, mine manager, mine manager's mobile phone number, mine office phone number, dispatch room phone number, administrative division (province, municipality, city, county), detailed address, regulatory department, enterprise type, affiliation, postal code, geological reserves, design capacity, mine design time, development method, mineable coal seam, main shaft coordinates, auxiliary shaft coordinates, minefield boundary (coordinates), minefield area, recoverable reserves, approved capacity, commissioning time, mining level, currently mined coal seam, historical highest flood level, main shaft elevation, auxiliary shaft elevation, number of shafts, total required ventilation volume, total return air volume, ground elevation, ventilation method, total intake air volume, mining depth, gas level, relative gas emission, absolute gas emission, and mine production status.

[0271] Licenses and permits: Mining licenses (mining permit, safety production permit, business license); personnel licenses (mine manager safety qualification certificate, safety qualification certificate, special operations personnel operation qualification certificate).

[0272] Location information: number, name, category (mine level, mining area, working face, roadway, etc.).

[0273] Organizational information: Organization name, organization level.

[0274] Schedule information: Schedule name, start time, end time.

[0275] Job information: blasting worker, coal mining machine operator, main hoist operator, mining electrician, gas inspector, gas drainage worker, safety instrument monitoring worker, safety inspector, gas outburst prevention worker, underground drilling worker, etc.

[0276] Job positions: Mine Manager, Deputy Mine Manager, Chief Engineer, Section Chief, Deputy Section Chief, Section / Team Leader, Deputy Section / Team Leader, Technician.

[0277] In the file uploader of the data acquisition and transmission software platform in this embodiment, the data files generated by the aforementioned file generator, as well as the attachment files of some data, are stored in a designated directory called the upload directory. The data files use the .tmp extension, and the official files, which are renamed to the .txt extension after the files are closed, are stored in the designated directory.

[0278] The upload directory has four levels of subdirectories. The first level is UploadSAWS, the second level is the mine code, the third level is the business data system code, and the fourth level is the data category (Realtime is the real-time data directory, History is the historical data directory (including basic data and definition information, etc.), Attachment is the attachment file directory, and Backup is the backup file directory). For example, the data file directory of subsystem 1001 with mine code 0101 is shown in Table 39 below:

[0279] Table 39

[0280] type Upload Data Directory Real-time data upload directory D:\UploadSAWS\0101\1001\Realtime Historical data upload directory D:\UploadSAWS\0101\1001\History Attachment Upload Directory D:\UploadSAWS\0101\1001\Attachment

[0281] The file uploader needs to implement system configuration and upload task parameter configuration functions, manual and automatic upload functions, file backup and cleanup functions, and logging functions (including operation logs, upload logs, FTP operation logs, and cleanup logs). The functional architecture diagram of the file uploader is as follows: Figure 4 As shown, the file uploader scans the upload directory at configured intervals (default 5 seconds). If a file with a .txt extension is generated, it uses multi-threading to process the data files from each mine in parallel. It iterates through all business system directories sequentially, using an FTP / TCP interface to upload files in the Realtime directory first, then the Attachment directory, and finally the History directory. The uploaded file directories remain consistent with the original directories. During file upload, filenames with the .tmp extension are used, and after upload, the filenames are renamed to the official filenames. After successful upload, the files are moved to a backup directory (e.g., D:\UploadSAWS\0101\Backup), and a file upload verification record is generated, recording the uploaded filename, file size, and upload time.

[0282] The file uploader can also be configured to clean up backup directory files. The file cleanup function is enabled by default, but can be disabled in special circumstances (such as when retrieving historical files). The file cleanup function automatically cleans up backup files older than a specified time period (default 3 months).

[0283] In the file parser of the data acquisition and transmission software platform, the file parser performs functions such as parsing, storing, backing up, and cleaning uploaded files. The file parser scans the local upload directory at configured intervals (default 1 second). If a file with a .txt extension is generated, it uses a multi-threaded approach to process the data files of various business systems in the mine in parallel. It sequentially traverses all business system directories and performs data verification according to data exchange specifications, checking whether the filename, file header, and file fields conform to the specifications. If an attachment exists but the corresponding attachment cannot be found, the verification is considered a failure, and the failed files are stored in the CheckError directory. After successful verification, the data is stored in the database, processing real-time data first, followed by historical data files. Table 40 below shows the local parsing file directory list of a certain subsystem in a certain mine:

[0284] Table 40

[0285] type Local data file directory Real-time data catalog D:\UploadSAWS\0101\1001\Realtime Historical Data Catalog D:\UploadSAWS\0101\1001\History Appendix Table of Contents D:\UploadSAWS\0101\1001\Attachment Backup file directory D:\UploadSAWS\0101\1001\Backup Error file directory D:\UploadSAWS\0101\1001\CheckError

[0286] The data ingestion module has a data caching function. If there are many data records, the batch ingestion interface is used for ingestion; if there are few data records, the INSERT statement can be used directly. The interval between each ingestion is configurable (default 50 milliseconds). When the number of records in the cache queue is greater than 10 (the specific number of records can be adjusted according to ingestion performance), batch ingestion is used.

[0287] After the file parsing is complete, the data file is moved to the backup directory, and a file parsing verification record is generated, which records the file name, the number of file records, the file verification result, and the file processing time.

[0288] The file parser also needs to support the function of cleaning up backup directory files, automatically cleaning up backup files older than a configured time period (default 12 months).

[0289] The attachments and drawing files in the Attachment directory, as well as the verification error files in the CheckError directory, including the file parsing and verification record files, need to be synchronized to the Web server through the "drawing file synchronization function" so that Web terminals can easily view the drawing files and file parsing and verification records.

[0290] Example 2

[0291] This embodiment describes the specific design and implementation of the system proposed in Embodiment 1.

[0292] Taking the data collected by the gas monitoring system as an example, the data collected by the gas monitoring system includes equipment definition information, real-time data, real-time alarm records, real-time power outage records, analog quantity status change records, analog quantity statistical records, switch quantity status change records, switch quantity operation records, alarm and power outage handling measures, etc. The data specifications fully comply with the standard data protocol stipulated by the system.

[0293] Plug-in programming allows for easy replacement of components in one or more processing flows, readily adapting to different business processes within a given flow. This eliminates the need for software recompilation, facilitates early software release and deployment, and allows for the development of customized functionalities for the same business flow but different processes based on subsequent on-site needs. This improves development speed, software compatibility, and flexibility, making it an excellent component-based programming methodology. In plug-in development, the interface defines the interaction principles between the plug-in management program and the plug-ins, without concerning itself with the specific functional implementation of the plug-ins. For example, when the plug-in management program needs to load a plug-in, it calls the plug-in's initialization interface function according to the principles. This function is implemented by the plug-in itself; how it initializes is the plug-in's responsibility. Since different plug-ins implement different functionalities, their initialization actions may also differ, but this is transparent to the plug-in management program, which only needs to ensure that the specific plug-in interface is called at specific times.

[0294] The interface class for the subsystem data acquisition plugin based on the standard protocol provided by the project is named `IDataAdapter`. This interface is the foundation for all adapter plugins, and the adapter plugin manager manages them through this interface. The adapter program framework can operate the adapter modules of each subsystem and display their interfaces by manipulating this interface. Its type structure is as follows: Figure 5 As shown.

[0295] The specific meanings of the interface's properties and methods are required as shown in Table 41 below:

[0296] Table 41

[0297] Serial Number Properties / Methods Standard Description Remark 1 Enable Get plugin running status 2 RunState Configure whether the current plugin is enabled / disabled. 3 Close Off function Plugin data collection function disabled 4 Open Open function Start and continuously collect data 5 ShowConfigWnd Display configuration window Plugin configuration interface in the host environment 6 Suspend Suspend function Suspend the current plugin

[0298] Since the system integration involves multiple subsystems and a large amount of plugin data, a plugin manager is provided to facilitate the management of these plugins. This manager is used to uniformly load, start, update, and stop the use of these plugins. It is integrated into the module of the data acquisition software.

[0299] The design and implementation logic of the data acquisition plugin for the security monitoring system is as follows: Figure 6 As shown, its final implementation class, DataAdapter, does not directly inherit from the IDataAdapter interface, but rather extends the interface further.

[0300] The IConfigWnd interface defines the display and operations related to the user interface, providing users with the ability to automatically add and uninstall this plugin.

[0301] The `ISerializeXmlX` interface is used to save XML-formatted data to a file or database. In the data acquisition module, when users load and configure plugins, the relevant configuration information is stored in XML format. By inheriting this interface, `DataAdapter` can define and handle the saving and reading of configuration information.

[0302] The IDevice interface is used to abstractly define plug-in devices. In system design, all objects, including hardware devices and virtual abstract objects, share some common attributes or actions, such as device name, device on / off, etc. It is the interface that specifies the specific actions and methods that plug-ins possess.

[0303] The DABase abstract class is the base class for generating data in the data collection module. It provides the default operation mode for IDevice actions, and the defined properties and methods in this class can be used directly when they are not overridden or remain unchanged in subsequent implementations.

[0304] The `DANormalTemplet` abstract class provides a general data adaptation template suitable for subsystems that read data from a database and have real-time, historical, monitoring, and downlink data. Clearly, the data acquisition plugin in the KJ90N monitoring system should inherit from this class.

[0305] The DataAdapter class: This class performs the final data reading and message queue generation for the security monitoring system, and then transmits it to the server. Its main function is accomplished by its own variable: a DataManager object instance. The structure of the DataManager class is as follows... Figure 7 As shown.

[0306] This category also specifies and implements the standard data content that the security monitoring system needs to acquire, and includes the following functions:

[0307] GetDIDA: Retrieves analog quantity definition information;

[0308] GetDIDD: Retrieves switch quantity definition information;

[0309] GetDICR: Retrieves control relationship definition information;

[0310] GetReal: Retrieves real-time data information;

[0311] GetRealAlarm: Gets real-time alarm information;

[0312] GetRealCut: Gets real-time power outage information;

[0313] GetFiveStc: Retrieves minute-by-minute statistics;

[0314] GetAStatusRecord: Retrieves the record of analog quantity status changes;

[0315] GetDStatusRecord: Retrieves records of status changes of switch inputs;

[0316] GetDRunRecord: Retrieves the running record of the switch quantity;

[0317] GetFBRecord: Retrieves power supply record information;

[0318] IsWarring: Determines whether an alarm has been triggered and returns the corresponding alarm status code;

[0319] IsCut: Determines whether there is a power outage and returns the corresponding power outage status code;

[0320] GetStatus: Changes the status and returns the corresponding status code;

[0321] GetTypeID: Converts the measurement point type encoding.

[0322] In this category, status acquisition and type acquisition both involve converting the data types in the security monitoring system into standard types and status codes recognized by the protocol, according to the provisions in the standard protocol.

[0323] Additionally, this embodiment also proposes a specific method for designing and implementing a flat file data source. A flat file data source subsystem generally refers to storing relevant data in flat files, or in a database server, but without providing a direct database service access mechanism for security or network restrictions. Instead, it provides the data to third-party integrators in a read-only flat file format. The provided flat file can be a standard-compliant data file, or it can meet the integrator's requirements. The integrator then converts the flat file into a standard-compliant data file, which is then read and uploaded to the message sequence by the acquisition module.

[0324] The data acquisition design and implementation of each subsystem based on the planar file data source are basically the same. The following is a brief explanation and introduction using the personnel positioning system as an example. The personnel positioning system is used for locating, recording and querying the trajectory of personnel going down the mine, attendance tracking, and shift auditing. In actual field testing, it was a product from a third-party manufacturer. The manufacturer provided data integration services based on the file data source, according to the standard data protocol proposed for the project.

[0325] The implementation of the personnel positioning system's data acquisition module plugin is basically the same as that of the security monitoring system. It also has a DataAdapter class, but its inheritance relationship differs somewhat from that in the security monitoring system. It directly inherits from DABase, rather than from the abstract class DANormalTemplet. Figure 8 As shown. This is because when dealing with file-based data sources, no database-related operations are required.

[0326] The DataAdapter class also utilizes the DataManager class to perform data acquisition from file data sources. It reads existing third-party data format files and generates standard data file formats from them using the DataManager class. The structure of the DataManager class is as follows: Figure 9 As shown. Its main functions are:

[0327] GetAreasInfo: Retrieves information about the area where personnel are located underground in a coal mine;

[0328] GetClassSetInfo: Retrieves class information;

[0329] GetDepartMentInfo: Retrieves personnel department information;

[0330] GetJopPositionInfo: Retrieves personnel job information;

[0331] GetWorkTypeInfo: Retrieves employee type information;

[0332] GetProTitleInfo: Retrieves personnel professional title information;

[0333] GetStaffInfo: Retrieves basic staff information;

[0334] GetRealDataRY: Retrieves information about personnel underground and their location;

[0335] GetMonthCheckRecord: Retrieves employee attendance information;

[0336] GetRealDeviceStatus: Retrieves real-time device status information.

[0337] This embodiment also proposes a specific implementation method for the design and implementation of the OPC class. Multiple subsystems of the coal mine production control class are based on OPC class data sources. These subsystems themselves, or their integrated configuration system, provide an OPCServer to provide system data acquisition services to third parties. During integration, the acquisition module directly obtains real-time system data, equipment status, etc., from the OPC Server and converts them into a standard format for use in message sequences. Due to the large number of integrated subsystems, the main ventilation fan subsystem is used as an example for explanation.

[0338] The main ventilation fan online monitoring system monitors the operating status of the main ventilation fan in real time, including parameters such as motor voltage, motor current, motor power supply frequency, fan static pressure, air volume, air speed, motor stator temperature, motor bearing temperature, fan ambient temperature and humidity, and fan horizontal and vertical vibration. All data are transmitted to the central station server in the monitoring room in real time, and it has real-time alarm, historical data query and remote information sharing functions.

[0339] The design and implementation logic of the main ventilation fan system's data acquisition module is as follows: Figure 10 As shown, it also inherits from the DABase base class, as well as the IDataAdapter, IConfigWnd, ISerializeXmlX, and IDevice interfaces. Compared to other subsystems, its inheritance implementation is relatively simple because during system data collection, it only needs to directly connect to and read tag data from the OPC service published by the system. All OPC class subsystems can use this class for data collection and uploading, exhibiting excellent compatibility.

[0340] In this implementation class, the GetDataType function is used to obtain the data type, and the result it returns is the code of several types specified in the standard; the GetQuality function is used to obtain the data quality of each tag point; the GetDataFile function is used to obtain data from the OPC class subsystem (by calling the GetOPC function), and generate a file, which is then read by the upload module and uploaded to the message sequence.

[0341] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A coal mine disaster monitoring data acquisition system, characterized in that: The system comprises at least a data center and a data acquisition and transmission software platform, wherein the data center comprises a data resource layer, a data processing layer, a special data layer, a management layer and a service layer, the data acquisition and transmission software platform comprises a file generator, a file uploader, a file parser and a data importer, and data information acquired by the data acquisition and transmission software platform is transmitted to a database of the data center; The data center further comprises a plurality of databases, which are classified into a basic information database, a monitoring and control database and a business database, and are respectively used for storing corresponding information; In the data acquisition and transmission software platform, a data exchange file format is defined in the file generator, data exchange is performed according to the defined data exchange file format, information classification is performed on data information, data files and attachments are generated according to protocols, and the data files are stored in a specified upload directory; the file uploader scans the upload directory, processes data files of each mine in a multi-threaded manner, and uploads the upload directory to the file parser; the file parser parses, stores, backs up and cleans the uploaded files; the uploaded attachments are synchronized to a Web server, and other data is manually entered through the data importer; The data acquisition and transmission software platform further designs different acquisition modes for different categories of data to be acquired, and acquires data of different categories through the corresponding acquisition modes.

2. The coal mine disaster monitoring data acquisition system according to claim 1, characterized in that: The data resource layer stores basic data and monitoring data acquired from a mine end, shared data acquired from a third party, log data automatically generated by the data center, and result data generated by an application system; The data processing layer stores data to a data special library through data extraction, data conversion, data cleaning and data loading by using original data of the mine end and result data generated by cloud applications; The special data layer extracts special data from different dimensions after processing by the data processing layer, and stores the special data in the special data layer; The management layer sets general management indicators and management methods of data; The service layer is used for providing a data service interface to the outside for calling and interaction of cloud applications and systems; Information resource management and information security guarantee management are further set, the data resource management provides an auxiliary role for data resource planning, and the information security guarantee management provides security guarantee.

3. The coal mine disaster monitoring data acquisition system according to claim 1, characterized in that: The basic information database refers to a coal mine basic information database, which at least comprises basic information, license information, mining information, personnel information, disaster factor information, safety status information and mine map information, wherein a corresponding information table is established for each type of information, attribute name, data type and length, and related note information are specified in each data table; The monitoring and control database comprises a safety environment monitoring information library, an underground operation personnel information library, a mechanical and electrical equipment monitoring information library and a device information library, wherein the safety monitoring information library comprises real-time information, data acquisition state information, substation device information, alarm information, statistical information and configuration information, the configuration information is classified into analog quantity configuration information, switch quantity configuration information and cumulative quantity configuration information, and a corresponding information table is also established; The downhole operation personnel information base includes real-time / historical information, alarm information and statistical information, wherein the real-time information and the historical information respectively include mine real-time / historical information and personnel position real-time / historical information, and corresponding information tables are also established; The electromechanical equipment monitoring information base includes equipment parameter definition information, extension information and electromechanical equipment real-time / historical information, wherein the extension information includes analog quantity extension information and switch quantity extension information, and corresponding information tables are also established; The equipment information base includes production process main equipment running state data, coal mine mining working face main equipment running state data, power supply system data, transportation monitoring, ventilation machine monitoring system data, water supply and drainage system data, compressed air machine monitoring data and hoisting system data, and corresponding information tables are also established; The management business database includes a coal mine safety production inspection information database and a coal mine risk analysis database, the coal mine safety production inspection information database includes abnormal prompt information and inspection record information, and the coal mine risk analysis database includes accident information, gas overrun information and hidden danger information, and corresponding information tables are also established.

4. The coal mine disaster monitoring data collection system of claim 1, wherein: In the data acquisition and transmission software platform, the obtained basic data and business data are processed by a file generator to obtain data files and attachments, and the data files are packaged according to the set format; a file uploader uploads the data files and attachments packaged by the file generator to a file parser, and the file parser completes the parsing, warehousing, backup and cleaning of the uploaded files.

5. The coal mine disaster monitoring data acquisition system according to claim 4, characterized in that: The file generator defines the data exchange file format, and the format requirements include: (1) all data exchange files are pure text files in UTF-8 encoding format, and the extension name is txt; (2) in this protocol, all data exchange files are first generated with tmp as the extension name, and then changed to the formal txt extension name after the data exchange file is generated; (3) the storage directory of the data exchange file is generated by the file generator according to the requirements, and the data transmission program has access permission to the folder; (4) the data exchange file is generated by the file generator and cleaned by the file uploader after correct transmission, and the data cleaning is responsible by the file uploader; (5) when generating the data exchange file, even if there is no new data generated, the file is also generated, and the data record number of the data header is 0; The file naming rules of the data exchange file name format are as follows: Coal mine code+business data code+data type identifier+yyyyMMddHHmmss.txt Wherein, the coal mine code is a preset length string, the business data code is a preset length string, yyyyMMddHHmmss is the time when the file is generated; the data type identifier is used to distinguish different data categories; For the data exchange file content, all the data exchange file content includes data header and data body, the data header is located in the first line of the entire document; the second line is the data body, wherein the data header includes coal mine code, business data code, data type identification and generation time; the data body is composed of multiple data records, each data record occupies a line, and each data record is composed of multiple fields, and the constraints of the data body are as follows: Each data record occupies a line and ends with a carriage return line feed (\r\n), and each line corresponds to a unique record; no carriage return line feed is allowed in each data record; The digital format is uniformly specified as the half-angle form in English state; each data record contains multiple fields, and the fields are separated by English half-angle ";” to ensure that the number of semicolons ";” in each data record line is one less than the number of fields; No English half-angle ";” is allowed in the record field domain value, and if the separator field must be used, the Chinese input state semicolon ";” is used instead; The date and time format is uniformly specified as "yyyy-MM-dd HH:mm:ss”, and if the month, day, hour, minute, and second are less than two digits, "0” is added in front; In the data acquisition and transmission software platform, the information is classified, and the classified data information is stored in the data table of the corresponding database, wherein all the data is classified into personnel data, equipment data, environmental data, safety management data, production management data and comprehensive management data; For the data file generated by the file generator and the attachment file of part of the data, the data file uses the tmp extension, and after closing the file, the formal file with the txt extension is renamed and stored in the specified directory, which is called the upload directory; the upload directory has four levels of subdirectories, the first level directory is UploadSAWS, the second level directory is mine code, the third level directory is business data system code, and the fourth level directory is data classification, wherein Realtime is the real-time data directory, History is the historical data directory, Attachment is the attachment file directory, and Backup is the backup file directory.

6. The coal mine disaster monitoring data acquisition system according to claim 5, characterized in that: The file uploader scans the upload directory at the configured interval, and if there is a txt suffix file, it uses a multi-threaded way to process the data files of each mine in parallel; all business system directories are traversed in order, and the Realtime directory file is uploaded first, then the Attachment directory file is uploaded, and finally the History directory file is uploaded, and the file directory after uploading remains the same as the original directory; During the file uploading process, the file name with the tmp suffix is used, and after uploading, it is renamed to the formal file name, and after the file uploading is successful, the file is moved to the backup directory, and a file uploading verification record is generated, recording the file name, file size and uploading time; The file uploader also configures whether to clean up the backup directory file function, and the file cleaning function is enabled by default; the file cleaning function automatically cleans up the backup files before the configured time period.

7. The coal mine disaster monitoring data collection system of claim 6, wherein: The file parser scans the local upload directory at configured intervals. If a file with the .txt extension is generated, it uses a multi-threaded approach to process the data files of various business systems in the mine in parallel. It traverses all business system directories in sequence and performs data verification according to the data exchange specifications. It verifies whether the file name, file header, and file fields conform to the specifications. If the data has an attachment file but the corresponding attachment cannot be found, the verification is considered to have failed. Files that fail verification are stored in the CheckError directory. After successful verification, the data is processed for database entry. Real-time data is processed first, followed by historical data files. The file parser's data entry module has a data caching function. When the number of records in the cache queue is greater than the record quantity threshold, the batch data entry interface is used to perform data entry. When the number of records in the cache queue is less than the record quantity threshold, the insert statement is used directly to perform data entry. The data entry interval is configured according to a preset time. After the file parsing is complete, the data file is moved to the backup directory, and a file parsing verification record is generated, which records the file name, the number of file records, the file verification result, and the file processing time. The file parser also supports the function of cleaning up backup directory files, automatically cleaning up backup files older than a configured time period; The attachments and drawing files in the Attachment directory, as well as the check error files in the CheckError directory, including the file parsing check record files, are synchronized to the web server through the "drawing synchronization function".

8. The coal mine disaster monitoring data collection system of claim 1, wherein: The system also includes data acquisition plugins for connecting various data subsystems, and a plugin manager for uniformly loading, starting, updating, and stopping various data acquisition plugins. The plugin manager is integrated into the data acquisition and transmission software platform. The final implementation class, DataAdapter, inherits the IDataAdapter interface through an extended interface. The DataAdapter class first inherits the general data adaptation template defined by the abstract class DANormalTemplet, then inherits the base class for generating data in the acquisition module defined by the abstract class DABase, and then connects to the IDataAdapter interface. The IDataAdapter interface is synchronously connected to the IConfigWnd interface, the ISerializeXmlX interface, and the IDevice interface. The IConfigWnd interface defines the display and operation related to the user interface, the ISerializeXmlX interface is used to save XML format data to a file or database, and the IDevice interface is used to abstract the definition of the data acquisition plugin. The DataAdapter class performs the final data reading and message queue generation, and transmits the data to the server itself. The DataAdapter class contains a DataManager object instance, which includes several functions: GetDIDA (analog quantity definition information), GetDIDD (digital quantity definition information), GetDICR (control relationship definition information), GetReal (real-time data information), GetRealAlarm (real-time alarm information), GetRealCut (real-time power outage information), GetFiveStc (minute statistics information), GetAStatusRecord (analog quantity status change record), GetDStatusRecord (digital quantity status change record), GetDRunRecord (digital quantity operation record), GetFBRecord (power supply record information), IsWarring (alarm detection), IsCut (power outage detection), GetStatus (status conversion), and GetTypeID (measuring point type encoding conversion).

9. The coal mine disaster monitoring data collection system of claim 1, wherein: The system also includes a flat file data source subsystem. The flat file data source subsystem refers to storing relevant data in flat files or in a database server, but does not provide a direct database service access mechanism. Instead, it provides the data to third-party integrators in the same read-only flat file manner. The integrators then convert the flat files into standard data files, and the acquisition module reads the data and uploads it to the message sequence. The system also includes an OPC-type data source subsystem. Multiple subsystems of the coal mine production control class collect data based on the OPC-type data source system. The multiple subsystems of the coal mine production control class or the integrated configuration system provide an OPC Server to provide system data acquisition services to third parties. During integration, the system directly obtains real-time system data and equipment status information from the OPC Server through the OPC-type data source subsystem and converts it into a standard format for use in message sequences.

Images