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.

headers supported are the Standard Formatted Data Unit (SFDU), Advanced X-ray<br />

Astrophysics Facility – Imagery (AXAF-I), Advanced Composition Explorer (ACE), Low<br />

Earth Orbit-Terminal (LEO-T), and the IP Data Unit (IPDU).<br />

DAS transmits Customer service data, both real-time and playback, as asynchronous<br />

data streams encapsulated in TCP/IP without any CCSDS processing or encapsulation<br />

unless otherwise specified by the Customer in a service request. In this case, the PTP<br />

is used to simply archive the data and to stream it as TCP/IP packets for delivery. With<br />

TCP/IP reliability, this method provides the highest assurance that the data received by<br />

the Customer MOC is exactly the same as the data received by the DAS demodulator.<br />

DAS provides telemetry data with the least manipulation for Customers with their own<br />

PTPs.<br />

H.3.3 Customer Interactions with DAS<br />

The Customer can interact with DAS in two time frames: Planning/Scheduling prior to<br />

an event or events, and during an event. During the planning/scheduling phase, the<br />

Customer schedules resources for service by interacting with DAS through <strong>SN</strong>AS.<br />

During an event, the Customer can monitor the status of communications from the<br />

Customer platform and, if necessary, modify parameters that control the<br />

communications during the event.<br />

H.3.3.1 The Planning/Scheduling Phase<br />

DAS service support begins with planning sequences. Planning sequences include<br />

interaction between DAS and the Customer to set up a resource allocation request<br />

within the context of the available DAS MAR resource times and the resource utilization<br />

objectives. This customer interaction provides DAS with the time window(s) in which<br />

the Customer requests DAS resources. DAS in turn provides the Customer with the<br />

available service time(s) and the associated TDRS(s) available for the support within<br />

the specified time window. The customer can then vary parameters of their request<br />

derived from this information.<br />

NOTE:<br />

If a dedicated customer preempts a non-dedicated customer,<br />

DAS will attempt to reschedule the non-dedicated<br />

customer’s preempted support at another time within the<br />

requested window.<br />

The customer sends a request via <strong>SN</strong>AS for the resources desired, including customer<br />

identification and location (ephemeris), identification of the TDRS(s) requested,<br />

parameters of resources requested, period of the request, demodulator parameters,<br />

archive and retrieval requests, and data forwarding requirements. DAS will interact with<br />

the Customer via <strong>SN</strong>AS to establish and confirm a customer request.<br />

Upon receipt of a specific request for resources, DAS will examine the parameters<br />

required to set up the request and determine if they are feasible. If DAS determines<br />

that the request is not within the capability of the system, DAS will notify the customer to<br />

this effect.<br />

Revision 10 H-16 450-<strong>SN</strong>UG

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

Saved successfully!

Ooh no, something went wrong!