Ticket terminal and ticket management system

Abstract

To provide a ticket terminal device and a ticket management system capable of preventing non-issuing of tickets and capable of reducing a maintenance load of a game device such as management of a residual amount of tickets.SOLUTION: A ticket terminal device 3 generates an electronic ticket on the basis of a ticket signal 30 inputted from a game device 2, and acquires identification information from a card by a terminal reader 15. The ticket terminal device 3 outputs the electronic ticket and the identification information to a ticket management device 4 for managing the electronic ticket. The ticket management device 4 adds an electronic ticket newly acquired on the basis of inputted ticket information to a stored electronic ticket in accordance with the identification information, and updates data. The electronic ticket can be exchanged with a privilege, a ticket exchange device 5 is allowed to acquire the identification information of the card, the ticket management device 4 is accessed from the ticket management device 5, and the privilege is put out from the ticket exchange device 5 in exchange for subtraction of the electronic ticket corresponding to the identification information.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a ticket terminal device that electronically issues tickets and a ticket management system that manages electronically issued tickets. [Background technology]

[0002] Coin-activated service devices that provide a predetermined service in response to the insertion of a coin are known. For example, a coin-activated game device provides a game as a service after a coin is inserted. Also known among these types of game devices are those that pay out a number of tickets or equivalent rewards according to the game results. The tickets are stored folded or rolled up inside the game device, and the number of tickets dispensed corresponds to the game results. The tickets dispensed from the payout port of the game device are acquired by the player. For example, the dispensed tickets can be exchanged for coupons, discount vouchers, merchandise, etc. For example, Japanese Patent Application Laid-Open Publication No. 2011-120741 discloses an arcade-type ticket-dispensing game device. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2011-120741 Summary of the Invention [Problem to be solved by the invention]

[0004] In conventional technology, tickets are stored inside the game device, and if all the tickets are ejected, there is a problem that tickets cannot be issued afterwards. Also, operators of facilities such as game centers have to manage the remaining number of tickets to prevent tickets from running out, and perform maintenance work such as replenishing tickets when the remaining number of tickets becomes low.

[0005] Operators of facilities such as game centers have been hoping to prevent tickets from going unissued due to insufficient remaining tickets, and to reduce the burden of maintaining game machines, such as managing remaining tickets.Furthermore, users of facilities such as game centers have been hoping to prevent tickets from going unissued or being lost, as they find it troublesome to have to negotiate with facility operators when problems such as unissued or lost tickets occur.

[0006] The present invention provides a ticket terminal device and a ticket management system that can prevent tickets from being issued due to a lack of tickets, reduce the maintenance load of service devices such as managing remaining tickets, and prevent tickets from being lost. [Means for solving the problem]

[0007] The ticket terminal device of the present invention comprises: A ticket terminal device connected to a service device that starts operating in response to a charging signal output from a fee receiving device, wherein the service device that starts operating in response to the charging signal outputs electronic tickets at a predetermined output timing based on a predetermined condition, and the electronic tickets are generated corresponding to a predetermined number of electronic tickets. an input means for inputting a ticket signal to be used by the service device; an identification information acquisition means for acquiring identification information for identifying a user who uses the service device; and the ticket signal input to the input means. Analyze the The number of said electronic tickets the number of electronic tickets and the identification information as a result of the calculation. a ticket generating means for generating ticket information including the identification information; The number of electronic tickets held for each user is stored in association with the number of electronic tickets held for each user. a communication means connected to the ticket management device so as to be capable of data communication; If the identification information is acquired after the previous generation of the ticket information and before the input of the ticket signal, the ticket generation means generates the ticket information including the number of electronic tickets calculated based on the input ticket signal and the identification information acquired last; if the identification information is not acquired before the input of the ticket signal and the identification information is not acquired within a first predetermined time period after the input of the ticket signal, the ticket generation means does not generate the ticket information; if the identification information is not acquired before the input of the ticket signal and the identification information is acquired within a first predetermined time period after the input of the ticket signal, the ticket generation means generates the ticket information including the number of electronic tickets calculated based on the input ticket signal and the identification information acquired for the first time within the first predetermined time period; The ticket information generated by the ticket generation means News The communication means outputs the ticket to the ticket management device.

[0008] The ticket management system of the present invention comprises: A ticket management system comprising a service device, a ticket terminal device, and a ticket management device, wherein the service device starts operation in response to input of a charging signal from a fee receiving device that outputs a charging signal in response to the receipt of a fee, and outputs ticket signals that are output at predetermined output timings based on predetermined conditions after the start of operation and that are generated corresponding to a predetermined number of electronic tickets, and the ticket terminal device To issue an electronic ticket The aforementioned Output from the service device The aforementioned a first input means for inputting a ticket signal; a first identification information acquisition means for acquiring identification information for identifying a user who uses the service device; and a first input means for inputting the ticket signal input to the first input means. Analyze the The number of said electronic tickets the number of electronic tickets and the identification information as a result of the calculation.and a first communication means connected to an external device so as to be capable of data communication. The ticket management device The device includes a second communication means connected to an external device so as to be able to perform data communication, a memory, and a control means for controlling the second communication means and the memory. and wherein, when the identification information is acquired after the previous generation of the ticket information and before the input of the ticket signal, the ticket information including the number of electronic tickets calculated based on the input ticket signal and the last acquired identification information is generated by the ticket generation means, when the identification information is not acquired before the input of the ticket signal and the identification information is not acquired within a first predetermined time from the input of the ticket signal, the ticket information is generated by the ticket generation means, and when the identification information is not acquired before the input of the ticket signal and the identification information is acquired within a first predetermined time from the input of the ticket signal, the ticket information including the number of electronic tickets calculated based on the input ticket signal and the identification information first acquired within the first predetermined time is generated by the ticket generation means, and the ticket information generated by the ticket generation means is output from the first communication means to the ticket management device, and the memory stores the number of electronic tickets held for each identification information in association with each other, The ticket management device receives the ticket from the first communication means by the second communication means. Before Ticket information News receiving the control means By controlling The ticket obtained from the ticket terminal Included in the ticket information The identification information and the electronic ticket and updating the number of the electronic tickets stored in association with the identification information stored in the memory based on the number of the electronic tickets. It is characterized by the following. [Effects of the Invention]

[0009] According to the present invention, it is possible to provide a ticket terminal device and a ticket management system that can prevent tickets from being issued due to a lack of tickets, reduce the maintenance burden on service devices such as managing remaining tickets, and prevent tickets from being lost. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a block diagram showing the configuration of a ticket management system. [Figure 2] FIG. 2 is a diagram illustrating an example of a terminal reader. [Figure 3] FIG. 3 is a timing chart illustrating the operation of the game device and the timing of related signals. [Figure 4] FIG. 4 is a diagram illustrating an example of data managed by the ticket management device. [Figure 5] FIG. 5 is a flowchart illustrating the operation of the ticket management system. [Figure 6] FIG. 6 is a flowchart illustrating an example of the ticket exchange operation. [Figure 7] FIG. 7 is a flowchart illustrating an example of the operation of moving a ticket. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Each drawing is merely a schematic illustration to enable a sufficient understanding of the present invention, and the present invention is not limited to the illustrated examples.

[0012] The embodiment of the present invention uses a gaming machine equipped with a ticket terminal device as an example. The gaming machine is a device that starts by receiving payment for the game to be offered from the user, for example, by depositing coins, and provides the user with a game. The ticket management system can also be applied to coin-activated service provision devices (also called service devices) such as laundry machines and massage machines, and to product vending machines, in the same way as gaming machines. Gaming machines differ in that the results obtained vary depending on the skill of the person operating the gaming machine, while laundry machines and massage machines provide a uniform service regardless of the skill of the person operating them. Adding a ticket provision function to a gaming machine can reduce user dissatisfaction due to differences in the results obtained. Furthermore, providing a ticket terminal device to a service provision device can improve the service provided to users.

[0013] First, the overall configuration of the ticket management system will be described. Figure 1 is a block diagram showing the configuration of the ticket management system.

[0014] The ticket management system 1 includes a game device 2, a ticket terminal device 3, a ticket management device 4, a ticket exchange device 5, and a user terminal 6.

[0015] The game device 2 comprises a deposit device 11 and a game machine 10. The game device 2 provides a game and receives payment from the user. To receive the game, the user deposits the payment using the deposit device 11. After the payment is made, the game machine 10 starts operating. Although the example shows a case where there is one game device 2, there may be multiple game devices 2. The present invention can also be applied to other service providing devices as long as they output a ticket signal.

[0016] The deposit device 11 is a device for depositing cash, a device for settling payment by credit card, a device for settling payment by electronic money, a device for settling payment by two-dimensional code payment, etc., and is a device for settling payment for the service provided. When the payment for the service is settled by the deposit device 11, a charging signal is output to the game machine 10.

[0017] The game machine 10 is a device that provides games to users as a service, and when a charging signal is input from the money deposit device 11, the game operation starts.

[0018] The ticket signal 30 is output from the game machine 10. The game machine 10 outputs the ticket signal 30 at predetermined times, such as when a game starts, during a game, or when a game ends, so that a predetermined number of tickets can be issued from the connected ticket issuing device. For example, the game machine 10 outputs a number of ticket signals 30 corresponding to the number of tickets to be issued within a predetermined period of time, such as within five seconds, after the game ends. For example, the number of tickets that can be issued can be determined based on the number of ticket signals 30. If two game tickets are to be issued after the game ends on the game device 2, two ticket signals 30 are output from the game machine 10 after the game ends, and if three game tickets are to be issued, three ticket signals 30 are output from the game machine 10. The ticket signal 30 also contains information regarding the number of tickets to be issued. Furthermore, it is preferable that the ticket signal be output before the user leaves the game device after the game ends and before the next game starts. Therefore, it is preferable that the ticket signal be output within 10 seconds immediately after the game ends.

[0019] Furthermore, if the game device 2 is equipped with a start button, when the payment for the service is settled by the deposit device 11 and the start button is pressed, a billing signal is output from the deposit device 11 and input to the game machine 10, and the game machine 10 starts up.

[0020] The ticket terminal device 3 is installed for each game device 2, inputs the ticket signal 30 output from the game device 2, analyzes the input ticket signal 30, calculates the number of electronic tickets to be generated, generates ticket information, and outputs the ticket information to an external device.

[0021] The ticket terminal 3 comprises a terminal control circuit 12, a terminal display device 14, a terminal reading device 15, an input means 16, a terminal communication device 17, and a charging signal generating device 13. The charging signal generating device 13 will be described later, but it is not necessarily provided. The ticket terminal 3 can be built into the game device 2 or integrated with it. Alternatively, the ticket terminal 3 can be added to the game device 2 later and installed either internally or externally. It is possible to add a ticket terminal 3 to an existing game device 2.

[0022] The terminal control circuit 12 controls the operation of the ticket terminal device 3. The terminal control circuit 12 is equipped with a CPU and memory (not shown), and its operation is controlled according to a program stored in the memory. The memory stores setting values ​​and also serves as a work area for the CPU.

[0023] The terminal display device 14 is controlled by the terminal control circuit 12. The terminal display device 14 is a display device, such as a liquid crystal display device, that displays characters, symbols, images, etc. under the control of the terminal control circuit 12. The terminal display device 14 can display values ​​stored in the ticket management device 4, such as the number of generated electronic tickets, the number of electronic tickets owned by the user obtained from the ticket management device 4 described below, and the cumulative number of electronic tickets acquired by the user.

[0024] The terminal reading device 15 is controlled by the terminal control circuit 12. The terminal reading device 15 is a reading device that reads identification information from a card on which the identification information is recorded. For example, the card may be a magnetic card or an IC card on which at least the identification information is recorded, or a card on which at least the identification information is recorded as a barcode or a two-dimensional code. The identification information may be a numeric string, an alphabet string, or a character string containing numbers and alphabets, and is information that is uniquely assigned to the card. The terminal reading device 15 reads at least the identification information from the card and outputs it to the terminal control circuit 12. The terminal control circuit 12 acquires the identification information and uses it for control. The terminal reading device 15 may also have a function to write data to the card. The terminal reading device 15 may be a magnetic card reader capable of reading magnetic cards, an IC card reader capable of reading IC cards, a barcode reader capable of reading barcodes, a two-dimensional code reader capable of reading two-dimensional codes, or the like. If the identification information can be read by the aforementioned deposit device 11, the identification information read by the deposit device 11 can be used instead of the identification information read by the terminal reading device 15. The identification information read by the deposit device 11 is output to the ticket terminal device 3, and the identification information is acquired by the terminal control circuit 12, which uses the acquired identification information for control purposes.

[0025] The terminal control circuit 12 includes an analysis means for analyzing the barcode or two-dimensional code data read by the terminal reader 15 and decoding it into data such as letters and numbers. To be able to handle a variety of recording media, it is preferable that the terminal reader 15 is provided with readers compatible with a variety of recording media. The identification information is also information for identifying the user who owns the card that will be provided with the game.

[0026] The input means 16 is controlled by the terminal control circuit 12. The input means 16 inputs a ticket signal 30 output from the game device 2. The terminal control circuit 12 acquires the input ticket signal 30 and uses it for control. For example, the terminal control circuit 12 counts the number of ticket signals 30, stores the resulting count value as the number of electronic tickets, and uses it for control. The input means 16 also includes an interface for inputting signals output from the game device 2, and is equipped with connectors, terminals, etc. The ticket signal 30 may be numerical data indicating the number of tickets to be issued. In this case, the numerical data is transmitted via serial communication. The terminal control circuit 12 generates and stores information on the number of electronic tickets to be issued based on the ticket signal 30 acquired via the input means 16. The terminal control circuit 12 uses this information on the number of electronic tickets for control. The terminal control circuit 12 generates ticket information that associates information on the number of electronic tickets with identification information read by the terminal reader 15. When the ticket information is generated by the terminal control circuit 12, in addition to these two types of information, it can also include information such as device ID information individually assigned to the ticket terminal device 3 and the game device 2, and the date and time when the ticket information was generated.

[0027] The terminal communication device 17 is controlled by the terminal control circuit 12. The terminal communication device 17 is connected to an external device, for example, the ticket management device 4 described below, and transmits and receives data. The terminal control circuit 12 acquires data from the ticket management device 4 via the terminal communication device 17, uses it for control, and outputs various information to the ticket management device 4 via the terminal communication device 17. The ticket terminal device 3 outputs ticket information to the ticket management device 4, including at least the identification information read by the terminal reading device 15 and information on the number of electronic tickets generated by the terminal control circuit 12.

[0028] The charging signal generator 13 is controlled by the terminal control circuit 12. The charging signal generator 13 generates and outputs a signal equivalent to the charging signal output by the deposit device 11 to the game machine 10. For example, if the card used has an electronic money function, the terminal control circuit 12 controls the terminal reader 15 to read and write the card instead of the deposit device 11 of the game machine 2, perform payment using electronic money, and after payment, control the terminal control circuit 12 to generate a signal equivalent to the charging signal and output it to the game machine 10. Furthermore, the terminal control circuit 12 can read identification information from a card with an electronic money function and use it for control. The deposit device 11 can also output a payment completion signal 8, indicated by a dashed line, indicating that payment has been completed, and the charging signal generator 13 can input this signal. When the charging signal generator 13 inputs the payment completion signal 8, the terminal control circuit 12 controls the charging signal generator 13 to output a charging signal 9, indicated by a dashed line, to the game machine 10. The game device 2 starts operating in response to input of the charging signal 9 output from the ticket terminal device 3. The charging signal generating device 13 is for operating the game device 2 by the ticket terminal device 3, and therefore is a function that may or may not be provided, taking into consideration the convenience of the user.

[0029] The ticket management device 4 manages information on the number of electronic tickets associated with each piece of identification information. Because cards are owned by users, the identification information of a card can also be considered the identification information of the user who owns the card. The user who owns the card can be identified from the card's identification information. Furthermore, if a user owns multiple cards, the user will have identification information for each card. If a user owns multiple cards, it is not possible to identify a single card from the user, but it is possible to know which cards the user owns. Here, identification information using a card is used as an example, but information that can identify a user, such as an email address or telephone number, can also be used as identification information, and a user account set up in the ticket management device 4 can also be used as identification information.

[0030] The ticket management device 4 includes a management device control circuit 18, a management device memory 19, and a management device communication device 20. The ticket management device 4 is a computer equipped with a communication function, such as a server.

[0031] The management device control circuit 18 controls the operation of the ticket management device 4. The management device control circuit 18 is equipped with a CPU and memory (not shown), and its operation is controlled according to a program stored in the memory. The memory also stores setting values ​​and serves as a work area for the CPU.

[0032] The management device memory 19 is controlled by the management device control circuit 18. The management device memory 19 forms a database that stores information on the number of electronic tickets in association with identification information under the control of the management device control circuit 18. The database stores information on the number of electronic tickets associated with identification information, and the management device control circuit 18 can obtain the number of electronic tickets for each piece of identification information.

[0033] The management device communication device 20 is controlled by a management device control circuit 18. The management device communication device 20 is connected to external devices, such as the ticket terminal device 3, a user terminal 6 (described later), and a ticket exchange device 5, and transmits and receives data. The management device control circuit 18 acquires various data via the management device communication device 20, uses it for control, and outputs various information to the external devices via the management device communication device 20.

[0034] The user terminal 6, which will be described later, can access the ticket management device 4 and display a user page, which is a web page. In the management device memory 19 of the ticket management device 4, information to be displayed on the user page is stored in a database associated with identification information. When displaying the user page on the user terminal 6, the desired information is extracted from the database and displayed. The ticket management device 4 extracts the desired information instructed by the user terminal 6 from the database, converts it into data so that it can be displayed on the user terminal 6, and outputs it. The database stores a password corresponding to the identification number, and when the user terminal 6 accesses the ticket management device 4 and is successfully authenticated using the identification number and password, the user terminal 6 is able to access the user page and display the user page. The user page displays at least information on the number of electronic tickets, as well as information on acquired and unused benefits.

[0035] The ticket exchange device 5 is a device that exchanges issued electronic tickets for benefits provided to users. The ticket exchange device 5 can also read the identification information on the card using the exchange device reader 28 and display the number of electronic tickets corresponding to the identification information. The ticket exchange device 5 is connected to the ticket management device 4 and can acquire and display information associated with the identification information stored in the ticket management device 4. The ticket exchange device 5 acquires the identification information, accesses the ticket management device 4, and acquires various information stored in the ticket management device 4, such as the number of electronic tickets corresponding to the identification information. The ticket management device 4 extracts the number of electronic tickets corresponding to the identification information stored therein from the database and outputs it to the ticket exchange device 5. The ticket management device 4 can also extract information other than the number of electronic tickets corresponding to the input identification information and output the extracted information to the ticket exchange device 5. The ticket exchange device 5 can display various information input from the ticket management device 4.

[0036] The ticket exchange device 5 displays selectable benefits that can be exchanged according to the acquired identification number and the associated electronic ticket quantity information. The user can acquire the benefit in exchange for the number of electronic tickets corresponding to that benefit. The ticket exchange device 5 outputs the identification information and the number of electronic tickets corresponding to the benefit to the ticket management device 4. The ticket management device 4 subtracts the number of electronic tickets corresponding to the input benefit from the electronic ticket quantity information associated with the identification number and updates the data. The ticket management device 4 prints the selected benefit using the printer 26 or ejects it from the exchange item ejection device 29.

[0037] The ticket exchange device 5 includes an exchange device control circuit 24 , an exchange device communication device 25 , a printer 26 , an exchange device operation panel 27 , an exchange device reading device 28 , and an exchange item ejection device 29 .

[0038] The exchange device control circuit 24 includes a CPU and memory (not shown), and its operation is controlled according to a program stored in the memory. The memory also stores setting values ​​and serves as a work area for the CPU. The exchange device control circuit 24 also controls each element of the ticket exchange device 5 according to the program.

[0039] The exchange communication device 25 is connected to the exchange control circuit 24 and is controlled by the exchange control circuit 24. The exchange communication device 25 performs data communication with an external device. For example, the external device is the ticket management device 4.

[0040] The printer 26 is connected to the exchange device control circuit 24 and controlled by the exchange device control circuit 24. The printer 26 is a recording device such as a thermal, inkjet, or electrophotographic recording device that is controlled by the exchange device control circuit 24 and prints characters, symbols, images, and the like on recording paper. The rewards include game discount coupons, free game coupons, parking discount coupons, product exchange coupons, and coupons that can be exchanged for electronic tickets, and the printer 26 generates these rewards by recording characters and two-dimensional codes on recording paper. The printer 26 records the rewards on recording paper and ejects it. The user can obtain the ejected recording paper on which the rewards are recorded and use it.

[0041] The exchange device operation panel 27 is connected to and controlled by the exchange device control circuit 24. The exchange device operation panel 27 is equipped with input means and display means, and is a device equipped with a touch panel or a keyboard and a liquid crystal display device. The exchange device operation panel 27 is controlled by the exchange device control circuit 24 and displays characters and images. The exchange device operation panel 27 is controlled by the exchange device control circuit 24 and can acquire the touch position and input one button selected from multiple buttons, or characters and numbers. The exchange device operation panel 27 displays benefits that can be exchanged for electronic tickets, allows the user to select one, and outputs the selection result to the exchange device control circuit 24.

[0042] The exchange device reader 28 is connected to the exchange device control circuit 24 and is controlled by the exchange device control circuit 24. The exchange device reader 28 is a reader that reads identification information from a card on which the identification information is recorded. For example, the card is a magnetic card or IC card on which at least the identification information is recorded, or a card on which at least the identification information is recorded as a barcode or two-dimensional code. The exchange device reader 28 reads at least the identification information from the card and outputs it to the exchange device control circuit 24. The exchange device control circuit 24 acquires the identification information and uses it for control. The exchange device reader 28 may also have a function to write data to the card.

[0043] The exchange item discharge device 29 is connected to and controlled by the exchange device control circuit 24. It is a device that discharges the benefit selected on the exchange device operation panel 27 so that the user can acquire it. For example, a product such as a stuffed toy is discharged in exchange for a predetermined number of electronic tickets.

[0044] The user terminal 6 is a computer with a communication function operated by a user, such as a smartphone, a mobile phone, a notebook PC, or a tablet PC.

[0045] The user terminal 6 includes a user terminal control circuit 21, a user terminal communication device 22, and a user terminal operation panel 23.

[0046] User terminal control circuit 21 controls the operation of user terminal 6. User terminal control circuit 21 is equipped with a CPU and memory (not shown), and its operation is controlled according to a program stored in the memory. The memory also stores setting values ​​and serves as a work area for the CPU.

[0047] The user terminal communication device 22 is controlled by the user terminal control circuit 21. The user terminal communication device 22 is connected to an external device, for example, the ticket terminal device 3, and transmits and receives data thereto.

[0048] The user terminal control circuit 21 acquires various data via the user terminal communication device 22, uses it for control, and outputs various information to an external device via the user terminal communication device 22.

[0049] The user terminal operation panel 23 is connected to the user terminal control circuit 21 and controlled by the user terminal control circuit 21. The user terminal operation panel 23 is equipped with an input means and a display means, and is a device equipped with a touch panel or a keyboard and a liquid crystal display device. The user terminal operation panel 23 is controlled by the user terminal control circuit 21 and displays characters and images. The user terminal operation panel 23 is controlled by the user terminal control circuit 21 and can acquire the position of a touch and can input one button selected from multiple buttons, or characters and numbers.

[0050] FIG. 2 is a diagram illustrating an example of a terminal reader.

[0051] The terminal reader 15 is a reader that reads identification information from a card on which the identification information is recorded. For example, the card may be an IC card 34 on which at least the identification information is recorded, a magnetic card 35 on which at least the identification information is recorded, or a code card 36 on which at least the identification information is recorded as an image code 37 such as a barcode or a two-dimensional code on a paper or resin medium. The terminal reader 15 includes at least one reader selected from the group consisting of an IC card reader 31 that reads at least the identification information from the IC card 34, a magnetic card reader 32 that reads at least the identification information from the magnetic card 35, and an image reader 33 that reads at least the identification information from the code card 36. Furthermore, an image code 37 such as a barcode or a two-dimensional code containing the identification information can be displayed on the user terminal operation panel 23 of the user terminal 6, and the displayed code 37 can be read by the image reader 33. The exchange device reader 28 may also have a configuration similar to that of the terminal reader 15.

[0052] Next, the ticket signals output from the game device will be described. Figure 3 is a timing chart illustrating the operation of the game device and the timing of the related signals.

[0053] The game device operation timing chart in FIG. 3 shows the timing at which the state of the game device 2 changes. When a deposit 49, which is payment for the game, is made into the game device 2 and a start button or the like is pressed, operation of the game device 10 starts 50. Operation of the game device 10 eventually ends 51. Time-up 52 is the timing when a first predetermined time has elapsed after the ticket signal 30 is input from the game device 10. For example, the first predetermined time is about 10 to 30 seconds, and is the operation time for the user to obtain an electronic ticket if they intend to obtain one after the game ends. Time-up 52 can be changed by time or by button input. After time-up 52, the next deposit 53 is made and the game starts 54. Such state changes are repeated. The timing of inputting the ticket signal 30 corresponding to the started game into the ticket terminal device 3 and reading the identification information from the card will be described below.

[0054] The ticket signal 30 is output between the end of the game machine 10 (51) and the second predetermined time. The ticket signal 30 is input by the ticket terminal 3, and there may be one or more ticket signals 30. The number of tickets issued may be different signals at each timing. The ticket signal 30 is output until the time is up (52) and input to the ticket terminal 3. The ticket signal chart in FIG. 3 shows the timing at which the ticket signal 30 is output from the game machine 2 and input to the ticket terminal 3. The ticket signal 30 is output from the game machine 2 when the game ends, and the ticket terminal 3 inputs the ticket signal 30 at approximately the same time. The second predetermined time is a time predetermined by the game machine 2. The first predetermined time is set to be longer than the second predetermined time. The first predetermined time is set to be several seconds longer than the second predetermined time, and it is preferable that this difference be set as short as possible so as not to cause user dissatisfaction. For example, the difference is 1 to 2 seconds, preferably within 5 seconds.

[0055] The first ID reading period 40 is a period during which identification information is read from a card, and is a period during which identification information associated with an electronic ticket generated based on a ticket signal 30 output in response to a deposit 49 and a start 50 is read. The first ID reading period 40 extends from before the deposit 49 until time-out 52. However, even before time-out 52, if an electronic ticket has already been generated and ticket information has been output to an external device, the period falls outside the range of the first ID reading period 40. In other words, ticket information is generated only once for the corresponding ticket signal 30 and output to the outside.

[0056] The second ID reading period 41 is a period during which identification information associated with an electronic ticket corresponding to a ticket signal output in response to deposit 53 and start 54 is read. The second ID reading period 41 begins after the end of the first ID reading period 40 or after time-out 52. The end of the second ID reading period 41 is the same as that of the first ID reading period 40.

[0057] The H level 42 of the ticket output possible period indicates the period during which an electronic ticket and ticket information may be generated and output to an external device. When an electronic ticket and ticket information are generated and output to an external device, the level changes from H to L, indicating a period during which an electronic ticket cannot be generated.

[0058] The latter part of the first ID reading period 40 indicated by the dashed line indicates that the first ID reading period 40 lasts up to the time-out 52. The beginning part of the second ID reading period 41 indicated by the dashed line indicates that the second ID reading period 41 starts at the end of the ticket output period at the latest.

[0059] As for the first identification information, if it is before the ticket signal 30 is input to the ticket terminal device 3, the last acquired identification information becomes the valid identification information. For example, if a card is read multiple times within the first ID reading period 40 before the ticket signal 30 is input to the ticket terminal device 3, the identification information of the last card read becomes valid. The valid identification information and electronic ticket information are output to an external device. If it is within the first ID reading period 40 and after the ticket signal 30 is input to the ticket terminal device 3, the identification information of the first card read becomes valid.

[0060] Next, we will explain information related to electronic tickets stored in the ticket management device 4. Fig. 4 is a diagram illustrating an example of data managed by the ticket management device. The ticket management device 4 stores various data for each piece of identification information. The data for each piece of identification information stored in the ticket management device 4 also includes history information.

[0061] The information about the total number of tickets is the number of the latest electronic tickets associated with the identification information. It can also be said to be the number of electronic tickets owned by the user identified by the identification information. The update date and time are stored together with the number of the latest electronic tickets associated with the identification information.

[0062] Acquisition information is historical information when the number of electronic tickets held by a user increases, such as electronic tickets paid out at the end of a game. Each time the number of electronic tickets held by a user increases, new acquisition information is added and stored. For example, it is information about the number of electronic tickets paid out to a user when a game ends. The acquisition information includes the number of electronic tickets entered from the ticket terminal device 3 along with their identification information as the number of acquired tickets, the date and time when the electronic ticket was acquired as the acquisition date and time, and the reason for acquisition. The reason for acquisition is information that identifies the reason for acquisition, such as whether the ticket was paid out at the end of a game or acquired through a coupon or transfer.

[0063] Usage information is historical information when the number of electronic tickets owned by a user decreases, such as when an electronic ticket is exchanged for a benefit. Each time the number of electronic tickets owned by a user decreases, additional usage information is stored. For example, a user's electronic tickets decrease when they are exchanged for a benefit to obtain a benefit. The number of used tickets is the number of electronic tickets that have decreased, and the date and time of use is the date and time of the exchange. The reason for use is information that identifies the reason why the number of tickets owned by the user decreased, such as information about the benefit exchanged. Information about the benefit exchanged is a coupon or discount voucher. In addition, the number of electronic tickets owned may decrease when an electronic ticket is transferred to another user.

[0064] The attribute information includes, for example, information about the user, such as the user name and contact information, and the total number of tickets acquired, which is information about the cumulative value of electronic tickets acquired up to that point. The total number of tickets acquired can be used to determine the user's rank according to this number, or to grant benefits according to the rank. The rank is stored in the attribute information. Electronic tickets can also be added as a bonus depending on the rank.

[0065] Benefit information is information about benefits acquired by the user, such as benefits acquired by the user in exchange for electronic tickets. Owned benefit information is information about benefits acquired by the user, and each time a user acquires a benefit, additional benefit information is added and stored. Furthermore, when the benefit is used, date and time information is stored as the date and time the benefit was used. It is possible to determine whether an acquired benefit has been used. Benefit attribute information is attribute information about the benefit, and stores information about the benefit, such as the usage conditions, such as the period during which the benefit can be used.

[0066] Information about electronic tickets associated with each identification information is stored as a database, and various information can be extracted and used for control based on search conditions such as identification information, date and time, etc. The extracted various information is output to an external device, acquired by the external device, and the various information acquired by the external device can be used for control.

[0067] Next, the operation of the ticket management system will be described using the flowcharts of Figures 5 to 7. The operation of the ticket management system is realized by controlling each element shown in the block diagram of Figure 1 by each control circuit in accordance with a pre-stored program.

[0068] FIG. 5 is a flowchart illustrating the operation of the ticket management system.

[0069] Game processing device processing is processing by the game device 2, ticket terminal device ticket signal processing is processing by the ticket management device 4, and ticket management device ticket verification processing and ticket management device ticket verification processing are processing by the ticket management device. Various operations of the game device 2 are controlled by a control circuit (not shown) built into the game device 2. Various operations of the ticket terminal device 3 are controlled by a terminal control circuit 12. Various operations of the ticket management device 4 are controlled by a management device control circuit 18.

[0070] First, the operation of the game device 2 will be described.

[0071] In step S1, the game device 2 waits for payment of the game fee, and when payment of the game fee has been made, the deposit device 11 outputs a charging signal to the game machine 10. Alternatively, if operation of the start button is a condition for starting the game, the deposit device 11 outputs a charging signal to the game machine 10 when both payment of the game fee and pressing of the start button are detected.

[0072] In step S2, the game machine 10 inputs a charging signal and the game starts.

[0073] In step S3, the game device 2 provides the user with a game, and the user performs various operations on the game device 2 to receive the game.

[0074] In step S4, the game device 2 ends the game being provided if a predetermined condition is met.

[0075] In step S5, the game device 2 outputs a ticket signal 30 to the ticket terminal device 3 so that a predetermined number of tickets can be issued in accordance with predetermined conditions.

[0076] The game device 2 provides the user with a game, and after providing the game, outputs a ticket signal 30 to the ticket terminal device 3. Then, the process returns to step S1 to wait for the game to be played again.

[0077] Next, we will explain the operation of the ticket terminal device 3. The ticket terminal device 3 acquires identification information that identifies the user who will be provided with the game, inputs the ticket signal output from the game device 2, calculates the number of electronic tickets to be issued, and outputs the identification information and the number of electronic tickets to be issued to the ticket management device 4.

[0078] Steps S6 to S10 are an identification information acquisition process for acquiring identification information that identifies the user who will be provided with the game. The identification information acquisition process is a process in which the ticket terminal 3 acquires the identification information before inputting the ticket signal from the game device 2. The ticket terminal 3 can also acquire the identification information after inputting the ticket signal and before timeout by a process described below.

[0079] In step S6, the ticket terminal device 3 monitors whether information including the identification information recorded on the recording medium has been read by the terminal reading device 15, and if the identification information has been read, it proceeds to step S7, and if it has not been read, it proceeds to step S11.

[0080] Next, in step S7, the terminal control circuit 12 analyzes the read data, extracts the identification information, acquires the extracted identification information, and uses it for control. The identification information is stored in the terminal control circuit 12 as necessary.

[0081] For example, if the recording medium is an IC card 34, the IC card reader 31 reads the identification information recorded on the IC card 34, which is acquired by the terminal control circuit 12 and used for control. For example, if the recording medium is a code card 36 on which a two-dimensional code is recorded, the image reader 33 reads the two-dimensional code, which is analyzed by the terminal control circuit 12 and the identification information is extracted. The extracted identification information is acquired by the terminal control circuit 12 and used for control.

[0082] Next, in step S8, the ticket terminal device 3 outputs an information output request to the ticket management device 4, along with the acquired identification information. In this example, the ticket terminal device 3 performs a process of acquiring information on the total number of electronic tickets from the ticket management device 4. The information output request includes the identification information and information specifying the total number of tickets as information specifying the information to be acquired. The information specifying the information to be acquired is information related to the information stored in association with the identification information stored by the ticket management device 4, such as information on the total number of tickets, usage information, benefit information, attribute information, etc. Based on the identification information included in the information output request and the information specifying the information to be acquired, the ticket management device 4 extracts the desired information from the various types of stored information.

[0083] In step S9, the ticket terminal 3 waits for a response from the ticket management device 4 to the information output request, and obtains information on the total number of tickets sent from the ticket management device 4.

[0084] In step S10, the ticket terminal device 3 displays the information on the total number of tickets obtained from the ticket management device 4 on the terminal display device 14. The user can check the number of electronic tickets he or she owns. The ticket terminal device 3 can also obtain and display other information that is returned in response to the information output request from the ticket management device 4.

[0085] Here, the ticket management process of the ticket management device 4 will be described.

[0086] In step S22, the ticket management device 4 receives an information output request from the ticket terminal device 3. The management device control circuit 18 of the ticket management device 4 extracts the identification information and information specifying the information to be acquired from the received information output request and uses these for control. An example will be described in which the management device control circuit 18 receives information specifying the total number of tickets as the information specifying the information to be acquired.

[0087] Next, in step S23, the management device control circuit 18 extracts information on the total number of tickets for the acquired identification information from the information stored in the management device memory 19. The management device control circuit 18 can extract desired information from the database configured in the management device memory 19 based on the identification information and information specifying the information to be acquired, and can use the extracted information for control.

[0088] Next, in step S24, the ticket management device 4 outputs the extracted information on the total number of tickets to the ticket terminal device 3.

[0089] Next, the processing of the ticket terminal device 3 will be explained again.

[0090] In step S11, the ticket terminal 3 monitors whether or not a ticket signal output from the game device 2 has been input. If a ticket signal has not been input, the ticket terminal 3 proceeds to step S6 and checks whether identification information identifying the user of the game device 2 has been read. If a ticket signal has been input, the ticket terminal 3 proceeds to step S12. Before a ticket signal is input, the ticket terminal 3 can read the card and obtain identification information any number of times. The newly obtained identification information and related information become valid information, while the previously obtained identification information and related information become invalid, and the information temporarily stored in the ticket terminal 3 during the processing is updated with the newly obtained information. In this case, the ticket terminal 3 generates ticket information (described later) corresponding to the last obtained identification information.

[0091] In step S12, the ticket signal output from the game device 2 is input.

[0092] Next, in step S13, the ticket terminal device 3 calculates the number of electronic tickets based on the input ticket signal. For example, if the ticket signal is a pulse signal, the number of electronic tickets can be a number corresponding to the number of input pulse signals. The calculation is performed based on a predetermined rule. The number of electronic tickets can be determined by multiplying the input number of pulses by a predetermined number. The multiplier can also be changed depending on the user rank in the attribute information stored in the ticket management device 4. If the predetermined number is 1, the number of pulses is the number of electronic tickets, and if the predetermined number is 2, the number of pulses multiplied by 2 is the number of electronic tickets. The predetermined rule may be a formula that expresses the relationship between the number of pulses and the number of electronic tickets, or it may be a table that shows the relationship between the number of pulses and the number of electronic tickets.

[0093] Next, in step S14, the ticket terminal 3 displays the number of electronic tickets calculated in step S12 on the terminal display device 14. When the game ends, the number of electronic tickets issued to the user is displayed.

[0094] Next, in step S15, the ticket terminal 3 determines whether or not the identification information has been acquired, and if the identification information has been acquired, the process proceeds to step S16, and if not, the process proceeds to step S20. This example considers the cases where a ticket signal is input to the ticket terminal 3 after the ticket terminal 3 has acquired the identification information, and the cases where a ticket signal is input to the ticket terminal 3 before the ticket terminal 3 acquires the identification information. Until a predetermined time has passed since the ticket terminal 3 input the ticket signal, the ticket terminal 3 can acquire the identification information that identifies the user who acquires the electronic ticket.

[0095] In step S20, the ticket terminal 3 checks whether the identification information has been acquired after the ticket signal has been input. For example, if the user has performed an operation to read the card into the terminal reader 15, the same processes as steps S6 to S10 and steps S22 to S24 are performed.

[0096] In step S21, the ticket terminal 3 determines whether a predetermined time, such as 10 seconds, has passed since the ticket signal was input. If the predetermined time has not passed, the ticket terminal 3 proceeds to step S15 to check whether identification information has been acquired. If the predetermined time has passed, the ticket terminal 3 determines that no user is available to acquire the generated electronic ticket, and ends the process.

[0097] Next, in step S16, the ticket terminal 3 generates ticket information. The ticket information is information that combines at least an identification number corresponding to the user who acquires the electronic ticket and the number of electronic tickets to be issued. The ticket information can also include information such as a device ID and date and time information.

[0098] Next, in step S17, the ticket terminal device 3 transmits to the ticket management device 4 the ticket information generated in step S16.

[0099] Here, the information update process of the ticket management device 4 will be described.

[0100] In step S25, the ticket management device 4 inputs the ticket information output from the ticket terminal device 3 in step S17. The ticket management device 4 extracts the identification information and the number of electronic tickets from the input ticket information and makes them available for control.

[0101] Next, in step S26, the ticket management device 4 accesses the information for each identification information stored in the management device memory 19 and adds or updates the information. The ticket management device 4 adds the number of electronic tickets entered as the number of acquired tickets, the date and time when the information was entered as the acquisition date, and information indicating that the acquisition was based on the use of the game device 2 as the reason for acquisition, as historical information associated with the identification information, as new acquisition information. The ticket management device 4 also extracts the total number of tickets corresponding to the identification information. The ticket management device 4 adds the number of electronic tickets acquired this time to the extracted total number of tickets to calculate a new total number of tickets, and uses this value to update the information on the total number of tickets stored in association with the identification information stored in the management device memory 19. The ticket management device 4 also updates the update date and time in the same way.

[0102] Next, in step S27, the ticket management device 4 outputs and notifies the ticket terminal device 3 of update information indicating that the update of the information in the management device memory 19 has been completed based on the ticket information output in step S17 and input in step S25.

[0103] Next, the processing of the ticket terminal device 3 will be explained again.

[0104] In step S18, the ticket terminal 3 receives update information from the ticket management device 4.

[0105] Next, in step S19, the ticket terminal device 3 displays on the terminal display device 14 that an electronic ticket has been acquired. By including information on the new total number of tickets stored in association with the identification information in the update information, the terminal display device 14 can display the new information on the total number of tickets, allowing the user to confirm the total number of electronic tickets held by the user after the update.

[0106] The ticket terminal 3 generates ticket information corresponding to the identification information last acquired before generating the ticket information. In step S15, the ticket terminal 3 generates ticket information after determining that identification information has been acquired. That is, the ticket terminal 3 generates ticket information corresponding to the identification information last acquired before the ticket signal is input from the game device 2. If the ticket terminal 3 has not acquired identification information before the ticket signal is input from the game device 2 and acquires identification information after the ticket signal is input, the ticket terminal 3 can acquire identification information corresponding to the ticket signal only once, but only before time is up. The user can have the ticket terminal 3 read a card any number of times to update the identification information before the end of the game. If the ticket terminal 3 acquires identification information after the ticket signal is input, an electronic ticket corresponding to the identification information is acquired.

[0107] Next, the operation of exchanging an electronic ticket held by a user for a benefit will be described. Fig. 6 is a flowchart illustrating an example of the ticket exchange operation. Various operations of the ticket exchange device 5 are controlled by the exchange device control circuit 24. Various operations of the ticket management device 4 are controlled by the management device control circuit 18.

[0108] Steps S30, S31, and S32 are processes performed by the ticket exchange device 5.

[0109] Steps S30 to S36 are processing for acquiring identification information that identifies the user who will exchange the electronic ticket for a benefit.

[0110] In step S30, the ticket exchange device 5 reads the identification information from the recording medium using the exchange device reader .

[0111] Next, in step S31, the read data is analyzed by the exchange control circuit 24 to extract identification information, which is then acquired by the exchange control circuit 24 and used for control. If necessary, the identification information is stored in the exchange control circuit 24. For example, the exchange reader 28 has the same configuration as the terminal reader 15.

[0112] Next, in step S32, the ticket exchange device 5 outputs an information output request to the ticket management device 4, along with the acquired identification information. In this example, a process is performed to acquire information on the total number of tickets from the ticket management device 4. The information output request includes the identification information and information specifying the information to be acquired, which information specifies the total number of tickets. The information specifying the information to be acquired is information related to the information stored in association with the identification information stored by the ticket management device 4, such as information on the total number of tickets, usage information, benefit information, attribute information, etc. Based on the identification information included in the information output request and the information specifying the information to be acquired, the ticket management device 4 extracts the desired information from the various types of stored information.

[0113] Next, steps S33, S34, and S35 are processes performed by the ticket management device 4.

[0114] In step S33, the ticket management device 4 receives an information output request from the ticket exchange device 5. The management device control circuit 18 of the ticket management device 4 extracts the identification information and information specifying the information to be acquired from the received information output request, and uses them for control. An example will be described in which the management device control circuit 18 receives information specifying the total number of tickets as the information specifying the information to be acquired.

[0115] Next, in step S34, the management device control circuit 18 extracts information on the total number of tickets corresponding to the acquired identification information from the information stored in the management device memory 19. Based on the identification information and information specifying the information to be acquired, the management device control circuit 18 can extract the desired information from the database configured in the management device memory 19 and use it for control.

[0116] Next, in step S35, the ticket management device 4 outputs information on the extracted total number of tickets to the ticket exchange device 5.

[0117] The ticket exchange device 5 performs the processes from step S36 to step S39.

[0118] In step S36, the ticket exchange device 5 waits for a response from the ticket management device 4 to the information output request, and obtains information on the total number of tickets sent from the ticket management device 4.

[0119] In step S37, the ticket exchange device 5 displays the information on the total number of tickets obtained from the ticket management device 4 on the exchange device operation panel 27. The user can check the number of electronic tickets he or she owns. Furthermore, the exchange device control circuit 24 of the ticket exchange device 5 displays a menu that the user can select on the exchange device operation panel 27. The exchange device operation panel 27 displays the number of electronic tickets the user owns, the exchangeable benefits, and the number of electronic tickets required to exchange them.

[0120] Next, in step S38, buttons corresponding to the benefits to be exchanged for the ticket are displayed on the menu displayed on the exchange device operation panel 27, and the user selects the desired button. Since the exchange device operation panel 27 is a touch panel, the user touches the desired button. The exchange device control circuit 24 executes a process to exchange the benefit corresponding to the button selected by the user for the electronic ticket.

[0121] Next, in step S39, the ticket exchange device 5 outputs a ticket use request to the ticket management device 4 to exchange the electronic ticket for a benefit. The ticket management device 4 manages information related to electronic tickets, including the use of the electronic ticket. The ticket use request includes identification information that identifies the user exchanging the electronic ticket and information about the benefit to be exchanged for the electronic ticket. The information about the benefit is, for example, information indicating the number of electronic tickets required for exchange to obtain the benefit and the benefit to be exchanged. If the ticket management device 4 previously stores the relationship between the information indicating the benefit to be exchanged and the number of electronic tickets required for exchange, the number of electronic tickets required for exchange to obtain the benefit does not need to be included in the ticket use request.

[0122] The processes from step S40 to step S43 are performed by the ticket management device 4.

[0123] In step S40, the ticket management device 4 inputs the ticket use request output from the ticket exchange device 5. The ticket management device 4 extracts the identification information and information related to the benefit to be exchanged included in the ticket use request, and uses the extracted information for control. The extracted information includes the identification information, information indicating the benefit, and the number of electronic tickets required for exchange. If the ticket use request does not include the number of electronic tickets required for exchange, the number of electronic tickets required for exchange corresponding to the desired benefit is obtained from the correspondence between the information indicating the benefit stored in the ticket management device 4 and the number of electronic tickets required for exchange, based on the information indicating the benefit.

[0124] In step S41, the ticket management device 4 updates the information stored in the management device memory 19 and adds and stores new historical information. The ticket management device 4 subtracts the number of electronic tickets required to be exchanged to obtain the benefit from the total number of tickets associated with the acquired identification information to obtain a new total number of tickets, updates the information, and also updates the update date and time. Furthermore, since the electronic ticket is used to obtain the benefit, the ticket management device 4 adds and stores historical information as usage information. The information on the number of tickets used is the number of electronic tickets required for exchange. The information on the date and time of use is the date and time when the ticket use request was input. The information on the reason for use and the exchanged benefit is information indicating the exchange of the benefit and information indicating the benefit to be exchanged.

[0125] Next, in step S42, the ticket management device 4 adds information about the benefits obtained by the user to the benefit information as historical information and stores it. Owned benefit information is information indicating the benefits exchanged by the user. Benefit attribute information is information about the benefits, including conditions such as the period during which the benefit can be used, and the date and time of exchange. The benefit usage date and time is stored as the date and time when the benefit is used. If the date and time of use is stored as the benefit usage date and time, the benefit cannot be used. For example, in the case of a benefit with a usage limit of multiple times, the counted number of uses is stored in the benefit attribute information. When the counted number of uses reaches the usage limit, processing is performed to make the benefit unusable. The benefit usage date and time is updated when the benefit is used, so if the benefit usage date and time is the value set by default, it can be determined that the benefit has not been used.

[0126] Next, in step S43, the ticket management device 4 outputs information indicating that the ticket use process, such as the process of subtracting the number of electronic tickets held to obtain a benefit, and the process of storing benefit information and history information, has been completed, to the ticket exchange device 5. The information indicating the completion of the ticket use process includes information on the new total number of tickets after exchanging the benefit.

[0127] Next, the processing of the ticket exchange device 5 will be explained again.

[0128] In step S44, if the ticket exchange device 5 receives information from the ticket management device 4 indicating that the ticket usage process has been completed, the ticket exchange device 5 issues a benefit to be offered to the user. If the benefit to be offered to the user is an item, the exchange device control circuit 24 controls the exchange item ejection device 29 to eject the item. If the benefit to be offered to the user is a printed matter such as a coupon, the exchange device control circuit 24 controls the printer 26 to print and eject the printed matter such as a coupon. The ticket exchange device 5 can issue a benefit in exchange for an electronic ticket.

[0129] Next, in step S45, information about the new total number of tickets after exchanging the benefits is displayed on the exchange device operation panel 27 of the ticket exchange device 5. After a predetermined time has elapsed since the display, the display on the exchange device operation panel 27 returns to the initial state.

[0130] Next, the process for transferring tickets will be described. It is possible to transfer the number of electronic tickets corresponding to one card from one of two cards to the other. For example, if the owner of a game center presents a card with a preset number of electronic tickets to a customer, the owner can add the number of electronic tickets on the gifted card to the number of electronic tickets corresponding to the card already owned by the owner, and then subtract the number of electronic tickets on the gifted card. The number of electronic tickets to be transferred may be a predetermined number, or may be a number arbitrarily determined by input or the like.

[0131] 7 is a flowchart illustrating an example of the operation of transferring tickets. An example will be described in which the number of electronic tickets corresponding to the first card is transferred to the number of electronic tickets corresponding to the second card. The number of electronic tickets to be transferred can also be set to any value input from the exchange device operation panel 27. In such a case, for example, a process for inputting the number of electronic tickets to be transferred is inserted between steps S57 and S58, the number of electronic tickets to be transferred is included in the request output in step S60, and the calculation of the number of electronic tickets in step S66 is performed based on the number of electronic tickets to be transferred.

[0132] Steps S50 to S52, steps S56 to S60, steps S64 to S65, steps S68 to S70, and step S73 are processes of the ticket exchange device 5, and steps S53 to S55, steps S61 to S63, steps S66 to S67, and steps S71 to S72 are processes of the ticket management device 4. Various operations of the ticket exchange device 5 are controlled by the exchange device control circuit 24. Various operations of the ticket management device 4 are controlled by the management device control circuit 18.

[0133] In step S50, the ticket exchange device 5 uses the exchange device reader 28 to read the identification information from the first card that is the source of the electronic ticket.

[0134] Next, in step S51, the exchange device control circuit 24 analyzes the read data, extracts the identification information, acquires the extracted identification information, and uses it for control. The identification information is stored in the exchange device control circuit 24 as necessary.

[0135] Next, in step S52, the ticket exchange device 5 outputs a first information transfer request, to which the acquired identification information is added, to the ticket management device 4. In this example, the first information transfer request is a request to acquire information on the total number of tickets from the ticket management device 4 and to process the transfer of the electronic ticket. The first information transfer request includes the identification information and information indicating that it will be the source of the electronic ticket transfer.

[0136] In step S53, the ticket management device 4 receives the first information transfer request from the ticket exchange device 5. The management device control circuit 18 of the ticket management device 4 extracts the identification information and information indicating the source of the electronic ticket transfer, which are included in the received first information transfer request, and uses them for control.

[0137] Next, in step S54, the management device control circuit 18 extracts information on the total number of tickets corresponding to the acquired identification information from the information stored in the management device memory 19.

[0138] Next, in step S55, the ticket management device 4 outputs the extracted information on the total number of tickets as information on the first ticket number corresponding to the first identification information of the first card to the ticket exchange device 5. The ticket management device 4 waits for input to perform the next process.

[0139] Next, in step S56, the ticket exchange device 5 waits for a response from the ticket management device 4 to the first information transfer request, and acquires information on the first number of tickets sent from the ticket management device 4. The information on the first number of tickets is information on the total number of tickets corresponding to the first identification information of the first card.

[0140] Next, in step S57, the ticket exchange device 5 displays the information on the total number of tickets obtained from the ticket management device 4 on the exchange device operation panel 27. The user can confirm the number of electronic tickets corresponding to the first card. Furthermore, the exchange device control circuit 24 of the ticket exchange device 5 displays an input field on the exchange device operation panel 27 for the number of electronic tickets to be transferred, which the user can select, and allows the user to input the number. In this example, there is no input process for the number of electronic tickets to be transferred, and the electronic tickets are transferred using a value set by default. For example, the default value for the number of electronic tickets to be transferred is the total number of electronic tickets. The exchange device operation panel 27 displays the number of electronic tickets corresponding to the first card and the number of electronic tickets to be transferred.

[0141] Next, in step S58, the ticket exchange device 5 causes the exchange device reader 28 to read the identification information from the second card to which the number of electronic tickets is to be transferred.

[0142] Next, in step S59, the exchange device control circuit 24 analyzes the read data, extracts the identification information, acquires the extracted identification information, and uses it for control. If necessary, the identification information is stored in the exchange device control circuit 24.

[0143] Next, in step S60, the ticket exchange device 5 outputs a second information transfer request, to which the acquired identification information is added, to the ticket management device 4. In this example, the second information transfer request is a request to acquire information on the total number of tickets from the ticket management device 4 and to continue the process of transferring the electronic ticket. The second information transfer request includes the identification information and information indicating the destination of the electronic ticket.

[0144] In step S61, the ticket management device 4 receives a second information transfer request from the ticket exchange device 5. The management device control circuit 18 of the ticket management device 4 extracts the identification information and information indicating the destination of the electronic ticket from the received second information transfer request, and uses them for control.

[0145] Next, in step S62, the management device control circuit 18 extracts information on the total number of tickets of the acquired identification information from the information stored in the management device memory 19.

[0146] Next, in step S63, the ticket management device 4 outputs the extracted information on the total number of tickets as information on the second number of tickets corresponding to the second identification information of the second card to the ticket exchange device 5. Following the processing of step S63, the ticket management device 4 proceeds to and executes the processing of step S66.

[0147] Next, in step S64, the ticket exchange device 5 waits for a response from the ticket management device 4 to the second information transfer request, and acquires information on the second number of tickets sent from the ticket management device 4. The acquired information on the second number of tickets is information on the total number of tickets corresponding to the second identification information of the second card.

[0148] Next, in step S65, the ticket exchange device 5 displays the information on the total number of tickets obtained from the ticket management device 4 on the exchange device operation panel 27. The user can check the number of electronic tickets corresponding to the second card. After this process is completed, the ticket exchange device 5 waits for information to be output from the ticket management device 4.

[0149] In step S66, the ticket management device 4 temporarily stores a value obtained by adding the number of electronic tickets to be transferred to the second number of tickets, which is the total number of tickets corresponding to the second identification information. If no value is specified, the number of electronic tickets to be transferred is the total number of tickets corresponding to the first identification information. Furthermore, the ticket management device 4 temporarily stores a value obtained by subtracting the number of electronic tickets to be transferred from the first number of tickets, which is the total number of tickets corresponding to the first identification information. If no value is specified, the number of electronic tickets to be transferred is the total number of tickets corresponding to the first identification information.

[0150] Next, in step S67, the ticket management device 4 adds identification information to the calculated first ticket number and second ticket number, and outputs them to the ticket exchange device 5. Then, the ticket management device 4 waits for information input from the ticket exchange device 5.

[0151] Next, in step S68, the first number of tickets and the second number of tickets to be updated are input to the ticket exchange device 5. The ticket exchange device 5 then displays the input first number of tickets and the second number of tickets on the exchange device operation panel 27. Preferably, the first number of tickets and the second number of tickets before the transfer are also displayed on the exchange device operation panel 27 together with the values ​​after the transfer, so that they can be compared. At least the number of electronic tickets held after the transfer corresponding to the first card at the source of the transfer and the second card at the destination of the transfer are displayed.

[0152] Next, in step S69, the ticket exchange device 5 prompts the user to confirm the number of electronic tickets held after the transfer corresponding to each of the first card as the transfer source and the second card as the transfer destination, which are displayed on the exchange device operation panel 27, and prompts the user to input the result as to whether or not to permit the transfer of the electronic tickets. The user inputs whether or not to permit the transfer of the electronic tickets from the exchange device operation panel 27, and the result is acquired by the exchange device control circuit 24 and used for control.

[0153] Next, in step S70, the ticket exchange device 5 outputs information from the ticket exchange device 5 to the ticket management device 4 as to whether or not the ticket can be moved.

[0154] The process moves to the ticket management device 4.

[0155] In step S71, the ticket management device 4 receives information output from the ticket exchange device 5 indicating whether or not the electronic ticket can be transferred. If the transfer of the electronic ticket is denied, the ticket management device 4 does not transfer the electronic ticket, and does not rewrite the data in the management device memory 19. If the transfer of the electronic ticket is affirmative, the ticket management device 4 transfers the electronic ticket. In step S66, the ticket management device 4 writes the result of the calculation to the database in the management device memory 19. The ticket management device 4 updates the second number of tickets, which is the total number of tickets corresponding to the second identification information, to the result of the calculation in step S66. The update date and time of the total number of tickets is also updated to the date and time when the addition was made. Furthermore, with regard to the acquisition information, the number of acquired tickets is set to the number of electronic tickets to which the addition was made, the acquisition date and time is set to the update date and time, and a history is added and stored as information indicating that the acquisition reason was a transfer from the first identification information. Furthermore, the ticket management device 4 updates the first number of tickets, which is the total number of tickets corresponding to the first identification information, to the result of the calculation in step S66. The update date and time of the total number of tickets is also updated to the date and time when the subtraction was made. In addition, the usage information is stored as the number of electronic tickets subtracted from the number of tickets used, the usage date and time is the update date and time, and the reason for use is stored as a history indicating that the ticket was moved to the second identification information.

[0156] Next, in step S72, if the transfer of the electronic ticket is denied, the ticket management device 4 outputs information indicating that the electronic ticket will not be transferred to the ticket exchange device 5 as a ticket transferred notice. If the transfer of the electronic ticket is affirmative, the ticket management device 4 outputs information indicating that the electronic ticket has been transferred to the ticket exchange device 5 as a ticket transferred notice. The ticket transferred notice includes information on the total number of tickets after updating both the first identification information and the second identification information.

[0157] Next, the process moves to the ticket exchange device 5.

[0158] In step S73, the ticket exchange device 5 receives the ticket transfer notification output from the ticket management device 4 and performs processing in accordance with the notification. When the ticket exchange device 5 receives information indicating that the electronic ticket will not be transferred as the ticket transfer notification, it displays on the exchange device operation panel 27 the total number of tickets corresponding to the first identification information of the first card, the total number of tickets corresponding to the second identification information of the second card, and information indicating that the electronic ticket has not been transferred. When the ticket exchange device 5 receives information indicating that the electronic ticket has been transferred as the ticket transfer notification, it displays on the exchange device operation panel 27 the updated total number of tickets corresponding to the first identification information of the first card, the updated total number of tickets corresponding to the second identification information of the second card, and information indicating that the electronic ticket has been transferred. The user can check the number of electronic tickets held corresponding to each updated card.

[0159] For example, electronic tickets corresponding to couples on multiple cards can be combined onto one card. Furthermore, the history of transfers is recorded in the ticket management device 4. In step S72, the ticket transfer notification can include history information, which can be displayed on the exchange device operation panel 27 of the ticket exchange device 5. The ticket exchange device 5 can not only exchange electronic tickets for benefits, but also transfer electronic tickets corresponding to the identification information of couples with different identification information from one to another.

[0160] According to this aspect, it is possible to provide a ticket terminal device and a ticket management system that can prevent tickets from being issued due to a lack of tickets and reduce the maintenance burden of service devices such as game devices, such as managing the remaining amount of tickets. It is also possible to prevent users from losing their tickets. According to this aspect, even in a service device that starts operating in response to a deposit of cash or the like, by outputting the identification information acquired by the ticket terminal device and the number of electronic tickets based on the ticket signal generated by the ticket terminal device to a ticket management device and having the ticket management device manage them, it is possible to provide a ticket terminal device and a ticket management system that can prevent tickets from being issued due to a lack of tickets and reduce the maintenance burden of service devices such as game devices, such as managing the remaining amount of tickets. [Explanation of symbols]

[0161] 1. Ticket Management System 2. Game devices 3 Ticket terminals 4 Ticket Management Device 5 Ticket exchange device 6 User terminals

Claims

1. A ticket terminal device connected to a service device that starts operating in response to input of a charging signal output from a fee accepting device, an input means for inputting ticket signals that are output at predetermined output timings based on predetermined conditions by the service device that has started operating in response to the charging signal, and that are generated corresponding to a predetermined number of electronic tickets; an identification information acquisition means for acquiring identification information that identifies a user who uses the service device; a ticket generation means for analyzing the ticket signal input to the input means, calculating the number of the electronic tickets, and generating ticket information including the number of the electronic tickets obtained as a result of the calculation and the identification information; a communication means connected to a ticket management device capable of data communication, the ticket management device storing the number of electronic tickets held for each of the identification information in association with each other; If the identification information is acquired after the previous ticket information is generated and before the ticket signal is input, the ticket generation means generates the ticket information including the number of electronic tickets calculated based on the input ticket signal and the last acquired identification information, if the identification information is not acquired before the input of the ticket signal and if the identification information is not acquired within a first predetermined time period from the input of the ticket signal, the ticket information is not generated by the ticket generation means, If the identification information has not been acquired before the input of the ticket signal and the identification information is acquired during the first predetermined time period from the input of the ticket signal, the ticket generation means generates the ticket information including the number of electronic tickets calculated based on the input ticket signal and the identification information that was first acquired during the first predetermined time period; A ticket terminal device, characterized in that the ticket information generated by the ticket generation means is output from the communication means to the ticket management device.

2. a display means for displaying the number of the electronic tickets included in the ticket information; 2. The ticket terminal device according to claim 1, wherein the number of the electronic tickets included in the ticket information generated by the ticket generating means is displayed on the display means.

3. inputting the number of the electronic tickets stored in association with the identification information from the ticket management device via the communication means; 3. The ticket terminal device according to claim 2, wherein the display means displays the number of the input electronic tickets.

4. A ticket terminal device described in any one of claims 1 to 3, characterized in that the identification information acquisition means has an image input means and an image analysis means, and the image input means acquires image data from a medium on which the identification information is recorded based on predetermined rules, and analyzes the image data acquired by the image analysis means to extract the identification information.

5. A ticket management system comprising a service device, a ticket terminal device, and a ticket management device, The service device an operation is started in response to an input of a charging signal from a fee receiving device which outputs a charging signal in response to the collection of a fee, and after the start of the operation, a ticket signal is output at a predetermined output timing based on a predetermined condition, and is generated corresponding to a predetermined number of electronic tickets; The ticket terminal device a first input means for inputting the ticket signal output from the service device in order to issue the electronic ticket; a first identification information acquisition means for acquiring identification information for identifying a user who uses the service device; a ticket generation means for analyzing the ticket signal input to the first input means, calculating the number of electronic tickets, and generating ticket information including the number of electronic tickets obtained as a result of the calculation and the identification information; a first communication means connected to an external device so as to be able to perform data communication; The ticket management device a second communication means connected to an external device so as to be able to perform data communication; a memory; and a control means for controlling the second communication means and the memory; The ticket terminal device If the identification information is acquired after the previous ticket information is generated and before the ticket signal is input, the ticket generation means generates the ticket information including the number of electronic tickets calculated based on the input ticket signal and the last acquired identification information, If the identification information is not acquired before the input of the ticket signal and if the identification information is not acquired within a first predetermined time period from the input of the ticket signal, the ticket information is generated by the ticket generation means; If the identification information has not been acquired before the input of the ticket signal and the identification information is acquired during the first predetermined time period from the input of the ticket signal, the ticket generation means generates the ticket information including the number of electronic tickets calculated based on the input ticket signal and the identification information that was first acquired during the first predetermined time period; outputting the ticket information generated by the ticket generation means from the first communication means to the ticket management device; the memory stores the number of the electronic tickets held for each of the identification information in association with each other; A ticket management system characterized in that the ticket management device receives the ticket information from the first communication means via the second communication means, and updates the number of electronic tickets stored in association with the identification information stored in the memory based on the identification information and the number of electronic tickets contained in the ticket information obtained from the ticket terminal device under the control of the control means.

6. The ticket management system according to claim 5, characterized in that the service device has a service providing means for providing a service and a service device control means for controlling the service providing means in response to input of the charging signal from the fee receiving device, and the service device control means outputs the ticket signal in response to completion of the service of the service providing means.

7. a ticket exchange device including: an issuing means for exchanging a benefit for a predetermined number of the electronic tickets and issuing the benefit; a third communication means connected to an external device so as to be able to perform data communication; and a second identification information acquiring means for acquiring the identification information that identifies the user who uses the issuing means; the ticket exchange device transmits the identification information acquired by the second identification information acquisition means to the ticket management device from the third communication means; the ticket management device performs a calculation to subtract the number of the electronic tickets to be exchanged for the benefit from the number of the electronic tickets stored in association with the identification information received by the second communication means from the third communication means, and transmits the result of the subtraction from the second communication means to the ticket exchange device; 6. The ticket management system according to claim 5, wherein the ticket exchange device receives the result from the second communication means by the third communication means, and issues the benefit from the issuing means.

8. the ticket exchange device acquires first identification information identifying a first user and second identification information identifying a second user by the second identification information acquisition means, and outputs the first identification information and the second identification information to the ticket management device; The ticket management system described in claim 7, characterized in that the ticket management device adds a pre-specified number of electronic tickets to the number of electronic tickets stored in association with the first identification information, and subtracts the pre-specified number of electronic tickets from the number of electronic tickets stored in association with the second identification information.

9. the ticket exchange device has a second input means; 9. The ticket management system according to claim 8, wherein the predetermined number of electronic tickets is input by the second input means.

Images