Use DSP when possible.
The digital signal processing portion of the receiver can
perform the following tasks:
- downconvert the sampled signal to baseband
- track any changes in the phase or frequency of the
modulating sinusoid
- adjust the symbol timing by interpolation
- compensate for channel imperfections by filtering
- convert modestly inaccurate recovered samples into symbols
- perform frame synchronization via correlation
- decode groups of symbols into message characters
A central task in
Software Receiver Design is to elaborate on the system structure
in
[link] –
[link] to create a working software-defined radio that can perform these tasks.
This concludes the illustrative design at the outer,most superficial layer of the onion.
Use DSP to compensate for cheap ASP.
The complete onion
This section provides a whirlwind tour of the complete
layered structure of
Software Receiver Design . Each layer
presents the same digital transmission systemwith the outer layers peeled away to reveal greater depth and detail.
-
The Naive Digital Communications Layer: As we have just seen, the first layer of the onion
introduced the digital transmission of data, and discussedhow bits of information may be coded into waveforms,
sent across space to the receiver, and then decodedback into bits. Since there is no universal clock,
issues of timing become important, and some of themost complex issues in digital receiver design involve
the synchronization of the received signal. The systemcan be viewed as consisting of three parts:
- a transmitter
as in
[link]
- a transmission channel
- a receiver as in
[link]
-
The Component Architecture Layer: The next two chapters provide more
depth and detail by outlining a complete telecommunicationsystem. When the transmitted signal is passed through the
air using electromagnetic waves, it must takethe form of a continuous (analog) waveform. A good way to understand
such analog signals is via the Fourier transform, and thisis reviewed briefly in
[link] . The five basic
elements of the receiver will be familiar to many readers,and they are presented in
[link] in a form that will be directly
useful when creating M
atlab implementations
of the various parts of the communication system.By the end of the second layer, the basic system architecture
is fixed and the ordering of the blocks in the systemdiagram is stabilized.
-
The Idealized System Layer: The third layer encompasses
[link] through
[link] . This layer gives a closer look at
the idealized receiver—how things work when everythingis just right: when the timing is known, when the clocks run
at exactly the right speed, when there are no reflections,diffractions, or diffusions of the electromagnetic waves.
This layer also integrates ideas from previous systems courses,and introduces a few M
atlab tools that are needed to
implement the digital radio.The order in which topics are discussed is precisely
the order in which they appear in the receiver:
[link] provides a complete (though idealized)
software-defined digital radio system.
-
The Adaptive Component Layer: The fourth layer describes all the practical fixes that
are required in order to create a workable radio.One by one the various problems are studied and solutions
are proposed, implemented, and tested. These include fixesfor additive noise, for timing offset problems, for clock
frequency mismatches and jitter, and for multipath reflections.Again, the order in which topics are discussed is
the order in which they appear in the receiver:
-
The Integration Layer: The fifth layer is the final project of
[link] which integrates all the fixes of the fourth layer into the
receiver structure of the third layer to create afully functional digital receiver. The well-fabricated
receiver is robust to distortions such as those causedby noise, multipath interference, timing inaccuracies,
and clock mismatches.
Please observe that the word “layer” refers
to the onion metaphor for the method ofpresentation (in which each layer of the communication
system repeats the essential outline of the last, exposinggreater subtlety and complexity),
and not to the “layers” of a communication systemas might be found in Bertsekas and Gallager's
Data Networks .
In this latter terminology, the whole of
Software Receiver Design lies within the so-called
physical layer .
Thus we are part of an even larger onion,which is not currently on our plate.