Information processing device and information processing method

Abstract

This invention provides technology that enables users to continuously support specific organizations through their daily consumption activities. [Solution] An information processing device according to one embodiment includes an acquisition unit that acquires IP identification information that identifies the IP related to the payment-related means used by the user in payment at the user terminal, a recording unit that records amount-related information related to the amount of the payment in association with the IP identification information, and an output unit that outputs an aggregate value of the amount-related information recorded in the recording unit.

Description

TECHNICAL FIELD

[0001] The present invention relates to an information processing apparatus and an information processing method.

BACKGROUND ART

[0002] A technique for making a donation to a specific target using a payment function is known. For example, Patent Document 1 discloses an invention that provides a function of settling a donation amount using a payment application, so that a user can make a monetary donation to a specific organization.

PRIOR ART DOCUMENTS

PATENT DOCUMENTS

[0003]

PATENT DOCUMENT 1

SUMMARY OF THE INVENTION

PROBLEMS TO BE SOLVED BY THE INVENTION

[0004] The invention described in Patent Document 1 is limited to a simple donation function attached to a payment function, and does not provide a continuous support mechanism linked to the user's consumption behavior. In addition, there is still room for improvement in ensuring transparency regarding the use of donated funds and motivating users to provide support.

[0005] In response to this, the present invention provides a technique for allowing users to continuously support specific organizations through their daily consumption activities. Furthermore, through visualization of the support amount, provision of benefits, and ensuring transparency in the use of funds, the present invention enhances user satisfaction and supports more effective support activities.

MEANS FOR SOLVING THE PROBLEMS

[0006] An information processing device according to one aspect of the present disclosure includes: an acquisition unit that acquires IP identification information that identifies an IP related to a payment-related means used by a user in a payment at a user terminal; a recording unit that records amount-related information related to the amount of the payment in association with the IP identification information; and an output unit that outputs an aggregate value of the amount-related information recorded in the recording unit.

[0007] An information processing method relating to another aspect of the present disclosure includes the steps of: a computer obtaining IP identification information that identifies an IP related to a payment-related means used by a user in a payment at a user terminal; recording amount-related information related to the amount of the payment in association with the IP identification information; and outputting an aggregate value of the amount-related information. [Effects of the Invention]

[0008] According to the present invention, users can support their favorite organizations through their daily consumption activities. Furthermore, by making the amount of support or the use of funds visible, it is expected that this will increase user trust and encourage continued support. [Brief explanation of the drawing]

[0009] [Figure 1] A diagram illustrating the system configuration of an information processing system 1 according to one embodiment. [Figure 2] A diagram illustrating the functional configuration of information processing system 1. [Figure 3] A diagram illustrating the hardware configuration of the information processing device 10. [Figure 4] A flowchart illustrating the operation overview of information processing system 1 according to one embodiment. [Figure 5] A sequence chart showing the operation of the information processing system 1 according to one embodiment, related to ticket surface setting. [Figure 6] A diagram illustrating the display screen of user terminal 20. [Figure 7] A diagram illustrating the ticket management database 1000. [Figure 8]A sequence chart showing the payment-related operations of the information processing system 1 in the embodiment. [Figure 9] A diagram illustrating the 2000 payment point management database. [Figure 10] A sequence chart showing the operation of the information processing system 1 in this embodiment regarding the aggregation of support amounts. [Figure 11] A diagram illustrating the user-specific aggregation database 3000. [Figure 12] A diagram illustrating the IP-based aggregation database 4000. [Figure 13] A sequence chart showing the IP-related operations of the information processing system 1 in this embodiment. [Modes for carrying out the invention]

[0010] 1. Structure Figure 1 is a diagram illustrating the system configuration of an information processing system 1 according to one embodiment. In this example, the information processing system 1 (hereinafter simply referred to as "the system") is a system for supporting customers' "fan activities" within a service or economic sphere provided by the target business operator, such as payment, points, and shopping. In recent years, customer needs have diversified, and the forms of support for specific IP (Intellectual Property) have also diversified. In this example, IP refers to content that customers want to support, such as sports teams like J.League (registered trademark) clubs, anime, or idols, and the business entity that owns the IP will be referred to as the "IP holder" below. Business operators involved in the economic sphere are required to create services that respond to the diverse needs of customers and build long-term economic relationships.

[0011] While conventional technologies exist, for example, a system that supports IPs with a fixed return rate at the time of payment, there was no system that allowed users to actively select which IPs to support and visualize the amount of support they provided. Furthermore, there was a lack of features to encourage further support, such as providing rewards based on the amount of support or clearly indicating the user's contribution.

[0012] Accordingly, the information processing system 1 of the present embodiment provides returns to the IP selected by the user in accordance with the payment amount generated through the use of the economic sphere or the points earned, and provides the user with benefits corresponding to the support amount or visualizes the user's contribution, thereby providing a more fulfilling "oshi activity" experience. In addition, the information processing system 1 enhances cooperation with IP holders to realize invitations to limited events or provision of original goods, so as to maximize customer satisfaction. This makes it possible to respond to diversifying customer needs and contribute to the vitalization of the economic sphere provided by the business operator.

[0013] The information processing system 1 includes an information processing apparatus 10, a user terminal 20, a ticket surface management server 31, a payment management server 32, a point management server 33, an IP operator server 40, and a site management server 50. In this example, the respective components of the system are connected to each other via a network 9. In this example, the network 9 is a computer network such as the Internet or a mobile network. The information processing system 1 has a function of collecting, recording, and aggregating information related to payments made by a user to support a specific IP.

[0014] The information processing apparatus 10 is an information processing apparatus or a server apparatus in the information processing system 1. The information processing apparatus 10 is any computer device such as a server computer, a cloud computer, or an edge computer. In this example, the information processing apparatus 10 functions as a base apparatus that analyzes various data used in the present system. For example, the information processing apparatus 10 manages the setting status related to oshi activities, support amount, rank, and payment amount for each IP for each user.

[0015] The user terminal 20 is a terminal device possessed by a user, and corresponds to a smartphone or the like. The user terminal 20 includes, for example, a smartphone, a tablet, a personal computer, or a wearable terminal. In this example, the user terminal 20 implements payment-related means used by the user for payment. The payment-related means refers to services related to payment, and indicates, for example, a point application (hereinafter referred to as "point App") or a payment application (hereinafter referred to as "payment App"). For example, the user can operate the point App on the user terminal 20, and select a voucher surface to be displayed at the time of payment as the selection of an IP. The voucher surface refers to a screen when using a payment service in a payment App, a point App, or the like. Many payment Apps or point Apps display an image code (for example, a barcode or QR Code (registered trademark)) when using a payment service, and a screen imitating a card is used at this time. The "voucher surface" refers to the design of the card (virtual card) in this screen. By changing this voucher surface as the screen design on the application, the user can participate in oshi activities, and for example, a part of the usage amount related to payment is returned to the supported IP.

[0016] Further, the user terminal 20 communicates with the voucher surface management server 31, the payment management server 32, and the point management server 33 via the network 9, and performs processes such as payment and point earning. In addition, the user can participate in oshi activities through the user terminal 20, select the voucher surface of the IP to be supported, and check the support amount or benefits.

[0017] The ticket management server 31 is a server that manages information about tickets available in the points app. The ticket management server 31 is any computer device, such as a server computer, cloud computer, or edge computer. The ticket management server 31 stores IP information or ticket data and provides ticket data in response to requests from the user terminal 20. Users can select a ticket for an IP they want to support from the provided ticket data and participate in supporting their favorite IP. The ticket design, for example, displays the club's character as a barcode design on the app screen, which has the effect of reminding users of the club when making a payment.

[0018] The payment management server 32 is a server that manages payment processing for payment apps and the like. The payment management server 32 is any computer device, such as a server computer, cloud computer, or edge computer. When a user makes a payment using a payment app, the payment management server 32 sends the payment data to the information processing device 10. The information processing device 10 aggregates the support amount based on the payment data and calculates the amount to be returned to the IP holder. Regarding the payment data, if information about the IP on the card selected at the time of payment cannot be obtained, the information processing device 10 can determine the IP on the card set at the end of the month as the recipient of the return for the month and return the support amount based on the points earned or payment amount for the month to the IP holder.

[0019] The point management server 33 is a server that manages points. The point management server 33 is any computer device, such as a server computer, cloud computer, or edge computer. When a user earns points, the point management server 33 sends the point acquisition data to the information processing device 10. The information processing device 10 aggregates the support amount based on the point acquisition data and calculates the amount to be returned to the IP holder.

[0020] The IP operator server 40 is a server that comprehensively manages various information, such as corporate information, of each IP holder. The IP operator server 40 is any computer device, such as a server computer, cloud computer, or edge computer. The IP operator server 40 connects to operator terminals (hereinafter referred to as "IP operator terminals") of each IP holder (not shown in the diagram) and provides financial support based on the support amount aggregated each month. The IP operator server 40 can also provide users with information about IP or information about benefits. The information processing device 10 works in conjunction with the IP operator server 40 to acquire the latest information about IP or benefit information and provide it to users. In addition, IP holders can check information such as the support amount or the use of funds through the IP operator server 40 connected to their IP operator terminal.

[0021] The site management server 50 is the server that manages the fan support site. The site management server 50 is any computer device, such as a server computer, cloud computer, or edge computer. On the fan support site, the amount of support for each IP is displayed, allowing users to see how much support their favorite IP is receiving. In addition, messages from IP holders or information on how the funds are being used are made public on the fan support site, allowing users to see how their support is being used.

[0022] Information Processing System 1, through the coordinated operation of the above components, enables users to support their fan activities and provide economic benefits to IP holders. Users can increase their support amount by changing the voucher design in the Points App and using payment or points. IP holders can use the collected support amount for fan events and content creation, thereby strengthening their relationship with fans.

[0023] Figure 2 is a diagram illustrating the functional configuration of the information processing system 1. In this embodiment, the information processing device 10 has functional blocks (or components) including an acquisition unit 11, a recording unit 12, an output unit 13, an aggregation unit 14, a calculation unit 15, an assignment unit 16, a provision unit 17, a storage unit 191, and a control unit 192. In this example, the storage unit 191 stores various data, programs, and software, including a database. In this example, the control unit 192 performs various controls.

[0024] The acquisition unit 11 acquires IP identification information that identifies the IP related to the payment-related means used by the user in the payment on the user terminal 20. Here, IP identification information refers to card face identification information, which is used to distinguish individual IPs and to identify which "favorite" the payment is linked to. When a user selects a card face of a specific IP (for example, a barcode with the design of the IP they want to support) on the points app and makes a payment using that card face, the acquisition unit 11 acquires the IP identification information corresponding to that card face. Depending on the amount of the user's payment, the payment service provider (for example, the management company of the payment management server 32) or the points service provider (for example, the management company of the points management server 33) provides financial support to the IP holder based on the acquired IP identification information. More specifically, a portion of the points earned by the user in the payment or the amount of the payment is returned as support to the IP holder corresponding to the IP identification information. The acquired IP identification information is sent to the recording unit 12 and recorded in conjunction with payment-related information.

[0025] The recording unit 12 records monetary information related to the amount of payment in association with the IP identification information. Monetary information refers to, for example, the amount of payment when a user uses a payment app, or the number of points earned when a user earns points in a points app. This information shows how much economic activity a user has engaged in to support a particular IP, and is important data for calculating the amount of return to the IP holder. The recording unit 12 records this monetary information as aggregated values ​​for each IP identification information and manages the amount of support for each IP.

[0026] The output unit 13 outputs the aggregated value of the monetary information recorded in the recording unit 12. The output destination is, for example, a website, a payment app, or a points app, and through these media, users can check the amount of support they have given to the IP they are supporting, as well as the total amount of support including other users. In addition, the output unit 13 can output to the user terminal 20 information indicating how the support funds related to the aggregated value of monetary information are being used by the business entity related to the IP identification information. This allows users to know how their support is being used and can increase their motivation to continue supporting.

[0027] The aggregation unit 14 has the function of aggregating monetary information for each user. This makes it possible to understand the amount of support each user has given and to implement measures to build long-term financial relationships with users. For example, the aggregation unit 14 sends the aggregated values ​​for each user to the calculation unit 15 to calculate the user rank.

[0028] The calculation unit 15 calculates the user rank according to the aggregated value for each user. The user rank changes according to the amount of support, and the higher the rank, the more benefits are awarded. This is expected to encourage users to actively engage in support activities in order to receive more benefits. The calculated user rank is sent to the awarding unit 16, where benefits are awarded according to the rank.

[0029] The rewards unit 16 grants rewards according to the aggregated values ​​for each user. Rewards may include, for example, the right to participate in exclusive events, original goods, or increased points. These rewards are important elements for increasing user satisfaction and promoting long-term use.

[0030] The service provider 17 provides the user terminal 20 with screen data that allows the user to select one ticket design from several available designs. Through this screen, the user can select a ticket design for the IP they want to support and participate in supporting their favorite IP. The service provider 17 works in conjunction with the ticket management server 31 to obtain the latest ticket information and provide it to the user. For example, the user can use the "card customization" function of the points app to select a ticket design for their favorite IP. When making a payment, the user presents the barcode displaying the selected ticket design, leading to active support. The display of the club's character on the ticket design also has the effect of reminding the user of the club when making a payment.

[0031] The memory unit 191 is used to store various types of data. For example, IP information, ticket data, user information, payment information, support amount, user rank, and reward information are stored there. The memory unit 191 reads and writes this data under the control of the control unit 192.

[0032] The control unit 192 controls the entire information processing device 10. For example, the control unit 192 controls data transfer between components, the execution order of processing, and error handling. The control unit 192 realizes these control functions by executing programs stored in the storage unit 191.

[0033] The information processing device 10, through the coordinated operation of the above components, supports users' fan activities and enables economic returns to IP holders.

[0034] Figure 3 illustrates the hardware configuration of the information processing device 10. Physically, the information processing device 10 is configured as a computer including a processor 101, memory 102, storage 103, communication device 104, and a bus connecting them. Each of these devices operates on power supplied from a battery (not shown). In the following description, the term "device" can be read as a circuit, device, unit, etc. The hardware configuration of the information processing device 10 may include one or more of the devices shown in Figure 3, or it may be configured without some of the devices. Alternatively, multiple devices with different enclosures may be connected via communication to constitute the information processing device 10.

[0035] Each function in the information processing device 10 is realized by loading predetermined software (programs) onto hardware such as the processor 101 and memory 102, which allows the processor 101 to perform calculations, control communication by the communication device 104, and control at least one of the reading and writing of data in the memory 102 and storage 103.

[0036] The processor 101 controls the entire computer, for example, by running the operating system. The processor 101 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. Alternatively, a baseband signal processing unit or a call processing unit may be implemented by the processor 101.

[0037] The processor 101 reads programs (program code), software modules, data, etc., from at least one of the storage 103 and the communication device 104 into the memory 102 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described later. The functional blocks of the information processing device 10 are stored in the memory 102 and may be realized by control programs that run on the processor 101. Various processes may be executed by one processor 101, or they may be executed simultaneously or sequentially by two or more processors 101. The processor 101 may be implemented by one or more chips. The program may also be transmitted to the information processing device 10 via a telecommunications line.

[0038] Memory 102 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. Memory 102 may also be called a register, cache, main memory, etc. Memory 102 can store executable programs (program code), software modules, etc., for carrying out the method according to this embodiment.

[0039] The storage 103 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The storage 103 may also be called an auxiliary storage device.

[0040] The communication device 104 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc.

[0041] Each device, such as the processor 101 and memory 102, is connected by a bus for communicating information. The bus may be configured using a single bus, or different buses may be used for each device.

[0042] The information processing device 10 may include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), and some or all of the functional blocks may be implemented by such hardware. For example, the processor 101 may be implemented using at least one of these hardware components.

[0043] In this example, the program stored in storage 103 includes a program (hereinafter referred to as the "server program") that causes the computer to function as a server in the information processing system 1. When the processor 101 is executing the server program, the processor 101, memory 102, storage 103, and communication device 104 are examples of functional blocks for operating the information processing device 10. The processor 101 is an example of a recording unit 12, an aggregation unit 14, a calculation unit 15, and a control unit 192. At least one of the memory 102 and storage 103 is an example of a storage unit 191. The communication device 104 is an example of an acquisition unit 11, an output unit 13, an assignment unit 16, and a provision unit 17.

[0044] While a detailed explanation will be omitted, the user terminal 20 is a computer having a processor, memory, storage, communication device, input device, and output device; specifically, it is, for example, a smartphone, tablet terminal, or personal computer. In this example, the program stored in the storage of the user terminal 20 includes a program that causes the computer to function as a client in the information processing system 1 (hereinafter referred to as the "client program"). The configuration of the information processing system 1 has now been described. Next, the operation of the information processing system 1 will be described.

[0045] 2.Operation Figure 4 is a flowchart illustrating the operation overview of the information processing system 1 according to one embodiment. As shown in Figure 4, the operation of the information processing system 1 can be broadly divided into four phases: the ticket setting phase, the payment-related phase, the support amount aggregation phase, and the IP-related phase. In this embodiment, the processing of the information processing system 1 corresponding to each phase is defined as a step. These phases represent a series of steps to realize a function in which a user makes a payment through a points app or the like to support a specific IP, and a portion of the payment amount is returned to the IP holder.

[0046] First, in the card design setting phase (step S1), the user uses their user terminal 20 to set a card design corresponding to the IP they wish to support through payment-related means such as the Points App. This card design is a barcode or similar displayed on the user terminal during payment and functions as IP identification information to identify which IP the user is supporting. Users can select and set their desired card design from multiple options using the "Card Customization" function of the Points App. The details of the card design setting phase will now be explained.

[0047] Figure 5 is a sequence chart showing the operation of ticket setting in the information processing system 1 according to one embodiment. In this embodiment, processing by various entities constituting the information processing system 1 will be described. Figure 5 shows the flow of data between the information processing device 10, the user terminal 20 (or point App 210), and the ticket management server 31.

[0048] First, in step S101, the information processing device 10 provides the user terminal 20 with screen data related to the ticket. This screen data is data that provides an interface for the user to select and set a desired ticket from among several ticket designs through a Point App 210 such as the Point Club app. Therefore, the screen data includes images and descriptions of the ticket corresponding to each IP, and the user can select the ticket of the IP they want to support while referring to this information.

[0049] Next, in step S102, the user operates the display screen provided by the Points App 210 on the user terminal 20 to set or change the ticket design. The display screen provided by the Points App 210 will now be described.

[0050] Figure 6 illustrates an example of the display screen of the user terminal 20. Figure 6 shows an example of a schematic diagram of a ticket face in the display screen provided by the Point App 210. In this example, the ticket face display screen shows both the ticket face T1 set by the user and the barcode B1 used for payment. The user can perform payments using the barcode via the ticket face display screen. Field F1 is a display area that allows the user terminal 20 to transition to a list of ticket face options when the user selects or changes a ticket face. The user accesses the ticket face selection list screen from here.

[0051] The card design selection screen displays a list of card designs available to the user (for example, card designs T1 to T4). From this screen, users can change the card design to one featuring IPs such as soccer clubs, anime, or idols (so-called "card customization"). Users can select their desired card design from the list displayed on the screen and complete the card design setting by pressing a confirmation button (not shown in the diagram). This operation records the IP identification information corresponding to the selected card design on the user's device, and this information will be used for subsequent payments.

[0052] Returning to Figure 5, in step S103, the user terminal 20 sends the data of the ticket face that has been configured or modified to the ticket face management server 31. This data includes a user identifier to identify the user, IP identification information corresponding to the selected ticket face, and so on.

[0053] Finally, in step S104, the ticket management server 31 records the received ticket data in the database. Here, we will describe the database used to manage the ticket information set by the user.

[0054] Figure 7 illustrates the ticket management database 1000. In this example, the ticket management database 1000 contains multiple records, each corresponding to a user who owns a user terminal 20. Each record includes a user ID, account information, a timestamp, a ticket ID, and IP information. Of these, the timestamp, ticket ID, and IP information are records related to the settings or changes made to the ticket by the user.

[0055] The User ID is unique identification information for each user who owns the user terminal 20. Account information is information about the account of each user who uses the Points App 210, Payment App 220, or various service apps, and includes basic information such as the user's identification information, membership information, and user information. The timestamp is time information used to record the time when operations related to setting or changing the card face were performed in the Points App 210. Card face ID and IP information are unique identification information (an example of IP identification information) and information about the content of that IP that corresponds to each card face.

[0056] The ticket management database 1000 can record the setting period for a specific ticket used by a user based on this information. This information is used during aggregation. This database is also used to manage the ticket setting status for each user and forms the basis for data analysis in the support amount aggregation phase (step S3). Furthermore, the data recorded in the database is referenced as needed and used for processing payments to IP or displaying the support status to users.

[0057] Through these steps, users can easily set the IP they want to support on the card, and in subsequent payment-related phases (step S2), a portion of the points earned by the user or the amount spent on payments can be returned to the IP holder. In other words, payment service providers or point service providers can provide financial support to IP holders in proportion to the amount of payments made by the user.

[0058] Returning to Figure 4, in the next payment-related phase (step S2), the user makes a payment using the configured card face through a payment method such as the payment app 220. At this time, payment-related information such as the payment amount or the amount of points awarded is recorded in association with the IP identification information on the configured card face. This phase is intended to explain the process by which users support IP through their daily consumption, and the user's payment actions directly lead to support for IP.

[0059] Figure 8 shows a sequence chart illustrating the payment-related operations of the information processing system 1 in this embodiment. Figure 8 shows the processing flow from step S201, when the user presents their point card at the register; step S202, when the payment method is used; step S203, when the store server 91 acquires payment usage data from the PoS terminal 92; step S204, when the usage data is stored in a database or the like; to step S205, when the data is transmitted monthly or daily from the store server 91 to the payment management server 32 or point management server 33. In this example, the store server 91 and the PoS terminal 92 are devices or terminals related to a PoS (Point of Sale) system installed at the register of each store. The store server 91 and the PoS terminal 92 record various data related to payments made at the store's register and, in cooperation with the information processing system 1, output this data to the payment management server 32 or point management server 33. Here, for example, the process for recording information related to payments made after a user has set a card design (e.g., "Deneb Wakaba") in the point app 210 will be explained.

[0060] In step S201, the user presents their point card at the register, and the point card is read via a PoS terminal 92 operated by, for example, a store employee. In this example, the point card can be a physical point card or a virtual point card, including, for example, a card displayed via a point app 210. By reading these point cards, the PoS terminal 92 can obtain information such as IP identification information.

[0061] Next, in step S202, the user executes the payment using a payment method. The payment method includes, for example, app payment via the payment app 220 installed on the user terminal 20, use of points, a registered credit card, or use of a physical credit card. As an example of application, if online shopping is the target of the payment, the user selects the product or service to be paid for on the payment app 220 and executes the process using one of the payment methods described above.

[0062] Here, when a user selects a card design for a specific IP and makes a payment, an amount equivalent to the number of points earned or a portion of the payment amount is returned to the entity that owns that IP (i.e., the IP holder). For example, if a user selects the "Deneb Wakaba" card design and uses app payment, 0.1% of the amount spent (e.g., 1000 yen) will be returned to the Deneb Wakaba IP holder. Also, if the user earns points with this payment, 10% of the points earned (e.g., 10 points) will be returned to the Deneb Wakaba IP holder. This return amount is borne by the operating company that develops the economic sphere of Information Processing System 1, and there is no burden on the user. Furthermore, users can freely change the IP they support by switching card designs on Point App 210. However, the amount of support given to IP holders is calculated based on settings as of the end of the month, for example. This will be explained in the support amount calculation phase (step S3).

[0063] Next, in step S203, once the payment is completed, the store server 91 obtains payment usage data from the PoS terminal 92. This usage data includes, for example, user identification information, payment date and time, payment method, payment amount (or number of points earned), and IP identification information of the selected voucher. Similarly, even in the case of online payments where the voucher is not displayed at the time of payment, or various direct debits, usage data is recorded on various servers.

[0064] In step S204, this usage data is stored in various databases within the store server 91. Examples of these databases include a database managed in common by the payment management server 32 and the point management server 33 (for example, the payment point management database 2000, described later). The payment point management database 2000 records payment amounts, points earned, and payment amounts, associated with user IDs and IP identification information.

[0065] In step S205, the accumulated data is periodically transmitted from the store server 91 to the payment management server 32 and the point management server 33, for example, monthly or daily. In this example, the store server 91 can output information regarding the payment amount paid at the time of payment to the payment management server 32 on a monthly basis. The store server 91 can also output information regarding points earned by the user at the time of payment to the point management server 33 on a daily basis. The timing at which the store server 91 transmits the usage data to the payment management server 32 and the point management server 33 can be determined in any way. Based on this usage data, the payment management server 32 or the point management server 33 can calculate the support amount for each IP. Now, the payment point management database 2000 will be described.

[0066] Figure 9 illustrates the payment point management database 2000. In this example, the payment point management database 2000 contains multiple records, each corresponding to a user. Each record includes user ID, timestamp, usage details, payment amount, points earned, and IP identification information. Of these, the timestamp, usage details, payment amount, points earned, and IP identification information are records in which payment-related usage information is recorded in association with terminal ID and IP identification information.

[0067] The User ID is unique identification information for each user. The timestamp is time information used to record the time of payment made by the user via the Payment App220, etc. The usage details, payment amount, and points earned are records of the specific details (or payment method, etc.) of the payment made via Payment App220, and the payment amount and points earned resulting from that payment. In the Payment Point Management Database 2000, the payment amount and points earned from payments are managed centrally. The IP identification information is unique identification information (which may be a card ID, etc.) corresponding to each card set at the time of payment.

[0068] The data recorded in these databases is used for aggregating support amounts for each IP, ranking users, and awarding rewards. These processes are performed in the support amount aggregation phase (step S3). Through these operations, the information processing system 1 of this embodiment can provide a mechanism that allows users to easily support IPs through their daily payments.

[0069] The aforementioned payments are expected to take place in various forms, including app payments at physical or online stores, and credit card payments. Figure 8 shows an example where both a point card and a payment method are used, but either one may be used. Therefore, payments that do not involve directly showing the card, such as communication charges, will also be counted as support for the IP, according to the card design set at that time.

[0070] Note that the correspondence between each record and IP identification information is not limited to the example in Figure 9. In the example in Figure 9, IP identification information is identified for each payment (or usage event) and recorded in the payment point management database 2000. However, IP identification information may be identified independently of payment or usage events, for example, periodically (monthly). In this case, when a new payment or usage event record is added, the IP identification information has not been identified, and the value of the IP identification information in this record is blank or null. At a predetermined timing (for example, at the beginning of the month), the point management server 33 accesses the ticket management database 1000 and identifies the IP identification information as of the end of the month. The point management server 33 writes the identified IP identification information to the records for the target period (for example, the previous month) where the IP identification information is blank. For example, if the IP identification information at the end of the previous month in the ticket management database 1000 was "Red Open Y", the point management server 33 writes "Red Open Y" as the IP identification information to all records for the previous month.

[0071] Returning to Figure 4, in the support amount aggregation phase (step S3), information recorded by various data servers is used to aggregate each user's support activity settings, support amount, rank, and payment amount per IP. This aggregation process is performed based on aggregation requests from the information processing device 10, triggered at the end of the month, and the support amount is calculated based on a predetermined return rate, such as 0.1% of the amount used for app payments and / or 10% of the amount of points earned. The aggregated support amount is linked to the payment server as the payment amount per IP and used for payment processing to each IP. Alternatively, the support amount per IP is displayed on a website or in various apps, allowing users to check their own support status.

[0072] Figure 10 is a sequence chart showing the operation of the information processing system 1 in this embodiment regarding the aggregation of support amounts. The information processing system 1 mainly consists of an information processing device 10, a user terminal 20, a ticket management server 31, a payment management server 32, and a point management server 33. In this support amount aggregation phase, various processes are executed to support the user's support activities. The detailed operation of each step is described below.

[0073] First, the information processing device 10 requests data to be used for aggregation from the ticket management server 31, the payment management server 32, and the point management server 33 (step S301). This data collection request includes, for example, a request to collect information such as which IP the user supports (i.e., which is set on the ticket), how much app payment has been used, and how many points have been earned. In response to this request, the ticket management server 31, the payment management server 32, and the point management server 33 access databases such as the ticket management database 1000 and the payment point management database 2000, and collect the relevant data. The collected data is then transmitted to the information processing device 10.

[0074] Next, the ticket management server 31, the payment management server 32, and the point management server 33 refer to their internal databases based on the data received from the information processing device 10 (step S302). For example, the ticket management server 31 refers to the ticket management database 1000 to obtain user attribute information (e.g., age, gender, place of residence, etc.) and information on the IP address they support. The payment management server 32 or the point management server 33 refers to the payment point management database 2000 to obtain usage data related to the user's payments corresponding to the aggregation period, such as past payment history and point acquisition history.

[0075] Next, the ticket management server 31, the payment management server 32, and the point management server 33 provide various data to the information processing device 10 (step S303). As described above, the ticket management server 31 provides information about the ticket selected by the user (the barcode of the IP being supported). The payment management server 32 provides information about the user's payment history (payment amount, payment date and time, payment method, etc.). The point management server 33 provides information about the user's point acquisition history (number of points acquired, acquisition date and time, acquisition location, etc.). This data is used by the information processing device 10 to accurately calculate the amount of support the user has given.

[0076] Furthermore, the information processing device 10 calculates aggregate values ​​for each user based on the various data provided (step S304). These aggregate values ​​show, for example, how much the user used the payment app 220 and how many points they earned during a specific period (for example, one month). A predetermined formula is used to calculate the aggregate values. For example, the user's support amount is the sum of 0.1% of the amount spent using the payment app 220 and 10% of the amount of points earned.

[0077] For example, if a user selects the Deneb Wakaba card design and makes a payment of 10,000 yen using the payment app 220, the amount of support for Deneb Wakaba will be 10 yen. Alternatively, if a user earns 1,000 points, the amount of support for Deneb Wakaba will be 100 points. The information processing device 10 sums up these support amounts for each user to calculate the total support amount for each user. The calculated total support amount for each user is used for calculating user rank or awarding benefits. Now, let's explain the database for managing points for each user.

[0078] Figure 11 illustrates a user-specific aggregation database 3000. In this example, the user-specific aggregation database 3000 contains multiple records, each corresponding to a user. Each record includes the user ID, aggregation period, IP information, support amount aggregation information, and user rank. Here, the aggregation of support amounts for each IP for each user during the current month, as of the end of the month, and the user rank corresponding to each IP are recorded.

[0079] The User ID is unique identification information for each user. The aggregation period is a predetermined period for aggregating support amounts, for example, from the beginning to the end of the current month. The IP information is unique identification information (which may include a card ID, etc.) corresponding to each card set at the time of payment. Here, support amounts are aggregated for payments made during the period for which a card is set (hereinafter referred to as the "card setting period") for any card set by the user at least once during the current month. The aggregated support amount information includes payment support amount and point support amount (indicated as "Pt support amount" in the diagram). The former shows the aggregated support amount corresponding to payments, which is set at 0.1% of the amount spent, and the latter shows the aggregated support amount corresponding to point acquisition, which is set at 10% of the amount of points earned. The user rank is information indicating the rank assigned to each IP for that user according to the aggregated support amount, determined by the method described later.

[0080] Return to Figure 10. The information processing device 10 calculates the user rank based on the aggregated values ​​for each user (step S305). The user rank is determined according to the amount of support the user has given. The user rank is an indicator of the activity level of the user's support activities. For example, users who have given 1,000 yen or more in total support are assigned the Bronze rank, users who have given 5,000 yen or more are assigned the Silver rank, and users who have given 10,000 yen or more are assigned the Gold rank. The rank (for example, 3 or 5 levels) is determined based on predetermined criteria. Users whose support amount exceeds a certain amount are promoted to a higher rank.

[0081] Furthermore, various benefits (such as the right to participate in exclusive events, merchandise gifts, and increased points) are granted according to the user rank. Here, the content of the benefits changes according to the user rank. For example, Gold rank users are given the right to participate in exclusive events and original merchandise gifts. User rank plays an important role in increasing user motivation and encouraging further support activities.

[0082] The determined user rank is recorded in the user-specific aggregation database 3000 for each IP address. This step serves as an important incentive to increase user motivation and encourage continued support. By implementing a ranking system, users feel that their support activities are being valued, and become more actively involved in supporting their favorite idols.

[0083] Once the user rank is calculated, the information processing device 10 grants the user a reward (step S306). The reward is granted, for example, by notifying the user of the reward information through the points app 210 or by issuing a coupon for reward redemption through the payment app 220. Different rewards are offered depending on the user's rank. For example, users with the highest rank may receive an invitation to an exclusive event or a gift of special merchandise.

[0084] The information processing device 10 calculates aggregate values ​​for each IP in parallel with calculating aggregate values ​​for each user (step S307). This aggregate value shows the total amount of support collected from all users for a particular IP. The aggregate value for each IP is used to determine the amount to be paid to the IP holder (for example, a J.League (registered trademark) club, an anime company, etc.). The payment amount is determined according to the aggregate value and paid from the operating company to the IP holder.

[0085] Here, the support amount for each IP is calculated based on the amount each user has paid and the amount of points they have earned while selecting a specific IP card. For example, the support amount for Deneb Wakaba is the sum of 0.1% of the total amount paid by all users in Payment App 220 during the period when they selected Deneb Wakaba's card (including all card types if there are multiple types) and 10% of the amount of points they have earned. The information processing device 10 aggregates these support amounts for each IP to calculate the total support amount for each IP. The calculated total support amount for each IP is used for payments to IP holders, publication on the website, etc. Now, let's explain the database for managing points for each IP.

[0086] Figure 12 illustrates the IP-based aggregation database 4000. In this example, the IP-based aggregation database 4000 contains multiple records, each corresponding to a specific IP address. Each record includes the ticket ID (IP identification information), IP information, aggregation period, total support amount information, and the number of supporters. Here, the total support amount paid per IP address for the current month as of the end of the month is recorded.

[0087] The ticket ID and IP information are unique identifiers for each IP address. The aggregation period is a predetermined period for aggregating support amounts (for example, the same period as the aggregation period for user-specific aggregation database 3000). In IP-specific aggregation database 4000, support amounts are aggregated based on payments made during the ticket setting period in the current month.

[0088] The support amount summary information includes payment support amount, point support amount, and total support amount. The payment support amount is the sum of support amounts corresponding to payments, which is set at 0.1% of the amount spent by the corresponding user during the card setting period. The point support amount is the sum of support amounts corresponding to points earned, which is set at 10% of the amount of points earned by the corresponding user during the card setting period. The total support amount is the sum of the payment support amount and the point support amount. In other words, the total support amount at the end of the month in the IP-specific summary database 4000 is the amount of support paid to the IP holder (or individual IP).

[0089] The number of supporters is the number of users who participated in "Oshikatsu" (support activities) for each IP address, and includes, for example, the total number of users who contributed to payment support amount, point support amount, or total support amount during the aggregation period. In addition, when aggregating the number of supporters, duplicate users who contributed to payment support amount and point support amount may be counted as one person, and the number of supporters may be aggregated in any way.

[0090] Return to Figure 10. Finally, the information processing device 10 outputs various notifications to the user terminal 20 (step S308). The information processing device 10 notifies the user of their support amount for the current month, their user rank for the next month, and information regarding benefits. These notifications are made through the Points App 210 or the website. For example, the user terminal 20 receives notifications such as a quick update on the support amount, a rank-up notification, and information about benefits as push notifications or in-app messages. These notifications allow the user to realize how their support contributes to IP, which can encourage continued use.

[0091] The website will also publish the total amount of support received for each IP, as well as thank-you messages from the club. Furthermore, IP holders can be notified of payment amounts and support messages. IP holders can use this information for future promotional activities and product development. This will be explained in more detail in the IP-related phase described later.

[0092] Through the series of steps described above, the information processing system 1 supports users' fan activities and contributes to the revitalization of the operating company's economic sphere. Through these operations, the information processing system 1 of this embodiment provides a mechanism that allows users to easily support IPs through everyday payments, thereby achieving both increased revenue for IP holders and increased user satisfaction.

[0093] Returning to Figure 4, in the final IP-related phase (Step S4), payment processing is carried out to IP holders based on the aggregated support amount. The operating company pays the aggregated support amount to each IP holder without any burden on the users. IP holders can also use the received support amount to strengthen their IP by creating fan events or special content. In addition, the operating company and IP holders can ensure transparency and encourage further support by publishing information on how the support amount is used and messages of gratitude to fans through their website.

[0094] Figure 13 is a sequence chart showing the IP-related operations of the information processing system 1 in this embodiment. The coordinated operations of the information processing device 10, the IP provider server 40, and the site management server 50 in this system will be explained in sequence. This sequence shows the entire process from processing the amount of support a user has made to supporting a specific IP to posting various information on the website.

[0095] First, the information processing device 10 interacts with various servers and reads aggregated information from the database (step S401). This database stores data such as each user's activity settings, support amount, rank (for example, user-specific aggregate database 3000), and payment amount for each IP (for example, IP-specific aggregate database 4000). Based on this data, the information processing device 10 obtains aggregated support amounts and other information, and compiles information regarding payment processing for each IP.

[0096] Next, the information processing device 10 transmits the aggregated support amount information to the IP operator server 40 (step S402). This support amount information serves as an indicator of how much support each IP is receiving. The IP operator server 40 receives this information and proceeds with preparing payment processing for each IP, and can also grasp the level of user interest in the content or services provided by each IP. This information is an important factor for IP operators when considering future content strategies or fan services.

[0097] The IP operator server 40 confirms the support amount transmitted from the information processing device 10 and processes the payment (step S403). Based on this information, the IP operator server 40 can process payments to each IP through various financial institutions. Alternatively, once the support amount is confirmed, the IP operator server 40 may send support amount information or a notification regarding payment processing to an IP operator terminal (not shown). This support amount information is used by each IP operator as important data to evaluate the value of their content and optimize their marketing strategy.

[0098] Next, the information processing device 10 sends the posted information to the site management server 50 (step S404). This posted information includes the amount of support per IP (total amount from all users), a message to the user, information about special offers, and how the funds will be used. Based on this information, the site management server 50 can create content to be posted on the support site (for example, web pages, web content, etc.).

[0099] Finally, the site management server 50 posts the received information to the website (step S405). The website displays the amount of support per IP (for example, per club), a message from the club, and information about special offers. The disclosure of this information provides transparency to users and clarifies the results of their support activities. This allows users to see the results of their support in a visible way through the website, which is expected to increase their motivation to support further, foster a sense of community, and encourage further support.

[0100] 3. Variant The present invention is not limited to the embodiments described above, and various modifications are possible. Several modifications are described below. Two or more of the items described below may be combined and applied.

[0101] (1) Information processing system 1 The hardware and network configurations in the information processing system 1 are not limited to those exemplified in the embodiments. The information processing system 1 may have any hardware and network configuration as long as it can realize the required functions. For example, multiple physical devices may cooperate to function as the information processing system 1.

[0102] (2) Information processing device 10 Some of the functions of the information processing device 10 may be implemented on other servers. These servers may be, for example, physical servers or virtual servers (including so-called cloud servers). Furthermore, the correspondence between functional elements and hardware is not limited to those illustrated in the embodiments. For example, at least some of the functions described in the embodiments as being implemented on the information processing device 10 may be implemented on other devices or systems, and conversely, at least some of the functions described as being implemented on other devices or systems may be implemented on the information processing device 10. In this example, at least some of the functional elements implemented by the information processing device 10 may be implemented on other devices or systems, for example, AI, applications, or other software.

[0103] (3) User terminal 20 The user terminal 20 is not limited to those exemplified in the embodiments. The user terminal 20 may perform the above-described processing using any display screen, input device, or UI. The functions of the applications installed on the user terminal 20 (e.g., the points app 210 or the payment app 220) may be modified in any way. For example, the points app 210 and the payment app 220 may implement functions related to setting up vouchers, using them for payments, and earning points.

[0104] (4) Ticket management server 31, payment management server 32, point management server 33 The ticket management server 31, payment management server 32, and point management server 33 are not limited to those exemplified in the embodiment. These servers may have any functional elements as long as they can realize the required functions and operations. Some of the functions of the ticket management server 31, payment management server 32, and point management server 33 may be implemented on other servers. These servers may be, for example, physical servers or virtual servers (including so-called cloud servers).

[0105] (5) IP provider server 40, site management server 50 The IP operator server 40 and site management server 50 are not limited to those exemplified in the embodiment. These servers may have any functional elements as long as they can realize the required functions and operations. The IP operator server 40 and site management server 50 may be, for example, physical servers or virtual servers (including so-called clouds).

[0106] (6) Diversification of ticket designs The card designs offered by PointApp210 are not limited to J.League (registered trademark) clubs, anime, idols, etc., but can target a diverse range of entities, including local communities, local governments, and NPOs. This allows users to more freely choose who they want to support, leading to regional revitalization and social contribution. For example, providing card designs featuring local specialties or tourist attractions can support the development of the local economy. Furthermore, providing card designs that support environmental protection groups or animal welfare organizations can contribute to solving social issues.

[0107] (7) Implementation of campaigns linked to IP Information processing system 1 can collaborate with IP holders to conduct campaigns that offer benefits to users who set a specific ticket design during a specific period. This can encourage support for specific IPs and contribute to increasing the revenue of IP holders. For example, to commemorate the release of a new song, users who set a ticket design for a specific artist may be given limited edition merchandise or the right to participate in an online event. In addition, users who set a ticket design for a specific J.League (registered trademark) club at a match venue may be offered discounts at the stadium or exclusive items.

[0108] (8) Collaboration with AI agents Information processing system 1 can achieve the same effect as changing the card design by changing the AI ​​agent's character to an IP. This allows users who do not frequently use Point App 210, or users who are hesitant to change the card design, to easily participate in supporting their favorite idols. For example, the character walking on the AI ​​agent's home screen could be changed to the mascot character of a specific J.League (registered trademark) club. In this state, using the operating company's economic ecosystem could result in a system where support for that J.League (registered trademark) club is accumulated.

[0109] (9) Expansion of payment methods Information processing system 1 can also include the use of credit cards (or virtual cards, etc.) in addition to the use of payment app 220 (or points app 210) as a way to receive rewards for support. This will allow more users to participate in supporting their favorite idols and contribute to the expansion of usage by the operating company. For example, a system could be set up where, if a user provides an IP-linked credit card and makes a payment with that card, they will receive support for their favorite idols or points in addition to the regular payment amount or points.

[0110] (10) Strengthening cooperation with member stores Information processing system 1 may increase the rate at which support funds are returned based on the amount of payment made at participating merchants that provide goods or services related to IP. This will encourage users to use participating merchants more actively, contributing to increased sales for those merchants. For example, the rate at which support funds are returned may be increased for payments made on the J.League website where J.League (registered trademark) uniforms can be purchased, or on e-commerce sites where goods from IP organizations can be purchased.

[0111] (11) Support for NFC payments Information processing system 1 can support NFC payments (contactless payments) in addition to displaying barcodes from payment app 220. For example, during NFC payments, user terminal 20 can display the logo or character of the IP that the user supports, thereby encouraging recall during payment and increasing awareness of their fan activities.

[0112] (12) Diversification of methods for displaying donation amounts Information processing system 1 may display the support amount not only on the total amount displayed on the website, but also on the payment screen of payment app 220 or on points app 210. This allows users to easily check their support amount anytime, anywhere, and maintain their motivation to support. For example, the payment completion screen of payment app 220 may display the support amount earned for each payment and the total support amount for the individual. Also, the top screen of points app 210 may display the support amount and ranking of the IP being supported.

[0113] (13) Diversification of methods for returning support funds The information processing system 1 can aggregate support amounts not only based on the amount spent and points earned using the payment app 220, but also through direct donations of points. This allows users to choose a method of support that suits their lifestyle and values. For example, a donation page for each IP could be set up on the points app 210, allowing users to directly donate the points they hold. Alternatively, when purchasing a product from a specific IP, the points used could be automatically added to the support amount for that IP. It should be noted that the financial support provided by the payment service provider or points service provider to IP holders based on the user's payment amount, as described in the embodiment, may be limited to only a portion of the points earned or only a portion of the payment amount.

[0114] (14) Introduction of a ranking system Information processing system 1 can assign ranks to users based on the amount of support they provide and offer rewards according to their rank. This encourages users to actively participate in supporting their favorite idols in order to receive more rewards, thereby promoting continuous engagement. For example, when the amount of support reaches a certain level, rewards such as gifts of original merchandise, invitations to exclusive events, and messages from the IP (intellectual property) can be provided.

[0115] (15) Diversification of methods for providing benefits to IP holders Information processing system 1 allows users to choose from a variety of reward methods, including cash payments of support funds, provision of goods, invitations to events, and advertising placements. This enables IP holders to select the most effective reward method according to their own needs and strategies. For example, for anime production companies, limited edition goods can be produced and given to users based on the amount of support received. For local governments, tourism promotion advertisements can be placed based on the amount of support received.

[0116] (16) Global expansion This system can target not only Japanese IPs but also overseas IPs. This allows overseas fans to support Japanese IPs and helps facilitate the overseas expansion of Japanese content. For example, information processing system 1 provides tickets for popular overseas anime and presents limited edition Japanese merchandise to users who support those anime. Furthermore, this system can be used to raise funds when organizing overseas performances by popular Japanese idols. These variations expand the scope of application of the present invention and address diverse needs. By combining these variations, it becomes possible to provide an even wider range of services.

[0117] (17) Others The various programs executed by processor 101 may be provided by downloading them over a network such as the Internet, or they may be provided recorded on a computer-readable non-temporary recording medium such as a DVD-ROM. Each processor may be, for example, a CPU, an MPU (Micro Processing Unit), or a GPU (Graphics Processing Unit).

[0118] The block diagrams used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0119] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. As mentioned above, the method of implementation is not particularly limited.

[0120] For example, the information processing device 10 in one embodiment of the present disclosure may function as a computer that performs the processing of the present disclosure.

[0121] Each aspect or embodiment described in this disclosure may be applied to at least one of the following systems: LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

[0122] The processing procedures, sequences, flowcharts, etc., of each aspect or embodiment described in this disclosure may be reordered, provided they do not contradict each other. For example, the methods described in this disclosure present various step elements in an exemplary order and are not limited to the specific order presented.

[0123] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be sent to other devices.

[0124] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0125] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0126] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name. Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technologies (such as infrared or microwave), at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0127] The information, signals, etc., described herein may be represented using any of the following different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be referred to throughout the above description, may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof. Terms used herein and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meaning.

[0128] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information.

[0129] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0130] Any reference to elements using designations such as “First,” “Second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the First and Second elements do not imply that only two elements may be employed, or that the First element must precede the Second element in any way.

[0131] In the above-described configuration of each device, the term "part" may be replaced with "means," "circuit," "device," etc.

[0132] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0133] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0134] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different." [Explanation of Symbols]

[0135] 1...Information processing system, 10...Information processing device, 20...User terminal, 210...Points App, 220...Payment App, 31...Ticket surface management server, 32...Payment management server, 33...Point management server, 40...IP operator server, 50...Site management server, 9...Network, 91...Store server, 92...PoS terminal, 11...Acquisition unit, 12...Recording unit, 13...Output unit, 14...Aggregation unit, 15...Calculation unit, 16...Issuance unit, 17...Provision unit, 191...Storage unit, 192...Control unit, 101...Processor, 102...Memory, 103...Storage, 104...Communication device, 1000...Ticket surface management database, 2000...Payment point management database, 3000...User-specific aggregation database, 4000...IP-specific aggregation database, B...Barcode, F...Field, T...Ticket surface

Claims

1. An acquisition unit that acquires IP identification information that identifies the IP related to the payment-related means used by the user in payment on the user terminal, A recording unit that records amount-related information related to the amount of the settlement in association with the IP identification information, An output unit that outputs the aggregated value of the amount-related information recorded in the recording unit. An information processing device having

2. The recording unit records the amount-related information as aggregated values ​​for each IP identification information, The output unit outputs the aggregated value for each IP identification information. The information processing apparatus according to claim 1.

3. It has a aggregation unit that aggregates the aforementioned amount-related information for each user, The output unit outputs the aggregated values ​​for each user. The information processing apparatus according to claim 2.

4. Calculation unit that calculates user rank according to the aggregated values ​​for each user. The information processing apparatus according to claim 3, having the following features.

5. The rewarding unit grants benefits according to the aggregated values ​​for each user. The information processing apparatus according to claim 3, having the following features.

6. The payment-related means includes a ticket that is displayed on the user terminal at the time of payment. The information processing apparatus according to claim 1.

7. A provisioning unit provides the user terminal with screen data that allows the user to select one ticket from among multiple ticket designs. The information processing apparatus according to claim 6, having the following features.

8. The output unit outputs to the user terminal information indicating how the support funds related to the aggregated value of the amount-related information were used by the business entity related to the IP identification information. The information processing apparatus according to claim 1.

9. Computers A step of obtaining IP identification information that identifies the IP related to the payment method used by the user in payment on the user terminal, A step of recording amount-related information related to the amount of the settlement in association with the IP identification information, A step of outputting the aggregated value of the aforementioned amount-related information. An information processing method having

Images