<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Kickoff</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.17080" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010>Hi Larry (& et al)</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010>Thanks for the slide link</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010>An element of interest to me is thinking about how SDR
for space might be different than "conventional" or "terrestrial" SDR systems,
across the spectrum of views (operational, system, interface, services,
etc).</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010>It might also be useful to express where/how this group
thinks it should relate to similar or related efforts within SDR Forum
and OMG? For that matter, how should this effort relate to the other
efforts within CCSDS outside of SOIS?
</SPAN></FONT></DIV></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010>Given the potential range of usages for SDR in space, I
think it would be worthwhile to try to capture and articulate a couple of the
usage scenarios that might serve as uses cases to help define or bound the scope
of this group and help with the process of defining a
charter...</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010>1) Spacecraft TT&C related communications -
typically needs low data rate but high reliability links with high degree of
protection/security (at least on command transfers) on an occasional basis to
support mission operations. May operate in broadcast (omni) mode for
transmit and receive at S/C to mitigate pointing concerns but may also operate
using point-to-point link services.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010>2) Mission/Payload related communications -
driven by mission sensor data generation needs but may scale from low to high to
very high data rates with periodic to continuous transmission requirements with
variable quality of service and security needs (mission dependent). May
operate in a point to point, multi-cast or broadcast mode of
operations, depending on specific mission.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010>3) Proximity operations - typically local area space to
space communications for coordinating RPOD type activities. Implies a
situational awareness and potential closed loop control needs due to potential
use for collision avoidance. Viewed as similar to TT&C needs wrt data
rates. May have additional functionality embedded in comm system
architecture for S/C identification and location information
provisioning</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010>4) Cluster/Constellation related communications -
Virtual spacecraft data bus for "distributed spacecraft" concepts that provides
the means for transferring data and other spacecraft related "bus services"
needed for mission operations. "Distributed spacecraft" concepts may necessitate
(or at least raise the potential) for special features in the comm system
architecture, similar to prox ops, but may include timing and frequency
distribution and precision relative navigation metrology</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010>5) Navigation, Tracking and/or Data Relay related
communications - SDR as a payload for supporting space operations, such as
providing navigation reference signals, performing tracking of incoming signals
and/or serving as a bent pipe or processing repeater of some sort. (SATCOM
payload systems could also fall into this category, as well as TDRS and GPS type
systems)</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010>6) Multi-function Software Defined RF Payloads - SDR
systems that can serve multiple purposes, such as act as radar, comm system and
even sensor payload for RF sensing missions.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010>7) Wireless spacecraft bus - SDR as a means of
implementing a wireless databus for spacecraft command and control as an
alternative to wired (MIL-STD-1553, SpaceWire, optical fiber) options for
distributing services within the spacecraft</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010>Regards</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010>Michael</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010>
<DIV align=left><FONT face=Arial size=2>Michael Enoch</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Sr. Staff Systems Engineer</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Lockheed Martin Space Systems
Company</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>
<DIV align=left><FONT face=Arial size=2>2100 Airpark Road SE</FONT></DIV>
<DIV align=left>Suite 150 East</DIV>
<DIV align=left><FONT face=Arial size=2>Albuquerque, NM 87106</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Voice:
505-222-6084</FONT></DIV></FONT><FONT face=Arial size=2>Mobile:
505-301-1166</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Pager: 888-861-1141</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>SMS:
8888611141@page.metrocall.com</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Email:
michael.enoch@lmco.com</FONT></DIV></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=329352922-17082010></SPAN></FONT> </DIV><FONT face=Arial
color=#0000ff></FONT><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sois-sdr-bounces@mailman.ccsds.org
[mailto:sois-sdr-bounces@mailman.ccsds.org] <B>On Behalf Of </B>Foore, Larry R.
(GRC-RHD0)<BR><B>Sent:</B> Monday, August 09, 2010 2:48 PM<BR><B>To:</B>
sois-sdr@mailman.ccsds.org<BR><B>Subject:</B> EXTERNAL: [Sois-sdr]
Kickoff<BR></FONT><BR></DIV>
<DIV></DIV><FONT face="Lucida Grande"><SPAN
style="FONT-SIZE: 11pt">All,<BR>Thanks for subscribing to the mailing list.
In approximately one month, I’ll report to Adrian the membership of this
list and hopefully any pros/cons we jointly discuss regarding addressing
reconfigurable platforms within CCSDS.<BR><BR>What may be an instructive
exercise is to consider how Prox-1 may be implemented and fielded on two
separately developed/provided SDRs. What would need to be clarified for
waveform developers and/or system integrators to ensure interoperability?
Would it be limited to a common lexicon for SDRs, or perhaps more?
Is a reference architecture necessary with clearly articulated and
supported functions? These are just a few questions to get a dialogue
going.<BR><BR>Perhaps such a dialogue would help us understand 1) the necessity
(or lack thereof) of an SDR WG, 2) the bounds of such a group, and 3) the
objectives of such a group.<BR><BR>As a matter of reference, the content of the
STRS Architecture lunchtime talk during the Spring CCSDS meeting in Portsmouth,
VA can be found here:<BR><BR><A
href="http://public.ccsds.org/meetings/2010Spring/Tech/lunchtime/Foore-CCSDS%20STRS%20Presentation%20May%203rd.pdf">http://public.ccsds.org/meetings/2010Spring/Tech/lunchtime/Foore-CCSDS%20STRS%20Presentation%20May%203rd.pdf</A><BR><BR><BR>Thanks
again,<BR>Larry</SPAN></FONT> </BODY></HTML>