Melting information on a client device

• US 7,783,310 B2
• Filed: 08/23/2006
• Issued: 08/24/2010
• Est. Priority Date: 07/14/2003
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Orative Corp. (Cisco Systems, Inc.)
• Inventors: Shah, Ankur, Perfetto, Josh, Schramm, Steven D., Fullarton, Paul, Chatterjee, Saurav, Rana, Hemendra
• Primary Examiner(s): Al Aubaidi; Rasha S
• Application Number:
  US11/509,472
• Publication Number:
  US 20070049304A1
• Time in Patent Office: 1,462 Days
• Field of Search: 379/211.02, 455/466
• US Class Current: 455/466
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04M 2203/1091 Fixed mobile conversion
• CPC Class Codes: H04M 2203/2011 Service processing based on information specified by a party before or during a call, e.g. information, tone or routing selection
• CPC Class Codes: H04M 2207/206 composed of PSTN and wireless network
• CPC Class Codes: H04M 3/42093 Notifying the calling party of information on the called or connected party
• CPC Class Codes: H04M 3/42263 where the same subscriber uses different terminals, i.e. nomadism
• CPC Class Codes: H04M 3/42365 Presence services providing information on the willingness to communicate or the ability to communicate in terms of media capability or network connectivity
• CPC Class Codes: H04M 3/436 Arrangements for screening incoming calls , i.e. evaluating the characteristics of a call before deciding whether to answer it based on the calling party profile H04M3/42059; based on location H04M3/42348; based on presence H04M3/42365; diversion H04M3/54

Abstract

Melting information of a client device is described. The device melting includes receiving a melt message at an inbox of a client device. A source of the melt message is authenticated using identification information of the melt message. The client device automatically deletes client state information of the client device in response to authenticating the source of the melt message.

Claims

1. A method, comprising:

receiving a first data component from a facilitator wherein the first data component includes data representative of an identification of the facilitator as an authenticated source;

storing the first data component on a client device;

storing client state information comprising enterprise information of a host enterprise on the client device;

receiving, from the facilitator, a message at a common inbox of the client device, wherein the message includes a melt command, the first data component, and a second data component, wherein the second data component comprises data to enable identification of an application for parsing the message and data to enable searching for the message in the common inbox;

identifying an application for parsing the message in the common inbox in accordance with the second data component;

parsing the message by the application identified in accordance with the second data component, determining from parsing the message that the message contains the melt command, and obtaining the first data component from the message;

authenticating a source of the message by comparing the first data component obtained from the received message with the first data component stored on the client device; and

automatically deleting client state information of the client device based on the melt command in response to determining the message is from an authenticated source, wherein the deleted client state information includes the enterprise information stored on the client device.

2. The method of claim 1, wherein the first data components includes a pseudo-random number.

3. The method of claim 1, wherein the first data component comprises a Globally Unique Identifier (GUID).

4. The method of claim 1, comprising determining a connectivity state of the client device.

5. The method of claim 4, comprising transmitting the message from a host server when the connectivity state of the client device is connected with the host server.

6. The method of claim 4, comprising, when the connectivity state of the client device is a persistent connection state with a host server:

detecting a coupling of the client device with the host server; and

detecting an attempt by the client device to authenticate with the host server and, in response, transmitting the message.

7. The method of claim 1, comprising pushing the message to the client device, wherein the message is an application-directed message, wherein the source is a host server.

8. The method of claim 7, wherein the pushing the application-directed message includes pushing a one of a Short Message Service (SMS) message, an electronic mail (email) message, a device-specific electronic message, a Wireless Application Protocol (WAP) push message, a Blackberry push message, or a device-specific push message.

9. The method of claim 1, comprising removing a session maintained by the source on behalf of the client device.

10. The method of claim 9, comprising, when unable to verify a session between the client device and the host server, detecting an attempt by the client device to authenticate with the host server and, in response, transmitting the message.

11. The method of claim 1, wherein the receiving said message includes receiving a push message.

12. The method of claim 1, further comprising transmitting the message to the client device, wherein the transmitting includes pushing the message to the client device.

13. The method of claim 1, wherein said receiving the message includes receiving a one of a Short Message Service (SMS) message, an electronic mail (email) message, a device-specific electronic message, or a device-specific push message.

14. The method of claim 1, comprising receiving an electronic instruction to inactivate the device.

15. The method of claim 1, comprising re-authenticating the client device, wherein the re-authenticating re-synchronizes the client state information reinstated on the client device.

16. The method of claim 1, comprising re-provisioning the client device, wherein the re-provisioning reinstates the client state information on the client device.

17. The method of claim 16, wherein the re-provisioning comprises:

receiving a re-provisioning message at the inbox of the client device;

automatically transferring an application to the client device in response to selection of the re-provisioning message; and

automatically launching the application upon receipt at the client device, the launching including re-configuring the client device and re-synchronizing the client device.

18. The method of claim 17, further comprising transmitting the re-provisioning message to the client device, wherein the transmitting includes pushing the message to the client device.

19. The method of claim 17, wherein said receiving the re-provisioning message includes receiving a one of a Short Message Service (SMS) message, an electronic mail (email) message, a Wireless Application Protocol (WAP) push message, a Blackberry push message, a device-specific electronic message, or a device-specific push message.

20. The method of claim 17, wherein said receiving the re-provisioning message includes receiving one or more of electronic provisioning information of a source device or user information of a user of the client device.

21. The method of claim 20, wherein said receiving the provisioning information includes receiving a Uniform Resource Locator (URL) for locating the source device and its access mechanism.

22. The method of claim 20, wherein said receiving the provisioning information includes receiving information of one or more of a host name of the source device of the re-provisioning message, a provisioning port, an identification of the client device, user information, a port for remote couplings via a Web browser, a device access point string, a security level of the coupling, and a string agreed upon by the source device and the client device to indicating the provisioning URL.

23. The method of claim 17, wherein the source is one or more of a provisioning server, at least one server hosting the provisioning server, a proxy server coupled to the provisioning server, and a load balancer coupled to the provisioning server.

24. The method of claim 17, wherein the receiving the re-provisioning message includes user selection of a component of the message.

25. The method of claim 24, wherein the user selection of the component of the re-provisioning message includes user selection of a Uniform Resource Locator (URL) for a source of the message.

26. The method of claim 17, wherein automatically transferring comprises:

launching a browser of the client device; and

forming a coupling with the source device.

27. The method of claim 17, wherein automatically transferring comprises downloading the application to the client device using a browser of the client device.

28. The method of claim 17, wherein the configuring comprises:

searching the inbox and locating the message;

parsing the message for one or more of electronic provisioning information and user information of a user of the client device.

29. The method of claim 28, wherein the provisioning information includes provisioning information of one or more of a host name of a source device of the message, wherein the source device is one or more of a server, facilitator, and endpoint of a provisioning server, a host name of a synchronization facilitator server, service provider information, a provisioning port, a synchronization port, client device information, user information, a port for remote couplings via a Web browser, a device access point, security levels of a plurality of couplings, and a string agreed upon by the source device and the client device to indicating the provisioning URL.

30. The method of claim 17, wherein the source is a load balancer coupled to a provisioning server.

31. A system comprising:

a client device operable to communicate with a server that is coupled to an enterprise and a communication network, wherein the client device is configured to host enterprise information of the enterprise;

wherein the client device is configured to receive a first data component from a facilitator wherein the first data component includes data representative of an identification of the facilitator as an authenticated source;

wherein the client device is configured to store the first data component;

wherein the client device is configured to receive a message at a common inbox, from a facilitator, wherein the message includes a melt command, the first data component, and a second data component, wherein the second data component comprises data to enable identification of an application for parsing the message and to enable searching for the message in the common inbox;

wherein the client device is configured to identify an application for parsing the message in the common inbox in accordance with the second data component;

wherein the client device is configured to employ the application identified in accordance with the second data component to parse the message, to determine the message includes the melt command, and to acquire the second data component;

wherein the client device is configured to authenticate a source of the message by comparing the first data component obtained from the received message with the first data component stored on the client device;

wherein the client device is configured to automatically delete client state information of the client device in response to determining the message is from an authenticated source; and

wherein the client state information automatically deleted includes the enterprise information stored on the client device.

32. The system of claim 31, wherein at least one component of the system is configured to determine a connectivity state of the client device.

33. The system of claim 32, wherein at least one component of the system is configured to push the message from a host server when the connectivity state of the client device is connected with the host server.

34. The system of claim 32, wherein at least one component of the system is configured to, when the connectivity state of the client device is a persistent connection state with a host server:

detect a coupling of the client device with the server; and

detect an attempt by the client device to authenticate with the host server and, in response, transmit the message.

35. The system of claim 31, wherein at least one component of the system is configured to remove a session maintained by the source on behalf of the client device.

36. The system of claim 35, wherein at least one component of the system is configured to, when unable to verify a session between the client device and the host server, detect an attempt by the client device to authenticate with the host server and, in response, transmit the message.

37. The system of claim 31, wherein the melting component is configured to transfer a message including a Short Message Service (SMS) message, an electronic mail (email) message, a device-specific electronic message, and a device-specific push message.

38. The system of claim 31, wherein at least one component of the system is configured to receive an electronic instruction to inactivate the device.

39. The system of claim 31, wherein at least one component of the system is configured to re-authenticate the client device, wherein the re-authenticating resynchronizes the client state information reinstated on the client device.

40. The system of claim 31, wherein at least one component of the system is configured to re-provision the client device, wherein the re-provisioning reinstates the client state information on the client device.

41. The system of claim 40, wherein the at least one component of the system is configured to re-provision the client device by:

receiving a re-provisioning message at the inbox of the client device;

automatically transferring an application to the client device in response to 30 selection of the re-provisioning message; and

automatically launching the application upon receipt at the client device, the launching including re-configuring the client device and re-synchronizing the client device.

42. The system of claim 41, wherein at least one component of the system is configured to transmit the re-provisioning message to the client device, wherein the transmitting includes pushing the message to the client device, wherein the reprovisioning message includes one or more of electronic provisioning information of the source device and user information of a user of the client device.

43. The system of claim 41, wherein the selection of the re-provisioning message includes user selection of a component of the message.

44. The system of claim 41, wherein at least one component of the system is configured to automatically transfer by downloading the application to the client device using a browser of the client device.

45. The system of claim 41, wherein the at least one component of the system is configured to configure by:

searching the inbox and locating the message;

parsing the message for one or more of electronic provisioning information and user information of a user of the client device.

46. A computer readable media including executable instructions which, when executed in a processing system on a client device, automatically melts client state information that comprises enterprise information at the client device by:

receiving a first data component from a facilitator wherein the first data component includes data representative of and identification of the facilitator as an authenticated source;

storing the first data component on the client device;

receiving, from the facilitator, a message at a common inbox of the client device, wherein the message includes a melt command, the first data component, and a second component, wherein the second component comprises data to enable identification of an application for parsing the message and to enable searching for the message in the common inbox;

identifying an application for parsing the message in the common inbox in accordance with the second data component;

parsing the message by the application identified in accordance with the second data component, determining from parsing the message that the message includes the melt command and acquiring the first data component from the message;

authenticating a source of the message by comparing the first data component obtained from the received message with the first data component stored on the client device; and

automatically deleting client state information of the client device including automatically deleting enterprise information in response to the melt command determining the message is from an authenticated source.