Standard Service Configurations 31 March – 3 April 2014 Noordwijkerhout, Netherlands John Pietras Global Science and Technology, Inc., Greenbelt, MD, USA

2 Purpose Nominally to respond to CSSMWG Action Item Walk through the Functional Groups to determine the different permutations of configuration profiles using the Service Catalog 1

Possible Approaches to Developing a Configuration Profile Information Entity (1 of 3) Building Block Approach: define all of the components (FG specializations) and the rules for combining them 3

Possible Approaches to Developing a Configuration Profile Information Entity (2 of 3) The Michelangelo approach: start with a template containing all functional group specializations and cut away anything that doesn’t “look” like the mission of interest 4

Middle Approach: define a set of configurations that can be trimmed and/or augmented 5

All Functional Groups for IOAG SC#1, with Specializations 6

Functional Groups for SLS Services, with Specializations 7 All FGs involved, but no connections between: o Offline Data Delivery Production and Data Delivery Transfer Services o Retrieval Radio Metric Data Production and Radio Metric Data Services

Relationships Among FG Specializations for SLS Services 8

FGs Needed to Support IOAG Service Catalog #1 Data Delivery and Radio Metric Services 9 FG -> IOAG service v Aperture Forward Physical Channel Xmission TC Sync & Channel Encoding Forward AOS Sync & Channel Encoding Forward TC Space Link Protocol Xmission Forward AOS Space Link Protocol Xmission Return Physical Channel Reception Return TM Sync & Channel Decoding Return TM/AOS Space Link Protocol Reception SLS Data Delivery Production Offline Data Delivery Production Data Delivery Transfer Services SLS Radio Metric Data Production Retrieval Radio Metric Data Production Radio Metric Data Services Forward CLTUMMM M C 1 M Forward Space Packet MMM M C2 M Forward FrameMMC3C4 C5 M Forward File (SLS) MMC6C7C6C7C8 MM RAF (online)M MM M RCF (online)M MM M ROCFM MM M Offline Frame Buffer M MM MM RUFT (real- time) M M M M TM Segment Buffer M M MM Return File (SLS)MC8C9C10C9C10MMMMM Validated R-M (SLS) MM M MM Raw Data R-M (real-time) MM M M M TDM Recording Bufffer MM M MM Delta-DOR (SLS)M M MM Conditions C1Required if forward link status is required to control production statusC6Required if the service is operating over a TC link C2 Required if forward link status is required to control production status or if the services is running over COPC7Required if the service is operating over an AOS link C3Required if service is transferring TC framesC8Required if the service is operating in Reliable Transfer mode C4Required if service is transferring AOS CADUs or AOS framesC9Required if the service is operating in Reliable Transfer mode and the forward link is TC C5Required if service is transferring AOS framesC10Required if the service is operating in Reliable Transfer mode and the forward link is AOS

IOAG SC1 Paths through the FGs (1 of 3) FCLTU o FCLTU over unreliable Telecommand (4 FGs) o FCLTU over reliable Telecommand (7 FGs) o 4 FGs common to both paths FSP o FSP over unreliable Telecommand (5 FGs) o FSP over reliable Telecommand (8 FGs) o 5 FGs common to both paths FF-CSTS o FF-CSTS over unreliable Telecommand (5 FGs) o FF-CSTS over reliable Telecommand (8 FGs) o FF-CSTS frame mode over AOS (5 FGs) o FF-CSTS CADU mode over AOS (4 FGs) o 3 FGs common to all paths SLE RAF o RAF over Return TM/AOS (4 FGS) 10

IOAG SC1 Paths through the FGs (2 of 3) SLE RCF o RCF over Return TM/AOS (4 FGS) SLE ROCF o ROCF over Return TM/AOS (4 FGS) RUFT CSTS o RUFT over Return TM/AOS (4 FGS) Forward File o Forward File over unreliable CFDP over unreliable Telecommand (6 FGs) o Forward File over reliable CFDP over Telecommand (9 FGs) o Forward File over unreliable CFDP over Forward AOS (6 FGs) o Forward File over reliable CFDP over Forward AOS (9 FGs) o 4 FGs common to all paths Return File o Return File over unreliable CFDP (6 FGs) o Return File over reliable CFDP (Telecommand ack channel) (9 FGs) o Return File over reliable CFDP (Forward AOS ack channel) (9 FGs) o 6 FGs common to all paths 11

IOAG SC1 Paths through the FGs (3 of 3) Validated Radiometric Data o Forward-only link (4 FGS) o Return-only link (4 FGs) o Bidirectional link (5 FGs) Raw Radiometric Data o Forward-only link (4 FGS) o Return-only link (4 FGs) o Bidirectional link (5 FGs) Delta-DOR Data (return link only - 4 FGs) o Forward-only link (4 FGS) o Return-only link (4 FGs) o Bidirectional link (5 FGs) Open Loop Recording (return link only – 4 FGs) o ROCF over Return TM/AOS (4 FGS) 12

Common FGs in Service Paths Only one FG common to all 13 services in all configurations – Antenna 2 FGs common to all 4 forward services in all configurations 3 FGs common to all 4 TC services in all configurations 2 FGs common to all 5 return services in all configurations 2 FGs common to all radio metric services in all configurations 13

Possible Standard Configurations Bidirectional space link data delivery configurations TC/TM SLE-Plus Reliable File Transmission – TC Forward AOS SLE-Plus Reliable File Transmission – AOS Forward Reliable Telecommand Unidirectional space link data delivery configurations Unreliable Telecommand Unreliable Forward File Transmission – TC Forward AOS CSTS Unreliable Forward File Transmission – AOS Return SLE-Plus Unreliable Return File Reception Radio Metric-only configurations No-Communication Radiometric Delta-DOR Open Loop Recording 14

TC/TM SLE-Plus (1 of 2) 15

TC/TM SLE-Plus (2 of 2) One F-CLTU service instance OR (zero or more FSP service instances AND zero or more Forward Frames service instances) Zero or more instances of any of the following services/buffers (at least one required) RAF service RCF service ROCF service RUFT service Offline Frame Buffer Unframed Telemetry Buffer Raw Radiometric Data o All radiometric parameters available to be reported by TD-CSTS o Optional – can be deleted Validated Radiometric Data o All radiometric parameters available to be recorded for subsequent validation o Optional – can be deleted 16

Reliable File Transmission – TC Forward (1 of 2) 17

Reliable File Transmission – TC Forward (2 of 2) Builds on TC/TM SLE-Plus, minus FCLTU and RUFT One Forward File Server and/or one Return File Server Zero or more FSP service instances AND zero or more Forward Frames service instances Zero or more instances of any of the following services/buffers (none required) RAF service RCF service ROCF service Offline Frame Buffer Raw Radiometric Data o All radiometric parameters available to be reported by TD-CSTS o Optional – can be deleted Validated Radiometric Data o All radiometric parameters available to be recorded for subsequent validation o Optional – can be deleted 18

AOS SLE-Plus (1 of 2) 19

AOS SLE-Plus (2 of 2) Zero or more Forward Frames service instances Can be either frame mode or CADU mode Zero or more instances of any of the following services/buffers (at least one required) RAF service RCF service RUFT service Offline Frame Buffer Unframed Telemetry Buffer Real-Time Radiometric Data o All radiometric parameters available to be reported by TD-CSTS o Optional – can be deleted Validated Radiometric Data o All radiometric parameters available to be recorded for subsequent validation o Optional – can be deleted 20

Reliable File Transmission – AOS Forward (1 of 2) 21

Reliable File Transmission – AOS Forward (2 of 2) Builds on AOS SLE-Plus, minus Forward Frames in CADU mode and RUFT One Forward File Server and/or one Return File Server Zero or more Forward Frames service instances in frame mode Zero or more instances of any of the following services/buffers (at least one required) RAF service RCF service Offline Frame Buffer Unframed Telemetry Buffer Real-Time Radiometric Data o All radiometric parameters available to be reported by TD-CSTS o Optional – can be deleted Validated Radiometric Data o All radiometric parameters available to be recorded for subsequent validation o Optional – can be deleted 22

Reliable Telecommand (1 of 2) 23

Reliable Telecommand (2 of 2) Used whenever forward link status or COP feedback is required from the CLCW One F-CLTU service instance OR (zero or more FSP service instances AND zero or more FSP service instances) Real-Time Radiometric Data o All radiometric parameters available to be reported by TD-CSTS o Optional – can be deleted Validated Radiometric Data o All radiometric parameters available to be recorded for subsequent validation o Optional – can be deleted NOTE – Reliable Telecommand for 3-way tracking configurations could be achieved by adding an ROCF User FG to the Unreliable Telecommand configuration 24

Unreliable Telecommand (1 of 2) 25

Unreliable Telecommand (2 of 2) 26 Used when neither forward link status nor COP feedback is required One F-CLTU service instance OR (zero or more FSP service instances AND zero or more Forward Frame service instances) Real-Time Radiometric Data o Only radiometric parameters that are available from the antenna and forward link physical channel (e.g., antenna angles and actual transmit frequency) o Optional – can be deleted

Unreliable Forward File Transmission – TC (1 of 2) 27

Unreliable Forward File Transmission – TC (2 of 2) Builds on Unreliable Telecommand, minus FCLTU One Forward File Server Zero or more FSP service instances AND zero or more Forward Frame service instances Real-Time Radiometric Data o Only radiometric parameters that are available from the antenna and forward link physical channel (e.g., antenna angles and actual transmit frequency) o Optional – can be deleted 28

Forward AOS CSTS (1 of 2) 29

Forward AOS CSTS (2 of 2) One or more Forward Frames CSTS instances Frames mode CADU mode Q: will any mission choose to use both modes? Forward AOS Space Link Protocol Transmission is only required when FF-CSTS operate in the frames mode Not needed for CADU mode Real-Time Radiometric Data o Only radiometric parameters that are available from the antenna and forward link physical channel (e.g., antenna angles and actual transmit frequency) o Optional – can be deleted 30

Unreliable Forward File Transmission – AOS (1 of 2) 31

Unreliable Forward File Transmission – AOS (2 of 2) Builds on Forward AOS CSTS, minus Forward Frame CADU mode One Forward File Server One or more Forward Frames CSTS instances (Frame mode) Real-Time Radiometric Data o Only radiometric parameters that are available from the antenna and forward link physical channel (e.g., antenna angles and actual transmit frequency) o Optional – can be deleted 32

Return SLE-Plus (1 of 2) 33

Return SLE-Plus (2 of 2) Zero or more instances of any of the following services/buffers (at least one required) RAF service RCF service ROCF service RUFT service Offline Frame Buffer Unframed Telemetry Unneeded types can be deleted Real-Time Radiometric Data o All radiometric parameters available to be reported by TD-CSTS o Optional – can be deleted Validated Radiometric Data o All radiometric parameters available to be recorded for subsequent validation o Optional – can be deleted 34

Unreliable Return File Reception (1 of 2) 35

Unreliable Return File Reception (2 of 2) Builds on Return SLE-Plus, minus RUFT One Return File Server Zero or more instances of any of the following services/buffers (at least one required) RAF service RCF service ROCF service Offline Frame Buffer Unneeded types can be deleted Real-Time Radiometric Data o All radiometric parameters available to be reported by TD-CSTS o Optional – can be deleted Validated Radiometric Data o All radiometric parameters available to be recorded for subsequent validation o Optional – can be deleted 36

Non-Communication Raw Radiometric (1 of 2) 37

Non-Communication Raw Radiometric (2 of 2) Does anyone schedule a pass that is pure tracking (no comm)? 38

Non-Communication Validated Radiometric (1 of 2) 39

Non-Communication Validated Radiometric (2 of 2) Does anyone schedule a pass that is pure tracking (no comm)? 40

Delta-DOR (1 of 2) 41

Delta-DOR (2 of 2) Does any communication take place across the Delta-DOR return link? 42

Open Loop Recording (1 of 2) 43

Open Loop Recording (2 of 2) Open Loop Recording is not part of IOAG SC #1, but should have been according to W. Hell Open Loop Recording should really be an add-on to any of the configurations with a return link o TC/TM SLE-Plus o Reliable File Transmission (TC and AOS) o AOS SLE-Plus o Reliable Telecommand o Return SLE-Plus o Unreliable Return File Transmission OLR should not be a part of the standard configurations because it is rarely used 44