CA3062846A1

CA3062846A1 - Mobile digital video and data recording system

Info

Publication number: CA3062846A1
Application number: CA3062846A
Authority: CA
Inventors: Thomas J. Ii Predmore; George SHANIN
Original assignee: Seon Design Inc
Current assignee: Seon Design Inc
Priority date: 2016-04-22
Filing date: 2017-04-21
Publication date: 2017-10-26
Also published as: WO2017184931A1

Abstract

A mobile digital audio-visual recording (MDVR) system includes an audio/video (A/V) input module that generates media data including at least one of audio and video. A metadata interface includes at least one channel that transfers metadata thereon.
A data collection module includes a first data container and a second data container separate from the first data container. The data collection module is in signal communication with the metadata interface and the A/V interface, and receives the metadata and the media data. The data collection module stores the metadata in the first data container which excludes the media data, and separately stores the media data in the second data container.

Description

MOBILE DIGITAL VIDEO AND DATA RECORDING SYSTEM
TECHNICAL FIELD
[0001] The present invention relates generally to digital video recording systems, and more specifically, to mobile digital video recording systems.
BACKGROUND

[0002] Video and data surveillance systems are commonly used by individuals, businesses, and governments to remotely monitor activity. Traditional video, audio and data collection systems are limited because they comprise locally installed systems that store surveillance information locally and they operate with static software. These local systems are referred to as a standalone digital video recorder (DVR). A typical standalone DVR
system integrates audio/video (A/V) data and metadata into a single data stream, which is then stored together in a single database or data container. Consequently, the entire recorded A/V data file must be analyzed in order to obtain the metadata. In addition, such a video, audio and data collection system requires a labor intensive process of viewing the entire A/V
data file or data stream in order to analyze the related metadata.

[0003] Advances in technology have allowed for combining the components of a traditional video, audio and data collection system into a single, mobile package. This mobile package is typically referred to as a mobile DVR (MDVR) system. These MDVR
systems may be employed as surveillance systems on moving vehicles, such as buses, or as body-worn recording systems, such as a law enforcement body-camera system.
However, these traditional MDVR systems still store the integrated audio/video (A/V) data and metadata together in a single database which results in storing and analyzing vast amounts of data. Consequently, a vast amount of data must be streamed or downloaded before users can access or analyze the metadata associated with the media data.
SUMMARY

[0004] According to at least one embodiment, a mobile digital audio-visual recording (MDVR) system comprises an audio/video (A/V) input module configured to generate media data including at least one of audio and video and a metadata interface including at least one channel configured to transfer metadata thereon. The MDVR system further includes a data collection module including a first data container and a second data container separate from the first data container. The data collection module is in signal communication with the metadata interface and the A/V interface, and is configured to receive the metadata and the media data. The data collection module stores the metadata in the first data container and separately stores the media data in the second data container. The data collection module includes a hardware processor operatively connected to memory having instructions recorded thereon that, when read by the hardware processor, commands the processor to execute operations. The operations include identifying the metadata with respect to the media data and delivering the metadata to the first data container via a first data channel and delivering the media data to the second data container via a second data channel that is separate from the first data channel such that the first data container contains only the metadata while excluding the media data. The hardware controller receives a single data stream integrated with the metadata and the media data, extracts the metadata from the data stream, and delivers the extracted metadata to the first data container via the first data channel. The hardware controller receives a single data stream integrated with the metadata and the media data, extracts the metadata from the integrated data stream, and delivers the extracted metadata to the first data container via the first data channel. The hardware controller then stores the integrated metadata and media data to the second data container via the second data channel.
The A/V input module includes at least one microphone that captures the audio and at least one camera that captures the imagery. The metadata interface is a single or dual-line serial interface operating according to a message-based protocol, where the metadata is at least one of vehicle identification data; braking data, acceleration data, brake pedal/accelerator pedal position data, speed data, actuator state data, voltage/current data; location data; global-positioning satellite data; digital tags, and time stamps. The metadata interface is a wireless interface, and the metadata corresponds to a second user located nearby the first user, where the metadata includes user identification data; user-location data; global-positioning satellite data; digital tags, time stamps. The data collection module electrically communicates with at least one user-equipment (UE) device so as to receive UE metadata corresponding to the at least one user equipment device, the UE metadata including at least one of weaponry discharge detection, duration of weaponry discharge, Taser discharge detection, Taser battery power, Taser internal temperature. The MDVR system further comprises at least one metadata analytics module in signal communication with the data collection module. The metadata analytics module is configured to execute at least one analytics operation on the metadata stored in the first data container. The at least one metadata analytics module is configured to extract metadata integrated with media data from the second data container prior to executing at least one analytics operation on the extracted metadata.
The metadata analytics module includes a user interface (UI) configured to receive an input from a user indicative of a desired analytics operation, and the metadata analytics module generates at least one data management and content analytics solution from the metadata stored in the first recording medium based on the input. The MDVR system further comprises a recorded media control module configured to process the media data stored in the second recording medium. The recorded media control module is configured to perform at least one of A/V
data playback, sound adjustment, image rewind, image fast-forwarding, and image zooming.

[0005] In addition to one or more of the features described above or below, or as an alternative, further embodiments include a method of storing data collected by a mobile digital audio-visual recording (MDVR) system. The method comprises receiving media data from an electronic audio/video (A/V) device and receiving metadata from at least one electronic communication network interface. The method further includes outputting the metadata to a first data channel and outputting the media data to a second data channel that is separate and different from the first data channel and simultaneously storing the metadata in a first data storage unit and the media data in a second data storage unit that is separate and different from the first data storage unit. The metadata is simultaneously collected with respect to the media data, and the media data and the metadata are integrated in a single data stream. The method further comprises extracting the metadata from the integrated single data stream, delivers the extracted metadata to the first data container via the first data channel, and stores the integrated metadata and media data to the second data container via the second data channel. The method further comprises extracting metadata integrated with media data from the second data container prior to executing at least one analytics operation on the extracted metadata.
BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The subject matter which is regarded as the present disclosure is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other features of the present disclosure are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:

[0007] FIG. 1 is a top view of a mass transit vehicle including a MDVR system according to a non-limiting embodiment;

[0008] FIG. 2 illustrates a body-worn MDVR system according to a non-limiting embodiment;

[0009] FIG. 3 is a block diagram of a MDVR system according to a non-limiting embodiment; and

[0010] FIG. 4 is a flow diagram illustrating a method of storing metadata collected by a MDVR system separately from media data (e.g., audio and/or video) gathered by the MDVR system according to a non-limiting embodiment.
DETAILED DESCRIPTION

[0011] Various non-limiting embodiments provide a mobile audio/video recording (MDVR) system configured to collect audio data, visual data, and other data of interest (i.e., metadata), extract the data of interest from the audio and visual data, and store the data of interest in a first memory unit that is separate and independent from a second memory unit used to store the audio-visual data. In at least one embodiment, a MDVR system includes an A/V input module, a metadata interface, and a data collection module. The A/V
input module collects an A/V data such as, for example, audio-visual surveillance.
The metadata interface includes an electronic communication network interface such as a controller area network (CAN) bus or a Bluetooth interface, for example, capable of delivering message-based metadata. The data collection module includes two separate and individual data containers connected to a data collection module via two separate and individual data channels. The data collection module separately transfers the A/V data from the metadata such that the A/V data is stored in a first data container while the metadata is stored separately in the second data container. That is, the MDVR system provides a dedicated data container that exclusively stores metadata separately from media data (e.g., audio and/or video data). A data container may include two separate data files stored in a single data container (e.g., recordable storage medium) or may include two separate and individual recordable storage mediums.

[0012] The MDVR system therefore may provide various data management &
content analytics solutions based on the metadata which include analyzing and processing the metadata alone without requiring analysis and processing of the A/V data. In this manner, only a low amount of data is necessary to be streamed to provide users with real-time access to the metadata, as opposed to streaming large amounts of data necessitated when streaming media data integrated with the metadata.

[0013] Turning now to FIG. 1, a vehicle 10 in FIG. 1 includes a mobile digital video recording (MDVR) system 100, which during normal operation captures and records audio-visual segments using an onboard MDVR apparatus 102. The MDVR apparatus 102 includes an audio and/or video (A/V) input module 104, a data collection module 106, and at least one metadata interface 108.

[0014] The A/V input module 104 includes one or more media input devices. The media input devices may be installed at various locations throughout the vehicle 10. The media input devices include, but are not limited to, one or more images sensors (e.g., cameras) and one or more audio sensors (e.g., microphones).

[0015] The data collection module 106 includes a first data container 110a, a second data container 110b, and a data collection controller 112. The first and second data containers 110a-110b can be any suitable electronic medium for storing data files such as a recordable disc solid state memory, or the like. The data that may be stored includes, but is not limited to, video data, audio data, and/or other data of interest (i.e., metadata) such as digital tags, time stamps, GPS data, etc. In at least one embodiment, a data container may include two separate data files stored in a single data container or may include two separate and individual recordable storage mediums.

[0016] In at least one embodiment, A/V input module 104 and the metadata interface 108 simultaneously collect and output the media data and the metadata, respectively to the data collection module 106. The first data container 110a stores only the metadata, while the second data container 110b stores media data such as, for example, the audio data and the video data. In addition, the first data container 110a stores various vehicle data of interest (i.e., vehicle metadata). The vehicle metadata includes, but is not limited to, vehicle operation data, vehicle communication bus data (e.g., data frames), door opening/closing state, braking data, acceleration data, brake pedal/accelerator pedal position data, speed data, actuator state data, voltage/current data, switch/relay states, other general purpose input/outputs (GPI0s), etc. The metadata may also include all user input and device output information.

[0017] In at least one embodiment, the first and second data containers 110a-110b are each independently removable from the MDVR apparatus 102. The removed data containers 110a-110b may be reinserted into the MDVR apparatus 102, or moved to a different vehicle 10, or replaced by a different data container 110a-110b. During operation of the vehicle 10, the MDVR apparatus 102 and data containers 110a-110b may work in conjunction to act as a surveillance system for the vehicle 10. The vehicle 10, as shown by way of a non-limiting example, is a public bus 10 but can be any other suitable type of transportation vehicle such as a train, aircraft, etc.

[0018] With continued reference to FIG. 1, the data collection controller 112 is in signal communication with the first and second data containers 110a-110b via first and second data channels. The data collection controller 112 may be constructed as a hardware processor 112 operatively connected to memory (not shown in FIG. 1). The memory includes instructions recorded thereon that, when read by the processor 112, causes the processor 112 to perform various functions described in greater detail below.

[0019] The data collection module 106 is also in signal communication with the metadata interface 108. The metadata interface 108 may itself comprise of one or more interfaces configured to deliver metadata to the data collection module 106.
For example, a first wired serial-based metadata interface may deliver locally generated vehicle system metadata (e.g., data generated by a general purpose input/output), while a second wireless metadata interface may deliver metadata generated by one or more data sources other than the vehicle data (i.e., the data transferred on the wired metadata interface).

[0020] In at least one embodiment, the metadata interface 108 operates according to a message-based protocol such as, for example, a controller-area network (CAN) bus 108. The CAN bus 108 includes a single or dual-line that communicates various messages or data frames between one or more systems, sensors and/or actuators generally referred to as CAN
nodes 114a-114n. The data collection module 106 may itself act as a node, and therefore, is capable of receiving messages output by other CAN nodes 114a-114n in addition to the A/V
data provided by the A/V input module 102. The data collection controller 112 is capable of distinguishing the A/V data from the message data (i.e., metadata) received from the CAN
bus 108. In this manner, the data collection controller 112 may store the metadata received from the CAN bus in the first data container 110a and may separately store the A/V data in the second data container 110b.

[0021] Turning now to FIG. 2, a body-worn MDVR system 100 worn by a user 20 is illustrated according to a non-limiting embodiment. The MDVR system 100 includes an audio and/or video (A/V) input module 104, a data collection module 106, and a metadata interface 108. In at least one embodiment, the A/V input module 104 is separated from the data collection module 106. In this manner, the A/V input module 104 may be fastened to a different location of the person than the data collection module. The A/V
input module 104 may include one or more media input devices including, but not limited to, one or more images sensors (e.g., cameras) and one or more audio sensors (e.g., microphones).

[0022] The data collection module 106 includes a user-interface (UI) 109, a first data container 110a, a second data container 110b, and a data collection controller 112. The UI

109 is configured to receive one or more inputs provided by the user 20, and output one or more status alerts. The UI 109 may be manipulated by the user 20 to input a command that controls the operating mode of the data collection module 106 as described in greater detail below. In at least one embodiment, the user 20 may manipulate the UI 109 (i.e., input one or more commands) to operate the data collection module 106 in either a buffer mode or full-record mode. When operating in the buffer mode, the A/V input module 102 captures data, but A/V data and/or metadata is stored for only a predetermined time (e.g., 30 seconds) before being automatically deleted. When, however, operating in the full-record mode the A/V data and the metadata are stored in their respective first and second data containers 110a-110b. Both A/V data and metadata stored in response to activating the full-recording mode may not be deleted by the user 20. The UI 109 may also provide an alert such as a sound alert and/or graphical alert, for example, which informs the user 20 of the current operating mode. (all user input and device output information is also stored as metadata)

[0023] The first and second data containers 110a-110b can be any suitable electronic medium for storing data files such as a recordable disc solid state memory, or the like. The data that may be stored includes, but is not limited to, video data, audio data, and/or metadata such as digital tags, time stamps, GPS data, etc. In at least one embodiment, the first data container 110a stores only metadata, while the second data container 110b stores media data such as, for example, the audio data and the video data. In addition, the first data container 110a stores various user-equipment (UE) metadata associated with a UE device possessed by the user 20. The UE metadata includes, but is not limited to, weaponry discharge detection, duration of weaponry discharge, Taser discharge detection, Taser battery power, Taser internal temperature, etc. User-metadata may also be stored in the first data container 110a. The user-metadata may include user identification (ID) associated with the body-worn MDVR system 100, and all user input and device output. The body-worn MDVR
system of a particular user 20 may also wirelessly communicate with other body-worn MDVR systems 100 worn by users in the nearby vicinity. In this manner, additional user-metadata such as the IDs and/or equipment metadata of other nearby users may be stored in the first data container 110a of a subject user 20.

[0024] In at least one embodiment, the first and second data containers 110a-110b are each independently removable from the data collection module 106. The removed data containers 110a-110b may be reinserted into the data collection module 106, or moved to a docking station to be uploaded to a main data server (not shown), and analyzed by authorized personal other than the user 20.

[0025] With continued reference to FIG. 2, the data collection controller 112 is in signal communication with the first and second data containers 110a-110b via first and second data channels. The data collection controller 112 may be constructed as a hardware processor 112 operatively connected to memory (not shown in FIG. 2). The memory includes instructions recorded thereon that, when read by the processor 112, causes the processor 112 to perform various functions described in greater detail below.

[0026] The data collection module 106 is also in signal communication with the metadata interface 108. The metadata interface 108 may operate according to various wireless protocols including, but not limited to, Bluetooth, radio-frequency identification (RFID), etc. As mentioned above, the data collection 106 may wirelessly communicate with both the A/V input module 102 and the UE devices 111 possessed by the user 20.

Accordingly, the data collection controller 112 is capable of distinguishing the A/V data from the metadata received from the metadata interface 108. In this manner, the data collection controller 112 may store the metadata received from the metadata interface 108 in the first data container 110a while separately storing the A/V data in the second data container 110b.

[0027] With reference now to FIG. 3, a block diagram of a MDVR system 100 is illustrated according to a non-limiting embodiment. The MDVR system 100 includes an A/V
input module 104, a metadata interface 108, and a data collection module 106.
In at least one embodiment, the A/V input module 104, the metadata interface 108 and the data collection module 106 are combined in a single device to provide an integrated MDVR
apparatus such as an on-board vehicle MDVR apparatus is described in detail above. In another embodiment, the A/V input module 104 may be separated from the data collection module 106 and/or the metadata interface 108, while still configured to electrically communicate with the data collection module 106.

[0028] The audio/video (A/V) input module 104 is configured to generate media data including at least one of audio and video. For example, the A/V input module 104 may include one or more audio sensors 116a-116n that capture the audio and one or more image sensors 118a-118n that capture the imagery. The audio sensors 116a-116n may include, for example, a microphone and the image sensors 118a-118n may include a camera such as, for example, a video camera.

[0029] The metadata interface 108 includes at least one channel configured to transfer metadata thereon. In at least one embodiment, the metadata interface 108 includes, but is not limited to, Ethernet, and a serial channel interface. The serial channel interface may be a single or dual-line serial interface operating according to a message-based protocol such as, for example, a controller area network (CAN) bus installed on a vehicle to provide an on-board MDVR system. When constructed as an on-board vehicle MDVR system, the metadata transferred on the metadata interface 108 (e.g., CAN bus) includes, but is not limited to, vehicle identification data; braking data, acceleration data, brake pedal/accelerator pedal position data, speed data, location data; global-positioning satellite data; digital tags, and time stamps.

[0030] The metadata interface 108 may also include a wireless interface capable of providing a body-worn MDVR system. The wireless interface includes, for example, a Bluetooth interface or a radio-frequency identification (RFID) interface. When constructed as body-worn MDVR system, the metadata transferred on the metadata interface 108 (e.g., wireless interface) includes, but is not limited to, user identification data, user-location data, global-positioning satellite data, digital tags, time stamps, and metadata corresponding multiple users located near one another with each user possessing their own individual MDVR system 100. In at least one embodiment, the metadata interface 108 is also in electrical communication with one or more user equipment (UE) devices (e.g., a firearm, Taser, etc.). Accordingly, the metadata interface 108 may transfer UE metadata including, but not limited to, weaponry discharge detection, duration of weaponry discharge, Taser discharge detection, Taser battery power, and Taser internal temperature.

[0031] The metadata interface 108 may further include one or more general purpose input/outputs (GPIO s) 120a-120n, or physical node/terminals 120a-120n. The GPIO
channels 120a-120n may be in electrical communication with various actuator, relays, etc., that output data of interest including, but not limited to, sensor output signals, actuator state signals, voltage/current values, and switch/relay states.

[0032] Still referring to FIG. 3, the metadata interface 108 transfers metadata provided by one or more data sources 122a-122n. The data sources 122a-122n include, but are not limited to, a separate serial data interface, a separate Ethernet interface, a separate wireless interface configured to electrically communicate with a remotely located wireless device that provides local metadata or locally generated data of interest.

[0033] The data collection module 106 includes a hardware processor 112, a first data container 110a and a second data container 110b that is separate from the first data container 110a. The data collection module 106 is in signal communication with the A/V
interface 104 and the metadata interface 108. In this manner, the data collection module 106 is configured to receive the media data generated by the A/V input module 104 and the metadata provided by the metadata interface 108. When implemented as a body-worn MDVR system 100, the data collection module 106 may also be in electrical communication with at least one user-equipment (UE) device so as to receive UE metadata as described above.

[0034] According to at least one non-limiting embodiment, the data collection module 106 stores the metadata in the first data container 110a and separately stores the media data (e.g., audio and/or video) in the second data container 110b. For example, the hardware processor 112 is operatively connected to memory 124 having instructions recorded thereon that, when executed by the hardware processor 112, commands the processor 112 to identify (i.e., distinguish) the metadata with respect to the media data, deliver the metadata to the first data container 110a via a first data channel 126a, and deliver the media data to the second data container 110b via a second data channel 126b that is separate from the first data channel 126a. In at least one embodiment, the first data container 110a stores only the metadata while the second data container 110b stores both A/V data and metadata. Therefore, the system 100 still provides a dedicated storage unit (e.g., the first data container 110a that stores only metadata while excluding the A/V data.

[0035] In another embodiment, the hardware controller 112 may receive a single data stream integrated with the metadata and the media data, extract the metadata from the data stream, and then deliver the extracted metadata to the first data container 110a via the first data channel 126a. In this manner, the first data container 110a contains only the metadata provided by the metadata interface 108 while excluding the media data provided by the A/V
input module 104.

[0036] With further reference to FIG. 3, the MDVR system 100 further includes a metadata analytics module 128 and a recorded media control module 130. The metadata analytics module 128 is in signal communication with the data collection module 106. The metadata analytics module 128 includes a graphical user interface (GUI) 132 and a hardware controller 134 (including memory). The metadata analytics module 128 is configured to generate one or more data management and content analytics solutions in response to executing one or more analytics operations on the metadata stored in the first data container 110a. The analytics operations include, but are not limited to, querying a specific type of metadata (e.g., data of interest) from the first data container 110a, downloading only a specific type of metadata from the first data container 110a. Another analytics solution includes providing one or more users with real-time access to only the meta-data stored in the first data container 110a. Therefore, only a low amount of data is necessary to be streamed to provide users with real-time access to the metadata, as opposed to streaming large amounts of data necessitated when streaming media data integrated with the metadata.
Accordingly, the metadata may be obtained before ever having played-back or replayed the media data. For example, a user may review the metadata first, without the need to view the media data, and then subsequently view the media data, if necessary, to corroborate the metadata and/or obtain additional audio and/or visual data related to the metadata data.

[0037] In at least one embodiment, multiple metadata analysis modules 128 may electrically communicate with the data collection module 106 and access the metadata stored in the first recording medium 110a in parallel. In this manner, multiple individual analytics solutions may be performed on the metadata in parallel. For instance, a first analytics operation may be performed by a first metadata analysis module, while a different analytics operation may be performed by a different analysis module. In addition, a single metadata analysis module 128 is capable of communicating with one or more other data collection modules installed in one or more other (e.g., remotely located) MDVR systems 100. In this manner, one or more analytics operations (e.g., a metadata search query) may be output to multiple different data collection modules 106 of different systems using only a single metadata analysis module 128. Accordingly, the MDVR system 100 may significantly reduce the work and time necessitated by conventional systems that require analyzing an A/V
stream integrated with metadata.

[0038] The recorded media control module 130 is configured to process the media data stored in the second recording medium 110b. For example, the recorded media control module 130 is configured to perform at least one of A/V data playback, sound adjustment, image rewind, image fast-forwarding, and image zooming. The recorded media control module 130 is also capable of performing metadata analysis originating from collected A/V
media, however, the recorded media control module 130 may perform the analysis only after the A/V data stream has been downloaded and a pre-process or extraction has occurred.

[0039] Turing now to FIG. 4, a method of storing metadata collected by a MDVR
system separately from media data (e.g., audio and/or visual data) gathered by the MDVR
system is illustrated according to a non-limiting embodiment. The method begins at operation 400, and at operation 402 media data such as audio data and visual data, for example, is captured and output by one or more media devices. The media devices include, for example, a microphone and a camera. At operation 404, data of interest other than media data (e.g., metadata) is captured and output. In at least one embodiment, the media data may be collected at the same time as the metadata using two different inputs. For example, the first input corresponding to the media data is different than the second input corresponding to the metadata. The different inputs allow for individually collecting media data only, metadata only, and/or collecting media data and metadata simultaneously. The media data and metadata may also be integrated into a single data stream and output to the data collection module accordingly.

[0040] Regardless as to how the media data and metadata are received, the media data is output to a first data channel at operation 406, while the metadata is output to a second data channel at operation 408. In the scenario where a single integrated data stream is received, at least one embodiment provides a data collection module capable of extracting only the metadata from the data stream before the media data and metadata are delivered to the first and second data channels, respectively. At operation 410, the media is stored in a first data container (e.g., first data storage unit) while the media data is stored in a second container (e.g., second data storage unit) separate and different form the first data container.
Accordingly, the second data container includes the metadata while excluding the media data.
The first data container, however, may include media data and/or metadata. In at least one embodiment, the media data is stored in the first data container, while the metadata is simultaneously stored in second data storage unit, and the method ends at operation 412.
Since at least one non-limiting embodiment provides a data container that includes the metadata while excluding the media data, the metadata may be obtained before ever having played-back or viewed the media data. For example, a user may review the metadata from the first storage data container first, without the combined media data and metadata being required to be first downloaded from the second storage data container, played-back and analyzed. In addition, providing the first data container dedicated to storing metadata while excluding the media data (e.g., A/V data) allows independent manipulation and analysis of the first storage unit and the metadata stored therein, without the need to also analyze the media data.

[0041] As described in detail above, various embodiments provide a mobile audio/video recording (MDVR) system configured to collect audio data, visual data, and other data of interest (i.e., metadata), extract the data of interest from the audio and visual data, and store the data of interest in a first memory unit that is separate and independent from a second memory unit used to store the audio-visual data. Accordingly, the MDVR
system may provide various data management & content analytics solutions based on the metadata which include analyzing and processing the metadata alone without requiring analysis and processing of the A/V data which is typically a substantially larger data size than the metadata.

[0042] As used herein, the term "module" refers to an application specific integrated circuit (ASIC), an electronic circuit, an electronic computer processor (shared, dedicated, or group) and memory that executes one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality. When implemented in software, a module can be embodied in memory as a non-transitory machine-readable storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method.

[0043] While the present disclosure has been described in detail in connection with only a limited number of embodiments, it should be readily understood that the present disclosure is not limited to such disclosed embodiments. Rather, the present disclosure can be modified to incorporate any number of variations, alterations, substitutions or equivalent arrangements not heretofore described, but which are commensurate with the spirit and scope of the present disclosure. Additionally, while various embodiments of the present disclosure have been described, it is to be understood that aspects of the present disclosure may include only some of the described embodiments. Accordingly, the present disclosure is not to be seen as limited by the foregoing description, but is only limited by the scope of the appended claims.

Claims

CLAIMS:

1. A mobile digital audio-visual recording (MDVR) system, comprising:
an audio/video (A/V) input module configured to generate media data including at least one of audio and video;
a metadata interface including at least one channel configured to transfer metadata thereon; and a data collection module including a first data container and a second data container separate from the first data container, the data collection module in signal communication with the metadata interface and the A/V interface, and configured to receive the metadata and the media data, wherein the data collection module stores the metadata in the first data container and separately stores the media data in the second data container.

2. The MDVR system of claim 1, wherein the data collection module includes a hardware processor operatively connected to memory having instructions recorded thereon that, when read by the hardware processor, commands the processor to execute operations comprising:
identifying the metadata with respect to the media data; and delivering the metadata to the first data container via a first data channel and delivering the media data to the second data container via a second data channel that is separate from the first data channel such that the first data container contains only the metadata while excluding the media data.

3. The MDVR system of claim 2, wherein the hardware controller receives a single data stream integrated with the metadata and the media data, extracts the metadata from the data stream, and delivers the extracted metadata to the first data container via the first data channel.

4. The MDVR system of claim 2, wherein the hardware controller receives a single data stream integrated with the metadata and the media data, extracts the metadata from the integrated data stream, and delivers the extracted metadata to the first data container via the first data channel, and stores the integrated metadata and media data to the second data container via the second data channel.

5. The MDVR system of claim 1, wherein the A/V input module includes at least one microphone that captures the audio and at least one camera that captures the imagery.

6. The MDVR system of claim 1, wherein the metadata interface is a single or dual-line serial interface operating according to a message-based protocol.

7. The MDVR system of claim 6, wherein the metadata is at least one of vehicle identification data; braking data, acceleration data, brake pedal/accelerator pedal position data, speed data, actuator state data, voltage/current data; location data;
global-positioning satellite data; digital tags, and time stamps.

8. The MDVR system of claim 1, wherein the metadata interface is a wireless interface, and the metadata corresponds to a second user located nearby the first user.

9. The MDVR system of claim 8, wherein the metadata includes user identification data; user-location data; global-positioning satellite data;
digital tags, time stamps.

10. The MDVR system of claim 8, wherein the data collection module electrically communicates with at least one user-equipment (UE) device so as to receive UE
metadata corresponding to the at least one user equipment device, the UE metadata including at least one of weaponry discharge detection, duration of weaponry discharge, Taser discharge detection, Taser battery power, Taser internal temperature.

11. The MDVR system of claim 1, further comprising at least one metadata analytics module in signal communication with the data collection module, the metadata analytics module configured to execute at least one analytics operation on the metadata stored in the first data container.

12. The MDVR system of claim 11, wherein the at least one metadata analytics module is configured to extract metadata integrated with media data from the second data container prior to executing at least one analytics operation on the extracted metadata.

13. The MDVR system of claim 10, wherein the metadata analytics module includes a user interface (UI) configured to receive an input from a user indicative of a desired analytics operation, and wherein the metadata analytics module generates at least one data management and content analytics solution from the metadata stored in the first data container based on the input.

14. The MDVR system of claim 11, further comprising a recorded media control module configured to process the media data stored in the second data container.

15. The MDVR system of claim 12, wherein the recorded media control module is configured to perform at least one of A/V data playback, sound adjustment, image rewind, image fast-forwarding, and image zooming.

16. A method of storing data collected by a mobile digital audio-visual recording (MDVR) system, the method comprising:
receiving media data from an electronic audio/video (A/V) device and receiving metadata from at least one electronic communication network interface;
outputting the metadata to a first data channel and outputting the media data to a second data channel that is separate and different from the first data channel; and simultaneously storing the metadata in a first data storage unit and the media data in a second data storage unit that is separate and different from the first data storage unit.

17. The method of claim 16, wherein the metadata is simultaneously collected with respect to the media data.

18. The method of claim 16, wherein the media data and the metadata are integrated in a single data stream.

19. The method of claim 18, further comprising extracting the metadata from the integrated single data stream;
delivering the extracted metadata to the first data container via the first data channel, and storing the integrated metadata and media data to the second data container via the second data channel.

20. The method of claim 19, further comprising extracting metadata integrated with media data from the second data container prior to executing at least one analytics operation on the extracted metadata.