Server device, information processing system, information processing method, and information processing program

Abstract

To reduce the situation where entry / exit processing for a user cannot be executed at an automatic ticket gate even when there are multiple servers which store information on contents of a ticket used by the user.SOLUTION: A server device includes: first acquisition means (communication units 133, 233) for acquiring ticket content information D2; storage control means (control units 131, 231) for causing storage units 132, 232 to store the ticket content information D2; generation means (control units 131, 231) for generating two-dimensional code data D12 for each ticket content information D2; second acquisition means (communication units 133, 233) for acquiring two-dimensional code data D12 read at ticket gate devices 140, 240; and first specifying means (control units 131, 231) for specifying ticket issuing servers 130, 230 storing ticket content information D2 corresponding to the two-dimensional code data D12 acquired by the second acquisition means.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a server device, an information processing system, an information processing method, and an information processing program. [Background technology]

[0002] In recent years, it has become mainstream for train passengers at stations to automatically determine whether they can enter and exit the ticket gates using automatic ticket gates, and various systems have been developed to facilitate smooth processing by such automatic ticket gates (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6668112 Summary of the Invention [Problem to be solved by the invention]

[0004] Such processing related to a user's entry and exit through an automatic ticket gate can be performed independently by the automatic ticket gate by reading the information stored on the ticket, if the ticket held by the user contains all the information related to the contents of the ticket, such as information related to the areas that can be traveled using the ticket. In contrast, it is possible that the ticket held by the user does not contain all of the information related to the contents of the ticket, such as information regarding the areas that can be traveled using the ticket, and that all or part of this information is stored on the server.In this case, the automatic ticket gate will need to communicate with a designated server when performing processing related to the user's entry and exit.

[0005] If the server is configured to store all or part of the information related to the contents of tickets held by users, it is not realistic to have a single server store information related to the contents of tickets used in all areas and issued by all operators, so it is conceivable that there will be multiple servers with which the automatic ticket gates communicate, for example, divided by area or operator. In this case, the automatic ticket gate can only obtain data stored on the server with which it communicates, so if a user uses a ticket at an automatic ticket gate where information related to the ticket contents is stored on a server other than the one with which the automatic ticket gate communicates, there is a risk that the automatic ticket gate will not be able to process the user's entry and exit.

[0006] The objective of the present invention is to reduce the risk of automatic ticket gates being unable to process users' entry and exit even when information regarding the contents of tickets used by users is stored on a server and there are multiple such servers. [Means for solving the problem]

[0007] In order to solve the above problem, the invention described in claim 1 provides a server device, a first acquisition means for acquiring ticket content information, which is information relating to the content of a ticket used for transportation; a storage control means for storing the ticket content information in a first storage means; a creating means for creating ticket storage information, which is information to be stored on a ticket used for transportation, for each of the ticket content information stored in the first storage means; a second acquisition means for acquiring the ticket storage information read by the ticket gate device; a first identification means for identifying a server device in which the ticket content information corresponding to the ticket storage information acquired by the second acquisition means is stored; The present invention is characterized by comprising:

[0008] The invention described in claim 2 is the server device described in claim 1. a second storage means for storing server identification information that is information capable of identifying a server device in which the ticket content information is stored; The first identification means is characterized in that it uses the server identification information stored in the second storage means to identify the server device in which the ticket content information corresponding to the ticket storage information acquired by the second acquisition means is stored.

[0009] The invention described in claim 3 is the server device described in claim 1, the ticket storage information created by the creation means includes server identification information that is information that can identify a server device in which the ticket content information is stored, The first identification means is characterized in that it uses the server identification information included in the ticket storage information to identify the server device in which the ticket content information corresponding to the ticket storage information acquired by the second acquisition means is stored.

[0010] The invention described in claim 4 is the server device described in claim 3, providing means for providing ticket identification information, which is information that can identify the ticket content information, for each of the ticket content information stored in the first storage means; The ticket storage information created by the creating means further includes the ticket specifying information.

[0011] The invention described in claim 5 is the server device described in claim 4, The ticket storage information is encoded with only a portion of the information; the ticket-specific information is included in the encoded information; The server specific information is characterized in that it is included in unencoded information.

[0012] The invention described in claim 6 is the server device according to any one of claims 1 to 5, The ticket storage information has a plurality of storage areas, The one memory area includes first test information, which is information relating to the result of conversion or calculation performed according to a first conversion rule or calculation formula based on information included in the other memory area, and second test information, which is information relating to the result of predetermined conversion or calculation performed according to a second conversion rule or calculation formula based on information included in the other memory area, The first conversion rule or calculation formula is a conversion rule or calculation formula that is commonly used among a plurality of operators, and the second conversion rule or calculation formula is a conversion rule or calculation formula that is used individually for each operator.

[0013] The invention described in claim 7 is the server device according to any one of claims 1 to 6, The ticket storage device is characterized by comprising a first transmission control means for causing a transmission means to transmit the ticket storage information acquired by the second acquisition means to the server device identified by the first identification means.

[0014] The invention described in claim 8 is the server device described in claim 7, a third acquisition means for acquiring, from the server device identified by the first identification means, first determination result information, which is information relating to the determination result of whether or not the user holding the ticket is permitted to enter or exit at the ticket gate device, determined using the ticket content information corresponding to the ticket storage information; second transmission control means for causing a transmission means to transmit the first determination result information to the ticket gate device; The present invention is characterized by comprising:

[0015] The invention described in claim 9 is the server device described in claim 7, a fourth acquisition means for acquiring the ticket content information corresponding to the ticket storage information from the server device identified by the first identification means; a determination means for determining whether or not a user holding the ticket at the ticket gate device is permitted to enter or exit the ticket gate using the ticket content information acquired by the fourth acquisition means; a third transmission control means for causing a transmitting means to transmit second determination result information, which is information relating to the determination result by the determining means, to the ticket gate device; The present invention is characterized by comprising:

[0016] The invention described in claim 10 is the server device described in claim 7, a fourth acquisition means for acquiring the ticket content information corresponding to the ticket storage information from the server device identified by the first identification means; a fourth transmission control means for causing a transmission means to transmit the ticket content information acquired by the fourth acquisition means to the ticket gate device; The present invention is characterized by comprising:

[0017] The invention described in claim 11 is an information processing system, A server device according to any one of claims 1 to 10; a ticket gate device having a reading means for reading the ticket storage information; The present invention is characterized by comprising:

[0018] The invention described in claim 12 is an information processing system, A server device and a ticket gate device are provided. The server device a first acquisition means for acquiring ticket content information, which is information relating to the content of a ticket used for transportation; a storage control means for storing the ticket content information in a storage means; a generating means for generating ticket storage information, which is information to be stored on a ticket used for transportation, for each of the ticket content information stored in the storage means; Equipped with The ticket gate device reading means for reading the ticket storage information; a second identification means for identifying a server device in which the ticket content information corresponding to the ticket storage information read by the reading means is stored; The present invention is characterized by comprising:

[0019] The invention described in claim 13 is the information processing system described in claim 12, The ticket storage device is characterized by comprising a fifth transmission control means for causing a transmission means to transmit the ticket storage information read by the reading means to the server device identified by the second identification means.

[0020] The invention described in claim 14 is the information processing system described in claim 12, The method is characterized by comprising a sixth transmission control means for causing a transmission means to transmit the ticket storage information read by the reading means to a specified server device together with information indicating the server device identified by the second identification means.

[0021] The invention described in claim 15 is an information processing method, a first acquisition step of acquiring ticket content information, which is information relating to the content of a ticket used for using a transportation facility; a storage control step of storing the ticket content information in a storage means; a creating step of creating ticket storage information, which is information to be stored on a ticket used for transportation, for each of the ticket content information stored in the storage means; a second acquisition step of acquiring the ticket storage information read by the ticket gate device; a step of identifying a server device that stores the ticket content information corresponding to the ticket storage information acquired in the second acquisition step; The present invention is characterized by comprising:

[0022] The invention described in claim 16 is an information processing program, The computer of the server device, a first acquisition means for acquiring ticket content information, which is information relating to the content of a ticket used for using a transportation facility; a storage control means for storing the ticket content information in a storage means; a generating means for generating ticket storage information, which is information to be stored on a ticket used for transportation, for each of the ticket content information stored in the storage means; a second acquisition means for acquiring the ticket storage information read by the ticket gate device; a specifying means for specifying a server device in which the ticket content information corresponding to the ticket storage information acquired by the second acquiring means is stored; The present invention is characterized in that it functions as a [Effects of the Invention]

[0023] According to the present invention, information relating to the contents of the ticket used by the user is stored on a server, and even if there are multiple such servers, the risk of the automatic ticket gate being unable to perform processing related to the user's entry and exit can be reduced. [Brief explanation of the drawings]

[0024] [Figure 1] 1 is a block diagram showing an outline of the configuration of a ticket information processing system according to a first embodiment. [Figure 2] 2 is a block diagram showing the configuration of a ticket information management server in the ticket information processing system according to the first embodiment. FIG. [Figure 3] 1 is a block diagram showing the configuration of a ticket reservation server in the ticket information processing system according to the first embodiment. FIG. [Figure 4] 2 is a block diagram showing the configuration of a ticket issuing server in the ticket information processing system according to the first embodiment. FIG. [Figure 5] 1 is a block diagram showing the configuration of a ticket gate device in a ticket information processing system according to a first embodiment. [Figure 6] 1 is a block diagram showing the configuration of a ticket issuing device in the ticket information processing system according to the first embodiment. FIG. [Figure 7] 2 is a block diagram showing the configuration of a user terminal in the ticket information processing system according to the first embodiment. FIG. [Figure 8]3 is a flowchart showing an outline of the overall flow of the operation of the ticket information processing system according to the first embodiment. [Figure 9] 5 is a flowchart showing the operation of the ticket information processing system according to the first embodiment when issuing a ticket. [Figure 10] 5 is a flowchart showing the operation of the ticket information processing system according to the first embodiment when issuing a ticket. [Figure 11] 2 is a diagram showing the data structure of two-dimensional code data in the ticket information processing system according to the first embodiment. FIG. [Figure 12] 1 is a flowchart showing the operation of the ticket information processing system according to the first embodiment when entering or exiting a ticket gate (when entry or exit is determined in the first ticket information processing system). [Figure 13] 10 is a flowchart showing the operation of the ticket information processing system according to the first embodiment when entering or exiting through a ticket gate (when entry or exit is determined in the second ticket information processing system). [Figure 14] FIG. 10 is a block diagram showing an outline of the configuration of a ticket information processing system according to a second embodiment. [Figure 15] FIG. 10 is a block diagram showing the configuration of a ticket issuing server in the ticket information processing system according to the second embodiment. [Figure 16] FIG. 10 is a diagram showing an example of a list of issuing companies in the ticket information processing system according to the second embodiment. [Figure 17] FIG. 10 is a diagram showing an example of issuing server list information in the ticket information processing system according to the second embodiment. [Figure 18] FIG. 10 is a diagram showing the data structure of two-dimensional code data in the ticket information processing system according to the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0025] A first embodiment of the present invention (where the server identification information is included in the two-dimensional code data) and a second embodiment of the present invention (where the server identification information is stored in the ticket issuing server) will be described below with reference to Figures 1 to 18. However, the technical scope of the present invention is not limited to the illustrated examples.

[0026] [1st Embodiment] A first embodiment of the present invention (where server identification information is included in two-dimensional code data) will be described.

[0027] [1. Configuration Description] First, the configurations of the first ticket information processing system 100 and the second ticket information processing system 200 according to the first embodiment of the present invention will be described.

[0028] [(1) First Ticket Information Processing System] The first ticket information processing system 100 is a system for providing users of the system with tickets using a predetermined one-dimensional or two-dimensional code, and for assisting them in entering and exiting ticket gates using the tickets.As shown in FIG. 1, the system is configured with various servers managed by a specific railway operator (hereinafter referred to as "Railway Operator A") that manages and operates the first ticket information processing system 100, namely, a ticket information management server 110, a ticket reservation server 120, and a ticket issuing server 130, as well as a ticket gate device 140 and a ticket issuing device 150 installed at each station on the railway line operated by Railway Operator A, and a user terminal 160 carried by each user of the first ticket information processing system 100. As shown in FIG. 1, the devices are connected to each other via a communication network N.

[0029] The ticket gate device 140 and ticket issuing device 150 included in the first ticket information processing system 100 are installed at each station on the railway line operated by railway operator A, and are therefore installed within a specific area (hereinafter referred to as ``area X'') in which railway operator A operates the railway line.

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

[0031] [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 issuing tickets, such as operating train information D3 and reservation status information D4, and also generates ticket content information D2 and transmits it to other servers. As shown in FIG. 2, the ticket information management server 110 includes, for example, a control unit 111, a storage unit 112, and a communication unit 113.

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

[0033] The storage unit 112 is a part that stores various information required for the operation of the ticket information management server 110, and is configured, for example, by an HDD (Hard Disk Drive), semiconductor memory, etc. The data required for the operation of the ticket information management server 110, such as program data, is stored in a manner readable and writable by the control unit 111.

[0034] The storage unit 112 includes a ticket content information issuing program 1121, a running train information storage unit 1122 in which running train information D3 is stored, and a reservation status information storage unit 1123 in which reservation status information D4 is stored.

[0035] The ticket content information issuance program 1121 is a program that includes various commands 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 ticket content information issuance program 1121. The information stored in each storage unit will be described in detail in the explanation of the operation.

[0036] 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 150, 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.

[0037] The ticket information management server 110 cooperates with the ticket information management server 210 related to the second ticket information processing system 200, and has information relating to railway lines operated by railway operator B, which manages and operates the second ticket information processing system 200 described below, as running train information D3 and reservation status information D4, and is configured to be able to generate information relating to tickets whose boarding or disembarking station is a station on a railway line operated by railway operator B (a station located within area Y described below, a station where the ticket gate device 240 and ticket issuing device 250 related to the second ticket information processing system 200 are installed), as ticket content information D2.

[0038] [Ticket reservation server] The ticket reservation server 120 is, for example, an information device such as a PC or a WS, and, as will be described later, acquires information relating to tickets that users wish to purchase from the user terminal 160. As shown in FIG. 3, the ticket reservation server 120 is configured to include, for example, a control unit 121, a storage unit 122, and a communication unit 123, similar to the ticket information management server 110.

[0039] 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 storage unit 122 is configured with, for example, a HDD (Hard Disk Drive), a semiconductor memory, etc., similar to the storage unit 112 in the ticket information management server 110, and stores a ticket reservation program. The system is equipped with a RAM 1221 and a ticket information storage unit 1222 that stores ticket content information D2, ticket purchase information D6, ticket reservation information D8, ticket number information D11, and two-dimensional code available time information D14.

[0040] The ticket reservation program 1221 is a program that includes various instructions to the control unit 121 for operating the ticket reservation server 120, and the operation of the ticket reservation server 120 described in the operation explanation below 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.

[0041] 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 160 via a communication network N by a communication unit 123, and is capable of sending and receiving data between the ticket information management server 110, the ticket issuing server 130, and the user terminal 160.

[0042] [C Ticket issuing server] The ticket issuing server 130 is, for example, an information device such as a PC or a WS, and generates data relating to a two-dimensional code used as a ticket, as will be described later. As shown in FIG. 4, the ticket issuing server 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.

[0043] 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 is configured with, for example, a hard disk drive (HDD), a semiconductor memory, etc., similar to the memory unit 112 in the ticket information management server 110, and stores a ticket issuing program. The device is equipped with a RAM 1321, a ticket information storage unit 1322 in which ticket content information D2, ticket purchase information D6, ticket identifier information D10, ticket number information D11, and two-dimensional code usable time information D14 are stored, an encoded information storage unit 1323 in which encoded information D16 is stored, a test processing information storage unit 1324 in which common test processing information D18A and individual test processing information D18B are stored, and a specific information storage unit 1325 in which issuing server specific information D15 and issuing business operator specific information D27 are stored.

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

[0045] In addition, as shown in Figure 1, the ticket issuing server 130 is connected to the ticket information management server 110, the ticket reservation server 120, the ticket gate device 140, and the ticket issuing device 150 via a communication network N by a communication unit 133, and is capable of sending and receiving data between the ticket information management server 110, the ticket reservation server 120, the ticket gate device 140, and the ticket issuing device 150.

[0046] [D. Ticket gate device] The ticket gate device 140 is a device installed at each station on a railway line that automatically performs ticket gate operations such as determining whether or not a person can enter or exit the ticket gate, and as described below, opens and closes the opening / closing section 145 depending on whether or not a user holding a ticket can enter or exit the ticket gate. As shown in Figure 5, the ticket gate device 140 is similar to the ticket information management server 110, and is configured to include, for example, a control unit 141, a memory unit 142, and a communication unit 143, as well as a ticket information reading unit 144 and an opening / closing unit 145.

[0047] 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 is configured with, for example, an HDD (Hard Disk Drive), a semiconductor memory, etc., similar to the memory unit 112 in the ticket information management server 110, and stores an entrance / exit processing program. The test processing information storage unit 1421 stores common test processing information D18A, and an equipment information storage unit 1423 stores ticket gate device installation station information D21 and ticket gate device equipment information D22.

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

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

[0050] The ticket information reading unit 144 is a part for reading the stored contents of a ticket issued using a predetermined one-dimensional or two-dimensional code, as described below, i.e., a ticket printed on a predetermined medium such as paper by the ticket issuing device 150 or ticket issuing device 250 and issued, or a ticket displayed on the user terminal 160, 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 144, it reads the stored contents of the ticket.

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

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

[0053] [Ticket issuing device] The ticket issuing device 150 is a device installed at each station on a railway line and used by users when purchasing tickets to board trains. In this embodiment, as described below, the ticket issuing device 150 is used when issuing tickets with a specified one-dimensional or two-dimensional code on a specified medium such as paper. As shown in FIG. 6, the ticket issuing device 150 is configured to include, for example, a control unit 151, a memory unit 152, and a communication unit 153, similar to the ticket information management server 110, and further includes a display unit 154, an operation unit 155, and a ticket issuing unit 156.

[0054] 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 storage unit 152 is configured with, for example, a hard disk drive (HDD), a semiconductor memory, etc., similar to the storage unit 112 in the ticket information management server 110, and stores ticket content information. The system includes a running program 1521, a running train information storage unit 1522 in which running train information D3 is stored, and a reservation status information storage unit 1523 in which reservation status information D4 is stored.

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

[0056] In addition, as shown in FIG. 1, the ticket issuing device 150 is connected to the ticket information management server 110 and the ticket issuing server 130 via a communication network N by a communication unit 153, and is capable of sending and receiving data between the ticket information management server 110 and the ticket issuing server 130.

[0057] The display unit 154 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 151 on a display screen.

[0058] The operation unit 155 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 150 and outputs an operation signal corresponding to the operation input to the control unit 151. The operation unit 155 may be, for example, a touch panel formed integrally with the display unit 154, 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 150.

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

[0060] [User terminal] The user terminal 160 is an information device such as a smartphone or tablet terminal carried by each user who receives tickets using this system, and is used when entering or exiting the ticket gate device 140 using a ticket issued using a specified one-dimensional or two-dimensional code, as described below. As shown in FIG. 7, the user terminal 160 is configured to include, for example, a control unit 161, a memory unit 162, a communication unit 163, a display unit 164, and an operation unit 165, similar to the ticket issuing device 150.

[0061] The control unit 161, communication unit 163, display unit 164, and operation unit 165 are configured in the same manner as the control unit 151, communication unit 153, display unit 154, and operation unit 155 in the ticket issuing device 150, respectively. The storage unit 162 is configured with, for example, a hard disk drive (HDD), a semiconductor memory, etc., similar to the storage unit 152 in the ticket issuing device 150, and stores the application for the user terminal. The information storage unit 1621 stores two-dimensional code image data D19, ticket number information D11, and ticket reservation information D8.

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

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

[0064] [G Communication Network] The communication network N is, for example, the Internet, a telephone line network, a mobile phone communication network, a wireless LAN communication network, etc., and connects the devices that make up the first 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.

[0065] [(2) Second Ticket Information Processing System] Similar to the first ticket information processing system 100, the second ticket information processing system 200 is a system for providing users of the system with tickets using a predetermined one-dimensional or two-dimensional code, and for assisting them in entering and exiting ticket gates using the tickets. As shown in FIG. 1, the second ticket information processing system 200 is configured with various servers managed by a specific railway operator (hereinafter referred to as "railway operator B") that manages and operates the second ticket information processing system 200, namely, a ticket information management server 210, a ticket reservation server 220, and a ticket issuing server 230, as well as a ticket gate device 240 and a ticket issuing device 250 installed at each station on the railway line operated by railway operator B, and a user terminal 260 carried by each user of the second ticket information processing system 200. 1, the devices are connected to each other via a communication network N. The ticket issuing server 230 of the second ticket information processing system 200 is connected to the ticket issuing server 130 of the first ticket information processing system 100 via the communication network N.

[0066] The ticket gate device 240 and ticket issuing device 250 included in the second ticket information processing system 200 are installed at each station on the railway line operated by railway operator B, and are therefore installed within a specific area (hereinafter referred to as "Area Y") in which railway operator B operates the railway line.

[0067] As shown in Figures 2 to 7, the configuration of each device that constitutes the second ticket information processing system 200 is similar to the configuration of each device that constitutes the first ticket information processing system 100 (the configuration of the ticket information management server 210 is similar to the ticket information management server 110 of the first ticket information processing system 100, the configuration of the ticket reservation server 220 is similar to the ticket reservation server 120 of the first ticket information processing system 100, the configuration of the ticket issuing server 230 is similar to the ticket issuing server 130 of the first ticket information processing system 100, the configuration of the ticket gate device 240 is similar to the ticket gate device 140 of the first ticket information processing system 100, the configuration of the ticket issuing device 250 is similar to the ticket issuing device 150 of the first ticket information processing system 100, and the configuration of the user terminal 260 is similar to the user terminal 160 of the first ticket information processing system 100), so detailed explanations will be omitted.

[0068] However, the conversion rules or calculation formulas stored as individual testing processing information D18B in the testing processing information memory unit 2324 of the memory unit 232 of the ticket issuing server 230 are different from the conversion rules or calculation formulas stored as individual testing processing information D18B in the testing processing information memory unit 1324 of the memory unit 132 of the ticket issuing server 130 of the first ticket information processing system 100.

[0069] Furthermore, the content of the encoded information D16 stored in the encoded information storage unit 2323 of the storage unit 232 of the ticket issuing server 230 is different from the content of the encoded information D16 stored in the encoded information storage unit 1323 of the storage unit 132 of the ticket issuing server 130 of the first ticket information processing system 100. As a result, the first ticket information processing system 100 and the second ticket information processing system 200 generate two-dimensional codes in different formats, making it impossible for each system to decode the two-dimensional codes generated by the other system.

[0070] It should be noted that the railway operator A that manages and operates the first ticket information processing system 100 and the railway operator B that manages and operates the second ticket information processing system 200 do not necessarily have to be separate operators, and the same railway operator may manage and operate multiple systems. Furthermore, the area X where the ticket gate device 140 and the ticket issuing device 150 included in the first ticket information processing system 100 are installed and the area Y where the ticket gate device 240 and the ticket issuing device 250 included in the second ticket information processing system 200 are installed do not necessarily have to be separate areas, and multiple systems may be managed and operated in the same area or in partially overlapping areas.

[0071] [2 Operation Description] The following describes the operation of the first ticket information processing system 100 and the second ticket information processing system 200 according to this embodiment when in use. As shown in the flowchart of Fig. 8, the operation of the first ticket information processing system 100 and the second ticket information processing system 200 is roughly divided into two steps: step S1 (issuing a ticket) and step S2 (entering and exiting the ticket gate).

[0072] [(1) Step S1: Issuing a ticket] First, the operation of this system when issuing a ticket to a user for use in boarding a train will be explained in accordance with the flowcharts of Figures 9 and 10, taking as an example a case where a ticket is issued to a user terminal 160 by data in the first ticket information processing system 100.

[0073] When a user of the first ticket information processing system 100 wishes to use this system to receive a ticket for use on a train, the user first uses the operation unit 165 of the user terminal 160 to input information about the ticket they wish to reserve, i.e., the desired ticket purchase information D1, which includes information about the train's boarding station, disembarking station, departure time, arrival time, seat number, etc. (step S1-1). Once the desired ticket purchase information D1 has been input, the control unit 161 transmits the input information from the communication unit 163 to the ticket reservation server 120 via the communication network N (step S1-2). Here, it is assumed that either the boarding station or the disembarking station is not a station on a railway line operated by railway operator A (a station located within area X, a station where the ticket gate device 140 and ticket issuing device 150 related to the first ticket information processing system 100 are installed), but a station on a railway line operated by railway operator B (a station located within area Y, a station where the ticket gate device 240 and ticket issuing device 250 related to the second ticket information processing system 200 are installed).

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

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

[0076] In the ticket information management server 110, when the communication unit 113 receives the desired ticket purchase information D1 and a request to send ticket content information D2, the control unit 111 checks the train's seat availability based on the running train information D3 stored in the running train information storage unit 1122 and the reservation status information D4 stored in the reservation status information storage 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 ticket content information D2 (step S1-4).

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

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

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

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

[0081] In the ticket reservation server 120, when the communication unit 123 receives the ticket content information D2 and the purchase result information D5, the control unit 121 transmits the purchase result information D5 from the communication unit 123 via the communication network N to the user terminal 160 that transmitted the desired ticket purchase information D1 in step S1-2 (step S1-6), and in the user terminal 160 that receives this via the communication unit 163, the control unit 161 displays the ticket purchase result on the display unit 164 based on the received data (step S1-7).

[0082] Once the ticket reservation server 120 has completed sending the purchase result information D5 to the user terminal 160, it then generates ticket purchase information D6 and ticket reservation information D8 relating to the ticket purchased by the user, links these to the ticket content information D2, and stores them in the ticket information storage unit 1222 of the storage unit 122 (step S1-8).

[0083] Ticket purchase information D6 is information for linking together information related to an issued ticket, such as ticket content information D2, purchase result information D5, and ticket reservation information D8, including ticket purchase number information D7, which is information related to the purchase number assigned to each ticket. Ticket purchase information D6 also includes information related to the content of the ticket corresponding to the desired ticket purchase information D1, and information related to the ticket status, similar to that included in ticket content information D2.

[0084] Ticket reservation information D8 is data relating to the specific reservation details made by the user for the reserved ticket, which is managed by ticket reservation server 120. Ticket reservation information D8 also includes information relating to the contents of the ticket corresponding to desired ticket purchase information D1, similar to that included in ticket content information D2, and information relating to the status of the ticket.

[0085] In the ticket reservation server 120, once the above data is generated, the control unit 121 transmits the ticket content information D2 and ticket purchase information D6 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 ticket content information D2 and ticket purchase information D6 and stores them in the ticket information memory unit 1322 of the memory unit 132 (step S1-10).

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

[0087] 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 165 of the user terminal 160 to input predetermined information (ticket issuance request information D9) requesting the issuance of a ticket with a two-dimensional code (step S1-11).When the ticket issuance request information D9 has been input, the control unit 161 of the user terminal 160 transmits the input information from the communication unit 163 to the ticket reservation server 120 via the communication network N (step S1-12).

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

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

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

[0091] Next, the control unit 131 uses the ticket purchase information D6 and the generated ticket identifier information D10 to create two-dimensional code data D12 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.

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

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

[0094] The two-dimensional code data D12 has multiple storage areas, for example, a basic information section D12-1 and a validity verification section D12-2 as shown in Fig. 11, and only a portion of the information in the basic information section D12-1 is encoded using encoding information D16 stored in an encoding information storage section 1323 of the storage unit 132. The encoding information D16 is data relating to a predetermined conversion rule that the ticket issuing server 130 uses when encoding the two-dimensional code data D12.

[0095] Of these, the basic information section D12-1 includes, in addition to attribute information related to the issuance date and the like, ticket identifier information D10 generated in step S1-14, issuing server specific information D15, and issuer specific information D27. Note that the ticket identifier information D10 is included in the information encoded using the encoding information D16, while the issuing server specific information D15 and issuer specific information D27 are included in the information not encoded using the encoding information D16.

[0096] The issuing server identification information D15 is information that can identify the ticket issuing server 130 that created the two-dimensional code data D12, such as an identifier assigned to the ticket issuing server 130. Note that the issuing server identification information D15 does not have to directly identify the ticket issuing server 130. For example, if the ticket issuing server 130 and the area (area X) in which the ticket gate device 140 and the ticket issuing device 150 under its jurisdiction are installed have a one-to-one correspondence, as in the present embodiment, the issuing server identification information D15 may be information that can identify the ticket issuing server 130 by storing information about such an area. Also, if the ticket issuing server 130 and the railway operator (railway operator A) that manages it have a one-to-one correspondence, the issuing server identification information D15 may be information that can identify the ticket issuing server 130 by storing information about such a railway operator.

[0097] The issuing company identification information D27 is information that can identify the company that issued the two-dimensional code data D12 (in this embodiment, railway company A that manages and operates the first ticket information processing system 100 including the ticket issuing server 130 that created the two-dimensional code data D12), such as an identifier assigned to each railway company.

[0098] Since the issuing server specific information D15 and the issuing business specific information D27 are stored in advance in the specific information storage unit 1325 of the storage unit 132, the control unit 131 simply reads out the information stored in the specific information storage unit 1325 of the storage unit 132 and assigns it directly to the two-dimensional code data D12.

[0099] The validity verification section D12-2 includes basic verification information D17A and individual verification information D17B. The basic testing information D17A is generated by inputting the data contained in the basic information section D12-1 into common testing processing information D18A, which is a predetermined conversion rule or calculation formula that is common to the first ticket information processing system 100 and the second ticket information processing system 200, i.e., is used commonly by railway operator A and railway operator B. In addition, the individual testing information D17B is generated by inputting the data contained in the basic information section D12-1 into individual testing processing information D18B, which is a predetermined conversion rule or calculation formula that differs between the first ticket information processing system 100 and the second ticket information processing system 200, i.e., is used individually by railway operator A and railway operator B.

[0100] Once the two-dimensional code data D12 is generated, the control unit 131 of the ticket issuing server 130 transmits the generated two-dimensional code data D12 together with the corresponding ticket number information D11 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 D14 in step S1-15, it also transmits the two-dimensional code usage time information D14, together with the ticket number information D11 and the two-dimensional code data D12, from the communication unit 133 via the communication network N to the ticket reservation server 120.

[0101] 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 D11 in the ticket information storage unit 1222 of the storage unit 122 in association with the corresponding ticket content information D2, ticket purchase information D6, and ticket reservation information D8, and then generates two-dimensional code image data D19, which is data converted from the received two-dimensional code data D12 into image data, based on the received two-dimensional code data D12 (step S1-17). In addition, when two-dimensional code usage time information D14 is received from the ticket issuing server 130, the control unit 121 also stores the two-dimensional code usage time information D14 in the ticket information storage unit 1222 of the storage unit 122, linking it to the corresponding ticket content information D2, ticket purchase information D6, ticket reservation information D8, and ticket number information D11.

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

[0103] Also, when the above transmission process is completed, in the ticket reservation server 120, the control unit 121 updates the information related to the status of the ticket, which is stored in the ticket information storage unit 1222 of the storage unit 122 and is included in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8, to information indicating that a two-dimensional code has been issued (step S1-19), and transmits the two-dimensional code issuance status update information D20, which is information related 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 related to the status of the ticket, which is stored in the ticket information storage unit 1322 of the storage unit 132 and is included in the ticket content information D2 and ticket purchase information D6, to information indicating that a two-dimensional code has been issued (step S1-21).

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

[0105] In the user terminal 160, when the communication unit 163 receives the two-dimensional code image data D19, ticket number information D11, and ticket reservation information D8, the control unit 161 links the received data and stores them in the ticket information storage unit 1622 of the storage unit 162 (step S1-22). This makes it possible for the user terminal 160 to display on the display unit 164 an image of the two-dimensional code related to the two-dimensional code image data D19 stored in the ticket information memory unit 1622 of the memory unit 162 and the ticket number related to the ticket number information D11.

[0106] 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 D12 from the communication unit 123 to the user terminal 160 via the communication network N instead of the two-dimensional code image data D19, and upon receiving this, the control unit 161 may generate the two-dimensional code image data D19 in accordance with the user terminal application 1621, thereby acquiring the two-dimensional code image data D19.

[0107] [(2) Step S2: Entering and Exiting the Ticket Gate] Next, the operation of this system when a user uses the two-dimensional code issued by the first ticket information processing system 100 in step S1 to enter or exit a ticket gate at the ticket gate device 240 related to the second ticket information processing system 200 will be explained separately for cases where the decision on whether to allow entry or exit is made by the first ticket information processing system 100 that issued the two-dimensional code, and by the second ticket information processing system 200 where the two-dimensional code is used in the ticket gate device.

[0108] [Step S21: When entry / exit determination is made in the first ticket information processing system] First, the operation of the first ticket information processing system 100 and the second ticket information processing system 200 when entry / exit determination is made in the ticket issuing server 130 of the first ticket information processing system 100 will be described with reference to the flowchart of FIG.

[0109] If the user wishes to enter the station ticket gate through the ticket gate device 240 associated with the second ticket information processing system 200 before boarding the train, or if the user wishes to exit the station ticket gate through the ticket gate device 240 associated with the second ticket information processing system 200 after boarding the train, the user holds the two-dimensional code issued in step S1 over the ticket information reading unit 244 of the ticket gate device 240. Specifically, the user performs a predetermined operation using the operation unit 165 of the user terminal 160 to display the two-dimensional code related to the two-dimensional code image data D19 on the display unit 164, and then holds the displayed two-dimensional code over the ticket information reading unit 244.

[0110] When the two-dimensional code is held over the ticket information reading unit 244, the control unit 241 of the ticket gate device 240 causes the ticket information reading unit 244 to read two-dimensional code data D12 from the held two-dimensional code (step S21-1).

[0111] When the two-dimensional code data D12 is read by the ticket information reading unit 244, the control unit 241 identifies the railway operator that issued the two-dimensional code data D12 based on the issuer identification information D27 included in the basic information unit D12-1 (step S21-2). Here, railway operator A, which manages and operates the first ticket information processing system 100 including the ticket issuing server 130 that created the two-dimensional code data D12, is identified as the railway operator that issued the two-dimensional code data D12.

[0112] Next, the control unit 241 determines whether the two-dimensional code held over the ticket information reading unit 244 is a genuine ticket (step S21-3). That is, as explained in step S1, the two-dimensional code data D12 is composed of multiple memory areas, for example, as shown in FIG. 11, a basic information section D12-1 and a validity testing section D12-2, and the validity testing section D12-2 includes basic testing information D17A, which is information related to the results of a predetermined testing conversion or calculation based on the data included in the basic information section D12-1, in accordance with common testing processing information D18A, which is a predetermined conversion rule or calculation formula common to the first ticket information processing system 100 and the second ticket information processing system 200.

[0113] In addition, in the ticket gate device 240, a similar predetermined conversion rule or calculation formula is stored in the test processing information storage unit 2422 of the storage unit 242 as common test processing information D18A.

[0114] Therefore, the control unit 241 performs a predetermined conversion or calculation for testing based on the data contained in the basic information section D12-1 of the two-dimensional code data D12 read in step S21-1, in accordance with the above-mentioned predetermined conversion rule or calculation formula stored as common testing processing information D18A in the testing processing information storage section 2422 of the storage unit 242. Then, if the result of the above conversion or calculation matches the basic testing information D17A included in the validity testing unit D12-2, the control unit 241 determines that the two-dimensional code is related to a genuine ticket, and if they do not match, it determines that the two-dimensional code is not related to a genuine ticket.

[0115] If it is determined in step S21-3 that the two-dimensional code data D12 relates to a genuine ticket, the control unit 241 in the ticket gate device 240 transmits the two-dimensional code data D12 read by the ticket information reading unit 244, together with the ticket gate device installation station information D21 and the ticket gate device equipment information D22 stored in the equipment information storage unit 2423 of the storage unit 242, from the communication unit 243 via the communication network N to the ticket issuing server 230 (step S21-4). If it is determined in step S21-3 that the ticket is an unauthorized ticket, the control unit 241 closes the opening / closing unit 245 and ends the process.

[0116] The ticket gate installation station information D21 is information relating to the station where the ticket gate 240 is installed, and indicates the station where a user who holds the two-dimensional code over the ticket information reading unit 244 enters or exits through the ticket gate. The ticket gate device equipment information D22 is information related to the ticket gate device 240, and includes information indicating the operator that installed it (railway operator B), information related to detailed settings such as fraud detection that each ticket gate device 240 has, and the like.

[0117] In the ticket issuing server 230, which receives the information transmitted from the ticket gate device 240 via the communication unit 233, the control unit 231 identifies the ticket issuing server that created the two-dimensional code data D12 based on the issuing server identification information D15 contained in the basic information section D12-1 of the two-dimensional code data D12 that has not been encoded using the encoding information D16 (step S21-5).

[0118] As explained in step S1, the ticket issuing server that created the two-dimensional code data D12 stores information related to the contents of the ticket corresponding to the two-dimensional code data D12 (ticket content information D2 and ticket purchase information D6). Therefore, by identifying the ticket issuing server that created the two-dimensional code data D12 based on the issuing server identification information D15 included in the basic information section D12-1 of the two-dimensional code data D12, it is possible to identify the ticket issuing server that stores the information related to the contents of the ticket corresponding to the two-dimensional code data D12 (ticket content information D2 and ticket purchase information D6).

[0119] As described above, in this embodiment, the two-dimensional code data D12 is created by the ticket issuing server 130 of the first ticket information processing system 100, and therefore the control unit 231 identifies that the two-dimensional code data D12 was created by the ticket issuing server 130 of the first ticket information processing system 100.

[0120] Next, the control unit 231 transmits the two-dimensional code data D12, ticket gate installation station information D21, and ticket gate equipment information D22 received in step S21-4 from the communication unit 233 via the communication network N to the ticket issuing server (ticket issuing server 130) that created the two-dimensional code data D12 identified in step S21-5 (step S21-6).

[0121] Unlike this embodiment, if the control unit 231 determines in step S21-5 that the ticket issuing server that created the two-dimensional code data D12 is itself (ticket issuing server 230), it will not go through the processes from step S21-6 to step S21-11, but will instead perform individual testing, decode the two-dimensional code data, determine whether entry or exit is permitted, and update the status information in the same manner as described in steps S21-7 to S21-10, and then proceed to step S21-12.

[0122] In the ticket issuing server 130 of the first ticket information processing system 100, when the communication unit 133 receives information transmitted from the ticket issuing server 230 of the second ticket information processing system 200, the control unit 131 first determines whether the received two-dimensional code data D12 relates to a genuine ticket (step S21-7).

[0123] That is, as explained in step S1, the two-dimensional code data D12 is composed of multiple memory areas, for example, as shown in FIG. 11, a basic information section D12-1 and a validity verification section D12-2, and the validity verification section D12-2 includes individual verification information D17B, which is information related to the results of a predetermined verification conversion or calculation based on the data included in the basic information section D12-1, in accordance with individual verification processing information D18B, which is a predetermined conversion rule or calculation formula that differs between the first ticket information processing system 100 and the second ticket information processing system 200.

[0124] In addition, in this case, since the two-dimensional code data D12 is created in the ticket issuing server 130 of the first ticket information processing system 100, the predetermined conversion rule or calculation formula stored as individual testing processing information D18B in the testing processing information storage unit 1324 of the storage unit 132 is the same as that used when the two-dimensional code data D12 was created.

[0125] Therefore, the control unit 131 performs a predetermined conversion or calculation for testing based on the data contained in the basic information section D12-1 of the two-dimensional code data D12 received in step S21-6, in accordance with a predetermined conversion rule or calculation formula stored as individual testing processing information D18B in the testing processing information storage section 1324 of the storage unit 132. Then, if the result of the above conversion or calculation matches the individual testing information D17B contained in the validity testing unit D12-2, the control unit 131 determines that the two-dimensional code relates to a genuine ticket, and if they do not match, it determines that the two-dimensional code does not relate to a genuine ticket.

[0126] If it is determined in step S21-7 that the two-dimensional code data D12 relates to a genuine ticket, the control unit 131 then uses the encoding information D16 stored in the encoding information memory unit 1323 of the memory unit 132 to decode the encoded information in the basic information section D12-1 of the two-dimensional code data D12 (step S21-8).

[0127] If it is determined in step S21-7 that the ticket is an unauthorized ticket, the control unit 131 transmits the determination result that the ticket is unauthorized from the communication unit 133 via the communication network N to the ticket issuing server 230 of the second ticket information processing system 200. Upon receiving this, the control unit 231 of the ticket issuing server 230 of the second ticket information processing system 200 transmits a predetermined command to close the opening / closing unit 245 of the ticket gate device 240 from the communication unit 233 via the communication network N to the ticket gate device 240, and ends the process.

[0128] After decoding the encoded information in the basic information section D12-1 of the two-dimensional code data D12, the control unit 131 then searches the ticket information storage section 1322 of the storage unit 132 based on the ticket identifier information D10 contained in the decoded information, extracts the ticket content information D2 and ticket purchase information D6 corresponding to the received two-dimensional code data D12, and compares the received ticket gate device installation station information D21 and ticket gate device equipment information D22 with the ticket content information D2 to determine whether entry or exit is permitted (step S21-9). If the ticket content information D2 and ticket purchase information D6 corresponding to the received two-dimensional code data D12 are not extracted, the control unit 131 determines that entry or exit is not possible at that time. Therefore, the process proceeds to comparing the ticket content information D2 with the ticket gate device installation station information D21 and the ticket gate device information D22 as described above only when the ticket content information D2 and ticket purchase information D6 corresponding to the received two-dimensional code data D12 are extracted.

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

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

[0131] In addition, if two-dimensional code usage time information D14 corresponding to the received two-dimensional code data D12 is stored in the ticket information storage unit 1322 of the storage unit 132, the control unit 131 also determines whether the two-dimensional code corresponding to the received two-dimensional code data D12 is within the usage time before extracting the ticket content information D2 and the ticket purchase information D6. Specifically, the ticket information storage unit 1322 of the storage unit 132 is searched based on the ticket identifier information D10, and the two-dimensional code usage time information D14 corresponding to the received two-dimensional code data D12 is extracted. After that, for example, the time at which the two-dimensional code data D12 was created, which is included in the two-dimensional code usage time information D14, 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 D14, 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 D14, 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 hours are within the period of use, will it extract the ticket content information D2 and ticket purchase information D6 corresponding to the received two-dimensional code data D12 and determine whether entry or exit is possible by comparing the ticket gate installation station information D21 and ticket gate equipment information D22 with the ticket content information D2.If it determines that the available hours are outside the period of use, the control unit 131 will determine that entry or exit is not possible at that time.

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

[0133] Once the above update is complete, the control unit 131 transmits information relating to the result of the ticket gate entry / exit judgment in step S21-9 (first entry / exit judgment result information D23) from the communication unit 133 via the communication network N to the ticket issuing server 230 of the second ticket information processing system 200 (step S21-11).

[0134] In the ticket issuing server 230 of the second ticket information processing system 200, which receives the first entry / exit judgment result information D23 transmitted from the ticket issuing server 130 of the first ticket information processing system 100 via the communication unit 233, the control unit 231 transmits the information from the communication unit 233 via the communication network N to the ticket gate device 240 that transmitted the two-dimensional code data D12, etc. in step S21-4 (step S21-12).

[0135] In the ticket gate device 240, which receives the first entry / exit judgment result information D23 sent from the ticket issuing server 230 via the communication unit 243, the control unit 241 opens and closes the opening / closing section 245 based on the received first entry / exit judgment result information D23 (step S21-13). Specifically, if the received first entry / exit judgment result information D23 allows entry or exit, the opening / closing section 245 will be set to the open state, and if the received first entry / exit judgment result information D23 does not allow entry or exit, the opening / closing section 245 will be set to the closed state.

[0136] In the ticket issuing server 130 of the first ticket information processing system 100, after transmitting the first entry / exit judgment result information D23 to the ticket issuing server 230 of the second ticket information processing system 200, information regarding the update contents of the information related to the ticket status contained in the ticket content information D2 and the ticket purchase information D6 in step S21-10 (first entry / exit status update information D24) is transmitted from the communication unit 133 to the ticket reservation server 120 via the communication network N (step S21-14).

[0137] In the ticket reservation server 120 of the first ticket information processing system 100, when the communication unit 123 receives the first entry / exit status update information D24, the control unit 121 updates the information related to the ticket status contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 stored in the ticket information memory unit 1222 of the memory unit 122 in the same manner as the update in the ticket issuing server 130 in step S21-10 (step S21-15).

[0138] [Step S22: When entry / exit determination is made in the second ticket information processing system] Next, the operation of the first ticket information processing system 100 and the second ticket information processing system 200 when entry / exit determination is made in the ticket issuing server 230 of the second ticket information processing system 200 will be described with reference to the flowchart of FIG.

[0139] First, the process from reading the two-dimensional code data (step S22-1) to decoding the two-dimensional code data (step S22-8) is no different from the process from reading the two-dimensional code data (step S21-1) to decoding the two-dimensional code data (step S21-8) when entry / exit determination is made in the first ticket information processing system (step S21).

[0140] In the ticket issuing server 130 of the first ticket information processing system 100, the encoded information in the basic information section D12-1 of the two-dimensional code data D12 received from the ticket issuing server 230 of the second ticket information processing system 200 is decoded.The control unit 131 then searches the ticket information storage section 1322 of the storage unit 132 based on the ticket identifier information D10 contained in the decoded information, and extracts the ticket content information D2 and ticket purchase information D6 corresponding to the received two-dimensional code data D12 (step S22-9).

[0141] Next, the control unit 131 transmits the ticket content information D2 extracted in step S22-9 from the communication unit 133 via the communication network N to the ticket issuing server 230 of the second ticket information processing system 200 (step S22-10). In addition, if in step S22-9, the ticket content information D2 and ticket purchase information D6 corresponding to the received two-dimensional code data D12 are not extracted, the control unit 131 will send information to the ticket issuing server 230 of the second ticket information processing system 200 that the ticket content information D2 and ticket purchase information D6 corresponding to the received two-dimensional code data D12 were not extracted.

[0142] In the ticket issuing server 230 of the second ticket information processing system 200, when the communication unit 233 receives the ticket content information D2 transmitted from the ticket issuing server 130 of the first ticket information processing system 100, the control unit 231 makes a determination as to whether entry or exit is permitted (step S22-11).

[0143] Specifically, first, if the ticket content information D2 is not received and information is received to the effect that it has not been extracted, it is determined at that point that entry or exit is not possible. When the ticket content information D2 is received, the ticket gate station information D21 and ticket gate device information D22 received in step S22-4 are compared with the ticket content information D2 received in step S22-10 to determine whether entry or exit is permitted. The specific method of determination at this time is the same as that explained in step S21-9.

[0144] In addition, if two-dimensional code usable time information D14 corresponding to the two-dimensional code data D12 is stored in the ticket information memory unit 1322 of the memory unit 132 of the ticket issuing server 130 of the first ticket information processing system 100, the control unit 131 of the ticket issuing server 130 will also transmit the two-dimensional code usable time information D14 along with the ticket content information D2 in step S22-10, and the ticket issuing server 230 of the second ticket information processing system 200 that receives this will also determine whether the two-dimensional code corresponding to the received two-dimensional code data D12 is within the usable time before comparing the ticket gate device installation station information D21 and ticket gate device equipment information D22 with the ticket content information D2. The specific determination method at this time is the same as that explained in step S21-9.

[0145] Once the above judgment is completed, the control unit 231 transmits information relating to the judgment result of the ticket gate entry / exit in step S22-11 (second entry / exit judgment result information D25) from the communication unit 233 via the communication network N to the ticket gate device 240 that transmitted the two-dimensional code data D12 etc. in step S22-4 and the ticket issuing server 130 of the first ticket information processing system 100 (step S22-12).

[0146] In the ticket gate device 240, which receives the second entry / exit judgment result information D25 sent from the ticket issuing server 230 via the communication unit 243, the control unit 241 opens and closes the opening / closing section 245 based on the received second entry / exit judgment result information D25 (step S22-13). Specifically, if the received second entry / exit judgment result information D25 allows entry or exit, the opening / closing section 245 will be set to the open state, and if the received second entry / exit judgment result information D25 does not allow entry or exit, the opening / closing section 245 will be set to the closed state.

[0147] In the ticket issuing server 130 of the first ticket information processing system 100, when the communication unit 133 receives the second entry / exit judgment result information D25, the control unit 131 updates the information related to the ticket status contained in the ticket content information D2 and ticket purchase information D6 stored in the ticket information memory unit 1322 of the memory unit 132 (step S22-14). The updated contents are the same as those explained in step S21-10.

[0148] Next, the control unit 131 transmits information regarding the update content of the ticket status information included in the ticket content information D2 and the ticket purchase information D6 in step S22-14 (second entry / exit status update information D26) from the communication unit 133 to the ticket reservation server 120 via the communication network N (step S22-15).

[0149] In the ticket reservation server 120 of the first ticket information processing system 100, when the communication unit 123 receives the second entry / exit status update information D26, the control unit 121 updates the information related to the ticket status contained in the ticket content information D2, ticket purchase information D6, and ticket reservation information D8 stored in the ticket information memory unit 1222 of the memory unit 122 in the same manner as the update in the ticket issuing server 130 in step S22-14 (step S22-16).

[0150] [3 Explanation of effects] Next, the effects of this embodiment will be described.

[0151] In this embodiment, information such as ticket content information D2, which is information related to the contents of the ticket in the form of a one-dimensional or two-dimensional code used by the user, is stored in the ticket issuing server and is not stored in the ticket in the form of a one-dimensional or two-dimensional code held by the user. There are at least two ticket issuing servers: a ticket issuing server 130 associated with the first ticket information processing system 100, and a ticket issuing server 230 associated with the second ticket information processing system.

[0152] Therefore, for example, as described above, it is conceivable that a ticket in the form of a one-dimensional or two-dimensional code issued in the first ticket information processing system 100 and in which information relating to the ticket content, such as ticket content information D2, is stored in the ticket issuing server 130 may be used in the ticket gate device 240 relating to the second ticket information processing system 200. In this case, the ticket issuing server 230 of the second ticket information processing system 200 cannot make a determination as to whether or not a user is allowed to enter or exit.

[0153] However, according to this embodiment, the information stored in the ticket using a one-dimensional or two-dimensional code used by the user includes issuing server identification information D15, which is information that can create two-dimensional code data D12 and identify the ticket issuing server 130 in which information related to the contents of the ticket, such as ticket content information D2 corresponding to the two-dimensional code data D12, is stored.Therefore, in the ticket issuing server 230 of the second ticket information processing system 200, it is possible to identify the ticket issuing server 130 in which information related to the contents of the ticket, such as ticket content information D2 corresponding to the two-dimensional code data D12, is stored. This enables the ticket issuing server 230 of the second ticket information processing system 200 to obtain information regarding the result of the determination as to whether a user is permitted to enter or exit from the ticket issuing server 130 of the first ticket information processing system 100, or to obtain information regarding the contents of the ticket, such as ticket content information D2, from the ticket issuing server 130 of the first ticket information processing system 100, and then make its own determination as to whether a user is permitted to enter or exit.

[0154] Therefore, even if information regarding the contents of the ticket used by the user is stored in a ticket issuing server 130 of the first ticket information processing system 100 that is different from the ticket issuing server 230 connected to the ticket gate device 240 where the ticket was used, it is possible to obtain information regarding the result of the determination as to whether the user is allowed to enter or exit at the ticket gate device 240, thereby reducing the risk of the ticket gate device 240 not allowing the user to enter or exit.

[0155] Furthermore, since the ticket issuing server 130 storing information relating to the contents of the ticket, such as the ticket content information D2 corresponding to the two-dimensional code data D12 as described above, is identified by the ticket issuing server 230, not by the ticket gate device 240, there is no need to modify individual ticket gate devices to enable such identification. Therefore, special tickets that can be used across lines operated by multiple railway operators can be issued quickly and at low cost while still enabling the above-mentioned identification.

[0156] Furthermore, according to this embodiment, the above-mentioned effects can be obtained while maintaining different contents between the encoded information D16 stored in the encoded information memory unit 1323 of the memory unit 132 of the ticket issuing server 130 of the first ticket information processing system 100 and the encoded information D16 stored in the encoded information memory unit 2323 of the memory unit 232 of the ticket issuing server 230 of the second ticket information processing system 200. Therefore, if railway operator A, which manages and operates the first ticket information processing system 100, and railway operator B, which manages and operates the second ticket information processing system 200, are different railway operators, there is no need for them to disclose information related to ticket encoding to each other, which is also preferable from a security standpoint.

[0157] In addition, in the two-dimensional code data D12, only a portion of the information in the basic information section D12-1 is encoded, the ticket identifier information D10 is included in the encoded information, and the issuing server specific information D15 is included in the unencoded information. This allows the issuing server specific information D15 to be read even by the ticket issuing server 230 of the second ticket information processing system 200 that did not create the two-dimensional code data D12. Also, the ticket identifier information D10 cannot be read by the ticket issuing server 230 of the second ticket information processing system 200 that did not create the two-dimensional code data D12, which is preferable from the viewpoint of security.

[0158] Furthermore, according to this embodiment, the two-dimensional code data D12 is composed of a basic information section D12-1 and a validity verification section D12-2, as shown in FIG. 11. The validity verification section D12-2 includes basic verification information D17A, which is information relating to the results of a predetermined verification conversion or calculation based on the data included in the basic information section D12-1, in accordance with a predetermined conversion rule or formula related to common verification processing information D18A, which is a predetermined conversion rule or formula used commonly by railway operator A and railway operator B, and individual verification information D17B, which is information relating to the results of a predetermined verification conversion or calculation based on the data included in the basic information section D12-1, in accordance with individual verification processing information D18B, which is a predetermined conversion rule or formula used individually by railway operator A and railway operator B, and which is different between the first ticket information processing system 100 and the second ticket information processing system 200.

[0159] Therefore, as described above, by performing a predetermined testing conversion or calculation using common testing processing information D18A based on the data contained in the basic information section D12-1 of the two-dimensional code data D12, and then determining whether it matches the basic testing information D17A contained in the validity testing section D12-2, it is possible to determine whether the ticket is genuine at the ticket gate device 240 even when entering or exiting using a two-dimensional code issued by the first ticket information processing system 100 at the ticket gate device 240 related to the second ticket information processing system 200.

[0160] Furthermore, when the ticket issuing server 130 of the first ticket information processing system 100 that issued the two-dimensional code receives the two-dimensional code data D12, it performs a predetermined conversion or calculation for testing using the individual testing processing information D18B based on the data contained in the basic information section D12-1 of the two-dimensional code data D12, and then determines whether it matches the individual testing information D17B contained in the validity testing section D12-2, thereby determining whether the ticket is genuine.

[0161] This means that regardless of whether the two-dimensional code data D12 read by the ticket gate device 240 was generated by the ticket issuing server 130 of the first ticket information processing system 100 or the ticket issuing server 230 of the second ticket information processing system 200, the ticket gate device 240 can determine whether the ticket is genuine and only send the two-dimensional code data D12 to the ticket issuing server 230 if it determines that the ticket is genuine, thereby reducing the possibility that information related to an unauthorized ticket will reach the ticket issuing server and reducing the burden on the ticket issuing server related to processing unauthorized tickets.

[0162] Furthermore, when the ticket issuing server 130 of the first ticket information processing system 100 that issued the two-dimensional code receives the two-dimensional code data D12, it performs a genuine ticket determination separately from the ticket gate device 240, thereby further reducing the risk of an unauthorized ticket being used.In addition, since the individual testing processing information D18B used in the ticket issuing server 130 has different contents for the first ticket information processing system 100 and the second ticket information processing system 200, even if railway operator A that manages and operates the first ticket information processing system 100 and railway operator B that manages and operates the second ticket information processing system 200 are different railway operators, there is no need to disclose to the outside the individual testing processing information used to determine whether a ticket is genuine in the ticket issuing server, making it less likely that security issues will arise.

[0163] Furthermore, since the common testing processing information D18A has common content in the first ticket information processing system 100 and the second ticket information processing system 200 and is stored in the ticket gate device, it is more likely to be leaked to the outside than the individual testing processing information D18B. Therefore, it is preferable to take measures such as changing the common test processing information D18A immediately when it is confirmed that it has been leaked to the outside, or changing it at specified intervals even if it is not confirmed that it has been leaked to the outside.

[0164] [4 Variations] Next, a modification of this embodiment will be described.

[0165] [(1) Variation 1: Issuance of tickets in the second ticket information processing system] In the above, we have explained the case where a ticket with a two-dimensional code is issued by the first ticket information processing system 100 when the ticket is issued (step S1 in the operation explanation), but the same processing is also performed when a ticket with a two-dimensional code is issued by the second ticket information processing system 200.

[0166] In other words, in this case, the two-dimensional code data D12 created in the ticket issuing server 230 will include issuing server identification information D15 as information that can identify the ticket issuing server that created the data, i.e., the ticket issuing server 230 of the second ticket information processing system 200.

[0167] [(2) Variation 2: Ticket gate entry and exit in the first ticket information processing system] In the above, we have explained the case where a user uses a ticket with a two-dimensional code issued by the first ticket information processing system 100 to enter or exit a ticket gate at the ticket gate device 240 related to the second ticket information processing system 200 when entering or exiting the ticket gate (step S2 in the operation explanation).However, the same processing is also performed when a user uses a ticket with a two-dimensional code issued by the second ticket information processing system 200 to enter or exit a ticket gate at the ticket gate device 140 related to the first ticket information processing system 100.

[0168] That is, in this case, when the ticket issuing server 130 of the first ticket information processing system 100 determines, based on the issuing server identification information D15, that the two-dimensional code data D12 was created by the ticket issuing server 230 of the second ticket information processing system 200, data such as the two-dimensional code data D12 is transmitted from the ticket issuing server 130 of the first ticket information processing system 100 to the ticket issuing server 230 of the second ticket information processing system 200. Thereafter, the ticket issuing server 230 of the second ticket information processing system 200 determines whether the user is permitted to enter or exit, or the ticket issuing server 130 of the first ticket information processing system 100 acquires the ticket content information D2 from the ticket issuing server 230 of the second ticket information processing system 200 and determines whether the user is permitted to enter or exit.

[0169] [(3) Variation 3: Adding a ticket issuing server] In the above, we have described a case where two systems are provided: a first ticket information processing system 100 managed and operated by railway operator A, with a ticket gate device 140 and a ticket issuing device 150 installed in area X; and a second ticket information processing system 200 managed and operated by railway operator B, with a ticket gate device 240 and a ticket issuing device 250 installed in area Y; and the ticket issuing server 130 of the first ticket information processing system 100 and the ticket issuing server 230 of the second ticket information processing system 200 are connected; however, it is also possible to provide a larger number of ticket information processing systems and connect a larger number of ticket issuing servers.

[0170] Furthermore, in the above, we have described the case where both the first ticket information processing system 100 and the second ticket information processing system 200 have only one ticket issuing server in each system (ticket issuing server 130 in the first ticket information processing system 100, ticket issuing server 230 in the second ticket information processing system 200), but multiple ticket issuing servers may be provided within a single system, and the creation of two-dimensional code data D12 and the storage of information related to the contents of the ticket, such as the corresponding ticket content information D2, may be divided among the multiple ticket issuing servers.

[0171] In either case, when the ticket issuing server creates the two-dimensional code data D12, the issuing server identification information D15 is included in the two-dimensional code data D12, so that other ticket issuing servers that receive the two-dimensional code data D12 from the ticket gate device can create the two-dimensional code data D12 from among multiple ticket issuing servers based on the issuing server identification information D15, and identify the ticket issuing server in which the corresponding information related to the ticket contents, such as ticket content information D2, is stored.

[0172] (4) Variation 4: Issuing a ticket in a ticket issuing device In the above, we have explained the case where tickets are issued to the user terminal 160 using data, but this is not limited to this, and it is also possible for the ticket issuing device 150 to issue tickets using a specified medium such as paper.

[0173] In this case, the user inputs the ticket information D1 he wishes to purchase using the operation unit 155 in the ticket issuing device 150, and according to this information, the ticket information management server 110 generates ticket content information D2, and the ticket issuing server 130 generates two-dimensional code data D12. After receiving the two-dimensional code data D12, the ticket issuing device 150 generates two-dimensional code image data D19 based on the two-dimensional code data D12, and the ticket issuing unit 156 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 D11 are stored by printing or the like on a predetermined medium such as paper.

[0174] In addition, when issuing the ticket at the ticket issuing device 150, the ticket content information D2 may not be generated by the ticket information management server 110, but may be generated by the ticket issuing device 150 immediately after the user inputs the ticket information D1 they wish to purchase, and transmitted to the ticket issuing server 130.

[0175] The fact that tickets may be issued by a ticket issuing device also applies when tickets are issued in the second ticket information processing system 200.

[0176] In addition, when the ticket issuing device 150 issues a ticket using a specified medium such as paper, the two-dimensional code usage time information D14 is not generated, and the determination in step S21-9 or step S22-11 as to whether the two-dimensional code is within the usage time is also omitted.

[0177] (5) Variation 5: Entry / Exit Determination in Ticket Gate Device In the above, it has been explained that in both cases where the entry / exit determination is made in the first ticket information processing system 100 and where the entry / exit determination is made in the second ticket information processing system 200, the entry / exit determination is made in the ticket issuing server. However, when the entry / exit determination is made in the second ticket information processing system 200 described in step S22, it is also possible to have the entry / exit determination be made in the ticket gate device 240.

[0178] In this case, the ticket issuing server 230 receives the ticket content information D2 in step S22-10 and transmits the ticket content information D2 to the ticket gate device 240, which then makes a determination as to whether entry or exit is permitted, similar to that described in S22-11, and after opening and closing the opening / closing section 245, transmits information relating to the determination result to the ticket issuing server 230.

[0179] When the ticket gate device 240 determines whether entry or exit is permitted, instead of transmitting the ticket content information D2 from the ticket issuing server 130 of the first ticket information processing system 100 to the ticket issuing server 230 of the second ticket information processing system 200 in step S22-10, the ticket content information D2 may be transmitted directly from the ticket issuing server 130 of the first ticket information processing system 100 to the ticket gate device 240 of the second ticket information processing system 200. In this case, the ticket issuing server 130 and the ticket gate device 240 must be connected without going through the ticket issuing server 230. By configuring in this manner, even if the second ticket information processing system 200 does not have a ticket issuing server 230, it is possible to send ticket content information D2 to the ticket gate device 240, and have the ticket gate device 240 make a determination regarding whether entry or exit is permitted, similar to that described in S22-11.

[0180] (6) Variation 6: Issuing tickets using codes other than one-dimensional or two-dimensional codes In the above, an example has been described in which tickets are issued using one-dimensional or two-dimensional codes. In this respect, it is most preferable to issue the ticket using such a one-dimensional or two-dimensional code, since it can be easily issued without using a dedicated medium, but it is also possible to issue the ticket using other means as long as the ticket identifier information D10 and the issuing server specific information D15 can be stored and read by the ticket gate device. For example, the ticket may be issued using an IC card, a magnetic ticket, or the like.

[0181] [(7) Variation 7: Identifying the issuing server in the ticket gate device] In the above, a case has been described in which the ticket issuing server that created the two-dimensional code data D12 is identified in step S21-5 or step S22-5 based on the issuing server identification information D15 included in the two-dimensional code data D12 in the ticket issuing server 230. As described above, it is preferable to identify the ticket issuing server that created the two-dimensional code data D12 in the ticket issuing server 230 because this does not require modification of each ticket gate device. However, it is also possible to identify the ticket issuing server that created the two-dimensional code data D12 in the ticket gate device 240.

[0182] In other words, in this case, in the ticket gate device 240, the ticket information reading unit 244 reads the two-dimensional code data D12 in step S21-1 or step S22-1, and in step S21-2 or step S22-2, the control unit 241 identifies the railway operator that issued the two-dimensional code data D12 based on the issuing operator identification information D27 included in the two-dimensional code data D12, and then further identifies the ticket issuing server (ticket issuing server 130) that created the two-dimensional code data D12 based on the issuing server identification information D15 included in the two-dimensional code data D12.

[0183] In this case, the transmission of information such as the two-dimensional code data D12 from the ticket gate device 240 to the ticket issuing server 130 that created the two-dimensional code data D12 may be done directly, or may be done via the ticket issuing server 230, as in the above embodiment.

[0184] In the former case, the control unit 241 of the ticket gate device 240 directly transmits the two-dimensional code data D12 read by the ticket information reading unit 244, together with the ticket gate device installation station information D21 and the ticket gate device device information D22 stored in the device information storage unit 2423 of the storage unit 242, from the communication unit 243 via the communication network N to the ticket issuing server (ticket issuing server 130) that created the two-dimensional code data D12. In this case, the ticket gate device 240 and the ticket issuing server 130 need to be connected without going through the ticket issuing server 230.

[0185] In the latter case, the control unit 241 transmits the two-dimensional code data D12 read by the ticket information reading unit 244, together with the ticket gate device installation station information D21 and ticket gate device equipment information D22 stored in the equipment information storage unit 2423 of the storage unit 242, from the communication unit 243 via the communication network N to the ticket issuing server 230, together with information indicating the ticket issuing server (ticket issuing server 130) that created the two-dimensional code data D12 (information including content that can identify the ticket issuing server 130). This enables the ticket issuing server 230 to transmit the information received from the ticket gate device 240 to the ticket issuing server 130 without going through the process of identifying the ticket issuing server that created the two-dimensional code data D12 based on the issuing server identification information D15. In this case, the ticket issuing server that created the two-dimensional code data D12 may be identified at the ticket gate device 240, and then the ticket issuing server that created the two-dimensional code data D12 may also be identified at the ticket issuing server 230, thereby performing the identification process twice to improve the accuracy of the identification.

[0186] (8) Variation 8: Application to non-railroads The above describes the case where the means of transportation that a user uses a two-dimensional code to board is a train, but the system according to the above embodiment can also be applied to tickets used for means of transportation other than trains, as long as the ticket can be issued and entry / exit can be determined in a similar manner to the above.

[0187] (9) Variation 9: Utilizing information stored in a ticket issuing server to identify the issuing server In the above, we have described a case where the ticket issuing server that created the two-dimensional code data D12 is identified using only the issuing server identification information D15 contained in the two-dimensional code data D12, but it is also possible to identify the ticket issuing server that created the two-dimensional code data using both the information contained in the two-dimensional code data and the information stored in the ticket issuing server.

[0188] For example, the unencoded information in the basic information section of the two-dimensional code data may include identification information used only to identify the issuing server, such as a number assigned to each two-dimensional code data, and the ticket issuing server may store information relating to the correspondence between the identification information assigned to each such two-dimensional code data and the ticket issuing server that created the two-dimensional code data containing that identification information.The ticket issuing server may then use both the identification information included in the two-dimensional code data received from the ticket gate device and the information relating to the correspondence stored in the ticket issuing server to identify the ticket issuing server that created the two-dimensional code data received from the ticket gate device.

[0189] In this way, information contained in the two-dimensional code data that, when used in conjunction with information stored in the ticket issuing server, can identify the ticket issuing server that created the two-dimensional code data, i.e., the ticket issuing server in which information relating to the contents of the ticket corresponding to the two-dimensional code data (ticket content information D2 and ticket purchase information D6) is stored, also corresponds to server identification information in the present invention, as information that can identify the ticket issuing server in which information relating to the contents of the ticket corresponding to the two-dimensional code data is stored. In addition, information stored in the ticket issuing server that can be used in conjunction with information contained in the two-dimensional code data to identify the ticket issuing server that created the two-dimensional code data also falls under the category of server identification information in this invention, as it is information that can identify the ticket issuing server in which information related to the contents of the ticket corresponding to the two-dimensional code data is stored. Therefore, in this case, both the information contained in the two-dimensional code data and the information stored in the ticket issuing server correspond to the server-specific information of the present invention.

[0190] [2nd Second Embodiment] A second embodiment of the present invention (where server specific information is stored in the ticket issuing server) will be described. Note that parts that are the same as those in the first embodiment will be given the same reference numerals and descriptions thereof will be omitted.

[0191] [1. Configuration Description] First, the configurations of a first ticket information processing system 100A and a second ticket information processing system 200A according to the second embodiment of the present invention will be described.

[0192] As shown in FIG. 14, the first ticket information processing system 100A includes a ticket issuing server 130A instead of the ticket issuing server 130 of the first ticket information processing system 100 in the first embodiment.

[0193] As shown in FIG. 15, the ticket issuing server 130A includes a specific information storage unit 1325A in the storage unit 132A, which stores issuing company list information D28 and issuing server list information D29.

[0194] The ticket issuing server 130A acquires such issuing company list information D28 and issuing server list information D29 in advance based on input by railway operator A, and the control unit 131 stores the acquired information in the specific information storage unit 1325A of the storage unit 132A.

[0195] The issuing company list information D28 is information that stores a list of issuing company identification information D27 used by each company that provides tickets through this system (in this embodiment, railway company A that manages and operates the first ticket information processing system 100A and railway company B that manages and operates the second ticket information processing system 200A).

[0196] In this embodiment, for ease of explanation, an example is given in which only two companies, railway operators A and B, provide tickets through this system. However, if there are five companies, railway operators A, B, C, D, and E, the names of these five companies will be linked to information such as an identifier that can identify the company as the corresponding issuing company identification information D27 and stored as shown in Figure 16.

[0197] In addition, the issuing server list information D29 is information that stores a list of issuing server identification information D15 related to the ticket issuing servers used by each business operator that provides tickets through this system (in this embodiment, the ticket issuing server 130A in the first ticket information processing system 100A and the ticket issuing server 230A in the second ticket information processing system 200A).

[0198] In this embodiment, for ease of explanation, an example is given in which the first ticket information processing system 100A managed and operated by railway operator A has only ticket issuance server 130A as the ticket issuance server, and the second ticket information processing system 200A managed and operated by railway operator B has only ticket issuance server 230A as the ticket issuance server. However, if there are five railway operators A, B, C, D, and E, and the ticket information processing system managed and operated by each company has three ticket issuance servers, then the information stored will be linked to information such as the operator names of these five companies, the names of the corresponding ticket issuance servers, and an identifier that can identify the server as issuing server identification information D15, as shown in Figure 17.

[0199] As shown in FIG. 14, the second ticket information processing system 200A is provided with a ticket issuing server 230A instead of the ticket issuing server 230 related to the second ticket information processing system 200 of the first embodiment, and as shown in FIG. 15, the memory unit 232A of the ticket issuing server 230A is provided with a specific information memory unit 2325A in which issuing company list information D28 and issuing server list information D29 are stored.

[0200] [2 Operation Description] The following describes the operation of the first ticket information processing system 100A and the second ticket information processing system 200A according to this embodiment when they are in use.

[0201] (1) Issuance of tickets In the first ticket information processing system 100A, the flow when a ticket is issued to a user terminal 160 using data is the same as that described for the first embodiment according to the flowcharts of Figures 9 and 10, except for the processing when generating two-dimensional code data.

[0202] When generating two-dimensional code data (step S1-15 when issuing a ticket according to the first embodiment), the control unit 131 of the ticket issuing server 130A generates two-dimensional code data D12A shown in FIG. As shown in Figure 18, the two-dimensional code data D12A has multiple memory areas, namely, a basic information section D12-1A and a validity verification section D12-2. Similar to the two-dimensional code data D12 of the first embodiment, the basic information section D12-1A is encoded using the encoding information D16 stored in the encoding information storage section 1323 of the storage section 132A, with only a portion of the information being encoded. The encoded information includes ticket identifier information D10, and the unencoded information includes issuer identification information D27. However, unlike the two-dimensional code data D12 of the first embodiment, the basic information section D12-1A does not include issuing server identification information D15.

[0203] As described above, the specific information storage unit 1325 of the storage unit 132 stores issuing company list information D28, which is information that lists the issuing company specific information D27 used by each business that provides tickets through this system (in this embodiment, railway business A that manages and operates the first ticket information processing system 100A and railway business B that manages and operates the second ticket information processing system 200A).Therefore, the control unit 131 reads information about railway business A that manages and operates the first ticket information processing system 100A from the issuing company list information D28 stored in the specific information storage unit 1325A of the storage unit 132A and assigns this information to the two-dimensional code data D12.

[0204] (2) Entry and exit of the ticket gates The operation of this system when a user enters or exits a ticket gate at the ticket gate device 240 of the second ticket information processing system 200A using the two-dimensional code issued by the first ticket information processing system 100A after going through the process of issuing a ticket according to the second embodiment described above will be explained separately for the case where the determination of whether entry or exit is permitted is made by the first ticket information processing system 100A that issued the two-dimensional code, and the case where the determination is made by the second ticket information processing system 200A in which the two-dimensional code is used in the ticket gate device.

[0205] [A. When entry and exit is determined in the first ticket information processing system] When entry / exit determination is made in the ticket issuing server 130A of the first ticket information processing system 100A, the operation of the first ticket information processing system 100A and the second ticket information processing system 200A is the same as that described for the first embodiment according to the flowchart of Figure 12, except for the processing when the issuing server is identified.

[0206] When identifying the issuing server (step S21-5 when entry / exit determination is made in the first ticket information processing system of the first embodiment), the control unit 231 of the ticket issuing server 230A receives information transmitted from the ticket gate device 240 via the communication unit 233, and identifies the ticket issuing server that created the two-dimensional code data D12A transmitted from the ticket gate device 240 based on the issuing server list information D29 stored in the identification information memory unit 2325A of the memory unit 232A.

[0207] That is, the control unit 231 first identifies the name of the business that issued the two-dimensional code data D12A (the name of the business that manages and operates the ticket information processing system that includes the ticket issuing server that created the two-dimensional code data D12A) from the issuer identification information D27 stored in the basic information section D12-1A of the two-dimensional code data D12A and the issuer list information D28 stored in the identification information storage section 2325A of the storage unit 232A. In addition, the name of the business that issued the two-dimensional code data D12A does not have to be identified by the ticket issuing server 230A, but the result of identification by the ticket gate device 240 (step S21-2 when entry / exit determination is made in the first ticket information processing system of the first embodiment) can be sent from the ticket gate device 240 to the ticket issuing server 230A together with the two-dimensional code data D12A, etc., and the identification result sent from the ticket gate device 240 can be used.

[0208] Furthermore, as described above, the issuing server list information D29 stored in the specific information storage unit 2325A of the storage unit 232A is information in which the business name of the issuing business, the name of the corresponding ticket issuing server, and the issuing server specific information D15 are linked and stored, as shown in FIG. 17. Therefore, the control unit 231 can extract the issuing server specific information D15 that is linked to the business name and stored based on the identified business name.

[0209] 17, if the issuing server list information D29 includes information on multiple ticket issuing servers for each railway operator, redundancy processing can be performed using, for example, a load balancer, etc. There is one load balancer address for each operator, but distribution to the multiple ticket issuing servers for each operator is performed using a round-robin method. In this case, the load balancer and the like are included in the server device of the present invention.

[0210] Also, for example, instead of providing a separate load balancer, each ticket issuing server may have the function of a load balancer, and the ticket issuing server (in this case, ticket issuing server 230A) that receives the information sent from the ticket gate device may distribute the information to multiple ticket issuing servers associated with each operator.

[0211] When the same railway operator has multiple ticket issuing servers, the purpose is to distribute the load and ensure availability, so the distribution result will be the same regardless of which ticket issuing server of the same operator performs the above process. Therefore, by using either of the above methods (providing a separate load balancer or providing the ticket issuing server with a load balancer function), it is possible to identify the ticket issuing server that created the two-dimensional code data D12 sent from the ticket gate device 240, even if the issuing server list information D29 includes information related to multiple ticket issuing servers for each railway operator.

[0212] [A. When entry and exit is determined by the second ticket information processing system] When entry / exit determination is made by the ticket issuing server 230A of the second ticket information processing system 200A, the operation of the first ticket information processing system 100A and the second ticket information processing system 200A is the same as that described for the first embodiment according to the flowchart of Figure 13, except for the processing when the issuing server is identified.

[0213] In identifying the issuing server (step S22-5 when entry / exit determination is made in the second ticket information processing system of the first embodiment), the control unit 231 of the ticket issuing server 230A, which receives information sent from the ticket gate device 240 via the communication unit 233, identifies the ticket issuing server that created the two-dimensional code data D12A sent from the ticket gate device 240 in the same manner as described when entry / exit determination is made in the first ticket information processing system of the second embodiment.

[0214] [3 Explanation of effects] In this embodiment, as described above, the ticket issuing server 230A of the second ticket information processing system 200A can identify the ticket issuing server 130A that stores information related to the contents of the ticket, such as ticket content information D2 corresponding to the two-dimensional code data D12A received from the ticket gate device 240. This allows the ticket issuing server 230A of the second ticket information processing system 200A to obtain information regarding the determination result of whether a user is permitted to enter or exit from the ticket issuing server 130A of the first ticket information processing system 100A, or to obtain information regarding the contents of the ticket, such as ticket content information D2, from the ticket issuing server 130A of the first ticket information processing system 100A, and then make its own determination as to whether a user is permitted to enter or exit, thereby achieving the same effect as in the first embodiment.

[0215] Furthermore, in the first embodiment, the issuing server specific information D15 was included in the unencoded information in the basic information section D12-1 of the two-dimensional code data D12, which could be easily read by a third party, which was undesirable from the perspective of improving security. In contrast, according to this embodiment, the basic information section D12-1A of the two-dimensional code data D12A does not include issuing server identification information D15, and the ticket issuing server in which information related to the contents of the ticket, such as the ticket content information D2 corresponding to the two-dimensional code data D12A, is stored is identified using issuing server list information D29 stored in the ticket issuing server, so that security can be improved compared to the first embodiment while achieving the same effects as the first embodiment.

[0216] [4 Variations] As explained for the first embodiment, the same processing is performed when a ticket is issued in the second ticket information processing system, the same processing is performed when a user enters or exits at a ticket gate device related to the first ticket information processing system using a ticket with a two-dimensional code issued by the second ticket information processing system, a ticket issuing server may be added, tickets may be issued in the ticket issuing device, entry and exit determination may be made in the ticket gate device, tickets may be issued using codes other than one-dimensional or two-dimensional codes, and this may be applied to tickets used for transportation other than railways (variations 1 to 6 and 8 in the explanation of variations related to the first embodiment).

[0217] In this embodiment, as described above, the two-dimensional code data D12A, unlike the two-dimensional code data D12 according to the first embodiment, does not include issuing server identification information D15, and the ticket issuing server that created the two-dimensional code data D12A, i.e., the ticket issuing server in which information relating to the contents of the ticket corresponding to the two-dimensional code data D12A (ticket content information D2 and ticket purchase information D6) is stored, is identified based on issuing server list information D29 stored in the ticket issuing server. Therefore, with the above configuration, it is not possible to configure the ticket gate device to identify the ticket issuing server that created the two-dimensional code data D12A, as in variant example 7 in the description of the variant example according to the first embodiment. Although it is possible to configure the ticket gate device to identify the ticket issuing server that created the two-dimensional code data D12A by storing issuing server list information D29 in the ticket gate device, from a security standpoint, it is preferable to store issuing server list information D29 in the ticket issuing server and have the ticket issuing server identify the ticket issuing server that created the two-dimensional code data D12A. [Explanation of symbols]

[0218] 100, 100A First Ticket Information Processing System (Information Processing System) 110 Ticket information management server 120 Ticket Reservation Server 130, 130A Ticket issuing server (server device) 131 control unit (storage control means, creation means, first identification means, assignment means, first transmission control means, second transmission control means, determination means, third transmission control means, fourth transmission control means) 132, 132A Storage unit (first storage means, second storage means, storage means) 1321 Ticket issuing program (information processing program) 133 communication unit (first acquisition means, second acquisition means, transmission means, third acquisition means, fourth acquisition means, acquisition means) 140 Ticket gate device 141 control unit (second specifying means, fifth transmission control means, sixth transmission control means) 142 Storage section 143 Communication unit (transmission means) 144 Ticket information reading unit (reading means) 145 Opening and Closing Section 150 Ticket issuing device 160 User Terminals 200, 200A Second Ticket Information Processing System (Information Processing System) 210 Ticket information management server 220 Ticket Reservation Server 230, 230A Ticket issuing server (server device) 231 control unit (storage control means, creation means, first identification means, assignment means, first transmission control means, second transmission control means, determination means, third transmission control means, fourth transmission control means) 232, 232A Storage unit (first storage means, second storage means, storage means) 2321 Ticket issuing program (information processing program) 233 communication unit (first acquisition means, second acquisition means, transmission means, third acquisition means, fourth acquisition means, acquisition means) 240 Ticket gate device 241 control unit (second specifying means, fifth transmission control means, sixth transmission control means) 242 Storage section 243 Communication unit (transmission means) 244 Ticket information reading unit (reading means) 245 Opening and Closing Section 250 Ticket issuing device 260 User Terminals D2 Ticket Information D6 Ticket purchase information (ticket content information) D8 Ticket reservation information (ticket content information) D10 Ticket Identifier Information (Ticket Specific Information) D12 Two-dimensional code data (ticket memory information) D15 Issuing server specific information (server specific information) D16 encoding information D17A Basic Examination Information (First Examination Information) D17B Individual Examination Information (Second Examination Information) D18A Common Test Processing Information D18B Processing information for individual testing D23 1st entry / exit judgment result information (1st judgment result information) D25 2nd entrance / exit judgment result information (2nd judgment result information) D28 Issuer List Information D29 Issuing server list information (server specific information)

Claims

1. A first acquisition means for acquiring ticket content information, which is information relating to the content of a ticket using a predetermined one-dimensional or two-dimensional code used for the use of public transportation, A memory control means for storing the aforementioned ticket content information in a memory means, For each ticket content information stored in the storage means, a creation means for creating ticket storage information which includes server identification information which is information stored in the ticket that can identify the server device on which the ticket content information is stored, and ticket identifier information which is information that can identify the ticket content information, and available time information which relates to the available time of the ticket storage information. A second acquisition means for acquiring the ticket storage information read by the ticket gate device, The system includes a method for identifying a server device that stores the ticket content information corresponding to the ticket storage information acquired by the second acquisition means, using the server identification information contained in the ticket storage information. A server device identified by the aforementioned identification means extracts ticket content information stored in the server device based on the ticket identifier information within the available time period of the available time information, and determines whether or not entry or exit is permitted.

2. The ticket storage information is such that only a portion of the information is encoded. The aforementioned ticket identifier information is included in the encoded information. The server device according to claim 1, characterized in that the server identification information is included in the unencoded information.

3. A first transmission control means that causes the second acquisition means to transmit the ticket storage information acquired by the second acquisition means to a server device identified by the identification means, A third acquisition means acquires first determination result information, which is information relating to the determination result of whether a user possessing the ticket is allowed to enter or exit the ticket gate, determined using the ticket content information corresponding to the ticket storage information transmitted by the first transmission control means, from the server device identified by the identification means. A second transmission control means for transmitting the aforementioned determination result information to the ticket gate device, The server device according to claim 1, characterized by comprising:

4. A fourth acquisition means for acquiring ticket content information corresponding to the ticket storage information transmitted by the first transmission control means from the server device identified by the identification means, A determination means that uses the ticket content information acquired by the fourth acquisition means to determine whether or not the user holding the ticket is allowed to enter or exit the ticket gate device, A third transmission control means causes the transmission means to transmit the second determination result information, which is information relating to the determination result by the determination means, to the ticket gate device. The server device according to claim 1, characterized by comprising:

5. A fourth acquisition means for acquiring ticket content information corresponding to the ticket storage information transmitted by the first transmission control means from a server device identified by the identification means, A fourth transmission control means causes the fourth acquisition means to transmit the ticket content information acquired by the fourth acquisition means to the ticket gate device via a transmission means, Based on the ticket information transmitted to the ticket gate device by the fourth transmission control means, an entry / exit determination is made. The ticket storage information created by the creation means further includes the ticket identifier information, The server device according to claim 1, characterized in that the server device identified by the identifying means extracts ticket content information stored in the server device based on the ticket identifier information within the available time of the available time information.

6. A server device according to any one of claims 1 to 5, A ticket gate device equipped with a reading means for reading the aforementioned ticket storage information, An information processing system characterized by comprising the following features.

7. The ticket gate device is A reading means for reading the aforementioned ticket memory information, A second identification means for identifying a server device in which the ticket content information corresponding to the ticket storage information read by the reading means is stored, A fifth transmission control means causes the reading means to transmit the ticket storage information it has read to the server device identified by the second identification means via a transmission means, An opening / closing control means that opens and closes the opening / closing means based on the determination result information based on the ticket storage information transmitted from the server device identified by the second identification means, The information processing system according to claim 6, characterized by comprising:

8. The ticket gate device is A reading means for reading the aforementioned ticket memory information, A second identification means for identifying a server device in which the ticket content information corresponding to the ticket storage information read by the reading means is stored, A sixth transmission control means causes the reading means to transmit the ticket storage information, read by the reading means, along with information indicating the server device identified by the second identification means, to a predetermined server device via a transmission means. An opening / closing control means that opens and closes the opening / closing means based on the determination result information based on the ticket storage information transmitted from the predetermined server device, The information processing system according to claim 6, characterized by comprising:

9. In an information processing method by an information processing system, A first acquisition step involves acquiring ticket content information, which is information relating to the content of a ticket using a predetermined one-dimensional or two-dimensional code used for the use of public transportation. A memory control step of causing the aforementioned ticket content information to be stored in a storage means, For each ticket content information stored in the storage means, a creation step of creating ticket storage information which includes server identification information which is information stored in the ticket that can identify the server device on which the ticket content information is stored, and ticket identifier information which is information that can identify the ticket content information, and available time information which relates to the available time of the ticket storage information. A second acquisition step involves acquiring the ticket storage information read by the ticket gate device, The second acquisition step includes a selection step which uses the server identification information contained in the ticket storage information to identify the server device on which the ticket content information corresponding to the ticket storage information acquired by the second acquisition step is stored, An information processing method characterized in that, using the server device identified in the specified step, ticket content information stored in the server device based on the ticket identifier information within the available time period of the available time information, and a determination is made as to whether or not entry or exit is permitted.

10. The computer of the server device A first acquisition means for acquiring ticket content information, which is information relating to the content of a ticket using a predetermined one-dimensional or two-dimensional code used for the use of public transportation. A memory control means that causes the aforementioned ticket content information to be stored in a memory means, For each ticket content information stored in the storage means, creation means for creating ticket storage information which includes server identification information which is information stored in the ticket that can identify the server device on which the ticket content information is stored, and ticket identifier information which is information that can identify the ticket content information, and available time information which relates to the available time of the ticket storage information. A second acquisition means for acquiring the ticket storage information read by the ticket gate device, A identifying means that identifies a server device where the ticket content information corresponding to the ticket storage information acquired by the second acquisition means is stored, using the server identification information contained in the ticket storage information. To make it function as, An information processing program characterized in that, using the server device identified by the identifying means, ticket content information stored in the server device based on the ticket identifier information within the available time of the available time information, and a determination is made as to whether or not entry or exit is permitted.

Images