Data flow: Receiving configuration updates on an Android device


Diagram showing the steps and components mentioned in the following data flow.

  1. An action is taken in the management console that triggers a configuration update for an Android device.
  2. Updates are applied in BlackBerry UEM, and objects that must be shared with the device are identified.
  3. The BlackBerry UEM Core contacts the BlackBerry Infrastructure, through the BlackBerry Router or TCP proxy server, if installed, and the external firewall over port 3101.
  4. The BlackBerry Infrastructure uses the FCM to notify Android devices that an update is pending.
  5. The FCM sends a notification to the BlackBerry UEM Client on the Android device to contact the BlackBerry UEM Core.
  6. The BlackBerry UEM Client contacts the BlackBerry UEM Core, on port 3101 on the external firewall, to request any pending actions and commands that must be performed on the device.
  7. The BlackBerry UEM Core replies, through the BlackBerry Infrastructure and BlackBerry Router or TCP proxy server, if installed, with the highest priority action.

    Priority is given to IT administration commands, such as Delete device data and Lock device, followed by requests for device information, installed apps, and so on. The BlackBerry UEM Core sends only one command at a time. If necessary, additional information is included in the response.

  8. The BlackBerry UEM Client inspects the response, schedules the command to be processed, and waits for the command to be run. The BlackBerry UEM Client sends a response to the BlackBerry UEM Core, through the BlackBerry Infrastructure, to update the command status. The status indicates whether the command ran successfully and provides an error message in the event of a failure.
  9. If more actions or commands are pending for the device, the BlackBerry UEM Core replies, through the BlackBerry Infrastructure, with the highest priority action. If no actions or commands are pending for the device, the BlackBerry UEM Core replies with an idle command.

    Steps 7 to 9 are repeated until no more pending actions or commands must be performed on the device.