2023年4月URL変更

この項は2023年4月21日、AUTOSARの文書のURLが変更になった。
/classic/22-11/
が
/R22-11/CP/
過去記事で、URLでエラーが出たら書き換えてみてください。

/adaptive/22-11/
は　
/R22-11/AP/

/foundation/22-11/
は　
/R22-11/FO/
です。

2023年11月URL変更

2023年11月にもAUTOSAR文書のURLが変更になっている。
/user_upload/standards/classic/21-11/
を
/standards/R21-11/CP/
などに書き換えてください。

/user_upload/standards/adaptive/21-11/
を
/standards/R21-11/AP/

/user_upload/standards/foundation/21-11/
を
/standards/R21-11/FO/

お手数をおかけします。
１年に２度URLを変更するなんて、新しい記事が書ける。とても嬉しい。

一覧

AUTOSAR R22-11 Qiita記事一覧 20230421 。

この記事の表題の最後に「20230421」を加えます。

<この項は書きかけです。順次追記します。>

AUTOSARが、2022年の版、R22-11を公開しました。

R21-11

R20-11

R19-11

文書は検索してダウンロードできます。

R20-11,R21-11, R22-11の３年分だけになりました。

公開行事の模様は

AUTOSAR R22-11 Release Event 20221208

AUTOSAR R22-11 Classic Platform 一覧はこちら。

Classic Platform Release Overview, AUTOSAR No.0 ,R22-11, CP, 20230421

要求仕様対応(Requirement and Specification)

Abstract Platformとの関係

RTEの仕様の一部でよいかもしれない。

<この項は書きかけです。順次追記します。>

文書変更(Document Change)

Replaced "Figure 2.1" in the document with the "Figure 2.9" from TR_Methodology
Changed the caption of "Figure 2.2" to "Concept of the virtual functional bus"
Rephrased references to the obsolete step called “Configure System”

用語(terms)

Kind	Description
Application software component	The Application Software Component is an Atomic Software Component that implements (part of) an application. It can use all AUTOSAR communication mechanisms and services. The Application Software Component interacts with sensors or actuators through a Sensor-Actuator Software Component.
Sensoractuator software component	The Sensor-Actuator Software Component is an Atomic Software Component that handles the specifics of a sensor and/or actuator. It directly interacts with the ECUAbstraction (this is illustrated by a port called “IO”). See Chapter 6, Interaction with hardware.
Parameter software component	A Parameter Software Component provides parameter values. These can be fixed data, const or variable. This Software Component allows for data access to either fixed data or calibration data. See chapter 10.
Composition software component	A Composition Software Component encapsulates a collaboration of Software Components, thereby hiding detail and allowing the creation of higher abstraction levels. Through delegation connectors a composition software component explicitly specifies, which ports of the internal components are visible from the outside. Composition Software Components are a specialized type of Software Components, e.g. they can be part of further Composition Software Components.
Service Proxy software component	The Service Proxy SW Component is responsible for distribution of modes throughout the system. Once deployed each ECU should have a copy of every instance of this software component type. However at the VFB level only one is necessary.
Service software component	A Service Software Component provides standardized services through standardized interfaces. To provide these services, this component may interact directly with certain other basic-software modules (this is represented by the double arrow). See Chapter 7.
ECU abstraction software component	The ECU-Abstraction Software Component provides access to the ECU’s specific IO capabilities. These services are typically provided through client-server PPorts and are used by the sensor-actuator software components. The ECU-abstraction may directly interact with certain other basic-software modules (this is represented by the double arrow). See Chapter 6, Interaction with hardware.
Complex driver software component	The Complex Driver Software Component generalizes the “ECUabstraction component”. It can define ports to interact with other components in specific ways and can also interact directly with other basicsoftware modules. The purpose of the Complex Driver Software Component is described further in Section 6.5 Complex Driver.
NVBlock software component	The NV Block Software Component allows SWC-S access to non volatile data. Specifically this block allows for the modeling of the NV data at the VFB level. It is the responsibility of the NV Block to map individual NV data elements to NV Blocks and to interact with the NV Manager in the BSW. The behavior of this component is to be generated based on the port services in the RTE.

英日

日本語は仮訳

T.B.D.

参考(reference)

[1] Methodology
AUTOSAR_TR_Methodology.pdf
[2] Glossary, AUTOSAR_TR_Glossary.pdf
https://www.autosar.org/fileadmin/standards/R22-11/FO/AUTOSAR_TR_Glossary.pdf
[3] Main Requirements
AUTOSAR_RS_Main.pdf
[4] List of Basic Software Modules
AUTOSAR_TR_BSWModuleList.pdf
[5] Layered Software Architecture
AUTOSAR_EXP_LayeredSoftwareArchitecture.pdf
[6] Software Component Template
AUTOSAR_TPS_SoftwareComponentTemplate.pdf
[7] Specification of RTE
AUTOSAR_SWS_RTE.pdf
[8] Specification of Timing Extensions
AUTOSAR_TPS_TimingExtensions.pdf
[9] Explanation of Application Interfaces of the Body and Comfort Domain
AUTOSAR_EXP_AIBodyAndComfort.pdf
[10] Explanation of Application Interfaces of the Powertrain Domain
AUTOSAR_EXP_AIPowertrain.pdf
[11] Explanation of Application Interfaces of the Chassis Domain
AUTOSAR_EXP_AIChassis.pdf
[12] Explanation of Application Interfaces of Occupant and Pedestrian Safety Systems Domain
AUTOSAR_EXP_AIOccupantAndPedestrianSafety.pdf
[13] Explanation of Application Interfaces of the HMI, Multimedia and Telematics Domain
AUTOSAR_EXP_AIHMIMultimediaAndTelematics.pdf
[14] Application Interfaces User Guide
AUTOSAR_EXP_AIUserGuide.pdf
[15] ISO 17356-4, OSEK/VDX Communication (COM)
www.iso.org

＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞

文書履歴(document history)

ver. 0.01 初稿　20230527

最後までおよみいただきありがとうございました。

いいね　💚、フォローをお願いします。

Thank you very much for reading to the last sentence.

Please press the like icon 💚　and follow me for your happy life.

Virtual Functional Bus, AUTOSAR 56, R22-11, CP, 20230421