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 7-11. TDRS KuSAR IF Service Spacecraft and Ground Segment Channel<br />

Characteristics (cont’d)<br />

Notes:<br />

1. The customer should schedule the TDRS receive center frequency to the KuSAR TDRS receive<br />

center frequency, where the TDRS receive center frequency will be translated to the center of the IF<br />

bandwidth. The signal and carrier frequency will be constrained such that the first null of the<br />

spectrum falls between 14.8834 and 15.1234 GHz. The KuSAR IF service only supports noncoherent<br />

frequencies. The KuSAR IF service supports only one Ku frequency through one TDRS at<br />

a time. These frequencies do not include the effects of Doppler shift. The KuSAR IF service is not<br />

required to provide a Doppler-corrected IF output signal. The customer provided receiver needs to<br />

handle Doppler.<br />

2. Constraint parameters are contributions from the TDRS spacecraft and the <strong>SN</strong> ground segment to<br />

the IF interface. Not included in these aggregate distortion amounts are TDRS spacecraft gain<br />

flatness, linear and parabolic allowances, and phase nonlinearity parabolic and cubic allowances as<br />

described in 405-TDRS-RP-SY-001, WU-02-01, and SY1-89E. Customer and receiver signal<br />

characteristics need to be considered to determine the end-to-end performance. Please contact<br />

GSFC Code 450 for further information.<br />

3. The 3 dB RF bandwidth is larger than the specified 225 MHz bandwidth value specified in Table 7-7.<br />

This value has validated through spacecraft and ground terminal measurements, but may not be<br />

applicable to future TDRS.<br />

Table 7-12. Potential TDRSS KuSA IF Return Service Configurations (Customer<br />

interfaces with the <strong>SN</strong> at a 370 MHz IF and Customer provides the Receiver)<br />

BPSK<br />

QPSK /<br />

SQPSK<br />

8PSK<br />

Return IF Service Configuration<br />

(notes 1, 2)<br />

Potential Maximum Data Rates<br />

(IF Service)<br />

Rate 1/2 convolutional coded See Table 7-6<br />

Uncoded See Table 7-6<br />

Rate 1/2 convolutional coded See Table 7-6<br />

Uncoded See Table 7-6<br />

(128,120)x(128,120) TPC (note 3) 400 Mbps<br />

(8176,7136) LDPCC (notes 3, 4) 400 Mbps<br />

(2048, 1024) AR4JA LDPCC 200 Mbps<br />

(128,120)x(128,120) TPC (note 3) 600 Mbps<br />

(8176,7136) LDPCC (notes 3, 4) 600 Mbps<br />

Uncoded 450 Mbps<br />

Notes:<br />

1. All data rates assume NRZ data format.<br />

2. These service configurations and maximum data rates were based upon simulation<br />

results only and have not been verified by testing. Other data rates and modulation<br />

schemes may be possible. Please contact GSFC Code 450 for further information.<br />

3. For the IF service, data rates up to 410 Mbps may be possible for QPSK/SQPSK<br />

modulation with either TPC or (8176, 7136) LDPCC. For the 225 MHz IF service, data<br />

rates up to 625 Mbps may be possible for 8PSK with either TPC or (8176,7136)<br />

LDPCC. Please contact GSFC Code 450 for further information.<br />

4. The code being supported is the (8160, 7136), the shortened version of the (8176,<br />

7136) code.<br />

Revision 10 7-48 450-<strong>SN</strong>UG

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

Saved successfully!

Ooh no, something went wrong!