# Presentation: 740117

## Implementation of ICESat Communication Requirements

- September 16, 1999

- Clayton Sigman
- ESDIS Mission Systems Network Engineer & ESDIS Information Technology Security Official
- 301-614-5309
- clayton.sigman@gsfc.nasa.gov

## Topics

-   S-band
-  Assumptions
-  Data Flow Diagram
-   X-band
-  Assumptions
-  Data Flow Diagram
-   Other Assumptions
-   Requirements Tables
-   Issues/Concerns

-  Page

- ICESat Communications Requirements - Updated September 23, 1999

## S-band Assumptions

-  Page

- The ICESat Mission will be operated from a MOC at the CU-LASP in Boulder, Colorado
- ICESat S-band data flows are designed similarly to the QuikSCAT mission
- Real-time command and telemetry (S-band) between the MOC and AGS, SGS, and WGS are routed/Internet Protocol (IP) via IOnet
- S-band playback housekeeping data will be routed through the SAFS at the ground stations to the CSAFS at GSFC and distributed to its final destination(s)
-  ***Interface with Univ TX via vBNS? Abilene? Or EBnet?***

- ICESat Communications Requirements - Updated September 23, 1999

## S-band Data Flows

-  Page

- ICESat Communications Requirements - Updated September 23, 1999

## X-band Assumptions

-  Page

- ICESat X-band data flows are designed similarly to the PM-1 mission
- Science data (X-band) will be serial clock and data and will flow via the EDOS GSIF at AGS and SGS to the EDOS LZPF at GSFC
- All science data transfers from AGS and SGS to the NSIDC DAAC, including GLAS data, shall be via EDOS LZPF
-  Level Zero Science Data will be forwarded to the the NSIDC DAAC and to the ISIPS for generation and return of Science Data Products

- ICESat Communications Requirements - Updated September 23, 1999

## X-band Data Flows

-  Page

- ICESat Communications Requirements - Updated September 23, 1999

## Other Assumptions

-  Page

- Requirements provided to NISN to date have been operational support requirements
- Those interfaces requiring upgrade or new installation to support the above operational requirements will be in place one month before project need date
- Dates are needed to coordinate with integration and testing schedule
- The ability to support all requirements will require careful coordination and scheduling of shared ground station resources with other missions.

- ICESat Communications Requirements - Updated September 23, 1999

## Command Requirements

-  Page

- ICESat Communications Requirements - Updated September 23, 1999

## Real Time Housekeeping Requirements

-  Page

- ICESat Communications Requirements - Updated September 23, 1999

## Playback Housekeeping Requirements

-  Page

- ICESat Communications Requirements - Updated September 23, 1999

## Science Data Requirements

-  Page

- ICESat Communications Requirements - Updated September 23, 1999

## Science Products Requirements

-  Page

- ICESat Communications Requirements - Updated September 23, 1999

## Testing & Updates Requirements

-  Page

- ICESat Communications Requirements - Updated September 23, 1999

## Other Requirements

-  Page

- ICESat Communications Requirements - Updated September 23, 1999

## Issues/Concerns

-  Page

- Currently, only operational support requirements are known.
- Dates of tests must be confirmed to determine start dates of requirements.
- Launch requirements remain undefined. Three additional voice circuits at JPL required.
- Pre-launch & CTV test support  must be defined well in advance in order to ensure timely implementation.
- Voice circuit requirements remain incomplete.
- An exact location at CCR-University of Texas has not yet been specified for establishing connectivity.

- ICESat Communications Requirements - Updated September 23, 1999

## General Trouble Reporting

-  Page

- User identifies/recognizes communications problem
- User reports problem:
- Mission - Network Operations Management Center (NOMC): 301-286-6141
- Science Support - NISN Information Support Center (NISC): 256-544-1771
- User identifies interface experiencing trouble, including:
- Type of Interface: Routed or Clock & Data
- If Routed:
- Source and Destination IP addresses
- Multicast group, if applicable
- If Clock & Data
- Source and Destination location nodes
- Data Channel (e.g. channel 1:8:1)
- Describe problem (e.g. no data, corrupted data, when first noticed, history, etc.)
- Contact names and phone numbers at Source and Destination

- ICESat Communications Requirements - Updated September 23, 1999

## Network Operations Management Center

- Roles and Responsibilities

-  Page

- NOMC (GSFC CommMgr)
- Responsible for NISN Mission Support Services
- Receives trouble reports
- Coordinates with Tech Control, GSFC IPNOC, Voice Control, and maintenance for services restoration and performance testing
- Initiates escalation procedures for carrier services

- ICESat Communications Requirements - Updated September 23, 1999

## NISN Information Support Center

- Roles and Responsibilities

-  Page

- NISC
- Responsible for NISN Science Support Services
- Receives trouble reports
- Coordinates with MSFC IPNOC for services restoration and performance testing
- Initiates escalation procedures for carrier services
- Coordinates services and equipment releases
- Monitors network performance

- ICESat Communications Requirements - Updated September 23, 1999

## EOS

- Mission / Science Trouble Reporting

-  Page

- Network Operations Management Center
- NISN Communications Manager (CommMgr)
- 301--286-6141

- NISN Information Support Center
- NISN Help Desk
- 256-544-1771

- Technical Control
- GSFC IPNOC
- Mission Voice, Video, Data

- Carrier Resolution

- Premium/Standard IP, Facsimile,
- MSFC IPNOC
- LBV, Switched Voice & Conferencing

- Carrier Resolution

- ICESat Communications Requirements - Updated September 23, 1999