Specification of State Management, No.908, AUTOSAR 21-11 (44) AP

Specification of State Management, No.908, 2021-11

https://www.autosar.org/fileadmin/standards/adaptive/21-11/AUTOSAR_SWS_StateManagement.pdf

一覧はこちら。

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

https://qiita.com/kaizen_nagoya/items/648b32867635993410c8

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

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

# 用語(terms)
|Terms| Description|
|:--|:--|
|State Management| The element defining modes of operation for AUTOSAR Adaptive Platform. It allows flexible definition of functions which are active on the platform at any given time.
|Execution Management [3] |The element of the AUTOSAR Adaptive Platform responsible for the ordered startup and shutdown of the AUTOSAR Adaptive Platform and Adaptive Applications.
|Platform Health Management [4] |A Functional Cluster within the Adaptive Platform Foundation
|Communication Management[1]|A Functional Cluster within the Adaptive Platform Foundation
|Network Management [5]| A Functional Cluster within the Adaptive Platform Services. Part of Communication Management.
|Diagnostic Management [6] |A Functional Cluster within the Adaptive Platform Services
|Update And Configuration Management [7]| A Functional Cluster within the Adaptive Platform Services
|Network Handle| Network Handles are provided by Network Management. A handle represents a set of (partial) networks.
|process |A process refers to the OS concept of a running process. Attention: process is not equal to Modelled Process (see below). Hence each Modelled Process has at some time a related (OS) process but a process may not always have a related Modelled Process.
|Modelled Process |A Modelled Process is an instance of an Executable to be executed on a Machine and has a 1:1 association with the ARXML/Meta-Model element Modelled Process. This document also uses the term process (without the “modelled” prefix) to refer to the OS concept of a running process.
|Function Group |A Function Group is a set of coherent Modelled Processes which need to be controlled consistently. Depending on the state of the Function Group, processes (related to the Modelled Processes) are started or terminated. Modelled Processes can belong to more than one Function Group State (but at exactly one Function Group). "MachineFG" is a Function Group with a predefined name, which is mainly used to control Machine lifecycle and processes of platform level Applications. Other Function Groups are sort of general purpose tools used (for example) to control processes of user level Applications.
|Function Group State |The element of State Management that characterizes the current status of a set of (functionally coherent) user-level Applications. The set of Function Groups and their Function Group States is machine specific and are configured in the Machine Manifest [8].
|Machine State| The state of Function Group "MachineFG" with some predefined states (Startup/Shutdown/Restart).
|Execution Manifest| Manifest file to configure execution of an Adaptive Application.
|Machine Manifest| Manifest file to configure a Machine. The Machine Manifest holds all configuration information which cannot be assigned to a specific Executable or process.


## 英日
日本語は仮訳

|no.|count|word|日本語|
|:----|:----|:----|:----|
|1|551|management|管理|
|2|497|state|状態|
|3|439|the|その|
|4|372|of|の|
|5|338|to|に|
|6|278|sws_sm_|sws_sm_|
|7|212|and|と|
|8|197|in|の中に|
|9|185|a|一つの|
|10|140|function|関数|
|11|139|be|です|
|12|135|is|です|
|13|129|autosar|AUTomotive Open System Architecture(短縮名)|
|14|113|c|c|
|15|108|rs_ap_|rs_ap_|
|16|99|update|更新|
|17|96|by|に|
|18|96|r|r|
|19|94|for|にとって|
|20|90|specification|仕様|
|21|86|group|班|
|22|85|machine|機械|
|23|83|adaptive|適用|
|24|82|this|これ|
|25|81|document|ぶんshお|
|26|80|rs_sm_|rs_sm_|
|27|78|network|通信網|
|28|70|platform|土台|
|29|61|diagnostic|診断|
|30|59|applications|応用|
|31|59|configuration|構成|
|32|59|reset|再設定|
|33|58|ap|adaptive platform(短縮名)|
|34|58|autosar_sws_state|autosar_sws_state|
|35|58|id|identifier, 識別子(短縮名）|
|36|58|interface|界面|
|37|58|that|それ|
|38|57|from|から|
|39|55|are|です|
|40|54|can|できる|
|41|54|not|いいえ|
|42|54|on|の上|
|43|54|with|と|
|44|53|execution|実行|
|45|52|states|状態|
|46|52|will|意思|
|47|50|as|なので|
|48|50|shall|しなければならない|
|49|49|groups|班|
|50|49|request|要求|
|51|47|processes|過程|
|52|46|or|または|
|53|44|draft|原案|
|54|43|description|説明|
|55|43|it|それ|
|56|43|service|奉仕|
|57|42|internal|内部|
|58|42|modelled|模型化|
|59|40|has|もっている|
|60|39|change|変化する|
|61|38|down|下|
|62|37|all|すべて|
|63|36|an|一つの|
|64|36|specific|明確|
|65|36|which|どれの|
|66|35|handle|取り持つ|
|67|35|session|節|
|68|34|application|応用|
|69|34|when|いつ|
|70|33|shut|閉める|
|71|32|cluster|集まる|
|72|31|name|名前|
|73|31|tables|表|
|74|30|constraints|制約|
|75|30|provided|提供した|
|76|30|set|設定する|
|77|30|trace|痕跡|
|78|29|functional|機能的|
|79|29|see|見る|
|80|29|sws_sm_na|sws_sm_na|
|81|27|any|どれか|
|82|27|fields|田畑|
|83|27|interaction|相互作用|
|84|27|managements|経営陣|
|85|26|process|処理する|
|86|26|project|事業|
|87|25|system|系|
|88|24|have|持ってる|
|89|24|type|型|
|90|23|requested|要求された|
|91|22|changed|変わった|
|92|22|health|健康|
|93|22|manifest|管理票|
|94|22|might|かもしれない|
|95|22|other|他の|
|96|22|support|対応|
|97|21|added|追加した|
|98|21|configured|構成した|
|99|21|if|もし|
|100|21|out|外に|

pdftotextが[stateをdstateと誤認識。


# 参照(reference)

[1] Specification of Communication Management, AUTOSAR_SWS_CommunicationManagement
[2] Glossary, AUTOSAR_TR_Glossary
[3] Specification of Execution Management, AUTOSAR_SWS_ExecutionManagement
[4] Specification of Platform Health Management, AUTOSAR_SWS_PlatformHealthManagement
[5] Specification of Network Management, AUTOSAR_SWS_NetworkManagement
[6] Specification of Diagnostics, AUTOSAR_SWS_Diagnostics
[7] Specification of Update and Configuration Management, AUTOSAR_SWS_UpdateAndConfigurationManagement
[8] Specification of Manifest, AUTOSAR_TPS_ManifestSpecification
[9] Requirements of State Management, AUTOSAR_RS_StateManagement