JP2011048458A - Server device and security management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prevent that other processing cannot be performed because a server device collecting and integrating histories updates a history database, in a security management system. <P>SOLUTION: A server device suspends the update of the history database when an accumulation flag indicating that transmission has failed is attached to a history when receiving the history from a security management device. When continuously receiving a prescribed number of histories each not attached with the accumulation flag or when a prescribed time lapses without receiving the history, the server device resumes the update of the history database. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a security management system for managing entry / exit of a user.

  Conventionally, there is a security management system that manages the entry / exit of a user into a security management area such as a room or a building. The security management system performs the authentication based on the authentication information read from the authentication medium held by the user on the lock and unlocking of the electric lock provided on the door of the room, and controls the security management device and the security management device. And a server device that manages history information indicating events related to authentication and locking / unlocking of electric locks. The security management system may include a plurality of security management devices. In this case, the server device manages history information of each security management device. The server device manages each history in a database so that the operator of the security management system can easily view the history information (hereinafter, the database managed by the server device is referred to as a history database).

  Each time an event occurs, the security management device transmits a history indicating the event to the server device. When the history rises, the server device performs processing for adding the history to the history database. The history that the security management device gives to the server device is coded. When updating the history database, the server device manages the security history so that the operator can see and understand the coded history. A process of converting into character string information indicating which user has authenticated at which door managed by the apparatus is performed.

In addition to the history database update processing, the server device also manages processing to manage status information as to whether each security management device is normal, and if a history is received, a response signal indicating that the history has been received Processing such as transmission to the management device is also performed.
Patent Document 1 discloses an entrance / exit management system as an example of a security management system.

No. 2000-003492

  By the way, depending on the scale of the security management system, the history managed by the server device may reach several hundred thousand orders, and a new history history depending on the number of users and the number of security management devices. Adding to the database can take more time. In particular, communication between the security management device and the server device may be interrupted, which may cause a state in which the security management device cannot raise a history. The problem that it takes time to add is prominent.

  When communication is interrupted, the security management apparatus stores the history, and when communication is recovered later, the accumulated history is collected and transmitted to the server apparatus. Then, it takes more time because the history conversion and additional processing corresponding to the accumulated amount occur. When the processing performance of the processor of the server device is not so high, when the history database is updated, most of the processing performance is spent for updating the database.

  Then, processing other than the above-described history database update processing cannot be performed. For example, the response signal indicating that the update of the state information indicating the operation state of the security management device managed by the server device is delayed or the history is received. The transmission will be delayed. For this reason, even if some kind of error has occurred in the security management device, there is a possibility that notification of the error to the operator will be delayed.

  An object of the present invention is to provide a security management system that does not cause delay as described above, and to provide a server device that manages history in the security management system.

  In order to solve the above-described problem, a server device according to the present invention is a server device that manages a history of entry / exit of a user to / from a security management area, and manages entry / exit of the user to / from the security management area A history receiving means for receiving the history transmitted from the security management apparatus, a response means for transmitting a response signal indicating that the history has been received to the security management apparatus that has transmitted the history, and the history managed by the database system A history database, a storage means for storing the history received by the history receiving means, and a history database that is periodically stored in the storage means and not registered in the history database in a format for the history database. Database update means to be added to the new history received by the history receiving means Interruption means for interrupting addition of the history to the history database by the database update means when a history flag has been added that indicates that the history has been transmitted from the security device before and has not reached its own server device; It is characterized by providing.

  The security management system according to the present invention includes a security management device that manages entry / exit of a user to / from a security management area, and a server device that manages a history of the entry / exit in the security management device. The server device includes a history receiving means for receiving a history transmitted from the security management device for managing entry / exit of a user to / from the security management area, and a security management for transmitting the history Response means for transmitting a response signal indicating that the history has been received to the apparatus, history database for managing the history by a database system, storage means for storing the history received by the history receiving means, and periodically storing the history The history stored in the means and not registered in the history database Database update means for adding to the history database in a history database format, and a new history received by the history receiving means, that the history was previously transmitted from the security device and did not reach its own server device Interruption means for interrupting the addition of the history to the history database by the database updating means when the accumulation flag is added, and the security management device is configured to enter the security management area of the user. Entry / exit management means for managing withdrawal based on authentication information including an identifier acquired from an authentication medium held by the user, and a history of entry / exit of the user into the security management area, the server device History storage means for storing together with the accumulation flag determined based on success or failure in transmission to History transmitting means for transmitting a history stored in a history storage unit and not yet transmitted to the server device to the server device with the accumulation flag when the transmission flag indicates that the transmission has failed. It is characterized by comprising.

  The addition of the accumulation flag here may be in a state in which the server device can recognize that the flag is added, for example, indicates that a new history received by the server device has previously failed to be transmitted. It may be configured to include information indicating that it is a history, or is added because data at a data position defined as an accumulation flag in the history is predetermined information. It is good as well.

  With the configuration as described above, even if the server device receives the history, the history database is not regularly updated if the history flag is attached to the history device. Since the processor of the server device uses most of the processing performance for the update processing of the history database, this processor must execute a response signal that is a process other than the history database update, It is possible to avoid a situation in which processing such as information update cannot be executed.

Further, in the server device according to the present invention, the interrupting unit has the history receiving unit continuously added a predetermined number of the accumulation flags after interrupting the periodic confirmation of the database updating unit. The interruption may be canceled when no history is received.
Alternatively, the interruption unit may cancel the interruption when the history reception unit has not received a history for a predetermined time after the periodic confirmation of the database update unit is interrupted.

As a result, even if the periodic update process of the history database is interrupted, the update process of the history database can be resumed under the above-mentioned conditions. Can be prevented.
In the server device according to the present invention, the history transmitted from the security management device to the server device includes a status flag indicating the status of the security management device, and the server device is configured so that the security management device operates normally. It is good also as providing the status management means which manages the status information which shows whether it is, and the update means which updates the said status information based on the said history flag.

As a result, the server apparatus performs the update process of the state information independently of the update process of the history database, and the history database update process is interrupted when the history with the accumulation flag is received. Therefore, even if many histories are continuously received, the status information of the security management device can be updated and managed almost in real time.
Further, in the security management system according to the present invention, the history storage means sets the accumulation flag as a history of no response when a response to the history transmitted by the history transmission means is not obtained from the response means. It is good also as memorize | storing.

Thus, the security management apparatus can appropriately attach a history accumulation flag depending on whether or not a response signal has been received.
In the security management system according to the present invention, when the history storage unit succeeds in transmitting the history with the accumulation flag, the history storage unit updates the history without setting the accumulation flag. It is good as well.

  As a result, when the transmission of the history with the accumulation flag succeeded, the double transmission of the same history can be prevented by setting the state without the accumulation flag.

FIG. 1 is a system configuration diagram illustrating a system configuration example of a security management system. FIG. 2 is a functional block diagram showing a functional configuration of the security management apparatus. FIG. 3 is a functional block diagram illustrating a functional configuration of the server apparatus. FIG. 4 is a conceptual diagram showing a data structure of a history managed by the security management apparatus and transmitted to the server apparatus. FIG. 5 is a data conceptual diagram showing a data configuration example of authentication information stored in the security management device and the server device. FIG. 6 is a data conceptual diagram of a GU code table 352 showing codes indicating the respective security management apparatuses and information associated with the codes. FIG. 7 is a data conceptual diagram of a device code table 353 showing codes indicating card readers and electric locks managed and controlled by each security management apparatus, and information associated therewith. FIG. 8 is a data conceptual diagram showing a data configuration example of a code indicating various events that can occur in the security management apparatus and an event code table 354 indicating the contents thereof. FIG. 9 is a data conceptual diagram showing a data configuration example of the history database. FIG. 10 is a flowchart showing the operation of the security management apparatus. FIG. 11 is a flowchart illustrating the operation of the analysis unit of the server device. FIG. 12 is a flowchart showing the operation of the storage unit of the server device.

<Embodiment>
<Configuration>
Hereinafter, a security management system according to an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a diagram showing a system configuration of a security management system.

As shown in FIG. 1, the security management system includes security management devices 200 a, 200 b, 200 c and a server device 300. Each security management device is connected to the server device 300 via the network 160.
The security management device 200a manages entry / exit of users (hereinafter referred to as users) to / from the area A and the area B, and a history generated when the user enters / exits the area A or area B. Is transmitted to the server apparatus 300.

  The security management device 200a manages a card reader (CR (abbreviation of Card Reader) in FIG. 1) 110a, a card reader 120a, Card reader connected to the electric lock 130a provided in the door 140a provided in the card, the card reader 110b, the card reader 120b, and the electric lock 130b provided in the door 140b provided in the area B. Manages and controls the status of each device such as a lock or electric lock.

The security management device 200b manages entry / exit of users to / from area C and area D, and the security management device 200c manages entry / exit of users to / from area E.
Similarly to the security management device 200a, the security management device 200b and the security management device 200c are provided in each of the devices under their control, that is, in the case of the security management device 200b, the card reader 110c, the card reader 120c, and the area C. If the security management device 200c is used for each device of the electric lock 130c, the card reader 110d, the card reader 120d, and the electric lock 130d provided in the door 140d provided in the area D, a card is provided. The state of each device of the reader 110e, the card reader 120e, and the electric lock 130e provided in the door 140e provided in the area E is managed and controlled, and the history is transmitted to the server device 300.

  Each user of the security management system has the IC card 150 shown in FIG. Each IC card 150 holds a unique ID (Identifier) so as to be distinguished from other IC cards. When the IC card 150 is held over the card reader, the held card reader reads the ID held in the IC card 150 and transmits the read ID to the connected security management apparatus. If the transmitted ID is registered in the authentication information held by the security management device, the card reader that transmitted the ID unlocks the electric lock of the corresponding door. If the ID is not registered, it is not unlocked as an authentication failure.

  Each time such an event such as authentication processing occurs, a history is generated. There are various types of history, such as successful authentication, unlocking, door opening, door closing, locking, etc., and error reporting. The error report includes, for example, an abnormality of the electric lock (for example, the electric lock sensor does not detect the lock state even though there is a lock instruction from the security management device).

The security management devices 200a to 200e and the server device 300 according to the security management system will be described in more detail.
FIG. 2 is a functional block diagram showing a functional configuration of the security management apparatus. Since the functional configurations of the security management devices 200a to 200c are common, the security management device 200 will be described here with the alphabet after the security management device 200 removed. The same applies to the card readers 100a to 100e and the electric locks 130a to 130e.

As shown in FIG. 2, the security management device 200 includes an I / F (InterFace) unit 210, an authentication unit 220, a history generation unit 230, an external communication unit 240, and a storage unit 250.
The I / F unit 210 is connected to the card readers 110 and 120, the electric lock 130, and an opening / closing sensor (not shown) provided on the door. The I / F unit 210 has a function of performing communication with these devices in accordance with, for example, the RS232C communication standard.

  Specifically, when the card reader 110 or the card reader 120 receives an ID read by the card reader from the IC card 150, the I / F unit 210 transmits the ID to the authentication unit 220. When a signal indicating authentication success is received from the authentication unit 220 in accordance with the ID, the card reader that reads the ID is instructed to unlock the electric lock 130 and receives a signal indicating authentication failure. Is notified of authentication failure.

In addition, the I / F unit 120 is configured to notify that each device has an abnormality when there is an abnormality in each device from the electric lock 130 or the card reader 110, 120. When received, the history generation unit 230 is notified of the content of the abnormality.
The authentication unit 220 has a function of executing authentication of an ID read by a card reader. Specifically, when the authentication unit 220 receives an ID from the I / F unit 210, the authentication unit 220 searches whether the ID is registered in the authentication information 252. If the ID is registered in the authentication information 252, the authentication success is transmitted to the I / F unit 210, and the ID and the authentication success information are associated with each other and transmitted to the history generation unit 230. If the ID is not registered in the authentication information 252, the authentication failure is transmitted to the I / F unit 210, and the ID and the authentication failure information are associated with each other and transmitted to the history generation unit 230.

  The history generation unit 230 generates a history from the information indicating the abnormality of each device transmitted from the I / F unit 210, the authentication success / failure information transmitted from the authentication unit 220, and the ID information. And has a function of transmitting to the external communication unit 240. The history generation unit 230 has an accumulation flag “0”, information on the date and time when an event occurred in each device, a GU code set in advance in the own device, a code of the device in which the event occurred, and an event that has occurred When an ID is transmitted from the authentication unit 220, a history with the ID as a user ID is generated. The event code is based on the event code and the status flag indicating whether the security management device is operating normally. . Details of the accumulation flag and the contents of each code will be described later.

The external communication unit 240 has a function of performing communication with the server apparatus 300 via the network 160 in accordance with, for example, the Ethernet (registered trademark) standard.
Specifically, the external communication unit 240 has a function of transmitting the history transmitted from the history generation unit 230 to the server device 300. When a response signal indicating that a history has been received from the server apparatus 300 is received with respect to the transmitted history, the history accumulation flag remains “0” and is registered in the history information 251. In addition, when a response signal indicating that a history has been received from the server apparatus 300 is not received within a predetermined time with respect to the transmitted history, the history accumulation flag is set to “1”, and history information together with the transmitted history is recorded. 251 is registered.

  Also, the external communication unit 240 determines whether communication with the security management device 200 periodically transmitted from the server device 300 is valid, and whether the security management device 200 is operating normally. When the server apparatus 300 receives a survival confirmation signal for confirming whether or not, a survival response signal is generated and transmitted to the server apparatus 300. At this time, the history information 251 is confirmed, and if there is a history whose accumulation flag is “1” in the history information 251, the history is transmitted to the server apparatus 300. Then, when a response signal is received from the server apparatus 300 for the transmission of the history whose accumulation flag is “1”, the history accumulation flag is changed from “1” to “0”.

The storage unit 250 includes a hard disk device, a memory, and the like, and has a function of storing various programs and data necessary for the security management device 200 to operate. The storage unit 250 particularly stores history information 251 and authentication information 252.
The history information 251 is information obtained by collecting the history information generated in the history generation unit 230, and is stored in a code state. One history includes at least a management number for managing the history, an accumulation flag indicating whether or not the history has already been transmitted, a date and time code indicating the date and time when the history was generated, and a history event. In addition to the event code shown in the example, in addition to the history, for example, if the event code is a history indicating that the authentication has been performed, the authentication ID, the code indicating the card reader that has performed the authentication, and the like are included. Further, for example, if the event code of the history indicates an abnormality of the device, the code indicating the device is included.

The authentication information 252 is information that is referred to when the authentication unit 220 executes authentication, and is information indicating a correspondence between a user ID permitted to enter an area and an area where each user ID can enter. is there. Details thereof will be described later.
Next, the server apparatus 300 will be described with reference to FIG. FIG. 3 is a functional block diagram illustrating a functional configuration of the server apparatus 300.

As illustrated in FIG. 3, the server device 300 includes a communication unit 310, an analysis unit 320, a state management unit 330, an alarm management unit 340, and a storage unit 350.
The communication unit 310 has a function of executing communication with all the security management devices connected via the network 160 according to, for example, the Ethernet (registered trademark) communication standard. In the present embodiment, as shown in FIG. 1, it has a function of executing communication with the security management devices 200a to 200c.

Specifically, when receiving a history from the security management device, the communication unit 310 transmits the history to the analysis unit 320 and transmits a response signal indicating that the history has been received to the security management device that has transmitted the history. To do.
The analysis unit 320 has a function of analyzing the history content and a function of additionally registering the history transmitted from the communication unit 310 in the file 321 as a code. The analysis unit 320 analyzes the transmitted history and transmits the status flag included in the history to the status management unit 330 together with the code of the security management device that has transmitted the history.

  In addition, the analysis unit 320 confirms the history accumulation flag transmitted, and instructs the storage unit 350 to interrupt the history database update operation when the accumulation flag indicates “1”. In addition, after instructing the interruption, the analysis unit 320 releases the interruption in the following two cases. That is, (1) a case where a predetermined number (for example, three) of histories whose accumulation flag indicates “0” is continuously received, and (2) a case where a predetermined time (for example, two minutes) has elapsed without receiving the history. .

  The state management unit 330 has a function of storing state information indicating the state of each security management device for each security management device. Then, the state management unit 330 has a function of updating the held state information based on the security management device code transmitted from the analysis unit 320 and the state information. The status information indicates “0” when it is normal and “1” when it is abnormal. The state management unit 330 holds state information for each security management device. Taking FIG. 1 as an example, the state management unit 330 holds state information for a total of three security management devices 200a to 200c.

  The alarm management unit 340 has a function of managing an alarm state for each security management device. The alarm management unit 340 manages alarm information based on the status information held by the status management unit 330. Specifically, every time a history is transmitted and registered in the file 321 of the analysis unit 320, the state information of the state management unit 330 is updated, and the state information changes from “0” to “1”. If it has been changed, an alarm is issued if it has not been changed from “1”. Further, when the value is changed from “1” to “0”, or when the value is not changed from “0”, an alarm is not issued. When an alarm is issued, an alarm is to be issued on the operator interface of the server apparatus 300, and the operator recognizes that an abnormal situation has occurred.

  The storage unit 350 has a function of storing various programs and data necessary for the operation of the server apparatus 300, and also has a function of updating a history database 351 (in FIG. 3, the database is expressed as DB). The storage unit 350 also has a function of holding a GU code table 352, a device code table 353, an event code table 354, and authentication information 355 that are referred to when the history database 351 is updated. The history database 351 is a database formed by converting the history in the file 321 into a character string. The GU code table 352 is a code table that is referred to in order to convert a GU (Gate Unit: another name for security management device) code included in the history into a character string. The device code table 353 is a code table that is referred to in order to convert a CR code included in the history into a character string. The event code table 354 is a code table referred to for converting an event code into a character string. Details of the history database 351, various code tables, and authentication information 355 will be described later.

  The storage unit 350 checks the file 321 periodically (for example, every second), and if there is a history that is not registered in the history database 351 in the file 321, the code of the history is stored in each code table and the authentication information 355. Is converted to a character string and added to the history database 351. The storage unit 350 suspends the periodic update operation of the history database 351 based on the suspension instruction from the analysis unit 320, releases the suspension according to the release instruction, and restarts the update operation of the history database 351.

Other devices will be briefly described.
The card reader 120 periodically transmits a request signal for requesting an ID held by the IC card to the IC card, and a security connected to the ID included in the response signal received as a response to the request signal. It transmits to the management apparatus 200.
The electric lock 130 performs locking and unlocking according to instructions from the connected security management apparatus 200. In the security management system, the IC card 150 holds a unique ID for each IC card, receives a request signal for requesting an ID from the card reader 150, and transmits a response signal including the held ID. . The electric lock 130 notifies the security management device of an error when the lock is not in a predetermined state (for example, the lock is blocked by a wall or the like and cannot be locked).

Although not shown, the door provided in each area is provided with an open / close sensor, and the open / close sensor notifies the security management apparatus 200 whether the door is open. The open / close sensor is realized by, for example, a magnet sensor provided on a door and a magnet provided on a wall facing the magnet sensor when the door is closed.
<Data>
Hereinafter, various data relating to the security management system will be described.

FIG. 4 shows a configuration for one history transmitted from the security management apparatus 200 to the server apparatus 300, which is registered in the history information 251 held by the security management apparatus 200 and the file 321 held by the server apparatus 300. It also refers to the state of being.
As shown in FIG. 4, the history includes an accumulation flag 451, a date / time code 452, a GU code 453, a device code 454, an event code 455, a user ID 456, and a status flag 457. In addition, a code indicating an electric lock or a code of an open / close sensor may be included. The data length of each flag or code is determined in advance, so that the analysis unit 320 of the server apparatus 300 can analyze which part of the history has which data.

  The accumulation flag 451 is a flag indicating whether the history transmission has succeeded or failed, and is indicated by “0” or “1”. When the accumulation flag 451 in the security management device is “0”, it indicates that the transmission has been successful, and when it is “1”, the transmission has failed and the history has not been transmitted yet. And is used for selection of a history to be transmitted when a survival confirmation signal is received from the server device 300. The accumulation flag 451 in the server device 300 is used by the analysis unit 320 as a trigger for interrupting and resuming update of the history database.

The date / time code 452 is date / time information indicating when the history has occurred, and includes information up to the year / month / day and time in seconds. Specifically, for example, “20090231113116” means “2009 March 21, 13:11:16”. Note that the date and time codes shown in this specific example are written in decimal notation for convenience of explanation.
The GU code 453 is a code indicating the security management device that generated the history. Each security management device is assigned a unique code, and is used to recognize in which security management device the server device 300 is an event.

The device code 454 is a code for indicating where the event code is generated when the event code is an authentication or error, and is applied to each card reader or electric lock. Means a unique code. The device code 454 is used for recognizing which card reader the event has occurred on the server device.
The event code 455 is a code indicating the content of the event that has occurred.

The user ID 456 is information indicating the ID used for the authentication when the event code 455 of the history matches the one indicating the execution of authentication (authentication success or authentication failure).
The status flag 457 is a flag indicating whether or not the security management apparatus that has generated the history is operating normally. If it is “0”, it is normal, and if it is “1”, it is abnormal. Security management devices, card readers, electric locks, etc. are equipped with detection mechanisms such as various sensors for judging whether they are normal or abnormal, and are normal based on the detection values of these sensors. Whether or not, and the value of the status flag 457 is determined based on the determination.

The history information 251 and the file 321 are a set of the history, and the security management device and the server device can distinguish the history and other histories.
Next, the authentication information 252 will be described. The authentication information 252 is referred to in order for the security management device to authenticate the ID read by the card reader. Each security management device holds authentication information having the same data configuration, and the authentication information 355 held by the server device 300 is a collection of authentication information 252 held by each security management device. Therefore, here, as a representative example, a data configuration example of the authentication information 252 held by the security management apparatus 200a of FIG. 1 will be described.
As shown in FIG. 5, the authentication information 252 is an information group in which identification information 502, a user name 503, and an authority 504 are associated with a management number 501. The management number 501 is described as “Management No.” in FIG.
The management number 501 is a management number assigned for convenience in order for the authentication unit 220 of the security management apparatus to manage each authentication information.
The identification information 502 is identification information unique to the IC card.
The user name 503 is the name of the user holding the IC card.
The authority 504 indicates information on an area where the corresponding user can enter the room.
For example, the identification information of the IC card corresponding to the management number “10686” is “IC00006897”, the name of the user holding the IC card is “Noriko Aoi”, and its authority is “Area A, B”. It has become. That is, “Noriko Aoi” is allowed to enter Area A and Area B.
The operator of the security management system may register a new ID and user in the authentication information 252 and authentication information 355 as necessary, or may delete the registered ID and user.

Next, the GU code table 352 held by the server apparatus 300 will be described with reference to FIG.
The GU code table 352 is a table used to convert a GU code in the history into a character string. As shown in FIG. 6, the GU code table 352 is a table in which a GU code 601 and a GU setting name 602 are associated with each other.
The GU code 601 indicates a unique code assigned to each security management apparatus.

The GU setting name 602 is a name set by the operator for each security management apparatus, and is a name set so that the operator can easily recognize which security management apparatus is indicated.
According to FIG. 6, the GU setting name corresponding to the GU code “G04” is “A building 1F management device”, and for example, the GU code “G04” is set in the security management device 200a of FIG. Then, the server device 300 can recognize that the security management device 200a is “A building 1F management device”, and if the GU code included in the history is “G04”, the history database stores “A building” "1F management device" can be converted and registered.

FIG. 7 is a diagram illustrating a data configuration example of the device code table 353 held by the server apparatus 300. As illustrated in FIG. 7, the device code table 353 is a table in which a device code 701 and a device setting name 702 are associated with each other.
The device code 701 indicates a unique code assigned to each card reader or electric lock.
The device setting name 702 is a name set by the operator for each card reader, and is a name set so that the operator can easily recognize which card reader or electric lock is installed on which door. . In FIG. 7, the door 1 is simply described, but an electric lock or the like may be attached thereafter.

According to FIG. 7, the device setting name corresponding to the device code “C036” is “General Affairs Department Section 2_Door 1”, and for example, the device code “C036” is set in the card reader 120a of FIG. If so, the server apparatus 300 can recognize that the card reader 120a is a card reader installed in “General Affairs Department Section 2_door 1”.
FIG. 8 is a diagram illustrating a data configuration example of the event code table 354. As shown in FIG. 8, the event code table 354 is a table in which event codes 801 and event contents 802 are associated with each other.

The event code 801 indicates a unique code assigned to various events that can occur in the security management system.
The event content 802 indicates the name of the event assigned to each event code.
FIG. 9 is a diagram illustrating a data configuration example of the history database 351 generated by the storage unit 350. As illustrated in FIG. 9, the history database 351 is information in which a management number 901, a date and time 902, identification information 903, a user name 904, a location 905, and an event 906 are associated with each other. In addition to these pieces of information, information on the card reader that has performed authentication may be included.
The management number 901 is a management number assigned for convenience in order for the storage unit 350 to manage each history.
The date and time 902 is information on the date and time when authentication was performed or an event occurred.
The identification information 903 is identification information unique to the IC card used for authentication.
The user name 904 is the name of the user who holds the IC card used for authentication. The user name 904 is obtained by converting the identification information using the authentication information 355.
The location 905 is information on a security management device or a door where authentication has been performed or an event such as unlocking of a key or a decrease in battery voltage has occurred.
The event 906 is information indicating the content of the event that has occurred. The event 906 is obtained by converting the event code using the event code table 354.
For example, the identification information of the IC card corresponding to the management number “087882” is “IC00006897”, the name of the user holding the IC card is “Noriko Aoi”, and the place where the authentication is performed is “ “Personnel Department_Door 1” and the date of authentication is “November 12, 2008, 12:13:54”, and according to the event content, Noriko Aoi is “HR Department_Door 1”. The card reader provided in the system succeeds in authentication. If the generated event is not related to authentication, the identification information 902 and the user name 903 are blank. In FIG. 9, “−” is described.

The storage unit 350 converts the history into a character string using the GU code table 352, the device code table 353, the event code 354, and the authentication information 355, and adds it to the history database. A history database 351 as shown is generated.
<Operation>
From here, operation | movement of the security management apparatus of the security management system which concerns on this invention, and the server apparatus 300 is demonstrated. Here, the security management apparatus will be described as the security management apparatus 200 as in the configuration of the security management apparatus described above.

First, the operation of the security management apparatus 200 will be described with reference to FIG. FIG. 10 is a flowchart showing an operation when a history is generated in the security management apparatus 200.
When an event such as authentication occurs in the security management device 200 (step S1001), the history generation unit 230 generates a history (step S1002).

The external communication unit 240 of the security management device 200 receives the history code transmitted from the history generation unit 230 and transmits it to the server device 300.
The external communication unit 240 determines whether or not the transmission of the history has succeeded based on whether or not a response signal to the history transmitted from the server device 300 has been received within a predetermined time after transmitting the history (step S1003).

  When the response signal for the history is received, the history is successfully transmitted (YES in step S1003), so the external communication unit 240 adds the history with the accumulation flag remaining 0 to the history information 251 (step S1003). S1004). If there is no free space to be added, the history with the accumulation flag set to 0 and the date and time information with the oldest history is overwritten. Then, the security management apparatus 200 enters a standby state and waits for the next event to occur (return to step S1001).

On the other hand, when the response signal for the history transmitted within the predetermined time cannot be obtained (NO in step S1003), the external communication unit 240 changes the accumulated flag of the transmitted history to “1” and sets the history information 251. Registration is performed (step S1005).
After that, when the history generation unit 230 generates a new history (YES in step S1006), the external communication unit 240 does not transmit the newly generated history to the server device 300 and sets the accumulation flag. It is changed to “1” and registered in the history information 251 (step S1005).

While the history generation unit 230 generates a new history each time an event occurs, the external communication unit 240 monitors whether there is a survival confirmation signal from the server device 300 (step S1006). .
When the external communication unit 240 receives the survival confirmation signal from the server device 300 (YES in step S1007), it means that the communication has been recovered, and thus indicates that the survival confirmation signal is alive. A survival response signal is transmitted, and a history in which the accumulation flag is “1” is searched with reference to the accumulation flag of the history information 251. Then, the history in which the accumulation flag obtained by the search is “1” is transmitted to the server device 300 (step S1008).

When the external communication unit 240 has not received the survival confirmation signal from the server device 300 (NO in step S1007), the process returns to step S1006.
After transmitting the history whose accumulation flag is “1”, the external communication unit 240 determines whether or not the history has been successfully transmitted depending on whether or not the response signal for the history from the server device 300 has been received within a predetermined time. (Step S1009).

When the transmission of the history having the accumulation flag “1” is successful (YES in step S1009), the external communication unit 240 updates the history information 251 by changing the accumulation flag of the transmitted history to “0”. (Step S1010), the process returns to step S1001.
If transmission of the history with the accumulation flag “1” has failed (NO in step S1009), the process returns to step S1005.

The above is the operation related to the history transmission of the security management apparatus 300.
Now, the operation of the server device 300 that receives the history will be described. The server apparatus 300 will be described separately for the operation of the storage unit 350 and the operation of other functional units. FIG. 11 is a flowchart showing operations of the communication unit 310 and the analysis unit 320, and FIG. 12 is a flowchart showing operations of the storage unit 350.

As illustrated in FIG. 11, first, when receiving a history, the communication unit 310 transmits the received history to the analysis unit 320, generates a response signal for the history, and transmits the response signal to the security apparatus that has transmitted the history ( Step S1101).
The analysis unit 320 analyzes whether the received history accumulation flag is “1” (step S1102).

  If the accumulation flag is “0” (NO in step S1102), the analysis unit 320 adds the history to the file 321 as a code. If there is no free space to add, the oldest history is overwritten. Further, the analysis unit 320 transmits the status flag in the received history to the status management unit 330 to instruct update of the status information, and instructs the alarm management unit 340 to update the alarm (step S1103). The state management unit 330 overwrites the state information corresponding to the security device information transmitted from the analysis unit 320 with the state flag transmitted. Further, the alarm management unit 340 issues an alarm in response to a change in state in the state management unit 330.

On the other hand, when the accumulation flag is “1” (YES in step S1102), the analysis unit 320 instructs the storage unit 350 to interrupt the update of the history database (step S1104).
Then, the history is added to the file 321 as a code. If there is no free space to add, the oldest history is overwritten. Further, the analysis unit 320 transmits the status flag in the received history to the status management unit 330 to instruct update of the status information, and instructs the alarm management unit 340 to update the alarm (step S1105). The state management unit 330 overwrites the state information corresponding to the security device information transmitted from the analysis unit 320 with the state flag transmitted. Further, the alarm management unit 340 issues an alarm in response to a change in state in the state management unit 330.

  After instructing to interrupt the update of the history database, the communication unit 310 generates and transmits a response signal every time the history is received, the analysis unit 320 registers the history in the file 321, and the state management unit 330 stores the state. Information is managed, and the alarm management unit 340 manages alarm on / off. The analysis unit 320 sequentially analyzes the history accumulation flag and determines whether or not three history records having the accumulation flag “0” have been received in succession (step S1106).

In the course of the process after instructing to interrupt the update of the history database, when three history records with the accumulation flag “0” are received in succession (YES in step S1106), the analysis unit 320 saves them. The unit 350 is instructed to resume updating the history database (step S1108), and the process returns to step S1101.
Further, even if the analysis unit 320 does not continuously receive three histories whose accumulation flag is “0” (NO in step S1106), the analysis unit 320 instructs to interrupt the update of the history database and receives the last history. Even when the history is not received for a predetermined time (for example, 20 seconds) (YES in step S1107), the restart of the history database is instructed (step S1108), and the process returns to step S1101.

In step 1107, when the next history is received before the predetermined time has elapsed since the last history was received (step S1107), the process returns to step S1106.
Finally, the operation of the storage unit 350 will be described using the flowchart of FIG.
The storage unit 350 monitors whether there is an instruction to interrupt the update of the history database from the analysis unit 320 (step S1201).

When the storage unit 350 receives a history database update interruption instruction from the analysis unit 320, the storage unit 350 interrupts the periodic history database update. Then, it is monitored whether there is an instruction to cancel the interruption (step S1202). If there is no release instruction (NO in step S1202), the process waits for the release instruction to arrive.
If there is a cancel instruction (YES in step S1202), the process proceeds to step S1204.

When there is no instruction to interrupt the update of the history database from the analysis unit 320 (NO in step S1201), the storage unit 350 determines whether a predetermined time (for example, 1 second) has elapsed since the previous update of the history database. Is determined (step S1203). If the predetermined time has not elapsed (NO in step S1203), the process returns to step S1201.
If the predetermined time has elapsed (YES in step S1203), the storage unit 350 checks the file 321 of the analysis unit 320 (step S1204), and whether there is a new history that has not yet been registered in the history database. Is searched (step S1205). This is performed by a flag indicating whether or not each history is registered. When the analysis unit 320 registers the history in the file 321, it is not registered. When the storage unit 350 registers the history in the history database, it is registered. Change to

  If there is a new history in the file 321 (step S1205), the storage unit 350 converts the history from a code to a character string using each code table, authentication information, etc., and additionally registers it in the history database 351. Then (step S1206), the process returns to step S1201. If there is no new history (step S1204), the history database 351 is not updated and the process returns to step S1201.

The above is the operation of each device related to the security management system.
<Summary>
With the installation of the security management system, low-performance processors are still used as the processors of the security management device 200 and the server device 300 in order to reduce the overall cost. However, if the processor of the server apparatus 300 has a low performance, it may be necessary to use almost all of the processing performance for updating the history database.

  Then, when the history database is updated, transmission of a response signal to the history, state update processing in the state management unit 330, and alarm management in the alarm management unit 340 cannot be processed. In particular, communication between the security management device and the server device is interrupted due to some reason, so that unsent histories are accumulated in the security management device. After communication is restored, unsent histories are sent together. Sometimes it takes more time to add only one history to the history database update. Then, as a matter of course, the processor is devoted to much time for updating the history database, so that the state cannot be updated for many times.

Since the security management system manages the entry / exit of users to / from the security area, the state management of each security management device in the state management unit 330 and the alarm management in the alarm management unit 340 are controlled in real time as much as possible. It is a situation that we want to avoid that it becomes impossible.
However, when the server apparatus 300 shown in the present embodiment receives a history with an accumulation flag, that is, “1”, there is a high possibility of receiving a lot of history from the history. Therefore, the periodic update of the history database is interrupted to the storage unit 350. As a result, since the history database update process does not occur, the processing capability of the processor can be allocated to the transmission of a response signal to the history and the update of the state information during that time. After that, when the server apparatus 300 has room, the history database is updated again, so that there is no problem that history is lost when the history is stored in the history database.
<Supplement>
In the above embodiment, the method of implementing the present invention has been described, but the present invention is not limited to this. Hereinafter, various modified examples included in the present invention other than the above-described embodiment will be described.
(1) In the above-described embodiment, when the storage unit 350 adds a history database to the history database, a flag that has been stored is added to the history. However, the same history is duplicated. In this case, the registered history may be deleted from the file 321.
(2) In the above embodiment, each authentication information includes a user name. However, the user name substantially only needs to be in the authentication information 355 held by the server apparatus 300, and each security management apparatus does not have to have a user name item.
(3) In the above-described embodiment, each security management device is configured to stop transmission of a history until a survival confirmation signal is received from the server device 300 when the history cannot be transmitted. However, this does not have to wait for the survival confirmation signal, and the following method may be used.

That is, for a history with the accumulation flag “1”, a configuration may be made in which history transmission is attempted every predetermined time (for example, every 30 minutes). When there is a response signal for the transmitted history, the accumulated flag of the transmitted history may be changed to “0”.
(4) Although not particularly described in the above embodiment, the server apparatus 300 may have an interface for an operator to browse and search the history database 351.

Based on an instruction from the operator, the interface displays information on whether or not the security management apparatus is operating normally by using the status information managed by the status management unit 330, and the alarm management unit 340 manages the alarm. A function for notifying the state may also be held.
Further, it may have a function of receiving a query input from an operator, searching for a history matching the query, and displaying the list. The query includes, for example, a user name, date and time, and a location. When the input query is a user name, a history including the input user name is searched.
(5) The operation related to the update of the history database of the server apparatus, the update stop process (see FIGS. 11 and 12) shown in the above embodiment is performed on the processor of the server apparatus and the various circuits connected to the processor. A control program comprising program codes for execution can be recorded on a recording medium, or can be distributed and distributed via various communication paths. Such recording media include IC cards, hard disks, optical disks, flexible disks, ROMs, and the like. The distributed and distributed control program is used by being stored in a memory or the like that can be read by the processor, and the processor executes the control program, thereby realizing various functions as shown in the embodiment. Will come to be.

110, 110a to 110e, 120, 120a to 120e Card reader (CR)
130, 130a-130e Electric lock 140a-140e Door 160 Network 200, 200a-200e Security management device (GU)
210 I / F unit 220 Authentication unit 230 History generation unit 240 External communication unit 250 Storage unit 251 History information 252 and 355 Authentication information 300 Server device 310 Communication unit 320 Analysis unit 321 File 330 Status management unit 340 Alarm management unit 350 Storage unit 351 History database (DB)
352 GU Code Table 353 Device Code Table 354 Event Code Table

Claims (7)

A server device that manages the history of users entering and leaving the security management area,
A history receiving means for receiving a history transmitted from a security management device for managing entry / exit of a user to / from the security management area;
Response means for transmitting a response signal indicating that the history has been received to the security management device that has transmitted the history;
A history database for managing the history by a database system;
Storage means for storing the history received by the history receiving means;
Periodically, database update means for adding a history stored in the storage means and not registered in the history database to the history database in a format for the history database;
When a new flag received by the history receiving unit is added with an accumulation flag indicating that the history has not been transmitted from the security device and reached its own server device, the database updating unit An interruption means for interrupting the addition of history to the history database;
A server device comprising: The interruption unit interrupts the periodic check of the database update unit, and then interrupts the interruption when the history reception unit continuously receives a history without a predetermined number of the accumulation flags. The server device according to claim 1, wherein the server device is released. The suspension means cancels the suspension when the history receiving means has not received a history for a predetermined time after the periodic confirmation of the database update means is suspended. 1. The server device according to 1. The history transmitted by the security management device to the server device includes a status flag indicating the status of the security management device,
The server device
Status management means for managing status information indicating whether the security management device is operating normally;
The server apparatus according to claim 1, further comprising an update unit configured to update the state information based on the history flag. A security management system including a security management device that manages entry / exit of a user to / from a security management area, and a server device that manages a history of the entry / exit in the security management device,
The server device
History receiving means for receiving a history transmitted from the security management device for managing entry / exit of a user to / from the security management area;
Response means for transmitting a response signal indicating that the history has been received to the security management device that has transmitted the history;
A history database for managing the history by a database system;
Storage means for storing the history received by the history receiving means;
Periodically, database update means for adding the history stored in the storage means and not registered in the history database to the history database in the history database format;
When a new flag received by the history receiving unit is added with an accumulation flag indicating that the history has not been transmitted from the security device and reached its own server device, the database updating unit An interruption means for interrupting the addition of the history to the history database,
The security management device includes:
Entry / exit management means for managing entry / exit of the user into the security management area based on authentication information including an identifier acquired from an authentication medium held by the user;
History storage means for storing a history of entry / exit of the user into the security management area together with the accumulation flag determined based on success or failure in transmission to the server device;
History transmission that is stored in the history storage unit and that has not yet been transmitted to the server device is transmitted to the server device with the accumulation flag when the transmission flag indicates that transmission has failed. And a security management system. The history storage means, when a response to the history transmitted by the history transmission means is not obtained from the response means, stores the accumulation flag with the history of no response. The security management system according to claim 5. The security according to claim 6, wherein the history storage means updates the history in a state where the accumulation flag is not attached when transmission of the history attached with the accumulation flag is successful. Management system.

Images