The present invention relates to lock systems, and more particularly to controllers and keys for such lock systems.
Certain door locks include a latch or bolt engageable with a frame to prevent relative displacement between the latch and frame. Typically, a do or having such a lock includes interior and exterior handles that are each rotated, pushed or otherwise displaced so as to disengage the latch from the frame to enable the door to be opened. Often, such door locks are provided with a device for preventing disengagement of the latch, for example by preventing movement of one or both handles. Some of these locks include electronic systems for preventing latch disengagement, such as by providing a clutch or other device that enables one or both handles to be disengaged from operative connection with the latch/bolt. Other types of locks include an electromagnet mounted on a door or frame that magnetically engages with a steel plate or another magnet on the other one of the frame or door, so as to secure the door within the frame by magnet force.
Often, each of the above types of locks include a controller that operates the clutching device, relay, or other device for locking/unlocking the dour, and a key device (e.g., fob, swipe card, iButton, etc.) for initiating authorized operation of the controller. Generally, such controllers include a stored list of authorized user values or a predefined access value, and the key device includes a code with one authorized user value or the lock access value. However, with either the code system, the ability to provide numerous individual users with different access privileges within a single system containing many doors, and thus locks and associated controllers, has often been found generally unsatisfactory.
In one aspect, the present invention is an access control system for at least one structure having at least first and second doors, each door having a lock adjustable between a locked state and an unlocked state. The control system comprises a key with a code, the code including at least a first segment and a second segment. A first controller is operatively coupled with the first door lock and has a memory with a stored value. The controller is configured to receive the code from the key, to compare at least the first value segment with the stored value, and to adjust the first door lock to the unlocked state when the controller determines that the code first segment corresponds with the first controller value. Further, a second controller is operatively coupled with the second door lock and has a memory with a stored value. The second controller is configured to receive the code from the key, to compare at least the code second segment with the second controller stored value, and to adjust the second door lock to the unlocked state when the second controller determines one of that the code second segment corresponds with the second controller value and that the code first segment corresponds with a first portion of the second controller value and the code second segment corresponds with a second portion of the second controller value.
In another aspect, the present invention is an access control system for at least one structure having at least one door, the door having a lock adjustable between a locked state and an unlocked state. The control system comprises at least one key having a code, the code including at least one access segment, an identifier segment, and an expiration date segment. A controller is operatively coupled with the door lock and has a memory with a stored access value and a void file, the void file being configured to store at least one void value with an identifier portion and an expiration date portion. The controller is configured to receive the code from the key, to compare the key access segment with the stored access value and the identifier segment with the identifier portion of each void file value. The controller is further configured to separately remove each one of the void values from the void file at least one of on or after the expiration date of the void value and when the void file includes a predetermined maximum number of void values and the one void value has an expiration date earlier than the expiration date of each one of the other void values.
In a further aspect, the present invention is an access control system for use with at least two doors, each door having a lock adjustable between a locked state and an unlocked state. The control system comprises a key having a first code and a second code and a first controller operatively coupled with the lock of a first one of the two doors and having a memory with a stored value. The controller is configured to receive the first and second codes from the key, to select one of first and second codes, to compare the selected code with the stored value, and to adjust the first door lock to the unlocked state when the controller determines that the selected code corresponds with the first controller stored value. Further, a second controller is operatively coupled with the lock of a second one of the two doors and has a memory with a stored value. The second controller is configured to receive the first and second codes from the key, to select one of first and second codes, to compare the selected code with the second controller stored value, and to adjust the second door lock to the unlocked state when the second controller determines that the selected code corresponds with the second controller stored value.
The foregoing summary, as well as the detailed description of the preferred embodiments of the present invention, will be better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there is shown in the drawings, which are diagrammatic, embodiments that are presently preferred. It should be understood, however, that the present invention is not limited to the precise arrangements and instrumentalities shown. In the drawings:
Referring now to the drawings in detail, wherein like numbers are used to indicate like elements throughout, there is shown in
The access control system 10 basically comprises at least one and preferably a plurality of keys 14, at least one first controller 16 operatively coupled with one first door D1 and at least one second controller 18 operatively coupled with one second door D2. Each key 14 has a code CK including at least a first segment SC1 and a second segment SC2, and may include any desired number of code segments SCn, (e.g., a third segment SC3, etc.) as described in greater detail below. Preferably, at least one key 14 is a first key 15A and the control system 10 further comprises at least one and preferably a plurality of other keys 14, such as a second key 15B, a third key 15C, etc., which each provide different access privileges to the one or more doors D1, D2, D3, etc., through which access is monitored or regulated by control system 10 of the present invention, as described below.
Further, each first lock controller 16 has a memory 17 with a stored access value VA1, which preferably corresponds with one or more characters representing one or more attributes or characteristics of the specific door D1 to which the particular lock L1 is coupled. The first lock controller 16 is configured (i.e., programmed, provided with appropriate software, hard-wired, etc.) to receive the code CK from each key 14 and to compare at least the code first segment SC1 with the stored access value VA1, and may compare two or more code segments SC1, Sc2, etc., with the access value VA1. The lock controller(s) 16 are each configured to adjust the coupled first door lock L1 to the unlocked state when the controller 16 determines that the code first segment SC1 “corresponds with” the first controller access value VA1, or alternatively that both the code first and second segments SC1, SC1 each correspond with a separate portion PV11, PV12 of the access value VA1, as discussed below. Furthermore, each second controller 18 has a memory 19 with a stored access value VA2, which includes one or more characters representing certain attributes of the particular second door D2. The second lock controller(s) 18 are configured to receive the code CK from each key 14 and to compare at least the code second segment SC2 with the stored access value VA2, and may compare two or more code segments SC1, SC2, etc., with the access value VA2. Preferably, each controller memory 17, 19 is programmable such that the access values VA1, VA2 are variable or adjustable, as discussed below.
Further, the second lock controller(s) 18 are each configured to adjust the coupled second door lock L2 to the unlocked state when the controller 18 determines that the code second segment SC2 corresponds with the second access value VA2, or alternatively that both the code first and second segments SC1, SC2 each correspond with separate portion PV21, PV22, respectively, of the access value VA2, as described in greater detail below. However, if the first controller 16 is configured to require both key code segments SC1, SC2 to correspond with each portion of the first stored access value VA1, either the second controller 18 should require only the code second segment SC2 to correspond with the stored access value VA2, or the criteria for determining “correspondence” (discussed in detail below) should be different than the correspondence criteria of the first controller 16, for the following reasons. Further, although the controllers are designated as first controller(s) 16 and second controller(s) 18, the first and second controllers 16, 18 (and other controllers, as discussed below) are preferably generally identically constructed (i.e., same type of microprocessor, etc.) and differ primarily by having different access values VA1, VA2 and/or different methodology for determining correspondence between the code(s) CK and particular value VA1 or VA2, as described in detail below.
By constructing the access control system 10 such that each lock controller 16, 18 has different access values VA1, VA2, or has different criteria for determining correspondence, the access system 10 may be designed to provide different users with different privileges to access the various doors D1, D2, etc., of the system 10. More specifically, as mentioned above, the access control system 10 is preferably used with a plurality of the keys 15A, 15B, etc., each assigned to a different user and having at least one code CK with code segments SC1, SC2, etc., that are different than the segments SC1, SC2, of each other key 15A, 15B, etc. As such, one key (e.g. 15A) may provide the assigned user with access through both the first and second doors D1, D2, while another key (e.g., 15B) may permit the assigned user to access only one of the two doors D1 or D2.
For example, an access control system 10 may be constructed with first and second keys 15A, 15B each having a code CK with two segments SC1, SC2, each segment SC1, SC2 including two characters, and with the first and second controller access values VA1, VA2 each including four characters, as follows:
With this exemplary system 10, when either the first and second keys 15A, 15B are used to access the first door D1, the first controller 16 may compare each key first segment SC11, SC21 with the access value first portion PV11, determine that each key code CK1, CK2 corresponds with the first access value VA1, and adjust the coupled first lock LI to the unlocked state. Further, when the first key 15A is used to access the second door D2, the second lock controller 18 may compare each of the key first and second segments SC11, SC12 with the second access value VA2, determine that the first segment SC11 corresponds with a first value portion PV21 and the second segment SC12 corresponds with a second value portion PV22, and then adjusts the coupled door lock L2 to the unlocked state. However, when the second key 15B is used to access the second door D2, the second lock controller 18 may compare each of the key first and second segments SC21, SC22 with the second access value VA2, determine that the code first segment SC21 corresponds with the first value portion PV21, but that the code second segment SC22 does not correspond with the second value portion PV22 (i.e., 00≠1). As such, the second controller 18 will not adjust the coupled door lock L2 to the unlocked state (i.e., the door D2 remains “locked”) when the second key 15A is used to access the second door D2. Alternatively, the second lock controller 18 may be configured to compare only the code second segment SC12, SC22 of each key 15A, 15B with the access value second portion PV22, or compare each code CK1, CK2 as an entire string to the entire second access value VA2, and achieve the same result.
Thus, the exemplary control system 10 is arranged to provide two users with privilege to access a first door D1 (e.g., a building exterior door), but only the first user has the privilege to access the second door D2 (e.g., a building interior door). The previous example is used to illustrate certain basic features of the access control system 10 of the present invention, and additional, more detailed examples are presented below.
Furthermore, as mentioned above, each of the key codes CK may have three or more code segments SC1, SC2, SC3, SC4, etc., and either or both controllers 16, 18 may be configured to further compare the third segment SC3, the fourth segment SC4, etc., with the particular stored access value VA1 or VA2. For example, the control system 10 may have a key(s) 14 having a code CK with three segments SC1, SC2, SC3 and with one or both controllers 16 or 18 configured to compare the third segment CS3 with the controller stored value VA1 or VA2. The controller(s) 16 may further be configured to adjust the associated lock L1, L2 to the unlocked state when the code third segment SC3 corresponds with a portion of the access value VA1, VA2 (or the entire value VA1, VA2), when the third segment SC3 corresponds with a portion (e.g., PV3) of the access value VA1, VA2 and at least one of first and second segments SC1, SC2 corresponds with another portion (e.g., PV1, PV2) of the stored value VA1, VA2, or that all three code segments SC1, SC2, SC3 correspond with a separate one of three access value portions PV1, PV2, PV3, respectively. Such a code comparison scheme may be extended to any number of code segments SC1, SC2, SC3, . . . SCn, and/or access value portions PV1, PV2, PV3, . . . PV1.
Additionally, the access control system 10 may include one or more third controllers 20, fourth controllers 22, etc., each coupled with the lock L3, L4, etc., of a respective third door D3, fourth door D4, etc., each having a different access value VA3, VA4 and requiring different criteria for enabling access through the associated door D3, D4. For example, the access control system 10 may have one or more keys 14 having a code CK with three segments SC1, SC2 and SC3 and any number of first, second, and third controllers 16, 18, 20, respectively, controlling access through associated doors D1, D2, D3. With such a system 10, the first and second controllers 16, 18 may be configured as described above, and the third controller(s) 20 may be configured to compare at least the third segment SC3 with the third access value VA3 stored in a memory 21, and to adjust the coupled door lock L3 to the unlocked state when the controller 20 determines one of the following: that the third segment SC3 corresponds with the third access value VA3, that the first and third segments SC1, Sc3 or second and third segments SC2, SC3, correspond with separate one of two access value portions PV1, PV2, or that all three code segments SC1, SC2, SC3 correspond with a separate one of three access value portions PV1, PV2, PV3. Thus, the capability of using three or more different controllers 16, 18, 20, etc., further expands the capability of the access control system 10 to provide different access privileges to different users, as discussed above and in greater detail below.
Besides the capability of having specific key codes CK with any desired number of code segments SCn, the access control system 10 may also include one or more keys 14 each having two or more different codes CKn, such as for example, a first code C1K and a second code C2K. With such a control system 10, the first and second controllers 16, 18 may each be configured to receive both the first and second codes C1K, C2K and to select the first code C2K for comparison with the particular access value VA1 or VA2, as discussed above. A third controller 20 (and possibly also a fourth controller 22, etc.) may be configured to receive both the first and second codes C1K, C2K from the same key 14, to select and compare the second code C2K with a third access value VA3, and to adjust a third door lock L3 to an unlocked state when the third controller 20 determines that at least a portion of the second code C2K corresponds with at least a portion of the third access value VA3. The access control system 10 can have keys 14 with any desired number of codes CnK and any desired number of different controllers 16, 18, 20, 22, etc., each selectively utilizing different codes CnK to determine authorized access through the associated door D1, D2, D3, etc. Thus, by providing multiple codes C1K, C2K, C3K, etc., on a single key 14, the flexibility of the access control system 10 is even further increased.
Preferably, each lock controller 16, 18, 20, etc., is configured to determine that one of the code segment SC1, SC2, SC3, etc., corresponds with the controller access value VAn (or a portion thereof) under at least one of the following (or other) conditions:
In other words, each lock controller 16, 18, 20, 22, etc., of the access control system 10 may be configured to determine correspondence of a key code CK, or code segment SCn, with an access value VAn (or portion thereof) under any desired “matching rule”. Such correspondence or matching may include an exact match (e.g., SCn=PVn), greater than or equal to match, a wildcard match, a match defined by a mathematical formula or other logical relationship, or even no match at all. Further, each controller 16, 18, 20, etc. may each be programmed or constructed to determine correspondence under a matching rule(s) different than the other controllers 16, 18, 20, etc. and/or to determine correspondence between different code segments SC1, SC2, etc., under different matching rules (e.g., SC1=VAn1, SC2>VAn2).
Referring to
Referring now to
Furthermore, each key code segment SC1, SC2 is equated to or corresponds with at least one character, such that the key code CK includes a plurality or “string” of characters. For example, the key code CK may correspond with a string of five characters, with a code first segment SC1, including two of the characters and a code second segment SC2 including the remaining three characters of the string. Most preferably, each code character is one of sixteen characters of the hexadecimal numbering system, i.e., numbers 0-9 and letters A-F. However, the code characters may be of any other known number, letter, symbol, etc., or systems thereof, as desired by the person(s) establishing the access criteria of the control system 10.
Preferably, the access value VAn of each lock controller 16, 18, 20, 22, etc. indicates at least one property or characteristic PDn of the associated door Dn and most preferably each access value VAn has a plurality of value portions PVn1, PVn2, etc. each indicating a separate characteristic of the associated door Dn. In other words, the access value VA1 of the first controller 16 indicates at least one property or characteristic PD1 of the first door D1, the stored value VA2 of the second controller 18 indicates at least one characteristic PD2 of the associated second door D2, etc. Such door characteristics PD, may include, but are not limited to, specific door location (e.g., 15 West, Room 322, etc.), security level (e.g., low, high, restricted, etc.), department (math, science, engineering, sales, etc.), authorized user gender (i.e., male, female, both genders), door type (e.g., interior, exterior, closet, cabinet, etc.), intended user position/rank/office (staff member, manager, captain, senator, etc.), and may include any other characteristic deemed relevant to the person(s) establishing or implementing the access control system 10. Further, to enable different access privileges to be established, at least one of the doors (e.g., the second door D2) has a characteristic PD2 that the other door (e.g., the first door D1) lacks, for example, the second door D2 may be for female users only or a high security door, whereas the first door D1 is intended for use by all authorized users of the control system 10.
By establishing the controller access values VAn to correspond with one or more characteristics PDn of the associated door Dn, the desired access privileges for a particular user may be implemented by writing, generating, etc., that user's key code CK to include code segments SCn which correspond to the characteristics PDn, of those doors Dn to which user access is intended to be granted. In other words, the code CKn of each key 14 is preferably generated, written, etc. such that each code segment SC1, SC2, SC3, etc., corresponds with a separate characteristic of each door D1, D2, D3, etc., to which the authorized key user is intended to have access privileges. As such, the code CK of each key 14 preferably has two or more segments SC1, SC2, etc., enabling access to two or more doors D1, D2, etc., but may have only a single segment, character, etc., permitting access to one or more doors D1 of a single type (e.g., only exterior doors).
For example, a structure S may have one or more first doors D1 which are exterior doors for use by both genders and one or more second doors D2 that are interior doors D2 for use by women only (e.g., a women's bathroom). As such, the access value VA1 for each such first door D1 may include one or more characters indicating an exterior door (e.g., 00) and one of more characters indicating both genders (e. g., 00). The access value for each second door D2 may include one or more characters indicating an interior door (e.g., 01) and one of more characters indicating only the female gender (e.g., 01).
With this system 10, a female user intended to access privileges to both doors D1, D2 may be assigned a first key 15A with a code CK1 (e.g., 0101) having two codes segments SC11=01, SC12=01. A male user may be assigned a second key 15B with a code CK (e.g., 0100) having two codes segments SC11=01, SC12=00. As such, when the female user presents the first key 15A to each of the first and second door controllers 16, 18, each controller 16, 18 determines that the first key code CK1 corresponds with each access value VA1, VA2 and provides the female user with access through both doors D1, D2. The male user will be able to use the second key 15B to access the exterior door D1, but when the male user presents the second key 15B to the second door controller 18, the second controller 18 should be configured to determine that the second key code CK2 does not correspond with the second access value VAn, and deny access through the second door D2.
Referring to
Further, each controller 16, 18, 20, etc. of the system 10 preferably further includes an audit file FA and a void user file FV stored in the controller memory 17, 19, 21, etc. The controllers 16, 18, 20, etc. are each preferably configured to create an audit record RA within the audit file FA whenever a key 14 is used, each audit record RA preferably including at least the code identifier segment SI of the particular key 14 and data corresponding to the time and date of key usage. Also, the controllers 16, 18, 20, etc. are also configured to compare the code identifier segment SI with each value fv (if any) in the void file FV and to prevent lock operation when the identifier segment SI corresponds with a value in the void file FV. More specifically, each void file value fv preferably includes data corresponding to a voided key's identifier segment SI, most preferably both the identity portion ISI and the replacement code portion RSI. When a key 14 having an identifier segment SI listed within a controller's void file FV is presented to a door controller 16, 18, 20, etc., the particular controller will not operate the coupled lock L1, L2, L3, etc. even if the access segments SC1, SC2, etc. correspond with door access value VA1, VA2, VA3, etc. Thus, the provision of the controller void files FV enable the access control system 10 to prevent the use of a key 14 that has been lost, stolen and/or replaced.
Furthermore, each controller 16, 18, 20, etc., is preferably further configured to create new void file entries or values fv in the following manner. When a key 14 is presented to a lock controller 16, 18, 20, etc., the particular controller will determine that the key 14 has been replaced when it reads the replacement code portion RSI of the key code identifier segment SI and the replacement code value cr is greater than the original issue/base value cr and has an expiration date dre, as discussed above. In such cases, when the controller 16, 18, 20, etc. searches the void file FV for any value fV with the same code identifier segment SI (SI (ISI, RSI)=fV (ISI, RSI)) as discussed above, the particular controller 16, 18, 20, etc. also preferably searches for any void values fV that have the same identity portion ISI and an earlier replacement code RSI. If such a void value fV is found, the controller 16, 18, 20, etc. “updates” the void value fV to have a replacement code value cr equal to the value of the key's replacement code cr reduced by one (or by whatever inclement the replaced codes cr are increased), i.e., fv (Cr)=CK ( Cr)−1, and with the same expiration date dre as the key code replacement expiration date dre(i.e., fV (dre)=CK (dre)) . However, if no such void value fV is found, the controller 16, 18, 20, etc. writes a new void value fv having the code identifier segment ISI and a replacement code portion RSI with an incrementally-reduced replacement code value cr (i.e., fV (cr)=CK (Cr)−1) and the key code expiration date dre(i.e., fV (dre)=CK (dre)). Alternatively or in addition to automatically created void file value fV, the controllers 16, 18, 20, etc. may each be configured to receive void file values fv from an appropriate programming device or data transfer device (none depicted) Further, each key code CK may further have a “user type” code segment CU providing different time and/or weekday restrictions or privileges for each one of a plurality of different authorized users of a particular access system 10. For example, a first user type designated by a character “A” may permit access to authorized doors twenty four hours a day, seven days a week, a second user type designated by character “B” may permit access twenty four hours a day, but only on weekdays, a third user type designated by character “C” may permit access only between 6:00 a.m. and 8:00 p.m. and only on weekdays, etc. Further, the lock controllers 16, 18, 20, etc. each preferably has a clock and calendar 43 (see
As an alternative to using a user type segment code CU, each key code CK may instead have an authorized usage time segment ST and an authorized day or date segment SD. The code time segment ST indicates either an authorized usage period (e.g., between 7:00 am and 6:00 p.m.) or an unauthorized usage period (e.g., between 6:00 p.m. and 7:00 am), and the code date segment SD indicates either an authorized usage day or date (e.g., weekdays, between Jan. 1, 2005 and Jun. 1, 2005) or an unauthorized usage day/date (e.g., Saturdays and Sundays, after Jun. 1, 2005). Further, each controller 16, 18, 20, etc., is configured to prevent operation of the associated lock L1, L2, L3 when the controller 16, 18, 20, etc., determines from the code time segment ST that the key code CK is being received during an unauthorized usage period or determines from the code date segment SD that the key code CK is being received during an unauthorized usage period. However, as some users may be intended to have access privileges at all times or/and on all days or dates, certain key codes CK may not have either or both of the code time segment ST and the code date segment SD.
Furthermore, each key code CK may further include an activation date segment SA indicating a date on (or after) which the particular key 14 is authorized and each controller 16, 18, 20, etc. may be configured to ignore any key 14 that is presented before the date indicated by the code activation date segment SA. Preferably, each key code CK also further includes an expiration date segment SE and each lock controller 16, 18, 20, etc. is further configured to “ignore” the code CK, such that the associated lock L1, L2, L3, etc. remains in the locked state, when a key 14 is presented after the date of the code expiration segment SE. As such, a user may be provided with access privileges within the control system 10 for only a limited time period or be required to have their access privileges periodically renewed. Further, as keys 14 may be lost prior to the expiration date, the control system 10 preferably has the capability of denying access to such keys 14 by utilizing a void file FV and configuring the lock controllers 16, 18, 20, etc., to check all key codes CK against the void file values, as described above. Depending on the number of users, frequency of card loss, user turnover, average expiration period, etc., the void file FV of each controller 16, 18, 20, etc., may become filled and unable to store additional values without servicing the lock controller 16.
As such, each lock controller 16, 18, 20, etc., is preferably further configured to at least store, and preferably also write, void file values fv that each include both an identifier portion corresponding to the voided code identifier segment SI and an expiration date portion corresponding to the expiration segment SE of the particular voided key code CK. Further, the lock controllers 16, 18, 20, etc. are also configured to separately remove or delete each one of the void values fv from the void file FV after the expiration date of the void value fV. In addition, each controller 16, 18, 20, etc. is programmed to remove/delete a void value fv from the void file FV when the file FV includes a predetermined maximum number (e.g., 20) of void values fV and the particular void value fV has an expiration date earlier than the dates of all the other void values fV. Thus, by at least storing, and preferably also writing, void values fV that include an expiration date, the lock controllers 16, 18, 20, etc. are each able to automatically purge void values fV from the void file FV, and therefore prevent the controller void file FV from being filled with voided codes and unable to receive additional, more recent void values fV.
Referring to
Referring to FIGS. 3 and 8-10, each controller 16, 18, 20, etc. preferably includes a microprocessor 40 and one or more memory chips 42 coupled with the microprocessor 40 and providing the controller memory 17, 19, 21, etc. The microprocessors 40 are each electrically connected with the one or more input devices 26 so as to receive the key code(s) CK as electrical signals. Further, each microprocessor 40 is electrically connected with the actuator 34 of the associated lock Ln and is configured to generate and transmit a control signal CS (
Referring to
With the above access value scheme, the following three keys 15A, 15B, 15C and 15D maybe created for four different employees, as follows:
Keys 15A, 15B, 15C each have a time restriction (ST=01) which will causes each lock controller 16-24 to deny Employee One, Two and Three the ability to access any door Dn during a designated time period (e.g., between 8:00 p.m. and 6:00 a.m.), and Key 15D has no time restriction (SC4=00), such that Employee Four may access authorized doors Dn at any time. Additionally, each key code CK has an identifier segment SI that includes a three digit identifier portion ISI (001, 002, etc.) uniquely identifying each employee and a replacement code portion RSI, which indicate the issuance of the card. In this example, keys 15B, 15C, 15D are the original issue (RSI=1) and key 15A is a second issue (cr=2), i.e., key 15A replaced/reissued once and indicates that the lost/stolen key will expire January 2006. Also, each key code CK further has an third digit expiration date segment SE that indicates month and year of expiration, the first three keys 15A, 15B, 15C expiring in January 2006 (SE=106) and the fourth key 15D expiring in January 2008 (SE=108).
For this example, each lock controller 16-24 is configured to compare each code segment SCn with each corresponding access value portion PVn, i.e., each code first segment SC1 with each value first portion PV1, each code second segment SC2 with each value second portion PV2, and each code third segment SC3 with each value third portion PV3. Furthermore, except as discussed below, each controller 16-24 is also configured to find correspondence between a code segment SCn and the corresponding access portion PVn when the code segment value is equal to or greater than the access value portion, and to require all three code segments SC1, SC2, SC3 to correspond with the three access value portions PV1, PV2, PV3. The exception to this basic “correspondence rule” is the controllers 20, 22 controlling access through the doors D3, D4 of the two bathrooms should each be programmed or otherwise configured to require an exact match between each code second or “gender” segment SC2, and the access value second portion PV32, PV42. However, each lock controller 16-24 may be configured to compare only one or more selected code segments SCn with the controller's access value VAn or/and having any other desired matching criteria. For example, each lock controller 24 of the secured closet doors D5 may have an access value VAn that indicates a high security characteristic PD3, such that VA4=01, and be programmed to compare the third code segment SC3 of each key 1A-15D with the controller access value VA4.
With the above-described exemplary access control system 10, Employee One may present his key 15A to obtain access through any of the three entrance doors D1 and through the Men's bathroom door D3. However, if he presents the key 15A to the any of the office doors D2 (office 1-3, engineering or conference room), the second lock controllers 18 will deny access due to the non-correspondence of the code first segment SC1 (00) with the controller value first portion PV21 (01) (i.e., door type not authorized). Further, if he presents the key 15A to the women's bathroom door D3, the third controller 20 will deny access due to a non-correspondence of the code second segment SC2 (00) and the controller value second portion PV32 (10) (i-e., gender is unauthorized).
Employee Two may use her key 15B to access the three entrance doors D1, the five interior office doors D2, and the women's bathroom door D3. However, key 15B would not provide her with access through the men's bathroom door D4 and the secured closet doors D5. Similarly, Employee Three may use his key 15C to obtain access through the three entrance doors D1, the five interior office doors D2, and the men's bathroom door D4, but would be denied access through the women's bathroom door D3 and the secured closet doors D5.
Finally, Employee Four will be able to use key 15D to access all the doors except the men's bathroom door D4. For example, if she presented her key 15D to one of the secured closet doors D5, the fifth lock controller 24 will determine that the first code segment SC1 (01) matches the first, “location” value portion PV1 (00), that the code second segment SC2 (00) matches the second, “gender” value portion PV2 (00), and that the code third segment SC3 (01) matches the third, “security” value portion PV3 (01), and will then adjust the lock L5 to the unlocked state. However, if she presented the key 15D to the men's bathroom door D4, she would be denied access through the door D4 due to non-correspondence between the key code second segment SC2 (10) and the access value gender portion PV2 (01) of the fourth lock controller 22.
The above-described access plan/scheme is just one example of the implementation of the access control system 10 of the present invention that has been provided to illustrate certain features and the flexibility of control system 10. It must be emphasized that the access control system 10 may be used with any desired number of doors Dn, any number and/or types of controllers 16, 18, 20, etc., any number or appropriate type of locks Ln, etc. Further, the control system 10 may utilize any desired structure of the key codes CKn having any number of code segments Scn indicating any desired door characteristic PDn, using any desired symbols, characters, etc., having any desired number of different codes C1K, C2K, C3K, etc. on each key 14, and/or carrying or generating the one or more key codes CK using any appropriate type of key or credential.
It will be appreciated by those skilled in the art that changes could be made to the embodiments described above without departing from the broad inventive concept thereof. It is understood, therefore, that this invention is not limited to the particular embodiments disclosed, but it is intended to cover modifications within the spirit and scope of the present invention as defined herein and by the appended claims.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/US05/07657 | 3/9/2005 | WO | 00 | 9/6/2007 |
Number | Date | Country | |
---|---|---|---|
60551593 | Mar 2004 | US |