Baseband Processing - Revision history

Gema.Cueto: /* Mathematical Model */

2024-01-24T08:57:58Z

Mathematical Model

← Older revision		Revision as of 08:57, 24 January 2024
Line 43:		Line 43:


	with <math>s(t_k) = A_Im_I(t_k)d(t_k)-jA_Qm_Q(t_k)d(t_k)\,</math>		with <math>s(t_k) = A_Im_I(t_k)d(t_k)+jA_Qm_Q(t_k)d(t_k)\,</math>

Claudia.Prajanu at 19:58, 2 September 2018

2018-09-02T19:58:44Z

← Older revision		Revision as of 19:58, 2 September 2018
Line 160:		Line 160:

	==Platforms==		==Platforms==
	Most receivers implement the baseband processing algorithms in dedicated ASICs, DSPs or even FPGAs, as discussed [[Receiver Types\|here]]. The baseband processing block, however, may also be implemented in software, following a Software Defined Radio (SDR)<ref>[[Wikipedia:Software GNSS Receiver\|Software GNSS Receiver in Wikipedia]]</ref> philosophy. Although the software implementations provide a higher degree of flexibility, upgradeability and expandability, they still raise concerns regarding processing load and CPU power consumption in current commercial platforms<ref>http://www.gpsworld.com~~/gps/the-software-gnss-receiver-936~~</ref>.		Most receivers implement the baseband processing algorithms in dedicated ASICs, DSPs or even FPGAs, as discussed [[Receiver Types\|here]]. The baseband processing block, however, may also be implemented in software, following a Software Defined Radio (SDR)<ref>[[Wikipedia:Software GNSS Receiver\|Software GNSS Receiver in Wikipedia]]</ref> philosophy. Although the software implementations provide a higher degree of flexibility, upgradeability and expandability, they still raise concerns regarding processing load and CPU power consumption in current commercial platforms<ref>http://www.gpsworld.com</ref>.

	==Related articles==		==Related articles==

Filipe.Pelica: Included editor logo.

2014-09-18T16:33:14Z

Included editor logo.

← Older revision		Revision as of 16:33, 18 September 2014
Line 4:		Line 4:
	\|Level=Advanced		\|Level=Advanced
	\|YearOfPublication=2011		\|YearOfPublication=2011
			\|Logo=GMV
	\|Title={{PAGENAME}}		\|Title={{PAGENAME}}
	}}		}}

Carlos.Lopez at 11:00, 23 February 2012

2012-02-23T11:00:25Z

← Older revision		Revision as of 11:00, 23 February 2012
Line 1:		Line 1:
	{{Article Infobox2		{{Article Infobox2
	\|Category=Receivers		\|Category=Receivers
	\|Editors=GMV ~~A.D.~~		\|Editors=GMV
	\|Level=Advanced		\|Level=Advanced
	\|YearOfPublication=2011		\|YearOfPublication=2011

Carlos.Lopez at 10:33, 23 February 2012

2012-02-23T10:33:45Z

← Older revision		Revision as of 10:33, 23 February 2012
Line 1:		Line 1:
	{{Article Infobox2		{{Article Infobox2
	\|Category=Receivers		\|Category=Receivers
	\|~~Authors~~=GMV		\|Editors=GMV A.D.
	\|Level=Advanced		\|Level=Advanced
	\|YearOfPublication=2011		\|YearOfPublication=2011
	~~\|Logo=GMV~~
	\|Title={{PAGENAME}}		\|Title={{PAGENAME}}
	}}		}}

Teresa.Ferreira: /* Signal Detection */

2011-11-21T10:57:15Z

Signal Detection

← Older revision		Revision as of 10:57, 21 November 2011
Line 154:		Line 154:
	Finally, the dimensioning of these techniques has to consider the expected noise conditions, probability of false alarm, probability of detection and mean acquisition time. In fact, the longer the integrations the higher probability of detection (the lower the probability of false alarm) but the slower the potential acquisition time is, since the receiver will dwell longer in each search bin, defined by the pair [code delay, Doppler frequency].		Finally, the dimensioning of these techniques has to consider the expected noise conditions, probability of false alarm, probability of detection and mean acquisition time. In fact, the longer the integrations the higher probability of detection (the lower the probability of false alarm) but the slower the potential acquisition time is, since the receiver will dwell longer in each search bin, defined by the pair [code delay, Doppler frequency].

	The concepts of coherent and non-coherent integrations are also used when the receiver is in tracking mode, in order to reduce the noise levels and increase accuracy (see [[Tracking Loops\|tracking loops]] for details). The advantage is that, after bit synchronization, the receiver may increase the integration time up to the bit duration (e.g. 20 ms for GPS L1 C/A). Modernized GNSS such as Galileo already have so-called pilot channels that do not convey any navigation data, and therefore can be used to further extend (coherent) integration times.		The concepts of coherent and non-coherent integrations are also used when the receiver is in tracking mode, in order to reduce the noise levels and increase accuracy (see [[Tracking Loops\|tracking loops]] for details). The advantage is that, after bit synchronization, the receiver may increase the integration time up to the bit duration (e.g. 20 ms for GPS L1 C/A<ref>[GPS ICD 200, 2006] IS-GPS-200 Revision D, IRN-200D-001:NAVSTAR GLOBAL POSITIONING SYSTEM Navstar GPS Space Segment/Navigation User Interface, dated 7 March 2006.
			</ref>). Modernized GNSS such as Galileo already have so-called pilot channels that do not convey any navigation data, and therefore can be used to further extend (coherent) integration times.

	Long integration times are also used to track weak signals in harsh environments (such as indoors), but they are limited both by the data bit and by the accuracy of the clock/Doppler frequency estimation<ref>DINGPOS: A Hybrid Indoor Navigation Platform for GPS and GALILEO, J. A. López-Salcedo (UAB) , Y. Capelle (TAS-F), M. Toledo (GMV), G. Seco (UAB), J. López Vicario (UAB), D. Kubrak (TAS-F), M. Monnerat (TAS-F), A. Mark (GMV), D. Jiménez (ESA), ION GNSS 2008.</ref>.		Long integration times are also used to track weak signals in harsh environments (such as indoors), but they are limited both by the data bit and by the accuracy of the clock/Doppler frequency estimation<ref>DINGPOS: A Hybrid Indoor Navigation Platform for GPS and GALILEO, J. A. López-Salcedo (UAB) , Y. Capelle (TAS-F), M. Toledo (GMV), G. Seco (UAB), J. López Vicario (UAB), D. Kubrak (TAS-F), M. Monnerat (TAS-F), A. Mark (GMV), D. Jiménez (ESA), ION GNSS 2008.</ref>.

Teresa.Ferreira at 10:52, 21 November 2011

2011-11-21T10:52:23Z

← Older revision		Revision as of 10:52, 21 November 2011
Line 1:		Line 1:
	{{Article Infobox2		{{Article Infobox2
	\|Category=Receivers		\|Category=Receivers
	~~\|Title={{PAGENAME}}~~
	\|Authors=GMV		\|Authors=GMV
	\|Level=Advanced		\|Level=Advanced
	\|YearOfPublication=2011		\|YearOfPublication=2011
	\|Logo=GMV		\|Logo=GMV
			\|Title={{PAGENAME}}
	}}		}}
	The baseband processing block is responsible for processing the down-converted and digitized GNSS signal in order to provide observables: code pseudo-ranges and carrier phase measurements, as well as navigation data. Additional information, such as Doppler frequency, Carrier-to-Noise ratio, or lock indicators, can also be provided.		The baseband processing block is responsible for processing the down-converted and digitized GNSS signal in order to provide observables: code pseudo-ranges and carrier phase measurements, as well as navigation data. Additional information, such as Doppler frequency, Carrier-to-Noise ratio, or lock indicators, can also be provided.
Line 19:		Line 19:

	This process is implemented in an iterative way, usually using PLL and DLL [[Tracking Loops\|tracking loops]] to track the incoming signal's phase and code delay, respectively. In parallel, the receiver extracts the navigation data of the incoming signal, and ensures monitoring and control features further described [[Digital Signal Processing\|here]].		This process is implemented in an iterative way, usually using PLL and DLL [[Tracking Loops\|tracking loops]] to track the incoming signal's phase and code delay, respectively. In parallel, the receiver extracts the navigation data of the incoming signal, and ensures monitoring and control features further described [[Digital Signal Processing\|here]].

			Please refer to <ref>"GPS Data Processing: Code and Phase Algorithms, Techniques and Recipes", M. Hernandéz, J. Zomoza, J. Sanz, gAGE-NAV, gAGE/ UPC</ref> for additional literature on baseband processing.

	==Principle==		==Principle==

Rui.Pereira: moved Work in Progress:Baseband Processing to Baseband Processing over redirect

2011-05-27T15:50:40Z

moved Work in Progress:Baseband Processing to Baseband Processing over redirect

← Older revision	Revision as of 15:50, 27 May 2011
(No difference)

Rui.Pereira: /* Platforms */

2011-05-11T10:45:56Z

Platforms

← Older revision		Revision as of 10:45, 11 May 2011
Line 157:		Line 157:

	==Platforms==		==Platforms==
	Most receivers implement the baseband processing algorithms in dedicated ASICs, DSPs or even FPGAs, as discussed [[Receiver Types\|here]]. The baseband processing block, however, may also be implemented in software, following a Software Defined Radio (SDR)<ref>>[[~~wikipedia~~:Software GNSS Receiver]]</ref> philosophy. Although the software implementations provide a higher degree of flexibility, upgradeability and expandability, they still raise concerns regarding processing load and CPU power consumption in current commercial platforms<ref>http://www.gpsworld.com/gps/the-software-gnss-receiver-936</ref>.		Most receivers implement the baseband processing algorithms in dedicated ASICs, DSPs or even FPGAs, as discussed [[Receiver Types\|here]]. The baseband processing block, however, may also be implemented in software, following a Software Defined Radio (SDR)<ref>[[Wikipedia:Software GNSS Receiver\|Software GNSS Receiver in Wikipedia]]</ref> philosophy. Although the software implementations provide a higher degree of flexibility, upgradeability and expandability, they still raise concerns regarding processing load and CPU power consumption in current commercial platforms<ref>http://www.gpsworld.com/gps/the-software-gnss-receiver-936</ref>.

	==Related articles==		==Related articles==

Rui.Pereira: moved Baseband Processing to Work in Progress:Baseband Processing

2011-05-11T10:30:46Z

moved Baseband Processing to Work in Progress:Baseband Processing

← Older revision	Revision as of 10:30, 11 May 2011
(No difference)