Information processing method and computer program

Abstract

To provide an application performance processing method, an application performance processing system, and an application linking method that realize information sharing between applications using a blockchain system.SOLUTION: In an application performance processing method, a device that provides an application acquires application account data of a user of the application and blockchain account data of the user in a blockchain system, and transmits a request to the blockchain system in which a token based on the user's usage performance linked to the application is imparted to the blockchain account data of the user. The blockchain system accepts a request to confirm the presence or absence of a token for the user, the amount of tokens, and contents or condition data of the token.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] This application claims the benefit of priority to U.S. Provisional Patent Application No. 62 / 953,738, filed December 26, 2019, which is incorporated by reference in its entirety.

[0002] The present invention relates to an application record processing method, an application record processing system, and an application linking method that utilize a block chain. [Background technology]

[0003] In recent years, with regard to digital content (games, animation, television content, radio content, manga, magazines, newspapers, etc.), not only is primary content consumed by individuals (playing games, watching animation, watching television content, listening to radio content, reading manga, reading magazines, reading newspapers, etc.), but communities are also actively consuming n-th order content. In other words, the secondary commercial sphere for digital content is expanding. At the same time, the diversification of media through which individuals (content creators, athletes, entertainers, etc.) can disseminate content has progressed, and as with the digital content, the scope of content consumption for these individuals is expanding (e.g., watching the private lives of professional athletes through their YouTube (registered trademark) channels).

[0004] Moreover, the secondary trade area is constructed across multiple applications (for example, in the case of games, the game itself, a video distribution platform, SNS, etc.). When crossing applications in a secondary trade area, the challenge is information sharing between applications. To implement a link by returning activity in one application to activity in another application, it is necessary to link the accounts of a specific user in each application between the applications.

[0005] In the past, in application linkage, an API (Application Programming Interface) for providing user information in one application has been developed and provided (Patent Document 1, etc.). [Prior art documents] [Patent documents]

[0006] [Patent Document 1] JP 2019-057778 A Summary of the Invention [Problem to be solved by the invention]

[0007] When collaborating through APIs, the challenges are reducing the costs of developing and operating the APIs, as well as security risks.

[0008] The present invention has been made in consideration of the above circumstances, and aims to provide an application record processing method, an application record processing system, and an application cooperation method that realizes information sharing between applications using a blockchain system. [Means for solving the problem]

[0009] In one embodiment of the application history processing method of the present disclosure, a device providing an application acquires app account data of a user of the application and blockchain account data of the user in a blockchain system, and sends a request to the blockchain system to grant a token based on the user's usage history linked to the application to the user's blockchain account data, and the blockchain system accepts a request to confirm whether or not the user has the token, the amount of the token, or data on the contents or conditions of the token. Effect of the Invention

[0010] According to this disclosure, it is possible to link applications securely and at low cost by using a blockchain system, without the development and operating costs of APIs. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a schematic diagram of a system of the present disclosure. [Diagram 2] FIG. 2 is a sequence diagram showing the basics of application linkage processing in the system. [Diagram 3] FIG. 11 is a sequence diagram showing a processing procedure of an existing method for application cooperation in a comparative example. [Figure 4] FIG. 2 is a block diagram showing a configuration of an information terminal device. [Diagram 5] FIG. 2 is a block diagram showing a configuration of a management device. [Figure 6] A block diagram showing the configuration of a node in a blockchain system. [Figure 7] FIG. 11 is a sequence diagram illustrating an example of an authentication process procedure in application cooperation. [Figure 8] FIG. 11 is a sequence diagram illustrating an example of a processing procedure for confirming the contents of a token. [Figure 9] FIG. 11 is a sequence diagram illustrating an example of processing execution based on a ticket-type token. [Figure 10] 1 is a schematic diagram of a system according to a first embodiment. [Figure 11] FIG. 11 is a sequence diagram illustrating an example of a cooperation procedure between applications in the first embodiment. [Figure 12] FIG. 11 is a sequence diagram illustrating an example of a cooperation procedure between applications in the first embodiment. [Figure 13] FIG. 13 is a schematic diagram illustrating a structure of a rights token corresponding to an n-th usage related right in the second embodiment. [Figure 14] FIG. 11 is a schematic diagram of a system according to a second embodiment. [Figure 15] FIG. 11 is a sequence diagram illustrating an example of a cooperation procedure between applications according to the second embodiment. [Figure 16] FIG. 11 is a sequence diagram illustrating an example of a cooperation procedure between applications according to the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] The present disclosure will be specifically described with reference to the drawings showing the embodiments thereof.

[0013] In this disclosure, the term "blockchain system" refers to a system that includes multiple computers that can communicate with each other and a network that connects the multiple computers, and creates a blockchain through distributed processing of the multiple computers. In the blockchain, requested transactions are executed and the results are captured.

[0014] An example of secondary content consumption is the broadcasting of gameplay, which is the primary content, on a video distribution platform. Gameplay video broadcasts, especially live broadcasts, are completed and established online, with the secondary content of "other people's gameplay videos" being "watched together with other viewers," and the secondary content being the subject of "conversations between broadcasters and viewers on social media." The total viewing time of broadcasted videos across multiple major video distribution platforms is estimated to reach hundreds of millions of hours per month, and the secondary market for games as primary content is indeed booming.

[0015] For businesses that produce or operate games, which are primary content, the importance of indicators related to such secondary trade areas, such as the number of viewers per game for game-related broadcasts, is increasing. For example, some online games with hundreds of millions of players set indicators such as the number of viewers as KPIs (Key Performance Indicators) and incorporate official partner programs centered on live broadcasts to intentionally stimulate the secondary trade area. For example, official partner programs are programs that treat quality broadcasters who meet certain conditions as partners and support their online social activities with various non-financial benefits.

[0016] However, the challenge in revitalizing the secondary market, which is built across different applications such as the game itself, the distribution platform, and SNS, is the information sharing between the applications. Even in the above example of gameplay distribution, there is cross-pollination between the application for the "game" itself and the application for the video distribution platform. If a game operator wants to evaluate the video distribution activity of a specific game and give some kind of reward (such as items) to the distributor when playing the game, the game operator needs to link the distributor's account between the game and the video distribution platform.

[0017] When linking applications, generally, the party providing user information including usage history and results associated with an account (in the above example, the video distribution platform) needs to develop and operate an API that can be accessed by the party requesting the information. Moreover, this API needs to control access to the API after implementing authentication and authorization that complies with appropriate protocols (OAuth, OpenID Connect, etc.). Here, the cost of developing and operating the API and security risks become issues. In particular, even for large organizations, a large-scale leak of user information such as accounts can cause great damage, so increased security risks should be avoided as much as possible.

[0018] The party requesting user information and accessing the API, in the above example the operator of a specific game, is also subject to development and operation costs and security risks. For example, as a security risk, if the authorization protocol is OAuth, the party requesting user information must store secret information (access token) to access the user information. Storing secret information poses a major risk if it is leaked. Security risks and development and operation costs to match the API specifications of linked applications can become enormous in proportion to the number of linked applications.

[0019] In light of this situation, in order to revitalize secondary trade areas for content built across applications, a low-cost, secure method of sharing user information (mainly activity records that contribute to the revitalization of secondary trade areas, etc.) is required.

[0020] The application linkage method disclosed herein includes an information terminal device that stores app account data of a user of a first application and a second application, and blockchain account data of the user in a blockchain system, and transmits a request for linkage of the first and second applications to a first device that provides the first application or a second device that provides the second application, in association with the blockchain account data, and based on the request for linkage, causes the first device to transmit a request to the blockchain system to grant, to the blockchain account data, a token based on the user's usage history of the first application that is associated with the app account data, and causes the second device to obtain data on whether or not the token has been granted to the blockchain account data, the amount of the token, and the contents or conditions of the token.

[0021] In the application linking method of the present disclosure, publicly available digital assets are tokenized and shared between different applications. Digital assets are achievements, rights, etc. linked to each application program, and are different from crypto assets such as BTC or ETH. It is possible for an application to confirm that an asset, namely, a user's usage achievements in one application, is recorded in a blockchain system, thereby enabling the user to exercise rights regarding the other application.

[0022] The data recorded in the blockchain system has a high level of resistance to tampering due to its data structure, making it extremely difficult to perform unauthorized manipulation of the recorded data (such as granting rights). This allows for extremely secure sharing. Costs can also be reduced because there is no need for API development and operation costs.

[0023] Such an application linking method will now be described in detail.

[0024] 1 is a schematic diagram of a system 100 according to the present embodiment. The system 100 includes an information terminal device 1 of a first user outside a block chain system 300, and management devices 2A and 2B for different applications A and B, respectively. In the following embodiment, the link between two applications will be described as an example, but the same applies to the link between three or more applications.

[0025] The management device 2A can communicate with an instance based on a program for application A on the information terminal device 1 in a client-server relationship via a network N outside the block chain system 300. Similarly, the management device 2B can communicate with an instance based on a program for application B on the information terminal device 1. Note that the management devices 2A and 2B may be realized by instances of the applications A and B on the information terminal device 1.

[0026] In the system 100 of this embodiment, a user has an account (hereinafter referred to as an application account) that enables the user to sign in (log in) to both application A and application B on the information terminal device 1. Sign-in data for each of applications A and B is stored in the information terminal device 1 in advance or by a user's input operation.

[0027] The information terminal device 1 also stores account data (hereinafter referred to as a blockchain account) in the blockchain system 300 and is capable of accessing the blockchain system 300. In this disclosure, the term "blockchain system" refers to a system that includes multiple computers that can be communicatively connected to each other and a network that connects the multiple computers, and creates a blockchain through distributed processing of the multiple computers.

[0028] The management devices 2A and 2B hold blockchain accounts and are able to broadcast transactions to the blockchain system 300 and view data within blocks imported into the blockchain system 300.

[0029] The system 100 of this embodiment utilizes the blockchain system 300 as a digital asset management platform, and treats the user's activity results that can be disclosed as digital assets and tokenizes them to make them shareable between different applications A and B used by the user. Here, the digital assets are results or rights linked to the applications and are different from crypto assets.

[0030] Digital assets equivalent to activity records and rights are implemented as smart contracts in the blockchain system 300 and are deployed according to the execution and use of the user's applications A and B. The token holding status in the blockchain system 300 is managed by the smart contract of the digital assets. The smart contract equivalent to the digital assets is hereinafter referred to as the token contract.

[0031] In the system 100, the management devices 2A and 2B each have an account management function that performs authentication of a user's blockchain account, and a digital asset management function that tokenizes achievements in applications A and B as digital assets.

[0032] In the account management function, when an account linking request is received from a user's information terminal device 1, the management devices 2A and 2B of the applications A and B respectively execute a process to authenticate the existence of the user's blockchain account.

[0033] The functions of holding a blockchain account (including a private key, which will be described later) in the management devices 2A and 2B, broadcasting a transaction to the blockchain system 300, and browsing data in a block imported into the blockchain system 300 may be implemented separately from the applications provided by the management devices 2A and 2B. Functions related to the blockchain system 300 (account management function, digital asset management function) may be provided as SaaS or PaaS implemented between the management devices 2A and 2B and the blockchain system 300. Furthermore, these functions may be available to the user via an application running on the information terminal device 1.

[0034] FIG. 2 is a sequence diagram showing the basics of application linkage processing in the system 100. As shown in FIG.

[0035] In the system 100, a request for application cooperation including account data of application A is transmitted from the user's information terminal device 1 to the management device 2A via a program for application A (step S1).

[0036] An authentication process for the user's blockchain account is executed between the information terminal device 1, the management device 2A, and the blockchain system 300 (step S2).

[0037] Based on the digital asset management function, the management device 2A creates a transaction to grant a digital asset, which is a publicly available activity record (excluding crypto assets) in application A linked to the user's account data, to the user's blockchain account (step S3). The management device 2A broadcasts the created transaction to the blockchain system 300 (step S4).

[0038] When the blockchain system 300 receives a transaction from the management device A (step S5), it verifies the transaction (step S6) and approves it (step S7). In step S7, the user's token contract updates the token holding status.

[0039] The user's information terminal device 1 transmits a request for application cooperation, including the account data of application B, to the management device 2B through the program for application B to be cooperated with (step S8).

[0040] An authentication process for the user's blockchain account is executed between the information terminal device 1, the management device 2B, and the blockchain system 300 (step S9).

[0041] The management device 2B checks the contents of the token linked to the user's blockchain account (step S10) and executes a linking process based on the contents checked in step S10 for the user's application account (step S11). The digital assets in the block imported into the blockchain system 300 can be checked from different applications A and B. Therefore, the performance of application A is tokenized and can be refunded based on this in application B.

[0042] With this procedure, the operators of applications A and B can implement authentication and management functions based on the user's blockchain account without needing to operate APIs for linking with other applications. Since the token is confirmed in the blockchain system 300, it can be implemented securely.

[0043] 2, a request for application cooperation is sent to the management device 2A when a user's operation is accepted by the information terminal device 1 used by the user. However, the present invention is not limited to this, and the request for cooperation may be sent at any timing, or may be started during the processing of applications A and B. A request to start cooperation may be sent to application A when a request is sent to the management device 2B.

[0044] Fig. 3 is a sequence diagram showing the processing procedure of an existing method of application cooperation as a comparative example. The sequence diagram in Fig. 3 shows the processing of "OAuth 2.0 Authorization Code Grant". In the existing method, as shown in the sequence diagram in Fig. 3, when a request for cooperation is received, the client used by the user is responsible for redirecting the transmission and reception of the authorization request and authorization code between applications X and Y. After the authorization code is passed to application Y to be cooperated, application X passes an access token to application Y after verifying the authorization code, and application Y transmits a request to obtain user information in application X, and in response, application X transmits user information to application Y.

[0045] As shown in Figure 3, the existing method requires the exchange of access tokens (secret information) after authentication and authorization using an appropriate protocol. Application Y must store the access token, so not only must the operator of application Y bear the risk of leakage, but this risk and the development costs of the integration process increase in proportion to the number of applications that are integrated. In addition, as shown in Figure 3, application X faces the development and operation costs of APIs for providing user information and the risk of user information leakage, which also increase with the number of applications that are integrated. To promote integration, these risks and increases in costs should be avoided. In addition, as shown in Figure 3, application X faces the development and operation costs of APIs for providing user information and the risk of user information leakage, which also increase with the number of applications that are integrated. To promote integration, these increases in risks and ...

[0046] A specific configuration of a system for achieving cooperation between applications without using APIs and access tokens, as shown in FIG. 3, will be described below.

[0047] FIG. 4 is a block diagram showing the configuration of the information terminal device 1. The information terminal device 1 is, for example, a smartphone or a tablet terminal. The information terminal device 1 may be a personal computer. The information terminal device 1 may be any type of device as long as it is capable of data communication with management devices 2A and 2B that perform electronic signature processing using a private key and authentication, as described later (FIG. 7). The information terminal device 1 may be realized by combining a device (hardware wallet) that specializes in managing private keys and performing electronic signature processing with a smartphone or a personal computer.

[0048] The information terminal device 1 includes a processing unit 10, a storage unit 11, a communication unit 12, a display unit 13, and an operation unit 14. The processing unit 10 uses a processor such as a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit), a memory, etc. The processing unit 10 may be configured as a single piece of hardware (SoC: System On a Chip) that integrates the processor, the memory, and further the storage unit 11 and the communication unit 12.

[0049] The storage unit 11 uses a flash memory, and stores programs and data referenced by the processing unit 10, including the information terminal program 1P. The information terminal program 1P is a program for causing a computer to function as the information terminal device 1 of the system 100 of the present disclosure. A blockchain account is stored in the storage unit 11. The storage unit 11 also stores app accounts for each application, including different applications A and B, and these account data can be used to sign in to the applications.

[0050] The information terminal program 1P stored in the storage unit 11 may be an information terminal program 8P stored in a computer-readable storage medium 8 that has been read by the processing unit 10 and stored in the storage unit 11.

[0051] The storage unit 11 may store a private key of a user in the block chain system 300, as shown in Fig. 4. The private key may be stored in a non-rewritable manner in the memory of the processing unit 10 or in the storage unit 11 (wallet on a chip). The private key may be managed in a hardware wallet dedicated to private keys, as described above.

[0052] The communication unit 12 is a communication module that realizes communication connections with the management devices 2A and 2B and other communication devices. The communication unit 12 uses a network card, a wireless communication device, or a carrier communication module. The communication unit 12 may use a module that realizes communication with the communication units 22 of the management devices 2A and 2B by near field communication.

[0053] The display unit 13 uses a display device such as a liquid crystal panel or an organic EL display. The operation unit 14 is an interface that accepts user operations, and uses physical buttons, a touch panel device built into the display, a speaker, a microphone, etc. The operation unit 14 may accept operations on a screen displayed on the display unit 13 using physical buttons or a touch panel, or may recognize the operation content from an input voice using a microphone and accept the operation in an interactive format using the voice output from a speaker.

[0054] 5 is a block diagram showing the configuration of the management devices 2A and 2B. The management devices 2A and 2B may be server computers, desktop or laptop personal computers, or communication terminals such as smartphones or tablet terminals. The management devices 2A and 2B are not limited to devices capable of long-distance communication via a network such as the Internet, and may be devices that communicate data with the information terminal device 1 through short-distance communication.

[0055] Each of the management devices 2A and 2B includes a processing unit 20, a storage unit 21, and a communication unit 22. Only the management device 2A is shown in Fig. 5. The configuration of the management device 2B is similar to that of the management device 2A, and therefore a detailed description thereof will be omitted.

[0056] The processing unit 20 uses a processor such as a CPU or a GPU, a memory, etc. The processing unit 20 realizes an authentication function and an asset management function in the blockchain system 300, including transaction creation and transaction execution, based on a management program 2P stored in the storage unit 21. The storage unit 21 uses a hard disk or a flash memory, and stores programs and data referenced by the processing unit 20, including the management program 2P.

[0057] The management program 2P stored in the storage unit 21 may be a management program 9P stored in a computer-readable storage medium 9 that has been read by the processing unit 20 and stored in the storage unit 21.

[0058] The communication unit 22 is a communication module that realizes a communication connection with the information terminal device 1 or the block chain system 300. The communication unit 22 uses a network card, a wireless communication device, or a carrier communication module. The communication unit 22 may use a module that realizes communication with the communication unit 12 of the information terminal device 1 by short-range communication.

[0059] 6 is a block diagram showing a configuration of a node 30 in a blockchain system 300. The node 30 may be a server computer, a desktop or laptop personal computer, or a communication terminal device such as a smartphone. The node 30 includes a processing unit 31, a storage unit 32, and a communication unit 33. If the node 30 is a device including at least the processing unit 31 and the communication unit 33, a part of the processing unit 31 can constitute a part or the whole of the node.

[0060] The processing unit 31 uses a processor such as a CPU or a GPU, a memory, etc. The processing unit 31 may be configured as a single piece of hardware that integrates a processor, a memory, a storage unit 32, and a communication unit 33. The memory of the processing unit 31 may store a private key unique to each node 3. The processing unit 31 then executes each process based on the node program stored in the storage unit 32, and causes the general-purpose computer to function as a node in the blockchain system 300.

[0061] The storage unit 32 uses a hard disk or flash memory, and stores programs and data referenced by the processing unit 31, including a node program. The storage unit 32 stores a blockchain. The node program includes a program for functioning as a smart contract (the processing unit 31 that executes predetermined calculation processing for transactions), which will be described later. The above-mentioned private key may be stored in the storage unit 32. The storage unit 32 may store a public key and an address based on the private key.

[0062] The communication unit 33 is a communication module that realizes intercommunication between the nodes 30. The communication unit 33 uses a network card, an optical communication device, a wireless communication device, or the like.

[0063] The application cooperation in the system 100 configured as above will be described in detail with reference to a sequence diagram.

[0064] Before the basic processing, the user holds digital assets according to the activity record in the applications A and B. The user's information terminal device 1 stores a blockchain account for managing these digital assets. Since a typical blockchain account is associated with one or more asymmetric key pairs, in step S2 of the basic processing, the management devices 2A and 2B of the applications A and B can utilize this to authenticate the user (whether the user is really the owner of the blockchain account).

[0065] The challenge-response authentication using an asymmetric key will be described below. Fig. 7 is a sequence diagram showing an example of an authentication process procedure in application linkage. The procedure shown in the sequence diagram of Fig. 7 corresponds to the details of the "account authentication process" in the process shown in the sequence diagram of Fig. 2.

[0066] In response to a request for account linking (S1), the processing unit 10 of the information terminal device 1 transmits an identifier of the block chain account to the management devices 2A and 2B (S101).

[0067] When the processing unit 20 of the management device 2A (or 2B) receives an identifier of a blockchain account via the communication unit 22 (step S201), it inquires of the blockchain system 300 about the existence of the blockchain account (step S202).

[0068] In step S202, the processing unit 20 may determine whether the identifier received in step S201 exists as an account in the blockchain system 300 and holds any tokens. In step S202, the processing unit 20 obtains from the blockchain system 300 the public key itself linked to the identifier of the blockchain account transmitted from the information terminal device 1, or information required for calculating the public key.

[0069] The processing unit 20 of the management device 2A (or 2B) generates a pseudo-random number (step S203), and transmits the generated pseudo-random number to the information terminal device 1 that has requested cooperation (step S204).

[0070] The processing unit 10 of the information terminal device 1 receives a pseudo-random number from the management device 2A (or 2B) (step S102) and generates an electronic signature for the received pseudo-random number using a private key associated with the user's blockchain account (step S103). The processing unit 10 transmits the generated electronic signature to the management device 2A (or 2B) that transmitted the pseudo-random number (step S104).

[0071] The processing unit 20 of the management device 2A (or 2B) receives the electronic signature (step S205) and determines a public key from the identifier received in step S201 (step S206). In step S206, the processing unit 20 reads the public key if it has acquired the public key itself, and calculates the public key if it has acquired information necessary for calculation.

[0072] The processing unit 20 verifies the validity of the electronic signature in step S205 using the pseudo-random number generated in step S203 and the public key determined in step S206 (step S207). If it is determined to be valid in step S207, the management device 2A (or 2B) determines that the authentication of the blockchain account of the user of the information terminal device 1 that sent the link request has been successful.

[0073] In step S3 (see FIG. 2) of the basic process, if authentication is successful, the management device 2A or the management device 2B grants a token related to application A or application B to the user who requests application cooperation.

[0074] The nature of the token to be granted, the conditions for granting the token, or the process are not particularly limited. The patterns of tokens to be granted are listed below.

[0075] The nature of tokens can be broadly considered along the following three axes:

[0076] [Substitutability] It may be fungible (FT: Fungible Token) or non-fungible (NFT: Non-Fungible Token).

[0077] [Transferability] The tokens granted may be transferable or non-transferable.

[0078] [Possibility of incineration] The tokens granted may be burnable or non-burnable in the blockchain system 300. If burning is possible, burning may be possible by the token issuer (management devices 2A, 2B) or by the user who holds the token (as long as certain conditions are met). "Burning" may be expressed by reducing the amount of tokens, or may be expressed by metadata such as a burn flag.

[0079] The basic properties of the token may be defined by a combination of the selections in the above three axes. For example, a token corresponding to some achievement (achievement, achievement, etc.) in application A is unique to the user who is the holder and cannot be transferred to others, and it is desirable that it can be used semi-permanently, so it is appropriate to realize it with a combination of non-transferable, non-substitutable, and non-burnable. In the case of a non-substitutable token, the unit token can be identified by data such as the token's unique identification information and a unique image created by application A. In the case of a substitutable token, since there is a concept of quantity, an upper limit may be set on the token issue amount or the amount that can be held by each blockchain account, the transferable amount, the burnable amount, etc. In addition, metadata related to the token (for example, relatively large data such as an image of the achievement asset and a detailed description) may be held within the blockchain system 300 or outside the blockchain system 300. When held outside the blockchain system 300, a method is conceivable in which the metadata is published in, for example, JSON format with a specific link information (URL), and the link information is linked to the token and recorded in the blockchain system 300.

[0080] The token may be implemented as a token contract as described above. In this case, in the case of a non-fungible token, the deployed token contract may, for example, disable transfer calls. Conversely, in the case of a transferable token, the token may be deployed in a state where transfer calls are possible and the amount can be specified.

[0081] The conditions for granting tokens can be set in association with concepts and indicators in each application A and B.

[0082] The process of token granting (S3) may be realized, for example, by transferring a token that has been issued in advance by the management device 2A of application A and held in a blockchain account held (manageable) by the management device 2A to the blockchain account of the user. Alternatively, the management device 2A may directly issue a token to the blockchain account of the user. Such transfer or issuance may be performed by the management device 2A at any timing, or may be performed at the timing of a request for token grant including application linkage of a user who satisfies the granting conditions.

[0083] In step S10 (see FIG. 2) of the basic process, the processing unit 20 of the linked management device 2B checks the contents of the token linked to the user's blockchain account. This check process can basically be performed at any timing after the blockchain account has been authenticated, by referencing the token information held in the user's blockchain account on the blockchain system 300. While any timing can be used, there are three possible patterns for the timing of token check: (1) The timing of receiving a request from the information terminal device 1 (user) (2) When application B needs to reference (3) When the token was granted to the user

[0084] The timing of (3) will be described with reference to a sequence diagram. Fig. 8 is a sequence diagram showing an example of a processing procedure for confirming the contents of a token. The confirmation is performed by the management device 2B of application B. The sequence diagram of Fig. 8 is performed up to step S9 in the basic processing of Fig. 2, that is, when authentication processing of the blockchain account has been completed in both the linked management device 2A and management device 2B.

[0085] The processing unit 20 of the management device 2B judges whether a predetermined monitoring timing has arrived (step S401). If it is judged that the monitoring timing has not arrived (S401: NO), the processing unit 20 returns the process to step S401 and waits until it is judged that the timing has arrived. The predetermined monitoring timing is, for example, the arrival of a fixed period of time. The arrival of the monitoring timing may also be judged by some other event.

[0086] If it is determined that a predetermined monitoring timing has arrived (S401: YES), it is determined whether or not a token has been granted by the management device 2A of application A to the user's blockchain account on the blockchain system 300 (step S402). If it is determined that a token has been granted (S402: YES), it is determined that confirmation has been successful (step S403).

[0087] If it is determined in step S402 that a token has not been granted (S402: NO), the processing unit 20 returns the process to step S401.

[0088] While step S401 is being continuously repeated, as shown in the basic processing of Figure 2, when the asset-granting transaction is approved by steps S3 to S7 and incorporated into a block of the blockchain system 300, it is determined that the asset has been granted in step S402, and the granting of the token can be detected.

[0089] In this case, by appropriately setting the monitoring timing, as soon as the management device 2A of the application A grants a token to a user, the management device 2B of the application B can immediately grasp this fact.

[0090] In the first place, it is difficult for a smart contract (token contract) running on the blockchain system 300 to directly access a device outside the blockchain system 300. It is difficult for a node 3 or the like in the blockchain system 300 to notify the management device 2B of application B of the token grant as the main body. Therefore, when it is necessary to grasp information updates on the blockchain system 300 as quickly as possible in real time, this can be achieved by continuously monitoring updates of data related to the target blockchain account or the target token, as shown in FIG. 8.

[0091] As described above, the tokens granted in this embodiment are achievements or rights that are issued in association with an application, and are different from so-called crypto assets such as BTC and ETH. Therefore, the management device 2A of application A, which is the issuer of the token, or the business entity that manages application A, affects the value of the token. In such a case, it is important in the confirmation process to be able to confirm not only the possession of the token but also its issuer.

[0092] Basically, a blockchain transaction is approved (confirmed) after verifying an electronic signature generated based on a private key linked to the blockchain account that executes the transaction. Therefore, the blockchain account that executed the transaction to issue the token can be verified cryptographically. In other words, if application A that issues the token or the business that manages application A publishes a public key (blockchain account address, data that can calculate the public key) that corresponds to the private key used to issue the token, application B that is linked to the application A or the business that manages the application B can accurately verify the issuer of the token. It may be implemented in a form that enables verification of the issuer. For the business of application B, there are cases where approval cannot be granted by merely verifying the granting of a token to a user's blockchain account. Since it is linked to the blockchain account, it can be verified whether the token was legitimately granted by the business of application A, and in this way, the verification of the issuer can also be performed.

[0093] In the basic process, in step S11 (see FIG. 2), some process is authorized by the management device 2B of the linked application B based on the right associated with the confirmed token. The rights associated with the token are roughly divided into the following two types. (1) Permanently exercisable rights (membership type) (2) A pattern in which rights are lost after a certain number of exercises (ticket type)

[0094] For the membership type (1), as long as the authentication process in steps S2 and S9 and the token confirmation process in step S10 are performed, the rights can be exercised at any time thereafter. For the ticket type (2), the management device 2B needs to store data on whether the rights can be exercised, such as by recording the number of times the rights can be exercised or the number of times the rights have been exercised in some form. For example, the number of times the rights can be exercised based on the amount of tokens held may be stored in a storage device inside or outside the management device 2B, and the number of times may be reduced each time the rights are exercised in application B. If the tokens that are the basis for exercising the rights are partially or completely burned each time the rights are exercised, the remaining number of times the rights can be exercised can be reliably managed on the blockchain system 300.

[0095] 9 is a sequence diagram showing an example of processing execution based on a ticket-type token. Based on the token granted based on the performance in application A, the following processing is executed in response to a request from information terminal device 1 of a user who desires processing in application B.

[0096] The processing unit 10 of the information terminal device 1 transmits the identifier of the user's blockchain account to the management device 2B of application B based on the user's operation (intention to exercise rights) on the operation unit 14 (step S111).

[0097] The processing unit 20 of the management device 2B receives the identifier of the user's blockchain account (step S411), and confirms (obtains) the presence or absence, amount, or conditions of the token associated with the received identifier (step S412).

[0098] The processing unit 10 of the information terminal device 1 creates a transaction for burning the tokens granted by application A in an amount according to the desired right exercise (step S112).

[0099] The processing unit 10 broadcasts (transmits) the transaction created in step S112 to the block chain system 300 (step S113).

[0100] The blockchain system 300 receives the transaction broadcast in step S113 (step S301). The blockchain system 300 verifies the received transaction with the user's blockchain account (step S302) and approves it (step S303).

[0101] Upon approval in step S303, the transaction is included in a block and the amount of tokens from application A associated with the user's blockchain account is burned in the amount specified in step S112.

[0102] After a predetermined time has elapsed since step S412, or in response to a notification from the information terminal device 1, the processing unit 20 of the management device 2B checks (obtains) the presence or absence, amount, or conditions of the token associated with the identifier received in step S411 (step S413).

[0103] The processing unit 20 compares the presence / absence, amount, or condition of the tokens acquired in step S413 with the presence / absence, amount, or condition of the tokens acquired in step S413, and determines whether some or all of the tokens have been incinerated (step S414).

[0104] If it is determined that the information has not been incinerated (no change) (S414: NO), the processing unit 20 returns to step S413 and checks again after a predetermined time has elapsed or when a notification event from the information terminal device 1 occurs.

[0105] If it is determined that the token has been burned (changed) (S414: YES), the processing unit 20 executes processing to provide a benefit to the user in application B according to the content, amount or conditions of the requested and burned token (step S415), and terminates the processing.

[0106] Through the process shown in the sequence diagram of FIG. 9, the tokens given to the user based on the results of the application A are burned, and the user is given a benefit in exchange for burning the tokens, like a ticket.

[0107] The ticket-type right exercise as shown in the sequence diagram of FIG. 9 is basically performed by the information terminal device 1 used by the user who is the subject of the right exercise, and the management devices 2A and 2B that confirm the right exercise while communicating with each other. Of course, the right exercise is not limited to the execution of the right exercise via so-called long-distance communication including the Internet between the information terminal device 1 and the management devices 2A and 2B. Specific application examples of the management devices 2A and 2B include a device that exercises payment-related rights in conjunction with a POS register, a device that exercises rights (unlocks) in conjunction with a smart lock device, and a device that exercises rights (unlocks the door and starts the engine) in conjunction with a connected car. The right exercise may be performed through communication by these short-distance communications. In addition, such a ticket-type right exercise is compatible with trial-type rights (such as the right to view content provided by media or communities with a monthly fee system with time or number of times limited), and if the token is transferable, it can be expected to spread through circulation, so it may be combined with marketing measures, etc.

[0108] In addition, these rights are exercised by the information terminal device 1 and the management devices 2A and 2B communicating digitized information, but the scope of the rights exercised as a result does not need to be entirely digital. For example, in an environment where the Internet of Things (IoT) is highly developed (such as a smart city), the right to provide personalized services via facilities and mobility in that environment may be issued as a token. For example, it may be a preferential right to use a facility or the equipment provided therein (elevators, air conditioning equipment, lighting equipment, Internet line equipment, etc.), or mobility (taxis, buses, etc.). In addition, if the facility is a sales store, inventory management may be performed taking into account the rights held by specific customers.

[0109] The above-mentioned application cooperation will now be described in detail with reference to several examples.

[0110] [Example 1] In the first embodiment, application linkage is explained using an example of use in a campaign or a loyalty program that takes into account performance in a secondary trade area. In the digital content business, utilizing the secondary trade area is an important issue. Therefore, with the aim of solving such an issue, a campaign or a royalty program can be constructed that evaluates not only primary trade area activities (in the case of a game, activities completed within the game) but also secondary trade area activities (video distribution of game play) and provides rewards for those activities.

[0111] Fig. 10 is a schematic diagram of the system 100 in the first embodiment. In the first embodiment, application A is a video distribution platform (application), and application B is an application related to a service provided by a game operator in a primary trade area. Fig. 10 corresponds to the schematic diagram of the system 100 shown in Fig. 1, with applications A and B being a video distribution platform and a game, respectively.

[0112] In the case of streaming game play videos, user activity on the video streaming platform corresponds to secondary commercial activity, so by tokenizing the activity record on the video streaming platform and allowing game operators to reference the tokens, a system can be created for running campaigns or awarding royalties.

[0113] Figures 11 and 12 are sequence diagrams showing an example of a procedure for cooperation between applications in the first embodiment. The sequence diagrams in Figures 11 and 12 show cooperation between a game and a video distribution platform. Among the processing procedures shown in the sequence diagrams in Figures 11 and 12, those procedures that are unchanged from the basic processing procedures shown in Figure 2 are given the same reference numerals and detailed descriptions thereof are omitted.

[0114] When an application linking request is transmitted from the information terminal device 1 (S1), authentication processing is executed between the management device 2A that provides a video distribution platform, the information terminal device 1, and the blockchain system 300 (S2).

[0115] When the authentication process is completed, the processing unit 20 of the management device 2A determines whether the user's usage record of the video distribution platform satisfies certain conditions based on the user's application account (service account) included in the cooperation request (step S221).

[0116] If the processing unit 20 determines that the certain condition is not satisfied (S221: NO), the processing unit 20 returns the processing to step S221 and waits until the condition is satisfied. If the processing unit 20 determines that the certain condition is not satisfied (S221: NO), the processing unit 20 may notify the information terminal device 1 that the link condition is not satisfied and terminate the processing.

[0117] In step S221, the processing unit 20 may determine whether or not certain conditions are met with respect to the length of time of video distribution, the number of times the video distribution is played, the number of viewers of the video distribution, the number of viewers during live distribution, the number of comments, etc. The processing unit 20 may also make a determination based on the length of time the video is viewed, the number of times the video is viewed, and the total amount of "tipping" for the video. The certain conditions may be stored in the storage unit 21 in advance and may be rewritable by an administrator. The certain conditions may include that the distributed video includes a game application, and that the viewed video includes a game application.

[0118] If it is determined that the certain condition is satisfied (S221: YES), the processing unit 20 creates a transaction that grants assets (performance) as performance tokens to the blockchain account received in steps S1 and S2 based on the performance of the video distribution platform (step S222). The processing unit 20 broadcasts the created transaction (S4).

[0119] The broadcasted transaction is received by the blockchain system 300 (S5), verified (S6), and approved (S7).

[0120] The processing unit 10 of the information terminal device 1 transmits an application link request to the management device 2B of the game application (S8). As a result, authentication processing is executed between the management device 2B, the information terminal device 1, and the blockchain system 300 (S9).

[0121] The processing unit 20 of the management device 2B checks the achievement token linked to the blockchain account when the authentication process for the user's blockchain account is completed (S421). If the achievement token cannot be confirmed in step S421, the linking process is interrupted at this point. In this case, the information terminal device 1 may be notified that the linking has failed.

[0122] After confirming the contents, the processing unit 20 of the management device 2B of the game application in Example 1 creates a transaction to grant the user's blockchain account a rights token for rights that can be exercised in the game application or the affiliated video distribution platform thereafter (step S422).

[0123] The processing unit 20 of the management device 2B broadcasts (transmits) the transaction created in step S422 to the block chain system 300 (step S423).

[0124] The transaction sent in step S423 is received by the blockchain system 300 (step S321), verified (step S322), and approved (step S323).

[0125] This allows users to obtain rights tokens that can be used later from game applications based on their usage history on the video distribution platform. In this case, no API is used, and the blockchain system 300 only needs to receive, verify, and approve transactions (assets are implemented as token contracts), so no large-scale process is required.

[0126] The right token may not only be a right that can be exercised in the game application and returned to the user, but also a right that can be used in applications other than the game application, including a video distribution platform. For example, the right may be a right to receive a certain discount on an e-commerce site that sells goods related to the game application. Or, the right may be a right to participate in a beta test of another game application (which may be a sequel) provided by the same business operator related to the game application. Or, the right may be a right to participate in a community (group chat, salon) related to the game application. Or, the right may be a right to enter a specific facility (which may be real or virtual) related to the game application.

[0127] Game application providers can freely combine such achievements and rights to build campaigns and royalty-granting systems to stimulate secondary trade areas for games. Of course, achievements or rights related to games are not limited to the above examples. In addition to using a video distribution platform, an achievement may be made by purchasing a certain amount of game-related goods on an e-commerce site accessed from a related application, with an application A being related to the game application. An achievement may also be made by posting a certain number of times on an SNS with a hashtag related to the game application, with an SNS application being application A. An achievement may also be made by achieving a certain level of success in a specific tournament, with an application A being related to a system for managing eSports tournaments.

[0128] In this way, any valuable activity occurring in applications other than games (secondary trade areas) can be considered as achievements related to game applications. Naturally, the same can be done for non-game applications to promote the revitalization of secondary trade areas.

[0129] It is also possible to learn how to revitalize the secondary trade area by utilizing not only the achievements in the secondary trade area but also the achievements in the primary trade area in the secondary trade area. By providing rewards in the form of rights as explained in the first embodiment for achievements in a game application (clearing a specific stage, obtaining a certain score, entering the top of the rankings), it is expected to increase engagement with the game in a multifaceted way both inside and outside the game.

[0130] A third party, neither the provider of the application (such as a video distribution platform) that generates achievements nor the provider of the application (such as a game application) that directly utilizes achievements, may provide an application dedicated to achievement management to a user who has achievements. Of course, such an achievement management application may be capable of managing achievements related to not only a single application, but also multiple applications across the board.

[0131] [Example 2] In the second embodiment, the application of the second use of copyrighted works (posting of illustrations, etc.) will be described as an example. The application linking method of the present embodiment can contribute to stimulating the distribution of appropriate digital content while preventing the illegal digitalization of copyrighted works such as comics, illustrations, and videos, and the free distribution of such digital content.

[0132] In the current situation where various digital contents are distributed across various applications, cooperation between multiple applications is essential when managing the n-th use of copyrighted works such as manga. However, the cost of cooperation between each application is huge when designing, developing, and operating the cooperation. A model in which some kind of common platform system is constructed and each application is connected to it is conceivable, but if the common platform system is managed and operated by a single business or organization, that single business or organization becomes the SPOF (Single Point Of Failure) of the system. There is also a risk that the business or organization may use its administrator authority to arbitrarily infringe on the interests of other stakeholders. In this case, the risk becomes more serious as the number of applications that cooperate with the common platform system increases. In other words, a method of application cooperation that solves the issues of cost, redundancy, and reliability is required for the management system of n-th use of copyrighted works that will be carried out across a larger number of applications in the future.

[0133] In the second embodiment, the application linking method of the present embodiment will be described by taking as an example a case where the application linking method is applied to n-th use management of an original work.

[0134] FIG. 13 is a schematic diagram showing the structure of a rights token corresponding to the n-th usage-related right in Example 2. As shown in FIG. 13, multiple rights tokens can be issued for the ID of the "content" that is the original work. The "ID" is an identifier (hereinafter referred to as a content ID) that can uniquely identify the digital content (data) of the original work. Specific examples of content IDs include a URL, a DID (Decentralized IDentifier), a content address in IPFS (Inter Planetary File System), or a combination of these, or a hash of the content itself.

[0135] In the second embodiment, the token is managed by linking each digital content with a content ID in a token contract deployed in the block chain system 300. This makes it possible to realize commercial area activation based on n-th usage related rights.

[0136] Fig. 14 is a schematic diagram of the system 100 in the second embodiment. In the second embodiment, application A is a publisher system (application related to content authority management), and application B is an application for using an SNS (hereinafter simply referred to as SNS) in which content such as images and videos can be posted. Fig. 14 corresponds to the schematic diagram of the system 100 shown in Fig. 1, with applications A and B being the publisher system and the SNS, respectively.

[0137] Figures 15 and 16 are sequence diagrams showing an example of a linking procedure between applications in the second embodiment. The sequence diagrams in Figures 15 and 16 show a link between a publisher system and an SNS platform. Among the processing procedures shown in the sequence diagrams in Figures 15 and 16, the same reference numerals are used for the procedures that are unchanged from the basic processing procedures shown in Figure 2, and detailed descriptions thereof will be omitted.

[0138] The management device 2A of the publisher system provides (transmits) manga data (digital content) to the management device 2B so that the data can be used for secondary purposes on the SNS (step S231).

[0139] The management device 2B of the SNS receives the comic data (step S431) and stores it (step S432).

[0140] Then, a request for application linkage is sent from the information terminal device 1 by a user who wishes to use the manga data provided in step S231 on the SNS (S1). Authentication processing is executed between the management device 2A, which provides the system services of the publisher system, the information terminal device 1, and the blockchain system 300 (S2).

[0141] Once the authentication process is complete, the processing unit 20 of the management device 2A determines whether the user satisfies certain conditions, such as whether the user has paid a certain fee to the publisher system (usage rights management), based on the user's application account (service account) included in the collaboration request (step S232).

[0142] If the processing unit 20 determines that the certain condition is not satisfied (S232: NO), the processing unit 20 returns the processing to step S232 and waits until the condition is satisfied. If the processing unit 20 determines that the certain condition is not satisfied (S232: NO), the processing unit 20 may notify the information terminal device 1 that the link condition is not satisfied and terminate the processing.

[0143] In step S232, the processing unit 20 may make a judgment based on a certain condition, such as points for a service or possession of a rights token, other than the payment of the fee for the use of the content by the user.

[0144] If it is determined that the certain conditions are met (S232: YES), the processing unit 20 creates a transaction that grants the rights token to the blockchain account received in steps S1 and S2 on the condition that a compensation is paid (step S233). The processing unit 20 broadcasts the created transaction (S4).

[0145] The broadcasted transaction is received by the blockchain system 300 (S5), verified (S6), and approved (S7).

[0146] The processing unit 10 of the information terminal device 1 transmits a request for application linkage to the management device 2B of the SNS (S8). As a result, authentication processing is executed between the management device 2B, the information terminal device 1, and the blockchain system 300 (S9).

[0147] The processing unit 20 of the management device 2B checks the rights token associated with the blockchain account when the authentication process for the user's blockchain account is completed (S433). If the rights token cannot be confirmed in step S433, the linking process is interrupted at this point. In this case, the information terminal device 1 may be notified that the linking has failed.

[0148] By confirming the contents, the processing unit 20 of the management device 2B of the SNS in the second embodiment allows the user's application account data to access the manga data received in step S431 on the SNS (step S434), and ends the process.

[0149] After step S434, the user can access and post manga data on the SNS. For example, the user is permitted to publish parody manga in which dialogue has been replaced or illustrations in which specific frame images have been modified on the SNS.

[0150] As explained in the second embodiment with reference to the sequence diagrams of Figures 15 and 16, a publisher system that manages usage rights of manga data tokenizes and grants secondary usage rights of the manga to users who meet certain conditions, and provides the manga data to applications that want to use the manga. This allows users to use the secondary usage rights across applications. As shown in the sequence diagrams of Figures 15 and 16, secondary usage rights for manga data can be used on SNS, and users can, for example, allow the publication of derivative content using the manga data.

[0151] In the second embodiment, the digital content of a comic book is described as an example, but of course, the present invention is not limited to this. Images, audio, and video (illustrations, music, animation, TV programs, etc.) in various formats are considered as examples of digital content. Of course, the use of secondary use rights is not limited to SNS. Other examples include digital content production platforms and video distribution platforms (audio distribution applications, radio distribution applications, short video SNS, live distribution applications).

[0152] Not only for n-th use, but also for tokenizing various rights and managing them across applications, it may lead to solving monetization issues. For example, a token sale and trading function may be implemented in the token contract, and the sales profit and transaction fee may be automatically sent to the blockchain account of the original author. This makes it possible to pay the legitimate original author through the sale and distribution of various forms of digital content usage rights. The content usage rights may be, for example, viewing and viewing rights, secondary usage rights for live streaming, early access rights to content before it is released, etc.

[0153] Monetization can be implemented in the token contract itself, which is linked to the ID of each content and manages the rights of each content, so that when the rights token is used, crypto assets equivalent to the sales profit and transaction fee can be sent to the blockchain account of the original author. This allows the original author to monetize in the secondary business area.

[0154] In the above detailed description, the application (management device 2A) that provides tokens as digital assets does not need to develop and operate an API for acquiring (providing) information on the digital assets to be tokenized and shared. Since no API is used, there is no risk of security holes.

[0155] The application (management device 2B) that uses the tokenized digital assets does not need to change its implementation to match the linked application if it builds a token contract. It is possible to avoid the increase in development costs that accompanies an increase in the number of linked applications. When accessing information published on the blockchain, the secret information required for OAuth is not required, so there is no security risk associated with its management.

[0156] By enabling verification of the token issuer, it is virtually impossible to counterfeit the token, which significantly reduces the possibility that users of the digital asset will be deceived by false digital asset data.

[0157] As described above, in the application linking method of the present disclosure, the blockchain system 300, which is a highly transparent distributed system without a single management entity, is used as a management platform for digital assets. This significantly mitigates the problems of redundancy and reliability that are a concern when using a platform system managed by a single organization. In addition, the data recorded in the blockchain system 300 has a high tamper-resistance due to its data structure, so that unauthorized manipulation of the recorded data (rights granting, etc.) is extremely difficult. With such a platform system, application linking (shared use of content) between competing stakeholders is also realistically possible.

[0158] The embodiments disclosed above are illustrative in all respects and are not restrictive. The scope of the present invention is defined by the claims, and includes all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0159] 1 Information terminal device 10 Processing section 11 Storage section 13 Display section 14 Control section 1P Information terminal program 2 Management device (1st device, 2nd device) 20 Processing section 21 Memory section 2P Management Program 300 Blockchain System

Claims

1. The device providing the application is Obtain app account data of a user of the application and blockchain account data of the user in a blockchain system; Transmitting a request to the blockchain system to grant a token based on the user's usage history associated with the application to the blockchain account data of the user; The blockchain system receives a request from the user to confirm the presence or absence of the token, the amount of the token, or the content or condition of the token. Application performance processing method.

2. A computer capable of communicating with an application providing device, receiving a request from the device, the request including granting of a token to blockchain account data in a blockchain system of a user of the application based on a usage history of the user of the application associated with the application; Based on the received request, granting the token to the blockchain account data in the blockchain system; Accepting a reference request from the device or another device regarding the presence or absence of the token associated with the blockchain account data, the amount of the token, or the contents or conditions of the token; In response to the lookup request, the lookup result is transmitted to the sender of the request. Application performance processing method.

3. The application is an application for digital content creation, digital content distribution, or digital content posting.

3. The application performance processing method according to claim 1 or 2.

4. The application is an application for a service provided by a game operator.

3. The application performance processing method according to claim 1 or 2.

5. The application is a payment application.

3. The application performance processing method according to claim 1 or 2.

6. The system includes a user's information terminal device and a providing device that provides an application, The providing device comprises: Acquire from the information terminal device app account data of the user of the application and blockchain account data of the user in a blockchain system; Broadcasting a transaction to the blockchain system that grants a token based on the user's usage history associated with the application to the blockchain account data of the user; The blockchain system receives a request from the user to confirm the presence or absence of the token, the amount of the token, or the content or condition of the token. Application performance processing system.

7. An information terminal device stores app account data of a user of a first application and a second application, and blockchain account data of the user in a blockchain system; A first device providing the first application obtains blockchain account data of the user; The first device transmits a request to the blockchain system to grant, to the acquired blockchain account data, a type or amount of tokens according to the usage history associated with the first application; The blockchain system performs the assignment of the token to the blockchain account data in response to the request; The information terminal device transmits a request for linking the second application based on the token assigned to the block chain account data to a second device that provides the second application by associating the block chain account data with the second application; The second device acquires data on the presence or absence of the token, the amount of the token, and the contents or conditions of the token from the blockchain system. How applications work together.

Images