Abstract Master Thesis

GNSS receivers can suffer severely from radio frequency interference (RFI). RFI can introduce errors in the position and time calculations or if the interference is very severe, can lead to a total loss of GNSS reception. This vulnerability of GNSS can have large implications on critical infrastructure such as power plants, telephony, aviation or search and rescue operations. RFI is a real threat to GNSS as many interfering incidents are reported every day.

A common type of RFI is chirp interference, which is a sweep over a wide range of frequencies that overlap with the frequencies used by GNSS. This is often emitted by cheap Personal Privacy Devices that can be bought online. The question in this thesis was how well such interference can be modelled and if modelling could help mitigation against it.

This thesis consists of two main parts. In the first part a novel estimator is proposed that assumes a mathematical model of a chirp and estimates its parameters from recordings of chirps. The estimator has shown to work well in simulations for chirps with an SNR of −9 dB or more. On real recordings the estimates were accurate for 66.7 % of the signals.

In the second part the estimator was used to derive a filter. The filter is based on the subtraction of a replica of the chirp interference from the received signal. It uses the proposed estimator to create the replica. In simulations, the filter is able to improve correlation strength by up to 7 dB. On real recordings the performance was worse as for only 46 % of the recordings the GNSS correlation was increased.

Both the estimator and filter have many ways in which they could be improved. The estimator can be improved to allow for more complex chirps, which would in turn improve the filter. Both can also be made more computationally efficient.

Furthermore, in order to get a better understanding of Personal Privacy Devices, one such device has been tested. It was found that the signal from the device was very unstable and changed much over time, it was also highly dependent on ambient temperature.


Really, WordPress?

Yes, really. This is one of those moments where you’ve been trying to achieve something for a number of years but still haven’t. Of course I was going to build my own website. First in PHP (remember Yii2?). That was off the table not much later. AngularJS + Loopback 3 was up next, this one actually got quite far, I had image upload and galleries all set up. Still however, it was not far from ready for release (I hadn’t understood the idea of rolling out straight away, agile, …, yet…). Of couse AngularJS is an archaic framework now, so that would have had to be replaced by – you guessed it – Angular (which one are we on yet?). Also, Loopback 3 has its flaws and NestJS seems a worthy opponent.

You get the point. I don’t have enough time to build a reasonable website for myselft, nor do I feel like it, nor can I decide on which framework to use. Enter simplicity. Who cares what it looks like, just pick something that works. And here we have it, 36 lines of YAML and the WordPress Docker image is spinning away. Thankfully I had some infrastructure in place from some earlier projects.

Anyway, here is a website. Expect some blog items (maybe, we’ll see) and some pictures (hopefully). If none of these things happen, at least you won’t get a 404 if you try to find me.