Vehicle event recorder systems

Description

RELATED APPLICATIONS

The present application is a 371 of international application PCT/US2006/047042, filed Dec. 8, 2006, which claims priority to U.S. application Ser. No. 11/296,906, filed Dec. 8, 2005, both of which are incorporated herein by reference.

FIELD OF THE INVENTION

The present invention relates to vehicle event recorders. More specifically, the present invention is related to distributed vehicle event recorder systems that include networked portions coupled via the internet.

BACKGROUND OF THE INVENTION

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

Video systems also have been configured for use in conjunction with a moving vehicle, for example, for use with police automobiles. As a police cruiser is frequently near the scene of an active crime, important image information may be captured by video cameras installed on the police cruiser. However, activity of interest occurring in the proximity of an automobile may not always be related to criminal activity. One example is a traffic accident, for which events and circumstances leading up to an automobile collision may be preserved so that an accurate reconstruction can be created and a more precise assessment of cause, fault and liability may be determined.

Accordingly, the use of video systems in automobiles is rapidly becoming an important tool that is useful not only for the protection of specific individuals, but also of the general public. Some examples of automobile video systems in the prior art are illustrated below.

U.S. Pat. No. 5,570,127 to Schmidt discloses a video recording system for a school bus that has two video cameras, one for an inside bus view and the other one for a traffic view, and also has a single recorder and a system through which the two cameras are multiplexed at appropriate times to the recording device. A switching signal controls which camera is in communication with the video recorder, so to view passengers on the school bus at certain times and passing traffic at other times.

U.S. Pat. No. 5,586,130 to Doyle discloses an invention for an apparatus and a method for detecting fault conditions in a vehicle data recording device, so to detect tampering or unauthorized access. 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. Also, U.S. Pat. No. 5,815,071 to Doyle discloses a method and apparatus for monitoring parameters of vehicle electronic control units.

U.S. Pat. No. 5,815,093 to Kikinis discloses a computerized vehicle log, based on a vehicle accident recording system that employs a digital camera connected to a controller in nonvolatile memory, and on 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 important images, which may include important information about the accident. Kikinis teaches that the system may include a communication port, by which stored images are downloaded after an accident to a digital device capable of displaying images. In particular, images may be downloaded with a wired download to a server having specialized image handling and processing software thereon.

U.S. Pat. No. 6,002,326 to Turner teaches an antitheft device for an automotive vehicle having both an audible alarm and a visual monitor system. Video monitor operators are responsible for monitoring and handling an emergency situation and informing an emergency station.

U.S. Pat. No. 6,088,635 to Cox et. al discloses an accident video recorder for a railroad vehicle, which provides for a recording of the status of the railroad vehicle prior to an accident. A monitoring unit continuously monitors the status of the emergency brake and 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.

U.S. Pat. No. 6,185,490 to Ferguson discloses a vehicle crash data recorder that is arranged with a three stage memory to record and retain information. The recorder is equipped with series or parallel hardwire connectors to provide instant on-scene access to accident data.

U.S. Pat. No. 6,246,933 to Bague teaches a system and a method for recording traffic accident data and for reproducing a traffic accident. A plurality of sensors register parameters of vehicle operation and include at least one vehicle-mounted digital video and audio camera for sensing, storing, and updating operational parameters. Re-writable, nonvolatile memory is provided by the microprocessor controller for storing the processed operational parameters, video images and audio signals. Data is converted to a computer readable form and read by a computer, so that an accident can be reconstructed via the collected data.

U.S. Pat. No. 6,298,290 to Abe et al teaches a memory apparatus for vehicle information data. A plurality of sensors, including a CCD camera, a vehicle speed sensor, a steering angle sensor, a brake pressure sensor, and an acceleration sensor are all coupled to a control unit, which transfers information to a flash memory and a RAM memory. The collected information collected is transmitted through a video output terminal. This video systems is data intensive, and a wired system is necessary to provide sufficient bandwidth for transferring large amounts of data.

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

U.S. Pat. No. 6,389,339 to Just 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.

U.S. Pat. No. 6,411,874 to Morgan et al. discloses an advanced law enforcement response technology. A central control system provides the control for numerous subsystems associated with a police car or other emergency vehicle, driving a plurality of detector systems that include video and audio systems distributed about the vehicle.

U.S. Pat. No. 6,421,080 to Lambert teaches a digital surveillance system with pre-event recording, which is relevant in accident recording systems because detection of the accident generally happens only after the accident has occurred. A first memory is used for temporary storage, and images are stored in the temporary storage continuously until a trigger is activated that indicates an accident has occurred, causing images to be transferred to a permanent memory.

U.S. Pat. Nos. 6,389,340, 6,405,112, 6,449,540, and 6,718,239 to Rayner disclose cameras for automobiles that capture video images, both with forward-looking and driver views, and that store recorded images locally on a mass storage system. At the end of a day of service of the vehicle service, an operator inserts a wired connector into a device port and downloads information into a desktop computer system having specialized application software, so that the images and other information can be played-back and analyzed at a highly integrated user display interface. However, an administrative operator is not able to manipulate or otherwise handle the data captured in the vehicle at an off-site location without human intervention. Instead, a download operator must transfer data captured from the recorder unit device to a disconnected computer system. While proprietary ‘DriveCam’ files can be e-mailed or transferred through the internet, the files are in a format that can only be opened by specific DriveCam software running at a remote computer. Therefore, a major disadvantage is that a human operator must service the equipment daily in a manual download action.

Therefore, vehicle event recording systems in the prior art are not structured to have system components located remotely from one another. At best, a manager workstation computer must be positioned in the vehicle parking facility, forcing that manager and all the users of the server to make use of the server at the parking facility. As a consequence, personnel requiring access to the recorded information must go to the server facility to receive that information, and even if data were transmitted by e-mail in proprietary digital formats, such data may not be in readable formats at the receiving ends, and time would be consumed to access those receiving computers.

Therefore, the systems in the prior art cannot be structured as distributed systems, limiting deployment due to the above described drawbacks.

SUMMARY OF THE INVENTION

It is an object of the present invention to provide a fleet management system based upon a vehicle event recording system.

It also is an object of the present invention to provide a vehicle event recorder system that includes a distributed network component.

It is another object of the present invention to provide a vehicle event recorder system that includes the internet.

It is a further object of the present invention to provide a fleet management system, in which automated reporting is enabled, so that a fleet manager can take specific actions in response to reports automatically generated by the system.

It is still a further object of the present invention to provide a fleet management system, in which a data analyst may be far removed from fleet vehicles.

It is still another object of the present invention to provide distributed fleet management services and applications, in which an insurance underwriter can process data captured by the system to manage risk.

It is yet another object of the present invention to provide a fleet management system, in which an automobile maintenance team can respond to conditions detected and reported by the system.

It also is an object of the present invention to provide fleet management system, in which a roadway or highway engineer can receive reports and alerts which relate to roadway conditions.

It is one more object of the present invention to provide fleet management system, in which government authorities can act upon data captured by the system.

These and other objects of the present invention are accomplished by apparatus and methods related in a distributed vehicle event recording system that are deployed in networks which may include the internet. The vehicle event recorder system of the present invention finds applications in vehicle fleets and relates to video recording systems, communications networks, centralized server computers, and specialized application specific computer code to enable highly unique system functionality.

Fleet vehicles communicate with the server, and data exchange is automatically triggered in response to normal and common use of the vehicle without intervention by the driver or fleet manager. Vehicles returning to an appropriately arranged parking facility automatically connect to the server to download video data to the server, where it may be processed and further accessed by various interested parties. Such video data includes primarily scenes before a vehicle that are captured when the vehicle is involved in an event such as a traffic accident.

Vehicle fleet management networks are characterized as including at least one vehicle event recorder, a communication space formed from the combination of a vehicle parking facility and a wireless communications system, a network that may include the internet, and an application specific server computer.

A vehicle event recorder includes a radio transmitter and is further coupled to the communication space by way of a proximity trigger, so that the presence of the vehicle in the communication space enables data transfer actions, by which video data is conveyed from the vehicle to a remote server for further use. The vehicle event recorder includes a camera, a microprocessor, a memory, a mobile wireless transceiver, a connection manager, and a proximity trigger. Video images captured by the camera are stored in a specially arranged memory buffer until the vehicle returns to a parking facility, where images are automatically transferred to a remote server.

A communication space includes a parking facility, a fixed wireless transceiver, a network address server, a broadband connection to a communications network, and authentication systems. Upon arrival of an authorized fleet vehicle into the communication space, an enabled connection between the vehicle event recorder and the fixed wireless transceiver includes an authorization process. A vehicle suitably identified can then call a remote server via a proprietary data exchange method. Accordingly, servers include application specific software, a connection to a computer network, and web applications and web services arranged to cooperate with vehicle event recorders.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects and advantages of the present invention will become apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, in which:

FIG. 1 illustrates schematically various types of fleet vehicles in respective groups, each in communication with a central server via the internet;

FIG. 2 illustrates in greater detail a facility in which fleet vehicles are in communication through the internet;

FIG. 3 illustrates an embodiment that includes a ‘store and forward’ preprocessing station;

FIG. 4 is a block diagram of a vehicle event recorder unit suitable for use in an automobile;

FIG. 5 is a block diagram illustrating elements of a vehicle event recorder unit;

FIG. 6 is a schematic representation of cooperative systems forming a network relationship with recorder elements;

FIG. 7 illustrates examples of a system server and illustrates functionality associated therewith;

FIG. 8 is a diagrammatic representation of a relationships between entities that interface with a server via networks;

FIG. 9 shows a relationship paths between network entities, vehicle event recorders and related servers;

FIG. 10 illustrates a system having a plurality of download spaces related to a single server;

FIG. 11 illustrates fields associated with a scheme to enlarge a download space; and

FIG. 12 illustrates a proximity trigger which sets into motion a function of the systems of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

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.

Vehicle Event Recorder: An electronic apparatus that may include video recording equipment, audio recording equipment, vehicle system sensors, environmental sensors, a microprocessor, application-specific programming, and a communication port, among others. A vehicle event recording unit is sometimes built into a small housing suitable for mounting to a common vehicle such as a truck, car, motorcycle, airplane, or ship. Some vehicle system sensors may not be contained within the housing of the vehicle event recording unit and may include electronic. Wireless, or wireline communication, for example a ‘bluetooth’ link.

Wireless Communication Space: A region in which a electromagnetic communication signals may be reliably received and transmitted by at least two communicating transceivers. The wireless communication space has a ‘soft’ boundary that is not defined to be some particular size at all times. However, a wireless communication space still is a discrete entity.

Fleet: A group of related vehicles. The relationship between vehicles in any one fleet is generally by ownership or management; however, other factors may connect the vehicles of a single fleet. For example, maintenance interests may cause several vehicles owned by independent parties to become part of a ‘single fleet’ for the purpose of the present systems. A ‘fleet’ may also be comprised of a single vehicle. While outside the traditional sense of the word fleet, a single vehicle fleet is fully included for the purposes of the systems discussed herein.

Proximity Trigger: A system devised to detect a prescribed proximity condition and provide an electronic signal in response thereto, the electronic signal being coupled to another system which may be set into action as a result of receiving the proximity trigger signal.

Event Trigger: A system devised to detect a predetermined physical condition and provide an electronic signal in response thereto, the electronic signal being coupled to another system that may be set into action by receiving the event trigger signal.

Parking Facility and Parking Lot: Any place that can accommodate temporary storage of a vehicle for at least a short period of time. It is not necessary that the vehicle actually stops nor fully engages a ‘parked’ status. A slow moving vehicle in a certain space, such as a specially configured ‘download’ lane, may be designated for the purposes of this invention as a ‘parking facility’. Therefore, a parking facility/lot merely indicates a place that a vehicle might occupy while within range of a radio transceiver.

Download Space: An area over which a wireless communications link can be maintained between the radio transceiver of a vehicle event recorder and a fixed wireless transceiver. “Download Space” is also meant to include a facility, in which a vehicle can be temporarily accommodated (parked) while a communication link is maintained.

A vehicle event recorder system constructed in accordance with the principles of the present invention relates to at least one fleet of vehicles and includes a recorder unit that may be connected to a download space, a wireless radio having a broadband network connection, and a server computer system arranged to provide application specific functionality. Application specific functionality is provided as web services and web applications, which may be supplied from a remote server via TCP/IP transactions over a public communication network. In this event, proprietary protocols are adopted, in which microprocessors in vehicle recorder units make calls to and receive responses from remote servers.

Due to its highly mobile nature, a vehicle is not easily connected in a permanent manner to an information networks. While limited connection support may be envisioned, for example, via USB or fire-wire hardwire connection, or via a mobile telephone network, these connections have burdensome limitations which render such arrangements undesirable. Temporary hardwire connections require a human operator and significant daily overhead associated with a download strategy. Mobile telephone networks have bandwidth limitations and reliability issues which prevent the use of these connections in the manner required by certain high performance applications.

In a system according to the present invention, a vehicle enters a communication space having wireless coverage that enables the vehicle to be connected to the server and communicate therewith. The relationship between the vehicle event recorder and the communication space is such that mere entry of the vehicle establishes the communications link and initiates at least a download transaction. Accordingly, an operator need not carry a laptop to each vehicle and initiate a physical connection.

Referring to FIG. 1, the communication of an independent fleet of vehicles with a centralized server by way of a highly distributed network such as the public internet is described. Communication space 1 is the region of space covered by wireless communications radio service. For example, when a communications link comprises a ‘WiFi’ type radio transceiver 2, reliable communication may be sustained only over a limited range, which may be approximated by a sphere having a radius of a few hundred feet. Therefore, a common parking facility such as a small parking garage may be served by a WiFi radio system, which is large enough to cover fleets of a few dozens of vehicles all parked in a common parking location. Accordingly, these systems include cooperation between a storage location for vehicles and a wireless data communications link; that is, the range of transceivers is configured to envelope and surround the appropriate vehicle storage location.

Thus, the extent of wireless communication space 1 is defined by and served by wireless radio transmitter 2, which broadcasts radio signals into the space. When a specially configured mobile computer installed within a prescribed fleet vehicle 3 enters the communication space, the computer detects this condition. Upon detection that a signal is present (that a vehicle has arrived in the communication space), the computer makes a communication connection and performs a ‘handshaking’ which includes a network address assignment, for example, from a radio or router service arranged as a network address server. Once the mobile computer has a network address, it is ready to communicate directly over the internet 4 and with network nodes similarly connected. The radio is preferably connected to the internet by broadband connection 5, for example a digital subscriber line DSL or cable or fiber type connection or a mix of these high-speed systems. Finally, as a network endpoint, application specific system server 6 is comprised of programs suitable for communicating with a plurality of vehicle event recorder units and a plurality of communication spaces, which may be widely and remotely distributed.

Various vehicles 3, including trucks, motorcycles, buses, etcetera, together form an example of a fleet. A fleet is generally a group of cars which are somehow interrelated. A fleet may be comprised of a plurality of vehicles such as the school buses of a single school district. Fifty buses may form a fleet of vehicles with a common owner, administrative staff, physical management facility and parking lot. Accordingly, a school bus vehicle fleet is ideally suited for an embodiment of this invention.

Any particular fleet may have associated therewith a parking lot or other storage area, to which fleet members are returned each night after a day of service. In one embodiment, such parking space is equipped with a radio transceiver or radio transceiver network, so that all vehicles connect to communicate with the internet upon their arrival at the parking facility. Thus, a vehicle storage location is combined with a suitably arranged transceiver, which envelopes the vehicle storage location in communication space 7. Radio transceivers form a communication envelope, which surrounds a parking facility, whereby returning vehicles pierce the envelope boundary as they enter the parking facility and a reliable communications connection to the internet is automatically initiated after the vehicle enters the communication space. Application specific computer programming code running on the vehicle event recorder enables the vehicle event recorder to contact a remote server and perform transactions therewith. Thus, a driver need not manually set, trigger, connect or enable any actions. In fact, the driver need not even be aware of the existence of the system and of its operation. A driver merely has to return the car to the parking lot to cause a communications connection to be enabled automatically.

While the embodiment described in detail herein is on that includes fleet members of the type characterized as ‘motor vehicles’, i.e. cars, motorcycles, trucks and buses operated on streets and highways, this embodiment is not limited to those kinds of vehicles, but can also serve vehicle systems which are not automobile-type vehicles.

For example, download space 8 can be arranged, in which yachts enter that space to cause an automated communications connection. A harbor can support a fixed WiFi transmitter and high-speed internet connection, through which all boats entering the harbor are enabled with communication to a server. Under this arrangement, a harbor is a ‘parking facility’.

Similarly, airplanes that approach an appropriately equipped gate come into contact with the system server that can download information recorded during the service of that aircraft aircraft. A restrictive meaning should not be associated with the term ‘vehicle’ to conclude that only cars are being considered herein.

As described, vehicles equipped with event recording units automatically establish a wireless communications link with a remote application server that is configured to communicate with the vehicle event recorders upon entering predetermined communication spaces. There is no longer a need for a human operator to engage a vehicle to establish a physical connection by way of a mechanical plug-in device and system, to remove and exchange tapes from tape recording type systems, and to manually perform a download step, or an on-site fleet IT manager to be involved in any way.

Independent fleets of vehicles, which are maintained, owned and operated by independent parties, may similarly be in communication with the same server. A separate communication space 7 which may be remotely located with respect to another communication space 8, serves an entirely different and unrelated fleet. For example, when public authorities operate and maintain a fleet of emergency vehicles 9, these vehicles may enter communication space 7 to activate a communications link, whereby data recorded by recording unit can be downloaded to the centralized server. This communication space may be a parking lot associated with city vehicles. It may also be the same parking lot that is appropriate for storage of vehicles overnight. This way, the vehicle operator returns the car to the lot at night for storage, and without taking any further act causes data to be downloaded to the remotely located server. Thus, the lot only need be equipped with a WiFi transmitter connected to the internet, and it is no longer necessary to maintain a computer on-site. Such architecture frees fleet information technology managers from the need to be in the same location as the fleet vehicles. It is no longer necessary to maintain a strong IT capacity at the same location where the vehicles are stored. A ‘smart’ parking lot only needs to be equipped with very inexpensive WiFi radio transmitters and a broadband connection to the nearest internet service provider.

Referring now to FIG. 2, an architecture including additional system elements in communication with a vehicle event recorder network is shown in greater detail. In particular, server 21 having a defined and fixed network address associated therewith is in communication with mass storage database 22, and is further coupled by way of the internet to a wireless radio transceiver 23. The transceiver has a useful range which defines the extent of communication or download space 24.

One skilled in the art will appreciate the advantages of having the internet situated between the architecture endpoints, i.e. the server or database network node and the vehicle recorder unit network node. As fleet vehicle storage and information technology professionals and offices are sometimes not in the same location, efficient communication over long distances has to be provided. Moreover, because the data collected for this system is useful to different independent and distributed parties, is similarly useful to access to the data over highly distributed networks that include the internet.

While the internet is a public system, it also can be used for highly secure and private transmissions of information. For example, link 26, dedicated to the application at hand, may permit the server to communicate privately with known system members. In some instances, this can be achieved by way of a virtual private network or VPN 27. It is also possible to simply arrange communications over the public network, in a coded fashion only understood by the server and the vehicle event recording units aboard vehicles 28, 29 and 210. Each of these vehicles, being qualified members of the system, exchange digital transactions with a prescribed server. An unauthorized computer attempting to communicate with the server could not properly form requests without prior knowledge of the services and communication protocols available on the server. Thus, the server's private services would not be easily accessible to non-members.

The server connected to the internet is widely available to all systems similarly coupled to the internet, without regard to location. Thus, web applications may be served to authorized users by the same server along communication path 211. As the server is connected to the internet in this manner, any number of users may establish communication 212 simultaneously with the server. Individual managers operating remote workstations 213 can view web applications provided by the server and interact therewith from any location in the world. Thus, an administrator of recorded vehicle video information needs no longer to be present at the vehicle or at the vehicle's parking facility, which had previously been near in distance or co-located with the location where the vehicle fleet is stored during the night.

A parking facility may include an IT office with a download workstation running desktop applications. The entire remote intranet 214 of a company of a number of employees may be similarly connected and in communication with a server and database, holding data captured by a vehicle event recorder. Because the data gathered by a vehicle event recorder is useful for employees that are not a top level fleet administrator or manager, other parties interested to vehicle use and management no longer have to receive raw data by unmanaged e-mail transmission, or visit a physical site where a vehicle is parked, nor rely on human operators to download data from the necessary vehicles each day when the vehicle arrives at its storage facility. When vehicle event recorders are coupled through automatic downloads to high power servers connected in a shared network relationships, information is processed more efficiently and results in a system of greater functionality and processing power.

Another important strategy permits system members, for example computer programs in recorder units, to consume ‘web services,’ computer services or programming functionality. The programming functionality is not available to outside systems, nor there are any visible components or a human interface to the web services, which are provided for computers to interact with computers. Thus, a vehicle event recorder unit in a vehicle, which is in a predetermined communication space, may call a computer function which resides and is executed on the remote server. Thus, very large processing power and database capacity is available at the same time at a relatively small computing facility associated with a vehicle event recorder unit, obviating the need for a computer workstation at the parking site.

Another advantage to having the internet as part of system architecture relates to customer interaction from various locations. Interested parties may not be located in a common place with download and server facility, partly because many unrelated parties may have an interest in the same data. For example, insurance underwriters may be interested in reviewing driving histories, and it would be overly burdensome for insurance underwriters to review driving records at a fleet facility.

Because of the nature of vehicle fleets and of the activity associated therewith, it is sometimes necessary to provide a different system architecture. In particular, special circumstances may arises in the situation where a large number of fleet vehicles returns to a lot at approximately at the same time. If a server computer is separated from the vehicle fleet by a link of limited bandwidth, excessive data traffic will prevent properly organized downloads from all vehicles. As it is physically impossible to provide links of unlimited bandwidths, a local buffer may be deployed, which is arranged to receive and hold a massive amount of video data from all returning cars and to later transfer that information over time to a server is an improved arrangement.

The problem is exacerbated when fleet ‘turn-around time’ is short, for example, in a taxi or police fleet, where the vehicles are used on multiple shifts with various drivers. In this situation, it is impossible for the server to download data from one vehicle at a time in a serial operation, because the vehicles in the download queue will tend to return to service before their download operation may be completed.

An alternative system architecture configuration is described in FIG. 3, and includes a dedicated workstation computer co-located at or near the facility where vehicles are stored. The dedicated workstation computer includes specialized data management services and provides fast download, store and forward functions, scheduling, and authorization administration, among others. In some instances, it is preferable to include a very high speed downloading service on site at the parking facility. This is particularly the case when several vehicles arrive simultaneously, for example at a shift change. Since not all broadband connections to the internet are sufficient for quick transfers of very large quantities of data, in some cases a workstation computer configured should be configured for authorization and authentication processes, to receive at very high speeds information including video data from arriving vehicles, for buffer storage of that data, for data queue management, and for further transferring data to a centralized server at a later time.

Accordingly, FIG. 3 shows server 31 properly coupled to mass storage database 32. By properly coupled, it is meant that provision is made for fast, frequent, and efficient exchange of data. To this end, not only is bandwidth very high, but the programming between code running on the server and code running in the database are tuned with respect to the application at hand and formed in conjunction with one another. The server is connected via the internet to workstation ‘store and forward’ buffer computer 33, which is co-located at the parking facility where fleets vehicles are stored. The workstation computer is in communication with the WiFi wireless transmitter via very high speed communications link 34 that provides communication space 35, into which arriving vehicles 36 may be received. Such download may be completed in a very short period of time. Data is passed wirelessly from a vehicle event recording unit to the WiFi transmitter, and thereafter to the workstation computer. Data is temporarily stored at the workstation computer, and is later transmitted through the internet 37, then over modest bandwidth private link 38, and finally arrives at server 31 and database 32. This server provides web services and web applications to wide audience 39, which may utilize these services and application anywhere where internet access is available. In this manner, data collected by fleet vehicles is made available to widely distributed interested parties.

The premise of these embodiments lies in fleet vehicle management strategy. As such, one system endpoint is a vehicle event recorder which is suitably affixed and mounted within a common vehicle especially an automobile. These devices may be a permanently affixed within vehicles and will soon be provided as standard equipment. Electrical couplings such as power supply and data connections with the vehicles electronic systems may be made through standard connectors and interfaces. These devices are thus coupled to the vehicle and its systems. They are further coupled to the vehicle whereby an optic axis of a camera is aligned to provide images of events occurring about the vehicle. In some versions a second camera has a field-of-view includes the space which contains the vehicle operator. A single vehicle event recorder may be provided with a plurality of cameras and corresponding number of image spaces. Thus some vehicle recorder units contain two cameras, one pointing forward and one pointing toward the operator spaces.

These devices are sometimes arranged to be completely self-contained and require as little mechanical connection with vehicle systems as possible. For example, it is necessary to have a good mount, which provides that the optical axis be aligned with desired fields of view; however, it is not a requirement that the device be integrated with a vehicle computer or other vehicle hardware.

The head portion of a vehicle event recorder system is shown in greater detail in FIG. 4, which illustrates vehicle event recorder head 41 in block diagram form. The primary elements include microprocessor 42 including application specific computer code, electronic video camera 43, event triggers 44, memory buffer system 45, connection manager 46, and radio communication system 47. In some versions, an on-board data bus, OBD, diagnostics system 48 is included. Such OBD systems are coupled to sensors at vehicle subsystems 49 such as lights, engine, brakes, and steering, among others, to provide feedback as to the state of those systems, which may yield further information in conjunction with video data related to causes of events being recorded.

Vehicle event recorder systems are built about a microprocessor suitable for use in computing platforms for self-contained electronic apparatus. In most cases, these microprocessors are not arranged as general computing platforms, but rather with application specific firmware directed to particular functions at hand. These processors support the ability to perform application-specific functions and drive complementary subsystems such as memory, input/output ports, network connections, video input, and event triggers, among others.

Particularly worthy of mention among these functions is ‘event handling’, wherein an event trigger causes execution of a computer routine and an image or image series collected by a camera is transferred from a temporary short-term buffer memory to a durable and lasting memory, where it may be stored for a considerable period of time. Thus, the microprocessor is responsive to an event trigger such as an accelerometer and a predetermined threshold, which detects abrupt movements and sets the microprocessor into action to transfer stored data from one memory to another.

Further, the microprocessors of vehicle event recorders are arranged to support wireless connections and data exchange with authorized networks. In particular, the microprocessor is coupled to a proximity trigger which is toggled whenever the vehicle event recorder enters a prescribed communication space. Upon detection of such proximity condition, the microprocessor attempts an authorization step whereby the identity of the network and vehicle event recorder are checked and verified.

If the vehicle event recorder is identified as one properly located within an authorized download space, the microprocessor continues with a data transfer or download step, in which information stored in the memory of the vehicle event recorder is transferred wirelessly to either a server or to a ‘store-and-forward’ workstation for later transmission into the broader systems network.

After a completed download, error checking and confirmation steps permit the microprocessor to complete the connection to proceed with a disconnect operation.

The functions including connection detection (sometimes called ‘proximity detection’), network address client, authorization, download, disconnect, among others, are sometimes arranged as part of a connection manager module.

An electronic video camera may be arranged such that it has a field-of-view which includes an environment about a vehicle. For example, the forward space ahead of a car is an area generally of great importance in consideration of accidents which occur from time-to-time. The camera is further coupled to the microprocessor and image buffer, so that images captured by the camera may be discarded when it is determined that those images are no longer of importance, or in the opposing case, saved to a durable memory when it is determined the images are associated with an important event.

This type of video cameras is arranged to continuously capture video images both before and after an accident, should one occur. Thus the cameras are durable and fixed mechanically in a vehicle, so that they can survive the impact associated with a collision. While in most cases it is anticipated the camera will be affixed within the driving compartment, an alternative includes mounting cameras on the exterior the vehicle, for example, at a rooftop or coupled with a bumper. The camera is in electronic communication with the microprocessor, whereby the microprocessor operates to drive camera functions.

Event triggers include means for sensing an important event and in response thereto activating the microprocessor to perform save operations, preserving images associated with the detected important event. Event triggers may be arranged about various systems including an on-board data bus, accelerometers, a panic button, or a time interval trigger. An onboard data bus may be arranged as an event trigger when some measured parameter exceeds a prescribed threshold to indicate the occurrence of some condition. When the threshold is exceeded, an electronic signal can be provided to the microprocessor queuing it to handle images accordingly. Alternatively, accelerometers can detect very strong movements such as a car swerving or breaking excessively hard, or a direct collision. In these situations, the events may be declared important and the accelerometer will provide the signal upon which the microprocessor will act to preserve images recently captured and those captured soon after the event.

A ‘panic button’ type event trigger may be arranged as a tactile switch, which a user can engage when the user makes a judgment that an event has occurred. When a driver sees some relevant activity, she can engage the panic button to cause an image save operation. An event trigger may be as simple as a mere timed interval. After a certain period of time has elapsed, an image save operation can be executed. In this case, the mere passage of time causes a signal, which sets the microprocessor into action to save images.

Vehicle event recorders in these embodiments include important memory systems. Preferred memory systems include those having a managed loop buffer, where images are temporarily stored for brief periods of time. When an event occurs, trigger toggle images are transferred to a second more durable memory from the managed loop buffer, thus preserving images associated with the event. In some versions, the managed loop buffer is embodied as a semiconductor memory such as a DRAM memory, which is quite fast and may be written to many millions of times without exhausting its functionality. In the same system, the durable memory may be fashioned from a flash memory system suitable for holding large amounts of data, including video type data. Said flash memories are very inexpensive and have suitable capacity for holding video information associated with a large plurality of separate events, which may occur throughout the service day of a vehicle event recorder.

Wireless communications radios in wide use today include those known as WiFi transceivers. A WiFi transceiver is very inexpensive radio, which generally includes network functions such as network address handling services, router services, firewall services, and network switching, among others. Thus, it is an advantage of these systems to deploy WiFi type transceivers, so that a vehicle entering a parking facility can be automatically connected to a cooperating network.

New, soon to be introduced, systems boast far greater range than those WiFi systems; for example, “WiMax” systems will have range of a few, perhaps tens of miles. It is useful in some embodiments to arrange WiMax transceivers in conjunction with a parking facility in a vehicle event recorder system. In either case, a wireless communications transceiver has a finite and limited range, which gives rise to a coverage region or communication space and some implicit peripheral boundary. While we use herein WiFi and WiMax systems as examples, it will be recognized by a person skilled in the art that many alternative wireless systems are available, some which might be used in place of a WiFi or WiMax system. WiFi and WiMax have been described here because of their adequate performance characteristics and very low-cost.

In addition to these subsystems, the vehicle on-board data bus system or OBD is also coupled to the vehicle event recorder microprocessor. An on-board data bus is an electronic system coupled to a plurality of transducers and sensors throughout the vehicle, each of which collects data related to vehicle characteristics and performance. The on-board data bus may include information about drive train and transmission, engine operational status, brakes, lights, et cetera. The on-board data bus is useful in vehicle event recorders for providing additional data and information, which relate to the status of a vehicle, subsystems and engine conditions at a particular time of interest, for example in association with a traffic accident.

Subsystems of vehicle data recorders may include additional optional elements. Some of the most important of these optional elements are illustrated in the block diagram of FIG. 5 alongside with the primary elements. Data recorder unit 51 comprises computer microprocessor 52 with appropriate vehicle event recording management programming installed. Two cameras 53 include a forward-looking camera and microphone 54 and a driver compartment camera and microphone. Advanced high performance memory system 55 includes a two-stage buffer of managed loop memory 56, and flash memory 57 is provided according to attributes and the nature of these systems and applications. Radio 58 provides a wireless communications link in conjunction with connection manager 59, which couples the microprocessor to systems external to the vehicle event recorder head. Internal web server module 510 runs within the device to provide an hypertext transfer protocol interface, whereby internal adjustments to subsystems may be effected via remote web browsers. Some embodiments include position determining means 511 such as a global position system GPS locator. Other sensors and transducers 512 may be deployed about a vehicle to measure parameters related to vehicle performance, independent of those transducers that are already a part of the on-board data bus system. In addition, data collected from an on-board data bus directly coupled to the microprocessor provides similar functionality.

Graphical user interface 514 provides a visual means of conveying messages and information to a human operator. User tactile input means 515 such as a keypad may also drive activity within the vehicle data recorder head. Event triggers, including accelerometers 516 and panic button 517, are arranged to indicate to the microprocessor the occurrence of an instant event and the need to preserve images associated therewith. Finally, internal illumination system 519 is provided for nighttime use.

In some versions, a forward-looking camera and exterior microphone are arranged to record video and audio information outside the vehicle compartment. Conversely, a vehicle event recorder system may additionally deploy a second camera as a vehicle driver compartment video camera and second microphone as an interior microphone, arranged to record video and audio inside the driver compartment. Thus, it is said here that vehicle event recorders include at least one camera, but may also include any number of auxiliary cameras and microphones.

In some embodiments, a vehicle event recorder may be provided with a very large capacity memory system such as a disk drive unit. A so-called ‘microdrive’ can be arranged as a very small memory system capable of recording video data over extended periods. All driving activity throughout a service day, including service days with no accidents, may be of interest in some system versions. Thus in the present embodiments, a recorder is started in the morning at the beginning of the service day and operates to continuously deliver data to the memory until the end of the service day, when the vehicles are returned to the storage facility. All recorded data including non-accident or non-event related data is put into memory and downloaded at the end of the day. This way, the vehicle event recorders of these embodiments completely omit accident triggers that manipulate data storage systems, so to prevent overwrite of memory.

In other embodiments, a computer module known as a ‘web server’ may be included, so that a vehicle event recorder that has established a communications connection may be addressed and manipulated by way of a common computer internet browser. Thus, a vehicle event recorder present in a communication space may be ‘browsed’ by remotely located systems operators. It is possible in this manner to reset or to otherwise manipulate various adjustable settings which may be within the vehicle event recorder. It is not necessary to physically access the vehicle event recorder with a screwdriver for example, in order to change the brightness or contrast of the video system. Instead, an operator located in India may adjust the brightness of a particular vehicle after noticing problems in a video analysis operation being taken up far from the vehicle location. While updated firmware downloads can provide the same function, a web browser provides a highly functional user interface front end which is easily operated by anyone who can operate a computer.

A recorder unit may be equipped with GPS receiving system 510. At all times, a GPS receiving system can provide a position signal to the microprocessor for recording. Position determination results can be recorded by these versions of vehicle event recorders to associate measured location with accident video. Further, the system sometimes includes an electronic compass device, which can measure the direction of a reference axis associated with the vehicle. Thus, one can tell precisely in which direction the vehicle is pointing at various recording intervals and this information can be similarly recorded.

It is also possible to incorporate other transducers, which are coupled to the vehicle in some way to measure physical parameters of the vehicle or its environment. These transducers might be coupled to the processor directly and connected to one or another vehicle subsystem. For example, a drive shaft pickup might include a magnet which the detects every turn of the drive shaft. This information could yield indications as to vehicle speed, which are important during accident review.

Some versions of these vehicle event recorders include a graphical user interface in the form of a display unit, suitable for converting electronic signals provided by the microprocessor to graphical messages easy to read and understand by human users. After properly logging in, a driver may receive a message reminder to “drive safely” on such displays

A tactile keypad is provided in some versions in order to allow users to provide inputs to the microprocessors. Where fleet vehicles are shared by several drivers, it is useful to provide means for a driver to identify herself to a system by way of a touchpad code or PIN number. As such, vehicle event recorders may sometimes be provided with such keypad input devices suitable for these functions.

For nighttime use, or in other no or low light level conditions such as when the vehicle enters a tunnel, these vehicle event recorder units may include integrated IR illumination system 519, providing illumination in the driver compartment that does not distract the driver. Infrared light is detected by the video camera but cannot be seen by the driver. Accordingly, the infrared light does not distract the driver.

In some circumstances, wireless mobile phone networks may also be used for the communication link in special versions of these systems. In this regard, the wireless communication space boundaries are defined by the extent of the cellular network coverage. Since mobile phone network systems are relatively mature, the coverage area attainable is considerable. Accordingly, vehicle event recording systems arranged in this fashion may have a wireless communication space of considerable extent, covering tens or even hundreds of square miles.

Video frames selected from a series may also be transmitted. For example, while recording locally at a rate which far exceeds one frame per second, one could transmit at less than that rate over the limited bandwidth wireless telephone network. Thus, the system could convey image information albeit in limited quantity, resolution or rate.

In systems deploying a mobile telephone network as a communication link, the ‘proximity trigger’ described above becomes somewhat ambiguous, because the vehicle rarely leaves and reenters communication space and may remain continuously therein during the entire service day. In the embodiments described above, a vehicle's entry of the download space is the trigger which causes a download action. However, such triggers are ineffective when mobile telephone networks are used as the communications link

Considering now the opposing node of these networked vehicle event recorder systems, reference is made to the portion of these network systems that includes the server and data consumer clients. In particular, reference is made to server computer 61, which communicates by way of the internet with a plurality of prescribed and authorized member entities. While data is received from vehicle event recorders along paths 62 from remote recorder units as previously explained, it is relevant to how such collected data is distributed, analyzed and consumed.

Recorded information which bears indication and history as to the use and abuse of vehicles is important to a number of interested parties. For example, a fleet administrator/manager keeps track of vehicles and drivers he manages not only for maintenance and safety purposes, but also with respect to scheduling and loss prevention, among others.

A fleet administrator/manager working from workstation 64 located in any part of the world can interact with web applications served by the server to manipulate and examine data recorded by any of the fleet vehicles. Web servers can be arranged to provide a fleet manager access to vehicles under her specific management only and to restrict access to the information collected by vehicles under the management of an independent entity. Thus a single server can be used by completely independent entities who manage different fleet vehicles. No other system known in the arts has a single server which can receive information from various vehicles belonging to different fleets, sort that information accordingly, and restrict its access to the appropriate authorized parties. Thus, in a municipality, a vehicle maintenance department can subscribe to the service by way of the internet in parallel with the fleet manager of a private fleet operation. While the two users know nothing of the other, they share a common server, database and service provider, thereby reducing costs for all.

The server/service provider might include high security level administrative workstation 65, which has a direct private connection and unique credentials to the server. A service administrator, requiring high-level administrative privileges to the server, may be connected on the inside of a strong firewall. Such administrative node is not appropriately exposed over the internet for security reasons.

Applications consumers 66-69, include network nodes which communicate with the server by way of its applications and services. Special applications may be configured for different particular users or data consumers. Some of these special purpose applications are illustrated hereinafter.

Insurance adjusters and underwriters use advanced data analysis to better position themselves with regard to risk management. Presently, reports and statistical analyses available to insurance adjustors and underwriters are largely compiled by manual processes. When insurance adjusters and underwriters deploy and use the systems described herein, immediate access is provided from their remote offices to detailed current data from vehicles insured by their companies. This data set can be accessed directly from the server having an application host running a special insurance application configured to serve the precise information that insurance underwriters and adjusters need. Some information relating to vehicle use remains private with respect to the vehicle's owner and driver, however, by agreement with insurance companies, a vehicle owner may decide to make available and submit particular information in consideration for preferred insurance rates. In this situation, the server of these systems provides an application, addressable by insurance underwriters, to deliver information that insurance companies can use to manage risk.

In addition, insurance underwriters will find another advantage in using of the system of the present invention. The mere presence of a vehicle event recorder system has a very strong effect on drivers wishing to keep their jobs. Mere knowledge that a detailed video record will be available to fleet managers in case of incident keeps driver behavior in check. Thus, even placebo systems arranged to appear functional but in fact totally inoperable will provide insurance underwriters with a great advantage. However, where a fully operable system is deployed, insurance underwriters will be in far better position to manage risk more precisely.

Insurance company workstation computer 66 connected to the internet can communicate with the server computer and employ the web services and applications that are provided specifically for insurance companies. Thus, the server is arranged with particular web applications that insurance companies can use to monitor the vehicles insured by them. In this manner, insurance companies can mitigate their exposure to high risk vehicles and situations. An insurance company can maintain a constant monitoring for changes that might affect their position and can remain highly responsive thereto. Such high access to current information is be a powerful tool for insurance underwriters to develop advanced risk management strategies. Previously, insurance companies had only access to vehicle history records by way of a public authority and clients reporting and history.

These systems of the present invention enable another important management application yielding advantages not only to fleet vehicles, but also to the roadways upon which the vehicles operate. Data collected by these systems includes information about traffic accidents, therefore, computing systems can be set up, whereby a threshold can be triggered to indicate a dangerous condition. For example, if several accidents happen within a short period of time at the same location, this occurrence may be indicative of faulty roadway equipment such as a malfunctioning traffic light. When a threshold is exceeded, the systems of the present invention can be arranged to send an e-mail notice to roadway engineers, notifying them of the dangerous condition. Workstations 67 used by road safety engineers having access to e-mail and the internet may also be connected to the systems of the present invention. Thus, road safety engineers might look to web applications served by the embodiments described herein to provide information related to some particular road safety issue.

For example, if there are fifteen automobile crashes at Fifth and Elm street during the month of July, the server can trigger a message and send it to a road safety engineer. Some condition may have changed at the intersection unbeknownst to the authorities. The message could put the road engineer on alert that something has happened and the intersection has become dangerous. For example, a huge pothole maybe causing cars to swerve just at the moment when drivers need to pay attention to incoming traffic at the intersection.

Another example of how road service engineers might use the systems of the present invention includes the following. To determine the safe speed on a road, some municipalities set a threshold indicator. For example, it may be determined that 85% of drivers drive at or below the “safe speed”. In this regard, a system keeping track of vehicle locations and of the speed at which the vehicles are driven may be used to compile information for any particular road stretch and determine what is the safe speed per that section of the road. Road safety engineers can use this information to provide proper signage and road construction elements, such as guard rails, indicators, warnings, etcetera. Some versions can be completely automated and left unattended by human operators. The computer can monitor roadway conditions without input from anyone, and provide appropriate notice when a certain condition is met. Such highly automated systems can prove extremely valuable for general public safety.

Another important application enabled by these systems relates to Departments of Motor Vehicles managed by local authorities, that typically maintain records of traffic accidents and driver behavior.

Since the systems disclosed herein provide highly effective data capture functions, and further provide ready and easy access to such data, a Department of Motor Vehicles may employ these data capture and management systems via a server applications host running a program configured and designed to provide particular types of data. With vehicle event recorder systems arranged as described here, it is now possible for a driver to be involved in a collision at 10 o'clock in the morning, and a video record can be made available at the Department of Motor Vehicles by 10:02 (or before). When a vehicle event recorder is coupled to remote servers as described, and where such remote servers provide need-specific web applications to interested parties, very valuable data handling processes are enabled.

Other workstations 68, similarly having access to the internet, can be used by other users that require information sorted and arranged for their specific application. These users may include entities like vehicle leasing companies. It may be a condition of the lease that the vehicles are used in a safe and proper manner, and a leasing company with access to information provided by these servers through the related web applications can easily check the status of the vehicles it owns.

Very relevant are also applications that relate to vehicle fleet management and administration. Scheduling functions, tracking systems, maintenance operations, etcetera can be organized and provided via computer programs, whereby a human fleet administrator/manager can read and manipulate data with the functionality made possible by systems of the present invention. Thus, a large fleet of vehicles operated in southern California may be maintained and organized by a fleet manager in New York City. With systems according to the present invention, it is no longer the case that the fleet manager has to be situated in the same location as the vehicles, because the systems of the present invention include a highly efficient capture and sorting of information that is provided automatically and directly from fleet vehicles to a remote server, which may be accessed by fleet administrator/managers anywhere.

Maintenance workers might use a particular web application that compiles information relating to wear and tear on the vehicle. Oil changes, tire rotation, wheel alignment, and other general maintenance actions should be performed in view of conditions which can be managed and detected by the server. It is a common practice that oil should be changed every 3000 miles. However, this rule of thumb does not reflect very accurately the conditions upon which oil should really be changed. Oil suffers degradation from many factors, and particularly from excessive heat and high ‘rpm’. So the system could set some oil change guidance based on detailed use of the vehicle rather than a simple mileage scheme. If the car runs with high revolutions on many hot days, the oil may need to be changed before 3000 miles. Conversely, if the car is gently driven with low engine stress on mildly cool days, it may not be necessary to change the oil until 4500 miles. Oil changes is a very simplistic example, but is provided here to show that web applications can be used for more accurate guidance in the maintenance of vehicles. Data collected throughout the vehicle service day, recorded and stored, later transmitted to the server, and properly sorted and analyzed by a web application can be read by a maintenance engineer to keep a vehicle in good condition. While fleet management is an application of the embodiment described herein, other interested parties may have a similarly important stake in the fleet vehicle data management systems of the present invention.

Another very important application relates to teenage use of vehicles. Systems are provided for use by families that have new drivers, generally teenagers learning to drive. Teenagers account for a disproportionately large percentage of vehicle accidents, including vehicle accidents that result in deaths. However, when young new drivers know that they are being observed, that their actions will be recorded, and they will be held accountable, better decisions may be made with regard to driving. Thus, parents might be premium subscribers to a service that will benefit them by protecting their children. Special applications can be prepared and delivered by an application host, whereby parents can inquire as to the use of vehicles by their teenagers. Accordingly, families can benefit from reviewing detailed vehicle use information including video data that is easily accessible from the privacy of one's own home by way of an internet server arranged in accordance with these embodiments.

FIG. 7 shows a block diagram which corresponds to the concept of independent web applications and services provided at a server. Communication space 71 is associated with parking facility 72, such as a common parking lot that is enveloped by a space in which a reliable communications connection can be made via wireless radio 73. Further, broadband connection 74 to the internet couples the communication space 71 to the system server whereby video data collected at various vehicle event recorders may be transferred to the server.

A server computer is arranged to provide computer services including, but not limited to, a general computational service, a database service, an e-mail service, and a web application service, among others. For the purpose of the present embodiments, a primary function of the server lies within an applications host that may be arranged as a web server, under which a plurality of independent applications 75, or interdependent applications, are executed and served to clients 76 via TCP/IP or other suitable protocol 77. By way of example, the applications host of the server can be deployed as a Microsoft Internet Information Services IIS system. In conjunction with IIS, the Microsoft.Net technologies including the .NET framework and ASP.NET are suitable for providing the web applications and web services described herein.

In a first example, a special application 78 is provided to perform download operations. When a vehicle enters a communication space and toggles a proximity trigger, a service module within the vehicle event recorder makes appropriate calls to the server, and more specifically the applications host, and also to the download application. The download application responds to these calls by executing operations that permit the vehicle event recorder to transfer data to the server for further processing. Thus, one application of an applications host includes a module to communicate and execute transfers with various vehicle event recorders. Other applications, which belong to the same application host, may operate independently of the download module. Further, these other applications may be designed to be addressed by application clients that are not vehicle event recorders, but rather other entities or interested parties.

Thus, the system server includes computer code programming modules in the form of various web applications, each having access to data downloaded from vehicle event recorders. Web applications consumers or web “applications clients” connect to and communicate with these web applications by way of internet protocol or TCP/IP, by way of example. These web applications, each perhaps independent of any other, provide information exchange function with these application clients.

These systems include application-specific software suitable for fashioning network communications as ‘web request’ actions and for transmitting those web requests to the server whose network address is known a priori to vehicle event recorder systems. Web requests directed to a specific URL (Uniform Resource Locator, or ‘internet address’) may be transmitted from the microprocessor of a vehicle event recording unit. These web requests include web requests directed to specific services, which may be provided at a system server and may include software upgrades, registry updates, scheduling information, as well as data download operations. Thus, a vehicle event recorder that has collected data through its service day is in a condition to download that data once it enters a suitable download or communication space and receives its network address assignment to enable communications with the prescribed servers. Servers are ‘known’ to vehicle event recorder units because their computers are programmed with a predetermined server network address or means of obtaining it dynamically. Further, a vehicle recorder unit computer is programmed to form appropriately designed web requests, so that the recorder unit can properly interact with the web applications and services provided by the server via the application host.

In preferred versions, the vehicle event recorder unit includes special programming, which anticipates available web services. Such programming is suitable for making action requests to the server and is operable for processing returned responses that are in a particular format. Thus, the vehicle event recorder unit is specifically programmed with prior knowledge of services available at the server. Accordingly, vehicle event recorders cooperate together with established proprietary servers.

Some web services provided by servers are not generic and cannot be processed by other computer clients that have no prior knowledge of the available services and of the proprietary interfaces or formats with which responses are returned. Thus, the server is a specially configured to communicate with the vehicle event recorders. The server is also configured to run self contained local applications 79, which may be directed to data analysis and statistical services that operate on collected data without interaction of outside parties.

Another module of the server includes an e-mail server 710 system, which can be arranged to respond to special conditions and events occurring in related applications 711, whereby e-mail messages can be sent on the internet.

FIG. 8 provides another illustration related to applications of server 81 and to an applications host in accordance with vehicle event recorder systems of the embodiments described herein. Communication space 82, which supports wireless downloads from vehicles having captured video data, is coupled to a remotely located server by way of communication path 83 that may include the internet. The communication space is directly coupled to a web application 84 arranged specifically for communication with vehicle event recorders, whereby it is operable for downloading collected data. The application may be called by vehicle event recorders through a specific network address or URL. Other application clients, such as those described above, may be fashioned as ‘read-only’ clients 85, whereby the server provides data for analysis and use by interested parties, but those clients do not provide data to the server. These clients each communicate with the application host, by way of various paths 86, which may include unique URLs to appropriately direct communication traffic to the various particular applications 87. An entirely different type of application/service, herein known as a ‘push’ type service 88, conversely is arranged to provide information to the server. Information from a push service is transmitted by way of the internet, via explicit URLs or other routing protocol to particular applications 89 arranged to receive information.

Push services may provide information to applications that process this type of information and respond thereto by amending are augmenting certain records maintained by the entire system. For example, information from weather reporting agencies may be transmitted to these applications. The applications then sort and process the weather information, taking important pertinent parts, for example, weather conditions in certain areas at a certain time may be associated with a particular accident recorded by a vehicle event recorder.

Other push services may include those that contain information from vehicle manufacturers, including include updates related to particular model vehicles which may be part of a vehicle fleet. In response to receiving such information, managers can alter the way they use and deploy these vehicles. Vehicle recall information may be transmitted that enables a fleet manager to respond by applying an appropriate fix as part of an automated maintenance program.

FIG. 9 describes push services of two different types that are arranged with various network connections. System server 91, including specially designed applications 92 in communication with various interested party applications clients 93, also includes specially arranged application 94, which receives information from push service 95. In addition to this arrangement, other applications 96 are configured to communicate with push services, whereby information may be received over the internet while at the same time these push services can provide information directly to vehicle event recorders over communication path 98. These systems anticipate not only push services that are in communication directly with the server applications host, but also, at the same time, push services that are in communication directly with vehicle event recorder head units, without first passing through any applications at the server.

A principle of the vehicle event recorder systems described herein includes the arrangement where a single server provides management and service to a plurality of independent fleets.

Independent fleets of vehicles managed by separate entities may share a single server having a common applications host. While fleet members log-on with separate identities, the separate fleets may log-on to the same application host which is provided with powerful membership management facility to maintain separation between various fleets and associated data received from members of the fleet.

A first fleet is associated with communication space 100 served by wireless radio 101 to communicate with fleet members 102 and 103. A vehicle event recorder 104 deployed within the fleet member includes connection manager 105. Connection manager 105 includes computer programming code to properly identify and authenticate the vehicle as a member of a particular fleet when in communication with centralized server 106. A separate fleet may include truck vehicle 107 as a member, in a separate communication space 108 which is physically removed from communication space 100. Should vehicle 109 from the first fleet enter the communication space associated with another fleet, the condition may be designated as a non-authorized condition. In this event, communications and downloads would be prevented. Thus vehicle event recorders of these embodiments include connections managers appropriately suited to manage membership operations and distinguish between vehicles of particular fleets and communication spaces designated for authorized download operations.

FIG. 11 illustrates communication spaces and the networks which may exist within a single communication space. Since the size of vehicle fleets in use may exceed hundreds of vehicles, it may be necessary to arrange a communication space which is quite extensive. In these situations, it is impossible to serve a communication space that could accommodate the entire fleet of hundreds of vehicles with a single radio transmitter of the WiFi type, because these transmitters have limited ranges not compatible with the parking facilities required to accommodate large fleets. Accordingly, it is a single parking facility of a large area can be served by a plurality of WiFi transmitters networked together. FIG. 11 shows remote server 111, including database 112, application host 113, and at least one web application 114 coupled to the internet and further to extended communication space 115. Communication space 115 is comprised of a plurality of individual communication spaces 116 spatially removed but overlapping one another to operate in conjunction with each other to service an extended and large parking facility 117.

FIG. 12 illustrates the proximity trigger. By entering the communication space and piercing the envelope of the radio transceiver range boundary, the vehicle causes the proximity trigger to be toggled. Server 121 is in broadband communication 122 with radio transceiver 123 serving communication space 124. Moving vehicle 125 transits from outside of the communication space to the interior of same communication space to cause proximity trigger 126 to be activated. Upon detection of the proximity trigger being toggled, vehicle event recorder 127 equipped with connection manager 128 responds by providing handshaking and authentication with the radio transceiver and further performs a download function, in which data is passed to the remote server in direct response to the vehicle entering the download space.

Thus, the actions of vehicles trigger and cause network responses without intervention of human operators. The arrangement of these systems provides an automated means of passing video data collected in vehicle event recorders to remotely located servers for further processing.

While some wireless communications systems, such as WiFi and WiMax systems, have a large bandwidth, wireless telephone networks do not. Since vehicle event recording systems tend to capture data in extremely large amounts, wireless telephone networks are sometime not suitable for this application. However, systems can be arranged whereby only a select or ‘abbreviated’ dataset is passed over the wireless telephone network.

It is easy to appreciate that some types of data are well-suited for transmission over low bandwidth communication links that can cover a large area. On the contrary, transmission of high-resolution, live video is may be difficult. On the other hand, where a system is devised such that an abbreviated set of video images is occasionally transmitted, the wireless telephone network may operate reasonably well as a communications link in these systems.

In a first illustrative example, an event recorder duly writes data to a local storage in accordance with the operation described herein. This set of data, extremely large in quantity, is suitable for local storage but not for transmission over the bandwidth of limited wireless telephone type networks. Data written to the local storage could be subject to a download action when the vehicle returns for high-bandwidth communications link. However, while connected via a wireless telephone communications network, the system can be arranged to transmit bandwidth limited subsets of data including selected video frames.

Non-video data recorded by the system may be suitable for continuous transmission. Non-video data can be very small in size and easily transmitted over low bandwidth communications links. For example, a numeric, position-only measurement data may result in a dataset that is quite small and easily transmitted via a mobile phone network. Thus, a vehicle event recorder system which captures a position measurement can be arranged to transmit that type of information over the bandwidth-limited communications link into the system network.

An abbreviated video sequence may include a video sequence that can be detected by some preset mechanism. For example, an ‘impact detector’ might trigger a transmission of a limited amount of video data, for example three seconds of video prior to the impact and up to three seconds after the impact. This limited dataset might not be transmitted in real-time, but it can be transmitted within a reasonable time and passed to the server while a vehicle is still in the field.

Systems arranged to download data as described, i.e. in limited datasets, may be deployed with mobile telephone networks as a communication link. In such cases, an alternative trigger system may be employed.

In the situation where fleet vehicles never rest or ‘park’, a download station may operate as one in which a vehicle merely enters, performs a download and then leaves without a full parking, stopping, or storage action.

While embodiments of the invention are described above, it will be apparent to one skilled in the art that various changes and modifications may be made. The appended claims are intended to cover all such changes and modifications that fall within the true spirit and scope of the invention.

Claims

1. A vehicle fleet management system comprising: a vehicle event recorder unit configured for mounting in a vehicle, the vehicle event recorder unit comprising: a video camera having a field-of-view that includes an environment about the vehicle, the video camera configured to detect video images of the environment about the vehicle; anda radio transceiver, the vehicle event recorder unit configured to record video images responsive to an event trigger exceeding a predetermined threshold;a vehicle on-board data system including one or more sensors configured to generate output signals conveying vehicle feedback information, the vehicle feedback information including information related to one or more of vehicle lights, an engine of the vehicle, a drive train of the vehicle, a transmission of the vehicle, vehicle brakes, and/or vehicle steering, the vehicle event recorder unit configured to record vehicle feedback information that corresponds to the recorded video images;a network coupled to the Internet and including at least one wireless transceiver having a corresponding communication space;a server computer coupled to the network; andat least one workstation coupled to the network, wherein the vehicle event recorder unit is configured to automatically establish a wireless link with the network when the vehicle enters the communication space,wherein the vehicle event recorder unit is configured to initiate transmission of the recorded video images and the vehicle feedback information to the server computer over the wireless link, andwherein the workstation is configured to facilitate, via the server, adjustment of the predetermined threshold and video camera image control settings through a web browser interface presented to a user on the workstation over the wireless link.
2. The vehicle fleet management system of claim 1, wherein the vehicle event recorder unit further comprises: a connection manager configured to transfer the video images and the vehicle feedback information to the server via the radio transceiver of the vehicle event recorder unit.
3. The vehicle fleet management system of claim 2, wherein the connection manager further comprises a server network address lookup system.
4. The vehicle fleet management system of claim 2, wherein the connection manager further comprises a network address client.
5. The vehicle fleet management system of claim 2, wherein the connection manager further facilitates an authentication process.
6. The vehicle fleet management system of claim 5, wherein the connection manager further comprises a prescribed server network address.
7. The vehicle fleet management system of claim 5, wherein the connection manager further comprises a proximity trigger configured to provide a triggering indication to the connection manager responsive to detection of a radio signal such that the connection manager transfers the video images and the vehicle feedback information to the server responsive to receiving the triggering indication.
8. The vehicle fleet management system of claim 1, further comprising at least one audio microphone and recorder.
9. The vehicle fleet management system of claim 1, wherein the network comprises a WiFi or WiMax transceiver and a wireline connection from the WiFi or WiMax transceiver to the Internet.
10. The vehicle fleet management system of claim 9, wherein the communication space encompasses a parking facility suitable for accommodating a vehicle fleet.
11. The vehicle fleet management system of claim 9, wherein the communication space encompasses a parking facility suitable for storage of vehicles.
12. The vehicle fleet management system of claim 1, wherein the server computer comprises a web application arranged to exchange data with the vehicle event recorder unit.
13. The vehicle fleet management system of claim 1, further comprising a plurality of vehicle event recorder units, a first group of the plurality of vehicle event recorder units being associated with a first vehicle fleet, and a second group of the plurality of vehicle event recorder units being associated with a second, independent vehicle fleet.
14. The vehicle fleet management system of claim 13, wherein the communication space includes first and second distinct and physically removed communication spaces, the first communication space being associated with the first fleet and the second communication space associated with the second fleet.
15. The vehicle fleet management system of claim 14, wherein the server computer is in respective communication with the vehicle event recorder units of the first and second groups via the first and second communication spaces.
16. The vehicle fleet management system of claim 15, wherein the vehicle event recorder units associated with the first fleet are not authorized to communicate with the second communication space.
17. The vehicle fleet management system of claim 1, wherein the wireless communication space comprises a cellular network.
18. The vehicle fleet management system of claim 1, wherein the vehicle event recorder unit includes a user interface configured to receive entry and/or selection of information from the vehicle operator that identifies the vehicle operator while the vehicle operator is in the vehicle, and wherein the vehicle event recorder unit is configured to transmit the information that identifies the vehicle operator with the recorded video images and the vehicle feedback information to the server computer over the wireless link.
19. A method for monitoring a vehicle, the method comprising: recording video images responsive to an event trigger exceeding a predetermined threshold, wherein the recording is performed by a vehicle event recorder unit configured for mounting in a vehicle, the vehicle event recorder unit comprising: a video camera having a field-of-view that includes an environment about the vehicle that is configured to detect the video images, the video images including video images of the environment about the vehicle; anda radio transceiver;generating, with one or more sensors of a vehicle on-board data system, output signals conveying vehicle feedback information, the vehicle feedback information including information related to one or more of vehicle lights, an engine of the vehicle, a drive train of the vehicle, a transmission of the vehicle, vehicle brakes, and/or vehicle steering, the vehicle event recorder unit configured to record vehicle feedback information that corresponds to the recorded video images;automatically establishing a wireless link between the vehicle event recorder unit and a network when the vehicle enters a communication space, the network being coupled to the Internet and including at least one wireless transceiver having a corresponding communication space;transmitting the recorded video images and the vehicle feedback information to a server computer over the wireless link; andfacilitating adjustment of the predetermined threshold and video camera image control settings through a web browser interface presented to a user on a workstation associated with the user over the wireless link.
20. The method of claim 19, wherein the wireless communication space comprises a cellular network.
21. The method of claim 19, further comprising receiving entry and/or selection of information from a vehicle operator that identifies the vehicle operator while the vehicle operator is in the vehicle, and transmitting the information that identifies the vehicle operator with the recorded video images and the vehicle feedback information to the server computer over the wireless link.

PCT Information

Filing Document	Filing Date	Country	Kind	371c Date
PCT/US2006/047042	12/8/2006	WO	00	10/3/2008

Publishing Document	Publishing Date	Country	Kind
WO2007/067772	6/14/2007	WO	A

US Referenced Citations (881)

Number	Name	Date	Kind
673203	Freund	Apr 1901	A
673795	Hammer	May 1901	A
673907	Johnson	May 1901	A
676075	McDougall	Jun 1901	A
679511	Richards	Jul 1901	A
681036	Burg	Aug 1901	A
681283	Waynick	Aug 1901	A
681998	Swift	Sep 1901	A
683155	Thompson	Sep 1901	A
683214	Mansfield	Sep 1901	A
684276	Lonergan	Oct 1901	A
685082	Wood	Oct 1901	A
685969	Campbell	Nov 1901	A
686545	Selph	Nov 1901	A
689849	Brown	Dec 1901	A
691982	Sturgis	Jan 1902	A
692834	Davis	Feb 1902	A
694781	Prinz	Mar 1902	A
2943141	Knight	Jun 1960	A
3634866	Meyer	Jan 1972	A
3781824	Caiati	Dec 1973	A
3812287	Lemelson	May 1974	A
3885090	Rosenbaum	May 1975	A
3992656	Joy	Nov 1976	A
4054752	Dennis	Oct 1977	A
4072850	McGlynn	Feb 1978	A
4258421	Juhasz	Mar 1981	A
4271358	Schwarz	Jun 1981	A
4276609	Patel	Jun 1981	A
4280151	Tsunekawa	Jul 1981	A
4281354	Conte	Jul 1981	A
4401976	Stadelmayr	Aug 1983	A
4409670	Herndon	Oct 1983	A
4420773	Toyoda	Dec 1983	A
4425097	Owens	Jan 1984	A
4456931	Toyoda	Jun 1984	A
4489351	d'Alayer de Costemore	Dec 1984	A
4496995	Colles	Jan 1985	A
4500868	Tokitsu	Feb 1985	A
4528547	Rodney	Jul 1985	A
4533962	Decker	Aug 1985	A
4558379	Huetter	Dec 1985	A
4588267	Pastore	May 1986	A
4593313	Nagasaki	Jun 1986	A
4621335	Bluish	Nov 1986	A
4625210	Sagl	Nov 1986	A
4630110	Cotton	Dec 1986	A
4632348	Keesling	Dec 1986	A
4638289	Zottnik	Jan 1987	A
4646241	Ratchford	Feb 1987	A
4651143	Yamanaka	Mar 1987	A
4671111	Lemelson	Jun 1987	A
4718685	Kawabe	Jan 1988	A
4754255	Sanders	Jun 1988	A
4758888	Lapidot	Jul 1988	A
4763745	Eto	Aug 1988	A
4785474	Bernstein	Nov 1988	A
4789904	Peterson	Dec 1988	A
4794566	Richards	Dec 1988	A
4804937	Barbiaux	Feb 1989	A
4806931	Nelson	Feb 1989	A
4807096	Skogler	Feb 1989	A
4814896	Heitzman	Mar 1989	A
4837628	Sasaki	Jun 1989	A
4839631	Tsuji	Jun 1989	A
4843463	Michetti	Jun 1989	A
4843578	Wade	Jun 1989	A
4853856	Hanway	Aug 1989	A
4853859	Morita	Aug 1989	A
4866616	Takeuchi	Sep 1989	A
4876597	Roy	Oct 1989	A
4883349	Mittelhaeuser	Nov 1989	A
4896855	Furnish	Jan 1990	A
4926331	Windle	May 1990	A
4930742	Schofield	Jun 1990	A
4936533	Adams	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	Jan 1991	A
4992943	McCracken	Feb 1991	A
4993068	Piosenka	Feb 1991	A
4995086	Lilley	Feb 1991	A
5012335	Cohodar	Apr 1991	A
5027104	Reid	Jun 1991	A
5046007	McCrery	Sep 1991	A
5050166	Cantoni	Sep 1991	A
5056056	Gustin	Oct 1991	A
5057820	Markson	Oct 1991	A
5096287	Kakinami	Mar 1992	A
5100095	Haan	Mar 1992	A
5111289	Lucas	May 1992	A
5140434	Van Blessinger et al.	Aug 1992	A
5140436	Blessinger	Aug 1992	A
5140438	Kurahashi et al.	Aug 1992	A
5144661	Shamosh	Sep 1992	A
5178448	Adams	Jan 1993	A
5185700	Bezos	Feb 1993	A
5196938	Blessinger	Mar 1993	A
5223844	Mansell	Jun 1993	A
5224211	Roe	Jun 1993	A
5262813	Scharton	Nov 1993	A
5283433	Tsien	Feb 1994	A
5294978	Katayama	Mar 1994	A
5305214	Komatsu	Apr 1994	A
5305216	Okura	Apr 1994	A
5308247	Dyrdek	May 1994	A
5309485	Chao	May 1994	A
5311197	Sorden	May 1994	A
5321753	Gritton	Jun 1994	A
5327288	Wellington	Jul 1994	A
5330149	Haan	Jul 1994	A
5343527	Moore	Aug 1994	A
5353023	Mitsugi	Oct 1994	A
5361326	Aparicio	Nov 1994	A
5387926	Bellan	Feb 1995	A
5388045	Kamiya	Feb 1995	A
5388208	Weingartner	Feb 1995	A
5404330	Lee	Apr 1995	A
5408330	Squicciarini	Apr 1995	A
5422543	Weinberg	Jun 1995	A
5430431	Nelson	Jul 1995	A
5430432	Camhi	Jul 1995	A
5435184	Pineroli	Jul 1995	A
5445024	Riley	Aug 1995	A
5445027	Zoerner	Aug 1995	A
5446659	Yamawaki	Aug 1995	A
5455625	Englander	Oct 1995	A
5455716	Suman	Oct 1995	A
5465079	Bouchard	Nov 1995	A
5473729	Bryant	Dec 1995	A
5477141	Naether	Dec 1995	A
5495242	Kick	Feb 1996	A
5495243	McKenna	Feb 1996	A
5497419	Hill	Mar 1996	A
5499182	Ousborne	Mar 1996	A
5504482	Schreder	Apr 1996	A
5513011	Matsumoto	Apr 1996	A
5515285	Garrett	May 1996	A
5519260	Washington	May 1996	A
5521633	Nakajima	May 1996	A
5523811	Wada	Jun 1996	A
5526269	Ishibashi	Jun 1996	A
5530420	Tsuchiya	Jun 1996	A
5532678	Kin	Jul 1996	A
5537156	Katayama	Jul 1996	A
5539454	Williams	Jul 1996	A
5541590	Nishio	Jul 1996	A
5544060	Fujii	Aug 1996	A
5546191	Hibi	Aug 1996	A
5546305	Kondo	Aug 1996	A
5548273	Nicol	Aug 1996	A
5552990	Ihara	Sep 1996	A
5559496	Dubats	Sep 1996	A
5568211	Bamford	Oct 1996	A
5570087	Lemelson	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	Dec 1996	A
5586130	Doyle	Dec 1996	A
5590948	Moreno	Jan 1997	A
5596382	Bamford	Jan 1997	A
5596647	Wakai	Jan 1997	A
5600775	King	Feb 1997	A
5608272	Tanguay	Mar 1997	A
5610580	Lai	Mar 1997	A
5612686	Takano	Mar 1997	A
5631638	Kaspar	May 1997	A
5638273	Coiner	Jun 1997	A
5642106	Hancock	Jun 1997	A
5646856	Kaesser	Jul 1997	A
5652706	Morimoto	Jul 1997	A
RE35590	Bezos	Aug 1997	E
5654892	Fujii	Aug 1997	A
5659355	Barron	Aug 1997	A
5666120	Kline	Sep 1997	A
5667176	Zamarripa	Sep 1997	A
5669698	Veldman	Sep 1997	A
5671451	Takahashi	Sep 1997	A
5677979	Squicciarini	Oct 1997	A
5680117	Arai	Oct 1997	A
5680123	Lee	Oct 1997	A
5686765	Washington	Nov 1997	A
5686889	Hillis	Nov 1997	A
5689442	Swanson	Nov 1997	A
5696705	Zykan	Dec 1997	A
5706362	Yabe	Jan 1998	A
5706909	Bevins	Jan 1998	A
5712679	Coles	Jan 1998	A
5717456	Rudt	Feb 1998	A
5719554	Gagnon	Feb 1998	A
5758299	Sandborg	May 1998	A
5781101	Stephen	Jul 1998	A
5781145	Williams	Jul 1998	A
5784007	Pepper	Jul 1998	A
5784021	Oliva	Jul 1998	A
5784521	Nakatani	Jul 1998	A
5790403	Nakayama	Aug 1998	A
5790973	Blaker	Aug 1998	A
5793308	Rosinski	Aug 1998	A
5793420	Schmidt	Aug 1998	A
5793739	Tanaka	Aug 1998	A
5793985	Natarajan	Aug 1998	A
5794165	Minowa	Aug 1998	A
5797134	McMillan	Aug 1998	A
5798458	Monroe	Aug 1998	A
5800040	Santo	Sep 1998	A
5802545	Coverdill	Sep 1998	A
5802727	Blank	Sep 1998	A
5805079	Lemelson	Sep 1998	A
5813745	Fant	Sep 1998	A
5815071	Doyle	Sep 1998	A
5815093	Kikinis	Sep 1998	A
5819198	Peretz	Oct 1998	A
5825284	Dunwoody	Oct 1998	A
5825412	Hobson	Oct 1998	A
5844505	Van Ryzin	Dec 1998	A
5845733	Wolfsen	Dec 1998	A
5867802	Borza	Feb 1999	A
5877897	Schofield	Mar 1999	A
5896167	Omae	Apr 1999	A
5897602	Mizuta	Apr 1999	A
5897606	Miura	Apr 1999	A
5899956	Chan	May 1999	A
5901806	Takahashi	May 1999	A
5914748	Parulski	Jun 1999	A
5919239	Fraker	Jul 1999	A
5926210	Hackett	Jul 1999	A
5928291	Jenkins et al.	Jul 1999	A
5938321	Bos	Aug 1999	A
5946404	Bakshi	Aug 1999	A
5948038	Daly	Sep 1999	A
5959367	OFarrell	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	Dec 1999	A
6011492	Garesche	Jan 2000	A
6028528	Lorenzetti	Feb 2000	A
6037860	Zander	Mar 2000	A
6037977	Peterson	Mar 2000	A
6041410	Hsu	Mar 2000	A
6049079	Noordam	Apr 2000	A
6057754	Kinoshita	May 2000	A
6060989	Gehlot	May 2000	A
6064792	Fox	May 2000	A
6067488	Tano	May 2000	A
6076026	Jambhekar	Jun 2000	A
6084870	Wooten et al.	Jul 2000	A
6088635	Cox	Jul 2000	A
6092008	Bateman	Jul 2000	A
6092021	Ehlbeck	Jul 2000	A
6092193	Loomis	Jul 2000	A
6100811	Hsu	Aug 2000	A
6111254	Eden	Aug 2000	A
6118768	Bhatia	Sep 2000	A
6122738	Millard	Sep 2000	A
6141611	Mackey et al.	Oct 2000	A
6144296	Ishida	Nov 2000	A
6147598	Murphy	Nov 2000	A
6151065	Steed	Nov 2000	A
6163338	Johnson	Dec 2000	A
6163749	McDonough	Dec 2000	A
6167186	Kawasaki	Dec 2000	A
6170742	Yacoob	Jan 2001	B1
6181373	Coles	Jan 2001	B1
6182010	Berstis	Jan 2001	B1
6185490	Ferguson	Feb 2001	B1
6195605	Tabler	Feb 2001	B1
6200139	Clapper	Mar 2001	B1
6208919	Barkesseh	Mar 2001	B1
6211907	Scaman	Apr 2001	B1
6218960	Ishikawa	Apr 2001	B1
6246933	Bague	Jun 2001	B1
6246934	Otake	Jun 2001	B1
6252544	Hoffberg	Jun 2001	B1
6253129	Jenkins	Jun 2001	B1
6259475	Ramachandran	Jul 2001	B1
6263265	Fera	Jul 2001	B1
6266588	McClellan	Jul 2001	B1
6298290	Abe	Oct 2001	B1
6300875	Schafer	Oct 2001	B1
6324450	Iwama	Nov 2001	B1
6333759	Mazzilli	Dec 2001	B1
6337622	Sugano	Jan 2002	B1
6349250	Hart	Feb 2002	B1
6353734	Wright et al.	Mar 2002	B1
6356823	Iannotti	Mar 2002	B1
6360147	Lee	Mar 2002	B1
6366207	Murphy	Apr 2002	B1
6389339	Just	May 2002	B1
6389340	Rayner	May 2002	B1
6400835	Lemelson	Jun 2002	B1
6405112	Rayner	Jun 2002	B1
6405132	Breed	Jun 2002	B1
6408232	Cannon	Jun 2002	B1
6411874	Morgan	Jun 2002	B2
6421080	Lambert	Jul 2002	B1
6434510	Callaghan	Aug 2002	B1
6449540	Rayner	Sep 2002	B1
6456321	Ito	Sep 2002	B1
6459988	Fan	Oct 2002	B1
6470241	Yoshikawa	Oct 2002	B2
6472771	Frese	Oct 2002	B1
6490513	Fish	Dec 2002	B1
6493650	Rodgers	Dec 2002	B1
6505106	Lawrence	Jan 2003	B1
6507838	Syeda-Mahmood	Jan 2003	B1
6508400	Ishifuji	Jan 2003	B1
6516256	Hartmann	Feb 2003	B1
6518881	Monroe	Feb 2003	B2
6525672	Chainer	Feb 2003	B2
6529159	Fan	Mar 2003	B1
6535804	Chun	Mar 2003	B1
6552682	Fan	Apr 2003	B1
6556905	Mittelsteadt	Apr 2003	B1
6559769	Anthony	May 2003	B2
6574538	Sasaki	Jun 2003	B2
6575902	Burton	Jun 2003	B1
6580373	Ohashi	Jun 2003	B1
6580983	Laguer-Diaz	Jun 2003	B2
6593848	Atkins, III	Jul 2003	B1
6594576	Fan	Jul 2003	B2
6611740	Lowrey et al.	Aug 2003	B2
6611755	Coffee	Aug 2003	B1
6624611	Kirmuss	Sep 2003	B2
6629029	Giles	Sep 2003	B1
6629030	Klausner	Sep 2003	B2
6636791	Okada	Oct 2003	B2
6664922	Fan	Dec 2003	B1
6665613	Duvall	Dec 2003	B2
6679702	Rau	Jan 2004	B1
6684137	Takagi	Jan 2004	B2
6694483	Nagata	Feb 2004	B1
6701234	Vogelsang	Mar 2004	B1
6714894	Tobey	Mar 2004	B1
6718239	Rayner	Apr 2004	B2
6721640	Glenn	Apr 2004	B2
6721652	Sanqunetti	Apr 2004	B1
6728612	Carver	Apr 2004	B1
6732031	Lightner et al.	May 2004	B1
6732032	Banet et al.	May 2004	B1
6735503	Ames	May 2004	B2
6737954	Chainer	May 2004	B2
6738697	Breed	May 2004	B2
6739078	Morley	May 2004	B2
6741168	Webb	May 2004	B2
6745153	White	Jun 2004	B2
6747692	Patel	Jun 2004	B2
6748305	Klausner	Jun 2004	B1
6760757	Lundberg	Jul 2004	B1
6762513	Landgraf	Jul 2004	B2
6795017	Puranik	Sep 2004	B1
6795111	Mazzilli	Sep 2004	B1
6795759	Doyle	Sep 2004	B2
6798743	Ma	Sep 2004	B1
6804590	Sato	Oct 2004	B2
6810362	Adachi	Oct 2004	B2
6812831	Ikeda	Nov 2004	B2
6819989	Maeda	Nov 2004	B2
6831556	Boykin	Dec 2004	B1
6832140	Fan	Dec 2004	B2
6832141	Skeen	Dec 2004	B2
6836712	Nishina	Dec 2004	B2
6842762	Raithel	Jan 2005	B2
6847873	Li	Jan 2005	B1
6850823	Eun	Feb 2005	B2
6859695	Klausner	Feb 2005	B2
6859705	Rao	Feb 2005	B2
6862524	Nagda	Mar 2005	B1
6865457	Mittelsteadt	Mar 2005	B1
6867733	Sandhu	Mar 2005	B2
6873261	Anthony	Mar 2005	B2
6882313	Fan	Apr 2005	B1
6882912	DiLodovico	Apr 2005	B2
6894606	Forbes	May 2005	B2
6895248	Akyol	May 2005	B1
6898492	De Leon	May 2005	B2
6898493	Ehrman	May 2005	B2
6919823	Lock	Jul 2005	B1
6922566	Puranik	Jul 2005	B2
6928348	Lightner et al.	Aug 2005	B1
6931309	Phelan	Aug 2005	B2
6947817	Diem	Sep 2005	B2
6950122	Mirabile	Sep 2005	B1
6954223	Miyazawa	Oct 2005	B2
6988034	Marlatt et al.	Jan 2006	B1
7003289	Kolls	Feb 2006	B1
7012632	Freeman	Mar 2006	B2
7020548	Saito	Mar 2006	B2
7023333	Blanco	Apr 2006	B2
7039510	Gumpinger	May 2006	B2
7076348	Bucher	Jul 2006	B2
7079927	Tano	Jul 2006	B1
7082359	Breed	Jul 2006	B2
7082382	Rose et al.	Jul 2006	B1
7088387	Freeman	Aug 2006	B1
7095782	Cohen	Aug 2006	B1
7098812	Hirota	Aug 2006	B2
7100190	Johnson	Aug 2006	B2
7113853	Hecklinger	Sep 2006	B2
7117075	Larschan	Oct 2006	B1
7119832	Blanco	Oct 2006	B2
7138904	Dutu	Nov 2006	B1
7155321	Bromley	Dec 2006	B2
7177738	Diaz	Feb 2007	B2
7209833	Isaji et al.	Apr 2007	B2
7239252	Kato	Jul 2007	B2
7254482	Kawasaki	Aug 2007	B2
7265663	Steele	Sep 2007	B2
7266507	Simon	Sep 2007	B2
7272179	Siemens	Sep 2007	B2
7308341	Schofield	Dec 2007	B2
7317974	Luskin et al.	Jan 2008	B2
7343306	Bates	Mar 2008	B1
7348895	Lagassey	Mar 2008	B2
7349027	Endo	Mar 2008	B2
7370261	Winarski	May 2008	B2
7382933	Dorai	Jun 2008	B2
7386376	Basir	Jun 2008	B2
7389178	Raz	Jun 2008	B2
7457693	Olsen et al.	Nov 2008	B2
7471189	Vastad	Dec 2008	B2
7471192	Hara	Dec 2008	B2
7536457	Miller	May 2009	B2
7548586	Mimar	Jun 2009	B1
7561054	Raz	Jul 2009	B2
7584033	Mittelsteadt	Sep 2009	B2
7623754	McKain	Nov 2009	B1
7659827	Gunderson	Feb 2010	B2
7659835	Jung	Feb 2010	B2
7667731	Kreiner	Feb 2010	B2
7702442	Takenaka	Apr 2010	B2
7725216	Kim	May 2010	B2
7768548	Silvernail et al.	Aug 2010	B2
7769499	McQuade	Aug 2010	B2
7783956	Ko	Aug 2010	B2
7804426	Etcheson	Sep 2010	B2
7821421	Tamir	Oct 2010	B2
7853376	Peng	Dec 2010	B2
7868912	Venetianer	Jan 2011	B2
7893958	DAgostino	Feb 2011	B1
7940250	Forstall	May 2011	B2
7941258	Mittelsteadt	May 2011	B1
7974748	Goerick	Jul 2011	B2
8054168	McCormick	Nov 2011	B2
8068979	Breed	Nov 2011	B2
8090598	Bauer	Jan 2012	B2
8113844	Huang	Feb 2012	B2
8139820	Plante	Mar 2012	B2
8140265	Grush	Mar 2012	B2
8140358	Ling	Mar 2012	B1
8152198	Breed	Apr 2012	B2
8239092	Plante	Aug 2012	B2
8269617	Cook	Sep 2012	B2
8311858	Everett	Nov 2012	B2
8314708	Gunderson	Nov 2012	B2
8321066	Becker	Nov 2012	B2
8373567	Denson	Feb 2013	B2
8417562	Siemens	Apr 2013	B1
8442690	Goldstein	May 2013	B2
8471701	Yariv	Jun 2013	B2
8508353	Cook	Aug 2013	B2
8538696	Cassanova	Sep 2013	B1
8538785	Coleman	Sep 2013	B2
8564426	Cook	Oct 2013	B2
8564446	Gunderson	Oct 2013	B2
8571755	Plante	Oct 2013	B2
8577703	McClellan	Nov 2013	B2
8606492	Botnen	Dec 2013	B1
8635557	Geise	Jan 2014	B2
8676428	Richardson	Mar 2014	B2
8744642	Nemat-Nasser	Jun 2014	B2
8775067	Cho	Jul 2014	B2
8781292	Ross	Jul 2014	B1
8803695	Denson	Aug 2014	B2
8805110	Rhoads	Aug 2014	B2
8849501	Cook	Sep 2014	B2
8855847	Uehara	Oct 2014	B2
8868288	Plante	Oct 2014	B2
8880279	Plante	Nov 2014	B2
8892310	Palmer	Nov 2014	B1
8989959	Plante	Mar 2015	B2
8996234	Tamari	Mar 2015	B1
8996240	Plante	Mar 2015	B2
9047721	Botnen	Jun 2015	B1
9183679	Plante	Nov 2015	B2
9201842	Plante	Dec 2015	B2
9208129	Plante	Dec 2015	B2
9226004	Plante	Dec 2015	B1
9240079	Lambert	Jan 2016	B2
20010005217	Hamilton	Jun 2001	A1
20010005804	Rayner	Jun 2001	A1
20010018628	Jenkins	Aug 2001	A1
20010020204	Runyon	Sep 2001	A1
20010052730	Baur	Dec 2001	A1
20020019689	Harrison et al.	Feb 2002	A1
20020027502	Mayor	Mar 2002	A1
20020029109	Wong	Mar 2002	A1
20020035422	Sasaki	Mar 2002	A1
20020044225	Rakib	Apr 2002	A1
20020059453	Eriksson	May 2002	A1
20020061758	Zarlengo	May 2002	A1
20020067076	Talbot	Jun 2002	A1
20020087240	Raithel	Jul 2002	A1
20020091473	Gardner	Jul 2002	A1
20020105438	Forbes	Aug 2002	A1
20020107619	Klausner	Aug 2002	A1
20020111725	Burge	Aug 2002	A1
20020111756	Modgil	Aug 2002	A1
20020118206	Knittel	Aug 2002	A1
20020120374	Douros	Aug 2002	A1
20020135679	Scaman	Sep 2002	A1
20020138587	Koehler	Sep 2002	A1
20020163532	Thomas	Nov 2002	A1
20020169529	Kim	Nov 2002	A1
20020169530	Laguer-Diaz	Nov 2002	A1
20020183905	Maeda	Dec 2002	A1
20030016753	Kim	Jan 2003	A1
20030028298	Macky	Feb 2003	A1
20030053433	Chun	Mar 2003	A1
20030055557	Dutta	Mar 2003	A1
20030065805	Barnes	Apr 2003	A1
20030067541	Joao	Apr 2003	A1
20030079041	Parrella	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
20030112133	Webb	Jun 2003	A1
20030125854	Kawasaki	Jul 2003	A1
20030144775	Klausner	Jul 2003	A1
20030152145	Kawakita	Aug 2003	A1
20030154009	Basir	Aug 2003	A1
20030158638	Yakes	Aug 2003	A1
20030177187	Levine	Sep 2003	A1
20030187704	Hashiguchi	Oct 2003	A1
20030191568	Breed	Oct 2003	A1
20030195678	Betters	Oct 2003	A1
20030214585	Bakewell	Nov 2003	A1
20030220835	Barnes	Nov 2003	A1
20030222880	Waterman	Dec 2003	A1
20040008255	Lewellen	Jan 2004	A1
20040033058	Reich	Feb 2004	A1
20040039503	Doyle	Feb 2004	A1
20040039504	Coffee	Feb 2004	A1
20040044452	Bauer	Mar 2004	A1
20040044592	Ubik	Mar 2004	A1
20040054444	Abeska	Mar 2004	A1
20040054513	Laird	Mar 2004	A1
20040054689	Salmonsen	Mar 2004	A1
20040064245	Knockeart	Apr 2004	A1
20040070926	Boykin	Apr 2004	A1
20040083041	Skeen	Apr 2004	A1
20040088090	Wee	May 2004	A1
20040103008	Wahlbin	May 2004	A1
20040103010	Wahlbin	May 2004	A1
20040104842	Drury	Jun 2004	A1
20040111189	Miyazawa	Jun 2004	A1
20040138794	Saito	Jul 2004	A1
20040145457	Schofield et al.	Jul 2004	A1
20040153244	Kellum	Aug 2004	A1
20040153362	Bauer	Aug 2004	A1
20040167689	Bromley	Aug 2004	A1
20040179600	Wells	Sep 2004	A1
20040181326	Adams et al.	Sep 2004	A1
20040184548	Kerbiriou	Sep 2004	A1
20040203903	Wilson	Oct 2004	A1
20040209594	Naboulsi	Oct 2004	A1
20040210353	Rice	Oct 2004	A1
20040230345	Tzamaloukas	Nov 2004	A1
20040230370	Tzamaloukas	Nov 2004	A1
20040230373	Tzamaloukas	Nov 2004	A1
20040230374	Tzamaloukas	Nov 2004	A1
20040233284	Lesesky	Nov 2004	A1
20040236474	Chowdhary	Nov 2004	A1
20040243285	Gounder	Dec 2004	A1
20040243308	Irish	Dec 2004	A1
20040243668	Harjanto	Dec 2004	A1
20040254689	Blazic	Dec 2004	A1
20040254698	Hubbard et al.	Dec 2004	A1
20040267419	Jeng	Dec 2004	A1
20050021199	Zimmerman	Jan 2005	A1
20050043869	Funkhouser	Feb 2005	A1
20050060070	Kapolka et al.	Mar 2005	A1
20050060071	Winner	Mar 2005	A1
20050065682	Kapadia	Mar 2005	A1
20050065716	Timko	Mar 2005	A1
20050073585	Ettinger	Apr 2005	A1
20050078423	Kim	Apr 2005	A1
20050088291	Blanco	Apr 2005	A1
20050099498	Lao	May 2005	A1
20050100329	Lao	May 2005	A1
20050102074	Kolls	May 2005	A1
20050125117	Breed	Jun 2005	A1
20050131585	Luskin	Jun 2005	A1
20050131595	Luskin	Jun 2005	A1
20050131597	Raz	Jun 2005	A1
20050136949	Barnes	Jun 2005	A1
20050137757	Phelan	Jun 2005	A1
20050137796	Gumpinger	Jun 2005	A1
20050146458	Carmichael et al.	Jul 2005	A1
20050149238	Stefani et al.	Jul 2005	A1
20050149259	Cherveny	Jul 2005	A1
20050152353	Couturier	Jul 2005	A1
20050159964	Sonnenrein	Jul 2005	A1
20050166258	Vasilevsky	Jul 2005	A1
20050171692	Hamblen	Aug 2005	A1
20050174217	Basir	Aug 2005	A1
20050182538	Phelan	Aug 2005	A1
20050182824	Cotte	Aug 2005	A1
20050185052	Raisinghani	Aug 2005	A1
20050185936	Lao	Aug 2005	A9
20050192749	Flann	Sep 2005	A1
20050197748	Holst et al.	Sep 2005	A1
20050200714	Marchese	Sep 2005	A1
20050203683	Olsen et al.	Sep 2005	A1
20050206741	Raber	Sep 2005	A1
20050209776	Ogino	Sep 2005	A1
20050212920	Evans	Sep 2005	A1
20050216144	Baldassa	Sep 2005	A1
20050228560	Doherty	Oct 2005	A1
20050233805	Okajima	Oct 2005	A1
20050251304	Cancellara	Nov 2005	A1
20050256681	Brinton	Nov 2005	A1
20050258942	Manasseh	Nov 2005	A1
20050264691	Endo	Dec 2005	A1
20050283284	Grenier	Dec 2005	A1
20060001671	Kamijo	Jan 2006	A1
20060007151	Ram	Jan 2006	A1
20060011399	Brockway	Jan 2006	A1
20060015233	Olsen	Jan 2006	A1
20060022842	Zoladek et al.	Feb 2006	A1
20060025897	Shostak	Feb 2006	A1
20060030986	Peng	Feb 2006	A1
20060040239	Cummins	Feb 2006	A1
20060047380	Welch	Mar 2006	A1
20060053038	Warren	Mar 2006	A1
20060055521	Blanco et al.	Mar 2006	A1
20060057543	Roald	Mar 2006	A1
20060058950	Kato	Mar 2006	A1
20060072792	Toda	Apr 2006	A1
20060078853	Lanktree	Apr 2006	A1
20060082438	Bazakos	Apr 2006	A1
20060092043	Lagassey	May 2006	A1
20060095175	deWaal et al.	May 2006	A1
20060095199	Lagassey	May 2006	A1
20060095349	Morgan	May 2006	A1
20060103127	Lie	May 2006	A1
20060106514	Liebl et al.	May 2006	A1
20060111817	Phelan	May 2006	A1
20060122749	Phelan	Jun 2006	A1
20060129578	Kim	Jun 2006	A1
20060142913	Coffee et al.	Jun 2006	A1
20060143435	Kwon	Jun 2006	A1
20060147187	Takemoto	Jul 2006	A1
20060161960	Benoit	Jul 2006	A1
20060168271	Pabari	Jul 2006	A1
20060178793	Hecklinger	Aug 2006	A1
20060180647	Hansen	Aug 2006	A1
20060184295	Hawkins	Aug 2006	A1
20060192658	Yamamura	Aug 2006	A1
20060200008	Moore-Ede	Sep 2006	A1
20060200305	Sheha	Sep 2006	A1
20060204059	Ido	Sep 2006	A1
20060209090	Kelly et al.	Sep 2006	A1
20060209840	Paatela	Sep 2006	A1
20060212195	Veith	Sep 2006	A1
20060215884	Ota	Sep 2006	A1
20060226344	Werth	Oct 2006	A1
20060229780	Underdahl	Oct 2006	A1
20060242680	Johnson	Oct 2006	A1
20060247833	Malhotra	Nov 2006	A1
20060253307	Warren	Nov 2006	A1
20060259218	Wu	Nov 2006	A1
20060261931	Cheng	Nov 2006	A1
20070001831	Raz	Jan 2007	A1
20070005404	Raz	Jan 2007	A1
20070027583	Tamir	Feb 2007	A1
20070027726	Warren	Feb 2007	A1
20070035632	Silvernail	Feb 2007	A1
20070043487	Krzystofczyk	Feb 2007	A1
20070120948	Fujioka	May 2007	A1
20070124332	Ballesty	May 2007	A1
20070127833	Singh	Jun 2007	A1
20070132773	Plante	Jun 2007	A1
20070135979	Plante	Jun 2007	A1
20070135980	Plante	Jun 2007	A1
20070136078	Plante	Jun 2007	A1
20070142986	Alaous	Jun 2007	A1
20070143499	Chang	Jun 2007	A1
20070150138	Plante	Jun 2007	A1
20070150140	Seymour	Jun 2007	A1
20070173994	Kubo	Jul 2007	A1
20070179691	Grenn	Aug 2007	A1
20070183635	Weidhaas	Aug 2007	A1
20070208494	Chapman	Sep 2007	A1
20070216521	Guensler	Sep 2007	A1
20070219685	Plante	Sep 2007	A1
20070219686	Plante	Sep 2007	A1
20070241874	Okpysh	Oct 2007	A1
20070244614	Nathanson	Oct 2007	A1
20070257781	Denson	Nov 2007	A1
20070257782	Etcheson	Nov 2007	A1
20070257804	Gunderson	Nov 2007	A1
20070257815	Gunderson	Nov 2007	A1
20070260677	DeMarco	Nov 2007	A1
20070263984	Sterner	Nov 2007	A1
20070268158	Gunderson	Nov 2007	A1
20070271105	Gunderson	Nov 2007	A1
20070273480	Burkman	Nov 2007	A1
20070279214	Buehler	Dec 2007	A1
20070299612	Kimura	Dec 2007	A1
20080035108	Ancimer	Feb 2008	A1
20080059019	Delia	Mar 2008	A1
20080071827	Hengel	Mar 2008	A1
20080111666	Plante	May 2008	A1
20080122603	Plante	May 2008	A1
20080143834	Comeau	Jun 2008	A1
20080147267	Plante et al.	Jun 2008	A1
20080157510	Breed	Jul 2008	A1
20080167775	Kuttenberger	Jul 2008	A1
20080169914	Albertson	Jul 2008	A1
20080177436	Fortson	Jul 2008	A1
20080195261	Breed	Aug 2008	A1
20080204556	deMiranda	Aug 2008	A1
20080211779	Pryor	Sep 2008	A1
20080234920	Nurminen	Sep 2008	A1
20080243389	Inoue	Oct 2008	A1
20080252412	Larsson	Oct 2008	A1
20080252485	Lagassey	Oct 2008	A1
20080252487	McClellan	Oct 2008	A1
20080269978	Shirole	Oct 2008	A1
20080281485	Plante	Nov 2008	A1
20080309762	Howard et al.	Dec 2008	A1
20080319604	Follmer	Dec 2008	A1
20090009321	McClellan	Jan 2009	A1
20090043500	Satoh	Feb 2009	A1
20090043971	Kim	Feb 2009	A1
20090051510	Follmer	Feb 2009	A1
20090138191	Engelhard	May 2009	A1
20090216775	Ratliff et al.	Aug 2009	A1
20090224869	Baker	Sep 2009	A1
20090290848	Brown	Nov 2009	A1
20090299622	Denaro	Dec 2009	A1
20090312998	Berckmans	Dec 2009	A1
20090326796	Prokhorov	Dec 2009	A1
20090327856	Mouilleseaux	Dec 2009	A1
20100030423	Nathanson	Feb 2010	A1
20100045451	Periwal	Feb 2010	A1
20100049516	Talwar	Feb 2010	A1
20100054709	Misawa	Mar 2010	A1
20100057342	Muramatsu	Mar 2010	A1
20100063672	Anderson	Mar 2010	A1
20100063680	Tolstedt	Mar 2010	A1
20100063850	Daniel	Mar 2010	A1
20100070175	Soulchin	Mar 2010	A1
20100076621	Kubotani	Mar 2010	A1
20100085193	Boss	Apr 2010	A1
20100085430	Kreiner	Apr 2010	A1
20100087984	Joseph	Apr 2010	A1
20100100315	Davidson	Apr 2010	A1
20100103165	Lee	Apr 2010	A1
20100104199	Zhang	Apr 2010	A1
20100149418	Freed	Jun 2010	A1
20100153146	Angell	Jun 2010	A1
20100157061	Katsman	Jun 2010	A1
20100191411	Cook	Jul 2010	A1
20100201875	Rood	Aug 2010	A1
20100220892	Kawakubo	Sep 2010	A1
20100250020	Lee	Sep 2010	A1
20100250021	Cook	Sep 2010	A1
20100250060	Maeda	Sep 2010	A1
20100250116	Yamaguchi	Sep 2010	A1
20100253918	Seder	Oct 2010	A1
20100268415	Ishikawa	Oct 2010	A1
20100283633	Becker	Nov 2010	A1
20100312464	Fitzgerald	Dec 2010	A1
20110035139	Konlditslotis	Feb 2011	A1
20110043624	Haug	Feb 2011	A1
20110060496	Nielsen	Mar 2011	A1
20110077028	Wilkes	Mar 2011	A1
20110091079	Yu-Song	Apr 2011	A1
20110093159	Boling	Apr 2011	A1
20110112995	Chang	May 2011	A1
20110121960	Tsai	May 2011	A1
20110125365	Larschan	May 2011	A1
20110130916	Mayer	Jun 2011	A1
20110140884	Santiago	Jun 2011	A1
20110153367	Amigo	Jun 2011	A1
20110161116	Peak	Jun 2011	A1
20110166773	Raz	Jul 2011	A1
20110173015	Chapman	Jul 2011	A1
20110208428	Matsubara	Aug 2011	A1
20110212717	Rhoads	Sep 2011	A1
20110213628	Peak	Sep 2011	A1
20110224891	Iwuchukwu	Sep 2011	A1
20110251752	DeLarocheliere	Oct 2011	A1
20110251782	Perkins	Oct 2011	A1
20110254676	Marumoto	Oct 2011	A1
20110257882	McBurney	Oct 2011	A1
20110273568	Lagassey	Nov 2011	A1
20110282542	Nielsen	Nov 2011	A9
20110283223	Vattinen et al.	Nov 2011	A1
20110304446	Basson	Dec 2011	A1
20120021386	Anderson	Jan 2012	A1
20120035788	Trepagnier	Feb 2012	A1
20120041675	Juliver	Feb 2012	A1
20120046803	Inou	Feb 2012	A1
20120071140	Oesterling	Mar 2012	A1
20120078063	Moore-Ede	Mar 2012	A1
20120081567	Cote	Apr 2012	A1
20120100509	Gunderson	Apr 2012	A1
20120109447	Yousefi	May 2012	A1
20120123806	Schumann	May 2012	A1
20120134547	Jung	May 2012	A1
20120150436	Rossano	Jun 2012	A1
20120176234	Taneyhill	Jul 2012	A1
20120190001	Knight	Jul 2012	A1
20120198317	Eppolito	Aug 2012	A1
20120210252	Fedoseyeva	Aug 2012	A1
20120277950	Plante	Nov 2012	A1
20120283895	Noda	Nov 2012	A1
20120330528	Schwindt	Dec 2012	A1
20130004138	Kilar	Jan 2013	A1
20130006469	Green	Jan 2013	A1
20130021148	Cook	Jan 2013	A1
20130028320	Gardner	Jan 2013	A1
20130030660	Fujimoto	Jan 2013	A1
20130073112	Phelan	Mar 2013	A1
20130073114	Nemat-Nasser	Mar 2013	A1
20130096731	Tamari	Apr 2013	A1
20130145269	Latulipe	Jun 2013	A1
20130151980	Lee	Jun 2013	A1
20130170762	Marti	Jul 2013	A1
20130197774	Denson	Aug 2013	A1
20130274950	Richardson	Oct 2013	A1
20130317711	Plante	Nov 2013	A1
20130332004	Gompert et al.	Dec 2013	A1
20130345927	Cook	Dec 2013	A1
20130345929	Bowden	Dec 2013	A1
20140025225	Armitage	Jan 2014	A1
20140025254	Plante	Jan 2014	A1
20140032062	Baer	Jan 2014	A1
20140046550	Palmer	Feb 2014	A1
20140047371	Palmer	Feb 2014	A1
20140058583	Kesavan	Feb 2014	A1
20140089504	Scholz	Mar 2014	A1
20140094992	Lambert	Apr 2014	A1
20140098228	Plante	Apr 2014	A1
20140152828	Plante	Jun 2014	A1
20140226010	Molin	Aug 2014	A1
20140232863	Paliga	Aug 2014	A1
20140279707	Joshua	Sep 2014	A1
20140280204	Avery	Sep 2014	A1
20140300739	Mimar	Oct 2014	A1
20140309849	Ricci	Oct 2014	A1
20140335902	Guba	Nov 2014	A1
20140336916	Yun	Nov 2014	A1
20150035665	Plante	Feb 2015	A1
20150057836	Plante	Feb 2015	A1
20150105934	Palmer	Apr 2015	A1
20150112542	Fuglewicz	Apr 2015	A1
20150112545	Binion	Apr 2015	A1
20150134226	Palmer	May 2015	A1
20150135240	Shibuya	May 2015	A1
20150156174	Fahey	Jun 2015	A1
20150189042	Sun	Jul 2015	A1
20150222449	Salinger	Aug 2015	A1
20150317846	Plante	Nov 2015	A1

Foreign Referenced Citations (69)

Number	Date	Country
2469728	Dec 2005	CA
2469728	Dec 2005	CA
2692415	Aug 2011	CA
2692415	Aug 2011	CA
4416991	Nov 1995	DE
20311262	Sep 2003	DE
202005008238	Sep 2005	DE
102004004669	Dec 2005	DE
102004004669	Dec 2005	DE
0708427	Apr 1996	EP
0840270	May 1998	EP
0848270	May 1998	EP
1170697	Jan 2002	EP
1324274	Jul 2003	EP
1355278	Oct 2003	EP
1 427 165	Jun 2004	EP
1818873	Aug 2007	EP
2104075	Sep 2009	EP
2320387	May 2011	EP
2407943	Jan 2012	EP
2268608	Jan 1994	GB
2402530	Dec 2004	GB
2402530	Dec 2004	GB
2451485	Feb 2009	GB
2447184	Jun 2011	GB
2446994	Aug 2011	GB
58085110	May 1983	JP
S5885110	May 1983	JP
62091092	Apr 1987	JP
S6291092	Apr 1987	JP
S62166135	Jul 1987	JP
02056197	Feb 1990	JP
H0256197	Feb 1990	JP
H04257189	Sep 1992	JP
H05137144	Jun 1993	JP
5294188	Nov 1993	JP
H08124069	May 1996	JP
H09163357	Jun 1997	JP
H09272399	Oct 1997	JP
10076880	Mar 1998	JP
H1076880	Mar 1998	JP
2002191017	Jul 2002	JP
2002191017	Jul 2002	JP
1000588169	Dec 2000	KR
8809023	Nov 1988	WO
9005076	May 1990	WO
9427844	Dec 1994	WO
9600957	Jan 1996	WO
9701246	Jan 1997	WO
WO 9726750	Jul 1997	WO
9937503	Jul 1999	WO
WO 9940545	Aug 1999	WO
9962741	Dec 1999	WO
0007150	Feb 2000	WO
0028410	May 2000	WO
0048033	Aug 2000	WO
0077620	Dec 2000	WO
0123214	Apr 2001	WO
0125054	Apr 2001	WO
0146710	Jun 2001	WO
03045514	Jun 2003	WO
2006022824	Mar 2006	WO
2006022824	Mar 2006	WO
2007067767	Jun 2007	WO
2007109091	Sep 2007	WO
2009081234	Jul 2009	WO
2011055743	May 2011	WO
2013072939	May 2013	WO
2013159853	Oct 2013	WO

Non-Patent Literature Citations (131)

Entry
International Search Report for PCT/US2006/47042, Mailed Feb. 25, 2008 (2 pages).
Written Opinion of the International Searching Authority for PCT/US2006/47042, Mailed Feb. 25, 2008 (5 pages).
Drivecam, User's Manual for DriveCam Video System's HindSight 20/20 Software Version 4.0 (2003).
Rayner et al., Final Report for Innovations Deserving Exploratory Analysis (IDEAS) Intelligent Transportation Systems (ITS) Programs Project 84, I-Witness Black Box Recorder (Nov. 2001).
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.
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/297,889, 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/593,882, 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.
Bill, ‘DriveCam—FAQ’, Dec. 12, 2003.
Bill Siuru, ‘DriveCam Could Save You Big Bucks’, Land Line Magazine, May-Jun. 2000.
Chris Woodyard, ‘Shuttles save with DriveCam’, Dec. 9, 2003.
Dan Carr, Flash Video Template: Video Presentation with Navigation, Jan. 16, 2006, http://www.adobe.com/devnet/fiash/articles/vidtemplate—mediapreso—flash8.html.
David Cullen, ‘Getting a real eyeful’, Fleet Owner Magazine, Feb. 2002.
David Maher, ‘DriveCam Brochure Folder’, Jun. 6, 2005.
David Maher, “DriveCam Brochure Folder”, Jun. 8, 2005.
David Vogeleer et al., Macromedia Flash Professional 8UNLEASHED (Sams Oct. 12, 2005).
Del Lisk, ‘DriveCam Training Handout Ver4’, Feb. 3, 2005.
DriveCam, Inc.'s Infringement Contentions Exhibit A, U.S. Pat. No. 6,389,340, Document 34.1, Oct. 20, 2011.
DriveCam, Inc.'s Infringement Contentions Exhibit B, U.S. Pat. No. 7,659,827. Aug. 19, 2011.
DriveCam, Inc.'s Infringement Contentions Exhibit B, U.S. Pat. No. 7,804,426, Document 34.2, Oct. 20, 2011.
DriveCam, Inc.'s Infringement Contentions Exhibit C, U.S. Pat. No. 7,659,827, Document 34.3, Oct. 20, 2011.
DriveCam, Inc.'s Infringement Contentions Exhibit C, U.S. Pat. No. 7,804,426. Aug. 19, 2011.
DriveCam, Inc.'s Infringement Contentions Exhibit D, Document 34.4, Oct. 20, 2011.
DriveCam—Illuminator Data Sheet, Oct. 2, 2004.
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.
DriveCam Driving Feedback System, Mar. 15, 2004.
DriveCam Extrinsic Evidence with Patent LR 4.1 .a Disclosures, Nov. 3, 2011.
DriveCam Extrinsic Evidence with Patent LR 4.1 .a Disclosures, Nov. 8, 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, Document 55, filed Jan. 1, 2012, pp. 86-103.
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 55, filed Jan. 3, 2012, pp. 86-103.
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.
GE published its VCR User's 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.
I/O 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&Categorys- ub.--Code=coaching)., printed from site on Jan. 11, 2012.
Interior Camera Data Sheet, Oct. 26, 2001.
International Search Report and Written Opinion issued in PCT/US07/68325 on Feb. 27, 2008.
International Search Report and Written Opinion issued in PCT/US07/68328 on Oct. 15, 2007.
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 for PCT/US2006/47055, Mailed Mar. 20, 2008 (2 pages).
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. Pat. 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 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 Claim Construction Worksheet, U.S. Pat. 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 Worksheet, U.S. Pat. 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 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 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 20120’, 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.
Kitchin, Charles. “Understanding accelerometer scale factor and offset adjustments.” Analog Devices (1995).
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.
Passenger Transportation Mode Brochure, May 2, 2005.
Patent Abstracts of Japan vol. 007, No. 180 (P-215), Aug. 9, 1983 (Aug. 9, 1983) & JP 58 085110 A (Mitsuhisa Ichikawa), May 21, 1983 (May 21, 1983).
Patent Abstracts of Japan vol. 011, No. 292 (E-543), Sep. 19, 1987 (Sep. 19, 1987) & JP 62 091092 A (OK ENG:KK), Apr. 25, 1987 (Apr. 25, 1987).
Patent Abstracts of Japan vol. 012, No. 001 (M-656), Jan. 6, 1988 (Jan. 6, 1988) & JP 62 166135 A (Fuji Electric Co Ltd), Jul. 22, 1987 (Jul. 22, 1987).
Patent Abstracts of Japan vol. 014, No. 222 (E-0926), May 10, 1990 (May 10, 1990) & JP 02 056197 A (Sanyo Electric Co Ltd), Feb. 26, 1990 (Feb. 26, 1990).
Patent Abstracts of Japan vol. 017, No. 039 (E-1311), Jan. 25, 1993 (Jan. 25, 1993) & JP 04 257189 A (Sony Corp), Sep. 11, 1992 (Sep. 11, 1992).
Patent Abstracts of Japan vol. 017, No. 521 (E-1435), Sep. 20, 1993 (Sep. 20, 1993) & JP 05 137144 A (Kyocera Corp), Jun. 1, 1993 (Jun. 1, 1993).
Patent Abstracts of Japan vol. 1996, No. 09, Sep. 30, 1996 (Sep. 30, 1996) & JP 08 124069 A (Toyota Motor Corp), May 17, 1996 (May 17, 1996).
Patent Abstracts of Japan vol. 1997, No. 10, Oct. 31, 1997 (Oct. 31, 1997) & JP 09 163357 A (Nippon Soken Inc), Jun. 20, 1997 (Jun. 20, 1997).
Patent Abstracts of Japan vol. 1998, No. 02, Jan. 30, 1998 (Jan. 30, 1998) & JP 09 272399 A (Nippon Soken Inc), Oct. 21, 1997 (Oct. 21, 1997).
Patent Abstracts of Japan vol. 1998, No. 8, Jun. 30, 1998 (Jun. 30, 1998) & JP 10 076880 A (Muakami Corp), Mar. 24, 1998 (Mar. 24, 1998).
PCT/US2010/022012, Invitation to Pay Additional Fees with Communication of Partial International Search, Jul. 21, 2010.
Peter G. Thurlow, Letter (including exhibits) Regarding Patent Owner's Response to Initial Office Action in Ex Parte Reexamination, Mar. 27, 2012.
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’, Apr. 17, 2006.
Quinn Maughan, ‘Enterprise Services’, Apr. 7, 2006.
Quinn Maughan, ‘Hindsight Installation Guide’, Sep. 29, 2005.
Quinn Maughan, ‘Hindsight Users Guide’, Jun. 7, 2005.
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.
The DriveCam, Nov. 8, 2002.
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.
U.S. Appl. No. 12/691,639, entitled ‘Drive Risk Assessment System and Method Employing Selectively Automatic Event Scoring’, filed Jan. 21, 2010.
U.S. Appl. No. 11/377,157, filed Mar. 16, 2006 entitled, “Vehicle Event Recorder Systems and Networks Having Parallel Communications Links”.
U.S. Appl. No. 11/377,167, filed Mar. 16, 2006 entitled, “Vehicle Event Recorder System and Networks Having Integrated Cellular Wireless Communications Systems”.
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, CBC 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.
Written Opinion issued in PCT/US07/68328 on Oct. 15, 2007.
Written Opinion of the International Searching Authority for PCT/US2006/47055, Mailed Mar. 20, 2008 (5 pages).
PCT International Search Report and Written Opinion for PCT/IB16/51863, dated Sep. 16, 2016.
Trivinci Systems, LLC, “Race-Keeper System User Guide”, V1 .1.02, Jan. 2011, p. 21.

Related Publications (1)

	Number	Date	Country
	20090157255 A1	Jun 2009	US

Continuations (1)

	Number	Date	Country
Parent	11296906	Dec 2005	US
Child	12096591		US

Vehicle event recorder systems

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications

Term Extension

Abstract