**Radios Project Proposal**

The Cognitive Radio Test System (CRTS) provides a flexible framework for over the air test and evaluation of cognitive radio (CR) networks. 

GNU Radio is a popular processing framework for SDR applications. It provides an environment for the deployment and management of processing units. The basic processing unit is a block. \cite{robert2015software} 

In order to leverage GNU Radio's capabilities for CRTS, it's important to interface the two. CRTS uses scenario controllers to provide a centralized and customizable way to receive feedback and exert control over a scenario’s operation in real time. A simple API can be used to enable or disable specific types of feedback from each node involved in the scenario, receive said feedback, and even directly control the scenario test parameters e.g. the network throughput as well as the operating parameters of the radio e.g. its transmit power. \cite{crts_manual}. This would involve writing a new CRTS block for GNU Radio.

Since there is a new CRTS under development, this project would take into considerations new design changes that would affect this project. 

~~~~~~~~~~~~~~~~~~
\section{Schedule}
Considering an 8-week time period, the following is the proposed schedule.
\begin{table}[h]
    \centering
    \begin{tabular}{|c|c|}
    \hline
         Week & Topic \\
         \hline 
         1 & GNU Radio basics\\
         2 & Understanding scenario controller \\
         3 & Understanding new controller code \\
         4 & Understaning GNU Radio companion interface \\
         5 & Implementation \\
         6 & Implementation \\
         7 & Implementation \\
         8 & Implementation \\
         \hline
    \end{tabular}
    \caption{Proposed Schedule}
    \label{tab:schedule}
\end{table}

\begin{comment}
What is a scenario?

What is a scenario controller?

Why do we need a CRTS block in GNURadio?

This is a simple python flowgraph that was developed using GNURadio-companion. It reads data from the tunCRTS virtual interface using the TUNTAP_PDU block, and passes it along to a second node via a Socket_PDU block operating in server mode. The second node receives the data from a Socket PDU block operating in client mode, then passes it to the TUNTAP PDU block to write the data to the tunCRTS virtual interface. This radio can be used as a template for other python radios, by replacing the Socket_PDU blocks with USRP blocks to send the data over the air, rather than over the network

Scenario controllers provide a centralized and customizable way to receive feedback and exert control over a scenario’s operation in real time. A simple API can be used to enable or disable specific types of feedback from each node involved in the scenario, receive said feedback, and even directly control the scenario test parameters e.g. the network throughput as well as the operating parameters of the radio e.g. its transmit power.

In order to communicate with CRTS nodes 

\end{comment}
~~~~~~~~~~~~~~~~~~

Reply
--------------
looks good submit some examples for the final report

<!-- Markdeep: -->
<style class="fallback">body{visibility:hidden;white-space:pre;font-family:monospace}</style><script src="markdeep.min.js"></script>
<script src="https://casual-effects.com/markdeep/latest/markdeep.min.js"></script>
<script>window.alreadyProcessedMarkdeep||(document.body.style.visibility="visible")</script>