Navigational error accounts for half of the accidents and serious incidents in close to shore maritime transport in Norway predominantly due to the rapidly changing weather conditions and the dangerous nature of the narrow inshore waters found along the Norwegian coast. This creates a dependence on Differential Global Positioning System (DGPS) use and any disruption to this service can lead to an increased accident rate. The aim of this paper is to research the jamming vulnerability of existing maritime receivers and to understand if an upgrade to a multi-constellation or multi-frequency receiver would improve system resilience. The novelty of this work is a comparison of jamming resilience between different combinations of multiple constellations (GPS and Globalnaya Navigatsionnaya Sputnikovaya Sistema (GLONASS)) and multi-frequency Global Navigation Satellite System (GNSS) signals. This paper presents results from GNSS jamming trials conducted in the northern part of Norway, confirming previous research and indicating that typical maritime GPS receivers are easy to jam and may produce erroneous positional information. Results demonstrate that the single frequency multi-constellation receivers offer better jamming resilience than multi-frequency (L1 + L2) GPS receivers. Further, the GLONASS constellation demonstrated a better resilience than GPS. Results demonstrate a known correlation between GPS L1 and L2 frequencies, as well as a probable over-dependence on GPS for signal acquisition, meaning that no signal can be received without GPS L1 present. With these limitations in mind, the authors suggest that the most economic update to the single frequency GPS receivers, currently used for maritime applications, should be multi-constellation GPS + GLONASS receivers. This solution is cheaper and it also offer better jamming resistance for close to shore navigation than dual frequency receivers.
Email your librarian or administrator to recommend adding this journal to your organisation's collection.
* Views captured on Cambridge Core between <date>. This data will be updated every 24 hours.
Usage data cannot currently be displayed