Refund object discrimination device, refund object discrimination system, refund object discrimination program, and refund object discrimination method

Abstract

To allow for determining whether a ticket for use in getting on a train, which is held by a passenger having left a station, is a refund object or not even if the ticket was issued by using means for which rewriting stored contents and printing on a ticket surface are difficult in a ticket examination device.SOLUTION: A refund object determination device comprises first acquisition means (communication unit 133) for acquiring two-dimensional code data D13 read by a ticket examination device 150 and determination means (control unit 131) for determining whether a refund to a user of a ticket from which the two-dimensional code data D13 is acquired is necessary or not.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a refund object determination device, a refund object determination system, a refund object determination program, and a refund object determination method. [Background technology]

[0002] In recent years, technology has been developed to issue train tickets, which were previously issued using magnetic cards, using a specified 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 IC card tickets, which have become increasingly common in recent years, such one- or two-dimensional codes can be issued without the use of a dedicated card, for example by displaying it on a smartphone, tablet device, etc., or by printing it on ordinary paper, making it possible to issue tickets to users to use for boarding trains cheaply and easily. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2006-59249 A [Patent Document 2] Patent No. 5380338 Summary of the Invention [Problem to be solved by the invention]

[0004] Railway operators sometimes operate express trains that require a special fare in addition to the regular fare to board. In the case of such express trains, if there is a delay of more than a certain amount of time, for example two hours, passengers may be refunded this special fare (and sometimes the regular fare as well).

[0005] In contrast, with conventional magnetic card tickets, when a ticket required to board such an express train is inserted into a ticket gate device, information indicating that the ticket is eligible for a refund is encoded into the magnetic information stored on the ticket, and a notice indicating that the ticket is eligible for a refund is printed on the face of the ticket before it is returned to the passenger.This makes it possible for station counters, etc. to determine whether a passenger who has brought such a ticket is eligible for a refund and to carry out the refund process.

[0006] In contrast, tickets issued using a specified one-dimensional or two-dimensional code can usually be passed through the ticket gate simply by holding the code over a reader installed in the ticket gate device, and it is therefore impossible to rewrite the contents stored in the code at the ticket gate device or print it on the face of the ticket. Therefore, it was not possible to determine whether a ticket held by a passenger after exiting the ticket gate device was eligible for a refund, making it difficult to process refunds for passengers after they had exited the ticket gate device.

[0007] The objective of the present invention is to provide a refund eligibility determination device, a refund eligibility determination system, a refund eligibility determination program, and a refund eligibility determination method that are capable of determining whether a ticket held by a passenger after exiting a train is eligible for a refund, even when tickets used to board a train are issued using a means that makes it difficult to rewrite the contents stored in the ticket gate device or print on the ticket face. [Means for solving the problem]

[0008] In order to solve the above problem, the present invention provides a refund target determination device, A first acquisition means for acquiring ticket stored information, which is information stored in a ticket used for boarding a train that has been read at a ticket gate device; a determination means for determining whether or not a refund is required for a user of the ticket for which the ticket storage information has been acquired; A second acquisition means for acquiring abnormality setting information which is information indicating whether a passenger who has passed through the ticket gate device is eligible for a refund; Equipped with The abnormality setting information is information for turning on an abnormality setting based on delayed train information transmitted to the ticket gate device of a station at which a train for which the ticket is to be refunded stops, The determination means determines whether or not a refund is required to be made to the user of the ticket for which the ticket storage information has been acquired, using the ticket content information extracted by the first extraction means and the on / off of the emergency setting in the emergency setting information acquired by the second acquisition means. It is characterized by:

[0009] The invention described in claim 2 is the refund target determination device described in claim 1, a first extraction means for extracting, from a first storage means in which the ticket storage information and ticket content information, which is information related to the contents of the ticket including information on whether the ticket is eligible for refund, are stored in association with each other, the ticket content information corresponding to the ticket storage information acquired by the first acquisition means; The determination means determines the ticket content information extracted by the first extraction means. and using the on / off of the abnormality setting in the abnormality setting information acquired by the second acquisition means, The ticket storage information is used to determine whether or not a refund is required for the user of the acquired ticket.

[0010] The invention described in claim 3 is 1 or 3. In the refund item determination device according to claim 2, The ticket storage information is information stored on the issued ticket by a one-dimensional or two-dimensional predetermined code. It is characterized by:

[0012] Claim 4 The invention described in claim 1 3 In the refund object determination device according to any one of the claims, a second extraction means for extracting, from a second storage means in which the ticket storage information and status information relating to the status of the ticket are stored in association with each other, the status information corresponding to the ticket for which the ticket storage information has been acquired; an update means for updating the status information extracted by the second extraction means according to a result of the determination by the determination means; The present invention is characterized by comprising:

[0013] Claim 5 The invention described in is a refund target determination system, From claim 1 4 The refund target determination device according to any one of the preceding claims, A ticket gate installed at a railway station, The present invention is characterized by comprising:

[0014] Claim 6 The invention described in claim 5 In the refund eligibility determination system described in The ticket gate device, A third storage means for storing the abnormality setting information; a first transmission means for transmitting the abnormality setting information stored in the third storage means to the refund eligibility determination device; A second transmission means for transmitting ticket storage information, which is information stored in a ticket used for boarding the train and read by the ticket gate device, to the refund eligibility determination device; The present invention is characterized by comprising:

[0015] Claim 7 The invention described in claim 5 or 6 In the refund eligibility determination system described in The present invention is characterized in that it further comprises a refund eligibility notification device which transmits a notification to a terminal device used by a user of a ticket that has been determined by the refund eligibility determination device to require a refund, to the effect that the ticket is eligible for refund.

[0016] Claim 8 The invention described in is a refund target discrimination program, Computer, A first acquisition means for acquiring ticket stored information which is information stored in a ticket used for boarding a train read by a ticket gate device; a determination means for determining whether or not a refund is required for the user of the ticket for which the ticket storage information has been acquired; a second acquisition means for acquiring abnormality setting information which is information indicating whether a passenger who has passed through the ticket gate device is eligible for a refund; The abnormality setting information is information for turning on an abnormality setting based on delayed train information transmitted to the ticket gate device of a station at which a train for which the ticket is to be refunded stops, The determination means determines whether or not a refund is required to the user of the ticket for which the ticket storage information has been acquired, using the on / off of the emergency setting in the emergency setting information acquired by the second acquisition means. It is characterized by:

[0017] Claim 9 The invention described in In a refund object determination method using a refund object determination device, A first acquisition step of acquiring ticket stored information, which is information stored in a ticket used for boarding a train that has been read by a ticket gate device; a determination step of determining whether or not a refund is required for the user of the ticket for which the ticket storage information has been acquired; A second acquisition step of acquiring abnormality setting information which is information indicating whether a passenger who has passed through the ticket gate device is eligible for a refund, The abnormality setting information is information for turning on an abnormality setting based on delayed train information transmitted to the ticket gate device of a station at which a train for which the ticket is to be refunded stops, The determination step determines whether or not a refund is required to be made to the user of the ticket for which the ticket storage information has been acquired, using the on / off of the emergency setting in the emergency setting information acquired by the second acquisition means. It is characterized by: Effect of the Invention

[0018] According to the present invention, it is possible to provide a refund eligibility determination device, a refund eligibility determination system, a refund eligibility determination program, and a refund eligibility determination method that make it possible to determine whether a ticket held by a passenger after exiting a train is eligible for a refund, even when tickets used to board a train are issued using a means that makes it difficult to rewrite the contents stored in the ticket gate device or print on the ticket face. [Brief description of the drawings]

[0019] [Figure 1] 1 is a block diagram showing an outline of the configuration of a ticket information processing system according to an embodiment. [Diagram 2] 2 is a block diagram showing a configuration of a ticket information management server in the ticket information processing system according to the embodiment. FIG. [Diagram 3] 2 is a block diagram showing a configuration of a ticket reservation server in the ticket information processing system according to the embodiment. FIG. [Figure 4] 2 is a block diagram showing a configuration of a ticket issuing server in the ticket information processing system according to the embodiment. FIG. [Diagram 5] 2 is a block diagram showing a configuration of an operation information server in the ticket information processing system according to the embodiment. FIG. [Figure 6] 1 is a block diagram showing a configuration of a ticket gate device 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 a configuration of a user terminal in the ticket information processing system according to the embodiment. FIG. [Figure 9] 2 is a flowchart showing an outline of an overall flow of operations of the ticket information processing system according to the embodiment. [Figure 10] 5 is a flowchart showing an operation of the ticket information processing system according to the embodiment when issuing a ticket. [Figure 11] 5 is a flowchart showing an operation of the ticket information processing system according to the embodiment when issuing a ticket. [Figure 12] 2 is a diagram showing a data structure of two-dimensional code data in the ticket information processing system according to the embodiment. FIG. [Figure 13] 13 is a flowchart showing operations of the ticket information processing system according to the embodiment when performing a refund object encoding process and switching an abnormality setting. [Figure 14] 5 is a flowchart showing the operation of the ticket information processing system according to the embodiment when exiting through a ticket gate device. [Figure 15] 10 is a flowchart showing an operation during a refund process of the ticket information processing system according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0021] [First Configuration Description] First, the configuration of a ticket information processing system 100 according to an embodiment of the present invention will be described.

[0022] The ticket information processing system 100 is a system for providing tickets using a predetermined one-dimensional or two-dimensional code to users who use the system, and for supporting refund processing for users who exit through a ticket gate device using the ticket when a train is delayed.As shown in FIG. 1, the system is configured with various servers managed by a railway operator or the like who manages and operates the ticket information processing system 100, namely, a ticket information management server 110, a ticket reservation server 120, a ticket issuing server 130, and an operation information server 140, as well as a ticket gate device 150 and a ticket issuing device 160 installed at each station on the railway line, and a user terminal 170 carried by each user who uses the ticket information processing system 100. Moreover, each device is connected to the others via a communication network N, as shown in FIG.

[0023] The above-mentioned servers do not necessarily have to be provided separately, and a single information device such as a PC (Personal Computer), WS (Work Station), etc. may function as multiple servers. For example, a single server may function as both the ticket reservation server 120 and the ticket issuing server 130. In this case, such a single server corresponds to both the ticket reservation server 120 and the ticket issuing server 130 in this embodiment.

[0024] 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 PCs or WSs connected via a communication network N. In this case, a group of such a plurality of information devices corresponds to each server in this embodiment. Moreover, the ticket gate device 150, the ticket issuing device 160, and the user terminal 170 do not necessarily have to be realized by a single device, and may be realized by a plurality of devices.

[0025] [1 Ticket information management server] The ticket information management server 110 is an information device such as a PC or a WS, and as described below, manages information required for ticket issuance, such as operating train information D4 and reservation status information D5, and also generates magnetic ticket encoding information D3 and transmits it to other servers. As shown in FIG. 2, the ticket information management server 110 includes, for example, a control unit 111, a storage unit 112, and a communication unit 113.

[0026] The control unit 111 is a part that controls the operation of the ticket information management server 110, and is configured, for example, with a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), etc., and controls each part of the ticket information management server 110 in cooperation with the CPU and programs stored in the memory unit 112.

[0027] The memory unit 112 is a part where various information required for the operation of the ticket information management server 110 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 110, such as program data, in a manner that can be read and written by the control unit 111.

[0028] The memory unit 112 includes a magnetic ticket encoded information issuing program 1121, a running train information memory unit 1122 in which running train information D4 is stored, and a reservation status information memory unit 1123 in which reservation status information D5 is stored.

[0029] The magnetic ticket encoded information issuance program 1121 is a program that includes various instructions to the control unit 111 for operating the ticket information management server 110, and the operation of the ticket information management server 110 described in the operation explanation below is performed in accordance with the magnetic ticket encoded information issuance program 1121. The information stored in each storage unit will be described in detail in the explanation of the operation.

[0030] The communication unit 113 is a part used for communication between the ticket information management server 110 and the ticket reservation server 120, the ticket issuing server 130 and the ticket issuing device 160, 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 111.

[0031] [2 Ticket Reservation Server] The ticket reservation server 120 is, for example, an information device such as a PC or a WS, and, as described below, acquires information related to tickets that users wish to purchase from the user terminal 170, and processes refunds to users who are eligible for refunds. As shown in FIG. 3, like the ticket information management server 110, the ticket reservation server 120 includes, for example, a control unit 121, a storage unit 122, and a communication unit 123.

[0032] The configurations of the control unit 121 and the communication unit 123 are the same as those of the control unit 111 and the communication unit 113 in the ticket information management server 110, respectively. The memory unit 122, like the memory unit 112 in the ticket information management server 110, is composed of, for example, an HDD (Hard Disk Drive), semiconductor memory, etc., and is equipped with a ticket reservation program 1221 and a ticket information memory unit 1222 in which user information D2, magnetic ticket encoding information D3, ticket purchase information D7, ticket reservation information D9, ticket number information D12, and two-dimensional code usage time information D16 are stored.

[0033] The ticket reservation program 1221 is a program including various commands to the control unit 121 for operating the ticket reservation server 120. The operation of the ticket reservation server 120, which will be described later in the description of the operation, is performed in accordance with the ticket reservation program 1221. The information stored in each storage unit will be described in detail in the explanation of the operation.

[0034] In addition, as shown in FIG. 1, the ticket reservation server 120 is connected to the ticket information management server 110, the ticket issuing server 130, and the user terminal 170 via a communication network N by the communication unit 123, making it possible to send and receive data between the ticket information management server 110, the ticket issuing server 130, and the user terminal 170.

[0035] [3 Ticket issuing server] The ticket issuing server 130 is, for example, an information device such as a PC or a WS, and performs tasks such as generating data related to the two-dimensional code used as the ticket, and determining whether or not a user who exits through the ticket gate device 150 is eligible for a refund, as described below. As shown in FIG. 4, the ticket issuing server 130 is configured to include, for example, a control unit 131, a storage unit 132, and a communication unit 133, similar to the ticket information management server 110 and the like.

[0036] The configurations of the control unit 131 and the communication unit 133 are the same as those of the control unit 111 and the communication unit 113 in the ticket information management server 110, respectively. The memory unit 132, like the memory unit 112 in the ticket information management server 110, is composed of, for example, an HDD (Hard Disk Drive), semiconductor memory, etc., and is equipped with a ticket issuance program 1321, a ticket information memory unit 1322 in which magnetic ticket encoding information D3, ticket purchasing information D7, ticket identifier information D11, ticket number information D12 and two-dimensional code usable time information D16 are stored, an encoded information memory unit 1323 in which encoded information D14 is stored, a test processing information memory unit 1324 in which test processing information D18 is stored, and a stop station information memory unit 1325 in which train stop station information D23 is stored.

[0037] The ticket issuing program 1321 is a program that includes various instructions to the control unit 131 for operating the ticket issuing server 130, and the operation of the ticket issuing server 130 described in the operation explanation below is performed in accordance with the ticket issuing program 1321. The information stored in each storage unit will be described in detail in the explanation of the operation.

[0038] In addition, as shown in FIG. 1, the ticket issuing server 130 is connected to the ticket information management server 110, the ticket reservation server 120, the operation information server 140, the ticket gate device 150, and the ticket issuing device 160 via a communication network N by the communication unit 133, and data can be transmitted and received between the ticket information management server 110, the ticket reservation server 120, the operation information server 140, the ticket gate device 150, and the ticket issuing device 160.

[0039] [4 Traffic Information Server] The operation information server 140 is, for example, an information device such as a PC or a WS, and as described below, collects information related to train delay times and transmits information related to trains whose delay times exceed a predetermined time to the ticket issuing server 130. As shown in FIG. 5, the operation information server 140 is configured to include, for example, a control unit 141, a storage unit 142, and a communication unit 143, similar to the ticket information management server 110 and the like.

[0040] The configurations of the control unit 141 and the communication unit 143 are the same as those of the control unit 111 and the communication unit 113 in the ticket information management server 110, respectively. The memory unit 142, similar to the memory unit 112 in the ticket information management server 110, is composed of, for example, an HDD (Hard Disk Drive), semiconductor memory, etc., and is equipped with a delayed train identification program 1421 and a delay time information memory unit 1422 in which delay time information D21 is stored.

[0041] The delayed train identification program 1421 is a program that includes various instructions to the control unit 141 for operating the operation information server 140, and the operation of the operation information server 140 described in the operation explanation below is performed in accordance with the delayed train identification program 1421. The information stored in each storage unit will be described in detail in the explanation of the operation.

[0042] As shown in FIG. 1, the operation information server 140 is connected to the ticket issuing server 130 via a communication network N by a communication unit 143, and is capable of transmitting and receiving data to and from the ticket issuing server 130.

[0043] [5 Ticket gates] The ticket gate device 150 is installed at each station on a railway line and automatically performs ticket gate operations such as determining whether or not a person can enter or exit the ticket gate. As described below, the ticket gate device 150 opens and closes the gate opening / closing section 155 depending on whether or not a user holding a ticket can enter or exit the ticket gate. As shown in FIG. 6, the ticket gate device 150 is configured similarly to the ticket information management server 110, for example, by including a control unit 151, a memory unit 152, and a communication unit 153, as well as a ticket information reading unit 154 and an opening / closing unit 155.

[0044] The configurations of the control unit 151 and the communication unit 153 are the same as those of the control unit 111 and the communication unit 113 in the ticket information management server 110, respectively. The memory unit 152, like the memory unit 112 in the ticket information management server 110, is composed of, for example, an HDD (Hard Disk Drive), semiconductor memory, etc., and is equipped with an entry / exit processing program 1521, a test processing information memory unit 1522 in which test processing information D18 is stored, an equipment information memory unit 1523 in which ticket gate device installation station information D25 and ticket gate device equipment information D26 are stored, and an abnormality setting information memory unit 1524 in which abnormality setting information D24 is stored.

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

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

[0047] The ticket information reading unit 154 is a part for reading the stored contents of a ticket issued by 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 reading unit 154, it reads the stored contents of the ticket.

[0048] The opening / closing section 155 is a means for switching the ticket gate device 150 between an open and closed state, and has a fence that can be opened and closed freely. As described below, based on the result of a determination as to whether the user can enter or exit the station where the ticket gate device 150 is installed, the opening section 155 is set to an open state when entry or exit is permitted, and the closing section 155 is set to a closed state when entry or exit is not permitted.

[0049] In addition, in an unused state where the user is not holding the ticket over the ticket information reading unit 154 and the ticket gate device 150 is not being used, the opening / closing unit 155 may be in either the open state or the closed state. However, it is preferable to set it to the open state in the unused state, and to keep it in the open state when a user who holds the ticket is permitted to enter or exit, and to set it to the closed state when a user who holds the ticket is not permitted to enter or exit, or when a user attempts to enter or exit without holding the ticket. In the present invention, opening / closing section 155, which was open when not in use, and maintaining the open state when a user holds a ticket over it, is also considered to be included in opening / closing section 155 being open.

[0050] [6 Ticket issuing device] The ticket issuing device 160 is a device installed at each station on a railway line and used by users when purchasing tickets to board a train. In this embodiment, as described below, the ticket issuing device 160 is used when issuing tickets using a specified one-dimensional or two-dimensional code on a specified medium such as paper. As shown in FIG. 7, the ticket issuing device 160 is configured to include a control unit 161, a memory unit 162, and a communication unit 163, similar to the ticket information management server 110, and further includes a display unit 164, an operation unit 165, and a ticket issuing unit 166.

[0051] The configurations of the control unit 161 and the communication unit 163 are the same as those of the control unit 111 and the communication unit 113 in the ticket information management server 110, respectively. The memory unit 162, like the memory unit 112 in the ticket information management server 110, is composed of, for example, an HDD (Hard Disk Drive), semiconductor memory, etc., and is equipped with a magnetic ticket encoding information issuance program 1621, a running train information memory unit 1622 in which running train information D4 is stored, and a reservation status information memory unit 1623 in which reservation status information D5 is stored.

[0052] The magnetic ticket encoded information issuance program 1621 is a program that includes various instructions to the control unit 161 for operating the ticket issuing device 160, and the operation of the ticket issuing device 160 described in the operation explanation below is performed in accordance with the magnetic ticket encoded information issuance program 1621. The information stored in each storage unit will be described in detail in the explanation of the operation.

[0053] In addition, as shown in FIG. 1, the ticket issuing device 160 is connected to the ticket information management server 110 and the ticket issuing server 130 via a communication network N by a communication unit 163, making it possible to send and receive data between the ticket information management server 110 and the ticket issuing server 130.

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

[0055] The operation unit 165 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 who purchases a ticket on the ticket issuing device 160 and outputs an operation signal corresponding to the operation input to the control unit 161. The operation unit 165 may be, for example, a touch panel formed integrally with the display unit 164, and is not particularly limited as long as it can receive operation input from a user who purchases a ticket on the ticket issuing device 160.

[0056] The ticket issuing unit 166 is a part that issues tickets to users under the control of the control unit 161, and in this embodiment, as described below, issues tickets using a specified one-dimensional or two-dimensional code based on data received from the ticket issuing server 130 on a specified medium such as paper.

[0057] [7 User terminals] The user terminal 170 is an information device such as a smartphone or tablet terminal carried by each user who uses this system to receive tickets, etc., and is used when entering or exiting the ticket gate device 150 using a ticket issued by a specified one-dimensional or two-dimensional code, as described below. As shown in FIG. 8, the user terminal 170 is configured to include, for example, a control unit 171, a storage unit 172, a communication unit 173, a display unit 174, and an operation unit 175, similar to the ticket issuing device 160.

[0058] The configurations of the control unit 171, communication unit 173, display unit 174, and operation unit 175 are the same as those of the control unit 161, communication unit 163, display unit 164, and operation unit 165 in the ticket issuing device 160, respectively. The memory unit 172, like the memory unit 162 in the ticket issuing device 160, is composed of, for example, an HDD (Hard Disk Drive), semiconductor memory, etc., and is equipped with a user terminal application 1721 and a ticket information memory unit 1722 in which two-dimensional code image data D19, ticket number information D12, and ticket reservation information D9 are stored.

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

[0060] The user terminal 170 is also connected to the ticket reservation server 120 via a communication network N through a communication unit 173, and is capable of transmitting and receiving data to and from the ticket reservation server 120.

[0061] [8 Communication Networks] 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 constituting 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.

[0062] [Second operation explanation] The operation of the ticket information processing system 100 according to this embodiment when used will be described below. As shown in the flowchart of Fig. 9, the operation of the ticket information processing system 100 is roughly divided into two steps, step S1 (issuing a ticket) and step S2 (exiting the ticket gate when the train is delayed), and step S2 (exiting the ticket gate when the train is delayed) is composed of step S21 (encoding processing for refund and switching of abnormality settings), step S22 (exiting from the ticket gate device), and step S23 (refund processing).

[0063] [1 Step S1: Issuing a ticket] First, the operation of the present system when issuing a ticket to a user for boarding a train will be described with reference to the flowcharts of Figs. 10 and 11, taking as an example a case where a ticket is issued to the user terminal 170 by data.

[0064] When a user of the ticket information processing system 100 wishes to use this system to be issued a ticket for boarding a train, the user first uses the operation unit 175 of the user terminal 170 to input information related to the ticket he or she wishes to reserve, i.e., desired ticket information D1 including, for example, the train boarding station, disembarking station, departure time, arrival time, seat number, etc., and information related to the user who wishes to make the reservation, i.e., user information D2 including, for example, the user's identification information such as a pre-set ID, information related to the payment method such as a credit card, etc. (step S1-1). Once the desired ticket information D1 and user information D2 have been input, the control unit 171 transmits the input information from the communication unit 173 via the communication network N to the ticket reservation server 120 (step S1-2).

[0065] The user may input the desired ticket information D1 and user information D2, for example, by specifying the desired train, seat, boarding station, disembarking station, payment method, etc. on a specific ticket reservation website provided by the ticket reservation server 120 and configured to allow the user to specify the desired train, seat, boarding station, disembarking station, payment method, etc. Also, a specific application may be downloaded in advance to storage unit 172 of user terminal 170, and input may be performed according to that application.

[0066] In addition, the user information D2 may be input one by one by the user in accordance with the above-mentioned website or application, but the information may also be stored in advance in the ticket information storage unit 1222 of the storage unit 122 of the ticket reservation server 120 in accordance with the user's input, and the user may input only the user's identification information, such as an ID, and the ticket reservation server 120, upon receiving the identification information, may extract the corresponding user information D2 based on the identification information.

[0067] In the ticket reservation server 120, when the communication unit 123 receives the desired ticket purchase information D1 and user information D2, the control unit 121 transmits the received desired ticket purchase information D1 from the communication unit 123 via the communication network N to the ticket information management server 110, together with a specified request to transmit magnetic ticket encoded information D3 corresponding to the data (step S1-3).

[0068] In the ticket information management server 110, when the communication unit 113 receives the desired ticket purchase information D1 and a request to send the magnetic ticket encoded information D3, the control unit 111 checks the train's available seats based on the operating train information D4 stored in the operating train information memory unit 1122 and the reservation status information D5 stored in the reservation status information memory unit 1123 if a seat needs to be reserved, and if a ticket can be purchased 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 and obtains the corresponding magnetic ticket encoded information D3 (step S1-4).

[0069] The magnetic ticket encoding information D3 is information that constitutes the ticket contents, and is the same as that encoded onto a magnetic ticket when a ticket for boarding a train is issued using a conventional magnetic ticket, and includes, for example, information relating to the contents of the ticket that corresponds to the desired ticket purchase information D1, such as the specific validity section of the ticket (the boarding station that is the start of the section, the disembarking station that is the end of the section, and any intermediate stations located between the boarding station and the disembarking station) and the validity period of the ticket.

[0070] The magnetic ticket encoded information D3 also includes the status of the ticket, i.e., entry and exit history, and information on the section already boarded, specifically, information on the state of each ticket, such as unused (before entry), used (after exiting at the disembarking station), in use (after entry and before exiting), in use (after exiting at an intermediate station), etc. Some tickets used to board trains allow repeated entry and exit (getting off and getting on at an intermediate station) within the valid section (the section that passes through intermediate stations between the boarding station and the disembarking station) as long as the ticket does not return to the section already boarded, so if the ticket has got off at an intermediate station and has not yet boarded, the ticket will be in use (after exiting at an intermediate station).

[0071] For example, immediately after purchasing a ticket, the status stored is that the ticket is unused, and when use begins (for example, entry through the ticket gate device 150), the status is 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 is updated to indicate that the ticket is in use (after exiting from an intermediate station), and when use is completed (exiting through the ticket gate device 150 at the disembarking station), the status is updated to indicate that the ticket has already been used.

[0072] By using the magnetic ticket encoding information D3, it is possible to reuse the same information that was used when issuing conventional magnetic tickets, thereby reducing costs when issuing tickets and when issuing two-dimensional codes related to the two-dimensional code image data D19 described below.

[0073] Once the magnetic ticket encoded information D3 is generated, the control unit 111 in the ticket information management server 110 transmits the generated magnetic ticket encoded information D3 together with the purchase result information D6 to the ticket reservation server 120 from the communication unit 113 via the communication network N (step S1-5). The purchase result information D6 is information related to whether or not the user can purchase the ticket corresponding to the desired ticket purchase information D1, and when the magnetic ticket encoded information D3 is generated, the information necessarily indicates that the ticket is available for purchase. If the user cannot purchase the ticket corresponding to the desired ticket purchase information D1, the magnetic ticket encoded information D3 is not sent, and only the purchase result information D6 indicating that the ticket cannot be purchased is sent to the ticket reservation server 120.

[0074] In the ticket reservation server 120, when the communication unit 123 receives the magnetic ticket encoded information D3 and the purchase result information D6, the control unit 121 transmits the purchase result information D6 from the communication unit 123 via the communication network N to the user terminal 170 that transmitted the desired ticket purchase information D1 and user information D2 in step S1-2 (step S1-6), and in the user terminal 170 that receives this via the communication unit 173, the control unit 171 displays the ticket purchase result on the display unit 174 based on the received data (step S1-7).

[0075] Once the ticket reservation server 120 has completed sending the purchase result information D6 to the user terminal 170, it then generates ticket purchase information D7 and ticket reservation information D9 relating to the ticket purchased by the user, links these to the user information D2 and magnetic ticket encoded information D3, and stores them in the ticket information storage unit 1222 of the storage unit 122 (step S1-8).

[0076] The ticket purchase information D7 is information for linking together each piece of information related to an issued ticket, such as the magnetic ticket encoded information D3, the purchase result information D6, and the ticket reservation information D9, including, for example, ticket purchase number information D8, which is information related to a purchase number assigned to each ticket. The ticket purchase information D7 also includes information related to the contents of the ticket corresponding to the desired ticket purchase information D1, and information related to the status of the ticket, similar to that included in the magnetic ticket encoded information D3. The ticket reservation information D9 is data relating to the specific reservation details made by the user for the reserved ticket, for management by the ticket reservation server 120. The ticket reservation information D9 also includes information relating to the details of the ticket corresponding to the desired ticket purchase information D1, similar to that contained in the magnetic ticket encoded information D3, and information relating to the status of the ticket.

[0077] In the ticket reservation server 120, once the above data is generated, the control unit 121 transmits the magnetic ticket encoded information D3 and the ticket purchasing information D7 to the ticket issuing server 130 from the communication unit 123 via the communication network N (step S1-9). In the ticket issuing server 130, which receives this data via the communication unit 133, the control unit 131 links the received magnetic ticket encoded information D3 and ticket purchasing information D7 and stores them in the ticket information memory unit 1322 of the memory unit 132 (step S1-10).

[0078] In addition, the transmission of the magnetic ticket encoded information D3 and the ticket purchasing information D7 from the ticket reservation server 120 to the ticket issuing server 130 in step S1-9 does not necessarily have to be performed immediately after the generation of the ticket purchasing information D7 and the ticket reservation information D9 in step S1-8. For example, multiple pieces of magnetic ticket encoded information D3 and ticket purchasing information D7 may be transmitted to the ticket issuing server 130 together at a predetermined timing.

[0079] After the information has been stored in the ticket reservation server 120 and the ticket issuance server 130 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 175 of the user terminal 170 to input specific information (ticket issuance request information D10) requesting the issuance of a ticket with a two-dimensional code (step S1-11). When the ticket issuance request information D10 has been input, the control unit 171 of the user terminal 170 transmits the input information from the communication unit 173 to the ticket reservation server 120 via the communication network N (step S1-12).

[0080] The information relating to the ticket for which the user wishes to have a two-dimensional code issued may be entered, for example, by selecting the ticket for which the user wishes to have a two-dimensional code issued on a specific website provided by ticket reservation server 120 and configured to allow the user to select the ticket for which the user wishes to have a two-dimensional code issued from a list of ticket reservation information D9 relating to tickets that the user has purchased and which is stored on ticket reservation server 120. Also, a specific application may be downloaded in advance to storage unit 172 of user terminal 170, and input may be performed according to that application.

[0081] In the ticket reservation server 120, when the communication unit 123 receives the ticket issuance request information D10, the control unit 121 searches the ticket information storage unit 1222 of the storage unit 122 based on the received ticket issuance request information D10, extracts the corresponding ticket purchasing information D7, and transmits the ticket purchase number information D8 included in the extracted ticket purchasing information D7 from the communication unit 123 via the communication network N to the ticket issuance server 130 together with static / dynamic issuance identification information D15, 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 S1-13).

[0082] In the ticket issuing server 130, when the communication unit 133 receives the ticket purchase number information D8 included in the ticket purchase information D7 related to the ticket issuance request information D10, the control unit 131 extracts the corresponding ticket purchase information D7 stored in the ticket information storage unit 1322 of the storage unit 132 according to the received ticket purchase number information D8, sets an ID (identifier) ​​for each of the extracted ticket purchase information D7 according to a predetermined rule, generates ticket identifier information D11 which is information related to the identifier to be assigned to each two-dimensional code data D13 described later, and generates a number to generate ticket number information D12 which is information related to the number to be assigned to each two-dimensional code data D13 described later, and stores it in the ticket information storage unit 1322 of the storage unit 132 in association with the corresponding magnetic ticket encoded information D3 and ticket purchase information D7 (step S1-14). Both the ticket identifier information D11 and the ticket number information D12 are information that can identify and specify each ticket assigned to each ticket.

[0083] Next, the control unit 131 uses the ticket purchase information D7 and the generated ticket identifier information D11 to create two-dimensional code data D13 in accordance with a predetermined two-dimensional code format (step S1-15). As the two-dimensional code format, for example, a format related to QR Code (registered trademark) can be used.

[0084] In addition, when creating the two-dimensional code data D13, the control unit 131 refers to the received static / dynamic issuance identification information D15, and if this information indicates that the two-dimensional code to be issued is dynamic, it generates two-dimensional code usage time information D16, which is information related to the usage time of the two-dimensional code related to the two-dimensional code data D13 to be created, and stores the generated two-dimensional code usage time information D16 in the ticket information storage unit 1322 of the storage unit 132 in association with the corresponding magnetic ticket encoding information D3, ticket purchasing information D7, ticket identifier information D11, and ticket number information D12. The two-dimensional code available time information D16 may be set, for example, in the form of the time when the two-dimensional code data D13 was created in step S1-15 and a predetermined time (such as 5 minutes) from that time.

[0085] The two-dimensional code data D13 is the original data of the two-dimensional code created according to a predetermined two-dimensional code format, and includes information to be stored on a ticket issued by the two-dimensional code as described later. Note that it is also possible to use a one-dimensional code instead of the two-dimensional code, although this is not preferable due to the relationship of data capacity to area.

[0086] The two-dimensional code data D13 has multiple storage areas, for example, a basic information section D13-1 and a validity checking section D13-2 as shown in Fig. 12, and only a part of the information in the basic information section D13-1 is encoded using the encoding information D14 stored in the encoding information storage section 1323 of the storage section 132. The encoding information D14 is data related to a predetermined conversion rule used by the ticket issuing server 130 when encoding the two-dimensional code data D13.

[0087] The basic information section D13-1 includes attribute information related to the issuing company, the issuing time, etc., as well as the ticket identifier information D11 generated in step S1-14. The ticket identifier information D11 is included in the information encoded using the encoding information D14.

[0088] The validity testing section D13-2 also includes testing information D17, 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 D13-1. The testing information D17 is generated by the control section 131 inputting the data included in the basic information section D13-1 into a predetermined conversion rule or calculation formula stored as testing processing information D18 in the testing processing information storage section 1324 of the storage section 132.

[0089] When the two-dimensional code data D13 is generated, the control unit 131 in the ticket issuing server 130 transmits the generated two-dimensional code data D13 together with the corresponding ticket number information D12 from the communication unit 133 via the communication network N to the ticket reservation server 120 (step S1-16). In addition, when the control unit 131 generates the two-dimensional code usage time information D16 in step S1-15, it also transmits the two-dimensional code usage time information D16, together with the ticket number information D12 and the two-dimensional code data D13, from the communication unit 133 via the communication network N to the ticket reservation server 120.

[0090] In the ticket reservation server 120, when the communication unit 123 receives the information transmitted from the ticket issuing server 130, the control unit 121 stores the received ticket number information D12 in the ticket information storage unit 1222 of the storage unit 122 in association with the corresponding magnetic ticket encoded information D3, ticket purchasing information D7, and ticket reservation information D9, and then generates two-dimensional code image data D19, which is data that has been converted into image data based on the received two-dimensional code data D13 (step S1-17). In addition, when two-dimensional code usage time information D16 is received from the ticket issuing server 130, the control unit 121 also stores the two-dimensional code usage time information D16 in the ticket information storage unit 1222 of the storage unit 122 in association with the corresponding magnetic ticket encoding information D3, ticket purchasing information D7, ticket reservation information D9, and ticket number information D12.

[0091] After generating the two-dimensional code image data D19, the control unit 121 transmits the generated data together with the corresponding ticket number information D12 and ticket reservation information D9 from the communication unit 123 via the communication network N to the user terminal 170 (step S1-18).

[0092] Furthermore, when the above transmission process is completed, in the ticket reservation server 120, the control unit 121 updates the information relating to the status of the ticket, which is contained in the magnetic ticket encode information D3, ticket purchase information D7, and ticket reservation information D9 related to the ticket, stored in the ticket information storage unit 1222 of the storage unit 122, to information indicating that a two-dimensional code has been issued (step S1-19), and transmits two-dimensional code issuance status update information D20, which is information relating to the content of the status update, to the ticket issuing server 130 (step S1-20). Similarly, in the ticket issuing server 130, the control unit 131 updates the information relating to the status of the ticket, which is contained in the magnetic ticket encode information D3 and ticket purchase information D7 related to the ticket, stored in the ticket information storage unit 1322 of the storage unit 132, to information indicating that a two-dimensional code has been issued (step S1-21).

[0093] In addition, in step S1-19, it is possible to update only the information regarding the ticket status contained in the ticket purchasing information D7 and the ticket reservation information D9, without updating the information regarding the ticket status contained in the magnetic ticket encoded information D3.

[0094] In the user terminal 170, when the communication unit 173 receives the two-dimensional code image data D19, the ticket number information D12, and the ticket reservation information D9, the control unit 171 links the received data and stores it in the ticket information storage unit 1722 of the storage unit 172 (step S1-22). This makes it possible for the user terminal 170 to display on the display unit 174 an image of the two-dimensional code relating to the two-dimensional code image data D19 stored in the ticket information memory unit 1722 of the memory unit 172 and the ticket number relating to the ticket number information D12.

[0095] Alternatively, instead of generating the two-dimensional code image data D19 in the ticket reservation server 120, the control unit 121 of the ticket reservation server 120 may transmit the two-dimensional code data D13 from the communication unit 123 to the user terminal 170 via the communication network N instead of the two-dimensional code image data D19, and upon receiving the data in the user terminal 170, the control unit 171 may generate the two-dimensional code image data D19 in accordance with the user terminal application 1721, thereby acquiring the two-dimensional code image data D19.

[0096] [2 Step S2: Exiting the ticket gate when the train is delayed] Next, the operation of the system when a user exits through the ticket gate device 150 when the train is delayed for longer than a specified time will be explained in steps S21 (encoding process for refund target and switching of abnormality settings), step S22 (exiting through the ticket gate device) and step S23 (refund process).

[0097] [(1) Step S21: Switching between encoding processes subject to refund and abnormality settings] First, when a train is delayed for longer than a specified time, the magnetic ticket encoding information D3 for the ticket to be refunded is updated in the ticket issuing server 130 to indicate that the ticket is eligible for refund, and the operation of the system when the abnormality setting in the ticket gate device 150 is set to "ON" will be described with reference to the flowchart in Figure 13.

[0098] The operation information server 140 periodically acquires delay time information D21, which is delay information for each train, at predetermined time intervals (step S21-1). The acquisition method is not particularly limited, and for example, the latest information at the time may be acquired by communicating with a predetermined external system that collects and stores train delay information, and receiving delay information for each train in operation via the communication network N by the communication unit 143. In addition, an employee of the railway operator or the like may manually input the delay time information D21 to the operation information server 140. At this time, information relating to all trains that may be included in the issueable ticket is obtained in step S1.

[0099] When the delay time information D21 is acquired, the control unit 141 in the operation information server 140 stores the acquired delay time information D21 in the delay time information storage unit 1422 of the storage unit 142, and then identifies trains whose delay time exceeds a predetermined time from the acquired information (step S21-2). For example, if the specified time is two hours, the control unit 141 extracts information related to trains that are delayed by two hours or more from the delay time information D21 acquired in step S21-1, and identifies the train related to that information as a train whose delay time exceeds the specified time.

[0100] From the standpoint of accuracy, it is preferable to identify trains whose delay times exceed a specified time individually for each train as described above. However, since it is assumed that trains running on the same line and section are delayed by roughly the same amount of time, in order to simplify the identification process, it is also possible to set a line and section, and then collectively identify all trains running on that line and section as trains whose delay times exceed a specified time.

[0101] After identifying a train whose delay time exceeds a predetermined time, the control unit 141 then transmits delayed train information D22, which is information relating to the train whose delay time identified in step S21-2 exceeds the predetermined time, from the communication unit 143 via the communication network N to the ticket issuing server 130 (step S21-3).

[0102] In the ticket issuing server 130, which receives the delayed train information D22 sent from the operation information server 140 via the communication unit 133, the control unit 131 searches the ticket information storage unit 1322, extracts the magnetic ticket encoded information D3 for which the passenger plans to use the train related to the delayed train information D22 from that point onwards, and updates the extracted magnetic ticket encoded information D3 by adding information indicating that the train is eligible for refund (step S21-4).

[0103] In the ticket issuing server 130, once the update of the magnetic ticket encoding information D3 is completed, the control unit 131 then identifies the stations at which the train related to the delayed train information D22 is scheduled to stop, based on the train stop station information D23 stored in the stop station information memory unit 1325 of the memory unit 132 (step S21-5). The train stop station information D23 includes information regarding the stations each train stops at and the stop times at each station, and the control unit 131 can identify the stations at which the train related to the delayed train information D22 will stop after that time based on such train stop station information D23.

[0104] Next, the control unit 131 transmits the delayed train information D22 from the communication unit 133 via the communication network N to the ticket gate device 150 installed at the station where the train related to the delayed train information D22 identified in step S21-5 is scheduled to stop (step S21-6).

[0105] In the ticket gate device 150, when the communication unit 153 receives the delayed train information D22 transmitted from the ticket issuing server 130, the control unit 151 switches the abnormality setting information D24 stored in the abnormality setting information memory unit 1524 to the "on" state in which the abnormality setting is turned on (step S21-7).

[0106] The abnormality setting information D24 is information that indicates whether or not the trains scheduled to stop at the station where the ticket gate device 150 is installed include trains that have been delayed beyond a specified time and are eligible for a refund. As described above, when delayed train information D22 sent from the ticket issuing server 130 is received, the control unit 151 switches this to the "on" state. In addition, after setting the abnormality setting information D24 to the "on" state, the control unit 151 may switch the abnormality setting to the "off" state, for example, when a predetermined time has elapsed since all trains that have received the delayed train information D22 sent from the ticket issuing server 130 have arrived at the station.

[0107] [(2) Step S22: Exiting from the ticket gate] Next, the operation of the system when a train is delayed beyond a predetermined time and a user uses the two-dimensional code issued in step S1 to exit through the ticket gate device 150 will be explained with reference to the flowchart in Figure 14 as an example of a case in which the ticket issuing server 130 determines whether or not the user can exit.

[0108] When the user wishes to exit the station through the ticket gate device 150 after boarding the train, the user holds the two-dimensional code issued in step S1 over the ticket information reading unit 154 of the ticket gate device 150. Specifically, the user performs a predetermined operation using the operation unit 175 of the user terminal 170 to cause the two-dimensional code relating to the two-dimensional code image data D19 to be displayed on the display unit 174, and then holds the displayed two-dimensional code over the ticket information reading unit 154.

[0109] When the two-dimensional code is held over the ticket information reading unit 154, the control unit 151 of the ticket gate device 150 causes the ticket information reading unit 154 to read the two-dimensional code data D13 from the held over two-dimensional code (step S22-1).

[0110] When the two-dimensional code data D13 is read by the ticket information reading unit 154, the control unit 151 determines whether the two-dimensional code is a genuine ticket or not (step S22-2).

[0111] Specifically, as described in step S1, the two-dimensional code data D13 is composed of multiple memory areas, for example, as shown in FIG. 12, a basic information section D13-1 and a validity testing section D13-2, and the validity testing section D13-2 includes testing information D17, which is information related to the result of a specified conversion or calculation for testing based on the data included in the basic information section D13-1, in accordance with a specified conversion rule or formula related to testing processing information D18.

[0112] Moreover, in the ticket gate device 150, a similar predetermined conversion rule or formula is stored in the test processing information storage unit 1522 of the storage unit 152 as test processing information D18.

[0113] Therefore, the control unit 151 performs a predetermined conversion or calculation for testing based on the data contained in the basic information section D13-1 of the two-dimensional code data D13 read in step S22-1, in accordance with the above-mentioned predetermined conversion rule or formula stored as testing processing information D18 in the testing processing information storage section 1522 of the storage unit 152. Then, if the result of the above conversion or calculation matches the testing information D17 contained in the validity testing unit D13-2, the control unit 151 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.

[0114] If it is determined in step S22-2 that the two-dimensional code data D13 relates to a genuine ticket, the control unit 151 in the ticket gate device 150 transmits the two-dimensional code data D13 read by the ticket information reading unit 154, together with the ticket gate device installation station information D25 and the ticket gate device equipment information D26 stored in the equipment information memory unit 1523 of the memory unit 152, and the abnormality setting information D24 stored in the abnormality setting information memory unit 1524, from the communication unit 153 via the communication network N to the ticket issuing server 130 (step S22-3). If it is determined in step S22-2 that the ticket is an unauthorized one, control unit 151 closes opening / closing unit 155 and ends the process.

[0115] The ticket gate installation station information D25 is information related to the station where the ticket gate 150 is installed, and indicates the station where a user who holds the two-dimensional code over the ticket information reading unit 154 will enter or exit through the ticket gate. The ticket gate device equipment information D26 is information related to the ticket gate device 150, and includes information indicating the operator that installed it, information regarding whether the ticket gate device 150 requires entry / exit determination by the ticket issuing server 130 or whether the ticket gate device 150 performs the entry / exit determination itself, and information regarding detailed settings such as fraud determination that are set for each ticket gate device 150.

[0116] In the ticket issuing server 130, which receives the information transmitted from the ticket gate device 150 via the communication unit 133, the control unit 131 determines based on the ticket gate device equipment information D26 whether the ticket gate device 150 is a ticket gate device 150 that requires an entry / exit determination by the ticket issuing server 130.If an entry / exit determination by the ticket issuing server 130 is required, the control unit 131 first decodes the encoded information in the basic information section D13-1 of the two-dimensional code data D13 using the encoded information D14 stored in the encoded information memory unit 1323 of the memory unit 132 (step S22-4).

[0117] Next, the control unit 131 searches the ticket information storage unit 1322 of the storage unit 132 based on the ticket identifier information D11 contained in the decrypted information, extracts the magnetic ticket encoded information D3 and ticket purchase information D7 corresponding to the received two-dimensional code data D13, and then compares the received ticket gate installation station information D25 and ticket gate equipment information D26 with the magnetic ticket encoded information D3 to make a determination as to whether the user is allowed to enter (step S22-5). If the magnetic ticket encoded information D3 and ticket purchase information D7 corresponding to the received two-dimensional code data D13 are not extracted, the control unit 131 determines that exit is not possible at that point. Therefore, the comparison of the ticket gate station information D25 and the ticket gate device information D26 with the magnetic ticket encoded information D3 as described above is performed only when the magnetic ticket encoded information D3 and ticket purchase information D7 corresponding to the received two-dimensional code data D13 are extracted.

[0118] Specifically, the entry history and exit history are checked from the information related to the ticket status included in the magnetic ticket encoding information D3 and the ticket purchase information D7, and the user's exit station related to the ticket gate station information D25 is compared with the information related to the validity zone included in the magnetic ticket encoding information D3. Then, for example, if the user is after entry but before exit, is within the validity period related to the magnetic ticket encoding information D3, and the user's exit station related to the ticket gate station information D25 is a station that is within the validity zone in the information related to the validity zone included in the magnetic ticket encoding information D3, it is determined that the user is able to exit, and if the user is before entry or after exit, is outside the validity period related to the magnetic ticket encoding information D3, or the user's exit station related to the ticket gate station information D25 is not a station that is within the validity zone in the information related to the validity zone included in the magnetic ticket encoding information D3, it is determined that the user is unable to exit.

[0119] In addition, if two-dimensional code usable time information D16 corresponding to the received two-dimensional code data D13 is stored in the ticket information memory unit 1322 of the memory unit 132, the control unit 131 also determines whether the two-dimensional code corresponding to the received two-dimensional code data D13 is within the usable time period prior to extracting the magnetic ticket encoding information D3 and the ticket purchase information D7. Specifically, the ticket information storage unit 1322 of the storage unit 132 is searched based on the ticket identifier information D11, and the two-dimensional code usage time information D16 corresponding to the received two-dimensional code data D13 is extracted. Then, for example, the time at which the two-dimensional code data D13 was created, which is included in the two-dimensional code usage time information D16, is compared with the current time, and if the difference is within a specified time period included in the two-dimensional code usage time information D16, it is determined that the time is within the usage time period, and if the difference is outside the specified time period included in the two-dimensional code usage time information D16, it is determined that the time is outside the usage time period. In this case, only if the control unit 131 determines that the available time is within the available time frame will it extract the magnetic ticket encoded information D3 and ticket purchase information D7 corresponding to the received two-dimensional code data D13, and compare the ticket gate installation station information D25 and the ticket gate equipment information D26 with the magnetic ticket encoded information D3 to determine whether or not the person can exit.If it determines that the available time frame is outside the available time frame, the control unit 131 will determine that the person cannot exit at that time.

[0120] Next, the control unit 131 determines whether or not a refund is required for the user of the ticket associated with the two-dimensional code data D13 received in step S22-3 (step S22-6).

[0121] That is, the control unit 131 first determines whether the abnormality setting information D24 received in step S22-3 is in the "on" state where the abnormality setting is on, or in the "off" state where the abnormality setting is off, and if it is in the "off" state where the abnormality setting is off, it determines that no refund is required.

[0122] If the abnormality setting information D24 received in step S22-3 is the "on" state, meaning that the abnormality setting is on, the control unit 131 then searches the ticket information storage unit 1322 of the storage unit 132 based on the ticket identifier information D11 contained in the information decoded in step S22-4, extracts the magnetic ticket encoded information D3 corresponding to the received two-dimensional code data D13, and determines whether the extracted magnetic ticket encoded information D3 contains information indicating that the ticket is eligible for refund. As a result, if the extracted magnetic ticket encoded information D3 contains information indicating that the ticket is eligible for a refund, it is determined that a refund is required, and if the extracted magnetic ticket encoded information D3 does not contain information indicating that the ticket is eligible for a refund, it is determined that a refund is not required.

[0123] When the above-mentioned determination is completed, the control unit 131 updates the information related to the status of the ticket stored in the ticket information storage unit 1322 of the storage unit 132 (step S22-7).

[0124] Specifically, if it is determined in step S22-5 that exit is possible, the information regarding the ticket status contained in the magnetic ticket encoding information D3 and the ticket purchase information D7 is set to "used" (after exiting at the disembarking station) or "in use" (after exiting at an intermediate station). In contrast, if it is determined in step S22-5 that exit is not possible, the information regarding the ticket status contained in the magnetic ticket encoding information D3 and the ticket purchase information D7 is not updated to indicate "used" (after exiting at the disembarking station) or "in use" (after exiting at an intermediate station).

[0125] Furthermore, if the control unit 131 determines in step S22-6 that the ticket related to the two-dimensional code data D13 received in step S22-3 requires a refund to the user, it updates the information related to the ticket status contained in the magnetic ticket encoded information D3 and the ticket purchase information D7 to indicate that the ticket is eligible for refund. Note that the magnetic ticket encoded information D3 was updated in step S21-4 to add information indicating that the ticket is eligible for refund, but the update of the information related to the ticket status is performed based on the determination result in step S22-6, separately from the update in step S21-4. On the other hand, if it is determined in step S22-6 that a refund is not required, the information relating to the ticket status contained in the magnetic ticket encoded information D3 and the ticket purchase information D7 is not updated to indicate that a refund is required.

[0126] When the above update is completed, the control unit 131 transmits information related to the determination result of the ticket gate exit in step S22-5 (exit determination result information D27) from the communication unit 133 via the communication network N to the ticket gate device 150 (step S22-8).

[0127] In the ticket gate device 150, which receives the entry determination result information D27 transmitted from the ticket issuing server 130 via the communication unit 153, the control unit 151 opens and closes the opening / closing gate 155 based on the received entry determination result information D27 (step S22-9). Specifically, if the received entry judgment result information D27 allows entry, the opening / closing section 155 will be set to the open state, and if the received entry judgment result information D27 does not allow entry, the opening / closing section 155 will be set to the closed state.

[0128] In addition, if it is determined in step S22-6 that a refund is required, specified information indicating that the ticket is eligible for a refund may be sent from the ticket issuing server 130 to the ticket gate device 150 along with the entry determination result information D27, and the ticket gate device 150 may receive the information via the communication unit 153 and notify the user passing through the ticket gate device 150 that the ticket is eligible for a refund by, for example, playing a specified sound using a sound generating means such as a speaker. In addition, the notification to the user terminal 170 in step S23-2 described below may be made at the same time as the user passes through the ticket gate, or after a predetermined time has elapsed since passing through the ticket gate, instead of the notification by the ticket gate device 150 described above.

[0129] In the ticket issuing server 130, after transmitting the entry determination result information D27 to the ticket gate device 150, information regarding the update contents of the information relating to the ticket status contained in the magnetic ticket encoded information D3 and the ticket purchasing information D7 in step S22-7 (entrance status update information D28) is transmitted from the communication unit 133 to the ticket reservation server 120 via the communication network N together with the ticket number information D12 stored in the ticket information memory unit 1322 of the memory unit 132 in association with the magnetic ticket encoded information D3 and the ticket purchasing information D7 (step S22-10).

[0130] In the ticket reservation server 120, when the communication unit 123 receives the entry status update information D28 and the ticket number information D12, the control unit 121 searches the ticket information memory unit 1222 of the memory unit 122 based on the received ticket number information D12, extracts the magnetic ticket encoded information D3, ticket purchase information D7, and ticket reservation information D9 stored in association with the ticket number information D12, and updates the information related to the ticket status contained in the extracted magnetic ticket encoded information D3, ticket purchase information D7, and ticket reservation information D9 in the same manner as the update in the ticket issuing server 130 in step S22-7 (step S22-11).

[0131] [(3) Step S23: Refund Processing] Next, the operation of the present system when carrying out a refund process for a user who has exited through the ticket gate device 150 when a train is delayed beyond a predetermined time will be described with reference to the flowchart of FIG.

[0132] In the ticket reservation server 120, in step S22-11, the information relating to the status of the ticket contained in the magnetic ticket encoded information D3, the ticket purchase information D7, and the ticket reservation information D9 is updated, and then the control unit 121 determines whether or not a refund is required for the user of the ticket related to the updated information (step S23-1).

[0133] In other words, if the update content in step S22-11 updates the information regarding the status of the ticket contained in the magnetic ticket encoded information D3, ticket purchasing information D7, and ticket reservation information D9 to be eligible for refund, the control unit 121 determines that the user of the ticket related to the magnetic ticket encoded information D3, ticket purchasing information D7, and ticket reservation information D9 is eligible for refund. On the other hand, if the update content in step S22-11 does not update the information related to the status of the ticket contained in the magnetic ticket encoded information D3, ticket purchasing information D7, and ticket reservation information D9 to be refunded, the control unit 121 determines that the user of the ticket related to the magnetic ticket encoded information D3, ticket purchasing information D7, and ticket reservation information D9 is not eligible for refund. If it is determined that the ticket is not eligible for refund, the process ends without proceeding to the steps after step S23-2.

[0134] If it is determined in step S23-1 that the ticket is eligible for refund, the control unit 121 of the ticket reservation server 120 then extracts, from the ticket information storage unit 1222 of the storage unit 122, the ticket number information D12 that was stored in association with the magnetic ticket encoded information D3, ticket purchase information D7, and ticket reservation information D9 updated in step S22-11, and transmits refund eligibility notification information D29, which is information notifying the user that the ticket is eligible for refund, together with the extracted ticket number information D12 from the communication unit 123 via the communication network N to the user terminal 170 that transmitted the desired ticket purchase information D1 and user information D2 relating to the ticket in step S1-2 (step S23-2).

[0135] In the user terminal 170 that has received the ticket number information D12 and the refund eligibility notification information D29 via the communication unit 173, the control unit 171 searches the ticket information storage unit 1722 of the storage unit 172 based on the received ticket number information D12, extracts the two-dimensional code image data D19 and ticket reservation information D9 stored in association with the ticket number information D12, and displays on the display unit 174 a notification that the ticket is eligible for refund based on the refund eligibility notification information D29, together with the two-dimensional code related to the extracted two-dimensional code image data D19 and detailed reservation information based on the extracted ticket reservation information D9 (step S23-3).

[0136] Furthermore, after transmitting the ticket number information D12 and the refund target notifying information D29 in step S23-2, the control unit 121 of the ticket reservation server 120 carries out a refund process (step S23-4). Specifically, for example, if the information relating to the payment method contained in the user information D2 received from the user terminal 170 in step S1-2 and stored in the ticket information memory unit 1222 of the memory unit 122 of the ticket reservation server 120 is a refundable payment method such as a credit card, the refund process can be carried out by carrying out a specified refund process for the credit card, etc.

[0137] In addition, if the information relating to the payment method included in the user information D2 is not refundable, in step S23-2, the refund target notification information D29 may include a message requesting the user to input information relating to the refund destination, and the refund process may be carried out after the user inputs the refund destination after confirming the request displayed on display unit 174 in step S23-3.

[0138] In addition, in cases where the information relating to the payment method included in the user information D2 is not refundable, a refund may be substituted for the user who would otherwise be eligible for a refund by, for example, awarding a specified number of points or a discount coupon for the next ticket purchase.

[0139] [Third effect explanation] Next, the effects of this embodiment will be described.

[0140] According to this embodiment, the ticket issuing server 130 acquires delayed train information D22, which is information relating to trains whose delay time exceeds a predetermined time, and then updates the magnetic ticket encoding information D3 for trains related to the delayed train information D22 by adding information indicating that the train is eligible for a refund. Therefore, when two-dimensional code data D13, which is information stored on a ticket based on a two-dimensional code read by the ticket gate device 150, is obtained, the corresponding magnetic ticket encoded information D3 is extracted, and depending on whether the extracted magnetic ticket encoded information D3 contains information indicating that the ticket is eligible for refund, it is possible to determine whether the ticket related to the two-dimensional code data D13 needs to be refunded to the user.

[0141] This makes it possible for the ticket issuing server 130 to determine whether or not a ticket held by a passenger after exiting the ticket gate 150 is eligible for a refund, even when tickets for boarding trains are issued using one-dimensional or two-dimensional codes, which make it difficult to rewrite the contents stored in the ticket gate 150 or to print on the face of the ticket.

[0142] In addition, the ticket issuing server 130 obtains from the ticket gate device 150 abnormality setting information D24, which is information indicating whether or not a passenger who exits through the ticket gate device 150 may be eligible for a refund when trains scheduled to stop at the station where the ticket gate device 150 is installed include trains that are delayed beyond a specified time, and then determines whether or not a refund is necessary using the abnormality setting information D24.This makes it possible to uniformly exclude users who exit through a ticket gate device 150 that is not eligible for a refund from being eligible for a refund, thereby reducing the processing burden related to determining whether or not a refund is necessary.

[0143] In addition, by determining whether or not a refund is required using the abnormality setting information D24, the following effects can be obtained, although they are rare cases. In other words, when there is a section between the entrance station and the exit station where two lines run parallel to each other, and only the train running on the first line is delayed beyond a predetermined time, and the train running on the second line is not delayed beyond a predetermined time, if a user holding a ticket for a train running on the first line boards a train running on the second line with a ticket for the train running on the first line and disembarks at an intermediate station where the train running on the first line does not stop, the abnormality setting information D24 of the ticket gate device 150 installed at such an intermediate station is in the "off" state with the abnormality setting turned off, and therefore it is possible to prevent a refund from being made to such a user by determining whether a refund is necessary using the abnormality setting information D24 as well.

[0144] Furthermore, if the ticket issuing server 130 determines that a refund is required for the user of the ticket related to the acquired two-dimensional code data D13, the information related to the ticket status contained in the magnetic ticket encoding information D3 and the ticket purchasing information D7 is updated to indicate that the ticket is eligible for refund, thereby enabling information related to the ticket status as to whether or not the ticket is eligible for refund to be stored. Additionally, by sending the updated information, that is, the entry status update information D28, to the ticket reservation server 120, the ticket reservation server 120 is able to notify the user terminal 170 used by the user eligible for refund and to perform the refund process.

[0145] In addition, by sending refund notification information D29, which is information notifying the user of the ticket to be refunded that it is eligible for a refund, from the ticket reservation server 120 to the user terminal 170 used by the user of the ticket to be refunded, the user to whom the ticket is eligible for a refund can be notified that it is eligible for a refund.

[0146] Furthermore, by having the ticket reservation server 120 carry out the refund process for the user of the ticket to be refunded, the refund process for the user can also be carried out automatically. Furthermore, refund processing can be performed even if the ticket was not issued using a means that allows the contents stored in the ticket gate device, such as a magnetic card, to be rewritten and the ticket face to be printed, and another advantage is that the user does not need to go to a station ticket counter or the like when processing a refund.

[0147] [Fourth Variation] Next, a modification of this embodiment will be described.

[0148] [1 Ticket issuing in ticket issuing device] In the above, we have described the case where a ticket is issued to the user terminal 170 using data, but this is not limited to this, and it is also possible for the ticket issuing device 160 to issue a ticket using a specified medium such as paper.

[0149] In this case, the user inputs the desired ticket information D1 and user information D2 into the ticket issuing device 160 using the operation unit 165, and according to this information, the ticket information management server 110 generates magnetic ticket encoded information D3, and the ticket issuing server 130 generates two-dimensional code data D13. After receiving the two-dimensional code data D13, the ticket issuing device 160 generates two-dimensional code image data D19 based on the two-dimensional code data D13, and the ticket issuing unit 166 issues a ticket on which the two-dimensional code related to the two-dimensional code image data D19 and the number related to the ticket number information D12 are stored by printing or other method on a specified medium such as paper.

[0150] In addition, when issuing the ticket at the ticket issuing device 160, the magnetic ticket encoded information D3 does not need to be generated by the ticket information management server 110, but may be generated at the ticket issuing device 160 immediately after the user inputs the desired ticket information D1 and user information D2, and then transmitted to the ticket issuing server 130.

[0151] Furthermore, when a ticket is issued by the ticket issuing device 160, the user terminal 170 does not transmit the desired ticket purchase information D1 and user information D2 to the ticket reservation server 120, and therefore the ticket reservation server 120 is unable to automatically obtain information regarding the user terminal 170, which will be the notification destination (the destination of the refund notification information D29) when the user becomes eligible for a refund, at the time of issuing the ticket.

[0152] Therefore, when issuing a ticket, it is preferable to require the user to use the operation unit 165 of the ticket issuing device 160 to input information regarding the notification destination in the event that the ticket becomes eligible for refund, and to enable the ticket reservation server 120 to obtain the information input by the user via the ticket issuing server 130. At this time, the user may also be required to input the refund destination for the refund process, or the notification when a refund is made may include a message requesting the user to input information regarding the refund destination, and the refund process may be carried out after the user has confirmed the request and input the refund destination.

[0153] [2. Entry Determination at Ticket Gate Devices] In the above, a case has been described in which the ticket issuing server 130 determines whether or not the user is permitted to enter the venue. However, the ticket gate device 150 may also determine whether or not the user is permitted to enter the venue.

[0154] In this case, in step S22-3, the ticket issuing server 130 receives information such as the two-dimensional code data D13 from the ticket gate device 150, and transmits magnetic ticket encoding information D3 corresponding to the received two-dimensional code data D13 to the ticket gate device 150. The ticket gate device 150 then determines whether entry or exit is possible, opens and closes the opening / closing section 155, and transmits information related to the determination result to the ticket issuing server 130.

[0155] [3 Issuing tickets using methods other than one-dimensional or two-dimensional codes] In the above, an example has been described in which a ticket is issued using a one-dimensional or two-dimensional code. In this regard, it is most preferable to issue tickets using such one-dimensional or two-dimensional codes because they can be easily issued without using dedicated media, but the method of issuing tickets is not necessarily limited to one-dimensional or two-dimensional codes. In other words, the above embodiment is similarly effective in that it enables the ticket issuing server 130 to determine whether or not a ticket held by a passenger after exiting through the ticket gate device 150 is eligible for refund even when tickets are issued by means other than a one-dimensional or two-dimensional code and even when the means is not capable of rewriting the contents stored in the ticket or printing on the face of the ticket at the ticket gate device 150.

[0156] Examples of means in which the configuration according to the above embodiment is effective other than one-dimensional or two-dimensional codes include tickets using IC cards and tickets that store specified ticket information in an IC tag attached to a mobile terminal.

[0157] [4 Change in abnormality setting switching method] In the above operation description, in step S21-7, when the ticket gate device 150 receives delayed train information D22 sent from the ticket issuing server 130, the abnormality setting information D24 stored in the abnormality setting information storage unit 1524 is automatically switched to the "on" state in which the abnormality setting is turned on. However, the method of switching the abnormality setting is not limited to this.

[0158] For example, a station attendant may operate the ticket gate device 150 from a designated terminal provided at the station, or an employee at a control facility that has jurisdiction over the ticket gate devices 150 at stations located within a designated range may operate the ticket gate device 150 using a terminal provided at the control facility, allowing a human to determine whether or not the abnormality settings need to be changed and then manually perform the changeover operation.

[0159] [5 Addition and modification of factors of encoding process eligible for refund] In the above operation description, in step S21-4, when the ticket issuing server 130 receives delayed train information D22, which is information related to a train whose delay time exceeds a predetermined time, from the operation information server 140, the ticket issuing server 130 updates the magnetic ticket encoded information D3 for users who plan to use the train related to the delayed train information D22 by adding information indicating that the train is eligible for a refund, and thereby determines in step S22-6 that a user who planned to use a train whose delay time exceeds a predetermined time is eligible for a refund. However, the reason for updating the magnetic ticket encoded information D3 to add information indicating that the train is eligible for a refund is not limited to train delays.

[0160] For example, in the event that a train becomes unable to operate (stopped), the ticket issuing server 130 may obtain information relating to such unable to operate (stopped) train from the operation information server 140 via the communication unit 133. Upon obtaining such information, the control unit 131 may search the ticket information storage unit 1322 to extract magnetic ticket encoded information D3 for plans to use such unable to operate (stopped) train from that point onwards, and update the extracted magnetic ticket encoded information D3 by adding information indicating that it is eligible for refund. As a result, in step S22-6, users who had planned to use the out-of-service (stopped) train are determined to be eligible for a refund.

[0161] In addition, the magnetic ticket encoded information D3 may be updated based on multiple factors, such as by adding information indicating that the ticket is eligible for refund in both cases of train delays and suspension of operation (stoppage).

[0162] [6 Change in the method for determining whether or not a refund is required] In the above operation, a case has been described in which in step S21-4 the magnetic ticket encoded information D3 is updated in advance to add information indicating that the ticket is eligible for refund, and in step S22-6 such magnetic ticket encoded information D3 is used to determine whether or not a refund is required. However, the method of determining whether or not a refund is required is not limited to this. Instead of updating the magnetic ticket encoded information D3 by adding information indicating that the ticket is eligible for refund before determining whether or not a refund is required, the ticket issuing server 130 may determine whether or not a refund is required based on information sent from the ticket gate device 150 to the ticket issuing server 130, and after determining whether or not a refund is required, the magnetic ticket encoded information D3 may be updated retroactively based on the determination result by adding information indicating that the ticket is eligible for refund.

[0163] For example, while using the delayed train information D22 obtained from the operation information server 140, without updating the magnetic ticket encoded information D3 in advance, in step S22-6, only if the abnormality setting information D24 received in step S22-3 is in the ``on'' state where the abnormality setting is on, a determination is made as to whether the magnetic ticket encoded information D3 corresponding to the two-dimensional code data D13 received in step S22-3 was planned to use the train related to the delayed train information D22, and if the train related to the delayed train information D22 was planned to be used, it is determined that a refund is required, and if the train related to the delayed train information D22 was not planned to be used, it is determined that a refund is not required.

[0164] Also, for example, the ticket issuing server 130 may determine whether or not a refund is required based on the difference between the standard arrival time and the actual time required. In other words, in this case, the memory unit 132 stores information related to the standard arrival time defined for each section (the average time required for a train running on each section to arrive at the destination station after departing from the departure station for that section) in advance, and when the control unit 131 receives information such as the two-dimensional code data D13 from the ticket gate device 150 in step S22-3, it calculates the actual time required from entry to exit using the ticket related to the two-dimensional code data D13 (the difference between the entry time from the ticket gate device 150 at the entry station and the exit time from the ticket gate device 150 at the exit station), and then calculates the difference between the information related to the standard arrival time required from the entry station to the exit station, which is included in the standard arrival time defined for each section, and the time actually required from entry at the entry station to exit at the exit station. If the calculated difference is greater than a predetermined time, it is determined that a refund is required, and if the calculated difference is within the predetermined time, it is determined that a refund is not required. In this case, it is possible to determine whether or not a refund is required without acquiring delayed train information D22 from the operation information server 140.

[0165] As described above, if there is no need to update the magnetic ticket encoded information D3 by adding information indicating that the ticket is eligible for a refund before determining whether or not a refund is required, the timing for updating the magnetic ticket encoded information D3 by adding information indicating that the ticket is eligible for a refund can be set to any point after the determination of whether or not a refund is required in step S22-6.

[0166] For example, between steps S23-1 and S23-2, the ticket reservation server 120 may instruct the ticket issuing server 130 to update the magnetic ticket encoded information D3, and after waiting for information relating to the instruction to be received by the communication unit 133, the ticket issuing server 130 may update the magnetic ticket encoded information D3 by adding information indicating that the ticket is eligible for refund, and then send a refund notification (step S23-2) and perform the refund process (step S23-4). [Explanation of symbols]

[0167] 100 Ticket information processing system (refund eligibility determination system) 110 Ticket information management server 120 Ticket reservation server (refund notification device) 130 Ticket issuing server (refund target determination device) 131 control unit (first extraction means, determination means, second extraction means, update means) 132 Storage unit (first storage means, second storage means, storage means) 1321 Ticket issuing program (refund eligibility determination program) 133 Communication Department (first acquisition means, second acquisition means, acquisition means) 150 Ticket gate equipment 152 Storage unit (third storage means) 153 Communication unit (first transmission means, second transmission means) 170 User terminal (terminal device) D3 Magnetic ticket encoding information (ticket content information, status information) D7 Ticket purchase information (status information) D9 Ticket reservation information (status information) D13 Two-dimensional code data (ticket memory information) D24 Abnormality setting information

Claims

1. a first acquiring means for acquiring ticket stored information which is information stored in a ticket used for boarding a train and which is read by a ticket gate device; a determination means for determining whether or not a refund is required for a user of the ticket for which the ticket storage information has been acquired; A second acquisition means for acquiring abnormality setting information which is information indicating whether a passenger who has passed through the ticket gate device is eligible for a refund, The abnormality setting information is information for turning on an abnormality setting based on delayed train information transmitted to the ticket gate device of a station at which a train for which the ticket is to be refunded stops, The refund eligibility determination device is characterized in that the judgment means uses the on / off status of the abnormality setting of the abnormality setting information acquired by the second acquisition means to determine whether or not a refund is necessary to the user of the ticket for which the ticket memory information has been acquired.

2. a first extraction means for extracting, from a first storage means in which the ticket storage information and ticket content information, which is information on the contents of the ticket including information on whether the ticket is eligible for refund, are stored in association with each other, the ticket content information corresponding to the ticket storage information acquired by the first acquisition means; The refund eligibility determination device of claim 1, characterized in that the judgment means determines whether or not a refund is required to the user of the ticket for which the ticket memory information has been acquired, using the ticket content information extracted by the first extraction means and the on / off status of the emergency setting information acquired by the second acquisition means.

3. A refund eligibility determination device as described in claim 1 or 2, characterized in that the ticket storage information is information stored on a ticket issued by a specified one-dimensional or two-dimensional code.

4. a second extraction means for extracting, from a second storage means in which the ticket storage information and status information relating to the status of the ticket are stored in association with each other, the status information corresponding to the ticket for which the ticket storage information has been acquired; an update means for updating the status information extracted by the second extraction means according to a result of the determination by the determination means; The refund item determination device according to claim 1 , further comprising:

5. The refund item determination device according to any one of claims 1 to 4, A ticket gate installed at a railway station, A refund eligibility determination system comprising:

6. The ticket gate device, A third storage means for storing the abnormality setting information; a first transmission means for transmitting the abnormality setting information stored in the third storage means to the refund eligibility determination device; a second transmission means for transmitting ticket storage information, which is information stored in a ticket used for boarding the train and read by the ticket gate device, to the refund eligibility determination device; The refund eligibility determination system according to claim 5, further comprising:

7. The refund eligibility determination system as described in claim 5 or 6, characterized in that it is further characterized by a refund eligibility notification device that sends a notification that a ticket that the refund eligibility determination device has determined to require a refund is eligible for a refund to a terminal device used by a user of the ticket.

8. Computer, a first acquiring means for acquiring ticket stored information which is information stored in a ticket used for boarding a train read by a ticket gate device; a determination means for determining whether or not a refund is required for the user of the ticket for which the ticket storage information has been acquired; a second acquisition means for acquiring abnormality setting information which is information indicating whether a passenger who has passed through the ticket gate device is eligible for a refund; The abnormality setting information is information for turning on an abnormality setting based on delayed train information transmitted to the ticket gate device of a station at which a train for which the ticket is to be refunded stops, A refund eligibility determination program characterized in that the judgment means uses the on / off status of the abnormality setting of the abnormality setting information acquired by the second acquisition means to determine whether or not a refund is necessary to the user of the ticket for which the ticket memory information has been acquired.

9. A method for determining whether a refund is to be made by a refund-eligible determination device, comprising: a first acquisition step of acquiring ticket stored information, which is information stored in a ticket used for boarding a train read by a ticket gate device; a determination step of determining whether or not a refund is required for the user of the ticket for which the ticket storage information has been acquired; A second acquisition step of acquiring abnormality setting information which is information indicating whether a passenger who has passed through the ticket gate device is eligible for a refund, The abnormality setting information is information for turning on an abnormality setting based on delayed train information transmitted to the ticket gate device of a station at which a train for which the ticket is to be refunded stops, A method for determining whether or not to issue a refund to a user of a ticket for which the ticket memory information has been acquired, characterized in that the judgment step uses the on / off status of the abnormality setting information acquired in the second acquisition step to determine whether or not to issue a refund to the user of the ticket for which the ticket memory information has been acquired.

Images