ISO 17356-6:2006
(Main)Road vehicles — Open interface for embedded automotive applications — Part 6: OSEK/VDX Implementation Language (OIL)
Road vehicles — Open interface for embedded automotive applications — Part 6: OSEK/VDX Implementation Language (OIL)
ISO 17356-6:2006 describes the OSEK Implementation Language (OIL) concept for the description for ISO 17356 real-time systems, capable of multitasking and communications, which can be used for motor vehicles. It is not a product description that relates to a specific implementation.
Véhicules routiers — Interface ouverte pour applications automobiles embarquées — Partie 6: Language d'exécution OSEK/VDX (OIL)
General Information
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 17356-6
First edition
2006-01-15
Road vehicles — Open interface for
embedded automotive applications —
Part 6:
OSEK/VDX Implementation Language
(OIL)
Véhicules routiers — Interface ouverte pour applications automobiles
embarquées —
Partie 6: Language d'exécution OSEK/VDX (OIL)
Reference number
©
ISO 2006
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO 2006
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2006 – All rights reserved
Contents Page
Foreword. iv
0 Introduction . v
0.1 General remarks. v
0.2 Motivation. v
1 Scope . 1
2 Normative references . 1
3 Language Definition . 1
3.1 Preamble. 1
3.2 General concept. 2
4 ISO 17356-6 object definitions. 5
4.1 Rules . 5
4.2 ISO 17356-6 objects, standard attributes and references . 6
5 Definition of a particular implementation. 25
5.1 General. 25
5.2 Attribute types. 25
5.3 Reference Types . 27
5.4 Multiple values . 27
5.5 Example . 27
6 Syntax and default definition. 29
6.1 ISO 17356-6 syntax . 29
6.2 Default definition of ISO 17356-6 objects and standard attributes. 35
7 Description of the ISO 17356-6 objects . 46
Annex A (informative) Generator hints . 47
Bibliography . 48
Index. 49
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 17356-6 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3,
Electrical and electronic equipment.
ISO 17356 consists of the following parts, under the general title Road vehicles — Open interface for
embedded electronic equipment:
⎯ Part 1: General structure and terms, definitions and abbreviated terms;
⎯ Part 2: OSEK/VDX specifications for binding OS,COM and NM;
⎯ Part 3: OSEK/VDX Operating System (OS);
⎯ Part 4: OSEK/VDX Communication (COM);
⎯ Part 5: OSEK/VDX Network Management (NM);
⎯ Part 6: OSEK/VDX Implementation Language (OIL).
iv © ISO 2006 – All rights reserved
0 Introduction
0.1 General remarks
This part of ISO 17356 refers to ISO 17356-2, ISO 17356-3 and ISO 17356-4. For a better understanding of
this document, the reader should be familiar with the contents of these other specifications.
0.2 Motivation
To reach the goal of portable software, this part of ISO 17356 defines a way to describe the configuration of
an application.
This part of ISO 17356 only addresses a single central processing unit (CPU) in an electronic control unit
(ECU), not an ECU network.
Figure 1 — Example of development process for applications
Figure 1 shows an example of a development process for applications.
The ISO 17356-6 description may be handwritten or generated by a system configuration tool. There can be
several ISO 17356-6 files, e.g.:
⎯ files which contain CPU-specific configuration items (created by the supplier); and
⎯ files which contain configuration items for the entire network (provided by the OEM).
Sub-systems delivered in source code are compiled together with the application; others delivered as a library
are integrated by the linker.
INTERNATIONAL STANDARD ISO 17356-6:2006(E)
Road vehicles — Open interface for embedded automotive
applications —
Part 6:
OSEK/VDX Implementation Language (OIL)
1 Scope
This document describes the OSEK Implementation Language (OIL) concept for the description for ISO 17356
real-time systems, capable of multitasking and communications, which can be used for motor vehicles. It is
not a product description that relates to a specific implementation.
General conventions, explanations of terms and abbreviations are compiled in a glossary, which is part of
ISO 17356-1.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO 9899, Programming languages — C
ISO 17356-1, Road vehicles — Open interface for embedded automotive applications — Part 1: General
structure and terms, definitions and abbreviated terms
ISO 17356-2, Road vehicles — Open interface for embedded automotive applications — Part 2: OSEK/VDX
specifications for binding OS, COM and NM
ISO 17356-3, Road vehicles — Open interface for embedded automotive applications — Part 3: OSEK/VDX
Operating System (OS)
ISO 17356-4, Road vehicles — Open interface for embedded automotive applications — Part 4: OSEK/VDX
Communication (COM)
ISO 17356-5, Road vehicles — Open interface for embedded automotive applications — Part 5: OSEK/VDX
Network Management (NM)
3 Language Definition
3.1 Preamble
The goal of this part of ISO 17356 is to provide a method to configure an application inside a particular CPU.
This means for each CPU there is one ISO 17356-6 description.
All system objects are described using ISO 17356-6 objects.
3.2 General concept
The ISO 17356-6 description of the application is considered to be composed of a set of ISO 17356-6 objects.
A CPU is a container for these objects.
This part of ISO 17356 defines standard types for its objects. Each object is described by a set of attributes
and references. This part of ISO 17356 defines explicitly all standard attributes for each ISO 17356-6 object.
Each implementation can define additional implementation-specific attributes and references. It is possible
only to add attributes to existing ISO 17356-6 objects. Creating new ISO 17356-6 objects, or other changes to
the grammar, are not allowed. All non-standard attributes (optional attributes) are considered to be fully
implementation-specific and have no standard interpretation. Each implementation can limit the given set of
values for attributes (e.g. restrict the possible value range for priorities).
3.2.1 ISO 17356-6 file structure
The ISO 17356-6 description contains two parts — one part for the definition of standard and
implementation-specific features (implementation definition), and another for the definition of the structure of
the application located on the particular CPU (application definition).
The ISO 17356-6 description consists of one main ISO 17356-6 file that can refer to included files (see 3.2.9).
3.2.2 Syntax
The grammar rules for an ISO 17356-6 file are presented in the document using a notation similar to the
Backus-Naur Form (BNF) [1, 2], see 6.1.
All keywords, attributes, object names, and other identifiers are case-sensitive.
++
Comments in the BNF notation are written as C -style comments.
3.2.3 ISO 17356-6 versions
Two ISO 17356-6 sets of objects and standard attributes are defined:
⎯ Full set of objects and standard attributes: ISO 17356-3 and full-featured ISO 17356-4, supporting the
conformance classes BCC1, BCC2, ECC1, ECC2, CCCA, CCCB, CCC0, CCC1.
⎯ Subset of objects and standard attributes: ISO 17356-3 with internal communication only, supporting the
conformance classes BCC1, BCC2, ECC1, ECC2, CCCA, CCCB.
Refer to ISO 17356-3 and ISO 17356-4 for the features available with each of the abovementioned
conformance classes.
3.2.4 Implementation definition
For each ISO 17356-6 object, the implementation definition defines all attributes and their properties for a
particular implementation.
The implementation definition shall be present in the ISO 17356-6 description and have to contain all standard
attributes, which are listed in 4.2. The value range of those attributes may be restricted. Attribute definition is
described in clause 5.
Additional attributes and their properties can be defined for the objects for a particular implementation.
Additional attributes are optional.
2 © ISO 2006 – All rights reserved
The include mechanism (see 3.2.1) can be used to define the implementation definition as a separate file.
Thus, corresponding implementation definition files can be developed and delivered with particular
implementations and then included with the application definition in user's ISO 17356-6 files.
An implementation of ISO 17356-6 shall support either all objects and standard attributes or a specific subset
defined in 6.2.1.
3.2.5 Application definition
The application definition comprises a set of objects and the values for their attributes. Except for the
ISO 17356-3, ISO 17356-4 and ISO 17356-5 objects, the application definition can contain more than one
ISO 17356-6 object of a particular type.
Each object is characterized by a set of attributes and their values. No attribute may appear that is not defined
in the implementation definition. Attribute values shall comply with the attribute properties specified in the
implementation definition.
Attributes that take a single value shall only be specified o
...








Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.