A multi-level data management system, method, electronic device and storage medium

Abstract

The application relates to a multi-level data management system, method, electronic equipment and storage medium, the system comprising at least one edge end, at least one local end and a cloud end, for each edge end, the edge end is used for generating at least one basic data, each basic data comprises a first unique identifier and a second unique identifier, for each local end, the local end is used for receiving at least one basic data generated by at least one edge end, and according to the second unique identifier corresponding to each basic data, all the basic data are classified and stored; the cloud end is used for receiving all the classified basic data sent by all the local ends, and according to the first unique identifier and the second unique identifier corresponding to each classified basic data, each classified basic data is managed. Through the system, the efficiency and reliability of data management can be improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, in particular, the present application relates to a multi-level data management system, method, electronic device and storage medium. BACKGROUND

[0002] With the rapid development of Internet of Things (IoT) and edge computing, data generation and processing gradually move closer to the edge. However, this distributed generation and centralized management mode of data poses new challenges to data synchronization, differentiation and audit. In the prior art, the common data management system often lacks effective identification and classification mechanism when dealing with multi-level data synchronization and audit, resulting in data confusion, management difficulty and low audit efficiency and other problems. SUMMARY

[0003] The technical problem to be solved by the present application is to provide a multi-level data management system, method, electronic device and storage medium, aiming to solve at least one of the above technical problems.

[0004] In a first aspect, the technical solution of the present application to solve the above technical problems is as follows: a multi-level data management system, comprising at least one edge, at least one local end and a cloud, each of the local ends is in communication connection with all the edges, and the cloud is in communication connection with all the local ends;

[0005] For each edge, the edge is used to generate at least one basic data, each basic data contains a first unique identifier and a second unique identifier, the first unique identifier represents the identity of the basic data, and the second unique identifier represents the identity of the edge to which the basic data belongs;

[0006] For each local end, the local end is used to receive at least one basic data generated by at least one edge, and according to the second unique identifier corresponding to each basic data, all basic data are classified and stored;

[0007] The cloud is used to receive the classified basic data sent by all local ends, and according to the first unique identifier and the second unique identifier corresponding to each classified basic data, each classified basic data is managed.

[0008] The beneficial effects of the present application are: through the unique identification mechanism, that is, through the setting of the first unique identifier and the second unique identifier, the efficient synchronization, accurate differentiation and effective management of data between the edge, the local end and the cloud can be realized. The system can ensure the accuracy and integrity of data in the transmission process between different levels (edge, local end and cloud), and improve the efficiency and reliability of data management.

[0009] On the basis of the above technical solutions, the application can be further improved as follows.

[0010] Further, the cloud end is further used for:

[0011] The classified basic data is audited to obtain an audit result of each piece of the classified basic data.

[0012] Further, the cloud end is further used for:

[0013] The audit result is transmitted back to the corresponding local end and edge end through a Kafka message queue.

[0014] Further, the cloud end is further used for:

[0015] For each audit result, all classified basic data is divided into different types of data.

[0016] Based on the obtained types, a third unique identifier corresponding to the type of each basic data is generated, and for each third unique identifier, the third unique identifier is used to represent the type to which the corresponding basic data belongs.

[0017] Further, for each local end, the local end is further used for periodically or in real time transmitting at least one piece of classified basic data to the cloud end.

[0018] In a second aspect, the application provides a multi-level data management method to solve the above technical problems, which is applied to a local end and includes the following steps:

[0019] At least one edge end transmits at least one piece of basic data, each piece of the basic data contains a first unique identifier and a second unique identifier, the first unique identifier represents the identity of the basic data, and the second unique identifier represents the identity of the edge end to which the basic data belongs;

[0020] According to the second unique identifier corresponding to each piece of the basic data, all basic data is classified and stored.

[0021] The classified basic data is transmitted to the cloud end, so that the cloud end manages the classified basic data according to the first unique identifier and the second unique identifier corresponding to each piece of the classified basic data.

[0022] In a third aspect, the application provides a multi-level data management method to solve the above technical problems, which is applied to a cloud end and includes the following steps:

[0023] receiving at least one piece of basic data sent by at least one local end, for each of the local ends, the local end is configured to receive at least one piece of basic data generated by at least one edge end, and according to a second unique identifier corresponding to each piece of the basic data, classify and store all the basic data, each piece of the basic data comprising a first unique identifier and a second unique identifier, the first unique identifier representing an identity of the basic data, and the second unique identifier representing an identity of the edge end to which the basic data belongs;

[0024] managing each piece of the classified basic data according to the first unique identifier and the second unique identifier corresponding to each piece of the classified basic data.

[0025] In a fourth aspect, the present application provides a multi-level data management method to solve the above technical problems, which is applied to an edge end and comprises the following steps:

[0026] generating at least one piece of basic data, each piece of the basic data comprising a first unique identifier and a second unique identifier, the first unique identifier representing an identity of the basic data, and the second unique identifier representing an identity of the edge end to which the basic data belongs;

[0027] sending at least one piece of the basic data to a corresponding local end, so that the local end classifies and stores all the basic data according to a second unique identifier corresponding to each piece of the basic data, and sends each piece of the classified basic data to a cloud end, so that the cloud end manages each piece of the classified basic data according to a first unique identifier and a second unique identifier corresponding to each piece of the classified basic data.

[0028] In a fifth aspect, the present application provides an electronic device to solve the above technical problems, which comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the multi-level data management method of the present application when executing the computer program.

[0029] In a sixth aspect, the present application provides a computer readable storage medium to solve the above technical problems, which stores a computer program, and the computer program is executable on a processor to implement the multi-level data management method of the present application.

[0030] Additional aspects and advantages of the present application will be made apparent by the following description and the accompanying drawings. BRIEF DESCRIPTION OF DRAWINGS

[0031] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments of the present application will be briefly introduced.

[0032] Figure 1 A structural schematic diagram of a multi-level data management system provided for an embodiment of the present application;

[0033] Figure 2 A flowchart of a multi-level data management method provided for an embodiment of the present application;

[0034] Figure 3 A flowchart of another multi-level data management method provided for an embodiment of the present application;

[0035] Figure 4 A flowchart of still another multi-level data management method provided for an embodiment of the present application;

[0036] Figure 5 A structural schematic diagram of an electronic device provided for an embodiment of the present application. DETAILED DESCRIPTION

[0037] The principles and features of the present application are described below, and the examples are only used to explain the present application, and are not used to limit the scope of the present application.

[0038] The technical solutions of the present application and how the technical solutions of the present application solve the above technical problems will be described in detail below. The following specific embodiments can be combined with each other, and the same or similar concepts or processes can not be described again in some embodiments. The embodiments of the present application will be described below with reference to the accompanying drawings.

[0039] The scheme provided by the embodiments of the present application can be applied to any application scenario that needs to access a webpage in an application. The application scenario is in a scenario of a cloud server, a local end and an edge computing box arm end (edge end), basic data generated in the box (edge end) is interchanged with the basic data of the local end and the cloud server (cloud end), and the basic data can be uniformly processed by the cloud end.

[0040] Based on the application scenario, the embodiments of the present application provide a possible implementation manner, as shown in Figure 1 A structural schematic diagram of a multi-level data management system is provided, as shown in the schematic diagram in Figure 1 The system includes at least one edge end, at least one local end and a cloud end, each of the local ends is in communication connection with all the edge ends, and the cloud end is in communication connection with all the local ends.

[0041] For each of the edge ends, the edge end is configured to generate at least one piece of basic data, each piece of the basic data comprising a first unique identifier and a second unique identifier, the first unique identifier representing the identity of the basic data, and the second unique identifier representing the identity of the edge end to which the basic data belongs.

[0042] For each of the local ends, the local end is configured to receive at least one piece of basic data generated by at least one of the edge ends, and to classify and store all the basic data according to the second unique identifier corresponding to each piece of the basic data.

[0043] The cloud end is configured to receive all the classified basic data sent by the local ends, and to manage each piece of the classified basic data according to the first unique identifier and the second unique identifier corresponding to each piece of the classified basic data.

[0044] The system of the present application can realize efficient synchronization, accurate differentiation and effective management of data between the edge end, the local end and the cloud end through the unique identification mechanism, i.e. through the setting of the first unique identifier and the second unique identifier. The system can ensure the accuracy and integrity of data during transmission between different levels (edge end, local end and cloud end), and improve the efficiency and reliability of data management.

[0045] The technical problems to be solved by the present application and the corresponding solutions are described below in conjunction with the following specific embodiments. In this embodiment, the technical problems to be solved by the present application and the corresponding solutions are first described:

[0046] (1) Data differentiation and identification problem and corresponding solution

[0047] In a multi-level data architecture, the data generated by the edge end needs to be effectively differentiated and managed in the local end and the cloud end. Traditional data management systems cannot accurately differentiate data from different sources, resulting in data confusion and management difficulties. In the present application, the unique identification (cdKey and uuid) is introduced to realize accurate differentiation and identification of data, ensuring the uniqueness and traceability of each piece of data during transmission between different levels.

[0048] (2) Data synchronization and transmission problem and corresponding solution

[0049] In the scenario of combining edge end and cloud end, data needs to be synchronized and transmitted in real time between edge end, local end and cloud end. In the prior art, the real-time performance and reliability of data transmission cannot be guaranteed, and data loss or delay may occur. The present application realizes efficient transmission and synchronization of data through Kafka message queue, ensuring the timeliness and integrity of data between levels.

[0050] (3) Data review and feedback problem and corresponding solution

[0051] In a multi-level data management system, data auditing is an important link to ensure data quality and reliability. Traditional auditing mechanisms often lack centralized and efficient management, making it difficult to effectively audit and feedback a large amount of data. The present application centrally audits data in the cloud, and returns the audit results to the corresponding local and edge ends through the Kafka message queue, implementing an efficient data auditing and feedback mechanism to ensure the accuracy of business processes.

[0052] (4) Data isolation and security issues and corresponding solutions

[0053] On the same platform, the local and cloud need to manage the data of multiple edge ends. How to ensure the isolation and security of data of different edge ends is an important problem. The present application distinguishes the data of different edge ends by cdKey, ensures the isolation of data of the same level local and cloud, and thus improves the security and reliability of the system.

[0054] Referring to Figure 1 , based on the above technical problems and corresponding solutions, the present embodiment provides a multi-level data management system, which can specifically include at least one edge end (box) as described in Figure 1 , at least one local end (local end server) as shown in Figure 1 , and a cloud (cloud server) as shown in Figure 1 , each of the local ends is in communication connection with all edge ends, and the cloud is in communication connection with all local ends.

[0055] For each edge end, the edge end is used to generate at least one piece of basic data, each piece of basic data contains a first unique identifier and a second unique identifier, the first unique identifier represents the identity of the basic data, and the second unique identifier represents the identity of the edge end to which the basic data belongs.

[0056] Each edge end corresponds to at least one data acquisition device, such as a camera, and the data collected by the camera can be used as basic data.

[0057] Optionally, the first unique identifier can be represented by uuid as shown in Figure 1 , used to identify the uniqueness of each piece of basic data, ensuring traceability and preventing duplication of basic data in the entire system. The second unique identifier can be represented by cdKey as shown in Figure 1 , used to distinguish the basic data generated by different edge ends, ensuring data isolation in the same level. One edge end can generate at least one piece of basic data, and each piece of basic data can further include sensor data, log information, etc.

[0058] For each of the local ends, the local end is configured to receive at least one piece of basic data generated by at least one of the edge ends, and to classify and store all the basic data according to a second unique identifier corresponding to each piece of the basic data.

[0059] The local end can communicate with at least one edge end, receive basic data sent by the at least one edge end, and manage the basic data sent by the at least one edge end.

[0060] The cloud end is configured to receive all the classified basic data sent by the local ends, and to manage, such as archive, store, etc., each piece of the classified basic data according to a first unique identifier and a second unique identifier corresponding to each piece of the classified basic data.

[0061] Optionally, the plurality of local ends can synchronously transmit the respective classified basic data to the cloud end.

[0062] Optionally, for each of the local ends, the local end is further configured to periodically or in real time transmit at least one piece of the classified basic data to the cloud end.

[0063] Optionally, the cloud end is further configured to:

[0064] audit each piece of the classified basic data to obtain an audit result of each piece of the classified basic data. The audit includes, but is not limited to, legality audit, integrity audit, and business demand matching audit. For each audit result, the audit result can be in the form of pass or fail.

[0065] Optionally, the cloud end is further configured to:

[0066] transmit each of the audit results back to the corresponding local end and edge end through a Kafka message queue.

[0067] As an example, for a piece of classified basic data, if the audit result corresponding to the classified basic data is pass, the local end corresponding to the classified basic data is the local end that classifies the basic data to obtain the classified basic data, and the edge end corresponding to the classified basic data is the edge end that generates the basic data corresponding to the classified basic data. The audit result corresponding to the classified basic data is sent to the local end and the edge end corresponding to the classified basic data.

[0068] Since there are multiple pieces of classified basic data transmitted by multiple local ends in the cloud end, multiple audit results can be obtained, and each piece of the classified basic data and the corresponding audit result can form a Kafka message queue to ensure the timeliness and integrity of the data between the levels.

[0069] Optionally, the cloud is further configured to:

[0070] For each of the audit results, all the classified basic data is divided into different types of data; for example, each piece of classified basic data with an audit result of passing the audit is divided into one type, and each piece of classified basic data with an audit result of failing the audit is divided into another type.

[0071] Based on the obtained types, a third unique identifier corresponding to the basic data of each type is generated, and for each of the third unique identifiers, the third unique identifier is used to represent the type to which the corresponding basic data belongs.

[0072] The third unique identifier can be represented by a Kafka topic.

[0073] As an example, one Kafka topic is used to identify the basic data with an audit result of passing the audit, and another Kafka topic is used to identify the basic data with an audit result of failing the audit.

[0074] Optionally, all the classified basic data can also be divided into different types of data based on the business operations corresponding to each piece of classified basic data, wherein each business operation refers to the business operation corresponding to the generation of the basic data at the edge side. Then, based on the obtained types, a fourth unique identifier corresponding to the basic data of each type is generated, and for each of the fourth unique identifiers, the fourth unique identifier is used to represent the type of the business operation corresponding to the corresponding basic data.

[0075] Optionally, in the scheme of the present application, the cloud can also determine the message format corresponding to each piece of classified basic data to ensure that the edge side and the local side can correctly identify and process the returned data.

[0076] Specifically, the message content corresponding to the message format can include information such as cdKey, uuid, and audit result.

[0077] In order to better illustrate and understand the principles of the method provided by the present application, the scheme of the present application will be described below in combination with an optional specific embodiment. It should be noted that the specific implementation of each step in the specific embodiment should not be understood as a limitation on the scheme of the present application. On the basis of the principles of the scheme provided by the present application, other implementation manners that can be thought of by those skilled in the art should also be regarded as within the protection scope of the present application.

[0078] In the present embodiment, the following technical scheme is provided:

[0079] 1. For each box deployed platform (understandable as the edge described in the foregoing), there is a platform identification cdKey (second unique identification), in the deployed platform, all devices and cameras in the platform produce various data with the value of the platform identification cdKey corresponding to the platform and a unique id (uuid (first unique identification), unique in the current platform).

[0080] 2. Then the platform will determine the identity of the platform according to the identity of the deployed platform, provide all the basic data received by the local end to the cloud, or provide the basic data generated by the box to the local end, etc.

[0081] 3. For some basic information (basic data) of devices and cameras added in the platform corresponding to the box, these data can be synchronized to the corresponding superior (cloud) through the operation of "one-key synchronization" function on the platform, which can be understood as business operation, so that these superiors can see these basic information of the sub-platform. These basic information can also be edited on the platform, and the edited basic data can be synchronized back to the corresponding box through the operation of "one-key delivery" function.

[0082] 4. Actual application scenario. A device A1 is added in the box A, and 2 cameras are added under the device A1. When the camera 1 produces a personnel intrusion event, the event data produced this time is reported to the local end AA as basic data, the local end AA reports the event data to the cloud, and the local end AA and the platform in the cloud can see that the data is the event data produced by the camera 1 under the device A1 of the box A. The local end and the cloud can perform auditing and editing operations on the event data, and after considering that the event is accurate and correct, the corresponding identification can be performed on the data synchronized and delivered back to the corresponding sub-level (local end and edge).

[0083] Through the scheme of the application, the following beneficial effects are obtained:

[0084] (1) Efficient data management: cdKey and uuid are used to realize accurate differentiation and management of data at different levels, preventing data confusion.

[0085] (2) Real-time data synchronization: Kafka message queue is used to realize real-time synchronization and feedback of data between edge, local end and cloud, and improve system response speed.

[0086] (3) Perfect data auditing mechanism: data is audited in the cloud to improve data quality and reliability, and ensure the accuracy and consistency of business process.

[0087] (4) Flexible messaging: By defining different Kafka topics, flexible management of different types of data transmission and business operations can be achieved, enhancing the scalability of the system.

[0088] Based on the same principle as the system shown in Figure 1 Embodiments of the application also provide a multi-level data management method, which is applied to the local end and includes the following steps: Figure 2

[0089] S10, receiving at least one edge end sending at least one basic data, each basic data containing a first unique identifier and a second unique identifier, the first unique identifier representing the identity of the basic data, and the second unique identifier representing the identity of the edge end to which the basic data belongs;

[0090] S11, classifying and storing all basic data according to the second unique identifier corresponding to each basic data;

[0091] S12, sending each classified basic data to the cloud end, so that the cloud end manages each classified basic data according to the first unique identifier and the second unique identifier corresponding to each classified basic data.

[0092] Based on the same principle as the system shown in Figure 1 Embodiments of the application also provide a multi-level data management method, which is applied to the cloud end and includes the following steps: Figure 3

[0093] S20, receiving at least one local end sending at least one basic data classified by the local end, for each local end, the local end is used to receive at least one basic data generated by at least one edge end, and classify and store all basic data according to the second unique identifier corresponding to each basic data, each basic data containing a first unique identifier and a second unique identifier, the first unique identifier representing the identity of the basic data, and the second unique identifier representing the identity of the edge end to which the basic data belongs;

[0094] S21, managing each classified basic data according to the first unique identifier and the second unique identifier corresponding to each classified basic data.

[0095] Based on the same principle as the system shown in Figure 1 Embodiments of the application also provide a multi-level data management method, which is applied to the edge end and includes the following steps: Figure 4 ​​​

[0096] S30, generating at least one piece of basic data, each piece of the basic data comprising a first unique identifier and a second unique identifier, the first unique identifier representing an identity of the basic data, and the second unique identifier representing an identity of an edge end to which the basic data belongs;

[0097] S31, sending the at least one piece of basic data to a corresponding local end, so that the local end classifies and stores all the basic data according to the second unique identifier corresponding to each piece of the basic data, and sends each piece of the classified basic data to a cloud end, so that the cloud end manages each piece of the classified basic data according to the first unique identifier and the second unique identifier corresponding to each piece of the classified basic data.

[0098] The multi-level data management method of the embodiment of the present application has the same principle as the multi-level data management system provided by the embodiment of the present application, and the processing process has been described in the system scheme in the foregoing, which will not be repeated here.

[0099] Based on the same principle as the method shown in the embodiment of the present application, an electronic device is also provided in the embodiment of the present application, which can include but is not limited to: a processor and a memory; the memory is used to store a computer program; and the processor is used to execute the method shown in any embodiment of the present application by calling the computer program.

[0100] In an optional embodiment, an electronic device is provided, as shown in Figure 5 As shown in Figure 5 The electronic device 4000 shown in the embodiment of the present application includes a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, such as through a bus 4002. Optionally, the electronic device 4000 can also include a transceiver 4004, which can be used for data interaction between the electronic device and other electronic devices, such as data transmission and / or data reception. It should be noted that in actual application, the transceiver 4004 is not limited to one, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of the present application.

[0101] The processor 4001 can be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in connection with the present disclosure. The processor 4001 can also be a combination of computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

[0102] The bus 4002 can include a path for transmitting information between the above-mentioned components. The bus 4002 can be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, or the like. The bus 4002 can be divided into an address bus, a data bus, a control bus, and the like. For convenience of representation, Figure 5 In the figure, only one thick line is used to represent the bus, but it does not mean that there is only one bus or only one type of bus.

[0103] The memory 4003 can be a ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, a RAM (Random Access Memory) or other type of dynamic storage device that can store information and instructions, an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, an optical disk storage (including a compact disk, a laser disk, an optical disk, a digital versatile disk, a Blu-ray disk, and the like), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.

[0104] The memory 4003 is configured to store application code (computer program) for implementing the method of the present application, and the processor 4001 is configured to control the execution. The processor 4001 is configured to execute the application code stored in the memory 4003 to implement the above-mentioned method embodiments.

[0105] The electronic device can also be a terminal device, Figure 5 The electronic device shown is only an example and should not limit the function and use range of the embodiments of the present application.

[0106] The computer readable storage medium stores the computer program, and when the computer program is run on the computer, the computer can execute the corresponding content in the above-mentioned method embodiments.

[0107] According to another aspect of the present application, a computer program product or computer program is also provided, which includes computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method provided in the above various embodiment implementation manners.

[0108] The computer program code for carrying out the operations of the present application can be written in one or more programming languages or combinations thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" language or similar programming languages. The program code can be executed entirely on the user computer, partially on the user computer, as an independent software package, partially on the user computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, through the Internet using an Internet service provider).

[0109] It should be understood that the flow diagrams and block diagrams in the drawings are presented to illustrate the architecture, functionality, and operation of possible implementations of methods and computer program products according to various embodiments of the present application. In this regard, each block in the flow diagrams and block diagrams can represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical functions ("instructions"). It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks may be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flowchart illustrations, and combinations thereof, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

[0110] The computer readable storage medium of embodiments of the present application may, for example, be but is not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, the computer readable storage medium can be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0111] The computer readable storage medium described above can bear one or more programs, which, when executed by the electronic device, cause the electronic device to perform the method shown in the above embodiments.

[0112] The above description merely illustrates the preferred embodiments of the present application and the principles of the technology applied. It should be understood that the disclosed scope of the present application is not limited to the technical solutions formed by the specific combinations of the above technical features, and should also cover other technical solutions formed by any combinations of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above technical features can be replaced with the technical features disclosed in the present application (but not limited to) having similar functions to form technical solutions.

Claims

1. A multi-tiered data management system, characterized by, The system comprises at least one edge terminal, at least one local terminal and a cloud terminal, each of the local terminals is in communication connection with all the edge terminals, and the cloud terminal is in communication connection with all the local terminals. For each edge terminal, the edge terminal is configured to generate at least one piece of basic data, each piece of the basic data comprises a first unique identifier and a second unique identifier, the first unique identifier represents the identity of the basic data, and the second unique identifier represents the identity of the edge terminal to which the basic data belongs. For each local terminal, the local terminal is configured to receive at least one piece of basic data generated by at least one edge terminal, and classify and store all the basic data according to the second unique identifier corresponding to each piece of the basic data. The cloud terminal is configured to receive the classified basic data sent by all the local terminals, and manage each piece of the classified basic data according to the first unique identifier and the second unique identifier corresponding to each piece of the classified basic data. The cloud terminal is further configured to divide all the classified basic data into different types of data based on the business operation corresponding to each piece of the classified basic data, wherein each business operation refers to the business operation corresponding to the generation of the basic data at the edge terminal. Based on the types obtained by the division, a fourth unique identifier corresponding to the basic data of each type is generated, and for each fourth unique identifier, the fourth unique identifier is used to represent the type of the business operation corresponding to the corresponding basic data. The cloud terminal is further configured to determine the message format corresponding to each piece of the classified basic data. The message content corresponding to the message format comprises a cdKey, a uuid and audit result information. The first unique identifier is a uuid, and the second unique identifier is a platform identifier cdKey.

2. The system of claim 1, wherein, The cloud terminal is further configured to: audit each piece of the classified basic data to obtain an audit result of each piece of the classified basic data.

3. The system of claim 2, wherein, The cloud terminal is further configured to: return each of the audit results to the corresponding local terminal and edge terminal through a Kafka message queue.

4. The system of claim 3, wherein, The cloud terminal is further configured to: divide all the classified basic data into different types of data for each of the audit results; based on the types obtained by the division, a third unique identifier corresponding to the basic data of each type is generated, and for each third unique identifier, the third unique identifier is used to represent the type to which the corresponding basic data belongs.

5. The system of claim 1, wherein, For each local terminal, the local terminal is further configured to periodically or in real time transmit at least one piece of the classified basic data to the cloud terminal.

6. A multi-level data management method characterized by, The application is applied to a local terminal and comprises the following steps: receiving at least one piece of basic data sent by at least one edge terminal, each piece of the basic data comprising a first unique identifier and a second unique identifier, the first unique identifier representing the identity of the basic data, and the second unique identifier representing the identity of the edge terminal to which the basic data belongs; classifying and storing all the basic data according to the second unique identifier corresponding to each piece of the basic data; and The classified basic data is sent to the cloud to enable the cloud to manage the classified basic data according to the first unique identifier and the second unique identifier corresponding to each piece of classified basic data, wherein the cloud is also used to divide all classified basic data into different types of data based on the business operation corresponding to each piece of classified basic data, wherein each business operation refers to the business operation corresponding to the generation of the basic data at the edge; Based on the division of each type, a fourth unique identifier corresponding to the basic data of each type is generated, and for each fourth unique identifier, the fourth unique identifier is used to represent the type of the business operation corresponding to the corresponding basic data; The method further comprises: determining, by the cloud, a message format corresponding to each piece of classified basic data; wherein the message content corresponding to the message format includes cdKey, uuid and audit result information; The first unique identifier is uuid, and the second unique identifier is platform identifier cdKey.

7. A multi-level data management method characterized by, Applied to the cloud, comprising the following steps: Receiving at least one local end sending at least one piece of basic data classified by the local end, for each local end, the local end is used to receive at least one piece of basic data generated by the edge, and all basic data is classified and stored according to the second unique identifier corresponding to each piece of basic data, each piece of basic data contains a first unique identifier and a second unique identifier, the first unique identifier represents the identity of the basic data, and the second unique identifier represents the identity of the edge to which the basic data belongs; According to the first unique identifier and the second unique identifier corresponding to each piece of classified basic data, the classified basic data is managed; The method further comprises: based on the business operation corresponding to each piece of classified basic data, all classified basic data is divided into different types of data, wherein each business operation refers to the business operation corresponding to the generation of the basic data at the edge; Based on the division of each type, a fourth unique identifier corresponding to the basic data of each type is generated, and for each fourth unique identifier, the fourth unique identifier is used to represent the type of the business operation corresponding to the corresponding basic data; determining a message format corresponding to each piece of classified basic data; wherein the message content corresponding to the message format includes cdKey, uuid and audit result information; The first unique identifier is uuid, and the second unique identifier is platform identifier cdKey.

8. A multi-level data management method, characterized by, Applied to the edge, comprising the following steps: Generating at least one piece of basic data, each piece of basic data contains a first unique identifier and a second unique identifier, the first unique identifier represents the identity of the basic data, and the second unique identifier represents the identity of the edge to which the basic data belongs; transmitting at least one of the basic data to a corresponding local end, so that the local end classifies and stores all the basic data according to a second unique identifier corresponding to each piece of the basic data, and transmits each piece of the classified basic data to a cloud end, so that the cloud end manages each piece of the classified basic data according to a first unique identifier and the second unique identifier corresponding to each piece of the classified basic data; The cloud end is further configured to divide all the classified basic data into different types of data based on a business operation corresponding to each piece of the classified basic data, wherein each business operation refers to a business operation corresponding to the generation of the basic data at the edge end, and the cloud end is further configured to determine a message format corresponding to each piece of the classified basic data; wherein the message format corresponds to message content including a cdKey, a uuid, and audit result information. Based on the division of each type, a fourth unique identifier corresponding to each type of basic data is generated, and for each fourth unique identifier, the fourth unique identifier is used to represent the type of the business operation corresponding to the corresponding basic data. The first unique identifier is a uuid, and the second unique identifier is a platform identifier cdKey.

9. An electronic device, comprising: The computer readable storage medium stores a computer program, and the computer program is executed by the processor to implement the method in any one of claims 6 to 8.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, and the computer program is executed by the processor to implement the method in any one of claims 6 to 8.

Images