OTA , E\E ,HPC, MQTT , HTTPS , Demo-Campaign management, TCU ,UDS ,OTA cyber attacks,OTA testing,Bootloader, bootmanager
What you'll learn:
It was inevitable that the increasing amount of software installed in a car would one day pose a problem. When you consider the infotainment system, advanced driver assistance system (ADAS), and under-the-hood software used for engine management, you can be sure that it all will need updating at some stage. The need to keep all of this software up to date and secure is challenging the industry. And that’s just current functionality—the expectation of new features and functionality is just as important. As Figure 1 illustrates, current projections are that within the coming decade, approximately 50% of a vehicle’s value will be defined by software and experiences, compared to just 10% in the past (when the remaining 90% was accounted for by tangible mechanical component parts).
While OTA opens the opportunity to remotely update firmware and software, it also opens the vehicle system to the Internet. The security challenges associated with any connected device arise, along automotive-specific safety and reliability concerns. Consider, as well, connection requirements and cost for OTA enablement. Given varying data rates, automakers must ensure that the connection to the vehicle is robust enough to transmit required updates while keeping costs low. In the face of widely varying bandwidth and signal strengths, the OTA solution must be capable of completing and verifying update downloads that have had to stop and start several times
In very few years OTA will raise as a mandatory element in Automotive and this course will be helpful understanding the overall view about Automotive OTA concepts.
What you'll learn:
- What is OTA
- SOTA vs FOTA
- Importance OF OTA
- Market analysis- By OEM , By country
- OTA architecture
- OEM backend
- Cloud providers(AWS , AZURE,IBM)
- Campaign management Demonstration
- MQTT in Automotive example and HTTPS
- OTA Manager
- UDS flashing, UDS over CAN , UDS over Ethernet
- DOIP and CAN TP demo
- OTA testing
- Tesla Usecase
- Fail safe strategy(Single bank, dual bank)
- OTA cyber attacks
- Bootloader, bootmanager
It was inevitable that the increasing amount of software installed in a car would one day pose a problem. When you consider the infotainment system, advanced driver assistance system (ADAS), and under-the-hood software used for engine management, you can be sure that it all will need updating at some stage. The need to keep all of this software up to date and secure is challenging the industry. And that’s just current functionality—the expectation of new features and functionality is just as important. As Figure 1 illustrates, current projections are that within the coming decade, approximately 50% of a vehicle’s value will be defined by software and experiences, compared to just 10% in the past (when the remaining 90% was accounted for by tangible mechanical component parts).
While OTA opens the opportunity to remotely update firmware and software, it also opens the vehicle system to the Internet. The security challenges associated with any connected device arise, along automotive-specific safety and reliability concerns. Consider, as well, connection requirements and cost for OTA enablement. Given varying data rates, automakers must ensure that the connection to the vehicle is robust enough to transmit required updates while keeping costs low. In the face of widely varying bandwidth and signal strengths, the OTA solution must be capable of completing and verifying update downloads that have had to stop and start several times
In very few years OTA will raise as a mandatory element in Automotive and this course will be helpful understanding the overall view about Automotive OTA concepts.
