TWI778433B - Data management system and method for data synchronization - Google Patents

Abstract

A data management system and a method for data synchronization are provided. The system provides a data-management platform with a database, and the system includes one or more subsystems. Each of the subsystems performs a data-retrieving program for retrieving data via one or more channels, and a data-synchronization program for synchronizing data with the data-management platform. The data-management platform operates a data-synchronization method, by which the platform receives data from one of the subsystems and obtains data attribute after analyzing the data. The data attribute is such as a source of the data, importance of the data, time to create the data, and its independence, dependence and its grouping. After comparing with the data stored in the database of the platform, the platform determines whether or not the data needs to be updated synchronously according to the data attribute and the comparison result.

Description

Data management system and data synchronization method

The specification proposes a data management method, especially a data management system that can integrate data from different departments within an organization and a method for data synchronization in it.

Various official and non-governmental organizations (such as companies, banks, schools, and governments) will generate a large amount of documents when performing tasks and dealing with affairs, including videos, patterns, sounds and texts, making archives management a necessary and important topic .

For example, take financial institutions as an example, such as banks, financial institutions have different business departments and systems, such as insurance departments, mobile banking, online banking, check-in system, wealth management (wealth management) system, credit card department, customer service department Etc., each business department has its own file data system, and also maintains the data of its own customers, and in particular, the customer data of financial institutions has different data strengths for different business departments.

Because the data used by various departments in an institution may have commonalities under certain circumstances, for example, the customer data maintained by various departments in a financial institution should be consistent with each other, but there is a lack of data consistency management and data synchronization methods, making data It may be outdated and not updated, or even if it is the same financial institution, customers still need to refill the information when applying for services from different departments, causing unnecessary trouble and trouble.

In view of the fact that the data of the same customer in different departments in an organization should have commonality and consistency, the disclosure document proposes a data management system and a data synchronization method therein, so that different departments can maintain consistent data for the same customer, and When dealing with specific transactions, it is also possible to share the same customer's data and allow the data to be updated synchronously.

According to an embodiment, the disclosed data management system provides a data management platform in which a database is provided, the system includes one or more subsystems, and each subsystem executes a data acquisition program for receiving data through one or more channels , and execute a data synchronization program for synchronizing data with the data management platform.

In the data synchronization method running in the data management platform, a piece of data transmitted by one of the subsystems is first received, and the attribute of the data can be obtained after parsing the data. In one embodiment, the attribute of the data is the At least include the business department to which the subsystem belongs, the importance of the data, the change time of the data, and the independence, interdependence and grouping of one or more items in the data. Then, compare the corresponding data in the database to generate a comparison result, so as to determine whether the corresponding data in the database in the data management platform or one or more of them needs to be updated synchronously according to the attributes of the data and the comparison result. project.

Wherein, when it is determined that the corresponding data or one or more items in the database on the data management platform need to be updated synchronously, the corresponding data in the database is updated synchronously according to the comparison result. At the same time, the program in the data management platform also determines whether to update the corresponding data in other subsystems synchronously. When judging that it needs to be updated to other subsystems, a permission check is also performed to confirm whether other subsystems have the permission to receive data synchronization, including the permission to write items in the synchronization data.

Preferably, the data management platform is a platform operated by a financial institution, and operates as a main system for managing the data provided by the one or more subsystems. Thus, the subsystem can be an enterprise in the financial institution. Departments receive data through counters, online banking, form filling, customer service systems, or wealth management specialists, etc., and the data attributes will be added to these sources.

For a further understanding of the features and technical content of the present invention, please refer to the following detailed descriptions and drawings of the present invention. However, the drawings provided are only for reference and description, and are not intended to limit the present invention.

The following are specific embodiments to illustrate the embodiments of the present invention, and those skilled in the art can understand the advantages and effects of the present invention from the content disclosed in this specification. The present invention can be implemented or applied through other different specific embodiments, and various details in this specification can also be modified and changed based on different viewpoints and applications without departing from the concept of the present invention. In addition, the drawings of the present invention are merely schematic illustrations, and are not drawn according to the actual size, and are stated in advance. The following embodiments will further describe the related technical contents of the present invention in detail, but the disclosed contents are not intended to limit the protection scope of the present invention.

It should be understood that although terms such as "first", "second" and "third" may be used herein to describe various elements or signals, these elements or signals should not be limited by these terms. These terms are primarily used to distinguish one element from another element, or a signal from another signal. In addition, the term "or", as used herein, should include any one or a combination of more of the associated listed items, as the case may be.

The disclosure document discloses a data management system and a data synchronization method, which can be applied in a specific organization. Through a data management platform proposed by the data management system, the need for data synchronization between the organization and its subordinate departments can be managed. In particular, in view of the fact that the data of the same client in different departments of an organization should have commonality and consistency, but the data sources are different, even if it comes from the same client, there may be differences between the data, so the disclosure The book proposes a data management system and a data synchronization method therein, which allows different departments to maintain consistent data for the same customer, and can also share customer data when dealing with specific transactions, and allow data to be effectively synchronized and updated.

FIG. 1 shows a schematic diagram of an embodiment of a data management system. The figure shows a data management platform 100 proposed by the data management system. The data management platform 100 is provided with a database 101 in which various data are stored. The data management platform 100 is connected to one or more other subsystems through the network 10, as shown in the figure Subsystem one 111 , subsystem two 112 and subsystem three 113 .

According to an embodiment, the data management system is applied in a financial institution, and the proposed data management platform 100 is used to manage customer data generated by various business departments of the financial institution. Financial institutions (such as banks) have different business departments (including service systems), such as insurance departments, mobile banking, Internet banking, counter departments (financial affairs at the counter), wealth management departments, credit card departments, customer service departments, etc. Each business department has its own system and maintains the data of its own customers. The customer data has different data strengths for different business departments. However, when there is a specific demand, if the data between departments is different, or if the customer updates the data in a specific department, other departments are not aware of it, which will make the data inconsistent, and may cause service problems or information preservation. Therefore, through the proposed data management platform 100, different levels of data can be given according to the data maintained by each department (ie subsystem), as well as according to the attributes of the data, the authority of the department, the source of the data, the time of data update, etc. Synchronous processing.

The database 101 in the data management platform 100 is used to store the synchronously stored data, so that each subsystem 111, subsystem two 112 and subsystem three 113 can obtain the latest data from the data management platform 100 when required , and each subsystem 1 111, subsystem 2 112 and subsystem 3 113 will also obtain data through their specific channels. If the data is different from the database 101 of the data management platform 100, it can also be processed according to the attributes of the data such as intensity and time. Synchronization and supplementation are used to maintain the correctness and integrity of the data in the data management platform 100. Moreover, the data management platform 100 can also be used to synchronize the data of the database 101 to other subsystems, so as to maintain the data of the entire system to be updated synchronously. It can effectively avoid the problems caused by different departments in traditional institutions maintaining their own data.

According to an embodiment, the data management platform 100 may be a platform run by a financial institution, with a server host and software therein to implement a main system for managing data provided by one or more subsystems. The data management platform 100 is provided with a management interface 103 , which allows the administrator to view the data and data processing settings currently stored in the database 101 in the system through the management interface 103 , and maintain the operation of the server host.

FIG. 2 shows a functional block diagram of the main system and the subsystem applicable to the data synchronization method. In the application of the system in a financial institution, the main system in the financial institution is run by the data management platform 200, and the subsystem 20 may be the main system in the financial institution. a business department.

The data management platform 200 is a platform implemented by a server host, and is connected to the subsystem 20 through a network. According to the function, it may include a data receiving unit 211 for receiving the data transmitted by the subsystem 20. Taking a financial institution as an example, it is Customer data; including the data analysis unit 213, which is used to analyze the received data, parse out the attributes of the data through the interpretation of the data content and the pre-set data classification, and can use the data annotation unit 215 to annotate each entry according to the set data classification Data, such as setting labels describing the attributes of the data through a file or metadata of the data, which can include marking the customer's identity, setting labels for the data of different business departments, thereby marking the customer as important, general, and whether it is a key marketing customer , the level of risk, etc. The label forms the basis for the processing program running in the data management platform 200 to determine the attribute of the data. For example, the label can record the name of the data, the source of the data (such as a certain subsystem (business department)), and the creation time (which can be read from the self-interpretation data) , and the update time (which can be read out from the interpretation data), etc., so that the software program running in the data management platform 200 judges the independence, dependency and grouping of each piece of data or its items. .

When each piece of data obtained by a subsystem is annotated, such as adding a tag or updating a tag, the data synchronization unit 217 mainly uses the annotation to perform subsequent processing according to the annotation, and the data synchronization unit 217 determines whether to update the data in the database unit 219. data, or whether to synchronize to other subsystems.

A subsystem 20 is shown in the figure, which can be realized by a server host, wherein a customer database 205 is provided for storing data received from customers through one or more channels, and various data attributes 251 can be obtained by analyzing the data through software methods, Such as data name, label, data source, creation time, update time, etc., are also stored in the customer database 205.

Likewise, the subsystem 20 implements various functions by cooperating with circuits and software programs, and also has a data synchronization unit 201 for synchronizing data with the data management platform 200 . The subsystem 20 is provided with a data acquisition unit 203, which can receive customer data through one or more channels. Take a business department of a financial institution as an example, such as a credit card department, through the counter 231, online banking 232, filling form 233, The customer service system 234 and the wealth management specialist 235 obtain customer information. In this way, when the customer data is sent to the data management platform 200, the data attributes can be obtained through analysis, such as the business department to which the subsystem 20 belongs, the importance of the customer data, the change time of the customer data, and one or more of the customer data. Independence, dependencies, and grouping of projects. In particular, in the process of data analysis, the system will set the dependent group relationship according to the field correlation in the data provided by the customer, that is, the above-mentioned independence, interdependence, and grouping, according to the data of each subsystem (such as each business department) Correctness sets the priority of the system and the range of allowable changes, and establishes the data modification criteria with the sequence of change times, that is, the Golden Rule.

It is mentioned here that the independence of the data means that some data items are irrelevant to other people, such as the customer's name, education, ID number, address, etc. These data can be updated individually, with other The data is irrelevant. Therefore, when the independent data is generated, it can be updated and synchronized according to the change time. The dependency of the data indicates that the data (or its items) has a linkage relationship with other data (or projects), so when one of the items changes, the other related data should also be updated. For example, a company The ID number, name and date of birth of the person in charge should be related. If there is any update, they should be updated together. The group nature of the information is that some information is related to each other, such as the customer and his guarantor, relatives, etc. The information is a group change; information such as the relationship or shareholding ratio of a certain beneficial beneficiary under the company is updated, and other beneficial beneficiaries may also need to be updated simultaneously. Among them, the data with dependencies and groups will be updated together, not only one of them.

Further, when the data management platform 200 obtains the data transmitted by the subsystem 20, the data will affect the importance of the data itself due to the characteristics of the subsystem 20. Taking a business department of a financial institution as an example, the customer data obtained by the subsystem 20. Attributes include at least the business division to which the subsystem 20 belongs, the importance of the customer data, the time of change derived from the data metadata, and the independence, dependencies, and grouping of one or more items in the customer data.

Next, when the data management platform 200 synchronously updates the corresponding data in the database, it also determines whether to synchronously update the corresponding data in other subsystems. For example, taking a financial institution as an example, when a customer changes his financial certificate in the credit card department (a certain subsystem), the data is also synchronized to the data management platform 200, and the software program determines that the data update should also be updated to the credit department synchronously. (another subsystem), ie attributes based on this data are also synchronized to the credit department. Wherein, when the synchronization is updated to other subsystems, a permission check is also performed to confirm whether other subsystems have the permission to receive data synchronization, and the data synchronization is performed only after confirmation.

FIG. 3 shows an example of the flow of data synchronization between the client 31 , the subsystem 32 and the data management platform 33 . This example shows that the system can confirm the updated content with the client according to the difference.

First, the client 31 provides data to the subsystem 32, and the subsystem 32 receives the data provided by the client 31 through a certain channel (step S301). After receiving, the subsystem 32 can confirm the data with the client 31 (step S303). According to an embodiment, when the subsystem 32 or the data management platform 33 receives the customer data and updates the corresponding data in the database synchronously, it also determines that the data is general customer data or data that needs to be compulsorily synchronized. In one case, if it is general customer data, the subsystem 32 then transmits the customer data to the data management platform 33 (step S305 ), and the data management platform 33 synchronizes the data to other subsystems 34 (step S307 ). During this process, according to an embodiment, the data management platform 33 can analyze the data to obtain the attributes of the data, and compare the corresponding data in the database to generate a comparison result. Therefore, according to the attributes of the data and The comparison results determine whether the corresponding data or one or more items in the database need to be updated synchronously. In practice, taking a financial institution such as a bank as an example, the bank clerk operates the management interface in the subsystem 32 to confirm the data with the customer 31 with the received data, and the confirmed data is returned to the subsystem 32 for modification, and then the customer data is transmitted after the modification. Go to the data management platform 33, perform the data comparison and operation described in the above steps in the data management platform 33, and generate and provide the data comparison result to other subsystems 34, ie, step S307).

In another case, if the customer 31 confirms that the information is the latest and correct information at present and agrees to update the information of the whole bank uniformly, after the subsystem 32 and the customer 31 confirm the correctness of the data, it is determined that the information needs to be updated forcibly , the subsystem 32 can forcibly update (synchronize) the data to the data management platform 33 (step S309 ), and the data management platform 33 will forcibly update the data and overwrite and notify other subsystems 34 to synchronously update the entire bank data (step S311 ). For example, when the customer 31 visits the counter to change information such as e-mail, mobile phone number, etc., the data of the whole bank can be updated synchronously after the judgment of the data management platform 33.

What's more, in the data management platform 33, after the update is synchronized to other subsystems (as shown in the subsystem 34), the client 31 can also be notified of the change of relevant data by various communication methods (such as e-mail, SMS, etc.) (step S313). In this way, the proposed data management system can solve the problem of inconsistency or error of customer data in different business departments. Through the data management platform 33, when a business department wants to use customer data, it can take the initiative to synchronize with the data management platform 33 for confirmation. The correctness of the data can also be obtained directly from the data management platform 33 .

Further, when executing the data synchronization method, the data management system can register customer data (such as customer identity, business department, important customer, general, key marketing customer, risk value) through the data management platform. High and low, etc.), as a judgment to determine whether to update in the future, especially the independence, interdependence and grouping of customer data can be obtained from the notes, according to the golden rule applicable to the applied organization (according to the correct data of each business department) The priority order of the system and the range of allowable changes are set to determine the data modification criteria), as the basis for judging whether to update, for a related embodiment, reference may be made to the flowchart shown in FIG. 4 .

In this example, when the data management platform receives the customer data transmitted by the subsystem (step S401 ), it uses software methods to analyze the customer data (step S403 ), and obtains the attributes of the data (step S405 ), so that the data management platform can analyze the data attributes according to the data attributes (step S405 ). Registering the customer data can be used to determine whether the data has been stored before, and also to determine the attributes of the data (step S407). In this part, various labels describing the customer data can be created with reference to the method described in the above embodiment. Metadata or specific files are tagged and stored in the database.

Next, the customer data stored in the database in the data management platform in the past can be compared (step S409 ) to determine whether the data needs to be updated? (Step S411), determine whether the factors need to be updated, for example, first obtain the data of each field in the customer data, and obtain the attributes of the customer data, such as business department, intensity, priority, change time, objects to be synchronized (other subsystems), And independence/dependency/groupness.

If the data are consistent, including considering the above-mentioned various factors, the procedure should be terminated without updating the data (step S413 ); otherwise, the data in the data management platform will be updated (step S415 ). In one scenario, when a customer changes data, it can be forced to cover the subsystem and data management platform. Taking financial institutions such as banks as an example, when a customer visits the counter or uses a specific communication method to confirm that their data is current, correct and up-to-date. When agreeing to update the information of the whole bank in a unified manner, the relevant subsystems will synchronize the information to the information management platform, and the information management platform will also force the update of the information and notify other subsystems to update the information of the whole bank synchronously. In the data management platform, the data received from the subsystem can also be used to judge its independence, dependence and grouping, and to judge whether the corresponding data in other subsystems needs to be updated synchronously, that is, to judge the customer data of other subsystems. Whether it has the permission to receive, or whether the item/field has the permission to write, that is, it is synchronized to each subsystem according to the permission (step S417 ).

Further, the above-mentioned change history of each piece of data can also be recorded on the data management platform. In the step of judging whether to update or not, the time involved is one of the main basis for judging whether to update, because data with a relatively recent time can often be replaced. Older data; the factor for judging whether to update is also data strength, in which subsystems (each business unit) have different strengths for the correctness of specific data, taking financial institutions as an example, customers obtained from the Internet or other subsystems The strength of the information may not be as strong as that of the information filled in by the customer, so whether to update or not can be judged according to this factor. In each subsystem, when the data is obtained from the client or the platform, it can be judged whether there is an annotation. If the data has been registered, it will no longer be stored. If the data obtained from the customer has been registered, it will no longer be transmitted to the data management platform.

To sum up, according to the data management system and data synchronization method described in the above embodiments, the system can operate in an organization with one or more business departments, and is especially used for synchronizing data generated by different departments, so that each business department can be used at any time. Correct and complete data can be obtained, and there will be no errors in data management due to some differences. In the process, according to the data provided by the customer and according to the field correlation, set the dependent group relationship (including independence (I), dependency (D), Group (G)), according to the correctness of the data of each business system, the system priority order and the range of allowable changes are set, and the data modification criteria (that is, the golden rule) are set according to the sequence of the change time, and the data can be provided. A more complete data management solution for the management system.

The contents disclosed above are only preferred feasible embodiments of the present invention, and are not intended to limit the scope of the present invention. Therefore, any equivalent technical changes made by using the contents of the description and drawings of the present invention are included in the application of the present invention. within the scope of the patent.

10: Internet 100: Data Management Platform 101:Database 103: Management interface 111: Subsystem one 112: Subsystem II 113: Subsystem three 20: Subsystem 205: Customer Database 251:Data attribute 201: Data synchronization unit 203: Data acquisition unit 231: Closet 232: Internet Banking 233: Fill in the form 234: Customer Service System 235: Financial Specialist 200: Data Management Platform 211: Data receiving unit 213: Data Analysis Unit 215: Data Annotation Unit 217: Data synchronization unit 219: Library Unit 31: Customers 32,34: Subsystems 33: Data Management Platform Steps S301-S313: data synchronization process Steps S401～S417: customer data processing flow

1 shows a schematic diagram of an embodiment of a data management system;

FIG. 2 shows a functional block diagram of the main system and subsystems applicable to the data synchronization method;

FIG. 3 shows a flow chart of an embodiment of data synchronization; and

FIG. 4 shows a flowchart of an embodiment of a data synchronization method.

20: Subsystem

205: Customer Database

251:Data attribute

201: Data synchronization unit

203: Data acquisition unit

231: Closet

232: Internet Banking

233: Fill in the form

234: Customer Service System

235: Financial Specialist

200: Data Management Platform

211: Data receiving unit

213: Data Analysis Unit

215: Data Annotation Unit

217: Data synchronization unit

219: Library Unit

Claims (4)

A data synchronization method is executed on a data management platform. The data management platform operates a main system to manage data provided by a plurality of subsystems, including: receiving a piece of data transmitted by one of the subsystems; parsing the data to obtain the data The attributes of the data; compare the corresponding data in a database to generate a comparison result; and determine whether the corresponding data in the database or one or one of them needs to be updated synchronously according to the attributes of the data and the comparison result. A plurality of items; wherein, when it is determined that the corresponding data in the database on the data management platform or one or more of the items need to be updated synchronously, the corresponding data in the database is synchronously updated according to the comparison result; wherein , when executing the data synchronization method, the main system registers the received data through the data management platform as the basis for judging whether to update, and the data management platform parses the data when receiving the data sent by the subsystem And obtain the attributes of the data, so that the data management platform can annotate according to the attributes of the data to determine whether the data has been stored and determine the attributes of the data, according to the attributes of the data and the comparison result If it is determined that the data is consistent, the corresponding data in the database will not be updated synchronously, otherwise, the data corresponding to the database in the data management platform will be updated; wherein, the data management platform is also based on the data received from the subsystem. When judging whether the data needs to be synchronously updated to the corresponding data in other subsystems, determine whether other subsystems have the permission to receive the data or whether it has the permission to write, and update each subsystem synchronously according to the permissions; The data is a customer data, the subsystem receives the customer data through one or more channels, and the attributes of the customer data at least include the business department to which the subsystem belongs, the importance of the customer data, and the change of the customer data. time, and the independence and dependencies of the one or more items in the client profile and group nature; the main system runs in a financial institution, the subsystem runs in one of the business divisions of the financial institution, and the subsystem obtains the customer information through the one or more channels that belong to the business division , the channel for obtaining the customer information is the counter, online banking, filling in the form, customer service system or wealth management specialist. The data synchronization method according to claim 1, wherein when synchronously updating the corresponding data in the database, it is also determined to be general customer data or data that requires forced synchronization, so as to synchronously update the corresponding data in other subsystems. A data management system, comprising: a data management platform with a database; and one or more subsystems, each subsystem executes a data acquisition program for receiving data through one or more channels and performing a data synchronization a program for synchronizing data with the data management platform; wherein a data synchronization method is executed in the data management platform, including: receiving a piece of data sent by one of the subsystems; parsing the data to obtain attributes of the data; comparing the data generating a comparison result for the corresponding data in the database; and judging whether the corresponding data in the database or one or more items thereof needs to be updated synchronously according to the attributes of the data and the comparison result; wherein, when judging When the corresponding data or one or more items in the database on the data management platform needs to be updated synchronously, the corresponding data in the database is updated synchronously according to the comparison result; wherein, when the data synchronization method is executed , the data management system registers the received data through the data management platform as the basis for judging whether to update, and when the data management platform receives the data transmitted by the subsystem, it parses the data and obtains the attributes of the data , so that the data management platform can annotate according to the attributes of the data to determine whether the data has been stored and determine the attributes of the data, according to the attributes of the data and the data If the comparison result determines that the data is consistent, the corresponding data in the database will not be updated synchronously, otherwise, the data corresponding to the database in the data management platform will be updated; When judging whether the data of this subsystem needs to be updated to the corresponding data in other subsystems synchronously, it is judged whether other subsystems have the permission to receive the data or whether it has the permission to write in it, and update it synchronously to each sub-system according to the permission. Subsystem; wherein the data management platform is a platform operated by a financial institution, and operates as a main system to manage the data provided by the one or more subsystems; the subsystem is a business department in the financial institution, through the temporary If the information is received by the counter, online banking, form filling, customer service system or wealth management specialist, the attributes of the information at least include the business department to which the subsystem belongs, the importance of the information, the change time of the information, and the information in the information. The independence, dependencies, and grouping of one or more items. The data management system according to claim 3, wherein when synchronously updating the corresponding data in the database, it is also determined to be general customer data or data that needs to be forced to be synchronized, so as to synchronously update the corresponding data in other subsystems.

Images