Specification of Health Monitoring, AUTOSAR 850, R22-11, FO, 20230421

AUTOSARは団体規格です。　
業務で利用する場合には、会員になることを条件にしています。

2002年から20年経ち、当初の狙いの段階に近づいてきました。

MATLABでモデルさえ記述すれば、あとは自動生成だけでソフトが完成するところまで、あと一歩です。
Ethernet, UNIXが生まれて20年で大衆化したのと同じように考えると分かりやすいでしょう。　

AUTOSARの上で動く、クラウド対応のミドルウェアが出て、開発も運用もクラウドになれば、一気にAUTOSARは大衆化するでしょう。

AUTOSAR Abstract Platformへの道 R22-11
https://qiita.com/kaizen_nagoya/items/8ac2826635a8c536c7ec

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

# 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 。

https://qiita.com/kaizen_nagoya/items/81a35774f1aa3d64d3f6

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

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

https://www.autosar.org/fileadmin/standards/R22-11/FO/AUTOSAR_ASWS_HealthMonitoring.pdf

R21-11

https://www.autosar.org/fileadmin/standards/R21-11/FO/AUTOSAR_ASWS_HealthMonitoring.pdf

R20-11

https://www.autosar.org/fileadmin/standards/R20-11/FO/AUTOSAR_ASWS_HealthMonitoring.pdf

R19-11

https://www.autosar.org/fileadmin/standards/R19-11/FO/AUTOSAR_ASWS_HealthMonitoring.pdf

https://www.autosar.org/

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

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

公開行事の模様は

AUTOSAR R22-11 Release Event 20221208

https://qiita.com/kaizen_nagoya/items/18471d0b340480fdcd42

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

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

Foundation Release Overview, AUTOSAR, 781, R22-11, FO, 20230421

https://qiita.com/kaizen_nagoya/items/596a7e2ec86913daa3c2

Adaptive Platform Release Overview, AUTOSAR 782, R22-11, AP, 20230421

https://qiita.com/kaizen_nagoya/items/fc8e02e8cb07411dbc2a

# 要求仕様対応(Requirement and Specification)
# Abstract Platformとの関係
RS統合

# 文書変更(Document Change) 

>• Introduced Elementary Supervision Status for Adaptive platform
• Determination of Supervision Status is now platform specific
# 用語(terms)
|Term|Description|
|:--|:--|
|Alive Indication |An indication of a Supervised Entity to signal its aliveness by calling a checkpoint used for Alive Supervision.
|Alive Supervision |Kind of supervision that checks if a Supervised Entity executed in a correct frequency.
|Checkpoint |A point in the control flow of a Supervised Entity where the activity is reported.
|Deadline Supervision |Kind of supervision that checks if the execution time between two Checkpoints is within minimum/maximum time limit.
|Final Checkpoint| The ending Checkpoint of a Graph. There can be zero or more Final Checkpoints for each Graph.
|Global Supervision Status| Status that summarizes the Local Supervision Status of all Supervised Entities of a software subsystem.
|Graph |A set of Checkpoints connected through Transitions, where at
least one of Checkpoints is an Initial Checkpoint. There is a path (through Transitions) between any two Checkpoints of the Graph.
|Health Channel| Channel providing information about the health status of a (sub)system. This might be the Global Supervision Status of an application, the result any test routine or the status reported by a (sub)system (e.g. voltage monitoring, OS kernel, ECU status, ...).
|Health Channel Supervision| Kind of supervision that checks if the health indicators registered by the supervised software are within the tolerances/limits.
|Health Monitoring |Supervision of the software behaviour for correct timing and sequence.
|Health Status |A set of states that are relevant to the supervised software (e.g. a Voltage State, an application state, the result of a RAM monitoring algorithm).
|Health Status Supervision| Check if the health indicators registered by the supervised software are within the tolerances/limits.
|Initial Checkpoint| The starting Checkpoint of a Graph. There can be one or more Initial Checkpoints for each Graph.
|Logical Supervision |Kind of online supervision of software that checks if the software (Supervised Entity or set of Supervised Entities) is executed in the sequence defined by the programmer (by the developed code).
|Local Supervision Status| Status that represents the current result of Alive Supervision, Deadline Supervision and Logical Supervision of a single Supervised Entity.
|Machine| see [3] AUTOSAR Glossary
|Platform Health Management |Health Monitoring for the Adaptive Platform
|Supervised Entity| A whole or part of a software component type which is included in the supervision. A Supervised Entity denotes a collection of Checkpoints within the corresponding software component type. A software component type can include zero, one or more Supervised Entities. A Supervised Entity may be instantiated multiple times, in which case each instance is independently supervised.
|Supervision Mode| An overall state of a microcontroller or virtual machine or state of a Function Group (in case of Adaptive Platform). Modes are mutually exclusive. A mode can be e.g. Startup, Shutdown, Low power.
|Health Indicator| Health Indicator provides an evaluation metric of current system performance with regard to safety requirements.
|System Health Monitor(SHM)| System Health Monitor is responsible for monitoring the health of a (Sub)-system. It provides Health Indicators that can be used for system wide error handling across several Classic, Adaptive and any third party platforms.
|Local Health Monitor |Local Health Monitor gathers health information of the platform on which it is deployed.
|Health Indicator Interface |Health Indicator Interface is an interface used for communication of Health Indicators using a standardized service field.
|SE |Supervised Entity.
|SOTIF| Safety Of The Intended Functionality [4].
|Performance |The Performance rates the performance with respect to malfunctioning behavior.
|Reliability |Reliability evaluates how much to trust the system due to uncertainties.

## 英日
日本語は仮訳

T.B.D.

# 参考(reference)

[1] ISO 26262:2018 (all parts) – Road vehicles – Functional Safety
http://www.iso.org
[2] Requirements on Health Monitoring
AUTOSAR_RS_HealthMonitoring
[3] Glossary, AUTOSAR_TR_Glossary
https://www.autosar.org/fileadmin/standards/R22-11/FO/AUTOSAR_TR_Glossary.pdf
[4] ISO/PAS 21448:2019 – Road vehicles – Safety of the intended functionality
http://www.iso.org
[5] Explanation of System Health Monitoring
AUTOSAR_EXP_SystemHealthMonitoring
[6] Specification of Watchdog Manager
AUTOSAR_SWS_WatchdogManager
[7] Specification of Platform Health Management
AUTOSAR_SWS_PlatformHealthManagement


# 関連文書(Related document)

AUTOSAR Abstract Platformへの道 R22-11

https://qiita.com/kaizen_nagoya/items/8ac2826635a8c536c7ec

自動車　記事　１００

https://qiita.com/kaizen_nagoya/items/f7f0b9ab36569ad409c5

Basic principles, ボッシュ自動車handbook(英語)11版まとめ<2>

https://qiita.com/kaizen_nagoya/items/24a1ba5da3d09b2a95d1

JAXA/IPA クリティカルソフトウェアワークショップ WOCS言語関連発表(改定版)

https://qiita.com/kaizen_nagoya/items/4789832baf494cb74626

CAN(controller area network) 

https://qiita.com/kaizen_nagoya/items/e8c0bd7bfb2827b83de9

「はじめてのCAN/CANFD 」 ベクタージャパン ＜エンジニア夏休み企画>【読書感想文】

https://qiita.com/kaizen_nagoya/items/1fee270be00ef90ca4ec


三方良し　Udemy 車載LAN入門講座 CAN通信編

https://qiita.com/kaizen_nagoya/items/bed038c52510fea72c0a


詳解 車載ネットワーク CAN, CAN FD, LIN, CXPI, Ethernetの仕組みと設計のために(1) 著者　 ＜エンジニア夏休み企画 読書感想文＞

https://qiita.com/kaizen_nagoya/items/e9971698a108c3dba794

詳解 車載ネットワーク CAN, CAN FD, LIN, CXPI, Ethernetの仕組みと設計のために(2)参考文献 ＜エンジニア夏休み企画>【読書感想文】

https://qiita.com/kaizen_nagoya/items/e156cbdd5fce9263776e

詳解 車載ネットワーク CAN、CAN FD、LIN、CXPI、Ethernetの仕組みと設計のために

https://qiita.com/kaizen_nagoya/items/44a9e6b0f5363b4a5b35

# R23-11
https://qiita.com/kaizen_nagoya/items/0369a1db83c525ac4c3c
 
＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞
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 初稿　　20230716
ver. 0.02 R23-11追記 20240101
### 最後までおよみいただきありがとうございました。

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

####  Thank you very much for reading to the last sentence.

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