Considerations for the Service Considerations for the Service Package Request/Service Package Package Request/Service Package

Recommended StandardRecommended Standard

28-31 October 2013San Antonio, TX

John PietrasGlobal Science and Technology, Inc., Greenbelt, MD, USA

www.ccsds.org

Service Package Request

• Service Package Request must be capable of accommodating all* known/planned SM interfaces defined as of today (or some other TBD cutoff?)

• “Extensibility” in the Service Package Request is about the ability to accommodate flexibilities and constraintso Minimal flexibilities/constraints: start and stop times per Space Link

Configurationo B-1 equivalent flexibilities and constraints: start time, plus offset, minus offset,

preferred duration, minimal duration per Space Link Configuration; group space link carriers by antenna with relative offsets; scenarios; respecifications; sequence of events

o SGSS flexibilities and constraints: recurrent requests, time windows, linked Space Link configurations, waitlisting, freeze intervals

2

*Where all is defined as those interfaces of Agencies willing to provide requirements and participating in (at least) Red Book reviews

www.ccsds.org

SLS Service Package Request Template

3

Identifies all of the Space Link Profiles that are used in the Request

Identifies all of the SLS TS Profiles that are used in the Request

Specifications of the flexibilities and constraints that areused in the Request.

Extension Point for new flexibilities and constraintsSpace Link Profile

Aperture

Forward Physical Channel

Transmission

Return Physical Channel

Reception

Forward Sync and Channel

Encoding

Return Sync and Channel

Decoding

Forward Space Link

ProtocolTransmission

Return Space Link

ProtocolReception

Radio Metric Data Production

Data Delivery

Production

Data Delivery

Production

Data Delivery

Production

spaceLinkProfileNameRef

SpaceLinkRequest

transferServiceProfileNameRef

SlsTsRequest

1

1..*

servicePackageId

ExtensibleSpaceLinkSessionServicePackageRequest

FexibilitiesAndConstraints

1

0..*

1

1..*

ServiceManagementFunctions

1

0..*

Instances of SM Function Functional Resources

references

Service Management

Functions

Data Delivery Services

Data Delivery Services

Data Delivery Services

www.ccsds.org

Flexibilities and Constraints

• F & C “rule classes” reference the Profiles that they operate on, they do not contain themo “Schedule Space Link Profile M from start time X to stop time Y”

• F & C rule classes can operate in combinations (subject to conflict avoidance)o E.g., “Schedule Space Link Profile M with nominal start time X, start

lead of X1, start lag of X2, preferred duration of Y1, minimal duration of Y2” AND “Schedule Space Link Profile N to start 5 minutes after the start of Space Link Configuration M” AND “Schedule Space Link Profile N to end 3 minutes before the end of Space Link Configuration M”

• Rule classes can operate on rule classeso E.g., a single scenario can be a set of rules; a different scenario can be

controlled by a different set of rules4

www.ccsds.org

“Standard” Service Package Request

• Define a truly minimal Request that every implementation must supporto At least one Space Link Configurationo The SLS TSs that go with that Space Link Configurationo Minimal Flexibilities and Constraints rule class

Start time and stop time for the Space Link Configuration and associated TSs I.e., a “Simple Service Package Request”

• Define additional rule objects that provide all of the additional F&Cs required for the target set of implementationo Standard but optional

• Update book to add new F&C rule classes as they are defined

• NOTE – users/implementers won’t have to understand the “rules for making rules”; the resulting rules will be simply specified in the book

• Possible variation?o Allow SLS Service Package Request to directly include configuration profiles

“Simpler” in those cases where a one-off configuration is needed

5

www.ccsds.org

Service Package

• Must support at least 2 levels of detailo Terse – identifies the Functional Resource Names of all the FRs

in the Service Package Needed for MD-CSTS (and Service Control CSTS in the future) Implies that even a minimal Service Package will contain objects for

all FRs in the Packageo Verbose – also contains all parameter values

Required for NASA SGSS

• Result – Service Package will look more like their source configuration profiles

6

www.ccsds.org

Schedule of Service Packages

• An SGSS “schedule” is a collection of Service Packages (nominally, for one week or two week periods)o SGSS has modified the Query Service Package operation to be able to

retrieve multiple Service Packages at once

• Proposal - include a Schedule of Service Packages information entity in the Service Package Request/Service Package book that would address this need in a standard way without depending of a new ESCCS-SM operation to do it o Can be defined as a simple wrapper around multiple Service Package

Info Entities with schedule start/stop times

7