JP2011197909A - Passage management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce concentration of load on a passage management server to smoothly operate a passage management system, as the whole, in which the management server manages a plurality of exits and entrances.SOLUTION: A passage management system 10 includes a plurality of controllers 20, a management server 30 which communicates with the plurality of controllers 20, and one or more relay servers 40 which communicate with the management server 30. A high-load time in which prescribed high loads are imposed on the controllers 20, and a low-load time zone in which prescribed low loads are imposed on the controllers 20, are determined on the basis of passage history information which is generated by the controllers 20. Then, when the controllers 20 are put in the high-load time zone, the transmission of the passage history information is stopped at least until the high-load time zone elapses, and then the information concerned is transmitted to the management server 40, without the relay server 30, after the high-load time zone elapses.

Description

  The present invention relates to a traffic management system.

  In recent years, traffic management systems that manage traffic of people in specific areas such as buildings and rooms have been introduced in companies and hospitals. For example, when a passer-by goes to a specific area, the passer-by reads the specific information (authentication information) held by the recording medium or the like with a wireless reader (reading device) and analyzes it in the system. The security of a specific area is improved by determining permission / non-permission of traffic.

  As such a technique, for example, an entrance / exit management system as disclosed in Patent Document 1 below is known. In the entrance / exit management system of Patent Document 1, an authentication device is provided at the entrance of each room, and security check of the user's entrance / exit is performed based on personal authentication information of an IC / ID card for identifying the user. . The log of the user's entry / exit is monitored in real time by the log monitor, and this log is analyzed to improve the security against unauthorized entry / exit, and the load on the system is reduced by reducing the man-hours for setting up the advance security conditions. It is mitigating.

JP 2005-301928 A

  By the way, in a conventional traffic management system, one or a plurality of terminal devices (authentication devices) are generally connected directly or indirectly to a management server. In the management server, various information (traffic from the terminal device side) (E.g., authentication information and traffic history information of a user) or transmission processing of various types of information necessary for operation (e.g., passer data) is frequently performed. As described above, in the traffic management system, the amount of data to be processed on the management server side tends to increase, and in particular, there is a problem that data traffic tends to increase due to an increase in the amount of data from the terminal device side. .

  For example, in the time zone when the number of passers increases, the number of authentication processes performed by the terminal device (authentication apparatus) increases, and the amount of information (passage history information, etc.) generated along with the authentication process also increases. Therefore, in the management server that collects such information, the amount of information transmitted to and received from the terminal device in a specific time zone increases, and the processing speed of the entire system (particularly the processing speed of the management server) decreases. There is a problem such as. Such a problem becomes particularly noticeable when a large number of terminal devices are managed by a single management server, and a system in which a plurality of terminal devices are connected to a single management server (for example, a single management server) In the case of constructing a system that manages a plurality of areas, how to eliminate such a processing load is an issue.

  The present invention has been made to solve the above-described problems. In a traffic management system in which the management server can manage a plurality of entrances, the load on the management server is reduced, and the entire system is smooth. The purpose is to operate.

  In order to achieve the above object, in the traffic management system according to claim 1, a plurality of wireless readers capable of reading a recording medium on which unique information is recorded are provided, and a plurality of gateways through which passers-by can pass. A wireless management system in which each of the wireless readers is arranged, a plurality of controllers that process each reading result obtained by the plurality of wireless readers, a management server that can communicate with the plurality of controllers, One or a plurality of relay servers communicable with the management server, the relay server being assigned to one or a plurality of the controllers, and transmitting at least information from the assigned controller to the management server Comprising an information transmission means, wherein the controller is configured to be able to obtain passer data from the outside and corresponds to the controller A determination means for determining whether or not the recording medium is a passage permission target based on the unique information of the recording medium obtained by the wireless reader and the permitted passage person data, and a determination result by the determination means A traffic history information generating unit that generates traffic history information corresponding to the recording medium, and a history transmitting unit that transmits the traffic history information to the relay server or the management server. Based on the traffic history information generated in step 1, time zone determining means is provided for determining a high load time zone in which the controller is in a predetermined high load state and a low load time zone in which the controller is in a predetermined low load state. The history transmission means of the controller is based on the determination result by the time zone determination means, and when the controller is in the high load time zone, Line history information is transmitted to the relay server, and when the controller is in the high load time period, transmission of the traffic history information is stopped until at least the high load time period has elapsed, and the high load time period has elapsed. Then, it is transmitted to the management server without going through the relay server.

  The invention according to claim 2 is the traffic management system according to claim 1, wherein the time zone determining means is based on the traffic history information from a plurality of the controllers for each time zone divided at a predetermined time interval. A calculating unit that calculates a degree of the number of traffic histories in the plurality of controllers as a whole and a degree of the number of traffic histories for each of the plurality of controllers, the plurality of controllers calculated by the calculating unit; Based on the degree of the number of traffic histories for each time zone in the whole and the degree of the number of traffic histories for each time zone in each of the plurality of controllers, the high load time zone and the low load of each controller It is characterized by determining a time zone.

  According to a third aspect of the present invention, in the traffic management system according to the second aspect, the calculating unit is configured to generate a per-unit controller in the plurality of controllers for each time period based on the traffic history information from the plurality of controllers. An average value calculating means for calculating an average value of the number of traffic histories of the vehicle, and an average value of the number of traffic histories per unit controller calculated for each time period by the average value calculating means; The high load time zone and the low load time zone of each controller are determined based on the number of traffic history cases.

  According to a fourth aspect of the present invention, in the traffic management system according to the first aspect, the time zone determining means is based on the traffic history information obtained from each of the plurality of controllers, at a predetermined time interval for each controller. Computation means for calculating the degree of the number of traffic histories for each divided time zone, and based on the degree of the number of traffic histories for each time zone calculated by the controller by the controller and a predetermined threshold The high load time zone and the low load time zone of each controller are determined.

  According to a fifth aspect of the present invention, in the traffic management system according to any one of the second to fourth aspects, the history transmitting unit provided in the controller is configured to be configured so that the controller in the controller after the high-load time period elapses. The traffic history information is transmitted to the management server in the time zone in which the degree of the number of traffic histories is equal to or less than a predetermined value and in the time zone closest to the high load time zone.

  According to a sixth aspect of the present invention, in the traffic management system according to any one of the second to fifth aspects, the time zone determination unit is configured to perform the high load time for each of the time zones divided at the predetermined time interval. When one or a plurality of the controllers to be set in a band can be selected and a predetermined number or more of the controllers satisfy the condition of the high load time period in any of the competition time periods, the predetermined selection condition is satisfied. Based on the above, a part of the predetermined number or more of the controllers satisfying the condition is selected, and the high load time zone of the selected controller is excluded from the contention time zone.

  According to a seventh aspect of the present invention, in the traffic management system according to any one of the first to sixth aspects, the history transmission unit provided in the controller is configured to perform the operation after the elapse of the high load time period of the controller. A plurality of the traffic history information accumulated during the high load time period are collectively transmitted to the management server.

The invention of claim 1 includes a plurality of controllers, a management server capable of communicating with the plurality of controllers, and one or a plurality of relay servers capable of communicating with the management server. The relay server includes information transmission means that is assigned to one or a plurality of controllers and transmits at least information from the assigned controllers to the management server. In addition, the controller is configured to be able to acquire permitted person data from the outside, and the recording medium is a permitted object based on the unique information of the recording medium obtained by the corresponding wireless reader and the permitted person data. Determination means for determining whether or not, a traffic history information generating means for generating traffic history information corresponding to the recording medium based on a determination result by the determination means, and history transmission for transmitting the traffic history information to the relay server or the management server Means.
Furthermore, the traffic management system of the present invention includes a high load time zone in which the controller is in a predetermined high load state and a low load time zone in which the controller is in a predetermined low load state based on the traffic history information generated by the controller. A time zone determining means for determining. The history transmission means of the controller transmits the traffic history information to the relay server when the controller is in the low load time zone based on the determination result by the time zone determination means, and passes when the controller is in the high load time zone. The transmission of the history information is stopped at least until the high load time period elapses, and after the high load time period elapses, it is transmitted to the management server without going through the relay server.

  As a result, even if the number of controllers (authentication devices) managed by a single management server increases, when the load on the controller is relatively low, the controller is connected via each assigned relay server. Is sent to the management server, compared to the case where information is directly sent and received from each controller to the management server, the load on the management server is reduced and the entire system is operated smoothly. be able to. Also, for example, when the controller is in a high load time zone (high load time zone) such as a time zone when the number of passers increases and the number of authentication processes performed by the controller increases, the traffic history information from the controller Is stopped until at least the high load time period elapses, so even if the high load time period during which the load on the controller increases is reached, data traffic from the controller can be suppressed. For this reason, even if it is a time slot | zone (high load time slot | zone) when a controller becomes high load, it can reduce that a load concentrates on a management server and can aim at the smooth operation of the whole system. In addition, traffic history information is sent to the management server without going through a relay server after the high load time period has elapsed, so traffic history information that was stopped during high load time periods can be managed more quickly. It is possible to transmit to the server, and the traffic history can be reliably reflected on the management server while minimizing the influence of the suspension of data transmission.

  In the invention of claim 2, the degree of the number of traffic histories for each time zone in the whole of the plurality of controllers and the plurality of controllers for each time zone divided by a predetermined time interval by the calculating means provided in the time zone determining means The degree of the number of traffic histories for each time zone is calculated, and based on these, the high load time zone and the low load time zone of each controller are determined. In this way, it is possible to determine whether each controller is in a relatively high load time zone or a low load time zone based on the load status of the entire system, and an appropriate time zone setting considering the entire system Is possible.

  In the invention of claim 3, the average value calculating means provided in the calculating means calculates the average value of the number of traffic history records per unit controller calculated for each time zone, and the average value and each of the plurality of controllers are calculated. Based on the number of traffic histories, the high load time zone and the low load time zone of each controller are determined. In this way, by calculating the “average value of the number of traffic histories per unit controller” for each time zone, the average number of traffic histories for each controller when viewed from the entire system is calculated for each time zone. Can grasp. Then, by determining the high load time zone and the low load time zone of each controller based on the average value for each time zone obtained from the entire system in this way, whether each controller is in a relatively high load time zone. Whether it is a low load time zone can be appropriately determined based on a more objective criterion.

  In the invention of claim 4, the number of traffic histories for each time zone divided by a predetermined time interval for each controller based on the traffic history information obtained from each of the plurality of controllers by the calculating means provided in the time zone determining means. A degree is calculated. The high load time zone and the low load time zone of each controller are determined based on the calculated degree of the traffic history number and a predetermined threshold value. In this way, the high load time zone and the low load time zone can be appropriately determined for each controller based on the traffic history information obtained from each of the plurality of controllers and the predetermined threshold value.

  In the invention of claim 5, the history transmitting means provided in the controller is a time zone in which the degree of the number of traffic history records in the controller is equal to or less than a predetermined value after the high load time zone elapses, and the high load time zone The traffic history information is transmitted to the management server in the nearest time zone. In other words, when the load on the system becomes relatively small after the high load time period has elapsed, the transmission of the traffic history information by the controller is immediately resumed, so the time lag of reflecting the traffic history information to the system is reduced. Reflection processing can be performed in an appropriate time zone with a small load while suppressing as much as possible.

  In the invention of claim 6, the time zone determining means can select one or a plurality of controllers to be set in the high load time zone for each time zone divided by a predetermined time interval, and any of the contention times When more than a predetermined number of controllers in the band satisfy the conditions of the high load time period, a part of the selected number of controllers satisfying the conditions is selected based on a predetermined selection condition, and the selected controller's The high load time zone is excluded from the competition time zone. By configuring in this way, even if a predetermined number or more of controllers in any time zone (contention time zone) satisfy the condition of the high load time zone, the contention time zone is set as the high load time zone. The number of controllers can be narrowed down. Therefore, it is possible to effectively prevent the high load time zones of a plurality of controllers from being concentrated on a specific time zone, and the high load time zones of the controllers can be set in a balanced manner.

  In the invention of claim 7, the history transmission means provided in the controller transmits a plurality of traffic history information accumulated during the high load time period to the management server after the high load time period of the controller has elapsed. ing. In this way, by transmitting a plurality of traffic history information to the management server, the time lag of reflecting the traffic history information to the system can be further reduced, and smooth operation of the entire system can be achieved.

It is explanatory drawing which shows roughly the structure of the traffic management system 10 which concerns on this embodiment. 1 is a block diagram of a traffic management system 10 according to the present embodiment. It is a flowchart which illustrates the flow of the locking / unlocking process of the door 16 by the controller 20 which concerns on this embodiment. It is a flowchart which illustrates the flow of the history information transmission process in the traffic management system 10 which concerns on this embodiment. It is a figure for demonstrating the flow of the historical information transmission process in the traffic management system 10 which concerns on this embodiment. It is a flowchart which illustrates the flow of the history information transmission process in the traffic management system 10 which concerns on this embodiment. It is a table | surface which shows an example of the traffic history information produced | generated in the traffic management system 10 which concerns on this embodiment.

Hereinafter, an embodiment of a traffic management system according to the present invention will be described with reference to the drawings.
In the present embodiment, as shown in FIGS. 1 and 2, a case where the traffic management system 10 is adopted as a system for managing entry / exit with respect to a specific area will be described as an example. The traffic management system 10 includes a wireless reader 12, a controller 20, a relay server 30, a management server 40, and a client server 50. A door 16 that is locked and unlocked by an electric lock 14 is provided at the entrance / exit of a specific area where the traffic management system 10 is adopted. 1 and 2, the number of the controller 20, the electric lock 14, the door 16, and the relay server 30 is omitted for the sake of space.

  The wireless reader 12 is configured, for example, as a known IC card reader in terms of hardware. When a user brings a recording medium (not shown) such as an IC card into contact with or in proximity to the wireless reader 12, the IC is read. The unique information of the user recorded on the card is read, and the read unique information is input to the controller 20. The wireless reader 12 may be provided only on either the entrance side or the exit side according to the security level, or may be provided on both the entrance side and the exit side.

  As the electric lock 14, for example, an electromagnetic electric lock that locks and unlocks the door 16 by operating an electromagnet inside the electric lock when energized can be used. The door 16 is provided with an open / close sensor (not shown) so that the open / closed state of the door 16 is detected by any electromagnetic or optical method. The door 16 may be a manual type or an automatic type.

  The controller 20 is provided corresponding to the door 16, is electrically connected to the wireless reader 12 and the electric lock 14, and is communicably connected to the relay server 30 and the management server 40. The controller 20 is configured as an information processing apparatus, and includes a CPU 21, a communication unit 22, a memory 23, and a display unit 24 as shown in FIG. The CPU 21 compares the permitted passer data stored in the memory 23 with the unique information acquired by the wireless reader 12 to determine whether the IC card is permitted to pass or not, and unlocks and unlocks the electric lock 14. At the same time, based on the determination result, the traffic history information (see FIG. 7) corresponding to the IC card is generated. The communication unit 22 is configured as a communication interface for communicating with an external device, and is configured to transmit the travel history information generated by the CPU 21 to the relay server 30 or the management server 40. In addition, the communication unit 22 is configured to receive the permitted passer data from the management server 40 and output it to the CPU 21. The memory 23 includes a semiconductor memory such as a ROM, a RAM, and a non-volatile memory, and stores passer-permitted person data and traffic history information. The display unit 24 is configured by a liquid crystal display or the like, and is configured to be able to display a determination result as to whether or not the IC card is a passage permission target. The CPU 21 corresponds to an example of “determination means” and “traffic history information generation means” recited in the claims. The communication unit 22 corresponds to an example of a “history transmission unit” recited in the claims.

  The relay server 30 is configured to be able to communicate with the controller 20 and the management server 40. The number of controllers 20 connected to one relay server 30 is set to a predetermined number or less. In the present embodiment, for example, up to 100 controllers 20 are set to be connectable to one relay server 30, but can be appropriately changed according to the processing capability of the relay server 30. In this way, by limiting the number of controllers 20 connected to one relay server 30, the load on each relay server 30 can be suppressed.

The relay server 30 is configured as a computer, and includes a CPU 31, a communication unit 32, a memory 33, a display unit 34, and an operation unit 35 as shown in FIG. The CPU 31 is configured to mainly control the entire relay server. The communication unit 32 is configured by a communication interface for communicating with an external device, and is configured to transmit the travel history information received from the controller 20 to the management server 40 in response to a signal from the CPU 31. Further, the communication unit 32 transmits information such as permitted-permitter data received from the management server 40 to the controller 20 (see the flow E shown in FIG. 5 described later). The memory 33 includes a semiconductor memory such as a ROM, a RAM, and a nonvolatile memory, a hard disk, and the like, and is configured to temporarily store the received traffic history information and permitted person data. The display unit 34 is a liquid crystal monitor or the like, and is configured to be able to display the operation state of the relay server 30. The operation unit 35 includes a keyboard, a mouse, and the like. For example, the system administrator can input a signal directly to the relay server 30 by operating the operation unit 35. The communication unit 32 corresponds to an example of an “information transmission unit” described in the claims.

  The management server 40 is mainly configured to control the entire system. As described above, the management server 40 is communicably connected to the controller 20 and the relay server 30, and is also communicably connected to the client server 50. Has been. The management server 40 is configured as a computer, and includes a CPU 41, a communication unit 42, a memory 43, a display unit 44, and an operation unit 45, as shown in FIG. The CPU 41 is configured to mainly control the entire management server. The communication unit 42 is constituted by a communication interface for communicating with an external device, and transmits information such as permitted-permitter data to the relay server 30 according to a signal from the CPU 41 (D shown in FIG. 5 described later). The traffic history information is received from the relay server 30 and the controller 20. The memory 43 is configured by a semiconductor memory such as a ROM, a RAM, and a nonvolatile memory, a hard disk, and the like, and is configured to store passage permitter data and received traffic history information. The display unit 44 is a liquid crystal monitor or the like, and is configured to be able to display the operation state of the management server 40. The operation unit 45 includes a keyboard, a mouse, and the like. For example, the system administrator can input a signal directly to the management server 40 by operating the operation unit 45.

  The client server 50 is mainly configured to communicate with the management server 40, and includes a CPU 51, a communication unit 52, a memory 53, a display unit 54, and an operation unit 55, as shown in FIG. ing. The CPU 51 is configured to mainly control the entire client server 50. The communication unit 52 is configured to transmit information such as authorized person data to the management server 40 and to be able to access the traffic history information stored in the memory 43 of the management server 40. The display unit 54 is configured to be able to display the operation state of the client server 50. The operation unit 55 is configured such that a system administrator or the like can operate the operation unit 55 to update information such as authorized person data or to refer to traffic history information (described later). (Refer to the flow F shown in FIG. 5).

  Next, the unlocking process of the door 16 by the controller 20 is demonstrated using the flowchart shown in FIG. In the present embodiment, a case where the user enters the specific area by causing the wireless reader 12 to read the IC card will be described as an example.

  First, in step S101 of FIG. 3, it is determined whether or not the wireless reader 12 has read the IC card on which the user specific information is recorded. Here, when there is no user entering the room and the IC card is not read and the unique information is not input from the wireless reader 12, the determination of No is repeated in step S101.

  In such a state, when the user causes the wireless reader 12 to read the IC card and the unique information of the IC card is input to the CPU 21 (Yes in S101), it is stored in advance in the memory 23 in step S103. The authorized person data and the unique information acquired by the wireless reader 12 are collated. If the unique information does not match the permitted passer data, it is determined No in step S103. On the other hand, if the unique information matches the authorized person data (Yes in S103), the unlocking process is performed in step S105, and the electric lock 14 of the door 16 is unlocked for a certain period. When the electric lock 14 is unlocked, the user can open the door 16 and enter a specific area.

  Then, history information generation processing is performed in step S <b> 107, for example, traffic history information as shown in FIG. 7 is generated, and the generated traffic history information is stored in the memory 23 of the controller 20. Then, the generated traffic history information is transmitted to the relay server 30 or the management server 40 in a history information transmission process described later. In this history information transmission process, the passage history information is transmitted to a predetermined server (relay server 30 or management server 40) in a predetermined time zone determined in advance according to the load state of the controller 20. Details will be described in the following.

  Next, a method for determining the load state of the controller 20 will be described. The load state of the controller 20 is the degree of the number of traffic histories in each controller 20 for each time zone divided by the CPU 41 of the management server 40 at predetermined time intervals based on the traffic history information generated by the controller 20. And the degree of the number of traffic histories for each of the controllers 20 is determined. Further, the time zone in which the controller 20 is in a predetermined high load state is determined as a high load time zone, and the time zone in which the controller 20 is in a low load state is determined as a low load time zone. Here, the predetermined time interval means, for example, a time interval obtained by dividing one day every hour (in this case, 24 time zones in total).

  Specifically, the degree of the number of traffic histories in each controller 20 and the degree of the number of traffic histories for each controller 20 are the average value of the number of traffic histories per unit controller (the number of traffic histories of each controller 20 is the time. (A value obtained by dividing the total for each belt by the total number of controllers) and the number of traffic histories for each controller are calculated for each time zone. If the number of traffic histories exceeds this average value, the load is high. It is determined that the time zone condition is satisfied. When a predetermined number or more of the controllers 20 satisfy the condition of the high load time period, a part is selected from the predetermined number or more of the controllers 20 that satisfy the condition based on a predetermined selection condition. The high load time zone of the controller is set to be excluded from the contention time zone. For example, among the controllers 20 exceeding 1000 / h per unit time, the time zone of the top 10 controllers 20 is determined as the high load time zone, and the time zone of the other controllers 20 is determined as the low load time zone. be able to. The CPU 41 corresponds to an example of “time zone determination unit”, “calculation unit”, and “average value calculation unit” described in the claims.

  In the history information transmission process (S201 to S207, S505 to S509) described later, when the controller 20 is in a low load time period, the traffic history information generated in the history information transmission process is transmitted to the relay server 30, When the controller 20 is in the high load time zone, transmission of the traffic history information is stopped until the high load time zone elapses, and the traffic history information is accumulated in the memory 23 of the controller 20 and relayed after the high load time zone elapses. The data is transmitted to the management server 40 without going through the server 30. This history information transmission process will be described separately with reference to FIGS. 4 to 6 when the controller 20 is in a low load state (ie, a low load time zone) and in a high load state (ie, a high load time zone). .

  First, the management server 40 determines the high load time zone and the low load time zone of each controller by the method for determining the load state described above, and the time zone when any of the controllers 20 is determined to be in the high load state ( In other words, when it becomes a high load time zone), an instruction to stop transmission of traffic history information of the controller 20 is given to the relay server 30 to which the controller 20 is connected.

  Next, each process performed by the controller 20, the relay server 30, and the management server 40 when the controller 20 is in a low load state will be described. The history information transmission process in the controller 20 shown in FIG. 4 is performed, for example, for each process in FIG. 3 or for each fixed period. First, in step S201, a transmission history information transmission stop instruction ( It is determined whether or not there is an instruction in S605 described later. If there is an instruction to stop transmission of traffic history information from the relay server 30 (Yes in S201), a high load state process described later is performed in step S203, and a process of step S509 from step S505 described later is performed. (See FIG. 6). On the other hand, if it is determined that there is no instruction to stop transmission of the traffic history information (No in S201), a transmission confirmation signal for the traffic history information is transmitted to the relay server 30 in Step S205, and the relay server 30 stores the traffic history information. An inquiry is made as to whether or not reception is possible. When the controller 20 receives the traffic history information transmission permission signal from the relay server 30, the controller 20 transmits the traffic history information to the relay server 30 in step S <b> 207. The transmission of the traffic history information from the controller 20 has a flow A in FIG. The travel history information is transmitted to the relay server 30 until an instruction to stop transmission of the travel history information is issued.

  In relay server 30, whether or not controller 20 is in a high load time period is determined based on whether or not there is the above-described instruction (instruction to stop the traffic history information of controller 20) from management server 40 in step S301. Is determined. Then, from the above instruction until a predetermined release condition is satisfied, that is, if it is a high load time zone (Yes in S301), a process in a high load state is performed in step S303, and from step S605 to step S609 described later. Is performed (see FIG. 6). On the other hand, if it is not the high load time zone (No in S301), when a transmission confirmation signal of traffic history information is received from the controller 20 in step S305, a transmission permission signal is transmitted to the controller 20 in step S307. The relay server 30 receives the traffic history information transmitted from the controller 20 in step S309, and the traffic history information is stored in the memory 33 in step S311. Next, in step S313, it is determined whether or not it is a preset transmission time zone of the traffic history information. Here, transmission history information from the relay server 30 to the management server 40 is set to be performed at a predetermined time interval (for example, every 10 minutes), for example. If it is determined that the transmission time period is reached (Yes in S313), a transmission confirmation signal is transmitted to the management server 40 in Step S315. When the transmission permission signal for the transmission confirmation signal is received from the management server 40, the traffic history information stored in the memory 33 is transmitted to the management server 40 in step S317. The transmission of the traffic history information from the relay server 30 has a flow B in FIG.

  When the management server 40 receives the transmission confirmation signal of the traffic history information from the relay server 30, the management server 40 transmits a transmission permission signal to the relay server 30 in step S401. In step S403, the traffic history information from the relay server 30 is received. In step S405, the received traffic history information is stored in the memory 43 of the management server 40. Based on the traffic history information stored in the memory 43, the management server 40 determines the load state of each time zone of the controller 20 in step S407.

  Next, each process performed by the controller 20, the relay server 30, and the management server 40 when the controller 20 is in a low load state will be described. As shown in FIG. 6, the controller 20 determines in step S <b> 201 whether or not there is an instruction to stop transmission of traffic history information to the controller 20. If there is no instruction to stop transmission of traffic history information from the relay server 30 (No in S201), the low load state process is performed in Step S202, and the processes in Steps S205 and S207 described above are performed (FIG. 4). reference). On the other hand, if it is determined that there is an instruction to stop transmission of the traffic history information (Yes in S201), it is determined in step S503 whether or not the timing to cancel the instruction to stop transmission of the traffic history information has arrived. This transmission stop instruction release timing signal is configured to be transmitted from the relay server 30 or the management server 40 to the controller 20.

  The timing at which the transmission stop signal of the traffic history information is released is a time zone in which the degree of the traffic history number in the controller 20 is equal to or less than a predetermined value after the high load time zone has elapsed, and the high load time zone. The closest time zone is set. For example, in the management server 40, the average value of the number of traffic histories for each time zone in the past predetermined number of days is recorded for each controller 20, and for the controller 20 giving a transmission stop instruction, for example, For each time interval in which one day is divided every hour, an average value of the number of traffic history records in a predetermined number of past days is calculated and stored. The release timing can be set based on the past data (average value of the number of traffic histories for each time zone) for the controller 20 registered in this manner. For example, the high load time of the controller 20 When the average value of the number of traffic histories per unit time becomes 500 cases / h or less after the elapse of the band, the management server 40 outputs a signal indicating the timing for canceling the transmission stop instruction to the controller 20. It is like that. In step S503, the determination of “No” is repeated until a signal indicating the cancellation timing of such a transmission stop instruction is received (that is, until the cancellation timing comes). In this example, the release timing signal is directly given from the management server 40 to the controller 20. However, the release timing signal may be given to the controller 20 via the relay server 30.

  When the release timing has arrived (Yes in S503), in step S505, whether or not a transmission confirmation signal for traffic history information (that is, a transmission stop signal for traffic history information (S605 described later) is canceled) to the relay server 30 is confirmed. Signal) is transmitted. Then, when the transmission stop signal is canceled and the transmission permission signal is received from the relay server 30, the controller 20 collects a plurality of traffic history information accumulated in the memory 23 during the high load time period in step S507 ( For example, it is transmitted to the management server 40 as one transmission file. Transmission of the traffic history information from the controller 20 has a flow C in FIG. Next, in step S509, it is determined whether or not all the traffic history information stored in the memory 23 has been transmitted to the management server 40. If there is untransmitted traffic history information in the memory 23, the determination of Yes is repeated in step S509 until all the traffic history information is transmitted.

  In the relay server 30, it is determined in step S301 whether or not the controller 20 is in a high load time period. If it is not the high load time zone (No in S301), the low load state process is performed in step S302, and the processes from step S305 to step S317 described above are performed (see FIG. 4). On the other hand, if it is determined that the controller 20 is in the high load time zone (Yes in S301), a transmission stop signal of traffic history information is transmitted to the controller 20 in step S605. This transmission stop signal is transmitted to the controller 20 until a predetermined time period determined by the CPU 41 of the management server 40 (that is, a time period in which the degree of the traffic history number in the controller 20 is equal to or less than a predetermined value). to continue. When a confirmation signal is received in step S607 from the controller 20 whether or not the traffic history information transmission stop signal has been cancelled, permission to transmit the traffic history information to the controller 20 in step S609. Send a signal.

  When the management server 40 receives the traffic history information from the controller 20 in step S701, the management server 40 stores the received traffic history information in the memory 43 in step S703. Then, the management server 40 determines the load state of each time zone of the controller 20 in step S705 based on the traffic history information stored in the memory 43.

  As described above, in the traffic management system 10 according to the present embodiment, the plurality of controllers 20, the management server 30 that can communicate with the plurality of controllers 20, and one or more relay servers 40 that can communicate with the management server 30. It has. The relay server 40 is assigned to one or more controllers 20 and is configured to be able to transmit at least information from the assigned controller 20 to the management server 30. In addition, the controller 20 is configured to be able to acquire passer-permitted data from the outside, and the recording medium is allowed to pass based on the unique information of the recording medium obtained by the corresponding wireless reader 12 and the passer-permitted data. The traffic history information corresponding to the recording medium is generated based on the determination result, and the traffic history information is transmitted to the relay server 30 or the management server 40. Furthermore, based on the traffic history information generated by the controller 20, a high load time zone in which the controller 20 is in a predetermined high load state and a low load time zone in which the controller 20 is in a predetermined low load state are determined. Based on the determination result, when the controller 20 is in the low load time zone, the traffic history information is transmitted to the relay server 30. When the controller 20 is in the high load time zone, the traffic history information is transmitted at least as high as possible. It stops until the load time zone elapses, and after the high load time zone elapses, it is transmitted to the management server 40 without going through the relay server 30.

  As a result, even if the number of controllers (authentication devices) managed by a single management server 40 increases, when the load on the controller 20 is relatively low, the assigned relay server 30 is used. Since the information from the controller 20 is transmitted to the management server 30, the concentration of the load on the management server 40 is reduced compared to the case where information is directly transmitted and received from each controller 20 to the management server 40. Smooth operation of the entire system can be achieved. Further, for example, when the controller 20 is in a high load time period (high load time period) such as a time period when the number of passersby increases and the number of authentication processes performed by the controller 20 increases, Since the transmission of the traffic history information is stopped at least until the high load time period elapses, the data traffic from the controller 20 can be suppressed even if the load of the controller 20 increases. For this reason, even if it is a time slot | zone (high load time slot | zone) when the controller 20 becomes a heavy load, it can reduce that a load concentrates on the management server 40, and can aim at the smooth operation of the whole system. Further, since the passage history information is transmitted to the management server 40 without passing through the relay server 30 after the high load time period has elapsed, the passage history information that has been stopped during the high load time period can be more quickly displayed. Thus, the traffic history can be reliably reflected on the management server 40 while minimizing the influence of the suspension of data transmission.

  Further, the degree of the number of traffic histories for each time zone in the entire plurality of controllers 20 and the degree of the number of traffic histories for each time zone in each of the plurality of controllers are calculated for each time zone divided by a predetermined time interval. Based on these, the high load time zone and the low load time zone of each controller 20 are determined. In this way, it is possible to determine whether each controller 20 is in a relatively high load time zone or a low load time zone based on the load status of the entire system, and an appropriate time zone in consideration of the entire system. Setting is possible.

  Further, the average value of the number of traffic histories per unit controller calculated for each time zone is calculated, and the high load time zone and low load of each controller 20 are calculated based on the average value and the number of traffic histories of each of the plurality of controllers. The time zone is determined. Thus, by calculating the “average value of the number of traffic histories per unit controller” for each time zone, it is possible to determine the average number of traffic histories for each controller 20 as viewed from the entire system. It can be grasped every time. Then, by determining the high load time zone and the low load time zone of each controller 20 based on the average value for each time zone obtained from the entire system in this way, each controller 20 is relatively in the high load time zone. It is possible to appropriately determine whether there is a low load time zone based on a more objective criterion.

  In addition, after the high load time period has elapsed, the traffic history information is sent to the management server 40 in a time period in which the degree of the traffic history number in the controller 20 is equal to or less than a predetermined value and closest to the high load time period. I am trying to send it. That is, after the high load time period has elapsed, when the load on the system becomes a relatively small time period, the transmission of the travel history information by the controller 20 is immediately resumed, so the time lag for reflecting the travel history information to the system Can be reflected in an appropriate time zone with a small load.

  In addition, one or a plurality of controllers 20 to be set in the high load time zone can be selected for each time zone divided by a predetermined time interval, and a predetermined number or more of the controllers 20 are high in any competing time zone. When satisfying the condition of the load time zone, based on a predetermined selection condition, a part is selected from a predetermined number or more of the controllers 20 satisfying the condition, and the high load time zone of the selected controller 20 is determined as the contention time. I try to remove it from the obi. By configuring in this way, even if a predetermined number or more of controllers in any time zone (contention time zone) satisfy the condition of the high load time zone, the contention time zone is set as the high load time zone. The number of controllers can be narrowed down. Therefore, it is possible to effectively prevent the high load time zones of a plurality of controllers from being concentrated on a specific time zone, and the high load time zones of the controllers can be set in a balanced manner.

  In addition, after the high load time zone of the controller 20 elapses, a plurality of traffic history information accumulated during the high load time zone is collectively transmitted to the management server 40. In this way, by transmitting a plurality of the traffic history information to the management server 40, the time lag for reflecting the traffic history information to the system can be further reduced, and smooth operation of the entire system can be achieved.

In addition, this invention is not limited to the said embodiment, You may actualize as follows, and even in that case, an effect | action and effect equivalent to the said embodiment are acquired.
(1) In the above embodiment, the case where the time zone determining means is provided in the management server 40 is illustrated, but it may be provided in the relay server 30.

(2) In the above embodiment, the high load time zone and the low load time zone are calculated from the average value of the number of traffic histories per unit controller calculated for each time zone and the number of traffic histories of each of the plurality of controllers. In the example, the number of traffic histories for each controller 20 is determined based on the degree of the number of traffic histories in each controller 20 and the level of the traffic histories for each controller 20. It may be determined based on the degree and a predetermined threshold. For example, it is possible to determine the high load time zone and the low load time zone by using the standard deviation as the degree of the number of traffic histories for each time zone calculated for each controller.

DESCRIPTION OF SYMBOLS 10 ... Traffic management system 12 ... Wireless reader 20 ... Controller 21 ... CPU (Judgment means, traffic history information generation means)
22 ... Communication part (history transmission means)
30: Relay server 32: Communication unit (information transmitting means)
40 ... management server 50 ... client server 41 ... CPU (time zone determination means, calculation means, average value calculation means)

Claims (7)

A traffic management system comprising a plurality of wireless readers capable of reading a recording medium on which unique information is recorded, wherein the wireless readers are respectively disposed at a plurality of entrances and exits through which passers-by can pass,
A plurality of controllers for processing each read result obtained by the plurality of wireless readers;
A management server capable of communicating with the plurality of controllers;
One or more relay servers capable of communicating with the management server;
With
The relay server is assigned to one or a plurality of the controllers, and includes at least information transmission means for transmitting information from the assigned controller to the management server,
The controller is
Whether or not the recording medium is permitted to pass based on the unique information of the recording medium obtained by the corresponding wireless reader and the permitted person data and configured to be able to acquire permitted person data from outside A determination means for determining whether or not,
Traffic history information generating means for generating traffic history information corresponding to the recording medium based on a determination result by the determination means;
History transmission means for transmitting the traffic history information to the relay server or the management server;
Have
Further, based on the traffic history information generated by the controller, a time zone determination for determining a high load time zone in which the controller is in a predetermined high load state and a low load time zone in which the controller is in a predetermined low load state Means are provided,
The history transmission means of the controller includes:
Based on the determination result by the time zone determining means, when the controller is in the low load time zone, the traffic history information is transmitted to the relay server,
When the controller is in the high load time zone, the transmission of the traffic history information is stopped until at least the high load time zone has elapsed, and the management is performed without going through the relay server after the high load time zone has elapsed. A traffic management system characterized by being transmitted to a server. The time zone determining means is
Based on the traffic history information from the plurality of controllers, the degree of the number of traffic histories in the plurality of controllers as a whole, and the traffic history for each of the plurality of controllers, for each time zone divided at predetermined time intervals. A calculating means for calculating the degree of the number of cases;
Based on the degree of the number of traffic histories for each time zone in the whole of the plurality of controllers and the degree of the number of traffic histories for each time zone in each of the plurality of controllers, calculated by the calculation means. The traffic management system according to claim 1, wherein the high load time zone and the low load time zone of each controller are determined. The calculating means includes an average value calculating means for calculating an average value of the number of traffic histories per unit controller in the plurality of controllers based on the traffic history information from the plurality of controllers, for each time zone,
Based on the average value of the number of traffic histories per unit controller calculated for each time zone by the average value calculation means and the number of traffic histories of each of the plurality of controllers, the high load of each controller The traffic management system according to claim 2, wherein a time zone and the low load time zone are determined. The time zone determining means is
Based on the traffic history information obtained from each of the plurality of controllers, comprising a calculation means for calculating the degree of the traffic history number for each time zone divided by a predetermined time interval for each controller,
Determining the high load time zone and the low load time zone of each controller based on the degree of the number of traffic histories for each time zone calculated by the controller by the calculating means and a predetermined threshold value; The traffic management system according to claim 1.   The history transmission means provided in the controller is the time zone in which the degree of the number of traffic histories in the controller is equal to or less than a predetermined value after the high load time zone elapses and is the highest in the high load time zone. The traffic management system according to any one of claims 2 to 4, wherein the traffic history information is transmitted to the management server in a near time zone.   The time zone determining means is capable of selecting one or more of the controllers to be set in the high load time zone for each of the time zones divided at the predetermined time interval, and in any competing time zone When a predetermined number or more of the controllers satisfy the conditions of the high load time period, a part is selected from the predetermined number or more of the controllers satisfying the condition based on a predetermined selection condition, and the selected The traffic management system according to any one of claims 2 to 5, wherein the high load time zone of the controller is excluded from the contention time zone.   The history transmission means provided in the controller transmits a plurality of the travel history information accumulated during the high load time period to the management server after the high load time period of the controller has elapsed. The traffic management system according to any one of claims 1 to 6, wherein the traffic management system is characterized.

Images