Method and system for detecting duration and cause of border delays
A method at a computing device for attributing a cause to a border delay, the method including determining that a vehicle has entered a border geofence; obtaining sensor data from the vehicle; and correlating the sensor data with the determining that the vehicle has entered the geofence to attribute the cause to the border delay.
1. A method at a computing device for attributing a cause to a border delay, the method comprising:
receiving third-party data, the third-party data comprising data from a border agency associated to a border crossing indicating a wait time at the border crossing;
determining a size of a border geofence around the border crossing based on the wait time, wherein the size of the border geofence is selected to include a traffic queue waiting to reach the border crossing;
receiving, from a vehicle, a report over an electronic communication network;
determining, from the report, that the vehicle has entered the border geofence;
obtaining sensor data of the vehicle from the report;
correlating the sensor data with the determining that the vehicle has entered the geofence to attribute the cause to the border delay;
assigning a cost for the border delay based on the cause; and
based on historic data and the cost for the border delay, sending instructions over the electronic communication network to active vehicles to change routes.
2. The method of claim 1 , wherein the sensor data includes a door opening event and the cause is an inspection.
3. The method of claim 1 , wherein the sensor data includes accelerometer readings showing repeated starts and stops, indicating a cause of traffic.
4. The method of claim 1 , further comprising:
calculating a shipping delay; and
providing a notification to a receiving company or customer of the shipping delay.
5. The method of claim 1 , further comprising storing the report from the vehicle and compiling historic data for the border crossing.
6. The method of claim 5 , wherein the computing device uses the historic data for future route planning for vehicles.
7. A computing device for attributing a cause to a border delay, the computing device comprising:
a processor; and
a communications subsystem,
wherein the computing device is configured to:
receive third-party data, the third-party data comprising data from a border agency associated to a border crossing indicating a wait time at the border crossing;
determine a size of a border geofence around the border crossing based on the wait time, wherein the size of the border geofence is selected to include a traffic queue waiting to reach the border crossing;
receive, from a vehicle, a report over an electronic communication network;
determine, from the report, that the vehicle has entered the border geofence;
obtain sensor data of the vehicle from the report;
correlate the sensor data with the determining that the vehicle has entered the geofence to attribute the cause to the border delay;
assign a cost for the border delay based on the cause; and
based on historic data and the cost for the border delay, sending instructions over the electronic communication network to active vehicles to change routes.
8. The computing device of claim 7 , wherein the sensor data includes a door opening event and the cause is an inspection.
9. The computing device of claim 7 , wherein the sensor data includes accelerometer readings showing repeated starts and stops, indicating a cause of traffic.
10. The computing device of claim 7 , wherein the computing device is further configured to:
calculate a shipping delay; and
provide a notification to a receiving company or customer of the shipping delay.
11. The computing device of claim 7 , wherein the computing device further stores the report from the vehicle and compiles historic data for the border crossing.
12. The computing device of claim 11 , wherein the computing device uses the historic data for future route planning for vehicles.
13. A non-transitory computer readable medium for storing instruction code, which, when executed by a processor of a computing device configured for attributing a cause to a border delay cause the computing device to:
receive third-party data, the third-party data comprising data from a border agency associated to a border crossing indicating a wait time at the border crossing;
determine a size of a border geofence around the border crossing based on the wait time, wherein the size of the border geofence is selected to include a traffic queue waiting to reach the border crossing;
receive, from a vehicle, a report over an electronic communication network;
determine, from the report, that the vehicle has entered the border geofence;
obtain sensor data of the vehicle from the report;
correlate the sensor data with the determining that the vehicle has entered the geofence to attribute the cause to the border delay;
assign a cost for the border delay based on the cause; and
based on historic data and the cost for the border delay, sending instructions over the electronic communication network to active vehicles to change routes.
14. The non-transitory computer readable medium of claim 13 , wherein the sensor data includes a door opening event and the cause is an inspection.
15. The non-transitory computer readable medium of claim 13 , wherein the sensor data includes accelerometer readings showing repeated starts and stops, indicating a cause of traffic.
16. The non-transitory computer readable medium of claim 13 , wherein the instruction code further causes the computing device to:
calculate a shipping delay; and
provide a notification to a receiving company or customer of the shipping delay.
17. The non-transitory computer readable medium of claim 13 , wherein the instruction code further causes the computing device to store the report from the vehicle and compiling historic data for the border crossing.
18. The non-transitory computer readable medium of claim 17 , wherein the instruction code further causes the computing device to use the historic data for future route planning for vehicles.