Information processing device, information processing method, and information processing system

Abstract

This information processing device manages assistance to an assisted person in accordance with purchase of goods by a user, on the basis of user identification information for identifying the user, assisted person identification information for identifying the assisted person, and goods identification information for identifying the goods.

Description

Information Processing Apparatus, Information Processing Method, and Information Processing System

[0001] The present technology relates to an information processing apparatus, an information processing method, and an information processing system.

[0002] Conventionally, in commercial transactions for selling products, how to arouse consumers' willingness to purchase products has been an issue. Therefore, an e-commerce method has been proposed to arouse the willingness to purchase products by enabling free shopping for an amount corresponding to the purchase price when a consumer purchases a product (Patent Document 1).

[0003] In addition, there are commercial transactions that arouse fans' willingness to purchase products for the purpose of supporting artists, creators, etc., and sell original contents, goods, etc. of artists, creators, etc.

[0004] Japanese Patent Application Laid-Open No. 2002-197331

[0005] In commercial transactions, it is required to more efficiently arouse consumers' willingness to purchase products. On the other hand, there is a problem that the economic burden and psychological burden increase when fans purchase a large amount of the same product unnecessarily to support artists, creators, etc. Therefore, a mechanism is required that allows fans to easily support creators, artists, etc. without feeling a burden.

[0006] The present technology has been made in view of such problems, and an object thereof is to provide an information processing apparatus, an information processing method, and an information processing system that enable a supported person to be supported by purchasing a product.

[0007] In order to solve the above-described problems, a first technology is an information processing apparatus that manages support for a supported person according to a user's purchase of a product based on user identification information for identifying a user, supported person identification information for identifying a supported person, and product identification information for identifying a product.

[0008] The second technology is an information processing method that manages support provided to a person in response to a user's purchase of a product, based on user identification information that identifies the user, person being supported identification information that identifies the person being supported, and product identification information that identifies the product.

[0009] Furthermore, the third technology is an information processing system comprising a user terminal used by the user to purchase products, and an information processing device that manages support provided to the person being supported in accordance with the user's purchase of products, based on user identification information that identifies the user, person being supported identification information that identifies the person being supported, and product identification information that identifies the product.

[0010] This is a diagram showing an overview of the support service. This is a block diagram showing the configuration of the information processing system 10. This is a diagram showing the processing blocks of the information processing device 100. This is a diagram showing the hardware configuration of the information processing device 100. This is a diagram showing a first example of ID linking in transaction data. This is a diagram showing a first example of the detailed configuration of transaction data. This is a diagram showing a second example of ID linking in transaction data. This is a diagram showing a second example of the detailed configuration of transaction data. This is a diagram showing a user ID and the information associated with it. This is a diagram showing a product ID and the information associated with it. This is a diagram showing a supported person ID and the information associated with it. This is a diagram showing a project ID and the information associated with it. This is a sequence diagram showing the processing in user registration. Figure 14A shows a list of supported persons displayed on the user terminal 200, Figure 14B shows detailed information of supported persons displayed on the user terminal 200, and Figure 14C shows a list of projects displayed on the user terminal 200. This is a diagram showing a GUI for inputting the distribution ratio of the support amount to the project. This is a diagram showing a GUI for inputting the distribution ratio of the support amount to the supported person. Figure 17A shows the notification on the supported terminal 300 that the user has been registered as a target for support, and Figure 17B shows the display of the first content on the user terminal 200. This is an explanatory diagram of the first example of score calculation. This is an explanatory diagram of the second example of score calculation. This is a diagram showing an example of affinity score vectors. This is a sequence diagram showing the process when a user purchases a product. Figure 22A shows the display of a list of products on the user terminal 200, Figure 22B shows the display of detailed product information on the user terminal 200, and Figures 22C and 22D show the display of special support on the user terminal 200. This is a diagram showing the display of the outstanding support amount on the user terminal 200. This is a diagram showing the display of the support result on the supported terminal 300. Figures 25A and 25B show the display of support results on the user terminal 200, and Figure 25C shows the display of ranking information on the user terminal 200. This is a sequence diagram when product recommendation processing is included. This is a sequence diagram showing the process when the target support amount is achieved.

[0011] The embodiments of this technology will be described below with reference to the drawings. The description will be in the following order. <Embodiment> [Overview of the support service] [Configuration of the information processing system 10] [Configuration of the information processing device 100] [Data and information used in the information processing system 10] [Processing in the information processing system 10] [User registration process] [Score calculation process] [Processing when purchasing a product] [Processing when the target support amount is achieved] <Modification>

[0012] <Embodiment> [Overview of Support Services] An overview of the support services implemented by the information processing system 10 will be described with reference to Figure 1.

[0013] The support service is used by users, manufacturers, and beneficiaries through a marketplace operated by the service provider. The marketplace allows users to purchase products by listing product information provided by manufacturers without the service provider holding inventory. The support service allows beneficiaries to receive a portion of the product price as a support amount when a user purchases a product on the marketplace. Support is provided when the beneficiary receives a predetermined support amount relative to the product price. The beneficiary can receive the support amount, for example, by bank transfer.

[0014] The operator is the entity that manages the marketplace and oversees the support provided to beneficiaries through user purchases of products on the marketplace. The operator can be a company, an organization, or an individual.

[0015] A manufacturer is someone who sells products by listing them on a marketplace. Manufacturers can be companies, organizations, or individuals. When a product is sold on the marketplace, the manufacturer receives payment equal to the product price minus a commission. Manufacturers can also sell their products with added value by providing support services, thereby enabling them to help those who need support.

[0016] Users are consumers who purchase goods on the marketplace. By purchasing goods on the marketplace, users can support individuals they have chosen to support. By using the marketplace, users can obtain the goods they purchase and also gain feelings of satisfaction, fulfillment, and happiness from supporting those they support.

[0017] A recipient of support is someone who receives a support amount, which is a portion of the price of a product, when a user purchases a product on the marketplace. By using the support service, recipients can earn a stable income and concentrate on their original activities. Recipients do not have to be individuals; they can also be groups or organizations consisting of multiple people. Specifically, recipients of support include, for example, artists, bands, idols, talents, comedians, YouTubers, actors, writers, manga artists, artists, film directors, television producers, video creators, animators, illustrators, voice actors, game creators, programmers, manga and anime characters, mascot characters, companies, NPOs and organizations, animals kept in zoos, and protected and managed wild animals. However, it is not limited to people; anything that can be supported financially is acceptable.

[0018] In recent years, the concept of "oshi" (favorite / favorite idol / artist) has become more widely recognized, and "oshi-katsu" (favorite activity), where fans diligently attend events and purchase merchandise to support their favorite artists, has become commonplace. However, fans sometimes purchase large quantities of the same CDs and merchandise unnecessarily to support their favorite artists, which can lead to significant financial and psychological burdens.

[0019] In recent years, artists and other performers have faced the problem of reduced income due to the free or low-price distribution of content and low royalties from subscription services. On the other hand, merchandise such as T-shirts and towels are said to have higher profit margins than music and videos, and are a major source of income for artists. However, there are also problems such as artists and other performers having to expend effort and time on the production of merchandise, which is not their core activity, and the fact that merchandise does not always sell as well as artists and other performers expect.

[0020] This technology solves these problems, allowing fans to support their favorite artists (the recipients of support) without having to purchase unnecessary items, simply by purchasing the items they need.

[0021] Furthermore, there is no need for any relationship between the products sold on the marketplace and the beneficiaries who receive support from users. The products can be anything that is subject to commercial transactions, such as daily necessities, food products, miscellaneous goods, beverages, clothing, precious metals, electronic devices, home appliances, sporting goods, toys, automobiles, and various content and data such as videos, music, and games, which have no relation to the beneficiaries. Regardless of what product a user purchases from the marketplace, the beneficiaries supported by the user will receive a portion of the product's price as support.

[0022] [Configuration of Information Processing System 10] The configuration of the information processing system 10 will be described with reference to Figure 2. The information processing system 10 consists of an information processing device 100, a user terminal 200, a supported person terminal 300, and a manufacturer terminal 400.

[0023] The user terminal 200, the supported terminal 300, and the manufacturer terminal 400 are each connected to the information processing device 100 via a network. In Figure 2, one of each is shown for the user terminal 200, supported terminal 300, and manufacturer terminal 400, but in reality, multiple user terminals 200, multiple supported terminals 300, and multiple manufacturer terminals 400 are connected to the information processing device 100. Technically, there is no limit to the number of user terminals 200, supported terminals 300, and manufacturer terminals 400.

[0024] The user terminal 200 is used by the user to access the marketplace and support services. The user terminal 200 comprises at least a control unit 201, a display unit 202, an input unit 203, a communication unit 204, and a storage unit 205.

[0025] The control unit 201 consists of a CPU (Central Processing Unit), RAM (Random Access Memory), and ROM (Read Only Memory). The CPU controls the entire user terminal 200 and its individual components by executing various processes and issuing commands according to the program stored in the ROM.

[0026] The display unit 202 is a liquid crystal display or an organic EL (Electro-Luminescence) display that displays a GUI (Graphical User Interface) for using the marketplace, content such as messages, images, and videos, and a web browser.

[0027] The input unit 203 is, for example, various operators and operating devices such as a keyboard, mouse, keys, dial, touch panel, touchpad, or remote controller. User operations are detected by the input unit 203, and the signals corresponding to the input operations are interpreted by the control unit 201.

[0028] The communication unit 204 is a communication interface for connecting to a network. The communication method can be either wired or wireless. Possible communication methods include cellular communication, 4G, 5G, Wi-Fi, Bluetooth®, NFC (Near Field Communication), Ethernet®, HDMI® (High-Definition Multimedia Interface), and USB (Universal Serial Bus). It is desirable that the communication be encrypted using TLS (Transport Layer Security) or SSL (Secure Sockets Layer).

[0029] The storage unit 205 is a large-capacity storage medium composed of, for example, a hard disk, an SSD (Solid State Drive), or flash memory. Applications for using the marketplace and other data are stored in the storage unit 205.

[0030] The supported user terminal 300 is used by the supported user to access the marketplace and support services. The supported user terminal 300 comprises at least a control unit 301, a display unit 302, an input unit 303, a communication unit 304, and a storage unit 305. The configuration of each unit is the same as that of the user terminal 200. It should be noted that the supported user does not necessarily have to perform the input operations on the supported user terminal 300; the input operations may be performed by the supported user's administrator, manager, caretaker, or other person who manages or supports the supported user.

[0031] The manufacturer terminal 400 is used by manufacturers to access the marketplace and support services. The manufacturer terminal 400 comprises at least a control unit 401, a display unit 402, an input unit 403, a communication unit 404, and a storage unit 405. The configuration of each unit is the same as that of the user terminal 200.

[0032] The user terminal 200, the supported person terminal 300, and the manufacturer terminal 400 may be, for example, a smartphone, tablet, personal computer, or wearable device, but they may also be dedicated terminals for using the support services provided by the information processing system 10.

[0033] [Configuration of Information Processing Device 100] The processing blocks of the information processing device 100 will be described with reference to Figure 3. The information processing device 100 is used by operators who run a marketplace and provide support services to manage the support provided to beneficiaries in response to product purchases by users. Note that processing related to the operation and management of the marketplace itself is performed by a processing device separate from the information processing device 100.

[0034] The transmitting / receiving unit 101 uses the communication function of the information processing device 100 to perform data, information, content, and other transmission and reception processing between the user terminal 200, the supported terminal 300, and the manufacturer terminal 400.

[0035] The data management unit 102 performs processing related to the data and information handled by the information processing device 100, such as associating IDs used by the information processing device 100 with various data and information, registering data and information in the database 110, reading data and information from the database 110, verifying data and information associated with IDs, and searching for information in the database 110.

[0036] The transaction data generation unit 103 generates transaction data used for managing support provided by the information processing device 100. Based on the transaction data, the information processing device 100 manages the support provided to the person receiving support in accordance with the user's purchase of goods.

[0037] The score processing unit 104 calculates various scores used for managing support provided by the information processing unit 100. These scores include the support recipient affinity score, social contribution score, product affinity score, user attribute score, and affinity score vector.

[0038] The support amount management unit 105 performs processing related to the support amount, such as calculating the support amount based on the distribution ratio, adding the support amount, and determining whether the target support amount has been achieved.

[0039] The database 110 includes a transaction database 111, a user database 112, a product database 113, a supported person database 114, a project database 115, and a score vector database 116.

[0040] The transaction database 111 stores transaction data and various data associated therewith. The user database 112 stores a user ID and various information associated therewith. The product database 113 stores a product ID and various information associated therewith. The supported person database 114 stores a supported person ID and various information associated therewith. The project database 115 stores a project ID and various information associated therewith. The score vector database 116 stores score vectors. Note that the database 110 may be provided in the information processing apparatus 100, or may be configured in an external storage device outside the information processing apparatus 100, and the information processing apparatus 100 may be configured to access the external storage device.

[0041] Next, referring to FIG. 4, the hardware configuration of the information processing apparatus 100 will be described.

[0042] The CPU 151 functions as an arithmetic processing unit that performs various processes, and controls the entire information processing apparatus 100 and each part thereof. The CPU 151 executes various processes according to a program stored in the ROM 152 or a program loaded from the storage unit 160 to the RAM 153. In the RAM 153, data and the like necessary for the CPU 151 to execute various processes are appropriately stored. Each processing block constituting the information processing apparatus 100 can be realized by a processor constituted by the CPU 151, the ROM 152, and the RAM 153 executing a program.

[0043] The CPU 151, the ROM 152, and the RAM 153 are interconnected via a bus 154, and the bus 154 is connected to a bridge 155.

[0044] An interface 157 is connected to the bridge 155 via a bus 156.

[0045] An input unit 158, a display unit 159, a storage unit 160, a drive 161, a connection port 162, and a communication unit 163 are connected to the interface 157.

[0046] The input unit 158 is various operators and operation devices such as a keyboard, a mouse, keys, a dial, a touch panel, a touch pad, a remote controller, etc. The operation of the user is detected by the input unit 158, and the signal corresponding to the input operation is interpreted by the CPU 151.

[0047] The display unit 159 is a liquid crystal display, an organic EL display, etc. that display GUIs, contents such as messages, images, and videos.

[0048] The storage unit 160 is a large-capacity storage medium such as a hard disk or a flash memory. Various applications, data, information, etc. are stored in the storage unit 160. Various databases for storing data in the information processing apparatus 100 can be constituted by the storage unit 160. The database 110 can be constituted by the storage unit 160.

[0049] A removable storage medium 164 can be connected to the information processing apparatus 100 via the drive 161. The removable storage medium 164 includes a USB flash memory, an SD memory card, a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc.

[0050] The drive 161 can read data files such as programs used for each process from the removable storage medium 164. The read data file is stored in the storage unit 160. Also, programs etc. read from the removable storage medium 164 are installed in the storage unit 160 as necessary. Furthermore, the information processing apparatus 100 may transfer information and data to an external device via the removable storage medium 164.

[0051] An external connection device 165 can be connected to the information processing apparatus 100 via the connection port 162.

[0052] The communication unit 163 includes various communication terminals and communication modules for communication processing via networks such as the Internet, and communication with various devices via wired / wireless communication, bus communication, etc. The information processing device 100 can be connected to a user terminal 200, a supported person terminal 300, and a manufacturer terminal 400 via the communication unit 163. The communication method can be either wired or wireless. Communication methods include cellular communication, 4G, 5G, Wi-Fi, Bluetooth®, NFC, Ethernet®, HDMI®, USB, etc.

[0053] Other external devices can be connected via connection port 162 or communication unit 163.

[0054] Note that the information processing device 100 does not need to have all the configurations shown in Figure 4. For example, if the information processing device 100 only performs processing and outputs the processing results to the outside, the display unit 159 is not necessary.

[0055] In the information processing device 100, a program for processing this technology can be installed via network communication by the communication unit 163 or via a removable storage medium 164. Alternatively, the program may be pre-stored in the ROM 152, storage unit 160, etc.

[0056] The information processing device 100 may be configured as a standalone device, or it may be composed of electronic devices having information processing and communication functions, such as a server, personal computer, smartphone, or tablet terminal. Alternatively, the information processing device 100 and the information processing method may be realized by an electronic device with computer functions executing a program. The program may be pre-installed on the electronic device, or it may be distributed via download or storage media for users to install.

[0057] The functions realized by the components described herein may be implemented in a circuit or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), CPUs, conventional circuits, and / or combinations thereof, programmed to realize the described functions. A processor, including transistors and other circuits, is considered a circuit or processing circuitry. A processor may be a programmed processor that executes a program stored in memory. In this specification, circuitry, unit, and means are hardware programmed to realize or execute the described functions. Such hardware may be any hardware disclosed herein, or any hardware known to be programmed to realize or execute the described functions. If such hardware is a processor that is considered a type of circuitry, then such circuitry, means, or unit is a combination of hardware and software used to constitute such hardware and / or processor.

[0058] The information processing device 100 may be configured on a cloud server. The cloud server is not limited to being composed of a single computer device, but may be composed of a system of multiple computer devices. The multiple computer devices are systematized, for example, by a LAN (Local Area Network). Alternatively, multiple computer devices located in remote locations may be systematized by a VPN (Virtual Private Network) using the Internet, etc. The multiple computer devices may include computer devices that constitute a group of servers (cloud) available through cloud computing services.

[0059] The information processing system 10 is configured as described above.

[0060] [Data and Information Used in Information Processing System 10] Next, we will explain the various types of data and information used in Information Processing System 10. First, we will explain the structure of transaction data.

[0061] Transaction data is generated by the information processing device 100 each time a user purchases an item on the marketplace. Transaction data is generated by the information processing device 100 for each item purchase (purchase payment). Therefore, if multiple items are purchased in a single transaction, multiple item IDs will be associated with a single transaction data. In other words, for example, if three units of item A and one unit of item B are purchased in a single transaction, one transaction data will be generated containing information such as "item A, quantity purchased: 3" and "item B, quantity purchased: 1".

[0062] Transaction data may be generated for each purchase of the same product by the same user. In that case, if the same user purchases multiple different products in a single purchase transaction, the same number of transaction data entries will be generated as the number of product types. For example, if the same user purchases product A and product B in a single purchase transaction, two transaction data entries will be generated: one for product A and one for product B. Also, if the same user purchases multiple identical products in a single purchase transaction, one transaction data entry will be generated.

[0063] Figure 5 shows a first example of how various IDs are linked in transaction data. In this first example, the transaction ID is linked to the user ID and the product ID. Additionally, the user ID is linked to the recipient ID, and the recipient ID is linked to the project ID.

[0064] A transaction ID is an identifier used to identify transaction data.

[0065] The User ID is identification information used to identify users who utilize the marketplace and support services.

[0066] A product ID is an identifier used to identify products sold on the marketplace or products purchased by users.

[0067] The recipient ID is identification information used to identify the recipient of support services.

[0068] The Project ID is identification information used to identify a project set up by the supporter. A project is a specific activity or activity for which the supporter wishes to receive support. Examples of projects include the production of content (music, music videos, movies, books, etc.), the holding of live performances or events, and advertising through ad trucks, billboards, or street screens. However, any project related to the supporter's activities or life, and for which the supporter desires support from users, is acceptable. A supporter can set up multiple projects, and there is no technical limit to the number of projects. The information processing device 100 manages support for the supporter's projects based on the Project ID.

[0069] Figure 6 shows the detailed structure of the transaction data in the first example described above. In addition to the user ID, product ID, supporter ID, and project ID mentioned above, the transaction data can include various other pieces of information. In the example in Figure 6, the transaction data includes the support amount, number of items purchased, source of purchase, transaction date and time, payment method, payment amount, media used, and other transaction information.

[0070] Each beneficiary ID is associated with the amount of support the beneficiary receives from the user's purchase of a product. The support amount is a predetermined amount set by the manufacturer for each product. Furthermore, if a user supports multiple beneficiaries, the support amount will be calculated by the information processing device 100 based on the amount predetermined by the manufacturer for each product and a distribution ratio arbitrarily set by the user. The distribution ratio is the percentage that indicates how the support amount will be divided among multiple beneficiaries when a user supports multiple beneficiaries.

[0071] The project ID is associated with the amount of support the project receives from the user's purchase of a product. The support amount is a predetermined amount set by the manufacturer for each product. If a user supports multiple projects, the support amount will be calculated by the information processing device 100 based on the amount predetermined by the manufacturer for each product and the distribution ratio arbitrarily set by the user.

[0072] For example, suppose a support amount of 100 yen is set for product A, and a user supports recipient A and project A of recipient A. In this case, the support amount associated with the recipient ID will be 100 yen, and the support amount associated with the project ID will also be 100 yen.

[0073] For example, suppose a support amount of 100 yen is set for product A, and a user supports beneficiary A and project A, and beneficiary B and project B. Suppose the user sets a distribution ratio of 60% for project A supported by beneficiary A, and a distribution ratio of 40% for project B supported by beneficiary B. In this case, the support amount associated with beneficiary A's beneficiary ID will be 60 yen, and the support amount associated with project ID of project A will also be 60 yen. Also, the support amount associated with beneficiary B's beneficiary ID will be 40 yen, and the support amount associated with project ID of project B will also be 40 yen.

[0074] For example, suppose a support amount of 100 yen is set for product A, and a user supports recipient A, project A1, and project A2. The user sets the distribution ratio for the projects to be 60% for project A1 and 40% for project A2. In this case, the support amount associated with recipient ID will be 100 yen, the support amount associated with project ID A1 will be 60 yen, and the support amount associated with project ID A2 will be 40 yen.

[0075] For example, suppose a support amount of 100 yen is set for product A, and a user supports recipient A, project A1 and project A2, and recipient B, project B. Suppose the user sets a distribution ratio of 50% for project A1 of recipient A, 10% for project A2, and 40% for project B of recipient B. In this case, the support amount associated with recipient A's recipient ID will be 60 yen, the support amount associated with project A1's project ID will be 50 yen, and the support amount associated with project A2's project ID will be 10 yen. Also, the support amount associated with recipient B's recipient ID will be 40 yen, and the support amount associated with project B's project ID will also be 40 yen.

[0076] The number of items purchased is linked to the product ID and indicates the number of identical items purchased by the user. Since support is provided to the supporter based on a pre-set support amount relative to the product price, a larger number of items purchased will result in a larger support amount. For example, if a user purchases five items with a support amount of 100 yen each, the support amount will be 500 yen.

[0077] The traffic source is linked to the product ID and represents information indicating the path a user takes to access the marketplace, including applications, external links, and delivery screens.

[0078] The transaction date and time is the date and time the user purchased the item on the marketplace.

[0079] The payment method is the method used by the user when purchasing goods on the marketplace. Payment methods include credit card payments, bank transfers, online banking payments, convenience store payments, and electronic money payments.

[0080] The payment amount is the amount paid by the user when purchasing an item on the marketplace.

[0081] The "usage medium" refers to the medium that a user uses to purchase products on the marketplace, such as applications, web browsers, and APIs (Application Programming Interfaces).

[0082] Figure 7 shows a second example of how various IDs are linked in transaction data. In this second example, the user ID and product ID are linked to the transaction ID, but the recipient ID and project ID are not.

[0083] As will be explained later with reference to Figure 9, in the user database 112, the user ID is associated with the supported person ID of the person the user supports and the project ID of the project the user supports. In the second example, the supported person ID and project ID are not associated with the transaction data ID, and the information processing device 100 identifies the supported person ID and project ID by referring to the user database 112 based on the user ID in the transaction data. Thus, the supported person ID and project ID are not essential elements in the transaction data.

[0084] In the second example of transaction data, as in the first example, various information can be included in the transaction data. As shown in Figure 8, unlike the first example, in the second example, the support amount is linked to the transaction ID. This is based on the assumption that the support amount linked to the product ID registered in the product database 113 is variable data that can be changed at any time at the manufacturer's discretion. For example, if a user purchases a product with a support amount of 50 yen, and then the manufacturer changes the support amount of that product to 10 yen, the information processing device 100 may process the transaction as if the support amount were 10 yen, even though the user was attracted to the product with a support amount of 50 yen. To prevent this, the support amount, which is an expression of the user's intention, is included in the transaction data as a fixed value at least when the transaction data is generated.

[0085] Other information associated with the transaction ID is the same as in the first example.

[0086] By associating various IDs and information with the transaction ID in this way, the information processing device 100 can manage appropriate support for each transaction in accordance with the user's intentions, based on the transaction data.

[0087] Next, we will explain the user IDs registered in the user database 112. As shown in Figure 9, each user ID is linked to the support recipient ID, distribution ratio, outstanding project support amount, project ID, user attributes, cumulative support amount, outstanding support amount, and personal information.

[0088] The Supporter ID is identification information that identifies the supporter being supported by the user. The Supporter ID is linked to the distribution ratio of the support amount to that supporter. The distribution ratio indicates how the support amount will be divided among multiple supporters when the user supports multiple supporters. When a user supports only one supporter, the support amount set for the product becomes the amount of support for that supporter. When a user supports only one supporter, the user does not need to set a distribution ratio.

[0089] The Project ID is an identifier that identifies the project a user is supporting. The Project ID is linked to the distribution ratio of the support amount for that project. The distribution ratio indicates how the support amount will be divided among multiple projects if the user supports several projects. If a user supports only one project, the support amount set for the product becomes the support amount for that project. When a user supports only one project, they do not need to set a distribution ratio.

[0090] User attributes are information about a user's characteristics. These attributes can include age, gender, occupation, family structure, residence, current address, annual income, consumption patterns, purchase history, etc., but any information relating to the user is acceptable.

[0091] The cumulative support amount is the total amount of support provided by the user to date. While the cumulative support amount is the sum of all support provided by the user to date, it may also include the total amount of support provided by the user to each individual recipient.

[0092] Unprocessed support amounts represent the total amount of support provided by a user for product purchases that has not yet been processed as support for the recipient. Unprocessed support amounts arise when a user purchases a product before registering the recipient they are supporting.

[0093] The unprocessed project support amount is the total amount that has been processed as support for a recipient but has not been processed as support for a project. This amount arises when a user has registered a recipient but has not registered a project to support. For example, this can occur if a registered project has reached its funding goal and new support is no longer accepted. The unprocessed project support amount is recorded in conjunction with the "recipient ID linked to the user ID."

[0094] The outstanding support amount and outstanding project support amount are finalized as a support amount when the user registers the support recipient ID and project ID at any time.

[0095] Personal information refers to information about the user other than the various types of information mentioned above.

[0096] The registration process for the user ID, the supported person ID associated with the user ID, the project ID, and user attributes will be described later.

[0097] Next, we will explain the product IDs registered in the product database 113. As shown in Figure 10, each product ID is associated with product information, price, regular support amount, special support information, recipient affinity score, manufacturer ID, social contribution score, product genre, and other information.

[0098] Product information refers to information about a product, such as its name, photos, description, usage instructions, ratings, reviews, and related products. However, any information necessary for selling on the marketplace is acceptable.

[0099] The price is the selling price of the product on the marketplace.

[0100] The standard support amount is the normal support amount set for a product and is different from the special support amount. The standard support amount can be determined by the manufacturer. In this specification, when simply referred to as "support amount," it means the standard support amount. Manufacturers can change the standard support amount while the product is listed. The standard support amount may be a specific amount or a percentage of the product price, such as "20% of the price."

[0101] Special support information refers to information about special support provided to recipients with a support amount different from the usual support amount. This special support information includes the special support recipient ID, special user attributes, and special support amount.

[0102] The Special Support Recipient ID is identification information used to identify recipients who are eligible for special support and who are entitled to receive special support (hereinafter sometimes referred to as "Special Support Recipients"). Special Support Recipients may be determined by the manufacturer or the operator.

[0103] Special user attributes refer to the attributes of users who are eligible for special support (hereinafter sometimes referred to as "special users") and who can purchase products to which special support amounts are applied. Special user attributes may include, for example, the person being supported, age, gender, occupation, family structure, residence, place of residence, annual income, consumption trends, purchase history, etc., but any information related to the special user is acceptable. Special users may be determined by the manufacturer or the operator.

[0104] The special support amount is a higher amount than the regular support amount. The special support amount can be any amount higher than the regular support amount. The manufacturer can determine the special support amount. The manufacturer can change the special support amount while the product is listed for sale. The special support amount can be a specific amount or a percentage of the product price.

[0105] Special support can be targeted at the recipient of support or at the user. By identifying the recipient of special support using the recipient's ID, even if user A, who supports recipient A, and user B, who supports regular recipient B, purchase the same product, recipient A can receive a higher amount of special support than regular recipient B would receive.

[0106] This makes it possible, for example, for a manufacturer to designate a specific supporter as a "special supporter" when selling a collaborative product. If that collaborative product is purchased, the special supporter can receive a higher amount of special support than the regular support amount received by other supporters.

[0107] Furthermore, by identifying special users who are eligible for special support based on special user attributes, even if special user A, who supports recipient A, and regular user B, who also supports recipient A, purchase the same product, the amount of support provided to recipient A through special user A's product purchase can be higher than the amount provided through regular user B's product purchase.

[0108] This means that, for example, if the main target audience for product A is women in their 30s, it becomes possible to offer a special support amount only when a woman in her 30s purchases product A. In this way, special support can stimulate the purchasing intent of users with specific attributes.

[0109] The manufacturer selects whether to set the support amount for the product as a standard support amount or a special support amount, and transmits the selection information from the manufacturer's terminal 400 to the information processing device 100. The information processing device 100 switches the support amount accordingly. The manufacturer can switch the support amount from a standard support amount to a special support amount at any time during the product listing period, and conversely, can also switch the support amount from a special support amount to a standard support amount. In the case of special support, the manufacturer needs to input information indicating the special support recipient or transmit information indicating the special user who is eligible for special support to the information processing device 100.

[0110] When identifying users eligible for special support based on user attributes, a notification such as "You are eligible for special support" may be displayed on the user terminal 200 when that user accesses the marketplace. Alternatively, when identifying recipients eligible for special support based on their special support recipient ID, a notification such as "The artist you support is eligible for special support" may be displayed on the user terminal 200 when a user who has registered that recipient as a support recipient accesses the marketplace.

[0111] The recipient affinity score is a score that indicates the affinity between the product and the recipient.

[0112] The manufacturer ID is identification information used to identify manufacturers selling products on the marketplace.

[0113] Each manufacturer ID is linked to a social contribution score. The social contribution score is a numerical representation of the manufacturer's contribution to society. For example, the social contribution score may be calculated by the information processing device 100 based on information provided by the manufacturer demonstrating its contribution to society, or it may be calculated by an operator or a company or organization conducting a review based on predetermined criteria. Information demonstrating a contribution to society may include donation records, volunteer activity records, and efforts toward SDGs (Sustainable Development Goals), but any information that can showcase the manufacturer's social contribution is acceptable.

[0114] The product category is information that indicates the category to which a product belongs. Product categories include, for example, food, beverages, clothing, miscellaneous goods, daily necessities, precious metals, electronic devices, home appliances, sporting goods, toys, games, automobiles, and various data such as videos, music, and games, but any category to which a product sold on the marketplace belongs is acceptable.

[0115] When a manufacturer registers for a support service or lists a product on the marketplace, they are required to provide the information processing device 100 with product information, price, standard support amount, special support information, manufacturer ID, and product category. All of this information can be added, deleted, or changed later. The product ID and manufacturer ID may be assigned by the operator, or set by the manufacturer using any string of characters.

[0116] Next, we will explain the supporter IDs registered in the supporter database 114. As shown in Figure 11, the supporter ID is linked to supporter information, project ID, product affinity score, user attribute score, cumulative support amount, ineligible product information, number of supporters, first content, payment destination information, and personal information.

[0117] Supporter information refers to information about the supporter, including name, photo, genre, age, gender, activity history, published works, portfolio, media coverage, and SNS (Social Networking Service) links, but any information relating to the supporter is acceptable.

[0118] The project ID is identification information used to identify the project set up by the recipient of the support.

[0119] The product affinity score is a score that indicates the affinity between the recipient and the product.

[0120] The user attribute score is a score that indicates the affinity between the attributes of the supported person and the user. The user attribute score is information that shows what kind of users are supporting the supported person, that is, what kind of fans the supported person has. The user attribute score can be scores for various attributes such as age, gender, occupation, family structure, residence, place of residence, annual income, consumption trends, and purchase history, but any information about the users who support the supported person is acceptable.

[0121] The cumulative amount of support received is the total amount of support the recipient has received to date.

[0122] Information on excluded products refers to information indicating specific products that the recipient will not receive support for. Recipients can arbitrarily designate excluded products. Excluded products can be specified by manufacturer, manufacturer's genre, product type, specific product name, product ID, price, ESG (Environment, Social, Governance) score, support amount, social contribution score, etc.

[0123] If a user purchases an item on the marketplace but that item is not eligible, the information processing device 100 will not process the amount of support for that item as support for the recipient.

[0124] By specifying excluded products by manufacturer, it becomes possible, for example, for a supported person appearing in a commercial for beverage manufacturer A to be ineligible for support through the purchase of beverage manufacturer B's products. Similarly, by specifying excluded products by type, it becomes possible, for example, for a supported person appearing in a commercial for beverage manufacturer A's beer to be ineligible for support through the purchase of beverage manufacturer B's beer. In this case, the supported person can still receive support through the purchase of other products sold by beverage manufacturer B besides beer.

[0125] Furthermore, manufacturers and products that are morally inappropriate for receiving support can be excluded. For example, if the recipient is a minor, they can specify "alcohol" as an excluded product, thus preventing them from receiving support through the purchase of alcohol.

[0126] Furthermore, by specifying excluded items based on their price or the amount of support provided, it becomes possible, for example, to exclude support for the purchase of expensive items or large amounts of support if the recipient is a minor. The price or support amount can be specified as a specific amount, a maximum of a specific amount, or as a range.

[0127] Furthermore, information on excluded products can include information on exceptional manufacturers. Exceptional manufacturers are those that are exempt from the exclusion of products, meaning they are not excluded and can receive support. By specifying exceptional manufacturers, it becomes possible to specify that support will not be received for purchasing certain types of products, but support will be received for purchasing products from a specific manufacturer (exceptional manufacturer). For example, if all beverages are specified as excluded products under "Product Type," and beverage manufacturer A, for which the recipient is an advertiser, is specified as an exceptional manufacturer, then the recipient will not receive support for purchasing beverages from manufacturers other than manufacturer A, but will receive support for purchasing beverages from manufacturer A. Specifying all products and manufacturers that will not receive support in this way, and only specifying manufacturers that will receive support as exceptions, makes it easier to input information on excluded products. Note that exceptional manufacturers can also be specified when excluding products based on specific prices, specific ESG scores, specific support amounts, or specific social contribution scores, not just specific products.

[0128] The number of supporters is the total number of users who support the person being supported.

[0129] The first content is content provided to the user as a reward for registering as a support recipient. The first content is not mandatory, but providing it can increase the user's motivation to provide support. The first content may be, for example, video, images, audio, text, distribution links, or discount coupons for merchandise or events, and may consist of one of these or a combination of several. The first content may store the support recipient database 114, or a content database for content storage may be provided, and the first content may be read from the content database based on the ID attached to the content.

[0130] Recipient information refers to details such as the payment method, financial institution, and account number used by the recipient to receive the support funds.

[0131] Personal information refers to information about the individual receiving support, excluding information about the person receiving support.

[0132] When a recipient of support registers for the support service, they are required to provide the information processing device 100 with recipient information, information on excluded products, the first content, payment destination information, and personal information. Information on excluded products is not mandatory. If the recipient receives support from the purchase of all products, they do not need to provide information on excluded products. All of this information can be added, deleted, or changed later. The recipient ID may be assigned by the operator, or the recipient may set it with any string of characters.

[0133] Next, we will explain the project ID stored in the project database 115. As shown in Figure 12, the project ID is associated with project information, cumulative support amount, target support amount, second content, co-supported person ID, period, and progress information. Note that the project ID may also be stored in the supporter database 114.

[0134] Project information refers to information about a project, such as its name, content, purpose, scale, and location, but any information related to the project is acceptable.

[0135] The cumulative amount of support received is the total amount of support the project has received to date.

[0136] The target funding amount is the amount of funding the project aims to receive. The recipient of funding can set the final target funding amount as the amount necessary to execute the project. In addition to the final target funding amount, the recipient can also set intermediate target funding amounts. Intermediate target funding amounts are amounts that can be set below the final target funding amount, and any amount below the final target funding amount is acceptable. Multiple intermediate target funding amounts may be set.

[0137] The target funding amount is associated with a second type of content that will be provided to users who have contributed if the total amount of support reaches the target amount. This second type of content is for the recipients to express their gratitude to the users for achieving the project's funding goal.

[0138] If a supporter sets one or more intermediate support goals in addition to their final support goal, they can also associate each goal with a different type of secondary content. For example, if the supporter is an artist or idol, the secondary content corresponding to the intermediate support goal could be an image or text message, while the secondary content corresponding to the final support goal could be a video message or a link to a live stream on a video sharing site, which is considered to be more valuable than an image or text message. This can increase the user's motivation to support the supporter.

[0139] The Co-Supported Person ID is identification information used to identify co-supported persons. A co-supported person is a person other than a specific supported person among multiple supported persons involved in the same project. There is no limit to the number of co-supported persons. However, the distribution of support funds is limited to the supported persons indicated by the supported person ID associated with the transaction ID.

[0140] For example, in an idol group, band, or theater troupe with multiple members, if each member has a supporter ID, each member can designate other members as co-supporters.

[0141] For example, when multiple beneficiaries, such as a director, screenwriter, and actor, are involved in the production of a film, and each of them has a beneficiary ID, each beneficiary can designate other beneficiaries as co-beneficiaries.

[0142] By specifying co-supported individuals using their co-supported individual IDs, multiple supporters can work on the same project. By linking the co-supported individual IDs to the project ID, each of the multiple supporters can serve as a point of contact for support on a single project.

[0143] The duration is the period during which users can support a project. The duration can be set by date, or by date and time.

[0144] Progress information is information that shows the progress of a project. Progress can be shown as a percentage of the total project completion (100%), or it can be shown by dividing the project into multiple stages and indicating whether each stage has been completed or not. Alternatively, project progress can be shown using text or photographs.

[0145] When a recipient of support registers for the support service, they are required to provide the information processing device 100 with project information, target support amount, duration, and, if applicable, the IDs of co-recipients. All of this information can be added, deleted, or changed later. The project ID may be assigned by the operator or set by the recipient using any string of characters.

[0146] [Processing in Information Processing System 10] [User Registration Process] Next, the user registration process will be explained with reference to Figure 13. In the user registration process, the user ID, user attributes, the person the user supports, the project the user supports, and the distribution ratio of the support amount are registered. The user registration process is performed by the transmission / reception unit 101 and the data management unit 102.

[0147] First, when the user inputs a string that is a candidate for the user ID and user attributes into the user terminal 200, in step S101, the user terminal 200 transmits the candidate user ID and user attributes to the information processing device 100. To allow the user terminal 200 to input the candidate user ID and user attributes, it is preferable to display an input form that shows the input fields.

[0148] Then, in step S102, the information processing device 100 registers the candidate user ID as a unique user ID for that user in the user database 112. The information processing device 100 also associates user attributes with the user ID and registers them in the user database 112.

[0149] If a candidate user ID is already in use by another user or is inappropriate, the information processing device 100 may instruct the user via the user terminal 200 to enter a different candidate user ID. Alternatively, the information processing device 100 may determine a string to be a candidate user ID, send it to the user terminal 200, and if the user accepts it, register the candidate user ID as a unique user ID for that user in the user database 112.

[0150] Next, in step S103, the information processing device 100 transmits the support recipient IDs and list display information for all support recipients registered in the support recipient database 114 to the user terminal 200. Then, in step S104, as shown in Figure 14A, the user terminal 200 displays the received list display information. The list display information may include, for example, a photo of the support recipient, their name, and the number of supporters. The information processing device 100 reads this information linked to the support recipient ID in the support recipient database 114 and transmits it to the information processing device 100. However, this list display is merely an example, and other information may be displayed in the list display.

[0151] When a user enters information for a search for a supported person, in step S105, the user terminal 200 requests information for displaying a list of supported persons according to the search content from the information processing device 100. In step S106, the information processing device 100 transmits the IDs of supported persons and the information for displaying the list according to the search content to the user terminal 200. Then, in step S107, the user terminal 200 displays the received information for displaying the list. Supported persons can be searched by name, genre, etc. Furthermore, the display of supported persons may be sorted by alphabetical order, popularity, rating, etc.

[0152] When the user inputs a selection of a person to be supported to the user terminal 200, in step S108 the user terminal 200 requests detailed information of the person to be supported selected by the user from the information processing device 100. In step S109 the information processing device 100 sends the person to be supported ID and detailed information of the selected person to the user terminal 200.

[0153] Then, in step S110, as shown in Figure 14B, for example, the user terminal 200 displays detailed information about the selected supporter. This detailed information may include, for example, genre, activity history, published works, and SNS links. The information processing device 100 reads this information, which is linked to the supporter ID, from the supporter database 114 and transmits it to the information processing device 100. However, this display of detailed information is merely an example, and other information may be displayed as detailed information.

[0154] When the user inputs to the user terminal 200 to determine the person to be supported, in step S111, the user terminal 200 transmits the person to be supported ID and user ID, which indicate the person to be supported selected by the user, to the information processing device 100.

[0155] Next, in step S112, the information processing device 100 associates the received user ID with the supported person ID and registers it in the user database 112. This registers the supported persons that the user will support. The information processing device 100 also updates the number of supported persons in the supported person database 114 by incrementing the number of supporters associated with the supported person ID.

[0156] Next, in step S113, the information processing device 100 reads the project ID and project list display information for the project of the supported person that the user is supporting from the project database 115 and sends it to the user terminal 200. In step S114, as shown in Figure 14C, the user terminal 200 displays a list of projects. The information for displaying the project list includes, for example, the project, name, content, target amount, period, and cumulative support amount. However, this list display is merely an example, and other information may be displayed in the list display. If the supported person selected by the user has set up multiple projects, the information processing device 100 sends the project ID and project information for all projects to the user terminal 200, and the user terminal 200 displays a list of all projects.

[0157] When a user inputs a project selection to the user terminal 200, in step S115, the user terminal 200 transmits the project ID and user ID of the selected project to the information processing device 100. Then, in step S116, the information processing device 100 associates the received project ID with the user ID in the user database 112. This registers the project that the user is supporting. In addition, the project display may also display detailed information of the project selected by the user, similar to the display of the supported person.

[0158] If a user supports multiple projects, the user terminal 200 displays a GUI for inputting the distribution ratio of the support amount to each project, as shown in Figure 15.

[0159] As shown in Figure 15A, this input GUI displays multiple icons representing multiple projects selected by the user. The size of these icons indicates the proportion of funding each project receives. The distribution proportion changes according to the user's input, and as shown in Figure 15B, the size of the icons changes accordingly. This allows the user to intuitively and visually recognize and decide on the distribution proportion. In addition to the icons, numerical values ​​indicating the distribution proportion may also be displayed. Once the distribution proportion is determined, it is displayed in a different manner than during input, as shown in Figure 15C. Note that the shape of the icons is not limited to circles; other shapes are also acceptable.

[0160] Input methods for changing the size of an icon include pinch-in / pinch-out gestures if the user terminal 200 has a touch panel, methods based on the duration of a finger press, and methods for adjusting the size by manipulating a seek bar with a finger. Alternatively, a cursor may be displayed, allowing the user to change the size of the icon by manipulating the cursor, or the user may be allowed to set the distribution ratio by entering a numerical value. Any method that allows the user to set the distribution ratio is acceptable.

[0161] Furthermore, if multiple projects are selected as recipients of support, the distribution ratio can be pre-set to automatically equalize the allocation. In this case, the user does not need to input the distribution ratio.

[0162] When the user enters the distribution ratio of the support amount for each project, in step S117 the user terminal 200 transmits the project ID, user ID, and distribution ratio to the information processing device 100. In step S118, the user terminal 200 displays the distribution ratio.

[0163] Then, in step S119, the information processing device 100 links the received project ID and distribution ratio to the user ID in the user database 112. This registers the distribution ratio of the support amount for multiple projects. If multiple projects are selected as support targets, the distribution ratio may be set in advance, such as making the distribution ratio equal. In that case, input of the distribution ratio is not required. Also, if the user supports only one project, the distribution ratio may be registered as 100%, or input and registration of the distribution ratio may be not required.

[0164] If a user is supporting multiple people, steps S105 to S119 are repeated the same number of times as the number of people being supported.

[0165] When a user supports multiple beneficiaries, the user terminal 200 displays a GUI for inputting the distribution ratio of the support amount to each beneficiary, as shown in Figure 16. The input method for this GUI is the same as that for inputting the distribution ratio of the support amount to the project. Note that if multiple beneficiaries are selected as support targets, the distribution ratio may be pre-set to automatically equalize it. In this case, the user does not need to input the distribution ratio. Furthermore, if the user supports only one beneficiary, the distribution ratio may be registered as 100%, or input and registration of the distribution ratio may be unnecessary.

[0166] When the user inputs the distribution ratio of the support amount to each beneficiary, in step S120 the user terminal 200 transmits the beneficiary ID, user ID, and distribution ratio to the information processing device 100. In step S121, the user terminal 200 displays the distribution ratio.

[0167] Then, in step S122, the information processing device 100 links the received support recipient ID and distribution ratio to the user ID in the user database 112. This registers the distribution ratio of the support amount.

[0168] Next, in step S123, the information processing device 100 notifies the supported terminal 300 that it has been registered as a supported item. This notification includes the user ID and the project ID of the project the user is supporting. As shown in Figure 17A, the supported terminal 300 displays this notification, allowing the supported person to know that they have been registered as a supported item.

[0169] Furthermore, in step S124, the information processing device 100 transmits the first content to the user terminal 200, and in step S125, as shown in Figure 17B, the user terminal 200 displays the first content. An example of the first content in Figure 17B is a message from the person being supported.

[0170] The user registration process is carried out as described above. Note that users are not required to register their beneficiaries and projects at the time of user registration; they can do so at any time after registration. Furthermore, users can add, delete, or modify their beneficiaries and projects at any time after registration. Users can also change their registered information, such as user attributes, at any time after registration.

[0171] [Score Calculation Process] Next, we will explain how the score calculation process based on transaction data is performed by the score processing unit 104.

[0172] The scoring processing unit 104 calculates a product affinity score that indicates the affinity between the supporter and the product based on the transaction data. As shown in Figure 18, the supporter database 114 is updated by calculating the product affinity score for the supporter from the transaction data and linking it to the supporter ID.

[0173] For example, suppose the transaction data indicates that user A purchased product A (the transaction ID is linked to user A's user ID and product A's product ID). Based on user A's user ID, the user database 112 is referenced, and if it can be determined from the supported person ID linked to the user ID that user A is supporting supported person S, then product A is considered to have affinity with supported person S, and a predetermined value (e.g., 1) is added to the product affinity score of product A for supported person S.

[0174] Similarly, if other users who have purchased product A also support recipient S, a predetermined value (e.g., 1) is added to the product affinity score of product A for recipient S. Therefore, the more users who support recipient S and purchase product A, the higher the product affinity score of product A for recipient S becomes. Note that the product affinity score may be calculated for each specific product or for each product category.

[0175] Furthermore, as shown in Figure 18, the score processing unit 104 calculates a user attribute score that indicates the attributes of the user supporting the person being supported based on the transaction data, and updates the person being supported database 114 by linking it to the person being supported ID.

[0176] For example, suppose the transaction data indicates that user A purchased product A (the transaction ID is linked to user A's user ID and product A's product ID). Based on user A's user ID, the user database 112 is referenced, and if it can be determined from the user attributes and supported person ID linked to the user ID that user A is a woman in her 30s and is supporting supported person S, then it is assumed that supported person S has an affinity with women in their 30s, and a predetermined value (for example, 1) is added to the user attribute score for "30s" and "female" in supported person S.

[0177] Similarly, if other users who purchased product A are women in their 30s, a predetermined value (for example, 1) is added to the user attribute scores for "30s" and "female" in the supported person S. Therefore, the more female users in their 30s who purchase product A, the higher the user attribute scores for "30s" and "female" in product A will become. User attribute scores can be calculated based on any one of various items such as age, gender, occupation, family structure, residence, place of residence, annual income, consumption trends, and purchase history, or they can be calculated based on multiple items such as "30s" and "female".

[0178] In this way, the scoring processing unit 104 calculates a product affinity score and a user attribute score linked to the support recipient ID from the transaction data. By providing the product affinity score and user attribute score to the support recipient, the support recipient can understand which products and users they have a high affinity with. Furthermore, by providing the product affinity score and user attribute score to the manufacturer, the manufacturer can use them as a reference when determining the normal support amount and the special support amount, and when determining which support recipients will receive the special support amount.

[0179] Furthermore, as shown in Figure 18, the scoring processing unit 104 calculates the supporter affinity score for a product based on the transaction data and updates the product database 113 by linking it to the product ID.

[0180] For example, suppose the transaction data indicates that user A purchased product A (the transaction ID is linked to user A's user ID and product A's product ID). Based on user A's user ID, the user database 112 is referenced, and if it can be determined from the supported person ID linked to the user ID that user A is supporting a supported person S, then product A is considered to have affinity with supported person S, and a predetermined value (e.g., 1) is added to the supported person affinity score for product A.

[0181] Similarly, if other users who have purchased product A have registered support recipient S as a target for support, a predetermined value (e.g., 1) is added to the support recipient affinity score for product A. Therefore, the more users who support support recipient S and purchase product A, the higher the support recipient affinity score for support recipient S in product A will become.

[0182] By providing manufacturers with a supporter affinity score linked to their product ID, manufacturers can understand which supporters their products are most compatible with. This allows manufacturers to use this information as a reference when planning collaborative merchandise with supporters, for example.

[0183] The information processing device 100 can determine which products and users a supported person has a high affinity with based on the product affinity score and user attribute score associated with the supported person ID. Furthermore, the information processing device can determine which supported person a manufacturer has a high affinity with based on the supported person affinity score associated with the product ID. Therefore, the information processing device 100 may also have a function to analyze what products and users supported people and manufacturers should target based on the product affinity score, user attribute score, and supported person affinity score, and to provide recommendations to supported people and manufacturers based on the analysis results.

[0184] Furthermore, as shown in Figure 19, the score processing unit 104 refers to the transaction database 111 and calculates affinity score vectors representing the distance between users, products, and supported individuals, as shown in Figure 20, and updates the score vector database 116. When the information processing unit 100 receives a request from a user terminal 200 along with a user ID, it sends some score obtained from the affinity score vector corresponding to that user ID to the user terminal 200. Similarly, when the information processing unit 100 receives a request from a supported individual terminal 300 along with a supported individual ID, it sends some score obtained from the affinity score vector corresponding to that supported individual ID to the supported individual terminal 300. Furthermore, when the information processing unit 100 receives a request from a manufacturer terminal 400 along with a manufacturer ID, it sends some score obtained from the affinity score vector corresponding to that manufacturer ID to the manufacturer terminal 400. In other words, scores are not recorded in the user database 112, product database 113, and supported individual database 114, but rather the affinity score vectors are recorded in the score vector database 116, and the scores are sent only when a request is received from each terminal. Note that the affinity score vector shown in Figure 20 is merely an example, and affinity score vectors do not always contain this kind of information.

[0185] [Processing when purchasing products] Next, with reference to Figure 21, the process when a user purchases products on the marketplace will be explained. This process is carried out by the transmission / reception unit 101, the data management unit 102, the transaction data generation unit 103, and the support amount management unit 105.

[0186] First, the user provides input to the user terminal 200 to access the marketplace. This input may include clicking a link or selecting a bookmark that the user has previously registered. In response to the user's input, in step S201, the user terminal 200 requests information for displaying the product list from the information processing device 100, along with the transmission of the user ID.

[0187] In step S202, the information processing device 100, upon request, reads the product IDs and product list display information for all products currently being sold on the marketplace from the product database 113 and sends them to the user terminal 200.

[0188] Then, in step S203, the user terminal 200 displays a list of products. The information for displaying the product list includes, for example, the image, name, manufacturer, price, and support amount for each product, as shown in Figure 22A. However, this display is merely an example, and other information may be displayed in the product list.

[0189] When a user enters information for a product search, in step S204, the user terminal 200 requests information for displaying a product list corresponding to the search content from the information processing device 100. In step S205, the information processing device 100 reads the product ID and information for displaying the product list corresponding to the search content from the product database 113 and sends it to the user terminal 200. Then, in step S206, the user terminal 200 displays the product list as the search results. Product searches can be performed by product name, genre, price, release date, etc. Furthermore, the product display may be sorted alphabetically, by price, by popularity, by rating, etc.

[0190] When a user inputs a product selection to the user terminal 200, in step S207 the user terminal 200 requests product details for the selected product from the information processing device 100. In step S208 the information processing device 100 reads the product ID and product details of the selected product from the product database 113 and sends them to the user terminal 200. Then, in step S209 the user terminal 200 displays the product details.

[0191] When displaying product details, as shown in Figure 22B, for example, in addition to the information displayed in a list format such as the image, name, manufacturer, price, and support amount for each product, more detailed information than the basic product information, such as product description and ratings, is also displayed. However, this display is merely an example, and other information, such as usage instructions, reviews, and related products, may also be displayed in the product details display.

[0192] Furthermore, in order to display the product list, the information processing device 100 transmits the support amount to the user terminal 200 as information for displaying the product list. However, if the support amount is a special support amount, the information processing device 100 transmits the special support amount to the user terminal 200 as information for displaying the product list. The same applies to the product details. As a result, the special support amount is displayed as the support amount for the product on the user terminal 200.

[0193] Furthermore, for products that qualify for special support, it is advisable to display text or marks indicating that they are special support products in the product list display and product details display, as shown in Figures 22C and 22D. This will allow users to understand that a product is a special support product.

[0194] The manufacturer's social responsibility score may be displayed in the product list and product details pages. This allows users to check the manufacturer's stance and track record regarding social responsibility before deciding which products to purchase.

[0195] The information processing device 100 refers to the recipient ID associated with the user ID, and if ineligible product information is associated with that recipient ID, it is preferable to display that the support amount for the ineligible product is 0 yen in the product list display and product details display. Alternatively, the support amount for ineligible products may be hidden. This allows the user to understand which products will not provide support to recipients even if purchased.

[0196] When the user inputs information to the user terminal 200 to determine the product to purchase, in step S210 the user terminal 200 displays a product purchase page. On this product purchase page, the user enters the necessary information for purchasing the product, such as payment information and shipping information. The product purchase page may also display the discount amount.

[0197] When a user enters information to confirm their purchase on the product purchase page, in step S211, the user terminal 200 transmits the purchase information to the information processing device 100. The purchase information includes at least the user ID and the product ID of the product for which the purchase has been confirmed. The purchase information may also include other information. Upon receiving the purchase information, the information processing device 100 generates transaction data in step S212 once the payment is completed.

[0198] The information processing device 100 generates transaction data by referring to the user database 112 based on the user ID included in the purchase information and obtaining the supported person ID and project ID of the person being supported by the user.

[0199] Note that the settlement process may be performed by a settlement server separate from the information processing device 100, or the information processing device 100 may have a settlement processing function. When the settlement server performs the settlement process, the information processing device 100 transmits the information necessary for settlement to the settlement server. After that, the information processing device generates transaction data and performs subsequent processing after receiving notification of settlement completion from the settlement server.

[0200] Next, in step S213, the information processing device 100 updates the inventory information and sales information of the products. Then, in step S214, the information processing device 100 transmits the updated inventory information and sales information to the manufacturer terminal 400. Note that the management of product inventory information and sales information may be performed by a device other than the information processing device 100.

[0201] In step S215, the information processing device 100 updates the cumulative amount of support received by the supporter and the cumulative amount of support received by the project. If the transaction data has the first configuration described above, the information processing device 100 identifies the amount of support set for the purchased product by referring to the product database 113 based on the product ID included in the transaction data. The information processing device 100 then refers to the supporter database 114 based on the supporter ID included in the transaction data and adds the amount of support set for the purchased product to the cumulative amount of support received associated with the supporter ID. This updates the cumulative amount of support received by the supporter.

[0202] Furthermore, if the user is supporting multiple individuals, the information processing device 100 adds the support amount to the cumulative support amount according to the distribution ratio included in the transaction data.

[0203] Furthermore, the information processing device 100 refers to the project database 115 based on the project ID included in the transaction data and adds the set support amount for the purchased goods to the cumulative support amount associated with the project ID. This updates the cumulative support amount for the project.

[0204] Furthermore, if a user supports multiple projects, the information processing device 100 adds the support amount to the cumulative support amount according to the distribution ratio included in the transaction data.

[0205] Furthermore, if the transaction data has the second configuration described above, the information processing device 100 identifies the ID of the person being supported by the user by referring to the user database 112 based on the user ID. Then, it refers to the person being supported database 114 based on that person being supported ID and adds the support amount set for the purchased product to the cumulative amount of support received associated with the person being supported ID. This updates the cumulative amount of support received by the person being supported.

[0206] Furthermore, if the transaction data is in the second configuration, the information processing device 100 identifies the ID of the project supported by the user by referring to the user database 112 based on the user ID. Then, based on that project ID, it refers to the support recipient database 114 and adds the support amount set for the purchased goods to the cumulative support amount associated with the project ID. This updates the cumulative support amount for the project.

[0207] If the transaction data has the second configuration, the user can also register the beneficiaries and projects they will support after purchasing a product. In this case, the support amount is not processed as support for the beneficiaries and projects, so the transaction data is recorded in the transaction database 111 with an unprocessed status. The unprocessed support amount is also added to the unprocessed support amount associated with the user ID and recorded.

[0208] If a user registers the beneficiaries and projects they wish to support after purchasing a product, as shown in Figure 23A, the user terminal 200 will display a list of outstanding support amounts and beneficiaries or projects, allowing the user to select the beneficiaries or projects they wish to support while checking the outstanding support amounts.

[0209] Furthermore, if there are outstanding project support amounts, as shown in Figure 23B, the user terminal 200 displays the outstanding project support amounts and a list of projects, allowing the user to select a project to support while confirming the outstanding project support amounts.

[0210] In step S216, the information processing device 100 updates the user's cumulative support amount. If the transaction data is in the first configuration, the information processing device 100 can identify the support amount set for that product by referring to the product database 113 based on the product ID included in the transaction data. Then, the information processing device 100 refers to the user database 112 based on the user ID included in the transaction data and adds the support amount to the cumulative support amount associated with the user ID. This updates the cumulative support amount of the person being supported.

[0211] Furthermore, when adding the cumulative amount of support received and the cumulative amount of support provided as described above, if the support amount for the purchased goods is a special support amount, the information processing device 100 adds the special support amount instead of the regular support amount. This ensures that the special support amount is reflected in the cumulative amount of support received and the cumulative amount of support provided.

[0212] Here, we will explain the amount of support when a user supports multiple beneficiaries, and one of them is a special beneficiary. For example, suppose a user who is supporting beneficiaries A and B purchases product C, and product C has a normal support amount of 100 yen, with a special support amount of 160 yen set for beneficiary A. Furthermore, suppose the user has set the distribution ratio between beneficiaries A and B to 50:50. In this case, when the user purchases product C, the process is such that beneficiary A receives 80 yen and beneficiary B receives 50 yen. In other words, the amount of support that each beneficiary would have originally received is divided 50:50.

[0213] After updating the cumulative amount of support received, the information processing device 100 sends the support result to the support recipient terminal 300 in step S217. As shown in Figures 24A and 24B, the support recipient terminal 300 displays the support result, allowing the support recipient to confirm that they have been supported and the amount of support received. The support result displays the name of the supporting user, the latest support amount, the support amount for each project, the amount of support received over a certain period (this month, this week, etc.), the cumulative amount of support received, the cumulative amount of support received for each project, and the achievement rate of the target support amount for the project. The achievement rate of the target support amount can be calculated from the target support amount and the cumulative support amount linked to the project ID. However, this display is merely an example, and other information may be displayed as part of the support result.

[0214] Furthermore, after updating the cumulative support amount, the information processing device 100 transmits the support results to the user terminal 200 in step S218. Then, in step S219, as shown in Figures 25A and 25B, the user terminal 200 displays the support results, allowing the user to know their own support amount and other information. The support results include the name of the support recipient, the latest support amount, the support amount for each project, the support amount for a certain period (this month, this week, etc.), the cumulative support amount, the cumulative support amount for each support recipient, the cumulative support amount for each project, and the achievement rate of the target support amount for the project. However, this display is merely an example, and other information may be displayed as support results. This display of support results on the user terminal 200 makes the legitimacy of support based on product purchases visible, and allows the user to confirm that their support has reached the support recipient.

[0215] Furthermore, the information processing device 100 may calculate statistics on the total amount of support provided by all users of the support service and a ranking based on those statistics, and transmit the ranking information to the user terminal 200. As shown in Figure 25C, the user terminal 200 displays the ranking information, allowing users to check their own support status and the support status of other users. Ranking information may include, for example, a ranking of the total amount of support provided over a predetermined period (the entire period from the start of the service, months, or weeks), a ranking of the amount of support received for each project, or a ranking of the amount of support received for each support recipient.

[0216] If the recipient of the support has set an interim support target amount for the project, and that interim support target amount is achieved, in step S220, the information processing device 100 sends a notification to the user terminal 200 that the interim support target amount has been achieved. Then, in step S221, the user terminal 200 displays the notification that the interim support target amount has been achieved. Whether or not the target support amount has been achieved can be confirmed by comparing the cumulative support amount with the target support amount.

[0217] Furthermore, in step S222, the information processing device 100 transmits the second content to the user terminal 200. Then, in step S223, the user terminal 200 displays the second content. The second content is content in which the supporter expresses gratitude to the user for achieving the project's target funding amount.

[0218] Furthermore, when the information processing device 100 receives a request for product list display information from the user terminal 200 in step S201, if there are products that meet certain conditions, it may perform product recommendation processing in step S231 as shown in Figure 26. If product recommendation processing is performed, in step S232 the information processing device 100 sends the recommended product information to the user terminal 200. Then, in step S233 the user terminal 200 displays the recommended product information, so that specific products are displayed preferentially and the user can confirm the recommended products.

[0219] The first example of a product that meets specific conditions is a product in which the person being supported by the user is eligible for special support. The information processing device 100 can identify a product in which the person being supported by the user is eligible for special support by checking whether the person being supported ID linked to the user ID in the user database 112 matches the special support recipient ID in the special support information linked to the product ID in the product database 113. If there is a product in which the person being supported by the user is eligible for special support, the information processing device 100 transmits the product ID, basic product information, and special support rate as recommended product information to the user terminal 200.

[0220] A second example of a product that meets specific conditions is a product for which the user's user attributes qualify for special support. The information processing device 100 can identify products for which a user is eligible for special support by checking whether the user attributes associated with the user ID in the user database 112 match the special user attributes in the special support information associated with the product ID in the product database 113. If there is a product for which the user's user attributes qualify for special support, the information processing device 100 transmits the product ID, basic product information, and special support rate as recommended product information to the user terminal 200.

[0221] [Processing when the target funding amount is achieved] Next, with reference to Figure 27, the processing when the project's target funding amount is achieved will be explained. This processing is performed by the transmission / reception unit 101 and the funding amount management unit 105.

[0222] The information processing device 100 can determine whether the target funding amount has been achieved by comparing the project's target funding amount with the cumulative funding amount received. The information processing device 100 makes a determination as to whether the target funding amount has been achieved each time the cumulative funding amount is updated.

[0223] If the information processing device 100 determines that the target funding amount for the project has been achieved, in step S301 it sends a notification to the support recipient terminal 300, along with the project ID, indicating that the target funding amount has been achieved. By displaying this notification, the support recipient can learn that their project has achieved its target funding amount.

[0224] Furthermore, in step S302, the information processing device 100 sends a notification to the user terminal 200 that the target support amount has been achieved, along with the project ID and cumulative support amount information. In step S303, the user terminal 200 displays this notification, allowing the user to know that the target support amount for the project they supported has been achieved.

[0225] Furthermore, in step S304, the information processing device 100 transmits the second content to the user terminal 200. In step S305, the user terminal 200 displays the second content. The second content is content in which the supporter expresses gratitude to the user for achieving the project's target funding amount, and was uploaded to the information processing device 100 in advance by the supporter before the project's target funding amount was achieved.

[0226] Upon receiving notification that the target funding amount has been reached, the recipient terminal 300 uploads the third content to the information processing device 100 in step S306 in response to the recipient's input. Next, in step S307, the information processing device 100 transmits the third content to the user terminal 200. Then, in step S308, the user terminal 200 displays the third content.

[0227] The third type of content, like the second type, is content in which the supporter expresses their gratitude to the user for achieving the project's funding goal. While the second type of content is prepared in advance before the funding goal is reached, the third type of content, created and provided to the user after the funding goal is achieved, allows the user to see the supporter's genuine reactions and gratitude. Examples of the third type of content include a video of the supporter's reaction at the moment the funding goal is reached, or a link to a live streaming site for broadcasting the moment the funding goal is reached.

[0228] The process shown in Figure 27 is merely an example; the supporter may provide only the second content, or only the third content, or neither. However, providing either one or both of the second and third content is likely to give the user a greater sense of satisfaction and encourage continued support.

[0229] Furthermore, the information processing device 100 updates the progress information (status) of projects that have achieved their target funding amount to "achieved." In addition, it is desirable to display that a project has been achieved in the project list display during subsequent user registration processes. Projects that have been achieved may be hidden.

[0230] Recipients of support may be allowed to receive the funds even after the target amount has been reached.

[0231] Furthermore, the supporter may provide the user with a fourth type of content based on the user's total support amount. For example, the fourth type of content may be provided to a user when their total support amount reaches a predetermined amount. The fourth type of content is provided based on the total support amount from the user to the supporter and the total support amount from the user to the project. To provide the fourth type of content, the supporter may upload the fourth type of content to the information processing device 100 in advance, or they may upload the fourth type of content to the information processing device 100 after the user's total support amount reaches a predetermined amount.

[0232] When the information processing device 100 provides fourth content based on the cumulative amount of support a user has provided to a supporter, it needs to update the cumulative amount of support associated with the supporter ID linked to the user ID. Furthermore, when the information processing device 100 provides fourth content based on the cumulative amount of support a user has provided to a project, it needs to update the cumulative amount of support associated with the supporter ID linked to the user ID, and then with the project ID linked to that supporter ID.

[0233] The fourth type of content is designed to allow individual users to express their gratitude for support. Like the first to third types of content, the fourth type of content can include images, messages, videos, and distribution links. However, unlike the first to third types of content, which are the same for all users, the fourth type of content is provided to individual users, so it may include the recipient user's name. This can give users a sense of exclusivity and increase their motivation to provide support.

[0234] Alternatively, a set period, such as weekly or monthly, may be established, and the fourth content may be provided only if the cumulative amount of support provided by individual users to the supporter reaches a predetermined amount within that period. This would allow for the setting of campaign periods, such as "This Month's Thank You Gift," which could increase user motivation to provide support. After the set period has elapsed, the cumulative support amount should be reset, and the fourth content and campaigns for the supporter should be reset.

[0235] The processing of this technology is performed as described above. According to this technology, transaction data is managed by linking it with the user ID, product ID, supporter ID, and project ID, enabling appropriate management of support for each product purchase. Furthermore, support can be traced for each transaction, allowing for the construction of a highly transparent support system. Even when a user supports multiple supporters or projects, the distribution ratio of the support amount is linked to the transaction data, enabling appropriate distribution and management of the support amount.

[0236] By selling everyday necessities, food, and miscellaneous goods that are not directly related to the beneficiaries on the marketplace, users can support the beneficiaries simply by purchasing items they need for daily life or items they want. In other words, users' casual, everyday consumption becomes support for the beneficiaries. As a result, users do not need to purchase large quantities of unnecessary items to support the beneficiaries, thus avoiding any financial or psychological burden.

[0237] By purchasing daily necessities such as household goods and groceries, users can support the beneficiaries they support, meaning they can help those in need simply by continuing their lives as before. Furthermore, because users can support the beneficiaries they support simply by purchasing products, this can stimulate their desire to buy products and create a new consumption principle.

[0238] Existing music and video streaming services often employ a parimutuel system, where the total amount charged by all users is divided by the total playback time, resulting in revenue distribution that does not reflect the intentions of each individual user. This technology generates transaction data containing the necessary support data for each product purchase and manages support based on that transaction data, enabling appropriate support that aligns with the user's intentions. Furthermore, because the support recipient and amount are determined and processed for each product purchase, appropriate and transparent support becomes possible.

[0239] By using support services, recipients of support can avoid having to expend time and effort on creating merchandise or other items that are not part of their core activities, allowing them to focus on their original work.

[0240] Manufacturers can set a support amount for each product, adding value to their products by making a portion of the price a subsidy. This can stimulate user interest in purchasing products and is expected to increase sales.

[0241] Furthermore, since manufacturers can designate any supporter or user as a target for special support, it becomes possible to sell products by conducting campaigns targeting fans of specific supporters. This can also stimulate users' desire to purchase products.

[0242] <Modifications> Although embodiments of this technology have been described in detail above, this technology is not limited to the embodiments described above, and various modifications are possible based on the technical concept of this technology.

[0243] In this embodiment, the distribution ratio is shown to indicate how the support amount is divided when a user supports multiple beneficiaries or projects, but the distribution method of the support amount may also be shown as specific amounts rather than ratios.

[0244] Projects are not a mandatory element in support services. Support services can be provided even without a project. If there is no project element, the recipient of support will not set up a project, the user will not register a project as the target of support, and the support amount will be directed towards the recipient themselves.

[0245] Furthermore, even if the support service includes a project element and the recipient has set up a project, users may be allowed to choose whether to support the recipient's project or the recipient themselves rather than the project.

[0246] While users purchase products on marketplaces where the operator does not hold inventory, this technology is applicable even to e-commerce (EC) sites where the operator holds inventory and sells products.

[0247] In this embodiment, support is provided when the recipient receives a monetary amount corresponding to the price of the product. However, support can also be provided by granting the recipient something that can be used as a substitute for money, such as points, miles, or coupons from the marketplace's own point service.

[0248] (1) An information processing device that manages support to a supported person in response to a user's purchase of a product, based on user identification information that identifies the user, supported person identification information that identifies the supported person, and product identification information that identifies the product. (2) The information processing device according to (1), wherein the support is provided by the supported person receiving a support amount based on the price of the product. (3) The information processing device according to (2), wherein the supported person who receives the support amount is the supported person selected as the target of support by the user who purchased the product from among a plurality of supported persons. (4) The information processing device according to (2) or (3), wherein the support amount is set in advance by the manufacturer of the product. (5) The information processing device according to any one of (1) to (4), which manages support to the supported person based on project identification information that identifies a project set in advance for the supported person. (6) The information processing device according to any one of (1) to (5), which generates transaction data including the user identification information and product identification information indicating the product purchased by the user. (7) The information processing device according to (6), which generates the transaction data after the user purchases the product. (8) The information processing device according to (6) or (7), wherein the transaction data includes the recipient identification information indicating the recipient supported by the user. (9) The information processing device according to any one of (6) to (7), wherein the transaction data is a project pre-set for the recipient and includes project identification information indicating the project supported by the user. (10) The information processing device according to any one of (6) to (9), which manages support for the recipient in accordance with the user's purchase of the product based on the transaction data. (11) The information processing device according to any one of (2) to (10), which manages support for the recipient in accordance with a pre-set distribution ratio to the support amount when the user supports multiple recipients. (12) The information processing device according to any one of (2) to (11), which manages support for the projects in accordance with a pre-set distribution ratio to the support amount when the user supports multiple projects.(13) The information processing device according to (2), wherein the support amount is a normal support amount and a special support amount that is higher than the normal support amount. (14) The information processing device according to (6), which calculates a product affinity score indicating the affinity between the support recipient and the product based on the transaction data. (15) The information processing device according to (6), which calculates a user attribute score indicating the affinity between the attributes of the support recipient and the user based on the transaction data. (16) The information processing device according to (6), which calculates a support recipient affinity score indicating the affinity between the product and the support recipient based on the transaction data. (17) The information processing device according to any one of (1) to (16), which transmits the support result to a user terminal used by the user after the user has purchased the product. (18) The information processing device according to any one of (1) to (17), which transmits the non-support result to a support recipient terminal used by the support recipient after the user has purchased the product. (19) An information processing method for managing support to a person who is being supported in response to a user's purchase of a product, based on user identification information for identifying a user, person who is being supported for identifying a person who is being supported, and product identification information for identifying a product. (20) An information processing system comprising: a user terminal used by a user to purchase a product; and an information processing device for managing support to a person who is being supported in response to a user's purchase of a product, based on user identification information for identifying a user, person who is being supported for identifying a person who is being supported, and product identification information for identifying a product.

[0249] 10... Information processing system 100... Information processing device

Claims

1. An information processing device that manages support provided to a person who is being supported, in accordance with the user's purchase of the product, based on user identification information that identifies the user, person being supported identification information that identifies the person being supported, and product identification information that identifies the product.

2. The information processing apparatus according to claim 1, wherein the support is provided by the recipient receiving a support amount based on the price of the product.

3. The information processing device according to claim 2, wherein the person who receives the support amount is the person selected as the support recipient by the user who purchased the product from among a plurality of such persons.

4. The information processing device according to claim 2, wherein the support amount is predetermined by the manufacturer of the product.

5. The information processing device according to claim 1, which manages support to the person being supported based on project identification information that identifies a project set in advance for the person being supported.

6. The information processing apparatus according to claim 1, which generates transaction data including the user identification information and the product identification information indicating the product purchased by the user.

7. The information processing apparatus according to claim 6, which generates the transaction data after the user has purchased the product.

8. The information processing device according to claim 6, wherein the transaction data includes the supported person identification information indicating the supported person supported by the user.

9. The information processing apparatus according to claim 6, wherein the transaction data is a project pre-configured for the person being supported, and includes project identification information indicating a project supported by the user.

10. The information processing device according to claim 6, which manages support to the supported person in response to the user's purchase of the product based on the transaction data.

11. When the user provides support to multiple persons, the information processing device according to claim 2, which manages the support to the persons according to a predetermined distribution ratio of the support amount.

12. The information processing device according to claim 2, which manages support for a project according to a predetermined distribution ratio of the support amount when the user supports multiple projects.

13. The information processing device according to claim 2, wherein the support amount is a normal support amount and a special support amount that is higher than the normal support amount.

14. The information processing device according to claim 6, which calculates a product affinity score indicating the affinity between the supported person and the product based on the transaction data.

15. The information processing apparatus according to claim 6, which calculates a user attribute score indicating the affinity between the attributes of the supported person and the user based on the transaction data.

16. The information processing apparatus according to claim 6, which calculates a supporter affinity score indicating the affinity between the product and the supporter based on the transaction data.

17. The information processing device according to claim 1, wherein the support results are transmitted to a user terminal used by the user after the user has purchased the product.

18. The information processing device according to claim 1, wherein the user transmits the non-support result to a terminal used by the person being supported after the user has purchased the product.

19. An information processing method for managing support provided to a person who has been supported, based on user identification information that identifies a user, person who has been supported identification information that identifies a person who has been supported, and product identification information that identifies a product.

20. An information processing system comprising: a user terminal used by a user to purchase a product; and an information processing device that manages support provided to the supported person in accordance with the user's purchase of the product, based on user identification information that identifies the user, supported person identification information that identifies the supported person, and product identification information that identifies the product.

Images