02.04.2013 Views

SN User's Guide - ESC Home - NASA

SN User's Guide - ESC Home - NASA

SN User's Guide - ESC Home - NASA

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Table 8-1. TDRSS KaSA Forward Service Signal Parameters (cont’d)<br />

Notes (cont’d):<br />

2. The forward data rate in this table is the baud rate that will be transmitted by the TDRSS<br />

(includes all coding and symbol formatting). For non-WDISC customers, forward data<br />

conditioning is transparent to the <strong>SN</strong>. For all customers, forward convolutional coding is<br />

transparent to the <strong>SN</strong>. These transparent operations should be performed by the customer prior<br />

to transmission to the <strong>SN</strong> data interface. Refer to Section 3, paragraph 3.6 for a description of<br />

<strong>SN</strong> data interfaces, associated constraints, and WDISC capabilities. WSC/GRGT is capable of<br />

25 Mbps with changes.<br />

3. The <strong>SN</strong> is capable of supporting BPSK signals at data rates less than 300 kbps; however, its use<br />

will be controlled and must be coordinated with GSFC Code 450.<br />

4. After the start of the KaSA forward service, if a customer MOC is unable to accurately define fo (the nominal center frequency of the customer platform receiver), the forward service carrier<br />

frequency can be swept. The KaSA forward service frequency sweep will be initiated by the <strong>SN</strong><br />

ground terminal at fo-30 kHz and linearly swept to fo +30 kHz in 120 seconds and held at fo +30<br />

kHz thereafter. The KaSA forward service frequency sweep does not impact simultaneous <strong>SN</strong><br />

ground terminal Doppler compensation of the KaSA forward service carrier and PN code rate (if<br />

applicable).<br />

fo<br />

22555<br />

6<br />

5. “K” =<br />

10<br />

Rounded to the nearest integer if K integer and 0 < K < 198.<br />

5<br />

fo is the nominal center frequency in Hz of the customer platform receiver as defined by the<br />

customer MOC.<br />

6. Customers who operate in a SS-BPSK mode for one service cannot reconfigure any of their<br />

Forward Services (i.e., MAF, SMAF, SSAF, KuSAF, or KaSAF) to an SS-UQPSK mode. Contact<br />

Code 450 if additional flexibility is required.<br />

This modulation scheme includes separate but simultaneous command and<br />

range channels. The command channel includes a rapidly acquirable PN code<br />

and contains the forward service data. The range channel is acquired<br />

separately and contains a PN code which satisfies the range ambiguity<br />

resolution requirements. The length of the command channel PN code is 2 10 -1,<br />

where the length of the range channel PN code is 256 times the command<br />

channel PN code length. The customer platform command channel acquisition<br />

can precede customer platform range channel acquisition; this feature permits<br />

rapid acquisition of the range channel by limiting the range channel PN code<br />

search to only 256 chip positions while the range channel PN code itself<br />

contains 261,888 chips. The PN code chip rate is coherently related to the<br />

TDRS transmit frequency in all cases. This feature permits the customer<br />

platform receiver to use the receiver PN code clock to predict the received<br />

carrier frequency, thereby minimizing receiver complexity and reducing<br />

acquisition time. 451-PN CODE-<strong>SN</strong>IP defines all the salient characteristics for<br />

the forward range and command channel PN code libraries. The Agency<br />

Spectrum Manager responsible for PN code assignments will allocate a<br />

customer platform-unique PN code assignment from these libraries. The GSFC<br />

Spectrum Manager is responsible for <strong>NASA</strong> PN code assignments.<br />

Revision 10 8-6 450-<strong>SN</strong>UG

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!