Data redundancy and hardware tracking system for gun-mounted recording device

Abstract

A recording device for mounting on a gun. The recording device includes a recording unit that houses a recording module and a removable power source unit detachably coupled to the recording unit. The removable power source unit houses a battery and memory, wherein the battery is configured for providing power to the recording device while attached thereto and the memory stores recording data from the recording module. The memory of the removable power source unit includes data collected from the recording device and includes a hardware ID or ID code associated with a user of the recording device.

Description

FIELD OF THE DISCLOSURE

The present disclosure relates to gun-mounted recording devices, and more specifically, to a data redundancy and tracking system including hardware tracking features.

SUMMARY

Law enforcement officers and non-law enforcement people may use body cameras and/or other types of cameras to record events when using guns, such as encounters between a gun's user and one or more third parties. In many instances, though, a law enforcement officer and/or non-law enforcement person may unintentionally block the view of the camera with his/her arms when the gun is drawn. Additionally, or alternatively, the person may not activate the body camera at the appropriate time. In these instances, body cameras may not provide support that the law enforcement officer's use of the gun was justified or unjustified and/or may not record the event that the non-law enforcement person wishes to record. Stationary cameras and/or non-stationary cameras, on the other hand, may not provide the best perspective of an event, especially if a user is moving. Accordingly, body cameras suffer from many drawbacks including failure to activate at appropriate times, obstructed views depending on the positioning of the body camera and/or providing a less than desirable perspective of an event.

Embodiments of the present disclosure may overcome these limitations. In particular, the embodiments herein disclose gun-mounted recording devices. Additionally, upon determination of an event, a recording device mounted to a gun may transition from a lower-power state to a higher-power state automatically. Embodiments of the present disclosure may also have the advantage of eliminating user discretion for when/if to record an event. Furthermore, the embodiments provided herein may be used by law enforcement and non-law enforcement when no other recording device is currently being used.

As used herein, “events” may be occurrences when a gun is deployed from a previously un-deployed position. For example, an event may be when a user (e.g., law enforcement and/or non-law enforcement) deploys his/her gun from his/her holster during an encounter between the user and a third party. As another example, an event may be when a user of a gun deploys a gun from a safe and/or picks up the gun from a flat surface, a nightstand drawer, an automobile glove box, from clothing, gun case, duty belt and/or the like. However, these are only examples and not meant to be limiting. In addition, while the term “gun” is being used throughout this description, the recording device may be coupled to other devices that may not be considered guns, such as bows, crossbows and/or other devices not considered guns that shoot projectiles.

One or more embodiments are directed to a system for data retention and hardware tracking of event recorders with a removable power source unit. In one or more embodiments and described further below, the power source unit can additionally include memory. In such embodiments, the power source unit can function as both a battery for powering operation of the event recording device and as a data store for information collected by the device. Furthermore, in various embodiments the memory allows for data redundancy in the recording device. Similarly, in various embodiments the memory of the power source unit allows for easy data transfer from the recording device to an external storage system.

For example, in one or more embodiments, one or more charging nodes or docking stations can be configured to automatically download and/or transfer stored information from the memory to a more permanent database. In such a manner data transfer from the recording device can be accomplished easily in the regular and required process of recharging the power source unit, obviating any requirements for removal of the recording device from the gun or other more complicated processes for transferring saved data.

One or more embodiments are directed to a recording device, wherein the recording device includes a recording unit and a power source unit removably coupled with housing of the recording unit. In embodiments, recording unit may include a recording module, a processing device and memory; and the power source unit may include a battery for providing power to the recording unit, and memory configured to store data recorded by the recording unit and to connect with a server and/or external communication device for transfer of data stored therein. In one or more embodiments, the memory of each of the recording unit and the power source unit includes a redundant data file set, each redundant data file set including one or more data files having bits of recording and/or status data stored therein. In embodiments, the redundant data set of the recording unit and the power source unit are synchronized to mirror the respective redundant data files. In embodiments, the power source unit of the recording device is configured to connect with a server and/or external communication device for charging and/or networking with the memory of the power source unit. In embodiments, one or more of the recording devices may be included in a data management system and associated with a common network, a server and/or an external communications device.

In one or more embodiments, memory of each of the recording device recording unit and the power source unit stores and maintains a redundant data file set. Each redundant data file set may include one or more data files having certain recording and/or status data stored therein. In embodiments, the recording unit and the power source unit may be configured to synchronize the redundant data files of the recording unit and the power source unit, such that the data therein is mirrored. In embodiments, such redundant data files may be used for data integrity and security.

The above summary is not intended to describe each illustrated embodiment or every implementation of the present disclosure.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The drawings included in the present application are incorporated into, and form part of, the specification. They illustrate embodiments of the present disclosure and, along with the description, serve to explain the principles of the disclosure. The drawings are only illustrative of certain embodiments and do not limit the disclosure.

FIG. 1 depicts a perspective view of a handgun with a recording device attached thereto, according to one or more embodiments of the disclosure.

FIG. 2A depicts a top perspective view of a recording device and rail set attached thereto, according to one or more embodiments of the disclosure.

FIG. 2B depicts a bottom perspective view of a recording device and rail set attached thereto, according to one or more embodiments of the disclosure

FIG. 3A depicts an exploded perspective view of the recording device, according to one or more embodiments of the disclosure.

FIG. 3B depicts a perspective view of a power source unit, according to one or more embodiments of the disclosure.

FIG. 3C depicts a perspective view of a recording device with the power source unit removed, according to one or more embodiments of the disclosure.

FIG. 3D depicts a perspective view of a recording device with the power source unit and a backing removed, according to one or more embodiments of the disclosure.

FIG. 3E depicts a perspective view of a power source unit, according to one or more embodiments of the disclosure.

FIG. 3F depicts a perspective view of a recording device with the power source unit removed, according to one or more embodiments of the disclosure.

FIG. 3G depicts a perspective view of electrical contacts of the recording devices of FIG. 3F, according to one or more embodiments of the disclosure.

FIG. 4 is a block diagram of an embodiment of a system including a gun and a recording device, according to one or more embodiments of the disclosure.

FIG. 5A is a block diagram of a data transfer and hardware tracking system, according to one or more embodiments of the disclosure.

FIG. 5B is a perspective view of a docking station with power source unit attachment nodes according to one or more embodiments.

FIG. 6 is a block diagram of a computing node/server of a hardware tracking system, according to one or more embodiments of the disclosure.

FIGS. 7A-7B depict methods for data retention and hardware tracking, according to one or more embodiments of the disclosure.

While the embodiments of the disclosure are amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit the disclosure to the particular embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure.

DETAILED DESCRIPTION

Referring to FIGS. 1-2 a view of a handgun 102 with a recording device 104 attached thereto and views of the recording device 104 detached from the handgun are depicted, according to one or more embodiments of the disclosure. Additionally, referring to FIGS. 3A-3B, an exploded view of the recording device and a top perspective view of a removed power source unit are depicted, according to one or more embodiments.

In one or more embodiments, the handgun 102 includes, among other elements and features, a barrel 106 and a trigger guard 108. In embodiments, the barrel 106 includes a rail system 110 that is configured to accommodate a variety of different accessories and attachments, including the ability to attach the recording device 104 to the rail system 110. Additionally, or alternatively, the handgun 102 may include other attachment points to which the recording device 104 can be attached, for example, a trigger guard mount, a grip mount and/or other attachment points on the handgun 102. While a handgun is depicted in FIG. 1, the recording devices 104 described herein may be used with a variety of different gun styles and sizes, including handguns, rifles, shotguns and/or the like, as well as other devices not considered guns, but that shoot projectiles. For example, recording device 104 could be implemented with non-lethal equipment, such as those that shoot electrical contacts. As such, the handgun 102 depicted in FIG. 1 is meant for illustrative purposes and not meant to be limiting.

As shown, the recording device 104 may be secured to the rail system 110 ahead of the trigger guard 108. While the recording device 104 is shown as attached to the rail system 110, the recording device 104 may be attached to other attachment points on the handgun 102 including, for example, a trigger guard mount, a grip mount and/or like. In embodiments the recording device 104 is configured to record one or more of a video aspect and an audio aspect. As such, in various embodiments the recording device 104 includes a camera 136 and/or a microphone 135 disposed on an end 114 of the recording device 104. The camera 136 and/or microphone 135 disposed on the end 114 of the recording device 104 may be forward facing along a longitudinal axis 116 of the barrel 106 to sense and record video and/or audio that is in front of the handgun 102.

In embodiments, the camera 136 and/or microphone on the end 114 of the recording device 104 may be configured to sense and record video and/or audio that is 1 foot, 5 feet, 10 feet, 25 feet, 50 feet, 100 feet and/or the like in front of the handgun 102. In embodiments, the camera 136 on the end 114 of the recording device 104 may have a fixed focal length or include an autofocus to focus. Additionally, or alternatively, the camera 136 may include more than one camera. For example, multiple cameras may be used to record multiple views (e.g., a view of the user of the handgun 102, a view of what the user is pointing the handgun 102, side views, and/or the like). Additionally, or alternatively, the multiple cameras may be configured to: record a non-zoomed-in view and a zoomed-in view and/or have different focal lengths, at different frames per second, at different resolutions, and/or the like.

Referring to FIGS. 2-3 a perspective and exploded view of the recording device is depicted, according to one or more embodiments. In the embodiment shown, the recording device 104 includes a rail set 130A, 130B. In various embodiments, the rail set 130A, 130B may include several different mounting apertures to 132 accommodate handguns 102 having different positions for the horizontal cross slot 128. As such, it will be appreciated that the recording device 104 may be attached to a variety of different guns or handguns 102 without requiring alteration of the recording device 104. Further details of embodiments of mounting devices for a gun are disclosed in, for example, U.S. patent application Ser. No. 14/583,342, entitled “Gun Holster and Electronic Assembly” and published as U.S. Pat. Publication 20150184978, which is hereby incorporated by reference in its entirety. Additionally, or alternatively, the recording device 104 may be mounted to the handgun 102 via other methods, such using a trigger guard mount and/or a grip mount. This recording device 104 could be integrated into the gun.

The recording device 104 may include a recording module 134 configured to record one or more of the following: a visual aspect, an audio aspect, a motion aspect of the gun, a temperature aspect, a pressure aspect, date, time and/or location of the recording device 104. In embodiments, the recording module 134 may begin or cease recording in response to one or more signals, as described in more detail below. In embodiments where the recording module 134 is configured to record a visual aspect, the recording module 134 may be a video camera with a lens 136 disposed on an end 114 of the recording device 104. In embodiments, the recording module 134 may be configured to focus at different distances, record at different frames per second, record at different resolutions, and/or the like. To capture video in low light, the recording device 104 may include a light-emitting diode 138 (LED) (or other type of lighting device) that is capable of illuminating areas in front of the recording device 104. Additionally, or alternatively, the video camera 136 may be configured to capture video in low light with or without the use of the LED 138. Additionally, or alternatively, the recording device 104 may be configured to include a time stamp on any recordings. The time stamp may indicate a local time that the recording was recorded.

Additionally, or alternatively, the recording device 104 may include a laser 137 that facilitates aiming of a gun (or other device configured to shoot a projectile) to which the recording device 104 is attached. In embodiments, the recording device 104 may include a green, red, blue and/or other color laser sight(s) for determining where the handgun 102 and/or the recording device 104 are pointed. An example of a laser light that may be incorporated into the recording device 104 is disclosed in U.S. Pat. No. 9,658,031, entitled “Auto On Green Laser Sight,” which is hereby incorporated by reference in its entirety.

Additionally or alternatively, the recording device 104 may include a microphone for recording an audio aspect, a temperature sensor for sensing a temperature of the environment of the recording device 104, a pressure sensor for sensing a pressure of the environment of the recording device 104, one or more motion sensors (e.g., gyroscopes, accelerometers and/or the like) for sensing motion of the recording device 104, one or more sensors for measuring times and/or dates, one or more sensors for recording biometric indicators, and/or one or more location sensors (e.g., a GPS receiver) for measuring the location of the recording device 104. In embodiments, the pressure sensor for sensing pressure of the environment of the recording device 104 may be a different than the pressure sensor used for determining whether the handgun 102 is deployed or un-deployed.

To power the recording device 104, the recording device 104 includes an onboard power source, such as power source unit 139. In embodiments, the power source unit 139 may be replaceable, rechargeable and/or removable. In embodiments, the power source unit 139 may include a plurality of electrical contacts 418, 618, for power and data transmission between the power source unit 139 and the recording unit 141 via the mating electrical contacts 415, 515, of the recording unit 141, and between the power source unit 139 and a docking station or power and/or data transfer node.

Additionally, or alternatively, the power source unit 139 may be a customized power source unit 139 and may include spring contacts that allow the power source unit 139 to be removable. In embodiments where the power source unit 139 is rechargeable, the power source unit 139 may be recharged via a wire (e.g., via a power cord coupled to the recording device 104 and/or the power source unit 139) and/or may be recharged wirelessly, (e.g., inductively or capacitively). In embodiments, the power source unit 139 and the recording unit may include contactless connectors for power and data transmission.

Additionally, or alternatively, the power source unit 139 may be removable and coupled with a docking station to recharge the power source unit 139 and/or transfer data from the memory of the power source unit 139. Described further below, in various embodiments the power source unit 139 can additionally include memory. In such embodiments, the power source unit 139 can function as both a battery for powering operation of the recording device 104 and as a data store for information collected by the device 104. Furthermore, in various embodiments the memory allows for data redundancy in the recording device 104. Similarly, in various embodiments the memory of the power source unit 139 allows for easy data transfer from the recording device 104 to an external storage system. For example, in one or more embodiments, one or more charging nodes or docking stations can be configured to automatically download and/or transfer stored information from the memory to a more permanent database. In such a manner data transfer from the recording device 104 can be accomplished easily in the regular and required process of recharging the power source unit 139, obviating any requirements for removal of the recording device 104 from the gun 102 or other more complicated processes for transferring saved data.

In embodiments, the recording device 104 may also include an indicator 140 disposed on the, bottom, left side and/or right side of the recording device 104. The indicator 140 may indicate the remaining amount of power of the power source unit 139 and/or how much memory is left for recording video, sound, etc. Additionally, or alternatively, the indicator 140 may indicate whether the recording device 104 is recording. In embodiments, the recording device 104 may include two modes: one mode where a user cannot modify one or more settings of the recording device 104 (e.g., when the recording device 104 records) and another mode where a user can modify one or more of the settings of the recording device 104. In the embodiments where a user cannot modify one or more settings of the recording device 104, one or more settings of the recording device 104 may only be modified by an administrator. Additionally, or alternatively, while a user may not be able to modify one or more settings, the user may be able to view and/or listen to the recordings but may not be able to modify the recordings.

In embodiments, the recording device 104 may include one or more user interface buttons 142 disposed on the left side and/or right side of the recording device 104. A user interface button 142 may provide a user and/or administrator, depending on the mode of the recording device 104, with the ability to program and/or modify the functionality of the recording device 104. For example, the user interface button 142 may provide an administrator the ability to determine when and how the recording device 104 records, how long the recording device 104 records and/or the like. Additionally, or alternatively, the user interface button 142 may control the operation of the LED 138 and/or other functions included in the recording device (e.g., a microphone, a temperature sensor, a pressure sensor, audio sensor, biometric sensor, and/or a laser gun sight). In some embodiments, some functions of the user interface button 142 may be controllable by a non-administrator while others may only be controllable by an administrator. For example, recording aspects of the recording device 104 (e.g., when and how long the recording device 104 records) may only be controllable by an administrator while a non-administrator may be able to control a laser and/or light of the recording device 104.

In some embodiments, the interface button 142 may be replaced by a touchscreen or other user interface. In some embodiments, before being able to modify one or more settings of the recording device 104, a specific code and/or other authorizing indicia (e.g., a biometric identifier) may need to be entered into the user interface button 142 before the user has the ability to modify the functionality of the recording device 104. This may prevent some users from controlling the settings of the recording device 104, while still allowing other users (e.g., administrators) to have access to the settings of the recording device 104. Additionally, or alternatively, some functions of the interface button 142 may be replaced and/or replicated by an application on a smartphone.

As such, in at least some embodiments, the power source unit 139 includes a plurality of electrical contacts 418, which may include electrical contacts configured to be electrically coupled to the battery 424 within the power source unit 139 for supply of power to the recording device unit 141 when the power source unit 139 is coupled to the recording unit 141 and for recharging the battery when the power source unit 139 is electronically engaged with a charging node or a docking station, for example charging nodes 512, 514, 516 and docking station 517.

In embodiments, recording unit 141 includes a plurality of electrical contacts 415 corresponding to the electrical contacts 418 of the power source unit 139. The electrical contacts 415 may include electrical contacts configured for power transfer to the electronic components within the recording unit 141 when the recording unit 141 is coupled to the power source unit 139. In embodiments, the coupling may also facilitate recharging of an optional internal battery electrically coupled to the electrical contacts 415.

In addition, the electrical contacts 418 of the power source unit 139 may further include one or more data contacts 419 communicatively connected to the memory 424 within the power source unit 139 and configured to transfer data to and from the power source unit 139. In embodiments, the electrical contacts 415 of the recording unit may also further include one or more data contacts communicatively connected to memory, recording and data modules and electronic components within the recording unit 141 and configured to transfer data to and from the recording unit 141. The data contacts of the power source unit 139 and the recording unit 141 may be matingly configured for data transmission between the power source unit 139 and the recording unit 141 when the contacts are coupled.

In embodiments, the data contacts 419 of the power source unit 139 may be further configured and adapted to communicatively connect with a server for networking with the memory 424 of the power source unit 139. In an embodiment, the data contacts 419 are configured for a docking engagement with an external device and transmission of data and/or control signals between the power source unit memory 424 and the server device. In embodiments, the data contacts 419 may be configured to communicationally engaged with a docking station or device for transmission of data to and from the memory 424 within the power source unit 139. As noted, engagement with the docking station or device may also be adapted for recharging of the battery of the power source unit 139.

Referring to FIGS. 3E-3G, in one or more embodiments, the power source unit 139 may further include a second set of electronic contacts 618 including data contacts 619. The second set of electronic contacts 618 may be configured to matingly engage a second set of electrical contacts 515 including data contacts correspondingly configured on the recording unit 141.

In one or more embodiments, electrical contacts 418 and 618 may each include data transfer contacts and power transfer contacts and electrical contacts 415 and 515 may each include data transfer contacts and power transfer contacts. In one or more embodiments, electrical contacts 418 and corresponding electrical contacts 415 include power transfer contacts for transfer of power between the power source unit 139 and the recording unit 141 and for the recharging of the power source unit when coupled to a docking station or device; and electrical contacts 618 and corresponding electrical contacts 515 include data transfer contacts for transfer of data between the power source unit 139 and the recording unit 141 and between the memory 424 of the power source unit 139 and a server device when coupled to a docking station or device. The docking station or device would include corresponding electrical contacts for mating engagement with the electrical data and power contacts of the power source unit 139.

An embodiment of the electrical contacts 415, 515, of the recording unit 141 are illustrated in FIG. 3G. In one or more embodiments, the electrical contacts are electrical spring contacts.

The recording device 104 may also include a processing device 144. The processing device 144 may control the functionality of the recording device 104, as described below. Additionally, in embodiments, the recording device 104 may include memory (not shown) to store any data recorded by the recording device 104.

For example, FIG. 4 is a block diagram of an embodiment of a system 400 including a gun 102 and the recording device 104 mounted thereto, in accordance with embodiments of the present disclosure. In embodiments, the recording device 104 may include one or more of the following components: one or more sensors 406, a processing device 408, a recording module 410, memory 412, a data port 414, a transceiver 416, and/or a user interface 421. In various embodiments, the recording device 104 additionally includes a power source unit 420 (139) removable from a recording unit 141. The recording unit 141 may further include internal spring components 411 between the recording unit 141 and the power source unit 139.

As described, in various embodiments the removable power source unit 420 can include a battery 422 for providing power to the recording device 104 while attached thereto and memory 424. In embodiments, the power source unit 420 may separately include a data port 413 and a transceiver for transfer of data. While the above components are depicted as being included in the recording device 104, one or more of the components may be located external to the recording device 104 or removably attachable to the device, such as the power source unit 420. The present disclosure further contemplates one or more embodiments, wherein a remotely located external device may access the recording device, recording unit 141 and/or power source unit 139, 420, to download and/or access recorded data, and, in one or more embodiments, in real-time or near real-time.

In embodiments, the sensor(s) 406 may be configured to sense a signal that corresponds to the gun 102 being deployed. As indicated above, to be deployed, the gun 102 does not have to be fired. Instead, the gun 102 may be deployed if it is withdrawn from a holster and/or safe, picked up from a surface (e.g., a nightstand drawer, automobile glove box and/or the like), activated via an audio command, activated via a biometric indicator, moved in such a way that would indicate that a user is using the gun 202, such as pointing the gun 202 at a target, in the vicinity of a target, moving the gun in a defensive manner and/or for an expected engagement, and/or in a direction in which the user believes there to be a target.

The processing device 408 may be any arrangement of electronic circuits, electronic components, processors, program components and/or the like configured to store and/or execute programming instructions, to direct the operation of the other functional components of the recording device 104 and may be implemented, for example, in the form of any combination of hardware, software, and/or firmware. The recording module 410 for example is a collection of software instructions that cause the recording device 104 to record video and/or audio aspects using the elements of the device 104. In embodiments, the recordings of the recording module 410 may be saved in one or both of memory 412 and 424. The saved recordings may be password protected, encrypted, access limited (e.g., only an authorized user such as an administrator may have access to the saved recordings on memory 412), and/or the like. In embodiments, if the memory is full the recordings may loop and save over the earliest saved recordings in memory. In embodiments, segmenting the recordings into multiple files may facilitate reducing the amount of recordings that are recorded over in comparison to embodiments where the recordings are saved as one file. In embodiments, saving over the earliest saved recordings in memory may be disabled, so that once memory is full, the recording stops saving to memory and, in embodiments, only transmits the data via a communication link 428 to an external communication device 423 and/or external server 429.

In embodiments, the memory 412 includes computer-readable media in the form of volatile and/or nonvolatile memory and may be removable, nonremovable, or a combination thereof. Media examples include Random Access Memory (RAM); Read Only Memory (ROM); Electronically Erasable Programmable Read Only Memory (EEPROM); flash memory; optical or holographic media; magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices; data transmissions; and/or any other medium that can be used to store information and can be accessed by a computing device such as, for example, quantum state memory, and/or the like, including memory that may be compatible with existing law enforcement and/or other data management system.

In embodiments, the recordings may be transmitted to an external communication device 423 via a network or communication link 428 where the recordings can be saved on a server 429. In embodiments, recordings may also be transferred from the recording device 104, including the recording unit 141 and or the power source unit 139, 420, to the server 429 via a wireless or wired connection (e.g., via the data port 414 or transceiver 416). In embodiments, the data management of the recording device 104 may be compatible with existing law enforcement data management systems and requirements. Additionally, or alternatively, the transmission may be encrypted via public-key encryption methods and/or other types of encryption.

In embodiments, the recordings may be transmitted to the server 429 at a specified time interval and/or upon demand. Additionally, or alternatively, the recordings may be transmitted to the server 429 when a designated amount of space on the memory 412 or 424 has been used. For example, when 70%, 80%, 90%, and/or 100% of the memory has been used, the recordings may be transmitted to the server 429. Additionally, or alternatively, the recordings may be transmitted to the server 429 upon certain conditions occurring (e.g., the gun 102 being fired and/or a law enforcement officer returning to the station at which he/she works).

In embodiments, the communication link 428 may be, or include, a wireless communication link such as, for example, a short-range radio link, such as Bluetooth, IEEE 802.11, cellular, a proprietary wireless protocol, and/or the like. In embodiments, for example, the communication link 428 may utilize Bluetooth Low Energy radio (Bluetooth 4.1), or a similar protocol, and may utilize an operating frequency in the range of 2.40 to 2.48 GHz. The term “communication link” may refer to an ability to communicate some type of information in at least one direction between at least two devices and should not be understood to be limited to a direct, persistent, or otherwise limited communication channel. That is, according to embodiments, the communication link 428 may be a persistent communication link, an intermittent communication link, an ad-hoc communication link, and/or the like. The communication link 428 may refer to direct communications between the recording device 104 and the external communication device 423, and/or indirect communications that travel between the recording device 104 and the external communication device 423 via at least one other device (e.g., a repeater, router, hub, and/or the like). The communication link 428 may facilitate uni-directional and/or bi-directional communication between the recording device 104 and the external communication device 423. Data and/or control signals may be transmitted between the recording device 104 and the external communication device 423 to coordinate the functions of the recording device 204 and/or the external communication device 423. In embodiments, the communication link 428 may be compatible with existing law enforcement data management systems and requirements.

Additionally, or alternatively, the memory 424 of the power source unit 420 may be connectable with the external communication device 423 via the communication link 428. For example, in various embodiments the power source unit 420 is removable and can be coupled with an external communication device 423 in the form of a data station. In one or more embodiments, the data station is additional configured as a recharge station that recharges the battery 422. In such embodiments, the memory 424 provides for data redundancy in the recording device 104. In such instances, data redundancy allows for reduction or elimination of potential tampering by providing a backup or master copy of all recorded data. In one or more embodiments, the copies can be compared with one another to verify that the data has not been tampered with or corrupted in a manner to prevent access to recorded information. Similarly, data redundancy provides for a reduced chance of data loss from device damage.

In an embodiment, the recording unit 141 and/or the power source unit 420 of the recording device 104 may be communicatively coupled to one or more mobile external communication devices. In one or more embodiments, the one or more mobile external communications devices is an electronic mobile device carried by the person using the recording device 104 or an individual in proximity thereto. The mobile external communications device may be a mobile device that may be carried on the user's person. In one or more embodiments, the mobile external communications device may be a body camera, a cell phone or other wireless data recording and transmission device. In one or more embodiments, recordings from the recording device 104, including the recording unit 141 and or the power source unit 139, 420 may be wirelessly transmitted to the mobile external communication device where the recordings can be saved and stored and/or transmitted. In embodiments, the data management of the recording device 104 and the mobile external communications device may be authorized devices and compatible with existing law enforcement data management systems and requirements. Additionally, or alternatively, the transmission may be encrypted via public-key encryption methods and/or other types of encryption.

In one or more embodiments, recording unit 141 and or the power source unit 139, 420 and the mobile external communication device are may be wirelessly communicatively coupled. The recording device 104 and the mobile external communication device may be synced such that data, recordings, time stamps and ID's are linked and coordinated. In one or embodiments, power and recording modes are connected such that the start of recording by one initiates recording of the other device(s).

In one or more embodiment, the mobile device may wirelessly access and download recorded data from the recording device 104, in one or more embodiments, in real-time or near real-time. In one or more embodiments, the mobile device collects and coordinates the recorded data from the recording device 104 and, in one or more embodiments, the mobile device may be communicatively coupled to multiple recording devices 104 and may collect and coordinate recorded data from multiple recording devices for storage for later access or for transmission to another external communications device and/or server, in one or more embodiments, in real-time or near real-time.

In one or more embodiments, the communication link may facilitate uni-directional and/or bi-directional communication between the recording device(s) 104 and the mobile external communication device. Data and/or control signals may be transmitted between the recording device(s) 104 and the mobile external communication device to coordinate the functions of the recording device(s) 204 and/or the mobile external communication device. In one or more embodiments, the mobile external communications device is a body camera communicatively coupled to a recording device 104, both carried by one person. In one or more embodiments, the mobile external communications device is a body camera communicatively coupled to multiple recording devices 104 carried by multiple individuals. In embodiments, the communication link may be compatible with existing law enforcement data management systems and requirements.

Similarly, in various embodiments the memory of the power source unit 420 allows for easy data transfer from the recording device 104 to an external storage system. For example, in one or more embodiments, one or more charging nodes or docking stations can be configured to automatically download and/or transfer stored information from the memory to a more permanent database. In such a manner data transfer from the recording device 104 can be accomplished easily in the regular and required process of recharging the power source unit 420, obviating any requirements for removal of the recording device 104 from the gun 102 or other more complicated processes for transferring saved data.

For instance, referring to FIGS. 5A and 5B, a data transfer and hardware tracking system is depicted according to one or more embodiments of the disclosure. In one or more embodiments, the system 500 includes one or more charging nodes 512, 514, 516, that may be part of a docking station 517 and a server 518. Charging nodes are physical devices, usable by a consumer or other user, to recharge one or more power source units 420. The nodes may be integrated with the docking station 517, which is located at a law enforcement station where the law enforcement officers using the recording devices return after their shifts. However, in addition, charging nodes and/or docking station can include including processing elements, sensors, user interface, and memory 520. Seen in FIGS. 5A and 5B, nodes 512, 514, 516, and server 518, are interconnected via network 524, for communication. In one or more embodiments, the network 524 may be, for example, a local area network, a wide area network, a cloud computing environment, a public network (e.g. the internet), or other suitable network for communication between the networked elements of the system 500.

In one or more embodiments, the system 500 outputs data and receives inputs to/from users via the nodes 512, 514, 516, and server 518. For example, the nodes 512, 514, 516, and server 518 may each include input/output devices, for example a display and/or touchscreen 519, for interfacing with a user via a graphical user interface (GUI) or other user interface.

In one or more embodiments, one or more of the nodes 512, 514, 516, and server 518 includes application 522 (“App”). In some embodiments, the App 522 is a program or “software” that is stored in memory accessible by charging nodes 512, 514, 516, and server 518 for execution by logic/memory. In one or more embodiments App 522 includes a set of instructions for execution by processing elements on one or more of the charging nodes 512, 514, 516, or docking station, and server 518, for management of recorded data, hardware tracking, event tracking, and other functions. In certain embodiments, App 522 is stored locally on some or all of the nodes, or docking station, and server 512-518. In some embodiments, App 522 is stored remotely, accessible via a network.

The docking station 517 may have a plurality of assigned slots 523, each with labeled indicia 525 for receiving specifically assigned power source units, or the slots may be unassigned and receive any of the power source units 420.

In some embodiments, nodes 512, 514, 516, and server 518, are arranged in a client server architecture. For example, nodes 512-516 may be configured as clients with server 518. Depicted in FIGS. 5A-5B, server 518 is a computing node including database 530, and nodes 512, 514, 516 are clients that use App 522 to communicate with the server 518 to transfer recorded data 532 from memory 424, record/write hardware or user identification codes 534, and track/modify user accounts and user data 536. In some embodiments, App 522 is an application dedicated to data management, configured to collect user data from one or more docking power source units 420, including text, video, images, audio, and the like. In some embodiments, App 522 is a more generalized device tracking and event tracking system. In such embodiments, the App 522 is configured to associate and/or assign system hardware, such as the power source units 420 to specific users for close tracking of possession of system elements in the field.

In various embodiments App 522 may be configured to communicate with a server to create one or more user accounts. The user accounts may include an administrative account and one or more client accounts. In some embodiments, the administrative account may be a user account including privileges for configuring the system 500. For example, in some embodiments the administrative account may create or modify user accounts. In certain embodiments, the system 500 assigns/tracks possession of the devices by correlating the user account of users who physically possess certain elements of the system, such as a power source unit 420. In such embodiments, tracking of the power source unit 420 can be done via a unique hardware identifier associated with the power source unit, a software ID code, a combination, or the like. In such a manner, the user of the device and their assigned storage device 424 of the system can be mutually identified, for easy tracking of who possessed the device and when possession of the device occurred.

In some embodiments, the system can additionally include information on other hardware assigned to a user. For example, in various embodiments a hardware ID for a specific recording device 104 could be associated with a user account. Then, when the hardware ID of the power source unit 420 is subsequently associated with the user account, the system identifies which recording device it is coupled with.

The administrative account may assign which hardware codes/ID codes to specific user accounts. In some embodiments, this decision may be based on user data. For example, in some embodiments, the administrative account selectively assigns modules based on employee need, job requirements, etc. In one or more embodiments, the user data includes user information including, the user's name, date of birth, email address, phone number, and notification preferences. In some embodiments, the user data includes job information, such as, for example, the user's job, department, and position.

Referring now to FIG. 6, a block diagram of a computing node 612 is depicted, according to one or more embodiments of the disclosure. Computing node 612 is only one example of a suitable system and is not intended to suggest any limitation as to the scope of use or functionality of the embodiments described herein. Regardless, computing node 612 is capable of being implemented and/or performing any of the functionality set forth as described herein.

Computing node/server may be is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computing node/server 612 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed computing environments that include any of the above systems or devices, and the like.

Computing node/server 612 may be described in the general context of computer system, including executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computing node/server 612 may be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a network. In a distributed computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.

As shown in FIG. 6, computing node/server 612 is shown in the form of a general-purpose computing device. The components of computing node/server 612 may include, but are not limited to, one or more processors or processing units 629, a system memory 630, and a bus 631 that couples various system components including system memory 630 to processor 629.

Bus 631 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

Computing node/server 612 typically includes a variety of computer readable media. Such media may be any available media that is accessible by computing node/server 612, and it includes both volatile and non-volatile media, removable and non-removable media.

System memory 630 can include computer readable media in the form of volatile memory, such as random-access memory (RAM) 32 and/or cache memory 633. Computing node/server 612 may further include other removable/non-removable, volatile/non-volatile computer storage media. By way of example only, storage system 634 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 631 by one or more data media interfaces. As will be further depicted and described below, memory 630 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the disclosure.

Program/utility 640, having a set (at least one) of program modules 642, may be stored in memory 630 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 642 generally carry out the functions and/or methodologies of one or more of the embodiments described herein.

Computing node/server 612 may also communicate with one or more external devices 644 such as a keyboard, a pointing device, a display 646, etc.; one or more devices that enable a user to interact with computing node/server 612; and/or any devices (e.g., network card, modem, etc.) that enable computing node/server 612 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 648. Still yet, computing node/server 612 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 650. As depicted, network adapter 650 communicates with the other components of computing node/server 612 via bus 631. It should be understood that, although not shown, other hardware and/or software components could be used in conjunction with computing node/server 612. Examples, include, but are not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

Referring to FIGS. 7A-7B, methods 700, 716 of hardware tracking are depicted, according to one or more embodiments of the disclosure. In one or more embodiments, the method 700 includes, at operation 704, associating a hardware ID and/or ID code with a power source unit (“Device”). In one or more embodiments, the method 700 includes, at operation 708 recording removal of the power source unit from a charging node. In one or more embodiments, the method 700 includes, at operation 712, associating a user account with removed power source unit using hardware ID/ID Code.

In one or more embodiments, the method 716 includes, at operation 720, receiving a power source unit (“Device”) at a charging node. In one or more embodiments, the method 716 includes, at operation 724, recording a return of the power source unit to the charging node. In one or more embodiments, the method 716 includes, at operation 728, transferring data from the power source unit to a database. In one or more embodiments, the method 716 includes, at operation 732, disassociating a user account with the power source unit.

In one or more embodiments, data recorded by the recording device 104, including, for example, but not limited to, video, audio and device status data, is stored in memory of the power source unit 139, 420, which may be linked to an external device for access to and/or transfer of the recorded data, physical and/or remote. In embodiments, memory of each of the recording unit 141 and the power source unit 139, 420, stores and maintains a redundant data file set that includes a portion of the recorded data. Each redundant data file set may include one or more data files having certain recording and/or status data stored therein. In embodiments, the recording unit 141 and the power source unit 139, 420, may be configured to synchronize the redundant data files of the recording unit 141 and the power source unit 139, 420, such that the data therein is mirrored. In embodiments, such redundant data files may be used for data integrity and security, verification, identification, and authentication purposes. In one or more embodiments, redundant data files in the power source unit memory may be accessed by a server and/or external communication device and used for time-line analysis, verification of associated user and/or recording device/unit and/or device troubleshooting.

In one or more embodiments, each redundant data file of the recording unit 141 and the power source unit 139, 420 includes one or more data files having bits of certain recording and/or status data stored therein. In embodiments, the redundant data files may include, but not limited to, one or more of: date, time and/or location data; CSV files; time segments; user and/or hardware ID; recording device, recording unit and/or power source unit status data; power/charge data; and recording start/stop/interruption data. Additionally or alternatively, in embodiments, data stored in the redundant data files may include, but is not limited to, analog and frequency parameters, such as, but not limited to, pressure, temperature, current, and voltage; Boolean data such as device switch and actuator positions, indicator light illumination, and actuator commands; GPS data and/or GIS data, such as position and movement data; video and image information; audio information; programmed and device information; information about the environmental conditions; device control status and operational data generated by device systems; and data derived from a combination from any of the above including, but not limited to, additional data, video, and audio analysis and analytics.

According to one or more embodiments of the disclosure, recording device 104 is configured for and implemented in recording and/or monitoring uses and applications other than weapon mounted uses and applications. In embodiments, the recording device, comprising recording unit 141 and power source unit 139, 420, as described herein, may include the various features described herein, including, but not limited to, data transfer and collection, charging, redundancy, including recording unit/power source unit redundant data files, monitoring, communication linking, verification, identification, authentication and security features. In one or more embodiments, the recording device is configured to communicate/network with a server and/or external communication device. In one or more embodiments, a recording device or a set, kit or group of two or more of the recording devices may be associated with a common network, a server and/or an external communications device, as described herein, and may be part of a data management system for one or more recording devices, as described herein.

In one or more embodiments, the recording device 104 may include an engagement component configured to removably secure the recording device to a person, to a structure or in a particular location for recording and/or monitoring. A recording device may be secured/positioned in a location that is generally inaccessible. The recording device may be configured to record at set times or include one or more sensors, as described herein, and automatically record in response to a sensor trigger, for example, a motion sensor trigger. In embodiments, the power source unit 139/420 may be removed from the recording unit for charging and/or data transfer without detaching or moving the recording unit 141. In one or more embodiments, such tasks may also be conducted via cord and/or wireless connection.

In one or more embodiments, the recording device may be worn by or secured to a person, secured to a structure or positioned in a specific location. In embodiments, the engagement component may include, but is not limited to, one or more of: a clip, a strap, one or more magnets, a coupling, an adhesive, a hook, a slot or post, a hook and loop material, a bracket, a rail system and a mounting mechanism.

In one or more embodiments, the recording device may be configured and used as an industrial, residential and/or home recording and/or monitoring device. In embodiments, one or more of the recording devices may be used in association with a common network, server and/or external communications device, as described herein, and/or may be part of a data management system for one or more recording devices, as described herein, for industrial, residential and/or home recording and/or monitoring purposes.

Referring to FIGS. 3B-3D, which illustrated a power source unit 139, a recording unit 141 decoupled from the power source unit 139, and the recording unit 141 with a backing 430 removed, respectively, according to one or more embodiments of the disclosure. In one or more embodiments, the housing 403 of the recording unit 141 defines one or more recesses 417 configured to engage a portion of the power source unit 139, 420 to form a seal (e.g., a hermetic seal), such as to prevent dust or debris to enter. In one or more embodiments, the seal is a waterproof seal. In certain embodiments, the one or more recesses 417 are on the power source unit 139, 420 and configured to engage the housing 403 to form the seal. In one or more embodiments, the power source unit 139, 420 includes a sealing member 440. The sealing member 440 is configured to engage the recess(es) 417 of the housing 403 to form a seal and prevent debris and/or liquid from entering between the power source unit 139, 420 and the housing 403 when the power source unit 139, 420 is coupled 405 to the housing 404.

In one or more embodiments, recording device 104, without rail set 130A, 130B, may have a length of about 6 inches or less and, in some embodiments, a length of 5 inches or less. In some embodiments, the recording device may have a length of about 6 inches or less, a width of about 4 inches or less and a thickness of about 2 inches or less. In further embodiments, the recording device may have a length of about 5 inches or less, a width of about 3 inches or less and a thickness of about 1.5 inches or less. In still further embodiments, the recording device may have length of about 2 to about 5 inches, a width of about 0.9 to about 2.3 inches and a thickness of about 0.6 to about 1.5 inches. In one or more embodiments, the recording device has a length of about 3.0 inches, a width of about 1.4 inches and a thickness of about 0.9 inches. In one or more embodiments, the power source unit 139, 420, may have a length of about 4 inches or less and, in some embodiments, a length of 3 inches or less. In some embodiments, the power source unit may have a length of about 4 inches or less, a width of about 3 inches or less and a thickness of about 1.2 inches or less. In further embodiments, the power source unit may have a length of about 3 inches or less, a width of about 3 inches or less and a thickness of about 1.2 inches or less. In still further, the power source unit may have a length of about 1 to about 2.5 inches, a width of about 0.9 to about 2.3 inches and a thickness of about 0.4 to about 1 inch. In one or more embodiments, the power source unit may have a length of about 1.5 inches, a width of about 1.4 inches and a thickness of about 0.6 inches.

In one or more embodiments, features of the recording device may include one or more of: 1080p HD video camera with audio, instant-on camera activation (programmed and/or sensor triggered), microphone, adjustable tactical light, ambidextrous taclight activation, USB connectivity, password protection, and USB port(s) and system status indicator lights.

U.S. Pat. Nos. 10,459,678; 10,323,903; 10,060,701; 9,658,031; 5,430,967; 6571503; 6,185,854; 6,705,038; 8,182,109; 9,934,623, 9,467,500; 9,958,228; D873946; D873946; and D672005 are hereby incorporated by reference herein in their entirety for all purposes. In addition, U.S. Patent Publication Nos.: 2019/0222771; 2018/0106568; 2018/0196628; 2018/0238649; 2017/0155269; 2016/0172876; 2018/0321015; 20180299217; 2015/0184978; 2007/0061508; 2010/0178540; 20060204835; 2004/0244259; 2019/0304210; 2019/0063864; 2020/0109909; and 2015/0369554 are hereby incorporated by reference herein in their entirety for all purposes.

The patents, patent publications and other references mentioned above in all sections of this application are herein incorporated by reference in their entirety for all purposes. All of the features disclosed in this specification (including the references incorporated by reference, including any accompanying claims, abstract and drawings), and/or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and/or steps are mutually exclusive. The invention is not restricted to the details of the foregoing embodiment(s). The invention extends to any novel one, or any novel combination, of the features disclosed in this specification (including any incorporated by reference references, any accompanying claims, abstract and drawings), or to any novel one, or any novel combination, of the steps of any method or process so disclosed

The descriptions of the various embodiments of the present disclosure have been presented for purposes of illustration but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A recording device for mounting on a gun, the device comprising: a recording unit comprising a housing and a recording module within the housing; anda removable power source unit detachably coupled to the recording unit, wherein the removable power source unit comprises a housing, a battery and memory, the battery and memory being within the housing and the battery being configured for providing power to the recording device while attached thereto,wherein the memory of the removable power source unit includes data collected from the recording device and includes a hardware ID or ID code associated with a user of the recording device.

2. The recording device of claim 1, comprising a processing device and one or more sensors within the housing of the recording unit and the recording unit comprising a mounting assembly for mounting the recording unit to a barrel of the gun.

3. The device of claim 1, the recording unit comprising a processing device and memory, wherein each memory includes a redundant data file set, each redundant data file set including one or more data files having bits of recording and/or status data stored therein, wherein the redundant data set of the memories are synchronized.

4. The device of claim 1, wherein the recording unit and the power source unit each include a plurality of electrical contacts and one or more data contacts for transfer of data and power therebetween when coupled.

5. The device of claim 3, wherein the redundant data set of at least one of the power source unit and the recording unit is accessed by at least one of a server and an external communication device.