News Column

"Selective Data Synchronization and Transfer to Remote Distributed Database Servers" in Patent Application Approval Process

August 19, 2014



By a News Reporter-Staff News Editor at Information Technology Newsweekly -- A patent application by the inventors Jiang, Oscar L. (Rosemead, CA); Pasion, Jason A. (San Diego, CA), filed on January 28, 2014, was made available online on August 7, 2014, according to news reporting originating from Washington, D.C., by VerticalNews correspondents.

This patent application is assigned to General Instrument Corporation.

The following quote was obtained by the news editors from the background information supplied by the inventors: "The present invention relates to providing identity data from a central database server to remote distributed database servers. More particularly, the present invention relates to synchronization of the distributed identity data between the central server and all the remote servers.

"In previous systems, identity data is loaded to all remote distributed database servers so each server has the same identity data. There is no prior knowledge on which database server gets which identity data, so it is important that the identity data loaded to central database server is in synch with each distributed database server.

"Synchronizing identity data across all remote distributed database servers with the central database server, however, is difficult for the following reasons:

"5. Identity data which are modified in the central database server must be synchronized to all applicable remote distributed database servers. This would be difficult to do without a robust solution to synchronize data from the central database to each remote database server.

"U.S. patent application Ser. No. 11/947,902 (Attorney Docket No. BCS04382) entitled 'System and Method for Dynamic and On-Demand Data Transfer and Synchronization between Isolated Networks' describes a system to synchronize identity data. The synchronization method of the '902 patent application, however, uses human interaction; the synchronized data is downloaded to a file and then uploaded to the database. The synchronization method of the '902 application is further designed for isolated networks."

In addition to the background information obtained for this patent application, VerticalNews journalists also obtained the inventors' summary information for this patent application: "The system disclosed solves problems for a system which requires synchronization of large data over a WAN and unstable network. It also solves synchronizing a subset of the data within a table to only applicable remote distributed database servers. The system enables PKI provisioning for Set Top Boxes being produced in a factory, as well as other electronic components being produced in a factory.

"This disclosed system provides a solution to resolve the synchronization of identity data from a central database server to distributed database servers. The solution includes a method to synchronize identity data to the central database server and distributed servers based on identity type assignments allocated to a factory. This solution can be applied to any system separate from a single factory which has similar challenges with replication over a WAN including network instability, strict security requirements, and syncing selective identity data.

"The following steps provide the example showing how a system according to the present invention is provided with identity data.

"1. For the first step, the configuration manager assigns different identity data types to the factories which may manufacture the devices which will need Identity Data (ID). Each identity data is associated with a device and will be required to be loaded during the manufacturing time. Since it is not known which factory will have the device, the identity data must be synced to the factories where the device is built.

"2. In a second step, the ID Loader receives a file containing new identity data and loads it to the central database server.

"3. In a third step, once the records are loaded to the central database server, a record of the file information is created and stored in a file history table.

"4. In a fourth step, once the file is loaded and the file history table is updated, an identity data loaded event triggers a Factory Synchronizer and Loader (FSL) to process the event. The FSL is triggered to create jobs based on the event table. Once the FSL is triggered to create a job, the steps a)-d) that the FSL follows are described as follows:

"a) the FSL determines the records associated with a File ID from the Identity Data table.

"b) the FSL determines the identity data type(s) associated with records from 4a.

"c) the FSL determines the factory locations associated with data type.

"d) Based on information from items a)-c), the FSL creates two 'LOAD DATA' jobs, and sets the event status to COMPLETED.

"5. In a fifth step, the FSL will execute each 'Pending' job and load the identity data to one of the primary remote database servers in a factory. If a job fails, the FSL will continue on to the next job and retry later. Once a job is completed, the job status will be updated to COMPLETED in the Job Detail Table of FIG. 6 so that FSL will not execute the same job twice.

"6. In a sixth step, the identity data is synchronized in the central data base with the remote database server in a location of one of the factories. Local database synchronization can be used in a factory location because the network within a LAN is much more stable than a WAN. There could be up to M number of database servers in a single factory location which will be kept in sync with the primary database server.

"Different jobs can be triggered by the above steps. In one example, instead of identity data, configuration data can be maintained and synchronized with a central database that is running in remote servers.

"Further, identity data can be incorrect due to numerous reasons that require modification. Once any incorrect identity data is distributed to all remote database servers, it must be corrected everywhere. The correction will happen in central database server, and the changes will be synchronized to all remote distributed database servers using the process described above as implemented by the FSL.

"Further situations can require application of the above steps. For example, a new configuration manager can be added to a factory, and will need identity data loaded that is associated with the factory and synchronized with all remote servers. Further, the FSL can occasionally fail to synchronize the data from central to the remote database servers, and the FSL will need to reload and synchronize the identity data to recover.

BRIEF DESCRIPTION OF THE DRAWINGS

"Further details of the present invention are explained with the help of the attached drawings in which:

"FIG. 1 shows a Configuration Table used for a system of a first example embodiment of the present invention that provide an example association between factories and identity data types that are assigned by a configuration manager;

"FIG. 2 shows an Identity Data Table used in the first example embodiment of the present invention;

"FIG. 3 shows a File History Table used in the first example embodiment of the present invention;

"FIG. 4 shows an Event Table used in the first example embodiment of the present invention;

"FIG. 5 shows a Job Table used in the first example embodiment of the present invention;

"FIG. 6 shows a Job Detail Table use in the first example embodiment of the present invention;

"FIGS. 7-11 show tables of data used in accomplishing configuration data synchronization according to an example embodiment of the present invention;

"FIGS. 12-16 show tables of data used in synchronization of changed identity data according to embodiments of the present invention;

"FIGS. 17-21 show tables of data used in accomplishing addition of a new remote database server according to embodiments of the present invention;

"FIGS. 22-23 show tables of data used for accomplishing synchronization after a failure occurs according to embodiments of the present invention;

"FIG. 24 shows a table indicating that multiple FSLs can be used according to embodiments of the present invention; and

"FIG. 25 shows a block diagram of a system of components used in embodiments of the present invention."

URL and more information on this patent application, see: Jiang, Oscar L.; Pasion, Jason A. Selective Data Synchronization and Transfer to Remote Distributed Database Servers. Filed January 28, 2014 and posted August 7, 2014. Patent URL: http://appft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&u=%2Fnetahtml%2FPTO%2Fsearch-adv.html&r=908&p=19&f=G&l=50&d=PG01&S1=20140731.PD.&OS=PD/20140731&RS=PD/20140731

Keywords for this news article include: Information Technology, General Instrument Corporation, Information and Data Tabulation, Information and Data Synchronization.

Our reports deliver fact-based news of research and discoveries from around the world. Copyright 2014, NewsRx LLC


For more stories covering the world of technology, please see HispanicBusiness' Tech Channel



Source: Information Technology Newsweekly


Story Tools






HispanicBusiness.com Facebook Linkedin Twitter RSS Feed Email Alerts & Newsletters