OSEK/VDX
Open Systems and the Corresponding Interfaces
for Automotive Electronics
Page 1 © by OSEK/VDX NM Concept & API 2.5.2
OSEK/VDX
Network Management
Concept and Application Programming Interface
Version 2.5.3
26
th
July 2004
This document is an official release and replaces all previously distributed documents. The OSEK
group retains the right to make changes to this document without notice and does not accept liability
for errors. All rights reserved. No part of this document may be reproduced, in any form or by any
means, without permission in writing from the OSEK/VDX steering committee.
OSEK/VDX
Open Systems and the Corresponding Interfaces
for Automotive Electronics
Page 2 © by OSEK/VDX NM Concept & API 2.5.2
Table of Contents
Introduction.................................................................................................................................3
Summary.....................................................................................................................................4
1. Scope of the OSEK Network Management ........................................................................5
2. Direct Network Management..............................................................................................7
2.1. Concept .......................................................................................................................7
2.1.1. Node Monitoring.................................................................................................7
2.1.2. Addressing ..........................................................................................................8
2.1.3. NM Infrastructure for Data Exchange ..............................................................10
2.1.4. 2.1.4.Standard Functionality.............................................................................10
2.1.5. Configuration Management ..............................................................................10
2.1.6. Operating Modes...............................................................................................13
2.1.7. Network Error Detection and Treatment ..........................................................14
2.1.8. Support of Diagnostic Application ...................................................................15
2.2. Algorithms and Behavior..........................................................................................15
2.2.1. Communication of the Network Management System.....................................15
2.2.2. NM Infrastructure for Data Exchange ..............................................................19
2.2.3. Standard Tasks..................................................................................................20
2.2.4. Configuration Management ..............................................................................23
2.2.5. Example: Skipped in the logical ring................................................................32
2.2.6. Example: Logical Successor.............................................................................33
2.2.7. Operating Mode ................................................................................................34
2.2.8. Fusion of Configuration Management and Operating Modes ..........................40
2.2.9. Alarms inside the Network Management .........................................................57
3. Indirect Network Management .........................................................................................60
3.1. Concept .....................................................................................................................61
3.1.1. Node Monitoring...............................................................................................61
3.1.2. Configuration-Management..............................................................................62
3.1.3. Standard Task....................................................................................................62
3.1.4. Monitoring Mechanisms...................................................................................63
3.1.5. Monitoring time-outs ........................................................................................65
3.1.6. Operating Modes...............................................................................................67
3.2. Algorithms and behavior...........................................................................................67
3.2.1. Configuration Management ..............................................................................67
3.2.2. Operating Mode ................................................................................................71
3.2.3. State Machine in SDL.......................................................................................73
OSEK/VDX
OSEK/VDX
Network Management
Concept and Application Programming
Interface
Page 2 © by OSEK/VDX NM Concept & API 2.5.2
4. System generation and API...............................................................................................85
4.1. Overview...................................................................................................................85
4.2. Conventions for Service Description........................................................................87
4.2.1. System Generation............................................................................................87
4.2.2. Type of Calls.....................................................................................................87
4.2.3. Error Characteristics .........................................................................................87
4.2.4. Structure of the Description..............................................................................88
4.3. General Data Types...................................................................................................89
4.4. Common services......................................................................................................89
4.4.1. Standard Functionality......................................................................................89
4.4.2. Configuration Management ..............................................................................92
4.4.3. Operating Modes and Operating Mode Management.......................................98
4.5. Services for direct NM............................................................................................102
4.5.1. Standard Functionality....................................................................................102
4.5.2. Operating Modes and Operating Mode Management.....................................102
4.5.3. Data Field Management..................................................................................103
4.6. Services for indirect NM.........................................................................................106
4.6.1. Standard functionality.....................................................................................106
4.6.2. Configuration Mangement..............................................................................106
5. Impacts upon OS, COM and the data link layer.............................................................107
5.1. Error Codes .............................................................................................................107
5.2. Common impacts ....................................................................................................108
5.2.1. Requirements of the data link layer ................................................................108
5.2.2. Requirements of OSEK Operating System (OSEK OS).................................110
5.3. Impacts from direct NM..........................................................................................111
5.3.1. Interface to the data link layer ........................................................................111
5.4. Impacts from indirect NM.......................................................................................112
5.4.1. Interface to OSEK Communication (OSEK COM)........................................112
6. History.............................................................................................................................115
7. Implementation proposal (direct NM) ............................................................................116
7.0.1. Overview of Internal Activities ......................................................................116
7.0.2. Specification of Internal Activities.................................................................119
7.0.3. NMPDU ..........................................................................................................124
7.0.4. Scalability .......................................................................................................129
7.1. Implementation proposal (indirect NM).................................................................131
7.1.1. Scalability .......................................................................................................131
7.1.2. Implementation hints ......................................................................................132
7.1.3. Summary of SDL state diagram graphical notation........................................134
7.2. Outlook ...................................................................................................................135
8. Index ...............................................................................................................................137
OSEK/VDX
OSEK/VDX
Network Management
Concept and Application Programming Interface
NM Concept & API 2.5.2 © by OSEK/VDX Page 3
Introduction
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 the OSEK/VDX co-operation, 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 has to be accessible for authorized entities
• maximum tolerance with regard to temporary failures
• support of network related diagnostic features.
At a basic configuration stage, NM implementations complying with OSEK specifications
must be 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 must be recorded and evaluated uniformly at all ECUs at
intervals. Thus each node features a determined behavior as regards the network and the
application concerned.
OSEK 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 must be in accordance with requirements as
regards to the entire networked system.
System status
In view of the application, NM comprises two standardized interfaces:
• Software: Application program <-> NM
• Network behavior: Station <-> Communication medium
The resulting entire system is open. Thus, it can adapt to new requirements within the
restrictions defined by the system design.
网络管理的本质目的就是保证ECU之间的网络可靠和安全的通信。
OSEK/VDX
OSEK/VDX
Network Management
Concept and Application Programming
Interface
Page 4 © by OSEK/VDX NM Concept & API 2.5.2
Remarks by the authors
This document 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 the
additional inter project "OSEK Overall Glossary" which is part of the OSEK Binding
Specification.
Summary
In order to achieve the essential task of a network monitoring, i.e.
• ensure safety and reliability of a communication network for ECUs,
OSEK 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 signaling 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)
• Support of diagnosis
There are two main parts within the document: Direct Network Management described by
Chapter 2 and Indirect Network Management described by Chapter 3. Both chapters describe
the concepts, the algorithms and behavior.
The Subsections Concept describe the fundamental aspects of the configuration management,
the operating states and operating state management.
The Subsections Algorithms and Behavior describes the protocol used for communication
between nodes.
Chapter 4 describes the Application Programming Interface comprising the pure specification
of the services offered by NM for both direct and indirect. Input and output data, the
初始化网路资源
启动网络
提供网络配置
检测、处理各种网络和节点的操作状态。
读取、设置网络和节点的参数
支持诊断
评论3