Ticket management program, ticket management server, and ticket management method

Abstract

To prevent ticket fraud without requiring extra effort. [Solution] The ticket application is a program executed on a mobile terminal, and causes the mobile terminal to perform the following steps: first step (S512) to identify the location information of the mobile terminal; second step (S516) to display unreadable information on the mobile terminal, indicating that the two-dimensional code used for using the transportation is unusable, when predetermined conditions are met such that an operation for using a ticket usable on a predetermined section of the transportation is accepted (YES in S511) and the identified location information is the place where the ticket will start to be used (YES in S112); and third step (S525) to display a code image on the mobile terminal in place of the unreadable information, when the unreadable information is displayed (YES in S521) and a predetermined operation is detected (YES in S524).

Description

Technical Field

[0001] This disclosure relates to a ticket management program, a ticket management server, and a ticket management method, and particularly to a ticket management program executed on a mobile terminal, a ticket management server that manages tickets usable in a predetermined section of a transportation facility, and a ticket management method that manages tickets usable in a predetermined section of a transportation facility.

Background Art

[0002] Conventionally, there has been a technology for preventing fraud of ticket images for transportation facilities (such as railways and buses) used in smartphones and the like (see, for example, paragraph

[0034] of Patent Document 1). Patent Document 1 describes the following content. When the operation button added to the official ticket is tapped according to the admission determination code announced by the staff at the entrance gate, an image different from the original official ticket image is displayed on the condition that the input operation has been correctly performed. If the staff determines that this display change is appropriate, admission will be permitted.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the technology of Patent Document 1, the staff has to tell the admission determination code to the person trying to enter at the entrance gate one by one, which causes a lot of trouble for the staff.

[0005] This disclosure has been made to solve the above-described problems, and an object thereof is to provide a ticket management program, a ticket management server, and a ticket management method capable of preventing ticket fraud without much trouble.

Means for Solving the Problems

[0006] The ticket management program disclosed herein is a program executed on a mobile terminal, and causes the mobile terminal to perform the following steps: first step of identifying the location information of the mobile terminal; second step of displaying unreadable information on the mobile terminal, which indicates a code image used for using the transportation in an unusable manner, when an operation for using a ticket usable on a predetermined section of the transportation is accepted and predetermined conditions are met such that the identified location information is the place where the ticket is to be used; and third step of displaying a code image on the mobile terminal in place of the unreadable information, when the unreadable information is displayed and a predetermined operation is detected.

[0007] With this configuration, the location information of the mobile device is the starting location of the ticket, and when a predetermined operation is detected, the code image used for using public transport is displayed on the mobile device in place of unreadable information that would otherwise render the code image unusable. As a result, a ticket management program can be provided that can prevent ticket fraud without requiring any extra effort.

[0008] The predetermined operation may be a shake or swipe operation on the mobile device. With such a configuration, the code image can be displayed on the mobile device with a simple operation.

[0009] The second step may include a step of determining the location information using location-determining information obtained through communication between the mobile device and the outside world. With such a configuration, the location information of the mobile device can be appropriately determined.

[0010] The ticket management program may also cause the mobile terminal to perform a fourth step in which, after a predetermined period of 10 seconds or less has elapsed since the display of the code image began in the third step, the code image is changed to an unusable form or the code image is invalidated.

[0011] This configuration makes it possible to prevent others from reading the code image on other mobile devices and using it illegally after the code image has been displayed.

[0012] According to other aspects of this disclosure, the ticket management server is a server that manages tickets usable on a predetermined section of a transportation system, and comprises a processor and a communication unit that communicates with a mobile terminal. The processor receives through the communication unit that an operation for using a ticket has been accepted by the mobile terminal, and if the location information of the mobile terminal received through the communication unit is the place where the ticket will be used, it transmits unreadable information, which indicates that the code image used for using the transportation system is unusable, to the mobile terminal via the communication unit in order to display it on the mobile terminal. If the mobile terminal is displaying unreadable information and the server receives through the communication unit that a predetermined operation has been detected, it transmits a code image to the mobile terminal via the communication unit in place of the unreadable information.

[0013] This configuration allows for the provision of a ticket management server that can prevent ticket fraud without requiring extra effort.

[0014] In another aspect of this disclosure, a ticket management method is a method for managing tickets usable on a designated section of a transportation system, comprising the steps of: generating a code image to be used for the use of the transportation system; generating unreadable information that indicates the code image as unusable; displaying the unreadable information on a mobile terminal when an operation for using the ticket is accepted and the location information of the mobile terminal is the place where the ticket will be used; and displaying a code image on the mobile terminal in place of the unreadable information when the unreadable information is displayed on the mobile terminal and a designated operation is detected.

[0015] This configuration provides a ticket management method that can prevent ticket fraud without requiring extra effort. [Effects of the Invention]

[0016] This disclosure provides a ticket management program, a ticket management server, and a ticket management method that can prevent ticket fraud without requiring extra effort. [Brief explanation of the drawing]

[0017] [Figure 1] This diagram shows a schematic configuration of the ticket management system according to this embodiment. [Figure 2] This flowchart shows the processing flow of the ticket application program and the ticket server in the first embodiment. [Figure 3] This diagram shows the screen transitions displayed on the mobile device in this embodiment. [Figure 4] This flowchart shows the processing flow of the ticket application program and the ticket server in the second embodiment. [Figure 5] This is a flowchart showing the processing flow of the ticket application program and the ticket server in the third embodiment. [Modes for carrying out the invention]

[0018] The embodiments of this disclosure will be described in detail below with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals, and their descriptions will not be repeated.

[0019] FIG. 1 is a diagram showing an outline of the configuration of the ticket management system 1 according to this embodiment. Referring to FIG. 1, the ticket management system 1 includes a server 100, mobile terminals 500A and 500B (hereinafter also generically referred to as "mobile terminal 500"), an automatic ticket gate 200, and a beacon device 700. The server 100 manages tickets that can be used in a predetermined section of a transportation facility (e.g., railway, bus). The plurality of mobile terminals 500 each have a display which is one of the output units 540 that display a two-dimensional code 545 used to utilize the ticket at the transportation facility, and are used by a plurality of users 10. The ticket is, for example, a one-way ticket, a round-trip ticket, or a ticket with unlimited rides for a predetermined period. The automatic ticket gate 200 maintains the flap door 260 in an open state when a proper two-dimensional code 545 displayed on the display 541 of the mobile terminal 500B by the user 10 is held up to the reading unit 230. Thereby, the user 10 can pass through the automatic ticket gate 200. The beacon device 700 is used to identify near which of the automatic ticket gates 200 the user 10's mobile terminal 500 is located. The ticket management system 1 may not include some devices such as the beacon device 700.

[0020] The server 100, the mobile terminal 500, the automatic ticket gate 200, and the beacon device 700 can communicate with each other via a communication network 900. The communication network 9 is a public network such as a LAN (Local Area Network), a VPN (Virtual Private Network), and the Internet, a public switched telephone network, or a public wireless LAN.

[0021] The server 100 includes a CPU (Central Processing Unit) 110, a memory 120, a mass storage device 150, and a communication unit 190. The CPU 110, the memory 120, the mass storage device 150, and the communication unit 190 are connected to each other via a bus.

[0022] Memory 120 includes RAM (Random Access Memory), which is used as a working area necessary for the CPU 110 to execute programs, and ROM (Read Only Memory), which stores programs to be executed by the CPU 110. Furthermore, programs and data for executing predetermined processes are read from ROM and stored in the RAM.

[0023] The mass storage device 150 consists of a hard disk drive, a DVD (Digital Versatile Disk) drive, or a memory card reader / writer. The mass storage device 150 records predetermined data or programs received from the CPU 110 onto the recording medium 151 magnetically, optically, or electrically, or reads them from the recording medium 151 and transfers them to the CPU 110. The recording medium 151 can be a magnetic disk such as a hard disk, an optical disk such as a DVD-ROM (Digital Versatile Disk Read Only Memory), a memory card, or a USB (Universal Serial Bus) memory.

[0024] The communication unit 190 sends and receives data to and from external devices (for example, a mobile terminal 500, an automatic ticket gate 200) via the communication network 900. The communication unit 190 transmits data received from devices connected to the bus, such as the CPU 110, to the outside, and passes data received from the outside to devices connected to the bus, such as the CPU 110.

[0025] The CPU 110 controls the memory 120, the communication unit 190, and the mass storage device 150, executes predetermined processing according to the programs and data stored in the memory 120, processes data input from the communication unit 190 and the mass storage device 150, and stores the processed data in the memory 120, outputs it to other devices from the communication unit 190, or stores it in the recording medium 151 of the mass storage device 150.

[0026] In this embodiment, the server 100 does not include an operation unit and a display unit, but is not limited to this and may include the configuration of an operation unit and a display unit. The operation unit may include a keyboard and a mouse, and operation signals indicating the operation content input to the server 100 by operating the keyboard and mouse of the operation unit may be passed to the CPU 110. The display unit may include a display such as an LCD (Liquid Crystal Display), and the display may display an image corresponding to the image data received from the CPU 110.

[0027] The mobile terminal 500 includes a CPU 510, a memory 520, an operation unit 530, an output unit 540, a GNSS (Global Navigation Satellite System) receiver 560, a short-range communication unit 570, and a wireless communication unit 590. The CPU 510, memory 520, operation unit 530, output unit 540, GNSS receiver 560, short-range communication unit 570, and wireless communication unit 590 are connected to each other by a bus. The CPU 510 and memory 520 are the same as the CPU 110 and memory 120 of the server 100 described above, so a redundant explanation will not be repeated.

[0028] The control unit 530 includes a touch panel and operation buttons for inputting numbers, letters, and other characters such as phone numbers and various data. The control unit 530 may also include parts for other operations (for example, a microphone). When the control unit 530 is operated by the user, an operation signal corresponding to the operation is transmitted from the control unit 530 to the CPU 510. The CPU 510 controls various parts of the mobile terminal 500 in response to the operation signal from the control unit 530.

[0029] The output unit 540 includes a display 541 and a speaker. The display 541 is formed integrally with the aforementioned touch panel. The output unit 540 is controlled by the CPU 510 to display the image signal and audio signal, which are converted by the CPU 510 from information received by the wireless communication unit 590 or information stored in the memory 520, as an image on the display 541 and output as audio from the speaker, respectively.

[0030] The GNSS receiver 560 is controlled by the CPU 510 to determine the current position and altitude of the device based on the radio waves of the navigation signal from the positioning satellite 600, and outputs information indicating the current position and altitude to the CPU 510 in accordance with the CPU 510's request.

[0031] The short-range communication unit 570 is controlled by the CPU 510 and wirelessly transmits data to nearby devices based on short-range wireless communication standards such as Bluetooth® or Wi-Fi.

[0032] The wireless communication unit 590 is controlled by the CPU 510 and receives wireless signals from the other mobile terminal 500 or landline telephone of the person making the call via the public line and antenna, converts the received wireless signals into voice signals, transmits the converted voice signals to a speaker, and converts voice signals from the microphone into wireless signals and transmits them to the other mobile terminal 500 or landline telephone of the person making the call via the antenna and the telecommunications carrier's communication equipment.

[0033] Furthermore, the wireless communication unit 590, controlled by the CPU 510, receives wireless signals via public lines and antennas from data communication-capable devices, such as a server 100 or other mobile terminal 500, converts the received wireless signals into data, stores the converted data in memory 520, or transmits it to output unit 540 for display, and also converts the data to be transmitted into wireless signals and transmits them to the data communication destination server 100 or other mobile terminal 500 via antennas and telecommunications carrier communication equipment.

[0034] Although the mobile terminal 500 has been described as a portable device such as a smartphone, it is not limited to this and may also be a wearable device such as a smartwatch, a PC (Personal Computer), or other information processing device such as a tablet.

[0035] The automatic ticket gate 200 includes a CPU 210, a memory 220, a reading unit 230, a flap door 260, and a communication unit 290. The CPU 210, memory 220, and communication unit 290 are the same as the CPU 110, memory 120, and communication unit 190 of the server 100 described above, so redundant explanations will not be repeated.

[0036] The reading unit 230 has a code reader that reads the two-dimensional code 545 displayed on the display 541 of the output unit 540 of the mobile terminal 500 when the two-dimensional code 545 is held over it, and outputs the image data of the read two-dimensional code 545 to the CPU 210. The CPU 210 decodes the two-dimensional code 545 and either stores it in the memory 220 or transmits it to an external device such as a server 100 via the communication unit 290.

[0037] The flap door 260 is controlled by the CPU 210 to open and close, and if the ticket indicated by the decoded data of the two-dimensional code 545 is invalid, it remains closed to prevent the user 10 from passing through. If the ticket is valid, it remains open at least until the user 10 has passed through. The flap door 260 may be a normally open type that closes when the ticket is invalid, or a normally closed type that opens when the ticket is valid.

[0038] The beacon device 700 includes a CPU 710, a memory 720, a short-range communication unit 770, and a wireless communication unit 790. The CPU 710, memory 720, short-range communication unit 770, and wireless communication unit 790 are the same as those of the mobile terminal 500, respectively (CPU 510, memory 520, short-range communication unit 570, and wireless communication unit 590), so redundant explanations will not be repeated.

[0039] Previously, there were technologies to prevent fraudulent use of ticket images for transportation services (such as trains and buses) used on mobile devices like the 500 series. For example, there was a technology like this: When a user tapped an operation button attached to their official ticket according to an entry verification code given by an attendant at the entrance gate, a different image from the original official ticket would be displayed, provided that the input operation was performed correctly. If the attendant determined that this display change was legitimate, entry would be permitted. However, with this technology, attendants had to tell each person trying to enter the entry verification code at the entrance gate, which was time-consuming for the attendants.

[0040] Therefore, the ticket management program executed on the mobile terminal 500 causes the mobile terminal 500 to perform the following steps: first step of identifying the location information of the mobile terminal 500; second step of displaying unreadable information on the mobile terminal 500, indicating that the two-dimensional code 545 used for using the transportation is unusable, when an operation for using a ticket usable in a predetermined section of the transportation system is accepted and predetermined conditions are met such that the identified location information is the place where the ticket is to be used; and third step of displaying the two-dimensional code 545 on the mobile terminal 500 in place of the unreadable information, when the unreadable information is displayed and a predetermined operation is detected.

[0041] As a result, when the location information of the mobile terminal 500 indicates the starting location of the ticket, and a predetermined operation is detected, the two-dimensional code 545 used for using public transportation is displayed on the mobile terminal 500 instead of unreadable information indicating that the two-dimensional code 545 cannot be used. Consequently, ticket fraud can be prevented without any extra effort.

[0042] [First Embodiment] Figure 2 is a flowchart showing the processing flow of the ticket application program (hereinafter also referred to as "app") and the ticket server in the first embodiment. Referring to Figure 2, the ticket app is installed on the mobile terminal 500 and pre-stored in the memory 520. The processing of the ticket app is periodically called and executed by the CPU 510 of the mobile terminal 500 from a higher-level process. The processing of the ticket server is periodically called and executed by the CPU 110 of the server 100 from a higher-level process. The ticket gate processing is periodically called and executed by the CPU 210 of the automatic ticket gate 200 from a higher-level process.

[0043] When the ticket application is executed on the mobile terminal 500, the CPU 510 determines whether or not an operation to start using the ticket has been received by the operation unit 530 (step S511). Note that the operation is not limited to operations received by the touch panel or operation buttons of the operation unit 530, such as touch operations, but may also be voice operations received by the microphone of the operation unit 530.

[0044] Figure 3 is a diagram showing the screen transitions displayed on the mobile terminal 500 in this embodiment. Referring to Figure 3(A), when the ticket application is executed, the display 541 of the output unit 540 of the mobile terminal 500 displays a list of tickets owned by the user 10 of the mobile terminal 500. The list of owned tickets displays ticket information 542, including the name of the ticket and a button to start using the ticket, for each ticket owned by the user 10. When the user 10 taps this ticket start button, the operation to start using the ticket is accepted by the CPU 510.

[0045] Referring to Figure 3(B), when the "Start Use" button is tapped, a pop-up display 543 confirming the start of use of the ticket is shown. When the "OK" button is tapped, the operation to start use of the ticket is confirmed.

[0046] Returning to Figure 2, if the CPU 510 determines that the operation to start using the ticket has been accepted by the mobile terminal 500 (YES in step S511), the CPU 510 acquires the location information of the mobile terminal 500 and controls the wireless communication unit 590 to transmit the acquired location information, along with the ID of the ticket to be used, to the server 100 (step S512). The memory 720 of the beacon device 700 has information stored in advance to identify the station or stop where the beacon device 700 is installed. The CPU 510 may also acquire the location information of the mobile terminal 500 by communicating with the short-range communication unit 770 of the beacon device 700 using the short-range communication unit 570 and receiving information to identify the station or stop where the beacon device 700 is installed. Alternatively, instead of communicating with the beacon device 700, the CPU 510 may acquire the location information of the mobile terminal 500 using the current position from the GNSS receiver unit 560, which is determined using signals from the positioning satellite 600.

[0047] In the server 100, the CPU 110 determines whether the ticket ID and location information have been received from the mobile terminal 500 by the communication unit 190 (step S111). If it is determined that the ticket ID and location information have been received (YES in step S111), the CPU 110 determines whether the location of the mobile terminal 500 indicated by the location information is a place where the ticket indicated by the ticket ID can be used (for example, a station or bus stop at the start or within the section) (step S112). Places where the ticket can be used are places within the usable section defined by the ticket (for example, stations, bus stops). It is also possible to determine whether it is within the period during which the ticket can be used (for example, the validity period of the ticket, or the period from when the use of the ticket begins until the period during which the ticket can be used has elapsed). If the CPU 110 determines that the ticket is valid at the location (YES in step S112), it controls the communication unit 190 to generate a two-dimensional code 545 for using the ticket and transmit it to the mobile terminal 500 (step S113).

[0048] If the mobile terminal 500 determines that the operation to start using the ticket has not been accepted (NO in step S511), or after step S512, the CPU 510 determines whether or not the two-dimensional code 545 has been received from the server 100 by the wireless communication unit 590 (step S515). If the CPU 510 determines that the two-dimensional code 545 has been received (YES in step S515), the CPU 510 controls the display 541 of the output unit 540 to display the received two-dimensional code 545 in an unusable, damaged state (step S516).

[0049] Moving on to Figure 3, and referring to Figure 3(C), on the display 541 of the output unit 540 of the mobile terminal 500, a toggle switch 546, which is operated by moving the slide part 547 left or right, is displayed above the received two-dimensional code 545, causing the two-dimensional code 545 to be displayed in a missing state. In addition, a pop-up display 544 is displayed on the display 541 indicating how to clear this missing state and display the two-dimensional code 545. In this case, the pop-up display 544 prompts the user to slide the slide part 547 of the toggle switch 546 to the right or shake the mobile terminal 500 just before passing through the automatic ticket gate 200 in order to clear the missing state of the two-dimensional code 545.

[0050] Returning to Figure 2, if the mobile terminal 500 determines that the two-dimensional code 545 has not been received (NO in step S515), or after step S516, the CPU 510 determines whether or not the two-dimensional code 545 is being displayed in a missing state (step S521). If it determines that it is being displayed in a missing state (YES in step S521), the CPU 510 determines whether or not the first period has elapsed since the start of displaying the two-dimensional code 545 in a missing state (step S522). The first period is a predetermined period of less than a few tens of minutes, which in this case is 10 minutes.

[0051] If the CPU 510 determines that the first period has elapsed (YES in step S522), it returns to a different screen from the display with the missing QR code 545 shown in Figure 3(C), in this case the owned ticket list screen shown in Figure 3(A) (step S523).

[0052] If it is determined that the first period has not elapsed (NO in step S522), the CPU 510 determines whether a predetermined operation (in this case, the rightward slide operation and shake operation described in Figure 3(C)) has been performed (step S524). If it is determined that a predetermined operation has been performed (YES in step S524), the CPU 510 controls the display 541 of the output unit 540 to display the two-dimensional code 545 in a readable and normal state (step S525).

[0053] Moving on to Figure 3, and referring to Figure 3(D), the two-dimensional code 545 is displayed correctly on the display 541 of the output unit 540 of the mobile terminal 500. A pop-up display 548 is also displayed on the display 541 prompting the user to hold the two-dimensional code 545 over the reader unit 230 of the automatic ticket gate 200 and pass through the automatic ticket gate 200.

[0054] Returning to Figure 2, in the automatic ticket gate 200, the CPU 210 determines whether the two-dimensional code 550 displayed on the mobile terminal 500 has been held over the reader 230 and whether the two-dimensional code 550 has been read by the reader 230 (step S211). If it is determined that the two-dimensional code 545 has been read (YES in step S211), the CPU 210 controls the communication unit 290 to send the decoded information of the read two-dimensional code 545 to the server 100 (step S212). Note that the information decoded from the two-dimensional code 545 is not limited to being sent directly from the automatic ticket gate 200 to the server 100, but may also be sent from the automatic ticket gate 200 to the server 100 via the user 10's mobile terminal 500.

[0055] In the server 100, the CPU 110 determines, via the communication unit 190, whether or not decoded information of the two-dimensional code 545 has been received from the automatic ticket gate 200 (or, as in the modified example above, from the mobile terminal 500 of user 10 if the information decoded from the two-dimensional code 545 is transmitted from the automatic ticket gate 200 to the server 100 via the mobile terminal 500 of user 10) (step S131). If it is determined that decoded information has been received (YES in step S131), the CPU 110 determines whether or not the ticket indicated by the two-dimensional code 545 is being used properly (step S132). For example, if the place where the ticket was used is an usable location, in this case a location within the usable section defined by the ticket (for example, a station, a bus stop), and within the period during which the ticket can be used (for example, the period from when the ticket is used until the period during which the ticket can be used has elapsed), the CPU 110 determines that the ticket is being used properly.

[0056] If the CPU 110 determines that the ticket is being used correctly (YES in step S132), it registers in the memory 120 or mass storage device 150 that the use of the ticket has begun (step S133). The CPU 110 then controls the communication unit 190 to send information to the automatic ticket gate 200 that permits user 10 to pass through the automatic ticket gate 200 (step S134). In the modified example described above, if the information obtained by decoding the two-dimensional code 545 is sent from the automatic ticket gate 200 to the server 100 via the user's mobile terminal 500, the CPU 110 controls the communication unit 190 to send information to the automatic ticket gate 200 via the mobile terminal 500 that permits user 10 to pass through the automatic ticket gate 200. If it is determined that decryption information has not been received (NO in step S131), or if it is determined that the ticket has not been used properly (NO in step S132), or after step S134, the CPU 110 returns the process to be executed to the higher-level process that called this process.

[0057] If the automatic ticket gate 200 determines that the two-dimensional code 545 has not been read (NO in step S211), or after step S212, the CPU 210 determines, via the communication unit 290, whether permission information for the user 10 to pass through the automatic ticket gate 200 has been received from the server 100 (or, as in the modified example above, the mobile terminal 500 if information allowing the user 10 to pass through the automatic ticket gate 200 is transmitted to the automatic ticket gate 200 via the mobile terminal 500) (step S221). If permission information has been received (YES in step S221), the CPU 210 controls the flap door 260 to keep it open until the user 10 passes through the automatic ticket gate 200 (step S222). If permission information has not been received (NO in step S221), or after step S222, the CPU 210 returns the processing to be executed to the higher-level processing that called this process.

[0058] If the mobile terminal 500 determines that the two-dimensional code 545 is not being displayed in a missing state (NO in step S521), if it determines after step S523 that the predetermined operation has not been performed (NO in step S524), or after step S525, the CPU 510 determines whether the two-dimensional code 545 is being displayed in a normal state (step S531). If it determines that it is being displayed in a normal state (YES in step S531), the CPU 510 determines whether a second period has elapsed since the start of the normal display of the two-dimensional code 545 (step S532). The second period is a predetermined period of several seconds or more and less than several tens of seconds, which in this case is 10 seconds.

[0059] If the CPU 510 determines that the second period has elapsed (YES in step S532), it returns to a different screen from the normal display of the two-dimensional code 545 shown in Figure 3(D), in this case the ticket list screen shown in Figure 3(A) (step S533). Alternatively, it may return to a display showing the two-dimensional code 545 in a missing state, as a different screen from the normal display of the two-dimensional code 545. Furthermore, even if the two-dimensional code 545 is held over the automatic ticket gate 200 while it is still displayed in the normal state, it may be made unusable (specifically, in a state where it is determined to be improper use in step S132). If the CPU 510 determines that the two-dimensional code 545 is not currently displayed in the normal state (NO in step S531), if the second period has not elapsed (NO in step S532), or after step S533, it returns the process to be executed to the higher-level process that called this process.

[0060] Moving on to Figure 3, and referring to Figure 3(E), after user 10 has properly passed through the automatic ticket gate 200, the list of tickets held displayed on the display 541 of the output unit 540 of the mobile terminal 500 includes, in addition to the ticket information 542 that has not been used, ticket information 542A that includes the name of the ticket and information indicating that the ticket is in use.

[0061] [Second Embodiment] In the first embodiment, an example of unreadable information indicating that the two-dimensional code 545 used for using public transportation is unusable is shown when a toggle switch 546 is displayed on the two-dimensional code 545, resulting in a partially missing two-dimensional code 545, which is generated when the application is executed on the mobile terminal 500. In the second embodiment, the unreadable information is generated on the server 100.

[0062] Figure 4 is a flowchart showing the processing flow of the ticket application program and the ticket server in the second embodiment. Referring to Figure 4, the ticket application processing is periodically called and executed by the CPU 510 of the mobile terminal 500 from a higher-level process. The ticket server processing is periodically called and executed by the CPU 110 of the server 100 from a higher-level process. In Figure 4, the processing with the same step numbers as in Figure 2 of the first embodiment is the same processing as in Figure 2, so redundant explanations will not be repeated.

[0063] Steps S511 and S512, and steps S111 and S112 are the same as in Figure 2 of the first embodiment. If it is determined that the ticket is valid at the location (YES in step S112), the CPU 110 generates a two-dimensional code 545 for using the ticket indicated by the ticket ID and stores it in the memory 120 (step S113A). The CPU 110 generates a missing code that renders the created two-dimensional code 545 unusable and controls the communication unit 190 to send it to the mobile terminal 500 (step S114).

[0064] Returning to Figure 3 and referring to Figure 3(F), the missing code is, for example, an image where the blank image 549 is on top of the two-dimensional code 545. However, it is not limited to this, and the missing code may be any other information that indicates the two-dimensional code 545 in an unusable manner.

[0065] If the mobile terminal 500 determines that the operation to start using the ticket has not been accepted (NO in step S511), or after step S512, the CPU 510 determines whether or not a missing code has been received from the server 100 by the wireless communication unit 590 (step S517). If it determines that a missing code has been received (YES in step S517), the CPU 510 controls the display 541 of the output unit 540 to display the received missing code (step S518). The missing code is displayed on the display screen shown in Figure 3(C) with the image of the two-dimensional code 545, which is displayed in a missing state, replaced with the image in Figure 3(F).

[0066] Steps S521 to S524 are the same as in Figure 2. If it is determined that a predetermined operation has been performed (YES in step S524), the CPU 510 acquires the location information of the mobile terminal 500 and controls the wireless communication unit 590 to transmit the acquired location information, along with the ID of the ticket to be used, to the server 100 (step S526), ​​similar to step S512 in Figures 2 and 4.

[0067] In the server 100, the CPU 110 determines whether the ticket ID and location information have been received from the mobile terminal 500 by the communication unit 190 (step S121). If the CPU 110 determines that the ticket ID and location information have been received (YES in step S121), it determines, similar to step S112 in Figures 2 and 4, whether the location of the mobile terminal 500 indicated by the location information is a place where the ticket indicated by the ticket ID can be used (for example, a station or bus stop) (step S122). If the CPU 110 determines that the location is a place where the ticket can be used (YES in step S122), it controls the communication unit 190 to send the two-dimensional code 545 stored in the memory 120 in step S113A to the mobile terminal 500 (step S123).

[0068] If the mobile terminal 500 determines that the two-dimensional code 545 is not being displayed in a missing state (NO in step S521), if it determines after step S523 that the predetermined operation has not been performed (NO in step S524), or after step S525, the CPU 510 determines whether the two-dimensional code 545 has been received from the server 100 by the wireless communication unit 590 (step S527). If it determines that the two-dimensional code 545 has been received (YES in step S527), the CPU 510 controls the display 541 of the output unit 540 to display the received two-dimensional code 545 in place of the missing code currently being displayed (step S528). Here, the two-dimensional code 545 is displayed as shown in Figure 3(D).

[0069] The ticket gate processing, steps S131 to S134, and steps S531 to S533 are the same as those in Figure 2 of the first embodiment.

[0070] [Third Embodiment] In the first and second embodiments, the server 100 determines whether or not the location is one where the ticket initiated by user 10 can be used. In the third embodiment, the ticket application running on the mobile terminal 500 determines whether or not the location is one where the ticket initiated by user 10 can be used.

[0071] Figure 5 is a flowchart showing the processing flow of the ticket application program and the ticket server in the third embodiment. Referring to Figure 5, the ticket application processing is periodically called and executed by the CPU 510 of the mobile terminal 500 from a higher-level process. The ticket server processing is periodically called and executed by the CPU 110 of the server 100 from a higher-level process. In Figure 5, the processing with the same step numbers as in Figure 2 of the first embodiment is the same processing as in Figure 2, so redundant explanations will not be repeated.

[0072] Step S511 is the same as in Figure 2 of the first embodiment. If the mobile terminal 500 determines that an operation to start using the ticket has been accepted (YES in step S511), the CPU 510 acquires the location information of the mobile terminal 500 (step S512A). The CPU 510 determines, similar to step S112 in Figure 2, whether the location of the mobile terminal indicated by the acquired location information is a place where the ticket to be used can be used (for example, a train station or bus stop) (step S513).

[0073] If the CPU 510 determines that the ticket is valid at the location in question (YES in step S513), the CPU 510 controls the wireless communication unit 590 to send the ID of the ticket to be used to the server 100 (step S514).

[0074] In the server 100, the CPU 110 determines whether or not a ticket ID has been received from the mobile terminal 500 via the communication unit 190 (step S111A). If it determines that a ticket ID has been received (YES in step S111A), the CPU 110 executes the same process as in step S113 shown in Figure 2. Steps S515, S516, steps 521 to S533, steps S131 to S134, and the ticket gate processing are the same as in Figure 2 of the first embodiment.

[0075] [Differentiation] (1) In the embodiment described above, the code image used for the use of transportation was assumed to be a two-dimensional code 545. However, it is not limited to this, and the code image may be other code images such as a barcode, which is a one-dimensional code.

[0076] (2) In the embodiment described above, the automatic ticket gate 200 is of the type that uses a flap door 260. However, it is not limited to this, and the automatic ticket gate 200 may be of other types, for example, a turnstile type or a retractable type. Also, the automatic ticket gate 200 may be of the normally closed type or the normally open type.

[0077] (3) In the embodiments described above, the two-dimensional code 545 reader for transportation was assumed to be the reading unit 230 of an automatic ticket gate 200 installed at a railway station. However, the embodiments are not limited to this, and the reading device may be a reading unit included in a device installed at a railway station or bus stop that does not include doors such as flap doors 260, or it may be a reading device installed at the entrance or exit of a bus.

[0078] (4) In the embodiment described above, as shown in Figure 3(C), the unreadable information indicating that the two-dimensional code 545 used for the use of public transport is unusable is the two-dimensional code 545 with a portion missing due to the toggle switch 546 being displayed on top of the two-dimensional code 545. However, it is not limited to this, and the unreadable information may be other information as long as it indicates that the two-dimensional code 545 is unusable. For example, the unreadable information may be the two-dimensional code 545 with a portion missing due to the display of a white image 549 on top of the two-dimensional code 545, as shown in Figure 3(F). The unreadable information may be an image that completely hides the two-dimensional code 545. The unreadable information may be characters indicating the contents of the ticket corresponding to the two-dimensional code, which are displayed in place of the two-dimensional code 545.

[0079] (5) In the embodiments described above, as shown in step S524 of Figure 2 and in Figure 3(C), the predetermined operation for displaying the two-dimensional code 545 from a missing state to a normal state is a shake operation or a swipe operation. However, the predetermined operation is not limited to this, and may be other operations, such as a slide operation, an operation of holding the mobile terminal 500 over the reading unit 230, or a voice operation.

[0080] (6) In the embodiment described above, as shown in step S533 of Figure 2, when a predetermined period (for example, 10 seconds) has elapsed since the two-dimensional code 545 was displayed in a normal state, the two-dimensional code 545 was changed to an unusable state by returning to the list of owned tickets. However, the invention is not limited to this, and other methods may be used to change the two-dimensional code 545 to an unusable state, such as erasing the two-dimensional code 545, or displaying characters indicating the contents of the ticket in place of the two-dimensional code 545. Furthermore, the invention is not limited to this, and the two-dimensional code 545 may be invalidated when a predetermined period has elapsed since the two-dimensional code 545 was displayed in a normal state.

[0081] (7) In the embodiments described above, as shown in steps S511 and S512 in Figures 2 and 4, and steps S511 and S512A in Figure 5, the location information of the mobile terminal 500 is acquired by the mobile terminal 500 and the server 100 when the operation to start using the ticket is performed. However, the invention is not limited to this, and the timing at which the location information of the mobile terminal 500 is acquired may be at a different time than when the operation to start using the ticket is performed, for example, immediately before the creation of the two-dimensional code 545, when the ticket application is launched, or at a regular interval.

[0082] (8) The embodiments described above can be interpreted as a disclosure of the ticket management system 1, a disclosure of the server 100 or mobile terminal 500 included in the ticket management system 1, or a disclosure of a ticket management method, ticket management program, or ticket application program executed by the server 100 or mobile terminal 500.

[0083] [summary] (1) As shown in Figures 2, 4, and 5, the ticket management program (for example, the ticket application program) is a program executed on the mobile terminal 500, and in the first step of identifying the location information of the mobile terminal 500 (for example, step S512 in Figures 2 and 4, step S512A in Figure 5), when the following predetermined conditions are met, an operation for using a ticket that can be used on a predetermined section of the transportation system is accepted (for example, YES in step S511), and the identified location information is the place where the ticket will be used (for example, YES in step S112 in Figures 2 and 4, YES in step S513 in Figure 5), the program will be used for the use of the transportation system. The mobile terminal 500 is instructed to perform a second step (for example, step S516 in Figures 2 and 5, step S518 in Figure 4) in which unreadable information (for example, see Figures 3(C) and 3(F)) indicating that the code image to be used (for example, a two-dimensional code 545) is unusable, and a third step (for example, step S525 in Figure 2, step S528 in Figure 4) is instructed to display the code image on the mobile terminal in place of the unreadable information if the unreadable information is displayed (for example, YES in step S521) and a predetermined operation (for example, see Figure 3(C)) is detected (for example, YES in step S524).

[0084] As a result, when the location information of the mobile terminal 500 indicates the starting location of the ticket, and a predetermined operation is detected, the code image used for using public transportation is displayed on the mobile terminal 500 instead of unreadable information indicating an unusable code image. Consequently, ticket fraud can be prevented without any extra effort.

[0085] (2) As shown in step S524 of Figure 2 and in Figure 3(C), the predetermined operation may be a shake operation or a swipe operation of the mobile terminal 500. This makes it possible to display the code image on the mobile terminal 500 with a simple operation.

[0086] (3) As shown in step S512 of Figure 2, the second step may include a step of determining the location information using location-determining information obtained through communication with an external source (e.g., a beacon device 700, a positioning satellite 600) of the mobile terminal 500. This allows the location information of the mobile terminal 500 to be appropriately determined.

[0087] (4) As shown in step S533 of Figure 2, the ticket management program may also cause the mobile terminal 500 to perform a fourth step in which, after a predetermined period of 10 seconds or less has elapsed since the display of the code image began in the third step, the code image is changed to an unusable form or the code image is invalidated.

[0088] This prevents others from reading the code image with another mobile device 500 and using it fraudulently after the code image has been displayed.

[0089] (5) As shown in Figure 1, the server 100 manages tickets usable on a predetermined section of the transportation system and includes a processor (e.g., CPU 110) and a communication unit (e.g., communication unit 190) that communicates with the mobile terminal 500. As shown in Figure 4, the processor receives through the communication unit 190 that an operation for using the ticket has been accepted by the mobile terminal 500 (for example, YES in step S111), and if the location information of the mobile terminal 500 received through the communication unit 190 is the place where the ticket will be used (for example, YES in step S112), it transmits unreadable information (for example, a missing code) to the mobile terminal 500 through the communication unit 190 in order to display the code image (for example, a two-dimensional code 545) used for using the transportation in an unusable manner (for example, step S114). If the mobile terminal 500 is displaying the unreadable information (for example, YES in step S521) and the processor receives through the communication unit 190 that a predetermined operation has been detected (for example, YES in step S524), it transmits a code image to the mobile terminal 500 through the communication unit 190 in place of the unreadable information (for example, step S123). This makes it possible to prevent ticket fraud without requiring extra effort.

[0090] (6) As shown in Figures 1 to 5, the ticket management method is a method for managing tickets that can be used on a predetermined section of a transportation system, and includes the steps of: generating a code image (e.g., a two-dimensional code 545) to be used for the use of the transportation system (e.g., step S113); generating unreadable information that indicates the code image in an unusable manner (e.g., step S516 in Figures 2 and 5, step S114 in Figure 4); and when an operation for using the ticket is accepted (e.g., YES in step S511) and the location information of the mobile terminal 500 is the place where the ticket will be used (e.g., step S516 in Figures 2 and 4) Step S112 (Step S513 in Figure 5) includes a step of displaying unreadable information (for example, see Figures 3(C) and 3(F)) on the mobile terminal 500 (for example, Step S516 in Figures 2 and 5, Step S518 in Figure 4), and a step of displaying a code image on the mobile terminal 500 in place of the unreadable information if the unreadable information is displayed on the mobile terminal 500 (for example, Step S525 in Figure 2, Step S528 in Figure 4) when a predetermined operation (for example, see Figure 3(C)) is detected (for example, Step S524). This makes it possible to prevent fraudulent use of tickets without requiring extra effort.

[0091] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of this disclosure is indicated by the claims rather than by the description of the embodiments above, and all modifications within the meaning and scope equivalent to the claims are intended to be included. [Explanation of symbols]

[0092] 1 Ticket management system, 10 users, 100 servers, 110, 210, 510, 710 CPUs, 120, 220, 520, 720 memory, 150 mass storage devices, 151 recording media, 190, 290 communication units, 200 automatic ticket gates, 230 reading units, 260 flap doors, 500, 500A, 500B mobile terminals, 530 operation units, 540 output units, 541 displays, 542, 542A ticket information, 543, 544, 548 pop-up displays, 545, 550 two-dimensional codes, 546 toggle switches, 547 slide units, 549 outline images, 560 receiving units, 570, 770 short-range communication units, 590, 790 wireless communication units, 600 positioning satellites, 700 Beacon devices, 900 communication network.

Claims

1. A ticket management program that runs on a mobile device, The aforementioned ticket management program is: The first step is to identify the location information of the aforementioned mobile device, A second step is to display unreadable information on the mobile terminal indicating that the code image cannot be used, before displaying the code image used for the use of the transportation service, when an operation for using the transportation service is accepted and the specified location information is the place where the ticket is to be used, A ticket management program that causes a mobile terminal to perform a third step: when the unreadable information is displayed and a predetermined operation is detected, to display the code image shown in a usable manner in place of the unreadable information on the mobile terminal.

2. The ticket management program according to claim 1, wherein the predetermined operation is a shake operation or a swipe operation of the mobile terminal.

3. The ticket management program according to claim 1, wherein the second step includes identifying the location information using location identification information obtained through communication of the mobile terminal with an external party.

4. The ticket management program, when a predetermined period of 10 seconds or less has elapsed since the display of the code image began in the third step, further causes the mobile terminal to execute a fourth step which involves performing a predetermined process. The ticket management program according to any one of claims 1 to 3, wherein the predetermined processing is a process that changes the code image to an unusable form, or a process that invalidates the code image.

5. A ticket management server that manages tickets usable on designated sections of public transportation, Processor and It is equipped with a communication unit that communicates with a mobile terminal, The aforementioned processor, When the communication unit receives confirmation via the mobile terminal that an operation for using the aforementioned ticket has been received, and the location information of the mobile terminal received via the communication unit is the place where the ticket will be used, before displaying the code image used for using the transportation, the communication unit transmits unreadable information indicating that the code image is unusable to the mobile terminal in order to display it on the mobile terminal. A ticket management server that, when it receives through the communication unit that the unreadable information is displayed on the mobile terminal and that a predetermined operation has been detected, transmits the code image, shown in a usable form, to the mobile terminal via the communication unit in order to display it on the mobile terminal instead of the unreadable information.

6. A ticket management method for managing tickets usable on designated sections of transportation, The steps include generating a code image to be used for the use of the aforementioned transportation system, The steps include generating unreadable information that shows the aforementioned code image in an unusable manner, When an operation for using the aforementioned ticket is accepted and the location information of the mobile terminal is the place where the use of the aforementioned ticket will begin, the steps include displaying the unreadable information on the mobile terminal before displaying the code image shown in a usable form, A ticket management method comprising the step of, when the unreadable information is displayed on the mobile terminal and a predetermined operation is detected, the mobile terminal displays the code image shown in a usable manner in place of the unreadable information.

Images