WO2023039483A1 - Automatic safety platform - Google Patents

Abstract

An automatic safety platform is provided that includes a memory device including stored authorization information that specifies at least one rule to restrict activation of a weapon and instructions for controlling activation of the weapon; and a safety processor communicatively coupled to the memory device, the safety processor configured to execute the instructions to perform operations including: receiving an indication that a user desires to activate the weapon; determining whether the weapon is permitted by the stored authorization information for activation in a location where the weapon is currently located; and in response to determining that the stored authorization information permits activation and that the user desired to activate the weapon, activating the weapon.

Description

AUTOMATIC SAFETY PLATFORM

CROSS-REFERENCES TO RELATED APPLICATIONS

[0001] The present disclosure claims priority to U.S. Provisional Patent Application No. 63/242,180 filed on September 9, 2021 and having the title “AUTOMATIC SAFETY PLATFORM,” which is incorporated herein by reference in its entirety.

BACKGROUND

[0002] Firearms, knives, electroshock devices, defensive sprays (e.g., pepper or other chemical irritants), and other weapons for self-defense generally have little to no protection regarding use. While these weapons are generally defensive in nature, there is nothing stopping a user from using them in an offensive manner. For example, weapons can be stolen or a mindset of a user can change over time to a point where a weapon for self-defense is used in an aggressive manner to harm others or facilitate crimes. In some tragic circumstances, a user’s weapon may be forcibly taken and used against the user or others.

[0003] Some known firearm weapon systems have a fingerprint reader that only permits a firearm to discharge if a trigger is pulled by an authenticated user. However, an accuracy of the fingerprint reader may be comprised by a user’s sweat, finger/hand placement, or environmental conditions, which can prevent the user from legitimately using a weapon for self-defense. Aside from firearms, there are generally no known automatic safety systems for knives, electroshock devices, defensive sprays, or other weapons.

SUMMARY

[0004] Example systems, methods, and apparatuses are disclosed herein for an automatic safety platform for use in any weapon system that has a deployable deterrent. For example, the safety system may restrict a firearm from firing, a defensive spray device from discharging a fluid irritant, an electroshock device from arming/firing, a blade from being deployed from a handle, and/or a blunt/sharp weapon from being removed from a sheath if one or more conditions are not satisfied. The disclosed automatic safety platform ensures a correct (approved) user is in an approved location at a correct time before a weapon system is permitted to discharge or otherwise deploy.

[0005] In an example, a safety system includes an automatic safety processor that includes one or more rules for weapon discharge/deployment. The rules may specify certain geographic locations where use is permitted, certain geographic locations where use is not permitted, certain user authentications to permit a user to activate an associated weapon, and/or restriction to weapon system activation strength based on geographic location, time, and user identity (e.g., permit only a portion of a knife blade to discharge from a holder based on local/state rules or location-specific rules). The rules may be defined by or saved to a safety server, which is part of the automatic safety platform. During use, the safety processor may comminute with the server via a cellular system or satellite system to determine a physical location, and implement the one or more corresponding permissive/restrictive rules. Additionally or alternatively, the safety processor may communicate with a computing device, such as a smartphone to obtain location information on behalf of the safety device.

[0006] In light of the present disclosure and the above aspects, it is therefore an advantage of the present disclosure to provide an automated safety platform for weapon systems.

[0007] It is another advantage of the present disclosure to use an automated safety platform to prevent weapon discharge or deployment based on one or more geographic restrictions and/or user biometric restrictions.

[0008] It is further advantage of the present disclosure to use an automated safety platform to alter a degree of weapon discharge or deployment based on one or more geographic restrictions and/or user biometric restrictions.

[0009] It is yet another advantage of the present disclosure to provide an automated safety platform that causes one or more surveillance vehicles to launch upon receiving an indication of a weapon discharge or deployment.

[0010] Additional features and advantages are described in, and will be apparent from, the following Detailed Description and the Figures. The features and advantages described herein are not all-inclusive and, in particular, many additional features and advantages will be apparent to one of ordinary skill in the art in view of the Figures and Detailed Description. Also, any particular embodiment does not have to have all of the advantages listed herein and it is expressly contemplated to claim individual advantageous embodiments separately. Moreover, it should be noted that the language used in the specification has been selected principally for readability and instructional purposes, and not to limit the scope of the inventive subject matter.

BRIEF DESCRIPTION OF THE FIGURES

[0011] Figures 1A and IB are diagrams of an automated safety platform, according to an example embodiment of the present disclosure.

[0012] Figure 2 is a diagram of file including stored authorization information that specifies when a weapon system may operate, according to an example embodiment of the present disclosure.

[0013] Figure 3 is a flowchart of a method for using a safety platform, according to embodiments of the present disclosure.

[0014] Figure 4 is a flowchart of a method for using a safety platform, according to embodiments of the present disclosure.

[0015] Figure 5 illustrates a deployment scenario, according to embodiments of the present disclosure.

[0016] Figure 6 is a flowchart of a method, according to embodiments of the present disclosure.

DETAILED DESCRIPTION

[0017] Methods, systems, and apparatus are disclosed for an automated safety system for a weapon or weapon system. Reference is made herein to various weapons including firearms, electroshock devices, knives, defensive sprays, etc. It should be appreciated that the disclosed automated safety system may be applied to any weapon or weapon system that provides for a discharge of a projectile or fluid or a deployment/release of a blunt/sharp object. For example, the automated safety system may be integrated with a sheath and control the release of a blade.

[0018] The automated safety system disclosed herein is configured to enable only approved users to discharge, brandish, use, or otherwise activate a weapon system in an approved location. In some embodiments, the automated safety system also controls or limits a degree of force discharged, a volume of fluid dispersed, a blade length deployed, a rate of fire permitted, or other measure of activation strength based on one or more user identities or geographic rules.

[0019] Figures 1A and IB are diagrams of an automated safety platform 100, according to an example embodiment of the present disclosure. The safety platform 100 includes a safety system 102 with a safety processor 104. The safety system 102 includes an activation actuator 106 that controls a weapon 108. In an example, when the safety system 102 includes portions of a firearm, the actuator 106 includes a firing mechanism or trigger, and the weapon 108 includes the bullets and the chamber. In another example, when the safety system 102 includes a deployable or switch knife, the actuator 106 includes a switch to set an exposed blade length, and the weapon 108 includes a blade. In yet another example, when the safety system 102 includes an electroshock device, the actuator 106 includes a trigger, and the weapon 108 includes a battery, electrodes, control electronics, and compressed gas.

[0020] In various embodiments, the actuator 106 includes a physical interlock that the safety system 102 deploys to prevent the movement of the weapon 108 to a deployed state (e.g., a hammer striking, a blade extending) or a safety device moving from a safe to a live state. Additionally or alternatively, the actuator 106 includes an electronic interlock that blocks activation or deployment signals for the weapon system 108 or actively generates suppression signals to prevent activation or deployment from transmitting within the weapon system 108.

[0021] In various examples, the safety system 102 may be manufactured and integrated with the weapon 108 as a combined weapon system, or may be added to a preexisting weapon 108 (e.g., as an aftermarket safety solution). In the illustrated example, the safety processor 104 is integrated with the safety system 102. In other examples, the safety processor 104 is mechanically or communicatively coupled to the safety system 102. The safety processor 104 may include any control logic, controller, microcontroller, microprocessor, Application Specific Integrated Circuit (ASIC), or other computational circuit. The safety processor 104 is communicatively coupled to a safety memory device 110, which may include any RAM, ROM, flash memory, etc. The safety memory device 110 stores computer-readable instructions 112, which when executed by the safety processor 104, cause the safety processor 104 to perform the operations disclosed herein.

[0022] The safety memory device 110 is also configured to store stored authorization information 114 that specifies conditions under which the weapon 108 may be used or conditions under which the weapon 108 may not be used. In other words, the conditions may be permissive or restrictive. The stored authorization information 114 is discussed in greater detail in regard to Figure 2.

[0023] The safety processor 103 includes or is communicatively coupled to acceleration or inertial sensors 118 that detect movement or acceleration in the weapon 108. When the movement or acceleration of the weapon 108 exceeds a threshold, indicating activation of the weapon 108 or a struggle for possession of the weapon 108, the sensors 118 signal the safety processor 104 to generate an alert. The alert may be forwarded to various third parties (e.g., police, medical professionals, etc.) over the network 130 via the safety system 102 or the user device 120.

[0024] The safety processor 104 includes or is communicatively coupled to a transceiver/antenna 116. As illustrated, the transceiver/antenna 116 can be configured for various communications protocols (e.g., a BLUETOOTH® protocol or an Near Field Communication (NFC)) protocol to communicate with a user device 120 (e.g., a smartphone, a tablet computer, a laptop computer, a desktop computer, a workstation, etc.) or a safety server 140 via a network 130. In the embodiment illustrated in Figure 1 A, the user device 120 is configured as a communication gateway for the safety processor 104 to enable connectivity to a network 130, which may include any cellular, Wi-Fi, Ethernet, satellite, or mesh network and combinations thereof. In the embodiment illustrated in Figure IB, the transceiver/antenna 116 is configured to communicate directly with the network 130 via a cellular, Wi-Fi, Ethernet, satellite, or mesh network and combinations thereof. In the embodiment shown in Figure IB, the transceiver/antenna 116 may also communicate with the user device 120, which may provide for remote control and/or configuration of the safety processor 104. Additionally or alternatively, in the illustrated embodiment, the user device 120 may communicate or set configuration settings within the server 140, which are then transmitted to the safety processor 104 via the network 130. Additionally or alternatively, as discussed in greater detail in regard to Figure 5, the transceiver/antenna 116 or the user device 120 may communicate with a drone (502) that acts as a link to the network 130 or as a component of the safety platform 100.

[0025] The user device 120 includes a user processor 124 may include any control logic, controller, microcontroller, microprocessor, ASIC, or other computational circuit. The user processor 124 is communicatively coupled to a user memory device 126, which may include any RAM, ROM, flash memory, etc. The user memory device 126 stores computer-readable instructions for an application 122, which when executed by the user processor 124, cause the user processor 124 to perform the operations disclosed herein.

[0026] In the illustrated example, the safety platform 100 includes a server 140 and a third party system 142 (optional). The example server 140 is communicatively coupled to a server memory device 144, which stores a plurality of stored authorization information 114. The server 140 is configured to aggregate rules for different geographic locations and/or users. In some embodiments, rules are based on a classification for a user. For example, users designated as security or police may have more permissive rules compared to other persons. Further, persons associated with a geographic location, such as a place of employment or their home may have more permissive rules for those locations compared to other users. The rules may be provided by the primary users, related parties to the primary users (e.g., an employer setting use of force rules for security guard users, a parent setting family rules for children), government agencies, or the like.

[0027] The example server 140 includes one or more Application Program Interfaces (APIs), which are accessible from a mobile application 122 on the user device 120. The mobile application 122 may be defined by one or more instructions stored in a memory device of the user device 120, where execution of the instructions by the user processor 124 of the user device 120 causes the user device 120 to perform the operations discussed herein. The application 122 may include one or more user interfaces for a user to provide registration information, such as a home address, occupation, employer information, employer approval codes, and any other information for creating rules. The application 122 transmits the information to the server 140, which converts the information into one or more stored authorization information 114 specifically for the user. For example, creating permissive rules for a user’s home, place of employment, etc. The server 140 also adds local or government restrictive or permissive rules to the stored authorization information 114 for the particular user. Once a complete stored authorization information 114 is complete for the user, the server 140 transmits the stored authorization information 114 to the safety processor 104 via the network 130 and/or the user device 120. The server 140 may periodically transmit rule updates based on changes to the user, new laws/restrictions for certain geographic locations, or as the user enters new areas not previously covered by an existing stored authorization information 114. [0028] In the illustrated examples of Figures 1A and IB, the safety processor 104 receives GPS or other geographic location information from the user device 120, which may include a GPS chipset. Further, for urban and indoor locations, the safety processor 104 may receive GPS data combined with dead reckoning or other terrestrial-based location information to provide more precise additional or alternative location information. In some instances, the location information may include elevation information for rules that specify an elevation or floor of a building. In some embodiments, the safety processor 104 directly receives the geographic location information from GPS satellites, from drones covering an area in a mesh network, from localized transmitters (e.g., Wi-Fi routers, cellular base stations, etc.), and combinations thereof. In some embodiments, the user device 120 or the safety processor 104 are configured to transmit a location request to a third party system 142. Such a request may be used for indoor or other terrestrial location tracking. In some instances, the third party system 142 includes terrestrial or satellite-based beacons for location tracking.

[0029] During use, the safety processor 104 compares the current location of the safety system 102 to the stored authorization information 114. Based on which rule matches a current location, the safety processor 104 applies the specified restrictions or permissions to the deployment actuator 106. In various embodiments, in instances where two or more rules apply, the safety processor 104 is configured to select the most restrictive rule. In these examples, the safety processor 104 provides continuous location monitoring. In other examples, the safety processor 104 may only request a location in response to detecting a request for activating the weapons (e.g., a user pulling a trigger, a user attempting to unlock or set a status of the weapon 108 to live/dangerous). For example, the safety processor 104 may detect that a user is attempting to pull a trigger on a firearm weapon 108 or set a nozzle on a defensive spray weapon 108 from blocked to open, and in response transmits a location message, and receives a current location for determining if the weapon can activate using the stored authorization information 114.

[0030] Additionally or alternatively to location-based rules, the safety processor 104 may use identity -based rules. In various embodiments, the safety processor 104 may receive biometric information from a potential user of the safety system 102 via a biometric scanner 150 included in the user device 120 or the safety system 102 to identify whether the potential user is registered as an authorized user. In various embodiments, the biometric scanner 150 includes one or more of a fingerprint scanner, a Radio Frequency Identifier (RFID) tag, a facial recognition algorithm/camera, a voice print, a retinal scan algorithm/camera, or the like to collect a biometric scan from a candidate user of the weapon 108 to identify and authenticate that candidate user.

[0031] Figure 2 is a diagram of a file including stored authorization information 114 that specifies when the weapon 108 may operate, according to an example embodiment of the present disclosure. As shown, the stored authorization information 114 specifies first coordinates 210a (generally or collectively, coordinates) and second coordinates 210b for locations where the weapon 108 may be used, biometric information 220 for who is allowed to use the weapon 108, and adapted use parameters 230 for a strength of deployment permitted at various coordinates 210 and for various users (e.g., according to different biometric information 220). Although two sets of coordinates 210 are illustrated in the example stored authorization information 114, the stored authorization information 114 may include more or fewer than two sets of coordinates 210 in various embodiments. Similarly, in various examples, more than one set of biometric information 220 (e.g., for different biometric makers for one user or for multiple users) and more than one set of adapted use parameters 230 may be included in the stored authorization information 114.

[0032] In various embodiments, the coordinates 210 can include GPS coordinates, geo-fenced locations, mapped signal source identifiers, or the like that can be used to refer to or otherwise identify a location. For example, the first coordinates 210a may correspond to GPS coordinates where full use of the weapon 108 is permitted, while the second coordinates 210b may correspond to a signal strength and beacon identifier for a cellular transmitter that covers a location where reduced or partial use of the weapon 108 is permitted.

[0033] In some embodiments, the coordinates 210 may refer to locations where use of the weapon 108 is permitted, and all other locations are treated so as to deny use of the weapon 108. For example, for an electroshock weapon 108 used by a security guard, the first coordinates 210a may correspond to a stadium or airport, while the second coordinates 210b corresponds to an office, both of which the security guard is authorized to use the associated weapon 108 at. At the first location, the stored authorization information 114 specifies that the electroshock weapon 108 may be operated to full discharge capacity while at the second location the electroshock weapon 108 may only operate at A% of the available discharge capacity.

[0034] In some embodiments, the coordinates 210 may refer to locations where the use of the weapon 108 is denied, an all other locations are treated so as to permit use of the weapon 108. For example, for a defensive spray weapon 108 carried by a person for self-defense against wildlife (e.g., bear spray), the first coordinates 210a may correspond to a stadium or airport where use of the spray is prohibited, while the second coordinates 210b corresponds to a campground, where use of the spray is controlled to X% of the available pressure, so that all other areas correspond to locations where full use of the spray is permitted.

[0035] In some embodiments, the stored authorization information 114 may be based on government or facility regulations to ensure a user is compliant with those regulations. For example, a city may restrict a legal blade length to two inches, while areas outside the city permit blade lengths up to three inches, while the local airport does not permit knives of any length. In this example, the stored authorization information 114, in conjunction with the safety processor 104, prevents the user from deploying the blade while the user in in the airport. When in the city, the stored authorization information 114, in conjunction with the safety processor 104, permits the user to deploy the blade, albeit with two inches or less exposed, and outside the city, the stored authorization information 114, in conjunction with the safety processor 104, permits the user to deploy the blade up to its full length. This configuration enables the retractable knife to be labeled as Transportation Security Administration (TSA) compliant in addition to being legal in the different jurisdictions.

[0036] The biometric information 220 may include various scans of biometric features for registered users of the safety system 102. For example, fingerprints, palm prints, retinal scans, voice prints, or the like In addition to providing tracking based on location, the safety processor 104 and the stored authorization information 114 also provide restrictions based on user identity. For example, the user device 120 or the safety system 102 may include a biometric scanner 150. The safety processor 104 receives biometric scans from the biometric scanner 150, which is compared to biometric information 220 specified in one or more of the stored authorization information 114. The biometric information 220 may include retina data, facial data, fingerprint data, voice data, etc. The user may use the application 122 for capturing the biometric information 220 and creating associated rules via the server 140 during registration. Accordingly, subsequent scans of the biometric markers when a user is attempting to activate the weapon 108 via the safety system 102 are compared against the stored biometric information 220 to authenticate a user and differentiate different authorized (or unauthorized) users of the weapon 108 who may have different use permissions. [0037] For example, a primary user may create rules for other (e.g., secondary) users. In an example, a parent user may set a rule that up to five inches of a blade are allowed for deployment by the parent user, and no more than two inches of deployment are allowed for child users. The biometric scanner 150 records biometric information of a user, which is transmitted to the safety processor 104 for comparison to the rules. Thus, based on which user is detected, the safety processor 104 applies the appropriate restriction, allowing different ranges of weapon activation for different registered users. Combining the previous two examples for identify-based rules and the location-based rules so that the most restrictive rule controls the activation level of the weapon 108, the safety processor 104 may permit parent user to deploy up to zero inches of the blade in an airport, two inches of the blade in the city, and five inches elsewhere, and may permit the child user to deploy up to zero inches of the blade in an airport, two inches of the blade in the city, and two inches elsewhere.

[0038] The activation level, deployment strength, or authorization of a first user may differ from a second user at the same location. The different permitted use levels may be governed by an adapted use parameter 230 associated with coordinates 210 and biometric information 220. For example, a first user may be able to discharge a defensive spray at a first location and a second location at full deployment strength, while a second user may be able to discharge the defensive spray at the first location at full deployment strength, but at less than full deployment strength at the second location. In another example, a user may activate the defensive spray using either a fingerprint or a voice print, but the adapted use parameter 230 may permit full deployment strength activation when the fingerprint matches the biometric information 220, and half-strength activation when the voice print matches the biometric information 220 (e.g., due to greater confidence in accuracy of the fingerprint scan).

[0039] In some embodiments, the server 140 creates a master rule that enables specific weapons 108 to be enabled/disabled based on an internal policy. For example, the TSA, could lock a device upon entering into a restricted area and re-enable the device upon exit of the restricted area. In another example, it is possible to support police by disabling all non-police weapons 108 in an area. In yet another example, the safety processor 104 and/or stored authorization information 114 may be configured to only allow the weapon 108 to be used in a single area. For example, a security company may only allow for usage of a weapon 108 on company property. The safety processor 104 may be configured (e.g., via user privileges of the stored authorization information 114) to only allow the weapon 108 to be activated during a specific time period of the day. For example, a security company may only allow for usage of the weapon 108 during a guard’s active shift hours (e.g., time/day based rules).

[0040] Figure 3 is a flowchart of a method 300 for using a safety platform 100, according to embodiments of the present disclosure. Method 300 begins at operation 310 where the user engages the safety system 102. In various aspects, the user engages the safety system 102 by engaging a biometric scanner 150 associated with the safety system 102 (either integrated in the safety system 102, the weapon 108, or a paired user device 120). User engages safety device [0041] At operation 320, the safety system 102 authenticates the user who engaged the safety system 102 per operation 310. In various embodiments, the safety system 102 collects a biometric scan from the user, which is compared against biometric information included in stored authorization information 114 to determine whether the user is authorized or not authorized to activate the weapon 108. When the user is authorized, method 300 proceeds to operation 330, otherwise, when the user is not authorized, method 300 many end without the user being able to activate the weapon 108.

[0042] At operation 330, the safety system 102 generates an activation request for activating the weapon 108. In various embodiments, the activation request is transmitted to a server 140 to determine up-to-date use scenario for the weapon 108 based on the current location of the weapon 108, the current time, the identity of the currently authorized user, and combinations thereof. In some embodiments, as discussed in greater detail in regard to Figure 4, when the safety system 102 may receive a rejection or no authorization within a specified time period (e.g., a time-out), and method 300 may end without the user being able to activate the weapon 108.

[0043] At operation 340, the safety system 102 receives permissions to activate the weapon 108. In various aspects, the permissions may be received by the safety system 102 from the user device 120 or via a direct connection to a network 130. The server 140 may respond with a most recent stored authorization information 114, updates to an existing stored authorization information 114 currently stored on a user device 120 or safety system 102, a use key to decrypt a currently stored stored authorization information 114 or control/safety for the actuator 106 to temporarily enable activation of the weapon 108.

[0044] At operation 350, the safety system 102 determines an adapted use parameter 230 for activating the weapon 108. In various embodiments, the adapted use parameter 230 allows for unrestricted (e.g., full strength) activation of the weapon 108, fully restricted activation (e.g., no activation) of the weapon 108, or partially restricted (e.g., between 99% and 1% strength) activation of the weapon 108 based on one or more of the location of the weapon 108, the identity of the user, and a time of activation (e.g., during a shift for a security guard).

[0045] At operation 360, the safety system 102 permits activation of the associated weapon 108 according to the relevant adapted use parameter 230. For example, when the weapon 108 is a blade, the safety system 102 permits the user to extend the blade for a defined length from a handle. When the weapon 108 is a defensive spray, the safety system 102 permits the user to expel a chemical irritant at a defined pressure, flow rate, or amount over a period of time.

[0046] In some embodiments, when user attempts to engage the safety system 102 (per operation 310) or an alert sensor detects attempted (or actual) use of the weapon 108, method 300 may proceed to operation 370, where the safety system 102 generates an SOS message, which may be forwarded to response personnel over various networks 130.

[0047] Figure 4 is a flowchart of a method 400 for using a safety platform 100, according to embodiments of the present disclosure. Method 400 begins at operation 410 where a user device 120 receives a request to activate the associated weapon 108. In various embodiments, the request may be received from the safety system 102 (e.g., when the user attempts depresses a trigger or other actuator 106, when a sensor 118 generates an alert), or via an application 122 on the user device 120 (e.g., via a fingerprint scanner). In various embodiments, the request is generated as part of an attempt to discharge the weapon 108 (e.g., fire a firearm, expel a chemical irritant, deploy a blade from a handle), as part of an attempt to prime or ready the weapon 108 for use (e.g., disengaging a safety on a firearm, charging an electroshock device, ready a blade for deployment), or as a sign attempted forced deployment or of a struggle over the weapon 108 (e.g., an acceleration sensor 118 showing jerking motions on the weapon 108).

[0048] At operation 420, the user device 120 determines the location of the safety system 102. In various embodiments, the user device 120 includes a GPS chipset or other geo-fencing technologies that identify where the user device 120 is located. When the user device 120 is paired with the safety system 102 via a short range communications standard (e.g., within 50 feet), the location of the user device 120 can be extrapolated to be the location of the safety system 102.

[0049] In various embodiments, while the weapon is activated or allowed to be activated (e.g., after being granted activation permission in an earlier iteration), the user device 120 may generate a new activation request on behalf of the safety system 102 to determine whether the weapon 108 may remain activated. For example, to in response to the user moving to a second location (e.g., at least X feet from the last checked location), a set amount of time elapsing since the last grant of permission, the user device 120 gaining or losing communications with a location-providing service (e.g., a GPS satellite, cell tower, Wi-Fi router, etc.), the user device 120 may determine to generate a new activation request to determine whether the weapon 108 is permitted by the stored authorization information 114 for continued activation. Accordingly, the user device 120 may continue to allow activation of the weapon 108, adjust a use parameter for the weapon 108, or prevent or terminate activation of the weapon 108 based on the updated conditions.

[0050] At operation 430, the user device 120 requested activation permission from the server 140 for the weapon 108. The activation request includes the location of the safety system 102, a time of the request, and (optionally) an identity or user class of the user of the safety system 102 from whom the request to activate the weapon 108 (per operation 410) was received.

[0051] In various embodiments, the user device 120 may receive permissions from the server 140, a rejection from the server 140, or no response from the server 140 within a defined amount of time (e.g., a time-out). When the user device 120 receives permissions from the server 140, method 400 proceeds to operation 440, where the user device 120 forwards permission to the safety system 102 to allow the weapon 108 to be deployed. Otherwise, when the user device 120 times out or receives a rejection from the server 140, method 400 may optionally proceed to operation 450, where the user device 120 may send a rejection message to the safety system, denying permission to activate the weapon 108, or may conclude without sending a rejection message, allowing the safety system 102 to also time out and thereby prevent activation of the weapon 108. [0052] In some embodiments, when a request to activate the weapon 108 is received (per operation 410) or an alert sensor detects attempted (or actual) use of the weapon 108, method 400 may proceed to operation 470, where the user device 120 generates an SOS message, which may be forwarded to response personnel over various networks 130.

[0053] Figure 5 illustrates a deployment scenario, according to embodiments of the present disclosure. In some embodiments, the safety system 102 is configured to generate an alert when a user 510 attempts to activate the weapon 108. Further, in embodiments where the safety system 102 includes acceleration or inertial sensors 118, the safety processor 104 may generate an alert if movement or acceleration is above a threshold, which may be indicative of a struggle or attempted activation of the weapon 108.

[0054] As illustrated, a user 510 has a safety system 102 that is in communication with a network 130. The safety platform 100 may include a drone-mesh as part of the network 130 that includes a plurality of drones 502. In various embodiments, at least one drone 502 in the dronemesh is a user device 120 associated the safety system 102. Other drones 502 in the drone-mesh can include the drones 502 associated with other users 510 within communications range of another user’s drone 502 and drones 502 managed by third-parties (e.g., a parks service) that form a basis for a mesh network, but are not associated with any given safety system 102 or user 510. In some embodiments, a user 510 may communicate with the drone-mesh network (via the safety system 102 or a user device 120) even when none of the drones 502 therein are associated with the user 510. In some embodiments, the mesh network may include one or more base stations 504 that can send and receive communications with the drones 502 (e.g., to coordinate a swarm) or act as immobile/stationary drones 502 for purposes of communicating with various other devices (e.g., the safety system 102) in a coverage area.

[0055] Each drone 502 in the drone-mesh is equipped with sensors and edge processing capability, and may be provided with a High Definition (HD) map and area markers for the location in which the drone 502 is deployed. The drones 502 may include various propulsion systems to travel the environment (e.g., quad-copter drones 502 to fly or hover in the environment, jet/screw drones to move in the water, etc.). Various drones 502 may be strategically located (e.g., on top of streetlight poles, building tops, etc.) in the environment to provide aerial coverage for a predetermined area when not in flight, or may be deployed to follow or track a user 510 or a threat 520 identified in the environment. When an alert is triggered by the safety system 102, an SOS signal is transmitted to the mesh network. The SOS signal may include the location of the user 510 for whom the SOS signal was generated and other related information, such as a type of weapon 108 managed by the safety system 102. On receipt of the SOS signal, one or more of the drones 502 coordinate transmission of the SOS signal to the server 140 of the safety platform 100. In various embodiments, the safety platform 100 transmits a response command to one or more of the drones 502, dispatch personnel 540, or response personnel 530a-b (generally or collectively, response personnel 530) such as police, security, emergency medical services, paramedics, fire fighters, rangers, animal control, physicians, etc. The response command includes the location information and may be sent to one or more drones 502.

[0056] In various embodiments, the dispatch personnel 540 determine which drones 502 and/or response personnel 530 are to be sent the response command. For example, in a campground where the SOS signal is received from a user 510 in possession of a defensive spray, response personnel 530 may dispatch a first drone 502 to determine the nature of the threat 520 before determining whether to send the response command to police or park rangers if the threat 520 is human-based or animal-based. Additionally or alternatively, the dispatch personnel 540 may determine whether to send secondary response personnel 530b (e.g., paramedics) in addition to primary response personnel 530a (e.g., police or park rangers) based on environmental conditions at the location (e.g., whether anyone was injured).

[0057] When a drone 502 receives an SOS signal within its area of coverage, or is directed in a response command from the server 140 or dispatch personnel 540, the drone 502 plans and flies to the location of the user 510. Once at the location of the user 510, the drone 502 can collect information at the location for provision the server 140, including captured video and sound, and analyze these data to classify a threat 520 in the environment that may have led the user 510 to have sent the SOS signal. For example, the drone 502 may use image recognition technology to identify environmental threats (e.g., fires), animal threats (e.g., lions, tigers, bears), and human threats. For example the drone 502 may access edge computing resources via the network 130 to identify the emotions or identities of one or more persons in the environment (e.g., via an emotional state Al, a facial recognition service, etc.).

[0058] In embodiments using facial recognition, the drone 502 may move about the location to capture visuals of nearby persons (e.g., within X meters of a designated location), which may be cross referenced with a criminal database to identify whether a threat 520 is associated with a known criminal. In embodiments using an emotional state Al, the Al examines the emotional state of a person identified as a threat 520 to check for intoxication, metal instability, and so forth. The real-time informational analysis is transmitted to response personnel 530 that are coming to the scene. This provides situational awareness to the response personnel 530. In case a human or animal threat 520 leaves the location that the SOS was sent from, the drone 502 is configured to pursue the threat 520 to an edge of its coverage area, and transfer the pursuit to another drone 502 providing uninterrupted coverage of information to response personnel 530. [0059] In various embodiments, the drones 502 may operate autonomously, under the control of a user 510, dispatch personnel 540, response personnel 530, or a providing party, or under semi- autonomous control (e.g., partially or at various times under the control of a human operator and a computer control system).

[0060] In various embodiments, the drones 502 can be supplied by a user 510 to add to or form the basis of a drone-swarm. For example, a drone 502 can be built into a camper or other recreational vehicle to deploy therefrom in response to receiving an SOS signal from the user 510 to provide vital accident information and aerial coverage and provide situation awareness to response personnel 530 after detecting an alert signal. The drone 502 can also be integrated into or deployed from the vehicles of response personnel 530 to provide needed aerial coverage of a crime scene, assist during traffic stops, or deploy or expand a network 130 at the site of an accident. [0061] Figure 6 is a flowchart of a method 600, according to embodiments of the present disclosure. Method 600 begins at operation 610, where a drone 502 or base station 504 receives an SOS message from the safety system 102 or a user device 120. In various embodiments, the SOS message is generated in response to the user attempting to engage the safety system 102 (per operation 310) or an alert sensor detecting attempted (or actual) use of the weapon 108.

[0062] At operation 620, one or more drones 502 are deployed. For example, a drone 502 may take off from a charging station or leave a way-keeping point to position the drone 502 to respond to the SOS message.

[0063] At operation 630, a drone 502 deployed (per operation 620) is directed to a location of the safety system 102. In various embodiments, the drone 502 may move closer to the user 510 to identify any threats 520 in the environment, follow persons of interest, or gather information about the user 510 (e.g., is the user 510 conscious, in distress, etc.). The drone 502 may use various video and audio sensors to gather data about the environment, the user 510, and any threats 520 in the environment, and may process these data locally or forward the data for further processing to an external service.

[0064] At operation 640, a drone 502 deployed (per operation 620) is directed to establish a network connection. For example, a user located in a remote location in a park may not have cell service, and the drone 502 is dispatched to carry the SOS message to a network 130 accessible at a different location. Additionally or alternatively, the deployed drone 502 may join a drone swarm at the location, thereby establishing communications with other drones 502 and networks 130 that those other drones 502 are in contact with. When joining a drone swarm, the deployed drone 502 may be commanded to maneuver or position itself in relation to the other drones 502, and coordinates various tasks with those other drones 502.

[0065] In various aspects, a single drone 502 may perform one or both of operation 630 and operation 640, which may be performed in either order or while performing the other one of operation 630 and operation 640 (e.g., substantially simultaneously). Additionally or alternatively different drones 502 in a swarm may be directed to perform one or both of operation 630 and operation 640 as part of a coordinated team. For example, a first drone 502 may be directed to the location of the safety system 100 (per operation 630) and a second drone 502 may be directed at the same time to establish a network connection (per operation 640) as a bridge between the first drone 502 and a cellular, Wi-Fi, or other network 130.

[0066] At operation 650, the drone 502 forwards data to various responders. In some embodiments, the drone 502 forwards data to a safety system server 140 to grant (or deny) the user the ability to deploy the weapon 108. In various embodiments, the drone 502 may forward the data to various third party systems 142 for processing before sending data on to the responders (e.g., for image or facial recognition) to thereby prepare the responders for a threat 520 at the location. Method 600 may continue for a preset amount of time, until the drone 502 needs to recharge, or the drone 502 is dismissed by an authorized party, after which method 600 may end.

[0067] The present disclosure may also be understood by the following clauses.

[0068] Clause 1 : A safety system, comprising: a memory device including stored authorization information that specifies at least one rule to restrict activation of a weapon and instructions for controlling activation of the weapon; and a safety processor communicatively coupled to the memory device, the safety processor configured to execute the instructions to perform operations including: receiving an indication that a user desires to activate the weapon; determining whether the weapon is permitted by the stored authorization information for activation in a location where the weapon is currently located; and in response to determining that the stored authorization information permits activation and that the user desired to activate the weapon, activating the weapon.

[0069] Clause 2: The safety system of any of clauses 1 and 3-7, wherein the stored authorization information permits does not permit activation of the weapon at full deployment strength, wherein activating the weapon at less than full deployment strength is performed according to an adapted use parameter included in the stored authorization information.

[0070] Clause 3 : The safety system of any of clauses 1, 2, and 4-6, wherein the safety processor is further configured when the user has moved to a second location, different from the location according to the stored authorization information, to perform operations including: determining whether the weapon is permitted by the stored authorization information for activation in the second location; and in response to determining that the stored authorization information does not permit activation, preventing activation of the weapon while at the second location.

[0071] Clause 4: The safety system of any of clauses 1-3 and 5-7 wherein receiving the indication that the user desires to activate the weapon includes receiving a biometric scan from the user, wherein the stored authorization information does not permit activation when the biometric scan does not match a stored biometric information from an authorized user.

[0072] Clause 5: The safety system of any of clauses 1-4, 6, and 7, wherein the safety processor receives at least one of location information and the biometric scan from a wirelessly coupled user device, from a server via a cellular or Internet connection, or from an integrated Global Positioning System receiver.

[0073] Clause 6: The safety system of any of clauses 1-5 and 7, wherein the safety processor is further configured to generate an SOS signal in response to attempted activation of the weapon. [0074] Clause 7: The safety system of any of clauses 1-6, wherein the weapon includes at least one of a firearm, an electroshock device, a retractable knife, or a defensive spray.

[0075] Clause 8: A method, comprising: in response to a user engaging a safety system associated with a weapon, authenticating the user; in response to authenticating the user as permitted to use the weapon, generating an activation request that compares a location where the location where the weapon is currently located against coordinates included in stored authorization information; and in response to determining that the stored authorization information permits activation of the weapon at the location, activating the weapon.

[0076] Clause 9: The method any of clauses 8 and 10-14, further comprising: determining an adapted use parameter from the stored authorization information for activating the weapon; and wherein activating the weapon activates the weapon according to the adapted use parameter at less than full deployment strength. [0077] Clause 10: The method any of clauses 8, 9, and 11-14, further comprising: in response to the user moving to a second location, different from the location according to the stored authorization information, determining whether the weapon is permitted by the stored authorization information for continued activation in the second location; and in response to determining that the stored authorization information does not permit activation at the second location, preventing activation of the weapon while at the second location.

[0078] Clause 11 : The method any of clauses 8-10 and 12-14, wherein authenticating the user further comprises: receiving a biometric scan from a candidate user of the weapon indicating that the candidate user desires to activate the weapon; comparing the biometric scan to a biometric information for registered users of the weapon; and in response to the biometric scan matching the biometric information, authenticating the candidate user as the user.

[0079] Clause 12: The method any of clauses 8-11, 13, and 14, wherein the biometric scan and location information are provided to a safety system that controls activation of the weapon for determining whether to permit activation of the weapon from a wirelessly coupled user device or from a server via a cellular or Internet connection.

[0080] Clause 13: The method of any of clauses 8-12 and 14, further comprising generating an SOS signal in response to attempted activation of the weapon.

[0081] Clause 14: The method of any of clauses 8-13 wherein the weapon includes at least one of a firearm, an electroshock device, a retractable knife, or a defensive spray.

[0082] Clause 15: A memory device including instructions that when executed by a processor enable performance of operations comprising: in response to a user engaging a safety system associated with a weapon, authenticating the user; in response to authenticating the user as permitted to use the weapon, generating an activation request that compares a location where the location where the weapon is currently located against coordinates included in stored authorization information; and in response to determining that the stored authorization information permits activation of the weapon at the location, activating the weapon.

[0083] Clause 16: The memory device of any of clauses 15 and 17-20, the operations further comprising: determining an adapted use parameter from the stored authorization information for activating the weapon; and wherein activating the weapon activates the weapon according to the adapted use parameter at less than full deployment strength. [0084] Clause 17: The memory device of any of clauses 15, 16, and 18-20, the operations further comprising: in response to the user moving to a second location, different from the location according to the stored authorization information, determining whether the weapon is permitted by the stored authorization information for continued activation in the second location; and in response to determining that the stored authorization information does not permit activation at the second location, preventing activation of the weapon while at the second location.

[0085] Clause 18: The memory device of any of clauses 15-17, 19, and 20, wherein authenticating the user further comprises: receiving a biometric scan from a candidate user of the weapon indicating that the candidate user desires to activate the weapon; comparing the biometric scan to a biometric information for registered users of the weapon; and in response to the biometric scan matching the biometric information, authenticating the candidate user as the user.

[0086] Clause 19: The memory device of any of clauses 15-18 and 20, wherein the biometric scan and location information are provided to a safety system that controls activation of the weapon for determining whether to permit activation of the weapon from a wirelessly coupled user device or from a server via a cellular or Internet connection.

[0087] Clause 20: The memory device of any of clauses 15-19, the operations further comprising generating an SOS signal in response to attempted activation of the weapon.

[0088] The preceding disclosures are illustrative embodiments. It should be appreciated by those of skill in the art that the devices, techniques and methods disclosed herein elucidate representative embodiments that function well in the practice of the present disclosure. However, those of skill in the art should, in light of the present disclosure, appreciate that many changes can be made in the specific embodiments that are disclosed and still obtain a like or similar result without departing from the spirit and scope of the invention.

[0089] Unless otherwise indicated, all numbers expressing quantities of ingredients, properties such as molecular weight, reaction conditions, and so forth used in the specification and claims are to be understood as being modified in all instances by the term “about.” Accordingly, unless indicated to the contrary, the numerical parameters set forth in the following specification and attached claims are approximations that may vary depending upon the desired properties sought to be obtained by the present invention. At the very least, and not as an attempt to limit the application of the doctrine of equivalents to the scope of the claims, each numerical parameter should at least be construed in light of the number of reported significant digits and by applying ordinary rounding techniques. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the invention are approximations, the numerical values set forth in the specific examples are reported as precisely as possible. Any numerical value, however, inherently contains certain errors necessarily resulting from the standard deviation found in their respective testing measurements. [0090] The terms "a" and "an" and "the" and similar referents used in the context of describing the invention (especially in the context of the following claims) are to be construed to cover both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context. Recitation of ranges of values herein is merely intended to serve as a shorthand method of referring individually to each separate value falling within the range. Unless otherwise indicated herein, each individual value is incorporated into the specification as if it were individually recited herein. All methods described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g. "such as") provided herein is intended merely to better illuminate the invention and does not pose a limitation on the scope of the invention otherwise claimed. No language in the specification should be construed as indicating any non-claimed element essential to the practice of the invention.

[0091] The use of the term "or" in the claims is used to mean "and/or" unless explicitly indicated to refer to alternatives only or the alternatives are mutually exclusive, although the disclosure supports a definition that refers to only alternatives and "and/or."

[0092] Groupings of alternative elements or embodiments of the invention disclosed herein are not to be construed as limitations. Each group member may be referred to and claimed individually or in any combination with other members of the group or other elements found herein. It is anticipated that one or more members of a group may be included in, or deleted from, a group for reasons of convenience and/or patentability. When any such inclusion or deletion occurs, the specification is herein deemed to contain the group as modified thus fulfilling the written description of all Markush groups used in the appended claims.

[0093] Preferred embodiments of this invention are described herein, including the best mode known to the inventors for carrying out the invention. Of course, variations on those preferred embodiments will become apparent to those of ordinary skill in the art upon reading the foregoing description. The inventor expects those of ordinary skill in the art to employ such variations as appropriate, and the inventors intend for the invention to be practiced otherwise than specifically described herein. Accordingly, this invention includes all modifications and equivalents of the subject matter recited in the claims appended hereto as permitted by applicable law. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the invention unless otherwise indicated herein or otherwise clearly contradicted by context.

[0094] Specific embodiments disclosed herein may be further limited in the claims using consisting of or consisting essentially of language. When used in the claims, whether as filed or added per amendment, the transition term “consisting of’ excludes any element, step, or ingredient not specified in the claims. The transition term “consisting essentially of’ limits the scope of a claim to the specified materials or steps and those that do not materially affect the basic and novel characteristic(s). Embodiments of the invention so claimed are inherently or expressly described and enabled herein.

[0095] Further, it is to be understood that the embodiments of the invention disclosed herein are illustrative of the principles of the present invention. Other modifications that may be employed are within the scope of the invention. Thus, by way of example, but not of limitation, alternative configurations of the present invention may be used in accordance with the teachings herein. Accordingly, the present invention is not limited to that precisely as shown and described.

Claims

CLAIMS We claim:

1. A safety system, comprising: a memory device including stored authorization information that specifies at least one rule to restrict activation of a weapon and instructions for controlling activation of the weapon; and a safety processor communicatively coupled to the memory device, the safety processor configured to execute the instructions to perform operations including: receiving an indication that a user desires to activate the weapon; determining whether the weapon is permitted by the stored authorization information for activation in a location where the weapon is currently located; and in response to determining that the stored authorization information permits activation and that the user desired to activate the weapon, activating the weapon.

2. The safety system of claim 1, wherein the stored authorization information permits does not permit activation of the weapon at full deployment strength, wherein activating the weapon at less than full deployment strength is performed according to an adapted use parameter included in the stored authorization information.

3. The safety system of claim 1, wherein the safety processor is further configured when the user has moved to a second location, different from the location according to the stored authorization information, to perform operations including: determining whether the weapon is permitted by the stored authorization information for activation in the second location; and in response to determining that the stored authorization information does not permit activation, preventing activation of the weapon while at the second location.

4. The safety system of claim 1, wherein receiving the indication that the user desires to activate the weapon includes receiving a biometric scan from the user, wherein the stored authorization information does not permit activation when the biometric scan does not match a stored biometric information from an authorized user.

23

5. The safety system of claim 4, wherein the safety processor receives at least one of location information and the biometric scan from a wirelessly coupled user device, from a server via a cellular or Internet connection, or from an integrated Global Positioning System receiver.

6. The safety system of claim 1, wherein the safety processor is further configured to generate an SOS signal in response to attempted activation of the weapon.

7. The safety system of claim 1, wherein the weapon includes at least one of a firearm, an electroshock device, a retractable knife, or a defensive spray.

8. A method, comprising: in response to a user engaging a safety system associated with a weapon, authenticating the user; in response to authenticating the user as permitted to use the weapon, generating an activation request that compares a location where the location where the weapon is currently located against coordinates included in stored authorization information; and in response to determining that the stored authorization information permits activation of the weapon at the location, activating the weapon.

9. The method of claim 8, further comprising: determining an adapted use parameter from the stored authorization information for activating the weapon; and wherein activating the weapon activates the weapon according to the adapted use parameter at less than full deployment strength.

10. The method of claim 8, further comprising: in response to the user moving to a second location, different from the location according to the stored authorization information, determining whether the weapon is permitted by the stored authorization information for continued activation in the second location; and in response to determining that the stored authorization information does not permit activation at the second location, preventing activation of the weapon while at the second location.

11. The method of claim 8, wherein authenticating the user further comprises: receiving a biometric scan from a candidate user of the weapon indicating that the candidate user desires to activate the weapon; comparing the biometric scan to a biometric information for registered users of the weapon; and in response to the biometric scan matching the biometric information, authenticating the candidate user as the user.

12. The method of claim 11, wherein the biometric scan and location information are provided to a safety system that controls activation of the weapon for determining whether to permit activation of the weapon from a wirelessly coupled user device or from a server via a cellular or Internet connection.

13. The method of claim 8, further comprising generating an SOS signal in response to attempted activation of the weapon.

14. The method of claim 8, wherein the weapon includes at least one of a firearm, an electroshock device, a retractable knife, or a defensive spray.

15. A memory device including instructions that when executed by a processor enable performance of operations comprising: in response to a user engaging a safety system associated with a weapon, authenticating the user; in response to authenticating the user as permitted to use the weapon, generating an activation request that compares a location where the location where the weapon is currently located against coordinates included in stored authorization information; and in response to determining that the stored authorization information permits activation of the weapon at the location, activating the weapon.

16. The memory device of claim 15, the operations further comprising: determining an adapted use parameter from the stored authorization information for activating the weapon; and wherein activating the weapon activates the weapon according to the adapted use parameter at less than full deployment strength.

17. The memory device of claim 15, the operations further comprising: in response to the user moving to a second location, different from the location according to the stored authorization information, determining whether the weapon is permitted by the stored authorization information for continued activation in the second location; and in response to determining that the stored authorization information does not permit activation at the second location, preventing activation of the weapon while at the second location.

18. The memory device of claim 15, wherein authenticating the user further comprises: receiving a biometric scan from a candidate user of the weapon indicating that the candidate user desires to activate the weapon; comparing the biometric scan to a biometric information for registered users of the weapon; and in response to the biometric scan matching the biometric information, authenticating the candidate user as the user.

19. The memory device of claim 18, wherein the biometric scan and location information are provided to a safety system that controls activation of the weapon for determining whether to permit activation of the weapon from a wirelessly coupled user device or from a server via a cellular or Internet connection.

20. The memory device of claim 15, the operations further comprising generating an SOS signal in response to attempted activation of the weapon.

26