Provisioning in communications systems

• US 8,767,931 B2
• Filed: 08/23/2006
• Issued: 07/01/2014
• 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: Perfetto, Josh, Chatterjee, Saurav, Fullarton, Paul, Ling, Lorraine, Rana, Hemendra, White, Mike
• Primary Examiner(s): Nguyen, Khai N
• Application Number:
  US11/509,474
• Publication Number:
  US 20070042756A1
• Time in Patent Office: 2,869 Days
• Field of Search: 379/88.12, 379/93.17, 379/114, 379/211.01, 379/221.01, 379/230, 379/260, 379/433.02, 379/433.11, 379/100.08, 379/201.05, 379/201.01, 455/406, 455/569.1, 455/412.1, 455/412.2, 455/481, 455/419, 455/418, 709/206, 709/217, 715/749
• US Class Current: 379/201.01
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/02 using automatic reactions or user delegation, e.g. automatic replies or chatbot-generated messages
• CPC Class Codes: H04L 51/42 Mailbox-related aspects, e.g. synchronisation of mailboxes
• 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 1/72406 by software upgrading or downloading
• CPC Class Codes: H04M 1/7243 with interactive means for internal management of messages
• 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

Provisioning is described for use in communications systems. The provisioning includes receiving a message at an inbox of a device. The message includes information of an electronic location of a source device from which to download the appropriate application and device and user-specific information used for configuration of the application. An application is automatically transferred to the device in response to selection of the received message by a user of the device. The application is automatically installed on the device. The application is auto-started, at which time it self-configures using the original message.

Claims

1. A method comprising:

receiving a message at an inbox of a client device, the message comprising message content data, data corresponding to an identity of a message originator, and data corresponding to a location for obtaining an application and client device specific configuration information for the application;

automatically transferring the application from the location specified in the message to the client device in response to selection of the message;

automatically launching the application upon receipt at the client device, the launching of the application comprises searching the inbox of the client device for the message, parsing the message to obtain the client device specific configuration information from the message and self-configuring by the application using the client device specific configuration information from the message received at the inbox; and

generating an output corresponding to the message content data and the identity of the message originator on the client device in accordance with the launched application.

2. The method of claim 1, wherein the message is a push message.

3. The method of claim 2, wherein a provisioning server pushes the push message to the client device.

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

5. The method of claim 4, wherein the client device is a mobile device.

6. The method of claim 1, wherein the message includes at least 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.

7. The method of claim 1, wherein the message includes one or more of electronic provisioning information of the source device and user information of a user of the client device.

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

9. The method of claim 7, wherein the provisioning information includes 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.

10. The method of claim 7, wherein the message includes text.

11. The method of claim 1, wherein the source device 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.

12. The method of claim 1, comprising:

determining the client device fails to receive the message;

re-initiating the transferring in response to the determining.

13. The method of claim 1, wherein the selection of the message includes user selection of a component of the message.

14. The method of claim 13, wherein the component of the message includes a Uniform Resource Locator (URL) for a source of the message.

15. The method of claim 1, wherein automatically transferring comprises:

launching a browser of the client device; and

forming a coupling with the source device.

16. The method of claim 1, wherein automatically transferring comprises selecting the application from a plurality of applications.

17. The method of claim 16, wherein the selecting uses information from a user of the client device and identification information of the client device.

18. The method of claim 16, wherein a user of the client device performs the selecting.

19. The method of claim 16, wherein the source device performs the selecting using information of one or more of a service provider of the client device and one or more characteristic of the client device.

20. The method of claim 19, wherein the at least one characteristic includes one or more of operating system, model, screen size, connection type, memory, language, and language version of the client device.

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

22. The method of claim 1, wherein the launching further comprises parsing the message for one or more of electronic provisioning information of the source device and user information of a user of the client device.

23. The method of claim 22, wherein the provisioning information includes 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.

24. The method of claim 1, comprising receiving device information, the device information including one or more of a name of the client device, a model of the client device, a telephone number of the client device, a service provider of service of the client device, and electronic identification information of the client device.

25. The method of claim 24, wherein receiving comprises sending via at least one portal.

26. The method of claim 24, comprising transferring the message to the client device using the user information.

27. The method of claim 1, comprising generating an archive resource file that includes information of the client device.

28. The method of claim 27, wherein the information of the client device in the active resource file includes one or more of client devices supported, client device configurations, client device documentation, and client device applications.

29. The method of claim 27, comprising seeding the source device using information of the archive resource file.

30. The method of claim 29, wherein the source device is lacking information of the client device prior to the seeding.

31. The method of claim 27, comprising:

periodically updating the archive resource file to generate an updated archive resource file;

periodically re-seeding the source device with the updated archive resource file.

32. The method of claim 1, comprising transmitting a notification to the client device, the notification including information of an updated version of the application.

33. The method of claim 32, wherein the message includes the notification, and the application includes the updated application.

34. The method of claim 1, comprising synchronizing user data on the client device with user data on a source device.

35. The method of claim 1, wherein the searching for the message comprises searching for a message containing a predefined string.

36. A non-transitory, tangible computer readable media including executable instructions which, when executed in a processing system is operable to:

automatically provision a client device by receiving a message at an inbox of the client device, the message comprising message content data, data corresponding to an identity of a message originator and data corresponding to a location for obtaining an application and client device specific configuration information;

automatically transferring the application from the location specified in the message to the client device in response to selection of the message;

automatically launching the application upon receipt of the application at the client device, the launching comprises searching the inbox of the client device for the message, parsing the message to obtain client device specific configuration information, and self-configuring the application using at least a portion of the message received at the inbox of the client device, the portion of the message received including the client device specific configuration information; and

generating an output corresponding to the message content data and the identity of the message originator on the client device in accordance with the launched application.

37. A method comprising:

receiving a message at an inbox of a client device, the message comprising message content data, data corresponding to an identity of a message originator and data corresponding to a location for obtaining an application and client device specific configuration information for the application;

automatically transferring the application from the location specified in the message to the client device in response to selection of the message;

receiving an application directed push message, the application directed push message comprising an identification and configuration data;

matching the identification of the application directed push message with the application;

configuring the application with configuration data from the application directed push message responsive to matching the identification of the application directed push message with the application;

generating an output corresponding to the message content data and the identity of the message originator on the client device in accordance with the launched application.