JP2021174055A - Station service device, center server apparatus, and program - Google Patents

Abstract

To provide a station service device, a center server apparatus, and a program that enable earlier detection of failures, while suppressing an amount of communication by monitoring life-and-death at an appropriate frequency.SOLUTION: A station service device of an embodiment includes a center unit, a life-and-death monitor unit, and a connection control unit. The center unit detects an object. The life-and-death monitor unit transmits a life-and-death monitor message to the center server apparatus when detecting the object by the center unit and after a predetermined interval time elapses since the last communication with the center server apparatus is success. The connection control unit controls to switch a connection destination of the communication to a center server apparatus of a standby system when not receiving a response corresponding to the life-and-death message in a predetermined time.SELECTED DRAWING: Figure 1

Description

Embodiments of the present invention relate to station affairs equipment, center server equipment, and programs.

A cloud-type station affairs system (typically, a cloud-type ticket gate system) is a system in which at least a part of the processing conventionally performed by a ticket gate or the like is executed on the center server device side. The process executed on the center server device side is, for example, a determination process of tickets (for example, in the case of an IC type ticket, a process using information possessed by the IC type ticket). Another process executed on the center server device side is, for example, a process of generating detailed data (data for deducting an amount such as a fare from the amount information of the IC type ticket).

Unlike a system in which processing is completed inside a ticket gate or in a station, in a cloud-type station affairs system, if the center server device and the ticket gate are not connected by communication, nothing can be processed. In order to maintain the availability of the cloud-type station service system, it is necessary to monitor life and death between the ticket gate and the center server device.

On the other hand, in the cloud-type station affairs system, when the number of connected station affairs devices is large, the communication packet communication amount required for alive monitoring may increase proportionally. In addition, the processing load of the center server device may increase. Further, depending on the capacity of the communication network and the like, there is a possibility that problems such as communication delay may occur.

If, for example, the cycle for exchanging alive monitoring messages is lengthened in order to reduce the amount of packet communication, the detection of a failure of the center server device or a communication abnormality will be delayed. On the other hand, there is a dilemma that if the frequency of alive monitoring messages is increased in order to accelerate the detection of failures and communication abnormalities, the communication load will increase.

Japanese Unexamined Patent Publication No. 2018-032162

The problem to be solved by the present invention is to provide station affairs equipment, a center server device, and a program capable of early detection of a failure or the like while suppressing the amount of communication by performing life-and-death monitoring at an appropriate frequency. be.

The station service device of the embodiment has a sensor unit, a life-and-death monitoring unit, and a connection control unit. The sensor unit detects an object. The life-and-death monitoring unit is a life-and-death monitoring message when the sensor unit detects an object and after a predetermined interval time has elapsed since the last successful communication with the center server device. Is transmitted to the center server device. The connection control unit controls to switch the communication connection destination to the standby center server device when the response corresponding to the alive monitoring message is not received within a predetermined time.

The block diagram which shows the schematic functional structure of the ticket gate of 1st Embodiment. The block diagram which shows the configuration example of the whole station affairs system of 1st Embodiment. A view (plan view) of a state in which the ticket gate of the first embodiment is installed, as viewed from above. A view (side view) of the main engine of the ticket gate of the first embodiment as viewed from the side (passage side). The main engine of the ticket gate of 1st Embodiment is seen from the diagonally front upper side (perspective view). The sequence diagram which shows the example of the communication sequence between the ticket gate of 1st Embodiment and a center server apparatus. The sequence diagram which shows another example of the communication sequence between the ticket gate of 1st Embodiment and a center server apparatus. The flowchart which shows the processing procedure of the function which the ticket gate of 1st Embodiment has. The flowchart which shows the processing procedure of the life-and-death monitoring processing function which the ticket gate of 1st Embodiment has. The flowchart which shows the processing procedure of the ticket gate processing function which the ticket gate of 1st Embodiment has. The schematic diagram which shows the appearance of the modification of the ticket gate of 1st Embodiment. The block diagram which shows the schematic functional composition of the station affairs equipment of 2nd Embodiment. The block diagram which shows the configuration example of the whole station affairs system of 2nd Embodiment.

Hereinafter, the station service equipment, the center server device, and the program of the embodiment will be described with reference to the drawings.

(First Embodiment)
FIG. 1 shows a schematic functional configuration of the ticket gate 1 of the present embodiment. FIG. 2 shows a schematic configuration of the station affairs system 700 of the present embodiment.

The station affairs system 700 according to the present embodiment includes a ticket gate 1 and a center server device 300. The ticket gate 1 is a kind of cloud-type station affairs equipment. The ticket gate processing in the station affairs system 700 is not completed only in the ticket gate 1 (or the system in the station), and involves processing on the center server device 300 side. Specifically, the main part such as determination for ticket gate processing in the ticket gate 1 is performed on the center server device 300 side. The ticket gate 1 is a so-called thin client. The ticket gate 1 transmits information on tickets (referred to as "ticket gate information") to the center server device 300, and the center server device 300 performs business processing including determination processing on tickets. The center server device 300 returns the information as a result of this business process (referred to as "ticket gate response") to the ticket gate 1. The ticket gate 1 performs processing based on the ticket gate response received from the center server device 300. A typical process performed by the ticket gate 1 based on the ticket gate response is control of opening / closing the gate (door portion) of the ticket gate.

The ticket gate 1 normally waits for the arrival of a user on the premise that a communication connection with the center server device 300 has been established. The ticket gate 1 has a function of switching to a connection to another center server device 300 when the connection with the center server device 300 is cut off or when the center server device is not operating due to a failure or the like. ..

The time from when the user holds the ticket over the ticket gate 1 until the ticket gate 1 completes the ticket gate processing is very short, within a few seconds. Therefore, it is desirable that the ticket gate 1 detects a failure as soon as possible and quickly switches the center server device 300. Therefore, the ticket gate 1 has a function of performing a life-and-death monitoring process with the center server device 300. The process of life and death monitoring is also called "health check" or the like. The alive monitoring process is a process for confirming that the ticket gate, the center server device, and the communication network are operating normally and that the predetermined process can be executed within a predetermined time. The life-and-death monitoring process is performed by first sending a life-and-death monitoring message to the center server device 300, and then the ticket gate 1 receiving a life-and-death response message from the center server device 300. "Life-and-death monitoring message" and "life-and-life response message" may be called by other names. The "life-and-death monitoring message" is also called a "life-and-life monitoring command" as an example.

The center server device 300 includes a working device and a standby device. The standby system center server device 300 is a target to be switched and connected by the ticket gate 1 when the active system center server device 300 breaks down or communication is disconnected. The active center server device 300 and the standby center server device 300 do not necessarily have a one-to-one correspondence. Further, a certain center server device 300 may function as a standby system of another center server device 300 while operating as a working device.

One of the problems of the station affairs system 700 is to detect a failure or the like early in order to reduce the delay of the ticket gate processing in the event of a failure or the like. Another issue of the station affairs system 700 is to reduce the amount of communication in the entire station affairs system 700. If the amount of communication increases, the cost of the communication network will increase. Early detection of failures and the suppression of communication volume in networks are mutually contradictory requirements. One of the methods for detecting a failure or the like at an early stage is to increase the frequency of life-and-death monitoring, but increasing the frequency of life-and-death monitoring leads to an increase in communication volume. The station affairs system 700 of the present embodiment attempts to solve this dilemma.

The basic operation of the station affairs system 700 is as follows.
1) The cloud-type ticket gate 1 detects the approach or existence of an object such as a user (person). When the ticket gate 1 detects a user or the like, the ticket gate 1 notifies the center server device 300 of a life-and-death monitoring message.
2) After notifying the life-and-death monitoring message, the ticket gate 1 does not send a further life-and-death monitoring message when the approach or existence of the user (person) is continuously detected. If another user is detected after a predetermined time has elapsed after the transmission of the life-and-death monitoring message, that is, after the expiration of the interval timer (“timer T1” described later), the ticket gate 1 again monitors the life-and-life monitoring. Notify the center server device 300 of the message.
3) When the life-and-death response message is returned from the center server device 300, the ticket gate 1 waits for the user to hold the ticket or the like as it is.
4) If the life-and-death response message is not returned from the center server device 300, the ticket gate 1 switches the center server device 300 to be connected. That is, the ticket gate 1 starts the connection with the standby system center server device 300.
5) When the user holds an IC card type ticket, holds an optical two-dimensional code, or inserts a ticket with magnetic code information, the ticket gate 1 is connected. Communicates with the center server device 300 to perform ticket gate processing (passenger processing). The ticket gate process includes a determination process for tickets and a process for controlling the opening and closing of a gate (door).

In the present embodiment, since the ticket gate 1 performs the life-and-death monitoring process, it is possible to quickly detect a failure or malfunction of a component of the station affairs system 700. Therefore, the ticket gate 1 can quickly switch to the connection destination center server device 300. As a result, the amount of delay in processing (ticket gate processing, etc.) due to a cause such as a failure is reduced. Further, in the present embodiment, since the life-and-death monitoring process is performed only when the ticket gate 1 detects a user or the like, the amount of communication on the network can be suppressed. Further, even if the ticket gate 1 continuously detects a user or the like within a predetermined time, the life-and-death monitoring process is not repeated many times. Therefore, the amount of communication on the network can be suppressed. In addition to suppressing the amount of network communication, the load on the center server device is also reduced.

FIG. 1 is a block diagram showing a schematic functional configuration of a ticket gate (station affairs equipment) according to the present embodiment. The ticket gate 1 performs a process of reading information on tickets and determining its validity in transportation such as a railroad, and controls opening and closing of an entrance / exit gate according to the determination result. It is a device for processing (charging fare, etc.) associated with the use of tickets. As described above, the ticket gate 1 operates in cooperation with the center server device 300.

As shown in the figure, the ticket gate 1 includes a control unit 20, a sensor unit 61, and an information acquisition unit 62. Further, the control unit 20 includes a life-and-death monitoring unit 111, a ticket gate processing unit 112 (business processing unit), a communication unit 113, and a connection control unit 114. At least some of the functions of each of these parts can be realized using, for example, a general-purpose computer and a program. Further, at least a part of the functions of each part may be realized by a dedicated electronic circuit or the like. Further, each unit may be internally provided with a function of storing data (for example, a semiconductor memory, a magnetic disk device, or the like), if necessary. The functions of each part are as described below.

The control unit 20 controls the operation of the ticket gate 1. The functions of the life-and-death monitoring unit 111, the ticket gate processing unit 112, the communication unit 113, and the connection control unit 114 of the control unit 20 will be described later.

The control unit 20 has a timer that keeps time. The control unit 20 may have a plurality of timers for use for a plurality of purposes. One of the timers of the control unit 20 is the timer T1. This timer T1 is also called a "life-and-death monitoring interval timer". That is, the timer T1 is a timer used to manage whether or not a predetermined interval time that requires alive monitoring has elapsed after being reset. The timer T1 is set to "00:00:00" (time zero, 0:00:00) by, for example, a reset signal. Further, the value of the timer T1 is increased with the passage of time (however, conversely, the value may be decreased). Each functional unit in the ticket gate 1 can reset the timer T1 by a predetermined signal. Specifically, when the communication between the ticket gate 1 and the center server device 300 is successful, the functional unit in the ticket gate 1 resets the timer T1. As a specific example, when the ticket gate 1 receives some response message (life-and-death response message, ticket gate response message, etc.) from the center server device 300, the functional unit in the ticket gate 1 resets the timer T1. .. Further, each functional unit in the ticket gate 1 can obtain information on the value of the timer T1. Specifically, each functional unit can obtain information on whether or not a predetermined interval time has elapsed (timer has expired) after the timer T1 is reset. The length of the above interval time can be preset. The interval time is set to an appropriate length of, for example, several tens of seconds or more and several minutes or less.

The sensor unit 61 detects an object. Specifically, the sensor unit 61 detects that an object approaches the ticket gate 1 and that the object exists at a predetermined location in the vicinity of the ticket gate 1 by having an optical sensor. Here, the object to be detected by the sensor unit 61 is the body of the user (person) or an object associated therewith. The sensor unit 61 has at least one of a transmissive photoelectric sensor and a reflective photoelectric sensor. The sensor unit 61 may be configured to have both a transmissive photoelectric sensor and a reflective photoelectric sensor. The location where the transmissive photoelectric sensor and the reflective photoelectric sensor are provided will be described later with reference to FIGS. 4 and 5. For example, when the main engine (10) and the slave unit (30) of the ticket gate are installed substantially in parallel, the transmission type photoelectric sensor and the reflection type photoelectric sensor are in the area between the main engine and the slave unit (the user passes through). It is possible to detect a user who invades (which is a passage). In that case, the passage direction of the passage is the longitudinal direction of the ticket gate 1. The reflective photoelectric sensor provided in front of the ticket gate 1, that is, at the end of the ticket gate 1 in the longitudinal direction detects an object (user or the like) approaching the ticket gate 1 in the longitudinal direction.

The sensor unit 61 includes a transmission type photoelectric sensor St, a reflection type photoelectric sensor Sr, and a reflection type photoelectric sensor Sr2, which will be described later. When each of the transmissive photoelectric sensor St, the reflective photoelectric sensor Sr, and the reflective photoelectric sensor Sr2 detects an object (user or the like), the sensor signal is passed to the control unit 20.

The information acquisition unit 62 has a function of acquiring information from a medium such as a ticket. Specifically, the information acquisition unit 62 acquires information recorded on a medium such as a ticket by appropriately using the functions of various reading means such as magnetic reading, electromagnetic wave reading, or optical reading. do. That is, for example, the information acquisition unit 62 reads the magnetically coded information from the magnetic ticket or the like. Alternatively, the information acquisition unit 62 reads information from an IC card type ticket or the like by electromagnetic waves. Alternatively, the information acquisition unit 62 reads the code information from the tickets on which the barcode or the two-dimensional code is printed by using the optical reading means. The two-dimensional code is code information in which a predetermined pattern composed of, for example, two values of white and black is arranged on a two-dimensional paper surface or the like. An example of a two-dimensional code is a QR code (registered trademark). The information acquisition unit 62 passes the acquired information to the ticket gate processing unit 112.
The information acquisition unit 62 includes a reading unit 11 and a reading unit 31, which will be described later.

The life-and-death monitoring unit 111 performs the life-and-death monitoring process. Specifically, the alive monitoring unit 111 transmits a alive monitoring message to the center server device 300, and determines whether or not there is a response corresponding to the alive monitoring message. The life-and-death monitoring unit 111 of the present embodiment is when the sensor unit 61 detects an object and after a predetermined interval time has elapsed since the communication with the center server device 300 was successful. , Send a life-and-death monitoring message to the center server device 300. In order to know whether or not the predetermined interval time has elapsed, the life-and-death monitoring unit 111 refers to the timer T1 described above.

The ticket gate processing unit 112 performs ticket gate processing for tickets. The ticket gate processing unit 112 is a kind of business processing unit for processing the business of the station. The ticket gate processing unit 112 transmits the ticket information acquired by the information acquisition unit 62 to the center server device 300 as ticket gate information. Further, the ticket gate processing unit 112 receives the response information (sometimes referred to as “ticket gate response”) corresponding to the above ticket gate information from the center server device 300. The above ticket gate information includes availability information regarding tickets. Based on this availability information, the ticket gate processing unit 112 permits or prohibits the user holding the tickets from passing through the ticket gate 1. Specifically, the ticket gate processing unit 112 outputs a display according to the availability information. Further, the ticket gate processing unit 112 controls the opening and closing of the gate (door unit) of the ticket gate 1 according to the availability information.

The ticket gate processing unit 112 performs error processing when there is no ticket gate response (not received) corresponding to the transmitted ticket gate information. This error handling may include displaying a message on the screen. Further, as a part of this error processing, the ticket gate processing unit 112 may request the connection control unit 114 to switch the connection of the center server device 300 (for example, switch to the standby system).

The communication unit 113 communicates with an external device. More specifically, the communication unit 113 transmits and receives data in response to a request from the life-and-death monitoring unit 111 and the ticket gate processing unit 112 (business processing unit). When the communication unit 113 fails in the transmission / reception processing of the requested data (including the case of a timeout waiting for reception), the communication unit 113

The connection control unit 114 controls the connection of communication between the ticket gate 1 and the external device. Specifically, the connection control unit 114 controls the connection of communication between the ticket gate 1 and the center server device 300. The connection control unit 114 also controls switching of connections between the plurality of center server devices 300.

The procedure for switching the center server device 300 from the active system to the standby system is as follows, for example. That is, the above-mentioned life-and-death monitoring unit 111 transmits a life-and-death monitoring message to the center server device. The life-and-death monitoring unit 111 waits for the life-and-death response message as a response to the life-and-death monitoring message. For example, if the alive monitoring unit 111 does not receive the alive response message within a predetermined time, the alive monitoring unit 111 requests the connection control unit 114 to switch the center server device. In response to this, the connection control unit 114 controls switching to the standby system center server device 300. That is, the connection control unit 114 controls to switch the communication connection destination to the standby center server device when the response corresponding to the alive monitoring message is not received within a predetermined time.

Further, when the connection with a certain center server device 300 cannot be established, the connection control unit 114 may attempt to connect with another center server device 300 as appropriate. Further, even when an error in a communication connection with a certain center server device 300 (such as a disconnection event of a connected communication) is detected, the connection control unit 114 appropriately connects with another center server device 300. You may try to connect between them.

FIG. 2 is a block diagram showing a configuration example of the entire station affairs system including a ticket gate, a center server device, and the like. As shown in the figure, the station affairs system 700 is configured to include a ticket gate 1, a center server device 300, a network 91, and a relay device 92. The station affairs system 700 may include a plurality of ticket gates 1. Further, the station affairs system 700 may include a plurality of center server devices 300. The ticket gate 1 can communicate with the center server device 300 via the network 91. A plurality of ticket gates 1 installed at a plurality of stations or the like may be connected to the center server device 300 via the network 91. In the network 91, for example, communication by the Internet Protocol (IP) is performed. However, communication may be performed using any other protocol.

The ticket gate 1 has the functions described with reference to FIG. That is, the ticket gate 1 is a sensor (optical sensor) arranged on the front portion (end in the longitudinal direction) or the side portion (passage side) of the ticket gate 1, and is used for approaching a user (person) or passing through the ticket gate. Is detected. When the sensor unit 61 detects a user (person) or the like, the ticket gate 1 performs a life-and-death monitoring process.

The center server device 300 receives information from the ticket gate 1 (station affairs equipment) and performs business processing according to the received information. Specifically, the center server device 300 receives information on tickets from the ticket gate 1 and performs a determination process (determines whether or not the user can pass through the passage of the ticket gate 1), or if necessary. And generate payment data. The center server device 300 returns the processing result (response information) to the ticket gate 1. The response information may include availability information. The availability information is information indicating that the user is permitted or prohibited from passing through the passage of the ticket gate 1.

In addition, the center server device 300 performs a life-and-death monitoring process. Specifically, the center server device 300 receives the life-and-death monitoring message transmitted from the ticket gate 1 (station affairs equipment). Further, the center server device 300 transmits a life-and-death response message as a response to the life-and-death monitoring message. When the center server device 300 is in a non-operating state (malfunction, etc.), the center server device 300 cannot transmit this life-and-death response message. Further, even when a communication network failure or the like occurs, the life-and-death monitoring process cannot be performed between the ticket gate 1 and the center server device 300.

The plurality of center server devices 300 are made redundant. That is, when a certain center server device 300 cannot operate due to a failure or the like, another center server device 300 can perform processing instead. The plurality of center server devices 300 may be provided in the same data center, or may be distributed in remote data centers. The center server device 300 may be realized by using a so-called cloud server.
One center server device 300 can simultaneously respond to processing requests from a large number of ticket gates 1.

The network 91 is a network for performing data communication. The network 91 is realized by using, for example, a dedicated communication line. At least a part of the network 91 may be the Internet.

The relay device 92 is a device that relays communication between the network 91 and the plurality of center server devices 300. The relay device 92 may have a load balancer function for distributing the load of the center server device 300.

FIG. 3 is a top view (plan view) of the state in which the ticket gate of the present embodiment is installed. The ticket gate 1 is installed at, for example, a railway station or the like, and performs ticket gate processing for tickets. Further, the ticket gate 1 may control the opening and closing of the door portion (gate) in order to allow or prohibit the passage of the user holding the ticket in accordance with the ticket gate processing. The ticket gate 1 includes a main engine 10 and a slave unit 30 which are arranged so as to face each other across a passage. The main engine 10 includes, for example, a reading unit 11, a top surface display unit 12, a front display unit 13, door units 14 and 15, and a control unit 20. Further, the slave unit 30 includes a reading unit 31, a top surface display unit 32, a front display unit 33, and door units 34 and 35.

The reading unit 11 of the main engine 10 reads information from the tickets held by the user who intends to pass in the direction a of FIG. The reading unit 11 may read information using at least one of reading means such as magnetic reading, electromagnetic wave reading, or optical reading. The information read by the reading unit 11 is passed to the control unit 20 via the information acquisition unit 62 (FIG. 1).

The top surface display unit 12 includes a display device realized by using a liquid crystal display element or the like. For example, the upper surface display unit 12 displays the result of processing caused by the reading unit 11 reading the information held by the user.

The front display unit 13 includes a display device realized by using a liquid crystal display element or the like. The front display unit 13 displays, for example, a mark, a graphic character, a character, or the like indicating whether or not the vehicle can pass in the a direction of FIG. The display content of the front display unit 13 or the presence or absence of the display is determined by the control unit 20.

On the other hand, the reading unit 31 of the slave unit 30 reads information from the tickets held by the user who intends to pass in the direction b of FIG. The reading unit 31 reads information on tickets using the same technical means as the reading unit 11. The information read by the reading unit 31 is passed to the control unit 20 via the information acquisition unit 62 (FIG. 1).

The top surface display unit 32 includes a display device realized by using a liquid crystal display element or the like. For example, the upper surface display unit 12 displays the result of processing caused by the reading unit 31 reading the information held by the user.

The front display unit 33 includes a display device realized by using a liquid crystal display element or the like. The front display unit 33 displays, for example, a mark, a graphic character, a character, or the like indicating whether or not the vehicle can pass in the direction b of FIG. The display content of the front display unit 33 or the presence or absence of the display is determined by the control unit 20.

When the ticket gate 1 is set to the operation mode that allows the user to pass in the direction a in FIG. 3, the control unit 20 keeps the door units 15 and 35 in the open state and the door unit 14 By controlling the and 34 in the open state or the closed state, the passage of the user in the a direction is permitted or prohibited. Further, when the ticket gate 1 is set to the operation mode for allowing the user to pass in the direction b in FIG. 3, the control unit 20 keeps the door units 14 and 34 in the open state and the doors. By controlling the parts 15 and 35 to be in the open state or the closed state, the passage of the user in the b direction is permitted or prohibited.

Further, the operation mode of the ticket gate 1 may include an operation mode that allows both passage in the a direction and passage in the b direction in FIG. In this case, the control unit 20 of the main engine 10 is controlled to display, for example, a mark, a graphic character, a character, or the like indicating that both the front display unit 13 and the front display unit 33 are allowed to pass if the user is not passing. I do. Further, for example, when a user enters from either side and a ticket is held over one of the reading unit 11 and the reading unit 31, the control unit 20 invalidates the other reading unit and also invalidates the other reading unit. Control is performed to display marks, figures, characters, etc. indicating that passage is prohibited on the display unit (front display unit 13 or front display unit 33) on the side where the user has not entered.

The vertical direction in FIG. 3 is the longitudinal direction of the ticket gate 1 (main engine 10 and slave unit 30). The surface on which the front display units 13 and 33 are provided is the "front" of the ticket gate 1. Strictly speaking, when the user tries to pass in the a direction, the surface on which the front display unit 13 is provided is the "front" of the ticket gate 1 (main engine 10). When the user tries to pass in the b direction, the surface on which the front display unit 33 is provided is the "front" of the ticket gate 1 (secondary machine 30).

FIG. 4 is a view of the main engine 10 of the ticket gate 1 of the present embodiment as viewed from the side surface (passage side). The main engine 10 further includes a transmission type photoelectric sensor St and a reflection type photoelectric sensor Sr in addition to the reading unit 11 and the door portions 14 and 15. A plurality of transmissive photoelectric sensors St are provided, for example, on the housing surface on the passage side of the housing surface of the main engine 10 at equal intervals.

In the present embodiment, a transmissive photoelectric sensor St that functions as a floodlight and a transmissive photoelectric sensor St that functions as a receiver are used as a pair. For example, when the transmissive photoelectric sensor St provided in the main engine 10 is a floodlight, the transmissive photoelectric sensor St provided on the slave unit 30 side functions as a light receiver.

The transmissive photoelectric sensor St provided on the slave unit 30 side receives the projected light emitted from the transmissive photoelectric sensor St on the main engine 10 side when there is no such thing as blocking light in the passage. On the other hand, when a user is present in the passage, the projected light emitted from the transmissive photoelectric sensor St is blocked by the user. Therefore, the transmissive photoelectric sensor St on the slave unit 30 side does not receive the projected light emitted from the transmissive photoelectric sensor St.

The control unit 20 acquires a detection signal from the transmissive photoelectric sensor St and determines whether or not there is a person in the passage. For example, when the control unit 20 acquires the detection signal generated when the projected light is not received from the transmissive photoelectric sensor St, the control unit 20 determines that there is no user who blocks the projected light in the passage. Further, when the detection signal generated when the projected light is received is acquired from the transmissive photoelectric sensor St, the control unit 20 determines that there is a user who blocks the projected light in the passage.

Similar to the transmissive photoelectric sensor St, a plurality of reflective photoelectric sensors Sr are provided at equal intervals on, for example, a passage-side surface of a partition portion protruding upward from the housing of the main engine 10. The reflective photoelectric sensor Sr projects light in a predetermined direction. The reflective photoelectric sensor Sr projects light and then receives the light reflected from the projected direction.

The reflective photoelectric sensor Sr generates a detection signal indicating whether or not a user's body that reflects light is present in the passage based on the intensity of the received light. For example, when the intensity of the received light is equal to or less than the threshold value, the reflection type photoelectric sensor Sr generates a detection signal indicating that the user does not exist in the passage. Further, when the intensity of the received light exceeds the threshold value of the reflective photoelectric sensor Sr, a detection signal indicating that a user is present in the passage is generated.

The above-mentioned reflection type photoelectric sensor Sr has been described as being provided in the main engine 10, but the present invention is not limited to this, and the reflection type photoelectric sensor Sr may be provided in the slave unit 30, or may be provided in both the main engine 10 and the slave unit 30. good.

FIG. 5 is a perspective view of the main engine 10 of the ticket gate 1 of the embodiment as viewed diagonally from above. Here, the front surface is a surface on the side where the front display unit 13 is provided. The main engine 10 further includes a reflective photoelectric sensor Sr2 in addition to the reading unit 11 and the front display unit 13. The reflective photoelectric sensor Sr2 is provided, for example, below the front surface of the main engine 10. That is, the reflective photoelectric sensor Sr2 is provided at the end of the ticket gate 1 (main engine 10) in the longitudinal direction. With such an arrangement, the reflective photoelectric sensor Sr2 can detect a user (person) or the like approaching the ticket gate 1 from the front side.
The reflective photoelectric sensor Sr2 is also provided below the front surface of the slave unit 30 on the opposite side, if necessary.

FIG. 6 is a sequence diagram showing an example of a communication sequence between the ticket gate and the center server device of the present embodiment. In the illustrated example, the ticket gate 1 executes the ticket gate processing a plurality of times after exchanging life-and-death monitoring. After that, when the predetermined time elapses (timer T1 expires), the life-and-death monitoring exchange is performed again. Hereinafter, a description will be given with reference to this sequence diagram.

Assuming that the sequence of FIG. 6 is started, the timer T1 has expired.
In that situation, the sensor unit 61 of the ticket gate 1 detects an event such as an approach of a user. With the detection of this event as a trigger, the ticket gate 1 executes the operation of the next step S1.

In step S1, the life-and-death monitoring unit 111 of the ticket gate 1 transmits a life-and-death monitoring message to the center server device 300. After transmitting the life-and-death monitoring message, the life-and-death monitoring unit 111 of the ticket gate 1 waits for the arrival of the life-and-death response message from the center server device 300. The center server device 300 receives the alive monitoring message transmitted from the ticket gate 1.
In step S2, the center server device 300 transmits a life-and-death response message to the ticket gate 1 of the transmission source as a response to the life-and-death monitoring message received in step S1. The life-and-death monitoring unit 111 of the ticket gate 1 receives this life-and-death response message. By receiving the life-and-death response message, the life-and-death monitoring unit 111 of the ticket gate 1 knows that the network 91 is normal and that the center server device 300 to which the life-and-death monitoring message is transmitted is operating normally. ..

Next, the user holds the ticket over the reading unit 11 or 31 of the ticket gate 1. As a result, the information acquisition unit 62 of the ticket gate 1 acquires information on tickets. The information acquisition unit 62 passes the acquired ticket information to the ticket gate processing unit 112. The ticket gate processing unit 112 performs a predetermined ticket gate processing based on the information of the passed tickets. As a part of this, the ticket gate processing unit 112 makes an inquiry to the center server device 300. The communication sequence for that is the following steps S3 and S4.

In step S3, the ticket gate processing unit 112 of the ticket gate 1 transmits the ticket gate information to the center server device 300. The ticket gate information includes information on tickets acquired by the information acquisition unit 62. The center server device 300 receives this ticket gate information.
In step S4, the center server device 300 performs a determination process or the like based on the ticket gate information received in step S3, and transmits a ticket gate response including the result information to the ticket gate 1 which is the source of the ticket gate information. The ticket gate processing unit 112 of the ticket gate 1 receives this ticket gate response. The ticket gate processing unit 112 performs processing based on the information of the ticket gate response. The process executed by the ticket gate processing unit 112 in this step includes control for permitting or prohibiting the passage of the user (door opening / closing control) and the like.

Next, another user holds the ticket over the reading unit 11 or 31 of the ticket gate 1. The following processes of steps S5 and S6 are the same as the processes of steps S3 and S4 described above.
That is, in step S5, the ticket gate processing unit 112 of the ticket gate 1 transmits the ticket gate information to the center server device 300. The center server device 300 receives the ticket gate information.
Further, in step S6, the center server device 300 transmits the ticket gate response corresponding to the ticket gate information received in step S5 to the ticket gate 1. The ticket gate processing unit 112 of the ticket gate 1 receives the ticket gate response.

Next, another user holds the ticket over the reading unit 11 or 31 of the ticket gate 1. The following processes of steps S7 and S8 are the same as the processes of steps S3 and S4 described above.
That is, in step S7, the ticket gate processing unit 112 of the ticket gate 1 transmits the ticket gate information to the center server device 300. The center server device 300 receives the ticket gate information.
Further, in step S8, the center server device 300 transmits the ticket gate response corresponding to the ticket gate information received in step S7 to the ticket gate 1. The ticket gate processing unit 112 of the ticket gate 1 receives the ticket gate response.

During the processing from step S3 to step S8, a plurality of users arrived at the ticket gate 1 in quick succession and used the ticket gate 1. During this time, the ticket gate 1 did not execute the procedure for alive monitoring. After that, when the user's foot is cut off, the timer T1 expires as shown in the figure. After the expiration, the sensor unit 61 of the ticket gate 1 detects an event such as an approach of a user. With the detection of this event as a trigger, the ticket gate 1 executes the operation of the next step S9.

In step S9, the life-and-death monitoring unit 111 of the ticket gate 1 transmits a life-and-death monitoring message to the center server device 300. The center server device 300 receives the alive monitoring message transmitted from the ticket gate 1.
In step S10, the center server device 300 transmits a life-and-death response message to the ticket gate 1 of the transmission source as a response to the life-and-death monitoring message received in step S9. The life-and-death monitoring unit 111 of the ticket gate 1 receives this life-and-death response message.

As shown in FIG. 6, in the present embodiment, after a predetermined interval time has elapsed from successful communication between the ticket gate 1 and the center server device 300 (after the timer T1 expires), the sensor unit 61 When the vehicle detects an object, the life-and-death monitoring unit 111 of the ticket gate 1 transmits a life-and-death monitoring message to the center server device 300. In other words, if a predetermined interval time elapses (timer T1 expires) without receiving any response message from the center server device 300, the life-and-death monitoring process is repeated. In this way, by suppressing the frequency of performing the life-and-death monitoring process, it is possible to prevent an increase in the amount of communication.

FIG. 7 is a sequence diagram showing another example of the communication sequence between the ticket gate and the center server device of the present embodiment. In the illustrated example, the ticket gate 1 detects a failure of the center server device 300A through the procedure of life and death monitoring. After that, the ticket gate 1 switches the connection destination server to the center server device 300B, and then executes the ticket gate process. Hereinafter, a description will be given with reference to this sequence diagram.

In step S21, the life-and-death monitoring unit 111 of the ticket gate 1 transmits a life-and-death monitoring message to the center server device 300A. After transmitting the life-and-death monitoring message, the life-and-death monitoring unit 111 of the ticket gate 1 waits for the arrival of the life-and-death response message from the center server device 300A. In the sequence shown in this figure, the life-and-death response message from the center server device 300A is not returned to the ticket gate 1 due to some kind of failure or the like. The life-and-death monitoring unit 111 of the ticket gate 1 detects a response timeout by a notification from a timer or the like.

In step S22, the connection control unit 114 of the ticket gate 1 transmits a server switching request to the center server device 300B, which is the switching destination.
In step S23, the center server device 300B transmits a server switching completion response as a response to the server switching request received in step S22. The connection control unit 114 of the ticket gate 1 receives this server switching completion response. As a result, the connection between the ticket gate 1 and the center server device 300B is established.

Next, the user holds the ticket over the reading unit 11 or 31 of the ticket gate 1. As a result, the information acquisition unit 62 of the ticket gate 1 acquires information on tickets. The information acquisition unit 62 passes the acquired ticket information to the ticket gate processing unit 112. The ticket gate processing unit 112 makes an inquiry to the center server device 300B as part of the ticket gate processing. The communication sequence for that is the following steps S24 and S25.

In step S24, the ticket gate processing unit 112 of the ticket gate 1 transmits the ticket gate information to the center server device 300. The center server device 300 receives this ticket gate information.
In step S25, the center server device 300 performs processing based on the ticket gate information received in step S24, and transmits a ticket gate response including the result information to the ticket gate 1 which is the transmission source of the ticket gate information. The ticket gate processing unit 112 of the ticket gate 1 receives this ticket gate response. The ticket gate processing unit 112 performs processing based on the information of the ticket gate response.

Next, another user holds the ticket over the reading unit 11 or 31 of the ticket gate 1. The following processes of steps S26 and S27 are the same as the processes of steps S24 and S25 described above.
That is, in step S26, the ticket gate processing unit 112 of the ticket gate 1 transmits the ticket gate information to the center server device 300B. The center server device 300B receives the ticket gate information.
In step S27, the center server device 300B transmits the ticket gate response corresponding to the ticket gate information received in step S26 to the ticket gate 1. The ticket gate processing unit 112 of the ticket gate 1 receives the ticket gate response.
Hereinafter, similarly, it is possible to continue the exchange between the ticket gate 1 and the center server device 300B.

The procedure for the ticket gate 1 to switch the center server device does not have to be the procedure shown in steps S22 and S23 of FIG. 7. Other procedures may be used. In either case, the ticket gate 1 switches the connection destination server and starts the exchange with the center server device 300B when it is determined that there is no response from the center server device 300A by exchanging a life-and-death monitoring message or the like. ..

As shown in FIG. 7, in the present embodiment, when there is no response from the center server device 300A to the alive monitoring message (when a timeout or the like occurs), the ticket gate 1 goes to another server, the center server device 300B. Switch to the connection. The ticket gate 1 transmits a life-and-death monitoring message to the center server device 300A when the sensor unit 61 detects the approach of the user or the like. That is, the life-and-death monitoring of the center server device can be started at a timing before the user holds the ticket over the reading unit 11 or 31. This makes it possible to switch the connection destination to the center server device 300B more quickly in the event of a failure of the center server device 300A, for example. That is, it is possible to shorten the time for the user to wait.

8, 9, and 10 are flowcharts showing a processing procedure of the function of the ticket gate 1. By executing this processing procedure, the ticket gate 1 can realize the sequence described with reference to FIGS. 6 and 7. The processes shown in FIGS. 9 and 10 are processes called from the processes shown in the flowchart of FIG. Hereinafter, description will be given along with these flowcharts.

In step S41 of FIG. 8, the control unit 20 of the ticket gate 1 determines whether or not the end condition is satisfied. As an example, when a command to shut down the ticket gate 1 is input, the end condition is satisfied. If the end condition is satisfied (step S41: YES), the processing of the entire flowchart is terminated. If the end condition is not satisfied (step S41: NO), the process proceeds to the next step S42.

Next, in step S42, the control unit 20 of the ticket gate 1 waits for the arrival of the event. The event is, for example, detecting a sensor signal from the sensor unit 61, or the information acquisition unit 62 acquiring information such as a ticket. When the control unit 20 detects the arrival of the event, the process proceeds to the next step S43.

Next, in step S43, the control unit 20 of the ticket gate 1 performs branching based on the type of event that has arrived. Specifically, when the sensor signal from the sensor unit 61 is detected, the process proceeds to step S44. When the information acquisition unit 62 acquires the information, the process proceeds to step S46.

Next, when the process proceeds to step S44, the life-and-death monitoring unit 111 of the ticket gate 1 determines whether or not the timer T1 has expired. If the timer T1 has expired (step S44: YES), the process proceeds to step S45. If the timer T1 has not expired (step S44: NO), the process returns to step S41.
If the process proceeds to step S45, a life-and-death monitoring process is performed. Details of the alive monitoring process are shown in FIG. When the process of step S45 is completed, the process returns to step S41.
If the process proceeds to step S46, the ticket gate processing is performed. Details of the ticket gate processing procedure are shown in FIG. When the process of step S46 is completed, the process returns to step S41.

FIG. 9 is a flowchart showing the procedure of the alive monitoring process by the ticket gate 1. Hereinafter, the description will be given according to this flowchart.

In step S61, the life-and-death monitoring unit 111 of the ticket gate transmits a life-and-death monitoring message to the center server device 300. After that, the life-and-death monitoring unit 111 waits for a life-and-death response message from the destination center server device 300.

In step S62, the life and death monitoring unit 111 of the ticket gate determines whether or not there is a response from the center server device 300. If the alive response message is received from the center server device 300 within a predetermined time after the alive monitoring message is transmitted, the response is "Yes". If the response is “Yes” (step S62: YES), the process proceeds to step S63. If the alive response message is not received from the center server device 300 (when timed out) within a predetermined time after the alive monitoring message is transmitted, the response is "none". If the response is “none” (step S62: NO), the process proceeds to step S65.

When the process proceeds to step S63, the life-and-death monitoring unit 111 of the ticket gate 1 resets the timer T1 in the same step. As a result, the timer T1 restarts the time counting from zero time.
Next, in step S64, the life-and-death monitoring unit 111 of the ticket gate 1 processes the life-and-death response message.
When the process of step S64 is completed, the ticket gate 1 ends the process of the entire flowchart (FIG. 9).

On the other hand, when the process proceeds to step S65, in the same step, the connection control unit 114 of the ticket gate 1 performs a process of switching the center server device 300 of the connection destination. The process of switching the center server device 300 is executed, for example, in the procedure shown in steps S22 and S23 of FIG. As a result, the connection destination of the ticket gate 1 is switched from the center server device 300 that did not return a response to the alive monitoring message (step S61) to another center server device 300. That is, it is expected that the center server device 300, which is the new connection destination, is more likely to be operating normally than the center server device 300 that did not return a response.
When the process of step S65 is completed, the ticket gate 1 ends the process of the entire flowchart (FIG. 9).

FIG. 10 is a flowchart showing a procedure of ticket gate processing by the ticket gate 1. Hereinafter, the description will be given according to this flowchart.

In step S81, the ticket gate processing unit 112 of the ticket gate 1 transmits the ticket gate information to the center server device 300. The ticket gate information includes information on tickets read by the ticket gate 1. After that, the ticket gate processing unit 112 waits for a ticket gate response from the destination center server device 300.

In step S82, the ticket gate processing unit 112 of the ticket gate determines whether or not there is a response from the center server device 300. If the ticket gate response is received from the center server device 300 within a predetermined time after the ticket gate information is transmitted (step S81), the response is "Yes". If the response is “Yes” (step S82: YES), the process proceeds to step S83. If the ticket gate response is not received from the center server device 300 (when timed out) within a predetermined time after the ticket gate information is transmitted, the response is "none". If the response is “none” (step S82: NO), the process proceeds to step S85.

When the process proceeds to step S83, the ticket gate processing unit 112 of the ticket gate 1 resets the timer T1 in the same step. As a result, the timer T1 restarts the time counting from zero time.
Next, in step S84, the ticket gate processing unit 112 of the ticket gate 1 performs processing based on the received ticket gate response information (for example, control of permission or prohibition of passage of the passenger through the passage of the ticket gate 1).
When the process of step S84 is completed, the ticket gate 1 ends the process of the entire flowchart (FIG. 10).

On the other hand, when the process proceeds to step S85, the ticket gate processing unit 112 of the ticket gate 1 displays an error message in the same step. This error message is displayed, for example, on the top display unit 12 or 32.
Next, in step S86, the connection control unit 114 performs a process of switching the connection destination center server device 300. This process is the same as the process of step S65 of FIG. As a result, the connection destination of the ticket gate 1 is switched from the center server device 300 that did not return a response to the ticket gate information (step S81) to another center server device 300.
When the process of step S86 is completed, the ticket gate 1 ends the process of the entire flowchart (FIG. 10).

As described above, as shown in the flowchart, the ticket gate 1 performs the life-and-death monitoring process when the sensor unit 61 detects the object and a predetermined time has elapsed since the previous communication exchange with the center server device 300. Only when completed (timer T1 has expired).

FIG. 11 is a diagram showing the appearance of a modified example of the ticket gate 1. The ticket gate 1 shown in the figure has a reading unit for reading information on tickets and a display unit for displaying information. However, the ticket gate 1 is a simple ticket gate that does not have a door. In the figure, Sr2 is a reflective photoelectric sensor provided in the ticket gate 1. The reflective photoelectric sensor Sr2 detects the approach of a user (person) or the like.

(Second Embodiment)
Next, the second embodiment will be described. In the following, the matters peculiar to the present embodiment will be mainly described. The matters already described in the first embodiment may be omitted here. In the second embodiment, the station affairs system is configured to include station affairs equipment 2 other than the ticket gate 1 (the ticket gate for ticket gates). The station equipment 2 other than the ticket gate is, for example, a payment machine that pays for fares, a vending machine that sells tickets, and a charge for IC-type tickets (addition of stored fairs). It is a charging machine to perform.

FIG. 12 is a functional block diagram showing a schematic functional configuration of the station service equipment 2 of the present embodiment. As shown in the figure, the station affairs device 2 includes a control unit 20a, a sensor unit 61, and an information acquisition unit 62. Further, the control unit 20a includes a life-and-death monitoring unit 111, a business processing unit 117, a communication unit 113, and a connection control unit 114. At least some of the functions of each of these parts can be realized using, for example, a general-purpose computer and a program. Further, at least a part of the functions of each part may be realized by a dedicated electronic circuit or the like.

In the station affairs equipment 2, the sensor unit 61, the information acquisition unit 62, the life-and-death monitoring unit 111, the communication unit 113, and the connection control unit 114 each have the same functions as those in the first embodiment. Is. The information acquisition unit 62 acquires information such as tickets, IC-type tickets (cards), and credit cards by using magnetic reading means, electromagnetic wave reading means, optical reading means, and the like.

The business processing unit 117 has a business processing function according to the role of each station affairs equipment.
When the station affairs equipment 2 is, for example, a settlement machine, the business processing unit 117 receives information on tickets to be settled from the information acquisition unit 62. Then, the business processing unit 117 performs settlement processing for the tickets and issues, for example, a settlement ticket. The settlement process is, for example, a process of collecting a shortage of a fare or the like from a user.
When the station affairs equipment 2 is a vending machine for tickets, the business processing unit 117 receives information such as an IC card having a stored fair function and a credit card for payment from the information acquisition unit 62. Then, the business processing unit 117 performs a process of selling the tickets designated by the user.
Further, when the station affairs device 2 is a device for charging the IC type ticket, the business processing unit 117 receives the information of the IC type ticket from the information acquisition unit 62. Then, the business processing unit 117 executes a process of charging the IC type ticket (adding the stored fair).
That is, the business processing unit 117 transmits the ticket information acquired by the information acquisition unit 62 to the center server device 300, and receives the response information corresponding to the ticket information from the center server device 300.

FIG. 13 is a block diagram showing a configuration example of the station affairs system of the present embodiment. As shown in the figure, the station affairs system 701 is configured to include a ticket gate 1, a station affairs device 2, a center server device 300, a network 91, and a relay device 92. The station affairs system 700 may include a plurality of ticket gates 1 and a plurality of station affairs devices 2. Further, the station affairs system 700 may include a plurality of center server devices 300. The ticket gate 1 and the station affairs equipment 2 can each communicate with the center server device 300 via the network 91.

The station service equipment 2 in the present embodiment behaves in the same manner as the ticket gate 1 in the first embodiment with respect to the life-and-death monitoring process. That is, when the life-and-death monitoring unit 111 detects an object by the sensor unit 61 and after a predetermined interval time has elapsed since the last successful communication with the center server device 300. , Send a life-and-death monitoring message to the center server device 300. Further, the connection control unit 114 controls to switch the communication connection destination to the standby center server device 300 when the response corresponding to the above-mentioned life-and-death monitoring message is not received within a predetermined time. In addition, the information acquisition unit 62 acquires information on tickets by at least one of a magnetic reading means, an optical reading means, and an electromagnetic wave reading means. Then, the business processing unit 117 transmits the ticket information acquired by the information acquisition unit 62 to the center server device 300, and receives the response information corresponding to the ticket information from the center server device 300.

According to at least one embodiment described above, the station affairs equipment (ticket gate 1 etc.) is when the sensor unit 61 detects an object, and the communication with the center server device 300 is finally successful. It has a life-and-death monitoring unit 111 that transmits a life-and-death monitoring message to the center server device 300 after a predetermined interval time has elapsed. As a result, the frequency with which the station affairs equipment (ticket gate 1 or the like) transmits a life-and-death monitoring message can be suppressed only when it is highly necessary. That is, the amount of communication in the system can be suppressed. Further, the station affairs equipment (ticket gate 1 etc.) is a connection control unit that controls the communication connection destination to be switched to the standby center server device 300 when the response corresponding to the alive monitoring message is not received within a predetermined time. Has 114. As a result, the switching of the center server device 300 can be completed prior to the information acquisition unit 62 acquiring the information and starting the processing (as soon as a few seconds). That is, the degree of waiting for the users is relatively small.

It should be noted that at least a part of the functions of the ticket gate 1, the station affairs device 2, and the center server device 300 in each of the above-described embodiments may be realized by a computer. In that case, the program for realizing this function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read by the computer system and executed. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. The "computer-readable recording medium" is a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, a DVD-ROM, or a USB memory, or a storage device such as a hard disk built in a computer system. Say that. Further, a "computer-readable recording medium" is a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line, and dynamically holds the program for a short period of time. It may also include a program that holds a program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or a client in that case. Further, the above-mentioned program may be a program for realizing a part of the above-mentioned functions, and may be a program for realizing the above-mentioned functions in combination with a program already recorded in the computer system.

Of the terms used in the above description, "IC" means an integrated circuit. In addition, "tickets" include various tickets such as fare tickets and admission tickets in addition to tickets for railways and the like.

Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, as well as in the scope of the invention described in the claims and the equivalent scope thereof.

1 ... Ticket gate (station affairs equipment), 2 ... Station affairs equipment, 10 ... Main engine, 11 ... Reader, 12 ... Top display, 13 ... Front display, 14 ... Door, 15 ... Door, 20, 20a ... control unit, 30 ... slave unit, 31 ... reading unit, 32 ... top display unit, 33 ... front display unit, 34 ... door unit, 35 ... door unit, 61 ... sensor unit, 62 ... information acquisition unit, 91 ... network , 92 ... Relay device, 111 ... Life and death monitoring unit, 112 ... Ticket gate processing unit (business processing unit), 113 ... Communication unit, 114 ... Connection control unit 117 ... Business processing unit, 300, 300A, 300B ... Center server device, 700,701 ... station affairs system, Sr, Sr2 ... reflective photoelectric sensor, St ... transmissive photoelectric sensor

Claims (6)

A sensor that detects an object and
When the sensor unit detects an object and a predetermined interval time has elapsed since the last successful communication with the center server device, a life-and-death monitoring message is sent to the center server device. With the life and death monitoring department to send to
A connection control unit that controls to switch the communication connection destination to the standby center server device when the response corresponding to the life-and-death monitoring message is not received within a predetermined time.
Station affairs equipment equipped with. The information acquisition department that acquires information on tickets, and
A business processing unit that transmits information on the tickets acquired by the information acquisition unit to the center server device and receives response information corresponding to the information on the tickets from the center server device.
The station affairs equipment according to claim 1. The business processing unit transmits information on the tickets to the center server device, and receives information on the result of business processing corresponding to the ticket gate information from the center server device.
The ticket gate response includes availability information regarding the tickets.
The business processing unit controls the opening and closing of the door portion of the ticket gate based on the availability information.
The station affairs equipment according to claim 2. The sensor unit detects the object approaching substantially in the longitudinal direction by a reflective photoelectric sensor provided at the end in the longitudinal direction of the station equipment.
The station affairs equipment according to any one of claims 1 to 3. A life-and-death monitoring message transmitted from the station affairs device according to any one of claims 1 to 4 is received, and a life-and-death response message corresponding to the life-and-death monitoring message is transmitted to the station affairs device.
Center server device. Sensor unit that detects objects,
To a computer equipped with
When the sensor unit detects an object and a predetermined interval time has elapsed since the last successful communication with the center server device, a life-and-death monitoring message is sent to the center server device. With the life and death monitoring department to send to
A connection control unit that controls to switch the communication connection destination to the standby center server device when the response corresponding to the life-and-death monitoring message is not received within a predetermined time.
A program for executing the functions of.

Images