Octave A Portable, Distributed, Opened Platform for Interoperable Monitoring Services

1
OctaveA Portable, Distributed, Opened Platform
for Interoperable Monitoring Services

• Christophe Pipo, CS
• Evelyne Cortiade, CNES

2
Plan

• Spatial context
• Results of studies for Octave design
• Octave telemetry treatment concepts
• Octave platform architecture
• Client applications
• Conclusion

3
Spatial telemetry context

• Many specific programs and tools to handle
  telemetry and telecommands
• Why such a wide range ?
• Very few standards (descriptions, monitoring,
  communications)
• Different OS on machine
• Potential solution is
• To use standards
• Portability
• Interoperability
• Octave is driven by these constraints to be able
  to be integrated into many contexts

4
From real life to abstract concepts to Octave

• CNES (CST/SGE) study  control centers
  harmonization in 06/2005
• A good starting point to design Octave

5
Functionnal view of telemetry treatment

• Acquisition extracts telemetry from telemetry
  provider
• Preprocessing apply transformations, check etc.
• Decoding calculate human-reading parameters
• Distribution dispatch values to registered
  clients
• Archiving store telemetry for further replay

6
Components view of telemetry treatment

• Creation of  glue object  TMFlow
• Multi-user-level object view
• At Basic user level TMFlow is the tool to
  handle telemetry
• At Advanced user level, under the hood of TMFlow
  AcquisitionChain, OctaveDecom and Dispatcher.
• User friendly customizable objects with distant
  MMI

7
Plan

• Now, lets have a look on acquisition function

8
Acquisition Stream preprocessing

• Often, specific operations are needed before
  decoding
• Multiplexing
• Demultiplexing
• Checks
• Distribute raw telemetry with multi-clients
  ports
•  AcquisitionChain  is a combination of
   Packetizer 
• A Packetizer, with inputs and outputs, allows to
  route, to transform and to distribute streams.

AcquisitionChain graphical editor
9
Acquisition Customizable Packetizer as base
component

• A Packetizer has a plugin-architecture
• A Packetizer consists in
• One or more interconnected customizable routers
  route data from inputs to outputs
• Inputs connected to an URL
• Outputs open a multi-clients port
• Filters customizable filters
• Readers customizable readers

10
Plan

• Now, lets have a look on decoding function

11
Decoding engine generation

• Engine dynamically generated from DEDSL-XML
  description with JavaAssist technology

BEST (CNESESRIN) DEDSL Editor
Semantic
Syntax
Octave Semantic Editor
12
Plan

• Now, lets have a look on distribution function

13
Distributing function in Octave

• Currently, CORBA registration service allows
  client to receive parameters
• Soon, this function will be delegated to a MOM
  (Message Oriented MiddleWare) according to CCSDS
  SMC architecture

14
Octave global architecture flexibility

• All monitoring functions are embedded in a
  distributed CORBA flexible platform. Main CORBA
  components are
• The OctaveServer component homes
• TMContext that contains DEDSL-XML descriptions
• The running TMFlows
• The TMTCBank offers services to store and to
  extract telemetry from a database.
• The UserManagement component offers
  authentication and user management services

Mono machine deployment
Multi machine deployment
15
CORBA Octave services interoperable open
architecture

• Octave provides interoperable services described
  in IDL (Interface Definition Language of OMG)

• UserManagement services
• Authentification
• Profiles
• Itinerant environments
• Monitoring services
• Loading DEDSL-XML
• Customizing Acquisition Chain
• Creating TMFlow (real time and replay)
• Piloting TMFlow
• Archiving

• External systems can connect and use the platform

16
Example of client Platform Manager

• Friendly application to administrate remotely the
  whole platform

17
Example of client Visualization client
18
Conclusion

• Octave customers are
• JASON-2
• CRYOSAT
• MeghaTropique
• PHARAO
• PICARD
• Drawback
• DEDSL-XML is not enough to describe a whole
  Satellite with telecommands and telemetry. XTCE,
  for example, would be suitable ?
• Advantages portability, interoperability,
  genericity, flexibility
• Current works
• Octave is used to develop CCSDS SMC prototype
• Future integration of telecommands services