JP7826100B2 - Information processing device, method, and program - Google Patents

Description

This disclosure relates to an information processing device, method, and program.

For example, in various businesses, including the entertainment industry, one of the main challenges is to develop existing customers into more engaged customers (i.e., turning them into fans).

Patent Document 1 discloses technology that provides special effects to specific participants (e.g., participants who participate in many virtual events, participants who purchase specific products, or participants who have made a certain amount of payment) selected based on the behavioral history of event participants.

JP 2018-094326 A

However, with the technology described in Patent Document 1, participants are evaluated based on behavioral indicators over a specified period (e.g., the number of events participated in over the entire period or a certain period (within the past week), the number of items purchased, the total amount spent, support parameters, or the score in a game related to the event). For example, event participation and payments made when a certain acting character had few fans would be treated the same as event participation and payments made after the acting character's fan base had grown. As such, with the technology described in Patent Document 1, it was difficult to evaluate participants by taking into account the qualitative aspects of similar behavior. Furthermore, with the technology described in Patent Document 1, it was difficult to evaluate participants by taking into account their behavioral history with parties other than the virtual event organizer, such as purchases of related products from different businesses or purchases of specific products through secondary distribution.

One objective of the present disclosure is to provide technology that takes into account a variety of information to evaluate customers as fans. Another objective of the present disclosure is to provide technology that analyzes a variety of customer information and extracts useful information.

A program according to one aspect of the present disclosure causes a computer to function as a means for identifying NFTs (Non-Fungible Tokens) held by a customer by querying a distributed ledger system, and a means for calculating the customer's score as a fan of a target concept based on the NFTs held by the customer and evaluation rules that define evaluation values assigned to each of multiple NFTs related to the target concept.

1 is a block diagram showing a configuration of an information processing system according to an embodiment of the present invention; FIG. 2 is a block diagram showing the configuration of a customer terminal according to the present embodiment. FIG. 2 is a block diagram showing the configuration of a server according to the present embodiment. FIG. 1 is a diagram illustrating the configuration of a distributed ledger system according to an embodiment of the present invention. FIG. 2 is a block diagram showing the configuration of an evaluator terminal according to the present embodiment. FIG. 1 is an explanatory diagram of one aspect of the present embodiment. FIG. 4 is a diagram illustrating a data structure of an evaluation table according to the present embodiment. 10 is a flowchart of an NFT granting process according to the present embodiment. 10 is a flowchart of an evaluation rule editing process according to the present embodiment. 10 is a flowchart of a score confirmation process according to the present embodiment. 10 is a flowchart of a provision mode adjustment process according to the present embodiment.

One embodiment of the present invention will be described in detail below with reference to the drawings. In the drawings used to explain the embodiment, identical components will generally be assigned the same reference numerals, and repeated explanations will be omitted.

(1) Configuration of Information Processing System The configuration of the information processing system will be described below. Fig. 1 is a block diagram showing the configuration of the information processing system according to this embodiment.

As shown in FIG. 1 , the information processing system 1 includes a customer terminal 10 , a customer evaluation server 30 , a distributed ledger system 50 , and an evaluator terminal 70 .
The customer terminal 10, the customer evaluation server 30, the distributed ledger system 50, and the evaluator terminal 70 are connected via a network (e.g., the Internet) NW.

The customer terminal 10 is an example of an information processing device that sends requests to the customer evaluation server 30. The customer terminal 10 is, for example, a smartphone, tablet terminal, or personal computer. The user of the customer terminal 10 is a fan of some specific concept (for example, a specific person, group, character, work, brand, category, etc.; hereinafter referred to as the "target concept").

The customer evaluation server 30 is an example of an information processing device. The customer evaluation server 30 provides the customer terminal 10 with a response in response to a request sent from the customer terminal 10. The customer evaluation server 30 provides the evaluator terminal 70 with a response in response to a request sent from the evaluator terminal 70. The customer evaluation server 30 is, for example, a web server. A user of the customer evaluation server 30 is, for example, the operator of the information processing system 1.

The distributed ledger system 50 manages the distributed ledger in response to requests from the customer terminal 10, the customer evaluation server 30, or the evaluator terminal 70.

The evaluator terminal 70 is an example of an information processing device that sends requests to the customer evaluation server 30. The evaluator terminal 70 is, for example, a smartphone, tablet terminal, or personal computer. The user of the evaluator terminal 70 is an evaluator for the target concept. An evaluator for the target concept is a person (including an organization) who defines rules for evaluating customers as fans of the target concept. As an example, an evaluator is a person who holds rights to the target concept (e.g., copyright, trademark, publicity right, or merchandising right based on contract or business practice), or a person who provides goods, services, or content related to the target concept, or a person designated by such a person (for example, a fan community).

(1-1) Configuration of the Customer Terminal The configuration of the customer terminal will be described below. Fig. 2 is a block diagram showing the configuration of the customer terminal of this embodiment.

As shown in FIG. 2, the customer terminal 10 includes a storage device 11, a processor 12, an input/output interface 13, and a communication interface 14. The customer terminal 10 is connected to a display 21.

The storage device 11 is configured to store programs and data. The storage device 11 is, for example, a combination of ROM (Read Only Memory), RAM (Random Access Memory), and storage (e.g., flash memory or a hard disk).

The programs include, for example, the following programs:
・OS (Operating System) programs ・Application programs that execute information processing (e.g., web browsers)

The data includes, for example, the following data:
- Databases referenced in information processing - Data obtained by executing information processing (i.e., the results of executing information processing)

The processor 12 is a computer that executes the programs stored in the storage device 11 to realize the functions of the customer terminal 10. The processor 12 is, for example, at least one of the following:
・CPU (Central Processing Unit)
・GPU (Graphic Processing Unit)
・ASIC (Application Specific Integrated Circuit)
・FPGA (Field Programmable Array)

The input/output interface 13 is configured to acquire information (e.g., user instructions) from an input device connected to the customer terminal 10 and to output information (e.g., images) to an output device connected to the customer terminal 10.
The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof.
The output device is, for example, a display 21, a speaker, or a combination thereof.

The communication interface 14 is configured to control communication between the customer terminal 10 and an external device (e.g., the customer evaluation server 30 or the distributed ledger system 50).

The display 21 is configured to display images (still images or videos). The display 21 is, for example, a liquid crystal display or an organic EL display.

(1-2) Server Configuration The server configuration will be described below with reference to Fig. 3, which is a block diagram showing the configuration of the server according to this embodiment.

As shown in FIG. 3, the customer evaluation server 30 includes a storage device 31, a processor 32, an input/output interface 33, and a communication interface 34.

The storage device 31 is configured to store programs and data. The storage device 31 is, for example, a combination of ROM, RAM, and storage (e.g., flash memory or a hard disk).

The programs include, for example, the following programs:
・OS programs ・Application programs that execute information processing

The data includes, for example, the following data:
・Databases referenced in information processing ・Results of information processing

The processor 32 is a computer that executes the program stored in the storage device 31 to realize the functions of the customer evaluation server 30. The processor 32 is, for example, at least one of the following:
CPU
・GPU
・ASIC
・FPGA

The input/output interface 33 is configured to acquire information (user instructions) from an input device connected to the customer evaluation server 30 and to output information (e.g., an image) to an output device connected to the customer evaluation server 30 .
The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof.
The output device is, for example, a display.

The communication interface 34 is configured to control communication between the customer evaluation server 30 and an external device (e.g., a customer terminal 10, a distributed ledger system 50, or an evaluator terminal 70).

(1-3) Configuration of the Distributed Ledger System The configuration of the distributed ledger system will be described. Figure 4 is a diagram showing the configuration of the distributed ledger system of this embodiment.

As shown in Figure 4, the distributed ledger system 50 includes multiple node computers 55-1 to 55-4.

The node computers 55 are connected to each other via a network (which may include the network NW in FIG. 1). In this embodiment, the network may include a public network, a private network, a dedicated line, a VPN (Virtual Private Network), or a combination thereof. The node computers 55 are connected to the network, for example, by wire or wirelessly. The node computers 55 communicate with each other in a peer-to-peer manner.

The node computer 55 manages the distributed ledger using, for example, blockchain technology.
Specifically, one of the node computers 55 acquires data related to token transactions to be recorded. The node computer 55 creates a block including the acquired data and adds it to the blockchain. The node computer 55 transmits information about the added block to the other node computers 55. The other node computers 55 verify the accuracy of the received block and, if the verification is successful, add the block to the blockchain. The node computers 55 finalize the blockchain, for example, according to the number of linked blocks (number of approvals). As a result, the same distributed ledger is stored across the multiple node computers 55 that make up the distributed ledger system 50. The stored data is encrypted as appropriate.

The configuration of the distributed ledger system 50 is not limited to that shown in Figure 4. For example, the distributed ledger system 50 may include five or more node computers 55, or may include two or three node computers 55. Furthermore, the number of node computers 55 comprising the distributed ledger system 50 may change over time.

The hardware configuration of the node computer 55 may be the same as or similar to that of the customer terminal 10 or the customer evaluation server 30, so a detailed description will be omitted. As an example, the node computer 55 includes a processor, a storage device, an input/output interface, a communication interface, an input device, an output device, or a combination thereof.

(1-4) Configuration of the Evaluator Terminal The configuration of the evaluator terminal will be described below. Fig. 5 is a block diagram showing the configuration of the evaluator terminal of this embodiment.

As shown in FIG. 5, the evaluator terminal 70 includes a storage device 71, a processor 72, an input/output interface 73, and a communication interface 74. The evaluator terminal 70 is connected to a display 81.

The storage device 71 is configured to store programs and data. The storage device 71 is, for example, a combination of ROM, RAM, and storage (e.g., flash memory or a hard disk).

The programs include, for example, the following programs:
・OS programs ・Application programs that execute information processing (e.g., web browsers)

The data includes, for example, the following data:
- Databases referenced in information processing - Data obtained by executing information processing (i.e., the results of executing information processing)

The processor 72 is a computer that realizes the functions of the evaluator terminal 70 by running a program stored in the storage device 71. The processor 72 is, for example, at least one of the following:
CPU
・GPU
・ASIC
・FPGA

The input/output interface 73 is configured to acquire information (e.g., user instructions) from an input device connected to the evaluator terminal 70, and to output information (e.g., an image) to an output device connected to the evaluator terminal 70.
The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof.
The output device is, for example, a display 81, a speaker, or a combination thereof.

The communication interface 74 is configured to control communication between the evaluator terminal 70 and an external device (e.g., the customer evaluation server 30 or the distributed ledger system 50).

The display 81 is configured to display an image (still image or video). The display 81 is, for example, a liquid crystal display or an organic EL display.

(2) One aspect of the embodiment One aspect of the present embodiment will be described below. Fig. 6 is an explanatory diagram of one aspect of the present embodiment.

As shown in FIG. 6, in response to an instruction from customer C11, the customer terminal 10 requests the customer evaluation server 30 to evaluate the score of customer C11 as a fan of the target concept T13 (sends an evaluation request to the customer evaluation server 30). This evaluation request includes information (e.g., the token ID of the NFT or identification information of wallet W12) that can identify the NFT (Non-Fungible Token) linked to customer C11's wallet W12 (i.e., the NFT held by customer C11). The customer evaluation server 30 identifies the NFT held by customer C11 based on the evaluation request. For example, the customer evaluation server 30 identifies the NFT held by customer C11 by querying the distributed ledger system 50 for the token ID of the NFT linked to customer C11's wallet ID.

The customer evaluation server 30 references the evaluation rule R14 associated with the target concept T13. The evaluation rule R14 is defined so as to be able to identify the evaluation value assigned to each of the multiple NFTs related to the target concept T13. NFTs related to the target concept T13 are typically, but are not limited to, NFTs that can be acquired by engaging in fan activities for the target concept T13. The customer evaluation server 30 calculates the score of customer C11 as a fan of the target concept T13 based on the NFTs held by customer C11 and the evaluation rule R14.

The customer evaluation server 30 sends the evaluation response to the customer terminal 10. The evaluation response includes information that can identify the score of customer C11 as a fan of the target concept T13, calculated by the customer evaluation server 30. The customer terminal 10 identifies the score based on the evaluation response and presents the score to customer C11.

In this way, the customer evaluation server 30 calculates the score of customer C11 as a fan of the target concept T13 by individually evaluating the NFTs held by customer C11 based on the evaluation rule R14 associated with the target concept T13. This allows the calculation of a customer's score by distinguishing between various NFTs that can be acquired through, for example, engaging in fan activities. For example, even for the same type of fan activity, different evaluations can be given to NFTs that can be acquired through the activity depending on the context of the activity (e.g., the time, place, or occasion when the activity was performed, or a commemorative event related to the target concept T13). Furthermore, even if multiple NFTs related to the same target concept T13 are issued by different issuers (e.g., issuers other than the evaluator), a common score as a fan of the target concept T13 can be calculated based on the evaluation values assigned to each NFT. Furthermore, even if a customer acquires (receives) an NFT through secondary distribution (e.g., customer-to-customer transactions) without the issuer's knowledge, the customer can be evaluated taking into account their ownership of the NFT. In other words, the customer evaluation server 30 can take into account a variety of information when evaluating customer C11 as a fan of the target concept T13.

(3) Database The database of this embodiment will be described. The following database is stored in the storage device 31.

(3-1) Evaluation Table The evaluation table of this embodiment will be described below with reference to Fig. 7, which shows the data structure of the evaluation table of this embodiment.

The evaluation table is a database that stores evaluation rules. Evaluation rules are information that define the evaluation value that a customer will earn by holding the corresponding NFT. The evaluation value corresponds to the material used to calculate a score as a fan of the target concept.

Evaluation tables are constructed separately for each target concept. Therefore, tokens for which evaluation values are defined in the evaluation table for a first target concept (hereinafter referred to as the "first evaluation table") may not overlap at all with tokens for which evaluation values are defined in the evaluation table for a second target concept (hereinafter referred to as the "second evaluation table"), or they may overlap partially or completely. Furthermore, because evaluation values in each database can be defined separately, the evaluation value defined for a given token in the first evaluation table will not necessarily match the evaluation value defined in the second evaluation table.

As shown in Figure 7, the evaluation table includes a "Rule ID" field, a "Token ID" field, a "Conditions for Assignment" field, a "Content" field, and an "Evaluation Value" field. Each field is associated with another.

The "Rule ID" field stores the rule ID. The rule ID is information that identifies the evaluation rule.

The "Token ID" field stores a token ID. The token ID is information that identifies the NFT to which the evaluation rule identified by the corresponding rule ID (hereinafter referred to as the "target rule") applies.

The "Assignment Condition" field stores assignment condition information. The assignment condition information is information about the conditions that must be met in order for an NFT to which the target rule applies (hereinafter referred to as the "target NFT") to be assigned. There are no particular restrictions on the format of the assignment condition information, but the assignment condition information may be written in natural language to help evaluators of the target concept understand the assignment conditions for NFTs.

The reward condition is typically defined as a customer taking a specific action (typically, fan activity) related to the target concept. The specific action may be, for example, visiting a specific location (e.g., an event venue or store), purchasing, borrowing (including renting), using, owning, or lending (including lending) a specific item (e.g., a ticket), service, or content, posting specific information on a social networking service (SNS), viewing specific content, applying for or participating in a specific campaign, or possessing one or more specific NFTs. Alternatively, the specific action may be encouraging a new customer (e.g., a customer who does not own any NFTs related to the target concept or whose score is below a predetermined value) to take at least one of the actions exemplified in the previous sentence, and the customer taking the encouraged action. Furthermore, the reward condition may include additional conditions for the specific action. The additional conditions may relate, for example, to time, date and time, location, quantity, number of times, frequency, amount, or number of people.

The "Content" field stores content information. Content information is information related to the content of the target NFT. There are no particular restrictions on the format of the content information, but the content information may be expressed in natural language, images, or audio to help the evaluator understand the content of the NFT. Here, the content of the target NFT is not limited to the information recorded in the target NFT, but may also include information that can be referenced from that information. As an example, if a URL (Uniform Resource Locator) is recorded in the target NFT, the content of the target NFT may include information (e.g., content) that can be referenced by that URL.

The "Evaluation Value" field stores evaluation value information. The evaluation value information is information regarding the evaluation value that a customer will obtain by holding the target NFT. The evaluation value information can be configured to be editable at the evaluator's instruction.

(4) Information Processing Information processing in this embodiment will be described.

(4-1) NFT Granting Process The NFT granting process of this embodiment will be described with reference to the flowchart of FIG.

The NFT granting process in Figure 8 may be initiated, for example, in response to a request from an evaluator.

As shown in FIG. 8, the evaluator terminal 70 executes a request to set the conditions and contents of the award (S170).
Specifically, the evaluator operates the evaluator terminal 70 to instruct the setting of the conditions for granting a new NFT and the content of the NFT. The evaluator terminal 70 generates a setting request for the conditions for granting and the content in response to the evaluator's instructions. The setting request includes information that can identify the conditions for granting and the content of the NFT that the evaluator wishes to set. The evaluator terminal 70 transmits the setting request to the customer evaluation server 30.

After step S170, the customer evaluation server 30 sets the conditions and contents of the award (S130).
Specifically, the customer evaluation server 30 acquires the setting request transmitted in step S170. Based on the setting request, the customer evaluation server 30 identifies the granting conditions and details of the NFT that the evaluator wishes to set. The customer evaluation server 30 stores the identified granting conditions and details in the storage device 31. As an example, the customer evaluation server 30 may store information on the identified granting conditions and details in a database for managing NFTs that the customer evaluation server 30 can grant.

After step S130, the customer evaluation server 30 detects behaviors that match the conditions for awarding (S131).
Specifically, the customer evaluation server 30 detects, based on information acquired from an external device, whether the customer has taken an action that meets any of the conditions for awarding set in step S130. The external device may be, for example, the customer terminal 10 or an external system. The external system may be, for example, a ticket system, an EC (Electronic Commerce) system, an SNS system, or a content viewing system.

As an example, the customer evaluation server 30 may detect that a customer has taken an action that meets the award conditions by, for example, obtaining from the customer terminal 10 a serial code that is issued to the customer as proof that the customer has taken that action. Alternatively, the customer evaluation server 30 may obtain the customer's behavioral history from an external system and analyze the behavioral history to determine whether the customer has taken an action that meets the award conditions.

After step S131, the customer evaluation server 30 executes the granting of NFT (S132).
Specifically, the customer evaluation server 30 grants an NFT corresponding to the granting condition to a customer whose behavior matching the granting condition is detected in step S131. For example, the customer evaluation server 30 requests the distributed ledger system 50 to grant the NFT to the customer. Here, before granting the NFT to the customer, the customer evaluation server 30 may inquire of the customer about information necessary for granting the NFT (e.g., the customer's wallet information).
Upon completion of step S132, the customer evaluation server 30 ends the NFT granting process of FIG.

(4-2) Evaluation Rule Editing Process The evaluation rule editing process of this embodiment will be described with reference to the flowchart of FIG.

The evaluation rule editing process in Figure 9 can be initiated, for example, in response to a request from an evaluator.

As shown in FIG. 9, the evaluator terminal 70 executes a request to view the evaluation rules (S270).
Specifically, the evaluator operates the evaluator terminal 70 to instruct viewing of the evaluation rules for the target concept related to the evaluator. The evaluator terminal 70 generates a request to view the evaluation rules in response to the instruction from the evaluator. The request includes information that can identify the evaluation rules that the evaluator wishes to view. The evaluation rules that the evaluator wishes to view may be all or part of the evaluation rules related to the target concept. The evaluator terminal 70 transmits the request to view to the customer evaluation server 30.

After step S270, the customer evaluation server 30 acquires the evaluation rules (S230).
Specifically, the customer evaluation server 30 acquires the viewing request sent in step S270. Based on the viewing request, the customer evaluation server 30 identifies the evaluation rule that the evaluator wishes to view. The customer evaluation server 30 acquires the identified evaluation rule from the evaluation table ( FIG. 7 ).

After step S230, the customer evaluation server 30 presents evaluation rules (S231).
Specifically, the customer evaluation server 30 transmits the evaluation rule acquired in step S230 to the evaluator terminal 70.

After step S231, the evaluator terminal 70 executes presentation of evaluation rules (S271).
Specifically, the evaluator terminal 70 acquires the evaluation rule transmitted in step S231. The evaluator terminal 70 presents the evaluation rule to the evaluator by, for example, displaying an image on the display 81.

After step S231, the evaluator terminal 70 executes a request to edit the evaluation rules (S272).
Specifically, the evaluator operates the evaluator terminal 70 to instruct editing of the evaluation rule for the target concept related to the evaluator. Here, editing of the evaluation rule may be either changing or deleting an already set evaluation rule, or adding a new evaluation rule. When the evaluator changes or deletes an already set evaluation rule, the evaluator may specify the target evaluation rule using an object displayed on the display 81 in step S271. The evaluator terminal 70 generates an editing request for the evaluation rule in response to the instruction from the evaluator. The editing request includes information that can identify the editing content desired by the evaluator. The editing content includes, for example, at least one of the following:
Evaluation rule to be changed Evaluation value information after change Evaluation rule to be deleted At least one of the token ID, assignment condition information, content information, and evaluation value information of the new evaluation rule

After step S272, the customer evaluation server 30 executes editing of the evaluation rules (S232).
Specifically, the customer evaluation server 30 acquires the editing request sent in step S272, and updates the evaluation table (FIG. 7) based on the acquired editing content.
Upon completion of step S232, the customer evaluation server 30 ends the evaluation rule editing process of FIG.

When an evaluator adds a new evaluation rule, the request to view the evaluation rule (S270), the acquisition of the evaluation rule (S230), the presentation of the evaluation rule (S231), and the presentation of the evaluation rule (S271) can be omitted.

(4-3) Score Confirmation Processing The score confirmation processing of this embodiment will be described below with reference to the flowchart of FIG.

The score confirmation process of Figure 10 may be initiated, for example, in response to a request from a customer.

As shown in FIG. 10, the customer terminal 10 executes a score evaluation request (S310).
Specifically, the customer operates the customer terminal 10 to instruct an evaluation of the customer's score as a fan of the target concept. The customer terminal 10 generates a score evaluation request in response to the customer's instruction. The evaluation request includes information that can identify the NFT held by the customer (e.g., a list of token IDs for the NFT or the customer's wallet information) and information that can identify the evaluation table used to calculate the score (e.g., information indicating the target concept). The customer terminal 10 sends the evaluation request to the customer evaluation server 30.

After step S310, the customer evaluation server 30 identifies the NFTs held (S330).
Specifically, the customer evaluation server 30 acquires the evaluation request sent in step S310. The customer evaluation server 30 identifies the NFT held by the customer based on the evaluation request. As an example, the customer evaluation server 30 may acquire, from the distributed ledger system 50, the token ID of the NFT linked to the customer's wallet information.

Note that the evaluation request may include multiple pieces of wallet information, not just one. If the evaluation request includes multiple pieces of wallet information, the customer evaluation server 30 may obtain the token ID of the NFT linked to any of the multiple pieces of wallet information from the distributed ledger system 50.

If a customer holds multiple wallets, the customer evaluation server 30 may obtain NFT token IDs linked to the customer's multiple wallet information from the distributed ledger system 50. As a first example, multiple pieces of wallet information are pre-registered in a database in association with a customer ID that identifies the customer, and the customer evaluation server 30 treats the wallet corresponding to the wallet information associated with the customer ID in the database as the customer's wallet. As a second example, at least one piece of wallet information is pre-registered in a database in association with a customer ID that identifies the customer, and the customer evaluation server 30 treats the wallet corresponding to the wallet information associated with the customer ID in the database as the customer's wallet. Furthermore, the customer evaluation server 30 infers that other wallets that are conducting transactions with the customer's wallet and that satisfy, for example, at least one of the following conditions are the customer's wallet (unregistered wallet):
- Another wallet is trading crypto assets or other tokens with your wallet, and the frequency of such transactions exceeds a threshold; - Another wallet has conducted a non-commercial transaction with your wallet; - Another wallet is associated with information that matches or is similar to your wallet (e.g., name, email address, or associated personal NFTs).

Furthermore, the evaluation request may include information for verifying that the customer has not falsified their wallet information (i.e., that the customer is not using someone else's wallet information). For example, such information may be an access token issued by an external system that provides a wallet corresponding to the wallet information specified by the customer. The external system authenticates the customer (e.g., confirms that the correct wallet ID and password combination have been entered), and if it is confirmed that the customer is the owner of the wallet, issues an access token to prove that fact.

NFTs may also be traded on a system that exists outside the distributed ledger system 50 (e.g., a private chain, sometimes called a second layer). In this case, the evaluation request may include information that identifies the system in which the NFTs held by the customer are actually traded, as well as the customer's wallet information in that system.

After step S330, the customer evaluation server 30 calculates the score (S331).
Specifically, the customer evaluation server 30 identifies the evaluation table (FIG. 7) to be used for calculating the customer's score based on the evaluation request, and acquires the evaluation table. The customer evaluation server 30 applies the evaluation rules stored in the evaluation table to the NFT identified in step S330.

As a first example, the customer evaluation server 30 determines, for each NFT held by a customer, whether an evaluation rule applicable to that NFT is stored in the evaluation table. If the customer evaluation server 30 finds a matching evaluation rule, it references the evaluation value defined in that evaluation rule. The customer evaluation server 30 may calculate the customer's score by summing the evaluation values for all evaluation rules applicable to the NFTs held by the customer.

As a second example, the customer evaluation server 30 may calculate the score of a customer by summing up a predetermined number of evaluation rules (e.g., the three with the highest evaluation values) in descending order of evaluation value for all evaluation rules applicable to the NFTs held by the customer.

Furthermore, the customer evaluation server 30 may correct the score of the customer based on the customer's attributes as exemplified below.
If a customer holds a first type of NFT (e.g., an NFT given as a bonus for purchasing a song or an NFT issued by a record company) but does not hold a second type of NFT (e.g., an NFT given as a bonus for purchasing a concert ticket or an NFT issued by a ticket sales company), the customer evaluation server 30 may add points to the customer's score. This allows for preferential treatment of customers who are fans of the target concept but who may have a narrow range of fan activities, and encourages them to broaden the range of their fan activities.
If a customer has not acquired an NFT to which the evaluation rule applies for a certain period of time, the customer evaluation server 30 may add points to the customer's score. This allows customers who are fans of the target concept but are at risk of losing interest to be given preferential treatment and encouraged to return to being fans.
The customer evaluation server 30 may refer to the transaction history for the NFT to which the evaluation rules apply, and may add points to the score of the customer if the frequency, amount, or number of acquisitions of the NFT in the most recent specified period exceeds a threshold. This allows customers who may be new fans of the target concept to be given preferential treatment and encouraged to develop into more core fans.
The customer evaluation server 30 references the transaction history for the NFT to which the evaluation rules apply, and identifies the customer (herein referred to as the "target customer") and other customers who have traded the NFT (hereinafter referred to as "connection 1 customers"), and the customer who has traded the NFT with the connection 1 customer (hereinafter referred to as "connection 2 customers"). The customer evaluation server 30 may add points to the score of the target customer by referencing the scores of the connection 1 customers or the connection 2 customers. As an example, the customer evaluation server 30 may determine the value to add to the target customer based on the maximum score of the connection 1 customers or the connection 2 customers. This allows target customers who have connections with core fans of the target concept to be given preferential treatment and encourages them to become even more core fans.

After step S331, the customer evaluation server 30 presents the score (S332).
Specifically, the customer evaluation server 30 transmits the score calculated in step S331 to the customer terminal 10. Note that the customer evaluation server 30 may provide the customer with an NFT that certifies the score instead of or in addition to transmitting the score.

After step S332, the customer terminal 10 acquires the score transmitted in step S332. The customer terminal 10 presents the customer's score to the customer by displaying an image on the display 81, for example.
Upon completion of step S332, the client terminal 10 ends the score confirmation process of FIG.

(4-4) Provision Mode Adjustment Processing The provision mode adjustment processing of this embodiment will be described with reference to FIG.

The provision mode adjustment process in Figure 11 can be initiated, for example, in response to a request from a customer.

As shown in FIG. 11, the customer terminal 10 executes a request for provision of goods or the like (S410).
Specifically, by operating the customer terminal 10, the customer instructs the purchase, rental, or use of goods, services, or content (hereinafter simply referred to as "goods, etc.") related to the target concept, or to reserve or apply for them. The customer terminal 10 generates a request for the provision of goods, etc. in response to the customer's instructions. The provision request includes information that can identify the NFT held by the customer, information that can identify the evaluation table used to calculate the score, and information that can identify the goods, etc. that the customer wishes to provide. The customer terminal 10 sends the provision request to the customer evaluation server 30.

After step S410, the customer evaluation server 30 identifies the NFTs held (S430).
Specifically, the customer evaluation server 30 acquires the provision request transmitted in step S410. The customer evaluation server 30 identifies the NFT held by the customer based on the provision request. As an example, the customer evaluation server 30 may acquire, from the distributed ledger system 50, the token ID of the NFT linked to the customer's wallet information.

After step S430, the customer evaluation server 30 calculates the score (S431).
Specifically, the customer evaluation server 30 identifies the evaluation table ( FIG. 7 ) to be used for calculating the customer's score based on the provision request, and acquires the evaluation table. The customer evaluation server 30 applies the evaluation rules stored in the evaluation table to the NFT identified in step S430. The method for calculating the customer's score in step S431 may be the same as or similar to the calculation method in step S331.

After step S431, the customer evaluation server 30 adjusts the provision mode of the product or the like (S432).
Specifically, the customer evaluation server 30 adjusts the manner in which the goods, etc. identified based on the provision request (i.e., specific goods, services, or content (which may include NFTs) related to the target concept that the customer wishes to receive) are provided to the customer in accordance with the score calculated in step S431.

As a first example, the customer evaluation server 30 may treat a customer with a higher score more favorably in terms of providing goods, etc. The favorable treatment may include at least one of the following.
Increasing the odds of winning an item, etc., whose availability is determined by lottery Allocating relatively high-quality or popular items, etc., among similar items, etc. (for example, seats with good viewing positions at an entertainment event) Increasing the number or amount of items that can be purchased Attaching benefits (which may include new NFTs) Accelerating the order or timing of provision Lowering the provision price Granting the right to experience the target concept (for example, shaking hands with a person who is the target concept)

As a second example, the customer evaluation server 30 may not grant the right to receive the goods, etc. identified based on the request to customers whose scores are below a threshold, and may grant the right to receive the goods, etc. only to customers whose scores are above the threshold.

As a third example, the customer evaluation server 30 sorts multiple customers in descending order of the scores calculated in step S431. The customer evaluation server 30 may not grant the right to receive the goods, etc. specified based on the request to customers who have not reached a predetermined rank, and may grant the right to receive the goods, etc. only to customers who have reached a predetermined rank or higher.

Upon completion of step S432, the customer evaluation server 30 terminates the provision mode adjustment process shown in Figure 11.

(5) Summary As described above, the customer evaluation server 30 identifies the NFTs held by a customer by querying the distributed ledger system and calculates the customer's score as a fan of the target concept based on the NFTs and the evaluation rules for the target concept. This allows the customer's score to be calculated while distinguishing between various NFTs that can be acquired through, for example, fan activities. For example, even if the same type of fan activity is involved, different evaluations can be assigned to NFTs that can be acquired through the activity depending on the context of the activity. Furthermore, even if multiple NFTs related to the same target concept are issued by different issuers (e.g., the seller of an artist's music and the organizer of the artist's live performance), a common score for the fan of the target concept can be calculated based on the evaluation values assigned to each NFT. Furthermore, even if a customer acquires an NFT through secondary distribution but the issuer is unaware of this fact, the customer can be evaluated taking into account the ownership of the NFT. In other words, the customer evaluation server 30 allows the evaluation of a customer as a fan of the target concept to be performed taking into account a variety of information.

The customer evaluation server 30 may adjust the manner in which specific products, etc. related to the target concept are provided to the customer depending on the score. This allows those who provide products, etc. related to the target concept to flexibly determine the manner in which the products, etc. are provided depending on the customer's score.

In terms of adjusting the mode of provision, the customer evaluation server 30 may give customers with higher scores more favorable treatment in providing specific goods, etc. related to the target concept. This motivates customers to increase their scores in order to be treated more favorably in providing specific goods, etc., thereby stimulating fan activity related to the target concept. Furthermore, the customer evaluation server 30 may give customers with higher scores a higher chance of winning a lottery to determine whether or not they will be provided with specific goods, etc. related to the target concept. This motivates customers to increase their scores in order to increase their chances of receiving specific goods, etc. related to the target concept, thereby stimulating fan activity related to the target concept.

Regarding adjustment of the provision mode, the customer evaluation server 30 may grant customers whose scores are equal to or greater than a threshold the right to receive specific goods, etc. related to the target concept. This motivates customers to increase their scores in order to receive specific goods, etc. related to the target concept, thereby stimulating fan activity related to the target concept. The customer evaluation server 30 may also calculate the scores of multiple customers who have requested specific goods, etc. related to the target concept, and grant the right to receive the goods, etc. to customers who rank at or above a predetermined rank when sorted in descending order of score among the multiple customers. This motivates customers to increase their scores in order to receive specific goods, etc. related to the target concept, thereby stimulating fan activity related to the target concept.

The customer evaluation server 30 may edit the evaluation rules for a target concept in response to instructions from an evaluator regarding the target concept. This allows the evaluator to flexibly change the definition of a fan of the target concept. As an example, in response to changes in the customer target demographic for the target concept, the old evaluation rules can be reviewed and the requirements for fans of the target concept can be flexibly redefined. The customer evaluation server 30 may also present the evaluator with information on at least one of the conditions or content for granting multiple NFTs related to the target concept. This makes it easier for the evaluator to determine the evaluation value to assign to each NFT.

The customer evaluation server 30 may detect behavior that meets the conditions for granting NFTs related to the target concept, and grant NFTs corresponding to the conditions to customers for whom the behavior was detected. This allows for capturing customer behavior that triggers the issuance of NFTs and automatically granting NFTs that contribute to improving scores. The customer evaluation server 30 may also detect, as behavior that meets the conditions, the purchase, rental, or use of specific goods, services, or content related to the target concept, or the dissemination of specific information related to the target concept. This allows for capturing customer fan activities that trigger the issuance of NFTs and automatically granting NFTs that contribute to improving scores. Furthermore, the customer evaluation server 30 may set at least one of the conditions or content for granting NFTs related to the target concept in response to instructions from the evaluator of the target concept. This allows the evaluator to flexibly determine the conditions for acquiring NFTs that contribute to improving scores, or the content of the NFTs.

(6) Other Modifications The storage device 11 may be connected to the customer terminal 10 via the network NW. The display 21 may be built into the customer terminal 10. The storage device 31 may be connected to the customer evaluation server 30 via the network NW.

Each step of the above information processing can be performed by either the customer terminal 10 or the customer evaluation server 30.

The above explanation shows an example of building a separate evaluation table for each target concept. However, the correspondence between target concepts and evaluation tables does not have to be 1:1, and can be 1:many. In other words, in order to evaluate customer fans of a certain target concept from different perspectives, multiple evaluation tables can be built for that target concept.

The above explanation shows an example of defining evaluation rules for each token ID. However, if there are multiple NFTs with the same grant conditions and content, the evaluation rules for these NFTs may be aggregated. In this case, instead of the token ID, a type ID for identifying differences in the NFT type (i.e., grant conditions and content) may be stored in the evaluation rule database. The customer evaluation server 30 converts the token ID into a type ID by referencing a conversion table. The conversion table associates multiple token IDs with a type ID. The conversion table may be constructed by manual input, or by referencing the database of the issuer of each NFT using an API (Application Programming Interface) or crawling. Alternatively, the type ID may be defined to correspond to additional data stored in the token (such as an industry-standard type ID).

The evaluation rule table can store various information not shown in FIG. 7. As a first example, the evaluation rule table may store issuer information related to the issuer, or an issuer ID for identifying the issuer. The evaluator can assign an evaluation value to each NFT taking into account the issuer of the NFT. As a second example, the evaluation rule table may store route information related to the acquisition route of the NFT. For example, the route information indicates whether the NFT was acquired through primary distribution or secondary distribution. The evaluator can assign an evaluation value to each NFT taking into account the acquisition route of the NFT.

The above explanation shows an example in which there is a 1:1 relationship between a token and the evaluation value for holding that token. However, the evaluation rules may also define an evaluation value for holding a token set consisting of multiple tokens. This makes it possible to give a special evaluation to customers who hold all of the tokens belonging to a token set.

The above explanation shows an example of calculating a multi-value score (i.e., three or more values). However, it is also possible to calculate a binary score. As a first example, the customer evaluation server 30 may calculate a score of "high" for a customer who possesses any of the tokens registered in the evaluation rule, and a score of "low" for a customer who does not possess any of the tokens registered in the evaluation rule. As a second example, the customer evaluation server 30 may calculate a score of "high" for a customer who possesses a token set registered in the evaluation rule, and a score of "low" for a customer who does not possess that token set. The customer evaluation server 30 may treat customers with "high" scores more favorably than customers with "low" scores when providing specific products, etc. related to the target concept.

In the above description, an example was shown in which the customer evaluation server 30 granted an NFT to a customer through the NFT granting process of FIG. 8 and evaluated the customer based on the NFT's ownership status. However, the customer evaluation server 30 may also evaluate a customer based on the ownership status of NFTs granted by a different device. As an example, the evaluation table may store evaluation rules that apply to NFTs granted by a device other than the customer evaluation server 30. For example, an authentication authority may issue an NFT that certifies that the wallet owner has been authenticated (e.g., eKYC (electronic KYC (Know Your Customer))), and the evaluation rules that apply to such NFTs may be stored in the evaluation table. In this case, the customer evaluation server 30 may refer to information about trusted authentication authorities and change the way the NFT is handled depending on whether the issuer of the NFT is a trusted authentication authority or not. For example, the customer evaluation server 30 may not apply evaluation rules to NFTs issued by authentication authorities other than trusted authentication authorities, or may apply evaluation rules that assign a lower evaluation value than those issued by trusted authentication authorities. Furthermore, at least one of the granting conditions or content of an NFT to which an evaluation rule applies may be set by someone other than the evaluator. For example, evaluation rules for evaluations by fans of an artist may be applied to an NFT granted in accordance with granting conditions set by an evaluator for a brand favored by that artist. Alternatively, at least one of the granting conditions or content of an NFT may be predetermined, with only the other being configurable by the evaluator.

The above explanation shows an example of evaluating a customer based on their NFT holdings. However, in addition to their NFT holdings, customers may also be evaluated based on their holdings of specific FTs. For example, the customer evaluation server 30 may calculate a customer's score based on whether or not they hold FTs related to the target concept (for example, crypto assets whose main purpose is to purchase goods, etc. related to the target concept), or the amount of such FTs they hold.

In the above explanation, an example was shown in which the customer terminal 10 and the customer evaluation server 30 presented the customer with their own score. However, instead of or in addition to the score, the customer terminal 10 and the customer evaluation server 30 may present the customer with their grade as a fan of the target concept (including the provision of an NFT to prove the grade). Specifically, the customer evaluation server 30 determines the customer's grade based on an absolute or relative evaluation of the score. As a first example, the customer evaluation server 30 determines that a customer whose score falls within a predetermined numerical range has a grade associated with that numerical range (absolute evaluation). As a second example, when multiple customers are sorted in descending order by score, the customer evaluation server 30 determines that a customer who falls within a predetermined ranking range has a grade associated with that ranking range (relative evaluation).

In the above explanation, an example was shown in which the customer terminal 10 and the customer evaluation server 30 presented the customer with their own score. However, instead of or in addition to the score, the customer terminal 10 and the customer evaluation server 30 may also present the customer with ranking information on the scores across multiple customers.

The above explanation shows an example in which the manner in which goods, etc. are provided to a customer is adjusted according to the customer's score. However, the customer evaluation server 30 may adjust the manner in which goods, etc. are provided according to whether the customer holds a specific NFT, instead of the score. As an example, the customer evaluation server 30 may not grant customers who do not hold a specific NFT the right to receive goods, etc. specified based on a provision request, and may grant the right to receive such goods, etc. only to customers who hold a specific NFT.

In the above description, an example has been shown in which the customer terminal 10 and the customer evaluation server 30 execute the provision mode adjustment process of Fig. 11. However, this process can be executed in various modes.
As a first example, the customer evaluation server 30 calculates a score (or determines a grade) for the customer in step S430 and transmits the score to an external device. The external device adjusts the provision of the product or the like based on the score (S432). The external device may be, for example, a server in a ticket system, an EC system, or a content viewing system.
As a second example, the customer terminal 10 transmits a provision request to an external device in step S410. The external device transmits an evaluation request for the customer's score to the customer evaluation server 30. In response to the evaluation request, the customer evaluation server 30 identifies the NFTs held (S430) and calculates the score (S431), thereby calculating the customer's score (or determining the grade) and transmitting the score to the external device. The external device adjusts the provision manner of the goods, etc. (S432).

In the above description, an example was given in which a customer's score was calculated in response to a request from the customer. However, the customer evaluation server 30 may also calculate the customer's score in response to a request from a party other than the customer. For example, the customer evaluation server 30 may calculate a score for each customer (here, the customer is, for example, a member of a customer evaluation service provided by the customer evaluation server 30) in response to a request from a party (hereinafter referred to as a "provider") who intends to provide goods, services, or content related to the target concept or other concepts. The customer evaluation server 30 then extracts customers whose scores satisfy certain conditions. The customer evaluation server 30 may present the extracted customer information to the provider or perform sales promotion processing (for example, automatically sending emails or recommending goods and the like that the provider can provide) for the customer on behalf of the provider.
The specific conditions may include, for example, at least one of the following:
- The score as a fan of a specific concept is within a predetermined numerical range; - The distribution of scores as a fan of multiple target concepts is similar to a specific distribution (e.g., the distribution of a specific other person); - As a result of clustering each customer based on the distribution of scores as a fan of multiple target concepts, the customer belongs to a specific cluster. As an example, the customer evaluation server 30 determines the distribution of scores for one or more concepts other than the specific concept (e.g., concepts related to the specific concept) of customers who have relatively high scores as fans of the specific concept as a reference distribution. Then, the customer evaluation server 30 extracts customers who have a score distribution similar to the reference distribution but have relatively low scores as fans of the specific concept. The extracted customers may not currently be fans of a specific concept, but may be potential fans who have similar preferences to fans of the concept. Therefore, by conducting marketing activities (including promotional activities (e.g., recommendations of products related to the specific concept, granting coupons, granting special discount rights, displaying advertisements, sending information, providing samples, free invitations, etc.)) related to the specific concept to the extracted customers, it is possible to efficiently acquire or cultivate new fans of the specific concept.

The above explanation shows an example in which an evaluator defines evaluation rules. The aforementioned provider does not have to be the same as the evaluator. In other words, the provider may request the customer evaluation server 30 to evaluate a customer based on evaluation rules defined by another person (evaluator). Furthermore, when an evaluator edits evaluation rules, the customer evaluation server 30 may provide evaluation rules defined by other evaluators to the evaluator terminal 70 so that the evaluator can reuse evaluation rules created by other people (i.e., other evaluators).

Alternatively, the customer evaluation server 30 may perform various information processes other than evaluating the fan score of each customer in response to a request from a provider.
Specifically, in response to a request from a provider, the customer evaluation server 30 identifies the customer's NFT holdings and collects the issuer ID (i.e., information identifying the issuer) of each NFT. Then, for customers who hold NFTs issued by an issuer ID designated by the provider (e.g., an issuer ID of the provider itself or a person related to the provider, hereinafter referred to as a "provider ID"), the customer evaluation server 30 analyzes the holdings of NFTs issued by an issuer ID (target issuer ID) different from the provider ID and extracts the corresponding target issuer ID. The issuer corresponding to the target issuer ID may be a provider of goods or other items related to a concept corresponding to the goods or other items provided by the provider, or a concept targeting customers with the same preferences as the goods or other items (i.e., in a complementary or alternative relationship), and thus may be useful information for the provider.
As a first example, the customer evaluation server 30 may notify the provider of information about the target issuer, allowing the provider to obtain information about potential partners or competitors and use it as information for making decisions.
As a second example, the customer evaluation server 30 may notify the provider of information about customers who hold NFTs issued by the target issuer. This allows the provider to obtain information about its potential customers (potential new fans) or existing customers who are at risk of being lost to the target issuer (potential defecting fans) and use the information in its marketing activities.

As another example, the customer evaluation server 30 may analyze the following various pieces of information in response to a request from a provider, and extract information that is useful to the provider. The information to be analyzed includes at least one of the following:
- History of how a certain NFT has been traded between customers (i.e., C2C) - Transaction prices of NFTs between customers - Real-time data on NFTs traded between customers - Data on how many NFTs are acquired from which issuers (sales analysis/competitive analysis)
As a first example, the customer evaluation server 30 may notify the provider of information about customers who owned NFTs issued by an issuer corresponding to the provider ID but transferred more than a threshold number of those NFTs to others, or who transferred those NFTs to others within a recent predetermined period. Such customers may have been fans of a concept corresponding to an item or the like provided by the provider but have since lapsed or are beginning to lapse. By notifying the provider of such customer information, the provider can take measures (e.g., re-approach) to re-establish or prevent churn.
As a second example, the customer evaluation server 30 may notify the provider of information about a customer who previously owned an NFT issued by an issuer corresponding to the provider ID but who acquired more than a threshold number of such NFTs within a recent predetermined period. Such a customer may be a new fan of a concept corresponding to a product or the like offered by the provider. By notifying the provider of such customer information, the provider can take measures to develop the customer into a more core fan.
As a third example, the customer evaluation server 30 may notify the provider of information about a customer who owns a collectible NFT among NFTs issued by an issuer corresponding to the provider ID. A collectible NFT is an NFT that belongs to a group (collection list) consisting of a finite number of NFTs. Such a customer may also be interested in other collectible NFTs. By notifying the provider of such customer information, the provider can ensure that the customer is approached when a project (e.g., a concert tour) is implemented to issue a new collectible NFT, thereby encouraging the customer to participate in the project.
As a fourth example, the customer evaluation server 30 may notify the provider of information about a customer who owns a collectible NFT among NFTs issued by an issuer corresponding to the provider ID but has missing NFTs, as well as information about the missing NFTs. By notifying the provider of such customer information and information about the missing NFTs, the provider can promote sales of the products and other items it provides by informing customers of the missing NFTs and how to obtain them.
As a fifth example, the customer evaluation server 30 may notify the provider of analysis results regarding the secondary distribution of NFTs issued by an issuer corresponding to the provider ID. For example, the customer evaluation server 30 may automatically obtain information on the secondary distribution prices of NFTs issued by the provider ID and notify the provider of alerts according to certain rules. By notifying customers who own NFTs issued by the provider of information regarding price increases of the NFTs issued by the provider, the provider can increase customers' willingness to acquire NFTs issued by the provider in the future.
As a sixth example, the customer evaluation server 30 may notify the provider of the results of a CRM (Customer Relationship Management) analysis or other analysis regarding the primary distribution (i.e., new acquisitions by customers) and secondary distribution of NFTs issued by an issuer corresponding to the provider ID. For example, the customer evaluation server 30 performs various analyses on each NFT issued by the provider ID, covering the primary distribution, secondary distribution, or total distribution. Specifically, the customer evaluation server 30 may analyze transaction frequency, transaction amount, or number of transactions. The customer evaluation server 30 may also perform a Pareto analysis or an ABC analysis. The provider can use the results of such analysis as a basis for planning future NFTs to be issued.

The customer evaluation server 30 may refer to a customer's behavioral history or transaction history to estimate the trading characteristics or attributes of that customer. As a first example, the customer evaluation server 30 estimates the trading characteristics of a customer with a particular attribute (e.g., a housewife) (e.g., when (e.g., on what day or during what time of day) they actively trade NFTs). As a second example, the customer evaluation server 30 estimates the attributes of a customer with a distinctive trading history (e.g., a customer who trades frequently is a speculative day trader). As a third example, the customer evaluation server 30 estimates the attributes of a customer with a distinctive behavioral history (e.g., a customer who frequently attends fan events is a true fan). The customer evaluation server 30 may notify the provider of the estimated information or use it to calculate the customer's score.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited to the above embodiments. Furthermore, various improvements and modifications to the above embodiments are possible without departing from the spirit of the present invention. Furthermore, the above embodiments and modifications can be combined.

1: Information processing system 10: Customer terminal 11: Storage device 12: Processor 13: Input/output interface 14: Communication interface 21: Display 30: Customer evaluation server 31: Storage device 32: Processor 33: Input/output interface 34: Communication interface 50: Distributed ledger system 55: Node computer 70: Evaluator terminal 71: Storage device 72: Processor 73: Input/output interface 74: Communication interface 81: Display

Claims (13)

At least one computer
A means for storing information regarding a correspondence relationship between an NFT (Non-Fungible Token) and an evaluation value assigned to the NFT for the target concept, the correspondence relationship being individually defined for each of a plurality of target concepts;
A means to identify NFTs held by customers by querying the distributed ledger system;
A means for calculating a score as a fan of each target concept based on the NFT held by the customer and the evaluation value included in the correspondence defined for the target concept to be calculated;
A program that functions as a causing the computer to function as a means for adjusting a manner in which at least one specific product, service, or content related to each of the target concepts is provided to the customer in accordance with the score calculated for each of the target concepts ;
The program according to claim 1. The adjusting means gives a customer with a higher score calculated for each of the target concepts a more favorable treatment in providing specific goods, services, or content related to each of the target concepts.
The program according to claim 2. the adjusting means adjusts the probability of winning for a customer in a lottery to determine whether or not to provide a specific product, service, or content related to each of the target concepts, for the customer having a higher score calculated for each of the target concepts;
The program according to claim 2. The adjusting means grants a right to receive a specific product, service, or content related to each of the target concepts to a customer whose score calculated for each of the target concepts is equal to or greater than a threshold.
The program according to claim 2. The calculation means calculates scores of a plurality of customers who have requested the provision of a specific product, service, or content related to the target concept as fans of the target concept;
the adjusting means grants the right to receive a specific product, service, or content related to each of the target concepts to customers who rank at or above a predetermined rank when sorted in descending order of the scores calculated for each of the target concepts among the plurality of customers;
The program according to claim 2. causing the computer to function as a means for editing evaluation rules for the target concept in response to an instruction from an evaluator for the target concept;
The program according to claim 1. The computer is caused to function as a means for presenting to an evaluator of the target concept at least one piece of information regarding the granting conditions or contents of a plurality of NFTs related to the target concept;
The program according to claim 7. The computer
A means for detecting an action that matches the condition for assigning an NFT related to the target concept;
and further functioning as a means for granting NFTs corresponding to the granting conditions to customers whose behavior matching the granting conditions is detected.
The program according to claim 1. The means for detecting the behavior detects, as the behavior that matches the grant condition, purchase, borrowing, use, possession, or lending of a specific product, service, or content related to the target concept, or transmission of specific information related to the target concept.
The program according to claim 9. causing the computer to function as a means for setting at least one of the conditions or contents of an NFT related to the target concept in response to an instruction from an evaluator related to the target concept;
The program according to claim 9. A means for storing information regarding a correspondence relationship between an NFT (Non-Fungible Token) and an evaluation value assigned to the NFT for the target concept, the correspondence relationship being individually defined for each of a plurality of target concepts;
A means to identify NFTs held by customers by querying the distributed ledger system;
A means for calculating a score as a fan of each target concept based on the NFT held by the customer and the evaluation value included in the correspondence defined for the target concept to be calculated;
An information processing device comprising: At least one computer
A step of storing information regarding a correspondence relationship between a non-fungible token (NFT) and an evaluation value assigned to the NFT for the target concept, the correspondence relationship being individually defined for each of a plurality of target concepts;
Identifying the NFTs held by the customer by querying the distributed ledger system;
A step of calculating a score as a fan of each target concept based on the NFT held by the customer and the evaluation value included in the correspondence defined for the target concept to be calculated;
How to do it.