Data storage method, device and equipment for fully mechanized working face

Abstract

The application discloses a data storage method, device and equipment for a fully-mechanized coal mining face, relates to the technical field of coal mining, and can solve the problem of low data use efficiency of various business systems of the fully-mechanized coal mining face. The method comprises the following steps: acquiring equipment data of the fully-mechanized coal mining face, and converting the equipment data into object model data with unified format; storing the object model data in an original database according to a preset table division strategy; and cleaning up object model data with a storage duration greater than a preset first duration in the original database.

Description

Technical Field

[0001] This application relates to the field of coal mining technology, and in particular to a data storage method, apparatus and equipment for fully mechanized mining faces. Background Technology

[0002] The fully mechanized longwall face is a coal mining face equipped with comprehensive mechanized equipment underground in a coal mine. In order to ensure the efficient and safe operation of underground equipment, various business systems need to process the data generated by the underground equipment.

[0003] In the existing design, the equipment in the longwall mining face is diverse and numerous. Each piece of equipment generates a large amount of data with inconsistent formats. Each business system independently accesses the data generated by the equipment and uses it according to its own usage method. As a result, each business system operates independently in data processing, which greatly wastes system resources and leads to low data utilization efficiency. Summary of the Invention

[0004] In view of this, this application provides a data storage method, apparatus and equipment for fully mechanized mining faces, relating to the field of coal mining technology, which can solve the problem of low data utilization efficiency in various business systems of fully mechanized mining faces.

[0005] According to one aspect of this application, a data storage method for a fully mechanized mining face is provided, the method comprising:

[0006] Acquire equipment data from the fully mechanized mining face and convert the equipment data into uniformly formatted physical model data;

[0007] The object model data is stored in the original database according to a preset table partitioning strategy;

[0008] Clean up the object model data stored in the original database that has a duration longer than a preset first duration.

[0009] According to another aspect of this application, a data storage device for a fully mechanized mining face is provided, the device comprising:

[0010] The acquisition module is used to acquire equipment data from the fully mechanized mining face and convert the equipment data into uniformly formatted physical model data.

[0011] The storage module is used to store the object model data in the original database according to a preset table partitioning strategy;

[0012] The cleaning module is used to clean up the object model data stored in the original database that has a duration longer than a preset first duration.

[0013] According to another aspect of this application, a non-volatile readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the above-described data storage method for a fully mechanized mining face.

[0014] According to another aspect of this application, a computer device is provided, including a non-volatile readable storage medium, a processor, and a computer program stored on the non-volatile readable storage medium and executable on the processor, wherein the processor executes the program to implement the above-described data storage method for a fully mechanized mining face.

[0015] By utilizing the above technical solution, this application discloses a data storage method, apparatus, and equipment for a fully mechanized mining face. It first acquires equipment data from the fully mechanized mining face and converts this data into uniformly formatted object model data. The object model data is then stored in the original database according to a preset table partitioning strategy. Finally, object model data in the original database with a storage duration exceeding a preset first duration is cleaned. Through the technical solution in this application, using uniformly formatted object model data for data storage significantly reduces the amount of data stored, lowers the overall data processing volume during data use, and improves data utilization efficiency. Centralized storage of uniformly formatted object model data allows various business systems to extract the necessary object model data, solving the problems of independent data access and usage by different business systems, leading to data reuse difficulties, wasted system resources, and difficulty in system integration. Storing object model data in the original database according to a preset table partitioning strategy reduces the data volume of a single table. Compared to storing all object model data in one table, the overall data processing volume is reduced, improving data utilization efficiency. Cleaning the original database... The system stores object model data for a duration longer than a preset first duration to prevent the large amount of object model data stored in the original database from reducing the efficiency of various business systems using the original database. A transitional database is established to prevent data loss from the mining face during communication failures because it cannot be directly synchronized to the original database. When the communication failure disappears, the data in the transitional database is synchronized to the original database from the point of interruption, ensuring data continuity. A mirror database synchronized with the original database is established. The original database implements read and write functions, while the mirror database implements read-only functions. This separation of read and write functions means that when a business system needs to read data, it reads from the mirror database without affecting the data stored in the original database, thus improving data utilization efficiency.

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

[0017] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0018] Figure 1 A flowchart illustrating a data storage method for a fully mechanized mining face according to an embodiment of this application is shown.

[0019] Figure 2 A flowchart illustrating another data storage method for a fully mechanized mining face provided in an embodiment of this application is shown.

[0020] Figure 3 This illustration shows a structural schematic diagram of a data storage device for a fully mechanized mining face according to an embodiment of this application;

[0021] Figure 4 A schematic diagram of the structure of a data storage device for another fully mechanized mining face provided in an embodiment of this application is shown. Detailed Implementation

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

[0023] To address the current problems, this application provides a data storage method for fully mechanized mining faces, such as... Figure 1 As shown, the method includes:

[0024] 101. Obtain equipment data from the fully mechanized mining face and convert the equipment data into a standardized physical model data.

[0025] In this embodiment, as one implementation method, there are many types and numbers of equipment in the fully mechanized mining face, and each type of equipment has multiple sensors, resulting in a large amount of equipment data on the fully mechanized mining face. In addition, the underlying hardware protocols of each piece of equipment, such as electrical control and coal mining machine, are inconsistent, resulting in inconsistent equipment data formats. Therefore, the equipment data is difficult to store, use and query. Thus, it is necessary to convert the equipment data into uniformly formatted physical model data.

[0026] Specifically, each device has an edge support unit at the protocol conversion layer. The edge support unit converts the device data into a unified object model data according to the device's corresponding protocol. The object model is a data model defined by the IoT platform for the product, used to describe the product's functions. It is the digital representation of entities in the physical space (such as sensors, electrical controls, coal mining machines, etc.) in the cloud. It describes what the entity is, what it can do, and what information it can provide to the outside world from three dimensions: attributes, services, and events. Defining these three dimensions of the object model completes the definition of the product's functions.

[0027] In terms of data storage, the converted object model data includes object model codes and values. Using object model codes and values ​​for storage reduces the complexity of data processing, horizontally reduces the amount of data stored, and reduces the overall amount of data processed when using the data, thus improving the efficiency of data use. Object model data with a unified format is used in the application and transmission of various business systems, eliminating the conversion cost of data transmission between various business systems and reducing the amount of data transmitted.

[0028] 102. Store the object model data in the original database according to the preset table partitioning strategy.

[0029] In this embodiment, as one implementation method, a preset table partitioning strategy is used for table partitioning. This preset partitioning strategy includes: dynamically expanding the table (expanding from the current table to a new table), for example, partitioning by calendar month (when the creation time of the object model data spans a calendar month, the object model data is saved to a new table); partitioning by the maximum storage capacity of each table (the object model data is stored sequentially in the current table according to its creation time, and a new table is created when the remaining storage capacity of the current table is zero); and a hybrid strategy of using calendar month and the maximum storage capacity of each table, in which case the split sub-tables are recorded in a set of parent tables. This preset partitioning strategy reduces the data volume of a single table. Compared to storing all object model data in one table, the overall data volume processed in subsequent data processing is reduced, improving data utilization efficiency.

[0030] Correspondingly, during the query, a query route is provided according to the preset table partitioning strategy. Taking the preset table partitioning strategy as a hybrid strategy as an example, all the sub-tables split within a natural month are recorded in a set of parent tables, and the start time and end time of the sub-tables are recorded. When the business system queries the object model data, the start time and end time are used as query conditions. First, the parent tables that meet the query results are filtered out. Then, the initial query results are obtained from the corresponding sub-tables of the parent tables. The initial query results are merged to obtain the final query result, and the final query result is returned.

[0031] This embodiment does not extract, clean, or discard the object model data, thus ensuring the authenticity and integrity of the object model data, so that each business system can process the data according to its own needs.

[0032] In the original database, the object model data is centrally stored, and each business system only queries the data it needs and puts it into the corresponding business database for use. Compared with the existing technology where each business system independently accesses the device data, there are problems such as reinventing the wheel, poor scalability, high coupling, and difficulty in reuse during the hardware device docking stage. The integration between various business systems is difficult and costly. Therefore, the object model data is centrally stored, which reduces data redundancy, reduces the problem of business systems reinventing the wheel, and reduces the integration cost of various business systems in the fully mechanized mining face.

[0033] 103. Clean up object model data in the original database whose storage duration exceeds the preset first duration.

[0034] In this embodiment, as one implementation method, to prevent the large amount of object model data stored in the original database from reducing the efficiency of various business systems using the original database, it is necessary to clean up object model data with a storage duration exceeding a preset first duration. Cleaning can include backup and deletion, which are not limited here. For example, delete object model data with a storage duration exceeding three months, and back up object model data with a storage duration exceeding two months but less than or equal to three months.

[0035] This application discloses a data storage method, apparatus, and equipment for a fully mechanized mining face. It first acquires equipment data from the fully mechanized mining face and converts this data into uniformly formatted object model data. The object model data is then stored in the original database according to a preset table partitioning strategy. Finally, object model data in the original database with a storage duration exceeding a preset first duration is cleaned. Through the technical solution in this application, using uniformly formatted object model data for data storage significantly reduces the amount of data stored, lowers the overall data processing volume during data use, and improves data utilization efficiency. Centralized storage of uniformly formatted object model data allows various business systems to extract the necessary object model data, solving the problems of independent data access and usage by different business systems, leading to data reuse difficulties, wasted system resources, and difficulty in system integration. Storing object model data in the original database according to a preset table partitioning strategy reduces the data volume of a single table. Compared to storing all object model data in a single table, the overall data processing volume is reduced, improving data utilization efficiency. Cleaning the original database... The system stores object model data for a duration longer than a preset first duration to prevent the large amount of object model data stored in the original database from reducing the efficiency of various business systems using the original database. A transitional database is established to prevent data loss from the mining face during communication failures because it cannot be directly synchronized to the original database. When the communication failure disappears, the data in the transitional database is synchronized to the original database from the point of interruption, ensuring data continuity. A mirror database synchronized with the original database is established. The original database implements read and write functions, while the mirror database implements read-only functions. This separation of read and write functions means that when a business system needs to read data, it reads from the mirror database without affecting the data stored in the original database, thus improving data utilization efficiency.

[0036] Furthermore, as a refinement and extension of the specific implementation methods of the above embodiments, and to fully illustrate the specific implementation process in this embodiment, another data storage method for the fully mechanized mining face is provided, such as... Figure 2 As shown, the method includes:

[0037] 201. Obtain equipment data from the fully mechanized mining face and convert the equipment data into a standardized physical model data.

[0038] For this embodiment, the specific implementation process can be referred to the relevant description in step 101 of the embodiment, and will not be repeated here.

[0039] 202. Obtain the generation time of the object model data, determine the time period of the sub-table where the generation time is located, determine the generation sequence number of the object model data within the time period of the sub-table, and determine the sub-table for storing the object model data based on the generation sequence number and the maximum storage capacity of each sub-table.

[0040] In this embodiment, as one implementation method, a table segmentation period can be a natural month. A group of parent tables is named using the month, and the system automatically expands and switches to the next group of parent tables until the month is reached. Each group of parent tables includes multiple sub-tables that record start and end times. The start time of the first sub-table and the end time of the last sub-table constitute a natural month. This allows various business systems to retrieve the required data by querying start and end times, and allows the original database to be backed up and deleted using the same criteria. The object model data recorded in each sub-table is arranged chronologically, starting from sequence number 1, until the remaining storage space of the first sub-table reaches 0. At this point, the second sub-table is automatically expanded. For example, if the maximum storage space of each sub-table is 3000 object model data entries, then the sequence number of the second sub-table starts from 3001, and so on.

[0041] The sub-tables for storing the object model data are determined based on the generated ordinal number and the maximum storage capacity of each sub-table, including: calculating the value of the generated ordinal number divided by the maximum storage capacity, determining the smallest integer greater than or equal to the value, and storing the object model data in the sub-table corresponding to the smallest integer.

[0042] For example, if a piece of object model data was generated on March 7th, then the time period of the sub-table containing the generation time is March. It is determined that the object model data should be stored in the parent table corresponding to March, and the number of the object model data generated in March should be recorded. If it is the 2000th record, then the object model data should be stored in the position of the 2000th record in the first sub-table of March. If it is the 3001st record, then the object model data should be stored in the position of the 1st record in the second sub-table of March.

[0043] When dealing with very large amounts of data, storing the object model data in the original database according to a pre-defined table partitioning strategy reduces the amount of data in a single table. Compared to storing all the object model data in a single table, the overall amount of data processed is reduced, improving data utilization efficiency. For example, if all the object model data is stored in a single table (containing 100 million records), deleting a single record would require creating a while loop to find and delete that record from the entire table, significantly reducing data deletion efficiency. However, after partitioning, deleting a single record only requires locating a sub-table (containing 10 million records), finding and deleting the record from that sub-table, greatly improving data deletion efficiency.

[0044] 203. Back up the object model data in the original database that has a storage duration greater than the preset first duration and less than or equal to the preset second duration. Where the preset second duration is greater than the preset first duration, delete the object model data in the original database that has a storage duration greater than the preset second duration.

[0045] In this embodiment, as one implementation method, for example, the second storage period is preset to 3 months and the first storage period is preset to 2 months. The object model data with a storage period of more than 2 months and less than or equal to 3 months is backed up, and the object model data with a storage period of more than 3 months is deleted. That is, the original database only stores object model data with a storage period of less than or equal to 2 months. This avoids the object model data being stored in the original database for a long time, which would make the original database too large and reduce the overall efficiency of the original database. Correspondingly, when various business systems query and use the object model data in the original database, they need to complete the query within three months. The preset second storage period is longer than the preset first storage period in order to ensure that the data is not lost.

[0046] Table partitioning reduces the amount of data in a single table. Deletion and backup are performed on a per-sub-table basis, improving data utilization efficiency. Specifically, taking data deletion as an example, if a single table contains too much data, you can only use `deletetable where between begintime and endtime`, which is very time-consuming. However, with table partitioning, for data that needs to be deleted, you can perform a `trancate table` operation on the entire sub-table by month, greatly improving deletion speed.

[0047] 204. Establish a mirror database synchronized with the original database. The original database implements read and write functions and is used to store object model data, while the mirror database implements read-only functions and is used by business systems to read object model data from the mirror database.

[0048] In this embodiment, as one implementation method, configuration is made between the original database and the mirror database to synchronize the object model data written to the original database to the mirror database. When the business system needs to read, it reads from the read-only mirror database, while the original database is responsible for data storage. Before the separation of read and write operations, both read and write tasks were performed in the original database. While a read task was being performed, the original database was simultaneously performing a write (storage) task, thus reducing the efficiency of reading and storing data. After separating read and write operations, the mutual interference between read and write operations is avoided, thereby improving the efficiency of reading and storing data.

[0049] 205. Establish a transition database. The transition database is set at the end and edge of the device to store object model data that is less than the current time and a preset third time interval away. The object model data in the transition database is then synchronously uploaded to the original database.

[0050] In this embodiment, as one implementation method, a transitional database is set at the end and edge of the underground equipment. A Redis cluster is deployed at the end and edge for temporary data storage (in addition to Redis, other caching tools such as Memcached or MongoDB can also be used for data storage at the end and edge). The original database is set above ground. Communication between the underground and the above ground is established through optical fiber. Due to the harsh environment and unstable network environment in coal mines, a transitional database is established to store object model data that is less than a preset third time interval from the current time. Synchronously, object model data is transferred from the transitional database to the original database to prevent data loss due to communication failure before the data generated by the underground equipment is stored. The preset third time interval (e.g., four hours) allows time for troubleshooting.

[0051] For example, if a communication failure occurs at 3:00, the transition database continues to store the object model data. When the communication failure disappears at 6:00, the transition database simultaneously performs two processes: one is to synchronize the object model data from 3:00 to 6:00 in the transition database to the original database, and the other is to continue storing the object model data after 6:00.

[0052] By implementing a small amount of redundant storage at the endpoint and edge, the risk of data loss due to network failures caused by the instability of the coal mine environment is reduced. Synchronization after fault recovery ensures data continuity, thereby increasing the accuracy and reliability of decision-making when various business systems perform data analysis.

[0053] 206. When a communication error occurs, the synchronization process is interrupted. When the communication error disappears, determine whether to start the synchronization task from the transition database to the original database. If so, start the synchronization task until the synchronization task is completed.

[0054] In this embodiment, as one implementation method, when a communication failure occurs, the breakpoint time of the transmission of object model data from the transition database to the original database is recorded; when the communication failure disappears, it is determined whether object model data exists between the breakpoint time and the time when the communication failure disappears. If it exists, the synchronization task from the transition database to the original database is started.

[0055] When a communication failure occurs, the synchronous transmission from the transition database to the original database is interrupted. To ensure data continuity, if there is object model data between the breakpoint and the time when the communication failure disappears, the data synchronization process is started, which uploads the data between the breakpoint and the time when the communication failure disappears.

[0056] To prevent data loss after a data synchronization process fails, data synchronization needs to continue even after a failure. Specifically, this involves starting a synchronization task and continuing until completion, including: starting a first data synchronization task; determining whether the first data synchronization task is complete; if complete, setting the first data synchronization task to a completed state and clearing it; if not complete, closing the first data synchronization task and recreating a second data synchronization task. The second data synchronization task is used to transmit the object model data between the time the first data synchronization task failed and the time the communication anomaly disappeared, until all object model data between the breakpoint and the time the communication anomaly disappeared has been transmitted.

[0057] This application discloses a data storage method, apparatus, and equipment for a fully mechanized mining face. It first acquires equipment data from the fully mechanized mining face and converts this data into uniformly formatted object model data. The object model data is then stored in the original database according to a preset table partitioning strategy. Finally, object model data in the original database with a storage duration exceeding a preset first duration is cleaned. Through the technical solution in this application, using uniformly formatted object model data for data storage significantly reduces the amount of data stored, lowers the overall data processing volume during data use, and improves data utilization efficiency. Centralized storage of uniformly formatted object model data allows various business systems to extract the necessary object model data, solving the problems of independent data access and usage by different business systems, leading to data reuse difficulties, wasted system resources, and difficulty in system integration. Storing object model data in the original database according to a preset table partitioning strategy reduces the data volume of a single table. Compared to storing all object model data in a single table, the overall data processing volume is reduced, improving data utilization efficiency. Cleaning the original database... The system stores object model data for a duration longer than a preset first duration to prevent the large amount of object model data stored in the original database from reducing the efficiency of various business systems using the original database. A transitional database is established to prevent data loss from the mining face during communication failures because it cannot be directly synchronized to the original database. When the communication failure disappears, the data in the transitional database is synchronized to the original database from the point of interruption, ensuring data continuity. A mirror database synchronized with the original database is established. The original database implements read and write functions, while the mirror database implements read-only functions. This separation of read and write functions means that when a business system needs to read data, it reads from the mirror database without affecting the data stored in the original database, thus improving data utilization efficiency.

[0058] Furthermore, as Figure 1 and Figure 2 To specifically implement the method shown, this application provides a data storage device for a fully mechanized mining face, such as... Figure 3 As shown, the device includes: an acquisition module 31, a storage module 32, and a cleaning module 33;

[0059] The acquisition module 31 is used to acquire equipment data from the fully mechanized mining face and convert the equipment data into uniformly formatted physical model data.

[0060] Storage module 32 is used to store the object model data in the original database according to a preset table partitioning strategy;

[0061] Cleanup module 33 is used to clean up object model data stored in the original database that has a duration longer than a preset first duration.

[0062] In specific application scenarios, in order to store object model data in the original database according to a preset table partitioning strategy, such as Figure 4 As shown, the storage module 32 may specifically include: a first determining unit 321 and a second determining unit 322;

[0063] The first determining unit 321 is used to obtain the generation time of the object model data and determine the sub-table time period in which the generation time is located.

[0064] The second determining unit 322 is used to determine the generation sequence number of the object model data within the table partitioning time period, and to determine the sub-table for storing the object model data based on the generation sequence number and the maximum storage quantity of each sub-table.

[0065] Accordingly, in order to determine the sub-table for storing the object model data based on the generated ordinal number and the maximum storage quantity of each sub-table, the second determining unit 322 can be specifically used to calculate the value of the generated ordinal number divided by the maximum storage quantity, determine the smallest integer greater than or equal to the value, and store the object model data in the sub-table corresponding to the smallest integer.

[0066] In specific application scenarios, in order to clean up object model data stored in the original database that has a duration longer than a preset first duration, such as... Figure 4 As shown, the cleaning module 33 may specifically include: a backup unit 331 and a deletion unit 332;

[0067] Backup unit 331 is used to back up object model data stored in the original database for a duration greater than a preset first duration and less than or equal to a second duration, wherein the preset second duration is greater than the preset first duration;

[0068] The deletion unit 332 is used to delete object model data stored in the original database that has a duration longer than a preset second duration.

[0069] In specific application scenarios, a data storage device for a fully mechanized mining face, such as... Figure 4As shown, the device also includes a synchronization module 34, which can be used to establish a mirror database synchronized with the original database. The original database implements read and write functions and is used to store object model data, while the mirror database implements read-only functions and is used by the business system to read object model data from the mirror database.

[0070] In specific application scenarios, a data storage device for a fully mechanized mining face, such as... Figure 4 As shown, the device also includes a transition module 35, which may specifically include an establishment unit 351 and a judgment unit 352.

[0071] Establishment unit 351 is used to establish a transition database. The transition database is set at the end and edge of the device and is used to store object model data that is less than a preset third time interval from the current time. The object model data in the transition database is synchronously uploaded to the original database.

[0072] The judgment unit 352 is used to determine whether to start the synchronization task from the transition database to the original database when the communication abnormality occurs and the communication abnormality disappears. If so, the synchronization task is started until the synchronization task is completed.

[0073] Accordingly, in order to determine whether to start the synchronization task from the transition database to the original database, the determination unit 352 can be used to record the breakpoint when the communication failure occurs and the object model data is transmitted from the transition database to the original database; when the communication failure disappears, it determines whether the object model data exists between the breakpoint and the time when the communication failure disappears, and if it exists, the synchronization from the transition database to the original database is started.

[0074] It should be noted that other corresponding descriptions of the functional units involved in the data storage device for a fully mechanized mining face provided in this embodiment can be found in [reference needed]. Figures 1 to 2 The corresponding description will not be repeated here.

[0075] Based on the above, Figures 1 to 2 Accordingly, this embodiment also provides a storage medium, which may be volatile or non-volatile, storing computer-readable instructions thereon. When these instructions are executed by a processor, they implement the above-described method. Figures 1 to 2 The data storage method for the fully mechanized mining face is shown.

[0076] Based on this understanding, the technical solution of this application can be embodied in the form of a software product, which can be stored in a storage medium (such as a CD-ROM, USB flash drive, portable hard drive, etc.) and includes several instructions to cause a computer device (such as a personal computer, server, or communication device, etc.) to execute the methods of various implementation scenarios of this application.

[0077] Based on the above, Figures 1 to 2 The method shown and Figure 3 , Figure 4 To achieve the above objectives, this embodiment also provides a computer device, which includes a storage medium and a processor; the storage medium is used to store a computer program; the processor is used to execute the computer program to implement the above-described virtual device embodiment. Figures 1 to 2 The data storage method for the fully mechanized mining face is shown.

[0078] Optionally, the computer device may also include a user interface, a communication interface, a camera, radio frequency (RF) circuitry, sensors, audio circuitry, a Wi-Fi module, etc. The user interface may include a display screen, input units such as a keyboard, etc., and optional user interfaces may also include USB interfaces, card reader interfaces, etc. The communication interface may optionally include standard wired interfaces, wireless interfaces (such as Wi-Fi interfaces), etc.

[0079] Those skilled in the art will understand that the computer device structure provided in this embodiment does not constitute a limitation on the physical device, and may include more or fewer components, or combine certain components, or have different component arrangements.

[0080] The storage medium may also include an operating system and a communication module. The operating system is a program that manages the hardware and software resources of the aforementioned computer device, supporting the operation of information processing programs and other software and / or programs. The communication module is used to enable communication between the various components within the storage medium, as well as communication with other hardware and software in the information processing device.

[0081] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware platform, or it can be implemented by hardware.

[0082] By applying the technical solution of this application, compared with the existing technology, this application discloses a data storage method, device, and equipment for fully mechanized mining faces. It first acquires equipment data from the fully mechanized mining face, converts the equipment data into uniformly formatted object model data, stores the object model data in the original database according to a preset table partitioning strategy, and cleans up object model data in the original database whose storage duration exceeds a preset first duration. Through the technical solution of this application, using uniformly formatted object model data for data storage greatly reduces the amount of data stored, lowers the overall data processing volume during data use, and improves data utilization efficiency. Centralized storage of uniformly formatted object model data allows various business systems to extract the required object model data, solving the problems of independent data access and usage by different business systems, leading to data reuse difficulties, wasted system resources, and difficulty in system integration. Storing object model data in the original database according to a preset table partitioning strategy reduces the data volume of a single table, lowering the overall data processing volume compared to storing all object model data in one table, thus improving data utilization efficiency. Cleaning up the original database... The system stores object model data for a duration longer than a preset first duration to prevent the large amount of object model data stored in the original database from reducing the efficiency of various business systems using the original database. A transitional database is established to prevent data loss from the mining face during communication failures because it cannot be directly synchronized to the original database. When the communication failure disappears, the data in the transitional database is synchronized to the original database from the point of interruption, ensuring data continuity. A mirror database synchronized with the original database is established. The original database implements read and write functions, while the mirror database implements read-only functions. This separation of read and write functions means that when a business system needs to read data, it reads from the mirror database without affecting the data stored in the original database, thus improving data utilization efficiency.

[0083] Those skilled in the art will understand that the accompanying drawings are merely schematic diagrams of a preferred embodiment, and the modules or processes shown in the drawings are not necessarily essential for implementing this application. Those skilled in the art will understand that the modules in the apparatus of the embodiment can be distributed within the apparatus of the embodiment as described, or can be modified to be located in one or more apparatuses different from this embodiment. The modules of the above-described embodiment can be combined into one module, or further divided into multiple sub-modules.

[0084] The serial numbers in this application are for descriptive purposes only and do not represent the superiority or inferiority of any particular implementation scenario. The above disclosures are merely a few specific implementation scenarios of this application; however, this application is not limited thereto, and any variations conceived by those skilled in the art should fall within the protection scope of this application.

Claims

1. A data storage method for a fully mechanized mining face, characterized in that, include: Acquire equipment data from the fully mechanized mining face and convert the equipment data into uniformly formatted physical model data; The object model data is stored in the original database according to a preset table partitioning strategy, which includes expanding from the current table to a new table. Clean up the object model data stored in the original database whose duration exceeds a preset first duration; The method further includes: A transition database is established, which is set at the end and edge of the device to store object model data that is less than a preset third time interval from the current time, and the object model data in the transition database is synchronously uploaded to the original database. When a communication anomaly occurs, the synchronization process is interrupted. When the communication anomaly disappears, it is determined whether to start the synchronization task from the transition database to the original database. If so, then start the synchronization task and continue until the synchronization task is completed; The step of determining whether to initiate the synchronization task from the transition database to the original database includes: When a communication failure occurs, record the breakpoint when the object model data is transmitted from the transition database to the original database; When communication fails, determine whether the object model data exists between the breakpoint and the time the communication fails. If it exists, initiate the synchronization task from the transition database to the original database. The step of initiating the synchronization task from the transition database to the original database includes: initiating a first data synchronization task; determining whether the first data synchronization task is completed; if completed, setting the first data synchronization task to a completed state and clearing the first data synchronization task; if not completed, closing the first data synchronization task and recreating a second data synchronization task, wherein the second data synchronization task is used to transmit the object model data between the time the first data synchronization task failed and the time the communication anomaly disappeared, until all the object model data between the breakpoint time and the time the communication anomaly disappeared has been transmitted.

2. The method according to claim 1, characterized in that, The step of storing the object model data in the original database according to a preset table partitioning strategy includes: Obtain the generation time of the object model data and determine the time segment of the table in which the generation time is located; Determine the generation ordinal number of the object model data within the time period of the sub-table, and determine the sub-table for storing the object model data based on the generation ordinal number and the maximum storage capacity of each sub-table.

3. The method according to claim 2, characterized in that, The step of determining the sub-tables for storing the object model data based on the generated ordinal number and the maximum storage size of each sub-table includes: Calculate the value of the generated ordinal number divided by the maximum storage quantity, determine the smallest integer greater than or equal to the value, and store the object model data in the sub-table corresponding to the smallest integer.

4. The method according to claim 1, characterized in that, The step of cleaning up the object model data stored in the original database for a duration longer than a preset first duration includes: The object model data stored in the original database for a duration greater than the preset first duration and less than or equal to the preset second duration is backed up, wherein the preset second duration is greater than the preset first duration; Delete the object model data stored in the original database that has a duration longer than the preset second duration.

5. The method according to claim 1, characterized in that, The method further includes: A mirror database synchronized with the original database is established, wherein the original database implements read and write functions to store the object model data, and the mirror database implements read-only functions to allow the business system to read the object model data from the mirror database.

6. A data storage device for a fully mechanized mining face, characterized in that, include: The acquisition module is used to acquire equipment data from the fully mechanized mining face and convert the equipment data into uniformly formatted physical model data. The storage module is used to store the object model data in the original database according to a preset table partitioning strategy, wherein the preset table partitioning strategy includes expanding from the current table to a new table; The cleaning module is used to clean up the object model data stored in the original database that has a duration longer than a preset first duration; The transition module includes: a setup unit and a judgment unit; The establishment unit is used to establish a transition database. The transition database is set at the end and edge of the device and is used to store object model data that is less than a preset third time interval from the current time. The object model data in the transition database is synchronously uploaded to the original database. The judgment unit is used to determine whether to start the synchronization task from the transition database to the original database when the communication abnormality occurs and the communication abnormality disappears. If so, the synchronization task is started until the synchronization task is completed. The judgment unit is used to record the breakpoint time when communication failure occurs, when the object model data is transmitted from the transition database to the original database; when the communication failure disappears, it determines whether object model data exists between the breakpoint time and the time when the communication failure disappears; if it exists, it initiates the synchronization from the transition database to the original database. The judgment unit is used to start the first data synchronization task; determine whether the first data synchronization task is completed; if completed, set the first data synchronization task to the completed state and clear the first data synchronization task; if not completed, close the first data synchronization task and recreate the second data synchronization task. The second data synchronization task is used to transmit the object model data between the time the first data synchronization task failed and the time the communication abnormality disappeared, until all the object model data between the breakpoint time and the time the communication abnormality disappeared has been transmitted.

7. A storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the data storage method for the fully mechanized mining face as described in any one of claims 1 to 5.

8. A computer device, comprising a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, characterized in that, When the processor executes the program, it implements the data storage method for the fully mechanized mining face as described in any one of claims 1 to 5.

Images