Validating availability of firmware updates for client devices

1. A method of operating a device management platform, the method comprising:

receiving device data from each of a plurality of client devices;

storing the device data in a plurality of device files, each device file including firmware version information for a corresponding client device;

replicating the plurality of device files to a plurality of distribution platforms; and

for each client device of the plurality of client devices:

selecting one of the plurality of distribution platforms to transmit a corresponding one of the plurality of device files to the client device, wherein the selected distribution platform is the distribution platform that is geographically closest to the client device; and

enabling an update server to transmit a new device data file to the client device based at least in part on the corresponding device file.

2. The method of claim 1 , wherein each device file corresponds to a respective client device.

3. The method of claim 1 , wherein each of the plurality of distribution platforms is located in a different geographical region that is remote to the device management platform.

4. The method of claim 1 , further comprising generating a plurality of updated device data files by updating the plurality of device files as new device data becomes available for the plurality of client devices.

5. The method of claim 4 , further comprising propagating the plurality of updated device data files to the plurality of distribution platforms.

6. The method of claim 1 , wherein the selected distribution platform is to periodically transmit the corresponding device file to the client device.

7. The method of claim 1 , wherein the client device is to determine that the new device data file is available by comparing a current firmware version of the client device with the firmware version information of the corresponding device file.

8. The method of claim 1 , wherein the new device data file comprises a new firmware image for the client device.

9. The method of claim 1 , comprising:

receiving an enrollment request from each client device, wherein the enrollment request comprises a request key and the device data of the client device;

generating a device identification for the client device;

transmitting a response to the client device, wherein the response includes the device identification; and

controlling subsequent sessions between the client device and the device management platform using the device identification.

10. The method of claim 9 , wherein the subsequent sessions each use an address convention comprising the device identification, wherein the address convention includes a service identification component that represents a logical active session between the client device and the platform, and a service domain identification component.

11. The method of claim 9 , wherein the device data comprises at least one of a device identification number, a device manufacturer, a manufacturer serial number, a model number, International Mobile Subscriber Identity (IMSI), International Mobile Station Equipment Identity (IMEI), Mobile Subscriber Integrated Services Digital Network-Number (MSISDN), a media access control (MAC) address, carrier data of a carrier corresponding to the client device, and state data of the client device.

12. The method of claim 9 , wherein the device identification includes location data of a location for which the device identification was generated.

13. The method of claim 9 , wherein the response includes an encrypted login credential, the method further comprising establishing a session with a client application of the client device after transmitting the response.

14. A device management platform comprising:

one or more processors; and

a memory storing instructions that, when executed by the one or more processors, cause the device management platform to:

receive device data from each of a plurality of client devices;

store the device data in a plurality of device files, wherein each device file includes firmware version information for a corresponding client device;

replicate the plurality of device files to a plurality of distribution platforms; and

for each client device of the plurality of client devices:

select one of the plurality of distribution platforms to transmit a corresponding one of the plurality of device files to the client device, wherein the selected distribution platform is the distribution platform that is geographically closest to the client device; and

enable an update server to transmit a new device data file to the client device based at least in part on the corresponding device file.

15. The device management platform of claim 14 , wherein each of the plurality of distribution platforms is located in a different geographical region that is remote to the device management platform.

16. The device management platform of claim 14 , wherein execution of the instructions further causes the device management platform to:

generate a plurality of updated device data files by updating the plurality of device files as new device data becomes available for the plurality of client devices; and

propagate the plurality of updated device data files to the plurality of distribution platforms.

17. The device management platform of claim 14 , wherein the selected distribution platform is to periodically transmit the corresponding device file to the client device.

18. The device management platform of claim 14 , wherein the client device is to determine that the new device data file is available by comparing a current firmware version of the client device with the firmware version information of the corresponding device file.

19. The device management platform of claim 14 , wherein the new device data file comprises a new firmware image for the client device.

20. The device management platform of claim 14 , wherein execution of the instructions further causes the device management platform to:

receive an enrollment request from each client device, wherein the enrollment request comprises a request key and the device data of the client device;

generate a device identification for the client device;

transmit a response to the client device, wherein the response includes the device identification; and

control subsequent sessions between the client device and the device management platform using the device identification.

21. The device management platform of claim 20 , wherein the subsequent sessions each use an address convention comprising the device identification, wherein the address convention includes a service identification component that represents a logical active session between the client device and the platform, and a service domain identification component.

22. The device management platform of claim 20 , wherein the device data comprises at least one of a device identification number, a device manufacturer, a manufacturer serial number, a model number, International Mobile Subscriber Identity (IMSI), International Mobile Station Equipment Identity (IMEI), Mobile Subscriber Integrated Services Digital Network-Number (MSISDN), a media access control (MAC) address, carrier data of a carrier corresponding to the client device, and state data of the client device.

23. The device management platform of claim 20 , wherein the device identification includes location data of a location for which the device identification was generated.

24. The device management platform of claim 20 , wherein the response includes an encrypted login credential and wherein execution of the instructions further causes the device management platform to establish a session with a client application of the client device after transmitting the response.