Data synchronization method and related device

Abstract

The invention discloses a data synchronization method and a related device. The method can be applied to a customer experience platform, and comprises the following steps: sending a data acquisition request to electronic equipment comprising a target data source; receiving a data synchronization request sent by the electronic equipment; the data synchronization request comprises to-be-synchronized data included in the target data source and a second timestamp; and in response to the received data synchronization request, performing data synchronization based on the to-be-synchronized data, and updating the first timestamp to the second timestamp. Therefore, the first timestamp can represent the time for synchronizing the data from the target data source last time, and the client experience platform can obtain the incremental data generated by the target data source based on the first timestamp compared with the incremental data generated when the data is synchronized last time, so that the incremental synchronization can be performed in a targeted manner, the data transmission quantity during data synchronization can be reduced, and the user experience is improved. And thus, the network bandwidth consumption and the data processing pressure are reduced.

Description

Technical Field

[0001] The present application relates to the field of data processing, and in particular to a data synchronization method and related devices. Background Art

[0002] In the current digital age, customer experience is crucial in fields such as finance. Taking credit cards in the financial field as an example, analyzing customer experience data such as customer suggestions and feelings about credit cards can help improve products and services.

[0003] Customer experience data may be scattered in different data sources. For example, customer experience data related to credit cards may be scattered in the data source of the sales management system, the data source of the customer relationship management system, and the data source of the UnionPay platform. Currently, data from these different data sources can be synchronized through third-party integration tools. However, third-party integration tools will synchronize all data from different data sources. In other words, if the data in any data source changes, the third-party integration tool will synchronize all the data from that data source. On the one hand, it is easy to increase network bandwidth consumption and data processing pressure, and on the other hand, using third-party integration tools will also cause additional cost overhead. Summary of the invention

[0004] In view of this, an embodiment of the present application provides a data synchronization method and related devices, the purpose of which is to reduce network bandwidth consumption and data processing pressure during data synchronization, and also reduce the cost overhead caused by using third-party integration tools.

[0005] In a first aspect, an embodiment of the present application provides a data synchronization method, which is applied to a customer experience platform, and the method includes:

[0006] Sending a data acquisition request to an electronic device including a target data source;

[0007] The data acquisition request includes a first timestamp, the first timestamp is used to indicate the time of last synchronization of data from the target data source, and the data acquisition request is used to instruct the electronic device to determine the data to be synchronized included in the target data source based on the first timestamp; the target data source is used to store financial business data;

[0008] receiving a data synchronization request sent by the electronic device; the data synchronization request includes the data to be synchronized included in the target data source and a second timestamp, the second timestamp being used to indicate the time when the latest data in the data to be synchronized is updated;

[0009] In response to receiving the data synchronization request, data synchronization is performed based on the data to be synchronized, and the first timestamp is updated to the second timestamp.

[0010] In a possible implementation, the data synchronization method further includes:

[0011] Establish a connection with the target data source;

[0012] Establish standard data structures;

[0013] The target data structure of the target data source is mapped to the standard data structure to obtain a mapping relationship between the target data structure and the standard data structure.

[0014] In a possible implementation manner, the performing data synchronization based on the data to be synchronized includes:

[0015] Based on the mapping relationship between the target data structure and the standard data structure, mapping the target data structure of the data to be synchronized to the standard data structure;

[0016] Determining that the mapped data to be synchronized includes data to be added, and adding the data to be added to a database of the customer experience platform;

[0017] It is determined that the mapped data to be synchronized includes data to be modified, and original data included in the database is modified based on the data to be modified, wherein the data to be modified corresponds to the original data.

[0018] In a possible implementation, the data to be synchronized includes first data to be synchronized and second data to be synchronized, the first data to be synchronized and the second data to be synchronized both correspond to the same target original data of the database of the customer experience platform; the first data to be synchronized corresponds to a first transaction, the second data to be synchronized corresponds to a second transaction, and a data synchronization request time of the first transaction is earlier than a data synchronization request time of the second transaction; and performing data synchronization based on the data to be synchronized includes:

[0019] Acquire a timestamp corresponding to the target original data through both the first transaction and the second transaction;

[0020] If, through the first transaction, it is determined that the acquired timestamp is the same as the timestamp currently corresponding to the target original data, data synchronization is performed on the target original data based on the first data to be synchronized, and the timestamp corresponding to the target original data is updated based on the timestamp corresponding to the first data to be synchronized;

[0021] If it is determined through the second transaction that the acquired timestamp is different from the timestamp currently corresponding to the target original data, the data synchronization request of the second transaction is rejected.

[0022] In a possible implementation, sending a data acquisition request to an electronic device including a target data source includes:

[0023] A data acquisition request is sent to the electronic device including the target data source multiple times according to a preset period.

[0024] In a second aspect, an embodiment of the present application provides a data synchronization method, which is applied to an electronic device, wherein the electronic device includes a target data source, and the method includes:

[0025] Receive data acquisition requests sent by the customer experience platform;

[0026] The data acquisition request includes a first timestamp, the first timestamp is used to indicate the time when the customer experience platform last synchronized data from the target data source, and the data acquisition request is used to instruct the electronic device to determine the data to be synchronized included in the target data source based on the first timestamp; the target data source is used to store financial business data;

[0027] In response to receiving the data acquisition request, determining a third timestamp corresponding to the latest data from the target data source;

[0028] If it is determined that the third timestamp is later than the first timestamp, the third timestamp is used as the second timestamp, and data with a timestamp later than the first timestamp is used as the data to be synchronized from the target data source;

[0029] Sending a data synchronization request to the customer experience platform; the data synchronization request includes the data to be synchronized and the second timestamp.

[0030] In a possible implementation, the data processing method further includes:

[0031] It is determined that the third timestamp is earlier than the first timestamp, and indication information for indicating that there is no data to be synchronized in the target data source is sent to the customer experience platform.

[0032] In a third aspect, an embodiment of the present application provides a data synchronization system, the data synchronization system comprising a customer experience platform and an electronic device, the electronic device comprising a target data source;

[0033] The customer experience platform is used to send a data acquisition request to an electronic device including a target data source;

[0034] The data acquisition request includes a first timestamp, the first timestamp is used to indicate the time of last synchronization of data from the target data source, and the data acquisition request is used to instruct the electronic device to determine the data to be synchronized included in the target data source based on the first timestamp; the target data source is used to store financial business data;

[0035] The electronic device is used to receive a data acquisition request sent by the customer experience platform;

[0036] The electronic device is configured to determine, in response to receiving the data acquisition request, a third timestamp corresponding to the latest data from the target data source;

[0037] The electronic device is configured to determine that the third timestamp is later than the first timestamp, use the third timestamp as the second timestamp, and use data with a timestamp later than the first timestamp from the target data source as the data to be synchronized;

[0038] The electronic device is used to send a data synchronization request to the customer experience platform; the data synchronization request includes the data to be synchronized and the second timestamp;

[0039] The customer experience platform is used to receive a data synchronization request sent by the electronic device; the second timestamp is used to indicate the time when the latest data in the data to be synchronized is updated;

[0040] The customer experience platform is used to, in response to receiving the data synchronization request, perform data synchronization based on the data to be synchronized, and update the first timestamp to the second timestamp.

[0041] In a fourth aspect, an embodiment of the present application provides a data synchronization device, the device comprising a memory and a processor:

[0042] The memory is used to store a computer program and transmit the computer program to the processor;

[0043] The processor is used to execute the computer program so that the device executes the data synchronization method described in the first aspect.

[0044] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed, the device executing the computer program implements the data synchronization method described in the first aspect above.

[0045] Compared with the prior art, the embodiments of the present application have the following beneficial effects:

[0046] The embodiment of the present application provides a data synchronization method and related devices, which are applied to a customer experience platform. In the method, the customer experience platform first sends a data acquisition request to an electronic device including a target data source; wherein the data acquisition request includes a first timestamp, which is used to indicate the time when the customer experience platform last synchronized data from the target data source, and the data acquisition request is used to indicate that the electronic device determines the data to be synchronized included in the target data source based on the first timestamp; the target data source is used to store financial business data. Then, the customer experience platform receives the data synchronization request sent by the electronic device, which includes the data to be synchronized included in the target data source and a second timestamp, which is used to indicate the time when the latest data in the data to be synchronized is updated; then, in response to receiving the data synchronization request, the customer experience platform can perform data synchronization based on the data to be synchronized, and update the first timestamp to the second timestamp.

[0047] In this way, the first timestamp can represent the time when the customer experience platform last synchronized data from the target data source. The customer experience platform can determine the incremental data generated by the target data source compared with the last time the data was synchronized based on the first timestamp, and then can perform incremental synchronization in a targeted manner. Therefore, the data synchronization method provided by the present application, on the basis of ensuring accurate data synchronization, only needs to transmit the incremental data that has changed in the target data source, which can reduce the amount of data transmission during data synchronization, thereby reducing network bandwidth consumption and data processing pressure.

[0048] In addition, only the incremental data that has changed in the target data source needs to be transferred, which can also reduce the time and resource costs of data synchronization. And there is no need to synchronize data through third-party integration tools, which can reduce cost expenses. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the technical solutions in this embodiment or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0050] Figure 1 An application scenario of a data synchronization method provided in an embodiment of the present application;

[0051] Figure 2 A flowchart of a data synchronization method provided in an embodiment of the present application;

[0052] Figure 3 A schematic diagram of data stored in a target data source provided in an embodiment of the present application;

[0053] Figure 4 A schematic diagram of a concurrent update processing mechanism provided in an embodiment of the present application;

[0054] Figure 5 A flowchart of another data synchronization method provided in an embodiment of the present application;

[0055] Figure 6 A schematic diagram of a data synchronization method provided in an embodiment of the present application;

[0056] Figure 7 A structural diagram of a data synchronization system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0057] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0058] At present, the existing data synchronization method is: use third-party integration tools to synchronize the data of the data source. When the data of the data source changes, the data of the data source needs to be synchronized in full. On the one hand, it is easy to increase network bandwidth consumption and data processing pressure. On the other hand, the use of third-party integration tools will also cause additional cost overhead.

[0059] Based on this, in order to solve the above problems, the embodiment of the present application provides a data synchronization method and related devices, which are applied to a customer experience platform. In this method, the customer experience platform first sends a data acquisition request to an electronic device including a target data source; wherein the data acquisition request includes a first timestamp, which is used to indicate the time when the customer experience platform last synchronized data from the target data source, and the data acquisition request is used to indicate that the electronic device determines the data to be synchronized included in the target data source based on the first timestamp; the target data source is used to store financial business data. Then, the customer experience platform receives the data synchronization request sent by the electronic device, which includes the data to be synchronized included in the target data source and a second timestamp, which is used to indicate the time when the latest data in the data to be synchronized is updated; then, in response to receiving the data synchronization request, the customer experience platform can perform data synchronization based on the data to be synchronized, and update the first timestamp to the second timestamp.

[0060] In this way, the first timestamp can represent the time when the customer experience platform last synchronized data from the target data source. The customer experience platform can determine the incremental data generated by the target data source compared with the last time the data was synchronized based on the first timestamp, and then can perform incremental synchronization in a targeted manner. Therefore, the data synchronization method provided by the present application, on the basis of ensuring accurate data synchronization, only needs to transmit the incremental data that has changed in the target data source, which can reduce the amount of data transmission during data synchronization, thereby reducing network bandwidth consumption and data processing pressure.

[0061] In addition, only the incremental data that has changed in the target data source needs to be transferred, which can also reduce the time and resource costs of data synchronization. And there is no need to synchronize data through third-party integration tools, which can reduce cost expenses.

[0062] For example, the embodiments of the present application can be applied to Figure 1 In the scenario shown. The scenario includes a customer experience platform 101 and a server 102. The server 102 may include a target data source, and the customer experience platform 101 may be deployed on a terminal device or on a server. The customer experience platform 101 adopts the implementation method provided in the embodiment of the present application, and may synchronize data with the target data source included in the server 102. The server 102 may also adopt the implementation method provided in the embodiment of the present application, so that the customer experience platform 101 synchronizes data with the target data source.

[0063] The server 102 may be an independent server, a cluster server, a cloud server, etc. The terminal device may be a smart phone, a computer, a tablet computer, etc.

[0064] First, in the above application scenario, the server 102 including the target data source is only an example. The terminal device may also include the target data source. The customer experience platform and the target data source are deployed on different electronic devices (the electronic device may include a terminal device and a server, etc.). The customer experience platform and the target data source may also be deployed on the same terminal device or server.

[0065] Secondly, the above scenario is only an example scenario provided by the embodiment of the present application, and the embodiment of the present application is not limited to this scenario. For example, there may be multiple target data sources, which are respectively deployed in different electronic devices, and the customer experience platform 101 may synchronize data with all of these multiple target data sources.

[0066] The following is a detailed description of the specific implementation of the data synchronization method and related devices in the embodiment of the present application through embodiments in conjunction with the accompanying drawings. Figure 2 , which is a flow chart of a data synchronization method provided in an embodiment of the present application, applied to a customer experience platform, combined with Figure 2As shown, it may specifically include:

[0067] S201: The customer experience platform sends a data acquisition request to an electronic device including a target data source.

[0068] In the embodiment of the present application, the target data source can be used to store financial business data. In some embodiments, the financial business data may include credit card business data, savings card business data, etc. For ease of understanding, the following text takes credit card business data as an example to introduce the data synchronization method provided in the embodiment of the present application.

[0069] In some embodiments, the target data sources may include customer databases, transaction systems, customer service platforms, marketing channels, etc. These target data sources may provide different types of data about credit card transactions, customer and credit card related data, credit card services, etc.

[0070] As an example, see Figure 3 , which is a schematic diagram of data stored in a target data source provided by an embodiment of the present application. Figure 3 As shown, the target data source may store credit card transaction data, customer and credit card related data, and credit card service data.

[0071] Among them, credit card transaction data may include credit card transaction record data such as transaction amount, transaction time and transaction location; customer-related credit card data may include information such as name, contact information and credit score; credit card service data may include customer complaints, customer suggestions and solutions regarding credit cards, etc., and interaction records with credit card customer service.

[0072] It should be noted that the target data source may include more or fewer types of data than the above examples, and this application does not limit this.

[0073] It should be emphasized that in the specific implementation methods of this application, the customer information (including but not limited to customer personal information such as name and contact information) and data (including but not limited to credit card transaction data, credit card service data, etc.) involved, when the above embodiments of this application are applied to specific products or technologies, are all information and data authorized by the customer or fully authorized by all parties, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.

[0074] The data acquisition request includes a first timestamp, and the first timestamp is used to indicate the time when the customer experience platform last synchronized data from the target data source.

[0075] In the next embodiment, each data of the target data source may include a field for recording the time when the data was last updated. Exemplarily, the field may be a timestamp, which is not limited in the present application. In the following embodiments, it is referred to as the timestamp corresponding to the data, which is used to record the time when the data was last updated.

[0076] In some embodiments, the first timestamp may be used to indicate the timestamp corresponding to the latest data in the data that the customer experience platform last synchronized from the target data source (i.e., the second timestamp mentioned below). Exemplarily, 10 data were synchronized last time, and the timestamps corresponding to these 10 data are t1-t10, with t10 being the latest, indicating that the data corresponding to t10 is the latest data of the target data source at the time of the last synchronization of data, such as the latest modified data at t10, or the latest added data at t10, then the first timestamp when sending a data acquisition request next time may be t10.

[0077] The data acquisition request is used to instruct the electronic device including the target data source to determine the data to be synchronized included in the target data source based on the first timestamp. That is, after receiving the data acquisition request, the electronic device can determine the incremental data based on the first timestamp for subsequent incremental synchronization. For specific implementation methods, please refer to Figure 5 The introduction of the corresponding embodiments will not be elaborated here.

[0078] In some embodiments, the data acquisition request sent by the customer experience platform to the electronic device may be a GET request based on the Hyper Text Transfer Protocol (HTTP).

[0079] S202: The customer experience platform receives a data synchronization request sent by the electronic device.

[0080] The data synchronization request includes the data to be synchronized included in the target data source and a second timestamp, where the second timestamp is used to indicate the time when the latest data in the data to be synchronized is updated.

[0081] In the embodiment of the present application, the second timestamp is later than the first timestamp, indicating that the data to be synchronized is updated to the target data source after the last synchronization.

[0082] The data synchronization request is used to instruct the customer experience platform to perform data synchronization based on the data to be synchronized, and to update the first timestamp based on the second timestamp.

[0083] For an introduction to the data to be synchronized and the second timestamp, see below Figure 5 The corresponding embodiments will not be expanded here.

[0084] S203: In response to receiving the data synchronization request, the customer experience platform performs data synchronization based on the data to be synchronized, and updates the first timestamp to the second timestamp.

[0085] In some embodiments, the data to be synchronized can be synchronized to the database of the customer experience platform, and the first timestamp can be updated to a second timestamp to indicate the time when the data is synchronized from the target data source this time, indicating that all data before the latest first timestamp in the target data source has been synchronized to the customer experience platform.

[0086] In addition, in a possible implementation, the data synchronization method may also include: the customer experience platform establishes a connection with the target data source; the customer experience platform establishes a standard data structure; the customer experience platform maps the target data structure of the target data source to the standard data structure to obtain a mapping relationship between the target data structure and the standard data structure.

[0087] After the customer experience platform is connected to the target data source, it can identify the data in the data source, such as the above Figure 3 The customer experience platform can establish a standard data structure (also called a unified data model) that can describe the relationship between credit card transaction data, customer and credit card related data, credit card service data, etc. The customer experience platform can then obtain the mapping relationship between the target data structure and the standard data structure to synchronize the data of the target data source to the customer experience platform.

[0088] In some embodiments, the present application does not limit the number of target data sources, and the target data source may include multiple target data sources. The customer experience platform can then perform the above operations on each of the multiple target data sources to obtain a mapping relationship between each target data structure and the standard data structure.

[0089] In this way, considering the inconsistency of data structures stored in different data sources, a unified standard data structure is established on the customer experience platform to facilitate data integration and understanding, which helps to improve the performance of data synchronization.

[0090] In some embodiments, the standard data structure may include a standard field and a standard data type, and the target data structure may include a target field and a target data type. The following embodiments will be described using this as an example.

[0091] It should be noted that the standard data structure and the target data structure may include more or less content than the above examples, and this application does not limit this. For example, they may also include data format, data length, etc.

[0092] In a possible implementation of the present application, the "data synchronization based on the data to be synchronized" included in S203 above may include: the customer experience platform first maps the target data structure of the data to be synchronized to the standard data structure based on the mapping relationship between the target data structure and the standard data structure; then the customer experience platform determines that the mapped data to be synchronized includes data to be added, and then adds the data to be added to the database of the customer experience platform; the customer experience platform determines that the mapped data to be synchronized includes data to be modified, and then modifies the original data included in the database based on the data to be modified, and the data to be modified corresponds to the original data.

[0093] For example, one of the data to be synchronized includes field 1, the data type of the value of field 1 is integer, and in the target data structure, field 1 is used to store the customer's contact information. In the standard data structure, field 2 is used to store the customer's contact information, and the data type of the value of field 2 is floating point. The customer experience platform can first map field 1 to field 2, and then map the data type of the value of field 1 to floating point.

[0094] If the data is data to be newly added, the customer experience platform can directly add it to the database as new data.

[0095] In the case where the data is data to be modified, for example, the original data is the customer's contact information 132xxxxxxxx, and the data to be modified is the customer's new contact information "188xxxxxxxx", then the customer experience platform can modify the value of field 2 of the original data to "188xxxxxxxx".

[0096] Each data (also referred to as each piece of data) has identification information for identifying the data from multiple data. The customer experience platform can determine whether the data to be synchronized is data to be added or data to be modified based on the identification information of the data to be synchronized.

[0097] In a possible implementation of the present application, the data to be synchronized includes first data to be synchronized and second data to be synchronized, and the first data to be synchronized and the second data to be synchronized both correspond to the same target original data in the database of the customer experience platform; the first data to be synchronized corresponds to a first transaction, and the second data to be synchronized corresponds to a second transaction, and a data synchronization request time of the first transaction is earlier than a data synchronization request time of the second transaction.

[0098] Accordingly, the "data synchronization based on the data to be synchronized" included in S203 above may include: the customer experience platform first obtains the timestamp corresponding to the target original data through both the first transaction and the second transaction; the customer experience platform then determines through the first transaction that the acquired timestamp is the same as the timestamp currently corresponding to the target original data, then synchronizes the target original data based on the first data to be synchronized, and updates the timestamp corresponding to the target original data based on the timestamp corresponding to the first data to be synchronized; the customer experience platform then determines through the second transaction that the acquired timestamp is different from the timestamp currently corresponding to the target original data, then rejects the data synchronization request of the second transaction.

[0099] Exemplarily, the first data to be synchronized is the data to be modified, such as increasing the customer's account balance in a credit card deposit, and the second data to be synchronized is also the data to be modified, such as reducing the same customer's account balance in a credit card withdrawal. Therefore, the first transaction and the second transaction corresponding to the two respectively need to modify the same target original data.

[0100] For an example of an assignment, see Figure 4 , which is a schematic diagram of a concurrent update processing mechanism provided by an embodiment of the present application. The target original data stores the account balance, and its corresponding timestamp is timestamp 1. Timestamp 1 is read through both the first transaction and the second transaction. The time of the data synchronization request of the first transaction is earlier than the time of the data synchronization request of the second transaction. The first transaction determines that the timestamp corresponding to the target original data is still timestamp 1, then the operation A of the first transaction can be executed to increase the customer's account balance, and the timestamp 1 corresponding to the target original data is updated to the timestamp 2 corresponding to the first data to be synchronized (also called the saved timestamp); then the timestamp corresponding to the target original data is determined to be timestamp 2 (that is, not timestamp 1) through the second transaction, then the data synchronization request of the second transaction can be rejected, that is, there is no need to execute operation B, and the second transaction can be prompted to be re-executed, that is, the operation is re-performed.

[0101] In this way, through the above-mentioned concurrent update processing mechanism, multiple transactions with similar data synchronization request times can be effectively processed to ensure data consistency and integrity, reduce data competition and conflicts caused by concurrent updates, and help maintain the stability and reliability of the customer experience platform.

[0102] In a possible implementation of the present application, S201 may specifically include: the customer experience platform sends a data acquisition request to the electronic device including the target data source multiple times according to a preset period. In some embodiments, the preset period may be 45 minutes or 1 hour, and may be set based on business needs and the data update frequency of the target data source.

[0103] Among them, different preset periods can be set for different target data sources.

[0104] In this way, compared with third-party integration tools that perform data synchronization based on pre-configured rules, which cannot be modified at any time and have poor flexibility, the data synchronization method provided in the present application can flexibly set the preset cycle based on business needs and the data update frequency of different target data sources, and can capture changes in the target data source in a timely manner, thereby ensuring the real-time and accuracy of data synchronization.

[0105] In addition, in some embodiments, each data synchronization process can be logged, such as recording the execution status of polling (that is, recording the situation of sending data acquisition requests according to a preset period), whether data synchronization has been performed, and the number of transactions in data synchronization (that is, the number of data to be synchronized), abnormal information on whether data synchronization is successful, and the processing time of data synchronization, etc., for subsequent auditing, troubleshooting and performance optimization.

[0106] See also Figure 5 , which is a flow chart of another data synchronization method provided by an embodiment of the present application, applied to an electronic device including a target data source, combined with Figure 5 As shown, it may specifically include:

[0107] S501: The electronic device receives a data acquisition request sent by the customer experience platform.

[0108] The data acquisition request includes a first timestamp, the first timestamp is used to indicate the time when the customer experience platform last synchronized data from the target data source, and the data acquisition request is used to instruct the electronic device to determine the data to be synchronized included in the target data source based on the first timestamp; the target data source is used to store financial business data;

[0109] It should be noted that the specific implementation of S501 can refer to the introduction of S201 and will not be repeated here.

[0110] S502: In response to receiving the data acquisition request, the electronic device determines a third timestamp corresponding to the latest data from the target data source.

[0111] In some embodiments, the target data source includes multiple data, and each data includes a corresponding timestamp for indicating the time when the data was last updated.

[0112] Exemplarily, each data includes a timestamp field, whose value is used to indicate the time when the data was last updated.

[0113] After receiving the data acquisition request, the electronic device can query the timestamps corresponding to the data in the target data source, and determine the latest timestamp as the third data stamp, the corresponding data of which is the latest data last updated in the target data source.

[0114] S503: The electronic device determines that the third timestamp is later than the first timestamp, uses the third timestamp as the second timestamp, and uses data with a timestamp later than the first timestamp from the target data source as the data to be synchronized.

[0115] The electronic device determines that the third timestamp is later than the first timestamp, indicating that after the customer experience platform last synchronized data from the target data source, the target data source has performed data update operations such as data modification or data addition, that is, there is data that needs to be synchronized. Therefore, the data in the target data source with a timestamp later than the first timestamp are all pending data that need to be synchronized this time. In order to ensure the smooth progress of the next data synchronization, the third timestamp can also be used as the second timestamp to execute subsequent steps.

[0116] S504: The electronic device sends a data synchronization request to the customer experience platform.

[0117] The data synchronization request includes the data to be synchronized and the second timestamp.

[0118] It should be noted that the specific implementation method of S504 can refer to the introduction of S202, which will not be repeated here.

[0119] As an example, see Figure 6 , this figure is a schematic diagram of a data synchronization method provided in an embodiment of the present application. The electronic device receives a data acquisition request, obtains the timestamp of each data in the target data source, and determines that there is a timestamp greater than the first timestamp, for example, the first timestamp is lastUpdateTime, then determines the data with a timestamp greater than lastUpdateTime as the data to be synchronized, and uses the largest timestamp as the second data stamp, for example, the second timestamp is latestSyncTime, and then sends a data synchronization request including the data to be synchronized and latestSyncTime to the customer experience platform. After receiving the data synchronization request, the customer experience platform can perform incremental synchronization based on the data to be synchronized, and update lastUpdateTime to latestSyncTime, and then record relevant logs of this data synchronization process.

[0120] In addition, in a possible implementation of the present application, the data synchronization method may also include: the electronic device determines that the third timestamp is earlier than the first timestamp, and sends indication information to the customer experience platform to indicate that there is no data to be synchronized in the target data source.

[0121] The electronic device determines that the third timestamp is earlier than the first timestamp, indicating that after the customer experience platform last synchronized data from the target data source, the target data source has not performed any data update operations such as data modification or data addition. Therefore, no data synchronization is required this time. Therefore, the electronic device can send an indication information to the customer experience platform to indicate that the target data source does not have any data to be synchronized.

[0122] The above are some specific implementations of the data synchronization method provided in the embodiment of the present application. Based on this, the present application also provides a corresponding data synchronization system. The data synchronization system provided in the embodiment of the present application will be introduced below from the perspective of functional modularization.

[0123] See also Figure 7 , which is a structural schematic diagram of a data synchronization system provided in an embodiment of the present application, the data synchronization system 700 may include: a customer experience platform 710 and an electronic device 720, wherein the electronic device 720 includes a target data source;

[0124] The customer experience platform 710 is used to send a data acquisition request to an electronic device including a target data source;

[0125] The data acquisition request includes a first timestamp, the first timestamp is used to indicate the time of last synchronization of data from the target data source, and the data acquisition request is used to instruct the electronic device to determine the data to be synchronized included in the target data source based on the first timestamp; the target data source is used to store financial business data;

[0126] The electronic device 720 is used to receive a data acquisition request sent by the customer experience platform;

[0127] The electronic device 720 is configured to determine, in response to receiving the data acquisition request, a third timestamp corresponding to the latest data from the target data source;

[0128] The electronic device 720 is configured to determine that the third timestamp is later than the first timestamp, use the third timestamp as the second timestamp, and use data with a timestamp later than the first timestamp from the target data source as the data to be synchronized;

[0129] The electronic device 720 is used to send a data synchronization request to the customer experience platform; the data synchronization request includes the data to be synchronized and the second timestamp;

[0130] The customer experience platform 710 is used to receive a data synchronization request sent by the electronic device; the second timestamp is used to indicate the time when the latest data in the data to be synchronized is updated;

[0131] The customer experience platform 710 is configured to, in response to receiving the data synchronization request, perform data synchronization based on the data to be synchronized, and update the first timestamp to the second timestamp.

[0132] As an implementation method, the customer experience platform 710 is also used to: establish a connection with a target data source; establish a standard data structure; map the target data structure of the target data source to the standard data structure to obtain a mapping relationship between the target data structure and the standard data structure.

[0133] As an implementation method, the customer experience platform 710 is specifically used for:

[0134] Based on the mapping relationship between the target data structure and the standard data structure, mapping the target data structure of the data to be synchronized to the standard data structure;

[0135] Determining that the mapped data to be synchronized includes data to be added, and adding the data to be added to a database of the customer experience platform;

[0136] It is determined that the mapped data to be synchronized includes data to be modified, and original data included in the database is modified based on the data to be modified, wherein the data to be modified corresponds to the original data.

[0137] As an implementation manner, the data to be synchronized includes first data to be synchronized and second data to be synchronized, the first data to be synchronized and the second data to be synchronized both correspond to the same target original data of the database of the customer experience platform; the first data to be synchronized corresponds to a first transaction, the second data to be synchronized corresponds to a second transaction, and a data synchronization request time of the first transaction is earlier than a data synchronization request time of the second transaction; the customer experience platform 710 is specifically used to:

[0138] Acquire a timestamp corresponding to the target original data through both the first transaction and the second transaction;

[0139] If, through the first transaction, it is determined that the acquired timestamp is the same as the timestamp currently corresponding to the target original data, data synchronization is performed on the target original data based on the first data to be synchronized, and the timestamp corresponding to the target original data is updated based on the timestamp corresponding to the first data to be synchronized;

[0140] If it is determined through the second transaction that the acquired timestamp is different from the timestamp currently corresponding to the target original data, the data synchronization request of the second transaction is rejected.

[0141] As an implementation method, the customer experience platform 710 is specifically used for:

[0142] A data acquisition request is sent to the electronic device including the target data source multiple times according to a preset period.

[0143] As an implementation manner, the electronic device 720 is specifically configured to:

[0144] It is determined that the third timestamp is earlier than the first timestamp, and indication information for indicating that there is no data to be synchronized in the target data source is sent to the customer experience platform.

[0145] The embodiments of the present application also provide corresponding data synchronization devices and computer-readable storage media for implementing the solutions provided by the embodiments of the present application.

[0146] The data synchronization device includes a memory and a processor, the memory is used to store a computer program, and the processor is used to execute the computer program, so that the device executes the data synchronization method described in any embodiment of the present application.

[0147] The computer-readable storage medium stores a computer program. When the computer program is executed, a device executing the computer program implements the data synchronization method described in any embodiment of the present application.

[0148] The "first" and "second" in the names such as "first" and "second" (if any) mentioned in the embodiments of the present application are only used as name identifiers and do not represent the first or second in order.

[0149] Through the description of the above implementation methods, it can be known that those skilled in the art can clearly understand that all or part of the steps in the above-mentioned embodiment method can be implemented by means of software plus a general hardware platform. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product, which can be stored in a readable storage medium, such as a read-only memory (ROM) / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network communication device such as a router) to execute the methods described in each embodiment of the present application or some parts of the embodiments.

[0150] It should be noted that each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. The device embodiment described above is merely schematic, in which the unit described as a separate component may or may not be physically separated, and the component prompted as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative work.

[0151] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A data synchronization method, characterized in that: Applied to the customer experience platform, including: Sending a data acquisition request to an electronic device including a target data source; The data acquisition request includes a first timestamp, the first timestamp is used to indicate the time of last synchronization of data from the target data source, and the data acquisition request is used to instruct the electronic device to determine the data to be synchronized included in the target data source based on the first timestamp; the target data source is used to store financial business data; receiving a data synchronization request sent by the electronic device; the data synchronization request includes the data to be synchronized included in the target data source and a second timestamp, the second timestamp being used to indicate the time when the latest data in the data to be synchronized is updated; In response to receiving the data synchronization request, data synchronization is performed based on the data to be synchronized, and the first timestamp is updated to the second timestamp.

2. The method according to claim 1, characterized in that Also includes: Establishing a connection with the target data source; Establish standard data structures; The target data structure of the target data source is mapped to the standard data structure to obtain a mapping relationship between the target data structure and the standard data structure.

3. The method according to claim 2, characterized in that The performing data synchronization based on the data to be synchronized includes: Based on the mapping relationship between the target data structure and the standard data structure, mapping the target data structure of the data to be synchronized to the standard data structure; Determining that the mapped data to be synchronized includes data to be added, and adding the data to be added to a database of the customer experience platform; It is determined that the mapped data to be synchronized includes data to be modified, and original data included in the database is modified based on the data to be modified, wherein the data to be modified corresponds to the original data.

4. The method according to claim 1, characterized in that: The data to be synchronized includes first data to be synchronized and second data to be synchronized, and the first data to be synchronized and the second data to be synchronized both correspond to the same target original data in the database of the customer experience platform; The first data to be synchronized corresponds to a first transaction, the second data to be synchronized corresponds to a second transaction, and a data synchronization request time of the first transaction is earlier than a data synchronization request time of the second transaction; The performing data synchronization based on the data to be synchronized includes: Acquire a timestamp corresponding to the target original data through both the first transaction and the second transaction; If, through the first transaction, it is determined that the acquired timestamp is the same as the timestamp currently corresponding to the target original data, data synchronization is performed on the target original data based on the first data to be synchronized, and the timestamp corresponding to the target original data is updated based on the timestamp corresponding to the first data to be synchronized; If it is determined through the second transaction that the acquired timestamp is different from the timestamp currently corresponding to the target original data, the data synchronization request of the second transaction is rejected.

5. The method according to any one of claims 1 to 4, characterized in that: The sending of a data acquisition request to an electronic device including a target data source comprises: A data acquisition request is sent to the electronic device including the target data source multiple times according to a preset period.

6. A data synchronization method, characterized in that: Applied to an electronic device, the electronic device includes a target data source, including: Receive data acquisition requests sent by the customer experience platform; The data acquisition request includes a first timestamp, the first timestamp is used to indicate the time when the customer experience platform last synchronized data from the target data source, and the data acquisition request is used to instruct the electronic device to determine the data to be synchronized included in the target data source based on the first timestamp; the target data source is used to store financial business data; In response to receiving the data acquisition request, determining a third timestamp corresponding to the latest data from the target data source; If it is determined that the third timestamp is later than the first timestamp, the third timestamp is used as the second timestamp, and data with a timestamp later than the first timestamp is used as the data to be synchronized from the target data source; Sending a data synchronization request to the customer experience platform; the data synchronization request includes the data to be synchronized and the second timestamp.

7. The method according to claim 6, characterized in that Also includes: It is determined that the third timestamp is earlier than the first timestamp, and indication information for indicating that there is no data to be synchronized in the target data source is sent to the customer experience platform.

8. A data synchronization system, characterized in that: The data synchronization system includes a customer experience platform and an electronic device, wherein the electronic device includes a target data source; The customer experience platform is used to send a data acquisition request to an electronic device including a target data source; The data acquisition request includes a first timestamp, the first timestamp is used to indicate the time of last synchronization of data from the target data source, and the data acquisition request is used to instruct the electronic device to determine the data to be synchronized included in the target data source based on the first timestamp; the target data source is used to store financial business data; The electronic device is used to receive a data acquisition request sent by the customer experience platform; The electronic device is configured to determine, in response to receiving the data acquisition request, a third timestamp corresponding to the latest data from the target data source; The electronic device is configured to determine that the third timestamp is later than the first timestamp, use the third timestamp as the second timestamp, and use data with a timestamp later than the first timestamp from the target data source as the data to be synchronized; The electronic device is used to send a data synchronization request to the customer experience platform; the data synchronization request includes the data to be synchronized and the second timestamp; The customer experience platform is used to receive a data synchronization request sent by the electronic device; the second timestamp is used to indicate the time when the latest data in the data to be synchronized is updated; The customer experience platform is used to, in response to receiving the data synchronization request, perform data synchronization based on the data to be synchronized, and update the first timestamp to the second timestamp.

9. A data synchronization device, characterized in that: The device comprises a memory and a processor: The memory is used to store a computer program and transmit the computer program to the processor; The processor is used to execute the computer program so that the device performs the steps of the data synchronization method as described in any one of claims 1-5, or performs the steps of the data synchronization method as described in any one of claims 6-7.

10. A computer-readable storage medium, characterized in that: A computer program is stored on the computer-readable storage medium. When the computer program is executed, a device executing the computer program implements the steps of the data synchronization method as described in any one of claims 1 to 5, or implements the steps of the data synchronization method as described in any one of claims 6 to 7.

Images