US 10,013,883 B2Grant
Tracking and analysis of drivers within a fleet of vehicles
Issue Date:2018-07-03
•20 Claims
•14 Drawing Sheets
Abstract
A system for tracking a fleet of vehicles and analyzing a driver associated with the fleet of vehicles. The system includes a monitoring engine for receiving information from a vehicle-tracking device associated with a vehicle of the fleet. A mapping engine displays, to a user, an icon indicative of an incident on a map. A video repository engine receives video data from a video camera associated with the vehicle and associates an incident video with the icon. A driver analysis engine obtains the incident information associated with a plurality of drivers and analyzes the incident information associated with the driver to generate a driver profile. The driver analysis engine compares the driver with corresponding drivers in the same and other fleets.
Metadata
Assignee
- Digital Ally, Inc.
Inventors
- James W. Farnham, IV
- Steven L. Phillips
- Jason R. Troxel
- John Rumage
Application Information
Application Number:US 14/746,058
Filing Date:2015-06-22
Priority Date:2015-06-22
Art Unit:2485
Classifications
IPC:
H04N7/18G08G1/00G06F3/0481G06F3/0484G08G1/01G08G1/04G08G1/127G07C5/00G07C5/08
Field of Search:
G06F 3/04817G06F 3/04842G08G 1/127G08G 1/0133G08G 1/04G08G 1/20
Patent Drawings (14 sheets)
Description
Background
[0001] 1. Field
[0002] Embodiments of the invention relate to the tracking and analysis of drivers within a fleet of vehicles.
[0003] 2. Related Art
[0004] Operators of fleets of vehicles desire tools to track and analyze their fleets. These fleets comprise a plurality of vehicles that are commonly associated. For example, a fleet of vehicles could be a commercial delivery service, a city police department, a state emergency response team, a military unit, or the like. Fleets require extensive costs for maintenance of the vehicles and training of the drivers. The fleet also represents a litigation liability for the operator due to the potential for property damage and injury that can be caused by the drivers. Therefore, operators desire detailed information on their drivers' activities while operating the vehicles.
[0005] Systems of the prior art utilize a vehicle-tracking device that is disposed in the vehicle. The vehicle-tracking device monitors the location and status of the vehicle and transmits this information to a central location. The central location may then populate a map with location and incident information and may also track incidents related to each driver.
[0006] These systems of the prior art have several drawbacks. First, any video of the incident is not associated with the incident in the system, or must be manually located and extracted. Second, incidents are difficult to review due to the lack of associated video. Third, the simple analysis performed by the systems of the prior art provides little meaningful information.
Summary
[0007] Embodiments of the invention solve the above-mentioned problems by providing a system, a computer program, and a method of fleet tracking and analysis. Embodiments of the invention associate video data from a video camera with the incident. Embodiments of the invention then populate the map with segments of the video to aid in the review of the incident by a supervisor. Embodiments of the invention perform detailed analysis of the drivers by comparing the drivers against other drivers in the fleet, across other fleets, across other similar drivers of other fleets, etc. Embodiments of the invention therefore provide improved analytical tools for operators of the fleet.
[0008] A first embodiment of the invention is directed to a system for tracking a fleet of vehicles. The system includes a monitoring engine for receiving information from a vehicle-tracking device associated with a vehicle of the fleet, wherein at least a portion of said information is incident information that is associated with an incident detected by the vehicle-tracking device. The system also includes a mapping engine for displaying, to a user, an icon indicative of the incident on a map, wherein the icon is located on the map in a location corresponding to an incident location. The system also includes a video repository engine for receiving video data from a video camera associated with the vehicle, said video repository engine acquiring an incident video based upon at least a portion of said video data. The mapping engine associates the incident video with said icon displayed on the map such that the user may select and view the incident video.
[0009] A second embodiment of the invention is directed to a system for analyzing a driver associated with a fleet of vehicles. The system includes a monitoring engine for receiving information from a vehicle-tracking device associated with a vehicle of the fleet that is associated with the driver, wherein at least a portion of said information is an incident information associated with an incident detected by the vehicle-tracking device. The system also includes a driver analysis engine for obtaining the incident information associated with a plurality of drivers, wherein the driver is one of said plurality of drivers. The driver analysis engine also analyzes the incident information associated with the driver to generate a driver profile. The driver analysis engine also compares the driver profile for the driver with corresponding driver profiles for the plurality of drivers.
[0010] A third embodiment of the invention is directed to a system for tracking a fleet of vehicles and analyzing a driver associated with the fleet of vehicles. The system includes a monitoring engine for receiving information from a vehicle-tracking device associated with a vehicle of the fleet, wherein at least a portion of said information is incident information that is associated with an incident detected by the vehicle-tracking device. The system also includes a mapping engine for displaying, to a user, an icon indicative of the incident on a map, wherein the icon is located on the map in a location corresponding to an incident location. The system also includes a video repository engine for receiving video data from a video camera associated with the vehicle. The video repository engine acquires an incident video based upon at least a portion of said video data. The mapping engine associates the incident video with said icon displayed on the map such that the user may select and view the incident video. The system also includes a driver analysis engine for obtaining the incident information associated with a plurality of drivers, wherein the driver is one of said plurality of drivers. The driver analysis engine analyzes the incident information associated with the driver to generate a driver profile. The driver analysis engine also compares the driver profile for the driver with corresponding driver profiles for the plurality of drivers.
[0011] A fourth embodiment of the invention is directed to a non-transitory computer readable medium having a computer program stored thereon. The computer program instructs at least one processing element to perform the at least a portion of the steps discussed herein.
[0012] A fifth embodiment of the invention is directed to a computerized method for tracking a fleet of vehicles and/or analyzing a driver of the fleet of vehicles. The method comprises at least a portion of the steps discussed herein.
[0013] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Other aspects and advantages of the invention will be apparent from the following detailed description of the embodiments and the accompanying drawing figures.
Brief Description of the Drawing Figures
[0014] Embodiments of the invention are described in detail below with reference to the attached drawing figures, wherein:
[0015] FIG. 1 is a system diagram illustrating the interactions of the various components of the system;
[0016] FIG. 2 is a system diagram illustrating the various hardware components associated with a vehicle;
[0017] FIG. 3 is a perspective view of a first embodiment of a vehicle-tracking device;
[0018] FIG. 4 is a flow diagram illustrating exemplary steps performed by a monitoring engine;
[0019] FIG. 5 is a flow diagram illustrating exemplary steps performed by a mapping engine;
[0020] FIG. 6 is a flow diagram illustrating exemplary steps performed by a video repository engine;
[0021] FIG. 7 is an exemplary depiction of a map with icons thereon;
[0022] FIG. 8 is an exemplary depiction of an incident review interface;
[0023] FIG. 9 is a flow diagram illustrating exemplary steps performed by a driver analysis engine;
[0024] FIG. 10 is a chart diagram illustrating an exemplary driver analysis;
[0025] FIG. 11 is a chart diagram illustrating an exemplary analysis of the drivers within a fleet;
[0026] FIG. 12 is a chart diagram illustrating an exemplary analysis of the fleet; and
[0027] FIG. 13 is a system diagram of an embodiment of the invention depicting various computing devices and their components.
[0028] The drawing figures do not limit the invention to the specific embodiments disclosed and described herein. The drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the invention.
Detailed Description
[0029] The following detailed description references the accompanying drawings that illustrate specific embodiments in which the invention can be practiced. The embodiments are intended to describe aspects of the invention in sufficient detail to enable those skilled in the art to practice the invention. Other embodiments can be utilized and changes can be made without departing from the scope of the invention. The following detailed description is, therefore, not to be taken in a limiting sense. The scope of the invention is defined only by the appended claims, along with the full scope of equivalents to which such claims are entitled.
[0030] In this description, references to “one embodiment,” “an embodiment,” or “embodiments” mean that the feature or features being referred to are included in at least one embodiment of the technology. Separate references to “one embodiment,” “an embodiment,” or “embodiments” in this description do not necessarily refer to the same embodiment and are also not mutually exclusive unless so stated and/or except as will be readily apparent to those skilled in the art from the description. For example, a feature, structure, act, etc. described in one embodiment may also be included in other embodiments, but is not necessarily included. Thus, the current technology can include a variety of combinations and/or integrations of the embodiments described herein.
[0031] Embodiments of the invention are broadly directed to a system 10 for providing an operator, supervisor, or administrator of a fleet 12 with tools to maximize the safety, cost efficiency, and effectiveness of the fleet 12. Embodiments of the invention improve safety by identifying weaknesses and other characteristics of a driver 14 that can be improved to reduce the likelihood and severity of accidents. Embodiments of the invention improve cost efficiency by reducing fuel and other maintenance costs, providing exculpatory evidence in the case of litigation, etc. Embodiments of the invention improve effectiveness of the fleet 12 by recommending training or changes in behavior of the drivers 14.
[0032] Before discussing embodiments of the invention in depth, a few terms will be discussed so as to orient the reader. It should be noted, however, that the terms discussed herein provide exemplary discussions that should not be considered constraining on the construction of said terms.
[0033] As used herein, a “fleet” is an association of vehicles 16, machinery, or other devices. Vehicles 16 of the fleet 12 can be operated primarily on land, primarily in water, primarily in the air, primarily in space, etc. Typically, a fleet 12 is united in a common purpose, location, or control. For example, the fleet 12 may all be owned and/or operated by a single company, organization, or government entity. Examples of fleets 12 include a group of commercial shipping vehicles, a group of taxi cabs owned by a company in a certain city, a company's commercial shipping barges, a school district's school buses, law enforcement vehicles belonging to a certain municipality, a squadron of military airplanes, etc. For the sake of clarity, the fleet 12 will primarily be referred to as a fleet 12 of law enforcement vehicles throughout the remainder of this application; however, this is only exemplary.
[0034] As used herein, a “driver” is a driver 14 of the vehicle 16, an operator of the vehicle 16, a pilot of the vehicle 16, a captain of the vehicle 16, another crew member associated with the vehicle 16, etc. The driver 14 may be co-located with the vehicle 16, or may be remote. For example, a driver 14 in a fleet 12 of unmanned aerial vehicles may be located hundreds of miles away from the vehicle 16. Typically, the driver 14 is responsible for the movement of the vehicle 16 through its environment. Generally speaking, embodiments of the invention track and evaluate how the driver 14 moves the vehicle 16 through its environment.
[0035] Turning to the figures, general components associated with the system 10 are depicted in FIG. 1 . At least one vehicle 16 and in embodiments, a plurality of vehicles, are associated in a fleet 12. Each vehicle 16 of the fleet 12 contains a vehicle-tracking device 18 and at least one video camera 20. Typically, the vehicle-tracking device 18 is located within or on the vehicle 16. The vehicle-tracking device 18 is discussed in more detail below. The at least one video camera 20 may be disposed within the vehicle 16 and oriented outward (such as in the direction of travel), disposed within the vehicle 16 and oriented inward (such as to observe the driver 14), etc.
[0036] As the vehicle 16 is operating, the vehicle-tracking device 18 is acquiring information regarding various aspects of the vehicle 16 such as location, speed, acceleration, the use of brakes, the use of blinkers, and the like. Abnormal behaviors or conditions may be detected by the vehicle-tracking device 18 (known as “incidents,” discussed more below). The vehicle-tracking device 18 communicates with a monitoring engine. The vehicle-tracking device 18 sends information to the monitoring engine such as location, speed, incident information, etc. In embodiments of the invention, communication between the vehicle-tracking device 18 and the monitoring engine happens substantially in real time. A mapping engine generates a display of a map 22 on a display for the user. The mapping engine generates an icon 24 to display on the map 22. The icon 24 is indicative of a location and/or a status of the vehicle 16, based upon the information received by the monitoring engine from the vehicle-tracking device 18. The location of the icon 24 on the map 22, color, written information, and the like may be periodically or continuously updated based on newly received information from the vehicle-tracking device 18.
[0037] Upon the vehicle 16 traveling or returning to an upload location (such as a facility associated with the fleet 12), a video repository engine communicates with the video camera 20 disposed in the vehicle 16. The video repository engine receives, retrieves, or otherwise acquires video data from the video camera 20 in the vehicle 16. Typically, the video repository engine acquires the video data at a time later than the incident. For example, in the case of a law enforcement vehicle, when the law enforcement vehicle returns to the central law enforcement station, the video repository engine may communicate with the video camera 20 (or other device) to download the recorded video data. Alternatively, recorded video data may be transmitted to the video repository engine in substantially real time as the incident is occurring (e.g., “live streamed”), at a time later than the incident but prior to the vehicle 16 returning to the upload location, or in response to a user request to download the video data.
[0038] A driver analysis engine acquires data regarding the performance of the driver 14 from the monitoring engine. The driver analysis engine may also receive information from the video repository engine and/or the mapping engine. The driver analysis engine compares the information related to the driver's performance against historical information for the driver 14, established standards, and comparisons to other drivers 14. Based upon this analysis, the driver analysis engine may present information for a supervisor to review, recommend training, etc.
[0039] FIG. 2 depicts various hardware components associated with the vehicle 16. It should be noted that FIG. 2 depicts the vehicle 16 as a law enforcement vehicle and the driver 14 as a law enforcement officer, but this is merely exemplary. Embodiments of the invention are directed to other vehicles 16 and drivers 14, such as those discussed above. Hardware components associated with the vehicle 16 may include the vehicle-tracking device 18, a video camera 20 that is a vehicle-mounted video camera 26, a recording device manager 28, a driver computing device 30, a video camera 20 that is a person-mounted video camera 32 worn by the driver 14, a proximity tag 34 worn by the driver 14, etc. Typically, the vehicle-tracking device 18, the vehicle-mounted video camera 26, the recording device manager 28, and the computing device are all installed in and powered by the vehicle 16. The person-mounted video camera 32 and proximity tag 34 are typically disposed on the driver 14 or other person. The person-mounted video camera 32 records events either as the driver 14 is operating the vehicle 16 and/or as the driver 14 is outside of the vehicle 16. The proximity tag 34 authenticates which driver 14 is operating the vehicle 16.
[0040] In some embodiments, the vehicle-tracking device 18 communicates only with the monitoring engine and not with any of the other components. In other embodiments, the vehicle-tracking device 18 communicates with the recording device manager 28 to send incident information, location information, and the like. In these embodiments, the recording device manager 28 may instruct the video camera 20 or other recording device to save the information from vehicle-tracking device 18. In addition, the video camera 20 or other recording device manager 28 may associate the information with the video data being recorded. In still other embodiments, the vehicle-tracking device 18 communicates directly with the video camera 20 or other recording device to provide incident information and/or current information about the status of the vehicle 16. In yet further embodiments, the vehicle-tracking device 18 communicates with the driver computing device 30, such that information from the vehicle-tracking device 18 is displayed to the driver 14 in the vehicle 16. This allows the driver 14 to make adjustments to driving habits to avoid future incidents, be able to discuss prior incidents with a dispatcher or supervisor while still driving, etc. The driver computing device may also display the map 22 to the driver 14.
[0041] It should be noted that while the vehicle-tracking device 18, the vehicle-mounted video camera 26, the recording device manager 28, and the driver computing device 30 are depicted in FIG. 2 as separate hardware components, in some embodiments of the invention various components are co-located in a single hardware component. For example, the vehicle-tracking device 18 may be located within the housing of the vehicle-mounted video camera 26, such as in the rear-view mirror of the vehicle 16 (as shown in FIG. 2 ). In some embodiments, there is no recording device manager or driver computing device 30 within the vehicle 16.
[0042] The components of the vehicle-tracking device 18 are schematically illustrated in FIG. 3 . Broadly, the vehicle-tracking device 18 comprises a body 36 and a vehicle interface 38. Within the body 36, the vehicle-tracking device 18 comprises an accelerometer 40, a location element 42, a vehicle status element 44, and a communications element 46. The vehicle-tracking device 18 may further comprise a processing element 48, a memory element 50, and a proximity tag reader 52.
[0043] The accelerometer 40 independently detects accelerations of the vehicle 16. The detected accelerations can be vertical (e.g. traveling over a bump or pothole too fast), horizontal forward (e.g. the driver 14 is accelerating or braking too quickly), and horizontal lateral (e.g. the driver 14 is taking turns at a high rate of speed). Accelerations that surpass a certain threshold are recorded and transmitted as incidents. The threshold may be fixed (e.g. a maximum safe acceleration rate of the vehicle 16), variable based upon location (e.g. within the posted speed limit, as determined by a map associated with the location element 42), variable based upon conditions (e.g. a very sudden deceleration or impact may be indicative of a vehicle crash), or the like.
[0044] The location element 42 determines the location of the vehicle 16. In some embodiments, the location element 42 utilizes the global positioning system (GPS) to determine location. The location element 42 determines the GPS location of the vehicle-tracking device 18 (and thereby the vehicle 16). The location element 42 transmits information indicative of the location to the processing element 48. The location information may then be stored on the memory element 50 of the vehicle-tracking device 18 and/or be transmitted to the recording device manager 28 and/or monitoring engine via the communications element 46. The location element 42 may also determine and record the time of the incident. This information can, like the incident information and other data, be further saved as video metadata, as described above. The location information and time information provide further authentication to the incident information.
[0045] The vehicle status element 44 interfaces with the vehicle 16 via the vehicle interface 38 and an on-board diagnostics (OBD) port in the vehicle 16 to determine various statuses of the vehicle 16. For example, the vehicle status element 44 may determine when and if the brakes are applied, the blinker is engaged, the engine is running, the headlights are on, the gas pedal is depressed, etc. The vehicle status element 44 may also determine levels and warnings displayed in the vehicle 16, such as the “check engine” light, the fuel level, the emergency brake, etc. The vehicle status element 44 provides operating information such as idle time, travel time, working time, etc. In some embodiments, the vehicle status element 44 stores this information. In some embodiments, the vehicle status element 44 records this information in connection with an incident (“incident information”). In other embodiments, the vehicle status element 44 records all of this information for later use and/or communicates at least a portion of the information to the recording device manager 28 for association with the recorded video data.
[0046] The communications element 46 of the vehicle-tracking device 18 transmits incident information and other information to the monitoring engine. In some embodiments, the vehicle-tracking device 18 sends continuous or substantially continuous information to the monitoring engine regarding the vehicle's location. In some embodiments, the vehicle-tracking device 18 sends incident information regarding an incident detected by the vehicle-tracking device 18. In still other embodiments, certain incidents are communicated if they are above a threshold severity. For example, the communications element 46 may send incident information to the monitoring engine for vehicular accidents and vehicle breakdowns but will not send incident information for other unsafe driving incidents.
[0047] In some embodiments of the invention, the communications element 46 is communicatively linked to the recording device manager 28 and/or the driver computing device 30, such that messages can be sent therebetween. In some embodiments, the communications element 46 is also communicatively coupled, either directly or indirectly, with one or more other elements of the system 10. In addition to the incident information, the vehicle-tracking device 18 may transmit information indicative of a status. The status could include information such as vehicle-tracking device power on, vehicle power on, vehicle driving, error detected, error not detected, name of the driver 14 (based, in some embodiments, upon the proximity tag system discussed below), one or more identifiers (such as model number or serial number) associated with vehicle-tracking device 18, etc. All of this information can be stored as metadata for video recorded by one or more video cameras 20, or displayed in real time by one or more displays associated with the system 10.
[0048] The communications element 46 of the vehicle-tracking device 18 may be wirelessly connected to the recording device manager 28, the driver computing device 30, and/or the monitoring engine. The communications element 46 transmits the incident information and/or status substantially in real time (as defined below). Typically, the communications element 46 will operate via the mobile broadband network, Bluetooth technology, Wi-Fi technology, or the like. The communications element 46 may alternatively or in addition be connected via a communications wire to the recording device manager 28, the driver computing device 32, and/or video camera 20.
[0049] The incident information may be stored in metadata of the recorded video data from the at least one video camera 20. In some embodiments, the storage of the metadata may be done in substantially real time as the vehicle 16 is operating. In other embodiments, the storage of the metadata is performed automatically or semi-automatically after the vehicle 16 returns to the upload location, discussed below.
[0050] Metadata associates one set of data with another set of data. The metadata may be embedded in the captured video data, stored externally in a separate file that is associated with the captured video data, otherwise associated with the captured video data, or all of the above. Embedding the incident information into the same file with the captured video data can be advantageous because it allows the metadata to travel as part of the data it describes. In some such embodiments, metadata is associated with a particular frame or frames of the video data. This is advantageous where, for example, the same video file contains more than one incident. In other such embodiments, the metadata is associated with the video file as a whole. Externally stored metadata may also have advantages, such as ease of searching and indexing. The metadata may also be stored in a human-readable format, such that a user can access, understand, and edit the metadata without any special software. Some information stored in the metadata may be relatively static, such as a manufacturer name and model of the vehicle-tracking device 18, an identifier assigned to the specific vehicle-tracking device 18 by a law enforcement agency, etc.
[0051] The user may also selectively superimpose the incident information, the status and/or the relatively static information over the recorded video data. This may aid in the presentation of the video in a court or other judicial body. For example, if the vehicle 16 is a commercial vehicle, the operating company may present a video of a traffic accident in court with the relevant incident information and/or status superimposed thereon. The video, along with the superimposed status and/or incident information may be visually appealing and persuasive to a fact finder that the driver 14 was not at fault for the accident. As another example, in corrective training generated for the driver 14, embodiments of the invention may utilize actual video data from the driver's history with superimposed information to demonstrate certain information to the driver 14. Still further embodiments of the invention may include a driving simulation in which the driver 14 is invited to recreate the event and attempt to improve their performance. For example, if a driver 14 struck an animal while driving, the driving simulation may use or base a simulation on the associated video data (along with the superimposed information) and allow the driver 14 to recreate the event through simulation such that the driver 14 can be better prepared to avoid striking animals in the future.
[0052] Some embodiments of the invention comprise a proximity tag system for authenticating the devices, cameras, and drivers 14 associated with the incident. The proximity tag system comprises a plurality of proximity tags 34 and at least one proximity tag reader 52. Proximity tags 34 are any devices that radiate an identifying signal, herein referred to as the proximity tag identifier, that can be read by a corresponding reader such as the proximity tag reader. Proximity tags 34 can be active (meaning that they periodically broadcast their identifier), assisted passive (meaning that they broadcast their identifier only when interrogated by a signal from the reader), or passive (meaning that they have no power source and are illuminated by a signal from the proximity tag reader in order to radiate their identifier). Other forms of proximity Lags are also possible. Proximity tag identifier may be preprogrammed into proximity tags 34, or may be field-programmable, such that the identifier is assigned by the user when the proximity tag 34 is deployed. One common form of proximity tag system is the radio-frequency identification (RFID) tag and the corresponding RFID reader. Another form of proximity tag system utilizes a challenge-response protocol to avoid the spoofing of a proximity tag identifier. An exemplary proximity tag system is described in U.S. patent application Ser. No. 14/517,368, filed Oct. 17, 2014, and entitled “FORENSIC VIDEO RECORDING WITH PRESENCE DETECTION,” which is incorporated by reference herein in its entirety.
[0053] In embodiments of the invention, the driver 14 uses a proximity tag 34 that contains a proximity tag indicator specific to that driver 14 to authenticate the name, fleet 12, and/or status of the specific driver using the recording device manager 28 and/or the vehicle-tracking device 18. The proximity tag 34 may be located within a proximity card held by the driver, within the badge worn by the driver, on a watch or a belt worn by the officer, within a key used by the driver to start the vehicle, etc. There may also be a proximity tag 34 in the vehicle-tracking device 18 and/or the video cameras 20. The proximity tag reader reduces work to be performed at a later time to associate the recorded video data and incident information with the specific driver.
[0054] The recording device manager 28, as illustrated in FIG. 2 , will now be briefly discussed. The recording device manager 28, such as a Digital Ally® VuLink®, controls and synchronizes various recording devices. For example, the recording device manager 28 links (via wireless communication, wired communication, or both) to the vehicle-tracking device 18, a person-mounted video camera 32 on the driver 14, another person-mounted video camera 32 on another operator or passenger of the vehicle 16, a vehicle-mounted video camera 26 in the vehicle 16 oriented to observe events external to the vehicle 16, a vehicle-mounted video camera 26 in the vehicle 16 oriented to observe events internal to the vehicle 16, and/or the auxiliary computing device (referred to generically or individually as “the various recording devices”). An exemplary recording device manager is described in U.S. Pat. No. 8,781,292, issued Jul. 15, 2014, and entitled “COMPUTER PROGRAM, METHOD, AND SYSTEM FOR MANAGING MULTIPLE DATA RECORDING DEVICES,” which is incorporated by reference herein in its entirety.
[0055] Typically, the recording device manager 28 detects when one video camera 20 begins recording, and then instructs all other associated devices to begin recording. The recording device manager 28 may also send information indicative of a time stamp to the various recording devices for corroborating the recorded data. In embodiments of the invention, the recording device manager 28 instructs all associated video cameras 20 to begin recording upon the receipt of a signal from the vehicle-tracking device 18 that an incident has been detected. This helps to ensure that the incident is captured as thoroughly as possible. For example, the vehicle 16 may have one forward-facing video camera that is continuously recording and multiple externally mounted video cameras facing in multiple directions that remain idle until an incident is detected. Upon the detection of an incident by the vehicle-tracking device 18, the recording device manager 28 instructs these secondary video cameras to begin recording, such that conditions around the vehicle 16 may be observed. The video cameras may also be continuously recording and dumping a set amount of time worth of video. The recording device manager 28 may instruct the video camera to store that amount of video data instead of dumping it.
[0056] Various methods of embodiments of the invention as performed by various engines will now be discussed. In some embodiments, a non-transitory computer readable storage medium having a computer program stored thereon may instruct at least one processing element to implement the steps of at least one of the described methods. The non-transitory computer readable storage medium may be located within a server device, the recording device manager 28, the vehicle-tracking device 18, and/or within a generic computing device.
[0057] FIG. 4 depicts exemplary steps performed by the monitoring engine. Typically, the monitoring engine is located at a location associated with the fleet 12, such as a dispatching station, a headquarters location, or the like (though in some embodiments it is located in another place, such as a location associated with the administrator of the system 10).
[0058] In Step 400, the monitoring engine detects the vehicle-tracking device 18. Step 400 may be performed during the powering on of the vehicle-tracking device 18 before the vehicle 16 leaves the vicinity. Upon detection, the monitoring engine may request additional information from the vehicle-tracking device 18 such as a current status and/or location. It should be appreciated that the monitoring engine may detect and track many vehicle-tracking devices 18 simultaneously (of the same or multiple fleets 12).
[0059] In Step 402, the monitoring engine receives location information for the vehicle-tracking device 18. In Step 404, the monitoring engine sends this information to the mapping engine so that the mapping engine can populate and/or move the icon 24 associated with the vehicle 16.
[0060] In Step 406, the monitoring engine receives incident information from the vehicle-tracking device 18. In some embodiments, the received incident information is minimal. For example, the information may include that there is an incident, a location of the incident, and a type of incident, but without excessive details. This minimizes the amount of data transferred while still alerting the monitoring engine (and by extension an operator or dispatcher observing the monitoring engine and/or the map 22) of the incident. The type of incident may be determined by the vehicle-tracking device 18, the driver computing device 30, the recording device manager 28, or other component. The type of incident is indicative of the nature of the incident and/or the severity of the incident. Examples of types of incidents include speeding, harsh braking, rapid acceleration, harsh cornering, failure to use a vehicular system (such as the brakes, blinker, wipers, etc.) vehicular collision, vehicular theft, vehicular breakdown, tampering with the vehicle-tracking device 18, operation of the vehicle by an unauthorized driver, operation of the vehicle outside work hours, operation of the vehicle outside a certain geographic area, the passing of a certain time interval, the passing of a certain geographic waypoint, etc. The type of incident may also include a severity level of the incident. For example, speeding in excess of twenty miles per hour over the posted speed limit may have a classification such as “imminently dangerous speeding” or “speeding level 3.” In some embodiments, the operator or dispatcher may request additional information from the vehicle-tracking device 18 if additional details are needed. In Step 408, this information is sent to the mapping engine for the creation or updating of the icon 24. In Step 410, the information is sent to the driver analysis engine for later analysis of the driver's performance.
[0061] FIG. 5 depicts exemplary steps by the mapping engine. Generally, the mapping engine receives the at least a portion of the information received by the monitoring engine and utilizes the information in populating the map 22 displayed to a user. In some embodiments, the user is a dispatcher or supervisor responsible for overseeing the fleet 12. In other embodiments, the user is an administrator that oversees the system 10 but has no direct oversight of the fleet 12. The map 22 may display on multiple displays, including to the driver 14, to all drivers of the fleet 12, to the supervisor, to the dispatcher, and/or to the administrator. The map 22 may be available on demand or continuously displayed.
[0062] In Step 500, the mapping engine generates a map 22 of the geographic area related to the incident or the area in which the vehicle 16 is traveling. The geographic area covered by the map 22 may also be dependent upon the geographic locations of the various vehicles 16 as reported (as discussed below). The geographic coverage area and/or dimensions may also change over time as the geographic area in which the vehicles 16 are located changes. For example, as a vehicle 16 moves off of the edge of the map 22, the map 22 may automatically adjust (e.g. zoom out or pan) such that all vehicles 16 remain visible on the map 22.
[0063] In Step 502, the mapping engine receives location information from the monitoring engine. The location information is indicative of the location in which the vehicle 16 is located. In Step 504, the mapping engine creates an icon 24 on the map 22 at a position associated with the position of the vehicle 16 (i.e. such that the icon 24 on the map 22 approximates the vehicle 16 on the ground). The icon 24 may have a corresponding color, shape, marking, or other indication that is indicative of the vehicle, vehicle type, and/or driver.
[0064] In Step 506, the mapping engine refines the location or other attributes of the icon 24 based upon updated information received by the mapping engine from the monitoring engine. For example, as the vehicle 16 moves through the area, the icon 24 is updated to depict an approximate current location. As another example, the icon 24 may begin presenting a first color, such as a green color. If the driver 14 experiences a first incident, the icon 24 may turn a second color, such as yellow, and if the driver 14 experiences a second incident the icon 24 may turn a third color, such as red. This allows the supervisor or dispatcher to quickly determine the quality of driving being exercised by the drivers 14 in the fleet 12 in real time.
[0065] In Step 508, the mapping engine receives incident information from the monitoring engine. In Step 510, the mapping engine creates an icon 24 at the geographic location associated with the incident. In some embodiments, the incident information includes location information. In other embodiments, the icon 24 is created at the current geographic location of the vehicle 16 associated with the incident. Typically, the icon 24 will remain static at the associated location, even after the vehicle 16 has moved to another location. This allows the dispatcher or supervisor to identify areas where incidents are common. The mapping engine may additionally or in the alternative generate a map 22 specific to the driver 14 that includes all incidents for a certain time period or specific geographic area.
[0066] In Step 512, the mapping engine receives video data from the video repository engine. In Step 514, the mapping engine associates the video data with the icon 24. The mapping engine may update or recreate the icon 24 to indicate that video data is available for this incident. For example, the icon 24 may display a small screen shot of the video on the icon 24 (either by default or on a mouse-over). The mapping may also present an option to the user to request additional video. For example, if the incident video data provided stops while the incident is still in progress, the user may request an additional amount of time of video (such as thirty seconds, one minute, two minutes, etc.). The mapping engine may then request the additional video data from the video repository engine, edit the incident video data to include the additional video data, and present the new video to the user.
[0067] The mapping may also display additional incident information to the user that was not immediately available when the icon 24 was created. For example, the vehicle-tracking device 18 may provide minimal incident information over the mobile broadband connection, such as driver involved, vehicle involved, type of incident, and location of incident. Later, upon return to the upload location, the mapping engine may receive more information about the incident, such as vehicle speed during the incident, accelerometer 40 readings during the incident, vehicle systems operating during the incident, and the like. This gives someone reviewing the incident with more information about the cause and fault involved in the incident. The user may also be presented with options to request additional incident information, such as conditions before or after the incident, weather conditions during the incident, the driver's shift hours for that day, etc.
[0068] In embodiments of the invention, Step 512 and Step 514 occur after the vehicle 16 has returned to the upload location. This is because transferring video over mobile broadband is typically slow and expensive. In other embodiments, the dispatcher or supervisor can initiate Step 512 and 514 while the vehicle 16 is still driving, as discussed below. For example, if the incident is a vehicular wreck, a shooting involving a law enforcement officer, or another emergency, the video data related to the incident may be vital in alleviating the situation. As a more specific example, if the driver 14 drives off of the roadway and down a ravine and cannot be located by rescue efforts, the dispatcher may select on the map 22 to have the recording device manager 28 or recording device upload the video associated with the incident remotely (because the slowness and expense of mobile broadband are less important in such a situation). As another specific example, if a law enforcement officer is shot and incapacitated by a suspect, the dispatch currently has no way to receive a video of the suspect to assist in his capture. Embodiments of the invention allow the dispatcher to receive the video, via a request made remotely through the mapping engine, and transmit the video (or a screenshot thereof) to the other officers in pursuit of the suspect. In performing these steps, the recording device manager 28 or recording device (which contains the video data) may utilize the communications element 46 of the vehicle-tracking device 18, an internal communications element, a smart phone associated with the driver 14 (via a Bluetooth connection), etc.
[0069] In embodiments of the invention, the video data includes orientation information. Orientation information may be derived from a compass element (not illustrated) in the video camera 20, a compass element in the vehicle 16, the direction of travel based on location data, etc. In Step 516, the mapping engine may provide an indication of the orientation of the video data. For example, the indication may be a cone shape in the orientation direction, a shaded area approximating the area covered by the video, etc. In some embodiments of the invention, in Step 518 the mapping engine analyzes the video data to determine a set of video data that covers an inquiry location at an inquiry time based upon the orientation data and a set of location information for the video data. In these embodiments, a user may be attempting to locate video regarding a certain inquiry location, such as the scene of a wreck or crime unrelated to the fleet. The user may enter an inquiry location and inquiry time into the mapping engine. The mapping engine may then analyze vehicles 16 of at least one fleet 12 near that inquiry location at that inquiry time and determine if any were oriented in a direction that may have potentially captured the inquiry time and location. The mapping engine may then present or request any potentially relevant video for review by the user.
[0070] As an example of this embodiment, a bank was robbed in the vicinity of a commercial shipping facility. As law enforcement officers are investigating the robbery, they ask the commercial shipping facility supervisor if any commercial shipping vehicles were coming into or out of the facility that may have potentially captured the bank robbers on video. The supervisor enters the location and time of the bank robbery into the mapping engine. The mapping engine analyzes the locations of the vehicles at that time in that vicinity and/or analyzes the location and orientation information associated with all available video data. The mapping engine then identifies one commercial shipping vehicle that had a video camera 20 oriented toward the bank at the inquiry time. The mapping engine then requests the relevant video from the video repository engine and presents the video to the supervisor. As another example, if a vehicle associated with the fleet becomes involved in a collision, the inquiry may determine whether there were any other vehicles in the vicinity that may have captured the collision on video. In some embodiments, the inquiry may search video data from other fleets to which the supervisor (or other user) may not have direct access. If a video is identified, the supervisor may request the video from a supervisor of that fleet.
[0071] FIG. 6 depicts exemplary steps of the video repository engine. The video repository engine generally receives and stores video data from the plurality of vehicles 16 in the fleet 12. The video data is then stored for a certain period of time for litigation and compliance reasons. Typically, the video repository engine is located at least in part at a facility associated with the fleet 12 or the system 10, known as the upload location. An exemplary video repository engine may operate in a hospital to download videos taken by ambulances after they return from retrieving a patient or at a law enforcement precinct to download videos taken by law enforcement vehicles after the vehicle is returned at the end of a shift. There may be more than one upload location associated with the fleet 12 and/or the system 10.
[0072] In Step 600, the video repository engine detects the video camera 20, the recording device manager 28, or the like. The connection may wireless (e.g. Wi-Fi technology, Bluetooth technology, or the like), wired (e.g. via a communications cable), or by the transfer of physical media (e.g. by the removal and manual transfer of a data store). Typically, the connection will be a wireless Wi-Fi connection. For example, as the vehicle returns to the vicinity of the upload location, the recording device manager 28, video camera 20, or recording device establishes a Wi-Fi connection with the video repository engine.
[0073] In Step 602, the video repository engine downloads video data from the recording device manager 28, video camera 20, or recording device. In embodiments of the invention, the video repository engine downloads all available video data that was created since the last download process. In other embodiments, the video repository engine may selectively download only certain portions of the video data. In Step 604, the video repository engine stores the video data in an associated data store.
[0074] In Step 606, the video repository engine extracts an incident video from the video data based upon the incident information. The incident information may be received from the monitoring engine, from the recording device manager 28, from the vehicle-tracking device 18, be embedded in the video data as metadata, or another source. For example, the video data may have associated metadata indicative of an incident during a certain time period of the video. The video repository engine may then extract that segment of video data, along with a certain period of time before and/or after the incident.
[0075] In Step 608, the video repository engine sends the incident video to the mapping engine such that the incident video may be associated with the icon 24. This allows the dispatcher, supervisor, driver 14, etc., to review the video in a convenient manner. The reviewer is not required to find the correct file and skip to the approximate location, as in other systems of the prior art. The user instead simply selects the icon 24 that has the incident video data already associated. Additionally, or in the alternative, the video repository engine may send the incident video to the driver analysis engine for review, analysis, and presentation to a person reviewing the driver's performance.
[0076] FIG. 7 depicts an exemplary graphical user interface of the map 22. As illustrated, the map depicts various streets and other geographical markers. The map also depicts a plurality of icons 24. Some of the icons 24 are vehicle icons 56. Vehicle icons 56 depict a location of the vehicle in substantially real time (as defined below). The vehicle icon 56 may have a certain identifier such as a color, a pattern, an alphanumeric, or other identifier so that the user may know to which the vehicle 16 the vehicle icon 56 relates. The user may select the vehicle icon 56 to receive information about the current status of the vehicle, the associated driver 14 (if any), the history of incidents, the hours worked, the miles traveled, the jobs completed, etc. The information about the vehicle may be displayed in a vehicle details window similar to an incident details window 58 (discussed below) illustrated in FIG. 7 .
[0077] As illustrated in FIG. 7 , some of the icons 24 are vehicle tracks 60. The vehicle tracks 60 depict the approximate pathways through which a vehicle 16 has traveled within a certain time frame (e.g. the current day). The vehicle tracks 60 provide an easy reference for users to be able to see at a glance where the vehicles have traveled. For example, a user would be able to quickly and easy see if a certain delivery has been performed based upon the presence or absence of the vehicle track 60 in the vicinity of the location associated with the delivery. In some embodiments, the vehicle track 60 begins as transparent and then upon each subsequent passing of a vehicle over the vehicle track 60 the transparency is reduced incrementally until the vehicle track 60 is opaque. It should also be noted that the vehicle track 60 is only an approximation of the traveled location of the vehicle because the location of the vehicle is typically determined periodically. The user may select the vehicle track 60 to receive information about which vehicle 16 or vehicles have traveled in the area, the time for each vehicle 16 traveling in the area, the point of origin and or destination associated with the vehicle 16 traveling in the area, the next vehicle scheduled to pass through the area (if known), a street and city name associated with the area, an approximate address for the area, a speed limit associated with the area (if known), etc. This information may be displayed on a route details window similar to the incident details window 58 in FIG. 7 .
[0078] As illustrated in FIG. 7 , some of the icons 24 are incident icons 62. The incident icons 62 depict the geographic location associated with the incident. The incident icon 62 may include an indication of the type and/or severity level of the incident. The incident icon 62 may also include an indication of whether the incident icon 62 has an associated video, whether a video is pending (e.g. the vehicle has not yet returned to the upload location to upload the video, but the video will be added to the icon at that time), whether the video has not been requested (and may include an option for the user to request the video), etc. As some incidents occur over time and distance (such as speeding and excessive acceleration), the incident icon 62 may be associated with a start position, an intermediate position, and/or an ending position for the incident. In other embodiments, the incident icon 62 may be displayed as a vehicle track 60, but be set off from other vehicle tracks 60 by a different color, pattern, or opacity.
[0079] The user may select the incident icon 62 to display more information about the incident. An exemplary incident details window 58 is illustrated in FIG. 7 . As shown, the exemplary incident details window 58 includes a type of incident, a date and time, a vehicle name, a vehicle driver name, the speed of the vehicle, the posted speed limit (either known from available map data or completed by the user), the heading at the time of the incident, a severity level for the acceleration, a severity level for the braking, a location, an altitude, a name for the location point, an indication of whether the incident video has been review, notes made by the reviewer (that may be entered directly on the incident details window 58 or from an incident review interface such as illustrated in FIG. 8 ), tags assigned (either by the system, the reviewer, or both). The exemplary incident details window 58 also presents options for the user to select. Among the exemplary options shown include an option to view the video details (which will bring up a screen such as the incident review interface of FIG. 8 ), an option to watch the video overlaid on the map, an option to view a street-view photograph from a third party resource (such as GOOGLE MAPS or the like), an option to view weather information associated with the incident (i.e. from the date, time, and location of the incident), and an option to view driver information (e.g. a driver profile).
[0080] FIG. 8 depicts an exemplary graphical user interface of an incident review interface. Typically, the reviewer and/or the driver will access the incident review interface in reviewing the incident. The incident review interface may be displayed upon selection of the incident icon 62, upon selection of the video details option on the incident details window 58, upon the video being uploaded and associated with the incident icon 62, etc. As illustrated the incident review interface includes video controls, an external camera video player, an internal camera video player, a map depicting the incident (including a start location, a vehicle track, and an end location), a summary of incident information, a graphical depiction of speed, and a section for notes to be entered or reviewed. The incident review interface may also include additional information such as that shown in FIG. 7 , detailed information the status of various sensors in the vehicle, a display of the metadata associated with the video, a display of the accelerometer and braking over time, a display of all available vehicle information, etc.
[0081] In embodiments of the invention, the external camera video player and the internal video camera video player are populated with video data from their respective video cameras automatically. The video repository engine (as discussed above in Step 606) extracts the video data that corresponds with the incident information. The extracted video data is then displayed for review in the incident review interface (and/or on the map). Reviewing the video data along with the incident information provides a better understanding to the reviewer of the conditions and the actions taken by the driver. The video data may provide the reviewer with information as to what caused the incident and allow the reviewer to formulate a plan of action to reduce the severity of or eliminate similar incidents in the future.
[0082] FIG. 9 depicts exemplary steps of the driver analysis engine. In Step 900, the driver analysis engine acquires information regarding the drivers 14 associated with the subject fleet 54 (i.e. the fleet 12 in which the driver 14 is associated). The information regarding the drivers 14 associated with the subject fleet 54 can include any of the above-discussed information or the like (e.g. hours worked, miles traveled, incidents recorded, etc.). The driver analysis engine stores this information in a driver characteristics data store 64.
[0083] In Step 902, the driver analysis engine acquires information related to additional peer fleets 66 (discussed below) beyond the subject fleet 54. In some embodiments, the driver analysis engine stores the information related to all of the fleets 12 in the driver characteristics data store 64. In other embodiments, the driver analysis engine accesses external driver characteristics data stores 64 without transferring data. The information transferred in Step 902 may be redacted, summarized, and/or analyzed (so as to avoid breaches of confidentiality between unaffiliated fleets while still providing analytical benefits).
[0084] In Step 904, the driver analysis engine analyzes a subject driver 68 based upon the information received or otherwise acquired. The driver analysis engine receives and analyzes the information that relates to the subject driver 68 and in comparison to other drivers as discussed below. The driver analysis engine organizes and analyzes the data to provide meaningful metrics to the supervisor. The metrics can include incidents per mile, incident severity average, incident cause average, idle time, work time, travel time, analytics of the various metrics, etc.
[0085] A simple exemplary depiction of the results of this analysis is illustrated in FIG. 10 . FIG. 10 depicts a chart showing the recorded information relevant to the subject driver 68 over the past few months. A top chart 70 on FIG. 10 depicts the recorded incidents related to the driver per mile traveled. The top chart 70 also depicts the fleet average value for the same time periods. A bottom chart 72 on FIG. 10 depicts a few exemplary types of incidents as recorded for the subject driver 68 over the same time period. The exemplary types of incidents depicted in FIG. 10 include excessive acceleration, excessive braking, and speeding over the posted speed limit. In other embodiments, the interval on the figures may be weekly, daily, etc.
[0086] Returning to FIG. 9 , in some embodiments of the invention the driver analysis engine performs a more detailed analysis to determine trends in the incidents of the subject driver 68. For example, the driver analysis engine may determine that the majority of incidents occur in the last hour of the driver's shift (based upon an analysis of the driver's shift times and the incident time), during bad weather (based upon an analysis of available weather data), after nightfall (based upon an analysis of daylight hours), when the subject driver 68 is not carrying a load (based upon route information), after a switch to a new type of vehicle, etc. This analysis is performed substantially independently of a comparison to other drivers 14 and peer fleets 66. However, the significance of this analysis may be even more relevant when compared to similar analyses of other drivers 14 and fleets 12 as discussed below.
[0087] In Step 906 the driver analysis engine compares the subject driver 68 to peer drivers 74 in the subject fleet 54. The peer drivers 74 are typically operating in the same types of vehicles, in the same geographic areas, and in the same conditions as the subject driver 68. Comparing the subject driver 68 to the peer drivers 74 therefore provides a more useful analysis than considering the subject driver's performance in isolation.
[0088] One exemplary depiction of the result of this analysis is shown in the top chart 70 of FIG. 10 . The “fleet average” chart value is a form of comparison between the subject driver 68 and the peer drivers 74. Other comparisons may be more detailed (including all or a plurality of the peer drivers 74). Another exemplary depiction of the result of this analysis is shown in FIG. 9 . FIG. 9 depicts drivers 14 within the subject fleet 54 along with totals and average values for the various types of incidents detected by the vehicle-tracking device 18. An analysis can be found in the “Risk Grade” value that approximates an amount of risk that the subject driver 68 takes during the operation of the vehicle.
[0089] Returning again to FIG. 9 , in Step 908 the driver analysis engine compares the subject driver 68 to an average value across a plurality of fleets 12. For example, the driver analysis engine may rank the subject driver 68 against all peer drivers 74 in all fleets 12. This gives information to the actual effectiveness of the subject driver 68. If the subject fleet 54 to which the subject driver 68 is associated is above or below average, this metric provides a more standardized and stable benchmark.
[0090] In Step 910, the driver analysis engine may compare the subject driver 68 to peer drivers 74 in other peer fleets 66. For example, an ambulance driver may be compared to all ambulance drivers in all peer fleets 66. Some fleets 12 comprise different types of vehicles within the fleet 12. Accordingly, it may not be an accurate comparison to compare the subject driver 68 against all drivers 14 in the fleet 12 because certain drivers 14 in the fleet 12 drive different vehicles 16 under different conditions than the subject driver 68. However, only comparing the subject driver 68 against similar drivers in the same fleet 12 reduces the comparison pool. Therefore, in embodiments of the invention, the driver analysis engine compares the subject driver 68 to comparable drivers 14 in both the subject fleet 54 and in peer fleets 66. For example, a squadron of military aircraft may have a single refueling aircraft along with multiple fighter aircraft. It would be of little value to compare the subject driver 68 (i.e. the pilot) of the refueling aircraft against the fighter aircraft pilots. A more valuable comparison would be to compare the pilot of the refueling aircraft against the pilots of other refueling aircraft in other squadrons. Similarly, in the law enforcement field, comparing the driving habits of a detective against patrol officers would not be as advantageous as comparing the detective to other detectives in the same precinct and in other precincts.
[0091] In Step 912, the driver analysis engine compares the subject driver 68 against all peer drivers 74 in the same geographic area. For example, if the subject driver 68 primarily drives on a certain route, the driver analysis engine may compare the subject driver 68 against all other drivers 14 (regardless of fleet) on that certain route. For example, if many drivers 14 register an incident rounding a certain turn on the route, the subject driver 68 may be less-severely penalized for incidents along the route because registering of the incident may be anomalous.
[0092] In Step 914, the driver analysis engine produces a driver score, a driver report, or other grade. The driver score may be detailed, in that it includes a sub-score for many different areas. The driver score may also be a single value that is calculated based upon the sub-scores. In some embodiments, the driver analysis engine may weight various sub-scores based upon their importance, their departure from the averages, etc. For example, if the subject driver 68 performs well in all areas except having numerous excessive accelerations, the driver analysis engine may weight the excessive accelerations as more important when calculating the driver score.
[0093] In Step 916, the driver analysis engine determines, recommends, and/or creates driver training to address identified deficiencies. The driver training can be in numerous forms including multi-media, education, driving simulation, and the like.
[0094] In some embodiments, the driver analysis engine may compare an entire fleet 12 of drivers 14 against another entire peer fleet 66. As depicted in FIG. 11 , the fleet analysis provides the supervisor or dispatcher with information as to the overall performance of the subject fleet 54 and may additionally recommend driver training for the collective drivers of the subject fleet 54.
[0095] The computer program of embodiments of the invention will now be discussed. The computer program comprises a plurality of code segments executable by a computing device for performing the steps of various methods of the invention. The steps of the method may be performed in the order discussed, or they may be performed in a different order, unless otherwise expressly stated. Furthermore, some steps may be performed concurrently as opposed to sequentially. Also, some steps may be optional. The computer program may also execute additional steps not described herein. The computer program, system, and method of embodiments of the invention may be implemented in hardware, software, firmware, or combinations thereof, which broadly comprises server devices, computing devices, and a communications network.
[0096] The computer program of embodiments of the invention may be responsive to user input. As defined herein user input may be received from a variety of computing devices including but not limited to the following: desktops, laptops, calculators, telephones, smartphones, smart watches, in-car computers, camera systems, or tablets. The computing devices may receive user input from a variety of sources including but not limited to the following: keyboards, keypads, mice, trackpads, trackballs, pen-input devices, printers, scanners, facsimile, touchscreens, network transmissions, verbal/vocal commands, gestures, button presses or the like.
[0097] The server devices and computing devices may include any device, component, or equipment with a processing element and associated memory elements. The processing element may implement operating systems, and may be capable of executing the computer program, which is also generally known as instructions, commands, software code, executables, applications (“apps”), and the like. The processing element may include processors, microprocessors, microcontrollers, field programmable gate arrays, and the like, or combinations thereof. The memory elements may be capable of storing or retaining the computer program and may also store data, typically binary data, including text, databases, graphics, audio, video, combinations thereof, and the like. The memory elements may also be known as a “computer-readable storage medium” and may include random access memory (RAM), read only memory (ROM), flash drive memory, floppy disks, hard disk drives, optical storage media such as compact discs (CDs or CDROMs), digital video disc (DVD), and the like, or combinations thereof. In addition to these memory elements, the server devices may further include file stores comprising a plurality of hard disk drives, network attached storage, or a separate storage network.
[0098] The computing devices may specifically include mobile communication devices (including wireless devices), work stations, desktop computers, laptop computers, palmtop computers, tablet computers, portable digital assistants (PDA), smart phones, and the like, or combinations thereof. Various embodiments of the computing device may also include voice communication devices, such as cell phones and/or smart phones. In preferred embodiments, the computing device will have an electronic display operable to display visual graphics, images, text, etc. In certain embodiments, the computer program facilitates interaction and communication through a graphical user interface (GUI) that is displayed via the electronic display. The GUI enables the user to interact with the electronic display by touching or pointing at display areas to provide information to the system 10.
[0099] The communications network may be wired or wireless and may include servers, routers, switches, wireless receivers and transmitters, and the like, as well as electrically conductive cables or optical cables. The communications network may also include local, metro, or wide area networks, as well as the Internet, or other cloud networks. Furthermore, the communications network may include cellular or mobile phone networks, as well as landline phone networks, public switched telephone networks, fiber optic networks, or the like.
[0100] The computer program may run on computing devices or, alternatively, may run on one or more server devices. In certain embodiments of the invention, the computer program may be embodied in a stand-alone computer program (i.e., an “app”) downloaded on a user's computing device or in a web-accessible program that is accessible by the user's computing device via the communications network. As used herein, the stand-along computer program or web-accessible program provides users with access to an electronic resource from which the users can interact with various embodiments of the invention.
[0101] In embodiments of the invention, users may be provided with different types of accounts. Each type of user account may provide their respective users with unique roles, capabilities, and permissions with respect to implementing embodiments of the invention. For instance, the driver may be provided with a driver account that permits the driver to access embodiments of the invention that are applicable to log work hours, review incidents, access driver training, etc. Additionally, the dispatcher or supervisor may be provided with a supervisory account that permits the dispatcher or supervisor to access embodiments of the invention that are applicable to monitoring the activities of the fleet, reviewing incidents, requesting video data, etc. In addition, any number and/or any specific types of account are provided to carry out the functions, features, and/or implementations of the invention. Upon the user logging in to the electronic resource for a first time, they may be required to provide various pieces of identification information to create their respective accounts. Such identification information may include, for instance, personal name, business name, email address, phone number, or the like. Upon providing the user may be required to enter (or may be given) a username and password, which will be required to access the electronic resource.
[0102] Execution of the computer program of embodiments of the invention performs steps of the method of embodiments of the invention. Because multiple users may be updating information stored, displayed, and acted upon by the computer program, information displayed by the computer program is displayed in real-time. “Real-time” as defined herein is when the processing element of the system 10 performs the steps less than every 1 second, every 500 milliseconds, every 100 milliseconds, or every 16 milliseconds.
[0103] Turning to FIG. 13 , an exemplary hardware platform 1300 that can serve as, for example, the control circuitry or other elements of certain embodiments of the invention is depicted. Computer 1302 can be a desktop computer, a laptop computer, a server computer, a mobile device such as a smartphone or tablet, or any other form factor of general- or special-purpose computing device. Depicted with computer 1302 are several components, for illustrative purposes. In some embodiments, certain components may be arranged differently or absent. Additional components may also be present. Included in computer 1302 is system bus 1304, whereby other components of computer 1302 can communicate with each other. In certain embodiments, there may be multiple busses or components may communicate with each other directly. Connected to system bus 1304 is central processing unit (CPU) 1306. Also attached to system bus 1304 are one or more random-access memory (RAM) modules.
[0104] Also attached to system bus 1304 is graphics card 1310. In some embodiments, graphics card 1304 may not be a physically separate card, but rather may be integrated into the motherboard or the CPU 1306. In some embodiments, graphics card 1310 has a separate graphics-processing unit (GPU) 1312, which can be used for graphics processing or for general purpose computing (GPGPU). In some embodiments, GPU 1312 may be used for encoding, decoding, transcoding, or compositing video. Also on graphics card 1310 is GPU memory 1314. Connected (directly or indirectly) to graphics card 1310 is display 1316 for user interaction. In some embodiments no display is present, while in others it is integrated into computer 1302. Similarly, peripherals such as keyboard 1318 and mouse 1320 are connected to system bus 1304. Like display 1316, these peripherals may be integrated into computer 1302 or absent. Also connected to system bus 1304 is local storage 1322, which may be any form of computer-readable media, and may be internally installed in computer 1302 or externally and removeably attached.
[0105] Finally, network interface card (NIC) 1324 is also attached to system bus 1304 and allows computer 1302 to communicate over a network such as network 1326. NIC 1324 can be any form of network interface known in the art, such as Ethernet, ATM, fiber, or Wi-Fi (i.e., the IEEE 802.11 family of standards). NIC 1324 connects computer 1302 to local network 1326, which may also include one or more other computers, such as computer 1328, and network storage, such as data store 1330. Local network 1326 is in turn connected to Internet 1332, which connects many networks such as local network 1326, remote network 1334 or directly attached computers such as computer 1336. In some embodiments, computer 1302 can itself be directly connected to Internet 1332.
[0106] Although the invention has been described with reference to the embodiments illustrated in the attached drawing figures, it is noted that equivalents may be employed and substitutions made herein without departing from the scope of the invention as recited in the claims.
Claims
Having thus described various embodiments of the invention, what is claimed as new and desired to be protectected by letters Patent includes the following:
1. A system for tracking a fleet of vehicles, the system comprising:
a receiver configured for receiving information from a vehicle-tracking device associated with a vehicle of the fleet,
wherein the fleet of vehicles comprises a plurality of types of vehicles,
wherein at least a portion of said information is incident information that is associated with an incident detected by the vehicle-tracking device;
a display configured for displaying, to a user, an icon indicative of the incident on a map,
wherein the icon is located on the map in a location corresponding to an incident location,
wherein the receiver is further configured for receiving video data from a video camera associated with the vehicle; and
a processor configured to perform the following steps:
storing in a data store an incident video based upon at least a portion of said video data,
associating the incident video with said icon displayed on the map such that the user may select and view the incident video,
obtaining the incident information associated with a plurality of drivers,
analyzing the incident information associated with the plurality of drivers to generate a profile for the plurality of drivers,
wherein the profile for plurality of drivers is generated based at least in part on a type of vehicle for the plurality of drivers matching a type of vehicle of the driver;
analyzing the incident information associated with the driver to generate a driver profile,
recommending a driver specific training program to the driver based on the profile for the plurality of drivers and the driver profile.
2. The system of claim 1, wherein the receiver receives the information associated with the incident substantially in real time.
3. The system of claim 1, wherein the incident information associated with the incident includes geographic information related to the incident, actions taken by a driver of the vehicle, vehicle status associated with the incident, and the durational time of the incident.
4. The system of claim 1,
wherein the receiver receives the video data from the video camera upon the vehicle arriving at an upload location,
wherein the upload location is different than the incident location.
5. The system of claim 4, wherein a recording device manager in the vehicle instructs the video camera to associate the incident information with the recorded video data prior to the vehicle arriving at the upload location.
6. The system of claim 1,
wherein the video data has associated orientation data,
wherein the mapping engine displays an orientation indication of the orientation data on the map.
7. The system of claim 6, wherein the processor analyzes the video data to determine a set of video data that covers an inquiry location at an inquiry time based upon the orientation data and a set of location information for the video data.
8. The system of claim 7, wherein the inquiry location is different than the incident location, such that the processor identifies video data that covers the inquiry location independently of whether said set of video data is associated with an incident.
9. A system for analyzing a driver associated with a fleet of vehicles, the system comprising:
a processor;
a receiver;
a display;
a non-transitory computer readable medium storing computer-executable instructions which, when executed by the processor, perform the steps of:
receiving information from a vehicle-tracking device associated with a vehicle of the fleet that is associated with the driver,
wherein the fleet of vehicles comprises a plurality of types of vehicles,
wherein at least a portion of said information is an incident information associated with an incident detected by the vehicle-tracking device;
determining a plurality of drivers including the driver, wherein each driver of the plurality of drivers has a shared type of vehicle
obtaining incident information associated with the plurality of drivers,
wherein the shared type of vehicles is a subset of the fleet of vehicles;
analyzing the incident information associated with the plurality of drivers to generate a profile for the plurality of drivers,
analyzing the incident information associated with the driver to generate a driver profile,
comparing the incident information associated with the driver with corresponding incident information for the plurality of drivers,
calculating a first sub-score based on the driver profile,
calculating a second sub-score based on the driver profile,
determining a score for the driver based on weighted values of the first sub-score and the second sub-score,
wherein the score is indicative of an amount of risk the driver takes while driving.
10. The system of claim 9, wherein the plurality of drivers includes substantially all drivers associated with the fleet of vehicles.
11. The system of claim 1, wherein a recommended driver training program is based at least in part on one of the sub-scores.
12. The system of claim 9,
wherein the plurality of drivers includes substantially all drivers associated with a vehicle of the shared type, in the fleet
wherein the incident information associated with the driver is further compared to incident information drivers of the subset of the fleet of vehicles.
13. The system of claim 9, wherein the processor identifies at least one characteristic of the driver.
14. The system of claim 13, wherein the identified characteristic of the driver is based upon the comparison of the driver profile for the driver with the corresponding driver profiles for the plurality of drivers.
15. The system of claim 13, wherein the processor recommends a set of training for the driver based at least in part on the identified characteristic of the driver.
16. A system for tracking a fleet of vehicles and analyzing a driver associated with the fleet of vehicles, the system comprising:
a receiver for receiving information from a vehicle-tracking device associated with a vehicle of the fleet,
wherein the fleet of vehicles comprises a plurality of types of vehicles,
wherein at least a portion of said information is incident information that is associated with an incident detected by the vehicle-tracking device;
a display for displaying, to a user, an icon indicative of the incident on a map,
wherein the icon is located on the map in a location corresponding to an incident location;
the receiver further configured for receiving video data from a video camera associated with the vehicle,
storing in a data store an incident video based upon at least a portion of said video data,
wherein a processor for associating the incident video with said icon displayed on the map such that the user may select and view the incident video;
said receiver configured for obtaining the incident information associated with a plurality of drivers including substantially all peer drivers associated with a vehicle of the same type as the vehicle that is associated with the driver,
wherein each vehicles of the peer drivers belongs to the fleet of vehicles,
wherein the driver is one of said plurality of peer drivers,
the processor configured for analyzing the incident information associated with the plurality of drivers to generating a profile for the peer drivers,
said processor configured for analyzing the incident information associated with the driver to generate a driver profile,
said processor configured for comparing the driver profile for the driver with corresponding driver profiles for the peer drivers,
determining a comparative driver score for the driver based at least in part on a comparison of the profile for the peer divers and the driver profile.
17. The system of claim 16,
wherein the plurality of drivers is further chosen from the group including substantially all drivers associated with the fleet of vehicles, and substantially all drivers operating in a geographic location.
18. The system of claim 16, wherein the processor identifies at least one characteristic of the driver based upon the comparison of the driver profile for the driver with the corresponding driver profiles for the plurality of drivers.
19. The system of claim 16, wherein the driver profile includes set of video data associated with the incident.
20. The system of claim 16, wherein a driver training program is recommended based at least in part on a comparative driver score.
Patent Citations (418)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4409670(A) | 1983-10-01 | Herndon et al. | Applicant |
| US4789904(A) | 1988-12-01 | Peterson | Applicant |
| US4863130(A) | 1989-09-01 | Marks, Jr. | Applicant |
| US4918473(A) | 1990-04-01 | Blackshear | Applicant |
| US5027104(A) | 1991-06-01 | Reid | Applicant |
| US5096287(A) | 1992-03-01 | Kaikinami et al. | Applicant |
| US5111289(A) | 1992-05-01 | Lucas et al. | Applicant |
| US5289321(A) | 1994-02-01 | Secor | Applicant |
| US5381155(A) | 1995-01-01 | Gerber | Applicant |
| US5408330(A) | 1995-04-01 | Squicciarii et al. | Applicant |
| US5446659(A) | 1995-08-01 | Yamawaki | Applicant |
| US5453939(A) | 1995-09-01 | Hoffman et al. | Applicant |
| US5473729(A) | 1995-12-01 | Bryant et al. | Applicant |
| US5479149(A) | 1995-12-01 | Pike | Applicant |
| US5497419(A) | 1996-03-01 | Hill | Applicant |
| US5526133(A) | 1996-06-01 | Paff | Applicant |
| US5585798(A) | 1996-12-01 | Yosioka et al. | Applicant |
| US5642285(A) | 1997-06-01 | Woo et al. | Applicant |
| US5668675(A) | 1997-09-01 | Fredricks | Applicant |
| US5689442(A) | 1997-11-01 | Swanson et al. | Applicant |
| US5742336(A) | 1998-04-01 | Lee | Applicant |
| US5752632(A) | 1998-05-01 | Sanderson et al. | Applicant |
| US5798458(A) | 1998-08-01 | Monroe | Applicant |
| US5815093(A) | 1998-09-01 | Kikinis | Applicant |
| US5850613(A) | 1998-12-01 | Bullecks | Applicant |
| US5878283(A) | 1999-03-01 | House et al. | Applicant |
| US5886739(A) | 1999-03-01 | Winningstad | Applicant |
| US5890079(A) | 1999-03-01 | Levine | Applicant |
| US5926210(A) | 1999-07-01 | Hackett et al. | Applicant |
| US5978017(A) | 1999-11-01 | Tino | Applicant |
| US5983161(A) | 1999-11-01 | Lemelson et al. | Applicant |
| US5996023(A) | 1999-11-01 | Winter et al. | Applicant |
| US6008841(A) | 1999-12-01 | Charlson | Applicant |
| US6028528(A) | 2000-02-01 | Lorenzetti et al. | Applicant |
| US6052068(A) | 2000-04-01 | Price R-W et al. | Applicant |
| US6097429(A) | 2000-08-01 | Seeley et al. | Applicant |
| US6100806(A) | 2000-08-01 | Gaukel | Applicant |
| US6121881(A) | 2000-09-01 | Bieback et al. | Applicant |
| US6141609(A) | 2000-10-01 | Herdeg et al. | Applicant |
| US6141611(A) | 2000-10-01 | Mackey et al. | Applicant |
| US6163338(A) | 2000-12-01 | Johnson et al. | Applicant |
| US6175300(B1) | 2001-01-01 | Kendrick | Applicant |
| US6298290(B1) | 2001-10-01 | Abe et al. | Applicant |
| US6310541(B1) | 2001-10-01 | Atkins | Applicant |
| US6314364(B1) | 2001-11-01 | Nakamura | Applicant |
| US6324053(B1) | 2001-11-01 | Kamijo | Applicant |
| US6326900(B2) | 2001-12-01 | Deline et al. | Applicant |
| US6333694(B2) | 2001-12-01 | Pierce et al. | Applicant |
| US6333759(B1) | 2001-12-01 | Mazzilli | Applicant |
| US6370475(B1) | 2002-04-01 | Breed et al. | Applicant |
| USRE37709(E) | 2002-05-01 | Dukek | Applicant |
| US6389340(B1) | 2002-05-01 | Rayner | Applicant |
| US6396403(B1) | 2002-05-01 | Haner | Applicant |
| US6405112(B1) | 2002-06-01 | Rayner | Applicant |
| US6449540(B1) | 2002-09-01 | Rayner | Applicant |
| US6452572(B1) | 2002-09-01 | Fan et al. | Applicant |
| US6490409(B1) | 2002-12-01 | Walker | Applicant |
| US6518881(B2) | 2003-02-01 | Monroe | Applicant |
| US6525672(B2) | 2003-02-01 | Chainer et al. | Applicant |
| US6546119(B2) | 2003-04-01 | Ciolli et al. | Applicant |
| US6560463(B1) | 2003-05-01 | Santhoff | Applicant |
| US6563532(B1) | 2003-05-01 | Strub et al. | Applicant |
| US6591242(B1) | 2003-07-01 | Karp et al. | Applicant |
| US6681195(B1) | 2004-01-01 | Poland et al. | Applicant |
| US6690268(B2) | 2004-02-01 | Schofield et al. | Applicant |
| US6697103(B1) | 2004-02-01 | Fernandez et al. | Applicant |
| US6718239(B2) | 2004-04-01 | Rayer | Applicant |
| US6727816(B1) | 2004-04-01 | Helgeson | Applicant |
| US6748792(B1) | 2004-06-01 | Freund et al. | Applicant |
| US6823621(B2) | 2004-11-01 | Gotfried | Applicant |
| US6831556(B1) | 2004-12-01 | Boykin | Applicant |
| US6856873(B2) | 2005-02-01 | Breed et al. | Applicant |
| US6883694(B2) | 2005-04-01 | Abelow | Applicant |
| US6950122(B1) | 2005-09-01 | Mirabile | Applicant |
| US6970183(B1) | 2005-11-01 | Monroe | Applicant |
| US7012632(B2) | 2006-03-01 | Freeman et al. | Applicant |
| US7034683(B2) | 2006-04-01 | Ghazarian | Applicant |
| USD520738(S) | 2006-05-01 | Tarantino | Applicant |
| US7038590(B2) | 2006-05-01 | Hoffman et al. | Applicant |
| US7088387(B1) | 2006-08-01 | Freeman et al. | Applicant |
| US7119832(B2) | 2006-10-01 | Blanco et al. | Applicant |
| US7126472(B2) | 2006-10-01 | Kraus et al. | Applicant |
| US7147155(B2) | 2006-12-01 | Weekes | Applicant |
| US7180407(B1) | 2007-02-01 | Guo et al. | Applicant |
| US7190822(B2) | 2007-03-01 | Gammenthaler | Applicant |
| US7363742(B2) | 2008-04-01 | Nerheim | Applicant |
| US7371021(B2) | 2008-05-01 | Ross et al. | Applicant |
| US7421024(B2) | 2008-09-01 | Castillo | Applicant |
| US7436143(B2) | 2008-10-01 | Lakshmanan et al. | Applicant |
| US7436955(B2) | 2008-10-01 | Yan et al. | Applicant |
| US7448996(B2) | 2008-11-01 | Khanuja et al. | Applicant |
| US7456875(B2) | 2008-11-01 | Kashiwa | Applicant |
| US7496140(B2) | 2009-02-01 | Winningstad et al. | Applicant |
| US7500794(B1) | 2009-03-01 | Clark | Applicant |
| US7508941(B1) | 2009-03-01 | O'Toole, Jr. et al. | Applicant |
| US7511737(B2) | 2009-03-01 | Singh | Applicant |
| US7536457(B2) | 2009-05-01 | Miller | Applicant |
| US7539533(B2) | 2009-05-01 | Tran | Applicant |
| US7561037(B1) | 2009-07-01 | Monroe | Applicant |
| US7594305(B2) | 2009-09-01 | Moore | Applicant |
| US7602301(B1) | 2009-10-01 | Stirling et al. | Applicant |
| US7656439(B1) | 2010-02-01 | Manico et al. | Applicant |
| US7659827(B2) | 2010-02-01 | Gunderson et al. | Applicant |
| US7680947(B2) | 2010-03-01 | Nicholl et al. | Applicant |
| US7697035(B1) | 2010-04-01 | Suber, III et al. | Applicant |
| US7804426(B2) | 2010-09-01 | Etcheson | Applicant |
| US7806525(B2) | 2010-10-01 | Howell et al. | Applicant |
| US7853944(B2) | 2010-12-01 | Choe | Applicant |
| US7944676(B2) | 2011-05-01 | Smith et al. | Applicant |
| US8077029(B1) | 2011-12-01 | Daniel et al. | Applicant |
| US8121306(B2) | 2012-02-01 | Cilia et al. | Applicant |
| US8175314(B1) | 2012-05-01 | Webster | Applicant |
| US8269617(B2) | 2012-09-01 | Cook et al. | Applicant |
| US8314708(B2) | 2012-11-01 | Gunderson et al. | Applicant |
| US8350907(B1) | 2013-01-01 | Blanco et al. | Applicant |
| US8356438(B2) | 2013-01-01 | Brundula et al. | Applicant |
| US8373567(B2) | 2013-02-01 | Denson | Applicant |
| US8373797(B2) | 2013-02-01 | Ishii et al. | Applicant |
| US8384539(B2) | 2013-02-01 | Denny et al. | Applicant |
| US8446469(B2) | 2013-05-01 | Blanco et al. | Applicant |
| US8456293(B1) | 2013-06-01 | Trundle et al. | Applicant |
| US8508353(B2) | 2013-08-01 | Cook et al. | Applicant |
| US8594485(B2) | 2013-11-01 | Brundula | Applicant |
| US8606492(B1) | 2013-12-01 | Botnen | Applicant |
| US8676428(B2) | 2014-03-01 | Richardson et al. | Applicant |
| US8690365(B1) | 2014-04-01 | Williams | Applicant |
| US8707758(B2) | 2014-04-01 | Keays | Applicant |
| US8725462(B2) | 2014-05-01 | Jain et al. | Applicant |
| US8744642(B2) | 2014-06-01 | Nemat-Nasser et al. | Applicant |
| US8780205(B2) | 2014-07-01 | Boutell et al. | Applicant |
| US8781292(B1) | 2014-07-01 | Ross et al. | Applicant |
| US8805431(B2) | 2014-08-01 | Vasavada et al. | Applicant |
| US8849501(B2) | 2014-09-01 | Cook et al. | Applicant |
| US8854199(B2) | 2014-10-01 | Cook et al. | Applicant |
| US8887208(B1) | 2014-11-01 | Merrit et al. | Applicant |
| US8930072(B1) | 2015-01-01 | Lambert et al. | Applicant |
| US8989914(B1) | 2015-03-01 | Nemat-Nasser et al. | Applicant |
| US8996234(B1) | 2015-03-01 | Tamari et al. | Applicant |
| US9003474(B1) | 2015-04-01 | Smith | Applicant |
| US9058499(B1) | 2015-06-01 | Smith | Applicant |
| US9122082(B2) | 2015-09-01 | Abreau | Applicant |
| US9164543(B2) | 2015-10-01 | Minn et al. | Applicant |
| US9253452(B2) | 2016-02-01 | Ross et al. | Applicant |
| US9591255(B2) | 2017-03-01 | Sakiewica et al. | Applicant |
| US2002/0013517(A1) | 2002-01-01 | West et al. | Applicant |
| US2002/0019696(A1) | 2002-02-01 | Kruse | Applicant |
| US2002/0032510(A1) | 2002-03-01 | Turnbull et al. | Applicant |
| US2002/0044065(A1) | 2002-04-01 | Quist et al. | Applicant |
| US2002/0049881(A1) | 2002-04-01 | Sugimura | Applicant |
| US2002/0084130(A1) | 2002-07-01 | Der Gazarian et al. | Applicant |
| US2002/0131768(A1) | 2002-09-01 | Gammenthaler | Applicant |
| US2002/0135336(A1) | 2002-09-01 | Zhou et al. | Applicant |
| US2002/0159434(A1) | 2002-10-01 | Gosior et al. | Applicant |
| US2002/0191952(A1) | 2002-12-01 | Fiore et al. | Applicant |
| US2003/0040917(A1) | 2003-02-01 | Fiedler | Applicant |
| US2003/0080713(A1) | 2003-05-01 | Kirmuss | Applicant |
| US2003/0080878(A1) | 2003-05-01 | Kirmuss | Applicant |
| US2003/0081121(A1) | 2003-05-01 | Kirmuss | Applicant |
| US2003/0081934(A1) | 2003-05-01 | Kirmuss | Applicant |
| US2003/0081935(A1) | 2003-05-01 | Kirmuss | Applicant |
| US2003/0081942(A1) | 2003-05-01 | Melnyk et al. | Applicant |
| US2003/0095688(A1) | 2003-05-01 | Kirmuss | Applicant |
| US2003/0106917(A1) | 2003-06-01 | Shelter et al. | Applicant |
| US2003/0133018(A1) | 2003-07-01 | Ziemkowski | Applicant |
| US2003/0151510(A1) | 2003-08-01 | Quintana et al. | Applicant |
| US2003/0184674(A1) | 2003-10-01 | Manico et al. | Applicant |
| US2003/0185417(A1) | 2003-10-01 | Alattar et al. | Applicant |
| US2003/0215010(A1) | 2003-11-01 | Kashiwa | Applicant |
| US2003/0215114(A1) | 2003-11-01 | Kyle | Applicant |
| US2003/0222982(A1) | 2003-12-01 | Hamdan et al. | Applicant |
| US2004/0008255(A1) | 2004-01-01 | Lewellen | Applicant |
| US2004/0043765(A1) | 2004-03-01 | Tolhurst | Applicant |
| US2004/0143373(A1) | 2004-06-01 | Ennis | Applicant |
| US2004/0145457(A1) | 2004-07-01 | Schofield et al. | Applicant |
| US2004/0150717(A1) | 2004-08-01 | Page et al. | Applicant |
| US2004/0168002(A1) | 2004-08-01 | Accarie et al. | Applicant |
| US2004/0199785(A1) | 2004-10-01 | Pederson | Applicant |
| US2004/0223054(A1) | 2004-11-01 | Rotholtz | Applicant |
| US2004/0243734(A1) | 2004-12-01 | Kitagawa et al. | Applicant |
| US2004/0267419(A1) | 2004-12-01 | Jing | Applicant |
| US2005/0030151(A1) | 2005-02-01 | Singh | Applicant |
| US2005/0046583(A1) | 2005-03-01 | Richards | Applicant |
| US2005/0050266(A1) | 2005-03-01 | Haas et al. | Applicant |
| US2005/0068169(A1) | 2005-03-01 | Copley et al. | Applicant |
| US2005/0083404(A1) | 2005-04-01 | Pierce et al. | Applicant |
| US2005/0094966(A1) | 2005-05-01 | Elberbaum | Applicant |
| US2005/0100329(A1) | 2005-05-01 | Lao et al. | Applicant |
| US2005/0101334(A1) | 2005-05-01 | Brown et al. | Applicant |
| US2005/0134966(A1) | 2005-05-01 | Burgner | Applicant |
| US2005/0132200(A1) | 2005-06-01 | Jaffe et al. | Applicant |
| US2005/0151852(A1) | 2005-07-01 | Jomppanen | Applicant |
| US2005/0035161(A1) | 2005-08-01 | Shioda | Applicant |
| US2005/0185438(A1) | 2005-08-01 | Ching | Applicant |
| US2005/0206532(A1) | 2005-09-01 | Lock | Applicant |
| US2005/0206741(A1) | 2005-09-01 | Raber | Applicant |
| US2005/0228234(A1) | 2005-10-01 | Yang | Applicant |
| US2005/0232469(A1) | 2005-10-01 | Schofield et al. | Applicant |
| US2005/0243171(A1) | 2005-11-01 | Ross, Sr. et al. | Applicant |
| US2006/0009238(A1) | 2006-01-01 | Stanco et al. | Applicant |
| US2006/0028811(A1) | 2006-02-01 | Ross, Jr. et al. | Applicant |
| US2006/0055786(A1) | 2006-03-01 | Olilla | Applicant |
| US2006/0158968(A1) | 2006-07-01 | Vanman et al. | Applicant |
| US2006/0164220(A1) | 2006-07-01 | Harter, Jr. et al. | Applicant |
| US2006/0164534(A1) | 2006-07-01 | Robinson et al. | Applicant |
| US2006/0170770(A1) | 2006-08-01 | MacCarthy | Applicant |
| US2006/0176149(A1) | 2006-08-01 | Douglas | Applicant |
| US2006/0183505(A1) | 2006-08-01 | Willrich | Applicant |
| US2006/0193749(A1) | 2006-08-01 | Ghazarian et al. | Applicant |
| US2006/0203090(A1) | 2006-09-01 | Wang et al. | Applicant |
| US2006/0220826(A1) | 2006-10-01 | Rast | Applicant |
| US2006/0225253(A1) | 2006-10-01 | Bates | Applicant |
| US2006/0244601(A1) | 2006-11-01 | Nishimura | Applicant |
| US2006/0256822(A1) | 2006-11-01 | Kwong et al. | Applicant |
| US2006/0267773(A1) | 2006-11-01 | Roque | Applicant |
| US2006/0270465(A1) | 2006-11-01 | Lee et al. | Applicant |
| US2006/0271287(A1) | 2006-11-01 | Gold et al. | Applicant |
| US2006/0274166(A1) | 2006-12-01 | Lee et al. | Applicant |
| US2006/0274828(A1) | 2006-12-01 | Siemens et al. | Applicant |
| US2006/0276200(A1) | 2006-12-01 | Radhakrishnan et al. | Applicant |
| US2006/0282021(A1) | 2006-12-01 | DeVaul et al. | Applicant |
| US2006/0287821(A1) | 2006-12-01 | Lin | Applicant |
| US2006/0293571(A1) | 2006-12-01 | Bao et al. | Applicant |
| US2007/0021134(A1) | 2007-01-01 | Liou | Applicant |
| US2007/0064108(A1) | 2007-03-01 | Haler | Applicant |
| US2007/0067079(A1) | 2007-03-01 | Kosugi | Applicant |
| US2007/0091557(A1) | 2007-04-01 | Kim et al. | Applicant |
| US2007/0102508(A1) | 2007-05-01 | Mcintosh | Applicant |
| US2007/0117083(A1) | 2007-05-01 | Winneg et al. | Applicant |
| US2007/0132567(A1) | 2007-06-01 | Schofield et al. | Applicant |
| US2007/0152811(A1) | 2007-07-01 | Anderson | Applicant |
| US2007/0172053(A1) | 2007-07-01 | Poirier | Applicant |
| US2007/0177023(A1) | 2007-08-01 | Beuhler et al. | Applicant |
| US2007/0199076(A1) | 2007-08-01 | Rensin et al. | Applicant |
| US2007/0229350(A1) | 2007-10-01 | Scalisi et al. | Applicant |
| US2007/0257781(A1) | 2007-11-01 | Denson | Applicant |
| US2007/0257782(A1) | 2007-11-01 | Etcheson | Applicant |
| US2007/0257804(A1) | 2007-11-01 | Gunderson et al. | Applicant |
| US2007/0257815(A1) | 2007-11-01 | Gunderson et al. | Applicant |
| US2007/0260361(A1) | 2007-11-01 | Etcheson | Applicant |
| US2007/0268158(A1) | 2007-11-01 | Gunderson et al. | Applicant |
| US2007/0271105(A1) | 2007-11-01 | Gunderson et al. | Applicant |
| US2007/0277352(A1) | 2007-12-01 | Maron et al. | Applicant |
| US2007/0285222(A1) | 2007-12-01 | Zadnikar | Applicant |
| US2007/0287425(A1) | 2007-12-01 | Bates | Applicant |
| US2007/0297320(A1) | 2007-12-01 | Brummette et al. | Applicant |
| US2008/0001735(A1) | 2008-01-01 | Tran | Applicant |
| US2008/0002031(A1) | 2008-01-01 | Cana et al. | Applicant |
| US2008/0002599(A1) | 2008-02-01 | Denny et al. | Applicant |
| US2008/0030580(A1) | 2008-02-01 | Kashhiawa et al. | Applicant |
| US2008/0042825(A1) | 2008-02-01 | Denny et al. | Applicant |
| US2008/0043736(A1) | 2008-02-01 | Stanley | Applicant |
| US2008/0049830(A1) | 2008-02-01 | Richardson | Applicant |
| US2008/0063252(A1) | 2008-03-01 | Dobbs et al. | Applicant |
| US2008/0084473(A1) | 2008-04-01 | Romanowich | Applicant |
| US2008/0100705(A1) | 2008-05-01 | Kister et al. | Applicant |
| US2008/0122603(A1) | 2008-05-01 | Piante et al. | Applicant |
| US2008/0129518(A1) | 2008-06-01 | Carlton-Foss | Applicant |
| US2008/0143481(A1) | 2008-06-01 | Abraham et al. | Applicant |
| US2008/0144705(A1) | 2008-06-01 | Rackin et al. | Applicant |
| US2008/0169929(A1) | 2008-07-01 | Albertson et al. | Applicant |
| US2008/0170130(A1) | 2008-07-01 | Ollila et al. | Applicant |
| US2008/0211906(A1) | 2008-09-01 | Lovric | Applicant |
| US2008/0222849(A1) | 2008-09-01 | Lavoie | Applicant |
| US2008/0239064(A1) | 2008-10-01 | Iwasaki | Applicant |
| US2008/0246656(A1) | 2008-10-01 | Ghazarian | Applicant |
| US2008/0266118(A1) | 2008-10-01 | Pierson et al. | Applicant |
| US2008/0307435(A1) | 2008-12-01 | Rehman | Applicant |
| US2008/0316314(A1) | 2008-12-01 | Bedell et al. | Applicant |
| US2009/0002491(A1) | 2009-01-01 | Haler | Applicant |
| US2009/0002556(A1) | 2009-01-01 | Manapragada et al. | Applicant |
| US2009/0027499(A1) | 2009-01-01 | Nicholl | Applicant |
| US2009/0052685(A1) | 2009-02-01 | Cilia et al. | Applicant |
| US2009/0070820(A1) | 2009-03-01 | Li | Applicant |
| US2009/0122142(A1) | 2009-05-01 | Shapley | Applicant |
| US2009/0135007(A1) | 2009-05-01 | Donovan et al. | Applicant |
| US2009/0169068(A1) | 2009-07-01 | Okamoto | Applicant |
| US2009/0189981(A1) | 2009-07-01 | Siann et al. | Applicant |
| US2009/0195686(A1) | 2009-08-01 | Shintani | Applicant |
| US2009/0207252(A1) | 2009-08-01 | Raghunath | Applicant |
| US2009/0213204(A1) | 2009-08-01 | Wong | Applicant |
| US2009/0243794(A1) | 2009-10-01 | Morrow | Applicant |
| US2009/0251545(A1) | 2009-10-01 | Shekarri et al. | Applicant |
| US2009/0252486(A1) | 2009-10-01 | Ross, Jr. et al. | Applicant |
| US2009/0276708(A1) | 2009-11-01 | Smith et al. | Applicant |
| US2009/0294538(A1) | 2009-12-01 | Wihlborg et al. | Applicant |
| US2009/0324203(A1) | 2009-12-01 | Wiklof | Applicant |
| US2010/0045798(A1) | 2010-02-01 | Sugimoto et al. | Applicant |
| US2010/0050734(A1) | 2010-03-01 | Chou | Applicant |
| US2010/0060747(A1) | 2010-03-01 | Woodman | Applicant |
| US2010/0097221(A1) | 2010-04-01 | Kreiner et al. | Applicant |
| US2010/0106707(A1) | 2010-04-01 | Brown et al. | Applicant |
| US2010/0118147(A1) | 2010-05-01 | Dorneich et al. | Applicant |
| US2010/0122435(A1) | 2010-05-01 | Markham | Applicant |
| US2010/0123779(A1) | 2010-05-01 | Snyder et al. | Applicant |
| US2010/0177193(A1) | 2010-07-01 | Flores | Applicant |
| US2010/0177891(A1) | 2010-07-01 | Keidar et al. | Applicant |
| US2010/0188201(A1) | 2010-07-01 | Cook et al. | Applicant |
| US2010/0191411(A1) | 2010-07-01 | Cook et al. | Applicant |
| US2010/0194885(A1) | 2010-08-01 | Plaster | Applicant |
| US2010/0217836(A1) | 2010-08-01 | Rofougaran | Applicant |
| US2010/0238009(A1) | 2010-09-01 | Cook et al. | Applicant |
| US2010/0238262(A1) | 2010-09-01 | Kurtz et al. | Applicant |
| US2010/0242076(A1) | 2010-09-01 | Potesta et al. | Applicant |
| US2010/0265331(A1) | 2010-10-01 | Tanaka | Applicant |
| US2010/0274816(A1) | 2010-10-01 | Guzik | Applicant |
| US2010/0287473(A1) | 2010-11-01 | Recesso et al. | Applicant |
| US2011/0006151(A1) | 2011-01-01 | Beard | Applicant |
| US2011/0018998(A1) | 2011-01-01 | Guzik | Applicant |
| US2011/0050904(A1) | 2011-03-01 | Anderson | Applicant |
| US2011/0069151(A1) | 2011-03-01 | Orimoto | Applicant |
| US2011/0084820(A1) | 2011-04-01 | Walter et al. | Applicant |
| US2011/0094003(A1) | 2011-04-01 | Spiewak et al. | Applicant |
| US2011/0098924(A1) | 2011-04-01 | Baladeta et al. | Applicant |
| US2011/0129151(A1) | 2011-06-01 | Saito et al. | Applicant |
| US2011/0157759(A1) | 2011-06-01 | Smith et al. | Applicant |
| US2011/0261176(A1) | 2011-10-01 | Monaghan, Sr. et al. | Applicant |
| US2011/0281547(A1) | 2011-11-01 | Cordero | Applicant |
| US2011/0301971(A1) | 2011-12-01 | Roesch et al. | Applicant |
| US2011/0314401(A1) | 2011-12-01 | Salisbury et al. | Applicant |
| US2012/0038689(A1) | 2012-02-01 | Ishil | Applicant |
| US2012/0056722(A1) | 2012-03-01 | Kawaguchi | Applicant |
| US2012/0063736(A1) | 2012-03-01 | Simmons et al. | Applicant |
| US2012/0120258(A1) | 2012-05-01 | Boutell et al. | Applicant |
| US2012/0162436(A1) | 2012-06-01 | Cordell et al. | Applicant |
| US2012/0188345(A1) | 2012-07-01 | Salow | Applicant |
| US2012/0189286(A1) | 2012-07-01 | Takayama et al. | Applicant |
| US2012/0230540(A1) | 2012-09-01 | Calman et al. | Applicant |
| US2012/0257320(A1) | 2012-10-01 | Brundula et al. | Applicant |
| US2012/0268259(A1) | 2012-10-01 | Igel et al. | Applicant |
| US2012/0276954(A1) | 2012-11-01 | Kowalsky | Applicant |
| US2013/0021153(A1) | 2013-01-01 | Keays | Applicant |
| US2013/0033610(A1) | 2013-02-01 | Osborn | Applicant |
| US2013/0035602(A1) | 2013-02-01 | Gemer | Applicant |
| US2013/0080836(A1) | 2013-03-01 | Stergiou et al. | Applicant |
| US2013/0096731(A1) | 2013-04-01 | Tamari et al. | Applicant |
| US2013/0148295(A1) | 2013-06-01 | Minn et al. | Applicant |
| US2013/0222640(A1) | 2013-08-01 | Baek et al. | Applicant |
| US2013/0225309(A1) | 2013-08-01 | Bentley et al. | Applicant |
| US2013/0300563(A1) | 2013-11-01 | Glaze | Applicant |
| US2013/0343571(A1) | 2013-12-01 | Lee | Applicant |
| US2014/0037262(A1) | 2014-02-01 | Sako | Applicant |
| US2014/0049636(A1) | 2014-02-01 | O'Donnell et al. | Applicant |
| US2014/0092299(A1) | 2014-04-01 | Phillips et al. | Applicant |
| US2014/0094992(A1) | 2014-04-01 | Lambert et al. | Applicant |
| US2014/0098453(A1) | 2014-04-01 | Brundula et al. | Applicant |
| US2014/0140575(A1) | 2014-05-01 | Wolf | Applicant |
| US2014/0170602(A1) | 2014-06-01 | Reed | Examiner |
| US2014/0192194(A1) | 2014-07-01 | Bedell et al. | Applicant |
| US2014/0195105(A1) | 2014-07-01 | Lambert et al. | Applicant |
| US2014/0195272(A1) | 2014-07-01 | Sadiq | Examiner |
| US2014/0210625(A1) | 2014-07-01 | Nemat-Nasser | Applicant |
| US2014/0218544(A1) | 2014-08-01 | Senot et al. | Applicant |
| US2014/0227671(A1) | 2014-08-01 | Olmstead et al. | Applicant |
| US2014/0311215(A1) | 2014-10-01 | Keays et al. | Applicant |
| US2014/0355951(A1) | 2014-12-01 | Tabak | Applicant |
| US2015/0050003(A1) | 2015-02-01 | Ross et al. | Applicant |
| US2015/0050345(A1) | 2015-02-01 | Smyth et al. | Applicant |
| US2015/0051502(A1) | 2015-02-01 | Ross | Applicant |
| US2015/0053776(A1) | 2015-03-01 | Rose et al. | Applicant |
| US2015/0078727(A1) | 2015-03-01 | Ross et al. | Applicant |
| US2015/0088335(A1) | 2015-03-01 | Lambert et al. | Applicant |
| US2015/0103246(A1) | 2015-04-01 | Phillips et al. | Applicant |
| US2015/0229630(A1) | 2015-08-01 | Smith | Applicant |
| US2015/0358549(A1) | 2015-12-01 | Cho et al. | Applicant |
| US2016/0042767(A1) | 2016-02-01 | Araya | Examiner |
| US2016/0104500(A1) | 2016-04-01 | Chee et al. | Applicant |
| US2016/0127695(A1) | 2016-05-01 | Zhang et al. | Applicant |
| US2016/0165192(A1) | 2016-06-01 | Saatchi et al. | Applicant |
| US2016/0364621(A1) | 2016-12-01 | Hill | Examiner |
| US2017/0070659(A1) | 2017-03-01 | Kievsky et al. | Applicant |
| US2017/0195635(A1) | 2017-07-01 | Yokomitsu et al. | Applicant |
| US2017/0230605(A1) | 2017-08-01 | Han et al. | Applicant |
| US2017/0237950(A1) | 2017-08-01 | Araya et al. | Applicant |
| US2017/0244884(A1) | 2017-08-01 | Burtey et al. | Applicant |
| US2017/0277700(A1) | 2017-09-01 | Davis et al. | Applicant |
| US2017/0287523(A1) | 2017-10-01 | Hodulik et al. | Applicant |
| US2018/0023910(A1) | 2018-01-01 | Kramer | Applicant |
| US2018/0050800(A1) | 2018-02-01 | Boykin et al. | Applicant |
| DE102010019451(A1) | 2011-11-01 | Applicant | |
| EP247993(A2) | 2012-07-01 | Applicant | |
| GB2273624 | 1994-06-01 | Applicant | |
| GB2320389 | 1998-05-01 | Applicant | |
| GB2343252 | 2000-05-01 | Applicant | |
| GB2351055 | 2000-12-01 | Applicant | |
| GB2417151 | 2006-02-01 | Applicant | |
| GB2425427 | 2006-10-01 | Applicant | |
| GB2455885 | 2009-07-01 | Applicant | |
| GB2485804(A) | 2012-05-01 | Applicant | |
| IE20090923(A1) | 2010-09-01 | Applicant | |
| JP294188 | 1993-09-01 | Applicant | |
| JP153298 | 1996-06-01 | Applicant | |
| JP198858 | 1997-07-01 | Applicant | |
| JP10076880(A) | 1998-03-01 | Applicant | |
| JP210395 | 1998-07-01 | Applicant | |
| JP2000137263(A) | 2000-05-01 | Applicant | |
| JP2005119631(A) | 2005-05-01 | Applicant | |
| KR20-0236817 | 2001-08-01 | Applicant | |
| KR1050897 | 2011-07-01 | Applicant | |
| RU2383915(C2) | 2010-03-01 | Applicant | |
| RU107851(U1) | 2011-08-01 | Applicant | |
| RU124780(U1) | 2013-02-01 | Applicant | |
| WO9005076 | 1990-05-01 | Applicant | |
| WO9738526 | 1997-10-01 | Applicant | |
| WO9831146 | 1998-07-01 | Applicant | |
| WO9948308 | 1999-09-01 | Applicant | |
| WO39556 | 2000-07-01 | Applicant | |
| WO51360 | 2000-08-01 | Applicant | |
| WO123214(A1) | 2001-04-01 | Applicant | |
| WO249881 | 2002-06-01 | Applicant | |
| WO2095757 | 2002-11-01 | Applicant | |
| WO3049446 | 2003-06-01 | Applicant | |
| WO2004036926(A2) | 2004-04-01 | Applicant | |
| WO2009013526(A1) | 2009-01-01 | Applicant | |
| WO2011001180(A1) | 2011-01-01 | Applicant | |
| WO2012037139(A2) | 2012-03-01 | Applicant | |
| WO2012120083(A1) | 2012-09-01 | Applicant | |
| WO2014000161(A1) | 2014-01-01 | Applicant | |
| WO2014052898(A1) | 2014-04-01 | Applicant |
Non-Patent Literature (95)
- Automation Systems Article, Know-How Bank Co. Ltd. Takes Leap Forward as a Company Specializing in R&D and Technology Consulting, published Jan. 2005.Applicant
- Car Rear View Camera—Multimedia Rear View Mirror—4′ LCD color monitor, Retrieved from the Internet: <URL: http://web.archive.org/web/20050209014751/http://laipac.com/multimedia-rear-mirror.htm>, Feb. 9, 2005.Applicant
- ATC Chameleon. Techdad Review [Online] Jun. 19, 2013 [Retrieved on Dec. 30, 2015]. Retrieved from Internet. <URL:http://www.techdadreview.com/2013/06/19atc-chameleon/>.Applicant
- “Breathalyzer.” Wikipedia. Printed Date: Oct. 16, 2014; Date Page Last Modified: Sep. 14, 2014; <http://en.wikipedia.org/wiki/Breathalyzer>.Applicant
- Dees, Tim; Taser Axon Flex: The next generation of body camera; <http://www.policeone.com/police-products/body-cameras/articles/527231-0-TASER-Axon-Flex-The-next-generation-of-body-camera/>, Date Posted: Mar. 12, 2012; Date Printed: Oct. 27, 2015.Applicant
- Brown, TP-LINK TL-WDR3500 Wireless N600 Router Review, Mar. 6, 2013.Applicant
- Controller Area Network (CAN) Overview, National Instruments White Paper, Aug. 1, 2014.Applicant
- Daskam, Samuel W., Law Enforcement Armed Robbery Alarm System Utilizing Recorded Voice Addresses Via Police Radio Channels, Source: Univ. of Ky, Off of Res and Eng., Serv (UKY BU107), pp. 18-22, 1975.Applicant
- Digital Ally vs. Taser International, Inc., Case No. 2:16-cv-232 (CJM/TJ); US D. Kan, Defendant Taser International Inc.'s Preliminary Invalidity Contentions, Jul. 5, 2016.Applicant
- Electronic Times Article, published Feb. 24, 2005.Applicant
- Supplementary European Search Report dated Sep. 28, 2010 in European Patent Application No. 06803645.8; Applicant: Digital Ally, Inc.Applicant
- W. Fincham, Data Recorders for Accident Investigation, Monitoring of Driver and Vehicle Performance (Digest No. 1997/122), Publication Date: Apr. 10, 1997, pp. 6/1-6/3.Applicant
- Frankel, Harry; Riter, Stephen, Bernat, Andrew, Automated Imaging System for Border Control, Source: University of Kentucky, Office of Engineering Services, (Bulletin) UKY BU, pp. 169-173, Aug. 1986.Applicant
- Freudenrich, Craig, Ph.D.; “How Breathalyzers Work—Why Test?.” HowStuff Works. Printed Date: Oct. 16, 2014; Posted Date: Unknown; <http://electronics.howstuffworks.com/gadgets/automotive/breathalyzer1.htm>.Applicant
- Hankyung Auto News Article, Know-How Bank's Black Box for Cars “Multi-Black Box,” Copyright 2005.Applicant
- Guide to Bluetooth Security: Recommendations of the National Institute of Standards and Technology, National Institute of Standards and Technology, U.S. Dep't of Commerce, NIST Special Publication 800-121, Revision 1 (Jun. 2012).Applicant
- ICOP Extreme Wireless Mic, Operation Supplement, Copyright 2008.Applicant
- ICOP Model 20/20-W Specifications; Enhanced Digital In-Car Video and Audio recording Systems, date: Unknown.Applicant
- ICOP Mobile DVRS; ICOP Model 20/20-W & ICOP 20/20 Vision, date: Unknown.Applicant
- Bertomen, Lindsey J., PoliceOne.com News; “Product Review: ICOP Model 20/20-W,” May 19, 2009.Applicant
- ICOP Raytheon JPS communications, Raytheon Model 20/20-W, Raytheon 20/20 Vision Digital In-Car Video Systems, date: Unknown.Applicant
- Overview of the IEEE 802.15.4 standards for Low rate Wireless Personal Area Networks, 2010 7th International Symposium on Wireless Communication Systems (ISWCS), Copyright 2010.Applicant
- Lewis, S.R., Future System Specifications for Traffic Enforcement Equipment, S.R. 1 Source: IEE Colloquium (Digest), N 252, Publication Date: Nov. 18, 1996, pp. 8/1-8/2.Applicant
- Kopin Corporation; Home Page; Printed Date: Oct. 16, 2014; Posted Date: Unknown; <http://www.kopin.com>.Applicant
- Translation of Korean Patent No. 10-1050897, published Jul. 20, 2011.Applicant
- Lilliput RV 18-50NP 5″ Rear View Mirror TFT LCD Screen with Camera, Retrieved from the Internet: <URL: http://www.case-mod.com/lilliput-rv1850np-rear-view-mirror-tft-lcd-screen-with-camera-p-1271.html>, Mar. 4, 2005.Applicant
- Motor Magazine Article, Recreating the Scene of an Accident, published 2005.Applicant
- New Rearview-Mirror-Based Camera Display Takes the Guesswork Out of Backing Up Retrieved from the Internet: <URL: httb://news.thomasnet.com/fullstory/497750>, Press Release, Oct. 30, 2006.Applicant
- SIIF Award for Multi Black Box, published Dec. 10, 2004.Applicant
- Near Field Communication; Sony Corporation; pp. 1-7, Date: Unknown.Applicant
- Oregon Scientific ATC Chameleon Dual Lens HD Action Camera, http://www.oregonscientificstore.com/Oregon-Scientific-ATC-Chameleon-Dual-Lens-HD-Action-Camera.data, Date Posted: Unknown; Date Printed: Oct. 13, 2014, pp. 1-4.Applicant
- Asian Wolf High Quality Angel Eye Body Video Spy Camera Recorder System, http://www.asianwolf.com/covert-bodycam-hq-angeleye.html, Sep. 26, 2013, Date Posted: Unknown, pp. 1-3.Applicant
- Brick House Security Body Worn Cameras / Hidden Cameras / Covert Spy Cameras, http://www.brickhousesecurity.com/body-wom-covert-spy-cameras.html?sf=0#sortblock&CMPID=PD_Google_%22body+camera%22&utm_source=google&utm_medium=cpc&utm_term=%22body+camera%22&mm_campaign=876a94ea5dd198a8c5dc3d1e67eccb34&keyword=%22body+camera%.Applicant
- Amazon.com wearable camcorders, http://www.amazon.com/s/ref=nb_sb_ss_i_0_4?url=search-alias%3Dphoto&field-keywords=wearable+camcorder&x=0&y=0&sprefix=wear, Sep. 26, 2013, Date Posted: Unknown, pp. 1-4.Applicant
- Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration dated Feb. 4, 2016; International Application No. PCT/US2015/056052; International Filing Date: Oct. 16, 2015; Applicant: Digital Ally, Inc.Applicant
- http:/ /www.k-h-b.com/board/board.php?board=products01&comand=body&no=1, Current State of Technology Held by the Company, Copyright 2005.Applicant
- City of Pomona Request for Proposals for Mobile Video Recording System for Police Vehicles, dated prior to Apr. 4, 2013.Applicant
- http://www.k-h-b.com/sub1_02.html, Copyright 2005.Applicant
- Renstrom, Joell; “Tiny 3D Projectors Allow You To Transmit Holograms From A Cell Phone.” Giant Freakin Robot. Printed Date: Oct. 16, 2014; Posted Date: Jun. 13, 2014; <http://www.giantfreakinrobot.com/sci/coming-3d-projectors-transmit-holograms-cell-phone.html>.Applicant
- Request for Comment 1323 of the Internet Engineering Task Force, TCP Extensions for High Performance, Date: May 1992.Applicant
- RevealMedia RS3-SX high definition video recorder, http://www.revealmedia.com/buy-t166/cameras/rs3-sx.aspx, Sep. 26, 2013, Date Posted: Unknown, pp. 1-2.Applicant
- Scorpion Micro DV Video Audio Recorder, http://www.leacorp.com/scorpion-micro-dv-video-audio-recorder/, Sep. 26, 2013, Date Posted: Unknown, pp. 1-3.Applicant
- “Stalker Press Room—Using In-Car Video, the Internet, and the Cloud to keep police officers safe is the subject of CopTrax live, free webinar.” Stalker. Printed Date: Oct. 16, 2014; Posted Date: Jul. 31, 2014.Applicant
- State of Utah Invitation to Bid State Cooperative Contract; Vendor: ICOP Digital, Inc., Contract No. MA503, Jul. 1, 2008.Applicant
- Wasson, Brian; “Digital Eyewear for Law Enforcement.” Printed Date: Oct. 16, 2014; Posted Date: Dec. 9, 2013; <http://www.wassom.com/digital-eyewear-for-law-enforcement.html>.Applicant
- X26 Taser, Date Unknown.Applicant
- Taser International; Taser X26 Specification Sheet, 2003.Applicant
- Digital Ally First Vu Mountable Digital Camera Video Recorder, http://www.opticsplanet.com/digital-ally-first-vu-mountable-digital-camera-video-recorder.html?gclid=CIKohcX05rkCFSIo7AodU0IA0g&ef_id=UjCGEAAAAWGEjrQF:20130925155534:s, Sep. 25, 2013, Date Posted: Unknown, pp. 1-4.Applicant
- Drift X170, http://driftinnovation.com/support/firmware-update/x170/, Sep. 26, 2013, Date Posted: Unknown, p. 1.Applicant
- Dyna Spy Inc. hidden cameras, https://www.dynaspy.com/hidden-cameras/spy-cameras/body-worn-wearable-spy-cameras, Sep. 26, 2013, Date Posted: Unknown, pp. 1-3.Applicant
- International Association of Chiefs of Police Digital Video System Minimum Specifications; Nov. 21, 2008.Applicant
- Petition for Inter Partes Review No. 2017-00375, Taser International, Inc. v. Digital Ally, Inc., filed Dec. 1, 2013.Applicant
- Petition for Inter Partes Review No. 2017-00376, Taser International, Inc. v. Digital Ally, Inc., filed Dec. 1, 2013.Applicant
- Petition for Inter Partes Review No. 2017-00515, Taser International, Inc. v. Digital Ally Inc., filed Jan. 11, 2017.Applicant
- PCT Patent Application PCT/US16/34345 International Search Report and Written Opinion dated Dec. 29, 2016.Applicant
- Digital Ally, Inc. vs. Taser International, Inc., Case No. 2:16-cv-020232 (CJM/TJ); US D. Kan, Complaint for Patent Infringement, Jan. 14, 2016.Applicant
- Digital Ally, Inc. vs. Enforcement video LLC d/b/a Watchguard Video., Case No. 2:16-cv-02349 (CJM/TJ); US D. Kan, Complaint for Patent Infringement, May 27, 2016.Applicant
- State of Utah Invitation to Bid State Cooperative Contract; Vendor: Kustom Signals Inc., Contract No. MA1991, Apr. 25, 2008.Applicant
- Petition for Inter Partes Review No. 2017-00775, Taser International, Inc. v. Digital Ally Inc., filed Jan. 25, 2017.Applicant
- Ecplaza HY-001HD law enforcement DVR, http://fireeye.en.ecplaza.net/law-enforcement-dvr--238185-1619696.html, Sep. 26, 2013, Date Posted: Unknown, pp. 1-3.Applicant
- Edesix VideoBadge, http://www.edesix.com/edesix-products, Sep. 26, 2013, Date Posted: Unknown, pp. 1-3.Applicant
- GoPro Official Website: The World's Most Versatile Camera, http://gopro.com/products/?gclid=CKqHv9jT4rkCFWZk7AodyiAAaQ, Sep. 23, 2013, Date Posted: Unknown, pp. 4-9.Applicant
- Isaw Advance Hull HD EXtreme, www.isawcam.co.kr, Sep. 26, 2013, Date Posted: Unknown, p. 1.Applicant
- Kustom Signals VieVu, http://www.kustomsignals.com/index.php/mvideo/vievu, Sep. 26, 2013, Date Posted: Unknown, pp. 1-4.Applicant
- Lea-Aid Scorpion Micro Recorder Patrol kit,http://www.leacorp.com/products/SCORPION-Micro-Recorder-Patrol-kit.html, Sep. 26, 2013, Date Posted: Unknown, pp. 1-2.Applicant
- Looxcie Wearable & mountable streaming video cams, http://www.looxcie.com/overview?gclid=CPbDyv6piq8CFWeFQAodlhXC-w, Sep. 26, 2013, Date Posted: Unknown, pp. 1-4.Applicant
- Midland XTC HD Video Camera, http://midlandradio.com/Company/xtc100-signup, Sep. 26, 2013, Date Posted: Unknown, pp. 1-3.Applicant
- Panasonic Handheld AVCCAM HD Recorder/Player, http://www.panasonic.com/business/provideo/ag-hmr10.asp, Sep. 26, 2013, Date Posted: Unknown, pp. 1-2.Applicant
- Notification of Transmittal of the International Search Report and the Written Opinion of the International Search Authority, or the Declaration dated Jan. 30, 2014, International Application No. PCT/US2013/062415; International Filing date Sep. 27, 2013, Applicant: Digital Ally, Inc.Applicant
- Point of View Cameras Military & Police, http://pointofviewcameras.com/military-police, Sep. 26, 2013, Date Posted: Unknown, pp. 1-2.Applicant
- POV.HD System Digital Video Camera, http://www.vio-pov.com/index.php, Sep. 26, 2013, Date Posted: Unknown, pp. 1-3.Applicant
- SIV Security in Vehicle Driving Partner, http://www.siv.co.kr/, Sep. 26, 2013, Date Posted: Unknown, p. 1.Applicant
- Spy Chest Mini Spy Camera / Self Contained Mini camcorder / Audio & Video Recorder, http://www.spytechs.com/spy_cameras/mini-spy-camera.htm, Sep. 26, 2013, Date Posted: Unknown, pp. 1-3.Applicant
- Stalker VUE Law Enforcement Grade Body Worn Video Camera/Recorder, http://www.stalkerradar.com/law_vue.shtml, Sep. 26, 2013, Date Posted: Unknown, pp. 1-2.Applicant
- SUV Cam, http://www.elmo.co.jp/suv-cam/en/product/index.html, Sep. 26, 2013, Date Posted: Unknown, p. 1.Applicant
- Taser Axon Body on Officer Video/Police Body Camera, http://www.taser.com/products/on-officer-video/axon-body-on-officer-video, Sep. 23, 2013, Date Posted: Unknown, pp. 1-8.Applicant
- Taser Axon Flex On-Officer Video/Police Video Camera, http://www.taser.com/products/on-officer-video/taser-axon, Sep. 26, 2013, Date Posted: Unknown, pp. 1-8.Applicant
- Taser Cam Law Enforcement Audio/Video Recorder (gun mounted), http://www.taser.com/products/on-officer-video/taser-cam, Sep. 26, 2013, Date Posted: Unknown, pp. 1-3.Applicant
- Tide Leader police body worn camera, http://tideleader.en.gongchang.com/product/14899076, Sep. 26, 2013, Date Posted: Unknown, pp. 1-3.Applicant
- uCorder Pockito Wearable Mini Pocket Camcorder, http://www.ucorder.com/, Sep. 26, 2013, Date Posted: Unknown, p. 1.Applicant
- Veho MUVI HD, http://veho-uk.fastnet.co.uk/main/shop.aspx?category=CAMMUVIHD, Sep. 26, 2013, Date Posted: Unknown, pp. 1-5.Applicant
- Veho MUVI portable wireless speaker with dock, http://veho-uk.fastnet.co.uk/main/shop.aspx?category=camcorder, Sep. 26, 2013, Date Posted: Unknown, p. 1.Applicant
- Vidmic Officer Worn Video & Radio Accessories, http://www.vidmic.com/, Sep. 26, 2013, Date Posted: Unknown, p. 1.Applicant
- Vievu Products, http://www.vievu.com/vievu-products/vievu-squared/, Sep. 25, 2013, Date Posted: Unknown, pp. 1-2.Applicant
- WatchGuard CopVu Wearable Video Camera System, http://watchguardvideo.com/copvu/overview, Sep. 26, 2013, Date Posted: Unknown, pp. 1-2.Applicant
- Witness Cam headset, http://www.secgru.com/DVR-Witness-Cam-Headset-Video-Recorder-SG-DVR-1-COP.html, Sep. 26, 2013, Date Posted: Unknown, pp. 1-2.Applicant
- WolfCom 3rd Eye, X1 A/V Recorder for Police and Military, http://wolfcomusa.com/Products/Products.html, Sep. 26, 2013, Date Posted: Unknown, pp. 1-3.Applicant
- Notification of Transmittal of the International Search Report and the Written Opinion of the International Search Authority, or the Declaration dated Jan. 14, 2016, International Application No. PCT/US2015/056039; International Filing date Oct. 16, 2015, Applicant: Digital Ally, Inc.Applicant
- U.S. Appl. No. 13/959,142 Final Office Action dated Jul. 20, 2016.Applicant
- U.S. Appl. No. 13/959,142 Office Action dated Nov. 3, 2015.Applicant
- Invalidity Chart for International Publication No. WO2014/000161 Oct. 31, 2017.Applicant
- Petition for Post Grant Review No. PGR2018-00052, Axon Enterprise, Inc. v. Digital Ally, Inc., filed Mar. 19, 2018.Applicant
- MPEG-4 Coding of Moving Pictures and Audio ISO/IEC JTC1/SC29/WG11 N4668 dated Mar. 2002.Applicant
- Invalidity Chart for International Publication No. WO2014/000161 Oct. 31, 2017 (Resubmitted).Applicant
- European Patent Application 15850436.6 Search Report dated May 4, 2018.Applicant