OTA Connect User Guide

OTA update workflow

To deploy OTA updates in production, we use the concept of a campaign. We’ll go into more details about campaigns later, but to understand the workflow, you first need to understand what goes into a campaign.

A campaign consists of the following elements:

  • The relevant software update and the supported hardware.

  • The new software versions to which you want to update.

  • The groups of devices that you want to target for this update.


In the OTA workflow, you set up each of these elements in a specific order.

Table 1. Overview of the OTA update worklow
1) Provision devices 2) Upload a software version 3) Group devices 4) Create a software update

Connect your devices to the OTA Connect server. The server stores the following information about each device:

  • The device name or identifier (often a VIN)

  • The serial number and control unit type of each control unit in the device

  • The software version that each control unit is currently running


Upload new software versions.


Put your devices into groups. For example, you can create groups based on regional markets.


Define the software versions that you want to update and the new replacement versions.