1. © 2004 Mercury Computer Systems, Inc. Implementation Design Choices for the SWRadio Specification A. Tansu Demirbilek ademirbi(at)mc(dot)com

2. © 2004 Mercury Computer Systems, Inc. Overview l Brief overview of the SWRadio Specification l PIM Facilities (waveform, channel) l Waveform Example using APIs l Real-time Aspects l Additional RFPs for waveform services

3. © 2004 Mercury Computer Systems, Inc. SWRadio Products Overview

4. © 2004 Mercury Computer Systems, Inc. Scope of SWRadio Spec Middleware Platform (e.g. CORBA/XML) External Client Software Radio Infrastructure Waveform Application (1)(2) (1) External client calls software radio infrastructure to request the services of a waveform application We will concentrate on this part contains interfaces specified by SWRadio spec (2) Infrastructure calls waveform application to request initiation

5. © 2004 Mercury Computer Systems, Inc. SWRadio Waveform Application l A Waveform application compliant with the SWRadio specification shall: wImplement the related CORBA interfaces defined by Waveform Applications PSM wImplement the related XML Serialization formats defined by Waveform Applications PSM wImplement the related semantics defined by Waveform Applications PIM

6. © 2004 Mercury Computer Systems, Inc. SCA API Supplement SCA 2.2 CORBA 1 SWRadio API PSM SCA 2.2 CORBA 2 SWRadio Infra PSM CORBA SWRadio API PSM 3 Lw CCM CORBA D&C SWRadio API PSM 4 CORBA SCA 2.2 D&C SWRadio API PSM 5 CORBA SWRadio Infra PSM D&C SWRadio API PSM 6 Waveform API Realization Options l Waveform APIs can be realized independent from the underlying SDR infrastructure l Only need to realize the Waveform interfaces

7. © 2004 Mercury Computer Systems, Inc. Overview l Brief overview of the SWRadio Specification l PIM Facilities (waveform, channel) l Waveform Example using APIs l Real-time Aspects l Additional RFPs for waveform services

8. © 2004 Mercury Computer Systems, Inc. PIM Facilities l Common Layer Facilities cut through layers l Radio Control Facilities include channel management, radio management l Common Radio Facilities are non-WF related services l Physical, I/O, MAC, LLC are based on OSI defns Waveform Facilities

9. © 2004 Mercury Computer Systems, Inc. Waveform PIM l Defines waveform related data and control interfaces l Based on the “Extended” OSI Model* l Semantic descriptions for the components realizing the interfaces l Product of a survey of existing specs such as: 3GPP, DLPI, GLoMo, OBSAI, CPRI, 802.x, X.200e * ISO 7498-1: Open System Interconnection – Basic Reference Model

10. © 2004 Mercury Computer Systems, Inc. How are they used? l Component based programming model l Similar to Flow-Based Programming* l Waveform elements realize control interfaces and achieve “configurable modularity” l Waveform PIM definitions aim to provide a complete set of configuration parameters * “Flow-Based Programming: A New Approach to Application Development”, J. Paul Morrison, Thomson Publishing, 1994 Data Out 1 Data Out 2 Waveform Component Data In Control Interfaces

11. © 2004 Mercury Computer Systems, Inc. PIM Facilities: Common Layer l Flow Control – control communication flow so that a sender does not transmit more packets than a receiver can process. l QoS Management – control quality of service related parameters. l Measurement Facilities – set up and schedule measurement parameters. l Error Control Facilities -- allows the Receiver to tell the Sender about frames damaged or lost during transmission, and coordinates the re-transmission of those frames by the Sender. l PDU Facilities – Protocol Data Units (PDU) are used as information packets both within and between radio sets l Stream Facilities – used in connection oriented communication among radio sets as well as inter-component communication within a radio.

12. © 2004 Mercury Computer Systems, Inc. PIM: Common Layer: Flow Control l Separate signaling and management interfaces l One flow control manager component per waveform, one signaling component for each channel l Can be implemented by both transmitter and receiver l Prevents overflow of data, ensures proper handling of data packets

13. © 2004 Mercury Computer Systems, Inc. PIM: Common Layer: PDU

14. © 2004 Mercury Computer Systems, Inc. PIM: Common Layer: QoS Management l Based on DLPI specification l Allows the Radio Resource Controller to config/query QoS parameters l Interface does not mandate any underlying protocol for transmitting and negotiating QoS parameters with the peer RadioSet * “Data Link Provider Interface”, The Open Group, 1997

15. © 2004 Mercury Computer Systems, Inc. PIM: Common Layer: Stream l Intended for setting up connectionless streams l Can be used for setting up a data stream between two components in the same radio set (vertical communication) l Can be used for setting up a data stream between two radio sets (horizontal communication)

16. © 2004 Mercury Computer Systems, Inc. PIM: Common Layer: Error Control l StatusSignal interface provides a mechanism to report transmission/reception errors l IErrorControl interface provides operations that the waveform controller can use to instruct different levels of error control on a component

17. © 2004 Mercury Computer Systems, Inc. PIM: Physical Layer l Interfaces on both control and data planes l Most of the signal processing is done at this layer l Provides parameterization of waveform algorithms for portable, modular code l Used to control the communication equipment device attributes defined in the UML Profile l Partitioned into: wModem Facilities wRF/IF Facilities

18. © 2004 Mercury Computer Systems, Inc. PIM: Physical Layer: RF/IF l RF/IF Interfaces l Allow controlling the parameters of hardware devices as defined in the UML Profile: Communication Equipment

19. © 2004 Mercury Computer Systems, Inc. PIM: Physical Layer: Modem

20. © 2004 Mercury Computer Systems, Inc. PIM: Data Link Layer: MAC l Provides control over medium access parameters l A MAC Component realizes interfaces that are defined in the Common Layer Facilities, as well as the IMediumAccessControl l IMacPdu specializes IPdu by binding its own header and SDU types l MAC Component provides Flow Control, Scheduling, Error Control, QoS, as well as services given by IMediumAccessControl

21. © 2004 Mercury Computer Systems, Inc. PIM: Data Link Layer: LLC l ILocalLinkManagement is common for both connection oriented and connectionless link protocols l Enables controlling the link parameters that only affect the local radio set l Typically realized by the same component that realizes all of the link related interfaces for a given WF

22. © 2004 Mercury Computer Systems, Inc. PIM: Data Link Layer: LLC l Connectionless link (packet based) does not have any extra interfaces, other than the common layer ones l Has its own pdu definitions, derived from IPriorityPdu

23. © 2004 Mercury Computer Systems, Inc. PIM: Data Link Layer: LLC l IConnectionLink provides the functionality to mux/demux/establish multiple data (circuit switched) streams l Once a data stream is started, it is treated as a continuous pipeline of data

24. © 2004 Mercury Computer Systems, Inc. PIM: Radio Control: Radio Management l Management of the radio (domain management) l Management of devices and services within a radio (device management) l Communication channel interfaces provide a mechanism for specifying the connection of WF components, and the general properties of the instantiated WF

25. © 2004 Mercury Computer Systems, Inc. PIM: Radio Control: Radio Management

26. © 2004 Mercury Computer Systems, Inc. Conclusion – PIM l Provides waveform portability through standard software interfaces Organized as in OSI model l Does not require layered implementation l Coherent with key characteristics of UML model l Can be extended to create vertical I/O models

27. © 2004 Mercury Computer Systems, Inc. Overview l Brief overview of the SWRadio Specification l PIM Facilities (waveform, channel) l Waveform Example using APIs l Real-time Aspects l Additional RFPs for waveform services

28. © 2004 Mercury Computer Systems, Inc. Example l A simple component example that realizes IPdu interface l Stereotyped as > l Has one output port l Illustrates how a waveform component can be implemented by realizing the interfaces

29. © 2004 Mercury Computer Systems, Inc. PIM: Common Layer: Flow Control l Separate signaling and management interfaces l One flow control manager component per waveform, one signaling component for each channel l Can be implemented by both transmitter and receiver l Prevents overflow of data, ensures proper handling of data packets

30. © 2004 Mercury Computer Systems, Inc. PIM: Common Layer: PDU

31. © 2004 Mercury Computer Systems, Inc. UML Profile: Resource Components

32. © 2004 Mercury Computer Systems, Inc. > ComponentB Data > ComponentA Control Interfaces > l ComponentA realizes IPdu interface, which inherits from ISimplePdu and IFlowControlSignalling interfaces l It is stereotyped as a ResourceComponent, so it provides the required interfaces PortSupplier, PropertySet, ControllableComponent, etc. These interfaces are used in realizing swrapi’s l ComponentB can send flow control related signals to ComponentA, by using IPdu interface l Another upstream component can control ComponentA to send its data using pushPdu operation l Data can be marshaled by the middleware, or it can by-pass the middleware for performance reasons Middleware

33. © 2004 Mercury Computer Systems, Inc. Overview l Brief overview of the SWRadio Specification l PIM Facilities (waveform, channel) l Waveform Example using APIs l Real-time Aspects l Additional RFPs for waveform services

34. © 2004 Mercury Computer Systems, Inc. Processing Power

35. © 2004 Mercury Computer Systems, Inc. Platform Architecture Container A Container B Each container has a single processing element Components with different timing requirements should run on different containers

36. © 2004 Mercury Computer Systems, Inc. Platform Architecture Container A Container B Comp A Runs once every 20ms Each execution takes 8ms

37. © 2004 Mercury Computer Systems, Inc. Platform Architecture Container A Container B Comp A

38. © 2004 Mercury Computer Systems, Inc. Platform Architecture Container A Container B Comp A Comp B Runs once every 2ms Each execution takes 1.2ms

39. © 2004 Mercury Computer Systems, Inc. Platform Architecture Container A Container B Comp A Comp B

40. © 2004 Mercury Computer Systems, Inc. Memory Buffer 1 Memory Buffer N Platform Architecture Container A Container B Comp A Comp B Memory Buffer N Memor y Buffer 1............ Multiple memory buffers enable components to run independently, without waiting for buffers to fill

41. © 2004 Mercury Computer Systems, Inc. Memory Buffer 1 Memory Buffer N Platform Architecture Container A Container B Comp A Comp B Memory Buffer N Memor y Buffer 1............ Switch Fabric / Middleware Fabric handles congestion management and priority based routing Switch fabric & Middleware provides transparent communication

42. © 2004 Mercury Computer Systems, Inc. Overview l Brief overview of the SWRadio Specification l PIM Facilities (waveform, channel) l Waveform Example using APIs l Real-time Aspects l Additional RFPs for waveform services

43. © 2004 Mercury Computer Systems, Inc. Digital IF RFP l Was issued in Aug 2004, by SBC DTF l PIM for control interfaces of tuners and exciters in a high bandwidth digital streaming system l Data descriptors for the messages passed across the digital Intermediate Frequency (IF) platform l A UML 2.0 compliant profile that allows the modeling of system aspects, topology and data flow

44. © 2004 Mercury Computer Systems, Inc. Digital IF RFP Tx DATA + Control (b) Control, Status (e) Control, Status (a) Synch Synthesizer Digital IF Interfaces Rx DATA + Status (d) (c)

45. © 2004 Mercury Computer Systems, Inc. Smart Antenna RFP Smart Antenna Interface l Was issued in Aug 2004, by SBC DTF l RFP solicits additional antenna PIM definition that will build upon the SWRadio spec, antenna interfaces

46. © 2004 Mercury Computer Systems, Inc. Security RFPs New RFPs underway: 1. key management (generation, distribution, storage, lifecycle, certificates, etc. including group keying support), 2. crypto algorithm selection & management, 3. secure audit, 4. transmission security.