Bayesian fault-tolerant protection level for multi-constellation navigation from integrity perspective

Aerospace Science and Technology(2022)

Cited 1|Views0
No score
Abstract
The multi-constellation is anticipated to enhance navigation performance by providing abundant satel-lites in view. However, with this comes the necessity of considering simultaneous fault events in integrity risk assessment when applying the receiver autonomous integrity monitoring. Meanwhile, the integrity monitoring efficacy remains vulnerable to the uncertainty of prior fault probability in multi-constellation navigation. In this regard, this paper proposes a Bayesian approach for the multi-constellation navigation at the user segment to strengthen the evaluation robustness of integrity risk. We bound the Bayesian pos-terior probability of fault hypotheses that comprise multiple concurrent faults (satellite or constellation faults) without assuming an optimistic prior fault distribution. This posterior probability bound leads to an associated Bayesian integrity risk. Following that, a fault-tolerant estimate accounting for multi-ple faults and nominal biases is derived to minimize the Bayesian integrity risk. Finally, we establish a Bayesian fault-tolerant protection level to bound the position estimate error and assess the integrity availability, resisting the uncertainty in the prior fault probability. Results validate the robustness im-provement the proposed Bayesian approach fulfills compared with the advanced receiver autonomous integrity monitoring in four cases. In addition, the Bayesian approach can lower the protection level at the cost of an offset from the least-square estimate while maintaining the same position accuracy.(c) 2022 Elsevier Masson SAS. All rights reserved.
More
Translated text
Key words
Advanced receiver autonomous integrity&nbsp,monitoring,Integrity support message,Sensitivity analysis,Probability bound
AI Read Science
Must-Reading Tree
Example
Generate MRT to find the research sequence of this paper
Chat Paper
Summary is being generated by the instructions you defined