d port component. The into three parts: baseband processing (assigned to component is both a resource and a port. a DSP), link processing (assigned to a GPP), and a user CHAPTER 2.4a The software defined radio as a platform for cognitive radio 2.4a.7 Cognitive waveform development Resource In the context of SDR, a cognitive engine is just another component of a waveform, SO the issue in cognitive engine deployment becomes one of component com- plexity. In the simplest case, a developer can choose to create components that are very flexible, an example of Figure 2.4a-16 Fan-in, fan-out structure for a component. The which is seen in Figure 2.4a-18. The flexible baseband resource uses both input and output ports. processor seen in this figure can respond to requests from the cognitive engine and alter its functionality. A similar interface (assigned to the same GPP). A diagram of this level of functionality is also available in the link- waveform is shown in Figure 2.4a-17. processing component. The system shown in Figure The application shown in Figure 2.4a-17 has several 2.4a-18 is a slight modification of the system shown in pieces that should be readily recognized; the application Figure 2.4a-17. The principal difference in this system is was generated by the framework as a result of the the addition of a reverse-direction set of ports and ApplicationFactory. Furthermore, the three proxies changed functionality for each component. representing the relevant processing for the radio are also The principal problem with the structure shown in shown. Since the baseband processing is performed on Figure 2.4a-18 is that it places all the complexity of the a DSP, the component shown is a proxy for data transfer system onto each separate component. Furthermore, the to and from the DSP. Link processing and the user in- tie-in between the cognitive engine and the rest of the terface, however, are actually implemented on the GPP. waveform risks the engine implementation to be limited The assembly controller shown is part o