Explanation of Adaptive Platform Design,  AUTOSAR 706, R22-11, AP(2)

Explanation of Adaptive Platform Design,  No.706, AP, AUTOSAR22-11 

AUTOSARは、ISO、IEC、ITUと情報交換契約を結んでいません。
AUTOSAR文書には、ISO、IEC,ITU記述を全文引用することはできません。
WTO/TBT協定に基づき、国際的な調達は国際規格との差異を記述することにより文化依存しない仕様を目指します。
ISO、IEC、ITU文書を合わせて読むと技術内容は理解できます。　
CAN、OSEK/VDX OS、DIAGは、ISO定義を先に確認しましょう。　　
OSEK COM、OSEK NMなどはISOの規定から基本的な部分で定義を変えています。
変更している部分を仕様等で明記するか、ISOを改定するとよいでしょう。　

AUTOSARの参考文献欄の改定が進んでいません。　
Glossary用語定義の網羅性が低いです。
本文を読む前に確認するとよいかもしれません。
本文を読んでから確認してもよいかもしれません。

AUTOSARが、2022年の版、R22-11公開しました。公開行事の模様は

AUTOSAR R22-11 Release Event 20221208

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

下記URL順次確認中です。

https://www.autosar.org/fileadmin/standards/R22-11/AP/AUTOSAR_EXP_PlatformDesign.pdf


間違っていたら、いいね　を押していただいて、コメント欄にご報告くださると幸いです。
編集リクエストが、構造的な変更をしている最中に、構造的な編集リクエストをしていただくと、
何をどう直したらいいかわからなくなってしまいます。自動修復ツールがつくれていません。ごめんなさい。

https://www.autosar.org/


文書は検索してダウンロードすることができます。
クラウドサービスにありがちな、あるのにないかのような検索結果が出ることがあります。

https://www.autosar.org/standards

# 要求/仕様（Requirement and Specification)

# 一覧

AUTOSAR R22-11 Adaptive Platform 一覧はこちら。

Adaptive Platform Release Overview, No.782, AP, AUTOSAR 22-11 新

https://qiita.com/kaizen_nagoya/items/7f8d6ddacc8573351232

Foundation Release Overview, No.781, FO, AUTOSAR 22-11 新

https://qiita.com/kaizen_nagoya/items/7fcfa4aa0786a38ac3d6

Classic Platform Release Overview, AUTOSAR R22-11, CP, No.0(2)

https://qiita.com/kaizen_nagoya/items/80636f4ca7c16501803b

AUTOSAR R22-11 マラソン

https://qiita.com/kaizen_nagoya/items/988aa405a6fdd794fe53

AUTOSAR 文書番号と発行年　

https://qiita.com/kaizen_nagoya/items/871d81b822984be5239d

Qiitaの記事の一覧は作成中です。

AUTOSAR R22-11 一覧（２）

https://qiita.com/kaizen_nagoya/items/6b0615884e954c65fb43

# Abstract Platformとの関係

Adaptive Platform統合
# 文書変更(Document Change) 

>• A new chapter Firewall
• Introduction of State Machine in the
State Management chapter
• Minor updates in Platform Health Management, E2E-Protection, Persistency, Update and Configuration Management and Diagnostics chapters

# 用語
|term|description|
|:--|:--|
| Access Control Decision| The access control decision is a Boolean value indicating if the requested operation is permitted or not. It is based on the identity of the caller and the Access Control Policy.
|Access Control Policy| Access Control Policies are used to define constraints that have to be met in order to access specific objects (e.g. Service Interfaces).
|Policy Decision Point (PDP)| A PDP makes the access control decision. It determines if an Adaptive Application is allowed to perform the requested task by checking the Access Control Policy.
|Policy Enforcement Point (PEP)| A PEP interrupts the control flow during requests from Adaptive Applications by requesting the Access Control Decision from a PDP and enforces this decision.
|Intent| An Intent is a property of an Adaptive Application Identity. Access to an AUTOSAR resource (e.g. Service interface) is granted only if a requesting AA possesses all acknowledged Intents that are mandatory for that specific resource. Intents are assigned to AAs within their Application Manifest.
|Grant| During deployment of Adaptive Applications, each Intent requested in the design phase shall be acknowledged. Grant elements are available in the metamodel. Grants will support integrators to review Intents, but it’s not intended to allow partial acceptance of Intent.
|Intermediate Identifier (IntID)| An identifier that enables the identification of running POSIX-processes and the mapping to modeled AUTOSAR Processes. The concrete nature of IntID depends on the mechanism that is used to authenticate running POSIX processes.
| Adaptive Application Identity (AAID)| The modelled identity of an Adaptive Application is represented by the AUTOSAR Process.
| Adaptive Application Identifier| A referrer to AAID, i.e. AUTOSAR Process, pointing to exactly one AAID.

## 短縮形(short name)
SOA serviceoriented-architecture 

## "14.3 Contents of the AUTOSAR specification"

| Description| Affiliated to| Part of|
|:--|:--|:--|
|Requirement specification for IAM|AUTOSAR Specification| RS_IdentityAndAccessManagement [9]
|Behavioral description of the IAM framework (regarding interfaces) |AUTOSAR specification| SWS_IdentityAndAccessManagement [10]
|API for communication between AAs implementing a PDP and the PEP in the Adaptive Platform |AUTOSAR Specification| SWS_IdentityAndAccessManagement [10]
|API for communication between Functional clusters implementing a PDP and the PEP in the Adaptive Platform.|Not specified by AUTOSAR| -
|The application intents & Access control policies (Manifest file information). |AUTOSAR specification| TPS_Manifest_Specification [11]
|Format and contents of warnings/error messages that the applications receive on failed authorization. |AUTOSAR specification| SWS_IdentityAndAccessManagement [10]|
|API for activity logging| AUTOSAR Specification |Not yet decided|
|Contents of the logging information|AUTOSAR Specification |Not yet decided|
|Interface between Adaptive Application and Functional Clusters| Not specified byAUTOSAR |-|
|Identification of Adaptive Applications during runtime| Not specified byAUTOSAR||



## 英日
日本語は仮訳。

|no.|count|word|日本語|
|:----|:----|:----|:----|
|1|1376|the|その|
|2|779|of|の|
|3|535|to|に|
|4|501|and|と|
|5|404|a|a|
|6|377|is|です|
|7|309|in|の|
|8|255|for|にとって|
|9|248|adaptive|適用|
|10|244|platform|土台|
|11|213|be|なれ|
|12|191|autosar|AUTomotive Open System Architecture(短縮名)|
|13|184|management|管理|
|14|181|ap|application(短縮名)|
|15|169|or|また|
|16|162|by|に|
|17|159|are|それは|
|18|159|that|それ|
|19|157|software|ソフトウェア|
|20|148|application|応用|
|21|145|on|の上|
|22|138|an|と|
|23|135|as|なので|
|24|129|design|設計|
|25|120|ucm|Update and Configuration Management(短縮名)|
|26|108|it|それ|
|27|107|document|資料|
|28|104|service|奉仕|
|29|102|from|から|
|30|99|this|これ|
|31|97|applications|応用|
|32|97|package|小包|
|33|96|can|できる|
|34|95|with|と|
|35|94|data|与件|
|36|90|communication|通信|
|37|90|not|いいえ|
|38|89|id|identifier, 識別子(短縮名）|
|39|89|r|r|
|40|88|explanation|説明|
|41|85|autosar_exp_platformdesign|autosar_exp_platformdesign|
|42|80|manifest|管理票|
|43|79|system|系|
|44|76|ara|AUTOSAR Runtime for Adaptive Applications(短縮形)|
|45|75|e|e|
|46|75|vehicle|車両|
|47|74|execution|実行|
|48|71|functional|機能的|
|49|67|interface|界面|
|50|65|time|時間|
|51|63|update|更新|
|52|63|which|どれの|
|53|61|state|状態|
|54|59|cluster|房|
|55|58|access|接続|
|56|58|other|他の|
|57|56|process|処理する|
|58|51|also|また|
|59|51|machine|機械|
|60|51|such|そのような|
|61|51|will|意思|
|62|50|safety|安全性|
|63|49|architecture|建築|
|64|49|master|主人|
|65|48|api|application programming interface(短縮形)|
|66|48|use|使用する|
|67|48|used|使用済み|
|68|47|based|基づく|
|69|47|configuration|構成|
|70|47|if|もしも|
|71|46|diagnostic|診断|
|72|45|information|情報|
|73|45|may|かもしれない|
|74|45|specification|仕様|
|75|44|core|芯|
|76|44|interfaces|界面|
|77|43|all|すべて|
|78|43|back|戻る|
|79|43|client|顧客|
|80|43|error|誤り|
|81|43|health|健康|
|82|43|provides|提供する|
|83|43|storage|記録|
|84|42|figure|形|
|85|42|implementation|実装|
|86|42|processes|過程|
|87|42|these|これらは|
|88|42|types|型|
|89|41|c|c|
|90|40|has|もっている|
|91|40|instance|実例|
|92|40|network|通信網|
|93|40|specific|明確|
|94|39|at|で|
|95|39|clusters|房|
|96|39|defined|定義済み|
|97|39|different|違う|
|98|39|end|終わり|
|99|39|only|それだけ|
|100|38|overview|概要|
|101|38|shall|しなければならない|


# 参照（reference)
[1] Glossary, AUTOSAR_TR_Glossary
https://www.autosar.org/fileadmin/standards/foundation/22-11/AUTOSAR_TR_Glossary.pdf
[2] Main Requirements, AUTOSAR_RS_Main
[3] Methodology for Adaptive Platform, AUTOSAR_TR_AdaptiveMethodology
[4] Explanation of Adaptive Platform Software Architecture, AUTOSAR_EXP_SWArchitecture
[5] The 4+1 View Model of Architecture
[6] Specification of Execution Management, AUTOSAR_SWS_ExecutionManagement
[7] Specification of Platform Types for Adaptive Platform, AUTOSAR_SWS_AdaptivePlatformTypes
[8] Specification of Synchronized Time-Base Manager, AUTOSAR_SWS_SynchronizedTimeBaseManager
[9] Requirements on Identity and Access Management, AUTOSAR_RS_IdentityAndAccessManagement
[10] Specification of Identity and Access Management, AUTOSAR_SWS_IdentityAndAccessManagement
[11] Specification of Manifest, AUTOSAR_TPS_ManifestSpecification
[12] Explanation of Safety Overview, AUTOSAR_EXP_SafetyOverview
[13] Safety Requirements for AUTOSAR Adaptive Platform and AUTOSAR Classic
Platform, AUTOSAR_RS_Safety
[14] ISO 26262:2018 (all parts) – Road vehicles – Functional Safety, http://www.iso.org
[15] E2E Protocol Specification, AUTOSAR_PRS_E2EProtocol
[16] Specification of Communication Management, AUTOSAR_SWS_CommunicationManagement
[17] Requirements on Health Monitoring, AUTOSAR_RS_HealthMonitoring
[18] Specification of Health Monitoring, AUTOSAR_ASWS_HealthMonitoring
[19] Requirements on Platform Health Management, AUTOSAR_RS_PlatformHealthManagement
[20] Specification of Platform Health Management AUTOSAR_SWS_PlatformHealthManagement



# 関連文書(Related document)

AUTOSAR Abstract Platformへの道（詳細編）

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

2023年1月　記事数一覧

https://qiita.com/kaizen_nagoya/items/78153968c5de76a7fd83

年末100記事を30点に仕上げる。

https://qiita.com/kaizen_nagoya/items/3ffdc82caee3a325d1d7

2023 書き初め

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

「はじめての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

AUTOSAR Abstract Platform User Group Weekly Report(1) 2022.1.8

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

AUTOSAR Abstract Platform User Group Weekly Report(2) 2022.1.15

https://qiita.com/kaizen_nagoya/items/6f1168a36e795976a906
# R23-11
https://qiita.com/kaizen_nagoya/items/6bb6621ca9c667a52d78

 ＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞

# 文書履歴(document history)
ver. 0.01 初稿 20230130


# 文書履歴(document history)
ver. 0.01 初稿 　20240103
### 最後までおよみいただきありがとうございました。
いいね　💚、フォローをお願いします。
#### Thank you very much for reading to the last sentence.
Please press the like icon 💚　and follow me for your happy life.