JP7545344B2 - Information processing device, information processing method, and program - Google Patents

Description

The present invention relates to an information processing device that performs processing related to subscriptions.

A known prior art subscription product sales system for selling subscription products is characterized in that it comprises a product information management means for managing product information related to multiple types of subscription products available for sale, a product designation means for designating one of the multiple types of subscription products, and a contract information management means for acquiring product information related to the subscription product designated via the product designation means from the product information management means and managing subscription contract information corresponding to the subscription product in association with this product information (see, for example, Patent Document 1).

JP 2020-67777 A (page 1, Figure 1, etc.)

However, in the past, stores that wanted to offer products, services, etc. through subscriptions had to individually install a system to manage the subscriptions. Installing a separate system resulted in high installation costs and required specialized knowledge to implement subscriptions, making it difficult to introduce subscriptions.

In addition, when a user uses products or services that have been subscribed to at multiple stores, the user must present information indicating that the user has subscribed (e.g., a contract certificate or membership card) at each store, which makes it less convenient to use the subscription.

The present invention has been made to solve the above problems, and aims to provide an information processing device etc. that can easily provide convenient subscriptions.

The information processing device of the present invention is an information processing device that includes a user subscription information storage unit that stores one or more pieces of user subscription information having a first target identifier that is associated with a card identifier that identifies a credit card and that identifies a contract target to be contracted by subscription, an identifier receiving unit that receives a second target identifier that is associated with the card identifier and identifies the contract target, a judgment unit that uses the second target identifier received by the identifier receiving unit, the card identifier associated with the second target identifier, and the user subscription information stored in the user subscription information storage unit to judge whether a user who uses a credit card identified by a card identifier corresponding to the second target identifier can use the contract target identified by the second target identifier by subscription, a judgment result acquisition unit that acquires judgment result information related to the judgment result of the judgment unit, and a judgment result transmission unit that transmits the judgment result information.

This configuration makes it easy to provide a convenient subscription.

In addition, in the information processing device of the present invention, the first target identifier and the second target identifier may be a store identifier that identifies a store.

This configuration makes it easy to manage subscriptions offered at the store.

In addition, the information processing device of the present invention may be configured such that the user subscription information storage unit stores two or more pieces of user subscription information, each of which has a first target identifier of a contract target contracted by subscription at a different store.

This configuration allows subscriptions offered at different stores to be centrally managed using a credit card.

The information processing device of the present invention may further include a usage information storage unit in which usage information relating to the usage of a contract object contracted by subscription is stored in association with a card identifier and a first target identifier, a storage unit that stores usage information associated with the card identifier associated with the second target identifier received by the identifier receiving unit and the first target identifier corresponding to the second target identifier when the determination unit determines that the contract object identified by the second target identifier is available for use, and a usage information transmission unit that transmits the usage information stored in the usage information storage unit.

With this configuration, when a subscription is used, information regarding the use of each target contracted in the subscription can be recorded and transmitted as appropriate.

In addition, in the information processing device of the present invention, the usage information may include one or more of the following information: cost information regarding the cost of the subscription, usage information regarding whether or not the subject of the subscription contract is used, usage count information regarding the number of times the subject of the subscription contract is used, and original amount information regarding the amount to be paid if the subscription is not contracted.

This configuration makes it possible to record the costs associated with a subscription, whether or not it was used, the number of times it was used, the original amount paid, etc.

In addition, the information processing device of the present invention includes a purchase information storage unit in which one or more purchase information having a purchase object identifier that identifies a purchase object and is associated with a card identifier and is information regarding a purchase using a credit card identified by the card identifier is stored, a registered subscription information storage unit in which one or more registered subscription information including a first object identifier that identifies a contract object that can be contracted by subscription is stored, and for each card identifier, a first object identifier is detected from among the first object identifiers held by the registered subscription information, where the user subscription information associated with the card identifier having the first object identifier is not stored in the user subscription information storage unit, The system may further include a user recommendation determination unit that detects purchase information including a purchase target identifier corresponding to the detected first target identifier, which is associated with a card identifier in the purchase information stored in the purchase information storage unit, for each detected first target identifier, to obtain a purchase frequency, and determines whether the obtained purchase frequency satisfies a user high frequency condition indicating a high frequency, and a user recommendation unit that transmits user recommendation information recommending a contract by subscription for the contract target identified by the first target identifier to a user associated with a card identifier corresponding to the first target identifier that the user recommendation determination unit has determined satisfies the user high frequency condition.

With this configuration, new subscriptions can be recommended to users based on information about purchases made using a credit card.

The information processing device of the present invention may further include an application receiving unit that receives subscription application information corresponding to the user recommendation information transmitted by the user recommendation unit, the application information being associated with a card identifier associated with the user to whom the user recommendation information is transmitted and a first target identifier that identifies the contract target recommended by the user recommendation information, and a subscription registration unit that stores the user subscription information having the first target identifier associated with the application information received by the application receiving unit in the user subscription information storage unit by associating the application information with the card identifier associated with the application information.

With this configuration, new subscriptions can be registered for users upon application from the users in response to user recommendation information.

In addition, the information processing device of the present invention includes a purchase information storage unit in which one or more purchase information having a purchase object identifier that is information related to a purchase using a credit card identified by the card identifier and that identifies a purchase object is stored in association with a card identifier, a registered subscription information storage unit in which one or more registered subscription information including a first object identifier that is a first object identifier that identifies a contract object that can be contracted by subscription and that is associated with a store identifier is stored, and a purchase information storage unit in which one or more registered subscription information including a first object identifier that is associated with a store identifier is stored, among the purchase information stored in the purchase information storage unit in association with the card identifier, The system may further include a store recommendation determination unit that uses purchase information that does not have an object identifier to obtain a purchase frequency for each card identifier associated with the purchase information for each purchase information that has a purchase object identifier associated with the same store identifier, and determines whether the purchase frequency for each card identifier obtained for each store identifier satisfies a store high frequency condition indicating that there are many users who purchase frequently, and a store recommendation unit that transmits store recommendation information that recommends providing, by subscription, a purchase object provided at the store to a store identified by a store identifier that the store recommendation determination unit has determined satisfies the high frequency condition.

With this configuration, it is possible to recommend that stores introduce subscriptions based on information about purchases made using credit cards.

In addition, in the information processing device of the present invention, the user subscription information storage unit stores, in association with the user subscription information, constraint information indicating constraints on the use of the contract object indicated by the first object identifier held by the user subscription information, and the judgment unit may further use the constraint information to judge whether the contract object identified by the second object identifier received by the identifier receiving unit can be used by subscription.

With this configuration, the use of the contract object for which the user has already signed up for a subscription can be permitted only if the use of the contract object for which the user has signed up for a subscription satisfies the constraints.

The information processing device of the present invention may also be an information processing device in which the constraint information includes one or more of total amount constraint information related to the total amount of usage when the contract object identified by the second target identifier is used without a subscription contract, number of times constraint information related to the number of times the contract object identified by the second target identifier is used, single amount constraint information related to the amount of usage per time when the contract object identified by the second target identifier is used without a subscription contract, and usage amount constraint information related to the usage amount of the contract object identified by the second target identifier.

With this configuration, if one or more of the constraints of the total usage amount, the number of usages, the usage amount per usage, and the usage amount are met, the usage of the contracted item through an already-contracted subscription can be permitted.

The information processing device of the present invention may further include a target group information storage unit in which one or more target group information is stored, the target group information including one or more user subscription information having a first target identifier that identifies a group consisting of two or more contract targets as a contract target, a group target identifier that identifies a group of two or more contract targets that can be contracted by subscription as a contract target, and two or more constituent target identifiers that respectively identify two or more contract targets that constitute the group of contract targets indicated by the group target identifier, and the determination unit may be an information processing device that determines whether a user using a credit card identified by a card identifier corresponding to the second target identifier can use the contract target corresponding to the second target identifier, using the second target identifier received by the identifier receiving unit and a card identifier associated with the second target identifier, the user subscription information stored in the user subscription information storage unit, and the target group information stored in the target group information storage unit.

With this configuration, the contracted items of multiple subscriptions that make up a group can be used with a single subscription.

The information processing device and the like according to the present invention can easily provide convenient subscriptions.

FIG. 1 is a block diagram of an information processing system according to an embodiment of the present invention; A flowchart illustrating the operation of the information processing device. A flowchart illustrating the operation of the information processing device. A flowchart illustrating the operation of the information processing device. A flowchart illustrating the operation of the information processing device. FIG. 13 is a diagram showing an example of a user subscription information management table of the information processing device. FIG. 13 is a diagram showing an example of a target group information management table of the information processing apparatus; 8A and 8B are diagrams showing an example of a usage information management table of the information processing device. 9A and 9B are diagrams showing an example of a purchase information management table for the information processing device. FIG. 13 is a diagram showing an example of a registered subscription information management table of the information processing device. 11(a) and 11(b) are diagrams showing examples of displays on the store terminal device. FIG. 13 shows an example of a display on the user terminal device. FIG. 13 is a user purchase frequency management table for the information processing device. FIG. 13 is a diagram showing a display example of the user terminal device. FIG. 15( a ) is a diagram showing an example of an acquisition purchase information management table of the information processing device, and FIG. 15( b ) is a diagram showing an example of a purchase target management table. FIG. 13 is a diagram showing an example of a purchase frequency management table for the information processing device. FIG. 13 shows an example of a display on the store terminal device. FIG. 1 shows an example of the external appearance of the computer system. FIG. 1 shows an example of the configuration of the computer system.

Embodiments of an information processing device and the like will be described below with reference to the drawings. Note that components with the same reference numerals in the embodiments perform similar operations, and therefore may not be described again.

(Embodiment)
FIG. 1 is a block diagram of an information processing system according to the present embodiment.

The information processing system 1000 includes an information processing device 1, one or more store terminal devices 2, and one or more user terminal devices 3. The information processing device 1, one or more store terminal devices 2, and one or more user terminal devices 3 are connected via wired or wireless communication lines, etc., so that information can be sent and received. For example, the information processing device 1, one or more store terminal devices 2, and user terminal devices 3 are connected via wireless or wired networks, etc., so that information can be sent and received. Note that in FIG. 1, as an example, a case will be described in which the information processing system 1000 has three or more store terminal devices 2 and three or more user terminal devices 3.

The information processing device 1 includes a user subscription information storage unit 101, a target group information storage unit 102, an identifier receiving unit 103, a judgment unit 104, a judgment result acquisition unit 105, a judgment result transmission unit 106, a usage information storage unit 107, an accumulation unit 108, a usage information transmission unit 109, a purchase information storage unit 110, a registered subscription information storage unit 111, a user recommendation judgment unit 112, a user recommendation unit 113, an application receiving unit 114, a subscription registration unit 115, a store recommendation judgment unit 116, and a store recommendation unit 117.

The information processing device 1 is typically a server device. For example, the information processing device 1 is a cloud server or an ASP server. However, the information processing device 1 is not limited to a server device. The information processing device 1 is realized, for example, by a computer, etc.

The user subscription information storage unit 101 stores one or more pieces of user subscription information in association with a card identifier that identifies a credit card. The user subscription information can be said to be, for example, information about a subscription with which a user has signed up. The user subscription information is information having a first object identifier that identifies the contract object that is signed up for by the subscription. The card identifier is, for example, a credit card number, a credit card security code, or information that identifies a credit card that can be read from the magnetic stripe or IC chip of a credit card.

A subscription is, for example, a method of purchasing or contracting for the right to use a contract object for a fixed period (for example, one month or a year), or a business method of paying a fee for the right to use, and is also called a subscription method. A subscription may be considered to be a method of paying a fee to obtain permission to use or use for a limited period. A subscription may be considered to be a business method in which the usage fee for the contract object is fixed during a fixed period. The usage fee for the subscription may vary for each fixed period (for example, each month). A billing method that provides a service at a fixed price per fixed period (year, month, day, etc.), such as a so-called flat-rate system, may also be considered to be a form of subscription. Contracting a contract object with a subscription may be considered to be a contract to use the contract object with a subscription. The use of the contract object here may be, for example, the use of the contract object or the acquisition of the contract object. The use of the contract object here is, for example, use that does not incur additional costs, etc.

The contract subject here is a product or service. The contract subject may be an intangible or tangible object. Contracting for a product through a subscription means, for example, contracting for the right to use the product for a fixed period of time, or contracting for the right to acquire the product in the amount the user desires within the fixed period of time without incurring additional costs. Contracting for a service through a subscription means, for example, contracting for the right to use the service for a fixed period of time. For example, when a user uses a restaurant through a subscription, the user can order as much food and drink as they want within the fixed period of time, paying only the subscription fee, without additional costs. However, a subscription contract may have predetermined restrictions, such as restrictions indicated by the restriction information described later. The contract subject for a subscription contract may be, for example, a single contract subject, or multiple different contract subjects.

The first object identifier may be, for example, an identifier for identifying the contract object, such as the name of the contract object or a code assigned to the contract object. The first object identifier may also be information other than the above, so long as it is information capable of identifying the contract object. The first object identifier may be a store identifier of a store that provides the contract object, an identifier of a contractable product, or a combination of a store identifier of a store that provides the contract object and an identifier of one or more contractable products. For example, the first object identifier may be a store identifier for identifying a store. This store identifier may be, for example, a store identifier for identifying a store with which a user has contracted for a subscription. For example, in cases where a store can provide only one contract object through a subscription, or where all contract objects provided by a store can be contracted through a single subscription, the store identifier can identify the contract object contracted for through the subscription. The store identifier may be, for example, a store name, a code assigned to a store, a store telephone number, a store email address, or the like.

It is preferable that the first target identifier is associated with information capable of identifying a store that provides the contract target. For example, the first target identifier associated with information capable of identifying a store may be information having a store identifier, or may be a store identifier as described above. Furthermore, information that associates and manages the first target identifier with the store identifier may be stored in a storage unit (not shown) or the like. Furthermore, for example, the first target identifier and the store identifier associated therewith may be included in the same user subscription information. Furthermore, the store identifier may be associated with the user subscription information.

The first object identifier may also be an identifier of a group of contract objects when the group is treated as a single contract object.

It is preferable that the user subscription information storage unit 101 stores, for example, two or more pieces of user subscription information including user subscription information each having a first target identifier of a contract object that can be contracted by subscription at different stores. For example, the user subscription information storage unit 101 may store two or more first target identifiers each having two or more different store identifiers, or may store two or more first target identifiers each having an identifier of a contract object that can identify two or more different stores.

The user subscription information may further include information other than the first target identifier. For example, the user subscription information may include an identifier that identifies the user subscription information, and may include information for managing the subscription, such as the subscription expiration date and whether or not the subscription period needs to be automatically extended.

Storing user subscription information in association with a card identifier may mean that a pair of the card identifier and the user subscription information is stored in the user subscription information storage unit 101, or that the user subscription information is linked and stored with a card identifier stored in a storage unit (not shown) other than the user subscription information storage unit 101, or that the user subscription information is stored in association via a common identifier, or that the user subscription information has a card identifier. However, the association between the card identifier and the user subscription information is not limited to the above manner. The same applies to the constraint information, etc., stored in association with the user subscription information described below.

In the following, in this embodiment, an example in which a pair of a card identifier and user subscription information is stored in the user subscription information storage unit 101 will be mainly described.

The card identifier associated with the user subscription information is preferably the card identifier of the credit card used in the contract by the subscription of the contract target indicated by the first target identifier indicated by the user subscription information, but may be the card identifier of a credit card other than the credit card used in the contract. However, in this case, the credit card is preferably the credit card of the user who made the contract, or the credit card of the family member or guardian of the user who made the contract. The user's credit card is, for example, the credit card with which the user has made the contract, or the credit card in whose name the user is the account holder.

In the user subscription information storage unit 101, for example, a first target identifier of a contract target for which the user has already signed a subscription contract is stored in association with the card identifier of a credit card used by the user. For example, when a user signs a subscription contract for a contract target, the first target identifier associated with the user's card identifier is transmitted to the information processing device 1 from the store terminal device 2 or a device (not shown) that accepts subscription contracts, and the receiving unit (not shown) receives it, and the received first target identifier is associated with the received card identifier and stored in the user subscription information storage unit 101. However, how the user subscription information is stored in the user subscription information storage unit 101 is not limited to the above. In addition, when the valid period of the subscription corresponding to the user subscription information stored in the user subscription information storage unit 101 (for example, the subscription contract period or the available period of the contract target) has ended, for example, the user subscription information is deleted from the user subscription information storage unit 101. The deletion here may be performed by associating information such as a flag indicating that the information has been deleted with the user subscription information. In addition, when the validity period of a subscription is extended by payment of a usage fee, for example, the corresponding user subscription information may not be deleted, and new user subscription information may be stored. However, how the user subscription information is managed is not limited to the above example.

The user subscription information storage unit 101 may store, for example, constraint information in association with the user subscription information, which indicates constraints on the use of the contract object indicated by the first object identifier held by the user subscription information. The constraint information may be considered, for example, as conditions under which the use of the contract object contracted in the subscription is restricted. For example, the constraint information is information used to allow the contract object to be used when the user's use of the contract object contracted in the subscription falls within the constraints indicated by the constraint information, and to prevent the use of the contract object even during the validity period of the subscription when the constraints indicated by the constraint information are exceeded. The constraint information will be described later.

The user subscription information stored in the user subscription information storage unit 101 may include one or more pieces of user subscription information having a first object identifier that identifies a group consisting of two or more contract objects as one contract object.

The user subscription information storage unit 101 is preferably a non-volatile recording medium, but can also be realized as a volatile recording medium. The same applies to the other storage units.

The target group information storage unit 102 stores one or more pieces of target group information. The target group information is information that associates a group target identifier with two or more constituent target identifiers. The group target identifier is an identifier that identifies a group of two or more contract targets that can be contracted by subscription as one contract target. The constituent target identifiers are identifiers that identify each of the two or more contract targets that constitute the group of contract targets indicated by the group target identifier. As the constituent target identifier, information similar to the first target identifier described above can be used. Note that, depending on the convenience of processing, etc., a single contract target may also be treated as one group of contract targets.

The identifier receiving unit 103 receives a second object identifier that identifies the contract object in association with the card identifier. For example, the identifier receiving unit 103 receives the second object identifier that identifies the contract object in association with the card identifier of the credit card of a user who has contracted for the contract object through a subscription. This card identifier is, for example, information used to identify a user who has contracted for the contract object through a subscription. This card identifier may be considered to be information registered as information that identifies a user who has contracted for the contract object through a subscription.

The identifier receiving unit 103 typically receives a card identifier and a second target identifier as the second target identifier associated with the card identifier. For example, the identifier receiving unit 103 receives information having a card identifier and a second target identifier. However, the identifier receiving unit 103 does not have to receive the card identifier associated with this second target identifier along with the second target identifier. The identifier receiving unit 103 may, for example, receive the second target identifier and information other than the card identifier associated with the card identifier. For example, the identifier receiving unit 103 may further receive information on the usage amount of the contract object used by the user and information indicating the usage amount of the contract object used by the user. The usage amount here is, for example, the usage amount incurred when the contract object is used in a case where a subscription contract is not made.

The second target identifier is an identifier that identifies the contract target, and the same information as the first target identifier described above can be used. For example, the second target identifier may be a store identifier. The store identifier here may be, for example, the store identifier of a store where a user using the credit card indicated by the corresponding card identifier has signed a subscription contract, or the store identifier of a store that is attempting to inquire whether a user using the credit card indicated by the corresponding card identifier is a user who has signed a subscription contract.

In this embodiment, for simplicity, an example will be described in which the same identifiers are used as the first object identifier, the second object identifier, and the constituent object identifier that identify the same contract object. However, if information is stored that manages the correspondence between the first object identifier, the second object identifier, and the constituent object identifier that correspond to the same contract object, and if one identifier can be converted to another different identifier that corresponds to this identifier as necessary, different identifiers may be used as the above identifiers that correspond to the same contract object.

The identifier receiving unit 103 is typically implemented using a wireless or wired communication means. The identifier receiving unit 103 may or may not include a communication device.

The determination unit 104 uses the second target identifier received by the identifier receiving unit 103, the card identifier associated with the second target identifier, and the user subscription information stored in the user subscription information storage unit 101 to determine whether a user who uses a credit card identified by a card identifier corresponding to the second target identifier can use the contract target identified by the second target identifier through a subscription. Use through a subscription means, for example, using the contract target through a subscription that has already been contracted. Use of the contract target may be using the contract target, acquiring the contract target, or receiving a service or the like corresponding to the contract target. This subscription is, for example, a subscription associated with the card identifier associated with the second target identifier. For example, the use here is a use that does not incur additional costs or the like. Determining whether use through a subscription of the contract target is possible means determining whether a subscription contract has been made for the contract target. For example, if a subscription contract has been made, use through a subscription of the contract target is possible.

The judgment unit 104 normally judges whether user subscription information corresponding to the second target identifier received by the identifier receiving unit 103 and the card identifier associated with this second target identifier exists in the user subscription information storage unit 101, and if it exists, judges that the contract target corresponding to the second target identifier is available. The user subscription information corresponding to the second target identifier received by the identifier receiving unit 103 and the card identifier associated with this second target identifier is user subscription information having a first target identifier corresponding to the second target identifier received by the identifier receiving unit 103 and a card identifier that matches the card identifier associated with this second target identifier.

The first target identifier corresponding to the second target identifier is a first target identifier that identifies the same contract target as the contract target identified by the second target identifier. For example, as described above, when the same identifier is used as the first target identifier and the second target identifier that correspond to the same contract target, the first target identifier corresponding to the second target identifier is a first target identifier that matches the second target identifier. The same applies to the constituent target identifier corresponding to the second target identifier, and the first target identifier corresponding to the group target identifier, etc.

The judgment unit 104 may further use the restriction information to judge whether the contract object identified by the second target identifier received by the identifier receiving unit 103 can be used by subscription. For example, the judgment unit 104 judges that a user using a credit card identified by a card identifier corresponding to the second target identifier can use the contract object corresponding to the second target identifier by using the second target identifier received by the identifier receiving unit 103, the card identifier associated with the second target identifier, and the user subscription information stored in the user subscription information storage unit 101 as described above, and the use of the contract object identified by the second target identifier received by the identifier receiving unit 103 by a user using a credit card identified by a card identifier corresponding to the second target identifier received by the identifier receiving unit 103 satisfies the restriction indicated by the restriction information associated with the user subscription information corresponding to the second target identifier received by the identifier receiving unit 103 and the card identifier associated with this second target identifier, and judges that the contract object corresponding to the second target identifier can be used by the user using the credit card identified by the card identifier corresponding to the second target identifier received by the identifier receiving unit 103; otherwise, the judgment unit 104 judges that the contract object cannot be used. Here, use through a subscription refers to use of the subject matter of an existing subscription, for example. For example, this use does not incur additional costs, etc.

The constraint information stored in the user subscription information storage unit 101 in association with the user subscription information includes, for example, one or more of total amount constraint information, number of times constraint information, one-time amount constraint information, and usage fee constraint information.

The total amount constraint information is constraint information on the total amount of usage when the contract object identified by the second object identifier is used without a subscription contract. The total amount of usage here is, for example, the total amount of usage within a predetermined period. The predetermined period may be any length of time as long as it is within the subscription usage period or contract period, for example, it may be the entire usage period or contract period, or it may be a period such as one month, one week, or one day. The constraint information on the total amount of usage is, for example, an upper limit (for example, an upper limit amount) of the total amount of usage. The usage amount here is the amount of usage when the contract object contracted by subscription is used without a subscription contract (for example, when used in a purchase format).

The number of times restriction information is restriction information regarding the number of times the contract object identified by the second object identifier can be used. The number of times of use here is, for example, the number of times of use within a predetermined period as described above. The restriction information regarding the number of times of use is, for example, an upper limit value for the number of times of use.

The one-time amount constraint information is constraint information regarding the amount of money that can be spent per time when the contract object identified by the second object identifier is used without entering into a subscription contract. The constraint information regarding the amount of money that can be spent per time is, for example, an upper limit on the amount of money that can be spent per time.

The usage amount constraint information is constraint information regarding the usage amount of the contract object identified by the second object identifier. The usage amount of the contract object may be, for example, the usage time of the contract object, or the quantity of the contract object used. For example, if the contract object of the subscription contract is a video distribution service, the usage amount of the contract object may be the viewing time of the video of the contract object. Also, for example, if the contract object of the subscription contract is a delivery service of bottled drinks, the usage amount of the contract object may be the number of bottles or cases of the drink of the contract object ordered. The usage amount here is, for example, the usage amount within a predetermined period as described above. The constraint information regarding the usage amount is, for example, the upper limit of the number of times of use.

The judgment unit 104, for example, uses usage information associated with a first target identifier corresponding to the second target identifier received by the identifier receiving unit 103, which is stored in the usage information storage unit 107 described below, and a card identifier corresponding to the second target identifier received by the identifier receiving unit 103, to judge whether or not usage by a user who uses a credit card identified by a card identifier corresponding to the second target identifier received by the identifier receiving unit 103, of a contract subject identified by the second target identifier received by the identifier receiving unit 103, satisfies the constraints indicated by the constraint information associated with the user subscription information corresponding to the second target identifier received by the identifier receiving unit 103 and the card identifier associated with this second target identifier.

For example, when the identifier receiving unit 103 receives the amount of the contract object used by the user together with the second target identifier associated with the card identifier, and the constraint information stored in association with the user subscription information corresponding to the second target identifier received by the identifier receiving unit 103 and the card identifier associated with this second target identifier is total amount constraint information, the judgment unit 104 uses the first target identifier corresponding to the second target identifier received by the identifier receiving unit 103, the card identifier associated with the second target identifier received by the identifier receiving unit 103, and the original amount information, which is usage information stored in the usage information storage unit 107 in association with the card identifier. For example, this total amount is the total amount of usage within a period (for example, this month, this week, etc.) determined in advance for the constraint information, and, for example, the total amount is obtained by obtaining usage information associated with a date within a predetermined period using a date associated with the usage information, and obtaining the usage amount within the period in advance using the date, etc. associated with the usage information. Then, the judgment unit 104 judges whether the total amount obtained by adding the amount for using the new contract object received by the identifier receiving unit 103 to the acquired total amount exceeds a threshold value that is a predetermined upper limit value for the total amount constraint information, and if it does not exceed the threshold value, it judges that the constraint indicated by the constraint information is satisfied, and if it exceeds the threshold value, it judges that the constraint indicated by the constraint information is not satisfied.

For example, when the constraint information stored in association with the user subscription information corresponding to the second target identifier received by the identifier receiving unit 103 and the card identifier associated with this second target identifier is count constraint information, the judgment unit 104 acquires the number of uses of the contract target using the usage count information, which is the usage information stored in the usage information storage unit 107 in association with the first target identifier corresponding to the second target identifier received by the identifier receiving unit 103 and the card identifier associated with the second target identifier received by the identifier receiving unit 103. For example, the acquired number of uses is the number of uses within a period (e.g., this month, this week, etc.) that is predetermined for the constraint information. The judgment unit 104 judges whether the number of uses obtained by adding the number of times the contract target is newly used this time to the acquired number of uses exceeds a threshold value that is a predetermined upper limit value for the number of uses constraint information, and if it does not exceed the threshold value, it judges that the constraint indicated by the constraint information is satisfied, and if it exceeds the threshold value, it judges that the constraint indicated by the constraint information is not satisfied.

For example, when the identifier receiving unit 103 receives the usage amount of the contract target used by the user together with the second target identifier associated with the card identifier, and the constraint information stored in association with the user subscription information corresponding to the second target identifier received by the identifier receiving unit 103 and the card identifier associated with this second target identifier is usage amount constraint information, the judgment unit 104 uses the first target identifier corresponding to the second target identifier received by the identifier receiving unit 103 and the card identifier associated with the second target identifier received by the identifier receiving unit 103 and the usage information stored in the usage information storage unit 107 in association with the first target identifier, to obtain the total amount of usage when the contract target indicated by this second target identifier is used without a subscription. For example, this total amount is the total amount of usage within a period (for example, this month, this week, etc.) determined for the constraint information, and for example, the usage information associated with the date within the predetermined period is obtained using the date, etc. associated with the usage information, and the usage amount within the period is obtained in advance to obtain the total amount. The judgment unit 104 then judges whether the total amount obtained by adding the newly used amount to the acquired total amount exceeds a threshold value that is a predetermined upper limit for the usage amount constraint information, and if it does not exceed the threshold value, it judges that the constraint indicated by the constraint information is satisfied, and if it exceeds the threshold value, it judges that the constraint indicated by the constraint information is not satisfied.

In addition, for example, when the identifier receiving unit 103 receives the amount of the contract object used by the user together with the second target identifier associated with the card identifier, and the constraint information stored in association with the user subscription information corresponding to the second target identifier received by the identifier receiving unit 103 and the card identifier associated with this second target identifier is one-time amount constraint information, it determines whether the amount of the received contract object exceeds a predetermined threshold value for the one-time amount constraint information, and if it does not exceed the threshold value, it is determined that the constraint indicated by the constraint information is satisfied, and if it exceeds the threshold value, it is determined that the constraint indicated by the constraint information is not satisfied.

Note that the above-described constraint information and the determination process using the constraint information are merely examples, and the constraint information and the determination process using the constraint information are not limited to the above examples. Furthermore, the order in which the determination of the use of the contract target by subscription using the user subscription information and the determination of the use of the contract target by subscription using the constraint information are performed does not matter.

The judgment unit 104 may use the second target identifier received by the identifier receiving unit 103, the card identifier associated with the second target identifier, the user subscription information stored in the user subscription information storage unit 101, and one or more target group information stored in the target group information storage unit 102 to judge whether a user using a credit card identified by a card identifier corresponding to the second target identifier can use the contract target corresponding to the second target identifier.

For example, the judgment unit 104 judges whether a user using a credit card identified by a card identifier corresponding to the second target identifier can use a contract object corresponding to the second target identifier, using the second target identifier received by the identifier receiving unit 103, the card identifier associated with the second target identifier, and the user subscription information stored in the user subscription information storage unit 101, as described above. In addition, the judgment unit 104 judges whether user subscription information corresponding to a group target identifier associated with a configuration target identifier corresponding to the second target identifier received by the identifier receiving unit 103 and a card identifier corresponding to the second target identifier received by the identifier receiving unit 103 exists in the user subscription information storage unit 101, and if it exists, judges that a user using a credit card identified by a card identifier corresponding to the second target identifier can use a contract object corresponding to the second target identifier. For example, the judgment unit 104 detects a group target identifier associated with a constituent target identifier corresponding to the second target identifier received by the identifier receiving unit 103 using the target group information, judges whether user subscription information corresponding to the card identifier associated with the second target identifier received by the identifier receiving unit 103 and the group target identifier detected using the target group information exists in the user subscription information storage unit 101, and if it exists, judges that the contract target corresponding to the second target identifier is available. The user subscription information corresponding to the group target identifier and the card identifier corresponding to the second target identifier received by the identifier receiving unit 103 is, for example, user subscription information having a first target identifier corresponding to the group target identifier and a card identifier that matches the card identifier received by the identifier receiving unit 103.

In this case, if the contract target is not determined to be available through a determination process that does not use the target group information, a determination process that uses the target group information may be performed, and if the contract target is not determined to be available through a determination process that does not use the target group information may be performed.

In addition, even when the judgment unit 104 uses the target group information to judge whether a user who uses a credit card identified by a card identifier corresponding to the second target identifier can use the contract target corresponding to the second target identifier, as described above, the judgment unit 104 may further use the restriction information in the same manner as described above to make the judgment.

The judgment result acquisition unit 105 acquires judgment result information related to the judgment result of the judgment unit 104. The judgment result information is, for example, information on the judgment result indicating whether or not the contract object identified by the second target identifier received by the identifier receiving unit 103 can be used by a user who uses a credit card identified by a card identifier associated with the received second target identifier. The judgment result information may be information for displaying such a judgment result. For example, the judgment result acquisition unit 105 reads out judgment result information corresponding to the judgment result of the judgment unit 104 from a storage unit (not shown) or the like.

The judgment result transmission unit 106 transmits the judgment result information. For example, the judgment result transmission unit 106 transmits the judgment result information to the store terminal device 2 that transmitted the second target identifier received by the identifier receiving unit 103.

The judgment result transmission unit 106 is usually realized by a wireless or wired communication means, but may also be realized by a broadcasting means. The judgment result transmission unit 106 may or may not be considered to include a communication device. The same applies to the other transmission units.

The usage information storage unit 107 stores usage information related to the use of the contract object contracted by subscription in association with the card identifier and the first object identifier. The use of the contract object contracted by subscription means using or acquiring a product through a contracted subscription, receiving a service through a contracted subscription, etc. The usage information includes, for example, one or more of the following information: cost information related to the cost of the subscription, use presence/absence information related to the use of the contract object contracted by subscription, number of uses information related to the number of times the contract object contracted by subscription is used, and original amount information related to the amount to be paid if the subscription is not made. The cost information is, for example, the cost of the subscription paid by the user. The cost information may include, for example, information on the date on which the cost was paid. The use presence/absence information may be, for example, information on the date on which the use was made. The number of uses information may include information on the number of uses. For example, the number of uses information may include information on the number of uses within one or more predetermined periods, such as monthly or weekly. The original amount information is, for example, the amount to be paid if the contract object is not contracted by subscription. However, the usage information is not limited to the above information. For example, information regarding the usage of a contract target contracted by subscription, which is transmitted in association with a card identifier and a first target identifier, may be associated with the date of receipt, the card identifier, the first target identifier, etc., and stored as usage information in the usage information storage unit 107.

The usage information may be stored in association with the second target identifier instead of the first target identifier. In this case, the usage information may also be considered to be associated with the first target identifier, since the first target identifier can be obtained by converting the second target identifier.

When the judgment unit 104 judges that the contract target corresponding to the second target identifier received by the identifier receiving unit 103 is available, the accumulation unit 108 accumulates the usage information associated with the card identifier associated with the second target identifier received by the identifier receiving unit 103 and the first target identifier corresponding to this second target identifier. The accumulated usage information may be information having the amount of the contract target received by the identifier receiving unit 103, information on the usage amount of the contract target, etc. For example, the accumulation unit 108 accumulates the usage information stored in the usage information storage unit 107, which is associated with the card identifier associated with the second target identifier received by the identifier receiving unit 103 and the first target identifier corresponding to this second target identifier. The accumulation here may be, for example, an addition of the usage information, or a change in the value of the usage information (for example, an addition of the value of the usage count information, which is the usage information). The change here may be considered to include, for example, an update. In addition, if the usage information storage unit 107 does not store the card identifier associated with the second target identifier received by the identifier receiving unit 103 and the usage information associated with the first target identifier corresponding to this second target identifier, the storage here may be a process of newly storing the usage information associated with the card identifier associated with the second target identifier received by the identifier receiving unit 103 and the first target identifier corresponding to this second target identifier in the usage information storage unit 107. Note that, when the determination unit 104 determines that the contract target corresponding to the second target identifier received by the identifier receiving unit 103 is available for use, the storage unit 108 may add the usage information associated with the card identifier associated with the second target identifier received by the identifier receiving unit 103 and the first target identifier corresponding to this second target identifier to the usage information storage unit 107 in association with the date of receipt, etc.

The usage information transmission unit 109 transmits the usage information stored in the usage information storage unit 107. For example, the usage information transmission unit 109 transmits the usage information associated with the card identifier to a user terminal device 3 or the like used by the user of the credit card identified by the card identifier. For example, the usage information transmission unit 109 transmits usage information within a predetermined period.

The timing or trigger for the usage information transmission unit 109 to transmit the usage information is not important. For example, the usage information transmission unit 109 may transmit the usage information at predetermined intervals (for example, the first day of every month or every Monday), or may transmit the usage information on a predetermined date. In addition, when information requesting usage information associated with a card identifier or the like is received from a user terminal device or the like, the usage information may be transmitted to the user terminal device corresponding to this card identifier.

The usage information transmission unit 109 may perform a predetermined processing on the usage information and transmit the processed usage information. This usage information may be, for example, statistical processing, or processing for drawing a graph, etc.

The purchase information storage unit 110 stores one or more pieces of purchase information in association with the card identifier. The purchase information is information about a purchase using a credit card identified by the associated card identifier, and is information having a purchase target identifier that identifies the purchase target. The purchase target here is, for example, the same as the contract target described above. The purchase target is, for example, a product or service that can be purchased at a store. The purchase target is, for example, something purchased by a user. The purchase target identifier is, for example, an identifier that can identify the product or service that is the purchase target. The purchase target identifier may be, for example, a store identifier of a store that purchases the product or service that is the purchase target. For example, if multiple different purchase targets provided at a single store are not distinguished and the purchase target is considered to be provided at this single store, the purchase target identifier may be a store identifier that provides the purchase target. The purchase target here may be, for example, a purchase target that can be used by entering into a subscription contract. The purchase target identifier may be, for example, an identifier that identifies a contract target of a subscription contract that makes the purchase target available. The purchase target identifier may be, for example, an identifier that identifies a contract target of a subscription contract that makes the purchase target available. The purchase target identifier may be associated in advance with a first target identifier of a subscription contract that makes the purchase target identified by this purchase target identifier available. For example, information that associates a purchase target identifier with a first target identifier may be stored in a storage unit (not shown).

The purchase information is, for example, information having a purchase object identifier of a purchase object purchased using a credit card identified by an associated card identifier. In the purchase information storage unit 110, for example, one or more purchase information may be stored in association with a card identifier and a store identifier that identifies a store where the purchase object can be purchased. The purchase information being stored in association with a card identifier may mean, for example, that information having the purchase information and the card identifier in association with each other is stored in the purchase information storage unit 110, or that the purchase information has a card identifier. The purchase information being stored in association with a store identifier may mean that information having the purchase information and the store identifier is stored in the purchase information storage unit 110, or that the purchase information has a store identifier, or that the purchase object identifier held by the purchase information has a store identifier. Furthermore, the purchase information being stored in association with a store identifier may mean that the store identifier is stored as the purchase object identifier.

The purchase information may include information other than the purchase identifier. For example, the purchase information may further include information such as the date of credit card use, the name of the store used, and the amount.

For example, the same information as the first object identifier described above can be used as the purchase object identifier. Note that in this embodiment, for simplicity, an example will be described in which the same identifier is used as the first object identifier and the purchase object identifier corresponding to the same purchase object. However, information that manages the correspondence between these is stored, and different identifiers may be used as long as one identifier can be converted into another different identifier corresponding to this identifier as necessary. Note that one first object identifier may be associated with multiple purchase object identifiers that respectively correspond to multiple purchase objects.

The purchase information storage unit 110 stores purchase information that is sent in association with a card identifier from, for example, a payment server device (not shown) that processes credit card payments, a credit card company terminal device, etc. However, the manner in which purchase information, etc. is stored in the purchase information storage unit 110 is not limited to this.

The registered subscription information storage unit 111 stores one or more pieces of registered subscription information. The registered subscription information is information including a first target identifier that identifies a contract target that can be contracted by subscription. It is preferable that the first target identifier held by the registered subscription information stored in the registered subscription information storage unit 111 is associated with a store identifier. For example, it is preferable that the first target identifier held by the registered subscription information stored in the registered subscription information storage unit 111 is associated with a store identifier that identifies a store that can contract for the contract target identified by the first target identifier. For example, the first target identifier may be a store identifier. When the first target identifier held by the registered subscription information is associated with a store identifier, the store identified by this store identifier is, for example, a store that offers one or more contract targets by subscription.

The user recommendation determination unit 112, for each card identifier, determines whether the user subscription information associated with the above card identifier having this first target identifier among the first target identifiers held by the registered subscription information stored in the registered subscription information storage unit 111 is associated with this card identifier for a first target identifier not stored in the user subscription information storage unit 101, and obtains the purchase frequency of the purchase object identified by this first target identifier using purchase information including a purchase object identifier corresponding to this first target identifier, and whether the obtained purchase frequency satisfies a user high frequency condition indicating a high frequency.

For example, the user recommendation determination unit 112 detects, for each card identifier, a first target identifier that has this first target identifier from among the first target identifiers held by the registered subscription information stored in the registered subscription information storage unit 111 and whose user subscription information associated with this card identifier is not stored in the user subscription information storage unit 101. Then, for each first target identifier detected for each card identifier, it detects purchase information that includes a purchase target identifier corresponding to each first target identifier and is associated with this card identifier in the purchase information stored in the purchase information storage unit 110, and obtains the purchase frequency of the purchase target indicated by the first target identifier using the purchase information detected for each first target identifier. Then, it is determined whether the obtained purchase frequency satisfies a high frequency condition.

The purchase frequency of a purchase target is, for example, the number of purchases of the purchase target, the number of purchases within a predetermined period (for example, the most recent month, last month, this week, etc.), or the average number of purchases within a period of multiple predetermined lengths. The purchase frequency of a purchase target is, for example, the minimum number of purchases within a period of multiple predetermined lengths. The value of the purchase frequency of the purchase target identified by the first target identifier is, for example, acquired by the user recommendation determination unit 112 using purchase information having a purchase target identifier corresponding to the first target identifier detected as described above. The user high frequency condition is, for example, a lower limit value for the purchase frequency of the purchase target by a user who uses a credit card identified by the card identifier. The lower limit value is, for example, a threshold value indicating the lower limit. For example, when the user high frequency condition is the number of purchases of the purchase target, the user recommendation determination unit 112 determines that the user high frequency condition is satisfied when the number of purchases is equal to or greater than the lower limit value, which is the user high frequency information. To satisfy the user high frequency condition means, for example, determining that the purchase frequency is high. When determining whether a purchase frequency is high using a lower limit value, it may be determined that the user high frequency condition is met when the purchase frequency value matches the lower limit value, or that the user high frequency condition is not met. The user high frequency information may be set for each purchase object, or may be set regardless of the purchase object.

The purchase object identifier corresponding to the first object identifier is, for example, a purchase object identifier that identifies the same object as the contract object identified by the first object identifier. For example, as described above, when the same identifier is used as the first object identifier and the purchase object identifier that correspond to the same object, the purchase object identifier corresponding to the first object identifier is a purchase object identifier that matches the first object identifier. Furthermore, the purchase object identifier corresponding to the first object identifier may be, for example, a purchase object identifier associated with the first object identifier. For example, when one contract object includes multiple purchase objects, the contract object identifier indicating this one contract object may be associated with the purchase object identifiers of the multiple purchase objects included in this one contract object.

The user recommendation unit 113 transmits user recommendation information recommending a subscription contract for the contract target identified by the first target identifier to a user associated with a card identifier corresponding to the first target identifier that the user recommendation determination unit 112 has determined to satisfy the user high frequency condition. The card identifier corresponding to the first target identifier may be, for example, a card identifier associated with purchase information having a purchase target identifier corresponding to the first target identifier. Sending to a user may be considered as sending to a user terminal device 3 used by the user. The user comment information is, for example, information including text, images, etc., recommending a contract for the contract target identified by the first target identifier. It is preferable that the user recommendation information is information having the first target identifier. In addition, it is preferable that the user recommendation information has a button for displaying an input screen for accepting operations, instructions, etc. for signing up for a subscription contract for the contract target recommended for a subscription contract, an input field for accepting input of information necessary for the contract, a button for accepting instructions for the contract, etc.

The application receiving unit 114 receives application information corresponding to the user recommendation information sent by the user recommendation unit 113, and is associated with a card identifier associated with the user to whom the user recommendation information is sent and a first target identifier that identifies the contract target recommended by the user recommendation information. For example, the application receiving unit 114 receives application information having the above card identifier and first target identifier. However, the card identifier, the first target identifier, etc. may be associated with the application information via another identifier, etc., and it does not matter how the card identifier, the first target identifier, etc. are associated with the application information. The application receiving unit 114 receives application information, for example, from a user terminal device (not shown).

The application receiving unit 114 is typically implemented using wireless or wired communication means. The application receiving unit 114 may or may not be considered to include a communication device.

The subscription registration unit 115 associates the user subscription information having the first target identifier associated with the application information received by the application receiving unit 114 with the card identifier associated with the application information, and stores the information in the user subscription information storage unit 101. The subscription registration unit 115 may also store the user subscription information by associating it with the date of accumulation of the user subscription information, etc.

The store recommendation determination unit 116 uses the purchase information that does not have a purchase target identifier corresponding to the first target identifier of the registered subscription information stored in the registered subscription information storage unit 111 among the purchase information stored in the purchase information storage unit 110 in association with the card identifier to obtain the purchase frequency for each card identifier associated with the purchase information for each purchase information having a purchase target identifier associated with the same store identifier, and determines whether the purchase frequency for each card identifier obtained for each store identifier satisfies a store high frequency condition indicating that there are many users who purchase frequently. The purchase information that does not have a purchase target identifier corresponding to the first target identifier of the registered subscription information is, for example, purchase information that already has a purchase target identifier that identifies a purchase target corresponding to a contract target other than a contract target that can be contracted by subscription. The first target identifier here is, for example, preferably an identifier that identifies a contract target associated with a store identifier, and the first target identifier may be a store identifier.

The purchase frequency for each card identifier here can be, for example, the same purchase frequency used by the user recommendation determination unit 112 described above for its determination, and a detailed explanation will be omitted here. The value of this purchase frequency is obtained, for example, by the store recommendation determination unit 116 using the purchase information.

The high store frequency condition is, for example, a condition for detecting a store identifier with many users who purchase frequently. For example, the store recommendation determination unit 116 determines that a store identifier in which a card identifier with a corresponding high purchase frequency is detected more than a predetermined threshold satisfies the high store frequency condition. The determination of whether the purchase frequency corresponding to the card identifier is high can be performed using the same process as the process performed by the above-mentioned user recommendation determination unit 112 when determining whether the purchase frequency is high, and detailed explanations are omitted here. The threshold here is preferably a numerical value of 2 or more. For example, in the case where the purchase frequency acquired for each card identifier is the number of purchases for each store identifier, when the number of card identifiers in which the number of purchases acquired for one store identifier is greater than a predetermined lower limit is detected to be equal to or greater than the threshold, the store recommendation determination unit 116 determines that the high store frequency condition is satisfied for this one store identifier. The high store frequency information may be set for each attribute such as the field of the store, or may be set regardless of the attribute of the store. When the number of card identifiers with a corresponding high purchase frequency matches the above-mentioned predetermined threshold, it may be determined that the store meets the high frequency condition, or that the store does not meet the high frequency condition.

The store recommendation unit 117 transmits store recommendation information that recommends providing a purchase target provided by the store through a subscription to a store identified by a store identifier that the store recommendation determination unit 116 has determined to satisfy the high frequency condition. For example, the store recommendation unit 117 transmits store recommendation information that recommends providing a purchase target that the store recommendation determination unit 116 has determined to satisfy the high frequency condition through a subscription to a store identified by a store identifier that the store recommendation determination unit 116 has determined to satisfy the high frequency condition. Sending to a store may be considered as sending to a store terminal device 2 used by the store. The store comment information is, for example, information including text, images, etc. that recommends the introduction of a subscription to the store. It is preferable that the store recommendation information has a button for displaying an input screen for accepting operations and instructions for introducing the subscription, an explanation screen for introducing the subscription, etc., and an input field for inputting information for requesting an explanation for introducing the subscription.

In addition, when two or more pieces of user subscription information including user subscription information each having a first target identifier of a contract target contracted by subscription at different stores are stored in the user subscription information storage unit 101, the store recommendation determination unit 116 may, for example, in addition to or instead of the determination process described above, determine using a predetermined threshold whether there are many combinations of two or more pieces of user subscription information stored in the user subscription information storage unit 101, each of which has a first target identifier of a contract target contracted by subscription at different stores associated with the same card identifier, and in which the combinations of first target identifiers held by each of the pieces match.

If it is determined that a large number of pieces of user subscription information are stored, the store recommendation unit 117 may, for example, in addition to or instead of transmitting the store recommendation information described above, transmit multiple store recommendation information that recommends to at least one, and preferably both, of the stores that provide the contract targets indicated by the first target identifiers possessed by each of the two or more pieces of user subscription information to provide a new subscription that combines the contract targets of different stores indicated by the first target identifiers possessed by each of the two or more pieces of user subscription information described above. In the above, making a judgment using a predetermined threshold means, for example, determining whether the number of pieces of user subscription information stored is equal to or greater than a predetermined threshold.

For example, the store recommendation determination unit 116 uses the user subscription information stored in the user subscription information storage unit 101 to obtain, for each card identifier, a combination of two or more user subscription information each having a first target identifier of a contract target contracted by subscription at a different store, detects from the obtained combinations a combination of two or more user subscription information having the same combination of first target identifiers associated with different card identifiers, and determines using a threshold whether a large number of card identifiers associated with the detected combinations are stored. For example, the store recommendation determination unit 116 determines whether the number of card identifiers associated with the detected combinations is equal to or greater than the threshold (or more than the threshold).

Then, if the store recommendation determination unit 116 determines that a large number of items are stored, the store recommendation unit 117 transmits multiple store recommendation information that recommends at least one, and preferably both, of the stores that provide the contract targets indicated by the first target identifiers of the two or more pieces of user subscription information detected above to provide a new subscription that combines the contract targets of different stores indicated by the first target identifiers of the two or more pieces of user subscription information detected above.

In this way, for example, if many users have a subscription for yakiniku from store X and a subscription for cakes from store Y, the information processing device 1 can propose a new subscription that combines yakiniku from store X and cakes from store Y to at least one of store X and store Y. Either or both of store X and store Y that receive the proposal may register the new subscription.

The store terminal device 2 is a terminal device used by a store. The store is, for example, a store that offers items for purchase or subscription contracts. The store may be, for example, a store that sells products, or a store that offers services. The store may be, for example, a store that sells electrical appliances or information devices, a sporting goods store, a restaurant, or a barber shop. In addition, the store here is usually a physical store, but may be a non-physical store such as a virtual store that provides mail order services or services such as the distribution of music and video images.

The store terminal device 2 may have, for example, a card information reception unit (not shown) that receives information such as a card identifier of a credit card used by a user, a store side identifier reception unit (not shown) that receives a second target identifier of a contract target with which the user makes a subscription contract, a store side transmission unit (not shown) that transmits information such as a card identifier received by the card information reception unit to the information processing device 1 in association with the second target identifier received by the terminal side identifier reception unit, a store side reception unit (not shown) that receives store recommendation information, and a store side display unit (not shown) that displays the store recommendation information received by the store side reception unit. The card information reception unit may have a card reader (not shown) that reads card information such as a card identifier from a credit card. The card reader may be a contact type that contacts a card to read data, or a contactless type that reads data without contacting the card. The store terminal device 2 may also have an input device used to input information received by the card information reception unit and the store side identifier reception unit. Furthermore, if the second target identifier of the contract subject is stored in advance in a storage unit (not shown), the store side identifier reception unit may read and receive the second target identifier stored in this storage unit.

The store terminal device 2 can be realized by a computer, a tablet terminal, a multi-function mobile phone such as a smartphone, a cash register capable of sending and receiving information, etc.

The user terminal device 3 is a terminal device used by a user. The user is, for example, a user who purchases a purchase object using a credit card. The user is, for example, a user who contracts for a contract object through a subscription using a credit card. The user here may be a natural person or a corporation.

The user terminal device 3 has, for example, a user-side receiving unit (not shown) that receives user recommendation information from the information processing device 1, a user-side display unit that displays the received user recommendation information (for example, by displaying it on a monitor not shown), a user-side input receiving unit that receives input of information for applying for a subscription, and a user-side transmitting unit (not shown) that transmits application information to the information processing device 1 in accordance with the received information.

The user terminal device 3 can be realized by a computer, a tablet terminal, a multi-function mobile phone such as a smartphone, etc.

Next, an example of the operation of the information processing device 1 of the information processing system 1000 will be described with reference to the flowchart in FIG. 2.

(Step S101) The identifier receiving unit 103 determines whether a second target identifier has been received in association with the card identifier. In addition to the second target identifier, the identifier receiving unit 103 may receive other information, such as the usage fee for the contract subject identified by the second target identifier. If the second target identifier has been received in association with the card identifier, the process proceeds to step S102, and if not, the process proceeds to step S107.

(Step S102) The judgment unit 104 judges, using the user subscription information stored in the user subscription information storage unit 101, whether the contract target identified by the second target identifier received in step S101 can be used by a user who uses a credit card identified by a card identifier associated with this second target identifier. Details of this judgment process will be described later.

(Step S103) The judgment result acquisition unit 105 acquires judgment result information regarding the judgment result of step S102.

(Step S104) The judgment result transmission unit 106 transmits the judgment result information acquired in step S103 to the source of the second target identifier received in step S101, such as the store terminal device 2 that transmitted the second target identifier.

(Step S105) The storage unit 108 determines whether the result of the determination in step S102 is that the content is available for use. If the content is available for use, the process proceeds to step S106. If the content is not available, the process returns to step S101.

(Step S106) The accumulation unit 108 accumulates the usage information stored in the usage information storage unit 107 in association with the card identifier received in step S101, using the second target identifier etc. received in step S101, and the usage information stored in association with the first target identifier that corresponds to the second target identifier received in step S101. Then, the process returns to step S101.

(Step S107) The usage information transmitting unit 109 determines whether it is time to transmit the usage information. For example, the usage information transmitting unit 109 determines whether a predetermined date and time for transmitting the usage information has arrived, and if the date and time has arrived, it determines that it is time to transmit, and if the date and time has not arrived, it determines that it is not time to transmit. If it is time to transmit, proceed to step S108, and if it is not time to transmit, proceed to step S110.

(Step S108) The usage information transmission unit 109 acquires the usage information stored in the usage information storage unit 107 for each card identifier associated with the usage information.

(Step S109) The usage information sending unit 109 sends the usage information acquired for each card identifier in step S108 to the user using the credit card identified by the card identifier. For example, it sends the usage information to the user terminal device 3 of the user using the credit card identified by the card identifier that is previously associated with the card identifier. When sending the usage information, the usage information sending unit 109 may process the usage information as appropriate or aggregate the usage information to send the information acquired. Then, the process returns to step S101.

(Step S110) The user recommendation determination unit 112 determines whether it is time to send the user recommendation information. For example, the user recommendation determination unit 112 determines whether a predetermined date and time for sending the user recommendation information has arrived, and if the date and time has arrived, determines that it is time to send, and if the date and time has not arrived, determines that it is not time to send. If it is time to send, proceed to step S111, and if it is not time to send, proceed to step S112.

(Step S111) The user recommendation determination unit 112 and the user recommendation unit 113, etc., acquire and transmit user recommendation information. Details of this process will be described later. Then, the process returns to step S101.

(Step S112) The store recommendation determination unit 116 determines whether it is the timing to send the store recommendation information. For example, the store recommendation determination unit 116 determines whether a predetermined date and time for sending the store recommendation information has arrived, and if the date and time has arrived, determines that it is the timing to send, and if the date and time has not arrived, determines that it is not the timing to send. If it is the timing to send, proceed to step S113, and if it is not the timing to send, proceed to step S114.

(Step S113) The store recommendation determination unit 116 and the store recommendation unit 115, etc., acquire and transmit store recommendation information. Details of this process will be described later. Then, return to step S101.

(Step S114) The application receiving unit 114 determines whether application information has been received from the user terminal device 3. If so, the process proceeds to step S115; if not, the process returns to step S101.

(Step S115) The subscription registration unit 115 associates the user subscription information having the first target identifier associated with the application information received in step S114 with the card identifier associated with this application information, and stores it in the user subscription information storage unit 101. The storage here may be an appending process. Then, the process returns to step S101.

Although not illustrated in the flowchart of FIG. 2, the purchase information received by a receiving unit (not illustrated) of the information processing device 1 may be stored in the purchase information storage unit 110 by a storage unit (not illustrated) of the information processing device 1.

In the flowchart in Figure 2, processing ends when the power is turned off or an interrupt occurs to end processing.

Next, an example of the operation of the information processing device 1 of the information processing system 1000 to determine whether the contract target can be used will be described with reference to the flowchart in FIG. 3. This operation corresponds to the processing of step S102 in FIG. 2.

(Step S201) The judgment unit 104 searches the user subscription information storage unit 101 for user subscription information having a first target identifier corresponding to the second target identifier received in step S101 and associated with the same card identifier as the card identifier associated with this second target identifier.

(Step S202) The judgment unit 104 judges whether user subscription information was detected in step S201. If it was detected, the process proceeds to step S203, and if it was not detected, the process proceeds to step S206.

(Step S203) The judgment unit 104 judges whether the constraints indicated by the constraint information corresponding to the user subscription information detected in step S202 are satisfied. For example, whether the constraints indicated by the constraint information corresponding to the user subscription information detected in step S202 are satisfied is judged using the usage information stored in the usage information storage unit 107 in association with the first target identifier possessed by this user subscription information and the card identifier associated with this user subscription information, and information received by the identifier receiving unit 103 together with the second target identifier associated with the card identifier, etc. If the constraints are satisfied, proceed to step S204, and if the constraints are not satisfied, proceed to step S205. Note that if there is no corresponding constraint information, proceed to step S204.

(Step S204) The judgment unit 104 judges that the contract object identified by the second object identifier received in step S101 can be used by a user who uses a credit card identified by a card identifier associated with this second object identifier. Then, the process returns to the upper level processing.

(Step S205) The judgment unit 104 judges that the contract target identified by the second target identifier received in step S101 cannot be used by a user who uses a credit card identified by a card identifier associated with this second target identifier. Then, the process returns to the upper level.

(Step S206) The judgment unit 104 searches the target group information stored in the target group information storage unit 102 for a constituent target identifier that corresponds to the second target identifier received in step S101.

(Step S207) The judgment unit 104 judges whether the configuration target identifier was detected in step S206. If it was detected, the process proceeds to step S208, and if it was not detected, the process returns to step S205.

(Step S208) The judgment unit 104 acquires a group target identifier corresponding to the configuration target identifier detected in step S206 from the target group information stored in the target group information storage unit 102.

(Step S209) The judgment unit 104 searches the user subscription information storage unit 101 for user subscription information having a first target identifier corresponding to the group target identifier acquired in step S208, and associated with the same card identifier as the card identifier associated with the second target identifier received in step S101.

(Step S210) In step S209, the judgment unit 104 judges whether the user subscription information was detected. If it was detected, the process returns to step S203, and if it was not detected, the process returns to step S205. Note that when returning from step S210 to step S203, in the process of step S203, instead of judging whether the constraints indicated by the constraint information corresponding to the user subscription information detected in step S202 are satisfied, a judgment is made as to whether the constraints indicated by the constraint information corresponding to the user subscription information detected in step S209 are satisfied.

In the flowchart in Figure 3, processing ends when the power is turned off or an interrupt occurs to end processing.

Next, an example of the operation of the information processing device 1 of the information processing system 1000 to acquire and transmit user recommendation information will be described with reference to the flowchart of FIG. 4. This operation corresponds to the processing of step S108 in the flowchart of FIG. 2.

(Step S301) The user recommendation determination unit 112 assigns 1 to the value of counter m.

(Step S302) The user recommendation determination unit 112 determines whether the purchase information stored in the purchase information storage unit 110 contains purchase information associated with the mth card identifier. For example, the user recommendation determination unit 112 may acquire card identifiers from the card identifiers associated with the purchase information stored in the purchase information storage unit 110, without duplication, and determine whether the mth card identifier is present among the acquired card identifiers. Alternatively, the purchase information stored in the purchase information storage unit 110 may be sorted by the associated card identifiers, and whether the mth card identifier is present among the associated card identifiers. If present, the process proceeds to step S303; if not, the process returns to the upper level process.

(Step S303) The user recommendation determination unit 112 assigns 1 to the value of counter n.

(Step S304) The user recommendation determination unit 112 obtains the first target identifier from the nth registered subscription information.

(Step S305) The user recommendation determination unit 112 determines whether user subscription information having the nth first target identifier associated with the mth card identifier is stored in the user subscription information storage unit 101. If it is stored, proceed to step S310, and if it is not stored, proceed to step S306.

(Step S306) The user recommendation determination unit 112 searches for purchase information corresponding to the nth registered subscription information in the purchase information associated with the mth card identifier. Specifically, the user recommendation determination unit 112 searches for purchase information having a purchase target identifier corresponding to the first target identifier possessed by the nth registered subscription information in the purchase information associated with the mth card identifier.

(Step S307) The user recommendation determination unit 112 determines whether one or more pieces of purchase information were detected in step S306. If they were detected, the process proceeds to step S308; if they were not detected, the process proceeds to step S310.

(Step S308) The user recommendation determination unit 112 uses the purchase information detected in step S306 to obtain the purchase frequency of the purchase object identified by the purchase object identifier corresponding to the first object identifier in the nth registered subscription information. When obtaining the purchase frequency, information such as the credit card usage date in the purchase information may be used as appropriate. For example, when obtaining the number of purchases within a predetermined period as the purchase frequency, the purchase frequency may be obtained using purchase information associated with the usage date within the predetermined period.

(Step S309) The user recommendation determination unit 112 associates the purchase frequency acquired in step S308 with the n-th registered subscription information and stores it in a storage unit (not shown). The storage here may be temporary.

(Step S310) The user recommendation determination unit 112 increments the value of counter n by 1.

(Step S311) The user recommendation determination unit 112 determines whether the nth registered subscription information is stored in the registered subscription information storage unit 111. If it is stored, the process returns to step S304; if it is not stored, the process proceeds to step S312.

(Step S312) The user recommendation determination unit 112 detects a purchase frequency that satisfies the user high frequency condition from the purchase frequency stored in step S307 in association with the registered subscription information for the purchase information associated with the mth card identifier. For example, it detects a purchase frequency that is higher than the lower limit indicated by the user high frequency condition.

(Step S313) The user recommendation determination unit 112 determines whether a purchase frequency that satisfies the user high frequency condition has been detected. If so, proceed to step S314; if not, proceed to step S316.

(Step S314) The user recommendation unit 113 acquires user recommendation information for the registered subscription information associated with one or more purchase frequencies determined in step S313 to satisfy the user high frequency condition. Specifically, the user recommendation information is acquired that recommends subscribing to a contract target identified by a first target identifier possessed by the registered subscription information. The user recommendation information is acquired, for example, by using a template stored in a storage unit (not shown).

(Step S315) The user recommendation unit 113 transmits the user recommendation information acquired in step S314 to the user who uses the credit card identified by the mth card identifier. Note that the information stored in step S309 may be deleted.

(Step S316) The user recommendation unit 113 increments the value of counter m by 1 and returns to step S302.

In the flowchart in Figure 4, processing ends when the power is turned off or an interrupt occurs to end processing.

Next, an example of the operation of the information processing device 1 of the information processing system 1000 to acquire and transmit store recommendation information will be described with reference to the flowchart in FIG. 5. This operation corresponds to the processing of step S113 in the flowchart in FIG. 2.

(Step S401) The store recommendation determination unit 116 searches the purchase information stored in the purchase information storage unit 110 for purchase information that does not correspond to any of the one or more registered subscription information stored in the registered subscription information storage unit 111. Purchase information that does not correspond to registered subscription information is purchase information that does not have a purchase target identifier that corresponds to the first target identifier possessed by the registered subscription information. Note that if such purchase information cannot be detected, the process may return to a higher-level process.

(Step S402) The store recommendation determination unit 116 acquires a store identifier corresponding to the detected purchase information without duplication. The store identifier corresponding to the purchase information is, for example, a store identifier associated with the purchase object identifier contained in the purchase information. For example, if the purchase object identifier contained in the purchase information is a store identifier, the store recommendation determination unit 116 acquires the store identifier that is the purchase object identifier contained in the purchase information as the store identifier corresponding to the purchase information.

(Step S403) The store recommendation determination unit 116 assigns 1 to the value of counter p.

(Step S404) The store recommendation determination unit 116 determines whether the pth store identifier is included in the store identifiers acquired in step S402. If so, the process proceeds to step S405; if not, the process returns to the upper level process.

(Step S405) The store recommendation determination unit 116 acquires purchase information corresponding to the p-th store identifier, i.e., purchase information having a purchase target identifier corresponding to the p-th store identifier, from the purchase information detected in step S401.

(Step S406) The store recommendation determination unit 116 sorts the purchase information acquired in step S405 by the card identifier associated with the purchase information.

(Step S407) In order to determine whether the store high frequency information is satisfied, the store recommendation determination unit 116 first obtains a purchase frequency for each card identifier using the purchase information sorted by card identifier in step S405. Note that the store recommendation determination unit 116 may obtain card identifiers from the card identifiers associated with the purchase information stored in the purchase information storage unit 110 without duplication, and obtain a purchase frequency for each obtained card identifier using the purchase information associated with the card identifier.

(Step S408) The store recommendation determination unit 116 further detects card identifiers with high purchase frequencies acquired for each card identifier in step S116 to determine whether the store high frequency information is satisfied. A card identifier with high purchase frequency is, for example, a card identifier whose corresponding purchase frequency is higher than a pre-specified lower limit.

(Step S409) The store recommendation determination unit 116 further determines whether the number of card identifiers with high purchase frequency detected in step S116 is greater than a predetermined threshold in order to determine whether the high store frequency information is satisfied. If it is greater than the threshold, it is determined that the purchase frequency indicated by the purchase information corresponding to the pth store identifier (e.g., purchase information having a purchase target identifier corresponding to the pth store identifier) satisfies the high store frequency condition, and proceeds to step S410, whereas if it is not greater than the threshold, it is determined that the high store frequency condition is not satisfied, and proceeds to step S412.

(Step S410) The store recommendation unit 117 obtains store recommendation information to send to the store indicated by the pth store identifier.

(Step S411) The store recommendation unit 117 sends the store recommendation information obtained in step S410 to the store indicated by the pth store identifier.

(Step S412) The store recommendation unit 117 increments the value of counter p by 1. Then, the process returns to step S404.

In the flowchart in Figure 5, processing ends when the power is turned off or an interrupt occurs to end processing.

The specific operation of the information processing system 1000 in this embodiment will be described below. A conceptual diagram of the information processing system 1000 is shown in FIG. 1. Note that, here, a case will be described in which the first object identifier, second object identifier, purchase object identifier, and configuration object identifier that identify the same object are the same identifier. Also, here, an example will be described in which the first object identifier, second object identifier, purchase object identifier, and configuration object identifier are store identifiers, and the store identifier can identify a contract object that can be contracted by subscription at a store with the store identifier. Also, here, the group object identifier is an identifier of a group made up of multiple stores, for identifying a group of contract objects that can be contracted by subscription at each of the multiple stores.

Figure 6 is a user subscription information management table that manages user subscription information stored in the user subscription information storage unit 101. The user subscription information management table has attributes such as "subscription ID", "card ID", "first target ID", and "constraint". "Subscription ID" is an identifier that manages records (rows) of user subscription information. "Card ID" is a card identifier, which is assumed to be a credit card number here. "First target ID" is a first target identifier, which is assumed to be a store identifier here. The store identifier is assumed to be a code assigned to a store. However, it is assumed that a group target identifier is used instead of a store identifier as part of the first target identifier "first target ID". "Constraint" is constraint information, and here, a name indicating the type of constraint information and a lower limit value of the constraint, etc. are connected via a ":" (semicolon). For example, the name "total amount" indicates total amount constraint information, the name "number of times" indicates number of times constraint information, and the name "amount per time" indicates amount per time information. A blank or Null attribute value for "constraint" indicates that there is no constraint information.

Figure 7 shows a target group information management table that manages target group information stored in the target group information storage unit 102. The target group information management table has attributes called "group target ID" and "composition target ID". "Group target ID" is a group target identifier. "Composition target ID" is a composition target identifier, which is assumed to be a store identifier here as described above. In the target group information management table, the attribute values of "composition target ID" for multiple records that have the same attribute value for "group target ID" are multiple grouped composition target identifiers.

8A is a usage information management table that manages the usage information stored in the usage information storage unit 107. The usage information management table further has attributes of "subscription ID", "cost", "number of times", and "original amount". "Subscription ID" is information corresponding to the "subscription ID" in FIG. 6. "Cost" is cost information indicating the cost of the subscription, which is the amount in this case. "Number of times" is usage count information, which is the number of times the contracted object of the subscription identified by the "first object ID", in this case, the number of times a store that provides the contracted object by subscription is used. "Original amount" is original amount information, which is the total amount when the contracted object is used (e.g., purchased) without using a credit card. Information other than "subscription ID" in the usage information management table corresponds to usage information. Note that here, it is assumed that only information regarding the usage for the current month is accumulated and stored as the value of each attribute, and information from before the current month is deleted as appropriate.

Figure 9 (a) shows a purchase information management table that manages purchase information stored in the purchase information storage unit 110. The purchase information management table has the attributes "card ID", "purchase object ID", "use date", and "use amount". "Card ID" is a card identifier. "Purchase object ID" is a purchase object identifier, which in this case is the store identifier of the store where the purchase of the purchase object was made. "Use date" is the date when the purchase was made using a credit card. Note that in this embodiment, the date may also include information such as time. "Use amount" is the amount purchased using a credit card.

Figure 10 shows a registration subscription information management table that manages the registration subscription information stored in the registration subscription information storage unit 111. The registration subscription information management table has an attribute called "first target ID," which is a first target identifier.

First, assume that user A enters store A, which offers all-you-can-eat food and drink through a subscription, and presents the credit card for which user A is the contract holder to the store clerk in order to apply for the subscription. Assume that the monthly usage fee for this subscription is "10,000 yen." Furthermore, assume that there is a restriction on this all-you-can-eat plan, which limits the total amount of food and drink that can be consumed in the all-you-can-eat plan per month to 20,000 yen. In order to register this credit card as a membership card for the subscription, the store clerk reads the card identifier "12345...01", which is the card number of this credit card, using the card reader of store terminal device 2, and performs an operation on store terminal device 2 to accept the subscription application. In response to this operation, the store terminal device 2 reads out the store identifier "R1590", the restriction information "Total amount: 20,000 yen", and the subscription usage fee "10,000 yen" that are stored in advance in a storage unit (not shown), and transmits them to the information processing device 1 in association with the card identifier "12345...01" read above. In addition, in order for the store clerk to charge the subscription usage fee from the credit card, the store terminal device 2 transmits the information excluding the restriction information in association with the information to a payment server device (not shown) that handles payments using the credit card. The payment server device uses the transmitted information to make a payment to charge the subscription usage fee "10,000 yen" from the credit card.

As shown here, it is preferable to charge the subscription usage fee from the credit card used as the subscription registration certificate, but the usage fee may not be charged from the credit card used as the registration certificate, and may instead be received in cash, for example.

When the application receiving unit 114 of the information processing device 1 receives the above information, the subscription registration unit 115 accumulates the user subscription information having the received store identifier as the first target identifier and associated with the received card identifier in the user subscription information storage unit 101. Here, the subscription registration unit 115 accumulates the user subscription information having the received card identifier.

Figure 6 shows a user subscription information management table to which such user subscription information has been added, and the record (row) in which the "Subscription ID" is "B1007" corresponds to the user subscription information that has just been added. The "Subscription ID" is automatically assigned when the user subscription information is added.

The accumulation unit (not shown) also adds to the usage information storage unit 107 the usage information that has the usage fee of "10,000 yen" as cost information from the received information, in association with "B1007," which is the "subscription ID" assigned to the user subscription information added above.

Figure 7 shows the usage information management table to which this usage information has been added, and the record (row) with "Subscription ID" "B1007" corresponds to the usage information that has just been added. Note that the "Number of times" and "Original amount" of the added record have the initial values of "0" because no consumption or eating has been done under the subscription yet.

Next, assume that user A enters store B, which is different from store A that offers all-you-can-eat food and drink by subscription, and eats and drinks at this store. Assume that user A has already registered to use the subscription for store B. Assume that the cost of eating and drinking here is "4000 yen." At the time of payment, user A presents the credit card that was registered as a membership card when applying for the subscription at this store. When the store clerk has the card reader of the store terminal device 2 read the card identifier "12345...01", which is the card number of this credit card, the store-side transmission unit (not shown) of the store terminal device 2 reads out the store identifier "R1001" stored in the storage unit (not shown), and transmits this store identifier as a second target identifier to the information processing device 1 in association with the card identifier read above and the usage fee. Here, the store-side transmission unit transmits the second target identifier, the card identifier, and the usage fee.

When the identifier receiving unit 103 of the information processing device 1 receives the second target identifier "R1001", the card identifier "12345...01", and the usage fee "4000 yen", the judgment unit 104 judges whether the user using the credit card identified by the card identifier "12345...01" can use the contract target through the contracted subscription.

First, the judgment unit 104 searches the user subscription information storage unit 101 for user subscription information having a first target identifier corresponding to the second target identifier received by the identifier receiving unit 103, and associated with the same card identifier as the card identifier associated with this second target identifier. Specifically, in the user subscription information management table shown in FIG. 6, a record (row) is searched for in which the attribute value of the "first target ID" matches the second target identifier "R1001" received above, and the attribute value of the "card ID" matches the card identifier "12345...01" received above. Here, a record with "subscription ID" of "B1006" is detected, and the judgment unit 104 judges that the user subscription information has been detected. Therefore, the judgment unit 104 reads out the constraint information "total amount: 100,000 yen", which is the attribute value of "constraint" of the detected record. This constraint information is total amount constraint information that restricts the upper limit of the total amount of the usage fee indicated by the usage information to 100,000 yen. The determination unit 104 obtains the attribute value of "original amount", "14,500 yen", from the record in the usage information management table shown in FIG. 8(a) where "Subscription ID" is "B1006". This attribute value is the total original usage fee up to the present time of this month if the subscription is not used. The determination unit 104 determines whether the amount "18,500 yen", obtained by adding the usage fee "4,000 yen" received by the identifier receiving unit 103 and the attribute value "14,500" of the read "original amount" exceeds the total amount constraint information "100,000 yen" obtained above. In this case, since it does not exceed the amount, the determination unit 104 determines that the user using the credit card identified by the card identifier "12345...01" can use the contracted target by the contracted subscription.

Because the judgment unit 104 judges that the service is available, the judgment result acquisition unit 105 acquires judgment result information indicating the judgment result that the service is available. For example, the judgment result information acquired here is information of a character string such as "Available for use by subscription." This information can be acquired, for example, by reading information stored in a storage unit (not shown) in association with the judgment result, according to the judgment result.

The judgment result sending unit 106 sends the judgment result information acquired by the judgment result acquiring unit 105 to the store terminal device 2 of store B that sent the second target identifier etc. received by the identifier receiving unit 103.

When the store-side receiving unit (not shown) of the store terminal device 2 in store B receives the judgment result information, the store-side display unit (not shown) displays the judgment result information.

Figure 11 (a) is a diagram showing an example of the display of judgment result information by the store terminal device 2. The judgment result information is displayed, for example, on the monitor 2a of the store terminal device 2.

Upon seeing this display, the store clerk at Store B determines that User A's usage fee can be paid using the subscription that has already been registered in association with the credit card presented by User A, and does not ask User A to pay the usage fee this time.

The storage unit 108 also updates the usage information by storing (e.g., overwriting) the amount "18,500 yen" obtained by adding the attribute value "14,500" of the "Original Amount" of the record in the usage information management table in which the "Subscription ID" is "B1006" to the usage fee "4,000 yen" received by the identifier receiving unit 103 as the attribute value of "Original Amount" of the record in the usage information management table in which the "Subscription ID" is "B1006". The storage unit 108 also updates the usage information by storing (e.g., overwriting) the attribute value of "Number of Times" of the same record by adding "1" to the original value. The usage information management table updated in this way becomes as shown in FIG. 8(b).

If the total of the total usage fee up to this month, which is the attribute value of "original amount" obtained from the record with "Subscription ID" "B1006" in the usage information management table shown in FIG. 8(a), and the current usage fee received above exceeds the total amount constraint information of "100,000 yen", the constraint information is not satisfied, so the judgment unit 104 judges that the contracted target cannot be used with the already-contracted subscription, and the judgment result acquisition unit 105 acquires judgment result information such as "Use with a subscription is not possible", and the judgment result transmission unit 106 transmits this judgment result information to the store terminal device 2 of store B.

The monitor 2a of the store terminal device 2 that receives this judgment result information displays the judgment result information as shown in FIG. 11(b).

Suppose user B enters store C, which offers all-you-can-eat food and drink through a subscription, and eats and drinks at this store. Store C is part of a group with multiple other stores that offers all-you-can-eat food and drink through a subscription, and any user who uses a subscription to this group can eat as much food and drink as they want at any store in the group. However, the total number of times that stores in the group can be used is limited to 10 times. User B has already registered to use the subscription for this group. Suppose the cost of user B's meal at store C was 3,000 yen. Then, at the time of payment, user B presents the credit card that was registered as a membership card when applying for the subscription at this store. When the store clerk has the card reader of the store terminal device 2 read the card identifier "14558...26", which is the card number of this credit card, the store side transmission unit (not shown) of the store terminal device 2 reads out the store identifier "R1307" stored in the storage unit (not shown), and transmits this store identifier as the second target identifier to the information processing device 1 in association with the card identifier read above and the usage fee.

When the identifier receiving unit 103 of the information processing device 1 receives the second target identifier "R1307", the card identifier "14558...26", and the usage fee "3000 yen", the judgment unit 104 judges whether the user using the credit card identified by the card identifier "14558...26" can use the contract target through the contracted subscription.

First, the judgment unit 104 searches the user subscription information management table shown in FIG. 6 for a record (row) in which the attribute value of the "first target ID" matches the second target identifier "R1307" received above, and the attribute value of the "card ID" matches the card identifier "14558...26" received above. Here, it is assumed that no corresponding record was found.

Therefore, the judgment unit 104 searches the target group information management table shown in FIG. 7 for a record whose attribute value of "configuration target ID" matches the second target identifier "R1307" received above, and obtains the attribute value "G1002" of the "group target ID" of the detected record.

Then, in the user subscription information management table shown in FIG. 6, a record (row) is searched for in which the attribute value of the "first target ID" matches the attribute value "G1002" of the "group target ID" acquired above, and the attribute value of the "card ID" matches the card identifier "14558...26" received above. Here, a record with a "subscription ID" of "B1003" is detected, and the judgment unit 104 judges that user subscription information has been detected. Therefore, the judgment unit 104 reads out the constraint information "number of times: 10 times", which is the attribute value of the "constraint" of the detected record. This constraint information is total amount constraint information that restricts the upper limit of the total number of times indicated by the usage information to "10 times". The judgment unit 104 acquires the attribute value of "number of times", "5 times", from the record with the "subscription ID" of "B1003" in the usage information management table shown in FIG. 8 (a). This attribute value indicates the number of times the target has been used by subscription up to the present time this month. The judgment unit 104 judges whether the number of uses "6 times", which is the sum of the current number of uses "1 time" and the attribute value "5 times" of this "number of times", exceeds the total number of uses "10 times" acquired above. Here, since it does not exceed the number of uses, the judgment unit 104 judges that the user who uses the credit card identified by the card identifier "14558...26" can use the contracted target by the contracted subscription. Thereafter, as in the above, the judgment result acquisition unit 105 acquires the judgment result information, and the store terminal device 2 of the store C displays the judgment result information transmitted by the judgment result transmission unit 106 on a monitor (not shown). Although detailed explanation is omitted here, the accumulation unit 108 updates the value of "number of times" of the record in the usage information management table shown in FIG. 8(b) in which the "subscription ID" is "B1003" by overwriting it with "6", which is a value obtained by incrementing it by "1". The "original amount" and the like are also updated in the same manner.

If, for example, no record is found in the target group information management table whose attribute value of "configuration target ID" matches the second target identifier "R1307" received above, the judgment unit 104 judges that the contract target cannot be used with the already-contracted subscription, and the judgment result acquisition unit 105 acquires judgment result information similar to that described above, such as "Cannot be used with a subscription," and the judgment result transmission unit 106 transmits this judgment result information to the store terminal device 2 of store C, which then displays this judgment result information on a monitor (not shown).

If the current date and time is 1:00 p.m. on the last day of each month (here, October 31st) that is predetermined as the date and time for transmitting usage information, the usage information transmitting unit 109 performs processing to transmit the usage information. Note that whether or not the predetermined date and time has arrived is determined, for example, by using a calendar or the like. The same applies below.

The usage information transmission unit 109 obtains one or more corresponding attribute values of "subscription ID" for each attribute value of "card ID" by obtaining the attribute value of "subscription ID" for each record that matches the attribute value of "card ID" in the user subscription information management table shown in FIG. 6. Then, in the latest usage information management table as shown in FIG. 8 (b), it detects for each attribute value of "card ID" for each record in which the attribute value of "subscription ID" matches the attribute value of "subscription ID" obtained for each attribute value of "card ID" as described above, and transmits usage information in which the attribute values of "cost", "number of times", "original amount" and "number of times" of the record detected for each attribute value of "card ID" are associated with the attribute value of "subscription ID" of the same record and the value of "first target ID" associated by the user subscription management table shown in FIG. 6 to the user terminal device 3 of the user associated with the card identifier, which is the attribute value of "card ID". For example, the usage information transmission unit 109 transmits the usage information by email, short message, etc.

When a user-side receiving unit (not shown) of the user terminal device 3 of a user using a credit card identified by the card identifier receives usage information from the usage information transmitting unit 109, a user-side display unit (not shown) of the user terminal device 3 displays the received usage information.

Figure 12 is a diagram showing an example of usage information displayed on the monitor 3a by the user terminal device 3. This user terminal device 3 is assumed to be the user terminal device 3 of a user who uses a credit card identified by the card identifier "12345...01".

In addition, destination information such as the email address and account of the user terminal device 3 can be obtained by searching using the card identifier from destination information that is stored in advance in a storage unit (not shown) in association with the card identifier of the credit card of the user who uses the user terminal device 3.

The usage information transmission unit 109 may also aggregate the attribute values of "cost," "number of times," "original amount," and "number of times" of records in which the attribute values of the "subscription ID" acquired for each attribute value of the "card ID" match the attribute values of the "subscription ID," for each attribute, and transmit usage information having the attribute values of each attribute aggregated for each attribute value of the "card ID" associated with the attribute name, etc., to the user terminal device 3 of the user associated with the card identifier, which is the attribute value of the "card ID."

If the current date and time is 5:00 PM on October 31st, which is the date and time for transmitting user recommendation information, the information processing device 1 performs a process of acquiring and transmitting the user recommendation information. Note that it is assumed here that the purchase information management table shown in FIG. 9(a) is the latest purchase information management table at the time of performing the process.

First, the user recommendation determination unit 112 acquires records (rows) in the purchase information management table shown in FIG. 9(a) in which the attribute value of "usage date" is a date for the current month, i.e., a date within the range of "2020/10/1" to "2020/10/31". The acquired purchase information is temporarily stored, for example, in a storage unit (not shown). For example, it is assumed that purchase information managed in a purchase information management table such as that shown in FIG. 9(b) is acquired. It is assumed that each attribute of the purchase information management table in FIG. 9(b) is the same as that of the purchase information management table in FIG. 9(a).

Then, in the acquired record, the card identifier, which is the attribute value of "card ID", is acquired by performing unique processing or the like so as to avoid duplication. Then, first, the first card identifier is acquired from the acquired card identifiers so as to avoid duplication. The order of the card identifiers here may be assigned in any way. Let us say that the acquired card identifier was "12345...01".

The user recommendation determination unit 112 obtains the first first target identifier from the registered subscription information management table shown in FIG. 10. Here, it obtains "R1001", which is the attribute value of "First target ID" in the first row of the registered subscription information management table shown in FIG. 10. Then, it searches the user subscription information management table shown in FIG. 6 for a record in which the "Card ID" is "12345...01" and the attribute value of "First target ID" is "R1001". Here, since a record is detected as a result of the search, the purchase frequency is not obtained for this first target identifier.

Next, the second first target identifier is obtained from the registered subscription information management table shown in FIG. 10. Here, "R1002", which is the attribute value of "First target ID" in the second row of the registered subscription information management table shown in FIG. 10, is obtained. Then, in the user subscription information management table shown in FIG. 6, a record in which the "Card ID" is "12345...01" and the attribute value of the "First target ID" is "R1002", i.e., user subscription information, is searched for. Here, it is assumed that no record was searched for. In other words, the user corresponding to the card identifier "12345...01" has not subscribed to the contract target identified by the first target identifier "R1002". For this reason, the user recommendation determination unit 112 searches the purchase information management table shown in FIG. 9(b) for a record, i.e., purchase information, in which the attribute value of the "card ID" matches the first card identifier "12345...01" and the attribute value of the "purchase target ID" matches the second first target identifier "R1002" obtained from the registered subscription information management table. Then, if one or more records are detected, the number of detected records is obtained as the purchase frequency, and the obtained purchase frequency is stored (e.g., temporarily stored) in a storage unit (not shown) in association with the first target identifier "R1002". Moreover, if no record is detected, the purchase frequency is not obtained.

Similarly, the user recommendation determination unit 112 sequentially acquires the third and subsequent first target identifiers from the registered subscription information management table shown in FIG. 10, and each time it acquires one, it searches for a record in the user subscription information management table shown in FIG. 6 in which the attribute value of the "card ID" matches the first card identifier and the attribute value of the "first target ID" matches the third and subsequent first target identifiers acquired from the registered subscription information management table, in the same manner as described above. If the record, i.e., user subscription information, cannot be detected, it searches for a record, i.e., purchase information, in the purchase information management table shown in FIG. 9(b) in which the attribute value of the "card ID" matches the first card identifier and the attribute value of the "purchase target ID" matches the third and subsequent first target identifiers "R1001" acquired from the registered subscription information management table, and only if the record is detected, it performs a process of acquiring the purchase frequency and storing it in association with the first target identifier. For the first target identifier in which user subscription information has been detected or the first target identifier in which one or more purchase information has not been detected, purchase frequency information is not acquired.

The information stored in the storage unit (not shown) at the time the user recommendation determination unit 112 performs the above process for all first target identifiers in the registered subscription information management table shown in FIG. 10, which associates the first target identifiers with purchase frequencies, is assumed to be the information shown in FIG. 13.

Figure 13 shows a user purchase frequency management table that manages the first target identifier and purchase frequency that the user recommendation determination unit 112 has acquired and stored in association with the card identifier "12345...01". The user purchase frequency management table has attributes called "first target ID" indicating the first target identifier and "frequency" indicating the purchase frequency.

The user recommendation determination unit 112 uses the user purchase frequency management table shown in FIG. 13 to acquire a first target identifier that satisfies the user high frequency condition. If the user high frequency condition here is a condition that the purchase frequency per month is "3" or more, the user recommendation determination unit 112 detects a record in the user purchase frequency management table shown in FIG. 13 where the "frequency" value is "3" or more, and acquires the value of the "first target ID" of the detected record as the first target identifier that satisfies the user high frequency condition. Here, the user recommendation determination unit 112 acquires "R1008" as the first target identifier that satisfies the user high frequency condition.

Because the user recommendation determination unit 112 has acquired "R1008" as the first target identifier that satisfies the user high frequency condition for the first card identifier "12345...01", the user recommendation unit 113 acquires (e.g., creates) and outputs user recommendation information recommending a contract by subscription for the contract target identified by the first target identifier "R1008" to the user terminal device 3 of the user who uses the credit card identified by the first card identifier "12345...01". For example, this user recommendation information is created using a template or the like. In addition, this user recommendation information is assumed to be information having a button or the like for applying for a contract by subscription for the contract target identified by the first target identifier "R1008".

Similarly, the user recommendation determination unit 112 performs the same process as described above for the second and subsequent card identifiers among the card identifiers obtained without duplication as described above, obtains the purchase frequency for each first target identifier, determines whether the obtained purchase frequency satisfies the user high frequency condition, and obtains and transmits user recommendation information recommending the purchase by subscription of the purchase target identified by the first target identifier that the user recommendation unit 113 determines to satisfy.

When a user-side receiving unit (not shown) of the user terminal device 3 of user A, who uses the credit card identified by the first card identifier "12345...01", receives recommendation information recommending a subscription to the contract object identified by the first object identifier "R1008" as described above, a user-side display unit (not shown) displays this recommendation information.

Figure 14 shows an example of the display of recommendation information displayed by the user terminal device 3 on the monitor 3a.

When user A presses button 3b for subscription contract with a mouse or the like to make a subscription contract for the purchase target identified by first target identifier "R1008" recommended by the recommendation information, a subscription contract screen (not shown) for the contract target identified by first target identifier "R1008" is displayed using link information or the like associated with button 3b, and when user A inputs card number "12345...01" or the like on this screen and presses a contract button (not shown) or the like, application information having card identifier "12345...01" and first target identifier "R1008" is transmitted to information processing device 1. This application information may have restriction information or the like that is associated in advance with first target identifier "R1008".

When the application receiving unit 114 receives application information from the user terminal device 3, the subscription registration unit 115 adds the user subscription information having the card identifier "12345...01" and the first target identifier "R1008" contained in the application information to the user subscription information management table shown in Figure 6. If the application information has restriction information, the user subscription information having this restriction information is added.

If the current date and time is now 6:00 p.m. on October 30th, which is the date and time that has been predetermined as the date and time for transmitting store recommendation information, the information processing device 1 performs processing for transmitting the store recommendation information.

First, the store recommendation determination unit 116 searches for purchase information stored in the purchase information storage unit 110 that does not have a purchase target identifier corresponding to the first target identifier of one or more registered subscription information stored in the registered subscription information storage unit 111. Specifically, the store recommendation determination unit 116, like the user recommendation determination unit 112 described above, acquires a purchase information management table as shown in FIG. 9(b) and acquires the purchase target identifier "R1221", which is the attribute value of the "purchase target ID", from the first record (for example, the record in the first row from the top) of this purchase information management table. Then, it searches for an attribute value of the "first target ID" in the registered subscription information management table shown in FIG. 10 that matches this purchase target identifier "R1221". If a matching attribute value is detected, the store recommendation determination unit 116 does not acquire the purchase information of this first record. Also, if a matching attribute value is not detected, it acquires the purchase information of this first record and accumulates it in a storage unit (not shown).

The store recommendation determination unit 116 performs the same process for all records in the purchase information management table shown in FIG. 9(b). FIG. 15(a) shows the acquired purchase information management table that manages the purchase information acquired in this manner.

Next, the store recommendation determination unit 116 acquires the store identifier corresponding to each record in the acquired purchase information management table shown in FIG. 15(a). In this case, since the purchase object identifier is a store identifier, the attribute value of the "purchase object ID" is acquired using unique processing or the like so as to avoid duplication.

Figure 15 (b) is a purchase target management table that manages the purchase target identifiers obtained in this manner. In the management table in Figure 15 (b), "Purchase target ID" indicates the purchase target identifier.

Next, the store recommendation determination unit 116 obtains "R1033", which is the first purchase object identifier (for example, the attribute value of "Purchase object ID" of the record in the first row from the top) from the purchase object management table in FIG. 15(b). Then, from the acquired purchase information management table shown in FIG. 15(a), a record in which the attribute value of "Purchase object ID" matches the purchase object identifier "R1033" obtained from the purchase object management table is obtained by searching. Then, the detected records are sorted by the attribute value of "Card ID". Here, for example, it is assumed that only one record in which the attribute value of "Purchase object ID" matches "R1033" is detected. In this case, sorting may be omitted. Then, using the sorted records, the store recommendation determination unit 116 obtains the number of records in which the attribute value of "Card ID" matches for each record in which the attribute value of "Card ID" matches as the purchase frequency value corresponding to the card identifier, which is the attribute value of the matching "Card ID". Here, only one record was found in the acquired purchase information management table where the attribute value of "Purchase target ID" matches "R1033", so "1" is acquired as the purchase frequency corresponding to the attribute value of "Card ID" of this record, "15823...05". The acquired purchase frequency value "1" is then stored in a storage unit (not shown) in association with the card identifier "15823...05".

Then, the store recommendation determination unit 116 determines whether the purchase frequency obtained from the record of the acquisition purchase information management table in which the attribute value of "Purchase target ID" is "R1033" and stored in association with each card identifier satisfies the store high frequency condition. Specifically, the store recommendation determination unit 116 first determines whether the purchase frequency stored in association with each card identifier is greater than a predetermined lower limit. Here, if the predetermined lower limit is "3", the purchase frequency value stored in association with the card identifier "15823...05" is "1", so it is determined that the lower limit is not exceeded. Furthermore, the store recommendation determination unit 116 determines whether the number of card identifiers whose corresponding purchase frequency value exceeds the lower limit exceeds a threshold value. If this threshold value is, for example, "2", here, the number of card identifiers whose corresponding purchase frequency value exceeds the lower limit is "0", so it is determined that the threshold is not exceeded. Therefore, the store recommendation determination unit 116 determines that the purchase frequency for each card identifier acquired for the store identifier corresponding to the purchase object identified by the purchase object identifier "R1033" (i.e., the store identifier "R1033") does not satisfy the high store frequency condition. Therefore, the store recommendation unit 117 does not acquire store recommendation information for this store identifier "R1033".

Next, the store recommendation determination unit 116 obtains "R1221", which is the second purchase object identifier (for example, the attribute value of "purchase object ID" of the record in the second row from the top) from the purchase object management table in FIG. 15(b). Then, from the acquisition purchase information management table shown in FIG. 15(a), a record in which the attribute value of "purchase object ID" matches the purchase object identifier "R1221" obtained from the purchase object management table is obtained by searching. Then, the detected records are sorted by the attribute value of "card ID". Here, for example, it is assumed that multiple records in which the attribute value of "purchase object ID" matches "R1221" are detected. Then, using the sorted records, the store recommendation determination unit 116 obtains the number of records in which the attribute value of "card ID" matches for each record in which the attribute value of "card ID" matches as the purchase frequency value corresponding to the card identifier, which is the attribute value of the matching "card ID". Then, the purchase frequency value obtained for each card identifier is stored in a storage unit (not shown) in association with the card identifier.

Figure 16 is a purchase frequency management table that manages the purchase frequency acquired and accumulated by the store recommendation determination unit 116 for each card identifier. The purchase frequency management table has attributes "card ID" which is the card identifier, and "frequency" which indicates the purchase frequency. It goes without saying that the purchase frequency acquired for the above purchase target identifier "R1033" may also be managed in a purchase information management table similar to that of Figure 16.

Then, the store recommendation determination unit 116 determines whether the purchase frequency obtained from the record in the acquired purchase information management table in which the attribute value of "Purchase target ID" is "R1221" and associated with each card identifier and accumulated satisfies the store high frequency condition. Specifically, the store recommendation determination unit 116 first determines whether the purchase frequency associated with each card identifier and accumulated is greater than a predetermined lower limit. In this case, if the predetermined lower limit is "3", the purchase frequency value stored in association with the card identifier "12345...01", that is, the attribute value of "frequency" of the record (row) in which the "card ID" in Figure 16 is "12345...01" is "7", and therefore it is determined that the lower limit is exceeded. In addition, since the purchase frequency value stored in association with the card identifier "15665...03" and the purchase frequency value stored in association with the card identifier "19582...03" are both "4", it is determined that both exceed the lower limit. In addition, it is determined that the purchase frequency value "2" stored in association with the card identifier "16654...07" does not exceed the lower limit.

Furthermore, the store recommendation determination unit 116 determines whether the number of card identifiers whose corresponding purchase frequency values exceed the lower limit exceeds a threshold. If this threshold is, for example, "2", then in this case, the number of card identifiers whose corresponding purchase frequency values exceed the lower limit is three, card identifiers "12345...01", "15665...03", and "19582...03", and therefore it is determined that the threshold is exceeded. Therefore, the store recommendation determination unit 116 determines that the purchase frequency for each card identifier obtained for the store identifier corresponding to the purchase object identified by the purchase object identifier "R1221" (i.e., store identifier "R1221") satisfies the store high frequency condition.

Since the store recommendation determination unit 116 has determined that the high store frequency condition is satisfied for the purchase target identifier "R1221" which is a store identifier, the store recommendation unit 117 acquires store recommendation information that recommends the store identified by the store identifier "R1221" to provide the purchase target provided by the store through a subscription. For example, the store recommendation unit 117 creates store recommendation information to be sent as a store recommendation. For example, the store recommendation information is created using a template or the like that is stored in advance in a storage unit (not shown). For example, the created store recommendation information is
Assume that the information has a character string such as "Store with store identifier R1221, it seems that you have many repeat customers. Why don't you consider providing services through subscriptions?" Then, the created store recommendation information is transmitted to the store terminal device 2 of the store corresponding to the store identifier "R1221".

Similarly, the store recommendation determination unit 116 performs the same process as above for the third and subsequent purchase object identifiers in the purchase object management table shown in FIG. 15(b) (for example, the attribute values of the "purchase object ID" in the records in the third row and subsequent rows from the top) to determine whether the purchase frequency obtained for each card identifier satisfies the high store frequency condition, and if the high store frequency condition is satisfied, the store recommendation unit 117 transmits store recommendation information to the store terminal device 2 of the store indicated by the store identifier that is the corresponding purchase object identifier.

When a store-side receiving unit (not shown) of the store terminal device 2 of the store identified by the store identifier "R1221" receives the store recommendation information, a store-side display unit (not shown) of the store terminal device 2 displays the received store recommendation information.

Figure 17 shows an example of store recommendation information displayed on the monitor 2a of the store terminal device 2.

As described above, according to this embodiment, it is possible to easily provide a convenient subscription.

In the above embodiment, each process (each function) may be realized by centralized processing in a single device (system), or may be realized by distributed processing in multiple devices.

Furthermore, in the above-described embodiment, it goes without saying that two or more communication means (such as an identifier receiving unit and an application receiving unit, or a judgment result transmitting unit and a usage information transmitting unit) present in one device may be realized physically on one medium.

In the above embodiment, each component may be configured with dedicated hardware, or components that can be realized by software may be realized by executing a program. For example, each component may be realized by a program execution unit such as a CPU reading and executing a software program recorded on a recording medium such as a hard disk or semiconductor memory. During execution, the program execution unit may execute the program while accessing a storage unit (for example, a recording medium such as a hard disk or memory).

The software for realizing the information processing device in the above embodiment is the following program. In other words, this program is a program for making a computer that can access a user subscription information storage unit in which one or more pieces of user subscription information having a first target identifier that is associated with a card identifier that identifies a credit card and that identifies a contract target contracted by subscription be function as an identifier receiving unit that receives a second target identifier that is associated with the card identifier and identifies the contract target, a judgment unit that uses the second target identifier received by the identifier receiving unit, the card identifier associated with the second target identifier, and the user subscription information stored in the user subscription information storage unit to judge whether a user who uses a credit card identified by a card identifier corresponding to the second target identifier can use the contract target identified by the second target identifier by subscription, a judgment result acquiring unit that acquires judgment result information related to the judgment result of the judgment unit, and a judgment result transmitting unit that transmits the judgment result information.

In addition, in the above program, the functions realized by the above program do not include functions that can only be realized by hardware. For example, functions that can only be realized by hardware such as a modem or interface card in an acquisition unit that acquires information or an output unit that outputs information are not included in the functions realized by the above program.

The program may be executed by a single computer or multiple computers. In other words, it may perform centralized processing or distributed processing.

Figure 18 is a schematic diagram showing an example of the appearance of a computer that executes the above program to realize an information processing device according to the above embodiment. The above embodiment can be realized by computer hardware and a computer program executed thereon.

In FIG. 18, the computer system 900 includes a computer 901 including a CD-ROM (Compact Disk Read Only Memory) drive 905, a keyboard 902, a mouse 903, and a monitor 904.

Figure 19 is a diagram showing the internal configuration of a computer system 900. In Figure 19, in addition to a CD-ROM drive 905, the computer 901 includes an MPU (Micro Processing Unit) 911, a ROM 912 for storing programs such as a boot-up program, a RAM (Random Access Memory) 913 connected to the MPU 911 and temporarily storing application program instructions and providing temporary storage space, a hard disk 914 for storing application programs, system programs, and data, and a bus 915 for interconnecting the MPU 911, the ROM 912, etc. Note that the computer 901 may also include a network card (not shown) for providing a connection to a LAN.

A program that causes the computer system 900 to execute the functions of the information processing device according to the above embodiment may be stored on a CD-ROM 921, inserted into the CD-ROM drive 905, and transferred to the hard disk 914. Alternatively, the program may be sent to the computer 901 via a network (not shown) and stored on the hard disk 914. The program is loaded into the RAM 913 when executed. The program may also be loaded directly from the CD-ROM 921 or the network.

The program does not necessarily have to include an operating system (OS) or a third-party program that causes the computer 901 to execute the functions of the information processing device according to the above embodiment. The program may include only an instruction portion that calls appropriate functions (modules) in a controlled manner to obtain the desired results. How the computer system 900 operates is well known, and a detailed description will be omitted.

The present invention is not limited to the above-described embodiment, and various modifications are possible, and it goes without saying that these are also included within the scope of the present invention.

As described above, the information processing device of the present invention is suitable as a device that performs processing related to subscriptions, and is particularly useful as a device that performs processing related to subscriptions using credit cards.

REFERENCE SIGNS LIST 1 Information processing device 2 Store terminal device 3 User terminal device 101 User subscription information storage unit 102 Target group information storage unit 103 Identifier receiving unit 104 Determination unit 105 Determination result acquisition unit 106 Determination result transmission unit 107 Usage information storage unit 108 Accumulation unit 109 Usage information transmission unit 110 Purchase information storage unit 110 Purchase information storage unit 111 Registered subscription information storage unit 112 User recommendation determination unit 113 User recommendation unit 114 Application receiving unit 114 Receiving unit 115 Subscription registration unit 116 Store recommendation determination unit 117 Store recommendation unit 1000 Information processing system

Claims (12)

a user subscription information storage unit in which one or more pieces of user subscription information having a first object identifier that identifies a contract object contracted by subscription are stored in association with a card identifier that identifies a credit card;
an identifier receiving unit for receiving a second object identifier for identifying a contract object in association with the card identifier;
a judgment unit that uses the second target identifier received by the identifier receiving unit, a card identifier associated with the second target identifier, and user subscription information stored in the user subscription information storage unit to judge whether user subscription information having a first target identifier corresponding to the second target identifier received by the identifier receiving unit and a card identifier matching the card identifier associated with the second target identifier exists in the user subscription information storage unit, and judges whether a user using a credit card identified by a card identifier corresponding to the second target identifier is able to use the contract target identified by the second target identifier through a subscription;
a judgment result acquisition unit that acquires judgment result information related to the judgment result of the judgment unit;
a judgment result transmission unit that transmits the judgment result information ;
a purchase information storage unit in which one or more pieces of purchase information are stored in association with a card identifier, the purchase information being information relating to a purchase made using a credit card identified by the card identifier and having a purchase object identifier for identifying a purchase object;
a registration subscription information storage unit in which one or more pieces of registration subscription information including a first object identifier that identifies a contract object that can be contracted by subscription and that is associated with a store identifier are stored;
a store recommendation determination unit that uses purchase information that does not have a purchase target identifier corresponding to a first target identifier of the registered subscription information stored in the registered subscription information storage unit among the purchase information stored in association with a card identifier to obtain a purchase frequency for each card identifier associated with the purchase information for each purchase information having a purchase target identifier associated with the same store identifier, and determines whether the purchase frequency for each card identifier obtained for each store identifier satisfies a store high frequency condition that differs depending on the attributes of the store, which condition indicates that there are many users who purchase frequently;
An information processing device comprising: a store recommendation unit that transmits store recommendation information recommending that a purchase item offered at the store be provided by subscription to a store identified by a store identifier that the store recommendation determination unit has determined to satisfy a high frequency condition . The information processing device according to claim 1, wherein the first target identifier and the second target identifier are store identifiers that identify a store. The information processing device according to claim 1 or 2, wherein the user subscription information storage unit stores two or more pieces of user subscription information, each of which has a first target identifier of a contract target contracted by subscription at a different store. a usage information storage unit in which usage information regarding the usage of a contract object contracted by a subscription is stored in association with the card identifier and the first object identifier;
a storage unit configured to store, when the determination unit determines that the contract object identified by the second object identifier is available for use, a card identifier associated with the second object identifier received by the identifier receiving unit and usage information associated with a first object identifier corresponding to the second object identifier;
The information processing apparatus according to claim 1 , further comprising: a usage information transmitting unit that transmits the usage information stored in the usage information storage unit. The usage information is
5. The information processing device of claim 4, further comprising one or more of the following information: cost information relating to the cost of the subscription; usage information relating to whether or not the subject of the subscription is used; number of usage information relating to the number of times the subject of the subscription is used; and original amount information relating to the amount to be paid if the subscription is not contracted. a purchase information storage unit in which one or more pieces of purchase information are stored in association with a card identifier, the purchase information being information relating to a purchase made using a credit card identified by the card identifier and having a purchase object identifier for identifying a purchase object;
a registration subscription information storage unit in which one or more pieces of registration subscription information including a first object identifier that identifies a contract object that can be contracted by subscription are stored;
a user recommendation determination unit that detects, for each card identifier, a first target identifier that is not stored in the user subscription information storage unit from among first target identifiers contained in the registered subscription information, and detects, for each detected first target identifier, purchase information stored in the purchase information storage unit that is associated with the card identifier and includes a purchase target identifier that corresponds to the detected first target identifier, thereby acquiring a purchase frequency, and determines whether the acquired purchase frequency satisfies a user high frequency condition indicating a high frequency;
The information processing device of any one of claims 1 to 5, further comprising a user recommendation unit that transmits user recommendation information recommending a subscription contract for a contract target identified by a first target identifier to a user associated with a card identifier corresponding to a first target identifier that the user recommendation determination unit has determined to satisfy a user high frequency condition. an application receiving unit that receives application information corresponding to the user recommendation information transmitted by the user recommendation unit, the application information being associated with a card identifier associated with a user to whom the user recommendation information is transmitted and a first target identifier that identifies a contract target recommended by the user recommendation information;
The information processing device of claim 6, further comprising a subscription registration unit that associates user subscription information having a first target identifier associated with the application information received by the application receiving unit with a card identifier associated with the application information and stores it in the user subscription information storage unit. The user subscription information storage unit stores, in association with the user subscription information, constraint information indicating constraints on the use of a contract object indicated by a first object identifier possessed by the user subscription information,
The information processing device according to claim 1 , wherein the determination unit further uses the restriction information to determine whether the contract target identified by the second target identifier received by the identifier receiving unit can be used through a subscription. 9. An information processing device as described in claim 8, wherein the constraint information includes one or more of total constraint information regarding the total amount of usage when the contract object identified by the second target identifier is used without a subscription contract, number of times constraint information regarding the number of times the contract object identified by the second target identifier is used, per-time amount constraint information regarding the amount of usage per time when the contract object identified by the second target identifier is used without a subscription contract, and usage amount constraint information regarding the usage amount of the contract object identified by the second target identifier. The user subscription information stored in the user subscription information storage unit further includes one or more user subscription information having a first object identifier that identifies a group consisting of two or more contract objects as a contract object, and a target group information storage unit in which one or more target group information having a group object identifier that identifies a group of two or more contract objects that can be contracted by subscription as a contract object and two or more constituent object identifiers that respectively identify two or more contract objects that constitute the group of the contract object indicated by the group object identifier is stored in association with each other;
An information processing device as described in any one of claims 1 to 9, wherein the judgment unit uses the second target identifier received by the identifier receiving unit and the card identifier associated with the second target identifier, the user subscription information stored in the user subscription information storage unit, and the target group information stored in the target group information storage unit to determine whether a user using a credit card identified by a card identifier corresponding to the second target identifier can use the contract target corresponding to the second target identifier. an information processing method performed by an information processing device including: a user subscription information storage unit in which one or more pieces of user subscription information having a first object identifier that is associated with a card identifier identifying a credit card and that identifies a contract object to be contracted by subscription is stored; an identifier receiving unit, a determination unit, a determination result acquisition unit, a determination result transmission unit; a purchase information storage unit in which one or more pieces of purchase information are stored in which the purchase information is associated with the card identifier and that is information regarding a purchase using a credit card identified by the card identifier and that has a purchase object identifier that identifies a purchase object; a registered subscription information storage unit in which one or more pieces of registered subscription information including the first object identifier that is associated with a store identifier and that is a first object identifier that identifies a contract object that can be contracted by subscription; a store recommendation determination unit; and a store recommendation unit,
an identifier receiving step in which the identifier receiving unit receives a second object identifier that identifies a contract object in association with the card identifier;
a judgment step in which the judgment unit uses the second target identifier received in the identifier receiving step, a card identifier associated with the second target identifier, and user subscription information stored in the user subscription information storage unit to judge whether user subscription information having a first target identifier corresponding to the second target identifier received in the identifier receiving step and a card identifier matching the card identifier associated with the second target identifier exists in the user subscription information storage unit, and judges whether a user using a credit card identified by a card identifier corresponding to the second target identifier is able to use the contract target identified by the second target identifier through a subscription;
a judgment result acquisition step in which the judgment result acquisition unit acquires judgment result information relating to the judgment result by the judgment step;
a judgment result transmission step in which the judgment result transmission unit transmits the judgment result information ;
a store recommendation determination step in which the store recommendation determination unit obtains a purchase frequency for each card identifier associated with the purchase information for each piece of purchase information having a purchase target identifier associated with the same store identifier, using purchase information that does not have a purchase target identifier corresponding to a first target identifier of the registered subscription information stored in the registered subscription information storage unit, among the purchase information stored in association with a card identifier in the purchase information storage unit, and determines whether the purchase frequency for each card identifier obtained for each store identifier satisfies a store high frequency condition that differs depending on the attributes of the store, which condition indicates that there are many users who purchase frequently;
and a store recommendation step in which the store recommendation unit transmits store recommendation information to a store identified by a store identifier determined in the store recommendation determination step to satisfy a high frequency condition, the store recommendation information recommending that the store provide purchase items by subscription . a user subscription information storage section in which one or more pieces of user subscription information are stored, the user subscription information storage section being associated with a card identifier that identifies a credit card and having a first object identifier that identifies a contract object to be contracted by subscription; a purchase information storage section being associated with the card identifier and storing one or more pieces of purchase information having a purchase object identifier that identifies a purchase object, the purchase object being information relating to a purchase made using a credit card identified by the card identifier; and a registration subscription information storage section being stored, the user subscription information storage section being associated with a store identifier and storing one or more pieces of registration subscription information including a first object identifier that identifies a contract object that can be contracted by subscription, the first object identifier being associated with a store identifier ;
an identifier receiving unit for receiving a second object identifier for identifying a contract object in association with the card identifier;
a judgment unit that uses the second target identifier received by the identifier receiving unit, a card identifier associated with the second target identifier, and user subscription information stored in the user subscription information storage unit to judge whether user subscription information having a first target identifier corresponding to the second target identifier received by the identifier receiving unit and a card identifier matching the card identifier associated with the second target identifier exists in the user subscription information storage unit, and judges whether a user using a credit card identified by a card identifier corresponding to the second target identifier is able to use the contract target identified by the second target identifier through a subscription;
a judgment result acquisition unit that acquires judgment result information related to the judgment result of the judgment unit;
a judgment result transmission unit that transmits the judgment result information ;
a store recommendation determination unit that uses purchase information that does not have a purchase target identifier corresponding to a first target identifier held by the registered subscription information stored in the registered subscription information storage unit among the purchase information stored in association with a card identifier to obtain a purchase frequency for each card identifier associated with the purchase information for each purchase information having a purchase target identifier associated with the same store identifier, and determines whether the purchase frequency for each card identifier obtained for each store identifier satisfies a store high frequency condition that differs depending on the attributes of the store, the condition indicating that there are many users who purchase frequently;
A program for functioning as a store recommendation unit that transmits store recommendation information recommending that a purchase item offered at the store be provided by subscription to a store identified by a store identifier that the store recommendation determination unit has determined satisfies a high frequency condition .

Images