Abstract: Methods and apparatuses that enroll a wireless device into an enterprise service with a management server addressed in a management profile are described. The enrollment may grant a control of configurations of the wireless device to the management server via the management profile. In response to receiving a notification from the management server, a trust of the notification may be verified against the management profile. If the trust is verified, a network session may be established with the management server. The network session may be secured via a certificate in the management profile. Management operations may be performed for management commands received over the secure network session to manage the configurations transparently to a user of the wireless device according to the control.

Abstract: Methods and apparatuses that enroll a wireless device into an enterprise service with a management server addressed in a management profile are described. The enrollment may grant a control of configurations of the wireless device to the management server via the management profile. In response to receiving a notification from the management server, a trust of the notification may be verified against the management profile. If the trust is verified, a network session may be established with the management server. The network session may be secured via a certificate in the management profile. Management operations may be performed for management commands received over the secure network session to manage the configurations transparently to a user of the wireless device according to the control.

Abstract: A technique for synchronizing a datum between a plurality of stores, wherein a version history is associated with the datum in each store. The version history has one or more entries, and each entry has an identifier and a value. The identifier identifies a store that has modified the datum, and indicates a number of modifications to the datum. When synchronizing the datum between stores, the version histories of the datum are compared to determine whether one version history is subordinate to another version history. The datum having the subordinate version history is then replaced with the datum having the dominant version history. Conflict resolution is required if the version histories are not identical, if the version histories do not have the same identifiers, and if one version history does not contain all of the identifiers with equal or greater values of those in the other version history.

Abstract: Methods and apparatuses that enroll a wireless device into an enterprise service with a management server addressed in a management profile are described. The enrollment may grant a control of configurations of the wireless device to the management server via the management profile. In response to receiving a notification from the management server, a trust of the notification may be verified against the management profile. If the trust is verified, a network session may be established with the management server. The network session may be secured via a certificate in the management profile. Management operations may be performed for management commands received over the secure network session to manage the configurations transparently to a user of the wireless device according to the control.

Abstract: Systems and methods for synchronization including the use of a global equivalency identification datum or set of datum. A universally unique identification datum may be associated with each independently created associated data set. In some embodiments, a synchronization server software element may be responsible for maintaining synchronization for a plurality of clients, including software elements or devices. A record believed to be new by the software elements may verify that the record is actually new. In some embodiments, verification of the record's newness involves assuming that the local ID is a global identification datum and comparing that datum to the all the sets of datum that the Sync-Server knows about. The synchronization server software element may use a table to hold information for all of the records known to that element. In some embodiments these records may have been deleted in the past.

Abstract: Improved techniques and apparatus for managing data between a host device (e.g., host computer) and a media device are disclosed. The data being managed can, for example, pertain to media data for media assets. The managing of the media data thus can involve transfer of media assets between the host device and the media device. In one embodiment, the transfer of media assets between a host device and a media device can be referred to as data backup.

Abstract: An apparatus and method of synchronizing a datum between a plurality of stores uses version vectors associated with the datum in each store. Each version vector has one or more entries, and each entry has an identifier and a value. The identifier identifies a store that has modified the datum, and the value indicates a number of modifications to the datum made by the store. When synchronizing the datum between stores, the version vectors of the datum are compared to determine whether one version vector is subordinate to another version vector. The datum in the store having the subordinate version vector is then replaced with the datum having the dominant version vector. When compared, a conflict resolution by a user is required if the version vectors are not identical, if the version vectors do not have all the same identifiers, and if one version vector does not contain all of the identifiers with equal or greater values of those in the other version vector.

Abstract: Methods and apparatuses that enroll a wireless device into an enterprise service with a management server addressed in a management profile are described. The enrollment may grant a control of configurations of the wireless device to the management server via the management profile. In response to receiving a notification from the management server, a trust of the notification may be verified against the management profile. If the trust is verified, a network session may be established with the management server. The network session may be secured via a certificate in the management profile. Management operations may be performed for management commands received over the secure network session to manage the configurations transparently to a user of the wireless device according to the control.

Abstract: An apparatus and method of synchronizing a datum between a plurality of stores uses version vectors associated with the datum in each store. Each version vector has one or more entries, and each entry has an identifier and a value. The identifier identifies a store that has modified the datum, and the value indicates a number of modifications to the datum made by the store. When synchronizing the datum between stores, the version vectors of the datum are compared to determine whether one version vector is subordinate to another version vector. The datum in the store having the subordinate version vector is then replaced with the datum having the dominant version vector. When compared, a conflict resolution by a user is required if the version vectors are not identical, if the version vectors do not have all the same identifiers, and if one version vector does not contain all of the identifiers with equal or greater values of those in the other version vector.

Abstract: Methods and apparatuses that enroll a wireless device into an enterprise service with a management server addressed in a management profile are described. The enrollment may grant a control of configurations of the wireless device to the management server via the management profile. In response to receiving a notification from the management server, a trust of the notification may be verified against the management profile. If the trust is verified, a network session may be established with the management server. The network session may be secured via a certificate in the management profile. Management operations may be performed for management commands received over the secure network session to manage the configurations transparently to a user of the wireless device according to the control.

Abstract: A technique for synchronizing a datum between a plurality of stores, wherein a version history is associated with the datum in each store. The version history has one or more entries, and each entry has an identifier and a value. The identifier identifies a store that has modified the datum, and indicates a number of modifications to the datum. When synchronizing the datum between stores, the version histories of the datum are compared to determine whether one version history is subordinate to another version history. The datum having the subordinate version history is then replaced with the datum having the dominant version history. Conflict resolution is required if the version histories are not identical, if the version histories do not have the same identifiers, and if one version history does not contain all of the identifiers with equal or greater values of those in the other version history.

Abstract: An apparatus and method of synchronizing a datum between a plurality of stores is disclosed. A version history is associated with the datum in each store. The version history has one or more entries, and each entry has an identifier and a value. The identifier identifies a store that has modified the datum, and the value indicates a number of modifications to the datum made by the store. When synchronizing the datum between stores, the version histories of the datum are compared to determine whether one version history is subordinate to another version history. The datum in the store having the subordinate version history is then replaced with the datum having the dominant version history. When compared, a conflict resolution by a user is required if the version histories are not identical, if the version histories do not have all the same identifiers, and if one version history does not contain all of the identifiers with equal or greater values of those in the other version history.

Abstract: An apparatus and method of synchronizing a datum between a plurality of stores uses version vectors associated with the datum in each store. Each version vector has one or more entries, and each entry has an identifier and a value. The identifier identifies a store that has modified the datum, and the value indicates a number of modifications to the datum made by the store. When synchronizing the datum between stores, the version vectors of the datum are compared to determine whether one version vector is subordinate to another version vector. The datum in the store having the subordinate version vector is then replaced with the datum having the dominant version vector. When compared, a conflict resolution by a user is required if the version vectors are not identical, if the version vectors do not have all the same identifiers, and if one version vector does not contain all of the identifiers with equal or greater values of those in the other version vector.

Abstract: Systems and methods for synchronization including the use of a global equivalency identification datum or set of datum. A universally unique identification datum may be associated with each independently created associated data set. In some embodiments, a synchronization server software element may be responsible for maintaining synchronization for a plurality of clients, including software elements or devices. A record believed to be new by the software elements may verify that the record is actually new. In some embodiments, verification of the record's newness involves assuming that the local ID is a global identification datum and comparing that datum to the all the sets of datum that the Sync-Server knows about. The synchronization server software element may use a table to hold information for all of the records known to that element. In some embodiments these records may have been deleted in the past.

Abstract: Methods and apparatuses that enroll a wireless device into an enterprise service with a management server addressed in a management profile are described. The enrollment may grant a control of configurations of the wireless device to the management server via the management profile. In response to receiving a notification from the management server, a trust of the notification may be verified against the management profile. If the trust is verified, a network session may be established with the management server. The network session may be secured via a certificate in the management profile. Management operations may be performed for management commands received over the secure network session to manage the configurations transparently to a user of the wireless device according to the control.

Abstract: Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for backing up and restoring data to a mobile device. In general, one aspect of the subject matter described in this specification can be embodied in methods that include the actions of receiving data from a mobile device to be included in a backup, the data including data associated with one or more mobile device applications; storing the data in a backup archive; generating a backup mapping file for each of the mobile device applications, each backup mapping file identifying each file in the backup associated with the respective application; and using the backup mapping files to restore the corresponding applications to the mobile device.

Abstract: Systems and methods for synchronization including the use of a global equivalency identification datum or set of datum. A universally unique identification datum may be associated with each independently created associated data set. In some embodiments, a synchronization server software element may be responsible for maintaining synchronization for a plurality of clients, including software elements or devices. A record believed to be new by the software elements may verify that the record is actually new. In some embodiments, verification of the record's newness involves assuming that the local ID is a global identification datum and comparing that datum to the all the sets of datum that the Sync-Server knows about. The synchronization server software element may use a table to hold information for all of the records known to that element. In some embodiments these records may have been deleted in the past.

Abstract: A system and method are disclosed for synchronizing data between devices and more particularly for synchronizing data between a plurality of peer-to-peer devices in a decentralized environment where no one device stores the most “recent” or “true” version of the data. Embodiments of the invention relate concepts of discovering synchronizing peers, communication between peers using special techniques, and using a way station concept as an aid for both discovery and synchronization between peers that are not simultaneously available.

Abstract: A system and method are disclosed for synchronizing data between devices and more particularly for synchronizing data between a plurality of peer-to-peer devices in a decentralized environment where no one device stores the most “recent” or “true” version of the data. Embodiments of the invention relate concepts of discovering synchronizing peers, communication between peers using special techniques, and using a way station concept as an aid for both discovery and synchronization between peers that are not simultaneously available.

Abstract: An apparatus and method of synchronizing a datum between a plurality of stores is disclosed. A version history is associated with the datum in each store. The version history has one or more entries, and each entry has an identifier and a value. The identifier identifies a store that has modified the datum, and the value indicates a number of modifications to the datum made by the store. When synchronizing the datum between stores, the version histories of the datum are compared to determine whether one version history is subordinate to another version history. The datum in the store having the subordinate version history is then replaced with the datum having the dominant version history. When compared, a conflict resolution by a user is required if the version histories are not identical, if the version histories do not have all the same identifiers, and if one version history does not contain all of the identifiers with equal or greater values of those in the other version history.