Louis M. Handler and Janette C. Briones

Glenn Research Center, Cleveland, Ohio

Dale J. Mortensen

ASRC Aerospace Corporation, Cleveland, Ohio

Richard C. Reinhart

Glenn Research Center, Cleveland, Ohio

Space Telecommunications Radio System (STRS) 

Architecture

Tutorial Part 1—Overview

NASA/TM—2012-217819

December 2012
NASA STI Program . . . in Profi le

Since its founding, NASA has been dedicated to the 

advancement of aeronautics and space science. The 

NASA Scientifi c and Technical Information (STI) 

program plays a key part in helping NASA maintain 

this important role.

The NASA STI Program operates under the auspices 

of the Agency Chief Information Offi cer. It collects, 

organizes, provides for archiving, and disseminates 

NASA’s STI. The NASA STI program provides access 

to the NASA Aeronautics and Space Database and 

its public interface, the NASA Technical Reports 

Server, thus providing one of the largest collections 

of aeronautical and space science STI in the world. 

Results are published in both non-NASA channels 

and by NASA in the NASA STI Report Series, which 

includes the following report types:

• TECHNICAL PUBLICATION. Reports of 

completed research or a major signifi cant phase 

of research that present the results of NASA 

programs and include extensive data or theoretical 

analysis. Includes compilations of signifi cant 

scientifi c and technical data and information 

deemed to be of continuing reference value. 

NASA counterpart of peer-reviewed formal 

professional papers but has less stringent 

limitations on manuscript length and extent of 

graphic presentations.

• TECHNICAL MEMORANDUM. Scientifi c 

and technical fi ndings that are preliminary or 

of specialized interest, e.g., quick release 

reports, working papers, and bibliographies that 

contain minimal annotation. Does not contain 

extensive analysis.

• CONTRACTOR REPORT. Scientifi c and 

technical fi ndings by NASA-sponsored 

contractors and grantees.

• CONFERENCE PUBLICATION. Collected 

papers from scientifi c and technical 

conferences, symposia, seminars, or other 

meetings sponsored or cosponsored by NASA.

• SPECIAL PUBLICATION. Scientifi c, 

technical, or historical information from 

NASA programs, projects, and missions, often 

concerned with subjects having substantial 

public interest.

• TECHNICAL TRANSLATION. Englishlanguage translations of foreign scientifi c and 

technical material pertinent to NASA’s mission.

Specialized services also include creating custom 

thesauri, building customized databases, organizing 

and publishing research results.

For more information about the NASA STI 

program, see the following:

• Access the NASA STI program home page at 

http://www.sti.nasa.gov

• E-mail your question to help@sti.nasa.gov

• Fax your question to the NASA STI 

Information Desk at 443–757–5803

• Phone the NASA STI Information Desk at

 443–757–5802

• Write to:

 STI Information Desk

 NASA Center for AeroSpace Information

 7115 Standard Drive

 Hanover, MD 21076–1320
Louis M. Handler and Janette C. Briones

Glenn Research Center, Cleveland, Ohio

Dale J. Mortensen

ASRC Aerospace Corporation, Cleveland, Ohio

Richard C. Reinhart

Glenn Research Center, Cleveland, Ohio

Space Telecommunications Radio System (STRS) 

Architecture

Tutorial Part 1—Overview

NASA/TM—2012-217819

December 2012

National Aeronautics and

Space Administration

Glenn Research Center

Cleveland, Ohio 44135
Available from

NASA Center for Aerospace Information

7115 Standard Drive

Hanover, MD 21076–1320

National Technical Information Service

5301 Shawnee Road

Alexandria, VA 22312

Available electronically at http://www.sti.nasa.gov

Trade names and trademarks are used in this report for identifi cation 

only. Their usage does not constitute an offi cial endorsement, 

either expressed or implied, by the National Aeronautics and 

Space Administration.

Level of Review: This material has been technically reviewed by technical management. 
Space Telecommunications Radio System (STRS) Architecture 

Tutorial Part 1—Overview 

Louis M. Handler and Janette C. Briones 

National Aeronautics and Space Administration 

Glenn Research Center 

Cleveland, Ohio 44135 

Dale J. Mortensen 

ASRC Aerospace Corporation 

Cleveland, Ohio 44135 

Richard C. Reinhart 

National Aeronautics and Space Administration 

Glenn Research Center 

Cleveland, Ohio 44135 

Abstract 

Space Telecommunications Radio System (STRS) Architecture Standard provides a NASA standard 

for software-defined radio. STRS is being demonstrated in the Space Communications and Navigation 

(SCaN) Testbed formerly known as Communications, Navigation and Networking Configurable Testbed 

(CoNNeCT). Ground station radios communicating the SCaN testbed are also being written to comply 

with the STRS architecture. The STRS Architecture Tutorial Overview presents a general introduction to 

the STRS architecture standard developed at the NASA Glenn Research Center (GRC), addresses 

frequently asked questions, and clarifies methods of implementing the standard. The STRS architecture 

should be used as a base for many of NASA’s future telecommunications technologies. The presentation 

will provide a basic understanding of STRS.

NASA/TM—2012-217819 1

National Aeronautics and Space Administration

Space Telecommunicatio

Radio System (STRS) 

Architecture

Tutorial Part 1 - Overview

Glenn Research Center

November 2011

NASA/TM—2012-217819 3
National Aeronautics and Space Administration

STRS Architecture

• STRS Background• STRS Hardware & Software Structur• STRS Infrastructure APIs• STRS Application APIs• STRS Configuration Files• STRS Reference Documents

NASA/TM—2012-217819 4
National Aeronautics and Space Administration

STRS Background

NASA/TM—2012-217819 5
National Aeronautics and Space Administration

STRS Goals and Objectives

• Applicable to space and ground missions of varyin

complexity.

• Decrease the development time and cost of deploy

capabilities.

• Increase the reliability of deployed radios.• Accommodate advances in technology with minim

rework.

• Adaptable to evolving requirements.• Enable interoperability with existing radio assets.• Leverage existing or developing standards, resour

and experience.

• Maintain vendor independence.• Enable waveform portability between compliant pla• Enable cognitive radio concepts.

NASA/TM—2012-217819 6
National Aeronautics and Space Administration

STRS Solution: Software-Defined Radio (S

• SDRs are commonplace in commercial and militar

industries.

– accommodates advances in technology– enables cognitive radio concepts

• SDRs allow encapsulation of functionality.

– allows multiple vendors to work on different par

radio at once

– allows updates to one part not to affect the othe

of the radio 

– allows portability

• Software design and implementation processes m

leveraged to lower risk and increase reliability

NASA/TM—2012-217819 7
National Aeronautics and Space Administration

STRS Background

• SDRs present unique challenges in space.

– Radiation environment– Temperature extremes– Autonomous operation– Size, weight, and power (SWaP) limitations– Timescale of deployments– Lengthy development cycles

• JTRS/SCA and OMG/SWRADIO were investigated

– including CORBA was too cumbersome due to SWaP – including an XML parser was too cumbersome due to S– SCA’s XML configuration files were too complex for ou– Used Platform Independent Model (PIM) as a starting p

STRS API design

• Decided to allow a C language interface to minimize 

NASA/TM—2012-217819 8
National Aeronautics and Space Administration

STRS Hardware and 

Software Structure

NASA/TM—2012-217819 9
National Aeronautics and Space Administration

SDR Signal Processing Hardware

HW

GPP

• General P

Processotypically cexecutes Software Software functiona

• Specialize

contains aApplicatio(i.e. firmwhigher ratwithin the Defined RFPGA)

NASA/TM—2012-217819 10
National Aeronautics and Space Administration

Waveform Application Decomposit

• Low rate waapplication coallocated to psignal processservices used monitor applic•Operating Enprovides acceand specializewaveform pro•High rate waapplication coallocated to sprocessing ha

Waveform Applications & High Level Services

Waveform Component Waveform Component

Operating Environment

HW Waveform decompos

by designers, not arc

NASA/TM—2012-217819 11
National Aeronautics and Space Administration

STRS Open Architecture

Waveform Application API and Hardware Abstractio

●Waveform desspecified API to and implements the GPP ● APIs specified separate the waOperating Envirowaveform portab●Operating Envpublished interfaservices and haabstraction cont●Hardware Abst(HAL) also provihelp port HDL soplatforms

Waveform Applications & High Level Services

APIHW Waveform Component Waveform Component

Operating Environment

NASA/TM—2012-217819 12
National Aeronautics and Space Administration

• Layer cake model– Waveform applications and high level services are insulated 

APIs

– STRS APIs abstract

away many platformdifferences

– POSIX used to 

reduce APIdevelopment

– OE– Hardware Abstraction

Layer (HAL)

STRS Architecture

NASA/TM—2012-217819 13
National Aeronautics and Space Administration

www.nasa.gov

STRS Architecture Conformance

Optional

Conformant to STRS 

Architecture Standard 

requirements for 

applications

Conformant to STRS 

Architecture Standard 

(STRS and WF APIs)

Compliant to POSIX PSE51 

or Subset with Waiver

Documented HAL and HID 

as required by STRS 

Architecture Specification

12

NASA/TM—2012-217819 14
National Aeronautics and Space Administration

Layer Cake Transition to UML

The software layer cake was UML to describe the software object-oriented style.

NASA/TM—2012-217819 15
National Aeronautics and Space Administration

STRS Layered Structure

NASA/TM—2012-217819 16
National Aeronautics and Space Administration

STRS Infrastructure APIs

NASA/TM—2012-217819 17
National Aeronautics and Space Administration

STRS Infrastructure APIs

• STRS Infrastructure APIs are used:

– Waveform calls methods in Infrastructure.– Infrastructure calls appropriate method in another W

Device, or Infrastructure.

• Purpose:

– Methods separate a request from the accomplishme

request.

– Methods are ‘extern “C”’ so that they can be called f

either C or C++.

– Methods insulate waveforms from having to know ho

another waveform, device or the infrastructure is implemented.

NASA/TM—2012-217819 18
National Aeronautics and Space Administration

STRS Infrastructure APIs

Queue Control• STRS_QueueCreate• STRS_QueueDelete• STRS_Read• STRS_Register• STRS_Log• STRS_Write• STRS_UnregisterDevice Control• STRS_DeviceClose• STRS_DeviceFlush• STRS_DeviceLoad• STRS_DeviceOpen• STRS_DeviceReset• STRS_DeviceStart• STRS_DeviceStop• STRS_DeviceUnload• STRS_SetISRTesting• STRS_RunTest• STRS_GroundTestAttribute• STRS_Configure• STRS_QueryProcess Errors• STRS_GetErrorQueue• STRS_IsOK

• The STRS So

Architecture pconsistent seallow wavefoapplications, and communequipment to in meeting a wspecification

• These APIs a

general or to waveform fro

• The list to the 

minimum list the STRS plainfrastructure implement 

Control• STRS_Initialize• STRS_ReleaseObject• STRS_Start• STRS_StopApplication • STRS_HandleRequest • STRS_InstantiateApp• STRS_AbortAppTime • STRS_GetNanoseconds• STRS_GetSeconds• STRS_GetTimeWarp• STRS_GetTime• STRS_SetTime• STRS_SynchFile (Named Area)• STRS_FileClose• STRS_FileGetFreeSpace• STRS_FileGetSize• STRS_FileOpen• STRS_FileRemove• STRS_FileRename

NASA/TM—2012-217819 19
National Aeronautics and Space Administration

STRS OE Compliance

STRS OE

StaticDynamic(debug)

Implements STRS_A

Document

HAL,

Uses HAL APIUses STRS ApplicatioHID, etc.Supports DeviceSupports FileSupports QueueSupports health/fault Parses configuration BITWDTSupports WF

NASA/TM—2012-217819 20
National Aeronautics and Space Administration

STRS Waveform APIs

NASA/TM—2012-217819 21
National Aeronautics and Space Administration

STRS Waveform Application Complian

• A waveform is an STRS Application and must implement the APIs shown in the diagram• An STRS Application hasOMG similarity; but STRS requires everything, except source and sink (STRS replaces OMG ports with source/sinks)• The diagram shows how a Device fits in the infrastructure

o Device is internal, must have 

the shown functionality

o Device is an abstraction 

(proxy) that uses the HAL to get to the hardware

o No standard for the HAL API. 

Standard is at Device level (provider)

NASA/TM—2012-217819 22
National Aeronautics and Space Administration

POSIX Compliance/Conform

An STRS operating environment can either use an OS that conforms with 10provide a POSIX abstraction layer that provides missing PSE51 interfaces. resource platforms, the POSIX requirement is based on waveform requiremwaveforms are upward compatible (require POSIX methods).

NASA/TM—2012-217819 23
National Aeronautics and Space Administration

STRS Waveform Compliance

STRS WF

StaticDynamic(debug)

Implements STRS Ap

Document

Uses Configuration FUses STRS InfrastrucWF executes (not peWF signal interoperat(not STRS responsibUses POSIX AEP

NASA/TM—2012-217819 24
National Aeronautics and Space Administration

STRS Configuration File

NASA/TM—2012-217819 25
National Aeronautics and Space Administration

Configuration Files

• Require schema and 

XML as part of the architecture

• The required XML 

should be transformed to a compact format

• The approach for the 

transformation is not mandated as part of the architecture 

• STRS Reference 

Implementation uses XSL/XSLT to transform XML to an S-expression as compact form

Schema

XML

Compact 

Form

Schema is used to validate XML. XML follows Schema.

T

Transforma

Completed XML, schema, and XSL used to create compact formTested code in STRS Infrastructure to parse compact form for waveforms

NASA/TM—2012-217819 26
National Aeronautics and Space Administration

STRS Reference Docume

NASA/TM—2012-217819 27
National Aeronautics and Space Administration

STRS Reference Documents

• Space Telecommunications Radio System (ST

Architecture Standard Release 1.02.1, Decem2010, NASA TM 2010-216809

http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/20110002806_20110• Space Telecommunications Radio System (ST

Architecture Goals/Objectives and Level 1 Requirements Document, June 2007, NASA T2007-215042. 

http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/20080008862_20080• Space Telecommunications Radio System (ST

Definitions and Acronyms, May 2008, NASA T2008-215445.

http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/20090005977_20090

NASA/TM—2012-217819 28
National Aeronautics and Space Administration

Backup Slides

NASA/TM—2012-217819 29
National Aeronautics and Space Administration

Waveform State Diagram

NASA/TM—2012-217819 30
National Aeronautics and Space Administration

Simplified Diagram

WF

STRS 

Infrastructur

STRS 

APIs

WF 

APIs

OS

POSIX 

APIs

NASA/TM—2012-217819 31
National Aeronautics and Space Administration

STRS Reference Implementation Developme

Use Case Identifier: Example Use CaseDescription: A Description of the use case goes here.External Actors: External actor(s) involved with thisspecific use-case.Related Use Cases: Use cases that related to this usecase by interaction or similarity.Precondition: Any precondition that must exist beforethis use case can occur. Usually the initial RADIOstate and WAVEFORM state is listed.Triggering event: Event that triggers use case. Notall use cases have triggering eventsMain Flow:1.This will be an ordered list of steps necessary to perform interaction. This is the nominal flow. Alternate flows will be listed below.2.Step 23.Step 34.Step 45.etc.Resulting event: If completion of use case results inan event it is listed here. Usually the resulting RADIOstate and WAVEFORM state is listed.Post condition: Describe the result of the use caseinteraction. (This is the post condition from thenominal flow)Alternatives:1a) This is where alternate flows are identified. The alternative will be identified by the number of the main flow where the branch occurs followed by a letter a-z.3a) This is an example of an alternative flow for step 3.3b) This is the second step in the alternative flow for step 3.7a-8a) This is an alternative flow for a range of steps from the main flow.Comments: Comments on use case.

: STRS Command and Data 

<<subsystem>>

: RTOS

Power On Sequence Diagram

1: Power On (Boot)

5: STRS INITIALIZING state9: STRS READY state

Load and initializeSTRS Infrastructure

3: 

2: Perform BIT

Refines RequirementsRefines Requirements

Class Di

Sequenc

Use Case

Solicited Monitored Item

-parameterName-queueName-valueList-testType-delay+checkParameter()+isSolicited()+getDelay()+deactive()+isActive()+activate()

STRS Application Control API

+WF_StartProcessing()+WF_StopProcessing()+WF_FreeResources()+WF_GetAttribute()+WF_SetAttribute()+WF_BuiltInTest()+WF_Init()

...

+unregister( publisher, subscriber )+register( publisher, subscriber )+closeQueue()+openQueue()+instance()+notify()

Messaging Manager

-publishSubscribeTable

Unsolicited Monitored Item

-parameterName-queueName-valueList-testType+checkParameter()+deactivate()+isSolicited()+isActive()+activate()

STRS Messaging API

+STRS_QueueRequest()+STRS_QueueCreate()+STRS_QueueDelete()+STRS_Unregister()+STRS_Register()

Applications Manager

-configTable-appTable+parseConfigurationFile()+instance()

Fault Manager

+resetWatchDogTimer()+builtInTest()

Memo

+reserv+releas

STRS Application

UploadControl

+requestUpload()+getStatistics()+abortUpload()+isComplete()+progress()

Real-Time Clock

+getTime()+synch()

+unload()+setISR()+close()+flush()+load()

Device

-monitorItemList

Health Monitor

+addTest()+start()+stop()

UploadService

Data Source

+read()

Da

Data Source

Data Source

Data Sink

+write()

Navigation

D

Data Sink

Data Sink

0..*

notifies

*

1

Data Sink

Data Source

creates

0..*

1

*

1

NASA/TM—2012-217819 32
National Aeronautics and Space Administration

Use Case Overview

Spacecraft

STRS Radio

Control

Waveform

ConfigureWaveform

Manage

Waveform

Catalog

Control Radio

Access

Waveform

System Health Manager

 <<includes>>Set Waveform ParameterGet Waveform Parameter

 <<includes>>Waveform InstantiationWaveform DeallocationStart WaveformStop Waveform <<includes>>Upload WaveformRemove Waveform

<<includes>> Transmit Receive

<<includes>>Fault Manager

<<includes>>Power OnPower Off

STRS Command and Control

External Port Flight Computer

Payload

Other Space Vehicle

Over the Air User

Ground Station 

<<use

A set of use cases were developed which is a set of scenarios that capt

different ways that external users interact with the STRS radio. 

NASA/TM—2012-217819 33
National Aeronautics and Space Administration

Class Example

Application Manager• The Application Manager is 

responsible for the passing of messages or invoking commands in other application objects such as devices, waveforms, or services actively running on the STRS radio. 

• It is responsible for creating or 

aborting application objects, waveforms, or services. 

• It is also responsible for parsing 

the Configuration Files and setting corresponding values in the appropriate classes.

Application Manager-appTable-configTable+parseConfigurationF+instance()

Name – Name that identi

class and describes the 

Attributes – Variables con

applicable data

Methods – Functions that 

implement some operation

Above is an example UML representation 

NASA/TM—2012-217819 34
National Aeronautics and Space Administration

STRS Open Architecture Hardwa

Representation

Data

Clock

Control

Modules

General

Purpose

Processing

Module (GPM)

Specialized 

Processing 

Module (SPM)

Radio

Frequency

Module (RFM)

Ground Test

External Connections

Data

Control

Internal Connections

Clock

System Bus

External Interface

NASA/TM—2012-217819 35
National Aeronautics and Space Administration

SDR/STRS Hardware Functiona

Diagram

text text

text

Data 

Formatting

Spacecraft 

Data 

Interface

Clock 

Distribution

Transmit RF Digital to Analog

General Processing Module (GPM)

 General Purpose Processor

Host/TT&C

Interface

Ground Test 

Interface

Low Speed 

Signal 

Processing

Persistent Memory

RF Mo

Radio 

Configuration 

& System 

Work Area Memory Control

High Speed

Digital Signal 

Processing

Signal Processing Module (SPM)

Anten

Interfa

Clock 

Interface

Analog to 

Digital Receive RF

Operating

Environment

Waveform / 

Application

System 

Control

Variable 

Gain/

Frequency

Test & 

Status

Test & 

Status

Data 

Buffer/

Storage

 Waveform

NASA/TM—2012-217819 36
National Aeronautics and Space Administration

SDR/STRS Hardware Functiona

Diagram

text text

text

Data 

Formatting

Spacecraft 

Data 

Interface

Clock 

Distribution

Transmit RF Digital to Analog

General Processing Module (GPM)

 General Purpose Processor

Host/TT&C

Interface

Ground Test 

Interface

Low Speed 

Signal 

Processing

Persistent Memory

RF Mo

Radio 

Configuration 

& System 

Work Area Memory Control

High Speed

Digital Signal 

Processing

Signal Processing Module (SPM)

Anten

Interfa

Clock 

Interface

Analog to 

Digital Receive RF

Operating

Environment

Waveform / 

Application

System 

Control

Variable 

Gain/

Frequency

Test & 

Status

Test & 

Status

Data 

Buffer/

Storage

 Waveform

General Proconsists of tprocessor, aspacecraft b1553) , interPCI), and thsupport the radio.

Signal Processing Module – signal processing used to handle the transformation of digital signals into data packets. Components include ASIC’s, FPGA’s, DSP’s, memory, and connection fabric/bus (e.g. PCI, flex-fabric)

RF Module –handles the RF functionathe digital signal. Its associated composwitches, diplexer, filters, LNAs and p

NASA/TM—2012-217819 37
National Aeronautics and Space Administration

text text

text

Data 

Formatting

Spacecraft 

Data 

Interface

Clock 

Distribution

Transmit RF Digital to Analog

General Processing Module (GPM)

 General Purpose Processor

Host/TT&C

Interface

Ground Test 

Interface

Low Speed 

Signal 

Processing

Persistent Memory

RF Mo

Radio 

Configuration 

& System 

Work Area Memory Control

High Speed

Digital Signal 

Processing

Signal Processing Module (SPM)

Anten

Interfa

Clock 

Interface

Analog to 

Digital Receive RF

Operating

Environment

Waveform / 

Application

HAL

System 

Control

Variable 

Gain/

Frequency

Test & 

Status

Test & 

Status

Data 

Buffer/

Storage

 Waveform

API

STRS Hardware Functional Diagra

Module Interfaces abstract and define the module functionality for data flow to waveform componmultiple vendors to provide different modules or add modules to existing radios. Electrical interfarequirements, and physical requirements are specified/published by the platform provider.

HAL API ispecialized multiple veintegrated STRS infra

Software/Firmware Abstraction: Layers define interfaces between components, separating SW/FW from HW.APIs separate waveform from operating environment – enabling waveform portability.

Managing So

NASA/TM—2012-217819 38
National Aeronautics and Space Administration

The End

NASA/TM—2012-217819 39
REPORT DOCUMENTATION PAGE Form Approved 

OMB No. 0704-0188 

The public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the 

data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this 

burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0704-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302. 

Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB 

control number. 

PLEASE DO NOT RETURN YOUR FORM TO THE ABOVE ADDRESS. 

1. REPORT DATE (DD-MM-YYYY)

01-12-2012 

2. REPORT TYPE

Technical Memorandum 

3. DATES COVERED (From - To)

4. TITLE AND SUBTITLE

Space Telecommunications Radio System (STRS) Architecture 

Tutorial Part 1--Overview

5a. CONTRACT NUMBER

5b. GRANT NUMBER

5c. PROGRAM ELEMENT NUMBER

6. AUTHOR(S)

Handler, Louis, M.; Briones, Janette, C.; Mortensen, Dale, J.; Reinhart, Richard, C. 

5d. PROJECT NUMBER

5e. TASK NUMBER

5f. WORK UNIT NUMBER

WBS 439432.04.07.01 

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES)

National Aeronautics and Space Administration 

John H. Glenn Research Center at Lewis Field 

Cleveland, Ohio 44135-3191 

8. PERFORMING ORGANIZATION

 REPORT NUMBER

E-18561 

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES)

National Aeronautics and Space Administration 

Washington, DC 20546-0001 

10. SPONSORING/MONITOR'S

 ACRONYM(S)

NASA 

11. SPONSORING/MONITORING

 REPORT NUMBER

NASA/TM-2012-217819 

12. DISTRIBUTION/AVAILABILITY STATEMENT

Unclassified-Unlimited 

Subject Categories: 17 and 61 

Available electronically at http://www.sti.nasa.gov 

This publication is available from the NASA Center for AeroSpace Information, 443-757-5802

13. SUPPLEMENTARY NOTES

14. ABSTRACT

Space Telecommunications Radio System (STRS) Architecture Standard provides a NASA standard for software-defined radio. STRS is

being demonstrated in the Space Communications and Navigation (SCaN) Testbed formerly known as Communications, Navigation and 

Networking Configurable Testbed (CoNNeCT). Ground station radios communicating the SCaN testbed are also being written to comply 

with the STRS architecture. The STRS Architecture Tutorial Overview presents a general introduction to the STRS architecture standard 

developed at the NASA Glenn Research Center (GRC), addresses frequently asked questions, and clarifies methods of implementing the 

standard. The STRS architecture should be used as a base for many of NASA’s future telecommunications technologies. The presentation 

will provide a basic understanding of STRS. 

15. SUBJECT TERMS

User manuals (computer programming); Architecture (computers); Telecommunications 

16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF

 ABSTRACT

UU 

18. NUMBER

 OF 

 PAGES

46 

19a. NAME OF RESPONSIBLE PERSON

STI Help Desk (email:help@sti.nasa.gov) 

a. REPORT

U 

b. ABSTRACT

U 

c. THIS 

PAGE

U 

19b. TELEPHONE NUMBER (include area code)

443-757-5802 

Standard Form 298 (Rev. 8-98)

Prescribed by ANSI Std. Z39-18