JP2014068912A - Stored game medium management system, stored game medium management device and stored game medium management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To perform management of stored ball service having high convenience to a player without impairing an advantage of a game parlor.SOLUTION: When operation of a stored ball replay is performed in an inter-stand card processor, a stored ball replay request is transmitted to a member management device. Only when satisfying an additional condition of permitting the stored ball replay set in the member management device aside from presence/absence of stored balls by game kinds of a member, the member management device having received the stored ball replay request permits the stored ball replay. By setting a ratio of a stored ball replay upper limit ball number per day to the stored balls or an upper limit ball number of the stored ball replay per day in association with characteristics of the member, a play date (a day), or a stored ball number as the additional condition of permitting the stored ball replay, the stored ball replay can be properly restricted.

Description

  The present invention relates to a storage medium management system, a storage medium management device, and a storage medium management method for managing the number of game media acquired by a player as the number of storage media.

  Conventionally, a game store such as a pachinko store manages various information related to the player in association with identification information for identifying the player and provides various services to the player. For example, Patent Document 1 provides a storage service that manages the number of game media in association with a member ID of a player registered as a member of a game store, and can use the number of game media for game and prize exchange from the next day. A storage management device is disclosed.

  The player can transfer the possessed ball to the accumulated ball by registering the retained ball, which is the number of game media acquired in the game, in the above-described accumulated ball management apparatus. Mochitama can be used for games and prize exchange only within a predetermined time limit (for example, until the closing time of the day), but it can be used beyond the predetermined time limit by shifting to a stored ball.

JP 2011-217846 A

  However, since the profit of the game store is based on the lending of game media to the player, if the replay that uses the stored ball again for the game is allowed without limitation, the profit of the game store may be impaired. On the other hand, if the replay is restricted uniformly, the convenience of the player is lowered, and there is a problem that the operating rate of the gaming machine may be lowered.

  For this reason, it has become an important issue to operate a storage service that is highly convenient for the player without losing the profit of the game store. Such a problem also occurs when a medal, which is a game medium for a slot gaming machine, is managed as a stored medal.

  The present invention has been made to solve the above-described problems of the prior art, and a storage medium management system, a storage medium management apparatus, and a storage medium management capable of effectively operating a storage medium. It aims to provide a method.

  In order to solve the above-described problems and achieve the object, the present invention is a stored game medium management system for managing the number of game media acquired by a player as the number of stored game media. A player information management means for managing at least the number of stored game media in association with identification information, and for a replay in which the player reuses the stored game media number for games again, the restriction condition for the replay is set for the player. And a restriction setting means for setting based on the information regarding.

  Further, the present invention is characterized in that, in the above invention, when the information regarding the player is changed, the restriction setting means changes a restriction condition for the re-game based on the change.

  Further, the present invention is characterized in that, in the above invention, the limit setting means sets an upper limit number of game media with respect to the number of game media that can be used for the replay within a predetermined period.

  Also, the present invention is characterized in that, in the above-mentioned invention, the limit setting means sets an upper limit number of replays with respect to the number of replays that can execute the replay within a predetermined period.

  Further, the present invention is characterized in that, in the above invention, the limit setting means sets the upper limit game medium number or the upper limit regame number based on the number of stored game media.

  Further, the present invention is the above invention, wherein the limit setting means includes the provisional value of the upper limit game medium number or the upper limit regame number obtained based on the number of stored game media, the upper limit game medium number, or the upper limit. The maximum value of the number of replays is compared, and a smaller value between the provisional value and the maximum value is set as the upper limit number of game media or the upper limit number of replays.

  Further, the present invention is the above invention, wherein the player information management means further manages the classification information obtained by classifying the player according to a predetermined standard, and the restriction setting means is configured to manage the classification based on the classification information. The upper limit number of game media or the upper limit number of replays is set.

  Further, the present invention is characterized in that, in the above-mentioned invention, the player information management means associates division information obtained by dividing the player based on a store visit history.

  Also, in the present invention, in the above invention, the limit setting means may be configured such that the number of stored game media or the number of replays used within the predetermined period is less than the maximum number of game media or the maximum number of replays. The number of unused game media or the number of replays that are unused is added to the number of upper limit game media or the upper limit number of replays for the next predetermined period.

  The present invention also provides a storage medium management apparatus that manages the number of game media acquired by a player as the number of storage media, and associates at least the number of storage media with the player identification information for identifying the player. And a restriction setting means for setting a restriction condition for the re-game based on information relating to the player for a re-game in which the player uses the number of stored game media again in the game. It is provided with.

  The present invention is also a storage medium management method for managing the number of game media acquired by a player as the number of stored game media, wherein at least the number of stored game media is associated with player identification information for identifying a player. A player information management step for managing the game, and a restriction setting step for setting a restriction condition for the re-game based on information relating to the player for a re-game in which the player uses the number of game media for the game again. It is characterized by including.

  According to the present invention, at least the number of stored game media is managed in association with the player identification information for identifying the player, and the restriction condition for the replay is set for the replay in which the player uses the stored game media number again in the game. Since it can be set on the basis of information relating to the player, it is possible to operate a storage medium service that is highly convenient for the player without losing profits of the game store.

FIG. 1 is an explanatory diagram for explaining the concept of the stored game medium management method in the stored game medium management system according to the first embodiment. FIG. 2 is a diagram illustrating a system configuration of the gaming system according to the first embodiment. FIG. 3 is a diagram showing an external configuration of the inter-card card processing machine shown in FIG. FIG. 4 is a block diagram showing an internal configuration according to the first embodiment of the inter-card card processing machine shown in FIG. FIG. 5 is a flowchart showing a processing procedure for replaying a stored ball by the inter-card processing machine. FIG. 6 is a block diagram illustrating an internal configuration according to the first embodiment of the member management apparatus illustrated in FIG. FIG. 7 is an explanatory diagram for explaining the member data of the member management apparatus shown in FIG. 6 and the data structure related to the pool replay. FIG. 8 is a flowchart illustrating a processing procedure related to a replay of stored balls by the member management apparatus according to the first embodiment. FIG. 9 is a block diagram illustrating an internal configuration according to the second embodiment of the member management apparatus illustrated in FIG. FIG. 10 is an explanatory diagram for explaining the member data of the member management apparatus shown in FIG. 9 and the data structure related to the pool replay. FIG. 11 is a flowchart illustrating a processing procedure related to a replay of stored balls by the member management apparatus according to the second embodiment. FIG. 12 is a block diagram illustrating an internal configuration according to the third embodiment of the member management apparatus illustrated in FIG. FIG. 13 is an explanatory diagram for explaining the member data of the member management apparatus shown in FIG. 12 and the data structure related to the pool replay. FIG. 14 is a flowchart illustrating a processing procedure related to a replay of stored balls by the member management apparatus according to the third embodiment. FIG. 15 is a block diagram illustrating an internal configuration according to the fourth embodiment of the member management apparatus illustrated in FIG. FIG. 16 is an explanatory diagram for explaining the member data of the member management apparatus shown in FIG. FIG. 17 is a flowchart illustrating a processing procedure related to a replay of stored balls by the member management apparatus according to the fourth embodiment.

  Hereinafter, preferred embodiments of a game storage medium management system, a game storage medium management device, and a game storage medium management method according to the present invention will be described in detail with reference to the accompanying drawings.

  In this specification, “mochitama” refers to data indicating the number of game media acquired by the player in the game or the number of the game media, and may be used again for the game only during that day (time before closing). Say what you can do. The stored ball is data indicating the game media acquired by the player in the game and the number of the game media, and can be used again for the game after the next day (time after closing). Mochidama can be used by both general and member players, and is used when a gaming machine is moved. The stored ball is normally only available to member players, and is used when the acquired game medium is used for games from the next day. A predetermined fee may be imposed on the use of the stored ball.

  First, the concept of the game media management method in the game media management system according to the first embodiment will be described. FIG. 1 is an explanatory diagram for explaining the concept of the stored ball replay management method in the gaming system according to the first embodiment. The gaming system shown in FIG. 1 has a configuration including an inter-card card processor 10 and a member management device 50.

  When the member card is inserted, the inter-card card processor 10 shown in FIG. 1 reads the card ID from the member card and transmits a card insertion notification including the card ID to the member management apparatus 50. The member management device 50 includes the member data 54a in which the PIN number and the number of balls are associated with the card ID, the storage ball replay permission condition data 54b indicating the upper limit of the number of balls that can be replayed, and the number of replays executed on the day. The storage unit 54 stores the number of replayed balls 54c managed for each card ID.

  When the member management device 50 receives the card insertion notification, the member management device 50 performs the storage replay that can be used with the inserted card based on the member data 54a, the storage replay permission condition data 54b, and the storage replay ball count 54c. The number of balls is calculated as the replayable number. This replayable number is a value obtained by subtracting the number of replay balls used on the day from the upper limit number of balls replay on the day determined by the number of balls.

  The member management device 50 notifies the inter-card card processor 10 of the stored ball replay data including the number of stored balls corresponding to the card ID indicated in the insertion notification, the replayable number, and the password. The inter-card processing machine 10 stores stored ball replay data and displays the number of stored balls and the number of replayable players. In the example shown in FIG. 1, the number of stored balls is “15000 balls” and the replayable number is “5000 balls”.

  The inter-card processing machine 10 can accept a stored ball replay operation when the replayable number is equal to or greater than the number of payout units for the stored ball replay (for example, 125). The player can be informed that the replay operation can be accepted by displaying on the touch panel display, lighting the storage ball replay button, or the like.

  When the inter-card processing machine 10 accepts the replay operation of the stored ball, it requests the input of the personal identification number, and on the condition that the input personal identification number matches the personal identification number received from the member management apparatus 50, the member management apparatus A storage ball replay request is transmitted to 50. This storage ball replay request includes a card ID.

  The member management apparatus 50 that has received the reclaimed ball replay request subtracts the number of stored balls associated with the card ID by the number of payout units of the reclaimed ball replay and updates the number of stored balls. In addition, the payout unit number of the stored ball replay is added to the stored ball replayed ball count 54c. Then, the replayable number is recalculated and updated based on the added stored ball replay ball count 54c, and the interbank card processing machine 10 is notified of the stored ball replay data. The stored ball replay data in this case includes the number of stored balls and the number of replayable items, but the password is not required.

  The inter-card processing machine 10 stores the storage ball replay data notified from the member management device 50, updates the display of the number of stored balls and the replayable number, and pays out the pachinko balls of the number of payout units of the storage ball replay. put out. As a result, the number of stored balls is displayed as “14875 balls”, and the replayable number is displayed as “4875 balls”.

  Here, if the replayable number is less than the number of payout units of the stored ball replay, the stored ball replay operation is not accepted. If the replayable number is equal to or greater than the number of payout units of the stored ball replay, the storedball replay can be repeatedly executed until the replayable number becomes less than the stored ball replay. In addition, since the confirmation of the code number is performed at the time of the first replay of the stored ball, it is not necessary for the subsequent replay of the stored ball.

  Thus, in the gaming system according to the first embodiment, the storage ball replay permission condition data 54b indicating the upper limit of the number of replayable balls is managed, and within the range of the storage ball replay upper limit ball number on the day determined by the number of stored balls. It is possible to use the replay of savings.

  Next, the system configuration of the amusement shop shown in FIG. 1 will be described. FIG. 2 is a diagram showing the system configuration of the amusement store. As shown in the figure, in the game store system, a plurality of gaming machines 20 and an inter-card card processing machine 10 provided corresponding to each gaming machine 20 are installed. A card management device 40, a member management device 50, and a prize management device 60 are connected to the communication line 90.

  A plurality of gaming machines 20 are provided with corresponding inter-card card processors 10 respectively. If the inter-card processing machine 10 accepts a bill inserted by the player, it sends the deposit amount to the card management device 40, adds the prepaid value for the deposit amount, and if a predetermined ball lending operation is performed. For example, the prepaid value managed by the card management device 40 is subtracted, and a pachinko ball corresponding to the subtracted prepaid value is paid out to the gaming machine 20.

  Further, when the inter-card card processing machine 10 receives the card, the inter-card card processing machine 10 stores the prepaid value and the number of possessed balls associated with the card. When the inter-card processing machine 10 accepts the ball replay operation, the inter-card processing machine 10 subtracts a predetermined number of balls managed by its own device, and pays out the subtracted number of balls to the gaming machine 20. In addition, when the inter-card processing machine 10 accepts the stored ball replay operation, the predetermined number of stored balls managed by the member management device 50 is subtracted, and the pachinko balls corresponding to the subtracted number of stored balls are given to the gaming machine 20. Pay out. When the inter-card processing machine 10 receives the card return operation, the inter-card processing machine 10 notifies the card management apparatus 40 of the number of possessed balls managed by the own apparatus, and then performs a process of discharging the card.

  The card management device 40 is a management device that manages the prepaid value of a card, the number of balls, etc. as card data. When the card management device 40 receives a deposit notification including the card ID and the deposit amount from the inter-card card processor 10, the card management device 40 adds the prepaid value corresponding to the deposit amount and updates the card data. When the ball lending request including the card ID is received, the prepaid value corresponding to the card ID is subtracted by a predetermined value, and the ball lending permission is transmitted to the inter-card card processing machine 10. Further, when the card management device 40 receives a card insertion notification including a card ID from the inter-card card processor 10, the card management device 40 notifies the inter-card card processor 10 of the prepaid value and the number of possessions associated with the card ID. To do. Here, the number of stored balls is acquired from the member management device 50 and notified to the inter-card processing machine 10.

  Moreover, the card management apparatus 40 subtracts the balance of the possession account when receiving the possession ball subtraction request from the inter-card processing machine 10, and receives the possession ball when receiving the possession registration request. Rewrite the balance of Mochitama account to a number. Further, when the card management device 40 receives a reclaimed ball replay request from the inter-card card processing machine 10, the card management device 40 transmits the reclaimed ball replay request to the member management device 50 and receives a reclaimed ball permission from the member management device 50. If it is, the stored ball replay permission is transmitted to the corresponding inter-card card processing machine 10. Further, when the card management device 40 receives the card ID from the premium management device 60, the card management device 40 notifies the premium management device 60 of the number of possessed balls associated with the card ID.

  The member management device 50 is a management device that manages member data of members registered as members in the amusement store. Specifically, the number of stored balls, points, password, name, etc. are managed in association with the member card ID issued to the member. In addition, when the member management device 50 receives a stored ball replay request via the card management device 40, the member management device 50 performs a process of subtracting a predetermined value from the balance of the corresponding stored ball account and transmitting a stored ball replay permission. In addition, when the member management device 50 receives the card ID of the member card from the gift management device 60, the member management device 50 notifies the gift management device 60 of the balance of the storage account associated with the member card ID.

  The prize management device 60 is a terminal device for exchanging prizes provided in the prize exchange counter in the amusement store, and performs a prize exchange process for storing and holding balls. The premium management device 60 is connected to a reader / writer that reads a card ID from a card and a premium dispensing device that dispenses premiums. When the reader / writer accepts a general card or a membership card, the prize management device 60 transmits the card ID read by the reader / writer to the card management device 40, and requests the number of balls in the card. In addition, when exchanging prizes for the stored balls, the member management device 50 is requested for the number of stored balls.

  Next, the external configuration of the inter-card card processing machine 10 shown in FIG. 2 will be described. FIG. 3 is a diagram showing an external configuration of the inter-card card processing machine 10 shown in FIG. In FIG. 3, the external configuration of the inter-card card processing machine 10 connected to the gaming machine 20 is shown as the inter-card card processing machine 10. In addition, the game machines to be provided are illustrated by broken lines. Moreover, in FIG. 3, although the inter-card processing machine 10 which receives only a banknote was illustrated, the unit for coin reception can also be provided.

  As shown in FIG. 3, the inter-card card processing machine 10 includes a status display unit 11 that displays the status of the apparatus of the inter-card card processing machine 10 by lighting or blinking a predetermined color lamp, and various types of pachinko balls. And a bill insertion slot 12 for accepting bills. Further, the inter-card card processing machine 10 falls from a display operation unit 13 such as a touch panel display, a card insertion slot 14 for receiving a card, a nozzle unit 17 for throwing out a pachinko ball into the gaming machine, and a lower plate of the gaming machine. And a counting unit 18 for counting the pachinko balls made.

  Next, the internal configuration of the inter-card card processing machine 10 shown in FIG. 2 will be described. FIG. 4 is a block diagram showing an internal configuration of the inter-card card processing machine 10 shown in FIG. As shown in FIG. 4, the inter-card card processing machine 10 includes a card reader / writer 10a, a bill transport unit 10b, a display operation unit 13, a card storage unit 16, a communication unit 19, a storage unit 10e, and a control. Part 10f. Further, the inter-card card processing machine 10 is connected to the nozzle unit 17 and the counting unit 18.

  The card reader / writer 10 a is a reading unit that reads a card ID from a card inserted into the card insertion slot 14. The card inserted into the card insertion slot 14 is stored in the card storage unit 16 via the card reader / writer 10a. At the end of the game, the card is transferred from the card storage unit 16 to the card reader / writer 10a, the latest information is written on the card, and the card is inserted into the card insertion slot 14.

  The banknote conveyance part 10b is a conveyance part conveyed to the banknote storage part which is not shown in figure, discriminating the money type and authenticity of the banknote inserted from the banknote insertion port 12. FIG. The display operation unit 13 is a touch panel type input / output device that is held by the inter-card card processing machine 10 for performing inquiry operations such as member information and card information, ball lending operations, and message display for the player in the present invention. It is.

  The communication unit 19 is an interface unit for performing data communication with the gaming machine 20, the member management device 50, and the card management device 40.

  The storage unit 10e is a storage device composed of a hard disk device, a nonvolatile memory, or the like. The memory | storage part 10e memorize | stores card ID10e1, the number-of-balls data 10e2, the prepaid value 10e3, and the stored ball replay data 10e4.

  The card ID 10e1 is a card ID read by the card reader / writer 10a. When a card is transported from the card storage unit 16 to the card insertion slot 14 and the card is ejected, the card ID 10e1 is updated with the card ID read by the card reader / writer 10a during the transport. Also, when a card is transported from the card insertion slot 14 to the card storage unit 16, the card ID 10e1 is updated with the card ID read by the card reader / writer 10a during the transport.

  The number of balls possessed 10e2 indicates the number of balls currently held by the player. The number of balls is acquired from the ball account of the card management device 40 or added by counting by the counting unit 18 and subtracted by the ball replay process. The prepaid value 10e3 indicates the current prepaid value of the player. The prepaid value 10e3 is acquired from prepaid value information managed in association with the card ID of the card management device 40, or when a banknote is inserted into the banknote insertion slot 12, a prepaid value corresponding to this banknote is added. And subtracted by the ball lending process.

  The stored ball replay data 10e4 is data relating to the replay of the stored ball, and includes the current number of stored balls of the player, the number of replayable items, and a password. The stored ball replay data 10e4 is received from the member management device 50 and stored or updated. The number of stored balls and the replayable number are used for display on the display operation unit 13, and the password is used for comparison with the password entered by the player.

  The control unit 10f is a control unit that totally controls the inter-card card processing machine 10, and includes a data management unit 10f1, a card processing unit 10f2, and a storage ball replay management unit 10f3.

  The data management unit 10f1 is a management unit that manages the number-of-balls data 10e2 and the prepaid value 10e3 stored in the storage unit 10e. When the ball lending operation is performed by the player, the data management unit 10f1 transmits a ball lending request to the card management device 40 and receives a ball lending permission from the card management device 40, for example, “250”. ) Pachinko balls. By this lending, the prepaid value managed by the card management device 40 is subtracted by a predetermined number, and the prepaid value 10e3 is updated to the value after subtraction. Further, when a bill is inserted into the bill insertion slot 12, the data management unit 10f1 notifies the card management device 40 of the amount corresponding to the bill. With this lending, the prepaid value managed by the card management device 40 is added with the amount equivalent to the deposit amount, and the prepaid value 10e3 is updated to the value after the addition.

  Further, when the counting unit 18 counts the pachinko balls, the data management unit 10f1 adds the counted number of balls to the number-of-balls data 10e2. Further, when the data management unit 10f1 accepts the possession ball replay operation, the data management unit 10f1 subtracts the possession number data 10e2 by a predetermined number (for example, 25 balls) and pays out the subtracted number of balls from the gaming machine. When the possessed ball replay operation is accepted, if the retained ball number data 10e2 is less than the predetermined number, the number of balls is paid out from the nozzle unit 17, and the retained ball number data 10e2 is set to zero.

  In addition, if the data management unit 10f1 accepts the storage ball replay operation, the data management unit 10f1 transmits a storage ball replay request to the member management device 50, and receives the storage ball replay data indicating permission of the storage ball replay from the member management device 50. Then, a predetermined number of balls (for example, 125 balls) is paid out from the gaming machine. A predetermined number of balls (for example, 125 balls) is subtracted from the number of stored balls managed by the member management apparatus 50 by a stored ball replay operation.

  When the card processing unit 10f2 receives a card from a card insertion slot 14 (not shown), the card reader / writer 10a reads the card ID and stores it in the storage unit 10e as the card ID 10e1. Further, the card processing unit 10f2 transmits the card ID 10e1 to the card management device 40, and receives the prepaid value and the possession account balance associated with the card ID from the card management device 40. The received prepaid value is stored in the storage unit 10e as the prepaid value 10e3, and the balance of the possession account is stored in the storage unit 10e as the number of possession balls 10e2. Further, when the inserted card is a membership card, the stored ball replay data 10e4 is received from the membership management device 50 via the card management device 40. The stored ball replay data includes the number of stored balls, which is the balance of the stored ball high account associated with the card ID, a personal identification number, and the replayable number. The card processing unit 10f2 stores the received stored ball replay data 10e4 in the storage unit 10e.

  The stored ball replay management unit 10f3 controls the display operation unit 13 to display the number of stored balls and the replayable number indicated in the stored ball replay data 10e4. Furthermore, when the replayable number is equal to or greater than the number of payout units for the stored ball replay (for example, 125), a stored ball replay button for accepting the stored ball replay operation is displayed on the display operation unit 13.

  When the stored ball replay button is operated, the stored ball replay management unit 10f3 permits transmission of a stored ball replay request by the data management unit 10f1 on the condition that the password has been confirmed. If the password has not been confirmed, a password input screen is displayed on the display operation unit 13 to accept the password input from the player. The stored ball replay management unit 10f3 compares the input password number and the password number of the stored ball replay data 10e4, and if they match, sets a flag indicating that the password number has been confirmed, and the stored data by the data management unit 10f1 Allow sending replay request. The flag indicating that the PIN has been confirmed is reset when the card is returned.

  If the data management unit 10f1 that has received permission from the storage ball replay management unit 10f3 transmits the storage ball replay request and then receives the storage ball replay data 10e4 from the member management device 50, the storage ball replay management unit 10f3 The replay data 10e4 is updated, and the updated number of stored balls and the replayable number are displayed and controlled on the display operation unit 13. Furthermore, it is determined whether the number of replayable items is less than the number of payout units for savings replay, and if the number is less than the number of payout units, the saver replay button is hidden or savings replay is impossible Change the display to indicate that

  Next, the processing procedure of the stored ball replay by the inter-card card processing machine 10 will be described. FIG. 5 is a flowchart showing a processing procedure of replay of stored balls by the inter-card card processing machine 10. The card processing unit 10f2 determines whether or not the card ID has been read by the card reader / writer 10a (step S101). If the card ID has not been read (step S101; No), whether or not the card ID has been read. The standby operation for repeating the determination (step S101) is performed.

  When the card ID is read by the card reader / writer 10a (step S101; Yes), the card processing unit 10f2 transmits a card insertion notification including the read card ID to the card management device 40 (step S102). When this card ID is the card ID of the member card, the card insertion notification is transmitted from the card management device 40 to the member management device 50, and the stored ball replay data is transmitted from the member management device 50 to the inter-card processing unit 10. Is done.

  The card processing unit 10f2 receives the stored ball replay data 10e4 transmitted from the member management device 50 and stores it in the storage unit 10e (step S103). The stored ball replay management unit 10f3 controls the display operation unit 13 to display the number of stored balls and the replayable number indicated in the stored ball replay data 10e4 (step S104).

  Also, the stored ball replay management unit 10f3 determines whether or not the replay of the stored ball is possible, that is, whether or not the replayable number is equal to or greater than the number of payout units of the stored ball replay (step S105). When the stored ball replay is impossible, that is, when the replayable number is less than the payout unit number (step S105; No), the stored ball replay management unit 10f3 displays that the stored ball replay cannot be performed. 13 is controlled (step S115), and the process is terminated.

  On the other hand, when the stored ball replay is possible, that is, when the replayable number is equal to or greater than the number of payout units (step S105; Yes), the stored ball replay management unit 10f3 displays the stored ball replay button. (Step S106).

  If the display control unit 13 accepts the operation of the storage ball replay button (step S107; Yes), the storage ball replay management unit 10f3 determines whether or not the personal identification number has been confirmed (step S108). This confirmation is performed by reading a flag indicating that the password has been confirmed.

  When the personal identification number has been confirmed (step S108; Yes), the data management unit 10f1 transmits a stored ball replay request (step S110). On the other hand, when the personal identification number is not confirmed (step S108; No), the storage ball replay management unit 10f3 performs a personal identification number confirmation process (step S109).

  The personal identification number confirmation process is a process of displaying a personal identification number input screen on the display operation unit 13, receiving a personal identification number input from the player, and comparing the inputted personal identification number with the personal identification number of the pool replay data 10e4. is there. If the input password and the password of the stored ball replay data 10e4 match, a flag indicating that the password has been confirmed is set, and the data management unit 10f1 transmits a stored ball replay request (step S110). If the code numbers do not match, the input of the code number is accepted again. Then, when the number of input of the personal identification number reaches the specified number, the display operation unit 13 is controlled to display that the replay of the stored ball cannot be performed, and the process is terminated.

  If the stored ball replay data 10e4 is received after transmitting the stored ball replay request in step S110, the stored ball replay management unit 10f3 updates the stored ball replay data 10e4 (step S111). Further, the stored ball replay management unit 10f3 updates the display of the updated number of stored balls and the replayable number (step S112). Thereafter, the data management unit 10f1 pays out a predetermined number of pachinko balls (step S113). The stored-ball replay management unit 10f3 determines whether or not the stored-ball replay is possible based on whether or not the replayable number after the update is equal to or greater than the number of payout units for the stored-ball replay (step S114).

  When the stored ball replay is possible (step S114; Yes), or when the stored ball replay operation is not received (step S107; No), the inter-card processing machine 10 determines whether or not the stored ball replay operation is received. The process proceeds to determination (step S107).

  When the replay of the stored ball is impossible (step S114; No), the stored ball replay management unit 10f3 controls the display operation unit 13 to display that the replay of the stored ball cannot be performed (step S115), and the process is performed. finish.

  Next, an internal configuration according to the first embodiment of the member management apparatus 50 shown in FIG. 2 will be described. FIG. 6 is a block diagram showing an internal configuration of the member management apparatus 50 shown in FIG. As shown in the figure, the member management apparatus 50 is connected to a display unit 51 and an input unit 52. The display unit 51 is a liquid crystal panel, a display device, or the like, and the input unit 52 is a keyboard, a mouse, or the like.

  The member management apparatus 50 includes a communication unit 53, a storage unit 54, and a control unit 55. The communication unit 53 is an interface unit for performing data communication with the inter-card processor 10 and the like via the communication line 90.

  The storage unit 54 is a storage device such as a hard disk device or a nonvolatile memory, and stores member data 54a, stored ball replay permission condition data 54b, and stored ball replay ball count 54c. In the member data 54a, personal information such as a member's name, address, personal identification number, telephone number, and identification ID of a mobile phone terminal, and stored ball information that is the balance of the stored account for each game type are associated with the card ID. It is data.

  The stored ball replay permission condition data 54b is data indicating a condition for determining permission of the stored ball replay. The number of replayed balls 54c is the maximum number of balls replayed for today calculated from the number of stored balls at the start of today's game and the replay permission condition data 54b for the balls, This is data indicating the number of replay balls and the number of replayable balls.

  The control unit 55 is a control unit that totally controls the member management apparatus 50, and includes a member data management unit 55a, a stored-ball replay upper limit management unit 55b, and a stored-ball replay processing unit 55c. In practice, programs corresponding to these functional units are stored in a ROM or non-volatile memory (not shown), and these programs are loaded into a CPU (Central Processing Unit) and executed, whereby the member data management unit 55a. The stored ball replay upper limit management unit 55b and the stored ball replay processing unit 55c are caused to execute corresponding processes.

  The member data management unit 55a is a processing unit that registers, inquires, updates, and deletes data for the member data 54a. The member data management unit 55a is also a processing unit that notifies the member data 54a. When the card insertion notification is received from the inter-card card processor 10, each member data management unit 55a is associated with the card ID included in the card insertion notification. The stored ball replay data including the number of stored balls, which is the balance of the rate stored ball account, the personal identification number, and the replayable number calculated by the stored ball replay upper limit management unit 55b is transmitted to the inter-card processing machine 10. When the card ID is received from the prize management device 60, the balance of the savings account at each rate associated with the card ID is notified. In addition, when the member data management unit 55a receives the card ID, the used storage account and the number of balls from the prize management device 60, the member data management unit 55a sets the received card ID and the number of balls associated with the used storage account to the received number of balls. replace.

  The stored ball replay upper limit management unit 55b is a processing unit that manages the upper limit of stored ball replay. Specifically, when the card ID indicated in the card insertion notification is the card ID received for the first time on that day, the stored-ball replay upper limit management unit 55b counts the number of stored-ball replay balls on the current date related to the card ID. 54c is created. Then, the storage ball replay upper limit ball number on the day of the stored ball replay ball number 54c is calculated from the stored ball information of the member data 54a and the stored ball replay permission condition data 54b, and the stored ball replay ball on the current day of the stored ball replay ball number 54c. Set the number to 0.

  The stored-ball replay upper limit management unit 55b calculates the replayable number based on the member data 54a and the stored-ball replayed ball count 54c. Specifically, using the number of stored balls associated with the card ID in the member data 54a and the number of stored balls replay upper limit balls and the number of stored ball replay balls associated with the card ID in the stored ball replay balls 54c, the number of stored balls The smaller one of (the upper limit number of balls for replaying the stored ball-the number of balls for replaying the same day) is the replayable number.

  Moreover, when the number of stored balls and the number of stored ball replay balls on the day are updated by the stored ball replay processing unit 55c, the storage ball replay upper limit management unit 55b recalculates the replayable number using the updated value. To do.

  The replayable number calculated by the stored ball replay upper limit management unit 55b is stored in the stored ball replay ball number 54c, and is included in the stored ball replay data and transmitted to the inter-card processing machine 10.

  When the storage ball replay processing unit 55c receives a storage ball replay request including the card ID from the inter-card processing machine 10, the storage ball replay processing unit 55c updates the member data 54a by subtracting the number of storage balls associated with the card ID by the number of payout units. Then, the number of replay balls of the day associated with the card ID in the number of replay balls 54c is updated by adding the number of payout units. By this update, the stored ball replay upper limit management unit 55b calculates the replayable number again, and updates the stored ball replay ball number 54c. The stored ball replay processing unit 55c transmits stored ball replay data including the updated number of stored balls and the replayable number to the inter-card card processing machine 10.

  Next, a data configuration according to the first embodiment of the member management apparatus 50 illustrated in FIG. 6 will be described. FIG. 7 is an explanatory diagram for explaining the configuration of the member data 54a, the stored ball replay permission condition data 54b, and the stored ball replay ball count 54c of the member management device 50 shown in FIG.

  The member data 54a is data in which personal information such as a member's name, address, and personal identification number is associated with stored ball information for each game type with respect to the card ID of the member card. The member data 54a shown in FIG. 7 includes, for the card ID “00001”, member personal information, a 4 yen pachinko storage ball “15000”, a 2 yen pachinko storage ball “2500”, and a 1 yen pachinko storage ball “ The data of the “0” ball is associated.

  In the first embodiment, the range of possible replaying of the stored ball is not limited to the number of stored balls in the member data 54a, but the upper limit number of replayed balls per day, or can be replayed by pulling out from the stored ball account per day. It is determined by the ratio to the stored balls, and is stored as stored ball replay permission condition data 54b. In the storage ball replay permission condition data 54b shown in FIG. 7, the maximum number of balls that can be replayed on the 1st is “5000”, and the ratio that can be withdrawn from the storage account on the 1st and replayed the stored balls is “50%”. Yes.

  In addition, the number of replayed balls 54c is related to the card ID of the member card, the last play date of the member, the stored ball information of the member data 54a at the start of play on the day of the last play, and the replay permit condition data 54b The above-mentioned upper limit of the number of balls replayed on the day of the member calculated from the above, the number of balls replayed on the day that is the actual number of balls replayed on the day of the last play, and the number of replayables are held. The number of replayed balls 54c shown in FIG. 7 is the last play date “2012/4/1” for the card ID “00001”, 4 yen pachinko for the upper limit of the number of replayed balls on that day, “5000”, 2 yen Pachinko is associated with "1250", 1 yen pachinko is "0", the number of replayed balls of the day is 4 yen pachinko is "0", 2 yen pachinko is "500", 1 yen pachinko is associated with "0". The replayable number of 4 yen pachinko is “5000”, the replayable number of 2 yen pachinko is “750”, and the replayable number of 1 yen pachinko is “0”.

  Next, a processing procedure related to the replay of stored balls by the member management apparatus 50 will be described. FIG. 8 is a flowchart showing a processing procedure related to the replay of stored money by the member management apparatus 50. First, the member data management unit 55a determines whether or not a card insertion notification has been received from the inter-card card processing machine 10 (step S201).

  If the card insertion notification is received (step S201; Yes), the stored ball replay upper limit management unit 55b creates a record of the number of replayed balls 54c corresponding to the card ID included in the card insertion notification (step S202). ).

  Specifically, today's date is written in the last play date, and the number of replay balls for that day is cleared to zero. Further, from the stored ball information of the member data 54a and the stored ball replay permission condition data 54b, the stored ball replay upper limit ball number for each game type of the stored ball replay ball count 54c is calculated and written to the upper limit number of stored ball replay balls of the day ( Step S203). If the card insertion notification including the card ID has already been received on the same day and there is a record in the number of replayed balls 54c, the existing value is used as it is.

  The stored-ball replay upper limit management unit 55b, the stored-ball replay upper limit ball number calculated in step S203, the number of stored balls indicated in the member data 54a, and the stored-ball replay ball of the day indicated in the stored ball replay ball number 54c. The replayable number is calculated from the number and stored in the stored ball replayed ball number 54c (step S204).

  The member data management unit 55a generates stored ball replay data including the number of stored balls and the secret number indicated in the member data 54a, and the replayable number indicated in the stored ball replayed ball number 54c. It transmits to the machine 10 (step S205).

  After step S205 or when a card insertion notification has not been received (step S201; No), the stored ball replay processing unit 55c determines whether or not a stored ball replay request has been received from the inter-card card processor 10. (Step S206). As a result of the determination, when the storage ball replay request has not been received (step S206; No), the process is terminated.

  On the other hand, when the storage ball replay request is received (step S206; Yes), the number of stored balls associated with the card ID in the member data 54a is updated by subtracting the number of payout units (step S207), and the storage ball replay ball is updated. In number 54c, the number of re-playing balls of the day associated with the card ID is added by the number of payout units and updated (step S208).

  After step S208, the stored ball replay upper limit management unit 55b calculates the replayable number again, and updates the stored ball replay ball number 54c (step S209). The stored ball replay processing unit 55c transmits the stored ball replay data including the updated number of stored balls and the replayable number to the inter-card processing machine 10 (step S210), and ends the process.

  As described above, in the first embodiment, the stored ball information is managed in association with the card ID of the member card for identifying the player, and the upper limit of the number of balls replayed on the 1st and the withdrawal from the stored account on the 1st. The percentage of players who can replay the stored ball can be set as a restriction condition that allows the replay of the stored ball, so it is possible to operate a highly convenient storage media service for players without losing the profits of the game store. Can be done.

  By the way, in the said Example 1, although the ratio of the upper limit of the replay with respect to the number of stored balls was made constant regardless of the number of stored balls, this invention is not limited to this, The range of the number of stored balls is set. It is also possible to set the ratio of the upper limit of replay to the number of stored balls for each range of stored balls. Therefore, in the second embodiment, a case will be described in which the range of the number of stored balls is set, and the ratio of the upper limit of the replay to the number of stored balls is set for each range of the number of stored balls, thereby appropriately limiting the replay of the stored balls. Note that the configuration and operation of the inter-card card processing machine 10 in the second embodiment are the same as those in the first embodiment, and a description thereof will be omitted.

  First, the internal configuration of the member management apparatus 150 according to the second embodiment will be described. FIG. 9 is a block diagram showing an internal configuration of the member management apparatus 150. As shown in the figure, the member management apparatus 150 is connected to a display unit 151 and an input unit 152. The display unit 151 is a liquid crystal panel, a display device, or the like, and the input unit 152 is a keyboard, a mouse, or the like.

  The member management apparatus 150 includes a communication unit 153, a storage unit 154, and a control unit 155. The communication unit 153 is an interface unit for performing data communication with the inter-card card processor 10 or the like via the communication line 90.

  The storage unit 154 is a storage device such as a hard disk device or a non-volatile memory, and stores member data 154a, stored ball replay permission condition data 154b, and stored ball replay ball count 154c. In the member data 154a, personal information such as a member's name, address, personal identification number, telephone number, and identification ID of a mobile phone terminal, and stored ball information that is a balance of a stored account for each game type are associated with a card ID. It is data.

  The storage ball replay permission condition data 154b is data indicating a condition for determining permission for storage ball replay. The number of replayed balls 154c is the maximum number of balls replayed for today calculated from the number of balls stored at the start of today's game and the replay permission condition data 154b for the balls, This is data indicating the number of replay balls and the number of replayable balls.

  The control unit 155 is a control unit that totally controls the member management apparatus 150, and includes a member data management unit 155a, a stored ball replay upper limit management unit 155b, and a stored ball replay processing unit 155c. Actually, programs corresponding to these functional units are stored in a ROM or a non-volatile memory (not shown), and these programs are loaded into a CPU (Central Processing Unit) and executed, whereby the member data management unit 155a. The stored ball replay upper limit management unit 155b and the stored ball replay processing unit 155c are caused to execute corresponding processes.

  The member data management unit 155a is a processing unit that registers, inquires, updates, and deletes data for the member data 154a. The member data management unit 155a is also a processing unit that notifies the member data 154a. When the card insertion notification is received from the inter-card card processor 10, each member data management unit 155a is associated with the card ID included in the card insertion notification. The stored ball replay data including the number of stored balls, which is the balance of the rate storage ball account, the personal identification number, and the replayable number calculated by the stored ball replay upper limit management unit 155b is transmitted to the inter-card processing machine 10. When the card ID is received from the prize management device 60, the balance of the savings account at each rate associated with the card ID is notified. In addition, when the member data management unit 155a receives the card ID, the used storage account and the number of balls from the prize management device 60, the member data management unit 155a sets the number of balls received corresponding to the received card ID and the used storage account. replace.

  The stored-ball replay upper limit management unit 155b is a processing unit that manages the upper limit of stored-ball replay. Specifically, when the card ID indicated in the card insertion notification is the card ID received for the first time on that day, the stored-ball replay upper limit management unit 155b counts the number of stored-ball replay balls on the current date related to the card ID. 154c is created. Then, from the stored ball information of the member data 154a and the member-specific stored ball replay allowance condition data 154b, the upper limit number of stored balls replayed balls 154c on the current day is calculated, and the stored ball replayed balls 154c on the current day Set the number of play balls to 0.

  The stored ball replay upper limit management unit 155b calculates the replayable number based on the member data 154a and the stored ball replay ball number 154c. Specifically, using the number of stored balls associated with the card ID in the member data 154a and the number of stored balls replay upper limit ball and the number of stored ball replayed balls associated with the card ID in the stored ball replayed ball number 154c, The smaller one of (the upper limit number of balls for replaying the stored ball-the number of balls for replaying the same day) is the replayable number.

  In addition, when the stored ball replay processing unit 155c updates the number of stored balls and the number of stored ball replayed balls on the day, the stored ball replay upper limit management unit 155b calculates the replayable number again using the updated value. To do.

  The replay possible number calculated by the stored ball replay upper limit management unit 155b is stored in the stored ball replay ball number 154c, and is included in the stored ball replay data and transmitted to the inter-card processing machine 10.

  When the stored ball replay processing unit 155c receives a stored ball replay request including the card ID from the inter-card processing machine 10, the stored ball replay processing unit 155c updates the member data 154a by subtracting the number of stored balls associated with the card ID by the number of payout units. Then, the number of re-playing balls of the day associated with the card ID in the number of re-playing balls 154c is updated by adding the number of payout units. With this update, the stored ball replay upper limit management unit 155b calculates the replayable number again, and updates the stored ball replay ball number 154c. The stored ball replay processing unit 155 c transmits stored ball replay data including the updated number of stored balls and the number of replayable items to the inter-card card processing machine 10.

  Next, a data configuration according to the second embodiment of the member management apparatus 150 illustrated in FIG. 9 will be described. FIG. 10 is an explanatory diagram for explaining the configuration of the member data 154a, the stored ball replay permission condition data 154b, and the stored ball replay ball number 154c of the member management apparatus 150 shown in FIG.

  The member data 154a is data in which personal information such as a member's name, address, and password is associated with stored ball information for each game type, with respect to the card ID of the member card. The member data 154a shown in FIG. 10 includes, for the card ID “00001”, member personal information, a 4-yen pachinko storage ball “15000”, a 2-yen pachinko storage ball “2500”, and a 1-yen pachinko storage ball “ The “0” ball is associated.

  In the second embodiment, the range of possible replaying of the stored balls is not limited to the number of stored balls in the member data 154a, but the upper limit number of stored balls replayed per day, and the reclaimed balls can be redrawn from the stored account in one day. It is determined by the ratio to the stored balls, and is stored as stored ball replay permission condition data 154b. In addition, the ratio to the number of stored balls that can be withdrawn from a stored account in a day and replayed can be set for each range. The storage ball replay permission condition data 154b shown in FIG. 10 stipulates that the number of balls at the upper limit of the storage ball replay per day is “5000”, and the ratio that can be withdrawn from the storage account in one day and replayed the storage ball. “50%” when the number of stored balls is in the range of 1 to less than 1000, “30%” when the number of stored balls is in the range of 1000 to less than 5000, and “50%” when the number of stored balls is in the range of 5000 to less than 10,000. “20%”, and “10%” when the number of stored balls is in the range of 10,000 to less than 50000.

  Further, the number of replayed balls 154c is calculated from the last play date of the member, the stored ball information of the member data 154a at the start of play on the day of the last play, and the replay permission condition data 154b of the stored ball in association with the card ID. The member has the maximum number of replay balls for that day, the number of replay balls for that day, which is the actual number of replays for that day, and the number of replayable items. The number of replayed balls 154c shown in FIG. 10 is “1500”, 2 yen for the card ID “00001”, the last play date “2012/4/1”, 4 yen pachinko for the maximum number of balls replayed on that day. Pachinko is associated with "1250", 1 yen pachinko is "0", the number of replayed balls of the day is 4 yen pachinko is "0", 2 yen pachinko is "500", 1 yen pachinko is associated with "0". The replayable number of 4 yen pachinko is “1500”, the replayable number of 2 yen pachinko is “750”, and the replayable number of 1 yen pachinko is “0”.

  Next, a processing procedure related to the replay of stored money by the member management apparatus 150 will be described. FIG. 11 is a flowchart showing a processing procedure related to the replay of stored balls by the member management apparatus 150. First, the member data management unit 155a determines whether or not a card insertion notification is received from the inter-card card processing machine 10 (step S301).

  If the card insertion notification is received (step S301; Yes), the stored ball replay upper limit management unit 155b creates a record of the number of stored ball replay balls 154c corresponding to the card ID included in the card insertion notification (step S302). ).

  Specifically, today's date is written in the last play date, and the number of replay balls for that day is cleared to zero. Further, from the stored ball information of the member data 154a and the stored ball replay permission condition data 154b, the upper limit number of stored ball replay balls for each game type of the stored ball replay ball number 154c is calculated and written to the upper limit number of stored ball replay balls of the day ( Step S303). If the card insertion notification including the card ID has been received on the same day and a record exists in the number of replayed balls 154c, the existing value is used as it is.

  The storage ball replay upper limit management unit 155b, the storage ball replay upper limit ball number calculated in step S303, the number of storage balls indicated in the member data 154a, and the storage ball replay ball of the day indicated in the storage ball replay ball number 154c. The replayable number is calculated from the number and stored in the stored ball replayed ball number 154c (step S304).

  The member data management unit 155a generates stored ball replay data including the number of stored balls and the password indicated in the member data 154a and the replayable number indicated in the stored ball replayed ball number 154c, and performs inter-card processing. It transmits to the machine 10 (step S305).

  After step S305 or when a card insertion notification has not been received (step S301; No), the stored ball replay processing unit 155c determines whether or not a stored ball replay request has been received from the inter-card card processing machine 10. (Step S306). As a result of the determination, when the storage ball replay request has not been received (step S306; No), the process is terminated.

  On the other hand, when the stored ball replay request is received (step S306; Yes), the number of stored balls associated with the card ID in the member data 154a is subtracted and updated by the number of payout units (step S307). In the formula 154c, the number of the re-playing balls of the day associated with the card ID is updated by adding the number of payout units (step S308).

  After step S308, the stored ball replay upper limit management unit 155b calculates the replayable number again, and updates the stored ball replay ball number 154c (step S309). The stored ball replay processing unit 155c transmits the stored ball replay data including the updated number of stored balls and the replayable number to the inter-card card processing machine 10 (step S310), and ends the process.

  As described above, in the second embodiment, the stored ball information is managed in association with the card ID of the member card, and the number of balls that can be used for replaying the ball that can be used in a day can be set as a percentage of the number of stored balls. At the same time, since the ratio is configured to vary according to the range of the number of stored balls, the number of replayed balls that can be used per day is set appropriately according to the number of stored balls, and without detracting from the profits of the amusement store. It is possible to operate a game storage service that is convenient for customers.

  Specifically, when the number of stored balls is small, the ratio is increased to ensure the number of times that the stored ball can be replayed, and when the number of stored balls is large, excessive replay of stored balls can be suppressed.

  By the way, in the first embodiment and the second embodiment, the upper limit number of balls allowed to be replayed is determined only in relation to the number of balls held by the player, but the present invention is limited to this. It is also possible to set the maximum number of replays of savings balls according to the rank of the member and the situation of visits, giving preferential treatment to excellent players or preferential treatment to players who have signs of leaving the other game stores It can also be used for sales strategies such as Therefore, in the third embodiment, a case will be described in which the upper limit number of replays of stored balls is set according to the rank of the member and the visiting situation. Note that the configuration and operation of the inter-card card processing machine 10 in the third embodiment are the same as those in the first embodiment, and a description thereof will be omitted.

  First, an internal configuration according to the third embodiment of the member management apparatus 250 will be described. FIG. 12 is a block diagram showing an internal configuration of the member management apparatus 250. As shown in the figure, the member management apparatus 250 is connected to a display unit 251 and an input unit 252. The display unit 251 is a liquid crystal panel, a display device, or the like, and the input unit 252 is a keyboard, a mouse, or the like.

  The member management device 250 includes a communication unit 253, a storage unit 254, and a control unit 255. The communication unit 253 is an interface unit for performing data communication with the inter-card processor 10 and the like via the communication line 90.

  The storage unit 254 is a storage device such as a hard disk device or a non-volatile memory, and stores member data 254a, a member rank-based stored ball replay upper limit 254b, an RF-specific stored ball replay upper limit 254c, and a stored ball replayed ball count 254d. The member data 254a includes member information such as a member's name, address, personal identification number, telephone number, mobile phone terminal identification ID and the like, as well as member information indicating the balance of the savings account for each game type. This is data in which a situation is associated with a card ID.

  The member rank-specific stored ball replay upper limit 254b is data defining an upper limit value of stored ball replay for each member rank. The RF-specific stored ball replay upper limit 254c is data that defines the upper limit value of the stored ball replay in association with the last visit date and the store visit frequency.

  The number of replayed balls 254d is calculated based on the number of stored balls at the start of the game in the member data 254a, the member rank, and the store visit status, the replay upper limit 254b by member rank, and the replay upper limit 254c by RF. It is data which shows the upper limit ball number of storage ball replay, the storage ball replay carried out today within the range, and the replayable number.

  The control unit 255 is a control unit that totally controls the member management apparatus 250, and includes a member data management unit 255a, a stored ball replay upper limit management unit 255b, and a stored ball replay processing unit 255c. Actually, programs corresponding to these functional units are stored in a ROM or a non-volatile memory (not shown), and these programs are loaded into a CPU (Central Processing Unit) and executed, whereby the member data management unit 255a. The stored ball replay upper limit management unit 255b and the stored ball replay processing unit 255c are each caused to execute a corresponding process.

  The member data management unit 255a is a processing unit that performs registration, inquiry, update, and deletion of data for the member data 254a. The member data management unit 255a is also a processing unit that notifies the member data 254a. When the card insertion notification is received from the inter-card card processor 10, each member data management unit 255a is associated with the card ID included in the card insertion notification. The stored ball replay data including the number of stored balls, which is the balance of the rate storage ball account, the personal identification number, and the replayable number calculated by the stored ball replay upper limit management unit 255b is transmitted to the inter-card processing machine 10. When the card ID is received from the prize management device 60, the balance of the savings account at each rate associated with the card ID is notified. In addition, when the member data management unit 255a receives the card ID, the used storage account and the number of balls from the prize management device 60, the member data management unit 255a sets the number of balls received corresponding to the received card ID and the used storage account. replace.

  The stored ball replay upper limit management unit 255b is a processing unit that manages the upper limit of stored ball replay. Specifically, when the card ID indicated in the card insertion notification is the card ID received for the first time on that day, the stored-ball replay upper limit management unit 255b stores the number of stored-ball replay balls on the current date related to the card ID. 254d is created. Then, using the storage information, the member rank and the store visit status of the member data 254a, the storage ball replay upper limit 254b by member rank, and the RF replay upper limit 254c by RF, the storage replay upper limit of the day of the number 254d of the storage replay balls While calculating the number of balls, 0 is set to the number of balls replayed on the day of the number 254d of replayed balls.

  The stored ball replay upper limit management unit 255b calculates the replayable number based on the member data 254a and the stored ball replay ball number 254d. Specifically, using the number of stored balls associated with the card ID in the member data 254a and the upper limit number of stored balls replayed and the number of stored ball replayed balls associated with the card ID in the stored ball replayed ball number 254d, The smaller one of (the upper limit number of balls for replaying the stored ball-the number of balls for replaying the same day) is the replayable number.

  In addition, when the stored ball replay processing unit 255c updates the number of stored balls and the number of stored ball replay balls of the day, the stored ball replay upper limit management unit 255b recalculates the replayable number using the updated value. To do.

  The replayable number calculated by the stored ball replay upper limit management unit 255b is stored in the stored ball replay ball number 254d, and is included in the stored ball replay data and transmitted to the inter-card processing machine 10.

  When the stored ball replay processing unit 255c receives a stored ball replay request including the card ID from the inter-card processing machine 10, the stored ball replay processing unit 255c updates the member data 254a by subtracting the number of stored balls associated with the card ID by the number of payout units. Then, the number of replay balls of the day associated with the card ID in the number of replay balls 254d is updated by adding the number of payout units. With this update, the stored ball replay upper limit management unit 255b calculates the replayable number again, and updates the stored ball replay ball number 254d. The stored ball replay processing unit 255 c transmits stored ball replay data including the updated number of stored balls and the replayable number to the inter-card processing machine 10.

  Next, a data configuration according to the third embodiment of the member management apparatus 250 illustrated in FIG. 12 will be described. FIG. 13 is an explanatory diagram for explaining the configuration of the member data 254a, the member rank-specific stored ball replay upper limit 254b, the RF-based stored ball replay upper limit 254c, and the stored ball replayed ball count 254d of the member management apparatus 250 shown in FIG. It is.

  The member data 254a associates the card ID of the member card with personal information such as the member's name, address, and personal identification number, storage information for each game type, member rank, and the store visit status of the last visit or visit frequency. Data. The member data 254a shown in FIG. 13 includes, for the card ID “00001”, the member personal information, the member rank “4”, the final store visit status “4”, the store visit frequency “2”, 4 Yen pachinko storage balls “15000”, 2-yen pachinko storage balls “2500”, and 1-yen pachinko storage balls “0” are associated with each other. In the third embodiment, the member rank can be set from 1 to 5, with “1” indicating the highest member rank, and decreasing in the order of “2”, “3”, “4”, “5”. “5” indicates the lowest member rank. The last store visit status can be set to 1 to 5, and “1” indicates that there is the closest store visit record, in the order of “2”, “3”, “4”, “5”. It goes down and “5” indicates the farthest visit. In addition, the store visit frequency of the store visit status can be set from 1 to 5, and “1” indicates the most frequently visited store results, and “2”, “3”, “4”, “5”. In this order, “5” indicates the lowest frequency of visits.

  The member rank-based stored ball replay upper limit 254b is data in which the upper limit of the number of balls for replaying the daily stored ball by member rank is set. The member rank-specific storage ball replay upper limit 254b shown in FIG. 13 is “unlimited” for member rank 1, “8000” for member rank 2, “5000” for member rank 3, and for member rank 4. For “3000” and member rank 5, an upper limit of “2000” storage replay is set.

  The RF-specific storage ball replay upper limit 254c is data in which the upper limit of the number of balls for the daily storage replay is set according to the final store visit frequency and the store visit frequency. The upper limit 254c for storing money replayed by RF shown in FIG. 13 is “8000” when the last visit “1” and the visit frequency “1”, “8000” when the last visit “1” and the visit frequency “2”, and “ “8000” when the visit frequency is “1” at “2”, “8000” when the visit frequency is “1” at the last visit “4”, “5000” when the visit frequency is “2” at the last visit “4”, and the last visit The upper limit of “5000” is set when the store visit frequency is “1” at “5”, and “5000” is set when the store visit frequency is “2” at the last store visit “5”. 13, the store visit replay upper limit 254c for each RF shown in FIG. 13 is “1” for the last visit “1”, “2” for the visit “1” for the last visit, and “1” for the visit “2” for the last visit. If it is one of the above, preferential treatment as a good player, the visit frequency is “1” at the last visit “4”, the visit frequency is “2” at the last visit “4”, the visit frequency is “1” at the last visit “5”, When the last visit is “4” and the visit frequency is “2”, this is a setting example in which preferential treatment is made with the intention of returning the player who is likely to flow to another game store.

  In addition, when the upper limit number of balls replay is set differently between the member rank-specific storage ball replay upper limit 254b and the RF-specific storage ball replay upper limit 254c, the higher number is applied.

  Further, the number of replay balls 254d is related to the card ID, and the last play date of the member, the stored ball information of the member data 254a at the start of play on the day of the last play, and the replay upper limit 254b by member rank and RF The number of stored balls replay upper limit of the day calculated from the separate stored ball replay upper limit 254c, the number of stored balls replayed that day, which is the actual number of stored ball replays of the day, and the number of replayable are held. The number of replay balls 254d shown in FIG. 13 is “5000”, 2 yen for the last play date “2012/4/1” for the card ID “00001”, 4 yen pachinko for the maximum number of replay balls for that day. Pachinko is associated with "2500", 1 yen pachinko is "0", the number of replayed balls of the day is 4 yen pachinko is "0", 2 yen pachinko is "500", 1 yen pachinko is associated with "0". The replayable number of 4 yen pachinko is “5000”, the replayable number of 2 yen pachinko is “2000”, and the replayable number of 1 yen pachinko is “0”.

  Next, a processing procedure related to the replay of stored money by the member management apparatus 250 will be described. FIG. 14 is a flowchart showing a processing procedure related to the replay of stored money by the member management apparatus 250. First, the member data management unit 255a determines whether a card insertion notification has been received from the inter-card card processing machine 10 (step S401).

  If the card insertion notification is received (step S401; Yes), the stored ball replay upper limit management unit 255b creates a record of the number of stored ball replay balls 254d corresponding to the card ID included in the card insertion notification (step S402). ).

  Specifically, today's date is written in the last play date, and the number of replay balls for that day is cleared to zero. Further, from the member data 254a, the member replay upper limit 254b by member rank, and the RF replay upper limit 254c by RF, the upper limit number of replay balls for each game type of the number of replay balls 254d is calculated, and Write to the play upper limit ball number (step S403). In addition, when the card insertion notification including the card ID has been received on the same day and there is a record in the number of replayed balls 254d, the existing value is used as it is.

  The stored-ball replay upper limit management unit 255b, the stored-ball replay upper-limit number calculated in step S403, the stored-ball number indicated in the member data 254a, and the stored-ball replayed ball of the day indicated in the stored-ball replayed ball number 254d The replayable number is calculated from the number and stored in the stored ball replayed ball number 254d (step S404).

  The member data management unit 255a generates the stored ball replay data including the number of stored balls and the secret number indicated in the member data 254a and the replayable number indicated in the stored ball replayed ball number 254d. It transmits to the machine 10 (step S405).

  After step S405 or when a card insertion notification has not been received (step S401; No), the stored ball replay processing unit 255c determines whether or not a stored ball replay request has been received from the inter-card card processing machine 10. (Step S406). As a result of the determination, if the storage ball replay request has not been received (step S406; No), the process is terminated.

  On the other hand, when the storage ball replay request is received (step S406; Yes), the number of stored balls associated with the card ID in the member data 254a is updated by subtracting the number of payout units (step S407), and the stored ball replay ball is received. In number 254d, the number of re-playing balls on the day associated with the card ID is updated by adding the number of payout units (step S408).

  After step S408, the stored-ball replay upper limit management unit 255b calculates the replayable number again, and updates the stored-ball replayed ball number 254d (step S409). The stored ball replay processing unit 255c transmits the stored ball replay data including the updated number of stored balls and the replayable number to the inter-card card processing machine 10 (step S410), and ends the process.

  As described above, in the third embodiment, the stored ball information, the member rank, and the store visit status are managed in association with the card ID of the member card for identifying the player, and used on the day based on the member rank and the store visit status. Since the upper limit of possible replay of stored balls can be set, it is possible to operate a storage medium service that is highly convenient for the player without losing profits of the game store.

  By the way, in the said Example 1, Example 2, and Example 3, although the case where the upper limit of the stored-ball replay which can be used on the 1st was set based on the number of stored balls, the rank of a member, and the store visit condition was demonstrated, this invention Without being limited to this, it is also possible to set the upper limit of the number of replays depending on the day. Specifically, by setting a larger upper limit of the number of replays of stored balls on a day when there are few visitors, the store can be used for a sales strategy on a day when there are few visitors. Therefore, in the fourth embodiment, a case where the upper limit number of stored ball replays is set according to the day will be described. Note that the configuration and operation of the inter-card card processing machine 10 in the fourth embodiment are the same as those in the first embodiment, and a description thereof will be omitted.

  First, the internal configuration according to the fourth embodiment of the member management apparatus 350 will be described. FIG. 15 is a block diagram showing an internal configuration of the member management apparatus 350. As shown in the figure, the member management apparatus 350 is connected to a display unit 351 and an input unit 352. The display unit 351 is a liquid crystal panel, a display device, or the like, and the input unit 352 is a keyboard, a mouse, or the like.

  The member management apparatus 350 includes a communication unit 353, a storage unit 354, and a control unit 355. The communication unit 353 is an interface unit for data communication with the inter-card card processor 10 and the like via the communication line 90.

  The storage unit 354 is a storage device such as a hard disk device or a non-volatile memory, and stores member data 354a, a daily storage ball replay grant count 354b, a stored ball replay history 354c, and a stored ball replay ball count 354d. The member data 354a is data in which personal information such as a member's name, address, personal identification number, telephone number, and identification ID of a mobile phone terminal, and storage information that is the balance of a storage account for each game type are associated with a card ID. It is.

  The daily storage ball replay grant number 354b is data that sets how many balls that can be replayed for each date are given. If the number of savings replays given on the date given by visiting the store is not used up, the unused portion can be carried over from the next day. The stored-ball replay history 354c is data that holds the number of stored-ball replays given for each visit day in association with the member ID and the number of stored-ball replays used for stored-ball replay within the range of the given number of balls. is there. The number of replayed balls 354d is the maximum number of balls replayed today, calculated from the number of stored balls at the start of the game in the member data 354a, the daily number of replayed balls 354b, and the replay history 354c The number of balls replayed today within the range is stored.

  The control unit 355 is a control unit that totally controls the member management apparatus 350, and includes a member data management unit 355a, a stored ball replay upper limit management unit 355b, and a stored ball replay processing unit 355c. Actually, programs corresponding to these functional units are stored in a ROM or a non-volatile memory (not shown), and these programs are loaded into a CPU (Central Processing Unit) and executed, whereby the member data management unit 355a. The stored ball replay upper limit management unit 355b and the stored ball replay processing unit 355c are caused to execute corresponding processes.

  The member data management unit 355a is a processing unit that performs registration, inquiry, update, and deletion of data for the member data 354a. The member data management unit 355a is also a processing unit for notifying the member data 354a. When the card insertion notification is received from the inter-card card processor 10, each member data management unit 355a is associated with each card ID included in the card insertion notification. The stored ball replay data including the number of stored balls, which is the balance of the rate storage ball account, the personal identification number, and the replayable number calculated by the stored ball replay upper limit management unit 355b is transmitted to the inter-card processing machine 10. When the card ID is received from the prize management device 60, the balance of the savings account at each rate associated with the card ID is notified. In addition, when the member data management unit 355a receives the card ID, the used storage account and the number of balls from the prize management device 60, the member data management unit 355a sets the number of balls received corresponding to the received card ID and the used storage account. replace.

  The stored ball replay upper limit management unit 355b is a processing unit that manages the upper limit of stored ball replay. Specifically, when the card ID indicated in the card insertion notification is the card ID received for the first time on that day, the stored-ball replay upper limit management unit 355b counts the number of stored-ball replay balls on the current date related to the card ID. 354d is created. Then, from the stored ball information of the member data 354a, the daily storage ball replay grant number 354b, and the stored ball replay history 354c, the upper limit number of stored ball replay balls 354d on the day is calculated and the number of stored ball replay balls Set the number of balls replayed on the day of 354d to 0.

  The stored ball replay upper limit management unit 355b calculates the replayable number based on the member data 354a and the stored ball replay ball number 354d. Specifically, using the number of stored balls associated with the card ID in the member data 354a and the number of stored balls replay upper limit and the number of stored balls replayed associated with the card ID in the number of replayed balls 354d, the number of stored balls The smaller one of (the upper limit number of balls for replaying the stored ball-the number of balls for replaying the same day) is the replayable number.

  In addition, when the stored ball replay processing unit 355c updates the number of stored balls and the number of stored ball replay balls of the day, the stored ball replay upper limit management unit 355b calculates the replayable number again using the updated value. To do.

  The replay possible number calculated by the stored ball replay upper limit management unit 355b is stored in the stored ball replay ball number 354d, and is included in the stored ball replay data and transmitted to the inter-card processing machine 10.

  When the stored ball replay processing unit 355c receives a stored ball replay request including the card ID from the inter-card processing machine 10, the stored ball replay processing unit 355c updates the member data 354a by subtracting the number of stored balls associated with the card ID by the number of payout units. Then, the number of replay balls of the day associated with the card ID in the number of replay balls 354d is updated by adding the number of payout units. With this update, the stored ball replay upper limit management unit 355b calculates the replayable number again, and updates the stored ball replayed ball number 354d. The stored ball replay processing unit 355c transmits stored ball replay data including the updated number of stored balls and the replayable number to the inter-card card processing machine 10.

  Next, a data configuration according to the fourth embodiment of the member management apparatus 350 illustrated in FIG. 15 will be described. FIG. 16 is an explanatory diagram for explaining the configuration of the member data 354a, the daily storage ball replay grant number 354b, the storage ball replay history 354c, and the storage ball replay ball number 354d of the member management device 350 shown in FIG. .

  The member data 354a is data in which personal information such as a member's name, address, and password is associated with stored ball information for each game type with respect to the card ID of the member card. The member data 354a shown in FIG. 16 includes the member personal information, the 4-yen pachinko storage ball “15000”, the 2-yen pachinko storage ball “2500” and the 1-yen pachinko storage ball “00001” for the card ID “00001”. The “0” ball is associated.

  The daily storage ball replay grant number 354b is data in which the storage ball replay grant number is associated with the date. The number 354b of daily storage ball replay grants shown in FIG. 16 is “1000” on 2012/4/1 (Sunday), “2000” on 2012/4/2 (Monday), and “2000” on 2012/4/3 (Tuesday). 2000 ", 2012/4/4 (Wednesday)" 3000 ", 2012/4/5 (Thursday)" 2000 ", 2012/4/6 (Friday)" 2000 ", 2012/4/7 (Sat) “1000” and 2012/4/8 (Sunday) are associated with the number “1000” of stored ball replay grants.

  The stored-ball replay history 354c is data in which the number of stored-ball replays given for each play date is associated with the card ID and the play date and the used number within the stored-ball replay used within the range. In the stored ball replay history 354c shown in FIG. 16, for the card ID “00010”, “1000/4” balls are given as the number of stored ball replays given to “2012/4/1 (Sunday)”, of which “500” balls are stored It is used for replay, and “3000/4” balls are given to the “2012/4/4 (Wednesday)” as the number of reclaimed storage balls, of which “2500” are used for replaying the stored balls. “2012/4/5 (Thu)” is given “2000” balls as the number of re-playing of stored balls, and “0” balls are used for re-playing of stored balls, and “2012/4/8 (Sun)” “1000” balls are given as the number of savings replay grants, and “0” balls are used for savings replays. If you do not use the number of reclaimed storage balls given for each play date, you can carry over after the next day, but you can carry forward the remaining number of replayable balls to avoid infinite increase. As a finite number, it is possible to carry over on the 6th in this embodiment, but it is not possible to carry over after the 7th.

  Further, the number of replay balls 354d of the stored ball is associated with the card ID, the member calculated from the last play date of the member, the stored ball information of the member data 354a at the start of play on the last play date, and the stored ball replay history 354c. Of the current day, and the number of replay balls of that day, which is the actual number of replays of that day, and the number of possible replays. The number 354d of the reclaimed balls shown in FIG. 16 is “3500” for the 4-yen pachinko of the last replay date “2012/4/8 (Sunday)” and the upper limit number of replayed balls of the day for the card ID “00001”. 2 yen pachinko is associated with “2500”, 1 yen pachinko with “0”, the number of replayed balls of the day is 4 yen pachinko with “0”, 2 yen pachinko with “0”, 1 yen pachinko with “0” ing. The replayable number of 4 yen pachinko is “3500”, the replayable number of 2 yen pachinko is “2500”, and the replayable number of 1 yen pachinko is “0”. The granted number of replayable balls can be carried forward to 6 days, but cannot be carried forward for more than 7 days, so the number of replayable balls that was granted on 2012/4/1 (Sunday) “1000” Of the balls, the remaining 500 balls obtained by subtracting the used “500” balls are not carried over to 2012/4/8 (Sunday) and cannot be used. Therefore, the number of reclaimed balls used from the number of reclaimable balls given to 2012/4/4 (Wednesday), 2012/4/5 (Thursday) and 2012/4/8 (Sunday) on the day. The subtracted number is the upper limit of the number of replays for 2012/4/8 (day) when the number of stored balls is not taken into consideration, and this number of balls or the smaller number of balls can be replayed on that day. This is the upper limit.

  Next, a processing procedure related to the replay of stored balls by the member management apparatus 350 will be described. FIG. 17 is a flowchart showing a processing procedure related to the replay of stored balls by the member management apparatus 350. First, the member data management unit 355a determines whether or not a card insertion notification has been received from the inter-card card processing machine 10 (step S501).

  If the card insertion notification is received (step S501; Yes), the storage ball replay upper limit management unit 355b creates a record of the number of stored ball replay balls 354d corresponding to the card ID included in the card insertion notification (step S502). ).

  Specifically, today's date is written in the last play date, and the number of replay balls for that day is cleared to zero. Further, from the stored ball information and stored ball replay history 354c of the member data 354a, the upper limit number of stored balls replayed for that member is obtained and written to the upper limit number of stored balls replayed for the current number of stored ball replayed balls 354d (step S503). If the card insertion notification including the card ID has already been received on the same day, and there is a record in the number of replayed balls 354d, the existing value is used as it is.

  The stored-ball replay upper limit management unit 355b, the stored-ball replay upper-limit number calculated in step S503, the stored-ball number indicated in the member data 354a, and the stored-ball replayed ball of the day indicated in the stored-ball replayed ball number 354d. The replayable number is calculated from the number, and stored in the stored ball replayed ball number 354d (step S504).

  The member data management unit 355a generates stored ball replay data including the number of stored balls and the password number indicated in the member data 354a and the replayable number indicated in the stored ball replayed ball number 354d. It transmits to the machine 10 (step S505).

  After step S505 or when a card insertion notification has not been received (step S501; No), the stored ball replay processing unit 355c determines whether or not a stored ball replay request has been received from the inter-card card processing machine 10. (Step S506). As a result of the determination, if the storage ball replay request has not been received (step S506; No), the process is terminated.

  On the other hand, when the stored ball replay request is received (step S506; Yes), the number of stored balls associated with the card ID in the member data 354a is subtracted and updated by the number of payout units (step S507), and the stored ball replayed ball is updated. In the number 354d, the number of the replay balls of the day associated with the card ID is updated by adding the number of payout units (step S508).

  Further, the stored ball replay processing unit 355c updates the stored ball replay history 354c by adding the number of payout units to the stored ball replay usage count (step S509). In the case of adding to the stored ball replay usage number of the stored ball replay history 354c, it is added to the stored ball replay usage number of the oldest date that has a remaining playing ball replay grant number within 7 days.

  After step S509, the stored-ball replay upper limit management unit 355b calculates the replayable number again, and updates the stored-ball replayed ball number 354d (step S510). The stored ball replay processing unit 355c transmits the stored ball replay data including the updated number of stored balls and the replayable number to the inter-card card processing machine 10 (step S511), and ends the process.

  As described above, in the fourth embodiment, the stored ball information is managed in association with the card ID of the member card for identifying the player, and the number of granted replays given per day is set for each day. Since the number of replayable balls that can be used per day is limited based on the number of plays granted, the game media service that is convenient for the player is operated without losing the profit of the game shop. be able to.

  In the above-described embodiment, the case where the pachinko balls are exchanged for prizes has been described as an example. However, the game media is not limited to pachinko balls, and any game media such as medals can be exchanged for prizes. Applicable to the case.

  Further, in the above-described embodiment, the member management device has been described as including the number of balls that can be used for savings replay as the replayable number in the savings replay data. It may be included in the replay data. The number of times that the pool replay can be used is a value obtained by dividing the number of balls that can be used for the pool replay by the number of payout units of the pool replay, and the fraction is rounded down. In this way, when the number of times that the pool replay can be used is calculated and notified to the inter-card processing machine, the inter-card card processing machine has a case where the number of times that the pool re-play can be used is “1” or more. The storage ball replay operation is accepted, and when the notified number of times is “0”, the storage ball replay operation is not accepted.

  In the above-described embodiments, detailed description of the form of the card, which is a medium for associating the number of game media, is omitted, but such a card includes a magnetic card, an IC card, and the like. Further, although the “card” has been described as an example here for convenience of explanation, the present invention can also be applied to a case where a chip, a stick, a portable terminal, or the like is used in addition to such a card. In particular, when a mobile terminal with an IC chip is used as a medium, since the mobile terminal can be uniquely identified using identification information that can be obtained in a non-contact manner from the IC chip of the mobile terminal, the game medium is associated with the identification information. You can manage the number.

  Each configuration illustrated in the present embodiment is functionally schematic and does not necessarily need to be physically configured as illustrated. That is, the form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed / integrated in an arbitrary unit according to various loads or usage conditions. Can be configured.

  As described above, the stored game medium management system, the stored game medium management device, and the stored game medium management method according to the present invention operate the stored game medium service that is highly convenient for the player without losing the profits of the game store. It is suitable for realizing.

10 inter-card processing machine 10a card reader / writer 10b banknote transport unit 10e storage unit 10e1 card ID
10e2 Number of possession balls 10e3 Prepaid value 10e4, 110e4 Storage ball replay data 10f Control unit 10f1 Data management unit 10f2 Card processing unit 10f3 Storage ball replay management unit 11 Status display unit 12 Banknote insertion slot 13 Display operation unit 14 Card insertion slot 16 Card Storage unit 17 Nozzle unit 18 Count unit 19 Communication unit 20 Game machine 40 Card management device 50, 150, 250, 350 Member management device 51, 151, 251, 351 Display unit 52, 152, 252, 352 Input unit 53, 153, 253, 353 Communication unit 54, 154, 254, 354 Storage unit 54a, 154a, 254a, 354a Member data 54b, 154b Storage replay permission condition data 54c, 154c, 254d, 354d Member data Storage replay ball number 2 4b Storage ball replay upper limit by member rank 254c Storage ball replay upper limit by RF 354b Daily storage ball replay grant number 354c Storage ball replay history 55, 155, 255, 355 Control unit 55a, 155a, 255a, 355a Member data management unit 55b, 155b Storage ball replay upper limit management unit 55c, 155c, 255c, 355c Storage ball replay processing unit 90 Communication line

Claims (11)

A game storage management system that manages the number of game media acquired by a player as the number of game media stored,
Player information management means for managing the player identification information for identifying the player in association with at least the number of the game media;
The game includes a limit setting means for setting a limit condition for the replay based on information about the player for a replay in which the player uses the number of stored game media again in the game. Media management system.   The game storage medium management system according to claim 1, wherein when the information about the player is changed, the restriction setting unit changes a restriction condition for the replay based on the change.   3. The stored game medium management system according to claim 1, wherein the limit setting unit sets an upper limit number of game media for the number of stored game media that can be used for the replay within a predetermined period.   3. The storage medium management system according to claim 1, wherein the limit setting unit sets an upper limit number of replays for the number of replays that can be executed within a predetermined period. 4.   5. The storage medium management system according to claim 3, wherein the limit setting unit sets the upper limit number of game media or the upper limit number of replays based on the number of stored game media.   The restriction setting means compares the provisional value of the upper limit number of game media or the upper limit number of replays determined based on the number of stored game media with the upper limit number of game media or the maximum value of the upper limit number of replays. 6. The game medium management system according to claim 5, wherein a smaller value of the provisional value and the maximum value is set as the upper limit game medium number or the upper limit replay number of times. The player information management means further manages in association with classification information obtained by classifying the player according to a predetermined standard,
5. The storage medium management system according to claim 3, wherein the limit setting unit sets the upper limit game medium number or the upper limit replay number based on the classification information.   8. The stored game media management system according to claim 7, wherein the player information management means associates division information obtained by dividing the player based on a store visit history.   The limit setting means, when the number of stored game media or the number of replays used within the predetermined period is less than the maximum number of game media or the maximum number of replays, the number of unused game media Alternatively, the replay game count is added to the upper limit game medium count or the upper limit replay count for the next predetermined period, according to any one of claims 3 to 8. A storage medium management device that manages the number of game media acquired by a player as the number of storage media,
Player information management means for managing the player identification information for identifying the player in association with at least the number of the game media;
The game includes a limit setting means for setting a limit condition for the replay based on information about the player for a replay in which the player uses the number of stored game media again in the game. Media management device. A game storage management method for managing the number of game media acquired by a player as the number of game media,
A player information management step for managing at least the number of game media associated with player identification information for identifying a player;
The game includes a restriction setting step of setting a restriction condition for the replay based on information about the player for a replay in which the player uses the number of stored game media again for the game. Media management method.

Images