Project Objectives, AUTOSAR 22-11, FO, No.599
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
下記URL順次確認中です。
下記は想定URLです。まだ公開していなければごめんなさい。
文書は、廃止になっていなければ、2022年12月8日(たぶんヨーロッパ時間)以降に検索してダウンロードできるはずです。
要求/仕様（Requirement and Specification)
一覧
AUTOSAR R22-11 Foundation(Abstract Platform) 一覧はこちら。
Foundation Release Overview, No.781, FO, AUTOSAR 22-11(2)
AUTOSAR R22-11 マラソン
Qiitaの記事の一覧は作成中です。
AUTOSAR R22-11 一覧（２）
Abstract Platformとの関係
FO基本文書の統合。
<この項は書きかけです。順次追記します。>
文書変更(Document Change)
No content changes
用語(terms)
| Term | Description |
|---|---|
| MUST | This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification. |
| MUST NOT | This phrase, or the phrase „SHALL NOT“, means that the definition is an absolute prohibition of the specification. |
| SHOULD | This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. |
| SHOULD NOT | This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. |
| MAY | This word, or the adjective „OPTIONAL“, means that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation, which does not include a particular option, MUST be prepared to interoperate with another implementation, which does include the option, though perhaps with reduced functionality. In the same vein an implementation, which does include a particular option, MUST be prepared to interoperate with another implementation, which does not include the option (except, of course, for the feature the option provides.) |
英日
日本語は仮訳
| no. | count | word | 日本語 |
|---|---|---|---|
| 1 | 96 | the | その |
| 2 | 86 | autosar | autosar |
| 3 | 66 | of | の |
| 4 | 45 | and | と |
| 5 | 38 | to | に |
| 6 | 30 | shall | しなければならない |
| 7 | 27 | rs_po_ | rs_po_ |
| 8 | 26 | document | 文書 |
| 9 | 25 | objectives | 目的 |
| 10 | 25 | project | 事業 |
| 11 | 24 | in | の |
| 12 | 23 | be | です |
| 13 | 23 | software | ソフトウェア |
| 14 | 21 | release | 開放 |
| 15 | 19 | for | にとって |
| 16 | 18 | management | 管理 |
| 17 | 18 | or | または |
| 18 | 18 | r | r |
| 19 | 16 | changes | 変更 |
| 20 | 16 | this | これ |
| 21 | 15 | support | 対応 |
| 22 | 14 | a | 一つの |
| 23 | 14 | requirements | 要件 |
| 24 | 13 | automotive | 自動車 |
| 25 | 13 | by | に |
| 26 | 13 | is | です |
| 27 | 12 | systems | 系 |
| 28 | 11 | an | 一つの |
| 29 | 11 | are | です |
| 30 | 11 | from | から |
| 31 | 11 | id | id |
| 32 | 11 | material | 材料 |
| 33 | 11 | no | いいえ |
| 34 | 11 | not | いいえ |
| 35 | 11 | which | どの |
| 36 | 11 | with | と |
| 37 | 10 | autosar_rs_projectobjectives | autosar_rs_projectobjectives |
| 38 | 10 | content | 内容 |
| 39 | 10 | description | 説明 |
| 40 | 10 | different | 違う |
| 41 | 10 | fo | foundation(短縮名) |
| 42 | 10 | use | 使う |
| 43 | 10 | valid | 有効 |
| 44 | 9 | any | どれか |
| 45 | 9 | case | 場合 |
| 46 | 9 | iso | iso |
| 47 | 8 | dependencies | 依存関係 |
| 48 | 8 | editorial | 編集上の |
| 49 | 8 | hardware | ハードウェア |
| 50 | 8 | may | かもしれない |
| 51 | 8 | rationale | 根拠 |
| 52 | 8 | supporting | 対応 |
| 53 | 8 | that | それ |
| 54 | 8 | type | 型 |
| 55 | 8 | used | 使った |
| 56 | 7 | across | 横切って |
| 57 | 7 | architecture | 建築 |
| 58 | 7 | must | しなければならない |
| 59 | 7 | particular | 特に |
| 60 | 7 | vehicles | 車両 |
| 61 | 7 | work | 仕事 |
| 62 | 6 | application | 応用 |
| 63 | 6 | as | なので |
| 64 | 6 | can | できる |
| 65 | 6 | implementation | 実装 |
| 66 | 6 | it | それ |
| 67 | 6 | network | 通信網 |
| 68 | 6 | partners | 提携者 |
| 69 | 6 | should | したほうがいい |
| 70 | 6 | standards | 基準 |
| 71 | 5 | between | の間に |
| 72 | 5 | development | 発達 |
| 73 | 5 | domain | 領域 |
| 74 | 5 | e | e |
| 75 | 5 | ecus | ecus |
| 76 | 5 | enable | 有効 |
| 77 | 5 | exchange | 両替 |
| 78 | 5 | has | 持つ |
| 79 | 5 | include | 含む |
| 80 | 5 | non | 非 |
| 81 | 5 | option | 選択肢 |
| 82 | 5 | road | 道 |
| 83 | 5 | specific | 明確 |
| 84 | 5 | standard | 標準 |
| 85 | 5 | system | 系 |
| 86 | 5 | technical | 技術的な |
| 87 | 5 | technologies | 技術 |
| 88 | 5 | vehicle | 車両 |
| 89 | 4 | applicable | 該当する |
| 90 | 4 | art | 美術 |
| 91 | 4 | change | 変化する |
| 92 | 4 | changed | かわった |
| 93 | 4 | data | 与件 |
| 94 | 4 | does | する |
| 95 | 4 | functional | 機能的 |
| 96 | 4 | future | 将来 |
| 97 | 4 | item | 項目 |
| 98 | 4 | means | 意味 |
| 99 | 4 | on | の上 |
| 100 | 4 | only | だけ |
| 101 | 4 | open | 開いた |
| 102 | 4 | phrase | 段階 |
| 103 | 4 | product | 製品 |
| 104 | 4 | recommended | お勧めの |
| 105 | 4 | sae | sae |
| 106 | 4 | state | 状態 |
| 107 | 4 | update | 更新 |
| 108 | 4 | word | 語 |
参考(reference)
[Glossary] AUTOSAR Glossary, AUTOSAR_TR_Glossary.pdf
https://www.autosar.org/fileadmin/standards/R22-11/FO/AUTOSAR_TR_Glossary.pdf
[IEEEElecEng] The Electrical Engineering Handbook, Editor R. C. Dorf, CRC Press
4th Edition
[ISO 11898] Road vehicles — Controller area network (CAN)
[ISO 14229] Road vehicles — Unified diagnostic services (UDS)
[ISO 15765] Road vehicles -- Diagnostic communication over Controller Area Network (DoCAN)
[ISO 26262] Road vehicles — Functional safety
[ISO 27145] Road vehicles — Implementation of WWH-OBD communication requirements
ISO 27145-1:2012
Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements — Part 1: General information and use case definition
2 Normative references
ISO 14229-1, Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements
ISO 14229-2, Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services
ISO 27145-2, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements — Part 2: Common data dictionary
ISO 27145-3, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements — Part 3: Common message dictionary
ISO 27145-4, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements — Part 4: Connection between vehicle and test equipment
Bibliography
[1] ISO 11898-1, Road vehicles — Controller area network (CAN) — Part 1: Data link layer and physical signalling
[2] ISO 11898-2, Road vehicles — Controller area network (CAN) — Part 2: High-speed medium access unit
[3] ISO 13400 (all parts), Road vehicles — Diagnostic communication over Internet Protocol (DoIP)
[4] ISO 15031 (all parts), Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics
[5] ISO 15765-2, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 2: Transport protocol and network layer services
[6] ISO 15765-4, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 4: Requirements for emissions-related systems
[7] ISO/IEC 7498-1, Information technology — Open Systems Interconnection — Basic Reference Model: The Basic Model
[8] ISO/IEC 10731, Information technology — Open Systems Interconnection — Basic Reference Model — Conventions for the definition of OSI services
[9] IEEE 802.3, IEEE Standard for Information technology — Specific requirements — Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications
[10] SAE J1930-DA, Electrical/Electronic Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms Web Tool Spreadsheet
[11] SAE J1939-73, Recommended Practice for a Serial Control and Communications Vehicle Network — Application Layer Diagnostics
[12] SAE J1939, Companion Spreadsheet
[13] SAE J1979-DA, Digital Annex of E/E Diagnostic Test Modes
[14] SAE J2012-DA, Diagnostic Trouble Code Definitions
[15] CCR 1968.2 Title 13, California Code Regulations, Section 1968.2, Malfunction and Diagnostic System Requirements for 2004 and Subsequent Model-Year Passenger Cars, Light-Duty Trucks, and Medium-Duty Vehicles and Engines (OBD II), available at: http://www.arb.ca.gov/msprog/obdprog/obdregs.htm
[16] CCR 1971.1 Title 13, California Code Regulations, Section 1971.1, On-Board Diagnostic System Requirements for 2010 and Subsequent Model-Year Heavy-Duty Engines (HD OBD), available at: http://www.arb.ca.gov/msprog/obdprog/hdobdreg.htm
[17] Global Technical Regulation No. 5, Technical Requirements for On-Board Diagnostic Systems (OBD) for Road Vehicles. United Nations Economic and Social Council, 15 November 2006, document: ECE/TRANS/180/Add.5 dated 23 January 2007, available at: http://www.unece.org/trans/main/wp29/wp29wgs/wp29gen/wp29registry/gtr5.html
ISO 27145-2:2012
Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements — Part 2: Common data dictionary
2 Normative references
ISO 14229-1:—1), Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements
ISO 14229-2, Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer interfaces
ISO 27145-1, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements — Part 1: General information and use case definition
ISO 27145-3, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements — Part 3: Common message dictionary
ISO 27145-4, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements — Part 4: Connection between vehicle and test equipment
SAE J1939, Companion Spreadsheet
SAE J1939-73:2010, Application layer — Diagnostics
SAE J1979-DA, Digital Annex of E/E Diagnostic Test Modes
SAE J2012-DA, Digital Annex of Diagnostic Trouble Code Definitions and Failure Type Byte Definitions
Bibliography
[1] ISO/IEC 7498-1, Information technology — Open Systems Interconnection — Basic Reference Model: The Basic Model
[2] ISO/IEC 10731, Information technology — Open Systems Interconnection — Basic Reference Model — Conventions for the definition of OSI services
[3] ISO 11898-1, Road vehicles — Controller area network (CAN) — Part 1: Data link layer and physical signalling
[4] ISO 11898-2, Road vehicles — Controller area network (CAN) — Part 2: High-speed medium access unit
[5] ISO 13400 (all parts), Road vehicles — Diagnostic communication over Internet Protocol (DoIP)
[6] ISO 15031 (all parts), Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics
[7] ISO 15765-2, Road vehicles — Diagnostic communication over Controller Area Networks (DoCAN) — Part 2: Transport protocol and network layer services
[8] ISO 15765-4, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 4: Requirements for emissions-related systems
[9] SAE J1930-DA, Electrical/Electronic Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms Web Tool Spreadsheet
[10] SAE J1939-03, On-Board Diagnostics Implementation Guide
[11] IEEE 802.3, IEEE Standard for Information technology — Specific requirements — Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications
[12] CCR 1968.2 Title 13, California Code Regulations, Section 1968.2, Malfunction and Diagnostic System Requirements for 2004 and Subsequent Model-Year Passenger Cars, Light-Duty Trucks, and Medium-Duty Vehicles and Engines (OBD II), available at: http://www.arb.ca.gov/msprog/obdprog/obdregs.htm
[13] CCR 1971.1 Title 13, California Code Regulations, Section 1971.1, On-Board Diagnostic System Requirements for 2010 and Subsequent Model-Year Heavy-Duty Engines (HD OBD), available at: http://www.arb.ca.gov/msprog/obdprog/hdobdreg.htm
[14] Global Technical Regulation No. 5, Technical Requirements for On-Board Diagnostic Systems (OBD) for Road Vehicles. (established in the Global Registry on 15 November 2006); document: ECE/TRANS/180/Add.5 dated 23 January 2007, available at: http://live.unece.org/trans/main/wp29/wp29wgs/wp29gen/wp29registry/gtr5.html
[SAE J1939] Recommended Practice for a Serial Control and Communications Vehicle Network
[TPS_STDT] AUTOSAR Standardization Template,
AUTOSAR_TPS_StandardizationTemplate.pdf
Countdown Calendar 2022
今年企画した6つのCountdown Calendarと、それぞれの記事一つをご紹介します。
AUTOSAR Countdown Calendar 2022
AUTOSAR References to ISO, IEC, ITU, IEEE, RFC and SEA etc.
Automotive Handbook Countdown Calendar 2022
Basic principles, ボッシュ自動車handbook(英語)11版まとめ<2>
2022 いいねをいただいた記事ランキング(O.K.版) Countdown Calendar 2022
2022年１月下旬 いいねをいただいた記事 16
CDCale(O.K.) Countdown Calendar 2022
「会議は15分未満」に。小耳にはさんだ話。
ABC language (O.K.版） Advent Calendar 2022
LLVMソースコードのコンパイルをしようと思ってハマった罠とそこから脱出するための努力
ABC maker(O.K版） Advent Calendar 2022
JAXA/IPA クリティカルソフトウェアワークショップ WOCS言語関連発表(改定版)
CountdownCalendar2022 報告
関連文書(Related document)
AUTOSAR Abstract Platformへの道（詳細編）
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の仕組みと設計のために
AUTOSAR Abstract Platform User Group Weekly Report(1) 2022.1.8
AUTOSAR Abstract Platform User Group Weekly Report(2) 2022.1.15
202304 URL更新
Project Objectives, AUTOSAR 599, R22-11, FO, 20230421
＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞
文書履歴(document history)
ver. 0.01 初稿 20230124
ver. 0.02 ありがとう追記 20230701
最後までおよみいただきありがとうございました。
いいね 💚、フォローをお願いします。
Thank you very much for reading to the last sentence.
Please press the like icon 💚 and follow me for your happy life.