Share via

Target Device Download Event (Windows Embedded CE 6.0)

  • Article

1/6/2010

When the target device receives the download instruction response, it schedules a download event. The download event can be triggered immediately or can be triggered only under specific conditions, such as when the target device is docked. The scheduling criteria, including time schedule and bandwidth restrictions, are part of the download instruction response.

A download event can be recurring or non-recurring. In either case, the download event consists of four phases:

  • The target device sends a package location request message to the server to get the current download URL. The server responds with a package location response to target device.
  • The target device sends a status report that indicates the beginning of the download event.
  • The target device sends status reports that indicate the end of the download event. When the download is successful, it triggers the execution of the post install command. This is the command that the target device should execute after the package is downloaded.
  • The target device sends status reports that indicates the end of execution of the post install command.

The server may designate a download event as recurring when it sends the instruction response to the target device. A recurring download event can be one of the following two types:

  • Download package on every recurrence.
  • Download package only on first execution and only execute the post install command on recurrence.

See Also

Concepts

Device Management Operation
Package Location Request to Server
Package Location Response to Target Device
Download Event Status Reports