Data flow: Updating firmware on Samsung Knox devices

This data flow describes how data travels when you use Samsung Enterprise Firmware Over the Air to control when firmware updates from Samsung are installed on devices.


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

  1. An administrator adds a Samsung E-FOTA customer ID and license key to BlackBerry UEM.
  2. The BlackBerry UEM Core sends the license information to the BlackBerry Infrastructure over a TLS connection.
  3. The BlackBerry Infrastructure establishes a TLS connection with the Samsung E-FOTA servers and provides the customer ID and license key.
  4. The E-FOTA server verifies the information and returns license information through the BlackBerry Infrastructure to BlackBerry UEM Core.
  5. An administrator creates a device SR requirements profile and specifies a Samsung device model, language, and wireless service provider for a new Samsung device firmware rule.
  6. The BlackBerry UEM Core connects to the E-FOTA server via the BlackBerry Infrastructure over a TLS connection and sends the specified criteria to the E-FOTA server.
  7. The E-FOTA server verifies the criteria and returns firmware information through the BlackBerry Infrastructure to BlackBerry UEM Core.
  8. The administrator saves the new device SR requirements profile.
  9. The BlackBerry UEM Core connects to the E-FOTA server via the BlackBerry Infrastructure over a TLS connection and sends the profile to the Samsung Cloud.
  10. The administrator assigns the device SR requirements profile to one or more users.
  11. BlackBerry UEM sends the profile to the BlackBerry UEM Client on the user's Samsung device.
  12. The Samsung device registers with the E-FOTA server.
  13. If a firmware update is available that meets the parameters specified in the device SR requirements profile, the E-FOTA server sends the update to the device.