WO2020048054A1

WO2020048054A1 - Data storage method, computer-readable storage medium, server, and apparatus

Info

Publication number: WO2020048054A1
Application number: PCT/CN2018/123786
Authority: WO
Inventors: 宦鹏飞; 张文明; 陈飞
Original assignee: 深圳壹账通智能科技有限公司
Priority date: 2018-09-03
Filing date: 2018-12-26
Publication date: 2020-03-12
Also published as: CN109446208A

Abstract

A blockchain-based data storage method, a computer-readable storage medium, a server (6), and an apparatus. The method comprises: receiving a data operation request and extracting a preset request type field from the data operation request (S101); determining the request type of the data operation request according to the value of the request type field (S102); if the request type of the data operation request is a chain batch write request, extracting a preset total data amount field from the chain batch write request (S105); extracting, according to the value of the total data amount field, the set of data to be stored from the chain batch write request (S106), the set being constituted by difference pieces of data; using a data verification rule to perform data verification on the data set (S107); and if the data set passes the data verification, storing the data set into a preset blockchain system in batch (S110). The method ensures the consistency of the same batch of data in the blockchain system, and improves the data storage efficiency.

Description

Data storage method, computer-readable storage medium, server and device

This application claims the priority of a Chinese patent application filed on September 3, 2018 with the Chinese Patent Office, application number 201811022476.X, and the invention name "a data storage method, computer-readable storage medium, and server", all of which The contents are incorporated herein by reference.

Technical field

The present application belongs to the field of computer technology, and particularly relates to a data storage method, a computer-readable storage medium, a server, and a device.

Background technique

The data writing of the existing blockchain system uses a write request to initiate a write operation, and there is more interaction with the blockchain system, which not only causes greater pressure on the blockchain system, but also does not satisfy Some batch business scenarios. Because some business scenarios need to write a batch of data, but if there is a problem in the middle of a piece of data, the entire batch of data needs to be rolled back. However, existing blockchain writing solutions cannot roll back data that has been successfully written before. Therefore, the consistency of this batch of data in the blockchain system cannot be guaranteed.

technical problem

In view of this, embodiments of the present application provide a data storage method, a computer-readable storage medium, a server, and a device to solve the interaction with the blockchain system when writing data to the blockchain system in the prior art in batches. Many, it has caused greater pressure on the blockchain system, and cannot guarantee the consistency of data in the blockchain system.

Technical solutions

A first aspect of the embodiments of the present application provides a data storage method, which may include:

Receiving a data operation request, and extracting a preset request type field from the data operation request;

Determining a request type of the data operation request according to a value of the request type field;

If the request type of the data operation request is a batch on-chain request, a preset total data field is extracted from the batch on-chain request, and the total data field is used to identify a total number of data to be stored ;

Extracting a data set to be stored from the batch on-chain request according to the value of the total data field, the data set is composed of each piece of data to be stored;

Perform data verification on the data set using a preset data verification rule;

If the data set passes the data verification, the data set is stored in batches into a preset blockchain system.

A second aspect of the embodiments of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by a processor, implement the steps of the foregoing data storage method. .

A third aspect of the embodiments of the present application provides a server including a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, where the processor executes the computer-readable The steps of the above data storage method are implemented when the instruction is read.

A fourth aspect of the embodiments of the present application provides a data storage device, which may include a module for implementing the steps of the foregoing data storage method.

Beneficial effect

In the embodiment of the present application, the entire data set will be stored into the blockchain system in batches only after the entire data set has passed the data verification, thereby ensuring the consistency of this batch of data in the blockchain system, and only You can perform batch data operations through a batch access request without having to initiate a separate access request for each data, which greatly reduces the interaction process with the blockchain system and improves the efficiency of data storage.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flowchart of an embodiment of a data storage method according to an embodiment of the present application;

FIG. 2 is a schematic diagram of a frame structure of a batch connection request;

FIG. 3 is a schematic flowchart of performing data verification on a data set using a target data verification rule;

4 is a schematic diagram of a generation process of each block in a block segment;

5 is a structural diagram of a data storage device according to an embodiment of the present application;

FIG. 6 is a schematic block diagram of a server according to an embodiment of the present application.

Embodiments of the invention

Referring to FIG. 1, an embodiment of a data storage method in an embodiment of the present application may include:

Step S101: Receive a data operation request, and extract a preset request type field from the data operation request.

When a business system needs to perform data operations on a preset blockchain system, it first sends a data operation request to any node server in the blockchain system, and the node server that receives the data operation request is an embodiment of this application. Implementation subject.

Generally, the request type field can be set at the start position of the data operation request, or at the end position of the data operation request or at another position. The request type field occupies a fixed number of bytes, for example , 4 bytes, 8 bytes or other values and so on.

Step S102: Determine a request type of the data operation request according to a value of the request type field.

In a specific implementation of this embodiment, if the value of the request type field is 0x0001, it indicates that the request type of the data operation request is a batch on-chain request, and if the value of the request type field is When 0x0000, it indicates that the request type of the data operation request is a single data on-chain request. Of course, this is just an example. In actual applications, the values of the fields corresponding to various request types can be set according to specific situations.

Step S103: Determine whether the request type of the data operation request is a batch on-chain request.

If the request type of the data operation request is a single data on-chain request, step S104 is performed; if the request type of the data operation request is a batch on-chain request, step S105 and subsequent steps are performed.

Step S104: Store a single piece of data in the single data in-chain request into a preset blockchain system.

The storage of a single piece of data into a blockchain system is a common way in the prior art, which is not repeated in this embodiment.

Step S105: Extract a preset data amount field from the batch on-chain request.

Figure 2 shows a specific frame structure of the batch incoming chain request, where:

MSG_TYPE is a request type field.

SYS_ID is a system identification field, and its value is the business system identifier of the target business system. The target business system is the business system that sends the data operation request. This field can be used to determine the specific one of the batch on-chain requests. This field sent by the service system occupies a fixed number of bytes, for example, 4 bytes, 8 bytes, or other values.

DATA_NUM is the total data field, which is used to identify the total number of data to be stored, that is, how many pieces of data need to be linked into the operation at the same time. This field occupies a fixed number of bytes, for example, 4 bytes, 8 Byte or other values and so on.

DATA_BODY is the data body field, that is, the specific data to perform the inbound operation this time, is composed of multiple data frames (FRAME), each frame is composed of a data body DATA and a data termination flag END.

It should be noted that FIG. 2 shows only one possible frame structure of the batch connection request. In actual applications, other frame structures may be set according to specific situations.

Step S106: Extract the data set to be stored from the batch on-chain request according to the value of the total data field.

The data set is composed of various pieces of data to be stored. Specifically, the data in the data body field is read in order. When the termination flag is read, it indicates that the first data has been read, and the data is added to the data set, and then the data body is continued to be read. For the data in the field, when the termination flag is read, it indicates that the second data has been read, and the data is added to the data set, and so on, and so on, until the Nth data is read ( When N is the termination flag of the total amount of data field, it indicates that the Nth data (that is, the last data) has been read, and the data is added to the data set.

Step S107: Perform data verification on the data set by using a preset data verification rule.

The data verification rule may be set according to an actual situation. Preferably, considering that different business systems may have different data verification rules, a data verification rule library as shown below is set in advance in this solution, and corresponding data verification rules are configured for various business systems:

Business system 1 ----- data verification rule A;

Business System 2 ----- Data Verification Rule B;

Business System 3 ----- Data Verification Rule C;

...

When data verification is performed, a business system identifier of a target business system is first extracted from the data operation request, and then a target verification rule is found in the data verification rule database, and the target verification rule is the same as the The data verification rule corresponding to the business system identification. For example, if the target business system is business system 3, by querying the data verification rule database, it can be determined that the corresponding data verification rule is data verification rule C, and the data is corrected. The verification rule C is determined as the target verification rule.

Finally, the target data verification rule is used to perform data verification on the data set through the process shown in FIG. 3:

Step S1071, an arbitrary piece of candidate data is selected from the data set as the current verification data.

The candidate data is data with a preset check identification bit being a first bit value. In this embodiment, a check identification bit may be set for each piece of data in the data set to identify whether the data is Data verification has been performed. When the check flag of a certain data is the first value, it means that the data has not been checked for data. When the check flag of a certain data is the second value, it means that the data has been checked. Data validation. The specific values of the first digit value and the second digit value can be set according to the actual situation. In this embodiment, it is preferable to set the first digit value to 0 and the second digit value to 1.

In the initial state, the values of the check identification bits of all the data in the data set are the first value.

Step S1072, it is determined whether the current verification data meets the target data verification rule.

If the current verification data does not satisfy the target data verification rule, step S1073 is performed, and if the current verification data meets the target data verification rule, step S1074 and subsequent steps are performed.

Step S1073: Determine that the data set fails the data check.

That is, as long as any data in the data set does not satisfy the target data check rule, it is determined that the data set fails the data check.

Step S1074: Set the verification identification bit of the current verification data to a second value, and increase the preset count value by one count unit.

In this embodiment, the count value may be COUNT, and the count value is used to count the number of data with successful data verification. In the initial state, its value is initialized to 0.

When the verification of a piece of data is completed, it is incremented by one count unit, that is:

COUNT = COUNT + 1

Step S1075: Determine whether the count value is equal to the value of the total data field.

If the count value is smaller than the value of the total data field, return to step S1071 and subsequent steps, and if the count value is equal to the value of the total data field, perform step S1076.

Step S1076: Determine that the data set passes data verification.

That is, it is determined that the data set passes the data check only when all the data in the data set meets the target data check rule.

Step S108: Determine whether the data set passes data verification.

If the data set fails the data check, step S109 is performed, and if the data set passes the data check, step S110 is performed.

Step S109: Send an incoming chain failure message to the target service system.

The incoming chain failure message may carry verification failure data. After receiving the incoming chain failure message, the target business system may re-initiate a new batch incoming chain request after correcting the data.

Step S110: Store the data set into the blockchain system in batches.

Specifically, a block segment corresponding to the data set is first generated, the block segment includes a block equal to the amount of data in the data set, and each block in the block segment is Generated from a piece of data in the data set.

The generation process of each block in the block segment includes: determining whether the block to be generated is the first block in the block segment, and if the block to be generated is in the block segment The first block of, the block newly added to the local block chain is determined as the end of the chain, if the block to be generated is not the first block in the block segment, Then the newly added block in the block segment is determined as a chain tail block, and a feature operation is performed on the block header of the chain tail block to obtain a first feature value. A feature operation is performed on the data corresponding to the block to be generated to obtain a second feature value. A block header of the block to be generated is generated according to the first feature value and the second feature value, and based on the data set and the The data corresponding to the block to be generated generates a block body of the block to be generated, thereby generating the block.

As shown in FIG. 4, the block segment is composed of sequential block connections. Each block records a piece of data in the data set. First, a corresponding storage space is created in the server for the new block. The space occupied by each block is divided into two parts, one is the block header, and the content stored in the block header is fixed (including the block header feature value, block body feature value, version number, difficulty value, time stamp, etc. ), The space it occupies is also fixed. The other part is the block body. The content stored in the block body is the data to be written, and its length is variable. Therefore, first obtain the length of the data to be written, and then add the length of the fixed block header to determine the storage space required for the new block. In the server, open up storage space for the new block. It should be noted that the storage location of the new block does not need to be immediately adjacent to the previous block, but any piece of unused storage space can be opened up. After the space, the pointer of the previous block points to the storage space address of the new block.

Obtain all the information in the block header of the previous block from the blockchain, and obtain the block header feature values of the new block based on all the information in the block header of the previous block, and the area to be stored in the new block The data in the block body is subjected to feature value calculation to obtain the block body feature value (HASH value) of the new block. Furthermore, the block header feature value (that is, the first feature value) of the previous block and the block body of the new block are obtained. The eigenvalue (that is, the second eigenvalue) is stored in the block header of the new block; the data to be written is stored in the block body of the new block, thereby generating a new block so that the new block and the previous block pass the previous block The feature value of the block header is related, so the purpose of connecting the blocks in the blockchain is achieved, so that any information in the block can be tampered with through the previous block stored in the block's block header. The block header characteristic value is detected retrospectively, thereby ensuring the security of the information.

Finally, the block segment is stored in a local blockchain, and the block segment is broadcasted in the blockchain system, so that each node server in the blockchain system will store the block Segments are stored in their respective local blockchains.

Specifically, the first node server sends the block segment to a first-level broadcast node server, the first node server is a node server receiving the data operation request, and the first-level broadcast node server is a The node server connected to the first node server; after receiving the block segment, the first-level broadcast node server sends the block segment to the second-level broadcast node server, and the second-level broadcast node The server is a node server connected to the first-level broadcast node server; after receiving the block segment, the second-level broadcast node server sends the block segment to the third-level broadcast node server. The third-level broadcast node server is a node server connected to the second-level broadcast node server; ...; and so on, after receiving the block segment, the m-th broadcast node server will The block segment is sent to the m + 1 level broadcast node server until each node server in the blockchain system receives the block segment and stores it in their respective local blockchains, Said first stage m + 1 to the broadcast server node server node connected to the m-th stage broadcast server node, m is an integer equal to or greater than 1.

In summary, the embodiments of the present application only store the entire data set into the blockchain system in batches after the entire data set has passed the data verification, thereby ensuring that this batch of data is stored in the blockchain system. Consistency, and batch data can be operated through only one batch request, instead of initiating a separate request for each data, greatly reducing the interaction process with the blockchain system and improving the data storage effectiveness.

Corresponding to a data storage method described in the above embodiment, FIG. 5 shows a structural diagram of an embodiment of a data storage device provided by an embodiment of the present application.

In this embodiment, a data storage device may include:

The request receiving module 501 is configured to receive a data operation request and extract a preset request type field from the data operation request;

A request type determining module 502, configured to determine a request type of the data operation request according to a value of the request type field;

The data total amount field extraction module 503 is configured to extract a preset data total amount field from the batch link input request if the request type of the data operation request is a batch link input request, and the data total field is used for For identifying the total number of pieces of data to be stored;

A data set extraction module 504, configured to extract a data set to be stored from the batch on-chain request according to a value of the data total amount field, where the data set is composed of each piece of data to be stored;

A data verification module 505, configured to perform data verification on the data set using a preset data verification rule;

A batch storage module 506 is configured to batch store the data set into a preset blockchain system if the data set passes data verification.

Further, the data verification module may include:

A service system identifier extraction unit, configured to extract a service system identifier of a target service system from the data operation request, where the target service system is a service system that sends the data operation request;

A target verification rule searching unit, configured to find a target verification rule in a preset data verification rule database, where the target verification rule is a data verification rule corresponding to the business system identifier;

A data verification unit is configured to perform data verification on the data set using the target data verification rule.

Further, the data verification unit may include:

A current verification data selection subunit, configured to arbitrarily select a candidate data from the data set as the current verification data, where the candidate data is data with a preset verification identification bit being a first value;

A first judging subunit, configured to judge whether the current verification data meets the target data verification rule;

A first determining subunit, configured to determine that the data set fails the data verification if the current verification data does not satisfy the target data verification rule;

A first processing subunit, configured to set a verification flag bit of the current verification data to a second value if the current verification data meets the target data verification rule, and set a preset count Increment the value by one count;

A second determination subunit, configured to determine whether the count value is equal to a value of the total data field;

A second determining subunit is configured to determine that the data set passes data verification if the count value is equal to a value of the data total amount field.

Further, the batch storage module may include:

A block segment generating unit is configured to generate a block segment corresponding to the data set, where the block segment includes a block equal to the amount of data in the data set, and each of the block segments Each block is generated according to one piece of data in the data set;

A block segment storage unit, configured to store the block segment in a local blockchain, and broadcast the block segment in the blockchain system, so that each node in the blockchain system The server stores the block segments into their respective local blockchains.

Further, the block segment generating unit may include:

A block judging subunit, configured to determine whether a block to be generated is the first block in the block segment;

A first chain tail determination subunit, configured to determine, if the block to be generated is the first block in the block segment, a block newly added to the local blockchain as a chain tail Block

A second chain tail determining subunit, configured to determine, if the block to be generated is not the first block in the block segment, the block newly added to the block segment as the chain tail region Piece;

A first eigenvalue calculation subunit, configured to perform a feature operation on a block header of the chain tail block to obtain a first eigenvalue;

A second eigenvalue calculation subunit, configured to perform a feature operation on data corresponding to the block to be generated in the data set to obtain a second eigenvalue;

A block generation subunit, configured to generate a block header of the block to be generated according to the first characteristic value and the second characteristic value, and according to data in the data set corresponding to the block to be generated Generate a block body of the block to be generated.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the devices, modules, and units described above can refer to the corresponding processes in the foregoing method embodiments, and are not repeated here.

In the above embodiments, the description of each embodiment has its own emphasis. For a part that is not detailed or recorded in an embodiment, reference may be made to related descriptions of other embodiments.

FIG. 6 shows a schematic block diagram of a server provided by an embodiment of the present application. For ease of description, only a part related to the embodiment of the present application is shown.

In this embodiment, the server 6 may include: a processor 60, a memory 61, and computer-readable instructions 62 stored in the memory 61 and executable on the processor 60, for example, to execute the foregoing data storage. Computer-readable instructions of the method. When the processor 60 executes the computer-readable instructions 62, the steps in the foregoing data storage method embodiments are implemented.

When each functional unit in each embodiment of the present application is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially a part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium. Including computer-readable instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), and a random access memory (RAM, Random Access) Memory), magnetic disks, or optical discs, which can store computer-readable instructions.

Claims

A data storage method, comprising:

Receiving a data operation request, and extracting a preset request type field from the data operation request;

Determining a request type of the data operation request according to a value of the request type field;

If the request type of the data operation request is a batch on-chain request, a preset total data field is extracted from the batch on-chain request, and the total data field is used to identify a total number of data to be stored ;

Extracting a data set to be stored from the batch on-chain request according to the value of the total data field, the data set is composed of each piece of data to be stored;

Perform data verification on the data set using a preset data verification rule;

If the data set passes the data verification, the data set is stored in batches into a preset blockchain system.
The data storage method according to claim 1, wherein the performing data verification on the data set using a preset data verification rule comprises:

Extracting a business system identifier of a target business system from the data operation request, where the target business system is a business system that sends the data operation request;

Searching a preset data verification rule database for a target verification rule, where the target verification rule is a data verification rule corresponding to the business system identifier;

Perform data verification on the data set using the target data verification rule.
The data storage method according to claim 2, wherein the performing data verification on the data set using the target data verification rule comprises:

Arbitrarily select a candidate data from the data set as current verification data, the candidate data is data with a preset verification identification bit being a first bit value;

Determining whether the current verification data meets the target data verification rule;

If the current verification data does not satisfy the target data verification rule, determining that the data set fails the data verification;

If the current verification data meets the target data verification rule, setting a verification identification bit of the current verification data to a second bit value, and increasing a preset count value by one count unit;

Determining whether the count value is equal to the value of the total data field;

If the count value is less than the value of the total data field, return to and execute the step of randomly selecting a candidate data from the data set as the current verification data until the count value is equal to the data Up to the value of the total field;

If the count value is equal to the value of the total data field, it is determined that the data set passes the data check.
The data storage method according to any one of claims 1 to 3, wherein the batch storing the data set into a preset blockchain system comprises:

Generate a block segment corresponding to the data set, the block segment including a block equal to the amount of data in the data set, and each block in the block segment is based on the data Generate a piece of data in the collection;

Storing the block segment into a local blockchain, and broadcasting the block segment in the blockchain system, so that each node server in the blockchain system stores the block segment Into their respective local blockchains.
The data storage method according to claim 4, wherein the generation process of each block in the block segment comprises:

Determining whether the block to be generated is the first block in the block segment;

If the block to be generated is the first block in the block segment, determining a block newly added to the local block chain as a chain tail block;

If the block to be generated is not the first block in the block segment, determining the most recently added block in the block segment as a chain tail block;

Performing a characteristic operation on a block header of the chain tail block to obtain a first characteristic value;

Performing a feature operation on data corresponding to the block to be generated in the data set to obtain a second feature value;

Generate a block header of the block to be generated according to the first characteristic value and the second characteristic value, and generate a block of the block to be generated according to data in the data set corresponding to the block to be generated Block body.
A computer-readable storage medium storing computer-readable instructions, wherein the computer-readable instructions implement the following steps when executed by a processor:

Receiving a data operation request, and extracting a preset request type field from the data operation request;

Determining a request type of the data operation request according to a value of the request type field;

If the request type of the data operation request is a batch on-chain request, a preset total data field is extracted from the batch on-chain request, and the total data field is used to identify a total number of data to be stored ;

Extracting a data set to be stored from the batch on-chain request according to the value of the total data field, the data set is composed of each piece of data to be stored;

Perform data verification on the data set using a preset data verification rule;

If the data set passes the data verification, the data set is stored in batches into a preset blockchain system.
The computer-readable storage medium according to claim 6, wherein the performing data verification on the data set using a preset data verification rule comprises:

Extracting a business system identifier of a target business system from the data operation request, where the target business system is a business system that sends the data operation request;

Searching a preset data verification rule database for a target verification rule, where the target verification rule is a data verification rule corresponding to the business system identifier;

Perform data verification on the data set using the target data verification rule.
The computer-readable storage medium according to claim 7, wherein the performing data verification on the data set using the target data verification rule comprises:

Arbitrarily select a candidate data from the data set as current verification data, the candidate data is data with a preset verification identification bit being a first bit value;

Determining whether the current verification data meets the target data verification rule;

If the current verification data does not satisfy the target data verification rule, determining that the data set fails the data verification;

If the current verification data meets the target data verification rule, setting a verification identification bit of the current verification data to a second bit value, and increasing a preset count value by one count unit;

Determining whether the count value is equal to the value of the total data field;

If the count value is less than the value of the total data field, return to and execute the step of randomly selecting a candidate data from the data set as the current verification data until the count value is equal to the data Up to the value of the total field;

If the count value is equal to the value of the total data field, it is determined that the data set passes the data check.
The computer-readable storage medium according to any one of claims 6 to 8, wherein the batch storing the data set into a preset blockchain system comprises:

Generate a block segment corresponding to the data set, the block segment including a block equal to the amount of data in the data set, and each block in the block segment is based on the data Generate a piece of data in the collection;

Storing the block segment into a local blockchain, and broadcasting the block segment in the blockchain system, so that each node server in the blockchain system stores the block segment Into their respective local blockchains.
The computer-readable storage medium according to claim 9, wherein the generation process of each block in the block segment comprises:

Determining whether the block to be generated is the first block in the block segment;

If the block to be generated is the first block in the block segment, determining a block newly added to the local block chain as a chain tail block;

If the block to be generated is not the first block in the block segment, determining the most recently added block in the block segment as a chain tail block;

Performing a characteristic operation on a block header of the chain tail block to obtain a first characteristic value;

Performing a feature operation on data corresponding to the block to be generated in the data set to obtain a second feature value;

Generate a block header of the block to be generated according to the first characteristic value and the second characteristic value, and generate a block of the block to be generated according to data in the data set corresponding to the block to be generated Block body.
A server includes a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, and is characterized in that, when the processor executes the computer-readable instructions, the following steps are implemented: :

Receiving a data operation request, and extracting a preset request type field from the data operation request;

Determining a request type of the data operation request according to a value of the request type field;

If the request type of the data operation request is a batch on-chain request, a preset total data field is extracted from the batch on-chain request, and the total data field is used to identify a total number of data to be stored ;

Extracting a data set to be stored from the batch on-chain request according to the value of the total data field, the data set is composed of each piece of data to be stored;

Perform data verification on the data set using a preset data verification rule;

If the data set passes the data verification, the data set is stored in batches into a preset blockchain system.
The server according to claim 11, wherein the performing data verification on the data set using a preset data verification rule comprises:

Extracting a business system identifier of a target business system from the data operation request, where the target business system is a business system that sends the data operation request;

Searching a preset data verification rule database for a target verification rule, where the target verification rule is a data verification rule corresponding to the business system identifier;

Perform data verification on the data set using the target data verification rule.
The server according to claim 12, wherein the performing data verification on the data set using the target data verification rule comprises:

Arbitrarily select a candidate data from the data set as current verification data, the candidate data is data with a preset verification identification bit being a first bit value;

Determining whether the current verification data meets the target data verification rule;

If the current verification data does not satisfy the target data verification rule, determining that the data set fails the data verification;

If the current verification data meets the target data verification rule, setting a verification identification bit of the current verification data to a second bit value, and increasing a preset count value by one count unit;

Determining whether the count value is equal to the value of the total data field;

If the count value is less than the value of the total data field, return to and execute the step of randomly selecting a candidate data from the data set as the current verification data until the count value is equal to the data Up to the value of the total field;

If the count value is equal to the value of the total data field, it is determined that the data set passes the data check.
The server according to any one of claims 11 to 13, wherein the batch storing the data sets into a preset blockchain system comprises:

Generate a block segment corresponding to the data set, the block segment including a block equal to the amount of data in the data set, and each block in the block segment is based on the data Generate a piece of data in the collection;

Storing the block segment into a local blockchain, and broadcasting the block segment in the blockchain system, so that each node server in the blockchain system stores the block segment Into their respective local blockchains.
The server according to claim 14, wherein the generation process of each block in the block segment comprises:

Determining whether the block to be generated is the first block in the block segment;

If the block to be generated is the first block in the block segment, determining a block newly added to the local block chain as a chain tail block;

If the block to be generated is not the first block in the block segment, determining the most recently added block in the block segment as a chain tail block;

Performing a characteristic operation on a block header of the chain tail block to obtain a first characteristic value;

Performing a feature operation on data corresponding to the block to be generated in the data set to obtain a second feature value;

Generate a block header of the block to be generated according to the first characteristic value and the second characteristic value, and generate a block of the block to be generated according to data in the data set corresponding to the block to be generated Block body.
A data storage device, comprising:

A request receiving module, configured to receive a data operation request and extract a preset request type field from the data operation request;

A request type determining module, configured to determine a request type of the data operation request according to a value of the request type field;

The data total amount field extracting module is configured to extract a preset data total amount field from the batch link input request if the request type of the data operation request is a batch input link request, and the data total amount field is used for Identifies the total number of data to be stored;

A data set extraction module, configured to extract a data set to be stored from the batch on-chain request according to a value of the data total amount field, where the data set is composed of each piece of data to be stored;

A data verification module, configured to perform data verification on the data set using a preset data verification rule;

A batch storage module is configured to batch store the data set into a preset blockchain system if the data set passes data verification.
The data storage device according to claim 16, wherein the data verification module comprises:

A service system identifier extraction unit, configured to extract a service system identifier of a target service system from the data operation request, where the target service system is a service system that sends the data operation request;

A target verification rule searching unit, configured to find a target verification rule in a preset data verification rule database, where the target verification rule is a data verification rule corresponding to the business system identifier;

A data verification unit is configured to perform data verification on the data set using the target data verification rule.
The data storage device according to claim 17, wherein the data verification unit comprises:

A current verification data selection subunit, configured to arbitrarily select a candidate data from the data set as the current verification data, where the candidate data is data with a preset verification identification bit being a first value;

A first judging subunit, configured to judge whether the current verification data meets the target data verification rule;

A first determining subunit, configured to determine that the data set fails the data verification if the current verification data does not satisfy the target data verification rule;

A first processing subunit, configured to set a verification flag bit of the current verification data to a second value if the current verification data meets the target data verification rule, and set a preset count Increment the value by one count;

A second determination subunit, configured to determine whether the count value is equal to a value of the total data field;

A second determining subunit is configured to determine that the data set passes data verification if the count value is equal to a value of the data total amount field.
The data storage device according to any one of claims 16 to 18, wherein the batch storage module comprises:

A block segment generating unit is configured to generate a block segment corresponding to the data set, where the block segment includes a block equal to the amount of data in the data set, and each of the block segments Each block is generated according to one piece of data in the data set;

A block segment storage unit, configured to store the block segment in a local blockchain, and broadcast the block segment in the blockchain system, so that each node in the blockchain system The server stores the block segments into their respective local blockchains.
The data storage device according to claim 19, wherein the block segment generating unit comprises:

A block judging subunit, configured to determine whether a block to be generated is the first block in the block segment;

A first chain tail determination subunit, configured to determine, if the block to be generated is the first block in the block segment, a block newly added to the local blockchain as a chain tail Block

A second chain tail determining subunit, configured to determine, if the block to be generated is not the first block in the block segment, the block newly added to the block segment as the chain tail region Piece;

A first eigenvalue calculation subunit, configured to perform a feature operation on a block header of the chain tail block to obtain a first eigenvalue;

A second eigenvalue calculation subunit, configured to perform a feature operation on data corresponding to the block to be generated in the data set to obtain a second eigenvalue;

A block generation subunit, configured to generate a block header of the block to be generated according to the first characteristic value and the second characteristic value, and according to data in the data set corresponding to the block to be generated Generate a block body of the block to be generated.