Remote management of mobile devices

• US 20060277590A1
• Filed: 06/03/2005
• Published: 12/07/2006
• Est. Priority Date: 06/03/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Yang, Zhidong, Tousignant, Patrick, Limont, David Paul, Aftab, Omar A.
• Granted Patent: US 7,516,478 B2
• Time in Patent Office: Days
• 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:

identifying a policy on the mobile device;

detecting a validation of the policy by the server;

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

verify 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 in to the server, to enable employing a single communication channel during interaction with the mobile device.

3. The method of claim 1 further comprising denying a non-compliant mobile device synchronization services of the server.

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

5. The method of claim 1 further comprising forcing at least one of a PIN lock arrangement and 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 issuing a first response by the server that identifies at least one of a policy key and content type to the mobile device, upon a first request by the mobile device for synchronization with the server.

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

11. The method of claim 9 further comprising determining whether the mobile device has previously been provisioned by the server, and if not displaying a dialog box to user of the mobile device to opt out of synchronization with the server.

12. The method of claim 9 further comprising trusting the mobile device by the server for initiating of synchronization.

13. The method of claim 9 further comprising request and down load of settings to the client.

14. The method of claim 13 further comprising receiving acknowledgement and receipt of settings by the server from the mobile device.

15. The method of claim 14 further comprising receiving request by the server for updated policy settings.

16. 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;

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

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

18. The system of claim 17, the connection instance includes identity of the mobile device that require configuration by the server.

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

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

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

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