root/ossiedev/branches/jsnyder/STTT_paper/sttt-draft.tex @ 11102

%%%%%%%%%%%%%%%%%%%%%%% file template.tex %%%%%%%%%%%%%%%%%%%%%%%%%
%
% This is a template file for the International Journal on
%                            Software Tools for Technology Transfer
%
% Copy it to a new file with a new name and use it as the basis
% for your article
%
%%%%%%%%%%%%%%%%%%%%%%%% Springer-Verlag %%%%%%%%%%%%%%%%%%%%%%%%%%
%

%
\documentclass[sttt,referee]{svjour}
% Remove option referee for final version
%
% Remove any % below to load the required packages
%\usepackage{latexsym}
\usepackage{graphicx}
\usepackage{stfloats}
\usepackage{fixltx2e}
% etc
%
\begin{document}
%
\title{Open Source Software Defined Radio Tools for Education, Research, and
Rapid Prototyping}
\author{Jason~Snyder, Deepan~Seeralan, Shereef~Sayed, Jeffery~Wilson,
Carl~B.~Dietrich, Stephen~H.~Edwards, and Jeffrey~H.~Reed}
%
%
\institute{Virginia Tech, Blacksburg, VA}
%
\date{Received: date / Revised version: date}
% The correct dates will be entered by Springer
%
\authorrunning{Snyder, Seeralan, Sayed, Wilson, Dietrich, Edwards, Reed}
\titlerunning{Open Source SDR Tools}
\maketitle
%
\begin{abstract}
Software Defined Radios (SDR) offer several advantages over traditional, hardware-based radios, most notably flexibility and reconfigurability. Developing SDR applications can be a difficult process however, for several reasons. First, much of the work involved deals with standards compliance, rather than radio functionality. This portion of the work is very detailed and error-prone, leading to wasted time and effort. Second, there is little to no support available for the debugging and refinement portions of the development cycle. There is no easy way to monitor or control SDR applications at runtime. The Waveform Workshop was created to address these issues. A part of the OSSIE SDR project, the Waveform Workshop drastically reduces the time and effort involved in SDR development. It automatically generates the portions of the software related to standards compliance, letting developers concentrate on radio functionality. In addition, the Waveform Workshop provides tools for both monitoring and controlling SDR applications at runtime, making debugging much easier.   
\keywords{Software Defined Radio, Rapid Prototyping Tools, Education}
\end{abstract}
%
\section{Introduction}
\label{introduction}
Software Defined Radio involves software implementation of radio functionality that is traditionally performed by analog hardware and digital application specific integrated circuits (ASICs).  SDR employs general purpose processors (GPPs), digital signal processors (DSPs), and field programmable gate arrays (FPGAs) that can be programmed or configured to provide great flexibility and support for multiple radio communications standards or waveforms.  Within limits of its hardware, a well designed SDR can support standards that were not conceived at the time the radio was designed \cite{Reed2002}.  SDR is of interest for both commercial \cite{Vanu} and military \cite{JTRS} applications.

Unfortunately, developers writing SDR software frequently face problems that are not addressed by traditional development tools.  This first problem is ensuring that SDR software conforms to the SCA standard. The standard is very complex, with many details that are necessary for compliance but unrelated to the functionality of the radio itself.  Another common problem SDR developers face is the lack of any way to interact with running SDR applications.  SDR applications are deployed as collections of CORBA software components running on one or more processors.  Software component configurations are recorded in XML files.  In this situation, the primary way to change a property value for a given component is to shut the application down entirely, change a value in a file, then restart the application. Finally, developers also have no readily available tools to monitor a running SDR application as it operates.

To address these problems, we have developed the Waveform Workshop a set of software tools. The Waveform Workshop was designed to work with the OSSIE open source SDR project \cite{Aguayo2009b}, \cite{ossieweb}. OSSIE is a partial implementation of the U.S. Defense Department's Software Communications Architecture (SCA) \cite{sca}, \cite{bard}, \cite{Aguayo2009a}.  The Waveform Workshop aids developers by automatically generating the parts of the software that relate to SCA compliance.  The developer can then concentrate on implementing the radio itself.  The Waveform Workshop also provides developers with a means to update application properties at runtime directly, without editing configuration files or restarting the application. This greatly reduces the time needed to debug applications.  Finally, the Waveform Workshop also provides an interface displaying block diagrams of running SDR applications. It also allows developers to take the output from an application and play it through speakers or plot it on a graph. This allows the developer to easily change application properties and observe the effects of those changes in real time, making it much easier to debug and refine SDR software.

In this paper, we discuss the problems faced by SDR developers and how those problems are addressed by the Waveform Workshop.  Section~\ref{background} discusses the need for SCA-based development tools for SDR projects.
Section~\ref{waveformworkshoptools} introduces the tools that are part of the Waveform Workshop and the problems they solve. Sections~\ref{sdrapplicationdevelopment-oef}--\ref{sdrapplicationdevelopment-alf} describe
their use in developing, configuring, and monitoring a waveform application. Finally, Section~\ref{conclusion} concludes and presents future work. 


\section{Background}
\label{background}

\subsection{Motivation for SCA-Based SDR Tools}
\label{toolmotivation}
The SCA is an open standard associated with the U.S. Department of Defense Joint Tactical Radio System (JTRS) \cite{JTRS}.  The SCA is a component and service based architecture that delineates and provides guidance for implementation of SDR infrastructure (e.g., the SCA core framework) and application software (e.g., waveform applications and signal processing components).  The SCA makes extensive use of software design patterns \cite{Gamma}, and of other standards that include POSIX \cite{POSIX}, CORBA \cite{CORBA}, and XML \cite{XML}.  Components in the SCA communicate using Common Object Resource Broker Architecture (CORBA) middleware, which provides interprocess communication and remote procedure call capability, allowing methods associated with remote components implemented in a variety of languages to appear as local function calls.  XML is used to store profile or configuration information.

The extensive nature of the SCA and its use of CORBA and XML both motivate and facilitate development of tools for SCA-based SDR development.  In most cases it is desirable to abstract the interface code required by CORBA from communications engineers who develop signal processing components and waveform applications.  Fortunately, use of CORBA also allows SCA-based SDR software tools to interact with SCA core frameworks and applications that are running either locally or remotely, while tools can parse XML files to obtain information needed to perform a variety of functions.  Commercial tools for SCA-based SDR development are available \cite{SpectraCX}, but the The Waveform Workshop fills a need for an open source Software Communications Architecture (SCA)-based SDR toolset.  These tools allow prototyping of SDR waveform applications that can be ported to work with commercial SCA software \cite{singh}, such as the Harris’ Domain Manager Tool Kit (dmTK) \cite{dmtk}, the SCA Reference Implementation (SCARI) tools from the Canadian Communications Research Centre \cite{jianxin}, and Prism Tech’s Spectra CX.  The latter retails for as low as \$15,000 per team member based on a 10-member team \cite{prismtech}.  The GNU Radio Companion (GRC) \cite{gnuradio} is an open source tool for SDR that provides many capabilities similar to those of the tools described in this paper, but is not based on the SCA.

\subsection{OSSIE}
The Open Source SCA Implementation::Embedded (OSSIE) project was started in 2003 by postdoctoral fellow Max Robert and a team of students at Virginia Tech \cite{Robert2004}.  OSSIE software consists of a core framework and a library of application software (signal processing components and waveform applications).  The project also provides materials for SDR education, training, and self study.
 
The OSSIE software, including the Waveform Workshop, is a widely used and distributed software package. There have been over 20,000 downloads of the OSSIE source code, ready-to-run live DVDs, and VMware images. We have confirmed that students and engineers at over 20 different universities, companies, nonprofit research centers, and government laboratories have used OSSIE. 


\section{Improving the SDR Development Process}
\label{waveformworkshoptools}

SDR frameworks such as OSSIE can be used without a set of specially designed developer tools, but it is a difficult and error-prone process. Component and waveform XML descriptors must conform to the SCA and have to be written and installed by hand. Controlling waveforms is typically limited to starting and stopping them, and there is no easy way to monitor or manipulate running waveforms. The Waveform Workshop solves these problems by doing the following:

\begin{enumerate}
\item Streamlining the development process by automatically generating the necessary infrastructure to ensure SCA compliance.

\item Providing a means to control and manipulate SDR waveforms at runtime.

\item Providing a means to observe SDR waveforms at runtime, including the ability to inject input to or monitor output from components.
\end{enumerate}

\subsection{Automating SDR Development}
\label{toolsdescription:oef}
The OSSIE Eclipse Feature (OEF) is the first tool in the Waveform Workshop and was created to automate as much of the SDR development process as possible. OEF is a port of the OSSIE Waveform Developer (OWD), an open source python tool for rapid component and waveform prototyping.  OWD automatically generated the necessary XML descriptors and CORBA-enabled skeleton implementations for SCA-based signal processing components and XML files that specify instantiation, interconnection, and deployment of these components to form waveform applications that implement end-to-end communications waveforms. In the case of signal processing components, the SDR developer who used OWD then had to fill in the implementation using his or her editor of choice. Finally, the component or waveform files had to be built and installed from the command line using automake tools.  The motivation for OEF was to duplicate the automatic generation functionality of OWD that ensured SCA compatibility, while adding support for the rest of the development process. To do so, OEF was developed as a plug-in for the Eclipse IDE. Along with providing the automatic generation from OWD, OEF also takes care of building and installing components and waveforms, eliminating many opportunities for introducing user error. It also brings all the advantages of a modern IDE. This includes syntax highlighting of source code in multiple programming languages, a simple to use interface for version control systems such as CVS and SVN, and project management tools. 

\subsection{Controlling SDR Applications in Real Time}
\label{toolsdescription:wavedash}
The second tool in the Waveform Workshop is the Waveform Dashboard (WaveDash) that was created to allow users to control SDR applications in real time. WaveDash is an interactive and reconfigurable graphical user interface (GUI) tool that acts as a control panel for working with multiple SDR waveform applications and their components. This tool abstracts the SCA interfaces and the implementation of the OSSIE core framework by providing a direct manipulation interface to control and configure SDR waveforms interactively. Users can install, start, stop and uninstall a running waveform application. More importantly, it allows users to configure the properties of a waveform's components in real time. Prior to WaveDash, all component properties were set at runtime and could not be changed. Finally, the Wavedash interface is customizable on a per-waveform and per-component basis. Users can choose the type of widget they prefer to represent a particular property of a component and can also hide or unhide specific components or properties.


\subsection{Monitoring SDR Applications in Real Time}
\label{toolsdescription:alf}
The Waveform Workshop monitors running SDR applications with a tool called ALF. The initial ALF tool was contributed to the project by SAIC in 2007, and Virginia Tech has maintained and enhanced the tool since that time.  Implemented in Python, ALF interacts with a local or remote OSSIE Domain Manager via CORBA, and allows users to install, start, stop, and uninstall OSSIE waveforms, and to display the waveforms in block-diagram form.  ALF includes plug-in tools that can be used to inject signals into signal processing components and to monitor signals at various points in a waveform application by playing those signals through speakers or by plotting them on a graph. 

%-------------------- FIGURE: SDR Development using Waveform Workshop --------------------
\begin{figure*}
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=\textwidth]{SDR_Development_using_Waveform_Workshop_bw.pdf}
% trim = left bottom right top
\caption{SDR application development using the OSSIE Waveform Workshop tools}
\label{fig:sdrdevelopmentdiagram}
\end{figure*}

Figure~\ref{fig:sdrdevelopmentdiagram} shows how these three tools interact with Waveform Application Software and the OSSIE Core Framework. 

\section{SDR Application Development Work FlowPart I:  Creating Components and Waveform Applications using the OSSIE Eclipse Feature}
\label{sdrapplicationdevelopment-oef}

\subsection{Creating a Component}
\label{sdrapplicationdevelopment-oef:creatingcomponent}
OEF helps developers to create signal processing components.  The developer specifies characteristics of the component such as ports and reconfigurable properties, and OEF generates CORBA-enabled skeletal code for OSSIE.  The developer then provides or links to signal processing code that implements the desired functionality.  While more complex components can be developed using the same approach, the following example describes creation of a simple signal processing component, an amplifier that scales the incoming signal by a constant gain factor.
%-------------------- FIGURE: GENERATING NEW COMPONENT --------------------
\begin{figure*}
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=\textwidth]{figure2_oef_generating_new_component.pdf}
% trim = left bottom right top
\caption{Generating a new component in OEF}
\label{fig:oef:generatenewcomponent}
\end{figure*}
To create a signal processing component, the user first opens Eclipse and selects Window $\rightarrow$ Open Perspective $\rightarrow$ Other.  The user then chooses OSSIE from the list. This opens the OSSIE perspective, a special Eclipse layout designed for SDR development. Next, the user chooses File $\rightarrow$ New $\rightarrow$ OSSIE Component to open the New OSSIE Component Project wizard. The user then fills in the name for the project, in this case ``amplifierIQ'' and clicks on finish. This creates a new component project called amplifierIQ with a makefile and a .ocd file which is opened in the Component Editor (CE) as seen in Figure~\ref{fig:oef:generatenewcomponent}. 
The CE has the following four sections:
\begin{enumerate}
\item Description - for giving the component a textual description
\item Generation Options - to specify what type of component to generate
\item Ports - to specify the ports the component will have
\item Properties - to specify which properties the component will have
\end{enumerate}
The user enters the following descriptions for the component, in this case, ``Amplifier with independently adjustable gains for in- phase and quadrature signal components.'' Under generation options, the user selects basic\_ports from the template drop-down menu and leaves both ACE Support and Timing Port Support unchecked. Selecting basic\_ports will create a C++ component. The other options in the template drop-down, custom\_ports and py-comp, are for components that use an alternative set of interfaces and for python components, respectively. Checking ACE support would let the component use certain features of ACE \cite{ACE} such as ACE threads, and checking Timing Port Support adds profiling support when using the custom ports or python component options.

\subsection{Adding Ports to a Component}
\label{sdrapplicationdevelopment-oef:addingports}

%-------------------- FIGURE: ADD PORT PORT DIALOG --------------------
\begin{figure}
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=8.5cm]{figure3_oef_add_port_dialog.png}
% trim = left bottom right top
\caption{Add Port dialog}
\label{fig:oef:addport}
\end{figure}

The next step is to add ports to the component. Ports allow components to communicate with one another. The user clicks on the Add button to bring up the Add Port dialog, as shown in Figure~\ref{fig:oef:addport}. Next, the user enters ``amp\_output'' for the port name. As defined by the SCA, a uses port is an output port while a provides port is an input port. Since this port will be an output port, the user selects uses from the type drop-down menu. To choose the type of interface, the user clicks the arrow next to Standard Interfaces and selects complexShort from the choices that appear. Finally, the user clicks ok and sees the new port in the Ports table. All three fields in the Ports table are editable in place, so the user can change the name, interface, or type of any port after it has been added. Selecting any port and clicking the Remove button will delete the port from the component. This component also requires an input port called amp\_input that is also a complexShort, so the user adds another port using the same process

\subsection{Adding Properties to a Component}
\label{sdrapplicationdevelopment-oef:addingproperties}

%-------------------- FIGURE: ADD PROPERTY DIALOG --------------------
\begin{figure}
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=8.5cm]{figure4_oef_add_property_dialog.png}
% trim = left bottom right top
\caption{Add Property dialog}
\label{fig:oef:addproperty}
\end{figure}

The final step to configure a component is to add any reconfigurable properties it will need. Our amplifier needs two properties: I\_gain and Q\_gain, which multiply in-phase and quadrature components of the signal, respectively. The user clicks the Add button in the Properties section of the CE to bring up the Add Property dialog as shown in Figure~\ref{fig:oef:addproperty}. The user enters ``I\_gain'' for the name and 1 for the value. The rest of the attributes are left as the defaults, so the user clicks Add Property. The process is repeated for a Q\_gain property.
        
\subsection{Generating Skeleton Implementation}
\label{sdrapplicationdevelopment-oef:skeletonimplementation}

%-------------------- FIGURE: GENERATED PROJECT --------------------
\begin{figure*}
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=\textwidth]{figure5_oef_newly_generated_component_project.pdf}
% trim = left bottom right top
\caption{Newly generated component project in OEF}
\label{fig:oef:generatedproject}
\end{figure*}

At this point, all of the configuration for the component is complete.  The next step is to generate the XML descriptors and skeleton implementation files. The user selects Generate Component from the OSSIE menu to start the generation. OEF will run the necessary make commands and show the output in the console view. After generation is complete, the new files will appear in the project explorer, as seen in Figure~\ref{fig:oef:generatedproject}.

\subsection{Filling in Implementation Code}
\label{sdrapplicationdevelopment-oef:implementation}

%-------------------- FIGURE: EDITING CODE IN OEF --------------------
\begin{figure*}
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=\textwidth]{figure6_oef_editing_code.pdf}
% trim = left bottom right top
\caption{Editing code in OEF}
\label{fig:oef:editingcode}
\end{figure*}

Once the component has been generated, the user has to fill in the skeleton with implementation code. The user double-clicks on amplifierIQ.cpp in the Project Explorer to open the file in a C++ editor as shown in Figure~\ref{fig:oef:editingcode}. After filling in the custom implementation that operates on the input signal using the specified property (gain) values, and sends the processed signal to the output port, he saves the file. As long as there are no errors, OEF automatically builds and installs the component to the filesystem.

\subsection{Creating and Configuring a Waveform}
\label{sdrapplicationdevelopment-oef:waveform}
Now that the user has successfully created and built a component, that component can be used in a new waveform. The example waveform will be a simulated QPSK communications link that runs entirely on a single computer, but essentially the same approach is used to develop a radio communication waveform application that interfaces with RF hardware.  To get started, the user selects File $\rightarrow$ New $\rightarrow$ OSSIE Waveform to open the New OSSIE Waveform Project wizard. The user names the project SimpleWaveform and clicks on Finish. When the wizard finishes, the user is presented with the main Waveform Editor (WE), as seen in Figure~\ref{fig:oef:waveformeditor}. The WE contains 3 main trees:
\begin{enumerate}
\item Available Resources - lists all of the components, devices, and nodes currently installed on the system and available for use
\item Waveform - shows all of the components to be used in the current waveform
\item Platform - shows the processing and input/output devices and nodes (collections of devices) and components allocated to each processing device in the current waveform.
\end{enumerate}

%-------------------- FIGURE: OEF WAVEFORM EDITOR --------------------
\begin{figure*}
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=\textwidth]{figure7_oef_waveform_editor.png}
% trim = left bottom right top
\caption{Waveform editor}
\label{fig:oef:waveformeditor}
\end{figure*}

Note that the component that the user just built, amplifierIQ, is listed under components in the Available Resources tree. To begin assembling the waveform, the user drags the TxDemo, amplifierIQ, ChannelDemo, and RxDemo components he will be using to the Waveform tree. The user then drags a default\_GPP\_node (which corresponds to a set of XML files for a Device Manager that manages a single x86 GPP) from nodes in the Available Resources tree to the Platform tree. The components are not yet allocated to any nodes, so the user expands default\_GPP\_node to show the device on it, GPP1. To allocate the components to this device, the user drags each component from the Waveform tree to GPP1 in the Platform tree. When a component is allocated to GPP1, the component appears under the GPP1 in the Platform tree, and the label on the component in the Waveform tree also changes to reflect where it has been allocated.

%-------------------- FIGURE: PORTS ON COMPONENTS --------------------
\begin{figure*}
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=\textwidth]{figure8_oef_ports_on_component.pdf}
% trim = left bottom right top
\caption{Ports on Components}
\label{fig:oef:portsoncomponents}
\end{figure*}

Next, the user has to connect the ports on the components to one another. The user expands each component in the Waveform tree to show their ports, as seen in Figure~\ref{fig:oef:portsoncomponents}. To connect the ports, the user drags a uses port (orange puzzle piece) on top of a provides port (blue puzzle piece). Each port then changes to a combined puzzle piece and its label changes to show which port it is connected to. Once all of the ports have been connected, the final step is to choose an Assembly Controller. To do so, the user right clicks on TxDemo1 in the Waveform tree and chooses Set Assembly Controller.  Once this is done, the waveform is fully configured and ready to be generated. The user saves the project and OEF automatically generates all of the necessary XML descriptors for the waveform and installs them to the filesystem.

\section{SDR Application Development Work Flow Part 2:  Configuring and Controlling Waveform Applications using the Waveform Dashboard}
\label{sdrapplicationdevelopment-wavedash}

%-------------------- FIGURE: WAVEDASH - INSTALL A WAVEFORM APPLICATION --------------------
\begin{figure}
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=8.5cm]{figure9_wavedash_waveform_menu.png}
% trim = left bottom right top
\caption{Installing a waveform application using WaveDash}
\label{fig:wavedash:install}
\end{figure}

WaveDash allows users to control and configure waveform applications in real time.  WaveDash can be used to install/uninstall and configure component properties of the waveform application that was developed in OEF in Section~\ref{sdrapplicationdevelopment-oef:waveform}. The Waveforms menu in WaveDash lists the currently available waveforms on the system. The user pulls down the menu and selects `SimpleWaveform' that was just created (Figure~\ref{fig:wavedash:install}). The sub-menu allows the user to either install a new application instance of the waveform or to preview the component and their properties present in the waveform. The user clicks on Install to install a new instance of SimpleWaveform. WaveDash displays the waveform applications in a tabbed fashion to allow users to work with multiple waveforms at one time. New waveform application tabs are appended to the right of the most recently installed waveform application.

\subsection{Install a new waveform application}
\label{sdrapplicationdevelopment-wavedash:installingwaveformapplication}
The WaveDash toolbar provides controls to start, stop or uninstall the waveform application denoted by the active tab.  The user has to click on the appropriate buttons on the toolbar to start, stop or uninstall a waveform application. 

\subsection{Show/Hide Components}
\label{sdrapplicationdevelopment-wavedash:showhidecomponents}

%-------------------- FIGURE: WAVEDASH - SELECT AND DESELECT COMPONENTS --------------------
\begin{figure} 
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=8.5cm]{figure10_wavedash_component_menu.png}
% trim = left bottom right top
\caption{Select/Deselect Components in WaveDash}
\label{fig:wavedash:selectdeselectcomponents}
\end{figure}

The Component menu lists the components present in the waveform application denoted by the active tab. The user deselects the component RxDemo from the Component menu (Figure~\ref{fig:wavedash:selectdeselectcomponents}) to hide it as it does not have any properties to configure. This feature is particularly useful when the waveform comprises a large number of components and only few of them are required to be configured often.  
        
\subsection{Configure Component Properties of a Waveform}
\label{sdrapplicationdevelopment-wavedash:configurecomponentproperties}
The ability to configure component properties at runtime was urgently needed and was one of the prime motivations to develop WaveDash. Prior to development of WaveDash, OSSIE users had to either modify property values in OEF and rebuild the waveform or hand-edit the property values in the component or waveform XML files and restart the waveform to configure the component property values.  

WaveDash enables users to modify component properties at runtime thus making SDR waveform development more live and interactive.  Each property has a GUI widget (e.g. text box, slider) associated with by default based on its data type (e.g. integer, string). The user can change the value of a component property by changing the value of the widget. By default, the property will be updated immediately after the user presses TAB or ENTER. Changes can be immediately seen with the ALF Plot tool (see Section $\ref{sdrapplicationdevelopment-alf:relationwithwavedash}$). In this example, the user changes the value of noise\_std\_dev of ChannelDemo from default value of 1000 to a 1500 and presses ENTER for the change to take effect. 

%-------------------- FIGURE: WAVEDASH - Update on Refresh --------------------
\begin{figure} 
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=8.5cm]{figure13_wavedash_update_properties_on_refresh.png}
% trim = left bottom right top
\caption{WaveDash with Update Properties on Refresh enabled}
\label{fig:wavedash_update_properties_on_refresh}
\end{figure}

While the user will normally want component properties to update immediately once the value of the widget has changed, there are times where it is better to be able to change multiple property values and have them all update simultaneously. Wavedash makes this easy to do. Under the Options menu, the user can select `Update Properties on Refresh'. This will enable the refresh buttons on each component and the waveform, as shown in Figure~\ref{fig:wavedash_update_properties_on_refresh}. When used this way, WaveDash only updates the component property values when one of the refresh buttons is clicked. Clicking the refresh button for a single component updates only that component's properties. Clicking the refresh button at the bottom updates all properties on all components in the waveform.

\subsection{Change Property Configuration Control Widgets}
\label{sdrapplicationdevelopment-wavedash:configurewidgets}
The component PRF files determine the data type for each property of the component. WaveDash does a default mapping of data type (mentioned in PRF files) to a GUI widget (control) and also provides an optional list of widgets which users can customize to their preferences. In this example, packet\_delay\_ms of TxDemo is mapped to a spin box by default. User right clicks on the spin box that brings a context menu with the list of optional widgets configurable for packet\_delay. The user selects slider (Figure~$\ref{fig:wavedash:changepropertywidgets}$) and that changes the widget on the application GUI also. The configure option in the context menu is used to set minimum and maximum values for spin box and slider controls.
%-------------------- FIGURE: WAVEDASH - CHANGE PROPERTY CONTROL WIDGETS --------------------
\begin{figure} 
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=8.5cm]{figure11_wavedash_property_context_menu.png}
% trim = left bottom right top
\caption{Change property control widgets in WaveDash}
\label{fig:wavedash:changepropertywidgets}
\end{figure}
       
\subsection{Show/Hide Component Properties}
\label{sdrapplicationdevelopment-wavedash:showhidecomponentproperties}
It is highly possible that a component may have so many properties that it is not convenient to display all of the properties at the same time. Users may wish to hide unwanted properties and keep only the frequently used properties on screen. In this example (Figure~$\ref{fig:wavedash:selectdeselectproperties}$), the user right clicks on a component and deselects phase\_offset from the pop-up menu.
%-------------------- FIGURE: WAVEDASH - SELECT/DESELECT COMPONENT PROPERTIES --------------------
\begin{figure} 
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=8.5cm]{figure12_wavedash_component_context_menu.png}
% trim = left bottom right top
\caption{Selecting Component Properties in Wavedash}
\label{fig:wavedash:selectdeselectproperties}
\end{figure}
      
\section{SDR Application Development Work Flow Part III:  Use of ALF Waveform Application Visualization and Debugging Environment}
\label{sdrapplicationdevelopment-alf}

The ALF environment provides several capabilities that are helpful for troubleshooting and debugging waveform applications.  Like WaveDash, ALF allows users to install/uninstall and start/stop waveform applications.  ALF also lets users display running applications in block diagram form as shown in Figure~\ref{fig:alf:block_diagram_plugin_menu}, and inject and monitor signals at various component ports in the application using provided or user-developed plug-in tools by right clicking on the port (small rectangle on either side of the component) and selecting from a menu as shown in Figure~\ref{fig:alf:block_diagram_plugin_menu}.  Additional features enable creation and installation of single-component waveform applications, and connections between ports on components in the same or different waveforms at run time.
%-------------------- FIGURE: ALF - BLOCK DIAGRAM WITH PLUG-IN MENU --------------------
\begin{figure*}
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=\textwidth]{figure13_Alf_Block_Diagram_plugins_menu.pdf}
% trim = left bottom right top
\caption{ALF tool showing SimpleWaveform block diagram and plug-in tool menu}
\label{fig:alf:block_diagram_plugin_menu}
\end{figure*}

\subsection {ALF Plug-In Tools}
\label{sdrapplicationdevelopment-alf:plugins}
Several plug-in tools for ALF are provided as part of the OSSIE distribution.  These tools are used to inject signals into component provides ports, and to display, record, or otherwise process the signals coming out of component uses ports.  The plugins are implemented in Python, and users can modify the plug-ins or develop their own based on those provided.

\subsubsection{Speaker Tool}
\label{sdrapplicationdevelopment-alf:plugins:soundtool}
The speaker tool accepts signals in OSSIE's complexShort (2-channel, short integer) interface format and plays the signals through a computer's sound card.  It allows the user to set the sampling rate at which the signal will be converted to audio.

\subsubsection{Plot Tool}
\label{sdrapplicationdevelopment-alf:plugins:plottool}
The plot tool (Figure~\ref{fig:alf:plugins:plot}) accepts signals from uses ports that employ the complexShort, complexLong, or complexFloat interfaces.  This tool displays the signal's spectrum on a normalized frequency scale or displays the quadrature vs. in-phase components of the signal in order to render the constellations of received digital signals.  In this mode, several symbols are shown that under ideal conditions would typically map to regularly spaced points, e.g. in a circle (phase-shift keying) or in a grid pattern (quadrature amplitude modulation).  In a realistic simulation or an operational radio, the symbols appear scattered about the nominal symbol points due to noise, fading, imperfect synchronization, or other anomalies.
%-------------------- FIGURE: ALF - PLOT TOOL --------------------
\begin{figure}
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=8.5cm]{alf_plot_tool.png}
% trim = left bottom right top
\caption{The ALF Plot tool displaying a quadrature phase-shift keying (QPSK) signal constellation}
\label{fig:alf:plugins:plot}
\end{figure}



\subsubsection{Arbitrary Waveform Generator (AWG) Tool}
\label{sdrapplicationdevelopment-alf:plugins:AWGtool}
Figure~\ref{fig:alf:plugins:awg} shows the Arbitrary Waveform Generator, which allows one to select from a number of predefined signal functions or simply read signals that are stored in data files, for the purposes of testing, debugging, or demonstrating components or waveforms.  By allowing a signal stored in a data file to be fed into a live SDR component, developers gain the capability of generating signals off-line using software such as MATLAB or replaying signals that are captured live over the air later during testing.
%-------------------- FIGURE: ALF - AWG TOOL --------------------
\begin{figure}
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=8.5cm]{figure17_ALF_AWG_Tool.pdf}
% trim = left bottom right top
\caption{The ALF AWG tool}
\label{fig:alf:plugins:awg}
\end{figure}

\subsection{Launching Individual Components as Waveform Applications}
\label{sdrapplicationdevelopment-alf:compform}
ALF includes a `compform' capability that packages individual components as self-contained waveform applications and deploys them to the default GPP device.  This is accessed by clicking on a component in the middle left panel of ALF.  The compform feature allows a user to test individual components by using the plug-in tools to inject and monitor signals into and out of each component as the component runs in a stand-alone application.



\subsection{Connect Tool}
\label{sdrapplicationdevelopment-alf:connecttool}
The Connect Tool, shown in Figure~\ref{fig:alf:connect}, provides the capability
to connect ports on components that are in the same or different waveform applications.  This capability, provided with the ability to create and run single-component applications, allows users to build ad-hoc applications by launching components as waveforms and connecting them at run time to form a temporary, larger composite application.  The composite application can be configured by configuring properties of its constituent applications using the WaveDash tool.  Further, the Connect Tool provides for automatic instantiation and tear-down of applications, and automated connections and routing of data among standard applications, single-component applications, and plug-in tools, by specifying the applications/components/plug-ins and behavior in an XML file.  This enables dynamic reconfiguration of SDR applications at run time, a capability that can be very useful in cognitive radio implementations \cite{Cormier2009}.
%-------------------- FIGURE: ALF - CONNECT TOOL --------------------
\begin{figure} 
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=8.5cm]{figure18_ALF_Connect_Tool_2.pdf}
% trim = left bottom right top
\caption{ALF Connect Tool}
\label{fig:alf:connect}
\end{figure}



\subsection{Relation of ALF with WaveDash}
\label{sdrapplicationdevelopment-alf:relationwithwavedash}
When used together, ALF and WaveDash allow the user to observe effects of parameter values on waveform operation interactively and in real time, as shown in Figure~\ref{fig:alf:alfwavedash}.  This is very useful for education, experimentation, and debugging of waveform applications.  ALF currently provides some of the same functionality as WaveDash, specifically the ability to install/uninstall and start/stop applications.  This functionality is included in both tools so that WaveDash can be used to run applications without the full ALF environment.  WaveDash can be launched from within ALF, and further integration is planned.  Planned changes include encapsulating all common functionality of the two tools in a python module or library.
%-------------------- FIGURE: ALF AND WAVEDASH --------------------
\begin{figure*}
\centering
%\includegraphics[trim = 10mm 130mm 50mm 20mm, clip, width=10cm]{figure1.pdf}
\includegraphics[width=\textwidth]{figure19_ALF_QPSK_Controlled_Wavedash.pdf}
% trim = left bottom right top
\caption{ALF and WaveDash used together to monitor and control a waveform}
\label{fig:alf:alfwavedash}
\end{figure*}

\section{Conclusions and Future Work}
\label{conclusion}
This paper has described a set of open source SCA-based SDR development tools suitable for education, research, and rapid prototyping. These tools ensure SCA compatibility while hiding much its complexity and exploiting the features provided by the SCA to enable an interactive development process.  The development process includes creation of signal processing components and waveform applications as well as execution, visualization, monitoring, testing, and run time reconfiguration of waveform applications.  The Waveform Workshop tools also allow developers to interact directly with running waveforms and components, as well as to visualize the output from components in real time.

The current state of the Waveform Workshop allows for the work flow shown in the preceding sections, and also allows applications such as SimpleWaveform to be prototyped as ad-hoc applications and then recreated in OEF.  Additional development of the tools will enhance this capability by providing the option to display multiple application block diagrams in the same window, make connections by dragging lines between component ports, and formalize ad-hoc applications by saving connection and deployment information in waveform XML files. 

Upgrades to the Waveform Workshop are planned as part of current and pending projects.  These include the following tasks:
\begin{itemize}
\item Integrate ALF and WaveDash capabilities into Eclipse

\item Enable interactive block-diagram based waveform development

\item Move to full Java implementations of the tools

\item Load waveform and component descriptions by parsing the SCA XML files rather than using dedicated file formats (.ocd and .owd)

\item Add features for collaborative development

\item Add model-based development capability for greater flexibility

\end{itemize}

\subsection{New Tools}
\label{toolsdescription:wavedasharchitecture}
Finally, two new tools for the Waveform Workshop are under development. The first is a server to enable control of an OSSIE SDR application over http. After installing the server on a computer running OSSIE that is connected to the internet, any waveforms on that computer can be installed and controlled via any other computer with an internet connection.  The second new tool is a command line interface to allow a user to control an OSSIE SDR application over an ssh session or via scripts. Both of these applications are simply alternative views that share the same backend code as WaveDash. This allows them to easily connect to and control OSSIE SDR applications. 

\section{Acknowledgements}
\label{acknowledgements}
This work was supported by the National Science Foundation under Grant No. 0520418, by Science Applications International Corporation, and by U.S. ARMY CERDEC.

\begin{thebibliography}{00}

%% \bibitem{label}
%% Text of bibliographic item

\bibitem{Aguayo2009b}
C. R. Aguayo Gonz$\acute{a}$lez, et al., Open\-Source SCA\-Based Core Framework and Rapid Development Tools Enable Software\-Defined Radio Education and Research, IEEE Communications Magazine, vol 47, no. 10, October 2009.

\bibitem{ossieweb}
OSSIE project web site. \\Available:  http://www.ossie.wireless.vt.edu

\bibitem{sca}
Software Communications Architecture Specification, 2nd ed., Joint Tactical Radio System (JTRS) Joint Program Office, April 2004. 

\bibitem{bard}
J. Bard and V.J. Kovarik Jr., Software Defined Radio:  The Software Communications Architecture, Wiley, Chichester, West Sussex, England, 2007.

\bibitem{Aguayo2009a}
C. R. Aguayo Gonz$\acute{a}$lez , C. B. Dietrich, and J. H. Reed, Understanding the software communications architecture, IEEE Communications Magazine, vol. 47, no. 9, September 2009.


\bibitem{Reed2002}
J.H. Reed, Software radio: a modern approach to radio engineering, Prentice Hall PTR, 2002.

\bibitem{Vanu}
Vanu{\textregistered} Introduces the Anywave{\textregistered} MultiRAN - Wireless Industry's First Software Radio Shared Active Infrastructure Solution, \\Available:  http://www.vanu.com/media/Web%20Site%20Press%20Releases/vanu-multiran-final.pdf

\bibitem{JTRS}
JPEO JTRS, Joint Tactical Radio System\\
Available: http://jpeojtrs.mil

\bibitem{Gamma}
E. Gamma, R. Helm, R. Johnson, J.M. Vlissides, Design Patterns: Elements of Reusable Object-Oriented Software, Addison-Wesley Professional, 1994.

\bibitem{POSIX}
IEEE Std 1003.1, 2004 Edition\\
Available: http://www.unix.org/version3/ieee\_std.html

\bibitem{CORBA}
OMG's CORBA website\\
Available:  http://www.corba.org

\bibitem{XML}
Extensible Markup Language (XML) 1.1 (Second Edition)\\
Available:  http://www.w3.org/TR/2006/REC-xml11-20060816/

\bibitem{Robert2004}
M. Robert, et al., OSSIE: Open Source SCA for Researchers, SDR Forum Technical Conference, 2004.

\bibitem{SpectraCX}
PrismTech and Zeligsoft partner to deliver Spectra CX - a third-generation modeling tool for Software-Defined Radio (SDR/SCA) developers\\
Available:  http://www.mil-embedded.com/news/Technology+Partnerships/18395

\bibitem{ACE}
The ADAPTIVE Communication Environment (ACE \texttrademark)\\
Available:  http://www.cs.wustl.edu/~schmidt/ACE.html

\bibitem{Cormier2009}
A.R. Cormier, C.B. Dietrich, J. Price, and J.H. Reed, Dynamic reconfiguration of software defined radios using standard architectures, Physical Communication, June, 2010, doi: 10.1016/j.phycom.2009.09.002

\bibitem{singh}
Singh, S., M. Adrat, M. Antweiler, “NATO RTO/IST RTG on SDR: Demonstrating Portability and Interoperability of SCA-Based Waveforms,” SDR 09 Technical Conference and Product Exposition, Washington, DC, December 1-4, 2009.

\bibitem{dmtk}
dmTK home page, http://www.govcomm.harris.com/dmtk/, available 16 November 2010.

\bibitem{jianxin}
Guan Jianxin, Ye Xiaohui, Gao Jun, Wang Bo, “The Flow of Software Defined Radio Waveform Development Based on SCARI,” Wireless Communications, Networking and Mobile Computing, 2009. WiCom '09. 5th International Conference on, Beijing, China, 24-26 September 2009.

\bibitem{prismtech}
PrismTech Spectra CX webcast slides, http://www.slideshare.net/PrismTech1/spectra-cx-v32-webcast-19-may-2010, available 16 November 2010.

\bibitem{gnuradio}
GNU Radio Companion, http://gnuradio.org/redmine/wiki/1/GNURadioCompanion, available 16 November 2010.

\end{thebibliography}
\end{document}

% end of file template.tex