Ticket-changing device and ticket-changing program

Abstract

To provide a ticket changing device and a ticket changing program capable of easily changing a magnetic ticket to another kind of ticket.SOLUTION: The ticket changing device 100 includes a reader 21 for reading the ticket validity from the magnetic information of the magnetic ticket MT, a converter 23 for converting the ticket validity into an identification code DC, and a ticket issuing device 24 for issuing a substitute ticket QT displaying the identification code DC.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a ticket change device and a ticket change program for changing a magnetic ticket into another type of ticket. [Background technology]

[0002] BACKGROUND ART Automatic ticket gates that process ticket media on which codes such as two-dimensional codes indicating ticket information are recorded and perform ticket gate processing are known (Patent Document 1).

[0003] If the technology of Patent Document 1 is introduced in a ticket gate that no longer accepts magnetic tickets, a problem will arise in that users who enter using a magnetic ticket will not be able to go through the ticket gate process. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-84275 Summary of the Invention

[0005] The present invention has been made in consideration of the above points, and aims to provide a ticket change device and a ticket change program that can easily convert a magnetic ticket into another type of ticket.

[0006] In order to achieve the above-mentioned object, the ticket change device of the present invention comprises a reading device that reads the ticket validity from the magnetic information of a magnetic ticket, a conversion device that converts the ticket validity into an identification code, and a ticket issuing device that issues a replacement ticket displaying the identification code.

[0007] The ticket change device changes magnetic tickets into replacement tickets bearing identification codes, enabling smooth ticket gate processing even at stations that have abolished magnetic tickets. Since the ticket validity is read from the magnetic information on the magnetic ticket, the ticket validity can be accurately extracted and converted into an identification code. The ticket change device can be a standalone device or can share components with existing automatic fare adjustment machines.

[0008] In order to achieve the above-mentioned object, the ticket change program of the present invention causes a control device to read the ticket validity from the magnetic information of a magnetic ticket using a reading device, convert the ticket validity into an identification code using a conversion device, and issue a replacement ticket displaying the identification code using a ticket issuing device. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is an overall conceptual diagram illustrating a ticket change device according to a first embodiment. [Figure 2] FIG. 2 is a block diagram illustrating the configuration of a ticket change device. [Figure 3] 10 is a flowchart illustrating the operation of the ticket change device. [Figure 4] FIG. 10 is a block diagram illustrating a ticket change device according to a second embodiment. [Figure 5] FIG. 10 is a block diagram illustrating a ticket change device according to a third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] [First embodiment] A first embodiment of a ticket change device according to the present invention will be described with reference to FIG.

[0011] Fig. 1 is an overall conceptual diagram illustrating the ticket change device 100. Fig. 2 is a block diagram illustrating the configuration of the ticket change device 100.

[0012] The ticket change device 100 shown in FIG. 1 and elsewhere changes a magnetic ticket MT into a different type of ticket, i.e., a replacement ticket QT, that is compatible with a ticket gate 200 of a station or operator that has discontinued the magnetic ticket MT. If a railway user US purchases a magnetic ticket MT from operator A, which issues magnetic tickets MT, and enters through operator A's ticket gate, if operator B, with which the railways share common access, has discontinued the magnetic ticket MT, the user US cannot pass through operator B's ticket gate 200 with the magnetic ticket MT. Therefore, the magnetic ticket MT issued by operator A must be changed into a replacement ticket QT that can be used at operator B's ticket gate 200. The ticket change device 100 of this embodiment reads the ticket validity, which is ticket information on the magnetic ticket MT, and issues a replacement ticket QT. This allows user US who entered using the magnetic ticket MT to exit through operator B's ticket gate 200, which has discontinued the magnetic ticket MT.

[0013] A replacement ticket QT is a ticket that displays an identification code DC, which records ticket validity (ticket information), on a medium instead of a magnetic ticket MT. The replacement ticket QT can be optically read by a reader 2, such as a camera, in the ticket gate 200. Replacement tickets QT include, for example, (a) a new ticket (such as a paper ticket) with the identification code DC printed on it, (b) a magnetic ticket MT with the identification code DC printed on its face TS (front side) (reuse of a magnetic ticket MT), and (c) a ticket displayed on the user US's mobile terminal. The user US passes through the ticket gate passage PA by holding the identification code DC of the replacement ticket QT over the reader 2 of the ticket gate 200. The ticket gate 200 captures an image of the identification code DC displayed on the replacement ticket QT with the reader 2 and outputs it as image data. The ticket gate 200 decodes the identification code DC based on the image data, obtains the ticket validity, and performs ticket gate processing.

[0014] The ticket change device 100 includes a control device 10, a ticket processing device 20, a fare processing device 30, a storage device 40, a display device 50, an operation device 60, and a communication device 70. The ticket change device 100 is capable of communicating with an external management server 80 via the communication device 70.

[0015] The ticket change device 100 operates based on application software or a program stored in the storage device 40 by the control device 10. The control device 10 is equipped with an arithmetic processing device such as a CPU, and reads the ticket change program P1 (see FIG. 2), other computer programs, data, etc. stored in the storage device 40, and executes predetermined information processing (specifically, various processes executed by the ticket change device 100). In other words, the control device 10 performs various data processing for controlling the ticket processing device 20, etc. For example, the control device 10 reads the ticket validity from the magnetic information on the magnetic ticket MT using the reader 21 of the ticket processing device 20. The control device 10 also converts the ticket validity into an identification code DC using the converter 23 of the ticket processing device 20. The control device 10 also issues a replacement ticket QT bearing the identification code DC using the ticket issuing device 24 of the ticket processing device 20.

[0016] As shown in FIG. 2, the ticket processing device 20 includes a reader 21, a collector 22, a converter 23, and a ticket issuing device 24.

[0017] The reading device 21 reads the ticket validity from the magnetic information on the magnetic ticket MT. The reading device 21 has an insertion slot 21a (see Figure 1) that accepts the magnetic ticket MT. The ticket validity corresponds to the ticket information, such as the issue date, issue location, entry location, type, validity section, expiration date, fare (fare), entry date and time, etc. The ticket validity is assigned, for example, a different identification number for each ticket. The ticket validity is linked to the identification number and recorded in the management server 80. The ticket validity described above is an example, and its content can be changed as appropriate depending on the purpose, usage situation, etc.

[0018] The collecting device 22 collects the magnetic ticket MT that has been read. Note that if the magnetic ticket MT is reused by printing the identification code DC on the face TS of the magnetic ticket MT, the collecting device 22 may be omitted.

[0019] The conversion device 23 converts the ticket validity into an identification code DC. Specifically, the conversion device 23 encodes the ticket validity to create the identification code DC. The identification code DC is, for example, a two-dimensional code such as a QR code (registered trademark) or a barcode, and corresponds to the ticket gate 200 at which the ticket user exits.

[0020] When no settlement process is performed, the conversion device 23 converts the read ticket validity directly into the identification code DC. The conversion device 23 may convert the entire ticket validity into the identification code DC, or, when the ticket validity is recorded in the management server 80 or the like, may convert only the identification number into the identification code DC. Note that, when an inquiry about exit permission or settlement process is performed, the conversion device 23 may add exit permission information to the read ticket validity and convert it into the identification code DC. In this embodiment, the conversion device 23 generates the identification code DC using the result of an inquiry to the management server 80. That is, a code generation program P2 that generates the identification code DC is stored in the storage device 8 of the management server 80, and the conversion device 23 generates the identification code DC online using the code generation program P2.

[0021] The ticket issuing device 24 is a printing machine that issues a replacement ticket QT that displays an identification code DC. Specifically, the ticket issuing device 24 issues a replacement ticket QT with the identification code DC printed on its face, for example, on the surface of a paper medium. This allows the user US to obtain the replacement ticket QT through the same process as an automatic fare adjustment machine, thereby reducing the workload of the user US. The issued replacement ticket QT has the same ticket validity as the magnetic ticket MT, or ticket validity with added validity through a fare adjustment process, etc. (updated ticket validity).

[0022] The fare processing device 30 performs fare adjustment processing based on the ticket validity of the magnetic ticket MT read by the reader 21. This allows the ticket change device 100 to perform both fare adjustment processing and other processing in one device. In other words, the ticket change device 100 can be incorporated into existing automatic fare adjustment machines. The ticket validity is checked by the management server 80, and the fare processing device 30 performs appropriate fare adjustment processing based on the check results. The fare processing device 30 receives coins or bills from the user US, identifies the type and number of coins or bills, and returns the appropriate type and number of coins or bills. The fare processing device 30 may also be compatible with prepaid cards, credit cards, etc.

[0023] As described above, when the ticket validity is insufficient at the destination station, the ticket change device 100 settles the missing fare and issues a replacement ticket QT that is valid at the destination station. The replacement ticket QT after settlement has its ticket validity updated, and is a ticket with new ticket validity that can pass through the ticket gate 200 at the destination station.

[0024] The ticket change device 100 may omit checking the ticket validity at the management server 80. In this case, the fare processing device 30 performs settlement processing etc. based on the ticket validity read by the reader 21.

[0025] As described above, the storage device 40 stores a program that operates the ticket change device 100, enabling the device to be operated. The storage device 40 stores a database necessary for the operation of the ticket change device 100. The storage device 40 is a non-volatile storage medium or non-temporary storage medium NM such as a hard disk or flash memory, and stores the ticket change program P1 and other programs that the control device 10 uses to execute various information processes. The ticket change program P1 and other programs may be provided by being stored in a storage medium other than the storage device 40, or may be provided by downloading them from a server. The storage device 40 also temporarily stores data necessary for the control device 10 to execute arithmetic processing.

[0026] The display device 50 is, for example, a display, and provides the user US with information related to ticket changes and fare adjustments.

[0027] The operation device 60 is, for example, an operation key or an operation button, and receives a response from the user US. After the user US inserts the magnetic ticket MT into the reader 21 of the ticket processing device 20, the user operates the operation device 60 to issue a replacement ticket QT. The operation device 60 may also serve as the display device 50, for example, as a touch panel.

[0028] The communication device 70 enables communication with the management server 80 via a communication network NT, either wired or wirelessly.

[0029] The management server 80 is a computer that operates under the management of a system administrator, and manages the operation of the ticket change device 100 and the ticket gates 200. The management server 80 is communicably connected to the ticket change device 100 via the communication device 70 and the communication network NT. The management server 80 is also communicably connected to the ticket gates 200 via the communication network NT. Although a single ticket change device 100 is shown in FIG. 1 and other figures, multiple ticket change devices 100 and ticket gates 200 may be operated and managed collectively.

[0030] A series of operations performed by the ticket change device 100 will be described with reference to FIG.

[0031] First, the control device 10 of the ticket change device 100 accepts a magnetic ticket MT (step S11). Specifically, when the user US inserts the magnetic ticket MT into the insertion slot 21a of the reader 21, the control device 10 reads and executes the ticket change program P1. When the ticket change program P1 is executed, the control device 10 performs the following operations.

[0032] The control device 10 operates the reader 21 to read the ticket validity of the magnetic ticket MT (step S12). Specifically, the reader 21 obtains the ticket validity from the magnetic information recorded on the magnetic ticket MT. The read magnetic ticket MT is collected by the collection device 22.

[0033] Next, the control device 10 inquires of the management server 80 about the validity of the ticket read in step S12 (step S13). Specifically, the control device 10 communicates with the management server 80 via the communication device 70 and inquires of the management server 80 about whether the ticket is valid. When inquiring, the control device 10 transmits the ticket identification number and the ticket validity (all or part of the ticket information). Here, a valid ticket means that the section, section fare, date, etc. on the ticket match the actual entry / exit section, section fare, date, etc. If there is no underpaid fare and the ticket is valid, the management server 80 transmits information indicating that there is no underpaid fare to the control device 10 of the ticket change device 100. If there is a underpaid fare, the management server 80 transmits information regarding the underpaid fare to the control device 10.

[0034] If there is an underpayment of fare (Y in step S14), the control device 10 operates the fare processing device 30 to perform the settlement process (step S15). After step S15, the control device 10 changes the ticket validity at the time of reading to a valid ticket validity (step S16). The control device 10 transmits the settlement result to the management server 80.

[0035] After step S16, or if there is no fare deficiency (N in step S14), the control device 10 operates the conversion device 23 to convert the ticket validity into an identification code DC (step S17). Specifically, the conversion device 23 queries the management server 80 about the generation of an identification code DC, and generates an identification code DC online for the ticket identification number and ticket validity.

[0036] Finally, the control device 10 operates the ticket issuing device 24 to issue a replacement ticket QT (step S18).

[0037] The ticket change device 100 described above changes a magnetic ticket MT into a replacement ticket QT bearing an identification code DC, enabling smooth ticket gate processing even at stations where magnetic tickets MT have been discontinued. Since the ticket validity is read from the magnetic information on the magnetic ticket MT, the ticket validity can be accurately extracted and converted into an identification code DC. The ticket change device 100 can be used not only as a standalone device, but also as a component of an existing automatic fare adjustment machine.

[0038] Second Embodiment An example of the ticket change device according to the second embodiment will be described below with reference to Fig. 4. In the second embodiment, the same matters as in the first embodiment will not be described again.

[0039] In the ticket change device 100 of this embodiment, the conversion device 23 of the ticket processing device 20 generates an identification code DC based on predefined rules. A code generation program P2 for generating the identification code DC is stored in the storage device 40, and the conversion device 23 generates the identification code DC offline using the code generation program P2.

[0040] In this embodiment, the management server 80 may be omitted. In this case, the communication device 70 can be omitted. Furthermore, when the management server 80 is omitted, no inquiry is made to the management server 80, and the ticket change device 100 generates the identification code DC and performs settlement processing, etc., based on the ticket validity read by the reader 21.

[0041] Third Embodiment An example of a ticket change device according to the third embodiment will be described below with reference to Fig. 5. In the third embodiment, descriptions of matters that are the same as those in the first embodiment will be omitted.

[0042] The ticket change device 100 of this embodiment is applied to an attendant-operated terminal 300 carried by a train crew member, a station attendant, etc. In this embodiment, instead of reading magnetic information, the ticket change device 100 photographs the face TS (see FIG. 1) of the magnetic ticket MT with the reading device 21 of the attendant-operated terminal 300, and obtains the ticket validity from the obtained image data.

[0043] The ticket change device 100 comprises a control device 10, a ticket processing device 20, a fare processing device 30, a storage device 40, a display device 50, an operation device 60, and a communication device 70. The ticket processing device 20 comprises a reading device 21, a conversion device 23, and a ticket issuing device 24. The ticket change device 100 is capable of communicating with an external management server 80 via the communication device 70. The settlement process performed by the fare processing device 30 in this embodiment mainly involves calculating the fare deficiency, etc. Note that in this embodiment, the ticket change device 100 may omit the fare processing device 30.

[0044] In this embodiment, the attendant-operated terminal 300 has the reading device 21 and the conversion device 23 of the ticket processing device 20. The ticket issuing device 24 is a printing machine or the like that is provided separately from the attendant-operated terminal 300. Note that when ticket gate processing is performed at a ticket window or the like in a station, the ticket change device 100 may omit the ticket issuing device 24.

[0045] The reader 21 reads the ticket validity from the image data of the face TS of the magnetic ticket MT. The reader 21 has a camera 21b and an image processing device 21c. The camera 21b photographs the face TS of the magnetic ticket MT.

[0046] The image processing device 21c processes the image data of the face TS of the magnetic ticket MT to extract the ticket validity. The image processing device 21c obtains the ticket validity by, for example, performing OCR (Optical Character Recognition) processing on the characters printed on the face TS. The image processing device 21c analyzes the arrangement and size of characters, etc. on the face TS and the text information read by OCR based on a ticket validity template to extract the ticket validity. The ticket validity template is set for each operator and includes the arrangement and size of characters, etc. on the face TS, keywords required for extraction, etc. The ticket validity template can be read from the storage device 40 or the management server 80 based on keywords such as the operator name and ticket type. The method of extracting the ticket validity can be changed as appropriate and is not limited to being based on a template, but may also be one that uses machine learning.

[0047] The display device 50 is, for example, a display, and provides information related to ticket changes and fare adjustments to train crew or station staff.

[0048] The operation device 60 is, for example, an operation key, an operation button, etc., and receives responses from the crew or station staff. The operation device 60 may also be used as the display device 50, for example, as a touch panel, etc.

[0049] The communication device 70 enables communication with the management server 80 and the ticket issuing device 24 via the communication network NT, either wired or wirelessly. The communication method between the attendant-operated terminal 300 and the ticket issuing device 24 may be different from the communication method between the attendant-operated terminal 300 and the management server 80. The communication method between the attendant-operated terminal 300 and the ticket issuing device 24 may be, for example, short-range wireless communication or wireless LAN.

[0050] 〔others〕 The present invention is not limited to the above-described embodiment, and can be embodied in various forms without departing from the spirit and scope of the present invention.

[0051] The ticket change device 100 may omit the fare processing device 30. In this case, the ticket change device 100 does not perform the settlement process, but simply converts the ticket validity of the magnetic ticket MT into an identification code DC, and issues a replacement ticket QT.

[0052] The method of checking the validity of a ticket at the ticket change device 100 or the ticket gate 200 can be changed as needed. For example, the validity of a ticket is recorded in a local server at a station that is periodically synchronized with the management server 80, and when checking, the validity of the ticket is checked against that local server.

[0053] The replacement ticket QT is not limited to being printed on paper or the like, but may also be displayed on the mobile terminal of the user US. In this case, the ticket issuing device 24 generates information (for example, a URL, a two-dimensional code, etc.) to be sent to the mobile terminal.

[0054] The ticket change device 100 may have the conversion device 23 provided in the management server 80 . [Explanation of symbols]

[0055] 10...control device, 20...ticket processing device, 21...reading device, 22...collection device, 23...conversion device, 24...ticket issuing device, 30...fare processing device, 40...storage device, 50...display device, 60...operation device, 70...communication device, 80...management server, 100...ticket change device, 200...ticket gate, 300...attendant operation terminal, DC...identification code, MT...magnetic ticket, NM...non-transitory storage medium, NT...communication network, P1...ticket change program, P2...code generation program, QT...replacement ticket, TS...ticket face

Claims

1. A reader that reads the validity of a magnetic ticket from the magnetic information on the magnetic ticket; a conversion device for converting the ticket validity into an identification code; a ticket issuing device that issues a replacement ticket displaying the identification code; Equipped with Ticket changing device.

2. The identification code is a two-dimensional code. The ticket change device according to claim 1.

3. the ticket issuing device issues the replacement ticket with the identification code printed on its face; The ticket change device according to claim 1.

4. a fare processing device that performs settlement processing based on the ticket validity, The ticket change device according to claim 1.

5. the conversion device generates the identification code using the result of the inquiry to the management server; The ticket change device according to claim 1.

6. the conversion device generates the identification code based on predefined rules; The ticket change device according to claim 1.

7. reading the ticket validity from the magnetic information on the magnetic ticket by a reader; converting the ticket validity into an identification code by a conversion device; issuing a replacement ticket displaying the identification code by a ticket issuing device; The control device executes Ticket change program.

Images