Vehicle event recorders with integrated web server

Information

  • Patent Grant
  • 8996240
  • Patent Number
    8,996,240
  • Date Filed
    Thursday, March 16, 2006
    18 years ago
  • Date Issued
    Tuesday, March 31, 2015
    9 years ago
Abstract
Vehicle event recorders are arranged with integrated web servers to provide a simple user interface and control mechanism which may be address with commonly available hardware and software. A vehicle event recorder of these inventions couples to a network having a workstation node. The workstation having either of the many available web browsers can be used to view, address, control, perform data transfer, et cetera, by way of data exchange in accordance with simple IP protocols. A vehicle equipped with these systems returns to a household to make a network connection. A local server is used to see all exposed system controls as provided by predefined web pages provided by a web server integrated as part of the vehicle event recorder unit.
Description
BACKGROUND OF THE INVENTIONS

1. Field


The following inventions disclosure is generally concerned with vehicle event recorder systems and specifically concerned with vehicle event recorder systems having integrated web server modules.


2. Prior Art


The inventions presented in U.S. Pat. No. 6,947,817 by inventor Diem for nonintrusive diagnostic tools for testing oxygen sensor operation relates to a diagnostic system for testing a vehicle where such systems include a wireless communications link between a vehicle any remote network of server computers. In particular, a WiFi type access points allowed an analyzer to communicate by way the Internet with a server computer hosting and oxygen sensor SOAP (simple object access protocol) service. In a nutshell, the system relates to smog sensors for automobiles which communicate with remote servers by way of a WiFi communications links.


Video surveillance systems are used to provide video records of events, incidents, happenings, et cetera in locations of special interest. For example, retail banking offices are generally protected with video surveillance systems which provide video evidence in case of robbery. While video surveillance systems are generally used in fixed location scenarios, mobile video surveillance systems are also commonly used today.


In particular, video systems have been configured for use in conjunction with an automobile and especially for use with police cruiser type automobiles. As a police cruiser is frequently quite near the scene of an active crime, important image information may be captured by video cameras installed on the police cruiser. Specific activity of interest which may occur about an automobile is not always associated with crime and criminals. Sometimes events which occur in the environments immediately about an automobile are of interest for reasons having nothing to do with crime. In example, a simple traffic accident where two cars come together in a collision may be the subject of video evidence of value. Events and circumstances leading up to the collision accident may be preserved such that an accurate reconstruction can be created. This information is useful when trying come to a determination as to cause, fault and liability. As such, general use of video systems in conjunction with automobiles is quickly becoming an important tool useful for the protection of all. Some examples of the systems are illustrated below with reference to pertinent documents.


Inventor Schmidt presents in U.S. Pat. No. 5,570,127, a video recording system for a passenger vehicle, namely a school bus, which has two video cameras one for an inside bus view and one for a traffic view, a single recorder, and a system whereby the two cameras are multiplexed at appropriate times, to the recording device. A switching signal determines which of the two video cameras is in communication with the video recorder so as to view passengers on the passenger vehicle at certain times and passing traffic at other times.


Thomas Doyle of San Diego, Calif. and QUALCOMM Inc. also of San Diego, present an invention for a method and apparatus for detecting fault conditions in a vehicle data recording device to detect tampering or unauthorized access, in U.S. Pat. No. 5,586,130. The system includes vehicle sensors for monitoring one or more operational parameters of the vehicle. The fault detection technique contemplates storing a current time value at regular intervals during periods in which the recording device is provided with a source of main power. Inventor Doyle also teaches in the U.S. Pat. No. 5,815,071, a method and apparatus for monitoring parameters of vehicle electronic control units.


A “computerized vehicle log” is presented by Dan Kikinis of Saratoga Calif. in U.S. Pat. No. 5,815,093. The vehicle accident recording system employs a digital camera connected to a controller in nonvolatile memory, and an accident sensing interrupter. The oldest memory is overwritten by the newest images, until an accident is detected at which time the memory is blocked from further overwrites to protect the more vital images, which may include important information about the accident. Mr. Kikinis instructs that in preferred embodiments, the system has a communications port whereby stored images are downloaded after an accident to a digital device capable of displaying images. This feature is described in greater detail in the specification which indicates a wired download to a server having specialized image handling and processing software thereon.


Inventor Mr. Turner of Compton, Calif., no less, teaches an antitheft device for an automotive vehicle having both an audible alarm and visual monitor system. Video monitor operators are responsible for monitoring and handling an emergency situation and informing a 911 emergency station. This system is presented in U.S. Pat. No. 6,002,326.


A vehicle accident video recorder, in particular, a railroad vehicle accident video recorder, is taught by inventors Cox et al. In this system, a method and monitoring unit for recording the status of the railroad vehicle prior to a potential accident is presented. The monitoring unit continuously monitors the status of an emergency brake of the railroad vehicle and the status of a horn of the railroad vehicle. Video images are recorded and captured for a predetermined period of time after detecting that the emergency brake or horn blast has been applied as an event trigger. This invention is the subject of U.S. Pat. No. 6,088,635.


A vehicle crash data recorder is presented by inventor Ferguson of Bellaire, Ohio in U.S. Pat. No. 6,185,490. The apparatus is arranged with a three stage memory to record and retain information. And further it is equipped with a series and parallel connectors to provide instant on-scene access to accident data. It is important to note that Ferguson finds it important to include the possibility of on-site access to the data. Further, that Ferguson teaches use of a wired connection in the form of a serial or parallel hardwire connector. This teaching of Ferguson is common in many advanced systems configured as vehicle event recorders.


A traffic accident data recorder and traffic accident reproduction system and method is presented as U.S. Pat. No. 6,246,933. A plurality of sensors for registering vehicle operation parameters including at least one vehicle mounted digital video, audio camera is included for sensing storing and updating operational parameters. A rewritable, nonvolatile memory is provided for storing those processed operational parameters and video images and audio signals, which are provided by the microprocessor controller. Data is converted to a computer readable form and read by a computer such that an accident can be reconstructed via data collected.


U.S. Pat. No. 6,298,290 presented by Abe et al, teaches a memory apparatus for vehicle information data. A plurality of sensors including a CCD camera collision center of vehicle speed sensors, steering angle sensor, brake pressure sensor, acceleration sensor, are all coupled to a control unit. Further, the control unit passes information to a flash memory and a RAM memory subject to an encoder. The information collected is passed through a video output terminal. This illustrates another hardwire system and the importance placed by experts in the art on a computer hardware interface. This is partly due to the fact that video systems are typically data intensive and wired systems are necessary as they have bandwidth sufficient for transfers of large amounts of data.


Mazzilli of Bayside, N.Y. teaches in U.S. Pat. No. 6,333,759 a 360° automobile video camera system. A complex mechanical mount provides for a single camera to adjust its viewing angle giving a 360° range for video recording inside and outside of an automotive vehicle.


U.S. Pat. No. 6,389,339 granted to Inventor Just, of Alpharetta, Ga. teaches a vehicle operation monitoring system and method. Operation of a vehicle is monitored with an onboard video camera linked with a radio transceiver. A monitoring service includes a cellular telecommunications network to view a video data received from the transceiver to a home-base computer. These systems are aimed at parental monitoring of adolescent driving. The mobile modem is designed for transmitting live video information into the network as the vehicle travels.


Morgan, Hausman, Chilek, Hubenak, Kappler, Witz, and Wright with their heads together invented an advanced law enforcement and response technology in U.S. Pat. No. 6,411,874 granted Jun. 25, 2002. A central control system affords intuitive and easy control of numerous subsystems associated with a police car or other emergency vehicle. This highly integrated system provides advanced control apparatus which drives a plurality of detector systems including video and audio systems distributed about the vehicle. A primary feature included in this device includes an advanced user interface and display system, which permits high level driver interaction with the system.


Inventor Lambert teaches in U.S. Pat. No. 6,421,080 a “digital surveillance system with pre-event recording”. Pre-event recording is important in accident recording systems, because detection of the accident generally happens after the accident has occurred. A first memory is used for temporary storage. Images are stored in the temporary storage continuously until a trigger is activated which indicates an accident has occurred at which time images are transferred to a more permanent memory.


Systems taught by Gary Rayner in U.S. Pat. Nos. 6,389,340; 6,405,112; 6,449,540; and 6,718,239, each directed to cameras for automobiles which capture video images, both of forward-looking and driver views, and store recorded images locally on a mass storage system. An operator, at the end of the vehicle service day, puts a wired connector into a device port and downloads information into a desktop computer system having specialized application software whereby the images and other information can be played-back and analyzed at a highly integrated user display interface.


It is not possible in the systems Rayner teaches for an administrative operator to manipulate or otherwise handle the data captured in the vehicle at an off-site location without human intervention. It is necessary for a download operator to transfer data captured from the recorder unit device to a disconnected computer system. While proprietary ‘DriveCam’ files can be e-mailed or otherwise transferred through the Internet, those files are in a format with a can only be digested by desktop software running at a remote computer. It is necessary to have the DriveCam desktop application on the remote computer. In order that the files be properly read. In this way, data captured by the vehicles is totally unavailable to some parties having an interest in the data. Namely those parties who do not have access to a computer appropriately arranged with the specific DriveCam application software. A second and major disadvantage is systems presented by Rayner includes necessity that a human operator service the equipment each day in a manual download action.


Remote reporting and manipulation of automobile systems is not entirely new. The following are very important teachings relating to some automobile systems having a wireless communications link component.


Inventors Fan et al, teach inventions of methods and systems for detecting vehicle collision using global positioning system GPS. The disclosure of Jun. 12, 2001 resulted in granted patent having U.S. Pat. No. 6,459,988. A GPS receiver is combined with wireless technology to automatically report accident and third parties remotely located. A system uses the GPS signals to determine when an acceleration value exceeds the preset threshold which is meant to be indicative of an accident having occurred.


Of particular interest include inventions presented by inventors Nagda et al., in the document numbered U.S. Pat. No. 6,862,524 entitled using location data to determine trafficking route information. In this system for determining and disseminating traffic information or route information, traffic condition information is collected from mobile units that provide their location or position information. Further route information may be utilized to determine whether a mobile unit is allowed or prohibited from traveling along a certain route.


A common assignee, @Road Inc., owns the preceding two patents in addition to the following: U.S. Pat. Nos. 6,529,159; 6,552,682; 6,594,576; 6,664,922; 6,795,017; 6,832,140; 6,867,733; 6,882,313; and 6,922,566. As such, @Road Inc., must be considered a major innovator in position technologies arts as they relate to mobile vehicles and remote server computers.


General Motors Corp. teaches in U.S. Pat. No. 6,728,612, an automated telematics test system and method. The invention provides a method and system testing a telematics system in a mobile vehicle a test command from a test center to a call center is based on a test script. The mobile vehicle is continuously in contact by way of cellular communication networks with a remotely located host computer.


Inventor Earl Diem and Delphi Technologies Inc., had granted to them on Sep. 20, 2005, U.S. Pat. No. 6,947,817. The nonintrusive diagnostic tool for sensing oxygen sensor operation include a scheme or an oxygen analyzer deployed in a mobile vehicle communicates by way of an access point to a remotely located server. A diagnostic heuristic is used to analyze the data and confirm proper operation of the sensor. Analysis may be performed by a mainframe computer quickly note from the actual oxygen sensor.


Similar patents including special relationships between mobile vehicles and remote host computers include those presented by various inventors in U.S. Pat. Nos. 6,735,503; 6,739,078; 6,760,757; 6,810,362; 6,832,141; and 6,850,823.


Another special group of inventions owned by Reynolds and Reynolds Holding Inc., is taught first by Lightner et al, in U.S. Pat. No. 6,928,348 issued Aug. 9, 2005. In these inventions, Internet based emission tests are performed on vehicles having special wireless couplings to computer networks. Data may be further transferred to entities of particular interest including the EPA or California Air Resources Board, for example, or particular insurance companies and other organizations concerned with vehicle emissions and environment.


Other patents held by Reynolds and Reynolds Holding Inc., include those relating to reporting of automobile performance parameters to remote servers via wireless links. Specifically, an onboard data bus OBD system is coupled to a microprocessor, by way of a standard electrical connector. The microprocessor periodically receives data and transmits it into the wireless communications system. This information is more fully described in U.S. patent granted Oct. 21, 2003 numbered U.S. Pat. No. 6,636,790. Inventors Lightner et al, present method and apparatus for remotely characterizing the vehicle performance. Data at the onboard data by his periodically received by a microprocessor and passed into a local transmitter. The invention specifically calls out transmission of data on a predetermined time interval. Thus these inventions do not anticipate nor include processing and analysis steps which result in data being passed at time other than expiration of the predetermined time period.


Reynolds and Reynolds Holding Inc., further describes systems where motor vehicles are coupled by wireless communications links to remote host servers in U.S. Pat. No. 6,732,031.


While systems and inventions of the art are designed to achieve particular goals and objectives, some of those being no less than remarkable, these inventions have limitations which prevent their use in new ways now possible. Inventions of the art are not used and cannot be used to realize the advantages and objectives of the inventions taught here following.


The inventions disclosure of U.S. patent application filed Dec. 9, 2005 having Ser. No. 11/299,028 is presented by this same inventor. Further, another U.S. application filed Dec. 8, 2005 having Ser. No. 11/297,669 is similarly presented by same inventor. In addition, another U.S. application filed Dec. 7, 2005, entitled: “Memory Management in Event Recording Systems” serial number unknown; this application will be amended to properly reflect the serial number as soon as it is known, is also presented by instant inventor. Each of these disclosures include material which is critically important to a full understanding of important concepts relating to vehicle event recording systems. Accordingly, these disclosures are hereby incorporated here by explicit reference.


SUMMARY OF THESE INVENTIONS

Comes now, James Plante with inventions of vehicle event recorders having integrated web servers.


Vehicle event recorders having integrated web server modules are first presented herein this disclosure. A vehicle event recorder is arranged as a video camera, microprocessor, memory among other supporting subsystems such that when a predetermined event occurs, in example a car crash or unexpected impact, a video record of the incident is preserved. In these inventions, such vehicle event recorders are further provided with an advanced interface system. A web server module is incorporated and arranged as part of the included computer system. Thus, the system and all its subsystems may be addressed via hypertext transfer protocol, http, type transactions and commands. Users can interact with vehicle event recorder units of these inventions with nothing other than any standard computer. It is no longer necessary to load, manage, and maintain, proprietary application specific software on a user's workstation computer. Rather, a user may manipulate system settings, view and transfer files, receive e-mail alerts, and otherwise completely control the device as its functionality is entirely exposed by the integrated web server and complementary computing systems.


As a consumer product, a vehicle event recorder may be installed in a family vehicle without special knowledge or skill. The device operates to collect video and other vehicle performance information while the vehicle is in normal operation. Upon connection to a computer network, or more specifically a home computer network, a simple computer workstation equipped with a web browser can address the vehicle event recorder as the web server is responsive to requests sent by the web browser.


In addition, these systems include pre-programmed ‘web pages’ or ‘web forms’. These pages may be implemented as computer files stored in a ROM or DRAM, et cetera, of the vehicle event recorder. They are pre-programmed with interconnects and preset relationships with subsystems. For example, these pages may be provide an interface to camera settings such as brightness and contrast, et cetera.


Further, in some versions, a file transfer protocol server and simple mail transfer protocol servers are also included. These servers also support general interface mechanisms which permit standard computers to interact with these vehicle event recorders without requiring installation of special software and hardware systems.


Objectives of these Inventions

It is a primary object of these inventions to provide vehicle event recorders and vehicle event recorder systems.


It is an object of these inventions to provide vehicle event recorders with an improved user interface.


It is a further object to eliminate previously required workstation desktop applications and complex external communications mechanisms and protocol.


It is an object of these inventions to provide interface to vehicle event recording systems via standard computing platforms and ubiquitous software.


A better understanding can be had with reference to detailed description of preferred embodiments and with reference to appended drawings. Embodiments presented are particular ways to realize these inventions and are not inclusive of all ways possible. Therefore, there may exist embodiments that do not deviate from the spirit and scope of this disclosure as set forth by appended claims, but do not appear here as specific examples. It will be appreciated that a great plurality of alternative versions are possible.





BRIEF DESCRIPTION OF THE DRAWING FIGURES

These and other features, aspects, and advantages of the present invention will become better understood with regard to the following description, appended claims and drawings where:



FIG. 1 is a simple block diagram showing relationships between primary elements of systems of these inventions;



FIG. 2 is a block diagram of a vehicle event recorder head;



FIG. 3 illustrates the relationship a vehicle event recorder video camera has with its exterior and further illustrates other important elements of the vehicle event recorder head;



FIG. 4 illustrates transactions over a network element of these vehicle event recorder systems;



FIG. 5 illustrates an example browser type user interface associated with these systems;



FIG. 6 illustrates a second page of a browser having various system control functions which may be manipulated via the browser;



FIG. 7 illustrates an important network architecture and connection associated with these systems;



FIG. 8 illustrates in diagram several additional important functions which may be incorporated within a vehicle event recorder head; and



FIG. 9 illustrates an important network configuration which permits remote access to vehicle event recorder heads.





GLOSSARY OF SPECIAL TERMS

Throughout this disclosure, reference is made to some terms which may or may not be exactly defined in popular dictionaries as they are defined here. To provide a more precise disclosure, the following terms are presented with a view to clarity so that the true breadth and scope may be more readily appreciated. Although every attempt is made to be precise and thorough, it is a necessary condition that not all meanings associated with each term can be completely set forth. Accordingly, each term is intended to also include its common meaning which may be derived from general usage within the pertinent arts or by dictionary meaning. Where the presented definition is in conflict with a dictionary or arts definition, one must use the context of use and liberal discretion to arrive at an intended meaning. One will be well advised to error on the side of attaching broader meanings to terms used in order to fully appreciate the depth of the teaching and to understand all the intended variations.


Web Browser


A web browser is a computer graphical user interface operable for receiving computer files and presenting a graphical display which may have interactive elements sometimes called ‘controls’ or web controls. Further, a browser is operable for sending requests in the form of a computer file—generally both received and sent files are in a format such as XML or more familiarly HTML.


Web Server


A web server is implemented as a special module of a computer and is operable for exchanging information via computer files—generally files in XML/HTML formats. A web server receives requests and returns responses to external parties via a communications link.


Web Request


A web request is a data transmission arranged in agreement with Internet protocol directed to a specific web server.


Web Response


A web response is a data transmission by a web server arranged in agreement with Internet protocol and directed toward a requesting agent usually a web browser.


Physical Anomaly


Any change in a prescribed physical parameter which is defined as outside the scope of normal operating conditions.


Managed Loop Memory


A ‘managed loop memory’ is a memory system arranged to preserve in detail data captured during a period immediately past with respect to any instant but to overwrite that data with newer data when that data has sufficiently aged in accordance with a predefined expiration definition.


Vehicle Environments


The environment in and about a vehicle includes those spaces interior or exterior with respect to the car body. That is to say, traffic ahead of, behind, towards the sides of, and inside the driver compartment are all included as vehicle environments.


Communications Port


Includes means for supporting a data communications link including a transceiver or modem arrangement and suitable connection apparatus. Some examples include: a mobile cellular transceiver; WiFi; WiMax; bluetooth; Ethernet; serial port such as RS-232; among others.


PREFERRED EMBODIMENTS OF THESE INVENTIONS

In accordance with each of preferred embodiments of these inventions, vehicle event recorders having integrated Web servers are provided. It will be appreciated that each of embodiments described include apparatus and that the apparatus of one preferred embodiment may be different than an apparatus of an alternative embodiment.


Vehicle event recorders first presented here are generally characterized as including: a video camera, microprocessor, memory, and web server module. Video images are captured during use of the vehicle. When a particular ‘event’ occurs, a captured video series is saved to a durable memory. When the vehicle is returned to a location where network connectivity is available, the captured video series is made available for review via a web server. The integrated web server, when connected to a TCP/IP network, can receive requests for information from external web browsers. These requests for information may be directed as requests to view data captured during a recent previous operation period. The web server is suitably coupled to a memory whereby data and files stored there may be transferred to the requesting web browser. Accordingly, web servers of these systems expose data captured by the device, including video data of scenes about the vehicle captured during vehicle use. In addition, these web servers are also coupled to system settings and operational parameters whereby adjustments to those settings and parameters may be effected via a web browser. For example, trigger threshold values may be set to be more or less sensitive. An event trigger system arranged to detect an abrupt acceleration action may include an adjustable sensitivity level. Via web browser interface, the event trigger threshold can be set by a remote user operating a standard web browser in communication with the device web server. A web server is part of a complement pair which forms a user interface system. A web server and web browser connected together via a TCP/IP network form an interface system which is convenient and very powerful. Complete control of the device is permitted because prerecorded “web pages” or “web forms” may be prepared as part of the web server. These pages and the controls thereon may be coupled to physical systems of the device. In this way, the user having no other tools than a standard computer with a web browser is able to completely interface with the system. As such, proprietary software and the complexity and inconvenience associated therewith are completely eliminated.


With reference to FIG. 1, the reader will gain further appreciation of architecture relating to apparatus of these inventions. In particular, vehicle event recorder head unit 1 with integrated web server 2 is installed in a motor vehicle such as a common family car 3. The vehicle event recorder head is coupled by way of a data communications link 4, preferably a TCP/IP network to a computer workstation 5 operable for running a web browser 6. The arrangement provides a graphical user interface to a remotely located user 7, and further, means of remote input and interaction with the vehicle event recorder by way of common computer keyboard 8 for example. A user, in the comfort of a computer workplace, can provide a vehicle event recorder mounted in an automobile with instruction, update, interaction, download, review, among others. Functionality exposed by the vehicle event recorder becomes available to users working at a workstation by way of a common computer or ‘Internet browser’ graphical user interface. For example, a user can use simple browser control interfaces to set the camera contrast and brightness while at a workstation not in, or even not near, the car.


A vehicle event recorder with integrated web server is installed in the vehicle whereby a video camera has a clear view of the space and surroundings in front of the car. In this way, should the unfortunate occasion of a traffic accident occur, the video camera can provide a video record of traffic conditions and events leading up to the accident. A video series, including images captured just prior and just after an event moment as initiated by an event trigger, the series relating to an accident, is saved in a vehicle event recorder local memory. At a later time, when the vehicle is appropriately coupled to a workstation by suitable communications link, video series data can be transferred to the workstation where it may be further viewed and analyzed. A vehicle may be coupled to a workstation by communications link of several alternative forms including at least an Ethernet hardware connection, a WiFi wireless communications link, a Bluetooth communications link, a wireless mobile telephone network link, among others. Workstations used in these arrangements are of the type common to nearly every desktop in every home or office. While a workstation alone is insufficient for interacting with vehicle event recorders of these inventions, a workstation with a ‘web browser’ or ‘Internet browser’ such as the Windows™ Internet Explorer is an ideal combination for providing access to vehicle event recorders so arranged. Of course, competing web browsers such as FireFox, Opera, Konqueror, Safari, Gecko, et cetera may be used with nearly identical effect. In all cases, these browsers will communicate with a vehicle event recorder because they all can read, parse and produce appropriate XML and HTML transactions. Thus, it is not necessary for users of these systems to buy, subscribe to, install, learn to use, maintain, update, re-install, among others, any proprietary software. Rather, these vehicle event recorders expose their functionality to any computer running a web browser of a user's choice.


In all prior art versions of similar systems, workstations are coupled to vehicle event recorders by way of proprietary application-specific software running on the workstation. Thus, it is impossible in those systems to manipulate and control a vehicle event recorder with a general purpose computer not having specially prepared programming. Data exchanges between a workstation application of the prior art and those vehicle event recorders typically include proprietary calls and file and object formats not compatible with general-purpose applications. In contrast, as the unique vehicle event recorders first presented here include a built-in web server, users have access to inner workings and settings of the vehicle event recorder by way of ‘http’ transactions. Further, simple data transfer including large video files may be taken up and handled by the same web server or by an accompanying ftp (file transfer protocol) server.


In some preferred versions, data communications link 4 is a common home network. A vehicle parked in the household garage becomes coupled to the home network by way of its proximity to a WiFi router for example. When a teenage driver returns home, mom instantly has access to information including video of her children's driving activity by way of her internet browser.


A top-level block diagram of a video event recorder is presented as FIG. 2. Video event recorders 21 of these inventions are comprised of the primary elements including: a video camera 22, a microprocessor 23, a web server 24, memory 25, and a communications port 26. A typical arrangement of a vehicle event recorder includes having these elements combined within a small plastic housing suitable for being mounted near or at a car windshield. It is preferable to install these devices on the interior portions of a vehicle in the passenger/occupant space. While the elements described together in combination form a vehicle event recorder head, sometimes reference herein is made to a ‘vehicle event recorder system’. When a head unit is coupled with a network or communications path which includes a workstation or other server remote from the vehicle event recorder head, the ensemble is considered a ‘vehicle event recorder system’.



FIG. 3 presents further detail with regard to the architecture of these vehicle event recorders 31. The camera field-of-view 32 may be arranged in ‘forward looking’ direction such that images of activity ahead of the vehicle are captured by the camera. Thus, it is said that the camera is coupled to environments about the vehicle. The video camera is further coupled electronically 33 to the microprocessor whereby the camera may transmit image data thereto. The microprocessor is further coupled electronically 34 to a memory which may be managed by the microprocessor to store image series associated with particular events such as traffic accidents. For example, upon receipt of signal from an event trigger 35, a short video series stored in managed loop memory 36, may be transferred to a more permanent stable memory, such as a high-capacity flash type memory 37. Finally, the web server 38 is coupled to a communications port 39 which permits the web server to interact with exterior computing systems.


In some preferred versions, cameras are arranged as forward looking cameras, others are rearward looking cameras, and still others as driver compartment view cameras. The number of cameras associated with a single vehicle recorder unit is meant to be not limited to one.


In preferred versions, a local memory is arranged to capture and preserve video information associated with a time prior to, and after, an important event. A managed loop memory includes an overwrite process which preserves data for a limited time and overwrites data as soon as it has aged in accordance with an overwrite scheme. Upon the occurrence of a ‘triggered event’—a car crash for example—the loop memory data is transferred to a buffer where it may be saved without subject to overwrite for an extended time.


An event trigger is arranged to detect a physical anomaly such as a high acceleration associated with a crash or other impact; alternatively a heavy swear or excessive braking maneuver; or even as a response to a panic button strike. The event trigger declares the occurrence of an incident and sets the memory to preserve all data associated with the incident or event.


A web server of these systems preferably includes preformed ‘web pages’ or sometimes ‘web forms’. In some advanced versions, these can be arranged in accordance with the Microsoft technology ASP.NET or sometimes referred to as Active Server Pages. These pages offer great latitude in providing web controls which are coupled to the internal systems of the vehicle event recorder systems. For example, the video camera may be controlled in that its contrast, brightness and intensity can be manipulated via such web controls on ASP.NET pages.


Because a car is easily coupled to a home computer network via a WiFi system, preferred versions include vehicle event recorder units having an output port fashioned as a WiFi or WiMax transceiver. Alternatives may include other radio type transceivers such as bluetooth, or optical type wireless links such as those which exploit infrared optical coupling. Of course, while not as convenient, it is entirely possible that a parked car be coupled to a home network via a hardwired Ethernet connection. A vehicle event recorder arranged with a common network interface card could be plugged in with hardwire (RJ45 type connector) to a local Ethernet system.


A web server is sometimes considered a part of the microprocessor or other computing platform, as it may be embodied as a computer code module running thereon. In FIG. 3, it is drawn separately from the microprocessor to bring emphasis to its importance. While known vehicle event recorders have been arranged with common microprocessors, it is first suggested here that a web server module be included and provide interface between a vehicle event recorder microprocessor and an external computing system. In this way, access to the microprocessor and vehicle event recorder subsystem functionality is provided to any computer system which address the web server with appropriate http transactions. That is, the web server is arranged to receive well-formed http requests (in example, http ‘GET’ commands), and further to provide responses constructed as http answers (http ‘POST’ responses).



FIG. 4 illustrates more clearly a particular example of a transaction between a user operating at a computer workstation 41, with installed Web browser 42, linked by a communications link to a vehicle event recorder 43 having integrated web server 44 installed in a common family automobile 45. From the workstation keyboard, the user 46 may inquire as to the state of the vehicle event recorder by sending an http request in the form of a GET type command 47. A GET command is fashioned as an http request and includes the URL of the source being addressed—the ‘web address’ of the vehicle event recorder; and perhaps an introduction web form or home/default web form. For example, a particular web page providing access to certain desired functionality may have a URL as follows: “http://192.168.1.8/camerasettings.aspx”. A GET command 47 including that URL is formed by and transmitted from the workstation's web browser to the vehicle event recorder's web server (having IP address 192.168.1.8). Upon receipt of the GET command, the web server responds by providing a POST action 48—an http response. The POST action may include transmission of an XML or/and HTML coded web page, which may be appropriately interpreted and displayed by the web browser and its graphical user interface or sometimes ‘window’ presented to the user on a system monitor 49.


To better explain what is meant by the phrase: ‘the state of the vehicle event recorder’ presented above, one might consider the following text in conjunction with the drawing presented as FIG. 5. FIG. 5 illustrates an example of a web page served by the web server of a vehicle event recorder. A web page is sometimes comprised a interactive objects sometimes and herein referred to as “web controls”. These include such controls commonly known as: ‘menus’; ‘toolbars’; ‘drop-down boxes’; ‘listboxes’; ‘radio buttons’; ‘checkboxes’; ‘sliders’; ‘textboxes’, among others. In FIG. 5, browser window 51 includes a field having a page title 52: “SmartDrive™ Camera Setup”. Further, the browser window includes a graphical element known as a menu or menu bar 53, and toolbar 54. Icons associated with various functionality are laid across a horizontal strip. When a user ‘clicks’ any of these icons, it sets into motion a computer code module to effect some operation. A very important aspect of any web browser include the address line 55. An address line may contain the URL or web address of the source currently displayed. This address may be typed-in manually by a user, or it may have been arrived at by way of a hyperlink from another page displayed previously in the browser window. Typical web browser windows further include other interactive objects such as a search engine interface including a drop-down box 56, a command button controls 57, slider controls 58, textboxes 59, an ‘option’ or radio buttons 510. From these web controls, a user interface is brought about and designed for interaction with the available functions in a vehicle event recorder hosting the associated web pages on its web server. A user may adjust a control and thereafter send the state of the web page to the vehicle event recorder unit. This is accomplished by ‘pointing’ and ‘clicking’ to change the control settings and then submitting the page or posting the page to the web server in the vehicle event recorder. In example, one may adjust the contrast of the camera by using slider control 58 and thereafter submit button 511 which results in the page being posted back to the web server and ultimately the contrast being improved. A careful observer will note that each of command button controls 57 may lead to a different association of certain functions in groups. The functions of the camera are grouped into those which are displayed in that field 512. If the command button associated with system functions is chosen, then the available functions in field may change without appreciable change to the general form of the page. FIG. 6 illustrates.


A group of controls associated with system function is presented in the diagram of FIG. 6 which is a graphical user interface embodied as a web page 61. Command button control 62 associated with the system settings is called at the browser by way of this page's URL http://192.168.1.8/systemsettings.htm 63. The page permits a user to adjust the IP address 64 of the vehicle event recorder at textbox 65. A user may choose a particular enhanced timeline at a drop down box 66 as prescribed by those available in a managed loop memory system. User data/profile can be entered at textbox 67 and command button 68 can be used to save a username to a memory in the vehicle event recorder. Finally, a trigger threshold can be set on a continuous slider control 69 to make an event trigger in the vehicle event recorder either more or less sensitive. In this way, a user at a remote computer running a simple internet browser makes adjustments directly to a vehicle event recorder installed in a vehicle.


While sometimes these web servers are arranged with pre-programmed ‘web page’ objects addressable via web request actions, they may also include programmed modules known as web services. These functions, properties and events, do not have a user interface associated with them, however they include transaction interface which permits their being addressed via TCP/IP web requests. These functions, properties and events may be coupled to subsystems of the vehicle event recorder head. For example, an ‘authorized users list’ may be adjusted whereby log-on actions by users are enabled/disabled. This web service may be taken up automatically in response to some condition being met. Therefore, without user interaction via a web page, but rather by purely automated processes, i.e. web services, these vehicle event recorder systems may be adjusted and otherwise manipulated.


Best modes of these inventions are illustrated in FIG. 7. A vehicle 71 is prepared with a vehicle event recorder unit 72 having therewith an integrated web server 73. A communications port, in example a WiFi transceiver 74 permits the vehicle event recorder to connect wirelessly to a home network by way of complimentary WiFi transceiver/router 75. When the car enters a zone or space 76 served by the transceiver/router, the vehicle event recorder web server is accessible by a user 77 operating workstation 78 running a web browser 79 program. The user may adjust, upload, download, browse, and otherwise interact with the vehicle event record and data stored on the vehicle event recorder.


In special advanced versions, vehicle event recorders additionally include modules other than a simple web server. For example, an vehicle event recorder may additionally include a file exchange and e-mail server systems. FIG. 8 shows graphically a vehicle event recorder 81 for use in conjunction with vehicle 82, the vehicle event recorder comprising an integrated web server 83, a file transport protocol ftp server 84, and an e-mail (SMTP) server 85. The web browser 86 at a user workstation 87 similarly communicates with these elements in a conventional way to bring about these functions in a vehicle event recorder. In this way, automatic triggers can be arranged in the vehicle event recorder such that it can send e-mail messages in response to certain events having been ‘fired’ in the normal processing of the system. When something of interest occurs, an e-mail message is prepared and queued. On the next occasion where the vehicle event recorder is connected to the internet, the SMTP sends the e-mail to the intended recipient. In a similar fashion, the vehicle event recorder ftp server operates to send and receive data files.


While most preferred versions are arranged with the primary objective being a home, family or small number user local systems, these inventions are also meant to include as a special case the need for remote operation. A private home computer network can be arranged with a public port which exposes certain services through a firewall to the public internet. In this way, a vacationing parent can still have a look at the vehicle use records from afar. Vehicle 91 equipped with vehicle event recorder 92 having integrated web server communicates with local radio 93 as it enters communications space 94. the mere act of the vehicle entering 95 the space causes the vehicle event recorder to become connected to the network which may include the Internet. Accordingly, a communications link 96 of many thousands of miles is possible whereby a user 97 working on any workstation 98 equipped with a browser can address the web, file and mail servers of the remotely located vehicle event recorder.


One will now fully appreciate how a vehicle event recorder having an integrated web server is used to provide simple user access to operation and function of these systems. Although the present inventions have been described in considerable detail with clear and concise language and with reference to certain preferred versions thereof including best modes anticipated by the inventors, other versions are possible. Therefore, the spirit and scope of the invention should not be limited by the description of the preferred versions contained therein, but rather by the claims appended hereto.

Claims
  • 1. A vehicle event recorder comprising: a video camera configured to acquire visual information representing a vehicle environment, the vehicle environment including spaces in and around an interior and an exterior of the vehicle, the video camera configured to acquire the visual information based on one or more camera control settings;a memory configured to electronically store information;a microprocessor configured to effectuate storage of the visual information in the memory; anda web server module configured to: facilitate wireless communication of the visual information to a remotely located computing device associated with a user, wherein communicating the information includes generating one or more web pages that present the visual information for browsing by the user via a web browser of the computing device; andadjust the camera control settings based on control information received from the user via the remotely located computing device, the web server module configured such that the one or more web pages are configured to receive entry and/or selection of the control information from the user.
  • 2. The vehicle event recorder of claim 1, wherein the video camera is configured such that the camera control settings include one or more of a zoom level, camera brightness, camera contrast, camera intensity, camera resolution, camera frame rate, or camera image color.
  • 3. The vehicle event recorder of claim 1, wherein said web pages are further characterized as ASP.NET type active server pages.
  • 4. The vehicle event recorder of claim 1, wherein the memory comprises a managed loop memory configured to store the visual information for a temporary period of time, andwherein the web server module is configured to adjust the temporary period of time based on timing information received from the user via the remotely located computing device, the web server module configured such that the one or more web pages are configured to receive entry and/or selection of the timing information from the user.
  • 5. The vehicle event recorder of claim 1, further comprising an event trigger configured to detect an event, the event including one or more of an impact, rapid acceleration, rapid deceleration, a swerve, or hard braking, and cause a data transfer from the managed loop memory to a buffer memory, the event detected responsive to an event parameter breaching an event trigger threshold level, wherein the web server module is configured to adjust the event trigger threshold level based on threshold information received from the user via the remotely located computing device, the web server module configured such that the one or more web pages are configured to receive entry and/or selection of threshold information from the user.
  • 6. The vehicle event recorder of claim 1, wherein the web server module further comprises prearranged web services comprising programming modules which may be invoked via a TCP/IP call from a web browser.
  • 7. The vehicle event recorder of claim 1, further comprising a file transfer protocol server.
  • 8. The vehicle event recorder of claim 1, further comprising a simple mail transfer protocol server.
  • 9. The vehicle event recorder of claim 1, further comprising a communications transceiver characterized as a WiFi or WiMax compliant transceiver, and wherein the web server module communicates with the remotely located computing device via the communications transceiver.
  • 10. The vehicle event recorder of claim 9, wherein the communications transceiver is a wireless transceiver.
  • 11. The vehicle event recorder of claim 1, further comprising: a data transmission network;the remotely located computing device; andthe web browser;wherein the data transmission network supports packet traffic via TCP/IP, and wherein the web browser is embodied as software running on the remotely located computing device.
  • 12. The vehicle event recorders of claim 11, wherein the data transmission network includes a portion characterized as a local area network LAN and/or a home type network.
  • 13. The vehicle event recorder of claim 12, wherein the data transmission network further comprises at least one router operable for directing data traffic in accordance with Internet protocol.
  • 14. The vehicle event recorder of claim 13, wherein the router is a WiFi and/or WiMax router and a vehicle event recorder communications transceiver is a complementary WiFi and/or WiMax transceiver.
  • 15. The vehicle event recorder of claim 12, wherein the data transmission network is a compound network comprising a wired portion and a wireless portion.
  • 16. The vehicle event recorders of claim 15, wherein the data transmission network further comprises a protocol gateway interface between a TCP/IP network and a mobile cellular communications network.
US Referenced Citations (458)
Number Name Date Kind
2943141 Knight Jun 1960 A
3634866 Meyer Jan 1972 A
3781824 Caiati et al. Dec 1973 A
3812287 Lemelson May 1974 A
3885090 Rosenbaum May 1975 A
3992656 Joy Nov 1976 A
4054752 Dennis, Jr. et al. Oct 1977 A
4271358 Schwarz Jun 1981 A
4280151 Tsunekawa et al. Jul 1981 A
4281354 Conte Jul 1981 A
4401976 Stadelmayr Aug 1983 A
4409670 Herndon et al. Oct 1983 A
4420773 Toyoda et al. Dec 1983 A
4425097 Owens Jan 1984 A
4456931 Toyoda et al. Jun 1984 A
4489351 D'Alayer de Costemore d'Arc Dec 1984 A
4496995 Colles et al. Jan 1985 A
4500868 Tokitsu et al. Feb 1985 A
4533962 Decker et al. Aug 1985 A
4558379 Hutter et al. Dec 1985 A
4593313 Nagasaki et al. Jun 1986 A
4621335 Bluish et al. Nov 1986 A
4625210 Sagl Nov 1986 A
4630110 Cotton et al. Dec 1986 A
4632348 Keesling et al. Dec 1986 A
4638289 Zottnik Jan 1987 A
4646241 Ratchford et al. Feb 1987 A
4651143 Yamanaka Mar 1987 A
4718685 Kawabe et al. Jan 1988 A
4758888 Lapidot Jul 1988 A
4763745 Eto et al. Aug 1988 A
4785474 Bernstein et al. Nov 1988 A
4789904 Peterson Dec 1988 A
4794566 Richards et al. Dec 1988 A
4804937 Barbiaux et al. Feb 1989 A
4806931 Nelson Feb 1989 A
4814896 Heitzman et al. Mar 1989 A
4837628 Sasaki Jun 1989 A
4839631 Tsuji Jun 1989 A
4843463 Michetti Jun 1989 A
4843578 Wade Jun 1989 A
4876597 Roy et al. Oct 1989 A
4883349 Mittelhauser Nov 1989 A
4896855 Furnish Jan 1990 A
4930742 Schofield et al. Jun 1990 A
4936533 Adams et al. Jun 1990 A
4939652 Steiner Jul 1990 A
4942464 Milatz Jul 1990 A
4945244 Castleman Jul 1990 A
4949186 Peterson Aug 1990 A
4980913 Skret Dec 1990 A
4987541 Levente et al. Jan 1991 A
4992943 McCracken Feb 1991 A
5012335 Cohodar Apr 1991 A
5027104 Reid Jun 1991 A
5050166 Cantoni et al. Sep 1991 A
5056056 Gustin Oct 1991 A
5057820 Markson et al. Oct 1991 A
5096287 Kakinami et al. Mar 1992 A
5100095 Haan et al. Mar 1992 A
5111289 Lucas et al. May 1992 A
5140434 Van Blessinger et al. Aug 1992 A
5140436 Blessinger Aug 1992 A
5144661 Shamosh et al. Sep 1992 A
5178448 Adams et al. Jan 1993 A
5196938 Blessinger Mar 1993 A
5223844 Mansell et al. Jun 1993 A
5262813 Scharton Nov 1993 A
5308247 Dyrdek May 1994 A
5309485 Chao May 1994 A
5311197 Sorden et al. May 1994 A
5321753 Gritton Jun 1994 A
5327288 Wellington et al. Jul 1994 A
5330149 Haan et al. Jul 1994 A
5343527 Moore Aug 1994 A
5353023 Mitsugi Oct 1994 A
5361326 Aparicio, IV et al. Nov 1994 A
5387926 Bellan Feb 1995 A
5388045 Kamiya et al. Feb 1995 A
5404330 Lee et al. Apr 1995 A
5408330 Squicciarini et al. Apr 1995 A
5422543 Weinberg Jun 1995 A
5430431 Nelson Jul 1995 A
5430432 Camhi et al. Jul 1995 A
5435184 Pineroli et al. Jul 1995 A
5445024 Riley, Jr. et al. Aug 1995 A
5445027 Zorner Aug 1995 A
5446659 Yamawaki Aug 1995 A
5455625 Englander Oct 1995 A
5455716 Suman et al. Oct 1995 A
5465079 Bouchard et al. Nov 1995 A
5473729 Bryant et al. Dec 1995 A
5477141 Nather et al. Dec 1995 A
5495242 Kick et al. Feb 1996 A
5495243 McKenna Feb 1996 A
5497419 Hill Mar 1996 A
5499182 Ousborne Mar 1996 A
5504482 Schreder Apr 1996 A
5515285 Garrett, Sr. et al. May 1996 A
5521633 Nakajima et al. May 1996 A
5523811 Wada et al. Jun 1996 A
5526269 Ishibashi et al. Jun 1996 A
5530420 Tsuchiya et al. Jun 1996 A
5537156 Katayama Jul 1996 A
5539454 Williams Jul 1996 A
5541590 Nishio Jul 1996 A
5544060 Fujii et al. Aug 1996 A
5546191 Hibi et al. Aug 1996 A
5546305 Kondo Aug 1996 A
5548273 Nicol et al. Aug 1996 A
5552990 Ihara et al. Sep 1996 A
5559496 Dubats Sep 1996 A
5568211 Bamford Oct 1996 A
5570127 Schmidt Oct 1996 A
5574424 Nguyen Nov 1996 A
5574443 Hsieh Nov 1996 A
D376571 Kokat Dec 1996 S
5581464 Woll et al. Dec 1996 A
5586130 Doyle Dec 1996 A
5590948 Moreno Jan 1997 A
5596382 Bamford Jan 1997 A
5600775 King et al. Feb 1997 A
5610580 Lai Mar 1997 A
5612686 Takano et al. Mar 1997 A
5631638 Kaspar et al. May 1997 A
5638273 Coiner et al. Jun 1997 A
5642106 Hancock et al. Jun 1997 A
5646856 Kaesser Jul 1997 A
5652706 Morimoto et al. Jul 1997 A
RE35590 Bezos et al. Aug 1997 E
5654892 Fujii et al. Aug 1997 A
5659355 Barron et al. Aug 1997 A
5666120 Kline et al. Sep 1997 A
5667176 Zamarripa et al. Sep 1997 A
5669698 Veldman et al. Sep 1997 A
5671451 Takahashi et al. Sep 1997 A
5677979 Squicciarini et al. Oct 1997 A
5680117 Arai et al. Oct 1997 A
5680123 Lee Oct 1997 A
5686889 Hillis Nov 1997 A
5689442 Swanson et al. Nov 1997 A
5696705 Zykan Dec 1997 A
5706362 Yabe Jan 1998 A
5712679 Coles Jan 1998 A
5717456 Rudt et al. Feb 1998 A
5719554 Gagnon Feb 1998 A
5781145 Williams et al. Jul 1998 A
5784021 Oliva Jul 1998 A
5784521 Nakatani et al. Jul 1998 A
5790403 Nakayama Aug 1998 A
5790973 Blaker et al. Aug 1998 A
5793420 Schmidt Aug 1998 A
5793985 Natarajan et al. Aug 1998 A
5794165 Minowa et al. Aug 1998 A
5797134 McMillan et al. Aug 1998 A
5798458 Monroe Aug 1998 A
5800040 Santo Sep 1998 A
5802545 Coverdill Sep 1998 A
5802727 Blank et al. Sep 1998 A
5815071 Doyle Sep 1998 A
5815093 Kikinis Sep 1998 A
5825284 Dunwoody et al. Oct 1998 A
5825412 Hobson et al. Oct 1998 A
5844505 Van Ryzin Dec 1998 A
5896167 Omae et al. Apr 1999 A
5897606 Miura et al. Apr 1999 A
5899956 Chan May 1999 A
5901806 Takahashi May 1999 A
5914748 Parulski et al. Jun 1999 A
5926210 Hackett et al. Jul 1999 A
5928291 Jenkins et al. Jul 1999 A
5946404 Bakshi et al. Aug 1999 A
5948038 Daly Sep 1999 A
5978017 Tino Nov 1999 A
6002326 Turner Dec 1999 A
6006148 Strong Dec 1999 A
6008723 Yassan Dec 1999 A
6008841 Charlson Dec 1999 A
6009370 Minowa et al. Dec 1999 A
6011492 Garesche Jan 2000 A
6028528 Lorenzetti et al. Feb 2000 A
6037860 Zander et al. Mar 2000 A
6037977 Peterson Mar 2000 A
6049079 Noordam et al. Apr 2000 A
6064792 Fox et al. May 2000 A
6084870 Wooten et al. Jul 2000 A
6088635 Cox et al. Jul 2000 A
6092193 Loomis et al. Jul 2000 A
6100811 Hsu et al. Aug 2000 A
6111254 Eden Aug 2000 A
6118768 Bhatia et al. Sep 2000 A
6122738 Millard Sep 2000 A
6141611 Mackey et al. Oct 2000 A
6144296 Ishida et al. Nov 2000 A
6151065 Steed et al. Nov 2000 A
6163338 Johnson et al. Dec 2000 A
6167186 Kawasaki et al. Dec 2000 A
6181373 Coles Jan 2001 B1
6185490 Ferguson Feb 2001 B1
6200139 Clapper Mar 2001 B1
6211907 Seaman et al. Apr 2001 B1
6218960 Ishikawa et al. Apr 2001 B1
6246933 Bague Jun 2001 B1
6252544 Hoffberg Jun 2001 B1
6253129 Jenkins et al. Jun 2001 B1
6298290 Abe et al. Oct 2001 B1
6333759 Mazzilli Dec 2001 B1
6337622 Sugano Jan 2002 B1
6353734 Wright et al. Mar 2002 B1
6389339 Just May 2002 B1
6389340 Rayner May 2002 B1
6405112 Rayner Jun 2002 B1
6405132 Breed Jun 2002 B1
6408232 Cannon et al. Jun 2002 B1
6411874 Morgan et al. Jun 2002 B2
6421080 Lambert Jul 2002 B1
6449540 Rayner Sep 2002 B1
6472771 Frese et al. Oct 2002 B1
6518881 Monroe Feb 2003 B2
6535804 Chun Mar 2003 B1
6556905 Mittelsteadt et al. Apr 2003 B1
6559769 Anthony et al. May 2003 B2
6575902 Burton Jun 2003 B1
6611740 Lowrey et al. Aug 2003 B2
6611755 Coffee et al. Aug 2003 B1
6624611 Kirmuss Sep 2003 B2
6679702 Rau Jan 2004 B1
6684137 Takagi et al. Jan 2004 B2
6714894 Tobey et al. Mar 2004 B1
6718239 Rayner Apr 2004 B2
6728612 Carver et al. Apr 2004 B1
6732031 Lightner et al. May 2004 B1
6732032 Banet et al. May 2004 B1
6735503 Ames May 2004 B2
6737954 Chainer et al. May 2004 B2
6739078 Morley et al. May 2004 B2
6760757 Lundberg et al. Jul 2004 B1
6795111 Mazzilli Sep 2004 B1
6810362 Adachi et al. Oct 2004 B2
6812831 Ikeda Nov 2004 B2
6819989 Maeda et al. Nov 2004 B2
6831556 Boykin Dec 2004 B1
6832141 Skeen et al. Dec 2004 B2
6842762 Raithel et al. Jan 2005 B2
6850823 Eun et al. Feb 2005 B2
6859695 Klausner Feb 2005 B2
6865457 Mittelsteadt et al. Mar 2005 B1
6873261 Anthony et al. Mar 2005 B2
6895248 Akyol et al. May 2005 B1
6898492 de Leon et al. May 2005 B2
6919823 Lock Jul 2005 B1
6928348 Lightner et al. Aug 2005 B1
6947817 Diem Sep 2005 B2
6950122 Mirabile Sep 2005 B1
6954223 Miyazawa et al. Oct 2005 B2
6988034 Marlatt et al. Jan 2006 B1
7012632 Freeman et al. Mar 2006 B2
7023333 Blanco et al. Apr 2006 B2
7082382 Rose et al. Jul 2006 B1
7098812 Hirota Aug 2006 B2
7100190 Johnson et al. Aug 2006 B2
7119832 Blanco et al. Oct 2006 B2
7155321 Bromley Dec 2006 B2
7209833 Isaji et al. Apr 2007 B2
7265663 Steele Sep 2007 B2
7317974 Luskin et al. Jan 2008 B2
7348895 Lagassey Mar 2008 B2
7370261 Winarski et al. May 2008 B2
7382933 Dorai et al. Jun 2008 B2
7386376 Basir et al. Jun 2008 B2
7389178 Raz et al. Jun 2008 B2
7457693 Olsen et al. Nov 2008 B2
7561054 Raz et al. Jul 2009 B2
7702442 Takenaka Apr 2010 B2
7725216 Kim May 2010 B2
7768548 Silvernail et al. Aug 2010 B2
7821421 Tamir et al. Oct 2010 B2
7853376 Peng Dec 2010 B2
7974748 Goerick et al. Jul 2011 B2
8113844 Huang Feb 2012 B2
8140358 Ling et al. Mar 2012 B1
8314708 Gunderson et al. Nov 2012 B2
8538696 Cassanova Sep 2013 B1
8635557 Geise Jan 2014 B2
20010005804 Rayner Jun 2001 A1
20020019689 Harrison et al. Feb 2002 A1
20020035422 Sasaki Mar 2002 A1
20020044225 Rakib Apr 2002 A1
20020059453 Eriksson et al. May 2002 A1
20020091473 Gardner et al. Jul 2002 A1
20020111725 Burge Aug 2002 A1
20020118206 Knittel Aug 2002 A1
20020135679 Scaman Sep 2002 A1
20020138587 Koehler Sep 2002 A1
20020163532 Thomas et al. Nov 2002 A1
20020169529 Kim Nov 2002 A1
20020169530 Laguer-Diaz et al. Nov 2002 A1
20020183905 Maeda et al. Dec 2002 A1
20030016753 Kim et al. Jan 2003 A1
20030028298 Macky et al. Feb 2003 A1
20030065805 Barnes Apr 2003 A1
20030079041 Parrella et al. Apr 2003 A1
20030080713 Kirmuss May 2003 A1
20030080878 Kirmuss May 2003 A1
20030081121 Kirmuss May 2003 A1
20030081122 Kirmuss May 2003 A1
20030081127 Kirmuss May 2003 A1
20030081128 Kirmuss May 2003 A1
20030081934 Kirmuss May 2003 A1
20030081935 Kirmuss May 2003 A1
20030095688 Kirmuss May 2003 A1
20030125854 Kawasaki et al. Jul 2003 A1
20030144775 Klausner Jul 2003 A1
20030154009 Basir et al. Aug 2003 A1
20030158638 Yakes et al. Aug 2003 A1
20030187704 Hashiguchi et al. Oct 2003 A1
20030191568 Breed Oct 2003 A1
20030214585 Bakewell et al. Nov 2003 A1
20030220835 Barnes Nov 2003 A1
20040039503 Doyle Feb 2004 A1
20040044452 Bauer et al. Mar 2004 A1
20040054513 Laird et al. Mar 2004 A1
20040083041 Skeen et al. Apr 2004 A1
20040088090 Wee May 2004 A1
20040103008 Wahlben et al. May 2004 A1
20040103010 Wahlben et al. May 2004 A1
20040111189 Miyazawa Jun 2004 A1
20040138794 Saito et al. Jul 2004 A1
20040153244 Kellum Aug 2004 A1
20040153362 Bauer et al. Aug 2004 A1
20040179600 Wells et al. Sep 2004 A1
20040181326 Adams et al. Sep 2004 A1
20040184548 Kerbiriou et al. Sep 2004 A1
20040209594 Naboulsi Oct 2004 A1
20040210353 Rice Oct 2004 A1
20040236474 Chowdhary et al. Nov 2004 A1
20040243308 Irish et al. Dec 2004 A1
20040243668 Harjanto Dec 2004 A1
20040254698 Hubbard et al. Dec 2004 A1
20050021199 Zimmerman et al. Jan 2005 A1
20050060070 Kapolka et al. Mar 2005 A1
20050060071 Winner Mar 2005 A1
20050073585 Ettinger et al. Apr 2005 A1
20050088291 Blanco et al. Apr 2005 A1
20050131585 Luskin et al. Jun 2005 A1
20050131595 Luskin et al. Jun 2005 A1
20050136949 Barnes Jun 2005 A1
20050137757 Phelan et al. Jun 2005 A1
20050137796 Gumpinger Jun 2005 A1
20050146458 Carmichael et al. Jul 2005 A1
20050149238 Stefani et al. Jul 2005 A1
20050159964 Sonnenrein et al. Jul 2005 A1
20050166258 Vasilevsky et al. Jul 2005 A1
20050171692 Hamblen et al. Aug 2005 A1
20050182824 Cotte Aug 2005 A1
20050185936 Lao et al. Aug 2005 A9
20050197748 Holst et al. Sep 2005 A1
20050200714 Marchese Sep 2005 A1
20050203683 Olsen et al. Sep 2005 A1
20050212920 Evans et al. Sep 2005 A1
20050258942 Manasseh et al. Nov 2005 A1
20060007151 Ram Jan 2006 A1
20060011399 Brockway et al. Jan 2006 A1
20060015233 Olsen et al. Jan 2006 A1
20060022842 Zoladek et al. Feb 2006 A1
20060025897 Shostak et al. Feb 2006 A1
20060040239 Cummins et al. Feb 2006 A1
20060053038 Warren et al. Mar 2006 A1
20060055521 Blanco et al. Mar 2006 A1
20060057543 Roald Mar 2006 A1
20060058950 Kato et al. Mar 2006 A1
20060072792 Toda et al. Apr 2006 A1
20060078853 Lanktree Apr 2006 A1
20060092043 Lagassey May 2006 A1
20060095175 deWaal et al. May 2006 A1
20060095199 Lagassey May 2006 A1
20060095349 Morgan et al. May 2006 A1
20060103127 Lie et al. May 2006 A1
20060106514 Liebl et al. May 2006 A1
20060142913 Coffee et al. Jun 2006 A1
20060161960 Benoit Jul 2006 A1
20060168271 Pabari et al. Jul 2006 A1
20060209090 Kelly et al. Sep 2006 A1
20060209840 Paatela et al. Sep 2006 A1
20060212195 Veith et al. Sep 2006 A1
20060242680 Johnson et al. Oct 2006 A1
20060253307 Warren et al. Nov 2006 A1
20070001831 Raz et al. Jan 2007 A1
20070005404 Raz et al. Jan 2007 A1
20070027583 Tamir et al. Feb 2007 A1
20070027726 Warren et al. Feb 2007 A1
20070120948 Fujioka et al. May 2007 A1
20070124332 Ballesty et al. May 2007 A1
20070132773 Plante Jun 2007 A1
20070135979 Plante Jun 2007 A1
20070135980 Plante Jun 2007 A1
20070136078 Plante Jun 2007 A1
20070143499 Chang Jun 2007 A1
20070150140 Seymour Jun 2007 A1
20070173994 Kubo et al. Jul 2007 A1
20070183635 Weidhaas Aug 2007 A1
20070208494 Chapman et al. Sep 2007 A1
20070216521 Guensler et al. Sep 2007 A1
20070219685 Plante Sep 2007 A1
20070219686 Plante Sep 2007 A1
20070241874 Okpysh et al. Oct 2007 A1
20070257781 Denson Nov 2007 A1
20070257782 Etcheson Nov 2007 A1
20070257804 Gunderson et al. Nov 2007 A1
20070257815 Gunderson et al. Nov 2007 A1
20070260677 DeMarco et al. Nov 2007 A1
20070268158 Gunderson et al. Nov 2007 A1
20070271105 Gunderson et al. Nov 2007 A1
20070273480 Burkman et al. Nov 2007 A1
20070279214 Buehler Dec 2007 A1
20070299612 Kimura et al. Dec 2007 A1
20080147267 Plante et al. Jun 2008 A1
20080157510 Breed et al. Jul 2008 A1
20080167775 Kuttenberger et al. Jul 2008 A1
20080169914 Albertson et al. Jul 2008 A1
20080177436 Fortson Jul 2008 A1
20080252485 Lagassey Oct 2008 A1
20080269978 Shirole Oct 2008 A1
20080281485 Plante Nov 2008 A1
20080309762 Howard et al. Dec 2008 A1
20090043971 Kim Feb 2009 A1
20090216775 Ratliff et al. Aug 2009 A1
20090224869 Baker et al. Sep 2009 A1
20100045451 Periwal Feb 2010 A1
20100063672 Anderson Mar 2010 A1
20100063850 Daniel Mar 2010 A1
20100070175 Soulchin et al. Mar 2010 A1
20100085193 Boss et al. Apr 2010 A1
20100087984 Joseph Apr 2010 A1
20100157061 Katsman et al. Jun 2010 A1
20100220892 Kawakubo Sep 2010 A1
20100250021 Cook et al. Sep 2010 A1
20100268415 Ishikawa Oct 2010 A1
20110035139 Konlditslotis et al. Feb 2011 A1
20110043624 Haug Feb 2011 A1
20110060496 Nielsen et al. Mar 2011 A1
20110077028 Wilkes et al. Mar 2011 A1
20110091079 Yu-Song et al. Apr 2011 A1
20110093159 Boling et al. Apr 2011 A1
20110121960 Tsai May 2011 A1
20110125365 Larschan et al. May 2011 A1
20110130916 Mayer Jun 2011 A1
20110173015 Chapman et al. Jul 2011 A1
20110224891 Iwuchukwu Sep 2011 A1
20110283223 Vaittinen et al. Nov 2011 A1
20110304446 Basson et al. Dec 2011 A1
20120035788 Trepagnier et al. Feb 2012 A1
20120046803 Inou et al. Feb 2012 A1
20120071140 Oesterling et al. Mar 2012 A1
20130006469 Green et al. Jan 2013 A1
20130030660 Fujimoto Jan 2013 A1
20130332004 Gompert et al. Dec 2013 A1
20140226010 Molin Aug 2014 A1
Foreign Referenced Citations (34)
Number Date Country
2692415 Aug 2011 CA
4416991 Nov 1995 DE
0848270 May 1998 EP
1355278 Oct 2003 EP
1427165 Jun 2004 EP
1818873 Aug 2007 EP
2268608 Jan 1994 GB
2447184 Jun 2011 GB
58085110 May 1983 JP
62091092 Apr 1987 JP
62166135 Jul 1987 JP
02056197 Feb 1990 JP
04257189 Sep 1992 JP
05137144 Jun 1993 JP
5294188 Nov 1993 JP
08124069 May 1996 JP
09163357 Jun 1997 JP
09272399 Oct 1997 JP
10076880 Mar 1998 JP
2002191017 Jul 2002 JP
WO 8809023 Nov 1988 WO
WO 9005076 May 1990 WO
WO 9427844 Dec 1994 WO
WO 9600957 Jan 1996 WO
WO 9701246 Jan 1997 WO
WO 9726750 Jul 1997 WO
WO 9937503 Jul 1999 WO
WO 9940545 Aug 1999 WO
WO 9962741 Dec 1999 WO
WO 0007150 Feb 2000 WO
WO 0048033 Aug 2000 WO
WO 0077620 Dec 2000 WO
WO 0125054 Apr 2001 WO
WO 2011055743 May 2011 WO
Non-Patent Literature Citations (110)
Entry
1/0 Port Racing Supplies' website discloses using Traqmate's Data Acquisition with Video Overlay system in conjunction with professional driver coaching sessions (available at http://www.ioportracing.com/Merchant2/merchant.mvc?Screen=CTGY&Category—Code=coaching)., printed from site on Jan. 11, 2012.
Adaptec published and sold Its VideoOh! DVD software USB 2.0 Edition in at least Jan. 24, 2003.
“Ambulance Companies Use Video Technology to Improve Driving Behavior”, Ambulance Industry Journal, Spring 2003.
“Amended Complaint for Patent Infringement, Trade Secret Misappropriation, Unfair Competition and Conversion” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California, Document 34, filed Oct. 20, 2011, pp. 1-15.
DriveCam, Inc.'s Infringement Contentions Exhibit A, U.S. Patent 6,389,340, Document 34.1, Oct. 20, 2011.
DriveCam, Inc.'s Infringement Contentions Exhibit B, U.S. Patent 7,804,426, Document 34.2, Oct. 20, 2011.
DriveCam, Inc.'s Infringement Contentions Exhibit C, U.S. Patent 7,659,827, Document 34.3, Oct. 20, 2011.
DriveCam, Inc.'s Infringement Contentions Exhibit D, Document 34.4, Oct. 20, 2011.
“Answer to Amended Complaint; Counterclaims; and Demand for Jury Trial” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Document 47, filed Dec. 13, 2011, pp. 1-15.
U.S. Appl. No. 11/296,906, filed Dec. 8, 2005, File History.
U.S. Appl. No. 11/297,669, filed Dec. 8, 2005, File History.
U.S. Appl. No. 11/298,069, filed Dec. 9, 2005, File History.
U.S. Appl. No. 11/299,028, filed Dec. 9, 2005, File History.
U.S. Appl. No. 11/593,659, filed Nov. 7, 2006, File History.
U.S. Appl. No. 11/593,682, filed Nov. 7, 2006, File History.
U.S. Appl. No. 11/595,015, filed Nov. 9, 2006, File History.
U.S. Appl. No. 11/637,754, filed Dec. 13, 2006, File History.
U.S. Appl. No. 11/637,755, filed Dec. 13, 2006, File History.
U.S. Appl. No. 12/691,639, entitled “Driver Risk Assessment System and Method Employing Selectively Automatic Event Scoring”, filed Jan. 21, 2010, File History.
Bill Siuru, “DriveCam Could Save You Big Bucks”, Land Line Magazine, May-Jun. 2000.
Bill, “DriveCam—FAQ”, Dec. 12, 2003.
Chris Woodyard, “Shuttles save with DriveCam”, Dec. 9, 2003.
Dan Carr, Flash Video template: Video Presentation with Navigation, Jan. 16, 2006.
David Cullen, “Getting a real eyeful”, Fleet Owner Magazine, Feb. 2002.
David Maher, “DriveCam Brochure Folder”, Jun. 6, 2005.
David Vogeleer et al., Macromedia Flash Professional 8UNLEASHED (Sams Oct. 12, 2005).
Del Lisk, “DriveCam Training Handout Ver4”, Feb. 3, 2005.
DriveCam Extrinsic Evidence with Patent LR 4.1.a Disclosures, Nov. 8, 2011.
“DriveCam—Illuminator Data Sheet”, Oct. 2, 2004.
“DriveCam Driving Feedback System”, Mar. 15, 2004.
Drivecam, Inc., User's Manual for Drivecam Video Systems' Hindsight 20/20 Software Version 4.0 S002751-S002804 (2003).
“DriveCam, Inc's Disclosure of Responsive Constructions and Extrinsic Evidence Pursuant to Patent L.R. 4.1.c & 4.1d” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California. Nov. 15, 2011.
“DriveCam, Inc's Disclosure of Proposed Constructions and Extrinsic Evidence Pursuant to Patent L.R. 4.1.a & 4.1.b” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California. Nov. 8, 2011.
Drivecam.com as retrieved by the Internet Wayback Machine as of Mar. 5, 2005.
“DriveCam's Disclosure of Asserted Claims and Preliminary Infringement Contentions” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California. Aug. 19, 2011.
“Driver Feedback System”, Jun. 12, 2001.
“First Amended Answer to Amended Complaint and First Amended Counterclaims; and Demand for Jury Trial” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Document 53, filed Dec. 20, 2011, pp. 1-48.
“First Amended Answer to Amended Complaint and First Amended Counterclaims; and Demand for Jury Trial” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Exhibit A, Document 55, filed Jan. 3, 2012, pp. 49-103.
Franke, U., et al., Autonomous Driving Goes Downtown, IEEE Intelligent Systems, 13(6):40-48 (1988); Digital Object Identifier 10.1109/5254.736001.
Gallagher, B., et al., Wireless Communications for Vehicle Safety: Radio Link Performance and Wireless Connectivity Methods, Vehicular Technology Magazine, IEEE, 1(4):4-24 (2006); Digital Object Identifier 10.1109/MVT.2006.343641.
Gandhi, T., et al., Pedestrian Protection Systems: Issues, Survey, and Challenges, IEEE Transactions on Intelligent Transportation Systems, 8(3):413-430 (2007); Digital Object Identifier 10.1109/TITS.2007.903444.
Gary and Sophia Rayner, Final Report for Innovations Deserving Exploratory Analysis (IDEA) Intelligent Transportation Systems (ITS) Programs' Project 84, I-Witness Black Box Recorder, San Diego, CA, Nov. 2001.
GE published its VCR Users Guide for Model VG4255 in 1995.
Glenn Oster, “HindSight 20/20 v4.0 Software Installation”, 1 of 2, Jun. 20, 2003.
Glenn Oster, “HindSight 20/20 v4.0 Software Installation”, 2 of 2, Jun. 20, 2003.
Glenn Oster, “Illuminator Installation”, Oct. 3, 2004.
Hans Fantel, Video; Search Methods Make a Difference In Picking VCR's, NY Times, Aug. 13, 1989.
“HindSight v4.0 Users Guide”, DriveCam Video Systems, Apr. 25, 2005.
“Interior Camera Data Sheet”, Oct. 26, 2001.
International Search Report and Written Opinion issued in PCT/US07/68329 on Mar. 3, 2008.
International Search Report and Written Opinion issued in PCT/US07/68332 on Mar. 3, 2008.
International Search Report and Written Opinion issued in PCT/US07/68334 on Mar. 5, 2008.
International Search Report and Written Opinion issued in PCT/US07/68328 on Oct. 15, 2007.
International Seach Report and Written Opinion issued in PCT/US0/68325 on Feb. 27, 2008.
International Search Report and Written Opinion issued in PCT/US07/68333 on Mar. 5, 2008.
Invitation to Pay Additional Fees with Communication of Partial International Search issued in PCT/US2010/0222012 on Jul. 21, 2010.
J. Gallagher, “Lancer Recommends Tech Tool”, Insurance and Technology Magazine, Feb. 2002.
Jean (DriveCam vendor), “DC Data Sheet”, Nov. 6, 2002.
Jean (DriveCam vendor), “DriveCam brochure”, Nov. 6, 2002.
Jean (DriveCam vendor), “Feedback Data Sheet”, Nov. 6, 2002.
Jean (DriveCam vendor), “HindSight 20-20 Data Sheet”, Nov. 4, 2002.
Jessyca Wallace, “Analyzing and Processing DriveCam Recorded Events”, Oct. 6, 2003.
Jessyca Wallace, “Overview of the DriveCam Program”, Dec. 15, 2005.
Jessyca Wallace, “The DriveCam Driver Feedback System”, Apr. 6, 2004.
Joint Claim Construction Chart, U.S. Patent No. 6,389,340, “Vehicle Data Recorder” for Case No. 3:11-CV-00997-H-RBB, Document 43-1, filed Dec. 1, 2011, pp. 1-33.
“Joint Claim Construction Worksheet” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Document 44, filed Dec. 1, 2011, pp. 1-2.
Joint Claim Construction Worksheet, U.S. Patent No. 6,389,340, “Vehicle Data Reporter” for Case No. 3:11-CV-00997-H-RBB, Document 44-1, filed Dec. 1, 2011, pp. 1-10.
“Joint Claim Construction Chart” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 11-CV-0997-H (RBB), for the Southern District of California, Document 43, filed Dec. 1, 2011, pp. 1-2.
“Joint Motion for Leave to Supplement Disclosure of Asserted Claims and Preliminary Infringement Contentions” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-cv-00997-H-RBB, Document 29, filed Oct. 12, 2011, pp. 1-7.
Julie Stevens, “DriveCam Services”, Nov. 15, 2004.
Julie Stevens, “Program Support Roll-Out & Monitoring”, Jul. 13, 2004.
Jung, Sang-Hack, et al., Egomotion Estimation in Monocular Infra-red Image Sequence for Night Vision Applications, IEEE Workshop on Applications of Computer Vision (WACV '07), Feb. 2007, pp. 8-8; Digital Object Identifier 10.1109/WACV.2007.20.
JVC Company of America, JVC Video Cassette Recorder HR-IP820U Instructions (1996).
Kamijo, S., et al., A Real-Time Traffic Monitoring System by Stochastic Model Combination, IEEE International Conference on Systems, Man and Cybernetics, 4:3275-3281 (2003).
Kamijo, S., et al., An Incident Detection System Based on Semantic Hierarchy, Proceedings of the 7th International IEEE Intelligent Transportation Systems Conference, Oct. 3-6, 2004, pp. 853-858; Digital Object Identifier 10.1109/ITSC.2004.1399015.
Karen, “Downloading Options to HindSight 20/20”, Aug. 6, 2002.
Karen, “Managers Guide to the DriveCam Driving Feedback System”, Jul. 30, 2002.
Kathy Latus (Latus Design), “Case Study—Cloud 9 Shuttle”, Sep. 23, 2005.
Kathy Latus (Latus Design), “Case Study—Lloyd Pest Control”, Jul. 19, 2005.
Kathy Latus (Latus Design), “Case Study—Time Warner Cable”, Sep. 23, 2005.
Ki, Yong-Kul, et al., A Traffic Accident Detection Model using Metadata Registry, Proceedings of the Fourth International Conference on Software Engineering Research, Management and Applications; Aug. 9-11, 2006 pp. 255- 259 Digital Object Identifier 10.1109/SERA.2006.8.
Lin, Chin-Teng et al., EEG-based drowsiness estimation for safety driving using independent component analysis; IEEE Transactions on Circuits and Systems-I: Regular Papers, 52(12):2726-2738 (2005); Digital Object Identifier 10.1109/TCSI.2005.857555.
Lisa McKenna, “A Fly on the Windshield?”, Pest Control Technology Magazine, Apr. 2003.
Miller, D.P., Evaluation of Vision Systems for Teleoperated Land Vehicles. Control Systems Magazine, IEEE, 8(3):37-41 (1988); Digital Identifier 10.1109/37.475.
Munder, S., et al., Pedestrian Detection and Tracking Using a Mixture of View-Based Shape-Texture Models, IEEE Transactions on Intelligent Transportation Systems, 9(2):333-343 (2008); Digital Identifier 10.1109/TITS.2008.922943.
Panasonic Corporation, Video Cassette Recorder (VCR) Operating Instructions for Models No. PV-V4020/PV-V4520 (1988).
“Passenger Transportation Mode Brochure”, May 2, 2005.
“Preliminary Claim Construction and Identification of Extrinsic Evidence of Defendant Counterclaimant SmartDriveSystems, Inc.” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H (RBB), for the Southern District of California. Nov. 8, 2011.
Quinn Maughan, “DriveCam Enterprise Services”, Jan. 5, 2006.
Quinn Maughan, “DriveCam Managed Services”, Jan. 5, 2006.
Quinn Maughan, “DriveCam Standard Edition”, Jan. 5, 2006.
Quinn Maughan, “DriveCam Unit Installation”, Jul. 21, 2005.
Quinn Maughan, “Enterprise Services”, April17, 2006.
Quinn Maughan, “HindSight Installation Guide”, Sep. 29, 2005.
Quinn Maughan, “HindSight Users Guide”, Jun. 20, 2005.
“Responsive Claim Construction and Identification of Extrinsic Evidence of Defendant/Counterclaimant SmartDrive Systems, Inc.” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H (RBB), for the Southern District of California. Nov. 15, 2011.
Ronnie Rittenberry, “Eyes on the Road”, Jul. 2004.
SmartDrives Systems, Inc.'s Production, SO14246-S014255, Nov. 16, 2011.
“Supplement to DriveCam's Disclosure of Asserted Claims and Preliminary Infringement Contentions” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California. Oct. 14, 2011.
“The DriveCam”, Nov. 6, 2002.
Transportation Systems (ITS) Programs' Project 84, 1-Witness Black Box Recorder, San Diego, CA. Nov. 2001.
Traqmate GPS Data Acquisition's Traqmate Data Acquisition with Video Overlay system was used to create a video of a driving event on Oct. 2, 2005 (available at http://www.trackvision.net/phpBB2/viewtopic.php?t=51&sid=1184fbbcbe3be5c87ffa0f2ee6e2da76), printed from site on Jan. 11, 2012.
Veeraraghavan, H., et al., Computer Vision Algorithms for Intersection Monitoring, IEEE Transactions on Intelligent Transportation Systems, 4(2):78- 89 (2003); Digital Object Identifier 10.1109/TITS.2003.821212.
Wijesoma, W.S., et al., Road Curb Tracking in an Urban Environment, Proceedings of the Sixth International Conference of Information Fusion, 1:261-268 (2003).
World News Tonight, CBS Television New Program discussing teen drivers using the DriveCam Program and DriveCam Technology, Oct. 10, 2005, On PC formatted CD-R, World News Tonight.wmv, 7.02 MB, Created Jan. 12, 2011.
World News Tonight, PBS Television New Program discussing teen drivers using the DriveCam Program and DriveCam Technology, Oct. 10, 2005, On PC formatted CD-R, Teens Behind the Wheel.wmv, 236MB, Created Jan. 12, 2011.
International Search Report issued in PCT/US2006/47042 mailed Feb. 25, 2008.
Inovate Motorsports, OT-1 16 Channel OBD-II Interface User Manual, Version 1.0, Nov. 28, 2007, pp. 3, 4, 21 & 27.
Trivinci Systems, LLC, Race-Keeper Systems User Guide, Jan. 2011, v1, 1.02, pp. 34 and 39.
USPTO Non-Final Office Action for U.S. Appl. No. 14/036,299, mailed Aug. 12, 2014.
Related Publications (1)
Number Date Country
20070219685 A1 Sep 2007 US