A data management method, device, apparatus, medium and product

Abstract

A data management method, device, equipment, medium and product are disclosed. The method is applied to a data management system, the data management system is used for storing multi-source data, the data includes data associated with a mine, the method comprises: in response to a meta-model management operation on a meta-model management interface, obtaining meta-model management information; based on the meta-model management information, updating the meta-information data of the data management system; in the case that the meta-model management information indicates to create a physical table of the meta-model, creating the physical table based on the meta-model management information. The technical scheme of the embodiment of the present application unifies the description standard of mine disaster data through the meta-model management information, completes the standardized definition of the meta-model, and creates the physical table based on the meta-model management information, so as to quickly manage the physical table when a new data source or data structure is changed, thereby improving the data management efficiency.

Description

Technical Field

[0001] This invention relates to the field of data management technology, and in particular to a data management method, apparatus, equipment, medium and product. Background Technology

[0002] With the advancement of intelligent coal mine construction, various sensors and monitoring systems have been deployed underground, generating massive amounts of multi-source, heterogeneous disaster-related data. This data typically originates from different business systems and has different data formats, storage structures, and update frequencies.

[0003] In existing technologies, data models for each business system are defined independently, lacking unified standards and specifications, which makes data fusion and comprehensive analysis difficult. Furthermore, due to the lack of automated model management and deployment mechanisms, developers often need to manually analyze differences, write adaptation code, and execute it to create physical tables. Therefore, a data management method is urgently needed to solve these problems. Summary of the Invention

[0004] This invention provides a data management method, apparatus, device, medium, and product to solve the problem of standardized configuration of meta-models.

[0005] According to one aspect of the present invention, a data management method is provided, the method comprising: Responding to metamodel management operations on the metamodel management interface, obtain metamodel management information; Based on the meta-model management information, update the meta-information data of the data management system; If the metamodel management information instructs the creation of a physical table for the metamodel, the physical table is created based on the metamodel management information.

[0006] According to another aspect of the present invention, a data management apparatus is provided, comprising: The acquisition module is used to respond to metamodel management operations on the metamodel management interface and acquire metamodel management information. The update module is used to update the metadata data of the data management system based on the metadata model management information. A creation module is used to create the physical table based on the metamodel management information when the metamodel management information indicates that the physical table of the metamodel should be created.

[0007] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the method described in any embodiment of the present invention.

[0008] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the method described in any embodiment of the present invention.

[0009] According to another aspect of the present invention, a computer program product is provided, the computer program product comprising a computer program that, when executed by a processor, implements the method described in any embodiment of the present invention.

[0010] The technical solution of this invention involves obtaining metamodel management information in response to metamodel management operations on the metamodel management interface; updating the meta-information data of the data management system based on the metamodel management information; and creating the physical table based on the metamodel management information when the metamodel management information indicates the creation of the physical table for the metamodel. This method updates the meta-information data of the data management system through metamodel management information, completes the standardized definition of the metamodel, and creates physical tables based on the metamodel management information to automatically manage the physical tables, thereby improving data management efficiency.

[0011] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

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

[0013] Figure 1 A flowchart of a data management method provided in Embodiment 1 of the present invention; Figure 2 A flowchart of a data management method provided in Embodiment 2 of the present invention; Figure 3 This is a flowchart of a meta-model management and physical table generation method provided in an embodiment of the present invention; Figure 4 This is a flowchart of an automated data storage and processing method provided in an embodiment of the present invention; Figure 5 This is a schematic diagram of the structure of a data management device provided in Embodiment 3 of the present invention; Figure 6 A schematic diagram of an electronic device that can be used to implement embodiments of the present invention is shown. Detailed Implementation

[0014] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0015] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0016] Example 1 Figure 1 This is a flowchart illustrating a data management method provided in Embodiment 1 of the present invention. This embodiment is applicable to situations involving the management of meta-models and subsequently physical tables. The method can be executed by a data management device, which can be implemented in hardware and / or software and can be configured in an electronic device. The electronic device can be, for example, a laptop, desktop computer, or smart tablet. Figure 1 As shown, the method includes: S110. Responding to metamodel management operations on the metamodel management interface, obtain metamodel management information.

[0017] In this embodiment, the metamodel management interface can be an interactive interface provided by an electronic device. The metamodel management interface can provide a visual interface for users to interact with the data management system. The metamodel can be a standardized model used to describe mine-related data. The metamodel manages data possessing these attributes by indicating the attributes that must be included when describing mine-related data. Attributes can be, for example, the identifier of the device generating the data, the timestamp when the data was generated, and / or the type of mine-related data. Metamodel management operations can be operations performed by the user to manage the metamodel. Metamodel management operations can include adding, modifying, and / or deleting metamodels. Metamodel management information can be information that implements metamodel management, such as structured operation instructions and configuration information for the metamodel. Metamodel management information originates from user input on the metamodel management interface, and its form can be, for example, a configuration form, parameters of an application programming interface, or a standardized data exchange format.

[0018] Specifically, when a user performs metamodel management operations on the metamodel management interface, the data management system obtains the metamodel management information entered by the user according to the user's instructions.

[0019] For example, the data management system receives information input by the user for metamodel management operations through the metamodel management interface. This information can be in the form of a data form or configured data in JSON / XML format. The data management system then parses this information and verifies user permissions. After successful permission verification, the conversion module encapsulates this information and converts it into a set of machine language instructions or structured data with a specific format that the system can recognize internally; this constitutes the metamodel management information.

[0020] S120. Based on the meta-model management information, update the meta-information data of the data management system.

[0021] In this embodiment, the metadata data can be structured data generated based on the metadata model. The metadata data records and stores the structure and attributes of all metadata models in the data management system. The metadata data can be stored in the data management system for unified management of metadata models.

[0022] Specifically, the data management system updates the metamodel according to the instructions of the metamodel management information, and updates and stores the latest updated information in the metamodel management information into the meta information data.

[0023] S130. If the metamodel management information indicates that a physical table of the metamodel should be created, the physical table should be created based on the metamodel management information.

[0024] Specifically, if the metamodel management information includes instructions for creating a metamodel, then the metamodel management information is mapped to the physical tables. The mapping process can be, for example, the data management system first parses the metamodel management information, extracting the metamodel's structural definition, attributes, and constraints between different attributes. Subsequently, the data management system converts the extracted information into a standard-compliant script and runs the script to obtain the physical tables.

[0025] The technical solution of this invention involves obtaining metamodel management information in response to metamodel management operations on the metamodel management interface; updating the meta-information data of the data management system based on the metamodel management information; and creating the physical table based on the metamodel management information when the metamodel management information indicates the creation of the physical table for the metamodel. This method updates the meta-information data of the data management system through metamodel management information, completes the standardized definition of the metamodel, and creates physical tables based on the metamodel management information to automatically manage the physical tables, thereby improving data management efficiency.

[0026] Example 2 Figure 2 This is a flowchart illustrating a data management method according to Embodiment 2 of the present invention. This embodiment is an optimization based on any of the above embodiments, and mainly includes a detailed description of the process of managing the metamodel according to the operation type and creating physical tables based on the metamodel management information. It should be noted that technical details not described in detail in this embodiment can be found in any of the above embodiments. Figure 2 As shown, the method includes: S210. Responding to metamodel management operations on the metamodel management interface, obtain metamodel management information.

[0027] S220. If the operation type indicates addition or modification, then update the metadata data of the data management system according to the model information, and execute S240.

[0028] In this embodiment, the metamodel management information includes operation type and model information of the metamodel. The model information includes metadata of the metamodel, first source identifier of the metamodel, storage type of data storage of the metamodel, and one or more of the business scenarios to which the metamodel belongs. The first source identifier is used to identify the data source subsystem corresponding to the metamodel.

[0029] In this embodiment, the operation type can be the type of operation instructing the user to perform on the metamodel. The operation type can be adding a metamodel, modifying a metamodel, or deleting a metamodel. Model information can be structured data information used to describe the metamodel. Model information can include descriptions of the corresponding metamodel's structural characteristics, its business environment, and its data source. Model information can include metadata, a first source identifier, storage type, and / or the business scenario to which the metamodel belongs. Metadata can be data describing the structure and constraints of the metamodel. Physical tables can be created based on metadata, which includes, but is not limited to, attributes of data associated with the mine; attributes can be physical attributes of the data. The first source identifier can be understood as an identifier that uniquely identifies the source of the metamodel. The source of the metamodel can be the data source subsystem corresponding to the metamodel. The data source subsystem can be part of the data management system used to generate data associated with the mine. Storage type can be the storage type of the data associated with the mine. Storage type can be partitioned according to a specific dimension or not partitioned. Business scenario can be the specific business scenario to which the metamodel belongs. A business scenario could be, for example, data monitoring during coal mine data collection.

[0030] Specifically, if the operation type indicates adding a metamodel, the model information is validated. Validation may include, for example, judging the legality and / or completeness of the model information. If the validation passes, the metamodel configuration is saved, and the model information is added to the metadata data of the data management system. If the operation type indicates modifying a metamodel, the model information is also validated. If the validation passes, the parts of the metadata data that need to be modified are deleted, and then the latest model information is written.

[0031] S230. If the operation type indicates deletion, then the meta-model is deleted from the meta-information data.

[0032] Specifically, if the operation type indicates deletion of a metamodel, then the corresponding metamodel is queried from the meta information data and deleted.

[0033] S240. Extract the required first information from the meta-model management information according to the table name generation rules to generate the table name of the physical table, and check whether the table name conflicts.

[0034] In this embodiment, the table name generation rule can be a predefined rule for generating physical table names. The data management system can automatically generate the physical table name based on the table name generation rule, provided that the metamodel management information instructs the creation of a physical table for the metamodel. The first information can be the information required to generate the physical table name. The first information can be determined by the table name generation rule. The first information includes, but is not limited to, the source of the data managed by the metamodel, the timestamp when the data was generated, and / or the name of the logical table corresponding to the physical table.

[0035] Specifically, the data management system extracts the first information required to generate the physical table name from the meta-model management information according to the table name generation rules, and combines it into the physical table name according to the instructions of the table name generation rules. After obtaining the table name, the newly generated table name is compared with the existing table names to check for naming conflicts.

[0036] If there is a conflict in the table name, an error alarm will be displayed on the metamodel management interface, prompting the user to provide the correct metamodel management information; If there are no conflicts in the table names, physical tables will continue to be generated based on the meta-model management information.

[0037] S250. Extract the required second information from the meta-model management information, and generate a first statement defining the structure of the physical table based on the second information.

[0038] In this embodiment, the second information may be information indicating the structure of the physical table. The second information is extracted from the metamodel management information and includes, but is not limited to, table field definitions, primary key / index settings, partitioning strategies, and / or the physical attributes of the stored data. The first statement may be a standardized data definition statement. Executing the first statement allows for the creation or modification of the corresponding physical table.

[0039] Specifically, if there is no conflict in the newly generated table name, the data management system extracts the second information from the meta-model management information. Based on the second information, it maps the information at specific points in the second information to the first statement through predefined syntax rules.

[0040] S260. Execute the first statement to create the corresponding physical table.

[0041] Specifically, the data management system parses and executes the first statement, and creates the corresponding physical tables according to the instructions in the first statement.

[0042] For example, Figure 3 This is a flowchart illustrating metamodel management and physical table generation provided by an embodiment of the present invention. Users perform metamodel management operations on the metamodel management interface. The metamodel management operation indicates the type of operation on the metamodel. If the indicated operation type is "add" or "modify," the metamodel structure is defined based on the model information, and the representation of the corresponding physical table is validated. If the validation passes, the metamodel configuration (i.e., model information) is updated to the meta-information data. If the indicated operation type is "delete," the corresponding model information is deleted from the meta-information data. If the metamodel management information indicates the creation of a physical table for the metamodel, a first statement is generated, Data Definition Language (DDL) is executed, the corresponding physical table is created, and the logical table corresponding to the physical table is updated to update the table mapping relationship.

[0043] The technical solution of this invention involves obtaining metamodel management information in response to metamodel management operations on the metamodel management interface. If the operation type indicates addition or modification, the meta-information data of the data management system is updated according to the model information. If the operation type indicates deletion, the metamodel is deleted from the meta-information data. The required first information is extracted from the metamodel management information according to table name generation rules to generate the table name of the physical table, and the table name is checked for conflicts. If the table name does not conflict, the required second information is extracted from the metamodel management information, and a first statement defining the structure of the physical table is generated based on the second information. The first statement is executed to create the corresponding physical table. By managing the corresponding physical table through the metamodel, manual configuration and modification of the physical table are avoided when adding new data sources or changing the data structure. Automated physical table generation and time-series data storage significantly reduce the access time and manpower costs of new data sources, improving development efficiency. Metamodel management information enables business personnel to define and manage data models more flexibly, quickly respond to business changes, and improve the flexibility and ease of use of the metamodel.

[0044] In another embodiment, the process of storing coal mine disaster-related data includes: A1. Obtain time-series data through the data access interface of the data management system. The time-series data includes coal mine disaster-related data.

[0045] In this embodiment, time-series data can be understood as a series of data recorded in chronological order according to timestamps. Time-series data may include coal mine disaster-related data, such as methane concentration, temperature, carbon monoxide concentration, hydrological borehole water level, dust concentration, borehole stress, and / or pipeline flow rate.

[0046] Specifically, time-series data is obtained through a unified data access interface provided by the data management system.

[0047] A2. If the data format of the time series data passes the verification, obtain the second source identifier contained in the time series data. The second source identifier is used to identify the data source subsystem to which the time series data belongs.

[0048] In this embodiment, data format verification can be a check to see if the data format of the time-series data meets the requirements. Data format verification includes, but is not limited to, checking and verifying the structure, type, value range, and / or encoding specifications of the time-series data. The second source identifier can be an identifier indicating the source of the time-series data. The source of the time-series data can be the data source subsystem to which the time-series data belongs, and the data source subsystem can include the device that generates the time-series data.

[0049] Specifically, the data format of the timing data is verified. If the data format verification passes, the second source identifier is parsed and extracted from the verified timing data. The second source identifier can be extracted from, for example, the data packet header or the first frame information.

[0050] A3. Query the meta-model that matches the second source identifier from the data management system.

[0051] Specifically, the metamodel associated with the data source subsystem pointed to by the second source identifier is retrieved from the data management system, and this metamodel is used as the metamodel that matches the second source identifier.

[0052] A4. If a meta-model matching the second source identifier exists, then the time-series data is mapped to the meta-model matching the second source identifier.

[0053] Specifically, if a meta-model matching the second source identifier exists, the time series data is mapped to the matching meta-model according to predefined rules.

[0054] For example, the mapping process can be as follows: each data point of the time series data record is parsed and classified according to the attributes of the data points. Each attribute can be accurately mapped to a field in the meta-model. Subsequently, the data management system converts the time series data from the message (e.g., JSON) format into a structured data format according to the instructions of the meta-model.

[0055] Optionally, mapping the time-series data to the meta-model matching the second source identifier includes: B1. Map the fields in the time series data according to the predefined mapping rules to obtain the second statement corresponding to the time series data; In this embodiment, the mapping rule can be a predefined rule that maps specific fields in time-series data to a second statement. The specific fields in the time-series data indicated in the mapping rule can be, for example, field names, types, and / or values. The second statement can be a data definition language used to instruct the storage of time-series data.

[0056] Specifically, the data management system parses and reads fields at specific locations in the time-series data according to the mapping rules, transforms them, and maps them to the corresponding locations in the second statement.

[0057] B2. Perform a uniqueness check on the statements included in the meta-model that match the second statement with the second source identifier, and obtain the check result; Specifically, the data management system performs a uniqueness check on the statements included in the meta-model that match the second statement with the second source identifier, and verifies whether the time-series data indicated by the second statement has been stored in the data management system, obtaining the verification result. In addition, the legality and completeness of the second statement can also be verified.

[0058] B3. If the verification result indicates that the verification is successful, execute the second statement to store the time-series data statement in the physical table of the second source identifier matching meta-model.

[0059] Specifically, if the verification result indicates that the verification is successful, the data management system automatically queries the physical table corresponding to the matching meta-model and executes the second statement to store the time series data into the physical table.

[0060] For example, Figure 4 This is a flowchart of an automated data storage and processing method provided by an embodiment of the present invention. The data management system is equipped with an Extract Transform Load (ETL) tool that receives time-series data in JSON format and performs data format validation on the time-series data. If the data format validation passes, it queries the meta-model that matches the time-series data. If a matching meta-model exists, it parses the data mapping rules (i.e., mapping rules) and performs uniqueness validation on the time-series data. If the validation passes, it writes the time-series data into the physical table corresponding to the matching meta-model and uses the physical table to update the cached data of the data management system.

[0061] In another embodiment, the management of physical tables in the data management method includes: When the storage type corresponding to the meta-model is automatic table partitioning, the physical tables are partitioned according to the partitioning dimensions when the partitioning conditions are met; and / or, If the deletion conditions of the physical table are met, delete the physical table; and / or, When the creation conditions of the physical table are met, a new sub-table is created for the physical table.

[0062] In this embodiment, automatic table partitioning can be a storage type that instructs the automatic creation of corresponding sub-tables for physical tables. Automatic table partitioning can be indicated by specific fields in the metamodel management information. Partitioning conditions can be conditions for dividing physical tables according to specific dimensions of the data. Partitioning conditions can be, for example, partitioning physical tables according to time. The partitioning dimension can be a physical dimension of the data. For example, the partitioning dimension can be a time dimension, which may include day, month, quarter, and / or year, etc. Deletion conditions can be conditions that trigger a deletion operation on a physical table. Deletion conditions can be related to the creation time of the physical table; for example, deletion conditions can be deleting a physical table that has been created for a certain period of time, or deleting the sub-tables corresponding to a physical table that has been created for a certain period of time. Creation conditions can be conditions that trigger the creation of sub-tables for a physical table. Creation conditions can be related to, for example, time periods, business environments, and the current data volume of the physical table. For example, the creation conditions could be: before the start of a new time period, a new sub-table is created for the physical table with a pre-set duration; a new sub-table is created for the physical table based on the new business environment; or the physical table currently stores a maximum amount of data, so a new sub-table is created for the physical table to store new data.

[0063] Specifically, the data management system can partition the physical tables corresponding to the meta-model with automatic partitioning storage type according to the partitioning conditions, and create new sub-tables; delete physical tables and / or corresponding sub-tables that meet the deletion conditions according to the deletion conditions; and / or create new sub-tables for physical tables according to the creation conditions.

[0064] The present invention will be described by way of example below, with "system" referring to "data management system": In existing technologies, the data models (i.e., meta-models) of each business system are defined independently, lacking unified standards and specifications, which makes data fusion and comprehensive analysis difficult. Furthermore, when new data sources are added or data structures change, developers need to manually write code for adaptation, resulting in long development cycles and low efficiency. In addition, for monitoring data with strong time-series characteristics, traditional single-table storage methods lead to excessively large data volumes in a single table, causing a sharp decline in query performance. Although table partitioning can solve this problem, the formulation of partitioning rules and the creation and destruction of tables lack automated lifecycle management. Moreover, the tight binding of data tables to specific business operations makes it difficult to quickly respond to new business analysis needs. Therefore, there is an urgent need for a technical solution that can achieve standardized definition, automated storage, and intelligent management of mine disaster data models.

[0065] To achieve the above objectives, this invention constructs a dynamically configurable meta-model management system that separates the business logic, storage logic, and access logic of data, thereby realizing full-process automation and standardization of data from access to storage.

[0066] In one example, the method of the present invention may include metamodel management, dynamic table structure management, and data parsing and storage: For example, metamodel management can characterize the metamodel from multiple dimensions by introducing concepts such as "data source subsystem," "storage business classification" (i.e., the type of data stored in the physical table corresponding to the metamodel) (e.g., real-time values, historical values), and "application business tags" (i.e., the business scenario to which the metamodel belongs). Users can define the structure (metadata) of data tables (i.e., physical tables) through a graphical interface (i.e., metamodel management operations), and specify its subsystem (i.e., the data source subsystem corresponding to the metamodel), storage type (independent table (i.e., no table partitioning) or time-partitioned table), business scenario, etc. The system will automatically generate physical table names and check for conflicts according to rules (i.e., table name generation rules) (e.g., SUB_TB_[subsystem number]_[logical table name]_[time identifier]).

[0067] For example, dynamic table structure management can include: for time-series data, the system supports automatic table partitioning (time collection table) by strategy such as day, month, quarter, year (i.e., physical table partitioning according to the partitioning dimension); users can set the "creation strategy" (i.e. creation conditions) (such as creating N days in advance) and "deletion strategy" (i.e. deletion conditions) (such as automatically deleting the oldest table after keeping M tables) for historical tables (i.e. physical tables that have been created), and the system executes them automatically, realizing unattended management of the entire life cycle of physical tables.

[0068] For example, data parsing and storage include: receiving JSON data (i.e., time-series data) uploaded by an Extract Transform Load (ETL) tool through a unified data access interface provided by the system. Based on the source identifier in the JSON data packet (i.e., a data packet encapsulating multiple time-series data points), the system automatically finds a predefined meta-model. Then, it automatically maps the fields in the JSON to SQL statements (i.e., the second statement) according to the mapping relationship (i.e., mapping rules) and stores them in the correct physical table. This process includes uniqueness verification and supports add, delete, and modify operations.

[0069] This invention enforces a unified description standard for mine disaster data through a meta-model, laying a solid foundation for data interoperability and in-depth analysis. Simultaneously, the solution implements templated configuration for data access, replacing traditional coding, significantly reducing the access time and manpower costs for new data sources and improving development efficiency. Furthermore, automated time-based table partitioning and lifecycle management effectively address the storage and performance pressures brought by massive amounts of time-series data, giving the system excellent horizontal scalability. Finally, by decoupling business logic from storage, business personnel can more flexibly define and manage data models, quickly responding to business changes, and the automatically generated query interfaces further lower the technical barrier to data use.

[0070] Example 3 Figure 5 This is a schematic diagram of a data management device provided in Embodiment 3 of the present invention. Figure 5 As shown, the device includes: The acquisition module 310 is used to respond to metamodel management operations on the metamodel management interface and acquire metamodel management information. Update module 320 is used to update the metadata data of the data management system based on the metadata model management information; The creation module 330 is used to create the physical table based on the metamodel management information when the metamodel management information indicates that the physical table of the metamodel should be created.

[0071] The technical solution of this invention involves an acquisition module responding to metamodel management operations on the metamodel management interface to acquire metamodel management information; an update module updating the meta-information data of the data management system based on the metamodel management information; and a creation module creating the physical table based on the metamodel management information when instructed by the metamodel management information. This method updates the meta-information data of the data management system through metamodel management information, completes the standardized definition of the metamodel, and creates physical tables based on the metamodel management information to automatically manage the physical tables, thereby improving data management efficiency.

[0072] In one embodiment, the metamodel management information includes operation type and model information of the metamodel. The model information includes metadata of the metamodel, a first source identifier of the metamodel, a storage type for data storage of the metamodel, and one or more of the business scenarios to which the metamodel belongs. The first source identifier is used to identify the data source subsystem corresponding to the metamodel. The update module 320 is specifically used for: If the operation type indicates addition or modification, then the metadata data of the data management system is updated according to the model information; If the operation type indicates deletion, then the meta-model is deleted from the meta-information data.

[0073] In one embodiment, module 330 is created specifically for: The table name of the physical table is generated by extracting the required first information from the meta-model management information according to the table name generation rules, and the table name is checked for conflict. If there is no conflict with the table name, the required second information is extracted from the meta-model management information, and a first statement defining the structure of the physical table is generated based on the second information; Execute the first statement to create the corresponding physical table.

[0074] In one embodiment, the device further includes: The time-series data acquisition module is used to acquire time-series data through the data access interface of the data management system, wherein the time-series data includes coal mine disaster-related data; The second source identifier acquisition module is used to acquire a second source identifier contained in the time series data when the data format verification of the time series data passes. The second source identifier is used to identify the data source subsystem to which the time series data belongs. The query module is used to query the meta-model that matches the second source identifier from the data management system; The mapping module is used to map the time series data to the metamodel that matches the second source identifier if a metamodel exists.

[0075] In one embodiment, the mapping module is specifically used for: The fields in the time series data are mapped according to predefined mapping rules to obtain the second statement corresponding to the time series data; Perform a uniqueness check on the statements included in the meta-model that match the second statement with the second source identifier to obtain the check result; If the verification result indicates that the verification passed, the second statement is executed to store the time-series data statement in the physical table of the second source identifier matching metamodel.

[0076] In one embodiment, the device further includes a table management module for: When the storage type corresponding to the meta-model is automatic table partitioning, the physical tables are partitioned according to the partitioning dimensions when the partitioning conditions are met; and / or, If the deletion conditions of the physical table are met, delete the physical table; and / or, When the creation conditions of the physical table are met, a new sub-table is created for the physical table.

[0077] The data management device provided in this embodiment of the invention can execute a data management method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of executing the method.

[0078] Example 4 Figure 6A schematic diagram of an electronic device that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0079] like Figure 6 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded into the RAM 13 from storage unit 18. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0080] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0081] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as the methods proposed in this invention.

[0082] In some embodiments, the method proposed in this invention can be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the method described above can be performed. Alternatively, in other embodiments, processor 11 can be configured to perform the method proposed in this invention by any other suitable means (e.g., by means of firmware).

[0083] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard parts (ASSPs), systems-on-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0084] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0085] In the context of this invention, a computer-readable storage medium stores computer instructions that are used to cause a processor to execute and implement the method provided by this invention.

[0086] The present invention also provides a computer program product comprising a computer program that, when executed by a processor, implements the method provided according to embodiments of the present invention.

[0087] Computer-readable storage media can be tangible media that may contain or store computer programs for use by or in conjunction with an instruction execution system, apparatus, or device. Computer-readable storage media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, computer-readable storage media can be machine-readable signal media. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0088] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device for displaying information to the user, such as a cathode ray tube (CRT) or a liquid crystal display (LCD); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0089] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0090] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system. It addresses the shortcomings of traditional physical hosts and Virtual Private Server (VPS) services, such as high management difficulty and weak business scalability.

[0091] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0092] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A data management method, characterized in that, Applied to a data management system for storing multi-source data, including data associated with a mine, the method includes: Responding to metamodel management operations on the metamodel management interface, obtain metamodel management information; Based on the meta-model management information, update the meta-information data of the data management system; If the metamodel management information instructs the creation of a physical table for the metamodel, the physical table is created based on the metamodel management information.

2. The method according to claim 1, characterized in that, The metamodel management information includes operation type and model information of the metamodel. The model information includes metadata of the metamodel, first source identifier of the metamodel, storage type of data storage of the metamodel, and one or more of the business scenarios to which the metamodel belongs. The first source identifier is used to identify the data source subsystem corresponding to the metamodel. The step of updating the metadata data of the data management system based on the metadata model management information includes: If the operation type indicates addition or modification, then the metadata data of the data management system is updated according to the model information; If the operation type indicates deletion, then the meta-model is deleted from the meta-information data.

3. The method according to claim 1, characterized in that, When the metamodel management information instructs the creation of a physical table for the metamodel, creating the physical table based on the metamodel management information includes: The table name of the physical table is generated by extracting the required first information from the meta-model management information according to the table name generation rules, and the table name is checked for conflict. If there is no conflict with the table name, the required second information is extracted from the meta-model management information, and a first statement defining the structure of the physical table is generated based on the second information. Execute the first statement to create the corresponding physical table.

4. The method according to claim 1, characterized in that, Also includes: Time-series data, including coal mine disaster-related data, is obtained through the data access interface of the data management system. If the data format of the time series data passes the verification, a second source identifier contained in the time series data is obtained. The second source identifier is used to identify the data source subsystem to which the time series data belongs. Query the metamodel that matches the second source identifier from the data management system; If a meta-model matching the second source identifier exists, the time-series data is mapped to the meta-model matching the second source identifier.

5. The method according to claim 4, characterized in that, Mapping the time-series data to the meta-model matching the second source identifier includes: The fields in the time series data are mapped according to predefined mapping rules to obtain the second statement corresponding to the time series data; Perform a uniqueness check on the statements included in the meta-model that match the second statement with the second source identifier to obtain the check result; If the verification result indicates that the verification passed, the second statement is executed to store the time-series data statement in the physical table of the second source identifier matching metamodel.

6. The method according to claim 1, characterized in that, Also includes: When the storage type corresponding to the meta-model is automatic table partitioning, the physical tables are partitioned according to the partitioning dimensions when the partitioning conditions are met; and / or, If the deletion conditions of the physical table are met, delete the physical table; And / or, When the creation conditions of the physical table are met, a new sub-table is created for the physical table.

7. A data management device, characterized in that, include: The acquisition module is used to respond to metamodel management operations on the metamodel management interface and acquire metamodel management information. The update module is used to update the metadata data of the data management system based on the metadata model management information. A creation module is used to create the physical table based on the metamodel management information when the metamodel management information indicates that the physical table of the metamodel should be created.

8. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the method of any one of claims 1-6.

10. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the method according to any one of claims 1-6.

Images