JP2014090879A - Game player management system and game player management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enhance a player's motivation for visiting a game parlor and for a game by efficiently using a visit point.SOLUTION: A on-machine card processing machine, upon an operation of the on-machine card processing machine using a member card, transmits data including a member ID to a member management device. The member management device recognizes a visit of a member by the data transmitted by the operation of the on-machine card processing spacer machine using the member card, and executes processing of granting a visit point. In the processing, as a visit frequency of a player is higher, larger visits points are granted, and as the past visit frequency is lower, smaller visit points are granted. In the calculation of the visit point, points are preferentially granted to good players by changing the number of points to be granted according to the length of the visit and a member rank, or narrowing the operation of the player for determining the visit to the game parlor, thereby enhancing the player's motivation for visiting the game parlor and for the game.

Description

  The present invention relates to a player management system and a player management method for managing information related to a player.

  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.

  In addition, as another member service, a store visit point service that motivates customers to visit stores by giving store visit points to customers who visit the store and providing privileges according to the accumulated store visit points is also known. Yes.

Japanese Patent Publication No. 2011-217846

  However, the conventional point-of-visit service provides a uniform point when visiting the store, and does not take into account the staying time, actual game situation, and past store visits. There was a problem that occurred.

  To explain this point in more detail, even if the player visits the store only for the purpose of adding visit points and does not play games, the visit points are the same for those who visit frequently and play for a long time. In fact, the point of visit was not fully functioning as a motivation for the player.

  The present invention has been made in order to solve the above-described problems of the prior art, and is a player management capable of efficiently operating store visit points and strengthening the motivation of players to visit the store and games. It is an object to provide a system and a player management method.

In order to solve the above-mentioned problems and achieve the object, the present invention is a player management system for managing information related to a player, a detection means for detecting a visitor of the player, and a store detected by the detection means Determined by specifying means for identifying the player who has been played, grant privilege determining means for determining a store visit privilege to be given to the player based on information relating to the player specified by the specifying means, and determining the grant privilege determining means It is characterized by comprising a privilege granting means for performing the grant of the visited store privilege.

  Further, the present invention, in the above invention, further comprises a store history management means for managing the visit history of the player, the grant privilege determining means determines the store privilege to be granted to the player based on the store history It is characterized by doing.

  Further, in the present invention, in the above invention, the grant privilege determining means grants a store visit privilege determined based on a determination period for determining a store visit privilege to be given to the player and a store visit history within the determination period. The grant period to be set is individually set.

  Moreover, the present invention is characterized in that, in the above-mentioned invention, the grant privilege determining means adds a store visit privilege to be granted to the player according to a stay time of the player.

  Further, in the present invention according to the above-mentioned invention, the grant privilege determining means grants to the player a grant visit privilege in a time zone in which the player stays among grant grant privileges determined corresponding to a time zone. When the player stays across a plurality of time zones, the store is provided with the maximum value of the plurality of granted store visit privileges corresponding to the plurality of time zones to the player. It is determined as a privilege.

  Moreover, the present invention is characterized in that, in the above invention, the store visit privilege granting unit executes the grant of the store visit privilege on condition that a predetermined operation related to a game is performed by the player.

  Further, the present invention is characterized in that, in the above-mentioned invention, an expiration date managing means for setting an expiration date for the store visit privilege granted to the player is further provided.

  Moreover, the present invention is characterized in that, in the above-mentioned invention, the expiration date management means sets an expiration date of a store visit privilege to be given to the player based on information on the player.

  Further, the present invention is a player management method for managing information relating to a player, a detection step of detecting a visitor of the player, a specifying step of specifying a player from which the store was detected by the detection step, Based on the information related to the player specified in the specifying step, a privilege grant step for determining a store privilege to be granted to the player and a privilege grant for executing the store privilege determined in the grant privilege determining step And a step.

  According to the present invention, a visitor's visit is detected, the detected player is identified, and the store visit privilege to be given to the player is determined based on the information related to the identified player, thereby being determined Since the provision of the store visit privilege is executed, it is possible to efficiently operate the store visit privilege and enhance the motivation of the visitor to the store and the game.

FIG. 1 is an explanatory diagram for explaining the concept of a player management method in the gaming 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 block diagram illustrating an internal configuration according to the first embodiment of the member management apparatus illustrated in FIG. 1. FIG. 4 is an explanatory diagram for explaining the data structure related to member data and store visit point assignment of the member management apparatus shown in FIG. FIG. 5 is a flowchart illustrating a processing procedure related to store visit point grant by the member management apparatus according to the first embodiment. FIG. 6 is an explanatory diagram for explaining the concept of the player management method in the gaming system according to the second embodiment. FIG. 7 is a block diagram illustrating an internal configuration according to the second embodiment of the member management apparatus illustrated in FIG. 6. FIG. 8 is an explanatory diagram for explaining the data structure related to member data and store visit point assignment of the member management apparatus shown in FIG. FIG. 9 is a flowchart illustrating a processing procedure related to store visit point grant by the member management apparatus according to the second embodiment. FIG. 10 is an explanatory diagram for explaining the concept of the player management method in the gaming system according to the third embodiment. FIG. 11 is a block diagram illustrating an internal configuration according to the third embodiment of the member management apparatus illustrated in FIG. FIG. 12 is an explanatory diagram for explaining the data structure related to member data and store visit point assignment of the member management apparatus shown in FIG. FIG. 13 is a flowchart illustrating a processing procedure related to store visit point grant by the member management apparatus according to the third embodiment. FIG. 14 is an explanatory diagram for explaining the concept of the player management method in the gaming system according to the fourth embodiment. FIG. 15 is a block diagram illustrating an internal configuration according to the fourth embodiment of the member management apparatus illustrated in FIG. 14. FIG. 16 is an explanatory diagram for explaining the data structure relating to member data and store point grant of the member management apparatus shown in FIG. FIG. 17 is a flowchart illustrating a processing procedure related to store visit point grant by the member management apparatus according to the fourth embodiment.

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

  First, the concept of the player management system and the player management method according to the first embodiment will be described. FIG. 1 is an explanatory diagram for explaining the concept of a player 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 processing machine 10, a gaming machine 20, and a member management device 50.

  When a player visits the amusement store and plays a game on the gaming machine 20, when the member card is inserted into the inter-card card processing machine 10, the inter-card card processing machine 10 uses the member ID stored in the membership card. The data including the member ID is read and transmitted to the member management apparatus 50. In addition, in the state where the membership card is inserted into the inter-card card processing machine 10, even when a deposit operation, a lending operation, a holding ball re-play operation, a storage ball re-play operation, a counting operation and a card removal operation are performed, The card processor 10 transmits data including the member ID of the inserted member card to the member management apparatus 50.

  The member management apparatus 50 that has received the member ID determines that the player corresponding to the member ID has visited the store by receiving the member ID. In addition, the process of determining whether or not to give store visit points is performed with reference to the time when the member ID is received, the point grant reference data, and the member point data.

  Specifically, the conditions for giving store points are set in the point grant reference data. There are basic points and additional points for points to visit, and basic points are granted by visiting the basic point grant time zone set in the point grant standard data, and after the basic points are granted, the game can be played up to a specific time zone. If it continues, additional points will be awarded separately from the basic points.

  From the time when the member ID is received and the point grant reference data, it is determined whether or not the time when the member ID is received falls within the basic point or additional point grant time zone. If the time when the member ID is received does not belong to any time zone in which basic points or additional points are given, points are not given when the member ID is received. If the time at which the member ID is received is included in any of the basic point grant times, refer to the member point data, and if there is no history of basic points given today, setting of point grant reference data The basic points are given as follows. Even if the time when the member ID is received is included in any of the basic point grant times, if there is a history of basic points given today with reference to the member point data, the basic points will be given. Absent.

  If the time at which the member ID is received is included in any of the time zones for adding additional points, refer to the member point data and if there is no history of basic points given today, the additional points will be given. Do not do. In addition, when the time when the member ID is received is included in any of the time zones for adding additional points, when the member point data is referenced, there is a history of basic points for the additional points, and When there is no grant history, the additional points are awarded according to the setting of the point grant reference data. In addition, when the time when the member ID is received is included in any of the time zones for adding additional points, when the member point data is referenced, there is a history of basic points for the additional points, and If there is also a grant history, the additional points are not given.

  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 data relating to 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 member card ID from the gift management device 60, the member management device 50 notifies the gift management device 60 of the balance of the savings 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 the card ID of the 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 of the card 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 internal configuration of the member management apparatus 50 shown in FIG. 1 will be described. FIG. 3 is a block diagram illustrating an internal configuration according to the first embodiment of the member management apparatus 50 illustrated in FIG. 1. As shown in FIG. 3, the member management device 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 non-volatile memory, and stores member data 54a, point grant reference data 54b, and member point data 54c. The member data 54a stores personal information such as a member's name, address, telephone number, and identification ID of a mobile phone terminal, and storage information that is the balance of the storage account for each game type in association with the member ID. . The point grant reference data 54b is a set value for conditions for granting store visit points, and the member point data 54c is provided with basic point and additional point grant date / time, divided into store visit points into basic points and additional points. The number of basic points and the number of additional points are stored in association with the member ID.

  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 member visit determination unit 55b, and a point management 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 member visit determination unit 55b and the point management 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 for notifying the member data 54a. When the card data is received from the inter-card card processing machine 10 or the gift management device 60, the member data management unit 55a stores each rate corresponding to the card ID. Notify your account balance. 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 member visit determination unit 55b is a processing unit that determines the visit of a player. Specifically, the notification is made by inserting / removing the membership card in the inter-card processing machine 10, the deposit operation, the lending operation, the holding ball replay operation, the storage ball replay operation, and the counting operation with the membership card inserted. When the information including the member ID is received, it is determined that the player corresponding to the member ID has visited the store.

  When the member visit determination unit 55b determines the visit of the player, the point management unit 55c determines whether or not points have been granted and the number of granted points from the visitor visit date / time, the point grant reference data 54b, and the member point data 54c. When the points are given and added, the added points are added to the member point data 54c separately for the basic points and the additional points, and the final point grant date / Record the time.

  Next, a data configuration according to the first embodiment of the member management apparatus 50 illustrated in FIG. 3 will be described. FIG. 4 is an explanatory diagram for explaining data related to membership of the member management apparatus 50 shown in FIG.

  The member data 54a is made up of personal information such as a member's name and address and storage information for each game type in association with the member ID. The member data 54a shown in FIG. 4 has a member ID “00001”. The member personal information is associated with data of a 4-yen pachinko “15000” ball, a 2-yen pachinko “2500” ball, and a 1-yen pachinko “0” ball.

  The point granting reference data 54b stores conditions for granting points of visits by players. There are basic points and additional points for points to visit, and basic points are granted by visiting the base point granting time zone set in the point granting standard data 54b, and after the basic points are granted, the game is played in a specific time zone. When continuing until (the point granting time zone of additional point 1 and the point granting time zone of additional point 2), additional points are awarded separately from the basic points. A plurality of basic point grant time zones and grant points can be set, and a point grant time zone and the number of additional points can be set as additional points 1 and 2 for each basic point.

  In the point grant reference data 54b shown in FIG. 4, three basic point addition time zones / number of grant points are set, and the basic points in the time zone “10: 0 to 12:00” are “1”, “ The basic point in the time zone from 14:00 to 16:00 is “1”, and the basic point in the time zone from “18:00 to 19:00” is “1”. In addition, with respect to the first basic point granting time zone “10:00 to 12:00”, the point granting time zone of the additional point 1 is “18:00 to 19:00”, the additional point number “3”, and the additional point 2 The additional point number “5” is set in “21:00 to 22:00” in the point grant time zone. In addition, for the second basic point granting time zone “14:00 to 16:00”, the point granting time zone of the additional point 1 is “18: 0 to 19:00” and the additional point number is “2” and the additional point 2 The additional point number “3” is set in “21:00 to 22:00” in the point grant time zone. In addition, the additional point number “2” is set at “21:00 to 22:00” in the point granting time zone of the additional point 1 with respect to the third basic point granting time zone “18:00 to 19:00” Yes.

  The member point data 54c includes the number of store visit points granted, the date and time when the last basic point was granted, and the last additional point grant time when the last granted point was an additional point. Is associated with. The date / time given at the end of the basic point or additional point is inserted into the inter-card processing machine 10 during the point granting time period of the basic point or additional point set in the point granting reference data 54b. This is data used to determine that points are given only once in the same time period by storing the points given in the same time period when the operation indicating the store visit is performed a plurality of times. .

  The member point data 54c shown in FIG. 4 includes a member ID “00001”, a final basic point grant date “2012/4/1”, a final basic point grant time “11:00”, and a final additional point grant time. “18:30” and point “35” are associated with each other.

  Next, a processing procedure related to store visit point grant by the member management apparatus 50 will be described. FIG. 5 is a flowchart illustrating a processing procedure related to store visit point grant by the member management apparatus 50 according to the first embodiment. First, the member visit determination unit 55b determines whether or not there is a store visit event of the player (step S101). Specifically, a member card insertion / extraction in the inter-card card processor 10 of a player, a deposit operation, a ball lending operation, a holding ball replay operation, a stored ball replay operation, and a counting operation with the member card inserted. The reception of information including the member ID notified by is a store visit event, and these store visit events are monitored, and if no data is received (step S101; No), the process ends. When any data of the store visit event is received (step S101; Yes), data associated with the member ID included in the store visit event is searched from the member point data 54c (step S102).

  The date of granting the last basic point of the member associated with the searched member ID is referred, and if it matches the today's date (step S103; Yes), the basic point has already been given today and added. The process proceeds to a process for determining whether or not the point is to be granted (step S106), and if the date of the last basic point grant does not coincide with today's date (step S103; No), no basic points are given today. The process proceeds to determination processing (step S104) as to whether or not the basic point is to be granted.

  If today's basic points have not been granted yet (step S103; No), whether or not the store visit event reception time is included in any of the basic point grant time zones set in the point grant reference data 54b. (Step S104), and if it is not included in any of the basic point granting time zones set in the point granting reference data 54b (step S104; No), the store visit points are not given and the process ends. . In addition, when included in any basic point granting time zone set in the point granting reference data 54b (step S104; Yes), the basic point granting of the point granting reference data 54b is performed as the basic point granting process. The number of granted points set in the time zone is added to the points associated with the member ID in the member point data 54c, and at the date / time of the last basic point associated with the member ID in the member point data 54c. Then, the date of today and the event reception time of the store event are written, and the time of granting the last additional point is cleared (step S105).

  If today's basic points have already been granted (step S103; Yes), which basic point grant time zone of the point grant reference data 54b corresponds to from the time of last basic point grant of the member point data 54c. Then, it is determined whether or not the visit event reception time is included in the point grant time zone of the additional point 1 or the additional point 2 associated with the basic point grant time zone (step S106). If the visit event reception time is not included in the point grant time zone of the additional point 1 or the additional point 2 associated with the basic point grant time zone (step S106; No), it is determined that no additional points are given and processing is performed. End.

  If the visit event reception time is included in the point granting time zone of the additional point 1 or the additional point 2 associated with the basic point granting time zone (step S106; Yes), the additional points of the point granting time zone are subsequently continued. Is determined (step S107). Specifically, with reference to the time of granting the last additional point in the member point data 54c, if it is the point granting time zone of the additional point 1 or the additional point 2 that is the same as the time of visiting the store event (step S107; Yes), it is added It is determined that no points are given, and the process ends. With reference to the time of granting the last additional point of the member point data 54c, if it is not the point granting time zone of the additional point 1 or the additional point 2 that is the same as the time of arrival of the store event (step S107; No), the addition of the additional point The number of points is added to the point associated with the member ID in the member point data 54c, and the store visit event reception time is written at the time of the last additional point associated with the member ID in the member point data 54c (step) S108).

  As described above, according to the processing procedure shown in FIG. 5, in addition to the basic points being awarded based on the first visit event, if the second and subsequent visit events occur within the additional point grant time, Additional points can be awarded.

  In addition, in the processing procedure shown in FIG. 5, it is determined whether or not to give additional points by using the occurrence of a store visit event as a trigger for adding additional points. The determination may be made at the end of the point grant time period.

  Specifically, the event history of store visits is maintained, and each member determines whether or not a store visit event has occurred within the granted time zone at the end of the added time zone, and a store visit event occurs. Additional points will be given to existing members.

  Moreover, even if it is a member, it does not always use a membership card and may use a general card. For example, it is possible to use a membership card for the purpose of earning points to visit or using a stored ball after a member first deposits and playing a game. If the payment is made, the prepaid value corresponding to the deposit amount is managed in association with the general card.

  As in this case, if a game is played for a long time before the visit event occurs after reading the membership card, it is preferable to give a visit point to the game before the membership card is read. . Therefore, when it is possible to associate a game with a general card with a member card, such as when a member card is read during a game with a general card, additional points for the game time played using the general card are given. Calculate and grant.

  Not only the membership card but also a mobile terminal or the like can be used in the same manner when a mobile terminal or the like is used instead of the membership card. In addition, when both the mobile terminal and the membership card are used, if the store visit points are individually given to the same member, the store members will be given duplicate points to the same member, so the member ID associated with the mobile terminal And the member ID associated with the member card are used to avoid giving duplicate store visit points for the same member ID. Specifically, if the associated member IDs are the same, regardless of whether the card is a member card or a mobile terminal, store point is given as if the same person continued to play.

  As described above, in the first embodiment, the member's personal information, stored ball information, and store visit points are managed in association with the member ID for identifying the player, and not only the points are given at the time of visit, but also continued. When the game is continued, additional store visit points are added, so that the store visit points can be efficiently used, and the motivation of the visitor to the store and the game can be enhanced.

  Further, in the above-described first embodiment, in the basic point granting time zone set in the point granting reference data 54b and the point granting time zone of additional points, if the shop is in each time zone, the total of the corresponding points However, the maximum value of each point may be assigned.

  Further, in the above-described first embodiment, the case where an additional store point is given according to the stay time of the player has been described. However, the expiration date of the basic store point is extended according to the stay time of the player. You may comprise. In this case, the number of visit points that a player can obtain in one day is fixed (for example, one point per day), but the expiration date of the visit point is extended by staying for a long time, so that the player's visit to the store and the motivation for the game The sticking can be strengthened. Moreover, it is good also as performing both an additional store visit point provision and the extension of an expiration date according to stay time.

  By the way, in the above-described first embodiment, the visitor's visit and the motivation to the game are strengthened by giving the visit point according to the length of the in-store time, but the present invention is limited to this. It is also possible to enhance the motivation for the visitor to the store and the game by changing the store visit point given according to the past visit frequency of the member. Therefore, in the second embodiment, an embodiment will be described in which the store visit points to be given are changed according to the past store visit frequency of the member.

  First, the concept of the player management system and the player management method according to the second embodiment will be described. FIG. 6 is an explanatory diagram for explaining the concept of the player management method in the gaming system according to the second embodiment. The gaming system shown in FIG. 6 has a configuration including an inter-card card processing machine 10, a gaming machine 20, and a member management device 150.

  When a player visits the amusement store and plays a game on the gaming machine 20, when the member card is inserted into the inter-card card processing machine 10, the inter-card card processing machine 10 uses the member ID stored in the membership card. The data including the member ID is read and transmitted to the member management apparatus 150. In addition, in the state where the membership card is inserted into the inter-card card processing machine 10, even when a deposit operation, a lending operation, a holding ball re-play operation, a storage ball re-play operation, a counting operation and a card removal operation are performed, The card processor 10 transmits data including the member ID of the inserted member card to the member management apparatus 150.

  The member management device 150 that has received the member ID determines that the player corresponding to the member ID has visited the store by receiving the member ID, and updates the number of visits to the store frequency data held by the member management device 150. To do. Next, store visit points are calculated. Specifically, the visit frequency of the player is obtained by referring to the store visit frequency data, and the visit point corresponding to the visit frequency of the player is obtained by referring to the point grant condition data. The point granting condition data is set such that the higher the store visit frequency, the larger the store visit points to be given, thereby strengthening the motivation for the visitor to visit the store. The obtained store visit points are added to the points stored in association with the member ID of the player in the member point data managed in the member management apparatus.

  Next, the internal configuration of the member management apparatus 150 shown in FIG. 6 will be described. FIG. 7 is a block diagram illustrating an internal configuration according to the second embodiment of the member management apparatus 150 illustrated in FIG. 6. As shown in FIG. 7, the member management apparatus 150 is connected to the display unit 151 and the 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 nonvolatile memory, and stores member data 154a, reference period setting data 154b, store visit frequency data 154c, point grant condition data 154d, and member point data 154e. The member data 154a stores personal information such as a member's name, address, telephone number, and identification ID of a mobile phone terminal, and storage information that is the balance of the storage account for each game type in association with the member ID. .

  The second embodiment is characterized in that the number of points given at one store visit point can be changed according to the store visit frequency in the past, and the period for measuring the store visit frequency can be set, and the reference period setting data 154b includes Stores the setting information of the period for measuring the store visit frequency. In the present embodiment, the period defined by the reference period setting data 154b is a period for measuring the store visit frequency and is also an effective period of the measured store visit frequency.

  The store visit frequency data 154c stores the number of store visits in the period for measuring the store visit frequency set in the reference period setting data 154b. The point grant condition data 154d holds information on the number of store visit points given for each store visit frequency. The member point data 154e stores a total value of store visit points given in association with the member ID.

  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 store visit frequency management unit 155b, a member visit determination unit 155c, and a point management unit 155d. 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 store visit frequency management unit 155b, the member visit determination unit 155c, and the point management unit 155d 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 ID is received from the inter-card card processing machine 10 or the prize management device 60, the member data management unit 155a stores each rate corresponding to the card ID. Notify your account balance. 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 store visit frequency management unit 155b is a processing unit that manages store visit frequency data 154c. Specifically, it manages the number of store visits in the previous period (previous week, previous month, previous year, etc.), which is a condition for granting store points, and the number of store visits this term (this week, this month, this year, etc.). In addition, when switching from the previous term to this term, the number of visits this term is copied to the number of visits in the previous term and the number of visits this term is cleared to zero.

  The member visit determination unit 155c is a processing unit that determines the visit of a player. Specifically, the notification is made by inserting / removing the membership card in the inter-card processing machine 10, the deposit operation, the lending operation, the holding ball replay operation, the storage ball replay operation, and the counting operation with the membership card inserted. When the information including the member ID is received, it is determined that the player corresponding to the member ID has visited the store.

  When the member visit determination unit 155c determines the visit of the player, the point management unit 155d searches the store visit frequency data 154c for the previous store visit frequency of the player and refers to the point grant condition data 154d. The store visit point to be given at the store visit frequency is determined, and the determined store visit point is added to the player point of the member point data 154e.

  Next, a data configuration according to the second embodiment of the member management apparatus 150 illustrated in FIG. 7 will be described. FIG. 8 is an explanatory diagram for explaining data relating to membership of the member management apparatus 150 shown in FIG.

  The member data 154a is made up of personal information such as a member's name and address in association with the member ID, and storage information for each game type. The member data 154a shown in FIG. 8 has a member ID “00001”. The member personal information is associated with data of a 4-yen pachinko “15000” ball, a 2-yen pachinko “2500” ball, and a 1-yen pachinko “0” ball.

  The reference period setting data 154b stores setting information of a period for measuring the store visit frequency, and this period is also an effective period of the measured store visit frequency. In the reference period setting data 154b shown in FIG. 8, "2" indicating the month is set as the reference period unit, "1" is set as the reference period number, and "1" is set as the period start date. The start date is the first day of every month and the end date is the last day of the month. The visit frequency measured in this month is from the first day of the next month to the last day of the next month. It means that there is.

  The store visit frequency data 154c stores the number of visits of the previous period, the number of visits of the current period, and the last visit date associated with the member ID when the content set in the reference period setting data 154b is one period. . The number of visits is held to realize that the number of visits is counted only once regardless of the number of visits per day. In the store visit frequency data 154c shown in FIG. 8, the number of visits of the previous period “7”, the number of visits of the current period “3”, and the last visit date “2012/4/5” are associated with the member ID “00001”.

  In the point grant condition data 154d, the number of store visit points given in one visit is associated with the store visit frequency of the previous period. The point granting condition data 154d shown in FIG. 8 includes the number of granted points “1” at the previous period visit frequency “0 day”, the number of granted points “2” at the previous period visit frequency “1-5 days”, and the previous period visit frequency. The number of granted points “3” is associated with “6th to 20th”, and the number of granted points “5” is associated with the previous-period store visit frequency “21st”.

  In the member point data 154e, the last point grant date and points are associated with the member ID. The last point grant date is held to realize that the store visit points are granted only once a day. In the member point data 154e shown in FIG. 8, the member ID “00001” is associated with the last point grant date “2012/4/3” and the point “35”.

  Next, a processing procedure related to store visit point grant by the member management apparatus 150 will be described. FIG. 9 is a flowchart illustrating a processing procedure related to store visit point grant by the member management apparatus 150 according to the second embodiment. First, the member visit determination unit 155c determines whether or not there is a store visit event of the player (step S201). Specifically, a member card insertion / extraction in the inter-card card processor 10 of a player, a deposit operation, a ball lending operation, a holding ball replay operation, a stored ball replay operation, and a counting operation with the member card inserted. The reception of information including the member ID notified by is a store visit event, and these store visit events are monitored, and if no data has been received (step S201; No), the process ends. When any data of the store visit event is received (step S201; Yes), the store visit frequency management unit 155b refers to the last visit date of the store visit frequency data 154c to determine whether there is a store visit history for today. (Step S202).

  When today's store visit history exists (step S202; Yes), the processing ends from the determination that the store visit history update for the current day and store point assignment have already been performed. If there is no visit history of today (step S202; No), the store visit frequency management unit 155b increments the store visit frequency data 154c by the number of visits in this period, and the last visit date of the store visit frequency data 154c is set as today's date. Update (step S203).

  Next, the point management unit 155d refers to the store visit frequency data 154c, obtains the number of visits of the previous period of the player who visited the store, and calculates store visit points to be given from the store visit number and the point grant condition data 154d (step S204). . Further, the point management unit 155d adds the calculated store visit point to the point data associated with the player in the member point data 154e, and updates the last point grant date associated with the player to today's date (step S205). ).

  As described above, the member management device 150 changes the point of visit to be given according to the store visit result. However, if the store visit result is notified to the player, the motivation of the player to visit the store is further increased. It can be done effectively.

  For example, if a notification is made that “the number of visits last month is 7 days, the number of visits this month is 3 points a day”, the player can recognize that the preferential treatment based on the number of visits last month has been received. Also, the number of visits this month is 3 days. Next month's visit points are 2 points. Next 3 days visit, next month's visit points will be 3 points. Motivate to improve performance.

  This notification to the player may be displayed on the display unit of the inter-card card processing machine 10 or the gaming machine 20, or may be printed on a counting receipt or the like. Moreover, it is good also as notifying with respect to a player's portable terminal.

  In addition, it is possible to motivate the store visit by generating ranking information of the number of store visit points acquired at the game store and notifying how many store visit points the other player has acquired. The ranking information may be displayed together with a ranking display name designated by the player. The notification of the ranking information may be performed by transmitting the ranking information itself to the mobile terminal, but may be performed by transmitting a site URL on the Internet on which the ranking information is posted.

  As described above, in the second embodiment, in addition to the member ID for identifying the player, the store visit frequency is managed in addition to the member's personal information, accumulated ball information, and store visit points, Since it is configured to give a lot of visit points per visit and a low number of visit points per visit, the store visit points are efficiently operated, and the visitor's visit and the motivation for the game The sticking can be strengthened.

  By the way, in the above-described first and second embodiments, the player visits the store by inserting / removing the member card in the player's inter-card processing machine 10, the deposit operation or the ball lending operation with the member card inserted, Although it was determined by receiving information including the member ID notified by the holding ball replay operation, the storage ball replay operation, and the counting operation, the present invention is not limited to this, and only the insertion / extraction of the member card is performed. It is possible to enhance the motivation to visit a good player and to play a game by avoiding giving points to the player for the purpose of earning points. Therefore, in this third embodiment, an embodiment will be described in which an event for judging a visit of a player is narrowed down to an event meaning a substantial visit.

  First, the concept of the player management system and the player management method according to the third embodiment will be described. FIG. 10 is an explanatory diagram for explaining the concept of the player management method in the gaming system according to the third embodiment. The gaming system shown in FIG. 10 has a configuration including an inter-card card processing machine 10, a gaming machine 20, and a member management device 250.

  When a player visits the amusement store and plays a game on the gaming machine 20, when the member card is inserted into the inter-card card processing machine 10, the inter-card card processing machine 10 uses the member ID stored in the membership card. The data including the member ID is read and transmitted to the member management apparatus 250. In addition, in the state where the membership card is inserted into the inter-card card processing machine 10, even when a deposit operation, a lending operation, a holding ball re-play operation, a storage ball re-play operation, a counting operation and a card removal operation are performed, The card processor 10 transmits data including the member ID of the inserted member card to the member management apparatus 250.

  Receiving the data including the member ID, the member management apparatus 250 determines that the player corresponding to the member ID has visited the store by receiving the member ID, and counts up the number of visits to the store. Further, it is determined whether or not the store point is given based on what operation the player ID includes. The conditions for granting store visit points are registered in the point grant condition data, and in the point grant condition data, the number of store visit points given in association with the operation of the player is set. If the point grant condition data indicates a player operation with a grant point of 1, 1 point of store visit is granted to the player.

  Next, the internal configuration of the member management apparatus 250 shown in FIG. 11 will be described. FIG. 11 is a block diagram illustrating an internal configuration according to the third embodiment of the member management apparatus 250 illustrated in FIG. As shown in FIG. 11, the member management device 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 nonvolatile memory, and stores member data 254a, point grant condition data 254b, and member point data 254c. The member data 254a stores personal information such as a member's name, address, telephone number, and mobile phone terminal identification ID, and stored ball information that is the balance of the stored ball account for each game type in association with the member ID. .

  The point granting condition data 254b holds the number of store visit points to be given in association with the operation performed by the player in the inter-card card processing machine 10. Even when the player's visit is recognized by transmitting the data including the member ID to the member management device 250 by the operation performed by the player in the inter-card processing machine 10 by setting the point grant condition data 254b. When the number of store visit points associated with the corresponding operation in the point grant condition data 254b is 0, store visit points are not granted. The member point data 254c stores the total value of points given, the last point grant date, the number of visits to the store, and the last visit date in association with the member ID.

  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 member visit determination unit 255b, and a point management 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 member visit determination unit 255b and the point management unit 255c are caused to execute corresponding processes.

  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 for notifying the member data 254a. When the card ID is received from the inter-card card processing machine 10 or the prize management device 60, the member data management unit 255a stores each rate corresponding to the card ID. Notify your account balance. 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 member visit determination unit 255b is a processing unit that determines the visit of a player. Specifically, the notification is made by inserting / removing the membership card in the inter-card processing machine 10, the deposit operation, the lending operation, the holding ball replay operation, the storage ball replay operation, and the counting operation with the membership card inserted. When the information including the member ID is received, it is determined that the player corresponding to the member ID has visited the store.

  The point management unit 255c identifies what operation is performed in the inter-card card processing machine 10 from the data including the member ID received from the inter-card card processing machine 10 that has determined the visit, and the point granting condition The data 254b is referred to determine whether or not store visit points need to be given. If it is determined that store visit points need to be given, store visit points are added to the points associated with the player in the member point data 254c.

  Next, a data configuration according to the third embodiment of the member management apparatus 250 illustrated in FIG. 11 will be described. FIG. 12 is an explanatory diagram for explaining data related to membership of the member management apparatus 250 shown in FIG.

  The member data 254a is made up of personal information such as a member's name and address and storage information for each game type in association with the member ID. The member data 254a shown in FIG. 12 has a member ID “00001”. The member personal information is associated with data of a 4-yen pachinko “15000” ball, a 2-yen pachinko “2500” ball, and a 1-yen pachinko “0” ball.

  The point granting condition data 254b holds the number of store visit points to be given in association with the operation performed by the player in the inter-card card processing machine 10. The point granting condition data 254b shown in FIG. 12 includes the number of granted points “0” associated with the player operation “insert membership card”, the number of granted points “0” associated with the player operation “extract membership card”, the player operation The number of granted points “1” in association with the “ball operation”, the number of granted points “1” in association with the player operation “payment operation”, and the number of granted points “1” in association with the player operation “replay operation of stored balls” The number of granted points “1” is stored in association with the player operation “mochitama replay operation”.

  The member point data 254c holds the last point grant date, the last visit date, the points, and the number of visits in association with the member ID. In the member point data 254c shown in FIG. 12, the member ID is “00001”, the last point grant date “2012/4/1”, the last visit date “2012/4/5”, the point “35”, and the number of visits “37”. Is associated.

  Next, a processing procedure related to store visit point grant by the member management apparatus 250 will be described. FIG. 13 is a flowchart illustrating a processing procedure related to store visit point granting by the member management apparatus 250 according to the third embodiment. First, the member visit determination unit 255b determines whether or not there is a store visit event of the player (step S301). Specifically, a member card insertion / extraction in the inter-card card processor 10 of a player, a deposit operation, a ball lending operation, a holding ball replay operation, a stored ball replay operation, and a counting operation with the member card inserted. The reception of information including the member ID notified by the above is a store visit event, and these store visit events are monitored, and if no data is received (step S301; No), the process ends. When any data of the store visit event is received (step S301; Yes), the presence / absence of the store visit history of the day is determined by comparing the last visit date of the player in the member point data 254c with the today's date. (Step S302). If there is no visit history for today (step S302; No), the number of visits of the player in the member point data 254c is counted up, and the last visit date is updated to today's date (step S303). If the store visit history of the day is already present (step S302; Yes), the store count update processing (step S303) is skipped.

  The point management unit 255c identifies what operation is performed in the inter-card card processing machine 10 from the data including the member ID received from the inter-card card processing machine 10 that has determined the visit, and the point granting condition It is determined whether or not it is necessary to give a store point with reference to the data 254b (step S304). When it is determined that the operation is not a point grant target (step S304; No), the process ends without performing the process related to point grant. When it is determined that the operation is a point grant target (step S304; Yes), By comparing the last point grant date of the member point data 254c with today's date, it is determined whether or not today's points have been granted (step S305). If it is determined that the points have been given today (step S305; Yes), the process ends without performing the process related to the point of visiting. When it is determined that the points are not given today (step S305; No), the store points are added to the player's points in the member point data 254c, and the last point grant date is updated with the current date (step). S306).

  As described above, in the third embodiment, points are obtained only by inserting / removing a member card by managing the member's personal information, stored ball information and store visit points in association with the member ID for identifying the player. Since it is configured to avoid giving points to the player for the purpose of, the store visit points can be efficiently used to enhance the motivation of the player to visit the store and the game.

  By the way, in the above-mentioned Example 1, Example 2, and Example 3, the expiration date of the given store visit point was uniformly unlimited, but the present invention is not limited to this, and the store visit point for each member rank It is possible to set a bonus point with an expiration date according to the attributes of the player by limiting the grant period, and to set a bonus point with an expiration date in the off season / off season of the amusement store By making it possible, it is possible to enhance the motivation for the visitor of the player and the game. Therefore, in the fourth embodiment, an explanation will be given of an embodiment in which the expiration date of the store visit point can be set for each member rank, and the attribute of the player and the bonus point in the idle season / off season of the game store are set.

  First, the concept of the player management system and the player management method according to the fourth embodiment will be described. FIG. 14 is an explanatory diagram for explaining the concept of the player management method in the gaming system according to the fourth embodiment. The gaming system shown in FIG. 14 has a configuration including the inter-card card processing machine 10, the gaming machine 20, and a member management device 350.

  When a player visits the amusement store and plays a game on the gaming machine 20, when the member card is inserted into the inter-card card processing machine 10, the inter-card card processing machine 10 uses the member ID stored in the membership card. The data including the member ID is read and transmitted to the member management apparatus 350. In addition, in the state where the membership card is inserted into the inter-card card processing machine 10, even when a deposit operation, a lending operation, a holding ball re-play operation, a storage ball re-play operation, a counting operation and a card removal operation are performed, The card processor 10 transmits data including the member ID of the inserted member card to the member management apparatus 350.

  Receiving the data including the member ID, the member management apparatus 350 recognizes that the player corresponding to the member ID has visited the store by receiving the member ID, and determines whether or not it is necessary to give the store points. In the fourth embodiment, the store visit points to be given are composed of normal store visit points and bonus points. The conditions related to the usual store visit points are set in the rank-specific store point grant condition data, and are composed of the number of points given per visit to each store rank and the validity period of the points. Bonus points are set in bonus point granting condition data, and are composed of conditions for granting bonus points, the number of points to be given, and the valid period of the points.

  When the member management device 350 recognizes the visit of the player, the member management device 350 first performs a process of granting a normal visit point. Specifically, the number of store visit points to be given and the expiration date of the points are added as member grant points to the member point data from the member rank of the player who has recognized the visit and the rank-specific visit point grant condition data.

  Next, with reference to the bonus point granting condition data, it is determined whether or not the point granting conditions set for the plurality of point granting conditions are met. The number of grant points set in the grant condition data and the expiration date of the points are added as the grant points of the player to the member point data. This is performed for all point grant conditions set in the bonus point grant condition data.

  With regard to member point data, not only the expiration date setting differs for each granted point, but the point acquisition date also differs, so the points of the visiting point awarding condition data by rank and bonus point awarding condition data at the time of addition to the member point data The expiration date of each point is calculated from the expiration date and today's date, and the points given in combination with the expiration date are managed. That is, the member point data includes a plurality of records for one member ID, and holds information on the number of granted points and the point expiration date for each given point.

  Next, the internal configuration of the member management apparatus 350 shown in FIG. 14 will be described. FIG. 15 is a block diagram illustrating an internal configuration according to the fourth embodiment of the member management apparatus 350 illustrated in FIG. As shown in FIG. 15, 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, rank-based visit point grant condition data 354b, bonus point grant condition data 354c, and member point data 354d. The member data 354a associates the member rank, personal information such as the member's name, address, telephone number, identification ID of the mobile phone terminal, and the stored ball information which is the balance of the stored account for each game type with the member ID. I remember it.

  The rank-specific visit point grant condition data 354b is obtained by setting the number of normal visit point grant points granted and the expiration date of the grant points for the member rank for each member stored in the member data 354a. is there.

  The bonus point granting condition data 354c includes bonus point granting conditions and the number of points granted according to the attributes of the player, the time of visiting the store, etc. The expiration date of the grant points is set.

  The member point data 354d stores normal store visit points and bonus points given to the player, and stores the expiration date and the number of points given for each given point.

  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 member visit determination unit 355b, and a point management 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 member visit determination unit 355b and the point management unit 355c execute the 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 that notifies the member data 354a. When the card ID is received from the inter-card card processing machine 10 or the prize management device 60, the member data management unit 355a stores each rate corresponding to the card ID. Notify your account balance. 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 member visit determination unit 355b is a processing unit that determines the visit of a player. Specifically, the notification is made by inserting / removing the membership card in the inter-card processing machine 10, the deposit operation, the lending operation, the holding ball replay operation, the storage ball replay operation, and the counting operation with the membership card inserted. When the information including the member ID is received, it is determined that the player corresponding to the member ID has visited the store.

  The point management unit 355c refers to the point grant conditions set in the rank-based visit point grant condition data 354b and the bonus point grant condition data 354c when the member visit determination unit 355b determines the visit of the player. If it is determined whether or not the player needs to be granted, and it is determined that points are to be granted, the player's point data is added to the member point data 354d.

  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 data related to membership of the member management apparatus 350 shown in FIG.

  The member data 354a is composed of personal information such as a member rank, a member's name and address, and storage information for each game type in association with the member ID. The member data 354a shown in FIG. “00001” is associated with member rank “Ace”, member personal information, and data of a 4-yen pachinko “15000” ball, a 2-yen pachinko “2500” ball, and a 1-yen pachinko “0” ball.

  The rank-specific visit point grant condition data 354b includes the number of normal visit point grant points and the point expiration date in association with the member rank. The rank-specific visit point grant condition data 354b shown in FIG. 16 includes a member rank “Premier” with a granted point number “2 points / day” and a point expiration date “indefinite”, and a member rank “Ace” with a given point number “2 points”. / Day ", point expiry date" 1 year ", member rank" ordinary ", granted point number" 2 points / day ", point expiry date" 6 months ", member rank" temporary member "granted point number" 1 point / Day ”and the point expiration date“ 1 month ”are associated with each other.

  The bonus point granting condition data 354c includes the bonus point granting point number and the expiration date in association with the bonus point granting condition. The bonus point granting condition data 354c shown in FIG. 16 includes the bonus point granting condition “female”, the number of points granted “1 point / day”, the point expiration date “1 month”, and the bonus point granting condition “weekday daytime”. “1 point / day” is associated with the point expiration date “3 months”.

  The member point data 354d has a plurality of records for the same member ID, and each record has a member ID, a point grant date, a point expiration date, a grant point, and a point grant condition. The member point data 354d shown in FIG. 16 includes a record of a member ID “00001” point grant date “2012/4/3” point validity date “2013/4/2” grant point “2” point grant condition “visit”, Member ID “00001” point grant date “2012/4/3” point validity date “2012/5/2” grant point “1” point grant condition “female” record and member ID “00001” point grant date “2012” / 4/3 ”point effective date“ 2012/7/2 ”granted point“ 1 ”point grant condition“ weekday daytime ”is stored.

  Next, a processing procedure related to store visit point grant by the member management apparatus 350 will be described. FIG. 17 is a flowchart illustrating a processing procedure related to store visit point grant by the member management apparatus 350 according to the fourth embodiment. First, the member visit determination unit 355b determines whether or not there is a store visit event of the player (step S401). Specifically, a member card insertion / extraction in the inter-card card processor 10 of a player, a deposit operation, a ball lending operation, a holding ball replay operation, a stored ball replay operation, and a counting operation with the member card inserted. The reception of information including the member ID notified by is a store visit event. These store visit events are monitored, and if no data has been received (step S401; No), the process ends.

  When any data of the store visit event is received (step S401; Yes), the point granting condition is “visit” with the player member ID of the member point data 354d and the point grant date is today's date. The presence / absence of today's store visit history is determined by determining the presence / absence of a record being present (step S402). If there is a record with the player member ID in the member point data 354d and the point granting condition is “visit” and the point grant date is today's date (step S402; Yes), Since it has been granted, the store visit point grant process (step S403) is not performed, and the process proceeds to a bonus point related process (step S404).

  If there is no record with the player member ID in the member point data 354d and the point granting condition is “visit” and the point grant date is today's date (step S402; No), the player from the member data 354a Member number, and the number of points given as a visit point of the member rank and the expiration date are acquired from the rank-specific visit point grant condition data 354b, and the expiration date is calculated from the expiration date and today's date, The point data of today's visit with the member ID is added to the member point data 354d (step S403).

  Next, it is determined whether or not there is an unevaluated bonus point granting condition in the bonus point granting condition data 354c (step S404). If there is an unevaluated bonus point granting condition (step S404; Yes), an unevaluated bonus is given. For one of the point grant conditions, a process for determining whether or not the bonus point grant condition is satisfied is performed (step S405). If the evaluated bonus point grant condition is satisfied (step S405; Yes), if the bonus point has not been given today (step S406; No), bonus point grant processing (step S407) is performed. Specifically, the number of granted points and the expiration date stored in association with the bonus point grant condition in the bonus point grant condition data 354c are acquired, and the expiration date is calculated from the expiration date and today's date, As a player record of the member ID in the member point data 354d, the point given date is today's date, the valid date calculated as the point valid date, and the number of grant points stored in association with the bonus point grant condition Then, a record composed of the bonus point granting condition stored in association with the bonus point granting condition is added to the point granting condition (step S407).

  When the evaluated bonus point grant condition is not satisfied (step S405; No), the process returns to the determination process for the presence / absence of unevaluated bonus points (step S404). If the bonus points have been given today (step S406; Yes), the bonus points are not given, and the process returns to the determination process for the presence of unevaluated bonus points (step S404). If there is no unevaluated bonus point granting condition (step S404; No) in the process of determining the presence or absence of unevaluated bonus points (step S404), the process ends.

  As described above, in the fourth embodiment, the member rank, personal information, and stored information visit points are managed in association with the member ID for identifying the player, and the number of points given or the number of points given according to the member rank are managed. Since it is configured to enable setting of expiration dates, setting of bonus points with expiration dates according to member attributes, and setting of bonus points with expiration dates during idle periods / off hours of amusement stores In addition, the store visit points can be efficiently used to enhance the motivation of the visitor to the store and the game.

  In the above-described embodiments, the first embodiment, the second embodiment, the third embodiment, and the fourth embodiment have been described as independent embodiments. However, in practice, the features of the respective embodiments can be combined. .

  Further, the additional points of the first embodiment and the bonus points of the fourth embodiment may be managed separately from the basic points. Further, as shown in the second embodiment, when a plurality of store visit events are detected, the store visit event that gives basic points can be made different from the store visit event that gives additional points or bonus points.

  Further, the number of members to whom basic points are given and the number of members to which additional points are given may be separately tabulated. The basic points are points indicating that you have visited the store, and the additional points correspond to the staying time. Therefore, by adding up the number of members who have been granted basic points and the number of members that have been given additional points separately, The number of members who stayed only and the number of members who stayed for a long time can be obtained.

  In the above-described embodiments, detailed description of the form of the membership card is omitted, but the 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.

  In addition, each configuration illustrated in the above-described embodiments 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 the one shown in the figure, and all or a part thereof may be functionally / physically distributed / integrated in arbitrary units according to various loads and usage conditions. Can be configured.

  For example, in the above-described embodiment, the case where both the setting of the store visit point and its granting conditions and the provision of the store visit point to the player satisfying the conditions are performed by the member management device has been described. The apparatus for setting the grant conditions and the apparatus for giving the store points to the players who satisfy the conditions may be configured as different devices. Further, the apparatus for setting the store visit points and the conditions for granting them is not necessarily provided in the game store, but may be provided in a management center that manages a plurality of game stores.

  As described above, the player management system and the player management method according to the present invention are suitable for efficiently operating the store visit points and enhancing the motivation of the players to visit the store and games.

10 card processing machines 20 gaming machines 40 card management devices 50, 150, 250, 350 member management devices 51, 151, 251 and 351 display units 52, 152, 252 and 352 input units 53, 153, 253 and 353 communication units 54, 154, 254, 354 Storage unit 54a, 154a, 254a, 354a Member data 54b Point grant reference data 54c, 154e, 254c, 354d Member point data 55, 155, 255, 355 Control unit 55a, 155a, 255a, 355a Member Data management unit 55b, 155c, 255b, 355b Member visit determination unit 55c, 155d, 255c, 355c Point management unit 60 Premium management device 90 Communication line 154b Reference period setting data 154c Store visit frequency data 154d, 254b Points Given condition data 155b visit frequency management unit 354b by rank visiting points giving condition data 354c bonus points given condition data

Claims (9)

A player management system for managing information related to a player,
Detection means for detecting the visit of the player;
A specifying means for specifying a player whose visit is detected by the detecting means;
Grant privilege determining means for determining a store visit privilege to be granted to the player based on information relating to the player specified by the specifying means;
A player management system comprising: privilege granting means for granting store visit privilege determined by the grant privilege determining means. It further comprises store visit history management means for managing the visit history of the player,
2. The player management system according to claim 1, wherein the grant privilege determining unit determines a store visit privilege to be granted to the player based on the store visit history.   The grant privilege determining means individually sets a determination period for determining a store visit privilege to be granted to the player and an grant period for granting a store visit privilege determined based on the store visit history within the determination period. The player management system according to claim 2, wherein:   2. The player management system according to claim 1, wherein the grant privilege determining unit adds a store visit privilege to be granted to the player according to a stay time of the player.   The grant privilege determining means determines a grant visit privilege in a time zone in which the player stays as a visit privilege to be given to the player among grant visit privileges determined corresponding to a time zone, and the player When the user stays over a plurality of time zones, the maximum value among the plurality of store visit privileges corresponding to the plurality of time zones is determined as the store visit privilege to be given to the player. Item 2. A player management system according to Item 1.   The game according to any one of claims 1 to 4, wherein the store visit privilege granting unit executes the store visit privilege grant on condition that a predetermined operation related to a game is performed by the player. Customer management system.   The player management system according to any one of claims 1 to 5, further comprising expiration date management means for setting an expiration date for a store visit privilege granted to the player.   The player management system according to claim 6, wherein the expiration date management means sets an expiration date of a store visit privilege to be given to the player based on information about the player. A player management method for managing information related to a player,
A detection step for detecting the visit of the player;
A specific step of identifying a player whose visit was detected by the detection step;
Based on information relating to the player specified in the specifying step, an granted privilege determining step for determining a store privilege to be granted to the player;
A player management method, comprising: a privilege granting step of performing the granting of the store visit privilege determined in the grant privilege determining step.

Images