OTA Firmware Update Architecture for Windows Mobile Version 5.0

6/2/2010

The following illustration shows the architecture of the OTA Firmware Update process:

The following numbered steps correspond with the numbers in the illustration:

1. Using WAP Push, the OMA DM server sends an alert Short Message Service (SMS) trigger to the client device. The SMS message includes the server ID and directs the client device to initiate a session with the OMA DM server. The client device uses the Server ID to verify that the server is authorized to communicate with it.
2. The client device sends a message over an IP connection to initiate the session. This message includes device information (DevInfo header) and credentials, if required.
3. The server sends a ROMPackage object query to the client device to get its ROM version information. The client device uses the ROMPackage Configuration Service Provider to return version information to the OMA DM server.
4. Based on the ROM version information, the OMA DM server determines which update package should be implemented. The OMA DM server then sends the package information, including a URL indicating the location of the package, to the FwUpdate Configuration Service Provider. The OMA DM server then performs an Exec command.
5. The FwUpdate Configuration Service Provider accepts the request and then passes the package download URL to the Download Agent.
6. The Download Agent notifies the user of the update and then downloads the package from the server. The download agent must use HTTP protocol and support byte range headers.
   For more information about downloading the package, see Downloading OTA Firmware Update Package Content.
7. The Download Agent calls the device Image Update installer to install the update. The Update Agent (UpdateBin.exe) initiates the update process. If the installation succeeds, the device reboots and a UI prompt informs the user that the installation succeeded. If the installation fails, the Download Agent maps the failure code to a FwUpdate Configuration Service Provider-managed object result code.
8. The State node in the FwUpdate Configuration Service Provider is updated with download failure or success.
9. The OMA DM server queries the ROMPackage object to verify that the version node contains the updated version information.

The following table lists sources of additional information.