SOME/IP  比較 AUTOSAR and ISO, ethenet(113)

Some/IP は、AUTOSARで規定してからISOになったとして、　
ISO ISO 17215-2:2014には、AUTOSARという用語定義はある.
また、RFCについての記述がある。　
RFC、AUTOSARの文書のどちらもNormative Referenceにない。Bibliographyは存在しない。

RFC、ISO、AUTOSARの引用、参照関係の希薄さが、Some/IPのわかりにくさの根っこにあるかもしれない。　

３つの文書の関係性が分かりそうになるまで、逐条対応をしてみます。
雰囲気がわかったら、概要だけにします。
 
<この項は書きかけです。順次追記します。>
This article is not completed. I will add some words in order.
# ISO Normative Reference
>NOTE The keywords shall, should, etc. as defined in [IETF RFC 2119] are used in this part of ISO 17215 to indicate requirement levels. Capitalization of those keywords is not required. If an RFC referenced by this part of ISO 17215 has been updated by one or several RFCs, the update is fully applicable for the purpose of implementing this International Standard. This presumes the additional document describes an implementation which is compatible with implementation described by document referred to herein. If one or more errata for an RFC referenced by this part of ISO 17215 have been published, all of these errata documents are fully applicable for the purpose of implementing this International Standard. It is assumed that future implementations of this International Standard will use the most recent versions of the referenced RFCs, but maintain backward compatibility to existing implementations.

仮役
「[IETF RFC 2119] で定義している用語は、要件水準を示すために ISO 17215 のこの部(part2)で使用します。 これらの用語を大文字にする必要はありません。 ISO 17215 のこの部(part2)で参照している RFC が 1 つまたは複数の RFC で更新している場合、更新はこの国際規格を実装する目的で完全に適用します。 追加の文書が、ここで言及している文書によって記述した実装と互換性のある実装を記述していることを前提としています。 ISO 17215 のこの部(part2)で参照する RFC の正誤表が 1 つ以上発行している場合、これらの正誤表文書はすべて、この国際規格を実装する目的で完全に適用できます。 この国際標準の将来の実装では、参照している RFC の最新版を使用されると想定していますが、既存の実装との後方互換性を維持しています。」

本文中に登場するRFCは、ここで出てくる RFC2119とIETF RFC 791だけです。
Normative Referenceにも、Bibliographyにもない。誰がEditorだったんだってなるかもです。

# autosar
SOME/IP Protocol Specification, No.696, AUTOSAR 21-11 (78) FO
https://qiita.com/kaizen_nagoya/items/8f57605e8565ebb5d3d5

SOME/IP Protocol Specification, No.696, 2021-11
https://www.autosar.org/fileadmin/user_upload/standards/foundation/21-11/AUTOSAR_PRS_SOMEIPProtocol.pdf

# ISO 
ISO 17215-2:2014
Road vehicles — Video communication interface for cameras (VCIC) — Part 2: Service discovery and control
https://www.iso.org/standard/59546.html

# 比較　
## AUTOSAR 4.1 Specification of SOME/IP Message Format (Serialization)
### [PRS_SOMEIP_00030] ⌈The structure of header layout shall consist of • Message ID (Service ID/Method ID) [32 Bits]
• Length [32 Bits]
• Request ID (Client ID/Session ID) [32 Bits]
• Protocol Version [8Bits]
• Interface Version [8 Bits] 
• Message Type [8 Bits]
• Return Code [8 Bits]
⌋
(RS_SOMEIP_00027)
[PRS_SOMEIP_00030] is shown in the Figure 4.1.]
Figure 4.1: SOME/IP Header Format

#### ISO 7.5 Packet format
Figure 9 — SOME/IP service discovery packet format
### [PRS_SOMEIP_00941] ⌈In case of E2E communication protection being applied, the E2E header is placed after Return Code, depending on the chosen Offset value for the E2E header. The default Offset value is 64 bit, which puts the E2E header exactly between Return Code and Payload.⌋(RS_SOMEIP_00027)
[PRS_SOMEIP_00941] ss shown in the Figure 4.2.

Figure 4.2: SOME/IP Header and E2E header Format

#### no ISO
### [PRS_SOMEIP_00031] 
⌈For interoperability reasons the header layout shall be identcal for all implementations of SOME/IP. The fields are presented in transmission order i.e. the fields on the top left are transmitted first.⌋(RS_SOMEIP_00027)

#### no ISO?
### [PRS_SOMEIP_00034]  (4.1.2.1 Message ID [32 Bit])
⌈The Message ID shall be a 32 Bit identifier that is used to identify
• the RPC call to a method of an application • or to identify an event.
⌋(RS_SOMEIP_00021, RS_SOMEIP_00022, RS_SOMEIP_00023, RS_SOMEIP_- 00027)
Note: The assignment of the Message ID is up to the user / system designer. However, the Message ID is assumed be unique for the whole system (i.e. the vehicle).

#### ISO 6.2.1 Message ID [32-bit]
The Message ID is a 32-bit identifier that is used to dispatch the RPC call to the method of an application and to identify an event.
The assignment of the Message ID is up to the user. The next section describes how to structure the Message IDs in order to ease the organization of Message IDs.
— The Message ID shall uniquely identify a method or an event and the format of its associated PDUs. 
In order to structure the different methods and events, they are clustered into services. Services have a set of methods and events as well as a Service ID, which is used for exactly one service. Events are in
addition clustered into event groups, which simplify the subscription for multiple events.
— The message ID for RPC calls shall consist of a 16-bit Service ID (high bytes) and a 16-bit Method ID (low bytes).
— The Service ID and the Method ID shall be defined in the interface specification.
— The highest bit of the Event ID shall always be one.
This scheme allows for up to 65 536 services with up to 32 767 methods and 32767 events each.
— The message ID for events shall consist of a 16-bit Service ID (high bytes) and a 16-bit Notification
ID (low bytes).
— The Eventgroup ID and Event ID shall be specified in the interface specification.
— The highest bit of the Eventgroup ID shall always be one.

### [PRS_SOMEIP_00038] 
⌈Message IDs of method calls shall be structured in the ID with 216 services with 215 methods as shown in Table 4.1 ⌋(RS_SOMEIP_00027)

### [PRS_SOMEIP_00040] (4.1.2.2 Method ID [15 Bit])
 ⌈Events and notifications are transported using RPC, Events shall be structured as shown in Table 4.2 ⌋(RS_SOMEIP_00016, RS_SOMEIP_00027)
 
図にevent IDがを省略している。

### [PRS_SOMEIP_00365] ⌈Empty eventgroups shall not be used.⌋(RS_SOMEIP_00027,
RS_SOMEIP_00017)
### [PRS_SOMEIP_00366] ⌈Events as well as field notifiers are mapped to at least one eventgroup.⌋(RS_SOMEIP_00027, RS_SOMEIP_00016, RS_SOMEIP_00017, RS_- SOMEIP_00018)
# ISO 21111-11:2021
Road vehicles — In-vehicle Ethernet — Part 11: Application layer to session layer conformance test plans
https://www.iso.org/standard/82193.html

Bibliography
[1]	ISO/IEC 7498-1:1994, Information technology — Open Systems Interconnection — Basic Reference Model: The Basic Model
[2]	ISO/IEC/IEEE 8802-3:2021, Telecommunications and exchange between information technology systems — Requirements for local and metropolitan area networks — Part 3: Standard for Ethernet
[3]	ISO/IEC 9646 (all parts), Information technology — Open Systems Interconnection — Conformance testing methodology and framework
[4]	ISO/IEC 10731:1994, Information technology — Open Systems Interconnection — Basic Reference Model — Conventions for the definition of OSI services
[5]	ISO 21111-6, Road vehicles — In-vehicle Ethernet — Part 6: Electrical 100-Mbit/s physical entity requirements and conformance test plan
[6]	ISO 21111-7, Road vehicles — In-vehicle Ethernet — Part 7: Electrical 100-Mbit/s PHY layer network system specification and interoperability test plan
[7]	ISO 21111-8, Road vehicles — In-vehicle Ethernet — Part 8: Electrical 100-Mbit/s component requirements and test methods
[8]	IEC 62228-5, Integrated circuits – EMC evaluation of transceivers – Part 5 Ethernet transceivers
[9]	AUTOSAR, SOME/IP Protocol Specification, FO Release 1.3.01
[10]	AUTOSAR, Specification of Service Discovery, V1.2.0, R4.1 Rev 32
[11]	AUTOSAR, SOME/IP Example for a Serialization Protocol, V1.1.0 R4.1 Rev 33
[12]	AUTOSAR, Testability Protocol and Service Primitives, TC Release 1.2.04
[13]	AUTOSAR, SOME/IP Service Discovery Protocol Specification, FO Release V1.3.05
[14]	RFC 2131:1997, Dynamic Host Configuration Protocol6

1 Available at https://www.autosar.org/fileadmin/user_upload/standards/foundation/1-3/AUTOSAR_PRS_SOMEIPProtocol.pdf.
2 Available at https://www.autosar.org/fileadmin/user_upload/standards/classic/4-1/AUTOSAR_SWS_ServiceDiscovery.pdf.
3 Available at https://www.autosar.org/fileadmin/user_upload/standards/classic/4-1/AUTOSAR_TR_SomeIpExample.pdf.
4 Available at https://www.autosar.org/fileadmin/user_upload/standards/tests/1-2/AUTOSAR_PRS_TestabilityProtocolAndServicePrimitives.pdf.
5 Available at https://www.autosar.org/fileadmin/user_upload/standards/foundation/1-3/AUTOSAR_PRS_SOMEIPServiceDiscoveryProtocol.pdf.
6 Available at https://tools.ietf.org/html/[rfc2131.

# RPC
RFC7861 Remote Procedure Call (RPC) Security Version 3
https://datatracker.ietf.org/doc/html/rfc7861

## 自己参照
物理記事　上位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

Qiita(0)Qiita関連記事一覧（自分）
https://qiita.com/kaizen_nagoya/items/58db5fbf036b28e9dfa6

鉄道（０）鉄道のシステム考察はてっちゃんがてつだってくれる
https://qiita.com/kaizen_nagoya/items/26bda595f341a27901a0

日本語（０）一欄
https://qiita.com/kaizen_nagoya/items/7498dcfa3a9ba7fd1e68

英語(0) 一覧
https://qiita.com/kaizen_nagoya/items/680e3f5cbf9430486c7d

転職(0)一覧
https://qiita.com/kaizen_nagoya/items/f77520d378d33451d6fe

仮説（0）一覧（目標100現在40）
https://qiita.com/kaizen_nagoya/items/f000506fe1837b3590df

安全（0）安全工学シンポジウムに向けて: 21
https://qiita.com/kaizen_nagoya/items/c5d78f3def8195cb2409

Error一覧 error(0)
https://qiita.com/kaizen_nagoya/items/48b6cbc8d68eae2c42b8

Ethernet 記事一覧　Ethernet(0)
https://qiita.com/kaizen_nagoya/items/88d35e99f74aefc98794

Wireshark 一覧 wireshark(0)、Ethernet(48) 
https://qiita.com/kaizen_nagoya/items/fbed841f61875c4731d0

線網（Wi-Fi）空中線(antenna)(0) 記事一覧(118/300目標)
https://qiita.com/kaizen_nagoya/items/5e5464ac2b24bd4cd001

OSEK OS設計の基礎　OSEK(100)
https://qiita.com/kaizen_nagoya/items/7528a22a14242d2d58a3

官公庁・学校・公的団体（NPOを含む）システムの課題、官（０）
https://qiita.com/kaizen_nagoya/items/04ee6eaf7ec13d3af4c3

Error一覧(C/C++, python, bash...) Error(0)
https://qiita.com/kaizen_nagoya/items/48b6cbc8d68eae2c42b8

なぜdockerで機械学習するか 書籍・ソース一覧作成中 (目標100)
https://qiita.com/kaizen_nagoya/items/ddd12477544bf5ba85e2

言語処理100本ノックをdockerで。python覚えるのに最適。:10+12
https://qiita.com/kaizen_nagoya/items/7e7eb7c543e0c18438c4

プログラムちょい替え（0）一覧:4件
https://qiita.com/kaizen_nagoya/items/296d87ef4bfd516bc394

TOPPERSまとめ　#名古屋のIoTは名古屋のOSで
https://qiita.com/kaizen_nagoya/items/9026c049cb0309b9d451

官公庁・学校・公的団体（NPOを含む）システムの課題、官（０）
https://qiita.com/kaizen_nagoya/items/04ee6eaf7ec13d3af4c3

自動制御、制御工学一覧（０）
https://qiita.com/kaizen_nagoya/items/7767a4e19a6ae1479e6b

名刺代わりの技術書10選
https://qiita.com/kaizen_nagoya/items/dc497dcaa5a304fc96c8

一覧の一覧( The directory of directories of mine.) Qiita(100)
https://qiita.com/kaizen_nagoya/items/7eb0e006543886138f39

プログラマが知っていると良い「公序良俗」
https://qiita.com/kaizen_nagoya/items/9fe7c0dfac2fbd77a945

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

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