会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 6. 发明授权
    • 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.
    • 可以解决同步期间检测到的更新 - 删除冲突,有利于更新或删除。 解决冲突有利于删除结果,在一个副本上删除的实体在所有选定的副本上被删除。 解决有利于更新的冲突导致更新的实体(包括从一个层次结构移动到另一个层次的实体)在所有选定的副本上复制。 为了解决有利于更新的冲突,删除被视为错误地报告。 被删除的实体以更新实体的形式复活。 更改版本信息保留在所有副本中。 更新 - 删除冲突可以根据各种解决方案策略进行解析,例如更新赢,删除胜利,特定设备上发生的更改胜利,以及最近的事件胜利。
    • 7. 发明申请
    • 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.
    • 可以从数据存储中删除墓碑,而不会导致数据损坏。 放置在被遗忘的知识列表中的墓碑可以相互比较和/或墓碑表中的项目,并且当代表随后删除的项目的墓碑是现存时被删除。 此外,创建数据库版本信息可以与数据库项一起保存,数据库可以在数据库同步时记录数据库版本信息。 如果同步数据库发现它没有的项目,但与该项目相关联的创建数据库版本信息反映了同步数据库“应该”具有该项目,则可以推断该项目随后被删除,并且项目复活 可以防止。
    • 8. 发明授权
    • 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,允许每个决议识别在进行特定更改时复制品知道什么。 使用知识产权值用于检测复制期间的冲突。
    • 9. 发明授权
    • 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接口)。 其他数据字段专门用于包含关于使用另一传送机制传输相同特定类型的数据段的信息。 当一个模块要传输一个数据段时,该模块会使统一的数据结构根据所需的传输机制进行更改。