JP7094757B2 - Relay device, relay method, and program - Google Patents

Description

Embodiments of the present invention relate to relay devices, relay methods, and programs.

Conventionally, a relay device (station affairs repeater) equipped with a dedicated system for appropriately controlling software used in various station affairs equipment and managing data has been proposed. The relay device is connected to, for example, a plurality of automatic ticket gates and a higher-level server, and performs various processes in cooperation with the automatic ticket gates.

Further, conventionally, a remote control technique for restarting various devices at a time desired by a user has been known. Since such a communication device needs to be always in operation during business, various devices are restarted during non-business hours such as at night.

However, in the conventional relay device, there is a possibility that the restart process may occur even during the night work by the maintenance person. Therefore, the maintenance person may be confused by the fact that the restart process is performed without permission, or may redo the maintenance work interrupted by the restart process.

Japanese Unexamined Patent Publication No. 2009-94556 Japanese Unexamined Patent Publication No. 2008-1235112 Japanese Unexamined Patent Publication No. 2006-268146

An object to be solved by the present invention is to provide a relay device, a relay method, and a program capable of providing an environment in which a worker can easily work.

The relay device of the embodiment has a communication unit, a business processing unit, a maintenance processing unit, and a reboot execution unit. The communication unit communicates with the automatic ticket gate, the host server, and the station affairs terminal. The business processing unit transmits the result of the processing performed at the automatic ticket gate to the higher-level server. The maintenance processing unit executes maintenance processing by remote control from the station affairs terminal. The reboot execution unit executes the reboot process at a predetermined timing. The maintenance processing unit displays an interface for executing the start of the reboot process and an interface for extending the start time of the reboot process on the screen displayed on the station office terminal in response to the remote control.

The schematic diagram of the station affairs system 1 including the relay device 100 of an embodiment. The block diagram which shows the relay device 100. A sequence diagram showing an example of the processing flow of the watching service. The figure which shows an example of the relay notice screen displayed by the relay device 100. The flowchart which shows an example of the flow of the reboot process by a relay device 100.

Hereinafter, the relay device, the relay method, and the program of the embodiment will be described with reference to the drawings.

FIG. 1 is a schematic diagram of a station affairs system 1 including the relay device 100 of the embodiment. The station affairs system 1 of FIG. 1 includes, for example, a relay device 100, a monitoring panel 20, an operation console 30, one or more higher-level servers 50, and one or more automatic ticket gates 60. The relay device 100, the monitoring panel 20, the operation console 30, and the automatic ticket gate 60 are installed in the station yard. Each of these components is connected to each other via a network such as a LAN (Local Area Network) or a WAN (Wide Area Network). FIG. 1 shows an example in which different upper servers 50-1 to 50-3 are connected to the upper portions of the relay device 100, the monitoring panel 20 and the operation console 30, but for example, the monitoring panel 20 and the operation console 30 are connected. It may be connected to the same upper server 50. Hereinafter, when the upper server is not particularly distinguished, it is referred to as the upper server 50.

The relay device 100 monitors the status of a predetermined number of automatic ticket gates 60 assigned to itself (for example, a maximum of 32), and receives and collects predetermined data from the automatic ticket gate 60 to be monitored. After accumulating the collected predetermined data for a certain period of time, the data is transmitted to the upper server 50-1. The predetermined data is, for example, identification information (for example, a card number) of a non-contact wireless card (IC card) held by a user who has passed through the automatic ticket gate 60.

The monitoring board 20 monitors the operating status of the relay device 100 and the automatic ticket gate 60. The monitoring panel 20 includes, for example, a display device such as a display and an input device such as a keyboard. The monitoring panel 20 may also serve as a display device for the relay device 100, and has a function of remotely controlling the relay device 100. The monitoring board 20 is operated by, for example, a stationmaster or a person in charge of maintenance of the station affairs system 1.

Like the monitoring panel 20, the operation console 30 monitors the operating status of the relay device 100 and the automatic ticket gate 60. The operation console 30 includes, for example, a display device such as a display and an input device such as a keyboard, similarly to the monitoring panel 20. The operation console 30 may also serve as a display device for the relay device 100, and has a function of remotely controlling the relay device 100. The operation console 30 is operated by, for example, a station clerk. When it is not necessary to particularly distinguish the functions that can be operated by the station staff and the stationmaster or the maintenance staff of the station affairs system 1, the operation console 30 may be the same device as the monitoring panel 20. In the following, the operation console 30 will be described on the premise that it is a device different from the monitoring panel 20. The monitoring panel 20 and the operation console 30 are examples of "station affairs equipment".

The host server 50 has, for example, a function of transmitting predetermined data received from the relay device 100 to a system other than the station affairs system 1, and a maintenance / update processing function of the relay device 100 and the automatic ticket gate 60. Further, the upper server 50 instructs the relay device 100 and the automatic ticket gate 60 to transmit the data corresponding to the specific identification information. The upper server 50 may be configured by one or more servers, or may be configured by a plurality of servers.

The automatic ticket gate 60 reads information on an IC card that is a wireless ticket. The automatic ticket gate 60 performs a process of determining passability according to a valid period, a valid section, a charge balance of an IC card, and the like based on the read information, and performs the following process based on the determination result. When it is determined that the passage is permitted, the ticket gate is kept open, the balance information of the IC card is displayed on the display unit, and the display light indicating the discount target person (for example, a child) is turned on. When it is determined that the passage is not permitted, the ticket gate is closed and the display unit is displayed with the reason for not permitting the passage (for example, insufficient balance).

Further, the automatic ticket gate 60 transmits, for example, a part or all of the information read from one IC card to the relay device 100 as one record. The record includes, for example, information for identifying whether the user has entered or exited the station with an IC card held, and information on the time when the record was generated. The automatic ticket gate 60 may transmit the record to the relay device 100 at the timing when one record is generated, or may accumulate and transmit the record for a certain period of time. The automatic ticket gate 60 accumulates records while the relay device 100 is stopped due to a reboot (restart) or the like, and resumes transmission of records when the relay device 100 resumes processing. The automatic ticket gate 60 may transmit all the records to the upper server 50, or may extract the records corresponding to the specific identification information and transmit them to the upper server 50.

FIG. 2 is a block diagram showing a relay device 100. The relay device 100 of FIG. 2 includes, for example, a communication unit 110, a control unit 120, a business processing unit 130, a maintenance processing unit 140, a reboot execution unit 150, and a storage unit 160. Each of these components except the storage unit 160 of the relay device 100 is realized by, for example, a hardware processor such as a CPU (Central Processing Unit) executing a program (software). In addition, some or all of these components are hardware (circuits) such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), GPU (Graphics Processing Unit), etc. It may be realized by the part; including circuitry), or it may be realized by the cooperation of software and hardware. The program may be stored in advance in a storage device such as an HDD (Hard Disk Drive) or a flash memory, or may be stored in a removable storage medium such as a DVD (Digital Versatile Disc) or a CD-ROM for storage. The medium may be installed in the storage device by being attached to the drive device.

The communication unit 110 communicates with the upper server 50 shown in FIG. 1, the monitoring panel 20, the operation console 30, and the automatic ticket gate 60 to transmit and receive data. The communication unit 110 receives, for example, a record from the automatic ticket gate 60 and outputs it to the control unit 120. Further, the communication unit 110 outputs a processing instruction received from the monitoring panel 20 to the control unit 120. The processing instruction received from the monitoring board 20 is, for example, an instruction for rebooting the relay device 100. Further, the communication unit 110 outputs the processing results of the business processing unit 130, the maintenance processing unit 140, and the reboot execution unit 150 to the upper server 50 and the monitoring board 20.

The control unit 120 controls each component of the relay device 100. The control unit 120 stores, for example, a record output by the communication unit 110 in the storage unit 160. Further, the control unit 120 outputs a processing instruction to any of the business processing unit 130, the maintenance processing unit 140, and the reboot execution unit 150, for example, based on the processing instruction output by the communication unit 110. Further, the control unit 120 outputs the processing results of the business processing unit 130, the maintenance processing unit 140, and the reboot execution unit 150 to the communication unit 110, and outputs the processing results to the storage unit 160 for storage.

The business processing unit 130 performs a record transmission process of transmitting a record corresponding to the specific identification information stored in the storage unit 160 to the upper server 50 via the communication unit 110. When the record transmission to the upper server 50 is completed, the business processing unit 130 may add flag information indicating that the transmission is completed to the record stored in the storage unit 160 for identification. As an example of the record transmission process performed by the business processing unit 130, there is a watching service or the like. The details of the watching service will be described later.

The maintenance processing unit 140 executes maintenance processing of the relay device 100 based on a remote control instruction from the monitoring panel 20 or the operation console 30. The maintenance process is, for example, a process associated with a temporary work of manually executing a specific application mounted on the relay device 100, such as changing a setting value of the relay device 100, checking an operating status, and updating a program. The set value is, for example, the IP address of the relay device 100, the connected upper server 50, the automatic ticket gate 60, or the number of connected automatic ticket gates 60. The operation status confirmation is, for example, confirmation of the number of transmitted / received data of the relay device 100, confirmation of an abnormality occurrence status, confirmation of an operation log, and the like.

The maintenance processing unit 140 determines whether or not the relay device 100 may start the reboot process, and when it is determined that the reboot process may be started, the reboot execution unit 150 informs the reboot execution unit 150 of the reboot process of the relay device 100. To do. If the maintenance processing unit 140 does not determine that the reboot processing may be started, the maintenance processing unit 140 accepts a change in the start time of the reboot processing.

For example, when the relay device 100 is not in maintenance work, the maintenance processing unit 140 instructs the reboot execution unit 150 to execute at a preset timing (for example, a set time such as "every day, 2:30 am"). Is output and the reboot process is performed. When the relay device 100 is undergoing maintenance work, the maintenance processing unit 140 is a display device provided on the work terminal of the maintenance worker of the relay device 100 (for example, a monitoring board 20 or a PC (Personal Computer) other than the monitoring board 20). At a predetermined grace timing (for example, 10 minutes before the reboot start time) earlier than the preset timing, the maintenance worker is notified of the start timing of the reboot process, and the start notice is displayed. Further, when the maintenance processing unit 140 receives an instruction to change the start time of the reboot processing from the maintenance worker, the maintenance processing unit 140 delays the start time of the reboot processing by a predetermined time (for example, about 15 minutes).

The maintenance processing unit 140 may accept a reboot execution instruction by a maintenance worker, for example, even at a timing other than the preset timing.

The reboot execution unit 150 executes the reboot process based on the reboot execution instruction of the maintenance process unit 140.

Hereinafter, a monitoring service, which is an example of record transmission processing performed by the business processing unit 130, will be described. The watching service is, for example, when a person to be watched (for example, a child) holds an IC card and passes through the automatic ticket gate 60, the service user (for example, a guardian of a child) passes to the terminal used at the passing time and the station used. It is a service that notifies information such as by e-mail. The upper server 50 stores in advance the identification information of the IC card used by the watched target person, which is applied by the service user, and stores it in the automatic ticket gate 60 via the relay device 100. The identification information of the IC card of the subject to be watched is an example of "specific identification information".

FIG. 3 is a sequence diagram showing an example of the processing flow of the watching service. From step S100 to step S110 in FIG. 3, a guardian who is a service user is an example of a flow of processing an application for a watching service.

First, the child who is the target person to be watched teaches the identification information of the IC card to be used to the guardian who is the service user (step S100). Next, the guardian recognizes the identification information of the IC card used by the child (step S102). Next, the upper server 50 is a dedicated service application site for monitoring the identification information of the IC card used by the child. The registration application by the guardian is accepted via the above (step S104). In the process of step S104, the upper server 50 also accepts the registration of the information of the user terminal that receives the notification to the guardian. Next, the upper server 50 stores the identification information of the IC card used by the child and transmits it to the relay device 100 (step S106). Next, the relay device 100 stores the identification information of the IC card used by the child received from the host server 50 and transmits it to the automatic ticket gate 60 (step S108). Next, the automatic ticket gate 60 stores the received identification information of the IC card used by the child (step S110).

Further, steps S112 to S126 of FIG. 3 are an example of a process flow until the guardian is notified that the child, who is the target person to be watched after the application, has passed the automatic ticket gate 60. First, the automatic ticket gate 60 receives the identification information from the IC card held by the child (step S112). Next, the automatic ticket gate 60 creates a record of the IC card (step S114), identifies the identification information of the IC card corresponding to the created record (step S116), and identifies the identification information of the IC card. It is determined that the identification information corresponds to the above, and the record is transmitted to the relay device 100 (step S118).

Next, the business processing unit 130 of the relay device 100 receives the record from the automatic ticket gate 60 (step S120) and transmits it to the upper server 50 (step S122). Next, the host server 50 receives the record from the relay device 100 (step S124) and notifies the terminal used by the guardian that the child has passed the automatic ticket gate 60 (step S126). Next, the terminal used by the guardian receives the notification from the upper server 50 (step S128). This completes the processing of this sequence.

FIG. 4 is an example of a display of a notice of the start of the reboot process, which is displayed by the maintenance processing unit 140 on the display device provided in the work terminal of the maintenance worker. The maintenance processing unit 140 displays, for example, the start notice shown in FIG. 4 at 2:20 am, which is a predetermined grace timing. The maintenance processing unit 140 displays, for example, information such as a reboot start time in the start notice. In addition, the maintenance processing unit 140 displays an interface such as an "OK" button that is pressed when it is confirmed that the reboot may be performed, and a "15 minute extension" button that is pressed when the reboot start time is extended. Let me.

When, for example, the maintenance processing unit 140 confirms that the OK button has been pressed, the maintenance processing unit 140 starts the reboot processing at 2:30 am, which is a preset timing. Further, for example, when the maintenance processing unit 140 confirms that the 15-minute extension button has been pressed, the maintenance processing unit 140 changes the start time of the reboot processing at 2:45 am, which is 15 minutes after the preset start time. Then, at a predetermined grace timing (for example, if the changed reboot processing start time is 2:45 am, 10 minutes before that, 2:35 am), counting from the changed reboot process start time. The notice of the start of the reboot process is displayed again.

In addition, for example, when the reboot start time arrives without pressing any of the buttons of the start notice, the maintenance processing unit 140 may wait without starting the reboot processing until the OK button is pressed, or OK. Some kind of alert may be given, such as displaying a warning screen indicating that the button has not been pressed. Further, the maintenance processing unit 140 may hide the start notice display when a certain period of time (for example, about 2 to 3 hours) has elapsed after the start notice is displayed. Further, the maintenance processing unit 140 determines whether or not the maintenance work by the worker has already been completed when the start notice display is hidden, and if it is determined that the maintenance work has been completed, the reboot process is performed. May be started, or the reboot process on the day may be stopped.

Further, when the OK button of the reboot process start notice is pressed, the maintenance process unit 140 may delete the reboot process start notice display or leave it displayed. When the maintenance processing unit 140 keeps displaying the notice display of the start of the reboot process, whether or not the OK button is pressed is expressed by, for example, a color or a shape indicating the state in which the button is pressed. Further, the maintenance processing unit 140 may accept the operation of the 15-minute extension button even when the OK button is already pressed when the reboot processing start notice display is left displayed.

FIG. 5 is a flowchart showing an example of the flow of the process of determining whether or not the reboot process can be started by the maintenance process unit 140. In the flowchart shown in FIG. 5, for example, the process is started at the time when the start notice display of the reboot process is displayed.

First, the maintenance processing unit 140 determines whether or not the relay device 100 is in maintenance work (step S200). If it is not determined that the relay device 100 is in maintenance work, the process of step S216 described later is performed. When it is determined that the relay device 100 is in maintenance work, the maintenance processing unit 140 determines whether or not it is time to display the reboot processing start notice display (step S202). When it is determined that it is time to display the start notice display of the reboot process, the maintenance processing unit 140 displays the start notice display (step S204). If it is not determined that it is time to display the start notice display of the reboot process, the process returns to step S200.

The maintenance processing unit 140 determines whether or not the 15-minute extension button of the start notice display has been pressed (step S206). The reboot start time is extended by 15 minutes (step S208), and the process returns to the process of step S200. If it is not determined that the 15-minute extension button has been pressed, the maintenance processing unit 140 determines whether or not the OK button of the start notice display has been pressed (step S210).

If it is not determined that the OK button has been pressed in the process of step S210, the maintenance processing unit 140 performs the process of step S206. When it is determined that the OK button is pressed, the maintenance processing unit 140 determines whether or not the reboot start time has been reached (step S212). If it is determined that the reboot start time has been reached, the maintenance processing unit 140 starts the reboot processing (step S214). If it is not determined that the reboot start time has been reached, the process of step S212 is performed again after a certain period of time has elapsed.

If it is determined in the process of step S200 that the maintenance work is not in progress, the maintenance process unit 140 determines whether or not the reboot start time has been reached (step S216). If it is determined that the reboot start time has been reached, the process of step S214 is performed. If it is not determined that the reboot start time has been reached, the process of step S200 is performed again after a certain period of time has elapsed. This completes the processing of this flowchart.

Further, in the flowchart of FIG. 5, an example is shown in which the processes of steps S206 and S210 are repeated and the reboot process is not started unless the OK button or the extension button is pressed, but the reboot process is not started, but the reboot process is not started. If 2 to 3 hours have passed, the reboot process on the day may be stopped, or a step to determine whether the maintenance work by the worker has already been completed has been added and completed. If it is determined, the reboot process may be started.

Further, in the flowchart of FIG. 5, an example in which the maintenance processing unit 140 extends the start time of the reboot process by 15 minutes is given, but for example, the time that can be extended may be selected from a plurality of options or changed. It may be possible to directly enter a later start time.

According to at least one embodiment described above, the communication unit 110 communicates with the automatic ticket gate 60, the upper server 50, the monitoring panel 20 and the operation console 30 which are station office terminals, and the business processing unit 130 communicates with the automatic ticket gate. The result of the processing performed in 60 can be transmitted to the upper server 50, and the maintenance processing unit 140 can accept the change of the start time of the reboot processing by remote control by the maintenance staff.

Further, according to the above-described embodiment, when the maintenance process is not particularly performed by the maintenance worker, the maintenance process unit 140 causes the reboot execution unit 150 to execute the reboot process at a predetermined timing, so that the worker can perform the reboot process. It is possible to provide an environment that is easy to work with.

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 embodiments, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and variations thereof are included in the scope of the invention described in the claims and the equivalent scope thereof, as are included in the scope and gist of the invention.

100 ... Relay device, 110 ... Communication unit, 120 ... Control unit, 130 ... Business processing unit, 140 ... Maintenance processing unit, 150 ... Reboot execution unit, 20 ... Monitoring panel, 30 ... Operation console, 50 ... Upper server, 60 ... Automatic ticket gate

Claims (3)

A relay device installed at a station
Communication department that communicates with automatic ticket gates, higher-level servers, and station affairs terminals,
A business processing unit that sends the result of processing performed at the automatic ticket gate to the higher-level server, and
The maintenance processing unit that executes maintenance processing by remote control from the station affairs terminal,
It is equipped with a reboot execution unit that executes a reboot process at a predetermined timing.
The maintenance processing unit displays an interface for executing the start of the reboot process and an interface for extending the start time of the reboot process on the screen displayed on the station office terminal in response to the remote control.
Relay device. The computer of the relay device installed at the station
Communicate with automatic ticket gates, higher-level servers, and station affairs terminals,
The result of the processing performed in the automatic ticket gate is transmitted to the upper server, and the result is transmitted to the upper server.
The maintenance process is executed by remote control from the station affairs terminal.
The maintenance process includes executing a reboot process at a predetermined timing, an interface for executing the start of the reboot process on a screen displayed on the station office terminal in response to the remote control, and the reboot process . Show an interface to extend the start time of
Relay method. To the computer of the relay device installed at the station
Communicate with automatic ticket gates, higher-level servers, and station affairs terminals,
The result of the processing performed in the automatic ticket gate is transmitted to the upper server, and the result is transmitted.
The maintenance process is executed by remote control from the station affairs terminal.
The maintenance process includes executing a reboot process at a predetermined timing, an interface for executing the start of the reboot process on a screen displayed on the station office terminal in response to the remote control, and the reboot process . Display an interface to extend the start time of
program.

Images