Key and security device

Information

  • Patent Grant
  • 11015373
  • Patent Number
    11,015,373
  • Date Filed
    Tuesday, May 12, 2020
    4 years ago
  • Date Issued
    Tuesday, May 25, 2021
    3 years ago
Abstract
A key for a security device is provided. The key may include an electronic component configured to communicate with one or more security devices to initially receive one or more codes associated with each of the security devices. The key may also include a memory configured to store the one or more codes associated with the one or more security devices. The electronic component is configured to communicate with each of the one or more security devices for arming and/or disarming the security devices upon a matching of the code stored by the memory with the code associated with the security device.
Description
BACKGROUND OF THE INVENTION

Embodiments of the present invention relate generally to keys and security devices of the type used to display an item of merchandise vulnerable to theft.


It is common practice for retailers to display items of merchandise on a security device. The security device displays an item of merchandise so that a potential purchaser may examine the item when deciding whether to purchase the item. The small size and relative expense of the item, however, makes the item an attractive target for shoplifters. A shoplifter may attempt to detach the item from the security device, or alternatively, may attempt to remove the security device from the display area along with the merchandise. In some instances, the security device is secured to a display support using a lock operated by a key, for example, a mechanical lock. In other instances, the security device is secured to the display support using a lock operated by an electronic key to arm and disarm the security device.


BRIEF SUMMARY OF THE INVENTION

Embodiments of the present invention are directed to keys, security devices, security systems, and method for securing items of merchandise from theft. In one embodiment, a key for a security device is provided. The key includes an electronic component configured to communicate with one or more security devices to initially receive one or more codes associated with each of the security devices. The key also includes a memory configured to store the one or more codes associated with the one or more security devices. The electronic component is configured to communicate with each of the one or more security devices for arming and/or disarming the security devices upon a matching of the code stored by the memory with the code associated with the security device.


In another embodiment, a security system is provided. The security system includes one or more security devices each comprising a monitoring circuit and a code. The security system also includes one or more keys each comprising an electronic component configured to communicate with the one or more security devices to initially receive one or more codes associated with each of the security devices. Each key further includes a memory configured to store the one or more codes associated with the one or more security devices. The electronic component is configured to communicate with each of the one or more security devices for arming and/or disarming the security devices upon a matching of the code stored by the memory with the code associated with the one or more security devices.


According to another embodiment, a method for securing items of merchandise is provided. The method includes communicating with one or more security devices to initially receive and store one or more codes associated with each of the one or more security devices. In addition, the method includes subsequently communicating with each of the one or more security devices for arming and/or disarming the one or more security devices upon a matching of the code stored with the code associated with the one or more security devices.


In another embodiment, a security device for an item of merchandise is provided. The security device includes an electronic component configured to communicate with one or more keys to initially receive one or more codes associated with each of the keys. The security device also includes a memory configured to store the one or more codes associated with the one or more keys. The electronic component is configured to communicate with each of the one or more keys for arming and/or disarming the security device upon a matching of the code stored by the memory with the code associated with the one or more keys.





BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description of the invention provided below may be better understood with reference to the accompanying drawing figures, which depict one or more embodiments of a security device and method.



FIG. 1 illustrates a key according to one embodiment of the present invention.



FIG. 2 illustrates a key according to another embodiment of the present invention.



FIG. 3 illustrates a schematic view of a key according to one embodiment of the present invention.



FIG. 4 is a perspective view of a security device according to one embodiment of the present invention.



FIG. 5 is a perspective view of a key engaged with a programming station according to one embodiment of the present invention.





DETAILED DESCRIPTION OF THE INVENTION

Referring now to the accompanying drawing figures, one or more embodiments of a key 10 for cooperating with a security device 12 are shown. The security device 12 may be one of the type commonly used to display one or more articles of merchandise (not shown for purposes of clarity) within a display area of a retail store. By way of example, and not by limitation, the security device 12 is a merchandise display hook for displaying relatively, small, expensive consumer products, for example, compact discs (CDs), digital video discs (DVDs), battery packs, etc., on a display support. The display support could be any suitable support, such as wire grid, horizontal bar rack, slatwall (also known as slatboard), wall, table, desk, countertop or other secure structure. Other examples of a security device 12 according to the present invention without limitation include merchandise display fixtures, merchandise tags (or “bugs”), stop locks, cable locks and wraps, and merchandise safers. In some embodiments, the security device 12 may be a display module, a puck, or an alarm that is mountable to a display surface, support, or the like, for displaying an item of merchandise (see, e.g., FIG. 4). The item of merchandise may be a display model or an operational sample of electronic merchandise, such as cellular telephones, portable computers (e.g., notebooks, laptops, tablets, etc.), e-readers, media players, and the like, for a customer to examine before making a decision to purchase the item. The item of merchandise may be displayed in a manner that permits a prospective purchaser to evaluate the operation and features of the merchandise, while protecting the merchandise from a potential thief. In some example embodiments, the security devices 12 are similar to the Locking Hooks, Smart Locks, and PODs manufactured by InVue Security Products Inc.


In one embodiment, a key 10 for a security device 12 is provided and generally includes a housing 14 and an actuation member 16 operably engaged with the housing (see, e.g., FIGS. 1 and 2). For example, the actuation member 16 may be at least partially disposed within the housing 14. The key 10 further includes an electronic component 20 operably engaged with the actuation member 16 and configured to cooperate with a security device 12 (see, e.g., FIG. 3). In some embodiments, the electronic component 20 comprises communication capability for communicating with the security device 12. Similarly, the security device 12 may include an electronic component 38 configured to communicate with the key 10. The actuation member 16 may be configured to move and/or activate the electrical component 20 for cooperation with the security device 12, and the actuation member 16 may be configured to be locked upon expiration of a predetermined period of time or number of activations such that the actuation member is unable to actuate the electrical component for cooperating with the security device. Thus, upon expiration of a particular period of time or number of activations, the key 10 is unable to be used to lock/arm or unlock/disarm a security device 12. In this way, stolen keys will be rendered useless after a predetermined period of time or activations. In addition, the key 10 can be used interchangeably with different types of security devices 12 such that a user is only required to carry one key. Thus, the key 10 may be “multi-purpose” in that the key may be used for different lock types (e.g., mechanical locking hooks, electronic locks, display modules, keepers, cable locks, etc.).


The housing 14 may be any suitable housing configured to at least partially receive the electrical component 20, as well as the actuation member 16, therein. For example, the housing 14 may be a single piece design or may include a plurality of components joined into a unitary member (e.g., via snap fit, fasteners, adhesive, and/or molding). In one example, the housing 14 includes two halves that are joined together to define an internal cavity. The housing 14 may define an internal cavity for accommodating various components, including the electrical component 20, the actuation member 16, and/or the locking mechanism 23. The housing 14 may also house various other components, such as a controller, a logic control circuit, or a printed circuit board, a battery, and/or an EAS tag. The housing 14 may also be coupled to various other optional components, such as a keychain 24, lanyard, or the like (see, e.g., FIGS. 1, 2, and 5). The housing 14 may be a variety of sizes and configurations, and may be suitably sized for placement within a user's pocket or on a key chain. The housing 14 may include an opening or channel 26 defined therein for receiving the actuation member 16. For instance, the actuation member 16 may be a manually operated button that is operable by the user and is operably engaged with the electrical component 20.


The actuation member 16 may be any device, mechanism, or feature that is configured to actuate the electrical component 20. For example, the actuation member 16 may be a manually actuated member, such as a push button, sliding mechanism, or the like. Alternatively, the actuation member 16 may be an automatically actuated member, such as an actuation member driven by a motor. The automatic actuation may occur, for example, in response to a user depressing a button or activating a switch. The actuation member 16 may be in communication with a logic control circuit, controller, or PCB of the key for actuating the actuation member in response to a signal from the logic control circuit, controller, or PCB.


Similar to the actuation member 16, the locking mechanism 23 may be a mechanical and/or electrical locking mechanism. Thus, as used herein, the term “locking mechanism” should be broadly construed to include any device, mechanism, or feature that physically locks, secures or protects the key 10 from further use. For example, the locking mechanism 23 could be a physical barrier that prevents the actuation member 16 and/or electrical component 20 from being displaced relative to the housing 14 or otherwise actuated to lock/arm or unlock/disarm a security device 12. Or, the locking mechanism 23 may be an electrically or an electro-mechanically controlled mechanism, such as a motor driven mechanism that is actuated to prevent the actuation member 16 and/or the electrical component 20 from being displaced or otherwise operated. Alternatively, the locking mechanism 23 could render the actuation member 16 inoperable such that the actuation member is incapable of being actuated. The locking mechanism 23 may be in communication with a logic control circuit, controller, or PCB of the key 10 such that the locking mechanism is configured to be actuated to lock or unlock the actuation member 16 in response to a signal from the logic control circuit, controller, or PCB.


In some cases, the actuation member 16 and the locking mechanism 23 may be separate components, while in other cases the actuation member and the locking mechanism may be integrated into a single component or otherwise operably engaged with one another. For example, where the actuation member 16 is a motor driven actuator, the locking mechanism 23 may also be operated via the motor driven actuator such that actuation of the motor in one direction actuates the electrical component 20 while actuation of the motor in an opposite direction or de-actuation of the motor locks the mechanical and/or electrical components.


In some embodiments, the key 10 may include a mechanical component 18 and an electrical component 20 (see, e.g., FIG. 3). For example, the mechanical component 18 may be configured to cooperate with a security device 12 having a mechanical member, such as, for example, a lock mechanism, a latch, or the like. In one embodiment, the mechanical component 18 may be configured to extend outwardly from the housing 14 to disengage a mechanical member of a security device 12, as well as retract relative to the housing 14. Thus, the mechanical component 18 could be a protrusion, extendable member, or the like that is configured to engage a mechanical member of the security device 12. In other embodiments, the mechanical component 18 facilitates communication between the electronic component 20 and the security device 12. For example, the mechanical component 18 may include one or more electrical contacts or allowing communication between the key 10 and the security device 12.


The electrical component 20 may be configured to cooperate with a security device 12 for arming and/or disarming a monitoring circuit 25 that is in electrical communication with the security device (see, e.g., FIG. 4). For example, the electrical component 20 may be configured for various forms of wireless communication with a security device 12, such as optical (e.g., infrared), acoustical (e.g. ultrasonic), radiofrequency (RF), or magnetic pulse. In one embodiment, data and/or power is transferred from the key 10 to the security device 12 by wireless communication, such as by infrared (IR) optical transmission, as shown and described in U.S. Pat. Nos. 7,737,843, 7,737,845, U.S. Publication No. 2011/0254661, and U.S. Patent Publication No. 2012/0047972, each of which is incorporated herein by reference in its entirety. In other cases, communication between the key 10 and the security device 12 may occur via wired means (e.g., electrical contacts) or other suitable communication means.


In some embodiments, the security device 12 may be programmed with an identification code, a security code, or the like. For example, each security device 12 may include a memory 36 that stores a particular code specific to the security device. The code may be programmed in the security device by the manufacturer or the retailer in some embodiments. Similarly, the key 10 may include a memory 28 for storing a code. The key 10 may be configured to be positioned within or proximate to a transfer port 30 of the security device 12, and the actuation member 16 may be depressed to activate communication of the security code between the key and the security device. In some cases, communication may occur automatically upon engagement of the key 10 with the security device 12, with or without actuation of an actuation member 16, or the security device may be actuated for communicating with the key. FIG. 4 shows one embodiment of a security device 12 including a transfer port 30 that is configured to communicate with a key 10. The key 10 may include a transfer probe 34 that is configured to be positioned proximate to, engaged with, or aligned with the transfer port 30 for facilitating communication therebetween. The security code may be wirelessly communicated between the security device 12 and the key 10 by infrared (IR) optical transmission. Alternatively, the security code may be transmitted and received by electrical contacts, acoustic transmission (e.g., RF signals), or magnetic induction.


In the event that the security code of the key 10 matches the security code of the security device 12, the key may then be permitted to arm and/or disarm the security device 12 and/or transfer electrical power to the security device, for example, to operate a lock mechanism of the security device. The key 10 may transfer electrical power to the security device 12 in any suitable manner, such as by electrical contacts, acoustical transmission (e.g. RF signals) or magnetic induction. Further discussion regarding data and electrical communication between an electronic key 10 and a security device 12 may be found, for example, in U.S. Publication No. 2012/0047972, which is hereby incorporated by reference in its entirety. It is understood that in other embodiments, the key 10 may only transfer a signal to arm and/or disarm the security device 12 and does not transfer electrical power to the security device.


The key 10 and/or the security device 12 may be programmed with a security code. The key 10 and/or the security device 12 may each be pre-programmed with the same code into a respective permanent memory. Alternatively, the key 10 may first be programmed with the code via communication with the security device 12. Thus, the key 10 may not have any stored code prior to communicating with the security device 12. For instance, the key 10 may be configured to communicate with one or more security devices 12 and store each of the codes in its memory 28. Thus, the key 10 may initially receive the codes from the security devices 12. The key 10 may be configured to store a plurality of codes such that the key may communicate with each of the security devices 12 associated with such codes for arming and/or disarming the security devices. In other embodiments, the security device 12 may be first programmed with a code via communication with one or more keys 10. Thus, the security device 12 may store one or more codes associated with each of the keys 10. In some embodiments, the key 10 and/or the security device 12 may be pre-programmed with a code or may be self-programming in other embodiments.


As discussed above, in one embodiment, the key 10 may include a time-out function. More particularly, the ability of the actuation member 16 to actuate the electrical component 20 may be deactivated after a predetermined time period or activations. The key 10 may be reactivated by communicating with a programming station 32, i.e., the key is “refreshed”. By way of example, the key 10 may include a logic control circuit that is configured to be deactivated after about six to twelve hours (e.g., about eight hours) from the time the key was last refreshed by a programming station 32. In one embodiment, an authorized sales associate is required to refresh the key 10 assigned to him or her at the beginning of each work shift. Thus, the key 10 would have to be refreshed by a programming station 32, which is typically monitored or maintained at a secure location, in order to reactivate the logic control circuit of the key. Other forms for refreshing the code may be used such as, for example, inputting a code, charging the key with an authorized charger, etc. The key 10 may be provisioned with a single-use (e.g., non-rechargeable) internal power source, such as a conventional or extended-life battery. Alternatively, the key 10 may be provisioned with a multiple-use (e.g., rechargeable) internal power source, such as a conventional capacitor or rechargeable battery.


In some embodiments, the key 10 is configured to communicate with a plurality of security devices 12 for initially programming the key with respective codes for each of the security devices. Thus, the key 10 may be initially programmed by communicating with the security devices 12. Such programming could be carried out for a predetermined period of time and once the time has expired, the key 10 stores all codes associated with the security devices 12 for which it can communicate with for arming and/or disarming thereof. After the programming of the key 10 has been completed, the key may then communicate with each security device 12 to arm and/or disarm the security device upon the code communicated by the key matching the code stored by the security device. Alternatively, the security device 12 may communicate with a plurality of keys 10 for receiving and storing respective codes for each of the keys. Therefore, in some cases, the programming station 32 is not required to program the key 10 and/or the security device 12. In some embodiments as discussed above, the programming station 32 may be used to refresh the key 10. Thus, the programming station 32 may only be employed to refresh the key 10 after the key has timed out but does not otherwise function to program a code into the key.


The foregoing has described one or more embodiments of a key for a security device or security packaging of the type commonly used to display an item of merchandise, a security device, and a system. Embodiments of a key, security device, and system have been shown and described herein for purposes of illustration. Those of ordinary skill in the art, however, will readily understand and appreciate that numerous variations and modifications of the invention may be made without departing from the spirit and scope of the invention.

Claims
  • 1. A system for securing retail merchandise from theft, the system comprising: a security system comprising a monitoring circuit and a memory,wherein the memory is configured to store a plurality of codes associated with each of a plurality of keys based on communication with the keys, each of the plurality of keys having a different code,wherein any one of the plurality of keys is configured to communicate with a security device for disarming the monitoring circuit based on an authorization of a respective key.
  • 2. The system of claim 1, wherein each of the plurality of keys is configured to disarm the monitoring circuit of any one of a plurality of security devices using a respective code.
  • 3. The system of claim 1, wherein the code of each of the plurality of keys is provided by a manufacturer of the key.
  • 4. The system of claim 1, wherein the code of each of the plurality of keys is an identification code.
  • 5. The system of claim 1, wherein each of the plurality of keys is configured to be deauthorized such that the keys are incapable of disarming a security device, wherein the security system is configured to reauthorize any one of the plurality of keys based on an authorization of a respective key.
  • 6. The system of claim 5, wherein the security system comprises an authorization station for reauthorizing any one of the plurality of keys in response to communication therewith.
  • 7. The system of claim 6, wherein the authorization station does not program the code in each of the plurality of keys.
  • 8. The system of claim 6, wherein each of the plurality of keys is configured to communicate with the same authorization station for reauthorizing the key.
  • 9. The system of claim 6, wherein the authorization station is configured to reauthorize any one of the plurality of keys in response to wireless communication therewith.
  • 10. The system of claim 1, wherein each of the plurality of keys comprises a predetermined number of activations for disarming the security device, wherein the security system is configured to communicate with any one of the plurality of keys to reauthorize the key after the predetermined number of activations.
  • 11. The system of claim 10, wherein an activation comprises a communication between any one of the plurality of keys and the security device.
  • 12. The system of claim 1, wherein the security system comprises a plurality of security devices each configured to communicate with any one of the plurality of keys.
  • 13. The system of claim 1, wherein any one of the plurality of keys is configured to communicate with the security device for disarming the monitoring circuit based on a wireless authorization of a respective key.
  • 14. The system of claim 1, wherein the security device comprises the monitoring circuit and the memory.
  • 15. The system of claim 1, wherein any one of the plurality of keys is configured to communicate with the security device for disarming the monitoring circuit based on an authorization of a respective code.
  • 16. The system of claim 1, wherein the security device is configured to secure a cellular telephone or portable computer from theft, and wherein the security device is configured to be mounted to a display surface for allowing a customer to evaluate the cellular telephone or portable computer.
  • 17. The system of claim 1, wherein each of the plurality of keys comprises a mechanical component configured to physically engage the security device, and wherein each of the plurality of keys is configured to automatically communicate with the security device in response to engagement therewith.
  • 18. The system of claim 5, wherein each of the plurality of keys is configured to be inactivated after a predetermined period of time such the keys are incapable of disarming a security device, and wherein each of the plurality of keys is further configured to be reauthorized after the predetermined period of time to thereby be capable of disarming the security device.
  • 19. A method for securing retail merchandise from theft, the method comprising: communicating between a security system and a plurality of keys, the security system comprising a monitoring circuit and a memory;storing a plurality of codes associated with each of the plurality of keys in the memory based on communication with the keys, each of the plurality of keys having a different code; andcommunicating between any one of the plurality of keys and a security device for disarming the monitoring circuit based on an authorization of a respective key.
  • 20. The method of claim 19, wherein each of the plurality of keys is configured to be deauthorized such that the keys are incapable of disarming a security device, and wherein the method further comprises reauthorizing any one of the plurality of keys based on an authorization of a respective key.
  • 21. The method of claim 20, wherein reauthorizing comprises communicating between the security system and any one of the plurality of keys to reauthorize the key after a predetermined number of activations.
  • 22. The method of claim 19, wherein communicating between any one of the plurality of keys and the security device comprises transferring a signal to disarm the security device.
  • 23. The method of claim 19, wherein communicating between any one of the plurality of keys and the security device comprises automatically communicating in response to engagement of one of the plurality of keys with the security device.
  • 24. The method of claim 21, wherein reauthorizing comprises communicating between the security system and any one of the plurality of keys to reauthorize the key after a predetermined period of time.
CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. application Ser. No. 16/110,843, filed on Aug. 23, 2018, which is a continuation of U.S. application Ser. No. 15/526,194, filed on May 11, 2017, and now U.S. Pat. No. 10,087,659, which is a 371 national phase entry of International Application No. PCT/US2015/058941, filed Nov. 4, 2015, which claims the benefit of U.S. Provisional Application No. 62/081,233, filed Nov. 18, 2014, the disclosures of which are incorporated herein by reference in their entireties.

US Referenced Citations (166)
Number Name Date Kind
883335 O'Connor Mar 1908 A
3444547 Surek Oct 1965 A
3493955 Minasy Feb 1970 A
3641498 Hedin Feb 1972 A
3685037 Bennett Aug 1972 A
3780909 Callahan et al. Dec 1973 A
3848229 Perron et al. Nov 1974 A
4117465 Timblin Sep 1978 A
4250533 Nelson Feb 1981 A
4286305 Pilat et al. Aug 1981 A
4354613 Desai et al. Oct 1982 A
4486861 Harmel Dec 1984 A
4573042 Boyd et al. Feb 1986 A
4686513 Farrar et al. Aug 1987 A
4800369 Gomi Jan 1989 A
4851815 Enkelmann Jul 1989 A
4853692 Wolk Aug 1989 A
4926665 Stapley et al. May 1990 A
4980671 McCurdy Dec 1990 A
5005125 Farrar et al. Apr 1991 A
RE33873 Romano Apr 1992 E
5117097 Kimura et al. May 1992 A
5140317 Hyatt et al. Aug 1992 A
5151684 Johnsen Sep 1992 A
5170431 Dawson Dec 1992 A
5182543 Siegel et al. Jan 1993 A
5245317 Chidley Sep 1993 A
5367289 Baro et al. Nov 1994 A
5479799 Kilman et al. Jan 1996 A
5543782 Rothbaum et al. Aug 1996 A
5570080 Inoue Oct 1996 A
5589819 Takeda Dec 1996 A
5610587 Fujiuchi et al. Mar 1997 A
5640144 Russo et al. Jun 1997 A
5650774 Drori Jul 1997 A
5656998 Fujiuchi et al. Aug 1997 A
5701828 Benore et al. Dec 1997 A
5710540 Clement et al. Jan 1998 A
5745044 Hyatt et al. Apr 1998 A
5748083 Rietkerk May 1998 A
5764147 Sasagawa et al. Jun 1998 A
5767773 Fujiuchi et al. Jun 1998 A
5793290 Eagleson et al. Aug 1998 A
5808548 Sasagawa et al. Sep 1998 A
5836002 Morstein et al. Nov 1998 A
5838234 Roulleaux-Robin Nov 1998 A
5864290 Toyomi et al. Jan 1999 A
5905446 Benore et al. May 1999 A
5942978 Shafer Aug 1999 A
5942985 Chin Aug 1999 A
5955951 Wischerop et al. Sep 1999 A
5964877 Victor et al. Oct 1999 A
5982283 Matsudaira et al. Nov 1999 A
6005487 Hyatt et al. Dec 1999 A
6020819 Fujiuchi et al. Feb 2000 A
6037879 Tuttle Mar 2000 A
6043744 Matsudaira Mar 2000 A
6104285 Stobbe Aug 2000 A
6118367 Ishii Sep 2000 A
6122704 Hass et al. Sep 2000 A
6137414 Federman Oct 2000 A
6144299 Cole Nov 2000 A
6255951 De La Huerga Jul 2001 B1
6269342 Brick et al. Jul 2001 B1
6275141 Walter Aug 2001 B1
6300873 Kucharczyk et al. Oct 2001 B1
6304181 Matsudaira Oct 2001 B1
6308928 Galant Oct 2001 B1
6331812 Dawalibi Dec 2001 B1
6346886 De La Huerga Feb 2002 B1
6362726 Chapman Mar 2002 B1
6380855 Ott Apr 2002 B1
D457051 Davis May 2002 S
6384711 Cregger et al. May 2002 B1
6420971 Leck et al. Jul 2002 B1
6433689 Hovind et al. Aug 2002 B1
6441719 Tsui Aug 2002 B1
6474117 Okuno Nov 2002 B2
6474122 Davis Nov 2002 B2
6512457 Irizarry Jan 2003 B2
6525644 Stillwagon Feb 2003 B1
6531961 Matsudaira Mar 2003 B2
6535130 Nguyen et al. Mar 2003 B2
6564600 Davivs May 2003 B1
6578148 Beuchat et al. Jun 2003 B1
6604394 Davis Aug 2003 B2
6615625 Davis Sep 2003 B2
6677852 Landt Jan 2004 B1
6718806 Davis Apr 2004 B2
6819252 Johnston et al. Nov 2004 B2
6895792 Davis May 2005 B2
6961000 Chung Nov 2005 B2
7002467 Deconinck et al. Feb 2006 B2
7053774 Sedon et al. May 2006 B2
7102509 Anders et al. Sep 2006 B1
7385522 Belden, Jr. et al. Jun 2008 B2
D579318 Davis Oct 2008 S
7482907 Denison et al. Jan 2009 B2
7629895 Belden, Jr. et al. Dec 2009 B2
7698916 Davis Apr 2010 B2
7737843 Belden, Jr. et al. Jun 2010 B2
7737844 Scott et al. Jun 2010 B2
7737845 Fawcett et al. Jun 2010 B2
7737846 Belden, Jr. et al. Jun 2010 B2
7821395 Dension et al. Oct 2010 B2
7969305 Belden, Jr. et al. Jun 2011 B2
8542119 Sankey Sep 2013 B2
8884762 Fawcett et al. Nov 2014 B2
8890691 Fawcett et al. Nov 2014 B2
8896447 Fawcett et al. Nov 2014 B2
8994497 Grant et al. Mar 2015 B2
9135800 Fawcett et al. Sep 2015 B2
9171441 Fawcett et al. Oct 2015 B2
9269247 Fawcett et al. Feb 2016 B2
9396631 Fawcett et al. Jul 2016 B2
9478110 Fawcett et al. Oct 2016 B2
9501913 Fawcett et al. Nov 2016 B2
9576452 Fawcett et al. Feb 2017 B2
9659472 Fawcett et al. May 2017 B2
9858778 Fawcett et al. Jan 2018 B2
9984524 Fares et al. May 2018 B2
10013867 Fawcett et al. Jul 2018 B2
10062266 Fawcett et al. Aug 2018 B1
10087659 Grant Oct 2018 B2
10403122 Fawcett et al. Sep 2019 B2
20020024420 Ayala et al. Feb 2002 A1
20020024440 Okuno Feb 2002 A1
20020085343 Wu et al. Jul 2002 A1
20020185397 Sedon et al. Dec 2002 A1
20030058083 Birchfield Mar 2003 A1
20030120922 Sun et al. Jun 2003 A1
20030156740 Siegel et al. Aug 2003 A1
20030179606 Nakajima et al. Sep 2003 A1
20030206106 Deconinck et al. Nov 2003 A1
20040003150 Deguchi Jan 2004 A1
20040046027 Leone Mar 2004 A1
20040046664 Labit et al. Mar 2004 A1
20040160305 Remenih et al. Aug 2004 A1
20040201449 Denison et al. Oct 2004 A1
20050073413 Sedon et al. Apr 2005 A1
20050077995 Paulsen et al. Apr 2005 A1
20050165806 Roatis et al. Jul 2005 A1
20050231365 Tester et al. Oct 2005 A1
20050242962 Lind et al. Nov 2005 A1
20070131005 Clare Jun 2007 A1
20070144224 Scott et al. Jun 2007 A1
20070146134 Belden et al. Jun 2007 A1
20070159328 Belden et al. Jul 2007 A1
20070194918 Rabinowitz Aug 2007 A1
20080224655 Tilley et al. Sep 2008 A1
20080252415 Larson et al. Oct 2008 A1
20090096413 Partovi et al. Apr 2009 A1
20090112739 Barassi et al. Apr 2009 A1
20100238031 Belden, Jr. et al. Sep 2010 A1
20110084799 Ficko Apr 2011 A1
20110254661 Fawcett et al. Oct 2011 A1
20120047972 Grant et al. Mar 2012 A1
20130081434 Grant et al. Apr 2013 A1
20140225733 Fawcett et al. Aug 2014 A1
20150137976 Fawcett et al. May 2015 A1
20160358431 Fawcett et al. Dec 2016 A1
20170069184 Fawcett et al. Mar 2017 A1
20170236401 Fawcett et al. Aug 2017 A1
20180102031 Fawcett et al. Apr 2018 A1
20180363332 Grant et al. Dec 2018 A1
20190003209 Grant Jan 2019 A1
Foreign Referenced Citations (22)
Number Date Country
2465692 Nov 2004 CA
201297072 Aug 2009 CN
101583983 Nov 2009 CN
103189902 Jul 2013 CN
4405693 Aug 1995 DE
0745747 Dec 1996 EP
2353622 Feb 2001 GB
H1-192970 Aug 1989 JP
8279082 Oct 1996 JP
1997-259368 Oct 1997 JP
20142746 Jan 2014 JP
2001-0075799 Aug 2001 KR
2002-0001294 Jan 2002 KR
9009648 Aug 1990 WO
97031347 Aug 1997 WO
9923332 May 1999 WO
1999047774 Sep 1999 WO
2002043021 May 2002 WO
2004023417 Mar 2004 WO
2004093017 Oct 2004 WO
2007075960 Jul 2007 WO
2015038201 Mar 2015 WO
Non-Patent Literature Citations (49)
Entry
Petition for Inter Partes Review of U.S. Pat. No. 8,896,447, May 22, 2015, 62 pages (IPR 2015-01263).
Petition for Inter Partes Review of U.S. Pat. No. 7,737,843, Mar. 20, 2014, 64 pages (IPR 2014-00457).
<http:/www.videx.com/AC_PDFs/Product%20Sheets/CD-GM.pdf>; “Grand Mastesr Key”; 2 pages.
<http:/www.lockingsystems.com/Pfd_Files/nexgen_xt_SFIC.pdf>; “SFIC Locks NEXGEN XT”; 1 page.
Supplementary European Search Report for related European Patent Application No. EP 06 845 868.6 filed Dec. 20, 2006; date of completion of the search May 7, 2010; 7 pages.
Supplementary European Search Report for related European Patent Application No. EP 06 847 982.3 filed Dec. 20, 2006; date of completion of the search May 7, 2010; 3 pages.
Supplementary European Search Report for related European Patent Application No. EP 06 845 865.2 filed Dec. 20, 2006; date of completion of the search May 12, 2010; 4 pages.
Ligong Li, The First Office Action for Chinese Patent Application No. 2012102534555 dated Dec. 16, 2013, Chinese Patent Office, Beijing, China.
Ziwen Li, The Sixth Office Action for Chinese Patent Application No. 2006800481876, dated Feb. 17, 2014, 7 pages, Chinese Patent Office.
C. Naveen Andrew, First Office Action for Indian Patent Application No. 3187/CHENP/2008, dated Jan. 27, 2015, 2 pages, Indian Patent Office, India.
Petition for Inter Partes Review of U.S. Pat. No. 9,135,800, Apr. 14, 2016, 66 pages (IPR2016-00895).
Petition for Inter Partes Review of U.S. Pat. No. 9,135,800, Apr. 14, 2016, 64 pages (IPR2016-00896).
Petition for Inter Partes Review of U.S. Pat. No. 8,884,762, Apr. 14, 2016, 63 pages (IPR2016-00892).
Petition for Inter Partes Review of U.S. Pat. No. 9,269,247, Apr. 14, 2016, 65 pages (IPR2016-00899).
Petition for Inter Partes Review of U.S. Pat. No. 9,269,247, Apr. 14, 2016, 65 pages (IPR2016-00898).
Petition for Inter Partes Review of U.S. Pat. No. 7,737,846, Jun. 21, 2016, 73 pages (IPR2016-01241).
Extended European search report for Application No. 15198379.8, dated Apr. 13, 2016, 7 pages, European Patent Office, Munich, Germany.
Petition for Inter Partes Review of U.S. Pat. No. 9,396,631, Nov. 29, 2016, 65 pages (IPR2017-00344).
Petition for Inter Partes Review of U.S. Pat. No. 9,396,631, Nov. 29, 2016, 63 pages (IPR2017-00345).
Schneier, Bruce, Applied Cryptography: Protocols, Algorithms, and Source Code in C, 1994, John Wiley & Sons, Inc., New York, NY, Table of Contents and Excerpts, 14 pages.
Petition for Inter Partes Review of U.S. Pat. No. 7,737,844, Sep. 30, 2016, 76 pages (IPR2016-01915).
Examination Report from related European Application No. 15198379.8, dated Jan. 23, 2017 (7 pages).
Petition for Inter Partes Review of U.S. Pat. No. 9,576,452 dated Jan. 12, 2018, 73 pages (IPR2018-00481).
Daher, John K., et al., “Test Concept and Experimental Validation of the Use of Built-In-Test to Simplify Conducted Susceptibility Testing of Advanced Technology Integrated Circuits and Printed Circuit Boards”, 1990, Georgia Tech Research Institute, Georgia Institute of Technology, Atlanta, Georgia (5 pages).
New Webster's Dictionary and Thesaurus of the English Language, 1992, Lexicon Publications, Inc., Santa Barbara, California, Excerpt, p. 747.
McGraw-Hill Dictionary of Scientific and Technical Terms, Sixth Edition, 2003, The McGraw-Hill Companies, Inc., New York, New York, Excerpts, pp. 689-690, 1672.
McGraw-Hill Dictionary of Scientific and Technical Terms, Sixth Edition, 2003, The McGraw-Hill Companies, Inc., New York, New York, Excerpts, pp. 689-690, 1231.
Petition for Post-Grant Review of Claims 1-45 of U.S. Pat. No. 9,659,472, dated Oct. 17, 2017, 93 pages, (PGR2018-00004).
Final Written Decision for Inter Partes Review of U.S. Pat. No. 8,884,762, dated Sep. 28, 2017, 71 pages (IPR2016-00892).
Final Written Decision for Inter Partes Review of U.S. Pat. No. 9,269,247, dated Sep. 28, 2017, 78 pages (IPR2016-00898 and IPR2016-00899).
Final Written Decision for Inter Partes Review of U.S. Pat. No. 9,135,800, dated Oct. 12, 2017, 82 pages (IPR2016-00895 and IPR2016-00896).
Petition for Inter Partes Review of U.S. Pat. No. 9,478,110, Jul. 31, 2017, 68 pages (IPR2017-01900).
Clements, Alan. Computer Organization and Architecture: Themes and Variations, 2014. Cengage Learning, Stamford, CT, Excerpts, 4 pages.
Petition for Inter Partes Review of U.S. Pat. No. 9,478,110, Jul. 31, 2017, 71 pages (IPR2017-01901).
Final Written Decision for Inter Partes Review of U.S. Pat. No. 7,737,844, dated Mar. 28, 2018, 51 pages (IPR2016-01915).
Final Written Decision for Inter Partes Review of U.S. Pat. No. 7,737,846, dated Dec. 19, 2017, 34 pages (IPR2016-01241).
International Search Report and Written Opinion from corresponding International Application No. PCT/US2015/058941, dated Jan. 27, 2016 (8 pages).
Final Written Decision from Inter Partes Review Nos. IPR2017-00344 and IPR2017-00345 of U.S. Pat. No. 9,396,631, dated May 24, 2018 (94 pages).
Corrected Petition from Inter Partes Review No. IPR2018-01138 of U.S. Pat. No. 9,659,472 dated May 22, 2018 (71 pages).
Extended European Search Report from corresponding European Patent Application No. 15862110.2, dated Jul. 4, 2018 (9 pages).
First Office Action from corresponding Chinese Patent Application No. 2015800627966, dated Nov. 5, 2018 (10 pages).
Petition for Inter Partes Review of U.S. Pat. No. 10,062,266, dated Aug. 28, 2019, 75 pages (IPR2018-01553).
Final Written Decision from Inter Partes Review of U.S. Pat. No. 9,576,452, dated Jul. 16, 2019, 55 pages (IPR2018-00481).
Patent Owner's Preliminary Response from Inter Partes Review of U.S. Pat. No. 9,269,247, dated Jul. 19, 2016, 57 pages (IPR2016-00898).
Complaint from Civil Action No. 1:18-cv-02653, Southern District of Indiana, dated Aug. 28, 2018 (15 pages).
Excerpts, “Newton's Telecom Dictionary: The Official Dictionary of Telecommunications Networking and Internet.” 16th Edition, 2000, CMP Books, 2000.
Decision Denying Institution of Inter Partes Review of U.S. Pat. No. 10,062,266, dated Mar. 6, 2020, 30 pages (IPR2019-01553).
Final Written Decision of Inter Partes Review of U.S. Pat. No. 9,748,110, dated Feb. 12, 2019, 71 pages (IPR2017-01900 and IPR2017-01901).
Final Written Decision of Inter Partes Review of U.S. Pat. No. 9,659,472, dated Dec. 5, 2019, 55 pages (IIPR2018-01138).
Related Publications (1)
Number Date Country
20200270911 A1 Aug 2020 US
Provisional Applications (1)
Number Date Country
62081233 Nov 2014 US
Continuations (2)
Number Date Country
Parent 16110843 Aug 2018 US
Child 16872981 US
Parent 15526194 US
Child 16110843 US