Not Applicable
Not Applicable
The preferred embodiments of the present invention relate to an RF access control system for controlling access to an access point. More specifically, the preferred embodiments of the present invention relate to a method and system for a cardholder interface for an access control system
A wireless access control system may provide several advantages over a traditional, wire-based access control system. In a traditional, wired access control system, each access point, such as a door, for example, is equipped with a locking module to secure the access point. Each locking module is in turn directly wired to a remote access control module. The access control module is typically a database that compares a signal received from the locking module to a stored signal in the database in order to determine an access decision for that locking module. Once the access decision has been determined by the access control module, the decision is relayed to the locking module through the wired connection.
The use of wired connections between the access control module and the locking module necessitates a large investment of time and expense in purchasing and installing the wires. For example, for larger installations, literally miles of wires must be purchased and installed. An access control system that minimizes the time and expense of the installation would be highly desirable.
Additionally, wire-based systems are prone to reliability and security failures. For example, a wire may short out or be cut and the locking module connected to the access control module by the wire may no longer be under the control of the access control module. If a wire connection is cut or goes, the only alternative is to repair the faulty location (which may not be feasible) or run new wire all the way from the access control module to the locking module, thus incurring additional time and expense. Conversely, an access control system that provides several available communication channels between the locking module and the access control module so that if one communication channel is not usable, communication may proceed on one of the other communication channels, would also be highly desirable, especially if such an access control system did not add additional costs to install the additional communication channels.
A wireless access system providing a wireless communication channel between the locking module and the access control module may provide many benefits over the standard, wire-based access control system. Such a wireless access system is typically less expensive to install and maintain due to the minimization of wire and the necessary installation time. Additionally, such a system is typically more secure because communication between the locking module and the access control module is more robust that a single wire.
However, one difficulty often encountered in installing and maintaining such a wireless access system is the design and implementation of a cardholder interface to provide indications of the operation and/or state of the wireless access system to a user and/or technician.
Consequently, a wireless access system providing such indications would be highly desirable.
A wireless access system including indicators for communicating the operation and/or status of the system to a user or technician is provided. The wireless access system preferably includes a cardholder interface. The cardholder interface preferably includes at least some of the following: visual display of firmware version number, LED indicator, beeper, card swipe indicator, access denial feature, and a request to enter feature.
The present application is directed toward a portion of a wireless access system. Additional disclosure of the wireless access system may be found in the following co-filed applications which are hereby incorporated by reference in their entirety: application Ser. No. 10/261,933, entitled “RF Channel Linking Method and System” filed Sep. 30, 2002; application Ser. No. 10/262,207, entitled “Energy Saving Motor-Driven Locking Subsystem” filed Sep. 30, 2002; application Ser. No. 10/262,196, entitled “System Management Interface for Radio Frequency Access Control” filed Sep. 30, 2002; application Ser. No. 10/262,194 entitled “Power Management for Locking System” filed Sep. 30, 2002; application Ser. No. 10/262,507, entitled “General Access Control Features for a RF Access Control System” filed Sep. 30, 2002; application Ser. No. 10/262,077, entitled “RF Wireless Access Control for Locking System” filed Sep. 30, 2002; application Ser. No. 10/262,508, entitled “Maintenance/Trouble Signals for a RF Wireless Locking System” filed Sep. 30, 2002; and application Ser. No. 10/262,409, entitled “RF Dynamic Channel Switching Method” filed Sep. 30, 2002.
In operation, an access signal is read at the access point 140. The access signal may be a signal from an access card, for example, a magnetic stripe or Wiegand access card. Alternatively, the access signal may be a biometric or a numeric sequence or some other access signal. The access signal is relayed from the access point 140 to the WAPM 130 through the wired communication link 135. As further described below, the access point 140 may be integrated into the WAPM 130 to form a single component or may be a separate component wired to the WAPM 130.
Once the WAPM 130 receives the access signal from the access point 140, the WAPM 130 transmits the access signal to the WPIM 120 over the RF communication link 125. The WPIM 120 receives the access signal and relays the access signal to the ACP 110 over the wired communication link 115.
In the expanded wireless access system 200, a single ACP 210 communicates with a number N of WPIMs 222, 252 over a number N of wired communication links 220, 250. That is, the ACP supports communication with and provides access decisions for plurality of WPIMs 222, 252. Each WPIM 222, 252 may in turn support a plurality of WAPMs 240, 242, 270, 272 each WAPM positioned at a single access point. For example, WPIM #1 communicates with a number K of WAPMs 240, 242 over a number K of RF communication links 230, 232. Additionally, WPIM #N communicates with a number J of WAPMs 270, 272 over a number J of RF communication links 260, 262.
In a preferred embodiment, the ACP 210 supports three WPIMs and each PIM can support up to six WAPMs. However, as more advanced and configurable systems are developed, the total numbers of WPIMs and WAPMs supported is expected to rise. Additionally, the N wired communication links 220, 250 are illustrated as the preferred embodiment of RS486 communication links. Alternatively, other well-known communication protocols may be employed.
The power supply 370 provides power to all of the other systems of the housing 310, including the transceiver 360, the locking control circuit 340, and the access/monitoring processor 350. The power supply 370 may be an internal battery or other internal type of power supply. Alternatively, an AC power supply may be employed. The transceiver 360 is coupled to the antenna 325 to allow signals to be sent and received from the housing 310 to an external point such as a WPIM through the RF communication link 332. The locking control circuit 340 is coupled to the access point 301 and provides locking control signals to the access point 301 through the wired communication link 330. Additionally, the locking control circuit 340 may receive feedback from the access point 301 through the wired communication link 330, for example to verify that the access point is secured. The access reader 390 receives access signals such as from an integrated card reader or other access device, for example. The indicators 320 may provide a visual or audio indication, for example, of the state of the WAPM 300 or that an access signal has been read by the access reader 390.
In operation, an access signal may be received from the access reader 390. The access signal is then relayed to the access/monitoring processor 350. The access/monitoring processor 350 then sends the access signal to the transceiver 360. The transceiver 360 transmits the access signal to WPIM 120 of
The WAPM 300 may include several variations. For example, the WAPM may be an Integrated Reader Lock (WAPM 300), a Wireless Reader Interface (WRI), a Wireless Integrated Strike Interface (WISI), a Wireless Universal Strike Interface (WUSI), or a Wireless Portable Reader (WPR). The WAPM 300 includes an integrated access reader and lock. That is, the WAPM 300 is similar to
Power is typically supplied to the WPIM via an AC power supply or through the wired communication 472. The transceiver 460 is coupled to the antenna 465 to allow signals to be sent and received from the housing 410 to an external point such as a WAPM through the RF communication link 467. The ACP 480 is coupled to the WPIM 400 through the wired communication link 472. The data port 430 is coupled to the control processor 450 to allow an external user such as a technician, for example, to interface with the control processor. The indicators 420 may provide a visual or audio indication, for example, of the state of the WPIM 400 or that an access signal has been passed to the ACP 480 or an authorization passed to a WAPM 300.
In operation, the WPIM 400 receives access signals from the WAPM 300 through the antenna 465 and transceiver 460. The WPIM relays the access signals to the ACP 480 for decision making. Once the access decision has been made, the ACP 480 transmits the access decision through the wired communication link 472 to the WPIM 400. The WPIM 400 then transmits the access decision to the WAPM 300.
As mentioned above, the WPIM 400 includes a data port 430. The data port 430 is preferably an RS485 port. The data port 430 may be used, for example, by an operator to connect a computer to the WPIM 400 to perform various tasks, such as configuring the WPIM 400, for example. Some exemplary WPIM items for configuration include the transmission frequency for the communication link with the WAPM and the performance of the indicators 420.
Additionally, configuration information may be received by the data port 430 of the WPIM 400 and relayed to the WAPM 300 via the transceiver 460. The configuration information that is received by the WAPM 300 may then by relayed to the access/monitoring processor 350 of the WAPM 300 for implementation at the WAPM 300.
The WPIM may include several variations including a panel interface module (PIM) and a panel interface module expander (PIME). As mentioned above, a single PIM may communicate with multiple WAPMs. Additionally, the housing for the PIM is preferably constructed to allow additional PIM modules to be installed in the PIM housing to form the PIME. Because the PIME includes multiple PIM modules, the PIME may service more access points.
Turning again to
As mentioned above, the indicators may be visual or audible indicators and may be used to provide insight into the functioning of the components of the wireless access system, and the WAPM 300, in particular. In a preferred embodiment, the indicators display the current status of operation to a user of the WAPM 300.
The indicators preferably display the following elements of information:
1)The version of software employed by the WAPM 300. As is typically the case, the WAPM 300 is preferably released with a first version of software installed. However, the software and WAPM 300 are preferably upgradable so that improvements in function or user customization is available. Consequently, a service operator may need to know the software version installed on the WAPM 300, for example, to successfully decode the indicators. An indicator provides confirmation of the software version.
2) Whether the WAPM 300 is being re-locked. The WAPM 300 is re-locked when the locking control circuit 340 causes the access point 301 to lock. An indicator provides confirmation that the WAPM 300 is being re-locked.
3) A communications link request by the WAPM 300. When the WAPM 300 is first powered-up, the WAPM 300 establishes a communications link with a WPIM as described above. The first step in establishing the communications link is the WAPM 300 sending a communications request to the WPIM. An indicator provides confirmation that this signal is being sent.
4) A packet error test being performed by the WAPM 300. The next step in establishing communication between the WAPM 300 and the WPIM is to perform a packet error test over the communications link. An indicator provides confirmation that this test is occurring.
5) Establishment of a successful communication channel by the WAPM 300. Once the communication channels between the WAPM 300 and the WPIM has been established and verified, normal communications may occur. An indicator provides confirmation that this communications link has been established. Also, the indicator preferably indicates the channel over which communication has been established in a multi-channel system.
6) Whether an access signal has been read by the WAPM 300. Access requests may be periodically submitted to the WAPM 300. For example, a user may swipe a card reader at the access reader 190. An indicator provides confirmation that a card has been swiped. The indicator may be a visual blink, an audible tone, or both.
7) Whether the access signal was successfully received by the WAPM 300. Once an access request is submitted to the WAPM 300, the WAPM 300 interprets the access request and tries to read the data contained in the access request. For example, with regard to a card reader, first the card is swiped and then the WAPM 300 attempts to recognize the data on the card. An indicator provides confirmation that the data was successfully read from the card.
8) Whether the WAPM 300's communication link has been interrupted. The WAPM 300 also preferably indicates if its communications link with the remote access control panel or WPIM has been interrupted.
Additionally, the WPAM may periodically send signals to the WPIM and receive a confirmation signal from the WPIM to confirm that the communication channel between the WAPM and WPIM remains active. This periodic signal may be referred to as a heartbeat. The WAPM preferably indicates the failure of the WPIM to respond to the WAPM's heartbeat signal.
9) If access has been granted or denied. Once the access signal has been read by the WAPM 300 and then compared to the authorized access signals at the access control panel, and a decision has been sent from the WPIM to the WAPM 300, the WAPM 300 gives an indication that access has been granted or denied.
10) Additionally, the WAPM preferably indicates when the WAPM is experiencing an internal malfunction. For example, the WAPM may indicate that its motor has stalled. Additionally, the WAPM may be configured to sense when the door is closed. For example, a magnetic sensor may be mounted on the door jam and the door to sense when the door is closed. If the door is not closed for a certain length of time, the WAPM may preferably indicate the condition. Additionally, the WAPM may be equipped with a pre-alarm signal to provide an indication at the WAPM at a first time and then to later transmit the alarm to the WPIM at a second, later time if the door remains open. For example, at the first time, the WAPM may emit an audible tone signifying that the door is ajar.
As mentioned above, in a preferred embodiment, the indicators 320 are the red LED 398, green LED 399, and audible sound generator 322 as shown in
Table 1 illustrates a preferred embodiment of the indicators 320 as implemented in the WAPM 300 of
As shown in Table 1, when the WAPM 300 is powered on, the red LED preferably blinks a number of times equal to the major version number of the software and the green LED preferably blinks a number of times equal to the minor version of the software. For example, if the software is version 2.4, the red LED blinks twice and the green LED blinks four times.
When the WAPM 300 relocks, the red LED flashes and the sound generator sounds a beep.
When the WAPM 300 sends a link request, the green LED flashes once and then the red LED flashes once.
When the WAPM 300 performs a packet error test, the WAPM 300 flashes green once for a good transmission and red once for a bad transmission.
When the WAPM 300 successfully establishes a link to a WPIM or remote access panel, the green LED flashes. Preferably, the green LED flashes a number of times equal to the number of the communication channel that the communication link occupies. For example, in a system having 15 possible communication links, the green LED blinks between once and 15 times to indicate the channel number. Additionally, the sound generator beeps a number of times equal to the channel number.
If the WAPM 300 is unable to establish a communication link, the WAPM 300 emits two red flashes and a long beep.
When an access signal is presented to the WAPM 300, for example, when a card is swiped, no indication is presented. Once the swiped card has been read, the sound generator preferably emits a beep. If access is denied, the WAPM 300 emits 2 red flashes and a single beep. If access is granted, the WAPM 300 emits a green flash.
If the WAPM 300 loses its communication link with the WPIM 400 or access control panel 110, the WAPM 300 emits a single red flash.
Turning again to
As with the WAPM 300 above, the WPIM indicators 420 preferably indicate numerous conditions. These include:
1) Whether the WPIM is in normal operation. An indicator provides confirmation the operation of the WPIM is proceeding normally.
2) Whether the WPIM's housing door is open. An indicator provides confirmation the WPIM's housing door is open or closed (e.g., a tamper signal).
3) Whether the WPIM or any of the WAPMs 300 that are linked to the WPIM are experiencing trouble. An indicator provides confirmation that the WPIM and/or WAPM 300 are experiencing trouble and preferably also provides information as to the type of trouble encountered. For example, the WPIM or WAPM may be experiencing a low battery level, not receiving communication, have been tampered with, or have received a notification from an WAPM that the WAPM's motor has stalled.
4) Whether the WPIM is in link mode A or link mode B. In a preferred embodiment, each WPIM is linked to two WAPMs, however, the WPIM is not constrained to link with only two WAPMs. When linked with two WAPMs, the WPIM designates one WAPM as A and the other WAPM as B. When the WPIM is initially linking to a WAPM it is in link mode. Thus, for example, the initial linking with WAPM A defines a link mode A.
5) Whether the WPIM is participating in a packet error test. As mentioned above, the WPIM and WAPM 300 conduct a packet error test when the WAPM 300 is powered up or re-linked. An indicator provides confirmation that the packet error test is being performed.
6) Whether the WPIM is transmitting or receiving a message. As mentioned above, in a preferred embodiment, the indicators include a single green LED 497, a pair of red LEDs 498, and a pair of LEDs that may display both red and green 499 as shown in
Table 2 illustrates a preferred embodiment of the indicators 420 as implemented in the WPIM 200 of
As shown in Table 2, when the WPIM is in normal operation and the access panel is closed, the green LED 497 blinks continuously and the green/red LEDs 499 are green. When the access panel is opened, the green LED 497 stays on and the green/red LEDs 499 are green. If the WPIM is not powered on, the green LED 497 stays off and all other LEDs are off.
If the WPIM 200 is experiencing trouble, the red LEDs 498 blink, the green LED 497 is on, and the green/red LEDs 499 are green. The number of blinks in a sequence is used to indicate the specific type of trouble that the WPIM is experiencing. If the sequence is one blink long, the WPIM is experiencing a low battery condition. If the sequence is two blinks long, the WPIM is not receiving communication from an WAPM. If the sequence is three blinks long, the WAPM's reader has been tampered with. If the sequence is four blinks long, the WPIM has received a signal from an WAPM that the WAPM's lock motor has stalled.
When the WPIM is communicating in link modes A or B, the green LED 497 is blinking, the red LEDs 498 are off, and the green/red LEDs 499 flash green and red.
When the WPIM is engaged in a packet error test, the green LED 497 is blinking, the red LEDs 498 are off, and the green/red LEDs 499 flash green and red. That is, the green/red LEDs flash green on each error-free transmission and flash red on any transmission including an error.
When the WPIM is transmitting a message, the green LED 497 is blinking, the red LEDs 498 are off, and the green/red LEDs 499 flash red once for each message.
When the WPIM 200 is receiving a message, the green LED 497 is blinking, the red LEDs 498 are off, and the green/red LEDs 499 blink off momentarily.
Additionally, one of the preferred embodiments of the present invention includes a request to enter feature. The request to enter may be either an access signal such as a card read, or the request to enter may be an input such as a switch mounted on the WAPM 300. The switch is preferably connected to the secured side (outside) of the WAPM 300. The request to enter switch may be used, for example, to indicate that someone is trying to gain access through the WAPM 300. That is, to indicate that someone wishes to gain access through the door.
The request to enter feature is similar to a doorbell, but may include the activation of a camera for observing the person seeking to gain entrance, or may trigger an interior buzzer or an audible or visual prompt on an interior access interface.
While particular elements, embodiments and applications of the present invention have been shown and described, it is understood that the invention is not limited thereto since modifications may be made by those skilled in the art, particularly in light of the foregoing teaching. It is therefore contemplated by the appended claims to cover such modifications and incorporate those features that come within the spirit and scope of the invention.
The present application claims priority to the following provisional applications all filed Sep. 30, 2001: Application No. 60/326,338, entitled “RF Channel Linking Method and System”; Application No. 60/326,299, entitled “Energy Saving Motor-Driven Locking Subsystem”; Application No. 60/326,201 entitled “Cardholder Interface for an Access Control System”; Application No. 60/326,316, entitled “System Management Interface for Radio Frequency Access Control”; Application No. 60/326,298 entitled “Power Management for Locking System”; Application No. 60/326,179, entitled “General Access Control Features for a RF Access Control System”; Application No. 60/326,296, entitled “RF Wireless Access Control for Locking System”; Application No. 60/326,294, entitled “Maintenance/Trouble Signals for a RF Wireless Locking System”; and Application No. 60/326,295, entitled “RF Dynamic Channel Switching Method.”
Number | Name | Date | Kind |
---|---|---|---|
528589 | Brownell et al. | Nov 1894 | A |
1946384 | Baril et al. | Feb 1934 | A |
3967478 | Guinn | Jul 1976 | A |
4048630 | Deming et al. | Sep 1977 | A |
4357601 | McWilliams | Nov 1982 | A |
4539555 | Tefka | Sep 1985 | A |
4557121 | Charlton | Dec 1985 | A |
4579376 | Charlton | Apr 1986 | A |
4634155 | Geringer et al. | Jan 1987 | A |
4672365 | Gehman et al. | Jun 1987 | A |
4677834 | Hicks | Jul 1987 | A |
D306806 | Hill | Mar 1990 | S |
4967478 | Sherman | Nov 1990 | A |
5009456 | Eck | Apr 1991 | A |
5019803 | Maram | May 1991 | A |
5075608 | Erdman et al. | Dec 1991 | A |
5095654 | Eccleston | Mar 1992 | A |
5148691 | Wallden | Sep 1992 | A |
5184349 | Riordan | Feb 1993 | A |
5263347 | Allbaugh et al. | Nov 1993 | A |
5308131 | Galindo et al. | May 1994 | A |
5313812 | Eklund et al. | May 1994 | A |
5410444 | Juds | Apr 1995 | A |
5418839 | Knuth et al. | May 1995 | A |
RE35124 | Erdman et al. | Dec 1995 | E |
5475375 | Barrett et al. | Dec 1995 | A |
5479151 | Lavelle et al. | Dec 1995 | A |
5491471 | Stobbe | Feb 1996 | A |
5497411 | Pellerin | Mar 1996 | A |
5531086 | Bryant | Jul 1996 | A |
5577229 | Wakerly | Nov 1996 | A |
5602536 | Henderson et al. | Feb 1997 | A |
5608298 | Frolov et al. | Mar 1997 | A |
5611582 | Frolov et al. | Mar 1997 | A |
5630169 | Jackson | May 1997 | A |
5682135 | LaBonde et al. | Oct 1997 | A |
5683127 | Chamberlain | Nov 1997 | A |
5705991 | Kniffin et al. | Jan 1998 | A |
5722276 | Aigner et al. | Mar 1998 | A |
5729198 | Gorman | Mar 1998 | A |
5769472 | Small | Jun 1998 | A |
5774059 | Henry et al. | Jun 1998 | A |
5791178 | Chamberlain et al. | Aug 1998 | A |
D397993 | Jimenez | Sep 1998 | S |
5808296 | McMonagle et al. | Sep 1998 | A |
5812782 | Jackson | Sep 1998 | A |
5847662 | Yokota et al. | Dec 1998 | A |
5867095 | Klein et al. | Feb 1999 | A |
5881055 | Kondo | Mar 1999 | A |
5884145 | Haartsen | Mar 1999 | A |
5901361 | Luong | May 1999 | A |
5933086 | Tischendorf et al. | Aug 1999 | A |
5936544 | Gonzales et al. | Aug 1999 | A |
5940771 | Gollnick et al. | Aug 1999 | A |
5948102 | Wuidart | Sep 1999 | A |
5974367 | Bianco | Oct 1999 | A |
6021477 | Mann | Feb 2000 | A |
6035676 | Hudspeth | Mar 2000 | A |
6038896 | Chamberlain et al. | Mar 2000 | A |
6067297 | Beach | May 2000 | A |
6076385 | Pedroso et al. | Jun 2000 | A |
6108188 | Denison et al. | Aug 2000 | A |
6167251 | Segal et al. | Dec 2000 | A |
6167934 | Debroche | Jan 2001 | B1 |
6185415 | Boatwright | Feb 2001 | B1 |
6189351 | Eagan et al. | Feb 2001 | B1 |
6212175 | Harsch | Apr 2001 | B1 |
6237028 | Jackson | May 2001 | B1 |
6259352 | Yulkowski et al. | Jul 2001 | B1 |
6260392 | Geiger | Jul 2001 | B1 |
6285295 | Casden | Sep 2001 | B1 |
6297725 | Tischendorf et al. | Oct 2001 | B1 |
6326754 | Mullet et al. | Dec 2001 | B1 |
6330817 | Frolov | Dec 2001 | B1 |
6347486 | Badillet | Feb 2002 | B1 |
6352202 | Takiguchi et al. | Mar 2002 | B2 |
6359547 | Denison et al. | Mar 2002 | B1 |
6377608 | Zyren | Apr 2002 | B1 |
6392537 | Tazumi et al. | May 2002 | B1 |
6397061 | Jordan et al. | May 2002 | B1 |
RE37784 | Fitzgibbon et al. | Jul 2002 | E |
6434985 | Walmsley | Aug 2002 | B1 |
6535136 | Rodenbeck et al. | Mar 2003 | B1 |
6624750 | Marman et al. | Sep 2003 | B1 |
6657976 | Larghi | Dec 2003 | B1 |
6658328 | Alrabady et al. | Dec 2003 | B1 |
6665520 | Romans | Dec 2003 | B2 |
6714118 | Frolov et al. | Mar 2004 | B1 |
6776332 | Allen et al. | Aug 2004 | B2 |
6778099 | Meyer et al. | Aug 2004 | B1 |
6801134 | Juzswik | Oct 2004 | B1 |
6828902 | Casden | Dec 2004 | B2 |
6879259 | Smith et al. | Apr 2005 | B1 |
6894609 | Menard et al. | May 2005 | B2 |
6956840 | Proctor, Jr. | Oct 2005 | B1 |
6958976 | Kikkawa et al. | Oct 2005 | B2 |
20010021639 | Kaku | Sep 2001 | A1 |
20010055283 | Beach | Dec 2001 | A1 |
20020163430 | Bergman et al. | Nov 2002 | A1 |
20020177473 | Skinner et al. | Nov 2002 | A1 |
20020180582 | Nielsen | Dec 2002 | A1 |
20030025082 | Brewington et al. | Feb 2003 | A1 |
20030096607 | Taylor | May 2003 | A1 |
20030098778 | Taylor et al. | May 2003 | A1 |
20030098779 | Taylor et al. | May 2003 | A1 |
20030100266 | Wiemeyer et al. | May 2003 | A1 |
20030103472 | Taylor et al. | Jun 2003 | A1 |
20030143956 | Taylor | Jul 2003 | A1 |
20040236547 | Rappaport et al. | Nov 2004 | A1 |
20050003812 | Gladwin et al. | Jan 2005 | A1 |
Number | Date | Country |
---|---|---|
2749607 | Dec 1997 | FR |
WO 0225040 | Mar 2002 | WO |
Number | Date | Country | |
---|---|---|---|
20030117263 A1 | Jun 2003 | US |
Number | Date | Country | |
---|---|---|---|
60326338 | Sep 2001 | US | |
60326299 | Sep 2001 | US | |
60326201 | Sep 2001 | US | |
60326316 | Sep 2001 | US | |
60326298 | Sep 2001 | US | |
60326179 | Sep 2001 | US | |
60326296 | Sep 2001 | US | |
60326294 | Sep 2001 | US | |
60326295 | Sep 2001 | US |