Content data management system

Abstract

To provide means for preventing reduction in value of content data due to duplication or alteration of the content data which is provided only to persons who have purchased a specific commodity or a service.SOLUTION: A system performs: a process to associate a non-fungible token (NFT) with content data or content enablement data which is data for enabling the content data; a process to acquire user action data indicating an action of a user who has purchased a commodity or a service; a process to determine whether the commodity or the service purchased by the user indicated by the user action data satisfies a predetermined condition or not; and a process to add, only when a determination is made that the specific commodity or service satisfies the predetermined condition, transaction data indicating that the NFT has been added to a wallet of the user, to a ledger of a blockchain.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a technique for managing data representing content. [Background technology]

[0002] Data (hereinafter referred to as "content data") representing information that can be sensed by humans, such as images, sounds, videos, and three-dimensional shapes (hereinafter referred to as "content"), is used to play the content that the content data represents (to display videos, generate physical signals that can be sensed by humans, such as the pronunciation of sounds), and brings about various emotional changes in people who view the content. For this reason, content data has value in human society and is a subject of trading in the market.

[0003] Content data is easily copied and modified. If a large amount of copied content data is distributed on the market, the market value of the content data will decrease, which may be undesirable for the source or holder of the content data. Also, if a large amount of modified content data is distributed on the market, it will become unclear which content data is the original, and the value of the content data due to its originality will be lost, which may be undesirable for the source or holder of the content data.

[0004] One way to solve the above problems is through a technology called NFT (Non-Fungible Token). NFT is a token, which is data whose uniqueness is guaranteed by being recorded on a blockchain. By associating NFT with content data, the uniqueness of that content data, i.e., that it has not been copied or altered, is guaranteed.

[0005] Patent Document 1 is an example of a patent document proposing technology related to NFTs. Patent Document 1 proposes a means of relaxing restrictions on artistic expression by adding rewritable text data to an NFT or an associated smart contract, allowing the owner of the NFT to freely rewrite this text data, while still using NFT technology, which does not allow for alterations by nature. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Patent No. 7043672 Summary of the Invention [Problem to be solved by the invention]

[0007] There are cases where special items are provided only to those who have had a particular experience. For example, when an artist holds a concert, there may be goods (T-shirts, towels, photo books, acrylic stands, etc.) that are sold only to those who attend the concert. Since these goods can only be purchased by attending the concert, they increase the motivation of those who want to obtain these goods (e.g., fans of the artist) to go to the concert, and serve to promote the sale of concert tickets, for example.

[0008] Like the goods mentioned above, goods that can only be obtained by people who have had a specific experience are more difficult to obtain than goods without such restrictions, so they generally have a high market value and come with a premium (hereafter referred to as "premium goods"). Premium goods satisfy the owner's desire to own them and fetch a high price when they are bought and sold on the market.

[0009] A premium may be attached not only to physical items such as the above-mentioned T-shirts, but also to content data whose substance is information. For example, a premium is attached to content data provided only to those who attend a concert (such as video data showing special footage of an artist). Hereinafter, content data with a premium attached is referred to as "premium content data."

[0010] Premium goods, which have a physical substance, are difficult to copy or modify, and therefore are unlikely to lose value as a result. On the other hand, premium content data is easy to copy or modify, and therefore is more likely to lose value as a result.

[0011] In view of the above circumstances, the present invention provides a means for preventing a decrease in value due to copying or alteration of content data provided only to people who have had a specific experience. [Means for solving the problem]

[0012] The present invention provides a system that performs the following processes: associating an NFT with content data or content activation data, which is data for activating the content data; acquiring user behavior data indicating that a user has purchased a product or service; determining whether the product or service purchased by the user, as indicated by the user behavior data, satisfies specified conditions; and adding transaction data to a blockchain ledger indicating that the NFT has been added to the user's wallet only if it is determined that the product or service satisfies the specified conditions. Effect of the Invention

[0013] According to the system of the present invention, only those who purchase a specific product or service can obtain an NFT associated with specific content data or content activation data for activating the content data, and can use the content data associated with the NFT. Furthermore, it is difficult to copy or modify the content data associated with the NFT. Therefore, according to the present invention, the value of the content data provided only to those who purchase a specific product or service is prevented from decreasing due to copying or modification. [Brief description of the drawings]

[0014] [Figure 1] FIG. 1 is a diagram showing a configuration of a content data management system according to an embodiment. [Diagram 2] FIG. 4 is a diagram illustrating a data configuration of a user table according to an embodiment. [Diagram 3] FIG. 4 is a diagram illustrating a data configuration of a content table according to an embodiment. [Figure 4] FIG. 13 is a diagram illustrating an example of the data configuration of an NFT acquisition log table according to an embodiment. [Diagram 5] FIG. 2 is a diagram illustrating a functional configuration of a user terminal device according to an embodiment. [Figure 6] FIG. 11 is a diagram showing a user registration process flow according to an embodiment. [Figure 7] FIG. 11 is a diagram showing a user registration process flow according to an embodiment. [Figure 8] A figure showing an NFT acquisition application page displayed on a user terminal device in one embodiment. [Figure 9] FIG. 13 is a diagram showing a wallet application guide page displayed on a user terminal device according to an embodiment. [Figure 10] FIG. 13 is a diagram showing a wallet generation process flow according to one embodiment. [Figure 11A] FIG. 13 is a diagram showing the flow of an NFT granting process according to one embodiment. [Figure 11B] FIG. 13 is a diagram showing the flow of an NFT granting process according to one embodiment. [Figure 12]FIG. 4 is a diagram showing a content acquisition process flow according to an embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of a configuration of a content table according to one modified example. [Figure 14] FIG. 13 is a diagram showing a configuration of a content data management system according to a modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] [Embodiment] A content data management system 1 according to an embodiment of the present invention will be described below. The content data management system 1 is a system that manages premium content data, which is content data that is provided only to people who have had a specific experience, and guarantees the uniqueness of the premium content data.

[0016] 1 is a diagram showing the configuration of a content data management system 1. The content data management system 1 includes a content data management server device 11 that forms the backbone of the content data management system 1, a file server device 12 that stores data used by the content data management server device 11 to manage content data, a storage system 13 that stores content data and distributes it upon request, a ledger management system 14 that manages a ledger according to blockchain technology, and a user terminal device 15 that is used by a user.

[0017] The content data management server device 11 communicates data with the file server device 12, the storage system 13, the ledger management system 14, and the user terminal device 15 via a communication network such as the Internet. Note that data communication between the content data management server device 11 and other devices may be performed by wired or wireless communication, or a combination of these.

[0018] Furthermore, the user terminal device 15 performs data communication with the content data management server device 11, as well as with the storage system 13 and the ledger management system 14, via a communication network such as the Internet. Note that data communication between the user terminal device 15 and other devices may be performed by wired or wireless means, or a combination of both.

[0019] 1, only one user terminal device 15 is shown, but in reality the number of user terminal devices 15 varies depending on the number of users who use the content data management system 1. Also, the user terminal device 15 used by each user may change.

[0020] The hardware of the content data management server device 11 and the file server device 12 is, for example, a computer for a general server device, and is equipped with a memory for storing various data, a processor for performing various data processing in accordance with programs stored in the memory, and a communication interface for performing data communication with external devices.

[0021] A computer used as the hardware of the content data management server device 11 performs data processing according to a program for the content data management server device 11 according to this embodiment, thereby functioning as the content data management server device 11 that performs various processes described later.

[0022] Either or both of the content data management server device 11 and the file server device 12 may be a system composed of two or more devices that operate in cooperation with each other.

[0023] The file server device 12 stores various data in accordance with instructions from the content data management server device 11. The data stored in the file server device 12 includes a user table that stores data related to users, a content table that stores data related to content, an NFT acquisition log table that is provided for each user and stores data related to the acquisition of NFTs by the user, and content data.

[0024] Fig. 2 is a diagram illustrating an example of the data configuration of a user table. The user table illustrated in Fig. 2 is a collection of data records corresponding to each user, and each data record has a "user ID" field that stores a user ID (identifier) ​​that is information for identifying the user, a "personal identification information" field that stores information (such as a password) for identifying the user, and a "wallet address" field that stores a wallet address that identifies the blockchain wallet (hereinafter simply referred to as a "wallet") used by the user in the user terminal device 15.

[0025] Fig. 3 is a diagram illustrating an example of the data configuration of a content table. The content table illustrated in Fig. 3 is a collection of data records corresponding to each piece of content, and each data record has a "content ID" field that stores a content ID, which is information for identifying the content, and a "provision condition" field that stores information indicating the conditions for providing the content.

[0026] In this embodiment, the condition for providing the content is, for example, a condition that is satisfied when the user is at the location of the event corresponding to the content at the time of the event. Specifically, the "Provision Condition" field of the content table stores information such as "Event time: March 23, 2023, 17:00-19:00, Event location: (latitude, longitude) = (35.65917308012245N, 139.69496655767185E) within a radius of 30 m." The content data identified by the content ID stored in the "Content ID" field of the data record in which this information is stored in the "Provision Conditions" field will be provided only to users of user terminal devices 15 located in an area within a radius of 30 m from the point with latitude and longitude (35.65917308012245N, 139.69496655767185E) during the period from 17:00 to 19:00 on March 23, 2023.

[0027] FIG. 4 is a diagram illustrating an example of the data configuration of the NFT acquisition log table. As described above, the file server device 12 stores an NFT acquisition log table corresponding to each of the multiple users who use the content data management system 1. The NFT acquisition log table illustrated in FIG. 4 is a collection of data records corresponding to each NFT provided to the user, and each data record has an "NFT" field that stores the NFT, a "content ID" field that stores a content ID that identifies the content data associated with the NFT, and a "receiving status" field that stores information indicating the status of receipt of the NFT by the user. The data stored in the "receiving status" field indicates information such as "not received" and "receiving completed at 17:15 on March 23, 2023".

[0028] As described above, the file server device 12 stores content data in addition to the user table (FIG. 2), the content table (FIG. 3), and the NFT acquisition log table (FIG. 4). The content data is stored in the file server device 12 in a state in which it can be identified by the content ID, for example, by including the content ID in the file name.

[0029] The storage system 13 (see FIG. 1) is a system that stores copies of content data stored in the file server device 12 in a state that allows them to be distributed to a user terminal device 15 upon request. In this embodiment, the storage system 13 is a P2P network conforming to the IPFS (InterPlanetary File System) protocol or the like. When a P2P network is employed as the storage system 13, there is an advantage that the content data is not substantially lost because copies of the content data are stored in each of a plurality of nodes.

[0030] The ledger management system 14 is a system that makes it virtually impossible to tamper with time-series data by managing a ledger called a blockchain in a distributed manner using multiple nodes in accordance with known blockchain technology.

[0031] The hardware of the user terminal device 15 is, for example, a computer for a general terminal device, and includes a memory for storing various data, a processor for performing various data processing according to programs stored in the memory, a communication interface for performing data communication with external devices, a display for providing visual information to the user, a speaker for providing auditory information to the user, and an input device (keyboard, mouse, touch panel, etc.) for accepting information input from the user to the user terminal device 15.

[0032] In addition, in this embodiment, the computer used as the hardware of the user terminal device 15 is equipped with a GNSS unit, which is a device that measures the latitude and longitude that indicate the device's position on the earth using the GNSS (Global Navigation Satellite System).

[0033] In addition, devices such as a display, speaker, input device, etc. equipped on a computer used as hardware of the user terminal device 15 may be built into the computer main body, or may be connected to the computer main body as external devices via a wired or wireless connection.

[0034] In the following explanation, as an example, the computer used as the hardware of the user terminal device 15 is assumed to be a small tablet PC (Personal Computer) equipped with the function of data communication and calling via a mobile communication network, generally called a smartphone, and has a built-in camera and microphone in addition to a touch screen that integrates a display and touch panel, a speaker, a GNSS unit, and a communication interface.

[0035] In this embodiment, user terminal device 15 has a web browser function, a wallet function, and a player function for playing back content represented by content data. Fig. 5 is a diagram showing the functional configuration of user terminal device 15. In this embodiment, the web browser function and wallet function of user terminal device 15 are independent of each other. On the other hand, the wallet function and player function of user terminal device 15 are integrated.

[0036] More specifically, a program for causing user terminal device 15 to function as a Web browser (hereinafter referred to as a "Web browser application") and a program for causing user terminal device 15 to function as a wallet and player (hereinafter referred to as a "wallet application") are individually downloaded to user terminal device 15 from a server device (not shown in FIG. 1, etc.) that distributes the programs, installed, and executed in user terminal device 15. Thus, user terminal device 15 has a state in which it functions as a Web browser (hereinafter referred to as "user terminal device 15B") and a state in which it functions as a wallet with player function (hereinafter referred to as "user terminal device 15W").

[0037] The computer used as the hardware of the user terminal device 15 processes data in accordance with the above-mentioned Web browser application and wallet application, thereby functioning as the user terminal device 15 that performs various processes described below.

[0038] This concludes the description of the configuration of the content data management system 1. Next, we will explain the operation of the content data management system 1. Note that the operation of the content data management system 1 will be explained below using as an example a case where a user participates in a concert and obtains content data that is only provided to those who attended the concert.

[0039] The process flow of the content data management system 1 is divided into, for example, a user registration process flow, an NFT application acceptance process flow, a wallet creation process flow, an NFT granting process flow, and a content acquisition process flow. Each process flow will be described below in order.

[0040] (User registration process flow) 6 is a diagram showing a user registration process flow. A new user who uses the content data management system 1 must first register himself / herself in the content data management server device 11 using the user terminal device 15. To do this, the user inputs a URL for user information registration into the user terminal device 15 (user terminal device 15B) in a state where a Web browser application is running.

[0041] In response to the input of the URL for user information registration, the user terminal device 15B displays a user information registration page (step S101). Note that the source of the data instructing the display of the user information registration page (HTML data, etc., hereinafter referred to as "Web page display instruction data") may be the content data management server device 11 or a device different from the content data management server device 11.

[0042] The user inputs a user ID and personal identification information (e.g., a password) into a user information registration page displayed on user terminal device 15B. As a result, user terminal device 15B acquires the user ID and personal identification information (step S102). Next, when the user performs a predetermined operation on user terminal device 15B (e.g., a touch operation on a "Send" button), user terminal device 15B transmits the user ID and personal identification information to content data management server device 11 in response to the operation (step S103).

[0043] Next, the content data management server device 11 transmits an instruction to the file server device 12 to register a new user (step S104). This instruction includes the user ID and personal identification information that the content data management server device 11 received from the user terminal device 15B. The file server device 12 adds a new data record to the user table (FIG. 2) in accordance with the instruction received from the content data management server device 11, and stores the user ID and personal identification information included in the instruction in the added data record (step S105). This completes the user registration processing flow.

[0044] The process flow of steps S101 to S105 described above is an example of a user registration process flow, and various other alternative process flows may be adopted. For example, the telephone number or email address of the user terminal device 15 may be used as personal identification information, and the content data management server device 11 may send an authentication code to the telephone number or email address, and only when the user correctly enters the authentication code into the user information registration page displayed on the user terminal device 15B, the file server device 12 may store the user ID and personal identification information in the user table.

[0045] (NFT application acceptance processing flow) 7 is a diagram showing a user registration process flow. In order to obtain content data that is provided only to those who attended the concert, the user must first apply to obtain an NFT associated with the content data at the concert venue. When the user arrives at the concert venue carrying the user terminal device 15, the user inputs a login URL into the user terminal device 15B at the concert venue to display a login page on the user terminal device 15B, inputs a user ID and personal identification information on the login page, and logs in to the service provided by the content data management server device 11.

[0046] Next, the user inputs the URL for the NFT acquisition application into user terminal device 15 B. Prior to or in parallel with the display of the NFT acquisition application page, user terminal device 15 B determines whether the conditions for providing content data are satisfied for the user in accordance with a script included in the Web page display instruction data that instructs the display of the NFT acquisition application page (step S201).

[0047] Here, the content data provision conditions are conditions indicated by the data stored in the "provision conditions" field of the data record corresponding to the content data provided to the participants of this concert among the data records in the content table (FIG. 3). As an example, the provision conditions used below are "Date of event: March 23, 2023, 17:00-19:00, Location: (latitude, longitude) = (35.65917308012245N, 139.69496655767185E) within a radius of 30 m."

[0048] In the judgment of step S201, the user terminal device 15B judges whether the current time is within the period from 17:00 to 19:00 on March 23, 2023, and whether the latitude and longitude indicating the current position of the user terminal device 15 measured by the GNSS unit is within an area of ​​a radius of 30 m from (35.65917308012245N, 139.69496655767185E). Depending on the result of the judgment of step S201, the user terminal device 15B displays a different NFT acquisition application page (step S202).

[0049] Fig. 8 shows examples of an NFT acquisition application page displayed by user terminal device 15 B. Fig. 8(A) is an example of an NFT acquisition application page displayed when the determination result in step S201 is positive, and Figs. 8(B) to (D) are examples of an NFT acquisition application page displayed when the determination result in step S201 is negative.

[0050] When the NFT acquisition request page of Fig. 8(A) is displayed, the user touches the "Get" button. In response to this operation, the user terminal device 15B transmits an NFT acquisition request to the content data management server device 11 (step S203). This acquisition request includes the content ID of the content data that the user wants to acquire.

[0051] In response to the acquisition request received from the user terminal device 15B, the content data management server device 11 transmits an update instruction to the file server device 12 to instruct the file server device 12 to change the receipt status of the NFT to "not received" (step S204). This update instruction includes the user ID and the content ID.

[0052] The file server device 12 updates the NFT acquisition log table (FIG. 4) in accordance with the update instruction received from the content data management server device 11 (step S205). More specifically, the file server device 12 adds a new data record to the NFT acquisition log table corresponding to the user ID included in the update instruction, stores the content ID included in the update instruction in the "content ID" field of the data record, and stores "not received" in the "received status" field.

[0053] When a user inputs a URL for applying to acquire an NFT into user terminal device 15B before the start of the concert period, user terminal device 15B displays an NFT acquisition application page as shown in Fig. 8(B). In this case, the user waits until the concert period arrives within the concert venue, and then inputs the URL for applying to acquire an NFT into user terminal device 15B again, thereby causing an NFT acquisition application page as shown in Fig. 8(A) to be displayed on user terminal device 15B.

[0054] When the user inputs the URL for applying to acquire an NFT into user terminal device 15B after the concert period ends, user terminal device 15B displays an NFT acquisition application page as shown in Fig. 8(C). In this case, the user cannot apply to acquire an NFT, and cannot acquire the content data.

[0055] If a user inputs the URL for applying to obtain an NFT into user terminal device 15B while in a position more than 30 m away from the center of the concert venue during the concert period, user terminal device 15B displays an NFT acquisition application page such as that shown in Fig. 8(D). In this case, the user can move closer to the center of the concert venue and then input the URL for applying to obtain an NFT into user terminal device 15B again, thereby causing an NFT acquisition application page such as that shown in Fig. 8(A) to be displayed on user terminal device 15B.

[0056] In addition, the source of the web page display instruction data that instructs the display of the NFT acquisition application page may be the content data management server device 11, or it may be a device different from the content data management server device 11.

[0057] (Wallet creation process flow)

[0058] In this embodiment, a wallet application is installed in user terminal device 15, and after the user logs in for the first time using the wallet application, when the user consents to the terms of use, etc., a wallet managed by user terminal device 15W is generated within user terminal device 15.

[0059] When the "Get" button is touched on the NFT acquisition application page in Fig. 8(A), if a wallet application is not installed in the user terminal device 15, the user terminal device 15B displays a wallet application guide page as shown in Fig. 9. When the user touches the "Install" button on the wallet application guide page, a wallet generation process flow is started. Fig. 10 is a diagram showing the wallet generation process flow.

[0060] In response to a user's touch operation on an “Install” button on the wallet application guide page, the wallet application is downloaded and installed in user terminal device 15 (step S301). The wallet application is distributed from content data management server device 11 or from a device different from content data management server device 11.

[0061] When the wallet application is executed in the user terminal device 15, the user terminal device 15 becomes in a state where it functions as a wallet with a player function (user terminal device 15W). The user enters a user ID and personal identification information on a login screen displayed by the user terminal device 15W to perform an initial login. If the initial login is successful, the user terminal device 15W then displays the terms of use and privacy policy of the service provided to the user by the content data management system 1, and displays an "Agree" button to confirm the user's agreement to these. When the user agrees to the terms of use and the like and touches the "Agree" button, the user terminal device 15W generates a new wallet (step S302).

[0062] Next, the user terminal device 15W notifies the content data management server device 11 of the wallet address that identifies the wallet created in step S302 (step S303).

[0063] The content data management server device 11 instructs the file server device 12 to register the wallet address notified by the user terminal device 15W (step S304). This instruction includes the user ID and the wallet address.

[0064] In accordance with the instructions from the content data management server device 11, the file server device 12 searches the user table (Figure 2) for a data record corresponding to the user ID included in the instruction, and stores the wallet address included in the instruction in the "wallet address" field of the searched data record (step S305).

[0065] (NFT granting process flow) The file server device 12 determines whether there are any unreceived NFTs in response to the occurrence of a predetermined event. The predetermined event is, for example, the process of step S305 in the above wallet generation process flow, i.e., the completion of the process of storing the wallet address of the newly generated wallet in the user table, the user logging in by starting a wallet app, the lapse of a predetermined time after starting the wallet app, etc.

[0066] These events trigger the file server device 12 to determine whether or not there is an unreceived NFT, and the NFT granting process flow is started. Figures 11A and 11B are diagrams showing the NFT granting process flow.

[0067] First, in response to the occurrence of a predetermined event, the file server device 12 determines whether or not there is an unreceived NFT for each user (step S401). More specifically, the file server device 12 extracts data records whose "receive status" is "unreceived" from the NFT acquisition log table (FIG. 4), and if one or more data records are extracted, it determines that there is an unreceived NFT, and if no data records are extracted, it determines that there is no unreceived NFT.

[0068] If the file server device 12 determines in step S401 that there is no unreceived NFT, the following processes included in the NFT granting process flow are not executed.

[0069] On the other hand, if it is determined in step S401 that there is an unreceived NFT, the file server device 12 searches the user table (Figure 2) for the wallet address of the user who owns the unreceived NFT, and transmits the searched wallet address, user ID, and the unreceived NFT to the content data management server device 11 (step S402).

[0070] When the content data management server device 11 receives the wallet address and the unreceived NFT from the file server device 12, it generates transaction data indicating a transaction in which the unreceived NFT has been added to the wallet identified by the received wallet address (step S403). Next, the content data management server device 11 instructs the ledger management system 14 to add the transaction data generated in step S403 to the ledger (step S404).

[0071] The ledger management system 14 adds the transaction data to the ledger (step S405) in accordance with the instruction from the content data management server device 11. Then, the ledger management system 14 transmits a completion notification of adding the transaction data to the ledger to the content data management server device 11 (step S406).

[0072] The content data management server device 11 instructs the file server device 12 to update the NFT acquisition log table (FIG. 4) in response to the completion notification from the ledger management system 14 (step S407). This update instruction includes the user ID and the NFT.

[0073] The file server device 12 updates the NFT acquisition log table in accordance with the instruction from the content data management server device 11 (step S408). Specifically, the file server device 12 searches for a data record corresponding to the NFT included in the instruction from the NFT acquisition log table (FIG. 4) corresponding to the user ID included in the instruction, and rewrites "Not received" stored in the "Receipt status" field of the searched data record to information such as "Receipt completed at 17:15 on March 23, 2023." This "17:15 on March 23, 2023" is, for example, the current time at the time when the file server device 12 updates the NFT acquisition log table, but may also be the time indicated by the transaction data added to the ledger.

[0074] Next, the content data management server device 11 notifies the user terminal device 15W of the transaction data that has been added to the ledger (step S409). The user terminal device 15W adds the unreceived NFTs to the wallet in accordance with the transaction data notified from the content data management server device 11 (step S410).

[0075] Through the above process, the user becomes the owner of the content data.

[0076] (Content acquisition process flow) A user can download content data corresponding to an NFT contained in a wallet managed by the user terminal device 15W from the storage system 13 at any time and play it on the user terminal device 15W.

[0077] 12 is a diagram showing a content acquisition process flow. The user terminal device 15W determines whether or not there is an NFT corresponding to content data that has not been downloaded to the user terminal device 15W among the NFTs included in the wallet (step S501). If it is determined in step S501 that there is no NFT corresponding to content data that has not been downloaded, the process described below in the content acquisition process flow is not executed.

[0078] On the other hand, if it is determined in step S501 that there is an NFT corresponding to the content data that has not been downloaded, the user terminal device 15W requests the ledger management system 14 for a download source URI (Uniform Resource Identifier) ​​of the content data that has not been downloaded (step S502). This request includes an NFT corresponding to the content data that has not been downloaded. The ledger management system 14 transmits the URI corresponding to the NFT included in the request received from the user terminal device 15W to the user terminal device 15W as the download source URI of the requested content data (step S503).

[0079] The user terminal device 15W uses the URI received from the ledger management system 14 to request the storage system 13 to transmit the content data (step S504). In response to the transmission request from the user terminal device 15W, the storage system 13 transmits the content data to the user terminal device 15W (step S505).

[0080] The user terminal device 15W can play the downloaded content data in response to a user's instruction. For example, if the content data is data representing a 3D shape (3D data), the user terminal device 15W displays a virtual space and displays an image of an object (hereinafter, referred to as a "virtual object") of a 3D shape represented by the 3D data, which is placed in the virtual space. The user can freely change the position, angle, etc. of the virtual object in the virtual space, and can freely change the viewpoint and line of sight in the virtual space to view the virtual object in the virtual space from various directions while moving in the virtual space.

[0081] For example, if the content data is audio data, the user terminal device 15W pronounces the sound represented by the audio data. Also, if the content data is still image data or video data, the user terminal device 15W displays the still image represented by the still image data or the video represented by the video data.

[0082] According to the above-mentioned content data management system 1, an NFT associated with content data that is provided only to a user who has had a specific experience, such as participating in a concert, is included in the user's wallet. As a result, the ledger managed according to the blockchain technology guarantees the uniqueness of the content data and also guarantees that the user is the legitimate owner of the content data. Therefore, copies of such content data will not be used by others, and such content data will not be altered by others. As a result, the value of the premium associated with the content data will not decrease due to unauthorized copying or alteration of the content data.

[0083] [Variations] The above-described embodiment is one embodiment of the present invention, and may be modified in various ways within the scope of the technical concept of the present invention. Examples of such modifications are shown below. Two or more of the following modifications may be combined as appropriate.

[0084] (1) The configuration shown in Fig. 1 is one example of the configuration of the content data management system 1, and may be modified in various ways. For example, the user terminal device 15 that executes a web browser application and the user terminal device 15 that executes a wallet application are physically the same terminal device, but these user terminal devices 15 may be physically different terminal devices. Also, the content data management server device 11 and the file server device 12 are different devices, but these devices may be realized by the same device.

[0085] In addition, the storage system 13 is assumed to be a distributed storage using a P2P network, but is not limited to this, and the storage system 13 may be configured by a single server device or a group of multiple redundant server devices. In this case, the file server device 12 may play the role of the storage system 13.

[0086] As described in the embodiment, if the wallet application executed by user terminal device 15 is independent of the Web browser application, the user can execute the user registration processing flow (FIG. 6) and the NFT application acceptance processing flow (FIG. 7) using the already installed Web browser application while away from home, such as at a concert venue, and download the wallet application to user terminal device 15 after returning home, and execute the wallet generation processing flow (FIG. 10) and subsequent steps. Therefore, if the amount of data communicated by user terminal device 15 is to be minimized due to reasons such as a poor communication environment while away from home, or fees being incurred for data communication, it is desirable for the wallet application to be independent of the Web browser application.

[0087] (2) In the above-described embodiment, the web browser application and wallet application executed on user terminal device 15 are separate programs, but a single program having a web browser function, a wallet function, and a player function may be executed by user terminal device 15.

[0088] (3) In the above-described embodiment, the wallet application executed on user terminal device 15 has a player function, but the wallet application may not have the player function, and a player application, which is a program that provides the player function, may be executed by user terminal device 15 separately from the wallet application.

[0089] (4) In the above-described embodiment, the wallet is generated and stored in user terminal device 15, but the wallet may also be generated and stored in another device accessible by user terminal device 15 (e.g., content data management server device 11, or a server device other than content data management server device 11).

[0090] (5) The order of processing performed by the content data management system 1 described in the above embodiment is one example and may be changed in various ways. For example, in the above embodiment, the NFT application acceptance processing flow (FIG. 7) is performed after the user registration processing flow (FIG. 6), but after the provision conditions are determined in step S201 of the NFT application acceptance processing flow, if the result of the determination is positive, the user registration processing flow (FIG. 6) may be performed, and then the processing from step S202 onwards in the NFT application acceptance processing flow may be performed.

[0091] (6) In the above-described embodiment, whether the user is within a specified area within a specified period of time is confirmed based on the current location of the user terminal device 15 measured by the user terminal device 15 and the current time. However, the method of confirming that the user is within a specified area within a specified period of time is not limited to this.

[0092] For example, a QR code (registered trademark) showing authentication information (keywords, etc.) corresponding to the event may be placed within an event venue, and the user may photograph the QR code with the camera of user terminal device 15, decode the QR code, and transmit the obtained authentication information to content data management server device 11. In this case, content data management server device 11 can confirm that the user of user terminal device 15 was present at the event venue corresponding to the authentication information during the event, based on the authentication information transmitted from user terminal device 15. Note that instead of the QR code, a code other than a QR code or unencoded authentication information may be used.

[0093] Also, instead of reading the QR code, a device with a data transmission function, such as an NFC (Near Field Communication) tag storing authentication information, may be placed in the event venue, and the user may obtain the authentication information transmitted from the device using user terminal device 15 and transmit it to content data management server device 11. In this case, the method by which the device with the data transmission function transmits the authentication information may be any of a method using radio waves, a method using sound (for example, a sound in a high frequency band that cannot be heard by humans), a method using light, and the like.

[0094] Also, a card on which a code such as a QR code or uncoded authentication information is printed, or a device such as an NFC tag storing authentication information may be distributed to users who participate in the event instead of being placed at the event venue. In this case, the user can use the distributed card or device to transmit authentication information from the user terminal device 15 to the content data management server device 11 at a location other than the event venue, thereby allowing the content data management server device 11 to confirm that the user has participated in the event. In this case, for example, a time limit may be set such that if the authentication information is not transmitted from the user terminal device 15 to the content data management server device 11 before a predetermined time has elapsed (for example, within two hours) after the end of the event, content data will not be provided to the user.

[0095] Alternatively, a device equipped with a data transmission function that is installed at the event venue or distributed to a user who has participated in the event may transmit an NFT instead of authentication information. In this case, the user receives an NFT transmitted from the device by using a user terminal device 15 (user terminal device 15W) running a wallet application, adds the received NFT to the wallet, and then notifies the content data management server device 11 of receipt of the NFT. The notification includes the NFT. In response to this notification, the content data management server device 11 updates the NFT acquisition log table (FIG. 4) and transmits transaction data indicating that the NFT has been added to the user's wallet to the ledger management system 14. The ledger management system 14 adds the transaction data received from the content data management server device 11 to the ledger. In this case, the content data management server device 11 can confirm that the user has participated in the event by receiving a notification of receipt of the NFT from the user terminal device 15.

[0096] (7) In the above-described embodiment, when a user goes to an event venue in real space and participates in an event at the event venue, specific content data is provided to the user. As long as the content data is provided by the content data management system 1 only to users who have had a specific experience, the type of the specific experience is not limited to participation in an event in real space. For example, the condition for providing the content data may be that the user uses the user terminal device 15 to watch videos or the like that are streamed or broadcast in real time during the event. Also, the condition for providing the content data may be that the user uses the user terminal device 15 to watch videos or the like that are archived after the event. When videos or the like are distributed, the content data management server device 11 identifies the user who has logged in using the user terminal device 15 and distributes the videos or the like to the user terminal device 15, thereby confirming that the user has had a specific experience. Also, when videos or the like are broadcast from a broadcast station, the user terminal device 15 has a receiver such as a television tuner, and transmits identification information of a program from which the receiver has received the videos or the like to the content data management server device 11. The content data management server device 11 can confirm, based on the program identification information received from the user terminal device 15, that the user of the user terminal device 15 has had a specific experience.

[0097] When the specific experience is participation in an event at an event venue, data on the user's behavior (user behavior data) used to confirm that the user has had the specific experience is data indicating the current location and current time of the user terminal device 15. In other words, the current location and current time of the user terminal device 15 indicate the user's behavior that the user of the user terminal device 15 was at that location at that time.

[0098] Furthermore, in the case where the specific experience is viewing a video or the like received by the user terminal device 15, the user behavior data used to confirm that the user has had a specific experience is, for example, identification information of the video or the like received by the user terminal device 15. For example, in the case where a video or the like is distributed from the content data management server device 11 to the user terminal device 15, the identification information of the video or the like received by the user terminal device 15 is, for example, the title of a movie. In the case where a video or the like is broadcast from a broadcast station and received by the user terminal device 15, the identification information of the video or the like received by the user terminal device 15 is, for example, the channel used by the receiver provided in the user terminal device 15 to receive the broadcast and the time of reception.

[0099] (8) In the above embodiment, the determination as to whether or not the user has had a specific experience (FIG. 7, step S201) is made by the user terminal device 15, but the determination may be made by the content data management server device 11. In that case, the content data management server device 11 may acquire data on the user's behavior used for the determination (user behavior data, for example, location data indicating the current location of the user terminal device 15) from the user terminal device 15 or from another device. The content data management server device 11 checks whether or not the user has had a specific experience based on the user behavior data acquired in this way.

[0100] (9) In the above-described embodiment, the content data acquired by user terminal device 15 is used for playback by the player function of the wallet application executed on user terminal device 15, but the manner in which the content data acquired by user terminal device 15 is used is not limited to this. For example, the content represented by the content data may be played by user terminal device 15 executing an application other than the wallet application.

[0101] Furthermore, the content data may be transmitted or output from the user terminal device 15 to an external device, and the content data may be used by the external device. For example, if the content data is data for a 3D printer, the user terminal device 15 may output the acquired data for the 3D printer to the 3D printer, and cause the 3D printer to model an object in accordance with the data for the 3D printer.

[0102] (10) In the above embodiment, the content data management server device 11 notifies the user terminal device 15W that transaction data indicating that an NFT has been added to a wallet has been added to a ledger and that the ownership of the content data associated with the NFT has been transferred to the user, but the method by which the user terminal device 15W recognizes the completion of the transaction is not limited to this. For example, the user terminal device 15W may inquire of the ledger management system 14 and recognize that an NFT has been added to the wallet based on a response from the ledger management system 14.

[0103] (11) In the above embodiment, the user terminal device 15W acquires the content data from the storage system 13 using the URI notified by the ledger management system 14, but the method by which the user terminal device 15W acquires the URI of the download source of the content data is not limited to this. For example, the content data management server device 11 may acquire the URI from the ledger management system 14 and notify the user terminal device 15W of the URI.

[0104] (12) In the above-described embodiment, the user terminal device 15W acquires the content data directly from the storage system 13. However, for example, the content data management server device 11 may acquire the content data from the storage system 13 and transmit it to the user terminal device 15W.

[0105] (13) The NFTs stored in the NFT acquisition log table (FIG. 4) for each user, i.e., the NFTs added to each user's wallet, serve to identify the content data to be provided when the user has a specific experience. Therefore, if there is content metadata, which is information about the content data that indicates what kind of experience the user had when the content data was provided to that user, it is possible to know what kind of experience each user had in the past. Therefore, the content data management system 1 may select an advertisement suitable for the user of the wallet based on the NFT added to the wallet, and transmit advertisement data indicating the selected advertisement to the user terminal device 15 of that user.

[0106] 13 is a diagram illustrating an example of the configuration of a content table stored in the file server device 12 in this modified example. That is, in this modified example, the content table has a "content metadata" field in addition to a "content ID" field and a "conditions for provision" field. This "content metadata" field stores data indicating the content of the experience of the user to whom the content data identified by the content ID is provided. For example, if the content data identified by the content ID is provided only to users who attended a concert by Yamada Hanako at the concert venue, data such as "Yamada Hanako concert (venue attendance)" is stored in the "content metadata" field of the data record in the content table related to that content ID.

[0107] 14 is a diagram showing a configuration of a content data management system 1 according to this modification. In this modification, the content data management system 1 includes an advertisement distribution server device 16. The advertisement distribution server device 16 stores a large amount of advertisement data indicating advertisements, and upon receiving a request including user attribute data indicating user attributes from the content data management server device 11, selects advertisement data indicating an advertisement corresponding to the attributes indicated by the user attribute data, and transmits the selected advertisement data to the content data management server device 11.

[0108] The content data management server device 11 reads out content metadata corresponding to the content ID (content ID identifying content data associated with an NFT) stored in the NFT acquisition log table (FIG. 4) from the content table (FIG. 13), and transmits a request including the read content metadata as user attribute data to the advertisement distribution server device 16. The advertisement distribution server device 16 selects advertisement data indicating advertisements corresponding to the user attributes indicated by the content metadata included in the request, that is, the user's hobbies and preferences indicated by events the user has experienced in the past, and transmits the selected advertisement data to the content data management server device 11.

[0109] The content data management server device 11 transmits the advertisement data received from the advertisement distribution server device 16 to the user terminal device 15. The user terminal device 15 displays or pronounces (or displays and pronounces) the advertisement indicated by the advertisement data received from the content data management server device 11.

[0110] When user terminal device 15 acquires or uses premium content data, it may display an advertisement indicated by the advertising data received from content data management server device 11. In this case, content data management server device 11 may select advertising data of a company involved in acquiring the premium content data from advertising data of multiple companies, and transmit the selected advertising data to user terminal device 15. In this case, by participating in the provision of premium content data, the company can provide effective advertising to users who have been provided with the premium content data.

[0111] According to this modification, the user can receive advertisements according to his / her past experiences.

[0112] (14) The user behavior data used to confirm that the user has had a specific experience may be data indicating that the user has acquired a specific service or product. In this case, the content data management server device 11 determines whether the user has had a specific experience based on whether the service or product acquired by the user indicated by the user behavior data satisfies a predetermined condition.

[0113] For example, a winner of a lottery such as a lottery has the specific experience of winning the lottery. Also, a person who purchases a betting ticket (betting ticket, car ticket, boat ticket, etc.) for a race such as horse racing, bicycle racing, boat racing, or auto racing and wins a high payout has the specific experience of winning a high payout. Also, a person who purchases a specific product or service at a store has the specific experience of being able to obtain the product or using the product or service. Therefore, in the content data management system 1, data indicating the behavior of a winning lottery ticket, a betting ticket with a high payout, or the purchase of a specific product or service may be used as user behavior data.

[0114] For example, the operation of the content data management system 1 according to this modification will be described using the case where a user purchases a betting ticket (boat ticket) for a boat race as an example. When a user purchases a boat ticket with a high payout, if the boat ticket is a physical medium such as paper, the user photographs the boat ticket with the camera of the user terminal device 15 and transmits image data representing the photographed image of the boat ticket to the content data management server device 11. If the boat ticket is electronically issued data such as through online sales, the user displays an image of the boat ticket corresponding to the data on the user terminal device 15, photographs (takes a screenshot) the screen displaying the image of the boat ticket, and transmits image data representing the photographed image of the boat ticket from the user terminal device 15 to the content data management server device 11. In this case, the image data transmitted from the user terminal device 15 to the content data management server device 11 plays the role of user behavior data indicating the user's behavior, such as purchasing a boat ticket and being overjoyed when he or she learns the results of the boat race.

[0115] When the content data management server device 11 receives the image data, it recognizes the boat ticket identification information from the boat ticket image using known character recognition technology, and confirms that an NFT has not already been issued for a boat ticket with the same identification information. If it is confirmed that an NFT has not yet been issued for a boat ticket identified by the identification information recognized from the boat ticket image, the content data management server device 11 then recognizes the name of the race, the date the race was held, the location of the race, and the identification information of the bet boat from the boat ticket image using character recognition technology. The content data management server device 11 then compares the boat race result information obtained from a website or the like published by the boat race organization with the information recognized from the boat ticket image, and specifies the payout amount for that boat ticket.

[0116] The content data management server device 11 determines whether the payout amount specified as described above satisfies a predetermined condition (for example, a predetermined threshold or more). Then, only when the content data management server device 11 determines that the payout amount satisfies the predetermined condition, does it grant the user an NFT associated with the premium content data. The NFT granted to the user is added to the user's wallet, and the premium content data associated with the NFT is downloaded to the user terminal device 15 and played, etc.

[0117] For example, the premium content data may be data generated using information on a boat ticket, such as 3D data of a trophy engraved with the name, date, time, location, amount of payout, etc. of a race in which a user won a large payout.

[0118] Also, for example, the premium content data may be video data representing a recorded video of a race in which the user won a high payout. If the recorded video is a video shot by multiple cameras and allows the viewpoint to be moved during playback, the user terminal device 15 may store the position measured by the GNSS unit during the time when the race was being held, and the video may be played back with the recorded position as the viewpoint.

[0119] In the above example, the process of character recognition of information from the images of the boat tickets is carried out by the content data management server device 11, but the user terminal device 15 may also carry out the character recognition process.

[0120] In addition, in the above example, information is recognized as characters from the boat ticket, but if various information is written on the boat ticket in the form of a code such as a QR code (registered trademark), the user terminal device 15 or the content data management server device 11 may decode the code to obtain the information written on the boat ticket.

[0121] Also, in the above example, an NFT associated with the premium content data is granted to a user when the user takes an image of a boat ticket with the user terminal device 15 and transmits the image data of the taken boat ticket to the content data management server device 11. For example, if the content data management server device 11 can obtain information on boat tickets purchased by each user of the content data management system 1 from an external server device managed by an organization implementing a boat race, the content data management server device 11 may identify a user who purchased a boat ticket that won a high payout based on the information obtained by the content data management server device 11 from the external server device, without receiving image data of the boat ticket from the user terminal device 15, and grant the user an NFT associated with the premium content data.

[0122] The above example is an example of a case where a user purchases a boat ticket, but the same applies when a user purchases other types of betting tickets such as betting tickets or lottery tickets such as lottery tickets. In that case, the boat ticket described above is replaced with other types of betting tickets or lottery tickets. Also, when a user purchases a lottery ticket, the boat ticket with a payout is replaced with a winning lottery ticket.

[0123] Furthermore, when a user purchases a product or service at a store, the above-mentioned boat ticket is replaced with a receipt issued by the store. Then, the boat ticket with a payout is replaced with a receipt indicating the purchase of a specific product or service.

[0124] (15) In the above-described embodiment, the data managed in association with the NFT is content data. However, instead of content data, content activation data, which is data for activating content data, may be managed in association with the NFT.

[0125] In this modification, the user terminal device 15 stores invalidated content data. The invalidated content data may be, for example, data indicating content that can be viewed but has no value (for example, a trophy or a certificate with no name written on it), or data that is encrypted and does not indicate the content unless it is decrypted.

[0126] In this modification, the file server device 12 stores content activation data for activating the content data instead of the content data as data identified by the content ID. The content activation data may be, for example, data added to worthless content to give value to the content (for example, data indicating a name, award name, etc. to be engraved on a trophy or a certificate), or data indicating a decryption key for decrypting encrypted content data.

[0127] When a user has a specific experience and acquires an NFT, the user terminal device 15 acquires content activation data associated with the NFT, and activates pre-stored, invalidated content data using the acquired content activation data. Specifically, the user terminal device 15 engraves the name, award name, etc. indicated by the content activation data into a trophy, award certificate, etc. indicated by the pre-stored content data to generate valuable content data, or decrypts the pre-stored content data using a decryption key indicated by the content activation data. As a result, the user becomes able to use the content indicated by the activated content data.

[0128] According to this variant, after a user has a particular experience and an NFT corresponding to the content data is stored in the user's wallet, compared to when the content data is acquired by the user terminal device 15 by downloading it, etc., the user can use the content data more quickly, and the content data can be used even if the communication environment of the user terminal device 15 is poor.

[0129] (16) In the above-described embodiment, the wallet application executed by the user terminal device 15 integrates a wallet function and a player function for playing content represented by content data, as described above (see FIG. 5). When a new NFT associated with 3D data is added to the wallet, the user terminal device 15 that operates according to the wallet application in which the wallet function and the player function are integrated may download the 3D data from the storage system 13 without requiring any operation by the user. In addition, when the user terminal device 15 downloads 3D data, the user terminal device 15 may play the 3D data without requiring any operation by the user.

[0130] (17) A player integrated into a wallet application executed by the user terminal device 15 may perform real-time rendering of 3D images when playing back 3D data. In this case, the user can use the wallet application to freely manipulate, for example, a 3D-shaped virtual object represented by the 3D data in a virtual space.

[0131] (18) After being downloaded to user terminal device 15, premium content data associated with an NFT may be continuously stored in user terminal device 15 even when not in use, or may be temporarily stored in user terminal device 15 only while it is being used in user terminal device 15 and deleted from user terminal device 15 after use has ended. For example, if the premium content data is video data, the content represented by the premium content data may be streamed in user terminal device 15.

[0132] (19) The content data management server device 11 may determine whether an NFT added to a wallet satisfies specified conditions, and only if it determines that the NFT added to the wallet satisfies the specified conditions, may it grant a new NFT associated with premium content data to the user of that wallet.

[0133] For example, a user who uses a specific train line within a specific period of time is granted an NFT associated with image data of a stamp corresponding to the train line as premium content data. When a user reads, for example, a QR code (registered trademark) printed on a sheet medium installed in a train car or a QR code (registered trademark) displayed on a display installed in the train car with a user terminal device 15, the user terminal device 15 transmits to the content data management server device 11 position data indicating the position measured by the GNSS unit at that time and line data indicating the line obtained by decoding the read QR code (registered trademark). The content data management server device 11 receives the position data and line data as user behavior data, and grants the user an NFT associated with image data of a stamp corresponding to the information indicated by those data.

[0134] When a user uses trains on multiple specified routes, acquires all of the NFTs corresponding to those routes, and adds those NFTs to the user's wallet, the content data management server device 11 determines that the stamp rally is complete and grants the user an NFT associated with premium content data representing, for example, an image of a frame that displays a list of the collected stamps.

[0135] In addition, if an NFT in a wallet meets certain conditions, premium content data or premium goods that are not associated with an NFT may be given to the user instead of the NFT to which the premium content data is associated.

[0136] The above example is of a railway, but NFTs may also be granted for transportation other than railways.

[0137] (20) The premium content data associated with an NFT and given to a user may be data indicating a benefit to be used virtually, such as in a game executed in the user terminal device 15, or may be data indicating a benefit available in the real world. For example, the premium content data may be a ticket for participating in an online event, or may be a ticket for participating in an event held in the real world. In addition, the premium content data may be data indicating points, coupons, etc. that can be used when purchasing a product or service on an EC site or in a physical store.

[0138] (21) Premium content data may be used by companies to obtain information from users. For example, a user who purchases a specified food product may use the camera of the user terminal device 15 to take a picture of the receipt for the purchase of the product, and transmit the picture data representing the picture to the content data management server device 11 as user behavior data. Upon receiving the user behavior data, the content data management server device 11 may grant the user of the user terminal device 15 an NFT associated with premium content data representing a participation ticket to a game in which a new food product is simulated or a product development event held in the real world or online.

[0139] When a game is awarded to a user, information that the user inputs to user terminal device 15 while playing the game is transmitted by user terminal device 15 to content data management server device 11. Content data management server device 11 provides the information thus received from user terminal device 15 to the food manufacturer. The food manufacturer can use the information provided by content data management server device 11 to develop products.

[0140] When a user is given a participation ticket to a product development event, the food manufacturer can use information obtained from the user at the product development event to develop a product.

[0141] (22) The content data management system 1 may operate in conjunction with external systems that users use to purchase products and services (e.g., EC (Electronic Commerce) sites, POS (Point of Sale) systems, cashless payment service platforms, etc.).

[0142] When a user of the content data management system 1 purchases a product or service on an EC site, the EC site transmits data (hereinafter referred to as "purchase history data") indicating the user's identification information and information regarding the product or service purchased by the user (the name of the product or service, the purchase date, the purchase amount, the purchase quantity, etc.) to the content data management server device 11.

[0143] Furthermore, when a user of the content data management system 1 purchases a product or service at a brick-and-mortar store using a point card, a prepaid card, or the like, the POS system of the brick-and-mortar store acquires the user's identification information from the point card, etc. The POS system transmits to the content data management server device 11 purchase history data indicating information about the product or service purchased by the user and the user's identification information acquired from the point card, etc.

[0144] The process of extracting purchase history data of users of the content data management system 1 from the purchase history data of an unspecified number of customers may be performed in the content data management system 1, or in an external system such as an EC site.

[0145] Furthermore, when a user of the content data management system 1 purchases a product or service at a brick-and-mortar store using a code payment service, which is a type of cashless payment service (a service in which a user terminal device reads a code such as a QR code (registered trademark) placed in a store, or a POS system reads a code such as a QR code (registered trademark) displayed on a user terminal device, and payment is made), the user terminal device 15 detects the use of the code payment service and prompts the user to take a picture of the receipt, for example, by displaying a pop-up. When the user photographs the receipt for the purchase of the product or service in response to the prompt, the user terminal device 15 performs character recognition from the photographed image, obtains information about the purchased product or service, and transmits purchase history data indicating the information and identification information for identifying the user to the content data management server device 11. The process of performing character recognition from an image may be performed in the content data management server device 11.

[0146] The content data management server device 11 uses purchase history data received from an EC site, a POS system, or a user terminal device 15 as user behavior data, and grants an NFT associated with premium content data to a user who purchases a specific product or service.

[0147] (23) Data representing sounds picked up by the microphone of user terminal device 15 may be used as user behavior data.

[0148] For example, when participating in a specific event, the sound heard at the venue of the event is picked up by, for example, the organizer of the event, and sound data representing the picked up sound is transmitted to the content data management server device 11. The user participating in the event transmits sound data representing the sound picked up by the microphone of the user terminal device 15 to the content data management server device 11. In this case, the sound data transmitted from the user terminal device 15 plays the role of user behavior data indicating the user's behavior of participating in a specific event. If the content data management server device 11 determines that the sound data are sound data that have picked up the same sound, it grants the user an NFT associated with premium content data.

[0149] Also, for example, the microphone of user terminal device 15 picks up the playback sound of a specific song, and transmits sound data representing the picked up sound to content data management server device 11. In this case, the sound data transmitted from user terminal device 15 plays the role of user action data indicating the user's action of listening to a specific song. When content data management server device 11 determines that the sound data of a specific song stored in advance and the sound data transmitted from user terminal device 15 are sound data of the same song, it grants the user an NFT associated with premium content data.

[0150] (24) In the case where the premium content data is large in data volume, such as video data or 3D data, for example, storage system 13 may transmit lightweight premium content data, which is data in which the amount of information of the premium content data has been reduced, to user terminal device 15, and then transmit the large amount of premium content data to user terminal device 15 while user terminal device 15 is playing back the content represented by the lightweight premium content data.

[0151] In this variant, the user terminal device 15 plays content with a small amount of information represented by the light-weight premium content data (e.g., low-resolution video, low-resolution 3D images, etc.) while receiving premium content data with a large amount of data, and when reception of the premium content data is complete, the user terminal device 15 uses the received premium content data to switch the content being played to content with a large amount of information.

[0152] According to this modification, the user can enjoy the content, although the amount of information is small, even while the time required for downloading the large amount of premium content data is passing.

[0153] (25) When an NFT associated with premium content data is transferred from a user to another person, the association between the NFT and the premium content data may be deleted. In this case, premium content data other than the deleted premium content data may be associated with the NFT.

[0154] (26) When a user uses a utility site that can only be accessed by people who hold specific NFTs, the wallet app may perform a process of presenting the NFTs in the wallet to the utility site. In this case, user terminal device 15 running the wallet app accesses the utility site using a pre-stored Uniform Resource Locator (URL), selects an NFT required to log in to the utility site from among the NFTs in the user's wallet, and passes the selected NFT to the utility site.

[0155] In addition, after logging in to the utility site, the user terminal device 15 running a wallet application may deliver premium content data associated with the NFT in the wallet to the utility site.

[0156] For example, if the utility site is a site that provides a metaverse space and the premium content data is 3D data, a user can easily operate a 3D avatar in the metaverse space using a user terminal device 15 running a wallet app.

[0157] (27) Premium content data may be data indicating the right to view specific data stored in cloud storage.

[0158] (28) When a user is granted an NFT associated with premium content data, the user may be allowed to select a desired one from among multiple premium content options. In this modification, the content data management server device 11 stores identification information of multiple premium content data that can be associated with the NFT granted to the user, and when the user is granted an NFT, transmits information on the content indicated by the candidate premium content data to the user terminal device 15. The user terminal device 15 uses the information received from the content data management server device 11 to display a screen prompting the user to select one of multiple contents. When the user selects one of the contents on the screen, the user terminal device 15 transmits identification information of the content selected by the user to the content data management server device 11. The content data management server device 11 generates an NFT associated with premium content data corresponding to the content indicated by the identification information received from the user terminal device 15, and grants it to the user.

[0159] (29) Before an NFT associated with premium content data is granted to a user, the user may be allowed to choose whether or not to accept the NFT. In this modification, when an NFT associated with premium content data becomes available for granting to a user, the content data management server device 11 transmits information on the content indicated by the premium content data to the user terminal device 15. The user terminal device 15 uses the information received from the content data management server device 11 to display a screen asking the user whether or not the content to be granted is necessary. When the user inputs whether or not the content is necessary on the screen, the user terminal device 15 transmits the data indicating the necessity input by the user to the content data management server device 11. If the data received from the user terminal device 15 indicates "necessary," the content data management server device 11 grants the NFT to the user, and if the data received from the user terminal device 15 indicates "not necessary," the content data management server device 11 does not grant the NFT to the user. [Explanation of symbols]

[0160] 1...content data management system, 11...content data management server device, 12...file server device, 13...storage system, 14...ledger management system, 15...user terminal device, 16...advertising distribution server device.

Claims

[Claim 1] A process of associating the NFT with content data or content activation data which is data for activating the content data; A process of acquiring user behavior data indicating a user's behavior of purchasing a product or service; A process of determining whether or not a product or service purchased by the user indicated by the user behavior data satisfies a predetermined condition; and adding transaction data indicating that the NFT has been added to the user's wallet to the blockchain ledger only if the product or service is determined to satisfy a predetermined condition. A system that performs the above.

Images