《ISO-17356-5-2006.pdf》由会员分享，可在线阅读，更多相关《ISO-17356-5-2006.pdf（124页珍藏版）》请在三一文库上搜索。
1、 Reference number ISO 17356-5:2006(E) ISO 2006 INTERNATIONAL STANDARD ISO 17356-5 First edition 2006-02-01 Road vehicles Open interface for embedded automotive applications Part 5: OSEK/VDX Network Management (NM) Vhicules routiers Interface ouverte pour applications automobiles embarques Partie 5:
2、Gestion du rseau OSEK/VDX (NM) ISO 17356-5:2006(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes 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
3、 performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes 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 t
4、his 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 Cen
5、tral 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
6、at the address below or ISOs 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 copyrightiso.org Web www.iso.org Published in Switzerland ii ISO 2006 All rights reserved ISO 17356-5:2006(E) ISO 2006
7、All rights reserved iii 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
8、 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 Algorit
9、hms 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.
10、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 ISO 17356-5:2006(E) iv ISO 2006 All rights reserved Foreword ISO (the International Organization for Standardization) is a worldwide federation o
11、f 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. In
12、ternational 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
13、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
14、 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 Committe
15、e 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: OSE
16、K/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) ISO 17356-5:2006(E) ISO 2006 All rights reserved v 0 Introduction 0.1 General There is an
17、 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 d
18、evelopment 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
19、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 s
20、pecifications 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 todays ECUs. Therefore, the status of the network is recorded and evaluated uniformly at all ECUs at intervals. Thus, each node fe
21、atures 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
22、 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
23、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
24、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. -,-,- ISO 17356-5:2006(E) vi ISO 2006 All rights reserved 0.4 Summary In order to achieve the essenti
25、al 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
26、, 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 set
27、ting 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 cl
28、auses 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.
29、 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
30、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. -,-,- INTERNATIONAL STANDARD ISO 17356-5:2006(E) ISO 2006 All rights reserved 1 R
31、oad 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 spe
32、cific 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 protoco
33、l 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
34、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 Thi
35、s consists of adaptation to a protocol circuit and a physical layer circuit, e.g. switching the bus hardware to one of the possible physically power save modes. -,-,- ISO 17356-5:2006(E) 2 ISO 2006 All rights reserved 1.5 Station management (system-specific algorithms) There are a variety of additio
36、nal tasks involved in coordinating a network. These are not described in ISO 17356, since they are system-dependent. Hence, these tasks are done by the application, e.g. by a module called station management. 1.6 Philosophy of node monitoring Node monitoring is used to inform the application about t
37、he nodes on the network. Thus, the application can check with the appropriate service if all stations required for operation are present on the network. Key 1 API 2 several buses connected to one Controller 3 interface to DLL, COM-specific, protocol-specific 4 interface to COM Interaction Layer 5 st
38、ation management (outside the scope of ISO 17356) 6 algorithms 7 protocol-specific management algorithms Figure 1 Responsibility of interface and algorithms ISO 17356-5:2006(E) ISO 2006 All rights reserved 3 2 Direct Network Management 2.1 Concept 2.1.1 Node monitoring 2.1.1.1 General NM supports th
39、e direct node monitoring by dedicated NM communication. A node is a logical whole to which a communication access is possible. A microprocessor with two communication modules connected to two different communication media (e.g. low speed CAN and a high-speed CAN) represents two nodes from the NM poi
40、nt of view. The rate of the NM communication is controlled across the network (minimization of bus load and consumption of resources) and the messages are synchronized (avoiding negative effects on application data by message bursts). Every node is actively monitored by every other node in the netwo
41、rk. For this purpose, the monitored node sends an NM message according to a dedicated and uniform algorithm. Direct node monitoring requires a network-wide synchronization of NM messages. For this purpose, a logical ring is used. 2.1.1.2 Logical ring 2.1.1.2.1 General In a logical ring, the communic
42、ation sequence is defined independently from the network structure. Therefore, each node is assigned a logical successor. The logically first node is the successor of the logically last node in the ring. Thus, the decentralized control of the overall amount of NM messages is ensured and the bus load
43、 due to these messages is determined. The communication sequence of the logical ring synchronizes NM communication. Any node shall be able to send NM messages to all other nodes and receive messages from them. Key 1 node 2 Electronic Communication Unit (ECU) 3 communication media 1 4 communication m
44、edia 2 Figure 2 Infrastructure of the NM (logical ring), example with two buses ISO 17356-5:2006(E) 4 ISO 2006 All rights reserved 2.1.1.2.2 Principle The direct NM transmits and receives two types of messages to build the logical ring. An alive message introduces a new transmitter to the logical ri
45、ng. A ring message is responsible for the synchronized running of the logical ring. It will be passed from one node to another (successor) node. Receive alive message: Interpretation as transmitter-related registration to the logical ring. Receive ring message: Interpretation as transmitter-specific
46、 alive signal and synchronization to initiate transmission of own NM message according to the logical ring algorithm. Time-out on ring message: Interpretation as transmitter-specific breakdown. 2.1.1.2.3 State of a node A monitoring node is able to distinguish two states of a monitored node: node pr
47、esent ? specific NM message received (alive or ring); node absent ? specific NM message not received during time-out. A monitoring node is able to distinguish two states of itself: present or not mute ? specific NM message transmitted (alive or ring); absent or mute ? specific NM message not transmi
48、tted during time-out. 2.1.2 Addressing 2.1.2.1 Status The status of nodes and of the network shall be acquired and evaluated uniformly at intervals. For this purpose, all nodes shall communicate via their NM. The NM communication is independent of the underlying bus protocol. Each node can communica
49、te unidirectionally and address-related with any other node of the network. Therefore, individual and group addressing of nodes is required. 2.1.2.2 Node addressing 2.1.2.2.1 General Address-related communication takes into account receiver and emitter. Each node has a unique identification which is known in the networ