会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 4. 发明申请
    • Resolving update-delete conflicts
    • 解决更新 - 删除冲突
    • US20070282914A1
    • 2007-12-06
    • US11444180
    • 2006-05-31
    • Muhunthan SivapragasamDon CaoIrena HudisLev NovikTomas TaliusVivek J. JhaveriYunxin WuAnn Tang
    • Muhunthan SivapragasamDon CaoIrena HudisLev NovikTomas TaliusVivek J. JhaveriYunxin WuAnn Tang
    • G06F17/30
    • G06F17/30578
    • Update-delete conflicts detected during synchronization can be resolved in favor of the update or the deletion. Resolving the conflict in favor of the deletion results in the entity deleted on one replica being deleted on all selected replicas. Resolving the conflict in favor of the update results in the updated entity, which includes an entity moved from one hierarchy to another, being replicated on all selected replicas. To resolve the conflict in favor of the update, the deletion is treated as though it were reported erroneously. The deleted entity is resurrected in the form of the updated entity. Change version information is maintained in all replicas. Update-delete conflicts are resolvable in accordance with various resolution policies such as the update wins, deletion wins, changes occurring on a particular device wins, and most recent event wins, for example.
    • 可以解决同步期间检测到的更新 - 删除冲突,有利于更新或删除。 解决冲突有利于删除结果,在一个副本上删除的实体在所有选定的副本上被删除。 解决有利于更新的冲突导致更新的实体(包括从一个层次结构移动到另一个层次的实体)在所有选定的副本上复制。 为了解决有利于更新的冲突,删除被视为错误地报告。 被删除的实体以更新实体的形式复活。 更改版本信息保留在所有副本中。 更新 - 删除冲突可以根据各种解决方案策略进行解析,例如更新赢,删除胜利,特定设备上发生的更改胜利,以及最近的事件胜利。
    • 5. 发明授权
    • Resolving update-delete conflicts
    • 解决更新 - 删除冲突
    • US07769727B2
    • 2010-08-03
    • US11444180
    • 2006-05-31
    • Muhunthan SivapragasamDon CaoIrena HudisLev NovikTomas TaliusVivek J. JhaveriYunxin WuAnn Tang
    • Muhunthan SivapragasamDon CaoIrena HudisLev NovikTomas TaliusVivek J. JhaveriYunxin WuAnn Tang
    • G06F7/00G06F15/16H04W4/00
    • G06F17/30578
    • Update-delete conflicts detected during synchronization can be resolved in favor of the update or the deletion. Resolving the conflict in favor of the deletion results in the entity deleted on one replica being deleted on all selected replicas. Resolving the conflict in favor of the update results in the updated entity, which includes an entity moved from one hierarchy to another, being replicated on all selected replicas. To resolve the conflict in favor of the update, the deletion is treated as though it were reported erroneously. The deleted entity is resurrected in the form of the updated entity. Change version information is maintained in all replicas. Update-delete conflicts are resolvable in accordance with various resolution policies such as the update wins, deletion wins, changes occurring on a particular device wins, and most recent event wins, for example.
    • 可以解决同步期间检测到的更新 - 删除冲突,有利于更新或删除。 解决冲突有利于删除结果,在一个副本上删除的实体在所有选定的副本上被删除。 解决有利于更新的冲突导致更新的实体(包括从一个层次结构移动到另一个层次的实体)在所有选定的副本上复制。 为了解决有利于更新的冲突,删除被视为错误地报告。 被删除的实体以更新实体的形式复活。 更改版本信息保留在所有副本中。 更新 - 删除冲突可以根据各种解决方案策略进行解析,例如更新赢,删除胜利,特定设备上发生的更改胜利,以及最近的事件胜利。
    • 8. 发明授权
    • Systems and methods for the utilization of metadata for synchronization optimization
    • 利用元数据进行同步优化的系统和方法
    • US08046424B2
    • 2011-10-25
    • US10927726
    • 2004-08-27
    • Lev NovikTomas TaliusYunxin WuShaoyu Zhou
    • Lev NovikTomas TaliusYunxin WuShaoyu Zhou
    • G06F15/167G06F15/16G06F7/00G06F17/00
    • G06F17/30176G06F17/30575Y10S707/99955
    • Various embodiments of the present invention are directed to synchronization utilizing one or more optimizations through the utilization of metadata. For several embodiments of the present invention, one method for optimizing synchronization is to reduce the overhead required for said synchronization by having each peer only tracking changes for itself and other peers within its change community (or communities) (a.k.a., “Intra-Community-Only Change Tracking Optimization”). For certain embodiments of the present invention, another method for optimizing synchronization is to not create synchronization overhead until required. For numerous embodiments of the present invention, yet another method for optimizing synchronization is to minimize redundant use of a partner's unique global ID—a large and cumbersome number—and to instead maintain a table that cross-references each partner (and its unique global ID) with a smaller and much less cumbersome partner key.
    • 本发明的各种实施例涉及通过利用元数据利用一个或多个优化的同步。 对于本发明的几个实施例,用于优化同步的一种方法是通过使每个对等体仅跟踪其变化社区(或社区)(或社区)内的其他对等体(也称为“共同体内社区”)来减少所述同步所需的开销, 只有更改跟踪优化“)。 对于本发明的某些实施例,用于优化同步的另一种方法是在需要之前不产生同步开销。 对于本发明的许多实施例,用于优化同步的另一种方法是最小化伙伴的唯一全局ID(冗余和繁琐的数量)的冗余使用,并且替代地维护交叉引用每个伙伴的表(及其唯一的全局ID )具有更小和更少的繁琐的合作伙伴密钥。
    • 10. 发明申请
    • Systems and methods for the utilization of metadata for synchronization optimization
    • 利用元数据进行同步优化的系统和方法
    • US20050256907A1
    • 2005-11-17
    • US10927726
    • 2004-08-27
    • Lev NovikTomas TaliusYunxin WuShaoyu Zhou
    • Lev NovikTomas TaliusYunxin WuShaoyu Zhou
    • G06F13/00G06F17/30
    • G06F17/30176G06F17/30575Y10S707/99955
    • Various embodiments of the present invention are directed to synchronization utilizing one or more optimizations through the utilization of metadata. For several embodiments of the present invention, one method for optimizing synchronization is to reduce the overhead required for said synchronization by having each peer only tracking changes for itself and other peers within its change community (or communities) (a.k.a., “Intra-Community-Only Change Tracking Optimization”). For certain embodiments of the present invention, another method for optimizing synchronization is to not create synchronization overhead until required. For numerous embodiments of the present invention, yet another method for optimizing synchronization is to minimize redundant use of a partner's unique global ID—a large and cumbersome number—and to instead maintain a table that cross-references each partner (and its unique global ID) with a smaller and much less cumbersome partner key.
    • 本发明的各种实施例涉及通过利用元数据利用一个或多个优化的同步。 对于本发明的几个实施例,用于优化同步的一种方法是通过使每个对等体仅跟踪其变化社区(或社区)(或社区)内的其他对等体(也称为“共同体内社区”)来减少所述同步所需的开销, 只有更改跟踪优化“)。 对于本发明的某些实施例,用于优化同步的另一种方法是在需要之前不产生同步开销。 对于本发明的许多实施例,用于优化同步的另一种方法是最小化伙伴的唯一全局ID(冗余和繁琐的数量)的冗余使用,并且替代地维护交叉引用每个伙伴的表(及其唯一的全局ID )具有更小和更少的繁琐的合作伙伴密钥。