A data backtracking verification method and device

Abstract

The present application provides a data retrospective verification method and device, which relates to the technical field of data inspection and verification. During verification, the method generates a unique and tamper-proof data label for the proof data through the extended information and proof elements of the proof data determined by the proof-provider, stores the data label in the proof-depositing party, and the proof-acquired party obtains the target data label from the proof-depositing party in response to the retrospective verification request of the data, and then verifies the data according to the target data label, providing a more reliable and efficient data verification solution for MIME and S / MIME application scenarios such as mail systems and file transfers; and, because the verification is performed through data labels, storage resources are effectively saved, the security of data content is enhanced, and the efficiency of verification response is improved.

Description

Technical Field

[0001] The present application relates to the technical field of data inspection and verification, and in particular to a method and device for retrospective verification of data. Background Art

[0002] With the in-depth development of informatization, the email system and its derivative systems under the technical standard system, as key platforms for carrying important data, are increasingly widely used. These systems have not only gained wide recognition of their legal status worldwide, but have also become the core medium for promoting data interaction. In the context of digital transformation in various fields, more and more data interaction behaviors are generated. Within the application system, data interaction is used to realize data processing between components within the system; between various application systems or devices, cross-system or cross-device collaboration is realized through data interaction; between various organizations, cross-organizational business collaboration is realized through data interaction.

[0003] The data standard of email is MIME (Multipurpose Internet Mail Extensions), which is mainly based on the specifications of RFC 2045 (MIME message body structure definition specification), RFC 2046 (MIME media type definition specification), and RFC 2047 (non-ASCII mail header encoding definition specification). It was originally used to define and represent the format type of email attachment files, and now it has been widely used in various scenarios involving data interaction on the Internet, such as specifying web page content types in HTTP (HyperText Transfer Protocol) transmission, specifying data transmission formats in WebServices (network services), specifying request and response data formats in API (Application Programming Interface) communication, and limiting file types when application systems upload files. Here, ASCII is a character encoding standard used for text exchange between computers, communication equipment and other electronic devices. Based on MIME, S / MIME (Secure / Multipurpose Internet Mail Extensions) was also developed. By combining MIME with PKI (Public Key Infrastructure) technology, data encryption and signing are achieved, thereby improving the security of data interaction.

[0004] The two typical features of email data standards are data encapsulation and data exchange, which are not only reflected in the server-to-server and server-to-client application scenarios of email systems, but also applied to instant messaging systems based on MIME encapsulated data exchange. Given the universality of such data interaction, the ability to store, trace, and verify such data and interaction is becoming increasingly important. Therefore, this technical problem needs to be solved urgently. Summary of the invention

[0005] In view of the above problems, this application is proposed to provide a data retrospective verification method and device that overcomes the above problems or at least partially solves the above problems. The technical solution is as follows:

[0006] In a first aspect, a method for backtracking and verifying data is provided, wherein the data is encapsulated based on the MIME standard or the S / MIME standard, and the method comprises:

[0007] Predefine the roles of providing evidence, storing evidence and obtaining evidence, wherein the role of providing evidence includes one or more parties providing evidence;

[0008] For any one of the one or more proof providers, the proof provider provides proof data, and determines the extended information and proof elements based on the proof data, and then combines the extended information and the proof elements to generate a unique data tag for the proof data, and submits the data tag to the proof depositor corresponding to the proof depositor role, and the proof depositor stores the data tag; wherein the proof elements include a complete data fingerprint value and / or a segmented data fingerprint value obtained by calculating the proof data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard;

[0009] The certified party corresponding to the certified role responds to the data retrospective verification request, and according to the verification conditions in the data retrospective verification request, queries one or more data tags stored by the certification party to obtain the target data tag, and then obtains the verification result based on one or more of the extended information of the target data tag, the complete data fingerprint value, and the segmented data fingerprint value.

[0010] In a possible implementation, the extended information includes time, identity and behavior;

[0011] Behavior is the operation of exiting, entering, holding, or discarding the proof data;

[0012] The identity is a value that uniquely identifies the identity of the operator who performs the operation of exiting, entering, holding, or discarding the certification data;

[0013] Time is the time value of the unique data tag that generates the proof data.

[0014] In a possible implementation, if the certification data provided by the certification provider is an outgoing operation on the certification data, the extended information also includes a data recipient.

[0015] In a possible implementation, if the certification data provided by the certification provider is an entry operation for the certification data, the extended information also includes the data source.

[0016] In a possible implementation, the method further includes:

[0017] For the set fingerprint elements, the party providing evidence traverses the data or fingerprint library held by the party providing evidence. If there is current data that matches the set fingerprint elements, the extended information of the current data is determined based on the matched current data; the extended information of the current data and the set fingerprint elements are combined to generate a unique data label for the current data, and the data label is submitted to the evidence storing party corresponding to the evidence storing role, and the evidence storing party stores the data label.

[0018] In a possible implementation, if the data backtracking verification request includes a request to confirm that the first certification data entered by the first certification party comes from the second certification party;

[0019] The certified party corresponding to the certified role responds to the data backtracking verification request, queries one or more data tags stored by the evidence depositor to obtain the target data tag according to the verification conditions in the data backtracking verification request, and then obtains the verification result according to one or more of the extended information of the target data tag, the complete data fingerprint value, and the segmented data fingerprint value, including:

[0020] The certified party corresponding to the certified role responds to a request for confirmation that the first certification data entered by the first certification party comes from the second certification party, and calculates the first certification data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the first certification data;

[0021] The party obtaining the certificate searches for at least one first data label that matches the complete data fingerprint value and / or the segmented data fingerprint value of the first proof data among the one or more data labels stored by the party storing the certificate;

[0022] Determining whether the identity of the extended information of at least one first data tag includes the second evidence providing party;

[0023] If the identity of the extended information of at least one first data tag includes the second proving party, determine whether the data recipient of the extended information of at least one first data tag includes the first proving party; if so, confirm that the first proof data entered by the first proving party comes from the second proving party; if not, confirm that the first proof data entered by the first proving party does not come from the second proving party;

[0024] If the identity of the extended information of at least one first data tag does not include the second certifying party, it is confirmed that the first certification data entered by the first certifying party does not come from the second certifying party.

[0025] In a possible implementation, if the request for backtracking verification of data includes a request for the second proof data of the first proving party to be out is sent to the third proving party for verification;

[0026] The certified party corresponding to the certified role responds to the data backtracking verification request, queries one or more data tags stored by the evidence depositor to obtain the target data tag according to the verification conditions in the data backtracking verification request, and then obtains the verification result according to one or more of the extended information of the target data tag, the complete data fingerprint value, and the segmented data fingerprint value, including:

[0027] The certified party corresponding to the certified role responds to the request for the second certification data of the first certification party to be sent to the third certification party for verification, and calculates the second certification data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the second certification data;

[0028] The party obtaining the certificate searches for at least one second data tag matching the complete data fingerprint value and / or the segmented data fingerprint value of the second proof data from the one or more data tags stored by the party storing the certificate;

[0029] Determine whether the identity of the extended information of at least one second data tag includes the first party providing evidence, whether the behavior of the extended information of at least one second data tag is data out, and whether the data recipient is the third party providing evidence;

[0030] If the identity of the extended information of at least one second data tag includes the first proving party, and the behavior of the extended information of at least one second data tag is data out, and the data recipient is the third proving party, it is determined that the second proof data of the first proving party out is sent to the third proving party;

[0031] If the identity of the extended information of at least one second data tag does not include the first certifying party, or the behavior of the extended information of at least one second data tag is not data out, it is determined that the first certifying party has not out the second certification data.

[0032] In one possible implementation, if the request for retrospective verification of data includes a request to verify that the first party providing proof holds or discards the third proof data;

[0033] The certified party corresponding to the certified role responds to the data backtracking verification request, queries one or more data tags stored by the evidence depositor to obtain the target data tag according to the verification conditions in the data backtracking verification request, and then obtains the verification result according to one or more of the extended information of the target data tag, the complete data fingerprint value, and the segmented data fingerprint value, including:

[0034] The certified party corresponding to the certified role responds to the request for verifying whether the first certification party holds or discards the third certification data, and calculates the third certification data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the third certification data;

[0035] The party obtaining the certificate searches for at least one third data tag matching the complete data fingerprint value and / or the segmented data fingerprint value of the third proof data from the one or more data tags stored by the party storing the certificate;

[0036] Determining whether the identity of the extended information of at least one third data tag includes the first evidence providing party;

[0037] If the identity of the extended information of at least one third data tag includes the first proving party, then checking the behavior of the extended information of at least one third data tag; if the behavior of the extended information of at least one third data tag is data discarding, then determining that the first proving party discards the third proof data; if the behavior of the extended information of at least one third data tag is data holding, then determining that the first proving party holds the third proof data;

[0038] If the identity of the extended information of at least one third data tag does not include the first certifying party, it is determined that the first certifying party does not hold or discard the third certification data.

[0039] In a possible implementation, if the data retrospective verification request includes a verification request of whether the fourth data held by the first certifying party is earlier than the fourth data held by the second certifying party;

[0040] The certified party corresponding to the certified role responds to the data backtracking verification request, queries one or more data tags stored by the evidence depositor to obtain the target data tag according to the verification conditions in the data backtracking verification request, and then obtains the verification result according to one or more of the extended information of the target data tag, the complete data fingerprint value, and the segmented data fingerprint value, including:

[0041] The certified party corresponding to the certified role responds to a verification request of whether the fourth data held by the first certified party is earlier than the fourth data held by the second certified party, and calculates the fourth certification data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the fourth certification data;

[0042] The party obtaining the evidence searches for a fourth data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the fourth proof data and whose identity is the first party providing the evidence, and searches for a fifth data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the fourth proof data and whose identity is the second party providing the evidence, from one or more data tags stored by the party storing the evidence;

[0043] If the time of the extended information of the fourth data tag is earlier than the time of the extended information of the fifth data tag, it is determined that the fourth data held by the first provider is published earlier than the fourth data held by the second provider.

[0044] In a second aspect, a data retrospective verification device is provided, wherein the data is encapsulated based on the MIME standard or the S / MIME standard, and the device includes:

[0045] A definition module, used to predefine the role of providing evidence, the role of storing evidence and the role of obtaining evidence, wherein the role of providing evidence includes one or more parties providing evidence;

[0046] Any one of the one or more attestation providers is used to provide attestation data, determine extended information and attestation elements based on the attestation data, and then combine the extended information and attestation elements to generate a unique data tag for the attestation data, and submit the data tag to the attestation provider corresponding to the attestation role; wherein the attestation elements include a complete data fingerprint value and / or a segmented data fingerprint value obtained by calculating the attestation data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard;

[0047] The evidence storage party is used to store one or more data tags;

[0048] The certified party corresponding to the certified role is used to respond to the data retrospective verification request, and according to the verification conditions in the data retrospective verification request, query and obtain the target data tag from one or more data tags stored by the certification party, and then obtain the verification result according to one or more of the extended information of the target data tag, the complete data fingerprint value, and the segmented data fingerprint value.

[0049] In a possible implementation, the extended information includes time, identity and behavior;

[0050] Behavior is the operation of exiting, entering, holding, or discarding the proof data;

[0051] The identity is a value that uniquely identifies the identity of the operator who performs the operation of exiting, entering, holding, or discarding the certification data;

[0052] Time is the time value of the unique data tag that generates the proof data.

[0053] In a possible implementation, if the certification data provided by the certification provider is an outgoing operation on the certification data, the extended information also includes a data recipient.

[0054] In a possible implementation, if the certification data provided by the certification provider is an entry operation for the certification data, the extended information also includes the data source.

[0055] In a possible implementation, the evidence provider is also used to:

[0056] For the set fingerprint elements, traverse the data or fingerprint library held by the evidence provider. If there is current data that matches the set fingerprint elements, determine the extended information of the current data based on the matched current data; combine the extended information of the current data and the set fingerprint elements to generate a unique data label for the current data, submit the data label to the evidence storing party corresponding to the evidence storing role, and the evidence storing party will store the data label.

[0057] In a possible implementation, if the data backtracking verification request includes a request to confirm that the first certification data entered by the first certification party comes from the second certification party; the certification party is further configured to:

[0058] In response to a request for confirmation that the first proof data entered by the first proof provider comes from the second proof provider, a preset digest algorithm is used in combination with the MIME standard or the S / MIME standard to calculate the first proof data to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the first proof data;

[0059] Searching for at least one first data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the first proof data among the one or more data tags stored by the evidence depositor;

[0060] Determining whether the identity of the extended information of at least one first data tag includes the second evidence providing party;

[0061] If the identity of the extended information of at least one first data tag includes the second proving party, determine whether the data recipient of the extended information of at least one first data tag includes the first proving party; if so, confirm that the first proof data entered by the first proving party comes from the second proving party; if not, confirm that the first proof data entered by the first proving party does not come from the second proving party;

[0062] If the identity of the extended information of at least one first data tag does not include the second certifying party, it is confirmed that the first certification data entered by the first certifying party does not come from the second certifying party.

[0063] In a possible implementation, if the data backtracking verification request includes a request for the second proof data of the first proof provider to be sent to the third proof provider for verification; the proof recipient is further configured to:

[0064] In response to a request that the second proof data issued by the first proof provider be sent to a third proof provider for verification, the second proof data is calculated using a preset digest algorithm in combination with the MIME standard or the S / MIME standard to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the second proof data;

[0065] Searching for at least one second data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the second proof data among the one or more data tags stored by the evidence depositor;

[0066] Determine whether the identity of the extended information of at least one second data tag includes the first party providing evidence, whether the behavior of the extended information of at least one second data tag is data out, and whether the data recipient is the third party providing evidence;

[0067] If the identity of the extended information of at least one second data tag includes the first proving party, and the behavior of the extended information of at least one second data tag is data out, and the data recipient is the third proving party, it is determined that the second proof data of the first proving party out is sent to the third proving party;

[0068] If the identity of the extended information of at least one second data tag does not include the first certifying party, or the behavior of the extended information of at least one second data tag is not data out, it is determined that the first certifying party has not out the second certification data.

[0069] In a possible implementation, if the data retrospective verification request includes a request to verify whether the first certification party holds or discards the third certification data; the certification party is further configured to:

[0070] In response to a request to verify whether the first party providing proof holds or discards the third proof data, a preset digest algorithm is used in combination with the MIME standard or the S / MIME standard to calculate the third proof data to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the third proof data;

[0071] Searching for at least one third data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the third proof data among the one or more data tags stored by the evidence depositor;

[0072] Determining whether the identity of the extended information of at least one third data tag includes the first evidence providing party;

[0073] If the identity of the extended information of at least one third data tag includes the first proving party, then checking the behavior of the extended information of at least one third data tag; if the behavior of the extended information of at least one third data tag is data discarding, then determining that the first proving party discards the third proof data; if the behavior of the extended information of at least one third data tag is data holding, then determining that the first proving party holds the third proof data;

[0074] If the identity of the extended information of at least one third data tag does not include the first certifying party, it is determined that the first certifying party does not hold or discard the third certification data.

[0075] In a possible implementation, if the data retrospective verification request includes a verification request of whether the fourth data held by the first verification provider is earlier than the fourth data held by the second verification provider; the verification recipient is further configured to:

[0076] In response to a verification request of whether the fourth data held by the first proof provider is earlier than the fourth data held by the second proof provider, a preset digest algorithm is used in combination with the MIME standard or the S / MIME standard to calculate the fourth proof data to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the fourth proof data;

[0077] Searching for a fourth data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the fourth proof data and whose identity is the first party providing proof, and searching for a fifth data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the fourth proof data and whose identity is the second party providing proof, from one or more data tags stored by the proof depositor;

[0078] If the time of the extended information of the fourth data tag is earlier than the time of the extended information of the fifth data tag, it is determined that the fourth data held by the first provider is published earlier than the fourth data held by the second provider.

[0079] By means of the above technical scheme, the data retrospective verification method and device provided in the embodiment of the present application, during verification, the method generates a unique and tamper-proof data label for the proof data through the extended information and proof elements of the proof data determined by the party providing the proof, and stores the data label in the proof depository, and the party obtaining the proof obtains the target data label from the proof depository in response to the retrospective verification request for the data, and then verifies the data according to the target data label, thereby providing a more reliable and efficient data verification solution for MIME and S / MIME application scenarios such as mail systems and file transfers; and, since the verification is performed through the data label, storage resources are effectively saved, the security of the data content is enhanced, and the efficiency of the verification response is improved; in addition, the data label is stored in the proof depository, and the party obtaining the proof obtains the target data label from the proof depository, and then verifies the data according to the target data label, thereby enhancing the traceability of the data and avoiding the complexity of PKI management.

[0080] Furthermore, the extended information of the data tag includes time, identity and behavior. That is to say, the data tag records the operations of exiting, entering, holding or discarding the proof data, as well as the identity of the operator who performs the exiting, entering, holding or discarding operations on the proof data. In this way, the proof depositor is responsible for storing these data tags, realizing the logical decoupling of data status change records and the proof provider, so as to be able to flexibly respond to various data flow scenarios; in the data verification link, the proof recipient can quickly access the data tags involved in each stage of the entire process from the generation to the disappearance of specific data (including exiting, entering, holding, and discarding) from the proof depositor. This feature fundamentally changes the perspective of verification at the traditional business level, and instead goes deep into the micro level of data status changes, greatly enhancing the security, traceability and accuracy of the data flow process, and providing more effective data protection and verification efficiency for MIME and S / MIME application scenarios such as email systems and file transfers. BRIEF DESCRIPTION OF THE DRAWINGS

[0081] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in describing the embodiments of the present application are briefly introduced below.

[0082] Figure 1 It is a flow chart of the data retrospective verification method provided in the embodiment of the present application;

[0083] Figure 2 It is a relationship structure diagram of the role of providing evidence, the role of storing evidence and the role of obtaining evidence provided in the embodiment of the present application;

[0084] Figure 3 It is a structural diagram of the data retrospective verification device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0085] The exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present application and to fully convey the scope of the present application to those skilled in the art.

[0086] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that such use is interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the term "including" and its variants are to be interpreted as open-ended terms meaning "including but not limited to".

[0087] In order to solve the above technical problems, the embodiment of the present application provides a data retrospective verification method, where the data is encapsulated based on the MIME standard or the S / MIME standard, such as Figure 1 As shown, the data retrospective verification method may include the following steps S101 to S103:

[0088] Step S101, pre-defining the role of providing evidence, the role of storing evidence and the role of obtaining evidence, wherein the role of providing evidence includes one or more parties providing evidence;

[0089] Step S102: for any one of the one or more evidence providers, the evidence provider provides evidence data, and determines the extended information and the evidence elements according to the evidence data, and then combines the extended information and the evidence elements to generate a unique data tag for the evidence data, and submits the data tag to the evidence depositor corresponding to the evidence depositor role, and the evidence depositor stores the data tag; wherein the evidence elements include the complete data fingerprint value and / or the segmented data fingerprint value obtained by calculating the evidence data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard;

[0090] In step S103, the certified party corresponding to the certified role responds to the data retrospective verification request, queries one or more data tags stored by the certification party to obtain the target data tag according to the verification conditions in the data retrospective verification request, and then obtains the verification result according to one or more of the extended information of the target data tag, the complete data fingerprint value, and the segmented data fingerprint value.

[0091] During verification, this embodiment generates a unique and tamper-proof data label for the proof data through the extended information and proof elements of the proof data determined by the party providing the proof, and stores the data label in the proof depository. The party obtaining the proof obtains the target data label from the proof depository in response to the data backtracking verification request, and then verifies the data according to the target data label, thereby providing a more reliable and efficient data verification solution for MIME and S / MIME application scenarios such as email systems and file transfers. Furthermore, since the verification is performed through the data label, storage resources are effectively saved, the security of the data content is enhanced, and the efficiency of the verification response is improved. In addition, the data label is stored in the proof depository, and the party obtaining the proof obtains the target data label from the proof depository, and then verifies the data according to the target data label, thereby enhancing the traceability of the data and avoiding the complexity of PKI management.

[0092] In the above step S102, the proof data provided by the proof provider is encapsulated based on the MIME standard or the S / MIME standard, so that different MIME types and corresponding data contents in the proof data can be obtained based on the MIME standard or the S / MIME standard, and then a preset digest algorithm can be used in combination with the MIME standard or the S / MIME standard to calculate the complete data content of the proof data to obtain a complete data fingerprint value, and a preset digest algorithm can be used in combination with the MIME standard or the S / MIME standard to calculate the data content of different MIME types of the proof data to obtain segmented data fingerprint values ​​corresponding to different MIME types.

[0093] Here, MIME types are used to define the format of data in emails, web pages, or other Internet documents. MIME types consist of two parts: type and subtype, which are separated by a slash ( / ). The type defines the general category of data, while the subtype provides more specific information.

[0094] Here are some examples of common MIME types and their subtypes:

[0095] (1) “text / ” indicates text data.

[0096] "text / plain" means ordinary text files, such as TXT (Text) files.

[0097] "text / html" indicates an HTML (HyperText Markup Language) document.

[0098] (2) “image / ” indicates image data.

[0099] "image / jpeg" indicates an image in the JPEG (Joint Photographic Experts Group) format.

[0100] "image / png" indicates an image in the PNG (Portable Network Graphics) format.

[0101] "image / gif" indicates an image in the GIF (Graphics Interchange Format) format.

[0102] (3) “audio / ” indicates audio data.

[0103] "audio / mpeg" indicates MPEG (Moving Pictures Experts Group) audio, such as MP3 files.

[0104] "audio / wav" indicates a WAV (Waveform Audio File Format) audio file.

[0105] (4) “video / ” indicates video data.

[0106] "video / mp4" indicates an MP4 video file.

[0107] (5) "application / " indicates binary data, usually used for application programs.

[0108] "application / json" indicates JSON (JavaScript Object Notation, a lightweight data exchange format) data.

[0109] "application / octet-stream", a generic type for unknown binary data.

[0110] (6) "multipart / ", a composite type used to combine multiple different types of data.

[0111] "multipart / form-data" is used for submitting form data, such as uploading files.

[0112] "multipart / byteranges", used to represent multiple parts of a document.

[0113] It should be noted that the above examples are merely illustrative and do not limit this embodiment.

[0114] The preset digest algorithm here can be MD5 (Message Digest Algorithm), SHA (Secure Hash Algorithm)-1, SHA-2, SHA-128, SHA-256, and a custom algorithm, etc., which is not limited in this embodiment.

[0115] A possible implementation method is provided in an embodiment of the present application. The extended information mentioned in step S102 above may include time, identity and behavior; the behavior here is the operation of exiting, entering, holding or discarding the proof data; the identity is a value that uniquely identifies the identity of the operator who performs the operation of exiting, entering, holding or discarding the proof data; and the time is the time value of the unique data tag generated for the proof data.

[0116] The party providing evidence corresponding to the role of providing evidence can provide the data label of the evidence data to the party storing evidence corresponding to the role of storing evidence through network protocols such as HTTP, FTP (File Transfer Protocol), etc., or storage media such as hard disk or USB (Universal Serial Bus), etc. The party storing evidence stores the data label in a retrievable manner (such as database, file system, directory, etc.). The data label stored by the party storing evidence involves four data states, namely data out, data in, data held, and data discarded.

[0117] Here, the act of proving that data enters the provider is data entry; the act of proving that data is sent from the provider or obtained to the outside is data exit; the act of proving that data is owned by the provider is data holding; the act of proving that data is not owned by the provider is data non-holding; and the act of proving that data is removed from the provider is data discard.

[0118] Figure 2 It is a relationship structure diagram of the witnessing role, evidence storing role and evidence obtaining role provided in the embodiment of the present application. The witnessing role may include one or more witnessing parties (for example, witnessing party A1, AN, etc., N is a positive integer). Any of the one or more witnessing parties can serve as a provider of proof data.

[0119] The evidence storage role may also include one or more evidence storage parties (such as evidence storage parties M1, MN, etc.). The evidence storage party, as the storage party of the data tag, may exist in any party of the data exchange or may be independent of any party of the data exchange. This embodiment does not limit this.

[0120] The certified role may also include one or more certified parties (such as certified parties B1, BN, etc.). The certified party may be various business software, client software, servers, gateways, mail routing devices, management and control systems that query, hold, exchange, manage, control, and flow MIME, S / MIME encapsulated data, data status and behavior, or any system that stores, transmits or processes this data. It may also be an organization, entity, and personnel role, etc. This embodiment does not limit this.

[0121] During verification, the evidence depositor provides the data label to the party obtaining the evidence. The party obtaining the evidence can also query the relevant data labels through searchable fields (such as complete data fingerprint value, segmented data fingerprint value, identity, behavior, etc.), and obtain the target data label. The verification result can be obtained based on one or more of the identity, behavior, date, complete data fingerprint value, and segmented data fingerprint value of the target data label.

[0122] A possible implementation method is provided in the embodiment of the present application. In the above step S102, if the proof data provided by the proof provider is an operation to eliminate the proof data, the extended information may also include the data recipient, or may also include the data source, thereby establishing a relationship chain between the proof providers, thereby forming a clear and verifiable data transmission behavior chain or data state evolution chain.

[0123] A possible implementation method is provided in an embodiment of the present application. In the above step S102, if the party providing the proof data provides the proof data for an entry operation, the extended information may also include the data source, and a relationship chain may also be established between the parties providing the proof, thereby forming a clear and verifiable data transmission behavior chain or data state evolution chain.

[0124] A possible implementation method is provided in an embodiment of the present application. In addition to the three required fields of time, identity and behavior, the extended information may also include the data recipient or data source. In addition, one or more fields may be expanded according to actual conditions, such as data size, data encryption level, etc., which is not limited in this embodiment.

[0125] The above step S102 specifically introduces a method for storing the certification data provided by any one of the one or more certification parties. In a possible implementation, the method for storing the set fingerprint element may include the following step a1:

[0126] In step a1, the party providing evidence traverses the data or fingerprint library held by the party providing evidence. If there is current data that matches the set fingerprint element, the extended information of the current data is determined based on the matched current data; the extended information of the current data and the set fingerprint element are combined to generate a unique data tag for the current data, and the data tag is submitted to the evidence storing party corresponding to the evidence storing role, and the evidence storing party stores the data tag.

[0127] In this step, the fingerprint element may be provided by the party providing the evidence, or may exist independently, for example, it may be obtained by querying the system of the party storing the evidence, or an existing fingerprint may be obtained from other channels, and this embodiment does not impose any limitation on this.

[0128] For the data held by the party providing the evidence, a preset summary algorithm can be used in combination with the MIME standard or the S / MIME standard to calculate the data held by the party providing the evidence to obtain a complete data fingerprint value and / or a segmented data fingerprint value; the complete data fingerprint value and / or the segmented data fingerprint value of the data held by the party providing the evidence are traversed, and if there is a complete data fingerprint value or a segmented data fingerprint value that matches the set fingerprint element, the data corresponding to the complete data fingerprint value or the segmented data fingerprint value that matches the set fingerprint element is used as the current data that matches the set fingerprint element.

[0129] The fingerprint database held by the party providing the evidence can be traversed, and if there is a fingerprint matching the set fingerprint element, the data corresponding to the fingerprint matching the set fingerprint element is used as the current data matching the set fingerprint element.

[0130] It should be noted that the set fingerprint elements are also obtained by calculating the set data using a preset summary algorithm.

[0131] In the embodiment of the present application, a possible implementation method is provided. If the data retrospective verification request in step S103 includes a request to confirm that the first proof data entered by the first proof provider comes from the second proof provider, then in step S103, the certified party corresponding to the certified role responds to the data retrospective verification request, and queries one or more data tags stored by the proof storing party to obtain the target data tag according to the verification conditions in the data retrospective verification request, and then obtains the verification result according to one or more of the extended information of the target data tag, the complete data fingerprint value, and the segmented data fingerprint value. Specifically, the following steps b1 to b5 may be included:

[0132] Step b1, the certified party corresponding to the certified role responds to a request for confirmation that the first certification data entered by the first certification party comes from the second certification party, and calculates the first certification data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the first certification data;

[0133] Step b2, the party obtaining the certificate searches for at least one first data label that matches the complete data fingerprint value and / or the segmented data fingerprint value of the first proof data among the one or more data labels stored by the party storing the certificate;

[0134] Step b3, determining whether the identity of the extended information of at least one first data tag includes the second evidence providing party;

[0135] Step b4, if the identity of the extended information of at least one first data tag includes the second proving party, determine whether the data recipient of the extended information of at least one first data tag includes the first proving party, if so, confirm that the first proof data entered by the first proving party comes from the second proving party; if not, confirm that the first proof data entered by the first proving party does not come from the second proving party;

[0136] Step b5: If the identity of the extended information of at least one first data tag does not include the second certifying party, it is confirmed that the first certification data entered by the first certifying party does not come from the second certifying party.

[0137] This embodiment can safely, accurately and efficiently confirm and verify that the first certification data entered by the first certification party comes from the second certification party.

[0138] In an embodiment of the present application, a possible implementation method is provided. If the data retrospective verification request in step S103 includes a request that the second proof data of the first proof provider be eliminated is sent to the third proof provider for verification, then in step S103, the certified party corresponding to the certified role responds to the data retrospective verification request, and according to the verification conditions in the data retrospective verification request, queries one or more data tags stored by the proof storing party to obtain the target data tag, and then obtains the verification result according to one or more of the extended information of the target data tag, the complete data fingerprint value, and the segmented data fingerprint value. Specifically, the following steps c1 to c5 may be included:

[0139] Step c1, the certified party corresponding to the certified role responds to the request that the second certification data of the first certification party be sent to the third certification party for verification, and calculates the second certification data using a preset digest algorithm and in combination with the MIME standard or the S / MIME standard to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the second certification data;

[0140] Step c2, the party obtaining the certificate searches for at least one second data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the second proof data in one or more data tags stored by the party storing the certificate;

[0141] Step c3, determining whether the identity of the extended information of at least one second data tag includes the first party providing evidence, whether the behavior of the extended information of at least one second data tag is data out, and whether the data recipient is the third party providing evidence;

[0142] Step c4, if the identity of the extended information of at least one second data tag includes the first certifying party, and the behavior of the extended information of at least one second data tag is data out, and the data recipient is the third certifying party, then determine that the second certification data of the first certifying party out is sent to the third certifying party;

[0143] Step c5: if the identity of the extended information of at least one second data tag does not include the first certifying party, or the behavior of the extended information of at least one second data tag is not data out, it is determined that the first certifying party has not out the second certification data.

[0144] This embodiment can safely, accurately and efficiently send the second certification data of the first certification party to the third certification party for verification.

[0145] In an embodiment of the present application, a possible implementation method is provided. If the data retrospective verification request in step S103 includes a request to verify whether the first proof providing party holds or discards the third proof data, then in step S103, the certified party corresponding to the certified role responds to the data retrospective verification request, and queries one or more data tags stored by the proof storing party to obtain the target data tag according to the verification conditions in the data retrospective verification request, and then obtains the verification result according to one or more of the extended information of the target data tag, the complete data fingerprint value, and the segmented data fingerprint value. Specifically, the following steps d1 to d5 may be included:

[0146] Step d1, the certified party corresponding to the certified role responds to the request for verifying whether the first certification party holds or discards the third certification data, and calculates the third certification data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the third certification data;

[0147] Step d2, the party obtaining the certificate searches for at least one third data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the third proof data among the one or more data tags stored by the party storing the certificate;

[0148] Step d3, determining whether the identity of the extended information of at least one third data tag includes the first party providing evidence;

[0149] Step d4, if the identity of the extended information of at least one third data tag includes the first proving party, then check the behavior of the extended information of at least one third data tag; if the behavior of the extended information of at least one third data tag is data discarding, then determine that the first proving party discards the third proof data; if the behavior of the extended information of at least one third data tag is data holding, then determine that the first proving party holds the third proof data;

[0150] Step d5: If the identity of the extended information of at least one third data tag does not include the first certifying party, it is determined that the first certifying party does not hold or discard the third certification data.

[0151] This embodiment can safely, accurately and efficiently verify whether the first party providing proof holds or discards the third proof data.

[0152] In an embodiment of the present application, a possible implementation method is provided. If the data retrospective verification request in step S103 includes a verification request for whether the fourth data held by the first evidence provider is published earlier than the fourth data held by the second evidence provider, then in step S103, the certified party corresponding to the certified role responds to the data retrospective verification request, and queries one or more data tags stored by the evidence depositor to obtain the target data tag according to the verification conditions in the data retrospective verification request, and then obtains the verification result according to one or more of the extended information of the target data tag, the complete data fingerprint value, and the segmented data fingerprint value. Specifically, the following steps e1 to e3 may be included:

[0153] Step e1, the certified party corresponding to the certified role responds to the verification request of whether the fourth data held by the first certified party is earlier than the fourth data held by the second certified party, and calculates the fourth certification data by using a preset digest algorithm and combining the MIME standard or the S / MIME standard to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the fourth certification data;

[0154] Step e2, the evidence-obtaining party searches for a fourth data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the fourth proof data and whose identity is the first evidence-providing party, and searches for a fifth data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the fourth proof data and whose identity is the second evidence-providing party, from one or more data tags stored by the evidence-depositing party;

[0155] Step e3: if the time of the extended information of the fourth data tag is earlier than the time of the extended information of the fifth data tag, it is determined that the fourth data held by the first certification party is published earlier than the fourth data held by the second certification party.

[0156] This embodiment can safely, accurately and efficiently verify whether the fourth data held by the first certifying party is earlier than the fourth data held by the second certifying party.

[0157] The witness role may include one or more witnesses, such as witness 1, witness 2, witness 3, witness 4... witness N, where N is a positive integer. The first witness, the second witness, and the third witness mentioned in the above embodiment are only illustrative, and do not specifically refer to the first witness as witness 1, the second witness as witness 2, and the third witness as witness 3; in actual application scenarios, the first witness may be witness 1, witness 2, witness 3, or witness N, the second witness may be a witness other than the first witness, and the third witness may be a witness other than the first witness and the second witness.

[0158] For example, in a scenario where the data backtracking verification request includes a request to confirm that the first proof data entered by the first certifying party comes from the second certifying party, the first certifying party may be certifying party 2 and the second certifying party may be certifying party 4.

[0159] In a scenario where the data retrospective verification request includes a verification request of whether the fourth data held by the first provider is published earlier than the fourth data held by the second provider, the first provider may be provider 1 and the second provider may be provider 3.

[0160] It should be noted that the above examples are merely illustrative and do not limit the present embodiment.

[0161] The above introduces Figure 1 There are multiple implementation methods for each link of the illustrated embodiment. The data backtracking verification method of the embodiment of the present application will be further explained below through specific embodiments.

[0162] Scenario example 1: The witness A1 corresponding to the witness role sends a MIME message M (such as an email) to A2, and A2 automatically obtains the original data of the message.

[0163] The email data in MIME format is as follows:

[0164] X-ANY-EXTHEADER:

[0165] Reply-To:"=?gbk?B?wfW24MC8?="<xxx@anymacro.com>

[0166] X-Send-Id:1723099968.ac7a1910355639c6904e2993cc20809814719

[0167] From:"-?gbk?B?wfW24MC8?="<xxx@anymacro.com>

[0168] Date:Thu,08 Aug 2024 14:52:45 +0800(CST)

[0169] MIME-version: 1.0

[0170] X-srcuser:xxx@anymacro.com

[0171] X-ANYWEBIP:IP_K

[0172] To:"=?utf-8?b?546L5YW16bKB?="<aaaaa@anymacro.com>

[0173] Subject:=?gbk?B?d2Fzbc / gudjWqsq2tKKxuA==?=

[0174] Content-Type:multipart / mixed;

[0175] boundary="14719.66b46b402b468.8ffc5632c87b09bc.anymacro"

[0176] --14719.66b46b402b468.8ffc5632c87b09bc.anymacro

[0177] Content-Type:text / html;charset=gbk

[0178] Content-Transfer-Encoding:base64

[0179] zfW5pLrDo708ZG12PixzcGFuIHN0eWx1PST3aG10ZS1zcGF iZTpwcmUiPgk8L3NwYW4+uL28 / srHd2Fzbc / gudilxNaqyra0orG4xNrI3aGjPC9kaXY+

[0180] --14719.66b46b402b468.8ffc5632c87b09bc.anymacro

[0181] Content-Type:application / octet-stream;name="=?gbk?B?d2Fzbdagyra0orG4LmRvY3g=?="

[0182] Content-Transfer-Encoding:base64

[0183] Content-Disposition:attachment;filename="=?gbk?B?d2Fzbdagyra0orG4LmRvY3g=?="

[0184] In the above MIME-formatted email data, X-ANY-EXTHEADER is a non-standard email header, usually used in specific email systems or applications; the Reply-To field specifies the address to which the reply should be sent. The address here is "xxx@anymacro.com", but it uses the Base64 (a method of encoding binary data based on 64 printable characters) format encoded in GBK (a Chinese character encoding standard); X-Send-Id is the unique identifier generated when the email is sent; From is the sender's email address, which is also "xxx@anymacro.com" and uses the Base64 format encoded in GBK; Date is the date and time the email is sent; MIME-version is the identifier of the MIME version followed by the email; X-srcuser is the email address of the sending user; X-ANYWEBIP is the network IP (Internet Protocol) used when sending the email Protocol, IP_K is schematic and is not limited in this embodiment; To is the recipient's email address, using the UTF-8 encoded Base64 format; Subject is the subject of the email, using the GBK encoded Base64 format; Content-Type specifies the type of email content, which is multipart / mixed here, meaning that the email contains multiple parts; boundary is a boundary marker used to separate different parts of the email.

[0185] The email content is divided into two parts: the first part is of type text / html, which contains text content in HTML format. The text is encoded in Base64 format, and the decoded content is HTML code. The second part is of type application / octet-stream, which is used to send binary files. The file name is specified here (Base64 format with GBK encoding), and the content is also Base64 encoded, which means that the email contains an attachment, and the specific content of the attachment needs to be decoded before it can be viewed.

[0186] For the witness A1, the preset digest algorithm can be used to encrypt the complete original data to obtain the complete data fingerprint value H1; the original data consists of two MIME types, and it is necessary to obtain each MIME type and encrypt the data of each MIME type to obtain the segmented data fingerprint values ​​H2 and H3 respectively; based on the original data, extended information is generated, including time, identity (a value that can uniquely identify the witness A1), behavior (data out), and data receiver A2, and the complete data fingerprint value H1, the segmented data fingerprints H2, H3 and the extended information are combined to generate a data label, and then the witness M1 stores the generated data label.

[0187] The data tags of the MIME-formatted mail data are as follows:

[0188] Complete data: complete data fingerprint value H1;

[0189] Segmented data:

[0190] 1) MIME type (text / html) and data content, segmented data fingerprint H2;

[0191] 2) MIME type (application / octet-stream) and data content, segmented data fingerprint H3;

[0192] Additional information:

[0193] 1) Time, the time value of the generated data label, which can be Thu,08 Aug 2024 14:52:45 +0800(CST);

[0194] 2) Identity, sender xxx@anymacro.com;

[0195] 3) Behavior, sending emails, and data out;

[0196] 4) Data recipient: recipient aaaaa@anymacro.com.

[0197] For the evidence provider A2, after receiving the message M, the data tag of the message M is stored, and the evidence storing party M1 stores the generated data tag.

[0198] If the certifying party A2 needs to verify the confirmation of the certifying party A1's behavior, the certified party B1 corresponding to the certified role can obtain the complete data fingerprint value H1 in the data tag generated by the certifying party A2, and retrieve at least one data tag consistent with H1 in the evidence storage party M1, and compare whether the identity in at least one data tag includes the certifying party A1, and whether the data recipient includes the certifying party A2; if the identity in at least one data tag includes the certifying party A1, and the data recipient includes the certifying party A2, the behavior confirmation verification is passed, and the verification process does not need to rely on PKI, and does not need to verify the validity of the digital certificate.

[0199] Scenario Example 2: All historical data held by the proving parties A1 and A2 have been stored in the evidence depository. A1 and A2 both publish an original painting in the form of a MIME message. After comparison, the two original paintings are 70% similar. A1 and A2 each have their own opinions and need to determine which work was created earlier. The certified party B1 intervenes and obtains the data tags D(1) and D(2) formed when the two works were first created from the evidence depository M1. After comparing the time in D(1) and the time in D(2), it can be determined that the creation time of A2's work is later than that of A1's work.

[0200] Scenario example three: All held and discarded data in the evidence provider A has been stored in the evidence depository M. The company where the evidence provider A is located needs to delete specific data regularly. The evidence recipient B needs to periodically verify whether these specific data are deleted within the specified time. During the verification, the evidence recipient B obtains the data label D when the file is discarded or deleted from the evidence depository M, and checks whether the time in the extended information of the data label D is within the specified time limit.

[0201] Scenario Example 4: In the data exchange scenario, business system (provider) A1 and business system (provider) A2 realize data interoperability through interactive interfaces. System A1 is responsible for encapsulating the files to be archived in the form of MIME messages, and calls the interface of system A2 through interactive protocols for data transmission. After obtaining these encapsulated data, system A2 performs storage processing. The data exchange behaviors between A1 and A2 have been stored in the evidence storage party M.

[0202] Recently, an abnormal situation was discovered: the data file that the A1 system claimed to have submitted to the A2 system was inconsistent with the storage of the A2 system, and the backtracking search process became complicated and difficult. In order to solve this problem, this solution introduces the certified party B, who is responsible for obtaining the data label D(A1) generated when the A1 system sends a request and the data label D(A2) generated when the A2 system stores data from the certified party M. D(A1) and D(A2) contain key information such as the timestamp of data exchange and the complete data fingerprint value, which are used to verify the accuracy of the data. By comparing the complete data fingerprint values ​​in D(A1) and D(A2), the certified party B confirmed whether the data was tampered with during the transmission process. At the same time, by comparing the timestamps, B found that the time in D(A1) was earlier than the time in D(A2), which proved that the A1 system did send data to the A2 system at the specified time. By further analyzing the identity, data recipient, and data source of the extended information in D(A1) and D(A2), B can confirm whether the data received and stored by the A2 system is consistent with the original data sent by the A1 system, thereby solving the problem of data inconsistency and clarifying the responsibility.

[0203] This embodiment provides more effective data protection and verification efficiency for MIME and S / MIME application scenarios such as email systems and file transfers, fully meeting the strict requirements in areas such as legal compliance, historical record retention, and security auditing.

[0204] It should be noted that the size of the sequence number of each step in the above embodiment does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. In practical applications, all the above possible implementation methods can be combined in any way to form possible embodiments of the present application, which will not be described one by one here.

[0205] Based on the data retrospective verification methods provided in the above embodiments and based on the same inventive concept, an embodiment of the present application also provides a data retrospective verification device.

[0206] Figure 3 is a structural diagram of the data retrospective verification device provided in the embodiment of the present application. Figure 3 As shown, the data retrospective verification device may specifically include a definition module, any one of the one or more certification parties, a certification storing party, and a certification party corresponding to the certification role.

[0207] A definition module, used to predefine the role of providing evidence, the role of storing evidence and the role of obtaining evidence, wherein the role of providing evidence includes one or more parties providing evidence;

[0208] Any one of the one or more attestation providers is used to provide attestation data, determine extended information and attestation elements based on the attestation data, and then combine the extended information and attestation elements to generate a unique data tag for the attestation data, and submit the data tag to the attestation provider corresponding to the attestation role; wherein the attestation elements include a complete data fingerprint value and / or a segmented data fingerprint value obtained by calculating the attestation data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard;

[0209] The evidence storage party is used to store one or more data tags;

[0210] The certified party corresponding to the certified role is used to respond to the data retrospective verification request, and according to the verification conditions in the data retrospective verification request, query and obtain the target data tag from one or more data tags stored by the certification party, and then obtain the verification result according to one or more of the extended information of the target data tag, the complete data fingerprint value, and the segmented data fingerprint value.

[0211] A possible implementation method is provided in an embodiment of the present application, wherein the extended information includes time, identity and behavior;

[0212] Behavior is the operation of exiting, entering, holding, or discarding the proof data;

[0213] The identity is a value that uniquely identifies the identity of the operator who performs the operation of exiting, entering, holding, or discarding the certification data;

[0214] Time is the time value of the unique data tag that generates the proof data.

[0215] A possible implementation method is provided in an embodiment of the present application. If the party providing the proof data provides an outgoing operation on the proof data, the extended information also includes a data recipient.

[0216] A possible implementation method is provided in an embodiment of the present application. If the party providing the proof data provides the proof data for entry, the extended information also includes the data source.

[0217] A possible implementation method is provided in an embodiment of the present application, and the evidence provider is also used to:

[0218] For the set fingerprint elements, traverse the data or fingerprint library held by the evidence provider. If there is current data that matches the set fingerprint elements, determine the extended information of the current data based on the matched current data; combine the extended information of the current data and the set fingerprint elements to generate a unique data label for the current data, submit the data label to the evidence storing party corresponding to the evidence storing role, and the evidence storing party will store the data label.

[0219] In an embodiment of the present application, a possible implementation method is provided. If the data retrospective verification request includes a request to confirm that the first proof data entered by the first proof provider comes from the second proof provider; the certificate recipient is further configured to:

[0220] In response to a request for confirmation that the first proof data entered by the first proof provider comes from the second proof provider, a preset digest algorithm is used in combination with the MIME standard or the S / MIME standard to calculate the first proof data to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the first proof data;

[0221] Searching for at least one first data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the first proof data among the one or more data tags stored by the evidence depositor;

[0222] Determining whether the identity of the extended information of at least one first data tag includes the second evidence providing party;

[0223] If the identity of the extended information of at least one first data tag includes the second proving party, determine whether the data recipient of the extended information of at least one first data tag includes the first proving party; if so, confirm that the first proof data entered by the first proving party comes from the second proving party; if not, confirm that the first proof data entered by the first proving party does not come from the second proving party;

[0224] If the identity of the extended information of at least one first data tag does not include the second certifying party, it is confirmed that the first certification data entered by the first certifying party does not come from the second certifying party.

[0225] In an embodiment of the present application, a possible implementation method is provided. If the data retrospective verification request includes a request for the second proof data of the first proof provider to be eliminated, the proof data is sent to the third proof provider for verification; the proof recipient is also used to:

[0226] In response to a request that the second proof data issued by the first proof provider be sent to a third proof provider for verification, the second proof data is calculated using a preset digest algorithm in combination with the MIME standard or the S / MIME standard to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the second proof data;

[0227] Searching for at least one second data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the second proof data among the one or more data tags stored by the evidence depositor;

[0228] Determine whether the identity of the extended information of at least one second data tag includes the first party providing evidence, whether the behavior of the extended information of at least one second data tag is data out, and whether the data recipient is the third party providing evidence;

[0229] If the identity of the extended information of at least one second data tag includes the first proving party, and the behavior of the extended information of at least one second data tag is data out, and the data recipient is the third proving party, it is determined that the second proof data of the first proving party out is sent to the third proving party;

[0230] If the identity of the extended information of at least one second data tag does not include the first certifying party, or the behavior of the extended information of at least one second data tag is not data out, it is determined that the first certifying party has not out the second certification data.

[0231] In an embodiment of the present application, a possible implementation method is provided. If the data retrospective verification request includes a request to verify whether the first proof provider holds or discards the third proof data; the proof recipient is further configured to:

[0232] In response to a request to verify whether the first party providing proof holds or discards the third proof data, a preset digest algorithm is used in combination with the MIME standard or the S / MIME standard to calculate the third proof data to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the third proof data;

[0233] Searching for at least one third data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the third proof data among the one or more data tags stored by the evidence depositor;

[0234] Determining whether the identity of the extended information of at least one third data tag includes the first evidence providing party;

[0235] If the identity of the extended information of at least one third data tag includes the first proving party, then checking the behavior of the extended information of at least one third data tag; if the behavior of the extended information of at least one third data tag is data discarding, then determining that the first proving party discards the third proof data; if the behavior of the extended information of at least one third data tag is data holding, then determining that the first proving party holds the third proof data;

[0236] If the identity of the extended information of at least one third data tag does not include the first certifying party, it is determined that the first certifying party does not hold or discard the third certification data.

[0237] In an embodiment of the present application, a possible implementation method is provided. If the data retrospective verification request includes a verification request of whether the fourth data held by the first certification party is earlier than the fourth data held by the second certification party; the certification party is further configured to:

[0238] In response to a verification request of whether the fourth data held by the first proof provider is earlier than the fourth data held by the second proof provider, a preset digest algorithm is used in combination with the MIME standard or the S / MIME standard to calculate the fourth proof data to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the fourth proof data;

[0239] Searching for a fourth data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the fourth proof data and whose identity is the first party providing proof, and searching for a fifth data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the fourth proof data and whose identity is the second party providing proof, from one or more data tags stored by the proof depositor;

[0240] If the time of the extended information of the fourth data tag is earlier than the time of the extended information of the fifth data tag, it is determined that the fourth data held by the first provider is published earlier than the fourth data held by the second provider.

[0241] Based on the same inventive concept, an embodiment of the present application also provides an electronic device, including a processor and a memory, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the data backtracking verification method of any one of the above embodiments.

[0242] Based on the same inventive concept, an embodiment of the present application further provides a storage medium, in which a computer program is stored, wherein the computer program is configured to execute the data backtracking verification method of any one of the above embodiments when running.

[0243] Those skilled in the art can clearly understand that the specific working processes of the systems, devices, and modules described above can refer to the corresponding processes in the aforementioned method embodiments, and for the sake of brevity, they are not further described here.

[0244] Those skilled in the art can understand that the technical solution of the present application can be essentially or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, which includes a number of program instructions, so that an electronic device (such as a personal computer, a server, or a network device, etc.) executes all or part of the steps of the method described in each embodiment of the present application when running the program instructions. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc., various media that can store program codes.

[0245] Alternatively, all or part of the steps of implementing the aforementioned method embodiments may be accomplished by hardware associated with program instructions (such as electronic devices such as personal computers, servers, or network devices), and the program instructions may be stored in a computer-readable storage medium. When the program instructions are executed by a processor of an electronic device, the electronic device executes all or part of the steps of the methods described in the embodiments of the present application.

[0246] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that within the spirit and principles of the present application, they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not deviate from the protection scope of the present application.

Claims

1. A data retrospective verification method, characterized in that: The data is encapsulated based on the MIME standard or the S / MIME standard, and the method includes: Predefine the roles of providing evidence, storing evidence and obtaining evidence, wherein the role of providing evidence includes one or more parties providing evidence; For any one of the one or more proof providers, the proof provider provides proof data, and determines the extended information and proof elements based on the proof data, and then combines the extended information and the proof elements to generate a unique data tag for the proof data, and submits the data tag to the proof depositor corresponding to the proof depositor role, and the proof depositor stores the data tag; wherein the proof elements include a complete data fingerprint value and / or a segmented data fingerprint value obtained by calculating the proof data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard; The certified party corresponding to the certified role responds to the data retrospective verification request, calculates the data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard, obtains the complete data fingerprint value and / or the segmented data fingerprint value of the data, searches for a target data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the data from one or more data tags stored by the certified party, and then obtains the verification result according to the extended information of the target data tag; Wherein, the extended information includes time, identity and behavior; Behavior is the operation of exiting, entering, holding, or discarding the proof data; The identity is a value that uniquely identifies the identity of the operator who performs the operation of exiting, entering, holding, or discarding the certification data; Time is the time value of the unique data tag that generates the proof data.

2. The method according to claim 1, characterized in that If the certification data provided by the certification party is an operation to remove the certification data, the extended information also includes a data recipient; If the certification data provided by the certification party is an entry operation for the certification data, the extended information also includes the data source party.

3. The method according to claim 1, characterized in that The method further comprises: For the set fingerprint elements, the party providing evidence traverses the data or fingerprint library held by the party providing evidence. If there is current data that matches the set fingerprint elements, the extended information of the current data is determined based on the matched current data; the extended information of the current data and the set fingerprint elements are combined to generate a unique data label for the current data, and the data label is submitted to the evidence storing party corresponding to the evidence storing role, and the evidence storing party stores the data label.

4. The method according to claim 2, characterized in that: If the request for data retrospective verification includes a request to confirm that the first certification data entered by the first certification party comes from the second certification party; The certified party corresponding to the certified role responds to the data retrospective verification request, calculates the data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard, obtains the complete data fingerprint value and / or the segmented data fingerprint value of the data, queries one or more data tags stored by the evidence depositor to obtain a target data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the data, and then obtains the verification result according to the extended information of the target data tag, including: The certified party corresponding to the certified role responds to a request for confirmation that the first certification data entered by the first certification party comes from the second certification party, and calculates the first certification data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the first certification data; The party obtaining the certificate searches for at least one first data label that matches the complete data fingerprint value and / or the segmented data fingerprint value of the first proof data among the one or more data labels stored by the party storing the certificate; Determining whether the identity of the extended information of at least one first data tag includes the second evidence providing party; If the identity of the extended information of at least one first data tag includes the second proving party, determine whether the data recipient of the extended information of at least one first data tag includes the first proving party; if so, confirm that the first proof data entered by the first proving party comes from the second proving party; if not, confirm that the first proof data entered by the first proving party does not come from the second proving party; If the identity of at least one of the extended information of the first data tag does not include the second certifying party, it is confirmed that the first certification data entered by the first certifying party does not come from the second certifying party.

5. The method according to claim 2, characterized in that: If the request for retrospective verification of data includes a request for the second proof data to be sent to the third proof party for verification; The certified party corresponding to the certified role responds to the data retrospective verification request, calculates the data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard, obtains the complete data fingerprint value and / or the segmented data fingerprint value of the data, queries one or more data tags stored by the evidence depositor to obtain a target data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the data, and then obtains the verification result according to the extended information of the target data tag, including: The certified party corresponding to the certified role responds to the request for the second certification data of the first certification party to be sent to the third certification party for verification, and calculates the second certification data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the second certification data; The party obtaining the certificate searches for at least one second data tag matching the complete data fingerprint value and / or the segmented data fingerprint value of the second proof data from the one or more data tags stored by the party storing the certificate; Determine whether the identity of the extended information of at least one second data tag includes the first party providing evidence, whether the behavior of the extended information of at least one second data tag is data out, and whether the data recipient is the third party providing evidence; If the identity of the extended information of at least one second data tag includes the first proving party, and the behavior of the extended information of at least one second data tag is data out, and the data recipient is the third proving party, it is determined that the second proof data of the first proving party out is sent to the third proving party; If the identity of the extended information of at least one second data tag does not include the first certifying party, or the behavior of the extended information of at least one second data tag is not data out, it is determined that the first certifying party has not out the second certification data.

6. The method according to claim 1, characterized in that If the request for retrospective verification of data includes a request to verify that the first party providing proof has held or discarded third proof data; The certified party corresponding to the certified role responds to the data retrospective verification request, calculates the data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard, obtains the complete data fingerprint value and / or the segmented data fingerprint value of the data, queries one or more data tags stored by the evidence depositor to obtain a target data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the data, and then obtains the verification result according to the extended information of the target data tag, including: The certified party corresponding to the certified role responds to the request for verifying whether the first certification party holds or discards the third certification data, and calculates the third certification data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the third certification data; The party obtaining the certificate searches for at least one third data tag matching the complete data fingerprint value and / or the segmented data fingerprint value of the third proof data from the one or more data tags stored by the party storing the certificate; Determining whether the identity of the extended information of at least one third data tag includes the first evidence providing party; If the identity of the extended information of at least one third data tag includes the first proving party, then checking the behavior of the extended information of at least one third data tag; if the behavior of the extended information of at least one third data tag is data discarding, then determining that the first proving party discards the third proof data; if the behavior of the extended information of at least one third data tag is data holding, then determining that the first proving party holds the third proof data; If the identity of the extended information of at least one third data tag does not include the first certifying party, it is determined that the first certifying party does not hold or discard the third certification data.

7. The method according to claim 1, characterized in that If the data retrospective verification request includes a verification request of whether the fourth data held by the first certifying party is earlier than the fourth data held by the second certifying party; The certified party corresponding to the certified role responds to the data retrospective verification request, calculates the data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard, obtains the complete data fingerprint value and / or the segmented data fingerprint value of the data, queries one or more data tags stored by the evidence depositor to obtain a target data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the data, and then obtains the verification result according to the extended information of the target data tag, including: The certified party corresponding to the certified role responds to a verification request of whether the fourth data held by the first certified party is earlier than the fourth data held by the second certified party, and calculates the fourth certification data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard to obtain a complete data fingerprint value and / or a segmented data fingerprint value of the fourth certification data; The party obtaining the evidence searches for a fourth data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the fourth proof data and whose identity is the first party providing the evidence, and searches for a fifth data tag that matches the complete data fingerprint value and / or the segmented data fingerprint value of the fourth proof data and whose identity is the second party providing the evidence, from one or more data tags stored by the party storing the evidence; If the time of the extended information of the fourth data tag is earlier than the time of the extended information of the fifth data tag, it is determined that the fourth data held by the first provider is published earlier than the fourth data held by the second provider.

8. A data retrospective verification device, characterized in that: The data is encapsulated based on the MIME standard or the S / MIME standard, and the device includes: A definition module, used to predefine the role of providing evidence, the role of storing evidence and the role of obtaining evidence, wherein the role of providing evidence includes one or more parties providing evidence; Any one of the one or more attestation providers is used to provide attestation data, determine extended information and attestation elements based on the attestation data, and then combine the extended information and attestation elements to generate a unique data tag for the attestation data, and submit the data tag to the attestation provider corresponding to the attestation role; wherein the attestation elements include a complete data fingerprint value and / or a segmented data fingerprint value obtained by calculating the attestation data using a preset digest algorithm in combination with the MIME standard or the S / MIME standard; The evidence storage party is used to store one or more data tags; The certified party corresponding to the certified role is used to respond to the data retrospective verification request, use a preset digest algorithm and combine the MIME standard or S / MIME standard to calculate the data, obtain the complete data fingerprint value and / or segmented data fingerprint value of the data, query from one or more data tags stored by the certified party to obtain the target data tag that matches the complete data fingerprint value and / or segmented data fingerprint value of the data, and then obtain the verification result according to the extended information of the target data tag; Wherein, the extended information includes time, identity and behavior; Behavior is the operation of exiting, entering, holding, or discarding the proof data; The identity is a value that uniquely identifies the identity of the operator who performs the operation of exiting, entering, holding, or discarding the certification data; Time is the time value of the unique data tag that generates the proof data.

Images