Vehicle Event Detector Wireless Data Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing fleet vehicle monitoring systems face challenges in efficiently transferring stored event data from vehicle-mounted event detectors to evaluation servers, particularly in conserving memory resources and ensuring timely data transfer, especially during driver changes or brief stops.
Innovation Solution
A method that involves capturing driving event data, monitoring a sensor output to determine when the vehicle is stationary, and transferring data to an access point or docking station when detected, with a backoff algorithm to conserve battery life and ensure data transfer only when the vehicle is stopped and in proximity to a communication point.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is transferred periodically from the event detector to the evaluation server, then data transfer reliability is improved, but memory resources in the vehicle-mounted device are consumed and battery power is drained
Solution Approach 1:
The system uses periodic action by implementing a backoff algorithm that schedules data transfer attempts at increasing time intervals after vehicle stop events. Instead of continuous or fixed-period transfers, the system waits progressively longer between transfer attempts (e.g., 1 minute, then 2 minutes, then 4 minutes), reducing energy consumption while maintaining data transfer reliability over time.
Solution Approach 2:
The system employs self-service by automatically determining transfer conditions based on vehicle stop detection and access point availability without requiring manual intervention. The event detector autonomously monitors sensor inputs, detects when the vehicle has stopped, searches for access points, and initiates data transfers only when conditions are favorable, eliminating the need for continuous manual control or high-frequency forced transfers.
2Loss of time
If data is transferred whenever the vehicle stops, then counseling effectiveness is improved, but unnecessary transfers are made when no access point is available
Solution Approach 1:
The system applies preliminary action by detecting vehicle stop events in advance and immediately initiating a search for access points. When a stop is detected, the system proactively queries for available access points before attempting data transfer, ensuring that transfers only occur when communication infrastructure is available. This prevents unnecessary transfer attempts while maintaining timely data delivery when conditions permit.
Solution Approach 2:
The system uses feedback by continuously monitoring access point availability and using this information to control data transfer decisions. The event detector receives feedback from access point search results and adjusts its behavior accordingly - transferring data when access points are available and suppressing transfers when they are not. This feedback loop optimizes transfer timing without requiring complex manual control logic.
3Productivity
If the event detector continuously checks for access points, then data transfer opportunities are maximized, but battery life is reduced
Solution Approach 1:
The system implements periodic action by checking for access points only at specific intervals triggered by vehicle stop events rather than continuously. The backoff algorithm defines periodic check intervals that increase over time (1 minute, 2 minutes, 4 minutes, etc.), maximizing data transfer opportunities when the vehicle is stopped while minimizing unnecessary checks during operation, thus preserving battery life.
Solution Approach 2:
The system applies dynamics by making the check frequency adaptive rather than fixed. The backoff algorithm dynamically adjusts the interval between access point checks based on whether previous transfers were successful and how long the vehicle has been stopped. This dynamic adjustment optimizes the balance between transfer frequency and battery consumption, checking more frequently when appropriate and less frequently when unnecessary.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
Driving events are captured at an event detector in a vehicle and stored in an associated data storage area. The output of a sensor in the vehicle is monitored, and the stored driving event data is sent to an evaluation server over a wireless communication network when a data transfer condition is detected. Driving event data is sent to the evaluation server when a predetermined output from the sensor is detected and the vehicle is in the transmission range of an access point. The predetermined sensor output may be from a motion sensor in the vehicle indicating that the vehicle is substantially stopped, or from a vehicle location sensor indicating that the vehicle is within transmission range of an access point.