Information processing program, information processing method, and server device

Abstract

To provide an information processing program configured to issue a ticket using a one- or two-dimensional code to easily prevent use of a forged ticket, an information processing method, a server apparatus, and a ticket issuing apparatus.SOLUTION: A computer of a ticket issuing server 3 functions as: acquisition means (communication unit 33) which acquires ticket content information D2 relating to contents of a ticket to be used for riding a train; storage control means (control unit 31) which causes storage means (storage unit 32) to store the ticket content information D2; identification information addition means (control unit 31) which adds ticket identifier information D10 to each of the ticket content information D2 stored in the storage means; and code data generation means (control unit 31) which generates ordinary issuance two-dimensional code data D12 including the ticket identifier information D10.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information processing program and an information processing method. and Server equipment Place Regarding. [Background technology]

[0002] In recent years, technology has been developed to issue train tickets, which were previously issued using magnetic cards, using a predetermined one-dimensional or two-dimensional code such as a QR code (registered trademark) (see, for example, Patent Documents 1 and 2). Unlike conventional magnetic card tickets or the IC card tickets that have become increasingly common in recent years, such one-dimensional or two-dimensional codes can be issued without the use of a dedicated card, for example, by displaying them on the display of a smartphone, tablet device, etc., or by printing them on regular paper, making it possible to issue tickets to users for use in boarding trains inexpensively and easily. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2006-59249 [Patent Document 2] Patent No. 5380338 Summary of the Invention [Problem to be solved by the invention]

[0004] Tickets with such one-dimensional or two-dimensional codes allow the information stored on the ticket to be easily duplicated, for example, by duplicating the image data of the code or by copying the code onto a paper medium. Furthermore, tickets used to board trains usually store information required for entering and exiting ticket gates, such as information related to stations accessible with the ticket. Therefore, if conventional tickets were simply coded as one-dimensional or two-dimensional codes, the information required for entering and exiting ticket gates could easily be duplicated, making it difficult to prevent the use of counterfeit tickets.

[0005] The object of the present invention is to provide an information processing program and an information processing method that enable the issuance of tickets that are easy to prevent the use of counterfeit tickets while using one-dimensional or two-dimensional codes. and Server equipment Place The purpose is to provide [Means for solving the problem]

[0006] In order to solve the above problem, the invention described in claim 1 provides an information processing program, The computer of the server device, a first acquisition means for acquiring ticket content information, which is information relating to the content of a ticket used to board a train; a first storage control means for storing the ticket content information in a storage means; an identification information assigning means for assigning identification information to each of the ticket content information stored in the storage means; functioning as a code data generating means for generating code data which is data relating to a one-dimensional or two-dimensional code including the identification information; When multiple tickets are entered when inputting the ticket purchase information, the first acquisition means acquires multiple ticket contents corresponding to the multiple tickets, the first storage control means stores the plurality of pieces of ticket content information acquired by the first acquisition means in the storage means; the identification information assigning means assigns the common identification information to the plurality of pieces of ticket content information; the code data generating means generates a single code data. It is characterized by:

[0007] The invention described in claim 2 is an information processing program, The computer of the server device, a first acquisition means for acquiring ticket content information, which is information relating to the content of a ticket used to board a train; a first storage control means for storing the ticket content information in a storage means; an identification information assigning means for assigning identification information to each of the ticket content information stored in the storage means; a code data generating means for generating code data which is data relating to a one-dimensional or two-dimensional code including the identification information; a fourth acquisition means for further acquiring identification information assigned to the ticket content information desired to be linked with second ticket content information, which is information relating to the content of the additionally purchased ticket to be used for boarding the train; a fifth storage control means for causing the storage means to store the second ticket content information acquired by the fourth acquisition means; a second identification information assigning means for assigning the identification information acquired by the fourth acquisition means to the second ticket content information acquired by the fourth acquisition means; The present invention is characterized in that it functions as a

[0008] The invention described in claim 3 is or 2 In the information processing program described in The code data has a plurality of storage areas, The one storage area contains test information, which is information relating to the results of a predetermined conversion or calculation based on information contained in the other storage areas.

[0009] The invention described in claim 4 is Any one of the items from to 3 In the information processing program described in a second acquisition means for acquiring available time information which is information relating to the available time of the one-dimensional or two-dimensional code related to the code data; a second storage control means for storing the available time information in a storage means in association with the identification information; The present invention is characterized in that it functions as a

[0010] The invention described in claim 5 is the same as that described in claim 1 to claim 2. 4 In the information processing program according to any one of the preceding claims, The computer If the ticket is a specific group ticket a third storage control means for storing, in the storage means, information on the number of issued tickets, which is information on the number of issued tickets, in association with the identification information; The present invention is characterized in that it further functions as a

[0011] The invention described in claim 6 is 5 In the information processing program described in The specific group ticket of The identification information relating to the tickets is common to all of them, The issued number information is characterized in that it is information relating to the number of issued tickets that include the common identification information.

[0012] The invention described in claim 7 is 5 In the information processing program described in The specific group ticket of the identification information relating to the ticket is unique to each ticket, the third storage control means stores group identification information, which is information indicating that the ticket including the identification information is a ticket included in a specific group ticket, in the storage means in association with the identification information; The information on the number of issues is characterized in that it is information relating to the number of pieces of identification information that are stored in association with the common organization-specific information.

[0013] The invention described in claim 8 is the same as that described in claim 1 to claim 8. 7 In the information processing program according to any one of the preceding claims, The computer of the server device, a third acquisition means for acquiring coupon information, which is information relating to the content of a coupon for receiving a benefit at a predetermined facility; a fourth storage control means for storing the coupon information in the storage means in association with the identification information; The present invention is characterized in that it further functions as a

[0014] The invention described in claim 9 is 1. An information processing method by a server device, a first acquisition step of acquiring ticket content information, which is information relating to the content of a ticket used to board a train; a first storage control step of storing the ticket content information in a storage means; an identification information assigning step of assigning identification information to each of the ticket content information stored in the storage means; a code data creation step of creating code data that is data relating to a one-dimensional or two-dimensional code including the identification information, When multiple tickets are entered when inputting the ticket purchase information, the first acquisition step acquires multiple pieces of ticket content information corresponding to the multiple tickets, the first storage control step stores the plurality of pieces of ticket content information acquired in the first acquisition step in the storage means; the identification information assigning step assigns the common identification information to the plurality of pieces of ticket content information; the code data generating step generates a single code data. It is characterized by:

[0015] The invention described in claim 10 is 1. An information processing method by a server device, an acquisition step of acquiring ticket content information, which is information relating to the content of a ticket used for boarding a train; a storage control step of storing the ticket content information in a storage means; an identification information assigning step of assigning identification information to each of the ticket content information stored in the storage means; a code data creation step of creating code data that is data relating to a one-dimensional or two-dimensional code including the identification information; a fourth acquisition step of further acquiring identification information assigned to the ticket content information desired to be linked with second ticket content information, which is information relating to the content of the additional ticket purchased and used for boarding the train; a fifth storage control step of storing the second ticket content information acquired in the fourth acquisition step in the storage means; a second identification information assigning step of assigning the identification information acquired in the fourth acquisition step to the second ticket content information acquired in the fourth acquisition step; The present invention is characterized by comprising:

[0016] The invention described in claim 11 is a server device, a first acquisition means for acquiring ticket content information, which is information relating to the content of a ticket used to board a train; a first storage control means for storing the ticket content information in a storage means; an identification information assigning means for assigning identification information to each of the ticket content information stored in the storage means; a code data creating means for creating code data which is data relating to a one-dimensional or two-dimensional code including the identification information, When multiple tickets are entered when inputting the ticket purchase information, the first acquisition means acquires multiple ticket contents corresponding to the multiple tickets, the first storage control means stores the plurality of pieces of ticket content information acquired by the first acquisition means in the storage means; the identification information assigning means assigns the common identification information to the plurality of pieces of ticket content information; the code data generating means generates a single code data. It is characterized by:

[0017] The invention described in claim 12 is a server device, an acquisition means for acquiring ticket content information, which is information relating to the content of a ticket used for boarding a train; a storage control means for storing the ticket content information in a storage means; an identification information assigning means for assigning identification information to each of the ticket content information stored in the storage means; a code data generating means for generating code data which is data relating to a one-dimensional or two-dimensional code including the identification information; a fourth acquisition means for further acquiring identification information attached to the ticket content information desired to be linked with second ticket content information, which is information relating to the content of the additionally purchased ticket to be used for boarding the train; a fifth storage control means for causing the storage means to store the second ticket content information acquired by the fourth acquisition means; a second identification information assigning means for assigning the identification information acquired by the fourth acquisition means to the second ticket content information acquired by the fourth acquisition means; The present invention is characterized by comprising: [Effects of the Invention]

[0022] According to the present invention, an information processing program and an information processing method are provided that enable the issuance of tickets that are easy to prevent the use of counterfeit tickets while using one-dimensional or two-dimensional codes. and Server equipment Place can be provided. [Brief explanation of the drawings]

[0023] [Figure 1] 1 is a block diagram showing an outline of the configuration of a ticket information processing system according to an embodiment. [Figure 2] 2 is a block diagram showing the configuration of a ticket information management server in the ticket information processing system according to the embodiment. FIG. [Figure 3] 1 is a block diagram showing a configuration of a ticket reservation server in a ticket information processing system according to an embodiment. [Figure 4] 2 is a block diagram showing the configuration of a ticket issuing server in the ticket information processing system according to the embodiment. FIG. [Figure 5] 1 is a block diagram showing the configuration of a ticket gate device in a ticket information processing system according to an embodiment. [Figure 6] 1 is a block diagram showing the configuration of a counter processing machine in a ticket information processing system according to an embodiment. [Figure 7] 1 is a block diagram showing a configuration of a ticket issuing device in a ticket information processing system according to an embodiment. [Figure 8] 2 is a block diagram showing the configuration of a station attendant terminal in the ticket information processing system according to the embodiment. FIG. [Figure 9] FIG. 2 is a block diagram showing the configuration of a user terminal in the ticket information processing system according to the embodiment. [Figure 10] 3 is a flowchart showing an outline of the overall flow of the operation of the ticket information processing system according to the embodiment. [Figure 11] 10 is a flowchart showing the operation of the ticket information processing system according to the embodiment when a ticket is issued (when the ticket is issued to a user terminal). [Figure 12] 10 is a flowchart showing the operation of the ticket information processing system according to the embodiment when a ticket is issued (when the ticket is issued to a user terminal). [Figure 13] 1 is a diagram showing the data structure of two-dimensional code data issued under normal circumstances in a ticket information processing system according to an embodiment; [Figure 14] 10 is a flowchart showing the operation of the ticket information processing system according to the embodiment when issuing a ticket (when the ticket is issued by the ticket issuing device (when ticket content information is generated by the ticket issuing device)). [Figure 15] 10 is a flowchart showing the operation of the ticket information processing system according to the embodiment when issuing a ticket (when the ticket is issued by the ticket issuing device (when the ticket content information is generated by the ticket information management server)). [Figure 16] 10 is a flowchart showing the operation of the ticket information processing system according to the embodiment when entering or exiting a ticket gate (when the ticket issuing server determines whether or not a ticket is entered or exited). [Figure 17] 10 is a flowchart showing the operation of the ticket information processing system according to the embodiment when entering or exiting a ticket gate (when entry or exit is determined by the ticket gate device). [Figure 18] 10 is a flowchart showing the operation of the ticket information processing system according to the embodiment at the time of web check-in / out. [Figure 19] 10 is a flowchart showing the operation of the ticket information processing system according to the embodiment at the time of collective entry and exit. [Figure 20] 10 is a flowchart showing the operation of the ticket information processing system according to the embodiment at the time of collective entry and exit. [Figure 21] 10 is a flowchart showing the operation of the ticket information processing system according to the embodiment when a station staff member processes entry and exit (when a ticket window processing machine is used). [Figure 22] 10 is a flowchart showing the operation of the ticket information processing system according to the embodiment when a station staff member processes entry and exit (when a station staff terminal is used). [Figure 23] 10 is a flowchart showing the operation of the ticket information processing system according to the embodiment when entering and exiting a ticket gate in the event of a communication failure. [Figure 24] 10 is a flowchart showing the operation of the ticket information processing system according to the embodiment during processing after recovery from a communication failure (when entry and exit determination is performed by the ticket issuing server). [Figure 25] 10 is a flowchart showing the operation of the ticket information processing system according to the embodiment during processing after recovery from a communication failure (when entry / exit determination is performed at the ticket gate device). [Figure 26] 10 is a flowchart showing the operation of the ticket issuing device when issuing a ticket in the event of a communication failure in the ticket information processing system according to the embodiment. [Figure 27] 10 is a diagram showing the data structure of two-dimensional code data issued in the event of a failure in the ticket information processing system according to the embodiment. FIG. [Figure 28] 10 is a flowchart showing the operation of the ticket information processing system according to the embodiment when entering and exiting a ticket gate using a ticket issued during a communication failure. [Figure 29] This is a block diagram showing the configuration of a ticket issuing server for issuing two-dimensional codes with the same content to multiple users in a modified example of a group ticket of the ticket information processing system of the embodiment (modification example 1 of step S1 and modification example 1 of step S2 in the operation explanation). [Figure 30] This is a block diagram showing the configuration of a ticket issuing server for issuing two-dimensional codes with different contents to multiple users in a modified example of a group ticket of the ticket information processing system of the embodiment (modification example 1 of step S1 and modification example 1 of step S2 in the operation explanation). [Figure 31] FIG. 10 is a block diagram showing an outline of the configuration of a variation (variation 2 of step S1 and variation 2 of step S2 in the explanation of the operation) relating to the unified management of tickets and coupons of the ticket information processing system according to the embodiment. [Figure 32] 10 is a flowchart showing the operation when a coupon is used (variation 2 of step S2 in the explanation of the operation) in a variation relating to the unified management of tickets and coupons in the ticket information processing system according to the embodiment. [Figure 33] FIG. 10 is a block diagram showing an outline of the configuration of a modified example (modification 4 of step S2 in the explanation of the operation) relating to the display of a pop-up in front of a ticket gate device of the ticket information processing system according to the embodiment. [Figure 34] 10 is a flowchart showing the operation of a modified example (modification 4 of step S2 in the explanation of the operation) relating to the display of a pop-up in front of a ticket gate device of the ticket information processing system according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0024] A ticket information processing system 100 according to an embodiment of the present invention will be described below with reference to Figures 1 to 34. However, the technical scope of the present invention is not limited to the illustrated examples.

[0025] [First Configuration Explanation] The ticket information processing system 100 is a system for providing users of the system with tickets using a predetermined one-dimensional or two-dimensional code, and for assisting them in entering and exiting ticket gates using the tickets.As shown in Figure 1, the system is composed of various servers managed by a company that manages and operates the ticket information processing system 100, namely, a ticket information management server 1, a ticket reservation server 2, and a ticket issuing server 3, as well as ticket gate devices 4, counter processing machines 5, and ticket issuing devices 6 installed at each station on the railway line, station staff terminals 7 carried by each station staff member at the station, and user terminals 8 carried by each user of the system. As shown in FIG. 1, the devices are connected to each other via a communication network N.

[0026] It should be noted that the above-mentioned servers do not necessarily have to be provided separately, and a single information device such as a PC (Personal Computer) or WS (Work Station) may also function as multiple servers. Conversely, each of the above servers does not necessarily have to be realized by a single information device such as a PC or WS, and the functions of each server may be realized by a plurality of information devices such as a plurality of PCs or WSs connected via a communication network N. Also, the ticket gate device 4, the counter processing machine 5, the ticket issuing device 6, the station attendant terminal 7, and the user terminal 8 do not necessarily have to be realized by a single device, and may be realized by a plurality of devices.

[0027] [1 Ticket information management server] The ticket information management server 1 is an information device such as a PC or WS, and as described below, manages information required for issuing tickets, such as operating train information D3 and reservation status information D4, and also generates ticket content information D2 and transmits it to other servers. As shown in FIG. 2, the ticket information management server 1 includes, for example, a control unit 11, a storage unit 12, and a communication unit 13.

[0028] The control unit 11 is the part that controls the operation of the ticket information management server 1, and is configured with, for example, a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), etc., and controls each part of the ticket information management server 1 in cooperation with the CPU and programs stored in the ROM expanded in the working area of ​​the RAM and the memory unit 12.

[0029] The memory unit 12 is a part where various information required for the operation of the ticket information management server 1 is stored, and is composed of, for example, an HDD (Hard Disk Drive), semiconductor memory, etc., and stores data required for the operation of the ticket information management server 1, such as program data, in a manner that allows it to be read and written by the control unit 11.

[0030] The storage unit 12 includes a ticket content information issuing program 121, a running train information storage unit 122 in which running train information D3 is stored, and a reservation status information storage unit 123 in which reservation status information D4 is stored.

[0031] The ticket content information issuance program 121 is a program that includes various commands to the control unit 11 for operating the ticket information management server 1, and the operation of the ticket information management server 1 described in the operation explanation below will be performed in accordance with the ticket content information issuance program 121. The information stored in each storage unit will be described in detail in the explanation of the operation.

[0032] The communication unit 13 is a part used for communication between the ticket information management server 1 and the ticket reservation server 2, ticket issuing server and ticket issuing device 6, and is, for example, a communication interface having a communication IC (Integrated Circuit) and a communication connector, and performs data communication via the communication network N using a predetermined communication protocol under the control of the control unit 11.

[0033] [2 Ticket Reservation Server] The ticket reservation server 2 is, for example, an information device such as a PC or a WS, and acquires information relating to tickets that users wish to purchase from user terminals 8, as will be described later. As shown in FIG. 3, the ticket reservation server 2 is configured to include, for example, a control unit 21, a storage unit 22, and a communication unit 23, similar to the ticket information management server 1.

[0034] The configurations of the control unit 21 and the communication unit 23 are the same as those of the control unit 11 and the communication unit 13 in the ticket information management server 1, respectively. The memory unit 22, like the memory unit 12 in the ticket information management server 1, is composed of, for example, an HDD (Hard Disk Drive), semiconductor memory, etc., and is equipped with a ticket reservation program 221, a ticket information memory unit 222 in which ticket content information D2, ticket purchase information D6, ticket reservation information D8, and ticket number information D11 are stored, and a railway station information memory unit 223 in which railway station information D27 is stored.

[0035] The ticket reservation program 221 is a program that includes various commands to the control unit 21 for operating the ticket reservation server 2, and the operation of the ticket reservation server 2 described below in the operation explanation will be performed in accordance with the ticket reservation program 221. The information stored in each storage unit will be described in detail in the explanation of the operation.

[0036] In addition, as shown in Figure 1, the ticket reservation server 2 is connected to the ticket information management server 1, ticket issuing server 3, station attendant terminal 7 and user terminal 8 via a communication network N by a communication unit 23, and data can be sent and received between the ticket information management server 1, ticket issuing server 3, station attendant terminal 7 and user terminal 8.

[0037] [3 Ticket issuing server] The ticket issuing server 3 is, for example, an information device such as a PC or a WS, and generates data relating to a two-dimensional code used as a ticket, as will be described later. As shown in FIG. 4, the ticket issuing server 3 is configured to include, for example, a control unit 31, a storage unit 32, and a communication unit 33, similar to the ticket information management server 1 and the like.

[0038] The configurations of the control unit 31 and the communication unit 33 are the same as those of the control unit 11 and the communication unit 13 in the ticket information management server 1, respectively. The memory unit 32, like the memory unit 12 in the ticket information management server 1, is composed of, for example, an HDD (Hard Disk Drive), semiconductor memory, etc., and is equipped with a ticket issuance program 321, a ticket information memory unit 322 in which ticket content information D2, ticket purchase information D6, ticket identifier information D10, and ticket number information D11 are stored, an encoding information memory unit 323 in which general encoding information D13 is stored, and a testing processing information memory unit 324 in which general testing processing information D15 is stored.

[0039] The ticket issuance program 321 is a program that includes various instructions to the control unit 31 for operating the ticket issuance server 3, and the operation of the ticket issuance server 3 described in the operation explanation below is performed in accordance with the ticket issuance program 321. The information stored in each storage unit will be described in detail in the explanation of the operation.

[0040] In addition, as shown in Figure 1, the ticket issuing server 3 is connected to the ticket information management server 1, ticket reservation server 2, ticket gate device 4, counter processing machine 5, and ticket issuing device 6 via a communication network N by a communication unit 33, and data can be sent and received between the ticket information management server 1, ticket reservation server 2, ticket gate device 4, counter processing machine 5, and ticket issuing device 6.

[0041] [4 Ticket gates] The ticket gate device 4 is a device installed at each station on a railway line that automatically performs ticket gate operations such as determining whether or not a person can enter or exit the ticket gate, and as described below, opens and closes the opening / closing section 45 depending on whether or not a user holding a ticket can enter or exit the ticket gate. As shown in Figure 5, the ticket gate device 4 is configured to include, similar to the ticket information management server 1, for example, a control unit 41, a memory unit 42, and a communication unit 43, as well as a ticket information reading unit 44 and an opening / closing unit 45.

[0042] The configurations of the control unit 41 and the communication unit 43 are the same as those of the control unit 11 and the communication unit 13 in the ticket information management server 1, respectively. The memory unit 42, like the memory unit 12 in the ticket information management server 1, is composed of, for example, an HDD (Hard Disk Drive), semiconductor memory, etc., and is provided with an entry / exit processing program 421, a test processing information memory unit 422 in which general test processing information D15 and special test processing information D50 are stored, an equipment information memory unit 423 in which ticket gate device installation station information D18 and ticket gate device equipment information D19 are stored, an encoding information memory unit 424 in which special encoding information D45 is stored, and a communication failure ticket information memory unit 425 in which normal-time issued two-dimensional code data D12, communication failure entry / exit date and time information D38, communication failure entry / exit station information D39, and communication failure entry / exit processing flag D40 are stored.

[0043] The entry / exit processing program 421 is a program that includes various commands to the control unit 41 for operating the ticket gate device 4, and the operation of the ticket gate device 4 described in the operation explanation below will be performed in accordance with the entry / exit processing program 421. The information stored in each storage unit will be described in detail in the explanation of the operation.

[0044] As shown in FIG. 1, the ticket gate device 4 is connected to the ticket issuing server 3 via a communication network N by a communication unit 43, and is capable of transmitting and receiving data to and from the ticket issuing server 3.

[0045] The ticket information reader 44 is a part for reading the stored contents of a ticket issued using a predetermined one-dimensional or two-dimensional code as described below, and is made up of a reader for a predetermined one-dimensional or two-dimensional code corresponding to the type of code used when issuing the ticket. When a user holds the ticket over the ticket information reader 44, it reads the stored contents of the ticket.

[0046] The opening / closing section 45 is a means for switching the ticket gate device 4 between an open state and a closed state, and has a fence that can be opened and closed. As described below, based on the determination result regarding whether the user can enter or exit the station where the ticket gate device 4 is installed, the opening section 45 opens the gate when entry or exit is permitted, and the closing section 45 closes the gate when entry or exit is not permitted.

[0047] In addition, in an unused state where the user is not holding the ticket over the ticket information reading unit 44 and the ticket gate device 4 is not being used, the opening / closing unit 45 may be in either the open state or the closed state. However, it is preferable that, after setting it to the open state in an unused state, it remains in the open state when a user who holds a ticket is permitted to enter or exit, and that it is set to the closed state when a user who holds a ticket is not permitted to enter or exit, or when a user attempts to enter or exit without holding a ticket. In the present invention, keeping the opening / closing section 45 in an open state when the user holds a ticket over it, even if the opening / closing section 45 is in an open state when not in use, is also considered to be included in keeping the opening / closing section 45 in an open state.

[0048] [5 Counter Processing Machine] The ticket counter processing machine 5 is a terminal used by station staff installed at each station on the railway line, and is originally used, for example, by station staff to process fares for passengers who have missed their destination. However, in this embodiment, as described below, it is used when station staff make decisions regarding whether or not a user can enter or exit the ticket gate, for example, when the ticket gate device 4 cannot be used due to a problem, or at stations that do not have ticket gate devices 4. As shown in Figure 6, the counter processing machine 5 is configured to include, for example, a control unit 51, a memory unit 52, and a communication unit 53, similar to the ticket information management server 1, and further includes a display unit 54, an operation unit 55, and a ticket information reading unit 56.

[0049] The configurations of the control unit 51 and the communication unit 53 are the same as those of the control unit 11 and the communication unit 13 in the ticket information management server 1, respectively. The storage unit 52, like the storage unit 12 in the ticket information management server 1, is configured with, for example, an HDD (Hard Disk Drive), a semiconductor memory, etc., and is provided with a counter processing application 521. The counter processing application 521 is a program that includes various instructions to the control unit 51 for operating the counter processing machine 5, and the operation of the counter processing machine 5 described in the operation explanation below will be performed in accordance with the counter processing application 521.

[0050] As shown in FIG. 1, the counter processing machine 5 is connected to the ticket issuing server 3 via a communication network N by a communication unit 53, and is capable of sending and receiving data to and from the ticket issuing server 3.

[0051] The display unit 54 includes a display such as an LCD (Liquid Crystal Display), and displays an image based on the display control signal output from the control unit 51 on the display screen.

[0052] The operation unit 55 includes, for example, a keyboard having character input keys, number input keys, and other keys associated with various functions, and receives operation input from a user of the ticket counter processing machine 5, such as a station attendant, and outputs an operation signal corresponding to the operation input to the control unit 51. The operation unit 55 may be, for example, a touch panel formed integrally with the display unit 54, and is not particularly limited as long as it can receive operation input from a user of the ticket counter processing machine 5.

[0053] The ticket information reading unit 56 is a part for reading the stored contents of a ticket issued using a predetermined one-dimensional or two-dimensional code as described below, and is made up of a one-dimensional or two-dimensional code reader that corresponds to the type of code used when issuing the ticket. The ticket information reading unit 56 reads the stored contents of the ticket when a station attendant holds the ticket to be used by the user over the ticket.

[0054] [6 Ticket issuing device] The ticket issuing device 6 is a device installed at each station on a railway line and used by users when purchasing tickets to board trains. In this embodiment, as described below, it is used when issuing tickets with a specified one-dimensional or two-dimensional code on a specified medium such as paper. As shown in Figure 7, the ticket issuing device 6 is configured to include, for example, a control unit 61, a memory unit 62, a communication unit 63, a display unit 64, and an operation unit 65, similar to the counter processing machine 5, and further includes a ticket issuing unit 66.

[0055] The configurations of the control unit 61, communication unit 63, display unit 64 and operation unit 65 are the same as those of the control unit 51, communication unit 53, display unit 54 and operation unit 55 in the counter processing machine 5, respectively. The memory unit 62, like the memory unit 52 in the counter processing machine 5, is composed of, for example, an HDD (Hard Disk Drive), semiconductor memory, etc., and is equipped with a ticket content information issuance program 621, an encoding information memory unit 622 in which special encoding information D45 is stored, a test processing information memory unit 623 in which special test processing information D50 is stored, a running train information memory unit 624 in which running train information D3 is stored, and a reservation status information memory unit 625 in which reservation status information D4 is stored.

[0056] The ticket content information issuance program 621 is a program that includes various commands to the control unit 61 for operating the ticket issuing device 6, and the operation of the ticket issuing device 6 described in the operation explanation below will be performed in accordance with the ticket content information issuance program 621. The information stored in each storage unit will be described in detail in the explanation of the operation.

[0057] In addition, as shown in Figure 1, the ticket issuing device 6 is connected to the ticket information management server 1 and the ticket issuing server 3 via a communication network N by a communication unit 63, and is capable of sending and receiving data between the ticket issuing server 3.

[0058] The ticket issuing unit 66 is a part that issues tickets to users under the control of the control unit 61, and in this embodiment, it issues tickets with a specified one-dimensional code or two-dimensional code based on data received from the ticket issuing server 3 as described below, on a specified medium such as paper.

[0059] [7 Station staff terminal] The station staff terminal 7 is an information device such as a smartphone or tablet terminal carried by station staff at each station on the railway line, and as described below, like the counter processing machine 5, it is used when station staff make decisions regarding whether or not a user can enter or exit the ticket gate. As shown in Figure 8, the station attendant terminal 7 is configured to include a control unit 71, a memory unit 72, a communication unit 73, a display unit 74, an operation unit 75, and further includes an imaging unit 76, similar to, for example, a counter processing machine 5.

[0060] The configurations of the control unit 71, communication unit 73, display unit 74 and operation unit 75 are the same as those of the control unit 51, communication unit 53, display unit 54 and operation unit 55 in the counter processing machine 5, respectively. The storage unit 72, like the storage unit 52 in the counter processing machine 5, is configured with, for example, an HDD (Hard Disk Drive), a semiconductor memory, etc., and is provided with an application 721 for station attendant terminals. The station attendant terminal application 721 is a program that includes various commands to the control unit 71 for operating the station attendant terminal 7, and the operation of the station attendant terminal 7 described in the operation explanation below will be performed in accordance with the station attendant terminal application 721.

[0061] Furthermore, the station attendant terminal 7 is connected to the ticket reservation server 2 via a communication network N through a communication unit 73, and is capable of transmitting and receiving data to and from the ticket reservation server 2.

[0062] The imaging unit 76 has, for example, an optical system such as a lens and an imaging element such as a CMOS (Complementary Metal Oxide Semiconductor) sensor or a CCD (Charge Coupled Device) sensor, and captures an image (including a moving image) in the optical axis direction of the lens. The imaging unit 76 outputs the captured image data to the control unit 71.

[0063] [8 User Terminals] The user terminal 8 is an information device such as a smartphone or tablet terminal carried by each user who receives tickets using this system, and is used when entering or exiting the ticket gate device 4 using a ticket issued using a specified one-dimensional or two-dimensional code, as described below. As shown in Figure 9, the user terminal 8 is configured to include, for example, a control unit 81, a memory unit 82, a communication unit 83, a display unit 84, an operation unit 85, and an imaging unit 86, similar to the station staff terminal 7, and further includes a location information acquisition unit 87.

[0064] The configurations of the control unit 81, communication unit 83, display unit 84, operation unit 85 and imaging unit 86 are the same as those of the control unit 71, communication unit 73, display unit 74, operation unit 75 and imaging unit 76 in the station staff terminal 7, respectively. The memory unit 82, like the memory unit 72 in the station attendant terminal 7, is composed of, for example, an HDD (Hard Disk Drive), semiconductor memory, etc., and is equipped with a user terminal application 821 and a ticket information memory unit 822 in which normally issued two-dimensional code image data D16, ticket number information D11, ticket reservation information D8, and accompanying person two-dimensional code image data D33 are stored.

[0065] The user terminal application 821 is a program that includes various instructions to the control unit 81 for operating the user terminal 8, and the operation of the user terminal 8 described in the operation explanation below will be performed in accordance with the user terminal application 821. The information stored in each storage unit will be described in detail in the explanation of the operation.

[0066] The user terminal 8 is also connected to the ticket reservation server 2 via a communication network N through a communication unit 83, and is capable of transmitting and receiving data to and from the ticket reservation server 2.

[0067] The location information acquisition unit 87 is a part that acquires information about the location of the user terminal 8, and for example, a GPS (Global Positioning System) receiver is used. The GPS receiver receives GPS signals, which are positioning radio waves provided by multiple GPS satellites that make up the GPS, and uses these to acquire location information of the user terminal 8, and ultimately of the user who owns it. The location information acquisition unit 87 is not limited to a GPS receiver as long as it can acquire location information of the user terminal 8. For example, a receiver for signals related to other satellite positioning systems, such as a QZSS (Quasi-Zenith Satellite System) receiver, may also be used.

[0068] [9 Communication Network] The communication network N is, for example, the Internet, a telephone line network, a mobile phone communication network, a wireless LAN communication network, etc., and connects the devices that make up the ticket information processing system 100 as shown in FIG. The communication network N is not particularly limited as long as it can connect the devices as described above and transmit and receive data between them.

[0069] [Second operation explanation] The operation of the ticket information processing system 100 according to this embodiment when in use will be described below. As shown in the flowchart of Figure 10, the operation of the ticket information processing system 100 is roughly divided into nine steps, from step S1 to step S9. Note that although the following will be described in the order of steps S1 to S9, the order in which these steps are performed is not limited to this. For example, steps S2 to S6 all relate to entry / exit processing, and in reality, they are processed in parallel.

[0070] [1 Step S1: Issuing a ticket] First, we will explain the operation of this system when issuing a ticket to a user to use for boarding a train, dividing it into cases where the ticket is issued to the user terminal 8 using data, and where the ticket is issued by the ticket issuing device 6 using a specified medium such as paper.

[0071] [(1) Operational flow] [A Step S11: Issuance to user terminal] First, the flow of operations when a ticket is issued to the user terminal 8 using data will be described with reference to the flowcharts of FIGS.

[0072] When a user wishes to use this system to receive a ticket for use on a train, the user first uses the operation unit 85 of the user terminal 8 to input information about the ticket they wish to reserve, i.e., the desired ticket purchase information D1, which includes information about the train's boarding station, disembarking station, departure time, arrival time, seat number, etc. (step S11-1). Once the desired ticket purchase information D1 has been input, the control unit 81 transmits the input information from the communication unit 83 to the ticket reservation server 2 via the communication network N (step S11-2).

[0073] The user can input information about the ticket they wish to reserve by, for example, specifying the train and seat they wish to reserve on a specific ticket reservation website provided by the ticket reservation server 2, which is configured to allow the user to specify the train, seat, boarding station, and disembarking station they wish to reserve. Alternatively, a predetermined application may be downloaded in advance to the storage unit 82 of the user terminal 8, and input may be performed in accordance with the application.

[0074] In the ticket reservation server 2, when the communication unit 23 receives the desired ticket purchase information D1, the control unit 21 transmits the received desired ticket purchase information D1 from the communication unit 23 to the ticket information management server 1 via the communication network N, together with a predetermined request to transmit ticket content information D2 corresponding to the data (step S11-3).

[0075] In the ticket information management server 1, when the communication unit 13 receives the desired ticket purchase information D1 and a request to send ticket content information D2, the control unit 11 checks the train's seat availability based on the running train information D3 stored in the running train information storage unit 122 and the reservation status information D4 stored in the reservation status information storage unit 123 if a seat needs to be reserved, and if it is possible to purchase a ticket for the seat on the train for which the user wishes to purchase a ticket, as related to the desired ticket purchase information D1, generates corresponding ticket content information D2 (step S11-4).

[0076] Ticket content information D2 is information that describes the contents of the ticket to be used to board the train corresponding to the ticket purchase information D1, and includes, for example, information such as the specific ticket validity area (boarding station, disembarking station, intermediate stations, etc.) and the validity period of the ticket.

[0077] In addition, ticket content information D2 includes the status of the ticket, i.e., entry and exit history, and information regarding the section traveled, specifically, information regarding the state of each ticket, such as unused (before entry), used (after exiting at the disembarking station), in use (after entry but before exiting), in use (after exiting at an intermediate station), etc.

[0078] For example, immediately after purchasing a ticket, the status stored will indicate that the ticket is unused, and when use begins (for example, entering through ticket gate device 4), the status will be updated to indicate that the ticket is in use (after entry but before exiting), and when the ticket exits at an intermediate station, the status will be updated to indicate that the ticket is in use (after exiting from the intermediate station), and when use is completed (exiting through ticket gate device 4 at the disembarking station), the status will be updated to indicate that the ticket has already been used.

[0079] Once the ticket content information D2 is generated, the control unit 11 in the ticket information management server 1 transmits the generated ticket content information D2 together with the purchase result information D5 to the ticket reservation server 2 from the communication unit 13 via the communication network N (step S11-5). The purchase result information D5 is information regarding whether or not the user can purchase the ticket corresponding to the ticket purchase request information D1, and when the ticket content information D2 is generated, the information necessarily indicates that the ticket is available for purchase. Note that if the user is unable to purchase the ticket corresponding to the ticket purchase request information D1, the ticket content information D2 is not sent, and only the purchase result information D5 indicating that the ticket is unavailable is sent to the ticket reservation server 2.

[0080] In the ticket reservation server 2, when the communication unit 23 receives the ticket content information D2 and the purchase result information D5, the control unit 21 transmits the purchase result information D5 from the communication unit 23 via the communication network N to the user terminal 8 that transmitted the desired ticket purchase information D1 in step S11-2 (step S11-6), and in the user terminal 8 that receives this via the communication unit 83, the control unit 81 displays the ticket purchase result on the display unit 84 based on the received data (step S11-7).

[0081] Once the ticket reservation server 2 has completed sending the purchase result information D5 to the user terminal 8, it then generates ticket purchase information D6 and ticket reservation information D8 relating to the ticket purchased by the user, links these to the ticket content information D2, and stores them in the ticket information storage unit 222 of the storage unit 22 (step S11-8).

[0082] Ticket purchase information D6 is information for linking together information related to an issued ticket, such as ticket content information D2, purchase result information D5, and ticket reservation information D8, including ticket purchase number information D7, which is information related to the purchase number assigned to each ticket. Ticket purchase information D6 also includes information related to the content of the ticket corresponding to the desired ticket purchase information D1, and information related to the ticket status, similar to that included in ticket content information D2. Ticket reservation information D8 is data relating to the specific reservation details made by the user for the reserved ticket, which is managed by the ticket reservation server 2. The ticket reservation information also includes information relating to the contents of the ticket corresponding to the desired ticket purchase information D1, similar to that contained in the ticket content information D2, and information relating to the status of the ticket.

[0083] In the ticket reservation server 2, once the above data is generated, the control unit 21 transmits the ticket content information D2 and ticket purchase information D6 to the ticket issuing server 3 from the communication unit 23 via the communication network N (step S11-9). In the ticket issuing server 3 that receives this data via the communication unit 33, the control unit 31 links the received ticket content information D2 and ticket purchase information D6 and stores them in the ticket information memory unit 322 of the memory unit 32 (step S11-10).

[0084] In addition, the transmission of ticket content information D2 and ticket purchase information D6 from ticket reservation server 2 to ticket issuing server 3 in step S11-9 does not necessarily have to be performed immediately after the generation of ticket purchase information D6 and ticket reservation information D8 in step S11-8, and for example, multiple pieces of ticket content information D2 and ticket purchase information D6 may be sent to ticket issuing server 3 together at a predetermined timing.

[0085] After the information has been stored in the ticket reservation server 2 and the ticket issuance server 3 as described above, if the user wishes to have a two-dimensional code issued for the purchased ticket, the user first uses the operation unit 85 of the user terminal 8 to input specified information (ticket issuance request information D9) requesting the issuance of a ticket with a two-dimensional code (step S11-11).Once the ticket issuance request information D9 has been input, the control unit 81 of the user terminal 8 transmits the input information from the communication unit 83 to the ticket reservation server 2 via the communication network N (step S11-12).

[0086] The user can input information relating to the ticket for which he / she wishes to have a two-dimensional code issued by selecting the ticket for which he / she wishes to have a two-dimensional code issued from a list of ticket reservation information D8 relating to tickets that the user has already purchased and that is stored on the ticket reservation server 2 on a specific website that is configured to allow the user to select the ticket for which he / she wishes to have a two-dimensional code issued from the list of ticket reservation information D8 provided by the ticket reservation server 2 and that is stored on the ticket reservation server 2. Alternatively, a predetermined application may be downloaded in advance to the storage unit 82 of the user terminal 8, and input may be performed in accordance with the application.

[0087] In the ticket reservation server 2, when the communication unit 23 receives the ticket issuance request information D9, the control unit 21 searches the ticket information storage unit 222 of the storage unit 22 based on the received ticket issuance request information D9, extracts the corresponding ticket purchase information D6, and transmits the ticket purchase number information D7 included in the extracted ticket purchase information D6 from the communication unit 23 to the ticket issuance server 3 via the communication network N, together with static / dynamic issuance identification information D51, which is information regarding whether the issued two-dimensional code is a static one with no time limit for use, or a dynamic one with a time limit for use that must be generated in real time by the user at the time of use (step S11-13).

[0088] In the ticket issuing server 3, when the communication unit 33 receives the ticket purchase number information D7 included in the ticket purchase information D6 related to the ticket issuance request information D9, the control unit 31 extracts the corresponding ticket purchase information D6 stored in the ticket information storage unit 322 of the storage unit 32 in accordance with the received ticket purchase number information D7, sets an ID (identifier) ​​for each extracted ticket purchase information D6 according to a predetermined rule, generates ticket identifier information D10, which is information related to an identifier to be assigned to each normally-issued two-dimensional code data D12 (described below), assigns a number, generates ticket number information D11, which is information related to the number to be assigned to each normally-issued two-dimensional code data D12 (described below), and stores the ticket number information D11 in the ticket information storage unit 322 of the storage unit 32 in association with the corresponding ticket content information D2 and ticket purchase information D6 (step S11-14). Both the ticket identifier information D10 and the ticket number information D11 are identification information assigned to each ticket that can identify each ticket.

[0089] Next, the control unit 31 uses the ticket purchase information D6 and the generated ticket identifier information D10 to create normally issued two-dimensional code data D12 in accordance with a predetermined two-dimensional code format (step S11-15). As the two-dimensional code format, for example, a format related to QR Code (registered trademark) can be used.

[0090] In addition, when creating the normally issued two-dimensional code data D12, the control unit 31 refers to the received static / dynamic issuance identification information D51, and if this information indicates that the two-dimensional code to be issued is dynamic, it generates two-dimensional code usage time information D52, which is information related to the usage time of the two-dimensional code related to the normally issued two-dimensional code data D12 to be created, and stores the generated two-dimensional code usage time information D52 in the ticket information storage unit 322 of the storage unit 32, linked to the corresponding ticket content information D2, ticket purchase information D6, ticket identifier information D10, and ticket number information D11. The two-dimensional code available time information D52 may be set, for example, in the form of the time when the normally issued two-dimensional code data D12 was created in step S11-15 and a predetermined time (such as 5 minutes) from that time.

[0091] The two-dimensional code data D12 issued under normal circumstances is the original data for a two-dimensional code created according to a predetermined two-dimensional code format. Note that this data is distinguished from the two-dimensional code data D44 issued under a fault, which will be described later, in that it is data issued through the procedure of this step under normal circumstances when no communication fault occurs. Although it is not preferable in terms of the relationship between the data capacity and the area, it is possible to use a one-dimensional code instead of a two-dimensional code. This also applies to all steps described below.

[0092] The normally-issued two-dimensional code data D12 has multiple storage areas, for example, a basic information section D12-1 and a validity verification section D12-2 as shown in Fig. 13, and only a portion of the information in the basic information section D12-1 is encoded using general encoding information D13 stored in the encoding information storage section 323 of the storage unit 32. The general encoding information D13 is data relating to a predetermined conversion rule that the ticket issuing server 3 uses when encoding the normally-issued two-dimensional code data D12.

[0093] The basic information section D12-1 includes attribute information related to the issuing company, the issuance date, etc., as well as the ticket identifier information D10 generated in step S11-14. The ticket identifier information D10 is included in the information encoded using the general encoding information D13.

[0094] The validity testing section D12-2 also includes general testing information D14, which is information related to the results of a predetermined conversion or calculation for testing based on the data included in the basic information section D12-1. The general testing information D14 is generated by the control section 31 inputting the data included in the basic information section D12-1 into a predetermined conversion rule or calculation formula stored as general testing processing information D15 in the testing processing information storage section 324 of the storage section 32.

[0095] Once the normally issued two-dimensional code data D12 is generated, the control unit 31 of the ticket issuing server 3 transmits the generated normally issued two-dimensional code data D12 together with the corresponding ticket number information D11 from the communication unit 33 via the communication network N to the ticket reservation server 2 (step S11-16). In addition, when the control unit 31 generates the two-dimensional code usage time information D52 in step S11-15, it also transmits the two-dimensional code usage time information D52, together with the ticket number information D11 and the normally issued two-dimensional code data D12, from the communication unit 33 via the communication network N to the ticket reservation server 2.

[0096] In the ticket reservation server 2, when the communication unit 23 receives the information transmitted from the ticket issuing server 3, the control unit 21 stores the received ticket number information D11 in the ticket information storage unit 222 of the storage unit 22 in association with the corresponding ticket content information D2, ticket purchase information D6, and ticket reservation information D8, and then generates normally issued two-dimensional code image data D16, which is data converted from the received normally issued two-dimensional code data D12 into image data, based on the received normally issued two-dimensional code data D12 (step S11-17). In addition, when two-dimensional code usage time information D52 is received from the ticket issuing server 3, the control unit 21 also stores the two-dimensional code usage time information D52 in the ticket information storage unit 222 of the storage unit 22, linking it to the corresponding ticket content information D2, ticket purchase information D6, ticket reservation information D8, and ticket number information D11.

[0097] After generating the normally issued two-dimensional code image data D16, the control unit 21 transmits the generated data, together with the corresponding ticket number information D11 and ticket reservation information D8, from the communication unit 23 via the communication network N to the user terminal 8 (step S11-18).

[0098] Also, when the above transmission process is completed, in the ticket reservation server 2, the control unit 21 updates the information related to the status of the ticket, which is contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 related to the ticket stored in the ticket information storage unit 222 of the storage unit 22, to information indicating that a two-dimensional code has been issued (step S11-19), and transmits the status update information D17 at the time of issuance of the two-dimensional code, which is information related to the content of the status update, to the ticket issuing server 3 (step S11-20).Similarly, in the ticket issuing server 3, the control unit 31 updates the information related to the status of the ticket, which is contained in the ticket content information D2 and ticket purchase information D6 related to the ticket stored in the ticket information storage unit 322 of the storage unit 32, to information indicating that a two-dimensional code has been issued (step S11-21).

[0099] In step S11-19, it is also possible to update only the information relating to the ticket status contained in the ticket purchase information D6 and the ticket reservation information D8, without updating the information relating to the ticket status contained in the ticket content information D2.

[0100] In the user terminal 8, when the communication unit 83 receives the normally issued two-dimensional code image data D16, ticket number information D11, and ticket reservation information D8, the control unit 81 links the received data and stores it in the ticket information memory unit 822 of the memory unit 82 (step S11-22). This makes it possible for the user terminal 8 to display on the display unit 84 an image of the two-dimensional code related to the normally issued two-dimensional code image data D16 stored in the ticket information memory unit 822 of the memory unit 82 and the ticket number related to the ticket number information D11.

[0101] Alternatively, instead of generating the normally issued two-dimensional code image data D16 in the ticket reservation server 2, the control unit 21 of the ticket reservation server 2 may transmit the normally issued two-dimensional code data D12 from the communication unit 23 to the user terminal 8 via the communication network N instead of the normally issued two-dimensional code image data D16, and upon receiving this, the control unit 81 of the user terminal 8 may generate the normally issued two-dimensional code image data D16 in accordance with the user terminal application 821, thereby acquiring the normally issued two-dimensional code image data D16.

[0102] Step S12: Issuance by the ticket issuing device Next, the operational flow when a ticket is issued by the ticket issuing device using a specified medium such as paper will be explained separately for the case when ticket content information D2 is generated by the ticket issuing device 6 and the case when ticket content information D2 is generated by the ticket information management server 1.

[0103] (A) Step S121: When ticket content information is generated in the ticket issuing device First, the flow of operations when ticket content information D2 is generated in ticket issuing device 6 will be described with reference to the flowchart of FIG.

[0104] When a user wishes to have a ticket issued for use on a train by the ticket issuing device 6, the user first uses the operation unit 65 of the ticket issuing device 6 to input information about the ticket they wish to reserve, i.e., the ticket purchase information D1, which includes, for example, information about the train's boarding station, disembarking station, departure time, arrival time, seat number, etc., and then performs the required purchase operation (step S121-1).

[0105] The user may input information relating to the ticket he or she wishes to reserve by, for example, using the operation unit 65 to specify the train and seat he or she wishes to reserve, in accordance with a predetermined ticket reservation screen displayed on the display unit 64 of the ticket issuing device 6 and configured to allow the user to specify the train and seat he or she wishes to reserve.

[0106] When the desired ticket purchase information D1 is input, the control unit 61 generates ticket purchase information D6 based on the input information (step S121-2).

[0107] Next, the control unit 61 checks the availability of seats on the train based on the operating train information D3 stored in the operating train information storage unit 624 and the reservation status information D4 stored in the reservation status information storage unit 625, and if it is possible to purchase a ticket for the seat on the train for which the user related to the ticket purchase information D6 wishes to purchase a ticket, generates corresponding ticket content information D2 (step S121-3).

[0108] After generating the ticket content information D2, the control unit 61 transmits the ticket content information D2 generated in step S121-3 together with the ticket purchase information D6 generated in step S121-2 from the communication unit 63 via the communication network N to the ticket issuing server 3 (step S121-4).

[0109] In the ticket issuing server 3, when the communication unit 33 receives the ticket content information D2 and the ticket purchase information D6, the control unit 31 links the received ticket content information D2 and the ticket purchase information D6 and stores them in the ticket information memory unit 322 of the memory unit 32 (step S121-5).

[0110] Next, the control unit 31 of the ticket issuing server 3 sets an ID (identifier) ​​for each ticket purchase information D6 in accordance with a predetermined rule, generates ticket identifier information D10, assigns a number, generates ticket number information D11, and stores it in the ticket information storage unit 322 of the storage unit 32 in association with the corresponding ticket content information D2 and ticket purchase information D6 (step S121-6).

[0111] Next, the control unit 31 generates normally issued two-dimensional code data D12 in accordance with a predetermined two-dimensional code format using the ticket purchase information D6 and the generated ticket identifier information D10 (step S121-7).

[0112] When the normally issued two-dimensional code data D12 is generated, the control unit 31 of the ticket issuing server 3 transmits the generated normally issued two-dimensional code data D12 together with the corresponding ticket number information D11 from the communication unit 33 via the communication network N to the ticket issuing device 6 (step S121-8).

[0113] In the ticket issuing device 6, when the communication unit 63 receives the normally issued two-dimensional code data D12 and the ticket number information D11, the control unit 61 generates normally issued two-dimensional code image data D16 based on the normally issued two-dimensional code data D12, and then causes the ticket issuing unit 66 to issue a ticket on which the two-dimensional code related to the normally issued two-dimensional code image data D16 and the number related to the ticket number information D11 are stored by printing or other means on a predetermined medium such as paper (step S121-9).

[0114] When the ticket issuance is completed, the control unit 61 in the ticket issuing device 6 transmits a predetermined notification that the ticket issuance is completed from the communication unit 63 to the ticket issuing server 3 via the communication network N (step S121-10).

[0115] In the ticket issuing server 3 that receives the above notification via the communication unit 33, the control unit 31 updates the information relating to the status of the ticket contained in the ticket content information D2 and ticket purchase information D6 relating to the ticket stored in the ticket information storage unit 322 of the storage unit 32 to information indicating that a two-dimensional code has been issued (step S121-11).

[0116] [(A) Step S122: When ticket content information is generated in the ticket information management server] Next, the flow of operations when ticket content information D2 is generated in the ticket information management server 1 will be described with reference to the flowchart of FIG.

[0117] When a user wishes to have a ticket issued for use on a train by the ticket issuing device 6, the user first uses the operation unit 65 of the ticket issuing device 6 to input information related to the ticket they wish to reserve, i.e., the ticket purchase information D1 including, for example, information related to the train's boarding station, disembarking station, departure time, arrival time, seat number, etc., and then performs the required purchase operation (step S122-1).

[0118] When the desired ticket purchase information D1 is input, the control unit 61 generates ticket purchase information D6 based on the input information (step S122-2), and transmits the generated ticket purchase information D6, together with a predetermined request to generate ticket content information D2 corresponding to the data, from the communication unit 63 via the communication network N to the ticket information management server 1 (step S122-3).

[0119] In the ticket information management server 1, when the communication unit 13 receives the ticket purchase information D6 and a request to generate ticket content information D2, the control unit 11 checks the seat availability on the train based on the running train information D3 stored in the running train information storage unit 122 and the reservation status information D4 stored in the reservation status information storage unit 123, and if it is possible to purchase a ticket for the seat on the train for which the user related to the ticket purchase information D6 wishes to purchase a ticket, generates the corresponding ticket content information D2 (step S122-4).

[0120] Once the ticket content information D2 is generated, the control unit 11 in the ticket information management server 1 transmits the generated ticket content information D2 to the ticket issuing server 3 via the communication unit 13 via the communication network N, together with the ticket purchase information D6 received in step S122-3 (step S122-5).

[0121] In the ticket issuing server 3, when the communication unit 33 receives the ticket content information D2 and the ticket purchase information D6, the control unit 31 links the received ticket content information D2 and the ticket purchase information D6 and stores them in the ticket information memory unit 322 of the memory unit 32 (step S122-6).

[0122] Next, the control unit 31 of the ticket issuing server 3 sets an ID (identifier) ​​for each ticket purchase information D6 in accordance with a predetermined rule, generates ticket identifier information D10, assigns a number, generates ticket number information D11, and stores it in the ticket information storage unit 322 of the storage unit 32 in association with the corresponding ticket content information D2 and ticket purchase information D6 (step S122-7).

[0123] Next, the control unit 31 generates normally issued two-dimensional code data D12 in accordance with a predetermined two-dimensional code format using the ticket purchase information D6 and the generated ticket identifier information D10 (step S122-8).

[0124] When the normally issued two-dimensional code data D12 is generated, the control unit 31 of the ticket issuing server 3 transmits the generated normally issued two-dimensional code data D12 together with the corresponding ticket number information D11 from the communication unit 33 via the communication network N to the ticket information management server 1 (step S122-9).

[0125] In the ticket information management server 1, when the communication unit 13 receives the normally issued two-dimensional code data D12 and ticket number information D11, the control unit 11 transmits the received information from the communication unit 13 to the ticket issuing device 6 via the communication network N (step S122-10).

[0126] In the ticket issuing device 6, when the communication unit 63 receives the normally issued two-dimensional code data D12 and the ticket number information D11, the control unit 61 generates normally issued two-dimensional code image data D16 based on the normally issued two-dimensional code data D12, and then causes the ticket issuing unit 66 to issue a ticket on which the two-dimensional code related to the normally issued two-dimensional code image data D16 and the number related to the ticket number information D11 are stored by printing or other method on a predetermined medium such as paper (step S122-11).

[0127] When the ticket issuance is completed, the control unit 61 in the ticket issuing device 6 transmits a predetermined notification that the ticket issuance is completed from the communication unit 63 to the ticket information management server 1 via the communication network N (step S122-12).

[0128] In the ticket information management server 1, when the communication unit 13 receives the above notification, the control unit 11 sends a predetermined notification indicating that the ticket issuance has been completed from the communication unit 13 to the ticket issuance server 3 via the communication network N (step S122-13).

[0129] In the ticket issuing server 3 that receives the above notification via the communication unit 33, the control unit 31 updates the ticket content information D2 and ticket status information D6 related to the ticket stored in the ticket information storage unit 322 of the storage unit 32 to information indicating that a two-dimensional code has been issued (step S122-14).

[0130] [(2) Effects of this step] According to the ticket information processing system 100 of this embodiment, the following effects can be obtained by issuing tickets as described above.

[0131] In other words, tickets using two-dimensional codes issued as described above, whether issued to a user terminal 8 or by the ticket issuing device 6, do not include information that constitutes the contents of the ticket, such as the boarding station, disembarking station, or train to be boarded. Data such as ticket content information D2, which includes information related to the contents of the ticket, is managed by the ticket issuing server 3, and the two-dimensional code that is issued only includes the corresponding ticket identifier information D10.

[0132] In the past, when the two-dimensional code itself contained information that constituted the contents of the ticket, such as the boarding station, disembarking station, and train to be boarded, even if it was encoded, if it was broken, there was a risk that a counterfeit ticket with any content could be created. However, according to this embodiment, the two-dimensional code itself does not contain information that constitutes the contents of the ticket, and even if only the ticket identifier information D10 is counterfeited, it cannot be used unless the corresponding data such as ticket content information D2 exists on the ticket issuing server 3, eliminating this risk.

[0133] Furthermore, tickets with two-dimensional codes are easy to copy, whether they are electronic data or a specified medium such as paper. According to this embodiment, even if a legitimately issued two-dimensional code is copied, since the two-dimensional code does not contain information that constitutes the content of the ticket as described above, when the ticket is used, the ticket issuing server 3 that manages information that constitutes the content of the ticket, such as ticket content information D2, must be inquired using the ticket identifier information D10. This means that if the same ticket is copied and used multiple times, the server can always detect this, making it easier to prevent legitimately issued tickets from being copied and used multiple times.

[0134] Furthermore, the data contained in the two-dimensional code has a basic information section D12-1 and a validity testing section D12-2, and the validity testing section D12-2 contains general testing information D14, which is information relating to the results of a specified testing conversion or calculation performed based on the data contained in the basic information section D12-1 in accordance with a specified conversion rule or calculation formula related to general testing processing information D15.As described below, this makes it possible to easily determine whether the ticket is a legitimately issued ticket at the ticket gate device 4.

[0135] Furthermore, when a two-dimensional code is issued to the user terminal 8 in step S11, if the static / dynamic issuance identification information D51 received by the ticket issuing server 3 from the ticket reservation server 2 contains content that makes the two-dimensional code to be issued dynamic, then, as described above, the ticket information storage unit 322 of the storage unit 32 of the ticket issuing server 3 and the ticket information storage unit 222 of the storage unit 22 of the ticket reservation server 2 store two-dimensional code usage time information D52, which is information related to the usage time of the two-dimensional code related to the normally issued two-dimensional code data D12, and it becomes possible to prevent the two-dimensional code from being used after the usage time has elapsed, as described below.

[0136] For example, tickets issued in this embodiment are not limited to those intended for one-time use, but may also be some kind of special ticket, i.e., a ticket that allows free boarding of trains within a specified period and within a specified range. Since such tickets can be reused, if a two-dimensional code related to the normally issued two-dimensional code data D12 is issued without limiting the time of use, this code may be distributed to other people by the user who received the two-dimensional code, and may be used by people other than the legitimate user to board the train fraudulently. In this regard, if two-dimensional code usable time information D52 is stored in the ticket information memory unit 322 of the memory unit 32 of the ticket issuing server 3 and the ticket information memory unit 222 of the memory unit 22 of the ticket reservation server 2, and the two-dimensional code cannot be used after the usable time has elapsed, such fraud will become impossible (strictly speaking, it is possible, but it is not effective because the usable time is limited), and it will be easier to issue special tickets such as those described above using two-dimensional codes.

[0137] (3) Modifications A variation of the present system relating to ticket issuance will now be described.

[0138] [A. Variation 1: Issuance of group tickets] The tickets that users use to board trains include tickets for a single user, as well as group tickets, i.e., tickets issued in bulk to a group of multiple users when they are traveling on the same section of the same train. Conventionally, such group tickets are operated in the following manner: a single ticket is issued to a representative, on which the number of people allowed to use the ticket is stored, and the users then enter or exit through a service entrance or the like without going through a ticket gate. At this time, station staff count the number of people entering or exiting, compare this with the number of people allowed to use the ticket issued to the representative, and allow entry or exit if the number does not exceed the number of people allowed to use the ticket.

[0139] The following describes how such a group ticket is issued using the ticket issuing method of this embodiment. Explanations of the configuration and operation that are the same as those of the above embodiment will be omitted. This also applies to the other modifications described below.

[0140] There are two methods for issuing group tickets using the ticket issuance method of this embodiment: issuing two-dimensional codes with the same content to multiple users who make up the group, and issuing two-dimensional codes with different content to multiple users who make up the group.Each issuance method will be explained below.

[0141] Whichever method is used, it becomes possible to issue group tickets using a two-dimensional code, and unlike the conventional practice of issuing one ticket to the representative, it is possible to issue tickets to each user who makes up the group.As a result, as will be described later, it becomes possible to process entry and exit at the ticket gate device 4 for users using group tickets as well. In addition, from the viewpoint of preventing the processes related to determining whether entry and exit are permitted and updating status information from becoming complicated, it is preferable to issue two-dimensional codes with different content to each of the multiple users who make up the group.

[0142] [(A) When issuing the same two-dimensional code to multiple users] In this case, when inputting the ticket information the user wishes to purchase (step S11-1 if issued to a user terminal, and steps S121-1 and S122-1 if issued by a ticket issuing device), the user inputs specific information indicating that the user wishes to purchase a group ticket, and information regarding the number of tickets desired to be issued (the number of people who can use the group ticket). In the case of issuance to a user terminal (step S11), the input information is transmitted from the user terminal 8 to the ticket reservation server 2, and then transmitted from the ticket reservation server 2 to the ticket issuing server 3. In the case of issuance by the ticket issuing device (step S12), the ticket is sent directly from the ticket issuing device 6 to the ticket issuing server 3 without going through the ticket reservation server 2. In the case of ticket content information being generated in the ticket information management server (step S122), the ticket issuance device 6 may send the ticket content information to the ticket information management server 1, and then the ticket information management server 1 may send the ticket content information to the ticket issuing server 3.

[0143] In addition, when generating the ticket identifier information and ticket number information (step S11-14 in the case of issuance to a user terminal and steps S121-6 and S122-7 in the case of issuance by a ticket issuing device), the control unit 31 sends information such as group ticket identification information D53, which is predetermined identification information indicating that the ticket is a group ticket, and the number of issued two-dimensional codes for the group ticket corresponding to the number of tickets desired by the user (number of people who can use the group ticket) (in the case of issuance to a user terminal, in step S11-18, the normally issued two-dimensional code image data D16). In the case of issuance by a ticket issuing device, in step S121-9 or step S122-11, group ticket issuance number information D54, which is information relating to the number of user terminals 8 to receive the ticket and the number of tickets to be issued in which a two-dimensional code or the like relating to the normally issued two-dimensional code image data D16 is stored in a specified medium, is generated, and then, as shown in Figure 29, this is stored in the ticket information memory unit 322 of the memory unit 32 of the ticket issuing server 3 in association with the corresponding ticket content information D2, ticket purchase information D6, ticket identifier information D10, ticket number information D11 and two-dimensional code usable time information D52. In this case, the group ticket identification information D53 is a flag that indicates only whether the ticket is a group ticket or not, and is information common to all group tickets. In contrast, the group ticket issue number information D54 is information related to the number of two-dimensional codes issued for each group ticket, and is information unique to each group ticket.

[0144] In addition, the group ticket issuance number information D54 may be stored in the memory unit 22 of the ticket reservation server 2, and when used by the ticket issuing server 3, the group ticket issuance number information D54 may be transmitted from the ticket reservation server 2 to the ticket issuing server 3.

[0145] Also, in the case of issuance to a user terminal, in step S11-18, the ticket reservation server 2 transmits the ticket reservation information D8, ticket number information D11 and normally issued two-dimensional code image data D16 from the communication unit 23 via the communication network N individually to the user terminal 8 possessed by each user using the group ticket, not just to the user terminal 8 that transmitted the desired ticket purchase information D1 in step S11-2.

[0146] In addition, when issuing to a user terminal, the method of transmitting the ticket reservation information D8, ticket number information D11, and normally issued two-dimensional code image data D16 is not limited to individual transmission to the user terminal 8 held by each user using the group ticket. For example, the information D1 on the tickets to be purchased may be sent only to the user terminal 8 used by the group representative, such as the user terminal 8 that sent the information D1 on the tickets to be purchased in step S11-2, and then from that user terminal 8 to the user terminals 8 held by each user who will use the group ticket. Furthermore, for example, the ticket reservation server 2 may store the ticket reservation information D8, ticket number information D11, and normally issued two-dimensional code image data D16 in a predetermined storage means (which may be provided within the storage unit 22 of the ticket reservation server 2 or in a predetermined external server), and then send only a link to the storage means to the user terminal 8 carried by each user using the group ticket, so that each user using the group ticket can access the predetermined storage means in which the ticket reservation information D8, ticket number information D11, and normally issued two-dimensional code image data D16 are stored and download these data.

[0147] In addition, in the case of issuance by a ticket issuing device, when issuing tickets using a specified medium (step S121-9 or step S122-11), the control unit 61 of the ticket issuing device 6 will cause the ticket issuing unit 66 to issue tickets in a number that matches the group ticket issuance number information D54, on which the two-dimensional code related to the normally issued two-dimensional code image data D16 and the number related to the ticket number information D11 are stored by printing or other method on a specified medium such as paper.

[0148] [(a) When issuing two-dimensional codes with different contents to multiple users] In this case, when the user inputs the ticket information they wish to purchase (step S11-1 if the ticket is issued to a user terminal, and steps S121-1 and S122-1 if the ticket is issued by a ticket issuing device), they input specific information indicating that they wish to purchase a group ticket, and information regarding the number of tickets they wish to issue (the number of people who can use the group ticket).

[0149] Furthermore, when generating ticket content information (step S11-4 when issued to a user terminal and steps S121-3 and S122-4 when issued by a ticket issuing device), a number of pieces of ticket content information D2 are generated that match the number of tickets desired by the user (number of people who can use the group ticket), and when generating ticket purchase information, etc. (step S11-8 when issued to a user terminal and steps S121-2 and S122-2 when issued by a ticket issuing device), a number of pieces of ticket purchase information D6 (ticket purchase information D6 and ticket reservation information D8 when issued to a user terminal) that match the number of tickets desired by the user (number of people who can use the group ticket), and when storing ticket content information, etc. (step S11-10 when issued to a user terminal and steps S121-5 and S122-6 when issued by a ticket issuing device), multiple pieces of ticket content information D2 and ticket purchase information D6 are linked together and stored in the ticket information storage unit 322 of the storage unit 32.

[0150] In addition, when generating ticket identifier information and ticket number information (step S11-14 when issued to a user terminal and steps S121-6 and S122-7 when issued at a ticket issuing device), the control unit 31 generates ticket identifier information D10 and ticket number information D11 in a number that matches the number of tickets desired by the user (number of people available for use of the group ticket), and stores each of the generated multiple ticket identifier information D10 and ticket number information D11 in the ticket information memory unit 322 of the memory unit 32 of the ticket issuing server 3, linked to the corresponding ticket content information D2 and ticket purchase information D6, as shown in Figure 30. In this case, each of the generated sets of multiple ticket identifier information D10 and ticket number information D11 will be stored in association with each of the multiple sets of ticket content information D2 and ticket purchase information D6 stored in association with each other in the ticket information storage unit 322 of the storage unit 32 when storing ticket content information, etc. (step S11-10 in the case of issuance to a user terminal and steps S121-5 and S122-6 in the case of issuance at a ticket issuing device).

[0151] Furthermore, at this time, for each of the generated multiple ticket identifier information D10 and ticket number information D11, group ticket identification information D53, which is predetermined identification information indicating that the ticket is a group ticket, and issued group ticket number information D54, which is information regarding the number of issued two-dimensional codes for the group ticket corresponding to the number of tickets desired by the user (the number of people allowed to use the group ticket) (in the case of issuance to a user terminal, the number of user terminals 8 to which information such as normally-issued two-dimensional code image data D16 is sent in step S11-18; in the case of issuance by a ticket issuing device, the number of tickets issued in which two-dimensional codes such as those related to normally-issued two-dimensional code image data D16 are stored in a predetermined medium in step S121-9 or step S122-11), are linked and stored. In this case, the issued group ticket number information D54 will match the generated number of ticket identifier information D10 and ticket number information D11.

[0152] In this case, group identification information D55 is generated as information indicating that the generated plurality of ticket identifier information D10 and ticket number information D11 relate to tickets included in a specific group ticket, and is then stored in association with each of the generated plurality of ticket identifier information D10 and ticket number information D11. As the group identification information D55, a number, identifier, etc. may be set for each group ticket, and this may be stored in association with all ticket identifier information D10 and ticket number information D11 relating to tickets included in the common group ticket. Also, the user may be prompted to input information relating to the group name, the name of the group representative, etc., and this may be used as the group identification information D55.

[0153] It is not necessary to set one group specific information D55 for each group, but rather one group may be subdivided and multiple group specific information D55 may be set so that multiple types of group tickets can be issued to one group. For example, if multiple itineraries are set for the same day within a single travel group and the group members are divided into multiple itineraries, it is possible to issue group tickets for each itinerary by assigning different group specific information D55 to each itinerary. Specifically, if a group trip of XX Elementary School is divided into a trip with a destination in Osaka and a trip with a destination in Nara, the group identification information D55, XX Elementary School (Osaka) or XX Elementary School (Nara), will be set for each itinerary.

[0154] Furthermore, when generating two-dimensional code data (step S11-15 in the case of issuance to a user terminal, and steps S121-7 and S122-8 in the case of issuance by a ticket issuing device), the control unit 31 of the ticket issuing server 3 individually generates normally-issued two-dimensional code data D12 including each of the generated ticket identifier information D10. As a result, normally-issued two-dimensional code data D12 in the number matching the number of tickets desired by the user (number of people eligible for a group ticket) are generated, each including different ticket identifier information D10.

[0155] In addition, in the case of issuance to a user terminal, in step S11-17, the ticket reservation server 2 generates normal-time issued two-dimensional code image data D16 for each normal-time issued two-dimensional code data D12 generated by the ticket issuance server 3, and in step S11-18, each of the generated multiple normal-time issued two-dimensional code image data D16 is linked to the ticket reservation information D8 and ticket number information D11 and sent individually to the user terminal 8 used by each user using the group ticket. Furthermore, in the case of issuance by a ticket issuing device, when issuing tickets using a predetermined medium (step S121-9 or step S122-11), the control unit 61 of the ticket issuing device 6 generates normal-issue two-dimensional code image data D16 for each received normal-issue two-dimensional code data D12, and then causes the ticket issuing unit 66 to issue tickets for each of the generated multiple normal-issue two-dimensional code image data D16, on which the two-dimensional code related to the normal-issue two-dimensional code image data D16 and the number related to the ticket number information D11 are stored by printing or other method on a predetermined medium such as paper. As a result, tickets in the number matching the number of tickets desired by the user (the number of people who can use the group ticket) are issued, each with a different two-dimensional code printed on it.

[0156] [Variation 2: Unified management of tickets and coupons] In the explanation of the above operation flow, the ticket issuing server 3 stores information such as ticket content information D2, which includes information related to the contents of the ticket used to board the train, and the two-dimensional code is used as the ticket to board the train. However, in addition to this, the two-dimensional code may also be used as a coupon for receiving special benefits at designated facilities such as stores.

[0157] [(A) Configuration of modified example] As shown in Figure 31, the ticket information processing system 100A of this modified example includes, in addition to the devices described in the above configuration description, a coupon information management server 9 and a facility terminal 10, and the devices are connected via a communication network N as shown in Figure 31.

[0158] The coupon information management server 9 is an information device such as a PC or a WS, which manages information required for issuing coupons and transmits coupon information D56 to other servers. As shown in Fig. 31, the coupon information management server 9 is configured to include, for example, a control unit 91, a storage unit 92, and a communication unit 93, similar to the ticket information management server 1. The ticket information management server 1 may also function as the coupon information management server 9.

[0159] The configurations of the control unit 91 and the communication unit 93 are the same as those of the control unit 11 and the communication unit 13 in the ticket information management server 1, respectively. The storage unit 92 is configured, for example, by a HDD, a semiconductor memory, etc., similar to the storage unit 12 in the ticket information management server 1, and stores coupon information D56.

[0160] Coupon information D56 is information relating to the content of coupons that can be issued in this system, including information on available facilities, information on the available period, information on benefits that can be received with the coupon, etc. Coupon information D56 is created individually for each coupon that can be issued by this system, and information relating to all coupons that can be issued in this system is stored in memory unit 92. Furthermore, in cases where the coupon is provided by a coupon business operator rather than by the available facility itself, the coupon information D56 may include information related to the coupon business operator that provides the coupon.

[0161] Facility terminal 10 is a terminal provided in each facility such as a store where coupons issued by this system can be used, and is configured with, for example, a control unit 101, a storage unit 102, a communication unit 103, a display unit 104, an operation unit 105, and a coupon information reading unit 106. Facility terminal 10 may be a dedicated terminal provided within each facility, or may be a smartphone, tablet terminal, or the like carried by a store clerk or other employee of each facility.

[0162] The configurations of the control unit 101, communication unit 103, display unit 104 and operation unit 105 are the same as those of the control unit 51, communication unit 53, display unit 54 and operation unit 55 in the counter processing machine 5, respectively. The storage unit 102 is configured, for example, by a HDD, a semiconductor memory, etc., similar to the storage unit 52 in the counter processing machine 5, and stores facility specification information D57.

[0163] The facility identification information D57 is information that can identify the facility where the facility terminal 10 is installed, and may be any information that can identify the facility, such as the facility name, an ID assigned to each facility, or the like.

[0164] The coupon information reader 106, like the ticket information reader 44 in the ticket gate device 4, is a part for reading the normally issued two-dimensional code data D12, which is information related to the stored contents, from the two-dimensional code that is held over it, and is made up of a predetermined one-dimensional or two-dimensional code reader corresponding to the type of code used. Note that if a smartphone, tablet terminal, or the like carried by an employee of each facility is used as the facility terminal 10, the camera provided on such a terminal can be used.

[0165] [(a) Operation of the modified example] The operation of the system when issuing a ticket according to this modification will be explained separately for the case where the ticket is issued to the user terminal 8 and the case where the ticket is issued by the ticket issuing device 6.

[0166] [a Issuance to user terminal] First, when issuing to the user terminal 8, the user inputs information about the coupon they wish to receive (hereinafter referred to as "coupon information they wish to receive") in addition to the ticket information D1 when inputting the ticket information they wish to receive (step S11-1 when issuing to the user terminal). The coupon information they wish to receive can be input by selecting the coupon they wish to receive in accordance with a specific website or application, just like when inputting the ticket information D1.

[0167] Alternatively, coupons corresponding to the boarding or disembarking stations related to the ticket purchase information D1 entered by the user or coupons that can be used at facilities near the boarding or disembarking stations may be automatically selected without requiring the user to input any information. In this case, the information related to such automatically selected coupons corresponds to the coupon information desired to be issued. Alternatively, coupons corresponding to the itinerary set by the user as the ticket purchase information D1 may be automatically selected and automatically granted regardless of the user's wishes, making it possible to utilize the granted coupons to stimulate demand among users.

[0168] When the coupon information to be issued is input, in step S11-2, the coupon information to be issued is sent to the ticket reservation server 2 along with the ticket purchase information D1. When the ticket reservation server 2 receives this, it sends the received coupon information to the coupon information management server 9 when sending the ticket purchase information D1 to the ticket information management server 1 in step S11-3. When the coupon information management server 9 receives this, the control unit 91 extracts coupon information D56 corresponding to the received coupon information to be issued from the memory unit 92 and sends it to the ticket reservation server 2.

[0169] In the ticket reservation server 2, in step S11-8, when the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 are linked and stored in the ticket information storage unit 222 of the storage unit 22, the coupon information D56 received from the coupon information management server 9 and information relating to the status of the coupon (hereinafter referred to as coupon status information) are also linked to these pieces of information and stored. The coupon status information is information about the status of the coupon associated with the stored coupon information D56, and includes, for example, information about whether the coupon is unused or has already been used. At this point, the information stored indicates that the coupon is unused.

[0170] In addition, when the ticket reservation server 2 sends the ticket purchase information D6 etc. to the ticket issuing server 3 in step S11-9, it also sends the coupon information D56 and coupon status information received from the coupon information management server 9, and in step S11-10, the ticket issuing server 3 links the coupon information D56 and coupon status information to the received ticket content information D2 and ticket purchase information D6, and stores them in the ticket information memory unit 322 of the memory unit 32.

[0171] In addition, in step S11-14, the ticket issuing server 3 links the generated ticket identifier information D10 and ticket number information D11 to the ticket content information D2 and ticket purchase information D6, as well as the corresponding coupon information D56, and stores them in the ticket information memory unit 322 of the memory unit 32.

[0172] As a result, in the ticket issuing server 3, the ticket information storage unit 322 of the storage unit 32 stores ticket content information D2 and ticket purchase information D6, which contain information regarding the content of the ticket used to board the train purchased by the user, linked to the ticket identifier information D10 contained in the normally issued two-dimensional code data D12, as well as coupon information D56, which contains information regarding the content of the coupon issued to the user.

[0173] [b Issuance at the ticket issuing device] When issuing a ticket using the ticket issuing device 6, the user uses the operation unit 65 of the ticket issuing device 6 to input the desired coupon information D1 in addition to the desired ticket information D1 when inputting the desired ticket purchase information D1 (step S121-1 or step S122-1).

[0174] When the coupon information to be issued is input, ticket content information D2 is generated in the ticket issuing device (step S121). When the ticket content information D2 and ticket purchase information D6 are sent to the ticket issuing server 3 in step S121-4, the coupon information to be issued is sent to the coupon information management server 9. When the coupon information management server 9 receives this, the control unit 91 extracts coupon information D56 corresponding to the received coupon information to be issued from the memory unit 92 and sends it to the ticket issuing server 3. In addition, when ticket content information is generated in the ticket information management server (step S122), when ticket purchase information D6 is sent to the ticket information management server 1 in step S122-3, the coupon information to be issued is sent to the coupon information management server 9, and when the coupon information management server 9 receives this, the control unit 91 extracts coupon information D56 corresponding to the received coupon information to be issued from the memory unit 92 and sends it to the ticket issuing server 3.

[0175] In addition, in step S121-5 or step S122-6, the control unit 31 of the ticket issuing server 3 links the coupon information D56 and coupon status information to the ticket content information D2 and ticket purchase information D6, and stores them in the ticket information storage unit 322 of the storage unit 32.

[0176] Also, in step S121-6 or step S122-7, the control unit 31 of the ticket issuing server 3 links the generated ticket identifier information D10 and ticket number information D11 to the corresponding coupon information D56 in addition to the ticket content information D2 and ticket purchase information D6, and stores them in the ticket information memory unit 322 of the memory unit 32.

[0177] As a result, in the ticket issuing server 3, the ticket information storage unit 322 of the storage unit 32 stores ticket content information D2 and ticket purchase information D6, which contain information regarding the content of the ticket used to board the train purchased by the user, linked to the ticket identifier information D10 contained in the normally issued two-dimensional code data D12, as well as coupon information D56, which contains information regarding the content of the coupon issued to the user.

[0178] In addition, in the case of issuance to a user terminal (step S11), the ticket reservation server 2 may also link ticket content information D2, ticket purchase information D6, and ticket reservation information D8, which contain information regarding the content of the ticket used to board the train purchased by the user, with coupon information D56, which contains information regarding the content of the coupon issued to the user, and store them in the ticket information storage unit 222 of the storage unit 22. In addition, the functions and configurations of each server are not limited to those shown in the figure, and the server that performs each of the above processes can be changed to another server, as long as it does not cause any problems in issuing a two-dimensional code to a user that can be used both as a ticket for boarding a train and as a coupon for receiving specified benefits.

[0179] [(c) Effects of Modifications] According to this modification, a two-dimensional code can be issued that can be used by a user both as a ticket for boarding a train and as a coupon for receiving a predetermined benefit. This allows the user to manage tickets and coupons used for a single trip with a single two-dimensional code, eliminating the need to carry and use multiple two-dimensional codes, magnetic tickets, etc. for tickets and coupons.

[0180] [C Variation 3: Unification of multiple tickets] In the explanation of the above operation flow, we have explained the case where the issued two-dimensional code (normally issued two-dimensional code data D12) corresponds one-to-one with information such as ticket content information D2, ticket purchase information D6, and ticket reservation information D8, which contains information related to the ticket content, and one two-dimensional code is issued for one ticket (information related to the content of one ticket), but it is also possible to issue a single two-dimensional code for multiple tickets so that the multiple tickets can be unified.

[0181] In this case, the user inputs the desired ticket information D1 for multiple tickets when inputting the desired ticket information (step S11-1 in the case of issuance to a user terminal, and steps S121-1 and S122-1 in the case of issuance by a ticket issuing device). For example, in the case of conventional magnetic tickets, if it is necessary to individually issue multiple tickets, limited express tickets, etc. to reach the destination, the desired ticket information D1 corresponding to each of these tickets, limited express tickets, etc. will be input.

[0182] In addition, when generating ticket content information (step S11-4 when issuing to a user terminal and steps S121-3 and S122-4 when issuing at a ticket issuing device), multiple ticket content information D2 is generated corresponding to each of the desired ticket purchase information D1 entered by the user.

[0183] In addition, when generating ticket purchase information, etc. (step S11-8 when issuing to a user terminal, and steps S121-2 and S122-2 when issuing at a ticket issuing device), multiple ticket purchase information D6 (and multiple ticket reservation information D8 when issuing to a user terminal) are generated corresponding to each of the desired ticket information D1 entered by the user.

[0184] In addition, when storing ticket content information, etc. (step S11-10 in the case of issuance to a user terminal and steps S121-5 and S122-6 in the case of issuance at a ticket issuing device), the received multiple ticket content information D2 and ticket purchase information D6 are stored in the ticket information storage unit 322 of the storage unit 32 so that information corresponding to the same desired ticket purchase information D1 is linked to each other.

[0185] In addition, when ticket identifier information and ticket number information are generated (step S11-14 in the case of issuance to a user terminal and steps S121-6 and S122-7 in the case of issuance at a ticket issuing device), the generated single ticket identifier information D10 and ticket number information D11 are linked to each of the corresponding multiple ticket content information D2 and ticket purchase information D6 and stored in the ticket information memory unit 322 of the memory unit 32 of the ticket issuing server 3.

[0186] As a result, the ticket identifier information D10 contained in the issued normally issued two-dimensional code data D12 and information relating to the contents of multiple tickets (ticket content information D2 and ticket purchase information D6) are linked and stored in the ticket information storage unit 322 of the storage unit 32 of the ticket issuing server 3, making it possible to use tickets corresponding to multiple pieces of desired ticket purchase information D1 with a single two-dimensional code.

[0187] As mentioned above, with conventional magnetic card tickets, a user may need to receive multiple tickets, multiple express tickets, etc. separately before arriving at their destination. In this case, it was necessary to use these multiple tickets according to the station, and this process was very cumbersome for the user. According to this modified example, by combining multiple passenger tickets, multiple express tickets, etc. into one two-dimensional code, there is no need to use them differently, which is a major advantage.

[0188] Furthermore, with conventional magnetic card tickets, multiple tickets could be inserted into the ticket gate at the same time, such as when a passenger ticket and a limited express ticket are inserted at the same time, but with tickets using two-dimensional codes, multiple two-dimensional codes cannot be read by the ticket gate at the same time. In this regard, by combining multiple tickets into one two-dimensional code, the disadvantage of two-dimensional code tickets, that they cannot be inserted simultaneously, can be overcome.

[0189] In the above, we have explained the case where a user enters the desired ticket purchase information D1 for multiple tickets when entering the desired ticket purchase information, but it is also possible for a user to purchase additional tickets after purchasing one ticket and combine them into a single two-dimensional code.

[0190] In this case, after the user has received the ticket (after information such as the normally issued two-dimensional code image data D16 is stored in the user terminal 8 in step S11-22 in the case of issuance to a user terminal, or after the ticket is issued on a specified medium in step S121-9 or step S122-11 in the case of issuance at a ticket issuing device), the user again uses the operation unit 85 of the user terminal 8 or the operation unit 65 of the ticket issuing device 6 to input the desired ticket purchase information D1 for the ticket they wish to add before using the ticket. At this time, the user also inputs information that can identify the ticket to which the ticket is to be added, such as ticket number information D11.

[0191] When the desired ticket purchase information D1 for the ticket to be added is input, the corresponding ticket content information D2 and ticket purchase information D6 (and ticket reservation information D8 if issued to a user terminal) are generated, and then the control unit 31 of the ticket issuing server 3 links the generated ticket content information D2 and ticket purchase information D6 to the ticket identifier information D10 and corresponding ticket number information D11 contained in the normally issued two-dimensional code data D12 for the already generated two-dimensional code to be added, and stores them in the ticket information memory unit 322 of the memory unit 32 of the ticket issuing server 3.

[0192] As a result, the ticket identifier information D10 contained in the already issued normally issued two-dimensional code data D12 and the information relating to the content of the added ticket (ticket content information D2 and ticket purchase information D6) are linked and stored in the ticket information storage unit 322 of the storage unit 32 of the ticket issuing server 3, so that after a user purchases a ticket once, they can purchase additional tickets and combine them into a single two-dimensional code relating to the normally issued two-dimensional code data D12.

[0193] The configuration of this embodiment, in which the normally issued two-dimensional code data D12 does not include information related to the ticket contents, and the information related to the ticket contents is stored on the server, has the great advantage that it makes it easy to add further ticket contents to an already issued two-dimensional code.

[0194] [2 Step S2: Entering and Exiting the Ticket Gate] Next, the operation of this system when a user uses the two-dimensional code issued in step S1 to enter or exit the ticket gate at the ticket gate device 4 will be explained separately for cases where the decision on whether to allow or disallow entry is made by the ticket issuing server 3 and cases where it is made by the ticket gate device 4. In the present invention, inside the ticket gate refers to a place in the station facilities where only those in possession of a ticket used to board a train (or a prescribed admission ticket) are allowed to enter, regardless of whether a ticket gate device 4 is installed. Furthermore, simply "entering" means entering such a ticket gate, and simply "exiting" means exiting from such a ticket gate.

[0195] [(1) Operational flow] [A Step S21: When entry and exit is determined by the ticket issuing server] First, the flow of operations when the ticket issuing server 3 performs entry / exit determination will be described with reference to the flowchart of FIG.

[0196] If the user wishes to enter the station through the ticket gate device 4 before boarding a train, or if the user wishes to exit the station through the ticket gate device 4 after boarding a train, the user holds the two-dimensional code issued in step S1 over the ticket information reading unit 44 of the ticket gate device 4. Specifically, when the ticket is issued to the user terminal 8, a predetermined operation is performed using the operation unit 85 of the user terminal 8 to display the two-dimensional code related to the normally issued two-dimensional code image data D16 on the display unit 84, and then the displayed two-dimensional code is held over the ticket information reading unit 44. When the ticket is issued by the ticket issuing device 6, the two-dimensional code stored by printing or other method on a predetermined medium such as paper is held over the ticket information reading unit 44.

[0197] When the two-dimensional code is held over the ticket information reading unit 44, the control unit 41 of the ticket gate device 4 causes the ticket information reading unit 44 to read the normally issued two-dimensional code data D12 from the held two-dimensional code (step S21-1).

[0198] When the normally issued two-dimensional code data D12 is read by the ticket information reading unit 44, the control unit 41 determines whether the two-dimensional code being held over the ticket is a legitimate ticket (step S21-2).

[0199] Specifically, as explained in step S11, the normally issued two-dimensional code data D12 is composed of multiple memory areas, for example, as shown in FIG. 13, a basic information section D12-1 and a validity testing section D12-2, and the validity testing section D12-2 includes general testing information D14, which is information related to the results of a specified testing conversion or calculation based on the data included in the basic information section D12-1, in accordance with a specified conversion rule or calculation formula related to general testing processing information D15.

[0200] In addition, in the ticket gate device 4, a similar predetermined conversion rule or calculation formula is stored in the test processing information storage unit 422 of the storage unit 42 as general test processing information D15.

[0201] Therefore, the control unit 41 performs a predetermined conversion or calculation for testing based on the data contained in the basic information section D12-1 of the normally issued two-dimensional code data D12 read in step S21-1, in accordance with the above-mentioned predetermined conversion rule or calculation formula stored as general testing processing information D15 in the testing processing information memory section 422 of the memory unit 42. If the result of the conversion or calculation matches the general testing information D14 contained in the validity testing unit D12-2, the control unit 41 determines that the two-dimensional code is a genuine ticket, and if they do not match, it determines that the two-dimensional code is not a genuine ticket.

[0202] If it is determined in step S21-2 that the normally issued two-dimensional code data D12 relates to a genuine ticket, the control unit 41 in the ticket gate device 4 transmits the normally issued two-dimensional code data D12 read by the ticket information reading unit 44, together with the ticket gate device installation station information D18 and ticket gate device equipment information D19 stored in the equipment information storage unit 423 of the storage unit 42, from the communication unit 43 via the communication network N to the ticket issuing server 3 (step S21-3). If it is determined in step S21-2 that the ticket is an unauthorized ticket, the control unit 41 closes the opening / closing unit 45 and ends the process.

[0203] The ticket gate device installation station information D18 is information related to the station where the ticket gate device 4 is installed, and indicates the station where a user who holds the two-dimensional code over the ticket information reading unit 44 will enter or exit through the ticket gate. The ticket gate device equipment information D19 is information related to the ticket gate device 4, and includes information indicating the operator that installed it, information regarding whether the ticket gate device 4 requires entry / exit determination by the ticket issuing server 3 or whether the ticket gate device 4 performs the entry / exit determination itself, and information regarding detailed settings such as fraud detection that each ticket gate device 4 has.

[0204] In the ticket issuing server 3 that receives the information transmitted from the ticket gate device 4 via the communication unit 33, the control unit 31 determines, based on the ticket gate device equipment information D19, whether the ticket gate device 4 is a ticket gate device 4 that requires entry / exit determination by the ticket issuing server 3. If entry / exit determination by the ticket issuing server 3 is required, the control unit 31 first decodes the encoded information in the basic information section D12-1 of the normally issued two-dimensional code data D12 using the general encoding information D13 stored in the encoding information memory unit 323 of the memory unit 32 (step S21-4).

[0205] Next, the control unit 31 searches the ticket information storage unit 322 of the storage unit 32 based on the ticket identifier information D10 contained in the decrypted information, extracts the ticket content information D2 and ticket purchase information D6 corresponding to the received normally issued two-dimensional code data D12, and then compares the received ticket gate installation station information D18 and ticket gate equipment information D19 with the ticket content information D2 to make a determination as to whether entry or exit is permitted (step S21-5). In addition, if the ticket content information D2 and ticket purchase information D6 corresponding to the received normally issued two-dimensional code data D12 are not extracted, the control unit 31 will send a predetermined command to close the opening / closing section 45 to the ticket gate device 4 from the communication unit 33 via the communication network N, and will terminate the processing.

[0206] Specifically, in the case of entry, the entry / exit history is confirmed from the ticket status information included in the ticket content information D2 and the ticket purchase information D6, and the user's entry station according to the ticket gate station information D18 is compared with the information on the valid section (the section passing through intermediate stations between the boarding station and the disembarking station) included in the ticket content information D2. Entry is determined to be permitted if, for example, there is no entry history or the user has exited at an intermediate station, the ticket is within the validity period according to the ticket content information D2, and the user's entry station according to the ticket gate station information D18 is within the validity period according to the information on the validity period included in the ticket content information D2. Entry is determined to be prohibited if there is an entry history and the user has not exited at an intermediate station, the ticket is outside the validity period according to the ticket content information D2, or the user's entry station according to the ticket gate station information D18 is not within the validity period according to the information on the validity period included in the ticket content information D2.

[0207] In the case of exiting, the entry history and exit history are confirmed from information related to the ticket status included in the ticket content information D2 and the ticket purchase information D6, and the user's exit station related to the ticket gate device installation station information D18 is compared with the information related to the validity zone included in the ticket content information D2. Then, for example, if the user has entered but not yet exited, is within the validity period related to the ticket content information D2, and the user's exit station related to the ticket gate device installation station information D18 is within the validity zone in the information related to the validity zone included in the ticket content information D2, it is determined that the user is able to exit. However, if the user has entered or exited, is outside the validity period related to the ticket content information D2, or the user's exit station related to the ticket gate device installation station information D18 is not within the validity zone in the information related to the validity zone included in the ticket content information D2, it is determined that the user is unable to exit.

[0208] In addition, if the ticket information storage unit 322 of the storage unit 32 stores two-dimensional code usage time information D52 corresponding to the received normally issued two-dimensional code data D12, the control unit 31 also determines whether the two-dimensional code corresponding to the received normally issued two-dimensional code data D12 is within the usage time prior to extracting the ticket content information D2 and ticket purchase information D6. Specifically, the ticket information storage unit 322 of the storage unit 32 is searched based on the ticket identifier information D10, and the two-dimensional code usable time information D52 corresponding to the received normally issued two-dimensional code data D12 is extracted.Then, for example, the time at which the normally issued two-dimensional code data D12, contained in the two-dimensional code usable time information D52, was created is compared with the current time, and if the difference is within a specified time period contained in the two-dimensional code usable time information D52, it is determined that the data is within the usable time period; if the difference is outside the specified time period contained in the two-dimensional code usable time information D52, it is determined that the data is outside the usable time period. In this case, the control unit 31 extracts the ticket content information D2 and ticket purchase information D6 corresponding to the received normal-time issued two-dimensional code data D12 and determines whether entry or exit is possible only if it determines that the available time is within the available time, and if it determines that the available time is outside the available time, the control unit 31 sends a specified command to close the opening / closing section 45 from the communication unit 33 via the communication network N to the ticket gate device 4, and terminates the processing.

[0209] When the above determination is completed, the control unit 31 updates the information relating to the status of the ticket stored in the ticket information storage unit 322 of the storage unit 32 (step S21-6). Specifically, if entry is possible, the information regarding the ticket status contained in the ticket content information D2 and ticket purchase information D6 will be set to ticket in use (after entry but before exit), and if exit is possible, the information regarding the ticket status contained in the ticket content information D2 and ticket purchase information D6 will be set to already used (after exit at the disembarking station) or in use (after exit at an intermediate station).

[0210] When the update is completed, the control unit 31 transmits information relating to the determination result of the entrance / exit through the ticket gate in step S21-5 (first entrance / exit determination result information D20) from the communication unit 33 to the ticket gate device 4 via the communication network N (step S21-7).

[0211] In the ticket gate device 4, which receives the first entry / exit judgment result information D20 sent from the ticket issuing server 3 via the communication unit 43, the control unit 41 opens and closes the opening / closing section 45 based on the received first entry / exit judgment result information D20 (step S21-8). Specifically, if the received first entry / exit judgment result information D20 allows entry or exit, the opening / closing section 45 will be set to the open state, and if the received first entry / exit judgment result information D20 does not allow entry or exit, the opening / closing section 45 will be set to the closed state.

[0212] In the ticket issuing server 3, after transmitting the first entry / exit judgment result information D20 to the ticket gate device 4, information regarding the update contents of the information related to the ticket status contained in the ticket content information D2 and the ticket purchase information D6 in step S21-6 (first entry / exit status update information D21) is transmitted from the communication unit 33 to the ticket reservation server 2 via the communication network N (step S21-9).

[0213] In the ticket reservation server 2, when the communication unit 23 receives the first entry / exit status update information D21, the control unit 21 updates the information related to the ticket status contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 stored in the ticket information memory unit 222 of the memory unit 22 in the same manner as the update in the ticket issuing server 3 in step S21-6 (step S21-10).

[0214] [Step S22: When entry / exit determination is performed at the ticket gate device] Next, the flow of operations when the ticket gate device 4 determines whether a passenger is entering or exiting will be described with reference to the flowchart in FIG.

[0215] When a user wishes to enter the station through the ticket gate device 4 before boarding a train, or when a user wishes to exit the station through the ticket gate device 4 after boarding a train, the user holds the two-dimensional code issued in step S1, specifically, the two-dimensional code displayed on the display unit 84 of the user terminal 8 if issued to the user terminal 8, or the two-dimensional code stored by printing or other method on a specified medium such as paper if issued by the ticket issuing device 6, over the ticket information reading unit 44 of the ticket gate device 4. When the two-dimensional code is held over the ticket information reading unit 44, the control unit 41 of the ticket gate device 4 causes the ticket information reading unit 44 to read the normally issued two-dimensional code data D12 from the held two-dimensional code (step S22-1).

[0216] When the normally issued two-dimensional code data D12 is read by the ticket information reading unit 44, the control unit 41 determines whether the two-dimensional code being held over the ticket is a legitimate ticket (step S22-2). The determination method is the same as that described in step S21-2.

[0217] If it is determined in step S22-2 that the normally issued two-dimensional code data D12 relates to a genuine ticket, the control unit 41 in the ticket gate device 4 transmits the normally issued two-dimensional code data D12 read by the ticket information reading unit 44, together with the ticket gate device installation station information D18 and ticket gate device equipment information D19 stored in the equipment information storage unit 423 of the storage unit 42, from the communication unit 43 via the communication network N to the ticket issuing server 3 (step S22-3). If it is determined in step S22-3 that the ticket is an unauthorized ticket, the control unit 41 closes the opening / closing unit 45 and ends the process.

[0218] In the ticket issuing server 3 that receives the information transmitted from the ticket gate device 4 via the communication unit 33, the control unit 31 determines, based on the ticket gate device equipment information D19, whether the ticket gate device 4 is the ticket gate device 4 that performs the entry / exit determination at the ticket gate device 4. If the ticket gate device 4 performs the entry / exit determination, the control unit 31 first decodes the encoded information in the basic information section D12-1 of the encoded normally-issued two-dimensional code data D12 using the general encoding information D13 stored in the encoding information memory unit 323 of the memory unit 32 (step S22-4).

[0219] Next, the control unit 31 searches the ticket information storage unit 322 based on the ticket identifier information D10 contained in the decrypted information, extracts the ticket content information D2 and ticket purchase information D6 corresponding to the received normally issued two-dimensional code data D12, and transmits the extracted ticket content information D2 to the ticket gate device 4 that transmitted the information in step S22-3 (step S22-5).

[0220] In addition, if the ticket content information D2 and ticket purchase information D6 corresponding to the received normally issued two-dimensional code data D12 are not extracted, the control unit 31 will send a predetermined command to close the opening / closing section 45 to the ticket gate device 4 from the communication unit 33 via the communication network N, and will terminate the processing.

[0221] In addition, if the ticket information storage unit 322 of the storage unit 32 stores two-dimensional code usage time information D52 corresponding to the received normally issued two-dimensional code data D12, the control unit 31 determines whether the two-dimensional code corresponding to the received normally issued two-dimensional code data D12 is within the usage time prior to extracting the ticket content information D2 and ticket purchase information D6. Specifically, the ticket information storage unit 322 of the storage unit 32 is searched based on the ticket identifier information D10, and the two-dimensional code usable time information D52 corresponding to the received normally issued two-dimensional code data D12 is extracted.Then, for example, the time at which the normally issued two-dimensional code data D12, contained in the two-dimensional code usable time information D52, was created is compared with the current time, and if the difference is within a specified time period contained in the two-dimensional code usable time information D52, it is determined that the data is within the usable time period; if the difference is outside the specified time period contained in the two-dimensional code usable time information D52, it is determined that the data is outside the usable time period. In this case, the control unit 31 extracts the ticket content information D2 and ticket purchase information D6 corresponding to the received normal-time issued two-dimensional code data D12 and transmits the ticket content information D2 to the ticket gate device 4 only if it determines that the available time is within the available time, and if it determines that the available time is outside the available time, the control unit 31 transmits a predetermined command to close the opening / closing section 45 from the communication unit 33 to the ticket gate device 4 via the communication network N, and terminates the processing.

[0222] In the ticket gate device 4 that has received the ticket content information D2 via the communication unit 43, the control unit 41 determines whether or not entry and exit are permitted based on the received ticket content information D2 (step S22-6).

[0223] Specifically, for example, just as when the ticket issuing server 3 determines whether entry or exit is permitted, in the case of entry, it is determined that entry is permitted if the information related to the ticket status included in the ticket content information D2 indicates that there is no entry history or that the user has exited at an intermediate station, the ticket is within the validity period related to the ticket content information D2, and the user's entry station related to the ticket gate device installation station information D18 is a station located within the validity section related to the ticket content information D2; in the case of exit, it is determined that exit is permitted if the information related to the ticket status included in the ticket content information D2 indicates that the user has entered but not yet exited, the ticket is within the validity period related to the ticket content information D2, and the user's exit station related to the ticket gate device installation station information D18 is a station located within the validity section related to the ticket content information D2.

[0224] When the above determination is completed, the control unit 41 opens or closes the opening / closing unit 45 based on the determination result (step S22-7). Specifically, if the judgment result in step S22-7 is that entry or exit is permitted, the opening / closing section 45 will be set to the open state, and if the judgment result is that entry or exit is not permitted, the opening / closing section 45 will be set to the closed state.

[0225] Next, in the ticket gate device 4, the control unit 41 transmits information relating to the result of the ticket gate entry / exit judgment in step S22-6 (second entry / exit judgment result information D22), together with the ticket content information D2 received in step S22-5, from the communication unit 43 via the communication network N to the ticket issuing server 3 (step S22-8).

[0226] In the ticket issuing server 3 that receives the information transmitted from the ticket gate device 4, the control unit 31 updates the information relating to the ticket status contained in the ticket content information D2 and ticket purchase information D6 stored in the ticket information memory unit 322 of the memory unit 32 (step S22-9). Specifically, if entry is possible, the information regarding the ticket status contained in the ticket content information D2 and ticket purchase information D6 will be set to ticket in use (after entry but before exit), and if exit is possible, the information regarding the ticket status contained in the ticket content information D2 and ticket purchase information D6 will be set to already used (after exit at the disembarking station) or in use (after exit at an intermediate station).

[0227] Once the above update is completed, the control unit 31 transmits information (second entry / exit status update information D23) relating to the updated information relating to the ticket status contained in the ticket content information D2 and ticket purchase information D6 in step S22-9 from the communication unit 33 via the communication network N to the ticket reservation server 2 (step S22-10).

[0228] In the ticket reservation server 2, when the communication unit 23 receives the second entry / exit status update information D23, the control unit 21 updates the information related to the ticket status contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 stored in the ticket information memory unit 222 of the memory unit 22 in the same manner as the update in the ticket issuing server 3 in step S22-9 (step S22-11).

[0229] [(2) Effects of this step] According to the ticket information processing system 100 of this embodiment, the following effects can be obtained by performing the above-described ticket gate entry and exit.

[0230] That is, as described above, in the ticket information storage unit 322 of the storage unit 32 of the ticket issuing server 3, ticket content information D2 and ticket purchase information D6, which are information on the contents of the ticket including, for example, the specific ticket validity section (the section passing through intermediate stations between the boarding station and the disembarking station) and the ticket validity period, and ticket identifier information D10, which is information related to an identifier assigned to each ticket, are stored in association with each other. Then, when the ticket identifier information D10 is received from the ticket gate device 4 in the form of being included in the normally-issued two-dimensional code data D12 read by the ticket information reading unit 44, the ticket issuing server 3 extracts the ticket content information D2 corresponding to the received ticket identifier information D10, and based on this, the ticket issuing server 3 determines whether or not to allow entry or exit, or the ticket gate device 4, which has acquired the ticket content information D2 from the ticket issuing server 3, determines whether or not to allow entry or exit.

[0231] Therefore, in either case, the two-dimensional code that is read by the ticket gate device 4 does not contain the information that constitutes the ticket content required to determine entry and exit, and unless the ticket content information D2 corresponding to the ticket identifier information D10 read by the ticket gate device 4 is stored in the ticket issuing server 3, the user will not be able to enter or exit.

[0232] Therefore, even if a two-dimensional code containing information that has not been issued is forged, the holder of the ticket will not be able to enter or exit unless the corresponding data is available from the ticket issuing server 3. Also, even if a ticket is forged by duplicating a legitimately issued two-dimensional code, if the same two-dimensional code is used multiple times, this can always be detected by the ticket issuing server 3, making it easier to prevent the use of counterfeit tickets at ticket gates.

[0233] Furthermore, unlike conventional magnetic tickets, if tickets are made into two-dimensional codes, it is difficult to rewrite the two-dimensional code once it has been issued, and therefore it is not possible to update information about the status of the ticket, such as whether it is unused, in use, or already used, by rewriting the information stored on the ticket itself.

[0234] In this regard, according to this embodiment, the ticket reservation server 2 and the ticket issuing server 3 store ticket content information D2, ticket purchase information D6, and ticket reservation information D8, which contain information related to the ticket status, linked to ticket identifier information D10, and the information related to the ticket status contained therein is updated according to the judgment result regarding whether entry or exit is permitted made by the ticket issuing server 3 or the ticket gate device 4.Therefore, while using a two-dimensional code on the ticket, the information related to the ticket status can be easily updated and stored.

[0235] Furthermore, according to this embodiment, whether the determination regarding a user's entry and exit is made by the ticket issuing server 3 or by the ticket gate device 4, the ticket information reading unit 44 of the ticket gate device 4 reads data from the two-dimensional code held up by the user, and then first determines whether the ticket is a legitimately issued ticket, and if it is not a legitimately issued ticket, the process does not proceed to the subsequent steps.

[0236] Therefore, for tickets that are not legitimately issued, no data is sent to the ticket issuing server 3, and processing can be completed without performing any processing related to determining whether entry or exit is permitted. This reduces the processing burden on the ticket issuing server 3 and the ticket gate device 4 when an unlegally issued ticket is held up to the ticket information reading unit 44 at the ticket gate device 4. Furthermore, since the ticket issuing server 3 will no longer make a decision regarding whether or not to allow entry or exit for tickets that have not been issued legitimately, it is possible to counter server load attacks such as DoS attacks.

[0237] Furthermore, in the ticket issuing server 3, if the ticket information storage unit 322 of the storage unit 32 stores two-dimensional code usable time information D52 corresponding to the received normally issued two-dimensional code data D12, the two-dimensional code usable time information D52 is used to determine whether the two-dimensional code corresponding to the received normally issued two-dimensional code data D12 is within the usable time, making it possible to prevent the two-dimensional code from being used after the usable time has elapsed.This makes it easier to issue special tickets that are not limited to one-time use using two-dimensional codes, as described in step S1.

[0238] In addition, the normally issued two-dimensional code data D12 read from the issued ticket has a basic information section D12-1 and a validity testing section D12-2, and the validity testing section D12-2 contains general testing information D14, which is information related to the results of a specified testing conversion or calculation based on the data contained in the basic information section D12-1, in accordance with a specified conversion rule or formula.In addition, in the ticket gate device 4, a similar specified conversion rule or formula is stored as general testing processing information D15 in the testing processing information memory section 422 of the memory unit 42, making it possible for the ticket gate device 4 to easily determine whether a ticket is genuine.

[0239] (3) Modifications A modified example of this system relating to ticket gate entry and exit will be described below.

[0240] [A. Variation 1: Entering and exiting ticket gates for group tickets] In the following, a case will be described in which a group ticket is issued as described in Variation 1 of step S1, and multiple users holding a specific group ticket enter or exit through the ticket gate device 4.

[0241] First, before the two-dimensional code data is read at the ticket gate device 4 (step S21-1 or step S22-1), the control unit 31 of the ticket issuing server 3 transmits group ticket issuance number information D54 from the communication unit 33 to the station attendant terminal 7 via the communication network N.

[0242] The timing of transmission is not particularly limited; for example, when the group ticket issue number information D54 is generated in the ticket issuing server 3, the entry and exit stations for the group ticket are identified from the ticket content information D2 or ticket purchase information D6 stored in association with it, and this information is sent via the ticket reservation server 2 to the station attendant terminal 7 carried by the station attendant at the identified entry or exit station, together with identification information that can identify the group ticket (the ticket issuing server 3 sends it to the ticket reservation server 2, and the ticket reservation server 2 sends it to the station attendant terminal 7), and the station attendant terminal 7 that receives it stores it in the memory unit 72.

[0243] Furthermore, for example, before the two-dimensional code data is read at the ticket gate device 4, a two-dimensional code relating to the normally-issued two-dimensional code image data D16 is displayed on the display unit 84 of the user terminal 8 used by the representative of the group using the group ticket, and when this is read at the station attendant terminal 7, the normally-issued two-dimensional code data D12 read by the station attendant terminal 7 is transmitted to the ticket issuing server 3 via the ticket reservation server 2, and the ticket issuing server 3 that receives the normally-issued two-dimensional code data D12 extracts the group ticket issue number information D54 stored in association with the ticket identifier information D10 contained in the received normally-issued two-dimensional code data D12, and transmits this to the station attendant terminal 7 via the ticket reservation server 2.

[0244] It is preferable that information be transmitted between the station attendant terminal 7 and the ticket issuing server 3 via the ticket reservation server 2 as described above, but the station attendant terminal 7 and the ticket issuing server 3 may be directly connected via the communication network N and the information may be transmitted directly without going through the ticket reservation server 2. Whether it is done via the ticket reservation server 2 or directly, there is no difference in the fact that information is ultimately sent from the ticket issuing server 3 to the station attendant terminal 7, or from the station attendant terminal 7 to the ticket issuing server 3. Therefore, this includes the case of sending information from the ticket issuing server 3 to the station attendant terminal 7, or the case of sending information from the station attendant terminal 7 to the ticket issuing server 3.

[0245] It is also possible to store the group ticket issue number information D54 in advance in the ticket reservation server 2, and then transmit the group ticket issue number information D54 from the ticket reservation server 2 to the station attendant terminal 7.

[0246] Furthermore, when a group ticket is used, the ticket issuing server 3 transmits to the station attendant terminal 7 information relating to the number of times the group ticket has been used.

[0247] Specifically, when a group ticket is issued by issuing two-dimensional codes with the same content to multiple users, the ticket issuing server 3 performs an entry / exit determination based on the normally issued two-dimensional code data D12 received from the ticket gate device 4 (step S21-5), or when it receives information relating to the entry / exit determination result (second entry / exit determination result information D22) and the ticket content information D2 used for the determination from the ticket gate device 4 (step S22-8), the ticket identifier information D10 is linked to the normally issued two-dimensional code data D12 used for the determination. The station terminal 7 checks whether the group ticket identification information D53 is stored in the ticket reservation server 2, and if it is stored, counts the number of times it has determined that entry or exit is possible using the ticket content information D2 corresponding to the normally-issued two-dimensional code data D12, or the number of times it has received information related to the determination result that entry or exit is possible using the ticket content information D2 corresponding to the normally-issued two-dimensional code data D12, and then transmits the counted number, i.e., information related to the number of times the specific group ticket has been used, to the station employee terminal 7 via the ticket reservation server 2 each time it increases.

[0248] In addition, when a group ticket is issued by issuing the same two-dimensional code to multiple users, multiple tickets with two-dimensional codes are issued for the same ticket content information D2, so the question arises as to when to update the status information (steps S21-6 and S21-10 when entry / exit determination is made by the ticket issuing server, and steps S22-9 and S22-11 when entry / exit determination is made by the ticket gate device).For example, the status information can be updated at any of the following times.

[0249] First, it is conceivable to update the status information when the number of people determined to be able to enter or exit using the ticket content information D2 reaches the number of people issued according to the group ticket issue number information D54. In this case, the status information is updated only when all of the issued group tickets have passed through the ticket gate 4. In other words, entry and exit determination is performed individually for all tickets included in the group ticket as they pass through the ticket gate 4, and the status information is updated only when the last ticket included in the group ticket passes through the ticket gate 4.

[0250] Furthermore, it is conceivable that the status information may be updated when it is first determined that entry or exit is possible using the ticket content information D2. In this case, the status information is updated when the first of the issued group tickets passes through the ticket gate 4, but is not updated when the second or subsequent tickets pass through. In other words, when entering the venue, the status information is updated from "unused" to "in use" when the first ticket passes through the ticket gate 4, and when the second or subsequent tickets pass through the ticket gate 4, the status information remains "in use."

[0251] Furthermore, if the status information is updated when the first ticket passes through the ticket gate device 4, when a normal determination of whether entry or exit is possible is made, which also takes into account the status information described in steps S21-5 and S22-6, it will be determined that entry or exit is not possible for the second or subsequent tickets, since the status information has already been updated to "in use" at the time of entry. Therefore, in this case, when making entry / exit determinations for the second and subsequent cards, it is necessary to use a simplified determination method that does not take into account information related to status. For example, it is possible to determine only whether the normally issued two-dimensional code data D12 for the second and subsequent tickets matches the normally issued two-dimensional code data D12 when the first ticket was determined to be able to enter or exit (whether there is a history of determining that the same normally issued two-dimensional code data D12 is able to enter or exit), and if they match, it is determined that entry or exit is possible. Furthermore, for example, when issuing a group ticket by issuing two-dimensional codes with the same content to multiple users, similar to when issuing a group ticket by issuing two-dimensional codes with different content to multiple users, the ticket issuing server 3 may be configured to store group specific information D55 linked to ticket identifier information D10, and it may then be determined only whether the group specific information D55 stored linked to the ticket identifier information D10 contained in the normally-issued two-dimensional code data D12 for the second and subsequent tickets matches the group specific information D55 stored linked to the ticket identifier information D10 contained in the normally-issued two-dimensional code data D12 when it was determined that the first ticket was allowed to enter or exit (whether there is a history of determining that entry or exit is allowed for normally-issued two-dimensional code data D12 containing ticket identifier information D10 stored linked to the same group specific information D55), and if they match, it may be determined that entry or exit is allowed. Furthermore, although this would be undesirable as it would allow anyone to enter or exit, it is also conceivable to adopt a method in which a determination as to whether entry or exit is permitted is made only for the first ticket, and subsequent tickets are allowed to pass through the ticket gate device 4 without any determination as to whether entry or exit is permitted. In this case, in actual operation, it is expected that only when entering or exiting using the same ticket gate device 4, a measure will be taken to allow passage without any determination as to whether entry or exit is permitted.

[0252] It is also possible to update the status information when a predetermined time has passed since it was first determined that entry or exit was possible using the ticket content information D2. In this case, the status information will be updated when a predetermined time, such as 10 minutes, has passed since the first issued group ticket passed through the ticket gate device 4.

[0253] Furthermore, in the case where a group ticket is issued by issuing two-dimensional codes with different contents to multiple users, when the ticket issuing server 3 performs an entry / exit judgment based on the normally issued two-dimensional code data D12 received from the ticket gate device 4 (step S21-5), or when it receives information relating to the result of the entry / exit judgment (second entry / exit judgment result information D22) and the ticket content information D2 used for the judgment from the ticket gate device 4 (step S22-8), it checks whether the group ticket identification information D53 is stored in association with the ticket identifier information D10 included in the normally issued two-dimensional code data D12 used for the judgment, and if it is stored, Furthermore, the group identification information D55 stored in association with the ticket identifier information D10 contained in the normally issued two-dimensional code data D12 used for the judgment is identified, and the number of times it is determined that entry or exit is possible using the ticket content information D2 corresponding to the normally issued two-dimensional code data D12 with which the group identification information D55 stored in association with the ticket identifier information D10 is common, or the number of times information related to the determination result that entry or exit is possible using the ticket content information D2 is received, and the counted number, i.e., information related to the number of times a specific group ticket has been used, is sent to the station attendant terminal 7 via the ticket reservation server 2 each time it increases.

[0254] In addition, if a group ticket is issued by issuing a two-dimensional code with different content to multiple users, when updating the status information (steps S21-6 and S21-10 when the entry / exit determination is made by the ticket issuing server, and steps S22-9 and S22-11 when the entry / exit determination is made by the ticket gate device), the ticket content information D2 used to determine whether entry / exit is possible, and the information related to the ticket status contained in the ticket purchase information D6 and ticket reservation information D8 linked to it and stored therein, can be updated individually.

[0255] At the station attendant terminal 7 that receives the information sent from the ticket issuing server 3 via the communication unit 73, the control unit 71 displays the received information regarding the number of times the specific group ticket has been used on the display unit 74, together with the group ticket issuance number information D54. This allows station staff using the station staff terminal 7 to easily monitor whether the number of people allowed to use a group ticket has been exceeded by comparing the information on the number of times a specific group ticket has been used, displayed on the display unit 74, with the group ticket issuance number information D54, without the need for station staff to be present at each entry and exit to count the number of people entering or exiting.

[0256] When a group ticket is used, the ticket issuing server 3 may transmit to the user terminal 8 information relating to the number of times the group ticket has been used. In this case, information relating to the user terminal 8 used by the representative of the users who will use the group ticket is stored in advance in the memory unit 32 of the ticket issuing server 3, and in the same way as when information is sent to the station attendant terminal 7, information D54 on the number of group tickets issued and information relating to the number of times a specific group ticket will be used by the group of which the user is the representative is sent is sent to such user terminal 8 and displayed on the display unit 84 of the user terminal 8. This allows the representative of a group using a group ticket to automatically know the number of people who have passed through the ticket gate device 4, and saves the trouble of having to take a roll call to confirm the number of people, for example, when traveling as a group. In this case, it is also possible to store the group ticket issue number information D54 in advance in the ticket reservation server 2, and then transmit the group ticket issue number information D54 from the ticket reservation server 2 to the user terminal 8.

[0257] [Variation 2: Unified management of tickets and coupons] As explained in variant example 2 of step S1, when coupon information D56 is stored in addition to ticket content information D2 and ticket purchase information D6 in the ticket information storage unit 322 of the storage unit 32, linked to ticket identifier information D10 contained in normally issued two-dimensional code data D12, the case where the two-dimensional code related to normally issued two-dimensional code data D12 is used to use a coupon (step S2A) will be explained according to the flowchart of Figure 32.

[0258] When a user wishes to use a coupon at a facility equipped with a facility terminal 10, the user holds the two-dimensional code issued in step S1 (a two-dimensional code stored as normally issued two-dimensional code image data D16 in memory unit 82 of user terminal 8 or a two-dimensional code stored by printing or the like on a predetermined medium such as paper in ticket issuing device 6) over coupon information reading unit 106 of facility terminal 10. When the two-dimensional code is held over coupon information reading unit 106, control unit 101 of facility terminal 10 causes coupon information reading unit 106 to read normally issued two-dimensional code data D12 from the held two-dimensional code (step S2A-1).

[0259] When the coupon information reading unit 106 reads the normally issued two-dimensional code data D12, the control unit 101 of the facility terminal 10 transmits the normally issued two-dimensional code data D12, together with the facility identification information D57 stored in the memory unit 102, from the communication unit 103 via the communication network N to the ticket reservation server 2 (step S2A-2).

[0260] The facility identification information D57 is information that can identify the facility where the facility terminal 10 is installed (if the facility terminal 10 is a smartphone, tablet terminal, etc. carried by a facility employee, it is the facility where the employee works), and means the facility where the user who holds the two-dimensional code over the coupon information reading unit 106 will use the coupon.

[0261] In the ticket reservation server 2, which receives the information transmitted from the facility terminal 10 via the communication unit 23, the control unit 21 transmits the received information from the communication unit 23 to the ticket issuing server 3 via the communication network N (step S2A-3).

[0262] In the ticket issuing server 3, which receives the information sent from the ticket reservation server 2 via the communication unit 33, the control unit 31 decodes the encoded information in the basic information section D12-1 of the normally issued two-dimensional code data D12 using the general encoding information D13 stored in the encoding information memory unit 323 of the memory unit 32 (step S2A-4).

[0263] Next, the control unit 31 searches the ticket information storage unit 322 of the storage unit 32 based on the ticket identifier information D10 contained in the decrypted information, extracts the coupon information D56 and coupon status information corresponding to the received normally issued two-dimensional code data D12, and then determines whether the coupon can be used (step S2A-5).

[0264] Specifically, for example, if the coupon status information indicates that the coupon has not been used, the available facility related to the coupon information D56 matches the facility related to the facility identification information D57 received in step S2A-3, and the coupon is within the available period related to the coupon information D56, it is determined that the coupon is available.If the coupon status information indicates that the coupon has already been used, or the available facility related to the coupon information D56 does not match the facility related to the facility identification information D57 received in step S2A-3, or the coupon is outside the available period related to the coupon information D56, it is determined that the coupon is not available. Furthermore, if the coupon information D56 corresponding to the received normally issued two-dimensional code data D12 is not extracted, it is determined that the coupon cannot be used at that point.

[0265] In addition, information relating to multiple coupons (multiple coupon information D56 and coupon status information) is stored in association with the received normally issued two-dimensional code data D12, and when multiple coupon information D56 and coupon status information corresponding to the received normally issued two-dimensional code data D12 are extracted, the control unit 31 determines whether or not all of the coupon information D56 and coupon status information can be used, and determines which coupons can be used. Also, for example, a determination may be made first as to whether the available facilities related to the coupon information D56 match the facilities related to the facility identification information D57 received in step S2A-3, and then the coupon information D56 that matches may be extracted, and only the extracted coupon information D56 may be determined as to whether it is within the available period.

[0266] If the result of the above determination is that the coupon can be used, the control unit 31 updates the corresponding coupon status information stored in the ticket information storage unit 322 of the storage unit 32 to indicate that the coupon has already been used (step S2A-6). If the coupon cannot be used, the status will not be updated. If the coupon can be used multiple times, the number of times it has been used will be recorded when the status is updated, and the status will be updated to show that it has already been used once the coupon has been used the maximum number of times it can be used.

[0267] Once the above update is complete, the control unit 31 transmits information relating to the result of the determination of whether the coupon can be used in step S2A-5 (coupon use eligibility determination result information D58) and information relating to the updated contents of the coupon status information in step S2A-6 (coupon status update information D59) from the communication unit 33 via the communication network N to the ticket reservation server 2 (step S2A-7).

[0268] In the ticket reservation server 2, when the communication unit 23 receives the coupon usage eligibility determination result information D58 and the coupon status update information D59, the control unit 21 updates the coupon status information stored in the ticket information memory unit 222 of the memory unit 22 based on the coupon status update information D59 in the same manner as the update in the ticket issuing server 3 in step S2A-6 (step S2A-8), and then transmits the coupon usage eligibility determination result information D58 from the communication unit 33 to the facility terminal 10 via the communication network N (step S2A-9).

[0269] In this modified example, as described above, information transmitted from facility terminal 10 is transmitted to ticket issuing server 3 via ticket reservation server 2, and information transmitted from ticket issuing server 3 is transmitted to facility terminal 10 via ticket reservation server 2. It is preferable that information is transmitted between facility terminal 10 and ticket issuing server 3 via ticket reservation server 2 as described above, but information may also be transmitted directly between facility terminal 10 and ticket issuing server 3 via communication network N, without going through ticket reservation server 2. Whether it is done via the ticket reservation server 2 or directly, there is no difference in that the information is ultimately sent from the ticket issuing server 3 to the facility terminal 10, or from the facility terminal 10 to the ticket issuing server 3. Therefore, this includes the case of sending information from the ticket issuing server 3 to the facility terminal 10, or the case of sending information from the facility terminal 10 to the ticket issuing server 3.

[0270] In the facility terminal 10, when the communication unit 103 receives the coupon usage eligibility determination result information D58 sent from the ticket reservation server 2, the control unit 101 causes the display unit 104 to display the received coupon usage eligibility determination result information D58 (step S2A-10).

[0271] As a result, by checking the coupon usage availability determination result information D58 displayed on the display unit 104 of the facility terminal 10, employees of the facility who use the facility terminal 10 can obtain information about whether or not the coupons held by the user can be used. In this case, coupon information D56, which is information related to the content of the coupon, and coupon status information, which is information related to the status of the coupon, are managed by the ticket issuing server 3, so the risk of counterfeit or tampered coupons being used fraudulently can be reduced compared to, for example, conventional coupons in which the content of the benefits to be obtained is simply written on paper.

[0272] In the above embodiment, we have described a case where the ticket issuing server 3 determines whether a coupon can be used, but instead of determining whether a coupon can be used in the ticket issuing server 3, the control unit 31 in the ticket issuing server 3 extracts coupon information D56 corresponding to the received normally issued two-dimensional code data D12 from the ticket information memory unit 322 of the memory unit 32, and then transmits this to the facility terminal 10 via the ticket reservation server 2. In this case, in the facility terminal 10, the control unit 101 displays the received coupon information D56 on the display unit 104, and an employee or other person at the facility where the facility terminal 10 is installed will check this and determine whether or not the coupon can be used based on the coupon information D56.

[0273] In this case, if an employee of a facility equipped with facility terminal 10 determines that a coupon can be used, he or she will use operation unit 105 to input a specified command to update the coupon status information to "used." When this command is input, the input command is sent to ticket issuing server 3 via ticket reservation server 2, and the coupon status information is updated in ticket reservation server 2 and ticket issuing server 3 based on the command.

[0274] Furthermore, for example, coupon information D56 may store information indicating that the coupon can only be used during a specific time period (for example, only usable in the morning, only usable after 5 p.m., etc.), and when determining whether or not the coupon can be used, the time period during which the coupon can be used may be compared with the time at which the coupon is used (the time at which the coupon information reading unit 106 of the facility terminal 10 reads the normally issued two-dimensional code data D12), and it may be determined that the coupon can be used only if the time at which the coupon is used is within the time period during which the coupon can be used.

[0275] Furthermore, for example, coupon information D56 may store information regarding the content of benefits that vary depending on the time of day (for example, a 10% discount in the morning, a 15% discount from 12:00 to 17:00, a 20% discount after 17:00, etc.), and when determining whether or not the coupon can be used, the content of the benefit to be granted may be determined from the time of coupon use (the time when the coupon information reading unit 106 of the facility terminal 10 reads the normally issued two-dimensional code data D12), and in addition to coupon use eligibility determination result information D58, this information regarding the benefit to be granted may also be sent to the facility terminal 10 and displayed on the display unit 104.

[0276] Another advantage of issuing coupons using this system is that by managing coupon information D56, which is information related to the content of the coupon, and coupon status information, which is information related to the status of the coupon, on the ticket issuing server 3, it is possible to easily issue coupons whose usability and the content of the benefits granted change depending on the time of day.

[0277] [C Variation 3: Entering and exiting ticket gates when multiple tickets are combined into a single ticket] A case will be described in which a single two-dimensional code is issued for the multiple tickets described in Variation 3 of step S1, and a user carrying the code enters or exits through the ticket gate device 4.

[0278] First, when the ticket issuing server 3 performs an entry / exit determination, at the time of the entry / exit determination (step S21-5), it extracts all of the multiple pieces of ticket content information D2 and ticket purchase information D6 that are stored in association with the ticket identifier information D10 included in the normally issued two-dimensional code data D12, and then makes an entry / exit determination individually for each of the multiple pieces of extracted ticket content information D2. The individual determination method at this time is the same as that explained in step S21-5. As a result of the judgment, if the control unit 31 of the ticket issuing server 3 determines that the user is able to enter or exit in relation to any of the ticket content information D2, it will judge that the user is able to enter or exit, and if it determines that the user is unable to enter or exit in relation to all of the ticket content information D2, it will judge that the user is unable to enter or exit.

[0279] In addition, when entry / exit determination is made at the ticket gate device 4, when transmitting ticket content information (step S22-5), the ticket issuing server 3 extracts all of the multiple ticket content information D2 and ticket purchase information D6 stored in association with the ticket identifier information D10 contained in the normally issued two-dimensional code data D12 received in step S22-3, and then transmits all of the extracted ticket content information D2 to the ticket gate device 4. Furthermore, at the time of entrance / exit determination (step S22-6), the ticket gate device 4 individually determines whether or not entrance / exit is permitted for each piece of received ticket content information D2. The individual determination methods at this time are the same as those described in step S22-6. In this case, too, if the control unit 41 of the ticket gate device 4 determines that entry or exit is possible in relation to any of the ticket content information D2, it will determine that the user is able to enter or exit, and if it determines that entry or exit is not possible in relation to all of the ticket content information D2, it will determine that the user is not able to enter or exit.

[0280] In addition, when updating the status information (steps S21-6 and S21-10 when the entry / exit determination is made by the ticket issuing server 3, and steps S22-9 and S22-11 when the entry / exit determination is made by the ticket gate device 4), the information relating to the ticket status is updated only for the ticket content information D2 that was determined to allow entry or exit at the time of the entry / exit determination and the ticket purchase information D6 linked to and stored therewith (and in the ticket reservation server 2, ticket reservation information D8).

[0281] This makes it possible to process users' entry and exit through a process similar to that described in the operation of the above embodiment, even when a single two-dimensional code is issued for multiple tickets.

[0282] [Variation 4: Displaying a pop-up in front of the ticket gate] In the explanation of the above operation flow, when a user enters or exits the ticket gate device 4 using a two-dimensional code issued to the user terminal 8, the user is first required to perform a predetermined operation using the operation unit 85 of the user terminal 8 to display the two-dimensional code related to the normally issued two-dimensional code image data D16 on the display unit 84. However, asking the user to perform such an operation may induce the user to operate the user terminal 8 while walking near the ticket gate device 4 (so-called "walking while using a smartphone"), which may not be desirable.

[0283] Therefore, when the user approaches an entrance station or exit station for which the ticket he / she has been assigned, the display unit 84 of the user terminal 8 may be configured to notify the user that the user is approaching the entrance station or exit station for which the ticket he / she has been assigned, and to display an image (pop-up) that allows the user to select the ticket he / she wishes to use with one touch. Specifically, this is as follows.

[0284] [(A) Configuration of modified example] As shown in Figure 33, the ticket information processing system 100B of this modified example includes, in addition to each device described in the above configuration description, a pop-up management server 110, and each device is connected via a communication network N, as shown in Figure 33.

[0285] The pop-up management server 110 is an information device such as a PC or a workstation, and performs tasks such as transmitting pop-up images to user terminals. As shown in Fig. 33, the pop-up management server 110 is configured to include, for example, a control unit 1101, a storage unit 1102, and a communication unit 1103, similar to the ticket information management server 1.

[0286] The configurations of the control unit 1101 and the communication unit 1103 are the same as those of the control unit 11 and the communication unit 13 in the ticket information management server 1, respectively. The memory unit 1102, like the memory unit 12 in the ticket information management server 1, is composed of, for example, an HDD, semiconductor memory, etc., and stores pop-up information D60 and user identification information D61 sent from the ticket reservation server 2 as described below.

[0287] [(a) Operation of the modified example] Next, the operation of the present system when displaying a pop-up on the user terminal 8 according to this modified example (step S2B) will be described with reference to the flowchart of FIG.

[0288] First, as a premise, in the ticket reservation server 2, at the time of ticket issuance, at a predetermined point after the ticket content information D2, ticket purchase information D6 and ticket reservation information D8 are linked and stored in the ticket information storage unit 222 of the storage unit 22 of the ticket reservation server 2 in step S11-8, the control unit 21 extracts information related to the departure station (boarding station) and arrival station (disembarking station) for the ticket and information related to the validity period of the ticket from the information related to the ticket content stored in the ticket information storage unit 222 of the storage unit 22 (ticket content information D2, ticket purchase information D6 and ticket reservation information D8), and sends the extracted information (hereinafter collectively referred to as pop-up information D60) together with user identification information D61, which is identification information (for example, a user number assigned to each user) that can identify the user who was issued the ticket related to the information, from the communication unit 23 to the pop-up management server 110 via the communication network N (step S2B-1).

[0289] In the pop-up management server 110, when the communication unit 1103 receives the information sent from the ticket reservation server 2, the control unit 1101 links the received pop-up information D60 and user identification information D61 and stores them in the memory unit 1102 (step S2B-2). At this time, the control unit 1101 groups the received pop-up information D60 by departure station, arrival station, and validity period, and stores the grouped information in the memory unit 1102 so that the corresponding user-specific information D61 can be extracted when the pop-up described below is displayed.

[0290] Furthermore, in the pop-up management server in which the pop-up information D60 and the user identification information D61 are stored in the memory unit 1102, at a predetermined time every day before the train starts running, the control unit 1101 pre-extracts only the pop-up information D60 and the associated user identification information D61 whose validity period includes the relevant day, based on the information regarding the ticket validity period contained in the pop-up information D60 (step S2B-3).

[0291] When a ticket is issued, the user terminal 8 stores the normally issued two-dimensional code image data D16, ticket number information D11, and ticket reservation information D8 in the ticket information storage unit 822 of the storage unit 82 in step S11-22.From that point on, the user terminal 8 constantly acquires the location information of the user terminal 8 and, ultimately, the user who owns it in the background using the location information acquisition unit 87, and then transmits the acquired location information (user location information D62) together with the user identification information D61 from the communication unit 83 via the communication network N to the pop-up management server 110 (step S2B-4).

[0292] The pop-up management server 110 receives the user location information D62 and user identification information D61 sent from the user terminal 8 via the communication unit 1103, and searches the information extracted in advance for each day in step S2B-3 based on the user identification information D61 received in step S2B-4. If information matching the user identification information D61 is found, the pop-up information D60 stored in association with the user identification information D61 is extracted (step S2B-5).

[0293] Next, the control unit 1101 of the pop-up management server 110 compares the position of the user terminal 8 according to the user position information D62 received in step S2B-4 with the position of the boarding station or disembarking station included in the pop-up information D60 extracted in step S2B-5, and determines whether the user has approached the boarding station or disembarking station, i.e., whether the distance between the position of the user terminal 8 according to the user position information D62 and the position of the boarding station or disembarking station included in the pop-up information D60 is within a predetermined distance (step S2B-6). As a method of determination, for example, the location information of all stations whose information may be included as boarding or disembarking stations in the pop-up information D60 is stored in advance in the memory unit 1102 of the pop-up management server 110, and this information is used to calculate the distance between the location of the user terminal 8 related to the user location information D62 and the location of the boarding or disembarking station included in the pop-up information D60, and then it is determined whether the calculated distance is within a predetermined distance.

[0294] In step S2B-6, if it is determined that the distance between the position of the user terminal 8 according to the user position information D62 and the position of the boarding station or disembarking station included in the pop-up information D60 is within a predetermined distance, the control unit 1101 in the pop-up management server 110 creates an image for the pop-up (step S2B-7). The pop-up image is an image that includes, for example, a message with predetermined content notifying the user that they are approaching an entry or exit station using a ticket that they hold (i.e., a ticket for which the normally issued two-dimensional code image data D16 is stored in the user terminal 8), information regarding the outline of the contents of the ticket including information regarding the boarding and disembarking stations, and a button to be operated when they wish to use the ticket.

[0295] Once the pop-up image is created, the control unit 1101 of the pop-up management server 110 transmits the pop-up image data D63, which is the image data relating to the created pop-up image, from the communication unit 1103 via the communication network N to the user terminal 8 that transmitted the location information, etc. in step S2B-4 (step S2B-8).

[0296] In the user terminal 8 that receives the popup image data D63 sent from the popup management server 110 via the communication unit 83, the control unit 81 causes the display unit 84 to display the popup image related to the received popup image data D63 (step S2B-9).

[0297] In addition, without creating a pop-up image in the pop-up management server 110, if it is determined in step S2B-6 that the distance between the position of the user terminal 8 related to the user position information D62 and the position of the boarding station or disembarking station included in the pop-up information D60 is within a predetermined distance, the pop-up information D60 can be sent from the pop-up management server 110 to the user terminal 8 that sent the position information etc. in step S2B-4, and the control unit 81 in the user terminal 8 can create a pop-up image and display it on the display unit 84. In either case, the display of the pop-up image on the user terminal 8 is based on information sent from the pop-up management server 110, so the pop-up management server 110 is causing the user terminal 8 to display the pop-up image.

[0298] After the pop-up image is displayed on the display unit 84, if the user wishes to use the ticket related to the displayed pop-up image, the user operates the button included in the pop-up image using the operation unit 85 of the user terminal 8 (step S2B-10), and when the button included in the pop-up image is operated, the control unit 81 causes the display unit 84 to display the two-dimensional code related to the corresponding normally issued two-dimensional code image data D16 stored in the ticket information memory unit 822 of the memory unit 82 (step S2B-11).

[0299] In the above, we have explained the case where in step S2B-4, the user terminal 8 constantly acquires location information using the location information acquisition unit 87 and transmits the acquired user location information D62 to the pop-up management server 110. However, the user terminal 8 may acquire location information using the location information acquisition unit 87 only when the user carrying the terminal approaches a station, and transmit the acquired user location information D62 to the pop-up management server 110.

[0300] As a means for the user terminal 8 to grasp the approach to the station, for example, a beacon can be used. In this case, for example, beacons are installed at each station, and a user terminal 8 capable of receiving beacon signals emitted from the beacons installed at the station is used, and only when the user terminal 8 receives a beacon signal from the beacon installed at the station, the location information acquisition unit 87 acquires location information, and the acquired user location information D62 is sent to the pop-up management server 110 together with user identification information D61. The transmitting device installed at the station is not limited to a beacon, as long as it can transmit a predetermined signal to notify the user terminal 8 of its approach to the station. For example, an existing wireless LAN access point or the like may be used.

[0301] Furthermore, the method of detecting the user's approach to a station is not limited to using the location information of the user terminal 8, and it is also possible to configure the user terminal 8 not to use the location information acquired by the location information acquisition unit 87.

[0302] For example, a beacon is installed at each station, and the beacon signal emitted from the beacon contains information that can identify the station, such as an ID assigned to each station.When a beacon signal from a beacon installed at a station is received by a user terminal 8, the information that can identify the station contained in the beacon signal is transmitted to the pop-up management server 110 from the communication unit 83 via the communication network N, together with user identification information D61. In this case, in the pop-up management server 110, if the user identification information D61 linked and stored from the pop-up information D60 extracted in step S2B-3 matches the user identification information D61 received from the user terminal 8, and the information relating to the boarding station or disembarking station included in the pop-up information D60 matches the information that can identify the station included in the beacon signal received from the user terminal 8, then the pop-up image will be created and the pop-up image data D63 will be sent from the communication unit to the user terminal 8 via the communication network N.

[0303] In this case, the transmitting device installed in the station is not limited to a beacon, and may be any device capable of transmitting a predetermined signal containing information that can identify the station, such as an ID that is set for each station. For example, an existing wireless LAN access point may be utilized, and a signal containing information that can identify the station where the access point is installed may be transmitted from such an access point.

[0304] Furthermore, for example, instead of a signal such as a beacon signal, a sound or an image may be used. When using audio, for example, a sound of a specific frequency (preferably in a frequency band that humans cannot hear) could be emitted at a station, and when this is received by the user terminal 8, the pop-up management server 110 could detect that the user is approaching the boarding or disembarking station included in the pop-up information D60, and cause the user terminal 8 to display a pop-up image. Furthermore, when images are used, for example, the pop-up management server 110 may store a facial photograph of each user, and when the user whose facial photograph is stored is identified by an image taken by a camera installed at a station, the pop-up management server 110 may detect the user's approach to the boarding or disembarking station included in the pop-up information D60, and cause the user terminal 8 to display a pop-up image.

[0305] Furthermore, for example, the memory unit 1102 of the pop-up management server 110 may store information relating to the status (unused, used, etc.) of the ticket for which the pop-up information D60 is stored, and when a user approaches a boarding or disembarking station included in the pop-up information D60, the control unit 1101 of the pop-up management server 110 may further determine whether the status of the corresponding ticket is usable for entry or exit from that station (for example, usable if unused, unusable if used, etc.), and may display a pop-up image on the user terminal 8 only if the ticket is usable.

[0306] In addition, instead of creating a pop-up image and transmitting the pop-up image data (steps S2B-7 to S2B-8), the pop-up management server 110 may transmit only a predetermined command to the user terminal 8 used by the user approaching the station to notify the user that the user is approaching the entry or exit station using the ticket he or she is holding, and the user terminal 8 that receives this command may notify the user that the user is approaching the entry or exit station using the ticket he or she is holding, for example, by sound, vibration, etc.

[0307] Furthermore, when issuing a ticket to the user terminal 8 in step S11, the location information of the departure station (boarding station) and arrival station (disembarking station) related to the ticket purchased in advance by the user is sent from the pop-up management server 110 etc. to the user terminal 8 and stored in the user terminal 8. When the user approaches the departure station (boarding station) or arrival station (disembarking station) related to the ticket purchased, the user terminal 8 determines whether the user is approaching the boarding station or disembarking station according to the user terminal application 821, without going through steps such as sending the location information etc. to the pop-up management server 110 (step S2B-4) or receiving the pop-up image data D63 from the pop-up management server 110 (step S2B-8). If it is determined that the user is approaching the boarding station or disembarking station, the user is notified by displaying a pop-up image or the like, and it is also possible to notify the user each time without going through the pop-up management server 110.

[0308] In addition, some of the processing described above as being performed by the popup management server 110 can also be appropriately performed by the user terminal 8, as long as it does not interfere with achieving the effects described below.

[0309] [(c) Effects of Modifications] According to this modified example, when a user approaches a boarding station or disembarking station associated with a ticket for which data such as normally issued two-dimensional code image data D16 is stored in the ticket information memory unit 822 of the memory unit 82 of the user terminal 8, a pop-up image is automatically displayed on the display unit 84, or the user can be notified by sound, vibration, etc. that they are approaching the boarding station or disembarking station associated with the ticket they hold.Furthermore, by simply operating the button included in the pop-up image, the two-dimensional code associated with the normally issued two-dimensional code image data D16 will be displayed on the display unit 84.

[0310] This means that when a user approaches the boarding or disembarking station for which they have a ticket, they can instantly see from the pop-up image that they have a ticket that can be used at that station, without having to launch the corresponding application, check whether they have a ticket that can be used at that station, and then select the ticket to use.Furthermore, by simply pressing the button displayed on the pop-up image, the two-dimensional code related to the normally issued two-dimensional code image data D16 can be used, which reduces the number of operations that the user needs to perform near the ticket gate device 4 and reduces the risk of the user operating the user terminal 8 while walking near the ticket gate device 4.

[0311] [3 Step S3: Web Check-in / Check-out] Next, in order to record the entry and exit history according to the user's entry and exit even at stations that do not have ticket gate devices 4, the flow of web check-in or web check-out, i.e., determining whether entry and exit are possible from the user terminal 8 without going through the ticket gate device 4, and reflecting the entry and exit history in the information related to the ticket status contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 stored in the ticket reservation server 2 and the ticket issuing server 3, will be explained using the flowchart in Figure 18.

[0312] [(1) Operational flow] As a premise, in order to enable web check-in and web check-out, at stations that do not have ticket gate devices 4, the station manager or other person in charge will post a specified two-dimensional code in a specified location, such as a pillar, near the entrance and exit of each station (the boundary between inside and outside the ticket gate).

[0313] Specifically, two types of two-dimensional codes, one for check-in and one for check-out, are posted near the entrances and exits of each station. Of these, the check-in code is a two-dimensional code that stores, for example, the name of the station where the two-dimensional code is posted, version information, and information indicating that it is for check-in (the information included in the two-dimensional code is collectively referred to as web check-in information D24), and is posted outside the entrances and exits of each station. Also, the check-out code is a two-dimensional code that stores, for example, the name of the station where the two-dimensional code is posted, version information, and information indicating that it is for check-out (the information included in the two-dimensional code is collectively referred to as web check-out information D25), and is posted inside the entrances and exits of each station.

[0314] The version information included in the web check-in information D24 and the web check-out information D25 is periodically updated, and the displayed two-dimensional code is replaced each time. It is also preferable to display whether the two-dimensional code is for check-in or check-out, so that the user does not make a mistake.

[0315] When a user wishes to perform web check-in or web check-out, the user first performs a predetermined operation using the operation unit 85 of the user terminal 8, accesses a predetermined web page, launches a predetermined application, etc., to establish a connection with the ticket reservation server 2 via the communication network N, and then selects the data that the user wishes to use for web check-in or web check-out from the normally issued two-dimensional code image data D16 stored in the ticket information memory unit 822 of the memory unit 82 (step S3-1). In step S3-1, it is sufficient for the user to select the ticket he or she wishes to use, and it is not necessary for the selection to be made from the normally issued two-dimensional code image data D16. For example, the display unit 84 of the user terminal 8 may be configured to display a list containing predetermined information about each ticket purchased by the user, such as information about the ticket's validity period and information about the ticket's validity zone, and the user may select the ticket he or she wishes to use from the list.

[0316] Next, the user operates the operation unit 85 of the user terminal 8 to use the imaging unit 86 to capture a two-dimensional code for web check-in posted at the station if the user is using web check-in, or to capture a two-dimensional code for web check-out posted at the station if the user is using web check-out. Once the two-dimensional code has been captured, the control unit 81 reads the web check-in information D24 or web check-out information D25, which is the stored content of the two-dimensional code captured by the imaging unit 86, from the two-dimensional code (step S3-2). As described above, the web check-in information D24 or web check-out information D25 includes information related to the name of the station where the two-dimensional code is posted. Therefore, when this information is read by the user terminal 8, the read information includes information related to the name of the station where the user terminal 8, and therefore the user, is located.

[0317] Next, the control unit 81 of the user terminal 8 causes the position information acquisition unit 87 to acquire position information (user position information D26) of the user terminal 8 and, in turn, of the user carrying it (step S3-3).

[0318] When the user location information D26 is acquired by the location information acquisition unit 87, the control unit 81 transmits the web check-in information D24 or web check-out information D25 read in step S3-2 and the user location information D26 acquired in step S3-3, together with the ticket reservation information D8 corresponding to the data selected by the user in step S3-1, from the communication unit 83 via the communication network N to the ticket reservation server 2 (step S3-4).

[0319] In the ticket reservation server 2 that receives the information transmitted from the user terminal 8 via the communication unit 23, the control unit 21 checks the version information contained in the web check-in information D24 or the web check-out information D25, and if it is the latest version, identifies the station used by the user using the received user location information D26 and the railway station information D27 stored in the railway station information storage unit 223 of the storage unit 22 (step S3-5). The railway station information D27 is information including location information (longitude and latitude) of the location of each station on a railway line. If the version information included in the web check-in information D24 or the web check-out information D25 is not the latest version, the control unit 21 notifies the user terminal 8 to that effect and ends the process.

[0320] Specifically, since the railway station information D27 includes the location information of each station as described above, this is compared with the received user location information D26, and, for example, a station that is within a predetermined distance from the location related to the user location information D26 and is closest to the location related to the user location information D26 is identified as the station used by the user. In this case, if there is no station within the predetermined distance from the location related to the user location information D26, a notification to that effect is sent to the user terminal 8, and the process ends.

[0321] Furthermore, if there are multiple stations within a predetermined distance from the position related to the user position information D26, information related to these multiple stations may be transmitted to the user terminal 8 as candidate stations, and the user may select a station to use from these multiple stations using the operation unit 85 of the user terminal 8. In this case, even if the accuracy of the user position information D26 acquired by the position information acquisition unit 87 is not sufficient, it is possible for the user to identify the correct station to use.

[0322] Next, the control unit 21 compares the station name identified in step S3-5 with the information regarding the station name contained in the web check-in information D24 or the web check-out information D25 received in step S3-4, and determines whether the station names match (step S3-6).

[0323] If the station name identified in step S3-5 matches the station name included in the web check-in information D24 or web check-out information D25 received in step S3-4, the control unit 21 sends information related to the station name (used station information D28) from the communication unit 23 via the communication network N to the user terminal 8 (step S3-7). If the station name identified in step S3-5 does not match the station name included in the web check-in information D24 or web check-out information D25 received in step S3-4, a notification to that effect is sent to the user terminal 8, and the process ends.

[0324] Although it is not preferable from the viewpoint of preventing fraud, it is also possible to configure the ticket reservation server 2 to either receive the web check-in information D24 or the web check-out information D25 in step S3-4 or identify the station to be used based on the location information in step S3-5 without going through the above process, and to use the station name information contained in the web check-in information D24 or the web check-out information D25, or the station name information of the station to be used identified based on the user location information D26 in step S3-5, as the station name information D28. In this case, the information that needs to be transmitted from the user terminal 8 to the ticket reservation server 2 in step S3-4 is only either the web check-in information D24 or the web check-out information D25, or the user location information D26.

[0325] In the user terminal 8 that has received the use station information D28 via the communication unit 83, the control unit 81 causes the display unit 84 to display the received use station information D28 (step S3-8). When the station information D28 is displayed on the display unit 84, the user checks it, and if the station is correct, uses the operation unit 85 to perform the required web check-in or web check-out operation.When the operation is performed, the control unit 81 sends information that the operation has been performed (web check-in / out instruction information D29) from the communication unit 83 to the ticket reservation server 2 via the communication network N (step S3-9).

[0326] In the ticket reservation server 2 that receives the web check-in / out instruction information D29 via the communication unit 23, the control unit 21 searches the ticket information storage unit 222 of the memory unit 22 based on the ticket reservation information D8 received in step S3-4, extracts the corresponding ticket purchase information D6, and then transmits the ticket purchase number information D7 contained therein, together with the station information D28 used and information related to the date and time of use (information related to the date and time at that time, usage date and time information D30), from the communication unit 23 to the ticket issuing server 3 via the communication network N (step S3-10).

[0327] In the ticket issuing server 3, which receives the information sent from the ticket reservation server 2 via the communication unit 33, the control unit 31 searches the ticket information storage unit 322 of the storage unit 32 based on the ticket purchase number information D7, extracts the corresponding ticket content information D2 and ticket purchase information D6, and then compares the information regarding the ticket's validity period and validity zone contained in the ticket content information D2 with the received station information D28 and usage date and time information D30 to determine whether web check-in or web check-out is possible, i.e., whether the user can enter or exit the ticket gate (step S3-11).

[0328] Specifically, in the case of web check-in, the entry and exit history is confirmed from the information related to the ticket status contained in the ticket content information D2 and ticket purchase information D6, and then the station information D28 and date and time of use information D30 are compared with the information related to the ticket's validity period and validity zone contained in the ticket content information D2. Then, for example, if there is no entry history or the ticket has already exited at an intermediate station, and further, the station related to the station information D28 is within the validity zone related to the ticket content information D2, and the date and time of use related to the date and time of use information D30 is within the validity period related to the ticket content information D2, web check-in is determined to be possible, but if any one of these conditions is not met, web check-in is determined to be impossible.

[0329] In the case of web checkout, the entry and exit history is confirmed from the information related to the ticket status contained in the ticket content information D2 and the ticket purchase information D6, and then the station information D28 and date and time of use information D30 are compared with the information related to the ticket validity period and validity zone contained in the ticket content information D2. Then, for example, in the case of after entry but before exit, if the station used according to the station information D28 is within the validity zone related to the ticket content information D2, and the date and time of use according to the date and time of use information D30 is within the validity period related to the ticket content information D2, web checkout is deemed possible, but if any one of these conditions is not met, web checkout is deemed impossible.

[0330] When the above determination is completed, the control unit 31 updates the information relating to the status of the ticket, which is included in the ticket content information D2 and the ticket purchase information D6 stored in the ticket information storage unit 322 of the storage unit 32 (step S3-12). Specifically, if web check-in is possible, the information regarding the ticket status contained in ticket content information D2 and ticket purchase information D6 will be set to ticket in use (after entry but before exit), and if web check-out is possible, the information regarding the ticket status contained in ticket content information D2 and ticket purchase information D6 will be set to already used (after exit at the disembarkation station) or in use (after exit at an intermediate station).

[0331] Once the above update is complete, the control unit 31 transmits information relating to the web check-in or web check-out determination result in step S3-11 (web check-in / check-out determination result information D31) and information relating to the updated information relating to the ticket status included in the ticket content information D2 and ticket purchase information D6 in step S3-12 (web check-in / check-out status update information D32) from the communication unit 33 via the communication network N to the ticket reservation server 2 (step S3-13).

[0332] In the ticket reservation server 2, when the communication unit 23 receives the information sent from the ticket issuing server 3, the control unit 21 updates the information related to the ticket status contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 stored in the ticket information memory unit 222 of the memory unit 22 in the same manner as the update in the ticket issuing server 3 in step S3-12 (step S3-14).

[0333] Once the above update is complete, the control unit 21 transmits the web check-in / check-out determination result information D31 from the communication unit 23 via the communication network N to the user terminal 8 (step S3-15), and in the user terminal 8 that receives this via the communication unit 83, the control unit 81 displays on the display unit 84 whether web check-in or web check-out is possible based on the web check-in / check-out determination result information D31 (step S3-16).

[0334] [(2) Effects of this step] According to the ticket information processing system 100 of this embodiment, the following effects can be obtained by enabling web check-in / out as described above.

[0335] Conventionally, at stations where ticket gates 4 are not installed, such as unmanned stations, the possibility of entry at the entrance station is determined based on the information acquired by the ticket gates 4, and entry is permitted only when entry is possible, and no history of entry can be kept. Therefore, users who hold tickets with such stations as their entry station have no choice but to be allowed to exit at the exit station regardless of whether they have an entry history or not. However, in such a situation, it is easy to commit fraud by purchasing tickets only for the sections of the journey near the boarding station and the disembarking station, and boarding without purchasing tickets for the intermediate sections. This issue becomes even more serious when two-dimensional codes, which, unlike magnetic tickets, can be easily handed over as image data, are used for tickets, making it easier to purchase and resell them in large quantities, which could lead to the risk of them being used for organized fraud.

[0336] In this regard, according to this embodiment, by allowing users to perform web check-in / out using the user terminal 8, it becomes possible to determine whether a user entering from a station where a ticket gate device 4 is not installed whether they are allowed to enter or exit, and depending on the determination result, the user's entry history is recorded on the ticket reservation server 2 and ticket issuing server 3 (updating information related to the ticket status contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8). Therefore, even if a user enters through a station where ticket gate device 4 is not installed, if there is no history of entry, it will be possible to deny exit at the station where the user exits, thereby reducing the risk of unauthorized boarding by a user who enters through a station where ticket gate device 4 is not installed.

[0337] However, if the system simply determines whether a user can enter or exit based on the information sent from the user terminal 8, and then records the user's entry history in the ticket reservation server 2 and ticket issuing server 3 based on the determination result, web check-in / out would be possible regardless of where the user terminal 8 is located. While this is better than being able to exit without any history, it does allow people to check in and out online in advance, and if a ticket that has been processed in this way is used, it cannot prevent unauthorized boarding. Furthermore, if the ticket is resold after online check-in and check-out, there is a risk that it could be used for organized fraud such as the one described above.

[0338] Therefore, in this embodiment, the station where the user enters or exits is specified using the web check-in information D24 or web check-out information D25 acquired by the user terminal 8 and the user location information D26, and by restricting web check-in / out to those entering or exiting at that station, only those who are actually at the station can perform web check-in / out, thereby reducing the risks described above. Although the risk of fraud still exists because web check-in / out can be performed by going to the station in advance, going to the station each time is extremely time-consuming, making it difficult to do this on an organized, large-scale basis.

[0339] Furthermore, if user location information D26 is simply obtained from user terminal 8, web check-in is possible from inside the train, and a user can commit train fraud by performing web check-in on the train when passing through the boarding station related to the ticket to be used when disembarking. However, by using web check-in information D24 or web check-out information D25 read from a two-dimensional code posted at the station, if a user wishes to commit train fraud as described above, the user will have to take the trouble of disembarking at the station and have the two-dimensional code read by user terminal 8, and since this type of behavior is clearly unnatural, the risk of train fraud as described above can be reduced.

[0340] Furthermore, if web check-in information D24 or web check-out information D25 is only acquired from the user terminal 8, there is a risk that if the two-dimensional code posted at the station is stolen or photographed and reproduced in advance, this code may be used to enable web check-in at places other than the station, but this risk can be reduced by using user position information D26 acquired by the user terminal 8. It is also possible to identify users attempting fraud and stations where the two-dimensional code has been stolen or photographed and leaked. Furthermore, by including version information in the web check-in information D24 and the web check-out information D25, and by making it so that only the latest information can be used for web check-in / out, and by frequently updating the version information, the risk of using a two-dimensional code that has been stolen or photographed and copied in advance can be reduced.

[0341] Furthermore, if the web check-in information D24 and the web check-out information D25 contain version information and only the latest information can be used for web check-in / out, and if a user attempts to perform web check-in / out using web check-in information D24 or web check-out information D25 that does not have the latest version information, the ticket reservation server 2 will store the information received from the user terminal 8 and leave a history, and will also prevent the user from using web check-in / out thereafter.This will further strengthen measures against fraudulent use of old web check-in information D24 or web check-out information D25 by taking a photo of the two-dimensional code posted at the station in advance.

[0342] [4 Step S4: Batch entry and exit] Next, the flow of performing web check-in / out together using the user terminal 8 for a user who has been issued a ticket based on the normally issued two-dimensional code image data D16 as described in step S11, and a companion who will use the ticket linked to the user, will be explained using the flowcharts in Figures 19 and 20.

[0343] [(1) Operational flow] In this case, the user first receives the normally issued two-dimensional code image data D16 in step S11, which is then stored in the ticket information storage unit 822 of the storage unit 82, and then receives the associated two-dimensional code image data D33 for companions, which is image data of the two-dimensional code relating to tickets to be used by companions other than the user who owns the user terminal 8 (step S4-1). When performing web check-in / check-out for multiple companions at the same time, the user receives two copies of the code for each companion.

[0344] The process for receiving the issuance of the two-dimensional code image data D33 for a companion is basically the same as the process for receiving the issuance of the normally issued two-dimensional code image data D16 described in step S11. The two-dimensional code image data D33 for a companion is transmitted from the ticket reservation server 2 to the user terminal 8 via the communication network N, and in the user terminal 8, the control unit 81 stores the received two-dimensional code image data D33 for a companion in the ticket information storage unit 822 of the storage unit 82. The content of the two-dimensional code data (two-dimensional code data for companions) that is the basis of the two-dimensional code image data D33 for companions is basically the same as the normally issued two-dimensional code data D12 described in step S11.

[0345] Once the two-dimensional code image data D33 for the companion is stored in the ticket information memory unit 822 of the memory unit 82, the user performs a predetermined operation using the operation unit 85 of the user terminal 8, and causes the two-dimensional code related to the two-dimensional code image data D33 for the companion to be printed on a predetermined medium such as paper using any printing means (step S4-2).

[0346] After the two-dimensional code related to the companion two-dimensional code image data D33 has been printed, if the user goes to a station and wishes to perform web check-in or web check-out, first, the user performs a predetermined operation using the operation unit 85 of the user terminal 8 to access a predetermined web page, launch a predetermined application, or the like, thereby establishing a connection with the ticket reservation server 2 via the communication network N, and then selects the data that the user wishes to use for web check-in or web check-out from the normally-issued two-dimensional code image data D16 stored in the ticket information storage unit 822 of the storage unit 82 (step S4-3). Note that, as described in step S3, it is not essential to select from the normally-issued two-dimensional code image data D16, and any selection method can be used as long as it allows the user to select the ticket they wish to use, such as selecting from a predetermined list.

[0347] Next, the user selects the data that the companion wishes to use for web check-in or web check-out from the companion two-dimensional code image data D33 stored in the ticket information storage unit 822 of the storage unit 82 (step S4-4). Note that here too, it is not essential to select from the companion two-dimensional code image data D33, and any selection method can be used as long as it allows the companion to select the ticket they wish to use, such as selecting from a predetermined list.

[0348] In this case, the user can select multiple companion two-dimensional code image data D33 and perform web check-in or web check-out for multiple companions at once. In this case, the subsequent processing will be performed on the data related to such multiple companions at once.

[0349] The processing from this point onwards is the same as that from step S3-2 onwards in step S3, except that processing is performed for the user and their companion(s) together. First, the user operates the operation unit 85 of the user terminal 8 to use the imaging unit 86 to photograph the two-dimensional code for web check-in or two-dimensional code for web check-out posted at the station, and once the two-dimensional code has been photographed, the control unit 81 reads the stored contents of the two-dimensional code photographed by the imaging unit 86, that is, the web check-in information D24 or web check-out information D25 (step S4-5).

[0350] Next, the control unit 81 causes the position information acquisition unit 87 to acquire the position information (user position information D26) of the user terminal 8 (step S4-6). When the user location information D26 is acquired by the location information acquisition unit 87, the control unit 81 transmits the web check-in information D24 or web check-out information D25 read in step S4-5 and the user location information D26 acquired in step S4-6, together with the ticket reservation information D8 corresponding to the normally issued two-dimensional code image data D16 selected in step S4-3 and the companion two-dimensional code image data D33 selected in step S4-4, from the communication unit 83 via the communication network N to the ticket reservation server 2 (step S4-7).

[0351] In the ticket reservation server 2 that receives the information sent from the user terminal 8 via the communication unit 23, the control unit 21 checks the version information contained in the web check-in information D24 or the web check-out information D25, and if it is the latest version, it identifies the station used by the user using the received user location information D26 and the railway station information D27 stored in the railway station information storage unit 223 of the storage unit 22 (step S4-8).

[0352] Next, the control unit 21 compares the station name identified in step S4-8 with the information related to the station name contained in the web check-in information D24 or web check-out information D25 received in step S3-4, and determines whether the station names match (step S4-9).If the station name identified in step S4-8 matches the station name contained in the web check-in information D24 or web check-out information D25 received in step S4-7, the control unit 21 transmits information related to the station name (station information D28 used) from the communication unit 23 via the communication network N to the user terminal 8 (step S4-10).

[0353] In the user terminal 8 that receives the station information D28 via the communication unit 83, the control unit 81 displays the received station information D28 on the display unit 84 (step S4-11), and after the user confirms this and is sure that the station is correct, the user uses the operation unit 85 to perform the required web check-in or web check-out operation.Once the operation is performed, the control unit 81 transmits information indicating that the operation has been performed (web check-in / check-out instruction information D29) from the communication unit 83 via the communication network N to the ticket reservation server 2 (step S4-12).

[0354] In the ticket reservation server 2 that receives the web check-in / out instruction information D29 via the communication unit 23, the control unit 21 searches the ticket information memory unit 222 of the memory unit 22 based on the ticket reservation information D8 received in step S4-7, extracts the ticket purchase information D6 corresponding to the normally issued two-dimensional code image data D16 selected in step S4-3 and the ticket purchase information D6 corresponding to the companion two-dimensional code image data D33 selected in step S4-4, and then transmits the ticket purchase number information D7 contained therein, together with the station information D28 used and information related to the date and time of use (date and time of use information D30), from the communication unit 23 to the ticket issuing server 3 via the communication network N (step S4-13).

[0355] In the ticket issuing server 3 that has received the information transmitted from the ticket reservation server 2 via the communication unit 33, the control unit 31 searches the ticket information storage unit 322 of the storage unit 32 based on the ticket purchase number information D7, extracts the corresponding ticket content information D2 and ticket purchase information D6, and then compares the information relating to the ticket validity period and the information relating to the ticket validity zone contained in the ticket content information D2 with the received station information D28 and use date and time information D30, and selects the ticket and step information relating to the normally issued two-dimensional code image data D16 selected in step S4-3. A determination is made as to whether web check-in or web check-out is possible for both tickets associated with the companion two-dimensional code image data D33 selected in S4-4, and web check-in / check-out determination result information D31, which is information relating to the determination result of web check-in or web check-out corresponding to the normally issued two-dimensional code image data D16, and companion web check-in / check-out determination result information D31A, which is information relating to the determination result of web check-in or web check-out corresponding to the companion two-dimensional code image data D33, are obtained (step S4-14).

[0356] Once the above determination is completed, the control unit 31 updates both the ticket content information D2 corresponding to the normally issued two-dimensional code image data D16 selected in step S4-3 and the ticket status information contained in the ticket purchase information D6 stored in the ticket information storage unit 322 of the storage unit 32, and the ticket content information D2 corresponding to the companion two-dimensional code image data D33 selected in step S4-4 and the ticket status information contained in the ticket purchase information D6 (step S4-15).

[0357] Once the above update is complete, the control unit 31 transmits information relating to the web check-in or web check-out judgment result in step S4-14 (web check-in / check-out judgment result information D31 and companion web check-in / check-out judgment result information D31A) and information relating to the update contents of the ticket status information included in the ticket content information D2 and ticket purchase information D6 in step S4-15 (web check-in / check-out status update information D32 corresponding to the normally issued two-dimensional code image data D16 and companion web check-in / check-out status update information D32A corresponding to the companion two-dimensional code image data D33) from the communication unit 33 via the communication network N to the ticket reservation server 2 (step S4-16).

[0358] In the ticket reservation server 2, when the communication unit 23 receives the information transmitted from the ticket issuing server 3, the control unit 21 updates both the ticket content information D2 corresponding to the normally issued two-dimensional code image data D16 selected in step S4-3, the ticket purchase information D6, and the ticket status information contained in the ticket reservation information D8 stored in the ticket information memory unit 222 of the memory unit 22, and the ticket content information D2 corresponding to the companion two-dimensional code image data D33 selected in step S4-4, the ticket purchase information D6, and the ticket status information contained in the ticket reservation information D8 in the same way as the update in the ticket issuing server 3 in step S4-15 (step S4-17).

[0359] Once the above update is complete, the control unit 21 transmits the web check-in / check-out judgment result information D31 corresponding to the normally issued two-dimensional code image data D16 selected in step S4-3 and the companion web check-in / check-out judgment result information D31A corresponding to the companion two-dimensional code image data D33 selected in step S4-4 from the communication unit 33 via the communication network N to the user terminal 8 (step S4-18).In the user terminal 8 that receives this via the communication unit 83, the control unit 81 displays on the display unit 84 whether the user and companion can web check in or check out based on the web check-in / check-out judgment result information D31 and the companion web check-in / check-out judgment result information D31A (step S4-19).

[0360] [(2) Effects of this step] According to the ticket information processing system 100 of this embodiment, as described above, it is possible to perform web check-in / out simultaneously for a user who carries a user terminal 8 and a companion who does not carry a user terminal 8, thereby obtaining the following effects.

[0361] That is, as explained in step S3, by allowing users to perform web check-in / out using a user terminal 8 such as a smartphone or tablet terminal, it becomes possible for users who enter through a station where a ticket gate device 4 is not installed to be denied exit at the exiting station if there is no history of entry. However, in this case, anyone who does not carry a user terminal 8 will not be able to use stations where a ticket gate device 4 is not installed. In this regard, for example, when a family goes out together, it is often the case that the parents have smartphones, tablets, etc., but the children do not, and this situation is inconvenient.

[0362] In this regard, according to this embodiment, a user carrying a user terminal 8 can perform web check-in / out not only for the ticket associated with the normally issued two-dimensional code image data D16 that the user uses, but also for the ticket associated with the companion's two-dimensional code image data D33 that the companion uses.

[0363] This makes it possible for even a person who does not carry a user terminal 8, if they are an accompanying person entering or exiting together with a user who carries a user terminal 8, to determine whether or not they are permitted to enter or exit, and depending on the determination result, to record their entry history in the ticket reservation server 2 and the ticket issuing server 3 (updating information relating to the ticket status contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8). Therefore, even if web check-in / check-out is required when entering and exiting a station where a ticket gate device 4 is not installed, a person who does not carry a user terminal 8 can still use such a station as long as they are accompanied by a user who carries a user terminal 8.

[0364] [5 Step S5: Station staff determine entry and exit] Next, we will explain the process for determining whether a user can enter or exit and updating information related to the ticket status when station staff at the station make the decision without using the ticket gate device 4, separately for when the counter processing machine 5 is used and when the station staff terminal 7 is used.

[0365] [(1) Operational flow] [A Step S51: When using a counter processing machine] First, the flow of operations when a station attendant uses the ticket window processing machine 5 will be described with reference to the flowchart of FIG.

[0366] For example, if the ticket gate device 4 cannot be used at a station where a station staff member is present due to some kind of trouble, or if the user goes to a station where a station staff member is present but no ticket gate device 4 is installed, and the user wishes to enter the station through the ticket gate before boarding a train, or to exit the station through the ticket gate after boarding a train, the user performs a predetermined operation using the operation unit 85 of the user terminal 8 to display on the display unit 84 the two-dimensional code related to the normally issued two-dimensional code image data D16 and the ticket number related to the ticket number information D11 for the ticket the user wishes to use for entry or exit, which are stored in the ticket information storage unit 822 of the storage unit 82, and then presents the displayed two-dimensional code and ticket number to the station staff member. Furthermore, in step S12, if the user uses a ticket issued on a predetermined medium such as paper, the user presents the ticket to the station staff.

[0367] After confirming the two-dimensional code related to the normally-issued two-dimensional code image data D16 and the ticket number related to the ticket number information D11 presented by the user, the station attendant holds the presented two-dimensional code over the ticket information reading unit 56 of the ticket counter processing machine 5, or inputs the presented ticket number using the operation unit 55 of the ticket counter processing machine 5. When the two-dimensional code is held over the ticket information reading unit 56, the ticket information reading unit 56, under the control of the control unit 51, reads the normally-issued two-dimensional code data D12 from the held two-dimensional code (step S51-1).

[0368] When the ticket information reading unit 56 reads the normally issued two-dimensional code data D12 or inputs the ticket number related to the ticket number information D11, the control unit 51 in the counter processing machine 5 transmits the read normally issued two-dimensional code data D12 or the input ticket number information D11 from the communication unit 53 to the ticket issuing server 3 via the communication network N (step S51-2).

[0369] In the ticket issuing server 3, which has received the information transmitted from the counter processing machine 5 via the communication unit 33, the control unit 31 searches the ticket information storage unit 322 of the storage unit 32 based on the normally-issued two-dimensional code data D12 or ticket number information D11, and if ticket purchase information D6 corresponding to the received normally-issued two-dimensional code data D12 or ticket number information D11 is present, extracts the ticket purchase information D6 (step S51-3). Note that when the normally-issued two-dimensional code data D12 is received, the control unit 31 first decodes the encoded information in the basic information unit D12-1 of the normally-issued two-dimensional code data D12 using the general encoded information D13 stored in the encoded information storage unit 323 of the storage unit 32, and then performs a search based on the ticket identifier information D10 included in the decoded information.

[0370] Once the extraction of the ticket purchase information D6 is complete, the control unit 31 in the ticket issuing server 3 temporarily stops updating information about the ticket related to the extracted ticket purchase information D6 (ticket content information D2, ticket purchase information D6, and ticket reservation information D8) and sends a predetermined instruction to fix the stored information from the communication unit 33 to the ticket reservation server 2 via the communication network N in step S51-1, together with the ticket purchase number information D7 related to the ticket if the normally issued two-dimensional code data D12 is read at the counter processing machine 5, or together with the ticket number information D11 related to the ticket if the ticket number information D11 is input at the counter processing machine 5 (step S51-4).

[0371] In the ticket reservation server 2, which receives the instruction sent from the ticket issuing server 3 and the ticket purchase number information D7 or ticket number information D11 via the communication unit 23, the control unit 21 extracts corresponding data from the ticket information storage unit 222 based on the ticket purchase number information D7 or ticket number information D11, and then temporarily stops updating the ticket content information D2, ticket purchase information D6 and ticket reservation information D8 and fixes the stored information, for example, by linking the extracted ticket content information D2, ticket purchase information D6 and ticket reservation information D8 to the extracted ticket content information D2, ticket purchase information D6 and ticket reservation information D8 and storing specified information indicating that the information has been stopped from updating (step S51-5).

[0372] Next, in the ticket issuing server 3, the control unit 31 transmits the ticket purchasing information D6 extracted in step S51-3 from the communication unit 33 via the communication network N to the counter processing machine 5 that transmitted the information in step S51-2 (step S51-6). If the ticket purchasing information D6 extracted in step S51-3 does not exist, a notification to that effect is transmitted to the counter processing machine 5, and the process ends.

[0373] In the counter processing machine 5, which receives the ticket purchase information D6 sent from the ticket issuing server 3 via the communication unit 53, the control unit 51 displays the received ticket purchase information D6 on the display unit 54 (step S51-7). When the ticket purchase information D6 is displayed on the display unit 54 of the ticket counter processing machine 5, the station staff will determine whether the user is permitted to enter or exit based on the displayed information, and will only allow the user to enter or exit if the user holds a ticket that allows entry or exit at the station.

[0374] Specifically, in the case of entry, for example, entry is permitted if the station where the station employee is located is within the validity area of ​​the ticket and there is no history of entry or the employee has already exited at an intermediate station, whereas entry is prohibited if the station where the station employee is located is outside the validity area of ​​the ticket or there is already a history of entry but the employee has not yet exited at an intermediate station. In addition, in the case of exiting, for example, if the station where the station staff member is located is within the valid area of ​​the ticket and after entry but before exiting, it is determined that the station staff member is able to exit, and if the station where the station staff member is located is outside the valid area of ​​the ticket or before entry or after exiting, it is determined that the station staff member is unable to exit.

[0375] If the station staff approves the user's entry or exit, in the counter processing machine 5, in accordance with a predetermined operation performed by the station staff using the operation unit 55, the control unit 51 transmits information regarding the station staff's judgment result on the user's entry or exit (third entry / exit judgment result information D34) together with the ticket purchase information D6 received in step S51-6 from the communication unit 63 via the communication network N to the ticket issuing server 3 (step S51-8).

[0376] In the ticket issuing server 3, when the communication unit 33 receives the information transmitted from the counter processing machine 5, the control unit 31 searches the ticket information storage unit 322 of the storage unit 32 based on the received ticket purchase information D6, and updates the ticket content information D2 corresponding to the received ticket purchase information D6 and the information relating to the ticket status contained in the ticket purchase information D6 based on the third entry / exit judgment result information D34 (step S51-9). Specifically, if entry is permitted, the information regarding the ticket status contained in the ticket content information D2 and ticket purchase information D6 will be set to "ticket in use" (after entry but before exit), and if exit is permitted, the information regarding the ticket status contained in the ticket content information D2 and ticket purchase information D6 will be set to "already used" (after exit at the disembarking station) or "in use" (after exit at an intermediate station).

[0377] Next, the control unit 31 transmits information regarding the updated contents of the ticket status information contained in the ticket content information D2 and the ticket purchase information D6 in step S51-9 (third entry / exit status update information D35) from the communication unit 33 to the ticket reservation server 2 via the communication network N (step S51-10).

[0378] Next, the control unit 31 sends a predetermined instruction to cancel the suspension of information updates in step S51-5 to the ticket reservation server 2 from the communication unit 33 via the communication network N, together with the ticket purchase number information D7 for the ticket if the normally issued two-dimensional code data D12 was read at the counter processing machine 5 in step S51-1, or together with the ticket number information D11 for the ticket if the ticket number information D11 was input at the counter processing machine 5 (step S51-11).

[0379] In the ticket reservation server 2, which receives the instruction sent from the ticket issuing server 3 and the ticket purchase number information D7 or ticket number information D11 via the communication unit 23, the control unit 21 extracts corresponding data from the ticket information storage unit 222 based on the ticket purchase number information D7 or ticket number information D11, and then cancels the suspension of updates to the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 by, for example, deleting specified information that indicates that the information has been suspended from updating and that is linked to the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 and stored in the ticket information storage unit 222 (step S51-12).

[0380] In the ticket reservation server 2, the communication unit 23 receives the third entry / exit status update information D35 in step S51-10, and then the suspension of information updates is lifted in step S51-12.Then, the control unit 21 updates the information related to the ticket status contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 stored in the ticket information memory unit 222 of the memory unit 22 in the same manner as the update in the ticket issuing server 3 in step S51-9 (step S51-13).

[0381] After sending the information to the ticket reservation server 2 in step S51-8, the control unit 31 of the ticket issuing server 3 sends the third entry / exit status update information D35 from the communication unit 33 to the counter processing machine 5 via the communication network N (step S51-14).

[0382] In the ticket counter processing machine 5, which receives the third entry / exit status update information D35 transmitted from the ticket issuing server 3 via the communication unit 53, the control unit 51 displays the received third entry / exit status update information D35 on the display unit 54 (step S51-15). This allows the station staff to check the status update results.

[0383] [Step S52: When using a station staff terminal] Next, the flow of operations when a station staff member uses the station staff terminal 7 will be described with reference to the flowchart of FIG.

[0384] In this case, similarly to step S51, the station attendant confirms the two-dimensional code related to the normally-issued two-dimensional code image data D16 and the ticket number related to the ticket number information D11 presented by the user, and then holds the presented two-dimensional code over the imaging unit 76 of the station attendant terminal 7, or inputs the presented ticket number using the operation unit 75 of the station attendant terminal 7. When the two-dimensional code is held over the imaging unit 76, the control unit 71 reads the normally-issued two-dimensional code data D12 based on the image of the two-dimensional code captured by the imaging unit 76 (step S52-1).

[0385] When the normally issued two-dimensional code data D12 is read or the ticket number related to the ticket number information D11 is input, the control unit 71 of the station attendant terminal 7 transmits the read normally issued two-dimensional code data D12 or the input ticket number information D11 from the communication unit 73 via the communication network N to the ticket reservation server 2 (step S52-2).

[0386] In the ticket reservation server 2, which receives the information transmitted from the station attendant terminal 7 via the communication unit 23, the control unit 21 transmits the received normally issued two-dimensional code data D12 or ticket number information D11 from the communication unit 23 to the ticket issuing server 3 via the communication network N (step S52-3).

[0387] In the ticket issuing server 3 that has received the information transmitted from the ticket reservation server 2 via the communication unit 33, the control unit 31 searches the ticket information storage unit 322 of the storage unit 32 based on the normally-issued two-dimensional code data D12 or ticket number information D11, and if ticket purchase information D6 corresponding to the received normally-issued two-dimensional code data D12 or ticket number information D11 is present, extracts the ticket purchase information D6 (step S52-4). Note that when the normally-issued two-dimensional code data D12 is received, the control unit 31 first decodes the encoded information in the basic information unit D12-1 of the normally-issued two-dimensional code data D12 using the general encoded information D13 stored in the encoded information storage unit 323, and then performs a search based on the ticket identifier information D10 included in the decoded information.

[0388] Once the extraction of the ticket purchasing information D6 is complete, the control unit 31 of the ticket issuing server 3 temporarily stops updating the ticket content information D2 and the ticket purchasing information D6 and fixes the stored information, for example, by linking the extracted ticket purchasing information D6 to information about the ticket (ticket content information D2 and ticket purchasing information D6) in the ticket information storage unit 322 of the storage unit 32 and storing specified information indicating that the information has been stopped from updating (step S52-5).

[0389] Next, in the ticket issuing server 3, the control unit 31 transmits the ticket number information D11 corresponding to the ticket purchasing information D6 extracted in step S52-4 from the communication unit 33 via the communication network N to the ticket reservation server 2 (step S52-6). That is, when the ticket issuing server 3 receives the ticket number information D11 from the ticket reservation server 2 in step S52-3, it checks whether or not the corresponding ticket purchasing information D6 is stored, and then transmits the same data as that received. If the ticket purchase information D6 extracted in step S52-4 does not exist, a notification to that effect is sent to the ticket reservation server 2, which then sends the notification to the station attendant terminal 7 and terminates the processing.

[0390] In the ticket reservation server 2, which receives the ticket number information D11 sent from the ticket issuing server 3 via the communication unit 23, the control unit 21 searches the ticket information storage unit 222 of the storage unit 22 based on the received ticket number information D11 and extracts the ticket reservation information D8 corresponding to the received ticket number information D11 (step S52-7).

[0391] Once the extraction of ticket reservation information D8 is complete, the control unit 21 in the ticket reservation server 2 temporarily stops updating the ticket content information D2, ticket purchase information D6 and ticket reservation information D8 and fixes the stored information, for example, by linking the extracted ticket reservation information D8 with information about the ticket (ticket content information D2, ticket purchase information D6 and ticket reservation information D8) in the ticket information storage unit 222 of the storage unit 22 and storing specified information indicating that the information has been stopped from updating (step S52-8).

[0392] Next, in the ticket reservation server 2, the control unit 21 transmits the ticket reservation information D8 extracted in step S52-7 from the communication unit 23 via the communication network N to the station attendant terminal 7 that transmitted the information in step S52-2 (step S52-9).

[0393] In the station attendant terminal 7 that has received the ticket reservation information D8 transmitted from the ticket reservation server 2 via the communication unit 73, the control unit 71 causes the display unit 74 to display the received ticket reservation information D8 (step S52-10). When the ticket reservation information D8 is displayed on the display unit 74 of the station attendant terminal 7, the station attendant will determine whether the user is permitted to enter or exit based on the displayed information, and will only allow the user to enter or exit if the user holds a ticket that allows entry or exit at the station.

[0394] Specifically, in the case of entry, for example, entry is permitted if the station where the station employee is located is within the validity area of ​​the ticket and there is no history of entry or the employee has already exited at an intermediate station, whereas entry is prohibited if the station where the station employee is located is outside the validity area of ​​the ticket or there is already a history of entry but the employee has not yet exited at an intermediate station. In addition, in the case of exiting, for example, if the station where the station staff member is located is within the valid area of ​​the ticket and after entry but before exiting, it is determined that the station staff member is able to exit, and if the station where the station staff member is located is outside the valid area of ​​the ticket or before entry or after exiting, it is determined that the station staff member is unable to exit.

[0395] If the station staff approves the user's entry or exit, in accordance with a predetermined operation performed by the station staff using the operation unit 75, the control unit 71 of the station staff terminal 7 transmits information regarding the station staff's judgment result regarding the user's entry or exit (fourth entry / exit judgment result information D36) together with the ticket reservation information D8 received in step S52-9 from the communication unit 73 via the communication network N to the ticket reservation server 2 (step S52-11).

[0396] In the ticket reservation server 2, when the communication unit 23 receives the information transmitted from the station attendant terminal 7, the control unit 21 transmits the received fourth entry / exit judgment result information D36, together with the ticket purchase number information D7 contained in the ticket purchase information D6 corresponding to the received ticket reservation information D8, from the communication unit 23 via the communication network N to the ticket issuing server 3 (step S52-12).

[0397] In the ticket issuing server 3, when the communication unit 33 receives the information transmitted from the ticket reservation server 2, the control unit 31 cancels the suspension of updates of the ticket content information D2 and the ticket purchasing information D6, for example, by deleting specified information indicating that the information has been suspended from the ticket information storage unit 322 of the storage unit 32 in association with the ticket content information D2 and ticket purchasing information D6 whose updating has been suspended (step S52-13).

[0398] Next, the control unit 31 searches the ticket information storage unit 322 of the storage unit 32 based on the ticket purchase information D6 received in step S52-12, and updates the ticket content information D2 corresponding to the received ticket purchase information D6 and the information related to the ticket status included in the ticket purchase information D6 based on the fourth entry / exit judgment result information D36 (step S52-14). Specifically, if entry is permitted, the information regarding the ticket status contained in the ticket content information D2 and ticket purchase information D6 will be set to "ticket in use" (after entry but before exit), and if exit is permitted, the information regarding the ticket status contained in the ticket content information D2 and ticket purchase information D6 will be set to "already used" (after exit at the disembarking station) or "in use" (after exit at an intermediate station).

[0399] Next, the control unit 31 transmits information regarding the update content of the ticket status information included in the ticket content information D2 and the ticket purchase information D6 in step S52-14 (fourth entry / exit status update information D37) from the communication unit 33 to the ticket reservation server 2 via the communication network N (step S52-15).

[0400] In the ticket reservation server 2, when the communication unit 23 receives the fourth entry / exit status update information D37, the control unit 21 cancels the suspension of updates of the ticket content information D2, ticket purchase information D6 and ticket reservation information D8, for example, by deleting specified information indicating that the information for which updates have been suspended, which is stored in the ticket information storage unit 222 of the storage unit 22 in association with the ticket content information D2, ticket purchase information D6 and ticket reservation information D8 for which updates have been suspended (step S52-16).

[0401] Next, the control unit 21 updates the information related to the ticket status contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 stored in the ticket information memory unit 222 of the memory unit 22 in the same manner as the update in the ticket issuing server 3 in step S52-14 (step S52-17).

[0402] Next, the control unit 21 of the ticket reservation server 2 transmits the fourth entry / exit status update information D37 received from the ticket issuing server 3 from the communication unit 23 to the station staff terminal 7 via the communication network N (step S52-18).

[0403] In the station staff terminal 7, which has received the fourth entry / exit status update information D37 transmitted from the ticket reservation server 2 via the communication unit 73, the control unit 71 displays the received fourth entry / exit status update information D37 on the display unit 74 (step S52-19). This allows the station staff to check the status update results.

[0404] [(2) Effects of this step] According to the ticket information processing system 100 of this embodiment, the following effects can be obtained by performing the above-described ticket gate entry and exit.

[0405] As explained in step S2, when a ticket for boarding a train is issued using a two-dimensional code related to the normally issued two-dimensional code data D12, whether it is issued to a user terminal 8 or by a ticket issuing device 6, it is impossible for a station attendant to read the contents of the ticket even if they visually inspect the issued ticket. Therefore, for example, in cases where the automatic ticket gates at a station where station staff are present are unable to operate due to some kind of trouble, or in cases where station staff are present but no automatic ticket gates are installed, even if the station staff visually check the ticket, they will not be able to determine whether the ticket holder can enter or exit the ticket gate and then allow the ticket holder to pass, as is the case with conventional magnetic card tickets, which have information about the ticket contents such as the boarding and disembarking stations printed on the ticket.

[0406] In this regard, according to this embodiment, the counter processing machine 5 or the station attendant terminal 7 acquires the normally issued two-dimensional code data D12 or ticket number information D11 including the ticket identifier information D10 and transmits this to the ticket reservation server 2 or the ticket issuing server 3. The ticket reservation server 2 or the ticket issuing server 3 receives this information and transmits ticket purchase information D6 or ticket reservation information D8 including information on the contents of the ticket corresponding to the received information to the counter processing machine 5 or the station attendant terminal 7.

[0407] This enables station staff using the counter processing machine 5 or the station staff terminal 7 to use the ticket purchase information D6 or ticket reservation information D8 to determine whether a user holding a ticket issued using a two-dimensional code related to the normally issued two-dimensional code data D12 can enter or exit the ticket gate. Furthermore, the decision as to whether a user can enter or exit the ticket gate is made by the station staff themselves, as in the conventional operation when automatic ticket gates are not available and station staff visually check tickets, so there is no need for the counter processing machine 5 or station staff terminal 7 to be able to determine whether a user can enter or exit the ticket gate, and no significant increase in costs will be incurred.

[0408] Furthermore, with conventional magnetic card tickets, when a station attendant determines whether or not a ticket holder can enter or exit the ticket gate without passing through an automatic ticket gate, the ticket holder is allowed to enter or exit the ticket gate, and a history of entry and exit is recorded on the ticket itself by stamping a specified stamp or cutting a notch in the ticket, thereby preventing the ticket from being used again. However, this type of processing is not possible with tickets issued using a two-dimensional code related to the normally issued two-dimensional code data D12. In other words, if the ticket is issued as data to the user terminal 8, it is not possible to perform processes such as stamping or cutting. Also, if the ticket is issued on a specified medium such as paper by the ticket issuing device 6, it is possible to perform processes such as stamping or cutting on the printed ticket, but since such two-dimensional codes can be duplicated any number of times, it is meaningless to perform such processes on a single printed ticket.

[0409] In this regard, according to this embodiment, the ticket reservation server 2 and the ticket issuing server 3 acquire the third entry / exit judgment result information D34 or the fourth entry / exit judgment result information D36, which is information relating to the results of the station staff's judgment on the user's entry / exit, and then update the information relating to the ticket status contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 accordingly. As a result, when the ticket reservation server 2 or the ticket issuing server 3 processes entry and exit from the ticket gate, it checks the ticket content information D2 corresponding to the received normally issued two-dimensional code data D12 and ticket number information D11, ticket purchase information D6, and ticket reservation information D8 regarding the ticket status, thereby making it possible to prevent tickets from being used again even for users who entered or exited without going through the ticket gate device 4.

[0410] [6 Step S6: Entering and exiting ticket gates when communication is disrupted] Next, the operation of the system when a communication failure of some kind prevents communication between the ticket gate device 4 and the ticket issuing server 3 when a user uses the two-dimensional code issued in step S1 to enter or exit the ticket gate through the ticket gate device 4 will be described with reference to the flowchart in Figure 23. Note that in this embodiment, "communication failure" is not limited to a failure in the communication line, but broadly includes a case in which the ticket gate device 4 is unable to obtain information from the ticket issuing server 3, and also includes a case in which a server failure occurs in the ticket issuing server 3. In addition, whether the entry / exit determination described in step S21 is performed by the ticket issuing server 3 or the entry / exit determination described in step S22 is performed by the ticket gate device 4, the fact remains that regular entry / exit processing cannot be performed without communication between the ticket gate device 4 and the ticket issuing server 3, so the following processing is the same in either case.

[0411] [(1) Operational flow] When the user holds the two-dimensional code issued in step S1, that is, the two-dimensional code related to the normally-issued two-dimensional code image data D16 issued to the user terminal 8 in step S11 or the two-dimensional code issued on a predetermined medium such as paper by the ticket issuing device 6 in step S12, over the ticket information reading unit 44 of the ticket gate device 4, the control unit 41 causes the ticket information reading unit 44 to read the normally-issued two-dimensional code data D12 (step S6-1), determines whether the held two-dimensional code is a legitimate ticket (step S6-2), and if it determines that it is a legitimate ticket, transmits the normally-issued two-dimensional code data D12, together with ticket gate device installation station information D18 and ticket gate device information D19, from the communication unit 43 via the communication network N to the ticket issuing server 3 (step S6-3). Up to this point, the process is the same as steps S21-1 to S21-3 in step S21 and S22-1 to S22-3 in step S22.

[0412] After the data is sent in step S6-3, the control unit 41 acquires information regarding the elapsed time since the data was sent in step S6-3 by a predetermined method, such as counting it itself, and if there is no response from the ticket issuing server 3 after a predetermined time (for example, 1 second) has elapsed (if the entry / exit determination is made in the ticket issuing server 3 described in step S21, the first entry / exit determination result information D20 cannot be received, or if the entry / exit determination is made in the ticket gate device 4 described in step S22, the ticket content information D2 cannot be received), the control unit 41 again sends the same information as in step S6-3 from the communication unit 43 to the ticket issuing server 3 via the communication network N (step S6-4).

[0413] If there is no response from the ticket issuing server 3 after a predetermined time (e.g., 1 second) has elapsed after the data is sent in step S6-4, the control unit 41 links the normally issued two-dimensional code data D12 read by the ticket information reading unit 44 in step S6-1 to communication failure entry / exit date and time information D38, which is information relating to the date and time at that time, communication failure entry / exit station information D39, which is data relating to the station where the ticket gate device 4 is installed, and communication failure entry / exit processing flag D40, which is data relating to a predetermined flag indicating that the normally issued two-dimensional code data D12 was entered or exited without going through a judgment regarding whether entry or exit is possible, and stores it in the communication failure ticket information memory unit 425 of the memory unit 42 (step S6-5).

[0414] When the storage process is completed, the control unit 41 opens the opening / closing unit 45 and allows the user to enter or exit (step S6-6). In the ticket gate device 4 that is set so that the opening / closing unit 45 is closed when the opening / closing unit 45 is originally in the open state and a user attempts to pass through without holding a ticket over the ticket information reading unit 44, or when the held ticket does not allow the user to enter or exit, the opening / closing unit 45 is not closed but is maintained in the open state, thereby allowing the user to enter or exit. As described above, such a case also corresponds to the case where the opening / closing unit 45 is set to the open state.

[0415] [(2) Effects of this step] According to the ticket information processing system 100 of this embodiment, the following effects can be obtained by allowing entrance and exit through the ticket gate even when a communication failure occurs as described above.

[0416] In other words, as explained in step S2, in this embodiment, whether the determination as to whether a user can enter or exit is made by the ticket issuing server 3 or by the ticket gate device 4, ticket content information D2 must be obtained from the ticket issuing server 3. Therefore, in either case, if a communication failure occurs between the ticket gate device 4 and the ticket issuing server 3, it will be impossible to determine whether a user attempting to enter or exit through the ticket gate device 4 can enter or exit. However, if the user is forced to wait in front of the ticket gate device 4 until the communication failure is resolved in such a case, the user will have to wait for a long time, and the station will become overcrowded with people.

[0417] In this regard, according to the ticket information processing system 100 of this embodiment, if there is no response from the ticket issuing server 3 due to a communication failure, the ticket gate device 4 automatically opens the opening / closing section 45 to allow the user to pass through, thereby preventing the above-mentioned situation from occurring.

[0418] In this case, since the user is simply allowed to enter without going through the determination as to whether or not they can enter and exit normally as explained in step S2, it becomes possible for the user to, for example, enter from a station other than their original entry station or exit from a station other than their original exit station. However, since the user is usually unaware of the occurrence of a communication failure between the ticket gate device 4 and the ticket issuing server 3, it is usually not possible for the user to intentionally enter or exit the facility in an unauthorized manner as described above. Furthermore, in step S6-2, it is confirmed whether the ticket is a legitimate ticket, so that entry or exit using an unauthorized ticket such as a counterfeit ticket can at least be prevented. Therefore, although the risks mentioned above are not zero, they are negligible for railway operators.

[0419] Furthermore, after the information is sent from the ticket gate device 4 to the ticket issuing server 3, the information is resent to the ticket issuing server 3 when a predetermined time has elapsed, and the opening / closing section 45 is opened when a predetermined time has elapsed since the resending. As the processing is carried out mechanically over time, it is possible to quickly let the user through with simple processing, and since the ticket gate device 4 only determines that a communication failure has occurred and lets the user through if there is no response after sending the information twice, the risk of the ticket gate device 4 making an erroneous judgment about the occurrence of a communication failure is reduced.

[0420] Furthermore, when the ticket gate device 4 allows a user to pass through with the opening / closing section 45 in the open state without determining whether entry or exit is possible, the two-dimensional code data D12 issued under normal circumstances is stored in the communication failure ticket information storage section 425 of the memory unit 42 in association with communication failure entry / exit date and time information D38, communication failure entry / exit station information D39, and communication failure entry / exit processing flag D40, making it possible to update information related to the ticket status after the communication failure is restored in step S7, as described below.

[0421] [7 Step S7: Processing after communication failure recovery] Next, in step S6, if a user is allowed to enter or exit without going through a judgment regarding whether or not they can enter or exit due to a communication failure, the operation of this system after the communication failure is restored will be explained separately for when the judgment regarding whether or not they can enter or exit is made by the ticket issuing server 3 as described in step S21, and when it is made by the ticket gate device 4 as described in step S22.

[0422] [(1) Operational flow] [A Step S71: When entry / exit determination is made on the ticket issuing server] First, the flow of operations when the ticket issuing server 3 performs entry / exit determination will be described with reference to the flowchart in FIG.

[0423] In the ticket gate device 4, after the communication failure with the ticket issuing server 3 is restored, the control unit 41 detects the restoration of the communication failure by a predetermined method (step S71-1). Although the specific method is not limited, for example, during a communication failure, the control unit 41 may continue to send a predetermined signal requesting a response from the ticket issuing server 3 from the communication unit 43 via the communication network N to the ticket issuing server 3, and determine that communication has been restored when a response is received to the signal. Alternatively, without taking any special measures, it may be determined that communication has been restored when a response is received when transmitting the normally-issued two-dimensional code data D12, etc. in step S6-3 in response to the two-dimensional code held up by the user.

[0424] When the control unit 41 of the ticket gate device 4 becomes aware of the recovery of the communication failure, it transmits the two-dimensional code data D12 issued under normal circumstances, the communication failure entry / exit date and time information D38, the communication failure entry / exit station information D39, and the communication failure entry / exit processing flag D40, which were stored in the communication failure ticket information storage unit 425 of the storage unit 42 during the occurrence of the communication failure (from the time when data was last received from the ticket issuing server 3 before the communication failure occurred until the recovery of the communication failure), together with the ticket gate device equipment information D19 stored in the equipment information storage unit 423, from the communication unit 43 via the communication network N to the ticket issuing server 3 (step S71-2).

[0425] In the ticket issuing server 3 that receives the information transmitted from the ticket gate device 4 via the communication unit 33, the control unit 31 determines, based on the ticket gate device equipment information D19, whether the ticket gate device 4 is a ticket gate device 4 that requires entry / exit determination by the ticket issuing server 3. If entry / exit determination by the ticket issuing server 3 is required, the control unit 31 first decodes the encoded information in the basic information section D12-1 of the normally issued two-dimensional code data D12 using the general encoding information D13 stored in the encoding information memory unit 323 of the memory unit 32 (step S71-3).

[0426] Next, the control unit 31 searches the ticket information storage unit 322 of the storage unit 32 based on the ticket identifier information D10 included in the decrypted information, extracts the ticket content information D2 and ticket purchase information D6 corresponding to the received normally-issued two-dimensional code data D12, and then compares the received communication failure entry / exit date and time information D38, communication failure entry / exit station information D39, and communication failure entry / exit processing flag D40 with the ticket content information D2 to determine whether entry or exit is permitted (step S71-4). Note that if the ticket content information D2 and ticket purchase information D6 corresponding to the received normally-issued two-dimensional code data D12 are not extracted, the control unit 31 ends the process without determining whether entry or exit is permitted.

[0427] Specifically, in the case of entry, for example, the entry history and exit history are checked from the information related to the ticket status contained in the ticket content information D2 and the ticket purchase information D6, and if there is no entry history or the entry history is after exiting at an intermediate station, and further if the entry station related to the communication failure entry / exit station information D39 is a station within the validity section related to the ticket content information D2, and the entry date and time related to the communication failure entry / exit date and time information D38 is within the validity period related to the ticket content information D2, it is determined that the user was eligible to enter, and if any one of these conditions is not met, it is determined that the user was not eligible to enter.

[0428] In addition, in the case of exit, for example, the entry history and exit history are checked from information related to the ticket status contained in the ticket content information D2 and ticket purchase information D6, and if the time is after entry but before exit, and if the exit station related to the communication failure entry / exit station information D39 is a station within the validity zone related to the ticket content information D2, and the exit date and time related to the communication failure entry / exit date and time information D38 is within the validity period related to the ticket content information D2, the user is determined to be eligible to exit, and if any one of these conditions is not met, the user is determined to be incapable of exiting.

[0429] When the above determination is completed, the control unit 31 updates the information relating to the status of the ticket, which is included in the ticket content information D2 and the ticket purchase information D6 stored in the ticket information storage unit 322 of the storage unit 32 (step S71-5). Specifically, if the user is eligible to enter, the information regarding the ticket status contained in the ticket content information D2 and ticket purchase information D6 will be set to "ticket in use" (after entry, before exit), and if the user is eligible to exit, the information regarding the ticket status contained in the ticket content information D2 and ticket purchase information D6 will be set to "already used" (after exit at the disembarking station) or "in use" (after exit at an intermediate station). If a user is unable to exit or enter the venue, the status information will not be updated.

[0430] Once the above update is complete, the control unit 31 transmits information regarding the updated contents of the ticket status information included in the ticket content information D2 and ticket purchase information D6 in step S71-5 (status update information D41 at the time of entry and exit due to the first communication failure) from the communication unit 33 to the ticket reservation server 2 via the communication network N (step S71-6).

[0431] In the ticket reservation server 2, when the communication unit 23 receives the status update information D41 at the time of entry and exit due to the first communication failure, the control unit 21 updates the information related to the ticket status contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 stored in the ticket information memory unit 222 of the memory unit 22 in the same manner as the update in the ticket issuing server 3 in step S71-5 (step S71-7).

[0432] In addition, if there are multiple sets of normally issued two-dimensional code data D12, communication failure entry / exit date and time information D38, communication failure entry / exit station information D39, and communication failure entry / exit processing flag D40 stored in the communication failure ticket information storage unit 425 of the storage unit 42 during a communication failure (from the time when data was last received from the ticket issuing server 3 before the communication failure occurred until the communication failure is restored), the processing from steps S71-2 to S71-7 will be repeated for the number of stored sets.

[0433] [Step S72: When entry / exit determination is performed at the ticket gate device] Next, the flow of operations when the ticket gate device 4 determines whether a passenger is entering or exiting will be described with reference to the flowchart in FIG.

[0434] In the ticket gate device 4, after the communication failure with the ticket issuing server 3 is restored, the recovery of the communication failure is detected by a predetermined method (step S72-1). When the recovery of the communication failure is detected, the control unit 41 transmits the two-dimensional code data D12 issued under normal circumstances, the communication failure entry / exit date and time information D38, the communication failure entry / exit station information D39, and the communication failure entry / exit processing flag D40, which were stored in the communication failure ticket information storage unit 425 of the storage unit 42 during the occurrence of the communication failure (from the time when the last data was received from the ticket issuing server 3 before the communication failure occurred until the recovery of the communication failure), together with the ticket gate device equipment information D19 stored in the equipment information storage unit 423, from the communication unit 43 via the communication network N to the ticket issuing server 3 (step S72-2). Up to this point, the process is the same as when the entry / exit determination is made in the ticket issuing server 3.

[0435] In the ticket issuing server 3, which receives the information transmitted from the ticket gate device 4 via the communication unit 33, the control unit 31 determines, based on the ticket gate device equipment information D19, whether the ticket gate device 4 is the ticket gate device 4 that performs entry / exit determination at the ticket gate device 4.If entry / exit determination is to be performed at the ticket gate device 4, the control unit 31 first decodes the encoded information in the basic information section D12-1 of the normally issued two-dimensional code data D12 using the general encoding information D13 stored in the encoding information memory unit 323 of the memory unit 32 (step S72-3).

[0436] Next, the control unit 31 searches the ticket information storage unit 322 based on the ticket identifier information D10 contained in the decrypted information, extracts the ticket content information D2 and ticket purchase information D6 corresponding to the received normally issued two-dimensional code data D12, and transmits the extracted ticket content information D2 to the ticket gate device 4 that transmitted the information in step S72-2 (step S72-4).

[0437] In addition, if the ticket content information D2 and ticket purchase information D6 corresponding to the received normally issued two-dimensional code data D12 are not extracted, the control unit 31 will terminate the processing without sending the ticket content information D2 to the ticket gate device 4.

[0438] In the ticket gate device 4 that has received the ticket content information D2 via the communication unit 43, the control unit 41 determines whether entry or exit is permitted based on the received ticket content information D2 (step S72-5). The logic for this determination may be to compare the ticket content information D2 with the communication failure entry / exit date and time information D38, the communication failure entry / exit station information D39, and the communication failure entry / exit processing flag D40.

[0439] Specifically, for example, just as when the ticket issuing server 3 determines whether entry or exit is possible, in the case of entry, it is determined that entry is possible if the information related to the ticket status included in the ticket content information D2 shows that there is no entry history or that the ticket has already exited at an intermediate station, the entry station related to the communication failure entry / exit station information D39 is a station within the validity period related to the ticket content information D2, and the entry date and time related to the communication failure entry / exit date and time information D38 is within the validity period related to the ticket content information D2; in the case of exit, it is determined that exit is possible if the information related to the ticket status included in the ticket content information D2 shows that the ticket has already entered but not yet exited, the exit station related to the communication failure entry / exit station information D39 is a station within the validity period related to the ticket content information D2, and the exit date and time related to the communication failure entry / exit date and time information D38 is within the validity period related to the ticket content information D2.

[0440] Next, in the ticket gate device 4, the control unit 41 transmits information relating to the ticket gate entry / exit determination result in step S72-5 (communication failure entry / exit determination result information D42) together with the ticket content information D2 received in step S72-4 from the communication unit 43 via the communication network N to the ticket issuing server 3 (step S72-6).

[0441] In the ticket issuing server 3 that receives the information transmitted from the ticket gate device 4, the control unit 31 updates the information relating to the ticket status contained in the ticket content information D2 and ticket purchase information D6 stored in the ticket information memory unit 322 of the memory unit 32 (step S72-7). Specifically, if the user is eligible to enter, the information regarding the ticket status contained in the ticket content information D2 and ticket purchase information D6 will be set to "ticket in use" (after entry, before exit), and if the user is eligible to exit, the information regarding the ticket status contained in the ticket content information D2 and ticket purchase information D6 will be set to "already used" (after exit at the disembarking station) or "in use" (after exit at an intermediate station). If the user is unable to exit or enter the venue, the data will not be updated.

[0442] Once the above update is complete, the control unit 31 transmits information regarding the updated contents of the ticket status information included in the ticket content information D2 and ticket purchase information D6 in step S72-7 (status update information D43 at the time of entry and exit due to second communication failure) from the communication unit 33 to the ticket reservation server 2 via the communication network N (step S72-8).

[0443] In the ticket reservation server 2, when the communication unit 23 receives the status update information D43 at the time of entry and exit due to the second communication failure, the control unit 21 updates the information related to the ticket status contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 stored in the ticket information memory unit 222 of the memory unit 22 in the same manner as the update in the ticket issuing server 3 in step S72-7 (step S72-9).

[0444] In addition, if there are multiple sets of normally issued two-dimensional code data D12, communication failure entry / exit date and time information D38, communication failure entry / exit station information D39, and communication failure entry / exit processing flag D40 stored in the communication failure ticket information storage unit 425 of the storage unit 42 during a communication failure (from the time when data was last received from the ticket issuing server 3 before the communication failure occurred until the communication failure is restored), the processing from steps S72-2 to S72-10 will be repeated for the number of stored sets.

[0445] [(2) Effects of this step] According to the ticket information processing system 100 of this embodiment, the following effects can be obtained by determining whether entry and exit are possible and updating information related to ticket status after the communication failure is restored as described above.

[0446] In other words, as explained in step S2, when the decision as to whether a user can enter or exit is made by the ticket issuing server 3, and even when it is made by the ticket gate device 4, the recording of the entry and exit history using a ticket (updating of information related to the ticket status contained in the ticket content information D2, ticket purchase information D6 and ticket reservation information D8 according to the entry and exit history) is done on the server side (ticket reservation server 2 and ticket issuing server 3), so if a communication failure occurs between the ticket gate device 4 and the ticket issuing server 3, it will not be possible to record the entry and exit history using a ticket.

[0447] However, such a situation is undesirable because, for example, if the entry history is not recorded even though the ticket was used for entry (if the information relating to the ticket status contained in the ticket content information D2, ticket purchase information D6 and ticket reservation information D8 does not indicate that the ticket is in use (after entry but before exit)), the user may be stopped at the ticket gate device 4 when exiting, and there is also the possibility that if a ticket is used but no entry / exit history is recorded due to a communication failure, the user may misuse such a ticket (by reusing or refunding a used ticket, etc.).

[0448] In this regard, according to this embodiment, information such as the normally issued two-dimensional code data D12 relating to tickets used by users who entered or exited during a communication failure is stored in the ticket information storage unit 425 during communication failure in the memory unit 42 of the ticket gate device 4, and after the communication failure is restored, the information is sent to the ticket issuing server 3, and the ticket issuing server 3 and ticket reservation server 2 can update the information relating to the ticket status contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8.

[0449] This means that, for example, if a user enters during a communication failure between the ticket gate device 4 and the ticket issuing server 3, and the communication failure is restored before the user exits, the information relating to the ticket status contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 can be updated to show that the ticket is in use (after entry and before exiting), thereby preventing the user from being stopped by the ticket gate device 4 as having no entry history, except in cases where the communication failure is prolonged and has not been restored even at the time of exiting.

[0450] Furthermore, even if a communication failure results in a ticket whose history is not recorded at the time of entry or exit, once the communication failure is restored, the information relating to the ticket status contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 can be updated to show that the ticket has already been used (after exiting), which prevents used tickets from being misused in the form of reuse or refund, etc., except in cases where the ticket was reused or refunded before the communication failure was restored.

[0451] [8 Step S8: Issuing a ticket at the ticket issuing device when a communication failure occurs] Next, we will explain the operation of this system in the case where a user wishes to have a ticket issued using a two-dimensional code on the ticket issuing device 6, but communication between the ticket issuing device 6 and the ticket issuing server 3 is impossible due to some kind of communication failure, using the flowchart in Figure 26.

[0452] [(1) Operational flow] When a user wishes to purchase a ticket for boarding a train using the ticket issuing device 6, the user first uses the operation unit 65 of the ticket issuing device 6 to input information about the ticket they wish to reserve, i.e., the ticket purchase information D1, which includes information about the train's boarding station, disembarking station, departure time, arrival time, seat number, etc., and then performs the required purchase operation (step S8-1).

[0453] When the desired ticket purchase information D1 is input, the control unit 61 generates ticket purchase information D6 based on the input information (step S8-2), and transmits the generated ticket purchase information D6 from the communication unit 63 to the ticket issuing server 3 via the communication network N (step S8-3). Up to this point, the process is the same as steps S12-1 to S12-3 in step S12.

[0454] After transmitting the data in step S8-3, the control unit 61 acquires information regarding the elapsed time since transmitting the data in step S8-3 by a predetermined method such as counting it itself, and if there is no response from the ticket issuing server 3 after a predetermined time (for example, 1 second) has elapsed (if the normally issued two-dimensional code data D12, etc. cannot be received), the control unit 61 again transmits the same information as in step S8-3 from the communication unit 63 to the ticket issuing server 3 via the communication network N (step S8-4).

[0455] If there is no response from the ticket issuing server 3 after a predetermined time (for example, one second) has elapsed since the data was sent in step S8-4, the control unit 61 issues a ticket issued in case of a failure.

[0456] That is, the control unit 61 first generates two-dimensional code data D44 to be issued in the event of a failure, based on the ticket purchase information D6, in accordance with a predetermined two-dimensional code format such as a format related to QR Code (registered trademark) (step S8-5).

[0457] The two-dimensional code data D44 issued during a communication failure is the source data of a two-dimensional code created according to a predetermined two-dimensional code format, similar to the two-dimensiona...

Claims

1. The computer of the server device, a first acquisition means for acquiring ticket content information, which is information relating to the content of a ticket used to board a train; a first storage control means for storing the ticket content information in a storage means; an identification information assigning means for assigning identification information to each of the ticket content information stored in the storage means; functioning as a code data generating means for generating code data which is data relating to a one-dimensional or two-dimensional code including the identification information; When multiple tickets are input when inputting the ticket purchase information, the first acquisition means acquires multiple pieces of ticket content information corresponding to the multiple tickets, the first storage control means causes the storage means to store the plurality of pieces of ticket content information acquired by the first acquisition means; the identification information assigning means assigns the common identification information to the plurality of pieces of ticket content information; the code data generating means generates a single code data. An information processing program characterized by:

2. The computer of the server device, a first acquisition means for acquiring ticket content information, which is information relating to the content of a ticket used to board a train; a first storage control means for storing the ticket content information in a storage means; an identification information assigning means for assigning identification information to each of the ticket content information stored in the storage means; a code data generating means for generating code data which is data relating to a one-dimensional or two-dimensional code including the identification information; a fourth acquisition means for further acquiring identification information assigned to the ticket content information desired to be linked with second ticket content information, which is information relating to the content of the additionally purchased ticket to be used for boarding the train; a fifth storage control means for causing the storage means to store the second ticket content information acquired by the fourth acquisition means; a second identification information assigning means for assigning the identification information acquired by the fourth acquisition means to the second ticket content information acquired by the fourth acquisition means; An information processing program characterized by causing the program to function as:

3. The code data has a plurality of storage areas, 3. The information processing program according to claim 1, wherein one memory area contains test information, which is information relating to the results of a predetermined conversion or calculation based on information contained in another memory area.

4. a second acquisition means for acquiring available time information which is information relating to an available time of the one-dimensional or two-dimensional code related to the code data; a second storage control means for storing the available time information in a storage means in association with the identification information; 4. The information processing program according to claim 1, wherein the information processing program functions as:

5. The computer a third storage control means for storing, in the storage means, information on the number of tickets issued, which is information on the number of tickets issued, in association with the identification information, if the ticket is a specific group ticket; 5. The information processing program according to claim 1, further functioning as:

6. The identification information relating to all tickets of the specific group ticket is common, 6. The information processing program according to claim 5, wherein the issued number information is information relating to the number of issued tickets including the common identification information.

7. The identification information relating to the specific group ticket is separate for each ticket, the third storage control means stores group identification information, which is information indicating that the ticket including the identification information is a ticket included in a specific group ticket, in the storage means in association with the identification information; 6. The information processing program according to claim 5, wherein the information on the number of issues is information relating to the number of identification information items stored in association with the common organization-specific information.

8. The computer a third acquisition means for acquiring coupon information, which is information relating to the content of a coupon for receiving a benefit at a predetermined facility; a fourth storage control means for storing the coupon information in the storage means in association with the identification information; 8. The information processing program according to claim 1, further functioning as:

9. An information processing method using a server device, a first acquisition step of acquiring ticket content information, which is information relating to the content of a ticket used to board a train; a first storage control step of storing the ticket content information in a storage means; an identification information assigning step of assigning identification information to each of the ticket content information stored in the storage means; a code data creation step of creating code data that is data relating to a one-dimensional or two-dimensional code including the identification information; When multiple tickets are input when inputting the ticket purchase information, the first acquisition step acquires multiple pieces of ticket content information corresponding to the multiple tickets, the first storage control step stores the plurality of pieces of ticket content information acquired in the first acquisition step in the storage means; the identification information assigning step assigns the common identification information to the plurality of pieces of ticket content information; the code data generating step generates a single code data.

1. An information processing method comprising:

10. An information processing method using a server device, an acquisition step of acquiring ticket content information, which is information relating to the content of a ticket used for boarding a train; a storage control step of storing the ticket content information in a storage means; an identification information assigning step of assigning identification information to each of the ticket content information stored in the storage means; a code data creation step of creating code data that is data relating to a one-dimensional or two-dimensional code including the identification information; a fourth acquisition step of further acquiring identification information assigned to the ticket content information desired to be linked with second ticket content information, which is information relating to the content of the additional ticket purchased and used for boarding the train; a fifth storage control step of storing the second ticket content information acquired in the fourth acquisition step in the storage means; a second identification information assigning step of assigning the identification information acquired in the fourth acquisition step to the second ticket content information acquired in the fourth acquisition step; An information processing method comprising:

11. a first acquisition means for acquiring ticket content information, which is information relating to the content of a ticket used to board a train; a first storage control means for storing the ticket content information in a storage means; an identification information assigning means for assigning identification information to each of the ticket content information stored in the storage means; a code data creating means for creating code data which is data relating to a one-dimensional or two-dimensional code including the identification information, When multiple tickets are input when inputting the ticket purchase information, the first acquisition means acquires multiple pieces of ticket content information corresponding to the multiple tickets, the first storage control means causes the storage means to store the plurality of pieces of ticket content information acquired by the first acquisition means; the identification information assigning means assigns the common identification information to the plurality of pieces of ticket content information; the code data generating means generates a single code data. A server device characterized by:

12. an acquisition means for acquiring ticket content information, which is information relating to the content of a ticket used for boarding a train; a storage control means for storing the ticket content information in a storage means; an identification information assigning means for assigning identification information to each of the ticket content information stored in the storage means; a code data generating means for generating code data which is data relating to a one-dimensional or two-dimensional code including the identification information; a fourth acquisition means for further acquiring identification information attached to the ticket content information desired to be linked with second ticket content information, which is information relating to the content of the additionally purchased ticket to be used for boarding the train; a fifth storage control means for causing the storage means to store the second ticket content information acquired by the fourth acquisition means; a second identification information assigning means for assigning the identification information acquired by the fourth acquisition means to the second ticket content information acquired by the fourth acquisition means; A server device comprising:

Images