Information processing device, method, and program

Abstract

Customer evaluations as fans are based on a variety of information, or useful information is extracted by analyzing a variety of customer information. [Solution] A program in 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 as a means for calculating a 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 a plurality of NFTs relating to the target concept.

Description

Technical Field

[0001] The present disclosure relates to an information processing apparatus, method, and program.

Background Art

[0002] In various businesses such as entertainment, for example, cultivating existing customers into more engaged customers (i.e., fan conversion) is one of the major issues.

[0003] Patent Document 1 discloses a technique for providing a special effect for a specific participant (for example, a participant who participates in many virtual events, a participant who purchases a specific product, or a participant who has been charged a certain amount or more) extracted based on the behavior history of event participants.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in the technology described in Patent Document 1, participants are evaluated based on the quantity of behavioral indicators over a predetermined period (for example, the number of events participated in, the number of items purchased, the total amount spent, the support parameters, or the score in a game related to the event, over the entire period or a certain period (within the last week)). For example, participation in events or spending when a certain character has few fans will be treated the same as participation in events or spending after the character's fan base has grown. Thus, in the technology described in Patent Document 1, it was difficult to evaluate participants by considering the qualitative aspects of similar behavior. Furthermore, in the technology described in Patent Document 1, it was difficult to evaluate participants by considering their behavioral history with parties other than the organizer of the virtual event, such as the purchase of related products from different businesses or the purchase of specific products through secondary distribution.

[0006] One of the purposes of this disclosure is to provide a technology that takes diverse information into account when evaluating customers as fans. Another purpose of this disclosure is to provide a technology that analyzes diverse customer information and extracts useful information. [Means for solving the problem]

[0007] A program in one aspect of this 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 as a means for calculating a 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 a plurality of NFTs relating to the target concept. [Brief explanation of the drawing]

[0008] [Figure 1] This is a block diagram showing the configuration of the information processing system in this embodiment. [Figure 2] This is a block diagram showing the configuration of the customer terminal in this embodiment. [Figure 3] This is a block diagram showing the server configuration of this embodiment. [Figure 4] This diagram shows the configuration of the distributed ledger system of this embodiment. [Figure 5] This is a block diagram showing the configuration of the evaluator terminal in this embodiment. [Figure 6] This is an explanatory diagram of one aspect of this embodiment. [Figure 7] This diagram shows the data structure of the evaluation table in this embodiment. [Figure 8] This is a flowchart of the NFT assignment process in this embodiment. [Figure 9] This is a flowchart of the evaluation rule editing process in this embodiment. [Figure 10] This is a flowchart of the score verification process in this embodiment. [Figure 11] This is a flowchart of the processing for adjusting the delivery method of this embodiment. [Modes for carrying out the invention]

[0009] Hereinafter, one embodiment of the present invention will be described in detail with reference to the drawings. In the drawings used to illustrate the embodiment, the same reference numerals are generally used for identical components, and repeated descriptions thereof will be omitted.

[0010] (1) Configuration of the information processing system The configuration of the information processing system will now be described. Figure 1 is a block diagram showing the configuration of the information processing system in this embodiment.

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

[0012] 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, 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 the "target concept").

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

[0014] 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.

[0015] 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, a tablet terminal, or a personal computer. The user of the evaluator terminal 70 is an evaluator regarding the target concept. An evaluator regarding 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 has rights regarding the target concept (for example, copyright, trademark right, publicity right, or merchandising right based on contract or business practice), or a person who provides goods, services, or content regarding the target concept, or a person designated by these persons (as an example, a fan community).

[0016] (1-1) Configuration of the customer terminal The configuration of the customer terminal will be described. FIG. 2 is a block diagram showing the configuration of the customer terminal of the present embodiment.

[0017] 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.

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

[0019] The program includes, for example, the following programs. · Program of an OS (Operating System) · Program of an application (e.g., web browser) that executes information processing

[0020] The data includes, for example, the following data. · Database referred to in information processing · Data obtained by executing information processing (i.e., execution result of information processing)

[0021] The processor 12 is a computer that realizes the functions of the customer terminal 10 by starting the programs 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)

[0022] 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., an image) to an output device connected to the customer terminal 10. Input devices include, for example, keyboards, pointing devices, touch panels, or combinations thereof. The output device is, for example, a display 21, a speaker, or a combination thereof.

[0023] The communication interface 14 is configured to control communication between the customer terminal 10 and an external device (for example, a customer evaluation server 30 or a distributed ledger system 50).

[0024] 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.

[0025] (1-2) Server configuration The server configuration will now be described. Figure 3 is a block diagram showing the server configuration of this embodiment.

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

[0027] 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 hard disk).

[0028] The program includes, for example, the following: • OS programs • Programs for applications that perform information processing.

[0029] The data includes, for example, the following: • Databases referenced in information processing • Results of information processing

[0030] The processor 32 is a computer that implements the functions of the customer evaluation server 30 by launching programs stored in the storage device 31. The processor 32 is, for example, at least one of the following: ·CPU GPU ASIC •FPGA

[0031] 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. Input devices include, for example, keyboards, pointing devices, touch panels, or combinations thereof. An output device is, for example, a display.

[0032] The communication interface 34 is configured to control communication between the customer evaluation server 30 and external devices (for example, a customer terminal 10, a distributed ledger system 50, or an evaluator terminal 70).

[0033] (1-3) Configuration of a distributed ledger system The configuration of the distributed ledger system will now be described. Figure 4 shows the configuration of the distributed ledger system of this embodiment.

[0034] As shown in Figure 4, the distributed ledger system 50 comprises multiple node computers 55-1 to 55-4.

[0035] The node computers 55 are connected to each other via a network (which may include the network NW in Figure 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 wireless. The node computers 55 communicate with each other in a peer-to-peer manner.

[0036] Node computer 55 manages a distributed ledger using, for example, blockchain technology. Specifically, one of the node computers 55 acquires data related to the token transactions to be recorded. Node computer 55 creates a block containing the acquired data and adds it to the blockchain. Node computer 55 sends the information of the added block to other node computers 55. Other node computers 55 verify the correctness of the received block, and if the verification is successful, add the block to the blockchain. Node computer 55 then finalizes the blockchain, for example, according to the number of linked blocks (number of confirmations). This ensures that the same distributed ledger is stored across multiple node computers 55 that constitute the distributed ledger system 50. The stored data is encrypted as appropriate.

[0037] 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 have five or more node computers 55, or it may have two or three node computers 55. Also, the number of node computers 55 constituting the distributed ledger system 50 may vary over time.

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

[0039] (1-4) Configuration of evaluator terminals The configuration of the evaluator terminal will now be described. Figure 5 is a block diagram showing the configuration of the evaluator terminal in this embodiment.

[0040] As shown in Figure 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 the display 81.

[0041] 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 hard disk).

[0042] The program includes, for example, the following: • OS programs • Programs for applications that perform information processing (e.g., web browsers)

[0043] The data includes, for example, the following: • Databases referenced in information processing • Data obtained by performing information processing (i.e., the results of performing information processing)

[0044] The processor 72 is a computer that realizes the functions of the evaluator terminal 70 by launching programs stored in the memory device 71. The processor 72 is, for example, at least one of the following: ·CPU GPU ASIC •FPGA

[0045] 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., images) to an output device connected to the evaluator terminal 70. Input devices include, for example, keyboards, pointing devices, touch panels, or combinations thereof. The output devices are, for example, a display 81, a speaker, or a combination thereof.

[0046] The communication interface 74 is configured to control communication between the evaluator terminal 70 and an external device (for example, a customer evaluation server 30 or a distributed ledger system 50).

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

[0048] (2) One embodiment One aspect of this embodiment will be described. Figure 6 is an explanatory diagram of one aspect of this embodiment.

[0049] As shown in Figure 6, the customer terminal 10 requests the customer evaluation server 30 to evaluate customer C11's score as a fan of the target concept T13, in response to instructions from customer C11 (sending an evaluation request to the customer evaluation server 30). This evaluation request includes information that can identify the NFT (Non-Fungible Token) associated with customer C11's wallet W12 (i.e., the NFT held by customer C11) (for example, the token ID of the NFT, or the identification information of wallet W12). Based on the evaluation request, the customer evaluation server 30 identifies the NFT held by customer C11. 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 associated with customer C11's wallet ID.

[0050] The customer evaluation server 30 refers to the evaluation rule R14 associated with the target concept T13. The evaluation rule R14 is defined in a way that allows for the identification of evaluation values ​​assigned to each of several NFTs related to the target concept T13. NFTs related to the target concept T13 are typically, but not limited to, NFTs that can be obtained by engaging in fan activities related to the target concept T13. Based on the NFTs held by customer C11 and the evaluation rule R14, the customer evaluation server 30 calculates customer C11's score as a fan of the target concept T13.

[0051] The customer evaluation server 30 sends an evaluation response to the customer terminal 10. The evaluation response includes information that identifies the score of 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 customer C11.

[0052] In this way, the customer evaluation server 30 calculates a score for 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 makes it possible to calculate a customer's score while distinguishing between various NFTs that can be obtained through fan activities, for example. For example, even for the same type of fan activity, different evaluations can be given to the NFTs that can be obtained by performing that activity, depending on the context of the activity (for example, when, where, or in what situation the activity was performed, or a commemorative event related to the target concept T13 concerning the activity). Furthermore, even if multiple NFTs relating to the same target concept T13 are issued by different issuers (especially issuers other than the evaluator), a common score as a fan of the target concept T13 can be calculated based on the evaluation value assigned to each NFT. Moreover, even if a customer acquires (receives) an NFT through secondary market (e.g., customer-to-customer transactions) but the issuer is unaware of this fact, the customer can be evaluated considering their possession of the NFT. In other words, according to the customer evaluation server 30, the evaluation of customer C11 as a fan of the target concept T13 can be performed by taking various pieces of information into consideration.

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

[0054] (3-1) Evaluation Table The evaluation table of this embodiment will now be described. Figure 7 shows the data structure of the evaluation table of this embodiment.

[0055] The evaluation table is a database where evaluation rules are stored. These evaluation rules define the evaluation value that a customer earns by owning the corresponding NFT. The evaluation value is equivalent to the score a customer earns as a fan of the target concept.

[0056] The evaluation table is constructed individually for each target concept. Therefore, tokens for which evaluation values ​​are defined in the evaluation table of the 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 of the second target concept (hereinafter referred to as the "second evaluation table"), or they may overlap in some or all respects. Furthermore, since evaluation values ​​can be defined individually in each database, the evaluation value defined in the first evaluation table for a given token does not necessarily match the evaluation value defined in the second evaluation table.

[0057] As shown in Figure 7, the evaluation table includes the "Rule ID" field, the "Token ID" field, the "Granting Condition" field, the "Content" field, and the "Evaluation Value" field. Each field is related to the others.

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

[0059] 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 the "Target Rule") identified by the corresponding Rule ID applies.

[0060] The "Granting Conditions" field stores granting condition information. Granting condition information is information about the conditions that an NFT to which the target rule applies (hereinafter referred to as the "Target NFT") must be granted. There are no particular restrictions on the format of the granting condition information, but granting condition information may be written in natural language to help evaluators of the target concept understand the granting conditions of the NFT.

[0061] The granting condition is typically defined as a customer taking a specific action (typically fan activity) related to the subject concept. Such actions may include, for example, visiting a specific location (e.g., an event venue or store), purchasing, borrowing (including leasing), using, owning, or lending (including lending) specific items (e.g., tickets), services, or content, posting specific information on a social networking service (SNS), viewing specific content, entering or participating in a specific campaign, or owning one or more specific NFTs. Alternatively, the specific action may be a prompting a new customer (e.g., a customer who does not own any NFTs related to the subject concept or whose score is below a certain value) to take at least one of the actions exemplified above, and the customer taking the prompting action. Furthermore, the granting condition may have additional conditions attached to the specific action. These additional conditions may relate to, for example, time, date and time, place, quantity, number of times, frequency, amount, or number of people.

[0062] The "Content" field stores content information. Content information is information about the content of the target NFT. There are no particular restrictions on the format of the content information, but it may be expressed in natural language, images, or audio to help evaluators 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 include information that can be referenced from that information. For example, if a URL (Uniform Resource Locator) is recorded in the target NFT, the content of the target NFT may include information that can be referenced by that URL (e.g., content).

[0063] The "Rating Value" field stores rating value information. This rating value information concerns the rating value that a customer earns by owning the target NFT. The rating value information can be configured to be editable according to the evaluator's instructions.

[0064] (4) Information processing The information processing of this embodiment will now be described.

[0065] (4-1) NFT assignment process The NFT assignment process of this embodiment will now be described. Figure 8 is a flowchart of the NFT assignment process of this embodiment.

[0066] The NFT assignment process shown in Figure 8 can be initiated, for example, in response to a request from an evaluator.

[0067] As shown in Figure 8, the evaluator terminal 70 executes a request to set the assignment conditions and content (S170). Specifically, the evaluator operates the evaluator terminal 70 to instruct the setting of the granting conditions and content of a new NFT. The evaluator terminal 70 generates a setting request for the granting conditions and content in response to the evaluator's instructions. The setting request includes information that identifies the granting conditions and content of the NFT that the evaluator intends to set. The evaluator terminal 70 sends the setting request to the customer evaluation server 30.

[0068] After step S170, the customer evaluation server 30 performs the setting of the grant conditions and content (S130). Specifically, the customer evaluation server 30 receives the configuration request sent in step S170. Based on the configuration request, the customer evaluation server 30 identifies the granting conditions and content of the NFT that the evaluator intends to configure. The customer evaluation server 30 stores the identified granting conditions and content in the storage device 31. As an example, the customer evaluation server 30 may store the information of the identified granting conditions and content in a database for managing the NFTs that the customer evaluation server 30 can grant.

[0069] After step S130, the customer evaluation server 30 performs the detection of actions that match the awarding conditions (S131). Specifically, the customer evaluation server 30 detects, based on information obtained from an external device, that the customer has taken an action that matches one of the awarding conditions set in step S130. The external device may be, for example, a customer terminal 10, or an external system. The external system may be, for example, a ticketing system, an e-commerce (electronic commerce) system, an SNS system, or a content viewing system.

[0070] For example, the customer evaluation server 30 may detect that a customer has taken an action that meets the criteria by obtaining a serial code issued to the customer from, for example, the customer terminal 10 as proof that the customer has taken an action that meets the criteria. Alternatively, the customer evaluation server 30 may obtain the customer's behavior history from an external system and analyze the behavior history to determine whether or not the customer has taken an action that meets the criteria.

[0071] After step S131, the customer evaluation server 30 performs the NFT granting (S132). Specifically, the customer evaluation server 30 grants an NFT corresponding to the granting conditions to customers whose actions in step S131 are detected to match the granting conditions. For example, the customer evaluation server 30 requests the distributed ledger system 50 to grant the NFT to the customer. Here, the customer evaluation server 30 may query the customer for information necessary for granting (e.g., the customer's wallet information) before granting the NFT to the customer. Upon completion of step S132, the customer evaluation server 30 terminates the NFT assignment process shown in Figure 8.

[0072] (4-2) Editing the evaluation rules The evaluation rule editing process of this embodiment will now be described. Figure 9 is a flowchart of the evaluation rule editing process of this embodiment.

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

[0074] As shown in Figure 9, the evaluator terminal 70 executes a request to view the evaluation rules (S270). Specifically, the evaluator operates the evaluator terminal 70 to instruct it to view the evaluation rules for the target concept relating to the evaluator. The evaluator terminal 70 generates a request to view the evaluation rules in response to the evaluator's instruction. The request includes information that identifies the evaluation rules the evaluator wishes to view. The evaluation rules the evaluator wishes to view may be all or part of the evaluation rules relating to the target concept. The evaluator terminal 70 sends the request to the customer evaluation server 30.

[0075] After step S270, the customer evaluation server 30 performs the acquisition of evaluation rules (S230). Specifically, the customer evaluation server 30 obtains 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 obtains the identified evaluation rule from the evaluation table (Figure 7).

[0076] After step S230, the customer evaluation server 30 performs the presentation of evaluation rules (S231). Specifically, the customer evaluation server 30 transmits the evaluation rules acquired in step S230 to the evaluator terminal 70.

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

[0078] After step S231, the evaluator terminal 70 executes an edit request for the evaluation rules (S272). Specifically, the evaluator operates the evaluator terminal 70 to instruct the editing of the evaluation rules for the target concept relating to the evaluator. Here, editing the evaluation rules may involve changing or deleting existing evaluation rules, or adding new evaluation rules. When the evaluator changes or deletes existing evaluation rules, 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 editing request for the evaluation rule in response to the evaluator's instructions. The editing request includes information that identifies the editing content desired by the evaluator. The editing content includes, for example, at least one of the following: • Changed evaluation rules • Revised evaluation value information • Evaluation rules that will be deleted • At least one of the following for the new evaluation rule: token ID, granting conditions information, content information, or evaluation value information.

[0079] After step S272, the customer evaluation server 30 performs the editing of the evaluation rules (S232). Specifically, the customer evaluation server 30 receives the edit request sent in step S272. Based on the received edits, the customer evaluation server 30 updates the evaluation table (Figure 7). Upon completion of step S232, the customer evaluation server 30 terminates the evaluation rule editing process shown in Figure 9.

[0080] Furthermore, when an evaluator adds a new evaluation rule, the requests 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.

[0081] (4-3) Score verification process The score verification process of this embodiment will now be described. Figure 10 is a flowchart of the score verification process of this embodiment.

[0082] The score verification process shown in Figure 10 can be initiated, for example, in response to a customer request.

[0083] As shown in Figure 10, the customer terminal 10 executes a score evaluation request (S310). Specifically, the customer operates the customer terminal 10 to instruct the evaluation of their score as a fan of the target concept. The customer terminal 10 generates a score evaluation request in response to the customer's instructions. The evaluation request includes information that can identify the NFTs held by the customer (e.g., a list of token IDs of the NFTs, 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.

[0084] After step S310, the customer evaluation server 30 performs the identification of owned NFTs (S330). Specifically, the customer evaluation server 30 obtains the evaluation request sent in step S310. Based on the evaluation request, the customer evaluation server 30 identifies the NFTs held by the customer. For example, the customer evaluation server 30 may obtain the token ID of the NFT linked to the customer's wallet information from the distributed ledger system 50.

[0085] Furthermore, an evaluation request may include not just one but multiple wallet information entries. If an evaluation request includes multiple wallet information entries, the customer evaluation server 30 may obtain the token ID of the NFT associated with any of the multiple wallet information entries from the distributed ledger system 50.

[0086] If a customer holds multiple wallets, the customer evaluation server 30 may obtain the token IDs of NFTs associated with the customer's multiple wallet information from the distributed ledger system 50. As a first example, multiple wallet information is pre-registered in the 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 wallet information is pre-registered in the 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 estimates other wallets that have conducted transactions with the customer's wallet that satisfy at least one of the following conditions, for example, as the customer's wallet (unregistered wallet). • Another wallet is trading cryptocurrency or other tokens with the customer's wallet, and the transaction frequency exceeds a threshold. • Another wallet conducted a transaction with the customer's wallet that did not involve any exchange of value. • 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 NFTs).

[0087] Furthermore, the evaluation request may include information to verify that the customer is not falsifying 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 performs identity verification on the customer (e.g., confirms that the correct wallet ID and password combination has been entered) and, if it can confirm that the customer is the owner of the wallet, issues an access token to prove that fact.

[0088] Furthermore, NFTs may be traded on a system that exists outside the distributed ledger system 50 (for example, sometimes called a private chain or second layer). In this case, the valuation request may include information that identifies the system on which the NFTs held by the customer are effectively being traded, and the customer's wallet information on that system.

[0089] After step S330, the customer evaluation server 30 performs score calculation (S331). Specifically, the customer evaluation server 30 identifies an evaluation table (Figure 7) used to calculate the customer's score based on the evaluation request and retrieves the evaluation table. The customer evaluation server 30 applies the evaluation rules stored in the evaluation table to the NFT identified in step S330.

[0090] As a first example, the customer evaluation server 30 determines whether an evaluation rule applicable to each NFT owned by a customer is stored in the evaluation table. If the customer evaluation server 30 finds a suitable evaluation rule, it refers to the evaluation value defined in that evaluation rule. The customer evaluation server 30 may also calculate the customer's score by summing the evaluation values ​​for all evaluation rules applicable to the customer's NFTs.

[0091] As a second example, the customer evaluation server 30 may calculate the customer's score by summing up a predetermined number of evaluation rules (for example, the three with the highest evaluation values) in descending order of evaluation values ​​for all evaluation rules applicable to the customer's NFTs.

[0092] Furthermore, the customer evaluation server 30 may further adjust the customer's score based on the customer's attributes, as illustrated below. If a customer possesses a Type 1 NFT (for example, an NFT given as a bonus for purchasing music, or an NFT issued by a record company) but does not possess a Type 2 NFT (for example, an NFT given as a bonus for purchasing live tickets, 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 whose fan activities may be limited, and encourages them to broaden their fan activities. If a customer has not acquired an NFT to which the evaluation rules apply for a certain period of time, the customer evaluation server 30 may add points to that customer's score. This allows for preferential treatment of customers who are fans of the target concept but are at risk of becoming churn, and encourages them to return as fans. The customer evaluation server 30 may refer to the transaction history of the NFT to which the evaluation rules apply, and may add points to the customer's score if the frequency of acquisition, acquisition amount, or number of acquisitions of the NFT within the most recent predetermined period exceeds a threshold. This allows for preferential treatment of customers who may be new fans of the target concept, and encourages them to become more core fans. The customer evaluation server 30 refers to the transaction history of the NFT to which the evaluation rules apply and identifies other customers who have traded the NFT with the customer (hereinafter referred to as "Connection 1 customers") and customers who have traded the NFT with Connection 1 customers (hereinafter referred to as "Connection 2 customers"). The customer evaluation server 30 may refer to the scores of Connection 1 customers or Connection 2 customers and add points to the score of the target customer. For example, the customer evaluation server 30 may determine the value to add to the target customer based on the maximum score among Connection 1 customers or Connection 2 customers. This makes it possible to give preferential treatment to target customers who have connections with core fans of the target concept and encourage the development of more core fans.

[0093] After step S331, the customer evaluation server 30 performs score presentation (S332). Specifically, the customer evaluation server 30 sends the score calculated in step S331 to the customer terminal 10. Alternatively, the customer evaluation server 30 may provide the customer with an NFT (Network Document Format) certifying the score, either instead of sending the score or in addition to sending the score.

[0094] After step S332, the customer terminal 10 retrieves the score transmitted in step S332. The customer terminal 10 presents the customer with their score, for example, by displaying an image on the display 81. Upon completion of step S332, the customer terminal 10 terminates the score verification process shown in Figure 10.

[0095] (4-4) Processing to adjust the manner of provision The process for adjusting the provisioning method of this embodiment will now be described. Figure 11 is a flowchart of the process for adjusting the provisioning method of this embodiment.

[0096] The service delivery adjustment process shown in Figure 11 can be initiated, for example, in response to a customer request.

[0097] As shown in Figure 11, the customer terminal 10 executes a request for the provision of goods, etc. (S410). Specifically, the customer operates the customer terminal 10 to instruct 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 request includes information that can identify the NFTs 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 receive. The customer terminal 10 sends the request to the customer evaluation server 30.

[0098] After step S410, the customer evaluation server 30 performs the identification of owned NFTs (S430). Specifically, the customer evaluation server 30 obtains the provision request sent in step S410. Based on the provision request, the customer evaluation server 30 identifies the NFTs held by the customer. For example, the customer evaluation server 30 may obtain the token ID of the NFT linked to the customer's wallet information from the distributed ledger system 50.

[0099] After step S430, the customer evaluation server 30 performs score calculation (S431). Specifically, the customer evaluation server 30 identifies an evaluation table (Figure 7) used to calculate the customer's score based on the request and obtains 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.

[0100] After step S431, the customer evaluation server 30 performs adjustment of the manner in which goods, etc. are provided (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 (including NFTs) related to the target concept that the customer wishes to receive) are provided to the customer, according to the score calculated in step S431.

[0101] As a first example, the customer evaluation server 30 may treat customers with higher scores more favorably in terms of the provision of goods, etc. Favorable treatment may include at least one of the following: • Increase the probability of winning items whose availability is determined by lottery. • Allocate items of relatively higher quality or more popular among similar items (for example, seats with better viewing options at entertainment events). • Increase the purchase quantity or purchase amount. • Include bonus items (which may include new NFTs). • Prioritize delivery order or delivery time. • Lower the price offered • Grant the right to have an experience related to the target concept (for example, shaking hands with a person representing the target concept).

[0102] As a second example, the customer evaluation server 30 may not grant customers whose scores are below a threshold the right to receive the goods, etc., specified based on the request, but may grant the right to receive such goods, etc., only to customers whose scores are above the threshold.

[0103] 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 only grant the right to receive such goods, etc. to customers who are at or above the predetermined rank.

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

[0105] (5) Summary As explained above, the customer evaluation server 30 identifies NFTs held by a customer by querying a distributed ledger system, and calculates the customer's score as a fan of the target concept based on the NFT and evaluation rules related to the target concept. This makes it possible to calculate the customer's score while distinguishing between various NFTs that can be obtained through fan activities, for example. For example, even for the same type of fan activity, different evaluations can be given to the NFTs that can be obtained through that activity depending on the context of the activity. Furthermore, even if multiple NFTs relating to the same target concept are issued by different issuers (for example, the distributor of an artist's music and the organizer of the artist's live performance), a common score as a fan of the target concept can be calculated based on the evaluation value assigned to each NFT. Moreover, even if a customer acquires an NFT through secondary marketplaces but the issuer is unaware of this fact, the customer can be evaluated considering the possession of the NFT. In short, the customer evaluation server 30 can evaluate a customer as a fan of a target concept by considering a variety of information.

[0106] The customer evaluation server 30 may adjust the manner in which specific goods or services related to the target concept are provided to the customer according to the score. This allows those who provide goods or services related to the target concept to flexibly determine the manner in which such goods or services are provided according to the customer's score.

[0107] Regarding the adjustment of the provision method, the customer evaluation server 30 may treat customers with higher scores more favorably in the provision of specific goods related to the target concept. This motivates customers to improve their scores in order to receive favorable treatment in the provision of specific goods, thereby stimulating fan activities related to the target concept. In addition, the customer evaluation server 30 may give customers with higher scores a higher probability of winning in the lottery to determine whether or not they can receive specific goods related to the target concept. This motivates customers to improve their scores in order to receive specific goods related to the target concept with a higher probability, thereby stimulating fan activities related to the target concept.

[0108] Regarding the adjustment of the provision method, the customer evaluation server 30 may grant customers whose scores are above a threshold the right to receive specific goods or services related to the target concept. This motivates customers to improve their scores in order to receive specific goods or services related to the target concept, thereby stimulating fan activities related to the target concept. Alternatively, the customer evaluation server 30 may calculate the scores of multiple customers who have requested specific goods or services related to the target concept, and grant the right to receive such goods or services to customers who rank above a predetermined rank when sorted in descending order of scores among the multiple customers. This motivates customers to improve their scores in order to receive specific goods or services related to the target concept, thereby stimulating fan activities related to the target concept.

[0109] The customer evaluation server 30 may edit the evaluation rules for a target concept in response to instructions from the evaluator regarding that concept. This allows the evaluator to flexibly change the definition of a fan of the target concept. For example, in response to a change in the target customer segment for the target concept, the old evaluation rules can be reviewed and the requirements for a fan of that 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 assigning multiple NFTs related to the target concept. This makes it easier for the evaluator to determine the evaluation value to assign to each NFT.

[0110] The customer evaluation server 30 may detect actions that match the conditions for granting NFTs related to the target concept, and grant NFTs corresponding to those conditions to customers whose actions are detected. This allows the server to capture customer actions that trigger NFT issuance and automatically grant NFTs that contribute to score improvement. The customer evaluation server 30 may also detect actions that match the grant conditions, such as 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 the server to capture customer fan activities that trigger NFT issuance and automatically grant NFTs that contribute to score improvement. Furthermore, the customer evaluation server 30 may set at least one of the conditions or content of granting NFTs related to the target concept in response to instructions from evaluators regarding the target concept. This allows evaluators to flexibly determine the conditions for acquiring NFTs that contribute to score improvement, or the content of such NFTs.

[0111] (6) Other modifications The storage device 11 may be connected to the customer terminal 10 via a 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 a network NW.

[0112] Each of the above information processing steps can be executed on either the customer terminal 10 or the customer evaluation server 30.

[0113] The above explanation showed an example of constructing an evaluation table individually for each target concept. However, the correspondence between the target concept and the evaluation table does not have to be one-to-one; it can be one-to-many. In other words, multiple evaluation tables can be constructed for a given target concept in order to evaluate the fans of that concept's customers from different perspectives.

[0114] The above explanation shows an example of defining evaluation rules for each token ID. However, if there are multiple NFTs with identical granting conditions and content, the evaluation rules for these NFTs may be aggregated. In this case, instead of token IDs, a type ID to identify the similarities and differences in the types of NFTs (i.e., granting conditions and content) may be stored in the evaluation rule database. The customer evaluation server 30 converts token IDs to type IDs by referring to 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 referring to the database of the issuer of each NFT via an API (Application Programming Interface) or crawling. Alternatively, the type ID may be defined to correspond to supplementary data (such as an industry-standard type ID) held within the token.

[0115] The evaluation rule table can store various types of information not shown in Figure 7. As a first example, the evaluation rule table may store issuer information about the issuer, or an issuer ID to identify the issuer. The evaluator can assign an evaluation value to each NFT, taking into account the issuer of that NFT. As a second example, the evaluation rule table may store route information about the acquisition route of the NFT. For example, route information indicates whether the NFT was acquired through primary or secondary market. The evaluator can assign an evaluation value to each NFT, taking into account the acquisition route of that NFT.

[0116] The above explanation showed an example where there is a one-to-one relationship between a token and the valuation value of holding that token. However, the valuation rules may also define a valuation value for holding a token set consisting of multiple tokens. This would allow for special valuations to be given to customers who hold all tokens belonging to the token set.

[0117] The above explanation shows an example of calculating a multi-valued (i.e., three or more) score. 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 customers who possess any of the tokens registered in the evaluation rules, and a score of "low" for customers who do not possess any of the tokens registered in the evaluation rules. As a second example, the customer evaluation server 30 may calculate a score of "high" for customers who possess a set of tokens registered in the evaluation rules, and a score of "low" for customers who do not possess that set of tokens. The customer evaluation server 30 will treat customers with a "high" score more favorably than customers with a "low" score when providing specific goods or services related to the target concept.

[0118] The above description shows an example in which the customer evaluation server 30 grants an NFT to a customer through the NFT granting process shown in Figure 8 and evaluates the customer based on the NFT ownership status. However, the customer evaluation server 30 may also evaluate the customer based on the NFT ownership status of NFTs granted by different devices. For example, the evaluation table may store evaluation rules that apply to NFTs granted by devices other than 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 verified (e.g., eKYC (electronic KYC (Know Your Customer))), and evaluation rules that apply to such an NFT may be stored in the evaluation table. In this case, the customer evaluation server 30 may refer to information on trusted certification authorities and change how it handles such NFTs depending on whether the issuer of the NFT is a trusted certification authority or not. For example, the customer evaluation server 30 may not apply evaluation rules to NFTs issued by certification authorities other than trusted certification authorities, or may apply evaluation rules that assign a lower evaluation value compared to trusted certification authorities. Furthermore, at least one of the granting conditions or content of an NFT to which the evaluation rules apply may be set by someone other than the evaluator. For example, evaluation rules for evaluating fans of a certain artist may apply to an NFT granted according to granting conditions set by the evaluator regarding a brand favored by that artist. Alternatively, at least one of the granting conditions or content of an NFT may be predetermined, and only the other may be set by the evaluator.

[0119] The above explanation provided 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 a target concept (for example, crypto assets primarily used for purchasing goods related to the target concept), or further based on the amount they hold.

[0120] The above description illustrates an example where the customer terminal 10 and the customer evaluation server 30 present the customer with their own score. However, instead of, or in addition to, the customer terminal 10 and the customer evaluation server 30 may present the customer with a grade as a fan of the target concept (including the provision of an NFT certifying 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 customers whose scores fall within a predetermined numerical range are of a grade associated with that numerical range (absolute evaluation). As a second example, when multiple customers are sorted in descending order of their scores, the customer evaluation server 30 determines that customers located within a predetermined rank range are of a grade associated with that rank range (relative evaluation).

[0121] The above description illustrates an example where the customer terminal 10 and the customer evaluation server 30 present the customer with their own score. However, instead of, or in addition to, the customer terminal 10 and the customer evaluation server 30 may present the customer with ranking information of scores across multiple customers.

[0122] The above explanation illustrates an example of adjusting the manner in which goods and services are provided to a customer according to that customer's score. However, the customer evaluation server 30 may adjust the manner of provision based on whether or not the customer possesses a specific NFT, instead of the score. For example, the customer evaluation server 30 may not grant the right to receive goods and services specified based on a provision request to customers who do not possess a specific NFT, and may only grant the right to receive such goods and services to customers who possess a specific NFT.

[0123] The above description shows an example in which the customer terminal 10 and the customer evaluation server 30 perform the service provision adjustment process shown in Figure 11. However, this process can be performed in various ways. As a first example, in step S430, the customer evaluation server 30 calculates the customer's score (or determines their grade) and transmits the score to an external device. Based on the score, the external device adjusts the manner in which goods or services are provided (S432). The external device may be, for example, a server in a ticketing system, an e-commerce system, or a content viewing system. As a second example, in step S410, the customer terminal 10 sends a request for provision to an external device. The external device sends a request for evaluation of the customer's score 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 identifying the NFTs held (S430) and calculating the score (S431), and sends the score to the external device. The external device then performs adjustment of the provision method of goods, etc. (S432).

[0124] The above description illustrates an example of calculating a customer's score triggered by a customer request. However, the customer evaluation server 30 may also calculate a customer's score in response to a request from someone other than a customer. For example, the customer evaluation server 30 may calculate a score for each customer (in this case, a customer is, for example, a member of the customer evaluation service provided by the customer evaluation server 30) in response to a request from a person (hereinafter referred to as "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 meet specific conditions. The customer evaluation server 30 may present the information of the extracted customers to the provider, or perform promotional processing on behalf of the provider for those customers (for example, automatically sending emails, recommending goods, etc. that the provider can provide). The specific conditions may include, for example, at least one of the following: • The score as a fan of a particular concept falls within a specified numerical range. • The distribution of fan scores for multiple target concepts resembles a specific distribution (e.g., the distribution of a particular individual). • By clustering each customer based on the distribution of their fan scores for multiple target concepts, it was determined that they belong to a specific cluster. As an example, the customer evaluation server 30 determines a baseline distribution based on the distribution of scores for one or more other concepts (e.g., concepts related to the specific concept) of customers who have a relatively high score as a fan of a particular concept. The customer evaluation server 30 then extracts customers who have a score distribution similar to the baseline distribution but have a relatively low score as a fan of the specific concept. These extracted customers are not currently fans of the specific concept, but they may be potential fans with similar preferences to fans of that concept. Therefore, by conducting marketing activities related to the specific concept (including promotional activities such as recommending goods related to the specific concept, providing coupons, granting special discount rights, displaying advertisements, sending information, providing samples, and offering free invitations) for these extracted customers, it becomes possible to efficiently acquire or cultivate new fans of that specific concept.

[0125] The above explanation illustrates an example where the evaluator defines the evaluation rules. The aforementioned provider does not need to be the same as the evaluator. In other words, the provider may request the customer evaluation server 30 to evaluate the customer based on evaluation rules defined by another person (the evaluator). Furthermore, when the evaluator edits the evaluation rules, the customer evaluation server 30 may provide the evaluator terminal 70 with evaluation rules defined by other evaluators so that they can reuse evaluation rules created by others (i.e., other evaluators).

[0126] Alternatively, the customer evaluation server 30 may perform various information processing tasks other than evaluating each customer's fan score, in response to requests from the provider. Specifically, the customer evaluation server 30 identifies the NFT ownership status of customers in response to requests from providers and collects the issuer ID (i.e., information identifying the issuer) for each NFT. The customer evaluation server 30 then analyzes the ownership status of NFTs issued by issuer IDs different from the provider ID (target issuer ID) for customers who own NFTs issued by the issuer ID specified by the provider (for example, the issuer ID of the provider itself or a party associated with the provider, hereinafter referred to as "provider ID"), and extracts the corresponding target issuer ID. The issuer corresponding to the target issuer ID may be a provider of goods related to a concept corresponding to the goods provided by the provider, or a concept targeting customers with the same tastes as that concept (i.e., complementary or alternative relationships), and therefore can be useful information for the provider. As a first example, the customer evaluation server 30 may notify the provider of information regarding the target publisher. This allows the provider to obtain information about potential collaborators or competitors and use it as a basis for their decision-making. 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 taken away by the target issuer (potential churn fans) and use this information in its marketing activities.

[0127] As another example, the customer evaluation server 30 may, in response to a request from the provider, analyze various types of information and extract information useful to the provider. The information to be analyzed includes at least one of the following: • The history of how a particular NFT has been traded between customers (i.e., C2C). • Transaction price of NFTs between customers • Real-time data of NFTs traded between customers • Data on how many NFTs are acquired from each issuer (sales analysis / competitor analysis) As a first example, the customer evaluation server 30 may notify the provider of information about customers who possessed NFTs issued by an issuer corresponding to the provider ID but transferred a number of such NFTs exceeding a threshold to others, or customers who transferred such NFTs to others within the most recent predetermined period. Such customers may be fans of the concepts corresponding to the goods, etc., provided by the provider, but have left or are beginning to leave. By notifying the provider of information about such customers, the provider can take measures to bring those customers back or prevent them from leaving (e.g., re-approaching them). As a second example, the customer evaluation server 30 may notify the provider of information about customers who have acquired a number of such NFTs exceeding a threshold within the most recent predetermined period, even though the server 30 possesses NFTs issued by an issuer corresponding to the provider ID. Such customers may be new fans of the concepts corresponding to the goods or services provided by the provider. By notifying the provider of information about such customers, the provider can take measures to cultivate those customers into more core fans. As a third example, the customer evaluation server 30 may notify the provider of information about customers who own collectible NFTs among the 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 information about such customers, the provider can ensure that they approach those customers when implementing a project (e.g., a concert tour) to issue new collectible NFTs, thereby encouraging their participation in the project. As a fourth example, the customer evaluation server 30 may notify the provider of information about customers who possess collectible NFTs among the NFTs issued by the issuer corresponding to the provider ID, but who have gaps in their collection of NFTs, and information about the missing NFTs. By notifying the provider of such customer information and information about the missing NFTs, the provider can promote the sale of the goods and services it offers by informing customers about the missing NFTs and how to obtain them. As a fifth example, the customer evaluation server 30 may notify the provider of the analysis results regarding the secondary market 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 market price of NFTs issued by the provider ID and notify the provider of alerts according to certain rules. By informing customers who own the NFTs of information regarding price increases of the NFTs issued by the provider, the provider can increase customer interest in acquiring NFTs that will be issued 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 (i.e., new customer acquisition) and secondary (secondary) trading of NFTs issued by the 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 primary, secondary, or overall trading. 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 ABC analysis. The provider can use the results of such analysis as a basis for decision-making in planning future NFTs to be issued.

[0128] The customer evaluation server 30 may refer to a customer's behavioral history or transaction history to estimate the customer's transaction characteristics or attributes. As a first example, the customer evaluation server 30 estimates what kind of transaction characteristics a customer with certain attributes (e.g., a housewife) has (e.g., when (e.g., day of the week, or time of day) they actively trade NFTs). As a second example, it estimates what kind of attributes a customer with a distinctive transaction history has (e.g., a customer who trades frequently is a speculative day trader). As a third example, it estimates what kind of attributes a customer with a distinctive behavioral history has (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.

[0129] Although embodiments of the present invention have been described in detail above, the scope of the present invention is not limited to the embodiments described above. Furthermore, the embodiments described above can be improved or modified in various ways without departing from the spirit of the present invention. In addition, the embodiments and modifications described above can be combined. [Explanation of Symbols]

[0130] 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

1. At least one computer, A means of identifying NFTs (Non-Fungible Tokens) held by a customer by querying a distributed ledger system. A means for calculating a 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 the multiple NFTs relating to the target concept. A program that makes it function as such.

2. The computer is made to function as a means for adjusting, in accordance with the score, at least one way in which a specific item, service, or content relating to the target concept is provided to the customer. The program according to claim 1.

3. The adjusting means treats customers with higher scores more favorably in the provision of specific goods, services, or content relating to the subject concept. The program according to claim 2.

4. The adjusting means ensures that customers with higher scores have a higher probability of winning in a lottery to determine whether or not they can be provided with specific goods, services, or content relating to the target concept. The program according to claim 2.

5. The adjusting means grants customers whose score is above a threshold the right to receive specific goods, services, or content relating to the subject concept. The program according to claim 2.

6. The means for calculating the above-mentioned means calculates the fan score of multiple customers who have requested the provision of specific goods, services, or content relating to the subject concept, The adjusting means grants customers who rank above a predetermined rank when sorted in descending order of their scores among the plurality of customers the right to receive specific goods, services, or content relating to the subject concept. The program according to claim 2.

7. The computer is made to function as a means for editing evaluation rules related to the target concept in response to instructions from an evaluator regarding the target concept. The program according to claim 1.

8. The computer is made to function as a means of presenting to an evaluator of the target concept information at least one piece of information regarding the conditions or content of multiple NFTs relating to the target concept. The program according to claim 7.

9. The aforementioned computer, Means for detecting actions that match the conditions for assigning NFTs related to the aforementioned target concept, To further function as a means of granting NFTs corresponding to the aforementioned granting conditions to customers whose actions are detected to match the aforementioned granting conditions, The program according to claim 1.

10. The means for detecting the aforementioned behavior detects, as behaviors that conform to the aforementioned conditions, the purchase, borrowing, use, possession, or lending of specific items, services, or content relating to the aforementioned target concept, or the dissemination of specific information relating to the aforementioned target concept. The program according to claim 9.

11. The computer is made to function as a means for setting at least one of the conditions or content of granting an NFT related to the target concept in response to instructions from an evaluator regarding the target concept. The program according to claim 9.

12. A means of identifying NFTs (Non-Fungible Tokens) held by a customer by querying a distributed ledger system, A means for calculating the customer's score as a fan of the target concept, based on the NFTs held by the customer and evaluation rules that define evaluation values ​​assigned to each of the multiple NFTs relating to the target concept. An information processing device equipped with the following.

13. At least one computer, The step of identifying the customer's NFTs (Non-Fungible Tokens) by querying a distributed ledger system. A step of calculating the customer's score as a fan of the target concept, based on the NFTs held by the customer and evaluation rules that define evaluation values ​​assigned to each of the multiple NFTs relating to the target concept, How to do it.

Images