A DYNAMIC MULTIPROTOCOL INTERFACE FOR TT

1
A DYNAMIC MULTI-PROTOCOL INTERFACEFOR TTC
SATELLITEBASEBAND PROCESSOROlivier
RiberonSpace Division Senior Manager
SalesJacques DavaineSpace Division Senior
Manager - Operations
2
ENERTEC
n ENERTEC designs and produces high-end data
storage, acquisition and processing systems for
aerospace, defense and derived markets,
... its strategy
focuses on seven core markets.
aerospace defense mission video/data
recorders mission debriefing and analysis systems
security on-board video-surveillance and
entertainment systems exploitation systems
space ground segment satellite ground control
systems and equipment satcom, science, and
military applications
3
GROUND SPACE SEGMENT

• ENERTEC Space Division offers competitive
  solutions to Customer needs, from the start of
  satellite integration up to in-orbit satellite
  operation

Satellite AIT
TTC Service
Payload Service
4
EQUIPMENT TTC 3801
n ENERTEC Space Division provides a wide product
range with modular hardware and software
architecture based on real-time technology

• High data rate base band processor for Science
  and Earth Observation
• Compact and cost effective Satcom base band
  processor
• Tracking receiver
• Satellite and Ground Station test equipment
• Specific ranging processor (Intelsat Burst Tone
  Ranging, etc )
• ITCU100 replacement solution
• Data recording and playback unit
• Full compatibility with most deployed satellites
• Multiple-SCC software interfacing using dynamic
  protocol server

5
Dynamic Multi-Protocol Interface

• Old Way Protocol Interface hard-coded
  everywhere in software!

• Storage format is protocol dependent

• Inter-task communication is protocol dependent

• Networking task is limited to data transfer

• Telemetry data is encapsulated into the protocol
  format at the demodulation level

• Protocol can not be changed dynamically
• New protocol implementation involves modification
  of most software modules

6
Dynamic Multi-Protocol Interface

• What is defined under a Protocol ?
• Services
• Data interfaces
• Control interface
• Monitoring interface
• User interface

7
Dynamic Multi-Protocol Interface

• New Way Multi-Protocol Mapping using Protocol
  Client/Server

• Configuration file stored in Flash

• Networking tasks are mapped into the protocol
  server

CONFIG.BIN Power-up

• Dynamic selection

I/O DRIVER
HDLC
SRAM.BIN User interface MC interface
PROTOCOL
I/O DRIVER
CLIENT/
TCP-IP
SERVER

• MC and User Interface automatically adapt to
  protocol selection

I/O DRIVER
RS232
8
Dynamic Multi-Protocol Interface

• Protocol Client/Server interfaces to other
  Servers via Callback/Function pointer interface
• Demodulator Server sends back pertinent data only

• Specific protocol information is located in the
  protocol client

• Telemetry data is transmitted by the demodulator
  server in a generic format

• Callback/function pointer manages connection to
  the demodulator server

• Demodulator server is protocol-independent

9
Dynamic Multi-Protocol Interface

• Protocol Client/Server interfaces in Real-Time to
  other Servers via Callback/Function pointer
  interface
• Data is stored on Hard Disk For Offline services

• Real-time and protocol tasks are independent

• Data storage is protocol-independent

• All services interface to the protocol
  client/server in a unified manner

10
Dynamic Multi-Protocol Interface

• Impact of the multi-protocol approach on the user
  interface

• Allocate protocols, I/O ports, security to each
  service (TM1, TM2, TM3, TC1, TC2, RG1, RG2, )

• Define protocol parameters for each service

11
Dynamic Multi-Protocol Interface

• Impact of the multi-protocol approach on the user
  interface
• Front panel modification
• Monitoring Control modification
• Service level modification

12
Dynamic Multi-Protocol Interface

• Dynamic switching

Current Interface
Next Interface
13
Dynamic Multi-Protocol Interface

• Consequences of the Dynamic Protocol Selection
• User interface switches on-the-fly
• Could be confusing to the operators
• Monitoring Control switches on-the-fly
• Requires correct handling of the switch by the
  MC system
• Data Interface switches on-the-fly
• Requires correct handling of the switch by the
  SCC and other data analysis systems

• CURRENT IMPLEMENTATION REQUIRES REBOOTING FOR
  PROTOCOL SELECTION TO TAKE EFFECT

• COULD BE MADE FULLY DYNAMIC IF SATELLITE
  OPERATORS TAKE NECESSARY STEPS IN MC AND SCC
  SOFTWARE

14
Dynamic Multi-Protocol Interface

• Benefits
• System more flexible
• One unit can be used in support to multiple
  missions by different Space Agencies
• Istrac unit was used by CSA in support to SciSat
  mission
• CSA unit will be used by CNES in support to
  Helios mission
• System more cost effective
• New protocols can be added with reduced cost,
  delay and risks
• Future upgrades
• Capability to integrate external software in a
  well defined API environment

15
Dynamic Multi-Protocol Interface

• Link to SLE development
• Multi-Protocol Interface is an interim solution
  before a wide availability of SLE compatible
  ground stations
• Multi-Protocol Interface will remain a way to
  combine the SLE support and the support of legacy
  ground stations in a single baseband equipment