TRANSPORT MANAGEMENT SYSTEM

• US 20110231354A1
• Filed: 07/24/2008
• Published: 09/22/2011
• Est. Priority Date: 08/09/2007
• Status: Abandoned Application

• Current Assignee: Avego Ltd. (RELX PLC)
• Original Assignee: Avego Ltd. (RELX PLC)
• Inventors: O'Sullivan, Sean, Balmer, Greg, Appelbe, Harvey
• Application Number:
  US12/733,083
• Publication Number:
  US 20110231354A1
• Time in Patent Office: Days
• US Class Current: 706/46
• CPC Class Codes: G08G 1/0104 Measuring and analyzing of parameters relative to traffic conditions
• CPC Class Codes: G08G 1/20 Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles

Abstract

A car pooling transport management system (1) comprises a central server (2) having a bank of prediction servers (3) linked with a geographical model (4). Vehicle on-board units (OBUs, 6) have prediction clients (7) which communicate with the central server (2) via a mobile network (10). Each OBU (6) has a satellite locating system, in this case GPS-based, to track actual vehicle position. Each prediction client 7 develops a vehicle prediction model for the driver'"'"'s regular routes and communicates data concerning the vehicle prediction model to a prediction server (3) running on the central server (2), and in a normal transport/commuting mode compares in real time the position and timing of the actual mute of the vehicle against a route of the vehicle prediction model and transmits progress updates to the prediction server (3). The prediction server 3 consolidates the data from the various prediction clients 7 and builds a geographical model 4 for all of the OBUs 6 of the system 1. Using the geographical model (4), the prediction server (3) can continue to provide predictions of the vehicle'"'"'s progress, such that passenger requests can be processed without using the costly communication resource. Only when the prediction client (7) decides that vehicle progress has materially deviated from its predicted route, by comparing actual progress from say GPS with the local client prediction, does it communicate with the server 3.

Claims

1. A transport management system comprising:

a plurality of on-board units each for installation in a vehicle free to travel on different routes, and comprising a wireless transceiver;

a server;

wherein each on-board unit comprises a prediction client adapted to;

monitor vehicle actual position,

use monitored vehicle actual positions to generate a vehicle prediction model of routes frequently travelled by its associated vehicle,

transmit data concerning the vehicle prediction model to the server, and

transmit vehicle progress data updates to the server as the associated vehicle travels on a route

wherein the server is adapted to;

receive said data concerning the vehicle prediction model from each prediction client and use it to generate and maintain a geographical prediction model, and

use the geographical prediction model to generate predictions of each vehicle position, so that only infrequent vehicle progress updates are required from the prediction clients.

2. A transport management system as claimed in any preceding claim, wherein the on-board unit comprises a satellite tracking device, and the prediction client receives vehicle actual location data from said satellite tracking device.

3. A transport management system as claimed in either of claim 1 or 2, wherein the server is adapted to update the geographical model according to vehicle progress updates received from the clients, so that the geographical model is synchronised with the vehicle prediction models.

4. A transport management system as claimed in any of claims 1 to 3, wherein each prediction client is adapted to compare actual vehicle location with a predicted location, and to transmit vehicle progress updates to the server only if actual vehicle location differs from predicted location by more than a tolerance level.

5. A transport management system as claimed in claim 4, wherein the tolerance level is variable.

6. A transport management system as claimed in claim 5, wherein the tolerance level varies according to time and date.

7. A transport management system as claimed in any of claims 4 to 6, wherein each prediction client determines deviation according to a clustering algorithm.

8. A transport management system as claimed in any preceding claim, wherein the data transmitted by the client concerning the vehicle prediction model is an initial model.

9. A transport management system as claimed in any preceding claim, wherein the server is adapted to apply additional information when generating predictions of a vehicle'"'"'s position.

10. A transport management system as claimed in claim 9, wherein said additional information is derived from a common model of common traffic information including unusual delays on roads.

11. A transport management system as claimed in any preceding claim, wherein the prediction client is adapted to transmit an initial progress update indicating a route being commenced by an associated vehicle.

12. A transport management system as claimed in claim 11, wherein the prediction client is adapted to employ a stochastic methods to automatically determine a route being commenced without need for a user input.

13. A transport management system as claimed in any preceding claim, wherein each prediction client generates a server update when an associated vehicle passes predetermined stop locations along a predicted route.

14. A transport management system as claimed in any preceding claim, wherein the prediction client is adapted to build the vehicle prediction model on a framework of route stop data.

15. A transport management system as claimed in claim 14, wherein the server is adapted to perform automatic discovery of stops by recording stop data from progress updates from a first prediction client vehicle and applying said stop data to the a route for a second prediction client.

16. A transport management system as claimed in claim 15, wherein the server is adapted to apply regions around route stops and to identify a potential additional stop for the second vehicle if its route passes through said region.

17. A transport management system as claimed in any of claims 14 to 16, wherein each stop is given an attribute of being unidirectional or bi-directional.

18. A transport management system as claimed in any of claims 15 to 17, wherein the server is adapted to query the second prediction client before applying additional route data.

19. A transport management system as claimed in any of claims 14 to 18, wherein the vehicle prediction model comprises statistics for each of a plurality of time slots for each line between two stops.

20. A transport management system as claimed in claim 19, wherein for each time slot the following statistics are maintained on a running basis:

average time duration taken to move between the stops,

variability of the duration,

rolling link usage frequency indicating the probability that the link will be driven, and

relative link performance rating live feedback of the prediction performance for the link.

21. A computer readable medium comprising software code for performing operations of a system of any preceding claim when executing on a digital processor.