System for amusement facilities

Abstract

To provide a system for amusement facilities that can efficiently perform file updates on gaming devices. [Solution] In a game arcade system 1, a game device 3 provided in correspondence with a game machine 2 and a management device 12 which is a source of terminal information that can be associated with the game device 3 are connected to each other in a way that allows them to communicate with one another and form a network 101, terminal information is managed by distinguishing between general terminal information related to the verification work of the game device 3 and special terminal information that is different from the general terminal information. When the game device 3 receives general terminal information, it is possible to receive special terminal information in parallel with the verification work related to the general terminal information.

Description

[Technical Field]

[0001] The present invention relates to a system for a game arcade. [Background Art]

[0002] In a game arcade, various game devices are individually installed for each gaming machine. In game devices, program files and content files are updated from time to time. For example, Patent Document 1 below proposes an information providing system in which a hall terminal of a game arcade manages versions of program files and provides the latest program files to a plurality of gaming machines. [Prior Art Literature] [Patent Literature]

[0003] [Patent Document 1] Japanese Unexamined Patent Application Publication No. 2004-073266 [Summary of the Invention] [Problem to be Solved by the Invention]

[0004] In the case of the information providing system described above, although the latest program files can be appropriately provided, when an update including a large-capacity content file such as video content is required, downloading the update file takes a lot of time, and there is a risk that the waiting time before an employee can perform confirmation work may be prolonged.

[0005] The present invention has been made in view of the above circumstances, and provides a system for a game arcade that can efficiently execute file update of game devices. [Means for Solving the Problem]

[0006] The system for a game arcade of the present invention is a system in which a game device provided in association with a gaming machine and a management device serving as a distribution source of terminal information that can be associated with the game device are communicably connected to each other to form a network.

[0007] In the amusement arcade system of the present invention, terminal information is managed by distinguishing between general terminal information related to predetermined processing in the gaming device and special terminal information that is different from the general terminal information. In this amusement arcade system, distribution information regarding terminal information to be distributed can be distributed to the gaming device. In this amusement arcade system, by comparing this distribution information with information indicating terminal information associated with the gaming device, distribution request information that can identify at least one of the following is identified: terminal information that needs to be distributed, and whether or not distribution of terminal information is necessary, and this is notified to the management device.

[0008] In the amusement arcade system of the present invention, terminal information is distributed in response to distribution request information, while general terminal information is distributed with priority over special terminal information. When general terminal information is distributed to the amusement machine, it can perform predetermined processing related to the general terminal information even while special terminal information is being distributed. In other words, the amusement machine in the amusement arcade system of the present invention can receive special terminal information while performing predetermined processing related to general terminal information. Therefore, the amusement arcade system of the present invention enables efficient distribution of both general terminal information and special terminal information. [Brief explanation of the drawing]

[0009] [Figure 1] Configuration diagram of the amusement arcade system in Example 1. [Figure 2] Front view of the gaming machine in Example 1. [Figure 3] Front view of the scoring processing device in Example 1. [Figure 4] A block diagram showing the configuration of the management device and information display device (terminal) in Example 1. [Figure 5] An explanatory diagram showing the version information list in Example 1. [Figure 6] Diagram illustrating the high-speed terminal status notification in Example 1. [Figure 7] Diagram illustrating the download request flag in Example 1. [Figure 8] A diagram illustrating the program content list in Example 1. [Figure 9] An explanatory diagram of the model content list in Example 1. [Figure 10] Flowchart of the configuration information distribution sequence in Example 1. [Figure 11] A flowchart of the program content distribution sequence in Example 1. [Figure 12A] Flowchart of the distribution sequence for device-specific content in Example 1 (first half). [Figure 12B] Flowchart of the distribution sequence for device-specific content in Example 1 (second half). [Figure 13] A flowchart showing the flow of external DL request processing in Example 1. [Figure 14] This figure shows an example of the aggregated results of download detail notifications from the terminal in Example 1. [Figure 15] An explanatory diagram illustrating the download plan file in Example 1. [Figure 16] Diagram illustrating the file transmission order in Example 1. [Modes for carrying out the invention]

[0010] For example, when opening a new amusement arcade, it may be necessary to simultaneously download configuration files and other data to hundreds of gaming machines installed within the arcade. If verification work cannot be performed until all downloads are complete, the process will inevitably become lengthy.

[0011] The amusement arcade system of the present invention allows for the execution of predetermined processes related to general terminal information even while special terminal information is being distributed. According to the amusement arcade system of the present invention, predetermined processes related to general terminal information can be executed in parallel with the distribution of special terminal information, thus reducing the waiting time until predetermined processes, such as verification work when a new amusement arcade opens, can be performed.

[0012] Embodiments of the present invention will be specifically described with reference to the following examples. (Example 1) This example relates to a gaming facility system 1 in which an information display device 3, which is an example of a gaming device provided in association with a gaming machine 2, and a management device 12, which serves as a distribution source of terminal information that can be associated with the information display device 3, are communicably connected to each other to form an in-facility network 101 (an example of a network). This content will be described with reference to FIGS. 1 to 16.

[0013] As shown in FIGS. 1 and 2, a large number of gaming machines 2 such as pachinko machines and slot machines are installed in a gaming facility. Each gaming machine 2 is individually provided with gaming devices such as a score processing device 4 and an information display device 3. The score processing device 4 is a gaming device having a function of granting game points, which are game values necessary for playing a game (a lending function). The information display device 3 is a gaming device that displays various types of game information such as game data and model content of the corresponding gaming machine 2. Model content is game information such as images, videos, and audio related to the corresponding gaming machine 2.

[0014] In the gaming facility, one relay device 106 connected to the in-facility network 101 is installed for every two gaming machines. The score processing device 4 and the information display device 3 are connected to the in-facility network 101 via the relay device 106. The gaming machine 2 is connected to the score processing device 4, and further connected to the in-facility network 101 via the relay device 106.

[0015] A management space (not shown) for the manager is provided in the gaming facility. The management space is provided with the management device 12, a POS terminal for prize exchange, and the like. The management device 12 and the POS terminal are connected to the in-facility network 101. Furthermore, the management device 12 is connected to an external server 100 via a public communication line. The external server 100 is, for example, a distribution server operated by a management device manufacturer. When there is an update to the operation program or content file of the gaming machine 2 installed in the gaming facility, the management device 12 can download the latest version from the external server 100.

[0016] The management device 12 is a computer device for managing the operating status of the gaming machines 2 and various peripheral equipment within the gaming arcade. The management device 12 has functions for aggregating and managing game data from each gaming machine 2, storing and managing the number of points owned by players as game value, and distributing program files, content files, etc., to the information display device 3.

[0017] Next, the configuration and basic operation of the gaming machine 2 and the scoring processing device 4 will be explained, followed by a description of the configuration and operation of the management device 12 and the information display device 3. Regarding the management device 12 and the information display device 3, the explanation will primarily focus on the operation programs and content file distribution operations for each information display device 3.

[0018] (Configuration of gaming machines and scoring processing devices) In this example, we will use a pachinko game machine (Figures 1 and 2) as an example, where the game is played by launching game balls, which are the game medium, as Game Machine 2. Game Machine 2 in this example is a so-called sealed-type game machine in which game balls can be launched by consuming game points, which are the game value, and points, which are the game value, can be awarded depending on the winning combination. Game Machine 2 is a so-called seven-ball machine, and when a ball enters the starting slot, a jackpot lottery is performed, and if the predetermined jackpot conditions are met upon winning, a jackpot state (jackpot) is generated. Game Machine 2 has three game states: normal state, probability variation state, and jackpot state. The probability variation state is an advantageous game state in which the probability of winning the jackpot lottery, etc., is higher than in the normal state.

[0019] The gaming machine 2 has a roughly circular game board 230 into which game balls are inserted. Decorative lamp units 236 are located on both sides above the game board 230. Below the game board 230, from left to right as viewed from the player's side, are a counting button 255, a game point display unit 250, and a balance display unit 252. Below the balance display unit 252, an operating handle 235 for inserting game balls into the game board 230 is erected. A decorative panel 237 is located in the space to the left of the operating handle 235.

[0020] The game score display unit 250 is a display unit that shows the number of game points that can be launched. The balance display unit 252 is the remaining amount of money that has been inserted into the scoring device 4 and can be exchanged for points. The counting button 255 is an operation button used by the gaming machine 2 to convert the game points stored in it into points.

[0021] A display device 29, which forms the special symbol display section 290, is located near the center of the game board 230. To the right of the display device 29, as viewed from the player's side, are a through-gate type general symbol start opening 24 and a general prize entry opening 291. The general symbol start opening 24 is the starting opening that triggers the general symbol lottery. When a ball passes through the general symbol start opening 24, a general symbol lottery random number is extracted and held. The general prize entry opening 291 is a mechanism that awards points according to the prize. In addition, a general prize entry opening 291 is also located diagonally below and to the left of the display device 29.

[0022] Below the display device 29, a first start opening 211 is located, and diagonally to its right and below, a second start opening 212 is located. Below the gap between the first start opening 211 and the second start opening 212, a large prize opening 260 is located, which opens when a jackpot is hit. At the very bottom of the game board 230, an out hole 238 is opened to collect game balls that have flowed down without entering a prize.

[0023] The first starting gate 211 and the second starting gate 212 are starting gates that trigger the special symbol lottery, which is the lottery for the big win. The first starting gate 211 is the starting gate that triggers the first special symbol lottery. When a ball enters the first starting gate 211, a random number for the first special symbol lottery is extracted and held. The second starting gate 212 is the starting gate that triggers the second special symbol lottery. When a ball enters the second starting gate 212, a random number for the second special symbol lottery is extracted and held.

[0024] The first starting opening 211 is a prize-winning opening with a fixed winning rate (a so-called "heso" type), while the second starting opening 212 is an electric-chū type prize-winning opening with a variable winning rate. When the regular lottery is won in the second starting opening 212, the tulip opens and the winning rate increases.

[0025] The display device 29 is equipped with a frame surrounding the special display unit 290. The general display unit 270 and the general display hold display unit 272 are located in the upper right part of the frame, and the first hold display unit 281 and the second hold display unit 282 are located side by side in the lower part of the frame.

[0026] The special symbol display unit 290 is a display unit that indicates whether the special symbol lottery, which is the jackpot lottery, has been won or lost. The special symbol display unit 290 displays whether the special symbol lottery has been won or lost by a combination of three digits. In this example, if the special symbol lottery is won, the combination of numbers 777 or 333 will be displayed on the special symbol display unit 290. The regular symbol display unit 270 is a display unit that indicates whether the regular symbol lottery has been won or lost by ○ or ×. The regular symbol reserve display unit 272 is a display unit that shows the number of reserved regular symbol lottery random numbers. The first reserve display unit 281 is a display unit that shows the number of reserved first special symbol lottery random numbers. The second reserve display unit 282 is a display unit that shows the number of reserved second special symbol lottery random numbers. The reserve display units 272, 281, and 282 display a maximum of four reserved numbers by the number of LEDs lit.

[0027] The scoring device 4 (Figures 1 and 3) is a device that enables gameplay on the corresponding gaming machine 2 upon acceptance of a game card 460, such as a membership card 461, or banknotes. The scoring device 4 is connected to the in-house network 101 via a relay device 106 and can send and receive signals and information with the management device 12. The scoring device 4 functions as a means of issuing game cards 460 (recording media). As an issuing means, the scoring device 4 issues a game card 460 associated with the player's points (acquired value) when it receives a return operation or a break operation from the player.

[0028] The front panel of the scoring device 4 is equipped with status lamps 41, a banknote slot 42, a camera unit 47, a display unit 43, operation buttons 441-444, an IC card reading surface 451, a remote control receiver 452, a card slot 46 for game cards 460, and the like. The display unit 43 has a touch sensor sheet (not shown) laminated on it, allowing for touch operation. The operation buttons include a game button 441 for replaying with points, a loan button 442 for receiving game points in exchange for payment, a call button 443 for calling an employee, and an issue button 444 for requesting the issuance of a game card 460. The IC card reading surface 451 is the surface where a compatible card or device is brought close to read the IC information. The remote control receiver 452 is a receiver of infrared light, which is the operation signal from a remote control held by an employee.

[0029] (Basic operation of gaming machines and scoring devices) When the scoring device 4 accepts a banknote, the amount deposited, corresponding to the banknote acceptance process, is added to the balance and displayed on both the gaming machine 2 and the scoring device 4. When the lending button 442 is operated (lending operation, grant operation) while there is a balance, points (value of consideration) for one lending unit (for example, 125 points) are added to the game points managed by the gaming machine 2 (lending process, consideration grant process). At this time, the amount of consideration according to the game rate (hereinafter, rate) is deducted from the balance. The scoring device 4 can accept amounts equivalent to the consideration for multiple consideration grant processes, with an upper limit of, for example, 11,000 yen.

[0030] In game machine 2, if the player has 1 or more points, game balls can be launched according to the operation of the control handle 235. When playing game machine 2, the player's points are reduced by the number of balls launched, and points awarded for winning are added to the player's points. When the player's points reach zero through gameplay, it becomes impossible to launch game balls.

[0031] When a starting entry occurs, which is a ball entering either the first starting gate 211 or the second starting gate 212, a special symbol lottery, which is a jackpot lottery, is executed. The result of the special symbol lottery is announced by the symbol changes executed by the special symbol display unit 290. If the combination of symbols stopped and displayed on the special symbol display unit 290 is a jackpot symbol such as 777 or 333, a jackpot is won.

[0032] Furthermore, if a new starting win occurs during a symbol change in the special symbol display unit 290, the special symbol lottery random number corresponding to the starting win is held in reserve. The first special symbol lottery random number corresponding to a starting win in the first starting port 211, and the second special symbol lottery random number corresponding to a starting win in the second starting port 212, are each held in reserve up to, for example, a maximum of four. If a starting win occurs when the number of reserved special symbol lottery random numbers has reached the maximum limit, even if a new special symbol lottery random number is drawn, it will not be held in reserve. The reserved first and second special symbol lottery random numbers are read out in order after the symbol change ends, and the symbol change begins. The second special symbol lottery random number is read out in priority to the first special symbol lottery random number, and the first special symbol lottery random number is read out only when the number of reserved second special symbol lottery random numbers is zero.

[0033] When a jackpot is hit, the large prize slot 260 opens, and a round of gameplay with a significantly increased chance of winning is repeatedly played for a predetermined number of times. In one round (1R), there is a set limit on the number of winning entries, for example, 10, and a set limit on the opening time, for example, 30 seconds. When either the limit on the number of winning entries or the limit on the opening time is reached, one round of gameplay ends. The number of rounds, which is the number of times the round of gameplay is repeated, is determined by a round lottery.

[0034] In the example of game machine 2, the number of rounds is determined by a round lottery, resulting in one of three types of jackpots: 2R, 8R, or 15R. The distribution rate for each of the three types of jackpots differs depending on whether the ball enters the first starting slot 211 or the second starting slot 212. If the ball enters the first starting slot 211, the probability is 10% for 2R, 50% for 8R, and 40% for 15R. If the ball enters the second starting slot 212, the probability is 0% for 2R, 10% for 8R, and 90% for 15R. Thus, in the example of game machine 2, entering the second starting slot 212 offers a higher probability of winning the 15R jackpot and is more advantageous than entering the first starting slot 211. Furthermore, if the ball enters the regular starting slot 212 and wins the regular starting slot lottery corresponding to the ball entering the regular starting slot 24, the probability of entering the second starting slot 212 increases in proportion to the opening of the tulip.

[0035] The jackpot ends when the round game, which has been played for the number of rounds determined by the round lottery, is completed. After the jackpot ends, the game transitions to either the normal state or the probability-increasing state. The probability-increasing state is a more advantageous state than the normal state, as the probability of winning a jackpot through the special symbol lottery is higher. The probability of transitioning to the probability-increasing state after a jackpot (probability-increasing rate) is, for example, 66%.

[0036] Whether or not the game transitions to a probability variation state after the end of a jackpot state is predetermined by the special symbol lottery that triggered the jackpot state. There are two types of jackpots won through the special symbol lottery: probability variation jackpots that allow the game to transition to a probability variation state, and regular jackpots that do not result in a subsequent probability variation state.

[0037] If the jackpot state is triggered by a probability-increasing jackpot, the game will transition to a probability-increasing state after the jackpot ends. In the probability-increasing state, the jackpot probability increases, and the rate of winning at the second starting slot 212 increases, resulting in a time-saving mode (time-saving state). On the other hand, if a regular jackpot occurs instead of a probability-increasing jackpot, after the jackpot state ends, a time-saving mode without a probability-increasing state (standalone time-saving mode) will occur. Regardless of whether a probability-increasing state is involved or not, the time-saving mode will continue for a predetermined number of time-saving mode spins, such as 100 spins, or until a new jackpot occurs. If the number of time-saving mode spins is completed without a new jackpot occurring, the game will return to the normal state.

[0038] In the normal state, the regular diagram changes to notify the success or failure of the regular diagram lottery are performed for 30 seconds, whereas in the time-saving mode, the regular diagram change time is 3 seconds. The opening time of the second start port 212 corresponding to the success of the regular diagram lottery is 0.3 seconds in the normal state, but becomes 5 seconds in the time-saving mode. Thus, in the time-saving mode, the period of regular diagram changes is shortened compared to the normal state, and the opening period of the second start port 212 is lengthened, resulting in a significantly higher chance of winning with the second start port 212.

[0039] In this example of game machine 2, the large prize slot 260 and the second starting slot 212 are located on the right side of the game board 230. Therefore, during time-saving mode or when a jackpot is occurring, it is advantageous to aim the balls towards the right side of the game board 230, a technique known as "right-handed shooting." The above explanation is based on machine A as an example, and the values ​​exemplified are just examples. For example, with machine B, the distribution of jackpot types will be different, and the values ​​will vary depending on the machine, resulting in different gameplay.

[0040] In this example, game machine 2 is a so-called enclosed-type pachinko game machine, in which balls launched onto the game board 230 circulate and are not dispensed externally even when a winning combination occurs. In game machine 2, game points are managed, and game points are deducted according to the number of balls launched (used) onto the game board 230, and game points are added according to the number of winning combinations (winning point awarding process).

[0041] On the other hand, the scoring device 4 manages the points that cannot be used in the game unless they are converted into game points. The points are converted into game points (conversion value, conversion points) equivalent to one payout unit through a conversion process corresponding to the operation of the game button 441 (replay operation, grant operation, payout operation) (consideration processing, replay processing). In this example, the conversion rate from points to game points during the conversion process is set to 1:1, but it is also possible to set a conversion rate other than 1:1. The same handling of such conversion rates applies to the counting process described below.

[0042] When the number of game points managed by the gaming machine 2 increases in response to gameplay, pressing the counting button 255 (gaming machine 2) (counting operation) converts the game points into points (counting process). In this case, one point is converted for each press, but by continuing to press the button, continuous and accelerated conversion becomes possible. Through this counting process, the number of game points managed by the gaming machine 2 and the number of points managed by the score processing device 4 are updated.

[0043] When the issuance button 444 is operated (return operation, issuance operation) while there is a remaining balance or points, the score processing device 4 associates the balance or points with the game card 460, such as a general card (not shown), that was in stock and issues it (issuance process). In this example, the score processing device 4 can also perform a partial issuance process, where only a portion of the points or the remaining balance is to be issued.

[0044] The issuance process for the game card 460 is based on issuance conditions that correspond to the game score managed by the game machine 2. In this example, the issuance condition is met when the game score becomes a predetermined number "0" or less, and the game card 460 can be issued. The score processing device 4 communicates with the game machine 2 at regular intervals (for example, every 300 milliseconds) to acquire various game information, including whether the player is out or safe.

[0045] When the game points managed by the gaming machine 2 become "0" due to use in gameplay or counting processing, this fact is notified to the score processing device 4, and if the issuance conditions are met, the issuance process is permitted. It is sufficient to update the game points and identify that the issuance conditions have been met by including game point information that can identify the game points in the data items transmitted from the gaming machine 2, but it is also possible to set up a separate data item to indicate that the game points have become "0", or to adopt other identification methods such as outputting a separate signal.

[0046] Points associated with the game card 460 can be exchanged for prizes at the POS terminal, and the balance can be settled in currency (banknotes and coins) at a settlement machine (not shown). In this example, banknotes and other cash are used as the monetary value accepted by the scoring processing device 4. Alternatively, or in addition to this, the scoring processing device may also be capable of handling monetary values ​​other than cash, such as electronic money or credit card payments. Furthermore, while the example illustrates the issuance process of associating points and balances with game cards 460 such as general cards, the issuance process may also involve associating points and balances with other recording media such as membership cards or mobile terminals held by the players.

[0047] The scoring device 4 performs serial communication with the relay device 106 so that the management device 12 can identify various types of information. The information that the management device 12 can identify includes information such as currency acceptance processing, payment processing, balance, points held, loan points, conversion points, deposit amount, counted points, sales amount which is the payment for loan points, and information such as acceptance and issuance processing of storage media such as game cards 460. This information may also be identified by pulse signals, for example, one pulse for every 1000 yen deposited and one pulse for every 100 yen sold.

[0048] In this example configuration, the gaming machine 2 communicates directly with the scoring processing device 4 without going through the relay device 106. The game information output from the gaming machine 2 to the scoring processing device 4 includes, for example, the following data items. (1) Out: Indicates the value (out) consumed (used, entered) since the last data transmission, in units of 1 point. (2) Safe: Indicates the prize value (Safe) awarded in units of 1 point, based on the number of wins since the last data submission. (3) S Prize (Number of Times): Indicates the number of starting prizes (S prizes) since the last data transmission, in units of one. (4) Start (Count): Indicates the start (number of symbol changes, number of mechanism activations, unit play) of the special feature (special display section) that is activated (changed) by S wins since the last data transmission. It is counted when it is confirmed, but it may also be counted when it starts. (5) Operating (state): When data is transmitted, if a special feature such as a changing symbol is in operation, it will be displayed as "on," and if it is not in operation, it will be displayed as "off." The period from when it is displayed as "on" until it is displayed as "off" is identified as when the special feature is in operation. (6) Jackpot (Number of times): Indicates the number of jackpots that have occurred since the last data transmission, in units of one. It is counted when it occurs, but it is also acceptable to count it when it ends. (7) Jackpot (State): When data is transmitted, "on" is displayed if a jackpot is in progress, and "off" is displayed if a jackpot is not in progress. The period from when it is "on" until it is "off" is identified as a jackpot. (8) Sweet Mode (State): When data is transmitted, "on" is indicated if the player is in a special state (Sweet Mode) or a jackpot, and "off" is indicated otherwise. The period from when it is "on" until it is "off" is identified as Sweet Mode or a jackpot. For example, if Sweet Mode (State) is "on", then if the jackpot (State) is "on", it is identified as a jackpot; if it is "off", it is identified as Sweet Mode. Sweet Mode corresponds to the special states such as the time-saving state and the probability variation state mentioned above. It is not necessary for it to be "on" during a jackpot. If both the jackpot (State) and Sweet Mode (State) are "off", it is identified as the normal state. The state of being either a jackpot or Sweet Mode is referred to as Special Prize Mode. (9) Game points: Indicates the game value stored in game machine 2 in units of 1 point.

[0049] In this example configuration, a data signal, such as a telegram, that can identify the above data items is transmitted from the gaming machine 2 to the scoring processing device 4 once every predetermined period (300ms). The above data items are only examples of information relevant to this example; other items such as the number of game balls and fraudulent activity information may also be output.

[0050] In this example, a so-called sealed-type pachinko game machine is used as an example, but the signal output configuration will be different for a payout-type game machine. In the case of a payout-type game machine, the game signal becomes a pulse signal and is output directly to the relay device 106 without going through the score processing device 4.

[0051] (Configuration of the management device and information display device) In addition to functions such as managing game information for each gaming machine 2 installed in the gaming arcade, the management device 12 also has functions such as distributing terminal information such as necessary setting information, operating programs, and machine content files to the information display device 3 (an example of a gaming device; hereinafter referred to as terminal 3) attached to each gaming machine 2.

[0052] The management device 12 and terminals 3 (Figure 4) are equipped with interface circuits 120 and 320 for connecting to the in-house network 101. The management device 12 and each terminal 3 are connected in a manner that allows them to communicate with each other, as shown in Figure 4. The connection relationships in Figure 4 are established for each terminal 3 individually attached to each gaming machine 2 in the gaming hall. The management device 12 uses these connection relationships to distribute terminal information to each terminal 3.

[0053] As shown in Figure 4, the management device 12 implements the function of distributing terminal information through the control unit 121, storage unit 123, terminal data management unit 125, distribution unit 127, and receiving unit 129. The control unit 121 manages instructions from the management device 12 and higher-level devices (such as the external server 100), manages the status of terminals 3 connected to the management device 12 and version information corresponding to terminal information stored in terminals 3, controls the download of terminal information from the external server 100, issues instructions for collecting information about the subordinate terminals 3, and performs other such operations.

[0054] The memory unit 123 stores and keeps terminal information downloaded from the external server 100. When the machine data management unit 125 receives information collection instructions from the control unit 121 or status information of its subordinate terminals 3, it establishes an FTP (File Transfer Protocol) connection with the subordinate terminals 3 as needed, and sends and receives machine data, including model information and machine number information of the gaming machine 2 corresponding to each terminal 3, to collect and update machine data.

[0055] The distribution unit 127 distributes a message containing version information (an example of information indicating terminal information identification) managed by the control unit 121 to the subordinate terminals 3 via multicast. Figure 5 illustrates a list of version information (first distribution information) that is set in association with the download type indicating the category of terminal information. As shown in the figure, the download types include settings, program content list, model content list, and download plan. For example, when the program content list No. 2 in the figure is updated, the corresponding version information is updated. For example, if the version information before the update was 1, the version information will be updated to 2 after the update. In this way, the amusement arcade system 1 manages version information for each download type.

[0056] Terminal 3 (Figure 4) has the function of receiving terminal information from the management device 12 through a storage unit 323 that stores machine data, version information, setting files, program content list, etc. of the gaming machine 2, a transmission unit 327, a reception unit 329, etc.

[0057] The control device 12 has the following functions: (1) Management means: Means for managing the version, which is an example of identification information for terminal information and distribution information. Distribution information is information about the terminal to which distribution is to be made. (2) Means for identifying the distribution destination: Means for identifying the distribution terminal, which is the terminal 3 (gaming device) to which the terminal information will be distributed. (3) Grouping means: Means for performing a grouping process to group distribution terminals and for identifying a representative terminal which is a representative distribution terminal for each group. (4) Terminal information distribution means: Means for distributing terminal information in response to distribution request information notified from terminal 3. (5) Distribution Information Distribution Means: Means for distributing distribution information concerning terminal information to be distributed to terminal 3. Distribution information distribution means include a first distribution means that distributes terminal information to distribution terminals regardless of whether they are representative terminals or not, and a second distribution means that distributes terminal information to distribution terminals on the condition that they are representative terminals. (6) Prioritization means: A means of prioritizing the distribution of general terminal information to the terminal information distribution means over special terminal information. General terminal information is terminal information necessary for installation verification work (an example of a predetermined process), such as settings and program content. Special terminal information is terminal information such as model content, which allows installation verification work to be performed in parallel with distribution. (7) Synchronization means: Means for synchronizing the reference timing of notifications of distribution request information from each terminal 3. (8) Notification means: A means for notifying an abnormal terminal when an abnormal terminal is identified among the grouped distribution terminals. The abnormal terminal is identified by terminal 3 and notified to the management device 12.

[0058] Terminal 3 has the following functions: (1) Identification means: A means for identifying distribution request information that can identify at least one of the following: the terminal information that needs to be distributed to terminal 3 (gaming device), and whether or not the distribution of terminal information is necessary, by comparing the distribution information distributed by the distribution information distribution means (management device 12) with the information indicating the terminal information associated with terminal 3. The information indicating the terminal information includes information indicating the identification information (version) of the terminal information and information indicating the type of terminal information. (2) Notification means: Means for notifying the management device 12 of the distribution request information (download request flag, download details notification) identified by the identification means. The notification means notifies the distribution request information at predetermined intervals. To distribute the notification timing, the management device 12 sets a delay time from the above reference timing for each terminal. (3) Terminal processing means: Means that can perform predetermined processing related to the general terminal information that has been distributed to terminal 3, even if special terminal information is being distributed when general terminal information has been distributed to terminal 3. The predetermined processing is, for example, processing to perform installation verification tasks such as confirming whether the model name of the gaming machine corresponding to terminal 3 registered in the setting information is correctly displayed in the display area (not shown) of terminal 3, and confirming whether the operating program is functioning normally and whether the gaming information is displayed in the correct arrangement on the display area. (4) Transfer means: When terminal information is distributed to a representative terminal by the management device 12 (second distribution means), means for transferring terminal information between distribution terminals to other distribution terminals included in the group to which the representative terminal belongs. (5) Abnormal terminal identification means: A means that can identify an abnormal terminal that is a distribution terminal to which terminal information is to be transferred and which is unable to perform the processing related to the transfer normally, after the transfer has started by the transfer means.

[0059] The management device 12, as a means of management, manages terminal information by distinguishing between general terminal information related to predetermined processing at terminal 3 (such as confirmation work during installation, such as settings and program content) and special terminal information different from general terminal information. It also manages terminal information by dividing it into first distribution information, which is distributed regardless of whether the destination terminal is a representative terminal or not, and second distribution information, which is distributed on the condition that the destination terminal is a representative terminal.

[0060] General terminal information includes at least one of the following: terminal setting information indicating setting information for executing the predetermined process, and basic operation information including an operation program for executing the predetermined process. Special terminal information includes model content information which differs for each model of gaming machine 2 corresponding to terminal 3.

[0061] The management device 12, which is a means of distributing distribution information, is capable of distributing first distribution information that associates the version (identification information) of the terminal information, and second distribution information that shows a list of terminal information that can be distributed by the terminal information distribution means. The second distribution information is distributed when it can be identified that distribution of terminal information is necessary based on the first distribution request information, which will be described later. The first distribution information is terminal information such as version information (see Figure 5, which will be described later), which is an example of information that indicates the identification information of the terminal information. The second distribution information is terminal information such as a list-type file (see Figure 8, which will be described later), such as a program content list.

[0062] As a means of identification, terminal 3 identifies first distribution request information that can determine whether distribution of terminal information is necessary by comparing the identification information (version information) of the first distribution information distributed by the management device 12 (distribution information distribution means) with the identification information of the terminal information associated with terminal 3. On the other hand, it identifies second distribution request information that can determine which terminal information needs to be distributed to terminal 3 by comparing the second distribution information distributed by the management device 12 (distribution information distribution means) with information indicating the type of terminal information associated with terminal 3. The management device 12, as a means of distributing terminal information, targets terminal information that can be identified by the second distribution request information for distribution.

[0063] As a priority means, the management device 12 determines which of the terminal information being distributed takes priority if, after the management device 12 (terminal information distribution means) has started the terminal information distribution process, a new instruction to distribute terminal information is received from at least one of the management devices, such as the management device 12 or a management device higher than the management device 12, such as an external server 100. The management device 12 (priority means) then decides which of the terminal information being distributed takes priority based on the determination result.

[0064] The management device 12, as a means of distributing terminal information, interrupts the distribution of terminal information currently being processed and starts distributing the preferred terminal information if terminal information that takes precedence over the terminal information being distributed is identified after the start of the terminal information distribution process.

[0065] The management device 12, as a group means, can identify the distribution order of the second distribution information on a group basis when performing the above-described group processing. The management device 12, as the second distribution means, distributes terminal information to representative terminals belonging to a group in the distribution order identified by the group means described above. In some cases, terminal information with different information capacities (data sizes) may be distributed within a group. The distribution order for each group should preferably be determined based on at least one of the following: the number of distribution terminals belonging to the group, and the information capacity of the terminal information to be distributed.

[0066] The management device 12, as a grouping tool, can divide distribution terminals that distribute the same type of terminal information into a first group and a second group when grouping distribution terminals that distribute the same type of terminal information, so as not to reach a predetermined upper limit. The grouping process includes grouping distribution terminals that have different types of terminal information to be distributed from the first group and the second group into a third group. The distribution order of this third group may be interrupted between the first group and the second group, depending on the number of distribution terminals belonging to each of the first to third groups.

[0067] Terminal 3, acting as a transfer means, transfers terminal information to a distribution terminal that is a different transfer destination from the abnormal terminal when an abnormal terminal is identified. Terminal 3, acting as an abnormal terminal identification means, can determine whether the abnormal terminal has returned to a normal state in which it can successfully execute transfer-related processing. The distribution destination identification means can then identify the distribution terminal again when the abnormal terminal returns to a normal state, and causes the management device 12 (first distribution means or second distribution means) to distribute the terminal information to that distribution terminal.

[0068] When terminal 3 receives a message containing version information (an example of information indicating terminal information identification information) from the management device 12, it determines the difference between the version information contained in the message and the version information of the terminal information (information indicating terminal information identification information) stored in the storage unit 323, on a download type basis. Here, terminal 3 sends a message (high-speed terminal status notification) to the management device 12 every 4 seconds via unicast from the transmission unit 327, notifying it of its terminal status. Download types that are determined to have a difference are included in the high-speed terminal status notification and sent as a terminal information distribution request (hereinafter referred to as DL request).

[0069] The high-speed terminal status notification sent unicast from each terminal 3 to the management device 12 includes the following items, as illustrated in Figure 6. (1) Machine number: This indicates the machine number of the gaming machine 2 to which terminal 3 is associated, and is used as the identification number of terminal 3. (2) Download request flag (DL request flag): A flag indicating a request for the distribution of terminal information on a per-download basis (distribution request information). (3) Machine data request flag: A flag used to request machine data when terminal 3 has cleared its system or when the corresponding machine number has changed. (4) Download status: A status flag indicating the download status of terminal information such as programs and content on terminal 3. (5) Version information: Version information stored in the memory unit 323 of terminal 3 (information indicating identification information of terminal information).

[0070] In some cases, hundreds of gaming machines 2 are installed in a gaming arcade, and simultaneously sending high-speed terminal status notifications could overload the in-house network 101. Therefore, in this example, a delay time from a reference time (an example of a reference timing) set by a server such as the management device 12 is set for each machine number, and the timing of high-speed terminal status notifications is slightly staggered to distribute the load on the in-house network 101. As a synchronization means, the management device 12 periodically distributes reference time information to each terminal 3, enabling synchronization of the reference time throughout the entire gaming arcade.

[0071] The management device 12 temporarily stores the high-speed terminal status notification (telegram) received from terminal 3 in the internal memory of the receiving unit 129 (management device 12). The control unit 121 queries the receiving unit 129 for new notifications (telegrams) every second. If there is a new notification, the control unit 121 reads out the high-speed terminal status notification and deletes it from the receiving unit 129.

[0072] If the control unit 121 receives a high-speed terminal status notification from terminal 3 and there is a change from a previously acquired notification, it analyzes the high-speed terminal status notification and executes processing. If a new DL request is confirmed, the control unit 121 identifies the source terminal 3 (hereinafter referred to as the DL request terminal). The distribution unit 127 distributes terminal information and a list of terminal information (distribution information) to the DL request terminal. The distribution sequence of terminal information will be described later with reference to Figures 10 to 12. When the DL request terminal receives the distributed terminal information, it performs actions such as storing it in the storage unit 323, extracting files, installing programs, and updating configuration information, thereby reflecting the received terminal information.

[0073] The structure of download requests included in the high-speed terminal status notification (Figure 6) will be explained with reference to Figure 7. If there is a difference between the version information of the management device 12 and the version information stored in the storage unit 323 of the terminal 3, the DL request flag corresponding to the download type with the difference is set to 1 and switched to on. For download types with no difference, the DL request flag remains at zero (off).

[0074] In this example configuration, terminal information corresponding to download types No. 1 to 5 in Figure 7 is managed separately as first distribution information, and terminal information corresponding to No. 6 is managed separately as second distribution information. Of the download types in the same figure, download types No. 1 to 3 are examples of general terminal information, which are download types necessary for verification work. Download types No. 4 to 6 are examples of special terminal information, which are download types that can be verified during installation in parallel with distribution, such as model-specific content.

[0075] The download types shown in Figure 7 are as follows: (1) Settings: Basic setting information for terminal 3. Includes performance information associated with the machine number. (2) Program Content List: A list of files that represent the common operating programs for the terminal. Refer to Figure 8 and see below. (3) Program content: A common operating program for all terminals. (4) Model Content List: A list of files that show content that differs for each model. Refer to Figure 9 and see below. Content information for multiple models is contained in one file. (5) Download Plan: A file that shows the distribution plan for terminal information. It includes the content to be distributed and the machine number information of the destination. (6) Device-specific content: This refers to content that differs depending on the device model and includes device information such as videos, audio, and images.

[0076] In this example, a distribution priority is set for each download type (Figure 7). In Figure 7, the lower the download type number (lower number), the higher the distribution priority. The management device 12 processes the download type with the highest priority within the game hall as the highest-priority download request (hereinafter referred to as the highest-priority DL request). The management device 12 identifies the highest-priority DL request using the procedure described below.

[0077] As described above, the high-speed terminal status notifications sent from each terminal 3 to the management device 12 are analyzed by the control unit 121 (management device 12). The analysis by the control unit 121 includes determining whether a request exists by aggregating the DL request flags for the entire store and taking a logical OR. In other words, if at least one DL request flag is set to "on" on any of the terminals 3, the management device 12 determines that there is a DL request for the download type corresponding to that DL request flag.

[0078] The management device 12 determines the highest priority download request among the download types for which a download request has been determined to exist as the "highest priority download request". If no higher priority download request is not notified from other terminals 3 during a predetermined period for aggregation (for example, 10 seconds), the "highest priority download request" is confirmed.

[0079] In this example, the management device 12 divides terminal information into multiple download types, sets a priority for each, and starts distribution from the highest priority download type across the entire gaming facility. By adopting such a configuration, even when it is necessary to update the information of some terminals 3, such as when new machines are installed, or when it is necessary to distribute files to hundreds of terminals 3, such as during the opening of a new store, it becomes possible to proceed with downloads in the appropriate order and in stages.

[0080] Furthermore, in the amusement arcade system 1 of this example, download types necessary for installation verification work, such as settings and program content (general terminal information No. 1-3 in Figure 7), are delivered with priority over download types that allow for installation verification work in parallel with distribution, such as machine content (special terminal information No. 4-6 in Figure 7). By prioritizing the delivery of download types necessary for installation verification work over download types that allow for installation verification work in parallel with distribution, the waiting time for verification work can be reduced, enabling more efficient verification work.

[0081] The management device 12 performs the following distribution process for terminals 3 (hereinafter referred to as distribution target terminals) whose DL request flag for the "highest level DL request" download type is on. For example, if the highest level DL request is "settings", it multicasts the settings information for each distribution target terminal. The multicast settings information includes individual machine number information. Each terminal 3 determines whether the distributed settings information is necessary, and if necessary, stores it in the storage unit 323.

[0082] Download types other than "Settings" are categorized into "List Type" and "Content Type," and the distribution process differs for each. The "List Type" is a file containing a list of filenames (second distribution information) that terminal 3 should store, as shown in Figure 8. After receiving the list type file, terminal 3 determines the difference between the group of files included in the list and the group of files stored by terminal 3 (information indicating the type of terminal information). If there is a difference, terminal 3 turns on the flag for the corresponding "Content Type" download type (see Figure 7).

[0083] For example, let's consider a scenario where the files in the program content list (version 1) shown in Figure 8(a) are stored in terminal 3, and the terminal information is updated as shown in the version 2 list in Figure 8(b). This figure shows an example where the file name of No. 1 has changed. In this case, the version information distribution confirms the difference in the version information of the program content list, and the corresponding download type becomes a DL request (first distribution request information).

[0084] When a list-type program content list is delivered in response to the top-level DL request, terminal 3 detects a difference in the file name of No. 1. Terminal 3 sets the program content DL request flag to "on" and sends a high-speed terminal status notification.

[0085] If the highest-level DL request is "content-type," the process proceeds as follows: First, a message (download details inquiry) for the purpose of inquiring about the details of the content where discrepancies have been found is multicast-distributed from the management device 12. Terminal 3 identifies the missing content based on the contents of the received list-type file. Missing content information (a download details notification, which is an example of second distribution request information) is unicast-distributed from Terminal 3 to the management device 12. After receiving missing content information from each terminal 3 in the gaming hall, the management device 12 multicast-distributes the corresponding content. Terminal 3 stores the missing content and completes the reception.

[0086] As shown in Figure 9, the device content consists of device programs and device content files that each terminal 3 should download. Among the content files, the device content, which is the second type of distribution information, includes large files such as video files, and is likely to take a long time to download. Therefore, in this example configuration, instead of multicast distribution targeting the first type of distribution information, a download process is performed by creating a group of distribution terminals, distributing to the representative terminal of that group, and then transferring the data among the terminals 3 belonging to the group.

[0087] Figures 9(a) and 9(b) illustrate the update of the No. 4 device content corresponding to device A. The device content before the update is "deviceA_image1.tgz", and the device content after the update is "deviceA_image2.tgz". When device content is updated in this way, the updated device content is distributed according to the distribution sequence shown in Figure 12, which will be described later.

[0088] Next, we will explain specific examples of distribution sequences for each download type, referring to Figures 10-12. Figure 10 is a flowchart of the distribution sequence for configuration information. Figure 11 is a flowchart of the distribution sequence for program content. Figure 12 is a flowchart of the distribution sequence for model content. Note that Figure 12 is divided into two parts, Figure 12A (first half) and Figure 12B (second half), due to the large number of steps involved.

[0089] The sequence for distributing configuration information when terminal 3 is installed will be explained with reference to Figure 10. In this example, UDP (User Datagram Protocol) and FTP (File Transfer Protocol) are used as the communication methods. UDP in this example includes unicast, which targets a single device, and multicast, which targets multiple devices. The processing of multicast distribution using UDP will not be explained here, but since all terminals 3 associated with the gaming machines 2 in the gaming arcade are to be targeted for distribution, a column for the second terminal is provided in Figure 10 to schematically show the situation.

[0090] In Figure 10, terminal 3, which is the target of the configuration information distribution performed when terminal 3 is installed, is referred to as terminal 1. In the following explanation of Figure 10, "terminal 3" refers to terminal 1. In the figure, dashed arrows indicate the flow of information via UDP unicast, solid arrows indicate the flow of information via UDP multicast, and dotted arrows indicate the flow of information via FTP communication.

[0091] Terminal 3 is powered on and started up after installation (S101). Upon initial startup, Terminal 3 is system-cleared, and all stored information in the memory unit 323, including version information, is cleared. After startup, Terminal 3 starts high-speed terminal status notification, notifying the management device 12 every 4 seconds. After the system clear, it turns on the machine data request flag (No. 3 in Figure 6) and requests machine data, including machine number information corresponding to Terminal 3, from the management device 12 (S102).

[0092] The management device 12 transmits unit data via FTP communication in response to a request from terminal 3 (S103), updating the unit data on terminal 3 (S104). The management device 12 also periodically distributes version information via multicast (S105). Terminal 3 periodically determines whether the newly received version information from the management device 12 matches the version information stored in the storage unit 323.

[0093] After the system is cleared, all version information on terminal 3 is treated as 0, so a mismatch with the version information shown in Figure 5 distributed from the management device 12 is detected (S106). Terminal 3 turns on the DL request flag corresponding to the download type in which the mismatch was detected, and sends a high-speed terminal status notification to the management device 12 via unicast, in which the DL request flags other than the download plan (No. 5 in Figure 7) are turned on (S107).

[0094] When the management device 12 receives a new DL request while in a download request monitoring state (hereinafter referred to as the DL request monitoring state), it starts aggregating the DL requests (S108). For example, during a predetermined aggregation period such as 10 seconds, it receives notifications of DL requests from each communicable terminal 3 in the gaming hall, and after the aggregation period ends, it identifies the highest-level DL request as "Setting" (No. 1 in Figure 7) (S109). The management device 12 creates a setting file for each distribution target terminal that sent "Setting" as a DL request and distributes it via multicast (S110).

[0095] Figure 10 illustrates the case where only terminal 3, the first terminal, requests to download the "settings." However, if multiple terminals 3 request to download the "settings," a configuration file will be distributed for each target terminal. The configuration file sent will have serial number information and new version information associated with it. When a target terminal receives the configuration file sent via multicast, it determines from the serial number information whether it is a missing file for its own terminal and reflects the settings and version information on its own terminal (S111).

[0096] In terminal 3, a version mismatch is detected because the version information other than the settings has not yet been updated (S112). Terminal 3 notifies the management device 12 of the high-speed terminal status notification that all flags except the settings (No. 1 in Figure 7) and the download plan (No. 5 in the same figure) are on (S113). The management device 12 starts aggregating DL requests (S114), identifies the highest-level DL request in the same way as in steps S108 and S109 above, and performs distribution according to the identification result (S115).

[0097] As described above with reference to Figure 10, in this example configuration, the distribution request for terminal information, including DL requests, is sent using high-speed terminal status notification. This allows for a shorter aggregation time for information from all terminals 3 in the gaming facility, enabling efficient determination of distribution files. Furthermore, in this example configuration, distribution files are delivered via multicast using UDP, a connectionless protocol. This reduces communication time due to connection and reception confirmation compared to distribution that requires a connection. Reducing communication time improves the efficiency of file distribution, allowing file distribution to be completed relatively quickly even in large-scale gaming facilities with hundreds of terminals 3 installed simultaneously.

[0098] Next, using the case where the program content is updated on the management device 12 as an example, the distribution sequence for download types of list-type and content-type files will be explained with reference to Figure 11. As with Figure 10, the column for the second terminal will only schematically show multicast distribution, and the explanation of the process will be omitted. As with Figure 10, in Figure 11, terminal 3, which is the target of the distribution of the program content, is referred to as the first terminal. In the following explanation of Figure 11, terminal 3 is the first terminal. In the figure, dashed arrows indicate the flow of information via UDP unicast, and solid arrows indicate the flow of information via UDP multicast.

[0099] Figure 11 shows a processing sequence that assumes the distribution of program content from the list in Figure 8(a) to terminal 3 has been completed, and that the management device 12 has not received any DL requests from any of the terminals 3 installed in the gaming area.

[0100] The distribution sequence in Figure 11 starts with a process (S201) in which the program content "OS0001.tgz" stored in the storage unit 123 of the management device 12 is updated to "OS0002.tgz" based on instructions from the management device 12 or a management device higher than the management device 12 (not shown).

[0101] The update from "OS0001.tgz" to "OS0002.tgz" updates the program content list to the list shown in Figure 8(b), and the version information of the program list content (see Figure 5) becomes version 2 (S202). After such an update, the management device 12 multicasts the version information (first distribution information) (S203). When terminal 3 receives this version information, it detects a mismatch in the program content list version information by checking for a match with the version information stored in the storage unit 323 (information indicating terminal information identification information) (S204).

[0102] Terminal 3 sets the flag for Program Content List No. 2 (see Figure 7) among the DL request flags to "on" and sends a high-speed terminal status notification (S205). When the management device 12 receives a new DL request, it starts aggregating DL requests from all terminals 3 (S206). After a predetermined aggregation time (for example, 10 seconds) has elapsed, it identifies the highest-level DL request as "Program Content List" (S207).

[0103] The management device 12 multicasts a version 2 program content list, as illustrated in Figure 8(b), corresponding to the highest-level DL request (S208). When terminal 3 has finished receiving the new program content list, it performs a match check between the program content included in the received list (second distribution information) and the program content stored in terminal 3 (information indicating the type of terminal information), and as a result, detects a mismatch in the file name of No. 1 (S209).

[0104] Terminal 3 sets the flag for Program Content (see Figure 7), which is DL request flag No. 3, to "on" and sends a high-speed terminal status notification via unicast (S210). Management device 12 aggregates the DL requests (S211) and identifies the highest-level DL request as "Program Content" (S212).

[0105] The management device 12 multicasts a download details query associated with the DL request flag (S213). When terminal 3, whose DL request flag matches, receives this download details query, it sends information about the missing "OS0002.tgz" (No. 1 in Figure 8(b)) to the management device 12 as a download details notification (second distribution request information) (S214).

[0106] When the management device 12 finishes receiving the download details notification from terminal 3 that requested the download details query, it identifies the aggregated result as "OS0002.tgz" (S215), associates it with the No. information (number information) from the program content list, and multicasts "OS0002.tgz" (S216). When terminal 3 whose download details notification and No. information match finishes receiving "OS0002.tgz" (S217), terminal 3 restarts (S218), extracts the received "OS0002.tgz", and executes the installation process (S219). After installation, no mismatch is detected by the version information matching check (S220), and terminal 3 sends a high-speed terminal status notification with all DL request flags off (S221). When there are no more DL requests from any terminal 3 in this manner, the management device 12 transitions to the DL request monitoring state (S222).

[0107] As described above with reference to Figure 11, in this example configuration, the management device 12 determines whether or not program or content distribution is necessary based on version information, and distributes a list-type download file according to the determination result. With this configuration, if the version information matches, the need to distribute a list-type download file can be reduced, and the download process can be carried out efficiently even when there is a large amount of content.

[0108] Furthermore, in this example configuration, if a system clear (see Figure 10) occurs even while program content is being delivered, the highest-level DL request is updated to the higher-priority "settings" request, interrupting the delivery of program content and executing the delivery of settings information. With this configuration, high-priority download types can be delivered quickly.

[0109] Next, using the case where the management device 12 updates the machine content as an example, the distribution sequence of the second distribution information, which is the machine content, will be explained with reference to Figure 12. In the figure, the first to third terminals are all terminals 3 corresponding to the gaming machine 2 of machine A. The sequence in Figure 12 is based on the premise that the download of content No. 1 to 4 corresponding to machine A among the machine content shown in Figure 9(a) has been completed, and no download requests have been received from the other terminals 3. In the figure, the dashed arrows indicate the flow of information via UDP unicast, the solid arrows indicate the flow of information via UDP multicast, and the dotted arrows indicate the flow of information via FTP communication.

[0110] Using the update of No. 4 shown in Figure 9(b) as an example of a device content update, the distribution sequence of device content will be explained with reference to Figure 12. As mentioned above, Figure 12 is divided into two parts, Figure 12A (first half) and Figure 12B (second half), due to the large number of steps. Figure 12A shows the processing steps from steps S301 to S315. Figure 12B shows the processing steps from step S316 onwards.

[0111] Steps S301 to S315 in Figure 12A are processed in the same way as steps S201 to S215 in Figure 11. However, when determining the match of model content in step S309, the targets for determination are the files containing the model name corresponding to the terminal from the model content list (first distribution information) distributed in step S308, and the model content stored in terminal 3 (information indicating the type of terminal information). For example, if the model content list in Figure 9(b) is distributed, each terminal 3 associated with model A will perform a match check on files No. 1 to 4 in Figure 9(b). Files No. 5 and later do not contain "model A" and are therefore excluded from the match check.

[0112] The download details notification from each terminal 3 requests the device content No. 4 "Device A_Image 2.tgz" in Figure 9(b) (S314). When the management device 12 receives the download details notification (S315), it creates a download plan as a distribution plan including inter-terminal transfer based on the notification (S316). In this example, the management device 12 identifies the first terminal as the representative terminal of the distribution terminal group consisting of the first to third terminals, and creates a download plan that transfers between terminals in the order of first terminal → second terminal → third terminal after distribution to the first terminal. The third terminal is a terminal 3 located at the end of the terminal where there is no destination terminal 3.

[0113] When the management device 12 creates a download plan, it updates the version information (see Figure 5) from 0 to 1 (S316). The updated version information is multicast distributed from the management device 12 (S317). Each terminal 3 (terminals 1 to 3) that receives the updated version information determines whether the version information of the download plan matches 0 and detects a mismatch (S318). Each terminal 3 notifies the download plan No. 5 (see Figure 7) and the model content No. 6 as DL request flags (S319).

[0114] When the management device 12 receives a new DL request, it aggregates the DL requests (S320) and identifies the top DL request as the download plan (S321). The management device 12 multicasts the download plan, which is a list-type file, and updates the version information from 1 to 0 after a predetermined time (for example, 1 minute) has elapsed since the creation of the download plan in step S316 (S322). Note that the management device 12 checks whether the version information of the download plan matches 0. Therefore, if the version information is not updated, the top DL request will not change from the download plan until the update is performed.

[0115] After the version information of the download plan is updated, the management device 12 distributes the version information, and the top-level DL request is identified as "machine content" (S323-S327). When this top-level DL request transitions from "download plan" to "machine content," the management device 12 begins distributing the machine content based on the download plan.

[0116] First, the management device 12 distributes "Model A_Image 2.tgz" (No. 4 in Figure 9(b) related to the DL request) to the first terminal via FTP communication (S328). Once the first terminal has finished receiving the content, it is transferred from the first terminal to the second terminal via FTP communication (S329). Furthermore, the same transfer as in S329 is performed from the second terminal to the third terminal.

[0117] Terminals 1 through 3, while transmitting and receiving via FTP, will set to download status (No. 4 in Figure 6) via high-speed terminal status notification and notify that they are downloading. After communication is complete, they will notify that they are in standby status via high-speed terminal status notification. When Terminals 1 and 2 have finished receiving the device content, they will turn off all DL request flags in the high-speed terminal status notification, and if they are sending the device content to the next terminal 3 via FTP, they will notify that they are in download status (No. 4 in Figure 6), and after transmission they will notify that they are in standby status (S330). Terminal 3, which is at the end of the transfer sequence and does not have a destination for the device content to be sent via FTP, will turn off all DL request flags in the high-speed terminal status notification and immediately notify that it is in standby status (S331) when it has finished receiving the device content.

[0118] When the management device 12 confirms via high-speed terminal status notification that there are no longer any terminals 3 in the gaming area whose download status (No. 4 in Figure 6) is in the middle of downloading (S332), it transitions to the DL request monitoring state (S333).

[0119] For terminal information such as device content, which is large in size and takes a long time to distribute, multicast distribution requires slow speed to prevent packet loss. In contrast, the configuration in this example makes it possible to perform high-speed distribution with reduced packet loss by establishing a connection via FTP communication and then distributing the data.

[0120] In this example, in the amusement arcade system 1, unlike the DL request from terminal 3, an "external DL request" may occur, in which the download is initiated by the management device 12 itself or by an instruction from another higher-level node (higher-level management device). Figure 13 is a flowchart showing the processing flow by the management device 12 when an "external DL request" occurs.

[0121] An external download request is a new instruction regarding the distribution of terminal information that occurs when the administrator of the gaming arcade updates the configuration information in the management device 12, or when the latest version of the content file is downloaded from the external server 100, etc. When an external download request occurs, the version information for the corresponding download type is first updated (S401). The management device 12 compares the priority of the highest-level download request at the time the "external download request" occurs with the priority of the download type corresponding to the "external download request" and determines whether the priority of the external download request is higher or lower (S402).

[0122] If the priority of the external DL request is higher (S402:YES), the management device 12 stops the distribution process for the highest priority DL request (S403) and performs the distribution of the download type corresponding to the external DL request (S404). Once the distribution for the external DL request is completed, the management device 12 moves to normal processing, which involves aggregating the DL requests from terminal 3 and identifying the highest priority DL request.

[0123] On the other hand, if the priority of an external DL request is not higher than that of the highest-priority DL request (S402: NO), the management device 12 rejects the external DL request (S405) and continues normal processing based on the highest-priority DL request. Thus, in the amusement arcade system 1 of this example, even if an external DL request is rejected, the version and content file updates on the management device 12 side are completed, so there is no disruption to distribution to terminal 3 through normal processing.

[0124] Thus, in the amusement arcade system 1 of this example, even when an "external download request" like the one described above occurs, the distribution is carried out according to the priority of the download type. Therefore, program files necessary for verification work such as settings and operating programs are downloaded in the appropriate order, and the waiting time before the verification work can begin can be reduced.

[0125] Next, the procedure for creating a download plan when distributing device-specific content will be explained with reference to Figures 14 to 16. The management device 12 receives download detail notifications from each terminal 3, as shown in step S315 in Figure 12A above, and performs aggregation of device-specific content that needs to be distributed.

[0126] Figure 14 shows an example of the aggregation results of model content by the management device 12. The management device 12 aggregates each model content by associating it with the serial numbers of the distribution requesting terminals, as shown in the requesting serial number list in the same figure. For model content in which the number of terminals included in the requesting serial number list exceeds 10, the distribution requesting terminals are divided into multiple groups so that the number of terminals does not exceed 10. For example, No. 1 in Figure 14(a) ("Model A_Program 2.tgz") is model content requested by a total of 25 terminals 3 from serial number 1 to 25. Therefore, the total of 25 terminals 3 from serial number 1 to 25 are divided into 3 groups as shown in Figure 14(b) No. 1 to 3 so that the number of terminals in the requesting serial number list is a maximum of 10.

[0127] As shown in Figure 14(b), the management device 12 creates groups based on pairs of filenames of the machine content and the requested serial number list, and then sorts the groups in descending order of the number of terminals in the requested serial number list. If the number of terminals in the requested serial number list is the same, the groups are further sorted in descending order of file size.

[0128] The management device 12 outputs the results of the group rearrangement described above as a download plan file, as illustrated in Figure 15. In the download plan file, each line for each type of content, such as "Model A_Program 2.tgz" or "Model B_Image 2.tgz," contains a sequence of machine numbers representing the relay-style distribution order. This sequence of machine numbers represents the distribution order, with the leftmost machine number being the first, and terminal 3 being the representative terminal, which is the distribution terminal (the terminal to be distributed to) from the management device 12.

[0129] As shown in step S322 in Figure 12B, when the download plan file is distributed, the management device 12 sequentially distributes the model content based on that plan. For example, the first line of the download plan in Figure 15, "Model B_Image 2.tgz", is first distributed via FTP to terminal 3 in the 101 series, which is the representative terminal, as shown in Figure 16. Subsequently, it is distributed in a relay format up to terminal 110, in the 102 series, 103 series, and so on. Once distribution to terminal 101, the representative terminal for the first line in Figure 15, is complete, the management device 12 sequentially switches the distribution terminals to the representative terminal for the second line, the third line, and so on. In this example configuration, only terminal 3, the leftmost terminal in the download plan file in Figure 15, which is the representative terminal for each line, becomes a distribution terminal that receives distribution directly from the management device 12.

[0130] As described above, when distributing device content in a relay format, if there are many terminals in a group, it will take time to complete the transfer. Therefore, in this example, the management device 12 performs distribution in order from the group with the most terminals. Similarly, if the file size to be distributed is large, it will take more time to complete the transfer, so the management device 12 performs distribution in order from the group with the largest file size of device content.

[0131] Furthermore, if the number of terminals in a group becomes excessive, the time until download completion will increase. Therefore, in this example, an upper limit is set on the number of terminals in the requesting terminal list. In this case, the number of terminals receiving the model content can be distributed in a relay format, shortening the time until download completion. Moreover, when distributing multiple model contents in any one download plan, for example, in Figure 15, the first and fifth rows are groups that distribute the same model content (model B_image2.tgz), while the second to fourth rows, between the first and fifth rows, contain groups with files different from those in the first and fifth rows. The groups in the first and fifth rows are examples of the first and second groups, which are divided by the upper limit on the number of terminals. The groups in the second to fourth rows are examples of a third group, where the type of terminal information to be distributed is different from that of the first and second groups. Thus, in this example, the distribution order is determined not by the type of model content, but by the number of terminals included in the group, enabling efficient distribution.

[0132] If, after distribution has started according to the download plan, the destination terminal is determined to be an abnormal terminal due to reasons such as communication failure or failure to transition to a standby state during the download, the device content will be transferred to terminal 3, which is set as the next terminal in the download plan. For example, in the group in row 7 of Figure 16, the transfer from terminal 101 to terminal 105 has not been completed. If terminal 105 is determined to be an abnormal terminal, the transfer from terminal 101 will proceed to terminal 106, which is the next terminal in the sequence after terminal 105. With this configuration, even if an abnormal terminal occurs, priority can be given to transferring to a normal terminal 3 (e.g., terminal 106).

[0133] Furthermore, if any terminal 3 is determined to be an abnormal terminal during information distribution, not just during the distribution of device-specific content, the machine number of the abnormal terminal 3 will be announced on the management device 12's monitor or via audio, prompting action to be taken regarding the abnormal terminal. Also, once the abnormal state is resolved and the terminal returns to a normal state, the terminal 3 will notify the device content download request flag corresponding to step S310 in Figure 12A, and information will be distributed again to the previously abnormal terminal 3 using the normal distribution sequence.

[0134] In the amusement arcade system 1 of this example, terminal information that requires a lot of time to download or differs from machine to machine, such as machine content, is grouped in the download plan as shown in Figures 12 and 14-16, and downloaded in parallel for each group via a representative terminal. On the other hand, terminal information such as configuration information that does not require much time to download or differs from terminal to terminal, or list-type files that are common to many terminals, is downloaded in parallel to all terminals 3 via multicast distribution without going through a representative terminal, as shown in Figures 10 and 11. In the amusement arcade system 1 of this example, efficient file updates for terminals are possible by using different download processes depending on the target terminal information.

[0135] The amusement arcade system in this example manages terminal information by distinguishing between general terminal information, which is a download type necessary for checking settings and program content, and special terminal information, which is a download type that does not require checking machine content or download plans, and allows for installation-time checking in parallel with distribution. It can also distribute distribution information regarding terminal information to be distributed to terminal 3 (gaming device). In this amusement arcade system 1, by comparing this distribution information with information indicating the terminal information associated with the gaming device, a DL request (distribution request information) is identified that can identify at least one of the following: terminal information that needs to be distributed, or whether or not distribution of terminal information is necessary, and this is notified to the management device 12.

[0136] In the amusement arcade system 1, terminal information is distributed in response to download requests, with general terminal information given priority over special terminal information. When terminal 3 receives general terminal information, it can perform predetermined processing related to the distributed general terminal information, even while special terminal information is being distributed. In other words, when a download type necessary for checking settings or program content is distributed, it is possible to perform the checking of settings or program content even while special terminal information is being distributed. For example, when some terminals 3 need to update their information, such as when new machines are installed, or when distributing files to hundreds of terminals 3 for the opening of a new store, the amusement arcade system 1 in this example can proceed with downloads in stages in the appropriate order, reducing the waiting time until the checking process can begin. Thus, the amusement arcade system 1 in this example is an excellent system that can efficiently distribute both general and special terminal information.

[0137] In this example of amusement arcade system 1, the download priority for basic configuration information and operating programs is set higher than that for machine content. Therefore, the download of basic settings can be completed first, and it is possible to efficiently proceed with the verification of settings and program content in parallel with the download of machine content, which is large in size and takes time to download.

[0138] The amusement arcade system 1 in this example is configured to determine whether programs and content are needed based on version information, as shown in Figure 5, and to distribute a list-type download (Figure 7) according to the determination result. With this configuration, when it can be determined that the content is not needed based on the version information, the need to distribute a list-type download can be reduced, and even when there is a large amount of content, the download process can be carried out efficiently.

[0139] In this example configuration, if a new download item is delivered from an external source while a download is in progress in response to the top-level DL request, the top-level DL request and the delivery instruction are compared, and the item with the higher priority is delivered. Therefore, even if a new delivery instruction is received, the download can proceed in the appropriate order and in stages, reducing the waiting time before the verification process begins.

[0140] The amusement arcade system 1 interrupts the ongoing distribution process and performs distribution corresponding to the latest top-level DL request when the top-level DL request changes. With this configuration, even if some terminals 3 are initialized during the distribution of machine content, for example, the waiting time until the verification of configuration information can be started can be reduced.

[0141] Furthermore, the amusement arcade system 1 in this example sets a delay time on a per-terminal basis and sends high-speed terminal status notifications so that the notification timing can be distributed, thereby suppressing load concentration on the in-house network 101 and improving the stability of communication.

[0142] In this example, the amusement arcade system 1 manages terminal information distributed from the management device 12 to terminals 3 (gaming devices) by dividing it into first distribution information and second distribution information. First distribution information is terminal information that is distributed regardless of whether it is the representative terminal. Second distribution information is terminal information that is distributed on the condition that it is the representative terminal of a group of distribution terminals, and is subsequently transferred between distribution terminals.

[0143] With this configuration, second-tier distribution information, such as device-specific content that takes a long time to download or differs from device to device, can be downloaded in parallel on a group basis via a representative device. On the other hand, first-tier distribution information, such as configuration information that does not take much time to download, or configuration information common to many devices 3, or list-type information, can be downloaded in parallel to all distribution devices, regardless of whether it is the representative device, i.e., without waiting for the representative device to finish downloading. With this configuration, file updates on each device 3 can be completed more efficiently.

[0144] The configuration in this example includes a first distribution means that distributes data from the management device 12 as the source, regardless of whether the destination terminal is a representative terminal or not, similar to multicast distribution, and a second distribution means that distributes data only if the destination terminal is a representative terminal, similar to distribution based on a download plan. In this example, the data distributed by the first distribution means is managed as first distribution information, and the data distributed by the second distribution means is managed as second distribution information. In this example, for example, second distribution information is exemplified as model content, and first distribution information as terminal information other than model content, but it is also possible to move from first distribution information to second distribution information, or vice versa. That is, even if the information is the same, if it is distributed from the management device 12 on the condition that the destination terminal is a representative terminal, it is second distribution information, and if it is distributed regardless of that condition, it is first distribution information.

[0145] In the amusement arcade system 1 of this example, when distributing the second distribution information, the machine content is distributed to the representative terminal of each group in order of the number of terminals included in the group or the size of the files to be distributed. In other words, in this amusement arcade system 1, distribution is prioritized to groups that require more time to complete the transfer due to the large number of terminals involved in inter-terminal transfer, or to groups that require more time to complete the transfer due to the large size of the files to be transferred between terminals. By prioritizing the distribution of terminal information to groups that require more time to complete the transfer in this way, the time required to complete distribution to all terminals 3 can be shortened.

[0146] Furthermore, in the amusement arcade system 1 of this example, when the same type of content is to be distributed, the group is divided so that the number of distribution terminals does not exceed the upper limit (10 terminals in this example). In addition, the distribution order of groups distributing content from other types of games may be interrupted between the groups that have been divided according to the number of distribution terminals.

[0147] For example, in the example shown in Figure 15, the group containing the same program, "Model A_Program 2.tgz," is divided into three parts, and the distribution order of the model images, "Model A_Image 2.tgz" and "Model B_Image 2.tgz," is interrupted between the second and third divided groups. This is because the third group, which contains "Model A_Program 2.tgz," has 5 distribution terminals, while the groups containing the model images, "Model A_Image 2.tgz" and "Model B_Image 2.tgz," have 6 distribution terminals. In this configuration, the time required to complete distribution to all terminals 3 can be shortened by appropriately distributing the transfer time regardless of the type of terminal information.

[0148] In this example configuration, if an abnormal terminal occurs that cannot complete the transfer between terminals, the data is transferred to the next terminal, terminal 3. For example, even if an abnormal terminal occurs that can communicate but cannot complete the reception due to a system malfunction, priority can be given to transferring to the normal terminal 3. In this way, when an abnormal terminal occurs that cannot complete the transfer between terminals, the machine number of the abnormal terminal is notified on the monitor of the management device 12 or by voice. In this example configuration, such notification appropriately supports the response of the arcade staff to the abnormal terminal. If the arcade staff respond appropriately and the abnormality is resolved, terminal information can be properly distributed to the distribution terminal that was the abnormal terminal. Thus, in the arcade system 1 of this example, even if an abnormal terminal occurs during transfer between terminals, the transfer of files, etc., is not interrupted. Furthermore, the notification of abnormal terminals by the management device 12 enables the arcade staff to take prompt action.

[0149] Alternatively, the following configurations may be adopted instead of, or in addition to, the configuration in this example. Furthermore, the following configurations may be combined as appropriate. In this example, the management device 12 illustrates a configuration in which it distributes terminal information in response to the receipt of a high-speed terminal status notification. Alternatively, even without receiving a high-speed terminal status notification, terminal information may be sent to all terminals 3 if the basic configuration information or operating program, which is necessary for the verification process, is updated. Furthermore, when distributing model-specific content, the management device 12 may manage model information in advance and selectively send content corresponding to the model by determining it on the management device 12 side.

[0150] In this example, a configuration is shown in which a list file is sent to terminal 3 that has been determined to have a version information difference based on the distribution of version information from the management device 12, and terminal 3 determines whether there is a difference in the content contained within the list file. Alternatively, all content files contained in the list file may be sent from the management device 12 as soon as a version information difference in the list file is confirmed.

[0151] Based on the version information transmitted from terminal 3, the management device 12 may determine the differences in version information and send a list-type file corresponding to the determination result, or it may send all content-type files included in the said list-type file.

[0152] The download types shown in Figure 7 are examples, and various download types can be set. Furthermore, the example download types can be further subdivided. For example, for machine content linked to a specific gaming machine model, terminal information necessary for wiring work, such as information indicating the wiring connection between the terminal and the gaming machine, can be set as "wiring information" and distributed as a regular content file via multicast.

[0153] In this example, we have illustrated a case where the transfer order is determined in a relay format so that the destination terminal is terminal 1 when formulating the download plan. However, multiple destination terminals may be set, or terminals that are not in the next position in the transfer order may be designated as destinations. Alternatively, the transfer may be performed in a format where the transfer is performed to any of the terminals 3 belonging to the group without specifying a transfer order.

[0154] Figures 12 and 14-16 illustrate device content as the target for relay transfer between terminals 3 based on the download plan, but terminal information other than device content may also be used as the target. Figures 14-16 illustrate the case where download plan group settings are made based on the aggregated results of download detail notifications, but groups may be specified in advance, such as by device model.

[0155] In this example, as shown in Figure 15, we illustrate cases where the type of terminal information differs, such as when the target model of the content or the type of content within the model differs. However, other cases such as differences in information capacity or differences in download type, such as program content and model content, are also acceptable. In this example, we illustrate how to determine the distribution order based on the number of devices in the group and the size of the files to be distributed, but you may also determine the distribution order based on either one of these criteria.

[0156] The settings information for the management device 12 and terminal 3 (gaming device) can be set by the administrator through manual input, or they can be pre-configured by the manufacturer of the management device 12 and terminal 3, or they can be downloaded from an external server, such as the chain store headquarters, and configured. In this case as well, the settings will be those entered through manual input on the server. Of course, past game data can also be used as reference values.

[0157] The game information indicating the game status of game machine 2 may be identified directly by the input signal or indirectly by using a calculation formula. The numbers, number of digits, and items shown in this example are illustrative; you may use any numbers you like. Furthermore, regarding "greater than" and "exceeding," either can be used, and expressions such as "reached" can correspond to either "greater than" or "exceeded." The same applies to "less than" and "less than," and expressions such as "did not reach" can correspond to both.

[0158] In this example, we have used a so-called smart pachinko machine, which manages game value solely through data, as the target gaming machine. However, the target can also be slot machines, or conventional payout-type pachinko machines or slot machines. The term "value," as in "game value," is used to encompass both the acquired value managed by data as in this example and the game medium that is paid out.

[0159] Some of the processing performed by terminal 3 (gaming device) may be carried out by other gaming devices such as the management device 12 and the scoring device 4, or by the relay device 106, etc., or the entire process may be performed by terminal 3 alone. Furthermore, the example configuration may be changed as appropriate depending on the settings, the example configuration including modified versions may be combined in any way, and configurations may be excluded as appropriate.

[0160] Although specific examples of the present invention have been described in detail as shown in the examples above, these examples only disclose an example of the technology covered by the claims. Needless to say, the claims should not be interpreted restrictively based on the configuration or numerical values ​​of the specific examples. The claims encompass technologies obtained by various modifications, changes, or combinations of the above examples using prior art or the knowledge of those skilled in the art. [Explanation of Symbols]

[0161] 1. System for amusement facilities 100 External server (higher-level management device) 101 On-site network (network) 106 Relay device 12 Management device (management means, destination identification means, group means, terminal information distribution means, distribution information distribution means, priority means, synchronization means, notification means) 120 Interface Circuit 121 Control Unit 123 Storage section 125 Data Management Department 127 Distribution Department 129 Receiving Unit 2 Gaming machines 3. Terminals (information display devices, gaming devices, identification means, notification means, terminal processing means, transfer means, abnormal terminal identification means) 320 Interface Circuit 323 Storage section 327 Transmitter 329 Receiving Unit 4. Score Processing Device

Claims

1. In a gaming arcade system in which a gaming device installed in conjunction with a gaming machine and a management device that serves as the source of terminal information that can be associated with the gaming device are mutually connected to form a network, A management means for managing terminal information by distinguishing between general terminal information related to a predetermined process in the gaming device and special terminal information different from the general terminal information, A distribution information distribution means capable of distributing distribution information regarding terminal information to be distributed to a gaming device, A means for identifying distribution request information that can identify at least one of the following: the terminal information that needs to be distributed to the gaming device, and whether or not the distribution of terminal information is necessary, by comparing the distribution information distributed by the distribution information distribution means with information indicating terminal information associated with the gaming device. A notification means for notifying the management device of the distribution request information identified by the aforementioned identification means, A terminal information distribution means that distributes the terminal information in response to the distribution request information notified by the notification means, A priority means that causes the general terminal information to be distributed to the terminal information distribution means with priority over the special terminal information, A gaming system comprising terminal processing means capable of executing the predetermined processing related to the general terminal information that has been distributed to a gaming device, even if the special terminal information has been distributed.

2. The general terminal information includes at least one of the following: terminal setting information indicating setting information for executing the predetermined process, and basic operation information including an operation program for executing the predetermined process. The amusement arcade system according to claim 1, wherein the special terminal information includes different model content information for each model of amusement machine corresponding to the amusement device.

3. The management means manages the identification information of the distribution information, The information indicating the terminal information associated with the gaming device includes information indicating identification information of the terminal information and information indicating the type of the terminal information. The distribution information distribution means is capable of distributing: first distribution information, which is distribution information associated with the identification information; and second distribution information, which is distribution information indicating a list of terminal information that can be distributed by the terminal information distribution means. The identification means identifies a first distribution request information that can determine whether or not terminal information needs to be distributed by comparing the identification information of the first distribution information distributed by the distribution information distribution means with the identification information of the terminal information associated with the gaming device, while identifying a second distribution request information that can determine which terminal information needs to be distributed to the gaming device by comparing the second distribution information distributed by the distribution information distribution means with information indicating the type of terminal information associated with the gaming device. The second distribution information is distributed when it can be identified from the first distribution request information that distribution of terminal information is necessary. The amusement arcade system according to claim 1 or 2, wherein the terminal information distribution means is to distribute terminal information that can be identified by the second distribution request information.

4. The priority means, after the terminal information distribution means has started the terminal information distribution process, determines which of the terminal information for which a new instruction to distribute terminal information is given from at least one of the management device and a management device higher than the management device, and determines which to prioritize according to the result of the determination, in the event that a new instruction to distribute terminal information is given from the management device and a management device higher than the management device, and the system for a game arcade according to claim 1 or 2.

5. The amusement arcade system according to claim 4, wherein the terminal information distribution means interrupts the distribution of terminal information being processed and performs the distribution of the preferred terminal information when terminal information that takes precedence over the terminal information being distributed is identified after the start of the terminal information distribution process.

6. The system includes a synchronization means for synchronizing the reference timing of notifications from multiple notification means, The amusement arcade system according to claim 1 or 2, wherein the notification means sets a delay time from the reference timing on a per-notification means basis so that the notification timing is distributed when the notification means notifies the distribution request information at a predetermined interval.

Images