Campaign Lifecycle Flow for v1

Campaign Lifecycle Flow for OMA-DM or LWM2M Devices using the /v1 Resource Path

1. The campaign always starts with a user scheduling the campaign with proper make, model, and current software prerequisites to be updated and identifying the software to be updated and when.
2. After the user sends the campaign request, the campaign changes to “Request Pending” status.
   1. After passing parameter checks, the campaign status moves to “Queued”.
      Parameter checks could include things like FOTA eligibility, unknown client type, make, model, firmware, and determining if the device is in another campaign.
   2. If parameter checks fail, it moves to "RequestFailed."
3. The campaign stays in “Queued” status while the systems collect requests.
   1. Normally the campaign would move to "in progress." This stage is is when the software updates are executed in the OMA-DM or LWM2M server.
   2. User can choose to cancel the campaign before the start date, or they can remove all devices from the queued campaign.
4. After the campaign starts, it is "in progress" during the device update.
   1. Once the campaign end date has been reached, the campaign status moves to "Finished."
   2. If the OMA-DM or LWM2M server schedule a campaign, it moves to "UpgradeFailed" status.

Device Lifecycle Flow for OMA-DM or LWM2M Devices using the /v1 Resource Path

Status and Error Messages for OMA-DM ro LWM2M Devices using the /v1 Resource Path