GMLAN Communication Strategy Specification
|Publication Date:||1 May 2019|
Note: Nothing in this standard supercedes applicable laws and regulations.
Note: In the event of conflict between the English and domestic language, the English language shall take precedence.
Purpose. This specification establishes the communication strategy for the GM In-Vehicle Local Area Network (GMLAN) Subsystem. Implementation of this strategy is required for all Electronic Control Units (ECU) connected to the network.
Applicability. This document is to be referenced by the particular Component Technical Specification (CTS), which describes any given Electronic Control Unit (ECU) in which the GMLAN data link controller and physical interface are located.
The intended audience includes, but is not limited to ECU suppliers, Design Release Engineers and Platform System Engineers.
Remarks. The GMLAN subsystem shall provide a reliable, cost effective, flexible and modular way to handle information sharing between different ECUs in the vehicle through the means of a family of serial communication buses. GMLAN is scaleable to support the range from simple control modules up to highly complex units. The communication system also supports the transfer of diagnostic services and the transformation from and to a specified set of globally accepted standards for diagnostic tester access and communication.
Requirement Wording Conventions.
Within this document the following conventions are applied:
The word "Shall" is used in the following ways:
a. To state a binding requirement on the GMLAN network, or the ECUs which comprise the network, which is verifiable by external manipulation and/or observation of a ECU or the network.
b. To state a binding requirement upon a ECU's requirements document that is verifiable through a review of the document.
The word "Must" is used in the following ways:
a. To state a binding requirement upon ECUs on the network that will have a corresponding ECU requirements document. These requirements will be verified as part of the component verification.
b. To characterize an expected behavior that is the natural consequence of another requirement in this document.
The word "Should" denotes a preference or desired conformance.