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

ISO 14229-2:2021 Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services
https://www.iso.org/standard/77322.html

関係表にある規格群。
markdownでどう表現していいかわからない。
PDF出力して、画像で貼り付け。

Table 1 — Example of diagnostic/programming specifications applicable to the OSI layers

Normative Reference

ISO/IEC 7498-1, Information technology — Open Systems Interconnection — Basic Reference Model: The Basic Model

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

Terms and Definitions

3.1 gateway

networking device that transfers the PDU on different OSI layers
EXAMPLE:A network device that enables communication between control module networks that uses different communication protocols, different communication rates, etc. and that includes, but is not limited to, gateway functionalities like bridge, switch (3.3), router (3.2) or application layer routing.

3.2 router

networking device that transfers the PDU on OSI layers 3 and 4

3.3 switch

networking device that transfers the PDU on OSI layer 2

4.2 Abbreviated terms

Diag diagnostics
ECU electronic control unit
N/A not applicable
OSI open systems interconnection
RDiag remote diagnostics
S_AE session layer address extension
S_Data session layer data transfer service name
S_Length session layer length of data
S_Mtype session layer message type
S_PDU session layer protocol data unit
S_SA session layer source address
S_TA session layer target address
S_TAtype session layer target address type
SecureDiag secure diagnostics
SecureRDiag secure remote diagnostics
SI service identifier
SOM start of message
SPP service primitive parameter

Bibliography

[1] ISO/IEC 10731:1994, Information technology — Open Systems Interconnection — Basic Reference Model — Conventions for the definition of OSI services

[2] ISO 10681-2, Road vehicles — Communication on FlexRay — Part 2: Communication layer services

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

[4] ISO 14230-2, Road vehicles — Diagnostic communication over K-Line (DoK-Line) — Part 2: Data link layer

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

[6] ISO 20794-3, Road vehicles — Clock extension peripheral interface (CXPI) — Part 3: Transport and network layer

content

Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Symbols and abbreviated terms
4.1 Symbols
4.2 Abbreviated terms
5 Conventions
6 Session layer services
6.1 Service interface
6.2 Service interface parameters
6.3 Service interface primitives
7 Service interface (SI) definition from application layer to session layer
7.1 SI — S_Data.req, S_Data.ind, and S_Data.conf service interface
7.2 SI — S_Data.req, S_Data.ind, and S_Data.conf service interface parameter mapping
7.3 SI — S_PDU mapping onto T_PDU and vice versa for message transmission
7.4 SI — S_Data.req
7.5 SI — S_Data.ind
7.6 SI — S_Data.conf
8 Service primitive parameters (SPP)
8.1 SPP – General
8.2 SPP – Data type definitions
8.3 SPP – S_Mtype, session layer message type
8.4 SPP – S_TAtype, session layer target address type
8.5 SPP – S_TA, session layer target address
8.6 SPP – S_SA, session layer source address
8.7 SPP – S_AE, session layer address extension
8.8 SPP – S_Length, session layer length of S_Data
8.9 SPP – S_Data, session layer data of PDU
8.10 SPP – S_Result, session layer result
9 Timing parameter definition
9.1 General application timing considerations
9.1.1 Server
9.1.2 Client
9.2 Application timing parameter definitions – defaultSession
9.3 Example for t without enhanced response timing P4_Server
9.4 Example for t with enhanced response timing . P4_Server
9.5 Session timing parameter definitions for the non-default session
9.6 Client and server timer resource requirements
9.7 Error handling
10 Timing handling during communication
10.1 Physical communication
10.1.1 Physical communication during defaultSession – without SOM.ind
10.1.2 Physical communication during defaultSession – with SOM.ind
10.1.3 Physical communication during defaultSession with enhanced response
timing
10.1.4 Physical communication during a non-default session
10.2 Functional communication
10.2.1 Functional communication during defaultSession – without SOM.ind
10.2.2 Functional communication during defaultSession – with SOM.ind
10.2.3 Functional communication during defaultSession with enhanced response
timing – with SOM.ind
10.2.4 Functional communication during non-default session – with SOM.ind
10.3 Minimum time between client request messages
Annex A (normative) T_PDU interface.
Annex B (informative) Vehicle diagnostic OSI layer architecture examples Bibliography

6 Session layer services

6 集会層奉仕

6.1 Service interface

奉仕界面
The service interface defines a set of services that are needed to access the functions offered by the session layer, i.e. transmission/reception of data and setting of protocol parameters.
奉仕界面は、集会層が提供する機能に接続するために必要な一連の奉仕、つまり与件の送受信と規約引数の設定を定義します。
The service primitives define how a service user (e.g. diagnostic application) cooperates with a service provider (e.g. session layer).
奉仕要素は、奉仕利用者（診断応用など）が奉仕提供者（集会層など）とどのように連携するかを定義する。
To define the services, three types of service primitives are specified:
奉仕を定義するために、次の3種類の奉仕要素指定する。
— a service request primitive S_Data.request, used by the higher application layer to pass control information or data required to be transmitted to the session layer (i.e. the service provider is being requested by the service user to process control information or to transmit data);
上位の応用層が集会層に送信する必要のある制御情報又は与件を渡すために使用する奉仕要求要素S_Data.request（奉仕提供者は、制御情報の処理または与件の送信を奉仕利用者から求められる）。
— a service indication primitive S_Data.indication, used by the session layer to pass status information and received data to the higher application layer (i.e. the service user is being informed by the service provider about an internal event of the session layer or the service request of a peer
protocol layer entity service user);
奉仕表示要素S_Data.indication。集会層が状態情報と受信与件を上位の応用層に渡すために使用する（奉仕利用者に、集会層の内部行事または奉仕要求を奉仕提供者が通知する。 対等規約層存在奉仕利用者）;
— a service confirmation primitive S_Data.confirm used by the session layer to pass status information to the application layer (i.e. the service user is being informed by service provider about the result of a preceding service request of the service user).
状態情報を応用層に渡すために集会層が使用する奉仕確認要素S_Data.confirm（奉仕利用者に、奉仕利用者の先行する奉仕要求の結果を、奉仕提供者が通知する）。

primitive:要素
peer:対等
entity:存在

参考資料

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

自己参照

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

ISO/IEC OSIに学ぶ
https://qiita.com/kaizen_nagoya/items/89562c52f37d6bf0a80d

IT業界における国際規格等の利用。仮説・検証（22）
https://qiita.com/kaizen_nagoya/items/0e2ab72fbddc391d4f41

OSI参照モデルの資料を作り始める（作業中）
https://qiita.com/kaizen_nagoya/items/26e1451ef4981c46b3be

＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞
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 初稿 　20240428

最後までおよみいただきありがとうございました。

いいね　💚、フォローをお願いします。

Thank you very much for reading to the last sentence.

Please press the like icon 💚　and follow me for your happy life.