SOME/IP Protocol Specification - AUTOSAR

1 SOME/IP Protocol SpecificationAUTOSAR FO Release TitleSOME/IP Protocol SpecificationDocument OwnerAUTOSARD ocument ResponsibilityAUTOSARD ocument Identification No696 Document ClassificationStandardDocument StatusFinalPart of AUTOSAR StandardFoundationPart of Standard Change HistoryDateReleaseChanged Release1 of 50 AUTOSAR CONFIDENTIAL Document ID 696: AUTOSAR_PRS_SOMEIPP rotocolSOME/IP Protocol SpecificationAUTOSAR FO Release Specification and the material contained in it, as released by AUTOSAR , is for thepurpose of information only. AUTOSAR and the companies that have contributed to itshall not be liable for any use of the material contained in this Specification is protected by copyright and other types ofIntellectual Property Rights. The commercial exploitation of the material contained inthis Specification requires a license to such Intellectual Property Specification may be utilized or reproduced without any modification, in any formor by any means, for informational purposes only.

2 For any other purpose, no part ofthe Specification may be utilized or reproduced, in any form or by any means, withoutpermission in writing from the AUTOSAR specifications have been developed for automotive applications have neither been developed, nor tested for non-automotive word AUTOSAR and the AUTOSAR logo are registered for usersAUTOSAR specifications may contain exemplary items (exemplary reference models,"use cases", and/or references to exemplary technical solutions, devices, processes orsoftware).Any such exemplary items are contained in the specifications for illustration purposesonly, and they themselves are not part of the AUTOSAR Standard. Neither their pres-ence in such specifications, nor any later documentation of AUTOSAR conformance ofproducts actually implementing such exemplary items, imply that intellectual propertyrights covering such exemplary items are licensed under the same rules as applicableto the AUTOSAR of 50 AUTOSAR CONFIDENTIAL Document ID 696: AUTOSAR_PRS_SOMEIPP rotocolSOME/IP Protocol SpecificationAUTOSAR FO Release of Contents1 Introduction and Protocol purpose and objectives.

3 Applicability of the Protocol .. and assumptions .. Dependencies .. Document Structure .. 62 Protocol Requirements Traceability .. 83 Acronyms and Abbreviations134 Protocol Specification of SOME/IP on wire-format (Serialization) .. ID [32 Bit] .. [32 Bit] .. ID [32 Bit] .. Version [8 Bit] .. Version [8 Bit] .. Type [8 Bit] .. Code [8 Bit] .. [variable size] .. , Field and Eventgroup .. of Data Structures .. Datatypes .. Datatypes (structs) .. (fixed length) .. Length Arrays .. / Variant .. Specification of SOME/IP Protocol .. Protocol Bindings .. Binding .. Binding .. Service-Instances .. large SOME/IP messages of UDP( SOME/IP -TP) .. Communication .. Communication .. 393 of 50 AUTOSAR CONFIDENTIAL Document ID 696: AUTOSAR_PRS_SOMEIPP rotocolSOME/IP Protocol SpecificationAUTOSAR FO Release Events .. for sending notifications.

4 Handling .. Code .. Message .. Processing Overview .. Errors and Handling of Communica-tion Errors .. 465 Configuration Parameters476 Protocol usage and Choosing the transport Protocol .. Transporting CAN and FlexRay Frames .. Insert Padding for structs .. 497 References504 of 50 AUTOSAR CONFIDENTIAL Document ID 696: AUTOSAR_PRS_SOMEIPP rotocolSOME/IP Protocol SpecificationAUTOSAR FO Release 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 )". 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; can commu-nicate with PDUs AUTOSAR can receive and send without modification to theAUTOSAR standard.

5 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 assumptionsThis document specifies the SOME/IP Protocol on network level. It was created duringelaboration of the AUTOSAR Foundation Standard which took place in parallelto the development of the AUTOSAR Classic Standard It already reflects allchanges implied to SOME/IP by the work which was done for AUTOSAR Classic5 of 50 AUTOSAR CONFIDENTIAL Document ID 696: AUTOSAR_PRS_SOMEIPP rotocolSOME/IP Protocol SpecificationAUTOSAR FO Release the SOME/IP Protocol specified here is not fully backward-compatible to theSOME/IP Protocol used in AUTOSAR Classic Standard The most importantdifferences are: Unicode strings are always preceded by a BOM (see Chapter )The older version was not consistent with respect to the usage of BOMs.

6 The cur-rent version of SOME/IP mandates that every unicode string starts with a else is no string but an array of uint8, uint16 or uint32 elements. Message Types have been changed (see [PRS_SOMEIP_00055] and Table ):Thetypesforacknowledgements(REQUEST_AC K,RE-QUEST_NO_RETURN_ACK, NOTIFICATION_ACK, RESPONSE_ACK andERROR_ACK) were completely removed because they were defined but neverused in the Protocol . Segmentation functionality ( SOME/IP -TP) was introduced (see Chapter ):Large data (>1400 Bytes) can now be transferred via UDP. SOME/IP -TP cansegment larger data into small chunks which can be transferred via UDP andreassembled at receiver 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) Structure of Header Format How the different data types are serialized as per some /IPSpecification of Protocol for Event and RPC-based communication Transport Protocol6 of 50 AUTOSAR CONFIDENTIAL Document ID 696: AUTOSAR_PRS_SOMEIPP rotocolSOME/IP Protocol SpecificationAUTOSAR FO Release Rules that govern the RPC for some /IP7 of 50 AUTOSAR CONFIDENTIAL Document ID 696.

7 AUTOSAR_PRS_SOMEIPP rotocolSOME/IP Protocol SpecificationAUTOSAR FO Release Protocol Requirements TraceabilityFeatureDescriptionSatisfied by[RS_SOMEIP_00004] SOME/IP Protocol shall supportevent communication[PRS_SOMEIP_00925][PRS_SOME IP_00926][RS_SOMEIP_00006] SOME/IP Protocol shall supportuni-directional RPC communication[PRS_SOMEIP_00171][PRS_SOME IP_00924][RS_SOMEIP_00007] SOME/IP Protocol shall supportbi-directional RPC communication[PRS_SOMEIP_00920][PRS_SOME IP_00921][PRS_SOMEIP_00922][PRS_SOMEIP_0 0923][PRS_SOMEIP_00927][PRS_SOMEIP_00928 ][RS_SOMEIP_00008] SOME/IP Protocol shall supporterror handling of RPCcommunication[PRS_SOMEIP_00187][PRS_S OMEIP_00188][PRS_SOMEIP_00189][PRS_SOMEI P_00190][PRS_SOMEIP_00191][PRS_SOMEIP_00 195][PRS_SOMEIP_00537][PRS_SOMEIP_00539] [PRS_SOMEIP_00576][PRS_SOMEIP_00614][PRS _SOMEIP_00901][PRS_SOMEIP_00902][PRS_SOM EIP_00903][PRS_SOMEIP_00904][PRS_SOMEIP_ 00905][PRS_SOMEIP_00910][RS_SOMEIP_00009 ] SOME/IP Protocol shall supportfield communication[PRS_SOMEIP_00179][PRS_SOME IP_00180][PRS_SOMEIP_00181][PRS_SOMEIP_0 0182][PRS_SOMEIP_00183][PRS_SOMEIP_00909 ]8 of 50 AUTOSAR CONFIDENTIAL Document ID 696.

8 AUTOSAR_PRS_SOMEIPP rotocolSOME/IP Protocol SpecificationAUTOSAR FO Release [RS_SOMEIP_00010] SOME/IP Protocol shall supportdifferent transport protocolsunderneath[PRS_SOMEIP_00137][PR S_SOMEIP_00138][PRS_SOMEIP_00139][PRS_SO MEIP_00140][PRS_SOMEIP_00141][PRS_SOMEIP _00142][PRS_SOMEIP_00154][PRS_SOMEIP_001 60][PRS_SOMEIP_00535][PRS_SOMEIP_00706][ PRS_SOMEIP_00707][PRS_SOMEIP_00708][PRS_ SOMEIP_00709][PRS_SOMEIP_00710][PRS_SOME IP_00711][PRS_SOMEIP_00720][PRS_SOMEIP_0 0721][PRS_SOMEIP_00722][PRS_SOMEIP_00723 ][PRS_SOMEIP_00724][PRS_SOMEIP_00725][PR S_SOMEIP_00726][PRS_SOMEIP_00727][PRS_SO MEIP_00728][PRS_SOMEIP_00729][PRS_SOMEIP _00730][PRS_SOMEIP_00731][PRS_SOMEIP_007 32][PRS_SOMEIP_00733][PRS_SOMEIP_00734][ PRS_SOMEIP_00735][PRS_SOMEIP_00736][PRS_ SOMEIP_00738][PRS_SOMEIP_00740][PRS_SOME IP_00741][PRS_SOMEIP_00742][PRS_SOMEIP_0 0743][PRS_SOMEIP_00744][PRS_SOMEIP_00745 ][PRS_SOMEIP_00746][PRS_SOMEIP_00747][PR S_SOMEIP_00748][PRS_SOMEIP_00749][PRS_SO MEIP_00750][PRS_SOMEIP_00751][PRS_SOMEIP _00752][PRS_SOMEIP_00753][PRS_SOMEIP_007 54]9 of 50 AUTOSAR CONFIDENTIAL Document ID 696.

9 AUTOSAR_PRS_SOMEIPP rotocolSOME/IP Protocol SpecificationAUTOSAR FO Release [RS_SOMEIP_00011] SOME/IP Protocol shall supportmessages of different lengths[PRS_SOMEIP_00162][PRS_SOMEIP_001 63][PRS_SOMEIP_00720][PRS_SOMEIP_00721][ PRS_SOMEIP_00722][PRS_SOMEIP_00723][PRS_ SOMEIP_00724][PRS_SOMEIP_00725][PRS_SOME IP_00726][PRS_SOMEIP_00727][PRS_SOMEIP_0 0728][PRS_SOMEIP_00729][PRS_SOMEIP_00730 ][PRS_SOMEIP_00731][PRS_SOMEIP_00732][PR S_SOMEIP_00733][PRS_SOMEIP_00734][PRS_SO MEIP_00735][PRS_SOMEIP_00736][PRS_SOMEIP _00738][PRS_SOMEIP_00740][PRS_SOMEIP_007 41][PRS_SOMEIP_00742][PRS_SOMEIP_00743][ PRS_SOMEIP_00744][PRS_SOMEIP_00745][PRS_ SOMEIP_00746][PRS_SOMEIP_00747][PRS_SOME IP_00748][PRS_SOMEIP_00749][PRS_SOMEIP_0 0750][PRS_SOMEIP_00751][PRS_SOMEIP_00752 ][PRS_SOMEIP_00753][PRS_SOMEIP_00754][RS _SOMEIP_00026] SOME/IP Protocol shall define theendianness of header and payload[PRS_SOMEIP_00368][PRS_SOMEIP_003 69]10 of 50 AUTOSAR CONFIDENTIAL Document ID 696.

10 AUTOSAR_PRS_SOMEIPP rotocolSOME/IP Protocol SpecificationAUTOSAR FO Release [RS_SOMEIP_00027] SOME/IP Protocol shall define theheader layout of messages[PRS_SOMEIP_00030][PRS_SOMEIP_00 031][PRS_SOMEIP_00034][PRS_SOMEIP_00035] [PRS_SOMEIP_00038][PRS_SOMEIP_00040][PRS _SOMEIP_00042][PRS_SOMEIP_00043][PRS_SOM EIP_00044][PRS_SOMEIP_00046][PRS_SOMEIP_ 00052][PRS_SOMEIP_00053][PRS_SOMEIP_0005 5][PRS_SOMEIP_00058][PRS_SOMEIP_00365][P RS_SOMEIP_00366][PRS_SOMEIP_00367][PRS_S OMEIP_00521][PRS_SOMEIP_00533][PRS_SOMEI P_00701][PRS_SOMEIP_00702][PRS_SOMEIP_00 703][PRS_SOMEIP_00704][PRS_SOMEIP_00739] [RS_SOMEIP_00028] SOME/IP Protocol shall specify theserialization algorithm for data[PRS_SOMEIP_00063][PRS_SOMEIP_00569] [PRS_SOMEIP_00611][PRS_SOMEIP_00612][PRS _SOMEIP_00613][RS_SOMEIP_00030] SOME/IP Protocol shall supporttransporting integer data types[PRS_SOMEIP_00065][PRS_SOMEIP_00615 ][RS_SOMEIP_00031] SOME/IP Protocol shall supporttransporting boolean data type[PRS_SOMEIP_00065][PRS_SOMEIP_00615] [RS_SOMEIP_00032] SOME/IP Protocol shall supporttransporting float data types[PRS_SOMEIP_00065][PRS_SOMEIP_00615 ][RS_SOMEIP_00033] SOME/IP Protocol shall supporttransporting structured data types[PRS_SOMEIP_00077][PRS_SOMEIP_00079 ][PRS_SOMEIP_00300][PRS_SOMEIP_00370][PR S_SOMEIP_00371][PRS_SOMEIP_00705][PRS_SO MEIP_00712][PRS_SOMEIP_00900]11 of 50 AUTOSAR CONFIDENTIAL Document ID 696.