E2E Protocol Specification - AUTOSAR

1 E2E Protocol SpecificationAUTOSAR FO R20-11 Document TitleE2E Protocol SpecificationDocument OwnerAUTOSARD ocument ResponsibilityAUTOSARD ocument Identification No849 Document StatuspublishedPart of AUTOSAR StandardFoundationPart of Standard ReleaseR20-11 Document Change HistoryDateReleaseChanged byDescription2020-11-30R20-11 AUTOSARR eleaseManagement E2E for methods. New profiles 08,44,4m,7m Extension of E2E State Machine2019-11-28R19-11 AUTOSARR eleaseManagement Introduction of Constraints forClient-Server Communication. Added E2E_PXXF orwardfunctionality to provide a mechanismfor replicating received E2E Errors. Incorporated new configurationoptions for switching between validand invalid state of E2E StateMachine. Fixed interoperability issues betweenP01 and P11, P02 and P22. Changed Document Status fromFinal to clarification on choosing suitablemaximum data lengths for of 319 Document ID 849: AUTOSAR_PRS_E2 EProtocolE2E Protocol SpecificationAUTOSAR FO Migrated all functional specificationsfrom Classic Platform s SWSE2 ELibrary into Foundation s E2 EProtocol Specification Moved all figures and tables out ofspecifications and added referencesto them Fixed duplicate/missing figures inprofiles 2 (Calculate DeltaCounter), 5(Read CRC), 6 (Read Counter) and11 (Read DataIDNibble).

2 Added Protocol examples for No content No content Initial Release2 of 319 Document ID 849: AUTOSAR_PRS_E2 EProtocolE2E Protocol SpecificationAUTOSAR FO R20-11 DisclaimerThis work ( Specification and/or software implementation) and the material contained init, as released by AUTOSAR , is for the purpose of information only. AUTOSAR and thecompanies that have contributed to it shall not be liable for any use of the material contained in this work is protected by copyright and other types of intel-lectual property rights. The commercial exploitation of the material contained in thiswork requires a license to such intellectual property work may be utilized or reproduced without any modification, in any form or byany means, for informational purposes only. For any other purpose, no part of the workmay be utilized or reproduced, in any form or by any means, without permission inwriting from the work has been developed for automotive applications only. It has neither beendeveloped, nor tested for non-automotive word AUTOSAR and the AUTOSAR logo are registered of 319 Document ID 849: AUTOSAR_PRS_E2 EProtocolE2E Protocol SpecificationAUTOSAR FO R20-11 Table of Contents1 Introduction and functional overview112 Acronyms and Abbreviations133 Related Input documents.

3 Standards and Norms .. 144 Constraints and Limitations .. in general .. in signal based communication .. in service oriented communication with events .. in service oriented communication in Clien-t/Server architecture .. to Service Translation .. Applicability to car domains .. 175 Requirements Tracing186 Functional Overview of communication protection .. Overview of E2E Profiles .. detection .. Types of E2E Profiles .. Xm Message Type Enumeration .. Xm Message Result Enumeration .. Functionality of an E2E-Profile .. of the Counter .. detection .. Redundancy Check .. Specification of E2E Profile 1 .. Layout .. ID .. calculation .. of E2E-Header .. CRC .. of E2E- Header .. Data Types .. 1 Protect State Type .. 544 of 319 Document ID 849: AUTOSAR_PRS_E2 EProtocolE2E Protocol SpecificationAUTOSAR FO 1 Check Status Type .. 1 Check Status Enumeration .. 1 Configuration Type.

4 Profile 1 Protocol Examples .. set to E2E_P01_DATAID_ALT .. set to E2E_P01_DATAID_LOW .. set to E2E_P01_DATAID_NIBBLE .. Specification of E2E Profile 2 .. Layout .. of E2E-Header .. of the E2E-Check .. Data Types .. 2 Protect State Type .. 2 Check Status Type .. 2 Check Status Enumeration .. 2 Configuration Type .. Profile 2 Protocol Examples .. Specification of E2E Profile 4 .. Layout .. ID .. detection .. of E2E-Header .. of the E2E-Header .. 4 Data Types .. 4 Protect State Type .. 4 Check Status Type .. 4 Check Status Enumeration .. 4 Configuration Type .. Profile 4 Protocol Examples .. Specification of E2E Profile 5 .. layout .. ID .. 985 of 319 Document ID 849: AUTOSAR_PRS_E2 EProtocolE2E Protocol SpecificationAUTOSAR FO .. of the E2E-Header .. of the E2E-Header .. Data Types .. 5 Protect State Type .. 5 Check Status Type .. 5 Check Status Enumeration.

5 5 Configuration Type .. Profile 5 Protocol Examples .. Specification of E2E Profile 6 .. layout .. ID .. of E2E-Header .. of E2E-Header .. Data Types .. 6 Protect State Type .. 6 Check Status Type .. 6 Check Status Enumeration .. 6 Configuration Type .. Profile 6 Protocol Examples .. Specification of E2E Profile 7 .. layout .. ID .. of the E2E-Header .. of the E2E-Header .. Data Types .. 7 Protect State Type .. 7 Check Status Type .. 7 Check Status Enumeration .. 7 Configuration Type .. Profile 7 Protocol Examples .. 1466 of 319 Document ID 849: AUTOSAR_PRS_E2 EProtocolE2E Protocol SpecificationAUTOSAR FO Specification of E2E Profile 8 .. layout .. ID .. detection .. of the E2E-Header .. of the E2E-Header .. Data Types .. 8 Protect State Type .. 8 Check Status Type .. 8 Check Status Enumeration .. 8 Configuration Type .. Profile 8 Protocol Examples.

6 Specification of E2E Profile 11 .. Header Layout .. ID .. Creation of the E2E-Header .. E2E_P11 Check .. Profile 11 Data Types .. 11 Protect State Type .. 11 Check Status Type .. 11 Check Status Enumeration .. 11 Configuration Type .. E2E Profile 11 Protocol Examples .. set to E2E_P11 DATAID_NIBBLE .. set to E2E_P11 DATAID_NIBBLE, Off-set set to 64 .. Specification of E2E Profile 22 .. Header layout .. ID .. Creation of E2E-Header .. 1907 of 319 Document ID 849: AUTOSAR_PRS_E2 EProtocolE2E Protocol SpecificationAUTOSAR FO Evaluation of E2E-Header .. Profile 22 Data Types .. 22 Protect State Type .. 22 Check Status Type .. 22 Check Status Enumeration .. 22 Configuration Type .. E2E Profile 22 Protocol Examples .. set to 64 .. Specification of E2E Profile 44 .. Header Layout .. ID .. detection .. Creation of E2E-Header .. Evaluation of the E2E-Header.

7 Profile 44 Data Types .. 44 Protect State Type .. 44 Check State Type .. 44 Check Status Enumeration .. 44 Configuration Type .. E2E Profile 44 Protocol Examples .. Specification of E2E Profile 4m .. Header Layout .. ID .. Type .. Result .. ID .. detection .. Creation of the E2E header .. Evaluation of the E2E Header .. - client overload .. - server overload .. Profile Data Types .. 4m Protect State Type .. 4m Check State Type .. 2448 of 319 Document ID 849: AUTOSAR_PRS_E2 EProtocolE2E Protocol SpecificationAUTOSAR FO 4m Check Status Enumeration .. 4m Configuration Type .. E2E Profile 4m Protocol Examples .. Specification of E2E Profile 7m .. Header Layout .. ID .. Type .. Result .. ID .. detection .. Creation of the E2E header .. Evaluation of the E2E Header .. - client overload .. - server overload .. Profile Data Types.

8 7m Protect State Type .. 7m Check State Type .. 7m Check Status Enumeration .. 7m Configuration Type .. E2E Profile 7m Protocol Examples .. Specification of E2E state machine .. Overview of the state machine .. State machine Specification .. FTTI and E2E parameters .. State Machine Configuration Type .. State Machine State Type .. State Machine Status Enumeration .. specific Check Status to State Machine CheckStatus mappings .. 2837 E2E API API of middleware to applications .. API of E2E .. 2908 Configuration General Constraints .. State Machine Settings .. 2939 Protocol usage and E2E and SOME/IP .. Client-Server Communication .. Periodic use of E2E check .. 2969 of 319 Document ID 849: AUTOSAR_PRS_E2 EProtocolE2E Protocol SpecificationAUTOSAR FO Error handling .. Maximal lengths of Data, communication buses .. Functional Safety Requirements .. Message Layout.

9 Of signals to byte limits .. bits .. order (Endianness) .. Configuration constraints on Data IDs .. IDs .. Data ID configuration of E2E Profile 1 and 11 .. Data ID configuration of E2E Profile 1 and 11 .. configuration of E2E Profile 1 and 11 .. 303A Usage and generation of DataID Lists for E2E profile 2 and Example A (persistent routing error) .. B (forbidden configuration) .. Conclusion .. DataID List example .. 308B Constraint Constraint History R19-11 .. Constraints .. Constraints .. Constraints .. Specification Items .. Specification Items .. Specification Items .. 31910 of 319 Document ID 849: AUTOSAR_PRS_E2 EProtocolE2E Protocol SpecificationAUTOSAR FO R20-111 Introduction and functional overviewThe concept of E2E communication protection assumes that safety-related [1] dataexchange shall be protected at runtime against the effects of faults on the communica-tion link (see Figure ). Faults detected between a sender and a receiver using E2 Ecommunication protection include systematic software faults, such as faults that areintroduced on the lower communication layers of sender or receiver, and random hard-ware faults introduced by the MCU hardware, communication peripherals, transceivers,communication lines or other communication for such faults are random HW faults ( corrupt registers of a CANtransceiver), interference ( due to EMC), and systematic faults of the lower com-munication layers ( RTE, IOC, COM and network stacks).

10 ECU 2 ECU 1 SenderE2 ECommunicationProtectionLower Communication LayersReceiverMCU HardwareCommunicationInfrastructureupper Communication LayersE2 ECommunicationProtectionLower Communication LayersMCU Hardwareupper Communication LayersFigure : Overview of E2E communication protection between a sender and a receiverBy using E2E communication protection mechanisms, faults in lower software andhardware layers can be detected and handled at runtime. The E2E Supervision pro-vides mechanisms for E2E communication protection, adequate for safety-related com-munication having requirements up to ASIL algorithms of protection mechanisms are implemented in the E2E callers of the E2E Supervision are responsible for the correct usage of the E2 ESupervision, in particular for providing correct parameters the E2E Supervision of 319 Document ID 849: AUTOSAR_PRS_E2 EProtocolE2E Protocol SpecificationAUTOSAR FO R20-11 The E2E communication protection allows the following:1. It protects the safety-related data to be sent by adding control data,2.