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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

database management, testing, trouble shooting, and scheduling) would update the<br />

PTP data, update NCCDS databases, and request NI<strong>SN</strong> gateway updates as needed.<br />

After customer/WDISC testing, the customer would use the NCCDS scheduling system<br />

to get routine WDISC services.<br />

Based on the WSGT and STGT schedules, the NCCDS controls the PTPs at each<br />

ground terminal for events that specify WDISC support. The MOC requests playbacks<br />

verbally or via email with WSC operations. For playbacks, a special file name (typically<br />

corresponding to a date of recording) is put in a PTP desktop and the desktop is<br />

activated manually to connect to the MOC and send data.<br />

Customer access to the WDISC is via TCP/IP connection for forward and return<br />

services. For forward services, the customer sends data via TCP/IP to the PTP at WSC.<br />

The PTP then sends that data to the WSC Local Interface (LI) via one of its PTP<br />

boards. The particular LI port to be used is identified by User Interface Channel (UIFC)<br />

ID. For return data, the PTP receives the data from the WSC LI via one of its PTP<br />

boards. It frame-syncs to the data and performs processing on it, if necessary. The<br />

data is then shipped to the customer via a TCP/IP connection. Mission-specific port<br />

numbers are assigned to each customer as required for control, as well as for data ports<br />

for forward and return services.<br />

Revision 10 Q-4 450-<strong>SN</strong>UG

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

Saved successfully!

Ooh no, something went wrong!