JP6338612B2 - Ticket system and ticket system control method - Google Patents

Description

  The present invention relates to a ticket system that manages ticket information, and more particularly to a ticket system that can restore a ticket that has already been issued to a state prior to ticketing, and a ticket system control method.

  After purchasing tickets for events such as sports matches and concerts at the ticket sales server, using ticket exchange information notified after purchase, use a ticket issuing terminal installed in a store such as a convenience store. A system for issuing a media ticket is known.

  In general, the ticket issued has not been changed in any way. However, in the following Patent Document 1, it is possible to refund the issued ticket using a personal computer and a printer at the user's home. A system is disclosed.

JP 2002-329028 A

  For example, when a ticket purchaser cannot go to an event due to an emergency or the like, there may be a situation in which the ticket cannot be transferred because there is no time delay for delivering the ticket even if the ticket issued is transferred to another person.

  On the other hand, if the ticket is in a state before the ticket issuance, the ticket can be easily transferred by notifying the transferee of the ticket exchange information.

  However, in the above-described conventional technology, the invalidated ticket is refunded and cannot be issued again. That is, with the above-described conventional technology, a ticket once issued cannot be returned to the state before the ticket is issued. Further, in the above-described prior art, invalidated tickets are not collected, so there is a possibility that tickets for a plurality of paper media issued based on the same ticket information will be available.

  The present invention has been made in view of the above problems, and an object of the present invention is to provide a ticket system and a ticket system control method capable of returning a ticket that has already been issued to a state in which the ticket can be issued again. is there.

According to the ticket system of the present invention, the subject is a ticket system comprising: a ticket management device that manages ticket information; and a ticket verification device that is communicably connected to the ticket management device, The ticket management device associates and stores whether each settled ticket is issued or not issued, and designation of a ticket to be restored from the issued tickets to an unissued state Receiving means, and first transmission means for sending a list of unique information of the tickets accepted by the accepting means to the ticket matching device , wherein the ticket matching device obtains the unique information of the issued ticket an acquisition unit that, specific information includes acquired by the acquisition unit in the list transmitted by the first transmission means When a guide means for guiding the recovery of the ticketing already ticket, and a second transmission means for transmitting the information ticketing already tickets recovered in accordance with the guidance by the guide means to the ticket management apparatus, a The ticket management apparatus further includes an updating unit that updates information stored in the storage unit in association with the ticket information transmitted by the second transmission unit , so that the ticket is in an unissued state. It is more resolved to Rukoto.
In addition, according to the ticket system of the present invention, the subject is a ticket system including a ticket management device that manages ticket information, and a ticket verification device that is communicably connected to the ticket management device. The ticket management device stores storage means for associating and storing whether each settled ticket is issued or not issued, and a ticket that is restored from the issued tickets to an unissued state. Receiving means for accepting designation of the ticket, wherein the ticket collating device acquires the unique information of the ticket that has been issued, and means for transmitting the unique information of the ticket acquired by the acquiring means to the ticket management device The ticket management apparatus includes the acquisition unit in the unique information of the ticket received by the reception unit. Further comprising means for transmitting a verification result indicating whether or not the acquired unique information is included to the ticket verification apparatus, wherein the ticket verification apparatus uses the verification result of the unique information of the ticket received by the reception means. A guide means for guiding the collection of the issued ticket when the specific information obtained by the obtaining means is included, and the ticket issued ticket collected according to the guidance by the guidance means. Transmitting means for transmitting information to the ticket management apparatus, wherein the ticket management apparatus stores information stored in the storage means in association with the ticket information transmitted by the transmission means. The problem is solved by further comprising an updating means for updating that the ticket is issued.

In addition, according to the ticket system control method of the present invention, a ticket system includes a ticket management device that manages ticket information, and a ticket verification device that is communicably connected to the ticket management device. The ticket management device stores in the storage means whether each settled ticket is in a ticketed state or in an unissued state, and stores the ticket in the ticketed state. Receiving a designation of a ticket to be restored to an unissued ticket state, and a first transmission step of transmitting a list of unique information of the ticket received in the receiving step to the ticket verification device, wherein the ticket verification device includes: an acquisition step of acquiring unique information ticketing already tickets, list transmitted by the first transmission step When the specific information acquired in the acquisition step in is included, a guide step of guiding the collection of the ticket already tickets, the information of the ticket already tickets recovered in accordance with the guidance in the guide step A second transmission step for transmitting to the ticket management device, wherein the ticket management device stores information stored in the storage means in association with the ticket information transmitted in the second transmission step. an update step of updating that is not yet issuing state is further more resolved the free Mukoto.
According to the ticket system control method of the present invention, there is provided a ticket system control method comprising: a ticket management device that manages ticket information; and a ticket verification device that is communicably connected to the ticket management device. The ticket management device stores in the storage means whether each of the settled tickets is in a ticketed state or in an unissued state, and an unissued state from among the tickets in the issued state Receiving the designation of the ticket to be restored to, the ticket verification device acquiring the unique information of the ticket that has been issued, and the ticket management device for acquiring the unique information of the ticket acquired in the acquisition step The ticket received by the ticket management device in the receiving step. The method further includes a step of transmitting a verification result indicating whether or not the unique information acquired in the acquisition step is included in the specific information to the ticket verification device, wherein the verification result is the reception step. In response to the guidance in the guidance step and the guidance step for guiding the collection of the issued ticket, in the case where it is shown that the unique information obtained in the obtaining step is included in the unique information of the ticket received in And a transmitting step of transmitting the collected ticket information to the ticket management device, wherein the ticket management device stores the information in the storage unit in association with the ticket information transmitted in the transmission step. This is solved by further including an update step of updating the information to be made that the ticket is in an unissued state.

  According to the above-described ticket system and ticket system control method, it is possible to return a designated ticket from tickets that have been issued once to an unissued state, that is, a state in which a ticket can be issued again. According to the above ticket system, since the issued tickets are collected, a plurality of tickets having the same contents are not issued. That is, according to the above ticket system, it is possible to return a ticket that has been issued to an unissued state while avoiding the duplicate issue of the same ticket.

In the above ticket system, the ticket management device includes a first transmission unit that transmits a list of unique information of the ticket received by the reception unit to the ticket verification device, and the guide unit includes the first transmission unit. When the transmitted information includes the unique information acquired by the acquisition unit, the ticket verification device guides collection of the issued ticket, and the ticket verification device collects the ticket according to the guidance by the guidance unit. A second transmission unit configured to transmit information on the issued ticket to the ticket management device, wherein the update unit stores information stored in the storage unit in association with the ticket transmitted by the second transmission unit; It may be updated that the ticket is in an unissued state.
By doing so, since it is possible to execute verification as to whether or not the ticket is an unissued ticket in the ticket verification device, it is possible to distribute the load of ticket verification processing.

In the above ticket system, the acquisition unit may scan and acquire the unique information printed on the issued ticket.
By doing so, it is possible to ensure the identity between the ticket to be issued and the designated ticket. In other words, the above configuration can prevent an incorrect ticket from being issued.

In the above ticket system, the unique information may be information including a ticket issue number of the issued ticket.
By doing so, the ticket issue number uniquely given to each ticket issued can be used as the unique information of each ticket.

In the above ticket system, the accepting unit may accept specific information of the ticket together with designation of the ticket to be restored to the unissued state.
In this way, unique information can be registered in advance for a ticket to be returned to an unissued state.
In addition, when registering a ticket to be returned to an unissued state, unique information on the ticket after it is issued is necessary, so that it is possible to prevent a ticket that is not on the user's hand from being erroneously registered as an unissued target.

In the above ticket system, the guidance unit stops the process of unissuing the issued ticket when the acquired unique information is not included in the ticket specific information received by the receiving unit. It is good to guide as you do.
By doing so, it is possible to prevent a ticket that has not been issued from being issued from being issued.

  According to the ticket system and the control method of the ticket system of the present invention, it is possible to return a designated ticket from tickets that have been issued once to an unissued state, that is, a state in which a ticket can be issued again.

It is a figure explaining the outline | summary of the non-ticket issuing process by the ticket system which concerns on this embodiment. It is a figure which shows an example of a ticket issued ticket. It is a figure which shows the system configuration | structure of a ticket system. It is a figure explaining the function with which a ticket system is equipped. It is a figure which shows an example of a ticket information management table. It is a figure which shows an example of an unissued list table. It is a figure which shows an example of the collect | recovered ticket list table. It is a sequence diagram regarding the registration process of an unissued ticket. It is a sequence diagram regarding distribution of an unissued list table. It is a sequence diagram regarding the collection | recovery process accompanying ticket non-issuance. It is a figure which shows an example of a purchase history list screen. It is a figure which shows an example of a ticket detail display screen. It is a figure which shows an example of an unissued application screen. It is a figure which shows an example of the purchase history list screen after non-ticketing application. It is a figure which shows an example of a non-ticketing procedure start screen. It is a figure which shows an example of a collection guide screen. It is a figure which shows an example of a reception completion screen. It is a figure which shows an example of an error screen. It is a figure which shows an example of the purchase history list screen after completion of non-ticketing.

Hereinafter, one embodiment (this embodiment) of the present invention will be described with reference to the drawings.
In addition, embodiment described below is for making an understanding of this invention easy, and does not limit this invention. That is, the present invention can be changed and improved without departing from the gist thereof, and the present invention includes the equivalents thereof.
In particular, the design and layout of the screen described in the following description and drawings are merely examples, and can be appropriately changed according to the application of the present invention, the user's request, and the like.

[1. Overview of processing in ticket system 1 according to the present embodiment]
First, based on FIG.1 and FIG.2, the outline | summary of the process in the ticket system 1 which concerns on this embodiment is demonstrated. The ticket system 1 is a computer system including a ticket management server 10 (corresponding to a ticket management device), a user terminal 20, and a ticket verification device 30.

  The ticket management server 10 is a server computer managed by a ticket issuer, and controls processing such as ticket sales, issuance, and ticket information provision. The user terminal 20 is a computer such as a smartphone, a personal computer, or a mobile phone operated by the user U. The ticket verification device 30 is a computer for verifying whether or not the issued ticket T is a ticket registered in advance as a target of the non-ticketing process in the ticket non-ticketing process described later. In addition, said ticket means the intangible thing or tangible thing with which the content of the right to appreciate and watch entertainment (entertainment, sports, etc.) was defined.

  First, as a premise of the present embodiment, an outline of ticket issuing processing in the ticket system 1 will be described.

  The user U accesses the ticket management server 10 using the user terminal 20 and purchases a desired ticket.

  In the ticket management server 10, when the ticket is purchased, the ticket management server 10 stores the fact that the ticket has not yet been issued and indicates that the ticket has not been issued. Notify the exchange number.

  The user U issues a purchased ticket by inputting the exchange number notified from the ticket management server 10 to a predetermined ticket issuing terminal. When the ticket issuance is completed, the ticket management server 10 updates the state of the ticket stored for the ticket purchased by the user U to the issued state indicating that the ticket has been issued.

  Here, FIG. 2 shows an example of the issued ticket T. The issued ticket T is, for example, a paper ticket, and various information related to the ticket is printed on the surface. In the example shown in FIG. 2, the issued ticket T has a barcode print area T1, a ticket issue number print area T2, a ticket issue date print area T3, and a purchaser print area T4.

  The barcode printing area T1 is an area where a barcode in which information (unique information) unique to the ticket is encoded is printed. The unique information is different for each ticket, and may be information including the ticketing number of the ticket T that has been issued (for example, ticketing number, ticketing date, purchaser name information, etc.).

  The issuance number printing area T2 is an area where the issuance number of the issued ticket T is printed. Further, the ticket issue date printing area T3 is an area in which the ticket issue date of the issued ticket T is printed. The purchaser print area T4 is an area where the purchaser name of the ticket T already issued is printed.

  Then, in the ticket system 1 according to the present embodiment, it is possible to return the ticket issued ticket T once issued to the state before the ticket issuance (unissued process) by the procedure described below. Hereinafter, the outline of the procedure of the non-ticketing process will be described with reference to FIG.

  (1) The user U accesses the ticket management server 10 through the user terminal 20 and registers information (unique information) on the ticket-issued ticket T requesting non-ticketing in the ticket management server 10.

  (2) The ticket management server 10 transmits a list of tickets that have been requested to be issued (unissued list) to the ticket verification device 30 installed in the store S at a predetermined timing (for example, midnight). The unissued list includes a list of ticket specific information.

  (3) The user U takes the issued ticket T to the store S where the ticket verification device 30 is installed. The ticket collation device 30 is a computer that collates the information on the issued ticket T with the information on the unissued list.

  (4) The ticket verification device 30 scans the barcode printing area T1 of the ticket T issued from the user U and reads the unique information encoded in the barcode. Further, the ticket verification device 30 verifies whether or not the read unique information exists in the unissued list. As a result of the collation, if the read unique information exists in the unissued list, the store S collects a predetermined fee from the user U and collects the issued ticket T.

  (5) The ticket verification device 30 transmits a list of the collected ticket issued tickets T to the ticket management server 10 at a predetermined timing (for example, midnight). The collected ticket T issued itself is also sent from the store S to a predetermined destination (ticket issuer).

  (6) The ticket management server 10 updates the state of the collected ticket from the issued state to the unissued state based on the collected ticket list transmitted from the ticket verification device 30.

  With the above processing, the ticket system 1 can recover the state of the ticket once issued from the issued state to the unissued state. In this way, unlike the case where the ticket is returned or canceled, the ticket can be returned from the issued state to the unissued state while maintaining the state where the user has purchased the ticket. Hereinafter, a configuration provided in the ticket system 1 for realizing the above-described processing will be described.

[2. Description of hardware configuration of ticket system 1]
FIG. 3 shows an example of the system configuration of the ticket system 1. As shown in FIG. 3, the ticket system 1 includes a ticket management server 10, a user terminal 20, and a ticket verification device 30, and the ticket management server 10 and the user terminal 20, the ticket management server 10 and the ticket verification device 30 are each a network. 2 is communicably connected via the terminal 2. In the present embodiment, the ticket system 1 is described as including the user terminal 20 operated by the user U. However, the user terminal 20 may not be included in the ticket system 1. In FIG. 1, one ticket verification device 30 is shown, but a plurality of ticket verification devices 30 may be provided.

[2.1. Hardware configuration of ticket management server 10]
As shown in FIG. 3, the ticket management server 10 is a computer including a control unit 10A, a storage unit 10B, and a communication unit 10C.

  The control unit 10A includes, for example, a central processing unit, and executes various arithmetic processes based on programs and data stored in the storage unit 10B and controls each unit of the ticket management server 10. .

  The storage unit 10B includes, for example, a memory and a magnetic disk device, and stores various programs and data, and also functions as a work memory for the control unit 10A. The storage unit 10B may include an information storage medium such as a flash memory or an optical disk.

  The communication unit 10 </ b> C connects to the network 2 and communicates with devices such as the user terminal 20 and the ticket matching device 30 connected to the network 2.

[2.2. Hardware configuration of user terminal 20]
As shown in FIG. 3, the user terminal 20 is a computer including a control unit 20A, a storage unit 20B, a communication unit 20C, an input unit 20D, and a display unit 20E.

  The control unit 20A includes, for example, a central processing unit, and executes various arithmetic processes based on programs and data stored in the storage unit 20B, and controls each unit of the user terminal 20.

  The storage unit 20B includes, for example, a memory and a magnetic disk device, and stores various programs and data, and also functions as a work memory for the control unit 20A. The storage unit 20B may include an information storage medium such as a flash memory or an optical disk.

  The communication unit 20C is connected to the network 2 and communicates with a device such as the ticket management server 10 connected to the network 2.

  The input unit 20D includes an input device such as a touch panel, a keyboard, and a mouse, for example, and accepts input of user operation information.

  The display unit 20E includes a display device such as a liquid crystal display device, and displays a screen based on graphic data generated by the control unit 20A.

  Note that the input unit 20 </ b> D and the display unit 20 </ b> E may not be built in the user terminal 20, and may be provided as an external device connected to the user terminal 20.

[2.3. Hardware configuration of ticket verification apparatus 30]
As shown in FIG. 3, the ticket verification device 30 is a computer including a control unit 30A, a storage unit 30B, a communication unit 30C, an information reading unit 30D, an input unit 30E, and a display unit 30F.

  The control unit 30A includes, for example, a central processing unit (Central Processing Unit), executes various arithmetic processes based on programs and data stored in the storage unit 30B, and controls each unit of the ticket verification device 30. .

  The storage unit 30B includes, for example, a memory and a magnetic disk device, and stores various programs and data, and also functions as a work memory for the control unit 30A. The storage unit 30B may include an information storage medium such as a flash memory or an optical disk.

  The communication unit 30C is connected to the network 2 and communicates with a device such as the ticket management server 10 connected to the network 2.

  The information reading unit 30D includes, for example, a bar code reader, a scanner, and the like, and is a device that reads information printed on a ticket. If the ticket is an electronic ticket, the information reading unit 30D may be a reader device that reads information on the electronic ticket by wireless communication.

  The input unit 30E includes input devices such as a touch panel, a keyboard, and a mouse, for example, and receives input of user operation information.

  The display unit 30F includes a display device such as a liquid crystal display device, for example, and displays a screen based on graphic data generated by the control unit 30A.

  Note that the information reading unit 30 </ b> D, the input unit 30 </ b> E, and the display unit 30 </ b> F may not be built in the ticket verification device 30, and may be provided as an external device connected to the ticket verification device 30.

[3. Description of functions provided in ticket system 1]
Next, an example of functions provided in the ticket system 1 will be described based on FIG.

  As shown in FIG. 4, the ticket management server 10 functions as a data storage unit 11, a non-ticketed designation receiving unit 12, a non-ticketed list transmitting unit 13, a collected ticket list receiving unit 14, and a ticket information updating unit 15. Is provided. The functions of the respective units provided in the ticket management server 10 are realized by causing the control unit 10A of the ticket management server 10 to operate the respective units of the ticket management server 10 based on a program stored in the storage unit 10B. Is. Note that the ticket management server 10 may read the above program from an information storage medium, or may download it via the network 2 by the communication unit 10C.

  As shown in FIG. 4, the user terminal 20 includes a non-ticketed designation unit 21 as a function. The functions of the respective units provided in the user terminal 20 are realized by causing the control unit 20A of the user terminal 20 to operate the units of the user terminal 20 based on a program stored in the storage unit 20B. . Note that the user terminal 20 may read the above program from an information storage medium, or may download the program via the network 2 by the communication unit 20C.

  As shown in FIG. 4, the ticket collation apparatus 30 functions as a data storage unit 31, an unissued list reception unit 32, a ticketed ticket information acquisition unit 33, a collation unit 34, a guide unit 35, a collection processing unit 36, A collected ticket list transmission unit 37 is provided. The functions of the above-described units included in the ticket verification device 30 are realized by causing the control unit 30A of the ticket verification device 30 to operate the units of the ticket verification device 30 based on a program stored in the storage unit 30B. Is. Note that the ticket verification device 30 may read the above program from an information storage medium, or may download the program via the network 2 by the communication unit 30C.

  Hereinafter, details of the functions of the above-described units included in the ticket system 1 will be described. First, functions for realizing the processes (1) and (2) in FIG. 1 will be described.

[3.1. Data storage unit 11]
The data storage unit 11 is realized mainly by the storage unit 10B of the ticket management server 10, and stores various types of information related to tickets to be managed. For example, in the present embodiment, the data storage unit 11 stores a ticket information management table 11A and a non-ticketed list table 11B. Details of each of the above tables will be described below.

  The ticket information management table 11A is a table for managing information on tickets sold by ticket issuers. In the present embodiment, in the ticket information management table 11A, the ticket status (ticket status) is stored in association with each ticket. For example, the above ticket states include a state where the ticket has been settled and has not been issued (state “0”), and a state where the ticket has been settled and has been issued (state “1”). That's good.

  FIG. 5 shows an example of the ticket information management table 11A. As shown in FIG. 5, the ticket information management table 11 </ b> A according to the present embodiment includes a ticket ID for identifying a ticket, a performance ID for identifying a performance related to the ticket, seat information regarding the ticket, and a purchaser who has purchased the ticket. The purchaser ID for identifying the ticket, the exchange number used when the ticket is issued, and the ticket status are stored in association with each other.

  The unissued ticket list table 11 </ b> B is a table that stores information on tickets that have been designated as non-issued by the user among issued tickets (issued tickets). Specifically, the non-issued ticket list table 11B is a list of issued tickets that have been designated as non-issued by the user among the tickets whose ticket status is already issued (status “1”) in the ticket information management table 11A. It is a table for storing unique information. The unique information of the issued ticket is information unique to each issued ticket, for example, the issued number assigned to the issued ticket. Further, in addition to the ticket issue number, the unique information may include ticket issue date and purchaser name information. The designation of non-ticketing is accepted by the non-ticketing designation receiving unit 12 described later.

  FIG. 6 shows an example of the unissued ticket list table 11B. As shown in FIG. 6, in the unissued list table 11B according to the present embodiment, a ticket ID for identifying a ticket designated to be issued, a ticket issue number, a ticket issue date, and a purchaser name are associated. Remembered.

[3.2. Unissued ticket designation unit 21, unissued ticket designation reception unit 12]
The non-ticketed designation unit 21 is realized mainly by the control unit 20A, the storage unit 20B, the communication unit 20C, the input unit 20D, and the display unit 20E of the user terminal 20, and the ticket is not issued from the ticket that has been issued. Specify the ticket to be restored. For example, the non-ticketed designating unit 21 is a ticket associated with identification information of a user who operates the user terminal 20 in the ticket information management table 11A, and the ticket status has been issued (status “1”). Among these, the ticket management server 10 is notified of information on a ticket designated as a non-ticketed target by the user (non-ticketed ticket). At this time, the non-ticketing designation unit 21 accepts input of unique information (for example, a ticketing number, a ticketing date, a purchaser name) of a ticket to be ticketed that has been input by the user via the input unit 20D, and receives the above notification. It is good also as transmitting to the ticket management server 10 including the specific information of an unissued ticket.

  The unique information is used for verification processing when confirming whether or not the issued ticket is an unissued ticket when the issued ticket is collected at the store S.

  The non-ticketed designation receiving unit 12 is realized mainly by the control unit 10A, the storage unit 10B, and the communication unit 10C of the ticket management server 10, and designates a ticket to be restored from a ticket that has been issued to an unissued state. Accept. Specifically, the non-ticketed designation receiving unit 12 receives the designation of information on the non-ticketed target ticket from the non-ticketed designation unit 21. More specifically, the non-ticketed designation receiving unit 12 receives identification information of a ticket that has been ticketed and identification of specific information that is used when matching a ticket that has been issued.

  Then, the non-ticketed designation receiving unit 12 registers the information of the ticket designated as non-ticketed in the non-ticketed list table 11B. Specifically, the non-ticketed designation receiving unit 12 adds a new record to the non-ticketed list table 11 </ b> B, and the identification information of the ticket that has been ticketed and the ticket that has been ticketed are added to the added record. The unique information used at the time of collation is stored in association with each other.

[3.3. Unticketed list transmission unit 13 and unissued list reception unit 32]
The non-ticketed list transmission unit 13 is realized mainly by the control unit 10A, the storage unit 10B, and the communication unit 10C of the ticket management server 10, and the unissued ticket designation received by the non-ticketed designation reception unit 12 is designated. A list of unique information is transmitted to the ticket verification device 30. Specifically, the non-ticketed list transmission unit 13 transmits the non-ticketed list table 11 </ b> B stored in the data storage unit 11 to the ticket verification device 30. Note that the non-ticketed list transmission unit 13 may transmit the latest non-ticketed list table 11 </ b> B to the ticket verification device 30 every time a predetermined timing arrives. Here, the predetermined timing may be a timing when the unissued list table 11B is updated, a predetermined time (for example, 2:00 am), a predetermined time interval (for example, every 12 hours), It is good also as the timing etc. which received the transmission request.

  The non-ticketed list receiving unit 32 is realized mainly by the control unit 30A, the storage unit 30B, and the communication unit 30C of the ticket verification device 30, and is designated by the non-ticketed list transmitting unit 13 and designated for non-ticketing. Receive a list of unique information. Specifically, the non-ticketed list receiving unit 32 receives the non-ticketed list table 11 </ b> B transmitted by the non-ticketed list transmitting unit 13.

  Then, the non-ticketed list receiving unit 32 stores in the data storage unit 31 a list of unique information of tickets for which non-ticketed is designated. Specifically, the non-ticketed list receiving unit 32 stores the received non-ticketed list table 11B in the data storage unit 31 as the non-ticketed list table 31A.

[3.4. Data storage unit 31]
The data storage unit 31 is mainly realized by the storage unit 30B of the ticket verification device 30, and stores various types of information regarding tickets that have not been issued. For example, in the present embodiment, the data storage unit 31 stores an unissued ticket list table 31A and a collected ticket list table 31B. Since the unissued list table 31A is the same information as the unissued list table 11B, the description of the unissued list table 31A is omitted. Details of the collected ticket list table 31B will be described later.

  The above corresponds to the function for realizing the processes (1) and (2) in FIG. Next, a function for realizing the processing after (4) after the user U has issued the ticket T issued ticket T to the store S in FIG. 1 (that is, after (3)) will be described.

[3.5. Issued ticket information acquisition unit 33]
The issued ticket information acquisition unit 33 is realized mainly by the control unit 30A, the storage unit 30B, and the information reading unit 30D of the ticket verification device 30. Then, the ticket-issued ticket information acquisition unit 33 acquires unique information of the ticket-issued ticket T presented as an unissued ticket from the user U.

  Specifically, the issued ticket information acquisition unit 33 scans the barcode printing area T1 of the issued ticket T by the information reading unit 30D, and the unique information encoded in the barcode (for example, the issue number, the issue date, Purchaser name) may be obtained. Further, for example, by issuing the OCR process while scanning the ticket issue number printing area T2, the ticket issue date printing area T3, and the purchaser printing area T4, information on the ticket issue number, the issue date, and the purchaser name printed in each area It is good also as acquiring.

[3.6. Verification unit 34]
The collation unit 34 is realized mainly by the control unit 30A and the storage unit 30B of the ticket collation device 30. The collating unit 34 collates the unique information of the ticket included in the non-ticketed list received by the non-ticketed list receiving unit 32 with the unique information acquired by the ticketed ticket information acquisition unit 33. And the collation part 34 determines whether the specific information acquired by the ticket-issued ticket information acquisition part 33 is contained in the non-ticketed list.

  Specifically, the collation unit 34 includes the unique information (ticketing number, ticketing date, purchaser name) of the ticket issued ticket T acquired by the ticketed ticket information acquiring unit 33, and each record of the unissued list table 31A. Is compared with the unique information stored in the table, and it is determined whether or not there is a record corresponding to the issued ticket T. Note that the record corresponding to the issued ticket T is a record in which the same information as the unique information acquired from the issued ticket T is stored.

[3.7. Guide part 35]
The guide unit 35 is mainly realized by the control unit 30A, the storage unit 30B, and the display unit 30F of the ticket verification device 30. The guide unit 35 executes an unissued ticket collection (execution of collection) or an unissued ticket to an operator (for example, a clerk of the store S) of the ticket collation device 30 according to a collation result by the collation unit 34. Guidance on stoppage (stopping recovery)

  For example, as a result of the collation by the collation unit 34, when the unique information of the ticket issued ticket T is included in the unissued list, the guide unit 35 collects a fee for making the issued ticket T unissued And guides the collection of the issued ticket T. Specifically, in the above case, the guide unit 35 displays on the display unit 30F a screen for guiding the collection of the fee for unissuing the ticket issued ticket T and the collection of the ticket issued ticket T being executed. It is good to make it.

  On the other hand, as a result of the collation by the collation unit 34, when the unique information of the issued ticket T is not included in the non-issued list, the guide unit 35 stops the procedure for making the issued ticket T unissued. invite. Specifically, in the above case, the guide unit 35 may cause the display unit 30F to display a screen that guides the non-ticketed ticket T to be issued and stops collection.

[3.8. Collection processing unit 36]
The collection processing unit 36 is realized mainly by the control unit 30A, the storage unit 30B, and the input unit 30E of the ticket verification device 30. When the collection processing unit 36 receives a fee collection and an input to the effect that the ticketed ticket T has been collected according to the guidance of the collection of the ticket issued ticket T by the guide unit 35, the collection processing unit 36 stores data in the data storage unit 31. The fact that the issued ticket T that has been subject to unissuance has been correctly collected is registered. Further, the collected ticket may be sent to a predetermined destination (for example, to a ticket issuer).

  Specifically, the collection processing unit 36 may write information on the collected ticket T collected in the collected ticket list table 31 </ b> B stored in the data storage unit 31. The information on the issued ticket T may be, for example, the ticket ID of the issued ticket T, the issued number of the issued ticket T, or the like.

  FIG. 7 shows an example of the collected ticket list table 31B. As shown in FIG. 7, the collected ticket list table 31B includes identification information for identifying a ticket, ticket issue number, identification information of the store S from which the ticket has been collected (collection store ID), and information on the ticket collection date and time. Are stored in association with each other.

  In the present embodiment, it is determined that the collection of the issued ticket T has been performed when the store S receives an input to the effect that the collection of the issued ticket T has been completed. At the time when T is sent and the collection of the issued ticket T is confirmed at a predetermined destination, or when the collected ticket list table 31B described later is transmitted (or received) to the ticket management server 10, the issued ticket T It may be determined that the collection is complete.

[3.9. Collected ticket list transmission unit 37, collected ticket list reception unit 14]
The collected ticket list transmission unit 37 is mainly realized by the control unit 30A, the storage unit 30B, and the communication unit 30C of the ticket verification device 30, and stores the collected ticket list table 31B stored in the data storage unit 31 as the ticket management server 10. Send to. The collected ticket list transmission unit 37 may transmit the latest collected ticket list table 31B to the ticket management server 10 every time a predetermined timing arrives. Here, the predetermined timing may be a timing at which the collected ticket list table 31B is updated, a predetermined time (for example, 2:00 am), a predetermined time interval (for example, every 12 hours), It is good also as the timing etc. which received the transmission request.

  The collected ticket list reception unit 14 is realized mainly by the control unit 10A, the storage unit 10B, and the communication unit 10C of the ticket management server 10, and receives the collected ticket list table 31B transmitted from the collected ticket list transmission unit 37. To do.

  When the receipt of the collected ticket list table 31B is normally completed, the ticket management server 10 may notify the ticket verification device 30 to that effect. Then, the ticket verification device 30 may delete the transmitted record from the collected ticket list table 31B in response to the notification.

[3.10. Ticket information update unit 15]
The ticket information update unit 15 is realized mainly by the control unit 10A and the storage unit 10B of the ticket management server 10. The ticket information updating unit 15 updates the ticket state of the ticket stored in the ticket information management table 11A based on the information in the collected ticket list table 31B received by the collected ticket list receiving unit 14.

  Specifically, the ticket information updating unit 15 changes the ticket status stored in association with the ticket information management table 11A to the ticket issued status (status “1” for the ticket identification information stored in the collected ticket list table 31B. ”) To an unissued state (state“ 0 ”).

  Further, for example, the ticket information update unit 15 receives the collected ticket list table 31B and receives the input indicating that the collected ticket has arrived at a predetermined destination. It is good also as performing.

[4. Description of processing executed in ticket system 1]
Next, based on FIG. 8 thru | or FIG. 19, the process which concerns on ticket non-issuance performed in the ticket system 1 is demonstrated concretely.

[4.1. Pre-registration process for unissued tickets]
FIG. 8 shows a sequence diagram relating to an example of a pre-registration process for an unissued ticket. The process shown in FIG. 8 is executed in the ticket management server 10 and the user terminal 20.

  The control unit 20A of the user terminal 20 transmits the user ID and password to the ticket management server 10 through the communication unit 10C, and executes login processing (S200).

  The control unit 10A of the ticket management server 10 performs authentication based on the user ID and password received from the user terminal 20 and executes login processing (S100). Hereinafter, the description will be continued assuming that the authentication is successful.

  When receiving a display request for a list screen (purchase history list screen) of tickets purchased by the user through the input unit 20D, the control unit 20A of the user terminal 20 transmits the data of the purchase history list screen to the ticket management server 10 through the communication unit 20C. The request is made (S202).

  When the control unit 10A of the ticket management server 10 receives a request from the user terminal 20 via the communication unit 10C (S102), based on the ticket information stored in the ticket information management table 11A in association with the user ID, User purchase history list screen data is generated (S104). The purchase history list screen data is data for causing the display means to display a purchase history list screen.

  Then, the control unit 10A of the ticket management server 10 transmits the generated purchase history list screen data to the user terminal 20 through the communication unit 10C (S106).

  The control unit 20A of the user terminal 20 receives the purchase history list screen data from the ticket management server 10 via the communication unit 20C (S204), and displays the purchase history list screen based on the received purchase history list screen data 20E. (S206).

  FIG. 11 shows an example of the purchase history list screen 50 displayed in S206. As shown in FIG. 11, the purchase history list screen 50 includes a list display area 50A for displaying a list of tickets purchased by the user and a return button 50C for returning to the previous screen.

  In the example shown in FIG. 11, it is assumed that there are two tickets (the first ticket and the second ticket) purchased by the user. Therefore, the first ticket displaying information about the first ticket is displayed in the list display area 50A. An information display area 50A-1 and a second ticket information display area 50A-2 for displaying information about the second ticket are included. In the first ticket information display area 50A-1 and the second ticket information display area 50A-2, the ticket status, performance name, ticket purchase date, performance date, venue, seat / number of sheets, detailed ticket information, respectively. A detailed display button 50B for displaying is displayed.

  In the example shown in FIG. 11, the ticket status of the second ticket is already issued, and a process for restoring the second ticket from the issued status to the unissued status will be described below.

  When the pressing of the detail display button 50B for the second ticket information display area 50A-2 is received by the input unit 20D, the control unit 20A of the user terminal 20 uses the communication unit 20C to display the details screen (ticket details screen) for the second ticket. Is requested to the ticket management server 10 (S208). For example, the control unit 20A of the user terminal 20 may transmit identification information for identifying the second ticket at the time of the above request.

  When the control unit 10A of the ticket management server 10 receives a request from the user terminal 20 via the communication unit 10C (S108), the control unit 10A records a record stored in the ticket information management table 11A in association with the transmitted ticket identification information (S108). Ticket detail screen data is generated based on (ticket information) (S110). The ticket detail screen data is data for displaying a ticket detail screen on the display means.

  Then, the control unit 10A of the ticket management server 10 transmits the generated ticket detail screen data to the user terminal 20 through the communication unit 10C (S112).

  The control unit 20A of the user terminal 20 receives the ticket detail screen data from the ticket management server 10 via the communication unit 20C (S210), and causes the display unit 20E to display the ticket detail screen based on the received ticket detail screen data. (S212).

  FIG. 12 shows an example of the ticket detail display screen 52 displayed in S212. As shown in FIG. 12, the ticket detail display screen 52 includes a ticket status display area 52A, an entertainment content display area 52C, a purchase information display area 52D, and a return button 52E for returning to the previous screen.

  In the ticket status display area 52A, detailed information related to ticket issuance is displayed. In the ticket status display area 52A, when a ticket has been issued, an unissued application button 52B for applying to restore the ticket to an unissued status is displayed.

  Detailed information regarding the performance of the ticket is displayed in the entertainment content display area 52C. For example, when the ticket is a sporting game, the date and time of the game, the place, seat information, and the like are displayed in the entertainment content display area 52C.

  Detailed information related to ticket purchase is displayed in the purchase information display area 52D. For example, the purchase information display area 52D displays the purchase date and time, purchase site, purchase price, and the like of the ticket.

  Next, when pressing of the non-ticketing application button 52B is accepted by the input unit 20D, the control unit 20A of the user terminal 20 requests the ticket management server 10 to issue a second ticket without issuing the communication unit 20C ( S214). For example, the control unit 20A of the user terminal 20 may transmit identification information for identifying the second ticket at the time of the above request.

  When the control unit 10A of the ticket management server 10 receives a request from the user terminal 20 via the communication unit 10C (S114), the control unit 10A displays a non-ticketed application screen for applying for non-ticketing of the ticket related to the request. To generate unissued ticket application screen data (S116).

  Then, the control unit 10A of the ticket management server 10 transmits the generated non-ticketed application screen data to the user terminal 20 through the communication unit 10C (S118).

  The control unit 20A of the user terminal 20 receives the non-ticketed application screen data from the ticket management server 10 via the communication unit 20C (S216), and displays the non-ticketed application screen based on the received non-ticketed application screen data. It is displayed on the display unit 20E (S218).

  FIG. 13 shows an example of the unissued ticket application screen 54 displayed in S218. As shown in FIG. 13, the non-ticketed application screen 54 includes a ticket information display area 54A, a ticketing number input field 54B, a ticketing date input field 54C, a purchaser name input field 54D, a decision button 54E, and a return button 54F. included.

  The ticket information display area 54 </ b> A is an area in which information on a ticket that has not been issued (ticket that has not been issued) is displayed. The ticket issue number input field 54B is an area for inputting a ticket issue number of an unissued ticket. The ticket issue date input field 54C is an area for inputting a ticket issue date of a ticket that is not issued. The purchaser name input field 54D is an area for inputting the name of the purchaser of the ticket that has not been issued.

  When information is entered in the ticketing number input field 54B, the ticketing date input field 54C, and the purchaser name input field 54D, and the press of the enter button 54E is accepted, the control unit 20A of the user terminal 20 is not issued by the communication unit 20C. By issuing the ticket generation target ticket data (ticket identification information and unique information) to the ticket management server 10, the non-ticketing is requested (S 222).

  When the control unit 10A of the ticket management server 10 receives the data of the non-ticketed ticket from the user terminal 20 via the communication unit 10C (S120), the control unit 10A updates the non-ticketed list table 11B based on the received data. . Specifically, the control unit 10A of the ticket management server 10 generates a new record in the unissued list table 11B, and includes the received ticket identification information and unique information (ticketing number, (Ticketing date, purchaser name).

  FIG. 14 shows an example of a purchase history list screen 50 after accepting a non-ticketed application for the second ticket. As shown in the second ticket information display area 50 </ b> A- 2 in FIG. 14, after accepting an unissued application, the state of the second ticket may be updated to “Unissued ticket application”. In this case, the control unit 10A of the ticket management server 10 determines the status of the ticket stored in the ticket information management table 11A for the unissued ticket after receiving the above-mentioned unissued ticket data. It may be updated to “Applying for ticketing”.

  The above is an example of the pre-registration process for an unissued ticket. Next, the distribution processing of the unissued list will be described based on FIG.

[4.2. Unissued ticket distribution processing]
As shown in FIG. 9, the control unit 10A of the ticket management server 10 determines whether or not the transmission timing of the unissued list table 11B has arrived (S130). For example, the above transmission timing may be a timing at which the non-ticketed list table 11B stored in the ticket management server 10 is updated, a predetermined time (for example, 2 am), or a predetermined time interval (for example, The timing at which a transmission request is accepted may be set every 12 hours.

  In S130, the control unit 10A of the ticket management server 10 stands by when the above transmission timing has not arrived (S130: N), and when the above transmission timing has arrived (S130: Y), The non-ticketed list table 11B is transmitted to the ticket verification device 30 (S132). When there are a plurality of ticket verification devices 30 in the ticket system 1, the ticket management server 10 transmits an unissued list table 11 </ b> B to each ticket verification device 30.

  The control unit 30A of the ticket verification device 30 receives the non-ticketed list table 11B from the ticket management server 10 via the communication unit 30C (S330), and stores the received non-ticketed list table 11B in the storage unit 30B ( S332).

  The above is an example of the distribution processing of the unissued list. Next, the control process of the non-ticketing procedure will be described based on FIG. In addition, the control process of the unissued procedure described below is a ticket after the user U has taken the issued ticket T to the store S and requested the clerk to issue the issued ticket T to the unregistered procedure at the cash register of the store S. The flow of processing in the system 1 is shown.

[4.3. Control processing of unissued procedures]
As illustrated in FIG. 10, the control unit 30A of the ticket verification device 30 receives a request for a non-ticketed procedure for the issued ticket T based on the operation received by the input unit 30E (S340). Then, the control unit 30A of the ticket verification device 30 displays the non-ticketed procedure start screen 60 on the display unit 30F (S342).

  FIG. 15 shows an example of the non-ticketing procedure start screen 60 displayed in S342. As shown in FIG. 15, the example of the non-ticketing procedure start screen 60 is the target of the non-ticketing procedure. An instruction for the store clerk of the store S is displayed so as to read the bar code of the issued ticket T. When the return button 60A is pressed, the unissued procedure is cancelled.

  In response to the guidance on the non-ticketing procedure start screen 60, the information reading unit 30D of the ticket verification device 30 reads the barcode printed in the barcode printing area T1 of the ticket issued ticket T (S344). Then, the control unit 30A of the ticket verification device 30 decodes the read barcode, and acquires unique information of the ticket T issued ticket T encoded in the bird.

  Next, the control unit 30A of the ticket collation device 30 collates the unissued ticket list table 31A with the unique information acquired from the issued ticket T, and stores the ticket issued ticket T in the unissued ticket list table 31A. It is determined whether unique information is included (S346).

  If the collation is successful as a result of the collation (that is, the unique information of the ticket issued ticket T is included in the unissued ticket list table 31A) (S348: Y), the collection guide screen is displayed on the display unit 30F. 62 is displayed (S350).

  FIG. 16 shows an example of the collection guide screen 62 displayed in S350. As shown in FIG. 16, in the example of the collection guidance screen 62, it is instructed to collect the issued ticket T and collect the fee required for the unissued procedure. By pressing the return button 62B, it is possible to return to the previous screen.

  When the collection of the issued ticket T and the collection of the fee are completed according to the guidance on the collection guidance screen 62, the store clerk presses the completion button 62A.

  When the above collection procedure is not completed (that is, when the input unit 30E does not accept the pressing of the completion button 62A) (S352: N), the control unit 30A of the ticket verification device 30 stands by.

  On the other hand, when the above-described collection procedure is completed (that is, when the input unit 30E accepts pressing of the completion button 62A) (S352: Y), the control unit 30A of the ticket matching device 30 performs the collected ticket list table 31B. Is updated (S354). Specifically, the control unit 30A of the ticket verification device 30 adds a new record to the collected ticket list table 31B, and at the same time, adds identification information of the ticket T issued ticket T, ticket issue number of the ticket issued ticket T, The identification information (collection store ID) of the store S that has collected the ticket issued ticket T and the information of the collection date and time of the ticket issued ticket T are written.

  When the control unit 30A of the ticket verification device 30 finishes updating the collected ticket list table 31B, the control unit 30A displays the acceptance completion screen 64 on the display unit 30F (S356).

  FIG. 17 shows an example of the reception completion screen 64 displayed in S356. As shown in FIG. 17, the acceptance completion screen 64 displays the completion of acceptance of the non-ticketing procedure and an instruction to send the collected ticket issued ticket T to a predetermined destination. In the acceptance completion screen 64, the menu screen can be returned by pressing the return button 64A.

  As a result of the collation in S346, if the collation is not successful (that is, the unique information of the issued ticket T is not included in the unissued list table 31A) (S348: N), the ticket collation apparatus 30 The control unit 30A displays the error screen 66 on the display unit 30F (S358).

  FIG. 18 shows an example of the error screen 66 displayed in S358. As shown in FIG. 18, the error screen 66 displays that the verification of the issued ticket T has failed and that the acceptance of the unissued procedure for the issued ticket T has been completed. That is, when the verification of the issued ticket T fails, the issued ticket T is not collected, and the issued ticket T is returned to the user U. In the error screen 66, it is possible to return to the previous screen by pressing the return button 66A.

  Here, when the transmission timing of the collected ticket list table 31B has not arrived (S360: N), the control unit 30A of the ticket verification device 30 returns to S340, and the transmission timing of the collected ticket list table 31B is If it has arrived (S360: Y), the communication unit 30C transmits the collected ticket list table 31B to the ticket management server 10 (S362).

  The control unit 10A of the ticket management server 10 receives the collected ticket list table 31B transmitted from the ticket verification device 30 by the communication unit 10C (S140). Then, the control unit 10A of the ticket management server 10 updates the unissued list table 11B stored in the storage unit 10B based on the received collected ticket list table 31B (S142).

  For example, the control unit 10A of the ticket management server 10 is included in the received collected ticket list table 31B among records including ticket identification information and unique information (ticketing number etc.) included in the unissued ticket list table 11B. A record including ticket identification information and unique information (ticketing number, etc.) may be deleted, and the unissued ticket list table 11B may be updated.

  Further, the control unit 10A of the ticket management server 10 updates the ticket information management table 11A stored in the storage unit 10B based on the received collected ticket list table 31B (S144).

  For example, the control unit 10A of the ticket management server 10 includes a record including ticket identification information included in the received collected ticket list table 31B among records including ticket identification information included in the ticket information management table 11A. The ticket state may be updated from the issued state to the unissued list table 11B.

  FIG. 19 shows an example of the purchase history list screen 50 displayed after S144. As shown in FIG. 19, on the purchase history list screen 50, the ticket status displayed for the second ticket information display area 50A-2 is updated to an unissued status.

  According to the ticket system 1 according to the present embodiment described above, it is possible to return a ticket designated from tickets that have been issued once to an unissued state in which the user has purchased, that is, a state in which ticketing is possible again. . Further, since the issued tickets are collected, it is possible to prevent a plurality of tickets having the same contents from being issued. That is, according to the ticket system 1, while maintaining the right to purchase a ticket, it is possible to return the ticket from the ticket issuing state to the unissued state while avoiding the duplicate issue of the ticket.

  Further, in the ticket system 1, the ticket specific information (for example, the ticket issuing number) printed on the ticket is used for collation of the ticket to be issued and designated as the ticket to be issued. It can guarantee the identity of the ticket. That is, according to the ticket system 1, it is possible to prevent an incorrect ticket from being issued.

  In the ticket system 1, unique information can be registered in advance for a ticket to be returned to an unissued state. Thereby, when registering the ticket to be returned to the unissued state, the unique information of the ticket after the issue is necessary, so that it is possible to prevent a ticket that is not on the user's hand from being erroneously registered as an unissued target.

  Further, in the ticket system 1, if the verification of the ticket that is not issued is not successful, the ticket issuing is stopped, so that the ticket that has not been issued is not issued. It can be prevented from being broken.

  The present invention is not limited to the above embodiment. For example, the ticket system 1 may further include the following functions.

  For example, in the ticket system 1 described above, an unissued ticket may be transferable from the purchaser of the ticket to another person. For example, the ticket system 1 may be able to set a ticket designated by the purchaser among the unissued tickets to the resale state (resale state). At this time, when the ticket in the resale state is purchased by another user within the expiration date of the resale state, the transfer of the ticket may be established.

  Note that a ticket that has already been issued cannot be set to the above-mentioned resale state. However, according to the above ticket system 1, a ticket that has been issued can be returned to an unissued state. Is possible.

  Further, for example, in the above ticket system 1, an unissued ticket may be issued as an electronic ticket stored in a smartphone or a mobile phone. In the above ticket system 1, even when a ticket is issued as a paper medium ticket, it can be returned to an unissued state, so that a paper medium ticket can be reissued as an electronic ticket.

  Further, in the ticket system 1 described above, the ticket management ticket 10 may be verified by the ticket management server 10 (that is, the verification unit 34 may be provided in the ticket management server 10). Hereinafter, a specific processing flow will be described.

  First, the ticket verification device 30 transmits the unique information of the issued ticket T acquired by the issued ticket information acquisition unit 33 to the ticket management server 10. Next, the ticket management server 10 verifies whether or not the unique information of the issued ticket T received from the ticket verification device 30 is included in the unissued list stored in the unissued list table 11B. The result is transmitted to the ticket verification device 30. Then, the ticket verification device 30 indicates that the verification result received from the ticket management server 10 indicates that the unique information of the ticket T already issued is included in the unissued list stored in the unissued list table 11B. Next, the collection of the issued ticket T is guided, and if not, the collection of the issued ticket T is stopped. Then, the ticket verification device 30 notifies the ticket management server 10 of the completion of collection when the collection of the issued ticket T is completed according to the above guidance. Then, the ticket management server 10 updates the ticket status of the issued ticket T to an unissued status when receiving the above notification of completion of collection.

  In the above example, the ticket management server 10 does not need to transmit the information in the unissued list table 11B to the ticket verification device 30. Therefore, the ticket system 1 includes the unissued list transmission unit 13, The ticketing list receiving unit 32 and the non-ticketing list table 31A may not be provided.

S store T ticket issued ticket T1 barcode printing area T2 ticket number printing area T3 ticketing date printing area T4 purchaser printing area U user 1 ticket system 2 network 10 ticket management server 10A control unit 10B storage unit 10C communication unit 11 data storage unit 11A Ticket information management table 11B Unissued ticketing list table 12 Unissued ticketing designation receiving unit 13 Unissued ticketing list transmitting unit 14 Collected ticket list receiving unit 15 Ticket information updating unit 20 User terminal 20A Control unit 20B Storage unit 20C Communication unit 20D Input unit 20E Display unit 21 Unissued ticket designation unit 30 Ticket verification device 30A Control unit 30B Storage unit 30C Communication unit 30D Information reading unit 30E Input unit 30F Display unit 31 Data storage unit 31A Unissued ticket generation list table 31B Collected ticket List table 32 unissued ticket list receiving unit 33 issued ticket information acquisition unit 34 collation unit 35 guide unit 36 collection processing unit 37 collected ticket list transmission unit 50 purchase history list screen 50A list display area 50A-1 first ticket Information display area 50A-2 Second ticket information display area 50B Detailed display button 50C Return button 52 Ticket detail display screen 52A Ticket status display area 52B Unissued ticket application button 52C Entertainment content display area 52D Purchase information display area 52E Return button 54 Not displayed Ticketing application screen 54A Ticket information display area 54B Ticketing number input field 54C Ticketing date input field 54D Purchaser name input field 54E Decision button 54F Return button 60 Unissued ticketing procedure start screen 60A Return button 62 Collection guidance screen 62A Completion button 62B That button 64 Back acceptance completion screen 64A Back button 66 error screen 66A button

Claims (8)

A ticket system comprising: a ticket management device that manages ticket information; and a ticket verification device that is communicably connected to the ticket management device,
The ticket management device includes:
Storage means for storing in association whether each settled ticket has been issued or not issued,
Accepting means for accepting designation of a ticket to be restored to an unissued state from tickets that have been issued;
First transmission means for transmitting a list of unique information of the ticket received by the reception means to the ticket verification device ;
The ticket verification device
An acquisition means for acquiring unique information of the issued ticket;
A guide unit for guiding collection of the issued ticket when the unique information acquired by the acquisition unit is included in the list transmitted by the first transmission unit ;
Second transmission means for transmitting information on the issued ticket collected according to the guidance by the guidance means to the ticket management device ,
The ticket management apparatus further includes an update unit that updates information stored in the storage unit in association with the ticket information transmitted by the second transmission unit , so that the ticket is in an unissued state. Characteristic ticket system. The ticket system according to claim 1, wherein the acquisition unit scans and acquires the unique information printed on the ticket that has been issued. The ticket system according to claim 1 or 2 , wherein the unique information is information including a ticket issue number of the ticket that has been issued. The ticket system according to any one of claims 1 to 3 , wherein the accepting unit accepts specific information of the ticket together with designation of the ticket to be restored to the unissued state. The guide means guides to stop the process of making the issued ticket unissued when the acquired unique information is not included in the unique information of the ticket received by the accepting means. The ticket system according to any one of claims 1 to 4 . A ticket system control method comprising: a ticket management device that manages ticket information; and a ticket verification device that is communicably connected to the ticket management device,
The ticket management device
Storing, in association with each other, whether the ticket that has been settled is issued or not issued in the storage means;
A reception step of accepting designation of a ticket to be restored to an unissued state from tickets that have been issued;
A first transmission step of transmitting a list of unique information of the ticket accepted in the acceptance step to the ticket verification device ,
The ticket verification device
An acquisition step of acquiring unique information of the issued ticket;
A guide step for guiding collection of the issued ticket when the unique information acquired in the acquisition step is included in the list transmitted in the first transmission step ;
A second transmission step of transmitting information on the issued ticket collected in response to the guidance in the guidance step to the ticket management device ,
The ticket management device
An update step of updating the information stored in the storage means in association with the ticket information transmitted in the second transmission step when the ticket is in an unissued state. Control method. A ticket system comprising: a ticket management device that manages ticket information; and a ticket verification device that is communicably connected to the ticket management device,
The ticket management device includes:
Storage means for storing in association whether each settled ticket has been issued or not issued,
Receiving means for accepting designation of a ticket to be restored to an unissued state from tickets that have been issued,
The ticket verification device
An acquisition means for acquiring unique information of the issued ticket;
Means for transmitting the ticket specific information acquired by the acquisition means to the ticket management device,
The ticket management device further comprises means for transmitting a matching result indicating whether or not the unique information acquired by the acquiring means is included in the unique information of the ticket received by the receiving means to the ticket matching device,
The ticket verification device
Guidance means for guiding collection of the issued ticket when the verification result indicates that the unique information of the ticket received by the accepting means includes the unique information acquired by the acquiring means;
Transmission means for transmitting information on the issued ticket collected according to the guidance by the guidance means to the ticket management device,
The ticket management device further comprises update means for updating information stored in the storage means in association with the ticket information transmitted by the transmission means that the ticket is in an unissued state. Ticket system. A ticket system control method comprising: a ticket management device that manages ticket information; and a ticket verification device that is communicably connected to the ticket management device,
The ticket management device
Storing, in association with each other, whether the ticket that has been settled is issued or not issued in the storage means;
Receiving a designation of a ticket to be restored to an unissued state from tickets that have been issued,
The ticket verification device
An acquisition step of acquiring unique information of the issued ticket;
Transmitting the ticket specific information acquired in the acquisition step to the ticket management device,
The ticket management device further includes a step of transmitting to the ticket verification device a verification result indicating whether or not the unique information acquired in the acquisition step is included in the specific information of the ticket received in the reception step,
The ticket verification device
When the verification result indicates that the unique information acquired in the acquisition step is included in the unique information of the ticket received in the reception step, a guidance step for guiding collection of the issued ticket;
A transmission step of transmitting information on the issued ticket collected in response to the guidance in the guidance step to the ticket management device,
The ticket management device further includes an update step of updating the information stored in the storage means in association with the ticket information transmitted in the transmission step so that the ticket is in an unissued state. To control the ticket system.

Images