Information processing method and information processing device

Abstract

To provide an information processing method and so on which can reduce processing burden in user review collecting processing and posting processing.SOLUTION: An identification code is associated with a provision object. Based on a block chain system for storing detailed information relating to the provision object in association with the identification code, a computer reads the detailed information associated with the identification code to output it. The computer also receives a review regarding the provision object and stores the received review in the block chain system in association with the identification code of the provision object.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information processing method and an information processing device. [Background technology]

[0002] Patent Document 1 discloses a technology for making user reviews posted by users about products and services that are the subject of e-commerce transactions available to other users. The technology disclosed in Patent Document 1 can provide useful information to users by creating summaries from multiple user reviews and providing them to users. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-101936 Summary of the Invention [Problem to be solved by the invention]

[0004] The technology disclosed in Patent Document 1 makes user reviews posted by users available to other users, and the user reviews are used as reference information when other users purchase the product or service, for example. Meanwhile, for businesses (e.g., manufacturers) that produce or manufacture products or services, reviews from users who have purchased the product or service are important for future product development. However, manufacturers and the like collect user reviews via, for example, postcards, email, or websites, which places a heavy burden on both the processing on the manufacturer that collects the user reviews and the operational burden on the users who post the user reviews. Therefore, there is room for improvement in the methods for collecting user reviews and providing them to manufacturers and the like.

[0005] The present invention has been made in consideration of the above circumstances, and its purpose is to provide an information processing method etc. that can reduce the processing burden in the process of collecting and posting user reviews. [Means for solving the problem]

[0006] An information processing method according to one aspect of the present invention is a process of, based on a blockchain system that associates an identification code with an object to be provided and stores detailed information about the object to be provided in association with the identification code, reading and outputting the detailed information corresponding to the identification code, accepting reviews about the object to be provided, storing the accepted reviews in the blockchain system in association with the identification code of the object to be provided, associating the reviews with the users who entered the reviews, and granting tokens for the reviews, in which a computer determines whether the content of the accepted reviews is appropriate, and switches between granting and not granting tokens for the reviews depending on the determination result. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to reduce the processing load in the process of collecting and posting user reviews. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a schematic diagram illustrating an example of the configuration of an information processing system. [Figure 2] FIG. 2 is a schematic diagram illustrating a configuration example of a node device. [Figure 3] FIG. 2 is a schematic diagram illustrating an example of the configuration of coffee information stored in a node device. [Figure 4] FIG. 2 is a block diagram showing an example of the configuration of a production management server. [Figure 5] FIG. 2 is a schematic diagram showing an example of the configuration of a production information DB. [Figure 6A] FIG. 2 is a schematic diagram showing an example of the configuration of a purification information DB. [Figure 6B] FIG. 1 is a schematic diagram showing an example of the configuration of a roasting information DB. [Figure 6C] FIG. 2 is a schematic diagram showing an example of the configuration of a sales information DB. [Figure 7A] 10A and 10B are schematic diagrams showing examples of screens for registering each piece of information in each server. [Figure 7B] 10A and 10B are schematic diagrams showing examples of screens for registering each piece of information in each server. [Figure 8A] 10A and 10B are schematic diagrams showing examples of screens for registering each piece of information in each server. [Figure 8B] 10A and 10B are schematic diagrams showing examples of screens for registering each piece of information in each server. [Figure 9] FIG. 2 is a block diagram showing an example of the configuration of a review management server and a poster terminal. [Figure 10A] FIG. 2 is a schematic diagram showing an example of the configuration of a product information DB. [Figure 10B] FIG. 2 is a schematic diagram illustrating an example of the configuration of a review DB. [Figure 10C] FIG. 2 is a schematic diagram showing an example of the configuration of a viewing authority DB. [Figure 11] 10 is a flowchart illustrating an example of a review posting process procedure. [Figure 12A] FIG. 10 is an explanatory diagram of a review posting process. [Figure 12B] FIG. 10 is a schematic diagram showing an example of a review input screen. [Figure 13] 10 is a flowchart showing an example of a review viewing process procedure. [Figure 14A] FIG. 10 is a schematic diagram showing an example of a screen. [Figure 14B] FIG. 10 is a schematic diagram showing an example of a screen. [Figure 14C] FIG. 10 is a schematic diagram showing an example of a screen. [Figure 15] FIG. 10 is a schematic diagram illustrating an example of the configuration of a block for token management. [Figure 16] 10 is a flowchart showing an example of a review posting process procedure according to the second embodiment. [Figure 17] FIG. 10 is a schematic diagram showing an example of a screen. [Figure 18] 10 is a flowchart illustrating an example of a procedure for providing a token grant history. [Figure 19] FIG. 10 is a schematic diagram showing an example of a screen. [Figure 20] 11 is a flowchart showing an example of a review posting process procedure according to the third embodiment. [Figure 21] FIG. 11 is a schematic diagram showing an example of a review input screen according to the third embodiment. [Figure 22] FIG. 10 is a schematic diagram showing a modified example of the review input screen. [Figure 23] 13 is a flowchart showing an example of a review posting process procedure according to the fourth embodiment. [Figure 24] 13 is a flowchart showing an example of a review posting process procedure according to the fifth embodiment. [Figure 25A] FIG. 10 is a schematic diagram showing an example of a screen. [Figure 25B] FIG. 10 is a schematic diagram showing an example of a screen. [Figure 26] FIG. 10 is a schematic diagram showing an example of a digital ID issuance history screen. [Figure 27] FIG. 22 is a schematic diagram showing an example of the configuration of a review DB according to the sixth embodiment. [Figure 28] 10 is a flowchart showing an example of a review NFT issuance processing procedure. [Figure 29A] FIG. 20 is a schematic diagram showing an example of the configuration of a production information DB according to the seventh embodiment. [Figure 29B] FIG. 13 is a schematic diagram showing an example of the configuration of a purification information DB according to the seventh embodiment. [Figure 29C] FIG. 13 is a schematic diagram showing an example of the configuration of a roasting information DB according to a seventh embodiment. [Figure 29D] FIG. 2 is a schematic diagram showing an example of the configuration of a sales information DB. [Figure 30] FIG. 20 is a schematic diagram showing an example of a review input screen according to the seventh embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] An information processing method and an information processing device according to the present disclosure will be described in detail below with reference to drawings illustrating embodiments. In the following embodiments, an information processing system for managing reviews of coffee posted by users who have purchased coffee is described. Note that coffee here includes coffee beverages, roasted coffee beans, and unroasted coffee beans. The technology of the present disclosure is not limited to coffee, but can be applied to information processing systems for managing reviews of alcoholic beverages such as sake, beer, wine, and whiskey; teas such as black tea, Japanese tea, and Chinese tea; sweets such as chocolate; luxury goods such as tobacco; and various foods sold in stores and on e-commerce sites. The technology of the present disclosure can also be applied to information processing systems for managing reviews of services provided at, for example, accommodations, restaurants, entertainment facilities such as amusement parks, barber shops and beauty salons, and relaxation facilities such as massage parlors. In other words, the technology of the present disclosure can be applied to information processing systems for managing reviews of products and services (offerings) that involve monetary transactions.

[0010] (Embodiment 1) An information processing system for managing coffee reviews will be described. In addition to reviews posted by coffee purchasers, the information processing system of this embodiment also manages information regarding the work performed by businesses (e.g., producers, refiners, roasters, and retailers) at each stage of coffee production, from coffee production to sales (delivery). FIG. 1 is a schematic diagram showing an example configuration of an information processing system. The information processing system of this embodiment manages various types of coffee-related information using a blockchain system, a type of distributed ledger technology. The blockchain system includes multiple node devices 10 connected to a peer-to-peer (P2P) network N1, and the multiple node devices 10 share various types of coffee-related information in a distributed manner. Each node device 10 is connected to a production management server 20, a refinement management server 30, a roasting management server 40, a sales management server 50, a review management server 60, and the like. The configuration of the blockchain system in this embodiment is not particularly limited, and public, consortium, private, or other types of blockchain systems can be used. The information processing system of this embodiment may also be configured using IPFS (InterPlanetary File System) or distributed cloud computing.

[0011] The production management server 20 is installed, for example, at the business establishment or office of a coffee bean producer, and stores and manages information related to the coffee bean production work performed by the producer in a production information DB 22a (see FIG. 4). The production management server 20 also outputs the information related to the production work to the blockchain system for storage. The refining management server 30 is installed, for example, at the business establishment or office of a coffee bean refiner, and stores and manages information related to the refining work performed by the refiner in a refining information DB (see FIG. 6A). The refining management server 30 also outputs the information related to the refining work to the blockchain system for storage. The roasting management server 40 is installed, for example, at the business establishment or office of a business operator that roasts the refined coffee beans, and stores and manages information related to the roasting work performed by the roaster in a roasting information DB (see FIG. 6B). The roasting management server 40 also outputs the information related to the roasting work to the blockchain system for storage. The sales management server 50 is installed in the business establishment or office of a vendor selling coffee beverages or coffee beans, and stores and manages information related to the sales operations performed by the vendor in a sales information DB (see FIG. 6C). The sales management server 50 also outputs and stores information related to the sales operations in the blockchain system. While the production management server 20, refinement management server 30, roasting management server 40, and sales management server 50 are distinguished for convenience, if a single vendor performs multiple processes, multiple servers may be integrated into one. That is, each server may be a server of a vendor at any stage from the coffee bean production stage to the coffee product sales stage. For example, if the roaster and vendor are the same vendor, the roasting management server 40 and sales management server 50 may be configured as a single server. If there are multiple vendors at each stage, multiple servers 20, 30, 40, and 50 may be installed.

[0012] The review management server 60 is installed and used, for example, in the business establishment or office of a company that collects and manages reviews on various products. The information processing system of this embodiment includes a poster terminal 70 of a poster who posts a review on a purchased coffee, and a viewer terminal 80 that issues a viewing request to the review management server 60 and receives information (reviews) provided from the review management server 60 in response to the viewing request. The review management server 60, the poster terminal 70, and the viewer terminal 80 are connected to each other so as to be able to communicate with each other via a network N2 such as the Internet.

[0013] When the review management server 60 acquires a review from the poster terminal 70, it associates the acquired review information with the poster and stores and manages it in the review DB 62b (see FIG. 9 ). The review management server 60 also accesses the blockchain system and stores the acquired review information in the blockchain system. When the review management server 60 receives a request from a viewer terminal 80 to view a review of a coffee (product), it accesses the blockchain system, acquires review information about the coffee, and provides it to the viewer terminal 80. In this embodiment, the poster of the review is a user who has purchased and consumed a coffee drink or coffee beans sold at various stores, e-commerce sites, etc. The viewer of the review is, for example, a person in charge of a store selling the coffee drink or coffee beans or a beverage manufacturer. Note that the viewer of the review is not limited to retailers such as stores and beverage manufacturers, but may also be a person in charge of a producer, refiner, or roaster.

[0014] In the blockchain system of this embodiment, multiple node devices 10 store information provided by each server: production management server 20, refinement management server 30, roasting management server 40, sales management server 50, and review management server 60. The blockchain system stores information about the work performed by each trader when the information is input via each server. The blockchain system can also provide the information stored in multiple node devices 10 to each server.

[0015] FIG. 2 is a schematic diagram showing an example configuration of node device 10. Node device 10 can be configured as a computer or a computer system. Node device 10 is installed and used in the business establishments or offices of producers, refiners, roasters, distributors, and review management companies. Node device 10 may function as production management server 20, refinement management server 30, roasting management server 40, sales management server 50, or review management server 60.

[0016] Node device 10 includes a communication unit 11, an information generation unit 12, an information recording unit 13, an information reference unit 14, and a database 15. Communication unit 11 has a function for communicating with other node devices 10 connected to network N1. Communication unit 11 also has a function for communicating with production management server 20, refinement management server 30, roasting management server 40, sales management server 50, and review management server 60.

[0017] The database 15 can be configured with a non-volatile semiconductor memory or a hard disk, etc., whose recorded contents can be rewritten. The database 15 records a node list 16 and coffee information 17. The node list 16 registers the IP address and electronic certificate of a node device 10 that has been properly registered in the blockchain system, in association with identification information that identifies the node device 10. The electronic certificate records the public key and electronic signature of each node device 10. When a new node device 10 is properly registered, the registration is reflected in the node list 16.

[0018] FIG. 3 is a schematic diagram showing an example of the configuration of coffee information 17 stored in node device 10. As shown in FIG. 3, coffee information 17 includes multiple blocks 170. The multiple blocks 170 are linked in a chain, forming information with a so-called blockchain structure. FIG. 3 shows an example in which nth and n+1th blocks 170 are linked together. Each block 170 includes a timestamp 171, a hash value 172 of the previous block 170, and recorded information 173. The timestamp 171 is information indicating the date and time when the block 170 was generated. The hash value 172 is a value generated from the previous block 170 based on a preset hash function. The recorded information 173 is the main part of the information to be registered in block 170. The recorded information 173 includes information about the details of each task performed by each vendor from the coffee production stage to the sales stage. For example, in the case of production information registered by a producer, as shown in the lower left of FIG. 3, recorded information 173 includes a coffee bean ID, which is identification information assigned to the coffee beans, information about the coffee bean-producing country, producing region, and producer, as well as the harvest date, etc. Furthermore, in the case of refining information registered by a refiner, as shown in the lower right of FIG. 3, recorded information 173 includes a refining process ID, which is identification information for the refining process performed by the refiner, the coffee bean ID of the coffee beans to be refined, information indicating the details of the refining process, the refining date, etc. In this way, block 170 records information about various operations performed on coffee beans from the coffee production stage to the sales stage, for example, in association with a coffee bean ID (identification information for identifying the product). Furthermore, block 170 records information about reviews by users who purchased coffee, for example, in association with the product ID (identification information, identification code) of the coffee sold by a retailer.

[0019] The information generation unit 12 generates a block 170 to be registered in the blockchain system using information obtained from the production management server 20, the refinement management server 30, the roasting management server 40, the sales management server 50, and the review management server 60 via the communication unit 11. The information regarding the work performed by each trader and the review information described above are stored in the record information 173 of the block 170, as well as in the production information DB 22a of the production management server 20, the refinement information DB of the refinement management server 30, the roasting information DB of the roasting management server 40, the sales information DB of the sales management server 50, and the review DB 62b of the review management server 60, and only the hash value 172 is stored in the block 170. Even in this configuration, it is possible to verify whether or not the information has been tampered with based on the hash value 172.

[0020] The information recording unit 13 determines whether a block 170 newly generated by another node device 10 satisfies a predetermined consensus rule in the blockchain system. The information recording unit 13 records the block 170 that satisfies the predetermined consensus rule in the blockchain system. In this case, the information recording unit 13 adds the new block to the end of the tandemly connected blocks 170. In a blockchain system, the reliability of information exchanged between participants is guaranteed by a consensus process within the network formed by all participants, and the integrity of the blockchain is maintained by preventing fraud such as tampering throughout the system. The consensus process can use a consensus algorithm such as proof of work or proof of stake.

[0021] When the information reference unit 14 receives a request to reference the contents stored in the blockchain system from the production management server 20, the refinement management server 30, the roasting management server 40, the sales management server 50, and the review management server 60 via the communication unit 11, it reads the recorded information 173 from the block 170 corresponding to the request and transmits the read recorded information 173 to the requestor. Note that if the contents of the recorded information 173 are stored in the production information DB 22a of the production management server 20, the refinement information DB of the refinement management server 30, the roasting information DB of the roasting management server 40, the sales information DB of the sales management server 50, or the review DB 62b of the review management server 60, the information reference unit 14 reads each piece of information from each DB and transmits it to the requestor. This allows the information registered in the blockchain system to be provided to each server 20, 30, 40, 50, and 60.

[0022] FIG. 4 is a block diagram showing an example configuration of the production management server 20. The production management server 20 is a personal computer, a server computer, or the like. The production management server 20 includes a control unit 21, a memory unit 22, a communication unit 23, an operation unit 24, a display unit 25, and the like, which are interconnected via a bus. The control unit 21 includes, for example, a central processing unit (CPU), a read-only memory (ROM), and a random access memory (RAM). The CPU of the control unit 21 controls the operation of the above-mentioned hardware by loading a control program 22P stored in advance in the ROM or the memory unit 22 into the RAM and executing the program, thereby executing the processing to be performed by the production management server 20. Note that although the control unit 21 is configured to include a CPU, a ROM, and a RAM, it may also be any arithmetic and control device including one or more CPUs, a multi-core CPU, a graphics processing unit (GPU), or the like.

[0023] The storage unit 22 is configured with a flash memory, a hard disk, a solid-state drive (SSD), a semiconductor memory, or the like. The storage unit 22 stores a control program 22P executed by the control unit 21, various data required for executing the control program 22P, and the like. The programs stored in the storage unit 22 may be written to the storage unit 22, for example, during the manufacturing stage of the production management server 20, or may be provided by a non-transitory recording medium 20M that readably stores the programs. The recording medium 20M is, for example, a portable memory such as a CD-ROM, a USB memory, a Secure Digital (SD) memory, or a microSD card. In this case, the control unit 21 can read various programs from the recording medium 20M using a reading device (not shown) and install the read programs in the storage unit 22. The programs stored in the storage unit 22 may also be provided by communication via the communication unit 23. In this case, the control unit 21 can acquire various programs through the communication unit 23 and install the acquired programs in the storage unit 22.

[0024] The communication unit 23 includes a communication interface for communicating with the node device 10 via the network N1. When the communication unit 23 receives various information via the network N1, it outputs the received information to the control unit 21. The control unit 21 executes appropriate processing based on the information received via the communication unit 23. When information to be transmitted to a desired destination via the network N1 is input from the control unit 21 to the communication unit 23, the communication unit 23 transmits the input information to the destination via the network N1. The communication unit 23 also includes a communication interface for connecting to the network N2.

[0025] The operation unit 24 has an input interface such as a keyboard or a mouse, accepts operation inputs from a user using the production control server 20, and sends a control signal corresponding to the operation content to the control unit 21. The display unit 25 is a liquid crystal display, an organic EL display, or the like, and displays various information in accordance with instructions from the control unit 21. The operation unit 24 and the display unit 25 may be integrated into a touch panel. Note that in this embodiment, the production control server 20 is configured to include the operation unit 24 and the display unit 25, but the operation unit 24 and the display unit 25 are not essential, and the production control server 20 may be configured to accept operations via an externally connected computer and output information to be displayed to an external display device.

[0026] When production management server 20 receives input of information regarding coffee bean production work performed by producers from operation unit 24, it stores the received information in production information DB 22a. Alternatively, production management server 20 may output the received information to node device 10 and store it in the blockchain system. FIG. 5 is a schematic diagram showing an example configuration of production information DB 22a. Production information DB 22a stores information regarding coffee bean production work performed by producers. The production information DB 22a shown in FIG. 5 includes a coffee bean ID column, a producing country column, a producing region column, a producer column, a cultivation method column, a harvest date column, a weather column on the harvest date, etc., and stores each piece of information regarding the producing country, producing region, producer column, cultivation method, harvest date, and weather on the harvest date in association with identification information (coffee bean ID) assigned to the harvested coffee beans. The coffee bean ID is, for example, an ID assigned to coffee beans harvested on the same day at the same farm.

[0027] The refining management server 30, roasting management server 40, and sales management server 50 each have the same configuration as the production management server 20, so a description of their configurations will be omitted. When the refining management server 30 receives input of information related to the refining work performed by the refiner from the operation unit, it stores the received information in the refining information DB. The refining management server 30 also outputs the received information to the node device 10, which stores it in the blockchain system. When the roasting management server 40 receives input of information related to the roasting work performed by the roaster from the operation unit, it stores the received information in the roasting information DB. The roasting management server 40 also outputs the received information to the node device 10, which stores it in the blockchain system. When the sales management server 50 receives input of information related to the sales work performed by the seller from the operation unit, it stores the received information in the sales information DB. The sales management server 50 also outputs the received information to the node device 10, which stores it in the blockchain system.

[0028] Fig. 6A is a schematic diagram showing an example of the configuration of a refining information DB, Fig. 6B is a schematic diagram showing an example of the configuration of a roasting information DB, and Fig. 6C is a schematic diagram showing an example of the configuration of a sales information DB. The refining information DB stores information about the refining work of coffee beans performed by refiners. The refining information DB shown in Fig. 6A includes a refining process ID column, a coffee bean ID column, a refiner column, a refining process content column, a refining date column, a weather column on the refining day, etc., and stores each piece of information about the coffee bean ID of the refined coffee beans, the refiner, the refining process content, the refining date, and the weather on the refining day in association with identification information (refining process ID) of the refining process performed on the coffee beans.

[0029] The roasting information DB stores information about the roasting of coffee beans performed by roasters. The roasting information DB shown in Fig. 6B includes a roasting process ID column, a coffee bean ID column, a refining process ID column, a roaster column, a roasting process content column, a roasting date column, a roasting date weather column, etc., and stores each piece of information, such as the coffee bean ID of the roasted coffee beans, the refining process ID of the refining process performed on the coffee beans, the roaster, the roasting process content, the roasting date, and the weather on the roasting date, in association with the identification information (roasting process ID) of the roasting process performed on the coffee beans.

[0030] The sales information DB stores information about coffee products sold by retailers. The sales information DB shown in Fig. 6C includes a store ID column, a product ID column, a product information column, a retailer column, a coffee bean ID column, a refining process ID column, a roasting process ID column, etc., and stores product information such as the product's menu name and price, the retailer, the coffee bean ID of the coffee beans used, the refining process ID of the refining process performed on the coffee beans, and the roasting process ID of the roasting process, in association with identification information (store ID) assigned to the retailer and identification information (product ID) assigned to the coffee product.

[0031] 7A to 8B are schematic diagrams showing example screens for registering various pieces of information in each server 20, 30, 40, and 50. Fig. 7A shows an example screen for inputting production information, Fig. 7B shows an example screen for inputting refining information, Fig. 8A shows an example screen for inputting roasting information, and Fig. 8B shows an example screen for inputting sales information. Each screen shown in Fig. 7A to 8B is displayed on the display unit of each server 20, 30, 40, and 50, for example, by each server 20, 30, 40, and 50 executing a predetermined application.

[0032] The production information input screen shown in FIG. 7A has input fields for inputting the coffee bean ID, coffee bean-producing country, producing region, producer and cultivation method information, harvest date, and weather on the harvest date. Each input field may be configured so that the information is input directly, or so that the information is input by selecting an arbitrary one from multiple options displayed. When the information is input via the production information input screen and the registration button is operated, the production management server 20 stores the input production information in the production information DB 22a. The production management server 20 also outputs the production information to the node device 10 and instructs the node device 10 to store the production information in the blockchain system. The node device 10 generates a block 170 using the production information acquired from the production management server 20, and records the generated block 170 in the blockchain system if it satisfies predetermined agreement rules.

[0033] The refining information input screen shown in FIG. 7B has input fields for inputting a refining process ID indicating the refining process performed on the coffee beans, a coffee bean ID, information about the refining company and refining process details, the refining date, and the weather on the refining date. Each input field may be configured so that the information is input directly, or may be configured so that the information is input by selecting an arbitrary one from multiple options displayed. When the information is input via the refining information input screen and the registration button is operated, the refining management server 30 stores the input refining information in the refining information DB. Furthermore, the refining management server 30 outputs the refining information to the node device 10 and instructs it to store the refining information in the blockchain system. The node device 10 generates a block 170 using the refining information acquired from the refining management server 30, and records the generated block 170 in the blockchain system if it satisfies predetermined consensus rules.

[0034] The roasting information input screen shown in FIG. 8A has input fields for inputting a roasting process ID indicating the roasting process performed on the coffee beans, a coffee bean ID, a refining process ID for the refining process performed on the coffee beans, information about the roaster and roasting process details, the roasting date, and the weather on the roasting date. Each input field may be configured so that the information is input directly, or so that the information is input by selecting an arbitrary one from multiple options displayed. When the information is input via the roasting information input screen and the register button is operated, the roasting management server 40 stores the input roasting information in the roasting information DB. The roasting management server 40 also outputs the roasting information to the node device 10 and instructs it to store the roasting information in the blockchain system. The node device 10 generates a block 170 using the roasting information obtained from the roasting management server 40, and records the generated block 170 in the blockchain system if it satisfies predetermined consensus rules.

[0035] The sales information input screen shown in FIG. 8B has input fields for inputting the store ID of the store selling the coffee drink or coffee beans (product), the product ID assigned to the coffee drink or coffee beans (product), product information including the menu name and price, the product vendor, the coffee bean ID of the coffee beans used in the product, the refining process ID, and the roasting process ID. Each input field may be configured so that the information is input directly, or so that the information is input by selecting an arbitrary one from multiple options displayed. The product ID is, for example, an ID assigned to each product (menu item) for sale. Note that the product ID may be an ID that can identify a specific product sold by a specific vendor or store, in which case, inputting the store ID is not necessary. When each piece of information is input via the sales information input screen and the registration button is operated, the sales management server 50 stores the input sales information in the sales information DB. The sales management server 50 also outputs the sales information to the node device 10 and instructs it to store the sales information in the blockchain system. The node device 10 generates a block 170 using the sales information acquired from the sales management server 50, and records the generated block 170 in the blockchain system if the generated block 170 satisfies a predetermined agreement rule.

[0036] FIG. 9 is a block diagram showing an example configuration of the review management server 60 and the poster terminal 70. The review management server 60 is an information processing device capable of various information processing and information transmission / reception, such as a server computer or a personal computer. For simplicity's sake, the review management server 60 is described as a single device in this embodiment. However, multiple review management servers 60 may be provided for distributed processing, implemented by multiple virtual machines on a single server, or implemented using a cloud server. The review management server 60 also has web server functionality and hosts a website S that accepts coffee reviews via a network N2 and a website S that accepts review viewing requests via the network N2. When the review management server 60 accepts a coffee review via the website S, it stores the accepted review in the review DB 62b and then outputs it to the blockchain system for recording. When the review management server 60 accepts a review viewing request via the website S, it extracts the requested review from the blockchain system and transmits it to the requesting device.

[0037] The review management server 60 includes a control unit 61, a storage unit 62, a communication unit 63, an operation unit 64, a display unit 65, and the like, all of which are interconnected via a bus. The control unit 61, storage unit 62, communication unit 63, operation unit 64, and display unit 65 of the review management server 60 are similar in configuration to the control unit 21, storage unit 22, communication unit 23, operation unit 24, and display unit 25 of the production management server 20, and therefore detailed description thereof will be omitted. The storage unit 62 stores a website S, a product information DB 62a, a review DB 62b, and a viewing authority DB 62c in addition to a control program 62P. In the review management server 60, the programs stored in the storage unit 62 may be written to the storage unit 62 during the manufacturing stage of the review management server 60, provided from a non-transitory recording medium 60M on which the programs are readably stored, or provided via communication via the communication unit 63.

[0038] Fig. 10A is a schematic diagram showing an example of the configuration of the product information DB 62a, Fig. 10B is a schematic diagram showing an example of the configuration of the review DB 62b, and Fig. 10C is a schematic diagram showing an example of the configuration of the viewing authority DB 62c. The product information DB 62a stores information about products that are the subject of reviews managed by the review management server 60. The product information DB 62a shown in Fig. 10A includes a product ID column, a coffee bean ID column, a refining process ID column, a roasting process ID column, a distributor column, a store ID column, etc., and stores, in association with the product ID of the product, information such as the coffee bean ID of the coffee beans used in the product, the refining process ID of the refining process performed on the coffee beans, the roasting process ID of the roasting process, and the distributor and store ID of the product.

[0039] The review DB 62b stores information about reviews of products posted by posters. The review DB 62b shown in Fig. 10B includes a product ID column, a retailer column, a store ID column, a poster ID column, an attribute information column, a review content column, etc., and stores identification information assigned to posters (poster IDs), poster attribute information, and reviews by posters, in association with a product ID for identifying the product being reviewed, retailer information, and store ID.

[0040] The viewing authority DB 62c stores information about viewers who view reviews stored in the blockchain system and information about the scope of reviews that each viewer can view. The viewing authority DB 62c shown in FIG. 10C includes a viewer ID column, a viewer information column, a viewing authority scope column, etc., and stores viewer information and information indicating the scope of viewing authority in association with identification information assigned to the viewer (viewer ID). The viewer information includes information about the viewer's industry (information indicating the producer, refiner, roaster, or seller) and the name of each seller. The viewer information may also include a password required for the viewer to view reviews. The scope of viewing authority is information for identifying products whose reviews the viewer can view. If the viewer is a producer, the scope of viewing authority is determined by the coffee bean ID of the coffee beans produced by the producer. If the viewer is a refiner, the scope of viewing authority is determined by the refining process ID of the refining process performed by the refiner. If the viewer is a roaster, the scope of viewing authority is determined by the roasting process ID of the roasting process performed by the roaster. Furthermore, if the viewer is a seller, the scope of the viewing authority is determined by the product ID of the product sold by the seller and the store ID of the seller's store. Viewers whose information is stored in the viewing authority DB 62c are businesses with legitimate viewing authority, such as businesses that have paid a fee for review viewing or businesses that have registered as viewers for review viewing. The fee for review viewing may be a fixed fee, a fee based on the number of products to be viewed, or a fee based on the number of reviews viewed.

[0041] The poster terminal 70 is a terminal of a poster who posts a coffee review via the website S, and may be a smartphone, tablet terminal, personal computer, or the like. In this embodiment, the poster terminal 70 is configured to access the website S using a web browser 72AP, but may also be configured to access the website S by executing a predetermined application program, for example. The poster terminal 70 in this embodiment accesses the website S made public by the review management server 60 in accordance with instructions from the poster, and performs a review posting process via the website S.

[0042] The poster terminal 70 includes a control unit 71, a memory unit 72, a communication unit 73, an operation unit 74, a display unit 75, a camera 76, etc., and these units are interconnected via a bus. The control unit 71, the memory unit 72, the communication unit 73, the operation unit 74, and the display unit 75 of the poster terminal 70 have the same configurations as the control unit 21, the memory unit 22, the communication unit 23, the operation unit 24, and the display unit 25 of the production management server 20, so detailed description will be omitted. The memory unit 72 stores a web browser 72AP in addition to a control program 72P. The camera 76 is an imaging device that takes pictures in accordance with instructions from the control unit 71 and sends the acquired captured images (image data) to the memory unit 72 for storage. The camera 76 may be built into the poster terminal 70 or may be externally attached to the poster terminal 70.

[0043] The following describes the processing performed by the poster terminal 70 and the review management server 60 when a poster posts a review about a product using the poster terminal 70. Fig. 11 is a flowchart showing an example of the review posting processing procedure, Fig. 12A is an explanatory diagram of the review posting processing, and Fig. 12B is a schematic diagram showing an example of a review input screen. In Fig. 11, the processing performed by the poster terminal 70 is shown on the left, and the processing performed by the review management server 60 is shown on the right.

[0044] In the information processing system of this embodiment, as shown in FIG. 12A , a two-dimensional code assigned to a product is printed or affixed to the product's package. In the example shown in FIG. 12A , a QR code (registered trademark) associated with the product is printed on the product package, but a one-dimensional code such as a barcode may also be printed. The product package is, for example, a paper cup for a coffee drink or a bag containing coffee beans. The two-dimensional code includes, for example, access information (e.g., a URL) for accessing website S and obtaining a review input screen, and product information including the product ID, distributor information, and store ID of the product. These pieces of information are pre-associated with the product (the object of provision). When a user wishes to post a review of a product they have purchased, they photograph the product's two-dimensional code using the camera 76 of the poster terminal 70 and read the code information from the two-dimensional code. It is assumed that the poster terminal 70 has a code reader app pre-stored in the storage unit 72 for reading the code information from the two-dimensional code photographed by the camera 76.

[0045] When the control unit 71 of the poster terminal 70 receives an instruction to read a two-dimensional code from the poster via the operation unit 74, it activates the camera 76 to take a picture and reads code information from the image of the two-dimensional code (S11).The control unit 71 then accesses the review management server 60 (website S) based on the access information included in the read code information and requests a review input screen (S12).In addition to the access information, the code information includes product information such as a product ID, retailer information, and store ID, and the control unit 71 transmits the product information to the review management server 60 and requests a review input screen corresponding to the product information.

[0046] When the control unit 61 of the review management server 60 receives a request for a review input screen from the poster terminal 70, it extracts information about the product corresponding to the product information acquired from the poster terminal 70 from the various pieces of information stored in the blockchain system (S13). Specifically, the control unit 61 identifies the coffee bean ID, refining process ID, and roasting process ID corresponding to the product from the stored contents of the product information DB 62a, based on the product information (product ID, retailer information, and store ID) acquired from the poster terminal 70. The control unit 61 then queries the production management server 20 for information about the coffee beans associated with the identified coffee bean ID (e.g., country of origin, producer), and acquires this information from the production management server 20. The control unit 61 also queries the refining management server 30 for refining information (information about the refining process and the refiner) corresponding to the identified refining process ID, and acquires this information from the refining management server 30. The control unit 61 also queries the roasting management server 40 for roasting information (information about the roasting process and the roaster) corresponding to the identified roasting process ID, and acquires this information from the roasting management server 40. The control unit 61 also queries the sales management server 50 for store information corresponding to the store ID included in the acquired product information, and acquires it from the sales management server 50. The control unit 61 also queries the sales management server 50 for a menu name corresponding to the product ID included in the product information, and acquires it from the sales management server 50. Note that the control unit 61 may request the node device 10 to acquire each piece of information, and acquire each piece of information that the node device 10 reads from the blockchain system.

[0047] The control unit 61 generates a review input screen based on the various pieces of information acquired as described above (S14). Specifically, the control unit 61 generates a review input screen that displays the product ID acquired from the poster terminal 70, the menu name acquired from the sales management server 50, information on the country of origin and producer acquired from the production management server 20, information on the refining process and refiner acquired from the refining management server 30, information on the roasting process and roaster acquired from the roasting management server 40, information on the retailer acquired from the sales management server 50, and information on the retailer acquired from the poster terminal 70. The control unit 61 also generates a review input screen that has the poster ID, age, gender, and input fields for entering a review. The control unit 61 transmits the generated review input screen to the poster terminal 70 that made the request (S15). As a result, the control unit 61 operates as an output unit that reads detailed information about the product from the blockchain system and outputs it to the poster terminal 70. The control unit 71 of the poster terminal 70 receives the review input screen sent by the review management server 60, and displays the review input screen as shown in FIG. 12B on the display unit 75 (S16).

[0048] The review input screen shown in FIG. 12B displays an image of the product being reviewed, the product ID, the product name (menu name), the country of origin and producer of the coffee beans, the refining process and refiner, the roasting process and roaster, the retailer, and information about the retailer. Each piece of information on the review input screen may have a link for obtaining more detailed information. When a link is selected, the poster terminal 70 obtains and displays the detailed information for the selected link from each server 20, 30, 40, or 50 via the review management server 60. The review input screen also has input fields for inputting the poster ID assigned to the poster posting the review, the poster's age and gender, the review, etc. Each input field may be configured to allow each piece of information to be entered directly, or may be configured to allow any item to be selected via a pull-down menu displaying multiple options. When displaying the review input screen, the control unit 71 of the poster terminal 70 may photograph the poster's face with the camera 76, determine the poster's age and gender based on the acquired facial image, and display the determined age and gender in each input field.

[0049] The control unit 71 of the poster terminal 70 accepts each piece of information and review via each input field on the review input screen and displays each accepted piece of information and review in the corresponding input field (S17). The control unit 71 determines whether the submit button on the review input screen has been operated (S18). If the control unit 71 determines that the submit button has not been operated (S18: NO), the control unit 71 returns to the processing of step S17 and repeats accepting each piece of information via the review input screen. If the control unit 71 determines that the submit button has been operated (S18: YES), the control unit 71 transmits review information including the information entered in each input field and product information identifying the product being reviewed (e.g., product ID, retailer information, store ID) to the review management server 60 (S19).

[0050] The control unit 61 (reception unit) of the review management server 60 receives the review information transmitted by the poster terminal 70 and stores the received review information in the review DB 62b (S20). Here, the control unit 61 associates the poster ID, attribute information such as age and gender, and the review in the review DB 62b with the product information (product ID, retailer information, store ID) contained in the received review information. The control unit 61 also stores the review information in the blockchain system (S21). Here, the control unit 61 outputs the review information to the node device 10 and instructs the node device 10 to store the review information in the blockchain system. The node device 10 generates a block 170 using the review information acquired from the review management server 60, and records the generated block 170 in the blockchain system if the generated block 170 satisfies a predetermined agreement rule. As a result, the review information input at the poster terminal 70 is associated with the product information and recorded in the blockchain system by the node device 10. In addition, the control unit 61 may be configured to store the review information only in the blockchain system without storing it in the review DB 62b, or may be configured to store the review information in the review DB 62b and store only the hash value 172 in the block 170 corresponding to the review information in the blockchain system.

[0051] The reviews entered on the review entry screen may include not only thoughts and ratings about the product, but also thoughts and ratings about vendors at each stage from the production stage to the sales stage. The review entry screen is not limited to the configuration shown in Fig. 12B, and may have a configuration that includes, for example, an input field for rating the product on a five-point scale.

[0052] Next, the viewer terminal 80 will be described. The viewer terminal 80 has a configuration similar to that of the contributor terminal 70, and therefore a description of the configuration will be omitted. The viewer terminal 80 of this embodiment accesses the website S published by the review management server 60 in accordance with instructions from the viewer, and views reviews via the website S. Note that the viewer terminal 80 may also be configured to access the website S using a web browser, or may be configured to access the website S by executing a predetermined application program.

[0053] The following describes the processing performed by the viewer terminal 80 and the review management server 60 when a viewer uses the viewer terminal 80 to view reviews stored in the blockchain system. Fig. 13 is a flowchart showing an example of the review viewing processing procedure, and Figs. 14A to 14C are schematic diagrams showing example screens. In Fig. 13, the processing performed by the viewer terminal 80 is shown on the left, and the processing performed by the review management server 60 is shown on the right.

[0054] In the information processing system of this embodiment, when a viewer wishes to view reviews stored in the blockchain system, the viewer uses the viewer terminal 80 to access the website S of the review management server 60 and obtain a review viewing screen. The control unit of the viewer terminal 80 launches a web browser in accordance with instructions from the viewer via the operation unit, accesses the review management server 60 (website S), obtains a review viewing screen such as that shown in FIG. 14A, and displays it on the display unit. The review viewing screen shown in FIG. 14A is a login screen having input fields for the viewer's ID and password required to view reviews stored in the blockchain system. The viewer requests to view the reviews by entering their own ID and password in the input fields and operating the OK button.

[0055] The control unit of the viewer terminal 80 determines whether a review viewing request has been accepted, depending on whether a viewer ID and password have been entered and the OK button has been operated on the review viewing screen shown in Fig. 14A (S31). If it is determined that a review viewing request has not been accepted (S31: NO), the control unit waits until it is accepted. If it is determined that a review viewing request has been accepted (S31: YES), the control unit transmits the entered viewer information (ID and password) to the review management server 60 (S32).

[0056] The control unit 61 of the review management server 60 authenticates whether the viewer is a user authorized to view reviews based on the viewer information received from the viewer terminal 80 (S33). The information used for authentication (the ID and password of the user authorized to view reviews) is assumed to be stored in advance in the storage unit 62 or another storage device. For example, if the viewer information stored in the viewing authority DB 62c includes the viewer's password, the control unit 61 performs authentication using the viewer ID and password stored in the viewing authority DB 62c. If the viewer ID and password received from the viewer terminal 80 are stored in the viewing authority DB 62c, the control unit 61 determines that the viewer has the review viewing authority (authentication succeeded). If the viewer ID and password are not stored in the viewing authority DB 62c, the control unit 61 determines that the viewer does not have the review viewing authority (authentication failed). If the control unit 61 cannot authenticate the viewer, it does not provide the review to the viewer and terminates the series of processes. At this time, the control unit 61 may send a message to the viewer terminal 80 that has made the viewing request, notifying the viewer that the review cannot be viewed because the viewer does not have valid viewing authority.

[0057] If the control unit 61 is able to authenticate the viewer, it identifies the scope of viewing authority, which indicates the reviews that the viewer can view (S34). Here, the control unit 61 identifies the scope of viewing authority corresponding to the viewer ID of the viewer, based on the stored contents of the viewing authority DB 62c. Then, the control unit 61 generates a viewing authority notification screen based on the identified scope of viewing authority, and transmits it to the viewer terminal 80 that has made the viewing request (S35). The control unit of the viewer terminal 80 receives the viewing authority notification screen from the review management server 60, and displays the notification screen as shown in FIG. 14B on the display unit (S36). The viewing authority notification screen shown in FIG. 14B shows an example in which the viewer is a producer. The scope of reviews that a producer can view (scope of viewing authority) is defined by the coffee bean ID, so the notification screen shown in FIG. 14B displays a list of coffee bean IDs as a list of products for which reviews can be viewed. The listed coffee bean IDs are associated with check boxes, and the viewer (producer) can check the coffee bean ID of the coffee bean for which they want to view reviews and operate the view button to request viewing of reviews of products that use the specified coffee beans.

[0058] If the viewer is a refiner, a notification screen displaying a list of refining process IDs as a list of products for which reviews can be viewed is provided from the review management server 60 to the viewer terminal 80. If the viewer is a roaster, a notification screen displaying a list of roasting process IDs as a list of products for which reviews can be viewed is provided from the review management server 60 to the viewer terminal 80. If the viewer is a retailer, a notification screen displaying a list of product IDs and a list of store IDs as a list of products for which reviews can be viewed is provided from the review management server 60 to the viewer terminal 80.

[0059] The control unit of the viewer terminal 80 determines whether or not the designation of the viewing target has been accepted, depending on whether or not an arbitrary coffee bean ID has been checked and the view button has been operated on the notification screen shown in FIG. 14B (S37). If it is determined that the designation of the viewing target has not been accepted (S37: NO), the control unit waits. If it is determined that the designation of the viewing target has been accepted (S37: YES), the control unit transmits a review viewing request based on the coffee bean ID designated as the viewing target to the review management server 60 (S38). Note that if the viewer is a refiner, the viewer terminal 80 transmits a review viewing request based on the refining process ID designated as the viewing target to the review management server 60. If the viewer is a roaster, the viewer terminal 80 transmits a review viewing request based on the roasting process ID designated as the viewing target to the review management server 60. If the viewer is a retailer, the viewer terminal 80 transmits a review viewing request based on the product ID or store ID designated as the viewing target to the review management server 60.

[0060] When the control unit 61 of the review management server 60 receives a review viewing request specifying a viewing target from the viewer terminal 80, it identifies the product ID of the product for which the review is to be viewed (S39). For example, when the control unit 61 receives a review viewing request based on a coffee bean ID from the viewer terminal 80, it identifies all product IDs corresponding to the coffee bean ID based on the stored contents of the product information DB 62a. When the control unit 61 receives a review viewing request based on a refining process ID from the viewer terminal 80, it identifies all product IDs corresponding to the refining process ID based on the stored contents of the product information DB 62a. When the control unit 61 receives a review viewing request based on a roasting process ID from the viewer terminal 80, it identifies all product IDs corresponding to the roasting process ID based on the stored contents of the product information DB 62a. When the control unit 61 receives a review viewing request based on a store ID from the viewer terminal 80, it identifies all product IDs corresponding to the store ID based on the stored contents of the product information DB 62a.

[0061] The control unit 61 extracts reviews corresponding to the product ID specified as the viewing target from the blockchain system (S40). Here, the control unit 61 requests one of the node devices 10 to view the reviews corresponding to the specified product ID. The node device 10 searches the blockchain system using the product ID requested for viewing as a key, extracts reviews corresponding to the product ID, and outputs them to the review management server 60. In this embodiment, the reviews are stored in the blockchain system in association with attribute information of the poster, so the control unit 61 reads out the attribute information of the poster along with the reviews.

[0062] Based on the reviews and poster's attribute information extracted in step S40, the control unit 61 generates a review viewing screen displaying a list of reviews and poster's attribute information, and transmits the generated review viewing screen to the viewer terminal 80 that issued the viewing request (S41). FIG. 14C shows an example of a review viewing screen displaying a list of reviews. The review viewing screen shown in FIG. 14C displays the coffee bean ID designated as the viewing target via the notification screen of FIG. 14B, the poster's attribute information, and the reviews. Note that the screen shown in FIG. 14C shows an example in which the viewer is a producer. Because a coffee bean ID is designated as the viewing target, the products subject to each review may use the same coffee beans but may have different refining processes, roasting processes, and retailers. Therefore, the review viewing screen shown in FIG. 14C displays the refining process ID, roasting process ID, product ID, and retailer information for the product subject to review in association with each review. The control unit 61 can generate the review viewing screen shown in Figure 14C by extracting each review from the blockchain system and obtaining the refining process ID, roasting process ID, and retailer information corresponding to the product in each review from the product information DB 62a.

[0063] The control unit of the viewer terminal 80 receives the review viewing screen transmitted from the review management server 60 via the communication unit and displays it on the display unit (S42). This allows the review management server 60 to provide a review of the product requested by the viewer terminal 80 (viewer) that made the viewing request.

[0064] In the information processing system of this embodiment, reviews posted by posters are registered in the blockchain system and can be provided to viewers with legitimate viewing rights. Therefore, product reviews can be collected and provided as feedback to viewers (product providers), such as product manufacturers. In the above-described process, viewers view reviews registered in the blockchain system using the viewer terminal 80. However, various information stored in the blockchain system can be viewed not only via the viewer terminal 80, but also via each server 20, 30, 40, and 50, as long as the viewer has legitimate viewing rights. For example, coffee bean producers can view various information regarding the use of the coffee beans they produce (refining methods, roasting methods, sales methods, etc.) and reviews by purchasers. Furthermore, coffee refiners can view various information regarding the use of the coffee beans they refine and reviews by purchasers, and coffee roasters can view various information regarding the use of the coffee beans they roast and reviews by purchasers. In this way, providing buyers' reviews (opinions and evaluations of products) to each trader can foster communication between traders and buyers, which is expected to lead to the development of better products. In addition, reviews are recorded in the blockchain system and are only available to viewers with legitimate viewing rights, which prevents reviews from being tampered with or inadvertently made public, and also protects copyrights related to reviews.

[0065] Furthermore, in the information processing system of this embodiment, information regarding the work performed at each stage of coffee (product) from production to sales is registered in the blockchain system. Each piece of information registered in the blockchain system can then be provided to viewers with legitimate viewing rights. For example, a purchaser of a product (a person who posts a review) can view various pieces of information regarding the production, refining, roasting, and sales of the purchased product. Furthermore, personnel at each company involved in production, refining, roasting, and sales can view various pieces of information regarding the coffee beans processed by each company. Thus, this embodiment enables the sharing of various pieces of information among each company and purchaser from the production to sales stages of coffee.

[0066] In the information processing system of this embodiment, a two-dimensional code (product identification information) is assigned to each product, allowing users to post reviews of each product. For example, in the case of a restaurant, reviews are generally posted about the store and feedback is provided to the store. In contrast, in the information processing system of this embodiment, reviews can be posted for each menu item sold at the store (for example, each drink or food), and users can rate each menu item. This allows the store to receive feedback on the ratings for each menu item, enabling more detailed analysis of product ratings.

[0067] In this embodiment, in addition to a configuration in which a two-dimensional code containing access information for obtaining detailed information about the product and product identification information (product ID, retailer information, etc.) is printed or affixed to the product, a configuration in which an IC tag storing access information and identification information corresponding to the product is attached to the product may be adopted. In this case, the access information and product identification information stored in the IC tag can be read from the IC tag using an RFID (Radio Frequency Identifier) ​​reader. For example, if the poster terminal 70 has an RFID reader function, the poster can use the RFID reader of the poster terminal 70 to read the information stored in the product's IC tag and obtain a review input screen.

[0068] (Embodiment 2) An information processing system for issuing tokens to reviewers who post product reviews will be described. The information processing system of this embodiment can be realized by the same device as the information processing system of the first embodiment, so detailed description of the configuration will be omitted.

[0069] FIG. 15 is a schematic diagram showing an example of the configuration of a token management block 170. As shown in the lower left of FIG. 15, the recorded information 173 in the token management block 170 includes information such as the amount of tokens issued (granted) to a contributor from a token issuer terminal (not shown), the date of issuance, and a contributor ID identifying the contributor to whom the token was issued. Therefore, information about the tokens granted to the contributor is stored and managed in the blockchain system in association with the contributor's identification information (contributor ID). Furthermore, in the information processing system of this embodiment, the contributor can distribute (transfer) the tokens issued to him / her to coffee bean producers, refiners, roasters, or retailers. Therefore, when a contributor distributes tokens to a desired vendor, as shown in the lower right of FIG. 15, the recorded information 173 in the block 170 includes information such as the contributor ID of the contributor distributing the tokens to the vendor, the date of token distribution, information identifying the vendor to whom the tokens are distributed (transferred), and the amount distributed (transferred). In this way, in the information processing system of this embodiment, information on tokens issued when a poster posts a review about a product and information on tokens that the poster distributes to desired vendors are recorded and managed in block 170.

[0070] Fig. 16 is a flowchart showing an example of the review posting process procedure of the second embodiment, and Fig. 17 is a schematic diagram showing an example screen. The process shown in Fig. 16 is the process shown in Fig. 11 with steps S51 to S56 added after step S21. Explanations of the same steps as in Fig. 11 will be omitted, and steps S11 to S18 in Fig. 11 will not be shown in Fig. 16.

[0071] In the information processing system of this embodiment, the control unit 71 of the poster terminal 70 and the control unit 61 of the review management server 60 perform the processes of steps S11 to S21 in Fig. 11. As a result, the poster inputs a review about a product via a review input screen acquired by reading the two-dimensional code of the product and transmits it to the review management server 60, and the review management server 60 records the review in the review DB 62b and the blockchain system.

[0072] The control unit 61 of the review management server 60 records the review information acquired from the poster terminal 70 in the blockchain system, and then issues a token to the poster (S51). For example, if the amount of tokens to be issued per review post is set, the control unit 61 issues a predetermined amount of tokens to the poster. Also, if the amount of tokens to be issued per review post is set for each product, each retail store, or each distributor, the control unit 61 issues the poster an amount of tokens corresponding to the product, retail store, or distributor corresponding to the review. The control unit 61 issues a token to the poster by correlating the poster ID, issue date, and issue amount of the poster to whom the token is to be issued, and storing them in the blockchain system.

[0073] When issuing tokens to a poster, the control unit 61 may evaluate whether the content of the posted review is appropriate and switch whether to issue tokens depending on the appropriateness. The determination of whether the content of the review is appropriate may be performed, for example, by a person in charge of review management, who reviews the posted review according to predetermined rules. The control unit 61 may also determine whether the content of the review is appropriate using a neural network constructed by machine learning. For example, a learning model composed of an RNN (Recurrent Neural Network) trained to output an output value corresponding to whether the content of the review is appropriate when text data of the review is input may be used. In this case, the control unit 61 inputs the text data into the trained learning model and can determine whether the content of the review is appropriate based on the output value from the learning model. The amount of tokens issued may also be changed depending on the content of the review. For example, the control unit 61 may identify an evaluation of the content of the review and issue an amount of tokens corresponding to the identified evaluation level. In this case, the control unit 61 may also determine the evaluation level of the content of the review using a neural network. For example, a learning model can be used that is configured with an RNN and that is trained to output an evaluation value (level) for the content of a review when review text data is input.

[0074] The control unit 61 generates a notification screen notifying the user of the issuance of the tokens and transmits it to the poster terminal 70 of the poster to whom the tokens are to be issued (S52). The control unit 71 of the poster terminal 70 receives the notification screen transmitted from the review management server 60 and displays it on the display unit 75 (S53). FIG. 17 shows an example of the notification screen. The screen shown in FIG. 17 displays information about the product to be reviewed, as well as the date and amount of tokens issued. The notification screen also notifies the user that the issued tokens can be distributed to businesses (product producers) involved in the product, and provides input fields for specifying the amount of tokens to be distributed to each business. In the example shown in FIG. 17, an input field for specifying the amount of tokens to be distributed to the producer, an input field for specifying the amount of tokens to be distributed to the refiner, an input field for specifying the amount of tokens to be distributed to the roaster, and an input field for specifying the amount of tokens to be distributed to the retailer are provided. Each input field may be configured to allow direct input of information, or may be configured to allow selection of an option via a pull-down menu displaying multiple options.

[0075] When a poster wishes to distribute the tokens issued to them to a desired vendor, they input the amount of tokens they wish to distribute in the input field corresponding to the desired vendor. The names of each vendor are displayed on the notification screen, and detailed information about each vendor can be obtained via the link set for each vendor's name on the notification screen. Furthermore, if the poster owns tokens other than the tokens issued this time, they can distribute more tokens than the tokens issued this time to the desired vendor.

[0076] The control unit 71 of the poster terminal 70 accepts a request to execute a token distribution process when the amount of tokens to be distributed to one of the vendors is entered in an input field on the notification screen and the execute button is pressed. The control unit 71 determines whether the request to execute the token distribution process has been accepted (S54), and if it is judged that the request has been accepted (S54: YES), it transmits the entered distribution information to the review management server 60 (S55). At this time, the control unit 71 transmits distribution information to the review management server 60, including the poster ID of the poster, vendor information of the vendor to which the amount of tokens to be distributed was entered, and the amount of tokens to be distributed.

[0077] The control unit 61 of the review management server 60 receives the distribution information transmitted from the poster terminal 70 and executes the distribution process of the tokens based on the received distribution information (S56). Here, the control unit 61 executes the distribution process of the tokens from the poster to the distribution destination vendor by correlating the poster ID of the poster from whom the tokens are distributed, the distribution date, information on the distribution destination vendor, and the amount of tokens to be distributed (distribution amount) and storing them in the blockchain system. If the control unit 71 determines that a token distribution request has not been received (S54: NO), it skips the process of step S55 and ends the series of processes.

[0078] According to the above-described process, in this embodiment, after a poster posts a review about a product, tokens are issued and given to the poster as an incentive for posting the review. Because tokens are given for posting a review, it is expected that posters will be more motivated to post reviews, and the number of reviews posted can be expected to increase. Furthermore, by evaluating the content of reviews and issuing an amount of tokens according to the evaluation results, it is expected that the number of reviews posted with appropriate content will increase, while the number of reviews posted with false or inappropriate content will decrease. Furthermore, in this embodiment, tokens issued to posters can be distributed to any vendor at the poster's discretion. Thus, posters can support desired vendors by distributing tokens, creating a connection between posters (purchasers) and producers (vendors). While conventional logistics systems allow sellers and buyers to exchange product purchases and review feedback, in this embodiment, various information can be shared and tokens can be used to support all vendors involved in the production of a product, not just sellers. This allows buyers to become closer to each other and build cooperative relationships.

[0079] In this embodiment, the distribution of tokens by the poster may be configured to be performed not only immediately after posting a review, but also at any timing. For example, the poster may be configured to be able to distribute tokens to any vendor via a viewing screen on which the poster can view information on the tokens they own.

[0080] The issuance of tokens in response to the posting of reviews as described above may be realized by a smart contract in a blockchain system. Specifically, by defining a program in the node device 10 that issues tokens on the condition that a review is posted, the node device 10 executes the program, and tokens are automatically issued when a review is posted. In addition, by setting the amount of tokens to be issued in the program, a predetermined amount of tokens can be automatically issued when a review is posted.

[0081] In this embodiment, the distribution amount of tokens granted to a poster to each vendor is not limited to a configuration specified via the notification screen shown in FIG. 17 . For example, a configuration may be adopted in which a poster pre-sets the distribution amount or distribution ratio of tokens granted to the poster when posting a review to each vendor (i.e., producer, refiner, roaster, and distributor). For example, the distribution amount or distribution ratio of tokens to be distributed to each vendor is stored in association with the poster in the storage unit 62 of the review management server 60. Then, when a poster posts a review, the review management server 60 issues tokens to the poster and distributes the issued tokens to each vendor based on the distribution amount or distribution ratio for each vendor registered for that vendor. This configuration eliminates the need for the poster to specify the amount of tokens to be distributed to each vendor each time they post a review, reducing the operational burden on the poster.

[0082] The process of confirming the token granted to the poster will be described below. FIG. 18 is a flowchart showing an example of the process procedure for providing the token grant history, and FIG. 19 is a schematic diagram showing an example screen. In this embodiment, when a poster wants to confirm the tokens he or she owns, the poster accesses the website S of the review management server 60 using the poster terminal 70 or executes a predetermined application to obtain a token confirmation screen (not shown). The poster then requests confirmation of the token via the token confirmation screen.

[0083] The control unit 71 of the poster terminal 70 determines whether a token confirmation request has been received in accordance with an instruction from the poster via the operation unit (S61), and if it determines that a token confirmation request has not been received (S61: NO), it waits until it is received. If it determines that a token confirmation request has been received (S61: YES), the control unit 71 transmits a token confirmation request to the review management server 60 (S62). Here, the control unit 71 transmits the poster ID of the poster to the review management server 60 to request token confirmation.

[0084] When the control unit 61 receives a token confirmation request from the poster terminal 70, it extracts token information of the poster ID of the requester from the blockchain system (S63). Here, the control unit 61 requests token information corresponding to the poster ID of the requester from one of the node devices 10. The node device 10 searches the blockchain system using the poster ID as a key, extracts token information corresponding to the poster ID, and outputs it to the review management server 60. The control unit 61 generates a token history screen based on the token information extracted by the node device 10 (S64). Figure 19 shows an example of the token history screen, and the token history screen shown in Figure 19 displays the date on which the token was issued or distributed to a trader, the amount issued or distributed, and the remaining balance.

[0085] The control unit 61 transmits the generated token history screen to the poster terminal 70 that made the request (S65), and the control unit 71 of the poster terminal 70 receives the token history screen from the review management server 60 and displays it on the display unit 75 (S66). As a result, the token history screen shown in FIG. 19 is displayed on the display unit 75 of the poster terminal 70, allowing the poster to check the history of tokens granted to the poster and tokens distributed to vendors. The history screen shown in FIG. 19 may be configured to allow tokens to be distributed to each vendor via this screen. For example, the history screen shown in FIG. 19 may display information about each vendor related to products purchased by the poster, and may include an input field for inputting the amount of tokens to be distributed to each vendor. This configuration allows the poster to check the tokens they own and distribute tokens to desired vendors.

[0086] In this embodiment, in addition to the configuration in which a token is issued to a poster when the poster posts a review of a product, tokens may also be issued as purchase points that are awarded when the poster (purchaser) purchases a product. Purchase points are points awarded to purchasers of a product through, for example, a campaign implemented by a product manufacturer or a retail store. In this case, information on the tokens issued as purchase points may be stored and managed in a blockchain system. Furthermore, the incentive awarded to a poster for posting a review is not limited to tokens, and may be, for example, the issuance of ID information that proves the existence of the poster. For example, when a review is posted, the review management server 60 may provide the poster with information that proves that the review was posted on the date and time the review was posted.

[0087] In this embodiment, the tokens granted to the poster may be configured not only to be distributed to various vendors but also to be usable at stores selling coffee products. In this case, the poster can purchase products using the tokens by paying the store with their tokens using the poster terminal 70. Furthermore, if the system is configured to allow exchange of tokens in different blockchain systems, the poster can convert their own tokens into tokens in other blockchain systems, thereby making it possible to make various payments with the tokens in the other blockchain systems. Furthermore, the system may be configured to allow tokens in the blockchain system to be converted into currency such as Japanese yen or US dollars. In this case, the poster can convert their own tokens into currency.

[0088] In this embodiment, the same effects as in the first embodiment described above can be obtained. Furthermore, in this embodiment, when a poster posts a review about a product, tokens are issued to the poster. Therefore, an increase in the number of reviews posted can be expected, and if tokens are issued according to the appropriateness of the review content, an increase in the number of high-quality reviews posted can be expected. Furthermore, in this embodiment, the tokens issued to the poster can be distributed to each business operator according to the poster's wishes. Therefore, the poster can distribute tokens to their favorite business operators to support them. In this embodiment, the modified examples described as appropriate in each of the above-mentioned embodiments can also be applied.

[0089] (Embodiment 3) An information processing system in which a user can specify a company to be reviewed and post a review of the company will be described. The information processing system of this embodiment can be realized by the same device as the information processing system of the first embodiment, so detailed description of the configuration will be omitted.

[0090] Fig. 20 is a flowchart showing an example of a review posting process procedure according to the third embodiment, and Fig. 21 is a schematic diagram showing an example of a review input screen according to the third embodiment. The process shown in Fig. 20 is the same as the process shown in Fig. 11 except that step S71 is added between steps S17 and S18, step S72 is added instead of step S19, and step S73 is added after step S21. Explanation of the same steps as in Fig. 11 will be omitted.

[0091] In the information processing system of this embodiment, the control unit 71 of the poster terminal 70 and the control unit 61 of the review management server 60 perform the processes of steps S11 to S17 in FIG. 11. In this embodiment, in step S14, the control unit 61 of the review management server 60 generates a review input screen as shown in FIG. 21. The review input screen shown in FIG. 21 includes, in addition to the configuration of the review input screen shown in FIG. 12B, an input field for specifying the company to be reviewed and an input field for specifying the distribution destination and distribution amount of tokens to be issued for the review posting. The input field for specifying the company to be reviewed displays each selectable company and has a check box corresponding to each company. The input field for the distribution destination and distribution amount of tokens is the same as the input field for specifying the amount of tokens to be distributed to each company on the notification screen shown in FIG. 17. Therefore, in this embodiment, when entering a review, the poster can specify the company to be reviewed using the check box, and can also specify the company to which tokens issued for the review posting will be distributed and the distribution amount.

[0092] In step S17, the control unit 71 of the poster terminal 70 accepts review information, including information on the review subject, the poster, and the review content, via each input field on the review input screen, and displays the accepted information in the corresponding input field (S17). The control unit 71 also accepts distribution information, indicating the amount of tokens to be distributed to each provider, via the review input screen, and displays the accepted distribution amount in the corresponding input field (S71). The control unit 71 then determines whether the submit button on the review input screen has been operated (S18). If it determines that the submit button has not been operated (S18: NO), the control unit 71 returns to the processing of step S17 and repeats accepting the review information and distribution information. If it determines that the submit button has been operated (S18: YES), the control unit 71 transmits the review information and distribution information entered via the review input screen to the review management server 60 (S72).

[0093] The control unit 61 of the review management server 60 performs steps S20 to S21 based on the review information received from the poster terminal 70, stores the review information in the review DB 62b, and also stores it in the blockchain system. In this embodiment, since the review information includes information about the company being reviewed, the control unit 61 operates as a receiving unit that receives the review content and the designation of the review target from the poster terminal 70. Based on the received review information, the control unit 61 associates the product information, the designated company (review target), the poster ID, attribute information such as age and gender, and the review, and stores them in the review DB 62b and the blockchain system. The control unit 61 then executes a token distribution process based on the distribution information received from the poster terminal 70 (S73). In this embodiment, the control unit 61 also operates as a receiving unit that receives, from the poster terminal 70, the designation of the token distribution destination and distribution amount, and distributes the designated distribution amount of tokens to the designated distribution destination company. The token distribution process is similar to step S56 in the process shown in FIG. 16 in the second embodiment.

[0094] According to the above-described process, in this embodiment, when a poster posts a review about a product, the poster can specify the company to be reviewed, and can post a review (impressions and ratings) about any company. The review input screen shown in FIG. 21 may have a configuration that includes an input field for a score that evaluates each company on a five-point scale, for example. Furthermore, in this embodiment, the recipient and amount of tokens to be distributed can be specified on the review input screen, so that when submitting a review, the poster can also specify the company to which tokens will be distributed and the amount to be distributed.

[0095] FIG. 22 is a schematic diagram showing a modified example of a review input screen. The review input screen shown in FIG. 22 is a screen that is displayed when a link to a manufacturer is selected in the product information of the product to be reviewed on the review input screen shown in FIG. 12B. When a link to a manufacturer is selected on the poster terminal 70 via the review input screen shown in FIG. 12B, the review management server 60 acquires detailed information about the manufacturer, for example, from the production management server 20, generates the screen shown in FIG. 22, and provides it to the poster terminal 70. The review input screen shown in FIG. 22 displays detailed information about the manufacturer of the product to be reviewed, and has an input field for inputting a review targeting the manufacturer and an input field for inputting the amount of tokens to be distributed to the manufacturer.

[0096] 12B on the poster terminal 70, the review management server 60 acquires detailed information about the refiner, for example, from the refinery management server 30. The review management server 60 then generates a review input screen that displays the detailed information about the refiner and has an input field for a review about the refiner as the review target and an input field for the amount of tokens to be distributed to the refiner, and provides this screen to the poster terminal 70. Furthermore, when a link to a roaster is selected on the review input screen shown in FIG. 12B, the review management server 60 generates a review input screen that displays detailed information about the roaster and has an input field for a review about the roaster as the review target and an input field for the amount of tokens to be distributed to the roaster, and provides this screen to the poster terminal 70. Furthermore, when a link to a seller or sales store is selected via the review input screen shown in Figure 12B, the review management server 60 displays detailed information about the seller or sales store, and generates a review input screen having an input field for a review with the seller or sales store as the review subject and an input field for the amount of tokens to be distributed with the seller or sales store as the recipient, and provides this to the poster terminal 70.

[0097] The poster can also post a review about a product by pointing to the company being reviewed on the review input screen shown in Fig. 22. Furthermore, on the review input screen shown in Fig. 22, when entering a review, the poster can designate the company being reviewed as the recipient of tokens and specify the amount of tokens to be distributed.

[0098] This embodiment provides the same effects as the above-described embodiments. Furthermore, in this embodiment, when a poster posts a review, the poster can specify the company to be reviewed. Therefore, the poster's review is managed in association with the company to be reviewed, so that the review can be reliably provided for the company to be reviewed. In this embodiment, it is possible to post reviews for all companies (producers) involved in a product, and also to post reviews for individual companies.

[0099] In this embodiment, for example, a review target company is designated by checking a checkbox for a desired company on the review input screen shown in FIG. 21 or by selecting a link for a desired company on the review input screen shown in FIG. 12B. However, this is not limiting. For example, when the review management server 60 receives a review from the poster terminal 70, the review target company may be identified based on the review content. For example, for each company, terms that are likely to appear in reviews targeting that company may be pre-registered. The review management server 60 determines whether any of the terms are included in the review content. If any of the terms are included, the review management server 60 selects the company corresponding to the term as the review target. For example, if the review includes terms related to coffee beans or farms, the producer may be selected as the review target. If the review includes terms related to refining processes (e.g., natural, washed, honey, etc.), the refiner may be selected as the review target. Furthermore, if a review includes terms related to roasting processes (e.g., roast, dark roast, etc.), the roaster may be determined to be the review target, and if a review includes terms related to sales (e.g., store name, product name, etc.), the retailer may be determined to be the review target. With this configuration, the poster can post a review without being aware of the review target, and the review management server 60 can assign a review target to each review. In this case, too, each review can be managed in association with the retailer being reviewed, making it possible to provide reviews that should be provided to each retailer.

[0100] In this embodiment, the review target and review can be input via the review input screen, and the token distribution destination and distribution amount can also be input, but this is not limited to this. For example, the review input screen may be configured to only input the review target and review. In this case, after the review target and review are input via the review input screen, a token notification screen such as that shown in FIG. 17 may be provided from the review management server 60 to the poster terminal 70, and the token distribution destination and distribution amount may be input via the notification screen. In addition, the modified examples described in each of the above embodiments can also be applied to this embodiment as appropriate.

[0101] (Embodiment 4) This embodiment describes an information processing system that identifies products or types of products that a contributor may purchase based on reviews by the contributor, and provides the identified products or types of products to retailers, etc. The information processing system of this embodiment can be realized by a device similar to the information processing system of the first embodiment, and therefore a detailed description of the configuration will be omitted.

[0102] Fig. 23 is a flowchart showing an example of a review posting process procedure in embodiment 4. The process shown in Fig. 23 is the process shown in Fig. 11 with steps S81 to S83 added after step S21. Explanations of the same steps as in Fig. 11 will be omitted, and steps S11 to S18 in Fig. 11 will not be shown in Fig. 23.

[0103] In the information processing system of this embodiment, the control unit 71 of the poster terminal 70 and the control unit 61 of the review management server 60 perform the processes of steps S11 to S21 in FIG. 11. The control unit 61 of the review management server 60 records review information acquired from the poster terminal 70 in the blockchain system, and then estimates products (purchased products) that the poster may purchase in the future (S81). The control unit 61 estimates the purchased products based on, for example, the products related to the reviews acquired from the poster terminal 70 and the content of the reviews. For example, if a review is posted that gives a high rating to a purchased product, the control unit 61 estimates a product similar to the product as the purchased product. On the other hand, if a review is posted that gives a low rating to a purchased product, the control unit 61 estimates a product of a different type from the product as the purchased product. Whether the review gives a high rating to a product or a low rating may be determined based on, for example, the wording appearing in the review. For example, by registering in advance phrases indicating a high rating for a product and phrases indicating a low rating, if one of the phrases appears frequently, it can be determined that the product has a high or low rating depending on the phrase. The control unit 61 may also estimate the purchased product by taking into account attribute information such as the poster's age and gender.

[0104] The control unit 61 stores the estimated purchased product (estimated product) in the storage unit 62 in association with the poster's information (S82). For example, the control unit 61 stores the estimated product information in association with the poster's attribute information. The control unit 61 may also store the estimated product information in association with the poster's contact information. The control unit 61 then transmits the estimated product information in association with the poster's attribute information and / or contact information to, for example, a seller's terminal (S83). Note that the transmission process to the seller's terminal may be executed, for example, after the estimated product information for multiple posters has been accumulated.

[0105] According to the above-described process, in this embodiment, when a poster posts a product review, it is estimated which products the poster may purchase in the future, and information about the estimated products is provided to retailers, etc. Retailers, etc. can use the information about the estimated products in their product promotion activities. For example, when a retailer obtains information about the estimated product associated with the poster's attribute information, it can deliver advertising information about the estimated product to customers with the corresponding attributes, thereby delivering effective advertising to customers who are likely to purchase the product. Furthermore, when a retailer obtains information about the estimated product associated with the poster's contact information, it can deliver advertising information about the estimated product to the corresponding poster, thereby enabling pinpointed advertising to be delivered to the poster. Note that the review management server 60 may be configured to send information about the estimated product to the poster and provide it to the poster as information about recommended products.

[0106] In this embodiment, for example, the process of a seller delivering advertising information to a customer may be performed using email or a messaging app such as LINE (registered trademark). Also, if a predetermined application is installed on the customer's device, the advertising information may be delivered by a push notification from the application.

[0107] This embodiment provides the same effects as the above-described embodiments. Furthermore, this embodiment can identify products that a poster may purchase in the future based on the content of the review posted by the poster, and provide feedback on the identified products to retailers, etc. This allows retailers, etc. to distribute advertising information that takes into account products that a poster may purchase, enabling efficient advertising activities.

[0108] The configuration of this embodiment can be applied to the information processing systems of the above-described embodiments 2 and 3, and the same effects can be obtained even when applied to the information processing systems of the above-described embodiments 2 and 3. Furthermore, the modified examples described in each of the above-described embodiments can also be applied to this embodiment.

[0109] (Embodiment 5) An information processing system capable of issuing a digital ID to a user who posts a review about a product will be described. The information processing system of this embodiment can be realized by a device similar to that of the information processing system of the first embodiment, and therefore detailed description of the configuration will be omitted.

[0110] The digital ID is ID information that serves as proof of the poster's existence, and includes, for example, information proving that a review was posted on the date and time the review was posted. The digital ID can be a self-sovereign identity (SSI) realized using a blockchain system, and the issued digital ID is recorded in the digital ID management block 170. In the digital ID management block 170, recorded information 173 includes information such as the date of issuance of the digital ID, the issuing organization, the poster ID, the date and time the review was posted, and the posted content. Therefore, in the information processing system of this embodiment, information on the digital ID issued when a poster posts a product review is recorded and managed in the blockchain system. The poster can obtain their own digital ID recorded in the blockchain system by running a specified application on the poster terminal 70.

[0111] Fig. 24 is a flowchart showing an example of the review posting process procedure of embodiment 5, and Figs. 25A and 25B are schematic diagrams showing example screens. The process shown in Fig. 24 is the process shown in Fig. 11 with steps S91 to S95 added after step S21. Explanations of the same steps as in Fig. 11 will be omitted, and steps S11 to S18 in Fig. 11 will not be shown in Fig. 24.

[0112] In the information processing system of this embodiment, the control unit 71 of the poster terminal 70 and the control unit 61 of the review management server 60 perform the processes of steps S11 to S21 in FIG. 11. In this embodiment, in step S14, the control unit 61 of the review management server 60 generates a review input screen as shown in FIG. 25A and transmits it to the poster terminal 70. In step S16, the control unit 71 of the poster terminal 70 receives the review input screen as shown in FIG. 25A from the review management server 60 and displays it on the display unit 75. The review input screen shown in FIG. 25A includes, in addition to the configuration of the review input screen shown in FIG. 12B, a checkbox for selecting whether or not a digital ID is desired for the review submission. Therefore, in this embodiment, in step S19, the control unit 71 of the poster terminal 70 transmits review information including information indicating whether or not a digital ID is desired to be issued to the review management server 60. By using a review input screen configured in this manner, the poster can request the issuance of a digital ID at a desired timing.

[0113] After recording the review information acquired from the poster terminal 70 in the blockchain system, the control unit 61 of the review management server 60 determines whether or not the issuance of a digital ID has been requested from the poster terminal 70 (S91). Here, if the review information received from the poster terminal 70 includes information indicating a desire for issuance of a digital ID, the control unit 61 determines that the issuance of a digital ID has been requested, and if not, determines that the issuance of a digital ID has not been requested.

[0114] If the control unit 61 determines that a digital ID has not been requested (S91: NO), it determines whether to issue a digital ID based on the content of the review received from the poster terminal 70 (S92). For example, the control unit 61 determines whether to issue a digital ID based on whether the review contains predetermined content. For example, if the review includes the taste of the coffee or the poster's impressions of the coffee's taste, the control unit 61 determines that a digital ID should be issued. Specifically, if a review is posted about a subjective experience and impression, such as whether the coffee was delicious or not, the control unit 61 determines that a digital ID should be issued. The control unit 61 may also obtain reviews previously posted by the poster from the blockchain system, compare the previous reviews with the current review, determine whether there has been a change in the poster's taste or attitude, and, if there has been a change, determine that a digital ID should be issued. With this configuration, even if the poster has not requested the issuance of a digital ID, a digital ID can be issued if the content of the review meets predetermined conditions.

[0115] If it is determined that a digital ID does not need to be issued (S92: NO), the control unit 61 ends the series of processes. If it is determined that issuance of a digital ID has been requested (S91: YES), or if it is determined that a digital ID should be issued (S92: YES), the control unit 61 issues a digital ID to the poster (S93). For example, the control unit 61 issues a digital ID to the poster by correlating the issue date, information about the issuing organization, the poster ID of the poster to whom the digital ID is to be issued, the review posting date and time, and the review content, and storing these as digital ID information in the blockchain system.

[0116] The determination of whether a digital ID should be issued for a posted review may be made, for example, by a person in charge of managing posted reviews according to a predetermined rule. Alternatively, the control unit 61 may use a neural network constructed by machine learning to determine whether a digital ID should be issued for a review. For example, a learning model composed of an RNN and trained to output an output value corresponding to whether a digital ID should be issued for the review when text data of the review is input may be used. In this case, the control unit 61 inputs the text data into the trained learning model and can determine whether a digital ID should be issued for the review based on the output value from the learning model.

[0117] The control unit 61 generates a notification screen notifying the issuance of a digital ID and transmits it to the poster terminal 70 of the poster to whom the digital ID is to be issued (S94). The control unit 71 of the poster terminal 70 receives the notification screen transmitted from the review management server 60 and displays it on the display unit 75 (S95). FIG. 25B shows an example of the notification screen. The screen shown in FIG. 25B displays information about the product to be reviewed and information indicating the issuance of the digital ID (issue certificate). The screen shown in FIG. 25B has a save button for instructing storage of the issuance certificate of the digital ID in the memory unit 72 of the poster terminal 70. When the save button is operated, the control unit 71 stores the issuance certificate notified on the notification screen in the memory unit 72.

[0118] Through the above-described process, when a poster posts a review about a product, a digital ID is issued to the poster as an incentive for posting the review. In the above-described process, the digital ID may be issued upon request from the poster or automatically based on the review content, but either one may be used. In a configuration in which a digital ID is issued upon request from the poster, posters who wish to be issued with a digital ID are expected to be more motivated to post reviews, and the number of reviews posted can be expected to increase. Furthermore, posters can obtain digital IDs on various occasions, such as birthdays, wedding anniversaries, graduations, or employment. Furthermore, in a configuration in which a digital ID is issued based on the review content, a digital ID is issued, for example, when a review is posted that reflects the poster's subjective impressions. This allows the poster to unconsciously assign a digital ID to their impressions.

[0119] The issuance of a digital ID for posting a review as described above may be realized by a smart contract in a blockchain system. Specifically, a program for issuing a digital ID on the condition that a review is posted is defined in the node device 10. Then, the node device 10 executes the program, and a digital ID is automatically issued when a review is posted.

[0120] In this embodiment, the poster can check the digital ID issued to them by accessing the website S of the review management server 60 using the poster terminal 70 or by running a specific application. When the poster checks the digital ID issued to them, the poster terminal 70 and the review management server 60 perform the same process as shown in Figure 18. Note that the "token" in each step in Figure 18 should be read as "digital ID."

[0121] FIG. 26 is a schematic diagram showing an example of a digital ID issuance history screen. When the poster terminal 70 and the review management server 60 execute the process shown in FIG. 18, the digital ID issuance history screen shown in FIG. 26 is provided from the review management server 60 to the poster terminal 70. The digital ID issuance history screen shown in FIG. 26 displays the digital ID issuance date, issuing institution, review posting date and time, review content, etc. The screen shown in FIG. 26 also displays information indicating whether the issuing institution issued the digital ID automatically (automatic issuance) or in response to a user request (user request). With this configuration, the poster can check the digital ID issued to them and understand whether the digital ID was issued automatically or in response to their request.

[0122] This embodiment provides the same effects as the above-described embodiments. Furthermore, in this embodiment, when a poster posts a review about a product, a digital ID is issued at the poster's request, which is expected to increase the number of reviews posted. Furthermore, the digital ID can prove the poster's individuality; for example, a change in the poster's taste or awareness can be proven as a personality trait, and the digital ID can be used as identification. Furthermore, since the digital ID issued to the poster is managed in a blockchain system, tampering with the digital ID can be prevented.

[0123] The configuration of this embodiment can also be applied to the information processing systems of the above-described embodiments 2 to 4, and similar effects can be obtained even when applied to the information processing systems of the above-described embodiments 2 to 4. For example, when applied to the information processing system of the second embodiment, a token and a digital ID can be issued for a review posting, and it can be configured to issue either one or both in response to a request from the poster. Furthermore, the modified examples described in each of the above-described embodiments can also be applied to this embodiment as appropriate.

[0124] (Embodiment 6) This section describes an information processing system that issues review NFTs (Non-Fungible Tokens) corresponding to product reviews on a blockchain system. The information processing system of this embodiment can be implemented using the same device as the information processing system of embodiment 1, so a detailed description of the configuration will be omitted. NFTs are digital data with a certificate of authenticity or ownership, and blockchain technology is used for data management, making them tamper-proof and forgery-proof. Review NFTs are issued on the blockchain, and linking the review text data to the NFT serves as proof of ownership of the review.

[0125] FIG. 27 is a schematic diagram showing an example of the configuration of the review DB 62b according to the sixth embodiment. The review DB 62b shown in FIG. 27 includes a review ID column and a review NFT column in addition to the configuration shown in FIG. 10B. The review ID column stores a review ID, which is identification information assigned to a review. In the review DB 62b according to the present embodiment, information about each review (poster ID, poster attribute information, review content, and review NFT) is stored in association with the review ID. The review NFT column stores review NFTs issued on the blockchain. For example, a review NFT that can prove its "authenticity" or "value" like a certificate may be issued on the blockchain using ERC721, one of the smart contract standards in Ethereum. When ERC721 is used, the review NFT is composed of a token ID, owner address, token URI (Uniform Resource Identifier), and the like. Therefore, for example, the review NFT column stores an index on the blockchain that includes the token ID, owner address, token URI, and the like of the review NFT. When a review NFT is issued, the token ID, owner address, token URI, and other information of the review NFT are stored on the blockchain. The token URI is an attribute that indicates the location of metadata for the review NFT. The location of the metadata is, for example, the URL (Uniform Resource Locator) of the metadata. The metadata itself may be stored in an external database device, for example, in JSON (JavaScript Object Notation) format.

[0126] The process of issuing a review NFT is described below. FIG. 28 is a flowchart showing an example of the review NFT issuance process. For example, when the review management server 60 receives a review posted by a poster from the poster terminal 70, the review management server 60 transmits an instruction to issue a review NFT for the received review to one of the node devices 10 in the blockchain, and acquires the review NFT issued by the node device 10. The control unit 61 acquires, for example, review information sent by the control unit 71 of the poster terminal 70 in step S19 of the review posting process shown in FIG. 11 as a target for issuing a review NFT (S101). The control unit 61 issues a review ID for the acquired review information (S102). The control unit 61 associates the issued review ID, poster ID, poster attribute information, and review with product information (product ID, retailer information, store ID) included in the review information, and stores them in the review DB 62b (S103).

[0127] Next, the control unit 61 transmits an instruction to issue a review NFT from the communication unit 63 to any one of the node devices 10 in the blockchain (S104). The node device 10 receives the instruction to issue a review NFT transmitted by the review management server 60, and issues a review NFT on the blockchain in accordance with the received issuance instruction (S105). The node device 10 stores the token ID, owner address, and token URI of the issued review NFT in the database 15 (S106). The node device 10 transmits the issued review NFT to the review management server 60 via the communication unit 11 (S107). The control unit 61 of the review management server 60 receives the review NFT transmitted by the node device 10, and stores the received review NFT in the review DB 62b in association with the review ID (S108).

[0128] Through the above-described process, a review NFT for a review posted by a poster using the poster terminal 70 can be issued on the blockchain. Because the review NFT includes the owner address, each user can obtain the review NFT they own from the blockchain and view the review corresponding to the review NFT. Furthermore, the owner of the review NFT can transfer the review NFT to another person on the blockchain. For example, if a first user transfers a review NFT owned by the first user to a second user on the blockchain, the ownership of the review NFT is transferred from the first user to the second user, and the owner address of the review NFT is changed from the address of the first user to the address of the second user.

[0129] The configuration of this embodiment can be applied to the information processing systems of the above-described embodiments 1 to 5, and similar effects can be obtained even when applied to the information processing systems of embodiments 1 to 5. Furthermore, in this embodiment, a review NFT is issued for a review by a poster, which is expected to increase the value of the review. For example, reviews (evaluation comments on the product) posted for each product by product experts (e.g., coffee, wine, etc.), such as baristas and sommeliers, can be sold as review NFTs. Furthermore, it is also possible to configure the system to issue NFTs for information that includes not only the review posted by the poster, but also information about the product and each company involved in the production and sale of the product (in the case of coffee, the producer, refiner, roaster, and seller).

[0130] Furthermore, in this embodiment, a configuration may be adopted in which a review NFT is issued corresponding to each review for each vendor. In this case, the control unit 61 of the review management server 60 acquires review information transmitted from the poster terminal 70 and issues a review ID for the acquired review information. The control unit 61 then associates the issued review ID, poster ID, poster attribute information, and review with information about the vendor being reviewed, and stores them in, for example, the review DB 62b. Thereafter, the control unit 61 transmits a review NFT issuance instruction to one of the node devices 10 in the blockchain from the communication unit 63, and the node device 10 issues a review NFT on the blockchain in accordance with the review NFT issuance instruction transmitted from the review management server 60. The node device 10 then stores the token ID, owner address, and token URI of the issued review NFT in the database 15 and transmits the issued review NFT to the review management server 60. The control unit 61 of the review management server 60 receives the review NFT transmitted from the node device 10, associates the review target merchant and review ID, and stores the received review NFT in, for example, the review DB 62b. This makes it possible to issue review NFTs corresponding to reviews of each merchant, such as producers, refiners, roasters, and retailers.

[0131] The above-described configuration allows for the transfer of review NFTs for each vendor. For example, if a user owns review NFTs corresponding to four vendors—the producer, refiner, roaster, and retailer—of a single product, incentives such as purchase points or tokens or the issuance of ID information that serves as proof of the poster's existence can be provided. Specifically, the control unit 61 of the review management server 60 determines whether each user owns review NFTs corresponding to the four vendors—the producer, refiner, roaster, and retailer—of a single product, and grants a predetermined incentive if it determines that the user owns review NFTs corresponding to all four vendors. For example, the control unit 61 issues tokens to users who own review NFTs corresponding to the four vendors, and stores the user's ID (e.g., the poster ID), the date of issuance, and the amount issued in the blockchain system in association with the tokens. Alternatively, incentives can be provided based on the number of vendors for which each user owns review NFTs. In this case, the control unit 61 of the review management server 60 can be configured to identify, for each user, the number of review NFTs owned by the user out of the review NFTs corresponding to the four vendors for one product, and to grant the user an incentive according to the identified number of NFTs owned. The modified examples described in each of the above-described embodiments can also be applied to this embodiment.

[0132] (Embodiment 7) This article describes an information processing system that manages the amount of CO2 (carbon dioxide) emissions from businesses (producers, refiners, roasters, retailers, etc.) at each stage from the coffee production stage to the sales stage (providing stage), and the amount of fertilizer produced from coffee grounds (hereinafter referred to as coffee grounds) generated by retailers (sales stores) after brewing. Coffee grounds are waste discarded after coffee brewing, but they can be recycled as fertilizer (charcoal) by, for example, drying and carbonizing them. Furthermore, by using the fertilizer (charcoal) thus produced on the producer's farm, CO2 can be fixed underground, contributing to CO2 reduction. The information processing system of this embodiment can be realized using the same devices as the information processing system of embodiment 1, and therefore a detailed description of the configuration will be omitted.

[0133] FIG. 29A is a schematic diagram showing an example of the configuration of the production information DB 22a of the seventh embodiment, FIG. 29B is a schematic diagram showing an example of the configuration of the refining information DB of the seventh embodiment, FIG. 29C is a schematic diagram showing an example of the configuration of the roasting information DB of the seventh embodiment, and FIG. 29D is a schematic diagram showing an example of the configuration of the sales information DB. The production information DB 22a shown in FIG. 29A includes a CO2 emission amount column in addition to the configuration of the production information DB 22a of the first embodiment shown in FIG. 5, and stores the amount of CO2 emitted in the production process of the coffee beans identified by the coffee bean ID in association with the coffee bean ID. The CO2 emission amount here may be, for example, the amount of CO2 emission per unit amount of coffee beans, or the total CO2 emission amount in the production process of the coffee beans. The CO2 emission amount for each coffee bean is measured and calculated by each producer and input via the input screen shown in FIG. 7A, and the control unit 21 of the production management server 20 acquires the input CO2 emission amount and stores it in the production information DB 22a and the blockchain system.

[0134] The refining information DB shown in FIG. 29B includes the same configuration as the refining information DB of Embodiment 1 shown in FIG. 6A, but also includes a CO2 emission column, and stores the amount of CO2 emitted in the refining process indicated by the refining process ID in association with the refining process ID. The CO2 emissions for each refining process are measured and calculated by each refiner and entered via the input screen shown in FIG. 7B. The control unit of the refining management server 30 acquires the input CO2 emissions and stores them in the refining information DB and the blockchain system. The roasting information DB shown in FIG. 29C includes the same configuration as the roasting information DB of Embodiment 1 shown in FIG. 6B, but also includes a CO2 emission column, and stores the amount of CO2 emitted in the roasting process indicated by the roasting process ID in association with the roasting process ID. The CO2 emissions for each roasting process are measured and calculated by each roaster and entered via the input screen shown in FIG. 8A. The control unit of the roasting management server 40 acquires the input CO2 emissions and stores them in the roasting information DB and the blockchain system. Furthermore, the sales information DB shown in FIG. 29D includes a CO2 emission column and a recycled fertilizer amount column in addition to the configuration of the sales information DB of embodiment 1 shown in FIG. 6C. The sales information DB stores, in association with a product ID, the amount of CO2 emitted in the sales process of the product indicated by the product ID and the amount of fertilizer generated by reusing coffee grounds generated from the product. The CO2 emission and recycled fertilizer amount for each product are calculated by measuring and calculating the amount of CO2 emission and the amount of fertilizer generated by each retailer and inputting them via the input screen shown in FIG. 8B. The control unit of the sales management server 50 acquires the input CO2 emission and recycled fertilizer amount and stores them in the sales information DB and the blockchain system. Note that each retailer may measure and calculate CO2 emission amounts in any manner, and the amount of recycled fertilizer generated by the retailer may be the amount of coffee grounds used to generate the fertilizer, instead of the amount of fertilizer generated.

[0135] In the information processing system of this embodiment, the poster terminal 70 and the review management server 60 can execute a process similar to the review posting process shown in FIG. 11 . FIG. 30 is a schematic diagram showing an example of a review input screen of the seventh embodiment. In this embodiment, in step S13 in FIG. 11 , the control unit 61 of the review management server 60 acquires, from the blockchain system or each DB, information about the product corresponding to the product information acquired from the poster terminal 70, as well as the CO2 emissions of each supplier. Specifically, the control unit 61 identifies a coffee bean ID, a refining process ID, and a roasting process ID corresponding to the product from the stored contents of the product information DB 62a based on the product information acquired from the poster terminal 70. Then, the control unit 61 acquires, from the production management server 20 or the node device 10, information about the coffee beans associated with the identified coffee bean ID (e.g., producing country, producer), as well as the CO2 emissions in the production process. The control unit 61 also acquires, from the refining management server 30 or the node device 10, the refining information (information about the refining process and the refiner) corresponding to the identified refining process ID, as well as the CO2 emissions in the refining process. Furthermore, the control unit 61 acquires the roasting information (information on the roasting process and roaster) corresponding to the identified roasting process ID, as well as the CO2 emissions in the roasting process, from the roasting management server 40 or the node device 10. Furthermore, the control unit 61 acquires the store information corresponding to the store ID and the menu name corresponding to the product ID included in the product information acquired from the poster terminal 70, as well as the CO2 emissions in the sales process and the amount of recycled fertilizer from the sales management server 50 or the node device 10.

[0136] Then, in step S14, the control unit 61 generates a review input screen as shown in FIG. 30 based on the information acquired as described above. In addition to the configuration shown in FIG. 12B , the review input screen shown in FIG. 30 displays the amount of CO2 emissions emitted by each company (producer, refiner, roaster, and distributor) in the supply chain from production to sale of the product and the amount of fertilizer produced from the coffee grounds generated by the distributor. The review input screen shown in FIG. 30 also displays the total CO2 emissions (CO2 emissions from production to sale) of each company and the amount of fertilizer produced from the coffee grounds, calculated based on the amount of fertilizer produced. The amount of CO2 reduction can be acquired by, for example, referencing a table in which the amount of fertilizer produced from coffee grounds and the amount of CO2 reduction resulting from using the fertilizer are registered in association with each other. Specifically, the control unit 61 of the review management server 60 acquires the amount of recycled fertilizer corresponding to the product from the blockchain system or the sales information DB, and then acquires the amount of CO2 reduction corresponding to the acquired amount of fertilizer by reading it from the table. Furthermore, the control unit 61 may calculate the amount of CO2 reduction corresponding to the amount of fertilizer produced from the coffee grounds of the product, using a formula for calculating the amount of CO2 reduction resulting from using the amount of fertilizer produced from the amount of fertilizer produced. By transmitting this type of review input screen from the review management server 60 and displaying it on the poster terminal 70, the review poster can not only know information about the coffee product they drank, but also the CO2 emissions at each stage from production to sale of the coffee, and further know the amount of CO2 reduction resulting from using the fertilizer produced from the coffee grounds after extraction of the coffee.

[0137] In the information processing system of this embodiment, the viewer terminal 80 and the review management server 60 can execute a process similar to the review viewing process shown in FIG. 13 . In this embodiment, for example, the review viewing screen shown in FIG. 14C may display, for each product corresponding to a review, the CO2 emissions of each vendor from production to sale of the product, the amount of fertilizer produced from coffee grounds generated by the vendor, and the CO2 reduction amount resulting from using the fertilizer. Specifically, in step S40 of FIG. 13 , the control unit 61 of the review management server 60 acquires, from the blockchain system or each DB, the CO2 emissions of each vendor related to the product and the amount of recycled fertilizer for the product, in addition to the review corresponding to the product ID of the product being viewed. The control unit 61 also identifies the CO2 reduction amount corresponding to the acquired amount of recycled fertilizer and displays the CO2 emissions of each vendor and the identified CO2 reduction amount on the review viewing screen. With this configuration, the user can understand, via the viewing screen, the CO2 emissions of each process for the product corresponding to each review and the CO2 reduction amount resulting from the fertilizer produced from coffee grounds. Furthermore, the product menu used in the store may display the CO2 emissions from each process from production to sale of each product, as well as the CO2 reduction achieved by using fertilizer made from the coffee grounds after brewing the coffee. In this case, coffee buyers can decide which product to purchase by considering not only the taste of the coffee, but also the degree of contribution to the global environment.

[0138] The configuration of this embodiment can be applied to the information processing systems of the above-described embodiments 1 to 6, and similar effects can be obtained even when applied to the information processing systems of embodiments 1 to 6. Furthermore, this embodiment can manage the CO2 emissions of each company in the supply chain from coffee product production to sales, as well as the CO2 reduction amount due to the use of fertilizer generated from brewed coffee grounds. This can be confirmed when posting a review, viewing reviews, viewing a product menu, etc. Therefore, people who are considering purchasing a product or who have already purchased a product can understand the degree of contribution to the global environment of the product they plan to purchase or have already purchased. Such a degree of contribution to the global environment can be used as a criterion when selecting a product to purchase. Therefore, this embodiment makes it possible to manage traceability in the coffee product supply chain, including the CO2 emissions of each company.

[0139] In this embodiment, the CO2 emissions at each stage (each trader) from product production to sales are managed, but the present invention is not limited to this configuration. For example, the CO2 emissions reduction amount at each trader may be managed relative to the general CO2 emissions at each stage. In this case, the CO2 emissions reduction amount at each stage from production to sales of each product can be presented, and the degree of contribution to the global environment can be determined based on the CO2 emissions reduction amount. In this embodiment, the modified examples described in each of the above-mentioned embodiments can also be applied as appropriate.

[0140] In each of the above-described embodiments, reviews of products can be collected, and thus consumer evaluations of products can be collected. Therefore, the true value of a product can be determined based on the review content based on the consumer's consumption experience, and the true value evaluated by consumers can be linked to each product in the supply chain. Such true value of a product can be used for future product development.

[0141] In the above-described embodiments, various types of information about coffee are shared among multiple node devices 10 as a blockchain in a blockchain system, but this is not limiting. Various types of information about coffee may also be shared among multiple node devices 10 using a distributed shared ledger technology other than blockchain. Furthermore, various types of information about coffee may also be shared among multiple node devices 10 using a technology other than distributed shared ledger technology. For example, each of the servers 20, 30, 40, 50 and the review management server 60 may broadcast each piece of information to all node devices 10, and each node device 10 may store and accumulate the received information.

[0142] The technology disclosed herein is not limited to coffee, but can also be applied to an information processing system that manages information on the work performed by businesses involved in the production and sale of various products, such as alcoholic beverages (e.g., sake, beer, wine, whiskey), teas (e.g., black tea, Japanese tea, Chinese tea), confectioneries (e.g., chocolate), and luxury goods (e.g., tobacco), and various foods sold in stores and e-commerce sites, as well as customer reviews. The technology disclosed herein can also be applied to an information processing system that manages information on the work performed by businesses involved in the provision of services, such as accommodations, restaurants, entertainment facilities (e.g., amusement parks), barber shops, beauty salons, and relaxation facilities (e.g., massage parlors), and customer reviews. Note that, in this embodiment, coffee beverages and coffee beans are used as examples of products, and various information on businesses involved in the production and sale of the products, such as producers, refiners, roasters, and retailers, is stored in the blockchain system. However, the present invention is not limited to this configuration, and any configuration may be used in which information on businesses involved in the production or manufacturing of a product, from production to sale, is stored in the blockchain system.

[0143] The embodiments disclosed herein are illustrative in all respects and should not be considered limiting. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0144] 10 Node Equipment 20 Production management server 30 Refining Management Server 40 Roasting Management Server 50 Sales management server 60 Review Management Server 70 Poster's Terminal 80 Viewer Devices

Claims

1. Associate an identification code with the object of provision, Based on a blockchain system that stores detailed information about the object to be provided in association with the identification code, read and output the detailed information corresponding to the identification code; Accepting reviews regarding the offering; The received review is stored in the blockchain system in association with the identification code of the subject to be provided; A token is assigned to the review in association with the user who input the review. A process comprising: Determine whether the content of the received review is appropriate; Depending on the result of the determination, whether or not to grant a token to the review is determined. An information processing method in which processing is performed by a computer.

2. Obtain an evaluation value for the content of the review; The amount of tokens to be given is changed according to an evaluation value of the content of the review. The information processing method according to claim 1 , wherein the processing is executed by the computer.

3. Acquire attribute information of the user who input the review; The review and the user's attribute information are stored in the blockchain system in association with the identification code.

3. The information processing method according to claim 1, wherein the processing is executed by the computer.

4. receiving a review request from a provider of the subject to be provided for the review of the subject to be provided; When the viewing request is received, the review about the object to be provided stored in the blockchain system is read based on the blockchain system and output to the terminal of the provider.

3. The information processing method according to claim 1, wherein the processing is executed by the computer.

5. The token for the review is stored in the blockchain system in association with the identification information of the user who input the review.

3. The information processing method according to claim 1, wherein the processing is executed by the computer.

6. Identifying, based on the review, information about an offering that the user who submitted the review is likely to purchase; Output information about the identified target 3. The information processing method according to claim 1, wherein the processing is executed by the computer.

7. A digital ID based on the review is issued in association with the user who input the review.

3. The information processing method according to claim 1, wherein the processing is executed by the computer.

8. A review NFT (Non-Fungible Token) corresponding to the received review is generated on the blockchain system.

3. The information processing method according to claim 1, wherein the processing is executed by the computer.

9. Obtain the CO2 (carbon dioxide) emissions of each company involved in the supply chain of the said target, The acquired CO2 emissions are stored in the blockchain system in association with the identification information of each business.

3. The information processing method according to claim 1, wherein the processing is executed by the computer.

10. Each trader involved in the sale of the object of provision acquires the amount of CO2 reduction due to the utilization of waste associated with the sale of the object of provision, The acquired CO2 reduction amount is stored in the blockchain system in association with the identification information of each trader involved in the sale.

3. The information processing method according to claim 1, wherein the processing is executed by the computer.

11. an association unit that associates an identification code with an object to be provided; an output unit that reads and outputs the detailed information corresponding to the identification code based on a blockchain system that stores detailed information about the object to be provided in association with the identification code; a reception unit that receives reviews related to the subject of provision; a storage processing unit that stores the received review in the blockchain system in association with the identification code of the subject of provision; an assigning unit that assigns a token to the review in association with the user who input the review; a determination unit that determines whether the content of the received review is appropriate; Equipped with The granting unit determines whether or not to grant a token to the review depending on the determination result. Information processing device.

Images