JP4388500B2 - Locking / unlocking management system - Google Patents

Description

  The present invention relates to a locking / unlocking management system.

  As a locking / unlocking management system for locking / unlocking a locking device on condition that the authentication code transmitted from the portable device is authenticated on the locking device side, the one described in Patent Document 1 is known. In this conventional example, the locking device and the portable device share the locking / unlocking code in which the portable device number is assigned to the ID code unique to the portable device 1, and the locking / unlocking code of the portable device is authenticated by the locking device. Then, the locking device is operated for locking and unlocking.

In addition, a plurality of memories for storing the lock / unlock code of the portable device are prepared, and the lock / unlock code set with the shared authentication unit that controls the opening / closing of the common door of the apartment house is stored. The
JP 2004-3153 A

  However, in the above-described conventional example, in order to register the portable device in the shared unit controller, it is necessary to make each portable device recognize by following the same procedure as the registration to the lock device, which is troublesome. There is.

  The present invention has been made to solve the above drawbacks, and an object of the present invention is to provide a locking / unlocking management system in which a registration operation to a common authentication unit is simple by a simple operation.

According to the present invention, the object is
A portable device 1 capable of automatically outputting an ID code (Cid) by receiving a predetermined communication request code (Creq);
A lock device 3 that is installed in each dwelling unit of the apartment house and is operated to be unlocked on the condition that the ID code (Cid) output from the portable device 1 matches the registered value in the lock-side control unit 2;
A common part controller 6 for operating the common service part 5 of the housing complex on the condition that the portable device 1 is authenticated by the common side control part 4;
When the portable device 1 is registered, the lock side control unit 2 generates a common code (Ccom) and a common code (Ccom) generated based on one ID code (Cid) of the portable devices 1 to be registered. A code including a classification code (Csub) capable of classifying the subordinate mobile devices 1 is stored in each mobile device 1 as a communication request code (Creq).
The shared-side control unit 4 uses the lock-side control unit 2 for the ID code (Cid) output from the portable device 1 that is used as a reference for generating the common code (Ccom) when the authentication of the portable device 1 is set. Achieved by applying a code generation rule to generate a communication request code (Creq), automatically searching for the corresponding portable device 1, and providing a lock / unlock management system that sequentially registers the searched portable device 1 as the authentication target portable device 1. Is done.

  The locking / unlocking management system includes a shared unit controller 6 in addition to the locking device 3 installed in each dwelling unit. The lock device 3 is equipped with a lock side control unit 2, and it is determined whether or not the ID code (Cid) transmitted from the portable device 1 matches that registered in advance, and the locking / unlocking operation is performed. .

  The common unit controller 6 is mainly installed in a common unit such as an entrance hall of an apartment house, and controls operations of the common service unit 5 such as opening / closing of a common door, accommodation guidance for a delivery box, and unlocking. The shared side controller 6 is equipped with the shared side control unit 4, and drives the shared service unit 5 when the shared side control unit 4 authenticates the portable device 1.

  The portable device 1 stores an ID code (Cid) unique to the portable device 1 and a communication request code (Creq). The ID code (Cid) is stored in the lock side control unit 2 and the shared side control unit 4. Can be sent from the portable device 1 at a desired timing, for example, by pressing the transmission button provided on the portable device 1 or the lock device 3 or the like. In addition, when the portable device 1 receives the same communication request code (Creq) as the stored communication request code (Creq), the portable device 1 automatically transmits the ID code (Cid).

  The communication request code (Creq) of the portable device 1 is generated in the lock side control unit 2 when the portable device 1 is registered in the lock side control unit 2, and has a common code (Ccom) and a classification code (Csub). Configured. When registering the portable device 1, the lock side control unit 2 generates a common code (Ccom) by using, for example, the ID code (Cid) of the portable device 1 that is first registered, and thereafter the portable device that is to be registered. A classification code (Csub) is sequentially assigned to the machine 1 to obtain a communication request code (Creq). The common code (Ccom) may be the ID code (Cid) itself of the portable device 1 from which the common code (Ccom) is acquired. Further, an appropriate function is applied to the ID code (Cid). The data length may be shortened to reduce the load on the processing system.

  As for the classification code (Csub) of the portable device 1, an appropriate code system can be used as long as the classification between the portable devices 1 sharing the common code (Ccom) is possible. If a set in which the subsequent value can be obtained by sequentially applying a predetermined bit operation to the previous value is used, the sorting and searching process of the portable device 1 is lightened.

  In order to receive the service in the shared service unit 5, it is necessary to establish authentication of the portable device 1 in the shared side control unit 4 mounted on the shared unit controller 6, and in the portable device registration mode in the shared side control unit 4 When the shared control unit 4 receives the ID code (Cid) from the portable device 1 from which the common code (Ccom) is extracted, the communication request code (Creq) is generated based on the ID code (Cid). The communication request code (Creq) generated in the shared-side control unit 4 is guaranteed to match the code system generated in the lock-side control unit 2 by matching the generation rules with those in the lock-side control unit 2. The

  As described above, the shared-side control unit 4 assigns different classification codes (Csub) sequentially to the common code (Ccom) to generate and output a communication request code (Creq). As described above, since the portable device 1 is configured to output the ID code (Cid) upon reception of the predetermined communication request code (Creq), the communication request code (Creq) is received from the shared-side control unit 4. Just by outputting, the portable device 1 storing the same communication request code (Creq) can be searched. When the ID code (Cid) is transmitted from the portable device 1, the portable device 1 is authenticated. Register as the target portable device 1.

  As a result, the portable device 1 that has been authenticated and registered on the lock device 3 side is held in a communicable range with the shared-side control unit 4, and the shared-side control unit 4 is accessed from the portable device 1 that has become the reference for the common code (Ccom). By simply doing, a plurality of portable devices 1 having the same common code (Ccom) can be registered in the shared-side control unit 4.

  According to the present invention, since the portable device can be registered at the same time when registering with the shared control unit, the registration operation can be simplified.

  1 and 2 show an embodiment of the present invention installed in an apartment house such as an apartment. In this embodiment, the locking / unlocking management system includes a lock device 3 installed in each dwelling unit of a housing complex, a common unit controller 6 installed in a common unit such as an entrance, the lock device 3, and a common unit controller. 6 and a portable device 1 capable of communicating with each other via an antenna.

  As shown in FIG. 1, the locking device 3 has an electric lock 3a that is fixed to the door of each dwelling unit and locks and unlocks the door, and a lock-side control unit 2 that controls the driving of the electric lock 3a. Then, communication with the portable device 1 side is performed, and the unlocking operation is performed. First, the lock side control unit 2 includes a button detection unit 2c, a lock / unlock signal generation unit 2d, a transmission / reception unit 2e, a bus line 2b connected to a CPU (2a) operated by a program described in a ROM (not shown). It is formed by connecting the communication request code generation unit 2f and the authentication unit 2g. Each component of the lock side control unit 2 may be temporarily or permanently constructed by the CPU (2a) in the memory space of the system memory (not shown), or formed by appropriate circuit components. It may be a circuit network.

  On the other hand, as shown in FIG. 2, the portable device 1 is formed by connecting a code storage means 1b, an antenna 1c, an unlocking operation button 1d, and a locking operation button 1e to the control unit 1a.

  During normal operation, the locking / unlocking operation is performed by pressing the unlocking operation button 3b or the locking operation button 3c of the locking device 3 arranged at a position where the operation from the outdoor side of the locking device 3 can be performed. When any one of these buttons 3b and 3c is pressed, the button detection unit 2c outputs a button press detection signal including information indicating the press button type to the CPU (2a). When the CPU (2a) receives the button pressing signal, it retrieves the communication request code (Creq) stored in the code storage means 3d, adds the code type data (Ccl) based on the pressed button type, and uses it as an unlocking / unlocking request code. It outputs to the transmission / reception part 2e.

  As shown in FIG. 3A, the communication request code (Creq) is composed of a common code (Ccom) and a classification code (Csub). As will be described later, at the time of authentication registration in the lock device 3 of the portable device 1 Assigned from the locking device 3 side. In this embodiment, the common code (Ccom) has a data length of 12 bits and the classification code (Csub) has a data length of 4 bits. Also, the output locking / unlocking request code is used for “for locking / unlocking response”, “for response at registration”, and “for response request”, and these types are code types (Ccl) having a data length of 4 bits. Sorted.

  As described above, when the locking / unlocking request code with the tag for locking / unlocking response is output from the antenna 3e of the locking device 3 and the portable device 1 receives the code, the control unit 1a of the portable device 1 reads from the code storage unit 1b. The communication request code (Creq) is extracted and compared with the communication request code (Creq) of the received lock / unlock request code. When the communication request code (Creq) matches, the control unit 1a generates an authentication code based on the ID code (Cid) extracted from the code storage unit 1b and outputs it from the antenna 1c. As shown in FIG. 3B, the authentication code is obtained by adding the above-described code type (Ccl) to the ID code (Cid) unique to the portable device (having a 32-bit data length in this embodiment). Composed.

  By outputting the locking / unlocking request code from the locking device 3 during the locking / unlocking operation, it is possible to limit the portable device 1 that communicates with the locking device 3 side, so that interference can be effectively prevented.

  When the lock device 3 receives the authentication code from the portable device 1 in response to the above-described locking / unlocking request code, the authentication unit 2g of the lock side control unit 2 takes out the registered ID code (Cid) from the code storage means 3d. The authentication unit 2g compares the ID code (Cid) in the authentication code.

  When the authentication code match is confirmed and authentication of the portable device 1 is established, the CPU (2a) causes the locking / unlocking signal generation unit 2d to generate a locking or unlocking drive signal, and the electric lock 3a in a predetermined direction. To drive. If the authentication by the authentication unit 2g is not established, the drive signal is not generated, and thus the electric lock 3a is not locked / unlocked.

  In the above description, the case where the locking / unlocking operation is performed by pressing the button on the locking device 3 side has been described, but the locking / unlocking operation can also be performed by pressing the buttons 1d, 1e on the portable device 1 side. When the lock / unlock buttons 1d and 1e of the portable device 1 are pressed, the portable device 1 transmits an authentication code, and the lock-side control unit 2 that has received the code extracts the ID code (Cid) from the authentication code. The electric lock 3a is operated in the same procedure as described above.

  Next, the registration procedure to the lock device 3 of the portable device 1 in the initial operation will be described. First, as shown in FIG. 4, when the initial setting (step S100) is completed, the control unit 1a of the portable device 1 transitions to a request code standby mode (step S101). When the request code is received in step S101, it is determined whether or not it is a locking / unlocking request code based on the code type or the code length (step S102). In the case of the locking / unlocking request code, the communication request code (Creq) further matches. Whether or not to do so is determined (step S103), and if they match, an authentication code is transmitted (step S104).

  The above control from step S101 to S104 corresponds to the authentication control in the lock device 3 described above. If the received request code is not the locking / unlocking request code in step S102, the process proceeds to the registration step after step S104. . In the registration step, first, it is confirmed that the request code is a registration request code (step S104). The registration request code is generated by the lock-side control unit 2 and transmitted to the portable device 1 when the lock-side control unit 2 registers the portable device 1. As shown in FIG. It has a data structure in which a communication request code (Creq) and a code type are added to the code (Cid).

  When the portable device 1 receives this registration request code, it extracts the ID code (Cid) from the code and compares it with its own ID code (Cid) (step S105), and then communicates with the code storage means. The request code (Creq) is stored (step S106). When step S106 is completed, the portable device 1 outputs an authentication code for registration confirmation (step S107).

  Next, the operation of the lock control unit 2 will be described based on the flowchart shown in FIG. In the lock side control unit 2, the initial setting is completed (step S201), the mode is checked (step S202), and when the mode is not the registration mode, the unlocking / unlocking operation using the portable device 1 as the normal operation mode as described above. Is done. Switching between the registration mode and the normal operation mode is performed by a changeover switch (not shown) arranged in the locking device 3.

  On the other hand, when the lock device 3 is in the registration mode and the transmission / reception unit 2e receives the authentication code from the portable device 1 (step S203), that is, after the changeover switch is switched to the registration mode, the button of the portable device 1 is displayed. When the authentication code is transmitted by pressing (see FIG. 6A), an error check repetitive routine is executed (steps S204, 205, and 206). If there is no error in the routine, first, it is determined whether or not it is the first registration target portable device 1 (step S207). In the case of the first portable device 1, the ID code (Cid) of this portable device 1 is also included. The communication request code generation unit 2f generates a common code (Ccom) of the communication request code (Creq), and adds a classification code (Csub) to the communication request code (Creq) (step S208). In this embodiment, the common code (Ccom) is generated by extracting the first 12 bits of the ID code (Cid), and the registration order is assigned as a classification code (Csub).

  Thereafter, the lock side control unit 2 generates a registration request code by adding the ID code (Cid) and the code type (Ccl) of the portable device 1 to the communication request code (Creq), and outputs the registration request code (step S209). (See FIG. 6 (a)). For the second and subsequent portable devices 1, the common code (Ccom), that is, the code related to the first ID code (Cid) is the same and only the classification code (Csub) is incremented. Sent as a registration request code.

  As described above, the registration request code is output for registration of the communication request code (Creq) to the portable device 1, and the lock-side control unit 2 transmits the registration request code to the portable device 1 side. The authentication code wait loop in the control step (S107) is executed (steps S210, 211, 212). When the response from the portable device 1 (authentication code transmission) matches within a predetermined time, the authentication code and the common code (Ccom) are stored in the code storage means 3d, and the registration for the portable device 1 is completed. (Step S213). Thereafter, if the locking device 3 is in the registration mode (step S214), the above-described procedure is repeated, and if not in the registration mode, the process is terminated (step S215).

  On the other hand, if there is no response from the portable device 1 within a predetermined time in the wait loop, an error processing routine is executed (steps 216 and 217).

  On the other hand, as shown in FIG. 7, the shared unit controller 6 includes a shared side control unit 4 that drives the shared service unit 5, a mode change switch 6a, and a code storage unit 6b. The shared-side control unit 4 is formed by connecting an authentication unit 4c, a transmission / reception unit 4d, a communication request code generation unit 4e, a switch detection unit 4f, and a shared service driving unit 4g to a bus line 4b to which a CPU (4a) is connected. In the normal operation mode, the authentication code from the portable device 1 is authenticated by the authentication unit 4c, and the shared service driving unit 4g is driven based on the result as in the case of the lock device 3 described above.

  FIG. 8 shows a procedure for authentication registration of the portable device 1 to the shared-side control unit 4. At the time of registration, first, the shared-side control unit 4 is initialized (step S301), and when the switch detection unit 4f connected to the mode change switch 6a is not in the registration mode (step S302), it operates as a normal operation mode. (Step S303).

  On the other hand, when the registration mode is detected in step S302, a waiting loop for transmitting the authentication code from the portable device 1 is executed (steps S304, 305, and 306). When the authentication code is received in step S305, that is, when the common control unit 4 is set to the registration mode and the registration by the lock control unit 2 is performed, the lock / unlock button of the portable device 1 that is the target for acquiring the common code (Ccom) When the authentication code is transmitted by pressing 1d and 1e (see FIG. 6B), the communication request code generation unit 4e of the shared-side control unit 4 generates a common code (Ccom) from the authentication code ( Step S307).

  The common code (Ccom) is generated by the same method as the generation method in the lock device 3, and the first 12 bits of the acquired authentication code are extracted. As a result, the common code (Ccom) generated in step S307 matches the common code (Ccom) of the portable device 1 to be registered, and the common code (Ccom) is divided into a classification code (Csub) and a code type (Ccl). ) Is added and a lock / unlock request code is generated and sent (step S308).

  As shown in FIG. 4, the portable device 1 that has received the locking / unlocking request code confirms the match of the communication request code (Creq) (step S103), and if the communication partner is designated as the own device, the authentication code Is transmitted (step S104). After transmitting the locking / unlocking request code, the shared-side control unit 4 waits for transmission of this authentication code from the portable device 1 (step S309), and when receiving the authentication code, the shared-side control unit 4 stores the authentication code in the temporary storage area of the code storage means. The authentication code for the portable device 1 is stored (step S310).

  When the reception of the authentication code is confirmed, the unlocking request code is generated by adding to the common code (Ccom) while incrementing the classification code (Csub) in the same manner, and then sequentially transmitted from the portable device 1. An authentication code is acquired and temporarily stored in the code storage means (steps S311 to S316). If no authentication code is returned in the storage procedure, the classification code (Csub) is incremented and the search is further continued.

  As described above, the second and subsequent portable devices 1 are automatically searched by the shared-side control unit 4 without any operation and automatically registered as the authentication-target portable device 1. The quantity of the portable device 1 to be registered is input by the user before the registration operation, and when the registered number reaches this set value, the received portable device 1 is displayed on the display (step S317).

  If the registration mode is still maintained in this state (step S318), a confirmation message for the completion of registration work is displayed on the display (step S319), and then the authentication code of the portable device 1 stored in the temporary storage area is displayed. Are registered in the code storage means (step S320).

  If the registration mode is not set in step S318, that is, if the user changes the mode change switch to the normal operation mode during the registration of the portable device 1, the stored content in the temporary storage area is cleared (step S321). Return to the initial state.

It is a functional block diagram which shows a locking device. It is a functional block diagram which shows a portable device. It is a figure which shows the structure of various codes. It is a flowchart which shows operation | movement of a portable device. It is an operation | movement flow of the lock | rock side control part in portable device registration mode. It is a figure which shows the communication procedure with a portable machine, (a) is a figure which shows communication with a portable machine and a locking device, (b) is a portable machine and a common use controller. It is a functional block diagram which shows a shared part controller. It is an operation | movement flow of the sharing side control part in portable device registration mode.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Mobile device 2 Lock side control part 3 Locking device 4 Shared side control part 5 Shared service part 6 Shared part controller Creq Communication request code Cid ID code Ccom Common code Csub Classification code

Claims (2)

A portable device capable of automatically outputting an ID code upon receipt of a predetermined communication request code;
A lock device that is installed in each dwelling unit of the apartment house and is operated to be unlocked on the condition that the ID code output from the portable device matches the registered value in the lock side control unit;
A common unit controller that operates the shared service unit of the apartment house on the condition that the portable device authentication in the common side control unit,
The lock-side control unit includes a common code generated based on an ID code of one of the portable devices to be registered and a classification code that can separate portable devices under the common code when registering the portable device. Store the code as a communication request code in each portable device,
The shared-side control unit applies a code generation rule in the lock-side control unit to an ID code output from a portable device that is used as a reference for generating a common code at the time of authentication setting of the portable device. Lock / unlock management system that automatically searches for the corresponding mobile device and sequentially registers the search mobile device as the authentication target mobile device. The communication request code is
The locking / unlocking management system according to claim 1, wherein the locking / unlocking management system is used as an authentication start code in the lock-side control unit and the shared-side control unit.

Images