Ticket Processing System

Abstract

To provide a ticket processing system which executes reception processing for a ticket quickly.SOLUTION: A ticket processing system 100 includes a ticket issuing server 50 for issuing a ticket TC; an automatic ticket examination machine 20 serving as a reading terminal for reading an ID (ticket ID) of a ticket; and a ticket information processing server 10 which acquires, in advance, information necessary for reception processing, out of information on the ticket TC, from the ticket issuing server 50, and executes the reception processing based on the ticket ID and an ID (reading terminal ID) of the reading terminal, in accordance with an inquiry from the automatic ticket examination machine 20.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a ticket processing system that enables ticket acceptance processing when passing through a gate device, etc. [Background technology]

[0002] A known technology related to the entry and exit of vehicles in a parking lot with a gate is a fee settlement system (see Patent Document 1) in which vehicle numbers are pre-registered in a fee collection server, and the vehicle number read when a vehicle enters or leaves the parking lot is queried from the fee collection server.

[0003] However, the method disclosed in Patent Document 1 above does not necessarily allow for rapid response when large amounts of information containing various types of information need to be processed quickly, such as when processing tickets at automatic ticket gates at stations. [Prior art documents] [Patent documents]

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

[0005] The present invention has been made in view of the above-mentioned points, and has as its object to provide a ticket processing system that can quickly process ticket reception.

[0006] The ticket processing system for achieving the above objective comprises a ticket issuing server that issues tickets, a reading terminal that reads the ticket ID, and a ticket information processing server that obtains information about the ticket necessary for reception processing from the ticket issuing server in advance, and performs reception processing based on the ticket ID and the ID of the reading terminal in response to an inquiry from the reading terminal.

[0007] In the above-mentioned ticket processing system, of the various types of ticket-related information handled by the ticket issuing server, only the information necessary for reception processing is stored in advance in the ticket information processing server, and then the ticket information processing server performs reception processing based on the ID of the ticket read by the reading terminal and the ID of the reading terminal itself, thereby enabling rapid reception processing of the ticket that was read by the reading terminal.

[0008] In a specific aspect of the present invention, the ticket information processing server determines the validity of a ticket based on the ticket ID and the ID of the reading terminal. In this case, in addition to verifying the ticket content based on the ticket ID, reception processing can also be performed based on, for example, location information of the reading terminal.

[0009] In another aspect of the present invention, the ticket information processing server is a fee calculation server that performs a payment process in response to an inquiry from a reading terminal. In this case, the payment process can be performed in conjunction with the reception process.

[0010] In yet another aspect of the present invention, the ticket information processing server completes the reception process in response to the inquiry from the reading terminal and then reports the processing result to the ticket issuing server, thereby ensuring the speed of the reception process and allowing various ticket-related processes to be performed after the reception process.

[0011] In yet another aspect of the present invention, the ticket issuing server is a ticket issuing server that issues a boarding pass as a ticket, the reading terminal is provided in an automatic ticket gate that performs an operation of permitting or denying passage and reads the ID of the ticket, and the ticket information processing server determines the validity of the ticket based on the ID of the ticket and the location information of the automatic ticket gate contained in the ID of the automatic ticket gate. In this case, the automatic ticket gate processing as the ticket acceptance processing can be performed quickly.

[0012] In yet another aspect of the present invention, a ticket issuing server issues a digital ticket to a user terminal as a passenger ticket, and a reader terminal at an automatic ticket gate reads the ID of the digital ticket from the user terminal. In this case, the user can use, for example, their own smartphone as the user terminal from which the digital ticket is issued.

[0013] In yet another aspect of the present invention, the ticket information processing server acquires in advance passage permission / denial determination information, which is the travel section, payment fare, and expiration date extracted from the various information at the time of ticket purchase managed by the ticket issuing server, and upon inquiry from the reading terminal, compares the ticket ID and the location information of the automatic ticket gate with the passage permission / denial determination information. In this case, by comparing the ticket ID and the location information of the automatic ticket gate with various information acquired in advance specifically for ticket acceptance processing, it becomes possible to handle processes that require speed on the order of several hundred milliseconds, such as passing through an automatic ticket gate. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 is a conceptual diagram illustrating an overview of a ticket processing system according to an embodiment. [Figure 2] FIG. 2 is a conceptual diagram showing an outline of the operation of the ticket processing system, from ticket issuance to reception. [Figure 3] FIG. 1 is a conceptual diagram showing an overall overview of a series of operations of a ticket processing system. [Figure 4] FIG. 1 is a block diagram illustrating an example of a configuration of a ticket processing system. [Figure 5] 10 is a data table showing data handled by the ticket issuing server. [Figure 6] 10A to 10D are data tables showing data handled by the ticket information processing server. [Figure 7] FIG. 2 is a sequence diagram illustrating a series of processing operations in the ticket processing system. [Figure 8]FIG. 10 is a conceptual diagram illustrating a modified example of the ticket processing system. [Figure 9] FIG. 10 is a conceptual diagram for explaining another modified example of the ticket processing system. DETAILED DESCRIPTION OF THE INVENTION

[0015] An example of a ticket processing system according to an embodiment will be described below with reference to FIG. 1 and other figures. As an example of a ticket processing system according to this embodiment, a ticket processing system 100 shown in FIG. 1 and other figures handles train tickets as tickets to be handled. In FIG. 1, the ticket processing system 100 includes a ticket information processing server 10, an automatic ticket gate 20 functioning as a reader terminal, and a ticket issuing server 50. For example, the ticket issuing server 50 in the ticket processing system 100 is a ticket issuing server that issues train tickets as tickets (TC) and communicates with ticket vending machines (TD) installed at stations to manage the issuance of paper tickets. In particular, in this embodiment, the ticket processing system 100 is capable of issuing not only paper tickets but also digital tickets. Therefore, as shown in the figure, in response to an inquiry from a user terminal SM such as a smartphone, the ticket issuing server 50 issues a digital ticket (TC) to the user terminal SM, as a display image on the display unit DSs of the user terminal SM. In the illustrated example, the ticket TC is displayed on the display unit DSs as a two-dimensional code such as a QR code (registered trademark), but the ticket processing system 100 is not limited to this and can issue digital tickets as tickets TC in various forms. In other words, the ticket processing system 100 is capable of ticket processing for digital tickets, i.e., is capable of handling digital tickets.

[0016] In the ticket processing system 100, the automatic ticket gate 20 is installed at a station ticket gate, accepts a ticket TC, and opens or closes a gate device GT to determine whether or not the user is permitted to pass through. To accept the ticket TC as a two-dimensional code (digital ticket) displayed on a user terminal SM, the automatic ticket gate 20 is provided with a reception unit RP and a reading unit RD. When the ticket TC displayed on the user terminal SM is held over the reception unit RP, the reading unit RD reads the ID (ticket ID) of the ticket TC from the ticket TC, i.e., the two-dimensional code. In other words, the automatic ticket gate 20 not only performs the operation to determine whether or not the user is permitted to pass through, but also functions as a reading terminal that reads the ID of the ticket TC as a prerequisite for determining whether or not the user is permitted to pass through. The ticket ID read by the automatic ticket gate 20 as a reading terminal is notified to the ticket information processing server 10. In other words, the automatic ticket gate 20 queries the ticket information processing server 10 regarding the determination of whether or not the ticket ID it reads is permitted. The automatic ticket gate 20 also notifies the ticket information processing server 10 of an ID for identifying itself, that is, a reading terminal ID (or ticket gate ID), along with the ticket ID. The reading terminal ID (or ticket gate ID) includes, for example, information about the location of the automatic ticket gate 20, which indicates which station the automatic ticket gate 20 is installed at.

[0017] In the ticket processing system 100, the ticket information processing server 10 performs reception processing based on the ticket ID and the reading terminal ID (ticket gate ID) in response to an inquiry from the automatic ticket gate 20 serving as a reading terminal. That is, the ticket information processing server 10 determines the validity of the ticket TC as a passenger ticket corresponding to the ticket ID based on the ticket ID and the reading terminal ID. The determination result is transmitted to the automatic ticket gate 20, and a display corresponding to the determination result is displayed on the display unit DSa of the automatic ticket gate 20. Furthermore, in order to enable the reception processing, i.e., the determination processing, the ticket information processing server 10 acquires in advance from the ticket issuing server 50 information related to the ticket TC that is necessary for the reception processing.

[0018] As described above, the ticket issuing server 50 of the ticket processing system 100 oversees all processes related to the issuance (issuance) of tickets TC, i.e., passenger tickets as tickets TC. For this reason, as described above, the ticket issuing server 50 is connected to a personal computer terminal TM in addition to communication with ticket vending machines TD and user terminals SM via, for example, a network line, and can issue tickets at, for example, face-to-face ticket counters at stations or via a network connection from general users. A wide variety of types of tickets can be issued, including, for example, standard tickets with a fixed route according to the fare, one-day tickets, fixed-date tickets, and prepaid tickets that can be used only for a certain amount paid in advance. The ticket issuing server 50 can also centrally manage information about the entire area of ​​the corresponding railway track. Furthermore, a wide variety of payment methods for purchasing (paying for) tickets TC are possible, including cash, credit cards, electronic payments, and electronic money. As described above, the ticket issuing server 50 manages and controls various matters relating to the issuance (issuance) of the ticket TC.

[0019] In the above configuration, the ticket issuing server 50 must handle a wide variety of information, and the amount of data handled is enormous. Therefore, it takes a considerable amount of time to process this information. In other words, from the user's perspective, when purchasing a ticket TC, the user must select the ticket TC and the purchase method, and processing must be performed accordingly. Therefore, it is expected that the purchase will take at least several seconds.

[0020] On the other hand, operations related to the use of the ticket TC, such as the reading operation to pass through the automatic ticket gate 20 using the purchased ticket TC, must be performed quickly, for example, within several hundred milliseconds, otherwise the convenience of the ticket TC will be significantly impaired. Therefore, if the information stored in the ticket issuing server 50 configured as described above were used as is to determine the validity of the ticket TC, it would be impossible to process at a realistic speed.

[0021] Therefore, in the ticket processing system 100 of this embodiment, the ticket information processing server 10 is provided separately from the ticket issuing server 50, and the ticket information processing server 10 has acquired in advance information necessary for the reception process among the information related to the ticket TC from the ticket issuing server 50. In other words, in the ticket processing system 100, the ticket information processing server 10 is specialized to handle the processes required for determining the validity of the ticket TC, thereby enabling the reception process for the ticket TC to be carried out quickly.

[0022] Hereinafter, with reference to the conceptual diagram shown in FIG. 2, an overview of the above embodiment will be described, particularly of the operation of the ticket processing system 100 from issuing the ticket TC to accepting the ticket TC.

[0023] First, in the case of issuing a ticket TC, shown as state α in the figure, the ticket issuing server 50 transmits, together with the ticket ID of the ticket TC, information required for the reception process at the ticket information processing server 10 from among various pieces of information related to the ticket TC generated when the ticket TC was issued, to the ticket information processing server 10. More specifically, the ticket issuing server 50 transmits to the ticket information processing server 10, linked to the ticket ID of the ticket TC, information extracted from various pieces of information generated when the ticket TC was issued, i.e., various pieces of information at the time of the user's purchase of the ticket, such as the travel section, fare paid, and expiration date (hereinafter referred to as information for determining whether or not to allow passage), etc.

[0024] In the above embodiment, after the ticket TC has been issued, when the ticket TC is used (see state β described later), the ticket information processing server 10 determines the validity of the ticket TC to determine whether the ticket TC is permitted to pass through the automatic ticket gate 20. This is done in response to an inquiry from the automatic ticket gate 20, which serves as a reading terminal, based on the ticket ID and the reading terminal ID (ticket gate ID). Therefore, the ticket information processing server 10 is in a state where it has received the above-mentioned passage permission / prohibition determination information from the ticket issuing server 50 in advance, and waits for an inquiry from the automatic ticket gate 20.

[0025] Next, in the case of using (utilizing) ticket TC, shown as state β in the figure, when the user holds the ticket TC over the automatic ticket gate 20 (or the reading unit RD of the automatic ticket gate 20), the ticket TC is detected by the automatic ticket gate 20 (or the reading unit RD of the automatic ticket gate 20) and the ticket ID is read, the ticket information processing server 10 is notified of the read ticket ID together with the reading terminal ID of the automatic ticket gate 20 itself as the reading terminal that read it.

[0026] The ticket information processing server 10 receives a notification from the automated ticket gate 20 as an inquiry about the validity of the ticket TC and makes a decision in response to the inquiry based on the passage permission determination information previously received from the ticket issuing server 50. Specifically, the ticket information processing server 10 analyzes the location information of the automated ticket gate 20 included in the reader terminal ID of the automated ticket gate 20, as well as information such as the expiration date and validity zone of the ticket linked to the ticket ID corresponding to the ticket TC, and compares the ticket ID and the location information of the automated ticket gate 20 obtained as the analysis result with the passage permission determination information to determine whether the ticket TC is valid for passage through the automated ticket gate 20 in question. In this case, the information previously transmitted from the ticket issuing server 50 to the ticket information processing server 10 also includes information necessary for fare settlement, for example, in the case of a prepaid ticket. In other words, the ticket information processing server 10 can also function as a fare calculation server that performs fare settlement processing in response to an inquiry from the automated ticket gate 20.

[0027] As indicated by the dashed arrow and the cross (x) symbol, neither the ticket information processing server 10 nor the automatic ticket gate 20 makes an inquiry to the ticket issuing server 50 when making the above-described pass-through permission / denial determination. In other words, the determination process and fare adjustment process are completed by the processing up to the ticket information processing server 10. This allows the above-described determination process to be performed even in a very short time, such as about 200 milliseconds. In other words, this system can be adapted to cases where a determination is required in a short time, such as when passing through a gate at the automatic ticket gate 20.

[0028] Below, an overall overview of the flow of a series of operations using the ticket processing system 100, including the processes from issuing the ticket TC to accepting it, will be explained step by step, with reference to the conceptual diagram shown in Figure 3. Here, as a specific example, we will explain the processing operations assuming that a user accesses the ticket issuing server 50 using a user terminal SM such as a smartphone that the user owns, purchases (has the ticket TC issued) in the form of a digital ticket, and then takes the user terminal SM to the automatic ticket gate 20 and uses the ticket TC to pass through the automatic ticket gate 20, i.e., uses the ticket TC.

[0029] First, when a ticket TC as a digital ticket is purchased as a result of an inquiry or the like made from the user terminal SM to the ticket issuing server 50 (step S1), at this time, the ticket issuing server 50 stores various information such as a purchase record generated at the time of purchase (issuance) of the ticket TC in the issuance (ticketing) information database 51. In addition, with the purchase of the ticket TC, the user can display a two-dimensional code as the ticket TC on, for example, the user terminal SM (step S2).

[0030] Meanwhile, in step S1, by appropriately selecting from the various information stored in the issuing (ticketing) information database 51, for example, passage permission / denial determination information, which is information summarizing items necessary for settlement and validity determination regarding the ticket TC, is created, and the created passage permission / denial determination information is transmitted to and stored in the ticket information processing server 10. Specifically, this information is stored as ticket information in the ticket information database 11 constituting the ticket information processing server 10 (step S3). As a result, the ticket issuing server 50 and the ticket information processing server 10 are in a state where information regarding the ticket TC has been pre-linked. Note that the time required for the above transmission is expected to be, for example, on the order of several seconds to several tens of seconds.

[0031] Thereafter, when the user uses the ticket TC at the automatic ticket gate 20 (step S4), i.e., when the ticket TC is verified, the automatic ticket gate 20 makes an inquiry (and, if necessary, a request for settlement) to the ticket information processing server 10 (step S5).

[0032] When the ticket information processing server 10 receives an inquiry or the like in step S5, it determines the validity of the ticket TC and performs fare calculation or settlement processing as necessary (step S6), and responds with the determination result or the like to the automatic ticket gate 20, so that the result is displayed, for example, on the display unit DSa of the automatic ticket gate 20 (see Figure 1) (step S7).

[0033] In this embodiment, when steps S5 to S7 are performed among the above steps, the processing is mainly communication between the automatic ticket gate 20 and the ticket information processing server 10, analysis processing in each section, display operation processing, etc., and high speed is maintained by simplifying the processing and limiting the objects to be analyzed to the minimum necessary. As a result, the processing of steps S5 to S7, i.e., the processing that should be performed while the user is passing through the automatic ticket gate 20, can be completed in, for example, about 200 milliseconds.

[0034] In the above, the ticket issuing server 50 is the main entity that operates when issuing a ticket TC, but it can also be considered that the issuing of a ticket TC also involves the user terminal SM that makes inquiries about the issuance of the ticket TC to the ticket issuing server 50. Here, these are collectively referred to as the ticket issuing system TIs.

[0035] Furthermore, components that operate when an issued ticket TC is used, i.e., components involved in the reception operation, include the ticket information processing server 10 and the automatic ticket gate 20 that makes inquiries about the ticket TC to the ticket information processing server 10. Here, these are collectively referred to as the ticket reception processing system CCs.

[0036] In the above embodiment, the ticket issuing system TIs functions in issuing the ticket TC as the first stage of processing, and the ticket acceptance processing system CCs functions in using the ticket TC as the second stage of processing.

[0037] Furthermore, in the above description, the ticket processing system 100 is described as being composed of the ticket information processing server 10, the automatic ticket gate 20, and the ticket issuing server 50, but it is also possible to consider the ticket processing system 100 to include the user terminal SM, the ticket vending machine TD (see FIG. 1), etc. In this case, the ticket processing system 100 can also be considered to be composed of a ticket issuing system TIs and a ticket reception processing system CCs. In other words, the ticket processing system 100 has a part that operates when a ticket TC is issued and a part that operates when the ticket TC is used, and these operate separately depending on the operation content.

[0038] Below, with reference to Fig. 4 etc., a more specific description will be given of an example of the configuration of the ticket processing system 100 and an example of data handled by the ticket processing system 100. It is assumed here that information relating to all targets of tickets issued by the ticket processing system 100 is managed. That is, the ticket issuing server 50 constituting the ticket processing system 100 collectively collects information on all lines and stations corresponding to the tickets TC to be issued. The ticket information processing server 10 is also capable of accepting and processing tickets TC for the entire range of targets covered by the ticket issuing server 50.

[0039] First, as shown in the example block diagram of Figure 4, in the ticket reception processing system CCs of the ticket processing system 100, the ticket information processing server 10 includes, in addition to the ticket information database 11 already described, a reading terminal information database 12, a communication unit 13, and a main control unit 15.

[0040] The ticket information database 11 stores passage permission determination information and the like transmitted from the ticket issuing server 50. A specific example of the passage permission determination information will be described later with reference to FIG.

[0041] Meanwhile, information on all automatic ticket gates (reading terminals) 20 that can accept tickets TC is stored in the reading terminal information database 12, linked to the reading terminal ID. That is, by referring to the data stored in the reading terminal information database 12 for the reading terminal ID that is the subject of acceptance, it is possible to obtain, for example, location information (information on the station where the ticket gate is installed) and the like for the corresponding automatic ticket gate 20.

[0042] The communication unit 13 is a device for communicating with the ticket issuing server 50 and the automatic ticket gate 20.

[0043] The main control unit 15 is configured with, for example, a CPU, electronic circuits, etc., and performs calculations for various operational processes and outputs various command signals to each unit. Here, the main control unit 15 functions as, for example, a ticket information updating unit TU, an ID matching unit IV, or a fare calculation unit CD.

[0044] First, the main control unit 15 of the ticket information processing server 10, for example as the ticket information update unit TU, writes the contents of changes (updates) regarding the contents of the ticket TC that occur in association with the reception process of the ticket TC inquired about from the automatic ticket gate 20 into the ticket information database 11. That is, when the contents of the ticket TC change, for example, from an unentered state to an entered state in association with the result of the pass-through permission determination when the ticket TC is used to pass through the automatic ticket gate 20, the change is stored in the ticket information database 11. That is, the data is rewritten (updated).

[0045] In addition, the main control unit 15, for example as an ID matching unit IV, matches the ticket ID and reading terminal ID received from the automatic ticket gate 20 with the data stored in the ticket information database 11 and the reading terminal information database 12, reads various information linked to the ID, and determines whether or not to allow passage.

[0046] Furthermore, the main control unit 15, for example, functions as a fare calculation unit CD and performs necessary processing when a fare calculation process is required as a result of various processes related to the ticket TC as described above. As a typical example, when it is detected that the type of ticket TC in question is a prepaid type, which allows use of the ticket only for an amount paid in advance, the fare calculation unit CD calculates the amount to be deducted from the prepaid amount of the ticket TC based on the history of the automatic ticket gates 20 through which the ticket TC has passed. Note that, for example, the result of this calculation is notified to the automatic ticket gate 20 via the communication unit 13 and is displayed on the display unit DSa of the automatic ticket gate 20.

[0047] In the ticket acceptance processing system CCs, the automatic ticket gate 20 includes the above-mentioned reading unit RD, display unit DSa, and gate device GT, as well as a self ID storage unit 22, a communication unit 23, and a main control unit 25.

[0048] As described above, the reading unit RD functions as a ticket ID reception unit TR that reads and receives the ticket ID from the ticket TC. Note that it can also be considered that the reception unit RP in FIG. 1 also functions as the ticket ID reception unit TR.

[0049] The display unit DSa is configured with a liquid crystal panel or an organic EL panel, etc., and displays the reception result for the ticket TC. The gate device GT performs opening and closing operations based on the reception result, i.e., the determination result as to whether passage is permitted or not. In other words, the display unit DSa and the gate device GT perform operations related to the reception processing result in the ticket reception processing system CCs under the command of the main control unit 25.

[0050] The self ID storage unit 22 stores the ID information of the automatic ticket gate 20 itself, i.e., the reading terminal ID information. The reading terminal ID information is notified to the ticket information processing server 10 via the communication unit 23 together with the ticket ID information read by the ticket ID reception unit TR.

[0051] The communication unit 23 is a device for communicating with the ticket information processing server 10 as described above.

[0052] The main control unit 25 is composed of, for example, a CPU, electronic circuits, etc., and outputs various command signals to each unit constituting the automatic ticket gate 20 to perform various operational processes in each unit. For example, it causes the reader unit RD to read ticket ID information from the ticket TC, and links the read ticket ID information with its own reading terminal ID information stored in the self ID storage unit 22, and outputs the result to the ticket information processing server 10 via the communication unit 23. The main control unit 25 also receives a response from the ticket information processing server 10, indicating whether or not passage is permitted, and outputs command signals related to display on the display unit DSa and opening / closing of the gate device GT according to the determination result. In this way, the automatic ticket gate 20 functions as a gate device for determining whether or not passage is permitted.

[0053] Next, in the ticket issuing system TIs of the ticket processing system 100, the ticket issuing server 50 includes a communication unit 53 and a main control unit 55 in addition to the issuance (ticketing) information database 51 already described.

[0054] Various types of information handled when issuing (purchasing) a ticket TC are stored in the issuance (ticketing) information database 51. A specific example of this information will be described later with reference to FIG.

[0055] The communication unit 53 is a device for communicating with the ticket information processing server 10 as well as with various equipment that makes the necessary requests when issuing (purchasing) a ticket TC, such as the user terminal SM, ticket vending machine TD, and personal computer terminal TM.

[0056] The main control unit 55 is composed of, for example, a CPU, electronic circuits, etc., and performs various information processes related to the issuance of tickets TC performed in the ticket issuing server 50. For example, the main control unit 55 has a ticket information creation unit 55t that edits various information stored in the issuance (ticketing) information database 51 and creates ticket information to be sent to the ticket information processing server 10. In other words, the ticket information creation unit 55t creates passage permission / denial determination information to be stored in the ticket information database 11.

[0057] The ticket issuance system TIs can be understood to include, in addition to the ticket issuance server 50, user terminals SM, ticket vending machines TD, personal computer terminals TM, and the like that access the ticket issuance server 50 to make inquiries or requests regarding the issuance process of tickets TC. Of these, for example, the user terminal SM, as described above, is configured as a smartphone or the like, and includes, in addition to the display unit DSs described above, a touch panel TP, a communication unit SMt, a main control unit SMp that is configured as a CPU, electronic circuits, and the like and controls various operations, and a memory unit SMm that is configured as a storage device or the like. For example, a user can make their smartphone function as the user terminal SM configured as described above by installing a dedicated app on it or by accessing a ticket issuance website.

[0058] By operating the touch panel TP, the user communicates with the ticket issuing server 50 via the communication unit SMt, requests the issuance of a ticket TC, and performs necessary processing such as payment processing to obtain something equivalent to the ticket TC (digital ticket), which is stored in the memory unit SMm. When using the ticket TC (digital ticket), the main control unit SMp reads data related to the ticket TC from the memory unit SMm, and as described above, displays a two-dimensional code equivalent to the ticket ID of the ticket TC on the display unit DSs, which is read by the ticket ID reception unit TR (reading unit RD) of the automatic ticket gate 20 and transmitted to the ticket information processing server 10, which determines whether or not the ticket is permitted to pass.

[0059] FIG. 5 is a diagram showing an example of a data table showing data handled by the ticket issuing server 50. As shown in FIG.

[0060] As described above, the ticket issuing server 50 issues various types of tickets (tickets) as tickets TC in response to inquiries from user terminals SM held by general users, ticket vending machines TD installed at each station, and even from operators at station counters and personal computer terminals TM operated by general users. Various types of tickets can be issued, from traditional paper tickets to digital tickets. Furthermore, as described above, various payment methods for transactions can be accepted, including cash, credit cards, and electronic money. Therefore, as illustrated in FIG. 5 , the ticket issuing server 50 handles a wide variety of data when issuing (purchasing) a ticket TC. For example, when issuing a ticket TC, various pieces of information are generated in association with a ticket ID identifying the ticket TC and information related to the date and time the ID was issued. Furthermore, the various pieces of information handled include, for example, ticket data DD1 relating to the contents of the ticket TC and transaction data DD2 indicating information related to various transactions involved in the issuance of the ticket TC. More specifically, the ticket data DD1 includes, for example, the ticket type (e.g., one-day pass, prepaid ticket, etc.) as well as information on the validity period and section. Meanwhile, the transaction data DD2 includes, in addition to the transaction number, information on the counter indicating the location or method of the issuance transaction, the payment method, various data such as the credit card number (PAN: Primary Account Number) referenced in the payment process or the corresponding token number, as well as information on the issuance mode of the ticket TC and the data transmission destination or display medium when a digital ticket is issued as the ticket TC. As shown in the figure, the content of this information varies for each transaction, and this diverse data is stored in the issuance (ticketing) information database 51. For this reason, if the information generated by the transaction at the time of issuance and stored in the issuance (ticketing) information database 51 is used for verification, for example, when validating the ticket TC or calculating the fare when using the ticket TC at the automated ticket gate 20, the verification and other processing are likely to take a long time (e.g., several seconds or more).In particular, this method cannot be applied to cases where a response of about 200 milliseconds is required, such as when passing through the automatic ticket gate 20 and not passing through.

[0061] Therefore, in this embodiment, the main control unit 55 serving as the ticket information creation unit 55t specifically extracts information necessary for performing reception processes such as determining the validity of the ticket TC and calculating the fare from the information stored in the issuance (ticketing) information database 51 (see FIG. 5), and provides a ticket information processing server 10 as a server for making a determination based on the extracted data, which is separate and independent from the ticket issuing server 50. That is, among the various types of information stored in the issuance (ticketing) information database 51, ticket data DD1 that should be the ticket information necessary for reception processes such as determining the validity and calculating the fare is transmitted to the ticket information processing server 10 as passage permission / denial information, and the ticket information processing server 10 handles this as ticket information, thereby realizing fast and accurate reception processes for the ticket TC.

[0062] Figure 6 shows an example of a data table of ticket information handled by the ticket information processing server 10, and Figures 6(A) to 6(D) show how the data content changes (is rewritten) over time. Note that this data is stored in the ticket information database 11 of the ticket information processing server 10, and is updated in order every time a matching operation is performed on the ticket TC in accordance with instructions from the main control unit 15.

[0063] First, as illustrated in FIG. 6(A), various data related to tickets TC valid on the day (month and day) on which the validity determination is made is collected based on the ticket data DD1 (see FIG. 5). Specifically, information related to the usable zone and usage history of each ticket TC is stored, linked to the ticket ID. This information is updated each time a pass-through determination is made for an automated ticket gate 20 based on the ticket TC. For example, as illustrated by the highlighted text (white letters) in FIG. 6(B), when a ticket TC that has not yet entered the station is permitted to pass through a certain automated ticket gate 20, information indicating that the ticket TC has entered the station and information on the ID (reading terminal ID) of the automated ticket gate 20 that was passed through when entering the station are written accordingly. Furthermore, when the ticket TC subsequently passes through an automated ticket gate 20 based on the ticket TC and exits the station, the information for the relevant section is further updated, as illustrated by the white letters in FIG. 6(C). In the example shown in the figure, the ticket TC corresponding to the hatched area is a one-day ticket, and is completely used when it reaches the state shown in Figure 6(C).Therefore, the data is subsequently deleted from the ticket information database 11, as shown in Figure 6(D).

[0064] Furthermore, the results of updating the information in the ticket information processing server 10 as described above may be transmitted to the ticket issuing server 50 at a predetermined timing as necessary. As a typical example, in order to ensure speed of the processing, the main control unit 15 of the ticket information processing server 10 rewrites (updates) the information in the ticket information database 11 until the reception processing in response to an inquiry from the automatic ticket gate 20 as a reading terminal, i.e., the processing of whether or not to allow passage through the automatic ticket gate 20, is completed, and after the processing is completed, the main control unit 15 reports the processing result, i.e., the update record in the ticket information database 11, to the ticket issuing server 50.

[0065] Regarding the rewriting (updating) of data within the ticket information database 11, as described above, the ticket information (information for determining whether or not to allow passage) is updated in response to the detection of passage at the automatic ticket gate 20, and also when new ticket data DD1 information is added from the ticket issuing server 50.

[0066] A series of processing operations in the ticket processing system 100 will be described below with reference to the sequence diagram shown in FIG.

[0067] First, as various processes in the ticket issuance stage (ST1), when an order (inquiry) for ticket issuance is received from a user's smartphone, i.e., user terminal SM, the ticket issuance server 50 of the ticket processing system 100 accepts the order, issues a ticket ID, and performs processes such as payment required for issuing the ticket TC. As a result, various information exemplified with reference to FIG. 5 is created and stored in the issuance (ticketing) information database 51. The ticket issuance server 50 also transmits ticket ID information corresponding to the issued ticket TC to the user terminal SM via the communication unit 53, and the ticket ID is recorded in the memory unit SMm of the user terminal SM. At the same time, the ticket issuance server 50 also transmits ticket information (passage permission / denial determination information) related to the issued ticket TC, i.e., information corresponding to the ticket data DD1 exemplified in FIG. 6(A) and the like, to the ticket information processing server 10 via the communication unit 53, and the ticket information (passage permission / denial determination information) is recorded in the ticket information database 11 of the ticket information processing server 10.

[0068] Next, as various processes in the ticket usage stage, i.e., the stage (ST2) of detecting passage through the automatic ticket gate 20, a two-dimensional code corresponding to the ticket ID recorded in the memory unit SMm of the user terminal SM is displayed on the display unit DSs of the user terminal SM, and when the user approaches the automatic ticket gate 20 in this state, the two-dimensional code is read by the ticket ID reception unit TR (reading unit RD) of the automatic ticket gate 20. In other words, operations related to passage detection at the automatic ticket gate 20 are started. The automatic ticket gate 20 transmits the ticket ID and its own ID, i.e., the reading terminal ID, acquired by the reading operation to the ticket information processing server 10. Upon receiving the above IDs from the automatic ticket gate 20, the ticket information processing server 10 performs ticket information processing. In other words, the ticket information processing server 10 compares the received ticket ID with the ticket information (information for determining whether or not to allow passage) in the ticket information database 11, which is stored in advance at the ticket issuance stage, etc. and updated as necessary, to confirm the existence of a corresponding ticket ID, and compares the received ticket ID and reading terminal ID with the information linked to the ticket ID existing as ticket information in the ticket information database 11 to determine whether or not to allow passage, and sends the determination result as a response to an inquiry from the automatic ticket gate 20.

[0069] Upon receiving the response from the ticket information processing server 10, the main control unit 25 of the automatic ticket gate 20 performs an output display on the display unit DSa and an opening / closing operation of the gate device GT to permit or deny passage in accordance with the judgment result received as the response. At this time, as indicated by the dashed arrow, the processing result of the automatic ticket gate 20 may also be notified to the user terminal SM. For example, a short-range wireless communication function may be provided between the automatic ticket gate 20 and the user terminal SM, and the result of permitting or denying passage may also be transmitted to the user terminal SM. This completes the series of operations related to passage detection in the automatic ticket gate 20.

[0070] As mentioned above, the various processes at the ticket usage stage are configured so that the ticket issuing server 50 is not involved, thereby speeding up the processes.

[0071] Finally, as an operation (ST3) after passage detection at the automatic ticket gate 20, as already mentioned, for example, the ticket information processing server 10 may transmit the result of the passage permission / denial decision and subsequent update information regarding the ticket TC to the ticket issuing server 50 at a predetermined timing.

[0072] As described above, the ticket processing system 100 according to this embodiment includes the ticket issuing server 50 that issues tickets TC, the automatic ticket gate 20 as a reading terminal that reads the ID of the ticket (ticket ID), and the ticket information processing server 10 that acquires in advance from the ticket issuing server 50 information necessary for reception processing from among the information related to the ticket TC, and performs reception processing based on the ticket ID and the ID of the reading terminal (reading terminal ID) in response to an inquiry from the automatic ticket gate 20. In this case, of the various information related to the ticket TC handled by the ticket issuing server 50, information necessary for reception processing is specialized and stored in advance in the ticket information processing server 10, and then the ticket information processing server 10 performs reception processing based on the ticket ID read by the automatic ticket gate 20 and the reading terminal ID of the automatic ticket gate 20 itself, thereby enabling rapid reception processing of the ticket TC that is the target of reading at the automatic ticket gate 20.

[0073] Furthermore, in the above embodiment, when the automatic ticket gate 20 reads information about the ticket TC, it is sufficient to read the ticket ID, and when the automatic ticket gate 20 inquires (transmits) to the ticket information processing server 10, it is sufficient to transmit the read ticket ID and its own ID. Therefore, compared to conventional magnetic tickets and IC cards, in which the decision on whether to allow or deny passage is made by checking various pieces of information written on the ticket TC itself, it is possible to minimize the amount of information handled during reading and transmission. Furthermore, it is also possible for the user to ultimately only need the ticket ID as the information they need to retain, which reduces the burden of retaining information compared to conventional magnetic tickets and IC cards, making it easier to use.

[0074] 〔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.

[0075] First, in the above, the automatic ticket gate 20 is exemplified as a reading terminal that reads the ticket ID or functions as a reading terminal, but the reading terminal is not limited to this. For example, a fare adjustment machine (excess fare adjustment machine) 220 as exemplified in FIG. 8 may have a reception unit RP and a reading unit RD, read the ticket ID on the ticket IC, and communicate with the ticket information processing server 10 to function as a reading terminal. For example, if the ticket TC is a prepaid type that allows use of the ticket for an amount paid in advance, and if the fare is insufficient at the time of exit, settlement (excess fare settlement) by the fare adjustment machine 220 is required. In such a case, the fare adjustment machine 220 can perform settlement processing based on calculations, for example, in a fare calculation unit CD through communication with the ticket information processing server 10, thereby enabling rapid settlement processing. In this case, as shown in the figure, the ticket information database 11 updates records such as the fact that the over-ride settlement has been made and the information on the settlement machine ID that identifies the settlement machine 220 that made the over-ride settlement, and this information is sent to the ticket issuing server 50 (not shown) at a specified time.

[0076] There are also various possible forms of ticket TC. In addition to the case where a paper ticket is omitted by making it a digital ticket that displays a two-dimensional code on the user terminal SM as described above, it is also possible to use a printed matter CC such as paper on which a two-dimensional code is printed in a ticket vending machine TD that issues tickets TC while communicating with a ticket issuing server 50, as illustrated in Figure 9.

[0077] In addition, in the above, for ease of explanation, the ticket information processing server 10 and the ticket issuing server 50 are illustrated as being physically separated, but various configurations are possible for these servers, such as a cloud-based configuration, and the above configuration can be used as long as the ticket information processing server 10 and the ticket issuing server 50 are functionally separate and independent.

[0078] Furthermore, the various types of information stored in the ticket information database 11 and the issuance (ticketing) information database 51 are also merely examples, and are not limited to the above-mentioned forms, and various forms of storing information are possible.

[0079] Furthermore, digital tickets (digital train passes) are not limited to two-dimensional codes such as QR codes (registered trademark), and various other forms are possible.

[0080] Furthermore, the ticket processing system 100 is not limited to station tickets (tickets), but can also be applied to the handling of various tickets, such as managing entry and exit to event venues, theme park facilities, or membership-based facilities. [Explanation of symbols]

[0081] 10...Ticket information processing server, 11...Ticket information database, 12...Reading terminal information database, 13...Communication unit, 15...Main control unit, 20...Automatic ticket gate (reading terminal), 22...Self-ID storage unit, 23...Communication unit, 25...Main control unit, 50...Ticket issuing server, 51...Issuance (ticketing) information database, 53...Communication unit, 55...Main control unit, 55t...Ticket information creation unit, 100...Ticket processing system, 220...Adjustment machine (excess fare adjustment machine), CC...Printed matter, CCs...Ticket Ticket reception processing system, CD...fare calculation unit, DD1...ticket data, DD2...transaction data, DSa...display unit, DSs...display unit, GT...gate device, IV...ID matching unit, RD...reading unit, RP...reception unit, SM...user terminal, SMm...storage unit, SMp...main control unit, SMt...communication unit, TC...ticket, TD...ticket vending machine, TIs...ticket issuing system, TM...computer terminal, TP...touch panel, TR...ticket ID reception unit, TU...ticket information update unit, α, β...status

Claims

1. a ticket issuing server that issues tickets; a reading terminal for reading the ID of the ticket; a ticket information processing server that acquires in advance from the ticket issuing server information necessary for reception processing among the information related to the ticket, and completes reception processing in response to an inquiry from the reading terminal based on the ID of the ticket and the ID of the reading terminal without the involvement of the ticket issuing server; Equipped with the ticket issuing server is a ticket issuing server that issues a boarding ticket as the ticket, The reading terminal is provided in an automatic ticket gate that performs an operation of permitting or denying passage, and reads the ID of the ticket, the ticket information processing server determines the validity of the ticket based on the ID of the ticket and location information included in the ID of the automatic ticket gate, the location information indicating at which station the automatic ticket gate is installed; Ticket processing system.

2. 2. The ticket processing system according to claim 1, wherein the ticket information processing server is a fee calculation server that performs settlement processing in response to an inquiry from the reading terminal.

3. 3. The ticket processing system according to claim 1, wherein the ticket information processing server reports a processing result to the ticket issuing server after completing an acceptance process in response to the inquiry from the reading terminal.

4. the ticket issuing server issues a digital ticket to the user terminal as the ticket; 4. The ticket processing system according to claim 1, wherein in the automatic ticket gate, the reading terminal reads the ID of the digital ticket from the user terminal.

5. The ticket processing system of any one of claims 1 to 4, wherein the ticket information processing server acquires in advance information for determining whether or not passage is permitted, which information is extracted from various information at the time of purchase of the ticket managed by the ticket issuing server, including the travel section, fare paid, and expiration date, and when an inquiry is received from the reading terminal, the ticket ID and the location information of the automatic ticket gate are compared with the information for determining whether or not passage is permitted.

Images