Hostname: page-component-8448b6f56d-m8qmq Total loading time: 0 Render date: 2024-04-19T18:36:09.107Z Has data issue: false hasContentIssue false

Using ontologies to aid navigation planning in autonomous vehicles

Published online by Cambridge University Press:  13 May 2004

CRAIG SCHLENOFF
Affiliation:
Nat. Inst. of Standards and Technology, 100 Bureau Drive, Stop 8230, Gaithersburg, MD 20899, USA; e-mail: craig.schlenoff@nist.gov
STEPHEN BALAKIRSKY
Affiliation:
Nat. Inst. of Standards and Technology, 100 Bureau Drive, Stop 8230, Gaithersburg, MD 20899, USA; e-mail: craig.schlenoff@nist.gov
MIKE USCHOLD
Affiliation:
Boeing, Phantom Works, P.O. Box 3707, m/s 7L-40, Seattle, WA 98124–2207, USA; e-mail: michael.f.uschold@boeing.com
RON PROVINE
Affiliation:
Boeing, Phantom Works, P.O. Box 3707, m/s 7L-40, Seattle, WA 98124–2207, USA; e-mail: michael.f.uschold@boeing.com
SCOTT SMITH
Affiliation:
Boeing, Phantom Works, P.O. Box 3707, m/s 7L-40, Seattle, WA 98124–2207, USA; e-mail: michael.f.uschold@boeing.com

Abstract

This paper explores the hypothesis that ontologies can be used to improve the capabilities and performance of on-board route planning for autonomous vehicles. We name a variety of general benefits that ontologies may provide, and list numerous specific ways that ontologies may be used in different components of our chosen infrastructure: the 4D/RCS system architecture developed at NIST. Our initial focus is on simple roadway driving scenarios where the controlled vehicle encounters objects in its path. Our approach is to develop an ontology of objects in the environment, in conjunction with rules for estimating the damage that would be incurred by collisions with the different objects in different situations. Automated reasoning is used to estimate collision damage; this information is fed to the route planner to help it decide whether to avoid the object. We describe our current experiments and plans for future work.

Type
Research Article
Copyright
© 2004 Cambridge University Press

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Footnotes

Certain software tools are identified in this paper in order to explain our research. Such identification does not imply recommendation or endorsement by the National Institute of Standards and Technology, nor does it imply that the software tools identified are necessarily the best available for the purpose.