CN114662128A - Data verification system construction method and device - Google Patents

Data verification system construction method and device Download PDF

Info

Publication number
CN114662128A
CN114662128A CN202210272352.7A CN202210272352A CN114662128A CN 114662128 A CN114662128 A CN 114662128A CN 202210272352 A CN202210272352 A CN 202210272352A CN 114662128 A CN114662128 A CN 114662128A
Authority
CN
China
Prior art keywords
verification
data
demander
service platform
stored
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210272352.7A
Other languages
Chinese (zh)
Inventor
程龙
李艳鹏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alipay Hangzhou Information Technology Co Ltd
Ant Blockchain Technology Shanghai Co Ltd
Original Assignee
Alipay Hangzhou Information Technology Co Ltd
Ant Blockchain Technology Shanghai Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alipay Hangzhou Information Technology Co Ltd, Ant Blockchain Technology Shanghai Co Ltd filed Critical Alipay Hangzhou Information Technology Co Ltd
Priority to CN202210272352.7A priority Critical patent/CN114662128A/en
Publication of CN114662128A publication Critical patent/CN114662128A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/602—Providing cryptographic facilities or services
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08—Insurance

Abstract

The specification discloses a data verification system construction method and device, which are applied to a verification service platform. The verification service platform is configured with a universal template for defining fields and a universal verification component set, and each verification component has the capability of verifying field values of at least one data type; the certificate storage service platform is connected with at least one data certificate storage demand party; the method comprises the following steps: providing a verification requirement configuration interface for the target storage certification demander; according to the operation of the target evidence storage demander based on the configuration interface, a custom data structure is created for the data to be stored of the target evidence storage demander, and a field with verification requirements and a corresponding verification component in the custom data structure are determined; and constructing a data verification system according to the created custom data structure, the field with verification requirements and the corresponding verification component, and returning a calling identifier for calling the data verification system to the target verification-storing demander.

Description

Data verification system construction method and device
Technical Field
The embodiment of the specification relates to the technical field of computer application, in particular to a method and a device for constructing a data verification system.
Background
At present, for different business scenes, a requirement of business data evidence storage generally exists, for example, in a logistics business scene, in order to ensure safe transportation of goods, a freight company can upload logistics records of freight vehicles to a block chain for evidence storage, so as to determine whether a problem occurs in the transportation process of the goods; for another example, in a stock trading business scenario, in order to ensure the security of trading data, a stock trading platform may upload the trading data to a blockchain for evidence storage in real time after the trading is completed, so as to audit the trading data.
Before the business data is stored, the business data needs to be checked, and the existing method for respectively developing the customized checking system aiming at different business scenes is complex and has higher development cost.
Disclosure of Invention
In order to solve the above technical problems, the present specification discloses a data verification system construction method and apparatus. The technical scheme is as follows.
A data verification system construction method is applied to a verification service platform, the verification service platform is configured with a universal template and a universal verification component set, the universal template is used for defining fields, and each verification component has the capability of verifying the authenticity of the field value of at least one data type; the verification service platform is connected with at least one data verification demander, the data verification demander has the requirement of verifying data, and the method is used for constructing a verification system aiming at the data to be verified of a target verification demander;
the method comprises the following steps:
providing a verification requirement configuration interface for the target storage certification demander, wherein the configuration interface is used for: causing the target verification demander to define one or more fields based on the generic template and for at least one field defined, select a verification component from the set of generic verification components for verifying that field;
according to the operation of the target evidence storage demander based on the configuration interface, a custom data structure is created for the data to be stored of the target evidence storage demander, and a field with verification requirements and a corresponding verification component in the custom data structure are determined;
generating an intelligent check contract serving as a data check system according to the created custom data structure, the field with the check requirement and the corresponding check component, and deploying the intelligent check contract to a blockchain network; the checking intelligent contract is used for checking the data to be checked which are already checked in the block chain network.
A data verification system construction device is applied to a verification service platform, wherein the verification service platform is configured with a universal template for defining fields and a universal verification component set, and each verification component has the capability of verifying the field value of at least one data type; the verification service platform is connected with at least one data verification demander, the data verification demander has the requirement of verifying data, and the device is used for constructing a verification system aiming at the data to be verified of the target verification demander;
the device comprises:
an interface providing unit: the verification requirement configuration interface is used for providing a verification requirement configuration interface for the target verification demander, and the configuration interface is used for: causing the target verification demander to define one or more fields based on the generic template and, for at least one field defined, select a verification component from the set of generic verification components for verifying that field;
a verification requirement definition unit: the system comprises a configuration interface, a user-defined data structure and a verification component, wherein the configuration interface is used for establishing the user-defined data structure for the data to be verified of the target verification demander according to the operation of the target verification demander based on the configuration interface, and determining the field with verification requirements and the corresponding verification component in the user-defined data structure;
the verification system construction unit: the system comprises a user-defined data structure, a field with verification requirements and a corresponding verification component, wherein the user-defined data structure is used for creating a verification intelligent contract which serves as a data verification system, and the verification intelligent contract is deployed to a blockchain network; the checking intelligent contract is used for checking the data to be checked which are already checked in the block chain network.
In the technical scheme, the evidence storage demander can customize a data structure for the data to be verified by means of a general template and a general verification component set which are pre-deployed in the evidence storage service platform, and select a verification component for verifying at least one field in the data structure so as to specify the relevant configuration of the service scene required by the verification system. Then, the evidence storage service platform can construct a special data verification system for the evidence storage demander based on the relevant configuration of the business scene specified by the evidence storage demander.
The verification-storing service platform is already provided with a general template and a general verification component set in advance as an infrastructure for constructing the verification system, and the verification-storing demanders only need to appoint the relevant configuration of the business scene on the basis of the infrastructure, so that the verification-storing service platform can construct a special verification system for the verification-storing demanders. Therefore, repeated work in the process of developing respective verification systems by different evidence storing demanders is avoided, the workload of developing the verification systems by the evidence storing demanders is reduced, and the development cost is saved.
Drawings
In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the embodiments of the present specification, and other drawings can be obtained by those skilled in the art according to the drawings.
Fig. 1 is a schematic flow chart of a data verification system construction method provided in an embodiment of the present specification;
FIG. 2 is a schematic diagram illustrating a method for constructing a data verification system according to an embodiment of the present disclosure;
FIG. 3 is a flow chart of a data verification method provided in an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of a data verification system building apparatus provided in an embodiment of the present specification;
fig. 5 is a schematic structural diagram of a data verification apparatus provided in an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of an apparatus for configuring a method according to an embodiment of the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the embodiments of the present specification, the technical solutions in the embodiments of the present specification will be described in detail below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all the embodiments. All other embodiments derived by one of ordinary skill in the art from the embodiments given herein are intended to fall within the scope of the disclosure.
At present, for different business scenes, there is a need for business data evidence storage, for example, in a business scene of logistics, in order to ensure safe transportation of goods, a freight company may upload logistics records of freight vehicles to a block chain for evidence storage, so as to determine whether a problem occurs in the transportation process of goods; for another example, in a stock trading business scenario, in order to ensure the security of the trading data, the stock trading platform may upload the trading data to the blockchain in real time for evidence storage after the trading is completed, so as to audit the trading data.
In practical application, the service data to be verified is often required to be verified. The verification may specifically be to verify the authenticity of one or more items of information related to the actual situation included in the service data, or may also be to verify a partial data format and the like included in the service data.
For ease of understanding, two examples of authenticity verification are given below.
Example one: in a logistics business scenario, the business data may be a logistics record uploaded by the freight vehicle upon arrival at the freight transfer station. The logistics record may contain the freight vehicle number, driver name, cargo type, cargo quantity, time information of arrival of the freight vehicle at the freight transfer station. Wherein, whether the time information and the goods quantity are real or not is of great significance to the business. Therefore, the logistics record is verified, and specifically, whether the time information and the quantity of the goods are real or not is verified.
Specifically, the entry/exit record of the freight vehicle a may be searched from the vehicle entry/exit record stored in the freight transfer station system, and the time information of arrival at the freight transfer station of the freight vehicle a may be extracted from the entry/exit record of the freight vehicle a. And then the time information extracted from the access record can be compared with the time information in the logistics record uploaded by the freight vehicle A for verification, and whether the time information is real or not can be determined.
The cargo check record of the freight vehicle A can be searched from the vehicle cargo check record stored in the freight transfer station system, and the quantity of the cargos on the freight vehicle A can be extracted from the cargo check record of the freight vehicle A. And then the quantity of the goods extracted from the check record can be compared with the quantity of the goods in the logistics record uploaded by the freight vehicle A for checking to determine whether the quantity of the goods is real or not.
Example two: in the business scenario of medical insurance, the business data may be a medical insurance policy uploaded by the insurer for applying for medical insurance compensation. The information may include information such as insurance carrier information, medical expenses, and applied compensation amount. The total expense information of the insurer spent on medical treatment can be used for determining the compensation amount of medical insurance, and whether the total expense information is real or not has important significance for business. For example, insurers increase the amount of compensation by forging overhead information. Therefore, the medical insurance policy is verified, and specifically, whether the total overhead information is real or not can be verified.
The method specifically comprises the following steps: the medical bill particulars of the insurer B are obtained from the hospital where the insurer B is located, and the real total expense information of the insurer B can be obtained from the medical bill particulars. And then the total expense information obtained from the medical bill details and the total expense information uploaded by the insurer B can be compared and checked to determine whether the total expense information is real or not.
Aiming at different service scenes, data evidence storing demanders in different service scenes are developed respectively and independently, and customized data verification systems aiming at respective service scenes are developed. The developed data verification system has the capability of verifying the information contained in the business data.
For example, by developing a data verification system, the system can be used to obtain real information and perform verification by comparing the real information with information contained in the business data; it can also be used to verify the format of part of the data contained in the service data.
However, the following technical problems exist in the independent development and verification system of different evidence-storing demanders.
Firstly, each evidence storage demander needs to independently perform the full-flow development of the verification system, which has a high technical threshold, wastes time and labor, and has high development cost.
Second, but in different business scenarios, there may be coincidence of the data types that need to be verified. For example, the type of data that needs to be verified in both the net appointment scenario and the take away scenario includes location information. Therefore, when different data storage and verification demanders independently develop the data verification system respectively, the data verification system can be developed once aiming at the capability of verifying the position information respectively, and from the overall consideration, the data verification system repeatedly develops the verification capability which is only developed once, and development resources are wasted.
In order to solve the above technical problem, the present specification provides a data verification system construction method. Specifically, the method comprises the following steps: aiming at a plurality of data storage and verification demanders, a storage and verification service platform can be arranged to construct a customized verification system for each data storage and verification demander.
The verification service platform can be pre-deployed with a universal verification component set. One of the universal verification components provides at least one verification capability, and the party requiring verification can select a group of verification components and designate an object to be verified for each selected verification component, thereby obtaining a special verification system. Therefore, each evidence storing demander does not need to independently perform the full-flow development of the verification system, but selects a group of verification components which need to be used in the general verification components provided by the evidence storing service platform, so that a large amount of development work is saved, and the development efficiency is improved. In addition, the universal verification component provided by the evidence storage service platform can be repeatedly called by different evidence storage demanders, so that the problem of resource waste caused by repeated development is avoided.
In practical application, the verification system dedicated for each certificate storage demander can be deployed on a certificate storage service platform, and the certificate storage demander submits the data to be verified to the certificate storage service platform for verification and certificate storage. The evidence storage service platform needs to be connected with different evidence storage demanders, and verifies the data to be stored of the different evidence storage demanders based on the universal verification component set.
It should be noted that, in consideration of the fact that the certification service platform needs to be able to extract an object to be verified from the data to be verified of any certification demander, and invoke a corresponding general verification component to verify the extracted object, the certification demander is usually required to register the data structure of the data to be verified of the certification demander to the certification service platform in advance, so that the certification service platform defines the data structure of the data to be verified of the certification demander, and defines which fields in the data structure are the objects to be verified.
Therefore, in one or more embodiments of the present specification, the verification service platform further needs to deploy a general template for defining fields, before constructing the verification system for any verification demander, the verification service platform provides the general template to the verification demander to define the fields, so as to specify a data structure of the data to be verified of the verification demander, and the verification service platform further needs to specify which fields in the data structure are objects to be verified according to an instruction of a user, and which verification component should be called to perform verification on each object to be verified.
From the perspective of the data evidence storage demander, in the method embodiment provided in this specification, the data evidence storage demander may request the evidence storage service platform in advance to construct a dedicated verification system for the data evidence storage demander, and then provide the data to be stored and verified to the evidence storage service platform through the evidence storage interface provided by the evidence storage service platform for the data evidence storage demander. The certificate storage service platform calls a special verification system of a certificate storage demand party to verify the data to be stored on one hand, and stores the data to be stored on the other hand.
In practical application, the data evidence storing demand party is not necessarily the producer of the data to be stored. In some embodiments, the data storage and certification demander may be an independent software developer ISV, which interfaces with at least one data producer, and the ISV is actually based on the verification capability and the certification storage capability of the certification storage service platform to provide data storage service for each data producer. For each data producer, the data producer does not sense the evidence storing service platform behind the ISV, each data producer submits the data to be stored which is produced by the data producer to the ISV, and the ISV further submits the data to be stored to the evidence storing service platform.
In one or more embodiments of the present description, the set of generic verification components deployed on the verification services platform effectively represent various verification capabilities that have been developed in advance, each of which may be used to verify at least one data type.
In particular, each verification component may have the capability to verify a field value for at least one data type, where a data type may specifically characterize a category of data content. In the data structure, a field may correspond to a data content, and the field value is the data content itself, such as location, time, etc.
The verification capability of the verification component specifically includes: acquiring real information in advance or in real time to be checked locally; or checking the data format, the data value range and the like.
The set of generic verification components is typically developed by a verification services platform. For example, in a scenario where verification is authenticity verification, the verification service platform may apply for a real information acquisition authority to a third party storing real information, acquire the real information of the third party in advance based on the authority, store the acquired real information to the local, and develop an assembly for comparing input data with the real information and verifying the input data. Of course, a component for acquiring real information from a third party in real time for comparison and verification of input data may be developed based on the real information acquisition authority.
The following explains a method for constructing a data verification system provided in the present specification in detail with reference to the accompanying drawings.
Fig. 1 is a schematic flow chart of a method for constructing a data verification system provided in this specification. The method can be applied to a certificate storage service platform.
The presence service platform may be configured with a generic template for defining fields and a set of generic verification components, each verification component may have the capability to verify field values of at least one data type.
The evidence storage service platform can be connected with at least one data evidence storage demand party, and the method flow can be used for constructing a data verification system aiming at the data to be stored of the target evidence storage demand party.
It should be noted that the flow of the method explains a process of constructing the data verification system for a single data storage certification demander (i.e. a target storage certification demander), and it can be understood that the data verification system can be constructed based on the same steps for other data storage certification demanders.
The method may comprise at least the following steps.
S101: the verification service platform provides a verification requirement configuration interface for the target verification demander.
In an alternative embodiment, the target certificate storing demander may comprise an independent software developer ISV. The ISV may interface with at least one data producer and need to provide a solution for data verification for the data producer. And the ISV can be developed by the evidence storage service platform in the process of the method. The data to be stored can be data produced by any data producer.
The configuration interface may be for: one or more fields are defined based on the generic template, and for at least one field defined, a verification component for verifying the field is selected from a set of generic verification components.
Specifically, the target authentication demander receives the general template and the general verification component set sent by the authentication service platform through the configuration interface, and then executes operations such as defining fields, selecting verification components and the like by the template authentication demander, and sends the defined one or more fields, the selected verification components and the corresponding verified fields to the authentication service platform through the configuration interface.
Optionally, the providing of the configuration interface may specifically be a providing of a visual interface, the visual interface may include a general template and a general verification component set, and the graphical operation result of the target evidence storage requirement policy on the visual interface is sent to the evidence storage service platform through the interface configured for the visual interface.
The graphical operation may specifically include, for one or more defined fields, dragging the specified field over a verification component specified in the set of generic verification components for verifying the field, thereby selecting a verification component for verifying the field.
Obviously, the graphical operation can reduce the operation threshold of the data evidence storage demander and can reduce the operation difficulty of the data evidence storage demander.
Optionally, the configuration interface may be a data interaction interface between the target inventory demander and the inventory service platform for interacting the generic template, the set of generic verification components, the defined fields, and the selected verification components.
Wherein, the universal verification component set can be configured in the following way. Take the case where the verification component is developed based on a verification third party with verification capability as an example.
Optionally, the verification service platform may receive verification service access applications submitted by a plurality of verification third parties respectively; different verifying third parties have the ability to verify field values of different data types. Such as the ability to verify against location data, and the ability to verify against transaction data. For each verification third party, generating and configuring at least one verification component based on the verification capability of the verification third party.
Optionally, the verification service platform may apply for the real information acquisition permission (i.e., capability of performing verification) to a plurality of verification third parties, and in case of successful application, generate and configure one or more verification components for each permission. The verification component can utilize the real information to obtain the authority to obtain the real information of the verification third party in advance or in real time and then verify the real information.
S102: the verification storage service platform creates a custom data structure for the data to be verified of the target verification storage demander according to the operation of the target verification storage demander based on the configuration interface, and determines a field with verification requirements and a corresponding verification component in the custom data structure.
The operation of the target certificate storage demander based on the configuration interface comprises the following steps: one or more fields are defined based on the generic template, and for at least one field defined, a verification component for verifying the field is selected from a set of generic verification components.
Based on all the fields defined in the operation, the credentialing service platform can create a custom data structure. The field selected for verification during operation may be determined as a field having a verification requirement in the customized data structure, and further, a verification component corresponding to the field having the verification requirement may be obtained according to the verification component determined during operation.
S103: and the verification storage service platform constructs a data verification system according to the created custom data structure, the field with the verification requirement and the corresponding verification component, and returns a calling identifier for calling the data verification system to the target verification storage demander.
The constructed data verification system can be used for acquiring field values with verification requirements from a custom data structure, calling verification capabilities of corresponding verification components and performing verification aiming at the acquired field values.
Due to the fact that the operation executed by the different constructed verification systems is communicated in nature, the method can comprise the steps of extracting data and calling a verification component to perform verification. Therefore, optionally, in order to further save development cost, the evidence storage service platform may be constructed according to the same basic verification system template configured in advance.
The verification service platform can develop a universal basic verification system template, and different customized information, such as a custom data structure, a field with verification requirements and a corresponding verification component, can be filled into the universal basic verification system template aiming at different verification demanders, so that a customized verification system is constructed and used for verifying to-be-verified data of the verification demanders.
Obviously, aiming at different evidence storage demanders, the evidence storage service platform can reuse the basic verification system template to carry out system construction, on one hand, only the basic verification system template needs to be developed once, development cost is saved, on the other hand, the customized verification system can be quickly constructed based on template filling customized information, and development efficiency is improved.
For ease of understanding, in one specific example, the base verification system template may be a code template to be populated at the code level. The code template cannot be directly run, and the executable code is obtained after partial data needs to be filled in, so that the code can realize specific functions during running.
An example of pseudo code for a code template for extracting data is given below: determining a data structure of 'data structure unique identification' ═ (); a field value of 'field name' ═ () is queried in the data structure.
The bracket part can be filled with data according to actual conditions, so that the executable code is obtained. For example, a data structure of '001' is determined as the 'data structure unique identification'; a field value of 'field name ═ vehicle location' is queried in the data structure. The code may enable, at run-time, extraction of specified data from the business data.
However, the specific representation of the attribute information contained in the fields and the data structure may not be the same in the service data of different certificate storing demanders. For example, the field name may be represented by 'field name' or 'code' in different service data; the data structure is uniquely identified in different service data, and may be represented by 'unique id' or 'structID'.
However, when the verification service platform develops the basic verification system template, it is usually difficult to see the specific representation of the attribute information contained in the fields and the data structures in different verification demanders, and the basic verification system template is developed according to the customized representation. For example, a data structure of 'unique id' ═ () is determined; a field value of 'code' ═ () is looked up in the data structure.
Obviously, if the representation of the attribute information contained in the field and the data structure in the to-be-stored data of the storage demand party is different from the representation of the basic verification system template, the constructed verification system cannot process the to-be-stored data. For example, for the data to be stored, which uses 'structID' to represent the unique identifier of the data structure, the value of 'unique queid' cannot be determined, and the data to be stored cannot be processed.
Therefore, in the method provided by the present specification, the general template for defining the fields can be further utilized to redefine the business data of different storage and verification demanders, unify the attribute information representation of the fields of the business data, and further unify the attribute information representation of the data structure of each business data to make the attribute information representation of each business data the same as that of the basic verification system template, so that the verification system constructed based on the basic verification system template can verify the business data of different storage and verification demanders, and the development cost is saved.
To facilitate further understanding, a specific example is given below.
The generic template may specifically be { idx: () (ii) a code: () (ii) a type: () (ii) a required: () (ii) a maxSize: () (ii) a minSize: () And idx represents a field unique identifier, code represents a field name, type represents a data type of a field value, required represents whether the field is required, maxSize represents a maximum value of a field value, and minSize represents a minimum value of the field value. Some of the attribute information may be defaulted.
The generic template may be used to define an attribute information representation of a field. The data evidence demander may fill in the parenthesized portion thereof with data defining one or more fields.
The following is an example of 3 fields defined based on the above-described generic template.
{idx：‘001’；code：‘companyName’；type：‘String’；required：‘True’}；{idx：‘002’；code：‘companyID’；type：‘String’；required：‘True’；maxSize：‘100’；minSize：‘0’}；{idx：‘003’；code：‘companyLocation’；type：‘String’；required：‘True’}。
After the data evidence storing requiring party defines the 3 fields, the data evidence storing requiring party can send the data evidence storing requiring party to the evidence storing service platform. The evidence storing service platform fills the 3 fields and partial information into a data structure template.
The data structure template may specifically be { uniqueID: () (ii) a version: () (ii) a author: () (ii) a createTime: () (ii) a dataItems: ()}. Wherein uniqueID represents a unique identifier of the data structure, version represents a version number of the data structure, author represents a creator of the data structure (which may be a data evidence demander), createTime represents a creation time of the data structure, and dataItems represents data content contained in the data structure, which may include one or more field contents.
After padding, the data structure may be { unique queid: '001'; version: '1.1'; an author: 'Tom'; createTime: '20210201'; dataItems: "{ idx: '001'; code: 'companyName'; type: 'String'; required: 'True' }; { idx: '002'; code: 'company ID'; type: 'String'; required: 'True'; maxSize: '100'; minSize: '0' }; { idx: '003'; code: 'company location'; type: 'String'; required: 'True' }.
Obviously, for different data to be verified represented by the attribute information with uniform fields and data structures, the verification service platform can utilize the basic verification system template to construct a verification system and perform verification.
Generally, the data verification system can be deployed on the storage and verification service platform, so that local verification components of the storage and verification service platform can be called conveniently. In this embodiment, the storage service platform may include a plurality of data verification systems, and may be distinguished by using the call identifier.
Correspondingly, the calling identifier may specifically be a unique identifier of the custom data structure, so that the corresponding custom data structure and the corresponding data verification system are uniquely determined according to the identifier.
The calling identifier may also be specifically a unique identifier of the data verification system, so that the corresponding data verification system is uniquely determined in the plurality of data verification systems locally deployed on the presence verification service platform according to the identifier. When the verification is carried out subsequently, the data verification demander can send the calling identifier and the service data to be verified to the verification service platform together, so that the data verification system can be conveniently determined according to the calling identifier.
In addition, the verification system can also be deployed outside the storage and authentication service platform.
For example, the data verification system may be deployed in a data storage and verification demand party, and may directly verify the service data to be stored. If a plurality of data verification systems are deployed in the same data storage and verification demand party, the data verification systems can be distinguished by calling the identifiers. More specifically, the data storage requirement party may directly invoke the locally deployed corresponding data verification system to verify the service data to be stored based on the invocation identifier. When the verification component is to be used for verification, the verification component can be deployed on the verification service platform, so that the business data to be verified needs to be sent to the verification component in the verification service platform for verification. Optionally, when the data verification system is deployed to the data verification demander, the verification component may also be deployed to the data verification demander, so that the service data does not need to be sent to the verification service platform for verification.
For another example, in an embodiment where the verification service platform utilizes the blockchain network for data verification, the data verification system may also be deployed in the blockchain network. For example, a verification intelligent contract can be generated according to the constructed custom data structure, the field with the verification requirement and the corresponding verification component, and the verification intelligent contract is deployed to the block chain network. The intelligent contract verification method comprises the steps of verifying the intelligent contract, and obtaining verification capability through calling a verification component of the verification service platform.
The verification system obtained based on the intelligent contract can realize credible distributed verification of the data to be verified by the block chain network, and improves the credibility of the data verification system.
Correspondingly, the calling identifier may include: and the link identification corresponding to the block link network is associated with the contract identification corresponding to the verification intelligent contract deployed in the block link network. By utilizing the calling identifier, a block chain can be determined according to the chain identifier, and then the corresponding check intelligent contract on the block chain is determined according to the contract identifier.
Of course, when only one blockchain is included in the blockchain network, the invocation identifier may only include the contract identifier corresponding to the verification smart contract.
In the process of the method, a storage and verification demander can customize a data structure for the data to be verified by means of a general template and a general verification component set which are pre-deployed in a storage and verification service platform, and select a verification component for verifying at least one field in the data structure so as to specify the relevant configuration of a service scene required for constructing a verification system. Then, the evidence storage service platform can construct a special data verification system for the evidence storage demander based on the relevant configuration of the business scene specified by the evidence storage demander.
The verification-storing service platform is already provided with a general template and a general verification component set in advance as an infrastructure for constructing the verification system, and the verification-storing demanders only need to appoint the relevant configuration of the business scene on the basis of the infrastructure, so that the verification-storing service platform can construct a special verification system for the verification-storing demanders. Therefore, repeated work in the process of developing respective verification systems by different evidence storing demanders is avoided, for example, the repeated work is the capability of repeatedly developing and verifying the same information by different evidence storing demanders, the workload of developing and verifying systems by the evidence storing demanders is reduced, and the development cost is saved.
In addition, any data storage and verification demander can construct a customized data verification system by the storage and verification service platform by means of the storage and verification service platform only by determining customized information such as fields and verification components for verifying the fields, and the operation of the data storage and verification demander is greatly simplified.
Furthermore, the data evidence storage demander can utilize the graphical operation of a visual interface to further reduce the operation threshold and difficulty, does not need to know programming knowledge, and is convenient for the data evidence storage demander to operate.
In addition, in order to improve the verification efficiency, the verification service platform can also provide some simple data screening logics, and the logics are added into the data verification system after being specified by the data verification demander, so that the business data to be verified can continue subsequent verification after passing through the data screening.
Simple data filtering logic, for example, restricts the format of a field value, and restricts the value range of a field. Specifically, the format of the position data can be limited to longitude and latitude, and the value range of the transaction data is limited to 0-50000.
The data verification demand party can specify a format or a value range, and the verification service platform generates corresponding data screening logic to be added into the data verification system, so that verification can be performed on the screened business data conveniently, unreal data can be directly determined on the business data which does not pass the screening, subsequent verification is not needed, and verification efficiency can be improved.
The specification also provides an application embodiment. Fig. 2 is a schematic diagram illustrating a method for constructing a data verification system according to the present disclosure. The system comprises a user, a certificate storage service platform and a block chain network.
The evidence storage service platform provides a visual interface for a user. The visual interface comprises a universal template and all verification components deployed on the evidence storage service platform.
The user may enter a plurality of business related fields in a common template in the visualization interface and specify a partial verification component for verifying the entered partial fields.
The deposit and verification service platform receives an operation result of a user through a configuration interface in a visual interface, generates a self-defined data structure based on a plurality of input fields, generates a verification intelligent contract based on the self-defined data structure, a specified verification component and a part of fields to be verified in the self-defined data structure, deploys the verification intelligent contract into a block chain network, receives and returns a contract identifier to the user, and the contract identifier can be used for calling the verification intelligent contract.
The data verification system constructed based on the method flow also provides a data verification method.
Fig. 3 is a schematic flow chart of a data verification method provided in this specification. The method may comprise at least the following steps.
S201: and the certificate storing service platform receives the data certificate storing request.
The data verification request specifies data to be verified and a calling identifier for calling the data verification system.
The calling identifier can be received by the data storage certification demander after the data storage certification service platform constructs the data verification system.
S202: and the verification storage service platform calls the corresponding data verification system based on the specified calling identifier in the data verification request.
Based on the explanation of the construction method flow of the data verification system, the calling identifier can be the only identifier of the data verification system. Optionally, the verification service platform may uniquely determine a corresponding data verification system among the plurality of data verification systems according to the call identifier.
The invocation identification may also include an association of the chain identification with the contract identification. Alternatively, the data verification system may be deployed as an intelligent contract in a blockchain network. The evidence-storing service platform can submit to the block chain network corresponding to the chain identifier: and packaging the transaction based on the data to be stored and certified. The transaction is used for calling the verification intelligent contract corresponding to the contract identification so as to verify the data to be stored.
S203: the called data verification system verifies the data to be stored specified in the data storage request.
Wherein, the specific data to be verified and stored may include: based on a self-defined data structure configured in the data verification system and the field with verification requirements, the field value of the field with the verification requirements is analyzed from the data to be verified, and a corresponding verification component is called to verify the analyzed field value.
In the above method flow, if the data to be stored is verified, the data to be stored can be stored. For example, when the verification result representation passes, the data to be stored is packaged into a transaction and submitted to the blockchain network for storage.
Certainly, in some embodiments, the data to be stored and the verification result may be directly stored without paying attention to whether the data to be stored passes the verification. For example, the verification service platform may obtain a verification result from the data verification system; and the certificate storage service platform encapsulates the data to be verified and the verification result into transaction and submits the transaction to the block chain network for certificate storage. The subsequent data storage certification demander can determine whether the data to be stored is real or not according to the verification result of the storage certification.
When storing the evidence data, the data to be stored can be stored in the blockchain network. Of course, centralized storage of the data to be stored with the certificate may be performed, and the specification does not limit the manner of storing the certificate data.
It should be noted that, in the embodiment of checking the data to be checked by using the checking intelligent contract, in order to run the intelligent contract, the data to be checked needs to be packaged into the transaction and further stored into the blockchain network, so that the data to be checked by using the checking intelligent contract can be checked. No matter whether the verification result of the verification intelligent contract represents that the verification passes or fails, the blockchain network writes the transaction where the data to be stored is located into the blockchain, and anchors the verification result corresponding to the transaction into the blockchain.
Further, in embodiments where data is certified to a blockchain and a verification system is built with intelligent contracts, the blockchain used for certification and the blockchain used for deploying the intelligent contracts may not be the same blockchain.
For example, the verification service platform may encapsulate data to be verified into a first transaction, store the data into a first blockchain, encapsulate the data into a second transaction by using a calling identifier (specifically, a contract identifier) and a summary of the first transaction, send the second transaction to a blockchain network that maintains the second blockchain, further call a verification intelligent contract deployed in the second blockchain, and obtain the first transaction in the first blockchain by crossing chains of the verification intelligent contract, further obtain the data to be verified, and perform verification. Thus, the data to be verified is actually verified in the first blockchain, and the verification result is verified in the second blockchain.
For the data to be stored in the method flow, as the data to be stored can be the business data of the data storage demand party, the data to be stored may have a confidential demand, and other problems caused by business data leakage are avoided. For example, private data may exist in part of the business data, and revealing the private data may result in loss of the party requiring data evidence.
In an alternative embodiment, in order to protect the data to be stored from being leaked, the device in which the data verification system is located may be provided with a trusted execution area.
The trusted execution area can be provided with independent computing resources and a storage area, the computing process in the trusted execution area cannot be leaked, the input and output of data in the trusted execution area are strictly limited, and the trusted execution area can be used for verifying the data, so that the plaintext of the data to be verified cannot be leaked to the data verification system.
In addition, the trusted execution area can also be provided with an independent public and private key, and the data verification system cannot acquire the private key of the trusted execution area. Specifically, the data verification system may generate a public key and a private key in the trusted execution area in advance, and keep the private key in the trusted execution area.
And the data to be stored may include: and encrypting the data plaintext to be stored with the certificate by using the public key of the trusted execution area to obtain the data ciphertext to be stored with the certificate.
Correspondingly, the data verification system verifies the data to be verified, and may include: in the trusted execution region, decrypting the ciphertext of the data to be stored and authenticated to obtain the plaintext of the data to be stored and authenticated; and checking the plaintext of the data to be verified in the trusted execution area. Specifically, the verification component is called in the trusted execution area to verify the plaintext of the data to be verified.
Before and after the whole verification process, the data verification system cannot acquire the plaintext of the data to be verified.
In addition, if the data to be stored is required to be sent to the blockchain network for storing the certificate, since the data in the blockchain network is public, the data to be stored also needs to be encrypted.
Optionally, the plaintext of the data to be stored with the certificate may be encrypted by using the public key of the party requiring the data storage certificate in the trusted execution region, and the encrypted ciphertext may be stored in the block chain network, so that only the party requiring the data storage certificate may decrypt the ciphertext in the block chain network to obtain the plaintext of the data to be stored with the certificate.
Or encrypting the plaintext of the data to be stored in the trusted execution region by using the public key of the block chain network, and storing the encrypted ciphertext into the block chain network. When the subsequent data certificate storage requiring party needs to use the certified data, the subsequent data certificate storage requiring party can apply the block chain network to decrypt the ciphertext to obtain the plaintext of the data to be verified.
In addition to the above-described method flow, the present specification also provides two apparatus embodiments.
The apparatus comprises a first apparatus.
Fig. 4 is a schematic structural diagram of a data verification system construction device provided in this specification. The device can be applied to a deposit service platform, the deposit service platform can be configured with a general template for defining fields and a general verification component set, and each verification component can have the capability of verifying the field value of at least one data type; the evidence storing service platform can be used for docking at least one data evidence storing demander, and the device can be used for constructing a verification system aiming at the data to be stored of the target evidence storing demander.
The apparatus may specifically include the following elements.
The interface providing unit 301: the verification requirement configuration interface is used for providing a verification requirement configuration interface for a target verification requirement party, and the configuration interface is used for: one or more fields are defined based on the generic template, and for at least one field defined, a verification component for verifying the field is selected from a set of generic verification components.
Verification requirement definition unit 302: the method is used for creating a custom data structure for the data to be stored of the target storage and certification demander according to the operation of the target storage and certification demander based on the configuration interface, and determining a field with a verification requirement and a corresponding verification component in the custom data structure.
Verification system construction unit 303: and the system is used for constructing a data verification system according to the created custom data structure, the field with verification requirements and the corresponding verification component, and returning a calling identifier for calling the data verification system to the target verification-storing demander.
Wherein, the target deposit certificate demander can comprise: independent software developers ISV; the ISV can be connected with at least one data producer, and the data to be stored can be data produced by any data producer.
The configuration method of the universal verification component set can comprise the following steps: receiving verification service access applications respectively submitted by a plurality of verification third parties; different verification third parties have the capability of verifying field values of different data types; for each verification third party, at least one verification component is configured based on the verification capabilities of the verification third party.
The verification system construction unit 303 may specifically be configured to: generating an intelligent check contract according to the constructed custom data structure, the field with the check requirement and the corresponding check component, and deploying the intelligent check contract to the blockchain network; the verification intelligent contract obtains verification capability by calling a verification component of the verification service platform. Correspondingly, the calling identifier may include: and the link identification corresponding to the block link network is associated with the contract identification corresponding to the verification intelligent contract deployed in the block link network.
For further explanation of the embodiment of the present apparatus, reference may be made to the above method flow.
Embodiment two of the device.
Fig. 5 is a schematic structural diagram of a data verification apparatus provided in this specification. The device can be applied to a certificate storage service platform and specifically comprises the following units.
The receiving unit 401: for receiving a data credentialing request. The data verification request specifies data to be verified and a calling identifier for calling the data verification system.
The calling unit 402: and the data verification system is used for calling the corresponding data verification system to verify the specified data to be stored based on the specified calling identifier.
Verifying the specified data to be stored may include: based on a self-defined data structure configured in the data verification system and a field with verification requirements, a field value with the verification requirements is analyzed from the data to be verified, and a corresponding verification component is called to verify the analyzed field value.
The data verification system may have a trusted execution area, and the data verification system may generate a public key and a private key in the trusted execution area in advance, and retain the private key in the trusted execution area. The data to be stored may include: and encrypting the data plaintext to be certified by using the public key of the trusted execution area to obtain the data ciphertext to be certified.
The verifying the specified data to be stored may specifically include: in the trusted execution region, decrypting the ciphertext of the data to be stored and authenticated to obtain the plaintext of the data to be stored and authenticated; and checking the plaintext of the data to be verified in the trusted execution area.
In the case that the calling identifier includes an association relationship between a chain identifier and a contract identifier, the calling unit 402 may specifically be configured to: submitting to the block chain network corresponding to the chain identification: packaging the transaction based on the data to be stored and certified; the transaction is used for calling the verification intelligent contract corresponding to the contract identification so as to verify the data to be stored.
The invoking unit 402 may also be configured to: obtaining a verification result from the data verification system; packaging the data to be stored and the verification result into a transaction and submitting the transaction to the block chain network; or, under the condition that the verification result representation passes, packaging the data to be stored into a transaction and submitting the transaction to the blockchain network.
For further explanation of the embodiments of the present device, reference may be made to the above-mentioned method flows.
The embodiment of the present specification further provides a computer device, which at least includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the program to implement a data verification system construction method or an operation performed by a storage and verification service platform in a data verification method.
Fig. 6 is a schematic diagram illustrating a more specific hardware structure of a computer device according to an embodiment of the present disclosure, where the device may include: a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050. Wherein the processor 1010, memory 1020, input/output interface 1030, and communication interface 1040 are communicatively coupled to each other within the device via bus 1050.
The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solutions provided in the embodiments of the present disclosure.
The Memory 1020 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, or the like. The memory 1020 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present specification is implemented by software or firmware, the relevant program codes are stored in the memory 1020 and called to be executed by the processor 1010.
The input/output interface 1030 is used for connecting an input/output module to input and output information. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. Wherein the input devices may include a keyboard, mouse, touch screen, microphone, various sensors, etc., and the output devices may include a display, speaker, vibrator, indicator light, etc.
The communication interface 1040 is used for connecting a communication module (not shown in the drawings) to implement communication interaction between the present device and other devices. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, Bluetooth and the like).
Bus 1050 includes a path that transfers information between various components of the device, such as processor 1010, memory 1020, input/output interface 1030, and communication interface 1040.
It should be noted that although the above-mentioned device only shows the processor 1010, the memory 1020, the input/output interface 1030, the communication interface 1040 and the bus 1050, in a specific implementation, the device may also include other components necessary for normal operation. In addition, those skilled in the art will appreciate that the above-described apparatus may also include only those components necessary to implement the embodiments of the present description, and not necessarily all of the components shown in the figures.
Embodiments of the present specification further provide a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a data verification system construction method or an operation performed by a storage certification service platform in the data verification method.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
From the above description of the embodiments, it is clear to those skilled in the art that the embodiments of the present disclosure can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the embodiments of the present specification or portions thereof contributing to the prior art may be embodied in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, or the like, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods described in the embodiments or some portions of the embodiments of the present specification.
The systems, apparatuses, modules or units described in the above embodiments may be specifically implemented by a computer chip or an entity, or implemented by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the apparatus embodiments are substantially similar to the method embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the description of the method embodiments for relevant points. The above-described apparatus embodiments are merely illustrative, and the modules described as separate components may or may not be physically separate, and the functions of the modules may be implemented in one or more software and/or hardware when implementing the embodiments of the present disclosure. And part or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The foregoing is only a detailed description of the embodiments of the present disclosure, and it should be noted that, for those skilled in the art, many modifications and decorations can be made without departing from the principle of the embodiments of the present disclosure, and these modifications and decorations should also be regarded as protection for the embodiments of the present disclosure.

Claims (17)

1. A data verification system construction method is applied to a verification service platform, the verification service platform is configured with a universal template and a universal verification component set, the universal template is used for defining fields, and each verification component has the capability of verifying the authenticity of the field value of at least one data type; the verification service platform is connected with at least one data verification demander, the data verification demander has the requirement of verifying data, and the method is used for constructing a verification system aiming at the data to be verified of a target verification demander;
the method comprises the following steps:
providing a verification requirement configuration interface for the target storage certification demander, wherein the configuration interface is used for: causing the target verification demander to define one or more fields based on the generic template and, for at least one field defined, select a verification component from the set of generic verification components for verifying that field;
according to the operation of the target evidence storage demander based on the configuration interface, a custom data structure is created for the data to be stored of the target evidence storage demander, and a field with verification requirements and a corresponding verification component in the custom data structure are determined;
generating an intelligent check contract serving as a data check system according to the created custom data structure, the field with the check requirement and the corresponding check component, and deploying the intelligent check contract to a blockchain network; the checking intelligent contract is used for checking the data to be checked which are already checked in the block chain network.
2. The method of claim 1, after deploying the verification intelligence contract to a blockchain network, further comprising:
and returning the data verification system and/or the calling identifier for calling the data verification system to the target certificate storage demander.
3. The method of claim 1, wherein the verification intelligence contract is configured to verify a verification result into the blockchain network.
4. The method of claim 1, further comprising: adding data screening logic specified by the target storage demander to the data verification system;
and the verification intelligent contract is used for verifying the data which is screened by the data screening logic in the data to be stored and verified.
5. The method of claim 1, wherein said verification requirements configuration interface comprises a visualization interface; the visual interface comprises the universal template and the universal verification component set;
the operation of the party requiring the evidence according to the target deposit evidence based on the configuration interface comprises the following steps: and according to the graphical operation of the target evidence storage demander based on the visual interface.
6. The method of claim 1, wherein generating a verification intelligence contract as a data verification system according to the created custom data structure, the fields with verification requirements and the corresponding verification components comprises:
and filling the created custom data structure, the field with the verification requirement and the corresponding verification component into a universal basic verification system template to generate a verification intelligent contract as a data verification system.
7. The method of claim 1, wherein the target certificate-storing demander comprises:
independent software developers ISV; the ISV is in butt joint with at least one data producer, and the data to be stored is data produced by any data producer.
8. The method of claim 1, wherein the set of generic verification components is configured by:
receiving check service access applications respectively submitted by a plurality of check third parties; different verification third parties have the capability of verifying field values of different data types;
for each verification third party, at least one verification component is configured based on the verification capabilities of the verification third party.
9. The method of claim 1, wherein the verification intelligence contract obtains verification capabilities by invoking a verification component of the verification services platform.
10. The method of claim 2, wherein said calling an identifier comprises:
and the association relationship between the chain identifier corresponding to the block chain network and the contract identifier corresponding to the check intelligent contract deployed in the block chain network.
11. A data verification method based on the data verification system according to any one of claims 1 to 9, comprising:
the certificate storing service platform receives a data certificate storing request; the data authentication request specifies data to be authenticated and a calling identifier for calling a data verification system;
the certificate storing service platform calls a corresponding data verification system based on the appointed calling identification;
the called data verification system verifies the appointed data to be stored and verified, and the verification method comprises the following steps: based on a self-defined data structure configured in the data verification system and a field with verification requirements, a field value with verification requirements is analyzed from the data to be verified, and a corresponding verification component is called to verify the analyzed field value.
12. The method of claim 11, wherein the data verification system has a trusted execution area, wherein the data verification system generates a public key and a private key in the trusted execution area in advance, and wherein the private key is retained in the trusted execution area;
the data to be stored with evidence comprises: encrypting the plaintext of the data to be stored with the public key to obtain ciphertext of the data to be stored with the certificate;
the data verification system verifies the data to be stored, and comprises:
in the trusted execution region, decrypting the to-be-stored data ciphertext to obtain the to-be-stored data plaintext;
and verifying the plaintext of the data to be stored in the trusted execution area.
13. The method of claim 11, wherein said calling identification comprises: the incidence relation between the chain identification and the contract identification;
the certificate storing service platform calls a corresponding data verification system based on the calling identifier, and the method comprises the following steps:
and the evidence storage service platform submits to the block chain network corresponding to the chain identifier: the transaction packaged based on the data to be stored and certified; and the transaction is used for calling the verification intelligent contract corresponding to the contract identification so as to verify the data to be verified.
14. The method as recited in claim 11, further comprising:
the verification service platform acquires a verification result from the data verification system;
the certificate storage service platform encapsulates the data to be verified and the verification result into a transaction and submits the transaction to a block chain network; or, under the condition that the verification result representation passes, packaging the data to be stored into a transaction and submitting the transaction to the block chain network.
15. A data verification system construction device is applied to a verification service platform, wherein the verification service platform is configured with a universal template for defining fields and a universal verification component set, and each verification component has the capability of verifying the field value of at least one data type; the verification service platform is connected with at least one data verification demander, the data verification demander has the requirement of verifying data, and the device is used for constructing a verification system aiming at the data to be verified of the target verification demander;
the device comprises:
an interface providing unit: the verification requirement configuration interface is used for providing a verification requirement configuration interface for the target verification demander, and the configuration interface is used for: causing the target verification demander to define one or more fields based on the generic template and, for at least one field defined, select a verification component from the set of generic verification components for verifying that field;
a verification requirement definition unit: the system comprises a configuration interface, a user-defined data structure and a verification component, wherein the configuration interface is used for establishing the user-defined data structure for the data to be verified of the target verification demander according to the operation of the target verification demander based on the configuration interface, and determining the field with verification requirements and the corresponding verification component in the user-defined data structure;
the verification system construction unit: the system comprises a user-defined data structure, a field with verification requirements and a corresponding verification component, wherein the user-defined data structure is used for creating a verification intelligent contract which serves as a data verification system, and the verification intelligent contract is deployed to a blockchain network; the checking intelligent contract is used for checking the data to be checked which are already checked in the block chain network.
16. A data verification device based on the data verification system of claim 15, applied to a verification service platform; the device comprises:
a receiving unit: the data authentication server is used for receiving a data authentication request; the data authentication request specifies data to be authenticated and a calling identifier for calling a data verification system;
a calling unit: the method is used for calling a corresponding data verification system to verify the appointed data to be stored based on the appointed calling identification, and the verification of the appointed data to be stored comprises the following steps: based on a self-defined data structure configured in the data verification system and a field with verification requirements, a field value with verification requirements is analyzed from the data to be verified, and a corresponding verification component is called to verify the analyzed field value.
17. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the program implements the functionality of the LC service platform as claimed in any one of claims 1 to 14.
CN202210272352.7A 2021-03-05 2021-03-05 Data verification system construction method and device Pending CN114662128A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210272352.7A CN114662128A (en) 2021-03-05 2021-03-05 Data verification system construction method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210272352.7A CN114662128A (en) 2021-03-05 2021-03-05 Data verification system construction method and device
CN202110243837.9A CN112613063B (en) 2021-03-05 2021-03-05 Data verification system construction method and device

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
CN202110243837.9A Division CN112613063B (en) 2021-03-05 2021-03-05 Data verification system construction method and device

Publications (1)

Publication Number Publication Date
CN114662128A true CN114662128A (en) 2022-06-24

Family

ID=75254509

Family Applications (2)

Application Number Title Priority Date Filing Date
CN202210272352.7A Pending CN114662128A (en) 2021-03-05 2021-03-05 Data verification system construction method and device
CN202110243837.9A Active CN112613063B (en) 2021-03-05 2021-03-05 Data verification system construction method and device

Family Applications After (1)

Application Number Title Priority Date Filing Date
CN202110243837.9A Active CN112613063B (en) 2021-03-05 2021-03-05 Data verification system construction method and device

Country Status (1)

Country Link
CN (2) CN114662128A (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113536342B (en) * 2021-07-06 2024-03-26 招商银行股份有限公司 Block chain-based certificate management method, system, program product and storage medium

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109657486A (en) * 2018-12-18 2019-04-19 青岛轮子软件科技有限公司 A kind of financial institution's user data sharing method and system based on block chain technology
CN112015739A (en) * 2020-09-14 2020-12-01 支付宝(杭州)信息技术有限公司 Data verification and data query method and device
CN112016924A (en) * 2020-10-21 2020-12-01 支付宝(杭州)信息技术有限公司 Data evidence storage method, device and equipment based on block chain
CN112380213B (en) * 2020-11-13 2022-11-15 苏宁云计算有限公司 Information acquisition method and device, computer equipment and storage medium

Also Published As

Publication number Publication date
CN112613063A (en) 2021-04-06
CN112613063B (en) 2022-02-18

Similar Documents

Publication Publication Date Title
CN109981679B (en) Method and apparatus for performing transactions in a blockchain network
US10558963B2 (en) Shareable widget interface to mobile wallet functions
US10269011B2 (en) Configuring a plurality of security isolated wallet containers on a single mobile device
US20190266604A1 (en) Configuring a plurality of security isolated wallet containers on a single mobile device
US10032160B2 (en) Isolating distinct service provider widgets within a wallet container
CN109246197B (en) Data processing method and device based on intelligent contract
CN113014475B (en) Message pushing integration method and device
CN111090581B (en) Intelligent contract testing method, intelligent contract testing device, computer equipment and storage medium
US20210319456A1 (en) Methods, apparatuses, devices, and systems for generating customs clearance confirmation information
CN111814172A (en) Method, device and equipment for acquiring data authorization information
CN111985007A (en) Contract signing and executing method and device based on block chain
CN112200569A (en) Block chain-based digital seal using method and device and electronic equipment
CN112613063B (en) Data verification system construction method and device
CN114239066A (en) Contract processing method based on block chain and related equipment
CN115018499A (en) Block chain-based digital certificate issuing method, device and system
CN113868691A (en) Authorized operation method and device of block chain based on cloud-native technology
CN106648770A (en) Generating method, loading method and device for application program installation package
CN116980182B (en) Abnormal request detection method and device and electronic equipment
CN117032727B (en) File compiling method, device, equipment, medium and product based on block chain
CN117495559A (en) Transaction processing method, device, equipment and storage medium
CN117974033A (en) Distributed account book-based selection test method and related device
CN114418578A (en) Block chain account risk query method and device
CN114565461A (en) Method and device for processing digital resources by system based on block chain
CN116126451A (en) Federal learning workflow construction method based on blockchain network and related equipment
CN113761496A (en) Identity verification method and device based on block chain and electronic equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination