CN112507395A - Information verification method, system, device, server and medium - Google Patents
Information verification method, system, device, server and medium Download PDFInfo
- Publication number
- CN112507395A CN112507395A CN202011503611.XA CN202011503611A CN112507395A CN 112507395 A CN112507395 A CN 112507395A CN 202011503611 A CN202011503611 A CN 202011503611A CN 112507395 A CN112507395 A CN 112507395A
- Authority
- CN
- China
- Prior art keywords
- information
- server
- verification
- hash value
- file
- 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
Links
- 238000012795 verification Methods 0.000 title claims abstract description 252
- 238000000034 method Methods 0.000 title claims abstract description 45
- 238000004590 computer program Methods 0.000 claims description 21
- 230000004044 response Effects 0.000 claims description 21
- 238000012790 confirmation Methods 0.000 claims description 18
- 239000000284 extract Substances 0.000 claims description 7
- 238000010200 validation analysis Methods 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 6
- 230000007246 mechanism Effects 0.000 description 5
- 230000003993 interaction Effects 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004321 preservation Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
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/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- 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/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Finance (AREA)
- Accounting & Taxation (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Development Economics (AREA)
- Computer Hardware Design (AREA)
- Data Mining & Analysis (AREA)
- General Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application is applicable to the technical field of computers, and provides an information verification method, which comprises the following steps: receiving a verification request sent by a target server, wherein the verification request comprises information to be verified, the number of the information to be verified and type indication information for indicating the verification type, which are requested to be verified; sending the verification request to a block chain so as to send the verification request to a verification server matched with the verification type through the block chain; and receiving verification result information for verifying the information to be verified by the verification server, and sending the verification result information to the target server, wherein the verification server verifies the information to be verified based on the pre-stored block chain data matched with the serial number of the information to be verified. The method and the device can improve the reliability of verifying the information to be verified.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, a system, an apparatus, a server, and a medium for information verification.
Background
The block chain is a distributed shared account book and a database, and has the characteristics of decentralization, no tampering, trace retaining in the whole process, traceability, collective maintenance, openness and transparency and the like. In practice, a blockchain typically has multiple blockchain nodes, the data stored at each blockchain node is the same, and each blockchain node typically has a complete ledger.
In the related art, there is a need to verify electronic data to be verified by using the non-tamperable characteristic of a blockchain.
Disclosure of Invention
The embodiment of the application provides an information verification method, a system, a device, a server and a medium, and aims to solve the problem that the reliability of electronic data to be verified in the related art is not high enough.
In a first aspect, an embodiment of the present application provides an information verification method, where the method includes:
receiving a verification request sent by a target server, wherein the verification request comprises information to be verified, the number of the information to be verified and type indication information for indicating the verification type, which are requested to be verified;
sending the verification request to a block chain so as to send the verification request to a verification server matched with the verification type through the block chain;
and receiving verification result information for verifying the information to be verified by the verification server, and sending the verification result information to the target server, wherein the verification server verifies the information to be verified based on the pre-stored block chain data matched with the serial number of the information to be verified.
Further, the method further comprises:
and in response to receiving the information to be stored sent by the target server, storing the hash value of the associated information to be stored and the number of the information to be stored into the block chain as block chain data as a whole.
Further, the storing the hash value of the associated information to be stored and the number of the information to be stored as blockchain data to the blockchain as a whole comprises:
in response to the information to be stored being the archive file and the file description information of the archive file, recording the hash value of the archive file as a first hash value, recording the hash value of the file description information as a second hash value, and recording the number of the archive file as a file number;
sending the file number to the target server so that the target server stores the archive file and the file description information to the storage server based on the file number;
and in response to receiving the storage confirmation information sent by the storage server, storing the whole of the first hash value, the second hash value and the file number as blockchain data to the blockchain.
Further, the target server stores the archive file and the file description information to the storage server based on the file number, including:
the target server sends the archive file, the file description information and the file number to a storage server;
the storage server records the received hash value of the archive file as a third hash value, records the received hash value of the file description information as a fourth hash value, and extracts a first hash value and a second hash value which are matched with the file number from the storage server; and in response to the first hash value being consistent with the third hash value and the second hash value being consistent with the fourth hash value, associating the storage archive file, the file description information and the file number, and sending storage confirmation information to the certificate storage server.
In a second aspect, an embodiment of the present application provides an information verification system, including: a target server, a deposit server, a blockchain, and a validation server, wherein,
the target server is used for sending a verification request to the evidence storage server, wherein the verification request comprises information to be verified which requires verification, the number of the information to be verified and type indication information used for indicating the verification type;
the certificate storage server is used for receiving a verification request sent by the target server; sending a verification request to the blockchain;
the block chain is used for sending the verification request to a verification server matched with the verification type;
the verification server is used for verifying the information to be verified based on the pre-stored block chain data matched with the serial number of the information to be verified;
the certificate storage server is also used for receiving verification result information of the verification server for verifying the information to be verified and sending the verification result information to the target server.
Further, the authentication types include any one or more of: the type of notarization service authentication, the type of arbitration service authentication and the type of court law enforcement service authentication; the authentication server includes any one or more of: notarization server, arbitration server, court server; the blockchain includes at least two of the following four blockchain nodes: financial nodes, notarization nodes, arbitration nodes and court nodes; and
in the certificate storage server, the verification request is sent to the block chain, and the method comprises the following steps: sending the verification request to the financial node; and
in the block chain, sending the verification request to a verification server matched with the verification type, including: and responding to the verification type being the notarization service verification type, the financial node sends the verification request to the notarization server through the notarization node.
Further, the system includes a storage server, wherein,
the certificate storage server is also used for responding to the received information to be stored sent by the target server, wherein the information to be stored is the archive file and the file description information of the archive file, recording the hash value of the archive file as a first hash value, recording the hash value of the file description information as a second hash value and recording the number of the archive file as a file number; sending a file number to a target server;
the target server is also used for storing the archive file and the file description information to the storage server based on the file number;
and the certificate storage server is also used for responding to the received storage confirmation information sent by the storage server and storing the whole of the first hash value, the second hash value and the file number to the block chain as block chain data.
In a third aspect, an embodiment of the present application provides an information verification apparatus, including:
the system comprises a request receiving unit, a verification unit and a verification unit, wherein the request receiving unit is used for receiving a verification request sent by a target server, and the verification request comprises information to be verified, which requests verification, the number of the information to be verified and type indication information used for indicating the verification type;
a request sending unit, configured to send the verification request to the blockchain, so as to send the verification request to a verification server matched with the verification type through the blockchain;
and the result sending unit is used for receiving verification result information which is obtained by verifying the information to be verified by the verification server and sending the verification result information to the target server, wherein the verification server verifies the information to be verified based on the pre-stored block chain data which is matched with the serial number of the information to be verified.
In a fourth aspect, an embodiment of the present application provides a server, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of any one of the information verification methods when executing the computer program.
In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored, and the computer program, when executed by a processor, implements the steps of any one of the information verification methods described above.
In a sixth aspect, the present application provides a computer program product, which when run on a server, causes the server to execute any one of the above information verification methods.
Compared with the related technology, the embodiment of the application has the beneficial effects that: the block chain has the characteristic of being not falsifiable, and the verification server verifies the information to be verified by adopting the pre-stored block chain data matched with the serial number of the information to be verified, so that the reliability of verifying the information to be verified can be improved. In addition, the verification request is sent to the verification server matched with the verification type, so that the verification server meeting the verification intention can be selected to verify the information to be verified. The verification requests of different verification types are verified by different verification servers, so that the speed of verifying the verification requests can be increased, and the efficiency of verifying the information to be verified is improved.
It is understood that the beneficial effects of the second to sixth aspects can be seen from the description of the first aspect, and are not described herein again.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required to be used in the embodiments or the related technical descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of an information verification method according to an embodiment of the present application;
fig. 2 is a schematic flowchart of storing information to be stored according to an embodiment of the present application;
FIG. 3 is a schematic structural diagram of an information verification system according to an embodiment of the present application;
FIG. 4 is a schematic structural diagram of an information verification system according to another embodiment of the present application;
fig. 5 is a schematic structural diagram of an information verification apparatus according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a server according to an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to" determining "or" in response to detecting ". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.
Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.
In order to explain the technical means of the present application, the following examples are given below.
Example one
With reference to fig. 1, an embodiment of the present application provides an information verification method, including:
The authentication request comprises information to be authenticated which requests authentication, the number of the information to be authenticated and type indication information used for indicating the authentication type. The information to be authenticated is typically information to be authenticated. In practice, the form of the information to be verified may be text, pictures, audio, video, etc. The type indication information is generally information for indicating the type of authentication. In practice, the authentication types may include, but are not limited to: a type of notary service authentication, a type of mediation service authentication, a type of court law enforcement service authentication. In practical applications, if the authentication type is a notarization service authentication type, the purpose of the authentication request is generally to implement notarization service-related authentication. If the authentication type is an arbitration service authentication type, the purpose of the authentication request is usually to implement arbitration service related authentication. If the authentication type is a type of court law enforcement service authentication, the purpose of the authentication request is usually to implement court law enforcement service related authentication.
The target server may be a preset server. In practice, the target server is typically a financial server that provides financial services. Financial services may include, but are not limited to, financing investment services, savings services, credit services, settlement services, securities trading services, business insurance services, financial information consulting services, and the like.
In this embodiment, the execution subject of the information verification method may be a certificate authority. The evidence server is usually a server that directly interacts with the blockchain. For example, the credential server may store data to the blockchain or retrieve data from the blockchain. The target server can perform data interaction with the blockchain through the certificate storage server. In practical applications, the deposit server and the target server are usually two servers belonging to the same financial institution (e.g., a bank), and the deposit server and the target server are usually located in the same local area network. The execution agent may receive an authentication request sent by the target server through a local area network.
And 102, sending the verification request to the block chain so as to send the verification request to a verification server matched with the verification type through the block chain.
The authentication server is generally a server that performs an authentication service. In practice, the authentication server may include, but is not limited to: a notarization server providing notarization service, an arbitration server providing arbitration service, a court server providing court law enforcement service.
In this embodiment, the execution agent may send the authentication request to the block chain via the network. In practice, the execution agent is typically a block chain link point in the block chain that directly interacts with the execution agent to send the authentication request. The block link point may push the authentication request to an authentication server matching the authentication type. Specifically, the blockchain link point may first determine a blockchain node from the blockchain that matches the authentication type. Then, an authentication server is obtained that interacts directly with the determined tile link points. And finally, pushing the verification request to the obtained verification server.
For example, if the block link point interacting directly with the execution entity is a bank node, the authentication server includes: the system comprises a notarization server, an arbitration server and a court server, wherein a block chain comprises the following four block chain nodes: the system comprises bank nodes, notarization nodes, arbitration nodes and court nodes, and the verification type is notarization service verification type. The executing agent typically sends an authentication request to the banking node. The bank node may first determine a notarization node from the blockchain that matches the authentication type. And then, obtaining the notarization server which directly interacts with the notarization node. And finally, pushing the verification request to the obtained notarization server.
The verification server verifies the information to be verified based on the pre-stored block chain data matched with the serial number of the information to be verified. In practice, the blockchain data stored in a blockchain typically has a number. The authentication server may find a number identical to the number of the information to be authenticated from the blockchain by using the number of the information to be authenticated, and obtain blockchain data corresponding to the identical number. And then, comparing the acquired block chain data with the information to be verified, if the acquired block chain data and the information to be verified are consistent, determining that the verification is passed, and otherwise, determining that the verification is not passed.
The verification result information is generally information indicating whether verification is passed. As an example, the verification result information may be "verification passed", may be "verification failed", and may be "pass".
In this embodiment, after the authentication server authenticates the information to be authenticated, the authentication server may return the authentication result information to the execution subject. In practice, the authentication server may directly send the authentication result information to the execution main body through a network. The authentication server may also return authentication result information to the execution subject through the blockchain.
The execution main body may send the verification result information to the target server after receiving the verification result information for the verification request. Therefore, the effective verification of the information to be verified can be realized.
In the method provided by this embodiment, since the blockchain has a characteristic of being not tampered, the verification server verifies the information to be verified by using the prestored blockchain data matched with the number of the information to be verified, which can improve the reliability of verifying the information to be verified. In addition, the verification request is sent to the verification server matched with the verification type, so that the verification server meeting the verification intention can be selected to verify the information to be verified. The verification requests of different verification types are verified by different verification servers, so that the speed of verifying the verification requests can be increased, and the efficiency of verifying the information to be verified is improved.
In some optional implementation manners of this embodiment, the information verification method may further include the following steps: and in response to receiving the information to be stored sent by the target server, storing the hash value of the associated information to be stored and the number of the information to be stored into the block chain as block chain data as a whole.
Wherein the information to be stored is typically information to be stored.
Here, the target server may store the information to be stored in the blockchain through the vouching server.
In this implementation, the credential storage server may receive information to be stored sent by the target server through the network. After receiving the information to be stored, the execution main body may calculate a hash value of the information to be stored, assign a number to the received information to be stored, and store the whole of the hash value and the number as a piece of blockchain data in a blockchain. Specifically, the execution main body may send the data to be stored to the block link point directly interacting with the execution main body for storage, and then, the block chain stores the data to be stored in the block link point directly interacting with the execution main body to other block chain nodes on the block chain through a consensus mechanism.
For example, if the node of the block chain directly interacting with the evidence storing server is a bank node, other nodes on the block chain are notary node, arbitration node and court node. The credentialing server typically sends the data to be stored to the banking node for storage. And then, the blockchain stores the data to be stored in the bank node into the notarization node, the arbitration node and the court node through a consensus mechanism.
The implementation mode can realize the storage of the information to be stored of the target server into the block chain and can realize the reliable storage of the information to be stored. The method and the device are beneficial to realizing that the pre-stored block chain data are taken out from the block chain to verify the data needing to be verified, and the efficiency of verifying the information to be verified is improved.
In some optional implementation manners of this embodiment, storing the hash value of the associated information to be stored and the number of the information to be stored as block chain data to the block chain as a whole may include the following steps one to three.
Step one, responding to the information to be stored as the archive file and the file description information of the archive file, recording the hash value of the archive file as a first hash value, recording the hash value of the file description information as a second hash value, and recording the number of the archive file as a file number.
The archive file can be various original record files with preservation value. As an example, the archive file may be a contract file. The file description information may be information for describing a file. As an example, if the document is a contract, the document description information may include an entering party of the contract, a contract entering time, a main appointment matter of the contract, and the like.
Here, the executing body may calculate the hash value of the archive file after receiving the archive file to be stored and the file description information of the archive file, and obtain the first hash value. Then, the hash value of the file description information is calculated to obtain a second hash value. And then, giving a unique number to the archive file to obtain a file number.
And step two, sending the file number to the target server so that the target server stores the archive file and the file description information to the storage server based on the file number.
Wherein a storage server is typically a server for storing data.
Here, the execution agent may return a file number to the target server. In this way, the target server can store the archive file and the description information of the archive file to the storage server based on the file number. As an example, the target server may send the archive file, the file description information, and the file number to the storage server together, so that the storage server stores the archive file, the file description information, and the file number in association as one piece of association information.
And step three, in response to receiving the storage confirmation information sent by the storage server, storing the whole of the first hash value, the second hash value and the file number as block chain data to the block chain.
The storage confirmation information is generally information for confirming that the storage is completed.
Here, after the archive file, the file description information, and the file number are stored in the storage server, the storage server may transmit storage confirmation information to the certificate storage server. In this way, the execution body may store the whole of the first hash value, the second hash value, and the file number as one blockchain data into the blockchain after receiving the storage confirmation information.
In practice, the target server, the storage server and the certificate server are usually in the same local area network. Here, since the hash value of the file data is often much smaller than the file data itself, the hash value of the archive file and the hash value of the file description information are only stored in the blockchain, which can save a lot of storage resources of the blockchain. In addition, the archive files and the file description information of the archive files are stored in the local storage server, so that the archive files and the file description information of the archive files can be ensured to be always in the local area network, and the safety and privacy of the archive files and the file description information of the archive files are guaranteed.
In some optional implementations of this embodiment, the storing, by the target server, the archive file and the file description information to the storage server based on the file number may include:
first, the target server sends the archive file, the file description information, and the file number to the storage server.
Here, the target server may transmit the archive file, the file description information, and the file number to the storage server.
Then, the storage server records the hash value of the received archive file as a third hash value, records the hash value of the received file description information as a fourth hash value, and extracts the first hash value and the second hash value that match the file number from the certificate storage server. And in response to the first hash value being consistent with the third hash value and the second hash value being consistent with the fourth hash value, associating the storage archive file, the file description information and the file number, and sending storage confirmation information to the certificate storage server.
Here, the storage server may calculate a hash value of the received archive file, resulting in a third hash value. And calculating the hash value of the received file description information to obtain a fourth hash value. Then, the storage server may extract the first hash value and the second hash value corresponding to the file number from the certificate authority server by using the file number. The storage server may then compare the first hash value with the third hash value, and if the first hash value and the third hash value are consistent, the archive file is considered to be unchanged. Otherwise, the archive file is considered tampered. And comparing the second hash value with the fourth hash value, and if the second hash value is consistent with the fourth hash value, determining that the file description information is not changed. Otherwise, the file description information is considered to be tampered. And finally, when the first hash value is consistent with the third hash value and the second hash value is consistent with the fourth hash value, the storage server can regard the archive file and the file description information of the archive file as original record data, perform associated storage of the archive file, the file description information and the file number, and send storage confirmation information to the certificate storage server.
In the implementation mode, accurate archive files and file description information can be stored in the storage server. In practice, storage servers are typically used to backup data in storage target servers. The accurate data is stored in the storage server, so that the target server can be ensured to subsequently extract the accurate data from the storage server to be used as the information to be verified for verification, and the efficiency of verifying the information to be verified is further improved.
Fig. 2 is a schematic flowchart of storing information to be stored according to an embodiment of the present application.
Step 201, the network credit server sends the archive file and the file description information of the archive file to the certificate storage server.
Here, the target server is a web loan server. The network credit server is generally a server that provides network credit services. The information to be stored is archive files and file description information of the archive files.
Step 202, the certificate storing server calculates the hash value of the archive file to obtain a hash1, calculates the hash value of the file description information to obtain a hash2, allocates a file number to the archive file, and sends the file number to the network credit server.
Here, hash1 is a first hash value and hash2 is a second hash value.
Step 203, the network loan server sends the archive file, the file description information and the file number to the storage server.
And step 204, the storage server sends the file number to the certificate storage server.
In step 205, the storage server sends the hash1 and the hash2 corresponding to the file number to the storage server.
In step 206, the storage server calculates the hash value of the archive file received from the network credit server to obtain a hash3, and calculates the hash value of the received file description information to obtain a hash 4. And comparing the hash1 with the hash3, comparing the hash2 with the hash4, and if the hash1 is consistent with the hash3 and the hash2 is consistent with the hash4, the storage server stores the archive file, the file description information and the file number in an associated manner.
Here, hash3 is the third hash value and hash4 is the fourth hash value.
Step 207, the storage server sends the associated hash3, hash4, and file number to the credential server.
Here, the storage server may send the hash3, hash4, and file number to the visa server to store the associated hash3, hash4, and file number into the blockchain through the visa server. In practice, since the certificate storing server calculates the first hash value and the second hash value, the storage server may send storage confirmation information to the certificate storing server when it is determined that the hash1 is consistent with the hash3 and the hash2 is consistent with the hash4, so that the certificate storing server stores the first hash value, the second hash value, and the file number into the block chain based on the storage confirmation information.
Example two
With continuing reference to fig. 3, a schematic structural diagram of an information verification system provided in the embodiment of the present application is shown. The information verification system shown in fig. 3 includes a target server 301, a vouching server 302, a blockchain 303, and a verification server 304, wherein,
the target server 301 is configured to send a verification request to the credential storage server, where the verification request includes information to be verified that requires verification, a number of the information to be verified, and type indication information used for indicating a verification type;
the certificate storing server 302 is used for receiving a verification request sent by a target server; sending a verification request to the blockchain;
a blockchain 303, configured to send the authentication request to an authentication server matching the authentication type;
the verification server 304 is configured to verify the information to be verified based on the pre-stored block chain data that matches the serial number of the information to be verified;
the certificate storing server 302 is further configured to receive verification result information obtained by the verification server verifying the information to be verified, and send the verification result information to the target server.
In the system provided by this embodiment, because the blockchain has a characteristic of being not tampered, the verification server verifies the information to be verified by using the prestored blockchain data matched with the number of the information to be verified, which can improve the reliability of verifying the information to be verified. In addition, the verification request is sent to the verification server matched with the verification type, so that the verification server meeting the verification intention can be selected to verify the information to be verified. The verification requests of different verification types are verified by different verification servers, so that the speed of verifying the verification requests can be increased, and the efficiency of verifying the information to be verified is improved.
In some optional implementations of this embodiment, the credential storage server may be further configured to: and in response to receiving the information to be stored sent by the target server, storing the hash value of the associated information to be stored and the number of the information to be stored into the block chain as block chain data as a whole.
In some optional implementations of this embodiment, the system may further include a storage server. At this time, the process of the present invention,
the certificate storage server is also used for responding to the received information to be stored sent by the target server, wherein the information to be stored is the archive file and the file description information of the archive file, recording the hash value of the archive file as a first hash value, recording the hash value of the file description information as a second hash value and recording the number of the archive file as a file number; sending a file number to a target server;
the target server is also used for storing the archive file and the file description information to the storage server based on the file number;
and the certificate storage server is also used for responding to the received storage confirmation information sent by the storage server and storing the whole of the first hash value, the second hash value and the file number to the block chain as block chain data.
In some optional implementations of this embodiment, in the target server, storing the archive file and the file description information to the storage server based on the file number includes:
the target server sends the archive file, the file description information and the file number to a storage server;
the storage server records the received hash value of the archive file as a third hash value, records the received hash value of the file description information as a fourth hash value, and extracts a first hash value and a second hash value which are matched with the file number from the storage server; and in response to the first hash value being consistent with the third hash value and the second hash value being consistent with the fourth hash value, associating the storage archive file, the file description information and the file number, and sending storage confirmation information to the certificate storage server.
It should be noted that, because the contents of information interaction, execution process, and the like between the target server 301, the credential storing server 302, the blockchain 303, and the verification server 304 are based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be specifically referred to a part of the method embodiment, and details thereof are not described here.
In some optional implementations of this embodiment, the authentication type includes any one or more of: a type of notary service authentication, a type of mediation service authentication, a type of court law enforcement service authentication. The authentication server includes any one or more of: notarization server, arbitration server, court server. The blockchain includes at least two of the following four blockchain nodes: financial nodes, notarization nodes, arbitration nodes, and court nodes.
At this time, in the certificate storing server, the verification request is sent to the block chain, including: the authentication request is sent to the financial node.
Here, the financial node may be implemented as one blockchain node, or may be implemented as a plurality of blockchain nodes. For example, there may be multiple financial nodes on the blockchain, such as a bank node interfacing with a bank, an insurance node interfacing with an insurance company, etc. In practice, the credential server typically sends the authentication request to the blockchain by sending the authentication request to a blockchain link point that directly interacts with the credential server.
In the block chain, sending the verification request to a verification server matched with the verification type, including: and responding to the verification type being the notarization service verification type, the financial node sends the verification request to the notarization server through the notarization node.
Here, the blockchain may transmit an authentication request corresponding to the authentication type being the type of the notarization service authentication to the notarization server. In practice, the vouching server typically sends the validation request to a blockchain link point in the blockchain that interacts directly with the execution master. The block link point may push the authentication request to an authentication server matching the authentication type. Specifically, the blockchain link point may first determine a blockchain node from the blockchain that matches the authentication type. Then, an authentication server is obtained that interacts directly with the determined tile link points. And finally, pushing the verification request to the obtained verification server.
In this implementation, the credential storage server may send the validation request to the financial node. The financial node may first determine a notary node from the blockchain that matches the authentication type. And then, obtaining the notarization server which directly interacts with the notarization node. And finally, pushing the verification request to the obtained notarization server.
The realization mode can realize that the verification request is sent to the verification server matched with the verification type, can realize that the verification server conforming to the verification intention is selected to verify the information to be verified, is favorable for realizing targeted verification of the information to be verified, and improves the verification efficiency.
It should be noted that, the financial node corresponding to the financial institution, the notarization node corresponding to the notarization institution, the arbitration node corresponding to the arbitration mechanism, and the court node corresponding to the court belong to the same block chain, so that the notarization institution, the arbitration mechanism, and the court commonly witness the financial institution to store the evidence data on the block chain can be realized, the accuracy of verifying the information to be verified can be ensured, and the verification efficiency can be further improved.
EXAMPLE III
Fig. 4 is a schematic structural diagram of an information verification system according to an embodiment of the present application. In fig. 4, the information verification system may include: target server, deposit certificate server, block chain, verification server, wherein, target server can be: the bank has a business server, and the deposit certificate server can be: and a bank deposit certificate server. The blockchain may include four blockchain nodes, respectively: bank nodes, notarization nodes, arbitration nodes and court nodes. The authentication server may include a notary server, a mediation server, and a court server. The bank has a service server, a bank deposit certificate server and a bank node in the bank intranet. The target server, the certificate storage server, the block chain and the verification server can realize the information verification function through the following interaction steps.
First, the bankcard server may send the service data to be stored to the bankcard server through the local area network. Here, the banking certification server may calculate a hash value of the business data and assign a data number to the business data.
The banking attestation server may then store the hash value and the data number of the business data into the blockchain. Here, the bank deposit certificate server stores the hash value and the data number of the service data in association with a bank node on the block chain, which directly interacts with the bank deposit certificate server. And the block chain stores the hash value and the data number of the service data stored in the bank node into the notarization node, the arbitration node and the court node through a consensus mechanism.
And then, the existing business server of the bank can send a judicial service request to the blockchain through the bank certificate storage server. Here, the judicial service request is an authentication request. The judicial authentication request usually includes information to be authenticated, the number of the information to be authenticated, and type indication information for indicating the authentication type. The bank credentialing server can send the judicial service request to the bank node. The banking node may push the judicial service request to an authentication server matching the authentication type. Specifically, if the verification type is a notarization service verification type, the bank node may push the judicial service request to a notarization server. If the authentication type is the arbitration service authentication type, the bank node may push the judicial service request to the arbitration server. If the verification type is the court law enforcement service verification type, the bank node can push the judicial service request to a court server.
Finally, the authentication server performs an authentication operation based on the received judicial service request. For example, if the notarization server receives the judicial service request, the notarization server performs data query from the notarization node on the blockchain to perform the verification operation. If the arbitration server receives the judicial service request, the arbitration server performs data query from the arbitration node on the blockchain to execute verification operation. And if the court server receives the judicial service request, the court server performs data query from the court nodes on the block chain to execute verification operation.
When the verification server performs the verification operation, since the blockchain data stored in the blockchain usually has a number, the verification server may use the number of the information to be verified, find the number identical to the number of the information to be verified from the blockchain, and obtain the blockchain data corresponding to the identical number. And then, comparing the acquired block chain data with the information to be verified, if the acquired block chain data and the information to be verified are consistent, determining that the verification is passed, and otherwise, determining that the verification is not passed.
After the verification server verifies the information to be verified, the verification server can return the verification result information to the bank deposit certificate server. In practice, the verification server can directly send the verification result information to the bank deposit certificate server through the network. The verification server can also return the verification result information to the bank deposit certificate server through the block chain.
Example four
Fig. 5 shows a block diagram of an information verification apparatus 500 according to an embodiment of the present application, which corresponds to the information verification method according to the first embodiment.
Referring to fig. 5, the apparatus includes:
a request receiving unit 501, configured to receive an authentication request sent by a target server, where the authentication request includes information to be authenticated that requires authentication, a number of the information to be authenticated, and type indication information used for indicating an authentication type;
a request sending unit 502, configured to send the authentication request to the blockchain, so as to send the authentication request to an authentication server matching the authentication type through the blockchain;
a result sending unit 503, configured to receive verification result information for verifying the information to be verified by the verification server, and send the verification result information to the target server, where the verification server verifies the information to be verified based on the pre-stored block chain data that matches the number of the information to be verified.
In some embodiments, the apparatus may further comprise:
and the information storage unit is used for responding to the received information to be stored sent by the target server, and storing the hash value of the associated information to be stored and the number of the information to be stored into the block chain as block chain data in a whole manner.
In some embodiments, storing the associated hash value of the information to be stored and the number of the information to be stored as blockchain data to the blockchain as a whole comprises:
in response to the information to be stored being the archive file and the file description information of the archive file, recording the hash value of the archive file as a first hash value, recording the hash value of the file description information as a second hash value, and recording the number of the archive file as a file number;
sending the file number to the target server so that the target server stores the archive file and the file description information to the storage server based on the file number;
and in response to receiving the storage confirmation information sent by the storage server, storing the whole of the first hash value, the second hash value and the file number as blockchain data to the blockchain.
In some embodiments, the target server stores the archive file and the file description information to the storage server based on the file number, including:
the target server sends the archive file, the file description information and the file number to a storage server;
the storage server records the received hash value of the archive file as a third hash value, records the received hash value of the file description information as a fourth hash value, and extracts a first hash value and a second hash value which are matched with the file number from the storage server; and in response to the first hash value being consistent with the third hash value and the second hash value being consistent with the fourth hash value, associating the storage archive file, the file description information and the file number, and sending storage confirmation information to the certificate storage server.
According to the device provided by the embodiment, because the blockchain has the characteristic of being not tampered, the verification server adopts the prestored blockchain data matched with the serial number of the information to be verified to verify the information to be verified, and the reliability of verifying the information to be verified can be improved. In addition, the verification request is sent to the verification server matched with the verification type, so that the verification server meeting the verification intention can be selected to verify the information to be verified. The verification requests of different verification types are verified by different verification servers, so that the speed of verifying the verification requests can be increased, and the efficiency of verifying the information to be verified is improved.
It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, which may be referred to in the embodiment of the method specifically, and are not described herein again.
EXAMPLE five
Fig. 6 is a schematic structural diagram of a server 600 according to an embodiment of the present application. As shown in fig. 6, the server 600 of this embodiment includes: at least one processor 601 (only one processor is shown in fig. 6), a memory 602, and a computer program 603, such as a data processing program, stored in the memory 602 and executable on the at least one processor 601. The steps in any of the various method embodiments described above are implemented when the computer program 603 is executed by the processor 601. The steps in the embodiments of the respective information verification methods described above are implemented when the processor 601 executes the computer program 603. The processor 601, when executing the computer program 603, implements the functionality of each module/unit in the various device embodiments described above, e.g., the functionality of units 501-503 shown in fig. 5.
Illustratively, the computer program 603 may be partitioned into one or more modules/units, which are stored in the memory 602 and executed by the processor 601 to accomplish the present application. One or more modules/units may be a series of computer program instruction segments capable of performing certain functions, which are used to describe the execution of computer program 603 in server 600. For example, the computer program 603 may be divided into a request receiving unit, a request sending unit, and a result sending unit, and specific functions of each unit are described in the foregoing embodiments, and are not described herein again.
The server 600 may be a server, a desktop computer, a tablet computer, a cloud server, a mobile terminal, and other computing devices. The server 600 may include, but is not limited to, a processor 601, a memory 602. Those skilled in the art will appreciate that fig. 6 is merely an example of a server 600 and is not intended to be limiting of server 600, and may include more or fewer components than those shown, or some components in combination, or different components, e.g., the server may also include input-output devices, network access devices, buses, etc.
The Processor 601 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The storage 602 may be an internal storage unit of the server 600, such as a hard disk or a memory of the server 600. The memory 602 may also be an external storage device of the server 600, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like provided on the server 600. Further, the memory 602 may also include both internal storage units of the server 600 and external storage devices. The memory 602 is used to store computer programs and other programs and data required by the server. The memory 602 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules, so as to perform all or part of the functions described above. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/server and method may be implemented in other ways. For example, the above-described apparatus/server embodiments are merely illustrative, and for example, a division of modules or units is merely a logical division, and an actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated module, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method according to the embodiments described above may be implemented by a computer program, which is stored in a computer readable storage medium and used by a processor to implement the steps of the embodiments of the methods described above. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying computer program code, recording medium, U.S. disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution media, and the like. It should be noted that the computer readable medium may contain other components which may be suitably increased or decreased as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, in accordance with legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunications signals.
The above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. An information verification method, the method comprising:
receiving a verification request sent by a target server, wherein the verification request comprises information to be verified which requires verification, the number of the information to be verified and type indication information used for indicating the verification type;
sending the verification request to a blockchain so as to send the verification request to a verification server matched with the verification type through the blockchain;
receiving verification result information of the verification server for verifying the information to be verified, and sending the verification result information to the target server, wherein the verification server verifies the information to be verified based on pre-stored block chain data matched with the number of the information to be verified.
2. The method of claim 1, further comprising:
and in response to receiving the information to be stored sent by the target server, storing the hash value of the associated information to be stored and the number of the information to be stored into the block chain as block chain data.
3. The method according to claim 2, wherein storing the associated hash value of the information to be stored and the number of the information to be stored to the blockchain as blockchain data in its entirety comprises:
in response to the information to be stored being the archive file and the file description information of the archive file, recording the hash value of the archive file as a first hash value, recording the hash value of the file description information as a second hash value, and recording the number of the archive file as a file number;
sending the file number to the target server so that the target server stores the archive file and the file description information to a storage server based on the file number;
and in response to receiving storage confirmation information sent by the storage server, storing the whole of the first hash value, the second hash value and the file number to the blockchain as blockchain data.
4. The method of claim 3, wherein the target server stores the archive file and the file description information to a storage server based on the file number, comprising:
the target server sends the archive file, the file description information and the file number to the storage server;
the storage server records the hash value of the received archive file as a third hash value, records the hash value of the received file description information as a fourth hash value, and extracts the first hash value and the second hash value which are matched with the file number from the storage server; and in response to the first hash value being consistent with the third hash value and the second hash value being consistent with the fourth hash value, storing the archive file, the file description information and the file number in an associated manner, and sending storage confirmation information to the certificate storage server.
5. An information verification system, the system comprising: a target server, a deposit server, a blockchain, and a validation server, wherein,
the target server is used for sending a verification request to the evidence storing server, wherein the verification request comprises information to be verified which requires verification, the number of the information to be verified and type indicating information used for indicating the verification type;
the certificate storage server is used for receiving a verification request sent by a target server; sending the verification request to a blockchain;
the block chain is used for sending the verification request to a verification server matched with the verification type;
the verification server is used for verifying the information to be verified based on the prestored block chain data matched with the number of the information to be verified;
the certificate storage server is further used for receiving verification result information of the verification server for verifying the information to be verified, and sending the verification result information to the target server.
6. The system of claim 5, wherein the authentication type comprises any one or more of: the type of notarization service authentication, the type of arbitration service authentication and the type of court law enforcement service authentication; the authentication server comprises any one or more of: notarization server, arbitration server, court server; the blockchain includes at least two of the following four blockchain nodes: financial nodes, notarization nodes, arbitration nodes and court nodes; and
in the certificate storage server, the sending the verification request to the block chain includes: sending the authentication request to the financial node; and
in the block chain, the sending the verification request to a verification server matched with the verification type includes: and responding to the verification type being a notarization service verification type, and the financial node sends the verification request to the notarization server through the notarization node.
7. The system of claim 5, further comprising a storage server, wherein,
the certificate storage server is further used for responding to the fact that the information to be stored sent by the target server is received, the information to be stored is the archive file and the file description information of the archive file, the hash value of the archive file is recorded as a first hash value, the hash value of the file description information is recorded as a second hash value, and the serial number of the archive file is recorded as a file serial number; sending the file number to the target server;
the target server is further used for storing the archive file and the file description information to the storage server based on the file number;
the certificate storage server is further configured to store the whole of the first hash value, the second hash value and the file number to the blockchain as blockchain data in response to receiving storage confirmation information sent by the storage server.
8. An information authentication apparatus, characterized in that the apparatus comprises:
the system comprises a request receiving unit, a verification unit and a verification unit, wherein the request receiving unit is used for receiving a verification request sent by a target server, and the verification request comprises to-be-verified information requesting verification, the number of the to-be-verified information and type indicating information used for indicating a verification type;
a request sending unit, configured to send the verification request to a blockchain, so as to send the verification request to a verification server matching the verification type through the blockchain;
and the result sending unit is used for receiving verification result information of the verification server for verifying the information to be verified and sending the verification result information to the target server, wherein the verification server verifies the information to be verified based on the pre-stored block chain data matched with the number of the information to be verified.
9. A server comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 4 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011503611.XA CN112507395A (en) | 2020-12-18 | 2020-12-18 | Information verification method, system, device, server and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011503611.XA CN112507395A (en) | 2020-12-18 | 2020-12-18 | Information verification method, system, device, server and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112507395A true CN112507395A (en) | 2021-03-16 |
Family
ID=74922485
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011503611.XA Pending CN112507395A (en) | 2020-12-18 | 2020-12-18 | Information verification method, system, device, server and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112507395A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117134918A (en) * | 2023-07-20 | 2023-11-28 | 威艾特科技(深圳)有限公司 | Distributed data signature verification method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110516458A (en) * | 2019-08-28 | 2019-11-29 | 腾讯科技（深圳）有限公司 | Data processing method, device and computer equipment based on block chain technology |
| CN110602116A (en) * | 2019-09-19 | 2019-12-20 | 腾讯科技（深圳）有限公司 | Block chain based data verification method, device and computer readable storage medium |
| CN110879903A (en) * | 2019-11-20 | 2020-03-13 | 北京海益同展信息科技有限公司 | Evidence storage method, evidence verification method, evidence storage device, evidence verification device, evidence storage equipment and evidence verification medium |
| CN111460394A (en) * | 2020-03-30 | 2020-07-28 | 陈兴芜 | Copyright file verification method and device and computer readable storage medium |
-
2020
- 2020-12-18 CN CN202011503611.XA patent/CN112507395A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110516458A (en) * | 2019-08-28 | 2019-11-29 | 腾讯科技（深圳）有限公司 | Data processing method, device and computer equipment based on block chain technology |
| CN110602116A (en) * | 2019-09-19 | 2019-12-20 | 腾讯科技（深圳）有限公司 | Block chain based data verification method, device and computer readable storage medium |
| CN110879903A (en) * | 2019-11-20 | 2020-03-13 | 北京海益同展信息科技有限公司 | Evidence storage method, evidence verification method, evidence storage device, evidence verification device, evidence storage equipment and evidence verification medium |
| CN111460394A (en) * | 2020-03-30 | 2020-07-28 | 陈兴芜 | Copyright file verification method and device and computer readable storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117134918A (en) * | 2023-07-20 | 2023-11-28 | 威艾特科技(深圳)有限公司 | Distributed data signature verification method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11880228B2 (en) | Systems and methods for verifying data via blockchain | |
| US10958438B2 (en) | Method, apparatus, and electronic device for blockchain-based recordkeeping | |
| CN109791591B (en) | Method and system for identity and credential protection and verification via blockchain | |
| CN109872149B (en) | Method and system for using trustworthiness of digital certificates | |
| US20220084027A1 (en) | Blockchain based account funding and distribution | |
| US20180308094A1 (en) | Time stamping systems and methods | |
| US20190147553A1 (en) | Storing linked lists of mineral rights transactions in directed acyclic graphs of cryptographic hash pointers | |
| CN113034274A (en) | Supply chain financial service system and method based on block chain and terminal equipment | |
| CN110084600B (en) | Processing and verifying method, device, equipment and medium for resolution transaction request | |
| CN110471982B (en) | Data processing method and device based on block chain | |
| CN114884674A (en) | Block chain-based user data transfer method, device and equipment | |
| CN112700250A (en) | Identity authentication method, device and system in financial scene | |
| KR20190108666A (en) | Apparatus and method for automated deposit and withdrawal of funds for cryptocurrency transactions and computer program for the same | |
| CN113330714A (en) | Preventing data loss | |
| KR102124440B1 (en) | The abcd-type apparatus and method of block chain for management of research funds by using randomized mesh blockchain type verifier module and smart tcv type blockchain mediation module | |
| CN110766403A (en) | Data processing device and method based on block chain and storage medium | |
| CN113034275B (en) | Management system and method based on block chain network and terminal equipment | |
| CN112507395A (en) | Information verification method, system, device, server and medium | |
| CN112037055A (en) | Transaction processing method and device, electronic equipment and readable storage medium | |
| US11106811B2 (en) | Object storage for guaranteed content for backup and retention | |
| CN110599176A (en) | Data processing method and device based on block chain, storage medium and node equipment | |
| CN112039893B (en) | Private transaction processing method and device, electronic equipment and readable storage medium | |
| CN109658104B (en) | System and method for confirming asset consistency on chain | |
| CN114697114B (en) | Data processing method, device, electronic equipment and medium | |
| CN109658100B (en) | System and method for determining downlink digital assets |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210316 |