WO2023195508A1

WO2023195508A1 - Information processing device, method, and program

Info

Publication number: WO2023195508A1
Application number: PCT/JP2023/014172
Authority: WO
Inventors: 圭史伊藤
Original assignee: ｐｌａｙｇｒｏｕｎｄ株式会社
Priority date: 2022-04-08
Filing date: 2023-04-06
Publication date: 2023-10-12
Also published as: JP2023154862A

Abstract

A program according to one aspect of the present disclosure causes a computer to function as: a means for identifying a non-fungible token (NFT) held by a customer by querying a distributed ledger system; and a means for calculating a score for the customer as a fan of a concept in question on the basis of the NFT held by the customer and evaluation rules defining evaluation values assigned to each of a plurality of NFTs related to the concept in question.

Description

Information processing device, method, and program

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

For example, in various businesses such as entertainment, one of the major challenges is to develop existing customers into more engaged customers (in other words, to turn them into fans).

Patent Document 1 describes specific participants extracted based on the behavior history of event participants (for example, participants who participate in many virtual events, participants who purchased a specific product, or participants who have paid more than a certain amount). Discloses a technique for providing a special performance to participants (who have performed the event).

JP2018-094326A

However, with the technology described in Patent Document 1, behavioral indicators in a predetermined period (for example, the number of events attended during the entire period or a certain period (within the last one week), the number of purchased items, the total billed amount, the support parameters, or the Participants are evaluated based on the number of points (scores) in games related to the event. For example, event participation and billing when there are few fans of a certain acting character will be treated the same as event participation and billing after the number of fans of the acting character increases. As described above, with the technique described in Patent Document 1, it is difficult to evaluate participants for the same type of behavior by considering the qualitative aspects of the behavior. In addition, the technology described in Patent Document 1 allows participants to record their behavior history with respect to parties other than the virtual event organizer, such as purchasing related products from different businesses or specific products through secondary distribution. It was difficult to conduct an evaluation of the participants, taking into account the purchase of products, etc.

One of the purposes of the present disclosure is to provide a technology that evaluates a customer as a fan by considering a variety of information. Another objective of the present disclosure is to provide a technique for analyzing various customer information and extracting useful information.

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

FIG. 1 is a block diagram showing the configuration of an information processing system according to the present embodiment. It is a block diagram showing the composition of the customer terminal of this embodiment. FIG. 2 is a block diagram showing the configuration of a server according to the present embodiment. FIG. 1 is a diagram showing the configuration of a distributed ledger system according to the present embodiment. It is a block diagram showing the composition of the evaluator terminal of this embodiment. FIG. 2 is an explanatory diagram of one aspect of the present embodiment. It is a figure showing the data structure of the evaluation table of this embodiment. It is a flowchart of NFT grant processing of this embodiment. It is a flowchart of evaluation rule editing processing of this embodiment. It is a flowchart of score confirmation processing of this embodiment. It is a flowchart of provision mode adjustment processing of this embodiment.

Hereinafter, one embodiment of the present invention will be described in detail based on the drawings. In addition, in the drawings for explaining the embodiments, the same components are generally designated by the same reference numerals, and repeated explanations thereof will be omitted.

(1) Configuration of information processing system The configuration of the information processing system will be explained. FIG. 1 is a block diagram showing the configuration of an 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 (eg, the Internet) NW.

The customer terminal 10 is an example of an information processing device that transmits a request to the customer evaluation server 30. The customer terminal 10 is, for example, a smartphone, a tablet terminal, or a 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 "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 according to the request transmitted from the customer terminal 10. The customer evaluation server 30 provides the evaluator terminal 70 with a response according to the request transmitted 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, an 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 transmits a request to the customer evaluation server 30. The evaluator terminal 70 is, for example, a smartphone, a tablet terminal, or a personal computer. The user of the evaluator terminal 70 is an evaluator regarding the target concept. An evaluator regarding a target concept is a person (including an organization) who defines rules for evaluating customers as fans of the target concept. As an example, the evaluator may be a person who owns rights to the subject concept (e.g., copyright, trademark rights, publicity rights, or merchandising rights based on contracts or business practices) or who provides goods, services, or content relating to the subject concept. or a person designated by these persons (for example, a fan community).

(1-1) Configuration of customer terminal The configuration of the customer terminal will be explained. 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. Customer terminal 10 is connected to 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 (for example, flash memory or hard disk).

The programs include, for example, the following programs.
・OS (Operating System) program ・Application program that executes information processing (e.g. web browser)

The data includes, for example, the following data.
・Databases referenced in information processing ・Data obtained by executing information processing (that is, execution results of information processing)

The processor 12 is a computer that implements the functions of the customer terminal 10 by activating a program stored in the storage device 11. 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 acquires information (for example, user instructions) from an input device connected to the customer terminal 10 and outputs information (for example, an image) to an output device connected to the customer terminal 10. It is composed of
The input device is, for example, a keyboard, pointing device, 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 (eg, the customer evaluation server 30 or the distributed ledger system 50).

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

(1-2) Server configuration The server configuration will be explained. FIG. 3 is a block diagram showing the configuration of the server of 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 (eg, flash memory or hard disk).

The programs include, for example, the following programs.
・OS program ・Application program that executes information processing

The data includes, for example, the following data.
・Databases referenced in information processing ・Execution results of information processing

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

The input/output interface 33 acquires information (user instructions) from an input device connected to the customer evaluation server 30 and outputs information (for example, an image) to an output device connected to the customer evaluation server 30. configured.
The input device is, for example, a keyboard, pointing device, 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 (eg, the customer terminal 10, the distributed ledger system 50, or the evaluator terminal 70).

(1-3) Configuration of distributed ledger system The configuration of the distributed ledger system will be explained. FIG. 4 is a diagram showing the configuration of the distributed ledger system of this embodiment.

As shown in FIG. 4, the distributed ledger system 50 includes a plurality of 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 leased line, a VPN (Virtual Private Network), or a combination thereof. The node computer 55 is connected to the network, for example, by wire or wirelessly. Node computers 55 communicate with each other in a peer-to-peer manner.

The node computer 55 manages a distributed ledger using, for example, blockchain technology.
Specifically, any node computer 55 obtains data regarding the token transaction to be recorded. The node computer 55 creates a block containing the obtained data and adds it to the blockchain. The node computer 55 transmits information about the added block to other node computers 55. The other node computers 55 verify the correctness of the received block, and if the verification is successful, add the block to the blockchain. The node computer 55 determines the blockchain according to the number of blocks to be connected (number of approvals), for example. As a result, the same distributed ledger is stored across the plurality of node computers 55 configuring the distributed ledger system 50. Note that the data to be saved is appropriately encrypted.

The configuration of the distributed ledger system 50 is not limited to that shown in FIG. 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. Further, the number of node computers 55 configuring the distributed ledger system 50 may vary over time.

The hardware configuration of the node computer 55 may be the same as or similar to the customer terminal 10 or the customer evaluation server 30, so a detailed description will be omitted. By way of example, 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 evaluator terminal The configuration of the evaluator terminal will be explained. 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. Evaluator terminal 70 is connected to 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 (eg, flash memory or hard disk).

The programs include, for example, the following programs.
・OS program ・Application program that executes information processing (e.g. web browser)

The processor 72 is a computer that implements the functions of the evaluator terminal 70 by activating 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 acquires information (for example, user instructions) from an input device connected to the evaluator terminal 70 and outputs information (for example, an image) to an output device connected to the evaluator terminal 70. configured to do so.
The input device is, for example, a keyboard, pointing device, 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 (eg, the customer evaluation server 30 or the distributed ledger system 50).

The display 81 is configured to display images (still images or moving images). 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. FIG. 6 is an explanatory diagram of one aspect of this embodiment.

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

The customer evaluation server 30 refers to the evaluation rule R14 associated with the target concept T13. The evaluation rule R14 is defined such that evaluation values assigned to each of the plurality of NFTs regarding the target concept T13 can be specified. The NFT related to the target concept T13 is typically an NFT that can be acquired by performing fan activities for the target concept T13, but is not limited thereto. The customer evaluation server 30 calculates the score of the customer C11 as a fan of the target concept T13 based on the NFT held by the customer C11 and the evaluation rule R14.

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

In this way, the customer evaluation server 30 evaluates the NFTs held by the customer C11 individually based on the evaluation rule R14 associated with the target concept T13, thereby determining the score of the customer C11 as a fan of the target concept T13. calculate. Thereby, it is possible to calculate a customer's score by distinguishing various NFTs that can be acquired through fan activities, for example. As an example, even fan activities of the same type may be classified depending on the context of the activity (for example, the time, place, or scene of the activity, or a commemorative event of the target concept T13 related to the activity). By doing so, you can give different evaluations to the NFTs that you can obtain. In addition, even if multiple NFTs related to the same target concept T13 are issued by different publishers (especially publishers other than the evaluator), the target concept T13 will be evaluated based on the evaluation value assigned to each NFT. A common score for fans of concept T13 can be calculated. Furthermore, even if a customer acquires (transfers) NFTs through secondary distribution (for example, transactions between customers), but the issuer is not aware of this fact, the company will take into account the ownership of the NFTs. Customers can be evaluated. In other words, according to the customer evaluation server 30, it is possible to evaluate the customer C11 as a fan of the target concept T13 by considering various information.

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

(3-1) Evaluation Table The evaluation table of this embodiment will be explained. FIG. 7 is a diagram showing the data structure of the evaluation table of this embodiment.

The evaluation table is a database in which evaluation rules are stored. The evaluation rule is information that defines the evaluation value that a customer obtains by holding the corresponding NFT. The evaluation value corresponds to the material for calculating the score as a fan of the target concept.

An evaluation table is constructed individually for each target concept. Therefore, a token whose evaluation value is defined in the evaluation table for the first target concept (hereinafter referred to as the "first evaluation table") will be defined in the evaluation table for the second target concept (hereinafter referred to as the "second evaluation table"). There may be no overlap with the token for which the evaluation value is defined, or there may be some or all overlap. Since the evaluation value in each database can be defined individually, the evaluation value defined in the first evaluation table for a certain token does not necessarily match the evaluation value defined in the second evaluation table.

As shown in FIG. 7, the evaluation table includes a "rule ID" field, a "token ID" field, a "granting condition" field, a "content" field, and an "evaluation value" field. Each field is associated with each other.

A rule ID is stored in the "Rule ID" field. Rule ID is information that identifies an evaluation rule.

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

Granting condition information is stored in the "granting condition" field. The granting condition information is information regarding conditions that must be met in order to be granted an NFT to which the target rule is applied (hereinafter referred to as "target NFT"). Although there is no particular restriction on the format of the grant condition information, the grant condition information may be written in natural language from the viewpoint of helping the evaluator understand the NFT grant conditions regarding the target concept.

The granting condition is typically defined as the customer taking a specific action (typically fan activity) regarding the target concept. Specific actions may include, for example, visiting a specific location (e.g., an event venue or store), purchasing, borrowing (including renting), using, possessing, or This may include lending (including borrowing), sending specific information on SNS (Social networking service), viewing specific content, applying for or participating in a specific campaign, or owning one or more specific NFTs. Alternatively, the specific action prompts a new customer (for example, a customer who does not own any NFT regarding the target concept or whose score is less than a predetermined value) to take at least one of the actions exemplified in the preamble, It may also be that the customer has taken the prompted action. Furthermore, the granting conditions may include additional conditions for specific actions. The incidental conditions relate to, for example, time, date and time, location, amount, number of times, frequency, amount of money, or number of people.

Content information is stored in the "content" field. The content information is information regarding the content of the target NFT. Although there is no particular restriction on the format of the content information, the content information may be expressed in natural language, images, or audio from the viewpoint of helping the evaluator understand the content of the NFT. Here, the content of the target NFT is not limited to information recorded in the target NFT, and may include information that can be referenced from the information. As an example, when a URL (Uniform Resource Locator) is recorded in the target NFT, the contents of the target NFT may include information (eg, content) that can be referenced by the URL.

Evaluation value information is stored in the "evaluation value" field. The evaluation value information is information regarding the evaluation value that the customer obtains by owning the target NFT. The evaluation value information may be configured to be editable according to instructions from the evaluator.

(4) Information processing Information processing of this embodiment will be explained.

(4-1) NFT granting process The NFT granting process of this embodiment will be explained. FIG. 8 is a flowchart of the NFT granting process of this embodiment.

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

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

After step S170, the customer evaluation server 30 executes setting of grant conditions and contents (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 specifies the NFT granting conditions and contents that the evaluator intends to set. The customer evaluation server 30 stores the specified grant conditions and contents in the storage device 31. As an example, the customer evaluation server 30 may store information on the specified granting conditions and contents in a database for managing NFTs that the customer evaluation server 30 can grant.

After step S130, the customer evaluation server 30 detects a behavior that matches the granting conditions (S131).
Specifically, the customer evaluation server 30 detects, based on information acquired from an external device, that the customer has taken an action that matches any of the grant conditions 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, a content viewing system, or the like.

As an example, the customer evaluation server 30 acquires, for example, from the customer terminal 10 a serial code that is issued to the customer as proof that the customer has taken the action that matches the granting conditions, thereby confirming that the customer has taken the action. May be detected. Alternatively, the customer evaluation server 30 may acquire the customer's behavior history from an external system and analyze the behavior history to determine whether the customer has taken a behavior that matches the grant condition.

After step S131, the customer evaluation server 30 executes NFT granting (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 NFTs to the customer. Here, before granting the NFT to the customer, the customer evaluation server 30 may inquire of the customer for information necessary for granting (for example, the customer's wallet information).
Upon completion of step S132, the customer evaluation server 30 ends the NFT granting process of FIG. 8.

(4-2) Evaluation rule editing processing The evaluation rule editing processing of this embodiment will be explained. FIG. 9 is a flowchart of the evaluation rule editing process of this embodiment.

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

As shown in FIG. 9, the evaluator terminal 70 issues an evaluation rule viewing request (S270).
Specifically, the evaluator operates the evaluator terminal 70 to instruct viewing of evaluation rules for the target concept regarding the evaluator. The evaluator terminal 70 generates an evaluation rule viewing request in response to instructions from the evaluator. The viewing request includes information that allows the evaluator to specify the evaluation rule that the evaluator wishes to view. The evaluation rules that the evaluator wishes to view may be all or part of the evaluation rules regarding the target concept. The evaluator terminal 70 transmits a viewing request to the customer evaluation server 30.

After step S270, the customer evaluation server 30 acquires evaluation rules (S230).
Specifically, customer evaluation server 30 acquires the viewing request transmitted in step S270. The customer evaluation server 30 specifies the evaluation rule that the evaluator wishes to view based on the viewing request. The customer evaluation server 30 acquires the specified 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 presents evaluation rules (S271).
Specifically, the evaluator terminal 70 acquires the evaluation rule transmitted in step S231. The evaluator terminal 70 presents evaluation rules to the evaluator by displaying an image on the display 81, for example.

After step S231, the evaluator terminal 70 issues an evaluation rule editing request (S272).
Specifically, by operating the evaluator terminal 70, the evaluator instructs editing of the evaluation rule for the target concept regarding the evaluator. Here, editing the evaluation rule may be either changing or deleting a set evaluation rule, or adding a new evaluation rule. When the evaluator changes or deletes a set evaluation rule, the evaluator may specify the target evaluation rule using the object displayed on the display 81 in step S271. The evaluator terminal 70 generates an evaluation rule editing request in response to instructions from the evaluator. The editing request includes information that allows the evaluator to specify the desired editing content. 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, provision condition information, content information, or evaluation value information of the new evaluation rule

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

Note that when the evaluator adds a new evaluation rule, the evaluation rule viewing request (S270), evaluation rule acquisition (S230), evaluation rule presentation (S231), and evaluation rule presentation (S271) are Optional.

(4-3) Score confirmation processing The score confirmation processing of this embodiment will be explained. FIG. 10 is a flowchart of the score confirmation process of this embodiment.

The score confirmation process in FIG. 10 may be started, 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, by operating the customer terminal 10, the customer instructs the evaluation of the customer's score as a fan regarding the target concept. The customer terminal 10 generates a score evaluation request in response to instructions from the customer. The evaluation request includes information that can identify the NFT held by the customer (for example, a list of token IDs of the NFT or the customer's wallet information), and information that can identify the evaluation table used to calculate the score (for example, the target concept). information). The customer terminal 10 transmits an evaluation request to the customer evaluation server 30.

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

Note that the evaluation request is not limited to one piece of wallet information and can include multiple pieces of wallet information. When the evaluation request includes a plurality of pieces of wallet information, the customer evaluation server 30 may acquire the NFT token ID linked to any of the plurality of wallet information from the distributed ledger system 50.

If the customer holds multiple wallets, the customer evaluation server 30 may acquire the NFT token ID linked to the customer's multiple wallet information from the distributed ledger system 50. As a first example, a plurality of pieces of wallet information are registered in advance in a database in association with a customer ID that identifies a customer, and the customer evaluation server 30 selects a wallet corresponding to the wallet information associated with the customer ID in the database. Treat it as a customer's wallet. As a second example, at least one piece of wallet information is registered in advance in a database in association with a customer ID that identifies a customer, and the customer evaluation server 30 stores a wallet corresponding to the wallet information associated with the customer ID in the database. is treated as the customer's wallet. Further, the customer evaluation server 30 estimates that another wallet that has conducted a transaction with the customer's wallet that satisfies at least one of the following conditions is the customer's wallet (unregistered wallet).
- Other wallets are trading crypto assets or other tokens with the customer's wallet, and the transaction frequency exceeds a threshold - Other wallets are trading with the customer's wallet for no consideration Other wallets are associated with information that matches or is similar to the customer's wallet (e.g., name, email address, or linked personal identification NFT)

Furthermore, the evaluation request may include information for verifying that the customer is not misrepresenting the wallet information (that is, 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 providing a wallet that corresponds to the wallet information specified by the customer. The external system authenticates the customer's identity (for example, confirms that they have entered the correct wallet ID and password combination) and provides access to prove that the customer is the owner of the wallet. Issue a token.

Additionally, NFTs may be traded on a system that exists outside the distributed ledger system 50 (for example, sometimes referred to as a private chain or second layer). In this case, the evaluation request can include information that can identify the system in which the NFT held by the customer is actually traded, and wallet information of the customer in the system.

After step S330, the customer evaluation server 30 executes score calculation (S331).
Specifically, the customer evaluation server 30 specifies the evaluation table (FIG. 7) used to calculate 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 specified in step S330.

As a first example, the customer evaluation server 30 determines, for each NFT held by a customer, whether or not an evaluation rule applicable to the NFT is stored in the evaluation table. When the customer evaluation server 30 finds a corresponding evaluation rule, it refers to the evaluation value defined in the evaluation rule. The customer evaluation server 30 may calculate the score of the customer by summing the evaluation values for all evaluation rules applicable to the NFT held by the customer.

As a second example, the customer evaluation server 30 totals up to a predetermined number (for example, three in descending order of evaluation value) of all evaluation rules applicable to the NFT held by the customer in descending order of evaluation value. The score of the customer may be calculated by doing so.

Furthermore, the customer evaluation server 30 may correct the customer's score further based on the customer's attributes, as exemplified below.
・If a customer owns the first type of NFT (for example, an NFT given as a bonus for purchasing a song, or an NFT issued by a record company), but owns a second type of NFT (for example, as a bonus for purchasing a live ticket) If the customer does not own the NFT granted or the NFT issued by the ticket sales company, the customer evaluation server 30 may add points to the customer's score. As a result, it is possible to give preferential treatment to customers who are fans of the target concept but who may have a narrow range of fan activities, and encourage them to widen the range of their fan activities.
- If a customer has not acquired an NFT to which the evaluation rule is applied for a certain period of time, the customer evaluation server 30 may add points to the customer's score. As a result, it is possible to give preferential treatment to customers who are fans of the target concept but who are at risk of leaving the company, and to encourage them to return to being fans.
- The customer evaluation server 30 refers to the transaction history regarding NFTs to which the evaluation rules are applied, and determines the customer's score if the acquisition frequency, acquisition amount, or acquisition number of the NFT in the most recent predetermined period exceeds a threshold value. You may add points to This makes it possible to give preferential treatment to customers who may be new fans of the target concept, and encourage them to become more core fans.
- The customer evaluation server 30 refers to the transaction history regarding the NFT to which the evaluation rule is applied, and identifies the customer (hereinafter referred to as "target customer") with other customers (hereinafter referred to as "connection "1") who have traded the NFT. A customer with connection "1" and a customer (hereinafter referred to as "customer with connection "2") who has transacted the NFT with the customer with connection "1" are identified. The customer evaluation server 30 may refer to the score of the customer with connection "1" or the customer with connection "2" and add points to the target customer's score. As an example, the customer evaluation server 30 may determine the value to be added to the target customer based on the maximum value of the scores of the customer with connection "1" or the customer with connection "2". As a result, it is possible to give preferential treatment to target customers who have a connection with core fans of the target concept, and to encourage 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 proves 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 own score by displaying an image on the display 81, for example.
Upon completion of step S332, the customer terminal 10 ends the score confirmation process of FIG. 10.

(4-4) Provision mode adjustment process The provision mode adjustment process of this embodiment will be explained. FIG. 11 is a flowchart of the provision mode adjustment process of this embodiment.

The provision mode adjustment process shown in FIG. 11 can be started, 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, etc. (S410).
Specifically, by operating the customer terminal 10, the customer can purchase, rent, or use goods, services, or content related to the subject concept (hereinafter simply referred to as "goods, etc."), or reserve or apply for them. instruct. The customer terminal 10 generates a request for providing goods, etc. in response to instructions from the customer. The provision request includes information that allows identification of the NFT owned by the customer, information that allows identification of the evaluation table used to calculate the score, and information that allows identification of the goods, etc. that the customer desires to provide. The customer terminal 10 transmits the provision request to the customer evaluation server 30.

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

After step S430, the customer evaluation server 30 executes score calculation (S431).
Specifically, the customer evaluation server 30 specifies the evaluation table (FIG. 7) used to calculate 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 specified in step S430. The method of calculating the customer's score in step S431 may be the same as or similar to the method of calculating the customer's score in step S331.

After step S431, the customer evaluation server 30 adjusts the manner in which the goods and the like are provided (S432).
Specifically, the customer evaluation server 30 evaluates the goods, etc. specified based on the provision request (that is, the specific goods, services, or contents related to the target concept that the customer wishes to provide (which may include NFT)). The manner of provision to the customer is adjusted according to the score calculated in step S431.

As a first example, the customer evaluation server 30 may treat customers with higher scores more advantageously in providing goods and the like. Beneficial treatment may include at least one of the following:
・Increase the probability of winning for items whose availability is determined by lottery ・Products that are relatively high quality or popular among similar items (for example, seats with easy viewing at entertainment events) )・Increase the quantity or amount that can be purchased・Include benefits (which may include new NFTs)・Increase the order or time of provision・Reduce the price offered・Experience with the target concept (e.g. Granting the right to shake hands with a person (as a concept)

As a second example, the customer evaluation server 30 does not grant the right to receive the goods, etc. specified based on the provision request to customers whose score is less than the threshold value, but only to customers whose score is equal to or higher than the threshold value. The right to receive the goods, etc. may be granted.

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

With the end of step S432, the customer evaluation server 30 ends the provision mode adjustment process of FIG. 11.

(5) Summary As explained above, the customer evaluation server 30 identifies the NFT held by the customer by querying the distributed ledger system, and based on the NFT and evaluation rules related to the target concept, Calculate the customer's score as a fan of the concept. Thereby, it is possible to calculate a customer's score by distinguishing various NFTs that can be acquired through fan activities, for example. As an example, even for fan activities of the same type, different evaluations can be given to NFTs that can be obtained by performing the fan activities, depending on the context of the activities. In addition, even if multiple NFTs related to the same target concept are issued by different publishers (for example, a seller of an artist's music and an organizer of the artist's live performance), the Based on the evaluation values, a common score for fans of the target concept can be calculated. Further, even if a customer acquires NFT through secondary distribution but the issuer is not aware of this fact, the customer can be evaluated taking into account the possession of the NFT. That is, according to the customer evaluation server 30, it is possible to evaluate the customer as a fan of the target concept by considering various information.

The customer evaluation server 30 may adjust the manner in which specific items related to the target concept are provided to the customer according to the score. Thereby, a person who provides goods etc. related to the target concept can flexibly determine the manner in which the goods etc. are provided according to the customer's score.

Regarding the adjustment of the provision mode, the customer evaluation server 30 may treat a customer with a higher score more advantageously in providing a specific item, etc. related to the target concept. As a result, customers are motivated to increase their own scores in order to be treated advantageously in the provision of specific goods, etc., so that fan activities related to the target concept can be activated. Further, the customer evaluation server 30 may increase the customer's probability of winning a lottery for determining whether or not to provide a specific item related to the target concept, the higher the customer's score. As a result, customers are motivated to increase their own scores in order to receive offers of specific goods, etc. related to the target concept with a higher probability, so that fan activities related to the target concept can be activated.

Regarding the adjustment of the provision mode, the customer evaluation server 30 may grant the right to receive a specific item related to the target concept to a customer whose score is equal to or higher than a threshold value. As a result, customers are motivated to increase their own scores in order to receive offers of specific goods, etc. related to the target concept, so that fan activities related to the target concept can be activated. In addition, the customer evaluation server 30 calculates the scores of a plurality of customers who have requested the provision of specific goods, etc. related to the target concept, and calculates the scores of the plurality of customers who rank in a predetermined rank or higher when sorted in descending order of scores among the plurality of customers. may be granted the right to receive the goods, etc. As a result, customers are motivated to increase their own scores in order to receive offers of specific goods, etc. related to the target concept, so that fan activities related to the target concept can be activated.

The customer evaluation server 30 may edit evaluation rules regarding the target concept in response to instructions from the evaluator regarding the target concept. This allows the evaluator to flexibly change the fan definition of the target concept. As an example, in response to a change in the customer target group for a target concept, old evaluation rules can be reviewed to flexibly redefine the requirements of fans of the target concept. Further, the customer evaluation server 30 may present the evaluator with at least one information on the conditions or contents of a plurality of NFTs regarding the target concept. This makes it easier for the evaluator to determine the evaluation value to be assigned to each NFT.

The customer evaluation server 30 may detect an action that matches the NFT granting condition regarding the target concept, and may grant the NFT corresponding to the said granting condition to the customer for whom the behavior was detected. This makes it possible to capture customer behavior that triggers the issuance of NFTs and automatically provide NFTs that contribute to score improvement. Further, the customer evaluation server 30 may detect the purchase, rental, or use of specific goods, services, or content related to the target concept, or the transmission of specific information related to the target concept, as actions that match the granting conditions. This makes it possible to capture customer fan activities that trigger the issuance of NFTs and automatically provide NFTs that contribute to score improvement. Furthermore, the customer evaluation server 30 may set at least one of the NFT provision conditions or contents regarding the target concept in response to instructions from the evaluator regarding the target concept. Thereby, the evaluator can flexibly determine the conditions for acquiring an NFT that contributes to score improvement or the content of the NFT.

(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 executed by either the customer terminal 10 or the customer evaluation server 30.

In the above explanation, an example was shown in which an evaluation table is constructed individually for each target concept. However, the correspondence between target concepts and evaluation tables does not have to be 1:1, and may be 1:many. That is, in order to evaluate a customer's fan of a certain target concept from different viewpoints, a plurality of evaluation tables can be constructed for the target concept.

In the above description, an example was shown in which evaluation rules are defined for each token ID. However, if there are multiple NFTs with the same granting conditions and contents, evaluation rules for these NFTs may be aggregated. In this case, instead of the token ID, a type ID for identifying the different types of NFTs (ie, granting conditions and contents) may be stored in the evaluation rule database. The customer evaluation server 30 refers to the conversion table and converts the token ID into a type ID. The conversion table associates a plurality of token IDs with a type ID. The conversion table may be constructed manually, or may be constructed by referring to the database of each NFT issuer using an API (Application Programming Interface) or crawling. Alternatively, the type ID may be defined to correspond to ancillary data (such as an industry standard type ID) held within the token.

Various information not shown in FIG. 7 can be stored in the evaluation rule table. As a first example, the evaluation rule table may store publisher information regarding a publisher or a publisher ID for identifying the publisher. The evaluator can consider the issuer of each NFT and assign an evaluation value to the NFT. As a second example, the evaluation rule table may store route information regarding an NFT acquisition route. For example, the route information indicates whether the NFT was acquired through primary distribution or secondary distribution. The evaluator can consider the acquisition path of each NFT and assign an evaluation value to the NFT.

In the above explanation, an example was shown in which a token and an evaluation value for holding the token have a 1:1 relationship. However, in the evaluation rule, an evaluation value for holding a token set consisting of a plurality of tokens may be defined. This allows special evaluation to be given to customers who hold all tokens belonging to the token set.

In the above description, an example was shown in which a multivalued (i.e., three or more) score is calculated. However, it is also possible to calculate a binary score. As a first example, the customer evaluation server 30 calculates a score of "high" for a customer who owns any token registered in the evaluation rule, and calculates a score of "high" for a customer who also owns any token registered in the evaluation rule. Customers who do not have a high score can be calculated as ``low''. As a second example, the customer evaluation server 30 calculates the score of a customer who owns a token set registered in the evaluation rule as "high", and calculates the score of a customer who does not own the token set as "low". It can be calculated. The customer evaluation server 30 treats customers with a "high" score more advantageously than customers with a "low" score in providing specific goods related to the target concept.

In the above description, an example was shown in which the customer evaluation server 30 grants NFTs to customers through the NFT granting process shown in FIG. 8, and evaluates the customers based on the ownership status of the NFTs. However, the customer evaluation server 30 may evaluate the customer based on the ownership status of NFTs given by different devices. As an example, the evaluation table may store evaluation rules applied to NFTs provided by a device different from the customer evaluation server 30. For example, a certification authority may issue an NFT that proves that the identity of the wallet owner has been authenticated (e.g. electronic KYC (Know Your Customer)), but the valuation rules applicable to such NFTs are May be stored in a table. In this case, the customer evaluation server 30 may refer to information on reliable certification bodies and change the handling of the NFT depending on whether the issuer of the NFT is a reliable certification body or not. . For example, the customer evaluation server 30 does not apply an evaluation rule to an NFT issued by a certification authority other than a trusted certification authority, or applies an evaluation rule that assigns a lower evaluation value than that of a trusted certification authority. It's okay. Furthermore, at least one of the NFT granting conditions or contents to which the evaluation rule is applied may be set by a person other than the evaluator. For example, evaluation rules for fan evaluation of a certain artist may be applied to NFTs granted according to granting conditions set by an evaluator regarding a brand favored by the artist. Alternatively, at least one of the NFT granting conditions or contents may be predetermined, and only the other may be configured to be settable by the evaluator.

In the above explanation, an example was shown in which a customer is evaluated based on the customer's NFT holding status. However, in addition to the customer's NFT holding status, the customer may be evaluated based on the customer's specific FT holding status. For example, the customer evaluation server 30 determines whether or not the customer owns FT related to the target concept (for example, a crypto asset whose main use is the purchase of goods related to the target concept) or based on the amount held. The score can be calculated.

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

In the above description, an example was shown in which the customer terminal 10 and the customer evaluation server 30 present the customer's 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 ranking information of scores across a plurality of customers.

In the above description, an example was shown 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 provision mode depending on whether the customer owns a specific NFT instead of the score. As an example, the customer evaluation server 30 does not grant the right to receive the goods specified based on the provision request to customers who do not own a specific NFT, but only to customers who own a specific NFT. The right to receive the goods, etc. may also be granted.

In the above description, an example was 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 performed in various ways.
As a first example, the customer evaluation server 30 calculates the customer's score (or determines the grade) in step S430, and transmits the score to an external device. The external device adjusts the manner in which the goods are provided based on the score (S432). The external device may be, for example, a ticket system, an EC system, or a server in 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 a customer score evaluation request to the customer evaluation server 30. In response to the evaluation request, the customer evaluation server 30 calculates the customer's score (or determines the grade) by specifying the NFT held (S430) and calculating the score (S431), and transmits the score to an external source. Send to device. The external device executes adjustment of the manner in which the articles and the like are provided (S432).

In the above description, an example was shown in which a request from a customer is used as a trigger to calculate the score of the customer. However, the customer evaluation server 30 may calculate the customer's score in response to a request from someone other than the customer. As an example, the customer evaluation server 30 responds to each customer (hereinafter referred to as "provider") in response to a request from a person (hereinafter referred to as "provider") who attempts to provide goods, services, or content related to the target concept or other concepts. For example, the customer may be a member of a customer evaluation service provided by the customer evaluation server 30). The customer evaluation server 30 then extracts customers whose scores satisfy specific conditions. The customer evaluation server 30 presents the extracted customer information to the provider, or performs promotional processing on behalf of the provider for the customer (for example, automatically sending emails, recommending goods, etc. that the provider can provide). ) may be performed.
The specific conditions can 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 (for example, 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. A distribution of scores for one or more concepts other than the specific concept (for example, concepts related to the specific concept) is determined as a reference distribution. The customer evaluation server 30 then extracts customers who have a score distribution similar to the reference distribution but who have relatively low scores as fans of the specific concept. The extracted customers may not currently be fans of a particular concept, but may be prospective fans who have similar preferences to fans of the concept. Therefore, marketing activities (promotional activities) related to a specific concept (e.g., recommending products related to a specific concept, giving coupons, giving special discount rights, displaying advertisements, sending information, offering free samples, etc.) to extracted customers. (including offers, free invitations, etc.), it becomes possible to efficiently acquire or cultivate new fans of the specific concept.

In the above explanation, an example was shown in which the evaluator defines the evaluation rules. The aforementioned provider need not be the same as the evaluator. That is, the provider may request the customer evaluation server 30 to evaluate the customer based on evaluation rules defined by another person (evaluator). In addition, when an evaluator edits an evaluation rule, the customer evaluation server 30 stores the evaluation rules defined by other evaluators so that the evaluation rule created by another person (that is, another evaluator) can be reused. may be provided to the evaluator terminal 70.

Alternatively, the customer evaluation server 30 may perform various information processing other than evaluating each customer's fan score in response to a request from the provider.
Specifically, the customer evaluation server 30 specifies the customer's NFT holding status in response to a request from a provider, and collects the issuer ID (that is, information identifying the issuer) of each NFT. The customer evaluation server 30 then uses the NFT issued by the issuer ID specified by the provider (for example, the provider's own ID or the issuer ID of a person related to the provider, hereinafter referred to as "provider ID"). For customers who own NFTs, the holding status of NFTs issued by an issuer ID (target issuer ID) different from the provider ID is analyzed, and the corresponding target issuer ID is extracted. The publisher corresponding to the target publisher ID is a concept that corresponds to the goods, etc. provided by the provider, or a concept that targets customers who have the same preferences as the concept (that is, a complementary relationship or a substitute relationship). This information may be useful for the provider because it may correspond to the person providing the goods, etc. related to the above.
As a first example, the customer evaluation server 30 may notify the provider of information regarding the target publisher. Thereby, the provider can obtain information on potential candidates for its own collaboration or competitors, and use this information as a basis for its own decision-making.
As a second example, the customer evaluation server 30 may notify the provider of information regarding customers who hold NFTs issued by the target issuer. As a result, the provider can acquire information on its own potential customers (potential new fans) or existing customers who are at risk of being lost to the target publisher (potential defective fans), and It can be used for marketing activities.

As another example, the customer evaluation server 30 may analyze the following various information in response to a request from a provider and extract information 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 (in other words, C2C) ・NFT transaction price between customers ・Real-time data on NFTs traded between customers ・How much NFT has been acquired from which issuer Data (best selling analysis/competitive analysis)
As a first example, the customer evaluation server 30 owns NFTs issued by the issuer corresponding to the provider ID, but has transferred the NFTs to others in a number exceeding a threshold, or The provider may be notified of information regarding the customer who transferred the NFT to another person within the period. Such a customer may be a fan of the concept corresponding to the goods etc. provided by the provider, but has disengaged or is beginning to disengage. By notifying the provider of such customer information, the provider can take measures to prevent the customer from returning or leaving (for example, re-approaching the customer).
As a second example, the customer evaluation server 30 provides information regarding a customer who owned NFTs issued by the issuer corresponding to the provider ID, but who acquired a number of NFTs exceeding a threshold within the most recent predetermined period. may be notified to the provider. Such customers may be new fans of the concepts that correspond to the products, etc. 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 regarding a customer who owns a collectible NFT among NFTs issued by the 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 customers may also be interested in other collectible NFTs. By notifying the provider of such customer information, the provider can encourage participation in the project by approaching the customer when implementing a project to issue new collectible NFTs (for example, a concert tour). I can do it.
As a fourth example, the customer evaluation server 30 provides information regarding a customer who owns a collectible NFT among NFTs issued by the issuer corresponding to the provider ID, but there is a missing item in the NFT, and the missing NFT. The provider may be notified of information regarding the By notifying the provider of such customer information and missing NFT information, the provider can inform the customer of the missing NFT information and how to obtain it, thereby increasing sales of the goods, etc. it provides. can be promoted.
As a fifth example, the customer evaluation server 30 may notify the provider of analysis results regarding secondary distribution of NFTs issued by the issuer corresponding to the provider ID. For example, the customer evaluation server 30 may automatically acquire information on the secondary distribution price of the NFT issued by the provider ID, and notify the provider of an alert according to a certain rule. By informing customers who own NFTs of the provider of information regarding the price increase of the NFTs that the provider has issued, the provider can increase the customer's desire to acquire NFTs that the provider will issue in the future.
As a sixth example, the customer evaluation server 30 performs CRM (Customer Relationship Management) analysis regarding the primary distribution (that is, new acquisition by a customer) and secondary distribution of NFTs issued by the issuer corresponding to the provider ID, or other The provider may be notified of the results of the analysis. For example, the customer evaluation server 30 performs various analyzes on each NFT issued by the provider ID in the range of primary distribution, secondary distribution, or total distribution. Specifically, customer evaluation server 30 may analyze transaction frequency, transaction amount, or number of transactions. Further, the customer evaluation server 30 performs Pareto analysis or ABC analysis. The provider can use such analysis results as material for making decisions in planning NFTs to be issued in the future.

The customer evaluation server 30 may refer to the customer's behavior history or transaction history to estimate transaction characteristics or attributes of the customer. As a first example, the customer evaluation server 30 determines what kind of transaction characteristics a customer with a specific attribute (for example, a housewife) has (for example, when (for example, day of the week or time of day) a customer actively trades NFTs). ). As a second example, it is estimated what kind of attributes a customer with a characteristic trading history has (for example, a customer who trades frequently is a day trader for speculative purposes). As a third example, it is estimated what kind of attributes a customer with a characteristic behavior history has (for example, a customer who frequently participates in fan events is a true fan). The customer evaluation server 30 may notify the provider of the estimated information, or may 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. Moreover, various improvements and changes can be made to the embodiments described above 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

at least one computer,
A means of identifying NFT (Non-Fungible Token) held by a customer by querying a distributed ledger system,
means for calculating the score of the customer as a fan of the target concept based on the NFT held by the customer and an evaluation rule that defines an evaluation value assigned to each of a plurality of NFTs related to the target concept;
A program that functions as
causing the computer to function as a means for adjusting the manner in which at least one particular product, service, or content related to the target concept is provided to the customer according to the score;
The program according to claim 1.
The adjustment means treats customers with higher scores more advantageously in providing specific goods, services, or content related to the target concept.
The program according to claim 2.
The adjusting means increases the higher the customer's score, the higher the customer's probability of winning in a lottery for determining whether or not to provide a specific product, service, or content related to the target concept.
The program according to claim 2.
The adjusting means grants a customer whose score is equal to or higher than a threshold the right to receive a specific product, service, or content related to the target concept.
The program according to claim 2.
The calculating means calculates a score of a plurality of customers who have requested provision of specific goods, services, or contents related to the target concept as fans of the target concept;
The adjustment means grants the right to receive specific goods, services, or content related to the target concept to customers whose scores rank at a predetermined rank or higher when sorted in descending order of the scores among the plurality of customers. ,
The program according to claim 2.
causing the computer to function as means for editing evaluation rules regarding the target concept in response to instructions from an evaluator regarding the target concept;
The program according to claim 1.
causing the computer to function as means for presenting to an evaluator regarding the target concept at least one information on conditions or contents for granting a plurality of NFTs regarding the target concept;
The program according to claim 7.
The computer,
means for detecting an action that matches the NFT granting conditions regarding the target concept;
further functioning as a means for granting NFTs corresponding to the granting conditions to customers whose actions match the granting conditions are detected;
The program according to claim 1.
The means for detecting the behavior includes purchasing, borrowing, using, owning, or lending specific goods, services, or contents related to the target concept, or transmitting specific information related to the target concept, as the behavior that matches the granting condition. detect,
The program according to claim 9.
causing the computer to function as means for setting at least one of NFT granting conditions or contents regarding the target concept in response to instructions from an evaluator regarding the target concept;
The program according to claim 9.
A means of identifying NFT (Non-Fungible Token) held by a customer by querying a distributed ledger system;
Means for calculating a score of the customer as a fan of the target concept based on NFTs held by the customer and an evaluation rule that defines evaluation values assigned to each of a plurality of NFTs regarding the target concept. information processing equipment.
At least one computer
A step of identifying the NFT (Non-Fungible Token) held by the customer by querying the distributed ledger system,
Calculating the score of the customer as a fan of the target concept based on the NFT held by the customer and an evaluation rule that defines an evaluation value assigned to each of the plurality of NFTs related to the target concept;
How to do it.