Metacosm identity and asset management method and terminal key generation method and device

Abstract

The invention provides a meta-universe identity management method and a meta-universe asset management method, and the method comprises the steps: completing the digital identity registration of a user entering a meta-universe through a specific terminal according to a terminal key and a block chain key of the user; an evidence storage contract is deployed in the block chain network and is used for recording related information of the user; according to the meta-universe asset management method, when a user needs to change a binding terminal, a platform generates a migration code and sends the migration code to the user, the user regenerates a terminal key associated with a new terminal, the migration code and the new terminal key are utilized to complete migration of digital assets, and the platform modifies information in an evidence storage contract. Through the provided identity and asset management method, the data security of interaction of the user in the meta universe is enhanced; in addition, the invention further provides a terminal key generation method, the main key is generated by using the unique block chain key of the user, and the terminal key is generated by using the main key and the terminal identifier, so that the binding relationship between the user identity and the interactive terminal is established.

Description

Technical Field

[0001] The present invention belongs to artificial intelligence technology, and in particular to a metaverse identity and asset management method, a terminal key generation method and device. Background Art

[0002] The Metaverse is a virtual mapping of the real world built on blockchain technology. Real-world natural persons can co-exist in this globally shared virtual space through digital avatars and massive digital people (including clones and fake bodies), and move around, access services, and interact with each other. As the only mapping of citizens, digital citizens control the activities of clones and fake bodies in the Metaverse. In the process of ensuring data transmission security, identity authentication becomes a key issue because it is related to user privacy, security, and trust.

[0003] The current common practice in the industry is to use blockchain digital identity technology, which is unique and easy to verify. However, this technology also has obvious drawbacks. Once the key of a user's digital identity is lost or leaked, it is easy for others to impersonate the user and enter the metaverse to steal their digital assets. Summary of the invention

[0004] Based on this, the present invention aims to provide a metaverse identity and asset management method and a terminal key generation method to improve the data security during the user's access to the metaverse and minimize the possibility of user digital identity leakage and impersonation.

[0005] In a first aspect, the present invention provides a Metaverse identity management method, which is executed on a Metaverse platform and includes an identity registration process and an identity authentication process;

[0006] The identity registration process includes:

[0007] Responding to an identity registration request initiated by a user through a first terminal, the identity registration request including a terminal key and a first terminal identifier, the terminal key being generated according to the user's blockchain key and the first terminal identifier;

[0008] Generate a certificate storage contract based on the terminal key and the first terminal identifier and deploy it to the blockchain network;

[0009] The authentication process includes:

[0010] Responding to a login request initiated by a user through a second terminal, the login request including a terminal key and a second terminal identifier;

[0011] The evidence contract is obtained from the blockchain network according to the terminal key, and the user identity is verified using the evidence contract and the second terminal identifier. When the verification is successful, a login response is generated and sent to the second terminal.

[0012] Furthermore, the identity registration process also includes the following steps before generating the evidence storage contract:

[0013] Verify the legitimacy of the user's identity. If the verification is passed, enter the step of generating a proof contract based on the terminal key and the first terminal identifier and deploying it to the blockchain network.

[0014] Furthermore, the identity registration request also includes a first digital signature signed by the user using the blockchain key to sign the first terminal identifier, and a second digital signature signed by the user using the terminal key to sign the data in the identity registration request, then verifying the legitimacy of the user identity includes:

[0015] Verifying the validity of the first digital signature using the blockchain key;

[0016] The validity of the second digital signature is verified using the terminal key and the first terminal identification.

[0017] Furthermore, the login request also includes a third digital signature of the user using the terminal key for the data in the login request, then requesting a storage contract from the blockchain network according to the terminal key, and verifying the user identity using the storage contract and the second terminal identifier includes:

[0018] Obtain the evidence contract associated with the terminal key from the blockchain network according to the terminal key;

[0019] Obtain the terminal key and the first terminal identifier in the evidence storage contract;

[0020] Verify the consistency of the first terminal identification and the second terminal identification. If the verification is successful, use the terminal key obtained from the evidence storage contract to verify the validity of the third digital signature.

[0021] Furthermore, the above method also includes:

[0022] After the user's identity is authenticated, the session ID carried in the login request is cached;

[0023] When the user initiates a login request again, the consistency between the session identifier in the new login request and the cached session identifier is verified. If the verification fails, the identity authentication process is repeated.

[0024] In a second aspect, the present invention provides a metaverse asset management method, which is executed on a metaverse platform and includes a device unbinding process and an asset migration process;

[0025] The device unbinding process includes:

[0026] Responding to a terminal unbinding request initiated by a user through a terminal, the terminal unbinding request includes the user's blockchain key and a first terminal key, where the first terminal key is generated according to the user's blockchain key and an old terminal identifier;

[0027] Obtaining a proof contract that records both the blockchain key and the first terminal key from the blockchain network, and changing the usage status of the proof contract;

[0028] Generate a migration code and unbinding response and send them to the terminal, recording the association between the migration code and the storage address of the evidence storage contract;

[0029] The asset migration process includes:

[0030] Respond to an asset migration request initiated by a user through a terminal, the asset migration request includes a second terminal key, a new terminal identifier, and a migration code, and the second terminal key is generated based on the user's blockchain key and the new terminal identifier;

[0031] Obtain the evidence contract from the blockchain network according to the association between the migration code and the storage address of the evidence contract, and modify the evidence contract according to the second terminal key and the new terminal identifier;

[0032] Generate a migration response and send it to the terminal.

[0033] Furthermore, obtaining the evidence storage contract that records both the blockchain key and the first terminal key includes:

[0034] Verify the legitimacy of the user's identity. When the verification is passed, enter the step of querying the evidence contract that records both the blockchain key and the terminal key from the blockchain network.

[0035] Furthermore, the terminal unbinding request also includes a fourth digital signature of the user using the blockchain key on the data in the terminal unbinding request, and then verifying the legitimacy of the user identity includes:

[0036] The validity of the fourth digital signature is verified using the blockchain key.

[0037] Furthermore, the asset migration process includes obtaining the evidence contract before:

[0038] Verify the legitimacy of the user's identity. If the verification is passed, proceed to the step of obtaining the evidence contract from the blockchain network based on the association between the migration code and the storage address of the evidence contract.

[0039] Furthermore, the asset migration request also includes a fifth digital signature of the user using the second terminal key to sign the data in the asset migration request. Then, the legitimacy of verifying the user identity during the asset migration process includes:

[0040] The validity of the fifth digital signature is verified using the second terminal key.

[0041] Further, modifying the evidence storage contract according to the second terminal key and the new terminal identifier includes:

[0042] Sign the data in the asset migration request using the platform key to generate a sixth digital signature;

[0043] The sixth digital signature and the asset migration request are encapsulated as a call request and sent to the blockchain network. The call request is used to request to call the modification function of the evidence information of the evidence contract;

[0044] Change the usage status of the evidence storage contract.

[0045] In a third aspect, the present invention provides a metaverse asset management method, which is executed in a user terminal and includes:

[0046] Generate a terminal unbinding request and send it to the Metaverse platform. The terminal unbinding request includes the user's blockchain key and the first terminal key. The first terminal key is generated according to the user's blockchain key and the old terminal identifier;

[0047] Receive the migration code sent by the Metaverse platform and delete the first terminal key;

[0048] Generate a second terminal key according to the blockchain key and the new terminal identifier;

[0049] Generate an asset migration request and send it to the Metaverse platform. The asset migration request includes the second terminal key, the new terminal identifier, and the migration code.

[0050] Receive the migration response sent by the Metaverse platform.

[0051] In a fourth aspect, the present invention provides a terminal key generation method, comprising:

[0052] Read the user's blockchain key and terminal ID;

[0053] Generate a master key based on the blockchain key;

[0054] Generate a terminal key based on the terminal identifier and the master key.

[0055] In a fifth aspect, the present invention provides a Metaverse identity management device, which is deployed on a Metaverse platform and includes an identity registration module and an identity authentication module;

[0056] The identity registration module includes:

[0057] A first request response unit, configured to respond to an identity registration request initiated by a user through a first terminal, the identity registration request including a terminal key and a first terminal identifier, the terminal key being generated according to the user's blockchain key and the first terminal identifier;

[0058] A contract generation unit, used to generate a certificate storage contract according to the terminal key and the first terminal identifier and deploy it to the blockchain network;

[0059] The authentication modules include:

[0060] A second request response unit, configured to respond to a login request initiated by a user through a second terminal, the login request including a terminal key and a second terminal identifier;

[0061] The identity authentication unit is used to obtain the evidence contract from the blockchain network according to the terminal key, use the evidence contract and the second terminal identifier to verify the user's identity, and generate a login response when the verification is successful and send it to the second terminal.

[0062] In a sixth aspect, the present invention provides a Metaverse asset management device, which is deployed on a Metaverse platform and includes a device unbinding module and an asset migration module;

[0063] The device unbinding module includes:

[0064] A third request response unit, configured to respond to a terminal unbinding request initiated by a user through a terminal, wherein the terminal unbinding request includes the user's blockchain key and a first terminal key, and the first terminal key is generated according to the user's blockchain key and an old terminal identifier;

[0065] A contract status changing unit, used to obtain a storage contract that records both a blockchain key and a first terminal key from a blockchain network, and change the usage status of the storage contract;

[0066] The unbinding response generation unit is used to generate a migration code and an unbinding response and send them to the terminal, recording the association between the migration code and the storage address of the evidence storage contract;

[0067] The asset migration module includes:

[0068] A fourth request response unit, configured to respond to an asset migration request initiated by a user through a terminal, wherein the asset migration request includes a second terminal key, a new terminal identifier, and a migration code, and the second terminal key is generated according to the user's blockchain key and the new terminal identifier;

[0069] The contract modification unit obtains the evidence contract from the blockchain network according to the association between the migration code and the storage address of the evidence contract, and modifies the evidence contract according to the second terminal key and the new terminal identifier;

[0070] The migration response generating unit is used to generate a migration response and send it to the terminal.

[0071] In a seventh aspect, the present invention provides a metaverse asset management device, which is deployed in a user terminal and includes:

[0072] A first request generating unit, configured to generate a terminal unbinding request and send it to the Metaverse platform, wherein the terminal unbinding request includes a user's blockchain key and a first terminal key, and the first terminal key is generated according to the user's blockchain key and an old terminal identifier;

[0073] A first data receiving unit, configured to receive a migration code sent by the Metaverse platform and delete a first terminal key;

[0074] A key generation unit, generating a second terminal key according to the blockchain key and the new terminal identifier;

[0075] A second request generating unit, configured to generate an asset migration request and send it to the Metaverse platform, wherein the asset migration request includes a second terminal key, a new terminal identifier, and a migration code;

[0076] The second data receiving unit receives a migration response sent by the Metaverse platform.

[0077] In an eighth aspect, the present invention provides a terminal key generation device, comprising:

[0078] Data reading module, used to read the user's blockchain key and terminal identification;

[0079] A master key generation module, used to generate a master key based on a blockchain key;

[0080] The terminal key generation module is used to generate a terminal key according to the terminal identification and the master key.

[0081] The present invention also provides an electronic device, comprising a memory and a processor;

[0082] The memory is used to store programs;

[0083] The processor is used to execute the program to implement the various steps of the Metaverse identity management method provided in the first aspect, or the various steps of the Metaverse asset management method provided in the second aspect and / or the third aspect, or the various steps of the device key generation method provided in the fourth aspect.

[0084] The present invention provides a readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the computer program implements the various steps of the Metaverse identity management method provided in the first aspect, or the various steps of the Metaverse asset management method provided in the second aspect and / or the third aspect, or the various steps of the device key generation method provided in the fourth aspect.

[0085] It can be seen from the above technical solutions that the present invention has the following beneficial effects:

[0086] The present invention provides a metaverse identity management method and a metaverse asset management method, wherein the metaverse identity management method completes the digital identity registration of the user entering the metaverse through a specific terminal according to the user's terminal key and blockchain key, and deploys a storage contract in the blockchain network to record the relevant information of the user, thereby establishing a binding relationship between the user terminal and the digital identity, so as to avoid the user using other terminals to log in to the same identity; in the provided metaverse asset management method, when the user requests to change the device bound to the digital identity, the platform generates a migration code and sends it to the user, the user regenerates the terminal key associated with the new terminal, uses the migration code and the new terminal key to complete the migration of the digital asset, and the platform modifies the information in the storage contract, and enhances the data security of the user's interaction in the metaverse through the provided identity and asset management method; in addition, the present invention also provides a terminal key generation method, which generates a master key with the user's unique blockchain key on the blockchain, and then generates a terminal key for the terminal using the master key and the terminal identifier, thereby establishing a binding relationship between the user identity and the interactive terminal, and when the user identity needs to change the device bound, the user's blockchain key is used to perform identity authentication to complete the change of binding, so as to improve the security of the user's activities in the metaverse. BRIEF DESCRIPTION OF THE DRAWINGS

[0087] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0088] Figure 1 A schematic diagram of the architecture of the interaction among a terminal, a blockchain network and a metaverse platform provided for one embodiment of the present application;

[0089] Figure 2 A flowchart of an implementation of a Metaverse identity management method executed on a Metaverse platform provided in one embodiment of the present application;

[0090] Figure 3 A flowchart of an implementation of a Metaverse asset management method executed on a Metaverse platform provided for one embodiment of the present application;

[0091] Figure 4 A flowchart of an implementation method of a metaverse asset management method executed on a user terminal provided in one embodiment of the present application;

[0092] Figure 5 A flowchart of a method for generating a terminal key according to an embodiment of the present application;

[0093] Figure 6A schematic diagram of the structure of a Metaverse identity management device deployed on a Metaverse platform provided for one embodiment of the present application;

[0094] Figure 7 A schematic diagram of the structure of a Metaverse asset management device deployed on a Metaverse platform provided for one embodiment of the present application;

[0095] Figure 8 A schematic diagram of the structure of a Metaverse asset management device deployed on a user terminal provided in one embodiment of the present application;

[0096] Fig. 9 A schematic diagram of the structure of a terminal key generation device provided in one embodiment of the present application;

[0097] Fig.10 This is a diagram of the electronic device architecture provided in an embodiment of the present application. DETAILED DESCRIPTION

[0098] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0099] Digital identity is a collection of attribute information that can uniquely identify a subject in digital form. In each digital space, users enter with different digital identities, are identified and trusted, and describe their own characteristics through unique identity attributes.

[0100] Existing digital identities are mainly divided into two systems: dedicated identity and universal identity. Dedicated identity means that application providers issue dedicated digital identities to their users, and the identities are only used within the application. Users need to register digital identities in multiple places, log in frequently, remember different usernames and passwords, and digital identity information is stored in multiple application systems, increasing the risk of identity information being leaked and abused. Universal identity means that digital identities are issued by a third party outside the application, and users can use a universal digital identity in multiple applications at the same time, which to a certain extent solves the problems of the dedicated system.

[0101] The metaverse is a virtual space parallel to the real world, in which users can immersively experience social, economic, cultural and other activities and create value. Currently, various metaverse applications are developing independently. User identities in the metaverse are diverse and fragmented, relatively independent, and unable to trust and communicate with each other. Decentralized digital identity has become a research hotspot, but it has high requirements for user private key management. Loss of private keys can easily lead to loss of digital assets and information leakage. The combined use of multiple identity authentication technologies in the metaverse has become a trend.

[0102] In order to solve the above technical problems, the present invention provides an identity and asset management method through the following embodiments, which uses the user's unique blockchain key to generate a terminal key bound to the terminal, and uses the terminal identification and terminal key to log in to the Metaverse platform, as well as complete operations such as device rebinding and asset migration.

[0103] See also Figure 1 In each embodiment provided by the present invention, the user 10 can interact with the blockchain network 30 directly through the terminal 20. At this time, the terminal 20 can be regarded as a node deployed on the blockchain network 30, or a node independent of the blockchain network 30; the user 10 can also directly enter the metaverse through the terminal 20 to carry out various activities, and can also indirectly interact with the blockchain network 20 through the metaverse platform 40.

[0104] In each embodiment provided by the present invention, the blockchain network 30 and the metaverse platform 40 are two independent systems. The blockchain network 30 or metaverse platform 40 mentioned can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, as well as big data and artificial intelligence platforms.

[0105] The blockchain network 30 and the Metaverse platform 40 can interact and authorize each other through the digital certificate CA. One Metaverse platform can interact with multiple blockchain networks. Similarly, one blockchain network can interact with multiple Metaverse platforms.

[0106] User 10 interacts with blockchain network 30 or metaverse platform 40 through terminal 20. Such terminal 20 includes smart terminals with data processing functions such as smart phones, tablet computers, laptops, desktop computers, wearable devices, smart homes, head-mounted devices, etc.

[0107] See also Figure 2An embodiment of the present application introduces a Metaverse identity management method from the perspective of the Metaverse platform, with the Metaverse platform as the execution end, including an identity registration process and an identity authentication process.

[0108] The identity registration process includes the following steps:

[0109] Step S210. Respond to an identity registration request initiated by the user through the first terminal, where the identity registration request includes a terminal key and a first terminal identifier, and the terminal key is generated based on the user's blockchain key and the first terminal identifier.

[0110] In this step, the user initiates an identity registration request to the Metaverse platform through the first terminal, and the identity registration request includes a terminal key and a first terminal identifier. The terminal key is generated based on the user's blockchain key and the first terminal identifier. The blockchain key and the terminal key can be generated in advance by the user locally at the terminal before requesting identity registration. The blockchain key is mainly used to represent the user's blockchain identity, which is unique and cannot be tampered with. Its main interaction scenario is the interaction between the user and the blockchain network, and it is also the binding object of the blockchain digital asset; the terminal key is mainly used to represent the user's business identity in the Metaverse, and its main interaction scenario is the interaction between the user and the Metaverse platform through the terminal, which is the user's identity proof in the Metaverse.

[0111] Step S220. Generate a proof contract based on the terminal key and the first terminal identifier and deploy it to the blockchain network.

[0112] In this step, the Metaverse platform stores the terminal key and the first terminal identifier provided by the user on the chain. Specifically, it can be manifested as deploying a storage contract on the blockchain network, which records the user identity and the relevant parameters and contract status of the terminal. The Metaverse platform can change the contract status according to the interaction with the user. For example, when the contract status is "normal", it means that the information recorded in the contract is valid. When the contract status changes to "disabled", it means that the information recorded in the contract is invalid. In this way, the relevant information of the user and the terminal is bound and mapped through the smart contract.

[0113] The identity verification process includes the following steps:

[0114] Step S230: Respond to a login request initiated by the user through the second terminal, where the login request includes a terminal key and a second terminal identifier.

[0115] In this step, when the user initiates a login request through the terminal, the terminal key and terminal identification of the terminal need to be carried in the request data packet. The Metaverse platform then verifies the legitimacy of the user's identity based on these two parameters.

[0116] Step S240. Obtain the evidence contract from the blockchain network according to the terminal key, use the evidence contract and the second terminal identifier to verify the user identity, and generate a login response when the verification is successful and send it to the second terminal.

[0117] In this step, the Metaverse platform does not store the user's terminal key itself, but stores the index relationship between the terminal key and the storage address of the evidence contract. Therefore, the associated evidence contract can be queried based on the terminal key provided by the user, and the associated terminal identifier and other parameters can be obtained from the contract. The terminal identifier and other parameters are compared with the terminal identifier currently provided by the user to see if they are the same terminal. If the verification is successful, it means that the user is the exclusive owner of the terminal, and a login response is returned to the user terminal.

[0118] It is understandable that since the terminal key is associated with the terminal identifier used by the user, the user can generate corresponding terminal keys on different terminals for logging into the Metaverse platform, that is, the user can have multiple "trusted devices" to enter the Metaverse. After completing the identity registration process, when the user uses the same terminal to log in to the Metaverse, the terminal can simplify the identity authentication process. When logging in with a new terminal, a new terminal key needs to be generated or the terminal needs to be rebound to prevent others from impersonating the user to log in to the user's Metaverse account, resulting in data leakage or loss of digital assets.

[0119] In a further embodiment, the identity registration process further includes the following steps before generating the evidence storage contract:

[0120] Verify the legitimacy of the user's identity. If the verification is passed, enter the step of generating a proof contract based on the terminal key and the first terminal identifier and deploying it to the blockchain network.

[0121] Specifically, the identity registration request also includes a first digital signature signed by the user using the blockchain key to sign the first terminal identification, and a second digital signature signed by the user using the terminal key to sign the data in the identity registration request. After the Metaverse platform receives the user's identity registration request, it uses the terminal key and the blockchain key to verify the validity of the first digital signature, and uses the terminal key and the first terminal identification to verify the validity of the second digital signature.

[0122] According to the conventional key generation algorithm and signature verification algorithm, the public key in the key pair is made public and the private key is kept by the holder. When data is interacted, the public key is used for encryption and signature verification, and the private key is used for decryption and signing. This mechanism is also applied to the various embodiments of the present invention.

[0123] Exemplarily, the identity registration request specifically includes the user's blockchain public key Q1, terminal public key Q2, terminal identification ID1, digital signature S1 of the blockchain private key on the terminal identification, auxiliary verification parameter R1 of the digital signature S1, hash value H1 calculated for the entire data packet of the identity registration request, and digital signature S2 of the terminal private key on the hash value H1. After receiving the identity registration request, the Metaverse platform verifies the validity of the digital signature S1 based on the blockchain public key Q1 and parameter R1. After the verification is passed, the validity of the digital signature S2 is verified based on the terminal public key Q2 and terminal identification ID1, and the hash value H1' is calculated for the data in the identity registration request. The hash values ​​H1 and H1' are compared to see if they are the same. If they are the same, it means that the information has not been tampered with. After the verification is passed, the evidence storage contract is deployed, and the contract records the user's blockchain public key Q1, terminal public key Q2, and terminal identification ID1.

[0124] In a further embodiment, the login request further includes a third digital signature of the user using the terminal key on the data in the login request, then requesting a storage contract from the blockchain network according to the terminal key, and verifying the user identity using the storage contract and the second terminal identifier includes the following steps:

[0125] Obtain the evidence contract associated with the terminal key from the blockchain network according to the terminal key;

[0126] Obtain the terminal key and the first terminal identifier in the evidence storage contract;

[0127] Verify the consistency of the first terminal identification and the second terminal identification. If the verification is successful, use the terminal key obtained from the evidence storage contract to verify the validity of the third digital signature.

[0128] Exemplarily, the login request includes the terminal identification ID2 of the terminal currently used by the user, the terminal public key Q2, the hash value H2 calculated for the entire data packet of the login request, and the digital signature S3 of the terminal private key on the hash value H2. After receiving the login request, the Metaverse platform first calculates the hash value H2' for the data in the login request, and compares whether the hash values ​​H2 and H2' are consistent. If they are inconsistent, the login fails. If they are consistent, the blockchain network is requested to obtain the evidence contract associated with the terminal public key Q2, and the recorded terminal identification ID1 is obtained in the evidence contract. The terminal identification ID1 and ID2 are compared for consistency. If they are inconsistent, the login fails. If they are consistent, the terminal public key Q2 is used to verify the validity of the digital signature S3, and a login response is returned to the user.

[0129] In some embodiments, after the user logs in successfully, the platform caches the session identifier carried in the login request. Usually, the session identifier is in the data header of the request data packet. When the user logs in again using the same terminal, the consistency of the session identifier in the new login request and the cached session identifier is verified. If the verification fails, the identity authentication process is repeated.

[0130] In a further embodiment, a cache time of the session identifier may also be set. When the user initiates a session beyond the cache time, the identity authentication process needs to be repeated even for the same terminal.

[0131] In some embodiments, when a user generates a blockchain key and a terminal key locally on a terminal, the user does not need to interact with the blockchain network or the Metaverse platform, but instead relies on the algorithm parameters of the SDK.

[0132] See also Figure 3 An embodiment of the present application introduces a Metaverse asset management method from the perspective of the Metaverse platform, with the Metaverse platform as the execution end, including a device unbinding process and an asset migration process.

[0133] The device unbinding process includes the following steps:

[0134] Step S310. Respond to a terminal unbinding request initiated by the user through the terminal, where the terminal unbinding request includes the user's blockchain key and a first terminal key, and the first terminal key is generated based on the user's blockchain key and the old terminal identifier.

[0135] In this step, the user initiates a terminal rebinding request to the Metaverse platform through the terminal, which includes a blockchain key and a first terminal key. The first terminal key is generated based on the user's blockchain key and the old terminal identifier. Terminal rebinding means that the user no longer uses the old terminal as a trusted device for entering the Metaverse. After the rebinding, the old terminal cannot be used to log in to the user's digital identity registered on the Metaverse platform.

[0136] Step S320. Obtain a proof contract that records both the blockchain key and the first terminal key from the blockchain network, and change the usage status of the proof contract.

[0137] In this step, since the evidence storage contract will record the relevant parameters of the terminal, when the platform confirms the user's request, it will change the contract status to "disabled", and the user will no longer be able to log in using the original terminal key.

[0138] Step S330. Generate a migration code and unbinding response and send them to the terminal, recording the association between the migration code and the storage address of the evidence storage contract.

[0139] In this step, the platform returns the migration code to the terminal, and the terminal can delete the terminal key information stored locally, but the user's blockchain key and migration code cannot be deleted, so that digital assets can be migrated after the terminal is changed.

[0140] The asset migration process includes the following steps:

[0141] Step S340. Respond to the asset migration request initiated by the user through the terminal, the asset migration request includes the second terminal key, the new terminal identifier and the migration code, and the second terminal key is generated according to the user's blockchain key and the new terminal identifier.

[0142] Step S350. Obtain the evidence contract from the blockchain network according to the association between the migration code and the storage address of the evidence contract, and modify the evidence contract according to the second terminal key and the new terminal identifier.

[0143] In this step, the Metaverse platform does not store the migration code itself, but stores the index relationship between the migration code and the storage address of the evidence contract. Therefore, the associated evidence contract can be queried based on the migration code provided by the user, and the original value in the evidence contract can be modified based on the new terminal identifier and new terminal key provided by the user, and the contract status can be changed to "normal". The user can then use the new terminal identifier and new terminal key to log in to the new terminal.

[0144] Step S360: Generate a migration response and send it to the terminal.

[0145] In a further embodiment, before the platform requests the evidence contract, it is also necessary to verify the legitimacy of the user's identity. When the verification is passed, it enters the step of querying the evidence contract that records both the blockchain key and the terminal key from the blockchain network.

[0146] Specifically, the terminal unbinding request also includes a fourth digital signature of the user using the blockchain key on the data in the terminal unbinding request. After the Metaverse platform receives the user's terminal rebinding request, it uses the blockchain key to verify the validity of the fourth digital signature.

[0147] Exemplarily, the terminal rebinding request specifically includes the user's blockchain public key Q1, the old terminal public key Q3, the hash value H3 calculated for the entire data packet of the terminal rebinding request, the digital signature S4 of the blockchain private key on the hash value H3, and the auxiliary verification parameter R2 of the digital signature S4. After receiving the terminal rebinding request, the Metaverse platform uses the blockchain public key Q1 and parameter R2 to verify the validity of the digital signature S4, and calculates the hash value H3' for the data in the request, and compares whether the hash values ​​H3 and H3' are consistent. If they are inconsistent, the request is rejected. If they are consistent, the blockchain network is requested to record the evidence contract that records both the blockchain public key Q1 and the terminal public key Q3, and the contract status is changed to "disabled". The user can no longer log in using the terminal public key Q3. The platform also generates a migration code M and returns it to the terminal.

[0148] In a further embodiment, after receiving the user's asset migration request, the platform also needs to verify the legitimacy of the user's identity. When the verification is passed, it enters the step of obtaining the evidence contract from the blockchain network based on the association between the migration code and the storage address of the evidence contract.

[0149] Specifically, the asset migration request also includes a fifth digital signature that the user signs the data in the asset migration request using the second terminal key. After receiving the user's asset migration request, the Metaverse platform uses the second terminal key to verify the validity of the fifth digital signature.

[0150] Exemplarily, an asset migration request includes the user's blockchain public key Q1, the new terminal public key Q4, the migration code M, the digital signature S5 of the blockchain private key to M, the auxiliary verification parameter R3 of the digital signature S5, the new terminal identification ID3, the hash value H4 calculated for the entire data packet of the asset migration request, and the digital signature S6 of the new terminal private key to the hash value H4. After receiving the asset migration request, the Metaverse platform verifies the validity of the digital signature S5 based on the blockchain public key Q1 and the parameter R3. After the verification is passed, the Metaverse platform requests the evidence contract from the blockchain network based on the association between the migration code M and the storage address of the evidence contract, uses the data in the asset migration request to overwrite the terminal public key, terminal identification and other parameter fields in the evidence contract, and changes the contract status to "normal". The user can subsequently use the new terminal identification and the new terminal key to log in to the new terminal.

[0151] In a further embodiment, a storage contract provides a storage information modification function. Before calling the function, it is necessary to verify the permissions of the user terminal and the Metaverse platform. Therefore, when the platform verifies the user's asset migration request, the platform will use the platform key to sign the data in the asset migration request, generate a sixth digital signature, and encapsulate the digital signature and the asset migration request as a call request and send it to the blockchain network. The verification function in the storage contract verifies the validity of the digital signature generated by the platform and the digital signature generated by the user using the blockchain private key, and verifies that the actual performance of modifying the storage contract information through the platform is to call the storage information modification function.

[0152] See also Figure 4 An embodiment of the present application introduces a metaverse asset management method from the perspective of a user terminal, with the user terminal as the execution end, including the following steps:

[0153] Step S410. Generate a terminal unbinding request and send it to the Metaverse platform. The terminal unbinding request includes the user's blockchain key and the first terminal key. The first terminal key is generated based on the user's blockchain key and the old terminal identifier.

[0154] Specifically, a terminal unbinding request is a request initiated by a user when he needs to replace the terminal device for logging into the Metaverse. For example, the user changes a mobile terminal such as a mobile phone or laptop computer and needs to authorize login to the new terminal and cancel the login authorization of the old mobile terminal.

[0155] The user generates a blockchain key and a terminal key locally on the terminal. The blockchain key is the user's unique identity in the blockchain network. The public key is broadcast throughout the network, and the private key can be stored on the terminal or a mobile storage device according to the user's choice. The terminal key is generated by the terminal based on the private key in the blockchain key and the terminal identity. Similarly, the public key of the terminal key is broadcast throughout the network, and the private key can be stored on the terminal or a mobile storage device according to the user's choice.

[0156] Step S420: Receive the migration code sent by the Metaverse platform and delete the first terminal key.

[0157] Specifically, after receiving the migration code, the terminal can delete the terminal key information corresponding to the old terminal stored locally, but the blockchain key and migration code are not deleted.

[0158] Step S430. Generate a second terminal key based on the blockchain key and the new terminal identifier.

[0159] Specifically, the user can import the blockchain key and migration code into the new terminal through a mobile storage device and regenerate the terminal key of the new terminal. The process of generating the key is similar to the terminal key generation process mentioned above and will not be repeated here.

[0160] Step S440. Generate an asset migration request and send it to the Metaverse platform. The asset migration request includes the second terminal key, the new terminal identifier and the migration code.

[0161] Specifically, the digital assets of users in the metaverse usually include NFT assets, Token assets, virtual items, virtual services, etc. generated by the blockchain network system. In addition to recording the user's identity information, such as blockchain public key, terminal public key, etc., and terminal identification, the evidence contract also records the digital asset information associated with the blockchain key. When the user initiates a terminal rebinding, it actually includes two steps: unbinding the old terminal and binding the new terminal. The contract needs to delete the original terminal public key, terminal identification and other information associated with the terminal, and record the terminal public key and terminal identification of the new terminal. Therefore, asset migration is actually manifested as modifying the terminal-related information of the evidence contract.

[0162] Step S450: Receive a migration response sent by the Metaverse platform.

[0163] The above embodiments introduce the Metaverse identity and asset management method provided by the present invention. The digital identity registration of the user entering the Metaverse through a specific terminal is completed according to the user's terminal key and blockchain key, and a storage contract is deployed in the blockchain network to record the user's relevant information, thereby establishing a binding relationship between the user terminal and the digital identity to avoid the user using other terminals to log in to the same identity. When the user requests to change the device bound to the digital identity, the platform generates a migration code and sends it to the user. The user regenerates the terminal key associated with the new terminal, and uses the migration code and the new terminal key to complete the migration of digital assets. The platform modifies the information in the storage contract, and enhances the data security of users interacting in the Metaverse through the provided identity and asset management method.

[0164] See also Figure 5 An embodiment of the present application further provides a terminal key generation method, comprising the following steps:

[0165] Step S510. Read the user's blockchain key and terminal identification.

[0166] Step S520. Generate a master key based on the blockchain key.

[0167] Step S530: Generate a terminal key according to the terminal identification and the master key.

[0168] Common algorithms for generating a master key and then generating a user key include the IBE algorithm, KDC encryption mode, PKI, etc. Using the master key to generate a user key can achieve efficient key management and distribution, ensuring security and flexibility.

[0169] Specifically in the embodiments of the present invention, the user's blockchain private key can be used to generate a master key, and then the terminal key pair can be generated based on the terminal identification and the master key. MAC address, serial number, IMEI, UUID, IP address, SIM card number, device identifier and other information can be used as the terminal identification.

[0170] Exemplarily, the SM2 algorithm is used to generate the user's blockchain key pair, the terminal's MAC address is used as the terminal identifier, and the SM9 algorithm is used to calculate the terminal's key pair.

[0171] Specifically, in the SM9 algorithm, a random number s needs to be selected as the master private key. The user's blockchain private key can be used as the value of s, and then the master public key is calculated. , It is a generator on the elliptic curve, and then uses the random number generator to generate a random number x to calculate the terminal public key , calculate the terminal private key based on the terminal's MAC address , Represents the hash function, the terminal public key Broadcast to the entire network.

[0172] The above embodiment introduces the terminal key generation method provided by the present invention, which generates a master key using the user's unique blockchain key on the blockchain, and then generates a terminal key for the terminal using the master key and the terminal identifier, thereby establishing a binding relationship between the user identity and the interactive terminal. When the user identity needs to be re-bound to a device, the identity is authenticated through the user's blockchain key to complete the re-binding, thereby improving the security of the user's activities in the metaverse.

[0173] The following is a further introduction to the terminal key generation provided by this application and the metaverse identity and asset management method based on it through actual application scenarios.

[0174] An embodiment of the present application provides a series of processes for a user to interact with the Metaverse platform through a terminal, which will describe the blockchain key pair generation, terminal key pair generation, identity registration and login, terminal rebinding and asset migration.

[0175] (1) Blockchain key pair generation

[0176] The chain key pair is generated locally by the terminal, which mainly uses an asymmetric encryption algorithm to calculate a pair of key strings, including a public key and a private key. They are mathematically related and can prove to be paired with each other, but cannot be deduced from each other, that is, it is impossible to deduce the specific value of the other key by obtaining one of the keys.

[0177] In this embodiment, the SM2 algorithm is used to generate the user's blockchain key pair, including the blockchain public key and private key , and generate a temporary point Used for signature verification, public key Broadcast to the entire network, private key Save the file locally on the terminal.

[0178] (2) Terminal key pair generation

[0179] The terminal key pair is calculated using the SM9 algorithm using the terminal's private key based on the blockchain key and the terminal's MAC address.

[0180] Based on the SM9 algorithm, in this embodiment, the private key As the master private key in the SM9 algorithm, calculate the master public key , It is the generator on the elliptic curve, the master public key It is used for signature verification in the whole network, and a random number generator is used to generate a random number x to calculate the terminal public key. , calculate the terminal private key based on the terminal's MAC address , Represents the hash function, the terminal public key Broadcast to the entire network.

[0181] (3) Identity registration and login

[0182] User 10 sends an identity registration request to Metaverse platform 40 via terminal 20. The request packet carries the user’s blockchain public key. , terminal public key , Use private key The result of signing the terminal MAC address S1, temporary point , terminal identification ID1, master public key , request action field, other business fields, the hash calculation value H1 of the string formatted with JSON for the aforementioned data in the request package, and the digital signature S2 of the hash value H1 by the private key d2.

[0183] After receiving the identity registration request, the Metaverse platform 40 uses the public key and temporary points Verify the digital signature S1 to ensure that the public key Q1 and its private key are indeed owned by the current user. After verification, use the terminal identification ID1 and public key and the master public key The digital signature S2 is verified, and the hash value H1' is calculated using the information in the identity registration request package. The hash values ​​H1 and H1' are compared for consistency. If they are consistent, it means that the data has not been tampered with.

[0184] After verification, the platform 40 creates a certificate contract to record the user's blockchain public key , terminal public key , terminal identification ID1, master public key Four parameters are used to deploy the evidence storage contract to the specified node on the blockchain network 30.

[0185] User 10 can initiate a login request to Metaverse platform 40 through terminal 20, and the login request packet carries the currently used terminal identification ID2 and terminal public key. , request action field, hash calculation value H2 of the string formatted in JSON for the aforementioned data in the login request package, and digital signature S3 of the hash value H2 by the terminal private key d2.

[0186] After receiving the login request, the Metaverse platform 40 uses the information in the login request packet to calculate the hash value H2' and compares whether the hash values ​​H2 and H2' are consistent. If they are inconsistent, the login fails. If they are consistent, the blockchain network 30 is requested to obtain the evidence contract associated with the terminal public key Qx, and the terminal public key is obtained from the evidence contract. , terminal identification ID1, master public key , compare the terminal identification ID1 and ID2 to see if they are consistent. If they are inconsistent, the login fails. If they are consistent, the terminal public key Q2 and the master public key are used. The digital signature S3 is verified. If it is valid, it means that the user is the holder of the terminal key associated with the public key Q2. If it is invalid, it means that the user is not the holder. A login response is returned to the user.

[0187] It is understandable that the terminal public key Qx carried by user 10 in the login request may not be the terminal public key Q2 stored in the evidence contract. The platform uses the terminal public key obtained from the evidence contract to verify the digital signature S3, and the private key is held secretly by the user. When the user is impersonated to log in, the platform will not pass the verification of the digital signature S3 because the real private key cannot be used to sign.

[0188] After user 10 successfully logs in, the Metaverse platform 40 caches the sessionid and terminal public key Q2 of this request session. When the user uses the same device to log in again during the cache validity period, he only needs to carry the same sessionid and does not need to log in again.

[0189] (4) Terminal rebinding and asset migration

[0190] User 10 sends a terminal unbinding request to the Metaverse platform 40 through the terminal. For the convenience of representation, the terminal public key and private key of the old terminal are respectively recorded as Q3 and d3, and the terminal public key and private key of the new terminal are respectively recorded as Q4 and d4. The terminal unbinding request package carries the user's blockchain public key. , the old terminal public key Q3, the request action field, the hash calculation value H3 of the string formatted with JSON for the aforementioned data in the request package, the digital signature S4 of the blockchain private key d1 on the hash value H3, and the temporary point R1.

[0191] After receiving the terminal rebinding request from user 10, the Metaverse platform 40 uses the blockchain public key The digital signature S4 is verified with parameter R1, and the hash value H3' is calculated for the data in the request. The hash values ​​H3 and H3' are compared for consistency. If they are inconsistent, the request is rejected. If they are consistent, a request is made to the blockchain network for a notarization contract that records both the blockchain public key Q1 and the terminal public key Q3. The contract status is changed to "disabled", and users can no longer log in using the terminal public key Q3. The platform also generates a migration code M and returns it to the terminal.

[0192] User 10 can import the blockchain key pair and migration code M into the new terminal through a mobile storage device, repeat the terminal key pair generation process of the aforementioned step (2) to generate a terminal key pair for the new terminal, and generate a new master key Pn accordingly.

[0193] User 10 sends an asset migration request to the Metaverse platform 40. The request package includes the user's blockchain public key Q1, the new terminal public key Q4, the migration code M, the digital signature S5 of the private key d1 on M, the temporary point R1, the new terminal identification ID3, the request action field, the new terminal identification ID3, the master key Pn, the string hash calculation value H4 of the aforementioned data in the request package in JSON format, and the digital signature S6 of the new terminal private key d4 on the hash value H4.

[0194] After receiving the asset migration request, the Metaverse platform uses the public key Q4, the new terminal identifier ID3, and the master key Pn to verify the digital signature S6. If it passes, it requests the evidence contract from the blockchain network 30 based on the association between the migration code M and the storage address of the evidence contract, and uses the platform key to sign the asset migration request, generates a digital signature S7 and a temporary point R2, and encapsulates the digital signature S7, temporary point R2 and the asset migration request into a call request and sends it to the blockchain network 30.

[0195] After receiving the call request, the evidence contract uses the verification function to verify the digital signature S7 and digital signature S5. After passing the verification, the evidence information modification function is called to overwrite the original corresponding fields in the contract with the new terminal public key Q4, the new terminal identifier ID3, and the master key Pn. The platform 40 changes the status of the evidence contract to "normal". The user can subsequently use the new terminal identifier ID3 and the new terminal public key Q4 to perform the Metaverse login operation on the new terminal.

[0196] The above method disclosed can be implemented by using various forms of equipment, so the present invention also discloses a device corresponding to the above method, and specific embodiments are given below for detailed description.

[0197] See also Figure 6 , an embodiment of the present application provides a Metaverse identity management device, which is deployed on a Metaverse platform and includes an identity registration module 61 and an identity authentication module 62;

[0198] The identity registration module 61 includes:

[0199] A first request response unit 611, configured to respond to an identity registration request initiated by a user through a first terminal, the identity registration request including a terminal key and a first terminal identifier, the terminal key being generated according to the user's blockchain key and the first terminal identifier;

[0200] The contract generation unit 612 is used to generate a proof contract according to the terminal key and the first terminal identifier and deploy it to the blockchain network;

[0201] The identity verification module 62 includes:

[0202] A second request response unit 621, configured to respond to a login request initiated by a user through a second terminal, the login request including a terminal key and a second terminal identifier;

[0203] The identity authentication unit 622 is used to obtain the evidence contract from the blockchain network according to the terminal key, use the evidence contract and the second terminal identifier to verify the user's identity, and generate a login response and send it to the second terminal when the verification is successful.

[0204] like Figure 7 As shown, an embodiment of the present application provides a Metaverse asset management device, which is deployed on a Metaverse platform and includes a device unbinding module 71 and an asset migration module 72;

[0205] The device unbinding module 71 includes:

[0206] A third request response unit 710 is used to respond to a terminal unbinding request initiated by a user through a terminal, where the terminal unbinding request includes the user's blockchain key and a first terminal key, where the first terminal key is generated according to the user's blockchain key and an old terminal identifier;

[0207] The contract status changing unit 712 is used to obtain the evidence storage contract which records both the blockchain key and the first terminal key from the blockchain network, and change the usage status of the evidence storage contract;

[0208] The unbinding response generation unit 713 is used to generate a migration code and an unbinding response and send them to the terminal, and record the association between the migration code and the storage address of the evidence storage contract;

[0209] The asset migration module 72 includes:

[0210] The fourth request response unit 721 is used to respond to the asset migration request initiated by the user through the terminal, the asset migration request includes the second terminal key, the new terminal identifier and the migration code, and the second terminal key is generated according to the user's blockchain key and the new terminal identifier;

[0211] The contract modification unit 722 obtains the evidence contract from the blockchain network according to the association relationship between the migration code and the storage address of the evidence contract, and modifies the evidence contract according to the second terminal key and the new terminal identifier;

[0212] The migration response generating unit 723 is configured to generate a migration response and send it to the terminal.

[0213] like Figure 8 As shown, an embodiment of the present application provides a metaverse asset management device, which is deployed in a user terminal and includes:

[0214] A first request generating unit 81 is used to generate a terminal unbinding request and send it to the Metaverse platform. The terminal unbinding request includes the user's blockchain key and a first terminal key. The first terminal key is generated according to the user's blockchain key and the old terminal identifier;

[0215] A first data receiving unit 82 is used to receive a migration code sent by the Metaverse platform and delete the first terminal key;

[0216] A key generation unit 83 generates a second terminal key according to the blockchain key and the new terminal identifier;

[0217] A second request generating unit 84 is used to generate an asset migration request and send it to the Metaverse platform. The asset migration request includes a second terminal key, a new terminal identifier, and a migration code;

[0218] The second data receiving unit 85 receives the migration response sent by the Metaverse platform.

[0219] like Fig. 9 As shown, an embodiment of the present application provides a terminal key generation device, including:

[0220] Data reading module 901, used to read the user's blockchain key and terminal identification;

[0221] A master key generation module 902, used to generate a master key according to a blockchain key;

[0222] The terminal key generation module 903 is used to generate a terminal key according to the terminal identification and the master key.

[0223] The implementation principle and technical effects of the above-mentioned device provided in the embodiment of the present application are the same as those of the aforementioned method embodiment. For the sake of brief description, for matters not mentioned in the device embodiment, reference can be made to the corresponding contents in the aforementioned method embodiment.

[0224] The alliance chain system provided in the embodiment of the present application can be applied to electronic devices. Fig.10 The hardware structure diagram of this electronic device is shown in FIG. Fig.10 , the hardware structure of the electronic device may include: at least one processor 1, at least one communication interface 2, at least one memory 3 and at least one communication bus 4;

[0225] In the embodiment of the present application, the number of the processor 1, the communication interface 2, the memory 3, and the communication bus 4 is at least one, and the processor 1, the communication interface 2, and the memory 3 communicate with each other through the communication bus 4;

[0226] The processor 1 may be a central processing unit CPU, or an application-specific integrated circuit ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present invention, etc.;

[0227] The memory 3 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), etc., such as at least one disk memory;

[0228] Among them, the memory stores a program, and the processor can call the program stored in the memory, and the program is used to: implement the various processing flows of the aforementioned Metaverse platform in the Metaverse identity management method or the Metaverse asset management solution, or, implement the various processing flows of the aforementioned user terminal in the Metaverse asset management solution, or, implement the various processing flows in the aforementioned terminal key generation solution.

[0229] An embodiment of the present application also provides a storage medium, which may store a program suitable for execution by a processor, wherein the program is used to: implement the various processing flows of the aforementioned Metaverse platform in the Metaverse identity management method or the Metaverse asset management solution, or, implement the various processing flows of the aforementioned user terminal in the Metaverse asset management solution, or, implement the various processing flows in the aforementioned terminal key generation solution.

[0230] Those skilled in the art should understand that the various steps of the above disclosed method can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, optionally, they can be implemented with program codes executable by the computing device, so that they can be stored in a storage device and executed by the computing device, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the embodiments of the present invention are not limited to any specific combination of hardware and software.

[0231] These computing device executable programs (also referred to as programs, software, software applications, or code) include machine instructions for programmable processors, and these computing programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, device, and / or device (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0232] Certain aspects of the present invention include process steps and instructions described herein in the form of algorithms. It should be noted that the process steps and instructions of the present invention can be implemented in software, firmware and / or hardware, and when implemented by software, it can be downloaded, stored on different platforms used by various operating systems and operated from the platforms.

[0233] Those skilled in the art will understand that the structures shown in the accompanying drawings are merely block diagrams of partial structures related to the scheme of the present application, and do not constitute a limitation on the terminal device to which the scheme of the present application is applied. The specific terminal device may include more or fewer components than shown in the figures, or combine certain components, or have a different arrangement of components.

[0234] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "possible design" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0235] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0236] The above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features thereof may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A metaverse identity management method, characterized in that: The method is performed on the Metaverse platform, including an identity registration process and an identity verification process; The identity registration process includes: Responding to an identity registration request initiated by a user through a first terminal, the identity registration request including a terminal key and a first terminal identifier, the terminal key being generated according to the user's blockchain key and the first terminal identifier; Generate a proof contract based on the terminal key and the first terminal identifier and deploy it to the blockchain network; The identity verification process includes: Responding to a login request initiated by a user through a second terminal, the login request including the terminal key and a second terminal identifier; The evidence contract is obtained from the blockchain network according to the terminal key, and the user identity is verified using the evidence contract and the second terminal identifier. When the verification is successful, a login response is generated and sent to the second terminal.

2. The method according to claim 1, characterized in that The identity registration process also includes the following steps before generating the evidence storage contract: Verify the legitimacy of the user's identity. If the verification is passed, enter the step of generating a proof contract based on the terminal key and the first terminal identifier and deploying it to the blockchain network.

3. The method according to claim 2, characterized in that The identity registration request also includes a first digital signature signed by the user using the blockchain key to sign the first terminal identifier, and a second digital signature signed by the user using the terminal key to sign the data in the identity registration request, then verifying the legitimacy of the user identity includes: Verifying the validity of the first digital signature using the blockchain key; The validity of the second digital signature is verified using the terminal key and the first terminal identification.

4. The method according to claim 1, characterized in that The login request also includes a third digital signature of the user using the terminal key to sign the data in the login request, and obtaining the evidence contract from the blockchain network according to the terminal key, and verifying the user identity using the evidence contract and the second terminal identifier includes: Acquire a certificate storage contract associated with the terminal key from the blockchain network according to the terminal key; Obtaining a terminal key and the first terminal identifier in the evidence storage contract; Verify the consistency of the first terminal identifier and the second terminal identifier, and if the verification is successful, use the terminal key obtained from the evidence storage contract to verify the validity of the third digital signature.

5. The method according to claim 1, characterized in that The method further comprises: After the user identity verification is passed, the session identifier carried in the login request is cached; When the user initiates a login request again, the consistency between the session identifier in the new login request and the cached session identifier is verified, and the identity authentication process is repeated if the verification fails.

6. A metaverse asset management method, characterized in that: The method is executed on the Metaverse platform, including a device unbinding process and an asset migration process; The device unbinding process includes: Responding to a terminal unbinding request initiated by a user through a terminal, wherein the terminal unbinding request includes the user's blockchain key and a first terminal key, where the first terminal key is generated according to the user's blockchain key and an old terminal identifier; Obtaining from the blockchain network a storage contract that records both the blockchain key and the first terminal key, and changing the usage status of the storage contract; Generate a migration code and an unbinding response and send them to the terminal, and record the association between the migration code and the storage address of the evidence storage contract; The asset migration process includes: Responding to an asset migration request initiated by a user through a terminal, the asset migration request including a second terminal key, a new terminal identifier, and a migration code, wherein the second terminal key is generated according to the user's blockchain key and the new terminal identifier; Obtaining the evidence contract from the blockchain network according to the association between the migration code and the storage address of the evidence contract, and modifying the evidence contract according to the second terminal key and the new terminal identifier; A migration response is generated and sent to the terminal.

7. The method according to claim 6, characterized in that The step of obtaining the evidence storage contract that simultaneously records the blockchain key and the first terminal key includes: Verify the legitimacy of the user's identity, and when the verification is passed, enter the step of obtaining the evidence storage contract that records both the blockchain key and the first terminal key.

8. The method according to claim 7, characterized in that The terminal unbinding request also includes a fourth digital signature of the user using the blockchain key to the data in the terminal unbinding request, and the verification of the legitimacy of the user identity includes: The blockchain key is used to verify the validity of the fourth digital signature.

9. The method according to claim 6, characterized in that The asset migration process includes: Verify the legitimacy of the user's identity. If the verification is passed, enter the step of obtaining the evidence contract from the blockchain network based on the association between the migration code and the storage address of the evidence contract.

10. The method according to claim 9, characterized in that The asset migration request also includes a fifth digital signature of the user using the second terminal key to sign the data in the asset migration request. The legitimacy of verifying the user identity during the asset migration process includes: The validity of the fifth digital signature is verified using the second terminal key.

11. The method according to claim 6, characterized in that Modifying the evidence storage contract according to the second terminal key and the new terminal identifier includes: Sign the data in the asset migration request using the platform key to generate a sixth digital signature; Encapsulate the sixth digital signature and the asset migration request into a call request and send it to the blockchain network, where the call request is used to request to call the modification of the evidence information function of the evidence contract; Change the usage status of the evidence storage contract.

12. A metaverse asset management method, characterized in that: The method is executed in a user terminal and includes: Generate a terminal unbinding request and send it to the Metaverse platform, wherein the terminal unbinding request includes the user's blockchain key and a first terminal key, and the first terminal key is generated according to the user's blockchain key and the old terminal identifier; Receive the migration code sent by the Metaverse platform and delete the first terminal key; Generate a second terminal key according to the blockchain key and the new terminal identifier; Generate an asset migration request and send it to the Metaverse platform, where the asset migration request includes the second terminal key, the new terminal identifier, and the migration code; Receive the migration response sent by the Metaverse platform.

13. A terminal key generation method, characterized in that: include: Read the user's blockchain key and terminal ID; Generate a master key based on the blockchain key; A terminal key is generated according to the terminal identification and the master key.

14. A metaverse identity management device, characterized in that: Deployed on the Metaverse platform, including identity registration module and identity authentication module; The identity registration module includes: A first request response unit, configured to respond to an identity registration request initiated by a user through a first terminal, the identity registration request including a terminal key and a first terminal identifier, the terminal key being generated according to the user's blockchain key and the first terminal identifier; A contract generation unit, used to generate a certificate storage contract according to the terminal key and the first terminal identifier and deploy it to the blockchain network; The identity verification module comprises: A second request response unit, configured to respond to a login request initiated by a user through a second terminal, the login request including a terminal key and a second terminal identifier; The identity authentication unit is used to obtain the evidence contract from the blockchain network according to the terminal key, use the evidence contract and the second terminal identifier to verify the user's identity, and generate a login response when the verification is successful and send it to the second terminal.

15. A metaverse asset management device, characterized in that: Deployed on the Metaverse platform, including device unbinding module and asset migration module; The device unbinding module includes: A third request response unit, configured to respond to a terminal unbinding request initiated by a user through a terminal, wherein the terminal unbinding request includes the user's blockchain key and a first terminal key, and the first terminal key is generated according to the user's blockchain key and an old terminal identifier; A contract status changing unit, used to obtain a storage contract that records both a blockchain key and a first terminal key from a blockchain network, and change the usage status of the storage contract; The unbinding response generation unit is used to generate a migration code and an unbinding response and send them to the terminal, recording the association between the migration code and the storage address of the evidence storage contract; The asset migration module includes: A fourth request response unit, configured to respond to an asset migration request initiated by a user through a terminal, wherein the asset migration request includes a second terminal key, a new terminal identifier, and a migration code, and the second terminal key is generated according to the user's blockchain key and the new terminal identifier; The contract modification unit obtains the evidence contract from the blockchain network according to the association between the migration code and the storage address of the evidence contract, and modifies the evidence contract according to the second terminal key and the new terminal identifier; The migration response generating unit is used to generate a migration response and send it to the terminal.

16. A metaverse asset management device, characterized in that: Deployed on user terminals, including: A first request generating unit, configured to generate a terminal unbinding request and send it to the Metaverse platform, wherein the terminal unbinding request includes a user's blockchain key and a first terminal key, and the first terminal key is generated according to the user's blockchain key and an old terminal identifier; A first data receiving unit, configured to receive a migration code sent by the Metaverse platform and delete a first terminal key; A key generation unit, generating a second terminal key according to the blockchain key and the new terminal identifier; A second request generating unit, configured to generate an asset migration request and send it to the Metaverse platform, wherein the asset migration request includes a second terminal key, a new terminal identifier, and a migration code; The second data receiving unit receives a migration response sent by the Metaverse platform.

17. A terminal key generation device, characterized in that: include: Data reading module, used to read the user's blockchain key and terminal identification; A master key generation module, used to generate a master key based on a blockchain key; The terminal key generation module is used to generate a terminal key according to the terminal identification and the master key.

Images