Cross Support Service Management Overview Nicolas Champsavoir DCT/PS/SSC CCSDS – CSS Area Cross Support Services ex-SLE Service Management

Cross Support Service Management 2 Contents ■What are Cross Support Services ? ■Space Link telemetry and command protocols overview ■Cross Support overview ■Space Link Extension (SLE) overview ■Cross Support Service Management concepts ■CSSM Services overview ■Real world use cases and examples References ■ ■Cross Support Concept Book (Green book) v1 : 910x3g2s.pdf ■Cross Support Reference model v1 : 910x4b2e1.pdf ■CSSM Standard (Red Book) v1 : 910x11r1.pdf

Cross Support Service Management 3 The SLE extend the return Telemetry (TM) and forward Telecommand (TC) services defined by CSSDS for Space Link data exchanges. What are SLE Services ?

Cross Support Service Management 4 What are Cross Support Services ? The Cross Support Services include to major elements : ■Transfer Services (CSTS)  move spacelink data unit between ground stations, control centers, and end-user facilities  SLE services are part of the Cross Support Transfer Services ■Service Management (CSSM)  that control the scheduling and provisioning of the Transfer Services (including SLE service)  CSSM is the new name of SLE-SM

Cross Support Service Management 5 From SLE to Cross Support Transfer Services (CSTS) ■The SLE services extend the Space Link services as follows :  over distance : Space Link protocol processing may be done in multiple locations, possibly geographically separeted from the antenna.  in time : data flows can be stored and retrieved later.  by adding information : conditions at the time of the receipt is added to the space link data (in the form of annotations). ■The CSTS services will extend the SLE by adding transfer services for Ground Facilities generated information :  Datation  Positioning (Delta-DOR)  Orbit Dertermination  Others ?

Cross Support Service Management 6 What are SLE Services ? Extension over time, distance and information

Cross Support Service Management 7 Space Link protocols : Return Services Spacecraft ID Virtual Channel ID… Optional Extra counters… Command Link Control Word APID Packet length… DATAHEADER Space packet HEADER 2 nd HEADER PACKET CLCWRSCODE Frame

Cross Support Service Management 8 Return SLE Services ■Return All Frames (RAF) : provides all the frames of the space link data stream. ■Return Complete Frames (RCF) : provides Master Channel (MC) or specific Virtual Channel (VC) of a particular RAF channel. ■Return Frame Secondary Header (RFSH) : provides MC or VC frame secondary header extracted from a RAF channel. ■Return Operational Control Field (ROCF) : provides MC or VC operational control fields extracted from a RAF channel. ■Return Space Packets (RSP) : provides packets with selected Application Process IDentifiers (APIDs) extracted from a VC. ■Return Insert or Return Bitstream : AOS services to be defined…

Cross Support Service Management 9 Return SLE Services

Cross Support Service Management 10 Space Link protocols : Forward Services Spacecraft ID Virtual Channel ID Frame counter… APID Packet length, counters… DATAHEADER TC Packet HEADERPACKET RSCODE TC Frame ENCODED TC DATASTART SEQUENCE Command Link Transmission Unit (CLTU) TAIL SEQUENCE

Cross Support Service Management 11 Forward SLE Services ■Forward Space Packets (FSP) : enables single users to provide packets for uplink with needing to co-ordinate with other users of the spacecraft. ■Forward Telecommand Virtual Channel Access (FTCVCA) : enables users to provide complete VCs for uplink. ■Forward Telecommand Frame (FTCF) : enables users to provide TC frames to be transformed to Command Link Transmission Units (CLTU) ready for uplink. ■Forward Command Link Transmission Unit (FCLTU) : enables users to provide CLTUs for uplink to the spacecraft.

Cross Support Service Management 12 Forward SLE Services

Cross Support Service Management 13 SLE Complexes SLE System is composed of one or more SLE Complexes. Each SLE Complex is a logical system that provides one or more SLE services and interoperate with the Mission Data Operations System (MDOS) and/or other SLE Complexes. The various SLE Complexes that composes an SLE System may be operated independently by different agencies.

Cross Support Service Management 14 Complex Management (CM) and Utilization Management (UM) One CM can handle many UMs

Cross Support Service Management 15 Purpose of Cross Support Service Management Standardize and automate interactions between users and providers of space link and transfer services, and provide the means to configure the resources needed to execute those services ■Set the values of the parameters involved in space link and cross support transfer services (CSTS) such as SLE ■Specify the services needed to execute space link and CSTS ■Configure ground stations for the establishment of space links ■Configure ground stations for processing of forward and return space link data ■Arrange timely provision of transfer services ■Disseminate Trajectory Predictions CSSM standardize the interactions between Utilization Management (UM) and Complex Management (CM)

Cross Support Service Management 16 CSSM Utilization Management (UM) It is the function within the MDOS that coordinates the requests by users for space link and transfer services from the SLE Complex. Utilization Management role: ■Requests periods of provision of space link services and space link extension transfer services ■Provides configuration information for RF, modulation, space link service, and space link extension transfer service ■Provides Trajectory Prediction information that allows the Complex to determine where the mission spacecraft will be at the requested periods of service provision ■Coordinates with Mission User Entities within the MDOS to enable the execution of SLE services and to collect status information.

Cross Support Service Management 17 CSSM Complex Management (CM) Complex management controls the extent to which Utilization Management can affect actual SLE Complex resources and, as such, acts as the SLE transfer service producer and provider. Complex Management role : ■Negotiates types of services, numbers of service instances, and the length of the Service Agreements with UM; ■Responds to requests from the UM for individual space link sessions; ■Provides configuration information to the resources of the SLE Complex to enable the production and provision of SLE services, and monitors their correct operation.

Cross Support Service Management 18 CSSM Services and Information Entities ■Service Agreement service  The Service Agreement covers all aspects of CSSM and defines the bounds for the three other information entities ■Configuration Profile service  Configuration Profiles are used by CM and UM to define preset configurations of space link and transfer services (eg. SLE) production parameters ■Trajectory Prediction service  Trajectory Predictions defines the course of the spacecraft over a period of time ■Service Package service  Service Packages specifies the antenna, space link and transfer services (eg. SLE) configuration, and time span for a particular space link session.

Cross Support Service Management 19 Services Dependencies Service Agreement Service Service Package Service Configuration Profile Service Trajectory Prediction Service

Cross Support Service Management 20 What is a « Service » ? ■Service definition in CCSM is simpler than in a classic Service Oriented Architecture (SOA) :  No discovery of service, no registry etc.  All messages and interactions are statically defined  More like a Client/Server architecture with one single server (CM) and multiple clients (UM) ■A service is defined by :  Information : what is necessary to configure the service  Operations to alter the information hold by the service : an operation is a sequence of exchanged messages between the service provider and the service consumer. ■The CSSM standard provides : UML Diagrams, State Diagrams and, for each service, a list of operations (with formal XML Schemas for every messages)

Cross Support Service Management 21 Services Dependencies Service Agreement Service Service Package Service Configuration Profile Service Trajectory Prediction Service Service Agreement Service

Cross Support Service Management 22 Service Agreement Service Information  Boundaries and constraints on services to be requested an provided agreed to by CM and UM.  Identification of authorized service users (tranfer service security information) Operations  QUERY_SERVICE_AGREEMENT

Cross Support Service Management 23 Services Dependencies Service Agreement Service Service Package Service Configuration Profile Service Trajectory Prediction Service Configuration Profile Service

Cross Support Service Management 24 Configuration Profile Service Information  Space Link Physical  E.G. carrier frequency, sub-carrier freqency, modulation index, etc.  Can change as a function of time  Space Link Protocols  Command encoding and telemetry decoding algorithms  Transfer Services  Parameters to configue, enable SLE Transfer Services Operations  [ ADD | DELETE | QUERY ]_SPACE_LINK_SESSION_PROFILE  [ ADD | DELETE | QUERY ]_SPACE_LINK_EVENTS_PROFILE  [ ADD | DELETE | QUERY ]_ SLS_TRANFER_SERVICE_PROFILE  [ ADD | DELETE | QUERY ]_ RETRIEVAL_SERVICE_PROFILE

Cross Support Service Management 25 Space Link Session Profile Configuration Service Profile ■Forward and return Space link Carrier and sub-carrier  Frequency, waveform, modulation, polarization, power ratio, sweep parameters… ■Symbol stream  Symbol rate, IQ channel assignement, convolutionnal coding… ■RAF Production  FEC, frame length, interleave depth… ■CCSDS DataSink  Datasink ID, storage selection criterion, store channels…

Cross Support Service Management 26 Space Link Event Profiles Configuration Service Profile ■Return and Forward Space Link State  State Id, start/end times, start/end time windows ■Return and Forward Space Link Events  Event time, time window, sequence number ■Space Link Data Transport Parameters (associated with State and Events)  Communication mode, convolutionnal coding, polarization… whatever can change during a space link session.

Cross Support Service Management 27 Space Link Session Transfer Service Profiles Configuration Service Profile ■CCSDS SLS transfer service common parameters  Functional group ID, timeout period, start time offset, end time offset, user ID… ■RAF service transfer profile  Authorize frame quality… ■RCF service transfer profile  Virtual Channel identifiers … ■FCLTU service transfer profile  Notification mode… ■Bilateral service transfer profile  User specific (currently not defined as an SLE service)

Cross Support Service Management 28 Retrieval Transfer Service Profiles Configuration Service Profile ■CCSDS Retriecal TS Profile  UserId, transfer buffer size, lower bound reporting period… ■Either Offline RAF TS Profile ■Or Offline RAF TS Profile  Virtual Channel ID ■Or Retrieval Bilateral TS Profile  User specific (currently not defined as an SLE service)

Cross Support Service Management 29 Services Dependencies Service Agreement Service Service Package Service Configuration Profile Service Trajectory Prediction Service

Cross Support Service Management 30 Trajectory Prediction Service Information  Spacecraft position as function of time, either in OEM format (Ephemeris), or in OPM format (?) Operations  ADD_TRAJECTORY_PREDICTION  DELETE_TRAJECTORY_PREDICTION  QUERY_TRAJECTORY_PREDICTION

Cross Support Service Management 31 Services Dependencies Service Agreement Service Service Package Service Configuration Profile Service Trajectory Prediction Service Service Package Service

Cross Support Service Management 32 Service Package Service Information  Coordinates use of configuration and trajectory information  Identifies start/stop time of services  Identifies types of services needed  Identifies sequencing of service events (as a function of time) Operations UM => CM  [ CREATE* | REPLACE* | DELETE | QUERY ]_SERVICE_PACKAGE  SELECT_ALTERNATE_SCENARIO  APPLY_NEW_TRAJECTORY CM => UM  SERVICE_PACKAGE_CANCELED (notify)  SERVICE_PACKAGE_MODIFIED (notify)  PROPOSE_SERVICE_PACKAGE*

Cross Support Service Management 33 Service Package Profiles ■Either a Space Link Session or a Retrieval Session. ■Space Link Session  Transfer Service Profile reference  Service Scenario ■Service Scenario  Trajectory Reference  Space Link Service request ■Space Link Service Request  Session start time and start time window, session duration …  Antenna Constraints : preferred antennas, required or excluded antennas  Event sequence reference ■Retrieval Session  Antenna reference  Transfer service profile reference  Access start and stop time

Cross Support Service Management 34 CSSM Standardized Messages CMUM Query Config Update Config Create Service Package New Trajectory Propose Service package Ground Stations Admin. Ground Stations Admin. Planning Auto Planning Manual Planning Orbit Comput. Ground Stations Control Spacecraft Monitoring & Control New Scenario Setup Action TM / TC over SLE Instantiate Sched.