How do you ensure safety for over-the-air (OTA) updates of ADAS/AV software?

OTA safety assurance: 1) Update validation - comprehensive testing before release (simulation, HIL, vehicle testing), rollback capability if issues detected; 2) Incremental deployment - staged rollout (small fleet percentage, geographic regions), monitoring for issues before wider release; 3) In-vehicle safety - update integrity verification, secure boot chain, A/B partition scheme for atomic updates, safety checks before activating update; 4) Change management - impact assessment for any modification affecting safety functions, re-certification requirements, documentation; 5) Monitoring and response - field performance monitoring, rapid response capability for issues, ability to disable features remotely. Regulatory requirements (UNECE WP.29) mandate software update management systems. Balance between rapid improvement and safety assurance. Testing cannot completely validate every configuration and environmental condition.