Device management service
Systems and methods are described that comprise receiving at a platform an enrollment request from a client device. The enrollment request comprises a request key and device data of the client device. Device identification is generated and issued to the client device in the absence of a previous enrollment event. A response to the client device is generated, and the response is a response to the enrollment request that includes the device identification. Subsequent sessions between the client device and the platform are controlled with the device identification.
1. A method of providing care service to a client device, the method performed by a platform remote to the client device and comprising:
receiving, from the client device, an enrollment request including a request key and device data of the client device;
generating, in the absence of a previous enrollment event by the client device, a device identification in the platform;
issuing, to the client device, a response to the enrollment request that includes the device identification; and
controlling subsequent sessions between the client device and the platform using an address convention comprising the device identification generated by the platform, the address convention comprising a form including device_identification@service domain/service identification.
2. The method of claim 1 , wherein the platform is a care service platform comprising a plurality of care applications configured to provide device management services to a plurality of client devices including the client device.
3. The method of claim 1 , wherein the address convention includes a service identification component that represents a logical active session between the client device and the platform.
4. The method of claim 3 , wherein the address convention further includes a service domain identification component.
5. The method of claim 1 , wherein the enrollment request is initiated in a client application hosted on the client device.
6. The method of claim 5 , further comprising:
instructing the client application to initiate the enrollment request.
7. The method of claim 1 , 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.
8. The method of claim 1 , further comprising:
identifying a previous enrollment event of the client device using the device data; and
including, in the response, the device identification issued to the client device during the previous enrollment event.
9. The method of claim 1 , wherein the device identification includes location data of a location from which the device identification is issued.
10. The method of claim 1 , wherein the response includes an encrypted login credential.
11. The method of claim 10 , wherein the device identification and the encrypted login credential are stored in the client device.
12. The method of claim 1 , further comprising:
establishing a session between a client application of the client device and the platform upon receipt of the response.
13. The method of claim 1 , wherein a subsequent session established between the platform and the client device remains connected logically until one of the platform and the client device terminates the session, regardless of connection point location of the client device.
14. The method of claim 3 , wherein the service identification component remains constant when the client device switches a connection to the platform between a mobile data network and a Wi-Fi network.
15. A platform for providing care service to a client device, the platform remote to the client device and comprising:
a processor; and
a memory storing one or more programs that, when executed by the processor, cause the platform to perform operations comprising:
receiving, from the client device, an enrollment request including a request key and device data of the client device;
generating, in the absence of a previous enrollment event by the client device, a device identification in the platform;
issuing, to the client device, a response to the enrollment request that includes the device identification; and
controlling subsequent sessions between the client device and the platform using an address convention comprising the device identification generated by the platform, the address convention comprising a form including device identification@service domain/service identification.
16. The platform of claim 15 , wherein the platform is a care service platform comprising a plurality of care applications configured to provide device management services to a plurality of client devices including the client device.
17. The platform of claim 15 , wherein the address convention includes a service identification component that represents a logical active session between the client device and the platform.
18. The platform of claim 17 , wherein the address convention further includes a service domain identification component.
19. The platform of claim 15 , wherein the enrollment request is initiated in a client application hosted on the client device.
20. The platform of claim 19 , wherein execution of the one or more programs causes the platform to perform operations further comprising:
instructing the client application to initiate the enrollment request.
21. The platform of claim 15 , 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.
22. The platform of claim 15 , wherein execution of the one or more programs causes the platform to perform operations further comprising:
identifying a previous enrollment event of the client device using the device data; and
including, in the response, the device identification issued to the client device during the previous enrollment event.
23. The platform of claim 15 , wherein the device identification includes location data of a location from which the device identification is issued.
24. The platform of claim 15 , wherein the response includes an encrypted login credential.
25. The platform of claim 24 , wherein the device identification and the encrypted login credential are stored in the client device.
26. The platform of claim 15 , wherein execution of the one or more programs causes the platform to perform operations further comprising:
establishing a session between a client application of the client device and the platform upon receipt of the response.
27. The platform of claim 15 , wherein a subsequent session established between the platform and the client device remains connected logically until one of the platform and the client device terminates the session, regardless of connection point location of the client device.
28. The platform of claim 17 , wherein the service identification component remains constant when the client device switches a connection to the platform between a mobile data network and a Wi-Fi network.