Augmented reality effects on blockchain

Abstract

Exemplary implementations include methods, apparatuses, and computer-readable media for managing augmented reality (AR) special effects on a blockchain including receiving a request to convert the AR special effects into a distributed digital asset. These implementations also include uploading an AR effect packet including an execution file of the AR effect to a distributed server connected to the peer-to-peer network. The implementations also include generating metadata associated with the AR effect packet, wherein the metadata indicates attributes of the AR effect and a storage address of the AR effect packet in the distributed server. These implementations also include generating a token universal resource identifier (tokenURI) linked to the metadata, and using a smart contract to generate a distributed digital asset corresponding to the AR effect packet and the tokenURI for storage on the blockchain and subsequent access by a content creation application.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. patent application serial number 17 / 741,135, filed on May 10, 2022, entitled “AUGMENTED REALITY EFFECTS ON BLOCKCHAIN,” the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] The described aspects relate to distributed ledger systems. Background Art

[0004] Aspects of the present disclosure relate generally to distributed ledger systems, and more particularly, to managing augmented reality (AR) effects on a blockchain.

[0005] Digital assets, such as non-interchangeable tokens, include two-dimensional (2D) images or three-dimensional (3D) models. However, such digital assets have limited use cases. Therefore, there is a need to improve the mechanism for creating and using such digital assets. Summary of the invention

[0006] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all anticipated aspects, nor is it intended to identify the key or important elements of all aspects, nor is it intended to delimit the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] Exemplary aspects include a method for managing augmented reality (AR) effects on a blockchain, the method including receiving a request to convert an AR effect into a distributed digital asset. The method also includes uploading an AR effect package including an execution file of an AR effect to a distributed server connected to a peer-to-peer network. The method also includes generating metadata associated with the AR effect package, wherein the metadata indicates the properties of the AR effect and the storage address of the AR effect package in the distributed server. In addition, the method also includes generating a token universal resource identifier (tokenURI) linked to the metadata. In addition, the method also includes using a smart contract to generate a distributed digital asset corresponding to the AR effect package and the tokenURI, wherein the smart contract assigns the ownership of the distributed digital asset to the creator of the AR effect package. In addition, the method also includes storing a creation event including generation information of the distributed digital asset on the blockchain. In addition, the method also includes receiving a user request from a content creation application to access the AR effect package, wherein the user request includes the tokenURI. In addition, the method also includes enabling the content creation application to access the AR effect package using a smart contract.

[0008] Another exemplary aspect includes a device for managing augmented reality (AR) effects on a blockchain, the device comprising a memory and a processor coupled to the memory. The processor is configured to receive a request to convert an AR effect into a distributed digital asset. The processor is configured to upload an AR effect package including an execution file of an AR effect to a distributed server connected to a peer-to-peer network. The processor is also configured to generate metadata associated with the AR effect package, wherein the metadata indicates the properties of the AR effect and the storage address of the AR effect package in the distributed server. In addition, the processor is also configured to generate a token universal resource identifier (tokenURI) linked to the metadata. In addition, the processor is also configured to use a smart contract to generate a distributed digital asset corresponding to the AR effect package and the token URI, wherein the smart contract assigns the ownership of the distributed digital asset to the creator of the AR effect package. In addition, the processor is also configured to store a creation event including generation information of the distributed digital asset on the blockchain. In addition, the processor is also configured to receive a user request from a content creation application to access the AR effect package, wherein the user request includes the tokenURI. In addition, the processor is configured to enable access to the AR effects package by the content creation application using a smart contract.

[0009] Another example aspect includes a device for managing augmented reality (AR) effects on a blockchain, the device including a device for receiving a request to convert an AR effect into a distributed digital asset. The device also includes a device for uploading an AR effect package including an execution file of an AR effect to a distributed server connected to a peer-to-peer network. The device also includes a device for generating metadata associated with the AR effect package, wherein the metadata indicates the properties of the AR effect and the storage address of the AR effect package in the distributed server. In addition, the device also includes a device for generating a token universal resource identifier (tokenURI) linked to the metadata. In addition, the device also includes a device for generating a distributed digital asset corresponding to the AR effect package and the tokenURI using a smart contract, wherein the smart contract assigns the ownership of the distributed digital asset to the creator of the AR effect package. In addition, the device also includes a device for storing a creation event including generation information of a distributed digital asset on the blockchain. In addition, the device also includes a device for receiving a user request from a content creation application to access the AR effect package, wherein the user request includes the tokenURI. In addition, the device also includes a device for enabling content creation applications to access AR special effects packages using smart contracts.

[0010] Another example aspect includes a computer-readable medium having instructions for managing augmented reality (AR) effects on a blockchain, wherein the instructions are executable by a processor to receive a request to convert an AR effect into a distributed digital asset. The instructions are also executable to upload an AR effect package including an execution file of an AR effect to a distributed server connected to a peer-to-peer network. The instructions are also executable to generate metadata associated with the AR effect package, wherein the metadata indicates the properties of the AR effect and the storage address of the AR effect package in the distributed server. In addition, the instructions are also executable to generate a token universal resource identifier (tokenURI) linked to the metadata. In addition, the instructions are also executable to generate a distributed digital asset corresponding to the AR effect package and the tokenURI using a smart contract, wherein the smart contract assigns ownership of the distributed digital asset to the creator of the AR effect package. In addition, the instructions are also executable to store a creation event including generation information of the distributed digital asset on the blockchain. In addition, the instructions are also executable to receive a user request from a content creation application to access the AR effect package, wherein the user request includes the tokenURI. In addition, the instructions are also executable to enable content creation applications to access AR effects packages using smart contracts.

[0011] To achieve the above-mentioned and related purposes, one or more aspects include the features fully described and particularly pointed out in the claims below. The following description and the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are only indicative of some of the various ways in which the principles of the various aspects can be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate one or more exemplary aspects of the present disclosure and, together with the detailed description, serve to explain their principles and implementations.

[0013] Figure 1 is a diagram of a system for accessing generated augmented reality (AR) effects using blockchain according to an exemplary aspect of the present disclosure.

[0014] Figure 2 is a diagram depicting a screen of an AR application when a user accesses a distributed digital asset according to an exemplary aspect of the present disclosure.

[0015] Figure 3 is a block diagram of a computing device executing a digital asset management component according to an exemplary aspect of the present disclosure.

[0016] Figure 4 is a flowchart illustrating a method for managing AR effects on a blockchain according to an exemplary aspect of the present disclosure.

[0017] Figure 5 is a flow chart illustrating a method of enabling different content creation applications to access distributed digital assets according to an exemplary aspect of the present disclosure.

[0018] Figure 6 is a flow chart illustrating a method of transferring ownership of a distributed digital asset according to an exemplary aspect of the present disclosure. DETAILED DESCRIPTION

[0019] Various aspects will now be described with reference to the accompanying drawings. In the following description, for the purpose of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. However, it is apparent that such aspects may be practiced without these specific details.

[0020] The present disclosure provides a way to combine non-interchangeable (interchangeably used with "distributed digital assets" or "digital assets") tokens with various augmented reality (AR) technologies. Distributed digital assets can be encrypted tokens that cannot be copied and are non-interchangeable data units stored on a blockchain. In an exemplary aspect, an AR effect package (such as but not limited to a folder or zip folder) storing multiple features and / or codes defining AR effects is considered a distributed digital asset, and a user of a computer application (such as but not limited to a social media application with a camera-based feature) can use the digital asset to create a video or image.

[0021] More specifically, AR effects are serialized into a package (also called a map package), such as a computer folder or a compressed version of a computer folder, such as a zip folder. The package is created internally by an interactive engineer or by an external effect creator. The package can then be decoded into an effect filter on a mobile app.

[0022] Figure 1 1 is a diagram of a system 100 for accessing generated augmented reality (AR) effects using blockchain according to an exemplary aspect of the present disclosure. The system 100 has a pipeline for storing, minting, trading, and distributing distributed digital assets using blockchain.

[0023] For example, the special effect creator 102 may create an AR special effect 105 on a creation tool 104 (e.g., a special effect house) that they want to share with users such as user 116 and user 120. Conventionally, in order to share the AR special effect 105 on a platform (e.g., a social media application), the special effect creator 102 must create an account on the platform and upload the AR special effect 105 to a central server that belongs only to the platform. If the special effect creator 102 intends to share the same AR special effect on different platforms, the special effect creator 102 must create an account on the different platform and upload the AR special effect 105 to another central server that belongs only to the different platform. This will cause exclusivity issues because users of one platform cannot access content on the server of another platform. For special effect creators 102 who may intend to upload AR special effects 105 on several platforms, the process may also be inefficient and cumbersome because the special effect creators 102 need to repeat their work and / or learn new tools and / or systems to create and store the same AR special effect on each different platform. Furthermore, ownership of the AR effect 105 may be unprotected because, in some cases, another creator may simply copy the AR effect 105 or use the AR effect 105 as their own without authorization.

[0024] In the system 100, the creation tool 104 may have a plug-in that enables the special effects creator 102 to upload an AR special effects package 106 to the server 110, the AR special effects package including a computer folder (e.g., a zip folder) with a normal memory size or a compressed memory size, which has all the visual effects, scripts, and configuration files of the AR special effects 105. For example, the graphical user interface of the creation tool 104 may have an "Upload special effects as distributed digital assets" button. After the user clicks the upload button, the creation tool 104 uploads the package 106 to the server 110. In some aspects, a panel may pop up, prompting the special effects creator 102 to create metadata 108 for the AR special effect 105 and select a thumbnail (e.g., a JPEG image) of the special effect. The metadata 108 may include information about the AR effects 105, such as, but not limited to, the effect type describing the general category of the effect (e.g., facial effects, environmental effects, world effects, hand effects, body effects, etc.), the storage size of the AR effect 105, component physics (e.g., how the AR effect interacts with surfaces, lighting, etc.), visual data (e.g., color, shape, etc.), and any other information or logic that defines the appearance and / or function of the effect. The metadata 108 may also include the storage address of the AR effect package 106 on the server 110.

[0025] The server 110 may be a distributed server that forms part of a peer-to-peer network. For example, the server 110 may utilize a protocol such as the InterPlanetary File System (IPFS). In some cases, a centralized server is not recommended because the AR effect 105 will be linked using an HTTP address on a centralized server. If the owner of the AR effect 105 were to change the object at the HTTP address (e.g., change the AR effect 105 with another AR effect), the value of the distributed digital asset 113 generated from the AR effect package 106 would change. IPFS uses content addressing, and multiple nodes store uploaded data. Therefore, when the AR effect package 106 is uploaded to the server 110 (part of IPFS), a content identifier of the package 106 is generated from the data of the package 106, and the content identifier is linked to the package 106 in the IPFS network. The content identifier refers only to the package 106; therefore, the package 106 cannot be modified without modifying the content identifier. If the package 106 is modified in some way, the content identifier will be invalid (unlike the HTTP address, which will simply point to a different AR effect).

[0026] The data storage entity (e.g., IPFS) may also generate a token universal resource (tokenURI) 111, which serves as an index pointing to the metadata 108 stored in the server 110. For example, accessing an index (such as a link) in the tokenURI 111 directs the user to the metadata 108.

[0027] In order to convert the AR special effects package 106 into a distributed digital asset 113, a smart contract 112 is used. The smart contract 112 can be a software program stored on the blockchain 114 that runs when certain predetermined conditions are met. Such conditions include receiving a request to generate a digital asset, modify a digital asset, change the ownership of a digital asset, delete a digital asset, etc. The smart contract 112 is specifically configured to generate a distributed digital asset based on a request / command made by the special effects creator 102, and store event data (e.g., about a creation event, an ownership transfer event, etc.) on the blockchain 114.

[0028] The smart contract 112 receives the tokenURI 111 and the wallet address of the wallet belonging to the special effect creator 102, and executes the mint function to generate a distributed digital asset 113 and assign the ownership of the distributed digital asset 113 to the special effect creator 102. In one aspect, the wallet address can be a unique identifier, such as but not limited to a randomly generated set of numbers and / or letters, wherein the wallet address is associated with or linked to an electronic account (e.g., a crypto wallet). For example, a wallet is a software program or physical device that can store digital assets such as distributed digital assets 113. It should be noted that a wallet can store multiple addresses, and during the minting process, the smart contract 112 obtains an address parameter (e.g., the address of the special effect creator 102 and the address is linked to the distributed digital asset 113). The address is selected by the user and used during the minting process. Depending on the specific implementation, the address can also be a default address provided by the wallet.

[0029] The wallet may also include private and public encryption keys, where the public key is derived from the private key, and may be a wallet address for exchanging digital assets. For example, the wallet address may be a combination of alphanumeric characters unique to the special effect creator 102.

[0030] Information about the creation event (e.g., transaction) of the distributed digital asset 113 is then stored on the blockchain 114 through the smart contract 112. As the ownership of the distributed digital asset 113 changes, additional events are published to the blockchain 114. For example, a user 116 can obtain a tokenURI 111 associated with the distributed digital asset 113 and attempt to acquire ownership of the AR effects package 106. For example, the user 116 can connect their wallet (e.g., provide a wallet address) to a content creation platform 118, which can be a mobile application (e.g., a social media application). This enables the platform 118 to find information corresponding to the address in the smart contract 112 on the blockchain 114 and display the distributed digital asset with the AR effects tag.

[0031] Typically, tokenURI 111 is stored in the storage space of smart contract 112. A user (e.g., user 116) can send a distributed digital asset request transaction to smart contract 112, which includes the public key of user 116 (e.g., Ethereum address), the identifier of distributed digital asset 113 (e.g., the hash value of the asset), and the signature (signed by the user's private key). Smart contract 112 uses the signature to verify the identity of user 116 and returns corresponding information about the requested distributed digital asset 113 (e.g., tokenURI 111).

[0032] The user 116 can then select the distributed digital asset through the corresponding IPFS storage address in the metadata and download it to the local storage on the computing device (e.g., a smartphone, laptop, desktop computer, tablet computer, or digital assistant). For example, the user 116 can use the tokenURI 111 to access the metadata 108, and then download the package 106 from the server 110 using the storage address listed in the metadata 108.

[0033] The content creation platform 118 can then decode the AR special effects package 106 through the special effects engine and allow the user 116 to create a video using the AR special effects 105. In some aspects, the ownership of the distributed digital asset 113 can be transferred from the special effects creator 102 to the user 116, and the ownership change event can be recorded on the blockchain 114 (e.g., in block 2).

[0034] As previously described, the distributed digital asset 113 can be accessed by different content creation platforms. For example, the user 120 can also use the tokenURI 111 to access the metadata 108, and then download the package 106 from the server 110 using the storage address listed in the metadata 108. The content creation platform 122, which can be a different mobile application (e.g., a different social media application), can then decode the package 106 and allow the user 120 to use the package. In addition, the ownership of the distributed digital asset 113 can be transferred from the special effect creator 102 to the user 120, or from the user 116 to the user 120. The ownership change event can be recorded on the blockchain 114 (e.g., in block N, where N is any integer).

[0035] Because all events are recorded on the blockchain 114, the system 100 enables the special effect creator to protect the AR content (e.g., AR special effects 105) he / she creates and consolidate ownership or ownership transfer. Special effect creators can also share AR special effects 105 more easily on different platforms without having to learn the complexity of each different platform of interest.

[0036] Figure 2 is a diagram 200 depicting a display including two screens 202 and 214 of an AR application that change over time as a user accesses a distributed digital asset, in accordance with exemplary operational aspects of the present disclosure.

[0037] Screen 202 represents a screenshot of an AR application (e.g., content creation platform 118) accessed by user 116. Assume that a selfie view 204 of user 116 is captured in screen 202. Wallet 206 can be presented on the graphical user interface of the AR application. Wallet 206 includes various AR effects 208 owned by user 116. One of the AR effects is AR effect 210, which corresponds to distributed digital assets 113 and is generated using package 106. When user 116 selects AR effect 210, for example, in screen 202, AR object 212 (e.g., glasses and facial hair covering) is generated on subsequent screen 214.

[0038] refer to Figure 3 and Figure 4 In operation, the computing device 300 may execute the method 400 for managing augmented reality (AR) effects on a blockchain, for example, by executing the digital asset management component 315 via the processor 305 and / or the memory 310 .

[0039] At block 402, method 400 includes receiving a request to convert an AR effect into a distributed digital asset. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or receiving component 320 may be configured to or may include means for receiving a request to convert an AR 105 effect into a distributed digital asset 113.

[0040] For example, the special effect creator 102 can use the creation tool 104 to create an AR special effect 105, which is an AR special effect that overlays glasses and a beard on the user's face in the content creation application. The creation tool 104 may include a button on its graphical user interface that generates a request to convert the created AR special effect into a distributed digital asset when selected.

[0041] At box 403, method 400 includes uploading an AR special effect package including an execution file of an AR special effect to a distributed server connected to a peer-to-peer network. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315 and / or upload component 323 may be configured as or may include means for uploading an AR special effect package 106 including an execution file of an AR special effect 105 to a distributed server 110 connected to a peer-to-peer network (e.g., a portion of IPFS).

[0042] For example, in response to receiving a selection of a button on creation tool 104 to convert an AR effect into a distributed digital asset, creation tool 104 may upload package 106 (e.g., a zip folder) that includes any relevant data needed to render and use AR effect 105. In some aspects, creation tool 104 may upload data to multiple servers (including server 110) that are part of a peer-to-peer network.

[0043] At box 404, method 400 includes generating metadata associated with the AR special effects package, wherein the metadata indicates the properties of the AR special effects and the storage address of the AR special effects package in the distributed server. For example, in one aspect, the computing device 300, the processor 305, the memory 310, the digital asset management component 315 and / or the generation component 325 can be configured as or can include a device for generating metadata 108 associated with the AR special effects package 106, wherein the metadata 108 indicates the properties of the AR special effects 105 in the distributed server 110 and the storage address of the AR special effects package 106.

[0044] For example, the generation component 325 can generate metadata 108, which can be a data structure that includes the following information about the AR special effects package 106: the creation date of the AR special effects 105, the user identifier of the creator and / or owner of the package 106 (e.g., the wallet address of the special effects creator 102, the IP / MAC address, name, location, email address, username, password, phone number, etc. of the computing device on which the creation tool 104 is installed), visual details of the AR special effects 105 (e.g., the size, color, position, function, etc. of objects in the AR special effects such as glasses and beards), the file name and size (e.g., a script or executable file), etc.

[0045] At block 406, the method 400 includes generating a token universal resource identifier (tokenURI) linked to the metadata. For example, in one aspect, the computing device 300, the processor 305, the memory 310, the digital asset management component 315, and / or the generation component 330 can be configured as or can include means for generating a tokenURI 111 linked to the metadata 108.

[0046] For example, the generation component 350 can be part of the creation tool 104 and can store the metadata 108 in the tokenURI 111. The TokenURI 111 serves as a pointer to the metadata 108 stored in the server 110.

[0047] At box 408, method 400 includes using a smart contract to generate a distributed digital asset corresponding to the AR special effects package and the tokenURI, wherein the smart contract assigns ownership of the distributed digital asset to the creator of the AR special effects package. For example, in one aspect, the computing device 300, the processor 305, the memory 310, the digital asset management component 315, and / or the generation component 335 can be configured as or can include a device for generating a distributed digital asset 113 corresponding to the AR special effects package 106 and the tokenURI 111 using a smart contract 112, wherein the smart contract 112 assigns ownership of the distributed digital asset 113 to the special effects creator 102 of the AR special effects 105.

[0048] The generation component 335 can be a function or module of the smart contract 112 and is triggered in response to receiving a request from the creation tool 104 to generate a distributed digital asset 113. For example, the generation component 335 can execute a creation event of the distributed digital asset 113. The event can be a transaction, which includes information such as from, to, nonce, cost (for example, if the blockchain 114 is Ethereum TMThe "from" field includes the public key of the special effect creator 102 (retrieved from the special effect creator 102 wallet), the "to" field includes the address of the smart contract 112 on the blockchain 114, the "nonce" field represents a "one-time number" that prevents the same event from being replayed, the "cost" field represents the cost required to successfully execute the event or execute the contract in the blockchain 114, and the "data" field includes the calculation to be performed (for example, executing the smart contract 112 distributed digital asset creation function). The creation function is signed using the private key of the special effect creator 102, where the private key is retrieved from the special effect creator's wallet 102. When the creation event is executed, the smart contract 112 generates a distributed digital asset 113 and sets the owner of the distributed digital asset 113 to the special effect creator 102. The distributed digital assets 113 may include the public key of the special effect creator 102, the tokenURI 111 of the AR special effect package 106, the name of the IPFS entity used (e.g., the server 110), the name of the AR special effect 105, the date when the AR special effect 105 was created, the description of the AR special effect 105, and some additional bookkeeping information.

[0049] In an alternative or additional aspect, assigning ownership of the distributed digital asset 113 to the special effect creator 102 of the AR special effect package 106 includes linking the distributed digital asset 113 to the wallet address of the special effect creator 102. As described above, the wallet address can be a public key used in the "from" field. Therefore, the creation event automatically assigns ownership to the special effect creator 102 using the data in the "from" field.

[0050] At block 410, method 400 includes storing a creation event including generation information of a distributed digital asset on a blockchain. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or storage component 340 may be configured to or may include means for storing a creation event including generation information of distributed digital asset 113 on blockchain 114 (e.g., on block 1). For example, storage component 340 may store details of the creation event (e.g., from, to, data, etc.) on blockchain 114.

[0051] At box 412, method 400 includes receiving a user request from a content creation application to access an AR special effects package, wherein the user request includes a tokenURI. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315 and / or receiving component 345 can be configured as or can include a device for receiving a user request from a content creation application (e.g., content creation platform 118) to access an AR special effects package 106, wherein the user request includes a tokenURI 111.

[0052] For example, user 116 may be using a social media platform. User 116's wallet may be connected to the social media application so that user 116 can use the AR effects in his / her wallet (e.g., generate Figure 2 The content creation platform 118 may provide an interface depicting a plurality of distributed digital assets that may be accessed using the server 110. Each distributed digital asset may be linked to a corresponding tokenURI. For example, a user 116 may desire to access a distributed digital asset 113 via the interface. When a thumbnail or tag of a distributed digital asset 113 is selected, a request may be sent to the smart contract 112 to enable access to the package 106 associated with the distributed digital asset 113. In particular, the request may include a tokenURI 111 that enables the smart contract 112 to identify the specific distributed digital asset being requested to be accessed.

[0053] At block 414, method 400 includes enabling access to the AR effects package by the content creation application using a smart contract. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or enabling component 350 may be configured as or may include means for enabling access to the AR effects package 106 by the content creation platform 118 using a smart contract 112. In some aspects, if user 116 requests to become the owner of a distributed digital asset 113, user 116 may only be able to access the distributed digital asset 113 (see Figure 6 ).

[0054] For example, the smart contract 112 may send metadata 108 of the package 106 to the content creation platform 118, wherein the metadata 108 includes a storage address of the package 106. The content creation platform 118 may retrieve and execute the package 106 to render the AR effect 105.

[0055] More specifically, in alternative or additional aspects, the content creation platform 118 is configured to download the AR effects package 106 from the distribution server 110 to the computing device 118 executing the content creation platform, decode the AR effects package 106 to present the AR effects 105, and enable the user 116 to access the AR effects 105.

[0056] refer to Figure 5 In an optional aspect, at box 502, method 400 may also include receiving another user request for accessing the AR special effects package from a different content creation application, wherein the other user request includes the tokenURI. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315 and / or receiving component 355 may be configured to or may include a device for receiving another user request for accessing the AR special effects package 106 from a different content creation application (e.g., content creation platform 122), wherein the other user request includes tokenURI 111.

[0057] For example, user 120 may link his / her wallet to a particular social media application. The social media application may also provide an interface depicting a plurality of distributed digital assets accessible via server 110. User 120 may select distributed digital asset 113.

[0058] In this optional aspect, at box 504, method 400 may also include enabling different content creation applications to access the AR special effects package using smart contracts. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or enabling component 360 may be configured as or may include a device that uses smart contracts 112 to enable different content creation applications (e.g., content creation platform 122) to access AR special effects package 106.

[0059] For example, smart contracts 112 can enable users 120 of social media applications to present AR special effects 105 for content creation. The benefit of the present disclosure shown here is that distributed digital assets 113 enable access to AR special effects 105 for multiple content creation platforms. In each case, the owner of the distributed digital assets 113 is still the special effect creator 102.

[0060] refer to Figure 6In an optional aspect, where the user request also includes a wallet address of a user 116 of a content creation application (e.g., a content creation platform 118), at box 602, enabling access to the AR special effects package by the content creation application at box 414 may also include transferring ownership of the distributed digital asset from the creator to the user by linking the distributed digital asset to the user's wallet address. For example, in one aspect, the computing device 300, the processor 305, the memory 310, the digital asset management component 315, and / or the transfer component 365 may be configured as or may include a device for transferring ownership of the distributed digital asset 113 from the special effects creator 102 to the user 116 by linking the distributed digital asset 113 to the wallet address of the user 116.

[0061] For example, a user request may explicitly request to purchase or receive ownership of a distributed digital asset 113. The request represents the creation of an ownership change event. The ownership change event may include the same fields as described above (e.g., from, to, cost, data, etc.). More specifically, the "data" field may request a function that triggers the transfer ownership (e.g., transfer component 365) of the smart contract 112. The special effect creator 102 and / or the user 116 may each sign the ownership change event using their respective private keys.

[0062] In this optional aspect, at box 604, method 400 may also include storing an ownership change event on the blockchain, the ownership change event including the wallet address of the creator, the wallet address of the user, and the tokenURI. For example, in one aspect, computing device 300, processor 305, memory 310, digital asset management component 315, and / or storage component 370 may be configured to or may include means for storing an ownership change event on blockchain 114 (e.g., on block 2), the ownership change event including the wallet address of special effect creator 102, the wallet address of user 116, and tokenURI 111. The publication of the ownership change event on blockchain 114 indicates that user 116 is the new owner of distributed digital asset 113.

[0063] Although the foregoing disclosure discusses illustrative aspects and / or embodiments, it should be noted that various changes and modifications may be made herein without departing from the scope of the described aspects and / or embodiments as defined by the appended claims. Furthermore, although elements of the described aspects and / or embodiments may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Furthermore, unless otherwise stated, all or a portion of any aspect and / or embodiment may be used with all or a portion of any other aspect and / or embodiment.

Claims

1. A method for managing augmented reality (AR) effects on a blockchain, the method comprising: Receiving a request to convert an AR effect into a distributed digital asset; Uploading an AR special effect package to a distributed server connected to a peer-to-peer network, wherein the AR special effect package includes an execution file of the AR special effect; Generate metadata associated with the AR special effect package, wherein the metadata indicates properties of the AR special effect and a storage address of the AR special effect package in the distributed server; generating a token universal resource identifier (tokenURI) linked to the metadata; Generate a distributed digital asset corresponding to the AR special effects package and the tokenURI using a smart contract, wherein the smart contract assigns ownership of the distributed digital asset to the creator of the AR special effects package; Storing a creation event including generation information of the distributed digital asset on the blockchain; Receiving a user request for accessing the AR special effects package from a content creation application, wherein the user request includes the tokenURI; and The smart contract is used to enable the content creation application to access the AR special effects package.

2. The method according to claim 1, further comprising: Receiving another user request for accessing the AR special effects package from a different content creation application, wherein the another user request includes the tokenURI; as well as The smart contract is used to enable the different content creation applications to access the AR special effects package.

3. The method of claim 1, wherein assigning the ownership of the distributed digital asset to the creator of the AR special effects package comprises linking the distributed digital asset to a wallet address of the creator.

4. The method of claim 1, wherein the user request further includes a wallet address of a user of the content creation application, and wherein enabling the content creation application to access the AR effects package comprises: The ownership of the distributed digital asset is transferred from the creator to the user by linking the distributed digital asset to the wallet address of the user.

5. The method according to claim 4, further comprising: An ownership change event is stored on the blockchain, wherein the ownership change event includes the wallet address of the creator, the wallet address of the user, and the tokenURI.

6. The method of claim 1, wherein the content creation application is configured to: Downloading the AR special effects package from the distributed server to a computing device executing the content creation application; Decoding the AR special effect package to present the AR special effect; as well as Enabling access to the AR effect by a user of the content creation application. 7 . The method according to claim 1 , wherein the AR special effect package is a folder including one or more of visual effects, scripts, and configuration files of the AR special effect.

8. A device for managing augmented reality (AR) effects on a blockchain, the device comprising: Memory; as well as a processor communicatively coupled to the memory and configured to: Receiving a request to convert an AR effect into a distributed digital asset; Uploading an AR special effect package to a distributed server connected to a peer-to-peer network, wherein the AR special effect package includes an execution file of the AR special effect; Generate metadata associated with the AR special effect package, wherein the metadata indicates properties of the AR special effect and a storage address of the AR special effect package in the distributed server; generating a token universal resource identifier (tokenURI) linked to the metadata; Generate a distributed digital asset corresponding to the AR special effects package and the tokenURI using a smart contract, wherein the smart contract assigns ownership of the distributed digital asset to the creator of the AR special effects package; Storing a creation event on the blockchain, the creation event including generation information of the distributed digital asset; Receiving a user request for accessing the AR special effects package from a content creation application, wherein the user request includes the tokenURI; and The smart contract is used to enable the content creation application to access the AR special effects package.

9. The apparatus of claim 8, wherein the processor is further configured to: Receiving another user request to access the AR special effects package from a different content creation application, wherein the another user request includes the tokenURI; and The smart contract is used to enable the content creation application to access the AR special effects package.

10. The apparatus of claim 8, wherein assigning the ownership of the distributed digital asset to the creator of the AR special effects package comprises linking the distributed digital asset to a wallet address of the creator.

11. The apparatus of claim 8, wherein the user request further comprises a wallet address of a user of the content creation application, and wherein enabling the content creation application to access the AR effects package comprises: The ownership of the distributed digital asset is transferred from the creator to the user by linking the distributed digital asset to the wallet address of the user.

12. The apparatus of claim 11, wherein the processor is further configured to: An ownership change event is stored on the blockchain, wherein the ownership change event includes the wallet address of the creator, the wallet address of the user, and the tokenURI.

13. The apparatus of claim 8, wherein the content creation application is configured to: Downloading the AR special effects package from the distributed server to a computing device executing the content creation application; Decoding the AR special effect package to present the AR special effect; as well as Enabling access to the AR effect by a user of the content creation application. 14 . The device according to claim 8 , wherein the AR special effect package is a folder including one or more of the following: visual effects, scripts, and configuration files of the AR special effect.

15. A computer-readable medium having stored thereon instructions for managing augmented reality (AR) effects on a blockchain, wherein the instructions are executable by a processor to: Receiving a request to convert an AR effect into a distributed digital asset; Uploading an AR special effect package including an execution file of the AR special effect to a distributed server connected to a peer-to-peer network; Generate metadata associated with the AR special effect package, wherein the metadata indicates properties of the AR special effect and a storage address of the AR special effect package in the distributed server; generating a token universal resource identifier (tokenURI) linked to the metadata; Generate a distributed digital asset corresponding to the AR special effects package and the tokenURI using a smart contract, wherein the smart contract assigns ownership of the distributed digital asset to the creator of the AR special effects package; Storing a creation event on the blockchain, the creation event including generation information of the distributed digital asset; Receiving a user request for accessing the AR special effects package from a content creation application, wherein the user request includes the tokenURI; and The smart contract is used to enable the content creation application to access the AR special effects package.

16. The computer-readable medium of claim 15, further comprising instructions executable by the processor to: Receiving another user request to access the AR special effects package from a different content creation application, wherein the another user request includes the tokenURI; and The smart contract is used to enable the content creation application to access the AR special effects package.

17. The computer-readable medium of claim 15, wherein assigning the ownership of the distributed digital asset to the creator of the AR special effects package comprises linking the distributed digital asset to a wallet address of the creator.

18. The computer-readable medium of claim 15, wherein the user request further comprises a wallet address of a user of the content creation application, and wherein enabling the content creation application to access the AR effects package comprises: The ownership of the distributed digital asset is transferred from the creator to the user by linking the distributed digital asset to the wallet address of the user.

19. The computer-readable medium of claim 18, further comprising instructions executable by the processor to: An ownership change event is stored on the blockchain, wherein the ownership change event includes the wallet address of the creator, the wallet address of the user, and the tokenURI.

20. The computer-readable medium of claim 15, further comprising instructions executable by the processor to: Downloading the AR special effects package from the distributed server to a computing device executing the content creation application; Decoding the AR special effect package to present the AR special effect; as well as Enabling access to the AR effect by a user of the content creation application.

Images