sois api
DESCRIPTION
SOIS API. CCSDS SOIS Noordwijk 2009 F. Torelli ESA-ESTEC. Background. SOIS Services define conceptual service primitives SOIS Services implementation is dependent on: the HW platform (in particular the sub-network) the OS the programming language the programming model - PowerPoint PPT PresentationTRANSCRIPT
Felice Torelli TEC-SWS 1
SOIS API
CCSDS SOIS
Noordwijk 2009
F. Torelli ESA-ESTEC
Felice Torelli TEC-SWS 2
Background
• SOIS Services define conceptual service primitives
• SOIS Services implementation is dependent on:– the HW platform (in particular the sub-network)– the OS– the programming language– the programming model– the Application SW development framework (if used)
• Different SW supplier can implement the same SOIS services in different ways and still be compliant to the standard
Felice Torelli TEC-SWS 3
Requirements (ESA)
• SOIS Service users should be independent from the specific SW implementation
• SOIS Service users should be independent from the specific HW platform
• The definition of the Avionics Architecture should use the SOIS Services as a building block
Felice Torelli TEC-SWS 4
Objective (1/2)
• To identify a common baseline (SW context) regarding:– OS (e.g. RTEMS)– Programming language (e.g. C)– Programming model (e.g. *.indication as call-back function)
• To specify the SOIS Service API in a concrete way (SW/SW ICD)
• To leave open the SOIS Services SW implementation
Felice Torelli TEC-SWS 5
Objective (2/2)
Com
munica
tion M
anagem
ent
CMD & DataAcquisitionServices
Time AccessService
File &Packet Store
Services
Message TransferService
DeviceEnumeration
Service
Packet Service
MemoryAccessService
SynchronisationService
DeviceDiscoveryService
Test Service
Datalink Convergence Protocols
ApplicationLayer
ApplicationSupport Layer
TransferLayer
Subnetwork Layer
Network Protocol
Transport Protocol
Milbus SpaceWire CAN Wireless
MissionSpecific
Applications
Open implementation
Open implementation
Standard API
Standard API
Open point (P&P?)
Felice Torelli TEC-SWS 6
Way Forward?
• Outcome of prototyping activity:– Identification of the baseline SW context– API ICD proposal
• Iteration with SW suppliers (industry) to assess the API ICD
• To make the API ICD an applicable standard for the specific SW context (e.g. OS, language, etc)
• Different SW contexts will require new iterations and potentially different API ICD
Felice Torelli TEC-SWS 7
SOIS API
CCSDS SOIS
Noordwijk 2009
F. Torelli ESA-ESTEC