Specification of Communication Manager, AUTOSAR R22-11, CP, No.79
AUTOSARが、2022年の版、R22-11公開しました。公開行事の模様は
AUTOSAR R22-11 Release Event 20221208
下記URL順次確認中です。
間違っていたら、いいね を押していただいて、コメント欄にご報告くださると幸いです。
編集リクエストが、構造的な変更をしている最中に、構造的な編集リクエストをしていただくと、
何をどう直したらいいかわからなくなってしまいます。自動修復ツールがつくれていません。ごめんなさい。
文書は検索してダウンロードすることができます。
クラウドサービスにありがちな、あるのにないかのような検索結果が出ることがあります。
要求/仕様（Requirement and Specification)
一覧
AUTOSAR R22-11 Classic Platform 一覧はこちら。
Classic Platform Release Overview, AUTOSAR R22-11, CP, No.0(2)
AUTOSAR R22-11 マラソン
Qiitaの記事の一覧は作成中です。
AUTOSAR R22-11 一覧（２）
Abstract Platformとの関係
COM, NM, State management, DIAG(TP), NVRAM、電源管理・状態管理の体系化。
<この項は書きかけです。順次追記します。>
文書変更(Document Change)
Introduced validation findings of concept
“ReworkOfPNCrelatedComMandNM
handling (part2)”
Introduced validation findings of
concept “VNSM (part1)”
Removed obsolete marked requirements of concept
“ReworkOfPNCrelatedComMandNM handling (part1/part2)” and “EthernetWakeOnDataLine (part1)”
用語(terms)
| Term | Description |
|---|---|
| BSW | Basic Software |
| BswM | Basic Software Mode Manager |
| ComM | Communication Manager |
| DCM | Diagnostic Communication Manager |
| Det | Default Error Tracer |
| EcuM | ECU State Manager module |
| I-PDU | Information Protocol Data Unit |
| NM | Network Management |
| PDU | Protocol Data Unit |
| SW-C | Software Component |
| VMM | Vehicle Message Matrix |
| OA TC10 | Open Alliance TC10 specification (see [33]) |
| IRA | Internal Request Array. This is a bit vector which contains the aggregated internal PNC requests per channel. (see also chapter 8.6.2 “Nm_UpdateIRA”) |
| EIRA | External and Internal Request Array. This is a bit vector which contains the aggregated external and internal PNC requests |
| ERA | External Request Array. This is a bit vector which contains the aggregated external PNC requests. Each ComMChannel which has a ComMGatewayType set is has one corresponding ERA |
| ERAn | All External Request Arrays which are available in ComM, i.e. “n” ComMChannels were ComMGatewayType is set, result in “n” External Request Arrays in ComM |
| DCM_ActiveDiagnostic indication | The DCM module indicates an active diagnostic session. DCM need “full communication” = COMM_FULL_COMMUNICATION for diagnostic purpose |
| Active wake-up | Wake-up caused by the hosting ECU e.g. by a sensor. |
| Application signal scheduling | Sending of application signals according to the VMM. Scheduling of CAN application signals is performed by the Communication Module, scheduling of LIN application I-PDUs (a PDU containing signals) is performed by the LIN interface and scheduling of FlexRay application PDUs is performed by the FlexRay Interface module. |
| Bus sleep | No activity required on the communication bus (e.g. CAN bus sleep). |
| Bus communication messages | Bus communication messages are all messages that are sent on the communication bus. This can be either a diagnostic message or an application message. |
| COM Inhibition status | Defines whether full communication, silent communication or wakeup is allowed or not. |
| Communication Channel | The medium used to convey information from a sender (or transmitter) to a receiver. |
| Communication Mode | Mode determining which kind of communication are allowed: “full communication” = COMM_FULL_COMMUNICATION “no communication” = COMM_NO_COMMUNICATION “silent communication” = COMM_SILENT_COMMUNICATION Note: COMM_SILENT_COMMUNICATION can not be requested by a user. Internal mode for synchronizing network at shutdown |
| Diagnostic PDU scheduling | Sending of diagnostic PDUs. Scheduling of CAN diagnostic PDUs is performed by the diagnostic module, scheduling of LIN diagnostic PDUs is performed by the diagnostic module and the LIN interface and scheduling of FlexRay diagnostic PDUs is performed by the diagnostic module and the FlexRay Interface module. |
| ECU shut down | See ECU State Manager specification [6]. |
| Fan-out | Same message/indication are sent to multiple destinations/receivers |
| Independent software component | A separately developed software component performing a coherent set of functions with a minimum amount of interfaces to other software applications on an ECU. This can be e.g. a basic software component or an application software component. |
| Passive wake-up | Wake-up by another ECU and propagated (e.g. by bus or wake-upline) to the ECU currently in focus. |
| System User | An administration functionality (a specific "user", which is generated within the internal context of the ComM) for making a default request and for overriding the user requests. |
| User | Concept for requestors of the ECU State Manager module and of the Communication Manager Module. A user may be the BswM, a runnable entity, a SW-C or a group of SW-Cs, which act as a single unit towards the ECU State Manager module and the Communication Manager Module. |
| User Request | A User can request different Communication Modes from ComM |
| Managed channel | A ComM channel that is referenced exclusively from one other channel by ECUC parameter ComMManageReference (see ECUC_ComM_00893). |
| Managing channel | A ComM channel that references 1..n other channels by ECUC parameter ComMManageReference (see ECUC_ComM_00893). |
英日単語帳
日本語は仮訳
T.B.D.
参考(reference)
[1] List of Basic Software Modules
AUTOSAR_TR_BSWModuleList.pdf
[2] Layered Software Architecture
AUTOSAR_EXP_LayeredSoftwareArchitecture.pdf
[3] General Requirements on Basic Software Modules
AUTOSAR_SRS_BSWGeneral.pdf
[4] Requirements on Mode Management
AUTOSAR_SRS_ModeManagement.pdf
[5] Specification of ECU Configuration
AUTOSAR_TPS_ECUConfiguration.pdf
[6] Specification of ECU State Manager
AUTOSAR_SWS_ECUStateManager.pdf
[7] Specification of NVRAM Manager
AUTOSAR_SWS_NVRAMManager.pdf
[8] Specification of RTE Software
AUTOSAR_SWS_RTE.pdf
[9] Specification of Generic Network Management Interface
AUTOSAR_SWS_NetworkManagementInterface.pdf
[11] Specification of Diagnostic Communication Manager
AUTOSAR_SWS_DiagnosticCommunicationManager.pdf
[12] Specification of LIN Interface
AUTOSAR_SWS_LINInterface.pdf
[13] Specification of FlexRay Interface
AUTOSAR_SWS_FlexRayInterface.pdf
[14] Specification of Default Error Tracer
AUTOSAR_SWS_DefaultErrorTracer.pdf
[16] Specification of CAN Transceiver Driver
AUTOSAR_SWS_CANTransceiverDriver.pdf
[17] Specification of CAN Interface
AUTOSAR_SWS_CANInterface.pdf
[18] Specification of FlexRay Transceiver Driver
AUTOSAR_SWS_FlexRayTransceiver.pdf
[19] Specification of PDU Router
AUTOSAR_SWS_PDURouter.pdf
[20] Requirements on IPDU Multiplexer
AUTOSAR_SWS_IPDUM.pdf
[21] Specification of System Services Mode Management
AUTOSAR_SystemServices_ModeManagement.pdf
[22] Specification of C Implementation Rules
AUTOSAR_Tr_CImplementationRules.pdf
[23] Specification of LIN State Manager
AUTOSAR_SWS_LINStateManager.pdf
[24] Specification of CAN State Manager
AUTOSAR_SWS_CANStateManager.pdf
[25] Specification of FlexRay State Manager
AUTOSAR_SWS_FlexRayStateManager.pdf
[26] Basic Software Module Description Template,
AUTOSAR_TPS_BSWModuleDescriptionTemplate.pdf
[27] Glossary, AUTOSAR_TR_Glossary.pdf
https://www.autosar.org/fileadmin/standards/foundation/22-11/AUTOSAR_TR_Glossary.pdf
[28] Specification of Ethernet State Manager
AUTOSAR_SWS_EthernetStateManager.pdf
[29] Specification of Basic Software Mode Manager
AUTOSAR_SWS_BSWModeManager.pdf
[30] General Specification of Basic Software Modules
AUTOSAR_SWS_BSWGeneral.pdf
[31] Specification of System Template
AUTOSAR_TPS_SystemTemplate
[32] Specification of Guide to BSW Distribution
AUTOSAR_EXP_BSWDistributionGuide
[33] OPEN ALIANCE Sleep/Wake-up Specification Version 2.0 (Rel Feb 21, 2017),
http://www.opensig.org/Automotive-Ethernet-Specifications/
関連文書(Related document)
2023年1月 記事数一覧
年末100記事を30点に仕上げる。
2023 書き初め
「はじめてのCAN/CANFD 」 ベクタージャパン ＜エンジニア夏休み企画>【読書感想文】
三方良し Udemy 車載LAN入門講座 CAN通信編
詳解 車載ネットワーク CAN, CAN FD, LIN, CXPI, Ethernetの仕組みと設計のために(1) 著者 ＜エンジニア夏休み企画 読書感想文＞
詳解 車載ネットワーク CAN, CAN FD, LIN, CXPI, Ethernetの仕組みと設計のために(2)参考文献 ＜エンジニア夏休み企画>【読書感想文】
詳解 車載ネットワーク CAN、CAN FD、LIN、CXPI、Ethernetの仕組みと設計のために
R22-11 URL変更
Specification of Communication Manager, AUTOSAR 79, R22-11, CP, 20230421
＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞
文書履歴(document history)
ver. 0.01 初稿 20230109
ver. 0.02 ありがとう追記 20230610
最後までおよみいただきありがとうございました。
いいね 💚、フォローをお願いします。
Thank you very much for reading to the last sentence.
Please press the like icon 💚 and follow me for your happy life.