30.12.2014 Views

document title / titre du document TRP W ORK PLAN ... - emits - ESA

document title / titre du document TRP W ORK PLAN ... - emits - ESA

document title / titre du document TRP W ORK PLAN ... - emits - ESA

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>TRP</strong> Work Plan 2005-2007<br />

Description of Activities<br />

TEC-SB/7935/dc<br />

12/Feb/09<br />

<strong>TRP</strong> Reference:<br />

Title:<br />

T609-26ED<br />

OCP-IP building blocks for Space-SoC<br />

"Open Cores Protocol" (OCP) is an emerging standard set of requirements and tools that are being successfully applied to<br />

facilitate IP Cores reuse, easier integration and compatibility between different on-chip bus systems (CAN, AMBA, SpaceWire,<br />

I2C, etc). The activity would be about designing OCP-IP mo<strong>du</strong>les for our existing <strong>ESA</strong> IP Cores, so future space-SoC can<br />

make use of <strong>ESA</strong> OCP compliant building blocks.<br />

Deliverables:<br />

OCP-IP mo<strong>du</strong>les architecture.<br />

Current TRL: TRL2 Target TRL: TRL3 Application Need/Date: TRL4 by 2007<br />

All spacecraft data handling systems /<br />

Application/Mission: Contract Duration: 10 months<br />

Space-SoC<br />

SW Clause : - Dossier0 Ref.: T-7799<br />

Consistency with Harmonisation<br />

On-Board Payolad Data Processing<br />

Roadmap and Conclusions:<br />

<strong>TRP</strong> Reference: T609-27ED<br />

Title:<br />

Standardisation of spacecraft onboard communication services<br />

Until recently, standardisation efforts within the realm of onboard spacecraft have concentrated on physical interfaces and<br />

associated protocols. Such activities have been handled by the Consultative Committee for Space data standardisation (<br />

CCSDS) or the ECSS. Within these standardisation bodies emphasis is now being placed on the definition of communication<br />

services and protocols which allow independence from the underlying hardware and thus open up the possibility for software<br />

re-use across multiple missions. This has the potential to significantly re<strong>du</strong>ce spacecraft development times and associated<br />

costs. As part of the ongoing work of the Spacecraft Onboard Interface Services (SOIS) group within the CCSDS,<br />

recommendations for a suite of communication services are well advanced and will be made available in draft form before the<br />

end of 2006. In order achieve final publication, the draft recommendations must be prototyped and verified in a representative<br />

spacecraft environment. This activity will cover there required prototyping, integration and test on an existing <strong>ESA</strong> test-bed<br />

infrastructure. Results will be incorporated by <strong>ESA</strong> into the final CCSDS recommendation which will subsequently be adopted<br />

by <strong>ESA</strong> for potential application to all spacecraft projects. The software should take the form of reference libraries which can<br />

be made available for use by <strong>ESA</strong> projects.<br />

Deliverables:<br />

Software implementing the CCSDS defined services and protocols<br />

Current TRL: TRL1 Target TRL: TRL3 Application Need/Date: TRL4 by 2007<br />

Application/Mission: All spacecraft data handling systems Contract Duration: 12 months<br />

SW Clause : Operational SW Dossier0 Ref.:<br />

Consistency with Harmonisation<br />

Roadmap and Conclusions:<br />

On-Board Payolad Data Processing<br />

Page 131 of 227

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!