An account data processing method and device, a terminal and a storage medium

Abstract

The application is suitable for the field of blockchain technology, and provides an account data processing method and device, a terminal and a storage medium, wherein the method comprises: obtaining an account registration request of a user; in response to the account registration request, performing account registration in an off-chain business system to obtain an account address corresponding to a registered account and account identity information, storing the account address and the account identity information in the local of the off-chain business system, and performing account registration in a blockchain contract based on the account address; wherein the account address and the account identity information associated with the account address are recorded in the blockchain contract after account registration, and the account identity information is used for operation permission verification of the registered account in the off-chain business system and / or the blockchain. The scheme can effectively improve the account maintenance efficiency and scalability of the system and reduce the maintenance cost of the system.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of blockchains, and particularly relates to an account data processing method and device, a terminal and a storage medium. BACKGROUND

[0002] In the field of blockchain applications, important data in a business system is stored in a blockchain to achieve data non-tamperability and ensure data security. Generally, the business system contains accounts of different users, and a set of account systems is maintained off-chain.

[0003] In a blockchain associated with a business system, a traditional data processing model includes a UTXO (Unspent Transaction Output) model of Bitcoin and an account model of Ethereum.

[0004] In the UTXO model, one UTXO represents a certain amount of Bitcoin, multiple UTXOs can be combined, and a single UTXO can be split to make any denomination required for payment. The stateless nature of UTXO ensures that multiple UTXO transactions can be processed concurrently. However, the UTXO model of Bitcoin does not have the concept of an account, so there is no special account address. Due to the stateless nature of UTXO, it cannot implement some complex logic, has poor programmability, and is difficult to convert the account system with the business system off-chain.

[0005] The account model of Ethereum private key is essentially a model that controls all operations of a user account through a private key. The account model of Ethereum private key can overcome the problems in the UTXO model, implement complex logic, quickly and clearly determine responsibilities in case of problems, and better support smart contracts.

[0006] However, the account model of Ethereum private key needs to maintain a set of independent account systems that run synchronously with the blockchain account system, and maintaining two independent account systems is costly. SUMMARY

[0007] The embodiments of the application provide an account data processing method, device, terminal and storage medium, which can connect the on-chain and off-chain account systems, effectively improve the account maintenance efficiency and scalability of the system, and reduce the maintenance cost of the system.

[0008] A first aspect of the embodiments of the application provides an account data processing method, comprising:

[0009] obtaining an account registration request of a user;

[0010] In response to the account registration request, account registration is performed in an off-chain business system to obtain an account address and account identity information corresponding to the registered account;

[0011] The account address and the account identity information are stored locally in the off-chain business system, and account registration is performed in a blockchain contract based on the account address; wherein the account address and the account identity information associated with the account address are recorded in the blockchain contract after account registration, and the account identity information is used to verify the operation permission of the registered account in the off-chain business system and / or the blockchain.

[0012] The second aspect of the embodiment of the present application provides an account data processing device, comprising:

[0013] An acquisition module is configured to acquire an account registration request of a user;

[0014] A registration module is configured to, in response to the account registration request, perform account registration in an off-chain business system to obtain an account address and account identity information corresponding to the registered account, store the account address and the account identity information locally in the off-chain business system, and perform account registration in a blockchain contract based on the account address; wherein the account address and the account identity information associated with the account address are recorded in the blockchain contract after account registration, and the account identity information is used to verify the operation permission of the registered account in the off-chain business system and / or the blockchain.

[0015] The third aspect of the embodiment of the present application provides a terminal, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method according to the first aspect when executing the computer program.

[0016] The fourth aspect of the embodiment of the present application provides a computer readable storage medium, which stores a computer program, wherein the computer program is executed by a processor to implement the steps of the method according to the first aspect.

[0017] The fifth aspect of the present application provides a computer program product, which, when executed on a terminal, causes the terminal to perform the steps of the method according to the first aspect.

[0018] From the above, in the embodiment of the present application, by responding to the account registration request of the user, the account registration is performed in the off-chain business system, the account address and the account identity information corresponding to the registered account are obtained, the account address and the account identity information are stored in the local of the off-chain business system, and the account registration is performed in the blockchain contract based on the account address, so that the account address and the account identity information associated with the account address are recorded in the blockchain contract after the account registration, and the operation permission verification of the registered account in the off-chain business system and / or the blockchain is realized. The process realizes the relationship binding between the on-chain account and the off-chain account information through the associated storage of the account address and the account identity information, and ensures the association between the account generated by the on-chain registration and the account corresponding to the off-chain user, effectively improves the account maintenance efficiency and scalability of the system, and reduces the maintenance cost of the system. BRIEF DESCRIPTION OF DRAWINGS

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0020] Figure 1 is a flow of an account data processing method provided by an embodiment of the present application Figure 1 ;

[0021] Figure 2 is an organization-group-user relationship diagram provided by an embodiment of the present application

[0022] Figure 3 is a flow of an account data processing method provided by an embodiment of the present application Figure 2 ;

[0023] Figure 4 is a structural diagram of an account data processing device provided by an embodiment of the present application

[0024] Figure 5 is a structural diagram of a terminal provided by an embodiment of the present application DETAILED DESCRIPTION

[0025] In the following description, specific details are set forth such as particular system architectures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application can be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

[0026] It should be understood that the term "include" as used in this specification and in the following claims indicates the presence of the described features, integers, steps, operations, elements, and / or components but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0027] It should also be understood that the terms used in the specification and the appended claims are intended to be interpreted broadly and in a manner consistent with the principles of the application, and not necessarily in a narrow or legal sense. As used in this specification and the appended claims, the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise.

[0028] It should also be further understood that the term "and / or" as used in the specification and in the claims, if and when used, means any one of the items, or a combination of any of the items, in the list that it co njoins.

[0029] As used in this specification and in the claims, the term "if" can be interpreted as meaning "when," or "once," or "in response to determining," or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [a described condition or event] is detected" can be interpreted to mean "once it is determined," or "in response to determining," or "once [the described condition or event] is detected," or "in response to detecting [the described condition or event]," depending on the context.

[0030] It should be understood that the sequence of the steps in the embodiments does not mean the order of execution, and the execution order of the processes should be determined according to the functions and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the application.

[0031] In order to illustrate the technical solutions described in the present application, the following will be described by specific embodiments.

[0032] Referring to Figure 1 , Figure 1 is a flow of an account data processing method provided by the embodiments of the present application Figure 1 . As shown in Figure 1 , an account data processing method includes the following steps:

[0033] Step 101, obtaining an account registration request of a user.

[0034] In the embodiments of the present application, the account data processing method is specifically applied to an off-chain business system. The off-chain business system is specifically assembled in a terminal device. The execution subject of the account data processing method can be a terminal device or a processing device (such as a chip, a processor, etc.) in the terminal device.

[0035] The off-chain business system is, for example, a financial transaction system, a settlement system, a bill processing system, etc. The off-chain business system can publish data into the blockchain, realize storage and recording of the data through the blockchain, and ensure the security and non-tamperability of the data.

[0036] The user can trigger account registration, data submission, operation triggering, etc. in the off-chain business system.

[0037] In this step, the account registration request can be directly submitted by the user and triggered to generate. Alternatively, the user can submit information and trigger the generation by the super-privilege account.

[0038] Correspondingly, in one embodiment, the account registration request of the user is obtained, including:

[0039] Registering a super-privilege account in the off-chain business system;

[0040] Obtaining the account registration request triggered by the super-privilege account based on the user operation.

[0041] In the off-chain business system, accounts with different permissions can be set, which can specifically include ordinary-privilege accounts and super-privilege accounts. The super-privilege account has more permissions than the ordinary-privilege account.

[0042] Specifically, the super-privilege account in the off-chain business system as a super administrator can be generated internally.

[0043] Specifically, based on the system self-defined configuration file, an address (Address) capable of proving the uniqueness of the super administrator identity is submitted to a trusted authentication center. The authentication center specifically assigns a key pair (skx, vkx) to the super-privilege account based on the ECC algorithm of the elliptic curve discrete logarithm problem (ECDLP), where skx is the private key and vkx is the public key, thereby generating a super administrator ROOT user.

[0044] After the super-privilege account (ROOT user) is registered, the corresponding account identity information is recorded to the local database, providing a permission verification function for subsequent user system operations. The ROOT user has the highest permission by default, can register the institution information of the off-chain business system to the blockchain network, and perform a series of operations, including registering an ordinary user, obtaining ordinary user information, canceling an ordinary user, updating user information, etc.

[0045] Specifically, in the off-chain, the off-chain account system can be composed of different entities such as users, groups, and institutions, forming the basis of data sharing and trusted storage, and the relationship is as follows Figure 2The ROOT user in the off-chain business system manages each entity in the off-chain account system in terms of user management, group management, and institution management. The ROOT user can register a normal user, unregister a normal user, update user information, verify user rights, and perform other user management operations.

[0046] Specifically, in combination with Figure 2 As shown, the concept of a group can be introduced. A group (Group) is a collection of accounts corresponding to a user. The account corresponding to the user can be added to a specific group. The group has different functions with different levels and different responsibilities under the institution organizational structure. The ROOT administrator can conceptually organize the accounts corresponding to multiple users into groups (Group), such as an operation group, a maintenance group, a model deployment group, and the like, to simplify batch operations on a large number of users.

[0047] The institution is an organizational unit, and the account corresponding to the user and the group can be created in the institution. The concept of the institution can be extended to represent a sub-institution of a hierarchical institution. In the embodiments of the present application, the next level of sub-institution can be registered through the previous level of institution. The institution information is automatically registered in the off-chain business system after being started, and is broadcast in the blockchain network to realize the on-chain recording of the registered information and keep the consistency of the off-chain and on-chain account management systems.

[0048] At step 102, in response to the account registration request, the account is registered in the off-chain business system to obtain an account address and account identity information corresponding to the registered account, and the account address and the account identity information are stored in the off-chain business system locally.

[0049] Specifically, when the account is registered in the off-chain business system, the registration process can be the same as the registration process when the super-privilege account is registered. Specifically, an address (Address) that can prove the identity uniqueness of the current account to be registered is submitted to a trusted authentication center. The authentication center assigns a key pair (skx, vkx) to the registered account based on an ECC algorithm of an elliptic curve discrete logarithm problem (ECDLP), where skx is a private key and vkx is a public key, thereby completing the registration of an account.

[0050] Correspondingly, the step of registering the account in the off-chain business system in response to the account registration request to obtain the account address and the account identity information corresponding to the registered account specifically includes:

[0051] In response to the account registration request, an account address associated with a set operation permission is determined, and an account authentication request carrying the account address is submitted to an authentication center;

[0052] Obtaining a key pair assigned by the authentication center to the registered account based on the account authentication request, to obtain the account identity information including the set operation permission, the key pair, and the account balance corresponding to the account address.

[0053] That is, the registered account corresponds to the set operation permission, the account address, the required key pair for data interaction, the account balance, and other information.

[0054] For example, whether the current registered account can modify the data on the blockchain, or whether the account can upload the unchained data to the blockchain, and so on.

[0055] Step 103, based on the account address, register the account in the blockchain contract.

[0056] After the account is registered, the account address and the account identity information associated with the account address are recorded in the blockchain contract, and the account identity information is used to verify the operation permission of the registered account in the off-chain business system and / or the blockchain.

[0057] After the account registration in the off-chain business system is completed, the account information obtained by the registration needs to be synchronized in the blockchain system, specifically, the account registered in the off-chain business system is synchronized and registered in the blockchain contract. The account generated by the registration in the blockchain contract has the same or corresponding account address as the account generated by the registration in the off-chain business system. The account address is associated with the account identity information for storage, realizing the relationship binding between the on-chain and off-chain account information. The on-chain registered account is associated with the account corresponding to the off-chain user.

[0058] In a specific application, after the user completes the off-chain account registration, the off-chain business system registers in the blockchain contract based on the unique address Address of the user identity. The contract associates the user address Address with the user identity information through a Map data structure, including the user public key vkx, the private key skx, and the account balance. If the on-chain account system needs to verify the user's identity information in the future, the user information saved by the contract can be matched, thereby realizing the binding of the off-chain identity and the on-chain identity.

[0059] In the embodiment of the present application, in response to the account registration request of the user, account registration is performed in the off-chain business system, the account address and the account identity information corresponding to the registered account are obtained, the account address and the account identity information are stored locally in the off-chain business system, and account registration is performed in the blockchain contract based on the account address. It is ensured that the account address and the account identity information associated with the account address are recorded in the blockchain contract after account registration, and the operation permission verification of the registered account in the off-chain business system and / or the blockchain is realized. The process realizes the relationship binding between the on-chain account and the off-chain account information through the associated storage of the account address and the account identity information, and ensures the association between the on-chain registered account and the account corresponding to the off-chain user. The account maintenance efficiency and scalability of the system are effectively improved, and the maintenance cost of the system is reduced.

[0060] The embodiment of the present application also provides different implementation manners of the account data processing method.

[0061] Referring to Figure 3 , Figure 3 is a flow of an account data processing method provided by the embodiment of the present application Figure 2 . As Figure 3 shown, an account data processing method comprises the following steps:

[0062] Step 301, obtaining an account registration request of a user.

[0063] The implementation process of this step is the same as that of step 101 in the foregoing embodiment, and will not be described here again.

[0064] Step 302, in response to the account registration request, performing account registration in the off-chain business system, obtaining an account address and account identity information corresponding to the registered account, and storing the account address and the account identity information locally in the off-chain business system.

[0065] The implementation process of this step is the same as that of step 102 in the foregoing embodiment, and will not be described here again.

[0066] Step 303, performing account registration in the blockchain contract based on the account address.

[0067] Wherein, the account address and the account identity information associated with the account address are recorded in the blockchain contract after the account registration, and the account identity information is used for operation permission verification of the registered account in the off-chain business system and / or the blockchain.

[0068] The implementation process of this step is the same as that of step 103 in the foregoing embodiment, and will not be described here again.

[0069] Further, optionally, after the account registration in the blockchain contract based on the account address, further comprising:

[0070] Step 304, obtaining a data sharing request of the first user in the off-chain business system.

[0071] The data sharing request indicates the data to be shared and the data sharing mode. The data sharing request can realize data sharing between different institutions, groups or users.

[0072] The data sharing mode is, for example, points sharing or authorization sharing.

[0073] In the points sharing mode, the first user can set the required remaining points of other users when obtaining the data to be shared. That is, after the data to be shared of the first user is chained, other users who come to obtain the data to be shared need to ensure that the remaining points in the account reach a certain number, and then the data to be shared can be obtained.

[0074] In the authorization sharing mode, the first user can give a data authorization list when chaining the data to be shared, and only the other users in the data authorization list can obtain the data to be shared.

[0075] The data authorization list can record the account addresses of the authorized users.

[0076] Step 305, in response to the data sharing request, when it is determined that the data to be shared is data to be chained, verifying whether the first user has the data chaining sharing permission based on the account identity information;

[0077] Based on the account address of the first user, the account identity information corresponding to the account address is extracted, and the set operation permission in the account identity information is used to audit and verify whether the first user has the data chaining sharing permission, to determine whether the first user has the permission to publish the data.

[0078] The data to be shared can be data to be chained or data not to be chained.

[0079] For example, in the off-chain business system, a user performs operations such as uploading a file, creating a model, and connecting a database, and the data generated by these operations does not need to be chained. The data generated by the data sharing, multi-party privacy calculation and other operations triggered by the user in the off-chain business system needs to be chained. At this time, it is necessary to jointly verify through the on-chain and off-chain account system to determine whether it can be chained.

[0080] Step 306, when it is determined that the first user has the data chaining sharing permission, publishing the data to be shared to the blockchain according to the data sharing mode.

[0081] After the user permission verification in the off-chain business system is passed, data can be chained, and account permission management can be realized.

[0082] Differently, in one embodiment, after the data sharing request of the first user in the off-chain business system is obtained, the method further includes:

[0083] In response to the data sharing request, when it is determined that the data to be shared is data that does not need to be chained, it is verified whether the first user has a data off-chain sharing permission based on the account identity information.

[0084] When it is determined that the first user has a data off-chain sharing permission, the data to be shared is published to the local of the off-chain business system according to the data sharing mode.

[0085] Here, corresponding to the processing condition when the data to be shared is data that does not need to be chained, the account identity information still needs to be checked to determine whether it has the relevant permission. At this time, only the account system in the off-chain business system needs to be verified, and the on-chain account system does not need to be verified.

[0086] Further, after the data to be shared is published to the blockchain according to the data sharing mode, the method further includes:

[0087] Step 307: Obtain a data application request of a second user.

[0088] The second user can be a user in a target organization, which can be an organization to which the first user belongs or an organization other than the organization to which the first user belongs. The second user is a user different from the first user.

[0089] Step 308: In response to the data application request, when it is determined that the second user corresponds to a registered account in the off-chain business system based on the account address, the data application request is output to the blockchain.

[0090] Based on the account address, it is determined that the second user corresponds to a registered account in the off-chain business system. Specifically, it can be determined whether the account address of the account corresponding to the second user is the account address of the registered account.

[0091] When it is determined that the account address of the account corresponding to the second user is contained in the account address of the registered account stored in the off-chain business system, it can be considered that the second user corresponds to a registered account in the off-chain business system.

[0092] Wherein, since the address Address of the resource publisher (i.e. the first user) and the sharing manner of the resource are recorded in the blockchain contract, after the first user's to-be-shared data is chained, the blockchain will broadcast the resource in the blockchain network. At the same time, other users in the blockchain network also need to apply for the to-be-shared data according to the resource acquisition rules, and the subsequent steps will verify the authority of the application user on the chain.

[0093] Step 309, obtaining the to-be-shared data fed back by the blockchain based on the data application request, and outputting the to-be-shared data to the second user.

[0094] Wherein, the to-be-shared data is sent by the blockchain based on the target account identity information of the second user extracted from the blockchain contract based on the account address of the second user, and the second user meets the data acquisition condition based on the target account identity information.

[0095] In this process, when the user of other institutions applies for the to-be-shared data, after determining that the application user has registered in the on-chain and off-chain account system, the blockchain needs to extract the account identity information associated with the account address of the second user based on the blockchain contract, so as to facilitate the second user's account identity information to determine whether the second user meets the data acquisition condition.

[0096] Wherein, in the optional implementation, the data information of the to-be-shared data is indicated in the data application request. Therefore, it can be known that the data application request is used to apply for the to-be-shared data.

[0097] Correspondingly, obtaining the to-be-shared data fed back by the blockchain based on the data application request comprises:

[0098] When the blockchain determines that the balance of the second user is sufficient or the second user is an authorized user of shared data based on the target account identity information of the second user corresponding to the data application request, the to-be-shared data fed back by the blockchain is obtained.

[0099] In the specific implementation process, if the to-be-shared data is shared in the form of integral sharing, when other users apply for the to-be-shared data, first, it is verified whether the account address of the current application user is registered in the on-chain and off-chain account system. If the verification is passed, the on-chain account system needs to extract the account identity information associated with the account address of the second user from the Map data storage structure of the blockchain contract, judge whether the account balance of the user can meet the remaining integral requirement of the data provider, and output the to-be-shared data to the current application user when the requirement is met.

[0100] Differently, if the to-be-shared data is to be shared in the integral sharing manner, when other users apply for the to-be-shared data, first, it is verified according to the account address of the current application user whether the user is registered in the on-chain and off-chain account system, if the verification is passed, the on-chain account system needs to extract the account identity information stored in association with the account address of the second user from the Map data storage structure of the blockchain contract, and judge whether the user is in the authorized list of the data provider, when the current application user is in the authorized list, the to-be-shared data is output to the user.

[0101] In the embodiment of the application, the account address and the account identity information corresponding to the registered account are obtained by performing account registration in the off-chain business system, the account address and the account identity information are stored in the local of the off-chain business system, and the account registration is performed in the blockchain contract based on the account address, so that the account address and the account identity information associated with the account address are recorded in the blockchain contract after the account registration, and the account permission verification processing in the data chaining and on-chain data request process is realized on this basis. Through the associated storage of the account address and the account identity information, the relationship binding between the on-chain account and the off-chain account information is realized, and on the basis of realizing the association between the account generated by the on-chain registration and the account corresponding to the off-chain user, the effective management of the account permission is ensured, the account maintenance efficiency and the scalability of the system are effectively improved, and the maintenance cost of the system is reduced.

[0102] Referring to Figure 4 , Figure 4 is a structural diagram of an account data processing device provided by an embodiment of the application, only parts related to the embodiments of the application are shown for ease of description.

[0103] The account data processing device 400 includes:

[0104] The account data processing device 400 includes:

[0105] The account data processing device 400 includes:

[0106] The account data processing device 400 includes:

[0107] The account data processing device 400 includes:

[0108] obtaining a data sharing request of a first user in the off-chain business system, the data sharing request indicating to-be-shared data and a data sharing manner;

[0109] in response to the data sharing request, verifying whether the first user has a data on-chain sharing permission based on the account identity information when the to-be-shared data is determined to be on-chain data;

[0110] when it is determined that the first user has the data on-chain sharing permission, publishing the to-be-shared data into the blockchain according to the data sharing manner.

[0111] The apparatus further comprises:

[0112] a data application module, configured to:

[0113] obtain a data application request of a second user;

[0114] in response to the data application request, outputting the data application request to the blockchain when it is determined that the second user corresponds to a registered account in the off-chain business system based on the account address;

[0115] obtaining the to-be-shared data fed back by the blockchain based on the data application request, and outputting the to-be-shared data to the second user;

[0116] The to-be-shared data is sent by the blockchain based on the account address of the second user to extract target account identity information of the second user from the blockchain contract, and determine that the second user meets a data acquisition condition based on the target account identity information.

[0117] The data application module is specifically configured to:

[0118] obtaining the to-be-shared data fed back by the blockchain when it is determined that the second user has sufficient balance or is an authorized user of shared data based on the target account identity information of the second user corresponding to the second user.

[0119] The data sharing module is further configured to:

[0120] in response to the data sharing request, verifying whether the first user has a data off-chain sharing permission based on the account identity information when the to-be-shared data is determined to be off-chain data;

[0121] when it is determined that the first user has the data off-chain sharing permission, publishing the to-be-shared data to a local of the off-chain business system according to the data sharing manner.

[0122] The obtaining module 401 is specifically configured to:

[0123] registering a super-privilege account in the off-chain service system;

[0124] obtaining an account registration request triggered by the super-privilege account based on a user operation.

[0125] The registration module 402 is specifically configured to:

[0126] in response to the account registration request, determining an account address associated with a set operation privilege, and submitting an account authentication request carrying the account address to an authentication center;

[0127] obtaining a key pair allocated by the authentication center for the registered account based on the account authentication request, to obtain the account identity information including the set operation privilege, the key pair, and an account balance corresponding to the account address.

[0128] The account data processing apparatus provided by the embodiments of the present application can implement each process of the embodiments of the account data processing method, and achieve the same technical effects. To avoid repetition, the details are not described here.

[0129] Figure 5 is a structural diagram of a terminal provided by an embodiment of the present application. As shown in the diagram, the terminal 5 of the embodiment includes at least one processor 50 (only one is shown in the figure), a memory 51, and a computer program 52 stored in the memory 51 and executable on the at least one processor 50, wherein the processor 50 implements the steps in any of the above method embodiments when executing the computer program 52. Figure 5

[0130] The terminal 5 can be a desktop computer, a notebook computer, a palm computer, a cloud server, and the like. The terminal 5 can include, but is not limited to, the processor 50 and the memory 51. Those skilled in the art can understand that the terminal 5 can include more or fewer components, or combine certain components, or include different components, for example, the terminal can also include an input / output device, a network access device, a bus, and the like. Figure 5 The terminal 5 is merely an example and does not constitute a limitation on the terminal 5, and can include more or fewer components than those shown in the diagram, or combine certain components, or include different components, for example, the terminal can also include an input / output device, a network access device, a bus, and the like.

[0131] ​The processor 50 can be a central processing unit (CPU), and can also be other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0132] The memory 51 can be an internal storage unit of the terminal 5, such as a hard disk or a memory of the terminal 5. The memory 51 can also be an external storage device of the terminal 5, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. Further, the memory 51 can also include both the internal storage unit and the external storage device of the terminal 5. The memory 51 is used to store the computer program and other programs and data required by the terminal. The memory 51 can also be used to temporarily store data that has been output or is to be output.

[0133] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above functional units and modules is exemplified, and in actual application, the above functions can be completed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to complete all or part of the above described functions. Each functional unit and module in the embodiment can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit, and the integrated unit can be realized in the form of hardware or in the form of software functional unit. In addition, the specific names of each functional unit and module are only for convenient distinction, and do not limit the protection scope of the present application. The specific working process of the units and modules in the system can refer to the corresponding process in the foregoing method embodiments, which will not be described here.

[0134] In the above embodiments, the description of each embodiment has its own emphasis, and the parts not described or recorded in detail in a certain embodiment can refer to the relevant description of other embodiments.

[0135] Those skilled in the art can understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0136] In the embodiments provided by the present application, it should be understood that the disclosed apparatus / terminal and method can be implemented in other ways. For example, the apparatus / terminal embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division, and there can be another division manner in actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or in other forms.

[0137] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, i.e. they can be located in one place, or distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiments.

[0138] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically independently, or two or more units can be integrated into one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0139] The integrated module / unit, if implemented in the form of a software function unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the above-mentioned embodiment methods can also be implemented by a computer program instructing related hardware, and the computer program can be stored in a computer readable storage medium. The computer program can implement the steps of the above-mentioned various method embodiments when executed by a processor. The computer program includes computer program code, which can be in the form of source code, object code, executable files or some intermediate forms. The computer readable medium can include any entity or device, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal and software distribution medium, etc. that can carry the computer program code. It should be noted that the contents included in the computer readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.

[0140] The above-mentioned embodiment methods can also be implemented by a computer program product, which, when running on a terminal, causes the terminal to execute the steps of the above-mentioned various method embodiments.

[0141] The above-mentioned embodiments are only used to illustrate the technical solutions of the present application, rather than limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacements to some technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application.

Claims

1. An account data processing method, characterized by, The method comprises: obtaining an account registration request of a user; in response to the account registration request, performing account registration in an off-chain business system to obtain an account address and account identity information corresponding to the registered account; the off-chain business system is provided with accounts with different permissions; the off-chain business system is used to realize account permission management, and after the user permission verification is passed, the to-be-shared data is published to the blockchain for storage record; the account address and the account identity information are stored in the local of the off-chain business system, and the account registration is performed in the blockchain contract based on the account address; wherein the account address and the account identity information associated with the account address are recorded in the blockchain contract after the account registration, and the account identity information is used for operation permission verification of the registered account in the off-chain business system and / or the blockchain.

2. The method of claim 1, wherein, After the account registration in the blockchain contract based on the account address, the method further comprises: obtaining a data sharing request of a first user in the off-chain business system, the data sharing request indicating to-be-shared data and a data sharing mode; in response to the data sharing request, when it is determined that the to-be-shared data is data that needs to be uploaded to the chain, verifying whether the first user has the data uploading and sharing permission based on the account identity information; when it is determined that the first user has the data uploading and sharing permission, publishing the to-be-shared data to the blockchain according to the data sharing mode.

3. The method of claim 2, wherein, After the to-be-shared data is published to the blockchain according to the data sharing mode, the method further comprises: obtaining a data application request of a second user; in response to the data application request, when it is determined that the second user corresponds to a registered account in the off-chain business system based on the account address, outputting the data application request to the blockchain; obtaining the to-be-shared data fed back by the blockchain based on the data application request, and outputting the to-be-shared data to the second user; wherein the to-be-shared data is target account identity information of the second user extracted from the blockchain contract by the blockchain based on the account address of the second user, and sent after it is determined that the second user meets the data acquisition condition based on the target account identity information.

4. The method of claim 3, wherein, The obtaining of the to-be-shared data fed back by the blockchain based on the data application request comprises: when the second user's balance is sufficient or the second user is an authorized user of shared data, the to-be-shared data fed back by the blockchain is obtained based on the target account identity information of the second user corresponding to the second user based on the data application request.

5. The method of claim 2, wherein, After the data sharing request of the first user in the off-chain business system is obtained, the method further comprises: in response to the data sharing request, when it is determined that the to-be-shared data is data that does not need to be uploaded to the chain, verifying whether the first user has the data off-chain sharing permission based on the account identity information; when it is determined that the first user has the data off-chain sharing permission, publishing the to-be-shared data to the local of the off-chain business system according to the data sharing mode.

6. The method of claim 1, wherein, The account registration request of the user is obtained, including: Registering a super-privilege account in the off-chain business system; Obtain the account registration request triggered by the super-privilege account based on user operation.

7. The method of claim 1, wherein, In response to the account registration request, the account registration is performed in the off-chain business system to obtain the account address and account identity information corresponding to the registered account, including: In response to the account registration request, determine the account address associated with the set operation permission, and submit an account authentication request carrying the account address to the authentication center; Obtain the key pair allocated by the authentication center for the registered account based on the account authentication request to obtain the account identity information including the set operation permission, the key pair and the account balance corresponding to the account address.

8. An account data processing apparatus, characterized by Including: An acquisition module is configured to obtain an account registration request of a user; A registration module is configured to, in response to the account registration request, perform account registration in an off-chain business system to obtain an account address and account identity information corresponding to a registered account, store the account address and the account identity information locally in the off-chain business system, and perform account registration in a blockchain contract based on the account address; wherein the account address and the account identity information associated with the account address are recorded in the blockchain contract after the account registration, and the account identity information is used to verify the operation permission of the registered account in the off-chain business system and / or the blockchain; The off-chain business system is configured to implement account permission management and store and record the to-be-shared data in the blockchain after the user permission verification is passed.

9. A terminal comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, The processor executes the computer program to implement the steps of the method of any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, the computer program comprising instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 9. The computer program is executed by the processor to implement the steps of the method of any one of claims 1 to 7.

Images