{"title":"Software defined radios (SDR) platform and application programming interfaces (API)","authors":"B. Tarver, E. Christensen, A. Miller","doi":"10.1109/MILCOM.2001.985781","DOIUrl":null,"url":null,"abstract":"A software defined radio, as defined by the Federal Communications Commission (FCC) Notice of Proposed Rule Making (NPRM), FCC 00-430, is fully software driven and performs all digital signal processing using programmable digital signal processors, general purpose microprocessors, or field programmable gate arrays. All functions, modes, and applications can be reconfigured by software. More importantly, new capability can be added without hardware changes enabling a new generation of communication waveform developers to create new applications without intimate alliances with radio manufacturers. However, to be successful, the union of the application with the platform must be clearly understood with well-defined application programming interfaces (APIs). The well-defined interfaces form the contract between the application developer and the platform developer. The well-defined interfaces allow an application developer to develop an application once, that executes on many different manufacturers' platforms and provides the platform developer consistent interfaces under which platform technologies can evolve separately from the application. An application is independent of the platform it runs on if it is not coupled to a specific platform implementation, i.e., does not require platform unique hardware or software components for execution. The application accesses platform services through well-defined public interfaces that support the entire lifecycle of the application, i.e., from installation of the application through removal of the application from any given platform. This paper discusses SDR software architecture features, the need and definition of a common set of APIs and their extensibility into classes addressing factors such as cost and capability.","PeriodicalId":136537,"journal":{"name":"2001 MILCOM Proceedings Communications for Network-Centric Operations: Creating the Information Force (Cat. No.01CH37277)","volume":"587 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2001-10-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"6","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2001 MILCOM Proceedings Communications for Network-Centric Operations: Creating the Information Force (Cat. No.01CH37277)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/MILCOM.2001.985781","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 6
Abstract
A software defined radio, as defined by the Federal Communications Commission (FCC) Notice of Proposed Rule Making (NPRM), FCC 00-430, is fully software driven and performs all digital signal processing using programmable digital signal processors, general purpose microprocessors, or field programmable gate arrays. All functions, modes, and applications can be reconfigured by software. More importantly, new capability can be added without hardware changes enabling a new generation of communication waveform developers to create new applications without intimate alliances with radio manufacturers. However, to be successful, the union of the application with the platform must be clearly understood with well-defined application programming interfaces (APIs). The well-defined interfaces form the contract between the application developer and the platform developer. The well-defined interfaces allow an application developer to develop an application once, that executes on many different manufacturers' platforms and provides the platform developer consistent interfaces under which platform technologies can evolve separately from the application. An application is independent of the platform it runs on if it is not coupled to a specific platform implementation, i.e., does not require platform unique hardware or software components for execution. The application accesses platform services through well-defined public interfaces that support the entire lifecycle of the application, i.e., from installation of the application through removal of the application from any given platform. This paper discusses SDR software architecture features, the need and definition of a common set of APIs and their extensibility into classes addressing factors such as cost and capability.