Methods, systems, and computer program products for the generation and transfer of non-fungible tokens

Abstract

The present invention provides a solution for the generation and transfer of digital media-based non-fungible tokens on a distributed blockchain ledger for implementation with a cloud-based service system, and more particularly within a cloud gaming system. The present invention relies on a cloud service server and a non-fungible token service platform for implementing the generation and / or transfer of digital media-based non-fungible tokens on a distributed blockchain ledger in accordance with the present invention.

Description

[Technical field]

[0001] The present invention relates to the generation and transfer of non-fungible tokens. In particular, the present invention provides a method, system, and computer program product for the generation and transfer of non-fungible tokens for implementation in cloud-based service systems, and even more specifically, within cloud gaming systems. [Background technology]

[0002] Blockchain technology is increasingly being used for the realization of digital assets created in the form of non-fungible tokens (or NFTs). Non-fungible tokens are generally distinct from other digital tokens or currencies. Non-fungible tokens are tokenizations of digital or real-world assets. They serve as verifiable proof of authenticity and ownership within the blockchain network. In general, non-fungible tokens are not interchangeable with one another and can be understood as realizing rights management solutions within the digital domain. While non-fungible tokens can be bought and sold using fungible tokens such as digital or non-digital currencies, non-fungible tokens themselves constitute a unique asset class and are not fungible like fungible tokens. Identifying information is embedded in the smart contract of each non-fungible token, making each non-fungible token unique. In general, this uniqueness makes non-fungible tokens unsuitable for traditional crypto trading purposes and token currency exchanges, but ideal for recording and remembering and storing ownership of digital items such as collectibles, games, and even art. However, generating non-fungible tokens and securely buying or selling such non-fungible tokens remains complex and beyond the reach of the average user of computing devices and software services.

[0003] At the same time, with the increasing availability of affordable computing hardware, it is becoming commonplace for individuals to use multiple computing or data processing devices to access cloud-based or network-based services, including, for example, cloud-based gaming services.

[0004] Such cloud-based services provide a significant opportunity to generate unique and valuable non-fungible tokens, given the marketability of a variety of different forms of digital media content, and digital media content associated with popular personalities or significant digital events.

[0005] For example, FIG. 1 illustrates a non-fungible token that includes a screenshot of an artwork image of the type that may be part of a cloud-based computer game.

[0006] However, the complexities involved in generating non-fungible tokens in connection with cloud-based services are even greater, creating even more obstacles to widespread adoption and use.

[0007] Thus, there is a need for a solution that enables easy, secure and convenient generation of non-fungible tokens in connection with cloud-based services, and for securely buying, selling, or otherwise transferring ownership or control of such non-fungible tokens. Summary of the Invention

[0008] The present invention enables the generation and transfer of non-fungible tokens for implementation in cloud-based service systems, and in particular, for implementation within cloud gaming systems. [Means for solving the problem]

[0009] The present invention provides a method for recording a digital media-based non-fungible token on a distributed blockchain ledger, the method including: (i) establishing a cloud service network communication session between a cloud service server and a client terminal, where establishing the cloud service network communication session includes allocating a network communication channel between the cloud service server and the client terminal to the cloud service network communication session; (ii) streaming data generated by an instance of a software application running on the cloud service server from the cloud service server to the client terminal over the network communication channel; and (iii) transmitting data generated by an instance of a software application running on the cloud service server from the cloud service server to the client terminal through the client terminal. (b) receiving user input identifying the selected digital media content; (iv) generating a non-fungible token record representing the non-fungible token, wherein the non-fungible token record includes data identifying or representing the selected media content; and (v) implementing a record of the non-fungible token on a distributed blockchain ledger, including: (c) transmitting the non-fungible token record to a non-fungible token service platform; and (d) storing data from the non-fungible token record in a record block associated with the distributed blockchain ledger.

[0010] The present invention also provides a method for recording transfers of digital media-based non-fungible tokens on a distributed blockchain ledger, the method including: (i) receiving, at a cloud services server, a request for a representation of digital media-based non-fungible tokens associated with the cloud services server or a cloud services application running on the cloud services server; (ii) obtaining data corresponding to a set of digital media-based non-fungible tokens associated with the cloud services server or cloud services application; (iii) performing a display of the obtained data corresponding to the set of non-fungible tokens; (iv) receiving user input for selecting a non-fungible token from within the set of digital media-based non-fungible tokens; and (v) transmitting a request to schedule a transfer of the selected media content for the selected non-fungible token to a non-fungible token service platform. (vi) responding to a confirmation message from the non-fungible token service platform confirming that the selected non-fungible token has been scheduled for transfer by performing a payment transaction to transfer the selected non-fungible token to the identified destination; and (vii) initiating recording of the transfer of the selected non-fungible token to the identified destination in a record block associated with the distributed blockchain ledger after the payment transaction for the transfer of the selected non-fungible token to the identified destination is completed.

[0011] The present invention also provides a system for recording digital media-based non-fungible tokens on a distributed blockchain ledger, the system including a processor implemented in a cloud services server configured to: (i) establish a cloud services network communication session between the cloud services server and a client terminal, where establishing the cloud services network communication session includes allocating a network communication channel between the cloud services server and the client terminal to the cloud services network communication session; (ii) stream data generated by an instance of a software application running on the cloud services server from the cloud services server to the client terminal over the network communication channel; and (iii) transmit, through the client terminal, data generated by an instance of a software application running on the cloud services server from the cloud services server to the client terminal via the network communication channel; (b) receiving user input identifying the selected digital media content; (iv) generating a non-fungible token record representing the non-fungible token, wherein the non-fungible token record includes data identifying or representing the selected media content; and (v) implementing the non-fungible token record on a distributed blockchain ledger includes transmitting the non-fungible token record to a non-fungible token service platform, wherein the non-fungible token service platform stores data from the non-fungible token record in a record block associated with the distributed blockchain ledger.

[0012] In another embodiment, the present invention provides a system for recording transfers of digital media-based non-fungible tokens on a distributed blockchain ledger, the system including a processor-implemented cloud services server configured to (i) receive, at the cloud services server, a request for display of digital media based on non-fungible tokens associated with the cloud services server or a cloud services application executing on the cloud services server, (ii) obtain data corresponding to a set of digital media-based non-fungible tokens associated with the cloud services server or the cloud services application, (iii) perform a display of the obtained data corresponding to the set of non-fungible tokens, and (iv) (v) sending a request to schedule a transfer of the selected non-fungible token to a non-fungible token service platform, wherein the non-fungible token service platform is configured to record the transfer of the non-fungible token in a distributed blockchain ledger in which the selected non-fungible token is recorded; (vi) responding to a confirmation message from the non-fungible token service platform confirming that the selected non-fungible token has been scheduled for transfer by performing a payment transaction to transfer the selected non-fungible token to an identified destination; and (vii) initiating recording the transfer of the selected non-fungible token to the identified destination in a record block associated with the distributed blockchain ledger after the payment transaction for the transfer of the selected non-fungible token to the identified destination is completed.

[0013] The present invention provides a computer program product for recording digital media-based non-fungible tokens on a distributed blockchain ledger, the computer program product comprising a non-transitory computer readable medium having computer readable program code embodied thereon, the computer readable program code including instructions for performing the steps of: (i) establishing a cloud service network communication session between a cloud services server and a client terminal, where establishing the cloud service network communication session includes allocating a network communication channel between the cloud services server and the client terminal to the cloud service network communication session, (ii) streaming data generated by an instance of a software application running on the cloud services server from the cloud services server to the client terminal over the network communication channel, and (iii) transmitting data generated by an instance of a software application running on the cloud services server from the cloud services server to the client terminal through the client terminal, the data being streamed from the cloud services server to the client terminal; (b) receiving user input identifying the selected digital media content; (iv) generating a non-fungible token record representing the non-fungible token, wherein the non-fungible token record includes data identifying or representing the selected media content; and (v) implementing recording of the non-fungible token on a distributed blockchain ledger, including: (c) transmitting the non-fungible token record to a non-fungible token service platform; and (d) storing data from the non-fungible token record in a record block associated with the distributed blockchain ledger.

[0014] The present invention also provides a computer program product for recording a transfer of digital media-based non-fungible tokens on a distributed blockchain ledger, the computer program product comprising a non-transitory computer readable medium having computer readable program code embodied thereon, the computer readable program code including instructions for performing the steps of: (i) receiving, at a cloud services server, a request for a display of digital media-based non-fungible tokens associated with the cloud services server or a cloud service application running on the cloud services server, (ii) obtaining data corresponding to a set of digital media-based non-fungible tokens associated with the cloud services server or a cloud service application running on the cloud services server, (iii) performing a display of the obtained data corresponding to the set of non-fungible tokens, (iv) receiving user input selecting a non-fungible token from within the set of digital media-based non-fungible tokens, and (v) sending a request to a non-fungible token service platform to schedule a transfer of the selected non-fungible token, wherein wherein the non-fungible token service platform is configured to record the transfer of the non-fungible token in a distributed blockchain ledger in which the selected non-fungible token is recorded; (vi) respond to a confirmation message from the non-fungible token service platform confirming that the selected non-fungible token has been scheduled for transfer by executing a payment transaction to transfer the selected non-fungible token to the identified destination; and (vii) initiate recording of the transfer of the selected non-fungible token to the identified destination in a record block associated with the distributed blockchain ledger after the payment transaction for the transfer of the selected non-fungible token to the identified destination is completed. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 illustrates an exemplary non-fungible token. [Diagram 2] FIG. 2 illustrates an example of a system environment in which the present disclosure may be applied. [Diagram 3] FIG. 3 illustrates an example of a system environment in which the present disclosure may be applied. [Figure 4] FIG. 4 illustrates an example configuration of a system configured to enable the generation of non-fungible tokens associated with cloud-based services in accordance with the present disclosure. [Diagram 5] FIG. 5 is a flow chart illustrating steps of a method for generating non-fungible tokens based on media content associated with a cloud-based service. [Figure 6] FIG. 6 is a communication flow diagram illustrating communication flow between system entities for implementing the method of FIG. [Figure 7] FIG. 7 is a flowchart illustrating the method steps involved in transferring non-fungible tokens associated with a cloud-based service. [Figure 8] FIG. 8 is a communication flow diagram illustrating communication flow between system entities for implementing the method of FIG. [Figure 9] FIG. 9 is a flow chart illustrating method steps included in a non-fungible token transfer workflow within the method of FIG. [Figure 10] FIG. 10 is a flow chart illustrating the method steps involved in accessing and managing non-fungible tokens via the non-fungible token management portal. [Figure 11] FIG. 11 is a communication flow diagram illustrating communication flow between system entities for implementing the method of FIG. [Figure 12] FIG. 12 illustrates an exemplary system for implementing the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] The present invention provides a solution for the generation and transfer of non-fungible tokens for implementation within cloud-based service systems, and more specifically within cloud gaming systems.

[0017] The method of the present invention may be implemented within a system environment 200 of the type shown in Figure 2. The system environment 200 includes one or more client devices 202 (e.g., any of a laptop 202a, a desktop 202b, a mobile device 202c, and / or a set-top box 202d) that interface with a server 206 via a network 204. The server 206 may be configured to support a traditional server-client configuration in which the client devices 202 communicate with the server 206 for any one or more of several purposes, such as, for example, downloading software applications, configuring the downloaded software applications, updating the downloaded software applications, or enabling the client devices 202 to upload or download data.

[0018] Alternatively, the server 206 may be configured to provide cloud-based service(s) to a requesting client device 202. In this case, software applications required by the client device 202 are installed and executed on the server 206, and video and audio output data from the software applications are streamed and rendered to the client device 202. Input received from a user or operator of the client device 202 is then transmitted to the server 206 and used to control the execution of the software applications running on the server 206.

[0019] Thus, for example, in a cloud-based gaming environment, game software is installed on a hardware device configured to execute the game software and integrated or coupled with a server 206. The game software runs on the hardware device and video and audio gameplay data is streamed from the hardware device (optionally via server 206) to a client device 202 where it is rendered for display and / or audio playback. A game layer operating a client device 202 uses the interface controls of the client device 202 to provide gameplay input. This gameplay input is streamed back to the hardware device on which the game software is running and used as gameplay control input for the game software running on the hardware device.

[0020] FIG. 3 illustrates a more particular embodiment of a system environment 300 of the type more generally described in connection with FIG.

[0021] The system environment 300 comprises one or more client devices 302 (e.g., any of a laptop 302a, a desktop 302b, a mobile device 302c, and / or a set-top box 302d) that interface with a cloud services server system 306 via a communications network, such as a data network or the Internet (not shown). The cloud services server system 306 may comprise (or be coupled with) multiple individual or separate hardware systems, each configured to provision, instantiate, and execute individual instances of one or more software applications. As a result, the cloud services server system 306 may utilize multiple individual or separate hardware systems to simultaneously execute software instance #1 (306a), software instance #2 (306b), software instance #n (306c), such that video and / or audio data from each of these software instances 306a-306c may be streamed to one or more requesting client devices 302a-302d.

[0022] For example, client device 302a may request cloud-based execution of a first software application from cloud services server system 306. Cloud services server system 306 may then respond by (i) instantiating a first instance of this first software application for execution on a first hardware system, and (ii) streaming video and / or audio data from the first instance of the claimed first software application to client device 302a.

[0023] Client device 302b may request cloud-based execution of a second software application (which may be the same as the first software application or may comprise a different software application) from cloud services server system 306, and cloud services server system 306 may respond by (i) instantiating a second instance of this second software application for execution on a second hardware system, and (ii) streaming video and / or audio data from the second instance of the second software application to client device 302a.

[0024] The client device 302c is connected to n software applications (which may be the same as either the first or second software application, or may be different from both). th A cloud-based execution of the software application may be requested from the cloud services server system 306, which in turn may (i) th Instantiate n instances of the software application to create n th (ii) executing said n th The n instances of the software application may respond by streaming video and / or audio data from the n instances of the software application to the client device 302c.

[0025] FIG. 4 illustrates an example configuration of a system 400 configured to enable the creation of non-fungible tokens associated with cloud-based services in accordance with the present disclosure.

[0026] As shown in FIG. 4, the system 400 may include a client terminal 402, a cloud service server 404, and an NFT service platform 406.

[0027] The client terminal 402 may comprise any processor-based client device or terminal through which a user accesses cloud-based services. In various examples, the client terminal 402 may include any of a laptop, desktop, mobile device, or set-top box configured to interface with the cloud services server 404 over a data network or a communications network, such as the Internet. The client terminal 402 implements therein a cloud services application interface 4022 configured to enable the client terminal 402 to communicate with the cloud services server 404 over the data network or communications network and receive one or more cloud-based services from the cloud services server 404. In various embodiments, the cloud services application interface 4022 may comprise an interface provided by a cloud services client software application or by a web browser-based interface implemented within the client terminal 402.

[0028] The cloud services server 404 may comprise any processor-based server having one or more cloud services application instances 4042 implemented thereon, and cloud-based services from the running cloud services application instances 404 are transmitted or delivered from the cloud services server 404 to the client terminals 402 over a communications network.

[0029] As described in more detail below, one or both of the client terminal 402 and the cloud services server 404 are further configured to enable generation of non-fungible tokens based on media content generated or delivered pursuant to cloud-based services provided by the cloud services server 404 to the client terminal 402.

[0030] The NFT service platform 406 comprises a server-implemented platform communicatively coupled to or in network communication with the cloud service server 404. One or both of the cloud service server 404 and the NFT service platform 406 are configured to enable non-fungible tokens generated according to the methods of the present invention to be published and stored in a blockchain infrastructure. As shown in FIG. 4, the NFT service platform 406 may comprise an NFT service layer 4062 comprising a processor-implemented software interface that enables the cloud service server 404 (and / or the cloud service application instance 4042) to communicate with the NFT service platform 4062 for purposes of publishing, storing, retrieving, or otherwise accessing non-fungible tokens generated based on the cloud-based services provided by the cloud service server 4040 to the client terminal 402. The NFT service layer 4062 may be configured to communicate with one or more blockchain networks or elements of a blockchain infrastructure, including, but not limited to, the InterPlanetary File System (IFPS) distributed storage system 4044, the Ethereum blockchain network 4046, the Stellar blockchain network 4068, or any other blockchain network or blockchain data storage system. Non-fungible tokens generated in accordance with the disclosure of the present invention may be stored within said blockchain infrastructure by the NFT service layer 4062 interacting with any such blockchain network or element of the blockchain infrastructure.

[0031] The system 400 of FIG. 4 may be used to implement any of the methods described later in this description.

[0032] 5 is a flow chart illustrating method steps involved in generating non-fungible tokens based on media content associated with a cloud-based service. In one embodiment, the method of FIG. 5 may be implemented within system 400, as described in connection with FIG.

[0033] Step 502 includes initiating a cloud service network communication session between a cloud services server 404 and a client terminal 402. In one embodiment, the initiated cloud service network communication session may comprise a network communication session involving at least one of a cloud service application instance 4042 and a cloud service application interface 4022. A cloud service network communication session may function as a network communication session in which cloud-based software services implemented within a cloud service application instance 4042 are delivered to a user via a client terminal 402. Initiation of the cloud service network communication session may include establishing a physical or logical data communication channel between the cloud services server 404 and the client terminal 402. Following initiation of the cloud service network communication session, transmission of video and / or audio data to the client terminal 402 occurs during the network communication session, and in one embodiment, the transmission may be effected via the physical or logical data communication channel established between the cloud services server 404 and the client terminal 402. In one embodiment of the invention, one or more of the remaining steps 504-518 of the method of FIG. 5 may be performed within the duration of the cloud service network communication session.

[0034] Step 504 includes receiving user input at the client terminal 402 to initiate generation of a non-fungible token. User input may be received via a user interface provided by the client terminal 402 and may include instructions to generate a non-fungible token including media content generated or delivered at the client terminal 402 as a result of the cloud-based service provided at the client terminal 402 within the cloud services network communication session by a cloud services server 404. Here, the client terminal 402 may be configured to generate and send to the cloud services server 404 instructions to generate the non-fungible token based on the user input received at the client terminal 402.

[0035] Step 506 includes receiving at the client terminal 402 (i) user input identifying media content for inclusion within the non-fungible token, and (ii) optionally, a non-fungible token template for the non-fungible token. The non-fungible token template may be selected from among a plurality of available non-fungible token templates based on user input or selection received at the client terminal 402. The non-fungible token template includes data that determines a layout / format / template for display, presentation, or playback of the non-fungible token. The received user input may be transmitted from the client terminal 402 to a cloud services server 404.

[0036] Step 508 includes generating a non-fungible token data record representing the non-fungible token, where the generation of the non-fungible token record is based on the identified media content and, optionally, the identified non-fungible token template. In various embodiments, the non-fungible token data record may be generated at either the client terminal 402 or the cloud services server 404. In embodiments where the non-fungible token data record is generated at the cloud services server 404, the step of generating the non-fungible token precedes the transmission of the identified media content and, optionally, the non-fungible token template from the client terminal 402 to the cloud services server 404.

[0037] Step 510 includes storing the generated non-fungible token data record in the cloud services server 404 .

[0038] Step 512 may include transmitting an instruction from the cloud services server 404 to the NFT service platform 406 to record or publish a non-fungible token on a blockchain, the published non-fungible token being based on the non-fungible token data record generated in step 508. Step 512 may further include transmitting the non-fungible token record from the cloud services server 404 to the NFT service platform 406.

[0039] Step 514 includes publishing the non-fungible token on one or more blockchains, which may be implemented in NFT service platform 406. In one embodiment, publishing the non-fungible token in step 514 may include storing data in the generated non-fungible token data record in any blockchain communicatively coupled or in network communication with NFT service platform 406.

[0040] Step 516 includes transmitting details of the published non-fungible token from the NFT service platform 406 to the cloud services server 404.

[0041] Step 518 includes optionally performing, at the cloud services server 404, (i) storing the received details of the published non-fungible token, and / or (ii) associating the received details of the published non-fungible token with the stored non-fungible token data record.

[0042] FIG. 6 is a communication flow diagram illustrating communication flow between system entities for implementing the method of FIG.

[0043] Step 6002 includes initiating a cloud services network communication session between the cloud services server 604 and the client terminal 602. The cloud services network communication session can function as a network communication session through which cloud-based software services implemented by the cloud services server 604 are delivered to a user via the client terminal 602.

[0044] Step 6004 includes receiving user input at the client terminal 602 initiating generation of a non-fungible token. The user input may be received via a user interface provided by the client terminal 602 and may include instructions to generate a non-fungible token that includes media content generated or delivered at the client terminal 602 as a result or consequence of the cloud-based service provided at the client terminal 602 within the cloud services network communication session by a cloud services server 604.

[0045] Step 6006 includes optionally receiving, at the client terminal 602, (i) user input identifying media content for inclusion within the non-fungible token, and (ii) a non-fungible token template for the non-fungible token. The non-fungible token template may be selected from among a plurality of available non-fungible token templates based on user input or selection received at the client terminal 602.

[0046] Step 6008 includes transmitting from client terminal 602 to cloud services server 604 (i) the identified media content and (ii) optionally, the identified non-fungible token template.

[0047] The cloud services server 604 then generates and stores a non-fungible token data record representing the non-fungible token, where generation of the non-fungible token is based on the identified media content and, optionally, the identified non-fungible token template received from the client terminal 602.

[0048] Step 6010 includes sending an instruction from the cloud services server 604 to the NFT service platform 606 to publish a non-fungible token on a blockchain, where the published non-fungible token is based on the non-fungible token data record generated by the cloud services server 604.

[0049] The NFT service platform 606 then publishes the non-fungible token on one or more blockchains. In one embodiment, publishing the non-fungible token may include storing data in the generated non-fungible token data record in any blockchain communicatively coupled or in network communication with the NFT service platform 606.

[0050] Step 6012 includes transmitting details of the published non-fungible token from the NFT service platform 606 to the cloud services server 404.

[0051] The cloud services server 604 then performs the steps of (i) storing the received details of the published non-fungible token, and / or (ii) associating the received details of the published non-fungible token with the stored non-fungible token data record.

[0052] Step 6014 includes sending a confirmation of successful generation and issuance of the non-fungible token from the cloud services server 604 to the client terminal 602 .

[0053] 7 is a flow chart illustrating method steps involved in transferring a non-fungible token associated with a cloud-based service. In one embodiment, the method of FIG. 7 may be implemented within system 400, as described in connection with FIG.

[0054] Step 702 includes receiving user input at client terminal 402 initiating transmission of a request to display purchasable non-fungible tokens associated with a cloud service application or cloud service server. User input may include input specifying or selecting a cloud service application or cloud service server with which the non-fungible token is to be associated. In one embodiment, by specifying or selecting a cloud service application or cloud service server with which the non-fungible token is to be associated, the user input seeks to ensure that the displayed non-fungible token includes media content that corresponds to, is associated with, or is generated by the specified cloud service application cloud service server.

[0055] Step 704 includes retrieving from the cloud services server 404 (i) data corresponding to a set of non-fungible tokens associated with the cloud services application or the cloud services server and / or including media content associated with, corresponding to, or generated by the cloud services application or the cloud services server, and (ii) data available for purchase / transfer.

[0056] Step 706 includes displaying, at client terminal 402, the retrieved data corresponding to the identified set of non-fungible tokens.

[0057] Step 708 includes receiving user input at the client terminal 402 selecting one or more non-fungible tokens within the identified set of non-fungible tokens for purchase / transfer.

[0058] Step 710 involves sending a request from the client terminal 402 to the cloud services server 404 to reserve the selected non-fungible token for purchase / transfer.

[0059] Step 712 includes sending a request from the cloud services server 404 to the NFT service platform 406 to reserve the selected non-fungible tokens for purchase / transfer, where the reserved non-fungible tokens cannot be purchased by or transferred to any third party during the period of the reservation.

[0060] Step 714 includes responding to a confirmation or acknowledgment message from the NFT service platform 406 that the selected non-fungible tokens have been reserved for purchase / transfer by initiating payment for the purchase / transfer of the selected non-fungible tokens.

[0061] In step 716, following a confirmation or acknowledgement message confirming successful completion of the payment, a transfer workflow (NFT transfer workflow) for transferring ownership of the non-fungible token to the purchaser / transferee is initiated in the NFT service platform 406. Transferring ownership of the non-fungible token to the purchaser / transferee includes recording the transfer of ownership on a distributed blockchain ledger on which the non-fungible token is recorded.

[0062] Once the NFT transfer workflow is completed, step 718 includes sending a confirmation of successful completion of the transfer of the purchased / transferred non-fungible token to the client terminal 402.

[0063] FIG. 8 is a communication flow diagram illustrating communication flow between system entities for implementing the method of FIG.

[0064] Step 8002 includes receiving user input at a client terminal 802 initiating a display of purchasable non-fungible tokens associated with a cloud service application or cloud service server. The user input may include input specifying or selecting a cloud service application or cloud service server with which the non-fungible token is to be associated. In one embodiment, by specifying or selecting a cloud service application or cloud service server with which the non-fungible token is to be associated, the user input seeks to ensure that the displayed non-fungible token includes media content that corresponds to, is associated with, or is generated by the specified cloud service application or cloud service server.

[0065] Step 8004 includes retrieving from cloud services server 804 (i) data corresponding to a set of non-fungible tokens associated with, and / or including media content associated with, corresponding to, or generated by, the cloud services application or the cloud services server, and (ii) data available for purchase / transfer.

[0066] The retrieved data corresponding to the identified set of non-fungible tokens is displayed on a display at the client terminal 802 .

[0067] Step 8006 includes receiving user input at the client terminal 802 selecting one or more non-fungible tokens within the set of identified non-fungible tokens for purchase / transfer.

[0068] Step 8008 includes sending a request from the client terminal 802 to the cloud services server 804 to reserve the selected non-fungible tokens for purchase / transfer. Step 8010 includes sending the request from the cloud services server 804 to the NFT service platform 806 to reserve the selected non-fungible tokens for purchase / transfer.

[0069] In response to the request sent from the cloud services server 804, the NFT service platform 806 (at step 8010) reserves the selected non-fungible tokens for purchase / transfer within the applicable blockchain infrastructure and prevents the reserved non-fungible tokens from being purchased or transferred by any third party during the period of the reservation.

[0070] Step 8012 includes sending a confirmation or acknowledgement message from the NFT service platform 806 to the cloud services server 804 confirming successful reservation of the selected non-fungible token. Step 8014 includes sending a confirmation or acknowledgement message from the cloud services server 804 to the client terminal 802 confirming successful reservation of the selected non-fungible token.

[0071] Step 8016 includes responding to a confirmation or acknowledgment message received at client terminal 802 confirming that the selected non-fungible token has been reserved / reserved for purchase / transfer by initiating a payment for the purchase / transfer of the selected non-fungible token. Step 8018 includes initiating a payment workflow to effect the payment from the purchaser / transferee to the seller.

[0072] In step 8020, following a confirmation or acknowledgement message confirming successful completion of the payment, a transfer workflow (NFT transfer workflow, non-fungible token transfer workflow) is initiated between the NFT service platform 806 and the cloud services server 804 to transfer the purchased / transferred non-fungible token to the purchaser / destination.

[0073] Upon completion of the NFT transfer workflow, step 8022 includes sending a confirmation or acknowledgement message from the NFT service platform 806 to the cloud services server 804 confirming successful execution of the transfer of the selected non-fungible token. Step 8024 includes sending a confirmation or acknowledgement message from the cloud services server 804 to the client terminal 802 confirming successful execution of the transfer of the selected non-fungible token.

[0074] Figure 9 is a flow chart illustrating method steps included in a non-fungible token transfer workflow within the method of Figure 7. In one embodiment, the non-fungible token transfer workflow may be implemented within step 716 of the method of Figure 7 or within step 8020 of the communication flow of Figure 8. In one embodiment, the method of Figure 9 may be implemented within an NFT service platform 406, 806.

[0075] Step 902 of the method of FIG. 9 includes determining the availability of an address for a crypto wallet of a purchaser or intended purchaser of one or more non-fungible tokens.

[0076] In response to (i) the availability of a buyer's crypto wallet address and (ii) expiration of any applicable refund hold period, step 904 includes transferring the purchased non-fungible tokens to the buyer's crypto wallet. For purposes of step 904, it will be understood that a refund hold period may include a predefined period during which the buyer may initiate a payment cancellation procedure or a payment refund procedure. The purchased non-fungible tokens are required to be reserved and held without transfer until expiration of the predefined refund hold period, and may only be transferred to the purchase after expiration of such period.

[0077] Step 906 of transferring the purchased non-fungible tokens to the purchaser's crypto wallet in response to (i) the unavailability of the purchaser's crypto wallet address and (ii) the expiration of any applicable refund hold period includes: · Transferring the purchased non-fungible tokens to an administrator account maintained by the cloud services server 404. Recording, in the cloud services server 404 or the administrator account, an association between the purchased non-fungible token and a unique identifier associated with the purchaser, thereby enabling the purchased non-fungible token to be subsequently transferred to a crypto wallet owned or controlled by the purchaser and also associated with the unique identifier associated with the purchaser.

[0078] The method of Figure 9 provides a significant advantage in that it allows for the purchase and storage of non-fungible tokens even if a purchaser does not have a crypto wallet account in which to store the purchased non-fungible tokens. By allowing a purchaser to store a purchased non-fungible token in a cloud services server or administrator account along with an identifier that associates the non-fungible token with the purchaser, the method of Figure 9 allows a purchaser to purchase, store, and subsequently transfer or trade non-fungible tokens without the need for a crypto wallet account.

[0079] Furthermore, by implementing a refund withholding period (e.g., in steps 904 or 906 of the method of FIG. 9), the present invention ensures compliance with the payment and refund policies of various software application distribution platforms (e.g., Google™ PlayStore or Apple™ AppStore) and ensures that application software implementing the methods of the present invention may be distributed through such platforms.

[0080] 10 is a flow chart illustrating method steps involved in accessing and managing non-fungible tokens through a non-fungible token management portal. In one embodiment, the non-fungible token management portal may be implemented in or via an NFT management portal server. In one embodiment, the NFT management portal server may be implemented within or comprise part of the NFT service platform 406 of FIG.

[0081] In step 1002, a user logs in to the NFT management portal server via a client terminal 402.

[0082] Step 1004 includes selecting a cloud service application / cloud service server based on user input received at client terminal 402. By selecting a cloud service application / cloud service server, the user seeks to search for or browse non-fungible tokens for purchase selections, including media content associated with or generated based on the selected cloud service application / cloud service server.

[0083] Step 1006 includes receiving a user ID via user input via client terminal 402. The received user ID comprises an identifier uniquely associated with the user within a record of the selected cloud service application / cloud service server.

[0084] Step 1008 includes initiating a communication session between the NFT management portal server and the selected cloud service application / cloud service server.

[0085] Step 1010 includes identifying a set of non-fungible tokens associated with or owned by the user and concurrently associated with the cloud services application / cloud services server based on the received user ID. In one embodiment, step 1010 may include identifying one or more non-fungible tokens associated with or linked to the received user ID from a database of non-fungible tokens associated with the cloud services application / cloud services server.

[0086] Step 1012 includes enabling the user, via the client terminal 402, to view and / or trade and / or transfer rights in the acquired set of non-fungible tokens at the NFT management portal server.

[0087] FIG. 11 is a communication flow diagram illustrating communication flow between system entities for implementing the method of FIG.

[0088] In step 11002 , the user enters login information at the client terminal 1102 .

[0089] Step 11004 includes transmitting the login information from the client terminal 1102 to the NFT management portal server 1104. The NFT management portal server 1104 uses the received login information to authenticate the identity of the user, and if it is found that the user has an account / access rights in the NFT management portal, uses the login information to enable the user to log in to the NFT management portal.

[0090] In step 11006, user input is received at client terminal 1102 identifying a cloud services application / cloud services server. By identifying or selecting a cloud services application / cloud services server, the user wishes to search for or browse non-fungible tokens for purchase selections, including media content associated with or generated based on the identified cloud services application / cloud services server.

[0091] Step 11008 includes transmitting data identifying the cloud service application / cloud service server from the client terminal 1102 to the NFT management portal server 1104.

[0092] Step 11010 includes receiving a user ID by user input via client terminal 1102. The received user ID comprises an identifier uniquely associated with the user within a record of the selected cloud service application / cloud service server.

[0093] Step 11012 includes transmitting the received user ID from the client terminal 1102 to the NFT management portal server 1104.

[0094] Step 11014 includes initiating a communication session between the NFT management portal server 1102 and the selected cloud service application / cloud service server 1106.

[0095] Step 11016 includes sending the user ID from the NFT management portal server 1104 to the cloud service application / cloud service server 1106.

[0096] Using or based on the received user ID, the cloud services application / cloud services server 1106 identifies a set of non-fungible tokens associated with or owned by the user and simultaneously associated with the cloud services application / cloud services server 1106. In one embodiment, the cloud services application / cloud services server 1106 may identify non-fungible tokens from a database of non-fungible tokens associated with the cloud services application / cloud services server 1106, and the identified non-fungible tokens are associated or linked to the received user ID.

[0097] Step 11018 includes retrieving the identified non-fungible token from the cloud service application / cloud service server 1106 to the NFT management portal server 1104.

[0098] Step 11020 then includes enabling the user, via the client terminal 1102, to view and / or trade and / or transfer rights in the extracted non-fungible token at the NFT management portal server 1104.

[0099] In certain embodiments, the present invention provides a method for recording digital media-based non-fungible tokens on a distributed blockchain ledger, the method including: (i) establishing a cloud services network communication session between the cloud services server and a client terminal, where establishing the cloud services network communication session includes allocating a network communication channel between the cloud services server and the client terminal to the cloud services network communication session; (ii) streaming data generated by an instance of a software application running on the cloud services server from the cloud services server to the client terminal over the network communication channel; and (iii) transmitting data generated by an instance of a software application running on the cloud services server from the cloud services server to the client terminal through the client terminal. (b) receiving user input identifying the selected digital media content; (iv) generating a non-fungible token record representing the non-fungible token, wherein the non-fungible token record includes data identifying or representing the selected media content; and (v) implementing a record of the non-fungible token on a distributed blockchain ledger, including: (c) transmitting the non-fungible token record to a non-fungible token service platform; and (d) storing data from the non-fungible token record in a record block associated with the distributed blockchain ledger.

[0100] In one embodiment of the method, (i) the user input received via the client terminal further identifies a non-fungible token template, and (ii) the generated non-fungible token record includes data representative of the non-fungible token template, the non-fungible template including data determining a layout, format, or template for display, presentation, or playback of the non-fungible token.

[0101] In another method embodiment, the cloud services server (i) receives from the client terminal the instruction to generate the non-fungible token and the user input identifying the selected digital media content, (ii) generates the non-fungible token record, (iii) stores the generated non-fungible token record in a memory coupled to the cloud services server, (iv) sends an instruction to the non-fungible token service platform to record the non-fungible token on the distributed blockchain ledger, and (v) receives data representing details of the recorded non-fungible token following the recording of the non-fungible token on the distributed blockchain ledger by the non-fungible token service platform.

[0102] In a further embodiment of the method, the cloud services server (i) stores the received data representing details of the recorded non-fungible token; and (ii) associates the details of the recorded non-fungible token with the stored non-fungible token data record.

[0103] The present invention also provides a method for recording a transfer of digital media-based non-fungible tokens on a distributed blockchain ledger, the method including: (i) receiving, at a cloud services server, a request for a representation of digital media-based non-fungible tokens associated with the cloud services server or a cloud services application running on the cloud services server; (ii) obtaining data corresponding to a set of digital media-based non-fungible tokens associated with the cloud services server or cloud services application; (iii) performing a display of the obtained data corresponding to the set of non-fungible tokens; (iv) receiving user input selecting a non-fungible token from within the set of digital media-based non-fungible tokens; and (v) sending a request to a non-fungible token service platform to schedule a transfer of the selected non-fungible token. (vi) responding to a confirmation message from the non-fungible token service platform confirming that the selected non-fungible token has been scheduled for transfer by performing a payment transaction to transfer the selected non-fungible token to the identified destination; and (vii) initiating recording of the transfer of the selected non-fungible token to the identified destination in a record block associated with the distributed blockchain ledger after the payment transaction for the transfer of the selected non-fungible token to the identified destination is completed.

[0104] The present invention also provides a system for recording digital media-based non-fungible tokens on a distributed blockchain ledger, the system including a processor implemented in a cloud services server configured to: (i) establish a cloud services network communication session between the cloud services server and a client terminal, where establishing the cloud services network communication session includes allocating a network communication channel between the cloud services server and the client terminal to the cloud services network communication session; (ii) stream data generated by an instance of a software application running on the cloud services server from the cloud services server to the client terminal over the network communication channel; and (iii) transmit, through the client terminal, data generated by an instance of a software application running on the cloud services server from the cloud services server to the client terminal via the network communication channel; (b) receiving user input identifying the selected digital media content; (iv) generating a non-fungible token record representing the non-fungible token, wherein the non-fungible token record includes data identifying or representing the selected media content; and (v) implementing the non-fungible token record on a distributed blockchain ledger includes sending the non-fungible token record to a non-fungible token service platform, wherein the non-fungible token service platform stores data from the non-fungible token record in a record block associated with the distributed blockchain ledger.

[0105] In one embodiment, the system may be configured such that (i) the user input received via the client terminal further identifies a non-fungible token template, and (ii) the generated non-fungible token record includes data representative of the non-fungible token template, the non-fungible template including data determining a layout, format, or template for display, presentation, or playback of the non-fungible token.

[0106] In another system embodiment, a cloud services server (i) receives from the client terminal an instruction to generate a non-fungible token and the user input identifying the selected digital media content, (ii) generates the non-fungible token record, (iii) stores the generated non-fungible token record in a memory coupled to the cloud services server, (iv) sends an instruction to the non-fungible token service platform to record the non-fungible token on the distributed blockchain ledger, and (v) receives data representing details of the recorded non-fungible token following the recording of the non-fungible token on the distributed blockchain ledger by the non-fungible token service platform.

[0107] In another system embodiment, the cloud services server (i) stores the received data representing details of the recorded non-fungible token, and (ii) associates the details of the recorded non-fungible token with the stored non-fungible token data record.

[0108] In another embodiment, the present invention provides a system for recording transfers of digital media-based non-fungible tokens on a distributed blockchain ledger, the system including a processor-implemented cloud services server configured to (i) receive, at the cloud services server, a request for display of digital media based on non-fungible tokens associated with the cloud services server or a cloud services application executing on the cloud services server, (ii) obtain data corresponding to a set of digital media-based non-fungible tokens associated with the cloud services server or the cloud services application, (iii) perform a display of the obtained data corresponding to the set of non-fungible tokens, and (iv) (v) sending a request to schedule a transfer of the selected non-fungible token to a non-fungible token service platform, wherein the non-fungible token service platform is configured to record the transfer of the non-fungible token in a distributed blockchain ledger in which the selected non-fungible token is recorded; (vi) responding to a confirmation message from the non-fungible token service platform confirming that the selected non-fungible token has been scheduled for transfer by performing a payment transaction to transfer the selected non-fungible token to an identified destination; and (vii) initiating recording the transfer of the selected non-fungible token to the identified destination in a record block associated with the distributed blockchain ledger after the payment transaction for the transfer of the selected non-fungible token to the identified destination is completed.

[0109] The present invention provides a computer program product for recording digital media-based non-fungible tokens on a distributed blockchain ledger, the computer program product comprising a non-transitory computer readable medium having computer readable program code embodied therein, the computer readable program code including instructions for performing the steps of: (i) establishing a cloud service network communication session between a cloud services server and a client terminal, where establishing the cloud service network communication session includes allocating a network communication channel between the cloud services server and the client terminal to the cloud service network communication session; (ii) streaming data generated by an instance of a software application running on the cloud services server from the cloud services server to the client terminal via the network communication channel; (iii) receiving, through the client terminal, (a) instructions to generate a non-fungible token including selected digital media content from the data streamed from the cloud services server to the client, and (b) user input identifying the selected digital media content; (iv) generating a non-fungible token record representing the non-fungible token, where the non-fungible token record includes data identifying or representing the selected media content; and (v) implementing a record of the non-fungible token on a distributed blockchain ledger, including: (c) transmitting the non-fungible token record to a non-fungible token service platform; and (d) storing data from the non-fungible token record in a record block associated with the distributed blockchain ledger.

[0110] The present invention also provides a computer program product for recording a transfer of digital media-based non-fungible tokens on a distributed blockchain ledger, the computer program product comprising a non-transitory computer readable medium having computer readable program code embodied thereon, the computer readable program code comprising instructions for performing the steps of: (i) receiving, at a cloud services server, a request for a display of digital media-based non-fungible tokens associated with the cloud services server or a cloud service application running on the cloud services server, (ii) obtaining data corresponding to a set of digital media-based non-fungible tokens associated with the cloud services server or a cloud service application running on the cloud services server, (iii) performing a display of the obtained data corresponding to the set of non-fungible tokens, (iv) receiving user input selecting a non-fungible token from within the set of digital media-based non-fungible tokens, and (v) sending a request to a non-fungible token service platform to schedule a transfer of the selected non-fungible token, wherein wherein the non-fungible token service platform is configured to record the transfer of the non-fungible token in a distributed blockchain ledger in which the selected non-fungible token is recorded; (vi) respond to a confirmation message from the non-fungible token service platform confirming that the selected non-fungible token has been scheduled for transfer by executing a payment transaction to transfer the selected non-fungible token to the identified destination; and (vii) initiate recording of the transfer of the selected non-fungible token to the identified destination in a record block associated with the distributed blockchain ledger after the payment transaction for the transfer of the selected non-fungible token to the identified destination is completed.

[0111] FIG. 12 illustrates an exemplary system 1200 for implementing the invention. The illustrated system 1200 includes a computer system 1202 including one or more processors 1204 and at least one memory 1206. The processor 1204 is configured to execute program instructions and can be a real or virtual processor. It will be understood that the computer system 1202 does not suggest any limitation as to the scope of use or functionality of the described embodiments. The computer system 1202 can include, but is not limited to, one or more of a general purpose computer, a programmed microprocessor, a microcontroller, an integrated circuit, and other devices or arrangements of devices capable of implementing steps constituting the method of the invention. Exemplary embodiments of the computer system 1202 according to the invention can include one or more servers, desktops, laptops, tablets, smartphones, mobile phones, mobile communication devices, tablets, phablets, and personal digital assistants. In one embodiment of the invention, the memory 1206 can store software for implementing various embodiments of the invention. The computer system 1202 can have additional components. For example, computer system 1202 may include one or more communication channels 1208, one or more input devices 1210, one or more output devices 1212, and storage 1214. An interconnection mechanism (not shown), such as a bus, controller, or network, interconnects the components of computer system 1202. In various embodiments of the invention, operating system software (not shown) uses processor 1204 to provide an operating environment for various software executing within computer system 1202 and manages different functions of the components of computer system 1202.

[0112] The communication channel 1208 enables communication over a communication medium to various other computing entities that provide information, such as program instructions, or other data in a communication medium, including, but not limited to, wired or wireless methods implemented with electrical, optical, RF, infrared, acoustic, microwave, Bluetooth, or other transmission medium.

[0113] The input devices 1210 may include, but are not limited to, a touch screen, a keyboard, a mouse, a pen, a joystick, a trackball, a voice device, a scanning device, or any other device capable of providing input to the computer system 1202. In one embodiment of the invention, the input devices 1210 may be a sound card or similar device that accepts audio input in analog or digital form. The output devices 1212 may include, but are not limited to, a user interface on a CRT, LCD, LED display, or any other display associated with any of the servers, desktops, laptops, tablets, smartphones, mobile phones, mobile communication devices, tablets, phablets, and personal digital assistants, printers, speakers, CD / DVD writers, or any other device that provides output from the computer system 1202.

[0114] The storage 1214 may include, but is not limited to, magnetic disks, magnetic tapes, CD-ROMs, CD-RWs, DVDs, any type of computer memory, magnetic stripes, smart cards, printed bar codes, or any other transitory or non-transitory medium used to store information and that can be accessed by the computer system 1202. In various embodiments of the present invention, the storage 1214 may contain program instructions for implementing any of the described embodiments.

[0115] In one embodiment of the invention, the computer system 1202 is part of a distributed network or set of available cloud resources.

[0116] The present invention can be implemented in numerous ways, including as a system, method, or computer program product, such as a computer readable storage medium or a computer network, where programming instructions are communicated from a remote location.

[0117] The present invention may suitably be embodied as a computer program product for use with the computer system 1202. The methods described herein are implemented as a computer program product, typically comprising a set of program instructions executed by the computer system 1202 or any other similar device. The set of program instructions may be, for example, a series of computer readable codes stored on a tangible medium, such as a computer readable storage medium (storage 1214) such as a diskette, CD-ROM, ROM, flash drive or hard disk, or may be transmittable to the computer system 1202 via a modem or other interface device, via any of the tangible media, including but not limited to optical or analog communication channels 1208. The implementation of the present invention as a computer program product may also be intangible, using wireless technologies, including but not limited to microwave, infrared, Bluetooth, or other transmission technologies. These instructions may be preloaded into the system, or may be recorded on a storage medium such as a CD-ROM, or may be available for downloading via a network, such as the Internet or a cellular phone network. The series of computer readable instructions may embody all or part of the functionality previously described herein.

[0118] The present invention thus enables straightforward, secure, and convenient generation of non-fungible tokens in connection with cloud-based services (e.g., cloud-based software gaming services), and provides a solution for securely buying, selling, or otherwise transferring ownership or control of such non-fungible tokens.

[0119] Although exemplary embodiments of the present invention are described and illustrated herein, it will be understood that they are merely exemplary. It will be understood by those skilled in the art that various modifications in form and details may be made without departing from or violating the scope of the present invention as defined by the appended claims. In addition, the present invention illustratively disclosed herein may suitably be practiced in the absence of elements not specifically disclosed herein, and is intended in certain specifically contemplated embodiments to be practiced in the absence of elements not specifically disclosed herein.

Claims

1. 1. A method for recording digital media-based non-fungible tokens on a distributed blockchain ledger, comprising: establishing a cloud service network communication session between a cloud service server and a client terminal, where establishing the cloud service network communication session includes allocating a network communication channel between the cloud service server and the client terminal to the cloud service network communication session; Streaming data generated by instances of software applications running on the cloud services server from the cloud services server to the client terminal over the network communications channel; receiving, via the client terminal, instructions to generate a non-fungible token including selected digital media content from the data streamed from the cloud services server to the client terminal, and user input identifying the selected digital media content; generating a non-fungible token record representing the non-fungible token, wherein the non-fungible token record includes data identifying or representing the selected media content; implementing a record of the non-fungible token on a distributed blockchain ledger, including sending the non-fungible token record to a non-fungible token service platform and storing data from the non-fungible token record in a record block associated with the distributed blockchain ledger.

2. The user input received via the client terminal further identifies a non-fungible token template; the generated non-fungible token record includes data representative of the non-fungible token template; 2. The method of claim 1, wherein the non-fungible template comprises data that determines a layout, format, or template for the display, presentation, or playback of the non-fungible tokens.

3. The cloud service server includes: receiving the instructions to generate the non-fungible token and the user input identifying the selected digital media content from the client terminal; generating said non-fungible token record; storing the generated non-fungible token record in a memory coupled to the cloud services server; sending an instruction to the non-fungible token service platform to record the non-fungible token on the distributed blockchain ledger; 2. The method of claim 1 , further comprising receiving data representing details of the recorded non-fungible token following recording of the non-fungible token on the distributed blockchain ledger by the non-fungible token service platform.

4. The cloud service server includes: storing the received data representative of details of the recorded non-fungible token; The method of claim 3 , further comprising: associating the recorded details of the non-fungible token with the stored non-fungible token data record.

5. 1. A method for recording transfers of digital media-based non-fungible tokens on a distributed blockchain ledger, comprising: receiving, at a cloud services server, a request for an indication of a digital media based non-fungible token associated with the cloud services server or a cloud services application executing on the cloud services server; obtaining data corresponding to a set of digital media-based non-fungible tokens associated with the cloud services server or cloud services application; performing a display of the obtained data corresponding to the set of non-fungible tokens; receiving a user input selecting a non-fungible token from within the set of digital media based non-fungible tokens; sending a request to schedule a transfer of the selected non-fungible token to a non-fungible token service platform, wherein the non-fungible token service platform is configured to record the transfer of the non-fungible token within a distributed blockchain ledger in which the selected non-fungible token is recorded; responding to a confirmation message from the non-fungible token service platform confirming that the selected non-fungible token has been scheduled for transfer by executing a payment transaction to transfer the selected non-fungible token to an identified destination; after the payment transaction for the transfer of the selected non-fungible tokens to the identified destination is completed, initiating recording of the transfer of the selected non-fungible tokens to the identified destination in a record block associated with the distributed blockchain ledger.

6. 1. A system for recording digital media-based non-fungible tokens on a distributed blockchain ledger, comprising: a processor implemented in a cloud services server; The cloud service server includes: establishing a cloud service network communication session between the cloud service server and a client terminal, where establishing the cloud service network communication session includes allocating a network communication channel between the cloud service server and the client terminal to the cloud service network communication session; Streaming data generated by instances of software applications running on the cloud services server from the cloud services server to the client terminal over the network communications channel; receiving instructions through the client terminal to generate a non-fungible token including selected digital media content from the data streamed from the cloud services server to the client terminal, and user input identifying the selected digital media content; generating a non-fungible token record representing the non-fungible token, wherein the non-fungible token record includes data identifying or representing the selected media content; and transmitting the non-fungible token record to a non-fungible token service platform, where the non-fungible token service platform implements the record of the non-fungible token on a distributed blockchain ledger, including storing data from the non-fungible token record in a record block associated with the distributed blockchain ledger.

7. The user input received via the client terminal further identifies a non-fungible token template; 7. The system of claim 6, wherein the generated non-fungible token record includes data representing the non-fungible token template, where the non-fungible template includes data determining a layout, format, or template for display, presentation, or playback of the non-fungible token.

8. The cloud service server includes: receiving the instructions to generate the non-fungible token and the user input identifying the selected digital media content from the client terminal; generating said non-fungible token record; storing the generated non-fungible token record in a memory coupled to the cloud services server; Sending an instruction to the non-fungible token service platform to record the non-fungible token on the distributed blockchain ledger; 7. The system of claim 6, further comprising: receiving data representing details of the recorded non-fungible token following recording of the non-fungible token on the distributed blockchain ledger by the non-fungible token service platform.

9. The cloud service server includes: storing the received data representative of details of the recorded non-fungible token; 9. The system of claim 8, further comprising: associating the recorded details of the non-fungible token with the stored non-fungible token data record.

10. 1. A system for recording transfers of digital media-based non-fungible tokens on a distributed blockchain ledger, comprising: a processor implemented in a cloud services server; configured to receive, at the cloud services server, a request to display digital media based on a non-fungible token associated with the cloud services server or a cloud services application executing on the cloud services server; obtaining data corresponding to a set of digital media-based non-fungible tokens associated with the cloud services server or cloud services application; performing a display of the obtained data corresponding to the set of non-fungible tokens; receiving a user input selecting a non-fungible token from within the set of digital media based non-fungible tokens; sending a request to schedule a transfer of the selected non-fungible token to a non-fungible token service platform, wherein the non-fungible token service platform is configured to record the transfer of the non-fungible token within a distributed blockchain ledger in which the selected non-fungible token is recorded; responding to a confirmation message from the non-fungible token service platform confirming that the selected non-fungible token has been scheduled for transfer by executing a payment transaction to transfer the selected non-fungible token to an identified destination; after the payment transaction for the transfer of the selected non-fungible token to the identified destination is completed, initiate recording of the transfer of the selected non-fungible token to the identified destination in a record block associated with the distributed blockchain ledger.

11. 1. A computer program product for recording digital media-based non-fungible tokens on a distributed blockchain ledger, comprising: A non-transitory computer readable medium having computer readable program code embodied therein; The computer readable program code comprises: establishing a cloud service network communication session between a cloud services server and a client terminal, where establishing the cloud service network communication session includes allocating a network communication channel between the cloud services server and the client terminal to the cloud service network communication session; Streaming data generated by instances of software applications running on the cloud services server from the cloud services server to the client terminal over the network communications channel; receiving, through the client terminal, instructions to generate a non-fungible token including selected digital media content from the data streamed from the cloud services server to the client, and user input identifying the selected digital media content; generating a non-fungible token record representing the non-fungible token, wherein the non-fungible token record includes data identifying or representing the selected media content; 2. A computer program product for implementing a record of the non-fungible token on a distributed blockchain ledger, including transmitting the non-fungible token record to a non-fungible token service platform and storing data from the non-fungible token record in a record block associated with the distributed blockchain ledger.

12. 1. A computer program product for recording digital media-based non-fungible tokens on a distributed blockchain ledger, comprising: A non-transitory computer readable medium having computer readable program code embodied therein; The computer readable program code comprises: establishing a cloud service network communication session between a cloud services server and a client terminal, where establishing the cloud service network communication session includes allocating a network communication channel between the cloud services server and the client terminal to the cloud service network communication session; Streaming data generated by instances of software applications running on the cloud services server from the cloud services server to the client terminal over the network communications channel; receiving, through the client terminal, instructions to generate a non-fungible token including selected digital media content from the data streamed from the cloud services server to the client, and user input identifying the selected digital media content; generating a non-fungible token record representing the non-fungible token, wherein the non-fungible token record includes data identifying or representing the selected media content; and transmitting the non-fungible token record to a non-fungible token service platform, where the non-fungible token service platform implements the record of the non-fungible token on a distributed blockchain ledger, including storing data from the non-fungible token record in a record block associated with the distributed blockchain ledger.

Images