Game information providing system and game information providing method

Abstract

To smoothly provide game information to a user using an application on a mobile terminal.SOLUTION: When the registration deletion setting period is 90 days, in an application server device 80, if the application has not been used by a mobile terminal 100 for 90 days or more, a user information management device 60 is notified of the deletion of user information related to the corresponding fan ID (S1). If a member ID is not associated with the received fan ID, the user information management device 60 deletes the user information related to the fan ID, and does not delete the user information of the fan ID associated with the member ID (S2). For example, a fan ID "AP1234" is not associated with a member ID, so the user information is deleted. On the other hand, the fan ID "AP5678" is associated with the member ID "2015", so the user information is not deleted.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a gaming information providing system and a gaming information providing method that can smoothly provide gaming information to a user using an application on a mobile terminal. [Background technology]

[0002] Conventionally, gaming establishments such as pachinko parlors have offered jackpot information services that provide players with jackpot information on gaming machines (see, for example, Patent Document 1). Specifically, jackpot information is transmitted from a hall computer (hall management device) installed in the gaming establishment to an external server device (game information management device). This allows players to access the server device using a browser installed on their mobile terminals and obtain the jackpot information.

[0003] In addition, a user can install an application program (hereinafter simply referred to as an "app") on a smartphone owned by the user and access the app server device via the app, thereby enabling the user to obtain game information such as jackpot information. When the app accesses the app server device for the first time, the app is given identification information (hereinafter referred to as a "fan ID") and user information is accepted, and the user information of the user is stored in the user information management device. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2012-191973 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, according to the above conventional technology, the more users who use the app, the more user information is accumulated in the user information management device. Therefore, it is desirable to delete the user information when a certain condition is met (for example, when the app has not been used for six months), but if the user information is deleted uniformly, the user must re-enter the user information when using the app again, which is not efficient.

[0006] The present invention has been made to solve the problems of the above-mentioned conventional technology, and aims to provide a gaming information providing system and a gaming information providing method that can smoothly provide gaming information to users using an app on a mobile device. [Means for solving the problem]

[0007] In order to solve the above problems, the present invention provides a gaming information providing system having an app server device that manages gaming information received from a hall management device installed in a gaming facility and provides the gaming information in response to access via an app on a user's mobile terminal, wherein the app server device is equipped with a deletion instruction means that, when a predetermined period of time has elapsed since the last access via the app, issues an instruction to a predetermined user information management device to delete user information corresponding to the app identification information of the app, and the user information management device is equipped with a management means that, when it receives the app identification information and the user information, associates the app identification information with the membership information of the user registered in the gaming facility and manages them, a deletion means that, when it receives an instruction to delete the user information, deletes the user information on the condition that the app identification information is not associated with the membership information, and a notification means that notifies the app server device of the deletion result of the user information.

[0008] In addition, in the above invention, the app server device is further characterized by having a user information receiving means for receiving user information of the user when access via the app is received, and a notification means for notifying the user information management device of app identification information that uniquely identifies the app of the user and the user information.

[0009] Furthermore, in the above invention, the deletion means is characterized in that when an instruction to delete the user information is received, the deletion means does not delete the user information if the app identification information is associated with the membership information.

[0010] Furthermore, in the above invention, the deletion means is characterized in that when an instruction to delete the user information is received, the deletion means deletes the user information if the app identification information is associated with the member information and if the member storage medium has not been used by the user for a predetermined period of time.

[0011] Furthermore, in the above invention, the deletion means is characterized in that when an instruction to delete the user information is received, the deletion means deletes the user information if the app identification information is associated with the membership information and if the user does not visit the gaming establishment within a specified period from the date of their last visit.

[0012] The present invention also provides a method for providing game information in a game information providing system having an app server device that manages game information received from a hall management device installed in a gaming facility and provides the game information in response to access by an app on a user's mobile terminal, the method including a deletion instruction process in which the app server device instructs a specified user information management device to delete user information corresponding to the app identification information of the app when a specified period of time has elapsed since the last access by the app, a management process in which, when the user information management device receives the app identification information and the user information, the app identification information is associated with and managed by the user, a deletion process in which, when the user information management device receives an instruction to delete the user information, the user information is deleted on condition that the app identification information is not associated with the membership information, and a notification process in which the user information management device notifies the app server device of the deletion result of the user information. Effect of the Invention

[0013] According to the present invention, gaming information can be smoothly provided to users using an application on a mobile terminal. [Brief description of the drawings]

[0014] [Figure 1] FIG. 1 is an explanatory diagram of an overview of a game information providing system according to an embodiment. [Diagram 2] FIG. 2 is a diagram showing a system configuration of the game information providing system according to the embodiment. [Diagram 3] FIG. 3 is a diagram showing a process flow in the game information providing system according to the embodiment. [Figure 4] FIG. 4 is a functional block diagram showing the configuration of the user information management device shown in FIG. [Diagram 5] FIG. 5 is a diagram showing an example of the user data shown in FIG. [Figure 6] FIG. 6 is a functional block diagram showing a configuration of the first game information management device shown in FIG. [Figure 7] FIG. 7 is a diagram showing an example of the game information data shown in FIG. [Figure 8] FIG. 8 is a functional block diagram illustrating a configuration of the application server device illustrated in FIG. [Figure 9] FIG. 9 is a diagram showing an example of the application user data and the set period data shown in FIG. [Figure 10] FIG. 10 is a diagram showing an example of the game information data and the usage history data shown in FIG. [Figure 11] FIG. 11 is a flowchart showing a process for deleting a fan ID according to the embodiment. [Figure 12] FIG. 12 is an explanatory diagram of an outline of a game information providing system according to the first modification. [Figure 13] FIG. 13 is an explanatory diagram of an outline of a game information providing system according to the second modification. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] [Embodiment] Hereinafter, a gaming information providing system and a gaming information providing method according to the present embodiment will be described in detail with reference to the drawings.

[0016] The gaming information providing system according to this embodiment has an application server device and a first gaming information management device that provide gaming information to mobile terminals. Access from mobile terminals to the application server device is managed by a fan ID stored in the device itself. Access from mobile terminals to the first gaming information management device is managed by a member ID stored in the user information management device. When a user with a member ID acquires a fan ID, the member ID and fan ID are associated in the user information management device.

[0017] <Outline of the gaming information providing system according to the embodiment> First, an overview of the gaming information providing system according to this embodiment will be described. Fig. 1 is an explanatory diagram for explaining the overview of the gaming information providing system according to this embodiment.

[0018] As shown in Figure 1, in the gaming information providing system of this embodiment, the date on which the application server device 80 was accessed using the application on the mobile terminal 100 is stored, and if there is no access using the application for a specified period of time, a determination is made as to whether or not to delete the user information, and the user information is deleted based on the determination result.

[0019] Specifically, when the registration deletion setting period is 90 days, if the app has not been used by the mobile terminal 100 for 90 days or more, the app server device 80 notifies the user information management device 60 to delete the user information related to the corresponding fan ID (S1).

[0020] If the received fan ID is not associated with a member ID, the user information management device 60 deletes the user information related to that fan ID, but does not delete the user information of the fan ID associated with a member ID (S2).

[0021] For example, if 90 days have passed since the last access by the app from fan IDs "AP1234" and "AP5678," the user information for "AP1234" will be deleted because "AP1234" is not associated with a member ID. On the other hand, the user information for "AP5678" will not be deleted because it is associated with member ID "2015."

[0022] In this way, the gaming information providing system of this embodiment is configured to delete the user information of a fan ID if the fan ID and member ID are not associated when a predetermined period of time has passed since the last access from a mobile terminal to the app server device, so that gaming information can be smoothly provided to users using an app on their mobile terminal.

[0023] <System configuration of the gaming information providing system according to the embodiment> Next, a system configuration of the game information providing system according to this embodiment will be described below. Fig. 2 is a diagram showing the system configuration of the game information providing system according to this embodiment.

[0024] As shown in Fig. 2, a gaming establishment is equipped with a plurality of gaming machines 20 and an inter-machine card processor 10 provided corresponding to each gaming machine 20. The inter-machine card processor 10 is communicably connected to a hall management device 40 and a management device 50. A hall management device 40a is installed in gaming establishment A, and a hall management device 40b is installed in gaming establishment B.

[0025] The hall management device 40 and the management device 50 are connected to the Internet, and a user information management device 60, a first game playing information management device 70, an application server device 80, a second game playing information management device 90 and a mobile terminal 100 are also connected to the Internet.

[0026] The gaming machine 20 is a device that plays games by shooting gaming balls enclosed inside the device onto a gaming board. The gaming balls are physical "balls" used in the game, and are different from "game balls" that the gaming machine 20 treats as data. The gaming board of the gaming machine 20 is provided with a plurality of winning areas (winning holes), and a predetermined number of gaming balls are awarded as prize balls based on the passing of the gaming balls through the winning areas. In addition, the gaming board is provided with a predetermined number of starting areas (starting holes), and a predetermined lottery is performed based on the passing of the gaming balls through the starting areas. If the lottery is a jackpot, a predetermined movable member or the like is operated to increase the probability of the gaming balls passing through the winning areas or other starting areas, and other operations that are advantageous in the game are performed. It is possible for there to be an area that serves as both a starting area and a winning area.

[0027] The winning area is provided with a winning sensor for detecting the passage of a game ball into the winning area, and the winning sensor detects the passage (winning) of a game ball shot into the winning area. The control unit of the gaming machine 20 also has a prize ball memory for storing the number of game balls to be awarded as prize balls for each winning area, and a game ball number memory for indicating the number of game balls managed by the gaming machine. The control unit of the gaming machine 20 also periodically transmits the number of game balls managed by the gaming machine to the machine-to-machine card processing machine 10.

[0028] When the inter-machine card processing machine 10 receives a deposit from a player, it associates a prepaid value corresponding to the amount of the deposit with the identification information (card ID) of the card stored inside the machine. This prepaid value can be used to lend game balls. The inter-machine card processing machine 10 can also accept the insertion of a card associated with a prepaid value, retained balls, saved balls, etc. Then, at the end of a game, the inter-machine card processing machine 10 ejects the card associated with the prepaid value, retained balls, saved balls, etc. and returns it to the player. The inter-machine card processing machine 10 also transmits a history of operations such as deposits, card insertion, and card ejection to the management device 50.

[0029] When a predetermined number of game balls are shot onto the game board, the game machine 20 transmits out data to the inter-machine card processor 10. When a game ball passes through a winning area (so-called winning) and a predetermined number of prize balls are added to the game balls, the game machine 20 transmits safe data to the inter-machine card processor 10. Furthermore, when a special state such as a jackpot occurs during play, the game machine 20 transmits special prize data indicating the occurrence of such state to the inter-machine card processor 10.

[0030] The out data corresponds to the number of balls inserted, which is the number of balls inserted by the player onto the game board. The safe data corresponds to the number of balls won as a result of winning. Furthermore, the special prize data indicates the status of the gaming machine 20, such as a jackpot. Each piece of data is transmitted to the hall management device 40 via the inter-machine card processing device 10, and the hall management device 40 can obtain the operation history of the gaming machine 20 by accumulating the out data, safe data, and special prize data.

[0031] The inter-machine card processing machine 10 accepts deposits, lends game balls, communicates with the hall management device 40 and the management device 50, and communicates with the gaming machines 20. When the inter-machine card processing machine 10 accepts bills inserted by a player, it sends a deposit notification including the amount of the deposit to the management device 50, thereby adding the prepaid value equivalent to the amount of the deposit to the prepaid value managed by the management device 50. Then, when a specified ball lending operation is performed, it sends a ball lending request to the management device 50, subtracts the prepaid value managed by the management device 50, and notifies the gaming machine 20 of the number corresponding to the subtracted prepaid value, which is added to the number of balls managed by the gaming machine.

[0032] When the inter-machine card processing machine 10 accepts the insertion of a card, it sends a card insertion notification to the management device 50. Furthermore, when the inter-machine card processing machine 10 receives the prepaid value, the balance of held balls, or the balance of saved balls from the management device 50, it stores the balance. When the inter-machine card processing machine 10 receives and stores the balance of held balls, it sends a request to subtract held balls to the management device 50, thereby clearing the balance of held balls (number of held balls) managed by the management device 50 to zero.

[0033] When the inter-machine card processing machine 10 accepts a held ball replay operation, it subtracts a predetermined number from the number of held balls it manages, notifies the gaming machine 20 of the number corresponding to the subtracted held balls, and adds it to the number of balls managed by the gaming machine. In addition, when the inter-machine card processing machine 10 accepts a saved ball replay operation, it sends a saved ball replay request to the management device 50, thereby subtracting a predetermined number from the number of saved balls managed by the management device 50, notifies the gaming machine 20 of the number corresponding to the subtracted saved balls, and adds it to the number of balls managed by the gaming machine.

[0034] When the inter-machine card processor 10 accepts a card return operation, it sends a ball addition request including the number of held balls to the management device 50, and after having the management device 50 add the number of held balls, it sends a card ejection notification to the management device 50 and controls the ejection of the card. Note that if a counting operation is accepted from the gaming machine 20 before the card return operation, the number of gaming machine managed balls is added to the number of held balls.

[0035] The inter-machine card processing device 10 has a function of acquiring a gaming machine ID from the gaming machine 20, and authenticating the gaming machine 20 using the acquired gaming machine ID and an authentication key received from the management device 50. This authentication is performed at the time of opening a store, etc., and the gaming machine 20 becomes available for play on condition that the authentication is successful.

[0036] The hall management device 40 is a device that collects and tallys information on the status of the gaming machines 20 from the inter-machine card processing device 10. The hall management device 40 can calculate the status and sales of the gaming machines 20 by accumulating the out data, safe data and special prize data received from the inter-machine card processing device 10. The status and sales of the gaming machines 20 can be tallyed by gaming machine, island or arcade, and can also be tallyed by date.

[0037] In addition, the hall management device 40 notifies the first game playing information management device 70 or the second game playing information management device 90 associated with the own device of the acquired state of the gaming machine 20 as game playing information.

[0038] When the management device 50 receives a card insertion notification from the inter-machine card processing device 10, it manages the identification information of the inserted card (hereinafter referred to as the "card ID") in association with the inter-machine card processing device 10, and transmits the prepaid value and the remaining balls associated with the card ID to the inter-machine card processing device 10. Also, if the card ID indicated in the card insertion notification is the card ID of a membership card, it transmits the stored ball replay data to the inter-machine card processing device 10.

[0039] In addition, when the management device 50 receives a request to subtract balls held from the inter-machine card processing machine 10, it clears the balance of held balls to zero, and when it receives a request to add balls held from the inter-machine card processing machine 10, it adds the number of held balls indicated in the request to add balls held to the balance of held balls.

[0040] Furthermore, when the management device 50 receives a ball lending request from the inter-machine card processing device 10, it subtracts a predetermined value from the prepaid value associated with the card ID and transmits ball lending permission to the inter-machine card processing device 10. When the management device 50 receives a saved ball replay request, it transmits saved ball replay data to the inter-machine card processing device 10.

[0041] The management device 50 also acquires a gaming machine ID from the inter-machine card processor 10 and manages the gaming machines 20 installed in its own arcade. It also acquires an authentication key for authenticating the gaming machines 20 set in its own arcade from an authentication key management center (not shown) outside the arcade and distributes it to the inter-machine card processor 10.

[0042] The management device 50 also manages the member management data of the members who are registered with the gaming establishment. Specifically, the management device 50 manages the number of balls, points, PIN, name, etc., in association with the member card ID issued to the member.

[0043] In addition, when new member information is registered in the member management data, the management device 50 attaches the gaming store ID of its own store to this member information and transmits it to the user information management device 60 or the second gaming information management device 90 associated with its own device.

[0044] Furthermore, when the management device 50 receives a card insertion notification from the inter-machine card processing machine 10, it transmits stored ball replay data including the balance of stored balls and the PIN number corresponding to the card ID indicated in the card insertion notification to the inter-machine card processing machine 10. Furthermore, when the management device 50 receives a stored ball replay request from the inter-machine card processing machine 10, it subtracts a predetermined number from the balance of stored balls associated with the card ID indicated in the stored ball replay request, and transmits stored ball replay data including the balance of stored balls after the subtraction to the inter-machine card processing machine 10.

[0045] The user information management device 60 is a device that manages user data related to the game information site and the app provided by the first game information management device 70. When the user information management device 60 receives member information from the management device 50, the user information management device 60 stores the member information in the user data.

[0046] Furthermore, when the user information management device 60 receives application user information from the application server device 80, the user information management device 60 stores the application user information in the user data. If the received application user information includes a member ID, the user information management device 60 stores the member ID in association with a fan ID and a profile.

[0047] Furthermore, when the user information management device 60 receives an authentication request from the first gaming information management device 70, it performs authentication based on whether or not the gaming facility ID and member ID included in this authentication request are included in the user data. If this gaming facility ID and member ID are included in the user data, the authentication result is "available", and if they are not included in the user data, the authentication result is "unavailable", and notified to the first gaming information management device 70.

[0048] Furthermore, when the user information management device 60 receives a deletion request from the application server device 80, it extracts data corresponding to the fan ID included in the deletion request from the user data. If the extracted data includes a member ID, it notifies the application server device 80 that "deletion not allowed" as the deletion result. If the extracted data does not include a member ID, it deletes the fan ID and profile of the data corresponding to the user data, and notifies the application server device 80 of the fan ID as the deletion result.

[0049] The first gaming information management device 70 is a device that provides gaming information of a gaming facility registered in the device itself at a gaming information site that the device itself manages. When the first gaming information management device 70 receives an authentication request including a gaming facility ID and a member ID from the mobile terminal 100, the first gaming information management device 70 notifies the user information management device 60 of the authentication request.

[0050] Furthermore, the first game information management device 70 receives an authentication result from the user information management device 60, and if the authentication result includes "available", the first game information management device 70 permits the mobile terminal 100 related to the authentication result to access the game information site. If the received authentication result includes "unavailable", the first game information management device 70 prohibits the mobile terminal 100 related to the authentication result from accessing the game information site.

[0051] Furthermore, when the first game information management device 70 receives game information from the hall management device 40, the first game information management device 70 stores the game information in game information data and notifies the application server device 80. The first game information management device 70 publishes the game information stored in the game information data on a game information site.

[0052] The application server device 80 is a device that provides game information of a gaming facility registered in the mobile terminal 100 via an application installed in the mobile terminal 100. When the application server device 80 receives a registration request including profile information such as a nickname from the mobile terminal 100, the application server device 80 generates a unique fan ID, stores it in the application user data, and notifies the mobile terminal 100 of the ID.

[0053] Furthermore, when the application server device 80 generates a fan ID, it notifies the user information management device 60 of the application user information including this fan ID and the profile received from the mobile terminal 100. If the registration request received from the mobile terminal 100 includes an amusement facility ID and a member ID, it notifies the user information management device 60 of the application user information including the amusement facility ID and the member ID.

[0054] Furthermore, when the application server device 80 accepts a registration deletion setting period, the application server device 80 stores the registration deletion setting period in the setting period data. When the application server device 80 receives game information from the first game information management device 70 or the second game information management device 90, the application server device 80 stores the game information in the game information data.

[0055] Furthermore, when the application server device 80 receives access using a fan ID from the mobile terminal 100, it notifies the mobile terminal 100 of the game information stored in the game information data. Then, it stores the current date as the last usage date of the application user data corresponding to the received fan ID and updates it.

[0056] In addition, the application server device 80 checks at a specified time every day whether or not there is a fan ID for which the registration deletion setting period has passed since the last date of use of the application, and if there is a fan ID for which the registration deletion setting period has passed, it notifies the user information management device 60 of a deletion request including this fan ID.

[0057] Furthermore, the application server device 80 receives a deletion result from the user information management device 60, and if the deletion result includes a fan ID, it deletes data relating to the fan ID from the application user data.

[0058] The second gaming information management device 90 is a device that provides gaming information of a gaming facility registered in the own device at a gaming information site managed by the own device. When the second gaming information management device 90 receives gaming information from the hall management device 40, the second gaming information management device 90 stores the gaming information in gaming information data and notifies the application server device 80 of the gaming information.

[0059] Furthermore, when the second game information management device 90 receives access from a mobile terminal 100 registered in the second game information management device 90, the second game information management device 90 provides the mobile terminal 100 with predetermined game information.

[0060] The mobile terminal 100 is a terminal device such as a smartphone owned by a user, and is used when accessing a gaming information site, etc. to display gaming information. The mobile terminal 100 accesses the gaming information site provided by the first gaming information management device 70 using a gaming facility ID and a member ID.

[0061] In addition, the mobile terminal 100 is given an access ID by the second game information management device 90 by registering specified information with the second game information management device 90, and uses this access ID to access the game information site provided by the second game information management device 90.

[0062] Furthermore, the mobile terminal 100 is assigned a fan ID by the application server device 80 by registering user information such as a nickname and address (hereinafter referred to as a "profile") with the application server device 80, and using this fan ID and an application installed on the mobile terminal, the mobile terminal 100 acquires game information provided by the application server device 80 and displays it on the application. When acquiring the fan ID, a game store ID and a member ID can also be registered.

[0063] <Processing flow in the gaming information providing system according to the embodiment> Next, the flow of processing in the gaming information providing system according to this embodiment will be described. Fig. 3 is a diagram showing the flow of processing in the gaming information providing system according to this embodiment.

[0064] As shown in FIG. 3, in the gaming information providing system according to this embodiment, when member information is registered in the management device 50 of the gaming establishment A, this member information is notified to the user information management device 60 (S11).

[0065] When the mobile terminal 100 registers for application use with the application server device 80 by attaching a member ID at game facility A (S12), the application server device 80 issues a fan ID and notifies the user information management device 60 of this fan ID and the received member ID (S13). The user information management device 60 stores the received fan ID and member ID in association with each other (S14).

[0066] The hall management device 40a of the gaming facility A notifies the first gaming information management device 70 of gaming information at a predetermined time (e.g., during closing processing) (S15), and the first gaming information management device 70 notifies the received gaming information to the application server device 80 (S16).

[0067] The hall management device 40b of the gaming facility B notifies the second gaming information management device 90 of the gaming information at a predetermined time (e.g., during closing processing) (S17), and the second gaming information management device 90 notifies the received gaming information to the application server device 80 (S18).

[0068] The mobile terminal 100 accesses the application server device 80 by an application installed in the mobile terminal 100 and browses the registered game information (S19).

[0069] <Configuration of User Information Management Device 60> Next, a description will be given of the configuration of the user information management device 60 shown in Fig. 2. Fig. 4 is a functional block diagram showing the configuration of the user information management device 60 shown in Fig. 2. As shown in Fig. 4, the user information management device 60 has a display unit 61, an input unit 62, a communication unit 64, a storage unit 65, and a control unit 66.

[0070] The display unit 61 is a display device such as a liquid crystal panel, etc. The input unit 62 is an input device such as a keyboard, a mouse, etc. The communication unit 64 is an interface unit for communicating data with various devices via the Internet.

[0071] The storage unit 65 is a storage device including a hard disk drive, a non-volatile memory, etc., and stores user data 65a. The user data 65a is data indicating information related to users who use the game information site provided by the first game information management device 70 and the game information service of the application provided by the application server device 80.

[0072] The control unit 66 is a control unit that controls the entire user information management device 60, and has a user data management unit 66a, a user authentication unit 66b, and an application user management unit 66c. In practice, these programs are loaded into a CPU (Central Processing Unit) and executed, causing the user data management unit 66a, the user authentication unit 66b, and the application user management unit 66c to execute their respective corresponding processes.

[0073] The user data management unit 66a is a processing unit that manages the user data 65a. When the user data management unit 66a receives member information from the management device 50, the user data management unit 66a stores the member information in the user data 65a.

[0074] Furthermore, when the user data management unit 66a receives application user information from the application server device 80, the user data management unit 66a stores this application user information in the user data 65a. If the received application user information includes a game store ID and a member ID, the user data management unit 66a stores the fan ID and profile included in the application user information in association with the data in the user data 65a corresponding to the game store ID and member ID.

[0075] The user authentication unit 66b is a processing unit that performs authentication in response to an authentication request. When the user authentication unit 66b receives an authentication request from the first gaming information management device 70, it performs authentication based on whether or not the gaming facility ID and member ID included in the authentication request are included in the user data 65a. If the gaming facility ID and member ID are included in the user data 65a, the authentication result is "available", and if they are not included in the user data 65a, the authentication result is "unavailable", and is notified to the first gaming information management device 70.

[0076] The application user management unit 66c is a processing unit that manages the deletion of profiles of the user data 65a. When the application user management unit 66c receives a deletion request from the application server device 80, it extracts data corresponding to the fan ID included in the deletion request from the user data 65a. If the extracted data includes a member ID, it notifies the application server device 80 that "deletion not allowed" as the deletion result. If the extracted data does not include a member ID, it deletes the fan ID and profile of the corresponding data in the user data 65a, and notifies the application server device 80 of the fan ID as the deletion result.

[0077] Next, a specific example of data stored in the storage unit 65 of the user information management device 60 shown in Fig. 4 will be described. Fig. 5 is a diagram showing an example of the user data 65a shown in Fig. 4.

[0078] User data 65a shown in FIG. 5 associates fan ID “AP1234” with an arcade ID of “-”, member ID of “-”, profile nickname of “Marveluck”, postal code of “123-4567”, address of “Shinjuku-ku, Tokyo”, date of birth of “1 / 20 / 1980”, favorite game of “pachinko”, and occupation of “self-employed”.

[0079] In addition, user data 65a associates fan ID "AP5678" with an arcade ID of "ABC789," member ID of "2015," nickname in profile of "Ice Mine," postal code of "145-6789," address of "Shibuya-ku, Tokyo," date of birth of "1985 / 10 / 15," favorite game of "pachinko slot machine," and occupation of "office worker."

[0080] <Configuration of the first game information control device 70> Next, a description will be given of the configuration of the first game information management device 70 shown in Fig. 2. Fig. 6 is a functional block diagram showing the configuration of the first game information management device 70 shown in Fig. 2. As shown in Fig. 6, the first game information management device 70 has a display unit 71, an input unit 72, a communication unit 74, a storage unit 75, and a control unit 76.

[0081] The display unit 71 is a display device such as a liquid crystal panel. The input unit 72 is an input device such as a keyboard, a mouse, etc. The communication unit 74 is an interface unit for data communication with various devices via the Internet.

[0082] The storage unit 75 is a storage device including a hard disk drive, a non-volatile memory, etc., and stores game information data 75a. The game information data 75a is data indicating game information of the gaming facility registered in the first game information management device 70.

[0083] The control unit 76 is a control unit that controls the entire first game information management device 70, and has a user authentication unit 76a and a game information management unit 76b. In practice, these programs are loaded into a CPU and executed, causing the user authentication unit 76a and the game information management unit 76b to execute processes corresponding thereto.

[0084] The user authentication unit 76a is a processing unit that performs authentication processing of a user of the gaming information site. When the user authentication unit 76a receives an authentication request including a gaming facility ID and a member ID from the mobile terminal 100, the user authentication unit 76a notifies the user information management device 60 of the authentication request.

[0085] Furthermore, when the user authentication unit 76a receives an authentication result from the user information management device 60, the user authentication unit 76a performs the following process. If the received authentication result includes "available", the user authentication unit 76a permits the mobile terminal 100 related to this authentication result to access the gaming information site. If the received authentication result includes "unavailable", the user authentication unit 76a prohibits the mobile terminal 100 related to this authentication result from accessing the gaming information site.

[0086] The game information management unit 76b is a processing unit that manages the game information data 75a. When the game information management unit 76b receives game information from the hall management device 40, the game information management unit 76b stores the game information in the game information data 75a and notifies the application server device 80. The game information management unit 76b publishes the game information stored in the game information data 75a on a game information site.

[0087] Next, a specific example of data stored in the storage unit 75 of the first game playing information control device 70 shown in Fig. 6 will be described. Fig. 7 is a diagram showing an example of the game playing information data 75a shown in Fig. 6.

[0088] The gaming information data 75a shown in FIG. 7 corresponds to the gaming establishment ID "ABC789," the gaming establishment name is "Parlor ABC," the installed machine types / number of machines are "EV01 / 20" and "DX03 / 30," and the number of jackpots is "EV01 / 65" and "DX03 / 103."

[0089] <Configuration of the application server device 80> Next, a description will be given of the configuration of the application server device 80 shown in Fig. 2. Fig. 8 is a functional block diagram showing the configuration of the application server device 80 shown in Fig. 2. As shown in Fig. 8, the application server device 80 has a display unit 81, an input unit 82, a communication unit 84, a storage unit 85, and a control unit 86.

[0090] The display unit 81 is a display device such as a liquid crystal panel. The input unit 82 is an input device such as a keyboard, a mouse, etc. The communication unit 84 is an interface unit for data communication with various devices via the Internet.

[0091] The storage unit 85 is a storage device including a hard disk drive, a non-volatile memory, etc. The storage unit 85 stores application user data 85a, set period data 85b, game information data 85c, and usage history data 85d.

[0092] The application user data 85a is data indicating a fan ID and the last date of application use by this fan ID. The set period data 85b is data indicating a registration deletion set period. The game information data 85c is data indicating game information of the gaming facility registered in the first game information management device 70 and the second game information management device 90. The usage history data 85d is data indicating the usage history of the application.

[0093] The control unit 86 is a control unit that controls the entire application server device 80, and has an application user management unit 86a, a setting management unit 86b, a game information management unit 86c, a usage history management unit 86d, and an application user deletion unit 86e. In practice, by loading these programs into a CPU and executing them, the application user management unit 86a, the setting management unit 86b, the game information management unit 86c, the usage history management unit 86d, and the application user deletion unit 86e are caused to execute processes corresponding thereto.

[0094] The application user management unit 86a is a processing unit that manages the application user data 85a. When the application user management unit 86a receives a registration request including profile information such as a nickname from the mobile terminal 100, the application user management unit 86a generates a unique fan ID, stores it in the application user data 85a, and notifies the mobile terminal 100 of the ID.

[0095] Furthermore, once the application user management unit 86a has generated a fan ID, it notifies the user information management device 60 of the application user information including this fan ID and the profile received from the mobile terminal 100. If the registration request received from the mobile terminal 100 includes an amusement facility ID and a member ID, the application user management unit 86a notifies the user information management device 60 of the application user information including the amusement facility ID and the member ID.

[0096] The setting management unit 86b is a processing unit that manages the set period data 85b. When the setting management unit 86b receives a registration deletion set period from the input unit 82, the setting management unit 86b stores the registration deletion set period in the set period data 85b.

[0097] The game information management unit 86c is a processing unit that manages the game information data 85c. When the game information management unit 86c receives game information from the first game information management device 70 or the second game information management device 90, the game information management unit 86c stores the game information in the game information data 85c.

[0098] Furthermore, when the game information management unit 86c receives access using a fan ID from the mobile terminal 100, it notifies the mobile terminal 100 of the game information stored in the game information data 85c. Then, it stores the current date as the last usage date in the application user data 85a corresponding to the received fan ID and updates it.

[0099] The usage history management unit 86d is a processing unit that manages the usage history data 85d. When the usage history management unit 86d receives access from the mobile terminal 100 using a fan ID, the usage history management unit 86d stores the fan ID, the date of the day, and the content of the access in the usage history data 85d.

[0100] The application user deletion unit 86e is a processing unit that performs a deletion process for fan IDs that have not used an application for a predetermined period. At a predetermined time every day, the application user deletion unit 86e checks whether there is a fan ID for which the registration deletion setting period in the set period data 85b has passed since the last use date of the application user data 85a. If there is a fan ID for which this registration deletion setting period has passed, the application user deletion unit 86e notifies the user information management device 60 of a deletion request including this fan ID.

[0101] Furthermore, the application user deletion unit 86e receives a deletion result from the user information management device 60, and if the deletion result includes a fan ID, it deletes the data related to this fan ID from the application user data 85a.

[0102] Next, a description will be given of specific examples of data stored in the storage unit 85 of the application server device 80 shown in Fig. 8. Fig. 9 and Fig. 10 are diagrams showing examples of the application user data 85a, the set period data 85b, the game information data 85c, and the usage history data 85d shown in Fig. 8.

[0103] The application user data 85a shown in FIG. 9(a) associates the fan ID "AP1234" with a state in which the last usage date is "2022 / 12 / 15", and associates the fan ID "AP5678" with a state in which the last usage date is "2023 / 2 / 20".

[0104] The set period data 85b shown in FIG. 9(b) indicates that the registration deletion set period is "90 days."

[0105] The gaming information data 85c shown in FIG. 10(a) corresponds to the gaming establishment ID "ABC789", the gaming establishment name is "Parlor ABC", the installed machine types / number of machines are "EV01 / 20" and "DX03 / 30", and the number of jackpots is "EV01 / 65" and "DX03 / 103".

[0106] In addition, the gaming information data 85c associates the gaming establishment ID "DEF234" with the gaming establishment name being "Parlor XYZ," the installed machine types / number of machines being "EZ02 / 35" and "DY04 / 15," and the number of jackpots being "EZ02 / 122" and "DY04 / 40."

[0107] The usage history data 85d shown in Figure 10 (b) associates the usage status of "viewing machine information for gaming machine "EV01"" with fan ID "AP1234" with a usage date of "2022 / 12 / 15", and associates the usage status of "viewing gaming machine information for gaming store "Parlor ABC"" with fan ID "AP5678" with a usage date of "2023 / 2 / 20".

[0108] <Processing procedure for deleting Fan ID according to the embodiment> Next, a process for deleting a fan ID according to this embodiment will be described with reference to the flowchart of FIG 11.

[0109] As shown in FIG. 11, if there is a fan ID for which the registration deletion set period has passed since the last use date (step S101: Yes), the application server device 80 notifies the user information management device 60 of a deletion request including this fan ID (step S102).

[0110] If the fan ID included in the deletion request does not correspond to a member ID (step S103: No), the user information management device 60 includes the fan ID in the deletion result (step S104) and deletes the fan ID and profile from the user data 65a (step S105).The user information management device 60 then notifies the application server device 80 of the deletion result (step S106).

[0111] If the received deletion result includes a fan ID (step S107: Yes), the application server device 80 deletes the data related to this fan ID from the application user data 85a (step S108), and ends the process.

[0112] As described above, in the gaming information providing system of this embodiment, if a predetermined period of time has passed since the last access from a mobile terminal to the app server device, and if the fan ID and member ID are not associated with each other, the user information for that fan ID is deleted, so that gaming information can be smoothly provided to users using an app on their mobile terminal.

[0113] In the above embodiment, a configuration has been described in which the hall management device collects game information and notifies the first game information management device, but the present invention is not limited to this, and the management device can also be configured to collect game information and notify the first game information management device.

[0114] [Variation 1] In the above embodiment, a configuration was described in which if a predetermined period of time has passed since the last access from a mobile terminal to the application server device and if the fan ID is not associated with a member ID, the user information of the fan ID is deleted, but the present invention is not limited to this. It may also be configured to delete the user information of a fan ID when a predetermined period of time has passed since the last day of play, in relation to a game using a member ID that is associated with the fan ID.

[0115] In this variant example 1, we describe a gaming information providing system that deletes user information for a fan ID associated with a member ID when a predetermined period of time has passed since the last day of play.

[0116] <Outline of the gaming information providing system according to the first modified example> An overview of the game information providing system according to the present modified example 1 will be described below. Fig. 12 is an explanatory diagram of the overview of the game information providing system according to the present modified example 1.

[0117] As shown in FIG. 12, in the gaming information providing system according to the present variant example 1, the date on which the application server device 80 was accessed using an application on the mobile terminal 100 is stored, and if there is no access using the application for a specified period of time, a determination is made as to whether or not to delete the user information depending on the user's gaming status, and the user information is deleted based on the determination result.

[0118] Specifically, when the registration deletion setting period is 90 days, if the app has not been used by the mobile terminal 100 for 90 days or more, the app server device 80 notifies the user information management device 200 to delete the user information related to the corresponding fan ID (S21).

[0119] The user information management device 200 deletes the user information related to the fan ID associated with the member ID if the non-playing period during which no play has been performed has exceeded a predetermined non-playing set period (60 days) for the member ID associated with the received fan ID. Also, if the non-playing period has not exceeded the non-playing set period (60 days), the user information of the fan ID associated with the member ID is not deleted (S22).

[0120] For example, if 90 days have passed since the last access by the app from Fan IDs "AP3456" and "AP5678", the non-playing period for member ID "2039" associated with "AP3456" is "65 days", which means the non-playing period of "60 days" has passed, so the user information for Fan ID "AP3456" will be deleted. The non-playing period for member ID "2015" associated with "AP5678" is "38 days", which means the non-playing period of "60 days" has not passed, so the user information for Fan ID "AP5678" will not be deleted.

[0121] As described above, the gaming information provision system of this variant example 1 is configured to delete the user information of a fan ID associated with a member ID when a predetermined period of time has passed since the last day of play, thereby enabling gaming information to be smoothly provided to users using an app on their mobile devices.

[0122] [Variation 2] In the above embodiment, a configuration was described in which if a predetermined period of time has passed since the last access from a mobile terminal to the application server device and if the fan ID is not associated with a member ID, the user information of the fan ID is deleted, but the present invention is not limited to this. It may also be configured to delete the user information of a fan ID when a predetermined period of time has passed since the last visit of a player who has a member ID associated with the fan ID to a gaming facility.

[0123] In this variant example 2, we describe a gaming information providing system that deletes the user information of a fan ID when a player who has a member ID that is associated with the fan ID visits a gaming facility and a predetermined period of time has passed since the last visit.

[0124] <Outline of the gaming information providing system according to the second modification> An explanation will be given of an outline of the gaming information provision system according to the present modified example 2. Fig. 13 is an explanatory diagram of the outline of the gaming information provision system according to the present modified example 2.

[0125] As shown in FIG. 13, the gaming information providing system according to the present modified example 2 stores the date on which the application server device 80 was accessed using an application on the mobile terminal 100, and if there is no access using the application for a specified period of time, a determination is made as to whether or not to delete the user information depending on the user's visit to the gaming facility, and the user information is deleted based on the determination result.

[0126] Specifically, when the registration deletion setting period is 90 days, if the app has not been used by the mobile terminal 100 for 90 days or more, the app server device 80 notifies the user information management device 300 to delete the user information related to the corresponding fan ID (S31).

[0127] The user information management device 300 deletes the user information related to the fan ID associated with the member ID if the future store period during which the user has not visited the gaming facility has passed a predetermined future store setting period (60 days) for the member ID associated with the received fan ID. Also, if the future store period has not passed the future store setting period (60 days), the user information of the fan ID associated with the member ID is not deleted (S32).

[0128] For example, if 90 days have passed since the last access by the app from Fan IDs "AP3456" and "AP5678", the future store period for member ID "2039" associated with "AP3456" is "65 days", which means the future store set period of "60 days" has passed, so the user information for Fan ID "AP3456" will be deleted. The future store period for member ID "2015" associated with "AP5678" is "38 days", which means the future store set period of "60 days" has not passed, so the user information for Fan ID "AP5678" will not be deleted.

[0129] As described above, the gaming information provision system of this variant example 2 is configured to delete the user information of a fan ID when a player who has a member ID that is associated with the fan ID visits a gaming facility and a specified period of time has passed since the last visit date, so that gaming information can be smoothly provided to users using an app on their mobile devices.

[0130] In the above embodiment and each of the modified examples, a gaming information providing system that manages gaming information related to smart pachinko, which uses gaming balls as a gaming medium, has been described. However, the present invention is not limited to this, and can also be configured to be applied to a gaming information providing system that manages gaming information related to smart pachislot, which uses medals as a gaming medium.

[0131] Furthermore, the configurations illustrated in the above embodiments and modifications are merely schematic functional diagrams, and are not necessarily physically configured as illustrated. In other words, the form of distribution and integration of each device is not limited to that illustrated, and all or part of the devices can be functionally or physically distributed and integrated in any unit according to various loads, usage conditions, etc. [Industrial Applicability]

[0132] The gaming information providing system and the gaming information providing method according to the present invention are suitable for smoothly providing gaming information to users using an application on a mobile terminal. [Explanation of symbols]

[0133] 10 Card Processing Machines 20 Gaming Machines 40, 40a, 40b Hall management device 50 Management device 60, 200, 300 User information management device 61 Display section 62 Input section 64 Communications Department 65 Storage section Section 65a User data 66 Control Unit 66a User Data Management Department 66b User authentication section 66c App User Management Department 70 First game information management device 71 Display section 72 Input section 74 Communications Department 75 Memory section 75a Game information data 76 Control Unit 76a User authentication section 76b Gaming Information Management Department 80 Application server device 81 Display section 82 Input section 84 Communications Department 85 Storage section 85a App User Data 85b Set period data 85c Game information data 85d Usage history data 86 Control Unit 86a Application User Management Department 86b Settings management section 86c Gaming Information Management Department 86d Usage History Management Department 86e Application User Deletion Department 90 Second game information management device 100, 100a, 100b Mobile terminal

Claims

1. A gaming information providing system having an application server device that manages gaming information received from a hall management device installed in a gaming facility and provides the gaming information in response to access by an application on a user's mobile terminal, The application server device a deletion instruction means for instructing a predetermined user information management device to delete user information corresponding to application identification information of the application when a predetermined period of time has elapsed since the last access by the application, The user information management device includes: a management means for managing, when the application identification information and the user information are received, the application identification information and membership information of the user registered at the gaming facility in association with each other; a deletion means for deleting the user information when a deletion instruction for the user information is received, on condition that the application identification information is not associated with the member information; a notification means for notifying the application server device of a result of the deletion of the user information; A game information providing system comprising:

2. The application server device a user information receiving means for receiving user information of the user when access via the application is received; a notification means for notifying the user information management device of application identification information that uniquely identifies the application of the user and the user information; 2. The game information providing system according to claim 1, further comprising:

3. The deletion means includes: The gaming information providing system according to claim 1 or 2, characterized in that when an instruction to delete the user information is received, the user information is not deleted if the app identification information is associated with the membership information.

4. The deletion means includes: The gaming information providing system of claim 1 or 2, characterized in that when an instruction to delete the user information is received, if the app identification information is associated with the member information and if the member storage medium has not been used by the user for a predetermined period of time, the user information is deleted.

5. The deletion means includes: The gaming information providing system described in claim 1 or 2, characterized in that when an instruction to delete the user information is received, if the app identification information is associated with the membership information and the user does not visit the gaming establishment within a specified period from the date of their last visit, the user information is deleted.

6. A method for providing game information in a game information providing system having an application server device that manages game information received from a hall management device installed in a game facility and provides the game information in response to access by an application on a user's mobile terminal, comprising: a deletion instruction step of the application server device instructing a predetermined user information management device to delete user information corresponding to the application identification information of the application when a predetermined period of time has elapsed since the last access by the application; a management step of, when the user information management device receives the application identification information and the user information, associating the application identification information with membership information of the user registered at the gaming facility and managing the information; a deletion step of deleting the user information, when the user information management device receives an instruction to delete the user information, on condition that the application identification information is not associated with the member information; a notification step of the user information management device notifying the application server device of a deletion result of the user information; A method for providing game information, comprising:

Images