Data content tamper-proof system, method and device

Abstract

The present application discloses a data content tamper-proof system, method and device. The data content tamper-proof system includes a data storage server, which is used to generate an operation log of key data and store the operation log of the key data; the data content tamper-proof system also includes at least one collaborative server for the key data, which is used to generate an operation log of the key data and store the operation log of the key data; the data storage server is also used to read the operation log of the key data stored in the collaborative server and compare the logs when a related party of the key data updates the key data; if the operation logs are inconsistent, the collaborative server is notified that an abnormality occurs in the operation log of the key data, so as to jointly negotiate and handle the abnormality to achieve the purpose of preventing the key data from being tampered with.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a data content tamper-proofing system, method and device. Background Art

[0002] In response to operational business needs, the car factory has its own operational content data to be uploaded to the server of the operation system through the network. However, data may be tampered with during the transmission process. Although server storage can protect data to a certain extent, some data tampering is inevitable during the data migration process. These tamperings are often not discovered in time, thus affecting the stability of the operation system. Summary of the invention

[0003] Embodiments of the present application provide a data content tamper-proofing system, method, and device.

[0004] In a first aspect, an embodiment of the present application provides a data content tamper-proof system, the data content tamper-proof system comprising a data storage server, the data storage server being used to generate an operation log of key data, and to store the operation log of the key data;

[0005] The data content tamper-proof system further comprises at least one collaboration server for the key data, the collaboration server being configured to generate an operation log for the key data and store the operation log for the key data;

[0006] The data storage server is also used to read the operation log of the key data stored in the collaborative server when the first target server updates the key data, and the first target server is one of the data storage server and the collaborative server; compare whether the operation log of the key data stored in the data storage server and the operation log of the key data stored in the collaborative server are consistent; if the operation logs are inconsistent, notify the collaborative server that an abnormality has occurred in the operation log of the key data, so as to jointly negotiate and handle the abnormality.

[0007] In a second aspect, an embodiment of the present application provides a data content tamper-proof method, which is applied to a data storage server in a data content tamper-proof system, and the method further includes:

[0008] Generate an operation log of key data, and store the operation log of the key data, the data content tamper-proof system further comprising at least one collaboration server of the key data, the collaboration server storing the operation log of the key data generated by the collaboration server;

[0009] When the first target server updates the key data, reading the operation log of the key data stored in the collaboration server, the first target server being one of the data storage server and the collaboration server;

[0010] comparing whether the operation log of the key data stored in the data storage server and the operation log of the key data stored in the collaboration server are consistent;

[0011] If the operation logs are inconsistent, the collaboration server is notified that an abnormality has occurred in the operation logs of the key data, so that the collaboration server can jointly negotiate and handle the abnormality.

[0012] In a third aspect, an embodiment of the present application provides a data content tamper-proof device, which is applied to a data storage server in a data content tamper-proof system, and the device includes:

[0013] A log generation unit, configured to generate an operation log of key data and store the operation log of the key data, wherein the data content tamper-proof system further comprises at least one collaboration server of the key data, wherein the collaboration server stores the operation log of the key data generated by the collaboration server;

[0014] a log reading unit, configured to read an operation log of the key data stored in the collaboration server when the first target server updates the key data, wherein the first target server is one of the data storage server and the collaboration server;

[0015] a log comparison unit, configured to compare whether the operation log of the key data stored in the data storage server and the operation log of the key data stored in the collaboration server are consistent;

[0016] The communication unit is used to notify the collaboration server that the operation log of the key data is abnormal if the operation log is inconsistent, so as to jointly negotiate and handle the abnormal problem.

[0017] In a fourth aspect, an embodiment of the present application provides a data storage server, comprising a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, and the program includes instructions for executing the steps of any method in the second aspect of the embodiment of the present application.

[0018] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program enables a computer to execute part or all of the steps described in any method of the second aspect of the embodiment of the present application.

[0019] It can be seen that in the embodiment of the present application, the data storage server generates and stores an operation log of the key data, and at least one collaborative server of the key data also generates and stores an operation log of the key data. When a relevant party of the key data updates the key data, the data storage server reads the operation log of the key data stored by all collaborative servers of the key data, and compares the operation log of the key data stored by itself with the operation log of the key data stored by all collaborative servers to see if they are consistent. If they are inconsistent, all collaborative servers are notified that an abnormality has occurred in the operation log of the key data, so that the abnormality can be handled through joint negotiation, thereby achieving data proofreading of the two servers, thereby preventing the key data from being tampered with, and ultimately improving the stability of system operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0021] Figure 1 is a schematic diagram of a data content tamper-proof system provided in an embodiment of the present application;

[0022] Figure 2 It is a schematic diagram of an operation log of key data provided by an embodiment of the present application;

[0023] Figure 3 is a schematic diagram of an operation log after key data is updated provided by an embodiment of the present application;

[0024] Figure 4 It is a flowchart of a data content tamper-proof method provided in an embodiment of the present application;

[0025] Figure 5 It is a structural diagram of a data storage server provided in an embodiment of the present application;

[0026] Figure 6 It is a structural diagram of a data content tamper-proof device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0028] The following are detailed descriptions of each.

[0029] The terms "first", "second", "third" and "fourth" etc. in the specification and claims of the present application and the drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

[0030] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0031] See also Figure 1 , Figure 1 is a schematic diagram of a data content tamper-proof system provided in an embodiment of the present application, the data content tamper-proof system comprising a data storage server 10;

[0032] The data storage server 10 is used to generate an operation log of key data and store the operation log of the key data;

[0033] The data content tamper-proof system further comprises at least one collaborative server 20 for the critical data;

[0034] The collaboration server 20 is used to generate an operation log of the key data and store the operation log of the key data;

[0035] The data storage server 10 is further configured to read the operation log of the key data stored in the collaboration server 20 when the key data is updated by the first target server, wherein the first target server is one of the data storage server 10 and the collaboration server 20;

[0036] The data storage server 10 is further used to compare whether the operation log of the key data stored in the data storage server and the operation log of the key data stored in the collaboration server are consistent;

[0037] The data storage server 10 is also used to notify the collaboration server 20 that the operation log of the key data is abnormal if the operation log is inconsistent, so as to jointly negotiate and handle the abnormal problem to prevent the key data from being tampered with.

[0038] The collaboration server 20 includes, for example, a backend server associated with a third party, a backend server associated with a manufacturer, a cloud server associated with a user, and the like.

[0039] Among them, the key data is the sensitive data of the data storage server 10 and the collaboration server 20. For example, the sensitive data of the data storage server 10 is all the operational data stored in the data storage server 10. For another example, the assisting server is a backend server associated with a third party, and the sensitive data of the assisting server is all the subscription data during the third party subscription period. For another example, the assisting server is a backend server associated with a manufacturer, and the sensitive data of the assisting server is the operational data related to the manufacturer. For another example, the collaboration server is a cloud server associated with a user, and the sensitive data of the collaboration server is the data that the user is concerned about (such as the data uploaded by the user himself, the data subscribed by the user, etc.).

[0040] The operation log of the key data does not include the key data.

[0041] Among them, the inconsistent operation log means that at least two of the operation logs of the key data stored in the data storage server and the operation logs of the key data stored in the collaboration server are inconsistent. For example, assuming that the operation log of the key data stored in the data storage server is operation log 1, the assisting servers for the key data are assisting server 1 and assisting server 2, the operation log of the key data stored in assisting server 1 is operation log 2, and the operation log of the key data stored in assisting server 2 is operation log 3. If at least two of the operation logs 1, 2, and 3 are inconsistent, it means that the operation logs of the key data are inconsistent.

[0042] In addition, since all carriers of critical data are not terminal devices (such as smart phones, tablets, etc.), the frequency of log reading operations is not high and will not bring excessive load to the system.

[0043] Optionally, the data storage server 10 is further configured to allow the first target server to update the key data if the operation logs are consistent.

[0044] The consistency of operation logs means that the operation logs of key data stored in the data storage server and the operation logs of key data stored in the collaboration server are completely consistent. For example, assuming that the operation log of key data stored in the data storage server is operation log 1, the assistant servers of key data are assistant server 1 and assistant server 2, the operation log of key data stored in assistant server 1 is operation log 2, and the operation log of key data stored in assistant server 2 is operation log 3. If operation log 1, operation log 2 and operation log 3 are consistent, it means that the operation logs of key data are consistent.

[0045] Optionally, the operation log of the key data consists of the following information: the key data's identification, timestamp, operator identification, data stakeholder identification, data Hash, and operation content.

[0046] The data stakeholder identifier includes at least one of the following: manufacturer identifier, third-party identifier, and user identifier.

[0047] The operation log consists of the following: Figure 2 As shown, the timestamp occupies 8 bytes, the operator ID occupies 16 bytes, the data related party ID occupies 16 bytes, the data Hash occupies 128 bytes, and the operation content occupies 8 bytes.

[0048] Optionally, the sensitive characteristics of the key data include at least one of the following: manufacturer information, subscription information, the key data, and user information.

[0049] The manufacturer information includes at least one first manufacturer identifier, and the at least one first manufacturer identifier includes a manufacturer identifier associated with the collaboration server. The manufacturer identifier is, for example, a manufacturer name, or other identifier. For example, assuming that the manufacturer information includes manufacturer identifier 1, then the background server associated with manufacturer identifier 1 is the assistance server of the key data.

[0050] And / or, the subscription information includes at least one third-party identifier subscribed to the key data, and the at least one third-party identifier includes a third-party identifier associated with the collaboration server. The third-party identifier is, for example, a third-party name, or other identifier. For example, assuming that the subscription information includes a third-party identifier 1 subscribed to the key data, then the background server associated with the third-party identifier 1 is the assisting server of the key data.

[0051] And / or, the key data includes at least one data content, the at least one data content includes at least one keyword, the at least one keyword is associated with at least one manufacturer type, the at least one manufacturer type is associated with at least one second manufacturer identifier, and the at least one second manufacturer identifier includes the manufacturer identifier associated with the collaboration server. For example, assuming that the key data includes data content 1, data content 1 includes keyword 1, keyword 1 is associated with manufacturer type 1 and manufacturer type 2, manufacturer type 1 is associated with manufacturer identifier 1 and manufacturer identifier 2, and manufacturer type 2 is associated with manufacturer identifier 3, then the background server associated with manufacturer identifier 1, manufacturer identifier 2, and manufacturer identifier 3 is the assisting server of the key data.

[0052] And / or, the user information includes at least one user identifier, and the at least one user identifier includes a user identifier associated with the collaboration server. The user identifier is, for example, a user name, an account, or other identifier. For example, assuming that the user information includes user identifier 1, then the cloud server associated with user identifier 1 is the assisting server for the key data.

[0053] In an implementation of the present application, the identifier of the operation log of the key data is generated based on the identifier of the key data;

[0054] The identifier of the operation log of the key data stored in the data maintenance server is consistent with the identifier of the operation log of the key data stored in the collaboration server.

[0055] The identifier of the operation log of the key data includes the identifier of the key data. For example, assuming that the identifier of the key data is New Baojun RM5 Album, the identifier of the operation log of the key data may be New Baojun RM5 Album-201109 Operation Log.

[0056] Alternatively, the identifier of the operation log of the key data includes information associated with the identifier of the key data. The information associated with the identifier of the key data includes a number corresponding to the identifier of the key data. For example, the identifier of the key data is the new Baojun RM5 album. If the number corresponding to the identifier "new Baojun RM5 album" is 11111, then the identifier of the operation log of the key data can be the 11111-201109 operation log.

[0057] It can be seen that in this embodiment, the identification of the operation log is unified, which can facilitate the data storage server to quickly read the operation log of key data.

[0058] In an implementation of the present application, the first target server is used to update the operation log of the key data after the key data is updated, and send the update information of the operation log to the second target server, so that the second target server synchronously updates the operation log of the key data;

[0059] The second target server is a server in the data storage server 10 and the collaboration server 20 except the first target server.

[0060] The update information of the operation log includes at least one of the following: timestamp, operator identification, data stakeholder identification, data hash, and operation content.

[0061] For example, assuming that the update information of the operation log is timestamp 1, operator ID 1, data stakeholder ID 1, data Hash 1, and operation content 1, if the previous operation log is Figure 2 As shown, the updated operation log is as follows Figure 3 shown.

[0062] It can be seen that in this embodiment, when the operation log of a party related to the key data is updated, other parties related to the key data are notified to update the operation log of the key data in time to ensure the stability of system operation.

[0063] See also Figure 4 , Figure 4 It is a flow chart of a data content tamper-proofing method provided in an embodiment of the present application, which is applied to a data storage server in a data content tamper-proofing system. The data content tamper-proofing method includes the following steps.

[0064] Step 410: The data storage server generates an operation log of key data, and stores the operation log of the key data. The data content anti-tampering system also includes at least one collaborative server for the key data, and the collaborative server stores the operation log of the key data generated by the collaborative server.

[0065] Step 420: When the first target server updates the key data, the data storage server reads the operation log of the key data stored in the collaboration server, and the first target server is one of the data storage server and the collaboration server.

[0066] Step 430: The data storage server compares the operation log of the key data stored in the data storage server and the operation log of the key data stored in the collaboration server to see whether they are consistent.

[0067] Step 440: If the operation logs are inconsistent, the data storage server notifies the collaboration server that an abnormality has occurred in the operation logs of the key data, so that the collaboration server can jointly negotiate to resolve the abnormality.

[0068] Optionally, the method further comprises:

[0069] If the operation logs are consistent, the data storage server allows the first target server to update the key data.

[0070] It can be seen that in the embodiment of the present application, when the operation log of key data is inconsistent, all collaborative servers are notified that the operation log of the key data is abnormal, so that they can jointly negotiate to handle the abnormal problem, thereby preventing the key data from being tampered with, and ultimately improving the stability of system operation.

[0071] Optionally, the operation log of the key data consists of the following information: the key data's identification, timestamp, operator identification, data stakeholder identification, data Hash, and operation content.

[0072] Optionally, the sensitive characteristics of the key data include at least one of the following: manufacturer information, subscription information, the key data, and user information;

[0073] The manufacturer information includes at least one first manufacturer identifier, and the at least one first manufacturer identifier includes a manufacturer identifier associated with the collaboration server;

[0074] And / or, the subscription information includes at least one third-party identifier subscribing to the key data, and the at least one third-party identifier includes a third-party identifier associated with the collaboration server;

[0075] And / or, the key data includes at least one data content, the at least one data content includes at least one keyword, the at least one keyword is associated with at least one manufacturer type, the at least one manufacturer type is associated with at least one second manufacturer identifier, and the at least one second manufacturer identifier includes a manufacturer identifier associated with the collaboration server;

[0076] And / or, the user information includes at least one user identifier, and the at least one user identifier includes a user identifier associated with the collaboration server.

[0077] Optionally, the identifier of the operation log of the key data is generated based on the identifier of the key data;

[0078] The identifier of the operation log of the key data stored in the data maintenance server is consistent with the identifier of the operation log of the key data stored in the collaboration server.

[0079] In one implementation of the present application, the method further includes:

[0080] After the key data is updated, the data storage server updates the operation log of the key data and sends the update information of the operation log to the second target server, so that the second target server synchronously updates the operation log of the key data, and the second target server is the collaborative server.

[0081] It should be noted that the specific implementation of this embodiment refers to the specific implementation described in the above system and will not be described again here.

[0082] See also Figure 5 , Figure 5 1 is a structural diagram of a data storage server provided in an embodiment of the present application. As shown in the figure, the data storage server includes a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, and the program includes instructions for executing the following steps:

[0083] Generate an operation log of key data, and store the operation log of the key data, the data content tamper-proof system further comprising at least one collaboration server of the key data, the collaboration server storing the operation log of the key data generated by the collaboration server;

[0084] When the first target server updates the key data, reading the operation log of the key data stored in the collaboration server, the first target server being one of the data storage server and the collaboration server;

[0085] comparing whether the operation log of the key data stored in the data storage server and the operation log of the key data stored in the collaboration server are consistent;

[0086] If the operation logs are inconsistent, the collaboration server is notified that an abnormality has occurred in the operation logs of the key data, so that the collaboration server can jointly negotiate and handle the abnormality.

[0087] Optionally, the program includes instructions for executing the following steps:

[0088] If the operation logs are consistent, the first target server is allowed to update the key data.

[0089] Optionally, the operation log of the key data consists of the following information: the key data's identification, timestamp, operator identification, data stakeholder identification, data Hash, and operation content.

[0090] Optionally, the sensitive characteristics of the key data include at least one of the following: manufacturer information, subscription information, the key data, and user information;

[0091] The manufacturer information includes at least one first manufacturer identifier, and the at least one first manufacturer identifier includes a manufacturer identifier associated with the collaboration server;

[0092] And / or, the subscription information includes at least one third-party identifier subscribing to the key data, and the at least one third-party identifier includes a third-party identifier associated with the collaboration server;

[0093] And / or, the key data includes at least one data content, the at least one data content includes at least one keyword, the at least one keyword is associated with at least one manufacturer type, the at least one manufacturer type is associated with at least one second manufacturer identifier, and the at least one second manufacturer identifier includes a manufacturer identifier associated with the collaboration server;

[0094] And / or, the user information includes at least one user identifier, and the at least one user identifier includes a user identifier associated with the collaboration server.

[0095] Optionally, the identifier of the operation log of the key data is generated based on the identifier of the key data;

[0096] The identifier of the operation log of the key data stored in the data maintenance server is consistent with the identifier of the operation log of the key data stored in the collaboration server.

[0097] In one implementation of the present application, the above program includes instructions for further executing the following steps:

[0098] After the key data is updated, the operation log of the key data is updated, and the update information of the operation log is sent to the second target server, so that the second target server synchronously updates the operation log of the key data, and the second target server is the collaborative server.

[0099] It should be noted that the specific implementation of this embodiment refers to the specific implementation described in the above system and will not be described again here.

[0100] See also Figure 6 , Figure 61 is a schematic diagram of the structure of a data content tamper-proof device provided in an embodiment of the present application, which is applied to a data storage server in a data content tamper-proof system, and the device includes:

[0101] A log generation unit 610, configured to generate an operation log of key data and store the operation log of the key data, wherein the data content tamper-proof system further comprises at least one collaboration server of the key data, and the collaboration server stores the operation log of the key data generated by the collaboration server;

[0102] A log reading unit 620, configured to read an operation log of the key data stored in the collaboration server when the first target server updates the key data, wherein the first target server is one of the data storage server and the collaboration server;

[0103] A log comparison unit 630 is used to compare whether the operation log of the key data stored in the data storage server and the operation log of the key data stored in the collaboration server are consistent;

[0104] The communication unit 640 is used to notify the collaboration server that the operation log of the key data is abnormal if the operation log is inconsistent, so as to jointly negotiate and handle the abnormal problem.

[0105] Optionally, the device further comprises:

[0106] The processing unit 650 is configured to allow the first target server to update the key data if the operation logs are consistent.

[0107] Optionally, the operation log of the key data consists of the following information: the key data's identification, timestamp, operator identification, data stakeholder identification, data Hash, and operation content.

[0108] Optionally, the sensitive characteristics of the key data include at least one of the following: manufacturer information, subscription information, the key data, and user information;

[0109] The manufacturer information includes at least one first manufacturer identifier, and the at least one first manufacturer identifier includes a manufacturer identifier associated with the collaboration server;

[0110] And / or, the subscription information includes at least one third-party identifier subscribing to the key data, and the at least one third-party identifier includes a third-party identifier associated with the collaboration server;

[0111] And / or, the key data includes at least one data content, the at least one data content includes at least one keyword, the at least one keyword is associated with at least one manufacturer type, the at least one manufacturer type is associated with at least one second manufacturer identifier, and the at least one second manufacturer identifier includes a manufacturer identifier associated with the collaboration server;

[0112] And / or, the user information includes at least one user identifier, and the at least one user identifier includes a user identifier associated with the collaboration server.

[0113] Optionally, the identifier of the operation log of the key data is generated based on the identifier of the key data;

[0114] The identifier of the operation log of the key data stored in the data maintenance server is consistent with the identifier of the operation log of the key data stored in the collaboration server.

[0115] In one implementation of the present application, the device further includes:

[0116] The processing unit 650 is also used to update the operation log of the key data after the key data is updated, and send the update information of the operation log to the second target server so that the second target server synchronously updates the operation log of the key data. The second target server is the collaborative server.

[0117] It should be noted that the log generating unit 610, the log reading unit 620, the log comparing unit 630 and the processing unit 650 may be implemented by a processor, and the communication unit 640 may be implemented by a communication interface.

[0118] An embodiment of the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program enables a computer to execute part or all of the steps described in the data storage server in the above method embodiment.

[0119] The steps of the method or algorithm described in the embodiment of the present application can be implemented in a hardware manner, or can be implemented by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory (Random Access Memory, RAM), a flash memory, a read-only memory (Read Only Memory, ROM), an erasable programmable read-only memory (Erasable Programmable ROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), a register, a hard disk, a mobile hard disk, a read-only compact disk (CD-ROM) or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in an access network device, a target network device, or a core network device. Of course, the processor and the storage medium can also be present in an access network device, a target network device, or a core network device as discrete components.

[0120] Those skilled in the art should be aware that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiments of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0121] The specific implementation methods described above further illustrate the purpose, technical solutions and beneficial effects of the embodiments of the present application. It should be understood that the above description is only the specific implementation method of the embodiments of the present application and is not intended to limit the protection scope of the embodiments of the present application. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the embodiments of the present application should be included in the protection scope of the embodiments of the present application.

Claims

1. A data content tamper-proof system, characterized in that: The data content tamper-proof system comprises a data storage server, wherein the data storage server is used to generate an operation log of key data and store the operation log of the key data; The data content tamper-proof system further comprises at least one collaborative server for the key data, the collaborative server being used to generate an operation log of the key data and store the operation log of the key data, wherein the key data is sensitive data of the data storage server and sensitive data of the collaborative server, the collaborative server comprises a backend server associated with a third party or a backend server associated with a manufacturer or a cloud server associated with a user, the sensitive data of the data storage server is all operational data stored in the data storage server, when the collaborative server is a backend server associated with the third party, the sensitive data of the collaborative server comprises all subscription data during the subscription period of the third party, when the collaborative server is a backend server associated with the manufacturer, the sensitive data of the collaborative server comprises operational data related to the manufacturer, when the collaborative server is a cloud server associated with the user, the sensitive data of the collaborative server comprises data concerned by the user; The data storage server is further configured to read the operation log of the key data stored in the collaboration server when the first target server updates the key data, wherein the first target server is one of the data storage server and the collaboration server; Compare whether the operation logs of the key data stored in the data storage server and the operation logs of the key data stored in the collaborative server are consistent; if the operation logs are inconsistent, notify the collaborative server that an abnormality has occurred in the operation log of the key data, so as to jointly negotiate and deal with the abnormality, wherein the data storage server is also used to allow the first target server to update the key data if the operation logs are consistent; the first target server is used to update the operation log of the key data after the key data is updated, and send the update information of the operation log to the second target server, so that the second target server synchronously updates the operation log of the key data; wherein the second target server is a server other than the first target server among the data storage server and the collaborative server.

2. The system according to claim 1, characterized in that The operation log of the key data consists of the following information: the key data's identification, timestamp, operator identification, data stakeholder identification, data Hash, and operation content.

3. The system according to claim 1 or 2, characterized in that: The sensitive characteristics of the key data include at least one of the following: manufacturer information, subscription information, and user information; The manufacturer information includes at least one first manufacturer identifier, and the at least one first manufacturer identifier includes a manufacturer identifier associated with the collaboration server; And / or, the subscription information includes at least one third-party identifier subscribing to the key data, and the at least one third-party identifier includes a third-party identifier associated with the collaboration server; And / or, the user information includes at least one user identifier, and the at least one user identifier includes a user identifier associated with the collaboration server.

4. The system according to claim 3, characterized in that The identifier of the operation log of the key data is generated based on the identifier of the key data; The identifier of the operation log of the key data stored in the data storage server is consistent with the identifier of the operation log of the key data stored in the collaboration server.

5. A data content tamper-proof method, characterized in that: The method is applied to a data storage server in a data content tamper-proof system, and further comprises: Generate an operation log of key data, and store the operation log of the key data, the data content tamper-proof system also includes at least one collaboration server for the key data, the collaboration server stores the operation log of the key data generated by the collaboration server, wherein the key data is sensitive data of the data storage server and sensitive data of the collaboration server, the collaboration server includes a backend server associated with a third party or a backend server associated with a manufacturer or a cloud server associated with a user, the sensitive data of the data storage server is all operational data stored in the data storage server, when the collaboration server is a backend server associated with the third party, the sensitive data of the collaboration server includes all subscription data during the third party subscription period, when the collaboration server is a backend server associated with the manufacturer, the sensitive data of the collaboration server includes operational data related to the manufacturer, when the collaboration server is a cloud server associated with the user, the sensitive data of the collaboration server includes data of concern to the user; When the first target server updates the key data, reading the operation log of the key data stored in the collaboration server, the first target server being one of the data storage server and the collaboration server; comparing whether the operation log of the key data stored in the data storage server and the operation log of the key data stored in the collaboration server are consistent; If the operation logs are inconsistent, the collaborative server is notified that an abnormality has occurred in the operation log of the key data, so as to jointly negotiate and handle the abnormality; if the operation logs are consistent, the first target server is allowed to update the key data; and, after the key data is updated, the operation log of the key data is updated, and the update information of the operation log is sent to the second target server, so that the second target server synchronously updates the operation log of the key data, and the second target server is the collaborative server.

6. The method according to claim 5, characterized in that The operation log of the key data consists of the following information: the key data's identification, timestamp, operator identification, data stakeholder identification, data Hash, and operation content.

7. The method according to claim 5 or 6, characterized in that: The sensitive characteristics of the key data include at least one of the following: manufacturer information, subscription information, and user information; The manufacturer information includes at least one first manufacturer identifier, and the at least one first manufacturer identifier includes a manufacturer identifier associated with the collaboration server; And / or, the subscription information includes at least one third-party identifier subscribing to the key data, and the at least one third-party identifier includes a third-party identifier associated with the collaboration server; And / or, the user information includes at least one user identifier, and the at least one user identifier includes a user identifier associated with the collaboration server.

8. The method according to claim 7, characterized in that The identifier of the operation log of the key data is generated based on the identifier of the key data; The identifier of the operation log of the key data stored in the data storage server is consistent with the identifier of the operation log of the key data stored in the collaboration server.

9. A data content tamper-proof device, characterized in that: A data storage server used in a data content tamper-proof system, the device comprising: a log generation unit, configured to generate an operation log of key data and store the operation log of the key data; the data content tamper-proof system further comprising at least one collaboration server for the key data; the collaboration server storing the operation log of the key data generated by the collaboration server; wherein the key data is sensitive data of the data storage server and sensitive data of the collaboration server; the collaboration server comprises a backend server associated with a third party or a backend server associated with a manufacturer or a cloud server associated with a user; the sensitive data of the data storage server is all operational data stored in the data storage server; when the collaboration server is a backend server associated with a third party, the sensitive data of the collaboration server comprises all subscription data during the subscription period of the third party; when the collaboration server is a backend server associated with a manufacturer, the sensitive data of the collaboration server comprises operational data related to the manufacturer; and when the collaboration server is a cloud server associated with a user, the sensitive data of the collaboration server comprises data of interest to the user; a log reading unit, configured to read an operation log of the key data stored in the collaboration server when the first target server updates the key data, wherein the first target server is one of the data storage server and the collaboration server; a log comparison unit, configured to compare whether the operation log of the key data stored in the data storage server and the operation log of the key data stored in the collaboration server are consistent; A communication unit is used to notify the collaborative server that an abnormality occurs in the operation log of the key data if the operation logs are inconsistent, so as to jointly negotiate and handle the abnormality problem; if the operation logs are consistent, allow the first target server to update the key data; and, after the key data is updated, update the operation log of the key data and send the update information of the operation log to the second target server, so that the second target server synchronously updates the operation log of the key data, and the second target server is the collaborative server.

10. A computer-readable storage medium, characterized in that: A computer program for electronic data exchange is stored, wherein the computer program enables a computer to execute the method according to any one of claims 5 to 8.

Images