Synchronizing endpoint data stores having disparate schemas
Abstract
Synchronizing data between multiple endpoint data stores that have disparate schemas is accomplished in a manner that reduces complexity. Each endpoint data store has an associated local schema that orders data into one or more fields. A synchronization server is disposed between the endpoints and keeps the multiple endpoints synchronized without the endpoints having to understand the various local schemas. A virtual schema is generated based on a set-intersection of the local schemas. The virtual schema maps a field in one local schema to a field in another local schema. Data is synchronized between the endpoint data stores using the virtual schema.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A method for synchronizing data between endpoint data stores, each endpoint data store having a local schema associated with the data store that orders data into one or more fields, comprising:
generating a virtual schema based on a first local schema and a second local schema, wherein the virtual schema mapping a field in the first local schema to a field in the second local schema; and synchronizing data between the endpoint data stores using the virtual schema.
2 . The method of claim 1 , further comprising:
performing a set-intersection on the first local schema and the second local schema.
3 . The method of claim 1 , further comprising:
retrieving the first local schema and the second local schema.
4 . The method of claim 3 , wherein each of the first local schema and the second local schema includes a respective set of field names and data types, and each field name has an associated list of synonyms for the field name.
5 . The method of claim 1 , wherein said synchronizing includes:
receiving a record from a first endpoint data store, the record being ordered according to the first local schema; processing the record based on the virtual schema so as to prepare an actual record that can be used with a second local schema of a second endpoint data store; and updating the second endpoint data store based on the actual record.
6 . The method of claim 5 , wherein said updating includes:
transporting the actual record to the second endpoint data store.
7 . The method of claim 5 , wherein said synchronizing is performed responsive to a triggering event.
8 . The method of claim 7 , wherein the triggering event is a synchronization request.
9 . The method of claim 8 , wherein the virtual schema maps data between the first endpoint data store and the second endpoint data store.
10 . The method of claim 1 , wherein each of the first local schema and the second local schema defines a set of field names and data types, and each field name has an associated list of synonyms for the field names, and further comprising:
performing a set-intersection on the first local schema and the second local schema.
11 . The method of claim 10 , wherein said performing a set-intersection includes resolving field names using the synonyms.
12 . A synchronization server for synchronizing data between endpoints, each endpoint having a local schema associated therewith, the synchronization server configured to:
(i) retrieve the local schema from each respective endpoint, each local schema orders the data into one or more fields, wherein the one or more fields include pairs of field names and data types, (ii) perform a set-intersection on the local schemas retrieved from the respective endpoints, (iii) generate a virtual schema calculated from said set-intersection, the virtual schema is used in synchronization to tailor the data for transport among the endpoints.
13 . The synchronization server of claim 12 , wherein each field name has an associated list of synonyms for the field name.
14 . The synchronization server of claim 13 , wherein the synchronization server is configured to resolve field names using the synonyms.
15 . The synchronization server of claim 14 , wherein the synchronization server is configured to store the virtual schema, and upon synchronization, retrieve data and process the data based on the virtual schema.
16 . The synchronization server of claim 12 , wherein the synchronization server is configured to communicate with a portable wireless device at each endpoint.
17 . The synchronization server of claim 16 , wherein the data can be stored within the portable wireless device.
18 . The synchronization server of claim 12 , wherein:
some of the fields of the local schemas are related by having similar content.
19 . The synchronization server of claim 12 , comprising:
a discoverer configured to retrieve local schemas from the endpoints.
20 . The synchronization server of claim 19 , further comprising:
a set-intersection performer configured to perform set-intersection on retrieved local schemas.Join the waitlist — get patent alerts
Track US2015331924A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.