WO2020147563A1

WO2020147563A1 - Method and device for service file storage based on blockchain

Info

Publication number: WO2020147563A1
Application number: PCT/CN2019/129744
Authority: WO
Inventors: 胡多峰
Original assignee: 阿里巴巴集团控股有限公司
Priority date: 2019-01-18
Filing date: 2019-12-30
Publication date: 2020-07-23
Also published as: TW202029690A; CN110032581A

Abstract

Disclosed are a method and device for service file storage based on blockchain. The method comprises the following steps: obtaining at least one service file, each service file corresponding to one service identification (202); compressing at least one service file based on a preset compression algorithm to form a compressed service file (204); performing hash operation on the compressed service file to generate a corresponding hash value (206); and storing the compressed service file and the hash value to an information storage node of a service consortium blockchain, the information storage node corresponding to the blockchain node of the service consortium blockchain (208).

Description

A business file storage method and device based on block chain

Technical field

This application relates to the field of computer technology, and in particular to a blockchain-based business file storage method and device, a blockchain-based business file query method and device, a computing device and a computer-readable storage medium.

Background technique

Blockchain technology is a new type of decentralized protocol that can safely store relevant data. Information cannot be forged and tampered with, and has strong historical traceability. The transaction and information data access authentication on the blockchain is determined by the block All nodes on the chain are completed together, and the innovating consensus algorithm guarantees its consistency; among them, the blockchain includes public chains, private chains and consortium chains. Therefore, many users are currently accustomed to storing important business documents on the blockchain. When needed, multiple users can query and use the business documents from the blockchain. So how to ensure the fast and safe transmission of business documents to the blockchain is Problems to be solved at present.

Summary of the invention

In view of this, the embodiments of the present application provide a blockchain-based business file storage method and device, a blockchain-based business file query method and device, a computing device, and a computer-readable storage medium. Solve the technical defects existing in the prior art.

In the first aspect, an embodiment of this specification discloses a blockchain-based business file storage method, including:

Obtain at least one business document, where each business document corresponds to a business identifier;

Compressing the at least one service file based on a preset compression algorithm to form a compressed service file;

Perform a hash operation on the compressed service file, and generate a hash value corresponding to the compressed service file;

The compressed service file and the hash value are stored in an information storage node of a business alliance chain, where the information storage node corresponds to a blockchain node of the business alliance chain.

Optionally, the business document includes an electronic insurance policy of an insurance institution.

Optionally, after the compressed service file is formed, before the hash operation is performed on the compressed service file, the method further includes:

The compressed service file is encrypted based on the preset encryption key to form an encrypted service file.

Optionally, performing a hash operation on the compressed service file and generating a hash value corresponding to the compressed service file includes:

Perform a hash operation on the encrypted service file, and generate a hash value corresponding to the encrypted service file.

Optionally, storing the compressed service file and the hash value in an information storage node of the service alliance chain includes:

The encrypted business file and the hash value are stored in an information storage node of the business alliance chain.

Optionally, the preset compression algorithm includes Snappy lossless compression algorithm, JDK GZIP compression algorithm, JDK deflate compression algorithm or LZ4 compression algorithm.

Optionally, the preset encryption key includes an encryption key generated according to a preset symmetric encryption key.

In the second aspect, an embodiment of this specification discloses a blockchain-based business document query method, including:

Receiving at least one service file query request, where the query request carries a hash value and at least one service identifier;

Searching and downloading the corresponding compressed service file at any information storage node of the business alliance chain based on the hash value, wherein the information storage node corresponds to the blockchain node of the business alliance chain;

Decompress the compressed service file based on a preset decompression algorithm to form a decompressed service file;

Query the corresponding at least one service file in the decompressed service file based on the at least one service identifier.

Optionally, after finding and downloading the corresponding compressed service file, it also includes:

In the case where the compressed service file is an encrypted service file formed after encryption, the encrypted service file is decrypted by using a preset decryption key to form a decrypted service file.

Optionally, decompressing the compressed service file based on a preset decompression algorithm to form a decompressed service file includes:

Decompress the decrypted service file based on a preset decompression algorithm to form a decompressed service file.

Optionally, the preset decompression algorithm includes a symmetric decompression algorithm determined according to a preset compression algorithm, where the preset compression algorithm includes Snappy lossless compression algorithm, JDK GZIP compression algorithm, JDK deflate compression algorithm, or LZ4 Compression algorithm.

Optionally, the preset decryption key includes a symmetric decryption key determined according to the preset encryption key.

In the third aspect, one or more embodiments of this specification disclose a blockchain-based business file storage device, including:

The obtaining module is configured to obtain at least one business document, where each business document corresponds to a business identifier;

The compression module is configured to compress the at least one service file based on a preset compression algorithm to form a compressed service file;

A hash module configured to perform a hash operation on the compressed service file and generate a hash value corresponding to the compressed service file;

The storage module is configured to store the compressed service file and the hash value in an information storage node of a business alliance chain, where the information storage node corresponds to a blockchain node of the business alliance chain.

Optionally, the device further includes:

The encryption module is configured to encrypt the compressed service file based on a preset encryption key to form an encrypted service file.

Optionally, the hash module is further configured to:

Optionally, the storage module is further configured to:

In the fourth aspect, an embodiment of this specification discloses a blockchain-based business document query device, including:

The receiving module is configured to receive at least one service file query request, wherein the query request carries a hash value and at least one service identifier;

The download module is configured to find and download the corresponding compressed service file at any information storage node of the business alliance chain based on the hash value, wherein the information storage node corresponds to the blockchain node of the business alliance chain ；

The decompression module is configured to decompress the compressed service file based on a preset decompression algorithm to form a decompressed service file;

The query module is configured to query at least one service file corresponding to the decompressed service file based on the at least one service identifier.

Optionally, the device further includes:

The decryption module is configured to use a preset decryption key to decrypt the encrypted service file to form a decrypted service file when the compressed service file is an encrypted service file formed after encryption.

Optionally, the decompression module is further configured to:

In the fifth aspect, an embodiment of this specification discloses a computing device, including a memory, a processor, and computer instructions stored on the memory and running on the processor. The processor executes the instructions as described above. The steps of the blockchain-based business file storage method or the blockchain-based business file query method.

In the sixth aspect, an embodiment of this specification discloses a computer-readable storage medium, which stores computer instructions that, when executed by a processor, implement the above-mentioned blockchain-based business file storage method or the district-based The steps of the blockchain business file query method.

This specification provides a blockchain-based business document storage method and device, a blockchain-based business document query method and device, a computing device and a computer-readable storage medium, wherein the block-based The business file storage method of the chain includes acquiring at least one business file, compressing the at least one business file based on a preset compression algorithm to form a compressed business file; performing a hash operation on the compressed business file, and generating the compressed business The hash value corresponding to the file; storing the compressed service file and the hash value in an information storage node of the business alliance chain. By compressing business documents to solve the problem of on-chain efficiency and storage space of business documents stored on the blockchain, and use the non-tampering and trust mechanism of the blockchain to save business documents to prevent unilateral tampering and ensure the information security of business documents .

BRIEF DESCRIPTION

FIG. 1 is a schematic structural diagram of a computing device provided by one or more embodiments of this specification;

FIG. 2 is a flowchart of a method for storing business files based on blockchain according to one or more embodiments of this specification;

FIG. 3 is a schematic diagram of an electronic insurance policy compressed on the chain in a blockchain-based business file storage method provided by one or more embodiments of this specification;

4 is a flowchart of a method for querying business documents based on blockchain provided by one or more embodiments of this specification;

FIG. 5 is a flowchart of a blockchain-based business document storage method and a blockchain-based business document query method using business documents as electronic insurance policies according to one or more embodiments of this specification;

6 is a schematic diagram of interaction between a blockchain-based business document storage method and a blockchain-based business document query method that uses business documents as electronic insurance policies according to one or more embodiments of this specification;

FIG. 7 is a schematic structural diagram of a business file storage device based on blockchain provided by one or more embodiments of this specification;

Fig. 8 is a schematic structural diagram of a block chain-based business document query device provided by one or more embodiments of this specification.

detailed description

In the following description, many specific details are set forth in order to fully understand this application. However, this application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar promotion without violating the connotation of this application. Therefore, this application is not limited by the specific implementation disclosed below.

The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms "a", "said" and "the" used in one or more embodiments of the present specification and the appended claims are also intended to include the majority forms unless the context clearly indicates other meanings. It should also be understood that the term "and/or" used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

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

First, the terminology involved in one or more embodiments of the present invention will be explained.

Blockchain: The essence is an open source distributed ledger. It is the core technology of Bitcoin and other virtual currencies. It can efficiently record transactions between buyers and sellers and ensure that these records are verifiable and permanently preserved. It has the characteristics of decentralization, disintermediation, information transparency, inability to tamper with, and security; including public chains, private chains and alliance chains.

Consortium chain: multiple pre-selected nodes are designated as bookkeepers within a certain group, and the generation of each block is jointly determined by all pre-selected nodes. Any other company or organization can restrict access through the open API of the blockchain.

Electronic insurance policy: An electronic insurance policy issued by an insurance company with the electronic signature of the insurance company with the help of digital signature software and corporate digital certificates following the PKI system.

Compression algorithm: The algorithm for data compression, which is often called signal coding in the electronics and communication fields, includes two steps: compression and restoration, that is, decompression (or decoding and encoding).

In this specification, a blockchain-based business document storage method and device, a blockchain-based business document query method and device, a computing device and a computer-readable storage medium are provided, which are implemented in the following Detailed explanations are given in the examples one by one.

Fig. 1 is a structural block diagram of a computing device 100 according to an embodiment of the present specification. The components of the computing device 100 include but are not limited to a memory 110 and a processor 120. The processor 120 and the memory 110 are connected through a bus 130, and the database 150 is used to store data.

The computing device 100 also includes an access device 140 that enables the computing device 100 to communicate via one or more networks 160. Examples of these networks include public switched telephone network (PSTN), local area network (LAN), wide area network (WAN), personal area network (PAN), or a combination of communication networks such as the Internet. The access device 140 may include one or more of any type of wired or wireless network interface (for example, a network interface card (NIC)), such as IEEE802.11 wireless local area network (WLAN) wireless interface, global interconnection for microwave access ( Wi-MAX) interface, Ethernet interface, universal serial bus (USB) interface, cellular network interface, Bluetooth interface, near field communication (NFC) interface, etc.

In an embodiment of this specification, the aforementioned components of the computing device 100 and other components not shown in FIG. 1 may also be connected to each other, for example, via a bus. It should be understood that the structural block diagram of the computing device shown in FIG. 1 is only for the purpose of example, and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

The computing device 100 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (for example, tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (for example, smart phones). ), wearable computing devices (for example, smart watches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or PCs. The computing device 100 may also be a mobile or stationary server.

The processor 120 may execute the steps in the method shown in FIG. 2. FIG. 2 shows a schematic flowchart of a method for storing business files based on a blockchain according to an embodiment of the present specification, including step 202 to step 208.

Step 202: Obtain at least one business document, where each business document corresponds to a business identifier.

Wherein, the business document includes, but is not limited to, an electronic insurance policy of an insurance institution; the business identifier is unique identification information corresponding to each business document, such as unique identification information composed of special characters or special symbols.

Step 204: Compress the at least one service file based on a preset compression algorithm to form a compressed service file.

Wherein, the preset compression algorithm includes Snappy lossless compression algorithm, JDK GZIP compression algorithm, JDK deflate compression algorithm or LZ4 compression algorithm.

The Snappy lossless compression algorithm is a compression algorithm with relatively good speed and compression ratio;

The JDK GZIP compression algorithm is a slow algorithm with a high compression ratio, and the compressed data is suitable for long-term use;

The JDK deflate compression algorithm is another algorithm in the JDK. The difference between it and the JDK GZIP compression algorithm is that the compression level of the algorithm can be specified, so that the compression time and the output file size can be balanced;

The compression speed of the LZ4 compression algorithm is the fastest.

In actual use, one of the aforementioned compression algorithms can be used to compress the service file, or other better compression algorithms in the prior art can be used to compress the service file, which is not limited in this specification.

The compressed business file becomes a compressed business file, reducing the total number of bytes of the business file, enabling the compressed business file to be transmitted faster through a slower Internet connection, and reducing the disk space occupied by the business file.

In addition, in order to ensure the security of the information in the business file, the business file can also be encrypted.

In one or more embodiments of this specification, after compressing the at least one service file based on a preset compression algorithm to form a compressed service file, the method further includes:

Wherein, the preset encryption key includes, but is not limited to, an encryption key generated according to a preset symmetric encryption key.

In actual use, the compressed file can be encrypted by using an encryption method in the prior art to form an encrypted service file, which is not limited in this specification.

Step 206: Perform a hash operation on the compressed service file, and generate a hash value corresponding to the compressed service file.

A hash operation is used to convert the compressed service file into a fixed-length character string, that is, a hash value. Through the hash operation of the service compressed file, the subsequent verification of the service file can be realized, which improves the security of the service compressed file.

Step 208: Store the compressed service file and the hash value in an information storage node of a business alliance chain, where the information storage node corresponds to a blockchain node of the business alliance chain.

Store the compressed business file and the hash value to an information storage node of the business alliance chain, that is, upload the compressed business file and the hash value to the nearest blockchain node of the business alliance chain , And then based on the consensus algorithm of the business alliance chain, the compressed business files stored on each blockchain node are consistent with the hash value.

In one or more embodiments of this specification, if the compressed file is encrypted based on a preset encryption key before the hash operation is performed on the compressed file, an encrypted service file is formed.

Then, performing a hash operation on the compressed service file and generating the hash value corresponding to the compressed service file is:

To store the compressed business file and the hash value in an information storage node of the business alliance chain is:

Referring to Fig. 3, taking the electronic insurance policy in which the business document is an insurance institution as an example, the compression and storage of the business document in the alliance chain are described.

When the upper limit of the blockchain node of the alliance chain is 10M, the frequency of block generation can be kept within 2 seconds. After obtaining the electronic insurance policy, compress the electronic insurance policy into a compressed file within 10M, and then the compressed file After performing the hash calculation, upload the compressed file and the corresponding hash value to the consortium chain to ensure that the block frequency of the consortium chain is within 2 seconds. The consortium chain includes insurance companies, regulatory agencies, and Ants wait.

In one or more embodiments of this specification, the blockchain-based business file storage method includes acquiring at least one business file, compressing the at least one business file based on a preset compression algorithm to form a compressed business file; Performing a hash operation on the compressed service file, and generating a hash value corresponding to the compressed service file; storing the compressed service file and the hash value in an information storage node of the business alliance chain. By compressing business documents to solve the problem of on-chain efficiency and storage space of business documents stored on the blockchain, and use the non-tampering and trust mechanism of the blockchain to save business documents to prevent unilateral tampering and ensure the information security of business documents , In addition, it can also encrypt compressed business files to protect the private information of business files.

The processor 120 may execute the steps in the method shown in FIG. 4. FIG. 4 shows a schematic flowchart of a method for querying a business document based on a blockchain according to an embodiment of the present specification, including steps 402 to 408.

Step 402: Receive at least one service file query request, where the query request carries a hash value and at least one service identifier.

Wherein, the business documents include, but are not limited to, electronic insurance policies of insurance institutions.

Each service file query request carries a hash value and a service identifier, where the service identifier is unique identification information corresponding to the service file, such as a unique identifier composed of special characters or a combination of special symbols information.

Step 404: Search and download the corresponding compressed service file at any information storage node of the business alliance chain based on the hash value, where the information storage node corresponds to the blockchain node of the business alliance chain.

The compressed service files stored on each blockchain node of the business alliance chain are the same. Therefore, based on the hash value, any information storage node of the business alliance chain can search for and download the corresponding compressed service file.

Step 406: Decompress the compressed service file based on a preset decompression algorithm to form a decompressed service file.

Wherein, the preset decompression algorithm includes but is not limited to a symmetric decompression algorithm determined according to a preset compression algorithm, where the preset compression algorithm includes Snappy lossless compression algorithm, JDK GZIP compression algorithm, JDK deflate compression algorithm or LZ4 compression algorithm.

For specific explanations of the four compression algorithms, reference may be made to the above-mentioned embodiment, which is not repeated here.

Step 408: Query at least one corresponding service file in the decompressed service file based on the at least one service identifier.

If the compressed service file is an encrypted compressed file, after searching and downloading the corresponding compressed service file, it also includes:

Wherein, the preset decryption key includes a symmetric decryption key determined according to the preset encryption key.

In practical applications, the encryption, decryption, compression and decompression in the blockchain-based business file storage method and the blockchain-based business file query method can all adopt methods in the prior art, and only Encryption, decryption, compression and decompression of business files are sufficient, and this application does not make any limitation on this.

Then, when the compressed service file is an encrypted compressed file, decompressing the compressed service file based on a preset decompression algorithm to form a decompressed service file is:

Finally, query at least one corresponding business file in the decompressed business file based on the at least one business identifier. If there are multiple service IDs, you can query the service file corresponding to each service ID in the decompressed service file.

In one or more embodiments of this specification, the blockchain-based business document query method includes receiving at least one business document query request, wherein the query request carries a hash value and at least one business identifier; The hash value searches for and downloads the corresponding compressed service file at any information storage node of the business alliance chain, where the information storage node corresponds to the blockchain node of the business alliance chain; pairing based on a preset decompression algorithm Decompress the compressed service file to form a decompressed service file; query at least one corresponding service file in the decompressed service file based on the at least one service identifier. Download the compressed and encrypted business file from the blockchain node of any business alliance chain through the hash value, then decrypt the compressed business file with the public key, and then decompress the compressed business file, and then use the unique business identifier to finally obtain the business file , Which greatly guarantees the privacy and security of business documents.

Referring to Figures 5 and 6, taking the business document as an electronic insurance policy of an insurance institution as an example, the blockchain-based business document storage method and the blockchain-based business document query method are described in detail, including Step 502 to step 520.

Step 502: When storing the electronic insurance policy, obtain at least one electronic insurance policy, where each electronic insurance policy corresponds to an insurance policy identifier.

Step 504: Compress the at least one electronic insurance policy based on a preset compression algorithm to form a compressed file.

Step 506: Encrypt the compressed file based on the private key to form an encrypted file.

Step 508: Perform a hash operation on the encrypted file, and generate a hash value corresponding to the encrypted file.

Step 510: Upload the encrypted file and the hash value to the blockchain node closest to the alliance chain.

Step 512: Receive an electronic insurance policy query request, where the query request carries a hash value and a service identifier.

Step 514: When inquiring about the electronic insurance policy, search and download the corresponding encrypted file on any blockchain node of the alliance chain based on the hash value.

Step 516: Decrypt the encrypted file based on the public key to obtain a decrypted compressed file.

Step 518: Decompress the decrypted compressed file based on the preset decompression algorithm to form a decompressed electronic insurance policy.

Step 520: Query the electronic insurance policy based on the service identifier.

In one or more embodiments of this specification, the problem of efficiency and storage of small files on the blockchain is solved by compression, and the success rate of block generation in the alliance chain is improved. The electronic insurance policy is stored using the immutability and trust mechanism of the blockchain. , To prevent unilateral tampering, to ensure the settlement of claims and regulatory audits after the accident, and to use encryption and decryption methods to ensure that the content of the electronic insurance policy can only be viewed by the organization holding the public key, ensuring user privacy.

Referring to Fig. 7, one or more embodiments of this specification disclose a business file storage device based on blockchain, including:

The obtaining module 702 is configured to obtain at least one service file, where each service file corresponds to a service identifier;

The compression module 704 is configured to compress the at least one service file based on a preset compression algorithm to form a compressed service file;

The hash module 706 is configured to perform a hash operation on the compressed service file and generate a hash value corresponding to the compressed service file;

The storage module 708 is configured to store the compressed service file and the hash value in an information storage node of a business alliance chain, where the information storage node corresponds to a blockchain node of the business alliance chain.

Optionally, the device further includes:

Optionally, the hash module 706 is further configured to: perform a hash operation on the encrypted service file, and generate a hash value corresponding to the encrypted service file.

Optionally, the storage module 708 is further configured to:

In one or more embodiments of this specification, the blockchain-based business document storage device solves the problem of the on-chain efficiency and storage space of business documents stored on the blockchain by compressing business documents, and uses the block The non-tampering and trust mechanism of the chain saves business documents, prevents unilateral tampering, and ensures the information security of business documents. In addition, compressed business documents can be encrypted to protect the private information of business documents.

Referring to Figure 8, an embodiment of this specification discloses a blockchain-based business document query device, including:

The receiving module 802 is configured to receive at least one service file query request, where the query request carries a hash value and at least one service identifier;

The download module 804 is configured to search and download the corresponding compressed service file at any information storage node of the business alliance chain based on the hash value, wherein the information storage node corresponds to the blockchain of the business alliance chain node;

The decompression module 806 is configured to decompress the compressed service file based on a preset decompression algorithm to form a decompressed service file;

The query module 808 is configured to query at least one corresponding service file in the decompressed service file based on the at least one service identifier.

Optionally, the device further includes:

Optionally, the decompression module 806 is further configured to:

In one or more embodiments of this specification, the blockchain-based business document query device downloads compressed and encrypted business documents from any blockchain node of the business alliance chain through a hash value, and then decrypts it through a public key After compressing the business file and decompressing the compressed business file, the business file can be finally obtained by using the unique business identifier, which greatly guarantees the privacy and security of the business file.

The foregoing is a schematic scheme of a block chain-based business file storage device and a block chain-based business file query device of this embodiment. It should be noted that the technical solutions of the blockchain-based business document storage device and the blockchain-based business document query device are the same as the above-mentioned blockchain-based business document storage method and blockchain-based business document query method The technical solutions belong to the same concept. For details that are not described in detail in the technical solutions of the blockchain-based business document storage device and the blockchain-based business document query device, please refer to the above-mentioned blockchain-based business document storage method and Description of the technical solution of the business document query method based on the blockchain.

An embodiment of the present specification discloses a computing device, including a memory, a processor, and computer instructions stored on the memory and capable of running on the processor. The processor executes the instructions based on the blockchain as described above. The steps of the business file storage method or the blockchain-based business file query method.

The foregoing is a schematic solution of a computing device of this embodiment. It should be noted that the technical solution of the computing device belongs to the same concept as the above-mentioned blockchain-based business file storage method or blockchain-based business file query method. The technical solution of the computing device does not describe the details in detail. For the content, please refer to the description of the technical solution of the above-mentioned blockchain-based business file storage method or the blockchain-based business file query method.

An embodiment of the present application also provides a computer-readable storage medium that stores computer instructions that, when executed by a processor, implement the blockchain-based business file storage method or the blockchain-based business file as described above The steps of the query method.

The foregoing is a schematic solution of a computer-readable storage medium of this embodiment. It should be noted that the technical solution of the storage medium belongs to the same concept as the above-mentioned blockchain-based business file storage method or blockchain-based business file query method. The technical solution of the storage medium does not describe the details in detail. For the content, please refer to the description of the technical solution of the above-mentioned blockchain-based business file storage method or the blockchain-based business file query method.

The computer instructions include computer program codes, and the computer program codes may be in the form of source code, object code, executable files, or some intermediate forms. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a mobile hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM, Read-Only Memory) , Random Access Memory (RAM, Random Access Memory), electrical carrier signals, telecommunications signals and software distribution media, etc. It should be noted that the content contained in the computer-readable medium can be appropriately added or deleted according to the requirements of the legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to the legislation and patent practice, the computer-readable medium Does not include electrical carrier signals and telecommunication signals.

It should be noted that for the foregoing method embodiments, for simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should know that this application is not limited by the described sequence of actions. Because according to this application, some steps can be performed in other order or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the involved actions and modules are not necessarily all required by this application.

In the above embodiments, the description of each embodiment has its own emphasis. For a part that is not detailed in an embodiment, you can refer to the related descriptions of other embodiments.

The preferred embodiments of the application disclosed above are only used to help explain the application. The optional embodiment does not describe all the details in detail, nor does it limit the invention to only the described specific implementation. Obviously, many modifications and changes can be made according to the content of this manual. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the application, so that those skilled in the art can understand and use the application well. This application is only limited by the claims and their full scope and equivalents.

Claims

A business file storage method based on blockchain, which is characterized in that it includes:

Obtain at least one business document, where each business document corresponds to a business identifier;

Compressing the at least one service file based on a preset compression algorithm to form a compressed service file;

Perform a hash operation on the compressed service file, and generate a hash value corresponding to the compressed service file;

The compressed service file and the hash value are stored in an information storage node of a business alliance chain, where the information storage node corresponds to a blockchain node of the business alliance chain.
The method according to claim 1, wherein the business document comprises an electronic insurance policy of an insurance institution.
The method according to any one of claims 1 or 2, wherein after forming the compressed service file, before performing a hash operation on the compressed service file, the method further comprises:

The compressed service file is encrypted based on the preset encryption key to form an encrypted service file.
The method according to claim 3, wherein performing a hash operation on the compressed service file and generating a hash value corresponding to the compressed service file comprises:

Perform a hash operation on the encrypted service file, and generate a hash value corresponding to the encrypted service file.
The method according to claim 4, wherein storing the compressed service file and the hash value in an information storage node of a service alliance chain comprises:

The encrypted business file and the hash value are stored in an information storage node of the business alliance chain.
The method according to any one of claims 1 or 2, wherein the preset compression algorithm comprises a Snappy lossless compression algorithm, a JDK GZIP compression algorithm, a JDK deflate compression algorithm or an LZ4 compression algorithm.
The method according to claim 3, wherein the preset encryption key comprises an encryption key generated according to a preset symmetric encryption key.
A method for querying business documents based on blockchain, which is characterized in that it includes:

Receiving at least one service file query request, where the query request carries a hash value and at least one service identifier;

Searching and downloading the corresponding compressed service file at any information storage node of the business alliance chain based on the hash value, wherein the information storage node corresponds to the blockchain node of the business alliance chain;

Decompress the compressed service file based on a preset decompression algorithm to form a decompressed service file;

Query the corresponding at least one service file in the decompressed service file based on the at least one service identifier.
8. The method according to claim 8, wherein the business document comprises an electronic insurance policy of an insurance institution.
The method according to any one of claims 8 or 9, characterized in that, after searching and downloading the corresponding compressed service file, the method further comprises:

In the case where the compressed service file is an encrypted service file formed after encryption, the encrypted service file is decrypted by using a preset decryption key to form a decrypted service file.
The method according to claim 10, wherein the decompressing the compressed service file based on a preset decompression algorithm to form the decompressed service file comprises:

Decompress the decrypted service file based on a preset decompression algorithm to form a decompressed service file.
The method according to claim 11, wherein the preset decompression algorithm comprises a symmetric decompression algorithm determined according to the preset compression algorithm, wherein the preset compression algorithm comprises Snappy lossless compression algorithm, JDK GZIP Compression algorithm, JDK deflate compression algorithm or LZ4 compression algorithm.
The method according to claim 10, wherein the preset decryption key comprises a symmetric decryption key determined according to the preset encryption key.
A business file storage device based on blockchain, which is characterized by comprising:

The obtaining module is configured to obtain at least one business document, where each business document corresponds to a business identifier;

The compression module is configured to compress the at least one service file based on a preset compression algorithm to form a compressed service file;

A hash module configured to perform a hash operation on the compressed service file and generate a hash value corresponding to the compressed service file;

The storage module is configured to store the compressed service file and the hash value in an information storage node of a business alliance chain, where the information storage node corresponds to a blockchain node of the business alliance chain.
The device according to claim 14, wherein the business document comprises an electronic insurance policy of an insurance institution.
The device according to any one of claims 14 or 15, wherein the device further comprises:

The encryption module is configured to encrypt the compressed service file based on a preset encryption key to form an encrypted service file.
The device according to claim 16, wherein the hash module is further configured to:

Perform a hash operation on the encrypted service file, and generate a hash value corresponding to the encrypted service file.
The device according to claim 17, wherein the storage module is further configured to:

The encrypted business file and the hash value are stored in an information storage node of the business alliance chain.
The device according to any one of claims 14 or 15, wherein the preset compression algorithm comprises Snappy lossless compression algorithm, JDK GZIP compression algorithm, JDK deflate compression algorithm or LZ4 compression algorithm.
The device according to claim 16, wherein the preset encryption key comprises an encryption key generated according to a preset symmetric encryption key.
A business document query device based on blockchain, which is characterized in that it comprises:

The receiving module is configured to receive at least one service file query request, wherein the query request carries a hash value and at least one service identifier;

The download module is configured to find and download the corresponding compressed service file at any information storage node of the business alliance chain based on the hash value, wherein the information storage node corresponds to the blockchain node of the business alliance chain ；

The decompression module is configured to decompress the compressed service file based on a preset decompression algorithm to form a decompressed service file;

The query module is configured to query at least one service file corresponding to the decompressed service file based on the at least one service identifier.
The device according to claim 21, wherein the business document comprises an electronic insurance policy of an insurance institution.
The device according to any one of claims 21 or 22, wherein the device further comprises:

The decryption module is configured to use a preset decryption key to decrypt the encrypted service file to form a decrypted service file when the compressed service file is an encrypted service file formed after encryption.
The device according to claim 23, wherein the decompression module is further configured to:

Decompress the decrypted service file based on a preset decompression algorithm to form a decompressed service file.
The device according to claim 24, wherein the preset decompression algorithm comprises a symmetric decompression algorithm determined according to the preset compression algorithm, wherein the preset compression algorithm comprises Snappy lossless compression algorithm, JDK GZIP Compression algorithm, JDK deflate compression algorithm or LZ4 compression algorithm.
The device according to claim 23, wherein the preset decryption key comprises a symmetric decryption key determined according to the preset encryption key.
A computing device, comprising a memory, a processor, and computer instructions stored on the memory and running on the processor, wherein the processor implements any one of claims 1-13 when executing the instructions Method steps.
A computer-readable storage medium storing computer instructions, characterized in that, when the instructions are executed by a processor, the steps of the method according to any one of claims 1-13 are implemented.