ISO 14229-2:2013
Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services
ISO 14229-2:2013 specifies data link independent requirements of session layer services.
ISO 14229-2:2013 specifies common session layer services to provide independence between unified diagnostic services (ISO 14229-1) and all transport protocols and network layer services (e.g. ISO 15765-2 DoCAN, ISO 10681-2 communication on FlexRay, ISO 13400 DoIP, ISO 14230-2 DoK-Line, etc.)
ISO 14229-2:2013 specifies a common service primitive interface between OSI layer 4 (Transport) and layer 5 (Session) via so-called service request/confirmation/indication primitives. This interface allows seamless implementation of ISO 14229-1 unified diagnostic services (UDS) with any communication protocol titled "DoXYZ / CoXYZ" like ISO 15765 DoCAN - diagnostic communication over Controller Area Network, ISO 13400 DoIP, ISO 10681 communication over FlexRay, ISO 14230 DoK-Line.
ISO 15031 (emissions-related OBD) and ISO 27145 (WWH-OBD) support the standardized service primitive interface.
| Get this standard | Prices exclude GST | |
|---|---|---|
| PDF ( Single user document) |
$118.26 NZD
|
|
| HardCopy |
$152.17 NZD
|
|
| Networkable PDF |
Price varies
|
1 Scope
2 Normative references
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
3.2 Abbreviated terms
4 Conventions
5 Document overview
6 Session layer services
6.1 General
6.2 Specification of session layer service primitives
6.2.1 General
6.2.2 S_Data.request
6.2.3 S_Data.confirm
6.2.4 S_Data.indication
6.3 Session data unit specification
6.3.1 S_Mtype, Session layer message type
6.3.2 S_SA, Session layer source address
6.3.3 S_TA, Session layer target address
6.3.4 S_TAtype, Session layer target address type
6.3.5 S_AE, Session layer Address Extension (optional parameter)
6.3.6 S_Length
6.3.7 S_Data
6.3.8 S_Result
6.3.9 Mapping of S_PDU onto T_PDU and vice versa for message transmission
7 Timing parameter definition
7.1 General application timing considerations
7.1.1 Server
7.1.2 Client
7.2 Application timing parameter definitions – defaultSession
7.3 Example for P4Server without enhanced response timing
7.4 Example for P4Server with enhanced response timing
7.5 Session timing parameter definitions for the non-default session
7.6 Client and server timer resource requirements
7.7 Error handling
8 Timing handling during communication
8.1 Physical communication
8.1.1 Physical communication during defaultSession – without SOM.ind
8.1.2 Physical communication during defaultSession – with SOM.ind
8.1.3 Physical communication during defaultSession with enhanced response timing
8.1.4 Physical communication during a non-default session
8.1.4.1 Functionally addressed TesterPresent (0x3E) message
8.1.4.2 Physically addressed TesterPresent (0x3E) message
8.2 Functional communication
8.2.1 Functional communication during defaultSession – without SOM.ind
8.2.2 Functional communication during defaultSession – with SOM.ind
8.2.3 Functional communication during defaultSession with enhanced response timing – with SOM.ind
8.2.4 Functional communication during non-default session – with SOM.ind
8.3 Minimum time between client request messages
Blank Page
Blank Page
Keep me up-to-date
Sign up to receive updates when there are changes to this standard
Related Information
Similar Standards
-
AS/NZS 2538:2004
Vehicle support stands
-
AS/NZS 2550.9:1996
Cranes - Safe use - Vehicle hoists
-
AS/NZS 2615:2004
Hydraulic trolley jacks
-
AS/NZS 2640:1994
Portable ramps for vehicles
1 Scope
2 Normative references
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
3.2 Abbreviated terms
4 Conventions
5 Document overview
6 Session layer services
6.1 General
6.2 Specification of session layer service primitives
6.2.1 General
6.2.2 S_Data.request
6.2.3 S_Data.confirm
6.2.4 S_Data.indication
6.3 Session data unit specification
6.3.1 S_Mtype, Session layer message type
6.3.2 S_SA, Session layer source address
6.3.3 S_TA, Session layer target address
6.3.4 S_TAtype, Session layer target address type
6.3.5 S_AE, Session layer Address Extension (optional parameter)
6.3.6 S_Length
6.3.7 S_Data
6.3.8 S_Result
6.3.9 Mapping of S_PDU onto T_PDU and vice versa for message transmission
7 Timing parameter definition
7.1 General application timing considerations
7.1.1 Server
7.1.2 Client
7.2 Application timing parameter definitions – defaultSession
7.3 Example for P4Server without enhanced response timing
7.4 Example for P4Server with enhanced response timing
7.5 Session timing parameter definitions for the non-default session
7.6 Client and server timer resource requirements
7.7 Error handling
8 Timing handling during communication
8.1 Physical communication
8.1.1 Physical communication during defaultSession – without SOM.ind
8.1.2 Physical communication during defaultSession – with SOM.ind
8.1.3 Physical communication during defaultSession with enhanced response timing
8.1.4 Physical communication during a non-default session
8.1.4.1 Functionally addressed TesterPresent (0x3E) message
8.1.4.2 Physically addressed TesterPresent (0x3E) message
8.2 Functional communication
8.2.1 Functional communication during defaultSession – without SOM.ind
8.2.2 Functional communication during defaultSession – with SOM.ind
8.2.3 Functional communication during defaultSession with enhanced response timing – with SOM.ind
8.2.4 Functional communication during non-default session – with SOM.ind
8.3 Minimum time between client request messages
Blank Page
Blank Page