Reward provision device, reward provision method, and program

Abstract

This allows for a wider variety of benefits available through subscription contracts, while reducing the burden on users. [Solution] The invention discloses a device comprising: a point awarding unit that associates predetermined points corresponding to the type of subscription contract with user identification information relating to a contract user who has entered into a subscription contract, for each predetermined period relating to the subscription contract; a point count information storage unit that stores point count information representing the number of points associated with the use of each of the multiple available benefits; a selection information acquisition unit that acquires selection information associated with the user identification information; and a selection screen output unit that displays selectable benefits from among the multiple benefits on a selection screen for generating selection information, wherein the selection screen output unit changes the remaining selectable benefits from among the multiple benefits on the selection screen according to one or more benefits selected on the selection screen, based on the predetermined points and the point count information.

Description

Technical Field

[0001] The present disclosure relates to a privilege providing apparatus, a privilege providing method, and a program. Background Art

[0002] Conventionally, techniques for automating billing for products and the like that are periodically purchased by customers for each predetermined period are known. Prior Art Documents Patent Documents

[0003] Patent Document 1 Japanese Unexamined Patent Application Publication No. 2016-126599 Summary of the Invention Problems to be Solved by the Invention

[0004] However, as the privileges available under a subscription contract diversify, the load on the user when selecting a privilege (for example, the operation load until finding a desired available privilege) and the accompanying information processing load increase.

[0005] Accordingly, in one aspect, an object is to reduce the load on the user and the like while enabling diversification of privileges available under a subscription contract. Means for Solving the Problems

[0006] In one aspect, a device is provided comprising: a point awarding unit that associates predetermined points corresponding to the type of subscription contract with user identification information relating to a contract user who has entered into a subscription contract, for each predetermined period relating to the subscription contract; a point count information storage unit that stores point count information representing the number of points associated with the use of each of a plurality of available benefits; a selection information acquisition unit that acquires selection information associated with the user identification information, which represents one or more selected benefits from among the plurality of benefits; and a selection screen output unit that displays selectable benefits from among the plurality of benefits on a selection screen for generating the selection information. The selection screen output unit changes the remaining selectable benefits from among the plurality of benefits on the selection screen according to the benefit selected on the selection screen, based on the predetermined points and the point count information in the point count information storage unit. [Effects of the Invention]

[0007] In one respect, the present invention makes it possible to diversify the benefits available through subscription contracts while reducing the burden on users. [Brief explanation of the drawing]

[0008] [Figure 1] This is a block diagram of the service system according to this embodiment. [Figure 2] This figure shows an example of a gameplay screen used to explain the overview of the competitive game part. [Figure 3] This is a functional block diagram relating to the functions related to subscription-based purchases, among the various functions implemented by the server device. [Figure 4] This is a diagram illustrating the data within the user information storage unit. [Figure 5] This is an explanatory diagram of information about the game. [Figure 6] This is a diagram illustrating the point parameters within the point parameter storage unit. [Figure 7] This is an explanatory diagram of the point count information stored in the point count information storage unit. [Figure 8] This is an explanatory diagram of selection information in a selection information storage unit. [Figure 9] This is an explanatory diagram of automatic update processing. [Figure 10] This is an explanatory diagram of selection information in the selection information storage unit after the automatic update processing. [Figure 11] This is a functional block diagram related to functions associated with subscription-related functions among various functions implemented by a terminal device. [Figure 12] This is an explanatory diagram of an example of a method for selecting a plurality of benefits that can be provided in a subscription service. [Figure 13] This is an explanatory diagram of another example of a method for selecting a plurality of benefits that can be provided in a subscription service. [Figure 14A] This is an explanatory diagram (Part 1) of still another example of a method for selecting a plurality of benefits that can be provided in a subscription service. [Figure 14B] This is an explanatory diagram (Part 2) of still another example of a method for selecting a plurality of benefits that can be provided in a subscription service. [Figure 15] This is an explanatory diagram of the premise of one operation example. [Figure 16] This is a schematic diagram of the flow of one operation example. [Figure 17] This is an explanatory diagram of the premise of another operation example. [Figure 18] This is a schematic diagram of the flow of another operation example. [Figure 19] This is a schematic diagram of the flow of yet another operation example. [Figure 20] This is a schematic diagram of the flow of yet another operation example. [Figure 21] This is a schematic diagram of the flow of yet another operation example. [Modes for Carrying Out the Invention]

[0009] Hereinafter, each embodiment will be described in detail with reference to the accompanying drawings.

[0010] (Overview of Service System) With reference to Figure 1, an overview of the service system 1 according to the present embodiment will be described. Figure 1 is a block diagram of the service system 1 according to the present embodiment. The service system 1 includes a server device 10 and one or more terminal devices 20. In Figure 1, three terminal devices 20 are illustrated for simplicity, but the number of terminal devices 20 may be two or more.

[0011] The server device 10 is, for example, an information processing apparatus such as a server managed by a service operator. In the present embodiment, as an example, the server device 10 implements a so-called service platform, and provides various services via the service platform. Specifically, as an example, the server device 10 provides a service for providing digital content such as an application portal site (hereinafter also simply referred to as "site") and application software (hereinafter also simply referred to as "application"), and a social network function (hereinafter also simply referred to as "SNS function") to registered users (and guest users as necessary). Hereinafter, registered users (and guest users as necessary) are also simply referred to as "users".

[0012] The number of sites provided by the server device 10 is arbitrary, but in the present embodiment, as an example, it is assumed to be one site (hereinafter also referred to as "site A"). Note that in a modified example, site A may include a plurality of sites including related sites.

[0013] The types and number of digital content provided by the server device 10 are arbitrary, but in this embodiment, as an example, the digital content provided by the server device 10 may include one or more game applications (hereinafter also simply referred to as "game apps"), information provision applications, ebooks, etc. Game apps, etc., may be executable via Site A, or they may be executable without going through a predetermined site such as Site A (for example, they may be executable offline). That is, the various applications as digital content provided by the server device 10 may be installed on the terminal device 20 and used as so-called native applications. Hereinafter, "game" refers to a game related to a game app provided by the server device 10. Information provision applications may relate to information provision services of a specific genre (information provision services related to travel, housing, food, fashion, health, beauty, etc.), broadcasting services by a specific user (for example, YouTube®), etc. Furthermore, a specific application provided by the server device 10 may be a combination of multiple applications (for example, a hierarchical application).

[0014] The types and number of SNS functions provided by server device 10 are arbitrary, but here they may include functions such as diaries, chat, message boards / bulletin boards (communities), comments, messengers, friend requests, and sending objects (sending gifts). The SNS functions may be accessible via site A.

[0015] The terminal device 20 is an information processing device used by a user, such as a mobile phone, smartphone, tablet device, PC (Personal Computer), or game device. The terminal device 20 is capable of executing various applications according to this embodiment. These applications may be received by the terminal device 20 from the server device 10 or another predetermined application distribution server via the network 3, or they may be pre-stored in a storage device provided in the terminal device 20 or in a storage medium such as a memory card that the terminal device 20 can read. The server device 10 and the terminal device 20 are connected to each other via the network 3 so as to be able to communicate. For example, the server device 10 and the terminal device 20 cooperate to perform various processing related to the service.

[0016] Network 3 may include wireless communication networks, the Internet, VPNs (Virtual Private Networks), WANs (Wide Area Networks), wired networks, or any combination thereof.

[0017] (Server configuration) The configuration of the server device 10 will be described in detail. The server device 10 is composed of server computers. The server device 10 may be realized by multiple server computers working together.

[0018] The server device 10 comprises a server communication unit 11, a server storage unit 12, and a server control unit 13.

[0019] The server communication unit 11 includes an interface for communicating with external devices wirelessly or via wired connections to send and receive information. The server communication unit 11 may include, for example, a wireless LAN (Local Area Network) communication module or a wired LAN communication module. The server communication unit 11 can send and receive information with the terminal device 20 via the network 3.

[0020] The server storage unit 12 includes, for example, a primary storage device and a secondary storage device. For example, the server storage unit 12 may include semiconductor memory, magnetic memory, or optical memory. The server storage unit 12 stores various information and programs used for processing services. At least a portion of the information and programs stored in the server storage unit 12 may be shared and synchronized with the terminal device 20.

[0021] The server control unit 13 includes one or more processors. These processors may include general-purpose processors that perform specific functions by loading specific programs, and dedicated processors specialized for specific processing. The server control unit 13 controls the operation of the entire server device 10. Details of the server control unit 13 will be described later.

[0022] (Terminal device configuration) The configuration of the terminal device 20 will now be described in detail. As shown in Figure 1, the terminal device 20 comprises a terminal communication unit 21, a terminal storage unit 22, a display unit 23, an input unit 24, and a terminal control unit 25.

[0023] The terminal communication unit 21 includes an interface for communicating with external devices wirelessly or via wired connections to send and receive information. The terminal communication unit 21 may include, for example, a wireless communication module compatible with mobile communication standards such as LTE (LongTermEvolution) (registered trademark), a wireless LAN communication module, or a wired LAN communication module. The terminal communication unit 21 can send and receive information with the server device 10 via the network 3.

[0024] The terminal storage unit 22 includes, for example, a primary storage device and a secondary storage device. For example, the terminal storage unit 22 may include semiconductor memory, magnetic memory, or optical memory. The terminal storage unit 22 stores various information and programs used for processing services, which are received from the server device 10. The information and programs used for processing services may be obtained from an external device via the terminal communication unit 21. For example, a game application may be obtained from a predetermined application distribution server.

[0025] The display unit 23 includes a display device such as a liquid crystal display or an organic EL (Electro-Luminescence) display. The display unit 23 is capable of displaying a variety of screens.

[0026] The input unit 24 includes an input interface, for example, a touch panel integrated with the display unit 23. The input unit 24 is capable of receiving user input to the terminal device 20. The input unit 24 may also include physical keys, or any other input interface, such as a pointing device like a mouse.

[0027] The terminal control unit 25 includes one or more processors. The terminal control unit 25 controls the operation of the entire terminal device 20. The operation of the terminal control unit 25 will be described in detail below.

[0028] The terminal control unit 25 transmits and receives information via the terminal communication unit 21. For example, the terminal control unit 25 receives various information and programs used for processing services from at least one of the server device 10 and other external servers. The terminal control unit 25 stores the received information and programs in the terminal storage unit 22.

[0029] The terminal control unit 25 launches Site A and various applications (for example, native applications on the terminal device 20 or game applications within Site A) in response to user operations. The terminal control unit 25 works in cooperation with the server device 10 to execute service-related processing. For example, the terminal control unit 25 displays various screens related to service processing on the display unit 23. A GUI (Graphic User Interface) for detecting user operations may be displayed on the screen. The terminal control unit 25 can detect user operations on the screen via the input unit 24.

[0030] In this embodiment, as an example, each user can play one or more games via Site A. One of these games is, for example, a game like the one described below with reference to Figure 2.

[0031] (Game app overview) An overview of an example of a game application according to this embodiment will be described. The game according to this embodiment includes one or more game parts. At least one of the one or more game parts may be executed using a game medium.

[0032] Game media refers to electronic data used in a game, and includes any medium such as cards, items, points, in-service currency (or in-game currency), tickets, characters, avatars, parameters, etc. Game media may also refer to game-related information such as level information, status information, game parameter information (such as health points and attack power), or ability information (such as skills, abilities, spells, jobs, etc.). Game media is electronic data that can be acquired, owned, used, managed, exchanged, synthesized, enhanced, sold, discarded, or gifted by the user within the game, but the manner in which game media are used is not limited to those explicitly stated herein.

[0033] Unless otherwise specified, "game media owned by a user" refers to game media associated with a user ID that uniquely identifies the user. "Assigning game media to a user" means associating the game media with the user ID as owned game media. "Discarding game media owned by a user" means removing the association between the user ID and the owned game media. "Consuming game media owned by a user" means that some effect or impact may occur in the game as a result of removing the association between the user ID and the owned game media. "Selling game media owned by a user" means removing the association between the user ID and the owned game media, and associating another game media (e.g., virtual currency or items) with the user ID as owned game media. "Transferring game media owned by user A to user B" means removing the association between user A's user ID and the owned game media, and associating the game media with user B's user ID as owned game media. Furthermore, "creating a game medium" means defining or determining at least some of the information related to the game medium.

[0034] The game part is content that users can play within the game, and includes, for example, quests, missions, mini-games, training, strengthening, and synthesis of game materials, events to obtain game materials, events to explore virtual spaces, and events to battle opponents (for example, other users, enemy characters, and enemy buildings). Each game part may have one or more predetermined tasks (game tasks) set for it. For example, if it is determined that a user has successfully completed one or more game tasks set for a game part they are playing, the user may be rewarded with, for example, game materials. Game tasks can be any task appropriate to the content of the game part, such as, for example, a task to win a battle against an enemy character, a task to reach a goal in a virtual space, and a task to prevent the user's character from entering a predetermined state (for example, an incapacitated state) until a predetermined time has elapsed. Furthermore, the completion of a specific task (clear task) among the one or more game tasks set for a game part is also called clearing the game part. If a user playing a game part successfully completes a clear task, it is determined that the game part has been cleared, and the game part may end.

[0035] One or more game parts may include single-player game parts and multiplayer game parts. A single-player game part may include, for example, a game part that is executed based on user operations on one terminal device 20 used by one user (e.g., a game part for one person). For example, one terminal device 20 may execute the single-player game part alone, or one terminal device 20 and a server device 10 may cooperate to execute the single-player game part. On the other hand, a multiplayer game part may include, for example, a game part that is common to two or more users, executed based on user operations on two or more terminal devices 20 used by two or more users (e.g., a game part for multiple players). A game part common to two or more users may include, for example, a game part in which at least a part of the progression processing and at least a part of the processing results of the game part are commonly applied to those two or more users. For example, two or more terminal devices 20 may cooperate, or two or more terminal devices 20 and a server device 10 may cooperate to execute the multiplayer game part. A single game part may support both single-player and multiplayer.

[0036] One example of a game according to this embodiment includes a competitive game part having, for instance, elements of a side-scrolling action game and elements of a competitive game in which a player competes against an opponent using a game medium. The user selects one or more game mediums from among the game mediums they own (owned game mediums) to be used in the competitive game part. Hereinafter, each game medium used in the competitive game part will also be referred to as the first game medium. The one or more first game mediums together will also be referred to as a deck or team. The opponent is, for example, an automatically controlled game medium such as an NPC (Non-Player Character), but is not limited to this. For example, the opponent may be a game medium controlled by another user. The number of opponents in a single competitive game part may be arbitrarily determined.

[0037] The overview of the competitive game part according to this embodiment will be outlined with reference to Figure 2. Figure 2 shows an example of a gameplay screen used to explain the overview of the competitive game part.

[0038] A user playing a single-player versus game using terminal device 20 can, for example, operate a moving object 140 placed in a virtual space to acquire a predetermined item while avoiding obstacles. The moving object 140 corresponds to a predetermined game medium (second game medium). The second game medium may include, for example, a motorcycle, car, or person traveling on a road surface 141. In response to acquiring an item 142, the game mediums included in the deck (first game mediums A1, B, C, D, E) perform a predetermined action (for example, an attack on the opponent). The actions of the first game medium can inflict damage on the opponent (in Figure 2, object 144 related to the opponent is displayed). On the other hand, the opponent performs a predetermined action (for example, an attack on the user) at predetermined time intervals. The actions of the opponent can inflict damage on the user (in Figure 2, object 143 related to the user is displayed). Both the user and the opponent have predetermined parameters (total HP and HP) that decrease by the amount of damage inflicted. In Figure 2, image area 145 displays the remaining total HP as a gauge, image area 148 displays the remaining opponent's HP as a gauge, and image area 149 shows the state of each first game medium included in the deck. When the opponent's parameter decreases to a predetermined value (e.g., zero), the user is determined to have won. On the other hand, when the user's parameter decreases to a predetermined value (e.g., zero), the user is determined to have lost. If the user is determined to have won or lost, the game part of the match may end.

[0039] On the other hand, the multiplayer battle game part is executed in the same way as the single-player battle game part described above, except that two or more users play against a common opponent. Specifically, each of the two or more users plays the common battle game part using their own terminal device 20. Each of the two or more users operates the second game medium in the virtual space as described above. A common virtual space may be used for the two or more users, or an independent virtual space may be used for each user. The first game medium included in each of the two or more users' decks attacks, for example, against a common opponent. The opponent's parameters described above are applied in common to the two or more users. For example, the opponent's parameters may be synchronized among multiple terminal devices 20 used by each of the two or more users. When the opponent's parameters decrease to a predetermined value (e.g., zero), it is determined that the two or more users have won. On the other hand, when the parameters of each of the two or more users decrease to a predetermined value (e.g., zero), it is determined that the two or more users have lost. When it is determined that the two or more users have won or lost, the battle game part may end.

[0040] It should be noted that the games mentioned above are merely examples, and this embodiment can be applied not only to typical RPGs (Role-Playing Games), but also to fishing games, running games, dungeon games, Othello games, fighting games, city-building games, horse racing games, sports games such as baseball games, shooting games, and more.

[0041] (Subscription-related features) In this embodiment, the server device 10 further has functions for performing various processes related to subscription contracts (hereinafter also referred to as "subscription-related functions") in order to realize a subscription service. A subscription service is a service that allows users who have entered into a subscription contract (hereinafter also referred to as "contract users") to use the benefits selected by the contract user from among the various benefits that can be provided. In the following, unless otherwise specified, "benefits" refers to benefits that can be provided in the subscription service.

[0042] The various benefits that can be offered to contract users in the subscription service may be benefits that can be offered without going through network 3, or they may include, in addition to or instead, benefits that can be offered via network 3 (for example, benefits that can be offered on a site such as site A). In this embodiment, as an example, the various benefits that can be offered to contract users in the subscription service include the various benefits that can be offered on site A.

[0043] Benefits that can be provided without going through Network 3 are optional, but may include, for example, benefits that can be used when a contract user visits a specific physical store. In this case, benefits that can be used when visiting a specific physical store may include priority reservations for specific products, discounts on specific products, free or discounted shipping for specific products, reduced delivery time when using delivery services, free or discounted parking fees, etc.

[0044] The benefits that can be offered on Site A are determined on a case-by-case basis and are optional, but may include, for example, benefits related to specific services that can be offered on Site A. These specific services may include social networking features or paid services. Other specific services may include, for example, a service that allows users to purchase coins usable on Site A (described later as A Coins) on a deferred payment basis (hereinafter also referred to as the "deferred payment service"). In this case, the benefits related to receiving specific services on Site A may include benefits that allow access to the deferred payment service, or benefits that increase the spending limit for the deferred payment service.

[0045] Furthermore, the benefits that can be offered on Site A may include benefits related to the digital content that can be offered on Site A. These benefits may include, for example, benefits that allow users to obtain certain digital content that can be offered on Site A preferentially, benefits that allow users to obtain (use) digital content that can be offered on Site A at a discounted price, or one or more benefits set for certain digital content that can be offered on Site A. The one or more benefits set for certain digital content that can be offered on Site A are optional, but for example, if the certain digital content is a game app, they may include benefits that allow users to spin a predetermined lottery (e.g., a specific gacha (registered trademark)), benefits that allow users to participate in a specific event, benefits that ease the conditions for participating in a specific event, benefits that allow users to obtain a specific game medium, benefits that make it easier to obtain a specific game medium, benefits that increase the number or value of rewards that can be obtained in a specific event, or benefits that generate advantageous effects in a specific event. Furthermore, the one or more benefits set for a game app may be benefits unrelated to in-game gameplay, gacha, in-app purchases, etc. In this case, for example, the one or more benefits set for a game app may be in the form of a login bonus, a daily bonus, or a similar form. A login bonus refers to a reward given for logging in at predetermined intervals (daily). For example, a login bonus may be the granting of specific in-game currency usable within the game, or A-coins. A daily bonus is a reward that can be obtained once or a predetermined number of times, either daily or every predetermined number of days (two or more days). Unlike login bonuses, daily bonuses are not given upon login, but rather when the user performs an action to claim them at their discretion. The rewards for daily bonuses may be the same as login bonuses, such as specific in-game currency usable within the game, or A-coins.

[0046] Other possible benefits include a reduction in the parameters and time required for actions that can be performed within the digital content. In this case, if the digital content is a game app, utilizing this benefit can produce advantageous effects, such as reducing the cost required to complete a specific quest, making it easier to complete the quest, or reducing the time required to construct a specific building, making it easier to construct that building. Another possible benefit is an increase in the types of actions that can be performed within the digital content. In this case, if the digital content is a game app, utilizing this benefit can produce advantageous effects, such as being able to construct buildings that would normally be impossible to build, or being able to send specific stamps.

[0047] In this explanation, we have described several specific examples of one or more benefits offered in a game app in order to illustrate the concept of one or more benefits offered in a particular digital content. However, the specific digital content may not be a game app. Furthermore, the digital content for which one or more benefits are offered may be multiple digital contents available on Site A.

[0048] Figure 3 is a functional block diagram relating to the subscription-related functions among the various functions implemented by the server device 10. Figure 4 is an explanatory diagram of the data in the user information storage unit 30. In Figure 4 (and similarly in Figures 5 and 6 shown later), "***" means that some information is stored, and "···" means that the same information is repeated. Figure 5 is an explanatory diagram of information related to the game. Figure 6 is an explanatory diagram of the point parameters in the point parameter storage unit 31, Figure 7 is an explanatory diagram of the point count information in the point count information storage unit 32, and Figure 8 is an explanatory diagram of the selection information in the selection information storage unit 34.

[0049] As shown in Figure 3, the server device 10 includes a user information storage unit 30, a point parameter storage unit 31, a point count information storage unit 32, a reward information storage unit 33, a selection information storage unit 34, a billing processing unit 35, a point granting unit 36, a selection information acquisition unit 37, a determination unit 38, a reward management unit 40, an information update unit 42, a selection information update unit 44, a notification unit 46, a billing unit 48, a candidate selection unit 52, and a notification unit 54. The point parameter storage unit 31, the point count information storage unit 32, the reward information storage unit 33, and the selection information storage unit 34 can be implemented, for example, by the server storage unit 12 shown in Figure 1. In addition, the billing processing unit 35, the point granting unit 36, the determination unit 38, the reward management unit 40, the information update unit 42, the selection information update unit 44, the billing unit 48, and the candidate selection unit 52 can be implemented, for example, by the server control unit 13 shown in Figure 1. Furthermore, the selection information acquisition unit 37, the notification unit 46, and the notification unit 54 can be implemented, for example, by the server communication unit 11 and the server control unit 13 shown in Figure 1.

[0050] The distinction between the functional units from the billing processing unit 35 to the candidate selection unit 52 is for explanatory purposes only, and some or all of the functions of a particular functional unit (the functions described below) may be implemented by another functional unit. The same applies to the user information storage unit 30 to the selection information storage unit 34; some or all of the functions of a particular storage unit (the functions described below) may be implemented by another storage unit. Furthermore, some of the functions of the server device 10 may be implemented by the terminal device 20.

[0051] The user information storage unit 30 stores user information relating to users who use Site A. As shown in Figure 4, the user information includes username, password, telephone number, coins held, game-related information, SNS-related information, preference information, etc., in a manner that is associated with a user ID (an example of user identification information). The user information may include information that is initially registered, such as a user ID and username, as well as information that is accumulated retrospectively, such as game-related information.

[0052] A user ID is information that uniquely identifies a user. A user ID may also be in the form of a user account. Hereafter, a user ID will also be simply referred to as a user.

[0053] The username is information that identifies the user's name. Unlike the user ID, the username does not need to uniquely identify the user. The username may be arbitrarily determined and changed in response to user operations on the terminal device 20.

[0054] The password is used to enable login to Site A using the username. Multiple passwords may be set depending on their purpose.

[0055] The phone number is, for example, the phone number used for Short Message Service (SMS) authentication.

[0056] The number of coins held by the user represents the number of coins the user possesses (the number of coins currently available). In this embodiment, for example, the coins are those usable on Site A (hereinafter referred to as "A coins"), and the user can receive digital content or various rewards within the game by spending the A coins they possess. For example, the user can acquire a desired first game medium or a desired item by spending the A coins they possess. They can also use their A coins to, for example, spin a gacha. In a modified example, A coins may be game medium usable only within the game. The initial value of the number of coins held is, for example, 0. The number of coins held can be updated by the billing unit 48 as described later.

[0057] As shown in Figure 5, game information may include, for each user ID, rank, information about owned game media, information about used game media, and friend information.

[0058] Rank is a parameter that indicates the user's skill level in the game. In this embodiment, the rank value may increase as the user plays the game. A higher rank indicates a higher level of the user's skill level in the game.

[0059] Information regarding owned game media includes various pieces of information specific to the game media owned by the user within the game (owned game media). When game media is acquired by the user, that game media is associated with the user as owned game media. Details of the information regarding owned game media are omitted here, but each game media ID may include the game media name, rarity, level, cost, HP (Hit Points), attack power, recovery power, etc.

[0060] Information regarding the game medium to be used indicates the game medium (first game medium) to be used by the user in the competitive game part. The first game medium is selected from among the owned game mediums. In this embodiment, up to five game mediums, selected from one or more owned game mediums, are each associated with the user as the first game medium. Therefore, one game medium can be both an owned game medium and the first game medium. The first game medium may be selected automatically or in response to user operation in, for example, a dedicated game part. For example, such a dedicated game part may include a game part for so-called deck building or team building. Up to five first game mediums indicated in the information regarding the game medium to be used constitute one deck. The information regarding the game medium to be used may include information on multiple decks.

[0061] Friend information represents the user IDs of users who are friends in the game. For example, if user A is friends with users B and C, the friend information associated with user A will include the user IDs of users B and C. Friend relationships are established through friend requests, etc. Thus, friend information includes the user IDs of other users who are unidirectionally or bidirectionally associated with the user. Users who are friends may be able to communicate with each other, for example, by sending and receiving messages during gameplay. Information about a user may also include, in place of or in addition to friend information, information indicating the group they belong to (e.g., a guild or party).

[0062] The information regarding the game is not limited to what is described above. For example, user information may further include information indicating the in-game points the user possesses within the game. These in-game points are consumed by the user to play game parts. The amount of in-game points consumed may differ for each game part. These in-game points may increase, for example, over time or in accordance with the use of a predetermined game medium.

[0063] Information related to social networking services (SNS) may include various types of information related to SNS functions. For example, information related to SNS may include information about avatars and friend information for each user ID. Information related to avatars may include information about clothing for dressing up. Friend information may represent user IDs and group IDs connected through SNS functions. Friend information may be the same as or different from friend information in the game.

[0064] Preference information includes information that represents a user's preferences, or information that can be used to derive a user's preferences. Information that represents a user's preferences may include information that shows what services and benefits a user likes, what services and benefits a user dislikes, what services and benefits a user is interested in, and what services and benefits a user is not interested in. Preference information may be generated, for example, based on a simple questionnaire survey during initial registration. Information that can be used to derive a user's preferences may include user log information. In this case, the log information to be accumulated may be all log information that may be related to the user's preferences, or it may be specific log information (for example, log information related to operation logs). The log information represents various activities on Site A based on each user ID (login, logout, use of digital content, access to / use of SNS functions, billing, etc.). The log information to be accumulated may also include log information related to game play.

[0065] The point parameter storage unit 31 stores parameter information representing point parameters for each type of subscription contract. There may be only one type of subscription contract, but in this embodiment, as an example, there are two types of subscription contracts, "Subscription Contract A1" and "Subscription Contract A2," as shown in Figure 6. Point parameters are parameters used to calculate predetermined points, which will be described later. In Figure 6, the value of the point parameter for "Subscription Contract A1" is "5," and the value of the point parameter for "Subscription Contract A2" is "10."

[0066] In the example shown in Figure 6, the point parameter storage unit 31 displays the amount (monthly) that the contract user will pay under the subscription contract for each type of subscription contract.

[0067] The parameter information in the point parameter storage unit 31 is updated accordingly when the type of subscription contract changes (for example, when one type is deleted or a new type is added).

[0068] The points information storage unit 32 stores point information for each of the multiple benefits that can be offered in the subscription service, representing the number of points associated with using that benefit. In Figure 7, the multiple benefits that can be offered in the subscription service include "Benefit B1," "Benefit B2," etc., and the number of points (the number of points required to use that benefit) is defined for each.

[0069] The point information stored in the point information storage unit 32 is updated accordingly when the benefits available in the subscription service change (for example, when one benefit is removed or a new benefit is added).

[0070] In this embodiment, the number of benefits that can be offered in the subscription service is significantly greater than the number of types of subscription contracts. For example, the number of types of subscription contracts may be around 2 to 5, while the number of benefits that can be offered in the subscription service is, for example, 10 or more. The number of benefits that can be offered in the subscription service and the number of types of subscription contracts may be increased or decreased as appropriate during operation, but even in this case, the relationship that the number of benefits that can be offered in the subscription service is significantly greater than the number of types of subscription contracts will be maintained.

[0071] The benefit information storage unit 33 stores benefit information (not shown) relating to multiple benefits that can be offered in the subscription service. The benefit information may include information describing the content of the benefits. The benefit information in the benefit information storage unit 33 is updated accordingly when the benefits that can be offered in the subscription service change (for example, when one benefit is deleted or a new benefit is added).

[0072] The selection information storage unit 34 stores selection information for each contract user. The selection information is associated with a user ID and represents one or more benefits selected by the contract user from among multiple benefits that can be offered in the subscription service. In the example shown in Figure 8, user ID "U01" is associated with three benefits consisting of "Benefit B1", "Benefit C1", and "Benefit D1", and user ID "U03" is associated with four benefits consisting of "Benefit B2", "Benefit C1", "Benefit D95", and "Benefit E60". In this case, the three benefits consisting of "Benefit B1", "Benefit C1", and "Benefit D1" are shown to have been selected by the contract user associated with user ID "U01", and the four benefits consisting of "Benefit B2", "Benefit C1", "Benefit D95", and "Benefit E60" are shown to have been selected by the contract user associated with user ID "U03".

[0073] The billing processing unit 35 performs various billing processes based on the subscription contract. For example, in the example shown in Figure 6, the billing processing unit 35 processes a payment of "500 yen" each month for contract users who have entered into "Subscription Contract A1" (for example, by automatic withdrawal from the registered account), and processes a payment of "1000 yen" each month for contract users who have entered into "Subscription Contract A2". The billing processing unit 35 may notify the corresponding contract user of the details once the payment process is completed. Such notification may be done via Site A or by email, etc. The monthly billing amount (the billing amount related to the subscription contract) is basically constant, but may be changed as appropriate. For example, the billing processing unit 35 may bill an amount different from the regular monthly charge only for a specific period. In addition, if a campaign such as the first month free or the birthday month free is implemented, the billing processing unit 35 may perform billing processing according to the content of the campaign.

[0074] The point awarding unit 36 ​​associates a predetermined number of points corresponding to the type of subscription contract with the user ID of the contracting user, for each predetermined period ΔT1 related to the subscription contract. The predetermined period ΔT1 is arbitrary and may differ depending on the type of subscription contract, but in this embodiment, it is a fixed one month. The predetermined number of points is determined according to the type of subscription contract. In this embodiment, as an example, the predetermined number of points is determined based on a point parameter associated with the type of subscription contract. Specifically, the point awarding unit 36 ​​refers to the parameter information in the point parameter storage unit 31 and determines the predetermined number of points based on the value of the point parameter associated with the type of subscription contract by the contracting user. For example, the point awarding unit 36 ​​determines (calculates) the predetermined number of points pt from the value of the point parameter k1 using the following calculation formula: pt = k1 × 10. In this case, if the point parameter is "5", the predetermined number of points is "50", and if the point parameter is "10", the predetermined number of points is "100". In a modified example, the value of the point parameter may be a parameter that represents the predetermined number of points itself. In other variations, the point parameter may not be a numerical parameter, but rather represents the type of subscription contract. In any case, the point awarding unit 36 ​​refers to the parameter information in the point parameter storage unit 31 and determines a predetermined number of points based on the point parameter associated with the type of subscription contract by the contracting user.

[0075] The timing of the point awarding unit 36 ​​is arbitrary and may differ for each contract user, or it may be constant. For example, it may be every other month depending on the contract date. In this case, for example, the update timing will be different for each user, such as the 26th and the 23rd. However, in this embodiment, as an example, the timing of the point awarding unit 36 ​​awarding the predetermined points is at the time of contract for new contract users, and uniformly at the beginning of the month (for example, when the settlement processing by the billing processing unit 35 is completed) for other contract users. The point awarding unit 36 ​​may also automatically associate the predetermined points according to the type of subscription contract with each contract user's user ID when the current time is 0:00 on the first day of the month, based on the date and time information.

[0076] In this embodiment, the point awarding unit 36 ​​assigns a predetermined number of points corresponding to the type of subscription contract for each predetermined period ΔT1, regardless of the selection information of the contract user in the most recent predetermined period ΔT1. In other words, in this embodiment, even if a contract user has selected benefits with significantly fewer points than the predetermined number in the most recent predetermined period ΔT1, the difference in points will not be carried over to the next predetermined period ΔT1. However, in modified versions, such point carryover may be implemented.

[0077] Furthermore, if a point-boosting campaign is implemented in which a predetermined number of points are awarded in a specific month, such as the first month or the user's birthday month, the point awarding unit 36 ​​may award the predetermined number of points to each contract user according to the details of the campaign. In this case, each contract user can use the additional benefit as a "trial" only in that specific month, thus improving convenience. If each contract user is satisfied with the trial of the additional benefit, they can also change their selection information to incorporate that additional benefit from the following month. In this modified example, selection information for a specific month and selection information for a normal month may be set.

[0078] The selection information acquisition unit 37 acquires selection information from each contract user. The selection information is as described above. The selection information acquisition unit 37 stores the acquired selection information in the selection information storage unit 34.

[0079] The determination unit 38 determines, for each contract user, whether the total number of points associated with one or more benefits selected by the contract user has a predetermined relationship with the predetermined points associated by the point awarding unit 36 ​​(predetermined points associated with the user ID related to the contract user).

[0080] The total number of points associated with one or more benefits selected by a contract user is determined based on the selection information (selection information relating to the corresponding contract user) in the selection information storage unit 34 and the point count information in the point count information storage unit 32. In other words, for a given contract user, "the total number of points associated with one or more benefits selected by that contract user" is the total number of points associated with the benefits represented by the selection information relating to that contract user. Hereinafter, such a total number of points will also be referred to as "the total points of selected benefits."

[0081] For example, in the example shown in Figure 8, the selection information related to user ID "U01" indicates that three benefits, consisting of "Benefit B1," "Benefit C1," and "Benefit D1," have been selected by the contract user associated with user ID "U01." In this case, according to the point information in the point information storage unit 32 (see Figure 7), if the points associated with "Benefit B1," "Benefit C1," and "Benefit D1" are pt1, pt2, and pt3 respectively, then the total points of the selected benefits are the sum of the points associated with "Benefit B1," "Benefit C1," and "Benefit D1," which is pt1 + pt2 + pt3. Therefore, in this case, the determination unit 38 will determine the relationship between the predetermined points associated with user ID "U01" and the total points of the selected benefits (=pt1 + pt2 + pt3). In this case, the predetermined points pt are calculated as pt = k1 × 10 based on the value k1 of the point parameter associated with user ID "U01," as described above.

[0082] In this embodiment, as an example, the predetermined relationship is one in which the total points of the selected rewards are less than or equal to a predetermined number of points. In this case, the determination unit 38 performs a determination process to determine whether or not the total points of the selected rewards are less than or equal to a predetermined number of points.

[0083] Here, selection information indicating that a reward has been selected whose total points exceed a predetermined number of points is referred to as "selection information requiring re-selection," and other selection information (i.e., selection information indicating that a reward has been selected whose total points do not exceed a predetermined number of points) is referred to as "selection information that does not require re-selection." In this embodiment, only selection information that does not require re-selection is stored in the selection information storage unit 34.

[0084] The determination method by the determination unit 38 may differ depending on whether the selection information acquired by the selection information acquisition unit 37 may include selection information that requires re-selection. For example, if the selection information acquired by the selection information acquisition unit 37 may include selection information that requires re-selection, the determination unit 38 may perform a determination process based on the selection information acquired by the selection information acquisition unit 37. On the other hand, if the selection information acquired by the selection information acquisition unit 37 does not include selection information that requires re-selection (for example, if the selection by the contract user is performed on the terminal device 20 so that only selection information that does not require re-selection is sent to the server device 10), the determination unit 38 may make a determination based on whether or not selection information is acquired by the selection information acquisition unit 37. In this case, if selection information is acquired by the selection information acquisition unit 37, the determination unit 38 may determine that the total points of the selection benefits based on that selection information have a predetermined relationship with a predetermined point value (i.e., the selection information may be determined to be "selection information that does not require re-selection").

[0085] In this embodiment, the notification unit 54, described later, performs notification processing to notify contract users, etc., of combinations of benefits in a manner that only selection information that does not require re-selection is acquired. That is, the notification unit 54, described later, notifies a single contract user (or non-contract user) of combinations that can be selected within a range in which the total points of the selected benefits do not exceed a predetermined number of points. Therefore, in this embodiment, when a user makes a selection based on the notification from the notification unit 54, only selection information that does not require re-selection is transmitted to the server device 10. In other words, in this embodiment, the selection by the contract user is performed in the terminal device 20 in such a manner that only selection information that does not require re-selection is transmitted to the server device 10.

[0086] The reward management unit 40 enables a contract user to use one or more selected rewards when the determination unit 38 determines that the total points of selected rewards based on selection information have a predetermined relationship to predetermined points. In other words, it enables the use of one or more selected rewards based on user identification information. The process by the reward management unit 40 to enable the use of rewards may be implemented in an appropriate manner according to the attributes of each reward. For example, if the attribute of a reward is that it can be used when using a specific physical store, the process to enable the use of the reward may be implemented by issuing a coupon to make the reward available. This type of coupon may be sent to the terminal device 20 as an electronic coupon or mailed as a paper coupon. Also, if the attribute of a reward is that it can be offered on site A, the process to enable the use of the reward is the process of making the reward available on site A. For example, if the benefit offered on site A is the ability to participate in a specific event in a game app, the process that enables the use of the benefit may be the process of sending an invitation ticket to the specific event as an electronic ticket to the terminal device 20, or the process of making a participation button appear on the home screen of the game app.

[0087] Furthermore, the benefits management unit 40 may appropriately restrict the use of benefits depending on their usage status. For example, if a benefit is only available once a month, and that benefit is used by one contract user, the benefits management unit 40 will restrict that contract user's use of that benefit for the remainder of that month.

[0088] The information update unit 42 updates the point count information in the point count information storage unit 32 and the benefit information in the benefit information storage unit 33 in response to changes such as the addition or deletion of benefits that can be offered in the subscription service. In addition, the information update unit 42 updates the parameter information in the point parameter storage unit 31 in response to changes such as the addition or deletion of types of subscription contracts.

[0089] The selection information update unit 44 updates the selection information in the selection information storage unit 34 in response to a change instruction from the contract user. The contract user can freely change their selection information as long as the total points of the selected benefits do not exceed a predetermined number of points. In other words, the contract user can re-select the desired benefits. However, such changes may be made every predetermined period ΔT1. Furthermore, when the selection information acquisition unit 37 acquires selection information from a new contract user, the selection information update unit 44 updates the selection information in the selection information storage unit 34.

[0090] In this embodiment, assuming that a subscription contract pertaining to a particular contract user is maintained, the selection information in the selection information storage unit 34 pertaining to that contract user will remain unchanged unless the contract user issues an instruction to change the selection information.

[0091] However, the benefits offered in a subscription service may be changed from time to time, such as being added or removed. For example, if one of the benefits offered in a subscription service is discontinued, but a new equivalent benefit is introduced to replace it, a subscriber who has selected that benefit may find it cumbersome to have to go through the selection process of selecting the new equivalent benefit each time.

[0092] Therefore, the selection information update unit 44 preferably performs an automatic update process to automatically update the selection information in the selection information storage unit 34 in accordance with the specific change when there is a specific change regarding the benefits that can be provided in the subscription service. Figure 9 is an explanatory diagram of the automatic update process. Figure 10 is an explanatory diagram of the selection information in the selection information storage unit 34 after the automatic update process. Figure 9 shows in chronological order that “Benefit B1” (an example of the first benefit) ends (becomes unavailable) at time t1 (an example of a certain timing) between February and March, and “Benefit B1'” (an example of the second benefit) becomes available from time t1. “Benefit B1'” is assumed to be a benefit related to “Benefit B1”. Here, the relationship between benefits may include not only relationships where there are differences in version or detailed specifications, but also relationships where the attributes of the benefits are the same but there are significant differences in specifications. For example, if benefit B1 is provided only for a certain period and is not provided from the next period onward, “Benefit B1'” may be a benefit that functions as a successor (successor version) to “Benefit B1”. In this case, the selection information update unit 44 performs an automatic update process by rewriting the selection information that selects "Benefit B1" as the selection target (in Figure 10, the selection information related to user ID "U01"), changing the selection target from "Benefit B1" to "Benefit B1'", as shown in Figure 10. This enables the selection information to be automatically updated in response to specific changes in the benefits that can be offered in the subscription service, without requiring the contract user to enter complicated information for the changes, thus achieving a user-friendly configuration.

[0093] In Figure 9, when the selection information update unit 44 performs the automatic update process as described above, from time t1, one of the benefits available to the contract user associated with user ID "U01" is changed from "Benefit B1" to "Benefit B1'". Accordingly, the benefit management unit 40 changes one of the benefits available to the contract user associated with user ID "U01" from "Benefit B1" to "Benefit B1'".

[0094] In the example shown in Figure 9, time t1 is in the middle of the month, not the beginning of the month, but it could be the beginning of the month. In this case, the timing of the change from “Benefit B1” to “Benefit B1'” is synchronized with the start timing of each predetermined period ΔT1 of the subscription contract. Also, in the example shown in Figure 9, the timing at which “Benefit B1” becomes unavailable and the timing at which “Benefit B1'” becomes available are the same time t1, but these timings may be staggered. For example, the timing at which “Benefit B1'” becomes available may be before the timing at which “Benefit B1” becomes unavailable. In this case, a transition period will be set during which both “Benefit B1” and “Benefit B1'” can be selectively used. In this way, the timing at which “Benefit B1'” becomes available does not necessarily have to be the same as the timing at which “Benefit B1” becomes unavailable, as long as it is set to coincide with the timing at which “Benefit B1” becomes unavailable.

[0095] Furthermore, the feasibility of such automatic renewal processing may be determined on a case-by-case basis for each contract user. For example, contract users may be asked in advance (e.g., at the time of contract) whether they wish to perform such automatic renewal processing. In this case, automatic renewal processing can be implemented in a manner that suits the intentions of each contract user. Furthermore, for contract users who do not wish to perform automatic renewal processing, guidance (notification) may be sent as appropriate to prompt them to perform a selection process to re-select their benefits. Furthermore, this type of notification may be implemented in a manner similar to the notification by the notification unit 46 described later.

[0096] When the selection information update unit 44 performs an automatic update process (rewriting of selection information), the notification unit 46 notifies the notification destination associated with the user identification information, based on the user identification information associated with the selection information for which the automatic update process has been performed, of information regarding the rewriting. The notification method is arbitrary and may be implemented by email, in-app notification, chat function on site A, telephone notification, or postal notification in paper form. For example, in the example shown in Figure 10, the notification unit 46 may notify the telephone number (see Figure 4), which is an example of a notification destination associated with user ID "U01", of information regarding the rewriting via SMS.

[0097] The billing unit 48 performs processing related to the billing service. In this embodiment, as an example, A coins are available on site A. In this case, when the billing unit 48 receives a request from a user to provide (purchase) A coins, it provides A coins to the user under predetermined conditions. The term "user" here includes users other than contracted users, and the same applies in the following description of the billing unit 48. The billing unit 48 may provide A coins to the user on the condition of settlement at that time, rather than on a deferred payment basis, or it may provide A coins to the user on a deferred payment basis based on a deferred payment service.

[0098] Furthermore, when the billing unit 48 receives a request from a user to spend A coins, it processes the A coins and enables the user to use predetermined benefits corresponding to the spending. Therefore, in this embodiment, a user can use predetermined benefits on site A by spending A coins. The predetermined benefits may include benefits that allow the user to acquire a desired first game medium, benefits that allow the user to acquire a desired item, benefits that allow the user to spin a desired gacha, etc.

[0099] In this embodiment, the benefits that can be offered in the subscription service preferably include benefits different from predetermined benefits that can be used by consuming A coins. For example, some of the multiple benefits that can be offered in the subscription service are the same as predetermined benefits that can be used by consuming A coins, but the other multiple benefits that can be offered in the subscription service are different from predetermined benefits that can be used by consuming A coins. This allows the operator to effectively promote the use of the subscription service by providing attractive benefits that can only be used when using the subscription service. Furthermore, it becomes possible to differentiate between the subscription service and the billing service, and to design benefits that are tailored to the characteristics of the subscription service. In the modified example, the billing service may be omitted and unified into the subscription service.

[0100] Furthermore, even if some of the multiple benefits offered in the subscription service are the same as the predetermined benefits available by consuming A-coins, the subscription service may be designed to be more price-advantageous than the pay-per-use service. This can effectively encourage the use of the subscription service. Alternatively, all predetermined benefits available by consuming A-coins may be available as benefits offered in the subscription service. This would give the subscription service an advantage over the pay-per-use service and effectively encourage the use of the subscription service.

[0101] The candidate selection unit 52 selects one or more combination candidates from among the various combinations of multiple benefits that can be offered in the subscription service, within the range where the total points of the selected benefits do not exceed a predetermined point limit. In other words, the candidate selection unit 52 selects one or more combination candidates in which the total points of the selected benefits have a predetermined relationship with the predetermined point limit.

[0102] In this case, the candidate selection unit 52 may randomly select one or more combination candidates. However, the candidate selection unit 52 preferably selects one or more recommended combination candidates for each user. Here, "user" includes users other than contract users, and the same applies to the candidate selection unit 52 and its description below.

[0103] For example, the candidate selection unit 52 selects one or more combination candidates that match the user's preferences based on preference information from the user information stored in the user information storage unit 30. For example, if the preference information for a particular user indicates that the user has a high preference for a specific game app, then one or more combination candidates may be selected in such a way that they include at least one of the benefits offered in that specific game app.

[0104] Alternatively, the candidate selection unit 52 selects one or more combination candidates that are suitable for the user based on the log information among the user information in the user information storage unit 30.

[0105] For example, with respect to a particular user, the system may derive the user's game progress from the user's log information, and if a specific reward set in the game app would be useful based on that progress, one or more combination candidates may be selected, each including at least one of those specific rewards. Game progress refers to, for example, the state or situation of how much of the game's content has been consumed (achieved / cleared). For example, in a game where clearing missions or quests changes the stage, level, story, etc., the progress may refer to the user's current stage, level, etc. In this case, the specific reward may be a reward that varies depending on the stage, level, etc., and is useful for further game progress. The game progress is derived directly or indirectly based on log information, and may be derived from, for example, information about the game (see Figure 5), or it may be part of the information about the game. The information about the game is generated based on log information. In this case, based on the user's progress, the system can derive or predict the next action the user should or will take, and present a reward suitable for that action. Such prediction of actions may be achieved using artificial intelligence. For example, it is possible to use artificial intelligence to input log information and output (generate) predicted results for operations. In the case of artificial intelligence, this can be achieved by implementing a convolutional neural network obtained through machine learning. In machine learning, for example, actual data related to log information is used to learn the weights of the convolutional neural network that minimize the error in the prediction results.

[0106] Alternatively, with respect to a particular user, the user's operational tendencies may be derived from the user's log information, and if, according to these operational tendencies, a specific reward set in the game app would be useful, one or more combination candidates may be selected, each including at least one of those specific rewards. In this case, based on the user's operational information, the next operation the user should or will perform can be derived or predicted, and a reward suitable for that operation can be presented. Similarly, such operation predictions may be realized using artificial intelligence. For example, it is possible to use artificial intelligence to input log information and output (generate) operation prediction results. In the case of artificial intelligence, this can be realized by implementing a convolutional neural network obtained through machine learning. In machine learning, for example, the weights of the convolutional neural network that minimize the error in the prediction result are learned using actual data related to log information.

[0107] Furthermore, the method of selecting one or more combination candidates based on the game's progress and operation tendencies, as described above, is not limited to game apps but can also be applied to other apps.

[0108] The timing of the selection process performed by the candidate selection unit 52 may be in accordance with the timing of the notification by the notification unit 54, which will be described later. For example, the timing of the selection process performed by the candidate selection unit 52 for one or more combination candidates relating to a particular user may be when the user applies for a regular purchase (when the regular purchase contract is concluded), or when the regular purchase contract of the user (contract user) is renewed (in this embodiment, for example, at the beginning of the month).

[0109] Incidentally, as mentioned above, the various benefits that can be offered in a subscription service may be changed after the fact. Also, the preferences of the contracting user, the user's game progress, and the user's operational tendencies may change after the fact. Therefore, the candidate selection unit 52 preferably selects one or more combination candidates that are suitable for the user's preferences, the user's game progress, and the user's operational tendencies, based on the user information in the user information storage unit 30, either periodically or irregularly, even at times other than when the subscription contract is concluded. In this case, the notification timing by the notification unit 54, which will be described later, may be synchronized with the selection timing by the candidate selection unit 52. This makes it possible to present the user with benefits that are suitable for the user in response to various changes after the fact.

[0110] Here, when the candidate selection unit 52 performs selection processing based on user information as described above, the execution conditions for the selection processing may be limited to cases where there is a significant change in user information and / or a change in the benefits that can be offered in the subscription service. For example, the timing of the selection processing by the candidate selection unit 52 for one or more combination candidates relating to a particular user may be set when there is a significant change in the user's preferences based on the user information of that user, the user's game progress, the user's operation tendencies, etc. This reduces the frequency of selection processing by the candidate selection unit 52, thereby efficiently reducing the processing load.

[0111] The notification unit 54 notifies the user of one or more combinations of various benefits that can be offered in the subscription service, provided that the total points of the selected benefits do not exceed a predetermined number of points. The notification method is arbitrary and may be the same as the notification method used by the notification unit 46 described above. The timing of the notification by the notification unit 54 is also arbitrary and may be, for example, at the time of subscription application, at renewal, or synchronized with the selection timing by the candidate selection unit 52 as described above. Furthermore, if information regarding the subscription service is posted on Site A, the notification may be sent to the user when they view such information.

[0112] Upon receiving a notification from the notification unit 54, the user selects one desired combination from the one or more combinations notified, and "selection information that does not require re-selection" is sent to the server device 10.

[0113] In this embodiment, the notification unit 54 may notify the user of one or more randomly selected combinations (provided that the total points of the selected rewards do not exceed a predetermined number of points), but preferably, it notifies the user of one or more combination candidates selected by the candidate selection unit 52. This makes it possible to notify each user of combination candidates that are likely to suit the user's preferences, the user's game progress, the user's operation tendencies, etc., making it easier for the user to select their desired reward. In other words, by presenting such notifications on the selection screen (see Figures 13 and 14A) described later, a user interface (UI) that makes it easy for the user to select their desired reward can be realized.

[0114] Figure 11 is a functional block diagram relating to the subscription-related functions among the various functions implemented by the terminal device 20. Figure 12 is an explanatory diagram of one example of a method for selecting from multiple benefits that can be offered in a subscription service, and shows an example of a selection screen. Figure 13 is an explanatory diagram of another example of a method for selecting from multiple benefits that can be offered in a subscription service, and shows another example of a selection screen. Figures 14A and 14B are explanatory diagrams of another example of a method for selecting from multiple benefits that can be offered in a subscription service, and show other examples of selection screens. In the following explanation relating to Figure 11, "user" refers to the user of the terminal device 20.

[0115] As shown in Figure 11, the terminal device 20 includes a selection screen output unit 210, a selection result generation unit 212, and a selection information transmission unit 214. The selection screen output unit 210 and the selection result generation unit 212 can be implemented, for example, by the terminal control unit 25 shown in Figure 1. The selection information transmission unit 214 can also be implemented, for example, by the terminal communication unit 21 and the terminal control unit 25 shown in Figure 1. Note that some or all of the functions of the selection screen output unit 210 and / or the selection result generation unit 212 may be implemented by the server device 10.

[0116] The selection screen output unit 210 outputs a selection screen to assist the user in selecting their desired benefits. For example, when the user operates the subscription button (or subscription benefit selection change button) (not shown) on the terminal device 20 for site A, the selection screen output unit 210 outputs a selection screen. The selection screen is arbitrary, as long as it allows the user to select any one or more combinations of the multiple benefits that can be offered in the subscription service.

[0117] In the example shown in Figure 12, the selection screen G1200 includes checkboxes B1211, B1212, B1213, ... that allow the user to select all of the multiple benefits available in the subscription service. The checkboxes B1211, B1212, B1213, ... are located near the benefit buttons B1201, B1202, B1203, ... which represent the corresponding benefits. The benefit buttons B1201, B1202, B1203, ... may display the name of the benefit and the number of points required to use the benefit. The number of points required to use the benefit is consistent with the point information in the point information storage unit 32 shown in Figure 7. The benefit buttons B1201, B1202, B1203, ... may be configured to transition to a screen explaining the benefit when operated. In this case, the explanation screen may contain an explanation based on the benefit information in the benefit information storage unit 33. In this way, users can easily select their desired benefits by checking the corresponding checkboxes associated with each benefit button that corresponds to their desired combination of benefits.

[0118] Furthermore, the selection screen G1200 may be a scrollable screen. Also, if there are many different benefits that can be offered in the subscription service, multiple selection screens G1200 may be provided for each category.

[0119] Furthermore, in the example shown in Figure 12, the selection screen G1200 includes an image section G1230 representing the currently selected reward and an image section G1240 displaying the total number of points associated with using the currently selected reward. The selection screen G1200 also includes a confirmation button B1220. The user can complete the reward selection process by selecting the desired combination of rewards and then operating the confirmation button B1220.

[0120] The selection screen output unit 210 may activate only the selectable checkboxes among checkboxes B1211, B1212, B1213, etc., so that the total number of points associated with the use of the currently selected benefits does not exceed a predetermined number of points. For example, in the example shown in Figure 12, the total number of points associated with the use of the currently selected benefits is "40". In this case, if the predetermined number of points is "50", the selection screen output unit 210 may activate only the checkboxes related to benefits for which the number of points associated is "10" or less. In this case, the selection screen output unit 210 will cooperate with the determination unit 38 of the server device 10 to determine whether the total number of points for the selected benefits is less than or equal to the predetermined number of points.

[0121] In the example shown in Figure 12, checkboxes B1211, B1212, B1213, etc. are initially unchecked, but checkboxes corresponding to recommended sets, as in the example shown in Figure 13, may be checked by default. In this case, for example, the user may operate a button (not shown) such as "Enable recommended default selection" to check the checkboxes corresponding to recommended sets, as in the example shown in Figure 13. In these cases, various recommended benefits can be presented to each user based on the notification from the notification unit 54 described above, thus realizing a user interface (UI) that makes it easy for users to select their desired benefits.

[0122] In the example shown in Figure 13, the selection screen G1300 is generated in a manner that makes it easy for the user to select one or more combinations based on one or more combinations notified by the notification unit 54 described above. Specifically, the selection screen G1300 includes checkboxes B1311, B1312, ... that allow the selection of multiple recommended sets, and the checkboxes B1311, B1312, ... are placed near the "recommended set buttons" B1301, B1302, ... that represent the corresponding recommended sets. At least one of the multiple recommended sets corresponds to the benefits of one or more combinations notified by the notification unit 54 described above. Note that although there are multiple recommended sets in Figure 13, there may be only one. The "Recommended Set" buttons B1301, B1302, ... may display the names of one or more benefits that make up the recommended set. Furthermore, the "Recommended Set" buttons B1301, B1302, ... may be configured to transition to the explanation screen for one or more benefits that make up the recommended set when operated. In this way, if a recommended set corresponding to the desired combination of benefits exists, the user can easily select the desired benefits by checking the corresponding checkbox. In this manner, various recommended benefits can be presented to each user based on the notification from the notification unit 54 described above, thus realizing a user interface (UI) that facilitates the selection of desired benefits by the user.

[0123] Furthermore, in the example shown in Figure 13, the selection screen G1300 includes an OK button B1320. The user can select their desired recommended set and then complete the selection process by operating the OK button B1320.

[0124] The selection screen G1300 may be implemented in combination with the selection screen G1200. For example, as shown in Figure 13, the selection screen G1300 includes an OK button B1320, and when the user operates the OK button B1320, the selection screen output unit 210 transitions from the selection screen G1300 to the selection screen G1200. In this case, the selection screen G1200 may be output with a check mark placed in each checkbox associated with each benefit that makes up the recommended set checked on the selection screen G1300. In this case, the user can complete the selection process by operating the confirmation button B1220 after making a final confirmation of the contents of the image unit G1230 on the selection screen G1200, provided there are no problems.

[0125] In the examples shown in Figures 14A and 14B, there are buttons B1411, B1412, ... that allow users to check all recommended sets at once, and it is also possible to check checkboxes B1421, B1422, B1423, ... corresponding to each benefit within the recommended set buttons B1401, B1402, ... In this case, the user can select the button for the desired recommended set from among buttons B1400, B1401, ... and then swap some of the benefits within the recommended set associated with the selected button. Specifically, for example, if the user selects the button for the benefit they want to swap from buttons B1431, B1432, B1433 representing the benefits in "Recommended Set 1", they will be taken to a benefit selection screen (not shown) where they can select the desired benefit. In the examples shown in Figures 14A and 14B, the user selects button B1411, which corresponds to “Recommended Set 1” in Figure 14A, and then changes from “Benefit B1” to “Benefit B2” within “Recommended Set 1.” In this way, a user interface (UI) that allows for flexible selection of benefits while saving the user effort can be realized.

[0126] In the examples shown in Figures 14A and 14B, buttons B1411, B1412, ... are initially unchecked, but the checkbox corresponding to the most recommended set may be checked by default. Furthermore, when any of buttons B1411, B1412, ... are selected, the buttons representing the benefits within that selected set (buttons B1431, B1432, B1433, etc.) may be automatically checked.

[0127] The selection result generation unit 212 generates the selection results of the user's rewards based on the user's input on the selection screen. For example, in the example shown in Figure 12, the combination of rewards with a checkmark when the confirmation button B1220 is pressed is generated as the selection result.

[0128] The selection information transmission unit 214 transmits selection information, including the selection result generated by the selection result generation unit 212, to the server device 10. In this case, the selection information transmission unit 214 may transmit selection information, which associates the user ID of Site A with the selection result generated by the selection result generation unit 212, to the server device 10 (selection information acquisition unit 37) as a change instruction. In this way, the selection information transmitted from the terminal device 20 is acquired by the selection information acquisition unit 37 of the server device 10, as described above. Note that the selection information generated based on the selection screen G1200 or G1300 shown in Figure 12 or Figure 13 is the "selection information that does not require re-selection" as described above.

[0129] As described above, the embodiment offers the following excellent effects in particular.

[0130] First, according to this embodiment, a predetermined number of points corresponding to the type of subscription contract are awarded to the contract user at predetermined intervals ΔT1. Then, the contract user can select and use a desired combination of benefits from among the multiple benefits available in the subscription service, provided that the total points of the selected benefits do not exceed the predetermined number of points.

[0131] Therefore, according to this embodiment, it is possible to diversify the combinations of benefits available through a subscription contract without excessively diversifying the types of subscription contracts. Specifically, in the comparative example where the number of subscription contract types is equal to the number of possible combinations of diverse benefits, the number of subscription contract types becomes excessively diversified, and the processing load related to subscription contracts increases. In contrast, according to this embodiment, it is possible to diversify the combinations of benefits available through a subscription contract while setting a smaller number of subscription contract types, without setting a number of subscription contract types equal to the number of possible combinations of diverse benefits.

[0132] Furthermore, according to this embodiment, the selection information update unit 44 updates the selection information in the selection information storage unit 34 in response to a change instruction from the contract user, as described above. Therefore, according to this embodiment, the user can change the selection information retrospectively without changing the type of subscription contract.

[0133] In this way, according to this embodiment, it is possible to reduce the processing load related to subscription contracts while improving the convenience of contract users.

[0134] Furthermore, according to this embodiment, as described above, the selection information update unit 44 performs an automatic update process (rewriting of selection information) in response to specific changes in the benefits available in the subscription service. Therefore, even if specific changes occur in the benefits available in the subscription service, the contract user can maintain a state where they can use equivalent benefits without taking any special procedures. This efficiently reduces the processing load on the server device 10 compared to outputting notifications to the contract user regarding changes in selection information in response to specific changes in the benefits available in the subscription service.

[0135] Furthermore, according to this embodiment, when the selection information update unit 44 performs an automatic update process (rewriting of selection information), the notification unit 46 notifies the corresponding contract user of information regarding the rewriting. This enhances the convenience of contract users while appropriately communicating the contents of the automatic update process to them. In addition, compared to notifying all contract users of specific changes to the benefits that can be provided in the subscription service, this enables more efficient notification and efficiently reduces the processing load on the server device 10. It is expected that the number of contract users who do not wish to have their selection information rewritten due to such changes will be small, but according to this embodiment, such contract users can change their selection information after receiving such notification, thus minimizing the negative effects caused by the automatic update process (rewriting of selection information).

[0136] Furthermore, according to this embodiment, since a billing unit 48 is provided, it is possible to provide both a billing service and a subscription service. In this case, by making the predetermined benefits that can be provided by the billing service and the benefits that can be provided by the subscription service at least partially different, they can be appropriately differentiated. Also, in this case, by setting the benefits that can be provided by the subscription service to be more advantageous than the predetermined benefits that can be provided by the billing service, it is possible to provide an effective incentive for users other than contract users to enter into a subscription contract.

[0137] Furthermore, according to this embodiment, the notification unit 54 notifies the user of one or more combinations of various benefits that can be offered in the subscription service, provided that the total points of the selected benefits do not exceed a predetermined number of points. This makes it easier for contract users to select benefits within the range where the total points of the selected benefits do not exceed a predetermined number of points, even when the benefits that can be offered in the subscription service become more diverse, thereby improving the convenience for contract users.

[0138] Furthermore, according to this embodiment, since a candidate selection unit 52 is provided, the notification unit 54 can notify each user of various combinations of benefits that correspond to the user's preferences, the user's game progress, the user's operation tendencies, etc. As a result, even if the benefits that can be offered in the subscription service become diverse, it becomes easier for contract users to select their desired benefits, thereby improving the convenience of contract users.

[0139] Next, referring to Figure 15 and subsequent figures, we will explain various operational examples when multiple benefits that can be offered in a subscription service are set for each of multiple digital content items.

[0140] Figure 15 is an explanatory diagram illustrating the premise of one example of operation, and is a table showing an example of the relationship between multiple digital content items, the benefits set for each digital content item, and the server computer that manages each digital content item.

[0141] In Figure 15, the digital content "Game App GA" has 51 bonuses set, A0 to A50, and is managed by the server computer SA. Similarly, the digital content "Game App GB" has 41 bonuses set, B0 to B40, and is managed by the server computer SA. Similarly, the collection of six digital content items, "E-books DD0 to DD5," has 6 bonuses set, C0 to C5, and is managed by the server computer SC. In the same manner, other digital content may also have one or more bonuses set. Note that the digital content with one or more bonuses set may be part of or all of the various applications provided by the server device 10.

[0142] Figure 16 is an explanatory diagram of this operation example, illustrating the general flow of operations from the point where a new user U10 who desires a subscription service enters into a subscription contract and becomes able to use the desired benefits, under the assumptions shown in Figure 15. The various server computers shown in Figure 16 (management server computer, server computer SC, and server computer SA) constitute the server device 10 shown in Figure 1. Note that in Figure 16 (and the other flowcharts described below as well), the processing order of each step may be changed as long as the relationship between the input and output of each step is not impaired.

[0143] In step S1500, user U10 transmits the type of subscription contract from terminal device 20 to management server computer when entering into a subscription contract.

[0144] In step S1502, the management server computer associates a predetermined number of points corresponding to the type of subscription contract received with the user ID of user U10. This process can be implemented by the point awarding unit 36 ​​described above.

[0145] In step S1504, the management server computer notifies the terminal device 20 associated with user U10 of the combinations of benefits available at the associated predetermined points. At this time, the management server computer may be equipped with the candidate selection unit 52 and notification unit 54 described above, in which case user U10 is notified of the combination selected based on the preference information among the user information related to user U10.

[0146] In step S1506, user U10 displays a notification from the management server computer (a combination of benefits available with a predetermined number of points) on the display unit 23 of the terminal device 20. In this case, the terminal device 20 may output a selection screen as shown in Figures 12 to 14A.

[0147] In step S1508, user U10 performs a selection operation on terminal device 20 and transmits the selection information from terminal device 20 to the management server computer. Here, it is assumed that the selection information for benefits A0, B0, and C0 is transmitted to the management server computer.

[0148] In step S1509, the management server computer determines, based on the received selection information, whether the total points of the selected rewards are less than or equal to a predetermined number of points. This process (determination process) can be implemented by the determination unit 38 described above. In Figure 16, the management server computer may determine that the total points of the selected rewards are less than or equal to a predetermined number of points if the received selection information corresponds to the combination of rewards notified in step S1504. If the management server computer determines that the total points of the selected rewards are not less than or equal to a predetermined number of points, it may send a request to the terminal device 20 to redo the selection.

[0149] In step S1510, the management server computer, based on the determination result in step S1509 being positive (i.e., determined that the total points of the selected benefits are less than or equal to a predetermined number of points), sends a benefit release request to the corresponding server computer based on the selection information pertaining to user U10 in the selection information storage unit 34. This process can be implemented by the benefit management unit 40 described above. In Figure 16, the management server computer, based on the selection information that targets benefits A0, benefits B0, and benefits C0, sends a benefit release request to the server computer SA that manages benefits A0 and benefits B0, enabling the use of benefits A0 and benefits B0 based on the user ID pertaining to user U10, and also sends a benefit release request to the server computer SC that manages benefits C0, enabling the use of benefit C0 based on the user ID pertaining to user U10.

[0150] In step S1512, one or more corresponding server computers release (make available) the corresponding benefits in response to the benefit release request. This process can be implemented by the benefit management unit 40 described above. In Figure 16, server computer SA enables the use of benefits A0 and B0 based on the user ID of user U10, and server computer SC enables the use of benefit C0 based on the user ID of user U10.

[0151] In step S1514, user U10 appropriately utilizes benefits A0, B0, and C0 on the terminal device 20.

[0152] Figure 17 is an explanatory diagram illustrating the premise of another operational example, and is a table diagram showing an example of the relationship between a digital content, the benefits set in that digital content, and the server computer that manages the digital content. Unlike the premise shown in Figure 15, in Figure 17, the benefits that can be offered in the subscription service are limited to those related to a specific digital content.

[0153] Figure 18 is an explanatory diagram of another example of operation, illustrating the general flow of operations from when a new user U10 who desires a subscription service enters into a subscription agreement and becomes able to use the desired benefits, under the assumptions shown in Figure 17. In Figure 18, processes that can be substantially the same as those in Figure 16 may be given the same step number and their explanations may be omitted.

[0154] In the example shown in Figure 18, unlike the example shown in Figure 16, in step S1508, selection information for selecting benefits A0 and A1 is sent to the management server computer. In this case, in step S1510, the management server computer sends a benefit release request to the server computer SA that manages benefits A0 and A1, based on the selection information for selecting benefits A0 and A1, enabling the use of benefits A0 and A1 based on the user ID of user U10. This process can be implemented by the benefit management unit 40 described above.

[0155] Figures 16 and 18 illustrate the case where user U10 enters into a new subscription contract, but the same procedure applies when changing the type of subscription contract.

[0156] Figure 19 is an explanatory diagram illustrating the flow of operations from when user U10 changes the benefits related to a subscription contract, under the assumptions shown in Figure 15, until the new desired benefits become available. In Figure 19, processes that can be substantially the same as those in Figure 16 may be given the same step number and their explanations may be omitted.

[0157] In step S1800, user U10 wishes to change the selected benefit (benefit related to the subscription contract) and sends a benefit inquiry from terminal device 20 to the management server computer.

[0158] In step S1802, the management server computer selects (derives) a combination of benefits suitable for user U10 based on the user information relating to user U10. This process can be implemented by the candidate selection unit 52 described above. In this case, in step S1504, the management server computer notifies the terminal device 20 of the combination of benefits selected in step S1802. In a modified example, the management server computer may generate a list of benefits based on the benefit information in the benefit information storage unit 33 and notify the terminal device 20 of the generated list of benefits.

[0159] In this case, if user U10 changes the benefits related to the subscription contract, the new selection information is sent to the management server computer in step S1508, and the management server computer performs the same processing based on the new selection information.

[0160] Note that Figure 19 shows the workflow under the assumptions shown in Figure 15, but the same applies to the workflow under the assumptions shown in Figure 17.

[0161] Figure 20 is a schematic diagram illustrating the flow of operations during renewal when user U10 maintains a subscription contract for a predetermined period ΔT1, under the assumptions shown in Figure 15. Note that in Figure 20, processes that are substantially the same as those in Figure 16 may be given the same step number and their explanations may be omitted.

[0162] In step S2000, the management server computer determines whether or not the update period for user U10 has arrived. In this embodiment, as described above, the update period is at the beginning of the month, so the management server computer determines whether or not it is the beginning of the month. If the update period has arrived, the process proceeds to step S2002.

[0163] In step S2002, the management server computer performs billing processing based on the subscription contract for user U10. This processing can be achieved by the billing processing unit 35 described above.

[0164] In step S2004, the management server computer associates a predetermined number of points corresponding to the type of subscription contract for user U10 (the same as the previous renewal date unless otherwise specified) with the user ID for user U10. This process can be implemented by the point allocation unit 36 ​​described above.

[0165] In step S2006, the management server computer sends a notification to the terminal device 20 relating to user U10 stating that the subscription contract will be maintained for a further predetermined period ΔT1. In this case, the notification may also include information representing the currently selected benefits (i.e., selection information).

[0166] In step S2008, user U10 displays a notification from the management server computer (a notification that the subscription contract will be maintained for a further predetermined period ΔT1) on the display unit 23 of the terminal device 20. In this case, user U10 may, if necessary, change the benefits related to the subscription contract as shown in Figure 19.

[0167] In step S2009, the management server computer determines whether the total points of the selected rewards are less than or equal to a predetermined number of points, based on the selection information related to user U10 in the selection information storage unit 34. This process (determination process) can be implemented by the determination unit 38 described above. In Figure 20, since there is no change in the selection information related to user U10 due to the update, step S2009 may be omitted.

[0168] Although not shown in Figure 20, the management server computer may send a notification to the terminal device 20 associated with user U10 informing it that the renewal period for user U10 is approaching (for example, one week prior). In this case, user U10 can more easily change the benefits related to the subscription contract as shown in Figure 19, in accordance with the timing of this renewal, if necessary.

[0169] Figure 21 is an explanatory diagram that schematically shows the flow of operations when a specific change occurs regarding the benefits that can be offered in a subscription service.

[0170] In step S2100, the management server computer determines whether there have been any specific changes to the benefits that can be offered in the subscription service. The specific changes are as described above. If there have been specific changes, the process proceeds to step S2102.

[0171] In step S2102, the management server computer automatically updates the selection information in the selection information storage unit 34 in response to a specific change. This process (automatic update process) can be implemented by the selection information update unit 44 described above. In Figure 21, it is assumed that user U10 has selected a benefit related to a specific change. In this case, the selection information related to user U10 in the selection information storage unit 34 will be automatically updated.

[0172] In step S2104, the management server computer sends a notification to the terminal device 20 relating to user U10 that the selection information has been automatically updated. In this case, the notification may also include information representing the currently selected benefit (the benefit after the automatic update) (i.e., the selection information).

[0173] In step S2106, user U10 displays a notification from the management server computer (a notification that the selection information has been automatically updated) on the display unit 23 of the terminal device 20. In this case, user U10 may, if necessary, change the benefits related to the subscription contract as shown in Figure 19.

[0174] Although not shown in Figure 21, the management server computer, based on the selection information related to user U10 in the selection information storage unit 34 (selection information after automatic update processing), sends a privilege release request to the corresponding server computer at an appropriate time, enabling use based on the user ID related to user U10.

[0175] Furthermore, although not shown in Figure 21, the management server computer may, after the automatic update process, determine whether the total points of the selected benefits are less than or equal to a predetermined number of points based on the selection information related to user U10 in the selection information storage unit 34 (selection information after the automatic update process). This process (determination process) can be implemented by the determination unit 38 described above. If the number of points corresponding to the benefits before and after the change does not change during the automatic update process, such a determination process may be omitted.

[0176] Although each embodiment has been described in detail above, the invention is not limited to any particular embodiment, and various modifications and changes are possible within the scope described in the claims. Furthermore, it is possible to combine all or more of the components of the embodiments described above.

[0177] For example, in the embodiment described above, at least a portion of the screen displayed on the terminal device 20 (such as a game screen or a selection screen as shown in Figures 12 and 13) may be a web display that is displayed on the terminal device 20 based on data generated by the server device 10, and at least a portion of the screen may be a native display that is displayed by a native application installed on the terminal device 20. [Explanation of symbols]

[0178] 1. Service System 3 Network 10 Server devices 11 Server Communication Unit 12 Server Storage 13 Server Control Unit 20 Terminal devices 21 Terminal Communication Section 22 Terminal storage unit 23 Display section 24 Input section 25 Terminal Control Unit 30 User information storage unit 31 Point Parameter Storage Unit 32 Point Information Storage Unit 33. Bonus Information Storage Unit 34 Selected Information Storage Unit 35 Billing Processing Section 36 Point Award Section 37 Selection Information Acquisition Unit 38 Judgment section 40. Special Offers Management Department 42 Information update department 44. Selected Information Update Section 46 Announcement Department 48 Billing Section 52 Candidate Selection Section 54 Notification Department 210 Selection screen output section 212 Selection Result Generation Unit 214 Selection Information Transmission Unit

Claims

1. A point awarding unit that associates user identification information relating to a contract user who has entered into a recurring purchase agreement with predetermined points corresponding to the type of recurring purchase agreement for each predetermined period related to the recurring purchase agreement, For each of the multiple available benefits, a points information storage unit stores point information representing the number of points associated with the use of that benefit. A selection information acquisition unit that acquires selection information associated with the user identification information, which represents one or more selected benefits from among the plurality of benefits, The system includes a point parameter storage unit that stores parameter information representing point parameters for each type of subscription contract, The point awarding unit is a device that refers to the parameter information in the point parameter storage unit and determines the predetermined points based on the point parameters associated with the type of recurring purchase contract by the contract user.

2. The apparatus according to claim 1, wherein the parameter information is updated in accordance with any change in the type of subscription contract.

3. The apparatus according to claim 2, wherein the change in the type of subscription contract includes the case in which one type is deleted and / or a new type is added.

4. The apparatus according to claim 1, which has a function for performing various processes related to the aforementioned subscription contract, and further comprises a benefit information storage unit for storing benefit information relating to a plurality of available benefits, in a subscription-related function that makes the benefits selected by the contract user available.

5. The apparatus according to claim 4, wherein the aforementioned benefit information is updated in accordance with any changes in the benefits that can be offered in the subscription-related function.

6. The apparatus according to claim 5, wherein the change in the available benefits includes the removal of one benefit and / or the addition of a new benefit.

7. A point awarding step that associates user identification information relating to a contract user who has entered into a recurring purchase agreement with predetermined points corresponding to the type of recurring purchase agreement for each predetermined period related to the recurring purchase agreement, A point information storage step that stores point information representing the number of points associated with the use of each of the multiple available benefits, A selection information acquisition step, which acquires selection information associated with the user identification information, and which represents one or more selected benefits from among the plurality of benefits, The system includes a point parameter storage step that stores parameter information representing point parameters for each type of subscription contract, The point awarding step is a method performed by a computer, which involves referring to the parameter information stored in the point parameter storage step and determining the predetermined points based on the point parameters associated with the type of subscription contract made by the contract user.

8. A point allocation process that associates user identification information relating to a contract user who has entered into a recurring purchase agreement with predetermined points corresponding to the type of recurring purchase agreement, for each predetermined period related to the recurring purchase agreement, For multiple available benefits, a point information storage process stores point information representing the number of points associated with the use of each benefit. A selection information acquisition process that acquires selection information associated with the user identification information, which represents one or more selected benefits from among the multiple benefits; A computer is used to perform a point parameter storage process that stores parameter information representing point parameters for each type of subscription contract. The point granting process is a program that refers to the parameter information stored in the point parameter storage process and determines the predetermined points based on the point parameters associated with the type of recurring purchase contract made by the contract user.

Images