COMMUNICATION PROTOCOLS FOR ETHERNET IN THE VEHICLE AUTOMOTIVE BUS SYSTEMS AND ETHERNET DECEMBER 2013, STUTTGART MARRIOTT HOTEL SINDELFINGEN

Transcription

1 Dr. Lars Völker, BMW Group. OMMUNIATION PROTOOL FOR ETHERNET IN THE VEHILE AUTOMOTIVE BU YTEM AND ETHERNET DEEMBER 2013, TUTTGART MARRIOTT HOTEL INDELFINGEN

2 AGENDA Use cases and requirements Example protocol stack hallenges on the basis of OME/IP (scalable ervice-oriented MiddlewarE over IP) ummary Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 2

3 UE AE AND REQUIREMENT Question: What do you want to do with Ethernet in the vehicle? Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 3

4 UE AE AND REQUIREMENT ELETED UE AE FOR ETHERNET IN VEHILE Infotainment systems e.g. RE connection or AV transport Drivers Assistance e.g. surround view Ethernet Domain Backbone Diagnostics and Flash Update OPEN Alliance onfidential! All rights reserved! Dr. IQP, Lars BMW, Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, eite Page 4

5 UE AE AND REQUIREMENT REQUIREMENT FOR AUTOMOTIVE MIDDLEWARE upport AN like communication upport MOT like control communication hall efficiently support switched medium like Ethernet (not a bus!) upport unicast communication Limit multicast/broadcast to acceptable level Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 5

6 UE AE AND REQUIREMENT WHAT HAVE WE DONE? With Ethernet, we tried to reuse as many protocols as possible: Ethernet is a well proven technology TP/IP stack is proven solution, why develop a new one? Parts of AVB fit out of the box, others need some adaption However: Finding a suitable middleware solution to transport control data was not that easy! o OME/IP was created! Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 6

7 EXAMPLE PROTOOL TAK Audio/Video Transport Time ync Automotive Network Management Diagnostics and Flash Update ontrol ommunication ervice Discovery Address onfiguration Address Resolution, ignaling, etc. Layer 5-7 Layer 4 IEEE 1722 AVB IEEE 802.1A AVB UDP-NM UDP DoIP OME/IP TP and/or UDP OME/IP-D UDP DHP IMP ARP Layer 3 Layer 2 Layer 1 IEEE Ethernet MA + VLAN (802.1Q) Automotive Ethernet Physical Layer (e.g. OABR) IP IT tandard Automotive Most parts are reused but on Layer 1 and Layer 7 specific protocols are needed. Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 7

8 OME/IP ONEPT MIDDLEWARE lient erver Visible: Interface App. App. OME/IP Middleware Visible: Packets TP/IP tack Automotive Ethernet Network TP/IP tack OME/IP allows applications to communicate. Packet formats are automatically determined by the specification of the ervice. erver offers a ervice Instance that implements the ervice Interface. lient uses the ervice Instance using OME/IP. OME/IP allows applications to communicate over Ethernet and TP/IP. Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 8

9 OME/IP ONEPT ERVIE ervices Request/Response Fire & Forget A ervice is defined by its ervice Interface. This is comparable to a MOT Functional Block (FBlock) and may include: Methods: With response (Request/Response). Events Field Without response (Fire&Forget). Events: Message from erver to lient when something happens. Fields: Getter/etter/Notifier of a property/status. Eventgroups: A logical group of Events and Fields used for publish/subscribe handling. lient AUTOAR lient/erver. A ervice is an interface that contains Methods, Fields, and Events. Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 9

10 OME/IP ONEPT REQUET WITH REPONE METHOD Request/Response ervices: Request/Response Methods Request a message from client to server calling a method. Response a message from server to client transporting the results of the method invocation. Request/Response a method call with Request and Response messages. Request/Response methods allow calls with answers. Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 10

11 OME/IP ONEPT FIRE&FORGET METHOD Fire&Forget ervices: Fire&Forget Methods Request a message from client to server calling a method. Fire&Forget a method invocation with just a Request message. Message Type REQUET_NO_RETURN. Does not support answers and errors. Fire&Forget methods do not have answer messages. Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 11

12 OME/IP ONEPT EVENT ervices: Events Event a Fire&Forget callback, that is sent out by the erver (e.g. cyclically or on change). ent from erver to lient. Events imilar to regular AN messages. Events are simple messages from erver to lient. Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 12

13 OME/IP ONEPT FIELD Field ervices: Fields Field represents a remote accessible property that includes Getter/etter and/or Notification. Getter Method to read field value. etter Method to set field value. Notification (sends out Events with new values on change of field value). imilar to a property on MOT. Fields are properties that may include a Getter, a etter, and a Notification. Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 13

14 OME/IP ONEPT FIELD (2) Type Name of Field. GETTER/ETTER/NOTIFIER UINT16 vehiclepeed Event vehiclepeed(uint16 vehiclepeed) Method setvehiclepeed(uint16 vehiclepeed) returns UINT16 Method getvehiclepeed() returns UINT16 Field consists of: 0..1 Getter Request/Response 0..1 etter Request/Response 0..1 Notifier Events Field consists of Getter, etter, and Notifier. Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 14

15 OME/IP ONEPT EVENT V. FIELD Event Field tatus / Property ends out Event message Event ends out Event message Event tatus Buffer getter setter getter setter Event is only when something happens. Events do not have initial values. The lifetime of an Event is not defined. tatus based elements shall be modeled as Field. Event messages of Event and Field are identical. Difference: Initial Events only exist for Fields. Use Events for time limited observations, Fields for status like data. Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 15

16 OME/IP ONEPT ERVIE DIOVERY ervice Discovery Request/Response Fire & Forget ervice Discovery is used to explicitly signal: tatus of ervice Instances (available or not) as well as how to reach the service Publish/ubscribe Which Events/Fields does a client need? Events ervice tatus Field This state is transported using cyclic messages carrying entries: ervice: Find, Offer, and topoffer Eventgroup: ubscribe, topubscribe, ubscribeack, and ubscribenack ervice Discovery ervice Discovery transports status explicitly ervice Discovery handles ervice tate as well as Publish/ubscribe. Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 16

17 HALLENGE EXAMPLE OME/IP Architecture for different systems (e.g. AUTOAR and GENIVI) AUTOAR is based on AN and FlexRay messages, Ethernet is more dynamic Ethernet is common to Linux (e.g. GENIVI) What s a good compromise for a protocol? Agile process (specification and implementation in parallel) More innovation in less time AUTOAR process stressed Testing a complex protocol stack Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 17

18 HALLENGE AUTOAR AND GENIVI RTE Linux, QNX, OM OME/IP D ocket Adaptor OME/IP AN FR UDP / TP IP V. UDP IP TP AVB AN Ethernet Ethernet ocket Adaptor, OM and RTE for OME/IP. D has own module. OME/IP and OME/IP-D are implemented using library. Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 18

19 HALLENGE AUTOAR ROADMAP Resource optimization OME/IP erializer (?) Enhanced erializer Interface Feedback More efficient data path 2 nd gen (AUTOAR 4.1) OME/IP erializer Tech Report erializer upport in RTE / ervice Discovery W (OME/IP-D) Restructuring (oad TP, ) 1 st gen (AUTOAR 4.0) OME/IP specification by BMW Initial Ethernet upport in AUTOAR: ocket Adaptor, UDP-NM, If, 11/ / Fast pace roadmap reflected in AUTOAR standardization. Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 19

20 HALLENGE TETING OME/IP AND OME/IP-D Protocol stack testing often requires support for the testing The test application is called Enhanced Testability ervice (ET) Different methods, events, and fields are included tandardization of ET is in discussion Enhanced Testability ervice Layer 5-7 Layer 4 IEEE 1722 IEEE 802.1A UDP-NM UDP DoIP OME/IP TP and/or UDP OME/IP-D UDP DHP IMP ARP Tester Layer 3 Layer 2 AVB AVB IP IEEE Ethernet MA + VLAN (802.1Q) Layer 1 Automotive Ethernet Physical Layer (e.g. OABR) Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 20

21 UMMARY Automotive Protocol tack OME/IP hallenges Use cases different to IT world Reuse as much as possible Only Automotive Middleware upport different architectures Vehicle is not plugand-play Add automotive protocols upports GENIVI and AUTOAR Agile process vs standardization Automotive solutions needed Optimize for limited resources ervice Discovery signals explicitly Testing complex protocols Ethernet-based in-vehicle communication comes with solvable challenges! Dr. Lars Völker, BMW Group, ommunication Protocols for Ethernet in the vehicle, Page 21