"ISO 17356标准化 OSEK_VDX通信规范 V3.0.2详解"

需积分: 5 28 浏览量更新于2024-01-02 收藏 883KB PDF 举报

本文总结了关于OSEK的一些相关标准和文档，主要包括“OSEK_VDX_Communication(COM)_V3.0.2_2003.pdf”和ISO 17356标准。首先，介绍了ISO 17356标准，该标准由多个部分组成，其中包括OSEK Glossary、OSEK Binding Specification、OSEK OS、OSEK COM、OSEK NM和OSEK OIL。这些部分分别对应于不同的功能或规范，涵盖了OSEK系统的各个方面。其中，OSEK Glossary是ISO 17356-1的一部分，它包含了介绍和术语表。OSEK Binding Specification是ISO 17356-2，是基于OSEK Binding 1.4.1的规范，除去了术语表。OSEK OS是ISO 17356-3，基于OSEK OS 2.2.1的规范。OSEK COM是ISO 17356-4，基于OSEK COM 3.0.2的规范。OSEK NM是ISO 17356-5，基于OSEK NM 2.5.2的规范。而OSEK OIL则是ISO 17356-6，基于OIL 2.4.1的规范。此外，本文还提到了“OSEK/VDX Communication Version 3.0.2”这一特定的文档。这是OSEK/VDX COM 3.0.2的官方版本，发布于2003年12月9日。该文档取代了以前的版本，并对其进行了一些修改和更新。不过，该文档的内容可能随时发生变化，OSEK组有权对其进行修改，而不需要提前通知。同时，该文档也无法保证不存在错误，并对由此可能产生的任何责任不承担责任。该文档的任何部分未经书面许可，不得以任何形式或任何方式复制。综上所述，本文总结了关于OSEK和ISO 17356的相关标准和文档。这些标准和文档涵盖了OSEK系统的各个方面，包括术语表、规范和功能规范。同时，本文还提到了特定的文档“OSEK/VDX Communication Version 3.0.2”，该文档是关于OSEK/VDX COM 3.0.2的官方版本，并对其进行了一些说明和免责声明。

OSEK/VDX

OSEK Communication

Specification 3.0.2

OSEK/VDX COM 3.0.2  by OSEK - 12 -

2.2 Message reception

This section states the services and the functionality requirements of the message reception

entity of the IL.

2.2.1 Message reception overview

The first few steps described in this section are applicable for external communication only.

Reception of a message starts with an indication of the delivery of its containing PDU from

the underlying layer. If this indication does not yield an error, the reception was successful. In

this case, an I-PDU Callout is called (if configured) and this PDU is copied into the I-PDU.

In the case of unsuccessful PDU reception error indication takes place and no data is

delivered to the IL. Error indication can lead to Message Reception Error notification

(Notification Class 3, described in section 2.6.1).

After copying the data into the I-PDU further processing is performed separately for each

contained message. If the I-PDU contains zero-length messages, these are processed last.

The Reception Deadline Monitoring takes place as described in section 2.5.1. Deadline

Monitoring can invoke Message Reception Error notification (Notification Class 3, described

in section 2.6.1) when the message reception deadline is missed because the I-PDU that

contains the message is not received in time.

Then, the message data is unpacked from the I-PDU and, if configured, a Network-order

Message Callout is called for the message. Message byte ordering is performed to convert

from network representation to the representation on the local CPU and, if configured, a

CPU-order Message Callout is called for the message.

The following steps are applicable for both internal and external communication.

The filtering is applied to the message content. If the message is not filtered out, then the

message data is copied into the receiver message object.

After filtering, Message Reception notification (Notification Class 1, described in section

2.6.1) is invoked as appropriate. Notification is performed per message object.

Message data are copied from message object to application messages when the application

calls the ReceiveMessage or ReceiveDynamicMessage API services.

2.2.2 Reception filtering

Filtering provides a means to discard the received message when certain conditions, set by

message filter, are not met for the message value. The message filter is a configurable

function that filters messages out according to specific algorithms. For each message a

different filtering condition can be defined through a dedicated algorithm.

Filtering is only used for messages that can be interpreted as C language unsigned integer

types (characters, unsigned integers and enumerations).

OSEK/VDX

OSEK Communication

Specification 3.0.2

OSEK/VDX COM 3.0.2  by OSEK - 13 -

For zero-length messages and dynamic-length messages no filtering takes place.

While receiving messages, only the message values allowed by the filter algorithms pass to

the application. If a value has been filtered out the current instance of the message in the IL

represents the last message value that passed through the filter.

Message filtering is performed per message object.

The following attributes are used by the set of filter algorithms (see Table 2-1):

new_value: current value of the message

old_value: last value of the message (initialised with the initial value of the message,

updated with new_value if the new message value is not filtered out)

mask, x, min, max, period, offset: constant values

occurrence: a count of the number of occurrences of this message

If the message filter algorithm is F_Always for any particular message no filter algorithm is

included in the runtime system for the particular message.

Algorithm Reference Algorithm Description

F_Always True No filtering is performed so that the

message always passes

F_Never False The filter removes all messages

F_MaskedNewEqualsX (new_value&mask) == x Pass messages whose masked value is equal

to a specific value

F_MaskedNewDiffersX (new_value&mask) != x Pass messages whose masked value is not

equal to a specific value

F_NewIsEqual new_value == old_value Pass messages which have not changed

F_NewIsDifferent new_value != old_value Pass messages which have changed

F_MaskedNewEqualsMaskedOld (new_value&mask) ==

(old_value&mask)

Pass messages where the masked value has

not changed

F_ MaskedNewDiffersMaskedOld (new_value&mask) !=

(old_value&mask)

Pass messages where the masked value has

changed

F_NewIsWithin min <= new_value <=

max

Pass a message if its value is within a

predefined boundary

F_NewIsOutside (min > new_value) OR

(new_value > max)

Pass a message if its value is outside a

predefined boundary

F_NewIsGreater new_value > old_value Pass a message if its value has increased

F_NewIsLessOrEqual new_value <= old_value Pass a message if its value has not increased

F_NewIsLess new_value < old_value Pass a message if its value has decreased

F_NewIsGreaterOrEqual new_value >= old_value Pass a message if its value has not decreased

F_OneEveryN Occurrence % period ==

offset

Pass a message once every N message

occurrences.

Start: Occurrence = 0.

Each time the message is received or

transmitted, Occurrence is incremented by 1

after filtering.

Length of Occurrence is 8 bit (minimum).

Table 2-1: Message filter algorithms

剩余72页未读，继续阅读

汽车电子助手

粉丝: 1w+
资源: 124

"ISO 17356标准化 OSEK_VDX通信规范 V3.0.2详解"

"ISO 17356标准和OSEK_VDX网络管理概念及API V2.5.3

"ISO 17356标准化的OSEK_VDX操作系统规范2.2.2详解

"ISO 17356标准：OSEK_VDX通信规范V3.0.3解读

OSEK_VDX.zip_OSEK VDX _OSEK_VDX_flame92l_osek_osek os

OSEK_VDX_Communication(COM)_V3.0.3_2004.pdf

OSEK_VDX_Fault-Tolerant Communication_V1.0_2001.pdf

OSEK_VDX_Binding_Specification_V1.4.1_2003.pdf

OSEK_VDX_Operating System(OS)_V2.2.1_2003.pdf

OSEK_VDX_Binding_Specification_V1.3_2001.pdf

OSEK_VDX_Binding_Specification_V1.4.2_2004.pdf

最新资源