Digital asset operation permission control method, module, and storage medium

Abstract

Disclosed in embodiments of the present application are a digital asset operation permission control method, a module, and a storage medium. The embodiments of the present application implement cross-platform management and control of digital asset operation permissions. When the embodiments of the present application are applied to metaverse scenarios, a cross-platform collaboration and sharing solution for digital assets can be provided for users in metaverses, thereby satisfying the requirements of people in the metaverse world anonymously navigating across service platforms in the metaverses and being able to perform sharing and collaboration operations on a same digital asset.

Description

Method, module and storage medium for controlling operation permission of digital asset

[0001] Cross-reference to related applications

[0002] The present application is based on and claims priority to Chinese Patent Application No. 202410880745.5, filed on July 2, 2024, the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0003] The present application relates to the technical field of business permission control, and particularly relates to a method, module and storage medium for controlling operation permission of digital asset. BACKGROUND

[0004] With the development of mobile network technology and the richness of mobile terminal types, people will have more urgent needs for metaverse in mobile networks, and hope to access the metaverse world through mobile devices at any time and anywhere.

[0005] Future businesses in the metaverse world will be very rich, and the use of digital assets will also have various needs. On the one hand, network live services need to be provided to support various businesses and meet various needs for the use of digital assets (cloud storage, sharing, etc.), and on the other hand, access control for digital assets needs to be considered to avoid illegal use.

[0006] The specification for supporting metaverse businesses in mobile communication networks is being established. At present, the related technology proposes to set up a digital asset storage management function module for storing digital assets of users in the metaverse world. However, there is no reasonable method for sharing the stored digital assets among users and between the metaverse. SUMMARY

[0007] At least one embodiment of the present application provides a method, module and storage medium for controlling operation permission of digital asset, which is used to solve the problem of cross-platform operation permission control of digital asset.

[0008] To solve the above technical problems, the present application is implemented as follows:

[0009] The present application provides a method for controlling operation permission of digital asset, comprising:

[0010] The first function module receives a first request sent by a first platform, for requesting a first user to perform a first operation on a first digital asset;

[0011] The first function module sends a second request to a second function module, for checking whether the first user has the permission of the first operation on the first digital asset;

[0012] The first function module receives a second response sent by a second function module, the second response being used for indicating whether the first user has the permission of the first operation of the first digital asset;

[0013] The first function module sends a first response to the first platform, the first response being used for indicating a result of the first operation of the first digital asset.

[0014] Optionally, the first request comprises: first user information of the first user, information of the first digital asset, and information of the first operation.

[0015] Optionally, the first user information comprises a user identifier and / or a token list of the first user.

[0016] The information of the first digital asset comprises a digital asset identifier of the first digital asset.

[0017] The information of the first operation comprises an operation type and / or an operation time, and the operation type comprises one or more of access, update, change, and download.

[0018] Optionally, the first request and the second request further comprise a token list of the first user respectively, wherein each token in the token list of the first user corresponds to an operation authorization of a digital asset.

[0019] Optionally, in a case where the second response comprises a second token, the second token is included in the first response sent to the first platform, so that the first user corresponding to a first terminal adds the second token into the token list of the first user.

[0020] Embodiments of the present application provide a control method of an operation permission of a digital asset, comprising:

[0021] A second function module receives a second request sent by a first function module, the second request being used for checking whether a first user has a permission of a first operation of a first digital asset;

[0022] The second function module checks whether the first user has the permission of the first operation of the first digital asset.

[0023] The second function module sends a second response to the first function module, the second response being used for indicating whether the first user has the permission of the first operation of the first digital asset.

[0024] Optionally, the second request comprises: first user information of the first user and / or information of the first digital asset and / or information of the first operation.

[0025] Optionally, the first user information comprises a user identifier and / or a token list of the first user.

[0026] The information of the first digital asset comprises a digital asset identifier of the first digital asset.

[0027] The information of the first operation comprises an operation type and / or an operation time, and the operation type comprises one or more of access, update, change, and download.

[0028] Optionally, the second function module verifying whether the first user has the permission of the first operation of the first digital asset comprises:

[0029] The second function module verifies a control mode of the first digital asset.

[0030] In a case where the first digital asset is in a relaxed control mode, the second function module sends a second response to the first function module, and the second response is used to indicate that the first user has the permission of the first operation of the first digital asset.

[0031] Optionally, the second function module verifying whether the first user has the permission of the first operation of the first digital asset further comprises:

[0032] In a case where the first digital asset is in a strict control mode or a general control mode, the permission of the first user to the first operation of the first digital asset is verified, and in a case where the permission verification is successful, the second function module sends a second response to the first function module, and the second response is used to indicate that the first user has the permission of the first operation of the first digital asset.

[0033] Optionally, the permission of the first user to the first operation of the first digital asset is verified by using an authorization record stored in the second function module.

[0034] Optionally, the second function module verifying whether the first user has the permission of the first operation of the first digital asset further comprises:

[0035] In a case where the permission verification fails, the second function module sends a third request to a second platform and / or a second terminal, and the third request is used to request the permission of the first user to the first operation of the first digital asset.

[0036] The second function module receives a third response sent by the second platform and / or the second terminal, and the third response is used to indicate whether the first user is allowed to perform the first operation on the first digital asset.

[0037] Optionally, the method further comprises:

[0038] In a case where the third response indicates that the first operation on the first digital asset by the first user is allowed, entering the second functional module to send a second response to the first functional module, and the second response is used to indicate that the first user has the right to perform the first operation on the first digital asset;

[0039] In a case where the third response indicates that the first operation on the first digital asset by the first user is not allowed, entering the second functional module to send a second response to the first functional module, and the second response is used to indicate that the first user does not have the right to perform the first operation on the first digital asset.

[0040] Optionally, the third request includes: first user information and / or first digital asset information and / or first operation information;

[0041] The first user information includes a user identifier;

[0042] The first digital asset information includes a digital asset identifier of the first digital asset;

[0043] The first operation information includes an operation type and / or an operation time, and the operation type includes one or more of access, update, change, and download.

[0044] Optionally, the method further includes:

[0045] In a case where the third response indicates that the first operation on the first digital asset by the first user is allowed, according to the third response, storing a new authorization record, and the new authorization record includes the first digital asset information and the first operation information.

[0046] Optionally, the second request includes a token list of the first user, wherein each token in the token list of the first user corresponds to an operation authorization of a digital asset;

[0047] Verifying, by the second functional module, the right of the first user to perform the first operation on the first digital asset includes: matching the token list of the first user with a token list of the first digital asset, wherein each token in the token list of the first digital asset corresponds to an operation authorization of the first digital asset and is associated with operation information;

[0048] In a case where the same first token exists between the token list of the first user and the token list of the first digital asset, information of a second operation associated with the first token is acquired, and in a case where the information of the first operation matches the information of the second operation, it is determined that the permission verification is successful, otherwise, it is determined that the permission verification fails.

[0049] Optionally, the storage of the new authorization record specifically includes: generating a second token, storing the second token in the token list of the first digital asset, and associating the second token with the information of the first operation.

[0050] Optionally, the method further includes:

[0051] The second response includes the second token, so that the first terminal corresponding to the first user adds the second token to the token list of the first user.

[0052] Embodiments of the present application provide a method for controlling operation permission of a digital asset, including:

[0053] The second function module receives a fourth request sent by the first platform or the first terminal, and the fourth request is used to apply for the permission of the first operation of the first digital asset by the first user.

[0054] The second function module determines whether the fourth request needs to obtain the consent and / or authorization of all parties of the first digital asset and / or the second platform and / or the second terminal.

[0055] In a case where the fourth request needs to obtain the consent and / or authorization, the second function module sends a fifth request to the second platform and / or the second terminal, and the fifth request is used to request the permission of the first operation of the first digital asset by the first user.

[0056] Optionally, the fourth request includes first user information and / or information of the first digital asset and / or information of the first operation.

[0057] The first user information includes a user identifier, the information of the first digital asset includes a digital asset identifier of the first digital asset, and the information of the first operation includes an operation type and / or an operation time, and the operation type includes one or more of access, update, change, and download.

[0058] Optionally, the method further includes:

[0059] The second function module receives a fifth response sent by the second platform and / or the second terminal, and the fifth response is used to indicate whether the first operation of the first digital asset by the first user is allowed.

[0060] Optionally, the method further includes:

[0061] In a case where the fifth response indicates that the first operation of the first digital asset by the first user is allowed, authorization information of all parties and / or the second platform to the first digital asset is recorded and / or stored, and the authorization information includes information of the first digital asset and / or user information and / or information of the first operation.

[0062] Optionally, the method further comprises:

[0063] The fourth response is sent to the first platform or the first terminal, and the fourth response is used to indicate an application result of the permission of the first operation of the first digital asset by the first user.

[0064] Optionally, the second function module determines whether the fourth request needs to obtain consent and / or authorization of all parties and / or the second platform and / or the second terminal of the first digital asset, including:

[0065] The second function module checks a control mode of the first digital asset.

[0066] In a case where the first digital asset is in a strict control mode, the step of sending the fourth response to the first platform or the first terminal is entered, and the fourth response is used to indicate that the application of the permission of the first operation of the first digital asset by the first user is rejected.

[0067] In a case where the first digital asset is in a general control mode, it is determined that the fourth request needs to obtain consent and / or authorization of all parties and / or the second platform and / or the second terminal of the first digital asset.

[0068] In a case where the first digital asset is in a loose control mode, it is determined that the fourth request does not need consent and / or authorization of all parties and / or the second platform and / or the second terminal of the first digital asset, the step of sending the fourth response to the first platform or the first terminal is entered, and the fourth response is used to indicate that the application of the permission of the first operation of the first digital asset by the first user obtains consent and / or authorization.

[0069] Optionally, the authorization information of all parties and / or the second platform to the first digital asset is recorded and / or stored, and specifically includes: a third token is generated, stored in a token list of the first digital asset, and associated with information of the first operation.

[0070] The fourth response includes the third token, so that the first terminal adds the third token to a token list of the first user.

[0071] Embodiments of the present application provide a control method of an operation permission of a digital asset, including:

[0072] The second function module receives a sixth request sent by the third platform and / or the third terminal and / or the first function module, and the sixth request is used to set or update a control mode of the first digital asset;

[0073] The second function module verifies whether the sixth request is authorized by all parties of the first digital asset and / or the second platform and / or the second terminal, and in a case where the verification succeeds, sets and / or updates and / or stores the control mode of the first digital asset according to the sixth request, and sends a sixth response to the third platform and / or the third terminal, and the sixth response is used to indicate whether the control mode of the first digital asset is successfully set or updated.

[0074] Optionally, the method further comprises:

[0075] The sixth request comprises information of the first digital asset and / or the control mode.

[0076] Optionally, the method further comprises:

[0077] In a case where the verification fails, the sixth response is sent to the third platform and / or the third terminal and the first function module, and the sixth response is used to indicate that the control mode of the first digital asset fails to be set or updated.

[0078] Embodiments of the present application provide a control method of an operation permission of a digital asset, comprising:

[0079] The first function module receives a seventh request sent by the third platform and / or the third terminal, and the seventh request is used to set or update a control mode of the first digital asset;

[0080] The first function module sends an eighth request to the second function module, and the eighth request is used to set or update the control mode of the first digital asset;

[0081] The first function module receives an eighth response sent by the second function module, and the eighth response is used to indicate whether the control mode of the first digital asset is successfully set or updated;

[0082] The first function module sends a seventh response to the third platform and / or the third terminal, and the seventh response is used to indicate whether the control mode of the first digital asset is successfully set or updated.

[0083] Optionally, the method further comprises:

[0084] The seventh request comprises information of the first digital asset and the control mode.

[0085] Embodiments of the present application provide a control method of an operation permission of a digital asset, comprising:

[0086] The second function module receives first information sent by the first function module, and the first information comprises information of the first digital asset and / or information of an owner of the first digital asset and / or second platform information;

[0087] The second function module sends a ninth request to the first function module, for requesting the owner of the first digital asset and / or the second platform and / or a second terminal to set a control mode of the first digital asset;

[0088] The second function module receives a ninth response sent by the first function module, for indicating the control mode of the first digital asset;

[0089] The second function module sets and / or stores the control mode of the first digital asset according to the ninth response.

[0090] Optionally, the information of the first digital asset comprises a digital asset identifier of the first digital asset; the information of the owner of the first digital asset comprises an owner identifier; and the information of the second platform comprises at least one of a platform IP address, a platform identifier and a platform calling interface.

[0091] Optionally, the ninth response comprises the information of the first digital asset and / or the control mode.

[0092] Optionally, the method further comprises:

[0093] The second function module sends fourth information to the first function module, for indicating a setting result of the control mode of the first digital asset.

[0094] Optionally, the method further comprises:

[0095] The second function module creates a token list for the first digital asset, generates a fourth token of the owner of the first digital asset, associates the fourth token with third operation information, and saves the fourth token in the token list of the first digital asset;

[0096] The fourth information further comprises the fourth token.

[0097] Embodiments of the present application provide a control method of operation permission of a digital asset, comprising:

[0098] The first function module sends first information to the second function module, and the first information comprises information of a first digital asset and / or information of an owner of the first digital asset and / or second platform information;

[0099] The first function module receives a ninth request sent by the second function module, for requesting to set a control mode of the first digital asset;

[0100] The first function module sends a tenth request to the second platform and / or the second terminal, for requesting to set a control mode of the first digital asset;

[0101] The first function module receives a tenth response sent by the second platform and / or the second terminal, for indicating the control mode of the first digital asset;

[0102] The first function module sends a ninth response to the second function module, for indicating the control mode of the first digital asset.

[0103] Optionally, the information of the first digital asset comprises a digital asset identifier of the first digital asset; the information of the owner of the first digital asset comprises an owner identifier; and the information of the second platform comprises at least one of a platform IP address, a platform identifier and a platform calling interface.

[0104] Optionally, the tenth response comprises the information of the first digital asset and / or the control mode.

[0105] Optionally, the method further comprises:

[0106] The first function module receives fourth information sent by the second function module, for indicating a setting result of the control mode of the first digital asset;

[0107] The first function module sends fifth information to the second platform or the second terminal, the fifth information comprising the setting result of the control mode of the first digital asset.

[0108] Optionally, the fourth information further comprises a fourth token, and the first function module further comprises the fourth token in the fifth information, so that the second terminal saves the fourth token in a token list of the owner of the first digital asset.

[0109] Embodiments of the present application provide a first function module, comprising:

[0110] A first receiving module is configured to receive a first request sent by a first platform, for requesting a first operation of a first user on a first digital asset;

[0111] A first sending module is configured to send a second request to a second function module, for checking whether the first user has a permission of the first operation on the first digital asset;

[0112] A second receiving module is configured to receive a second response sent by the second function module, for indicating whether the first user has the permission of the first operation on the first digital asset;

[0113] The second sending module is configured to send a first response to the first platform, where the first response is used to indicate a result of the first operation of the first digital asset.

[0114] The second function module provided in the embodiments of the present application comprises:

[0115] The first receiving module is configured to receive a second request sent by the first function module, where the second request is used to check whether the first user has the permission of the first operation of the first digital asset.

[0116] The checking module is configured to check whether the first user has the permission of the first operation of the first digital asset.

[0117] The first sending module is configured to send a second response to the first function module, where the second response is used to indicate whether the first user has the permission of the first operation of the first digital asset.

[0118] The second function module provided in the embodiments of the present application comprises:

[0119] The first receiving module is configured to receive a fourth request sent by the first platform or the first terminal, where the fourth request is used to apply for the permission of the first operation of the first digital asset by the first user.

[0120] The determining module is configured to determine whether the fourth request needs to obtain the consent and / or authorization of all parties of the first digital asset and / or the second platform and / or the second terminal.

[0121] The first sending module is configured to send a fifth request to the second platform and / or the second terminal, where the fifth request is used to request the permission of the first operation of the first digital asset by the first user, in a case where the fourth request needs to obtain the consent and / or authorization.

[0122] The second function module provided in the embodiments of the present application comprises:

[0123] The first receiving module is configured to receive a sixth request sent by the third platform and / or the third terminal and / or the first function module, where the sixth request is used to set or update a control mode of the first digital asset.

[0124] The first processing module is configured to verify whether the sixth request obtains the authorization of all parties of the first digital asset and / or the second platform and / or the second terminal, and in a case where the verification succeeds, set and / or update and / or store the control mode of the first digital asset according to the sixth request, and send a sixth response to the third platform and / or the third terminal, where the sixth response is used to indicate whether the control mode of the first digital asset is set or updated successfully.

[0125] The first function module provided in the embodiments of the present application comprises:

[0126] The first receiving module is configured to receive a seventh request sent by the third platform and / or the third terminal, and the seventh request is used to set or update the control mode of the first digital asset.

[0127] The first sending module is configured to send an eighth request to the second functional module, and the eighth request is used to set or update the control mode of the first digital asset.

[0128] The second receiving module is configured to receive an eighth response sent by the second functional module, and the eighth response is used to indicate whether the control mode of the first digital asset is set or updated successfully.

[0129] The second sending module is configured to send a seventh response to the third platform and / or the third terminal, and the seventh response is used to indicate whether the control mode of the first digital asset is set or updated successfully.

[0130] The second functional module provided in the embodiments of the present application comprises:

[0131] The first receiving module is configured to receive first information sent by the first functional module, and the first information comprises information of the first digital asset and / or information of an owner of the first digital asset and / or second platform information.

[0132] The first sending module is configured to send a ninth request to the first functional module, and the ninth request is used to request the owner of the first digital asset and / or the second platform and / or the second terminal to set the control mode of the first digital asset.

[0133] The second receiving module is configured to receive a ninth response sent by the first functional module, and the ninth response is used to indicate the control mode of the first digital asset.

[0134] The first processing module is configured to set and / or store the control mode of the first digital asset according to the ninth response.

[0135] The first functional module provided in the embodiments of the present application comprises:

[0136] The first sending module is configured to send first information to the second functional module, and the first information comprises information of the first digital asset and / or information of an owner of the first digital asset and / or second platform information.

[0137] The first receiving module is configured to receive a ninth request sent by the second functional module, and the ninth request is used to request to set the control mode of the first digital asset.

[0138] The second sending module is configured to send a tenth request to the second platform and / or the second terminal, and the tenth request is used to request to set the control mode of the first digital asset.

[0139] The second receiving module is configured to receive a tenth response sent by the second platform and / or the second terminal, the tenth response being used to indicate a control mode of the first digital asset.

[0140] The third sending module is configured to send a ninth response to the second functional module, the ninth response being used to indicate the control mode of the first digital asset.

[0141] The first functional module provided in the embodiments of the present application includes a processor, a memory, and a program stored in the memory and capable of running on the processor. When the program is executed by the processor, the steps of the method performed by the first functional module are implemented.

[0142] The second functional module provided in the embodiments of the present application includes a processor, a memory, and a program stored in the memory and capable of running on the processor. When the program is executed by the processor, the steps of the method performed by the second functional module are implemented.

[0143] The computer readable storage medium provided in the embodiments of the present application stores a program. When the program is executed by a processor, the steps of the method according to any one of the above embodiments are implemented.

[0144] The computer program product provided in the embodiments of the present application includes computer instructions. When the computer instructions are executed by a processor, the steps of the method according to any one of the above embodiments are implemented.

[0145] Compared with the related art, the method, module and storage medium for controlling the operation permission of a digital asset provided in the embodiments of the present application realize the management and control of the operation permission of a digital asset across platforms. When applied to a meta universe scenario, the embodiments of the present application can provide a cross-platform digital asset collaboration and sharing solution for meta universe users, meeting the demand for anonymous free travel among various meta universe business platforms and realizing the sharing and collaborative operation of the same digital asset in the meta universe world. BRIEF DESCRIPTION OF DRAWINGS

[0146] Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The accompanying drawings are included to provide a description of the preferred embodiments, and are not intended to limit the scope of the present application. Moreover, like reference numerals designate like parts throughout the several views in the drawings. In the drawings:

[0147] FIG. 1 is a schematic diagram of a system for managing and controlling the cross-platform operation permission of a digital asset according to an embodiment of the present application;

[0148] FIG. 2 is a flowchart of a method for controlling the operation permission of a digital asset according to an embodiment of the present application;

[0149] FIG. 3 is another flowchart of the method for controlling the operation permission of the digital asset according to an embodiment of the present application;

[0150] FIG. 4 is an interaction example diagram of the method for controlling the operation permission of the digital asset according to an embodiment of the present application;

[0151] FIG. 5 is another flowchart of the method for controlling the operation permission of the digital asset according to an embodiment of the present application;

[0152] FIG. 6 is another interaction example diagram of the method for controlling the operation permission of the digital asset according to an embodiment of the present application;

[0153] FIG. 7 is another flowchart of the method for controlling the operation permission of the digital asset according to an embodiment of the present application;

[0154] FIG. 8 is another flowchart of the method for controlling the operation permission of the digital asset according to an embodiment of the present application;

[0155] FIG. 9 is another interaction example diagram of the method for controlling the operation permission of the digital asset according to an embodiment of the present application;

[0156] FIG. 10 is another interaction example diagram of the method for controlling the operation permission of the digital asset according to an embodiment of the present application;

[0157] FIG. 11 is another flowchart of the method for controlling the operation permission of the digital asset according to an embodiment of the present application;

[0158] FIG. 12 is another flowchart of the method for controlling the operation permission of the digital asset according to an embodiment of the present application;

[0159] FIG. 13 is another interaction example diagram of the method for controlling the operation permission of the digital asset according to an embodiment of the present application;

[0160] FIG. 14 is a structural schematic diagram of the first function module according to an embodiment of the present application;

[0161] FIG. 15 is a structural schematic diagram of the second function module according to an embodiment of the present application;

[0162] FIG. 16 is another structural schematic diagram of the second function module according to an embodiment of the present application;

[0163] FIG. 17 is another structural schematic diagram of the second function module according to an embodiment of the present application;

[0164] FIG. 18 is another structural schematic diagram of the first function module according to an embodiment of the present application;

[0165] FIG. 19 is another structural schematic diagram of the second function module according to an embodiment of the present application;

[0166] FIG. 20 is another structural schematic diagram of the first function module according to an embodiment of the present application;

[0167] FIG. 21 is a structural schematic diagram of a first function module or a second function module according to another embodiment of the present application. DETAILED DESCRIPTION

[0168] The terms "first", "second", and the like in the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second" are generally of a kind and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in the present application means at least one of the connected objects. For example, "A or B" covers three schemes, namely, scheme one: including A and not including B; scheme two: including B and not including A; scheme three: including A and B. The character " / " generally represents that the objects before and after are in an "or" relationship.

[0169] The term "indication" in the present application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). Among them, the direct indication can be understood as that the sender explicitly informs the receiver of specific information, operations to be performed or requested results, etc. in the sent indication; the indirect indication can be understood as that the receiver determines the corresponding information according to the indication sent by the sender, or judges and determines the operations to be performed or the requested results according to the judgment result.

[0170] It is worth noting that the techniques described in embodiments of the present application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, and can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" are often used interchangeably in embodiments of the present application, and the described techniques can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these techniques can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0171] At present, based on the mobile communication network architecture, the related technology does not provide a control scheme for cross-platform use of digital assets in the metaverse. Although digital assets are shared and cooperatively operated between individuals in the non-metaverse world, the above operations are all based on the services provided by the same platform. The future metaverse world may be a digital world parallel to the real world, and there will be a large number of interconnection application scenarios between metaverse business platforms, therefore, a high-efficiency and feasible control scheme for digital asset sharing and interconnection is needed.

[0172] Please refer to FIG. 1, the embodiments of the present application provide a system capable of controlling the cross-platform operation permission of digital assets, the system includes multiple platforms, a first function module, a second function module and a terminal (such as the first terminal in FIG. 1).

[0173] The plurality of platforms can include a first platform, a second platform, a third platform, …, an nth platform, and the platforms can be various business platforms, such as metaverse business platforms 1-n, respectively. For a certain digital asset, one or some platforms can be a virtual application layer server of an owner (Owner Virtual Application Layer Server, Consumer VAL Server, Owner VAL Server), a platform of the owner, a business platform of the owner (such as a metaverse business platform of the owner); another or some other platforms can be a virtual application layer server of a consumer (Consumer VAL Server), a platform of the consumer, a business platform of the consumer (such as a metaverse business platform of the consumer). In addition, the owner is also referred to as the owner, and the consumer is also referred to as the user or the consumer.

[0174] The first function module can also be referred to as a digital asset storage management platform, a digital asset storage management function module, an application-digital asset container management (A-DACM) function, an A-DACM function module, an A-DACM platform, or an API provider area.

[0175] The second function module can also be referred to as a digital asset operation permission management platform or a digital asset operation permission management function module, a digital asset permission management (DAPM) function, a DAPM function module, or a common API framework (CAPIF) core function module.

[0176] The terminal includes a DAPM client, a personal computer (PC) terminal, a mobile phone terminal, a wearable device, and the like. Specifically, as shown in FIG. 1, the terminal can include, but is not limited to, the following modules: a platform client (such as a metaverse business client), a permission management client, and a local storage module. The first terminal and the second terminal shown in FIG. 1 can have similar structures.

[0177] The functions of the related modules / platforms and the related interfaces are described below.

[0178] The second function module is used for managing the operation permission of the digital asset. The specific functions include:

[0179] (1) Digital asset owner information storage and authorization inquiry;

[0180] (2) Generation, update, storage, deletion, and query of operation permission information of digital assets, wherein the operation permission information includes a digital asset identifier, authorized operations, and authorized time, etc. The operations on the digital assets include, but are not limited to, access, change, and download, etc.

[0181] (3) Generation of permission tokens, which are also referred to as tokens in some embodiments of the present application.

[0182] (4) Permission verification.

[0183] The first functional module is configured to store digital assets and record basic information (e.g., the name of a digital asset) of the digital assets.

[0184] The platform is configured to initiate uploading of digital assets and information, apply for setting permissions, apply for operation permissions, and perform operations on the digital assets.

[0185] The permission management client is configured to update operation permissions of digital assets and apply for new permissions through the permission management client.

[0186] The platform client (e.g., a metaverse business client) is configured to be installed on a terminal and used to interact with a user to set permissions for digital assets and apply for permissions.

[0187] The local storage module is a secure storage module in a terminal and is configured to store permission tokens of digital assets that can be operated by a user. The local storage module itself needs a secure access control mechanism to ensure that a legitimate user can access the information.

[0188] Interface 1 (IF1) is an interface between the first functional module and the second functional module and is configured to transmit basic information (e.g., a digital asset number, a digital asset name, and an owner) of digital assets, permission settings, and query requests and query results.

[0189] Interface 2 (IF2) is an interface between the second functional module and the platform and is configured to transmit information about setting and updating operation permissions of digital assets by all parties and to apply for and obtain permission information about operation permissions of digital assets by users.

[0190] Interface 3 (IF3) is an interface between the first functional module and the platform and is configured to transmit registration information (e.g., a digital asset number, a digital asset name, and an owner) of digital assets, permission setting information, and operation requests of digital assets.

[0191] Interface 4 (IF4) is an interface between the digital asset operation permission management platform / module and the permission management client and is configured to transmit information about setting and updating operation permissions of digital assets by all parties and to apply for and obtain permission information about operation permissions of digital assets by users.

[0192] In addition, the permission token (also referred to as token herein) of the digital asset involved in some embodiments of the present application and the control mode are described as follows:

[0193] The digital asset permission token is generated by the second function module, and can be generated according to the digital asset identifier, the authorized operation type, the authorized operation time and the like. Considering that the digital person identity of each platform (such as each business platform of the metaverse world) may not be unified, it is difficult to identify the identity of the same user on different business platforms, therefore the token is issued for the operation permission of the digital asset, and the operation is controlled by verifying the token.

[0194] The storage mode of the token is as follows:

[0195] (1) User side storage: each user has a permission token list (also referred to as token list herein), and each permission token in the token list corresponds to a digital asset that can be operated by the user, and the related digital asset identifier can also be stored.

[0196] (2) Second function module: a permission token list is stored for each digital asset, and the list stores all permission tokens authorized for the digital asset and the information of the associated operations (such as the authorized operation type and / or the authorized operation time), therefore the information stored by the second function module can include the digital asset identifier, the permission token, the authorized operation type, the authorized operation time and the like.

[0197] The control mode of the digital asset is the way to limit the operation of the user when the digital asset is used by the user. There are three modes, which are strict control mode (also referred to as first control mode), general control mode (also referred to as second control mode) and loose control (also referred to as third control mode). Among them, the general control mode means that any operation on the digital asset needs to be authorized by all parties, that is, part of the people are allowed to operate the digital asset, but whether others need to obtain the authorization of all parties before operating the digital asset; the loose control mode means that any operation on the digital asset does not need to be authorized by all parties, that is, the operation right of the digital asset is open to all people; the strict control mode means that any operation on the digital asset by any user is rejected except all parties.

[0198] In various embodiments below, it is assumed that the first user is a user under a first platform (such as a first metaverse business platform), and the first user accesses the first platform through a first terminal. The second user is a user under a second platform (such as a second metaverse business platform), and the second user accesses the second platform through a second terminal. The first digital asset is a digital asset of the second user, that is, the owner of the first digital asset is the second user, and the first digital asset is an asset of the second platform. The first user is a user of the first digital asset. The first terminal includes but is not limited to a DAPM client, a DAPM client, a PC terminal, a mobile terminal, a wearable device, and the like. Similarly, the second terminal includes but is not limited to a DAPM client, a DAPM client, a PC terminal, a mobile terminal, a wearable device, and the like. The first user sends a request, a response or information to the first platform or the second functional module, which can be sent through the terminal logged in / associated / corresponding to the first user, for example, the first user sends to the first platform or the second functional module through the first terminal. Similarly, the second user sends a request, a response or information to the second platform or the second functional module, which can be sent through the terminal logged in / associated / corresponding to the second user, for example, the second user sends to the second platform or the second functional module through the second terminal. In addition, in the embodiments of the present application, the xth request and the xth response are usually a pair of request and response, that is, the xth response is the response to the xth request. X can be one, two, three, and the like.

[0199] The method for controlling the operation permission of the digital asset provided by the embodiments of the present application can realize the cross-platform operation permission control of the digital asset. The above method of the present application will be described from different functional modules respectively through different business processes.

[0200] Process 1: The first user initiates a request for a first operation on a first digital asset

[0201] Please refer to FIGS. 2-4, the method for controlling the operation permission of the digital asset provided by some embodiments of the present application realizes the relevant permission control in the process of the first user initiating a request for a first operation on a first digital asset. Among them, FIG. 2 is a flowchart of the above process 1 on the first functional module side, FIG. 3 is a flowchart of the above process 1 on the second functional module side, and FIG. 4 is an example of the interaction process between various devices / modules in the above process 1 taking the metaverse business platform as an example.

[0202] As shown in FIG. 2, when the above process 1 is applied to the first functional module side, the following steps are included:

[0203] Step 21, the first functional module receives the first request sent by the first platform, for requesting the first user to perform a first operation on the first digital asset.

[0204] Here, the first user can initiate a request for the first operation on the first digital asset through the first platform, at which time the first platform sends a first request to the first function module, and the first function module receives the first request sent by the first platform. The information or content contained in the first request can include: first user information of the first user, information of the first digital asset, information of the first operation. Specifically, the first user information can include a user identifier of the first user and / or a token list of the first user. The information of the first digital asset includes a digital asset identifier of the first digital asset. The information of the operation on the digital asset (such as the first operation) can specifically include an operation type and / or an operation time, and the operation type includes one or more of access, update, change, and download. The operation time can be a start time and an end time of the operation, or a start time and a duration of the operation, or an operation period and an operation time range in each period, and the like, which are not limited in the embodiments of the present application.

[0205] In addition, in the embodiments of the present application, the token list of a certain user includes tokens of operation permissions of each digital asset obtained by the user, and each token corresponds to an operation permission of a digital asset. The operation permission specifically includes an operation type and / or an operation time.

[0206] Step 22, the first function module sends a second request to the second function module for checking whether the first user has the permission of the first operation on the first digital asset.

[0207] Step 23, the first function module receives a second response sent by the second function module for indicating whether the first user has the permission of the first operation on the first digital asset.

[0208] In steps 22-23 above, after receiving the first request, the first function module sends a second request to the second function module for checking / determining / judging whether the first user has the permission of the first operation on the first digital asset. After receiving the second request, the second function module checks / determines / judges whether the first user has the permission of the first operation on the first digital asset, and according to the checking / determining / judging result, returns a second response to the first function module for indicating whether the first user has the permission of the first operation on the first digital asset.

[0209] Step 24, the first function module sends a first response to the first platform for indicating the result of the first operation on the first digital asset.

[0210] Here, the first function module can allow or not allow the first operation of the first digital asset by the first user according to the second response after receiving the second response. In the embodiments of the present application, the digital assets of each platform can be pre-registered and stored in the first function module. In this way, in the case that the second response indicates that the first user has the right to the first operation of the first digital asset, the first function module can perform the first operation on the first digital asset; and in the case that the second response indicates that the first user does not have the right to the first operation of the first digital asset, the first function module can refuse the first operation. Then, the first function module can also send the first response in step 24 to the first platform, and the first platform can send it to the first terminal (the first user) after receiving it, to inform the first user (the first terminal) of the result of the first operation of the first digital asset, which can specifically include whether the first operation is allowed to be performed and whether the first operation is successfully performed when allowed to be performed, and the like.

[0211] Through the above steps, the embodiments of the present application realize the control of the right of the first operation of the first digital asset by the first user through the second function module. Since the first platform to which the first user belongs and the second platform to which the first digital asset belongs can be different platforms, the control of the operation right of the digital asset across platforms can be realized.

[0212] It should be noted that in the embodiments of the present application, the second function module can have multiple ways to check whether the first user has the permission of the first operation of the first digital asset. For example, by recording the operation authorization of the digital asset obtained by the user, the recorded data can be used for checking. A specific implementation means can be in the form of a permission token. For example, the second function module stores / saves a token list of each digital asset, wherein each token in the token list of a certain digital asset corresponds to an operation authorization of the digital asset, and is associated with the information of an operation, and the information of the operation includes the operation type and / or the operation time. Each user respectively saves the token list of the user, and each token in the token list of a user corresponds to an operation authorization of a digital asset. Taking the token list of the first user as an example, in the embodiments, when the first user requests the first operation of the first digital asset, the first platform can be sent a request, and the content carried by the request can include the first user information of the first user, the information of the first digital asset, the information of the first operation, and the token list of the first user. Similarly, the first request and the second request in steps 21-22 above can also respectively include the token list of the first user, wherein each token in the token list of the first user corresponds to an operation authorization of a digital asset, so as to send the token list of the first user to the second function module for comparison with the token list of the first digital asset saved by the second function module. In this way, the second function module can compare the token list of the first user with the token list of the first digital asset to determine whether there is a same token between them, obtain the information of the associated operation associated with the same token when there is a same token, and determine whether the first operation matches the associated operation to obtain the checking result. In the case where the first operation belongs to the subset of the associated operation, it is determined that the first operation matches the associated operation, otherwise, it is determined that the first operation does not match the associated operation.

[0213] For example, in the case where the information of the first operation includes the first operation type and the first operation time, if the associated operation also includes the first operation type, and the corresponding second operation time covers the first operation time, it is determined that the first operation belongs to the subset of the associated operation, otherwise, it is determined that the first operation does not belong to the subset of the associated operation.

[0214] For another example, in the case where the information of the first operation only includes the first operation type, if the associated operation also includes the first operation type, and the operation time corresponding to the first operation type is not limited, it is determined that the first operation belongs to the subset of the associated operation, otherwise, it is determined that the first operation does not belong to the subset of the associated operation.

[0215] For example, if the information of the first operation only includes a first operation time, and the information of the associated operation only includes a second operation time, and the first operation time is a subset of the second operation time, it is determined that the first operation belongs to the subset of the associated operation, otherwise, it is determined that the first operation does not belong to the subset of the associated operation.

[0216] In some embodiments of the present application, the first user can apply for the permission of the first operation on the first digital asset to the second function module before step 21. If the permission is granted, the second function module generates a token (referred to as the first token for convenience) for the first digital asset and saves it in the token list of the first digital asset, and associates the first token with the first operation. The second function module also sends the first token to the first user through the first platform, and the first user saves the first token in the token list of the first user after receiving the first token. In this way, the first token is included in the token list of the first user in the first request and the second request in steps 21 and 22. When the second function module performs the above check, it will find that the token list of the first user and the token list of the first digital asset have the same first token.

[0217] In some embodiments of the present application, the first user can apply for the permission of the first operation on the first digital asset to the second function module before step 21. If the permission is granted, the second function module generates a token (referred to as the first token for convenience) for the first digital asset and saves it in the token list of the first digital asset, and associates the first token with the first operation. The second function module also sends the first token to the first user through the first platform, and the first user saves the first token in the token list of the first user after receiving the first token. In this way, the first token is included in the token list of the first user in the first request and the second request in steps 21 and 22. When the second function module performs the above check, it will find that the token list of the first user and the token list of the first digital asset have the same first token.

[0218] As can be seen from the above description, the first token and the second token are the same token.

[0219] As shown in FIG. 3, when the above process 1 is applied to the second function module side, it includes the following steps:

[0220] Step 31, the second function module receives the second request sent by the first function module, and the second request is used to check whether the first user has the permission of the first operation of the first digital asset.

[0221] Here, the second request can include: first user information of the first user and / or information of the first digital asset and / or information of the first operation. The first user information includes a user identifier and / or a token list of the first user; the information of the first digital asset includes a digital asset identifier of the first digital asset; and the information of the first operation includes an operation type and / or an operation time, and the operation type includes one or more of access, update, change, and download.

[0222] Step 32, the second function module checks whether the first user has the permission of the first operation of the first digital asset.

[0223] Step 33, the second function module sends a second response to the first function module, which is used to indicate whether the first user has the permission of the first operation of the first digital asset.

[0224] Through the above steps, the embodiments of the present application check the permission of the first user to the first operation of the first digital asset by the second function mode and feed back the second response, thereby realizing the management and control of the cross-platform operation permission of the digital asset.

[0225] In the embodiments of the present application, the control mode of the digital asset includes a general control mode (which can also be called a first control mode), a relaxed control mode (which can also be called a second control mode), and a strict control mode (a third control mode). Among them, the general control mode means that any operation on the digital asset needs to be authorized by all parties; the relaxed control mode means that any operation on the digital asset does not need to be authorized by all parties; and the strict control mode means that any operation on the digital asset by any user is denied except all parties.

[0226] In step 32, the second function module can check the control mode of the first digital asset:

[0227] (1) In the case where the first digital asset is in the relaxed control mode, step 33 is entered, and at this time the second response is specifically used to indicate that the first user has the permission of the first operation of the first digital asset.

[0228] (2) In the case where the first digital asset is in the strict control mode or the general control mode, the second function module further verifies the permission of the first user to the first operation of the first digital asset:

[0229] If the permission verification succeeds, step 33 is entered, at which time the second response is used to indicate that the first user has the permission of the first operation on the first digital asset;

[0230] If the permission verification fails, the second functional module can also send a third request to the second platform and / or the second terminal, for requesting the permission of the first user on the first operation on the first digital asset; then, the second functional module receives a third response sent by the second platform and / or the second terminal, for indicating whether the first user is allowed to perform the first operation on the first digital asset. In this way, in the case where the third response indicates that the first user is allowed to perform the first operation on the first digital asset, step 33 is entered, at which time the second response is used to indicate that the first user has the permission of the first operation on the first digital asset; and in the case where the third response indicates that the first user is not allowed to perform the first operation on the first digital asset, step 33 is entered, and the second response is used to indicate that the first user does not have the permission of the first operation on the first digital asset.

[0231] Here, the third request can include at least one of the following: first user information, information of the first digital asset, and information of the first operation. The first user information includes a user identifier; the information of the first digital asset includes a digital asset identifier of the first digital asset; and the information of the first operation includes an operation type and / or an operation time, the operation type including one or more of access, update, change, and download.

[0232] Specifically, the second functional module verifies the permission of the first user on the first operation on the first digital asset, which can specifically include: verifying the permission of the first user on the first operation on the first digital asset through an authorization record stored by the second functional module. The authorization record is a record of operation authorization of each digital asset to a user.

[0233] In addition, in the case where the third response indicates that the first user is allowed to perform the first operation on the first digital asset, the second functional module can also store a new authorization record according to the third response, the new authorization record including information of the first digital asset and information of the first operation.

[0234] As described above, the authorization record of the embodiments of the present application can be a token. At this time, the second request includes a token list of the first user, wherein each token in the token list of the first user corresponds to an operation authorization of a digital asset. In this way, in step 32, when the authorization record stored by the second function module is used to verify the authority of the first user to the first operation of the first digital asset, the token list of the first user can be matched with the token list of the first digital asset, wherein each token in the token list of the first digital asset corresponds to an operation authorization of the first digital asset and is associated with the information of an operation. In this way, in the case that there is a same first token between the token list of the first user and the token list of the first digital asset, the information of the second operation associated with the first token is obtained, and in the case that the information of the first operation matches the information of the second operation, it is determined that the authority verification is successful, otherwise, it is determined that the authority verification fails. The judgment method of whether to match can refer to the description above, which will not be described here.

[0235] In the case of using a token as an authorization record, the storage of a new authorization record in the above process specifically includes: the second function module generates a second token, stores it in the token list of the first digital asset, and associates the second token with the information of the first operation. After generating the second token, the second function module can include the second token in the second response, so that the first terminal corresponding to the first user can add the second token to the token list of the first user.

[0236] As shown in FIG. 4, taking the meta-universe business platform as an example, the first function module is a digital asset storage management platform / function module, and the second function module is a digital asset operation authority management platform. The interaction process of the above process 1 between various devices / modules includes:

[0237] Step 101. The user initiates a request for a certain operation or multiple operations on a specific digital asset through the meta-universe business platform, carries digital asset information (such as digital asset identifier), user information (such as user identifier, authority token list), and specific operation (such as access, modification / upgrade, download, etc. of the digital asset), and sends the request to the digital asset storage management platform / function module.

[0238] Step 102. The digital asset storage management platform / function module initiates a query application to the digital asset operation authority management platform / function module to query whether the user has the operation authority applied for on the specific digital asset. The application carries the digital asset identifier and the user authority token list.

[0239] Step 103. The digital asset operation permission management platform / function module determines whether the digital asset has been controlled for operation permission, and if so, determines whether the operation application has been authorized. The judgment includes the platform extracting the permission token list corresponding to the digital asset and verifying the user's carried permission token memory, verifying whether the operation permission corresponding to the permission token passed is included in the user's application permission, and whether the permission token is within the valid period. Determine whether the operation can be performed, if so, jump to step 109, otherwise proceed to the next step.

[0240] Step 104. The digital asset operation permission management platform / function module finds all parties based on the digital asset identifier.

[0241] Step 105. The digital asset operation permission management platform / function module sends a request to inquire about the intention of all parties. The request information includes digital asset information, user information, application operation and operation time.

[0242] Step 106. The business platform obtains user opinions from all parties and informs whether to allow the application of digital asset operation permission.

[0243] Step 107. The business platform feeds back the user intention to the digital asset operation permission management platform / function module.

[0244] Step 108. After verifying the permissions of all parties, the digital asset operation permission management platform / function module records the authorization information of all parties this time, including digital asset identifier, authorized operation, permission token, etc. The permission token generated this time is stored in the permission token list corresponding to the digital asset and the permission information and authorization time limit corresponding to the permission token.

[0245] Step 109. The digital asset operation permission management platform / function module feeds back to the digital asset storage management platform / function module whether the user has operation permission, and if it is the first operation on the digital asset, returns the permission token.

[0246] Step 110. The digital asset storage management platform / function module performs the operation on the digital asset or rejects the operation according to the permission result, and if it is the first operation on the digital asset, returns the permission token.

[0247] Step 111. The digital asset storage management platform / function module feeds back the operation response to the user meta-universe business management platform, and if it is the first operation on the digital asset, provides the permission token, and the user locally stores the permission token.

[0248] Flow 2: Process of a first user applying for permission for a first operation on a first digital asset before initiating a request for the first operation on the first digital asset

[0249] Please refer to FIG. 5-6, the method for controlling the operation permission of the digital asset provided by some embodiments of the present application realizes the relevant permission control in the request process of the first user applying for obtaining the relevant authorization. Wherein, FIG. 5 is a flow chart of the above-mentioned process 2 on the second function module side, and FIG. 6 is an example of the interaction process between various devices / modules of the above-mentioned process 2 taking the meta-universe business platform as an example.

[0250] As shown in FIG. 5, when the above-mentioned process 2 is applied to the second function module side, the following steps are included:

[0251] Step 51, the second function module receives the fourth request sent by the first platform or the first terminal, for applying the permission of the first user to the first operation of the first digital asset.

[0252] Here, when the first user wants to obtain the permission of the first operation of the first digital asset, the fourth request can be sent directly to the second function module, for example, sent through the interface IF4; or the relevant request can be sent to the first platform, and then the fourth request is sent by the first platform through the interface IF4.

[0253] Specifically, the fourth request can include the first user information of the first user and / or the information of the first digital asset and / or the information of the first operation; the first user information includes a user identifier; the information of the first digital asset includes a digital asset identifier of the first digital asset; the information of the first operation includes an operation type and / or an operation time, and the operation type includes one or more of access, update, change, and download.

[0254] Step 52, the second function module determines whether the fourth request needs to obtain the consent and / or authorization of all parties of the first digital asset and / or the second platform and / or the second terminal.

[0255] Step 53, the second function module sends the fifth request to the second platform and / or the second terminal for requesting the permission of the first user to the first operation of the first digital asset, when the fourth request needs to obtain the consent and / or authorization.

[0256] Through the above steps, the embodiments of the present application realize the process of applying for relevant authorization before the operation of the digital asset by the user, thereby realizing the control of the operation permission of the digital asset across platforms.

[0257] After step 53, the second function module can further receive a fifth response sent by the second platform and / or the second terminal, for indicating whether the first operation of the first digital asset by the first user is allowed. For example, in the case that the fifth response indicates that the first operation of the first digital asset by the first user is allowed, the authorization information of all parties and / or the second platform to the first digital asset is recorded and / or stored, and the authorization information includes information of the first digital asset and / or user information and / or information of the first operation. The user information can be user identity information, and the information of the first operation includes operation type and / or operation time, etc.

[0258] In some embodiments, the second function module can further send a fourth response to the first platform or the first terminal, and the fourth response is used for indicating the application result of the permission of the first operation of the first digital asset by the first user, for example, whether the authorization is obtained.

[0259] In step 52, the second function module determines whether the fourth request needs to obtain the consent and / or authorization of all parties of the first digital asset and / or the second platform and / or the second terminal, and the specific manner can include:

[0260] Checking the control mode of the first digital asset:

[0261] In the case that the first digital asset is in the strict control mode, the step of sending the fourth response to the first platform or the first terminal is entered, and the fourth response is used for indicating that the application of the permission of the first operation of the first digital asset by the first user is rejected;

[0262] In the case that the first digital asset is in the general control mode, it is determined that the fourth request needs to obtain the consent and / or authorization of all parties of the first digital asset and / or the second platform and / or the second terminal;

[0263] In the case that the first digital asset is in the loose control mode, it is determined that the fourth request does not need the consent and / or authorization of all parties of the first digital asset and / or the second platform and / or the second terminal, and at this time, the fourth response is sent to the first platform or the first terminal, and the fourth response is used for indicating that the application of the permission of the first operation of the first digital asset by the first user obtains the consent and / or authorization.

[0264] Similarly, in the embodiments of the present application, the authorization information can be in the form of a token. At this time, the authorization information of all parties and / or the second platform to the first digital asset is recorded and / or stored, specifically including: generating a third token, storing it in the token list of the first digital asset, and associating the third token with the information of the first operation. In addition, the second functional module includes the third token in the fourth response when sending the fourth response, so that the first terminal adds the third token to the token list of the first user.

[0265] As can be seen from the above description, the third token, like the first token and the second token described above, is an authorization of the first user to the first operation of the first digital asset.

[0266] As shown in FIG. 6, taking the meta-universe business platform as an example, the first functional module is a digital asset storage management platform / function module, and the second functional module is a digital asset operation permission management platform. The interaction process of the above process 2 between various devices / modules includes:

[0267] Step 201. The user initiates a permission request for a certain operation or multiple operations on a specific digital asset through the meta-universe business platform / permission management client, and the request is sent to the digital asset operation permission management platform / function module. The request carries the digital asset identifier, operation method, and permission duration.

[0268] Step 202. The digital asset operation permission management platform / function module determines whether the operation of the specific asset needs to obtain authorization from all parties. If so, find all parties based on the digital asset identifier; if not, go to step 206.

[0269] Step 203. The digital asset operation permission management platform / function module sends an inquiry to the all parties for their intentions.

[0270] Step 204. The all parties feedback the inquiry through the business platform and inform whether the applicant is allowed to operate the specific digital asset.

[0271] Step 205. The digital asset operation permission management platform / function module records the authorization information of the all parties this time, including the digital asset identifier, the type of operation, the operation time, etc., generates a permission token for the user to operate the digital asset, and stores the permission token in the permission token list corresponding to the digital asset.

[0272] Step 206. The digital asset operation permission management platform / function module feeds back the operation permission application response to the user meta-universe business management platform, informs the application result and sends the permission token. The user stores the received permission token locally.

[0273] Flow 3: Process of setting or updating control mode of digital asset by owner of digital asset

[0274] If the user does not set the control mode when uploading the digital asset, or initiates modification of the control mode after the initial setting, flow 3 can be performed.

[0275] Referring to FIGS. 7-10, the control method of the operation permission of the digital asset provided by some embodiments of the present application realizes the setting or updating of the control mode of the digital asset by the owner of the digital asset. FIG. 7 is a flowchart of flow 3 on the second function module side, and FIG. 8 is a flowchart of flow 3 on the first function module side. Taking the meta-universe business platform as an example, FIGS. 9 and 10 provide two interaction examples of the setting or updating of the control mode of flow 3 between various devices / modules.

[0276] As shown in FIG. 7, when flow 3 is applied to the second function module side, the following steps are included:

[0277] Step 71: The second function module receives the sixth request sent by the third platform and / or the third terminal and / or the first function module, for setting or updating the control mode of the first digital asset.

[0278] Here, the sixth request includes the information of the first digital asset and / or the control mode. The control mode can include three types, which can be referred to in the foregoing, and will not be described here again.

[0279] Step 72: The second function module verifies whether the sixth request is authorized by the owner of the first digital asset and / or the second platform and / or the second terminal. If the verification is successful, the control mode of the first digital asset is set and / or updated and / or stored according to the sixth request, and a sixth response is sent to the third platform and / or the third terminal, for indicating whether the setting or updating of the control mode of the first digital asset is successful.

[0280] Through the above steps, the setting or updating of the control mode of the digital asset is realized by the embodiments of the present application.

[0281] In step 72, if the verification fails, the second function module can send a sixth response to the third platform and / or the third terminal and / or the first function module, and the sixth response is used to indicate that the setting or updating of the control mode of the first digital asset fails.

[0282] As shown in FIG. 8, when flow 3 is applied to the first function module side, the following steps are included:

[0283] Step 81, the first function module receives the seventh request sent by the third platform and / or the third terminal, for setting or updating the control mode of the first digital asset.

[0284] Here, the seventh request includes information of the first digital asset, control mode.

[0285] Step 82, the first function module sends an eighth request to the second function module for setting or updating the control mode of the first digital asset.

[0286] Step 83, the first function module receives the eighth response sent by the second function module, for indicating whether the control mode of the first digital asset is set or updated successfully.

[0287] Step 84, the first function module sends a seventh response to the third platform and / or the third terminal, for indicating whether the control mode of the first digital asset is set or updated successfully.

[0288] As shown in FIG. 9, taking the meta-universe business platform as an example, the second function module is a digital asset operation permission management platform, the third platform is an all-party meta-universe business platform, and the third terminal is a permission management client of an all-party corresponding terminal. The above-mentioned flow 3 sets or updates the control mode of the digital asset, and the interaction process between the devices / modules includes:

[0289] Step 301. The all-party initiates a digital asset control mode setting request or an update request to the digital asset operation permission management platform / module through the meta-universe business platform, and the request includes a digital asset identifier, a control mode of the digital asset operation, etc.

[0290] Step 302. The digital asset operation permission management platform / module verifies whether the all-party has the permission of setting or updating. If yes, go to step 3, otherwise go to step 304.

[0291] Step 303. The digital asset operation permission management platform / module stores the latest setting or the latest update of the control mode of the digital asset by the all-party.

[0292] Step 304. The digital asset operation permission management platform / module returns the result of the control mode setting or updating to the meta-universe business platform.

[0293] As shown in FIG. 10, the example includes steps 401-406, which is different from FIG. 9, the platform of the all-party (the meta-universe business platform) or the permission management client in the terminal corresponding to the all-party in FIG. 10 forwards the setting or updating request of the control mode via the first function module (the digital asset storage management module / function module).

[0294] Flow 4: Control mode setting in the digital asset registration process

[0295] The digital asset of each platform needs to be registered to the first function module. During the registration process, the second function module can set the control mode of the digital asset and generate relevant authorization records (such as permission tokens) for all parties of the digital asset.

[0296] Please refer to FIGS. 11-14. The operation permission control method of the digital asset provided by some embodiments of the present application realizes the setting of the control mode during the registration process of the digital asset. FIG. 11 is a flowchart of the above-mentioned flow 4 on the second function module side, and FIG. 12 is a flowchart of the above-mentioned flow 4 on the first function module side. Taking the meta-universe business platform as an example, FIG. 13 provides two interaction examples between each device / module in the above-mentioned flow 4.

[0297] As shown in FIG. 11, when the above-mentioned flow 4 is applied to the second function module side, the following steps are included:

[0298] Step 1101: The second function module receives the first information sent by the first function module, wherein the first information includes the information of the first digital asset and / or the information of the all parties of the first digital asset and / or the information of the second platform.

[0299] Here, the information of the first digital asset includes the digital asset identifier of the first digital asset; the information of the all parties of the first digital asset includes the all-party identifier; and the information of the second platform includes at least one of the platform IP address, the platform identifier, and the platform calling interface.

[0300] Step 1102: The second function module sends a ninth request to the first function module, for requesting the all parties of the first digital asset and / or the second platform and / or the second terminal to set the control mode of the first digital asset.

[0301] Step 1103: The second function module receives the ninth response sent by the first function module, for indicating the control mode of the first digital asset.

[0302] Here, the ninth response can include the information of the first digital asset and / or the control mode.

[0303] Step 1104: The second function module sets and / or stores the control mode of the first digital asset according to the ninth response.

[0304] Through the above steps, the second function module side realizes the setting of the control mode of the first digital asset during the registration of the digital asset to the first function module.

[0305] Optionally, the second function module can further send fourth information to the first function module, for indicating a setting result of the control mode of the first digital asset.

[0306] In addition, when a token is used as the permission, the second function module can create a token list for the first digital asset, generate a fourth token of all parties of the first digital asset, associate the fourth token with the third operation information, and save the fourth token in the token list of the first digital asset. In some embodiments, the fourth token can be included in the fourth information when the fourth information is sent. It should be noted that the first, second and third tokens in the foregoing are user tokens, and the fourth token in the present process is an all-party token, but these tokens can be the same or similar in format and function. Compared with the first, second and third tokens, the fourth token can have a wider permission.

[0307] As shown in FIG. 12, when the above-mentioned process 4 is applied to the first function module side, the following steps are included:

[0308] Step 1201, the first function module sends first information to the second function module, the first information including information of the first digital asset and / or all-party information of the first digital asset and / or second platform information.

[0309] Here, the information of the first digital asset includes a digital asset identifier of the first digital asset; the all-party information of the first digital asset includes an all-party identifier; and the second platform information includes at least one of a platform IP address, a platform identifier and a platform calling interface.

[0310] Step 1202, the first function module receives a ninth request sent by the second function module, for requesting to set the control mode of the first digital asset.

[0311] Step 1203, the first function module sends a tenth request to the second platform and / or the second terminal, for requesting to set the control mode of the first digital asset.

[0312] Step 1204, the first function module receives a tenth response sent by the second platform and / or the second terminal, for indicating the control mode of the first digital asset.

[0313] Here, the tenth response is a response to the tenth request, and specifically, the tenth response can include: information of the first digital asset and / or the control mode.

[0314] Step 1205, the first function module sends a ninth response to the second function module, for indicating the control mode of the first digital asset.

[0315] Through the above steps, the second function module can set the control mode of the digital asset in the digital asset registration process.

[0316] In some embodiments, in the above method, the first function module can further receive fourth information sent by the second function module, for indicating the setting result of the control mode of the first digital asset. The first function module can further send fifth information to the second platform or the second terminal, the fifth information including the setting result of the control mode of the first digital asset.

[0317] Specifically, the fourth information can further include a fourth token, and the first function module further includes the fourth token in the fifth information, so that the second terminal saves the fourth token in a token list of the owner of the first digital asset.

[0318] As shown in FIG. 13, taking the meta-universe business platform as an example, the second function module is a digital asset operation permission management platform, and the first function module is a digital asset storage management platform / function module. The above process 4 updates the control mode of the digital asset, and the interaction process between various devices / modules includes:

[0319] Step 501. The owner initiates a request for registration of digital asset information and uploading of a digital asset file through the meta-universe business platform, and the request carries digital asset related information (such as digital asset identifier, digital asset attribute, digital asset use terms, etc.), owner related information (such as owner identifier), and the digital asset file.

[0320] Step 502. The digital asset storage management platform / module stores the digital asset file and the digital asset information and the owner information.

[0321] Step 503. The digital asset storage management platform / function module forwards the digital asset registration information to the digital asset operation management platform / function module, including the digital asset information and the owner information.

[0322] Step 504. The digital asset operation management platform / function module stores the digital asset basic information, and initiates a control mode setting request for digital asset operation to the digital asset storage management platform / module.

[0323] Step 505. The digital asset storage management platform / module forwards the request for setting the control mode of the digital asset operation.

[0324] Step 506. The metaverse business platform sends the control mode of the digital asset operation set by the owner, including the digital asset identifier and the control mode information (strict control, general control, and relaxed control. Strict control is used for private use, and others are not allowed to operate the digital asset; general control is allowed for some people to use, and whether others need to seek the authorization intention of the owner before operation; relaxed control is public use, and is open to all people to operate the digital asset, etc.).

[0325] Step 507. The digital asset storage management platform / module forwards the control mode setting information of the digital asset operation to the digital asset operation permission control platform / module.

[0326] Step 508. The operation permission control platform / module stores the setting of the operation permission of the digital asset by all parties. The permission token list is generated for the newly registered digital asset, the operation permission of the digital asset by all parties is generated, the permission token is stored in the permission token list corresponding to the digital asset.

[0327] Step 509. The operation permission control platform / module returns the response of the control mode setting of the digital asset operation to the digital asset storage management platform / module, carries the setting success or failure result and the permission token after the setting is successful.

[0328] Step 510. The digital asset storage management platform / module returns the digital asset registration response to the metaverse business platform, carries the asset registration result, and the permission token after the setting is successful.

[0329] As can be seen from the above various embodiments, the embodiments of the present application provide a system and method for cross-platform digital asset collaboration and sharing, realizing the control of the operation permission of the cross-platform digital asset. When applied to the metaverse scene, the embodiments of the present application can provide a cross-platform digital asset collaboration and sharing solution for each metaverse user, meeting the demand of anonymous free travel in each metaverse business platform and realizing the sharing and collaborative operation of the same digital asset in the metaverse world.

[0330] The above introduces various methods of the embodiments of the present application. The following will further provide a device for implementing the above method.

[0331] Please refer to FIG. 14, the embodiments of the present application also provide a first function module, comprising:

[0332] The first receiving module 141 is configured to receive the first request sent by the first platform, and the first request is used to request the first user to perform the first operation on the first digital asset.

[0333] The first sending module 142 is configured to send a second request to a second function module, and the second request is used to check whether the first user has the permission of the first operation on the first digital asset.

[0334] The second receiving module 143 is configured to receive a second response sent by the second function module, the second response being used to indicate whether the first user has the permission of the first operation of the first digital asset.

[0335] The second sending module 144 is configured to send a first response to the first platform, the first response being used to indicate the result of the first operation of the first digital asset.

[0336] Optionally, the first request comprises first user information of the first user, information of the first digital asset, and information of the first operation.

[0337] Optionally, the first user information comprises a user identifier and / or a token list of the first user.

[0338] The information of the first digital asset comprises a digital asset identifier of the first digital asset.

[0339] The information of the first operation comprises an operation type and / or an operation time, and the operation type comprises one or more of access, update, change, and download.

[0340] Optionally, the first request and the second request further comprise a token list of the first user respectively, wherein each token in the token list of the first user corresponds to an operation authorization of a digital asset.

[0341] Optionally, the second sending module is further configured to, in the case that the second response comprises a second token, include the second token in the first response sent to the first platform, so that the first terminal corresponding to the first user adds the second token to the token list of the first user.

[0342] Referring to FIG. 15, the embodiment of the present application further provides a second function module, comprising:

[0343] The first receiving module 151 is configured to receive a second request sent by a first function module, the second request being used to check whether the first user has the permission of the first operation of the first digital asset.

[0344] The checking module 152 is configured to check whether the first user has the permission of the first operation of the first digital asset.

[0345] The first sending module 153 is configured to send a second response to the first function module, the second response being used to indicate whether the first user has the permission of the first operation of the first digital asset.

[0346] Optionally, the second request comprises: first user information of the first user and / or information of the first digital asset and / or information of the first operation.

[0347] Optionally, the first user information comprises a user identifier and / or a token list of the first user.

[0348] The information of the first digital asset comprises a digital asset identifier of the first digital asset.

[0349] The information of the first operation comprises an operation type and / or an operation time, and the operation type comprises one or more of access, update, change, and download.

[0350] Optionally, the verification module is further configured to:

[0351] verify a control mode of the first digital asset.

[0352] In a case where the first digital asset is in a relaxed control mode, the second functional module sends a second response to the first functional module, and the second response is used to indicate that the first user has the right to perform the first operation on the first digital asset.

[0353] Optionally, the verification module is further configured to:

[0354] In a case where the first digital asset is in a strict control mode or a general control mode, the verification module verifies the right of the first user to perform the first operation on the first digital asset, and in a case where the right verification is successful, the second functional module sends a second response to the first functional module, and the second response is used to indicate that the first user has the right to perform the first operation on the first digital asset.

[0355] Optionally, the verification module is further configured to:

[0356] The verification module verifies the right of the first user to perform the first operation on the first digital asset by using an authorization record stored in the second functional module.

[0357] Optionally, the verification module is further configured to:

[0358] In a case where the right verification fails, the second functional module sends a third request to a second platform and / or a second terminal, and the third request is used to request the right of the first user to perform the first operation on the first digital asset.

[0359] The second functional module receives a third response sent by the second platform and / or the second terminal, and the third response is used to indicate whether the first user is allowed to perform the first operation on the first digital asset.

[0360] Optionally, the method further comprises:

[0361] The first processing module is configured to, in a case where the third response indicates that the first user is allowed to perform the first operation on the first digital asset, enter the second functional module to send a second response to the first functional module, and the second response is used to indicate that the first user has the right to perform the first operation on the first digital asset.

[0362] The second processing module is configured to, in a case where the third response indicates that the first user is not allowed to perform the first operation on the first digital asset, enter the second functional module to send a second response to the first functional module, and the second response is used to indicate that the first user does not have the right to perform the first operation on the first digital asset.

[0363] Optionally, the third request includes: first user information and / or first digital asset information and / or first operation information.

[0364] The first user information includes a user identifier.

[0365] The first digital asset information includes a digital asset identifier of the first digital asset.

[0366] The first operation information includes an operation type and / or an operation time, and the operation type includes one or more of access, update, change, and download.

[0367] Optionally, the first processing module is further configured to, in a case where the third response indicates that the first user is allowed to perform the first operation on the first digital asset, store a new authorization record according to the third response, and the new authorization record includes the first digital asset information and the first operation information.

[0368] Optionally, the second request includes a token list of the first user, wherein each token in the token list of the first user corresponds to an operation authorization of a digital asset.

[0369] The checking module is further configured to match the token list of the first user with a token list of the first digital asset, wherein each token in the token list of the first digital asset corresponds to an operation authorization of the first digital asset and is associated with operation information.

[0370] In a case where there is a same first token between the token list of the first user and the token list of the first digital asset, the second operation information associated with the first token is obtained, and in a case where the first operation information matches the second operation information, it is determined that the right verification is successful, otherwise, it is determined that the right verification fails.

[0371] Optionally, the first processing module is further configured to generate a second token, store the second token in a token list of the first digital asset, and associate the second token with information of the first operation.

[0372] Optionally, the second response includes the second token, so that the first terminal corresponding to the first user adds the second token to a token list of the first user.

[0373] Referring to FIG. 16, the embodiment of the present application further provides a second function module, comprising:

[0374] The first receiving module 161 is configured to receive a fourth request sent by the first platform or the first terminal, and the fourth request is used to apply for a permission of a first operation of a first user on a first digital asset.

[0375] The determining module 162 is configured to determine whether the fourth request needs to obtain consent and / or authorization of all parties of the first digital asset and / or a second platform and / or a second terminal.

[0376] The first sending module 163 is configured to send a fifth request to the second platform and / or the second terminal in a case where the fourth request needs to obtain consent and / or authorization, and the fifth request is used to request the permission of the first operation of the first user on the first digital asset.

[0377] Optionally, the fourth request includes first user information and / or information of the first digital asset and / or information of the first operation.

[0378] The first user information includes a user identifier, the information of the first digital asset includes a digital asset identifier of the first digital asset, and the information of the first operation includes an operation type and / or an operation time, and the operation type includes one or more of access, update, change and download.

[0379] Optionally, the embodiment further comprises:

[0380] The second receiving module is configured to receive a fifth response sent by the second platform and / or the second terminal, and the fifth response is used to indicate whether the first operation of the first user on the first digital asset is allowed.

[0381] Optionally, the embodiment further comprises:

[0382] The first processing module is configured to record and / or store authorization information of all parties and / or the second platform on the first digital asset in a case where the fifth response indicates that the first operation of the first user on the first digital asset is allowed, and the authorization information includes information of the first digital asset and / or user information and / or information of the first operation.

[0383] Optionally, the embodiment further comprises:

[0384] a second sending module, configured to send a fourth response to the first platform or the first terminal, the fourth response being used to indicate an application result of the right of the first user to the first operation of the first digital asset.

[0385] Optionally, the determining module is further configured to:

[0386] check a control mode of the first digital asset;

[0387] in a case where the first digital asset is in the strict control mode, entering the step of sending the fourth response to the first platform or the first terminal, and the fourth response is used to indicate that the application of the right of the first user to the first operation of the first digital asset is rejected;

[0388] in a case where the first digital asset is in the general control mode, determining that the fourth request needs to obtain the consent and / or authorization of all parties of the first digital asset and / or the second platform and / or the second terminal;

[0389] in a case where the first digital asset is in the loose control mode, determining that the fourth request does not need the consent and / or authorization of all parties of the first digital asset and / or the second platform and / or the second terminal, entering the step of sending the fourth response to the first platform or the first terminal, and the fourth response is used to indicate that the application of the right of the first user to the first operation of the first digital asset obtains the consent and / or authorization.

[0390] Optionally, the first processing module is further configured to: generate a third token, store the third token in a token list of the first digital asset, and associate the third token with information of the first operation;

[0391] the fourth response includes the third token, so that the first terminal adds the third token to a token list of the first user.

[0392] Please refer to FIG. 17, the embodiment of the application further provides a second function module, comprising:

[0393] a first receiving module 171, configured to receive a sixth request sent by a third platform and / or a third terminal and / or a first function module, the sixth request being used to set or update a control mode of the first digital asset;

[0394] The first processing module 172 is configured to verify whether the sixth request is authorized by the owner of the first digital asset and / or the second platform and / or the second terminal, and in the case of successful verification, set and / or update and / or store the control mode of the first digital asset according to the sixth request, and send a sixth response to the third platform and / or the third terminal, to indicate whether the control mode of the first digital asset is successfully set or updated.

[0395] Optionally, the sixth request comprises information of the first digital asset and / or the control mode.

[0396] Optionally, the first function module further comprises:

[0397] The first sending module is configured to, in the case of failed verification, send a sixth response to the third platform and / or the third terminal first function module, and the sixth response is used to indicate that the control mode of the first digital asset fails to be set or updated.

[0398] Please refer to FIG. 18, the embodiment of the present application further provides a first function module, comprising:

[0399] The first receiving module 181 is configured to receive a seventh request sent by the third platform and / or the third terminal, to set or update the control mode of the first digital asset;

[0400] The first sending module 182 is configured to send an eighth request to the second function module, to set or update the control mode of the first digital asset;

[0401] The second receiving module 183 is configured to receive an eighth response sent by the second function module, to indicate whether the control mode of the first digital asset is successfully set or updated;

[0402] The second sending module 184 is configured to send a seventh response to the third platform and / or the third terminal, to indicate whether the control mode of the first digital asset is successfully set or updated.

[0403] Optionally, the seventh request comprises information of the first digital asset, the control mode.

[0404] Please refer to FIG. 19, the embodiment of the present application further provides a second function module, comprising:

[0405] The first receiving module 191 is configured to receive first information sent by the first function module, and the first information comprises information of the first digital asset and / or owner information of the first digital asset and / or second platform information;

[0406] The first sending module 192 is configured to send a ninth request to the first function module, and the ninth request is used to request a control mode of the first digital asset from an owner of the first digital asset and / or a second platform and / or a second terminal.

[0407] The second receiving module 193 is configured to receive a ninth response sent by the first function module, and the ninth response is used to indicate the control mode of the first digital asset.

[0408] The first processing module 194 is configured to set and / or store the control mode of the first digital asset according to the ninth response.

[0409] Optionally, the information of the first digital asset comprises a digital asset identifier of the first digital asset; the owner information of the first digital asset comprises an owner identifier; and the information of the second platform comprises at least one of a platform IP address, a platform identifier and a platform calling interface.

[0410] Optionally, the ninth response comprises the information of the first digital asset and / or the control mode.

[0411] Optionally, the method further comprises:

[0412] The second sending module is configured to send fourth information to the first function module, and the fourth information is used to indicate a setting result of the control mode of the first digital asset.

[0413] Optionally, the method further comprises:

[0414] The first processing module is configured to create a token list for the first digital asset, generate a fourth token of the owner of the first digital asset, associate the fourth token with third operation information, and save the fourth token in the token list of the first digital asset.

[0415] The fourth information further comprises the fourth token.

[0416] Please refer to FIG. 20, and the embodiment of the application further provides a first function module, comprising:

[0417] The first sending module 2001 is configured to send first information to a second function module, and the first information comprises information of a first digital asset and / or owner information of the first digital asset and / or information of a second platform.

[0418] The first receiving module 2002 is configured to receive a ninth request sent by the second function module, and the ninth request is used to request a control mode of the first digital asset.

[0419] The second sending module 2003 is configured to send a tenth request to a second platform and / or a second terminal, and the tenth request is used to request a control mode of the first digital asset.

[0420] The second receiving module 2004 is configured to receive a tenth response sent by the second platform and / or the second terminal, the tenth response being used to indicate the control mode of the first digital asset.

[0421] The third sending module 2005 is configured to send a ninth response to the second functional module, the ninth response being used to indicate the control mode of the first digital asset.

[0422] Optionally, the information of the first digital asset comprises a digital asset identifier of the first digital asset; the information of the owner of the first digital asset comprises an owner identifier; and the information of the second platform comprises at least one of a platform IP address, a platform identifier and a platform calling interface.

[0423] Optionally, the tenth response comprises the information of the first digital asset and / or the control mode.

[0424] Optionally, the method further comprises:

[0425] The third receiving module is configured to receive fourth information sent by the second functional module, the fourth information being used to indicate a setting result of the control mode of the first digital asset.

[0426] The fourth sending module is configured to send fifth information to the second platform or the second terminal, the fifth information comprising the setting result of the control mode of the first digital asset.

[0427] Optionally, the fourth information further comprises a fourth token, and the fifth information further comprises the fourth token, so that the second terminal saves the fourth token in a token list of the owner of the first digital asset.

[0428] It should be noted that the device in the above embodiment is a device corresponding to the method applied to the first functional module or the second functional module, and the implementation manners in the above embodiments are applicable to the embodiments of the device and can achieve the same technical effects. The device provided in the embodiments of the present application can implement all the method steps achieved by the method embodiments and achieve the same technical effects. Therefore, the same parts and beneficial effects in the method embodiments will not be described in detail.

[0429] The first function module or the second function module of another embodiment of the present application, as shown in FIG. 21, includes a transceiver 2110, a processor 2100, a memory 2120, and a program or instruction stored in the memory 2120 and executable on the processor 2100; the processor 2100 implements each process of the operation permission control method embodiment of the digital asset of the first function module or the second function module described above when executing the program or instruction, and achieves the same technical effects. To avoid repetition, details are not described here.

[0430] The transceiver 2110 is configured to receive and send data under the control of the processor 2100.

[0431] In FIG. 21, the bus architecture can include any number of interconnected buses and bridges, which are specifically linked together by various circuits of one or more processors represented by the processor 2100 and the memory represented by the memory 2120. The bus architecture can also link various other circuits such as peripheral devices, voltage stabilizers, and power management circuits, which are well known in the art, and thus, further description is not provided herein. The bus interface provides an interface. The transceiver 2110 can be a plurality of elements, that is, includes a transmitter and a receiver, and provides a unit for communicating with various other devices on a transmission medium. The processor 2100 is responsible for managing the bus architecture and general processing, and the memory 2120 can store data used by the processor 2100 when performing operations.

[0432] The embodiment of the present application also provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement each process of the operation permission control method embodiment of the digital asset and achieve the same technical effects. To avoid repetition, details are not described here. The computer readable storage medium is, for example, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, etc.

[0433] The embodiment of the present application also provides a computer program product, which includes computer instructions, and the computer instructions are executed by a processor to implement each process of the operation permission control method embodiment of the digital asset and achieve the same technical effects. To avoid repetition, details are not described here.

[0434] It should be noted that, in this text, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. Without more limitations, the element defined by the statement "including a" does not exclude the presence of other identical elements in the process, method, article or device including the element. Through the description of the above embodiments, those skilled in the art can clearly understand that the above example method can be realized by software and the necessary general hardware platform, of course, it can also be realized by hardware, but in many cases the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), including a plurality of instructions for making a terminal (which can be a mobile phone, computer, server, air conditioner, or network equipment, etc.) execute the method described in each embodiment of the present application. The embodiments of the present application are described above in conjunction with the drawings, but the present application is not limited to the above specific embodiments, the above specific embodiments are only illustrative, not restrictive, those skilled in the art can make many forms under the inspiration of the present application without departing from the scope of the present application and the protection scope of the claims.

Claims

1. A method for controlling operation permission of a digital asset, comprising: receiving, by a first function module, a first request sent by a first platform, the first request being used to request a first user to perform a first operation on a first digital asset; sending, by the first function module, a second request to a second function module, the second request being used to check whether the first user has permission to perform the first operation on the first digital asset; receiving, by the first function module, a second response sent by the second function module, the second response being used to indicate whether the first user has permission to perform the first operation on the first digital asset; sending, by the first function module, a first response to the first platform, the first response being used to indicate a result of the first operation on the first digital asset. 2.The method of claim 1, wherein: the first request comprises first user information of the first user, information of the first digital asset, and information of the first operation. 3.The method of claim 2, wherein: the first user information comprises a user identifier and / or a token list of the first user; the information of the first digital asset comprises a digital asset identifier of the first digital asset; the information of the first operation comprises an operation type and / or an operation time, the operation type comprising one or more of access, update, change, and download.

4. The method of claim 2, wherein, the first request and the second request each further comprises a token list of the first user, wherein each token in the token list of the first user corresponds to an operation authorization of a digital asset.

5. The method of claim 4, wherein, in a case where the second response comprises a second token, the second token is included in the first response sent to the first platform, so as to be added to the token list of the first user by a first terminal corresponding to the first user. 6.A method for controlling operation permission of a digital asset, comprising: receiving, by a second function module, a second request sent by a first function module, the second request being used to check whether a first user has permission to perform a first operation on a first digital asset; checking, by the second function module, whether the first user has permission to perform the first operation on the first digital asset; sending, by the second function module, a second response to the first function module, the second response being used to indicate whether the first user has permission to perform the first operation on the first digital asset. 7.The method of claim 6, wherein: the second request comprises first user information of the first user and / or information of the first digital asset and / or information of the first operation. 8.The method of claim 7, wherein: the first user information comprises a user identifier and / or a token list of the first user; the information of the first digital asset comprises a digital asset identifier of the first digital asset; the information of the first operation comprises an operation type and / or an operation time, the operation type comprising one or more of access, update, change, and download.

9. The method of claim 6, wherein, checking, by the second function module, whether the first user has permission to perform the first operation on the first digital asset, comprises: checking, by the second function module, a control mode of the first digital asset; In a case that the first digital asset is in a relaxed control mode, the second function module sends a second response to the first function module, and the second response is used to indicate that the first user has the permission of the first operation of the first digital asset.

10. The method of claim 6, wherein, The second function module checks whether the first user has the permission of the first operation of the first digital asset, and the checking further includes: In a case that the first digital asset is in a strict control mode or a general control mode, the permission of the first operation of the first digital asset by the first user is verified, and in a case that the permission verification is successful, the second function module sends a second response to the first function module, and the second response is used to indicate that the first user has the permission of the first operation of the first digital asset.

11. The method of claim 10, wherein, The permission of the first operation of the first digital asset by the first user is verified, including: verifying the permission of the first operation of the first digital asset by the first user through an authorization record stored by the second function module.

12. The method of claim 10, wherein, The second function module checks whether the first user has the permission of the first operation of the first digital asset, and the checking further includes: In a case that the permission verification fails, the second function module sends a third request to a second platform and / or a second terminal, and the third request is used to request the permission of the first operation of the first digital asset by the first user. The second function module receives a third response sent by the second platform and / or the second terminal, and the third response is used to indicate whether the first user is allowed to perform the first operation on the first digital asset.

13. The method of claim 12, wherein, Further including: In a case that the third response indicates that the first user is allowed to perform the first operation on the first digital asset, the second function module sends a second response to the first function module, and the second response is used to indicate that the first user has the permission of the first operation of the first digital asset; In a case that the third response indicates that the first user is not allowed to perform the first operation on the first digital asset, the second function module sends a second response to the first function module, and the second response is used to indicate that the first user does not have the permission of the first operation of the first digital asset.

14. The method of claim 12, wherein, The third request includes: first user information and / or information of the first digital asset and / or information of the first operation; The first user information includes a user identifier; The information of the first digital asset includes a digital asset identifier of the first digital asset; The information of the first operation includes an operation type and / or an operation time, and the operation type includes one or more of access, update, change, and download.

15. The method of claim 13, wherein, Further including: In a case that the third response indicates that the first user is allowed to perform the first operation on the first digital asset, a new authorization record is stored according to the third response, and the new authorization record includes the information of the first digital asset and the information of the first operation.

16. The method of claim 15, wherein, The second request includes a token list of the first user, wherein each token in the token list of the first user corresponds to an operation authorization of a digital asset; The second functional module verifies the permission of the first user to the first operation of the first digital asset by the authorization record stored by the second functional module, including matching the token list of the first user with a token list of the first digital asset, wherein each token in the token list of the first digital asset corresponds to an operation authorization of the first digital asset and is associated with information of an operation; In the case that there is a same first token between the token list of the first user and the token list of the first digital asset, the information of the second operation associated with the first token is obtained, and in the case that the information of the first operation matches the information of the second operation, it is determined that the permission verification is successful, otherwise, it is determined that the permission verification fails.

17. The method of claim 16, wherein, The storage of the new authorization record specifically includes generating a second token, storing the second token in the token list of the first digital asset, and associating the second token with the information of the first operation.

18. The method of claim 17, wherein, Further comprising: The second response includes the second token, so that the first terminal corresponding to the first user adds the second token to the token list of the first user.

19. A method for controlling operation permission of a digital asset, comprising: A second functional module receives a fourth request sent by a first platform or a first terminal, for applying for permission of a first user to a first operation of a first digital asset; The second functional module determines whether the fourth request needs to obtain consent and / or authorization of all parties of the first digital asset and / or a second platform and / or a second terminal; The second functional module sends a fifth request to the second platform and / or the second terminal for requesting permission of the first user to the first operation of the first digital asset, in the case that the fourth request needs to obtain consent and / or authorization.

20. The method of claim 19, wherein, The fourth request includes first user information and / or information of the first digital asset and / or information of the first operation; The first user information includes a user identifier; the information of the first digital asset includes a digital asset identifier of the first digital asset; and the information of the first operation includes an operation type and / or an operation time, and the operation type includes one or more of access, update, change, and download.

21. The method of claim 19, wherein, Further comprising: The second functional module receives a fifth response sent by the second platform and / or the second terminal, for indicating whether the first user is allowed to perform the first operation on the first digital asset.

22. The method of claim 21, wherein, Further comprising: In the case that the fifth response indicates that the first user is allowed to perform the first operation on the first digital asset, authorization information of all parties and / or the second platform to the first digital asset is recorded and / or stored, and the authorization information includes information of the first digital asset and / or user information and / or information of the first operation.

23. The method of claim 22, wherein, Further comprising: sending a fourth response to the first platform or the first terminal, the fourth response being used to indicate an application result of the first user's right to the first operation on the first digital asset.

24. The method of claim 23, wherein, The second function module determines whether the fourth request needs to obtain the consent and / or authorization of all parties of the first digital asset and / or the second platform and / or the second terminal, comprising: The second function module checks the control mode of the first digital asset; In the case that the first digital asset is in the strict control mode, the step of sending the fourth response to the first platform or the first terminal is entered, and the fourth response is used to indicate that the application of the first user's right to the first operation on the first digital asset is rejected; In the case that the first digital asset is in the general control mode, it is determined that the fourth request needs to obtain the consent and / or authorization of all parties of the first digital asset and / or the second platform and / or the second terminal; In the case that the first digital asset is in the loose control mode, it is determined that the fourth request does not need the consent and / or authorization of all parties of the first digital asset and / or the second platform and / or the second terminal, and the step of sending the fourth response to the first platform or the first terminal is entered, and the fourth response is used to indicate that the application of the first user's right to the first operation on the first digital asset obtains the consent and / or authorization.

25. The method of claim 23, wherein, The recordation and / or storage of the authorization information of all parties and / or the second platform on the first digital asset specifically comprises: generating a third token, storing the third token in a token list of the first digital asset, and associating the third token with information of the first operation; The fourth response comprises the third token, so that the first terminal adds the third token to a token list of the first user.

26. A control method of operation right of a digital asset, comprising: A second function module receives a sixth request sent by a third platform and / or a third terminal and / or a first function module, which is used to set or update a control mode of a first digital asset; The second function module verifies whether the sixth request obtains authorization of all parties of the first digital asset and / or the second platform and / or the second terminal, and in the case of successful verification, sets and / or updates and / or stores the control mode of the first digital asset according to the sixth request, and sends a sixth response to the third platform and / or the third terminal, which is used to indicate whether the control mode of the first digital asset is successfully set or updated.

27. The method of claim 26, wherein, Further comprising: The sixth request comprises information and / or the control mode of the first digital asset.

28. The method of claim 26, wherein, Further comprising: In the case of failed verification, a sixth response is sent to the third platform and / or the third terminal and / or the first function module, and the sixth response is used to indicate that the control mode of the first digital asset fails to be set or updated.

29. A control method of operation right of a digital asset, comprising: A first function module receives a seventh request sent by a third platform and / or a third terminal, which is used to set or update a control mode of a first digital asset; The first function module sends an eighth request to the second function module, for setting or updating the control mode of the first digital asset; The first function module receives an eighth response sent by the second function module, for indicating whether the control mode of the first digital asset is set or updated successfully; The first function module sends a seventh response to the third platform and / or the third terminal, for indicating whether the control mode of the first digital asset is set or updated successfully.

30. The method of claim 29, wherein, Further comprising: The seventh request comprises information of the first digital asset and the control mode.

31. A control method of operation authority of a digital asset, comprising: The second function module receives first information sent by the first function module, the first information comprising information of the first digital asset and / or owner information of the first digital asset and / or second platform information; The second function module sends a ninth request to the first function module, for requesting the owner of the first digital asset and / or the second platform and / or the second terminal to set the control mode of the first digital asset; The second function module receives a ninth response sent by the first function module, for indicating the control mode of the first digital asset; The second function module sets and / or stores the control mode of the first digital asset according to the ninth response.

32. The method of claim 31, wherein, The information of the first digital asset comprises a digital asset identifier of the first digital asset; the owner information of the first digital asset comprises an owner identifier; and the information of the second platform comprises at least one of a platform IP address, a platform identifier and a platform calling interface.

33. The method of claim 31, wherein, The ninth response comprises the information of the first digital asset and / or the control mode.

34. The method of claim 31, wherein, Further comprising: The second function module sends fourth information to the first function module, for indicating a setting result of the control mode of the first digital asset.

35. The method of claim 34, wherein, Further comprising: The second function module creates a token list for the first digital asset, generates a fourth token of the owner of the first digital asset, associates the fourth token with third operation information, and saves the fourth token in the token list of the first digital asset; The fourth information further comprises the fourth token.

36. A control method of operation authority of a digital asset, comprising: The first function module sends first information to the second function module, the first information comprising information of a first digital asset and / or owner information of the first digital asset and / or second platform information; The first function module receives a ninth request sent by the second function module, for requesting to set a control mode of the first digital asset; The first function module sends a tenth request to a second platform and / or a second terminal, for requesting to set the control mode of the first digital asset; The first function module receives a tenth response sent by the second platform and / or the second terminal, for indicating the control mode of the first digital asset; The first function module sends a ninth response to the second function module, for indicating the control mode of the first digital asset.

37. The method of claim 36, wherein, The information of the first digital asset includes a digital asset identifier of the first digital asset; the information of the first digital asset owner includes an owner identifier; and the information of the second platform includes at least one of a platform IP address, a platform identifier, and a platform calling interface.

38. The method of claim 36, wherein, The tenth response includes information of the first digital asset and / or a control mode.

39. The method of claim 38, wherein, Further comprising: The fourth information further includes a fourth token, and the first functional module further includes the fourth token in the fifth information, so that the second terminal saves the fourth token in a token list of the owner of the first digital asset. The fourth information further includes a fourth token, and the first functional module further includes the fourth token in the fifth information, so that the second terminal saves the fourth token in a token list of the owner of the first digital asset.

40. The method of claim 39, wherein, 41. A first functional module, comprising: a first receiving module configured to receive a first request sent by a first platform, the first request being used to request a first user to perform a first operation on a first digital asset; a first sending module configured to send a second request to a second functional module, the second request being used to check whether the first user has a right to perform the first operation on the first digital asset; a second receiving module configured to receive a second response sent by the second functional module, the second response being used to indicate whether the first user has the right to perform the first operation on the first digital asset; a second sending module configured to send a first response to the first platform, the first response being used to indicate a result of the first operation on the first digital asset.

42. A second functional module, comprising: a first receiving module configured to receive a second request sent by a first functional module, the second request being used to check whether a first user has a right to perform a first operation on a first digital asset; a checking module configured to check whether the first user has the right to perform the first operation on the first digital asset; a first sending module configured to send a second response to the first functional module, the second response being used to indicate whether the first user has the right to perform the first operation on the first digital asset.

43. A second functional module, comprising: a first receiving module configured to receive a fourth request sent by a first platform or a first terminal, the fourth request being used to apply for a right of a first user to perform a first operation on a first digital asset; a determining module configured to determine whether the fourth request needs to obtain an agreement and / or an authorization of an owner of the first digital asset and / or a second platform and / or a second terminal; a first sending module configured to send a fifth request to the second platform and / or the second terminal, the fifth request being used to request the right of the first user to perform the first operation on the first digital asset, when the fourth request needs to obtain the agreement and / or the authorization.

44. A second functional module, comprising: a first receiving module configured to receive a sixth request sent by a third platform and / or a third terminal and / or a first functional module, the sixth request being used to set or update a control mode of a first digital asset; ​ The first processing module is configured to verify whether the sixth request is authorized by the owner of the first digital asset and / or the second platform and / or the second terminal, and in the case of successful verification, set and / or update and / or store the control mode of the first digital asset according to the sixth request, and send a sixth response to the third platform and / or the third terminal, indicating whether the control mode of the first digital asset is successfully set or updated.

45. A first function module, comprising: a first receiving module configured to receive a seventh request sent by a third platform and / or a third terminal, for setting or updating a control mode of a first digital asset; a first sending module configured to send an eighth request to a second function module, for setting or updating the control mode of the first digital asset; a second receiving module configured to receive an eighth response sent by the second function module, indicating whether the control mode of the first digital asset is successfully set or updated; a second sending module configured to send a seventh response to the third platform and / or the third terminal, indicating whether the control mode of the first digital asset is successfully set or updated.

46. A second function module, comprising: a first receiving module configured to receive first information sent by a first function module, the first information comprising information of the first digital asset and / or information of an owner of the first digital asset and / or information of a second platform; a first sending module configured to send a ninth request to the first function module, for requesting the owner of the first digital asset and / or the second platform and / or a second terminal to set the control mode of the first digital asset; a second receiving module configured to receive a ninth response sent by the first function module, indicating the control mode of the first digital asset; a first processing module configured to set and / or store the control mode of the first digital asset according to the ninth response.

47. A first function module, comprising: a first sending module configured to send first information to a second function module, the first information comprising information of a first digital asset and / or information of an owner of the first digital asset and / or information of a second platform; a first receiving module configured to receive a ninth request sent by the second function module, for requesting to set the control mode of the first digital asset; a second sending module configured to send a tenth request to the second platform and / or a second terminal, for requesting to set the control mode of the first digital asset; a second receiving module configured to receive a tenth response sent by the second platform and / or the second terminal, indicating the control mode of the first digital asset; a third sending module configured to send a ninth response to the second function module, indicating the control mode of the first digital asset.

48. A first functional module comprising: a transceiver, a processor, a memory, and a program or instructions stored on the memory and executable on the processor; wherein the processor implements the steps of the method of any one of claims 1-5, 29-30, 36-40 when executing the program or instructions.

49. A second functional module comprising: a transceiver, a processor, a memory, and a program or instructions stored on the memory and executable on the processor; wherein the processor implements the steps of the method of any one of claims 6-18, 19-25, 26-28, 31-35 when executing the program or instructions.

50. A computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method of any one of claims 1-40.

51. A computer program product comprising computer instructions which, when executed by a processor, implement the steps of the method of any one of claims 1-40.

Images