Patent application number | Description | Published |
20120290657 | Transferring Application State Across Devices - A first client device or system performs a method that includes retaining in memory registration information for a respective application indicating the respective application is registered for sharing application state with other client devices or systems. The method further includes storing an application state of a respective application, and detecting a transfer triggering condition. The transfer triggering condition includes presence of a second client device or system within a predefined proximity of the first client device or system, and the predefined proximity is a predefined proximity for near field communication. Furthermore, upon detecting the triggering condition, the first client device or system determines, in accordance with the stored registration information, that the respective application is registered for application state sharing, and transmits the application state of the respective application to the second client device or system. | 11-15-2012 |
20120290663 | Transferring Application State Across Devices with Checkpoints - A first client device executes a plurality of actively running applications, each having one or more checkpoints, each checkpoint identifying an execution breakpoint at which a respective application can be suspended and subsequently resumed. The first client device detects a transfer triggering condition, stores an application state for each of the plurality of actively running applications, and transmits the stored application state for each of the plurality of actively running applications to a second client device or system. The stored application state for each respective application of the plurality of actively running applications corresponds to a checkpoint of the respective application. Optionally, the transfer triggering condition includes presence of the second client device or system within a predefined proximity of the first client device or system, wherein the predefined proximity is a predefined proximity for near field communication. | 11-15-2012 |
20120290669 | Zero-Click Sharing of Application Context Across Devices - A first client device performs a handoff operation to a second client device by transmitting application information, associated with a first application, to the second client device when the first client device is positioned within a predefined proximity of the second client device. The first application has a first client device user interface state when the handoff operation is performed. Further, the first client device, in response to receiving from another client device application information associated with a second application executed by the other first client device, executes a third application corresponding to the second application with an initial user interface state corresponding to a user interface state of the other client device. | 11-15-2012 |
20130173699 | Zero-Click Sharing of Application Context Across Devices - A first client device performs a handoff operation to a second client device by transmitting application information, associated with a first application, to the second client device when the first client device is positioned within a predefined proximity of the second client device. The first application has a first client device user interface state when the handoff operation is performed. Further, the first client device, in response to receiving from another client device application information associated with a second application executed by the other first client device, executes a third application corresponding to the second application with a user interface state corresponding to a user interface state of the other client device. | 07-04-2013 |
20130325967 | TRANSFERRING APPLICATION STATE ACROSS DEVICES - A first client device or system performs a method that includes retaining in memory registration information for a respective application indicating the respective application is registered for sharing application state with other client devices or systems. The method further includes storing an application state of a respective application, and detecting a transfer triggering condition. The transfer triggering condition includes presence of a second client device or system within a predefined proximity of the first client device or system, and the predefined proximity is a predefined proximity for near field communication. Furthermore, upon detecting the triggering condition, the first client device or system determines, in accordance with the stored registration information, that the respective application is registered for application state sharing, and transmits the application state of the respective application to the second client device or system. | 12-05-2013 |
20130347117 | AUTOMATED ACCOUNTS FOR MEDIA PLAYBACK - Content stored on a server may be selected using a user device and enabled on a central device. The identity of the central device may be authenticated without transmitting user credentials corresponding to the user, user device, user account, etc. A central device identifier can be sent to the server via the user device. An encrypted version of the central device identifier may be returned to the user device and to the central device. The central device can send the encrypted and unencrypted version of the identifier to the server, and the server can transmit the desired content to the remote device based on a comparison of the encrypted and unencrypted identifier. | 12-26-2013 |
20140366102 | AUTOMATED ACCOUNTS FOR MEDIA PLAYBACK - Content stored on a server may be selected using a user device and enabled on a central device. The identity of the central device may be authenticated without transmitting user credentials corresponding to the user, user device, user account, etc. A central device identifier can be sent to the server via the user device. An encrypted version of the central device identifier may be returned to the user device and to the central device. The central device can send the encrypted and unencrypted version of the identifier to the server, and the server can transmit the desired content to the remote device based on a comparison of the encrypted and unencrypted identifier. | 12-11-2014 |
20150121233 | Synchronized Distributed Networks with Frictionless Application Installation - Methods and systems are provided related to synchronized networks. A synchronized network can include a node and additional nodes. The node can receive a packet including information. The node can determine whether the packet is from the synchronized network. After determining that the packet is from the synchronized network, the node can: send the packet to at least one of the additional nodes, determine whether a synchronized network interface (SNI) is on the node and is associated with the packet, where the SNI includes software executable on the node. After determining that the SNI is on the node and is associated with the packet, the node can generate a view of data in the synchronized network by: determining a user interface (UI) layout associated with the SNI, generating the view based on the UI layout and on the information using the SNI, and provide the view. | 04-30-2015 |
20150121363 | Synchronized Distributed Networks with Frictionless Application Installation - A node of a synchronized network can receive a triggering input. The triggering input can be an input related to: receiving a packet from the synchronized network, sending a packet using the synchronized network, utilizing an application of the node, a sensor associated with the node, a user interface associated with the node, a location associated with the node, and/or a status of the node. The node can determine a synchronized network interface (SNI) that is associated with the triggering input and is configured with software for utilizing the synchronized network. The node can determine whether the software of the SNI is uninstalled on the node. After determining that the software of the SNI is uninstalled on the node, the node can receive, install, and execute the software of the SNI to utilize the synchronized network. | 04-30-2015 |