ELECTRONICALLY ACTIVATED GUN SAFE HAVING BUILT-IN ALARM AND RECORDING CAPABILITIES

Methods, systems and computer readable media for an electronically activated gun safe having built-in alarm and recording capabilities, are described.

Skip to: Description  ·  Claims  · Patent History  ·  Patent History
Description
TECHNICAL FIELD

Embodiments relate generally to gun safes, and more particularly, to methods, systems and computer readable media for an electronically activated gun safe having built-in alarm and recording capabilities.

BACKGROUND

It is imperative to keep handguns (or other firearms or weapons) out of the hands of children, thieves, of any unauthorized users. There are conventional small safes for locking up handguns. Typically, such safes are small portable safes, which may be easily carried off by thieves. Also, they are not easily disguised or proportioned to be hidable to reduce the possible discovery of their location and access thereinto by either a curious child or potential thief.

Some of these safes have combination locks, which can be unsatisfactory in that a gun stored in the safe cannot be quickly withdrawn because of the time for manipulation of the lock and the need for visibility of the lock, which makes night-time entry difficult. Thus, in the event of danger such as the encountering of a burglar at night, it is difficult to retrieve a handgun quickly without making noises or turning on lights. Under such times of stress, not only is fast action necessary, but a routine for removal of the handgun into a ready to use posture is necessary which is not apt to be aborted by the need to access the safe quietly and rapidly, or simply because of nerves in the excitement of the moment that makes a combination inoperable. With the operation of a combination lock necessary, for example, an aborted attempt to open the safe to retrieve a hand gun could end up as a fatality because the combination was not handy or because in the excitement and need for fast action the combination was entered incorrectly or the unlocking process was noisy or required turning on a light.

Similar problems are encountered with key operated safes. To find the key in times of stress in the presence of a middle-of-the-night intruder, for example, one may not be able to turn on a light to search for the key hidden in a drawer which could not be opened without possibility of a tell-tale noise, or a possibility of stumbling over an object trying to get to the key hiding place, thus being apt to make noises in the attempt that would possibly alert a burglar.

It would be desirable therefore to have a handgun safe that would permit a loaded handgun to be stored in a position available for immediate use and preferably a safe of a size that could easily be secreted so that it would be hard to locate.

In the case of storing a handgun in a household with minor children, special precautions must be taken to keep that gun secretly stored and if found, still inaccessible to the children because the safe is child-proof enough that it could not be easily opened. Also, the ability to hide the safe and its contents from potential theft is important.

Even with these pressing demands for better solutions, no known safes have been introduced which would satisfy the aforementioned safety and access conditions and avoid the problems. Gun safes in the prior art are typically small safes which are made and locked in a conventional way and depend upon keys or combinations for preventing access to a gun. Thus, there is a special need for a satisfactory improved and innovative handgun safe.

Thus, multiple solutions have been presented in prior art in terms of presenting safes for lockers. However, these solutions are limited and restricted to their conventional systems.

The present disclosure presents an assembly which is directed toward a camera equipped, button and remote activated gun safe that stores almost any handgun/pistol. One purpose of the disclosed safe is to have a gun or multiple guns hidden and locked away from everyone until harm is near or the gun is otherwise needed.

Thus, to Applicant's knowledge, none of these prior art methods have been found to be completely suitable to meet these needs and are cumbersome. Thus, there is a need in the prior art in which the aforementioned inconveniences, difficulties, and grooming problems are, for all practical purposes, reduced or eliminated. Thus, the present disclosure provides such a device and method where the overall combination of the features disclosed herein is not seen to have been provided by the conventional examples mentioned above.

Some implementations were conceived in light of the above-mentioned needs, problems and/or limitations, among other things.

SUMMARY

In light of the disadvantages of some conventional safes discussed above, the following summary is provided to facilitate an understanding of some of the innovative features unique to the present disclosure.

A prime objective of the present invention is to provide an improved safe for storing any type of gun, such as a handgun, rifle, shotgun, or other long gun, where the safe includes advanced features.

For example, an objective of the present disclosure is to provide an improved safe for storage of a handgun.

Another objective of the present disclosure is to provide a fast access, childproof safe especially adapted for storing a handgun.

Yet another objective of the present disclosure is to provide a safe which is equipped with security motion detection, two-way audio, video (e.g., 1080p full HD video), alert, night vision, and temperature monitoring camera.

Still another objective of the present disclosure is to provide motion alert notification that can be sent to either a computer, cellphone, or tablet, alerting motion near the safe.

Another objective of the present disclosure is to provide a safe for storing handguns which sustains its effectiveness over repeated usage and longer period of time.

This Summary is provided merely for the purpose of summarizing some example implementations, so as to provide a basic understanding of some aspects of the subject matter described herein. Accordingly, it will be appreciated that the above-described features are merely examples and should not be construed to narrow the scope or spirit of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following Detailed Description, Figures, and Claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a network environment configured for use with an implementation of the safe and corresponding application software in accordance with some implementations.

FIG. 2 is a flowchart showing an example method of locking and unlocking a safe in accordance with some implementations.

FIG. 3 is a flowchart showing an example method of recording and transmitting data from a safe in accordance with some implementations.

FIG. 4 is a diagram showing an example safe mobile application user interface in accordance with some implementations.

FIG. 5 is a diagram showing an example safe in an open state in accordance with some implementations.

FIG. 6 is a diagram showing an example safe in a closed state in accordance with some implementations.

FIG. 7 is a diagram showing an example safe lid in accordance with some implementations.

FIG. 8 is a diagram showing an example safe base in accordance with some implementations.

FIG. 9 is a diagram of an example computing device configured for electronic employment document control in accordance with at least one implementation.

DETAILED DESCRIPTION

In general, some implementations can include a magnetically locked gun safe assembly that can be hidden in a wall and covered by a picture or other wall decoration. The assembly can be equipped with a security motion detection device, a two-way audio sensor, 1080p full HD video, alert, night vision, and temperature monitoring camera. The motion alert notification can be sent to either a computer, cellphone, or tablet alerting one or more users of motion near the safe. Video and pictures of the motion are captured, saved and sent as a notification alert.

In some implementations, the safe can be activated from the master controller anywhere by using the get home safe application. If on the premises of the Get Home Safe the safe can be open by a hidden wired access button in the master control room, wireless Bluetooth remote, or the Get Home Safe mobile app on any electronic device.

The assembly as per its further embodiments can be stored in any drywall, brick wall, or metal wall. The safe is securely bolted to the studs or the base of the wall and wires are hidden and connected inside the wall.

Some implementations can include a steal box that's opens, closes and locks by a 350 lbs. electromagnetic lock. The lock can be powered by wires that run behind the wall where the safe is placed. The safe can be put together by welding. The interior brackets that secure the camera and gun in places are welded to the inside of the steal box. A drill is used to drill the holes for the camera to see and wires to come out of the back of the safe. A bracket for the magnetic lock is welded in place to hold the lock. A metal plate is welded at the tops of the safe for the magnetic lock to lock to. The brackets holding the gun have slots cut in them to fit a Velcro strap to hold the gun in a stable position.

FIG. 1 illustrates a block diagram of an example network environment 100, which may be used in some implementations described herein. In some implementations, network environment 100 includes one or more server systems, e.g., server system 102 in the example of FIG. 1. Server system 102 can communicate with a network 130, for example. Server system 102 can include a server device 104, a database 106 or other data store or data storage device, and a safe server application (e.g., the Get Home Safe server application). Network environment 100 also can include one or more client devices, e.g., client devices 120 (e.g., user mobile device with Get Home Safe mobile app 121), 122 (e.g., a safe as described herein), 124, and 126, which may communicate with each other and/or with server system 102 via network 130. Network 130 can be any type of communication network, including one or more of the Internet, local area networks (LAN), wireless networks, switch or hub connections, etc. In some implementations, network 130 can include peer-to-peer communication 132 between devices, e.g., using peer-to-peer wireless protocols.

For ease of illustration, FIG. 1 shows one block for server system 102, server device 104, and database 106, and shows four blocks for client devices 120, 122, 124, and 126. Some blocks (e.g., 102, 104, and 106) may represent multiple systems, server devices, and network databases, and the blocks can be provided in different configurations than shown. For example, server system 102 can represent multiple server systems that can communicate with other server systems via the network 130. In some examples, database 106 and/or other storage devices can be provided in server system block(s) that are separate from server device 104 and can communicate with server device 104 and other server systems via network 130. Also, there may be any number of client devices. Each client device can be any type of electronic device, e.g., a safe according to the present disclosure, a desktop computer, a laptop computer, portable or mobile device, camera, cell phone, smart phone, tablet computer, television, TV set top box or entertainment device, wearable devices (e.g., display glasses or goggles, head-mounted display (HMD), wristwatch, headset, armband, jewelry, etc.), virtual reality (VR) and/or augmented reality (AR) enabled devices, personal digital assistant (PDA), media player, game device, etc. Some client devices may also have a local database similar to database 106 or other storage. In other implementations, network environment 100 may not have all of the components shown and/or may have other elements including other types of elements instead of, or in addition to, those described herein.

In various implementations, end-users U1, U2, U3, and U4 may communicate with server system 102 and/or each other using respective client devices 120, 122, 124, and 126. In some examples, users U1, U3, and U4 may interact with each other via applications running on respective client devices and/or server system 102, and/or via a network service, e.g., an image sharing service, a messaging service, a social network service or other type of network service, implemented on server system 102. For example, respective client devices 120, 122, 124, and 126 may communicate data to and from one or more server systems (e.g., server system 102). In some implementations, the server system 102 may provide appropriate data to the client devices such that each client device can receive communicated content or shared content uploaded to the server system 102 and/or network service. In some examples, the users can interact via audio or video conferencing, audio, video, or text chat, or other communication modes or applications. In some examples, the network service can include any system allowing users to perform a variety of communications, form links and associations, upload and post shared content such as images, image compositions (e.g., albums that include one or more images, image collages, videos, etc.), audio data, and other types of content, receive various forms of data, and/or perform socially related functions. For example, the network service can allow a user to send messages to particular or multiple other users, form social links in the form of associations to other users within the network service, group other users in user lists, friends lists, or other user groups, post or send content including text, images, image compositions, audio sequences or recordings, or other types of content for access by designated sets of users of the network service, participate in live video, audio, and/or text videoconferences or chat with other users of the service, etc. In some implementations, a “user” can include one or more programs or virtual entities, as well as persons that interface with the system or network.

A user interface can enable display of images, image compositions, data, and other content as well as communications, privacy settings, notifications, and other data on client devices 120 (e.g., via get home safe mobile application 121), 122, 124, and 126 (or alternatively on server system 102). Such an interface can be displayed using software on the client device, software on the server device, and/or a combination of client software and server software executing on server device 104, e.g., application software or client software in communication with server system 102. The user interface can be displayed by a display device of a client device or server device, e.g., a display screen, projector, etc. In some implementations, application programs running on a server system can communicate with a client device to receive user input at the client device and to output data such as visual data, audio data, etc. at the client device.

In some implementations, server system 102 and/or one or more client devices 120-126 can provide gun safe functions as described herein.

Various implementations of features described herein can use any type of system and/or service. Any type of electronic device can make use of the features described herein. Some implementations can provide one or more features described herein on client or server devices disconnected from or intermittently connected to computer networks.

FIG. 2 is a flowchart showing an example method of locking and unlocking a safe in accordance with some implementations. Processing begins at 202, where an unlock signal is received at a safe (e.g., 122). The unlock signal can be generated via multiple ways - via mobile application (e.g., 121), via physical switch, or via biometric data (e.g., facial image, handprint or fingerprint, iris scan, voice print, etc.). Processing continues to 204.

At 204, based on the unlock signal, the safe deactivates an electromagnetic lock (e.g., 506) that secures the safe door. This permits the movable safe door to open to provide access to the handgun or other object stored in the safe. Processing continues to 206.

At 206, optionally, when the safe is unlocked, the safe can activate sensors such as video, audio, and heat sensors. Processing continues to 208.

At 208, the safe optionally records images and/or audio of the person opening the safe. The recorded data can be sent to the safe mobile application (e.g., 121) via the safe server application, or to another external system. Processing continues to 210.

At 210, a lock signal is received (e.g., via one of the methods mentioned above in 202). Processing continues to 212.

At 212, the electromagnetic lock of the safe is activated such that when the lid is closed, it will be secured to the base and the safe will be locked.

FIG. 3 is a flowchart showing an example method of recording and transmitting data from a safe in accordance with some implementations. Processing begins at 302, where a motion, movement, or sound signal is received by one or more sensors on the safe. Processing continues to 304.

At 304, the safe activates one or more sensors (e.g., image, audio, heat, etc.) in response to the signal. Processing continues to 306.

At 306, the sensor data is recorded for a given period of time (e.g., while motion continues, for a predetermined time period such as 15 minutes, etc.). Processing continues to 308.

At 308, the recorded data is provided to the safe mobile application (e.g., 121) via the server application (e.g., 108) or another external system.

FIG. 4 is a diagram showing an example safe mobile application user interface 400 in accordance with some implementations. The interface includes an element to lock the safe 402 or unlock the safe 404 and an element to view and/or listen to recorded data from the safe.

FIGS. 5-8 are diagrams showing an example safe in accordance with some implementations. The safe includes a base 502 that can be optionally secured to a wall, a piece of furniture or other object. The safe also includes a moveable lid 504 coupled to the base via a hinge. The base 502 includes an electromagnet 506 and a strap to secure a handgun, long gun, or other object in the safe.

The lid 504 includes a motion detector 510, a lock element 512 (e.g., a ferrous metal plate) that can be engaged by the electromagnet 506, an image and/or heat sensor 514 and an audio sensor 516.

FIG. 9 is a diagram of an example computing device 900 in accordance with at least one implementation. The computing device 900 includes one or more processors 902, nontransitory computer readable medium 906 and network interface 908. The computer readable medium 906 can include an operating system 904, an application 910 for safe access control, alarm, and data capture and a data section 912 (e.g., for storing user access codes, mobile app communication information, captured data, etc.).

In operation, the processor 902 may execute the application 910 stored in the computer readable medium 906. The application 910 can include software instructions that, when executed by the processor, cause the processor to perform operations to control a safe in accordance with the present disclosure (e.g., performing associated functions described above and shown in FIGS. 2 and 3).

The application program 910 can operate in conjunction with the data section 912 and the operating system 904.

It will be appreciated that the modules, processes, systems, and sections described above can be implemented in hardware, hardware programmed by software, software instructions stored on a nontransitory computer readable medium or a combination of the above. A system as described above, for example, can include a processor configured to execute a sequence of programmed instructions stored on a nontransitory computer readable medium. For example, the processor can include, but not be limited to, a personal computer or workstation or other such computing system that includes a processor, microprocessor, microcontroller device, or is comprised of control logic including integrated circuits such as, for example, an Application Specific Integrated Circuit (ASIC). The instructions can be compiled from source code instructions provided in accordance with a programming language such as Java, C, C++, C#.net, assembly or the like. The instructions can also comprise code and data objects provided in accordance with, for example, the Visual Basic™ language, or another structured or object-oriented programming language. The sequence of programmed instructions, or programmable logic device configuration software, and data associated therewith can be stored in a nontransitory computer-readable medium such as a computer memory or storage device which may be any suitable memory apparatus, such as, but not limited to ROM, PROM, EEPROM, RAM, flash memory, disk drive and the like.

Furthermore, the modules, processes systems, and sections can be implemented as a single processor or as a distributed processor. Further, it should be appreciated that the steps mentioned above may be performed on a single or distributed processor (single and/or multi-core, or cloud computing system). Also, the processes, system components, modules, and sub-modules described in the various figures of and for embodiments above may be distributed across multiple computers or systems or may be co-located in a single processor or system. Example structural embodiment alternatives suitable for implementing the modules, sections, systems, means, or processes described herein are provided below.

The modules, processors or systems described above can be implemented as a programmed general purpose computer, an electronic device programmed with microcode, a hard-wired analog logic circuit, software stored on a computer-readable medium or signal, an optical computing device, a networked system of electronic and/or optical devices, a special purpose computing device, an integrated circuit device, a semiconductor chip, and/or a software module or object stored on a computer-readable medium or signal, for example.

Embodiments of the method and system (or their sub-components or modules), may be implemented on a general-purpose computer, a special-purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit element, an ASIC or other integrated circuit, a digital signal processor, a hardwired electronic or logic circuit such as a discrete element circuit, a programmed logic circuit such as a PLD, PLA, FPGA, PAL, or the like. In general, any processor capable of implementing the functions or steps described herein can be used to implement embodiments of the method, system, or a computer program product (software program stored on a nontransitory computer readable medium).

Furthermore, embodiments of the disclosed method, system, and computer program product (or software instructions stored on a nontransitory computer readable medium) may be readily implemented, fully or partially, in software using, for example, object or object-oriented software development environments that provide portable source code that can be used on a variety of computer platforms. Alternatively, embodiments of the disclosed method, system, and computer program product can be implemented partially or fully in hardware using, for example, standard logic circuits or a VLSI design. Other hardware or software can be used to implement embodiments depending on the speed and/or efficiency requirements of the systems, the particular function, and/or particular software or hardware system, microprocessor, or microcomputer being utilized. Embodiments of the method, system, and computer program product can be implemented in hardware and/or software using any known or later developed systems or structures, devices and/or software by those of ordinary skill in the applicable art from the function description provided herein and with a general basic knowledge of the software engineering and computer networking arts.

Moreover, embodiments of the disclosed method, system, and computer readable media (or computer program product) can be implemented in software executed on a programmed general purpose computer, a special purpose computer, a microprocessor, a network server or switch, or the like.

It is, therefore, apparent that there is provided, in accordance with the various embodiments disclosed herein, methods, systems and computer readable media to control electric vehicle charging station power usage and storage.

While the disclosed subject matter has been described in conjunction with a number of embodiments, it is evident that many alternatives, modifications and variations would be, or are, apparent to those of ordinary skill in the applicable arts. Accordingly, Applicants intend to embrace all such alternatives, modifications, equivalents and variations that are within the spirit and scope of the disclosed subject matter.

Claims

1. A safe comprising:

a rectangular prism base with one open surface and having an electromagnet and a gun securing device configured to hold a handgun securely inside the base, wherein a power supply and a control circuit is mounted in the base, and wherein the power supply is coupled to the electromagnet and is controlled by the control circuit;
a lid coupled to the rectangular prism base via a hinge forming a cover for the open surface of the base, and having a lock element configured to be engaged by the electromagnet when it is engaged, a motion sensor coupled to the control circuit, and one or more sensors coupled to the control circuit,
wherein the one or more sensors include one or more of an image sensor, a two-way audio sensor/output device, and a heat sensor.

2. The safe of claim 1, further comprising one or more brackets welded in place in the base configured to hold the electromagnet in place.

3. The safe of claim 1, wherein the lock element includes a metal plate welded to the lid for the electromagnet to engage when the electromagnet is activated.

4. The safe of claim 1, wherein the gun securing device includes two or more straps having hook and loop fasteners.

5. The safe of claim 1, further comprising a switch coupled to the control circuit, wherein the control circuit is configured to activate or deactivate the electromagnet in response to a signal from the switch.

6. The safe of claim 1, wherein the control circuit includes a processor, computer readable memory, and a communication module.

Patent History
Publication number: 20260198684
Type: Application
Filed: Oct 31, 2024
Publication Date: Jul 16, 2026
Inventor: Devonta Cameron Gilmore (Lakeland, FL)
Application Number: 18/932,632
Classifications
International Classification: A47B 81/00 (20060101);