Requirements on BSW Modules for SAE J1939 (`SAEJ1939`)¶

属性	值
平台	CP
类别	RS — 需求规范（Requirements Specification）
UID	613
规范版本	R26-11

本地文件¶

规范 PDF: F:\Work\Standards\01_Sources\CP_RS_SAEJ1939_613\AUTOSAR_CP_RS_SAEJ1939.pdf
ARXML 模型: F:\Work\Standards\01_Sources\CP_RS_SAEJ1939_613\AUTOSAR_CP_RS_SAEJ1939.arxml
纯文本全文: F:\Work\Standards\01_Sources\CP_RS_SAEJ1939_613\zzgen\CP_RS_SAEJ1939.complete.txt

文档简介¶

This document specifies the requirements for the following BSW modules:

SAE J1939 Transport Layer module (J1939Tp, see )
SAE J1939 Request Manager (J1939Rm, see )
SAE J1939 Network Management module (J1939Nm, see )

The requirements for the SAE J1939 Diagnostic Communication Manager (J1939Dcm, see ) are contained in the .

章节详细内容¶

1. 范围 of Document¶

原文标题：Scope of Document

This document specifies the requirements for the following BSW modules:

SAE J1939 Transport Layer module (J1939Tp, see )
SAE J1939 Request Manager (J1939Rm, see )
SAE J1939 Network Management module (J1939Nm, see )

The requirements for the SAE J1939 Diagnostic Communication Manager (J1939Dcm, see ) are contained in the .

2. Conventions To Be Used¶

The representation of requirements in AUTOSAR documents follows the table specified in , see .

The verbal forms for the expression of obligation specified in shall be used to indicate requirements, see .

3. 需求指南¶

原文标题：Requirements Guidelines

There are no special guidelines for requirements for the Bus Mirroring.

4. 术语表, Acronyms, and Abbreviations¶

原文标题：Glossary, Acronyms, and Abbreviations

The glossary below includes terms and acronyms and abbreviations relevant to the SAE J1939 requirements specification that are not included in the .

Glossary Term	Explanation
AddressClaimed	Used to claim an address on an SAE J1939 bus (PGN = 0x0EE00).
Acknowledgement	Used to acknowledge a Request on an SAE J1939 bus (PGN = 0x0E800).
Controller Application	The role of an ECU that is tied to one source address.
Destination Address	The address of the receiver of a PG.
Default Error Tracer	Supports reporting of development errors and runtime errors.
Development Error	An error that is surely detected during development time. This class of errors typically stops the ECU.
Data Page	The most significant bit (MSB) of the 18 bit PGN.
Extended Data Page	The second bit (after MSB) of the 18 bit PGN.
Local Address	Refers to the source address of a transmitted PG and the destination address of a received PG.
PDU Meta Data	Meta data transferred alongside a PDU. For SAE J1939, this can be the CAN ID, the SA, the DA, or the Priority of a PGN.
N-PDU	PDU of the SAE J1939 Transport Layer, exchanged with the CAN Interface.

5. 需求规范¶

原文标题：Requirements Specification

6. 通用需求¶

原文标题：General Requirements

7. 功能性需求¶

原文标题：Functional Requirements

8. MetaData 处理¶

原文标题：MetaData Handling

J1939 Modules shall support MetaData ⌈ | Description: | The AUTOSAR BSW modules that support the J1939 standard shall support PDUs with MetaData. | |---|---| | Rationale: | J1939 requires a flexible approach to CAN IDs that must be reflected by all BSW modules supporting J1939 features. |

Applies To: | Dependencies: | - | |---|---| | Use Case: | * Request from arbitrary address. |

Answer to request via TP.
Request for AddressClaimed. | Supporting Material: | - | |---|---|

⌋

9. 需求 for the SAE J1939 传输 Layer 模块¶

原文标题：Requirements for the SAE J1939 Transport Layer module

10. 功能概述¶

原文标题：Functional Overview

This chapter describes the requirements that shall be fulfilled by the AUTOSAR J1939 Transport Layer module, which implements the transport protocol defined by with the variants BAM (Broadcast Announce Message) for broadcast mode and CMDT (Connection Mode Data Transfer, also known as RTS/CTS) for point to point communication.

The following pictures show the parts of the complete AUTOSAR system and in particular the Communication Services in which the J1939 Transport Layer module is situated.

11. 功能性需求¶

原文标题：Functional Requirements

12. 配置¶

原文标题：Configuration

This section describes the requirements on configurability of the module J1939 Transport Layer.

The J1939 Transport Layer module shall be configurable to support only transport protocol variant BAM ⌈ | Description: | The J1939 Transport Layer module shall be configurable to support either both the transport protocol variants BAM and CMDT or only the transport protocol variant BAM. | |---|---| | Rationale: | Some networks do not use CMDT. In these cases, the CMDT protocol shall be omitted completely to save resources. |

Applies To: | Dependencies: | - | |---|---| | Use Case: | ECUs that only support cyclic transmission of DM1 and no other large message. | | Supporting Material: | - |

⌋

The J1939 Transport Layer module shall identify each N-SDU with a unique identifier ⌈ | Description: | The J1939 Transport Layer module shall identify each N-SDU with a unique identifier, so that the upper layer can address an N-SDU without any assumption on the addressing mode configuration of the J1939Tp. | |---|---|

Furthermore, a symbolic name shall be assigned for each N-SDU identifier value to simplify the API usage. | Rationale: | Independence of upper layer from the J1939Tp configuration. | |---|---|

13. 初始化¶

原文标题：Initialization

This section describes the requirements on the initialization phase of the module J1939 Transport Layer.

The J1939 Transport Layer module shall implement an interface for initialization ⌈ | Description: | The J1939 Transport Layer module implements an interface for initialization. | |---|---|

This service shall initialize all global variables of the module and set all transport protocol connections in a default state (Idle). | Rationale: | Basic functionality. | |---|---|

Applies To: | Dependencies: | - | |---|---| | Use Case: | Set Transport Layer module to a defined state. | | Supporting Material: | - |

⌋

The J1939 Transport Layer services shall not be operational before initializing the module ⌈ | Description: | Before using the transmission capabilities of the J1939 Transport Layer module, it shall be initialized. If it is not initialized, the services of J1939Tp have to return an error and a development error shall be reported. | |---|---| | Rationale: | Basic functionality. |

Applies To: | Dependencies: | | |---|---| | Use Case: | To avoid usage of the module without a complete initialization - this could cause the transmission of corrupted frames. | | Supporting Material: | - |

⌋

14. Normal Operation¶

This section describes the requirements on the "normal" functionality of the module J1939 Transport Layer.

The AUTOSAR J1939 Transport Layer module shall support concurrent connections ⌈ | Description: | The number of concurrent connections supported by the AUTOSAR J1939 Transport Layer module depends on the used transport protocol and the transmitting direction. | |---|---|

In the sending direction:

If BAM is used: Only one connection shall be possible per local address (SA).
If CMDT is used: Parallel connections from all local addresses (SA) to all remote nodes (DA) shall be possible.

In the receiving direction:

If BAM has been used: One connection per remote node (SA) shall be possible.
If CMDT has been used: Parallel connections from all remote nodes (SA) to all local addresses (DA) are possible.

These restrictions are imposed by the way J1939 models multi packet communication via TP.CM and TP.DT. | Rationale: | An ECU must support parallel reception of N-SDUs that are issued either from different ECUs or shall be sent to different ECUs. So the AUTOSAR J1939 Transport Layer module shall allow concurrent connections. | |---|---|

15. 关机 Operation¶

原文标题：Shutdown Operation

The J1939 Transport Layer module shall provide an API to shut down operation of the module ⌈ | Description: | When the J1939 Transport Layer module needs to be re-initialized, the system is already running. It would lead to severe problems if a state variable is initialized in the same moment in which it is updated e.g. by a callback function. And it would lead to severe overhead, if the system must be protected against these problems. | |---|---|

A safe workaround is to de-initialize the module first, then wait for any callback function to terminate, and finally initialize the module again. | Rationale: | Clean handling of initialized state. | |---|---|

Applies To: | Dependencies: | - | |---|---| | Use Case: | Before re-initialization, the J1939 Transport Layer module should be de-initialized so that no operation is ongoing during initialization. | | Supporting Material: | - |

⌋

16. Fault Operation¶

The J1939 Transport Layer module shall handle unexpected PDUs according to the SAE J1939 specification ⌈ | Description: | The handling of an unexpected received N-PDU by the J1939 Transport Layer module depends on the configured N-PDU type: | |---|---|

Unexpected TP.DT frames shall be ignored.
Unexpected TP.CM_BAM frames shall terminate an active connection and start a new one.
Unexpected TP.CM_RTS frames shall terminate an active connection and start a new one if the PGN is the same. Otherwise they shall be answered by a TP.Conn_Abort frame.
Unexpected TP.CM_CTS and TP.CM_EndOfMsgACK frames shall be ignored.
Unexpected TP.Conn_Abort frames for a different PGN shall be ignored. | Rationale: | Protocol behavior on error. | |---|---|

Applies To: | Dependencies: | - | |---|---| | Use Case: | A TP.CM_CTS is received while the receiver still waits for data. | | Supporting Material: | |

⌋

The J1939 Transport Layer module shall be able to cope with invalid values in received TP frames ⌈ | Description: | The J1939 Transport Layer module shall be able to cope with invalid values in received TP frames (TP.CM, TP.DT). There are different possibilities of invalid values in TP frames. | |---|---|

TP.DT:

17. Non-Functional 需求 (Qualities)¶

原文标题：Non-Functional Requirements (Qualities)

The AUTOSAR J1939 Transport Layer module shall be based on SAE J1939 specifications ⌈ | Description: | If no requirement is explicitly added or excluded, the implementation of the AUTOSAR J1939 Transport Layer module shall follow the specification for the transport protocol (section 5.10 and appendix C of SAE J1939-21 of December 2010). | |---|---| | Rationale: | Reuse of existing standards for AUTOSAR BSW. |

The SAE J1939-21 specifications is the most used CAN related Transport Layer in Trucks. Applies To: | Dependencies: | - | |---|---| | Use Case: | Transport protocol on CAN according to SAE J1939: |

Segmentation of data in transmit direction
Collection of data in receive direction
Control of data flow
Detection of errors (message loss/doubling/sequence) | Supporting Material: | |---|

⌋

The J1939 Transport Layer module shall implement transport protocol functionalities in the layered software architecture ⌈ | Description: | The J1939 Transport Layer module shall handle segmentation and reassembling of large PDUs. For this task, it shall have interfaces to the | |---|---|

PDU Router and the CAN Interface. | Rationale: | Interfaces and interaction | |---|---|

Applies To: | Dependencies: | - | |---|---| | Use Case: | - | | Supporting Material: | - |

⌋

18. 需求 for the SAE J1939 Request 管理器¶

原文标题：Requirements for the SAE J1939 Request Manager

19. 功能概述¶

原文标题：Functional Overview

This chapter describes the requirements that shall be fulfilled by the AUTOSAR J1939 Request Manager, which implements the request management protocol defined by using the Request, the Request2, and the Acknowledgement PG.

The following pictures show the parts of the complete AUTOSAR system and in particular the Communication Services in which the J1939 Request Manager is situated.

20. 功能性需求¶

原文标题：Functional Requirements

21. 配置¶

原文标题：Configuration

The local addresses of the ECU shall be configurable ⌈ | Description: | The addresses which are accepted by the J1939 Request Manager when used as destination address of received messages or as source addresses of transmitted messages shall be configurable. | |---|---| | Rationale: | The ECU needs to be able to support more than one function. |

Applies To: | Dependencies: | - | |---|---| | Use Case: | An engine ECU might also control the retarder. | | Supporting Material: | Concept 579 "Support for Heavy Duty Vehicles" |

⌋

The queue size for transmitted PGs shall be configurable ⌈ | Description: | The size of the queues for the transmitted PGs Request and Acknowledgment shall be configurable separately. | |---|---| | Rationale: | The number of outgoing Request or Acknowledgement PGs strongly depends on the use case. |

Applies To: | Dependencies: | - | |---|---| | Use Case: | Adaptation to actual use case. | | Supporting Material: | Concept 579 "Support for Heavy Duty Vehicles" |

⌋

Requestable PGNs shall be configurable ⌈ | Description: | The J1939 Request Manager shall support configuration of the PGNs for which a request shall be accepted. | |---|---| | Rationale: | The set of PGNs that need to be requested is strongly use case dependent. |

22. 初始化¶

原文标题：Initialization

The J1939 Request Manager shall provide an interface for module initialization ⌈ | Description: | The J1939 Request Manager shall provide and implement an interface for initialization of all states and all global variables of the module. | |---|---| | Rationale: | Basic functionality |

Applies To: | Dependencies: | - | |---|---| | Use Case: | ECU initialization | | Supporting Material: | Concept 579 "Support for Heavy Duty Vehicles" |

⌋

23. Normal Operation¶

The J1939 Request Manager shall forward incoming requests to configured destinations ⌈ | Description: | The J1939 Request Manager shall filter incoming Request and Request2 PGs (destination address, PGN) and call the request indication of the modules configured for that PGN. | |---|---| | Rationale: | Request handling |

Applies To: | Dependencies: | Configuration of request destinations, see , , and | |---|---| | Use Case: | Dispatching of received requests to the correct destination module. | | Supporting Material: | Concept 579 "Support for Heavy Duty Vehicles" |

⌋

The J1939 Request Manager shall forward incoming acknowledgements to configured destinations ⌈ | Description: | The J1939 Request Manager shall filter incoming Acknowledgement PGs (acknowledged address, PGN) and call the acknowledgement indication of the modules configured for that PGN. | |---|---| | Rationale: | Acknowledgement handling |

Applies To: | Dependencies: | Configuration of acknowledgement destinations, see , , and | |---|---| | Use Case: | Dispatching of received acknowledgements to the correct destination module. | | Supporting Material: | Concept 579 "Support for Heavy Duty Vehicles" |

⌋

24. 关机 Operation¶

原文标题：Shutdown Operation

The J1939 Request Manager shall provide an interface for module shutdown ⌈ | Description: | The J1939 Request Manager shall provide and implement an interface for de-initialization of the module. | |---|---| | Rationale: | Basic functionality |

Applies To: | Dependencies: | - | |---|---| | Use Case: | ECU shutdown, ECU degradation | | Supporting Material: | Concept 579 "Support for Heavy Duty Vehicles" |

⌋

25. 需求 for the SAE J1939 网络管理¶

原文标题：Requirements for the SAE J1939 Network Management

26. 功能概述¶

原文标题：Functional Overview

This chapter describes the requirements that shall be fulfilled by the AUTOSAR J1939 Network Management, which implements the network management protocol defined by .

The following pictures show the parts of the complete AUTOSAR system and in particular the Communication Services in which the J1939 Network Management module is situated.

27. 功能性需求¶

原文标题：Functional Requirements

28. 配置¶

原文标题：Configuration

The channels on which the J1939 Network Management module is active shall be configurable ⌈ | Description: | The channels on which the J1939 Network Management module performs address claiming shall be configurable. | |---|---| | Rationale: | Address claiming is not required for all channels. |

Applies To: | Dependencies: | - | |---|---| | Use Case: | Gateway ECU with J1939 and proprietary channels. | | Supporting Material: | Concept 579 "Support for Heavy Duty Vehicles" |

⌋

The local addresses of the ECU shall be configurable ⌈ | Description: | The addresses which are claimed by the J1939 Network Management module shall be configurable. | |---|---| | Rationale: | The ECU needs to be able to support more than one function. |

Applies To: | Dependencies: | - | |---|---| | Use Case: | An engine ECU might also control the retarder. | | Supporting Material: | Concept 579 "Support for Heavy Duty Vehicles" |

⌋

The NAMEs used for claiming of each configured address shall be configurable ⌈ | Description: | For each address that is configured to be claimed a separate NAME is required. All fields of the NAME shall be configurable. | |---|---| | Rationale: | NAMEs must be unique for each network. |

29. 初始化¶

原文标题：Initialization

The J1939 Network Management module shall provide an interface for module initialization ⌈ | Description: | The J1939 Network Management module shall provide and implement an interface for initialization of all states and all global variables of the module. | |---|---| | Rationale: | Basic functionality |

Applies To: | Dependencies: | - | |---|---| | Use Case: | ECU initialization | | Supporting Material: | Concept 579 "Support for Heavy Duty Vehicles" |

⌋

30. Normal Operation¶

The J1939 Network Management module shall perform an initial address claim at startup ⌈ | Description: | For configured channels and ECU addresses, the J1939 Network Management module shall perform an initial address claim at startup. | |---|---| | Rationale: | Address claim is required before communication is allowed on J1939 networks. |

Applies To: | Dependencies: | - | |---|---| | Use Case: | Startup behavior of fully J1939 compliant ECUs. | | Supporting Material: | Concept 579 "Support for Heavy Duty Vehicles" |

⌋

The J1939 Network Management module shall react correctly to contending address claims ⌈ | Description: | When a contending address claim is received, the J1939 Network Management module shall answer with an AddressClaimed or with a CannotClaimAddress PG, depending on the relative priority of the NAMEs. | |---|---| | Rationale: | Duplicate addresses in the initial network setup shall not lead to undefined communication states. |

Applies To: | Dependencies: | - | |---|---| | Use Case: | Two ECUs might claim the same addresses, either because of an invalid network setup, or because one of the ECUs chooses its address at runtime. | | Supporting Material: | Concept 579 "Support for Heavy Duty Vehicles" |

⌋

31. 关机 Operation¶

原文标题：Shutdown Operation

The J1939 Network Management module shall provide an interface for module shutdown ⌈ | Description: | The J1939 Network Management module shall provide and implement an interface for de-initialization of the module. | |---|---| | Rationale: | Basic functionality |

Applies To: | Dependencies: | - | |---|---| | Use Case: | ECU shutdown, ECU degradation | | Supporting Material: | Concept 579 "Support for Heavy Duty Vehicles" |

⌋

32. Fault Operation¶

The J1939 Network Management module shall report a failed address claim to the Diagnostic Event Manager ⌈ | Description: | The J1939 Network Management module shall report to the Diagnostic Event Manager (DEM) when the address claim for one of the configured addresses fails. | |---|---| | Rationale: | Loss of address is critical, because some functionality will then not be available. |

Applies To: | Dependencies: | - | |---|---| | Use Case: | Due to invalid network setup, it can happen that one of the configured addresses cannot be claimed. | | Supporting Material: | Concept 579 "Support for Heavy Duty Vehicles" |

⌋

33. 需求 for the SAE J1939 功能性 Safety Communication 协议¶

原文标题：Requirements for the SAE J1939 Functional Safety Communication Protocol

34. 功能概述¶

原文标题：Functional Overview

This chapter describes the requirements that shall be fulfilled by the AUTOSAR J1939 Functional Safety Communication Protocol, which implements the functional safety communication protocol defined by .

The following pictures show the parts of the complete AUTOSAR system and in particular the Communication Services in which the J1939 Network Management module is situated.

35. 功能性需求¶

原文标题：Functional Requirements

36. 配置¶

原文标题：Configuration

Configurable PDUs Status: DRAFT ⌈ | Description: | The J1939 Functional Safety Communication Protocol shall support the configuration of the relevant PDUs for the SDG as upper layer PDU and for the SHM and SDM as lower layer PDUs. | |---|---|

Additional Information:

Only configured Tx/Rx SDGs shall be processed by J1939Fscp.
Reception of SDGs from multiple sources shall be processed by J1939Fscp. Rationale: Applies To: Dependencies: Use Case: Supporting Material: ⌋

Configurable SRVT between SHM and SDM for Tx SDGs Status: DRAFT ⌈ | Description: | The J1939 Functional Safety Communication Protocol shall support configuration of the maximum SRVT between SHM and SDM for transmitted SDGs. | |---|---|