Tolerating failures of continuous-valued sensors
ACM Transactions on Computer Systems (TOCS)
Intrusion detection systems and multisensor data fusion
Communications of the ACM
Guest Editorial: A Review of Worst-Case Execution-TimeAnalysis
Real-Time Systems - Special issue on worst-case execution-time analysis
DSN '02 Proceedings of the 2002 International Conference on Dependable Systems and Networks
Toward Easily Analyzable Sensor Networks via Structuring of Time-Triggered Tasks
FTDCS '03 Proceedings of the The Ninth IEEE Workshop on Future Trends of Distributed Computing Systems
DFuse: a framework for distributed data fusion
Proceedings of the 1st international conference on Embedded networked sensor systems
The Time-Triggered Ethernet (TTE) Design
ISORC '05 Proceedings of the Eighth IEEE International Symposium on Object-Oriented Real-Time Distributed Computing
Failsafe aspects of a decision unit inspired by cognitive sciences: the id without ego and super-ego
HSI'09 Proceedings of the 2nd conference on Human System Interactions
Machine perception in automation: a call to arms
EURASIP Journal on Embedded Systems - Special issue on networked embedded systems for energy management and buildings
Reducing impact of conflicting data in DDFS by using second order knowledge
SETN'10 Proceedings of the 6th Hellenic conference on Artificial Intelligence: theories, models and applications
| Hi-index | 0.00 |
In the literature there exist many proposed architectures for sensor fusion applications. This paper briefly reviews some of the most common approaches, i. e., the JDL fusion architecture, the Waterfall model, the Intelligence cycle, the Boyd loop, the LAAS architecture, the Omnibus model, Mr. Fusion, the DFuse framework, and the Time-Triggered Sensor Fusion Model, and categorizes them into abstract models, generic and rigid architectures. While an abstract model does not guide the designer in the concrete implementation, the generic architectures provide a generic design but leave open several design decisions regarding operating system, hardware, communication system, or database system. Rigid architectures specify at least some of these aspects and therefore provide existing hardware designs, tools, and source code at the cost of flexibility.