JP2014086002A - Management device, program and card management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a management device, a program and a card management system by which a card rental work is made easier.SOLUTION: A management device 1 manages a main card 7a which is owned by a user P and a lending card 7r which can be lent to the user P, in which the lending card 7r is at an unusable state, on the other hand, the main card 7a is at a usable state in a gate system 4 in use start acceptance, and the management device 1 comprises: a main card acceptance part 11 which accepts information on the main card 7a; a main card specification part 12 which retrieves a main card DB 31 for storing information regarding the main card 7a and a card ID on the basis of the accepted information to specify the user P; a lending card acquisition part 15 which acquires a card ID of the lending card 7r to be lent to the user P from a lending card DB 32; and a lending processing part 16 which makes the lending card 7r of the card ID usable and makes the main card 7a specified by the main card specification part 12 unusable in the gate system 4 in response to acquisition of the card ID.

Description

  The present invention relates to a management device, a program, and a card management system.

  Conventionally, various methods for restricting entry into an area such as an office or a machine room where security needs to be secured and printing in a printing system to a specific authorized user have been shown. For example, in a printing system, if a UID read from an IC card can be authenticated by an authentication table stored in an authentication server, a printing system is disclosed that acquires and prints the print data of the user temporarily stored on the server. . And when the IC card is lost or the IC card is forgotten, an operation using a temporary lending card is described (for example, Patent Document 1).

JP 2010-108348 A

  In patent document 1, when lending a temporary lending card to a user, there is no special description about the process with respect to the IC card which the user owns. In consideration of loss, it is necessary to make it impossible to use an IC card owned by the user. In such a case, card processing for the lending card and the IC card owned by the user is necessary, and the card lending operation is troublesome.

  Therefore, an object of the present invention is to provide a management device, a program, and a card management system that make the card lending business easier.

  The present invention solves the above problems by the following means. In addition, in order to make an understanding easy, although the code | symbol corresponding to embodiment of this invention is attached | subjected and demonstrated, it is not limited to this. In addition, the configuration described with reference numerals may be improved as appropriate, or at least a part thereof may be replaced with another configuration.

A first invention is a management device (1, 201) for managing an IC card for causing a device (4, 204) to perform a predetermined operation using the IC card (7, 207), The IC card includes a main card (7a, 207a) that is an IC card owned by a user (P) and a lending card (7r, 207r) that is an IC card that can be lent to the user. At the time of accepting the start of use of the lending card, the lending card is in an unusable state for the device, the book card is in a usable state for the device, and the book related to the book card A book card storage unit (31) for storing card information and book card identification information for identifying the book card; a lending card storage unit (32) for storing card identification information for identifying the lending card; Said A book card accepting unit (11) that accepts input of card information, and a book card that searches the book card storage unit based on the book card information accepted by the book card accepting unit and identifies the user of the book card A specifying unit (12), a lending card acquisition unit (15) for acquiring one card identification information corresponding to a lending card to be lent to the user from the lending card storage unit, and the lending card In response to the acquisition of the one card identification information by the acquisition unit, the lending card having the one card identification information can be used for the device and is specified by the card specifying unit. And a lending processing unit (16) for performing processing of making the book card having the book card identification information unusable to the device. A.
The second invention is the management device (1, 201) of the first invention, wherein the card identification information of the book card (7a, 207a) processed by the lending processing unit (16), and the The management apparatus includes an association unit (17, 217) for associating one card identification information with the lending card (7r, 207r).
A third invention is the management device (1, 201) of the first invention or the second invention, wherein the lending card (7r, 207r) stored in the lending card storage unit (32) When displaying the use state and displaying the use state of the lending card having the one card identification information stored in the lending card storage unit, the main card (7a, 7a, The management apparatus includes a usage state display unit (20) that displays the usage state of 207a) in association with each other.
A fourth invention is the management device (1, 201) according to any one of the first invention to the third invention, wherein the book is processed in response to the processing by the lending processor (16). An authority granting unit (18) for granting the authority of the card (7r, 207r) to the lending card (7r, 207r) that regulates the operation of the device (4, 204) using the card (7a, 207a). It is a management device characterized by comprising.
The fifth invention is the management device (1, 201) according to any one of the first invention to the fourth invention, wherein the lending card (7r, 207r) is used for the lending at the time of completion of use of the lending card (7r, 207r). In response to receipt of the card identification information by the return acceptance unit (21) that accepts card identification information of the card, the lending card corresponding to the card identification information is transferred to the device (4,204). ) And a return processing unit (22) for performing a process of making the main card (7a, 207a) associated with the lending card usable for the device. The management device characterized by the above.
A sixth invention is the management device (1, 201) of the fifth invention, wherein the lending card (7r, 207r) according to the processing by the return processing unit (22), A management device comprising: an association deleting unit (23) for deleting association with the book card (7a, 207a) associated with the lending card.
The seventh invention is the management device (1, 201) of the fifth invention or the sixth invention, in which the card (7a, 207a) is temporarily suspended as a reason for lending, A reason receiving unit (14) for receiving selection of one of the plurality of reasons for lending, and the return processing unit (22) receiving the one received by the reason receiving unit. If the reason for lending the card is ceased to be used, the book card can be used for the device (4, 204). The management device is characterized in that it remains unusable.
The eighth invention is the management device (1, 201) from the fifth invention to the seventh invention, wherein the book is processed in response to the processing by the return processing unit (22). A management device comprising an authority deletion unit (24) for deleting the authority of the card (7a, 207a) from the lending card (7r, 207r).
A ninth invention is the management device (1, 201) according to any one of the first invention to the eighth invention, wherein the card storage unit (31) is a photograph of the user (P). The management apparatus is characterized by comprising a confirmation data output unit (13) that stores data and outputs the face photo data of the user specified by the card specifying unit (12).
A tenth aspect of the present invention is the management apparatus according to any one of the first to ninth aspects of the present invention, at the time of accepting the start of use of a lending card having other card identification information different from the one card identification information. The lending card having the one card identification information is usable for the device, and the lending card having the other card identification information is not usable for the device. The lending card acquisition unit provides the other card identification information corresponding to the lending card to be lent to the user lending the lending card having the one card identification information, Acquired from the lending card storage unit, and the lending processing unit makes the lending card having the acquired other card identification information usable for the device and the one card identification. That the loan card with information performs a process of disabled for the device, a management device according to claim.
The eleventh invention is the management device (201) according to any one of the first invention to the ninth invention, wherein the book card identification information identifies the user (P) and the number of times the book is issued. A card issuing request unit (219) for requesting the issuing of the book card (207a) and a lending card (207r) having the one card identification information usable for the device (204) When a new book card of the user requested by the book card issuance request unit is issued to the user who rents the card, the card is associated with the card identification information of the lending card. An association unit (217) for deleting the association of the book card with the book card identification information and associating the card identification information of the lending card with the book card identification information of the newly issued book card A management apparatus, characterized in that, with a.
The twelfth invention is the management device (201) of the eleventh invention, wherein the book card issuance request unit (219) responds to the book card (207a) of the user (P) who requested it. When the lending card (207r) is associated, the management device is characterized in that the device (204) is requested to issue a new card that is unavailable.

  A thirteenth aspect of the invention is a management device (1, 201) that is a computer for managing an IC card for causing the device (4, 204) to perform a predetermined operation using the IC card (7, 207). A program to be executed, and the IC card includes a main card (7a, 207a) that is an IC card owned by a user (P) and a lending card (7r, 207) that is an IC card that can be lent to the user. 207r), at the time of accepting the start of use of the lending card, the lending card is in an unusable state for the device, and the card is in a usable state for the device The management device includes a book card storage unit (31) for storing book card information relating to the book card and book card identification information for identifying the book card, and a card for identifying the lending card. A lending card storage unit (32) for storing card identification information, and the management device accepting the input of the book card information, and the book card information received by the book card receiving means. The card identifying means for searching the book card storage unit based on the card to identify the user of the book card, and the card identification information corresponding to the card for lending to be lent to the user, A lending card acquisition unit that acquires from the card storage unit, and the lending card having the one card identification information in response to the acquisition of the one card identification information by the lending card acquisition unit. And the book card having the book card identification information specified by the book card specifying means is disabled for the device. And lending processing means for processing, thereby to function, a program characterized.

  A fourteenth aspect of the present invention is an apparatus (4, 204) that performs a predetermined operation using an IC card (7, 207), a main card (7a, 207a) that is an IC card owned by a user (P), and the use Card management system (100, 200) comprising the IC card including a lending card (7r, 207r) that is a lending card that can be lent to a person, and a management device (1, 201) for managing the IC card The lending card is in an unusable state with respect to the device and the card is in a usable state with respect to the device at the start of use of the lending card. The management device includes a book card storage unit (31) for storing book card information relating to the book card and book card identification information for identifying the book card, and a card for identifying the lending card. Based on the book card information received by the book card accepting unit, the book card accepting unit (11) for accepting the input of the book card information, the lending card storage unit (32) for storing other information The lending card storage unit that searches the storage unit to identify the user of the card and identifies the card identification information corresponding to the lending card to be lent to the user. The lending card acquisition unit (15) acquired from the lending card and the lending card having the one card identification information in response to the acquisition of the one card identification information by the lending card acquisition unit. Lending for making the book card having the book card identification information identified by the book card identifying unit unavailable to the device Further comprising processing section (16), and a card management system characterized.

  ADVANTAGE OF THE INVENTION According to this invention, the management apparatus, program, and card management system which made card | curd lending business easier can be provided.

It is a figure showing the whole card management system composition concerning a 1st embodiment. It is a figure which shows the function structure of the card management system which concerns on 1st Embodiment. It is a figure which shows the example of the database memorize | stored in the management apparatus which concerns on 1st Embodiment. It is a figure which shows the example of the database memorize | stored in the gate system which concerns on 1st Embodiment. It is a flowchart of the card lending process in the card management system according to the first embodiment. It is a figure which shows the example of a screen at the time of card | curd lending with the management apparatus which concerns on 1st Embodiment. It is a flowchart of the card | curd inquiry process in the management apparatus which concerns on 1st Embodiment. It is a figure which shows the example of a screen at the time of the card inquiry in the management apparatus which concerns on 1st Embodiment. It is a flowchart of the gate process in the gate system which concerns on 1st Embodiment. It is a flowchart of the card return process in the card management system concerning a 1st embodiment. It is a figure which shows the example of a screen at the time of the card return in the management apparatus which concerns on 1st Embodiment. It is a figure which shows the function structure of the card management system which concerns on 2nd Embodiment. It is a figure which shows the example of the database memorize | stored in each apparatus which concerns on 2nd Embodiment. It is a flowchart of this card reissue process in the card management system concerning a 2nd embodiment. It is a figure which shows the example of a screen at the time of the card inquiry which concerns on 2nd Embodiment.

DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. This is merely an example, and the technical scope of the present invention is not limited to this.
(First embodiment)
FIG. 1 is a diagram illustrating an overall configuration of a card management system 100 according to the first embodiment.
The card management system 100 includes a management device 1, a gate system 4 (device), and an IC card 7.

For example, the management device 1 includes a reception server 1a and a reception terminal 1b. The reception server 1a and the reception terminal 1b are connected to be communicable.
The reception server 1a is provided in a facility such as a data center, for example. The reception server 1a stores data input by the reception terminal 1b. In addition, the reception server 1 a includes an interface for performing communication with the gate system 4.
The reception terminal 1b is a terminal provided near the entrance of a company building, for example, and operated by a reception operator. Although only one reception terminal 1b is shown in the figure, a plurality of reception terminals may be provided.

The gate system 4 includes, for example, a gate management server 4a and a plurality of gates 6 (only one is shown in FIG. 1), and the gate management server 4a and the gate 6 can communicate with each other. It is connected.
The gate management server 4a is provided in a data center, for example. The gate management server 4 a stores data for opening and closing the gate 6 with respect to the gate 6. In addition, the gate management server 4 a includes an interface for performing communication with the management apparatus 1.
The gate system 4 updates the database of the gate system 4 based on the data received from the management device 1. When the management apparatus 1 transmits data to the gate system 4, the gate system 4 immediately receives data from the management apparatus 1 according to the specifications of the card management system 100, and updates the data based on the received data. .

The gate 6 is, for example, a device that is provided in the vicinity where the reception terminal 1b is installed, and restricts entrance of a company building by opening and closing its door. The gate 6 is installed so as to partition between an area where security that can be moved by anyone is not set and a security area Sa where security is set so as to allow a specific person such as an employee to move. It is a gate. In the embodiment, the gate 6 can pass when the user P carrying the IC card 7 enters the security area Sa. A plurality of gates 6 are arranged according to each security level of each security area Sa. The gate 6 includes a reader unit 60.
The reader unit 60 is a reader that reads data stored in the IC card 7.

The IC card 7 is used when the user P passes through the gate 6 when entering the security area Sa. There are two types of IC cards 7: a book card 7a owned by the user P and a lending card 7r used as a substitute for the book card 7a when the card 7a is forgotten or lost.
The IC card 7 has a card ID (IDentifier) (card identification information) printed on the card surface. The user P or the reception operator can determine the card ID by looking at the face of the IC card 7. In the case of this card 7a, the employee ID is used as the card ID (this card identification information). The card ID is stored in the storage unit 75 (described later) of the IC card 7.
The management device 1 and the gate system 4 are connected to be communicable via a communication network N.
The communication network N may be, for example, a dedicated line that directly connects the management device 1 and the gate system 4 or may be an Internet line. A part of the communication network N may perform wireless communication.

Next, the flow of entering the security area Sa by the user P will be described.
First, the case where the user P possesses this card 7a is demonstrated. The user P goes to the gate 6 without stopping at the reception, that is, without performing an operation by the reception terminal. Then, the user P holds (touches) the card 7 a close to the reader unit 60 of the gate 6. By doing so, the card 7 a communicates with the gate 6. The gate 6 inquires of the gate system 4 whether or not the card 7a can open the gate 6. When the gate system 4 permits the gate 6 to be opened, the gate 6 is opened, and the user P can pass through the gate 6 and enter the security area Sa. The gate 6 closes the door after the user P passes.

Next, the case where the user P forgets or loses the card 7a will be described with reference to FIG. The user P first goes to the reception where the reception terminal 1b of the management apparatus 1 is provided. Then, the user P requests the reception operator to temporarily lend the lending card 7r. Then, the reception operator takes out one lending card 7r from the plurality of lending cards 7r stocked (# 1), and performs a lending process in the management apparatus 1 (# 2). The user P receives the lending card 7r subjected to the lending process from the operator (# 3).
Thereafter, the user P carries the received lending card 7r and goes to the gate 6 (# 4). The user P then holds (touches) the lending card 7r close to the reader unit 60 of the gate 6 (# 5). By doing so, the lending card 7r communicates with the gate 6. The subsequent processing is the same as when the user P uses the card 7a. When the gate system 4 permits the opening of the gate 6, the gate 6 is opened and the user P can pass through the gate 6 (# 6).

  Next, the functional configuration of the card management system 100 will be described. FIG. 2 is a diagram illustrating a functional configuration of the card management system 100 according to the first embodiment. FIG. 3 is a diagram illustrating an example of a database stored in the management apparatus 1 according to the first embodiment. FIG. 4 is a diagram illustrating an example of a database stored in the gate system 4 according to the first embodiment.

The management apparatus 1 includes a control unit 10, a storage unit 30, a display unit 36, an operation unit 38, and an interface unit (I / F unit) 39.
The control unit 10 is a central processing unit (CPU) that controls the entire management apparatus 1. The control unit 10 implements various functions according to the present invention in cooperation with the hardware described above by appropriately reading and executing the operating system (OS) and various application programs stored in the storage unit 30. doing.

The control unit 10 includes a main card receiving unit 11, a main card specifying unit 12, a confirmation data output unit 13, a reason receiving unit 14, a lending card acquisition unit 15, a lending processing unit 16, and an associating unit 17. An authority granting unit 18, a usage state display unit 20, a return accepting unit 21, a return processing unit 22, an association deleting unit 23, and an authority deleting unit 24.
The card accepting unit 11 is a control unit that accepts input of, for example, a name and employee ID of the user P who owns the card 7a as data related to the card 7a.
The card specifying unit 12 is a control unit that specifies the user P of the card 7a based on the data received by the card receiving unit 11.
The confirmation data output unit 13 is a control unit that outputs the face photo data of the user P specified by the card specifying unit 12.
The reason reception unit 14 is a control unit that receives a lending reason when lending the lending card 7r. Reasons for lending mainly include “forget” in which the user P has forgotten the card 7a, “lost” in which the user P has lost the card 7a, and “breakage” in which the card 7a is broken.
The lending card acquisition unit 15 is a control unit that acquires the card ID of the lending card 7r.
The lending processing unit 16 enables the lending card 7r having the card ID acquired by the lending card acquiring unit 15 to be used in the gate system 4 and the user card P of the user P specified by the card specifying unit 12 is used. It is a control part which performs the process which makes it unusable in the gate system 4.
The association unit 17 is a control unit that associates the card ID of the lending card 7r processed by the lending processing unit 16 with the card ID of the main card 7a.
The authority grant unit 18 is a control unit that grants a new authority to the lending card 7r. The new authority to be given is the same authority as that of the book card 7 a associated by the associating unit 17. Here, the authority is a security rank that allows the card 6 to pass through the gate 6. A plurality of gates 6 exist, and the security rank is set higher as the gate 6 is connected to a higher security area.

The usage status display unit 20 is a control unit that causes the display unit 36 to display the usage status of the lending card 7r. Here, the use state means, for example, “in use” or “pause” which is a state of being rented and stocked at the reception. In addition, when the lending card 7r is usable by the lending processing unit 16, the usage status display unit 20 displays the usage status of the card 7a associated with the lending card 7r so as to be compared. Let
The return accepting unit 21 is a control unit that accepts an input of the card ID of the lending card 7r when the use termination of the lending card 7r is accepted.
The return processing unit 22 disables the lending card 7r having the card ID accepted by the return accepting unit 21 in the gate system 4, and uses the card 7a associated with the lending card 7r in the gate system 4. It is a control unit that enables.
The association deleting unit 23 is a control unit that deletes the association between the card ID of the lending card 7r processed by the return processing unit 22 and the card ID of the main card 7a.
The authority deletion unit 24 is a control unit that deletes the authority given to the lending card 7r processed by the return processing unit 22.

The storage unit 30 is a storage area such as a hard disk or a semiconductor memory element for storing programs, data, and the like necessary for executing the control unit 10.
The storage unit 30 includes a card database (DB) 31, a lending card DB 32, and an association DB 33.
This card DB 31 is a database that stores data related to the issued book card 7a and data (employee information) related to the user P who owns the card 7a.
As shown in FIG. 3 (a), this card DB 31 uses the employee ID as key information, each of the employee name, status, authority, department name, contact information, face photo data, and number of times of issue. Store the data. The book card DB 31 is created when the book card 7 a is issued to the user P as a preliminary preparation for operating the card management system 100.

  The employee ID possessed by the card DB 31 is identification information for identifying the user P who is an employee. The employee ID is the card ID of the card 7a. The status indicates the current usage state of the card 7a. Normally, the status is “in use”, but when the card 7a is forgotten and the lending card 7r is lent to the user P, the status is “temporarily stopped (forgotten)”. The authority is a security rank that can pass through the gate 6 with the employee ID. In this example, the authority is represented by, for example, numbers, and when the authority is “1”, for example, only the gate 6 in the vicinity where the reception terminal 1b is installed is allowed to pass, and the authority is “2”. In this case, the passage of the above-described gate 6 and the subsequent gate 6 having a high security level is permitted. In this example, the authority is given higher as the number is larger, and controls the passage of the gate 6 in which various ranks are set. The face photo data stores data of the user P's face photo. The number of times of issuance is the number of times this card 7a has been issued, and is “01” when the card 7a is issued for the first time. As for the number of issuances, when the card 7a is reissued, the number increases such as “02”, “03”,.

Returning to FIG. 2, the lending card DB 32 is a database that stores the status of the lending card 7r stocked at the reception and the lending card 7r that has been lending.
As shown in FIG. 3B, the lending card DB 32 stores the status and the expiration date using the card ID as key information. The lending card DB 32 is created when the lending card 7r is issued as a preliminary preparation for operating the card management system 100. Note that the lending card 7r stocked at the reception and not lent to the user P has a status of “pause” and an expiration date of blank.
The card ID is identification information constituted by a symbol that identifies the IC card 7 and there is no duplicate. The card ID is given when the renting card 7r is issued, and is printed on the surface of the renting card 7r. The status indicates the usage status including the current lending status of the lending card 7r, and includes “in use” and “paused”. The expiration date is a time limit during which the card 6 can pass through the gate 6. The expiration date stores the date and time for the status of “in use”.
In addition, what was described above is a mere example about the holding method of authority and an expiration date, It is not limited to these.

As shown in FIG. 3C, the association DB 33 is a database that stores the card ID of the main card 7a associated by the association unit 17 and the card ID of the lending card 7r.
Returning to FIG. 2, the display unit 36 is a display device, and includes, for example, a CRT (Cathode Ray Tube), an LCD (Liquid Crystal Display), or the like.
The operation unit 38 is operated by a reception operator, for example, a keyboard or a mouse.
The I / F unit 39 is an interface with the gate system 4.

The gate system 4 includes a control unit 40, a storage unit 50, an I / F unit 59, and a reader unit 60.
The control unit 40 is a CPU that controls the entire gate system 4. The control unit 40 appropriately reads and executes the OS and various application programs stored in the storage unit 50, thereby realizing various functions according to the present invention in cooperation with the hardware described above.
The control unit 40 includes a collation unit 41, an operation permission unit 42, and an update unit 43.

The collation unit 41 refers to the collation DB 52 and the gate DB 54 of the storage unit 50 as to whether or not the card ID of the IC card 7 read from the storage unit 75 of the IC card 7 permits the opening of the gate 6. And a control unit for collation.
The operation permission unit 42 is a control unit that opens the gate 6 when the collation unit 41 determines that the operation is permitted.
The update unit 43 is a control unit that updates the collation DB 52 of the storage unit 50 based on the update data received from the management device 1.

The storage unit 50 is a storage area such as a hard disk or a semiconductor memory element for storing programs, data, and the like necessary for executing the control unit 40.
The storage unit 50 includes a verification DB 52 and a gate DB 54.
As shown in FIG. 4A, the verification DB 52 has items of a card ID, an authority, a validity flag, and an expiration date. The verification DB 52 receives update data extracted from the main card DB 31 and the lending card DB 32 stored in the storage unit 30 of the management device 1 as advance preparations for the operation of the card management system 100. Create by storing. Therefore, at the start of use of the card management system 100, the collation DB 52 is set to the same authority as that of the card DB 31 for the employee ID of the card ID, and “1” representing the validity is set to the validity flag. The maximum value is set for the expiration date. On the other hand, in the verification DB 52, when the card ID of the lending card 7r is “0” that no gate 6 can pass through the authority, “0” representing invalidity is set in the validity flag, and the expiration date The minimum value is set for each.

As shown in FIG. 4B, the gate DB 54 has items of a gate ID and authority. The gate ID is a code that identifies the gate 6. The authority is a security rank that allows passage through the gate 6.
Returning to FIG. 2, the I / F unit 59 is an interface with the management apparatus 1.
The reader unit 60 is an interface with the IC card 7. The reader unit 60 reads data in the card ID area 76 of the storage unit 75 of the IC card 7.

The IC card 7 includes a CPU 70, a storage unit 75, and an I / F unit 79.
The CPU 70 is a central processing unit that controls the entire IC card 7. The CPU 70 executes various programs according to the present invention in cooperation with the hardware described above by executing a program stored in the storage unit 75 in accordance with data received via the I / F unit 79. doing.
The storage unit 75 is a storage area such as a semiconductor memory element for storing programs, data, and the like necessary for executing the CPU 70. The storage unit 75 includes storage media such as a RAM (Random Access Memory), a ROM (Read Only Memory), and an EPROM (Erasable Programmable ROM).
The storage unit 75 includes a card ID area 76. The card ID area 76 stores a card ID.
The I / F unit 79 is an interface with the reader unit 60 of the gate system 4.

Next, pre-preparation processing when the card management system 100 is introduced will be described. Here, the case where the management apparatus 1 is newly introduced into the gate system 4 installed in advance will be described.
First, the administrator issues a plurality of lending cards 7r used in the gate system 4. The lending card 7r that has been issued has the card ID printed on the face of the lending card 7r, and the card ID area 76 of the storage unit 75 stores the same card ID as that printed on the face. ing. The plurality of issued cards 7r are stocked at the reception.
Next, the administrator creates the lending card DB 32 and stores the card IDs of the plurality of lending cards 7r that have been issued. At this time, “temporary stop” is stored in the status corresponding to the card ID.
In addition, the administrator creates this card DB 31. The present card DB 31 can be created by extracting and storing the data of the present card 7a already possessed by the user P and the data of the user P from, for example, a personnel system that is a separate system.

  Then, the updating unit 43 of the management device 1 creates update data from the created card DB 31 and the lending card DB 32 and transmits the update data to the gate system 4. By doing so, the verification DB 52 can be created in the gate system 4. The collation DB 52 of the gate system 4 stores the employee ID of the card DB 31 and the card ID of the lending card DB 32 in the item of card ID. The data extracted from the card DB 31 is stored in the verification DB 52 with the validity flag set to “1” as usable in the gate system 4. Further, the data extracted from the lending card DB 32 is stored in the verification DB 52 with the validity flag set to “0” as being unusable in the gate system 4. Therefore, even if the lending card 7r stocked is stolen, etc., and the lending card 7r before lending is used by a malicious third party, the card ID of the lending card 7r is the gate system In 4, the valid flag is “0”, that is, since the use is disabled, the gate 6 is not opened. Therefore, the operator can easily manage the lending card 7r itself.

Next, when the user P forgets the card 7a and visits the reception, a process in which the reception operator lends the lending card 7r to the user P as a process at the time of reception start reception will be described. FIG. 5 is a flowchart of the card lending process in the card management system 100 according to the first embodiment. FIG. 6 is a diagram illustrating a screen example at the time of card lending in the management device 1 according to the first embodiment.
In step S (hereinafter referred to as “S”) 10 in FIG. 5, the control unit 10 of the management device 1 displays a card lending inquiry screen 81 on the display unit 36 by the operation of the reception operator.
The card lending inquiry screen 81 shown in FIG. 6A can be displayed, for example, when the operator selects card lending from a lending card menu (not shown). In the card lending inquiry screen 81, the management device 1 searches the card DB 31 and identifies the user P by selecting the button 81b after the operator inputs at least one of the employee ID and the name.
In S <b> 11, the card accepting unit 11 accepts input of at least one of the employee ID and name of the user P.
In S <b> 12, the card specifying unit 12 performs a search process based on the input content received by the card receiving unit 11. The search result is displayed on the search result screen 82 shown in FIG. The search result screen 82 outputs a plurality of data that matches the search condition depending on the search condition. The card specifying unit 12 specifies the user P when the operator selects the corresponding record and then selects the button 82b.

In S <b> 13, the confirmation data output unit 13 outputs a card lending screen 83 as shown in FIG. 6 (3) to the display unit 36. As shown in the example of FIG. 6 (3), the card lending screen 83 has data of the user P specified by the card specifying unit 12 and a data input area for lending the lending card 7r. The card lending screen 83 displays user P's employee ID and name as well as user P's face photo data, department name, contact information, and the like as user P's data. The reception operator can confirm whether or not the user P who has borrowed the lending card 7r is the person himself / herself based on the face photo data.
In S14, the reason accepting unit 14 accepts the lending reason for the lending card 7r by selecting the lending reason on the card lending screen 83 by the operator.
Next, the operator takes out one arbitrary piece from the plurality of lending cards 7r stocked at the reception. Then, the operator inputs the card ID of the taken out lending card 7r into the lending card ID on the card lending screen 83 and selects the button 83b. In S15, the lending card acquisition unit 15 The confirmed card ID exists in the lending card DB 32 and is confirmed to be in a state before lending, and the card ID of the lending card 7r is acquired.
The operator inputs the lending time limit of the lending card 7r as the expiration date and selects the button 83c. In S16, the lending processing unit 16 lends the lending card 7r.

As the lending process, first, the lending processing unit 16 updates the card DB 31. Specifically, the lending processing unit 16 changes the status corresponding to the corresponding employee ID in the card DB 31 specified by the card specifying unit 12 from “in use” to “pause”, and the reason for lending is changed. Add to the status. Here, when the lending reason is “forgotten”, the lending card 7r itself is set to “pause” in order to temporarily disable it. When the reason for lending is “lost”, the user P does not own the book card 7a, and the possibility of using the book card 7a again is low. Further, when the lending reason is “damaged”, the card 7a cannot be used. Therefore, when the reason for lending is “lost” or “damaged”, the status is set to “stop”.
Next, the lending processing unit 16 updates the lending card DB 32. Specifically, the lending processing unit 16 changes the status of the lending card DB 32 corresponding to the card ID acquired by the lending card acquiring unit 15 from “suspended” to “in use”. Further, the lending processing unit 16 updates the expiration date of the record to the expiration date input from the card lending screen 83.

Then, the associating unit 17 associates the employee ID of this card DB 31 with the card ID of the renting card DB 32 and stores them in the associating DB 33.
Furthermore, the control unit 10 generates update data for updating the verification DB 52 of the gate system 4. There are two types of update data: target employee ID data and rented card ID data. One is data of the employee ID for which the card DB 31 has been updated, and is data for updating the validity flag of the verification DB 52 to “0” representing invalidity. The other is card ID data in which the lending card DB 32 has been updated, the validity flag of the verification DB 52 is updated to “1” indicating validity, the authority is updated to the authority of the target employee ID, This is data for updating the expiration date.

In S <b> 17, the control unit 10 transmits update data to the gate system 4. Then, the control part 10 complete | finishes this process.
In S18, the control unit 40 of the gate system 4 receives the update data.
In S19, the update unit 43 updates the collation DB 52 using the received update data. Thereafter, the control unit 40 ends this process.
In this way, the card management system 100 only identifies the book card 7a owned by the user P and inputs the card ID of the lending card 7r selected from the stocked by the reception operator. The lending card 7r can be used in the gate system 4 and the book card 7a owned can be disabled in the gate system 4.

Next, the inquiry process of the IC card 7 will be described. Using this inquiry process, the operator can know the usage status of the lent card 7r and the usage status of the book 7a owned by the user P. Further, the operator can perform further processing on these IC cards 7. FIG. 7 is a flowchart of card inquiry processing in the management apparatus 1 according to the first embodiment. FIG. 8 is a diagram illustrating a screen example at the time of card inquiry in the management device 1 according to the first embodiment.
In S30, for example, when the operator inputs a card ID from the card inquiry search screen 85 shown in FIG. 8A, the control unit 10 receives the card ID. Here, the card inquiry search screen 85 can be displayed, for example, when the operator selects a card inquiry from a card menu (not shown).
In S31, the control unit 10 searches the main card DB 31 and the lending card DB 32 to identify the record having the received card ID. If the record cannot be identified, the control unit 10 may output an error message to the card inquiry search screen 85 and prompt the user to input the card ID again.
In S32, the control unit 10 determines whether or not the specified record exists in the lending card DB 32. If it exists in the lending card DB 32 (S32: YES), the control unit 10 moves the process to S33. On the other hand, when it does not exist in the lending card DB 32 (S32: NO), the control unit 10 moves the process to S40.

In S <b> 33, the control unit 10 performs an editing process for the lending card inquiry screen 86. Specifically, the control unit 10 extracts the expiration date and status data from the record of the card ID of the lending card DB 32 and arranges it at a predetermined position of the display screen data on the lending card inquiry screen 86. .
In S <b> 34, the control unit 10 determines whether or not the card ID exists in the association DB 33. If the card ID is present in the association DB 33 (S34: YES), the control unit 10 moves the process to S35. On the other hand, when the card ID does not exist in the association DB 33 (S34: NO), the control unit 10 moves the process to S36.
In S <b> 35, the control unit 10 extracts employee information and status data from the main card DB 31 as information on the main card 7 a associated with the card ID.
In S36, the control unit 10 edits the data extracted in S35 to a predetermined position on the lending card inquiry screen 86. Then, the use state display unit 20 outputs a lending card inquiry screen 86 to the display unit 36. Then, the control part 10 complete | finishes this process.
FIG. 8 (2) shows a lending card inquiry screen 86. The employee information 86a and the lending card operation 86d are displayed when YES is selected in S34 of FIG. Further, in the card status 86c, when there is no information of the corresponding book card 7a, the card status of the book card 7a is blank.

On the other hand, in S <b> 40, the control unit 10 performs an editing process for the card inquiry screen 87. Specifically, the control unit 10 extracts employee information from the record of the employee ID in the card DB 31 and edits it to a predetermined position on the card inquiry screen 87.
In S <b> 41, the control unit 10 determines whether or not the card ID exists in the association DB 33. When the card ID exists in the association DB 33 (S41: YES), the control unit 10 moves the process to S42. On the other hand, when the card ID does not exist in the association DB 33 (S41: NO), the control unit 10 moves the process to S43.
In S42, the control unit 10 extracts status data from the lending card DB 32 as information on the lending card 7r associated with the card ID.
In S43, the control unit 10 edits the data extracted in S42 to a predetermined position on the card inquiry screen 87. Then, the control unit 10 outputs the card inquiry screen 87 to the display unit 36. Then, the control part 10 complete | finishes this process.
FIG. 8 (3) shows the card inquiry screen 87. In the card status 87c, when there is no information on the corresponding lending card 7r, the card status of the lending card 7r is blank.

  As described above, the management device 1 associates the real card 7a with the lending card 7r regardless of whether the received card ID is the real card 7a or the lending card 7r. In case, both card statuses are displayed. Therefore, the operator can grasp the card lending status from one inquiry screen.

  The lending card inquiry screen 86 output by this card inquiry process can be used, for example, when the rented lending card 7r is forgotten or lost. In this case, the operator selects the reason for the lending card operation 86d on the lending card inquiry screen 86 and selects the button 86b. By doing so, the control unit 10 changes the status of the lending card DB 32 to “pause”, deletes the record in the association DB 33, and releases the association. Since the lending card DB 32 has been changed, the control unit 10 generates update data and transmits the update data to the gate system 4. By doing in this way, the card management system 100 can make the loan card 7r lent out unusable in the gate system 4, and the security is improved. Further, since the association in the association DB 33 has been deleted, the card management system 100 can lend another lending card 7r to the user P again.

Next, processing when the user P passes through the gate system 4 using the lending card 7r on which lending processing has been performed will be described. FIG. 9 is a flowchart of gate processing in the gate system 4 according to the first embodiment.
In S50, the control unit 40 of the gate system 4 controls the reader 6a so that the card ID area 76 of the lending card 7r can be read, and requests a card ID.
In step S <b> 50 a, the user P holds the lending card 7 r to be carried close to (touches) the reader unit 60 of the gate system 4, whereby the CPU 70 of the lending card 7 r is stored in the card ID area 76. In S51, the control unit 40 of the gate system 4 controls the reader unit 60 to read the card ID in the card ID area 76 of the lending card 7r.
In S <b> 52, the control unit 40 specifies the gate ID of the gate 6 having the reader unit 60.
In S53, the control unit 40 (collation unit 41) collates the card ID stored in the read card ID area 76 with the collation DB 52. Specifically, it is verified whether or not the same card ID as the card ID stored in the card ID area 76 exists in the verification DB 52.

In S54, if the same card ID as the card ID read by the gate system 4 exists in the verification DB 52 as a result of the verification in S53 (S54: YES), the control unit 40 moves the process to S55. On the other hand, when the same card ID as the card ID read by the gate system 4 does not exist in the verification DB 52 (S54: NO), the control unit 40 ends this process without opening the gate 6.
In S55, the collation unit 41 determines whether or not a condition for permitting the opening of the gate 6 is satisfied. Specifically, the collation unit 41 indicates that the validity flag of the collation DB 52 matching the card ID is “1” indicating validity, that the expiration date is today's date or a date later than today's date, and that the authority is Then, it is confirmed that the authority of the corresponding gate ID in the gate DB 54 is higher than the authority, and it is determined whether or not a permitting condition is satisfied. If the permitting condition is satisfied (S55: YES), the control unit 40 moves the process to S56. On the other hand, when the conditions for permission are not satisfied (S55: NO), the control unit 40 ends the process without opening the door of the gate 6.

In S56, the operation permission unit 42 opens the door of the corresponding gate 6.
In S57, the control unit 40 determines whether passage has been detected or whether a predetermined time has elapsed. The gate system 4 includes a detection unit such as an optical sensor (not shown) in the gate 6 and can detect whether or not the user P has passed. If the passage is detected or a predetermined time has elapsed (S57: YES), the control unit 40 moves the process to S58. On the other hand, when the passage is not detected and the predetermined time has not elapsed (S57: NO), the control unit 40 remains in S57.
In S58, the control unit 40 closes the door of the corresponding gate 6. Thereafter, the control unit 40 of the gate system 4 ends this process.

In this way, the user P carries the lending card 7r that has been lending, and passes the lending card 7r over the gate 6 at each location, thereby passing through the gate 6 that satisfies the security level. it can. The collation DB 52 of the gate system 4 has the same card ID as that stored in the card ID area 76 of the lending card 7r in advance, the card ID is made valid, and the authority of the user P is Since it is the same as that stored in the main card DB 31, even when the lending card 7 r is used, the user P can use the lending card 7 r with the same feeling as when using the main card 7 a. Can be used.
In the state where the lending card 7r is lent to the user P, the valid flag remains “0” when the card ID of the verification DB 52 is the card 7a. Therefore, when the user P or a third party who illegally obtains the card 7a uses the card 7a for the gate system 4, the condition permitted in S55 is not satisfied and the gate 6 is not opened.

Next, the process at the time of use termination reception performed by the user P returning the rental card 7r to the reception will be described. FIG. 10 is a flowchart of the card return process in the card management system 100 according to the first embodiment. FIG. 11 is a diagram illustrating a screen example when the card is returned in the management device 1 according to the first embodiment.
In S60, the control unit 10 of the management device 1 displays a card return screen 88 as shown in FIG. The card return screen 88 can be displayed, for example, when the operator selects card return from a lending card menu (not shown).
In S61, the return accepting unit 21 inputs the card ID of the lending card 7r returned by the reception operator from the card return screen 88 and selects the button 88b, whereby the return receiving unit 21 returns the card of the returned lending card 7r. Accept ID.
In S62, the return processing unit 22 performs return processing of the lending card 7r.

As the return process, first, the return processing unit 22 updates the lending card DB 32. Specifically, the return processing unit 22 changes the status of the lending card DB 32 corresponding to the card ID acquired by the return receiving unit 21 from “in use” to “pause”. In addition, the return processing unit 22 sets the expiration date of the record to a blank.
Next, the return process part 22 updates this card DB31. Specifically, the return processing unit 22 refers to the association DB 33, and if there is a card ID record acquired by the return receiving unit 21, the status of the record of the card DB 31 having the corresponding employee ID is “ Change from “Paused (Forgot)” to “In Use”. However, if the status of the record in the card DB 31 is “stop (lost)” when it is lost, the status is not changed.
Then, the association deletion unit 23 updates the association DB 33. Specifically, the association deletion unit 23 deletes the record of the corresponding card ID stored in the association DB 33.

Furthermore, the control unit 10 generates update data for updating the verification DB 52 of the gate system 4. There are two types of update data: the data of the target employee ID and the data of the card ID of the lent out rental card 7r. One is data of the employee ID for which the card DB 31 has been updated, and is data for updating the validity flag of the verification DB 52 to “1” representing validity. If the status of the card DB 31 remains “stopped” and is not changed, employee ID data is not generated. The other is the data of the card ID that has been updated in the lending card DB 32. The authority of the verification DB 52 is set to “0”, the validity flag is set to “0”, and the expiration date is set to the minimum value. It is data to do.
In S <b> 63, the control unit 10 transmits update data to the gate system 4. Then, the control part 10 complete | finishes this process.
In S64, the control unit 40 of the gate system 4 receives the update data.
In S65, the update unit 43 updates the collation DB 52 using the received update data. Thereafter, the control unit 40 ends this process.

Thus, according to the first embodiment, there are the following effects.
(1) The card management system 100 can use the lending card 7r in the gate system 4 by specifying the card 7a owned by the user P and acquiring the card ID of the lending card 7r to lend. At the same time, the owned card 7 a is disabled in the gate system 4. Thus, for example, when the user P forgets the card 7a, the gate system 4 can be caused to perform a predetermined operation using the lending card 7r that has been lended.
In addition, the lending card 7r can be used in the gate system 4 and the main card 7a cannot be used, so that both the lending card 7r and the main card 7a can be used. Can be prevented and security is improved.
Furthermore, the card 7a owned by the user P can be automatically selected simply by specifying the card 7a and inputting the card ID of the lending card 7r selected from the stocked by the reception operator. Can be disabled. Therefore, the card management system 100 can perform the processing for the lending card 7r and the processing for the main card 7a in one operation, and the operation of the operator can be facilitated.

(2) The management device 1 can store the book card 7a processed by the lending processing unit 16 and the lending card 7r in association with each other in the association DB 33. Therefore, for example, information on the main card 7a of the user P who lent out the lending card 7r can be output on the lending card inquiry screen 86.
(3) Since the management device 1 displays the usage status of the lending card 7r, the reception operator can grasp the usage status of the lending card 7r. Further, the management device 1 displays the usage status of the book card 7a corresponding to the rented card 7r for comparison, so that the reception operator also sets the usage status of the card 7a. Can be grasped.

(4) Since the card management system 100 grants the authority of the card 7a to the lending card 7r in response to the processing by the lending processing unit 16, when the lending card 7r is used, this card It is possible to cause the gate system 4 to perform the same predetermined operation as that used for the gate system 4. Therefore, even if the user P forgets the main card 7a, the user can use the lending card 7r like the main card 7a, which is convenient.
(5) When the lending card 7r is returned, the card management system 100 disables the lending card 7r from being used in the gate system 4, and the card 7a corresponding to the lending card 7r is changed to the gate system 4 Can be used in Therefore, the card management system 100 can perform the processing for the lending card 7r and the processing for the main card 7a by one operation even when the lending card 7r is returned, and the operation of the operator is easy.
(6) When the lending card 7r is returned, the management device 1 deletes the association between the lending card 7r and the main card 7a from the association DB 33. Therefore, for example, it is possible not to output the information of the book card 7a that has been output during the lending to the lending card inquiry screen 86. Moreover, since the association is deleted, the management device 1 can lend the lending card 7r to another user.

(7) The management device 1 can change the processing of the card 7a so as to be suitable for the lending reason. For example, when the lending reason is damage of the book card 7a, the book card 7a has been discontinued, and can be left unusable when the lending card 7r is returned.
(8) The card management system 100 deletes, from the lending card 7r, the same authority as the main card 7a assigned to the lending card 7r in response to the processing by the return processing unit 22. Therefore, even if the lending card 7r is mistakenly used for the gate system 4 after the lending card 7r is returned, unauthorized processing can be prevented.
(9) The management device 1 stores the face photo data of the user P, and outputs the face photo data of the user P specified by the card specifying unit 12. Therefore, the reception operator can confirm the identity of the user P who lends the lending card 7r based on the face photo data. Accordingly, the lending card 7r can be lent after the identity is confirmed, and the security is improved.
(10) Since the card management system 100 has an expiration date in the verification DB 52, for example, when the rental card 7r is not returned from the user P, the card management system 100 uses the rental card 7r for the gate system 4. However, the gate 6 is not opened and security can be maintained.

(Second Embodiment)
In the second embodiment, a case will be described in which the user reissues the card because the card is damaged. In the following description, parts that perform the same functions as those in the first embodiment described above are given the same reference numerals or the same reference numerals at the end, and redundant descriptions are omitted as appropriate.
FIG. 12 is a diagram illustrating a functional configuration of the card management system 200 according to the second embodiment. FIG. 13 is a diagram illustrating an example of a database stored in each device according to the second embodiment.

The card management system 200 includes a management device 201, a gate system 204, and an IC card 207.
The management apparatus 201 includes a control unit 210 and a storage unit 230 in addition to the display unit 36, the operation unit 38, and the I / F unit 39.
The control unit 210 includes a main card receiving unit 11, a main card specifying unit 12, a confirmation data output unit 13, a reason receiving unit 14, a lending card acquisition unit 15, a lending processing unit 16, and an authority granting unit. 18, usage state display unit 20, return acceptance unit 21, return processing unit 22, association deletion unit 23, authority deletion unit 24, association unit 217, and card issuance request unit 219. Prepare.
The associating unit 217 is a control unit that associates the card ID of the lending card 207r processed by the lending processing unit 16, the card ID of the card 207a, and the number of issues. Further, when reissuing the main card 207a, the associating unit 217 associates the card ID and number of times of the newly issued main card 207a with the card ID of the lending card 207r.
The book card issuance request unit 219 is a control unit that requests the issuance of a new book card 207a when the book card 207a is lost or damaged. Although not shown, in the system that issues a card by the management device 201 transmitting the data in the management device 201 to the system that actually issues the card, a new request is issued by the card issue request unit 219. It is possible to issue a genuine book card 207a.

The storage unit 230 includes an association DB 233 in addition to the main card DB 31 and the lending card DB 32.
As shown in FIG. 13A, the association DB 233 has an issue count item added as compared to that in the first embodiment (see FIG. 3C). The association DB 233 is a database that stores the employee ID and the number of times of issuance and the card ID of the lending card 207r, which are card IDs of the card 207a associated by the association unit 217. The association DB 233 associates the card 207a with the lending card 207r including the number of times of issuance.

The gate system 204 includes a control unit 240 and a storage unit 250 in addition to the I / F unit 59 and the reader unit 60.
The control unit 240 includes a matching unit 241 in addition to the operation permission unit 42 and the update unit 43.
The collation unit 241 is a control unit that collates the card ID and the number of issuances of the card ID area 276 of the IC card 207 with the collation DB 252.
The storage unit 250 includes a matching DB 252 in addition to the gate DB 54.
As shown in FIG. 13B, the verification DB 252 has an issue count item added as compared to that of the first embodiment (see FIG. 4A). The issuance count is input when the accepted IC card 207 is the main card 207a. The number of times of issue is blank when the accepted IC card 207 is a lending card 207r.
There are two types of IC cards 207, a main card 207a and a lending card 207r. The IC card 207 includes a card ID area 276 in the storage unit 275.
The card ID area 276 stores the card ID and the number of times of issuance in the case of the card 207a. The card ID area 276 stores the card ID in the case of the lending card 207r.

Next, the reissue process of the card 207a will be described. FIG. 14 is a flowchart of the card reissue process in the card management system 200 according to the second embodiment. FIG. 15 is a diagram illustrating an example of a screen at the time of a card inquiry according to the second embodiment.
In S210 of FIG. 14, the control unit 210 of the management apparatus 201 displays the card inquiry screen 287 as shown in FIG. The processing until this card inquiry screen 287 is displayed is based on FIG. 7 of the first embodiment.

Here, the card inquiry screen 287 will be described. The card inquiry screen 287 displays data related to the user P who owns the card 207a and data of the card 207a. Further, when the lending card 207r is associated with the main card 207a, the main card inquiry screen 287 displays the usage status of the lending card 207r on the card status 287c.
The card inquiry screen 287 can set a retirement grace period. This retirement grace period is for enabling the use of the gate system 4 in consideration of the use of the gate system 4 for rearranging work even when the user P is no longer an employee due to retirement. . When the operator inputs the number of days during the retirement grace period and selects the button 287u, the card management system 200 allows the card 207a until the retirement grace period expires even if the user P is retired. Can be used in the gate system 4.

  Specifically, an expiration date item is provided in the card DB 31 (not shown). The expiration date of the card DB 31 is set to a retirement date for the employee ID of the retired user P by a personnel system (not shown). However, by setting and updating the retirement grace period, the control unit 210 of the management apparatus 201 sets the expiration date of the card DB 31 to be extended. And the control part 210 produces | generates the update data for updating the collation DB252 of the gate system 204 by this card DB31 being updated. The controller 210 automatically sets the status of the card DB 31 corresponding to the book card 207a whose retirement grace period has passed to “stop” by nighttime batch work or the like. Then, the control unit 210 generates update data that sets the valid flag of the target card ID in the verification DB 252 to “0”.

Returning to FIG. 14, in S211, the card issuance request unit 219 accepts card issuance. This is because the button 287b is selected by the operator on the card inquiry screen 287 in FIG. 15 (1), the issue reason 289a is selected on the issue reason input screen 289 in FIG. 15 (2), and then the button 289b is selected by the operator. Can be accepted by being selected.
The issuance reason input screen 289 in FIG. 15 (2) is for inputting a reason for issuance of a new book card 207a. The issuance reason 289a includes “update” in addition to “lost” due to the user P losing the card 207a and “breakage” in which the card 207a is broken. This “update” is used when the card 207a is issued periodically, for example, every five years. For example, the card management system 200 can periodically update the card 207a, such as when the card 207a has a face photo or for operational reasons. When “update” is selected as the issuance reason 289a, an update grace period 289c can be set. The setting of the update grace period 289c is for setting a time limit for using the card 207a owned by the user P.
This is to make it possible to use the book card 207a owned by the user P until the newly issued book card 207a reaches the user P. That is, on the card management system 200, the card 207 a owned by the user P is stored in the gate system 4 by performing this process until the newly issued book 207 a reaches the user P. It will be usable. If the update grace period 289c is not set, the card 207a owned by the user P cannot be used immediately.

Returning to FIG. 14, in S <b> 212, the control unit 210 performs the card issuing process.
Here, the card issuing process will be described for each case.
(A) When the lending card 207r is associated with the real card 207a owned by the user P (that is, the user P is using the lending card 207r), and the lending reason is “forget” (A) When the reason for issuance is “lost” or “damaged” (1) The card DB 31 update processing of the newly issued card 207a The control unit 210 increases the number of times of issuance by 1 and the other items are those of the user P. A record similar to the book card 207a owned is newly created in the book card DB 31, and the status is set to “pause”.
(2) Update processing of the book card DB 31 of the book card 207a owned by the user P The control unit 210 sets the status of the record of the book card 207a owned by the user P stored in the book card DB 31 to “stop” and issuance Add reason to status. And today's date is set to the expiration date of the record. With this update process, the operator will subsequently operate the newly issued card 207a.

(3) Update data generation process The control unit 210 generates update data. There are two types of update data: data corresponding to the newly issued book card 207a and data corresponding to the book card 207a owned by the user P.
The data corresponding to the newly issued card 207a is data for adding a record for enabling the newly issued card 207a to be used in the verification DB 52, but the valid flag is “0”. This is because only the lending card 207r being lent can be used in the gate system 4.
Data corresponding to the card 207a owned by the user P is data for updating the validity period of the verification DB 52 to the current date and setting the validity flag to “0”.
(4) Association DB 233 Update Processing The association unit 217 updates the association DB 233. Specifically, the associating unit 217 updates the number of issuance of the target employee ID in the association DB 233 to the number of issuance of newly created records in the card DB 31.

(B) When the reason for issuance is “update” (1) The card DB 31 update processing of the newly issued card 207a The control unit 210 increases the number of issuances by 1, and the other card is owned by the user P. A record similar to 207a is newly created in the card DB 31 and its status is set to “in use”.
(2) Book card DB31 update process of book card 207a owned by user P The control unit 210 sets an update grace period on the expiration date of the record of book card 207a owned by user P stored in the card DB 31. Set a date that takes into account. Note that the status of the record remains “pause”. When the expiration date expires, the control unit 210 sets the status to “stopped” by nighttime batch work or the like, so that it cannot be used in the gate system 204.

(3) Update data generation process The control unit 210 generates update data. There are two types of update data: data corresponding to the newly issued book card 207a and data corresponding to the book card 207a owned by the user P.
The data corresponding to the newly issued card 207a is data for adding a record for enabling the newly issued card 207a to the verification DB 52, and the valid flag is “1”.
Data corresponding to the card 207a owned by the user P is data for updating the validity period of the verification DB 52 and setting the validity flag to “1”.
The association DB 233 is not updated. That is, the lent card 207r being lent remains associated with the book card 207a owned by the user P. If the expiry date expires when the lent loan card 207r is lent, the newly issued book 207a is associated with the rented card 207r, and the status of the newly issued book 207a is set to “pause” "

(B) The lending card 207r is associated with the card 207a owned by the user P (that is, the user P is using the lending card 207r), and the lending reason is “lost” or “damaged”. In the case of "", the same processing as (a) of (A) described above is performed.

(C) When the lending card 207r is not associated with the book card 207a owned by the user P (that is, when the book card 207a owned by the user P is being used)
(1) Update processing of the main card DB 31 of the newly issued main card 207a The control unit 210 increases the number of times of issuance by 1 and records other items in the main card DB 31 that are the same as the main card 207a owned by the user P. Create a new one and set its status to “In Use”.
(2) Processing for updating the main card DB 31 of the main card 207a owned by the user P (2-a) When the reason for issuance is “lost” or “damaged” The control unit 210 stores the user P stored in the main card DB 31. The status of the record of the book 207a owned by the card is set to “stop”, and the reason for issuing is added to the status. And today's date is set to the expiration date of the record.
(2-b) When the reason for issuance is “update” The control unit 210 sets a date in consideration of the update grace period in the expiration date of the record of the card 207a owned by the user P stored in the card DB 31. To do. Note that the status of the record remains “in use”. When the expiration date expires, the control unit 210 sets the status to “stopped” by nighttime batch work or the like, so that it cannot be used in the gate system 204.

(3) Update data generation process The control unit 210 generates update data. There are two types of update data: data corresponding to the newly issued book card 207a and data corresponding to the book card 207a owned by the user P.
The data corresponding to the newly issued card 207a is data for adding a record for enabling the newly issued card 207a to the verification DB 52, and the valid flag is “1”.
The data corresponding to the card 207a owned by the user P is data for updating the validity period of the verification DB 52 and setting the validity flag to “0” when the reason for issuance is “lost” or “damaged”. is there.

In step S <b> 213, the control unit 210 transmits update data to the gate system 204. Thereafter, the control unit 210 ends this process.
In S214, the control unit 240 of the gate system 204 receives the update data.
In S215, the control unit 240 (update unit 43) updates the collation DB 252 using the received update data. Thereafter, the control unit 240 ends this process.

  Next, processing when passing through the gate system 4 using the IC card 207 will be described. This process is substantially the same as that in FIG. 9 of the first embodiment, but the verification process in S53 of FIG. 9 is different. In the collation process, the collation unit 241 collates the data stored in the read card ID area 76 with the collation DB 252. Specifically, it is collated whether or not the same card ID and number of issuances as those stored in the card ID area 276 exist in the collation DB 252. In the case of the lending card 207r, the card ID area 276 has only the card ID and does not have the number of issuances. Therefore, the collation unit 241 collates the card ID stored in the card ID area 276 with the card ID in the collation DB 252.

Thus, according to the second embodiment, there are the following effects.
(1) When this card 207a is newly issued by the management apparatus 201 and the book card 207a owned by the user P is associated with the lending card 207r, the card is owned by the user P The association with the book card 207a to be deleted can be deleted, and the newly issued book card 207a can be associated with the lending card 207r being lent. Therefore, even when the lending card 207r is being lent, it is possible to smoothly switch the card to the newly issued card 207a.
(2) When the management device 201 newly issues the card 207a and the card 207a owned by the user P and the lending card 207r are associated with each other, And request the issuance of the unusable book 207a. Therefore, for the user P, only one card can be used, and the security is improved.

  As mentioned above, although embodiment of this invention was described, this invention is not limited to embodiment mentioned above. In addition, the effects described in the embodiments are merely a list of the most preferable effects resulting from the present invention, and the effects of the present invention are not limited to those described in the embodiments. In addition, although embodiment mentioned above and the deformation | transformation form mentioned later can also be used combining suitably, detailed description is abbreviate | omitted.

(Deformation)
(1) In the first embodiment, if you forget or lose a loan card that is being loaned, you can enter the reason by operating the loan card from the loan card inquiry screen. Described as disabling the gate system and releasing the association with this card. However, by entering the card ID of the new lending card on the card lending screen and performing lending operation, the lending card that has been lending before and currently lending is disabled in the gate system, and this card It is also possible to cancel the association and associate the newly lent card with the lent card. By doing so, it is possible to further lend out a lending card when, for example, the forgotten lending card is further forgotten. And since the lending card lent previously is made unusable with respect to the apparatus, it is possible to prevent both of the two lending cards from being usable, and the security is improved.

(2) In each embodiment, it has been described that the card ID of the lending card is manually input by the reception operator when the card is lent or returned. However, a reader unit may be provided in the management device, and the control unit may read the card ID of the lending card via the reader unit. By doing so, the operator's work becomes easier and erroneous input can be prevented.
(3) In each embodiment, the gate has been described as an example of an apparatus for maintaining security using an IC card. However, the present invention is not limited to this. For example, it can also be used in a multifunction machine and a PC (personal computer).
(4) In each embodiment, the reader and the reader / writer have been described as being capable of non-contact communication with the IC card, but may be of a contact type.
(5) In each embodiment, the employee card is used as an example of the card. However, as long as the user can be identified, it is not limited to an employee ID card. In addition, a face photograph may be attached to this card.

(6) In each embodiment, the management device has been described as a configuration including a reception server and a reception terminal. However, the management apparatus may be configured by a single computer having functions of a reception server and a reception terminal, or may be configured by a plurality of reception servers and a plurality of reception terminals.
(7) In each embodiment, the gate system has been described as a configuration including a gate management server and a gate. However, for example, the gate system may be configured by a gate having the function of a gate management server, and a plurality of gates may be provided. Also, for example, a gate control device is arranged between the gate management server and the gate and in the vicinity of the gate, the gate control device has the data of the gate management server, and the gate control device and the gate communicate with each other. By doing so, the function of the gate system may be exhibited.
(8) In each embodiment, it has been described that data can be updated in real time between the management device and the gate system. However, the gate system may receive data in real time and update the data received from the management device at a predetermined time interval (for example, every 10 minutes). Alternatively, the gate system may periodically receive data and update the data received from the management device at a predetermined time interval (for example, every 10 minutes). In other words, it can be introduced according to the specifications of the existing system.

1,201 management device 4,204 gate system 6 gate 6a reader 7,207 IC card 7a, 207a book card 7b, 207b lending card 10,40,210,240 control unit 11 card accepting unit 12 card specifying unit 13 Confirmation data output unit 14 Reason reception unit 15 Lending card acquisition unit 16 Lending processing unit 17,217 Association unit 18 Authority granting unit 20 Usage status display unit 21 Return receiving unit 22 Return processing unit 23 Related deletion unit 24 Authority deletion unit 30 , 50, 75, 230, 250, 275 Storage unit 31 Card DB
32 Lending card DB
33,233 Association DB
36 Display unit 41, 241 Verification unit 42 Operation permission unit 43 Update unit 52, 252 Verification DB
54 Gate DB
60 Reader unit 70 CPU
76,276 Card ID area 100,200 Card management system 219 Card issuance request part P User Sa Security area

Claims (14)

A management device that manages an IC card for causing the device to perform a predetermined operation using the IC card,
The IC card includes a main card that is an IC card owned by a user and a lending card that is an IC card that can be lent to the user. The card is in an unusable state for the device, and the card is in an unusable state for the device;
A book card storage unit for storing book card information related to the book card and book card identification information for identifying the book card;
A lending card storage unit for storing card identification information for identifying the lending card;
A book accepting unit for accepting input of the book card information;
A book card specifying unit that searches the book card storage unit based on the book card information received by the book card receiving unit and identifies a user of the book card;
A lending card acquisition unit that acquires the card identification information corresponding to a lending card to be lent to the user from the lending card storage unit;
In response to the acquisition of the one card identification information by the lending card acquisition unit, the lending card having the one card identification information can be used for the device, and the book card specification A lending processing unit that performs processing for disabling the book having the book card identification information specified by the unit to the device;
Providing
Management device characterized by. The management device according to claim 1,
An association unit that associates the card identification information of the book card that has been processed by the lending processing unit with the card identification information of one of the lending cards;
Management device characterized by. The management device according to claim 1 or 2,
When displaying the usage state of the lending card stored in the lending card storage unit and displaying the usage state of the lending card having the one card identification information stored in the lending card storage unit Comprises a usage status display unit that displays the usage status of the card corresponding to the lending card in association with each other;
Management device characterized by. A management device according to any one of claims 1 to 3, wherein
An authority granting unit that grants the authority of the book card that defines the operation to be performed by the device by using the book card to the lending card in response to processing by the lending processing unit. ,
Management device characterized by. A management device according to any one of claims 1 to 4, wherein
A return accepting unit for accepting card identification information of the lending card at the time of use termination acceptance of the lending card;
In response to receiving the card identification information by the return receiving unit, the lending card corresponding to the card identification information is disabled for the device, and the book associated with the lending card is used. A return processing unit that performs processing for making the card usable for the device;
Providing
Management device characterized by. The management device according to claim 5,
An association deleting unit that deletes the association between the lending card and the book card associated with the lending card in response to the processing by the return processing unit;
Management device characterized by. The management device according to claim 5 or 6,
As a reason for lending, the card has a temporary stop and the use has been suspended,
A reason accepting unit for accepting selection of one of the plurality of lending reasons;
The return processing unit makes the card usable for the device when the one reason for lending received by the reason receiving unit is suspended, and when the use is suspended. Leaving the card unusable for the device;
Management device characterized by. A management device according to any one of claims 5 to 7,
An authority deleting unit that deletes the authority of the book from the lending card in response to the processing by the return processing unit;
Management device characterized by. A management device according to any one of claims 1 to 8,
The card storage unit stores the user's face photo data,
A data output unit for confirmation that outputs the face photo data of the user identified by the card identifying unit;
Management device characterized by. A management apparatus according to any one of claims 1 to 9, wherein
The lending card having the one card identification information is usable for the device at the time of start of use of the lending card having other card identification information different from the one card identification information. The lending card having the other card identification information is in an unusable state with respect to the device,
The lending card acquisition unit uses the other card identification information corresponding to the lending card to be lent to the user lending the lending card having the one card identification information for the lending. Obtained from the card storage,
The lending processing unit allows the lending card having the acquired other card identification information to be used for the device and the lending card having the one card identification information to the device. To make it unavailable,
Management device characterized by. A management apparatus according to any one of claims 1 to 9, wherein
The book card identification information identifies the user and has the number of times the book is issued.
A card issuing request section for requesting the issuing of the card;
A new book card of the user who has been requested by the book card issuance request unit to the user who rents a lending card having the one card identification information usable for the device. When issued, delete the association with the card identification information of the card associated with the card identification information of the card for lending, and newly issue the card identification information of the card for lending An associating unit for associating with the book identification information of the book
Providing
Management device characterized by. The management device according to claim 11,
The book card issuance request unit requests the device to issue a new book card that cannot be used when a lending card is associated with the book card of the user who made the request. To do,
Management device characterized by. A program that is executed by a management device that is a computer that manages an IC card for causing the device to perform a predetermined operation using the IC card,
The IC card includes a main card that is an IC card owned by a user and a lending card that is an IC card that can be lent to the user. The card is in an unusable state for the device, and the card is in an unusable state for the device;
The management device
A book card storage unit for storing book card information related to the book card and book card identification information for identifying the book card;
A lending card storage unit for storing card identification information for identifying the lending card;
With
The management device,
A card receiving means for receiving input of the card information;
Book card specifying means for searching the book card storage unit based on the book card information received by the book card receiving means to identify a user of the book card;
Lending card acquisition means for acquiring one card identification information corresponding to a lending card to be lent to the user from the lending card storage unit;
In response to the acquisition of the one card identification information by the lending card acquisition means, the lending card having the one card identification information can be used for the device, and the book card identification Lending processing means for performing processing for disabling the book card having the book card identification information specified by the means for the device;
Make it work,
A program characterized by A device that performs a predetermined operation using an IC card;
The IC card including a book card that is an IC card owned by a user and a lending card that is an IC card that can be lent to the user;
A management device for managing the IC card;
A card management system comprising:
At the start of use of the lending card, the lending card is in an unusable state for the device, and the card is in a usable state for the device,
The management device
A book card storage unit for storing book card information related to the book card and book card identification information for identifying the book card;
A lending card storage unit for storing card identification information for identifying the lending card;
A book accepting unit for accepting input of the book card information;
A book card specifying unit that searches the book card storage unit based on the book card information received by the book card receiving unit and identifies a user of the book card;
A lending card acquisition unit that acquires the card identification information corresponding to a lending card to be lent to the user from the lending card storage unit;
In response to the acquisition of the one card identification information by the lending card acquisition unit, the lending card having the one card identification information can be used for the device, and the book card specification A lending processing unit that performs processing for disabling the book having the book card identification information specified by the unit to the device;
Providing
A card management system characterized by

Images