Specification of Diagnostics, AUTOSAR 723, R22-11 AP(2)

Specification of Diagnostics, AUTOSAR R21-11, AP, No.723

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_SWS_Diagnostics.pdf

22-11がなかなか文書を表示しない。原因、解決方法とも不明。
https://www.autosar.org/fileadmin/standards/adaptive/21-11/AUTOSAR_SWS_Diagnostics.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との関係
Template, TypeはAbstract Platformで統一的に定義するとよい。　
Template, Typeで、複数の文書を統合するとよい。

＃ 文書変更(Document Change) 
22-11がなかなか文書を表示しない。原因、解決方法とも不明。

• Document quality improvement and fixing bugs
• Incorporated Quality Scope Review Findings
• Introduced DTC suppressed feature
• Standardize mapping of vendor
specific error codes to UDS Error
codes
• Introduced 0x38 RequestFileTransfer
• Introduced SOVD Concept

# Diagnosticsを中心に。
今年は、Diagnosticsを中心に
CAN,Ethernet
OSEK,POSIX/LINUX
セキュリティ、不揮発性メモリ
という４段階に分けて整理する。

C言語、C+＋について言及できるところまで具体化する予定。

|platform|Title|number|URL|Qiita|
|:--|:--|:--|:--|:--|
|F|Requirements on Diagnostics|4|https://www.autosar.org/fileadmin/user_upload/standards/foundation/21-11/AUTOSAR_RS_Diagnostics.pdf|3 https://qiita.com/kaizen_nagoya/items/fce079cfd7ce9f6ee4ca|
|C|Specification of Diagnostic Communication Manager|18|https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_SWS_DiagnosticCommunicationManager.pdf| |
|C|Specification of Diagnostic Event Manager|19|https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_SWS_DiagnosticEventManager.pdf| |
|F|Main Requirements|54|https://www.autosar.org/fileadmin/user_upload/standards/foundation/21-11/AUTOSAR_RS_Main.pdf|2 https://qiita.com/kaizen_nagoya/items/54a9d90272d901ecc089|
|F|Glossary|55|https://www.autosar.org/fileadmin/user_upload/standards/foundation/21-11/AUTOSAR_TR_Glossary.pdf|1 https://qiita.com/kaizen_nagoya/items/9eaf0c2a82a39c356f92|
|F|Requirements on Log and Trace|350|https://www.autosar.org/fileadmin/user_upload/standards/foundation/21-11/AUTOSAR_RS_LogAndTrace.pdf|4 https://qiita.com/kaizen_nagoya/items/98fde7ffbef358fcf2ed|
|C|Specification of Diagnostic Log and Trace|351|https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_SWS_DiagnosticLogAndTrace.pdf| |
|C|Specification of Diagnostic over IP|418|https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_SWS_DiagnosticOverIP.pdf| |
|C|Specification of a Diagnostic Communication Manager for SAE J1939|610|https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_SWS_SAEJ1939DiagnosticCommunicationManager.pdf| |
|C|Acceptance Test Specification of Diagnostic Services|627|https://www.autosar.org/fileadmin/user_upload/standards/tests/1-2/AUTOSAR_ATS_DiagnosticServices.pdf| |
|C|Diagnostic Extract Template|673|https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_TPS_DiagnosticExtractTemplate.pdf| |
|C|Requirements on Diagnostic Extract Template|681|https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_RS_DiagnosticExtractTemplate.pdf| |
|A|Specification of Manifest AUTOSAR_TPS_ManifestSpecification|713|https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_TPS_ManifestSpecification.pdf| |
|A|Specification of Execution Management AUTOSAR_SWS_ExecutionManagement|721|https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_SWS_ExecutionManagement.pdf| |
|A|Specification of Diagnostics|723|https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_SWS_Diagnostics.pdf|6 https://qiita.com/kaizen_nagoya/items/ed65d04518231c2df96d|
|A|Log and Trace Protocol Specification|787|https://qiita.com/kaizen_nagoya/items/724143aa4e529e3fd079|5 https://qiita.com/kaizen_nagoya/items/724143aa4e529e3fd079|
|A|Specification of Log and Trace|853|https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_SWS_LogAndTrace.pdf| |
|A|Specification of Persistency AUTOSAR_SWS_Persistency|858|https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_SWS_Persistency.pdf| |
|A|Specification of Adaptive Platform Core AUTOSAR_SWS_AdaptivePlatformCore
|903|https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_SWS_AdaptivePlatformCore.pdf
| |

# 用語(term)

|Term|Description|
|:--|:--|
|AA |AUTOSAR Adaptive Application
|AP |AUTOSAR Adaptive Platform
|Channel |An abstraction of a network specific communication channel. In CAN networks a Channel can be identified via CAN identifier. In Ethernet networks a Channel might be defined by the quadruple Src-IP, Src-Port, Target-IP, Target-Port.
|CP| AUTOSAR Classic Platform
|DEXT| AUTOSAR Diagnostic Extract[3], describing diagnostic configuration of an ECU
|DM |AUTOSAR Adaptive Diagnostic Management
|DTC| Diagnostic Trouble Code according to ISO 14229-1[1]
|DDID |Dynamically Defined Data Identifier according to ISO 14229-1[1].
|DID| Data Identifier according to ISO 14229-1[1]. This 16 bit value uniquely defines one ore more data elements (parameters) that can are used in diagnostics to read, write or control data.
|ECU| Electronic control unit
|EDR| Extended Data Record
|Execution Management| Functional cluster Execution Management
|FDC |Fault Detection Counter according to 14229-1[1]. Has always the value range from -128 = FDCmin = "FinallyHealed" to +127 = FDCmax = "FinallyDefective"
|GID| Group identifier as used in DoIP
|MetaInfo| Meta-Information in the form of a key-value map, which is given from DM to external service processors.
|NRC |Negative Response Code used by UDS in the diagnostic response to indicate the tester that a certain failure has occurred and the diagnostic request was not processed.
|OBD| "On-Board Diagnostics"; Generally: A vehicles ability for self diagnosis and reporting to external test tools. Specifically here, the protocol is meant, as defined in SAE J1979, ISO 15031, ISO 27145 and others.
|OEM |"Original Equipment Manufacturer", but in this document herein, it is used for "Vehicle Manufacturer".
|PDID |Periodic Data Identifier according to ISO 14229-1[2].
|PowerMode| Vehicle basic status information retrieval of DoIP
|SA| SourceAddress of a UDS request
|SID |Service Identifier, identifying a diagnostic service according to UDS, such as 0x14 ClearDiagnosticInformation
|TA| TargetAddress of a UDS request
|UDS| Unified Diagnostic Services
|VIN |Vehicle Identification Number according to ISO-3779
|Dcm| Diagnostic Communication Manager (Module of the AUTOSAR Classic Platform)
|DoIP| Diagnostics over Internet Protocol (Communication protocol of automotive electronics according to ISO-13400[5])
|Aging| Unlearning/deleting of a no longer failed event/DTC after a defined number of operation cycles from event memory.
|Diagnostic Client| A Diagnostic Client is a diagnostic service requester, i.e. sends a UDS request to the Diagnostic Server. Usually the Diagnostic Client is an external tester equipment but can also be another vehicle internal ECU.
|Diagnostic Communication Management|Diagnostic Communication Management is the part of the Diagnostic Management which belongs to tester communication and the processing of UDS services.
|Diagnostic Conversation| Diagnostic Conversation represents a conversation between Diagnostic Client (Tester) and Diagnostic Server.
|Diagnostic Event Management| Diagnostic Event Management is the part of the Diagnostic Management which belongs to processing and storing of diagnostic events and associated data.
|Diagnostic Management| Diagnostic Management is a placeholder for the complete functionality of diagnostic communication and event handling.
|Diagnostic Server instance| Diagnostic Server (DM) is intended to support an own Diagnostic Server instance per installed SoftwareCluster, see section 7.5 for a detailed description. Each of those Server instances has and manages its own resources and is responsible for dispatching and processing of diagnostic services.
|Diagnostic Service instance| A diagnostic service instance implements a concrete use of a diagnostic service in a given context. It refers to a DiagnosticServiceClass and the DiagnosticAccessPermission , see 7.5.1.5.3 for a detailed description.
|Displacement| In case of an Event memory overflow: Replacing the most insignificant stored event memory entry by a reported event which needs to be stored and is more significant.
|DTC group| Uniquely identifies a set of DTCs. A DTC group is mapped to the range of valid DTCs. By providing a group of DTCs it is expressed that a certain operation is requested on all DTCs of that group. The DTC group definition is provided by ISO 14229-1[1] and OEM/supplier-specific.
|DTCStatusAvailabilityMask| The DTCStatusAvailabilityMask - byte is used in UDS responses to requests for certain sub-functions of service 0x19. It express which of the UDS DTC status bits are supported by the DM for masking purposes.
|Enable Conditions| The criteria / conditions under which the test results from the monitors in the AA’s are valid and shall be processed by DM. Configuration is done per event.
|Extended Data Records| Contains statistical data for a DTC. Extended data records are assigned to DTCs and maintained and stored by the DM.
|Event |An event (also diagnostic event) uniquely identifies a fault path of the system. An application monitors the system and reports events to the DM.
|Event memory |The DM stores information about events in the event memory. There can be multiple event memories, each keeping information independently from each other. Examples of the event memory is the UDS primary event memory or the up to 256 user-defined event memories.
|Event memory overflow |An event memory overflow occurs, if this specific event memory is full and the next event occurs to be stored in this event memory.
|Event status| Bit-packed status information based on Event level. Contains the following bits: Nr. Definition: • 0 testFailed • 1 testFailedThisOperationCycle • 6 testNotCompletedThisOperationCycle Compare UDS DTC status bit
|Fail-safe reaction| (Sometimes also called "limp home mode"): Reaction to avoid or minimize harm or damage in case of a failure.
|GroupOfAllDTCs |Identifies a special DTC group that contains all DTCs. This DTC group is identified by the DTC value 0xFFFFFF in 14229-1[1] and contains by default all DTCs of a fault memory. It is present by default in the DM and requires no configuration.
|Internal, External| Classifies if a DiagnosticDataElement is either managed internally inside DM or by an external adaptive applications, see 7.5.4.1 for the precise definition.
|Internally, Externally| Definition of the support type of a SID by the DM. Internally means processing is done by DM itself, Externally means an external service processor is used.
|internal data element| A DiagnosticDataElement which is provided by the DM itself. See also 7.5.4.1.
|Monitor| A monitor (also diagnostic monitor) is a piece of software running within an application, monitoring the correct functionality of a certain system part. The result of such a function check is reported to the DM in form of a diagnostic event.
|Operation cycle| A new operation cycle is the start of a new monitoring cycle. This is reflected in a reset of the testFailedThisOperationCycle and testNotCompletedThisOperationCycle bits in the DTC status and optional notification to the monitor to restart the monitoring.
|Primary event memory| The primary event memory is used to store events and event related data. It is typically used by OEMs for after sales purposes, containing information to repair the vehicle.
|Snapshot Record |Set of measurement values stored in the fault memory at a certain point of time during fault detection. It is used to gain environmental data information for occurred faults.
|SoftwareCluster| A SoftwareCluster groups all AUTOSAR artifacts which are relevant to deploy software on a machine. This includes the definition of applications, i.e. their executables, application manifests, communication and diagnostics. In the context of diagnostics a SoftwareCluster can be addressed individually by its own set of diagnostic addresses.
|SourceAddress| A Source Address is used to encode client and server identifiers. In a UDS request the source address encodes the Diagnostic Client whereas the source address in a UDS response encodes the Diagnostic Server.
|TargetAddress |A Target Address is used to encode client and server identifiers. In a UDS request the target address encodes the Diagnostic Server whereas the target address in a UDS response encodes the Diagnostic Client.
|Transport Protocol Handler |A subcomponent of DM implementing a particular Transport Protocol (either DoIP or any other proprietary UDS Transport Layer).
|Transport Protocol Manager| Link between UDS Transport Layer and Application Layer.
|UDS service| A diagnostic service as defined in ISO 14229-1[1].
|UDS DTC status bit |UDS DTC status bit as defined in ISO 14229-1[1] Annex D.2; Each single bit position represents and documents a certain status information for the connected DTC. The following eight bits are defined: Nr: Definition: 0 testFailed 1 testFailedThisOperationCycle 2 pendingDTC 3 confirmedDTC 4 testNotCompletedSinceLastClear 5 testFailedSinceLastClear 6 testNotCompletedThisOperationCycle 7 warningIndicatorRequested All eight bits constitute the UDS DTC status byte. Compare Event status 
|UDS DTC status byte |Bit-packed DTC status information byte as defined in ISO 14229- 1[1], based on DTC level. Contains the UDS DTC status bits.
|User-defined event memory |The user-defined event/fault memory is used by the UDS service 0x19 with subfunctions 0x17, 0x18 and 0x19. It behaves as the primary event memory but contains data independent from the primary fault memory. It is used to store information that are relevant for different purposes such as warranty or development.
|Non-volatile Memory |In the context of DM, Non-volatile Memory refers to the persistent information over the shutdown of the DM process. This does not depend on HW details.


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

|no.|count|word|日本語|
|:----|:----|:----|:----|
|1|4807|the|その|
|2|4776|sws_dm_|sws_dm_|
|3|3295|of|の|
|4|2821|diag|diagnostic(短縮名）|
|5|2304|uds|uds|
|6|2248|to|に|
|7|2020|diagnostic|診断|
|8|1610|ara|AUTOSAR Runtime for Adaptive Applications(短縮名|
|9|1418|a|一つの|
|10|1217|x|x|
|11|1143|nrc|Negative Response Code（短縮名）|
|12|1135|rs_diag_|rs_diag_|
|13|1101|in|の|
|14|1076|is|です|
|15|1017|draft|下男|
|16|1015|for|にとって|
|17|945|c|c|
|18|937|data|与件|
|19|874|class|級|
|20|866|error|誤り|
|21|845|return|戻る|
|22|809|according|によると|
|23|796|event|行事|
|24|792|function|働き|
|25|769|code|符号|
|26|769|iso|International Organization for Standardization(短縮名）|
|27|761|domain|領域|
|28|750|this|これ|
|29|749|and|と|
|30|749|service|奉仕|
|31|714|d|d|
|32|705|shall|しなければならない|
|33|682|negative|否定的|
|34|675|autosar|AUTomotive Open System Architecture(短縮名)|
|35|615|errc|error code(短縮名）|
|36|605|dtc|Diagnostic Trouble Code(短縮名）|
|37|590|id|identifier, 識別子(短縮名）|
|38|583|instance|実例|
|39|566|interface|界面|
|40|552|dm|diagnostic message(短縮名）|
|41|536|specification|仕様|
|42|529|if|もし|
|43|522|r|r|
|44|517|kind|親切|
|45|516|by|に|
|46|516|diagnostics|診断|
|47|516|document|資料|
|48|515|identifier|識別子|
|49|513|on|の上|
|50|498|ap|adaptive platform(短縮名)|
|51|480|autosar_sws_diagnostics|autosar_sws_diagnostics|
|52|469|be|です|
|53|468|description|説明|
|54|460|type|型|
|55|459|value|価値|
|56|453|element|要素|
|57|440|header|見出し|
|58|440|symbol|像|
|59|432|an|と|
|60|432|status|状態|
|61|431|scope|範囲|
|62|429|core|芯|
|63|427|file|紙ばさみ|
|64|418|include|含む|
|65|413|h|h|
|66|412|syntax|構文|
|67|401|with|と|
|68|398|request|要求|
|69|388|server|奉仕者|
|70|374|transport|輸送|
|71|365|response|応答|
|72|354|message|伝言|
|73|354|meta|超|
|74|333|atp|AUTOSAR Template Profile(短縮名）|
|75|324|or|または|
|76|319|not|ない|
|77|309|no|いいえ|
|78|286|name|名前|
|79|284|conversation|会話|
|80|284|rs_ap_|rs_ap_|
|81|282|as|なので|
|82|278|security|あんしん|
|83|275|processing|処理|
|84|271|info|information(短縮名）|
|85|267|memory|記憶装置|
|86|264|information|情報|
|87|264|note|覚書|
|88|264|port|港|
|89|261|std|standard(短縮名）|
|90|260|uds_transport|uds_transport|
|91|257|set|設定する|
|92|250|that|それ|
|93|244|from|から|
|94|244|tags|札|
|95|236|cancellation|取り消し|
|96|234|monitor|監視|
|97|229|handler|扱う人|
|98|225|space|空間|
|99|218|application|応用|
|100|217|session|節|

pdftotextが、[ifをdifと認識。

# Reference 
参照の仕方が駄々草。国際規格の番号を記載していない。なにしてくれちゃうんだAUTOSAR。

AUTOSAR文書の番号を記載していない。

[1] Unified diagnostic services (UDS) – Part 1: Specification and requirements (Release 2013-03) http://www.iso.org
[2] Unified diagnostic services (UDS) – Part 1: Application layer (Release 2020-02) http://www.iso.org
[3] Diagnostic Extract Template, AUTOSAR_TPS_DiagnosticExtractTemplate
[4] Glossary, AUTOSAR_TR_Glossary
https://www.autosar.org/fileadmin/standards/foundation/22-11/AUTOSAR_TR_Glossary.pdf
[5] Road vehicles – Diagnostic communication over Internet Protocol (DoIP), http://www.iso.org
[6] Specification of Adaptive Platform Core, AUTOSAR_SWS_AdaptivePlatformCore
[7] Specification of Execution Management, AUTOSAR_SWS_ExecutionManagement
[8] Specification of Log and Trace, AUTOSAR_SWS_LogAndTrace
[9] Specification of Persistency, AUTOSAR_SWS_Persistency
[10] Requirements on Diagnostics, AUTOSAR_RS_Diagnostics
[11] Road vehicles – Diagnostics on Controller Area Networks (CAN) – Part2: Network layer services
[12] Road vehicles – Diagnostic communication over Internet Protocol (DoIP) – Part 2: Network and transport layer requirements and services, http://www.iso.org
[13] Specification of Manifest, AUTOSAR_TPS_ManifestSpecification
[14] Unified diagnostic services (UDS) - Part 2: Session layer services (Release 2013-03), http://www.iso.org


### [1] 
Unified diagnostic services (UDS) – Part 1: Specification and requirements (Re- lease 2013-03)
http://www.iso.org


ISO 14229-1:2013
Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements

https://www.iso.org/standard/55283.html

### [2] 
Unified diagnostic services (UDS) – Part 1: Application layer (Release 2020-02) http://www.iso.org

ISO 14229-1:2020
Road vehicles — Unified diagnostic services (UDS) — Part 1: Application layer

https://www.iso.org/standard/72439.html 

### [3] 
Diagnostic Extract Template AUTOSAR_TPS_DiagnosticExtractTemplate

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

### [4] 
Glossary AUTOSAR_TR_Glossary

https://www.autosar.org/fileadmin/user_upload/standards/foundation/21-11/AUTOSAR_TR_Glossary.pdf

### [5] 
Road vehicles – Diagnostic communication over Internet Protocol (DoIP) http://www.iso.org

Partを記載しない場合は、全Partを意味する。しかし、


ISO 13400-1:2011
Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 1: General information and use case definition

は、すでに廃止している。これを含むか、含まないかの注記をしないのは不親切かも。

ISO 13400-2:2019/CD AMD 1
Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 2: Transport protocol and network layer services — Amendment 1

https://www.iso.org/standard/84208.html


ISO 13400-3:2016
Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 3: Wired vehicle interface based on IEEE 802.3

https://www.iso.org/standard/68424.html

ISO 13400-4:2016
Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 4: Ethernet-based high-speed data link connector

https://www.iso.org/standard/57317.html

### [6] 
Specification of Adaptive Platform Core AUTOSAR_SWS_AdaptivePlatformCore
903

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


### [7] 
Specification of Execution Management AUTOSAR_SWS_ExecutionManagement
721

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

### [8] 
Specification of Log and Trace AUTOSAR_SWS_LogAndTrace
853

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

### [9] 
Specification of Persistency AUTOSAR_SWS_Persistency
858

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

### [10] 
Requirements on Diagnostics AUTOSAR_RS_Diagnostics
4

https://www.autosar.org/fileadmin/user_upload/standards/foundation/21-11/AUTOSAR_RS_Diagnostics.pdf

### [11] 
Road vehicles – Diagnostics on Controller Area Networks (CAN) – Part2: Network layer services

ISO 15765-2:2004
Road vehicles — Diagnostics on Controller Area Networks (CAN) — Part 2: Network layer services

https://www.iso.org/standard/33616.html

標題かすると上記。７年後に改定している。どっちのつもりか不明。

ISO 15765-2:2011
Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 2: Transport protocol and network layer services

https://www.iso.org/standard/54499.html

### [12] 
Road vehicles – Diagnostic communication over Internet Protocol (DoIP) – Part 2: Network and transport layer requirements and services
http://www.iso.org

この文字列の国際規格は検索で出て来ない。ひょうっとしたら

ISO 13400-2:2012
Road vehicles - Diagnostic communication over Internet Protocol (DoIP) — Part 2: Transport protocol and network layer services

https://www.iso.org/standard/53766.html

ISO 13400-2:2019
Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 2: Transport protocol and network layer services

https://www.iso.org/standard/74785.html

### [13] 
Specification of Manifest AUTOSAR_TPS_ManifestSpecification
713

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

### [14] 
Unified diagnostic services (UDS) - Part 2: Session layer services (Release 2013- 03)
http://www.iso.org


ISO 14229-2:2013 
Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services

https://www.iso.org/standard/45763.html

なんで2021を参照しないんだろう。

ISO 14229-2:2021
Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services

https://www.iso.org/standard/77322.html

# 参考資料
@kazuo_reve AUTOSARのClassic PlatformとAdaptive PlatformにおけるDiagnosticsの違いを整理
https://qiita.com/kazuo_reve/items/05c179d705c69286b94a

自動車の故障診断に関連するプログラマーになりたての方が参照するとよさそうな情報
https://qiita.com/kazuo_reve/items/f773b320dcbf2ab316da

## 自己参照
@kazuo_reveさんの「自動車の故障診断に関連するプログラマになりたての方が参照するとよさそうな情報」の読み方
https://qiita.com/kaizen_nagoya/items/0c6b8373f93ce52def33

# 関連文書(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

物理記事　上位100
https://qiita.com/kaizen_nagoya/items/66e90fe31fbe3facc6ff

数学関連記事１００
https://qiita.com/kaizen_nagoya/items/d8dadb49a6397e854c6d

言語・文学記事　１００
https://qiita.com/kaizen_nagoya/items/42d58d5ef7fb53c407d6

医工連携関連記事一覧
https://qiita.com/kaizen_nagoya/items/6ab51c12ba51bc260a82

通信記事１００
https://qiita.com/kaizen_nagoya/items/1d67de5e1cd207b05ef7

自動車　記事　１００
https://qiita.com/kaizen_nagoya/items/f7f0b9ab36569ad409c5

小川清最終講義、小川清最終講義（再）計画, Ethernet(100) 英語(100) 安全(100)
https://qiita.com/kaizen_nagoya/items/e2df642e3951e35e6a53
# R23-11
https://qiita.com/kaizen_nagoya/items/ace39fa09356166bfdf7

 ＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞
# 文書履歴(document history)
ver. 0.01 初稿　
### 最後までおよみいただきありがとうございました。
いいね　💚、フォローをお願いします。
#### Thank you very much for reading to the last sentence.
Please press the like icon 💚　and follow me for your happy life.