JPH05266048A - Ticket issuing device - Google Patents

Abstract

PURPOSE:To provide the ticket issueing device which can prevent double issuance ticket for a ticket once issued. CONSTITUTION:A host computer 1 and a terminal device 2 are connected by a communication line 3. At the host computer 1, when ticket issuing request data is received from the terminal device 2, a processing part 11 prepares ticket issuing data, stores it temporarily in a storage part 12 and transmits it to the terminal device 2. At the terminal device 2, when the ticket issuing data is received, a ticket issuing part 23 issues tickets based on the ticket issuing data. At this time, a control part 25 detects whether tickets were issued normally or not, and transmits ticket issuing completion notice in the normal case, or abnormal completion notice in the abnormal case to the host computer 1. The host computer 1 clears the corresponding ticket issuing data inside the storage part 12 when it received the ticket issuing completion notice, and does not clear the ticket issuing data inside the storage part 12 and leaves it as it is when it received the abnormal completion notice.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention comprises, for example, a seat reservation terminal device installed at a window of a station and a host computer to which these terminal devices are online connected via a communication line. It relates to a ticket issuing device that issues such as.

[0002]

2. Description of the Related Art As is well known, for example, a ticket issuing device for issuing a seat reservation ticket for a train is connected to a seat reservation terminal device installed at a window of each station, and these terminal devices are connected online via a communication line. The host computer creates ticket-issuing data, transmits it to the terminal device, and the terminal device receives the data and issues the corresponding ticket.

[0003]

However, conventionally, it was not possible for the host computer side to judge whether or not the ticket was normally issued in the terminal device. If the ticket cannot be issued normally, the ticket issuing data is transmitted from the host computer to the terminal device again to issue the ticket.

Therefore, conventionally, there is a problem that even if a ticket is normally issued, the same ticket is issued when the same ticket data is subsequently received from the host computer.

In addition, several tickets can be issued
If the ticket issuing becomes abnormal during the process, the same ticket issuing data is received again from the host computer and the ticket is issued. In that case, there was a problem of double ticketing, in which some tickets issued before were also issued.

Therefore, according to the present invention, a normally issued ticket is not reissued, and a ticket that cannot be normally issued due to a jam or the like can be reissued to prevent double ticketing. It is an object of the present invention to provide a ticket issuing device that can be used.

[0007]

A ticket issuing apparatus of the present invention is a ticket issuing data creating means for creating ticket issuing data, and the ticket issuing data created by the ticket issuing data creating means is temporarily stored in a storage means. Of the ticket issuing data to the outside and the ticket issuing means for issuing the ticket corresponding to the ticket issuing data by receiving the ticket issuing data transmitted from the controlling means, and whether the ticket issuing means normally issued the ticket. Ticketing state detection means for detecting whether or not each ticket is issued, and transmitting a ticketing state signal indicating whether or not the ticket is normally issued to the control means, and the ticketing state detection means for the control means. When the ticketing status signal is received,
And a ticket issuing data clearing means for clearing the corresponding ticket issuing data in the storage means when the ticket issuing status signal indicates that the ticket is issued normally.

[0008]

[Function] For a ticket that has been normally issued, the corresponding ticketing data is cleared after the ticketing is completed, so even if the same ticketing data is requested again to the ticketing data creation side,
Ticketing data will not be sent. When issuing multiple tickets, 1
Since the ticketing status signal is transmitted for each ticketing, the ticketing data creation side can easily know how many tickets have been normally issued. As a result, reissued tickets will not be issued for tickets that have been issued normally, and tickets that could not be issued normally due to a ticket jam, etc., can be reissued, making it possible to issue double issued tickets normally. Can be prevented.

[0009]

DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 schematically shows the construction of a ticket issuing device for issuing, for example, a seat reservation ticket for a train according to this embodiment. In the figure, reference numeral 1 is a host computer as a main control unit, which is installed at a specific place remote from a station, for example. 2 is a train seat reservation terminal device,
It is installed at the window of each station, and is online connected to the host computer 1 via the communication line 3.

The host computer 1, for example, performs a seat reservation process and creates a ticketing data processing unit 11.
A storage unit 12 for temporarily storing the created ticketing data,
Further, it is configured by a control unit 13 that controls these and controls data transmission and reception.

The terminal device 2 includes, for example, an input unit 21 such as a keyboard for inputting ticketing condition data and the like, and a display unit 2 such as a CRT display for displaying input data and the like.
2. A ticket issuing unit 23 that prints and issues a ticket, a processing unit 24 that performs a face editing process, and a control unit 25 that controls these and controls data transmission and reception.

Next, the operation in such a configuration will be described. First, in the terminal device 2, by inputting ticketing condition data and the like using the input unit 21 and the display unit 22, the control unit 25 sends ticketing request data corresponding to the input ticketing condition data to the host computer 1. Send.

In the host computer 1, when the ticket issuing request data from the terminal device 2 is received, the processing section 11 performs a seat securing process based on the ticket issuing request data and creates corresponding ticket issuing data. The created ticketing data is temporarily stored in the storage unit 12 under the control of the control unit 13, and the ticketing data in the storage unit 12 is transmitted to the terminal device 2.

In the terminal device 2, when the ticket issuing data from the host computer 1 is received, the processing section 24 performs a ticket face editing process based on the ticket issuing data, and the editing process result is sent to the ticket issuing section 23 via the control section 25. Sending, ticketing section 23
Performs a ticket issuing process based on the edited ticket issuing data to print and issue a corresponding ticket.

At this time, the control unit 25 detects whether or not the ticket is normally issued for each ticket by checking signals from various sensors (not shown) in the ticket issuing unit 23. As a result, if normal, the control unit 25 transmits a ticketing completion notice to the host computer 1, and if abnormal,
An abnormal end notification is sent to the host computer 1.

In the host computer 1, when the ticket issuing end notification is received from the terminal device 2, the control unit 13 clears the corresponding ticket issuing data in the storage unit 12. If the abnormal termination notification is received from the terminal device 2, the ticket issuing data in the storage unit 12 is left as it is.

After that, when the host computer 1 receives the re-request data from the terminal device 2, the control unit 13
Sends the corresponding ticketing data in the storage unit 12 to the terminal device 2 again to issue a ticket. Then, when the ticketing completion notification is received from the terminal device 2, the corresponding ticketing data in the storage unit 12 is cleared. Further, when the abnormal end notification is received, the process when the abnormal end notification is received is repeated.

If the host computer 1 first receives ticketing request data from the terminal device 2 and the processing section 11 creates ticketing data, if a plurality of ticketing data are generated, all the ticketing data is generated. Is stored in the storage unit 12,
Tickets are issued in units of one.

That is, first, the first ticketing data is transmitted to the terminal device 2, the ticketing is completed, and the terminal device 2 transmits a ticketing completion notice. When the host computer 1 receives the ticketing completion notification, the control unit 13 causes the storage unit 1 to
The first ticketing data is cleared from all ticketing data in 2. Then, the control unit 13 issues the next ticket issuing data to the terminal device 2 and issues all the tickets by the method of issuing the ticket.

If the ticket issuing becomes abnormal in the course of issuing a plurality of tickets, the terminal device 2 sends an abnormal end notification to the host computer 1. In the host computer 1, the ticket issuing data in the storage unit 12 is cleared for the ticket issuing data of the normally issued ticket. Therefore, when the re-request data is received from the terminal device 2, the control unit 13 causes the storage unit to receive the request data. The ticket issuing data in 12 is transmitted to the terminal device 2, and the remaining tickets are issued.

When all tickets have been issued, the storage unit 12
Since there is no ticket issuing data in it, the host computer 1 does not send the ticket issuing data even if the terminal device 2 sends the re-request data. Therefore, the same ticket cannot be issued more than once. FIG. 2 shows a flow when a ticket is issued normally in units of one sheet.

FIG. 3 shows the flow when the ticket issuing process is not normally performed when the ticket is issued in units of one sheet. After receiving the abnormal termination notification, the host computer 1 keeps the ticket issuing data in the storage unit 12 stored for the reissue ticket. After recovering the place where the ticket issuing is abnormal, the terminal device 2 transmits the re-request data to the host computer 1 and performs the ticket issuing process again. FIG. 4 shows a flow when the ticket is issued after the re-request data is transmitted to the host computer 1 when the ticket is abnormally terminated and the ticket issuing data is received.

FIG. 5 shows the flow when the ticket reissuing process is sent to the host computer 1 when the ticket is abnormally terminated and the ticket reissuing data is received. In this case, the re-request data is transmitted to the host computer 1 until the flow of FIG. 4 is reached.

FIG. 6 shows the flow when a plurality of tickets are issued normally. First, the host computer 1 first stores a plurality of ticket issuing data in the storage unit 12, transmits the ticket issuing data for each ticket, and issues a ticket. Also, the storage unit 1
With regard to the ticketing data of No. 2, the ticketing data for each ticket is cleared after the ticket issuance. FIG. 7 shows a flow when a plurality of tickets are issued and a ticket issue occurs in the middle (Xth ticket).

FIG. 8 shows that after a plurality of tickets have been abnormally terminated,
The flow when the reissued data is transmitted to the host computer 1 and the ticket is issued after the abnormal portion of the terminal device 2 is recovered is shown. The ticket issuing data in the storage unit 12 of the host computer 1 is cleared for the ticket issuing data that is normally issued, but the ticket issuing data subsequent to the ticket issuing data that has become abnormal is stored without being cleared. Issue a ticket.

FIG. 9 shows the flow when abnormal termination occurs when a plurality of tickets are issued, then re-request data is transmitted from the terminal device 2 and ticket issue data is received from the host computer 1. Show.

As described above, even if the terminal device transmits a ticketing completion notification to a host computer for a ticket that has been normally issued, and then the terminal device re-requests the same ticketing data from the host computer, After the computer receives the ticketing completion notification, the ticketing data is not transmitted again. As a result, it is possible not to issue double-issued tickets that have already been issued.

Further, when a plurality of tickets are issued, the terminal device sends a ticket completion notification to the host computer every time it issues one ticket, so that the host computer can easily know how many tickets have been normally issued. This makes it possible to prevent a normally issued ticket from being issued twice even if a ticket jam occurs during the issuing of a plurality of tickets.

In the above embodiment, the case where the invention is applied to the ticket issuing device for issuing a seat reservation ticket for a train has been described, but the present invention is not limited to this.
The present invention can be similarly applied to a ticket issuing device that issues a train ticket, a ticket for another vehicle, a ticket for a facility, or the like.

Further, the case where the present invention is applied to a ticket issuing device including a host computer and a terminal device has been described, but the present invention is not limited to this, and a ticket issuing device in which these are integrated is similarly applied. it can.

[0032]

As described above in detail, according to the present invention, a ticket that has been normally issued cannot be reissued, and a ticket that cannot be normally issued due to a jam or the like can be reissued. Therefore, it is possible to provide a ticket issuing device capable of preventing double ticket issuing.

[Brief description of drawings]

FIG. 1 is a block diagram schematically showing a ticket issuing device according to an embodiment of the present invention.

FIG. 2 is a flowchart illustrating a normal termination when issuing one ticket.

FIG. 3 is a flowchart for explaining abnormal termination when issuing one ticket.

FIG. 4 is a flowchart illustrating normal termination at the time of reissue of a ticket after abnormal termination of one ticket issuance.

FIG. 5 is a flowchart for explaining abnormal termination at the time of reissue ticket issuance after the abnormal termination of one ticket issuance.

FIG. 6 is a flowchart illustrating a normal termination when a plurality of tickets are issued.

FIG. 7 is a flowchart illustrating an abnormal termination when a plurality of tickets are issued.

FIG. 8 is a flowchart illustrating a normal termination at the time of reissue of a ticket after abnormally issuing a plurality of tickets.

FIG. 9 is a flowchart for explaining abnormal termination at the time of reissue of a ticket after abnormal termination of ticket issuance for plural sheets.

[Explanation of symbols]

1 ... Host computer, 11 ... Processing unit, 12 ...
Storage unit, 13 ... Control unit, 2 ... Seat reservation terminal device, 2
1 ... Input section, 22 ... Display section, 23 ... Ticketing section, 24
...... Processing unit, 25 ...... Control unit, 3 ...... Communication line.

Claims (1)

[Claims] 1. Ticket issuing data creating means for creating ticket issuing data, and control means for temporarily storing the ticket issuing data created by the ticket issuing data creating means in a storage means and transmitting the ticket issuing data in the storage means to the outside. By receiving the ticket issuing data transmitted from the control means, the ticket issuing means for issuing a ticket corresponding to the ticket issuing data and whether or not the ticket issuing means normally issued the ticket are detected for each ticket issuing, A ticketing state detection means for transmitting to the control means a ticketing state signal indicating whether or not the ticket is normally issued, and in the control means, when the ticketing state signal transmitted from the ticketing state detection means is received, the ticketing state signal A ticket issuing data clearing means for clearing corresponding ticket issuing data in the storage means only when the ticket indicating that the ticket has been issued normally has been provided. That ticketing equipment.