| Patent application number | Description | Published |
|---|
| 20090307280 | SYNCHRONIZATION IMPROVEMENTS - Synchronization architectures, methods, systems, and computer readable media are described. A synchronization session is initiated between a first data processing system and a second data processing system. A first data, representing changes, is transmitted from the first data processing system to the second data processing system prior to completing a negotiation of a synchronization mode in the synchronization session for synchronizing data between the first data processing system and the second data processing system. | 12-10-2009 |
| 20090307281 | SYNCHRONIZATION IMPROVEMENTS - Synchronization architectures, methods, systems, and computer readable media are described. In one embodiment, a synchronization session is initiated between a first data processing system and a second data processing system. First data, representing changes to a first data class, is transmitted from the first data processing system to the second data processing system. Second data, representing changes to a second data class, is transmitted from the first data processing system to the second data processing system. Transmission of the second data begins before transmission of the first data is complete. The first data may comprise structured data such as contacts information, to do information, calendar information, or web browsing bookmarks. | 12-10-2009 |
| 20090307376 | SYNCHRONIZATION IMPROVEMENTS - Synchronization architectures, methods, systems, and computer readable media are described. In one embodiment, a first synchronization session is entered between a first data processing system and a second data processing system. A first command is processed in the first synchronization session. The first command causes data exchanged in the first synchronization session to be stored. The first command also represents a termination of the first synchronization session. A second synchronization session, between the first and second data processing systems, is entered after the first synchronization session. A mapping of identifiers of data synchronized during the first synchronization session is transmitted, during the second synchronization session, between the first and second data processing systems. The first command may be a commit command. The data which is synchronized may be structured data such as contact information, to do information, calendar information, or web browsing bookmarks. | 12-10-2009 |
| 20100082732 | Trickle Sync Protocol - Among other things, techniques and systems are disclosed for providing trickle syncing. In one aspect, a system includes a data repository to store one or more data records and a server in communication with the data repository. The server is designed to access the data repository in response to a user request to perform at least one of the following: access the one or more data records, add a data record, and modify the one or more data records. The system also includes a client application in communication with the server. The client application is designed to receive the user request through a client process; encapsulate a protocol that provides communications between the client process and the server; and forward the received user request to the server using the encapsulated protocol. | 04-01-2010 |
| 20100223400 | Data Synchronization Protocol - Among other things, techniques and systems are disclosed for syncing data between a client device and a server. Synchronizing data includes initiating a sync session by negotiating a sync mode between a client device and a server for each of one or more dataclasses. A status code is generated based on a result of the negotiating. Based on the generated status code, the client device and the server exchanges one or more data items to be updated for the one or more dataclasses using the negotiated sync mode for each dataclass. The exchanged one or more data items are updated at the client device or the server The updated one or more data items are committed at the client or the server. | 09-02-2010 |
| 20100279652 | Remotely Locating and Commanding a Mobile Device - Methods, systems, and apparatus are presented for processing a remote command message. In one aspect, a method includes accessing a subscribed topic hosted on a notification service, the subscribed topic corresponding to a mobile device, retrieving a remote command message included in the subscribed topic that identifies a command to be executed by the mobile device, determining whether the command can be executed by the mobile device, publishing a result message associated with the command, and executing, by the mobile device, the command based on the determining. Publishing the result message further can include identifying in the remote command message a result topic corresponding to the notification service and publishing the result message to the identified result topic. Additionally, the subscribed topic can be uniquely associated with the mobile device. | 11-04-2010 |
| 20100279673 | Remotely Locating and Commanding a Mobile Device - Methods and systems are presented for remotely commanding a mobile device. In one aspect, a method includes receiving input identifying a mobile device, presenting to a user one or more remote commands corresponding to the mobile device, receiving user input selecting a remote command from the one or more presented remote commands, generating a remote command message instructing the mobile device to execute the selected remote command, and transmitting the remote command message to a server for publication in a message topic. Further, a selectable list of mobile devices associated with a remote management account can be presented to the user, the selectable list including information uniquely identifying each mobile device. Additionally, the selectable list of mobile devices can include an indication of whether an included mobile device is online. | 11-04-2010 |
| 20100279675 | Remotely Locating and Commanding a Mobile Device - Methods, systems, and apparatus are presented for processing a remote lock command message. In one aspect, a method includes receiving, by a mobile device, a remote lock command message comprising a lock command and specifying a passcode to be set by the mobile device, locking the mobile device in response to the received remote lock command message, setting an unlock passcode associated with the mobile device to the specified passcode, and generating an acknowledgement message in response to the remote lock command message. Further, receiving the remote lock command message can include accessing a subscribed topic hosted on a notification service, the subscribed topic being associated with a lock command, and retrieving the remote lock command message from the subscribed topic. Additionally, locking the mobile device can include locking a display such that access to information stored on the mobile device and device functionality are blocked. | 11-04-2010 |
