Network Orientation DAT14

1
Network OrientationDAT14

• Valeta Glover
• June 2000

Teledyne Brown Engineering
2
Agenda

• Introduction
• Overview
• Acronyms Glossary
• Data Onboard
• Space-to-Ground
• United States Ground System
• International Ground System
• POIC
• PDSS and routing
• Transmission methods and protocols
• Interfaces between the POIC, remote sites, and
  Partner Gateways
• Reference Material

3
Introduction

• This course describes the ground network that
  supports data transmission upon its receipt from
  the ISS
• It will start with a description of onboard data
  and the space-to-ground network.
• It will go into more detail about the US Ground
  System and will briefly tell about the
  International Ground System.
• It will then describe the POIC and its ground
  services, including PDSS which routes the data.
• It will describe various transmission methods and
  protocols used to transport data.
• It also lists reference documentation where more
  details on any of these topics can be found.

4
Overview

• There are three distinct areas that define the
  data routing and downlink process. They are
  onboard systems, the space-to-ground
  communications network, and the ground data
  distribution system. This handout focuses on the
  ground data distribution system, but will contain
  some information on the on-board and
  space-to-ground network in order to give a
  complete picture.
• Once the data reaches the ground, distribution
  must be made to the users and program
  participants. The US. Ground System (USGS)
  includes all the NASA sites that are a part of
  ISS and the systems that are at these sites. The
  International Ground System encompasses all the
  major sites around the world that will be
  exchanging data, voice, and video. The USGS
  receives the data and distributes it. The
  HOSC/POIC is the site here at MSFC which will be
  controlling Payload data, voice, and video. The
  POIC interfaces with the other NASA centers,
  Partner payload centers, and payload users at
  various remote sites.
• The SSCC distributes core system data to the US
  Engineering support centers and the Partner
  Control Centers.
  Payload data
  distribution is coordinated between POIC/PDSS and
  the Partners.

5
Acronyms

• A/G Air to Ground
• APID Application Process Identifier
• APMCC Attached Pressurized Module Control Center
• APS Automated Payload Switch
• ARC Ames Research Center
• ASI Agenzia Spaziale Italiana (Italian Space
  Agency)
• ATVCC automated Transfer Vehicle Control Center
• BANDIT Bandwidth Integration Timeliner
• BPDU Bitstream Protocol Data Unit
• CC MDM Command and Control Multiplexer/Demultiple
  xer
• CCSDS Consultative Committee on Space Data
  Systems
• CDP Custom Data Packet
• Cmd Command
• Comm Communication
• COR Communications Outage Recorder
• CPS Consolidated Planning System
• CSA Canadian Space Agency

6
Acronyms

• ECO End-to-End Configuration Officer
• EDS Enhanced Data System
• EHS Enhanced HOSC System
• EMCS Enhanced Mission Communications System
• ERIS EHS Remote Interface System
• ESA European Space Agency
• EVA Extra Vehicular Activity
• EViDS Enhanced Video Distribution System
• EVoDS Enhanced Voice Distribution System
• FEP Front End Processor
• FTP File Transfer Protocol
• GC Ground Controller
• GRC Glenn Research Center (formerly LeRC)
• GSE Ground Support Equipment
• GSFC Goddard Space Flight Center
• HOSC Huntsville Operations Support Center

7
Acronyms

• ICD Interface Control Document
• I/F Interface
• IGS IVT International Ground Segment Integration
  Verification Test
• IGSS International Ground System segment
• IONet
• IP International Partner
• IP Internet Protocol
• IPS Integrated Planning System
• ISS International Space Station
• IST Integrated Support Team
• iURC interim User Requirements Collection
• JEM Japanese Experiment Module
• JSC Johnson Space Center
• kbps kilobits per second
• KSC Kennedy Space Center
• LAN Local Area Network

8
Acronyms

• MBF Multi-Build Facility
• Mbps Megabits per second
• MCC-H Mission Control Center - Houston
• MDL Micro-Gravity Development Laboratory
• MDM Multiplexer DeMultiplexer
• MHz Mega Hertz
• MPLM Mini-Pressurized Logisitics Module
• MRMDF Multiple Remote Manipulator Development
  Facility
• MSFC Marshall Space Flight Center
• MSS LAN Mission System Services Local Area
  Network
• NASA National Aeronautics and Space
  Administration
• NASDA National Space Agency of Japan
• NBL Neutral Bounancy Laboratory
• NCC Network Control Center
• NISN NASA Integrated Services Network
• NPRD Network Program Requirements Document
• NTSC National Television Standards Committee

9
Acronyms

• PCC Partner Control Center
• PCD POIC Capabilities Document
• PDI Payload Data Interleaver
• PDL Payload Data Library
• PDSRS PDSS Data Storage and Retrieval Subsystem
• PDSS Payload Data Services System
• PEHG Payload Ethernet Hub/Gateway
• PICF Payload Integration and Checkout Facility
• PIMS Payload Information Management System
• PG Product Group
• PGUIDD POIC to Generic User Interface Definition
  Document
• POIC Payload Operations Integration Center
• POIF Payload Operations Integration Function
• PPS Payload Planning System
• PRD Program Requirements Document
• Proc Procedure
• PSIV Payload System Integration Verification
• PTC Payload Training Center
• PTT Part Task Trainer

10
Acronyms

• RSA Russian Space Agency
• SES System Engineering Simulator
• SGS Space to Ground Subsystem
• SGTRC Space to Ground Transmit Receive Controller
• SMAC System Monitor and Control
• SMTP Simple Mail Transfer Protocol
• SOSC Space Operations Support Center
• SSCC Space Station Control Center
• SSH Secure Shell
• SSIPC Space Station Integration and Promotion
  Center
• SSL3 Secure Socket Layer 3
• SSMTF Space Station Mock-up Training Facility
• SSPF Space Station Processing Facility
• SSTF Space Station Training Facility
• S/W Software
• TAS Test And Simulation

11
Acronyms

• UDC Utilization Development Capability
• UDP User Datagram Protocol
• UF Utilization Flight
• UPD User Performance Data
• US United States
• USGS United States Ground System
• USOC United States Operations Center
• USOS United States On-orbit Segment
• VAL Validation
• WISARD Weekly Implementor of Systems and
  Resources for Data
• WSC White Sands Complex
• ZOE Zone of Exclusion

12
Glossary of Terms

• air-to-ground audio -- audio communications
  between the on-orbit space station and the ground
  in support of on-orbit operations including
  private a/g audio for medical information.
• air-to-ground video -- video generated onboard
  the on-orbit space station and transmitted to the
  ground.
• APID -- a number which gives source and
  destination information. It is used for routing
  data.
• audio -- audio communications between ground
  facilities in support of ground functions and
  training. Also referred to as coordination audio
• bandwidth -- a measure of spectrum (frequency)
  use or capacity. The higher (wider) the
  bandwidth the greater the amount of information
  it can carry.
• BPDU -- Bitstream Protocol Data Unit. A CCSDS
  protocol data unit of the bitstream function. It
  has a header followed by a fixed length block of
  contiguous bitstream data.
• CCSDS Packets -- Data formatted in accordance
  with recommendations or standards of the
  Consultative Committee on Space Data Systems.
  The packets have a primary header, an optional
  secondary header and source data.
• commands -- commands generated on the ground
  destined for the on-orbit space station. Command
  uplink includes payload commands and core system
  commands. This interface also includes the
  uplink of data files to the on-orbit Space
  Station.
• downlink data -- data generated onboard the
  on-orbit Space Station and transmitted to the
  ground as telemetry. Data downlink may include
  health and status, science data, medical data,
  ancillary data, and core systems data. This
  interface also includes the downlink of onboard
  data files and command responses.
• downlink video -- video generated on-board the
  on-Orbit Space Station and transmitted to the
  ground. It is converted from analog to digital
  back to analog.

13
Glossary of Terms

• EHS -- Enhanced HOSC Systems -- All the systems
  required to perform data acquisition and
  distribution, telemetry processing, command
  services, database services, mission support
  services, and system monitor and control
  services.
• forward link -- data going from the ground to the
  on-orbit space station (via TDRSS)
• frequency -- number of cycles per second of an
  electromagnetic transmission. Generally higher
  frequencies can carry more information at greater
  speeds.
• geosynchronous orbit -- a circular orbit above
  the equator. Satellite is 22,237 miles above the
  earth and stays above the same point on the
  earths surface.
• interface -- a means of interaction between two
  systems or groups
• kbps -- kilobits per second. Refers to
  transmission speed of 1000 bits per seconds.
• Ku-Band -- A portion of the electromagnetic
  spectrum used to deliver data from spacecraft to
  ground.
• Mbps -- Megabits per second. Refers to
  transmission speed of 1,000,000 bits per second.
• Network -- A way of connecting computer resources
  that handles communications between pieces of
  equipment.
• planning and procedures data -- the planning and
  procedures data required for realtime operations
  support or pre-increment preparations between
  facilities in support of ground functions. e.g.
  activity schedules, weekly plans, on-orbit
  summaries, etc.
• protocol -- a set of rules that define formats
  of transmitted data and the time sequences
  between devices.
• return link data -- data coming from the
  on-orbit space station to the ground (via TDRSS)

14
Glossary of Terms

• S-Band -- A lower frequency in the
  electromagnetic spectrum. Used to carry core
  systems information from the spacecraft to the
  ground.
• T1 -- a size of communication line
• TCP -- Transmission Control Protocol - TCP is a
  connection -oriented protocol. The computer
  sending the data will actually connect to the
  computer that will receive the data. since there
  is a connection between the two computers, all of
  the data will be delivered in the order it was
  sent.
• telemetry -- data delivered to the ground from
  the on-orbit vehicle. Telemetry is down-link
  only. Telemetry is not uplinked.
• TSC -- Telescience Support Center -- a NASA
  facility which provides the capability to plan
  and operate on-orbit payloads and experiments.
• UDP -- User Datagram Protocol - UDP is a
  connectionless-oriented protocol. The computer
  sending the data doesnt connect to a specific
  computer, but instead broadcasts the data to an
  address. Since the data is broadcast, the
  computer sending the data does not know if any
  other computer received it. In addition, the
  data may be received out of order.
• video -- video communications between ground
  facilities in support of ground functions. The
  term video may include recorded video playback
  or video teleconferencing.
• X-windows -- a standared for a multi-session
  protocol between an application and a display.
  It allows someone to log-on to another computer
  and see the displays from it on your own.

15
Overview Figure
shuttle
TDRSS

DomSat
ISS
Ku-Band

JSC
MSFC
SSCC
POIC

S-band over IONet
16
Data Onboard

• ISS onboard systems and payloads generate data
• Each payload or sub-rack payload may be assigned
  one or more APIDs for the routing of telemetry
  data.
• Data that is generated may be science data,
  housekeeping data, or health and status data
• Payload data is routed from the payload to the
  APS to the HRFM to the HRM to the Space to Ground
  Transmitter Receiver Controller (SGTRC) and thru
  the Ku-Band antenna to TDRSS.
• S-band digital data goes through the CC MDM to
  the Assembly Contingency Baseband Signal
  Processor.
• Payloads being transported on the Shuttle in a
  powered MPLM may generate data
• During payload transport operations the shuttle
  will send an Operational Downlink (OD) data
  stream to the ground. Part of this stream is the
  Payload Data Interleaver (PDI) which may contain
  data for ISS payloads that are on the shuttle
  either coming or going from the ISS.
• Ku-Band Data is sent from the ISS to TDRSS to
  White Sands to DomSat to the control centers
• The data structure for ISS data will conform to
  the Consultative Committee for Space Data Systems
  (CCSDS) recommendation for Advanced Orbiting
  Systems
• Shuttle data is sent from the shuttle to TDRSS to
  White Sands to JSC to MSFC. It is not in CCSDS
  format

17
Space-to-Ground

• Data can come to the ground via S-Band or
  Ku-Band.
• These are physical mechanisms to transport the
  data.
• Ku-Band was selected because there was very
  little traffic in the electromagnetic spectrum at
  that frequency and communication rates (bit
  rates) could be higher because of the wider
  possible bandwidth.
  Ku-Band operates at
  13,775 MHz and 15,003.4 MHz.
• S-Band data has a much lower frequency and
  bandwidth.
  S-Band operates at 2065.0 and 2085.6875 MHz.

18
Space-to-Ground (cont)

• S-Band
• S-band data is relayed to/from ISS via TDRSS
• S-Band carries primarily core systems data down
  and commands up
• Forward Link to ISS -- from the ground to space
• can carry CCSDS packets and up to 2 audio
  channels
• normal mode has rates up to 72 kbps (data
  audio)
• low rate mode has rates up to 6 kbps (data only)
• commands are sent via S-band forward link
• Return Link to ISS -- from space to ground
• can carry CCSDS packets and up to 2 channels of
  audio
• normal mode has rates up to 192 kbps (data
  audio)
• low rate mode has rates up to 12 kbps (data only)
• Shuttle S-Band Return Link
• relayed from the shuttle to TDRSS to the ground
• contains OD data which contains PDI data from
  payloads
• 64 kbps Low Rate Data 96 low rate with one
  voice channel
• 128 kbps High Rate Data 192 kbps high rate w/2
  voice chls

19
Space-to-Ground (cont)

• Ku-Band return link data
• Ku-Band data is sent from the ISS Space-to-Ground
  Subsystem (SGS) to the ground via TDRSS
• Ku-band primarily carries
• High Rate Payload Data
• Digital Video
• Core Playback Data
• Ku-Band can carry CCSDS packets or bitstream data
  note bitstream
  data can be packetized for downlink
• The ground system is currently set to support a
  50 Mbps link
• There will be 8 return link payload channels,
  which are configured by POIF cadre (the Data
  Management Coordinator (DMC))
• one channel is typically assigned for use by the
  Payload MDM
• one channel is typically assigned for use by the
  PEHG
• one channel is typically assigned for ZOE or COR
  dumps

20
Space-to-Ground (cont)

• Ku-Band Return Link Data (cont)
• the USOS to IGSS Ku-Band Telemetry Formats ICD
  (SSP 41158) describes the data structures used
  for Ku-Band data transfer
• All ISS Ku-Band packets generated by the USOS
  elements will contain a CCSDS primary header.
  The primary header is needed for the basic
  identification and routing of the packet. APIDs
  for payloads are placed in the primary header.
• All USOS-generated Ku-Band packets which are to
  be processed by the HOSC shall contain a CCSDS
  Secondary packet header which is necessary for
  any level of IGSS ground processing.
• Video is converted from analog to digital
  on-board and sent down as a part of the Ku-Band
  data

21
Space to Ground (cont)

• Tracking and Data Relay Satellite System
• TDRSS
• The main task of the TDRSS is to provide
  communication and tracking services for low-earth
  orbit spacecraft.
• TDRSS consists of satellites in geosynchronous
  orbits and a dedicated ground station.
• The ground station is at the White Sands Complex
  (WSC) in New Mexico.
• TDRSS can provide coverage over about 85 of a
  spacecraft's orbit.
• The TDRS operates as a repeater, relaying signals
  to and from the ground station. No data
  processing is done onboard the TDRS.
• The Network Control Center (NCC) at Goddard Space
  Flight Center manages and controls the Space
  Network and TDRSS.
• During/prior to real-time operations, conflicts
  of TDRSS satellite use that arise between ISS and
  other spacecraft are resolved between the Network
  Control Center, the SSCC, and the POIC.
• The data flow plan reflects which satellite is
  scheduled and for how long. The WISARD develops
  the data flow plan (DFP).
• The DMC will coordinate with the Network Control
  Center and SSCC on real-time changes. The BANDIT
  will help make changes to the DFP.

22
Space-to-Ground (cont)

• White Sands Complex (WSC)
• The ground station that monitors and controls the
  satellites is the White Sands Ground Terminal in
  New Mexico.
• White Sands forwards the data to NASA Integrated
  Services Network (NISN) to distribute to the NASA
  centers.
• Currently they have choosen DomSat for Ku-Band
• Currently they use IONet for S-Band
• White Sands has a Line Outage Recorder (LOR) that
  records data in case a connection between White
  Sands and one of the NASA centers fails. If that
  happens, WSC can play back the data when the
  connection is restored.

23
United States Ground System (USGS)

• The mission of the USGS is to support and
  maintain the on-orbit Space Station from the
  ground by providing the resources needed to
  successfully perform its mission It is
  comprised of end items used to support this
  mission. These end items provide the capability
  to monitor and control the on-orbit space
  station, perform payload operations, perform
  planning, and provide simulation of the on-orbit
  space station for verification and training.
• Geographically the USGS is split between
• Johnson Space Center (JSC) in Houston, Texas
• Marshall Space Flight Center (MSFC) in
  Huntsville, Alabama
• Goddard Space Flight Center (GSFC) in Greenbelt,
  Maryland
• White Sands Complex (WSC) in Las Cruces, New
  Mexico and
• Kennedy Space Center (KSC) in Cape Canaveral,
  Florida.
• The networks that are part of the US Ground
  System are provided by the NASA
  Integrated Service Network (NISN).
• The mission of the NISN is to provide
  cost-effective wide area network
  telecommunications services for transmission of
  data, video and voice for all NASA Enterprises,
  Programs and Centers, utilizing commercial
  capability wherever possible.

24
United States Ground Systems (USGS)

• figure F-1 from SSP 54500

25
US Ground System (cont)

• Who/what makes it up the US Ground System
• Facilities Used for Realtime Operations
• SSCC - Space Station Control Center -- at JSC
• The SSCC will be used for managing the execution
  of core systems operations.
• The SSCC is part of the Mission Control Center -
  Houston (MCC-H)
• The SSCC Ground Controller (GC) works closely
  with GSFC NCC for coordination of Ground Network
  and Space Network Resources
• POIC - Payload Operations Integration Center --
  at MSFC
• The POIC will be used for managing the execution
  of on-orbit payload and payload support systems
• The POIC has the overall responsibility for
  payload ground data distribution.
• USOC - United States Operations Center -- at
  MSFC
• The USOC will be used to provide a facility where
  users can be trained and where users can control
  and monitor the operations of their on-board
  payloads.
• It is located in the HOSC.

26
US Ground System (cont)

• Systems Used for Realtime Operations (cont)
• IPS - Integrated Planning System -- at JSC
• Used for comprehensive planning and analysis.
• PPS - Payload Planning System -- at MSFC
• Used for payload planning and scheduling
• PDSS - Payload Data Services System -- at MSFC
• PDSS will be used to receive, process, store, and
  distribute Space Station payload data to the
  POIC, the USOC, the International Partners, and
  user operations facilities.
• All data is distributed with the EHS protocol
  headers.

27
US Ground Systems (cont)

• Systems/Facilities used for training
• SSTF - Space Station Training Facility -- at JSC
• Used for training ISS crews and controllers on
  ISS operations and for verification of operations
  procedures
• MRMDF - Multiple Remote Manipulator Development
  Facility -- at JSC
• Used for training and procedure development for
  the space station robotics operations
• SSMTF - Space Station Mock-up Training Facility
  -- at JSC
• to develop and validate flight crew interfaces
  and designs, and train flight crew members,
  controllers and instructors on ISS operations,
  crew systems, maintenance and crew health care.
• SES - System Engineering Simulator -- at JSC
• Used to provide and maintain real-time dynamic
  models for crew-in-the-loop training and shuttle
  robotics, rendezvous/proximity, and docking
  operations.
• NBL - Neutral Buoyancy Lab -- at JSC
• Used to simulate null gravity for training crews
  on EVAs.
• SMTF SSI - Shuttle Mission Training Facility
  Space Station Integration -- at JSC
• Used for shuttle based ISS assembly training
• PTT - Part Task Trainer -- at JSC
• a training device which provides standalone
  single system training for crew and ground
  controllers.
• PTC - Payload Training Complex -- at JSC
• Used to train ISS crews and Ground Support
  Personnel on the operation of US controlled
  payloads
• RAPS - Remote Area Payload Support -- at MSFC
• allows training personnel to support the SSTF
  payload crew operations training, it also links
  to PTC

28
US Ground Systems (cont)

• Systems/Facilities used for Integration,
  Verification, etc
• MBF - Mission Build Facility -- at JSC
• The central repository for ISS core systems
  flight software and flight systems data.
• PDL - Payload Data Library -- at MSFC
• on online system used for collecting user
  requirements
• PICF - Payload Integration and Checkout Facility
  -- at KSC
• is used for processing of US payloads including
  physical integration and interface checkout
• PSIV - Payload Software Integration and
  Verification -- at MSFC
• Used to integrate and verify US. controlled
  payload software and make sure the payload
  interfaces are compatible with the ISS.
• SSPF - Space Station Processing Facility -- at
  KSC
• provides for the integration of hardware for the
  ISS prior to launch
• SVF - Software Verification Facility -- at JSC
• provides a facility for verifying ISS flight
  software

29
US Ground Systems (cont)

• see the
• International Ground System Specification
  Document
  (SSP 54500) Appendix F
  
  
• and the
  
  
• International Ground System Integration,
  Verification Test Management Plan
• (SSP 54501)
  
  
• for detailed information on US Ground System
  facilities.

30
US Ground Systems (cont)

• Uplink and Downlink Data is configured and routed
  on the ground
• S-band
• SSCC schedules and manages S-band utilization.
• The SSCC and POIC receive the ISS S-Band data and
  will configure their respective ground systems to
  capture and process ISS S-Band data based on the
  S-Band data flow scheduling performed by the SSCC
  plus any real-time changes.
• The POIC documents the scheduling via the data
  flow plan.
• S-band data goes out from White Sands via IONET
• ISS Command and Control, core system telemetry,
  and some payload-related telemetry will be sent
  down on the S-Band system.
• ISS Commands are sent through the SSCC and then
  up via S-Band
• Air-to-Ground Voice is sent and received via
  S-Band
• Shuttle S-band data is sent from WSC to JSC who
  then routes it to MSFC via NISN.

31
US Ground Systems (cont)

• Downlink Data is routed and configured on the
  ground
• Ku-Band
• Ku-Band utilization management is the
  responsibility of the POIC.
• The SSCC and POIC receive the Ku-Band data from
  the WSC and will configure their respective
  ground systems to capture and process Ku-Band
  data based on the data flow scheduling performed
  by the POIC plus any real-time changes.
• The data flow schedule is done via the Data Flow
  Plan (DFP) which is generated during Short Term
  Planning by the WISARD position at the POIC.
• The Ku-Band digital video data is processed by
  the MCC-H, which strips out video channels,
  performs digital-to-analog conversion, and
  provides the standard NTSC video to the
  communications networks for distribution.
  Note the POIC coordinates with SSCC, IPs,
  and users on the distribution of payload related
  video.
• The Ku-Band link is used for downlink of payload
  data, video, and core systems recorder dump data.
  

32
US Ground Systems (cont)

• Ground to Ground
• All commands to ISS onboard destinations are sent
  to JSC to be uplinked.
• All command responses that indicate whether a
  command was or was not successfully received and
  executed by the destination processor are first
  received and processed by the JSC SSCC prior to
  distribution to the originating source.
• planning procedure data is exchanged between
  SSCC, POIC, and users
• voice -- coordination audio is used between sites
  on the ground

33
International Ground Systems

• The US Ground Systems sends and receives
  information from the International Partners.
• The International Ground System provides the
  routing and communications of data, video, and
  audio both to and from the On-Orbit Segment and
  the end user. The IGS also performs analysis,
  training, planning, procedures development, and
  reconfiguration functions in support of the
  International Space Station Program.
• International Ground System is made up of
• CSA Ground System (Canada)
• ESA Ground System (Europe)
• ASI Ground System (Italy)
• NASDA Ground System (Japan)
• RSA Ground System (Russia)
• US Ground System (USA)
• NASA provided communication

34
International Ground System (cont)

• Types of data that will be distributed
• ISS Systems Telemetry
• ISS Systems Commands
• A/G Audio
• A/G Video
• Payload Telemetry
• Payload Commands
• Systems and Payload MDM software loads
• Planning and Procedures Data
• note the Partners are responsible for data
  distribution within their own ground network
  systems

35
International Ground Systems (cont)

• Command and telemetry data for ISS core systems
  will be a shared resource provided to the
  separate IPs. Except for RSA ( and possibly
  NASDA), each IP will control and command their
  respective modules via the data uplink/downlink
  provided by NASA.
• The POIC is responsible for scheduling, managing,
  and controlling the Space Station onboard payload
  data and video systems. The POIC has the overall
  responsibility for payload ground data
  distribution and will coordinate distribution
  with the IPs.
• Interface Control Documents (ICD) give details of
  the capabilities and interfaces between the
  various centers.
• A brief summary of the International Partner
  interfaces follows . . .

36
International Ground Systems (cont)

• International Partners
• CSA
• CSA will operate from the SOSC (Space Operational
  Support Center)
• SOSC capabilities include receiving data and
  video and exchanging planning products
• ESA
• The ESA Ground System functions are distributed
  to facilities throughout Europe. They are
  connected to each other and with the external
  facilities by the Interconnection Ground
  Subnetwork and are comprised of the Automated
  Transfer Vehicle Control Centre (ATV CC), the
  Attached Pressurized Module Control Centre (APM
  CC), the interconnection Ground Subnetwork
  Control Centre, industrial sites, and interfaces
  to remote user sites.
• The ESA Ground System capabilities include the
  generation of commands, the reception of data,
  audio, and video the exchange of planning and
  integration products and the simulation of
  hardware and software functions.

37
International Ground Systems (cont)

• ASI
• The Mini-Pressurized Logistics Module (MPLM)
  Ground System is a part of the MPLM Segment
  developed by Agenzia Spaziale Italiana (ASI).
  MPLM Ground System capabilities include receiving
  data, training, and exchanging planning products.
• NASDA
• NASDA will operate from the SSIPC (Space Station
  Integration and Promotion Center) in Tsukuba,
  Japan.
• The SSPIC is comprised of the computers,
  simulators, and other equipment to perform
  Japanese Experiment Module (JEM) engineering
  assessments, payload operations and user support,
  Japanese payload integration, logistics
  operations, and crew training for JEM systems and
  Japanese payload operations.
• The SSPIC will receive downlink payload data and
  payload planning data and procedures from the
  POIC.
• RSA
• The Russian Ground System consists of Mission
  Control Center - Moscow which is responsible for
  the control of the Russian segment hardware.
• It is a backup location for some SSCC functions.
• Voice and payload planning data procedures will
  be exchanged with the POIC.

38
POIC/Overview

• General POIC Information
• The POIC is located within the HOSC -- Building
  4663 at MSFC
• The POIC is an ISS facility that provides the
  capabilities required by the Cadre to manage and
  integrate payload operations.
• The POIC provides the capabilities to coordinate
  with distributed International Partner Payload
  Control Centers (PCC), Telescience Support
  Centers (TSC), and unique remote payload
  facilities. See the POIC Capabilities Document
  (SSP 50304) for more information.
• The POIC provides interfaces to the IPs, TSCs,
  and remote users to exchange voice, video, and
  data as required. See the POIC to Generic User
  Interface Definition Document (SSP 50305) for
  detailed information.
• The POIC also contains the United States
  Operations Center (USOC) that provides the
  capabilities required to support individual users
  or user teams so that they can operate and
  control their ISS payloads and experiments.

39
POIC/Overview

40
POIC/Overview

• Systems that make up the POIC
• EMCS -- The Enhanced Mission Communications
  System simultaneously receives multiple data
  streams, at various rates, and in ISS and non-ISS
  formats from the NASA Integrated Services Network
  (NISN). It also has functions to provide for the
  reception, processing, and distribution of
  digital voice and analog video, and distribution
  of data streams to MSFC core systems, remote user
  facilities, and to IP gateways.
• PDSS -- The Payload Data Services System
  acquires, distributes, and stores ISS data for
  the EHS, International Partners, TSCs, and other
  remote payload facilities.
• EHS -- The Enhanced HOSC System performs command
  processing, realtime and near realtime telemetry
  processing for prelaunch integration/checkout,
  simulations and training, and flight operations.
• PPS -- The Payload Planning System provides a
  unique POIC subsystem with software capabilities
  to automate payload planning and scheduling
  activities.

41
POIC

42
POIC/EMCS

43
POIC/EMCS

• EMCS - Enhanced HOSC Communications System
• Receives multiple data streams
• Distributes data, voice, and video
• It has 6 main subsystems
• Enhanced Video Distribution (EViDS),
• Enhanced Voice Dist. Sys (EVoDS),
• Enhanced Data System (EDS),
• Data Distribution System (DDS),
• Timing Distribution System (TDS),
• Communications System Monitoring and Control
  (CSMAC).

44
POIC

• Types of Data Received at the POIC
• Core Systems Data -- from ISS via S-Band
  telemetry
• Payload Data -- from ISS via Ku-Band telemetry
• Voice -- Air to Ground and coordination audio
  for ground-to-ground
• Video -- downlink from ISS via JSC and uplink
  video from users
• Planning and procedures data -- integrated info
  from JSC payload planning info from users
• Payload commands -- from IPs, TSCs, remote users
• Payload s/w loads from ESA
• Command responses -- from JSC
• TDRSS attitude and orbit data from JSC -- comes
  in through Consolidated Planning System (CPS)
• Files from users -- via PIMS
• e-mail
• web information
• Shuttle Data -- payload information received
  from shuttle OD/PDI during transport -- received
  from JSC
• Database information -- from PDL, PSIV, and MBF
• User Performance Data from White Sands

45
POIC

• Types of Data Sent from the HOSC
• ISS Payload downlink data -- PDSS sends out EHS
  encapsulated packet data to the local users,
  remote users, TSCs, and to the International
  Partner gateways
• Ground Ancillary -- sent from EHS to PDSS for
  distribution to users
• The EHS sends directly to remote users, TSCs, and
  IPs
• Ground Support Equipment (GSE) packets Custom
  Data Packets (CDP) which can contain parameters
  from the telemetry database including shuttle
  data or ground ancillary data.
• command responses (EHS Bld 5)
• status messages (EHS Bld 5)
• The EHS has X-windows and web interfaces for
  users to receive certain information
• Payload Planning data and procedures information
  is sent to users and JSC
• The POIC can distribute POIC generated video (JSC
  distributes downlink video)
• The POIC sends the following to JSC/SSCC
• payload commands
• file uplinks
• software/data loads
• payload planning data
• Voice -- A/G audio and coordination audio
• e-mail

46
POIC/PDSS

47
POIC/PDSS/Routing

• Routing the ISS Data -- PDSS
• PDSS
• Data is ingested into the PDSS system through the
  PDSS input switch and processed through a series
  of processors and switches until the data reaches
  the PDSS Network Servers. Once the data reaches
  the Network Servers, the data is placed into
  UDP/IP packets for distribution.
• PDSS has several subsystems including
• Data Acquisition Extraction (DAE) which is a
  type of front end processor
• Data Distribution (DD)
• Data Storage Retrieval (not available until EHS
  Bld 5 timeframe)
• PDSS can simultaneously receive Ku-Band data and
  S-Band data
• Two data types are processed during real-time
• CCSDS Packets (Consultative Committee on Space
  Data Systems)
• BPDU (Bitstream Protocol Data Unit)
• Data is distributed using User Datagram Protocol
  (UDP) protocol see
  Protocol section for more info
• The PDSS distributes data from onboard payloads
  in real-time by adding a primary EHS header and
  PDSS payload CCSDS or BPDU packet secondary
  header with no modification to the entire onboard
  formatted CCSDS packet.

48
POIC/PDSS/Routing

• Routing the ISS Data -- PDSS (cont)
• The PDSS receives the ISS Ku-Band data stream
  from the EMCS Enhanced Data System (EDS) at 50
  Mbps
• The PDSS receives S-Band data at 192 kbps data
  stream from the EMCS Data Distribution System
  (DDS) and IRIG -B time signal from the EMCS
  Timing Distribution System (TDS).
• ISS data is in CCSDS recommended format.
• All input data streams are first captured and
  processed by the PDSS Data Acquisition and
  Extraction (DAE) element.
• The output from the DAE element is always EHS
  encapsulated BPDUs or EHS encapsulated CCSDS data
  packets.
• The PDSS uses APIDs to determine routing. The
  APID is found in the CCSDS packet header.
• Distribution of the EHS encapsulated data can be
  to either single or multiple destinations based
  on APID and Data Mode.
• Configuration, control, and status of the PDSS
  hardware and software components is established
  and maintained by an Integrated Support Team
  (IST) console position.

49
POIC/Routing

• Routing Shuttle Data
• Comes from JSC via NISN
• Comes into the EMCS Data Distribution System
  which sends it to the HOSC Project/Telemetry
  Server (part of EHS).
• The Front End Processor / OD stream processor on
  the Project Server performs EHS encapsulation of
  PDI data and routing to EHS workstations.
• Remote users can receive shuttle data via GSE
  Packets or Custom Data Packets

50
POIC/EHS

51
POIC/EHS

• The Enhanced HOSC System processes data that is
  designated for processing.
• See the POIC Capabilities Document (SSP 50304)for
  detailed information on EHS.
• EHS uses a distributed architecture where the
  workstations provide the bulk of the processing
  capability to the individual users.
• EHS is made up of
• Workstations
• Telemetry Server
• Command Server
• Database Server
• Payload Information Management System Sever
  (PIMS)
• Web Server
• EHS Remote Interface System Server (ERIS)
• System Monitor and Control Server (SMAC)
• Non-operationsal Development Environment (NDE)
• Firewall
• Local Area Network
• Time Distribution System
• Print Servers

52
POIC/ Data Paths Overview

(EDS)
EMCS
53
POIC/Protocols

• Transmission Methods and Protocols
• Protocol Sets of rules agreements describe
  how elements interact
• Transport Protocols -- lower level standardized
  network protocols
• TCP -- Transmission Control Protocol
• requires handshaking on the part of the
  computers
• used for distribution of Custom Data Packets by
  the EHS system
• used for distribution of data to the G2
  application
• UDP -- User Datagram Protocol
• a connection-less oriented protocol that does not
  guarantee delivery of data. (i.e. no handshaking
  by the computers)
• Generally used as a mechanism for application
  programs to send datagrams to other application
  programs.
• used for distribution of PDSS telemetry data and
  GSE packets

54
POIC/Protocols

• Standard Application Protocols -- a layer above
  the standardized transport protocols
• FTP - File Transport Protocol
• a protocol to deliver file-structured information
  from one host to another
• used for moving files e.g. files to PIMS?
• Telnet -- Terminal to Host Network Protocol
• used for virtual terminals
• used for X-windows at the POIC
• SMTP/Mail -- Simple Mail Transfer Protocol
• a platform independent transport protocol which
  uses TCP/IP to transfer mail between various
  platforms
• used for e-mail access to/from the POIC
• HTTP-- HyperText Transfer Protocol
• used for web interfaces such as iURC and some EHS
  services
• SSH-- Secure Shell
• a secure packet-based binary protocol that works
  on top of any transport protocol that will pass a
  stream of binary data
• used for X-windows
• SSL3 -- Secure Socket Layer
• has encryption and handshake protocols
• used in the access of POIC web capabilities

55
POIC/Telemetry Command Protocols

• Telemetry and Command Protocols
• Used by ISS
• Commands
• all commands adhere to CCSDS packet format where
  the header information determines the routing to
  the destination.
• Telemetry Protocols
• Overall EHS protocol
• uses UDP for all distribution - except Custom
  Data Packets.
• It has a primary header a secondary header
  followed by the data in a CCSDS packet
• CCSDS packet
• has a primary header and optional secondary
  header followed by data
• Bitstream

56
POIC/Telemetry Protocols

• Specialized Telemetry Protocols
• PDSS Payload CCSDS Packets
• contains payload data downlinked from the ISS.
• POIC/PDSS distributes data real-time by adding a
  primary EHS header and a secondary header with no
  modification to the entire on-board formatted
  CCSDS packet
• PDSS Payload BPDU Packets
• contains payload bitstream data downlinked from
  the ISS
• POIC/PDSS distributes data real-time by adding a
  primary EHS header and a secondary header with no
  modification to the entire on-board formatted
  BPDU packet.
• GSE Packets
• contain data extracted from any of the data that
  is in the POIC telemetry database. The remote
  user creates the GSE packet through a telemetry
  database application.
• has an EHS header and CCSDS headers
• Custom Data Packets
• contains data extracted from any data that is
  defined in the POIC telemetry database.
• It is distributed via TCP/IP. The user
  identifies the packet contents through a
  programmatic interface
• It has an EHS Primary and secondary header and a
  CCSDS Packet

57
POIC/Interfaces

• See the POIC to Generic User Interface
  Definition Document (SSP 50305) for detailed
  information on interfaces and protocols.
• NOTE The POIC does not interface directly to
  remote user facilities or other NASA centers.
  The most common carrier is NISN -- which
  coordinates with commercial carries for
  communications transport.

58
POIC/Interfaces

• Interfaces
• POIC Interfaces to remote facilities (see PCD
  PGUIDD for more information)
• web -- many POIC services can be accessed via
  the world wide web.
  e.g. iURC, PG, PIMS, some EHS services
• X-windows-- a way for users outside the HOSC to
  log directly into an EHS workstation that is
  located within the HOSC
• Real-time Telemetry Interface -- data is sent
  from PDSS in CCSDS or BPDU packets using the UDP
  protocol
• Real-time Extracted Telemetry Interface -- EHS
  encapsulated data from the database and sends it
  out. Can use UDP or TCP protocols.
• Programmatic Interface -- a bi-directional
  interface between computers -- used for Custom
  Data Packets
• Command Interface -- allows users to update
  modifiable commands and uplink commands
• File Transfer -- used for PIMS, etc.
• video -- POIC generated video (downlink video is
  sent to users from JSC)
• voice -- can send/receive ground voice can send
  A/G voice
• e-mail -- can send and receive
• Note These interfaces are available to the
  non-TSC US remote sites. The users request them
  in the Ground Data Services section of PDL
• Note Users who bring GSE into the USOC are
  considered remote users.

59
POIC/Interfaces

• Interfaces to TSCs
• Telescience Support Centers (TSCs) are NASA
  funded facilities which provide the capability to
  plan and operate payloads and experiments from a
  central location. They provide floor space,
  workstations, as well as voice, video, and data
  interfaces.
• For ISS payloads, the TSCs use interfaces
  provided by the Huntsville Operations Support
  Center at MSFC to conduct space operations for
  experiment teams.
• TSCs are located at
• Johnson Space Center (JSC),
• Ames Research Center (ARC),
• Glenn Research Center (GRC), and
• Marshall Space Flight Center (MSFC) at the
  Microgravity Development Lab (MDL).
• The TSCs will generally have all the interfaces
  listed on the previous page.
• Each TSC has an Interface Control Document (ICD)
  with the HOSC that lists all the interfaces that
  will be supported between that center and the
  HOSC.

60
POIC/Interfaces

• Interfaces to IPs
• POIC Interfaces to IP Gateways
• interface for PDSS originated data
• FTP interface to PDSS Retrieval Processor/Storage
  Manager (this will be available later in the
  program . . .)
• Web Interface to POIC information systems such as
  PPS, PIMS, EHS applications -- web
• Voice
• Video (to those who require it)
• e-mail
• Generally these interfaces use the same protocols
  that were discussed previously.
• Interfaces are called for each International
  Partner in an Interface Control Document (ICD).

61
POIC/Interfaces to IPs

• Network Services (Protocols) used for Interfaces
  to IP Gateways
• FTP
• file transfer, e.g. data files for PIMS
• TCP/IP
• custom data packets from EHS e-mail uses it
• UDP/IP
• packets from PDSS
• X-windows over secure shell connection (SSH)
• view schedule of files being uplinked, view OSTP
• Simple Mail Transfer Protocol (SMTP)
• e-mail
• Hypertext Transfer Protocol over secure socket
  layers (https)
• web interfaces include, PPS systems PG URC,
  certain EHS applications such as viewing
  telemetry database info, PIMS
• additional services can be enabled with
  justification authorization

62
Summary

• You should have learned that data is generated
  on-board and sent to the ground via TDRSS (on
  either S-Band or Ku-Band)
• It can be distributed around the US to various
  users and around the world to IPs.
• The US Ground System has two main real-time
  facilities -- SSCC and POIC.
• the SSCC controls core systems
• the POIC controls payloads
• At the POIC, the EMCS, PDSS and EHS play major
  roles in collecting, processing and distributing
  data.
• There are a number of different transmission
  methods and protocols that are used to send and
  receive data.

63
Where to get more information

• Other training sessions
• PDSS Orientation
• Electronic sources
• NISN homepage http//www.nisn.nasa.gov
• Red Dwarf https//red-dwarf.msfc.nasa.gov

64
Reference Documentation

• SSP 41154 USOS to USGS Command and Telemetry ICD
• SSP 41158 USOS to USGS High Rate Data (Ku-Band)
  ICD
• SSP 42018 USOS to Ground through TDRSS ICD
• SSP 45001 SSCC to HOSC ICD
• SSP 45026 HOSC to ESA ICD
• SSP 45025 HOSC to NASDA ICD
• SSP 50364 HOSC to JSC TSC ICD
• SSP 50366 HOSC to LeRC TSC ICD
• SSP 50367 HOSC to ARC TSC ICD
• SSP 50368 HOSC to RSA ICD
• SSP 50304 POIC Capabilities Document (PCD)
• SSP 50305 POIC to Generic User IDD (PGUIDD)
• SSP 54001 NPRD/PRD - Space Station Program
  Support Requirements, System
  Network Program Requirements Document
• SSP 54500 International Ground Segment
  Specification
• SSP 54501 International Ground System
  Integration, Verification Test Management Plan