Modern vehicles are more electrical than mechanical. As the vehicle industry goes on, more mechanical parts are being replaced by electrical components, e.g. x-by-wire. Weight and production costs could be the major factors in this revolution. To ensure the safety and in time response (meeting request’s deadline), the connection between these components is of great importance. Trying to find a protocol and standard that fits the vehicle industry to connect all ECUs, sensors and actuators together is not an easy task, since we are dealing with a system that has got a diverse type of traffic. Safety on the one hand and cost on the other hand are pushing the manufacturers to find the best networking protocol. In this report I am going to investigate the possibility and the risk of implementing on-board diagnostics over Ethernet. UDS (unified diagnostic services) and DoIP (diagnostic communication over Internet protocol) are the protocols that are going to be studied. To be more precise, I will investigate the possibility and the risk of UDS and DoIP implementation. The reason is that with the increasing number of ECUs and volume of data (parameter setting, downloading software, etc.,), the already implemented protocols and standards are not able to answer the required bandwidth. The wide acceptance and high bandwidth of Ethernet on one hand and its low cost infrastructure on the other hand has made Ethernet a candidate for this purpose.  The feasibility of Ethernet for in-vehicle network has already been investigated as I will show in the review of previous works. There are a couple of works that shows by using a suitable protocol in data link layer, we can meet the real-time requirement of a process. By reviewing these previous works we will find out that using Ethernet for vehicle on-board diagnostics is feasible. After investigating risks and manufacturer’s requirements along with worldwide legislations for the vehicle industry I will develop a DoIP gateway according to ISO 13400 which is connected to a CAN bus from one side and to a test tool via Ethernet from another side (Fig.1). UDS and DoIP protocols are implemented on both test tool and DoIP gateway. The practical part of the work is a complementary step in risk investigation that will be analysed. Having Ethernet as a carrier allows us to make use of different protocols, based on different needs like bandwidth, latency and real-time characteristics. This fact allows the network to have multi-type data which is usually the case with in-vehicle network. That is, we can use Ethernet not only for on-board diagnostics but also for other in-vehicle domains, such as the chassis, infotainment and comfort. At the end I will propose two models that will help the designers in this domain.

With the development of advanced driving assistance systems, the amount of data that needs to be transmitted within a car has increased tremendously. Traditional communication bus based systems are unable to meet today’s requirements; hence automotive Ethernet is being developed and standardized. Ethernet has for many years been the de facto standard in interconnecting computers. In that time several vulnerabilities of the networking protocol stack implementations and even the protocols themselves have been discovered. The knowledge from exploiting computer networks can be applied to the automotive domain. Additionally, vehicle manufacturers tend to implement their own stacks, due to copyleft reasons; hence the chances of implementation faults increases as opposed to using well-tested open source solutions. Since the line between security and safety in cars is almost nonexistent, security has to be properly addressed. This thesis investigates the security of automotive Ethernet and its accompanying protocols. It starts with an introduction to computer and automotive networking and protocols. After a solid foundation is laid, it investigates what makes up automotive Ethernet, its application in the field, and the automotive specific components relying on it. After looking at related work, a data network security audit and analysis as defined by the open-source security testing methodology is performed. The system is graded with risk assessment values. Weak points are identified and improvements suggested. The impact of the proposed improvements is shown by reevaluating the system and recalculating the risk assessment values. These efforts further the ultimate goal of achieving increased safety of all traffic participants. / Med utvecklingen av avancerade körningsassisterande system har mängden data som behöver sändas inom en bil ökat enormt. Traditionella kommunikationsbussbaserade system kan inte uppfylla dagens krav. Därmed utvecklas och standardiseras Ethernet för fordon. Ethernet har i många år varit de facto-standarden i sammankopplandet mellan datorer. Under den tiden har flera sårbarheter hos nätverksprotokolls implementeringar och protokoll själva upptäckts. Det finns anledning att tro att kunskapen från att utnyttja datanätverk kan tillämpas på fordonsdomänen. Att tillägga är att fordonstillverkare tenderar att genomföra sina egna staplar. På grund av copyleft skäl, ökar chanserna för implementeringsfel i motsats till att använda testade open source-lösningar. Eftersom människors säkerhet hos bilar är extremt viktigt, måste även dess system hanteras ordentligt. Denna avhandling undersöker säkerheten för Ethernet och kompletterande protokoll hos bilar. Den börjar med en introduktion till datorers och bilars nätverk och protokoll. Efter en stabil grund fastställts, undersöker den vad som utgör Ethernet hos bilar, dess tillämpning inom fältet, och de bilspecifika komponenterna den beror av. Efter att ha tittat på relaterat arbete utförs en säkerhetsgranskning och analys av datanätverk som definieras av säkerhetsmetoden för open-source. Systemet värderas med riskbedömningsvärden. Svaga punkter identifieras och förbättringar föreslås. Effekten av de föreslagna förbättringarna framgår utav omvärdering av systemet och omräkning av riskbedömningsvärdena. Dessa bedömningar leder till det yttersta målet för ökad säkerhet för alla trafikanter.

The Android operating system, originally intended for smartphone devices, is now finding its way into cars and other vehicles. While the Android system already implements support for system updates, it is not suitable for use in the automotive domain. It is not compatible with modern automotive standards for diagnostic communication such as ISO 14229: Unified Diagnostic Services (UDS). This means that new tools, procedures and software would be needed to allow an Android device to be updated by a service technician in a repair shop or on the field. A better approach would be to add support for automotive diagnostic communication in Android. This way, the tools and supporting infrastructure that already exist can still be used. We have developed a solution for diagnostic communication on Android that is both modular and compatible with existing automotive standards. By using the standard ISO 13400: Diagnostic communication over Internet Protocol (DoIP), this solution enables both updating the system software on the Android device itself, as well as diagnostic communication with the ECUs on the vehicle’s internal CAN network. Thus, an existing diagnostic port based on a slower communication protocol such as CAN or J1587 could theoretically be replaced completely by the Android device’s Ethernet port. Finally, we have evaluated the performance of our implementation under various settings and conditions. These include varying the maximum size of a diagnostic message, different network settings, downloading software over a Wi-Fi link, and downloading data to multiple devices simultaneously. / Operativsystemet Android, ursprungligen avsett för smartphone-enheter, återfinns numera även i bilar och andra typer av fordon. Även om Android-systemet redan implementerar stöd för system-uppdateringar, är det inte lämpligt att använda i fordonsindustrin. Den är inte kompatibel med moderna fordons-standarder för diagnoskommunikation som t.ex. ISO:14229: Enhetliga diagnostiktjänster (UDS). Detta innebär att det skulle krävas nya verktyg, procedurer och mjukvara för att möjliggöra att en Android-enhet uppdaterades av en service-tekniker i verkstad eller i fält. Ett bättre tillvägagångssätt skulle vara att lägga till support för diagnoskommunikation i Android. På detta sätt skulle redan existerande verktyg och stödjande infrastruktur kunna fortsätta användas. Vi har utvecklat en lösning för diagnoskommunikation i Android som är både modulär och kompatibel med existerande fordonsstandarder. Genom att använda ISO 13400: Diagnostikkommunikation över Internet-protokoll (DoIP) möjliggör denna lösning både uppdatering av systemmjukvaran i själva Android-enheten, samt diagnoskommunikation med övriga styrenheter på fordonets interna CAN-nätverk. Därmed skulle en befintlig diagnosport baserad på ett långsammare kommunikationsprotokoll såsom CAN eller J1587 teoretiskt kunna ersättas helt och hållet med Android-enhetens Ethernet-port. Slutligen har vi testat vår implementations prestanda under varierande inställningar och förhållanden. Dessa inkluderar bland annat att variera den maximala storleken av ett diagnos-meddelande, olika nätverks-inställningar, att uppdatera mjukvaran över en Wi-Fi-länk, samt att uppdatera mjukvaran på flera enheter samtidigt.