WO2008109291A1 - Migration intelligente entre des dispositifs ayant une configuration matérielle ou logicielle différente - Google Patents

Migration intelligente entre des dispositifs ayant une configuration matérielle ou logicielle différente Download PDF

Info

Publication number
WO2008109291A1
WO2008109291A1 PCT/US2008/054984 US2008054984W WO2008109291A1 WO 2008109291 A1 WO2008109291 A1 WO 2008109291A1 US 2008054984 W US2008054984 W US 2008054984W WO 2008109291 A1 WO2008109291 A1 WO 2008109291A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
client device
user
client
server
Prior art date
Application number
PCT/US2008/054984
Other languages
English (en)
Inventor
Bharat Welingkar
Srikiran Prasad
William Eisner
Kevin T. Wu
Original Assignee
Palm, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US11/681,640 external-priority patent/US9037685B2/en
Application filed by Palm, Inc. filed Critical Palm, Inc.
Priority to EP08730733A priority Critical patent/EP2115577A1/fr
Publication of WO2008109291A1 publication Critical patent/WO2008109291A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0709—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0736—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function
    • G06F11/0742—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function in a data processing system embedded in a mobile device, e.g. mobile phones, handheld devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0793—Remedial or corrective actions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1469—Backup restoration techniques
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles

Definitions

  • a typical client-side computing device such as a mobile computing and communications device, relies on various disparate entities for the servicing and management of the client device.
  • a user of the client device may need a desktop computer to access a billing website provided by a service provider for the client device.
  • the user may have to access a website administered by an organization to which the client device is assigned.
  • the user may have to access a website associated with a manufacturer of the client device.
  • various interface points may have to be available to the user in order for the user to gain access to a full suite of services and management available for the client device.
  • certain services may be acquired via the client device.
  • Other services may have to be acquired using a desktop website.
  • other particular services may be available only via calls to a customer service representative.
  • certain updates for the client device may be obtained by accessing a website provided by a manufacturer of the client device.
  • a system for servicing a client device includes a web applications server arranged to provide a software download service.
  • the system further includes an account management server arranged to provide an account maintenance service.
  • the system also includes a synchronization server arranged to provide a data management service. Further, the services are available to the client device over a wireless communications network operatively connecting the client device to the web applications server, the account management server, and the synchronization server.
  • a method of providing a plurality of services to a client side computing device includes supporting a software download service on a server side. The method further includes supporting a centralized account maintenance service on the server side. The method also includes supporting a data management service on the server side. The method further includes providing said services in relation to each other to the client side computing device over a wireless communications network.
  • a system for servicing a client device includes a synchronization server that facilitates the user's migration from a first client device to a second client device.
  • the second client device may have hardware or software configuration different from the hardware or software configuration of the first client device.
  • the synchronization server detects the capability and compatibility of the second client server and converts the data sent from the first client device to a format that is compatible with the second client server.
  • a device includes an application program interface arranged to wirelessly communicate with a plurality of servers arranged to collectively provide a suite of services for the device.
  • the device further includes a first module arranged to request a software download via the application program interface.
  • the device also includes a second module arranged to provide account verification information via the application program interface.
  • the device further includes a third module arranged to backup data from and restore data to the device via the application program interface.
  • Figure 1 shows a high-level diagram of an over-the-air device services and management system in accordance with an embodiment of the present invention.
  • Figure 2 shows a component-level diagram of an over-the-air device services and management system in accordance with an embodiment of the present invention.
  • Figure 3 shows a module-level diagram of an account management server and a client-side computing device in accordance with an embodiment of the present invention.
  • Figure 4 shows a state transition diagram in accordance with an embodiment of the present invention.
  • Figure 5 shows a subsystem of an over-the-air device services and management system in accordance with an embodiment of the present invention.
  • Figure 6 shows a module-level diagram of a web applications server and a client- side computing device in accordance with an embodiment of the present invention.
  • Figure 7 shows a subsystem of an over-the-air device services and management system in accordance with an embodiment of the present invention.
  • Figure 8 shows a flow process in accordance with an embodiment of the present invention.
  • Figure 9 shows a subsystem of an over-the-air device services and management system in accordance with an embodiment of the present invention.
  • Figure 10 shows a flow process in accordance with an embodiment of the present invention.
  • Figure 11 shows a module-level diagram of a synchronization server and a client-side computing device in accordance with an embodiment of the present invention.
  • Figure 12a shows a flow process for de-duping in accordance with an embodiment of the present invention.
  • Figure 12b shows a flow process for migrating to a new client device in accordance with an embodiment of the present invention.
  • Figures 13-28 show various screenshots in accordance with one or more embodiments of the present invention.
  • embodiments disclosed herein relate to a system for providing services to and management of client-side computing devices.
  • an over-the-air services and management suite is provided for mobile computing devices, which include handheld computing devices.
  • handheld computing devices include cellular/mobile phones, personal digital assistants (PDAs), portable e-mail devices, and other computing devices having a form factor suitable for handheld use.
  • PDAs personal digital assistants
  • portable e-mail devices and other computing devices having a form factor suitable for handheld use.
  • client-side computing devices such as workstation, desktop, and laptop/notebook computers.
  • FIG. 1 shows an over-the-air device services and management system 100 in accordance with an embodiment of the present invention.
  • System 100 involves a client- side computing device 102a and and an auxiliary computing device 102b.
  • the client-side computing device 102a can be a stand-alone device such as a cellular/mobile phone, personal digital assistant, portable e-mail device, desktop computer, or a laptop/notebook computer.
  • the client- side computing device 102a may be any type of device that is capable of communicating with another device for services and/or data.
  • the auxiliary computing device 102b is an optional device that expands or supplements the capability or function of the client- side computing device 102b.
  • the auxiliary computing device 102b in one embodiment comprises a peripheral to a primary mobile computing device.
  • the primary mobile computing device may be a handheld computing device with mobile telephony capability such as a Palm Treo, a Nokia E61, a Motorola Q, or the like.
  • the auxiliary computing device 102b is configured to include a larger visual screen (e.g., 15 to 30 centimeters (cm) by 10 cm to 25 cm), a relatively full size keyboard (e.g., structured so that a user's fingers can type on in with fingers on keys at the "A-S-D-F" and "J-K-L-;” keys positions (or non-English equivalent thereof) ("language keyboard”)), a data processing subsystem, and a communication subsystem.
  • the data processing subsystem couples with the visual screen to display text, graphics, and/or images, the keyboard to display input received from the keyboard, and with the communication subsystem to process data received from the handheld computing device or for data to be sent to the handheld computing device.
  • the communication subsystem is configured to communicatively couple the handheld computing device.
  • a handheld computing device may be configured to send and receive electronic mail (email or e-mail).
  • the user may wish to transmit a lengthy reply.
  • Typing that reply on the handheld computing device may be impractical (e.g., small language keyboard) or not feasible (e.g., lacking a full size language keyboard).
  • the handheld computing device communicatively couples (e.g., a Bluetooth or infrared connection) the communication subsystem of the auxiliary computing device 102b to transmit the email to the auxiliary computing device 102b.
  • the user prepares the reply e-mail using the full language keyboard and display of the auxiliary computing device 102b.
  • the reply email is transmitted back to the handheld computing device which then transmits the email to the respondent through its email communication configuration (e.g., its GPRS configuration).
  • auxiliary computing device 102b can be created in the auxiliary computing device 102b and transmitted to the handheld computing device for further processing and/or communication.
  • a media file can be received through the handheld computing device and forwarded to the auxiliary computing device 102b for playback on its larger screen.
  • the auxiliary computing device 102b is particularly configured to serve as a peripheral of the handheld computing device.
  • the auxiliary computing device 102b does not require full featured Microsoft Windows or Apple Mac OS type operating system.
  • it require a high performance processing system, input/output system, or storage system typically found in conventional laptop computing devices.
  • the auxiliary computing device 102b is configured to use a more streamlined operating system that allows for "instant on” (e.g., it is immediately available for input right after it is powered on; for example, the primary software components need not be reloaded from longer term storage each time it is powered on, but rather from other non- volatile storage such as flash memory).
  • auxiliary computing device 102b data processing subsystem and communication subsystem are specifically configured (and optimized) for performing tasks common to handheld computing devices, for example, e-mail communication, messaging communication, document creation and transmission, navigation services, as well as video, music, and game download, playback, and uploads (particularly in smaller application formats, e.g., applets or widgets).
  • auxiliary computing device 102b are found in commonly owned U.S. Patent Application Serial Numbers 10/815,406 titled "Peripheral Device for a Wireless Communication Device” and 11/105,197 titled “System and Method for Enabling a Person to Switch Use of Computing Devices", the contents of each of which is herein incorporated by reference.
  • the client-side computing device 102a and the auxiliary computing device 102b are hereinafter collectively referred to as the client device 102.
  • one or more functions of the client device 102 may be implemented on the auxiliary client-side device 102b.
  • a server side of system 100 includes a web applications server 104, an account management server 106, and a synchronization server 108. Each of these servers 104, 106, 108 is further described below with reference to Figures 2 - 28.
  • the servers 104, 106, 108 may be configured for implementation in hardware and/or software.
  • the web applications server 104 may be associated with a physical computer system dedicated for providing services of the web applications server 104.
  • the web applications server 104 may be associated with software resident on a particular computer system that is not just dedicated for providing services of the web applications server 104.
  • the web applications server 104, the account management server 106, and the synchronization server 108 are shown as being separate in Figure 1, functionality of any one or more of the servers 104, 106, 108 may be combined with that of another of the servers 104, 106, 108. Moreover, a location of any one or more of the servers 104, 106, 108 may be the same as that of another of the servers 104, 106, 108. For example, the account management server 106 and the synchronization server 108 may be hosted on the same machine.
  • the servers 104, 106, 108 may be remotely located from one another. In some such cases, the servers 104, 106, 108 may communicate with one another over a local area network (LAN). For example, if the servers 104, 106, 108 are resident within or part of a particular organization, the servers 104, 106, 108 may communicate over an enterprise network and/or via point-to-point interconnect. Further, in one or more other embodiments, the servers 104, 106, 108 may communicate with one another over a wide area network (WAN). For example, the servers 104, 106, 108 may communicate with one another over the Internet using hypertext transport protocol (HTTP) requests and responses. More specifically, for example, the servers 104, 106, 108 may communicate with one another using extensible markup language (XML) based messages.
  • LAN local area network
  • HTTP hypertext transport protocol
  • HTML extensible markup language
  • each of the servers 104, 106, 108 may be designed, maintained, managed, and/or delivered by one or more of various entities.
  • the synchronization server 108 may be managed by the manufacturer of the client device 102.
  • the web applications server 104 and/or the account management server 108 may be designed and/or delivered in contract with a manufacturer of the client device 102.
  • one or more of the servers 104, 106, 108 may be designed and/or managed by a service provider arranged to provide voice and/or data services to a user of the client device 102.
  • one or more of the servers 104, 106, 108 may be managed by and/or designed for an organization to which a plurality of client devices 102 belongs or is otherwise associated with.
  • FIG. 2 shows a component-level diagram of system 100.
  • the client device 102 communicates with the web applications server 104, the account management server 106, and the synchronization server 108 over a network 202.
  • the network 202 is any medium over which the client device 102 can wirelessly communicate with one or more of the web applications server 104, the account management server 106, and the synchronization server 108.
  • the client device 102 is capable of wirelessly communicating with the network 202 to which any one or more of the web applications server 104, the account management server 106, and the synchronization server 108 are operatively connected.
  • system 100 may be described as an "over-the- air” system - the services and management features of servers 104, 106, 108 are provided wirelessly to the client device 102, where the client device 102 represents a central interface point through which a user of the client device 102 can access such services and management features (as opposed to the user having to access a system other than the client device 102).
  • system 100 may be a "push” network, a “pull” network, or a combination thereof.
  • a "push” network one or more of the servers 104, 106, 108 push out data to the client device 102.
  • a "pull” network one or more of the servers 104, 106, 108 send data to the client device 102 upon request for the data by the client device 102.
  • the network 202 may be at least in part a cellular network. In another example, the network 202 may be at least in part a wireless data network. Moreover, in still another example, the network 202 may be at least in part a radio network. In yet another example, the network 202 may be at least in part a wireless fidelity ("Wi-Fi") network. Further, in one or more embodiments, the network 202 may be at least in part an Internet-based network. Still further, information transferred between the client device 102 and any one or more of the web applications server 104, the account management server 106, and the synchronization server 108 may be encrypted using industry-standard data encryption techniques (e.g., 128-bit SSL). Moreover, user-specific data stored in any one or more of the web applications server 104, the account management server 106, and the synchronization server 108 may be encrypted using industry-standard data encryption techniques.
  • industry-standard data encryption techniques e.g., 128-bit SSL
  • the web applications server 104 includes at least in part a resource management component 204 and a "kill pill & lock" component 206.
  • the resource management component 204 may be used to centrally manage resources (e.g., data types) used by applications 218 resident on the client device 102.
  • the kill pill & lock component 206 may be used to wipe and/or lock data resident on the client device 102.
  • the account management server 106 includes at least in part a "heartbeat engine” component 212 and a state engine component 214.
  • the state engine component 214 may be used to maintain state information and track state changes of the client device 102.
  • the heartbeat engine component 212 may be used to control an update protocol followed by the client device 102.
  • the synchronization server 108 includes at least in part a backup/restore/migration component 208.
  • the backup/restore/migration component 208 may be used to backup data from and restore data to the client device 102.
  • the client device 102 includes system utilities 216, applications 218, and a data de-duping component 210. Use and operation of system utilities 216 and applications 218 will apparent from the description herein.
  • the data de-duping component 210 as further described below with reference to Figure 12a, may be used to detect and/or remove redundant data type instances.
  • the web applications server 104, the account management server 106, and the synchronization server 108 will now be described in further detail. Specifically, the description below with reference to Figures 3 - 5 relates to the account management server 106, the description below with reference to Figures 6 - 10 relates to the web applications server 104, and the description below with reference to Figures 11 and 12 relates to the synchronization server 108. It is noted that although the various functionalities are described below in association with one of the servers 104, 106, 108, such description is primarily for purposes of clarity, and as such, does not limit the ways different described functionalities may be mapped to one or more of the servers 104, 106, 108.
  • account management server 106 the web applications server 104, the synchronization server 108, and the client device 102 are described with reference to Figures 3, 6, and 11 as having modules, where a "module” is any program, logic, and/or functionality implemented in hardware and/or software.
  • ACCOUNT MANAGEMENT SERVER is any program, logic, and/or functionality implemented in hardware and/or software.
  • FIG. 3 shows a diagram of the account management server 106 and the client device 102 in accordance with an embodiment of the present invention.
  • the account management server 106 serves as a central account management point to which one or more vendors, service providers, device manufacturers, and the like may connect with to interface with an account associated with the client device 102.
  • the account management server 106 includes an HTTP transport component 314 and a short message service (SMS) transport component 316.
  • the client device 102 similarly includes an HTTP transport component 318 and a SMS transport component 320.
  • the HTTP transport components 314, 318 may be used for HTTP/S communications. Further, in one or more embodiments, the HTTP transport components 314, 318 may be used to support a simple object access protocol (SOAP), which can be used to exchange XML based messages.
  • SOAP simple object access protocol
  • the SMS transport components 316, 320 may be used to support SMS message communications. It is noted that SMS messages may be communicated in the form of what are referred to as "text" messages.
  • the client device 102 is shown as having a plurality of libraries.
  • a "library” may be defined as a collection of subroutines and functions stored in one or more files, usually in a compiled form, for linking with other programs.
  • the client device 102 includes an account management library 322 that may be used to interface resources and functionality with those provided by the account management server 106.
  • the client device 102 includes a synchronization library 324 that may be used to interface resources and functionality with those provided by the synchronization server 108 (further described below with reference to Figures 11 and 12).
  • the client device 102 also includes a registration library 326, an authentication library 328, a text library 330, a log library 332, a scheduling library 334, and a heartbeat library 336.
  • the use and role of the libraries 326, 328, 330, 332, 334, 336 will be clear from the description below with reference to Figures 3 - 28. Further, one or more of the libraries 326, 328, 330, 332, 334, 336 may be reusable in the sense that they may be used in connection with functionalities of the web application server 104, the account management server 106, the synchronization server 108, or any combination thereof.
  • the account management server 106 facilitates the creation/registration of and login to an account maintained for the client device 102.
  • a user has had to call a customer service representative, go through a live setup process with a representative at a retailer or service provider of the client device, or access the Internet to go through a setup process available via a website of a retailer, manufacturer, or service provider.
  • the user of the client device 102 may set up an account for his/her client device 102 completely (or almost completely) through use of the client device 102 as described below.
  • the account management server 106 and the client device 102 may be used, in one aspect, once a user of the client device 102 registers with the account management server 106 (e.g., an account for that user is created), that user may not have to create another user account again despite replacement of the client device 102, change in platform of the client device 102, and/or loss or corruption of data in the client device 102. Thus, such centralized account management may be thought of as a service provided by system 100.
  • the client software may be launched, whereby the user of the client device 102 is presented with the option to register for a new account or login to an existing account (see, e.g., Figure 13). If the user chooses to register for a new account, the user is prompted to enter account registration information. Such information may include, for example, name, home and/or work address, home and/or work phone number, social security number, driver's license or identification card number, username, password, and alternate e-mail address (e.g., e-mail address other than one associated with the client device 102).
  • account registration information may include, for example, name, home and/or work address, home and/or work phone number, social security number, driver's license or identification card number, username, password, and alternate e-mail address (e.g., e-mail address other than one associated with the client device 102).
  • the user may also be prompted to specify challenge questions and answers to be used for recovery of a forgotten username and/or password (see, e.g., Figure 14).
  • the registration information is then wirelessly submitted over the network 202 (shown in Figure 2) to the account management server 106. If the account is successfully created, the user may be notified accordingly; otherwise, if the account is not successfully created, the user may be presented with error information possibly containing instructions for reentry of part or all of the registration information. [0055] If the user has an existing account, he/she may indicate so and is then prompted for his/her e-mail address and password.
  • the e-mail address, password, and a phone number of the client device 102 are then communicated over the network 202 (shown in Figure 2) to the account management server 106.
  • the user may be prompted to perform a data backup or restore (see, e.g., Figure 15).
  • the data backup service allows the user to wirelessly backup the data on his/her client device 102 to a server side data store (not shown).
  • the data restore service allows the user to wirelessly restore data onto his/her client device 102 from a server side data store (not shown).
  • the new phone number in the case that a phone number of the client device 102 has been changed by the user (or an administrator), when the user chooses to login to his/her existing account, the new phone number, along with the e-mail address and password entered by the user, is wirelessly communicated to the account management server 106.
  • the account management server 106 detects the new phone number associated with the previously known e-mail address and password of the user and updates the user's account to reflect the new phone number. The user may then be prompted with data backup and/or restore service options as described above.
  • the user accordingly indicates so using client software.
  • This indication along with the user's e-mail address (see, e.g., Figure 16), are sent to the account management server 106, which in turn retrieves the challenge questions specified by the user during account registration and wirelessly communicates them over to the client device 102 for response by the user (see, e.g., Figure 17).
  • the account management server 106 may then prompt the user to enter a new password (see, e.g., Figure 18).
  • the account management server 106 updates the user's account to reflect the new password.
  • the account management server 106 may notify the user that his/her password must be reset by e- mail (see, e.g., Figure 19).
  • the password reset module 304 sends the user a hyperlink to the user's e-mail address.
  • the user then from either the client device 102 or another computer system (e.g., desktop or laptop/notebook computer) may click on the hyperlink, which effectively navigates the user through a password reset process for creating a new password.
  • the new password is then communicated to the password reset module 304, which in turn resets the user's account password accordingly.
  • the above description with respect to how a user of the client device 102 may register or login to an account on the account management server 106 represents use cases.
  • One of the client-side software applications 338 that facilitates and supports these use cases may have certain attributes, requirements, and features as described below.
  • the client software application When this client software application is launched, the client may first make sure that the client device 102 is a supported device. In other words, the client may check the client device 102 against a list of devices indicated as being supported by system 100. If the client device 102 is not supported, the user may be directed to an informational website (hosted by, for example, the web applications server 104) for further instructions.
  • an end-user license agreement may be displayed to the user.
  • the client software application ensures that the user can fully scroll through and read the end-user license agreement. Further, the user may be provided with an option to accept or decline the end-user license agreement. Still further, the end- user license agreement may inform the user of billing arrangements and other fees for use of one or more of the services provided in system 100.
  • the client software application will exit, thereby precluding the user from accessing particular services offered in system 100.
  • the client software application may re-display the end-user license agreement and prevent the user from accessing particular services until the user accepts the terms of the end-user license agreement.
  • the client software application may proceed to one or more of the login/register steps described above. It is noted that should the end-user license agreement be accepted, the end-user license agreement may not be displayed on subsequent launches; however, the user may still have the option of viewing the end-user license agreement at any time.
  • the client software application When the client software application is run on the client device 102, and the user chooses to register a new account, the client provides a registration interface. In the meantime, the client may verify if an account with the phone number of the client device 102 (noting that this phone number is likely a unique identifier for the account) already exists on the account management server 106.
  • the client may prompt the user to confirm whether the user wants to login instead of register. If the user selects to login, then the client presents a login interface; otherwise, if the user selects to register a new account, the client presents an account registration interface.
  • a unique identifier other than the client device's 102 may be used.
  • the unique identifier may be the client device's 102 serial number or media access control (MAC) address.
  • the client may indicate that server registration was successful and may provide the user with an option to configure and/or initiate a data backup.
  • the client may query the account management server 106 to determine whether the user has existing data backed up that can be restored to the client device 102. If the user has valid existing backup data, the client may ask the user if he/she wishes to initiate a data restore.
  • the user may be informed that data cannot be migrated and that the user needs to "start clean" on the client device 102 for backups if the user wishes to continue with login. If the user does not have any existing backup data, the client may require the user to backup his/her data, just as if the user were a newly-registered user.
  • OS operating system
  • the client should allow a new user to register with system 100, and more particularly, with the account management server 106.
  • the user may be asked for an e-mail address.
  • the client and/or the account management server 106 may validate that the e-mail address is a standard-formatted e-mail address - at a minimum, the client may check for the presence of an "@" sign, and the account management server 106 may perform a more complete validation. Further, the account management server 106 may validate the registered e-mail address as being unique in system 100. Still further, the client may inform the user that a validation e-mail will be sent to the provided e-mail address so as to encourage the user to enter a valid e-mail address.
  • the user may be asked for a password.
  • a format of the password may be required to have minimum and/or maximum numbers of characters.
  • the user may be asked to enter his/her password to ensure proper entry of the password.
  • the client may also require that the password contain both letters and numbers.
  • the user may be asked for the name of the country in which the user plans to use the client device 102. This may be supported by a drop-down list of country names.
  • the user may be asked whether he/she would like to receive marketing, advertising, and/or promotional messages.
  • the default option may be to opt-out of receiving such messages.
  • challenge questions may be selected from among the following: name of first school; name of first pet; name of street on which you grew up on; city of father's birth; city of mother's birth; grandmother's first name; make/model; and/or name of first employer.
  • the client may wirelessly communicate the registration information to the account management server 106.
  • registration information may be wirelessly communicated as the registration information is entered. If the client is unable to wirelessly communicate the registration information to the account management server 106 due to communication or server availability issues, the client may present a message to the user asking the user to try registration again at a later time. In such cases, the user may be informed that entered values have been saved and that the user can try again by, for example, clicking on a "retry" button.
  • the client device 102 may additionally send, for example, the following data to the account management server 106: mobile number; carrier; an International Mobile Equipment Identity (IMEI) and/or Electronic Serial Number (ESN); firmware version; software version; hardware version; synchronization identification number ("SyncID”); carrier DB; device serial number; and/or device model.
  • IMEI International Mobile Equipment Identity
  • ESN Electronic Serial Number
  • firmware version firmware version
  • software version software version
  • hardware version synchronization identification number
  • carrier DB device serial number
  • device serial number and/or device model.
  • the client may prompt the user to enter an e-mail and password. After a certain number of failed attempts, the user may be directed to challenge questions. Further, in one or more embodiments, the user may be provided with the option to go directly to challenge questions at any time that user is prompted for login credentials. If login fails, the user may be informed of authentication failure and may be allowed to try again.
  • the e-mail and password entered by the user are sent to the account management server 106 for account validation. If the e-mail is found on the account management server 106, the account management server 106 may attempt to use the e-mail and password for account validation. If the e-mail is found on the account management server 106 and account validation is unsuccessful based on the password entered by the user, the client may allow the user to re-enter the password and may additionally provide a password reset option.
  • the phone number of the client device 102 may be verified against the account's registered phone number. If the phone number taken from the client device 102 is not the same as the account's registered phone number, the account management server 106 may update the account with this new phone number. If the client is unable to retrieve the phone number from the client device 102, the client may initiate a short message service (SMS) to the account management server 106 and verify against the account's registered phone number.
  • SMS short message service
  • system 100 may attempt to transfer the phone number to the new user using an SMS confirmation method.
  • the client may direct the user for a password reset via challenge questions.
  • the account management server 106 may identify the user by phone number or e-mail in order to accurately determine corresponding challenge questions and answers.
  • the user may be able to initiate a password reset by answering, for example, at least two challenge questions the user selected and answering during registration as described above.
  • the account management server 106 may restrict the number of challenge question reset attempts that are allowed for a particular user account.
  • the account management server 106 updates the user's account password accordingly.
  • an e-mail may be sent to user's e-mail address of record with instructions on how to perform a web- based password reset.
  • the sent e-mail may contain a hyperlink that points to a password reset website.
  • the hyperlink may contain a token that confirms the identity of the user requesting the password reset. In one or more embodiments, this token may only be valid for a limited duration and may be only valid for one password reset use.
  • the password reset website may be supported by both mobile and desktop web browsers. If the user is validated via passed-in token, the password reset website may then prompt user to enter and confirm a new password.
  • the password reset website may allow the user to reset password and challenge questions as a combined function. Further, the password reset website may confirm to the user that password has been reset if the password reset is successful. If the password reset website is accessed from the client device 102, after the password reset is complete, the client may auto-launch to the login screen. On the other hand, if the password reset website is accessed from a desktop or notebook/laptop computer, after the password reset is complete, the user may be directed to re-login on the client device 102 using the new password. After any password reset or change, the account management server 106 may send an e-mail to user's email address informing the user that password was updated and directing the user to contact customer support if the user did not intend for the password to be changed. Also, after any password reset or change, the account management server 106 may expire all password reset tokens previously issued for the client device 102.
  • the client may resend device information.
  • the account management server 106 may then log this information. If the user's phone number has changed, the account management server 106 may notify the user that their account phone number will be changed and may give user the option to cancel login.
  • the client may store in an authentication library 328 a token that can be used to authenticate the user in future transactions with the account management server 106.
  • a token may not include any identifiable user data. Further, such a token may not be transferable to another device. Still further, the account management server 106 may be able to expire the token and force the user to re-login. Still further, previously existing tokens may be deleted after a successful login or registration occurs.
  • the client may detect if a phone number of the client device 102 changes during on-going usage. If the phone number of the client device 102 changes, the client may expire a previous login token and consequently require the user to re-login.
  • the client may provide the user with the ability to update user data (e.g., name, e-mail, password). If the user changes his/her e-mail address, the user may be required to reconfirm the new e-mail address. Further, the user may not be allowed to change an e-mail address to an e-mail address that is already associated with an active account.
  • user data e.g., name, e-mail, password
  • the account management server 106 includes an account deletion module 308 that provides for account deletion.
  • Account deletion may occur by sending an operator- or administrator-initiated e-mail to the user's email address of record and having the user click a link in the e-mail.
  • the account management server 106 may send a confirmation e-mail to the user informing the user that his/her account has been deleted.
  • the account management server 106 also includes an account state model 302.
  • the account state model 302 corresponds to the state engine 214 shown in Figure 2.
  • the account management server 106 may associate an account state with each of a plurality of accounts registered on the account management server 106.
  • a "State 0" may be referred to as an "inactive pending phone # verification" state.
  • the new account may be placed into State 0.
  • the account management server 106 may allow the client to authenticate with an account that is in State 0, but no other functionality may be allowed until phone number verification occurs.
  • an account in State 0 may change to state A (further described below). If a phone # verification process has not been successfully completed within a predetermined period of time (e.g., 7 days), an account in State 0 may change to State D (further described below).
  • a "State A” may be referred to as an "active pending verification" state.
  • a newly registered account may be in State A if its registered phone number is not already in another account (i.e., not in State 0).
  • the account management server 106 may allow the client to authenticate with an account that is in State A, but certain functionality may not be allowed. For example, an account in State A may be able to perform a data backup, but it may not be able to perform data restore and kill pill & lock functionalities (further described below). After successful phone # and e-mail verification, an account in State A may change to State B (further described below).
  • an account in State A may change to State D (further described below). Further, if the user contacts an operator, administrator, or customer service agent to delete their account, an account in State A may change to State E (further described below) using the account deletion module 308 described above.
  • a "State B" may be referred to as an "active" state.
  • an account in State B has successfully completed phone # and e-mail verification processes.
  • the account management server 106 may allow the client to authenticate with an account that is in State B. Further, the account management server 106 may allow the client to perform data backup and restore and kill pill & lock functionalities (further described below) if the account is in State B.
  • An account in State B may change to State C (further described below) when an associated phone number or e-mail address is changed (e.g., an account was transferred to a new number, user changed e-mail address on the account). If the user contacts the operator, administrator, or customer service agent to delete their account, an account in State B may change to State E (further described below) using the account deletion module 308 described above.
  • a "State C" may be referred to as an "active pending re-verification" state.
  • an account in State C may only come from State B as shown in Figure 4.
  • the account management server 106 may allow the client to authenticate with an account that is in State C.
  • the account management server 106 may allow the client to perform data backup and restore and kill pill & lock functionalities (further described below) if the account is in State C. After successful phone # and e-mail verification, an account in State C may change to State B.
  • an account in State C may change to State D (further described below). If the user contacts the operator, administrator, or customer service agent to delete their account, an account in State C may change to State E (further described below) using the account deletion module 308 described above.
  • a "State D" may be referred to as a "locked" state.
  • An account that has not completed phone # and e-mail verification process within a predetermined period of time may change to State D.
  • the account management server 106 may allow the client to authenticate with an account that is in State D, but certain functionality may not be allowed. For example, an account in State D may not be able to perform data backup and restore and kill pill & lock functionalities (further described below). Further, after the user initiates and successfully completes phone # and e-mail verification, an account in State D may change to State B.
  • a "State E" may be referred to as a "disabled/deleted” state.
  • the account management server 106 may change an account to State E if the user has requested to delete their account using the account deletion module 308 described above. Further, the account management server 106 may not allow the client to authenticate with an account that is in State E. Moreover, an account in State E may not be able to perform data backup and restore and kill pill & lock functionalities (further described below). Additionally, the account management server 106 may remove user registration information and backup data from an account in State E. In one or more embodiments, such backed up data may be fully unrecoverable.
  • the account management server 106 may change an account to State 0 when the user transfers their phone number and that phone number exists in another account. Further, the account management server 106 may change an account in the following manner if the user transfers their phone number and that phone number is not in another account: States 0 and A change to State A; State B changes to State C; State C remains in State C; and State D remains in State D.
  • the account management server 106 may verify that a newly-submitted e-mail address and/or phone number (noting that a phone number is taken directly from the client device 102, not entered by the user) is unique across system 100. If the user is attempting to register an account using an e-mail address that has been verified before, the user may be informed that the e-mail address is already being used and may be presented with password reset options (the assumption being that the user should be logging in, not registering).
  • the account management server 106 may allow the user to register and then may mark the account as State 0 until the phone number is confirmed. If the phone number is confirmed via, for example, an SMS message, the phone number may be removed from an old account and the account may be placed in State 0. The client may allow the user to "recover" their account by initiating an SMS verification process as described below. An e-mail may be sent to the old account notifying the user that the phone number has been transferred to a new account. If the phone number cannot be confirmed via an SMS message, the account may be disabled.
  • the client may send a confirmation SMS message to the account management server 106 to verify its phone number.
  • the SMS message may contain account identification and authentication information sufficient for the account management server 106 to perform one or more necessary security checks. If the account management server 106 does not receive the SMS confirmation, the account management server 106 may notify the client to prompt the user to re-send the SMS message periodically until the SMS confirmation message is received.
  • the account management server 106 may change the account status to State D. If the user's account is disabled because the phone number cannot be confirmed, the user may be directed by the client to a support website. More particularly, for example, the client may notify the user via an alert that their account has been de-activated and may direct the user to a support website.
  • the account management server 106 may validate that e-mail address.
  • the account management server 106 may send an e-mail message to the new e-mail address requesting the user to confirm the address.
  • the e-mail message may include a hyperlink with a token that the user can select to link to an e-mail confirmation website.
  • the e-mail confirmation website may be supported by both desktop and mobile web browsers. If a predetermined amount of time elapses and the user has not yet confirmed the e-mail address, the client may notify the user via an alert that the e-mail address has not been verified.
  • the client may give the user option to re-enter the e-mail address at this point. Further, the client may provide the user an option to have a confirmation e-mail resent. Moreover, the client may advise the user to check spam folders and filters if the e-mail is still not received.
  • the account management server 106 may change user's account to State D. In this case, the client may notify the user that the client is disabled until the e-mail address is verified. Further, the client may give the user option to re-enter the e-mail address at this point. Further still, the client may provide the user an option to have a confirmation e-mail resent. Moreover, the client may advise the user to check spam folders and filters if the e-mail is still not received. If the user is able to complete a password reset via e-mail as described above before accessing the e-mail verification link, the account management server 106 may mark the e-mail verification process as completed.
  • the account management server 106 includes a heartbeat manager module 312.
  • the heartbeat manager module 312 corresponds to the heartbeat engine 212 shown in Figure 2.
  • Figure 5 more particularly shows a subsystem associated with the heartbeat manager module 312.
  • a client side component sends out what is referred to as a "ping" or “heartbeat” to a server to let the server know that the client side component is alive and functioning.
  • ping or “heartbeat”
  • Such conventional pings are sent out periodically and regularly by the client side component.
  • the client device 102 sends out pings at a frequency and/or format specified and dynamically changeable by the account management server 106.
  • the client device 102 has an updater module 340 that is used to retrieve and receive updates from the account management server 106.
  • updates may be, for example, operating system updates, security updates, service updates, application updates, data updates, library updates, driver updates, and/or communication protocol updates.
  • the updater module 340 checks for updates via the use of what are referred to as "pings" or "heartbeats" as described above.
  • heartbeats may be particularly formatted or they may be simply structured HTTP requests.
  • the heartbeats may be communicated via SMS messages.
  • the heartbeats may be communicated via one or more available data and/or voice channels.
  • an application of the client device 102 may attempt to check for updates from the account management server 106 on some regular or periodic basis (e.g., daily) to see if one or more updates are available and to register a "heartbeat" with the account management server 106.
  • the client device 102 may have a library (not shown) that manages the schedule for a heartbeat process.
  • the client may provide identity information to the account management server 106.
  • the heartbeat may include information regarding a version of software being used by the client device 102, a last attempted data backup time, an e-mail verification status, an SMS verification status, account state information, an account identity token, and/or a next scheduled heartbeat.
  • the account management server 106 is operatively connected to or has resident within it a delay times data store 502.
  • the delay times data store 502 includes a collection of configurable and/or default delay times. These delay times, configurable via a delay configuration module 504, are used by the heartbeat manager module 312 to indicate to the client device 102 how and when the client device 102 should send future pings.
  • the response from the heartbeat manager module 312 may include information in its response as to how long the client device 102 should wait before attempting a next ping. If the client is unable to perform a heartbeat at a requested time for some reason, the client may cancel that heartbeat and retry that heartbeat again on some predetermined basis (e.g., daily). Accordingly, by controlling a ping frequency, the account management server 106 may, for example, slow down pings from the client device 102 if the account management server 106 is experiencing high traffic load (e.g., an increased internal or external demand for computing resources).
  • high traffic load e.g.
  • the response from the heartbeat manager module 312 may include information in its response as to how a next ping from the client device 102 should be sent.
  • the heartbeat manager module 312 may indicate to the client device 102 that a next ping should occur via an SMS message rather than by an HTTP request.
  • the heartbeat manager module 312 may indicate to the client device 102 that a next ping should be sent via a particular voice channel instead of by an HTTP request.
  • heartbeats can be sent from the client device 102 on an alternative network (e.g., a Wi-Fi network) even if an initially selected network (e.g., a mobile phone network) is not available.
  • a server side component controls a heartbeat of a client side component (here, the client device 102). Further, by managing the heartbeats of the client device 102 and knowing when to expect heartbeats from the client device 102, the account management server 106 may be used to track whether the client device 102 is functioning and "alive" (e.g., operational and/or active).
  • the delay time specified in a response to the client device 102 may vary according to carrier, group, device, and/or platform. For example, a delay time in a response to a client device 102 that is part of a first group may be longer than a delay time specified in a response to another client device (not shown) that is part of another group. As described above, delay times may be stored in the delay times data store 502. One or more of these delay times may have default values, and further, one or more of these delay times may be dynamically adjusted based on need and/or performance objectives.
  • a response from the heartbeat manager module 312 may indicate to the client device 102 an event trigger that should cause the client device 102 to send out a heartbeat.
  • the heartbeat manager module 312 may indicate that when the client device 102 sends an outgoing e-mail, the client device 102 at that time should also send a heartbeat to the account management server 106.
  • the heartbeat manager module 312 may indicate that the client device 102 should send out a heartbeat whenever an SMS message is sent from the client device 102.
  • the client may notify the user via an alert that leads the user to an application dialog. Further, in one or more embodiments, if an update is detected, the client may disallow attempts to perform additional server activities until the update is installed. Moreover, if an update is available, the client may ask the user if he/she wishes to download and install the update immediately or be reminded to download the update at a later time. If the user chooses to download and install the update immediately, the client may download and install the update in the background (e.g., the user may still use a phone functionality of the client device 102 without being interrupted).
  • the client may re-prompt the user at that time. Further, for example, after providing a particular number of reminders, the client may inform the user that the user will not be reminded again and that the user will need to download and install the update manually. Moreover, in one or more embodiments, the client may provide a preference setting to allow future updates to be downloaded without prompting the user.
  • FIG. 6 shows a diagram of the web applications server 104 and the client device 102 in accordance with an embodiment of the present invention.
  • the web applications server 104 may host a desktop website 602 and/or a mobile website 604 for providing information regarding a product, service, and management suite offered by system 100 to a user of the client device 102.
  • an entity such as a service provider, device manufacturer, and/or retailer, may rely on the desktop website 602 and/or the mobile website 604 to publicly convey information regarding products and/or services offered by system 100.
  • the web applications server 106 also includes an HTTP/S transport component 614 and an SMS transport component 616 for respectively interfacing with the HTTP/S transport component 318 and the SMS transport component 320 resident on the client device 102.
  • These transport components 614, 616, 318, 320 may support, for example, any one or more of the various communications supported between the client device 102 and the account management server 106.
  • the client device 102 may access one of the desktop website 602 and/or the mobile website 604.
  • the user enters their mobile phone number and carrier and requests the client software (see, e.g., Figure 20).
  • the user receives an SMS message on the client device 102, where the SMS message may include a web link to a mobile download page (see, e.g., Figure 21), possibly supported by a client download module 606 resident on the web applications server 104.
  • the user may then click on the web link and the user's mobile browser is launched.
  • the user may then be taken to a mobile download site that detects the client device's 102 operating system and begins the download of the appropriate client installer (see, e.g., Figures 22 and 23).
  • the client installer runs on the client device 102 upon download (see, e.g., Figure 24). Then, the client is initiated after installation and registration/login as described above begins.
  • the client may be installed via a storage device having stored therein client software available for installation.
  • the storage device may be a secure digital (SD) card.
  • the user may be provided with a secure digital card that contains a client installer for an operating system of the client device 102. The user then inserts the secure digital card into the client device 102, and the client device 102 in turn performs the appropriate installation.
  • the client launches and the user may be prompted to perform registration/login as described above.
  • the client may be downloaded and installed via a mobile website.
  • the user may open a web browser on the client device 102. The user may then navigate to the appropriate website for downloading the client. The user may then choose to begin the download of the client.
  • the mobile download page may detect the operating system of the client device 102 and deliver the appropriate client installer. The client installer may then run on the client device 102 after download. The client is then accordingly installed and registration/login as described above begins.
  • the web applications server 104 may convey product and/or service information regarding system 100. Further, the web applications server 104 may facilitate distribution of a client installer via an SMS message. Further still, the web applications server 104 may provide an interface for the user to submit the user's mobile phone number and carrier. Still further, the web applications server 104 may include a mechanism to prevent malicious users from sending repeated SMS messages. [0112] As described above, once the user has entered a mobile phone number and carrier, the web applications server 104 may send an SMS message to the client device 102, where the SMS message includes a link to a mobile landing site. In one or more embodiments, the web applications server 104 may utilize an SMS aggregator (not shown) to send SMS messages. After an SMS message is sent, the web applications server 104 may provide the user with information about the next steps the user will be taking - receiving the SMS and performing the client installation process.
  • SMS aggregator not shown
  • the mobile website 604 may be able to determine an operating system of the client device 102.
  • the mobile website 604 may provide direct download of the appropriate client installer for the client device 102 via a mobile download site. Further, the mobile website 604 may provide a mobile download site to deliver a mobile download and to serve as the destination for SMS links sent to users from the desktop website 602. Moreover, in one or more embodiments, the mobile download site may automatically begin download of an appropriate installer to the client device 102. In such cases, the mobile download site may detect the operating system of the client device 102.
  • the client application and related component files may be delivered in the form of a self-extracting client installer that can be executed on the client device 102. More particularly, in one or more embodiments, the client installer may check for sufficient memory on the client device 102 before performing installation. Further, the client installer may check to make sure the client device 102 is a supported device type. Still further, the client installer may detect which components are already on the client device 102 and may not overwrite any user information or pre-existing client components unless particular components are being upgraded. Moreover, as described above, the client installer may be able to run, for example, from either the client device 102 or from a storage device (e.g., a secure digital card). Additionally, the client installer may auto-delete itself from the client device 102 (but not from the storage device) after successful installation.
  • a storage device e.g., a secure digital card
  • the web applications server 104 includes a resource manager module 608.
  • Figure 7 shows a subsystem associated with the resource manager module 608.
  • resource management facilitates one or more services by which data resources referenced by software applications resident on client devices served by system 100 may be updated at the server level and broadcasted out to the client devices based on, for example, device type, carrier, and/or group.
  • the web applications server 104 is operatively connected to, or has resident within it, a resources data store 702.
  • the resources data store 702 includes resources, such as, for example, text strings, bitmaps, codes, images, character strings, and/or metadata, that may be used in connection with applications or user interfaces on the client device 102.
  • a resource is any form of static data.
  • the user of the client device 102 may register the error with a server-based component. For example, the user may access a help desk or provide quality assurance feedback. The user provided information may then be made available to an administrator (or operator or customer service agent) having access to the resource configuration module 704 shown in Figure 7. The administrator may then make a determination as to whether the error indicated by the user is a frequently occurring one and/or one that is significant relative to other types of errors. The administrator may also map the error to a particular resource stored in the resources data store 702.
  • the resource manager module 608 may auto-generate a resource bundle for deployment to the client device 102 (and to other client devices).
  • the resource bundle is auto- generated to include resources that are frequently referenced.
  • the resource bundle may be auto-generated to include "must-have" resources for the client device 102.
  • the resource file may be sent to the client device 102 over-the-air via, for example, an SMS message.
  • Figure 8 shows a flow process of a resource management process in accordance with an embodiment of the present invention.
  • the process begins when, at the client, an error is thrown 850. If a resource is locally available for that error (determined, for example, via reference to text library 330) 852, then the client operation proceeds with referencing that resource 854.
  • a resource for a thrown error is not available 852
  • the occurrence of that error is notified to the server 856.
  • Such notification may occur via one or more of various mechanisms.
  • the user may send an e-mail or SMS message notification of the error.
  • the user may access a particular web page to register the error with an administrator.
  • the resource(s) mapping to that error is/are identified 858. If the error is one not determined by the server as frequently occurring 860, those resources mapped to the received error may be sent to the client 862, whereupon the client installs the received resources 864 and client operation proceeds with referencing the appropriate resource(s) 854. However, if the error is determined as frequently occurring 860, the server marks the appropriate resource(s) to be included in a next resource file build 866. Then, at the appropriately scheduled time, the resource file is auto-generated 868 and sent to the client, whereupon the client installs the resource file 870 and client operation proceeds with referencing the appropriate resource(s) 854.
  • the client device 102 may perform an "on-demand" resource fetch. For example, if there is a continuous or frequent occurrence of a particular type of error, the client device 102 may, via the resource manager module 608, retrieve the appropriate resource(s) from the resources data store 702. In other words, the client device 102 may keep track of how many times a particular type of error occurs without being in a resource file build sent from the resource manager module 608. Upon reaching some threshold of occurrences of that error, the client device 102 demands and obtains the appropriate resource(s) from the resources data store 702.
  • that resource when retrieving the resource, that resource may be "marked" as being frequently used, so that the resource is included in a next auto-generate of a resource file.
  • the client device 102 may fetch a resource and not mark the resource as being frequently used. In such a case, that resource may be monitored for how often it is requested/fetched, and an alert may be sent to an administrator if a trend of requests for the resource indicates that that resource should be included in a next resource file build. Further, those skilled in the art will note that in one or more other embodiments, the process of monitoring resource request trends and determining whether to include the resource in a resource file build may be automated.
  • the resources in the resources data store 702 may be customized according to, for example, carrier, group, device type, and/or application suite. For example, should the client device 102 belong to a certain group regarding as having lower computer proficiency than another group, then a resource associated with an error message may be adjusted to provide more detailed error instructions as opposed to for the other group regarded as having higher computer proficiency. Thus, in such a manner, error codes may be dynamically mapped to particular resources.
  • the web applications server 104 includes a device lock module 610 and a device wipe module 612.
  • Figure 9 shows a subsystem associated with the device lock module 610 and the device wipe module 612.
  • these modules 610, 612 along with the counterpart modules on the client device 102 further described below, facilitate "kill pill & lock" services provided by system 100.
  • the availability of one or more of these services may be helpful, for example, if the user loses, misplaces, or is otherwise away from the client device 102.
  • the "kill pill & lock" services further described below allow the user to remotely restrict accessibility to user data stored on the client device 102 without having to fully deactivate the client device 102 or disable an account associated with the client device 102.
  • user data include calendar data, contact data, task data, memo data, browser bookmark data, phone application shortcut data (e.g., speed dial number data), call log data, application settings data, and SMS message history data.
  • a remote device lock may be performed by using the device lock module 610 via a kill pill & lock user interface 804.
  • the user or an administrator may access the desktop website 602, enter their phone number and account password, and choose a device lock option.
  • the user may be provided with an option to send down a message to the client device 102, where this message may then be displayed whenever someone tries to access the client device 102.
  • the "lock down" command is sent to client device 102, and the web applications server 104 waits for a confirmation.
  • a lock application 608 on the client device 102 receives the lock down command
  • the password for the client device 102 is set to the account password and the client device 102 is then locked.
  • the lock application 608 receives the lock down command
  • the command is executed, the result of which is to lock down user data on the client device 102 from being accessible through use of the client device 102.
  • the lock down command may be resent. If still not successful after a number of retries, an e-mail is sent to the user indicating failure to lock down the client device 102. On the other hand, if successful, the user receives a confirmation e-mail.
  • the web applications server 104 may request the account management server 106 to continuously broadcast messages to the client device 102 to increase a ping frequency of the client device 102 (as described above).
  • the lock down command may then be immediately sent to the client device 102 for execution.
  • a lock down command may be sent to the client device 102.
  • a remote kill pill may be sent using the device wipe module 612 via the kill pill & lock user interface 804.
  • the user or an administrator goes to the desktop website 602, enters their phone number and account password, and chooses a kill pill option.
  • the user may be asked to confirm his/her decision to send the kill pill and may be provided with an option to initiate a remote data backup before the kill pill is sent.
  • the kill pill is sent to the client device 102, and then a wipe application 808 on the client device 102 erases all (or at least a portion of) the user data on the client device 102 and returns the client device 102 to factory settings even if, for example, a requested data backup is not successful as per user preferences.
  • the user data may then be erased regardless of whether the client device 102 is connected to a service network. In this manner, once a kill pill is received, kill pill execution may not be stopped by disconnecting the client device 102 from the network (e.g., network 202 in Figure 2).
  • the kill pill may be resent. If still not successful after a number of retries, an e-mail may be sent to the user indicating a failure to successfully deploy the kill pill. On the other hand, if successful, the user receives a confirmation e-mail.
  • the web applications server 104 may request the account management server 106 to continuously broadcast messages to the client device 102 to increase a ping frequency of the client device 102 (as described above).
  • the kill pill command may then be immediately sent to the client device 102 for execution. In such a manner, as soon as the client device 102 is visible via the network, a kill pill may be sent to the client device 102.
  • the lock down command and/or the kill pill described above may be sent to the client device 102 in accordance with a configuration of the client device 102.
  • the lock down command and/or the kill pill may be sent in accordance with an operating system of the client device 102.
  • the lock down command and/or the kill pill may be sent in accordance with a type of the client device 102.
  • the corresponding desktop website 602 may only allow the user to perform a kill pill & lock function if the user's account is active (in State B or C). If the user's account is not in State B or C, the desktop website 602 may display a login error message and not allow the user to perform a kill pill & lock function. [0135] Further, the desktop website 602 may provide a user interface 804 for issuing kill pill & lock commands. As described above, to do so, the desktop website 602 may require the user to enter an account phone number and password. The desktop website 602 may authenticate the user's phone number and account password before sending out a lock down command or kill pill.
  • the desktop website 602 may allow "re- locking" of the client device 102 with a new password (if device is already locked, the user may be able to reset the password via e-mail and then re-lock the client device 102 with the new password).
  • the desktop website 602 may allow the user to choose between a kill pill or lock down command to send to the client device 102.
  • the desktop website 602 may not allow the user to issue if the user's password has been reset within a predetermined period of time (e.g., 24 hours). Further, in one or more embodiments, device locking may always be allowed regardless of a time of a last password change.
  • the kill pill or lock down command may be sent as an (encrypted) SMS message propagated through an SMS aggregator gateway (not shown).
  • the desktop website 602 may include information in the SMS message sent to the client that allows the client to authenticate the request. Further, the desktop website 602 may require the user to confirm before sending a kill pill and may remind the user of the effects of the kill pill.
  • the desktop website 602 may allow the user to enter a message to be displayed on the client device's 102 lock screen.
  • the desktop website 602 may allow the user to enter a phone number to be transmitted to the client device 102, whereupon that phone number may be displayed on the device lock screen in an effort to instruct an individual accessing the client device 102 to call that phone number (see, e.g., Figure 28).
  • the web applications server 104 may resend lock down commands and kill pills to the client device 102 if the web applications server 104 does not receive a success message from the client device 102.
  • the web applications server 104 may, for example, have the following retry schedule: 1st retry - 1 minute; 2nd retry - 5 minutes; 3rd retry - 30 minutes; 4th retry - 2 hours; 5th retry - 6 hours; 6th retry - 12 hours; and 7th retry - 24 hours. If all retries fail, the web applications server 104 may notify the user by sending an e-mail to the user's account e- mail address.
  • the user when requesting a kill pill, may have the option to request a data backup before execution of the kill pill. The user may be provided with an option to specify if the kill pill should continue even if the data backup is not initially successful.
  • the user When requesting a device lock, the user may be provided with an option to request device backup as part of the lock down command.
  • the client device 102 may be locked down and user data on the client device 102 may then be wirelessly transmitted to a remote data store. Thereafter, the client device 102 may also be "killed" (e.g., user data erased as described above) while in the locked state.
  • locking the client device 102 prevents an individual in possession of the client device 102 from trying to circumvent or prevent a lock down, data backup, and/or kill pill operation.
  • the web applications server 104 may send an e-mail to notify the user of the specific action(s) taken.
  • the web applications server 104 may notify the user via e-mail that the SMS message was received but no device confirmation was received.
  • the wipe application 808 may be able to receive and process a specially- formatted SMS message to initiate kill pill activity. Further, the wipe application 808 may authenticate the kill pill using information provided by the web applications server 104 in the SMS message. Moreover, upon receiving the SMS message, the client may initiate a data backup if the user has chosen to do so. During the backup process, if the backup fails due to any errors or is canceled manually, the client may still execute the kill pill command. When performing a kill pill function, the client may delete applications and data on the client device 102 by, for example, writing over the contents in memory and then doing a hard reset back to factory default settings.
  • the client may re-lock the client device 102 with his/her account password. Also, the client may notify its status to the web applications server 104 before the final kill pill procedure begins. If the client is unable to contact the web applications server 104, the client may continue with the kill pill process if the user has indicated such a preference when sending the kill pill.
  • the client may be able to receive and process a specially-formatted SMS message to initiate a device lock function.
  • the lock application 806 may authenticate the device lock request using information provided by the web applications server 104 in the SMS message. Upon receiving the SMS message, the client may initiate a data backup if the user has chosen to do so. Further, upon receiving the SMS message, the client locks the client device 102. Moreover, the lock application 806 may render on a display of the client device 102 a message indicating that the client device 102 is locked. The client may not allow a user to bypass the display screen without entering the correct password (see, e.g., Figure 28). Particularly, the client may allow a user to enter an account password to unlock the client device 102.
  • the client displays that message on the lock display screen. Still further, if the web applications server 104 has transmitted a user-specified phone number, the client may allow the user to call that phone number with the client device 102 (see, e.g., Figure 28). More particularly, in one or more embodiments, that phone number may not actually be displayed to the caller. Moreover, the client may allow the client device 102 to be used to dial emergency services (see, e.g., Figure 28).
  • FIG. 10 shows a flow process in accordance with an embodiment of the present invention. Particularly, a flow process for exemplar kill pill & lock services is shown.
  • a server side e.g., web applications server 104
  • client device e.g., client device 102
  • the user may specify particular instructions. Examples of additional instructions that may be requested include whether to perform a data backup before a kill pill operation is executed, whether to perform a data backup before a lock down operation is executed, a phone number to call should an individual attempt to use a phone functionality of the client device, and whether to remove a lock on user data on the client device after a predetermined amount of time.
  • the server side attempts to authenticate the user using credentials provided by the user 952. Such authentication may involve locating a user account for the client device. Assuming that the requesting user is authenticated, the server side accordingly generates a lock down command or a kill pill command 954.
  • the command may be generated in accordance with a specification of the client device as referenced in the user account located via authentication of the user. In other words, the command may be generated particularly for the intended client device.
  • the lock down or kill pill command is then wirelessly transmitted from the server side to an address of the client device 956.
  • the client device decrypts the command and makes a determination as to whether the command is a lock down command 960. If a lock down command has been received 960, the client device determines whether an instruction has been provided to perform a data backup prior to locking down the client device 962. It is noted that in one or more other embodiments, a data backup may be invoked systematically without particular request from the user. If data backup is required or requested, the user data on the client device is wirelessly backed up to a remote data store 964. Thereafter, the client device locks down the client device so that user data on the client device is restricted from being accessible using the client device 966.
  • the client device may automatically lock itself as described above (noting that should the received command not be a lock down command or kill pill command, the command is processed otherwise 982).
  • the client device determines whether an instruction has been provided to perform a data backup prior to erasing user date on the client device 970. It is noted that in one or more other embodiments, a data backup may be invoked systematically without particular request from the user. If data backup is required or requested, the user data on the client device is wirelessly backed up to a remote data store 972. Thereafter, the client device erases user data on the client device 974.
  • a kill pill or lock command may be sent to a client device from web applications server 104 even though that client device may not synchronize data via the web application server 104.
  • the ability to send a kill pill or lock command is not limited by the synchronization engine(s) used by the client device 102 to synchronize data.
  • kill pill and lock command functionalities may be supported, specific, and/or dependent on a device maker as opposed to a third party vendor offering data synchronization solutions for the device.
  • the user may choose what data is to be locked or killed. For example, the user may request that only critical data be erased as opposed to all user data. In another example, the user may allow certain types of data to remain unlocked while specifying other types of data to be locked as part of the user- initiated lock operation.
  • the client device wirelessly sends a success indication to the server side 980. Otherwise, the client device wireless sends a failure indication to the server side 978.
  • the server side then notifies the user accordingly 958. Notification to the user may be provided, for example, via e-mail, automated message to a stored home or work phone number, postal mail, or a website accessible to the user.
  • FIG 11 shows a diagram of the synchronization server 108 and the client device 102 in accordance with an embodiment of the present invention.
  • the synchronization server 108 includes a data backup module 902, a data restore module 904, a data store 906, a migration module 918, and a device database 920, each of which is further described below.
  • the synchronization server 106 also includes an HTTP/S transport component 914 and an SMS transport component 916 for respectively interfacing with the HTTP/S transport component 318 and the SMS transport component 320 resident on the client device 102.
  • These transport components 914, 916, 318, 320 may support, for example, any one or more of the various communications supported between the client device 102 and the account management server 106 (or web applications server 104).
  • data backup and restore operations between the client device 102 and the synchronization server 108 may occur using synchronization markup language (SyncML) messages sent over HTTP/S.
  • SyncML synchronization markup language
  • data backup and restore operations between the client device 102 and the synchronization server 108 may occur using a Public and Private Information (PAPI) based protocol over HTTP/S.
  • PAPI Public and Private Information
  • the data backup module 902, the data restore module 904, the data store module 906, the migration module 918, and the device database 920 support data backup, restore and migration services provided by system 100.
  • the user upon the user completing registration, the user is presented with an option to do a backup of data on his/her client device 102. If the user chooses to initiate a data backup, the user may be informed how long the data backup will take and how much data traffic will be incurred. If the user approves, the data backup is initiated and a data backup progress indicator may be displayed with a cancel option (see, e.g., Figure 25). The particular data that is backed up may vary. Upon successful completion of the data backup, the user is informed accordingly (see, e.g., Figure 26).
  • the user data may be automatically backed up according to a particular schedule. Further still, in one or more embodiments, the user data may be backed up on "as-needed" basis. Moreover, the user may manually initiate a data backup. In such cases, the user may make changes to particular data on the client device 102 and choose to perform a data backup on the changed data. In other words, in one or more embodiments, incremental changes in user data may be backed up instead of all of the user data resident on the client device 102.
  • the user may restore data to a clean client device (e.g., a new device) with data backed up from a previously used client device. This occurs by the user logging in to an existing account on their new client device.
  • the synchronization server 108 may then detect that the user has previously backed up data to the synchronization server 108.
  • the client offers the user the option to initiate a restore.
  • the user may then initiate the restore, whereupon the user is informed of the time and data usage before restore begins.
  • Restore is then initiated, and a restore progress indicator may be shown.
  • Target data is then restored to the client device 102.
  • data existing locally on the client device 102 is merged with the data stored on the synchronization server 108. After the restore is completed, the user is informed of the successful data restore.
  • the user may migrate to a new client device.
  • the new client device may have different hardware or software configuration compared to the previously used client device.
  • the new client device can be a newer generation of the used client device, or a device that is incompatible with the previously used client device.
  • the user performs a data backup of the previously used client device on the synchronization server 108.
  • the user may then acquire and install client software on the new client device as described above.
  • the data backed up from the previously used client device may then be restored (i.e., migrated) to the new client device.
  • the migration module 918 detects the hardware and software configuration of the new client device based on the configuration information.
  • the configuration information herein includes both device configuration information and user preference information.
  • the device configuration information is any information that identifies the hardware or software configuration of the client device including, among other information, client device model number, the types and version of operating system, the list and versions of applications installed on the client device, and hardware resources of the client device (e.g., RAM capacity, speed or type of a processing unit).
  • the user preference information is any information that each user individually configures for the individual client device and includes, among other preferences, ring tones, notification preferences, color schemes, speed dial numbers, and application settings. The user preference information may be in default values if the user has not modified the preference.
  • the migration module 918 may request the new client device to send the device configuration information of the new client device to the synchronization server 108. Based on the configuration information received from the new client device, the migration module 918 sends compatible data to the new client device.
  • the compatible data includes converted data and corresponding data.
  • the converted data refers to data that is converted or processed from the data stored in the data store 906 to be compatible with the new client device. For example, if the previous client device had the capability to associate a file with contact information of the sender of that file whereas the new client device does not have the capability to associate the file with the contact information of the sender, the migration module 918 may disassociate the file from the contact information before sending the file and the contact information to the new client device.
  • the migration module 918 may sort the emails or SMS messages in the data store 906 before sending them to the new client device.
  • the migration module 918 also can convert files in formats that are compatible only with the old client device to formats that are compatible with the new client device.
  • the corresponding data refers to data in the data store 906 that is compatible with the new client device without requiring any conversion or processing.
  • the device database 920 stores configuration information of various types of client devices.
  • Figure 12b shows a flow process for migrating to a new client device in accordance with an embodiment of the present invention.
  • the synchronization server 108 receives 708 backup data from the previous client device and stores 708 the data in the data store 906.
  • the synchronization server 108 requests 784 the configuration information of the new client device from the new client device or from the user.
  • the migration module 918 of the synchronization server 108 converts or processes the user's data in the data store 906 that is not compatible with the new client device. Then, the compatible data are sent to the new client device. The compatible data are then stored 796 on the new client device for use.
  • the migration may be allowed only when the user's account is active (in State B or C). If the user's account is not in State B or C, the synchronization server 108 does not perform the migration of data to the new client device. It is noted that one embodiment for migration of data is as described in, for example, commonly owned U.S. Patent No. 6,970,418 to Skinner entitled “Swapping a Nonoperational Networked Electronic System for an Operational Networked Electronic System,” which is incorporated by reference herein.
  • the types of data that may be backed up and then subsequently restored include, for example: a calendar; contacts; tasks; memos; browser bookmarks; phone application shortcuts, including speed dial numbers; call logs; application settings; and SMS message history. Further, the backup and restore process also can be configured for migration between devices of differing operating systems.
  • the compatible data includes executable codes (applications or applets).
  • the synchronization server 108 receives the executable codes from the previously used client device and stores the executable codes on the data store 906.
  • the device database 920 also includes a list of executable codes that are compatible with the client devices. The list of executable codes is referenced by the migration module 918 to determine which executable codes are compatible with the new client device. The synchronization server 108 then selectively sends the executable codes that are compatible with the new client device. For the executable codes in the data store 906 that are not compatible with the new client device, the migration module 918 identifies and sends versions of executable codes that are compatible with the new client device.
  • the new client device may provide the user with a report listing (i) the executable codes in the data store 906 that is compatible and could be transferred to the new client device, (ii) the executable codes in the data store 906 that are not compatible with the new client device but whose compatible versions has been identified and could be installed on the new client device, and (iii) the executable codes in the data store 906 that are not compatible with the new client device and whose compatible version could not be identified.
  • the user may be prompted to select the compatible version or be provided with a recommendation on executable codes that can substitute the executable codes of the previous client device.
  • the migration module 918 may search the data store 906 and/or the internet in order to identify the counterpart executable codes compatible with the new client device.
  • the data store 906 may store links to the executable codes instead of the actual binary codes of the executable codes.
  • the links may direct the new user device to a location where the user may download the executable codes compatible with the new client device.
  • the configuration information of the auxiliary computing device 102b is backed up in the paired client device 102a or in the synchronization server 108.
  • the client device 102a or the synchronization server 108 sends the stored configuration information to the auxiliary computing device 102b.
  • the configuration information may be sent from the synchronization server 108 to the auxiliary computing device 102b directly or via the client device 102a.
  • FIG. 27 shows an example of a data backup screenshot in accordance with an embodiment of the present invention.
  • the client may display a time and date of a last successful backup and any error condition if necessary.
  • the client may before a purge then perform a data backup (a "clean backup").
  • a data backup a "clean backup"
  • the client may perform the clean backup, the previously backed up data on the synchronization server 108 may be purged and replaced by the more recently backed up data.
  • the client may warn the user that existing data will be overwritten.
  • the client may perform incremental backups. If the user has already performed a backup or restore on the client device 102 (since the client was last newly registered or logged in), the client may perform an incremental backup. During the incremental backup, the client may only backup data that has been changed since it was last backed up to or restored from the synchronization server 108. Further, the client may backup data changes at the field level, rather than at a record or database/file level. [0171] Moreover, in one or more embodiments, user-initiated backups may disable other device activities that may interrupt the data backup. If a data backup times out, an error message may be displayed other device previously stopped activities may be (re-) enabled. Further, the user may be prevented from leaving a backup application. The user may be offered a cancel option that provides instant cancellation of an on-going backup and (re-) enables other previously stopped device activities.
  • an automated backup may be performed after the client device 102 has been dormant for some amount of time. If a data backup is interrupted, the data backup may auto-cancel instantly and hand over control to a requesting application or a default application (if there is no requesting application). If the data backup is auto-canceled, the client may re-attempt background backups. [0173] Further, in one or more embodiments, data backups may be performed in a non- blocking thread. If the client is the active application during a data backup, the client may display progress information to the user including the type of data currently being backed up and an overall completion percentage.
  • the client may be able to continue a data backup even if target data is changed by the user during the data backup. Still further, in one or more embodiments, the user may be able to initiate an outbound phone call or receive an inbound phone call when a data backup is being performed. Also, the user may be able to initiate data activity when a data backup is being performed. In such cases, the data backup may be canceled and the client may retry the data backup at a later time. Additionally, the user may be able to cancel a data backup process from within the client. [0174] As described above, the user may initiate a manual data backup. For example, the client may inform the user of a projected time and data usage for backup activity before activity begins and may give the user an option to cancel.
  • the client may present the user with a backup schedule configuration screen.
  • the client may be able to initiate automated backups. Automated backups may be performed based on a user-configurable schedule. If the user has not already performed an initial backup, an automated backup may not be performed. Moreover, automated backups may be performed, for example, "after any change", daily, weekly, monthly, or never as specified by the user. If the user selects "after any change", the client may attempt to perform an automated backup whenever particular data is changed.
  • the client may wait until the client device 102 is inactive before attempting an "after any change" data backup. Such data backups may not be performed more than once in a particular time period. Data changes performed during this waiting period may be batched and performed when the waiting period is over. If the user does not select "after any change” or “manual", the client may attempt to perform automated backups during a random time (based on local device time) within a time frame specified by the user's "time of day” preference: “morning" is 6am - 12pm; “afternoon” is 12pm - 6pm; “evening” is 6pm - 12am; and “overnight” is 12am - 6am. Further, automated backups may be attempted on a schedule regardless of whether the user has performed additional manual backups. Moreover, automated backups may only be performed when the client device 102 has gone into a sleep mode and has been sleeping for a particular amount of time.
  • the client may provide the user with one or more of the following user-configurable settings for automated backup: "after any change”; “once per day”; “once per week”; “once per month”; and “manual”. If the user has never performed a data backup, a "manual" selection may be the default setting. Further, the user may be prompted during an initial backup with an option to set a backup schedule to "automated” - the default automated value may be set to "daily”. When automated backup schedule is set to "daily”, “weekly”, or “monthly”, an additional "time of day” preference may be made available.
  • Possible values may include, for example, “morning”, “afternoon”, “evening”, and “overnight”, where a default setting may be set to "overnight”. Additionally, preference options may include a "do not backup when roaming" option, where the default setting may be set to leave this option unchecked. Further, this preference may only be applicable for an automated backup and not a manual backup.
  • the client may indicate a general data backup state on a main screen using a visual characteristic (e.g., a colored icon). For example, the client may use a green icon to indicate the user's data has been successfully backed up within a certain time since a last scheduled automated backup time. If the user performs backup manually, the client may show a green icon if the user has backed up within a last specified period of time. Further still, the client may use, for example, a yellow icon to indicate that the user's data has never been backed up or has not been backup up recently. Further still, for example, the client may use a red icon to indicate that the last attempted backup resulted in a fatal error.
  • a visual characteristic e.g., a colored icon
  • the client may perform one or more of the following checks before a data backup process.
  • the synchronization server 108 may allow the client to perform a data backup if the user's account is provisional or active. Further, if the user's account is disabled, the client may display a login error message and cancel backup activity. Moreover, the client may validate a token with the synchronization server 108 to authenticate the user before performing data backup activity. If validation fails and the application is running in the foreground, the client may show a login retry dialog, which may present the user with the ability to reset his/her password or authenticate with account management server 106. If the user is able to authenticate via the login retry dialog, the client may continue with the data backup process.
  • the client may treat the data backup as canceled. Moreover, if validation fails and an application is running in the background, the client may notify the user via a system notification that the authentication has failed. When the user successfully authenticates with the system, pending system notifications may be deleted. If validation fails, the client may not attempt another automated backup until the error condition is fixed.
  • the client may confirm that a radio is turned on. If the radio is not on and the client is running in the foreground, the client may prompt the user if he/she wants to turn on the radio. If the user selects "yes", the client turns the radio on and proceeds. If the selection is "no", the client may cancel the data backup process display an error message. If the radio is not on and the client is running in the background, the client may cancel the data backup process and notify the user of the failure. In this case, the client may start a data backup automatically when the radio is next turned on and the client device 102 goes into sleep mode. The client may then not start another automated backup until the radio is turned on.
  • the client may confirm that the client device 102 is in range of data coverage. If the client device 102 is out of data coverage range and the client is running in the foreground, the client may cancel the data backup process and display an error message. If the client device 102 is out of data coverage range and the client is running in the background, the client may cancel the data backup process and accordingly notify the user.
  • the client may start a data backup process automatically when the condition is fixed. Further, the client may not start another automated backup until the condition is fixed.
  • the client may determine if the client device 102 is in a roaming mode. If a "do not backup when roaming" preference is set to "true" and the client is running in the background, the client may cancel the data backup process. The client may start a data backup process automatically when the condition is fixed. Further, the client may not start another automated backup until the condition is fixed.
  • the client may confirm that a battery is at a sufficient level to complete a data backup. If the battery level is not sufficient and the client is running in the foreground, the client may cancel the data backup process and display an error message. If the battery level is not sufficient and client is running in the background, the client may cancel the data backup process and notify the user accordingly. Further, the client may start a data backup automatically when the battery level is sufficient. Moreover, the client may not start another automated backup until the battery level is sufficient. If the client is running in the foreground and backup activity fails for some reason, the client may notify the user that the data backup has failed. If the client is running in the background and the data backup process fails for some reason, the client may not immediately notify the user.
  • the client may perform, for example, the following retry schedule after encountering an unknown data backup failure: 1st retry - 1 minute; 2nd retry - 5 minutes; 3rd retry - 30 minutes; 4th retry - 2 hours; 5th retry - 6 hours; 6th retry - 12 hours; and 7th retry - 24 hours. If all retries fail, the client may notify the user accordingly.
  • the client may clear alerts generated by system notifications if the data backup becomes successful. Moreover, if the client is in the process of a retry schedule, other automated backups may be disallowed. Further still, if a successful data backup is performed, pending retries may be cancelled. Still further, the client may display information about the retry cycle including the number of failures, time of last failure, scheduled time of next attempt, and reason for failure.
  • the client application main screen may indicate device data signal strength and battery level.
  • the synchronization server 108 may be able to detect inactive backup accounts. When the synchronization server 108 detects an inactive backup account, the synchronization server 108 may notify an account holder via e- mail that their backup account is inactive and that backed up user data will be deleted after a certain period of time if no additional backup or restore activities are performed by the user.
  • backed up user data may be deleted from the synchronization server
  • the synchronization server 108 may send an e-mail to the user indicating that their user data has been deleted from the synchronization server 108 and informing the user that the user can re-login and perform a new initial backup if the user wishes to continue using the service.
  • the user's backup data is deleted due to inactivity, the user's account is not necessarily deleted.
  • the client may retrieve target data and restore all that data to the client device 102.
  • the restore may actually be a bi-directional synchronization operation. Further, the restore operation may be performed in the background.
  • the client may display status to the user including type of data currently being restored and an overall completion percentage. Moreover, during a restore operation, the client may prevent an automated backup from being initiated until the restore process is completed.
  • the client may provide the user the ability to pause the restore operation.
  • the restore activities may be put on hold.
  • the client may provide user with the ability to restart the restore operation.
  • the client may suspend an automated backup and disable a manual data backup until the restore operation is completed.
  • the client may inform the user of the following. The user may be informed that local data and settings will be restored to the client device 102. Further, the user may be presented with an estimate of time and data usage required to perform the restore. Moreover, the user may be informed of the time and date that the last successful backup was performed. Also, the user may be given the opportunity to cancel the restore operation at this point. [0191] Additionally, in one or more embodiments, the client may be able to perform a restore operation after an initial device login.
  • the client may offer the user the ability to do a restore operation if the user has existing backup data on the synchronization server 108 that can be restored to the client device 102. If the user does not have data backed up on the synchronization server 108, the client does not offer user the option to perform a restore operation. If the client is unable to determine whether the user has data backed up on the synchronization server 108, the client operates as if there is data available on the synchronization server 108 to restore. If the user chooses to restore and no data is backed up on the synchronization server 108, the client may inform the user that no data was restored to the client device 102.
  • the client may perform the following checks before a restore operation.
  • the synchronization server 108 may only allow the client to perform a restore operation if the user's account is in State B or C. If the user's account is not in State B or C, the client may display a login error message and cancel restore activity.
  • the client may confirm that a radio is turned on. If the radio is not on, the client must ask the user if he/she wants to turn on the radio. If the user selects "yes”, the client turns the radio on and proceeds with a restore operation. If the user selects "no", the client may cancel the restore activity and display an error message.
  • the client may offer the user the option to retry the restore operation later.
  • the client may confirm that the client device 102 is in range of data coverage. If the client device 102 is out of data coverage range, the client may cancel restore activity and display an error message. The client may then offer the user the option to retry the restore operation later.
  • the client may confirm that the battery is at a sufficient level to complete a restore operation. If the battery level is not sufficient, the client may cancel the restore activity and display an error message accordingly. The client may then offer the user the option to retry the restore operation later.
  • the client may confirm that the client device 102 has enough memory available to complete the restore operation. If there is not enough memory available, the client may cancel the restore activity and display an error message accordingly. The client may then offer the user the option to retry the restore operation later.
  • the client may notify the user that the restore has failed. The client may then offer the user the option to retry the restore operation later.
  • the client may pause the restore operation and follow a retry schedule.
  • the client may provide the user with the ability to restart the restore operation.
  • the client may suspend an automated backup and disable a manual backup until the restore process is completed.
  • the client may perform, for example, the following retry schedule after encountering an unknown restore failure: 1st retry - 1 minute; 2nd retry - 5 minutes; 3rd retry - 30 minutes; 4th retry - 2 hours; 5th retry - 6 hours; 6th retry - 12 hours; and 7th retry - 24 hours. If all retries fail, the client may notify the user accordingly.
  • the client may support migration
  • the client may convert a format of backed-up data as is necessary so that when it is restored, it is in the proper format for the target device.
  • the client may not allow the user to restore data from one operating system to a different operating system. Still further, the client may not restore non-applicable settings when migrating to a different type of device.
  • the client may restore data in such a manner so that regularly ongoing synchronization activities by the user are not negatively impacted and duplicates are not created on the client. If the user has performed an initial synchronization operation and is attempting to perform a restore, the client may ask the user if server data or device data should win in case of a conflict.
  • the client may inform the user that the restore operation was successful via an alert. Further, after successful restore, the client may proceed with scheduled automated backups.
  • the client may merge existing data on the client device 102 with retrieved data.
  • the restore process does not create duplicates.
  • duplicative data may be detected and removed at the server level.
  • data de-duping occurs at the client device 102.
  • the de-duping module 908 upon wirelessly receiving previously backed up user data, can detect and remove redundant data items so that only one instance of a particular data item remains. Examples of user data that may be processed by the de-duping module 908 include calendar data, contact data, task data, memo data, browser bookmark data, phone application shortcut data (e.g., speed dial number data), call log data, application settings data, and SMS message history data.
  • the de-duping module 908 may recognize the data items as being identical for purposes of phone number contact data, in which case one of the phone number data items is removed.
  • the de-duping module 908, and the de-duping functionality of system 100 in general may occur automatically. In other words, differences among user data may be resolved automatically and without query to a user.
  • the de-duping module 908 may be capable of detecting duplicate data items that are received via different synchronization mechanisms.
  • synchronization engines synchronize data of different types.
  • one particular synchronization engine may be used to synchronize contact, calendar, and memo data items, while another synchronization engine may be used to synchronize call history, browser bookmarks, phone favorites, contact, calendar, and memo data items.
  • the client device 102 may have duplicate data items received in response to synchronization operations performed with different synchronization engines.
  • the de-duping module 908 is capable of detecting duplicate data items even in view of the use of different synchronization engines.
  • Figure 12a shows a flow process of a client- side de-duping operation in accordance with an embodiment of the present invention. Initially, in a particular database, an nth record is read 750. If the end of the database has been reached 752, the de-duping operation ends 754. Otherwise, if the end of the database has not been reached 752, a determination is made as to whether the nth record has been deleted 756. If the record has been deleted, n is incremented 770, and the process goes back and reads the new nth record 750.
  • nth record has not been deleted 756, a next record is read 758. If the next record marks the end of the database 760, n is incremented 770, and the process goes back and reads the new nth record 750. Otherwise, if the end of the database has not been reached 760, a determination is made as to whether the nth record and the next record are of the same size 762. If these records are not of the same size 762, then a new next record is read 758 for subsequent comparison with the nth record. However, if the nth record and the next record are of the same size 762, a binary compare is performed on the nth record and the next record 764.
  • a binary compare operation may be performed only when it is needed (e.g., after comparison of sizes and other checks), so as to prevent unnecessary binary compare operations.
  • the set of databases subject to de-duping as described above may be specified in a list of user or administrator preferences. Moreover, preferences may indicate what types of data are desired to be de-duped. Different types of databases may correspond to different synchronization engines used by the client device 102 to perform data synchronization.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un système (et un procédé) qui décrit la migration de données d'un premier dispositif client vers un second dispositif client. Un second dispositif client transmet des informations de configuration du second dispositif client à un serveur distant. Le serveur distant compare ces données aux données provenant du premier dispositif client qui ont été précédemment envoyées au serveur distant par le premier dispositif client. Le serveur distant prépare les données dont le format est compatible avec la configuration matérielle ou logicielle du second dispositif client et qui correspondent aux données provenant du premier dispositif client. Par la suite, le serveur distant transmet ces données au second dispositif client, qui les utilise pour initialiser (par exemple, restaurer ou réinitialiser) le second dispositif client.
PCT/US2008/054984 2007-03-02 2008-02-26 Migration intelligente entre des dispositifs ayant une configuration matérielle ou logicielle différente WO2008109291A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP08730733A EP2115577A1 (fr) 2007-03-02 2008-02-26 Migration intelligente entre des dispositifs ayant une configuration matérielle ou logicielle différente

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/681,640 US9037685B2 (en) 2006-11-15 2007-03-02 Intelligent migration between devices having different hardware or software configuration
US11/681,640 2007-03-02

Publications (1)

Publication Number Publication Date
WO2008109291A1 true WO2008109291A1 (fr) 2008-09-12

Family

ID=39587968

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2008/054984 WO2008109291A1 (fr) 2007-03-02 2008-02-26 Migration intelligente entre des dispositifs ayant une configuration matérielle ou logicielle différente

Country Status (2)

Country Link
EP (1) EP2115577A1 (fr)
WO (1) WO2008109291A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2244440A1 (fr) * 2009-04-24 2010-10-27 Vodafone Group plc Procédé et système pour faire migrer les propriétés dans des dispositifs de télécommunications
WO2010145034A1 (fr) * 2009-06-18 2010-12-23 Research In Motion Limited Sauvegarder et/ou restaurer une application logicielle afin de faciliter la vérification de compatibilité avec un dispositif cible avant la restauration de l'application
WO2011080598A2 (fr) * 2009-12-30 2011-07-07 Nokia Corporation Mécanisme de restauration guidée par le contexte
EP2521034A1 (fr) * 2010-05-21 2012-11-07 ZTE Corporation Procédé, dispositif et terminal de gestion pour programme d'application
EP2922272A4 (fr) * 2012-11-16 2016-06-22 China Mobile Comm Corp Procédé de synchronisation de données, système, serveur de synchronisation de données et terminal

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020111972A1 (en) * 2000-12-15 2002-08-15 Virtual Access Networks. Inc. Virtual access
US20060026587A1 (en) 2004-07-28 2006-02-02 Lemarroy Luis A Systems and methods for operating system migration

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020111972A1 (en) * 2000-12-15 2002-08-15 Virtual Access Networks. Inc. Virtual access
US20060026587A1 (en) 2004-07-28 2006-02-02 Lemarroy Luis A Systems and methods for operating system migration

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2244440A1 (fr) * 2009-04-24 2010-10-27 Vodafone Group plc Procédé et système pour faire migrer les propriétés dans des dispositifs de télécommunications
ES2354331A1 (es) * 2009-04-24 2011-03-14 Vodafone S.A.U. Procedimiento y sistema para migrar perfiles en dispositivos de telecomunicaciones.
US8209436B2 (en) 2009-04-24 2012-06-26 Vodafone Group Plc Method and system of migrating profiles in telecommunications devices
WO2010145034A1 (fr) * 2009-06-18 2010-12-23 Research In Motion Limited Sauvegarder et/ou restaurer une application logicielle afin de faciliter la vérification de compatibilité avec un dispositif cible avant la restauration de l'application
WO2011080598A2 (fr) * 2009-12-30 2011-07-07 Nokia Corporation Mécanisme de restauration guidée par le contexte
WO2011080598A3 (fr) * 2009-12-30 2012-01-05 Nokia Corporation Mécanisme de restauration guidée par le contexte
EP2521034A1 (fr) * 2010-05-21 2012-11-07 ZTE Corporation Procédé, dispositif et terminal de gestion pour programme d'application
EP2521034A4 (fr) * 2010-05-21 2013-01-23 Zte Corp Procédé, dispositif et terminal de gestion pour programme d'application
US8555060B2 (en) 2010-05-21 2013-10-08 Zte Corporation Managing method, device and terminal for application program
EP2922272A4 (fr) * 2012-11-16 2016-06-22 China Mobile Comm Corp Procédé de synchronisation de données, système, serveur de synchronisation de données et terminal

Also Published As

Publication number Publication date
EP2115577A1 (fr) 2009-11-11

Similar Documents

Publication Publication Date Title
US9037685B2 (en) Intelligent migration between devices having different hardware or software configuration
US8086695B2 (en) Over the air services for mobile devices
US8135798B2 (en) Over-the-air device services and management
US8015163B2 (en) Detecting duplicative user data on computing device
US20080115141A1 (en) Dynamic resource management
JP6396887B2 (ja) モバイルデバイスサポートサービスを提供するためのシステム、方法、装置、および非一時的コンピュータ可読記憶媒体
US9594597B2 (en) Systems and methods for automated server side brokering of a connection to a remote device
US8762985B2 (en) User terminal device and service providing method thereof
US20080120423A1 (en) System and method of actively establishing and maintaining network communications for one or more applications
AU2005299577A1 (en) A method and apparatus for management of data on handheld
US20150199656A1 (en) Status Conditions of Imaging Devices for Generating Automatic Service Support
WO2008109291A1 (fr) Migration intelligente entre des dispositifs ayant une configuration matérielle ou logicielle différente
EP2620003B1 (fr) Stockage d'applications et de biens numériques associés en vue d'une utilisation dans des dispositifs et systèmes de communication sans fil
US10819842B2 (en) Providing on-demand access to a restricted resource of a user device
Cisco Backing Up and Restoring Cisco CallManager Release 3.1(1)
Headquarters Disaster Recovery System Administration Guide for Cisco Unified Contact Center Express Release 8.0 (2)
NO20091865L (no) Systemer, metoder og anordninger for administrasjon av flere mobile enheter

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08730733

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2008730733

Country of ref document: EP