Presentation is loading. Please wait.

Presentation is loading. Please wait.

POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 1 Onboard Payload Data Flow Capabilities Gary Knickerbocker POIF.

Similar presentations


Presentation on theme: "POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 1 Onboard Payload Data Flow Capabilities Gary Knickerbocker POIF."— Presentation transcript:

1 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 1 Onboard Payload Data Flow Capabilities Gary Knickerbocker POIF Data Management Phone: (256)961-1513 E-mail: gary.knickerbocker@pobox.tbe.com

2 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 2 Agenda Overview of the Onboard Data Systems Architecture High, Medium and Low Rate Data Link Capabilities Description Video Capabilities Uplink/Downlink Capabilities

3 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 3 Onboard Data Systems Overview The International Space Station (ISS) onboard data systems consist of the Command and Data Handling System (C&DH) and the Communications and Tracking System (C&T) C&DH provides: –Command/control of the International Space Station (ISS) Subsystems and Payloads –Distribution of Commands and Data to Subsystems/Payloads –Retrieval of status from Subsystems and Payloads –Data storage and retrieval services –Portable Computer System (PCS) interfaces for ISS control/monitoring by the Crew –Data distribution resources for High, Medium and Low Rate data transfers

4 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 4 Onboard Data Systems Overview C&T provides: –S-band subsystem for command, data, and audio uplink and status data/audio downlink –Ku-band subsystem for uplink of manual procedures, compressed video, and crew e-mail services and downlink of crew e-mail, Payload Support System status, ancillary, video, and payload data –Video subsystem for transfer of video from sources to destinations onboard the ISS –Audio subsystem for transfer of audio from sources to destinations onboard the ISS

5 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 5 Onboard C&DH Architecture Payload 1553B Buses Ethernet NASA Element To S-Band System Command and Control 1553B Buses Ethernet Attached Payloads Attached Pressurized Module (APM) COR Japanese Experiment Module (JEM) US ISPRs S-Band C&DH Subsystems PEHG 2 ULC P3 1-2 APP S3 1-4 Portable Computer System Portable Computer System APS (2) HRDL MRDL LRDL/1553B Bus LEGEND To Ku-Band Telemetry System HRFM ULC - Unpressurized Logistics Carrier APP - Attached Payload Port C&C MDM - Command and Control Multiplexer/Demultiplexer PL MDM - Payload Multiplexer/Demultiplexer ISPR - International Standard Payload Rack APS - Automated Payload Switch PEHG - Payload Ethernet Hub Gateway COR - Communications Outage Recorder HRFM - High Rate Frame Multiplexer HRM - High Rate Modem Legend : HRM Centrifuge Accommodations Module (CAM) PL MDM C&C MDM PEHG 1

6 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 6 Payload C&DH Data Transfer Overview C&DH provides 3 separate data distribution mechanisms for Payload data transfer –These are referred to as the Low, Medium and High Rate Data Links –Each interface provides a mechanism for routing data between Payloads or from Payloads to the Ku-band Subsystem for downlinking The Payload MDM provides the Multiplexing function for Payload Local Bus Low Rate Data Sources in addition to collection and downlinking of Payload Health and Status data, Broadcast Ancillary Data (BAD), and Payload Ancillary Data The Payload Ethernet Hub/Gateways (PEHG) provide the Multiplexing function for IEEE 802.3 Medium Rate Data Sources The High Rate Frame Multiplexer (HRFM) provides the Multiplexing function for High Rate Data Link (HRDL) Sources

7 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 7 C&DH Payload Data Transfer Capabilities Low Rate Data Capabilities –Each MIL-STD-1553B Payload Local Bus has allocation for 100 Kbps of Low Rate Telemetry (LRT) from the Payload Locations attached to that bus Bandwidth is allocated dynamically upon request from a Payload to the Payload MDM within its Health and Status response –Bandwidth is allocated in 10 Kbit increments at a pre-defined collection rate of 1 Hz or 0.1 Hz Bandwidth is allocated on a first come first serve basis Data must be transferred in CCSDS Packets ranging in size from 100 bytes up to 1280 bytes (10.24 Kbits) Each Packet occupies 10.24 Kbits worth of bandwidth over the bus regardless of its actual size –Only one Packet can be transferred over the bus for each LRT Transaction POIC currently has no capability to monitor the allocation of LRT –This capability may be added by Assembly Flight 8A

8 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 8 Payload Local Bus Connectivity MDM PL-1 MDM PL-2 LB PL-1 APP-S3-1 APP-S3-2 APP-S3-3 APP-S3-4 USL ISPR-LAP1 USL PL PCR-1 ULC-P3-1 ULC-P3-2 USL ISPR LAO1 USL ISPR LAP2 USL PL PCR-2 USL ISPR-LAO4 USL ISPR-LAO5 USL ISPR-LAP4 CAM ISPR-2 CAM ISPR-3 CAM PL PCR-2 LB PL-2 LB PL-3 APS-2 PEHG-2 USL ISPR-LAO2 USL ISPR-LAO3 LB PL-JEM LB PL-APM LB PL-4 USL ISPR-LAS3 USL ISPR-LAS4 USL ISPR-LAD3 CAM Centrifuge CAM ISPR-1 CAM PL PCR-1 APS-1 PEHG-1 USL ISPR-LAS1 USL ISPR-LAS2 APM ISPR A1 APM ISPR A2 APM ISPR A3 APM ISPR A4 APM ISPR O1 APM PL PCR-1 APM ISPR F1 APM ISPR F2 APM ISPR F3 APM ISPR F4 APM ISPR O2 APM PL PCR-1 JEM ISPR F6 JEM ISPR A1 JEM ISPR A2 JEM ISPR A3 JEM ISPR A4 JEM PL PCR JEM ISPR F1 JEM ISPR F2 JEM ISPR F3 JEM ISPR F5 JEM ISPR A5 APM - Attached Pressurized Moduel APP - Attached Payload Port APS - Automated Payload Switch CAM - Centrifuge Accommodations Module ISPR - International Standard Payload Rack JEM - Japanese Experiment Module LAD - Lab Deck (Floor) LAO - Lab Overhead (Ceiling) LAP - Lab Port LAS - Lab Starboard LB - Local Bus MDM - Multiplexer/Demultiplexer P - Port PCR - Portable Computer Receptacle PEHG - Payload Ethernet Hub/Gateway PL - Payload S - Starboard ULC - Unpressurized Logistics Carrier USL - US Lab

9 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 9 C&DH Payload Data Transfer Capabilities Low Rate Data Capabilities –Low Rate Telemetry Capabilities As a last resort, Payloads which exceed their planned LRT allocations may be deactivated if they can’t throttle their requests for LRT when their operations interfere with other scheduled Payload operations on that particular bus –The Payload MDM collects up to 20 Kbits of Payload Health and Status (H&S) data from each Payload Location at a pre-defined rate of 1 Hz or 0.1 Hz Should a Payload need to provide data to a Portable Computer System (PCS) for operation of the Payload, this data must be included in the Payload H&S packet –H&S data is the only Payload data pulled into the Payload MDM Current Value Table (CVT) –The Payload MDM can support one file transfer to and from a Payload Location on each of its Payload Local Buses Files can be transferred at a rate of 46.08 Kbps Operations does not plan to use this service to downlink Payload Files

10 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 10 C&DH Payload Data Transfer Capabilities Medium Rate Data Capabilities –The Payload Ethernet Hub/Gateway (PEHG) provides the centralize repeater function in order to support IEEE 802.3 communications between Payloads and a mechanism to transfer data to the ground when its Gateway is activated An IEEE 802.3 LAN can transfer data at a DATA SIGNALING RATE of 10 Mbps –The actual throughput of an IEEE 802.3 LAN depends upon the characteristics of the data transfers and the number of active stations (data sources) on the LAN –As the number of active stations (and data transfers) on the LAN increase, the likelihood of collisions increase »Collisions take away useable bandwidth from the LAN »Collisions are the flow control mechanism over IEEE 802.3 LANs –Operations is planning to a total throughput limitation of 7 Mbps on each LAN »Includes Payload to Payload Traffic and Payload to Gateway Traffic

11 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 11 C&DH Payload Data Transfer Capabilities Medium Rate Data Capabilities –There are 2 Payload LANs onboard, LAN-1 and LAN-2 LAN-1 is connected to all of the US Lab ISPR Locations and the Payload Locations in the Centrifuge Accommodations Module (CAM) LAN-2 is connected to all of the US Lab ISPR Locations, ISPRs and Attached Payloads in the Japanese Experiment Module (JEM) and JEM Exposed Facility, and ISPRs and Attached Payloads on the European Space Agency (ESA) Attached Pressurized Module (APM) and the APM Exposed Facility While the two LANs have a physical connection, operations does not plan to enable it –This would combine the collision domains of LAN-1 and LAN-2 meaning this would combine the two LANs into one LAN –There is no way for a data source on one LAN to communicate with a data source on another LAN at this time –Configuration of the LANs will be based on Payload complement requirements

12 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 12 Payload LAN Layout PEHG-1PEHG-2 USL ISPRs & PCRs PEHG-J JEM ISPRs & EF APM USL JEM PEHG-A APM ISPRs & EF CAM PEHG-C CAM Payloads IEEE 802.3 Connection LAN-1 LAN-2

13 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 13 C&DH Payload Data Transfer Capabilities Medium Rate Data Capabilities –The Gateway has a throughput limitation of 4 Mbps The PEHG stops responding with status when the Gateway is driven above this rate under certain conditions –Data transferred to the Gateway must be formatted (within the IEEE 802.3 data field) as a CCSDS Packet Only one Packet can be transferred in an IEEE 802.3 data frame Packet size can range from 512 bytes up to 1500 bytes –Requirement will be added to SSP 52050, the ISPR Software ICD The Gateway does not support upper layer protocols (TCP/IP) –However, the LANs do not prevent data sources from using upper layer protocols for Payload to Payload communications

14 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 14 IEEE 802.3 Gateway Message Format IEEE 802.3 Message format for Gateway addressed messages –Numbers represent the number of bytes (or octets) required for each field –Shaded Fields represent IEEE 802.3 Overhead –IEEE 802.3 requires a minimum inter-message gap of 9.6 micro- seconds Preamble 7 SFD 1 Src. Address 6 CCSDS Pkt 512-1500 FCS 4 FCS - Frame Check Sequence SFD - Start Frame Delimiter Dst. Address 6

15 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 15 C&DH Payload Data Transfer Capabilities High Rate Data Link Capabilities –High Rate Data Links (HRDL) consists of a pair of fiber optic cables at each Payload location (ISPR and Attached Payload Ports) attached to one of two Automated Payload Switches One fiber is permanently configured as an input the other being an output APSs route HRDL data from a source to a destination or destinations –Destinations include other IP Systems, Payload Locations, and COR/HRFM (Ku-band) –Each APS can support up to 20 input to output connections –Each APS has 4 outputs to the other APS for routing of data from a source on one APS to a destination or destinations on the other APS –Each fiber is capable of transferring data at a rate of up to 100 Mbps

16 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 16 C&DH Payload Data Transfer Capabilities High Rate Data Link Capabilities –For Data transfers to the HRFM, data can be transferred in one of two formats, Bitstreams or CCSDS Packets Bitstreams which require recording during Ku-band Loss of Signal (LOS) will be Packetized by the High Rate Communications Outage Recorder (HCOR) –Packetized Bitstreams will be delivered to the end user in this format for both real-time and recorded Bitstream Packets Packet sizes can range from 100 bytes up to 4096 bytes

17 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 17 Video Subsystem Capabilities Each US Lab ISPR location will have one fiber optic video input, one video output and one Video Sync signal interface with the Video Subsystem –Only one video signal can be transferred through a fiber at a time –The APM ISPR locations have similar video interfaces with the APM Video Subsystem Interfaces between the United States On-orbit Segment (USOS) Video Subsystem and the APM Video Subsystem are provided for transfer of up to 2 video signals from and/or to the APM –The ISPR locations in the JEM have the same video interfaces with the exception that the interface is electrical instead of optical As with the APM, the JEM video system has 2 sets of interfaces with the USOS Video Subsystem for exchange of video

18 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 18 Video Subsystem Capabilities The Video Subsystem provides the capability to downlink up to 4 Video signals via the Video Baseband Signal Processor (VBSP) –Has selectable Field Rates and Quantization levels for each channel Two Video Tape Recorders (VTR) are provided for recording/Playback of Video –Cassette tapes are Hi band 8 mm (2 hour duration) Two Sync and Control Units (SCU) are provided for distribution of Sync signals, Split Screen Processing (SSP) and Time Base Correction (TBC) –SSP provides the ability to combine the middle 50% of two video signals into one video signal –TBC is used for VTR dumps through Ku-band

19 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 19 Video Subsystem Diagram VSU-2VSU-4 VSU-3VSU-1 VBSP SCU-1 VTR-1 SCU-2 VTR-2 JEMAPM LAS1 LAS2 LAS3 LAS4 LAO1 LAO2 LAO3 LAO4 LAO5 LAP2 LAP4 LAD3 LAP1 ISPRs ISPR

20 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 20 Uplink Data Transfer Capabilities Files and Commands are uplinked through S-band –S-band provides a 72 Kbps uplink with up to two audio channels Throughput is 57 Kbps –Each audio channel requires 9.6 Kbps of bandwidth (not including overhead) –S-band is capable of uplinking 8 standard commands per second This includes both US and International Partner (IP) System and Payload commands Standard commands have a maximum length of 64 words –S-band may also support up to two file transfers simultaneously at a total rate of approximately 36 Kbps if only one Audio channel is utilized The maximum file size is limited to 8 Mbytes

21 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 21 Ku-band Downlink Data Transfer Capabilities Payload and Video Data are downlinked via Ku-band –Ku-band provides a 50 Mbps downlink capability through the UF- 2 timeframe Throughput is approximately 43.2 Mbps –The Ku-band HRFM multiplexes C&DH and Video data into one serial stream for downlinking Up to 8 HRDLs and 4 Video signals can be downlinked simultaneously within Bandwidth limitations –Ku-band output rate is expected to grow to 75 Mbps in the UF-3 timeframe and may eventually grow to 150 Mbps Ku-band is capable of all of these rates Depends on Ground System Upgrades 150 Mbps rate requires major Ground System Upgrades

22 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 22 Ku-band Downlink Data Transfer Capabilities During the UF-1 and UF-2 timeframes, the Medium Rate Communications Outage Recorder (MCOR) will be used to record 2 of the 8 HRDL interfaces with the HRFM –MCOR records data during “Scheduled” Ku-band communications outages Unscheduled Ku-band outages will result in lost data –One of the data sources which will be recorded by the MCOR will be the output of the Payload MDM Transfers Payload Health and Status data, Broadcast Ancillary Data, and Payload Low Rate Telemetry Data to Ku-band for downlink –The other data source is expected to be the output of the PEHG configured for Medium Rate Telemetry

23 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 23 MCOR Interface Diagram APS-1 APS-2 MCOR HRFM 1 2 3 5 6 7 8 4 MDM PL-1 MDM PL-2 PEHG-1 PEHG-2 Ku- band VBSP ISS Video

24 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 24 MCOR Capabilities The MCOR is a 75 Giga-bit device which provides two HRDL inputs (one from each APS) and two HRDL outputs to the HRFM –Data can be recorded on either or both inputs at rates up to 10 Mbps in CCSDS Packet Format only –Data can be played back at selectable rates up to 10 Mbps on one of the two outputs –The MCOR does not “Pass through” data from its input to its corresponding output The APSs are used to route the data sources directly to the HRFM –This effectively utilizes 4 of the 8 HRDL interfaces with the HRFM, two are routed to the MCOR and the same two sources must be routed around the MCOR to the HRFM –The MCOR can not be configured to record and playback simultaneously

25 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 25 Ku-band Downlink Data Transfer Capabilities The High Rate Communications Outage Recorder (HCOR) will be integrated onboard during the UF-2 timeframe –HCOR is a higher performance version of the MCOR which it replaces –Unlike the MCOR, the HCOR can “pass through” data on each of its inputs to each of its corresponding outputs –Data can be recorded at selectable rates up to 95 Mbps on each of its 8 inputs It can record data on all of the 8 HRDL interfaces between the APSs and the HRFM Data is recorded in CCSDS Packet Format Bitstreams which are required to be recorded can be encapsulated within a CCSDS Packet by the HCOR for both pass-through and recording

26 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 26 Ku-band Downlink Data Transfer Capabilities HCOR Capabilities –Data can be played back on up to two of its 9 outputs at selectable rates up to 95 Mbps Data coming into the port designated as the output port cannot be downlinked –Like the MCOR, the HCOR can not be configured to record and playback simultaneously –The HCOR will record/pass through data on its input based on its configured rate Any data sources which exceed this bandwidth allocation will result in lost data

27 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 27 HCOR Interface Diagram APS-1 APS-2 HCORHRFM 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 Ku- band 9 VBSP ISS Video MDM PL-1 MDM PL-2 PEHG-1 PEHG-2

28 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 28 VBSP Downlink Rates VBSP Selectable Field Rates and Quantization Settings and their effects on Ku-band Bandwidth

29 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 29 Ku-band Downlink Data Transfer Capabilities By Assembly Complete, HRFM Port availability becomes a major concern –There are only 8 HRFM Ports and several data sources besides Payloads require access Payload MDM must have access to a Port HCOR must utilize a port for Playbacks C&C MDM for ZOE File downlink (Ops Recorder) ESA will have allocation of a Port for downlinking of their Payload Data NASDA receives allocation of at least one port for their Payload Data downlink –An additional port may be required to obtain NASDA Payload Health and Status data Ops LAN for Crew Support requires access to the Ku-band downlink –May be shared with C&C MDM

30 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 30 Ku-band Downlink Data Transfer Capabilities HRFM Port Allocations At least one PEHG for Medium Rate Telemetry routing to Ku-band –This leaves up to two ports for all other HRDL Data sources US Attached Payload Ports provide only Payload Local Bus and HRDL interfaces

31 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 31 Communications Coverage Characteristics S-band and Ku-band antennas are placed in different locations onboard ISS which provides differing coverage characteristics –The Ku-band Antenna is permanently located on the Z1 Truss Up until 12A, the P6 PV Array is placed on top of Z1 causing a great deal of blockage to the Ku-band Antenna –S-band is located on top of the P6 PV Array at 5A.1 and is moved to the P1 Truss segment by Assembly Flight 1J/A A second S-band Radio Frequency Group is located on the S1 Truss segment at 9A

32 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 32 Documents of Interest SSP 52050, the ISPR to ISS Software Interface Control Document (ICD) for descriptions of the software interfaces with respect to Low Rate, Medium Rate and High Rate data transfers SSP 41158, USOS to International Ground System Segment Ku-band Telemetry Formats (the Ku-band Space to Ground ICD) provides details on the format requirements for Ku-band data transfers SSP 41002, the ISPR to NASA/ESA/NASDA ICD provides details on the ISPR hardware interfaces

33 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 33 Backup Charts

34 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 34 LRT Bandwidth Allocation Example The purpose of this example is to show how the Payload MDM will allocate resources to 4 Payloads attached to the same Payload Local Bus –Payload A requests 30 Kbits of LRT Bandwidth at a 1 Hz rate –Payload B requests 10 Kbits of LRT Bandwidth at a 0.1 Hz rate –Payload C requests 20 Kbits of LRT Bandwidth at a 0.1 Hz rate –Payload D requests 60 Kbits of LRT Bandwidth at a 1 Hz rate

35 POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 35 LRT Bandwidth Allocation Example 1 Sec 23456789101 2 Sec 3 Sec 4 Sec 5 Sec 6 Sec 7 Sec 8 Sec 9 Sec 10 Sec 11 Sec AAAB AAAC AAAC AAA AAA AAA AAA AAA AAA AAA AAA D D D D D D Slots (Processing Frames) D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D B


Download ppt "POIC Data Management POIWG, June 22-25, 1999 G.K./Ops/POIWG/June_99/POIWG_Data_Flow_6_99 1 Onboard Payload Data Flow Capabilities Gary Knickerbocker POIF."

Similar presentations


Ads by Google