Account management method and device based on a blockchain system, equipment and readable medium

Abstract

The application provides an account management method and device based on a blockchain system, equipment and a readable medium. The method comprises obtaining a login authorization code of a first account according to a logout request triggered by the first account, the login authorization code being used to establish a communication connection between the blockchain node and a remote storage service corresponding to the first account, the communication connection being established according to a login request and a connection verification request sent when the first account logs in the blockchain node; setting the login authorization code to an invalid state, the invalid state being used to indicate that the login authorization code cannot be used to establish a communication connection between the blockchain node and the remote storage service; and clearing business data corresponding to the first account cached by the blockchain node and disconnecting the communication connection between the blockchain node and the remote storage service. The method can avoid the risk of exposing data to subsequent personnel using node equipment, prevent information leakage, and improve data security.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an account management method, apparatus, device, and readable medium based on a blockchain system. Background Technology

[0002] With the development of computer technology, many government and commercial organizations have adopted blockchain systems to manage their operations. However, in such scenarios, it often happens that some nodes in the blockchain are unnecessary or unsuitable to serve as consensus nodes.

[0003] In related technologies, blockchain nodes that do not participate in the accounting consensus form a witness network. These blockchain nodes mainly perform business execution and obtain authorized and visible block data from the consensus network through identity authentication.

[0004] However, such blockchain nodes are usually located in public or untrusted environments. The node equipment of the blockchain node may be shared with unauthorized personnel, and data that is not cleaned up in a timely manner in the node equipment may be viewed by unauthorized personnel, thereby posing a risk of information leakage and affecting data security. Summary of the Invention

[0005] In view of the above-mentioned technical problems, this application provides an account management method, device, electronic device and readable medium based on a blockchain system to avoid the risk of data being exposed to subsequent users of the node device, prevent information leakage and improve data security.

[0006] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part from practice of this application.

[0007] According to one aspect of the embodiments of this application, an account management method based on a blockchain system is provided, wherein each blockchain node in the blockchain system corresponds to at least one account, and each account corresponds to a different remote storage service; including:

[0008] Based on the logout request triggered by the first account, the login authorization code of the first account is obtained. The login authorization code is used to establish a communication connection between the blockchain node and the remote storage service corresponding to the first account. The communication connection is established based on the login request and connection verification request sent by the first account when logging into the blockchain node.

[0009] The login authorization code is set to an invalid state, which indicates that the login authorization code cannot be used to establish a communication connection between the blockchain node and the remote storage service.

[0010] Clear the business data corresponding to the first account cached in the blockchain node and disconnect the communication connection between the blockchain node and the remote storage service.

[0011] According to one aspect of the embodiments of this application, an account management device based on a blockchain system is provided, comprising:

[0012] The logout module is used to obtain the login authorization code of the first account based on the logout request triggered by the first account. The login authorization code is used to establish a communication connection between the blockchain node and the remote storage service corresponding to the first account. The communication connection is established based on the login request and connection verification request sent by the first account when logging into the blockchain node.

[0013] The invalidation setting module is used to set the login authorization code to an invalidation state, which indicates that the login authorization code cannot be used to establish a communication connection between the blockchain node and the remote storage service.

[0014] The connection disconnection module is used to clear the business data corresponding to the first account cached by the blockchain node and disconnect the communication connection between the blockchain node and the remote storage service.

[0015] In one embodiment of this application, based on the above-described solution, the failure setting module includes:

[0016] The write stop unit is used to stop the write operation to the remote storage service corresponding to the first account and obtain the data status of the business data corresponding to the first account in the remote storage service.

[0017] The integrity verification unit is used to generate and store integrity verification information based on the data status of the business data.

[0018] An invalidation request unit is used to send an invalidation request including the login authorization code to the remote storage service, so that the remote storage service rejects the connection verification request containing the login authorization code based on the invalidation request.

[0019] In one embodiment of this application, based on the above-described scheme, the integrity verification unit includes:

[0020] The verification calculation subunit is used to perform verification calculation based on the data status of the business data corresponding to the first account, obtain a verification value, and send the verification value to the remote storage service corresponding to the first account.

[0021] The signature receiving subunit is used to receive the verification signature sent by the remote storage service, wherein the verification signature is obtained by the remote storage service from signing based on the verification value;

[0022] The local storage subunit is used to store the verification value and the verification signature in the local storage of the blockchain node.

[0023] In one embodiment of this application, based on the above-described scheme, the blockchain system further includes a management node; the account management device further includes:

[0024] The verification information acquisition module is used to acquire the login verification information of the first account;

[0025] The login request sending module is used to send a login request including the login verification information to the management node, so that the management node performs login verification based on the login verification information and returns the login verification result.

[0026] The verification result receiving module is used to receive the login verification result, which includes the blockchain registration identifier of the first account, the login authorization code, and the service information of the remote storage service corresponding to the first account.

[0027] The verification request sending module is used to send a connection verification request to the remote storage service based on the service information of the remote storage service. The connection verification request includes the blockchain registration identifier corresponding to the first account and the login authorization code, so as to establish a communication connection with the remote storage service.

[0028] In one embodiment of this application, based on the above-described solution, the account management device further includes:

[0029] The business data acquisition module is used to synchronize data with the management node and obtain the business data corresponding to the first account;

[0030] The validity period check module is used to check the validity period of the login authorization code;

[0031] The business data sending module is used to send the business data to the remote storage service corresponding to the first account according to the login authorization code if the validity period of the login authorization code is met at the current time.

[0032] The renewal request sending module is used to send an authorization code renewal request to the management node if the current time exceeds the validity period of the login authorization code, so that the management node extends the validity period of the login authorization code.

[0033] In one embodiment of this application, based on the above-described solution, the account management device further includes:

[0034] The verification information acquisition module is used to acquire the integrity verification information and obtain the storage data from the remote storage service corresponding to the first account.

[0035] The consistency verification module is used to perform consistency verification on the business data corresponding to the first account based on the integrity verification information.

[0036] The data synchronization module is used to synchronize data with the management node based on the stored data of the remote storage service if the consistency check passes.

[0037] The storage data deletion module is used to delete the storage data in the remote storage service corresponding to the first account and re-obtain the business data corresponding to the first account from the management node if the consistency check fails.

[0038] According to one aspect of the embodiments of this application, an account management method based on a blockchain system is provided, wherein each blockchain node in the blockchain system corresponds to at least one account, each account corresponds to a different remote storage service, and each account is used to log in to the blockchain node to establish a communication connection between the blockchain node and the corresponding remote storage service; the method includes:

[0039] Receive the login request sent by the blockchain node and perform login verification based on the login verification information in the login request;

[0040] If the login verification is successful, the login authorization code is obtained based on the login verification information, and the login verification result is sent to the blockchain node. The login verification result includes the blockchain registration identifier of the first account, the login authorization code, and the service information of the remote storage service corresponding to the first account.

[0041] The system receives an authorization code verification request sent by the remote storage service. The authorization code verification request is generated by the blockchain node based on the login verification result. The authorization code verification request includes the blockchain registration identifier and the login authorization code.

[0042] The login authorization code is validated based on the blockchain registration identifier, and the validation result is sent to the remote storage service so that the blockchain node establishes a communication connection with the remote storage service.

[0043] According to one aspect of the embodiments of this application, an account management device based on a blockchain system is provided, wherein each blockchain node in the blockchain system corresponds to at least one account, each account corresponds to a different remote storage service, and each account is used to log in to the blockchain node to establish a communication connection between the blockchain node and the corresponding remote storage service; the method includes:

[0044] The login request receiving module is used to receive the login request sent by the blockchain node and perform login verification according to the login verification information in the login request;

[0045] The login verification request module is used to obtain a login authorization code based on the login verification information if the login verification is successful, and send the login verification result to the blockchain node. The login verification result includes the blockchain registration identifier of the first account, the login authorization code, and the service information of the remote storage service corresponding to the first account.

[0046] The authorization code verification module is used to receive the authorization code verification request sent by the remote storage service. The authorization code verification request is generated by the blockchain node based on the login verification result. The authorization code verification request includes the blockchain registration identifier and the login authorization code.

[0047] The validity verification module is used to verify the validity of the login authorization code based on the blockchain registration identifier, and send the validity verification result to the remote storage service so that the blockchain node and the remote storage service can establish a communication connection.

[0048] In one embodiment of this application, based on the above-described solution, the account management device further includes:

[0049] The registration request receiving module is used to receive account registration requests and generate a blockchain registration identifier based on the account registration requests;

[0050] The registration request sending module is used to send a service registration request to the remote storage service, wherein the service registration request includes the blockchain registration identifier;

[0051] The registration response receiving module is used to receive a service registration response, which contains service information of the remote storage service corresponding to the blockchain registration identifier.

[0052] In one embodiment of this application, an account management method based on a blockchain system is provided. Each blockchain node in the blockchain system corresponds to at least one account, and each account corresponds to a different remote storage service. Each account is used to log in to the blockchain node to establish a communication connection between the blockchain node and the corresponding remote storage service; the method includes:

[0053] Receive a connection verification request sent by the blockchain node, the connection verification request including the blockchain registration identifier and login authorization code of the first account;

[0054] Based on the connection verification request, an authorization code verification request, the blockchain registration identifier, and the login authorization code are sent to the management node;

[0055] Receive the verification result sent by the management node, the verification result including the verification result of the validity of the login authorization code;

[0056] If the verification result indicates that the login authorization code is valid, then a communication connection is established with the blockchain node.

[0057] In one embodiment of this application, an account management device based on a blockchain system is provided. Each blockchain node in the blockchain system corresponds to at least one account, and each account corresponds to a different remote storage service. Each account is used to log in to the blockchain node to establish a communication connection between the blockchain node and the corresponding remote storage service; including:

[0058] A connection request receiving module is used to receive a connection verification request sent by the blockchain node, wherein the connection verification request includes the blockchain registration identifier and login authorization code of the first account;

[0059] The authorization code verification request module is used to send an authorization code verification request, the blockchain registration identifier and the login authorization code to the management node according to the connection verification request;

[0060] The verification result receiving module is used to receive the verification result sent by the management node, the verification result including the verification result of the validity of the login authorization code;

[0061] The communication connection establishment module is used to establish a communication connection with the blockchain node if the verification result indicates that the login authorization code is valid.

[0062] In one embodiment of this application, based on the above-described solution, the account management device further includes:

[0063] The registration request receiving module is used to receive the service registration request sent by the management node, wherein the service registration request includes the blockchain registration identifier of the first account;

[0064] A remote storage service generation module is used to respond to the service registration request and generate a remote storage service corresponding to the first account based on the blockchain registration identifier.

[0065] The registration response sending module is used to send a service registration response to the management node. The service registration response contains service information of the remote storage service corresponding to the first account.

[0066] In one embodiment of this application, based on the above-described solution, the account management device further includes:

[0067] An invalidation request receiving module is used to receive invalidation requests, wherein the invalidation request contains the login authorization code of the second account;

[0068] The validity period acquisition module is used to acquire the validity period of the login authorization code of the second account based on the expiration request;

[0069] The expiration record module is used to add the login authorization code of the second account and the validity period to the expiration authorization code record.

[0070] In one embodiment of this application, based on the above scheme, the authorization code verification request module includes:

[0071] A login authorization code lookup unit is used to look up the login authorization code in the connection verification request from the expired authorization code record;

[0072] The connection rejection unit is configured to reject the connection verification request if the expired authorization code record contains the login authorization code in the connection verification request, and the validity period of the login authorization code in the expired authorization code record is currently met.

[0073] The verification request sending unit is used to send an authorization code verification request to the management node if the expired authorization code record does not contain the login authorization code in the connection verification request, or if the validity period in the expired authorization code record is not met at the current time.

[0074] According to one aspect of the embodiments of this application, an electronic device is provided, the electronic notification device comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the account management method based on a blockchain system as described above by executing the executable instructions.

[0075] According to one aspect of the embodiments of this application, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the account management method based on a blockchain system as described above.

[0076] According to one aspect of the embodiments of this application, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the account management method based on a blockchain system provided in the various optional implementations described above.

[0077] In the embodiments of this application, the synchronized data is stored in a remote storage service, and the remote storage service is disconnected during the logout process, so that the node device cannot access the data in the remote storage service after logging out, thereby avoiding the risk of data being exposed to subsequent users of the node device, preventing information leakage, and improving data security.

[0078] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0079] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0080] In the attached diagram:

[0081] Figure 1 A schematic diagram of the blockchain network structure is shown.

[0082] Figures 2 to 4 The diagram shows the architecture of the blockchain system used in the embodiments of this application.

[0083] Figure 5 A schematic diagram of an electronic invoice system according to an embodiment of this application is shown.

[0084] Figure 6 A flowchart illustrating an embodiment of an account management method based on a blockchain system according to this application is shown;

[0085] Figure 7 A schematic diagram of a remote storage system connection process according to an embodiment of this application is shown;

[0086] Figure 8 A block diagram of an account management device based on a blockchain system according to an embodiment of this application is shown;

[0087] Figure 9 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown. Detailed Implementation

[0088] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this application more comprehensive and complete, and to fully convey the concept of the exemplary embodiments to those skilled in the art.

[0089] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this application.

[0090] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0091] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0092] Blockchain is a novel application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and cryptographic algorithms. Essentially, a blockchain is a decentralized database, a chain of data blocks (i.e., blocks) linked together using cryptographic methods. Each data block contains information about a batch of network transactions, used to verify the validity of the information (anti-counterfeiting) and to generate the next block. A blockchain can include an underlying platform, a platform product and service layer, and an application service layer.

[0093] The underlying blockchain platform can include processing modules such as user management, basic services, smart contracts, and operational monitoring. The user management module is responsible for managing the identity information of all blockchain participants, including maintaining public and private key generation (account management), key management, and maintaining the correspondence between user real identities and blockchain addresses (access management). Furthermore, under authorization, it monitors and audits transactions of certain real identities and provides risk control rule configuration (risk control audit). The basic services module is deployed on all blockchain node devices to verify the validity of business requests. After consensus is reached on valid requests, they are recorded in storage. For a new business request, the basic services first perform interface adaptation parsing and authentication (interface adaptation), and then encrypt the business information through a consensus algorithm (consensus management). After encryption, the data is transmitted completely and consistently to the shared ledger (network communication) and recorded and stored. The smart contract module is responsible for contract registration, issuance, triggering, and execution. Developers can define contract logic using a programming language and publish it to the blockchain (contract registration). According to the contract terms, the key or other events are invoked to trigger execution and complete the contract logic. It also provides functions for contract upgrades and cancellations. The operation monitoring module is mainly responsible for deployment, configuration modification, contract settings, cloud adaptation, and real-time status visualization output during product release, such as alarms, monitoring network conditions, and monitoring the health status of node devices.

[0094] The platform's product service layer provides the basic capabilities and implementation frameworks for typical applications. Developers can leverage these basic capabilities, along with the specific characteristics of their business needs, to implement blockchain-based business logic. The application service layer provides blockchain-based application services to business stakeholders.

[0095] See Figure 1 The illustrated blockchain network may include multiple nodes 101, which can be various clients forming the blockchain network. Each node 101, in its normal operation, receives input information and maintains shared data within the blockchain network based on this information. To ensure information exchange within the blockchain network, information connections can exist between each node, allowing for information transmission. For example, when any node in the blockchain network receives input information, other nodes in the network retrieve this input information according to a consensus algorithm and store it as shared data, ensuring data consistency across all nodes in the blockchain network.

[0096] Each node in a blockchain network has a corresponding node identifier, and each node can store the node identifiers of other nodes. This allows for the broadcast of generated blocks to other nodes in the blockchain network based on their node identifiers. Each node can maintain a list of node identifiers, storing the node name and its corresponding node identifier in this list. The node identifier can be an IP (Internet Protocol) address or any other information that can be used to identify the node.

[0097] Each node in a blockchain network stores the same blockchain. A blockchain consists of multiple blocks. The genesis block includes a block header and a block body. The block header stores input information features, version number, timestamp, and difficulty value, while the block body stores the input information. The next block after the genesis block is its parent block. The next block also includes a block header and a block body. The block header stores the current block's input information features, the parent block's header features, version number, timestamp, and difficulty value, and so on. This ensures that the data stored in each block is related to the data stored in its parent block, guaranteeing the security of the input information within each block.

[0098] When generating blocks in the blockchain, each node receiving input information verifies it. After verification, the input information is stored in a memory pool, and its hash tree used to record input information is updated. Next, the timestamp is updated to reflect the time the input information was received, and different random numbers are tried multiple times to calculate the feature value. When a random number that meets the conditions is obtained, the corresponding information is stored, generating the block header and block body, thus obtaining the current block. Subsequently, the blockchain node sends the newly generated block to other nodes in its data sharing system based on their node identifiers. These other nodes verify the newly generated block and, after verification, add it to their stored blockchain. Nodes can verify newly generated blocks through consensus algorithms, which may include, but are not limited to: PoW (Proof-of-Work), PoS (Proof-of-Stake), DPoS (Delegated Proof of Stake), PBFT (Practical Byzantine Fault Tolerance), Paxos, and Raft. PoW (Proof-of-Work) is a measurement method used by a system (such as the aforementioned blockchain network system) to achieve a specific goal. PoS (Proof-of-Stake) is an upgraded consensus mechanism of PoW; specifically, the longer someone holds electronic resources (holding time = quantity of electronic resources * holding time), the greater their chance of obtaining the right to record blocks. DPoS (Delegated Proof of Stake): Similar to a board of directors vote, holders of electronic resources elect a certain number of nodes to act as proxies for verification and record-keeping. PBFT (Practical Byzantine Fault Tolerance): A message-passing-based consensus algorithm that achieves consensus through three phases, which may be repeated if failures occur. Paxos (a distributed algorithm): A two-phase algorithm with three main roles: proposer, acceptor, and learner.The proposer proposes a motion, the acceptor agrees or rejects, and the learner obtains the final value after consensus is reached. Raft (a distributed consensus algorithm): The Raft algorithm has three roles: follower, candidate, and leader. All nodes initially start as followers. Followers that do not receive a heartbeat within a timeout period become candidates and broadcast a vote request. The node that receives a majority of votes becomes the leader. In this round of voting, whoever sends the request first has the advantage, and each node only gives one vote.

[0099] Optionally, each node in the blockchain network can be a server or a terminal device. A server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. Terminal devices can be smartphones, tablets, laptops, desktop computers, smart speakers, smartwatches, smart home devices, in-vehicle terminals, etc., but are not limited to these. Nodes can be directly or indirectly connected via wired or wireless communication, and this application does not impose any restrictions on this.

[0100] The aforementioned cloud computing refers to the delivery and usage model of IT infrastructure, specifically the acquisition of required resources through the network in an on-demand and easily scalable manner. In a broader sense, cloud computing refers to the delivery and usage model of services, namely, the acquisition of required services through the network in an on-demand and easily scalable manner. These services can be IT and software-related, internet-related, or other services. Cloud computing is a product of the convergence and development of traditional computer and network technologies such as grid computing, distributed computing, parallel computing, utility computing, network storage technologies, virtualization, and load balancing. Driven by the development of the internet, real-time data streams, the diversification of connected devices, and the demands of search services, social networks, mobile commerce, and open collaboration, cloud computing has rapidly developed. Unlike previous parallel and distributed computing, the emergence of cloud computing will, conceptually, drive a revolutionary change in the entire internet model and enterprise management model.

[0101] Based on blockchain technology, embodiments of this application propose an architecture for a blockchain system. For example... Figure 2 As shown, the blockchain system includes a ledger node network 2 and a business node network 1. The ledger node network 2 includes ledger nodes 21 that reach consensus on data blocks and record them on the blockchain. The business node network 1 includes business nodes 11, which can verify the data blocks recorded on the blockchain by the ledger nodes or request corresponding transaction data from the ledger nodes.

[0102] Specifically, the verification of data blocks recorded on the blockchain by the accounting nodes by business node 11 may include the following steps: An accounting node 21 in the accounting node network uses a key specific to that accounting node to generate a signature based on the transaction information to be included in a data block to be added to the blockchain; accounting node 21 adds the transaction information and the generated signature to the data block and adds it to the blockchain; accounting node 21 sends the signature to a business node in the business node network, and the business node verifies the signature using its key specific to that accounting node, thereby enabling business node 11 to verify the data blocks recorded on the blockchain by the accounting nodes. The accounting nodes in the accounting node network are responsible for recording data blocks to the blockchain, and the business nodes in the business node network are responsible for witnessing the results of the accounting node recording. Specifically, the accounting node generates a signature based on the transaction information to be included in a data block to be added to the blockchain, then adds the transaction information and the generated signature to the data block and uploads it to the blockchain. The signature is then sent to a business node in the business node network, allowing the business node to verify the signature using its key specific to that accounting node. In the business node network, business nodes can witness the transaction data of the entire network by verifying the signatures of the ledger nodes on the blocks. Although the ledger node network has a monopoly on the right to record transactions, all actions are publicly traceable because the data blocks have digital signatures representing the identities of the ledger recorders. If the ledger nodes collectively commit malicious acts, then all nodes in the business node network will retain evidence of the specific ledger nodes' malicious actions. Compared to traditional centralized systems and private blockchains, the system in this embodiment operates more transparently; and compared to traditional decentralized solutions, this solution is more controllable and easier to supervise.

[0103] In one embodiment of this application, the ledger node network 2 and the business node network 1 can be connected via a proxy node 12. The proxy node 12 can be a business node in the business node network 1, responsible for transmitting information from the ledger node 21 to the business node 11. The business node 11 is the terminal of the transaction party that generates various transaction data that needs to be uploaded to the blockchain, and can also be a terminal that queries transaction data from the ledger node network 2. The transaction data generated by the business node 11 is transmitted to the ledger node 21 through the proxy node 12, and then recorded on the blockchain after consensus. This facilitates the unified processing and supervision of transaction data. The business node 11 can also supervise and witness the on-chain uploading of transaction data through the information sent by the ledger node 21 via the proxy node 12. This is of great significance in scenarios where unified supervision is needed, but there is also a fear of collective cheating by the monitored nodes.

[0104] exist Figure 1 In the structure shown, business node network 1 adopts a P2P (Peer-to-Peer) network model. A P2P network is a distributed application architecture that distributes tasks and workloads among peers. It is a network form or topology of the peer-to-peer computing model at the application layer, i.e., a "point-to-point" or "end-to-end" network. It can be defined as follows: network participants share a portion of their hardware resources (processing power, storage capacity, network connectivity, printers, etc.). These shared resources provide services and content through the network and can be directly accessed by other peer nodes without going through an intermediary entity. Participants in this network are both providers and recipients of resources, services, and content. Therefore, in business node network 1, when agent node 12 receives a message from accounting node 21, it propagates it to surrounding business nodes 11. The surrounding business nodes 11 receive the message and then propagate it to their neighboring business nodes 11, achieving the propagation of the message among all business nodes 11 in business node network 1.

[0105] Figure 3 This illustrates the architecture of another blockchain system used in the embodiments of this application. This architecture is similar to... Figure 2 The difference in the architecture shown is that a P2P network mode is not adopted in business node network 1; instead, a broadcast network mode is used. Specifically, after receiving a message from accounting node 21, agent node 12 broadcasts the message to other business nodes 11 in business node network 1. In this way, the message is also propagated among each business node 11 in business node network 1.

[0106] Figure 4 This illustrates another blockchain system architecture used in embodiments of the present invention. This architecture is similar to... Figure 2 The difference in the illustrated architecture lies in that its ledger node network 2 is divided into multiple branch ledger node networks. Each branch ledger node network is responsible for recording a specific type of transaction information. For example, a company may have supply chain finance business and may need to record contract information, outstanding payments, and other information generated during the supply and sales process on the blockchain. Simultaneously, the company also needs to issue invoices and record invoice information and invoice reimbursement information on the blockchain. In this case, to facilitate the supervision of ledger nodes by the same department, the ledger nodes recording supply chain finance transactions and those recording transactions during the invoice circulation process may belong to different departments. For example, the ledger node recording supply chain finance transactions might be a bank-set ledger terminal, while the ledger node recording transactions during the invoice circulation process might be a tax authority-set ledger terminal. Furthermore, supply chain finance transactions and invoice circulation transactions may ultimately be recorded on different branch ledger node networks. In this case, the agent node 12, based on the transaction type carried in the transaction information sent from the business node 11, sends the transaction information to the branch ledger node network corresponding to that transaction type.

[0107] It should be noted that, in Figures 2 to 4 In the architecture of the blockchain system shown, the proxy node 12 is located in the business node network 1. In other embodiments of this application, the proxy node 12 may also be located in the consensus node network 2, or be independent of the business node network 1 and the consensus node network 2.

[0108] Figures 2 to 4 The architecture of the blockchain system shown can be applied to electronic invoice scenarios, which will be elaborated in detail below:

[0109] In one embodiment of this application, the accounting nodes in the accounting node network can be various State Taxation Administration terminals, for example, the accounting node network can be composed of State Taxation Administration terminals deployed in multiple regions, each serving as an accounting node. The business nodes in the business node network can be local tax bureau terminals, invoicing agent service provider terminals, invoicing enterprise terminals, individual user terminals, etc.

[0110] Specifically, in Figure 5 The electronic invoice system shown can include a business layer, a routing proxy layer, and a consensus network (i.e., an accounting node network, hereinafter referred to as the accounting network) layer. The business layer is the business node network, which contains various business nodes, such as local tax bureaus located in a dedicated tax network; invoicing service providers, reimbursement service providers, and enterprises located in a public cloud; and payment service providers, circulation service providers, and enterprises located in a private cloud.

[0111] The routing proxy layer includes proxy nodes that provide routing services, certificate caching and authentication services, P2P services, and other functions. The routing proxy layer isolates the business layer and the consensus network layer, as detailed in the technical solution of the aforementioned embodiments. Optionally, the proxy nodes in the routing proxy layer can be located within a tax-related private network. The consensus network (ledger network) layer is the ledger node network, which includes multiple blockchains. Of course, in other embodiments of this application, the consensus network (ledger network) layer may also include only one blockchain.

[0112] In one embodiment of this application, the consensus network (ledger network) of the electronic invoice system can include multiple blockchains. These blockchains can be divided into chains according to time sequence, such as chains for the same business transaction, where the business participants are consistent, and both blockchains use the same CA (Certificate Authority) center as the authentication and authorization party for the invoice business system. Of course, in one embodiment of this application, chains can be divided according to different business transactions, such as one blockchain for business A and another for business B, and cross-chain interaction between businesses is also possible.

[0113] In response to the multi-chain scenarios described in the foregoing embodiments, this application also proposes an account management method based on a blockchain system, which is described in detail below:

[0114] Figure 6 A flowchart illustrating an account management method based on a blockchain system according to an embodiment of this application is shown. Specifically, the solution of this application can be applied to... Figure 5 The blockchain system shown contains a main chain and at least one sub-chain, each derived from a block height in the main chain. Business nodes connect to the blockchain system and access data through login authentication. Figure 6 The account management method based on the blockchain system shown can be executed by business nodes in the blockchain system. Each business node corresponds to at least one account, and each account corresponds to a different remote storage service. Specifically, refer to... Figure 6 As shown, the account management method based on the blockchain system includes at least steps S610 to S630, which are described in detail below:

[0115] Step S610: Based on the logout request triggered by the first account, obtain the login authorization code of the first account. The login authorization code is used to establish a communication connection between the blockchain node and the remote storage service corresponding to the first account. The communication connection is established based on the login request and connection verification request sent by the first account when logging into the blockchain node.

[0116] The first account is one of at least one accounts corresponding to a blockchain node. In this embodiment, the first account has already logged into the blockchain node. During the login process of the first account, the blockchain node initiates a login request to verify the login information and obtain a login authorization code. Then, using the login authorization code, it initiates a connection verification request to establish a communication connection with the remote storage service corresponding to the first account. This communication connection is typically a remote network connection. The remote storage service is mounted to the blockchain node to become the node's storage, while the blockchain node stores synchronously obtained data and other information in the remote storage service to replace local storage. Specifically, the remote storage service is a mountable encrypted network storage (secure elastic file system, SEFS), a secure storage device with encrypted network access. The connection process of the remote storage service is performed based on the same verification information as the login process of the first account.

[0117] The login authorization code is a time-sensitive verification information provided by the blockchain system when the first account logs in. The first account uses this verification information to link to the remote storage service, and also provides the login authorization code for verification when communicating with the remote storage service.

[0118] Logout requests are typically initiated by the user or by the node device based on preset conditions, such as a period of no user activity or data communication. Blockchain nodes can obtain the login authorization code for the first account by either reading it directly from local storage or requesting it from the blockchain node.

[0119] Step S620: Set the login authorization code to an invalid state. The invalid state is used to indicate that the login authorization code cannot be used to establish a communication connection between the blockchain node and the remote storage service.

[0120] Setting a login authorization code to an invalid state can involve recording the invalidation in local storage or sending information to remote storage services and the blockchain system to record the invalid login authorization code. An invalid login authorization code indicates that it can no longer be used by the blockchain node to establish a communication connection with the remote storage service. Specifically, the duration of this invalidation state can be the same as the validity period of the login authorization code. The validity period of the login authorization code refers to the time period during which it can be used to log in to the blockchain system. If an account logs out within the validity period of the login authorization code, the login authorization code will be set to an invalid state for that period. After the validity period expires, the login authorization code will no longer be set to an invalid state but will return to a valid state and can be used to connect to the remote storage service. For example, if an account obtains a login authorization code with a validity period of 12 hours and logs out with 6 hours remaining, the login authorization code will be set to an invalid state for the remaining 6 hours. After the remaining 6 hours, the login authorization code will no longer be invalid and can be reused to connect to the remote storage service.

[0121] In one embodiment of this application, based on the above scheme, the process of setting the login authorization code to an invalid state may include the following steps: The blockchain node stops writing operations to the remote storage service corresponding to the first account and obtains the data status of the business data corresponding to the first account in the remote storage service. In-progress writing operations will continue, while writing operations that have not yet started will be canceled. The data status of the business data refers to the status of all data related to the first account in the remote storage service. Integrity verification information is generated and stored based on the data status of the business data. The calculation of the integrity verification information is performed by the blockchain node, specifically by calculating the data checksum or performing encrypted calculations according to a predetermined algorithm. The integrity verification information is saved by the user, either to local storage or to a mobile storage device. Subsequently, an invalidation request including the login authorization code is sent to the remote storage service, causing the remote storage service to reject the connection verification request containing the login authorization code. The remote storage service may directly record the login authorization code for comparison during verification.

[0122] In one embodiment of this application, based on the above scheme, the process of generating and storing integrity verification information according to the data status of the business data may include the following steps: performing verification calculations based on the data status of the business data corresponding to the first account to obtain a verification value, and sending the verification value to the remote storage service corresponding to the first account; receiving a verification signature sent by the remote storage service, wherein the verification signature is obtained by the remote storage service signing based on the verification value; and storing the verification value and the verification signature in the local storage of the blockchain node.

[0123] In one embodiment of this application, based on the above scheme, the blockchain system further includes a management node. The management node can be a computing device in the blockchain system used to perform system management services. This computing device can be used for system functions such as user registration and login authorization. Before the step of obtaining the login authorization code of the first account based on the logout request triggered by the first account, the account management method further includes the following steps: obtaining login verification information of the first account; sending a login request including the login verification information to the management node, so that the management node performs login verification based on the login verification information and returns a login verification result. Then, the login verification result is received, the login verification result including the blockchain registration identifier of the first account, the login authorization code, and service information of the remote storage service corresponding to the first account. Wherein, the blockchain registration identifier is a unique identifier registered by the first account on the blockchain, and the service information of the remote storage service may include information related to establishing a communication connection, such as the internet address and port of the remote storage service. Based on the service information of the remote storage service, a connection verification request is sent to the remote storage service, the connection verification request including the blockchain registration identifier corresponding to the first account and the login authorization code, to establish a communication connection with the remote storage service.

[0124] In one embodiment of this application, based on the above scheme, after sending a connection verification request to the remote storage service according to the service information of the remote storage service, the account management method further includes the following steps: synchronizing data with the management node to obtain the business data corresponding to the first account; checking the validity period of the login authorization code; if the validity period of the login authorization code is met at the current time, then sending the business data to the remote storage service corresponding to the first account according to the login authorization code; if the validity period of the login authorization code has expired at the current time, then sending an authorization code renewal request to the management node so that the management node extends the validity period of the login authorization code.

[0125] In one embodiment of this application, based on the above scheme, after sending a connection verification request to the remote storage service according to the service information of the remote storage service, the account management method further includes the following steps: obtaining the integrity verification information and obtaining storage data from the remote storage service corresponding to the first account; performing consistency verification on the business data corresponding to the first account according to the integrity verification information; if the consistency verification passes, synchronizing data with the management node based on the storage data of the remote storage service; if the consistency verification fails, deleting the storage data in the remote storage service corresponding to the first account and re-obtaining the business data corresponding to the first account from the management node. Specifically, during login, it is necessary to verify whether the data in the remote storage service is consistent with the previous one based on the integrity verification. If inconsistent, it is necessary to re-obtain the complete data from the blockchain system and store it in the remote storage service. If consistent, data synchronization with the blockchain system can be performed based on the data in the remote storage service.

[0126] Step S630: Clear the business data corresponding to the first account cached by the blockchain node and disconnect the communication connection between the blockchain node and the remote storage service.

[0127] In the embodiments of this application, the synchronized data is stored in a remote storage service, and the remote storage service is disconnected during the logout process, so that the node device cannot access the data in the remote storage service after logging out, thereby avoiding the risk of data being exposed to subsequent users of the node device, preventing information leakage, and improving data security.

[0128] This application also proposes an account management method based on a blockchain system, which is described in detail below: According to an embodiment of this application, the account management method based on a blockchain system allows other blockchains to initiate cross-chain transactions to this blockchain. Specifically, the solution of this application can be applied to... Figure 5 The blockchain system shown includes a main chain and at least one sub-chain, each sub-chain being derived from a block height in the main chain. Business nodes connect to the blockchain system and retrieve data through login authentication, while the management node responds to and controls the login process of the blockchain nodes. Each blockchain node in the system corresponds to at least one account, and each account corresponds to a different remote storage service. Each account is used to log in to the blockchain node to establish a communication connection between the blockchain node and the corresponding remote storage service. This blockchain-based account management method can be executed by the management node in the blockchain system. Specifically, this blockchain-based account management method includes at least the following steps: S641 to S644.

[0129] Step S641: Receive the login request sent by the blockchain node and perform login verification according to the login verification information in the login request.

[0130] Login verification information typically includes a user's username and password. Blockchain nodes send login requests based on the user's input. During login verification, the system uses this information to determine if the requesting user has permission to log in to the blockchain system. Accounts that pass login verification can then log in to the blockchain system.

[0131] In one embodiment of this application, based on the above scheme, before receiving the login request sent by the blockchain node, the method further includes: receiving an account registration request and generating a blockchain registration identifier based on the account registration request; sending a service registration request to the remote storage service, the service registration request including the blockchain registration identifier; and receiving a service registration response, the service registration response containing service information of the remote storage service corresponding to the blockchain registration identifier. Specifically, during the user registration process, the management node automatically registers the remote storage service for the user, so that the remote storage service allocates corresponding storage space to the user.

[0132] Step S642: If the login verification is successful, obtain the login authorization code based on the login verification information and send the login verification result to the blockchain node. The login verification result includes the blockchain registration identifier of the first account, the login authorization code, and the service information of the remote storage service corresponding to the first account.

[0133] The login authorization code is automatically generated by the management node. The blockchain registration identifier can be determined based on the login verification information provided by the user, such as directly using the user's username, or it can be generated by the management node and assigned to the user account. The service information of the remote storage service is information obtained by the management node after the user registers with the remote storage service, and is used for subsequent connection establishment between blockchain nodes and the remote storage service.

[0134] Step S643: Receive an authorization code verification request sent by the remote storage service. The authorization code verification request is generated by the blockchain node based on the login verification result. The authorization code verification request includes the blockchain registration identifier and the login authorization code.

[0135] After receiving successful login confirmation from the management node, a blockchain node initiates a connection verification with the remote storage service based on the received service information and login authorization code. This allows it to connect to the remote storage service and mount the corresponding storage space. The remote storage service, in turn, verifies the correctness of the login authorization code with the management node. Therefore, the management node receives the authorization code verification request from the remote storage service and checks whether the received blockchain registration identifier and login authorization code are correctly matched, thus determining the verification result.

[0136] Step S644: Verify the validity of the login authorization code based on the blockchain registration identifier, and send the verification result to the remote storage service so that the blockchain node establishes a communication connection with the remote storage service.

[0137] Specifically, during the verification process, the login authorization code recorded locally is obtained based on the blockchain registration identifier, and then compared with the login authorization code in the request to determine whether the authorization codes match and whether the login authorization code is valid. Furthermore, the management node can also determine whether the login authorization code is expired. After determining the result, the verification result is sent to the remote storage service, allowing the remote storage service to either agree or refuse to establish a connection with the blockchain node.

[0138] In this application, both the verification of the management node and the verification of the remote storage service are based on the login authorization code, which allows the login process and the remote connection process to be completed uniformly by the management node, reducing the operational difficulty of the login process and improving the efficiency of use.

[0139] This application also proposes an account management method based on a blockchain system, which is described in detail below: According to an embodiment of this application, the account management method based on a blockchain system allows other blockchains to initiate cross-chain transactions to this blockchain. Specifically, the solution of this application can be applied to... Figure 5 The blockchain system shown includes a main chain and at least one sub-chain, each sub-chain being derived from a block height in the main chain. Business nodes connect to the blockchain system through login authentication and retrieve data from the blockchain system, and connect to remote storage services to store synchronized data. Each blockchain node in the system corresponds to at least one account, and each account corresponds to a different remote storage service. This blockchain-based account management method can be executed by the remote storage service; specifically, the blockchain-based account management method includes at least steps S645 to S648 as follows:

[0140] Step S645: Receive a connection verification request sent by the blockchain node. The connection verification request includes the blockchain registration identifier and login authorization code of the first account.

[0141] Specifically, a connection verification request is a request initiated by a blockchain node during the login process to establish a communication connection between the blockchain node and the remote storage service.

[0142] Step S646: Based on the connection verification request, send an authorization code verification request, the blockchain registration identifier, and the login authorization code to the management node.

[0143] In one embodiment of this application, based on the above scheme, before the process of receiving the connection verification request sent by the blockchain node, the method further includes the following steps: receiving a service registration request sent by the management node, the service registration request including the blockchain registration identifier of the first account; responding to the service registration request, generating a remote storage service corresponding to the first account according to the blockchain registration identifier; and sending a service registration response to the management node, the service registration response containing service information of the remote storage service corresponding to the first account.

[0144] In one embodiment of this application, based on the above scheme, before the process of receiving the connection verification request sent by the blockchain node, the method further includes the following steps: receiving an invalidation request, the invalidation request containing a login authorization code of a second account; obtaining the validity period of the login authorization code of the second account according to the invalidation request; and adding the login authorization code of the second account and the validity period to an invalidation authorization code record. Specifically, for the logout process of another account, the validity of the corresponding login authorization code is recorded, and in subsequent processes, the invalidation authorization code record is used to check whether the login authorization code has expired.

[0145] Step S647: Receive the verification result sent by the management node, the verification result including the verification result of the validity of the login authorization code.

[0146] In one embodiment of this application, based on the above scheme, the process of sending an authorization code verification request to the management node according to the connection verification request includes the following steps: First, search the expired authorization code record for the login authorization code in the connection verification request; if the expired authorization code record contains the login authorization code in the connection verification request, and the validity period of the login authorization code in the expired authorization code record is currently met, then the login authorization code is expired, and the connection verification request is rejected; if the expired authorization code record does not contain the login authorization code in the connection verification request, then the login authorization code is valid, or the validity period in the expired authorization code record is not currently met, then although the login authorization code was previously expired, it is now valid, and therefore, an authorization code verification request is sent to the management node.

[0147] Step S648: If the verification result indicates that the login authorization code is valid, then establish a communication connection with the blockchain node.

[0148] The following combination Figure 7 The implementation details of the technical solutions in the embodiments of this application are described in detail, such as... Figure 7 As shown, the blockchain node is shared by User 1 and User 2. Taking the tax management system as an example, User 1 logs in to the tax management terminal from the device on the blockchain node, thereby obtaining User 1's corresponding blockchain registration identifier SPVID1, the corresponding login verification code AuthToken, and the SEFS address.

[0149] Subsequently, after the tax management system confirms the login, the blockchain node device interacts with SEFS using SPVID and AuthToken as parameters to log in. During the connection process, SEFS verifies the validity of the login verification code AuthToken by verifying it with the backend gateway of the tax management system. Figure 7 As shown, after successful verification, the blockchain node device is mounted in the storage space and communicates with the SEFS corresponding to SPVID1 via AuthToken.

[0150] When user 1 logs out, firstly, the blockchain nodes stop writing to SEFS. Then, the blockchain nodes calculate a checksum of the SEFS data state, which is signed by the SEFS service and returned to the user's SPV service. This checksum and signature file are stored by the user on their local disk for future verification. Next, the cumulative resource usage and logout behavior of the user corresponding to the SPVID are recorded and reported. If the preceding steps are successful, the authtoken is set to be invalid for SEFS during its validity period; that is, after logging out once, the authtoken cannot be used to log in to SEFS again unless a new authtoken is obtained by logging back into the tax management system. Finally, the SEFS network storage is unmounted to disconnect from SEFS, local cached data and memory cached data are cleared, and the login process of the tax management system is exited.

[0151] Subsequently, when User 2 logs in through this blockchain node device, the blockchain node device connects to another SEFS corresponding to SPVID1. However, when all users log out, the blockchain node device does not connect to any SEFS, and related information cannot be accessed through the blockchain node device.

[0152] In the specific implementation of this application, data such as user information and transaction data in the blockchain are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0153] It should be noted that although the steps of the method in this application are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0154] The following describes the implementation of the apparatus of this application, which can be used to execute the account management method based on the blockchain system in the above embodiments of this application. Figure 8 A schematic block diagram illustrating the components of an account management device based on a blockchain system, as shown in an embodiment of this application, is provided. Figure 8 As shown, each blockchain node in the blockchain system corresponds to at least one account, and each account corresponds to a different remote storage service. The account management device 800 based on the blockchain system mainly includes:

[0155] The logout module 810 is used to obtain the login authorization code of the first account based on the logout request triggered by the first account. The login authorization code is used to establish a communication connection between the blockchain node and the remote storage service corresponding to the first account. The communication connection is established based on the login request and connection verification request sent by the first account when logging into the blockchain node.

[0156] The invalidation setting module 820 is used to set the login authorization code to an invalidation state, the invalidation state being used to indicate that the login authorization code cannot be used to establish a communication connection between the blockchain node and the remote storage service.

[0157] The connection disconnection module 830 is used to clear the business data corresponding to the first account cached by the blockchain node and disconnect the communication connection between the blockchain node and the remote storage service.

[0158] In one embodiment of this application, based on the above-described solution, the failure setting module 820 includes:

[0159] The write stop unit is used to stop the write operation to the remote storage service corresponding to the first account and obtain the data status of the business data corresponding to the first account in the remote storage service.

[0160] The integrity verification unit is used to generate and store integrity verification information based on the data status of the business data.

[0161] An invalidation request unit is used to send an invalidation request including the login authorization code to the remote storage service, so that the remote storage service rejects the connection verification request containing the login authorization code based on the invalidation request.

[0162] In one embodiment of this application, based on the above-described scheme, the integrity verification unit includes:

[0163] The verification calculation subunit is used to perform verification calculation based on the data status of the business data corresponding to the first account, obtain a verification value, and send the verification value to the remote storage service corresponding to the first account.

[0164] The signature receiving subunit is used to receive the verification signature sent by the remote storage service, wherein the verification signature is obtained by the remote storage service from signing based on the verification value;

[0165] The local storage subunit is used to store the verification value and the verification signature in the local storage of the blockchain node.

[0166] In one embodiment of this application, based on the above-described scheme, the blockchain system further includes a management node; the account management device 800 further includes:

[0167] The verification information acquisition module is used to acquire the login verification information of the first account;

[0168] The login request sending module is used to send a login request including the login verification information to the management node, so that the management node performs login verification based on the login verification information and returns the login verification result.

[0169] The verification result receiving module is used to receive the login verification result, which includes the blockchain registration identifier of the first account, the login authorization code, and the service information of the remote storage service corresponding to the first account.

[0170] The verification request sending module is used to send a connection verification request to the remote storage service based on the service information of the remote storage service. The connection verification request includes the blockchain registration identifier corresponding to the first account and the login authorization code, so as to establish a communication connection with the remote storage service.

[0171] In one embodiment of this application, based on the above-described solution, the account management device 800 further includes:

[0172] The business data acquisition module is used to synchronize data with the management node and obtain the business data corresponding to the first account;

[0173] The validity period check module is used to check the validity period of the login authorization code;

[0174] The business data sending module is used to send the business data to the remote storage service corresponding to the first account according to the login authorization code if the validity period of the login authorization code is met at the current time.

[0175] The renewal request sending module is used to send an authorization code renewal request to the management node if the current time exceeds the validity period of the login authorization code, so that the management node extends the validity period of the login authorization code.

[0176] In one embodiment of this application, based on the above-described solution, the account management device 800 further includes:

[0177] The verification information acquisition module is used to acquire the integrity verification information and obtain the storage data from the remote storage service corresponding to the first account.

[0178] The consistency verification module is used to perform consistency verification on the business data corresponding to the first account based on the integrity verification information.

[0179] The data synchronization module is used to synchronize data with the management node based on the stored data of the remote storage service if the consistency check passes.

[0180] The storage data deletion module is used to delete the storage data in the remote storage service corresponding to the first account and re-obtain the business data corresponding to the first account from the management node if the consistency check fails.

[0181] In one embodiment of this application, an account management device based on a blockchain system is provided. Each blockchain node in the blockchain system corresponds to at least one account, and each account corresponds to a different remote storage service. Each account is used to log in to the blockchain node to establish a communication connection between the blockchain node and the corresponding remote storage service. The method includes:

[0182] The login request receiving module is used to receive the login request sent by the blockchain node and perform login verification according to the login verification information in the login request;

[0183] The login verification request module is used to obtain a login authorization code based on the login verification information if the login verification is successful, and send the login verification result to the blockchain node. The login verification result includes the blockchain registration identifier of the first account, the login authorization code, and the service information of the remote storage service corresponding to the first account.

[0184] The authorization code verification module is used to receive the authorization code verification request sent by the remote storage service. The authorization code verification request is generated by the blockchain node based on the login verification result. The authorization code verification request includes the blockchain registration identifier and the login authorization code.

[0185] The validity verification module is used to verify the validity of the login authorization code based on the blockchain registration identifier, and send the validity verification result to the remote storage service so that the blockchain node and the remote storage service can establish a communication connection.

[0186] In one embodiment of this application, based on the above-described solution, the account management device further includes:

[0187] The registration request receiving module is used to receive account registration requests and generate a blockchain registration identifier based on the account registration requests;

[0188] The registration request sending module is used to send a service registration request to the remote storage service, wherein the service registration request includes the blockchain registration identifier;

[0189] A registration response receiving module is used to receive a service registration response, wherein the service registration response contains service information of the remote storage service corresponding to the blockchain registration identifier. In one embodiment of this application, an account management device based on a blockchain system is provided, characterized in that each blockchain node in the blockchain system corresponds to at least one account, each account corresponds to a different remote storage service, and each account is used to log in to the blockchain node to establish a communication connection between the blockchain node and the corresponding remote storage service; including:

[0190] A connection request receiving module is used to receive a connection verification request sent by the blockchain node, wherein the connection verification request includes the blockchain registration identifier and login authorization code of the first account;

[0191] The authorization code verification request module is used to send an authorization code verification request, the blockchain registration identifier and the login authorization code to the management node according to the connection verification request;

[0192] The verification result receiving module is used to receive the verification result sent by the management node, the verification result including the verification result of the validity of the login authorization code;

[0193] The communication connection establishment module is used to establish a communication connection with the blockchain node if the verification result indicates that the login authorization code is valid.

[0194] In one embodiment of this application, based on the above-described solution, the account management device further includes:

[0195] The registration request receiving module is used to receive the service registration request sent by the management node, wherein the service registration request includes the blockchain registration identifier of the first account;

[0196] A remote storage service generation module is used to respond to the service registration request and generate a remote storage service corresponding to the first account based on the blockchain registration identifier.

[0197] The registration response sending module is used to send a service registration response to the management node. The service registration response contains service information of the remote storage service corresponding to the first account.

[0198] In one embodiment of this application, based on the above-described solution, the account management device further includes:

[0199] An invalidation request receiving module is used to receive invalidation requests, wherein the invalidation request contains the login authorization code of the second account;

[0200] The validity period acquisition module is used to acquire the validity period of the login authorization code of the second account based on the expiration request;

[0201] The expiration record module is used to add the login authorization code of the second account and the validity period to the expiration authorization code record.

[0202] In one embodiment of this application, based on the above scheme, the authorization code verification request module includes:

[0203] A login authorization code lookup unit is used to look up the login authorization code in the connection verification request from the expired authorization code record;

[0204] The connection rejection unit is configured to reject the connection verification request if the expired authorization code record contains the login authorization code in the connection verification request, and the validity period of the login authorization code in the expired authorization code record is currently met.

[0205] The verification request sending unit is used to send an authorization code verification request to the management node if the expired authorization code record does not contain the login authorization code in the connection verification request, or if the validity period in the expired authorization code record is not met at the current time.

[0206] It should be noted that the apparatus provided in the above embodiments and the method provided in the above embodiments belong to the same concept, and the specific way in which each module performs the operation has been described in detail in the method embodiments, and will not be repeated here.

[0207] Figure 9 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown.

[0208] It should be noted that, Figure 9 The computer system 900 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0209] like Figure 9As shown, the computer system 900 includes a Central Processing Unit (CPU) 901, which can perform various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) 902 or programs loaded from Storage Unit 908 into Random Access Memory (RAM) 903. The RAM 903 also stores various programs and data required for system operation. The CPU 901, ROM 902, and RAM 903 are interconnected via a bus 904. An Input / Output (I / O) interface 905 is also connected to the bus 904.

[0210] The following components are connected to I / O interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to I / O interface 905 as needed. Removable media 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 910 as needed so that computer programs read from them can be installed into storage section 908 as needed.

[0211] Specifically, according to embodiments of this application, the processes described in the various method flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 909, and / or installed from removable medium 911. When the computer program is executed by central processing unit (CPU) 901, it performs various functions defined in the system of this application.

[0212] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such transmitted data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0213] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0214] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0215] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, touch terminal, or network device, etc.) to execute the method according to the embodiments of this application.

[0216] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein.

[0217] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. An account management method based on a blockchain system, characterized in that, The blockchain system includes a blockchain node corresponding to at least one account, each account corresponding to a different remote storage service, and a management node; the method includes: Obtain the login verification information for the first account; Send a login request including the login verification information to the management node, so that the management node performs login verification based on the login verification information and returns the login verification result; Receive the login verification result, which includes the blockchain registration identifier of the first account, the login authorization code, and the service information of the remote storage service corresponding to the first account; According to the service information of the remote storage service, a connection verification request is sent to the remote storage service. The connection verification request includes the blockchain registration identifier corresponding to the first account and the login authorization code to establish a communication connection with the remote storage service, so that the remote storage service becomes the storage of the blockchain node. The blockchain node will synchronously store the information in the remote storage service to replace local storage. Based on the logout request triggered by the first account, obtain the login authorization code of the first account; The login authorization code is set to an invalid state, which indicates that the login authorization code cannot be used to establish a communication connection between the blockchain node and the remote storage service. Clear the business data corresponding to the first account cached in the blockchain node and disconnect the communication connection between the blockchain node and the remote storage service.

2. The method according to claim 1, characterized in that, Setting the login authorization code to an invalid state includes: Stop writing operations to the remote storage service corresponding to the first account and obtain the data status of the business data corresponding to the first account in the remote storage service; Based on the data status of the business data, generate and store integrity verification information; Send an invalidation request including the login authorization code to the remote storage service, so that the remote storage service rejects the connection verification request containing the login authorization code based on the invalidation request.

3. The method according to claim 2, characterized in that, The step of generating and storing integrity verification information based on the data status of the business data includes: The verification value is calculated based on the data status of the business data corresponding to the first account, and then the verification value is sent to the remote storage service corresponding to the first account. Receive a verification signature sent by the remote storage service, wherein the verification signature is obtained by the remote storage service from signing based on the verification value; The verification value and the verification signature are stored in the local storage of the blockchain node.

4. The method according to claim 1, characterized in that, After sending a connection verification request to the remote storage service based on the service information of the remote storage service, the method further includes: Synchronize data with the management node to obtain the business data corresponding to the first account; Check the validity period of the login authorization code; If the validity period of the login authorization code is met at the current time, the business data will be sent to the remote storage service corresponding to the first account based on the login authorization code. If the current time exceeds the validity period of the login authorization code, a renewal request for the authorization code is sent to the management node so that the management node can extend the validity period of the login authorization code.

5. The method according to claim 1, characterized in that, After sending a connection verification request to the remote storage service based on the service information of the remote storage service, the method further includes: Obtain integrity verification information and retrieve stored data from the remote storage service corresponding to the first account; Based on the integrity verification information, perform consistency verification on the business data corresponding to the first account; If the consistency check passes, then data synchronization is performed between the management node and the stored data in the remote storage service. If the consistency check fails, the stored data in the remote storage service corresponding to the first account is deleted, and the business data corresponding to the first account is retrieved again from the management node.

6. An account management method based on a blockchain system, characterized in that, The blockchain system has at least one account corresponding to each blockchain node, and each account corresponds to a different remote storage service. Each account is used to log in to the blockchain node to establish a communication connection between the blockchain node and the corresponding remote storage service. The method includes: Receive the login request sent by the blockchain node and perform login verification based on the login verification information in the login request; If the login verification is successful, the login authorization code is obtained based on the login verification information, and the login verification result is sent to the blockchain node. The login verification result includes the blockchain registration identifier of the first account, the login authorization code, and the service information of the remote storage service corresponding to the first account. The system receives an authorization code verification request sent by the remote storage service. The authorization code verification request is generated by the blockchain node based on the login verification result. The authorization code verification request includes the blockchain registration identifier and the login authorization code. The login authorization code is validated based on the blockchain registration identifier, and the validation result is sent to the remote storage service so that the blockchain node establishes a communication connection with the remote storage service. The remote storage service is mounted and connected to the blockchain node to become the storage of the blockchain node. The blockchain node will synchronously receive information and store it in the remote storage service to replace local storage. In the case of a logout request triggered by the first account, the login authorization code is set to an invalid state by the blockchain node and sent to the remote storage service through an invalidation request, indicating that the login authorization code cannot be used to establish a communication connection between the blockchain node and the remote storage service.

7. The method according to claim 6, characterized in that, Before receiving the login request sent by the blockchain node, the method further includes: Receive an account registration request and generate a blockchain registration identifier based on the account registration request; Send a service registration request to the remote storage service, the service registration request including the blockchain registration identifier; Receive a service registration response, which contains service information of the remote storage service corresponding to the blockchain registration identifier.

8. An account management method based on a blockchain system, characterized in that, Each blockchain node in the blockchain system corresponds to at least one account, and each account corresponds to a different remote storage service. Each account is used to log in to the blockchain node to establish a communication connection between the blockchain node and the corresponding remote storage service; including: Receive an invalidation request, the invalidation request containing the login authorization code of the second account; Based on the invalidation request, obtain the validity period of the login authorization code for the second account; Add the login authorization code of the second account and the validity period to the expired authorization code record; Receive a connection verification request sent by the blockchain node, the connection verification request including the blockchain registration identifier and login authorization code of the first account; Based on the connection verification request, an authorization code verification request, the blockchain registration identifier, and the login authorization code are sent to the management node; Receive the verification result sent by the management node, the verification result including the verification result of the validity of the login authorization code; If the verification result indicates that the login authorization code is valid, a communication connection is established with the blockchain node. The remote storage service is mounted and connected to the blockchain node to become the blockchain node's storage. The blockchain node will synchronously store the information it receives in the remote storage service to replace local storage.

9. The method according to claim 8, characterized in that, Before receiving the connection verification request sent by the blockchain node, the method further includes: Receive a service registration request sent by the management node, wherein the service registration request includes the blockchain registration identifier of the first account; In response to the service registration request, a remote storage service corresponding to the first account is generated based on the blockchain registration identifier; A service registration response is sent to the management node, the service registration response containing service information of the remote storage service corresponding to the first account.

10. The method according to claim 8, characterized in that, The step of sending an authorization code verification request to the management node according to the connection verification request includes: Search the invalid authorization code record for the login authorization code in the connection verification request; If the expired authorization code record contains the login authorization code from the connection verification request, and the validity period of the login authorization code in the expired authorization code record is currently met, then the connection verification request is rejected. If the expired authorization code record does not contain the login authorization code in the connection verification request, or if the validity period in the expired authorization code record is not met at the current time, then an authorization code verification request is sent to the management node.

11. An account management device based on a blockchain system, characterized in that, The blockchain system includes a blockchain node corresponding to at least one account, each account corresponding to a different remote storage service, and a management node; the device includes: The verification information acquisition module is used to acquire the login verification information of the first account; The login request sending module is used to send a login request including the login verification information to the management node, so that the management node performs login verification based on the login verification information and returns the login verification result. The verification result receiving module is used to receive the login verification result, which includes the blockchain registration identifier of the first account, the login authorization code, and the service information of the remote storage service corresponding to the first account. The verification request sending module is used to send a connection verification request to the remote storage service based on the service information of the remote storage service. The connection verification request includes the blockchain registration identifier corresponding to the first account and the login authorization code, so as to establish a communication connection with the remote storage service, so that the remote storage service becomes the storage of the blockchain node. The blockchain node will synchronously obtain information and store it in the remote storage service to replace local storage. The logout module is used to obtain the login authorization code of the first account based on the logout request triggered by the first account. The login authorization code is used to establish a communication connection between the blockchain node and the remote storage service corresponding to the first account. The communication connection is established based on the login request and connection verification request sent by the first account when logging into the blockchain node. The remote storage service is mounted to the blockchain node to become the storage of the blockchain node. The blockchain node will synchronously obtain information and store it in the remote storage service to replace local storage. The invalidation setting module is used to set the login authorization code to an invalidation state, which indicates that the login authorization code cannot be used to establish a communication connection between the blockchain node and the remote storage service. The connection disconnection module is used to clear the business data corresponding to the first account cached by the blockchain node and disconnect the communication connection between the blockchain node and the remote storage service.

12. An account management device based on a blockchain system, characterized in that, The blockchain system has at least one account corresponding to each blockchain node, and each account corresponds to a different remote storage service. Each account is used to log in to the blockchain node to establish a communication connection between the blockchain node and the corresponding remote storage service. The device includes: The login request receiving module is used to receive the login request sent by the blockchain node and perform login verification according to the login verification information in the login request; The login verification request module is used to obtain a login authorization code based on the login verification information if the login verification is successful, and send the login verification result to the blockchain node. The login verification result includes the blockchain registration identifier of the first account, the login authorization code, and the service information of the remote storage service corresponding to the first account. The authorization code verification module is used to receive the authorization code verification request sent by the remote storage service. The authorization code verification request is generated by the blockchain node based on the login verification result. The authorization code verification request includes the blockchain registration identifier and the login authorization code. The validity verification module is used to verify the validity of the login authorization code based on the blockchain registration identifier and send the validity verification result to the remote storage service so that the blockchain node and the remote storage service can establish a communication connection. The remote storage service is mounted to the blockchain node to become the storage of the blockchain node. The blockchain node will synchronously receive information and store it in the remote storage service to replace local storage. In the case of a logout request triggered by the first account, the login authorization code is set to an invalid state by the blockchain node and sent to the remote storage service through an invalidation request, indicating that the login authorization code cannot be used to establish a communication connection between the blockchain node and the remote storage service.

13. An account management device based on a blockchain system, characterized in that, Each blockchain node in the blockchain system corresponds to at least one account, and each account corresponds to a different remote storage service. Each account is used to log in to the blockchain node to establish a communication connection between the blockchain node and the corresponding remote storage service; including: An invalidation request receiving module is used to receive invalidation requests, wherein the invalidation request contains the login authorization code of the second account; The validity period acquisition module is used to acquire the validity period of the login authorization code of the second account based on the expiration request; The expiration record module is used to add the login authorization code of the second account and the validity period to the expiration authorization code record; the connection request receiving module is used to receive the connection verification request sent by the blockchain node, the connection verification request including the blockchain registration identifier and login authorization code of the first account; The authorization code verification request module is used to send an authorization code verification request, the blockchain registration identifier and the login authorization code to the management node according to the connection verification request; The verification result receiving module is used to receive the verification result sent by the management node, the verification result including the verification result of the validity of the login authorization code; The communication connection establishment module is used to establish a communication connection with the blockchain node if the verification result indicates that the login authorization code is valid. The remote storage service is mounted to the blockchain node to become the storage of the blockchain node. The blockchain node will synchronously obtain information and store it in the remote storage service to replace local storage.

14. A computer-readable medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the blockchain-based business processing method as described in any one of claims 1 to 10.

15. An electronic device, characterized in that, include: One or more processors; A storage device for storing one or more programs, which, when executed by one or more processors, cause the electronic device to implement the blockchain-based business processing method as described in any one of claims 1 to 10.

16. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium. The processor of the computer device reads and executes the computer instructions from the computer-readable storage medium, causing the computer device to perform the blockchain-based business processing method as described in any one of claims 1 to 10.

Images