Abstract: A client-side device is capable of wirelessly receiving user data for the device. The device is capable of removing duplicative user data items among data wirelessly received and data already existing on the device. The duplicative data may be “de-duped” even though duplicative data items may arise as a result of synchronization operations using different synchronization engines used to synchronize different sets of data types.

Abstract: Techniques are disclosed for a content-based navigation and launching for portable computing devices such as PDAs and smart phones. A content navigator and launcher allows a user to personalize content groupings. The techniques can run on top of any OS file system that has a mechanism to associate files with their creating applications. Personalization of the content-based navigation and launching scheme can be set-up on the user's work station, and then transmitted and synchronized with a target mobile device. A central server can be used to carry out content harvesting and/or configuring the personalization scheme. The content and/or personalization scheme can then be pushed on to the mobile device (e.g., via a GSM network or other suitable communication link). APIs can be used by application vendors to register the content types of their own choice. A preferences utility allows users to manage the content types and associations.

Abstract: Techniques are disclosed for a content-based navigation and launching for portable computing devices such as PDAs and smart phones. A content navigator and launcher allows a user to personalize content groupings. The techniques can run on top of any OS file system that has a mechanism to associate files with their creating applications. Personalization of the content-based navigation and launching scheme can be set-up on the user's work station, and then transmitted and synchronized with a target mobile device. A central server can be used to carry out content harvesting and/or configuring the personalization scheme. The content and/or personalization scheme can then be pushed on to the mobile device (e.g., via a GSM network or other suitable communication link). APIs can be used by application vendors to register the content types of their own choice. A preferences utility allows users to manage the content types and associations.

Abstract: A server computer system comprises a memory and a processing circuit. The memory is configured to store supplier identifiers for a plurality of product suppliers. The processing circuit is configured to receive a request to make a payment from a mobile computing device via a wireless communication, to select a supplier identifier from the memory based on the request, to generate a message comprising the supplier identifier, transaction amount, and a user identifier identifying a user of the mobile computing device, and to transmit the transaction message to a server associated with an entity which processes a transaction based on the transaction message.

Abstract: A client device may be managed in the event of, for example, device loss or mislocation. In such a case, a user can effectively cause a restriction command to be generated, where the restriction command is wirelessly transmitted to the client device. The restriction command can be specified to either lock user data on the client device or erase user data on the client device.

Abstract: Selecting a service for a mobile computing device includes receiving a message from the mobile computing device via a wireless network, storing data from the message, querying the data to identify a characteristic, selecting a service from a plurality of services based on the identified characteristic, and sending the selected service to the mobile computing device

Abstract: A client-side device is capable of wirelessly receiving user data for the device. The device is capable of removing duplicative user data items among data wirelessly received and data already existing on the device. The duplicative data may be “de-duped” even though duplicative data items may arise as a result of synchronization operations using different synchronization engines used to synchronize different sets of data types.

Abstract: A system and method of backing up a data file from a mobile computing device is disclosed. The method can include receiving a data file from the mobile computing device at a server computer and storing the data file on a storage device. The method can include receiving data indicative of changes made to the data file on the mobile computing device. The method can further include changing the data file stored on the storage device based on the data indicative of changes made to the data file on the mobile computing device.

Abstract: A mobile computing device comprises a wireless transceiver configured to communicate with a remote server, a memory; and a processing circuit. The processing circuit is configured in a restore operation to receive first data from the remote server, to receive a source indicator for second data from the remote server, wherein the first data and second data represent data previously stored in the memory of the mobile computing device or in a memory of another mobile computing device, and to send a request for the second data based on the source indicator using the wireless transceiver.

Abstract: A client device may be managed in the event of, for example, device loss or mislocation. In such a case, a user can effectively cause a restriction command to be generated, where the restriction command is wirelessly transmitted to the client device. The restriction command can be specified to either lock user data on the client device or erase user data on the client device.

Abstract: A system and method for facilitating approval of an application and for making the application available for download by mobile computing devices has a first module configured to receive a user input received from a software development environment, a second module configured to initiate an application approval process based on the user input, and a third module configured to make the application available for download by mobile computing devices based on the approval process.

Abstract: A client-side device is capable of wirelessly receiving user data for the device. The device is capable of removing duplicative user data items among data wirelessly received and data already existing on the device. The duplicative data may be “de-duped” even though duplicative data items may arise as a result of synchronization operations using different synchronization engines used to synchronize different sets of data types.

Abstract: Instead of initially deploying a full set of static data resources to a client device, when notification of an error experienced by the client device is made, a determination is made as to whether that error is frequently concurring. In such a case, the resource associated that error is scheduled to be part of a next resource file build, whereupon the generated resource file is wirelessly communicated to the client device for installation.

Abstract: A client-side device is capable of wirelessly receiving user data for the device. The device is capable of removing duplicative user data items among data wirelessly received and data already existing on the device. The duplicative data may be “de-duped” even though duplicative data items may arise as a result of synchronization operations using different synchronization engines used to synchronize different sets of data types.

Abstract: An over-the-air device services and management system includes a web applications server for providing a software download service, an account management server for providing an account maintenance service, and a synchronization server for providing a data management services. The suite of services offered by these servers may be wirelessly accessed from a client device.

Abstract: A client-side device is capable of wirelessly sending heartbeats to a server-side device. The server-side device is capable of instruction the client-side device when and at what frequency to send a next heartbeat. Additionally, the server-side device is capable of instructing the client-side device how to send a next heartbeat.

Abstract: A client device may be managed in the event of, for example, device loss or mislocation. In such a case, a user can effectively cause a restriction command to be generated, where the restriction command is wirelessly transmitted to the client device. The restriction command can be specified to either lock user data on the client device or erase user data on the client device.

Abstract: A system (and method) discloses migrating data of a first client device to a second client device. A second client device transmits configuration information of the second client device to a remote server. The remote server compares this data to data from the first client device that was previously sent to the remote server from the first client device. The remote server prepares data that is in a format that is compatible with hardware or software configuration of the second client device and that corresponds to the data from the first client device. Thereafter, the remote server transmits this data to the second client device, which uses it to initialize (e.g., restore or reinitialize) the second client device.

Abstract: Techniques are disclosed for a content-based navigation and launching for portable computing devices such as PDAs and smart phones. A content navigator and launcher allows a user to personalize content groupings. The techniques can run on top of any OS file system that has a mechanism to associate files with their creating applications. Personalization of the content-based navigation and launching scheme can be set-up on the user's work station, and then transmitted and synchronized with a target mobile device. A central server can be used to carry out content harvesting and/or configuring the personalization scheme. The content and/or personalization scheme can then be pushed on to the mobile device (e.g., via a GSM network or other suitable communication link). APIs can be used by application vendors to register the content types of their own choice. A preferences utility allows users to manage the content types and associations.