The standard is divided into six primary parts, each addressing a critical layer of the embedded software ecosystem:
| Part | Title | Content | |------|-------|---------| | | General overview and glossary | Definitions, terminology, scope | | ISO 17356-2 | OSEK/VDX specifications – OS | Real-time operating system (tasks, events, alarms, resources, interrupts) | | ISO 17356-3 | OSEK/VDX specifications – COM | Communication stack for internal ECU messages (databases, signals, interactions) | | ISO 17356-4 | OSEK/VDX specifications – NM | Network management (direct NM, indirect NM, monitoring) | | ISO 17356-5 | OSEK/VDX specifications – OIL | OSEK Implementation Language (configuration language) | | ISO 17356-6 | OSEK/VDX specifications – Binding | Language binding (C, assembly) and OSEK run-time interface (ORTI) for debugging | iso 17356
By establishing standardized Application Program Interfaces (APIs), ISO 17356 ensures that software modules can be ported across different processor families, significantly reducing development costs and increasing system reliability. The Core Structure of ISO 17356 The standard is divided into six primary parts,
The adoption of ISO 17356 had a significant impact on the automotive industry: The standard aimed to define a set of
The International Organization for Standardization (ISO) recognized the need for a global standard that would enable interoperability, simplify design, and reduce costs. In response, the ISO 17356 standard was born.
The standard aimed to define a set of requirements for connectors, including their design, testing, and validation. The goal was to ensure that connectors used in vehicle electrical systems were compatible, reliable, and perform well under various environmental conditions.