Data verification method and device, system

Abstract

The one or more embodiments of the specification provide a data verification method and device, system. The method is applied to a data verification platform, comprising: receiving a verification request for target data, the verification request containing a data identifier of the target data; providing the data identifier to a business system and a blockchain system related to the target data respectively to obtain a verification result of the target data; wherein the verification result is obtained by comparing original data found by the business system based on the data identifier and on-chain data found by the blockchain system based on the data identifier; and returning the verification result to the initiator of the verification request.

Description

Technical Field

[0001] This specification relates to the field of blockchain technology in one or more embodiments, and particularly to a data verification method, apparatus, and system. Background Technology

[0002] Blockchain technology (also known as distributed ledger technology) is a decentralized distributed database technology with many characteristics such as decentralization, transparency, immutability, and trustworthiness, making it suitable for many application scenarios with high requirements for data reliability.

[0003] In related technologies, to facilitate data flow while ensuring data security, data is stored both on-chain and off-chain. The original off-chain data is used for data flow, while the on-chain data is used to verify the original off-chain data to confirm its reliability. Summary of the Invention

[0004] In view of the above, one or more embodiments of this specification provide a data verification method, apparatus, and system.

[0005] To achieve the above objectives, one or more embodiments of this specification provide the following technical solutions:

[0006] According to a first aspect of one or more embodiments of this specification, an evidence verification system is proposed, comprising: a client, an evidence verification platform, a blockchain system, and a business system with access permissions to the evidence verification platform; wherein,

[0007] The client initiates a verification request for the target evidence based on the evidence number of the target evidence;

[0008] In response to the verification request, the evidence verification platform provides the evidence number to the business system and the blockchain system related to the target evidence to obtain a verification result for the target evidence; wherein the verification result is obtained by comparing the original data found by the business system related to the target evidence based on the evidence number and the on-chain data found by the blockchain system based on the evidence number; and the verification result is returned to the client.

[0009] The business system related to the target evidence returns the original data of the target evidence to the evidence verification platform according to the evidence number;

[0010] The blockchain system searches for the on-chain data of the target evidence based on the evidence number provided by the evidence verification platform. According to a second aspect of one or more embodiments of this specification, a data verification method is proposed, applied to a data verification platform, comprising:

[0011] Receive a verification request for target data, wherein the verification request contains a data identifier of the target data;

[0012] The data identifier is provided to the business system and blockchain system related to the target data respectively to obtain the verification result of the target data; wherein, the verification result is obtained by comparing the original data found by the business system based on the data identifier and the on-chain data found by the blockchain system based on the data identifier.

[0013] Return the verification result to the party that initiated the verification request.

[0014] According to a third aspect of one or more embodiments of this specification, a data verification apparatus is provided for use in a data verification platform, comprising:

[0015] The receiving unit receives a verification request for target data, wherein the verification request contains a data identifier of the target data.

[0016] The providing unit provides the data identifier to the business system and the blockchain system related to the target data respectively, so as to obtain the verification result of the target data; wherein, the verification result is obtained by comparing the original data found by the business system based on the data identifier and the on-chain data found by the blockchain system based on the data identifier;

[0017] The return unit returns the verification result to the party that initiated the verification request.

[0018] According to a fourth aspect of one or more embodiments of this specification, an electronic device is provided, comprising:

[0019] processor;

[0020] Memory used to store processor-executable instructions;

[0021] The processor implements the method as described in the second aspect by executing the executable instructions.

[0022] According to a fourth aspect of one or more embodiments of this specification, a computer-readable storage medium is provided that stores computer instructions thereon, which, when executed by a processor, implement the steps of the method as described in the second aspect. Attached Figure Description

[0023] Figure 1 This is a schematic diagram of a data verification system provided in an exemplary embodiment.

[0024] Figure 2 This is a flowchart of a data verification method provided in an exemplary embodiment.

[0025] Figure 3 This is an interactive diagram of an evidence verification method provided in an exemplary embodiment.

[0026] Figure 4 This is a schematic diagram of an evidence verification interface provided in an exemplary embodiment.

[0027] Figure 5 This is a schematic diagram of the structure of a device provided in an exemplary embodiment.

[0028] Figure 6 This is a block diagram of a data verification device provided in an exemplary embodiment. Detailed Implementation

[0029] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with one or more embodiments of this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of one or more embodiments of this specification as detailed in the appended claims.

[0030] It should be noted that the steps of the corresponding methods are not necessarily performed in the order shown and described in this specification in other embodiments. In some other embodiments, the methods may include more or fewer steps than described in this specification. Furthermore, a single step described in this specification may be broken down into multiple steps in other embodiments; and multiple steps described in this specification may be combined into a single step in other embodiments.

[0031] Because blockchain technology possesses characteristics such as immutability and trustworthiness, storing data on the blockchain ensures data security; while storing data in an off-chain database, without the limitations of a distributed ledger, ensures convenient data flow. Therefore, related technologies typically store data both on-chain and off-chain to improve data flow convenience while ensuring data security.

[0032] Data verification refers to the operation of verifying the reliability of off-chain data based on on-chain data. When performing verification, users need to upload the original data of the target data to be verified, so that the verification operator can verify the uploaded original data against the on-chain data stored in the blockchain.

[0033] It should be understood that because the relevant technologies require users to upload original data during the data verification process, the data verification methods in these technologies have at least the following three problems:

[0034] Firstly, since users need to provide raw data, and this raw data may not be electronic or stored on the currently used device, users need to convert other types of materials, such as paper materials, into electronic materials, or transfer electronic materials stored on other devices to the currently used device. Therefore, the process is quite cumbersome for users when data verification is required.

[0035] Secondly, the amount of raw data may be large, but the bandwidth on the user side is usually small, which makes it take a long time to upload the data and reduces the efficiency of data verification.

[0036] Third, since the original data needs to be transmitted between the user and the party performing the verification operation, and the transmission link between an individual user and other devices usually does not have a high security level, the original data may be stolen, thus affecting the security of the data.

[0037] To this end, this disclosure proposes a data verification system that can verify target data without requiring users to upload original data.

[0038] Figure 1 This specification illustrates a data verification system as an exemplary embodiment. For example... Figure 1 As shown, the system includes: a client 11, a data verification platform 12, a blockchain system 13, and a business system 14 with access permissions to the data verification platform 12; wherein,

[0039] Client 11 initiates a verification request for the target data based on the data identifier of the target data;

[0040] In response to the verification request, the data verification platform 12 provides the data identifier to the business system 141 and the blockchain system 13 related to the target data to obtain the verification result for the target data; wherein the verification result is obtained by comparing the original data found by the business system 141 related to the target data based on the data identifier and the on-chain data found by the blockchain system 13 based on the data identifier; and the verification result is returned to the client 11.

[0041] The business system 141 related to the target data returns the original data of the target data to the data verification platform 12 according to the data identifier;

[0042] Blockchain system 13 searches for on-chain data of the target data based on the data identifier provided by data verification platform 12.

[0043] In this specification, the data verification platform 12 can be integrated with the business systems of different organizations, allowing the data verification platform 12 to directly access the integrated business systems 14. Specifically, the person in charge of the data verification platform 12 can negotiate with the persons in charge of each organization to grant access permissions to the corresponding business systems to the data verification platform 12.

[0044] Based on this, when a user needs to verify target data, they can send a verification request to the data verification platform 12 through their client 11, instructing the platform to complete the verification operation. Since the data verification platform 12 is already integrated with the business systems of different organizations, the user only needs to add a data identifier for the target data to the verification request. The platform can then retrieve the original data of the target data from the relevant business system 141 based on this identifier, without requiring the user to upload the original data through the client 11. Furthermore, the platform can also instruct the blockchain system 13 to search for the on-chain data of the target data from the stored on-chain data based on the data identifier included in the verification request, for use in verifying the original data of the target data.

[0045] In this specification, the verification result can be obtained by comparing the on-chain data found by the blockchain system 13 based on the data identifier with the original data found by the business system 141 based on the data identifier. The verification result can be returned to the client 11 by the data verification platform 12 and displayed to the user by the client 11.

[0046] It should be understood that, because this specification pre-connects the data verification platform 12 with the business systems of various organizations, the data verification platform 12 can directly obtain the original data of the target data from the business system 141 related to the target data based on the data identifier of the target data to be verified. Based on this, users only need to add the data identifier of the target data to the verification request, without having to upload the original data of the target data. Therefore, this specification, while completing the verification operation for the target data based on the user's verification request, avoids the situation in related technologies where users need to upload the original data of the data to be verified. This solves the problem of cumbersome operation when users upload original data and avoids data security issues caused by the transmission of original data between the user and the party executing the verification operation.

[0047] In this specification, the data verification operation can be performed by either the aforementioned data verification platform 12 or by the blockchain system 13.

[0048] In one embodiment, upon receiving a verification request from the client 11, the data verification platform 12 can, on the one hand, send a raw data retrieval request to the business system 141 based on the data identifier contained in the verification request, instructing the business system 141 to locate and return the raw data of the target data; on the other hand, it can generate an on-chain data retrieval transaction for the target data based on the data identifier, instructing the blockchain system 13 to locate and return the on-chain data of the target data according to the data identifier. Based on this, the data verification platform 12 can compare the raw data returned by the business system 141 with the on-chain data returned by the blockchain system 13 to obtain the verification result of the target data.

[0049] In another embodiment, upon receiving a verification request from client 11, data verification platform 12 can still send a raw data retrieval request to business system 141 based on the data identifier contained in the verification request. This instructs business system 141 to locate and return the raw data of the target data. Furthermore, based on the data identifier and raw data of the target data, a verification transaction for the target data can be generated and sent to blockchain system 13. Upon receiving the verification transaction, blockchain system 13 can invoke and execute the verification contract to locate the on-chain data of the target data based on the data identifier contained in the verification transaction. The located on-chain data is then compared with the raw data contained in the verification transaction to obtain the verification result. Blockchain system 13 returns the verification result to data verification platform 12, which then returns the verification result to client 11.

[0050] In this specification, after receiving a verification request from the client 11, the data verification platform 12 can prioritize identifying the business system 141 related to the target data from among the multiple connected business systems 14. It should be noted that, in this specification, the business system 141 related to the target data refers to the business system that maintains the original data of the target data. In this specification, the business system related to the target data can be identified through various methods.

[0051] In one embodiment, the user may know which business system maintains the original data of the target data. In this case, in addition to inputting the data identifier of the target data in the client 11, the user can also input the system identifier of the business system 141 that maintains the original data of the target data in the client 11. The client 11 can then generate a verification request for the target data based on the data identifier of the target data and the system identifier of the business system 141. After receiving the verification request for the target data, the data verification platform 12 can determine the business system 141 related to the target data based on the system identifier contained therein, and initiate a request to the business system 141 to obtain the original data of the target data based on the data identifier.

[0052] In another embodiment, the data verification platform 12 can maintain a correspondence between the data identifiers of each piece of data and the system identifiers of their respective related business systems. In this case, after receiving a verification request, the data verification platform 12 can find the system identifier corresponding to the data identifier contained in the verification request from the correspondence, and determine the business system 14 corresponding to the found system identifier as the business system 141 related to the target data. Based on this, the data verification platform 12 can initiate a request to the business system 141 to obtain the original data of the target data based on the data identifier. It should be understood that, compared with the previous embodiment, this embodiment does not require the user to obtain the system identifier of the business system 141, which greatly simplifies the user's operation during data verification. However, as a trade-off, the data verification platform 12 needs to additionally maintain the correspondence between the system identifiers of each business system and the data identifiers of their stored data, thus occupying more storage space in the data verification platform 12.

[0053] In another embodiment, different formats can be used to set data identifiers for data maintained in different business systems. Then, when the data verification platform 12 receives a verification request, it can identify the identifier format of the data identifier contained in the verification request and determine the business system 141 related to the target data based on that identifier format.

[0054] Of course, the above examples are all illustrative. How to specifically identify the business system 141 related to the target data from several business systems 14 can be determined by those skilled in the art according to actual needs, and this specification does not impose any restrictions on this.

[0055] In this specification, each piece of data may be associated with different events. Therefore, upon receiving a verification request, the data verification platform 12 can also authenticate the initiator of the verification request to determine whether verification of the target data is required. Specifically, after reading the data identifier from the verification request, the data verification platform 12 can determine the target event related to the target data based on the data identifier, and verify whether the initiator is a relevant party to the target event based on the initiator's identity information contained in the verification request. If the identity information indicates that the initiator is a relevant party to the target event, the authentication is successful, and verification of the target data is performed.

[0056] This specification allows for further stringent verification criteria. For example, the data verification platform 12 can pre-set different verification scopes for different roles within an event. After reading the identity information contained in the verification request, the data verification platform 12 can determine the role of the requester in the target event based on that identity information, and then determine the target verification scope corresponding to that target role from the verification scopes set for each role. Only if the target data falls within this target verification scope is the identity verification considered successful, and the verification operation for the target data is executed.

[0057] In practice, different authentication levels can be set for different roles. A higher authentication level means a more complex authentication process and more conditions for successful authentication. For example, the authentication level set for different roles can be positively correlated with the corresponding verification scope; that is, the larger the verification scope for a role, the higher the authentication level should be. Of course, this example is merely illustrative. How to specifically set authentication levels for different roles, and the relationship between authentication levels and authentication operations, can be determined by those skilled in the art based on actual needs. This specification does not impose any restrictions on this.

[0058] In this specification, the data verification platform 12 can also perform batch verification of data. In this case, the target data can be a data set of multiple data related to the target event.

[0059] In one scenario of batch verification, the user may know the data identifiers of all data in the dataset. Client 11 can add the data identifiers of all data to the verification request at the user's instruction. Upon receiving the verification request, data verification platform 12 can, on the one hand, provide the data identifiers of multiple data to the business system 141 related to the corresponding data, so that each business system 141 can return the original data of the corresponding data. In this process, any of the methods described above can be used to determine the business system 141 related to each data and initiate a retrieval request to each business system 141. On the other hand, it can provide the data identifiers of all data to blockchain system 13, so that blockchain system 13 can find the on-chain data of each data based on the received multiple data identifiers.

[0060] In another scenario of batch verification, the data verification platform 12 can maintain a set of data identifiers corresponding to each event. In this case, the verification request may only contain data identifiers of some data in the aforementioned data set. Upon receiving a verification request, the data verification platform 12 can determine the data identifier set to which the data identifiers in the verification request belong from the set of data identifiers corresponding to each event. It then provides each data identifier in the determined data identifier set to the relevant business system 141 and provides all data identifiers in the determined data identifier set to the blockchain system 13. The method for determining the relevant business system 141 is similar to the previous scenario, and related details can be found in the previous description, so they will not be repeated here.

[0061] It is easy to see that batch verification allows users to verify data related to the same event at once, avoiding the need for users to verify each piece of data individually.

[0062] In this specification, the above technical solutions can be adopted in various scenarios. For example, in the judicial system, the data verification platform 12 can be an evidence verification platform, the target event can be a target case, the target data can be evidence information related to the target case, and the data identifier of the target data can be the evidence number of the evidence information. Correspondingly, the blockchain used to upload the evidence information of the case can be called a judicial chain, and the data verification operation can be called evidence verification. In this scenario, the evidence verification operation can occur when the relevant parties in the target case receive paper or electronic evidence. For example, when the plaintiff, defendant, judge, etc., receive mailed paper evidence, they can input the evidence number contained in the paper evidence into the client 11, and then initiate a verification request for the paper evidence to the evidence verification platform. Of course, the judicial scenario is merely illustrative, and the technical solutions in this specification can also be used in other scenarios. The specific scenario to which it is applied can be determined by those skilled in the art based on the actual situation, and this specification does not limit it.

[0063] As described above, the data verification system in this specification includes a data verification platform, a business system, and a blockchain system. The business system and the data verification platform are pre-connected, allowing the data verification platform to directly access the business system and obtain raw data from it. Based on this, when a user initiates a verification request through a client, they only need to add the data identifier of the target data to be verified to the verification request, without requiring the user to upload the raw data. This avoids the problems of cumbersome user operations and bandwidth consumption associated with related technologies that require users to upload raw data.

[0064] In addition, it should be understood that the security of the client, as a user-side device, and its transmission links with other devices are usually not very high. Therefore, uploading raw data from the user side is highly likely to result in the leakage of that raw data. Data verification platforms and business systems, on the other hand, are typically equipped with high-level data security measures, and data transmission between them usually does not lead to data leakage. Therefore, the technical solution in this specification can also avoid the problem of raw data leakage caused by the need for users to upload raw data, but the low security of the user-side transmission links, which is common in related technologies.

[0065] Furthermore, the target data to be verified in this specification can be related to the target event. The data verification platform can also authenticate the initiator of the verification request. Verification of the target data is only performed if the identity information included in the verification request indicates that the initiator is a relevant party to the target event. This approach avoids situations where personnel unrelated to the target event verify data related to the target event.

[0066] Furthermore, this specification allows setting different verification scopes for each role in the event. Based on this, during the identity authentication process, in addition to requiring the initiator to be a relevant party to the target event, the target role corresponding to the initiator in the target event can be further determined. This ensures that the target data falls within the target verification scope corresponding to that role, and verification is only performed on the target data if it does. This method further enhances the strictness of identity authentication, preventing relevant parties to the target event from verifying data they do not have the authority to do so.

[0067] The data verification platform described in this manual can also perform batch verification of multiple data belonging to the same event, avoiding the cumbersome verification operation caused by the need to verify each data individually in related technologies.

[0068] Corresponding to the aforementioned data verification system, this specification also proposes a data verification method. In this method, most operations, such as how to compare raw data with on-chain data, how to identify the business system related to the target data, how to perform identity authentication, and how to perform batch verification, have already been described above. Related content can be found in the description of the data verification system and will not be repeated below.

[0069] Figure 2 This is a flowchart illustrating an exemplary embodiment of a data verification method. The method is applied to a data verification platform, such as... Figure 2 As shown, the method may include the following steps:

[0070] Step 202: Receive a verification request for the target data, wherein the verification request contains the data identifier of the target data.

[0071] As mentioned above, after receiving a verification request from a client, the data verification platform can prioritize identifying the business system related to the target data from among the multiple business systems that have been connected.

[0072] In one scenario, a user may know which business system maintains the original target data. In this case, in addition to entering the data identifier of the target data in the client, the user can also enter the system identifier of the business system maintaining the target data. The client can then generate a verification request for the target data based on both the data identifier and the system identifier. Upon receiving the verification request, the data verification platform can read the system identifier contained in the verification request to determine the business system associated with the target data.

[0073] In another scenario, the data verification platform can maintain a mapping between data identifiers for each piece of data and the system identifiers of their respective related business systems. In this case, upon receiving a verification request, the platform can retrieve the system identifier corresponding to the data identifier included in the request from this mapping, and identify the business system corresponding to the found system identifier as the one associated with the target data. Based on this, the platform can then initiate a request to the business system to retrieve the original data for the target data, using the data identifier.

[0074] In another scenario, different formats can be used to set data identifiers for data maintained in different business systems. When a data verification platform receives a verification request, it can identify the identifier format of the data identifier contained in the verification request and determine the business system associated with the target data based on that identifier format.

[0075] Step 204: Provide the data identifier to the business system and blockchain system related to the target data respectively to obtain the verification result of the target data; wherein, the verification result is obtained by comparing the original data found by the business system based on the data identifier and the on-chain data found by the blockchain system based on the data identifier.

[0076] As mentioned above, data verification can be performed either by a data verification platform or by a blockchain system.

[0077] When executed by a data verification platform, upon receiving a verification request from a client, the platform can, on the one hand, send a raw data retrieval request to the business system based on the data identifier contained in the verification request, instructing the business system to locate and return the raw data of the target data; on the other hand, it can generate an on-chain data retrieval transaction for the target data based on the data identifier, instructing the blockchain system to locate and return the on-chain data of the target data according to the data identifier. Based on this, the data verification platform can then compare the raw data returned by the business system with the on-chain data returned by the blockchain system to obtain the verification result of the target data.

[0078] When executed by a blockchain system, upon receiving a verification request from a client, the data verification platform can still send a raw data retrieval request to the relevant business system based on the data identifier contained in the verification request. This instructs the business system to locate and return the raw data of the target data. Furthermore, based on the data identifier and the raw data, a verification transaction for the target data can be generated and sent to the blockchain system. Upon receiving the verification transaction, the blockchain system can invoke and execute the verification contract to locate the on-chain data of the target data based on the data identifier contained in the verification transaction. The found on-chain data is then compared with the raw data contained in the verification transaction to obtain the verification result. The blockchain system returns the verification result to the data verification platform, which then returns the verification result to the client.

[0079] As mentioned above, each piece of data may be related to different events. Therefore, upon receiving a verification request, the data verification platform can also authenticate the initiator of the verification request to determine whether verification of the target data is necessary. Specifically, after reading the data identifier from the verification request, the data verification platform can identify the target event related to the target data based on the data identifier, and verify whether the initiator is a relevant party to the target event based on the initiator's identity information included in the verification request. If the identity information indicates that the initiator is a relevant party to the target event, the authentication is successful, and verification of the target data is performed.

[0080] As mentioned above, this specification can further tighten the conditions for identity authentication. For example, the data verification platform can pre-set different verification scopes for different roles within an event. Then, after reading the identity information contained in the verification request, the data verification platform can determine the role of the initiator of the verification request in the target event based on the identity information, and determine the target verification scope corresponding to that target role from the verification scopes set for each role. Specifically, identity authentication is considered successful only if the target data falls within the target verification scope, and verification operations are performed on the target data.

[0081] As mentioned above, the data verification platform can also perform batch verification of data. In this case, the target data can be a collection of multiple data related to the target event.

[0082] In one scenario of batch verification, the user may know the data identifiers of all data in the dataset. The client can add all data identifiers to the verification request at the user's instruction. Upon receiving the verification request, the data verification platform can, on the one hand, provide the data identifiers of multiple data to the relevant business systems, so that each business system can return the original data of the corresponding data. In this process, any of the methods described above can be used to determine the relevant business systems and initiate retrieval requests to each business system. On the other hand, the platform can provide all data identifiers to the blockchain system, so that the blockchain system can find the on-chain data of each data based on the received multiple data identifiers.

[0083] In another scenario of batch verification, the data verification platform can maintain a set of data identifiers corresponding to each event. In this case, the verification request may only contain data identifiers of a portion of the data in the aforementioned data set. Upon receiving a verification request, the data verification platform can determine the data identifier set to which the data identifiers in the verification request belong from the set of data identifiers corresponding to each event. It then provides each data identifier in the determined data identifier set to the relevant business system and provides all data identifiers in that set to the blockchain system. The method for determining the relevant business system is similar to the previous scenario, and related details can be found in the previous description; they will not be repeated here.

[0084] As described above, the technical solutions described herein can be applied in various scenarios. For example, in the judicial system, the data verification platform can be an evidence verification platform, the target event can be a target case, the target data can be evidence information related to the target case, and the data identifier of the target data can be the evidence number of the evidence information. Correspondingly, the blockchain used to upload the evidence information of the case can be called a judicial chain, and the data verification operation can be called evidence verification. In this scenario, the evidence verification operation can occur when the relevant parties in the target case receive paper or electronic evidence. For example, when the plaintiff, defendant, judge, etc., receive mailed paper evidence, they can input the evidence number contained in the paper evidence into the client and then initiate a verification request for the paper evidence to the evidence verification platform. Of course, the judicial scenario is merely illustrative, and the technical solutions in this specification can also be used in other scenarios. The specific scenario to which it is applied can be determined by those skilled in the art based on the actual situation, and this specification does not limit this.

[0085] Step 206: Return the verification result to the party that initiated the verification request.

[0086] As can be seen from the above technical solution, the data verification method in this specification is applied to a data verification platform. This platform is pre-connected to the business system, allowing it to directly access and obtain raw data. Based on this, when a user initiates a verification request through the client, they only need to add the data identifier of the target data to be verified to the verification request, without requiring the user to upload the raw data. This avoids the problems of cumbersome user operations and bandwidth consumption associated with related technologies that require users to upload raw data.

[0087] In addition, in this data verification method, the target data to be verified can be related to the target event. The data verification platform can also authenticate the identity of the initiator of the verification request. Verification of the target data is only performed if the identity information included in the verification request indicates that the initiator is a relevant party to the target event. This approach avoids situations where personnel unrelated to the target event verify data related to the target event.

[0088] Furthermore, this data verification method can also perform batch verification of multiple data belonging to the same event, avoiding the cumbersome operation caused by the need to verify each data individually in related technologies.

[0089] As mentioned above, this specification requires prior integration between the data verification platform and the business systems of various organizations; in other words, the data verification platform needs to have priority access to the business systems of each organization. It should be understood that most private organizations typically do not have the resources to access other organizations' business systems; however, institutions within the judicial system, given their objective responsibility to supervise other organizations, such as online shopping platforms and payment platforms, usually have access to those systems. Therefore, this specification also proposes an evidence verification system applicable to the judicial system.

[0090] It should be noted that most of the operational methods in the evidence verification system described below, such as how to conduct verification and how to obtain raw data from the business system, are consistent with the data verification system described above. The only differences are that "data" is replaced with "evidence," "data verification platform" with "evidence verification platform," "data identifier" with "evidence number," and "event" with "case." All relevant details can be found in the introduction to the data verification system and will not be elaborated upon further below.

[0091] The architecture of the evidence verification system is basically the same as that of the data verification system described above; therefore, it can be referenced accordingly. Figure 1 The diagram illustrates the architecture. This evidence verification system may include: a client, an evidence verification platform, a blockchain system, and business systems with access permissions to the evidence verification platform; wherein,

[0092] The client initiates a verification request for the target evidence based on the evidence number of the target evidence;

[0093] The evidence verification platform, in response to the verification request, provides the evidence number to the business system and blockchain system related to the target evidence to obtain the verification result for the target evidence; wherein, the verification result is obtained by comparing the original data found by the business system related to the target evidence based on the evidence number and the on-chain data found by the blockchain system based on the evidence number; and the verification result is returned to the client.

[0094] The business system related to the target evidence, in response to the access request, returns the original data of the target evidence to the evidence verification platform according to the evidence number;

[0095] The blockchain system uses the evidence number provided by the evidence verification platform to locate the on-chain data of the target evidence.

[0096] As mentioned above, the evidence verification platform can be integrated with the business systems of different organizations, allowing the platform to directly access these systems. Specifically, the person in charge of the evidence verification platform can negotiate with the heads of various organizations to grant the platform access to the corresponding business systems.

[0097] As mentioned above, users may know which business system maintains the original data of the target evidence. In this case, in addition to entering the evidence number of the target evidence in the client, users can also enter the system identifier of the business system maintaining the target evidence. The client can then generate a verification request for the target evidence based on the evidence number and the system identifier. After receiving the verification request, the evidence verification platform can read the system identifier contained in the verification request to determine the business system related to the target evidence.

[0098] In another scenario, the evidence verification platform can maintain a mapping between the evidence numbers of each piece of evidence and the system identifiers of their respective related business systems. In this case, upon receiving a verification request, the platform can retrieve the system identifier corresponding to the evidence number included in the request from this mapping, and identify the business system corresponding to the found system identifier as the one relevant to the target evidence. Based on this, the platform can then initiate a request to the business system to obtain the original data of the target evidence, using the evidence number.

[0099] In another scenario, different formats can be used to assign evidence numbers to evidence maintained in different business systems. When the evidence verification platform receives a verification request, it can identify the format of the evidence number contained in the request and determine the business system associated with the target evidence based on that format.

[0100] As mentioned above, evidence verification can be performed either by an evidence verification platform or by a blockchain system.

[0101] When executed by an evidence verification platform, upon receiving a verification request from a client, the platform can, on the one hand, send a raw data retrieval request to the business system based on the evidence number included in the verification request, instructing the business system to locate and return the raw data of the target evidence; on the other hand, it can generate an on-chain data retrieval transaction for the target evidence based on the evidence number, instructing the blockchain system to locate and return the on-chain data of the target evidence according to the evidence number. Based on this, the evidence verification platform can then compare the raw data returned by the business system with the on-chain data returned by the blockchain system to obtain the verification result of the target evidence.

[0102] When executed by a blockchain system, upon receiving a verification request from a client, the evidence verification platform can still send a raw data retrieval request to the relevant business system based on the evidence number included in the verification request. This instructs the business system to locate and return the raw data of the target evidence. Furthermore, based on the evidence number and the raw data, a verification transaction can be generated for the target evidence, and this transaction is sent to the blockchain system. Upon receiving the verification transaction, the blockchain system can invoke and execute the verification contract to locate the on-chain data of the target evidence based on the evidence number included in the verification transaction. The retrieved on-chain data is then compared with the raw data included in the verification transaction to obtain the verification result. The blockchain system returns the verification result to the evidence verification platform, which then returns the verification result to the client.

[0103] As mentioned above, each piece of evidence may be related to different cases. Therefore, upon receiving a verification request, the evidence verification platform can also authenticate the initiator of the request to determine whether verification of the target evidence is necessary. Specifically, after retrieving the evidence number from the verification request, the platform can identify the target case related to the target evidence based on that evidence number. It then verifies whether the initiator is a relevant party to the target case based on the initiator's identity information included in the verification request. If the identity information indicates that the initiator is a relevant party to the target case, the authentication is successful, and verification of the target evidence is performed.

[0104] As mentioned above, this specification can further tighten the conditions for identity authentication. For example, the evidence verification platform can pre-set different verification scopes for different roles involved in the case. Then, after reading the identity information contained in the verification request, the evidence verification platform can determine the role of the requester in the target case based on the identity information, and determine the target verification scope corresponding to that target role from the verification scopes set for each role. Specifically, identity authentication is considered successful only if the target evidence falls within the target verification scope, and the verification operation for the target evidence is then performed.

[0105] As mentioned above, the evidence verification platform can also perform batch verification of evidence. In this case, the target evidence can be a collection of multiple pieces of evidence related to the target case.

[0106] In one scenario of batch verification, the user may know the evidence numbers of all evidence in the evidence set. The client can add the evidence numbers of all evidence to the verification request at the user's instruction. Upon receiving the verification request, the evidence verification platform can, on the one hand, provide the evidence numbers of multiple pieces of evidence to the relevant business systems, so that each business system can return the original data of the corresponding evidence. In this process, any of the methods described above can be used to determine the relevant business systems and initiate retrieval requests to each business system. On the other hand, the platform can provide the evidence numbers of all evidence to the blockchain system, so that the blockchain system can find the on-chain data of each piece of evidence based on the received evidence numbers.

[0107] In another scenario of batch verification, the evidence verification platform can maintain a set of evidence numbers corresponding to each case. In this case, the verification request may only contain evidence numbers from a portion of the evidence in the aforementioned evidence set. Upon receiving the verification request, the evidence verification platform can determine the set of evidence numbers to which the evidence numbers included in the verification request belong from the set of evidence numbers corresponding to each case. It then provides each evidence number in the determined set to the relevant business system and provides all evidence numbers in that set to the blockchain system. The method for determining the relevant business system is similar to the previous scenario, and related details can be found in the previous description; they will not be repeated here.

[0108] As described above, in the context of evidence verification, the verification process can occur when relevant parties in the target case receive paper or electronic evidence. For example, when the plaintiff, defendant, or judge receives mailed paper evidence, they can input the evidence number contained in the paper evidence into the client and then initiate a verification request for that paper evidence to the evidence verification platform. Of course, the scenario of receiving paper or electronic evidence is merely illustrative; evidence verification can also be performed in other scenarios. The specific scenario in which it is performed can be determined by those skilled in the art based on the actual situation, and this specification does not impose any limitations on this.

[0109] As can be seen from the above technical solution, the evidence verification platform included in the evidence verification system is pre-connected to various business systems, allowing the platform to directly access these systems and obtain the original data of each piece of evidence. Based on this, when a user initiates a verification request through the client, they only need to add the evidence number of the target evidence to be verified to the verification request, without requiring the user to upload the original data. This avoids the problems of cumbersome user operations and bandwidth consumption associated with related technologies that require users to upload original data.

[0110] The following section describes the technical solution of this manual, taking the verification of evidentiary information in paper evidence received by the relevant parties in the target case as an example.

[0111] Figure 3 This diagram illustrates an interactive method for evidence verification, as shown in an exemplary embodiment of this specification. This method is implemented based on the evidence verification system described above. Figure 3 As shown, the method may include the following steps:

[0112] Step 301: The client generates a verification request based on the evidence number and system identifier.

[0113] In this embodiment, the paper evidence received by the user may include an evidence number and a system identifier of the business system that maintains the original data of the paper evidence. The user can then generate a verification request for the paper evidence based on the evidence number and system identifier.

[0114] For example, after receiving paper evidence, users can open it in the client application. Figure 4 The verification interface shown allows users to input the evidence number and system identifier, enabling the client to generate a verification request for the paper evidence. Assuming the evidence information is an order from a shopping platform, the evidence number entered by the user could be... Figure 4 The order number shown is "202201041106", while the system identifier can be the shopping platform's platform identifier "4136".

[0115] Step 302: The client sends the generated verification request to the evidence verification platform.

[0116] After generating a verification request for paper evidence, the client can send the verification request to the evidence verification platform, which will then verify the evidence information contained in the paper evidence based on the evidence number and system identifier included in the verification request.

[0117] Step 303: The evidence verification platform reads the evidence number and system identifier contained in the verification request.

[0118] Once the evidence verification platform receives the verification request, it can read the evidence number and system identifier contained therein, which can be used to generate the original data acquisition request and the on-chain data acquisition transaction.

[0119] Step 304: The evidence verification platform generates the original data acquisition request and the on-chain data acquisition transaction based on the evidence number.

[0120] Step 305A: The evidence verification platform sends the original data acquisition request to the business system corresponding to the system identifier.

[0121] In this embodiment, since the verification request contains a system identifier, the evidence verification platform can determine the business system that maintains the original data of paper evidence from several connected business systems based on the read system identifier, and then send the generated original data acquisition request to the determined business system.

[0122] Following the example above, the generated raw data retrieval request can be sent to the shopping platform using platform number "4136". The shopping platform can then retrieve the raw information of the corresponding order from the maintained order information based on order number "202201041106" and return the retrieved raw data.

[0123] Step 306A: The business system searches for the original data of the paper evidence based on the evidence number.

[0124] Step 307A: The business system returns the found raw data to the evidence verification platform.

[0125] Step 305B: The evidence verification platform sends the on-chain data acquisition transaction to the blockchain system.

[0126] In this embodiment, the generated on-chain data acquisition transaction also needs to be sent to the blockchain system so that the blockchain system can return the on-chain data of the paper evidence according to the evidence number.

[0127] Following the example above, after receiving on-chain data to acquire a transaction, the blockchain system can search for and return the on-chain data of the paper evidence from a number of maintained on-chain data based on the order number contained therein.

[0128] Step 306B: The blockchain system searches for on-chain data of paper evidence based on the evidence number.

[0129] Step 307B: The blockchain system returns the found on-chain data to the evidence verification platform.

[0130] Step 308: The evidence verification platform verifies the received original data based on the received on-chain data.

[0131] After obtaining the on-chain data and original data of the paper evidence, the evidence verification platform can compare the two. If they match, the verification passes; otherwise, the verification fails.

[0132] Step 309: The evidence verification platform returns the verification results to the client.

[0133] After obtaining the verification result through comparison, the verification result can be returned to the client so that the user can know whether the received paper evidence is reliable through the client.

[0134] As can be seen from the above technical solution, the evidence verification system described in this specification can verify the original data corresponding to paper evidence upon receipt by the user, based on the evidence number contained therein, so that the user can know whether the received paper evidence is reliable. Furthermore, because the evidence verification platform is pre-connected to several business systems, it can directly access the business systems that maintain the original data of the paper evidence, and thus obtain the original data of the paper evidence from those business systems. This avoids the problems of cumbersome user operations and the potential for data theft that require users to upload original data during evidence verification in other technologies.

[0135] Figure 5 This is a schematic structural diagram of a device provided in an exemplary embodiment. Please refer to... Figure 5 At the hardware level, the device includes a processor 502, an internal bus 504, a network interface 506, memory 508, and non-volatile memory 510, and may also include other hardware required for business operations. One or more embodiments of this specification can be implemented in software, such as the processor 502 reading the corresponding computer program from the non-volatile memory 510 into memory 508 and then running it. Of course, in addition to software implementation, one or more embodiments of this specification do not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. That is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0136] Please refer to Figure 6 Data verification devices can be applied to, for example Figure 5 The device shown is used to implement the technical solution described in this specification. The data verification device may include:

[0137] The receiving unit 601 receives a verification request for target data, wherein the verification request includes a data identifier of the target data;

[0138] The providing unit 602 provides the data identifier to the business system and the blockchain system related to the target data respectively, so as to obtain the verification result of the target data; wherein, the verification result is obtained by comparing the original data found by the business system based on the data identifier and the on-chain data found by the blockchain system based on the data identifier;

[0139] Return unit 603 returns the verification result to the initiator of the verification request.

[0140] Optionally, the verification request may further include a system identifier of the business system associated with the target data; the device may also include:

[0141] The determining unit 604 reads the system identifier contained in the verification request to determine the business system related to the target data based on the system identifier.

[0142] Optionally, the data verification platform maintains a correspondence between the data identifiers of each piece of data and the system identifiers of their respective related business systems; the determining unit 604 is also used for:

[0143] From the correspondence maintained by the data verification platform, find the system identifier corresponding to the data identifier of the target data, and determine the business system corresponding to the found system identifier as the business system related to the target data.

[0144] Optionally, the data verification platform maintains the identifier formats used by each business system; the determining unit 604 is also used for:

[0145] Determine the identifier format of the data identifier, and determine the business system related to the target data based on the identifier format.

[0146] Optional, also includes:

[0147] The comparison unit 605 obtains the on-chain data of the target data from the blockchain system based on the data identifier, and compares the on-chain data with the original data to obtain a verification result for the target data; or, it generates a verification transaction for the target data based on the data identifier and the original data, uploads the verification transaction to the blockchain system, so that the blockchain system can call the verification contract to verify the original data by using the on-chain data found based on the data identifier, and return the verification result.

[0148] Optionally, the determining unit 604 is also used for:

[0149] The target event related to the target data is determined based on the data identifier, and the identity information of the initiator contained in the verification request is read.

[0150] Specifically, the verification operation for the target data is performed only if the identity information indicates that the initiator is a relevant party to the target event.

[0151] Optionally, the determining unit 604 is also used for:

[0152] Based on the identity information, determine the target role corresponding to the initiator in the target event;

[0153] From the pre-set verification ranges for each role, determine the target verification range corresponding to the target role;

[0154] Specifically, the verification operation for the target data is performed only if the target data falls within the target verification range.

[0155] Optionally, the target data is a dataset of multiple data related to the target event;

[0156] The providing unit 602 is further configured to: provide the data identifiers of the plurality of data to the business systems associated with the corresponding data, and provide the data identifiers of the plurality of data to the blockchain system; or,

[0157] The verification request includes data identifiers of some data in the data set; the determining unit 604 is further configured to: determine the data identifier set to which the data identifiers included in the verification request belong from the maintained data identifier set corresponding to each event; the providing unit 602 is further configured to: provide each data identifier contained in the determined data identifier set to the business system related to the corresponding data, and provide all data contained in the determined data identifier set to the blockchain system.

[0158] Optionally, the target event is a target case, the target data is evidence information related to the target case, and the data identifier of the target data is the evidence number of the evidence information.

[0159] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which can take the form of a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email sending and receiving device, game console, tablet computer, wearable device, or any combination of these devices.

[0160] In a typical configuration, a computer includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0161] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0162] Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0163] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0164] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0165] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of one or more embodiments of this specification. The singular forms “a,” “described,” and “the” used in one or more embodiments of this specification and in the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0166] It should be understood that although the terms first, second, third, etc., may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of one or more embodiments of this specification, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "in response to a determination," or "when," or "in the event of a determination."

[0167] The above description is merely a preferred embodiment of one or more embodiments of this specification and is not intended to limit the scope of one or more embodiments of this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of one or more embodiments of this specification should be included within the protection scope of one or more embodiments of this specification.

Claims

1. An evidence verification system, comprising: The client, the evidence verification platform, the blockchain system, and the business systems with access permissions to the evidence verification platform; wherein, The client initiates a verification request for the target evidence based on the evidence number of the target evidence; In response to the verification request, the evidence verification platform provides the evidence number to the business system and the blockchain system related to the target evidence to obtain a verification result for the target evidence; wherein the verification result is obtained by comparing the original data found by the business system related to the target evidence based on the evidence number and the on-chain data found by the blockchain system based on the evidence number; and the verification result is returned to the client. The business system related to the target evidence returns the original data of the target evidence to the evidence verification platform according to the evidence number; The blockchain system searches for the on-chain data of the target evidence based on the evidence number provided by the evidence verification platform.

2. The system according to claim 1, The evidence verification platform provides the evidence number to the blockchain system, including: Based on the evidence number, an on-chain data acquisition transaction is initiated for the target evidence, so that the blockchain system returns the on-chain data found according to the evidence number to the evidence verification platform; The evidence verification platform is also used to: compare the on-chain data returned by the blockchain system with the original data returned by the business system to obtain the verification result of the target evidence.

3. The system according to claim 1, The evidence verification platform provides the evidence number to the blockchain system, including: Initiate a verification transaction for the target evidence based on the evidence number and the raw data returned by the business system; The blockchain system is also used to: invoke a verification contract to verify the original data contained in the verification transaction based on the found on-chain data, and return the verification result to the evidence verification platform.

4. The system according to claim 1, The evidence verification platform maintains a correspondence between the evidence numbers of each piece of evidence and the system identifiers of their respective related business systems. It is also used to: search for the system identifier corresponding to the evidence number from the correspondence, and determine the business system corresponding to the found system identifier as the business system related to the target evidence; or... The evidence verification platform is further configured to: read the system identifier from the verification request, and identify the business system corresponding to the read system identifier as the business system related to the target evidence.

5. A data verification method, applied to a data verification platform, comprising: Receive a verification request for target data, wherein the verification request contains a data identifier of the target data; The data identifier is provided to the business system and blockchain system related to the target data respectively to obtain the verification result of the target data; wherein, the verification result is obtained by comparing the original data found by the business system based on the data identifier and the on-chain data found by the blockchain system based on the data identifier. Return the verification result to the party that initiated the verification request.

6. The method according to claim 5, wherein the verification request further includes a system identifier of the business system related to the target data; the method further includes: Read the system identifier contained in the verification request to determine the business system related to the target data based on the system identifier.

7. The method according to claim 5, wherein the data verification platform maintains a correspondence between the data identifiers of each data and the system identifiers of their respective related business systems; the method further includes: From the correspondence maintained by the data verification platform, find the system identifier corresponding to the data identifier of the target data, and determine the business system corresponding to the found system identifier as the business system related to the target data.

8. The method according to claim 5, wherein the data verification platform maintains the identification formats adopted by each business system; the method further includes: Determine the identifier format of the data identifier, and determine the business system related to the target data based on the identifier format.

9. The method according to claim 5, further comprising: Based on the data identifier, on-chain data of the target data is obtained from the blockchain system, and the on-chain data is compared with the original data to obtain a verification result for the target data; or, Based on the data identifier and the original data, a verification transaction for the target data is generated, and the verification transaction is uploaded to the blockchain system. The blockchain system then calls the verification contract to verify the original data using on-chain data found based on the data identifier, and returns the verification result.

10. The method of claim 5, further comprising: The target event related to the target data is determined based on the data identifier, and the identity information of the initiator contained in the verification request is read. Specifically, the verification operation for the target data is performed only if the identity information indicates that the initiator is a relevant party to the target event.

11. The method of claim 10, further comprising: Based on the identity information, determine the target role corresponding to the initiator in the target event; From the pre-set verification ranges for each role, determine the target verification range corresponding to the target role; Specifically, the verification operation for the target data is performed only if the target data falls within the target verification range.

12. The method according to claim 5, wherein the target data is a data set of multiple data related to the target event; The verification request contains data identifiers for all data in the dataset; The step of providing the data identifiers to the business systems and blockchain systems related to the target data includes: providing the data identifiers of the plurality of data to the business systems related to the corresponding data, and providing the data identifiers of the plurality of data to the blockchain system; or, The verification request includes data identifiers of some data in the data set; the method further includes: determining the data identifier set to which the data identifiers included in the verification request belong from the maintained data identifier set corresponding to each event; the step of providing the data identifiers to the business system and blockchain system related to the target data respectively includes: providing each data identifier contained in the determined data identifier set to the business system related to the corresponding data, and providing all data contained in the determined data identifier set to the blockchain system.

13. The method according to claim 10 or 12, wherein the target event is a target case, the target data is evidence information related to the target case, and the data identifier of the target data is the evidence number of the evidence information.

14. A data verification device, applied to a data verification platform, comprising: The receiving unit receives a verification request for target data, wherein the verification request contains a data identifier of the target data. The providing unit provides the data identifier to the business system and the blockchain system related to the target data respectively, so as to obtain the verification result of the target data; wherein, the verification result is obtained by comparing the original data found by the business system based on the data identifier and the on-chain data found by the blockchain system based on the data identifier; The return unit returns the verification result to the party that initiated the verification request.

15. An electronic device comprising: processor; Memory used to store processor-executable instructions; The processor implements the method as described in any one of claims 5-13 by executing the executable instructions.

16. A computer-readable storage medium having stored thereon computer instructions that, when executed by a processor, implement the steps of the method as claimed in any one of claims 5-13.

Images