JP2010233680A - Game parlor management system and game parlor management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To save a moving image of an event which a game parlor wants to remain for the future without spending time and effort. <P>SOLUTION: In a camera T/C100, an event kind, time and date when an event has occurred, and a machine number are stored as an event history, a storage destination of a moving image file according to the machine number of a machine in a parlor whose image is picked up is stored every image pickup date, the event kind to be an exemption of a moving image deletion condition is stored as an exemption setting, a stored destination of moving image files at the image pickup date which meets the moving image deletion condition, from among the image pickup dates of moving images stored every storage destination is specified as an object to be deleted, an event history stored as an exemption setting and including the event kind to be the event history which has occurred at the image pickup date satisfying the moving image deletion condition is extracted, and a moving image in a prescribed cut-out section based on an event occurrence time of day acquired as the event history from the moving image whose storage destination is specified and which corresponds to the machine number extracted as the event history is cut out. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention is connected to an in-store device installed in an amusement store, one or a plurality of in-store devices and an image pickup device provided in the vicinity thereof, and stores a moving image picked up by each image pickup device. The present invention relates to a game hall management system and a game hall management method that include an image management device that performs the same.

  Traditionally, amusement stores that provide pachinko games and pachislot games have been exposed to fraudulent acts such as fraudulent attacks and theft. For example, using a sensory device to illegally trigger a special prize on a gaming machine, inserting a foreign object instead of money to illegally throw out gaming media from a pedestal machine, or counting using a rake or the like with a counter Unauthorized Goto that causes the sensor to illegally count up the count value, and theft such as theft that the pre-paid card or other value-added game recording medium is removed while the original owner is away The act is done by stealing the eyes of the staff.

  In order to suppress such evidence of fraud and to identify fraudsters, an image pickup device is arranged so as to be able to pick up players who use various in-store equipment such as gaming machines, interbank machines and counters. A technique has been devised in which images taken by an apparatus are stored, and an image at the time of fraud is searched and displayed from the stored images (see, for example, Patent Document 1).

JP 2005-110788 A

  However, the above-described conventional technique has a problem that it takes much time to save a moving image of an event that the amusement store wants to keep for the following, as described below.

  In other words, the accumulated moving image has an older date and time as time elapses, such as when the storage capacity reaches a certain amount, or when it reaches the date and time (for example, after the end of business) that becomes the delimiter of predetermined moving image organization Since there is a moving image to be retained, it is necessary to find and save the moving image of the corresponding event portion from the accumulated moving images.

  When trying to save a moving image related to a specific event, search the log related to that event from another system, visually check the event occurrence time based on the search results, and then use that time as a reference for the moving image. It is necessary to determine the moving image corresponding to the event while playing the video, but if the moving image around the visually confirmed time is not the target, it is necessary to start again from the log search of another system, corresponding to the target event It takes a lot of time and effort to find a moving image part.

  In addition, when trying to save the same or different types of moving images comprehensively, the time spent to find the moving images of the events to be saved is immeasurable. There is also a high possibility of forgetting it, and in the worst case, it may be deleted and cannot be recovered.

  Therefore, the present invention has been made to solve the above-described problems (problems) of the conventional technology, and it is possible to easily save a moving image of an event that an amusement store wants to keep for the subsequent event. An object is to provide a game hall management system and a game hall management method.

  In order to solve the above-described problems and achieve the object, a game hall management system according to the present invention is provided so that an in-store device, one or a plurality of in-store devices, and their surroundings can be imaged. An image management device that is connected to the image pickup device and stores a moving image picked up by each image pickup device, wherein the image management device is an event of an event that occurs in the in-store device Event history storage means for storing a type, an event occurrence date and time when the event has occurred, and an in-store device identifier for uniquely identifying the in-store device in which the event has occurred as an event history, and in-store devices to be imaged for each imaging date A moving image management information storing means for storing a moving image storage location for each in-store device identifier assigned to the device as moving image management information; and deleting the moving image Application exclusion setting storage means for storing an event type to be excluded as a moving image deletion condition as application exclusion setting, and the moving image deletion condition among the moving image capturing dates stored by the moving image management information storage means A deletion target specifying unit that specifies a storage location of a moving image of an imaging date as a deletion target, and an event history that occurred on an imaging date that satisfies the moving image deletion condition, and is stored as an application exclusion setting by the application exclusion setting storage unit An application exclusion history extraction means for extracting an event history including the event type from the event history storage means, and a moving image whose storage destination is specified by the deletion target specifying means, and an event history by the application exclusion history extraction means The event acquired as the event history from the moving image corresponding to the in-store device identifier extracted as And having a moving image cutout unit for cutting out a moving image of a predetermined cutout section which bets occurrence time as a reference.

  Further, the game hall management system according to the present invention, in the above invention, stores a cutout moving image in which the moving image cut out by the moving image cutout unit is stored in a predetermined cutout moving image storage unit in association with the event history. And a moving image deletion unit that deletes the moving image whose storage destination is specified by the deletion target specifying unit after the cut out moving image is stored by the extracted moving image storage unit.

  In the game hall management system according to the present invention as set forth in the invention described above, the moving image cutout unit changes the cutout section according to an event type included in the event history extracted by the exemption history extraction unit. It is characterized by doing.

  In addition, the game hall management method according to the present invention is connected to an in-store device disposed in a game store, one or a plurality of in-store devices, and an imaging device provided so as to be able to image the periphery thereof, and each imaging device. A game hall management system applied to a game hall management system having an image management device for storing a moving image captured by the image management device, wherein the image management device has an event type of an event occurring in the in-store device, the event An event history acquisition step for acquiring an event occurrence date and time and an in-store device identifier for uniquely identifying the in-store device in which the event has occurred as an event history, and given to the in-store device to be imaged for each imaging date The moving image capturing date stored by the moving image management information storing means for storing the moving image storage destination for each in-store device identifier as moving image management information. , The deletion target specifying step of specifying a storage location of a moving image of an imaging date that satisfies the moving image deletion condition for deleting the moving image as a deletion target, and the moving image from the event history acquired by the event history acquisition step An event history that occurs on an imaging date that satisfies an image deletion condition, and that includes an event type stored by an application exclusion setting storage unit that stores an event type that is excluded from application of the moving image deletion condition as an application exclusion setting From the moving image corresponding to the in-store device identifier extracted as the event history by the application exclusion history extracting step and the moving image whose storage destination is specified by the deletion target specifying step and extracted by the application exclusion history extracting step, A moving image of a predetermined cut-out section based on the event occurrence time acquired as the event history is cut. And executes a to moving image cutout process.

  According to the present invention, an event type of an event that occurs in an in-store device, an event occurrence date and time when the event has occurred, and an in-store device identifier for uniquely identifying the in-store device in which the event has occurred are stored as an event history, and imaging is performed. Stored as moving image management information is a moving image storage location for each in-store device identifier assigned to the in-store device to be imaged for each date, and is an event type exempted from moving image deletion conditions for deleting moving images Is stored as an exemption setting, and the storage location of the moving image having the imaging date satisfying the moving image deletion condition among the moving image capturing dates stored for each storage destination is specified as the deletion target, and the moving image deletion condition is satisfied. A history of events that occurred on the shooting date and that contains the event type stored as an exception setting and that specifies the storage location. Since the image management apparatus is configured to cut out a moving image of a predetermined cut-out section based on the event occurrence time acquired as the event history from the moving image corresponding to the in-store device identifier extracted as the event history, If an event type that is closely related to theft or theft damage is set as an exception for the moving image deletion condition, the event type that is closely related to the fraudulent or theft damage among the moving images that are no longer needed due to the shooting date becoming old It is possible to automatically cut out the moving image of the part corresponding to, and re-save the moving image after cutting out, so that it is possible to save the moving image of the event that the amusement store wants to keep for the after-hours without trouble Has the effect of becoming.

  In addition, according to the present invention, since the extracted moving image is stored in association with the event history, and the moving image specifying the storage destination is deleted after the extracted moving image is stored, the amusement shop can perform the subsequent operation. For this reason, it is possible to continuously save only the portion of the moving image that you want to keep as deletion-prohibited data, and delete the moving image that is no longer needed as the imaging date becomes old, while reducing the amount of data to be saved. There is an effect that it is possible to save the moving image of the event that the store wants to keep for the subsequent time without trouble.

  In addition, according to the present invention, since the extraction section is changed according to the event type included in the extracted event history, a cut out moving image containing a moving image of a core part for each event type is obtained. Therefore, it is possible to obtain a clipped moving image useful for subsequent browsing.

FIG. 1 is a system configuration diagram of an in-store system according to the present embodiment. FIG. 2 is an explanatory diagram for explaining the difference between the present embodiment and the prior art. FIG. 3 is a functional block diagram showing the configuration of the member management T / C according to the present embodiment. FIG. 4 is a diagram illustrating a configuration example of information stored in the transmission classification management table. FIG. 5 is a diagram illustrating a configuration example of information stored in the event history table for each machine. FIG. 6 is a diagram illustrating a configuration example of information stored in the member-specific event history table. FIG. 7 is a functional block diagram illustrating the configuration of the camera T / C according to the present embodiment. FIG. 8 is a diagram illustrating a configuration example of information stored in the moving image management table. FIG. 9 is a diagram illustrating an example of a configuration example of the application exclusion setting file. FIG. 10 is a diagram showing an example of screen transition when an event history is selected. FIG. 11 is a diagram illustrating an example of a moving image file to be reproduced. FIG. 12 is an explanatory diagram for explaining the extraction procedure of the event history that is excluded from the application of the moving image deletion condition. FIG. 13 is a diagram illustrating an example of a cut-out section of an event moving image file. FIG. 14 is a flowchart illustrating a procedure of moving image deletion processing according to the present embodiment.

  Exemplary embodiments of a game hall management system and a game hall management method according to the present invention will be described below in detail with reference to the accompanying drawings. In the following, the case where the present invention is applied to a pachinko game will be described.

  First, the system configuration of the in-store system of the amusement store according to the present embodiment will be described. FIG. 1 is a system configuration diagram of an in-store system according to the present embodiment.

  As shown in the figure, the amusement store includes a pachinko machine 10, a CR unit 20, an island controller 30, a ball counter 40, a prize management device 50, a prize dispenser 60, and a member management T / C 70. A card T / C 80, an H / C 90, a camera T / C 100, and a camera 200.

  The pachinko machine 10 is a device in which a player plays a pachinko game by launching a pachinko ball into the game area. In this embodiment, the pachinko machine 10 is a so-called CR pachinko machine compatible with a prepaid card.

  The CR unit 20 is interposed between the card T / C 80 and each pachinko machine 10 and inquires the card T / C 80 about the remaining amount of the prepaid card (hereinafter referred to as “prepaid balance”) and subtracts the prepaid balance. It is a device that makes a request and issues a ball lending instruction to the pachinko machine 10 when there is a prepaid balance.

  In addition, the CR unit 20 has a so-called replay function that withdraws the stored money deposited in the member management T / C 70. Specifically, when a member inserts a membership card into the CR unit 20 and performs a predetermined replay operation, the member management T / C 70 requests that the number of replayed balls be subtracted from the stored balance that is stored and managed. And throw the number of balls for the replay.

  The island controller 30 is a relay device that bundles a group of pachinko machines 10 and a CR unit 20 provided in a space (amusement island) surrounded by a passage.

  The ball counter 40 is a counter that counts pachinko balls acquired by the player, and has a receipt issuing function for issuing a count receipt in association with the count result. Specifically, a pachinko ball thrown by a player or employee is counted, and the count value of the thrown ball, the date of issue, the person in charge (employee), and the counting ID associated with the counting machine number are barcoded. Issue printed count receipt. In addition, although the counter which has both the counting function and the receipt issuing function is illustrated here, these functions may be provided separately from the counting machine and the receipt issuing machine.

  In addition, the ball counter 40 has a so-called counting and storing ball function that adds a part or all of the counting values counted by registered members. Specifically, when a member of the game store receives a membership card received from a player after the completion of counting, a count storage ball request including a member number and a count value is transmitted to the member management T / C 70. In addition, the count value is added to the stored balance corresponding to the member number by the member management T / C 70 that has received the count storage request.

  The prize management device 50 is a prize exchange terminal device arranged in a prize exchange counter in the amusement store. Specifically, when an employee in the prize counter receives a count receipt issued by the ball counter 40 from a player, the count counter is acquired through a reading operation of the count receipt to a bar code reader, and the game When the exchange button corresponding to the prize specified by the customer is pressed, the exchange control for subtracting the number of exchanged balls corresponding to the prize from the counted value (acquired balls) is executed, and then the player is manually operated by the employee. Deliver. If the player wishes to exchange for a special prize, the employee presses a special prize exchange button provided in the prize management device 50 and pays out a special prize according to the count value. 60.

  In addition, the prize management device 50 has a function of controlling exchange with prizes in exchange for savings held by members. Specifically, when the membership number recorded on the membership card is read through a reading operation to the card reader, the membership balance corresponding to the membership number is inquired to the membership management T / C 70, and the inquiry response is obtained. Within the range of the stored ball balance, the exchange control with the general prize or the special prize is performed in the same manner as the count receipt, and the member management T / C 70 is requested to subtract the number of balls to be exchanged from the stored ball balance.

  The member management T / C 70 is a management device that performs overall management of members registered in the game store using a member management table (not shown). In this member management table, a member number is stored in association with a stored balance and attribute information. Then, if a savings addition request is accepted from the ball counter 40 or the prize management device 50, the number of savings in the corresponding savings account is added, and if a savings subtraction request is accepted from the CR unit 20 or the prize management device 50 Subtract the number of stored balls in the corresponding stored account.

  The card T / C 80 is a management device that manages the remaining amount of a prepaid card using a prepaid balance management table (not shown). This prepaid balance management table stores a prepaid balance in association with a prepaid card ID. When a value request (remaining amount addition request) is received from the CR unit 20, the prepaid remaining amount of the prepaid card ID included in the value request is added, and a remaining amount subtraction request is received from the CR unit 20. In this case, the prepaid balance of the prepaid card ID included in the balance subtraction request is subtracted.

  The H / C 90 is a hall computer that manages table data of each pachinko machine 10 using a table data management table (not shown). This table data management table stores table data such as the number of outs, the number of safes, the number of special prizes, the number of starts, etc. in association with the number of the pachinko machine 10. These table data are collected every time an out, safe, special prize or start occurs in each pachinko machine 10, and are registered in the table data management table. “Out” refers to a pachinko ball that has been driven into the game machine, “safe” refers to a pachinko ball thrown out as a prize ball from the game machine, and a special prize refers to a big hit on the game machine. The term “event” refers to an event of starting a unit game on a game machine.

  As described above, in the game store, as a system for providing services to members and other players, in-store devices (for example, the CR unit 20, the ball counter 40, the prize management device 50, etc.) that handle the membership card, and these A member management system that includes a member management T / C 70 that manages in-store devices, and in-store devices that handle prepaid cards (for example, the CR unit 20 and other card settlement machines not shown). In addition, there is a hallcon system that includes in-store devices (for example, pachinko machine 10, CR unit 20, ball counter 40, etc.) that handle game machine table data.

  Further, the game store includes a camera 200 that captures each in-store device and a camera T / C 100 that stores an image captured by the camera 200 as a system for monitoring the game hall. A system is provided.

  This amusement hall refers to a place where a player can enter. In addition to the amusement hall, the amusement store has an office that prohibits the entry of players, and various management devices that manage information relating to the secrecy of the amusement store, such as member management T / C 70, cards, etc. T / C80, H / C90, and camera T / C100 are arranged in the office, not in the game hall.

  This camera 200 is an imaging device provided so as to be capable of imaging in-store equipment and its surroundings. In the example of FIG. 1, a pair of the pachinko machine 10 and the CR unit 20, a ball counter 40, a prize management device 50, and a prize delivery One is installed corresponding to a combination of in-store equipment such as a pair of machines 60 or in-store equipment. An image captured by the camera 200 is transmitted together with a camera ID assigned in advance to each camera, and is stored for each in-store device by the camera T / C 100.

  The camera T / C 100 is a server device that stores a moving image captured by the camera 200. Specifically, an imaging date, a camera ID of the camera 200, an in-store device number captured by the camera 200, and a moving image storage location are managed in association with each other in the moving image management table 121 described later. When the camera ID and the captured image are received, the captured image is accumulated in the storage destination of the machine number corresponding to the camera ID. Note that the moving image stored in the camera T / C 100 can be reproduced by the output unit of the camera T / C 100 based on an instruction from the own device or another device.

  Here, in the present embodiment, the event history generated in the in-store device managed by the management device such as the member management T / C 70, the card T / C 80, or the H / C 90, and the moving image stored by the camera T / C 100 are displayed. In association with each other, a moving image to be reproduced is selected by selecting an event history.

  In other words, when fraud occurs, it is necessary to report the location and time from the player or employee and to find an image corresponding to the report from the camera T / C 100. Based on the location and time of this declaration, In the case of playing the image, it includes the video of the scene where the player and employee are not in contact with the equipment in the store at all and are completely out of the scope of fraud. It is necessary to find a video of the target scene, which takes a lot of effort. In addition, such declarations are often ambiguous or misunderstood, and there are many players who are not conscious of the time in particular.

  For this reason, in this embodiment, the event history such as the event type of the event that occurs in various in-store devices, the content of the event, the event occurrence date and time when the event occurred, and the machine number of the in-store device where the event occurred is selected, By playing back the video corresponding to the event history, you can select the video to play while referring to the details of the event, and play back only the video of the scene where there is room for fraud in the equipment in the store. I am going to let you. The “event” referred to in the present embodiment refers to an operation such as an operation on an in-store device performed by a player or employee, a process performed in response to the operation, or an error occurring in the in-store device.

  Furthermore, in this embodiment, the event history is displayed in a superimposed manner when a moving image is reproduced. By this superimposed display, what is meant by the moving image to be reproduced is understood from the event history.

  As described above, in this embodiment, the image at the time of the occurrence of fraud is referred to easily, and the image for easily grasping the fraud content to be monitored is presented.

  In this embodiment, the event history collected from the in-store device by the management device such as the member management T / C 70, the card T / C 80, or the H / C 90 is notified to the camera T / C 100 side, and the viewer actually moves the video. Event history selection operations are aggregated and performed by the camera T / C 100 that confirms the image.

  In other words, if the event history collected from the in-store device is selected on the management device side, if the selected event history does not correspond to the target moving image, the event history is selected again on the management device side. I have to. Furthermore, as in this embodiment, when the three systems of the member management system, the card system, and the hall control system coexist, the event history must be individually selected by each management device, and the event history selection operation is performed. Becomes complicated.

  For this reason, in this embodiment, the event history is notified from the management device to the camera T / C 100, and the event history selection operation is consolidated on the camera T / C 100 side, so that the event history on the management device side is recorded. The reselection operation, the reciprocating movement between the management device and the camera T / C, and the event history selection operation in the individual management device can be eliminated.

  In addition, in this embodiment, the timing at which the event history is notified from the management apparatus to the camera T / C 100 is changed depending on the difference in the property of each event, that is, the event type.

  That is, if the event history is notified to the camera T / C 100 every time an event occurs, the communication load between the management apparatus and the camera T / C increases, and the in-store communication network is compressed. Result.

  For this reason, for events that should be confirmed quickly when an event occurs, for example, events closely related to fraud and theft damage, event history is collected from in-store devices and the event history is notified to the camera T / C100. On the other hand, for an event that can be browsed afterwards, the camera T / C 100 is notified of an event history at a regular time (for example, every two hours).

  As a result, it is possible to preferentially notify the event history corresponding to the moving image that needs to be promptly confirmed when the event occurs, and to distribute and notify the event history notified from the management device to the camera T / C 100. In addition, it is possible to prevent the in-store communication network from being squeezed while reproducing a moving image using an event history necessary in an emergency.

  Here, since the moving images accumulated in the camera T / C 100 have a huge amount of data as the game shop continues to operate for a long time, all the moving images accumulated and accumulated every business day are stored. This is difficult in the medium to long term.

  Therefore, in this embodiment, as described above, the convenience of browsing the moving image is improved by calling the moving image corresponding to the event history, while the moving image captured by the camera 200 is accumulated in the medium to long term. In this case, the video game of the event that the amusement store wants to keep for the subsequent event can be saved without any hassle.

  That is, in the above prior art, when a part of the accumulated moving image is deleted to reduce the amount of stored data, the data arrangement is sequentially deleted from the accumulated moving images from the moving image having the oldest shooting date and time. I went there.

  For example, as shown in FIG. 2 (a), when the above data arrangement is performed on August 31 and the stored data is determined, the moving image data for July and the moving image data for August are stored on a hard disk or the like. Assuming that the image data is stored in the configured storage device, moving image data from September 1 to September 15 is newly accumulated from September 1 to September 15, while Data arrangement is performed to delete the moving image data from the old July 1st to July 15th.

  As a result, when the data arrangement on September 15 was performed, as shown in the figure, instead of deleting the video data from July 1 to July 15, the data from September 1 to September 15 was deleted. Movie data is newly accumulated.

  If such data arrangement is performed, even if the video data from July 1 to July 15 to be deleted contains video data that the amusement store wants to keep for the subsequent events, If there is no special operation, it will be deleted along with other data.

  For this reason, when trying to save a moving image related to a specific event, it is necessary to perform the complicated operation described in the above-described conventional technology, so that the moving image portion corresponding to the event to be stored is found. It takes a lot of time and effort, and in the worst case, there is a possibility that the user forgets to specify the storage and is deleted.

  On the other hand, in this embodiment, as in the above-described prior art, a part of the moving image is deleted from the accumulated moving images with priority from the moving image with the old imaging date, but the moving image with the old imaging date and time is deleted. Do not delete everything in a uniform way. In other words, in the above-described conventional technology, even a moving image with an imaging date to be deleted, a moving image corresponding to an event type closely related to illegal goto or theft damage is cut out from the moving image with the imaging date, Re-save as deletion prohibition data.

  For example, in the example shown in FIG. 2B, the same applies until the moving image data from September 1 to September 15 is newly accumulated from September 1 to September 15. The moving image data is not uniformly deleted in order from the moving image data of July 1 with the oldest shooting date in the stored data.

  That is, among the July moving image data to be deleted, the moving image data that the amusement store wants to keep for the subsequent event, that is, the moving image data corresponding to the event type that is closely related to illegal goto or theft damage While the cut-out and cut-out moving image data is re-saved as deletion-prohibited data, the moving image data on the imaging date when the cut-out is completed is deleted.

  As a result, at the time when the data arrangement on September 15 was performed, as shown in the figure, while moving image data from September 1 to September 15 was newly accumulated, While deleting unnecessary moving image data, only the moving image data that the amusement store wants to keep for the subsequent event can be continuously stored as deletion prohibition data.

  Therefore, according to the present embodiment, if an event type closely related to illegal goto or theft damage is set as an exemption of the moving image deletion condition, it is illegal even in moving images that are no longer necessary because the shooting date becomes old. Events that the amusement store wants to keep for the after-effect as a result of being able to automatically cut out the moving image of the part corresponding to the event type closely related to Goto and theft damage and re-saving the extracted moving image Can be saved without trouble.

  Then, the structure of each apparatus which comprises the game hall management system based on a present Example is demonstrated. Here, a game hall management system that plays back a moving image by linking the member management system and the camera system will be exemplified, and the member management T / C 70 that is the center of the member management system and the center of the camera system will be described. A configuration with the camera T / C 100 will be described in detail.

(1) Configuration of Member Management T / C 70 As described above, the configuration of the member management T / C 70 according to the present embodiment will be described here. FIG. 3 is a functional block diagram showing the configuration of the member management T / C according to the present embodiment.

  As shown in the figure, the member management T / C 70 includes a communication I / F unit 71, a storage unit 72, and a control unit 73. Note that the actual member management T / C 70 has functional units (for example, an input / output unit, a table for storing member information and a stored balance, software for updating the stored balance, etc.) other than the illustrated functional units. However, in FIG. 3, only components necessary for explaining the characteristics of the member management T / C 70 according to the present embodiment are extracted.

  The communication I / F unit 71 is an interface for performing data communication with the CR unit 20, the island controller 30, the card T / C 80, the H / C 90, and the camera T / C 100.

  The storage unit 72 is a storage device such as a hard disk device or a non-volatile memory. For example, for each event, transmission for managing a transmission category (notification timing setting) that determines the timing for notifying the camera T / C 100 of the event history of the event. The division management table 72a, two tables for managing event histories occurring in the in-store devices related to the member management system, that is, the event history table 72b for each device for managing the event history for each device in the store, and the event history for each member The member-specific event history table 72c to be managed is also stored.

  As shown in FIG. 4, the transmission category management table 72a is a table that stores an event type and a transmission category for each affiliation system. In the example shown in FIG. 4, the membership management system has four types of events, counting, exchanging, storing balls, and replaying. Among these, the counting transmission category is 1, and other exchanging, storing balls, and replaying events are performed. It is shown that the transmission category is 2. In the card system, only a banknote error event is set in the transmission category 1, and a transmission category 2 is set for other events (depositing banknotes, discharging cards, and unlocking bill burrs, etc.). It shows that. Also, in the hall control system, game console door open and game table error events are set in transmission category 1, and for game console jackpot (special prize winning), transmission category 2 is set. Show.

  Here, the transmission category refers to a setting that determines the timing for notifying the camera history to the camera T / C 100, and the transmission category “1” is the event history in real time when the event history is acquired from the in-store device of the affiliated system. Is sent to the camera T / C 100. On the other hand, in the transmission category “2”, the event history is accumulated in the management device until the regular time, and the event history is transmitted when the regular time is reached. It is a category that stipulates.

  As shown in FIG. 5, the event history table 72b for each unit is a table that stores the event type, date, time, number of T balls, and person-in-charge code for each unit number. In the example shown in FIG. 5, an event history that occurred in the counter having the unit number “B002” on July 1 is stored. For example, at 11 o'clock, 600 employees are present in the presence of the employee code “AAA”. This indicates that the number of acquired balls has been counted. Here, only the event history of the machine number “B002” is shown, but event histories of other machine numbers are similarly stored.

  As shown in FIG. 6, the member-specific event history table 72c is a table that stores the event type, date, time, machine number, and transaction volume for each member number. In the example shown in FIG. 6, the event history regarding the member with the member number “12345” on July 1 is stored. For example, at 11:20, the member with the member number “12345” has the CR of the machine number “P0001”. This shows that a member card has been inserted into the unit 20. Here, only the event history of the member number “12345” is shown, but event histories of other member numbers are also stored in the same manner.

  These two tables are common in that they store event histories, but on the one hand, histories are registered for each device number of in-store equipment, and on the other hand, histories of events performed through membership cards are registered for each member. The

  And the event content registered as an event history differs between both tables. Specifically, in the event history table 72b for each unit, the event content (for example, employee code) specialized for counting work is registered, while in the event history table 72c for each member, it is specialized for members. The event contents (for example, membership number) are registered.

  5 and 6 exemplify the event history of the CR management unit 20, the ball counter 40, and the prize management device 50 because the event history of the member management system is illustrated. However, in the case of the event history of another system, FIG. May belong to different in-store equipment.

  The control unit 73 is a control unit that totally controls the member management T / C 70, and includes an event history acquisition unit 73a, an event history notification unit 73b, and an event history registration unit 73c. In practice, programs corresponding to these functional units are stored in a ROM or non-volatile memory (not shown), and these programs are loaded into the CPU and executed, and an event history acquisition unit 73a, event history notification unit 73b, and The event history registration unit 73c is caused to execute a corresponding process.

  The event history acquisition unit 73a is a processing unit that acquires an event history from the in-store device of the affiliated system. Specifically, when an event occurs, the number of the in-store device, event type, date, time, transaction volume, person-in-charge code, and member code if the event occurred after the event is confirmed. The event history is acquired by notifying the in-store device of the number.

  The event history notification unit 73b is a processing unit that notifies the camera T / C 100 of the event history acquired by the event history acquisition unit 73a using the transmission classification management table 72a. Specifically, when the event history is acquired by the event history acquisition unit 73a, it is determined whether or not the transmission classification corresponding to the event history is “1” among the transmission classifications stored in the transmission classification management table 72a. Determine whether. When the transmission classification is “1”, the event history is notified to the camera T / C 100 as it is, thereby notifying the event history in real time, while when the transmission classification is “2”, The event history is not notified at the time.

  The event history notification unit 73b notifies the camera T / C 100 of the event history stored in the event history table 72b for each unit and the event history table 72c for each member at a regular time. Specifically, among the event histories stored in the event history table 72b for each unit and the event history table 72c for each member when the current time reaches a regular time (for example, a time of 2 hours from 10:00), The event history accumulated from the previous transmission time to the current transmission time (in other words, the event history from two hours before the current time) is read, and the read event history is notified to the camera T / C 100. Since the event history read from both tables includes the event history of the transmission category “1” transmitted in real time, the event history of the transmission category “1” may be excluded and transmitted.

  In this embodiment, the event history notified at the regular time includes the event history of the transmission category “1” that has been notified in real time. The reason is that the event history of the transmission category “1” In order to increase the search efficiency of the history, the camera T / C 100 side maintains a table for storing event histories corresponding to the transmission category “1” individually. The event history of the transmission section “1” is duplicated on the camera T / C 100 side by holding a table that stores both event history of the transmission sections “1” and “2” so that the same table can be searched. This is because it was decided to register.

  In addition, in order to specify the video file and playback section to be played, at least the machine number and time are indispensable, and the other items are additional information for display. It can also be excluded from the content.

  The event history registration unit 73 c is a processing unit that registers the event history acquired by the event history acquisition unit 73 a in the storage unit 72. Specifically, the event history acquisition unit 73a acquires the event number, event type, date, time, transaction volume, person-in-charge code, and member number if it is an event related to a member. The history is registered in the machine-specific event history table 72b, and when the member number is included in the event history, the acquired event history is registered in the member-specific event history table 72c.

(2) Configuration of Camera T / C Next, the camera T / C according to the present embodiment will be described. FIG. 7 is a functional block diagram illustrating the configuration of the camera T / C according to the present embodiment. Note that the actual camera T / C 100 has functional units (for example, an input device, a display device, an audio output device, and the like) other than the illustrated functional units, but in FIG. 7, the camera T / C 100 according to the present embodiment Only the components necessary to explain the features are extracted.

  As shown in the figure, the camera T / C 100 includes a communication I / F unit 110, a storage unit 120, and a control unit 130. The communication I / F unit 110 is an interface for performing data communication with the CR unit 20, the island controller 30, the member management T / C 70, the card T / C 80, and the H / C 90.

  The storage unit 120 is a storage device such as a hard disk device or a nonvolatile memory. For example, the storage unit 120 includes a moving image management table 121 that manages moving image files stored in the storage unit 120 and a group of moving image data captured by each camera 200. A moving image file group 122, an event history table 123 for storing event histories notified from other management devices such as member management T / C 70, card T / C 80, and H / C 90, and moving image deletion for deleting moving images An application exemption setting file 124 that is setting data in which an event type to be exempted from conditions is defined as an application exemption setting, and an event video file group 125 that is a group of video data from which a portion corresponding to a specific event is cut out Is stored together.

  As shown in FIG. 8, the moving image management table 121 is a table that stores an imaging date, a camera ID of the camera 200, an in-store device number captured by the camera 200, and a path name indicating a moving image storage location. The example shown in FIG. 8 shows an example of the management information of the moving image file imaged on July 1, and the uppermost record shows the CR unit of the machine number “P0001” by the camera 200 with the camera ID “00001”. 20 and the peripheral area of the pair of pachinko machines 10 are imaged and the moving image file is stored at the address of path 1. The initial of the machine number indicates the type of the in-store device. Those assigned P indicate CR units, those assigned B indicate counters, and J is assigned. The thing shows the prize management apparatus.

  The moving image file group 122 is a group of moving image data for each number of the device number of the in-store device to be imaged, which is moving image data for each imaging date. For example, taking the top record shown in FIG. 8 as an example, the camera 200 with the camera ID “00001” stores the peripheral area of the CR unit 20 with the machine number “P0001” and the pachinko machine 10 of the pair in the imaging range. The moving image data continuously captured from the opening process to the closing process on July 1 is stored as a moving image file compressed at a path 1 address in the storage unit 120 by a compression method such as MPEG.

  The event history table 123 is a table group including an emergency event history table and a normal event history table.

  Among these, the emergency event history table is a table that stores the machine number, date, time, member number, transaction volume, and person in charge code for each event type. Specifically, the event history notified in real time by the event history notification unit 73b of the member management T / C 70, as well as events notified in real time from other management devices such as the cards T / C 80 and H / C 90 in the same manner. The history is stored, and as a result, the event history notified from the three systems of the member management system, the card system, and the hall control system is stored.

  The event history of the transmission category “1” stored in the emergency event history table relates to counting, banknote errors, door opening and errors. For example, an illegal instrument such as a rake or a pachinko ball from another store is used. Such as counting goto to be thrown in, bill goto for inserting counterfeit bills and foreign objects, goto for gaming machine boards, and goto for inducing special prizes using sensory devices etc. It is.

  As described above, the event history set to the transmission category “1” is stored in order to individually store the event history of the event for which the moving image should be confirmed promptly when the event occurs. This is because the selection target is carefully selected as an event that should be confirmed as soon as possible.

  On the other hand, the normal event history table stores event histories corresponding to both transmission categories “1” and “2”. As the stored contents, for example, what is notified from the member management T / C 70 is stored in the event history table 72b for each machine shown in FIG. 5 and the event history table 72c for each member shown in FIG. The same event history is stored. However, the normal event history table does not necessarily store the same information as that shown in FIGS. 5 and 6, but stores information notified at the regular time. Here, the event history notified from the member management T / C 70 is taken as an example, but the event history notified from another management device such as the card T / C 80 or H / C 90 is also stored in the same manner.

  The application exclusion setting file 124 is setting data in which an event type to be excluded from the moving image deletion condition is defined as an application exclusion setting. In the example illustrated in FIG. 9, counting, banknote errors, door opening, and games The four event types of stand error are registered as exemption settings.

  The event types for which such application exclusion setting is made are cases where, for example, some moving image files in the moving image file group 122 are deleted using a moving image deletion condition of deleting moving image files having the oldest shooting date. However, deletion of the moving image data corresponding to the event type is prohibited, and moving image data corresponding to the event type is cut out by the moving image cutout unit 136 described later.

  The event moving image file group 125 is a group of moving image files in which a corresponding part of the event history is cut out by a moving image cutout unit 136 described later. The event moving image file group 125 is not configured such that moving images of one business day as a batch data stream as in the moving image file group 122 described above, but a predetermined amount based on the event occurrence time from the moving image file. This is a moving image file in which the cut section is cut out. The address for storing the event moving image file group 125 is registered in the event history table 123 in association with the event history after being cut out by the moving image cutout unit 136 described later.

  The control unit 130 is a control unit that controls the camera T / C 100 as a whole, and includes a moving image storage unit 131, an event history storage unit 132, a moving image reproduction processing unit 133, a deletion target specifying unit 134, and an application exclusion history extraction. A section 135, a moving image cutout section 136, and a moving image deletion section 137. Actually, programs corresponding to these functional units are stored in a ROM or non-volatile memory (not shown), and these programs are loaded into the CPU and executed, and the moving image storage unit 131, event history storage unit 132, moving image The image reproduction processing unit 133, the deletion target specifying unit 134, the application exclusion history extraction unit 135, the moving image cutout unit 136, and the moving image deletion unit 137 execute corresponding processes.

  The moving image storage unit 131 is a processing unit that stores a moving image captured by the camera 200 in the storage unit 120 using the moving image management table 121. Specifically, when a moving image and a camera ID are received from the camera 200, the path name stored in association with the corresponding imaging date and the corresponding camera ID is identified with reference to the moving image management table 121, and the identified Moving images are sequentially accumulated by storing moving images in the storage destination of the storage unit 120 corresponding to the path name.

  The event history storage unit 132 is a processing unit that stores the event history notified from various management devices in the event history table 123. Specifically, when the event history is notified by the event history notification unit 73b and the transmission category of the notified event history is 1, the event history is stored in the emergency event history table, and When the notified event history transmission category is 2, the event history is stored in the normal event history table.

  The moving image reproduction processing unit 133 is a processing unit that reproduces a moving image file stored in the storage unit 120. Specifically, the selection of an event history to be reproduced from the event history stored in the emergency event history table or the normal event history table is accepted, and the moving image file to be reproduced is specified using the moving image management table 121. At the same time, the playback section of the video file to be played is determined from the video file group 122, the video file specified as the playback target is played back for the playback section, and the event history that has received the selection is superimposed on the playback image. Reproduce.

  More specifically, when the selection of the event history is accepted, the moving image reproduction processing unit 133 refers to the moving image management table 121 and identifies the storage destination (path name) corresponding to the event number of the event history. In addition, the specified storage destination video file is determined as a playback target video file, and includes a predetermined period (for example, 45 seconds) before and after the event history time (event occurrence time) at which the selection is accepted. The section is determined as a playback section. Note that the length of the playback period that goes back from the event occurrence time and the length of the playback period that goes after the event occurrence time may be the same or different, and may be arbitrarily changed depending on the nature of the event. In addition, since the specification of the moving image to be played back and the playback section of the moving image are independent processes, any of these processes may be performed first or simultaneously.

  Then, the moving image reproduction processing unit 133 reproduces the moving image file specified as the reproduction target until the reproduction section ends, and reproduces the event history having received the selection superimposed on the reproduction image. Note that the event history display mode (for example, font, transparency, etc.) to be superimposed on the moving image can be arbitrarily set. For example, for events that are prone to fraudulent events such as bringing in pachinko balls from other stores or counting up with a rake, etc., a display mode that prompts attention such as red display or flashing display may be adopted. Good.

  To explain with an example, the moving image reproduction processing unit 133 displays the screen shown in FIG. 10A on the display unit of the camera T / C 100, so that the emergency event history table is input via an input unit such as a pointing device. Alternatively, it is accepted from which table of the normal event history table the event history is selected.

  When the emergency event history table is selected, the moving image reproduction processing unit 133 directly designates the event history by displaying the event history stored in the emergency event history table on the display unit. When the event history table is selected, the amount of event history to be selected becomes enormous, and the event history to be selected is narrowed down by searching. The event history stored in the emergency event history table is often highly urgent, so when received in real time, the event history can be displayed in a pop-up display, etc. so that the event history can be viewed with one operation. It doesn't matter.

  At this time, when accepting that the event history is selected from the normal event history table, the moving image reproduction processing unit 133 displays the search condition input screen shown in FIG. Search conditions are accepted for items such as event contents, event occurrence date, event occurrence time or machine number. Here, it has been described that a condition relating to the contents of an item is received. However, not only the contents of an item but also a search method for searching with an AND condition or an OR condition can be arbitrarily set.

  Then, the moving image reproduction processing unit 133 searches the event history stored in the normal event history table for an event history that matches or partially matches the received search condition, and matches the search condition as a search result. By displaying a list of event histories (see FIG. 10C) on the display unit, selection of an event history desired to be browsed is accepted via the input unit.

  For example, when the third event history from the top in the search result list shown in FIG. 10C is selected, the moving image shown in FIG. 11 is reproduced on the display unit. From the event history displayed superimposed on the moving image reproduced in this way, the player counts pachinko balls from other stores while the employee “CCC” has left the office for other duties. The employee “CCC” is alerted that he / she has left his office, and registered to the blacklist for registering fraud based on the player ’s face image. It is possible to search the inside of the store and take a corresponding action (for example, an exchange prohibition action or a report to the police) for the player. If the player who performs the fraud is a member, the member number is also displayed, so that other fraudulent acts of the member can be searched or the identity can be confirmed from the member management table.

  Returning to the description of FIG. 7, the deletion target specifying unit 134 uses the moving image management table 121 to specify, as the deletion target, the storage destination of the moving image file having the imaging date satisfying the moving image deletion condition in the moving image file group 122. It is. Specifically, for example, when the moving image deletion condition of deleting the moving image file with the oldest shooting date among the shooting dates stored by the moving image management table 121 is used, the storage destination of the moving image file with the oldest shooting date is set. The data is read from the moving image management table 121, and the storage destination of the read moving image file is specified as a deletion target. Here, the moving image deletion condition of deleting the moving image file with the oldest shooting date is illustrated, but the moving image deletion condition is not limited to this, and for example, the shooting date is the most except for fifty days. Arbitrary conditions can be used, such as deleting old video files.

  The application exclusion history extraction unit 135 obtains, from the event history table 123, an event history that is an event history that has occurred on an imaging date that satisfies the moving image deletion condition and includes an event type that is stored as an application exclusion setting by the application exclusion setting file 124. A processing unit for extraction.

  For example, when the shooting date of the moving image file on July 1 is the oldest among the shooting dates stored in the moving image management table 121, the event history occurred on July 1 as shown in FIG. The event history including the four event types of counting, banknote error, door opening, and game table error set to be excluded is extracted from the event history table 123. In this embodiment, since the event history to be used as the emergency event history (transmission category 1) and the event history to be excluded are set to be the same, only the emergency event history table is searched when the event history is extracted. By selecting the target, the extraction speed of the event history can be improved.

  The moving image cutout unit 136 is a moving image file whose storage destination is specified by the deletion target specifying unit 134 and is extracted from the moving image file corresponding to the machine number of the in-store device extracted as the event history by the application exemption history extracting unit 135. It is a processing unit that cuts out a moving image in a predetermined cut-out section based on an event occurrence time acquired as an event history.

  For example, when the moving image corresponding to the event history of the top record in the event history shown in FIG. 12 is cut out, the storage location of the July 1 moving image file specified as the deletion target by the deletion target specifying unit 134 Among them, a storage destination moving image file corresponding to the machine number “P0001” is read from the storage unit 120, and the cut-out section when the event type is “banknote error” based on the event occurrence time “16:20”, for example, A moving image of a section 30 seconds before the event occurrence time and a section 15 seconds after the event occurrence time is cut out as an event moving image file (see FIG. 13A).

  In this way, when cutting out an event moving image of a banknote-based error, the section that goes back from the event occurrence time is longer than the section that goes backward from the event occurrence time when a banknote that inserts counterfeit bills or foreign objects is performed In many cases, counterfeit bills are picked up by moving images in an operation stage where a bill is taken out from a wallet or a pocket and inserted into a bill insertion slot, and the bill reception time at the CR unit 20 is set as an event occurrence time. This is because the site of the banknotes has been imaged before.

  When the moving image corresponding to the event history of the fourth record from the top of the event history shown in FIG. 12 is cut out, the July 1 moving image specified as the deletion target by the deletion target specifying unit 134 A cut-out section in the case where the storage destination moving image file corresponding to the machine number “B002” is read from the storage unit 120 and the event type is “count” with the event occurrence time “17:00” as a reference. For example, the moving images of the section 10 seconds before the event occurrence time and the section of the calculation result of the calculation formula shown in FIG.

  The calculation formula shown in FIG. 13B shows the number of acquired balls (transaction amount) included in the event history, the unit counting time required to count 100 pachinko balls (A second / 100), and the acquired balls. This is for estimating the time required for completion of counting from the error B including the required time required for issuing in association with the counting receipt or the time required for storing the acquired ball after inserting the membership card.

  That is, if the number of acquired balls is multiplied by a unit counting time, the required time for counting the number of balls required for counting the acquired balls can be estimated, and if the error B is added to the required time for counting the acquired balls, the time required for completion of counting can be estimated. . As a result, the moving image is not cut out during the pachinko ball counting, and the event video file containing all the counting actions in the ball counter 40 can be cut out. As a result, an event video file useful for subsequent browsing can be obtained. It becomes possible to cut out.

  If the player who performs counting is a member, the event occurrence time of the event type “settlement” is determined when the member's saving operation is accepted or when the savings balance is added and updated by the member management T / C 70. It is assumed that it will be acquired and cut out including moving images corresponding to other event histories, but the event type `` stored ball '' is not exempted from moving image deletion conditions, but with the entire movie file of the shooting date Since it is deleted, it is preferable to cut out a moving image file containing both the “count” and “stored ball” events also from the viewpoint of enabling a series of counting flows in the ball counter 40 from a bird's-eye view.

  In this way, by appropriately changing the segment of the moving image according to the event type included in the event history extracted by the exemption history extracting unit 135, the core moving image is stored for each event type. Therefore, it is possible to obtain an event moving image file useful for subsequent browsing.

  Thereafter, the moving image cutout unit 136 re-saves the event moving image file cut out as described above in the storage unit 120 in association with the event history. Specifically, unlike a video file, since it is a video file newly generated by cutting, the event video file is stored in the storage unit 120 so that the event video file is called using the event history as a search index. Sometimes, the storage location of the event moving image file is registered in association with the corresponding event history stored in at least one of the emergency event history table and the normal event history table.

  At this time, if there is an event history indicating the same event as in the fourth and fifth records from the top of the event history shown in FIG. 12, it is associated with the fourth event history. The same pointer may be shared by registering the same storage location as the storage location of the registered event moving image file with the fifth event history.

  In this embodiment, since the event history to be used as the emergency event history (transmission category 1) and the event history to be set to be exempt are set to be the same, the storage destination in the emergency event history table in the event history table If is written, responsiveness up to reproduction can be improved during the moving image reproduction processing.

  The moving image deletion unit 137 is a processing unit that deletes the moving image file whose storage destination is specified by the deletion target specifying unit 134. Specifically, when an event moving image file corresponding to all event histories extracted by the application exclusion history extraction unit 135 is cut out by the moving image cutout unit 136, the storage target is specified by the deletion target specifying unit 134. The moving image file, that is, the moving image file of all the machine numbers on the imaging date that satisfies the moving image deletion condition (in the above example, all moving image files on July 1) is deleted.

  Next, the flow of processing of the game hall management system according to the present embodiment will be described. FIG. 14 is a flowchart illustrating a procedure of moving image deletion processing according to the present embodiment. The moving image deletion process is started when a notification of completion of the closing process is received from another management device such as the member management T / C 70, the card T / C 80, and the H / C 90. When the data amount of the moving image file stored in the storage unit 120 exceeds a predetermined value, when the free capacity of the storage unit 120 decreases below the predetermined value, or when an instruction to reduce the amount of stored data with a specified value is received The processing can be performed at any timing.

  As illustrated in FIG. 14, when the completion notification of the closing process is received from another management device (Yes in step S101), the deletion target specifying unit 134 has the amount of data stored in the moving image file group 122 in the storage unit 120 within a predetermined value. It is determined whether or not (step S102).

  At this time, when the stored data amount of the moving image file group 122 in the storage unit 120 is within a predetermined value, for example, when the storage unit 120 starts storing the moving image file and the date is shallow, the stored data amount does not reach the predetermined value. In (Yes at Step S102), since it is not necessary to perform the processes from Step S103 to Step S109, the process is terminated as it is.

  Here, when the amount of data stored in the moving image file group 122 in the storage unit 120 is not within the predetermined value (No in step S102), the deletion target specifying unit 134 selects the most of the imaging dates stored by the moving image management table 121. The storage location of the moving image file with the old imaging date is read from the moving image management table 121, and the storage location of the read moving image file is specified as a deletion target (step S103).

  Subsequently, the application exclusion history extraction unit 135 converts the event history that occurred on the imaging date to be deleted and includes the event type stored as the application exclusion setting by the application exclusion setting file 124 into the event history table 123. (Step S104).

  Then, the moving image cutout unit 136 is a moving image file whose storage destination is specified by the deletion target specifying unit 134 and corresponding to the device number of the in-store device extracted as the event history by the application exclusion history extracting unit 135. Then, a moving image in a predetermined cut-out section based on the event occurrence time acquired as the event history is cut out as an event moving image file (step S105).

  Subsequently, the moving image cutout unit 136 resaves the event moving image file cut out in step S105 as a deletion prohibition file in the storage unit 120 (step S106) and corresponds to the corresponding event history stored in the event history table 123. In addition, the storage location of the event moving image file is registered (step S107).

  Thereafter, the process from step S105 to step S107 is repeated until the event moving image file corresponding to all the event histories extracted by the application exclusion history extraction unit 135 is extracted by the moving image extraction unit 136 (No in step S108). Do.

  Then, when the event moving image file corresponding to all the event histories extracted by the application exclusion history extracting unit 135 is cut out by the moving image cutting unit 136 (Yes in step S108), the moving image deleting unit 137 specifies the deletion target. The moving image file whose storage destination is specified by the unit 134, that is, the moving image file of all the machine numbers on the imaging date that satisfies the moving image deletion condition is deleted (step S109).

  Thereafter, until the amount of data stored in the moving image file group 122 in the storage unit 120 falls within a predetermined value (No in step S102), the processing from step S103 to step S109 is repeated, and the amount of stored data in the moving image file group 122 is determined. Is within the predetermined value (Yes at step S102), the process is terminated.

  As described above, in this embodiment, the event type, the event occurrence date and time, and the machine number are stored as an event history, and the video file for each machine number assigned to the in-store device to be imaged for each imaging date is stored. The storage date is stored, the event type to be excluded from the moving image deletion condition is stored as the application exclusion setting, and the imaging date that satisfies the moving image deletion condition among the moving image imaging dates stored for each storage destination The video file storage location is specified as the deletion target, the event history that occurred on the shooting date that satisfies the moving image deletion condition and that includes the event type stored as the application exclusion setting is extracted, and the storage location is specified The event occurrence time acquired as the event history from the moving image corresponding to the machine number extracted as the event history Since the camera T / C is configured to cut out the moving image in the predetermined cut-out section, if the event type closely related to illegal goto or theft damage is set as an exemption of the moving image deletion condition, the imaging date As a result of being able to automatically cut out the moving image corresponding to the event type that is closely related to illegal goto and theft damage among the moving images that became old and unnecessary, It is possible to save a moving image of an event that an amusement store wants to keep for the subsequent event without trouble.

  Also, in this embodiment, the event video file after cutting is saved in association with the event history, and the video file specifying the storage destination is deleted after the event video file is saved. For this reason, it is possible to continuously save only the portion of the moving image that you want to keep as deletion-prohibited data, and delete the moving image that is no longer needed as the imaging date becomes old, while reducing the amount of data to be saved. It is possible to save the moving image of the event that the store wants to keep for the subsequent event without trouble.

  In the present invention, a link can be provided between event video files. For example, with regard to any of the four event types of counting, banknote errors, door opening, and game table errors that are closely related to fraudulent goto, the same game as the pair of CR unit 20 and pachinko machine 10 in which the event occurred With regard to a moving image file in which a part or all of the CR units 20 belonging to the island or a part or all of the CR units 20 belonging to the back-to-back gaming islands are imaged, a predetermined time before and after the event occurrence time of the event A section may be cut out and saved as a related video file. This makes it possible to detect fraud in a formula that is fraudulent if an unauthorized person has been fraudulent in the surrounding area before and after the event occurrence time.

  Here, the case of the CR unit 20 has been described. However, when the event type is counting, a link may be provided to the storage location of the moving image file of another counting event handled by the same employee. Alternatively, a moving image may be cut out even if the event type of an event caused by another in-store device by the same member is other than the exemption setting, and the cut image may be linked.

  Further, in the above embodiment, although not specifically mentioned, if the time notified by the member management T / C 70 as the event history and the time of the moving image stored by the camera T / C 100 are different, the camera Since the video corresponding to the event history cannot be viewed on the T / C 100, it is preferable to perform time adjustment of the member management T / C 70 and the camera T / C 100 periodically.

  In the above-described embodiment, an example in which one camera is installed for each in-store device has been described. However, the present invention is not limited to this, and imaging of a plurality of in-store devices and their peripheral areas is performed in one. It does not matter even if you let the camera of the table serve concurrently. In this case, in the case of an event type set as an emergency event history, the in-store device is enlarged and imaged with respect to the camera 200 that stores the in-store device in which the event occurs in the imaging range, or the focus It is preferable to perform image pickup control such as matching.

  In the above embodiment, the case where the member management system and the camera system are linked to each other has been described. However, the present invention is not limited to this, and is built around the card T / C 80 shown in FIG. The present invention can be similarly applied to a case where a camera system and a hall control system built around a card system or H / C 90 are linked.

  That is, a plurality of types of management devices are provided according to the management target, and an event history notified by any of the plurality of types of management devices is superimposed on the determined moving image. For example, when linked to the member management system, the member number is displayed when the counting event history is superimposed, whereas when counting with the H / C 90, the counting event history is superimposed. It is possible to display the out (placed ball) and the safe (paid-out ball) of the section in which the player with the member number has played, or the ball that is the difference between them.

  As described above, even if it is a moving image at the same time, as a result of displaying different event histories depending on the management device that accepts selection of the event history, it is possible to superimpose and reproduce the event history suitable for the characteristics of each management device. It is possible to present an image that makes it easier to grasp the portion to be watched in the moving image.

  In the above-described embodiment, a case where an illegal response to a player is performed (for example, a case where a moving image corresponding to an event history such as counting, banknote error, door opening, and game table error is cut out) has been described. In addition to fraudulent responses to customers, it is also possible to respond fraudulently to employee fraud (for example, sampling of prizes from prize dispensers or fraud when counting game media).

  In the above embodiment, an example in which the present invention is applied to a pachinko game has been described. However, the present invention is similarly applied to a case where a pachislot game is further included or only a pachislot game is targeted. Can do. Although an example in which the present invention is applied to a pachinko parlor has been described here, the present invention is not limited to this, and can be similarly applied to a game facility such as a game center.

  As described above, the game hall management system and the game hall management method according to the present invention are suitable for the case where the game store saves a moving image of an event that the game store wants to keep for the subsequent time without trouble.

10 Pachinko Machine 20 CR Unit 30 Island Controller 40 Ball Counting Machine 50 Premium Management Device 60 Premium Dispensing Machine 70 Member Management T / C
71 Communication I / F unit 72 Storage unit 72a Transmission classification management table 72b Event history table for each unit 72c Event history table for each member 73 Control unit 73a Event history acquisition unit 73b Event history notification unit 73c Event history registration unit 80 Card T / C
90 H / C
100 camera T / C
DESCRIPTION OF SYMBOLS 110 Communication I / F part 120 Storage part 121 Movie management table 122 Movie file group 123 Event history table 124 Exclusion setting file 125 Event movie file group 130 Control unit 131 Movie storage unit 132 Event history storage unit 133 Moving image reproduction processing unit 134 Deletion target specifying unit 135 Application exclusion history extraction unit 136 Moving image cutout unit 137 Moving image deletion unit 200 Camera

Claims (4)

An image management device that is connected to an in-store device disposed in an amusement store, one or a plurality of in-store devices, and an image pickup device provided in the vicinity thereof, and stores a moving image picked up by each image pickup device A game hall management system comprising:
The image management device includes:
An event history storage means for storing an event type of an event that occurs in the in-store device, an event occurrence date and time when the event has occurred, and an in-store device identifier for uniquely identifying the in-store device in which the event has occurred, as an event history;
Moving image management information storage means for storing, as moving image management information, a storage location of a moving image for each in-store device identifier assigned to the in-store device to be imaged for each imaging date;
Application exclusion setting storage means for storing, as an application exclusion setting, an event type that is an application exclusion of the moving image deletion condition for deleting the moving image;
Deletion target specifying means for specifying, as a deletion target, a storage location of a moving image having a shooting date that satisfies the moving image deletion condition among moving image shooting dates stored by the moving image management information storage unit;
An event history that occurred on an imaging date that satisfies the moving image deletion condition and that includes an event history that is stored as an application exclusion setting by the application exclusion setting storage unit from the event history storage unit. Extraction means;
The event occurrence time acquired as the event history from the moving image whose storage destination is specified by the deletion target specifying unit and corresponding to the in-store device identifier extracted as the event history by the exemption history extraction unit And a moving image cutout means for cutting out a moving image of a predetermined cutout section with reference to the game area management system. A cut-out moving image storage unit that stores the moving image cut out by the moving image cut-out unit in a predetermined cut-out moving image storage unit in association with the event history;
2. The moving image deleting means for deleting the moving image whose storage destination is specified by the deletion target specifying means after storing the extracted moving image by the extracted moving image storing means. Amusement park management system.   2. The game hall management system according to claim 1, wherein the moving image cutout unit changes the cutout section according to an event type included in the event history extracted by the exemption history extraction unit. An image management device that is connected to an in-store device disposed in an amusement store, one or a plurality of in-store devices, and an image pickup device provided in the vicinity thereof, and stores a moving image picked up by each image pickup device A game hall management method applied to a game hall management system comprising:
The image management device is
An event history acquisition step of acquiring, as an event history, an event type of an event that occurs in the in-store device, an event occurrence date and time when the event has occurred, and an in-store device identifier for uniquely identifying the in-store device in which the event has occurred;
Among the moving image imaging dates stored by the moving image management information storage means for storing the storage location of the moving image for each in-store device identifier assigned to the in-store device to be imaged for each imaging date as moving image management information, A deletion target specifying step for specifying, as a deletion target, a storage location of a moving image of an imaging date that satisfies the moving image deletion condition for deleting the moving image;
Among the event histories acquired by the event history acquisition step, event histories that occurred on the imaging date that satisfies the moving image deletion condition, and an event type that is excluded from application of the moving image deletion condition is set as an application exclusion setting. An application exemption history extracting step for extracting an event history including the event type stored by the application exemption setting storage means for storing;
The event occurrence time acquired as the event history from the moving image whose storage destination is specified by the deletion target specifying step and corresponding to the in-store device identifier extracted as the event history by the exemption history extraction step And a moving image cutting step of cutting out a moving image of a predetermined cut section with reference to the game area.

Images