AUTOSARが、2023年の版、R23-11を公開しています。

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

R23-11 Releaes overviews はこちら。

Classic Platform Release Overview, AUTOSAR No.0 ,R23-11, CP
https://qiita.com/kaizen_nagoya/items/9d22c8722cbc0f42b137

Foundation Release Overview, AUTOSAR 781, R23-11, FO
https://qiita.com/kaizen_nagoya/items/f249bdb8c313d8bff883

Adaptive Platform Release Overview, AUTOSAR 782, R23-11, AP
https://qiita.com/kaizen_nagoya/items/13a104606a34fe24fcf7

<この項は書きかけです。順次追記します。>
This article is not completed. I will add some words in order.

Qiita 記事一覧

Autosar Foundation R23-11 一覧
https://qiita.com/kaizen_nagoya/items/c30674cb2dac2fcbbd04

AUTOSAR Adaptive Platform R23-11一覧
https://qiita.com/kaizen_nagoya/items/1dece8799a730367b0dc

Autosar Classic Platform R23-11 一覧
https://qiita.com/kaizen_nagoya/items/f770f6c2906e1dcbf180

Term

Short Name（Abbreviation / Acronym)	Description
CAN Communication Matrix	Describes the complete CAN network: - Participating nodes - Definition of all CAN PDUs (Identifier, DLC) - Source and Sinks for PDUs Format is defined in other AUTOSAR workpackage
Physical Channel	A physical channel represents an interface to the CAN Network. Different physical channels of the CAN Hardware Unit may access different networks.
L-PDU	CAN (Data Link Layer) Protocol Data Unit. Consists of Identifier, DLC and Data (L-SDU).
L-SDU	CAN (Data Link Layer) Service Data Unit. Data that is transported inside the LPDU.
Hardware Object	A Hardware Object is defined as message buffer inside the CAN RAM of the CAN Hardware Unit. Also often called Message Object
Hardware Object Handle	The hardware object handle (HOH) is defined and provided by the CAN Driver. Typically each HOH represents a hardware object. The HOH is used as parameter by the CAN Interface Layer for transmit and read requests to the CAN Driver.
L-PDU Handle	The L-PDU handle is defined and placed inside the CAN Interface Layer. Typically each handle represents a L-PDU or a range of L-PDUs, and is a constant structure with information for Tx/Rx processing.
CAN Controller	A CAN controller serves exactly one physical channel. See Figure "Typical CAN HW Unit" in CAN Interface SWS.
CAN Hardware Unit	A CAN hardware unit may consist of one or multiple CAN controllers of the same type and one or multiple CAN RAM areas. The CAN hardware unit is either onchip, or an external device. The CAN hardware unit is represented by one CAN Driver. See Figure "Typical CAN HW Unit" in CAN Interface SWS.
Multiplexed Transmission	Usage of three TX HW objects, which are represented as one transmit entity (Hardware Object Handle) to the upper layer. Used for Outer Priority Inversion avoidance
Inner Priority Inversion	Transmission of a high-priority L-PDU is prevented by the presence of a pending low-priority L-PDU in the same physical channel.
Outer Priority Inversion	Occurs when a time gap is between two consecutive TX L-PDU transmissions. In this case a lower priority L-PDU from another node can prevent sending the next L-PDU because the higher priority L-PDU can't participate in the running bus arbitration because it comes too late.
Bus	A bus represents a CAN or LIN network. A bus has a given physical behavior (e.g. CAN low-speed or high-speed). A bus may support wakeup via bus or is “always on”.
N-PDU	Network Protocol Data Unit of the CAN Transport Layer
N-SDU	Service Data Unit of the CAN Transport Layer. Data that is transported inside the N-PDU.
static configuration	Configuration, that is not changeable during runtime. This means that a configuration is typically done once during startup phase of the ECU. This concern is independent from the possibilities to introduce the configuration parameters into the ECU itself: Pre-Compile-Time, Link-Time or Post-Build-Time
STmin	Separation Time min
BS	Block Size
HTH	CAN hardware transmit handle

Reference

[1] Specification of CAN Driver AUTOSAR_CP_SWS_CANDriver
[2] Specification of CAN Interface AUTOSAR_CP_SWS_CANInterface
[3] Specification of CAN State Manager AUTOSAR_CP_SWS_CANStateManager
[4] Specification of CAN Transport Layer AUTOSAR_CP_SWS_CANTransportLayer
[5] Specification of CAN Transceiver Driver AUTOSAR_CP_SWS_CANTransceiverDriver
[6] Standardization Template AUTOSAR_FO_TPS_StandardizationTemplate
[7] ISO 11898-1:2015 – Road vehicles – Controller area network (CAN)
[8] Road vehicles – Diagnostics on Controller Area Networks (CAN) – Part2:Network layer services
[9] Diagnostics on controller area network(CAN)–Part4:Requirementsforemission- related systems (Release 2005 01-04)

Glossaryも入れましょう。
https://www.autosar.org/fileadmin/standards/R23-11/FO/AUTOSAR_FO_TR_Glossary.pdf

補足資料（Additions）

2023 Countdown Calendar 主催・参加一覧
https://qiita.com/kaizen_nagoya/items/c4c2f08ac97f38d08543

CountDownCalendar月間　いいねをいただいた記事群　views　順
https://qiita.com/kaizen_nagoya/items/583c5cbc225dac23398a

＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞
This article is an individual impression based on the individual's experience. It has nothing to do with the organization or business to which I currently belong.

文書履歴(document history)

ver. 0.01 初稿　20231231

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

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

Thank you very much for reading to the last sentence.

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

Requirements on CAN, AUTOSAR 1, R23-11, CP