# 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. - 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. - If parameter checks fail, it moves to "RequestFailed." 3. The campaign stays in “Queued” status while the systems collect requests. - 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. - 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. - Once the campaign end date has been reached, the campaign status moves to "Finished." - 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 | Device Status | Device Detail Status | | ------------------- | -------------------------------------------------------------------------------------------------------------- | | Device Accepted | Device cleared all check so it can be added to the scheduled list. | | Device Rejected | Device not found. | | Device Rejected | Invalid Device IMEI. | | Device Rejected | Device not eligible for service. | | Device Rejected | Unknown client device type. | | LicenseRemoveFailed | License removal not allowed for devices that have ever upgraded firmware. | | LicenseRemoveFailed | Internal error. | | Device Rejected | Device scheduled for firmware-upgrade previously, it needs to be completed before another upgrade is schedule. | | Device Rejected | Device make/model do not meet firmware prerequisites. | | Device Rejected | Current device firmware version does not meet firmware prerequisites. | | Upgrade Failed | Device is not in an active state or is not connected. | | Upgrade Failed | Current device module does not meet firmware prerequisites. | | Upgrade Failed | Firmware update to device failed. | | Upgrade Failed | Internal System Error. Please retry upgrade. | | Upgrade Success | The firmware upgrade was successful. |