2010 International Conference on Autonomous and Intelligent Systems, AIS 2010 2010
DOI: 10.1109/ais.2010.5547041
|View full text |Cite
|
Sign up to set email alerts
|

Hierarchical agent-based command and control system for autonomous underwater vehicles

Abstract: Over the past decades, the design and development of mission based Autonomous Underwater Vehicle (AUV) continues to challenge researchers. Although AUV technology has matured and commercial systems have appeared in the market, a generic yet robust AUV command and control (C2) system still remains a key research area. This paper presents a command and control system architecture for modular AUVs. We particularly focus on the design and development of a generic control and software architecture for a single modu… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
10
0
2

Year Published

2012
2012
2021
2021

Publication Types

Select...
4
3
1

Relationship

1
7

Authors

Journals

citations
Cited by 25 publications
(12 citation statements)
references
References 9 publications
0
10
0
2
Order By: Relevance
“…Subsequent scenarios will include multi-vehicle configurations. 4. To extend the tests to on-air trials with realscale prototypes.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…Subsequent scenarios will include multi-vehicle configurations. 4. To extend the tests to on-air trials with realscale prototypes.…”
Section: Discussionmentioning
confidence: 99%
“…These approaches generally assign an agent to a functional system module (navigator, pilot, vision processor, etc.). Thus, the agents are defined as key components of the infrastructure that supports the system [1][2][3][4][5][6][7].…”
Section: Literature Reviewmentioning
confidence: 99%
“…The ASACS architecture focused on the control at the vehicle level, and included a plan dispatch subsystem, also called captain in the proposal, responsible for activating the items from the mission plan, that is, the tasks (or actions) that are part of it. This work has been used as a reference for other architectures, like the hybrid Command and Control (C2) architecture proposed in [25,26]. In this later work, the authors borrowed "captain" idea from the ASACS proposal, and included it at the supervisory level of a three-layer architecture, being responsible for the start, coordination, supervision and control of the execution of the mission.…”
Section: Related Workmentioning
confidence: 99%
“…Our previous work [7] adopted a similar approach and high level mission tasks were handled by only two agents at the Supervisory level. This has suffered from the "fat" agent problem where one agent is overloaded with various tasks and resulted in reliability and maintainability issues.…”
Section: Introductionmentioning
confidence: 99%