SOME/IP Protocol Specification - AUTOSAR

1 SOME/IP Protocol SpecificationAUTOSAR FO R20-11 Document TitleSOME/IP Protocol SpecificationDocument OwnerAUTOSARD ocument ResponsibilityAUTOSARD ocument Identification No696 Document StatuspublishedPart of AUTOSAR StandardFoundationPart of Standard ReleaseR20-11 Document Change HistoryDateReleaseChanged byDescription2020-11-30R20-11 AUTOSARR eleaseManagement Removed Draft Status from TLVR equirements Fixed discrepancies between SWSand PRS Clarified usage of length field Restricted alignment of variablelength arrays to 8, 16, 32, 64, 128 or256 Bits Editorial Changes2019-11-28R19-11 AUTOSARR eleaseManagement Added Support for unit64 / sint64 Error-Codes for E2E-Protection Clarify Serialization of fixed lengtharray data Support for Data Accumulationfeature Contradicting requirements IntroduceimplementsLegacyStringSerializa tiontag (as successor ofimplementsSOMEIPS tringHandling) Editorial Changes Changed Document Status fromFinal to No content changes1 of 70 Document ID 696.

2 AUTOSAR_PRS_SOMEIPP rotocolSOME/IP Protocol SpecificationAUTOSAR FO Backward-incompatibility statementremoved some statements Improved No content Editorial Serialization of Structured Datatypesand Arguments with Identifier andoptional Release2 of 70 Document ID 696: AUTOSAR_PRS_SOMEIPP rotocolSOME/IP 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.

3 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 70 Document ID 696: AUTOSAR_PRS_SOMEIPP rotocolSOME/IP Protocol SpecificationAUTOSAR FO R20-11 Table of Contents1 Introduction and Protocol purpose and objectives.

4 Applicability of the Protocol .. and assumptions .. Dependencies .. Document Structure .. 72 Protocol Requirements Traceability .. 83 Acronyms and Abbreviations164 Protocol Specification of SOME/IP Message Format (Serialization) .. ID [32 Bit] .. ID [15 Bit] .. ID [15 Bit] .. [32 Bit] .. ID [32 Bit] .. Version [8 Bit] .. Version [8 Bit] .. Type [8 Bit] .. Code [8 Bit] .. [variable size] .. of Data Structures .. Datatypes .. Datatypes (structs).

5 Datatypes and Arguments with Identifierand optional members .. / Variant .. Specification of SOME/IP Protocol .. Protocol Bindings .. Binding .. Binding .. Service-Instances .. 484 of 70 Document ID 696: AUTOSAR_PRS_SOMEIPP rotocolSOME/IP Protocol SpecificationAUTOSAR FO large SOME/IP messages of UDP( SOME/IP -TP) .. Communication .. Communication .. Events .. for sending notifications .. Handling .. Code .. Message .. Processing Overview .. Errors and Handling of Communica-tion Errors.

6 Compatibility Rules for Interface Version .. 635 Configuration Parameters676 Protocol usage and Choosing the transport Protocol .. Transporting CAN and FlexRay Frames .. Insert Padding for structs .. 697 References705 of 70 Document ID 696: AUTOSAR_PRS_SOMEIPP rotocolSOME/IP Protocol SpecificationAUTOSAR FO R20-111 Introduction and overviewThis Protocol Specification specifies the format, message sequences and seman-tics of the AUTOSAR Protocol "Scalable service-Oriented MiddlewarE over IP( SOME/IP )".

7 SOME/IP is an automotive/embedded communication Protocol which supports remoteprocedure calls, event notifications and the underlying serialization/wire format. Theonly valid abbreviation is SOME/IP . Other abbreviations ( SOME/IP ) are wrong andshall not be Protocol purpose and objectivesThe basic motivation to specify "Yet another RPC-Mechanism" instead of using anexisting infrastructure/technology is the goal to have a technology that: Fulfills the hard requirements regarding resource consumption in an embeddedworld Is compatible through as many use-cases and communication partners as possi-ble compatible with AUTOSAR at least on the wire-format level.

8 Can commu-nicate with PDUs AUTOSAR can receive and send without modification to theAUTOSAR standard. The mappings within AUTOSAR shall be chosen accordingto the SOME/IP Specification . Provides the features required by automotive use-cases Is scalable from tiny to large Applicability of the protocolSOME/IP shall be implemented on different operating system ( AUTOSAR , GENIVI,and OSEK) and even embedded devices without operating system. SOME/IP shall beused for inter-ECU Client/Server Serialization. An implementation of SOME/IP allowsAUTOSAR to parse the RPC PDUs and transport the signals to the Constraints and assumptionsThe "Support for serialization of extensible data structs" has been introduced - whichSOME/IP serializers based on AUTOSAR Foundation Standard (AUTOSARC lassic Standard ) cannot process.

9 To indicate this interoperability issue6 of 70 Document ID 696: AUTOSAR_PRS_SOMEIPP rotocolSOME/IP Protocol SpecificationAUTOSAR FO R20-11[PRS_SOMEIP_00220] requires to increase the major interface version of the respec-tive serialized LimitationsThis document gives a holistic overview over SOME/IP but doesn t state any require-ments towards any implementation of BSW be aware that not all parts of SOME/IP may be implemented in DependenciesThere are no dependencides to AUTOSAR SWS Document StructureThe SOME/IP PRS will describe the following two aspects of of SOME/IP on wire-format (Serialization)

10 Structure of Header Format How the different data types are serialized as per some /IPSpecification of Protocol for Event and RPC-based communication Transport Protocol Rules that govern the RPC for some /IP7 of 70 Document ID 696: AUTOSAR_PRS_SOMEIPP rotocolSOME/IP Protocol SpecificationAUTOSAR FO R20-112 Protocol Requirements TraceabilityFeatureDescriptionSatisfied by[RS_SOMEIP_00002] SOME/IP Protocol shall provideservice-based communication[PRS_SOMEIP_00043][PRS_SOME IP_00703][PRS_SOMEIP_00909][RS_SOMEIP_00 003] SOME/IP Protocol shall providesupport of multiple versions of aservice interface[PRS_SOMEIP_00053][PRS_SOMEIP_0 0937][PRS_SOMEIP_00938][RS_SOMEIP_00004] SOME/IP Protocol shall supportevent communication[PRS_SOMEIP_00925][PRS_SOME IP_00926]