Automatic creation, maintenance and monitoring of a guideway database

• US 8,260,480 B2
• Filed: 01/21/2009
• Issued: 09/04/2012
• Est. Priority Date: 01/17/2008
• Status: Active Grant

• Current Assignee: Lockheed Martin Corporation (Martin Marietta Corporation)
• Original Assignee: Lockheed Martin Corporation (Martin Marietta Corporation)
• Inventors: James, Demetri
• Primary Examiner(s): Tarcza, Thomas
• Assistant Examiner(s): MURSHED, NAGI M
• Application Number:
  US12/357,109
• Publication Number:
  US 20090187296A1
• Time in Patent Office: 1,322 Days
• Field of Search: None
• US Class Current: 701/19
• CPC Class Codes: B61L 2205/04 Satellite based navigation systems, e.g. global positioning system [GPS]
• CPC Class Codes: B61L 23/14 automatically operated
• CPC Class Codes: B61L 25/025 Absolute localisation, e.g. providing geodetic coordinates
• CPC Class Codes: G01C 21/005 with correlation of navigation data from several sources, e.g. map or contour matching G01C21/30 takes precedence

Abstract

A method and system for creating, maintain, and monitoring a guideway database is disclosed.

Claims

1. A method for updating an operational guideway database that is accessible by a computer, the method comprising:

generating, by the computer, a first estimate of vehicle position based on the operational guideway database for a guideway, wherein the first estimate is generated on-board a vehicle that operates on the guideway according to a block authorization that gives the vehicle authority to operate;

generating, by the computer, a second estimate of vehicle position, wherein the second estimate is independent of the operational guideway database, and wherein the second estimate is also generated on-board the vehicle that operates on the guideway;

comparing, by the computer, (i) a block occupancy corresponding to at least one of the first estimate of vehicle position and the second estimate of vehicle position with (ii) the block authorization for the vehicle; and

when the block occupancy and the block authorization match, updating, by the computer, the operational guideway database based on the second estimate of vehicle position.

2. The method of claim 1 wherein the first estimate of vehicle position is based on operational track-map data and at least one of:

Global Positioning System (“

GPS”

) data, inertial sensor data, and wheel tachometer data.

3. The method of claim 1 wherein the second estimate of vehicle position is based on at least one of:

Global Positioning System (“

GPS”

) data, inertial sensor data, and wheel tachometer data, but is not based on operational track-map data.

4. The method of claim 1 wherein the updating is further based on filtered data of the second estimate of vehicle position, wherein the filtered data is within predetermined limits.

5. A method for updating an operational guideway database that is accessible by at least one computer, the method comprising:

generating, by a first computer, a first estimate of vehicle position based on the operational guideway database for a guideway, wherein the first estimate is generated on-board a vehicle that operates on the guideway according to a block authorization that gives the vehicle authority to operate;

generating, by the first computer, a second estimate of vehicle position, wherein the second estimate is independent of the operational guideway database, and wherein the second estimate is also generated on-board the vehicle that operates on the guideway;

comparing, by a second computer, (i) a block occupancy corresponding to at least one of the first estimate of vehicle position and the second estimate of vehicle position with (ii) the block authorization for the vehicle, wherein the second computer is in a control center that communicates with the vehicle; and

when the block occupancy and the block authorization match, updating, by the second computer, the operational guideway database based on the second estimate of vehicle position.

6. The method of claim 5 wherein the first estimate of vehicle position is based on operational track-map data and at least one of:

Global Positioning System (“

GPS”

) data, inertial sensor data, and wheel tachometer data.

7. The method of claim 5 wherein the second estimate of vehicle position is based on at least one of:

GPS data, inertial sensor data, and wheel tachometer data, but is not based on operational track-map data.

8. The method of claim 5 wherein the updating is further based on filtered data of the second estimate of vehicle position, wherein the filtered data is within predetermined limits.

9. A method for updating an operational guideway database that is accessible by a computer, the method comprising:

generating, by the computer, a first estimate of vehicle position based on the operational guideway database for a guideway, wherein the first estimate is generated on-board a vehicle that operates on the guideway according to a block authorization that gives the vehicle authority to operate;

generating, by the computer, a second estimate of vehicle position, wherein the second estimate is independent of the operational guideway database, and wherein the second estimate is also generated on-board the vehicle that operates on the guideway;

comparing, by the computer, (i) a block occupancy corresponding to the second estimate of vehicle position with (ii) the block authorization for the vehicle;

when the block occupancy and the block authorization match, filtering the second estimate; and

when the filtered data is within predetermined limits, updating, by the computer, the operational guideway database based on the filtered second estimate of vehicle position.

10. The method of claim 9 wherein the first estimate of vehicle position is based on operational track-map data and at least one of:

Global Positioning System (“

GPS”

) data, inertial sensor data, and wheel tachometer data.

11. The method of claim 9 wherein the second estimate of vehicle position is based on at least one of:

Global Positioning System (“

GPS”

) data, inertial sensor data, and wheel tachometer data, but is not based on operational track-map data.