JP5684016B2 - Entrance / exit management control device and entrance / exit management system - Google Patents

Description

  The present invention relates to an entry / exit management system technique, and more particularly to a technique for storing system information (notification information).

  In the configuration example of the entrance / exit management system, a device such as a card reader (authentication device) installed at the entrance / exit of a room, a controller (entrance / exit management control device) that controls these devices, and a controller connected to the controller is managed. A system processing unit (SPU) that can be referred to by a person, and performs entry / exit management and control.

  Temporary information in data processing devices will be lost due to power interruption unless it is stored or held by some means, so there are many data processing devices that cannot be restored after power recovery. Information may be lost due to disruption.

  Especially in the controller of the entrance / exit management system, there is a possibility that the system information (notification information) may be lost due to the occurrence of power interruption.

  As means for measures against the power interruption, there are generally known techniques such as UPS (Uninterruptible Power Supply) (battery backup) and battery backup.

  Examples of the prior art relating to the above data processing apparatus and countermeasures against power interruption include JP-A-58-169218 (Patent Document 1), JP-A-2008-262350 (Patent Document 2), and the like.

  In Patent Document 1, the processing state of a program being processed is stored when a power interruption occurs, and the program is continuously executed when the power is restored (the program processing can be continued by a battery or the like even when a so-called power interruption occurs). In the apparatus, a means for detecting power-off, a plurality of stack areas for storing a program processing state at the time of power-off, and whether or not the processing program stored in the stack area is a power-off program that operates when the power is turned off. A means for identifying is provided, and the program processing state is sequentially stored in a plurality of stack areas when the power is turned off, and when the power is restored, the program processing state is read sequentially, until the program is no longer a power-off program. It describes the power-off recovery method that reads the program.

  In Patent Document 2, information in a temporary memory is stored in a nonvolatile memory for several hundred microseconds using an electrical signal generated immediately after the power is turned off as a key, and when the power is restored, the information is read from the nonvolatile memory, It describes information storage and recovery methods that restore the state before disconnection.

JP 58-169218 A JP 2008-262350 A

  When the well-known technique of the power interruption countermeasure / recovery method as in Patent Documents 1 and 2 is applied to the controller of the entrance / exit management system, there are the following problems.

  According to the technique of Patent Document 1, although information can be stored even in the event of a power failure, it is necessary to provide a sub power source separately from the main power source, such as means such as UPS and battery backup. As a result, there is a problem that the scale and cost of the device (controller) increase.

  According to the technique of Patent Document 2, there is no need for means such as UPS or battery backup, but it is necessary to save the data in the temporary memory within several hundred microseconds after detection of power-off. Therefore, when there is a large amount of stored data (for example, tens of thousands of pieces of notification information data in the entrance / exit management system), there is a problem that it becomes difficult to handle.

  Conventionally, in a controller or the like of an entry / exit management system, it is difficult to maintain system information (notification information) (especially long-term storage) as a countermeasure against power interruption as a countermeasure against power interruption. In the case of a configuration in which means is provided, there is a problem that the cost, scale, management burden, and the like increase.

  I want to maintain the system information (notification information) related to entrance / exit management / control in the controller of the entrance / exit management system. For example, when power is restored after a sudden power failure, the administrator can refer to and confirm if there is information stored in advance (for example, entry / exit history information). .

  In view of the above, the main object of the present invention relates to a controller of an entrance / exit management system, and (1) maintenance of system information (notification information) without providing a UPS or the like as a countermeasure against power interruption (especially long-term / massage) And (2) a technology capable of realizing a reduction in cost required for the maintenance (especially low cost even in the case of long-term and large-volume data maintenance).

  A typical embodiment of the present invention is a controller (entrance / exit management control device) or the like of an entrance / exit management system, and has the following configuration. The controller is connected to a notification destination device or the like.

  In the controller of the entry / exit management system of the present embodiment, a configuration for performing processing for transmitting notification information data from the controller to the notification destination device at any time and over time and storing it in the notification destination device during normal operation, and notification information data It has a configuration in which a nonvolatile storage device provided in the controller for storage and its processing are devised.

  As the above configuration, this controller has a notification control unit. The notification control unit implements a notification process associated with a normal operation control process. The notification control unit (notification process) includes a first nonvolatile storage unit, a first processing unit, a queue configured using the second nonvolatile storage unit, and a second processing unit. The queue has an area for an inlet portion and an outlet portion for a normal flow, and an area for a holding portion (holding queue) for a flow at the time of holding.

  When the communication state between the controller and the notification destination device is not good, the notification information data is appropriately stored using a holding unit (holding queue).

  When the notification information data from the control process for normal operation of the controller is stored in the first nonvolatile storage unit, the first processing unit converts the notification information data in the first nonvolatile storage unit to the second nonvolatile storage unit. The process of moving into the queue (entrance part or holding part) of the sex storage means is performed.

  The second processing unit performs processing for acquiring (moving) the notification information data in the queue (exit unit or holding unit) and transmitting it to the notification destination device.

  In the first form, the inlet and outlet of the queue and the holding unit are configured by a first type of nonvolatile storage device.

  In the second mode, the queue entrance and exit are configured by a first type of nonvolatile storage device, and the reservation unit is configured by a second type of nonvolatile storage device.

  In the relative relationship between the first type nonvolatile memory device and the second type nonvolatile memory device, the first type nonvolatile memory device is highly reliable and high speed, and the second type The nonvolatile memory device has a large capacity and is inexpensive.

  According to a typical embodiment of the present invention, it relates to a controller or the like of an entrance / exit management system, and (1) maintenance of system information (notification information) without providing means such as UPS as a countermeasure against power interruption (especially long-term / massage) Data conservation). (2) It is possible to reduce the cost required for the maintenance (especially low cost even in the case of long-term and large-volume data maintenance).

It is a figure which shows the whole structure of the entrance / exit management system of one embodiment of this invention. It is a figure which shows the flow of the 1st process of the controller of this Embodiment. It is a figure which shows the flow of the 2nd process of the controller of this Embodiment. It is a figure which shows the memory map of the non-volatile memory (MRAM) of the controller of this Embodiment. It is a figure which shows the structure of the sender queue etc. of the controller of this Embodiment, and corresponding memory structure (Embodiment 1, 2). It is a figure which shows the hardware and software structural example of the controller and SPU of this Embodiment.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. Note that components having the same function are denoted by the same reference symbols throughout the drawings for describing the embodiment, and the repetitive description thereof will be omitted.

<Summary>
In this entrance / exit management system (FIG. 1 and the like), the controller 1 does not include a UPS or the like as a measure against power interruption, has a notification process 200, and in particular, a sender queue 201 configured using an MRAM (207). , And processing of the event receiver 203 and the sender 208 using the sender queue 201 (first process and second process). During normal operation (normal power supply state), the control process 100 operates, and system information (notification information) is sent from the controller 1 to the external SPU 2 (notification destination) as needed by the notification process 200 over time. Transmitted and stored in DB5 of SPU2.

  Since the controller 1 does not have a UPS or the like, the operation is temporarily stopped when the power is cut off, such as a power failure. However, the notification information data is held in the nonvolatile memory of the controller 1, and the notification information is sent to the external SPU 2 in advance during normal operation. Is preserved. After power recovery from power failure, there is notification information that is preliminarily maintained in the external SPU 2 during the normal operation. For example, the administrator can refer to / confirm notification information (for example, entry / exit history information). Can be useful.

  The memory for the notification process 200 in the controller 1 includes a notification information memory 202 (which constitutes an event receiver queue), a sender queue memory 207 (which constitutes a sender queue 201), and a hold memory 206 (hold queue 209). Both form a FIFO queue. In particular, in the configuration of the first embodiment, the reserved memory 206 is configured by an MRAM as in the other memory portions. In particular, in the configuration of the second embodiment, the reserved memory 206 is configured by a CF (FIG. 5) unlike other memory portions.

  Normally, in a situation where the communication state between the controller 1 and the notification destination SPU2 is good, notification information data is transmitted from the sender queue 201 to the SPU2 promptly from the sender queue 201 and stored. In a situation where the communication state between the controller 1 and the notification destination SPU2 is poor, the notification information data cannot be transmitted from the sender 208 to the SPU2, but the notification information data is stored and held using the sender queue 201 and the hold queue 209. By using the hold queue 209, even relatively long-term data can be preserved. If the communication state between the controller 1 and the notification destination SPU2 is good, the stored and held notification information data is promptly transmitted to the SPU2 and stored.

[System configuration]
In FIG. 1, the whole structure of the entrance / exit management system of this Embodiment is shown. In this entrance / exit management system, an entrance / exit management control device (controller) 1, a system processing device (SPU) 2, a card reader (authentication device) 3, etc. are connected via a network 4.

  The entrance / exit management control device 1 is a controller of the entrance / exit management system. Various devices such as a card reader 3 and a sensor are connected to the controller 1. The controller 1 is connected to the SPU 2 that is a notification destination via a network 4 such as a LAN. The controller 1 has a configuration (specification) that does not include the above-described means such as UPS, and thereby has an effect such as low cost.

  The SPU 2 is a device that can be used by an administrator of the entrance / exit management system, and can make settings related to the control process 100 of the entrance / exit management system. The SPU 2 aggregates the notification information transmitted from the controller 1 and stores it in the database (DB) 5. The administrator can refer to the notification information stored in DB5 of SPU2. For example, the SPU 2 is configured by a server device, and the administrator can access the SPU 2 server from the terminal device via the network 4 to obtain notification information of the DB 5 and display the information on the screen of the terminal device for confirmation. .

  The controller 1 is configured to operate the control process 100 and the notification process 200. The control process 100 is a process related to entrance / exit management and control during normal operation (known technology). A part other than the control process 100 is a notification process 200 constituting the characteristic notification control unit. This notification process 200 operates together with the control process 100 during normal operation. The control process 100 and the notification process 200 are realized by program processing or circuit processing in the hardware / software configuration of the controller 1 described later (FIG. 6). Further, the controller 1 performs communication processing for transmitting notification information with the notification destination SPU2.

  The control process 100 includes a plurality of various processes such as a system manager, a device controller, a command server, an anti-passback controller, and an extended contact controller. Each process transmits a corresponding type of system information (notification information). For example, the device controller is a process for controlling and communicating with a device such as the card reader 3, and outputs entry / exit history information as an example of notification information. Information such as checksum is added to the notification information of each process in order to monitor and correct errors. The notification information data from the control process 100 is output (written) to the notification information memory 202 (a1).

  The notification process 200 includes elements such as a sender queue (notification information sender queue) 201, a notification information memory 202, an event receiver 203, and a sender (notification information sender) 208. The sender queue 201 is configured using a sender queue memory 207 and a holding memory 206. The sender queue memory 207 has an inlet (sender queue memory inlet) 204 and an outlet (sender queue memory outlet) 205. In addition, a hold queue 209 is configured using the hold memory 206 as necessary.

  The main process in the notification process 200 includes a process of the event receiver 203 (first process) and a process of the sender 208 (second process). These two processes operate independently (asynchronously). These two processes are performed using a non-volatile memory (MRAM) (202, 207) provided in the controller 1.

  The notification information memory 202 is a non-volatile memory such as an MRAM so that the notification information can be stored over time during normal operation. The subject of writing to the notification information memory 202 is the control process 100.

  The event receiver 203 reads (a2) the notification information data from the notification information memory 202. At this time, the normality of the notification information data can be confirmed by reading with the checksum for monitoring. In this case, the notification information is stored in the entrance 204 in the sender queue 201 (a3). As a result, the notification information data is moved from the notification information memory 202 to the entrance 204 (A). Basically, data is moved (copied and deleted), and an empty area is secured in the memory. In each movement (A, B, C), the data normality is confirmed by a checksum or the like as described above.

  Normally, the notification information written from the event receiver 203 is stored in the entrance 204 in the sender queue 201 (a3). On the other hand, the sender 208 monitors the update of the sender queue 201 (occurrence of notification information data), and when the notification information data is stored in the entrance unit 204, the data is moved from the entrance unit 204 to the exit unit 205. (A4) (B).

  As the entrance unit 204 and the exit unit 205 of the sender queue 201, a nonvolatile memory, for example, an MRAM is used so that notification information data can be stored with time during normal operation.

  The sender 208 reads out notification information data from the exit unit 205 (including checksum confirmation) (a5). And the process which transmits the said data to SPU2 of a notification destination with reference to the said notification information data is performed (a6). After confirming the successful transmission (OK) of the notification information data, the notification information data in the exit unit 205 is deleted. As a result, the notification information moves from the exit 205 of the sender queue 201 to the DB 5 in the SPU 2 (C).

  When the transmission of the notification information data fails (NG), the sender 208 holds the notification information data in the exit unit 205 without deleting it, and performs retransmission processing later.

  Communication for transmitting notification information data between the sender 208 of the controller 1 and the SPU 2 is performed by a predetermined protocol corresponding to the network 4 or the like, for example, TCP / IP. With regard to this communication, the sender 208 has a processing function for monitoring and determining a communication state in communication with the notification destination SPU2. The sender 208 obtains notification information data from the sender queue 201 (exit unit 205) (a5) while checking the communication state with the SPU 2 (communication enabled (OK) / communication disabled (NG)), and the notification information data The transmission to SPU2 (a6) is appropriately controlled.

  Here, the process (a1) of storing the notification information data from the control process 100 to the notification information memory 202, and the notification information from the notification information memory 202 in the sender queue 201 (entrance unit 204) by the first process of the event receiver 203 Data movement processing (A) and notification information data movement / acquisition from the sender queue 201 (entrance unit 204, exit unit 205) and transmission to SPU2 (B, C) by the second processing of the sender 208 Each process is performed independently.

  If the communication state between the sender 208 of the controller 1 and the SPU 2 is good (“OK” “communication allowed”), the notification information generated from the control process 100 does not stay in the queue and promptly. It can be sent to SPU2 for storage. However, in the communication between the sender 208 and the SPU 2, if the communication state is bad (“NG” or “communication impossible”) due to a failure of the network 4 or the convenience of the SPU 2 side, the error occurs from the control process 100. The incoming notification information cannot be efficiently transmitted to the SPU 2, and the notification information stays in the controller 1 (queue).

  Therefore, in this embodiment, as a mechanism that can appropriately cope with the retention of the notification information during the communication NG, the configuration includes a hold memory 206 in the sender queue 201 and a process using the hold queue 209. Thus, the notification information data is held (stored) in the hold queue 209 until the communication state is improved.

  At the time of communication OK, the notification information data is moved / transmitted in the normal flow from the entrance 204 to the exit 205 of the sender queue 201 (without using the hold queue 209). On the other hand, at the time of communication NG, the notification information data is held using the hold queue 209 in the middle of the flow of the entrance part 204 to the exit part 205 of the normal sender queue 201. When the communication NG is in a communication OK state, the notification information data is automatically extracted from the hold queue 209 and transmitted to the SPU 2.

  For example, if there is no room for storing the notification information data in the entrance 204 of the sender queue 201, the event receiver 203 creates the hold queue 209 and stores (moves) the notification information data in the hold queue 209 (a7). . A hold queue 209 is additionally created and secured in the hold memory 206 as appropriate according to the amount of notification information data generated. The hold queue 209 is, for example, a data image file in the processing queue of the entrance unit 204.

  The holding of the notification information data requires a larger capacity as the NG state becomes longer (for example, it is assumed that the number of cases exceeds tens of thousands). For this purpose, a configuration using a CF instead of an MRAM as the holding memory 206 ( By adopting the second embodiment, long-term (large amount) maintenance of the notification information data can be realized at low cost.

  When the communication state is good (OK), if there is the notification information data stored in the hold queue 209, the sender 208 sequentially moves to the exit unit 205 of the sender queue 201 (a8), and from the exit unit 205 to the SPU2 The notification information data is transmitted.

  Various known techniques may be applied for monitoring and determining the communication state. In the present embodiment, based on a predetermined protocol (TCP / IP or the like), the sender 208 of the controller 1 determines the communication state by looking at the response from the SPU 2 to the notification information data transmission. For example, when the sender 208 transmits notification information data (for example, one or a unit of a predetermined number) to the SPU 2 and a response indicating normal reception of the data is returned from the SPU 2, it is determined that the communication is possible (OK). The next notification information data unit can be transmitted. If a response indicating normal reception or the like is not returned, it is determined that transmission of the notification information data has failed and communication is impossible (NG). The notification information data is held in the sender queue 201 and is retransmitted later.

[Controller processing]
A processing flow example of the controller 1 will be described with reference to FIGS. 2 is mainly processing by the event receiver 203, and FIG. 3 is mainly processing by the sender 208. The processing algorithms in FIGS. 2 and 3 are in a correspondence relationship. S represents a processing step. Hereinafter, the processing flow of FIFO in units of one (one) notification information data will be described, but a plurality of notification information may be processed in the same manner. A plurality of pieces of notification information may be combined into one unit and processed in the same manner.

[First processing]
(S101) The notification process 200 receives notification information data from the control process 100 (each of a plurality of processes).

  (S102) The notification process 200 stores the received notification information data in the notification information memory 202.

  In the present embodiment, the control process 100 (a plurality of processes) stores the notification information data in the notification information memory 202 in S101 and S102. Then, using this as an opportunity, the event receiver 203 is configured to process the notification information data stored in the notification information memory 202 as in S103 and subsequent steps.

  (S103) The event receiver 203 determines whether or not the amount of notification information data stored in the entrance 204 of the sender queue 201 is greater than or equal to a predetermined value (X). When it is less than X (N), the process proceeds to S104, and when it is equal to or greater than X (Y), the process proceeds to S106.

  (S104) The event receiver 203 copies the notification information data in the notification information memory 202 to the entrance unit 204.

  (S105) The event receiver 203 deletes the notification information data in the notification information memory 202 and terminates (repeating similarly from the beginning).

  (S106) The event receiver 203 uses the hold memory 206 to create a hold queue 209 for holding (storing) notification information data. In this processing example, the hold queue 209 is added one file at a time in accordance with the notification information data amount (for example, for each size of the predetermined value (X) of the area of the entrance unit 204).

  (S107) The event receiver 203 moves the notification information data in the area of the entrance section 204 to the holding queue 209, and copies the notification information data in the notification information memory 202 to the area of the entrance section 204 that is vacated by the movement.

  (S108) The event receiver 203 deletes the notification information data in the notification information memory 202, and ends.

  In FIG. 2, as an example of FIFO processing, the notification information data of the entrance unit 204 is moved (saved) to the hold queue 209, and the next notification information data is stored in the area of the entrance unit 204 that is vacated thereby. .

[Second processing]
(S201) The sender 208 determines the communication state, such as whether communication with the notification-destination SPU2 is possible (OK) or not (NG). If communication is possible (OK) (Y), the process proceeds to S202, and if communication is not possible (NG), (N) is ended (repeated similarly from the beginning).

  (S202) The sender 208 determines whether or not there is notification information data in the exit unit 205 of the sender queue 201. If there is (Y), the process proceeds to S209, and if not (N), the process proceeds to S203.

  (S203) The sender 208 determines whether or not the holding queue 209 exists. If there is (Y), the process proceeds to S207, and if not (N), the process proceeds to S204.

  (S204) The sender 208 determines whether or not the notification information data exists in the entrance unit 204. If yes (Y), the process proceeds to S205, and if not (N), the process ends.

  (S205) The sender 208 copies the notification information data of the entrance unit 204 to the exit unit 205.

  (S206) The sender 208 deletes the notification information data of the entrance unit 204, and proceeds to S209.

  (S207) The sender 208 copies the notification information data in the hold queue 209 to the exit unit 205. Note that the order is from the previously created hold queue 209 (file).

  (S208) The sender 208 deletes the notification information data in the hold queue 209, and proceeds to S209. If all data in one hold queue 209 (file) disappears due to the deletion, the hold queue 209 (file) itself is deleted (files are decreased one by one).

  (S209) The sender 208 transmits the notification information data of the exit unit 205 of the sender queue 201 to the notification destination SPU 2 via the network 4.

(S210) The sender 208 determines whether the result of the transmission processing of the notification information data is success (OK) or not (NG) based on a response from the SPU2. When the result is NG (N), the notification information data is retransmitted as described above (return to S209). *
(S211) When the result is OK (Y), the sender 208 deletes the notification information data of the exit unit 205 and ends (repeats from the beginning).

  In FIG. 3, as an example of FIFO processing, the flow is that the data is moved and transmitted by checking the presence / absence of notification information data in the priority order of the exit unit 205, the hold queue 209, and the entrance unit 204.

[Memory map]
FIG. 4 shows a memory map of a single MRAM provided in the controller 1. A0 and the like indicate addresses. Reference numeral 401 denotes an event receiver queue area (corresponding to 501 in FIG. 5). The notification information memory 202 constitutes an event receiver queue (queue related to processing of the event receiver 203). Reference numeral 402 denotes a sender queue entrance area (corresponding to 502 in FIG. 5). Reference numeral 403 denotes a sender queue exit area (corresponding to 503 in FIG. 5). These areas may store not only the notification information data but also header information including a checksum.

[System Information (Notification Information)]
“System information (notification information)” to be stored / maintained in the present embodiment refers to entry / exit history information and control / control information on the status of each device (card reader 3 etc.) by the control process 100. Information in a predetermined format according to the entrance / exit management system. For example, in this entrance / exit management system, when the user passes the card over the card reader 3 and succeeds in authentication and passes through a door or the like, one or more (for example, several) pieces of notification information data are generated.

[Sender queue and memory configuration]
A characteristic queue and memory configuration in this system will be described with reference to FIG. This corresponds to the configuration shown in FIGS. Since the sender queue 201 (including the hold queue 209) has a queue structure, data (notification information) is processed by the FIFO.

  In the present embodiment (Embodiments 1 and 2), an MRAM (Magnetroresistive RAM) (magnetoresistive memory) is employed as an example of a nonvolatile memory (NVM) provided in the controller 1. In the second embodiment, CF (Compact Flash) is adopted together with MRAM. In FIG. 5, the normal first NVM = MRAM and the holding second NVM = MRAM or CF.

  Further, as the notification process 200 of the controller 1, a nonvolatile storage for temporarily storing notification information to be transmitted in each of the processing of the event receiver 203 (first processing) and the processing of the sender 208 (second processing). The device or its memory area is used, but the first area (401, 501) of the MRAM is used as the notification information memory 202, and the second area (402, 502) of the MRAM is used as the sender queue 201 (204, 205). Three regions (403, 503) are used. An MRAM notification information memory area 501 is an area corresponding to 401. An MRAM entrance area 502 is an area corresponding to 402. An MRAM exit area 503 is an area corresponding to 403.

  In the present embodiment, the notification information memory 202 and the sender queue 201 are configured as one integral MRAM. These can also be configured separately by another nonvolatile memory device.

  As a relative relationship such as characteristics between the first NVM for normal use and the second NVM for normal use, the first NVM for normal use has advantages such as high reliability and high speed, and the second NVM for normal use has a large capacity, low cost, etc. Have advantages. In terms of cost, MRAM is relatively expensive and CF is relatively inexpensive (inexpensive). In terms of capacity, CF has a large capacity and is inexpensive even when used in large numbers. MRAM is costly depending on capacity. In addition, the MRAM has no limit on the number of rewrites, has high durability, maintains the notification information data (high reliability), and has high speed read / write access.

  Therefore, in this embodiment (Embodiments 1 and 2), the MRAM is used in the notification information memory 202 and the entrance unit 204 and the exit unit 205 of the sender queue 201. It is possible to shorten the access for writing and reading the notification information data to the queue, and the efficiency becomes high.

  In the first embodiment, the sender queue 201 is configured with only MRAM. The holding memory 206 (holding second NVM) itself is assumed to be absent. Further, for example, a reserved memory 206 using an MRAM area may be provided, but in that case, a relatively small capacity is used. The first embodiment has a simple configuration because it is not necessary to provide a holding CF and its processing function. This is useful in an environment where the communication state between the controller 1 and the SPU 2 is kept good.

  In the second embodiment, the configuration of the sender queue 201 is a combination of two types of storage devices of MRAM + CF. As the capacities of the entrance part 204 and the exit part 205 of the sender queue 201, since the MRAM is used, it is suppressed to a relatively small capacity. A CF is used as the holding memory 206 (holding queue 209) taking advantage of large capacity and low cost. A plurality of CFs may be used. In the second embodiment, the advantages of MRAM and CF are combined in a balanced manner. This achieves both high reliability and low cost.

  Needless to say, the present invention is not limited to MRAM and CF, and other types of storage devices that satisfy the above characteristics and relationships can be applied. For example, an HDD or the like may be used instead of the CF.

  In FIG. 1 (and FIG. 2 and FIG. 3), as a basic form, the notification information data is temporarily moved (a2, a3) from the notification information memory 202 to the entrance unit 204. The flow of moving the data to the hold queue 209 (a7) is shown. Further, there is shown a flow in which when there is pending data, the notification information data is temporarily moved from the holding queue 209 to the exit unit 205 (a8), taken out from the exit unit 205, and transmitted (a5, a6). On the other hand, on the basis of the above form, as shown in FIG. 5, in the case of a hold, a form in which data is moved directly from the notification information memory 202 (501) to the hold queue 209 without going through the entry part 204 (502) (exit part) The same may be applied to the 205 side. However, it is necessary to process in consideration of the FIFO order of the notification information data.

[Setting the number of managed items and memory capacity]
Regarding S103, the predetermined value (X) is management information that can be variably set for the controller 1 (notification process 200) of the present system, for example. The setting can be performed from the SPU 2 to the controller 1 based on an administrator operation, for example, as in the case of the normal operation setting. The predetermined value (X) is set as the maximum number (the number of management cases), for example, in units of the number of notification information (or data amount conversion). Note that one item is one piece of notification information data, which is, for example, an average of about 50 bytes / one item depending on the system. The predetermined value (X) is set in consideration of the number of cases and the amount of data that can be maintained. At the same time, the capacity of each memory such as MRAM and CF provided in the controller 1 is set. For example, when a large amount (and long-term) of notification information such as a maximum of tens of thousands is assumed to be maintained, a corresponding value is set.

  In a normal environment, the communication state between the controller 1 and the SPU 2 is kept good, i.e., there is little or no hold, and the MRAM capacity may be relatively small.

[Example of configuration]
FIG. 6 shows a hardware / software implementation configuration example of the controller 1 and the SPU 2 (in the case of the second embodiment). The controller 1 includes a processor 401, a memory 402, a storage device 403, an input device 404, an output device 405, a communication I / F device 406, an MRAM & I / F unit 421, and a CF & I / F unit 422. The control program 411 implements the control process 100. The notification control program 412 implements the notification process 200. Each process (100, 200) is realized by the processor 401 loading the program (411, 412) into the memory 402 and executing it. The MRAM & I / F unit 421 includes an MRAM and an interface processing unit for reading and writing data with respect to the MRAM. The CF & I / F unit 422 includes a CF and an interface processing unit for reading and writing data with respect to the CF.

  The SPU 2 includes a processor 501, a memory 502, a storage device 503, an input device 504, an output device 505, and a communication I / F device 506. When the processor 501 loads the program (511) to the memory 502 and executes it, the control processing of the SPU 2 (the setting for the controller 1 and the processing for storing the notification information data received from the controller 1 in the DB 5 and the notification information data on the screen) Display processing).

[Effects]
As described above, the entry / exit management system (controller 1) of the present embodiment (1) maintenance of system information (notification information) (especially long-term, large-volume data) without providing means such as UPS as a countermeasure against power interruption. Maintenance). (2) It is possible to reduce the cost required for the maintenance (especially low cost even in the case of long-term and large-volume data maintenance).

  In this system, the notification information data is stored over time in the nonvolatile memory inside the controller 1 during normal operation, and the notification information data is transmitted to the external SPU 2 and stored centrally in the DB 5 and maintained. Therefore, the administrator can refer to and check the notification information (for example, entry / exit history information) of the DB 5 of the SPU 2 on the screen at any time. Therefore, it is effective for system management and continuous operation of the entrance / exit management system.

  When the notification information is transmitted from the controller 1 to the SPU 2 and stored, the notification information data can be held (suspended) in the nonvolatile memory in the controller 1 even when the communication state is bad, and if the communication state is improved, The transmission of the held data can be started, and the data can be maintained externally.

  In the prior art system, for example, notification information is stored as a file in the controller. On the other hand, in the present embodiment, notification information is transmitted from the controller 1 to the external SPU 2 and accumulated in the DB 5 in the SPU 2. The system of the prior art example includes a controller having a UPS or the like, a controller without a UPS, or the like. However, according to the present embodiment, one type of controller 1 (not having a UPS or the like is configured to have a notification process 200). Prepared).

  As mentioned above, the invention made by the present inventor has been specifically described based on the embodiment. However, the present invention is not limited to the embodiment, and various modifications can be made without departing from the scope of the invention. Needless to say.

  The present invention can be used for an entrance / exit management system and the like.

  DESCRIPTION OF SYMBOLS 1 ... Entrance / exit management control apparatus (controller), 2 ... SPU (system processing apparatus / notification destination apparatus), 3 ... Card reader (authentication apparatus), 4 ... Network, 5 ... DB, 100 ... Control process, 200 ... Notification process (Notification control unit), 201 ... sender queue (notification information sender queue), 202 ... notification information memory, 203 ... event receiver, 204 ... input unit, 205 ... output unit, 206 ... hold memory, 207 ... sender queue memory, 208 ... sender (Notification information sender), 209...

Claims (3)

An entrance / exit management control device constituting an entrance / exit management system,
No means of UPS or battery backup,
A notification control unit that executes a control process for transmitting and storing notification information from the control process to an external notification destination device during normal operation;
The notification control unit
During the normal operation, the notification information data from the control process is stored in the first nonvolatile storage means over time, and the notification information data stored in the first nonvolatile storage means is stored in the second nonvolatile storage. A first processing unit for performing a first process of moving to an inlet in a queue having an inlet and an outlet in a FIFO using storage means;
During the normal operation, the notification information data is moved from the entrance to the exit in the queue, and the notification information data stored in the exit in the queue is acquired and transmitted to the notification destination device. A second processing unit that performs second processing to be stored in the notification destination device,
The notification information data is processed and held at high speed and with high reliability by using a high-reliability and high-speed storage device as the non-volatile storage means constituting the queue. Entrance / exit management controller. In the entrance / exit management control apparatus of Claim 1,
When the first processing unit moves the notification information data, if the amount of notification information data stored in the entry area in the queue is greater than or equal to a predetermined value, the first processing unit uses a non-volatile storage unit. Create a queue, move the notification information data to an area in the pending queue,
When there is notification information data stored in an area in the holding queue, the second processing unit moves the acquisition information data to an exit area in the queue and acquires the notification information data to the notification destination device. Send and store in the notification destination device,
As the nonvolatile storage means constituting the queue, the first storage device having a characteristic higher in reliability and speed than the nonvolatile storage means constituting the hold queue is used, and the nonvolatile storage constituting the hold queue As a means, processing and holding the notification information data at a large capacity and at a low cost by using a second storage device having a large capacity and cheaper characteristics than the nonvolatile storage means constituting the queue,
With the above configuration, while the communication state with the notification destination device is not good, the notification information data is held using the queue and the hold queue, and while the communication state with the notification destination device is good, the queue and The entry / exit management control device, wherein the notification information data is transmitted from the hold queue to the notification destination device. The entrance / exit management control device according to claim 1;
An entry / exit management system configured to include a notification destination device connected to the entrance / exit management control device via a network and operable by an administrator;
Notification information data transmitted from the entrance / exit management control device during the normal operation is stored in a centralized database in the notification destination device,
The entry / exit management system characterized in that the notification destination device displays the notification information data of the database on a screen for reference based on the operation of the administrator.

Images