The present disclosure relates generally to the field of physical locks and more particularly to a system and method for managing physical locks.
Access control problems exist in different commercial and personal environments such as self-storage facilities, warehouses, marinas, businesses, cargo shipping, home rentals, recreational activity locations, sports clubs and other locations. Different types of assets, whether physical or virtual, may be protected from general access through an access control feature such as a physical lock.
In some environments, over-locks are used as a form of secondary lock. For example, self-storage units are typically rented on a monthly basis. If a customer is delinquent and does not pay rent to the self-storage facility owner by an agreed-upon due date, the owner (i.e., landlord) has a right to prevent the customer from accessing the storage unit. Self-storage facility owners typically place an over-lock over the storage unit door, such as through a hasp that prevents opening of the door. The over-lock is utilized until the customer pays the delinquent past due balance on their account.
The process of placing and removing physical locks of any kind, including over-locks, can be quite burdensome, particularly at locations which may be rented to month-to-month customers. Additionally, if a lock combination becomes compromised or forgotten, it can be time-consuming and burdensome to change out the lock or change the combination and provide the rightful owner with the new combination. These types of challenges exist in a variety of access control environments involving physical locks. In addition, the cost of conventional locks can be prohibitive. Many conventional locks including over-locks are electronic and provide automated and remote locking/unlocking functions. Such locks oftentimes require significant capital improvements at various types of locations. Furthermore, electronic locks inherently require constant power, and their continuous twenty-four hour per day operation increases power consumption costs at locations where installed. Furthermore, as with any complex electronic device, electronic locks are subject to failure and malfunction, and can require costly repairs to be conducted by an electrician, if not ultimately requiring replacement.
Standard combination locks are a type of conventional physical lock. However, with various facilities at different types of locations utilizing a limited number of standard combination locks, habitually delinquent customers eventually begin to recognize the unlock codes, and these locks can become futile. The facility must then perpetually replace locks when the unlock codes associated with those locks have become known and compromised.
Despite problems as described above, it can be helpful in various access control scenarios to employ physical locks with a single override for all locks to permit re-setting of a combination or other form of unlocking the physical locks, particularly in environments where it is necessary or helpful to not include lock identifiers on the physical locks.
According to embodiments of the present disclosure, a single override or code reset device is maintained among a group of physical locks to enable the combination or unlock code of all locks to be set or reset. In various embodiments, the override is a physical key or physical screwdriver. In other embodiments, the override is a form of electronic key such as a mobile communications device, for example.
In various embodiments, each lock in the group of locks does not include a lock identifier. Each lock can be a combination lock where a combination of numbers, letters, characters or symbols is employed to unlock the lock. The single override device can be employed to render the combination of each lock settable. For example, upon request such as where a user has forgotten a combination or where an unlock code has been compromised, a physical override key can be inserted into an appropriate keyhole in each of the physical locks and placed into a “set” position whereupon the combination of a given physical lock can be set. Once the combination is set, the key can be placed into a “finished” or “combination locked” position whereby the established combination is now fixed unless and until it is reset again in the future. In various embodiments, each lock is set to a different combination prior to deployment and/or use. At such time the combination is set for each lock, the combination and lock are stored such as in a database. In embodiments where the lock does not have a unique lock identifier, the combination can be associated with a given unit or location. The association with the unit could happen by entering and/or selecting a unit from within a related software program or scanning an identifier such as a quick response (QR) code on the unit or at a location for multiple units, for example. In the event a combination is forgotten, the user can request the combination in various ways, including by using a mobile communications device to request the unlock combination via a software application or via request to an external system.
These and other embodiments of the disclosure will be discussed with reference to the following exemplary and non-limiting illustrations, in which like elements are numbered similarly, and where:
The presently disclosed subject matter now will be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the presently disclosed subject matter are shown. Like numbers refer to like elements throughout. The presently disclosed subject matter may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Indeed, many modifications and other embodiments of the presently disclosed subject matter set forth herein will come to mind to one skilled in the art to which the presently disclosed subject matter pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the presently disclosed subject matter is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. In addition, the present disclosure describes, among other things, a lock and single override management system. Although the system is described with respect to its application in certain environments and locations, it is understood that the system could be implemented in any setting where access control may be useful.
It will be appreciated that reference to “a”, “an” or other indefinite article in the present disclosure encompasses one or more than one of the described element. Thus, for example, reference to a lock may encompass one or more locks, a communications device may encompass one or more communications devices and so forth.
In embodiments where the physical locks include a keyhole 22, it will be appreciated that a single physical override key 24 can be provided which is operable to engage the keyhole 22 of each physical lock (e.g., 12, 14, 16, 18) in order to place the lock in a combination reset mode, whereupon a user can reset an established combination lock to accommodate a variety of scenarios. A set screw integrated into a physical lock is another physical item that can permit resetting of specific physical locks. In such devices, after the proper unlock code is entered, the set screw can be rotated such as with a screwdriver, thereby allowing the unlock code to be reset to a different code, after which the set screw can be rotated back to the original position, setting the lock to be opened only by the different, newly set code. Near field communication (NFC) technology can also be employed to electronically reset the unlock code according to various embodiments of the present disclosure where the physical lock is NFC capable. In such embodiments, a replacement unlock code can be generated by a lock management software application, which can be operable by a mobile communications device or a remote server, for example, wherein the software application generates or transmits the replacement unlock code for/to the mobile communication device. Once the replacement unlock code is generated by or received by the mobile communications device, the mobile communications device can be held up to the NFC-capable physical lock. Through near field communication, the mobile communications device charges the internal power source within the physical lock and transmits the replacement unlock code to a processor within the physical lock. The processor within the lock then executes a function to manipulate internal elements within the lock, such as a solenoid, worm screw, internal mechanics and/or circuitry to adjust lock setting elements such as internal pins of the physical lock so that the replacement unlock code will be usable to unlock the lock thereafter.
Resetting of the lock code can be employed in different situations. For example, a user may set or reset a combination lock once the lock is received and ready to be installed in an environment. A user may also reset a combination lock when the lock is being re-used by a different party from the original party to which the lock was assigned. Further, a user may reset a combination lock if the original or current combination has been compromised and unauthorized parties are able to open the lock and access assets intended to be protected via the lock. Even further, a user may reset a combination if an owner or customer has somehow forgotten the combination and provides one or more credentials indicating the owner or customer is the proper party to request a resetting of the combination to thereby give the owner or customer proper access. By providing a single override key 24, an operator or manager of an access-controlled facility can easily establish, maintain, operate and reset a large number of physical locks for a variety of purposes. Further, such environments do not require a label or lock identifier which, if included, may potentially compromise security if an unscrupulous party has knowledge of associated lock identifiers and unlock codes.
In various embodiments, a customer's access to a location is restricted by a physical lock 12, 14 as illustrated in
In various embodiments, one or more users such as a customer or facility personnel can use a mobile communications device (e.g., 30, 32), such as a mobile phone, to access a software application available via, or having access to, an unlock code manager 50. The software application can be a proprietary program created and/or owned by a facility such as a self-storage facility, and which can be downloaded by the user via their device 30 and/or 32 from, for example, a website operated by or in communication with the unlock code manager 50, the Apple iTunes App Store®, the Android App Store®, and the like accessible over a network 40. The unlock code manager 50 can be part of a controlled access system (CAS) or in communication via network 40 with a CAS (not shown).
The software application can facilitate communication between the mobile device 30, 32 and the unlock code manager 50, which can be provided with a processor 52 and database 54, for example. The database 54 can store associated relationships between users, mobile communications devices, mobile telephone numbers, physical locks and/or unlock/combination codes, for example.
In various embodiments, the software application is a website accessed via one or more URLs using a browser on the mobile device 30 and/or 32. In such embodiments, the system can receive an indication from a communications device and thereafter provide access to a URL to the communications device such as via the software application. The system can further receive, via the URL, a credential associated with the customer and/or the communications device, determine whether the customer is authorized to reset and/or view the unlock code associated with the physical lock and, upon the customer being authorized to receive the unlock code, initiate actions to reset the code and/or display the unlock code at the web page accessed via the URL. In accordance with the present disclosure, the communications device, a customer account, and/or a customer mobile phone number can be associated with the physical lock and the unlock code in the database 54.
It will be appreciated that the mobile communications device 30,32 is not limited to a mobile phone, and can include tablets, wearable devices, personal digital assistants (PDAs), laptop computers, “smart” watches, “smart” glasses, and any other device capable of receiving input from the customer, and which is capable of being connected to the network 40.
As exemplified above, the software application can include an interface that displays the unlock code. Upon seeing the displayed unlock code, the customer can then unlock the lock (12 or 14), and gain access to the desired access-controlled environment. In this way, if a user forgets an unlock code, or if an unlock code is reset such as described herein, the user can obtain the unlock code via a readily available mobile communications device to obtain access to a locked environment or location to which the user has permission to access. Further, while outside personnel may be involved in resetting an unlock code for a lock, outside personnel is not required to be present or otherwise participate in assisting the user with gaining access to the location, which may occur at a different time from the time when the unlock code was reset.
It will be appreciated that the unlock code manager 50 can be part of, or connected to, an access-controlled location or a management site via network 40. The management site can be remote from the access-controlled location and can serve multiple distributed access-controlled locations, such as in a central management site. In various embodiments, the management site can be located overseas, such as in a foreign call center.
Environments and/or locations in which embodiments of the present disclosure may operate include education and membership environments with locks on school lockers and/or sports club lockers, transportation environments with locks on cargo containers, utility environments with locks on natural gas meters, transformer boxes or other physical utility feature, marinas and boat storage environments with locks on boats such as may be used to secure the boats to a dock or a mooring piling, parcel delivery environments where locks are used to secure containers for at-home delivery, shared transport environments such as may be used for temporary use of bikes, scooters, and other forms of transportation, for example.
The network 40 may be any type of network suitable to allow interaction between devices, such as a mobile device 30, 32 located at the access-controlled location and the unlock code manager 50. For example, the network 40 may be a wired network, a wireless network, or any combination thereof. Further, the network 40 may include a distributed computing network, an intranet, a local-area network (LAN) and/or a wide-area network (WAN), or any combination thereof. For example, the LAN may make use of WIFI in its many variations and the WAN may make use of broadband, cellular and/or satellite networks using technologies including, but not limited to, CDPD, CDMA, GSM, PDC, PHS, TDMA, FLEX, ReFLEX, iDEN, TETRA, DECT, DataTAC, Mobitex, EDGE and other 2G, 3G, 4G and LTE technologies. However, those of ordinary skill in the art will appreciate that the network 40 is not limited thereto.
As used herein, the term “customer” can include a renter, client, tenant, lessee, user, or an authorized agent. Although the present disclosure may be described in instances with respect to self-storage facilities, it will be appreciated that embodiments of the present disclosure can be implemented in any setting where access control as secured by a lock may be useful, such as hotel rooms, apartment buildings, storage containers, short-term housing rentals, lockers and other environments as described herein, for example. In addition, the present disclosure can be implemented within a controlled access system (CAS), such as for equipment rooms, vaults, hospitals, airports, government facilities, nuclear power facilities, water treatment facilities, weapon storage facilities, aircraft cockpits, and any other setting that requires restricted, selective, or monitored access.
Upon certain circumstances occurring, such as where a customer forgets the unlock code or where an unlock code has been compromised and requires changing, embodiments as described herein can facilitate resetting and release of an unlock code for the lock.
In various embodiments, the unlock code manager 50 can determine if the customer is authorized to reset or view the unlock code. It will be appreciated that the customer can designate authorized parties beyond the customer to request a resetting of the unlock code and/or to receive the unlock code. For example, a customer's spouse, authorized agents, business associates, attorneys, and any other parties whom the customer wishes to have access to the access-controlled location can have their credentials associated with the access-controlled location. In such embodiments, the database record for the lock(s) at the access-controlled location includes a listing of all authorized parties and their respective credentials.
A communications device 80 is provided and associated with environment A, another communications device 82 is provided and associated with environment B, another communications device 84 is provided and associated with environment C and another communications device 86 is provided and associated with environment D. In various embodiments, two or more of devices 80, 82, 84, 86 can be the same device. In environment B, the group 72 of locks can be electronic locks capable of communication with a device such as communications device 82, which can be provided with programming for interacting with each lock of the group 72 to initiate a change in the unlock code for any given lock of the group 72 of locks. In environment D, the group 76 of locks can be electronic locks capable of communication with a device such as communications device 86, which can be provided with programming for interacting with each lock of the group 76 to initiate a change in the unlock code for any given lock of the group 76 of locks. In environments B and D, each lock in the respective groups 72, 76 may include an identifier 79 enabling the respective communications device 82, 86 to communicate with a specific lock. Such an identifier 79 can be a quick response (QR) code or a near field communication (NFC) tag, for example. Further, each lock in the groups 72, 76 of locks can include a processor and memory storing instructions facilitating communications with devices 82, 86 and unlock code manager 50 and further permitting an unlock code to be changed.
Thus, as shown in
In various embodiments, an earlier unlock code such as the original unlock code is de-associated with a physical lock and the replacement unlock code is then associated with the physical lock in the database 54. In various embodiments, the request is received from the code reset and/or override device. In various embodiments, the code reset and/or override device is the mobile communications device. In various embodiments, the code reset and/or override device is different from the mobile communications device. For example, the code reset device can be a physical key, which can be provided with a processor, memory and display in various embodiments.
In various embodiments, associating each of the plurality of unlock codes with a respective physical lock from the group of physical locks involves receiving a selection of a respective physical location from a group of physical locations as presented in a graphical user interface (GUI) in communication with the database 54. For example, a user setting or resetting the unlock code(s) may have a GUI from a software application presented on a display of a mobile communications device such as 30, 32 in
In various embodiments, each lock in the group of locks for a particular environment, location and/or facility does not include a lock identifier. Each lock can be a combination lock where a combination of numbers is employed to unlock the lock. A single override key can be employed to render the combination of each lock settable. For example, the key can be inserted into an appropriate keyhole in each of the physical locks and placed into a “set” position whereupon the combination of a given physical lock can be set. Thus, the physical key is operable to engage and/or interact with each of the physical locks at one or more given locations, facilities or environments, and the engagement of the physical key with any of the physical locks permits the previously (e.g., original) operable unlock code to be changed to a replacement unlock code.
Once the combination is set, the key can be placed into a “finished” or “combination locked” position whereby the established combination is now fixed unless and until it is reset again in the future. In various embodiments, each lock is set to a different combination prior to deployment and/or use. At such time the combination is set for each lock, the combination and lock are stored such as in a database 54 in
While embodiments of the present disclosure have been described whereby there are no unique lock identifiers associated with respective physical locks, it will be appreciated that embodiments of the present disclosure can operate with lock identifiers, such as described with respect to environments B and D in
In various embodiments such as with regard to environments A and C, the replacement unlock code can be displayed on a key override device such as 71, 73 operable to engage each of the locks. In various embodiments, the override device may be a communications device such as 82, 86 in
In various embodiments, the unlock code can be a temporary unlock code which expires after a pre-determined period of time, or a one-time-use unlock code.
In certain embodiments in which the system includes a computing device, such as a mobile communications device, a CAS server, an unlock code manager, an electronic lock, etc., the computing device is any suitable computing device (such as a server) that includes at least one processor and at least one memory device or data storage device. As further described herein, the computing device includes at least one processor configured to transmit and receive data or signals representing events, messages, commands, or any other suitable information between the computing device and other devices. The processor of the computing device is configured to execute the events, messages, or commands represented by such data or signals in conjunction with the operation of the computing device.
It will be appreciated that any combination of one or more computer readable media may be utilized. The computer readable media may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing, including a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an appropriate optical fiber with a repeater, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable signal medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
As will be appreciated by one skilled in the art, aspects of the present disclosure may be illustrated and described herein in any of a number of patentable classes or context including any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof. Accordingly, aspects of the present disclosure may be implemented entirely hardware, entirely software (including firmware, resident software, micro-code, etc.) or combining software and hardware implementation that may all generally be referred to herein as a “circuit,” “module,” “component,” or “system.” Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in one or more computer readable media having computer readable program code embodied thereon.
It will be appreciated that all of the disclosed methods and procedures herein can be implemented using one or more computer programs or components. These components may be provided as a series of computer instructions on any conventional computer-readable medium, including RAM, SATA DOM, or other storage media. The instructions may be configured to be executed by one or more processors which, when executing the series of computer instructions, performs or facilitates the performance of all or part of the disclosed methods and procedures.
Unless otherwise stated, devices or components of the present disclosure that are in communication with each other do not need to be in continuous communication with each other. Further, devices or components in communication with other devices or components can communicate directly or indirectly through one or more intermediate devices, components or other intermediaries. Further, descriptions of embodiments of the present disclosure herein wherein several devices and/or components are described as being in communication with one another does not imply that all such components are required, or that each of the disclosed components must communicate with every other component. In addition, while algorithms, process steps and/or method steps may be described in a sequential order, such approaches can be configured to work in different orders. In other words, any ordering of steps described herein does not, standing alone, dictate that the steps be performed in that order. The steps associated with methods and/or processes as described herein can be performed in any order practical. Additionally, some steps can be performed simultaneously or substantially simultaneously despite being described or implied as occurring non-simultaneously.
It will be appreciated that algorithms, method steps and process steps described herein can be implemented by appropriately programmed computers and computing devices, for example. In this regard, a processor (e.g., a microprocessor or controller device) receives instructions from a memory or like storage device that contains and/or stores the instructions, and the processor executes those instructions, thereby performing a process defined by those instructions. Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in one or more computer readable media having computer readable program code embodied thereon.
Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB.NET, Python or the like, conventional procedural programming languages, such as the “C” programming language, Visual Basic, Fortran 2003, Perl, COBOL 2002, PHP, ABAP, dynamic programming languages such as Python, Ruby and Groovy, or other programming languages. The program code may execute entirely on a user's computer, partly on a user's computer, as a stand-alone software package, partly on a user's computer and partly on a remote computer or entirely on the remote computer or server.
Where databases are described in the present disclosure, it will be appreciated that alternative database structures to those described, as well as other memory structures besides databases may be readily employed. The drawing figure representations and accompanying descriptions of any exemplary databases presented herein are illustrative and not restrictive arrangements for stored representations of data. Further, any exemplary entries of tables and parameter data represent example information only, and, despite any depiction of the databases as tables, other formats (including relational databases, object-based models and/or distributed databases) can be used to store, process and otherwise manipulate the data types described herein. Electronic storage can be local or remote storage, as will be understood to those skilled in the art. Appropriate encryption and other security methodologies can also be employed by the system of the present disclosure, as will be understood to one of ordinary skill in the art.
Although the present approach has been illustrated and described herein with reference to preferred embodiments and specific examples thereof, it will be readily apparent to those of ordinary skill in the art that other embodiments and examples may perform similar functions and/or achieve like results. All such equivalent embodiments and examples are within the spirit and scope of the present approach.
Number | Name | Date | Kind |
---|---|---|---|
4870400 | Downs et al. | Sep 1989 | A |
5964110 | Crocco et al. | Oct 1999 | A |
7047773 | Lin | May 2006 | B1 |
7236085 | Aronson et al. | Jun 2007 | B1 |
8108927 | Michelle et al. | Jan 2012 | B2 |
8774714 | Metivier | Jul 2014 | B2 |
9464460 | Lai | Oct 2016 | B2 |
9524600 | Yong et al. | Dec 2016 | B2 |
9908697 | Ufkes | Mar 2018 | B2 |
10124765 | Wilt et al. | Nov 2018 | B2 |
10614646 | Boss et al. | Aug 2020 | B1 |
20020059114 | Cockrill et al. | May 2002 | A1 |
20030061192 | McGunn et al. | Mar 2003 | A1 |
20030208647 | Kumar | Nov 2003 | A1 |
20040030934 | Mizogushi et al. | Apr 2004 | A1 |
20050154605 | Tropp | Jul 2005 | A1 |
20050216673 | Kumar | Sep 2005 | A1 |
20050237149 | Loftin et al. | Oct 2005 | A1 |
20050241003 | Sweeney et al. | Oct 2005 | A1 |
20070214369 | Roberts et al. | Sep 2007 | A1 |
20080246583 | Blake et al. | Oct 2008 | A1 |
20090083851 | Michelle | Mar 2009 | A1 |
20090256676 | Piccirillo et al. | Oct 2009 | A1 |
20090328203 | Hass | Dec 2009 | A1 |
20120169461 | Dubois | Jul 2012 | A1 |
20130024528 | Gallant et al. | Jan 2013 | A1 |
20130139408 | Chaiken | Jun 2013 | A1 |
20130335193 | Hanson et al. | Dec 2013 | A1 |
20140062656 | Bowen | Mar 2014 | A1 |
20140207499 | Fleiss et al. | Jul 2014 | A1 |
20140207657 | Gacs | Jul 2014 | A1 |
20140266585 | Chao et al. | Sep 2014 | A1 |
20150077223 | Pipes | Mar 2015 | A1 |
20150078137 | Lee et al. | Mar 2015 | A1 |
20150186840 | Torres et al. | Jul 2015 | A1 |
20150199859 | Ouyang et al. | Jul 2015 | A1 |
20150199863 | Scoggins et al. | Jul 2015 | A1 |
20150356801 | Nitu et al. | Dec 2015 | A1 |
20160063235 | Tussy | Mar 2016 | A1 |
20160155293 | Reaves et al. | Jun 2016 | A1 |
20160173595 | Miller et al. | Jun 2016 | A1 |
20170161978 | Wishne | Jun 2017 | A1 |
20170236352 | Conrad et al. | Aug 2017 | A1 |
20180115595 | Krishnan et al. | Apr 2018 | A1 |
20180216364 | Wind et al. | Aug 2018 | A1 |
20180230713 | Sidhu et al. | Aug 2018 | A1 |
20180253786 | Frisby et al. | Sep 2018 | A1 |
20180350170 | Wang et al. | Dec 2018 | A1 |
20190259232 | Nandakumar | Aug 2019 | A1 |
20190371101 | Friedli | Dec 2019 | A1 |
20200190854 | Tropp | Jun 2020 | A1 |
20200318389 | Lou | Oct 2020 | A1 |
20200378155 | Zhang et al. | Dec 2020 | A1 |
20220076514 | Lingala et al. | Mar 2022 | A1 |
Number | Date | Country |
---|---|---|
111599048 | Aug 2020 | CN |
2799646 | Nov 2014 | EP |
2012047850 | Apr 2014 | WO |
Entry |
---|
Hung et al., “A Door Lock System with Augmented Reality Technology”, 2017 IEE 6th Global Conference on Consumer Electronics (GCCE 2017). |
Defendant's Answer to Second Amended Complaint and Counterclaim, DaVinci Lock, LLC v. SpiderDoor, LLC, Civil Action No. 2:23-cv-00343-NAD, U.S. District Court for the Northern District of Alabama, Jul. 19, 2023. |
Plaintiffs' Reply in Support of Their Motion for Preliminary Injunction, DaVinci Lock, LLC v. SpiderDoor, LLC, Civil Action No. 2:23-cv-00343-CLM, U.S. District Court for the Northern District of Alabama, Aug. 1, 2023. |
Defendant's Opposition to Amended Motion for Preliminary Injunction, DaVinci Lock, LLC v. SpiderDoor, LLC, Civil Action No. 2:23-cv-00343-NAD, U.S. District Court for the Northern District of Alabama, Jul. 14, 2023. |
Order, DaVinci Lock, LLC v. SpiderDoor, LLC, Civil Action No. 2:23-cv-00343-CLM, U.S. District Court for the Northern District of Alabama, Jan. 4, 2024. |
United States Patent and Trademark Office (USPTO), Non-final Office Action, U.S. Appl. No. 18/196,007, filed Aug. 11, 2023. |
United States Patent and Trademark Office (USPTO), Final Office Action, U.S. Appl. No. 18/196,007, filed Oct. 13, 2023. |
United States Patent and Trademark Office (USPTO), Non-Final Office Action, U.S. Appl. No. 18/196,007, filed Feb. 20, 2024. |
United States Patent and Trademark Office (USPTO), Final Office Action, U.S. Appl. No. 18/196,007, filed Apr. 8, 2024. |
Response to United States Patent and Trademark Office (USPTO), Non-final Office Action, U.S. Appl. No. 18/196,007, filed Sep. 28, 2023. |
Response to United States Patent and Trademark Office (USPTO), Final Office Action, U.S. Appl. No. 18/196,007, filed Jan. 16, 2024. |
Response to United States Patent and Trademark Office (USPTO), Non-final Office Action, U.S. Appl. No. 18/196,007, filed Mar. 14, 2024. |
Response to United States Patent and Trademark Office (USPTO), Final Office Action, U.S. Appl. No. 18/196,007, filed Apr. 12, 2024. |
United States Patent and Trademark Office (USPTO), Non-final Office Action, U.S. Appl. No. 17/994,596, filed Apr. 5, 2023. |
United States Patent and Trademark Office (USPTO), Response to non-final Office Action, U.S. Appl. No. 17/994,596, filed Oct. 3, 2023. |
United States Patent and Trademark Office (USPTO), Final Office Action, U.S. Appl. No. 17/994,596, filed Oct. 23, 2023. |