Curriculum
- 9 Sections
- 49 Lessons
- 2 Days
Expand all sectionsCollapse all sections
- The Connected Vehicle Ecosystem7
- 1.1Definitions: Connected Vehicle vs. Autonomous vs. Smart Vehicle
- 1.2Key domains: V2X, V2V, V2I, V2N, V2P
- 1.3Ecosystem players: OEMs, Tier-1s, Telecoms, Cloud, Regulators
- 1.4E/E Architecture evolution: CAN, Ethernet, OTA, SDVs
- 1.5Role of 5G, C-V2X, Edge computing, cloud offloading
- 1.6Buzzwords: Digital Twin, Over-The-Air (OTA), Digital Cockpit, Edge-AI
- 1.7Exercise: Map your current project/vehicle into a Connected Vehicle ecosystem chart
- Architecture Deep Dive – Hardware, Software & Communication6
- 2.1Key modules: TCU, HMI, ECUs, Gateways, GPS, Modems, eSIM
- 2.2Protocols: MQTT, HTTP, DDS, TCP/IP, C-V2X, DSRC
- 2.3OS & Middleware: QNX, Android Automotive, AUTOSAR Adaptive
- 2.4Cybersecurity elements: TLS, VPNs, Firewalls, PKI
- 2.5Diagnostic, logging & event tracing in connected systems
- 2.6Real-life Example: Architecting a connected vehicle stack for a luxury EV startup – problems, choices, trade-offs
- Data Strategy & Telemetry6
- 3.1Vehicle data types: CAN signals, location, status, diagnostics, user behavior
- 3.2Data lifecycle: Capture, clean, transmit, store, analyze
- 3.3Data monetization models: UBI, predictive maintenance, fleet analytics
- 3.4Edge vs. Cloud trade-offs
- 3.5Data privacy and compliance: GDPR, ISO 27001, OEM-specific rules
- 3.6Case Study: How a fleet operator reduced TCO using real-time telemetry analytics
- Cybersecurity in Connected Vehicles6
- 4.1Common threats: Man-in-the-middle, spoofing, malware injection, relay attacks
- 4.2Threat modeling for connected vehicles
- 4.3ISO/SAE 21434 – Key concepts
- 4.4Secure Boot, OTA validation, authentication frameworks
- 4.5Red team simulation overview
- 4.6Exercise: Simulate a cyber threat scenario in a connected vehicle system and respond as a team
- Regulatory & Functional Safety Landscape6
- 5.1UNECE WP.29 Cybersecurity & Software Update Regulations
- 5.2ISO 26262, ISO 21434 – Intersections & compliance strategies
- 5.3Functional safety in connected systems
- 5.4Homologation challenges for connected ECUs
- 5.5Regional variations (EU, US, China, India)
- 5.6Scenario Simulation: Delays in SOP due to OTA compliance failure – how to resolve it
- Business Models & Monetization for Connected Vehicles6
- 6.1Subscription models, pay-per-use, B2B2C strategies
- 6.2Usage-based insurance (UBI)
- 6.3Feature-on-demand (FOD), in-car commerce
- 6.4Strategic alliances: OEM-Telco, OEM-Cloud, OEM-Startup
- 6.5TCO and ROI modeling for CV programs
- 6.6Case study on how a mid-sized OEM monetized connected features in Gen-2 product line
- Testing & Validation of Connected Vehicle Features6
- 7.1Test strategies: SIL, HIL, VIL for connected ECUs
- 7.2Validation for OTA updates
- 7.3Simulators for V2X, GPS & cellular network simulation
- 7.4Cloud + lab co-testing practices
- 7.5KPIs for connectivity: latency, packet loss, uptime, jitter
- 7.6Exercise: Design a validation test suite for a new OTA feature release
- War Room Simulation – Launch Readiness for Connected Vehicle System4
- Integrating GenAI in Connected Vehicles2
Key domains: V2X, V2V, V2I, V2N, V2P
Next