A data deserialization method, device and related equipment

Abstract

The application discloses a data deserialization method, comprising: acquiring smart contract data; parsing the smart contract data to obtain an ABI parameter identifier; determining a target data type according to the ABI parameter identifier; and performing deserialization processing on the smart contract data according to the target data type to obtain a processing result. According to the technical scheme provided by the application, the target data type can be determined through the ABI parameter identifier in the smart contract data, and then the deserialization of the smart contract data is realized based on the target data type. Since the ABI parameter identifier is calculated based on the parameter list in the ABI and is not affected by the change of the method name, the ABI query hit rate is high, and the success rate of data deserialization is effectively improved. The application also discloses a data deserialization device, equipment and computer readable storage medium, which have the above beneficial effects.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and in particular to a data deserialization method, as well as a data deserialization device, apparatus, and computer-readable storage medium. Background Technology

[0002] On the blockchain, reading smart contract data requires the use of the ABI (Application Binary Interface); otherwise, the data cannot be parsed. Therefore, without the ABI, directly reading and parsing blockchain smart contract data becomes difficult.

[0003] In related technologies, a smart contract ABI hash identifier is added to the transaction message. The community maintains a database of ABI hash identifiers and ABIs, uploading commonly used ABIs to this database. Therefore, when parsing blockchain smart contract data, the required ABI can be obtained by querying the ABI hash identifier in this database, and then the data can be deserialized to retrieve the original data. However, since an ABI consists of a method name and a parameter list, and the same parameter list may correspond to different method names, inconsistencies in method names will lead to inconsistencies in ABIs, thus reducing the hit rate of ABI queries.

[0004] Therefore, how to effectively improve the hit rate of query ABI, and thus improve the success rate of data deserialization, is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] The purpose of this application is to provide a data deserialization method that can effectively improve the hit rate of query ABI and further improve the success rate of data deserialization. Another purpose of this application is to provide a data deserialization apparatus, device, and computer-readable storage medium, all of which have the above-mentioned beneficial effects.

[0006] Firstly, this application provides a data deserialization method, including:

[0007] Obtain smart contract data;

[0008] The smart contract data is parsed to obtain the ABI parameter identifier;

[0009] The target data type is determined based on the ABI parameter identifier;

[0010] The smart contract data is deserialized according to the target data type to obtain the processing result.

[0011] Preferably, obtaining smart contract data includes:

[0012] Invoke a smart contract method to send a data request to the blockchain;

[0013] Receive the smart contract data fed back by the blockchain based on the data request.

[0014] Preferably, determining the target data type based on the ABI parameter identifier includes:

[0015] The target data type corresponding to the ABI parameter identifier is obtained by querying the mapping database.

[0016] Preferably, the ABI parameter identifier is specifically the hash value of the ABI parameter.

[0017] Preferably, the hash value of the ABI parameter and the mapping database are generated by enumerating the parameter types and number of parameters in the smart contract data.

[0018] Preferably, the step of deserializing the smart contract data according to the target data type to obtain the processing result includes:

[0019] By combining the data assembly protocol, the smart contract data is deserialized based on the target data type to obtain the processing result.

[0020] Secondly, this application also discloses a data deserialization apparatus, comprising:

[0021] The data acquisition module is used to acquire smart contract data;

[0022] The data parsing module is used to parse the smart contract data and obtain the ABI parameter identifier;

[0023] The type determination module is used to determine the target data type based on the ABI parameter identifier;

[0024] The deserialization module is used to deserialize the smart contract data according to the target data type to obtain the processing result.

[0025] Preferably, the data acquisition module is specifically used to invoke a smart contract method to initiate a data request to the blockchain; and to receive the smart contract data fed back by the blockchain based on the data request.

[0026] Thirdly, this application also discloses a data deserialization device, comprising:

[0027] Memory, used to store computer programs;

[0028] A processor, configured to implement any of the data deserialization methods described above when executing the computer program.

[0029] Fourthly, this application also discloses a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of any of the data deserialization methods described above.

[0030] This application provides a data deserialization method, which includes acquiring smart contract data; parsing the smart contract data to obtain an ABI parameter identifier; determining a target data type based on the ABI parameter identifier; and performing deserialization processing on the smart contract data based on the target data type to obtain a processing result.

[0031] By applying the technical solution provided in this application, an ABI (Automatic Biology Analyzer) containing only a parameter list and excluding the method name is predefined. Then, an ABI parameter identifier is calculated and added to the smart contract data. Therefore, during the deserialization of smart contract data, the target data type can be determined through the ABI parameter identifier, and deserialization can be achieved based on this target data type. Since the ABI parameter identifier is unaffected by changes in the method name, the ABI query hit rate is high, further effectively improving the success rate of data deserialization. Furthermore, this implementation method does not require the blockchain application developer to provide a complete ABI, effectively protecting its design details.

[0032] The data deserialization apparatus, device, and computer-readable storage medium provided in this application all have the aforementioned beneficial effects, which will not be elaborated further here. Attached Figure Description

[0033] To more clearly illustrate the technical solutions in the prior art and the embodiments of this application, the accompanying drawings used in the description of the prior art and the embodiments of this application will be briefly introduced below. Of course, the accompanying drawings described below with respect to the embodiments of this application are only a part of the embodiments in this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort, and such other drawings also fall within the protection scope of this application.

[0034] Figure 1 A flowchart illustrating a data deserialization method provided in this application;

[0035] Figure 2 Example diagram of partial data from a mapping database provided in this application;

[0036] Figure 3 A schematic diagram of a data deserialization device provided in this application;

[0037] Figure 4This is a schematic diagram of the structure of a data deserialization device provided in this application. Detailed Implementation

[0038] The core of this application is to provide a data deserialization method that can effectively improve the hit rate of query ABI and further improve the success rate of data deserialization. Another core aspect of this application is to provide a data deserialization apparatus, device, and computer-readable storage medium, which also have the above-mentioned beneficial effects.

[0039] To provide a clearer and more complete description of the technical solutions in the embodiments of this application, the technical solutions in the embodiments of this application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0040] This application provides a data deserialization method.

[0041] Please refer to Figure 1 , Figure 1 This application provides a flowchart illustrating a data deserialization method, which may include:

[0042] S101: Obtain smart contract data;

[0043] This step aims to obtain smart contract data, which refers to various transaction messages generated through data interaction with the blockchain. Therefore, this smart contract data can be obtained from the blockchain.

[0044] Understandably, for ease of data transmission and storage, transaction messages on the blockchain are generally serialized data. Therefore, when reading smart contract data on the blockchain for related processing, it is necessary to deserialize it first. The smart contract data obtained in this step is the data that needs to be deserialized.

[0045] S102: Parse the smart contract data to obtain the ABI parameter identifier;

[0046] This step aims to parse smart contract data to obtain its ABI parameter identifier. Specifically, when smart contract data is generated on the blockchain, its corresponding ABI parameter identifier can be calculated simultaneously and added to the smart contract data. Therefore, after obtaining the smart contract data, the ABI parameter identifier can be obtained through data parsing technology.

[0047] It should be noted that the ABI parameter identifier refers to the identifier information calculated based on the parameter list in the ABI. In existing technologies, the ABI hash identifier is directly calculated and added to the smart contract data. Then, after parsing the smart contract data to obtain the ABI hash identifier, the corresponding ABI is retrieved by querying the ABI hash identifier, and finally, the data is deserialized to obtain the original data. However, since the ABI consists of a method name and a parameter list, and different parameter lists may correspond to different method names, inconsistencies in method names will lead to inconsistencies in the ABI, thus reducing the hit rate of ABI queries. To solve this problem, an ABI containing only the parameter list and not the method name can be predefined. Then, an identifier can be calculated on this ABI to obtain the ABI parameter identifier, which is then added to the smart contract data. Clearly, this ABI parameter identifier is unrelated to the method name of the ABI, and therefore it is not affected by changes in the method name, thus improving the hit rate of ABI queries.

[0048] S103: Determine the target data type based on the ABI parameter identifier;

[0049] This step aims to determine the target data type based on the ABI parameter identifier, which is then used to implement the deserialization process of the corresponding smart contract data. Specifically, after obtaining the ABI parameter identifier from the smart contract data, the target data type corresponding to that ABI parameter identifier can be queried. For example, a database or data table corresponding to ABI parameter identifiers and data types can be maintained in advance. Thus, the target data type corresponding to the ABI parameter identifier can be obtained by querying the database or data table.

[0050] S104: Deserialize the smart contract data according to the target data type to obtain the processing result.

[0051] This step aims to deserialize smart contract data. After obtaining the target data type, deserializing it directly will yield the corresponding processing result, which is the deserialized smart contract data.

[0052] As can be seen, the data deserialization method provided in this application predefines an ABI that contains only a parameter list and not the method name, then calculates its identifier to obtain the ABI parameter identifier, and adds it to the smart contract data. Therefore, when deserializing smart contract data, the target data type can be determined through the ABI parameter identifier in the smart contract data, and deserialization can be achieved based on this target data type. Since the ABI parameter identifier is not affected by changes in the method name, the ABI query hit rate is high, further effectively improving the success rate of data deserialization. Furthermore, this implementation does not require the blockchain application developer to provide a complete ABI, effectively protecting its design details.

[0053] In one embodiment of this application, obtaining smart contract data as described above may specifically include the following steps:

[0054] Step 1: Invoke the smart contract method to send a data request to the blockchain;

[0055] Step 2: Receive smart contract data from the blockchain in response to the data request.

[0056] As mentioned above, smart contract data refers to various transaction messages generated through data interaction with the blockchain. Therefore, smart contract data can be obtained by interacting with the blockchain. Specifically, a data request can be initiated to the blockchain by calling a smart contract method. This data request is a request for data interaction with the blockchain, and its specific type can be set by technical personnel according to actual needs; this application does not limit this. Furthermore, when the blockchain receives the data request, it can send the corresponding smart contract data back to the requesting party, thereby realizing the acquisition of smart contract data.

[0057] In one embodiment of this application, determining the target data type based on the ABI parameter identifier may specifically include:

[0058] Retrieve the target data type corresponding to the ABI parameter identifier from the mapping database.

[0059] Specifically, a mapping database can be maintained in advance, which stores the mapping relationship between various ABI parameter identifiers and data types. Thus, when determining the target data type based on the ABI parameters, the target data type corresponding to the ABI parameter identifier can be directly queried from the mapping database.

[0060] As mentioned above, in related technologies, smart contract ABI hash identifiers are added to transaction messages, and a database of ABI hash identifiers and ABIs is maintained by the community, uploading commonly used ABIs to this database. However, the cost of community-maintained databases is relatively high, and the time from zero to usability is long. However, in this embodiment, the target data type is queried by maintaining a mapping database that stores the mapping relationships between various ABI parameter identifiers and data types. Since the size of this database is relatively fixed and does not require community maintenance, the maintenance cost of the database is greatly reduced.

[0061] In one embodiment of this application, the aforementioned ABI parameter identifier may specifically be the hash value of the ABI parameter.

[0062] In this application embodiment, a specific type of ABI parameter identifier is provided, that is, the hash value of the ABI parameter can be used as the ABI parameter identifier. Specifically, when the blockchain generates smart contract data, it can perform hash calculation on the ABI that only contains a parameter list and does not contain a method name to obtain the corresponding hash value, and use the hash value as the ABI parameter identifier.

[0063] In one embodiment of this application, the hash value and mapping database of the above-mentioned ABI parameters can be generated by enumerating the parameter types and number of parameters in the smart contract data.

[0064] This application provides a method for generating hash values ​​and a mapping database for ABI parameters. As described above, an ABI containing only a parameter list and excluding the method name can be predefined, and then hashed to obtain the ABI parameter identifier. That is, the ABI parameter identifier is only related to the parameter list and not to the method name. Therefore, the ABI parameter identifier and mapping database can be automatically generated by enumerating the parameter types and number of parameters in smart contract data.

[0065] In one embodiment of this application, the above-mentioned deserialization processing of smart contract data according to the target data type to obtain the processing result may specifically include:

[0066] By combining the data assembly protocol, the smart contract data is deserialized based on the target data type to obtain the processing result.

[0067] In this application embodiment, a method for deserializing smart contract data based on the target data type obtained from the query is provided. Specifically, it can be implemented by combining a data assembly protocol. By combining the data assembly protocol with the target data type, the smart contract data is deserialized to obtain the corresponding processing result.

[0068] Based on the above embodiments, this application provides another data deserialization method.

[0069] 1. Smart Contract Data Generation Stage:

[0070] (1) Define an ABI that only contains a parameter list and does not contain a method name as ABIL;

[0071] (2) When the blockchain generates a transaction message, it calculates the hash value of ABIL to obtain the ABIL hash identifier (i.e., the ABI parameter identifier);

[0072] (3) By pre-enumerating the parameter types and number of parameters of the smart contract, an automated mapping database including ABIL hash identifiers and ABIL (i.e., data types) is generated. For example, please refer to [reference needed]. Figure 2 , Figure 2 This is an example diagram of a portion of the data in a mapping database provided in this application.

[0073] 2. Smart contract data deserialization stage:

[0074] First, here is an example of smart contract code:

[0075]

[0076] Furthermore, the parameter calculation method is as follows:

[0077] The ABI is "baz(uint32,bool)";

[0078] The hash identifier of ABI is the first four bytes of Keccak-256("baz(uint32,bool)"), which is represented as 0xcdcd77c0 in hexadecimal. Keccak-256 is a hash algorithm.

[0079] ABIL is "uint32,bool";

[0080] The hash identifier of ABIL is the first four bytes of Keccak-256("uint32,bool"), which is 0x915548c8 in hexadecimal string.

[0081] Finally, the implementation process of smart contract data deserialization is as follows:

[0082] (1) Initiate a transaction to the blockchain by calling the smart contract method "function baz(uint32 x,booly)".

[0083] (2) The following transaction data was obtained:

[0084] 0xcdcd77c0915548c80000000000000000000000000000000000000000000000 000000045000000000000000000000000000000000000000000000000000000000000001;

[0085] Among them, cdcd77c0 is the hash identifier of ABI, 915548c8 is the hash identifier of ABIL, and the remaining data types are unknown because they cannot be deserialized.

[0086] (3) Find ABIL: Figure 2 For example, searching for 915548c8 in the mapping database yields "uint32,bool", indicating that the remaining data consists of a unit32 and a bool.

[0087] (4) Deserializing data: The original text 69 and true can be deserialized by using the remaining data, the remaining data type (i.e. "uint32,bool") and the public data assembly protocol.

[0088] Therefore, the data deserialization method provided in this application predefines an ABI that contains only a parameter list and not a method name, then calculates its identifier to obtain an ABI parameter identifier, which is added to the smart contract data. Thus, when deserializing smart contract data, the target data type can be determined through the ABI parameter identifier in the smart contract data, and deserialization of the smart contract data can be achieved based on this target data type. Since the ABI parameter identifier is not affected by changes in the method name, the ABI query hit rate is high, further effectively improving the success rate of data deserialization. Furthermore, this implementation does not require the blockchain application developer to provide a complete ABI, effectively protecting its design details.

[0089] This application also provides a data deserialization apparatus; please refer to [reference needed]. Figure 3 , Figure 3 This application provides a schematic diagram of the structure of a data deserialization apparatus, which may include:

[0090] Data acquisition module 1 is used to acquire smart contract data;

[0091] Data parsing module 2 is used to parse smart contract data and obtain ABI parameter identifiers;

[0092] Type determination module 3 is used to determine the target data type based on the ABI parameter identifier;

[0093] Deserialization module 4 is used to deserialize smart contract data according to the target data type and obtain the processing result.

[0094] As can be seen, the data deserialization apparatus provided in this application predefines an ABI that contains only a parameter list and not a method name, then performs an identifier calculation on it to obtain an ABI parameter identifier, which is then added to the smart contract data. Therefore, when deserializing smart contract data, the target data type can be determined through the ABI parameter identifier in the smart contract data, and deserialization of the smart contract data can be achieved based on this target data type. Since the ABI parameter identifier is not affected by changes in the method name, the ABI query hit rate is high, further effectively improving the success rate of data deserialization. Furthermore, this implementation method does not require the blockchain application developer to provide a complete ABI, effectively protecting its design details.

[0095] In a preferred embodiment, the data acquisition module 1 described above can be specifically used to invoke a smart contract method to initiate a data request to the blockchain; and to receive smart contract data fed back by the blockchain based on the data request.

[0096] In a preferred embodiment, the type determination module 3 described above can be specifically used to query the mapping database to obtain the target data type corresponding to the ABI parameter identifier.

[0097] In a preferred embodiment, the ABI parameter identifier can specifically be the hash value of the ABI parameter.

[0098] As a preferred embodiment, the hash value and mapping database of the above-mentioned ABI parameters can be generated by enumerating the parameter types and number of parameters in the smart contract data.

[0099] In a preferred embodiment, the deserialization module 4 described above can be specifically used to combine a data assembly protocol to deserialize smart contract data based on the target data type and obtain the processing result.

[0100] For a description of the device provided in this application, please refer to the above method embodiments; further details will not be provided here.

[0101] This application also provides a data deserialization device; please refer to [reference needed]. Figure 4 , Figure 4 This application provides a schematic diagram of the structure of a data deserialization device, which may include:

[0102] Memory, used to store computer programs;

[0103] A processor, used to execute computer programs, can implement the steps of any of the data deserialization methods described above.

[0104] like Figure 4 The diagram shows the structural composition of a network access control device, which may include a processor 10, a memory 11, a communication interface 12, and a communication bus 13. The processor 10, memory 11, and communication interface 12 all communicate with each other through the communication bus 13.

[0105] In this embodiment, the processor 10 may be a central processing unit (CPU), an application-specific integrated circuit, a digital signal processor, a field-programmable gate array, or other programmable logic devices.

[0106] The processor 10 can call programs stored in the memory 11. Specifically, the processor 10 can execute operations in the embodiments of the network access control method.

[0107] The memory 11 is used to store one or more programs. The programs may include program code, which includes computer operation instructions. In this embodiment, the memory 11 stores at least a program for implementing the following functions:

[0108] Obtain smart contract data;

[0109] Parse the smart contract data to obtain the ABI parameter identifier;

[0110] Determine the target data type based on the ABI parameter identifier;

[0111] The smart contract data is deserialized according to the target data type to obtain the processing result.

[0112] In one possible implementation, the memory 11 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function (such as request interception function or information acquisition function). The data storage area may store data created during use, such as security indicator data and application protection policy data.

[0113] In addition, memory 11 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device or other volatile solid-state storage device.

[0114] Communication interface 12 can be an interface for the communication module, used to connect with other devices or systems.

[0115] Of course, it should be noted that, Figure 4 The structure shown does not constitute a limitation on the network access control device in the embodiments of this application. In practical applications, the network access control device may include more than Figure 4 More or fewer components as shown, or combinations of certain components.

[0116] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the steps of any of the data deserialization methods described above.

[0117] The computer-readable storage medium may include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0118] For a description of the computer-readable storage medium provided in this application, please refer to the above method embodiments; further details will not be repeated here.

[0119] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to the method section.

[0120] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0121] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0122] The technical solutions provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the methods and core ideas of this application. It should be noted that those skilled in the art can make several improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of this application.

Claims

1. A data deserialization method, characterized in that, include: Obtain smart contract data; The smart contract data is data that has undergone serialization processing; The smart contract data is parsed to obtain the ABI parameter identifier; the ABI parameter identifier is specifically the hash value of the ABI parameter; the ABI parameter is specifically an ABI parameter that only contains a parameter list and does not contain a method name; The target data type is determined based on the ABI parameter identifier; The smart contract data is deserialized according to the target data type to obtain the processing result.

2. The data deserialization method according to claim 1, characterized in that, The acquisition of smart contract data includes: Invoke a smart contract method to send a data request to the blockchain; Receive the smart contract data fed back by the blockchain based on the data request.

3. The data deserialization method according to claim 1, characterized in that, The step of determining the target data type based on the ABI parameter identifier includes: The target data type corresponding to the ABI parameter identifier is obtained by querying the mapping database.

4. The data deserialization method according to claim 3, characterized in that, The hash value of the ABI parameter and the mapping database are generated by enumerating the parameter types and number of parameters in the smart contract data.

5. The data deserialization method according to claim 1, characterized in that, The step of deserializing the smart contract data according to the target data type to obtain the processing result includes: By combining the data assembly protocol, the smart contract data is deserialized based on the target data type to obtain the processing result.

6. A data deserialization apparatus, characterized in that, include: The data acquisition module is used to acquire smart contract data; The smart contract data is data that has undergone serialization processing; The data parsing module is used to parse the smart contract data to obtain the ABI parameter identifier; the ABI parameter identifier is specifically the hash value of the ABI parameter; the ABI parameter is specifically an ABI parameter that only contains a parameter list and does not contain a method name. The type determination module is used to determine the target data type based on the ABI parameter identifier; The deserialization module is used to deserialize the smart contract data according to the target data type to obtain the processing result.

7. The data deserialization apparatus according to claim 6, characterized in that, The data acquisition module is specifically used to invoke smart contract methods to initiate data requests to the blockchain; and to receive smart contract data from the blockchain in response to the data requests.

8. A data deserialization device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the steps of the data deserialization method as described in any one of claims 1 to 5.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the data deserialization method as described in any one of claims 1 to 5.

Images