A data access method, device and computer equipment based on blockchain

Abstract

The present application belongs to blockchain technology, and relates to a data access method, device and computer equipment based on blockchain, the method comprising obtaining a data access permission query request; judging whether the accessed collector is a legitimate collector based on the preset collector blockchain table, according to the accessed collector number and the accessed collector signature; if it is a legitimate collector, judging whether the QR code generating user is a preset administrator based on the user name of the QR code generating user and the user signature of the QR code generating user; if it is a preset administrator, searching the preset QR code permission blockchain table for the QR code permission chain block number corresponding to the QR code permission chain block number; judging whether the accessing user is an accessible legitimate user based on the QR code permission information and the preset user information blockchain table; if it is an accessible legitimate user, returning the access permission information to the accessed collector. The present application improves the security and convenience of data access.

Description

Technical Field

[0001] The present application relates to the field of blockchain technology and more particularly to a method, device and computer equipment for accessing data based on blockchain. Background Art

[0002] In the power environment monitoring system, when accessing query data, whether the collector can trust the visitor has always been an unresolved problem. The current solution is to obtain access rights through CA certification. However, the problem with CA certification is that a third-party trust agency is required to independently determine whether it can be trusted. Data storage is centralized and data is easily tampered with. In addition, the current data query steps are cumbersome and need to be accessed through the computer login interface. It can be seen that the existing data access methods have the problems of low security and low convenience. Summary of the invention

[0003] The purpose of the embodiments of the present application is to propose a data access method, device and computer equipment based on blockchain to solve the problems of low security and low convenience of existing data access methods.

[0004] In order to solve the above technical problems, the embodiment of the present application provides a data access method based on blockchain, which adopts the following technical solutions:

[0005] Obtain a data access permission query request, wherein the data access permission query request is issued by the visited collector when the visitor verifies that the visited collector is a legitimate collector based on the QR code information obtained by the visiting user scanning the target QR code; the data access query request includes the visited collector number, the visited collector signature and the QR code information; the QR code information includes the QR code permission chain block number, the collector number, the user name of the user who generated the QR code and the user signature of the user who generated the QR code;

[0006] Based on the preset collector blockchain table, according to the accessed collector number and the accessed collector signature, determine whether the accessed collector is a legitimate collector;

[0007] If the accessed collector is a legitimate collector, judging whether the user who generated the QR code is a preset administrator according to the user name of the user who generated the QR code and the user signature of the user who generated the QR code;

[0008] If the QR code generating user is a preset administrator, the QR code permission information corresponding to the QR code permission chain block number is searched in the preset QR code permission blockchain table according to the QR code permission chain block number;

[0009] According to the QR code permission information and the preset user information blockchain table, determine whether the accessing user is a legitimate user who can access;

[0010] If the accessing user is a legitimate user with access rights, then the access permission information is returned to the accessed collector;

[0011] The preset collector blockchain table, the preset user information blockchain table and the preset QR code authority blockchain table are all stored in a preset alliance blockchain.

[0012] In order to solve the above technical problems, the embodiment of the present application also provides a data access device based on blockchain, including:

[0013] The first acquisition module is used to obtain a data access permission query request; the data access permission query request is issued by the visited collector when the visitor verifies that the visited collector is a legitimate collector based on the QR code information obtained by the visiting user scanning the target QR code; the data access query request includes the visited collector number, the visited collector signature and the QR code information; the QR code information includes the QR code permission chain block number, the collector number, the user name of the QR code generating user and the user signature of the QR code generating user;

[0014] A first judgment module is used to judge whether the visited collector is a legitimate collector based on a preset collector blockchain table, according to the visited collector number and the visited collector signature;

[0015] A second judgment module is used to judge whether the QR code generating user is a preset administrator according to the user name of the QR code generating user and the user signature of the QR code generating user if the accessed collector is a legitimate collector;

[0016] A search module, configured to search for the QR code permission information corresponding to the QR code permission chain block number in the preset QR code permission blockchain table according to the QR code permission chain block number if the QR code generating user is a preset administrator;

[0017] A third judgment module is used to judge whether the accessing user is a legitimate user who can access the QR code according to the QR code permission information and the preset user information blockchain table;

[0018] A first return module, used for returning access permission information to the visited collector if the visiting user is a legitimate user with access rights;

[0019] The preset collector blockchain table, the preset user information blockchain table and the preset QR code authority blockchain table are all stored in a preset alliance blockchain.

[0020] In order to solve the above technical problems, an embodiment of the present application also provides a computer device, wherein the memory stores computer-readable instructions, and the processor implements the steps of a blockchain-based data access method when executing the computer-readable instructions.

[0021] In order to solve the above technical problems, an embodiment of the present application also provides a computer-readable storage medium, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor, the steps of the blockchain-based data access method in the above embodiment are implemented.

[0022] Compared with the prior art, the embodiments of the present application mainly have the following beneficial effects: obtaining a data access permission query request, wherein the data access permission query request is issued by the visited collector, based on the QR code information obtained by the visiting user scanning the target QR code, when the visitor verifies that the visited collector is a legitimate collector; the data access query request includes the visited collector number, the visited collector signature and the QR code information; the QR code information includes the QR code permission chain block number, the collector number, the user name of the QR code generating user and the user signature of the QR code generating user; based on the preset collector blockchain table, judging whether the visited collector is a legitimate collector according to the visited collector number and the visited collector signature; if the visited collector is If it is a legal collector, then according to the user name of the QR code generating user and the user signature of the QR code generating user, determine whether the QR code generating user is the preset administrator; if the QR code generating user is the preset administrator, then according to the QR code permission chain block number, search for the QR code permission information corresponding to the QR code permission chain block number in the preset QR code permission blockchain table; according to the QR code permission information and the preset user information blockchain table, determine whether the accessing user is an accessible legal user; if the accessing user is an accessible legal user, return the access permission information to the accessed collector; the preset collector blockchain table, the preset user information blockchain table and the preset QR code permission blockchain table are all stored in the preset alliance blockchain.

[0023] In this way, user information, collector information and QR code permission information can be stored and judged based on the blockchain, making the user information, collector information and QR code permission information tamper-proof, and realizing data decentralization, thereby improving the security of data access. At the same time, QR codes are used to access and view data, thereby improving the convenience of data access. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the scheme in the present application, a brief introduction is given below to the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0025] Figure 1 is an exemplary system architecture diagram to which the present application may be applied;

[0026] Figure 2 A flowchart of an embodiment of a blockchain-based data access method according to the present application;

[0027] Figure 3 This is a schematic diagram of the structure of a preset collector blockchain table provided by this application;

[0028] Figure 4 This is a schematic diagram of the structure of a preset QR code permission blockchain table provided by this application;

[0029] Figure 5 This is a schematic diagram of the structure of a preset user information blockchain table provided by this application;

[0030] Figure 6 yes Figure 2 A flowchart of an embodiment before step S201;

[0031] Figure 7 yes Figure 2 A flowchart of an embodiment before step 204;

[0032] Figure 8 yes Figure 3 A flowchart of an embodiment after step 303;

[0033] Fig. 9 yes Figure 3 A flowchart of an embodiment after step 306;

[0034] Fig.10 It is a structural diagram of an embodiment of a blockchain-based data access device according to the present application;

[0035] Fig.11 yes Fig.10 A structural diagram of an embodiment before the first acquisition module;

[0036] Fig.12 yes Fig.10 A schematic diagram of the structure of an embodiment before the search module;

[0037] Fig.13 yes Fig.11A schematic diagram of the structure of an embodiment after the first generation module;

[0038] Fig.14 yes Fig.11 A schematic diagram of the structure of an embodiment after the chain list generation module;

[0039] Fig.15 It is a structural diagram of an embodiment of a computer device according to the present application. DETAILED DESCRIPTION

[0040] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by technicians in the technical field of the present application; the terms used in the specification of the application herein are only for the purpose of describing specific embodiments and are not intended to limit the present application; the terms "including" and "having" and any variations thereof in the specification and claims of the present application and the above-mentioned drawings are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of the present application or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.

[0041] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0042] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.

[0043] like Figure 1 As shown, the system architecture 100 may include a preset alliance blockchain 101, a management server 102, a QR code 103, a terminal device 104, and a collector 105. The management server 102, the terminal device 104, and the collector 105 may communicate with the preset alliance blockchain 101 through a network. The terminal device 104 and the collector 105 may also communicate through a network. The management server 102 is capable of generating a QR code 103. The terminal device 104 may obtain QR code information by scanning the QR code 103, and the QR code information includes: a QR code permission chain block number, a collector number, a user name of a QR code generating user, and a user signature of a QR code generating user. The network may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0044] The administrator can interact with the preset alliance blockchain 101 through the management server 102 and the network to receive or send messages, etc. Ordinary users can interact with the preset alliance blockchain 101 through the terminal device 104 and the network to receive or send messages, etc. The terminal device 104 can be installed with various communication client applications, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0045] The terminal device 104 can be various electronic devices with a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, Moving Picture Experts Group Audio Layer 3), MP4 (Moving Picture Experts Group Audio Layer IV, Moving Picture Experts Group Audio Layer 4) players, laptop computers and desktop computers, etc.

[0046] The preset alliance blockchain 101 includes multiple nodes, specifically, it can be based on 5 or more nodes, so that the nodes on the preset alliance blockchain 101 can implement the Byzantine fault-tolerant consensus mechanism.

[0047] The management server 102 is used to modify the collector information and user information, and is also used to generate the QR code 103 .

[0048] The collector 105 may be a device for collecting various data.

[0049] It should be noted that the blockchain-based data access method provided in the embodiment of the present application is generally executed by the preset alliance blockchain 101, and accordingly, the blockchain-based data access device is generally set in the preset alliance blockchain 101.

[0050] It should be understood that Figure 1 The number of preset alliance blockchains 101, management servers 102, QR codes 103, terminal devices 104, and collectors 105 is only illustrative. According to implementation requirements, there can be any number of preset alliance blockchains 101, management servers 102, QR codes 103, terminal devices 104, and collectors 105.

[0051] Continue to refer Figure 2 , showing a flow chart of an embodiment of a blockchain-based data access method according to the present application. The blockchain-based data access method comprises the following steps:

[0052] Step S201, obtain a data access permission query request, which is issued by the visited collector when the visitor verifies that the visited collector is a legitimate collector based on the QR code information obtained by the visiting user scanning the target QR code; the data access query request includes the visited collector number, the visited collector signature and the QR code information; the QR code information includes the QR code permission chain block number, the collector number, the user name of the QR code generating user and the user signature of the QR code generating user.

[0053] In this embodiment, the blockchain-based data access method is run on an electronic device (e.g. Figure 1 The preset alliance blockchain shown in the figure) can receive the data access permission query request through a wired connection or a wireless connection. It should be noted that the above wireless connection method may include but is not limited to 3G / 4G connection, WiFi connection, Bluetooth connection, WiMAX connection, Zigbee connection, UWB (ultra wideband) connection, and other wireless connection methods currently known or to be developed in the future.

[0054] Among them, the above-mentioned collector is a device for collecting data or providing data. The above-mentioned visited collector is the collector that the accessing user needs to access. The above-mentioned visited collector signature includes the private key of the visited collector, wherein there is a mapping relationship between the private key of the visited collector and the public key of the visited collector. Among them, the public key and private key of each collector are unique. The above-mentioned QR code generating user is the user who generates the QR code. Under normal circumstances, the QR code generating user is a specific management user. The user name of the above-mentioned QR code generating user is the user name of the user who generates the QR code, and the user signature of the above-mentioned QR code generating user also corresponds to the signature of the user who generates the QR code. Of course, the QR code generating user also has his own public key and private key, and the user signature of the QR code generating user includes its corresponding private key.

[0055] Specifically, when a user needs to access the data of a collector, the user can scan the target QR code corresponding to the collector through a scanning device to obtain the corresponding QR code information (QR code permission chain block number, collector number, user name of the user who generated the QR code, and user signature of the user who generated the QR code). The user first verifies whether the collector number is legal. If the collector number is legal, the user sends a data access request to the collector based on the QR code information. If the collector number is illegal, the access is stopped.

[0056] If the collector number is legal, the user uses the QR code information obtained by scanning the code, and attaches his or her own user name and signature to package and generate the user's data access request, and sends the data access request to the collector according to the legal collector number. After receiving the data access request, the collector first verifies whether the user is legal. If the user is legal, it sends a request to query the data access permission to the preset alliance blockchain (attached with the collector's own number and signature).

[0057] Step S202, based on the preset collector blockchain table, according to the accessed collector number and the accessed collector signature, determine whether the accessed collector is a legitimate collector.

[0058] In this embodiment, if Figure 3 As shown, the above-mentioned preset collector blockchain table follows the storage method of the preset alliance blockchain and is stored in the preset alliance blockchain. The preset collector blockchain table includes multiple collector chain blocks, and each collector chain block records a set of collector information. Each collector chain block includes a collector chain block header and collector chain block information. The collector chain block header includes the hash value of the previous collector chain block, the current timestamp, and the hash value of the current collector chain block. This ensures that after the data in front of the preset collector blockchain table is tampered with, all subsequent hash values ​​will change accordingly, and the preset collector blockchain table can be quickly found to be tampered with and an alarm can be issued. The collector chain block information includes the collector number, the collector's public key, and the collector status. The preset collector blockchain table includes all collector information (the collector status can be set: in use and out of use).

[0059] The above-mentioned legal collector refers to a collector that has a record in the preset collector blockchain table and is in normal use. If there is no record in the preset collector blockchain table and the collector is in an abnormal state or stopped state, the collector is an illegal collector.

[0060] Specifically, after receiving the data access permission query request from the accessed collector, the preset alliance blockchain first determines whether the collector sending the request is a legal collector (based on the accessed collector number and the accessed collector signature and the collector number and public key recorded in the preset collector blockchain table). If a collector number that is the same as the accessed collector number in the data access permission query request is found in the preset collector blockchain table, and there is a mapping relationship between the public key and the private key under the same collector number, it can be determined that the accessed collector is a legal collector. If a collector number that is the same as the accessed collector number in the data access permission query request is not found in the preset collector blockchain table, it can be directly determined that the accessed collector is not a legal collector (illegal collector).

[0061] Step S203: If the accessed collector is a legitimate collector, determine whether the user who generated the QR code is a preset administrator based on the user name of the user who generated the QR code and the user signature of the user who generated the QR code.

[0062] In this embodiment, the above-mentioned preset administrator can be the system's built-in main administrator user, who can modify the usage of the collector (set the erroneous collector status to stop using, and the collector is no longer a legal collector), modify the permissions of other users (ordinary users can be set as deputy administrators; the deputy administrator's permissions can also be revoked to turn them back into ordinary users; users can also be set as illegal users to prohibit users from accessing the system again).

[0063] Specifically, if the collector being accessed is a legitimate collector, the user name of the QR code generator obtained by scanning the target QR code can be compared with the user name of the administrator recorded in the preset user information blockchain table. If the two user names are the same, it is determined whether the two signatures are the same. If the two signatures are also the same, it can be determined that the QR code generator is the preset administrator; if the two user names and signatures are different, it is determined that the QR code generator is not the preset administrator (it may be a malicious user). If only one of the user names or signatures is the same, it is also determined that the QR code generator is not the preset administrator (it may be a malicious user).

[0064] Step S204: If the user who generates the QR code is a preset administrator, the QR code permission information corresponding to the QR code permission chain block number is searched in the preset QR code permission blockchain table according to the QR code permission chain block number.

[0065] In this embodiment, if Figure 4 As shown, the above-mentioned preset QR code permission blockchain table follows the storage method of the preset alliance blockchain and is stored in the preset alliance blockchain. The preset QR code permission blockchain table includes multiple QR code permission chain blocks, each of which represents a set of QR code permission information. Each QR code permission chain block includes a QR code permission chain block header and QR code permission chain block information. Each QR code permission chain block includes the hash value of the previous QR code permission chain block, the current timestamp, and the hash value of the current QR code permission chain block. This ensures that after the data in front of the preset QR code permission blockchain table is tampered with, all subsequent hash values ​​will change accordingly, and the preset QR code permission blockchain table can be quickly found to be tampered with and an alarm can be issued. The QR code permission chain block information includes the administrator user name, collector number, QR code permission chain block number, and a list of ordinary users who can access the collector data through the QR code.

[0066] The above QR code permission information is the QR code permission information of the QR code permission chain block recorded under the QR code permission chain block number in the preset QR code permission blockchain table. The QR code permission information includes the preset administrator user name, the preset administrator signature, the legal collector number that can be viewed corresponding to the QR code, and the list of legal user names that can be accessed.

[0067] Specifically, after determining that the QR code generating user is the preset administrator, the QR code permission chain block number is compared with the QR code permission chain block number recorded in the preset QR code permission blockchain table and in reverse order. If the same QR code permission chain block number is found in the preset QR code permission blockchain table, the QR code permission information under the same QR code permission chain block number is obtained.

[0068] Step S205, judging whether the accessing user is a legitimate user who can access the site based on the QR code permission information and the preset user information blockchain table.

[0069] In this embodiment, if Figure 5 As shown, the above-mentioned preset user information blockchain table follows the storage method of the preset alliance blockchain and is stored in the preset alliance blockchain. The preset user information blockchain table includes multiple user information chain blocks, and each user information chain block records the information of a user. The preset user information blockchain table contains information about all users, that is, user permissions (administrator users, ordinary users, illegal users). Each user information chain block includes a user information chain block header and user information chain block information. Each user information chain block includes the hash value of the previous user information chain block, the current timestamp, and the hash value of the user information chain block. This ensures that after the data in front of the preset user information blockchain table is tampered with, all subsequent hash values ​​will change accordingly, and the preset user information blockchain table can be quickly discovered to be tampered with and an alarm can be issued. The user information chain block information includes the user name, the user's public key, and the user's permissions.

[0070] Specifically, the username and signature of the accessing user are compared with the username and signature in the accessible legal username list of the QR code permission information. If a consistent legal username and corresponding signature are found in the accessible legal username list, and the corresponding username and signature can also be found in the preset user information blockchain table, the accessing user is considered to be an accessible legal user. Otherwise, the accessing user is considered to be an inaccessible illegal user.

[0071] Step S206: If the accessing user is a legitimate user with access rights, access permission information is returned to the accessed collector.

[0072] In this embodiment, the access permission information may include confirmation information of access permission, such as yes, agree or allow. If the accessing user is an illegal user who cannot access, access permission information is returned, such as no, disagree or not allow.

[0073] This application obtains a data access permission query request, which is issued by the visited collector based on the QR code information obtained by the visiting user scanning the target QR code, when the visitor verifies that the visited collector is a legal collector; the data access query request includes the visited collector number, the visited collector signature and the QR code information; the QR code information includes the QR code permission chain block number, the collector number, the user name of the QR code generating user and the user signature of the QR code generating user; based on the preset collector blockchain table, according to the visited collector number and the visited collector signature, it is judged whether the visited collector is a legal collector; if the visited collector is a legal collector If a QR code generating user is a preset administrator, then the QR code generating user is judged according to the user name of the QR code generating user and the user signature of the QR code generating user. If the QR code generating user is the preset administrator, then the QR code permission information corresponding to the QR code permission chain block number is searched in the preset QR code permission blockchain table according to the QR code permission chain block number. If the accessing user is an accessible legitimate user, then the access permission information is returned to the accessed collector. The preset collector blockchain table, the preset user information blockchain table and the preset QR code permission blockchain table are all stored in the preset alliance blockchain.

[0074] In this way, user information, collector information and QR code permission information can be stored and judged based on the blockchain, making the user information, collector information and QR code permission information tamper-proof, and realizing data decentralization, thereby improving the security and reliability of data in the power environment monitoring system. At the same time, the use of QR codes to access and view data makes data access convenient.

[0075] In some optional implementations of this embodiment, such as Figure 6 As shown, before obtaining the data access permission query request in step 201, the electronic device may further perform the following steps:

[0076] Step S301, obtaining a first registration request issued by a registration collector and a second registration request issued by a registered user, wherein the first registration request includes a registration collector number, and the second registration request includes a registered user name;

[0077] Step S302: register in the preset alliance blockchain according to the first registration request and the second registration request, generate a collector public key and a collector private key corresponding to the registered collector and return them to the registered collector, and generate a user public key and a user private key corresponding to the registered user and return them to the registered user.

[0078] Step S303, generating a collector blockchain table based on the registered collector number and the collector public key to obtain a preset collector blockchain table, and generating a user information blockchain table based on the registered user name and the user public key to obtain a preset user information blockchain table.

[0079] In this embodiment, the collector public key is used to generate the collector blockchain table, and the collector private key is used to perform collector signature verification. The user public key is used to generate the user information blockchain table, and the user private key is used to perform user signature verification.

[0080] When a collector needs to register, it can use its own number to generate a registration request to register with the preset alliance blockchain. The preset alliance blockchain will generate a unique collector public key and collector private key, and then return the corresponding collector public key and collector private key to the corresponding collector. The preset alliance blockchain generates a collector blockchain table by registering the collector number and the collector public key, and then obtains the preset collector blockchain table.

[0081] When a user needs to register, he can use his own user name to generate a registration request to register with the preset alliance blockchain. The preset alliance blockchain will generate a unique user public key and user private key, and then return the corresponding user public key and user private key to the corresponding user. The preset alliance blockchain generates a user information blockchain table through the registered user name and user public key, and then obtains the preset user information blockchain table.

[0082] In this way, collectors and users can register with the preset alliance blockchain to obtain their own blockchain tables and store them in the blockchain, thereby improving the information security of collectors and users.

[0083] In an embodiment of the present application, when a new collector or user is added, the collector number or user name is sent to the preset alliance blockchain. After verifying that the collector number or user name is not repeated, the preset alliance blockchain returns the public key and private key unique to the collector number or user name, and adds the collector number and collector public key or the user name and user public key to the corresponding linked list. When a new collector is added, the collector status is initialized to being in use. When a new user is added, the user authority is initialized to a normal user.

[0084] This application authenticates the identity information of the collector and the user through the preset collector blockchain table and the preset user information blockchain table obtained through registration, thereby improving the security of data access between the collector and the user.

[0085] In some optional implementations, such as Figure 7 As shown, in step 204, if the user generating the QR code is a preset administrator, before searching the preset QR code permission blockchain table for QR code permission information corresponding to the QR code permission chain block number according to the QR code permission chain block number, the electronic device may perform the following steps:

[0086] Step S401, obtaining the QR code permission information issued by the preset administrator, the QR code permission information includes the preset administrator user name, the preset administrator signature, the viewable legal collector number corresponding to the QR code, and the list of accessible legal user names.

[0087] Step S402: Verify whether the preset administrator is a legitimate administrator based on the preset administrator user name and the preset administrator signature.

[0088] Step S403, if the preset administrator is a legitimate administrator, a QR code permission chain block is generated according to the viewable legitimate collector number and the accessible legitimate user name list corresponding to the QR code in the QR code permission information, and a QR code permission blockchain table is generated according to the QR code permission chain block to obtain a preset QR code permission blockchain table, wherein the QR code permission chain block includes the QR code permission chain block number corresponding to the viewable legitimate collector number corresponding to the QR code.

[0089] In this embodiment, the viewable legal collector number corresponding to the above-mentioned QR code is the number of the collector that can be viewed through the QR code. The above-mentioned accessible legal user name list can be a list corresponding to the user name of the legal user who accesses the accessed collector through the QR code. The accessible legal user name list includes the user names of multiple legal users. For example, the accessible legal user name list includes user name A, user name B and user name C, then it can be said that user name A, user name B and user name C are all accessible legal users. At this time, user name A, user name B and user name C can all access the data in the accessed collector.

[0090] Specifically, when generating a QR code, the administrator can only select a legal collector in the system (i.e., a collector whose device status is in use in the preset collector blockchain table), and can only select legal users in the system (administrator users and ordinary users, illegal users cannot be selected). The administrator presets the alliance blockchain to publish the QR code permission information: the preset administrator user name, the preset administrator signature, the legal collector number that can be viewed corresponding to the QR code, and the list of legal user names that can be accessed. After receiving the administrator's request, after verifying the administrator's identity and signature and determining that the administrator is a legal administrator, the legal collector number that can be viewed in the QR code permission information and the list of legal user names that can be accessed are generated into a QR code permission chain block, and the QR code permission chain block is published to the QR code permission blockchain table to obtain the preset QR code permission blockchain table. In this way, a preset QR code permission blockchain table can be generated to judge the QR code permissions, the permissions of the access collector and the access user, and improve the reliability of the data of the user accessing the collector through the QR code.

[0091] In some optional implementations, after generating a preset QR code permission blockchain table according to the QR code permission information in step 403, the electronic device may perform the following steps:

[0092] The QR code chain block number is returned to the preset administrator, and the target QR code is generated with the viewable legal collector number corresponding to the preset administrator username, preset administrator signature and QR code.

[0093] In this embodiment, after generating the preset QR code permission blockchain table, the number of the generated QR code permission chain block is returned. After receiving the returned QR code permission chain block number, the administrator can use the QR code chain table block number, the legal collector number that can be viewed corresponding to the QR code, his own user name and signature to generate a QR code to obtain the target QR code. In this way, the user can access the collector through the target QR code number. Improve the convenience of users accessing collector data.

[0094] In some optional implementations, such as Figure 8 As shown, after generating a collector blockchain table based on the registered collector number and the collector public key in step 303 to obtain a preset collector blockchain table, the electronic device may perform the following steps:

[0095] Step S501, obtaining an information modification request of a preset administrator, the information modification request including a preset administrator signature, a preset administrator user name, a collector number to be modified corresponding to the collector to be modified, and a target state of the collector.

[0096] Step S502: verifying the administrator identity information of the preset administrator according to the preset administrator signature and the preset administrator user name.

[0097] Step S503: If the administrator identity information verification is successful, the identity information of the collector to be modified is verified according to the collector number to be modified and the preset collector blockchain table.

[0098] Step S504: If the identity information of the collector to be modified is successfully verified, the collector chain block information corresponding to the collector to be modified in the preset collector blockchain table is modified based on the collector target state.

[0099] Step S505: If the identity information verification of the collector to be modified fails, a failure message is returned.

[0100] In this embodiment, the information modification request may include a collector state modification request. The collector whose usage status needs to be modified may be the collector whose target state is modified. For example, the wrong collector state is set to stop using, and the collector is no longer a legal collector.

[0101] Specifically, when the administrator needs to change the collector status, the administrator can send a request to modify the collector status (including the collector number, collector target status, administrator username, and administrator signature) to the preset alliance blockchain. After the preset alliance blockchain verifies the administrator's identity and signature and determines that the administrator is a legitimate administrator (an administrator whose identity information has been successfully verified), and confirms that the collector number already exists in the preset collector blockchain table, a new collector chain block is generated according to the new status set by the administrator, and the collector status is updated. In this way, the legitimate administrator can modify the collector status, that is, after discovering a collector error, set its status to stop using, and the user will no longer access the collector, or change the collector's stop using status to the in-use status, and the user can continue to access the collector. Illegal administrators (administrators whose identity information verification failed) cannot modify the collector status and return a failure message (no). This allows users to access valid collector data, further improving the security of collector data.

[0102] In some optional implementations, such as Fig. 9 As shown, the information modification request also includes the user name of the user to be modified and the target identity status. After verifying the administrator identity information of the preset administrator according to the preset administrator signature and the preset administrator user name in step 502, the electronic device may perform the following steps:

[0103] Step S601: If the administrator identity information verification is successful, the identity information of the user to be modified is verified according to the user name of the user to be modified and the preset user information blockchain table.

[0104] Step S602: If the identity information of the user to be modified is successfully verified, the user information chain block information corresponding to the username of the user to be modified is modified based on the target identity status.

[0105] Step S603: If the identity information of the user to be modified fails to be verified, a failure message is returned.

[0106] In this embodiment, the information modification request may include a user identity status modification request. The user to be modified refers to a user whose identity status needs to be modified.

[0107] Specifically, when the administrator needs to change the identity status of a user, if the administrator can send a request to modify the user identity status to the preset alliance blockchain (user name of the user to be modified, target identity status, administrator username, administrator signature), the preset alliance blockchain verifies whether the administrator is a legitimate administrator after receiving the request. If the administrator is a legitimate administrator, query whether there is a corresponding user in the preset user information blockchain table. If there is a corresponding user, regenerate a new user information chain block and update the user's identity status. For example, the administrator can set an ordinary user as an administrator user so that he can generate a QR code; or set other administrator users as ordinary users to stop their permission to generate QR codes to access the collector; or set the user as an illegal user and no longer allow the user to access the system. In this way, a legitimate administrator (an administrator whose identity information has been successfully verified) can modify the user identity status of a legitimate user (a user whose identity information has been successfully verified). An illegal administrator (an administrator whose identity information has failed to be verified) cannot modify the user identity status of a legitimate user or an illegal user (a user whose identity information has failed to be verified). The collector data can be accessed by legitimate users, further improving the security of the collector data.

[0108] In some optional implementations, after generating a collector blockchain table based on the registered collector number and the collector public key in step 303 to obtain a preset collector blockchain table; and generating a user information blockchain table based on the registered user name and the user public key in step 306 to obtain a preset user information blockchain table, the electronic device may perform the following steps:

[0109] The preset user information blockchain table is synchronized to the local registered collector, the preset collector blockchain table is synchronized to the local registered user, and the preset user information blockchain table and the preset collector blockchain table are synchronized to the local preset administrator.

[0110] In this embodiment, after the preset user information blockchain table and the preset collector blockchain table are generated by registration, all registered collectors can synchronize the preset user information blockchain table so as to verify the request and verify whether the identity information is issued by the registered legal collector when receiving a request from the user. At the same time, all registered users can synchronize the preset collector blockchain table so as to verify the request and verify whether the identity information is issued by the registered legal user when receiving a request from the collector. Of course, the preset administrator also needs to use the preset user information blockchain table and the preset collector blockchain table to verify the requests and identity information of the collector and the user, thereby improving the security of accessing the collector data.

[0111] The preset alliance blockchain referred to in this application is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm, etc. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, platform product service layer, and application service layer.

[0112] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through computer-readable instructions, and the computer-readable instructions can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the aforementioned storage medium can be a non-volatile storage medium such as a disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0113] It should be understood that, although the steps in the flowchart of the accompanying drawings are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.

[0114] Further references Fig.10 , as a response to the above Figure 2The present application provides an embodiment of a data access device based on blockchain, and the data access device embodiment based on blockchain is Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0115] like Fig.10 As shown, the data access device 700 based on blockchain in this embodiment includes: a first acquisition module 701, a first judgment module 702, a second judgment module 703, a search module 704, a third judgment module 705 and a first return module 706. Among them:

[0116] The first acquisition module 701 is used to obtain a data access permission query request; the data access permission query request is issued by the visited collector when the visitor verifies that the visited collector is a legitimate collector based on the QR code information obtained by the visiting user scanning the target QR code; the data access query request includes the visited collector number, the visited collector signature and the QR code information; the QR code information includes the QR code permission chain block number, the collector number, the user name of the QR code generating user and the user signature of the QR code generating user;

[0117] The first judgment module 702 is used to judge whether the accessed collector is a legitimate collector based on the preset collector blockchain table, the accessed collector number and the accessed collector signature;

[0118] The second judgment module 703 is used to judge whether the user who generated the QR code is a preset administrator according to the user name of the user who generated the QR code and the user signature of the user who generated the QR code if the collector being accessed is a legitimate collector;

[0119] A search module 704 is used to search for the QR code permission information corresponding to the QR code permission chain block number in the preset QR code permission blockchain table according to the QR code permission chain block number if the QR code generating user is a preset administrator;

[0120] The third judgment module 705 is used to judge whether the accessing user is a legitimate user who can access the user according to the QR code permission information and the preset user information blockchain table;

[0121] The first return module 706 is used to return access permission information to the accessed collector if the accessing user is a legitimate user with access rights;

[0122] The preset collector blockchain table, the preset user information blockchain table, and the preset QR code permission blockchain table are all stored in the preset alliance blockchain.

[0123] In some optional implementations of this embodiment, such as Fig.11 As shown, before the first acquisition module 701, it also includes:

[0124] The second acquisition module 707 is used to acquire a first registration request issued by the registration collector and a second registration request issued by the registered user, the first registration request includes the registration collector number, and the second registration request includes the registered user name;

[0125] The registration module 708 is used to register in the preset alliance blockchain according to the first registration request and the second registration request, and respectively generate a collector public key and a collector private key corresponding to the registered collector and return them to the registered collector, and a user public key and a user private key corresponding to the registered user and return them to the registered user;

[0126] The first generation module 709 is used to generate a collector blockchain table based on the registered collector number and the collector public key to obtain a preset collector blockchain table, and to generate a user information blockchain table based on the registered user name and the user public key to obtain a preset user information blockchain table.

[0127] In some optional implementations of this embodiment, such as Fig.12 As shown, before the search module 704, it also includes:

[0128] The third acquisition module 710 is used to obtain the QR code permission information issued by the preset administrator, the QR code permission information includes the preset administrator user name, the preset administrator signature, the viewable legal collector number corresponding to the QR code, and the list of accessible legal user names;

[0129] The first verification module 711 is used to verify whether the preset administrator is a legitimate administrator according to the preset administrator user name and the preset administrator signature;

[0130] The second generation module 712 is used to generate a QR code permission chain block according to the viewable legal collector number and the accessible legal user name list corresponding to the QR code in the QR code permission information if the preset administrator is a legal administrator, and generate a QR code permission blockchain table according to the QR code permission chain block to obtain a preset QR code permission blockchain table, wherein the QR code permission chain block includes the QR code permission chain block number corresponding to the viewable legal collector number corresponding to the QR code.

[0131] In some optional implementations of this embodiment, after the second generating module 712, the following steps are further included:

[0132] The second return module is used to return the QR code chain block number to the preset administrator, and generate a target QR code with a viewable legal collector number corresponding to the preset administrator user name, preset administrator signature and QR code.

[0133] In some optional implementations of this embodiment, such as Fig.13As shown, after the first generation module 709, it also includes:

[0134] The fourth acquisition module 713 is used to obtain the information modification request of the preset administrator, which includes the preset administrator signature, the preset administrator user name, the collector number to be modified corresponding to the collector to be modified, and the collector target state;

[0135] The second verification module 714 is used to verify the administrator identity information of the preset administrator according to the preset administrator signature and the preset administrator username;

[0136] The third verification module 715 is used to verify the identity information of the collector to be modified according to the collector number to be modified and the preset collector blockchain table if the administrator identity information verification is successful;

[0137] The first modification module 716 is used to modify the collector chain block information corresponding to the collector to be modified in the preset collector blockchain table based on the collector target state if the identity information of the collector to be modified is successfully verified;

[0138] The first modification-free module 717 is used to return failure information if the identity information verification of the collector to be modified fails.

[0139] In some optional implementations of this embodiment, such as Fig.14 As shown, the information modification request also includes the user name of the user to be modified and the target identity status, and after the second verification module 714, it also includes:

[0140] The fourth verification module 718 is used to verify the identity information of the user to be modified according to the user name of the user to be modified and the preset user information blockchain table if the administrator identity information verification is successful;

[0141] The second modification module 719 is used to modify the user information chain block information corresponding to the user name of the user to be modified based on the target identity status if the identity information of the user to be modified is successfully verified;

[0142] The second modification-free module 720 is configured to return failure information if the identity information of the user to be modified fails to be verified.

[0143] In some optional implementations of this embodiment, after the first generating module 709, the following steps are further included:

[0144] The synchronization module is used to synchronize the preset user information blockchain table to the local registered collector, synchronize the preset collector blockchain table to the local registered user, and synchronize the preset user information blockchain table and the preset collector blockchain table to the local preset administrator.

[0145] The blockchain-based data access device 700 provided in the embodiment of the present application can implement each process implemented by the blockchain-based data access method in the above method embodiment, and can achieve the same beneficial effects. To avoid repetition, it will not be repeated here.

[0146] To solve the above technical problems, the present application also provides a computer device. Fig.15 , Fig.15 This is a basic structural block diagram of the computer device in this embodiment.

[0147] The computer device 8 includes a memory 81, a processor 82, and a network interface 83 that are interconnected through a system bus. It should be noted that the figure only shows a computer device 8 with components 81-83, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable gate arrays (Field-Programmable Gate Array, FPGA), digital processors (Digital Signal Processor, DSP), embedded devices, etc.

[0148] Computer devices can be computing devices such as desktop computers, notebooks, PDAs, and cloud servers. Computer devices can interact with users through keyboards, mice, remote controls, touch pads, or voice control devices.

[0149] The memory 81 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 81 can be an internal storage unit of the computer device 8, such as a hard disk or memory of the computer device 8. In other embodiments, the memory 81 can also be an external storage device of the computer device 8, such as a plug-in hard disk equipped on the computer device 8, a smart memory card (SmartMedia Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. Of course, the memory 81 can also include both the internal storage unit of the computer device 8 and its external storage device. In this embodiment, the memory 81 is generally used to store the operating system and various application software installed on the computer device 8, such as computer-readable instructions based on the data access method of the blockchain. In addition, the memory 81 can also be used to temporarily store various types of data that have been output or are to be output.

[0150] The processor 82 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip in some embodiments. The processor 82 is generally used to control the overall operation of the computer device 8. In this embodiment, the processor 82 is used to run computer-readable instructions stored in the memory 81 or process data, such as computer-readable instructions for running a blockchain-based data access method.

[0151] The network interface 83 may include a wireless network interface or a wired network interface, and the network interface 83 is generally used to establish a communication connection between the computer device 8 and other electronic devices.

[0152] The computer device 800 provided in the embodiment of the present application can implement each process implemented by the data access method based on blockchain in the above method embodiment, and can achieve the same beneficial effects. To avoid repetition, it will not be repeated here.

[0153] The present application also provides another implementation, namely, providing a computer-readable storage medium, which stores computer-readable instructions, and the computer-readable instructions can be executed by at least one processor to enable the at least one processor to perform the steps of the blockchain-based data access method as described above.

[0154] In this embodiment, when the computer program is executed by the processor, each process of the blockchain-based data access method provided in the embodiment of the present application is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0155] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the various embodiment methods of the present application.

[0156] Obviously, the embodiments described above are only some embodiments of the present application, rather than all embodiments. The preferred embodiments of the present application are given in the accompanying drawings, but they do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present application more thorough and comprehensive. Although the present application is described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions recorded in the aforementioned specific implementation methods, or to perform equivalent replacement of some of the technical features therein. Any equivalent structure made using the contents of the specification and drawings of this application, directly or indirectly used in other related technical fields, is similarly within the scope of patent protection of this application.

Claims

1. A data access method based on blockchain, characterized in that: The steps include: Obtaining a data access permission query request includes: an accessing user scans a QR code of a collector to obtain QR code information; the QR code information includes a QR code permission chain block number, a collector number, a user name of a user generating the QR code, and a user signature of a user generating the QR code; when the accessing user verifies that the accessed collector is a legitimate collector based on the QR code information and when the accessed collector verifies that the user is legitimate, a data access permission query request is sent to a preset alliance blockchain; the data access permission query request includes the accessed collector number, the accessed collector signature, and the QR code information; Based on the preset collector blockchain table, according to the accessed collector number and the accessed collector signature, determine whether the accessed collector is a legitimate collector; If the accessed collector is a legitimate collector, judging whether the user who generated the QR code is a preset administrator according to the user name of the user who generated the QR code and the user signature of the user who generated the QR code; If the QR code generating user is a preset administrator, the QR code permission information corresponding to the QR code permission chain block number is searched in the preset QR code permission blockchain table according to the QR code permission chain block number; According to the QR code permission information and the preset user information blockchain table, determine whether the accessing user is a legitimate user who can access; If the accessing user is a legitimate user with access rights, then the access permission information is returned to the accessed collector; The preset collector blockchain table, the preset user information blockchain table and the preset QR code authority blockchain table are all stored in a preset alliance blockchain.

2. The blockchain-based data access method according to claim 1, characterized in that: Before the step of obtaining the data access permission query request, the method further includes: Obtaining a first registration request issued by a registration collector and a second registration request issued by a registered user, wherein the first registration request includes a registration collector number, and the second registration request includes a registered user name; Registering in a preset alliance blockchain according to the first registration request and the second registration request, generating a collector public key and a collector private key corresponding to the registered collector and returning them to the registered collector, and a user public key and a user private key corresponding to the registered user and returning them to the registered user; A collector blockchain table is generated based on the registered collector number and the collector public key to obtain the preset collector blockchain table, and a user information blockchain table is generated based on the registered user name and the user public key to obtain the preset user information blockchain table.

3. The data access method based on blockchain according to claim 1 is characterized in that: Before the step of searching the preset QR code permission blockchain table for QR code permission information corresponding to the QR code permission chain block number according to the QR code permission chain block number if the QR code generating user is a preset administrator, the step also includes: Obtain the QR code permission information issued by the preset administrator, which includes the preset administrator user name, the preset administrator signature, the legal collector number that can be viewed corresponding to the QR code, and the list of legal user names that can be accessed; Verify whether the preset administrator is a legitimate administrator according to the preset administrator username and the preset administrator signature; If the preset administrator is a legitimate administrator, a QR code permission chain block is generated based on the viewable legitimate collector number and the accessible legitimate user name list corresponding to the QR code in the QR code permission information, and a QR code permission blockchain table is generated based on the QR code permission chain block to obtain the preset QR code permission blockchain table, wherein the QR code permission chain block includes the QR code permission chain block number corresponding to the viewable legitimate collector number corresponding to the QR code.

4. The data access method based on blockchain according to claim 3 is characterized in that: After the step of generating the preset QR code permission blockchain table according to the QR code permission information, the method further includes: The QR code permission chain block number is returned to the preset administrator, and the target QR code is generated with the viewable legal collector number corresponding to the preset administrator user name, the preset administrator signature and the QR code.

5. The blockchain-based data access method according to claim 2, characterized in that: After the step of generating a collector blockchain table based on the registered collector number and the collector public key to obtain the preset collector blockchain table, the method further includes: Obtaining an information modification request from a preset administrator, wherein the information modification request includes a preset administrator signature, a preset administrator user name, a collector number to be modified corresponding to the collector to be modified, and a target state of the collector; Verifying the administrator identity information of the preset administrator according to the preset administrator signature and the preset administrator user name; If the administrator identity information is successfully verified, the identity information of the collector to be modified is verified according to the collector number to be modified and the preset collector blockchain table; If the identity information of the collector to be modified is successfully verified, the collector chain block information corresponding to the collector to be modified in the preset collector blockchain table is modified based on the collector target state; If the identity information verification of the collector to be modified fails, a failure message is returned.

6. The blockchain-based data access method according to claim 5, characterized in that: The information modification request also includes a user name of the user to be modified and a target identity status, and after the step of generating a user information blockchain table based on the registered user name and the user public key to obtain the preset user information blockchain table, the step also includes: If the administrator identity information verification is successful, the identity information of the user to be modified is verified according to the user name of the user to be modified and the preset user information blockchain table; If the identity information of the user to be modified is successfully verified, the user information chain block information corresponding to the username of the user to be modified is modified based on the target identity status; If the identity information verification of the user to be modified fails, a failure message is returned.

7. The data access method based on blockchain according to claim 2 is characterized in that: Generating a collector blockchain table based on the registered collector number and the collector public key to obtain the preset collector blockchain table; And after the step of generating a user information blockchain table based on the registered user name and the user public key to obtain the preset user information blockchain table, the step also includes: The preset user information blockchain table is synchronized to the local of the registered collector, the preset collector blockchain table is synchronized to the local of the registered user, and the preset user information blockchain table and the preset collector blockchain table are synchronized to the local of the preset administrator.

8. A data access device based on blockchain, characterized in that: include: The first acquisition module is used to obtain a data access permission query request, including: the accessing user scans the QR code of the collector to obtain the QR code information; the QR code information includes the QR code permission chain block number, the collector number, the user name of the QR code generating user and the user signature of the QR code generating user; when the accessing user verifies that the accessed collector is a legitimate collector based on the QR code information and when the accessed collector verifies that the user is legitimate, a data access permission query request is sent to a preset alliance blockchain; the data access permission query request includes the accessed collector number, the accessed collector signature and the QR code information; A first judgment module is used to judge whether the visited collector is a legitimate collector based on a preset collector blockchain table, according to the visited collector number and the visited collector signature; A second judgment module is used to judge whether the QR code generating user is a preset administrator according to the user name of the QR code generating user and the user signature of the QR code generating user if the accessed collector is a legitimate collector; A search module, configured to search for the QR code permission information corresponding to the QR code permission chain block number in the preset QR code permission blockchain table according to the QR code permission chain block number if the QR code generating user is a preset administrator; A third judgment module is used to judge whether the accessing user is a legitimate user who can access the QR code according to the QR code permission information and the preset user information blockchain table; A first return module, used for returning access permission information to the visited collector if the visiting user is a legitimate user with access rights; The preset collector blockchain table, the preset user information blockchain table and the preset QR code authority blockchain table are all stored in a preset alliance blockchain.

9. A computer device, characterized in that: It includes a memory and a processor, wherein the memory stores computer-readable instructions, and when the processor executes the computer-readable instructions, the steps of the blockchain-based data access method as described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the blockchain-based data access method as described in any one of claims 1 to 7.

Images