JP2019160201A - Exit device and ticket examination system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a participation device and a ticket gate system capable of improving convenience for a user. The entry device of the embodiment includes a first acquisition unit, a communication unit, a second acquisition unit, a match determination unit, and a first settlement unit. The first acquisition unit acquires identification information from a medium for using the payment service. The communication unit transmits the identification information acquired by the first acquisition unit to the server device, and receives the amount of the charge specified by the transmitted identification information from the server device. The second acquisition unit acquires the identification information from the medium for using the payment service. The match determination unit determines whether or not the identification information acquired by the first acquisition unit and the identification information acquired by the second acquisition unit match. The first settlement unit uses the settlement service to perform settlement processing for the amount of the charge when it is determined by the determination unit to match, and does not perform settlement processing when it is determined by the determination unit that they do not match. [Selection diagram] Fig. 1

Description

  Embodiments described herein relate generally to a participation apparatus and a ticket gate system.

  Traffic that can be used to write information on entrance stations (stops in the case of buses), information on participating stations, and information on the sections available to users (regular sections and charge amounts) in transportation such as rail or bus IC (Integrated Circuit) cards are used. However, in the conventional technique, there is a case where an IC card in which an area for writing information of an entrance station or the like is not set cannot be used in a ticket gate.

JP 2014-63216 A

  The problem to be solved by the embodiment of the present invention is to provide a participation device and a ticket gate system that can improve convenience for the user.

  The participation apparatus of the embodiment is used when entering from an area where a fee is required for entry and exit. The participation apparatus of the embodiment includes a first acquisition unit, a communication unit, a second acquisition unit, a match determination unit, and a first settlement unit. The first acquisition unit acquires identification information from a medium for using the payment service. The communication unit receives the amount of the fee specified by the transmitted identification information from the server device by transmitting the identification information acquired by the first acquisition unit to the server device. The second acquisition unit acquires identification information from a medium for using the payment service. The coincidence determination unit determines whether or not the identification information acquired by the first acquisition unit matches the identification information acquired by the second acquisition unit. The first settlement unit performs a settlement process for the amount of the fee using the settlement service when it is determined by the determination unit to match, and the settlement process when the determination unit determines that they do not match Do not do.

The figure which shows an example of the whole structure of the ticket gate system which concerns on 1st Embodiment-4th Embodiment. The figure which shows an example of a structure and function of the medium which concern on 1st Embodiment-4th Embodiment. The figure which shows an example of the external appearance structure of the ticket gate unit which concerns on 1st Embodiment-4th Embodiment. The block diagram which shows an example of the principal part circuit structure and functional structure of the ticket gate system which concerns on 1st Embodiment-3rd Embodiment, and the automatic ticket gate and payment terminal which are included in the said ticket gate system. The block diagram which shows an example of the principal part circuit structure and functional structure of the center server which concern on 1st Embodiment and 2nd Embodiment. The block diagram which shows an example of the principal circuit structure and functional structure of the electronic money server which concern on 1st Embodiment-4th Embodiment. The figure which shows an example of the outline | summary of a process of the ticket gate system which concerns on 1st Embodiment. The figure which shows an example of the content of the management table. The flowchart of the process by the processor of the automatic ticket gate which concerns on 1st Embodiment-4th Embodiment. The flowchart of the process by the processor of the automatic ticket gate which concerns on 1st Embodiment. The flowchart of the process by the processor of the payment terminal which concerns on 1st Embodiment. The flowchart of the process by the processor of the center server which concerns on 1st Embodiment and 2nd Embodiment. The flowchart of the process by the processor of the automatic ticket gate which concerns on 2nd Embodiment. The flowchart of the process by the processor of the payment terminal which concerns on 2nd Embodiment. The figure which shows an example of the content of the management table. The figure which shows an example of the content of the adjustment table. The figure which shows the principal circuit structure and functional structure of the automatic ticket gate which concern on 3rd Embodiment. The figure which shows the principal circuit structure and functional structure of the payment terminal which concern on 3rd Embodiment and 4th Embodiment. The figure which shows the principal part circuit structure and functional structure of the center server which concern on 3rd Embodiment. The block diagram which shows an example of the principal part circuit structure and functional structure of the ticket gate system which concerns on 4th Embodiment, and the automatic ticket gate and payment terminal which are included in the said ticket gate system. The figure which shows the principal circuit structure and functional structure of the automatic ticket gate which concerns on 4th Embodiment. The figure which shows the principal part circuit structure and functional structure of the center server which concern on 4th Embodiment.

  Hereinafter, ticket gate systems according to some embodiments will be described with reference to the drawings. The ticket gate system of the embodiment is a system that manages entrance / exit of a station or boarding / exiting of a bus or the like in a transportation system such as a railway, a bus, an aircraft, or a ship. Alternatively, the ticket gate system of the embodiment may be a system that manages entrance / exit other than transportation. In the following description, an example in which the ticket gate system is applied at a railway station will be described.

[First Embodiment]
(overall structure)
FIG. 1 is a diagram illustrating an example of the overall configuration of the ticket gate system 1 according to the first embodiment. The ticket gate system 1 includes, for example, an A station system 10A, a B station system 10B, a center server 50, an electronic money server 70, and a store settlement terminal 100. In addition, when not distinguishing A station system 10A and B station system 10B, it is only called "the station system 10" below. Moreover, in each figure and below, "A" is attached | subjected to the end of the code | symbol of the structure contained in A station system 10A, and "B" is attached | subjected and shown to the code | symbol of the structure contained in B station system 10B. Yes. In addition, in the case where it is not distinguished which station system is included, “A” or “B” is omitted. Although FIG. 1 shows a station system 10 of two stations, A station and B station, the ticket gate system 1 typically includes more stations and station systems 10.

The station system 10 includes an automatic ticket gate 30 and a payment terminal 40. The automatic ticket gate 30 and the payment terminal 40 communicate via a dedicated line or wireless.
Further, the station system 10 includes a station server, an automatic ticket vending machine, station equipment, and the like. The station server transmits information acquired from the center server 50 via the network NW1 to the automatic ticket gate 30 via a dedicated line, a public line, a LAN (local area network), or the like. Further, the station server transmits information acquired from the automatic ticket gate 30 via a dedicated line, public line, LAN, or the like to the center server 50 via the network NW1. The network NW1 is typically a communication network including the Internet. The network NW1 is typically a communication network including a WAN (wide area network). The network NW1 may be a communication network including a private network such as an intranet. The network NW1 may be a communication network including a LAN. The network NW1 may be a wireless line or a wired line, and a wireless line and a wired line may be mixed. The network NW1 may be a communication network including a dedicated line or a public mobile phone network.

  The payment terminal 40 communicates with the electronic money server 70 via the network NW2, for example. Note that the payment terminal 40 may communicate via a station server. The network NW2 is typically a communication network including the Internet. The network NW2 is typically a communication network including a WAN. The network NW2 may be a communication network including a private network such as an intranet. The network NW2 may be a communication network including a LAN. The network NW2 may be a wireless line or a wired line, and a wireless line and a wired line may be mixed. The network NW2 may be a communication network including a dedicated line or a public mobile phone network. The network NW1 and the network NW2 may be partly or entirely the same communication network. Alternatively, the network NW1 and the network NW2 may be connected.

(Medium)
Here, the medium M used in the ticket gate system 1 of the present embodiment will be described. The medium M is a medium used for using a payment service such as electronic money. The medium M is, for example, an IC card. In the medium M, for example, the settlement service ID is written. The medium M used for using the electronic money service is further written with a charge amount. The payment service that can be used depending on the medium M is not limited to the electronic money service, but may be various payment services such as a prepaid type, a postpay type, and a debit type. In the embodiment, a case where an electronic money service is used as a settlement service will be described as a main example.

FIG. 2 is a diagram illustrating an example of the configuration and functions of the medium M. The medium M is a medium having a wireless communication function as an example. The medium M includes, for example, a base material M2, a chip M3, and an antenna M4. The base material M2 has, for example, a card shape. The chip M3 is, for example, a passive type IC chip. The chip M3 communicates with the automatic ticket gate 30 by non-contact communication using RFID (radio frequency identifier) or the like. For example, the chip M3 executes processing based on a command response method in which information is transmitted in response to a command (signal) transmitted by the automatic ticket gate 30. The chip M3 includes, for example, a transmission / reception unit M5, a control circuit M6, a storage unit M7, and the like. The transmission / reception unit M5 demodulates information included in the radio wave transmitted by the automatic ticket checker 30, generates a radio wave for superimposing information, and superimposes the information on the generated radio wave.

  The control circuit M6 includes, for example, a processor such as a CPU (central processing unit). The control circuit M6 writes information in the storage unit M7 and reads information written in the storage unit M7 according to the content of the command transmitted by the automatic ticket gate 30. The control circuit M6 reads information stored in the storage unit M7. Then, the control circuit M6 transmits the read information to the automatic ticket gate 30 using the antenna M4 and the transmission / reception unit M5.

  In the storage unit M7, a program executed by the control circuit M6, a medium ID, a charge amount (payment amount) of electronic money, and the like are encoded and stored. This will be specifically described below. For example, a first storage area AR1 and a second storage area AR2 are set in the storage unit M7. In the first storage area AR1, for example, identification information of the medium M (hereinafter referred to as “medium ID”) is stored. The medium ID is identification information given to each chip M3 of the medium M regardless of the electronic money service managed in the medium M. The medium ID is information acquired by performing communication with the chip M3 using a predetermined protocol.

In the second storage area AR2, information related to the electronic money service is stored. The information related to the electronic money service is acquired or rewritten by performing communication using a protocol corresponding to the electronic money service by a device having an access right corresponding to the electronic money service.
The information related to the electronic money service includes a service ID, a charge amount, and a usage history. The service ID is an ID managed by the administrator of the electronic money service.

  Further, at least an area for writing a medium ID is set for the medium M. The medium M does not have to be set with an area for writing information on the user's entry station, information on the entry station, or the charge amount. In this case, the charge amount is managed on the electronic money server 70 side. Note that the medium M may store information related to a plurality of types of electronic money services.

  Further, as the medium M, an electronic device such as a mobile phone having a card emulation function may be used. The electronic device includes an IC chip and an antenna for non-contact communication.

(Automatic ticket gates and payment terminals)
FIG. 3 is a diagram illustrating an example of an external configuration of the ticket gate unit 20 according to the first embodiment. The ticket gate unit 20 is installed at a station or the like for entry into or exit from the station ticket gate. The inside of the ticket gate is an example of an area that requires a fee for entry and exit. Buses are examples of areas that require a fee for entry and exit.
The ticket gate unit 20 includes, for example, an automatic ticket gate 30 and a payment terminal 40 as shown in FIG. The ticket gate unit 20 is supported by the support body 22, for example. The ticket gate unit 20 includes an automatic ticket gate 30 and a payment terminal 40. The ticket gate unit 20 is not limited to entering and exiting, and may be installed for transferring to another company's route. As an example, the ticket gate unit 20 is installed separately so as to know whether it is for entry or for entry. The entrance ticket gate unit 20, the entrance ticket gate unit 20, and the transfer ticket gate unit 20 may have the same configuration or different configurations. For example, in the entrance or transfer ticket gate unit 20, the payment terminal 40 may be omitted. The ticket gate unit 20 may be configured such that the automatic ticket checker 30 and the payment terminal 40 are configured in separate casings, and the automatic ticket checker 30 and the payment terminal 40 are connected by a cable or wireless. The entrance ticket gate unit 20 is an example of an entrance device that is used when entering an area that requires a fee for entry and exit. The ticket gate unit 20 for participation is an example of an entry device used when entering from an area that requires a fee for entry and exit.

  The ticket gate unit 20 includes an entrance / exit reader 38 of the automatic ticket gate 30 and a payment reader 47 of the payment terminal 40. The entrance / exit reader 38 and the settlement reader 47 are provided at positions where the user can touch the medium M. The entrance / exit leader 38 holds the medium M by a user who tries to pass in the direction A in FIG. 3 (the direction from the front side to the back side). Then, the medium M receives various processes inside the automatic ticket gate 30. The various processes will be described later. In addition, the medium M is again deceived in the settlement reader 47 by the user who deceives the medium M as the entrance / exit leader 38. Then, the medium M receives various processes inside the payment terminal 40. The various processes will also be described later. Further, as an example, the ticket gate unit 20 includes a touch panel 37 that displays a processing result of the automatic ticket gate 30 between the entrance / exit reader 38 and the payment reader 47.

  In FIG. 3, the automatic ticket gate 30 is described as an IC card dedicated machine. However, the automatic ticket gate 30 includes an IC card, a code ticket such as a QR (registered trademark) code, a magnetic ticket, or a paper ticket. And a combination machine capable of processing both. Further, the automatic ticket gate 30 is not limited to permitting the user to pass only in both directions, but may be permitted to allow the user to pass in one direction. Moreover, the automatic ticket gate 30 may be provided with a door or a bar that opens and closes depending on whether or not traffic is permitted.

  FIG. 4 is a block diagram illustrating an example of a main circuit configuration and a functional configuration of the ticket gate system 1 and the automatic ticket gate 30 and the payment terminal 40 included in the ticket gate system 1 according to the first embodiment.

  As an example, the automatic ticket gate 30 includes a processor 31, a ROM (read-only memory) 32, a RAM (random-access memory) 33, an auxiliary storage device 34, a first communication unit 35, a second communication unit 36, a touch panel. 37 and an entry / exit leader 38.

  The processor 31 corresponds to a central part of a computer that performs processing such as calculation and control necessary for the operation of the automatic ticket gate 30. The processor 31 controls each unit to implement various functions of the automatic ticket checker 30 based on a program such as system software, application software, or firmware stored in the ROM 32 or the auxiliary storage device 34. The processor 31 includes, for example, a CPU, a micro processing unit (MPU), a system on a chip (SoC), a digital signal processor (DSP), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), and a programmable logic device (PLD). ) Or FPGA (field-programmable gate array). Alternatively, the processor 31 is a combination of a plurality of these.

  The ROM 32 corresponds to a main storage device of a computer having the processor 31 as a center. The ROM 32 is a non-volatile memory used exclusively for reading data. The ROM 32 stores the above program. The ROM 32 stores data used for the processor 31 to perform various processes, various setting values, and the like.

  The RAM 33 corresponds to a main storage device of a computer having the processor 31 as a center. The RAM 33 is a memory used for reading and writing data. The RAM 33 is used as a so-called work area that stores data temporarily used when the processor 31 performs various processes.

  The auxiliary storage device 34 corresponds to an auxiliary storage device of a computer having the processor 31 as a center. The auxiliary storage device 34 is, for example, an EEPROM (electrically erasable programmable read-only memory), an HDD (hard disk drive), or an SSD (solid state drive). The auxiliary storage device 34 may store the above program. In addition, the auxiliary storage device 34 stores data used when the processor 31 performs various processes, data generated by the process in the processor 31, various setting values, and the like.

  The program stored in the ROM 32 or the auxiliary storage device 34 includes a program for executing processing to be described later. As an example, the automatic ticket checker 30 is transferred to an administrator of the automatic ticket checker 30 or the like with the program stored in the ROM 32 or the auxiliary storage device 34. However, the automatic ticket gate 30 may be transferred to the administrator or the like in a state where the program is not stored in the ROM 32 or the auxiliary storage device 34. The automatic ticket gate 30 may be transferred to the administrator or the like in a state where a program different from the program is stored in the ROM 32 or the auxiliary storage device 34. A program for executing processing to be described later may be separately transferred to the administrator or the like, and written to the ROM 32 or the auxiliary storage device 34 under the operation of the administrator or a serviceman. Transfer of the program at this time can be realized, for example, by recording it on a removable storage medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by downloading via a network NW1.

  The first communication unit 35 is a communication interface provided for the automatic ticket gate 30 to communicate with the center server 50 and the like via the network NW1 and the like, for example. The first communication unit 35 is an example of a communication unit.

  The second communication unit 36 is a communication interface provided for the automatic ticket gate 30 to communicate with the payment terminal 40, for example.

  As an example, the touch panel 37 is formed by laminating a display unit 371 and an input unit 372. The display unit 371 is a display such as a liquid crystal display or an organic EL display, for example. The display unit 371 displays a screen for notifying the operator of the automatic ticket gate 30 of various information. The input unit 372 is a pointing device such as a touch pad, for example. The input unit 372 receives a touch operation by an operator of the automatic ticket gate 30.

  The entrance / exit leader 38 communicates with a medium M or the like that has been deceived by a railway user. Thereby, the entrance / exit reader 38 acquires various information such as the medium ID stored in the medium M. The entrance / exit reader 38 may have a function of writing information on the medium M. The entrance / exit leader 38 included in the entrance ticket gate unit 20 is an example of a first acquisition unit. The entrance / exit leader 38 provided in the entrance ticket gate unit 20 is an example of a third acquisition unit.

For example, the processor 31 functions as a determination unit 311 and a communication control unit 312 based on a program stored in the ROM 32 or the auxiliary storage device 34.
The determination unit 311 stores the medium ID acquired by the entrance / exit reader 38 in the RAM 33 or the auxiliary storage device 34. Then, the determination unit 311 determines whether the IDs match.
The communication control unit 312 controls the first communication unit 35 to transmit the medium ID acquired by the entrance / exit reader 38 to the center server 50. In addition, the communication control unit 312 causes the first communication unit 35 to receive the fare information indicating the use fare of the railway transmitted by the center server 50.
In addition, the communication control unit 312 controls the second communication unit 36 so that the fare information received by the first communication unit 35 is transmitted to the payment terminal 40.

  The payment terminal 40 includes, as an example, a processor 41, a ROM 42, a RAM 43, an auxiliary storage device 44, a first communication unit 45, a second communication unit 46, and a payment reader 47. The payment terminal 40 provided in the ticket gate unit 20 for participation is an example of a first payment unit. The payment terminal 40 provided in the entrance ticket gate unit 20 is an example of a second payment unit.

  The processor 41 corresponds to a central part of a computer that performs processing such as calculation and control necessary for the operation of the payment terminal 40. The processor 41 controls each unit to realize various functions of the payment terminal 40 based on a program such as system software, application software, or firmware stored in the ROM 42 or the auxiliary storage device 44. The processor 41 is, for example, a CPU, MPU, SoC, DSP, GPU, ASIC, PLD, or FPGA. Alternatively, the processor 41 is a combination of a plurality of these.

  The ROM 42 corresponds to a main storage device of a computer having the processor 41 as a center. The ROM 42 is a non-volatile memory used exclusively for reading data. The ROM 42 stores the above program. Further, the ROM 42 stores data used for the processor 41 to perform various processes or various setting values.

  The RAM 43 corresponds to a main storage device of a computer having the processor 41 as a center. The RAM 43 is a memory used for reading and writing data. The RAM 43 is used as a so-called work area that stores data temporarily used when the processor 41 performs various processes.

  The auxiliary storage device 44 corresponds to an auxiliary storage device of a computer having the processor 41 as a center. The auxiliary storage device 44 is, for example, an EEPROM, HDD, or SSD. The auxiliary storage device 44 may store the above program. In addition, the auxiliary storage device 44 stores data used when the processor 41 performs various processes, data generated by the processes in the processor 41, various setting values, and the like.

  The program stored in the ROM 42 or the auxiliary storage device 44 includes a program for executing processing to be described later. As an example, the payment terminal 40 is transferred to an administrator of the payment terminal 40 or the like with the program stored in the ROM 42 or the auxiliary storage device 44. However, the payment terminal 40 may be transferred to the administrator or the like in a state where the program is not stored in the ROM 42 or the auxiliary storage device 44. The payment terminal 40 may be transferred to the administrator or the like in a state where a program different from the program is stored in the ROM 42 or the auxiliary storage device 44. A program for executing processing to be described later may be separately transferred to the administrator or the like, and written to the ROM 42 or the auxiliary storage device 44 under the operation of the administrator or a serviceman. Transfer of the program at this time can be realized, for example, by recording on a removable storage medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by downloading via a network NW2.

  The first communication unit 45 is, for example, a communication interface provided for the payment terminal 40 to communicate with the electronic money server 70 or the like via the network NW2 or the like.

  The second communication unit 46 is a communication interface provided for the payment terminal 40 to communicate with the automatic ticket gate 30, for example.

  The settlement reader 47 communicates with the medium M and the like. As a result, the settlement reader 47 acquires the medium ID and the charge amount stored in the medium M. The payment reader 47 may have a function of writing information to the medium M. The settlement reader 47 provided in the ticket gate unit 20 for participation is an example of a second acquisition unit. The settlement reader 47 provided in the entrance ticket gate unit 20 is an example of a fourth acquisition unit.

For example, the processor 41 functions as the determination unit 411 and the settlement control unit 412 based on a program stored in the ROM 42 or the auxiliary storage device 44.
The determination unit 411 compares the medium ID received by the second communication unit 46 with the medium ID received by the settlement reader 47 and determines whether the two medium IDs match.
The settlement control unit 412 performs control related to fare settlement using the electronic money service managed in the medium M.

(Center server)
FIG. 5 is a diagram illustrating a circuit configuration and a functional configuration of a main part of the center server. As an example, the center server 50 includes a processor 51, a ROM 52, a RAM 53, a communication unit 54, and a center server storage unit 60. The center server 50 is an example of a server device.

  The processor 51 corresponds to a central portion of a computer that performs processing such as calculation and control necessary for the operation of the center server 50. The processor 51 controls each unit to realize various functions of the center server 50 based on a program such as system software, application software, or firmware stored in the ROM 52 or the like. The processor 51 is, for example, a CPU, MPU, SoC, DSP, GPU, ASIC, PLD, or FPGA. Alternatively, the processor 51 is a combination of a plurality of these.

  The ROM 52 corresponds to a main storage device of a computer having the processor 51 as a center. The ROM 52 is a non-volatile memory used exclusively for reading data. The ROM 52 stores the above program. The ROM 52 stores data used for the processor 51 to perform various processes, various setting values, and the like.

  The RAM 53 corresponds to a main storage device of a computer having the processor 51 as a center. The RAM 53 is a memory used for reading and writing data. The RAM 53 is used as a so-called work area that stores data temporarily used when the processor 51 performs various processes.

  The communication unit 54 is a communication interface provided for the center server 50 to communicate with the automatic ticket checker 30 and the like via the network NW1 and the like, for example.

  The center server storage unit 60 corresponds to an auxiliary storage device of a computer having the processor 51 as a center. The center server storage unit 60 is, for example, an EEPROM, HDD, or SSD. The center server storage unit 60 may store the above program. The center server storage unit 60 stores data used when the processor 41 performs various processes, data generated by the process of the processor 51, various setting values, and the like. The center server storage unit 60 is an example of a first storage unit. The center server storage unit 60 is an example of a second storage unit.

  The center server storage unit 60 stores a fare table 61 and a management table 62. The fare table 61 is a table that stores information necessary to derive a fare between stations or a fare between stations. The management table 62 will be described later.

  The program stored in the ROM 52 or the center server storage unit 60 includes a program for executing processing to be described later. As an example, the center server 50 is transferred to an administrator of the center server 50 or the like with the program stored in the ROM 52 or the center server storage unit 60. However, the center server 50 may be transferred to the administrator or the like in a state where the program is not stored in the ROM 52 or the center server storage unit 60. The center server 50 may be transferred to the administrator or the like in a state where a program different from the program is stored in the ROM 52 or the center server storage unit 60. A program for executing processing to be described later may be separately transferred to the administrator or the like, and written into the ROM 52 or the center server storage unit 60 under the operation of the administrator or a serviceman. Transfer of the program at this time can be realized, for example, by recording it on a removable storage medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by downloading via a network NW1.

For example, the processor 51 functions as an information management unit 511 and a fare deriving unit 512 based on a program stored in the ROM 52 or the center server storage unit 60.
The information management unit 511 controls the communication unit 54 to receive information transmitted by the automatic ticket gate 30. The information management unit 511 manages the information received by the communication unit 54 using the management table 62. In addition, the information management unit 511 controls the communication unit 54 to transmit the railway use fare derived by the fare deriving unit 512 to the automatic ticket gate 30 of the participating station.
The fare deriving unit 512 refers to the fare table 61 and derives the fare between the stations from the entry station to the departure station of the user.

(Electronic money server)
The electronic money server 70 is a device that manages electronic money services.
As an example, the electronic money server 70 includes a processor 71, a ROM 72, a RAM 73, a communication unit 74, and an electronic money server storage unit 80.

  The processor 71 corresponds to a central part of a computer that performs processing such as calculation and control necessary for the operation of the electronic money server 70. The processor 71 controls each unit to implement various functions of the electronic money server 70 based on a program such as system software, application software, or firmware stored in the ROM 72 or the electronic money server storage unit 80. The processor 71 is, for example, a CPU, MPU, SoC, DSP, GPU, ASIC, PLD, or FPGA. Alternatively, the processor 71 is a combination of a plurality of these.

  The ROM 72 corresponds to a main storage device of a computer having the processor 71 as a center. The ROM 72 is a non-volatile memory used exclusively for reading data. The ROM 72 stores the above program. The ROM 72 stores data used for the processor 71 to perform various processes or various setting values.

  The RAM 73 corresponds to a main storage device of a computer having the processor 71 as a center. The RAM 73 is a memory used for reading and writing data. The RAM 73 is used as a so-called work area that stores data temporarily used when the processor 71 performs various processes.

  The communication unit 74 is a communication interface provided for the electronic money server 70 to communicate with the payment terminal 40 via the network NW2 or the like, for example.

  The electronic money server storage unit 80 corresponds to an auxiliary storage device of a computer having the processor 71 as a center. The electronic money server storage unit 80 is, for example, an EEPROM, an HDD, or an SSD. The electronic money server storage unit 80 may store the above program. Further, the electronic money server storage unit 80 stores data used when the processor 71 performs various processes, data generated by the process in the processor 71, various setting values, and the like.

  The electronic money server storage unit 80 stores electronic money information 81. In the electronic money information 81, for example, the charge amount after use, the date and time when the medium M was used, the use amount of the medium M, the name of the business operator who used the medium M, etc. Information included.

  The program stored in the ROM 72 or the electronic money server storage unit 80 includes a program for executing processing to be described later. As an example, the electronic money server 70 is transferred to an administrator of the electronic money server 70 in a state where the program is stored in the ROM 72 or the electronic money server storage unit 80. However, the electronic money server 70 may be transferred to the administrator or the like in a state where the program is not stored in the ROM 72 or the electronic money server storage unit 80. The electronic money server 70 may be transferred to the administrator or the like in a state where a program different from the program is stored in the ROM 72 or the electronic money server storage unit 80. A program for executing processing to be described later may be separately transferred to the administrator or the like and written to the ROM 72 or the electronic money server storage unit 80 under the operation of the administrator or a serviceman. . Transfer of the program at this time can be realized, for example, by recording on a removable storage medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by downloading via a network NW2.

For example, the processor 71 functions as a payment management unit 711 based on a program stored in the ROM 72 or the electronic money server storage unit 80.
The payment management unit 711 manages the payment process performed by the payment terminal 40 using the electronic money information 81.

(Outline of ticket gate system processing)
FIG. 7 is a diagram illustrating an example of an outline of processing of the ticket gate system 1. When the user puts the medium M on the entrance / exit reader 38 at the entrance station, the automatic ticket gate 30 transmits the media ID and station ID read by the entrance reader 38 to the center server 50. The station ID is identification information uniquely assigned to each station. The station ID transmitted by the automatic ticket gate 30 is the station ID of the station where the automatic ticket gate 30 is installed. The automatic ticket gate 30 stores the station ID.

  The center server 50 manages the medium ID received from the automatic ticket checker 30 by the management table 62 as shown in FIG. FIG. 8 is a diagram showing an example of the contents of the management table 62. The management table 62 has an entrance station ID (entrance station ID), an entry time, an entry station ID (entrance station ID), an entry time, an entry station, and an entry station to an entry station. Associate fare and information (settlement status) indicating whether or not fare settlement has been completed. The entry / exit ID is identification information uniquely assigned to each entry / exit. In addition, the initial value of the settlement status is a value indicating unsettled.

  The information management unit 511 of the center server 50 acquires the medium ID, station ID, and time transmitted by the automatic ticket checker 30. For example, when the station ID is acquired in the management table 62 in a state where the station identification information is not associated with the medium ID in the management table 62, the information management unit 511 regards the station specified by the acquired station ID as an entrance station. The time when the station ID is acquired is regarded as the entrance time. Then, the information management unit 511 stores the acquired medium ID in the management table 62 in association with the station ID and the entry time.

As shown in FIG. 7, when the user puts the medium M in the entry / exit leader 38 at the entry station, the automatic ticket checker 30 uses the center server 50 to read the medium ID and the station ID read by the entry / exit leader 38. Send to.
When the information management unit 511 of the center server 50 acquires the station ID in a state where the station ID is associated with the medium ID as an entrance station, the information management unit 511 regards the station specified by the acquired station ID as the participating station, and The time when the ID is acquired is regarded as the entry time. Then, as illustrated in FIG. 8, the information management unit 511 stores the acquired station ID and the participation time in the management table 62 in association with the medium ID. Further, the fare deriving unit 512 refers to the fare table 61 and derives the fare from the entry station to the departure station. The information management unit 511 associates the fare derived by the fare deriving unit 512 with the medium ID as shown in FIG. Further, the information management unit 511 controls the communication unit 54 to transmit the fare to the automatic ticket checker 30 at the participating station.

The automatic ticket checker 30 that has received the fare transmits the received fare and the medium ID read from the medium M to the settlement terminal 40.
When the payment terminal 40 receives the fare and the medium ID from the automatic ticket checker, the payment terminal 40 executes a process for paying the fare, and the payment terminal 40 waits for the medium M to be deceived. In this state, when the user places the medium M on the settlement reader 47, the settlement reader 47 acquires the medium ID from the medium M. Then, the determination unit 411 compares the medium ID acquired by the payment reader 47 with the medium ID transmitted from the automatic ticket checker 30 and determines whether or not they match.

When the determination unit 411 determines that the medium IDs match, the payment control unit 412 performs payment for the fare using the electronic money managed by the medium M. For example, the settlement control unit 412 performs a process for subtracting the fare from the charge amount. Then, the payment terminal 40 transmits the payment details to the electronic money server 70. The settlement details include, for example, the deducted amount, the charged amount after deduction, and the name of the business company using the medium M. The payment terminal 40 also transmits the payment details to the center server 50.
The center server 50 that has received the payment details updates the management table 62 and sets the value of the payment status to a value indicating that payment has been completed.

  When the electronic money server 70 receives the payment details, it updates the electronic money information 81. The electronic money information 81 includes, for example, information in which the charge amount after use, the date and time of use, the use amount, and the used business name are associated with the medium ID. When the payment details are acquired, the payment management unit 711 manages the usage status of the medium M by updating the electronic money information 81 based on the payment details. Thereby, the fare is paid by the electronic money managed by the medium M, and the entry / exit processing of the user is completed.

  On the other hand, when the determination unit 411 determines that the medium IDs do not match, the determination unit 411 transmits to the automatic ticket gate 30 mismatch information indicating that the medium ID does not match and payment has not been completed. The automatic ticket checker 30 that has received the mismatch information displays on the display unit 371 that the payment has not been completed, and prompts the user to touch the correct medium M on the payment reader 47. At this time, the user may be prompted to touch the entrance / exit leader 38 and start over from the fare derivation.

(Operation)
Hereinafter, the operation of the ticket gate system 1 according to the first embodiment will be described with reference to FIGS. Note that the content of the processing in the following description of the operation is an example, and various processing that can obtain the same result can be used as appropriate. Therefore, the processing in the following operation description may have a different part from that described in the outline of the processing of the above-described ticket gate system. 9 and 10 are flowcharts of processing by the processor 31 of the automatic ticket gate 30. FIG. The processor 31 executes this processing based on a program stored in the ROM 32 or the auxiliary storage device 34. FIG. 11 is a flowchart of processing by the processor 41 of the payment terminal 40. The processor 41 executes this processing based on a program stored in the ROM 42 or the auxiliary storage device 44. FIG. 12 is a flowchart of processing by the processor 51 of the center server 50. The processor 51 executes this processing based on a program stored in the ROM 52 or the like. When the processor 31, the processor 41, or the processor 51 proceeds to step S (N + 1) after the process of step S (N (N is a natural number)), a description explaining this may be omitted.

  In step S101 in FIG. 9, the processor 31 of the automatic ticket checker 30 turns the entrance / exit reader 38 into an ON state in which the medium M can be read. Further, the processor 31 may illuminate a light source such as an LED (light-emitting diode) provided in the vicinity of the entrance / exit reader 38 to indicate that the entrance / exit reader 38 can read the medium M. good. Further, the processor 31 displays on the display unit 371 a screen including content indicating that the entrance / exit reader 38 can read the medium M or instructing the entrance / exit reader 38 to pick up the medium M. It may be displayed.

  In step S <b> 102, the processor 31 waits for the medium M to approach the entrance / exit leader 38 using the entrance / exit leader 38. If the medium M has approached the entrance / exit reader 38, the processor 31 determines Yes in step S102 and proceeds to step S103.

  In step S <b> 103, the processor 31 controls the entry / exit reader 38 to obtain the medium ID stored in the medium M from the medium M close to the entry / exit reader 38.

  In step S104, the processor 31 sets the entrance / exit reader 38 to an off state in which the medium M cannot be read. Further, the processor 31 may turn off a light source such as an LED provided in the vicinity of the entrance / exit reader 38 in order to indicate that the entrance / exit reader 38 cannot read the medium M. In addition, the processor 31 displays a screen including content indicating that the entrance / exit leader 38 cannot read the medium M, or instructing the entrance / exit reader 38 to wait for a while for the media M to be read. You may display on the part 371.

  In step S105, the processor 31 determines whether or not the automatic ticket gate 30 is installed for entrance. It is assumed that the automatic ticket gate 30 can be set for two types of entry and entry. An entry set for entry is set for entry, and an entry set for entry is set for entry. Shall. The setting is changed by, for example, an administrator of the automatic ticket gate 30. Which setting is made is recorded in the auxiliary storage device 34, for example. If the automatic ticket gate 30 is installed for entry, the processor 31 determines Yes in step S105 and proceeds to step S106.

  In step S106, the processor 31 generates an entrance request. The admission request includes the medium ID acquired in step S103 and the station ID of the station where the automatic ticket gate 30 is installed. The admission request requests the center server 50 to perform processing necessary for the owner of the medium M specified by the medium ID to enter the station specified by the station ID. After generating the entrance request, the processor 31 instructs the first communication unit 35 to transmit the entrance request to the center server 50. Upon receiving this instruction, the first communication unit 35 transmits the admission request to the center server 50. The transmitted entry request is received by the communication unit 54 of the center server 50.

  On the other hand, in step S301 in FIG. 12, the processor 51 of the center server 50 waits for the communication unit 54 to receive an entry request or an emergency for entry. If the admission request is received, the processor 51 determines Yes in step S301 and proceeds to step S302. The medium ID included in the entry request or participation request received here is hereinafter referred to as “reception medium ID”, and the station ID included in the entry request or participation request is hereinafter referred to as “reception station ID”. The participation request will be described later.

  In step S302, the processor 51 determines whether or not the request received in step S301 is an entrance request. If the received request is an admission request, the processor 51 determines Yes in step S302 and proceeds to step S303.

  In step S303, the processor 51 performs an entrance process. That is, the processor 51 adds a new record to the management table 62. In this record, the medium ID value is the reception ID, the entry station ID value is the reception station ID, and the entry time value is the current time. Thereby, it is recorded that the owner of the medium M specified by the reception medium ID has already entered the ticket gate.

  In step S304, the processor 51 instructs the communication unit 54 to transmit an entrance notification to the automatic ticket gate 30 that is the sender of the entrance request. The entrance notification notifies the automatic ticket gate 30 that the entrance process has been completed. Upon receiving this instruction, the communication unit 54 transmits the admission notification to the automatic ticket gate 30 that is the transmission source of the admission request. The transmitted entry notification is received by the first communication unit 35 of the automatic ticket gate 30. The processor 51 returns to step S301 after the process of step S304.

  On the other hand, in step S107 of FIG. 9, the processor 31 of the automatic ticket checker 30 waits for the first communication unit 35 to receive an entrance notification. If the entry notification is received, the processor 31 determines Yes in step S107 and proceeds to step S108.

  In step S108, the processor 31 notifies that the entrance process has been normally performed. For example, the processor 31 causes the display unit 371 to display a screen including content indicating that the entrance process has been normally performed and content indicating that the medium M has been normally read. For example, the processor 31 outputs a sound indicating that the entrance process has been normally performed from a speaker or the like. The processor 31 returns to step S101 of FIG. 9 after the process of step S108.

On the other hand, if the automatic ticket gate 30 is installed for participation, the processor 31 determines No in step S105 and proceeds to step S109 in FIG.
In step S109, the processor 31 generates a participation request. The participation request includes the medium ID acquired in step S103 and the station ID of the station where the automatic ticket gate 30 is installed. The participation request is for requesting the center server 50 to perform processing necessary for the owner of the medium M specified by the medium ID to participate in the station specified by the station ID. After generating the participation request, the processor 31 instructs the first communication unit 35 to transmit the participation request to the center server 50. In response to this instruction, the first communication unit 35 transmits the participation request to the center server 50. The transmitted participation request is received by the communication unit 54 of the center server 50.

  On the other hand, if the participation request is received, the processor 51 of the center server 50 determines Yes in step S301 and proceeds to step S302. If the received request is an entry request, the processor 51 determines No in step S302 and proceeds to step S305.

  In step S305, the processor 51 derives the fare from the entrance station to the exit station as follows, for example. An entry station is a record in the management table 62 in which the entry station ID is associated with the reception medium ID and the entry station ID is not associated (hereinafter referred to as “target record”. This is a record indicating that it is a participation.) That is, the entrance station is a station specified by the entrance station ID as the reception medium ID in the target record. The participating station is the receiving station ID. The processor 51 derives the fare from the entry station to the entry station with reference to the fare table 61. The processor 51 that executes the process of step S305 is an example of a derivation unit.

  In step S306, the processor 51 generates a fare notification. The fare notification is to notify the automatic ticket gate 30 of the fare from the entrance station to the departure station. The fare notification includes the fare derived in step S305. After generating the fare notification, the processor 51 instructs the communication unit 54 to transmit the fare notification to the automatic ticket gate 30 that is the transmission source of the participation request. Upon receiving this instruction, the communication unit 54 transmits the fare notification to the automatic ticket gate 30. The transmitted fare notification is received by the first communication unit 35 of the automatic ticket gate 30.

  On the other hand, in step S110 of FIG. 10, the processor 31 of the automatic ticket checker 30 waits for a fare notification to be received by the first communication unit 35. If the fare notification is received, the processor 31 determines Yes in step S110 and proceeds to step S111.

  In step S <b> 111, the processor 31 notifies the settlement reader 47 to prompt the user to pick up the medium M. For example, the processor 31 includes a content that indicates that the payment reader 47 can read the medium M, a content that instructs the payment reader 47 to trick the medium M, and a fare included in the fare notification. Is displayed on the display unit 371. Further, the processor 31 may cause a speaker or the like to output a sound for urging the user to trick the settlement reader 47 into placing the medium M. Further, the processor 31 may illuminate a light source such as an LED provided in the vicinity of the payment terminal 40 in order to indicate that the payment reader 47 can read the medium M.

  In step S112, the processor 31 generates a settlement request. The payment request instructs the payment terminal 40 to perform processing related to payment. The settlement request includes the medium ID acquired in step S103 and the fare amount included in the fare notification received in step S110. After generating the payment request, the processor 31 instructs the second communication unit 36 to transmit the payment request to the payment terminal 40. In response to this instruction, the second communication unit 36 transmits the payment request to the payment terminal 40. The transmitted payment request is received by the second communication unit 46 of the payment terminal 40.

  On the other hand, in step S201 of FIG. 11, the processor 41 of the payment terminal 40 waits for a payment request to be received by the second communication unit 46. If the payment request is received, the processor 41 determines Yes in step S201 and proceeds to step S202.

  In step S202, the processor 41 turns on the payment reader 47.

  In step S <b> 203, the processor 41 determines whether or not the medium M is close to the payment reader 47. If the medium M is not close to the settlement reader 47, the processor 41 determines No in step S203 and proceeds to step S204.

  In step S <b> 204, the processor 41 determines whether a redo notification has been received by the second communication unit 46. If the redo notification is not received, the processor 41 determines No in step S204 and returns to step S203. Thus, the processor 41 repeats steps S203 and S204 until the medium M approaches the settlement reader 47 or a redo notification is received. The redo notification will be described later.

  If the medium M comes close to the settlement reader 47 when in the standby state of steps S203 and S204, the processor 41 determines Yes in step S203 and proceeds to step S205.

  In step S <b> 205, the processor 41 controls the payment reader 47 to acquire the medium ID from the medium M in proximity to the payment reader 47.

  In step S206, the processor 41 determines whether or not the two medium IDs of the medium ID included in the settlement request received in step S201 and the medium ID acquired in step S205 match. If the two medium IDs match, the processor 41 determines Yes in step S206 and proceeds to step S207. The processor 41 that executes the process of step S206 is an example of a coincidence determination unit.

  In step S207, the processor 41 cooperates with the electronic money server 70 to execute settlement processing for the amount included in step S201 using the electronic money managed by the medium M. As for the settlement process, a well-known method can be used in addition to the method described in the outline of the ticket gate system process.

  In step S208, the processor 41 turns off the payment reader 47.

  In step S209, the processor 41 determines whether or not the settlement in step S207 is successful. For example, the settlement fails when the charge amount of the medium M is less than the fare. If the processor 41 determines that the payment is successful, it determines Yes in step S209 and proceeds to step S210.

  In step S210, the processor 41 generates a first completion notification. The first completion notification indicates that the payment process has been completed normally. After generating the first completion notification, the processor 41 instructs the second communication unit 46 to transmit the first completion notification to the automatic ticket gate 30. In response to this instruction, the second communication unit 46 transmits the first completion notification to the automatic ticket gate 30. The transmitted first completion notification is received by the second communication unit 36 of the automatic ticket checker 30. The processor 41 returns to step S201 after the process of step S210.

  On the other hand, in step S113 of FIG. 10, the processor 31 of the automatic ticket checker 30 determines whether or not the first communication unit 36 has received the first completion notification, failure notification, or first mismatch notification. If the first completion notification, failure notification, or first mismatch notification is not received, the processor 31 proceeds to step S114. The failure notification and the first mismatch notification will be described later.

In step S <b> 114, the processor 31 determines whether or not an operation for redoing the medium M to the entrance / exit leader 38 (hereinafter referred to as “redo operation”) has been performed. If the redo operation has not been performed, the processor 31 determines No in step S114 and returns to step S113. Thus, the processor 31 repeats step S113 and step S114 until the first completion notification, failure notification, or first mismatch notification is received or a redo operation is performed.
If the first completion notification is received when the processor 31 is in the standby state in steps S113 and S114, the processor 31 determines Yes in step S113 and proceeds to step S115.

  In step S115, the processor 31 determines whether or not the notification received in step S113 is a first completion notification. If the received notification is the first completion notification, the processor 31 determines Yes in step S115 and proceeds to step S116.

  In step S116, the processor 31 generates a second completion notification. The second completion notification indicates that the payment process has been completed normally. After generating the second completion notification, the processor 31 instructs the first communication unit 35 to transmit the second completion notification to the center server 50. In response to this instruction, the first communication unit 35 transmits the second completion notification to the center server 50. The transmitted second completion notification is received by the communication unit 54 of the center server 50. The processor 31 returns to step S101 of FIG. 9 after the process of step S116.

  On the other hand, in step S307 in FIG. 12, the processor 51 of the center server 50 waits for the communication unit 54 to receive the second completion notification. If the second completion notification is received, the processor 51 determines Yes in step S307 and proceeds to step S308.

  In step S308, the processor 51 performs a participation process. That is, the processor 51 updates the target record, sets the value of the participating station ID of the target record to the receiving station ID, sets the value of the participating time to the current time, and sets the fare value to the fare amount derived in step S305. To do. Further, the processor 51 updates the target record, and sets the value of the settlement status of the target record to a value indicating that payment has been completed. As a result, it is recorded that the owner of the medium M specified by the receiving medium ID has already entered the ticket gate. The processor 51 returns to step S301 after the process of step S308.

  On the other hand, if the processor 41 of the payment terminal 40 determines that the payment in step S207 of FIG. 11 has failed, it determines “No” in step S209 and proceeds to step S211.

  In step S211, the processor 41 generates a failure notification. The failure notification indicates that payment has failed. Note that the failure notification includes failure information indicating the reason for failure in settlement. After generating the failure notification, the processor 41 instructs the second communication unit 46 to transmit the failure notification to the automatic ticket checker 30. In response to this instruction, the second communication unit 46 transmits the failure notification to the automatic ticket gate 30. The transmitted failure notification is received by the second communication unit 36 of the automatic ticket gate 30. The processor 41 returns to step S201 after the process of step S211.

On the other hand, when the failure notification is received by the second communication unit 36, the processor 31 of the automatic ticket checker 30 determines Yes in step S113 of FIG. 10 and proceeds to step S115. If the received notification is a failure notification, the processor 31 determines No in step S115 and proceeds to step S117.
In step S117, the processor 31 determines whether or not the notification received in step S113 is a failure notification. If the received notification is a failure notification, the processor 31 determines Yes in step S117 and proceeds to step S118.

  In step S118, the processor 31 notifies that an error has occurred based on the failure information included in the received failure notification. For example, the processor 31 displays on the display unit 371 that the payment has failed and the reason for the payment failure. Further, for example, the processor 31 outputs a sound indicating that payment has failed from a speaker or the like. The processor 31 returns to step S101 of FIG. 9 after the process of step S118.

If the two medium IDs do not match, the processor 41 of the payment terminal 40 determines No in step S206 of FIG. 11 and proceeds to step S212.
In step S212, the processor 41 generates a first mismatch notification. The first mismatch notification indicates that the two medium IDs do not match. After generating the first mismatch notification, the processor 41 instructs the second communication unit 46 to transmit the first mismatch notification to the automatic ticket checker 30. In response to this instruction, the second communication unit 46 transmits the first mismatch notification to the automatic ticket gate 30. The transmitted first mismatch notification is received by the second communication unit 36 of the automatic ticket checker 30. The processor 41 returns to step S203 after the process of step S212.

  On the other hand, if the first communication notification is received by the second communication unit 36, the processor 31 of the automatic ticket checker 30 determines Yes in step S113 of FIG. 10 and proceeds to step S115. If the received notification is the first mismatch notification, the processor 31 determines No in each of step S115 and step S117, and proceeds to step S119.

  In step S119, the processor 31 notifies that the medium M trapped by the entry / exit leader 38 is different from the medium M trapped by the settlement reader 47. For example, the processor 31 determines that the medium M trapped by the entry / exit leader 38 is different from the medium M trapped by the settlement reader 47 and the same medium M as the medium M trapped by the entrance / exit leader 38. The display unit 371 displays a screen including the content that the user is asked to envy the payment reader 47. Further, for example, the processor 31 causes a speaker or the like to output a sound indicating that the medium M trapped by the entrance / exit reader 38 and the medium M trapped by the settlement reader 47 are different. The processor 31 returns to step S113 after the process of step S119.

In addition, the user can restart the participation from the place where the medium M is tricked by the entry / exit leader 38. In this case, for example, the user performs a redo operation using the input unit 372 or the like. If the redo operation is performed when the processor 31 is in the standby state of step S113 and step S114, Yes in step S114. And the process proceeds to step S120.
In step S120, the processor 31 generates a redo notification. The redo notification notifies the payment terminal 40 that the medium reader M is tricked into the entrance / exit reader 38 and redoes. The redo notification instructs the payment terminal 40 not to read the medium M by the payment reader 47. After generating the redo notification, the processor 31 instructs the second communication unit 36 to transmit the redo notification to the payment terminal 40. In response to this instruction, the second communication unit 36 transmits the redo notification to the payment terminal 40. The transmitted redo notification is received by the second communication unit 46 of the payment terminal 40. The processor 31 returns to step S101 of FIG. 9 after the process of step S120.

On the other hand, if the redo notification is received when the processor 41 of the payment terminal 40 is in the standby state of step S203 and step S204 in FIG. 11, the processor 41 determines Yes in step S204 and proceeds to step S213.
In step S213, the processor 41 turns off the payment reader 47. The processor 41 returns to step S201 after the process of step S213.

  The ticket gate system 1 of the first embodiment can realize the ticket gate processing even for the medium M in which the information on the entry station or the entry station cannot be written. As a result, the user can use a medium convenient for the user, and the convenience for the user is improved.

  Further, according to the ticket gate system 1 of the first embodiment, the payment terminal 40 performs a payment process when it is determined that the two medium IDs match. That is, the payment terminal 40 does not perform the payment process when the medium M trapped by the entry / exit leader 38 and the medium M trapped by the payment reader 47 are different media M. Thereby, in the ticket gate system 1 of the first embodiment, for example, after a person who tricked the medium M into the entrance / exit reader 38 leaves the spot, another person tricks the settlement reader 47 into another medium M. It is possible to prevent wrong receipt of fares. As a result, since the user does not pay an unfair fare, the convenience of the user is improved.

[Second Embodiment]
Unlike the first embodiment in which the payment terminal 40 determines matching of terminal IDs, in the second embodiment, the automatic ticket gate 30 determines matching of terminal IDs.

(Constitution)
Since the ticket gate system 1 of the second embodiment is the same as the ticket gate system 1 of the first embodiment, the description thereof is omitted.

(Operation)
Hereinafter, the operation of the ticket gate system 1 according to the second embodiment will be described with reference to FIGS. 9 and 12 to 14. Note that the content of the processing in the following description of the operation is an example, and various processing that can obtain the same result can be used as appropriate. Unlike the first embodiment, the processor 31 of the automatic ticket gate 30 according to the second embodiment executes the processes shown in the flowcharts of FIGS. 9 and 13 instead of FIGS. 9 and 10. FIG. 13 is a flowchart of processing by the processor 31 of the automatic ticket gate 30. The processor 31 executes this processing based on a program stored in the ROM 32 or the auxiliary storage device 34. Unlike the first embodiment, the processor 41 of the payment terminal 40 according to the second embodiment executes the process shown in the flowchart of FIG. 14 instead of FIG. FIG. 14 is a flowchart of processing by the processor 41 of the payment terminal 40. The processor 41 executes this processing based on a program stored in the ROM 42 or the auxiliary storage device 44. Note that the processor 51 of the center server 50 executes the processing shown in the flowchart of FIG. 12 as in the first embodiment. In FIG. 13 and FIG. 14, the same processes as those in FIG. 10 or FIG. In the following description of the operation of the second embodiment, description of the same processing as that of the first embodiment may be omitted.

The processor 41 of the payment terminal 40 proceeds to step S221 after the process of step S205 in FIG.
In step S221, the processor 41 instructs the second communication unit 36 to transmit the medium ID acquired in step S205 to the payment terminal 40. Upon receiving this instruction, the second communication unit 36 transmits the medium ID to the payment terminal 40. The transmitted medium ID is received by the second communication unit 46 of the payment terminal 40.

On the other hand, if the processor 31 of the automatic ticket checker 30 determines No in step S105 of FIG. 9 in the second embodiment, it proceeds to step 109 of FIG. Then, the processor 31 proceeds to step S131 after the process of step S112 in FIG.
In step S131, the processor 31 determines whether or not the medium ID is received by the first communication unit 35. If the medium ID is not received, the processor 31 determines No in step S131 and proceeds to step S114.

  If the processor 31 determines No in step S114, it returns to step S131. Thus, the processor 31 repeats step S131 and step S114 in which the medium ID is received or a redo operation is performed.

If the medium ID is received when the processor 31 is in the standby state in steps S131 and S114, the processor 31 determines Yes in step S131 and proceeds to step S132.
In step S132, the processor 31 determines whether or not the two medium IDs of the medium ID acquired in step S103 and the medium ID received in step S131 match. If the two medium IDs match, the processor 31 determines Yes in step S132 and proceeds to step S133. The processor 31 that executes the process of step S132 is an example of a coincidence determination unit.

  In step S133, the processor 31 generates a coincidence notification. The match notification indicates that the two medium IDs match. The coincidence notification instructs the payment terminal 40 to execute the payment processing for the fare. After generating the coincidence notification, the processor 31 instructs the second communication unit 36 to transmit the coincidence notification to the payment terminal 40. In response to this instruction, the second communication unit 36 transmits the match notification to the payment terminal 40. The transmitted notification of coincidence is received by the second communication unit 46 of the payment terminal 40.

  On the other hand, in step S222 of FIG. 14, the processor 41 of the payment terminal 40 waits for the second communication unit 46 to receive a match notification or a second mismatch notification. If the match notification is received, the processor 41 determines Yes in step S222 and proceeds to step S223. The second mismatch notification will be described later.

  In step S223, the processor 41 determines whether or not the notification received in step S222 is a match notification. If the received notification is a match notification, the processor 41 determines Yes in step S223 and proceeds to step S207.

  On the other hand, if the two medium IDs do not match, the processor 31 of the automatic ticket gate 30 determines No in step S132 and proceeds to step S119. Then, the processor 31 proceeds to step S134 after the process of step S119.

  In step S134, the processor 31 generates a second mismatch notification. The second mismatch notification indicates that the two medium IDs do not match. After generating the second mismatch notification, the processor 31 instructs the second communication unit 36 to transmit the second mismatch notification to the payment terminal 40. In response to this instruction, the second communication unit 36 transmits the second mismatch notification to the payment terminal 40. The transmitted second mismatch notification is received by the second communication unit 46 of the payment terminal 40.

  On the other hand, if the second communication unit 46 receives the second mismatch notification, the processor 41 of the payment terminal 40 determines Yes in step S222 of FIG. 14 and proceeds to step S223. If the received notification is the second mismatch notification, the processor 41 determines No in step S223 and returns to step S203.

  If the redo operation is performed when the processor 31 of the automatic ticket checker 30 is in the standby state of steps S131 and S114 in FIG. 13, the processor 31 determines Yes in step S114 and proceeds to step S120. On the other hand, if the processor 31 determines No in step S115, it proceeds to step S118.

  The ticket gate system 1 of the second embodiment can realize the ticket gate processing even for the medium M in which the information on the entrance station or the entry station cannot be written. As a result, the user can use a medium convenient for the user, and the convenience for the user is improved.

  According to the ticket gate system 1 of the second embodiment, the payment terminal 40 performs a payment process when the automatic ticket checker 30 determines that the two medium IDs match. That is, the payment terminal 40 does not perform the payment process when the medium M trapped by the entry / exit leader 38 and the medium M trapped by the payment reader 47 are different media M. Thereby, the ticket gate system 1 of 2nd Embodiment can prevent misreception of a fare etc. similarly to 1st Embodiment. As a result, since the user does not pay an unfair fare, the convenience of the user is improved.

[Third Embodiment]
In the third embodiment, it is determined whether or not two medium IDs of the medium ID of the medium M trapped by the entrance reader 38 and the medium ID of the medium M trapped by the settlement reader 47 match. This is an embodiment in the case where it cannot be performed before the settlement process. When a commercially available IC card reader is used as the payment terminal 40, such a determination may not be possible before the payment process. Therefore, the third embodiment is effective when a commercially available IC card reader is used as the payment terminal 40. That is, in the third embodiment, after making a settlement, it is determined whether or not the two medium IDs match, and if they do not match, the fare for the misreceived and unaccepted receipts can be settled. It is what I did.

(Constitution)
The center server storage unit 60 of the third embodiment stores a fare table 61, a management table 62b, and a settlement table 63 as shown in FIG. FIG. 15 is a diagram illustrating a main circuit configuration and functional configuration of the center server 50 according to the third embodiment. In addition, since the other structure of the ticket gate system 1 which concerns on 3rd Embodiment is the same as that of 1st Embodiment, description is abbreviate | omitted.

  FIG. 16 is a diagram illustrating an example of the contents of the management table 62b. The management table 62b includes an entry station ID, an entry time, a medium ID of the medium M settled at the entry station (an entry medium ID), an entry station ID, an entry time, and the entry station from the entry station. The fare up to and the payment status are related.

  FIG. 17 is a diagram illustrating an example of the contents of the settlement table 63. The settlement table 63 records the medium ID and the settlement amount of the medium M that requires the settlement of the fare for the misreceived or unaccepted due to the occurrence of the erroneous receipt or unaccepted.

(Operation)
Hereinafter, the operation of the ticket gate system 1 according to the third embodiment will be described with reference to FIG. 9 and FIGS. Note that the content of the processing in the following description of the operation is an example, and various processing that can obtain the same result can be used as appropriate. The processor 31 of the automatic ticket gate 30 according to the third embodiment executes processing shown in the flowcharts of FIGS. 9 and 17 instead of the flowcharts of FIGS. 9 and 10 of the first embodiment. FIG. 17 is a flowchart of processing by the processor 31 of the automatic ticket gate 30. The processor 31 executes this processing based on a program stored in the ROM 32 or the auxiliary storage device 34. The processor 41 of the payment terminal 40 of the second embodiment executes the process shown in the flowchart of FIG. 18 instead of the flowchart of FIG. 11 of the first embodiment. FIG. 14 is a flowchart of processing by the processor 41 of the payment terminal 40. The processor 41 executes this processing based on a program stored in the ROM 42 or the auxiliary storage device 44. Further, the processor 51 of the center server 50 of the second embodiment executes the process shown in the flowchart of FIG. 19 instead of the flowchart of FIG. 12 of the first embodiment. FIG. 19 is a flowchart of processing by the processor 51 of the center server 50. The processor 51 executes this processing based on a program stored in the ROM 52 or the like. 17 to 19, processes similar to those in FIGS. 12 to 14 are denoted by the same reference numerals. In the following description of the operation of the third embodiment, description of the same processing as that of the first embodiment may be omitted.

In the third embodiment, if the processor 31 of the automatic ticket checker 30 determines No in step S105 of FIG. 9, the processor 31 proceeds to step 109 of FIG.
On the other hand, if the processor 31 determines No in step S110, it proceeds to step S141.
In step S <b> 141, the processor 31 determines whether or not a payment notice is received by the first communication unit 35. If the settlement notice is not received, the processor 31 determines No in step S141 and returns to step S110. Thus, the processor 31 repeats step S110 and step S141 until a fare notification or a payment notification is received. The payment notification will be described later.
If the fare notification is received when the processor 31 is in the standby state of step S110 and step S141, the processor 31 determines Yes in step S110 and proceeds to step S111.

Further, the processor 41 of the settlement terminal 40 proceeds to step S207 after the process of step S205 in FIG.
If the processor 41 determines Yes in step S209, the processor 41 proceeds to step S231.
In step S231, the processor 41 generates a third completion notification. Similar to the first completion notification, the third completion notification indicates that the payment process has been completed normally. The third completion notification includes the medium ID acquired in step S205. After generating the third completion notification, the processor 41 instructs the second communication unit 46 to transmit the third completion notification to the automatic ticket gate 30. In response to this instruction, the second communication unit 46 transmits the third completion notification to the automatic ticket gate 30. The transmitted third completion notification is received by the second communication unit 36 of the automatic ticket checker 30.

On the other hand, the processor 31 of the automatic ticket gate 30 proceeds to step S142 after the process of step S112 in FIG.
In step S142, the processor 31 waits for the second communication unit 36 to receive a third completion notification or failure notification. If the third completion notification or the failure notification is not received, the processor 31 proceeds to step S114. Thus, the processor 31 repeats step S142 and step S114 until a third completion notification or failure notification is received or a redo operation is performed.
If the third completion notification is received in the standby state in steps S142 and S114, the processor 31 determines Yes in step S142 and proceeds to step S143.

  In step S143, the processor 31 determines whether or not the notification received in step S142 is a third completion notification. If the received notification is a failure notification, the processor 31 determines No in step S143 and proceeds to step S118. On the other hand, if the notification received in step S142 is the third completion notification, the processor 31 determines Yes in step S143 and proceeds to step S144.

In step S144, the processor 31 determines whether or not the two medium IDs of the medium ID acquired in step S103 and the medium ID included in the third completion notification received in step S142 match. If the two medium IDs match, the processor 31 determines Yes in step S144 and proceeds to step S116. On the other hand, if the two medium IDs do not match, the processor 31 determines No in step S144 and proceeds to step S145. The processor 31 that executes the process of step S144 is an example of an erroneous receipt determination unit.
Here, the fact that the two medium IDs do not match indicates that an erroneous receipt has occurred. For the sake of explanation, the medium M trapped by the entry / exit leader 38 is hereinafter referred to as medium MX, and the medium M trapped by the settlement reader 47 is referred to as medium MY. For example, the user who tricked the medium MX goes out of the ticket gate without tricking the settlement reader 47 into the media MX. Thereafter, another user tricks the settlement reader 47 into the medium MY. As a result, the fare for the medium MX is not yet received. Then, the medium MY is erroneously received by the fare. That is, the medium MY will settle the amount that should have been settled by the medium MX.

  In step S145, the processor 31 generates an erroneous receipt notification. The erroneous receipt notification indicates that an erroneous receipt has occurred. The erroneous receipt notification includes the medium ID of the medium MX and the medium ID of the medium MY. After generating the erroneous receipt notification, the processor 31 instructs the first communication unit 35 to transmit the erroneous receipt notification to the center server 50. In response to this instruction, the first communication unit 35 transmits the erroneous receipt notification to the center server 50. The transmitted misreception receipt is received by the communication unit 54 of the center server 50. The processor 31 returns to step S101 of FIG. 9 after the process of step S145.

On the other hand, the processor 51 of the center server 50 proceeds to step S311 after the process of step S306 in FIG.
In step S <b> 311, the processor 51 determines whether an erroneous receipt notification has been received by the communication unit 54. If an erroneous receipt notification has not been received, the processor 51 determines No in step S311, and proceeds to step S307. Thus, the processor 51 repeats step S311 and step S307 until an erroneous receipt notification or a second completion notification is received. If the second completion notification is received in the standby state in steps S311 and S307, the processor 51 determines Yes in step S307 and proceeds to step S308. On the other hand, if an erroneous receipt notification is received in the standby state of steps S311 and S307, the processor 51 determines Yes in step S311 and proceeds to step S312.

In step S312, the processor 51 records erroneous receipts and unaccepted receipts as follows, for example. The processor 51 updates the management table 62b, and for the record in which the entry station ID is associated with the medium MX and the entry station ID is not associated (hereinafter referred to as “record of the medium MX”), the value of the entry medium ID. Is the medium ID of the medium MY, the value of the participating station ID is the receiving station ID, the value of the participating time is the current time, the value of the fare is the amount of the fare derived in step S305, and the value of the settlement status is settled Use the value shown. Further, the processor 51 updates the management table 62b, and for the record in which the entry station ID is associated with the medium MY and the entry station ID is not associated (hereinafter referred to as “record of the medium MY”), the entry station ID. From the entry station when the station specified by the entry station ID for the record of medium MY is the entry station and the station specified by the reception station ID is the entry station Use the fare of the participating station. The processor 51 derives the amount of the fare with reference to the fare table 61 as in step S305.
As a result of the above processing, the management table 62b is in a state as shown in FIG. That is, the record with the entrance / exit ID 10000003 in FIG. 15 is an example of the record of the medium MX. And the record of entrance ID 10000004 in FIG. 15 is an example of the record of medium MY. As a result, the misaccepted amount and the unaccepted amount for one misacceptance specified by the entrance / exit ID 10000003 and the entrance / exit ID 10000004 are recorded. As an example, the accrued amount of the medium MX is 340 yen which is the fare value of the record of the medium MX. This amount is an amount that needs to be settled for the medium MX for one misreceived case. Further, as an example, the erroneous receipt amount of the medium MY is 340 yen, which is the fare value of the record of the medium MX. The accrued amount of the medium MY is 260 yen which is the fare value of the record of the medium MY. Accordingly, the amount that needs to be settled for the medium MY for one misacceptance is -80 yen, which is the unaccrued amount of the medium MY minus the misaccepted amount of the medium MY. If the settlement amount is a negative value, it indicates that a refund is required.
Further, the processor 51 updates the settlement table 63 as follows, for example. When there is no record whose medium ID value is the medium ID of the medium MX in the settlement table 63, the processor 51 adds a record whose medium ID value is the medium ID of the medium MX to the settlement table 63. The value of the settlement amount of the added record is an amount that needs to be settled with respect to the medium MX for the one misacceptance. On the other hand, when there is a record whose medium ID value is the medium ID of the medium MX in the settlement table 63, the processor 51 sets the settlement amount value of the record as the medium MX for the above-mentioned one erroneous receipt. Add the amount that needs to be settled. Further, when there is no record whose medium ID value is the medium ID of the medium MY in the settlement table 63, the processor 51 adds a record whose medium ID value is the medium ID of the medium MY to the settlement table 63. The value of the settlement amount of the added record is an amount that needs to be settled with respect to the medium MY for the one misacceptance. On the other hand, when there is a record whose medium ID value is the medium ID of the medium MY in the settlement table 63, the processor 51 sets the settlement amount value of the record to the medium MY for the above-mentioned one misacceptance. Add the amount that needs to be settled. As a result, the amount that needs to be settled for each of the medium MX and the medium MY is stored in the settlement table 63. Note that the amount stored in the settlement table 63 is the sum of unsettled amounts. Therefore, the amount recorded in the settlement table 63 is the sum of the misreceived amount and the unaccepted amount in the case of the medium M that has been misaccepted a plurality of times and the settlement has not been completed. It is.
The processor 51 returns to step S301 after the process of step S312.

Next, the settlement of the settlement amount stored in the settlement table 63 will be described.
The processor 51 proceeds to step S313 after the process of step S305.
In step S313, the processor 51 determines whether payment is necessary. For example, the processor 51 determines whether payment is required as follows. That is, the processor 51 determines that settlement is required when there is a record in the settlement table whose medium ID value in the settlement table is the receiving medium ID and the settlement amount value of the record is not 0. . The value of the settlement amount is hereinafter referred to as “necessary settlement amount”. If payment is not necessary, the processor 51 determines No in step S313 and proceeds to step S306. On the other hand, if payment is necessary, the processor 51 determines Yes in step S313 and proceeds to step S314.

  In step S314, the processor 51 generates a settlement notice. The settlement notice indicates that settlement is required. The settlement notice includes the necessary settlement amount and the fare derived in step S305. After generating the payment notification, the processor 51 instructs the communication unit 54 to transmit the payment notification to the automatic ticket checker 30. In response to this instruction, the communication unit 54 transmits the payment notice to the automatic ticket gate 30. The transmitted settlement notice is received by the first communication unit 35 of the automatic ticket gate 30. The processor 51 proceeds to step S311 after the process of step S314. The processor 51 obtains the necessary settlement amount from the settlement table 63. Therefore, the processor 51 that acquires the required settlement amount from the settlement table 63 is an example of a first amount acquisition unit.

  On the other hand, if the processor 31 of the automatic ticket checker 30 is in the standby state of step S110 and step S141 in FIG. 17 and receives a settlement notice, it determines Yes in step S141 and proceeds to step S146. .

  In step S146, the processor 31 notifies that payment is necessary. For example, the processor 31 includes, for example, a content indicating that payment is required, a content indicating that the settlement reader 47 can read the medium M, and a medium M to the settlement reader 47. The display unit 371 displays a screen including the contents instructed in the above, the fare and the necessary settlement amount included in the settlement notice, and the total of the fare and the necessary settlement amount. Further, the processor 31 may cause a speaker or the like to output a sound for urging the user to trick the settlement reader 47 into placing the medium M. Further, the processor 31 may illuminate a light source such as an LED provided in the vicinity of the payment terminal 40 in order to indicate that the payment reader 47 can read the medium M.

In step S147, the processor 31 generates a settlement request. The payment request instructs the payment terminal 40 to perform processing related to payment. The settlement request includes the total amount of the medium ID acquired in step S103 and the fare included in the settlement notification received in step S141 and the necessary settlement amount included in the settlement notification. After generating the payment request, the processor 31 instructs the second communication unit 36 to transmit the payment request to the payment terminal 40. In response to this instruction, the second communication unit 36 transmits the payment request to the payment terminal 40. The transmitted payment request is received by the second communication unit 46 of the payment terminal 40. The processor 31 proceeds to step S142 after the process of step S147.
Note that the amount of money included in the settlement request may be a negative value. In this case, the processor 41 of the payment terminal 40 performs a refund process for the amount in the payment process in step S207 of FIG. In addition, the amount of money included in the settlement request may be zero. In this case, the automatic ticket gate 30 may not cause the payment terminal 40 to perform payment processing. Alternatively, the payment terminal 40 may skip the payment process. When the payment terminal 40 does not perform the payment process, the user does not need to put the medium M on the payment reader 47.

On the other hand, the processor 51 of the center server 50 proceeds to step S315 after the process of step S308 in FIG.
In step S315, the processor 51 updates the settlement table 63 and resets the necessary settlement amount for the medium M for which settlement has been completed. That is, the processor 51 sets the settlement amount value of the record whose medium ID value is the reception medium ID to 0 in the settlement table 63. Alternatively, the processor 51 deletes the record.

  The ticket gate system 1 of the third embodiment can realize the ticket gate processing even for the medium M in which the information on the entry station or the entry station cannot be written. As a result, the user can use a medium convenient for the user, and the convenience for the user is improved.

  According to the ticket gate system 1 of the third embodiment, the automatic ticket gate 30 is configured such that the medium M trapped by the entry / exit leader 38 and the medium M trapped by the settlement reader 47 are different media M, It is determined that an erroneous receipt has occurred. Then, the center server 50 stores that the erroneous receipt has occurred and the necessary settlement amount in association with the identification information of the medium M. This makes it possible to settle the amount later. This improves the convenience for the user.

  The ticket gate system 1 according to the third embodiment performs settlement for the necessary settlement amount at the time of participation. Therefore, the customer does not need a special procedure for settlement.

[Fourth Embodiment]
The ticket gate system 1 according to the fourth embodiment records a camera image at the time when an erroneous receipt occurs.
The camera 90 is provided so that the ticket gate unit 20 and its periphery are reflected. The camera 90 always records the captured video during operation. However, the camera 90 overwrites with new recordings in order from the oldest recording, for example. A moving image is a kind of image. The camera 90 is an example of a photographing device that photographs the ticket gate unit 20.

(Constitution)
The automatic ticket gate 30 of the fourth embodiment is connected to a camera 90 as shown in FIG. FIG. 20 is a block diagram illustrating an example of a circuit configuration and a functional configuration of main parts of the ticket gate system 1 and the automatic ticket gate 30 and the payment terminal 40 included in the ticket gate system 1 according to the fourth embodiment. In addition, since the other structure of the ticket gate system 1 which concerns on 4th Embodiment is the same as that of 3rd Embodiment, description is abbreviate | omitted.

(Operation)
Hereinafter, the operation of the ticket gate system 1 according to the fourth embodiment will be described based on FIG. 9, FIG. 18, FIG. 21, FIG. Note that the content of the processing in the following description of the operation is an example, and various processing that can obtain the same result can be used as appropriate. Unlike the third embodiment, the processor 31 of the automatic ticket gate 30 according to the fourth embodiment executes the processes shown in the flowcharts of FIGS. 9 and 21 instead of FIGS. 9 and 17. FIG. 21 is a flowchart of processing by the processor 31 of the automatic ticket gate 30. The processor 31 executes this processing based on a program stored in the ROM 32 or the auxiliary storage device 34. The processor 51 of the center server 50 according to the fourth embodiment executes the process shown in the flowchart of FIG. 22 instead of the flowchart of FIG. 19 of the third embodiment. FIG. 22 is a flowchart of processing by the processor 51 of the center server 50. The processor 51 executes this processing based on a program stored in the ROM 52 or the like. Note that the processor 41 of the settlement terminal 40 executes the processing shown in the flowchart of FIG. 18 as in the third embodiment. 21 and 22, the same processes as those in FIG. 17 or 19 are denoted by the same reference numerals. Also, in the following description of the operation of the fourth embodiment, description of processing similar to that of the third embodiment may be omitted.

If the processor 31 of the automatic ticket checker 30 determines No in step S144 of FIG. 21, the process proceeds to step S151.
In step S151, the processor 31 cuts out the moving image of the portion before and after the erroneous receipt notification from the moving image recorded by the camera 90. For example, the moving image includes a period from when the medium MX is tricked by the entrance / exit leader 38 to when the medium MY is trickled by the settlement reader 47. Furthermore, the said moving image also includes the moving image for the front and back. For example, the time before and after is several tens of seconds.

  The processor 31 analyzes the video clipped in step S151 and determines whether or not the person who tricked the medium MX into the entrance / exit leader 38 and the person who tricked the medium MY into the settlement reader 47 are the same person. To do. If the processor 31 determines that they are the same person, it proceeds to step S116. If the processor 31 determines that they are not the same person, the process proceeds to step S145. The processor 31 proceeds to step S153 after the process of step S145.

  In step S153, the processor 31 instructs the first communication unit 35 to transmit the video clipped in step S151 to the center server 50. Upon receiving this instruction, the first communication unit 35 transmits the moving image to the center server 50. The transmitted moving image is received by the communication unit 54 of the center server 50. The processor 31 returns to step S101 of FIG. 9 after the process of step S153.

On the other hand, the processor 51 of the center server 50 proceeds to step S321 after the process of step S312 of FIG.
In step S <b> 321, the processor 51 waits for a moving image to be received by the communication unit 54. If the moving image is received, the processor 51 determines Yes in step S321 and proceeds to step S322.

  In step S322, the processor 51 stores the moving image received in step S321 in association with the entrance / exit ID of the entrance / exit that has been subject to erroneous receipt. That is, for example, the processor 51 associates the moving image with the entrance / exit ID of the record of the medium MX and the entrance / exit ID of the record of the medium MY. The moving image is stored in, for example, the center server storage unit 60.

  The ticket gate system 1 of the fourth embodiment can realize the ticket gate processing even for the medium M in which the information on the entry station or the entry station cannot be written. As a result, the user can use a medium convenient for the user, and the convenience for the user is improved.

  The ticket gate system 1 of the fourth embodiment stores a moving image when an erroneous receipt occurs. Therefore, it is possible to confirm the situation at the time of occurrence of erroneous receipt later with a moving image.

  In the ticket gate system 1 according to the fourth embodiment, if the person who dressed the medium MX as the entry / exit leader 38 and the person dressed as the medium MY as the settlement reader 47 are the same person, there is no false receipt. I reckon. This is because it is considered that there is no problem even if payment is made with a different medium M if they are the same person. In addition, the user can make a settlement using the medium MY when the charge amount of the medium MX is insufficient. Therefore, convenience for the user is improved.

Each of the above embodiments can be modified as follows.
Instead of the automatic ticket gate 30 and the payment terminal 40, the ticket gate unit 20 may include a single device that doubles as the automatic ticket gate 30 and the payment terminal 40. The processor of one device that also serves as the two devices executes the same processing as the processor 31 in each of the above embodiments and the same processing as the processor 41 in each of the above embodiments.

  In the first embodiment, the payment terminal 40 determines whether or not the medium ID acquired by the entrance / exit reader 38 and the medium ID acquired by the payment reader 47 match. And in 2nd Embodiment, the automatic ticket gate performed the said determination. However, the center server 50 may make the determination. The processor 51 of the center server 50 that performs the determination is an example of a match determination unit.

  In each of the embodiments described above, the ticket gate unit 20 includes two readers, that is, the entrance / exit reader 38 and the settlement reader 47. However, instead of the two readers, the ticket gate unit 20 may include a single reader that also functions as the two readers.

  The ticket gate system 1 may be provided with an automatic ticket gate 30 for both entry and exit instead of the entrance automatic ticket gate 30 and the entrance automatic ticket gate 30.

  In the third embodiment and the fourth embodiment, when the sum of the necessary settlement amount and the fare derived in step S305 becomes a negative value, the center server 50 replaces the necessary settlement amount included in the settlement notification with a step. An amount less than or equal to the fare derived in S305 (hereinafter referred to as “the same amount or less”) may be included. Preferably, the amount less than or equal to the same amount is the same amount as the fare derived in step S305. Then, in step S315, the center server 50 subtracts, for the settlement table 63, the settlement amount value of the record whose medium ID is the receiving medium ID from the settlement amount value equal to or less than the same amount included in the settlement notification. Value. Thereby, the refund process does not occur in the payment terminal 40. By doing as described above, the settlement can be made even when the payment terminal 40 does not support the refund process.

  In the third embodiment and the fourth embodiment, the automatic ticket gate 30 determines that an erroneous receipt has occurred. However, the center server 50 may determine that an erroneous receipt has occurred. The processor 51 of the center server 50 that determines that erroneous receipt has occurred is an example of an erroneous receipt determination unit.

  The ticket gate system 1 of the third embodiment and the fourth embodiment paid out at the time of participation. However, payment may be made when entering. In this case, the center server 50 refers to the payment table 63 and determines whether or not payment is required in response to receiving the admission request. When the processor 51 of the center server 50 determines that payment is required, the processor 51 of the center server 50 acquires the required payment amount from the payment table 63. The processor 51 that acquires the necessary settlement amount is an example of a second amount acquisition unit. Then, the center server 50 notifies the automatic ticket checker 30 that the payment is required and the required payment amount. Receiving the notification, the automatic ticket checker 30 causes the display unit 371 to display a screen including contents indicating that payment is required and that the payment reader 47 is prompted to be tricked. Furthermore, the automatic ticket gate 30 instructs the payment terminal 40 to perform payment processing for the necessary settlement amount. The user puts the medium M in the payment reader 47. The payment terminal 40 performs a payment process using the medium M. Even in the above case, the customer does not need a special procedure for settlement.

  Although several embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

  1 ... Ticket gate system, 30 ... Automatic ticket gate, 31, 41, 51, 71 ... Processor, 32, 42, 52, 72 ... ROM, 33, 43, 53, 73 ... RAM, 34, 44 ... ... Auxiliary storage device, 35, 45 ... First communication unit, 36, 46 ... Second communication unit, 37 ... Touch panel, 38 ... Reader for entry / exit, 40 ... Payment terminal, 47 ... Payment Reader 50, center server 54, 74 ... communication unit 60 ... center server storage unit 61 ... fare table, 62, 62b ... management table, 63 ... settlement table, 70 ... electronic money Server, 80 ... Electronic money server storage unit, 81 ... Electronic money information, 82 ... Electronic money information, 90 ... Camera, 311, 411 ... Determination unit, 312 ... Communication control unit, 371 ... Table Department, 372 ...... input unit, 412 ...... settlement control unit, 511 ...... information management unit, 512 ...... fare deriving unit, 711 ...... settlement management unit, M ...... medium

Claims (7)

An entry device used when entering from an area that requires a fee for entry and exit,
A first acquisition unit that acquires identification information from a medium for using a payment service;
A communication unit that receives the amount of the fee specified by the transmitted identification information from the server device by transmitting the identification information acquired by the first acquisition unit to the server device;
A second acquisition unit that acquires identification information from a medium for using a payment service;
A coincidence determination unit that determines whether or not the identification information acquired by the first acquisition unit and the identification information acquired by the second acquisition unit match;
When the match determination unit determines that the match is made, the payment service is used to perform payment processing for the amount of the fee, and when the match determination unit determines that the match does not occur, the payment processing is not performed. And a settlement unit. Including an entry device used when entering an area that requires a fee for entry, an entry device used when entering from the area, and a server device;
A third acquisition unit included in the admission device that acquires identification information from a medium for using a payment service;
A first storage unit included in the server device for storing a record of entry into the area in association with the identification information acquired by the third acquisition unit;
A first acquisition unit included in the participation device that acquires identification information from a medium for using a payment service;
An entry record associated with the same identification information as the identification information obtained by the first obtaining unit is obtained from the first storage unit, and the amount of the fee is derived based on the obtained entry record. A derivation unit included in the server device;
A second acquisition unit provided in the participation device for acquiring identification information from a medium for using a payment service;
A coincidence determination unit that determines whether or not the identification information acquired by the first acquisition unit and the identification information acquired by the second acquisition unit match;
When the match determination unit determines that the match is made, the payment service is used to perform payment processing for the amount of the fee, and when the match determination unit determines that they do not match, the payment processing is not performed. A ticket gate system comprising: a first settlement unit included in the apparatus. Including an entry device used when entering an area that requires a fee for entry, an entry device used when entering from the area, and a server device;
A third acquisition unit included in the admission device that acquires identification information from a medium for using a payment service;
A first storage unit included in the server device for storing a record of entry into the area in association with the identification information acquired by the third acquisition unit;
A first acquisition unit included in the participation device that acquires identification information from a medium for using a payment service;
An entry record associated with the same identification information as the identification information obtained by the first obtaining unit is obtained from the first storage unit, and the amount of the fee is derived based on the obtained entry record. A derivation unit included in the server device;
A second acquisition unit provided in the participation device for acquiring identification information from a medium for using a payment service;
A first payment unit that performs a payment process for the amount of the fee using the payment service that can be used by the medium from which the second acquisition unit has acquired identification information;
An erroneous receipt determination unit that determines that an erroneous receipt has occurred when the identification information acquired by the first acquisition unit and the identification information acquired by the second acquisition unit do not match;
When it is determined that the misacceptance has occurred by the misacceptance determination unit, the identification information obtained by the first acquisition unit that the misacceptance has occurred, and the settlement amount required by the generated misreception, and A ticket gate system comprising: a second storage unit included in the server device, which is stored in association with each of the identification information acquired by the second acquisition unit. A first price acquisition unit included in the server device, which acquires a settlement amount associated with the same identification information as the identification information acquired by the first acquisition unit from the second storage unit;
4. The ticket gate system according to claim 3, wherein the first settlement unit performs a settlement process for a total amount of the amount of the fee and the settlement amount acquired by the first amount acquisition unit. A second price acquisition unit provided in the server device, which acquires a settlement amount associated with the same identification information as the identification information acquired by the third acquisition unit from the second storage unit;
A fourth acquisition unit included in the admission device that acquires identification information from a medium for using a payment service;
The admission device, which performs a settlement process for the settlement amount acquired by the second amount acquisition unit using the settlement service that can be used by the medium from which the fourth acquisition unit has acquired identification information. The ticket gate system according to claim 3 or 4, further comprising: a second settlement unit provided. It further includes a photographing device for photographing the participation device,
The second storage unit, when the misacceptance determination unit determines that the misacceptance has occurred, causes the first acquisition unit to capture an image captured by the imaging device when the misacceptance occurs. The ticket gate system according to any one of claims 3 to 5, wherein the ticket gate system is stored in association with at least one of the acquired identification information and the identification information acquired by the second acquisition unit.   The erroneous receipt determination unit determines that the person who deceived the medium in the first acquisition unit and the person deceived the medium in the second acquisition unit are the same person. 7. The device according to claim 3, wherein it is determined that no erroneous receipt has occurred even if the identification information acquired by the acquisition unit does not match the identification information acquired by the second acquisition unit. The ticket gate system according to item 1.