Your Vehicle Passed Type Approval. Can an OTA Update Make It Non-Compliant?
Your vehicle already passed type approval.
Then your software team releases an OTA update.
No hardware change.
No new ECU.
No physical modification.
So why should compliance teams care?
Because software can change the behavior of a type-approved vehicle.
And the critical question is not:
“Do we need to retest every OTA update?”
The better question is:
“What regulatory evidence does this software update change?”
This distinction is becoming increasingly important as vehicles move from fixed-function products toward software-defined vehicles (SDVs).
OTA Is No Longer Just a Software Team Issue
An OTA package may look like a software change to engineering.
But from a compliance perspective, it can potentially affect:
Bluetooth functionality
Wi-Fi operation
Cellular communication
eCall behavior
Infotainment functions
ADAS functions
Cybersecurity controls
RF parameters
EMC behavior
User-accessible vehicle functions
Software identifiers linked to regulated systems
UN Regulation No. 156 establishes requirements for software updates and Software Update Management Systems (SUMS). It requires manufacturers to have processes to identify software relevant to type approval and assess whether an update affects type-approved characteristics, safety or other regulated aspects.
So:
OTA does not automatically mean “re-certification.”
But OTA also does not mean:
“No certification impact because the hardware did not change.”
The Most Important Concept: Change Impact Assessment
Imagine your vehicle has already completed:
RF → EMC → eCall → Bluetooth → Wi-Fi → Vehicle Approval
Now an OTA update changes the Bluetooth stack.
The product manager may see:
“Just a connectivity improvement.”
The compliance engineer should ask:
What changed in the approved configuration?
For example:
Bluetooth Stack Update
↓
Bluetooth behavior changes?
↓
RF parameters affected?
↓
New transmission mode?
↓
Different operating conditions?
↓
EMC behavior affected?
↓
Existing test evidence still representative?
↓
Compliance Impact Assessment
This is the mindset manufacturers need.
Not Every OTA Update Has the Same Compliance Risk
A practical classification can help engineering and compliance teams decide what happens next.
| OTA Change | Typical Compliance Review |
|---|---|
| UI wording / visual change | Low regulatory impact in many cases |
| Infotainment UI logic | Functional review |
| Bluetooth stack update | RF + connectivity review |
| Wi-Fi firmware update | RF + EMC + functionality review |
| Cellular modem firmware | RF + network + eCall review |
| eCall software change | Safety + communication + regulatory review |
| ADAS software update | Potentially major approval impact |
| Cybersecurity patch | R155/R156 process & evidence review |
| New wireless function | Certification scope assessment |
| Change to regulated vehicle function | Type-approval impact assessment |
This is not a universal classification table.
The actual impact depends on the vehicle type, applicable regulations, approved configuration and what the software changes.
That is exactly why a documented OTA impact assessment is necessary.
What Does UN R156 Actually Require?
UN R156 is built around a Software Update Management System, not simply a one-time software test.
The manufacturer needs to demonstrate that software updates are properly managed.
This includes identifying relevant software, managing updates, maintaining software configuration information and assessing the consequences of updates.
For OTA specifically, the requirements also address issues such as:
Update authenticity and integrity
Software identification
Protection of software configuration
Recovery from failed/interrupted updates
Sufficient vehicle power
Safe execution
User information
Post-update status
UNECE's requirements specifically address recovery or safe-state behavior if an OTA update fails or is interrupted.
So the compliance question extends beyond:
“Does the new software work?”
It becomes:
“Can the manufacturer control, verify and demonstrate the complete software update process?”
The Hidden Risk for Connected Vehicles
This becomes even more important when the vehicle contains multiple connected systems.
Consider a modern vehicle architecture:
OTA Platform
↓
Telematics / T-Box
↓
Cellular
↓
Bluetooth / Wi-Fi
↓
Infotainment
↓
eCall
↓
Vehicle Gateway
↓
Multiple ECUs
A single software release may affect several systems simultaneously.
For example, a new connectivity package could change:
Bluetooth pairing behavior
Wi-Fi coexistence
Cellular modem behavior
Antenna operating conditions
eCall communication
Audio routing
CAN messages
Gateway behavior
This is why software configuration and compliance evidence must be connected.
The OTA Compliance Decision Tree
Before releasing an OTA update, ask:
1. What changed?
Software version? Firmware? Configuration? Communication protocol? New function?
↓
2. Which vehicle system is affected?
Infotainment? Bluetooth? Wi-Fi? T-Box? eCall? ADAS? Gateway?
↓
3. Does it affect a type-approved characteristic?
If no, document the assessment.
If yes, continue.
↓
4. Does the existing test evidence still represent the new configuration?
If yes, reuse where justified.
If no, identify the required validation.
↓
5. Does the update affect safety, cybersecurity or regulated functions?
If yes, escalate the assessment.
↓
6. Is additional testing or approval action required?
Only then should the project move toward the appropriate validation, revision or approval process.
This approach prevents two expensive mistakes:
Over-testing every software release
and
Underestimating a software change that actually affects compliance.
Where RF & EMC Teams Need to Get Involved
One mistake I see in connected-vehicle projects is treating software and RF/EMC as completely separate.
They are not always separate.
A software update can change:
Radio duty cycle
Channel selection
Transmit behavior
Bluetooth/Wi-Fi coexistence
Cellular operating modes
Power consumption
Communication timing
Simultaneous radio operation
These changes can potentially affect the RF or EMC behavior of the final vehicle configuration.
Therefore, a software change assessment should sometimes trigger a technical question:
Does the new software change the RF operating condition that was previously tested?
If the answer is yes, the existing report may need a technical review before it is reused.
What About CarPlay, Android Auto and eCall?
This is where OTA becomes particularly relevant to connected-vehicle manufacturers.
A firmware update can change:
CarPlay
Wired/wireless connection
Bluetooth discovery
Wi-Fi behavior
USB communication
Reconnection logic
Android Auto
USB behavior
Wireless projection
Bluetooth pairing
Wi-Fi connection
Phone compatibility
eCall
Cellular behavior
IMS/network communication
Emergency-call procedures
MSD handling
GNSS interaction
The function may still appear to be “the same product.”
But the validated configuration may no longer be identical.
That is why the compliance team needs a connection between:
Software Version → Hardware Version → RF Configuration → Test Evidence → Approval
A Simple OTA Compliance Evidence Matrix
I recommend manufacturers maintain something similar to this:
| Software Version | Hardware | Function | Regulatory Impact | Existing Evidence | Action |
|---|---|---|---|---|---|
| V1.0 | HW-A | Wi-Fi | Existing | RF/EMC report | — |
| V1.1 | HW-A | Wi-Fi optimization | Review | Existing | Engineering assessment |
| V1.2 | HW-A | New RF mode | Potential | Existing | RF review |
| V2.0 | HW-A | New eCall function | High | Partial | Validation |
| V3.0 | HW-B | New cellular module | Major | Not representative | New assessment |
The objective is simple:
Every production software version should have a traceable compliance decision.
What Automotive Manufacturers Should Ask Before the Next OTA Release
Before approving a software release, ask these seven questions:
1. What regulatory or safety-related functions changed?
2. Does the update change any RF operating parameters or communication behavior?
3. Does it affect Bluetooth, Wi-Fi, cellular or eCall?
4. Does the existing test report still represent the new software configuration?
5. Does the update affect a type-approved characteristic?
6. Is additional RF, EMC, connectivity or vehicle-level validation required?
7. Has the compliance decision been documented and linked to the exact software version?
If these questions cannot be answered, the OTA process is not yet compliance-ready.
Where BlueAsia Can Help
This is also where a testing laboratory can provide value beyond simply issuing a report.
At BlueAsia, we work with:
Automotive OEMs
T-Box / telematics suppliers
Infotainment manufacturers
Connected-display manufacturers
Bluetooth / Wi-Fi automotive product developers
Automotive ECU suppliers
Connected vehicle electronics manufacturers
Our capabilities cover:
RF Testing + EMC Testing + Bluetooth + Wi-Fi + Automotive Connectivity + eCall-related validation + Compliance Evidence Review
For an OTA project, our role can be to help determine:
What changed?
→ What technical characteristics could be affected?
→ Does the existing evidence remain representative?
→ What needs engineering validation?
→ What needs formal compliance action?
This can help manufacturers avoid both unnecessary retesting and late-stage compliance surprises.
The CEO Takeaway
The automotive industry is moving toward continuous software development.
That means the old compliance model:
Design → Test → Certify → Freeze
is becoming less practical for connected vehicles.
The new reality is closer to:
Design → Validate → Approve → Update → Assess → Revalidate When Necessary
UN R156 is fundamentally about creating the management framework to control this process. VCA describes the regulation as an audit-based approach covering software updates and their continued impact on regulatory compliance, cybersecurity and vehicle safety.
So, can an OTA update make an approved vehicle non-compliant?
Yes, potentially—but not because every OTA update requires re-certification.
The real risk is releasing software without knowing whether the update changes something that was part of the vehicle's approved configuration.
The question is not “Can we update the software?”
The question is “What regulatory evidence does this software update change?”
If your vehicle platform supports OTA, Bluetooth, Wi-Fi, cellular, CarPlay, Android Auto, eCall or other connected functions, BlueAsia can help review the technical and compliance impact before the software reaches production.