会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 12. 发明申请
    • 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 )具有更小和更少的繁琐的合作伙伴密钥。
    • 13. 发明授权
    • Systems and methods for replicating data stores
    • 用于复制数据存储的系统和方法
    • US07440981B2
    • 2008-10-21
    • US10631591
    • 2003-07-31
    • Lev NovikIrena HudisDouglas B. TerryAshish ShahSanjay AnandYunxin Wu
    • Lev NovikIrena HudisDouglas B. TerryAshish ShahSanjay AnandYunxin Wu
    • G06F17/30
    • G06F17/30581Y10S707/99953Y10S707/99955
    • Systems and methods for replicating replicas in a sync community. Each replica in the sync community stores knowledge that represents changes the replica is aware of. Because each replica has its own knowledge, each replica does not need to know how many replicas are in the sync community or the topology of the sync community. By sending the knowledge with a request for changes, a replicating replica can enumerate the changes to replicate by comparing its knowledge with the received knowledge. After replication, the knowledge is updated. Knowledge may also include made-with-knowledge change IDs that permit each resolution to identify what a replica was aware of when a particular change was made. The made-with-knowledge values are used to detect conflicts during replication.
    • 在同步社区中复制副本的系统和方法。 同步社区中的每个副本都存储表示副本所注意到的更改的知识。 由于每个副本都有自己的知识,因此每个副本不需要知道同步社区中多少副本或同步社区的拓扑。 通过向知识发送更改请求,复制副本可以通过将其知识与接收到的知识进行比较来枚举复制的更改。 复制后,知识将被更新。 知识也可以包括知识变更ID,允许每个决议识别在进行特定更改时复制品知道什么。 使用知识产权值用于检测复制期间的冲突。
    • 14. 发明申请
    • Multi-master database synchronization without loss of convergence
    • 多主数据库同步不失收敛
    • US20070299887A1
    • 2007-12-27
    • US11474245
    • 2006-06-23
    • Lev NovikYunxin WuIrena Hudis
    • Lev NovikYunxin WuIrena Hudis
    • G06F17/30
    • G06F17/30578
    • Tombstones can be removed from a data store without data corruption. Tombstones placed into a forgotten knowledge list can be compared against each other and/or items in a tombstone table, and deleted when tombstones representing subsequently deleted items are extant. Also, creation database version information can be kept along with database items, and databases can record database version information when they synchronize. If a synchronizing database discovers an item that it does not have, but the creation database version information associated with the item reflects that the synchronizing database “should” have the item, then it can be inferred that the item was subsequently deleted, and item resurrection can be prevented.
    • 可以从数据存储中删除墓碑,而不会导致数据损坏。 放置在被遗忘的知识列表中的墓碑可以相互比较和/或墓碑表中的项目,并且当代表随后删除的项目的墓碑是现存时被删除。 此外,创建数据库版本信息可以与数据库项一起保存,数据库可以在数据库同步时记录数据库版本信息。 如果同步数据库发现它没有的项目,但与该项目相关联的创建数据库版本信息反映了同步数据库“应该”具有该项目,则可以推断该项目随后被删除,并且项目复活 可以防止。
    • 15. 发明授权
    • Uniform transfer of data independent of the transfer mechanism
    • 统一传输数据,独立于传输机制
    • US07568204B1
    • 2009-07-28
    • US10175935
    • 2002-06-20
    • Irena HudisAlan Geoffrey BoshierLev NovikYunxin Wu
    • Irena HudisAlan Geoffrey BoshierLev NovikYunxin Wu
    • G06F9/46
    • G06F9/54Y10S707/99931
    • A uniform data structure contains a number of data fields. Some of the data fields are dedicated to contain information concerning the transfer of a data segment of a particular type (such as an XML segment) using one particular transfer mechanism (such as transferring as a string or DOM object, or transfer using an interface such as ISAXContentHandler, ITextSource, ITextSink, or IDOMSink interfaces). Other data fields are dedicated to contain information concerning the transfer of data segments of the same particular type using another transfer mechanism. When a module is to transfer a data segment, the module will cause the unified data structure to be altered as appropriate for the desired transfer mechanism.
    • 统一的数据结构包含多个数据字段。 一些数据字段专门用于包含有关使用一种特定传输机制(例如转换为字符串或DOM对象,或使用接口等传输的特定类型的数据段(例如XML段))的传输的信息 作为ISAXContentHandler,ITextSource,ITextSink或IDOMSink接口)。 其他数据字段专门用于包含关于使用另一传送机制传输相同特定类型的数据段的信息。 当一个模块要传输一个数据段时,该模块会使统一的数据结构根据所需的传输机制进行更改。