JP7524006B2 - Ticket machine - Google Patents

Description

An embodiment of the present invention relates to a ticket gate.

In recent years, ticket gates have been proposed for railway ticket gates and other facilities that use mobile devices carried by users to control entry and exit. However, people without mobile devices must first purchase a ticket that can be used at the ticket gate at a ticket vending machine before entering or exiting through the ticket gate. For example, when a group of people such as a family uses the railway, people without mobile devices such as children or elderly people must purchase a ticket at a ticket vending machine, even if the ticket gate allows entry and exit processing using a mobile device. Such problems hinder the improvement of convenience for users and pose a challenge for operators such as railway companies in their efforts to alleviate congestion and ensure smooth station operations.

JP 2007-72780 A

To solve the above problems, the objective is to provide a ticket gate that can smoothly process tickets for a group of multiple users.

According to an embodiment, the ticket gate has a communication unit, an ID reader, and a processor. The communication unit communicates with a server that holds usage information associated with the ID. The ID reader reads the ID from the mobile terminal. The processor transmits the ID read by the ID reader to the server via the communication unit, obtains information from the server indicating the number of users that can be used according to the usage information corresponding to the ID, and allows people equal to or less than the number of users to pass through the passage. Furthermore, when the number of users obtained from the server is multiple, the processor causes the ID reader to read the ID again from the mobile terminal every time a person passes through the passage and transmits the ID to the server, and obtains information from the server indicating the remaining number of users that can be used.

FIG. 1 is a diagram illustrating an example of the configuration of a ticket gate system according to an embodiment. FIG. 2 is a diagram illustrating an example of the configuration of a ticket gate according to the embodiment. FIG. 3 is a block diagram showing an example of the configuration of a control system in the ticket gate according to the embodiment. FIG. 4 is a block diagram showing an example of the configuration of a control system in the attendant terminal of the ticket gate system according to the embodiment. FIG. 5 is a block diagram showing an example of the configuration of a control system in a server of the ticket gate system according to the embodiment. FIG. 6 is a diagram showing an example of information that is managed by the server of the ticket gate system according to the embodiment in association with an ID. FIG. 7 is a flowchart for explaining a first operation example of the ticket gate according to the embodiment. FIG. 8 is a flowchart for explaining an example of the operation of the staff terminal in the ticket gate system according to the embodiment. FIG. 9 is a flowchart for explaining a second operation example of the ticket gate according to the embodiment.

Hereinafter, embodiments will be described with reference to the drawings.
FIG. 1 is a diagram illustrating an example of the configuration of a ticket gate system 1 according to an embodiment.
As shown in FIG. 1, in the ticket gate system 1 , a ticket gate 11 and an attendant terminal 12 provided at each station are connected to a server 21 via a communication device 13 .

The ticket gate 11 is installed at the ticket gates of each station. The ticket gate 11 controls passage (ticket gate processing), such as ticket gate (entry or exit) operations for users. The ticket gate 11 communicates with the server 21 via the communication device 13. The ticket gate 11 performs ticket gate processing for users based on information managed by the server 21.

The attendant terminal 12 is a device operated by an attendant. For example, the attendant terminal 12 is provided in a window at a ticket gate. The attendant terminal 12 may also be a terminal device carried by an attendant. The attendant terminal 12 performs various processes that are handled by an attendant in response to a request from a user. The attendant terminal 12 also communicates with the server 21 via the communication device 13. For example, the attendant terminal 12 obtains information about the user from the server 21 and performs various processes that are handled by an attendant.

The server 21 manages various types of data. The server 21 holds information associated with an ID for each user and an ID for each sold or reserved ticket. The server 21 provides the ticket gate 11 with information corresponding to the ID sent from the ticket gate 11, or a portion of the information, and updates the information corresponding to the ID according to the processing content at the ticket gate 11. The server 21 also has a function of providing the attendant terminal 12 with information in response to an inquiry from the attendant terminal 12, and updating the information according to the processing content at the attendant terminal 12.

In the ticket gate system 1, the ticket gate 11 reads an ID from a mobile terminal or the like held by a user and requests information corresponding to the read ID from the server 21. The server 21 holds usability information as ticket information corresponding to the ID. The server 21 can also hold usability information for multiple people for one ID. In response to a request from the ticket gate 11, the server 21 supplies the ticket gate 11 with information indicating whether or not the user can pass based on the usability information corresponding to the ID. The ticket gate 11 controls the passage of the user based on the information obtained from the server 21.

In the ticket gate system 1, the ticket gate 11 may be any device capable of acquiring an ID presented by a user. However, in this embodiment, the ticket gate 11 acquires information including the ID (code information) from a code image presented by the user. For example, a user displays a code image such as a two-dimensional barcode (e.g., a QR code (registered trademark)) that encodes information including the ID (code information) on the display unit of a mobile terminal carried by the user, and presents the mobile terminal at a specified position on the ticket gate 11. The user may also present a recording medium on which a code image that encodes code information including the ID is printed.

The ticket gate 11 obtains code information including the ID from a code image displayed on the display unit of a mobile device or a recording medium presented by the user, obtains information corresponding to the ID from the server 21, and controls the passage of the user. In addition, when the ticket gate 11 obtains information from the server 21 indicating that the ticket is available (passage is possible) for multiple people as information corresponding to the ID, it performs a passage control process to allow the passage of multiple people using that ID.

Next, the configuration of the ticket gate 11 according to the embodiment will be described.
FIG. 2 is a side view that illustrates a schematic configuration example of the ticket gate 11 according to the embodiment.
For example, two ticket gates 11 form one ticket gate (entrance or exit) passage in a set. The ticket gate 11 may be used as an entry-only or exit-only dedicated machine that can pass through the ticket gate passage in only one direction, or may be used as a dual-purpose machine that can pass through the ticket gate passage in both directions. The ticket gate 11 is set in advance as either an entry-only machine, an exit-only machine, or a dual-purpose machine.

In the configuration example shown in FIG. 2, the ticket gate 11 has a housing 30 that forms an entrance or exit passage. An ID reader 32 for reading IDs is provided at one end of the top surface of the housing 30 that forms the ticket gate 11. The ID reader 32 reads code information indicating the ID presented by the user. For example, the ID reader 32 is a code reader that reads a code image displayed on the display unit of a mobile terminal presented by the user. The ID reader 32 may also read a code image printed on a recording medium presented by the user. The ticket gate 11 may also be equipped with a wireless reader/writer that performs wireless communication with a mobile terminal including an IC card. In this case, the ID reader 32 may, for example, combine the functions of a code reader and a wireless reader/writer.

The ID reader 32 is composed of a scanner and a recognition unit. The code reader serving as the ID reader 32 is installed so that the presentation area at one end of the top surface of the housing is the reading range of the code image. When a user who wishes to pass through a ticket gate presents a code image toward the device in the presentation area (reading range), the ID reader 32 scans the code image displayed on the display unit of the mobile device presented by the user and recognizes the information indicated by the scanned code image. The ticket gate 11 obtains information corresponding to the ID contained in the code information indicated by the code image from the server 21, and controls the passage of the user based on the information obtained from the server 21.

A display 33 is provided on the top surface of the housing forming the ticket gate 11 to provide guidance to users or staff. The display 33 is, for example, a liquid crystal display device. The display 33 displays a guidance screen that informs users passing through the passage of the results of the ticket gate processing. The display 33 may be provided in a position where users can check the displayed content. The display 33 is not limited to being set at the end of the top surface of the housing on the exit side, and may be provided, for example, in the center of the top surface of the housing or adjacent to the ID reader 32 on the top surface of the housing.

At both ends of the side of the case 30 that forms the ticket gate 11 facing the passage, there are provided doors 34, 35 that can be opened and closed to allow or deny passage of pedestrians. In the configuration example shown in FIG. 2, door 34 is provided at the end of the passage on the exit (entrance) side, and prevents users from passing through the passage. Door 35 is provided at the end of the passage on the entrance (entrance) side, and prevents users from entering the passage.

A number of human detection sensors 36 are provided inside a sensor cover on the top surface of the housing 30 forming the ticket gate 11 and on the side of the housing 30. The human detection sensors 36 are composed of reflective detection sensors or transmissive detection sensors. The output signal from the human detection sensors 36 is either "light" or "dark". The human detection sensors 36 detect whether or not a person is present at a predetermined detection position. The ticket gate 11 detects the presence or absence of people at various points in the passage using the multiple human detection sensors 36. As a result, the ticket gate 11 is configured to determine the position of a user passing through the passage based on the detection results of the multiple human detection sensors 36. For example, the opening and closing of the door 34 is controlled based on the result of the determination of whether or not the user is allowed to pass and the detection results of the human detection sensors 36, etc.

Furthermore, the ticket gate 11 is provided with a proximity sensor 37 on the side facing the passage entrance direction on the side where the ID reader 32 is provided (the entrance side of the passage). The proximity sensor 37 detects a person approaching the ticket gate 11. The ticket gate 11 detects a person approaching the passage using the proximity sensor 37, allowing the person to undergo ticket gate processing smoothly. For example, the proximity sensor 37 may detect a person who is in a position where the display unit of a mobile terminal displaying a code image can be presented in the presentation area of the ID reader 32. In this case, the ticket gate 11 may control the ID reader 32 to become operable according to the detection result of the proximity sensor 37.

In addition, when the passageway is used in both directions, the ticket gate 11 controls the direction of travel of the user (the direction of the ticket gate) by controlling the opening and closing of the door 35 in response to the detection results of the approach sensor 37. In addition, the ticket gate 11 may control switching between a power saving mode, which reduces power consumption by turning off the display 33, and a normal operation mode (an operation mode in which the ticket gate process is performed), in response to the detection results of the approach sensor 37.

The ticket gate 11 may also have a passage guidance display unit on the side facing the passage entrance direction on the side where the ID reader 32 is provided (the entrance side of the passage). For example, the ticket gate 11 may display information on the passage guidance display unit on whether or not entry to the passage leading to the ticket gate is possible.

Next, the configuration of a control system of the ticket gate 11 according to the embodiment will be described.
FIG. 3 is a block diagram showing an example of the configuration of a control system for the ticket gate 11 configured as described above.
As shown in FIG. 3, the ticket gate 11 has a processor 41, a ROM (read only memory) 42, a RAM (random access memory) 43, a data memory 44, a communication unit 45, an ID reader 32, detectors (human detection sensor 36, approach sensor 37), a display control circuit 46, a display 33, a door control circuit 47, and doors 34, 35.

The processor 41 is, for example, a CPU. The processor 41 realizes various processing functions by executing programs stored in a memory such as the ROM 42 or the data memory 44. By executing the programs, the processor 41 realizes functions such as the function of obtaining information corresponding to an ID read from a code image from the server 21, the function of determining whether a person in the passage can pass based on the information obtained from the server 21, the function of detecting the position and movement of a person in the passage of the ticket gate 11 based on the detection result of the human detection sensor 36, and the function of controlling the opening and closing of the doors 34 and 35.

The ROM 42 is made up of a non-volatile memory in which data is stored in advance. For example, the ROM 42 stores the control program and control data executed by the processor 41. The RAM 43 is made up of a volatile memory that temporarily stores data. For example, the RAM 43 functions as a buffer memory for the control program executed by the processor 41. The data memory 44 is made up of a rewritable non-volatile memory. The data memory 44 stores various types of data that can be updated.

The communication unit 45 is an interface for performing data communication. For example, the communication unit 45 performs data communication with the server 21 via the communicator 13. The communication unit 45 also functions as an interface for communicating with the attendant terminal 12.

The human detection sensor 36 is a sensor that detects the presence or absence of a person (object). As shown in FIG. 2, the human detection sensor 36 is installed on the side of the ticket gate 11 so that each position in the passage is a detection position, and outputs a detection signal indicating the presence or absence of a person at each position to the processor 41. The processor 41 can determine whether or not a person is passing through the passage and the number of people passing through based on the detection result of the human detection sensor 36.

The approach sensor 37 detects a person approaching the ticket gate 11. The approach sensor 37 is provided on the entrance side of the housing of the ticket gate 11, and outputs a detection signal to the processor 41 indicating the presence or absence of a person near the entrance of the ticket gate 11.

The ID reader 32 is a code reader that reads code information from a code image presented by a user. The ID reader 32 reads an image including the face of a code ticket presented in a presentation area (a specified reading range), extracts a code image from the read image, and recognizes the encoded code information from the extracted code image.

For example, the ID reader 32 reads a code image displayed on the display unit of a mobile device presented by the user. The ID reader 32 may also read a code image printed on a medium presented by the user.

The ID reader 32 may have a function of non-contact communication with a portable electronic device such as a contactless IC card or a mobile terminal carried by the user. In this case, the ID reader 32 may have a function of acquiring information including the ID from the portable electronic device carried by the user by non-contact communication.

The display control circuit 46 controls the display content displayed by the display 33. The display control circuit 46 displays information in response to an instruction from the processor 41. For example, the display control circuit 46 causes the display 33 to display a guide to a person in the passage, indicating whether or not the person can pass through, in response to an instruction from the processor 41.
The door control circuit 47 has a mechanism for opening and closing the doors 34 and 35. The door control circuit 47 drives the doors 34 and 35 to open and close in response to a control instruction from the processor 41.

Next, the configuration of a control system of the attendant terminal 12 in the ticket gate system 1 according to the embodiment will be described.
FIG. 4 is a block diagram showing an example of the configuration of a control system of the attendant terminal 12 in the ticket gate system 1 according to the embodiment.
As shown in FIG. 4, the attendant terminal 12 has a processor 51, a ROM (read only memory) 52, a RAM (random access memory) 53, a data memory 54, a communication unit 55, an ID reader 56, a display interface (I/F) 57, a display device 58, an input interface (I/F) 59, and an operation device 60.

The processor 51 realizes various processing functions by executing programs stored in a memory such as the ROM 52 or the data memory 54. The processor 51 is, for example, a CPU. For example, by executing a program, the processor 51 realizes a function of obtaining information corresponding to an ID read from a code image from the server 21, and a function of displaying and modifying the information obtained from the server 21.

The ROM 52 is made up of a non-volatile memory in which data is stored in advance. For example, the ROM 52 stores control programs and control data executed by the processor 51. The RAM 53 is made up of a volatile memory that temporarily stores data. For example, the RAM 53 functions as a buffer memory for the control programs executed by the processor 51. The data memory 54 is made up of a rewritable non-volatile memory. The data memory 54 stores various types of data.

The communication unit 55 is an interface for performing data communication. For example, the communication unit 55 performs data communication with the server 21 via the communicator 13. The communication unit 55 may also be configured to communicate with the ticket gate 11.

The ID reader 56 reads the ID presented by the user. In this embodiment, the ID reader 56 is a code reader that reads code information from a code image presented by the user, similar to the ID reader 32. The ID reader 56 reads an image including the face of the code ticket presented in the presentation area (predetermined reading range), extracts a code image from the read image, and recognizes the coded code information from the extracted code image. The ID reader 56 may also have a function of acquiring information including the ID by a contactless communication function with an electronic device such as a contactless IC card or a mobile terminal.

A display device 58 is connected to the display interface (I/F) 57. The display interface 57 supplies display data from the processor 51 to the display device 58. The display device 58 displays the display data supplied from the processor 51 via the display interface 57 on a display screen.
An operation device 60 for inputting operation instructions, such as a touch panel, a keyboard, or a numeric keypad, is connected to the input interface (I/F) 59. The input interface 59 supplies information indicating the contents inputted by the operation device 60 to the processor 51. For example, the display device 58 and the operation device 60 are configured by a display with a touch panel, and are connected to interfaces used as the display interface 57 and the input interface 59.

Next, the configuration of the server 21 in the ticket gate system 1 according to the embodiment will be described.
FIG. 5 is a block diagram showing an example of the configuration of a control system of the server 21 in the ticket gate system 1 according to the embodiment.
As shown in FIG. 5, the server 21 includes a processor 61, a ROM (read only memory) 62, a RAM (random access memory) 63, a communication unit 64, and a data memory 65.

The processor 61 realizes various processing functions by executing programs stored in a memory such as the ROM 62 or the data memory 65. The processor 61 is, for example, a CPU. For example, by executing a program, the processor 61 realizes a function of supplying information corresponding to a specified ID to the ticket gate 11 or the attendant terminal 12, a function of updating information corresponding to the ID according to the processing results at the ticket gate 11 or the attendant terminal 12, etc.

The ROM 62 is made up of a non-volatile memory in which data is stored in advance. For example, the ROM 62 stores control programs and control data executed by the processor 61. The RAM 63 is made up of a volatile memory that temporarily stores data. For example, the RAM 63 functions as a buffer memory for the control programs and the like executed by the processor 61.

The communication unit 64 is an interface for communication. For example, the communication unit 64 performs data communication with the ticket gate 11 and the attendant terminal 12 via the communicator 13. The communication unit 64 also has a function for communicating with a user terminal (mobile terminal or personal computer) operated by a user. For example, the server 21 may be connected to the interface via the communication unit 64 and accept applications for user registration (issuance of a boarding ticket) from the user terminal on a web page published on the Internet.

The data memory 65 is composed of a rewritable non-volatile memory. The data memory 65 stores various types of data. The data memory 65 holds information associated with an ID. For example, the data memory 65 stores ticket information (entry/exit permission information) for entering and exiting the ticket gate 11 in association with the ID. In this embodiment, the data memory 65 can register ticket information for multiple people for one ID.

Next, information managed by the server 21 according to the embodiment will be described.
A user applies for registration of usage information (passenger ticket information) according to the content of the usage. For example, the user applies for registration of usage information by accessing the server 21 with a user terminal such as a mobile terminal or a personal computer. The application for registration of usage information is a procedure for registering information for permitting entry and exit at the ticket gate 11, and corresponds to the procedure for purchasing a ticket. The server 21 issues an ID in response to the application from the user, and registers the ID and the usage information according to the content of the usage applied for by the user in the data memory 65 in association with each other.

In the ticket gate system 1 according to this embodiment, the server 21 collectively manages usage information for multiple people, such as a family member. When a user (representative) applies for usage information for multiple people, such as a family member, the user applies for information indicating the usage content, including the number of users, along with information about the representative. In response to such an application, the server 21 issues an ID, registers (issues) usage information for multiple users in association with the ID, and provides information indicating the ID to the representative. In this embodiment, the server 21 provides the user (representative) with a code image that encodes information including the ID. The code image may be one that the representative can present to the ticket gate. In this embodiment, the code image is one that can be displayed on the display of a mobile device carried by the representative.

When the server 21 registers the usage information associated with the ID, it generates a code image that encodes information including the ID that has been registered in association with the usage information. The server 21 provides (downloads) the code image that encodes the information including the ID to the user's mobile terminal. For example, when the server 21 has completed registration of the usage information in response to the user's application, the server 21 may provide the user with a code image that indicates code information including the ID along with a message indicating completion of registration. The server 21 may also transmit the code image to a destination (e.g., an email address) specified by the user.

The fee for the usage information registered in association with the ID may be paid in advance or after the fact. For example, in an operation in which the fee is paid in advance, the user enters the usage details and then performs the payment procedure. Once the payment of the fee according to the usage details is completed, the server 21 registers the usage information based on the usage details requested by the user in association with the ID, thereby making the usage information available for use.

In addition, when the operation is such that the fee is paid after the fact, the user inputs the details of the use and registers the payment information (e.g., credit card information) to be used for payment. In this case, the server 21 verifies the validity of the payment information, and then registers the usage information based on the usage details requested by the user in association with the ID, thereby making the usage information available for use. When making a payment after the fact, the server 21 settles the fee using the payment information when the entry/exit process is actually performed using the usage information.

FIG. 6 is a diagram showing an example of information managed in association with an ID in the server 21 according to the present embodiment.
Server 21 issues an ID in response to an application from a user, and registers usage information for the ID in data memory 65 according to the contents of the application. For an ID, not only usage information but also entry information and exit information are recorded in association with the ID. Entry information is recorded when the entry process is performed at the ticket gate using the usage information. Also, exit information is recorded when the exit process is performed at the ticket gate using the usage information.

In the example shown in FIG. 6, the usage information includes the usage section, the number of users, the usage period, representative information, payment information, user authentication information, and the like.
The usage section indicates a valid section. The number of users indicates the number of people who can use the usage information. The number of users may also be registered as a breakdown of the number of people using the information (for example, the number of adults and the number of children). The usage period indicates the period during which the usage information is valid.

The representative information indicates information about the person who manages the usage information. For example, if the representative has an individual personal ID, the representative's ID may be registered. The payment information indicates information about payment. For example, in an operation where payment is made after the fact, the payment information records information (e.g., credit card information) for the person who makes the payment (e.g., the representative) to use the electronic money payment system to settle the fee.

User authentication information is information for identifying individual users. When there are multiple users, authentication information for identifying each individual user (e.g., family members) is registered. For example, facial images of each user are registered as user authentication information. User authentication information may be registered when it is necessary to identify each user individually. When it is not necessary to identify each user individually, user authentication information may not be registered.

In the example shown in FIG. 6, the entry information includes the entry time, entry location, and number of people who entered. The entry time indicates the time of entry using the usage information of the ID. The entry location indicates the location of entry using the usage information of the ID (the station, ticket gate, or ticket gate at which the person entered). The number of people who entered indicates the number of people who have been confirmed to have actually entered. For example, if the number of people who actually entered is less than the number of people using the facility, the number of people who actually entered, which is less than the number of people using the facility, is registered as the number of people who entered.

In the example shown in FIG. 6, the entry information includes the entry time, the entry location, and the number of entrants. The entry time indicates the time of entry using the usage information of the ID. The exit location indicates the location from which the entry was made using the usage information of the ID (the station, ticket gate, or ticket gate from which the entry was made). The number of entrants indicates the number of people who actually entered. For example, if the actual number of people who entered is less than the number of users, the number of people who actually entered, which is less than the number of users, is registered as the number of entrants.

Next, a first operation example of the ticket gate 11 according to the embodiment will be described.
FIG. 7 is a flowchart for explaining a first operation example of the ticket gate 11 according to this embodiment.
A user using the ticket gate 11 presents a code image displayed on the display unit of a portable terminal in the presentation area (reading range) of the ID reader 32 of the ticket gate 11. The processor 41 of the ticket gate 11 detects whether or not a person is approaching the passage while the ticket gate 11 is in a state in which the ticket gate 11 can perform ticket screening processing for the user using the proximity sensor 37. When a person is detected, the processor 41 makes the ID reader 32 in a state in which the code image can be read.

In this state, the ID reader 32 reads the code image presented by the user (ST10). The ID reader 32 captures an image including the code image presented by the user, and recognizes (decodes) the code image included in the captured image. The ID reader 32 supplies the processor 41 with code information as the recognition result of the code image presented by the user.

When the processor 41 acquires the code information read by the ID reader 32, it communicates with the server 21 via the communicator 13 using the communication unit 45, and transmits to the server 21 the ID contained in the code information and information indicating the station (or ticket gate) where the ticket gate 11 is installed (ST11). After transmitting the ID read from the code image and the information indicating the station, the processor 41 acquires a response from the server 21 (ST12).

The processor 61 of the server 21 identifies the usage information (ticket information) corresponding to the ID acquired from the ticket gate 11, and determines whether or not to permit passage through the ticket gate 11 based on the usage information. For example, if the user is not within the valid area, is not within the valid period, or there is no information corresponding to the ID, the processor 61 of the server 21 determines that passage is not permitted. If passage is not permitted, the processor 61 of the server 21 transmits information indicating that passage is not permitted via the communication unit 64 to the ticket gate 11 that sent the ID.

When permitting passage, the processor 61 of the server 21 records the time of passage and the place of passage as passage (entry or exit) information in the data memory 65 in association with the ID, and transmits information indicating the number of users together with information indicating permission to pass to the ticket gate 11 that sent the ID via the communication unit 64. The processor 61 of the server 21 may also transmit information indicating the number of users permitted to pass to the ticket gate 11 when the number of users in the usage information corresponding to the ID is more than one.

When the response from the server 21 indicates that passage is not permitted (ST13, NO), the processor 41 of the ticket gate 11 displays a message on the display 33 indicating that passage is not permitted and closes the door 34. In this way, the processor 41 prevents the user from passing through the passage formed by the ticket gate 11, and ends the processing for that user.

Furthermore, when processor 41 of ticket gate 11 receives a response from server 21 permitting passage of the user, processor 41 permits passage of the user. If passage is permitted (ST13, YES), processor 41 determines whether or not to permit passage of multiple people based on the response from server 21 (ST14). Processor 41 can determine whether people are passing through the passage and the number of people passing through based on the detection results of human detection sensor 36, which detects objects provided on the side of ticket gate 11.

If the gate does not permit the passage of multiple users (ST14, NO), the processor 41 controls passage to allow the user to pass through (ST15). For example, the processor 41 displays a message on the display 33 indicating that passage is permitted and opens the door 34 to allow one user to pass through. In this case, the processor 41 notifies the server 21 that the user has passed through (ST23), and ends the series of ticket gate processing.

When multiple people are permitted to pass (ST14, YES), the processor 41 sets the number of available people obtained from the server 21 in a counter provided in the RAM 43 (ST16). When multiple people are permitted to pass, the processor 41 notifies the number of available people (ST17). For example, the processor 41 displays the number of people who can pass on the display 33. The processor 41 may also notify the number of people who can pass by voice from a speaker (not shown).

After setting the number of available people in the counter, the processor 41 opens the door 34 to allow users to pass through (ST18), and detects the passage of each user based on the detection result of the human detection sensor 38 (ST19). If it detects that one user has passed through (ST19, YES), the processor 41 decrements the counter (subtracts 1 from the counter value) (ST20).

Furthermore, when the counter is decremented, the processor 41 determines whether the counter value has become 0 (ST21). If the counter value is not 0 (ST21, NO), the processor 41 returns to ST17 and notifies the number of people who have passed based on the current counter value or the remaining number of people who can pass (ST17). In other words, if the counter value is not 0, the processor 41 returns to ST17 and repeats the above-mentioned process.

Also, when the counter value becomes 0 (ST21, YES), the processor 41 determines that the number of users equal to the available number of users has passed through. When the counter value becomes 0 (ST21, YES), the processor 41 closes the door 34 to prevent subsequent people from passing through, and ends the passage control for multiple people (ST22). For example, the processor 41 performs control to close the door 34 of the ticket gate 11 when the number of people who have passed through the passage identified from the detection result of the human detection sensor 36 exceeds the number of users acquired from the server 21.
After completing the passage control for multiple people, the processor 41 transmits information indicating the actual number of people passing through to the server 21 (ST23), and ends the series of ticket gate processing for that ID.

In addition, until the counter value becomes 0, the processor 41 monitors whether the next user has been detected within a predetermined time (ST24). If the next user is not detected to pass within the predetermined time, the processor 41 determines that a timeout has occurred. If a timeout has occurred (ST24, YES), the processor 41 determines the number of people who have actually passed through or the number of people who are insufficient relative to the number of users based on the counter value (ST25). After determining the number of people who have actually passed through or the number of people who are insufficient relative to the number of users, the processor 41 closes the door 34 to prevent subsequent people from passing through, and ends the passage control for multiple people (ST22). After ending the passage control for multiple people, the processor 41 transmits information indicating the actual number of people who have passed through (or the number of people who are insufficient relative to the number of users) to the server 21 (ST23), and ends the series of ticket gate processing. In this case, the processor 61 of the server 21 records the actual number of people who have passed through (entered or exited) as passage (entered or exited) information in the data memory 65 based on information from the ticket gate 11.

According to the first operation example described above, when a code image displayed on the display unit of a mobile device is presented, the ticket gate transmits the ID included in the code information showing the presented code image to the server, and obtains from the server the result of a determination as to whether or not the user is permitted to pass based on the usage information corresponding to the ID. If usage by multiple people is registered as usage information corresponding to the ID, the ticket gate obtains information indicating the number of users from the server, and after the representative who presented the code image has passed through, the multiple users registered following the representative are permitted to pass through.

When a group of multiple people uses a ticket gate, if the representative passes through at the front of the group (for example a family) by holding a code image up to the ticket gate, the other people can pass through the gate without having to individually present a code image. As a result, children, elderly people and other users who pass through after the representative can pass through the ticket gate smoothly even without having to carry a mobile device to display the code image.

Next, the operation of the staff terminal 12 according to the embodiment will be described.
The attendant terminal 12 displays information corresponding to the ID included in the code image presented by the user and instructs the correction of the information, according to the operation of the attendant in response to the user's request. For example, the attendant terminal 12 obtains from the server 21 usage information corresponding to the ID indicated by the code image displayed on the display unit of the mobile terminal carried by the user, and displays it on the display device 58. This allows the attendant to check the usage information displayed on the display device 58 and perform entrance and exit (ticket gate) operations on behalf of the ticket gate 11.

In addition, when usage information for multiple users is registered, it is possible that some of the people connected to the representative cannot pass through the ticket gate 11. For example, if other people pass through the passage of the ticket gate 11 following the representative, or if some of the people connected to the representative cannot pass through the passage of the ticket gate 11 due to an emergency, the staff can use the staff terminal 12 to confirm that the user is a legitimate user and then allow them to enter or exit, and can also use the staff terminal 12 to modify the entry or exit information managed by the server 21.

FIG. 8 is a flowchart for explaining an example of the operation of the staff terminal 12 according to this embodiment.
The processor 51 of the attendant terminal 12 puts the ID reader 56 into a state in which the code image can be read in response to an operation by the attendant on the operation device 60. In this state, the attendant causes the code image displayed on the display unit of the mobile terminal carried by the user to be presented within the reading range of the ID reader 56.

The ID reader 56 reads the code image presented by the user within the reading range (ST30). The ID reader 56 captures an image including the code image presented by the user and recognizes the code image included in the captured image. The ID reader 56 supplies the processor 51 with code information as a recognition result of the code image presented by the user.

When the processor 51 acquires the code information read by the ID reader 56, it communicates with the server 21 via the communicator 13 using the communication unit 55, and transmits to the server 21 the ID contained in the code information and a request to display the information corresponding to the ID (ST31).

When the server 21 receives an ID and a display request from the staff terminal 12, it reads information corresponding to the ID (e.g., usage information, entry information, and exit information) from the data memory 65. The server 21 transmits the usage information, entry information, and exit information corresponding to the ID read from the data memory 65 to the staff terminal 12.

The processor 51 of the staff terminal 12 acquires information (usage information, entry information, and exit information) corresponding to the ID from the server 21 via the communication unit 55 (ST32). When acquiring information corresponding to the ID from the server 21, the processor 51 displays the information corresponding to the ID acquired from the server 21 on the display device 58 (ST33).

For example, when the processor 51 receives usage information as information corresponding to an ID, if entry and exit have not been performed, the processor 51 displays the usage information corresponding to the ID on the display device 58. This allows a staff member to allow entry to the user after checking the usage information displayed on the display device 58.

In addition, when the processor 51 receives usage information and entry information as information corresponding to an ID, if the user has not yet exited, the processor 51 displays the usage information and entry information corresponding to the ID on the display device 58. This allows a staff member to allow the user to exit after checking the usage information and entry information displayed on the display device 58.

Furthermore, when processor 51 receives usage information and entry information as information corresponding to an ID, it displays the usage information and entry information corresponding to the ID on display device 58. When the number of entrants in the entry information (the number of people actually detected as having entered) is less than the number of users in the usage information, processor 51 may display the shortage number (number of users in the usage information - number of entrants in the entry information) on display device 58. This allows staff to check the usage information and number of entrants displayed on display device 58, and allows entry to the shortage number of users.

Furthermore, when processor 51 receives usage information, entry information, and exit information as information corresponding to an ID, it displays the usage information, entry information, and exit information corresponding to the ID on display device 58. When the number of participants in the exit information (the number of people actually detected as having entered) is less than the number of people entering in the entry information, processor 51 may display the missing number of people (number of people entering in the entry information - number of people exiting in the exit information) on display device 58. This allows staff to check the number of people entering and the number of people exiting displayed on display device 58, and to check the number of people who have not been processed for exit, or to allow users who have not been able to exit to enter.

In addition, when the processor 51 records entries equal to the number of users in the usage information (when the number of users in the usage information is the same as the number of entrants in the entry information), the attendant terminal 12 may display the authentication information of each user included in the usage information displayed on the display device 58. This allows the attendant to confirm that the user is legitimate and to allow entry to the legitimate user by checking that other people are not being counted as entrants.

In addition, if the processor 51 records the number of entries equal to the number of entries (if the number of entries in the entry information is the same as the number of entries in the entry information), the staff terminal 12 may display the authentication information of each user contained in the usage information displayed on the display device 58. This allows the staff to confirm that the user is legitimate and that other people are not being counted as participants, and then allows the legitimate user to participate.

The processor 51 accepts input of corrections to information using the operation device 60 while displaying information corresponding to the ID acquired from the server 21 on the display device 58 (ST34). When corrections to information are input using the operation device 60, the processor 51 transmits the correction information corresponding to the ID to the server 21 (ST35). The server 21 updates the information stored in the data memory 65 in accordance with the correction information from the staff terminal 12.

For example, if entry and exit based on the usage information corresponding to the ID has not yet been performed, the processor 51 accepts the input of entry information with the usage information corresponding to the ID displayed on the display device 58. If the attendant allows the user to enter after checking the usage information displayed on the display device 58, the attendant inputs information such as the entry location (station) and the number of people entering through the operation device 60. When information such as the entry location and number of people for which entry has been permitted is input, the processor 51 transmits the entry information including the entry location and number of people entering in association with the ID to the server 21. As a result, the server 21 records information (entry information) regarding the user who was allowed to enter at the discretion of the attendant operating the attendant terminal 12.

Furthermore, if entry has not been performed using the usage information corresponding to the ID, the processor 51 accepts the input of entry information while displaying the usage information and entry information corresponding to the ID on the display device 58. If the attendant allows the user to enter after checking the usage information and entry information displayed on the display device 58, the attendant inputs the entry information, such as the exit location (station) and the number of entrants, on the operation device 60. When the entry information for which the attendant has permitted entry is input, the processor 51 transmits the entry information to the server 21 in association with the ID. As a result, the server 21 records information (entry information) about the user who has been allowed to enter at the discretion of the attendant operating the attendant terminal 12.

The processor 51 may also accept input of a correction to the number of people entering (or information indicating the number of additional people allowed to enter) when the number of people entering in the entry information is less than the number of users in the usage information corresponding to the ID and the shortage number is displayed on the display device 58. Here, when allowing entry to a number of users greater than the number of people entering in the entry information, the staff member inputs correction information for the number of people entering using the operation device 60. When the staff member inputs correction information for the number of people allowed to enter, the processor 51 transmits the correction information for the number of people entering to the server 21 in association with the ID. As a result, the server 21 updates (corrects) the number of people entering in the entry information to the number of people allowed to enter at the discretion of the staff member operating the staff member terminal 12.

The processor 51 may also be configured to accept input for correcting the number of participants when the number of participants in the participation information is less than the number of visitors in the admission information, with the missing number of people displayed on the display device 58. Here, when an attendant inputs correction information for the number of participants, the processor 51 transmits the correction information for the number of participants to the server 21 in association with the ID. This allows the server 21 to update (correct) the number of participants in the participation information to the number of participants that was allowed to participate at the discretion of the attendant operating the attendant terminal 12.

Next, a second operation example of the ticket gate 11 according to the embodiment will be described.
FIG. 9 is a flowchart for explaining a second example of the operation of the ticket gate 11 according to this embodiment.
The first operation example described above is an operation example assuming that a representative who presents a code image corresponding to one ID will be at the front and multiple available users will follow the representative through the passageway. In contrast, the second operation example is an operation example assuming that the representative will keep the code image presented within the reading range of the ID reader 32 while users other than the representative pass through the passageway.

First, when the processor 41 of the ticket gate 11 detects a person approaching the passageway using the proximity sensor 37, it sets the ID reader 32 to a state in which it can read a code image. In this state, the ID reader 32 reads the code image presented by the user (ST50). The ID reader 32 captures an image including the code image presented by the user, and recognizes the code image included in the captured image. The ID reader 32 supplies the processor 41 with code information as a recognition result of the code image presented by the user.

When the processor 41 acquires the code information read by the ID reader 32, it communicates with the server 21 via the communicator 13 using the communication unit 45, and transmits to the server 21 the ID contained in the code information and information indicating the station (or ticket gate) where the ticket gate 11 is installed (ST51). After transmitting the ID read from the code image and the information indicating the station, the processor 41 acquires a response from the server 21 (ST52).

The server 21 identifies the usage information (ticket information) corresponding to the ID acquired from the ticket gate 11, and determines whether or not passage through the ticket gate 11 is permitted based on the usage information. The server 21 responds to the ticket gate 11 with information indicating whether or not passage is permitted in response to the ID from the ticket gate 11. For example, if the usage information corresponding to the ID indicates that the user is not within the valid area, is not within the valid period, or there is no information corresponding to the ID, the server 21 determines that passage through the ticket gate 11 using the ID is not permitted. If it determines that passage is not permitted, the server 21 transmits information indicating that passage is not permitted to the ticket gate 11 that sent the ID.

If it is determined that passage is permitted, the server 21 records the time of passage and the place of passage as passage (entry or exit) information in association with the ID, and determines whether the number of users in the usage information corresponding to the ID is more than one. If the number of users is more than one, the server 21 sets a counter indicating the remaining number of users. Also, if a counter indicating the remaining number of users has already been set, the server 21 determines whether the counter value is 0 or not.

If the number of users is not more than one, or if the counter indicating the remaining number of users is 0, the server 21 transmits information indicating permission to pass to the ticket gate 11 that transmitted the ID.
In addition, if there is more than one user and the counter indicating the remaining number of people available is not 0, the server 21 sends a response indicating that passage is permitted for multiple people (people passing through in succession), along with information indicating permission to pass.

If a response is received from the server 21 that passage is not permitted (ST53, NO), the processor 41 of the ticket gate 11 displays a message on the display 33 indicating that passage is not permitted, and closes the door 34. As a result, the processor 41 prevents the user from passing through the passage formed by the ticket gate 11, and ends the processing for that user.

Also, if a response is received from server 21 to the effect that passage is permitted (ST53, YES), processor 41 of ticket gate 11 determines, based on the response from server 21, whether or not to permit passage of multiple people with that ID (ST54).
If the door does not permit passage of multiple users (ST54, NO), the processor 41 controls passage so as to allow the user to pass through (ST55). For example, the processor 41 displays a message on the display 33 indicating that passage is permitted and opens the door 34 to allow one user to pass through. The processor 41 also notifies the server 21 that the user has passed through (ST58).

When multiple people are permitted to pass (ST54, YES), the processor 41 notifies the number of people available (ST55). For example, the processor 41 displays the number of people who can pass on the display 33. The processor 41 may also notify the number of people who can pass by voice from a speaker (not shown).

After reporting the number of available occupants, the processor 41 opens the door 34 to allow users to pass through (ST56), and detects the passage of each user based on the detection results of the human detection sensor 38 (ST57). If it detects that a user has passed through (ST57, YES), the processor 41 returns to ST50 and reads the code image again.

If the representative of a multi-user group continues to present a code image in the reading range, the ID reader 32 reads the same code image again and notifies the processor 41 of the code image reading result. When the processor 41 obtains the code information read by the ID reader 32, it executes the process from ST51 onwards again.

In addition, each time the server 21 receives the same ID from the same ticket gate consecutively, it updates the value of the counter indicating the remaining number of people who can use the ticket by decrementing the counter associated with that ID. This allows the server 21 to update the counter indicating the remaining number of people who can use the ticket gate each time a user passes through the ticket gate for an ID that can be used by multiple people, and to manage the number of people who have passed through the ticket gate with that ID.

The processor 41 of the ticket gate 11 may notify the server 21 that the user has passed when it detects that the user has passed. In this case, the server 21 may decrement a counter associated with the ID in response to the notification from the ticket gate 11.

By the above process, the processor 41 of the ticket gate 11 repeatedly executes the above-mentioned ST50-58 process until the counter corresponding to the ID managed by the server 21 reaches 0 (as long as there are remaining users managed by the server 21 corresponding to the ID). As a result, the ticket gate 11 is able to allow the number of users corresponding to the ID shown in the code image to pass through while the representative is presenting the code image. For example, the processor 41 controls the door of the ticket gate 11 to close when the number of people passing through the passage identified from the detection results of the human detection sensor 36 exceeds the number of users.

Processor 41 also counts the elapsed time while it is unable to detect the passage of the next user (ST57, NO). Processor 41 determines whether a timeout has occurred based on whether the elapsed time during which it is unable to detect the passage of a user exceeds a predetermined period (ST59). If a timeout has not occurred (ST59, NO), processor 41 continues to detect the passage of users. If a timeout has occurred (ST59, YES), processor 41 transmits information indicating that a timeout has occurred as a result of the passage to server 21 (ST58), and ends the series of ticket gate processing.

When the server 21 receives information indicating a timeout, it identifies the number of people who actually passed through from the value of the counter corresponding to the ID, and records the number of people who actually passed through as entry information or exit information. This allows the server 21 to manage the number of people who actually passed through as entry information or exit information.

In the second operation example described above, the ticket gate transmits the ID contained in the code information indicating the presented code image to the server, and obtains from the server the result of a determination as to whether or not passage is permitted based on the usage information corresponding to the ID. If the number of users in the usage information corresponding to the ID received from the ticket gate is multiple, the server counts the number of people consecutively permitted to pass with the same ID, and permits passage for the number of users. Each time a user passes through in response to permission to pass from the server, the ticket gate re-reads the code image and transmits the ID to the server. As a result, while the code image is being presented, the ticket gate 11 permits passage for the number of users registered corresponding to the ID indicated by the code image.

When a group of multiple people uses a ticket gate, a representative of the group (for example a family) can present a code image to the ticket gate while everyone else in the group passes through, allowing everyone other than the representative to pass through the ticket gate without having to individually present a code image. As a result, users such as children or elderly people who pass through after the representative can pass through the ticket gate smoothly even without having to carry a mobile device to display the code image.

In the second operation example, while the representative is presenting the code image, the number of users is allowed to pass through, so it is also possible to let group members pass discontinuously. Also, if someone other than a group member cuts in line, the representative can prevent the other person from passing through by removing the code image from the reading range.

Next, a modification of the second operation example will be described.
In the second operation example described above, even if there are multiple users, the representative presents one code image that encodes information including one ID corresponding to the usage information, but in a modified version of the second operation example (method B), the code images presented by the representative are issued for the number of users.

In a variation of the second operation example, the server 21 manages information indicated by code images for the number of users, linked to one ID corresponding to the usage information. For example, the server 21 issues usage IDs for the number of users linked to one ID (e.g., a representative ID) corresponding to the usage information, generates code images for the number of users that encode information including the usage ID, and provides the code images for the number of users to the representative.

Such a modified example of the second operation example can be realized by a process flow similar to that shown in FIG. 9. For example, the ticket gate 11 reads the usage ID from the code image in ST50 and transmits the usage ID to the server 21, and the server 21 identifies one ID that corresponds to the usage information linked to the usage ID received from the ticket gate 11. This allows a process similar to that shown in FIG. 9 to be realized.

Even with this variation of the second operation example, the representative can present a code image to the ticket gate, allowing people other than the representative to pass without having to present code images individually, achieving smooth entry and exit processing for multiple people. Furthermore, with the variation of the second operation example, the representative can sequentially present code images for the number of users displayed on the mobile device, allowing the number of users to pass through, making it possible to allow group members to pass through discontinuously and making it easy to prevent people other than group members from cutting in line.

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.
The following appended claims clarifying what was stated in the scope of the claims as originally filed.
[1]
A communication unit that communicates with a server that holds usage information associated with the ID;
an ID reader for reading an ID from a mobile terminal;
a processor that transmits the ID read by the ID reader to the server via the communication unit, obtains from the server information indicating the number of users that can be used according to the usage information corresponding to the ID, and permits people equal to or less than the number of users to pass through the passage;
A ticket gate having the above structure.
[2]
the ID reader is a code reader that reads code information including an ID indicated by a code image displayed by the mobile terminal;
The ticket gate described in [1].
[3]
the processor allows the number of people to pass through the passage consecutively after the ID reader reads the ID from the mobile terminal;
A ticket gate according to any one of [1] or [2].
[4]
a counter in which the number of users acquired from the server is set;
the processor subtracts a value of the counter every time a person passes through the passage after the ID reader reads the ID from the portable terminal, and allows the person to pass through the passage until the value of the counter becomes 0.
The ticket gate according to [3].
[5]
Further, a notification unit is provided for notifying information indicating the remaining number of people available as indicated by the counter.
The ticket gate according to [4].
[6]
When the number of users acquired from the server is more than one, the processor causes the ID reader to re-read an ID from the portable terminal and transmit the ID to the server every time a person passes through the passage, and acquires information indicating the remaining number of available users from the server.
The ticket gate described in [1].
[7]
Further, a notification unit is provided that notifies the user of the information indicating the number of users every time the information indicating the number of users is acquired from the server.
The ticket gate described in [6].

1...Ticket gate system, 11...Ticket gate, 12...Staff terminal, 21...Server, 32...ID reader (code reader), 33...Display, 41...Processor, 43...RAM (counter), 45...Communication unit.

Claims (3)

A communication unit that communicates with a server that holds usage information associated with the ID;
an ID reader for reading an ID from a mobile terminal;
a processor that transmits the ID read by the ID reader to the server via the communication unit, obtains from the server information indicating the number of users that can be used according to the usage information corresponding to the ID, and permits people equal to or less than the number of users to pass through the passageway ;
When the number of users acquired from the server is more than one, the processor causes the ID reader to re-read an ID from the portable terminal and transmit the ID to the server every time a person passes through the passage, and acquires information indicating the remaining number of available users from the server.
Ticket machine. the ID reader is a code reader that reads code information including an ID indicated by a code image displayed by the mobile terminal;
The ticket gate according to claim 1. Further, a notification unit is provided that notifies the user of the information indicating the number of users every time the information indicating the number of users is acquired from the server.
The ticket gate according to claim 1.