ISO 17356-5:2006
(Main)Road vehicles — Open interface for embedded automotive applications — Part 5: OSEK/VDX Network Management (NM)
Road vehicles — Open interface for embedded automotive applications — Part 5: OSEK/VDX Network Management (NM)
ISO 17356-5:2006 defines a set of services for node monitoring (NM). NM consists of the following: interface to interact with the Application Programming Interface(API); algorithm for node monitoring; internal interfaces (NM COM, etc.); algorithm for transition into sleep mode; and NM protocol data unit (NMPDU).
Véhicules routiers — Interface ouverte pour applications automobiles embarquées — Partie 5: Gestion du réseau OSEK/VDX (NM)
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 17356-5
First edition
2006-02-01
Road vehicles — Open interface for
embedded automotive applications —
Part 5:
OSEK/VDX Network Management (NM)
Véhicules routiers — Interface ouverte pour applications automobiles
embarquées —
Partie 5: Gestion du réseau OSEK/VDX (NM)
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. v
0.2 System status. v
0.3 Remarks by the authors. v
0.4 Summary. vi
1 Scope . 1
1.1 Embedding of the Network Management (NM) . 1
1.2 Adaptation to bus protocol specific requirements . 1
1.3 Adaptation to node resources. 1
1.4 Adaptation to hardware-specific requirements . 1
1.5 Station management (system-specific algorithms) . 2
1.6 Philosophy of node monitoring. 2
2 Direct Network Management . 3
2.1 Concept. 3
2.2 Algorithms and behaviour . 11
3 Indirect Network Management. 54
3.1 General. 54
3.2 Concept. 54
3.3 Algorithms and behaviour . 60
4 System generation and API . 75
4.1 Overview . 75
4.2 Conventions for service description . 77
4.3 General data types. 79
4.4 Common services. 79
4.5 Services for direct NM. 89
4.6 Services for indirect NM. 92
5 Impacts upon OS, COM and the data link layer. 93
5.1 Error codes. 93
5.2 Common impacts. 93
5.3 Impacts from direct NM. 97
5.4 Impacts from indirect NM. 98
Annex A (informative) Implementation proposal (direct NM) . 101
Index. 117
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-5 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 automotive applications:
— 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
There is an increasing tendency for electronic control units (ECUs) made by different manufacturers to be
networked within vehicles by serial data communication links.
Therefore, standardization of basic and non-competitive infrastructure in ECUs aims at avoiding the design of
unnecessary variants and saving development time.
In the scope of OSEK/VDX cooperation, the Network Management system (NM) provides standardized
features which ensure the functionality of inter-networking by standardized interfaces.
The essential task of NM is to ensure the safety and the reliability of a communication network for ECUs.
In a vehicle, a networked ECU is expected to provide certain features:
⎯ each node accessible for authorized entities;
⎯ maximum tolerance with regard to temporary failures; and
⎯ support of network-related diagnostic features.
At a basic configuration stage, NM implementations complying with OSEK specifications are implemented in
all networked nodes. This implies a solution for NM which can be implemented throughout the broad range of
available hardware offered in today’s ECUs.
Therefore, the status of the network is recorded and evaluated uniformly at all ECUs at intervals. Thus, each
node features a determined behaviour as regards the network and the application concerned.
NM offers two alternative mechanisms for network monitoring:
⎯ indirect monitoring by monitored application messages; and
⎯ direct monitoring by dedicated NM communication using token principle.
However, the use of these mechanisms is up to the system responsible. Processing of information collected
by these mechanisms is in accordance with requirements as regards to the entire networked system.
0.2 System status
In view of the application, NM comprises two standardized interfaces:
⎯ Software: Application program <-> NM
⎯ Network behaviour: Station <-> Communication medium
The resulting entire system is open. Thus, it can adapt to new requirements within the restrictions defined by
the system design.
0.3 Remarks by the authors
This part of ISO 17356 describes the concept and the API of a Network Management, which can be used for
ECUs in vehicles. It is not a product description which relates to a specific implementation.
General conventions, explanations of terms and abbreviations have been compiled in ISO 17356-1.
0.4 Summary
In order to achieve the essential task of a network monitoring, i.e. ensure safety and reliability of a
communication network for ECUs, NM describes node-related (local) and network-related (global)
management methods. The global NM component is optional. However, it requires a minimum local
component to be operational.
Therefore, the following services are provided:
⎯ initialization of ECU resources, e.g. network interface;
⎯ start-up of network;
⎯ providing network configuration;
⎯ management of different mechanisms for node monitoring;
⎯ detecting, processing and signalling of operating states for network and node;
⎯ reading and setting of network- and node-specific parameters;
⎯ coordination of global operation modes (e.g. network wide sleep mode); and
⎯ support of diagnosis.
There are two main parts within the document: Direct Network Management described in Clause 2 and
Indirect Network Management described in Clause 3. Both clauses describe the concepts, algorithms and
behaviour.
Subclause 2.1, Concept, describes the fundamental aspects of the configuration management, the operating
states and operating state management.
Subclause 3.3, Algorithms and behaviour, describes the protocol used for communication between nodes.
Clause 4 describes the API (Application Programming Interface) comprising the pure specification of the
services offered for both direct and indirect NM. Input and output data, the functional description,
particularities, etc. are described for each service. Furthermore, System generation services are described
within this clause.
Clause 5 describes the impacts on the infrastructure of ISO 17356 and gives a brief description of all
requirements for COM, OS and the data link layer for both direct and indirect NM.
vi © ISO 2006 – All rights reserved
INTERNATIONAL STANDARD ISO 17356-5:2006(E)
Road vehicles — Open interface for embedded automotive
applications —
Part 5:
OSEK/VDX Network Management (NM)
1 Scope
1.1 Embedding of the Network Management (NM)
NM defines a set of services for node monitoring. Figure 1 shows how the NM is embedded into a system and
that the NM shall be adapted to specific requirements of the bus system used or to the resources of the nodes.
NM consists of the following:
⎯ interface to interact with the Application Programming Interface(API);
⎯ algorithm for node monitoring;
⎯ internal interfaces (NM <-> COM, etc.);
⎯ algorithm for transition into sleep mode; and
⎯ NM protocol data unit (NMPDU).
1.2 Adaptation to bus protocol specific requirements
Adaptation to bus protocol specific requirements consists of the following:
⎯ CAN, VAN, J1850, K-BUS, D2B, etc.;
⎯ error handling, e.g. bus-off handling in a CAN, transmission line error handling; and
⎯ interpretation of the status information, e.g. overrun or error active/passive in a CAN.
1.3 Adaptation to node resources
Adaptation to node resources consists of the following:
⎯ scaling of the NM as a requirement of the node; and
⎯ application-specific usage of the NM services.
1.4 Adaptation to hardware-specific requirements
This consists of adaptation to a protocol circuit and a physical layer circuit, e.g. switching the bus hardware to
one of the possible
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.