Remote management of mobile devices

• US 7,516,478 B2
• Filed: 06/03/2005
• Issued: 04/07/2009
• Est. Priority Date: 06/03/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Aftab, Omar A., Yang, Zhidong, Tousignant, Patrick, Limont, David Paul
• Primary Examiner(s): Barron, Jr.; Gilberto
• Assistant Examiner(s): Yousefi; Shahrouz
• Application Number:
  US11/145,282
• Publication Number:
  US 20060277590A1
• Time in Patent Office: 1,404 Days
• Field of Search: 726 1- 3, 726/16, 726/11, 726/29, 726/35, 713/168, 713182-183, 380/258
• US Class Current: 726/1
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

Systems and methodologies that proactively push down and enforce policies of a server(s) on mobile devices, when such devices connect to the server(s) for data synchronization. The subject invention employs a policy delivery and enforcement logic that is integrated as part of a communication channel (e.g. a single communication channel) with the mobile device(s). A hand shake can take place between the mobile devices and the server every time that a new policy occurs. Accordingly, non-compliant devices are denied service from the server.

Claims

1. A method of synchronization between a mobile device and a server, comprising:

issuing a synchronization command from the mobile device to the server, the synchronization command including at least a first policy key identifying the current policy in use by the mobile device and a content type identifying a format for policy settings understandable by the mobile device;

identifying the current policy on the mobile device;

detecting at the server that the current policy in use by the mobile device is invalid by the server;

determining whether the mobile device has previously been provisioned by the server, and upon determining that the mobile device has not been provisioned displaying a dialog box to a user of the mobile device to allow the user to opt out of synchronization of the mobile device with the server;

issuing a first response by the server formatted in accordance with the content type that identifies at least one of a second policy key and content type to the mobile device in response to the synchronization request by the mobile device, the second policy key identifying a new policy to be used by the mobile device;

proactively setting the new policy on the mobile device by the server prior to permitting a synchronization of the mobile device with the server, and

verifying enforcement of the new policy on the mobile device by the server.

2. The method of claim 1, further comprising integrating policy settings and configuration at the server to enable employing a single communication channel during interaction with the mobile device.

3. The method of claim 1, further comprising denying synchronization services to a mobile device having a non-compliant policy.

4. The method of claim 1, further comprising issuing an error message by the server upon identification of a mobile device having a non-compliant policy.

5. The method of claim 1, further comprising forcing at least one of a PIN lock arrangement or a PIN lock minimum length on the mobile device.

6. The method of claim 1, further comprising forcing a local wipe on the mobile device.

7. The method of claim 1, further comprising imposing arbitrary policies on the mobile device.

8. The method of claim 1, further comprising issuing a provisioning command to negotiate policy settings between the mobile device and the server.

9. The method of claim 1, further comprising receiving a second request at the server from the mobile device that identifies policy key and status.

10. The method of claim 1, further comprising trusting the mobile device by the server for initiating of synchronization upon receiving confirmation from the mobile device that the new policy has been applied.

11. The method of claim 1, further comprising downloading settings to the client in response to a request from the client.

12. The method of claim 11, further comprising receiving acknowledgement and receipt of settings by the server from the mobile device.

13. The method of claim 12, further comprising receiving request at the server from the mobile device for updated policy settings.

14. A system of setting policies from a server to a mobile device comprising:

a configuration manager that proactively sets server policies on the mobile device in response to a synchronization request from the mobile device, the synchronization request including at least a first policy key identifying a policy currently in use by the mobile device and a content type identifying a format in which the mobile device prefers to receive policy settings, the configuration manager sending a response to the mobile device that includes at least a second policy key identifying a new server policy to be used by the mobile device, the response formatted in accordance with the content type; and

a setting library that facilitates a track authorization, security, and validation of the mobile device that requests connection to the server.

15. The system of claim 14, a connection instance generated by the configuration manager and dynamically updated to reflect transmission progress between the server and the mobile device.

16. The system of claim 15, the connection instance includes identity of the mobile device that requires configuration by the server.

17. The system of claim 16, the connection instance facilitates verification for installations of policy configurations on the mobile device.

18. A system of setting policies from a server to a mobile device comprising;

means for receiving a synchronization request from the mobile device at the server, the synchronization request including at least a first policy key identifying a current policy in use by the mobile device and a content type indicating a preferred format for policy settings;

means for proactively setting a new policy on the mobile device via a response signal from the server prior to permitting a synchronization of the mobile device with the server, the response signal formatted in accordance with the content type and including at least a second policy key indicating the new policy, and

means for verifying enforcement of the new policy on the mobile device by the server, and

means for determining whether the mobile device has previously been provisioned by the server, and upon determining that the mobile device has not been provisioned displaying a dialog box to a user of the mobile device to allow the user to opt out of synchronization of the mobile device with the server.

19. The system of claim 18, further comprising means for forcing a local wipe on the mobile device.

20. The system of claim 18, further comprising means for denying synchronization services to a mobile device having a non-compliant policy.