1 Management of Offline SLE Services SLe-SM Red-1 RID GSFC-09-JP John Pietras

2 Scope Current (“traditional”) SLE return offline services only –Specifically, RAF and RCF –Could be extended for ROCF and RSP, but not elaborated here Could be extended for FTP-based return offline services, but not addressed here Structured in accordance with proposals in Composite Carrier Profiles analysis –Can be made to work without Composite Carrier Profiles structures, but the data sets would be structured differently

3 Summary of Concept Data storage requirements are negotiated and recorded as part of the Service Agreement Configuration profiles are expanded to include Data Sink entities that map SLE (and other bilaterally-defined) data channels into assigned (logical) data storage entities, based on characteristics of the data –All frames on a symbol stream or of particular GCVIDs –Good frames, bad frames, or all frames –(Concept extends to cover other CCSDS space link data units (e.g., space packets) –In accordance with provisions of the Composite Carrier Profile proposal, these Data Sink entities are activated by default unless modified on a per-Service Package basis Configuration profiles are expanded to include Offline Transfer Service Profiles for the playback of the recorded data (Online) Service Package structure augmented to allow optional per- Service Package modification of data storage operations – Not necessary when default storage configurations are used Offline Service Package defines the offline transfer service instances that can access the Data Stores (and when)

4 Extension of SLE-SM Resource Model for Offline Services: Execution of Online Service Package Forward Space Link Carrier Production Forward Symbol Stream Production Forward Link Protocol Production Forward CLTU Transfer Service Provison Return Link Protocol Production Return RAF Online Transfer Service Provision 1 provides symbols to Return RCF Online Transfer Service Provision Return Space Link Carrier Production provides symbols to 1 provides bitstream to 1 provides CLTUs to Return Symbol Stream Production 1 provides bitstream to 1 0..* provides transfer frames to 1 0..* provides transfer frames to antenna 1 sends carrier signals to 1 sends carrier signals to Return RAF Data Sink Return RCF Data Sink 1 0..* provides transfer frames to 1 0..* provides transfer frames to Data Store Data Store Default configuration defined as part of Carrier Profile(s) Data storage filtering may be modified in Service Package

5 Extension of SLE-SM Resource Model for Offline Services: Execution of Offline Service Package Return RAF Offline Transfer Service Provision Return RCF Offline Transfer Service Provision 1 0..* provides transfer frames to 1 0..* provides transfer frames to Data Store Data Store

6 Issue: How to Identify Offline Data Sets? Some scheme is needed to identify the specific space data channel that is to be used as the source of an offline transfer service instance One way might be to dedicate a separate DataStore to each flow –Results in either inefficient use of DataStores or micro-definition of DataStores Proposed approach: Identify stored space data channel data by Functional Group –Different functional groups may, e.g., represent multiple simultaneous symbol streams (e.g., S and Ku Band) –Syntax and significance of Functional Group IDs to be determined bilaterally by Mission and Complex –Functional Group ID is subsequently used to form the service-instance- identifier of the offline transfer service instance

7 New Data Sets for Offline Transfer Services New Service Agreement data set –DataStore: negotiated as part of Service Agreement New Configuration Profile data sets –Storage DataSinkProfile: defines configuration for filtering space link data channel contents into a DataStore DefaultDataSink: attached to Carrier Profile to specify a data sink to be activated by default –Retrieval OfflineTransferServiceProfile New Service Package data sets –Storage DataSinkInstanceRequest: Optionally allows modifications to DataSinkProfiles DataSinkMapping: Optionally allows modification of set of data sinks to be activated for a CarrierRequest –Retrieval Offline Service Package OfflineTransferService

8 Instances of DataStore entities are defined in the Service Agreement –minSize (in MOctets): The minimum storage guaranteed –maxSize (in MOctets): The maximum storage that can be used –dataStoreId: URI –storedDataType: set of Frame (ROCF - future) (RSP - future) –Overflow policy Discard oldest data first Don’t accept new data if DataStore is full (other?) –Purge policy Fixed availability period (e.g., 2 weeks) (other?) DataStore

9 DataSinkProfile DataSinkProfiles are configuration profiles that specify how space link channel data are to be stored Subclasses –RafSinkProfile –RcfSinkProfile –(RocfSinkProfile – future) –(RspSinkProfile – future) Common parameters of DataSinkProfiles –dataSinkConfigProfileId The unique identifier of this data sink config profile –functionalGroupId The “functional group” that produces the space data channel that is to be stored –dataStoreRef The Data Store that receives the data –defaultStartTimeOffset Offset from the start time of the containing carrier that the data will start to be captured –defaultStopTimeOffset Offset from the stop time of the containing carrier that the data will start to be captured RafDataSinkProfile –allowedFrameQuality Can be set to ‘good-only’ or ‘errored-only’ to reduce storage usage, or set to ‘all’ or ‘undefined’ to maximize retrieval options RcfDataSinkProfile –channelFrameGvcid Selects a single channel frame –By defn, only good frames can be stored when selecting on a GVCID or MCID Multiple RcfSinkProfiles and RafSinkProfiles can have the same dataStoreRef –Result would be a single DataStore instance that contains data from multiple (but not all) channels

10 DataSinkProfile

11 DefaultDataSink DefaultDataSink entities are added to CarrierProfiles in lieu of (or in addition to) SLE transfer service profiles Contained by RafProd data set DefaultDataSinks reference DataSinkProfiles –Preserves common storage configuration across multiple scenarios

12 Proposed Carrier Profile (“bottom”) with Default Data Sinks iqChannelAssignment convolutionalCoding R401SymbolStreamF401SymbolStream rFec rFrameLength tlmRandomization interleaveDepth RafProd transferService ConfigProfileRef defaultService InstanceNumber TransferService 1111 FcltuTsP 1111 RafTsPRcfTsP 1 0..* {at least one} * 0..* 0..* BilateralTsP 0..* 1 {xor} RafDataSink dataSinkProfileRef DfaultDataSink BilateralDataSink

13 Default vs. Reconfigurable Data Sinks Default Data Sinks that are specified as part of a Carrier Profile will be activated without explicit citation in Service Packages The default Data Sinks may be modified on a per-Service Package basis in either of the following ways: –The Service Package may modify the default offset start and/or stop time associated with all instances of one or Data Sink Profile (e.g., across all scenarios) in that Service Package, by explicitly including a DataSinkInstanceRequest data set for each Data Sink to be modified –The Service Package may modify the default set of active Data Sinks associated with one or more carriers in the Service Package by explicitly containing a DataSinkMapping for each DataSink that is to be active for each carrier If any DataSinkMappings are specified for a CarrierRequest, all DataSinkMappings for that CarrierRequest must be explicitly added The explicitly-specified DataSinkMappings must be a subset of the DefaultDataSinks for the referenced Carrier Profile

14 DataSinkInstanceRequests A DataSinkInstance entity is added to a > instantiation in order to modify the default offset start and/or stop time –Contained by DataSinkInstances data set Subclasses –No explicit DataSinkInstance types (e.g., RAF, RCF) DataSinkInstance parameters –dataSinkProfileRef The identifier of the data sink profile that this instance references –startTimeOffset Override value for the offset from the start time of the containing carrier that the data will start to be captured –stopTimeOffset Override value for the offset from the stop time of the containing carrier that the data will cease to be captured

15 DataSinkMapping A DataSinkMapping entity is added to a > instantiation in order to delete one of the default Data Sinks from the Carrier Profile referenced in the CarrierRequest –Contained by CarrierRequest data set Subclasses –No explicit DataSinkMapping types (e.g., RAF, RCF) DataSinkMapping parameters –dataSinkProfileRef The identifier of the data sink profile that this mapping references

16 > with DataSinkInstanceRequests and DataSinkMappings

17 OfflineTransferServiceProfile An OfflineTransferServiceProfile is a configuration profile that specifies what stored space link data channel is to be retrieved, and the configuration of the transfer service that is to deliver it –All offline transfer service profiles offlineTransferServiceProfileId dataStoreRef –All SLE offline transfer service profiles currentTsVersion functionalGroupId – used to both select the source space link data channel and to construct the service-instance-identifier of the offline transfer service instance lowerBoundReportingPeriod defaultUserId transferBufferSize –RAF offline transfer service profiles allowedFrameQuality –allowedFrameQuality may differ from that at which the frame channel was recorded –May result in no data transferred if there is no overlap with the quality at which the data was recorded –RCF transfer service profiles allowedChannelFrameGvcids –allowedChannelFrameGvcids may be a subset of the space link frame channels that were recorded

18 OfflineTransferServiceProfile

19 OfflineServicePackage An offline service package establishes one or more offline transfer service instances for specified periods of time Conceptually, a simple container for offlineServiceInstanceRequests –Complexity of online service packages not necessary No scenarios No carriers Data Stores Parameters of offlineServiceInstanceRequest –transferSeviceProfileRef Points to the offlineTransferServiceProfile that specifies the source DataStore and the configuration of the offline service instance –accessStartTime Specifies the start time that the offline transfer service instance is to be enabled –accessStopTime Specifies the start time that the offline transfer service instance is to be disabled Can be established by bilateral means, or via TBS “Create Offline Service Package” operation (etc.)

20 OfflineServicePackage

21 Execution of Offline Service Package Each offlineTransferServiceInstanceRequest results in an offline transfer service instance that is enabled from its individual accessStartTime through accessStopTime Each offline transfer service instance may retrieve data of the specified space link data channel(s) from the specified DataStore that was acquired between accessStartTime and accessStopTime –accessStartTime may be set to a time before service package creation time to allow access to “previous” data Data retrieval criteria are independent of those by which the data were originally stored –Good frames stored via an RAF data sink instance can be retrieved via RCF offline transfer service instances –Each attempt to retrieve data from the Data Store may or may not be successful, depending on whether the DataStore has data that meets the criteria Not an error condition