WP5-11 ACO - Revision history

Acorde: /* Description and Benefits */

2023-03-10T12:27:01Z

Description and Benefits

← Older revision		Revision as of 12:27, 10 March 2023
Line 27:		Line 27:

	In the WP5 of COMP4DRONES, ACORDE has tackled the challenge to enable '''anti-jamming and anti-spoofing capabilities''' for low-cost geo-referenced outdoor positioning and attituded estimation solution, i.e. GLAD+ [[WP3-15_2]], in a way that:		In the WP5 of COMP4DRONES, ACORDE has tackled the challenge to enable '''anti-jamming and anti-spoofing capabilities''' for low-cost geo-referenced outdoor positioning and attituded estimation solution, i.e. GLAD+ [[WP3-15_2]], in a way that:
	* ~~hold~~ a '''low-cost''' ~~of the solution (~~taking [~~[GLAD\| http~~://glad.acorde.com]~~] as a reference~~		* holds a '''low-cost''' taking as a reference ACORDE [https://glad.acorde.com \| GLAD] solution
	* a '''smooth integration''' ~~is enabled~~		* enables a '''smooth integration'''

	==How==		==How==

Acorde: /* Description and Benefits */

2023-03-10T12:23:40Z

Description and Benefits

← Older revision		Revision as of 12:23, 10 March 2023
Line 27:		Line 27:

	In the WP5 of COMP4DRONES, ACORDE has tackled the challenge to enable '''anti-jamming and anti-spoofing capabilities''' for low-cost geo-referenced outdoor positioning and attituded estimation solution, i.e. GLAD+ [[WP3-15_2]], in a way that:		In the WP5 of COMP4DRONES, ACORDE has tackled the challenge to enable '''anti-jamming and anti-spoofing capabilities''' for low-cost geo-referenced outdoor positioning and attituded estimation solution, i.e. GLAD+ [[WP3-15_2]], in a way that:
	* hold a '''low-cost''' of the solution (taking [[GLAD\| glad.acorde.com]] as a reference		* hold a '''low-cost''' of the solution (taking [[GLAD\| http://glad.acorde.com]] as a reference
	* a '''smooth integration''' is enabled		* a '''smooth integration''' is enabled

Acorde: /* Description and Benefits */

2023-03-10T12:23:21Z

Description and Benefits

← Older revision		Revision as of 12:23, 10 March 2023
Line 27:		Line 27:

	In the WP5 of COMP4DRONES, ACORDE has tackled the challenge to enable '''anti-jamming and anti-spoofing capabilities''' for low-cost geo-referenced outdoor positioning and attituded estimation solution, i.e. GLAD+ [[WP3-15_2]], in a way that:		In the WP5 of COMP4DRONES, ACORDE has tackled the challenge to enable '''anti-jamming and anti-spoofing capabilities''' for low-cost geo-referenced outdoor positioning and attituded estimation solution, i.e. GLAD+ [[WP3-15_2]], in a way that:
	* hold a '''low-cost''' of the solution (taking [GLAD\| glad.acorde.com] as a reference		* hold a '''low-cost''' of the solution (taking [[GLAD\| glad.acorde.com]] as a reference
	* a '''smooth integration''' is enabled		* a '''smooth integration''' is enabled

Acorde: /* Description and Benefits */

2023-03-10T12:23:04Z

Description and Benefits

← Older revision		Revision as of 12:23, 10 March 2023
Line 26:		Line 26:
	==Description and Benefits==		==Description and Benefits==

	~~One activity of ACORDE in~~ WP5 of COMP4DRONES has ~~been~~ to enable '''anti-jamming and anti-spoofing capabilities''' ~~to its~~ low-cost geo-referenced outdoor positioning and attituded estimation solution, i.e. GLAD+ [[WP3-15_2]].		In the WP5 of COMP4DRONES, ACORDE has tackled the challenge to enable '''anti-jamming and anti-spoofing capabilities''' for low-cost geo-referenced outdoor positioning and attituded estimation solution, i.e. GLAD+ [[WP3-15_2]], in a way that:
			* hold a '''low-cost''' of the solution (taking [GLAD\| glad.acorde.com] as a reference
	~~The challenge tackled has been to enable such a feature~~ in a way that:		* a '''smooth integration''' is enabled
	* hold ~~the~~ '''low-cost''' of the solution
	* ~~enabled~~ a '''smooth integration'''

	==How==		==How==

Acorde: /* Evaluation */

2023-03-10T12:11:36Z

Evaluation

← Older revision		Revision as of 12:11, 10 March 2023
Line 65:		Line 65:
	[[File:wp5-11_04.png\|100px\|frame\|center\|Debug trace showing the status of the detection of spoofing (in blue) and jamming (in red) when both features are enabled]]		[[File:wp5-11_04.png\|100px\|frame\|center\|Debug trace showing the status of the detection of spoofing (in blue) and jamming (in red) when both features are enabled]]

	As can be noticed, the configuration shown in the former figure enabled both spoofing and jamming detection. In addition, specfic parameters for jamming detection (~~c2=15~~ and ~~bb=3~~) were provided.		As can be noticed, the configuration shown in the former figure enabled both spoofing and jamming detection. In addition, specfic parameters for jamming detection, i.e. threshold for pure carrier jamming (15dB) and for broadband jamming (3dB) were provided.
	According to this configuration, the log excerpt shows corresponding spoofing and jamming status messages. In this case, spoofing free and low-level jamming scenario is detected.		According to this configuration, the log excerpt shows corresponding spoofing and jamming status messages. In this case, spoofing free and low-level jamming scenario is detected.

Acorde: /* Evaluation */

2023-03-10T12:08:34Z

Evaluation

← Older revision		Revision as of 12:08, 10 March 2023
Line 65:		Line 65:
	[[File:wp5-11_04.png\|100px\|frame\|center\|Debug trace showing the status of the detection of spoofing (in blue) and jamming (in red) when both features are enabled]]		[[File:wp5-11_04.png\|100px\|frame\|center\|Debug trace showing the status of the detection of spoofing (in blue) and jamming (in red) when both features are enabled]]

	As can be noticed, the configuration shown in the former figure enabled both spoofing and jamming detection. In addition, ~~specfici~~ parameters for jamming detection (c2=15 and bb=3) were provided.		As can be noticed, the configuration shown in the former figure enabled both spoofing and jamming detection. In addition, specfic parameters for jamming detection (c2=15 and bb=3) were provided.
	According to this configuration, the log excerpt shows corresponding spoofing and jamming status messages. In this case, spoofing free and low-level jamming scenario is detected.		According to this configuration, the log excerpt shows corresponding spoofing and jamming status messages. In this case, spoofing free and low-level jamming scenario is detected.

Acorde: /* Description */

2023-03-10T12:08:15Z

Description

← Older revision		Revision as of 12:08, 10 March 2023
Line 24:		Line 24:
	\|}		\|}

	==Description==		==Description and Benefits==

	One activity of ACORDE in WP5 of COMP4DRONES has been to enable '''anti-jamming and anti-spoofing capabilities''' to its low-cost geo-referenced outdoor positioning and attituded estimation solution, i.e. GLAD+ [[WP3-15_2]].		One activity of ACORDE in WP5 of COMP4DRONES has been to enable '''anti-jamming and anti-spoofing capabilities''' to its low-cost geo-referenced outdoor positioning and attituded estimation solution, i.e. GLAD+ [[WP3-15_2]].

	The challenge tackled has been to enable such a feature in a way that:		The challenge tackled has been to enable such a feature in a way that:
	* hold the low-cost of the solution		* hold the '''low-cost''' of the solution
	* enabled a smooth integration		* enabled a '''smooth integration'''

	==How==		==How==

Acorde: /* Evaluation */

2023-03-10T12:07:20Z

Evaluation

← Older revision		Revision as of 12:07, 10 March 2023
Line 65:		Line 65:
	[[File:wp5-11_04.png\|100px\|frame\|center\|Debug trace showing the status of the detection of spoofing (in blue) and jamming (in red) when both features are enabled]]		[[File:wp5-11_04.png\|100px\|frame\|center\|Debug trace showing the status of the detection of spoofing (in blue) and jamming (in red) when both features are enabled]]

	As can be ~~notice~~, the configuration shown in the former figure enabled both spoofing and jamming detection. In addition, specfici parameters for jamming detection (c2=15 and bb=3) were provided.		As can be noticed, the configuration shown in the former figure enabled both spoofing and jamming detection. In addition, specfici parameters for jamming detection (c2=15 and bb=3) were provided.
	According to this configuration, the log excerpt shows corresponding spoofing and jamming status messages. In this case, spoofing free and low-level jamming scenario is detected.		According to this configuration, the log excerpt shows corresponding spoofing and jamming status messages. In this case, spoofing free and low-level jamming scenario is detected.

Acorde: /* Evaluation */

2023-03-10T12:07:03Z

Evaluation

← Older revision		Revision as of 12:07, 10 March 2023
Line 57:		Line 57:
	The configuration through a simple .ini file was tested, as illustrated in the following figure:		The configuration through a simple .ini file was tested, as illustrated in the following figure:

	[[File:wp5-11_03.png\|100px\|frame\|center\|User settings file with new parameters for spoofing&jamming configuration (in blue and red respectively)]		[[File:wp5-11_03.png\|100px\|frame\|center\|User settings file with new parameters for spoofing&jamming configuration (in blue and red respectively)]]

	Via this type of file, different configurations were performed, with their later corresponding runs of GLAD+ application on the HW platform upgraded during the COMP4DRONEs project.		Via this type of file, different configurations were performed, with their later corresponding runs of GLAD+ application on the HW platform upgraded during the COMP4DRONEs project.

Acorde: /* Evaluation */

2023-03-10T12:05:45Z

Evaluation

← Older revision		Revision as of 12:05, 10 March 2023
Line 57:		Line 57:
	The configuration through a simple .ini file was tested, as illustrated in the following figure:		The configuration through a simple .ini file was tested, as illustrated in the following figure:

	[[File:wp5-11_03.png\|~~200px~~\|frame\|center\|User settings file with new parameters for spoofing (in blue) and ~~jamming (in~~ red)~~, being both features enabled]~~]		[[File:wp5-11_03.png\|100px\|frame\|center\|User settings file with new parameters for spoofing&jamming configuration (in blue and red respectively)]

	~~(via~~ this file ~~takes effect~~, different configurations were performed, with their later corresponding runs of GLAD+ application on the HW platform upgraded during the COMP4DRONEs project. For these experiments, GLAD+ application debug traces ~~where~~ enabled. These traces ~~enable~~ the application to dump the spoofing and jamming status obtained from the driver-level API~~. In this way~~, ~~from~~ the ~~configuration of Figure 3, a log whose excerpt is~~ shown in ~~Figure 4 was produced. The log shows how~~ the ~~anti-jamming and anti-spoofing features are disabled, as was configured~~.		Via this type of file, different configurations were performed, with their later corresponding runs of GLAD+ application on the HW platform upgraded during the COMP4DRONEs project.
			For these experiments, GLAD+ application debug traces were enabled. These traces enabled the application to dump the spoofing and jamming status obtained from the driver-level API
			into a log, as the one shown in the following figure.

			[[File:wp5-11_04.png\|100px\|frame\|center\|Debug trace showing the status of the detection of spoofing (in blue) and jamming (in red) when both features are enabled]]

			As can be notice, the configuration shown in the former figure enabled both spoofing and jamming detection. In addition, specfici parameters for jamming detection (c2=15 and bb=3) were provided.
	~~A different case was configured as shown in Figure 5~~, ~~to enable both anti-spoofing and anti-jamming features. The corresponding debug traces are~~ shown in ~~Figure 6.~~		According to this configuration, the log excerpt shows corresponding spoofing and jamming status messages. In this case, spoofing free and low-level jamming scenario is detected.


	~~Again,~~ the ~~debug traces of GLAD+ software provide different information, but consistent with the new configuration. Specifically, it provides the novel detection status of~~ both spoofing and jamming ~~events (enabled)~~, ~~plus additional information, i.e. that a~~ jamming ~~status is detected. This is explainable because this experiment was performed in a semi-indoor~~ (~~with a dumped GNSS signal~~) ~~noisy environment~~.
	~~Moreover~~, ~~a bit more detailed look to~~ the ~~debug~~ log, shows ~~that the specific~~ jamming status ~~report correspond to a “low-level” jamming~~. ~~This corresponds to a jamming level which could eventually yet correspond to a valid (worse quality) position~~, ~~in contrast to a high~~-level jamming ~~event, which would immediately cause an invalid fix on the application~~.