Server for ticket system, ticket system, and ticket processing method

Abstract

To provide a server for ticket systems, a ticket system, and a ticket processing method that can process a wide variety of tickets.SOLUTION: In a ticket system consisting of a server and terminal devices such as ticket gates and ticket vending machines that connect to the server, and where the server is communicatively connected to another system, the server has a terminal communication unit (first communication unit), an external communication unit (second communication unit), and a processor. The terminal communication unit communicates with terminal devices in the ticket system. The external communication unit communicates with an external system that is different from the ticket system. The processor identifies the system managing a ticket by a data format of ticket information read from the ticket by the terminal devices, obtains from the external system a determination result of the processing to be performed on the ticket by the terminal devices when the ticket is managed by the external system, and supplies the determination result obtained from the external system to the terminal devices.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The embodiments of the present invention relate to a ticket system server, a ticket system, and a ticket processing method. [Background technology]

[0002] In recent years, digital ticket systems have been proposed that provide various services using tickets that can be read by terminal devices. For example, in transport facilities such as railways, a station service system has been proposed in which a server acquires ticket information read from a medium presented by a user using a terminal device such as a ticket gate, and the server returns the processing results such as entrance and exit determination to the terminal device to perform station service processing.

[0003] Conventional digital ticket systems can only be used with tickets issued by the operator of the system or tickets that record ticket information in a format defined by the operator. However, in order to provide a variety of services, there is a demand for existing digital ticket systems to be able to provide services using tickets issued not only by the operator but also by other operators, including those in different industries.

[0004] Conventional digital ticket systems have a problem in that, in order to process tickets issued by other event operators, each terminal device must be provided with a dedicated interface for connecting to another system operated by the other event operator. In addition, each business operator often already has a ticket processing system that issues and processes tickets in different data formats for each business operator. For this reason, it is difficult to standardize the data format of tickets issued by various event operators, and it is not easy to sort and transfer ticket information to a system that can handle it. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2017-167612 A Summary of the Invention [Problem to be solved by the invention]

[0006] In order to solve the above problems, an object of the present invention is to provide a ticket system server, a ticket system, and a ticket processing method capable of processing a variety of tickets. [Means for solving the problem]

[0007] According to an embodiment, a server of a ticket system includes a terminal communication unit, an external communication unit, and a processor. The terminal communication unit communicates with a terminal device in the ticket system. The external communication unit communicates with an external system different from the ticket system. The processor identifies a system that manages the ticket based on a data format of ticket information read from the ticket by the terminal device, obtains from the external system a determination result of a process content that the terminal device should execute on the ticket when the ticket is managed by the external system, and supplies the determination result obtained from the external system to the terminal device. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a ticket gate system as a ticket system according to an embodiment. [Diagram 2] FIG. 2 is a block diagram showing an example of the configuration of a server in a ticket gate system serving as a ticket system according to an embodiment. [Diagram 3] FIG. 3 is a block diagram showing an example of the configuration of a ticket gate as a terminal device in a ticket gate system as a ticket system according to an embodiment. [Figure 4] FIG. 4 is a diagram showing an example of the configuration of an identification data table managed by a server of a ticket gate system serving as a ticket system according to an embodiment. [Diagram 5]FIG. 5 is a sequence diagram for explaining a first operation example of the ticket gate system as the ticket system according to the embodiment. [Figure 6] FIG. 6 is a sequence diagram for explaining a second operation example of the ticket gate system as the ticket system according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, embodiments will be described with reference to the drawings. First, the configuration of a ticket gate system 1 as a ticket system according to the embodiment will be described. FIG. 1 is a diagram showing an example of the configuration of a ticket gate system 1 as a ticket system according to an embodiment. As shown in Fig. 1, a ticket gate system 1 as a ticket system is composed of a server 2 and terminal devices such as a ticket gate machine 3 and a ticket vending machine 4 connected to the server 2. The server 2 of the ticket gate system 1 is connected to be able to communicate with multiple ABT systems 5 (5A, 5B, 5C), which are examples of other systems.

[0010] In an ABT (Account Based Ticketing) system, a server manages usage information associated with an account (ID) set for each user or each ticket, and a terminal device provides services based on the usage information managed by the server. The usage information includes information indicating the validity of the ticket (e.g., validity period and validity zone, etc.). The usage information may also include payment information, etc.

[0011] In this embodiment, the ticket gate system 1, the first ABT system 5A, the second ABT system 5B, and the third ABT system 5C are ABT systems operated by different operators, and each system manages usage information using an account that is set up independently. Therefore, even for the same user, each system manages usage information using an account that is set up (registered) independently.

[0012] Each ABT system, such as the ticket gate system 1, the first ABT system 5A, the second ABT system 5B, and the third ABT system 5C, has a server and a terminal device that manages usage information. The server of each ABT system receives information (ticket information) read from the ticket by the terminal device, performs processing such as judging whether or not the terminal device can provide a service based on the usage information specified by the ticket information, and supplies the processing result to the terminal device. The terminal device transmits the ticket information read from the ticket to the server, and provides the user with a service according to the processing result for the ticket information received from the server.

[0013] In the following description, the ticket gate system 1 is an ABT system as a ticket system operated by a transportation business operator (own business operator). The first, second and third ABT systems 5 (5A, 5B, 5C) are external systems (separate systems) operated by businesses (other businesses) different from the ticket gate system 1. However, the other businesses operating the external systems are not limited to transportation businesses, and may be businesses other than transportation businesses, for example, businesses that operate travel agencies or tourist facilities.

[0014] Next, a configuration of the ticket gate system 1 as a ticket system according to the embodiment will be described. In the exemplary configuration shown in FIG. 1, a ticket gate system 1 includes a server 2, and terminal devices such as a ticket gate machine 3 and a ticket vending machine 4. The ticket gate system 1 includes a server 2, a ticket gate machine 3, and a ticket vending machine 4. The server 2 manages usage information for each account in its own carrier. When the server 2 receives ticket information including the account information of its own carrier from the terminal device, it executes processing according to the ticket information and returns the processing result to the terminal device. For example, when the server 2 receives ticket information including the account information of its own carrier from the ticket gate 3, it determines whether or not passage (ticket gate) is permitted based on the usage information corresponding to the account information included in the ticket information, and returns the determination result to the ticket gate 3.

[0015] Furthermore, the server 2 has a function of identifying which system is operating (using) the ticket information received from the terminal device. The server 2 according to this embodiment identifies the system that processes the ticket information based on the data format of the ticket information. If the ticket information is processed by its own operator (ticket gate system), the server 2 identifies the usage information corresponding to the account of the ticket information from a database it manages, and executes a determination process based on the usage information.

[0016] If the ticket information is not that of its own operator, that is, if the ticket information is to be processed by another operator (another system), the server 2 identifies the other system that processes the ticket information, and transfers the ticket information and a processing request to the identified other system. The server 2 receives the processing result in response to the processing request from the other system that transferred the ticket information and the processing request, and supplies the processing result to the terminal device that read the ticket information.

[0017] The ticket gate 3 is an example of a terminal device that processes tickets. The ticket gate 3 controls the passage (entrance and exit) of users based on tickets. The ticket gate 3 is provided, for example, at a ticket gate of a station, and performs ticket gate processing such as ticket gate operations (entry into a station or exit from a station) for users. The ticket gate 3 forms an entrance passage or an exit passage, and performs passage control according to a passenger ticket presented as a ticket by a user passing through the passage.

[0018] The ticket gate 3 communicates with the server 2. The ticket gate 3 reads the information recorded on the ticket presented by the user. The ticket gate 3 transmits a ticket gate determination request including the information (ticket information) data read from the ticket to the server 2, and controls the passage of the user according to the result of the ticket gate determination based on the ticket information acquired from the server 2.

[0019] The ticket vending machine 4 is an example of a terminal device that processes tickets. For example, the ticket vending machine 4 reads information recorded on a ticket presented by a user and provides a service to the user. For example, the ticket vending machine 4 is installed at a station, reads information recorded on a ticket presented by a user, transmits the ticket information read from the ticket and a processing request for a specified processing to the server 2, and receives a processing result based on the ticket information from the server 2.

[0020] The ticket gate system 1 is operated using tickets whose ticket information can be read by a terminal device such as the ticket gate 3. The ticket may be a medium (printed medium or display device) that displays a two-dimensional code that encodes the ticket information, or a portable electronic device such as an IC card or a mobile terminal that holds the ticket information as electronic data. The ticket may also be a magnetic voucher that has a magnetic recording section and records the ticket information in the magnetic recording section.

[0021] Ticket information is assumed to be configured in a data format predefined by each system. In other words, the two-dimensional code used as the ticket is an image in which the ticket information is coded in a data format defined by the issuing (operating) company. Also, the portable electronic device or magnetic ticket used as the ticket may be any device that can read the ticket information in the data format defined by the issuing (operating) company on a terminal device such as the ticket gate 3.

[0022] Next, a configuration of the server 2 in the ticket gate system 1 according to the embodiment will be described. FIG. 2 is a block diagram showing an example of the configuration of a control system of the server 2 in the ticket gate system 1 according to the embodiment. As shown in FIG. 2, the server 2 includes a processor 21, a ROM (Read Only Memory) 22, a RAM (Random Access Memory) 23, a storage unit 24, a first communication unit 25, and a second communication unit 26, and the like.

[0023] The processor 21 realizes various processing functions by executing programs stored in a memory such as the ROM 22 or the storage unit 24. The processor 21 is, for example, a CPU.

[0024] The ROM 22 is a non-volatile memory in which data is stored in advance. For example, the ROM 22 stores a control program and control data executed by the processor 21. The RAM 23 is a volatile memory that temporarily stores data. For example, the RAM 23 functions as a buffer memory for the control program executed by the processor 21.

[0025] The storage unit 24 is composed of a rewritable non-volatile memory. The storage unit 24 stores various data. The storage unit 24 has a usage information database that stores usage information for each account information set in the own carrier. The usage information database stores information for receiving services such as ticket gate processing at a terminal device such as the ticket gate 3 for each account information of the own user as a user.

[0026] The servers of each ABT system 5 (5A, 5B, 5C), which is a separate system, manage a usage information database that stores usage information for each unique account information. This enables the servers of each system 5 (5A, 5B, 5C) to perform processing based on usage information corresponding to the account information included in the unique ticket information.

[0027] The storage unit 24 also has an identification data table for identifying the business operator (ABT system) that handles the ticket information read from the ticket by a terminal device such as the ticket gate 3. The identification data table stores information for identifying which ABT system operates the ticket information obtained from the terminal device.

[0028] The first communication unit 25 is a terminal communication unit for communicating data with terminal devices such as the ticket gate 3 and the ticket vending machine 4. The first communication unit 25 is a communication interface for communicating within the ticket gate system 1 as a ticket system operated by its own operator. The first communication unit 25 is, for example, a local area network (LAN) interface for communicating via a LAN to which the ticket gate 3 and the ticket vending machine 4 as terminal devices are connected.

[0029] The second communication unit 26 is an external communication unit for communicating with the first, second and third ABT systems 5 (5A, 5B, 5C) as external systems operated by an operator other than the ticket gate system 1. The second communication unit 26 is a communication interface for communicating with devices outside the ticket gate system 1 as a ticket system operated by its own operator. The communication unit 26 is, for example, a communication interface for communicating with the first, second and third ABT systems 5 via a wide area network to which the first, second and third ABT systems 5 as external systems are connected.

[0030] Next, a configuration of the ticket examiner 3 serving as a terminal device in the ticket examination system 1 serving as a ticket system according to the embodiment will be described. FIG. 3 is a diagram illustrating an example of the configuration of a ticket examiner 3 serving as a terminal device in the ticket examination system 1 according to the embodiment. The ticket gate 3 is an example of a terminal device in the ticket gate system 1 as a ticket system. The ticket gate 3 is a device that controls the passage of users who present tickets. For example, the ticket gates 3 are installed at ticket gates (entrance or exit) of a station, and a pair of ticket gates 3 form one passage for ticket gates (entrance or exit). The ticket gates 3 may also be dedicated entrance or exit machines that can pass through in only one direction.

[0031] As shown in FIG. 3, the ticket gate 3 has a processor 31, a ROM (read only memory) 32, a RAM (random access memory) 33, a storage unit 34, a communication unit 35, a reading unit 36, a display unit 37, a passage control unit 38, and a sensor 39.

[0032] The processor 31 is, for example, a CPU. The processor 31 executes programs stored in a memory such as the ROM 32 or the storage unit 34 to realize various processing functions.

[0033] The ROM 32 is made up of a non-volatile memory in which data is stored in advance. For example, the ROM 32 stores a control program and control data executed by the processor 31. The RAM 33 is made up of a volatile memory that temporarily stores data. For example, the RAM 33 functions as a buffer memory for the control program executed by the processor 31. The storage unit 34 is made up of a rewritable non-volatile memory. The storage unit 34 stores various types of data that can be updated.

[0034] The communication unit 35 is a server communication unit that performs data communication with the server 2. The communication unit 35 is a communication interface for performing data communication within the ticket gate system 1. For example, the communication unit 35 is a local area network (LAN) interface for communicating with the server 2 via a LAN.

[0035] The reading unit 36 ​​reads ticket information from a ticket presented by a user. The reading unit 36 ​​is provided, for example, at one end (the end on the entrance side) of the top surface of a housing forming the ticket gate 3. The reading unit 36 ​​reads information (ticket information) recorded on a ticket presented by a user who wishes to pass through a passage. The reading unit 36 ​​has a configuration according to the medium used as a ticket. The reading unit 36 ​​may be configured to be compatible with various media used as tickets.

[0036] For example, if the ticket is a two-dimensional code, the reading unit 36 ​​has an imaging unit that captures an image of the two-dimensional code. The reading unit 36, which includes an imaging unit, captures an image of the two-dimensional code printed or displayed on the medium used as the ticket, and reads the coded ticket information from the captured image of the two-dimensional code. Here, the two-dimensional code used on the ticket is an image in which the ticket information data, including account information (ID) registered with the business that issues or manages the ticket, is coded.

[0037] Furthermore, when the ticket is an IC card, the reading unit 36 ​​is configured with a card reader compatible with IC cards. The reading unit 36 ​​as a card reader includes a communication interface for communicating with the IC card as a ticket, and reads information recorded on the IC card presented at a predetermined position.

[0038] In addition, when the ticket is a magnetic ticket, the reading unit 36 ​​is configured with a magnetic ticket processing unit. The reading unit 36 ​​as a magnetic ticket processing unit reads the ticket information data recorded in the magnetic recording unit of the magnetic ticket as the ticket.

[0039] The display unit 37 displays guidance and the like. The display unit 37 displays information in response to an instruction from the processor 31. For example, in response to an instruction from the processor 31, the display unit 37 displays guidance to a person in the passage indicating whether or not the person can pass through.

[0040] The passage control unit 38 controls the passage of users through the passage formed by the ticket gate 3. The passage control unit 38 performs passage control as an example of a service provided by a terminal device. The passage control unit 38 operates to allow users who are determined to be allowed to pass through and to block the passage of users who are determined to be prohibited from passing through. For example, the passage control unit 38 includes a door control circuit that opens and closes doors (doors that block entry into the station premises and doors that block exit to the outside of the station premises) provided at the ends of the passage formed by the ticket gate 3. The passage control unit 38 as a door control circuit drives the doors to open and close in response to control instructions from the processor 31.

[0041] The sensor 39 includes a human detection sensor that detects the presence or absence of a user passing through the passage formed by the ticket gate 3. The sensor 39 as a human detection sensor is installed so that each position in the passage formed by the ticket gate 3 becomes a detection position, and outputs a detection signal indicating the presence or absence of a person at each position in the passage to the processor 31. The processor 31 determines whether or not a person has passed through the passage and the number of people passing through based on the detection result of the sensor 39. The sensor 39 may also include a proximity sensor that detects a person approaching the ticket gate 3. 37 is. The sensor 39 as a proximity sensor is provided at the end of the housing of the ticket gate 3, and outputs a detection signal indicating the presence or absence of a person near the entrance of the passage of the ticket gate 3 to the processor 31.

[0042] Next, an identification process will be described in which the server 2 of the ticket gate system 1 serving as a ticket system according to the embodiment identifies (specifies) the system that manages the ticket. When the server 2 of the ticket gate system 1 receives ticket information read from a ticket from a terminal device such as the ticket gate 3, it executes an identification process to identify a system (the ticket gate system 1 as a ticket system or any external system) that manages information related to the ticket based on the received ticket information. The processor 21 of the server 2 specifies the system that manages the ticket of the ticket information received by the first communication unit 25 based on the contents of the identification data table stored in the memory unit 24.

[0043] In this embodiment, the processor 21 identifies a system (the ticket gate system 1, or any one of the first to third ABT systems 5A, 5B, and 5C) that manages information related to the ticket of the ticket information based on the data format of the ticket information. However, in this embodiment, the data format of the ticket information does not simply indicate the definition of a data string, but is information that indicates the characteristics of the ticket information that the terminal device reads from the ticket.

[0044] FIG. 4 is a diagram showing an example of an identification data table held (stored) by the server 2 of the ticket gate system 1 according to the embodiment. 4, the identification data table is stored in the storage unit 24 of the server 2. The identification data table stores information indicating the data format (data characteristics) of the ticket information in association with information indicating a system for managing information related to the ticket of the ticket information.

[0045] In the identification data table, information indicating the characteristics of the data included in the ticket information is stored as the data format. Since it is assumed that the data characteristics vary depending on the type of ticket, information indicating the characteristics of multiple types of data is stored in the data format (data characteristics) of the ticket information.

[0046] In the example shown in FIG. 4, the data format stores "data size" and "identification code" etc. "Data size" is information indicating the size of the ticket information data. "Identification code" is information indicating a system identification code in a common authentication unit that is set in advance in the ticket information data. However, ticket information in which a common authentication unit is not set is also acceptable. In other words, ticket information in which a common authentication unit is not set stores the absence of an "identification code."

[0047] According to the identification data table shown in Fig. 4, the server 2 can identify the ticket information by the "data size". The server 2 can also identify the system that manages the ticket-related information of the ticket information by a combination of the "data size" and the "identification code". This makes it possible to identify the system that manages the ticket-related information of the ticket information (handling system) even for ticket information for which a common authentication section (identification code) is not set.

[0048] The identification data table may also store information other than the "data size" and "identification code" (information indicating the characteristics of the data). For example, if there is ticket information in which specific data is stored at a specified position, the data format of the identification data table may store information indicating the specified position and the data at the specified position (for example, the data at the nth byte is xxxxxxxx).

[0049] In addition, in the identification data table, information indicating the handling system is stored in correspondence with the data format. In the example shown in Fig. 4, "name" and "address" are stored as the handling system. This enables the server 2 to transfer ticket information, etc. to a system that has a matching data format for the ticket information.

[0050] Next, the operation of the entire system including the ticket gate system 1 having the server 2 of the ticket system according to the embodiment will be described. First, a first operation example in a system including a ticket gate system 1 having a server 2 of a ticket system according to an embodiment will be described. FIG. 5 is a flowchart for explaining a first operation example in a system including a ticket gate system 1 having a server 2 of a ticket system according to an embodiment. The processor 31 of the ticket gate 3 reads, by the reading unit 36, ticket information recorded on a ticket presented by a person (user) who wishes to pass through a passage (step ST11).

[0051] For example, when a user presents a two-dimensional code, the ticket gate 3 captures an image of the two-dimensional code presented by the user using a code reader as the reading unit 36, and reads the ticket information by decoding the captured two-dimensional code. Also, when a user presents an IC card, the ticket gate 3 reads the ticket information from the IC card presented by the user using a card reader as the reading unit 36.

[0052] The processor 31 of the ticket gate 3 acquires ticket information read from the ticket presented by the user by the reading unit 36. When the processor 31 acquires the ticket information by the reading unit 36, the processor 31 transfers the acquired ticket information and a judgment request (a processing request for judgment processing) requesting a judgment on whether or not the ticket of the ticket information is permitted to pass to the server 2 by the communication unit 35 (step ST12). Here, the judgment request is a request for the ticket gate 3 as a terminal device to judge the processing content to be executed on the ticket. The processor 31 of the ticket gate 3 transmits the judgment request including information indicating judgment conditions such as the judgment location (judgment station) for judging whether or not to pass and information indicating the judgment date and time together with the ticket information to the server 2.

[0053] The server 2 receives the ticket information and a determination request from the ticket gate 3 via the first communication unit 25. When the processor 21 of the server 2 acquires the ticket information from the ticket gate 3, the processor 21 identifies the system that manages the information related to the ticket of the received ticket information based on the data format of the ticket information (step ST13). For example, the processor 21 first determines whether or not the ticket information received from the ticket gate 3 is ticket information of a ticket managed by the ticket gate system (the ticket system of the operator) 1. If the received ticket information is not ticket information of a ticket managed by the ticket gate system 1, the processor 21 determines which external system manages the ticket information.

[0054] Furthermore, the processor 21 of the server 2 identifies a system that manages information related to the ticket of the received ticket information by referring to the above-mentioned identification data table. The processor 21 analyzes the data format of the ticket information and identifies a system with a matching data format of the ticket information, thereby identifying the system as a system that manages information related to the ticket of the ticket information (such as ticket usage information).

[0055] For example, the processor 21 of the server 2 refers to the data size indicated in the identification data table, and determines a system that manages the information related to the ticket of the ticket information based on the data size of the ticket information. The processor 21 may also identify a system that manages the information related to the ticket of the ticket information by a combination of the data size and an identification code (system identification code) indicated in the identification data table. The processor 21 may also identify a system that manages the information related to the ticket of the ticket information based on the characteristics of the data indicated in the identification data table. For example, the identification data table may register unique data and the position of the unique data as data characteristics, and the processor 21 may identify a system that manages the information related to the ticket of the ticket information based on whether or not the unique data is present at a specific position in the ticket information.

[0056] If the ticket information is a ticket operated in another ABT system (external system) 5 (step ST14, YES), the processor 21 of the server 2 transfers the ticket information and a processing request to the external system identified from the data format of the ticket information (step ST15). For example, when the processor 21 identifies that the ticket information received from the ticket gate 3 is ticket information for a ticket operated in the first ABT system 5A, it transmits to the first ABT system 5A the ticket information and a processing request (determination request) for a determination process to determine whether or not the ticket in the ticket information is permitted to pass through the ticket gate 3.

[0057] Here, it is assumed that the system that manages information relating to tickets in the ticket information is the first ABT system 5A as an external system, and that the server 2 transfers the ticket information and a processing request (a processing request for the process of determining whether or not to allow passage at the ticket gate 3) to the first ABT system 5A. In other words, it is assumed that the server of the first ABT system (external system) 5A receives the ticket information and the determination request from the server 2.

[0058] When the server of the first ABT system 5A receives the ticket information and the determination request from the server 2, it identifies the usage information corresponding to the account information (ID) included in the ticket information (step ST16). Here, the usage information corresponding to the account information included in the ticket information is information including information indicating the validity of the ticket, such as the validity zone and validity period, and is, for example, information such as boarding pass information and user information.

[0059] When the server of the first ABT system 5 identifies the usage information corresponding to the account information included in the ticket information, it executes a determination process to determine whether or not to permit passage through the ticket gate 3 based on the usage information identified from the ticket information (step ST17). For example, the server of the first ABT system 5 determines the valid section and valid period, etc., based on the usage information corresponding to the ticket information, and determines whether or not to permit passage through the ticket gate 3.

[0060] The server of the first ABT system 5A transmits the passability determination result based on the usage information to the server 2 as a response to the determination request (step ST18). Here, the server of the first ABT system 5A may store the process result (determination result) of the passability determination executed in response to the request from the server 2 as log data associated with the account information included in the ticket information.

[0061] The server 2 may transmit information indicating the processing result at the ticket gate 3 (terminal device) according to the judgment result to the first ABT system 5A, which is an external system that manages the ticket of the ticket information. In this case, the server of the external system (first ABT system 5A) acquires the processing result at the ticket gate 3 (terminal device) based on the judgment result from the server 2 and stores it. This allows the server of the external system to store information indicating the processing result at the ticket gate (terminal device) according to the processing such as ticket gate judgment by the server 2 in association with the account information, and to manage the usage status of the ticket.

[0062] After transferring the ticket information and the determination request from the ticket gate 3 to the first ABT system 5A, the server 2 waits to receive a determination result (processing result) from the first ABT system 5A. When the processor 21 of the server 2 receives information indicating the determination result as a processing result from the first ABT system 5A, it transmits the received information indicating the determination result to the ticket gate 3, which is the sender of the ticket information (the source that read the ticket) (step ST21).

[0063] In addition, if the ticket information from the ticket gate 3 is a ticket used in the ticket gate system 1, that is, if the ticket information is not a ticket for another ABT system (external system) (step ST14, NO), the processor 21 of the server 2 identifies usage information (information indicating the validity of the ticket, such as boarding pass information and user information) using the account information (ID) contained in the ticket information (step ST19).

[0064] When the processor 21 of the server 2 identifies the usage information corresponding to the ticket information, the processor 21 performs a determination process to determine whether or not the passage requested by the ticket gate 3 is permitted based on the usage information (step ST20). The processor 21 determines that the passage is permitted if the ticket on which the ticket information is recorded is within the validity area and validity period based on the usage information, and determines that the passage is not permitted if the ticket is outside the validity area or has expired. The processor 21 transmits information indicating the determination result, which is the result of the determination process, to the ticket gate 3 (step ST21).

[0065] On the other hand, after transmitting the ticket information read by the reading unit 36 ​​to the server 2, the ticket gate 3 waits for the determination result from the server 2. When the processor 31 of the ticket gate 3 receives the determination result from the server 2, it performs ticket gate (passage control) processing according to the determination result (step ST22).

[0066] For example, when processor 31 receives a determination result indicating passage permitted, it controls passage control unit 38 to allow the user who presented the ticket to pass through the passage formed by ticket gate 3. In addition, when processor 31 receives a determination result indicating passage prohibited, it controls passage control unit 38 to prevent the user who presented the ticket from passing through the passage of ticket gate 3.

[0067] As described above, the ticket gate system as a ticket system according to the first operation example of the embodiment has a server with a hub function for connecting to ABT systems (external systems) of other operators. The server with the hub function in the ticket gate system is communicatively connected to terminal devices such as ticket gates, and is communicatively connected to the ABT systems of various other operators. The server of the ticket gate system acquires the ticket information read from the ticket by the terminal device, and identifies a system that manages information related to the ticket of the ticket information by analyzing the data format of the ticket information. When the ticket information from the terminal device is a ticket managed by an external system, the server transmits the ticket information and a processing request to the external system that manages the ticket of the ticket information from the terminal device, and supplies information indicating the processing result based on the ticket of the ticket information in the external system of the transmission destination to the terminal device.

[0068] As a result, the ticket system according to the first operation example of the embodiment can provide services on the terminal device according to the tickets even if the tickets are issued in unique formats by various businesses. Furthermore, the ticket system can provide services using various tickets, such as tickets managed by an external system, through processing by the server, without significantly changing the system configuration or placing new burdens on terminal devices such as ticket gates. As a result, it becomes easier to cooperate with businesses in different industries, improving services for users, and making it easier for businesses to expand their business at low cost.

[0069] Next, a second operation example in the system including the ticket gate system 1 having the server 2 of the ticket system according to the embodiment will be described. FIG. 6 is a flowchart for explaining a second operation example in a system including a ticket gate system 1 having a server 2 of a ticket system according to an embodiment. The processor 31 of the ticket gate 3 reads, by the reading unit 36, ticket information recorded on a ticket presented by a person (user) who wishes to pass through a passage (step ST31).

[0070] For example, when a user presents a two-dimensional code, the ticket gate 3 captures an image of the two-dimensional code presented by the user using a code reader as the reading unit 36, and reads the ticket information by decoding the captured two-dimensional code. Also, when a user presents an IC card, the ticket gate 3 reads the ticket information from the IC card presented by the user using a card reader as the reading unit 36.

[0071] The processor 31 of the ticket gate 3 acquires ticket information read from the ticket presented by the user by the reading unit 36. When the processor 31 acquires the ticket information by the reading unit 36, the processor 31 transfers the acquired ticket information and a judgment request for a judgment process of passability based on the ticket information to the server 2 by the communication unit 35 (step ST32). Here, the judgment request is a request for the ticket gate 3 as a terminal device to judge the processing content to be executed on the ticket. The processor 31 of the ticket gate 3 transmits the judgment request including information indicating judgment conditions such as the judgment location (judgment station) for judging passability and information indicating the judgment date and time together with the ticket information to the server 2.

[0072] The server 2 receives the ticket information and a determination request from the ticket gate 3 through the first communication unit 25. When the processor 21 of the server 2 acquires the ticket information from the ticket gate 3, it identifies the system that manages the ticket-related information of the received ticket information based on the data format of the ticket information (step ST33). First, the processor 21 determines whether or not the ticket information received from the ticket gate 3 is a ticket (a ticket that manages account information, usage information, etc.) managed by the ticket gate system (its own operator's ticket system) 1. If the received ticket information is not a ticket managed by the ticket gate system 1, the processor 21 further identifies another ABT system (external system) 5 that manages the ticket-related information of the received ticket information.

[0073] The processor 21 of the server 2 identifies an external system that manages the information related to the ticket of the received ticket information by referring to the above-mentioned identification data table. For example, the processor 21 identifies a system that manages the information related to the ticket of the ticket information by analyzing the data format of the ticket information and identifying a system with which the data format of the ticket information matches.

[0074] Specifically, the processor 21 of the server 2 may refer to the data size indicated in the identification data table and determine the system that manages the ticket of the ticket information based on the data size of the ticket information. The processor 21 may also identify the system that manages the ticket of the ticket information by a combination of the data size and an identification code (system identification code) indicated in the identification data table. The processor 21 may also identify the system that manages the ticket of the ticket information based on the characteristics of the data indicated in the identification data table. The unique data and the position of the unique data may be registered in the identification data table as data characteristics, and the processor 21 may identify the system that manages the ticket of the ticket information based on whether or not the unique data is present at a specific position in the ticket information.

[0075] If the ticket information is a ticket operated in another ABT system (external system) 5 (step ST34, YES), the processor 21 of the server 2 transfers the ticket information and a determination request (or information indicating that a ticket inspection process has occurred at the ticket gate 3) to the external system identified from the data format of the ticket information (step ST35). For example, when the processor 21 determines that the ticket information received from the ticket gate 3 is a ticket operated in the first ABT system 5A, it transmits to the first ABT system 5A the ticket information and a processing request (determination request) for a determination process to determine whether or not the ticket in the ticket information is allowed to pass through the ticket gate 3.

[0076] Here, it is assumed that the system that manages (operates) the ticket of the ticket information is the first ABT system 5A as an external system, and the server 2 transfers the ticket information and the determination request to the first ABT system 5A. In other words, it is assumed that the server of the first ABT system (external system) 5A receives the ticket information and the determination request from the server 2.

[0077] When the server of the first ABT system 5A receives the ticket information and the determination request from the server 2, it identifies the usage information corresponding to the account information (ID) included in the ticket information (step ST36). The usage information corresponding to the account information is information including information indicating the validity of the ticket, such as the validity section and validity period, and is, for example, information such as passenger ticket information and user information.

[0078] When the server of the first ABT system 5A identifies the usage information corresponding to the account information included in the ticket information, it requests the server 2 to perform a determination process of whether or not the user can pass through the ticket gate 3 based on the usage information identified from the ticket information (step ST37). For example, the server of the first ABT system 5A transmits usage information (ticket usage information) corresponding to the ticket information together with a determination request (processing request) to the server 2. After transmitting the determination request to the server 2, the server of the first ABT system 5A waits to receive the result of the determination process from the server 2.

[0079] When the processor 21 of the server 2 receives the determination request and the usage information from the server of the first ABT system 5A, the processor 21 performs a determination process to determine whether or not the passage at the ticket gate 3 is passable based on the received usage information (step ST38). For example, the processor 21 of the server 2 determines that the passage is passable if the determination condition from the ticket gate 3 is within the valid area and valid period of the usage information, and determines that the passage is not passable if it is outside the valid area or the expiration date.

[0080] When the processor 21 of the server 2 performs a ticket gate determination in response to a determination request from the server of the first ABT system 5A as an external system, it transmits information indicating the determination result, which is the result of the ticket gate determination process, to the ticket gate 3, which is the sender of the ticket information (the source from which the ticket is read) (step ST39).

[0081] After transmitting the ticket information read by the reading unit 36 ​​to the server 2, the ticket gate 3 waits for a determination result from the server 2. When the processor 31 of the ticket gate 3 receives the determination result from the server 2, it performs a ticket gate (passage control) process according to the determination result (step ST40). For example, when the processor 31 receives a determination result indicating passage permitted, it controls the passage control unit 38 to allow the user who presented the ticket to pass through the passage formed by the ticket gate 3. Also, when the processor 31 receives a determination result indicating passage prohibited, it controls the passage control unit 38 to prevent the user who presented the ticket from passing through the passage of the ticket gate 3.

[0082] In addition, when the processor 21 of the server 2 executes a ticket gate determination process in response to a determination request from the first ABT system 5A (external system), it transmits information indicating the determination result, which is the result of the determination of whether or not passage is permitted (ticket gate determination) at the ticket gate 3, to the system that sent the determination request (here, the first ABT system 5A) (step ST41).

[0083] The server of the first ABT system 5A, which is the sender of the determination request, receives the determination result made by the server 2 in response to the determination request, and stores the information indicating the determination result received from the server 2, etc., in association with the account information included in the ticket information (step ST42). This allows the server of the first ABT system 5A (external system) to store the information indicating the determination result as the processing result of the ticket gate determination process executed by the server 2, etc., in association with the account information, and to manage the usage status of the ticket.

[0084] The server 2 may transmit information indicating the processing result at the ticket gate 3 (terminal device) according to the ticket gate determination to the first ABT system 5A (external system) which is the sender of the determination request. In this case, the server of the first ABT system 5A (external system) acquires the processing result at the ticket gate 3 (terminal device) based on the determination result from the server 2 and stores it. This allows the server of the first ABT system 5A (external system) to store information indicating the processing result at the ticket gate (terminal device) according to processing such as ticket gate determination by the server 2 in association with account information, and to manage the usage status of tickets.

[0085] In addition, if the ticket information from the ticket gate 3 is a ticket used in the ticket gate system 1, that is, if the ticket information is not a ticket for another ABT system (external system) (step ST34, NO), the processor 21 of the server 2 identifies usage information (information indicating the validity of the ticket, such as boarding pass information and user information) using the account information (ID) contained in the ticket information (step ST43).

[0086] When the processor 21 of the server 2 identifies the usage information corresponding to the ticket information, the processor 21 performs a determination process to determine whether or not the passage requested by the ticket gate 3 is permitted based on the usage information (step ST38). In this case, the processor 21 transmits information indicating the determination result, which is the result of the determination process based on the usage information managed by the ticket gate system 1 of the own operator, to the ticket gate 3 (step ST39). As a result, the processor 31 of the ticket gate 3 receives the determination result from the server 2, and performs ticket gate (passage control) processing according to the received determination result (step ST40).

[0087] As described above, the ticket gate system as a ticket system according to the second operation example of the embodiment has a server with a hub function for connecting to ABT systems (external systems) of other operators. The server with the hub function in the ticket gate system is connected to terminal devices such as ticket gates for communication, and also connected to ABT systems of various other operators for communication. The server of the ticket gate system acquires ticket information read from the ticket by the terminal device, and identifies a system that manages information related to the ticket of the ticket information by analyzing the data format of the ticket information. If the ticket information from the terminal device is a ticket managed by an external system, the server transmits the ticket information and a processing request to the external system that manages the ticket of the ticket information from the terminal device. Furthermore, in the second operation example, the server executes a judgment process in response to a processing request (judgment request) from the external system that transmitted the ticket information and the processing request, and supplies information indicating the judgment result to the terminal device and the external system that requested the processing.

[0088] As a result, the ticket system according to the second operation example of the embodiment can provide services on the terminal device according to the tickets even if the tickets are issued by various businesses in their own formats. Furthermore, the ticket system can provide services using various tickets, such as tickets managed by an external system, through processing by the server, without significantly changing the system configuration or placing new burdens on terminal devices such as ticket gates. As a result, it becomes easier to cooperate with businesses in different industries, improving services for users, and making it easier for businesses to expand their business at low cost.

[0089] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0090] 1...ticket gate system (ticket system), 2...server, 3...ticket gate (terminal device), 4...ticket vending machine, 5 (5A, 5B, 5C)...other ABT systems (external systems), 21...processor (first processor), 24...memory unit, 25...first communication unit (terminal communication unit), 26...second communication unit (external communication unit), 31...processor (second processor), 34...memory unit, 35...communication unit (server communication unit), 36...reading unit, 37...display unit, 38...passage control unit, 39...sensor.

Claims

1. A server for a ticket system, a terminal communication unit that communicates with a terminal device in the ticket system; an external communication unit that communicates with an external system different from the ticket system; a processor that identifies a system that manages the ticket based on a data format of ticket information read from the ticket by the terminal device, obtains from the external system a determination result of a process content that the terminal device should execute on the ticket when the ticket is managed by the external system, and supplies the determination result obtained from the external system to the terminal device; A server for a ticket system having

2. The ticket information includes account information set for each business operator, the processor acquires a result of a determination of a process content to be executed by the terminal device, the determination being based on usage information of the ticket managed by the external system in association with account information included in the ticket information; A server of the ticket system according to claim 1.

3. A server for a ticket system, a terminal communication unit that communicates with a terminal device in the ticket system; an external communication unit that communicates with an external system different from the ticket system; a processor that identifies a system that manages the ticket based on a data format of ticket information read from the ticket by the terminal device, transmits the ticket information read from the ticket by the terminal device to the external system when the ticket is managed by an external system, determines processing content that the terminal device should execute on the ticket in response to a determination request including ticket usage information from the external system, and supplies the determination result of the processing content to the terminal device; A server for a ticket system having

4. Further, a storage unit is provided for storing information indicating a data format of ticket information of tickets managed by each system, The processor identifies a system that manages information related to the ticket of the ticket information based on the information stored in the storage unit. A server for the ticket system according to claim 1 or 3.

5. The storage unit stores information indicating a data size as a data format of ticket information of tickets managed by each system. A server of the ticket system according to claim 4.

6. The terminal device is a ticket gate having a passage control unit that controls the passage of users, The processor transmits to the external system the ticket information read by the ticket gate and a determination request for determining whether or not the ticket of the ticket information is permitted to pass through the ticket gate. A server for the ticket system according to claim 1 or 3.

7. A ticket system including a terminal device and a server, The server, A terminal communication unit that communicates with the terminal device; an external communication unit that communicates with an external system different from the ticket system; a first processor that identifies a system that manages the ticket based on a data format of ticket information read from the ticket by the terminal device, obtains from the external system a determination result of a process content that the terminal device should execute on the ticket when the ticket is managed by the external system, and transmits the determination result obtained from the external system to the terminal device; The terminal device A server communication unit that communicates with the server; a reading unit that reads ticket information from a ticket presented by a user; a second processor that transmits to the server the ticket information read by the reader and a request for determining a process to be performed on the ticket, and executes a process according to a result of the determination received from the server. Ticket system.

8. A ticket system including a terminal device and a server, The server, A terminal communication unit that communicates with the terminal device; an external communication unit that communicates with an external system different from the ticket system; a first processor that identifies a system that manages the ticket based on a data format of ticket information read from the ticket by the terminal device, transmits the ticket information read from the ticket by the terminal device to the external system when the ticket is managed by an external system, determines processing content that the terminal device should execute on the ticket in response to a determination request including ticket usage information from the external system, and transmits a determination result of the processing content to the terminal device; The terminal device A server communication unit that communicates with the server; a reading unit that reads ticket information from a ticket presented by a user; a second processor that transmits to the server the ticket information read by the reader and a request for determining a process to be performed on the ticket, and executes a process according to a result of the determination received from the server. Ticket system.

9. The terminal device The ticket gate further includes a passage control unit that controls the passage of users, the second processor controls the passage of the user by the passage control unit in response to a determination result of whether the ticket is permitted to pass through the ticket gate, the determination result being received from the server; A ticket system according to claim 7 or 8.

10. A method for processing tickets in a ticket system, comprising: The terminal device obtains the information read from the ticket, identifying a system that manages the ticket based on a data format of information read by the terminal device from the ticket; When the ticket is managed by an external system, the terminal device transmits information read from the ticket to the external system; obtaining, from the external system, a determination result of the processing content that the terminal device should execute on the ticket; supplying the determination result obtained from the external system to the terminal device; Ticket handling methods.

11. A method for processing tickets in a ticket system, comprising: The terminal device obtains the information read from the ticket, identifying a system that manages the ticket based on a data format of the ticket information read by the terminal device from the ticket; When the ticket is managed by an external system, the terminal device transmits ticket information read from the ticket to the external system; determining a process content to be executed by the terminal device for the ticket in response to a determination request including the usage information of the ticket from the external system, and supplying a result of the determination of the process content to the terminal device; Ticket handling methods.

Images