OSEK/VDX
Binding Specification
OSEK/VDX BD 1.4.2 © by OSEK 3
Motivation
• High, recurring expenses in the development and variant management of non-
application related aspects of control unit software.
• Incompatibility of control units made by different manufacturers due to different
interfaces and protocols.
Goal
Support of the portability and reusability of the application software by:
• Specification of interfaces which are abstract and as application-independent as
possible, in the following areas: real-time operating system, communication and
network management.
• Specification of a user interface independent of hardware and network.
• Efficient design of architecture: The functionality shall be configurable and scaleable, to
enable optimal adjustment of the architecture to the application in question.
• Verification of functionality and implementation of prototypes in selected pilot projects.
Advantages
• Clear savings in costs and development time.
• Enhanced quality of the software of control units of various companies.
• Standardised interfacing features for control units with different architectural designs.
• Sequenced utilisation of the intelligence (existing resources) distributed in the vehicle,
to enhance the performance of the overall system without requiring additional hardware.
• Provides independence with regards to individual implementation, as the specification
does not prescribe implementation aspects.
Scope of the document :
As the standardisation of requirements that are applicable to different OSEK/VDX
specifications should not be replicated within the different specifications, this document is
therefore set-up to collate all requirements that are owned by the different specifications.
This document also provides an overall description of the OSEK/VDX specifications set.
This binding specification is therefore a ‘normative’ document and intention is laid to prevent
a divergence of the OSEK/VDX specifications by giving the possibility to refer to a single
binding document.
