Space Communications and Navigation Program: Difference between revisions

Revision as of 12:29, 28 April 2014

Revision as of 12:51, 24 July 2014

Line 3:

==History==

Before NASA's administrator [[Michael D. Griffin]] created SCaN to direct an integrated networks program, different organizations at NASA Headquarters have managed the Agency’s space communications capabilities and functions under separate Programs using a variety of administrative approaches.<ref name="ProgramPlan">{{cite book| title = Space Communications and Navigation (SCaN) Program Plan| edition = | last = NASA| first = | coauthors = | publisher = National Aeronautics and Space Administration| id = | pages =}}</ref>

The SCaN Office was established by direction of Griffin in a Memorandum entitled “Establishment of a Space Communications and Navigation Office,” dated July 19, 2006.<ref name="SEMP">{{cite book| title = SCaN Systems Engineering Management Plan (SEMP)| edition = | last = NASA| first = | coauthors = | date = January 30, 2009| publisher = NASA Space Communication and Navigation Program Office| id = SCaN-SEMP| pages =}}</ref> SCaN operates as a central organization within the ''Human Exploration and Operations Mission Directorate'' (HEOMD):

{{cquote2|The Office’s responsibilities encompass the management of existing space networks including the Tracking and Data Relay Satellite system, the Deep Space Network, the Ground Network, the NASA Integrated Services Network; implementing any improvements and upgrades to those systems and networks; and developing any future NASA communications and navigation architectures.}}

Line 12:

==Services==

SCaN is viewed as a service provider supporting interfaces and performing a standard set of functions, including:<ref name="ConOps">{{cite book| title = Constellation Design Reference Missions And Operational Concepts (ConOps), Annex 1: Constellation Communications and Tracking Concept of Operations| edition = Baseline| last = NASA| first = | coauthors = | date = June 28, 2008| publisher = National Aeronautics and Space Administration| id = CxP 70007, ConOps| pages =}}</ref>

* Forward data transfer ([[uplink]] to spacecraft)

* Return data transfer ([[downlink]] from spacecraft to ground)

Line 29:

===Spectra===

The Space Network communicates with spacecraft using [[S-band]], [[Ku-band]],<ref name="SNUG">{{cite book| title =Space Network User's Guide (SNUG), 2.3, Elements of the SN | edition = Rev 9| last = NASA| first = Exploration and Space Communications Projects Division | coauthors author2= Goddard Space Flight Center | year = August 2007 | publisher = National Aeronautics and Space Administration| id =450-SNUG | pages = }}</ref> and [[Ka-band]] with planned laser/optical communications.

The Deep Space Network communicates with spacecraft using S-band, [[X-band]], and [[Ka-band]].

===Modulation===

SN uses [[Phase Shift Keying]] and [[Phase Modulation]] of the [[Carrier wave|carrier frequency]].<ref name="SNUG">{{cite book| title =Space Network User's Guide (SNUG), 6.2 SSA Forward Services, and 6.2.3 Phase Modulation (PM) Signal Parameters| edition = Rev 9| last = NASA| first = Exploration and Space Communications Projects Division | coauthors author2= Goddard Space Flight Center | year = August 2007 | publisher = National Aeronautics and Space Administration| id =450-SNUG | pages = }}</ref>

===Encoding===

The Space Network (used for near-Earth communications) supports the following encoding schemes:<ref name="SNUG">{{cite book| title =Space Network User's Guide (SNUGx)| edition = Rev 9| last = NASA| first = Exploration and Space Communications Projects Division | coauthors author2= Goddard Space Flight Center | year = August 2007 | publisher = National Aeronautics and Space Administration| id =450-SNUG | pages = }}</ref>

* [[BPSK]]

* [[QPSK]]/[[SQPSK]]