Specification of Communication, No.15, AUTOSAR R21-11(184) CP

Specification of Communication, No.15, 2021-11

https://www.autosar.org/fileadmin/standards/classic/21-11/AUTOSAR_SWS_COM.pdf


AUTOSAR R21-11記事一覧はこちら。

AUTOSAR 21-11, 160文書読んだ。2022年5月に半分到達。

https://qiita.com/kaizen_nagoya/items/4043e8414f850ce266a4

AUTOSAR R21-11(0) 仕様ダウンロード一覧。単語帳。参考文献資料作成

https://qiita.com/kaizen_nagoya/items/9b3a1b9b8d1e8d7e288e

# 用語(terms)

|Term|Description|
|:--|:--|
|AUTOSAR COM |The AUTOSAR COM module is derived from [17]. For details, see Chapter 7.2.1.
|DM |Deadline Monitoring, for details see Chapter 7.3.6
|I-PDU |Interaction Layer Protocol Data Unit. An I-PDU carries signals. It is defined in [17].
|L-PDU |Data Link Layer Protocol Data Unit. In AUTOSAR, the Data Link Layer is equivalent to the Communication Hardware Abstraction and Microcontroller Abstraction Layer.
|MDT |A detailed description of the Minimum Delay Timer (MDT) can be found in [17]. See also Chapter 7.3.5.5.
|PDU Router |The PDU Router is a module transferring I-PDUs from one module to another module. The PDU Router can be utilized for gateway operations and for internal routing purposes.
|SDU |Service Data Unit For a description see [1] Chapter 4.
|TM |Transmission Mode
|TMC |Transmission Mode Condition, see Chapter 7.3.3.2
|TMS |Transmission Mode Selector, see Chapter 7.3.3.2
|Confirmation| With a Confirmation, the PDU Router reports that a request by the AUTOSAR COM module has been completed successfully. It is a reaction to a request of COM. E.g. when a PDU has been successfully transmitted.
|Data Invalid Value| Value sent by the AUTOSAR COM module to indicate that the sender side AUTOSAR Software Component is not able to provide a valid value.
|Dynamic Length Signal|A dynamic length signal is a signal which length can vary at run-time.
|Dynamic Length I-PDU|A dynamic length I-PDU is an I-PDU containing a dynamic length signal. It length varies depending on the length of the included dynamic length signal.
|Group signal |A group signal is a signal that is contained in a signal group.
|Indication| An Indication is asynchronous information from PDU Router to COM, e.g. to acknowledge that something has been received.
|Init Value| I-PDUs and signals are set to the Init Value by the AUTOSAR COM module after start-up. This value is used until it is overwritten.
|I-PDU group |An I-PDU Group is an arbitrary collection of I-PDUs of the same direction (i.e. send or receive) in the COM module.
|Inter-ECU – communication|Communication between two or more ECUs for example via a CAN network Intra-ECU – communication|Communication between Software components that reside on the same ECU
|Large Signal| A large signal is a signal that is too large to fit into a single L-PDU of the underlying communication protocol.
|Large I-PDU| Large I-PDUs are I-Signal-I-PDUs which do not fit into a single L-PDU of the underlying communication protocol. Large I-PDUs will be handled like other  I-PDUs by COM, but are transmitted/received via the TP API. Please note that large I-PDUs can also be handled in a more efficient way by LargeDataCOM if they contain just one signal, or if the signals can be (de- )serialized by the RTE. But if the signals have to be treated separately or have to be routed, the large I-PDUs have to be handled by COM.
|Message |[17] uses always the synonym message. In AUTOSAR, message is replaced by signal but with the same meaning.
|Metadata |For some I-PDUs, e.g. J1939 I-PDUs, the payload is extended with additional metadata containing for example the CAN-ID. Notification Information by the AUTOSAR COM module to its users (e.g. RTE, SwCluC), e.g. when new data is available, an error occurred.
|Signal| A signal in the AUTOSAR COM module’s context is equal to a message in [17]; see also [7].
|Signal group |In AUTOSAR, so called complex data types are used. Inside a complex data type, there are one or more data elements (primitive data types), like in a C struct. The data consistency of such complex data types must be ensured. The user (e.g. RTE or SwCluC) decomposes the complex data type in single signals and sends them to the AUTOSAR COM module. As these signals altogether need to be treated consistently, they are called signal group. See also [7].
|Update-bit |A mechanism supported by the AUTOSAR COM module with that the receiver of a signal/ signal group could identify whether the sender has updated the data in this signal/ signal group before sending. See Chapter 7.9.

## 英日単語帳
日本語は仮訳

T.B.D.

# 参考(reference)

[1] AUTOSAR Layered Architecture
AUTOSAR_EXP_LayeredSoftwareArchitecture.pdf
[2] Specification of Communication Stack Types
AUTOSAR_SWS_CommunicationStackTypes.pdf
[3] General Requirements on Basic Software Modules
AUTOSAR_SRS_BSWGeneral.pdf
[4] Basic Software UML Model
AUTOSAR_MOD_BSWUMLModel.eap
[5] Specification of Standard Types
AUTOSAR_SWS_StandardTypes.pdf
[6] Specification of the Virtual Functional Bus
AUTOSAR_EXP_VFB.pdf
[7] Requirements on Communication
AUTOSAR_SRS_COM.pdf
[8] Software Component Template
AUTOSAR_TPS_SoftwareComponentTemplate.pdf
[9] Requirements on Gateway
AUTOSAR_SRS_Gateway.pdf
[10] Specification of PDU Router
AUTOSAR_SWS_PDURouter.pdf
[11] Specification of Operating System
AUTOSAR_SWS_OS.pdf
[12] System Template
AUTOSAR_TPS_SystemTemplate.pdf
[13] Specification of RTE Software
AUTOSAR_SWS_RTE.pdf
[14] Specification of ECU Configuration
AUTOSAR_TPS_ECUConfiguration.pdf
[15] Specification of Communication Manager
AUTOSAR_SWS_COMManager.pdf
[16] AUTOSAR Basic Software Module Description Template
AUTOSAR_TPS_BSWModuleDescriptionTemplate.pdf
[19] Specification of CAN Transport Layer
AUTOSAR_SWS_CANTransportLayer.pdf
[20] Specification of FlexRay Transport Layer
AUTOSAR_SWS_FlexRayTransportLayer.pdf
[21] List of Basic Software Modules,
AUTOSAR_TR_BSWModuleList.pdf
[22] Generic Structure Template
AUTOSAR_TPS_GenericStructureTemplate.pdf
[23] General Specification of Basic Software Modules
AUTOSAR_SWS_BSWGeneral.pdf
[24] Specification of Software Cluster Connection
AUTOSAR_SWS_SoftwareClusterConnection.pdf
[17] ISO 17356-4:2005 Road vehicles -- Open interface for embedded automotive
applications -- Part 4: OSEK/VDX Communication (COM)
[18] ISO 17356-6:2006 Road vehicles -- Open interface for embedded automotive
applications -- Part 6: OSEK/VDX Implementation Language (OIL)