Data synchronization updating method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a data synchronization updating method and device, electronic equipment and a storage medium, and belongs to the technical field of financial science and technology. The method comprises the steps of determining a to-be-identified object from acquired real-time first update data, performing version identification generation processing according to a preset identification data format and the to-be-identified object to obtain version identification information, performing version identification on the to-be-identified object to obtain second update data including the version identification information; performing mapping conversion on the second update data according to the mapping conversion function to obtain third update data, synchronizing the third update data to the sandbox simulation transaction environment, determining target update data from the third update data according to the version identification information, updating the current first sandbox data to obtain second sandbox data, and synchronizing the second sandbox data to the sandbox simulation transaction environment. And performing authority control and sandbox simulation test according to the second sandbox data. According to the embodiment of the invention, real-time, efficient, safe and reliable data synchronous updating can be realized between the data source and the sandbox simulation transaction environment.

Description

Technical Field

[0001] The present application relates to the field of financial technology, and in particular to a data synchronization update method and device, an electronic device and a storage medium. Background Art

[0002] With the rapid development of financial technology, the open banking model has become an important trend. In the open banking system, real-time data updates and sandbox simulated transactions are two key functions, but how to ensure the synchronization and security between them remains a challenge.

[0003] At present, in the field of financial technology, there are some systems and solutions related to real-time data updates and sandbox simulated transactions, but there are still some potential defects or deficiencies: First, the existing solutions have the problem of data synchronization delay, resulting in inconsistency between the real-time updated data of the data source and the data of the sandbox simulated transaction environment; this will affect the testing and development process of developers and partners. Second, some existing open banking systems have security risks in data synchronization, which will lead to sensitive data leakage or data inconsistency. Third, the existing open banking systems are complex in data synchronization and security management, which requires developers to spend more time and energy to understand and use the system. Fourth, some existing open banking systems have limitations in scalability, and the current data synchronization update method is difficult to adapt to complex open banking business scenarios. In summary, how to achieve effective and secure data synchronization and update between the real-time updated data source and the sandbox simulated transaction environment in the open banking system is a technical problem that needs to be solved urgently. Summary of the invention

[0004] The main purpose of the embodiments of the present application is to propose a data synchronization update method and device, an electronic device and a storage medium, aiming to achieve real-time, efficient, safe and reliable data synchronization update between a data source and a sandbox simulation transaction environment.

[0005] To achieve the above object, a first aspect of an embodiment of the present application provides a data synchronization update method, the method comprising:

[0006] Acquire first updated data generated in real time from a data source;

[0007] Determine the object to be identified from the first update data, perform version identification generation processing according to a preset identification data format and the object to be identified, and obtain version identification information of the object to be identified; wherein the version identification information is used to represent the generation time sequence between the objects to be identified generated at different times;

[0008] In the first update data, version identification processing is performed on the object to be identified according to the version identification information to obtain second update data including the version identification information;

[0009] Performing mapping conversion processing on the second update data according to a mapping conversion function to obtain third update data;

[0010] Synchronize the third update data to the sandbox simulation transaction environment, and determine the target update data from the third update data according to the version identification information;

[0011] The current first sandbox data is updated according to the target update data to obtain the second sandbox data, so as to perform permission control and sandbox simulation testing according to the second sandbox data in the sandbox simulation transaction environment.

[0012] In some embodiments, the version identification information includes a first version identification; determining the object to be identified from the first update data, performing version identification generation processing according to a preset identification data format and the object to be identified, and obtaining the version identification information of the object to be identified includes:

[0013] Determine at least one target update type, and determine a data field in the first update data that matches the target update type as the object to be identified;

[0014] Integrate all the objects to be identified to obtain a first data packet;

[0015] A first version identifier is generated for the first data packet; the first version identifier is used to identify the first data packet.

[0016] In some embodiments, the version identification information includes a second version identification; determining the object to be identified from the first update data, performing version identification generation processing according to a preset identification data format and the object to be identified, and obtaining the version identification information of the object to be identified includes:

[0017] Determine at least one target update type, and determine a data field in the first update data that matches the target update type as the object to be identified;

[0018] The second version identifier is generated for each of the objects to be identified; wherein the second version identifier is used to independently identify each of the objects to be identified.

[0019] In some embodiments, performing mapping conversion processing on the second update data according to a mapping conversion function to obtain third update data includes:

[0020] Performing data structure analysis and data type identification and classification processing on the second update data, and determining a first data set to be mapped and converted from the second update data;

[0021] According to the mapping conversion function, mapping and converting the first data set are performed to obtain a second data set after mapping conversion;

[0022] The second data set is format converted to obtain third updated data whose data format is a preset target format.

[0023] In some embodiments, performing mapping and conversion processing on the first data set according to the mapping conversion function to obtain a second data set after mapping conversion includes:

[0024] Determine a data mapping table, a data conversion table and a permission mapping table from the mapping conversion function;

[0025] Determining first source data to be mapped, second source data to be converted, and source authority information from the first data set;

[0026] According to the data mapping table, performing data mapping processing on the first source data to obtain first target data;

[0027] According to the data conversion table, converting the second source data into second target data;

[0028] According to the permission mapping table, the source permission information is converted into the permission mapping information; wherein the permission mapping information is used to indicate the objects that can access the sandbox simulation trading environment and the scope of operation permissions allowed in the sandbox simulation trading environment;

[0029] According to the first target data, the second target data and the permission mapping information, the second data set after mapping conversion is obtained.

[0030] In some embodiments, the target update data includes system data and permission mapping information, and the first sandbox data includes: first sandbox simulation data, first sandbox permission information;

[0031] The updating of the current first sandbox data according to the target update data to obtain the second sandbox data includes:

[0032] When the target update data includes the system data, the current first sandbox simulation data is updated according to the system data to obtain second sandbox simulation data.

[0033] When the target update data includes the permission mapping information, the current first sandbox permission information is updated to obtain second sandbox permission information according to the permission mapping information;

[0034] In some embodiments, performing permission control and sandbox simulation testing according to the second sandbox data includes:

[0035] In response to receiving a sandbox login request or a sandbox operation request, obtaining identity information of a visiting object;

[0036] When the sandbox operation request involves sensitive operations, at least one identity authentication process is performed based on the identity information; when the identity information conforms to the second sandbox permission information, the sandbox login request or the sandbox operation request of the visiting object is allowed, and a simulation test is performed based on the second sandbox simulation data.

[0037] To achieve the above-mentioned purpose, a second aspect of an embodiment of the present application provides a data synchronization update device, the device comprising:

[0038] A real-time data acquisition module, used to acquire first updated data generated in real time from a data source;

[0039] A version identification generation module, used to determine the object to be identified from the first update data, perform version identification generation processing according to a preset identification data format and the object to be identified, and obtain version identification information of the object to be identified; wherein the version identification information is used to represent the generation time sequence between the objects to be identified generated at different times;

[0040] A version identification processing module, used to perform version identification processing on the object to be identified in the first update data according to the version identification information, to obtain second update data including the version identification information;

[0041] A mapping conversion module, configured to perform mapping conversion processing on the second update data according to a mapping conversion function to obtain third update data;

[0042] A data synchronization module, used for synchronizing the third update data to the sandbox simulation transaction environment, and determining target update data from the third update data according to the version identification information;

[0043] The data update module is used to update the current first sandbox data according to the target update data to obtain the second sandbox data, so as to perform permission control and sandbox simulation testing according to the second sandbox data in the sandbox simulation transaction environment.

[0044] To achieve the above-mentioned purpose, the third aspect of an embodiment of the present application proposes an electronic device, which includes a memory and a processor, the memory stores a computer program, and the processor implements the data synchronization update method described in the first aspect when executing the computer program.

[0045] To achieve the above objectives, the fourth aspect of an embodiment of the present application proposes a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the data synchronization update method described in the first aspect.

[0046] The data synchronization and updating method and device, electronic device and storage medium proposed in the present application, after obtaining the first update data generated in real time from the data source, determine the object to be identified from the first update data, perform version identification generation processing according to the preset identification data format and the object to be identified, and obtain version identification information of the object to be identified; wherein the version identification information is used to characterize the generation time sequence between the objects to be identified generated at different times; then, in the first update data, perform version identification processing on the object to be identified according to the version identification information, and obtain second update data including the version identification information; then, perform mapping conversion processing on the second update data according to the mapping conversion function, and obtain third update data; then, synchronize the third update data to the sandbox simulation transaction environment, and determine the target update data from the third update data according to the version identification information; finally, update the current first sandbox data according to the target update data to obtain the second sandbox data, so as to perform permission control and sandbox simulation testing according to the second sandbox data in the sandbox simulation transaction environment. By performing version identification processing on the acquired real-time first update data, second update data including version identification information can be obtained, and the second update data can be mapped and converted to obtain safe and reliable third update data; a data update version control mechanism is implemented based on the version identification information, so as to determine the latest target update data from the third update data according to the version identification information, and synchronously update the sandbox data in the sandbox simulation transaction environment; the embodiment of the present application can realize real-time, efficient, safe and reliable data synchronization update between the data source and the sandbox simulation transaction environment. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 This is an optional flow chart of the data synchronization update method provided in the embodiment of the present application;

[0048] Figure 2 yes Figure 1 A specific flow chart of step S102 in FIG.

[0049] Figure 3 yes Figure 1 Another specific flow chart of step S102 in FIG. 1 ;

[0050] Figure 4 yes Figure 1 Flow chart of step S104 in FIG.

[0051] Figure 5 yes Figure 4Flow chart of step S402 in FIG.

[0052] Figure 6 It is a structural diagram of a data synchronization update device provided in an embodiment of the present application;

[0053] Figure 7 It is a schematic diagram of the hardware structure of the electronic device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0054] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0055] It should be noted that, although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification, claims and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0056] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0057] Based on this, the embodiments of the present application provide a data synchronization update method and device, an electronic device and a storage medium, aiming to achieve real-time, efficient, safe and reliable data synchronization update between a data source and a sandbox simulation transaction environment.

[0058] The data synchronization update method and device, electronic device and storage medium provided in the embodiments of the present application are specifically described through the following embodiments. First, the data synchronization update method in the embodiments of the present application is described.

[0059] The data synchronization and update method provided in the embodiment of the present application relates to the field of financial technology. The data synchronization and update method provided in the embodiment of the present application can be applied to a terminal, can be applied to a server side, or can be software running in a terminal or a server side. In some embodiments, the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, etc.; the server side can be configured as an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application that implements the data synchronization and update method, etc., but is not limited to the above forms.

[0060] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0061] It should be noted that in each specific implementation of the present application, when it comes to the need to perform relevant processing based on data related to user identity or characteristics such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first, and the collection, use, and processing of these data will comply with relevant laws, regulations, and standards. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the embodiment of the present application will be obtained.

[0062] The embodiments of the present application are introduced below with reference to the accompanying drawings.

[0063] Figure 1 is an optional flow chart of the data synchronization update method provided in the embodiment of the present application. Figure 1The method may include but is not limited to steps S101 to S106.

[0064] Step S101, obtaining first update data generated in real time from a data source;

[0065] Step S102, determining the object to be identified from the first update data, performing version identification generation processing according to the preset identification data format and the object to be identified, and obtaining version identification information of the object to be identified; wherein the version identification information is used to represent the generation time sequence between the objects to be identified generated at different times;

[0066] Step S103, in the first update data, performing version identification processing on the object to be identified according to the version identification information, to obtain second update data including the version identification information;

[0067] Step S104, performing mapping conversion processing on the second update data according to the mapping conversion function to obtain third update data;

[0068] Step S105, synchronizing the third update data to the sandbox simulation transaction environment, and determining the target update data from the third update data according to the version identification information;

[0069] Step S106, updating the current first sandbox data according to the target update data to obtain second sandbox data, so as to perform permission control and sandbox simulation testing according to the second sandbox data in the sandbox simulation transaction environment.

[0070] Steps S101 to S106 shown in the embodiment of the present application are as follows: after obtaining the first update data generated in real time from the data source, the object to be identified is determined from the first update data, and a version identification generation process is performed according to the preset identification data format and the object to be identified to obtain version identification information of the object to be identified; wherein the version identification information is used to characterize the generation time sequence between the objects to be identified generated at different times; then, in the first update data, version identification processing is performed on the object to be identified according to the version identification information to obtain second update data including the version identification information; then, mapping conversion processing is performed on the second update data according to the mapping conversion function to obtain third update data; then, the third update data is synchronized to the sandbox simulation transaction environment, and the target update data is determined from the third update data according to the version identification information; finally, the current first sandbox data is updated according to the target update data to obtain the second sandbox data, so as to perform permission control and sandbox simulation testing according to the second sandbox data in the sandbox simulation transaction environment. By performing version identification processing on the acquired real-time first update data, second update data including version identification information can be obtained, and the second update data can be mapped and converted to obtain safe and reliable third update data; a data update version control mechanism is implemented based on the version identification information, so as to determine the latest target update data from the third update data according to the version identification information, and synchronously update the sandbox data in the sandbox simulation transaction environment; the embodiment of the present application can realize real-time, efficient, safe and reliable data synchronization update between the data source and the sandbox simulation transaction environment.

[0071] The embodiments of the present application can be customized and expanded according to different scales and needs, providing applicable solutions for different types of open banking systems to meet the needs of different customers, and bringing a more stable, secure and efficient system experience to the open banking field.

[0072] To further explain step S101, in step S101 of some embodiments, specifically, by monitoring the core data source of the open banking system, the real-time update of the source data in the data source is detected; when the real-time first update data is generated in the data source, the first update data is obtained from the data source, triggering a data update event. The data update event is used to perform the subsequent version identification generation process of step S102 and the version identification process of step S103, obtain the second update data including the version identification information, record the version identification information, and send the second update data to the message queue, so that the synchronization engine used to monitor the update status of the message queue can obtain the second update data from the message queue in time, perform the mapping conversion process in step S104 and the data synchronization in step S105.

[0073] It should be noted that the source data of the data source monitored in step S101 includes: system data and source authority data. In the open banking system, the monitored system data is not limited to personal identity information and account numbers, but also involves multiple data types such as transactions, accounts, user behavior, authority, finance, compliance, products and services, and system operation and maintenance. Specifically, system data includes but is not limited to: user identity data, business transaction data, account data, user behavior data, financial and settlement data, compliance data, product and service data. Source authority data includes: authority and authentication data.

[0074] Specifically, user identity data includes: personal identity information and account number.

[0075] Specifically, business transaction data includes: transaction record information and transaction merchant information. Transaction record information includes: transaction ID, transaction time, transaction amount, currency type, transaction status (such as success, failure, pending, etc.), transaction type (such as transfer, payment, withdrawal, etc.). Transaction merchant information includes: merchant ID, merchant name, merchant type, etc.

[0076] Specifically, account data includes: account balance information, account type information, and account status information. Account balance information includes: the current balance and available balance of each account. Account type information includes: savings account, checking account, credit account, investment account, etc. Account status information includes: account status information, such as normal, frozen, closed, etc.

[0077] Specifically, user behavior data includes: access log information and operation record information. Access log information includes: the time, location, device information, IP address, etc. of the user's access to the system. Operation record information includes: the user's operation record in the system (such as login, logout, modification of information, transfer, etc.).

[0078] Specifically, financial and settlement data include: income and expenditure data, settlement data. Income and expenditure data include: fees, commissions, interest, taxes, etc. Settlement data include: clearing and settlement data, such as transaction settlement date, settlement amount, settlement account, etc.

[0079] Specifically, compliance data includes: anti-money laundering monitoring data and compliance inspection data. Anti-money laundering monitoring data includes: data for monitoring and detecting potential money laundering activities, such as abnormal transaction patterns, frequent small transactions, large cash deposits and withdrawals, etc. Compliance inspection data includes: relevant data used to comply with regulatory requirements, such as KYC (Know Your Customer) data, customer identity verification records, tax information, etc.

[0080] Specifically, product and service data include: product information and service data. Product information includes: detailed information on products (such as loans, deposits, investment products, etc.) provided by the open bank, such as product ID, name, type, interest rate, term, fees, etc. Service data includes: data related to the services used by users, such as the number of API calls, call time, service response time, service error code, etc.

[0081] Specifically, the permission and authentication data include: user permission information and authentication information. User permission information includes: user role and permission information in the system (such as administrator, ordinary user, partner user, etc.). Authentication information includes: information used for identity authentication, such as password hashes, two-factor authentication tokens, digital certificates, etc.

[0082] It is understandable that monitoring system data in step S101 helps ensure the security, compliance, performance and user experience of the open banking system. The embodiment of the present application has been enhanced in terms of monitoring and logging. By implementing comprehensive monitoring functions, system performance, synchronization status and transaction records can be monitored in a timely manner. This helps to discover potential problems earlier and take appropriate measures to ensure the stability and reliability of the system.

[0083] To further explain step S102, version identification information is generated and recorded through step S102; the version identification information is used to characterize the generation time sequence between the objects to be identified generated at different times.

[0084] Specifically, the version identification information of the embodiment of the present application can provide a reliable reference for data synchronization and update processing, conflict resolution mechanism implementation, data audit processing, and rollback mechanism implementation. In the data synchronization and update processing, when the source data of the core data source in the open banking system needs to be synchronized to the sandbox simulation transaction environment, the version identification information is compared to determine which data needs to be updated to ensure that the data in the sandbox environment is synchronized with the latest version. When implementing the conflict resolution mechanism, when multiple users or multiple systems update data in parallel, the version identification information is used to help resolve data conflicts to ensure that each update does not overwrite other parallel operations. In the data audit processing, the version identification information records the details of each data change, including version number, modification time, etc., to facilitate subsequent audits and tracking of data change history. When implementing the rollback mechanism, when data exceptions or errors occur, you can roll back to the previous correct version based on the version identification information to ensure the correctness and stability of the data.

[0085] It is understandable that the purposes of generating version identification information are: first, to distinguish different data versions. The use of unique version identification information can effectively distinguish the data of each update, ensuring that different versions of data will not be confused when multiple data updates are processed in parallel. Second, to determine the latest status of the data: each time a new version identification is generated, it can be used to identify the latest data version to avoid using outdated or erroneous data. Third, it can perform version control: the version identification information can be rolled back to the previous version when necessary, and supports the comparison and testing of different versions of data in the sandbox simulation trading environment.

[0086] It is understandable that the purpose of recording version identification information is: first, it can track data changes; through the recorded version identification information, each data modification can be accurately tracked to know the generation time, modification operator and specific changes of each data version. Second, it is conducive to data synchronization: that is, when synchronizing data in multiple systems or sandbox simulation trading environments, the version identification information is used to determine the data that needs to be updated to ensure data consistency between different environments. Third, it can realize historical records and audits; through the version identification information, the historical versions of the retained data can be found, thereby supporting backtracking, auditing and data recovery.

[0087] Specifically, there are four preset identification data formats used in step S102, namely, four data forms of version identification information.

[0088] The first form of identification data is to use an increasing positive integer version number as the version identification information, such as 1, 2, 3. When using an increasing version number, by comparing the version numbers, the larger version number is the latest version. For example, the data of version v3 is newer than the data of version v2.

[0089] The second form of identification data is to use a timestamp as version identification information. Specifically, a timestamp of the data update time is recorded each time the data is updated, for example, 20240915120000, where '20240915120000' represents September 15, 2024 12:00:00. If the time recorded by the timestamp is the closest to the current time, then the version is the latest version.

[0090] The third form of identification data is to use a universally unique identifier (UUID) as version identification information. Using UUID to generate a globally unique identifier, such as 550e8400-e29b-41d4-a716-446655440000, can ensure the uniqueness of different version identifiers. The UUID records the time when the UUID was created. When the time when the UUID was created is the closest to the current time, the version is the latest version.

[0091] The fourth form of identification data is to use a composite identifier as version identification information, that is, to combine the timestamp and version number to form a composite identifier, such as 20240915120000-v3. It can indicate the data update time and version number at the same time. Combine the timestamp and version number to accurately determine the data version. When using a composite identifier, when the data packet versions are the same, the timestamp can be used to determine a more accurate update order.

[0092] The identification data format of the embodiments of the present application can be adjusted and optimized according to specific business scenarios. Therefore, the present application does not limit the specific form of the identification data format.

[0093] Furthermore, two specific implementations of the version identification generation process in step S102 are further described.

[0094] See also Figure 2 In some embodiments, the version identification information includes a first version identification; step S102 may include but is not limited to steps S201 to S203:

[0095] Step S201, determining at least one target update type, and determining a data field in the first update data that meets the target update type as an object to be identified;

[0096] Step S202, integrating all the objects to be identified to obtain a first data packet;

[0097] Step S203: Generate a first version identifier for the first data packet; the first version identifier is used to identify the first data packet.

[0098] In step S201 of some embodiments, the target update type indicates the data type of the data field that needs to be updated in the sandbox simulated transaction environment. The target update type can be the above-mentioned user identity data, business transaction data, account data, user behavior data, financial and settlement data, source authority data and other data types. This application does not impose specific restrictions on the selected target update type.

[0099] It is understandable that when the first update data includes multiple types of data fields, it is possible that not all types of data fields need to be synchronized to the sandbox simulation transaction environment. The tester can determine one or more target update types based on the actual needs of the sandbox simulation transaction environment, and then determine the objects to be identified; being able to selectively synchronize data is conducive to improving the efficiency and accuracy of data synchronization.

[0100] It can be understood that when the first update data includes only one type of data field and only one target update type, the object to be identified is the first update data.

[0101] In step S202 of some embodiments, all objects to be identified are integrated to obtain a first data packet, so as to facilitate overall update based on the first data packet in a sandbox simulated transaction environment, thereby improving the efficiency of data synchronization update.

[0102] In step S203 of some embodiments, a first version identifier is generated to identify the first data packet.

[0103] Through steps S201 to S203, the objects to be identified can be determined and organized into a first data packet, thereby facilitating overall update of data based on the first data packet, facilitating identification and improving the efficiency of data synchronization update.

[0104] See also Figure 3 In some embodiments, the version identification information includes a second version identification; step S102 may include but is not limited to steps S301 to S302:

[0105] Step S301, determining at least one target update type, and determining a data field in the first update data that meets the target update type as an object to be identified;

[0106] Step S302: Generate a second version identifier for each object to be identified; wherein the second version identifier is used to independently identify each object to be identified.

[0107] In step S301 of some embodiments, the target update type indicates the data type of the data field that needs to be updated in the sandbox simulation transaction environment. The target update type can be the above-mentioned user identity data, business transaction data, account data, user behavior data, financial and settlement data, source authority data and other data types. This application does not impose specific restrictions on the selected target update type. Step S301 has the same function as step S201 and will not be repeated here.

[0108] Step S302, identifying the objects to be identified one by one, thereby improving the flexibility of version identification and the flexibility of data synchronization update.

[0109] Through step S301 to step S302, the objects to be identified can be determined, and the objects to be identified can be identified one by one, thereby improving the flexibility of version identification control and data synchronization update.

[0110] In step S103 of some embodiments, specifically, when the first version identifier is obtained by adopting steps S201 to S203, the first version identifier is used to identify the first data packet. When the second version identifier is obtained by adopting steps S301 to S302, the second version identifier is used to identify each corresponding object to be identified one by one.

[0111] After the version identification information is obtained in step S102, the object to be identified is identified in step S103 to provide a reliable reference for subsequent update data.

[0112] It should be noted that the version identification information generated for each data update is used to identify different types of objects to be identified one by one, or to identify the first data packet; the selection of the identification method depends on the specific usage scenario of the data. If the data fields are closely related and are usually updated together, they are integrated into the first data packet for identification; if the data fields are likely to be updated independently, identifying the objects to be identified one by one will make the data update more flexible.

[0113] For example, when the object to be identified is personal identity information and account number data, through steps S202 to S203, the data fields of personal identity information and account number are integrated into a first data packet, and after identifying the first data packet, "first data packet + first version identification" is obtained.

[0114] For example, when the objects to be identified are personal identity information and business transaction data, in step S302, the personal identity information and business transaction data are identified one by one to obtain "personal identity information + second version identification" and "business transaction data + second version identification".

[0115] See also Figure 4 In some embodiments, step S104 may include but is not limited to steps S401 to S403:

[0116] Step S401: performing data structure analysis and data type identification and classification processing on the second update data, and determining a first data set to be mapped and converted from the second update data;

[0117] Step S402, mapping and converting the first data set according to the mapping conversion function to obtain a second data set after mapping conversion;

[0118] Step S403: convert the format of the second data set to obtain third updated data in a preset target format.

[0119] In step S401 of some embodiments, by parsing the structure of the data source, different data types (such as user information, transaction records, account data, etc.) are identified and classified. This step determines the first data set that needs to be mapped and converted, and lays the data foundation for subsequent mapping and conversion processing. This application does not impose specific restrictions on the data type in the first data set, and it can be set and selected according to actual needs.

[0120] In step S402 of some embodiments, the mapping conversion function is pre-configured to provide a reliable reference for mapping processing and conversion processing to improve processing efficiency.

[0121] In step S403 of some embodiments, the preset target format is a data format that meets the requirements of the sandbox environment, such as JSON, XML, and other structured data formats that meet the requirements of the sandbox environment. Specifically, the format conversion includes: converting data from one format to another format (for example: from JSON to XML, or from CSV to JSON).

[0122] Through step S401 to step S403, based on the mapping conversion function and format conversion, the first data set is efficiently and reliably converted into the third updated data, so as to facilitate data synchronization update in the sandbox simulation transaction environment.

[0123] Specifically, the embodiment of the present application monitors the message queue through a pre-designed synchronization engine. When the data update event is completed, the latest second update data including version identification information is obtained from the message queue, and the second update data is processed in the synchronization engine as shown in steps S401 to S403 to adapt to the format of the sandbox simulation transaction environment; and in the data mapping and conversion process, the permissions of the real environment are mapped to the sandbox environment to ensure that only users with corresponding permissions can operate data in the sandbox simulation transaction environment. Then, the synchronization engine executes step S105 to synchronize the mapped and converted data to the sandbox simulation transaction environment.

[0124] See also Figure 5 In some embodiments, step S402 may include but is not limited to steps S501 to S506:

[0125] Step S501, determining a data mapping table, a data conversion table and a permission mapping table from a mapping conversion function;

[0126] Step S502, determining first source data to be mapped, second source data to be converted, and source authority information from the first data set;

[0127] Step S503, performing data mapping processing on the first source data according to the data mapping table to obtain first target data;

[0128] Step S504, converting the second source data into second target data according to the data conversion table;

[0129] Step S505, converting the source permission information into permission mapping information according to the permission mapping table; wherein the permission mapping information is used to indicate the objects that can access the sandbox simulation trading environment and the scope of operation permissions allowed in the sandbox simulation trading environment;

[0130] Step S506: Obtain a second data set after mapping conversion according to the first target data, the second target data and the permission mapping information.

[0131] Before step S501, it also includes: defining mapping rules and conversion rules according to the requirements and data structure of the sandbox environment; forming a data mapping table and a permission mapping table based on the mapping rules, and forming a data conversion table based on the conversion rules; creating an overall mapping conversion function, combining data mapping and conversion together through the mapping conversion function, and performing mapping and conversion in sequence.

[0132] In step S501 of some embodiments, the mapping conversion function includes a data mapping table, a data conversion table and a permission mapping table; the data mapping table, the data conversion table and the permission mapping table lay a data foundation for subsequent mapping conversion.

[0133] In step S503 of some embodiments, specifically, the data mapping table is used to indicate the mapping relationship between the source data and the target data. The data mapping rules embodied in the data mapping table include: field mapping rules, data desensitization rules. Among them, the field mapping rule is: correspond the field name in the source data with the field name in the target data structure, such as: source field: customer_id, target field: sandbox_user_id. Specifically, when mapping, "customer_id" is mapped to "sandbox_user_id". The data desensitization rule is: desensitize sensitive information (such as identity card number, bank card number), and replace some characters with common characters to protect data privacy.

[0134] In step S504 of some embodiments, specifically, the data conversion table is used to indicate the conversion relationship between the source data and the target data. The data conversion rules reflected in the data conversion table include: data type conversion and data value conversion rules. Among them, data type conversion is: converting the data type in the source data to the target data type. For example: source data type: timestamp, target data type: datetime. Specifically, during conversion, the 'timestamp' type in the source data is converted to the 'datetime' type required by the sandbox environment. The data value conversion rule is: converting the value of a specific field; such as converting the currency unit from "USD" to "CNY".

[0135] In step S505 of some embodiments, specifically, the permission mapping table is used to indicate the mapping relationship between the source permission information and the target permission information. The permission mapping rules reflected in the data conversion table are: role mapping rules and permission mapping rules. The role mapping rule is: map the real environment role to the sandbox environment role, specifically, the real environment roles are: admin, user; correspondingly, the sandbox environment mapping roles are: sandbox_admin, sandbox_user. The permission mapping rule is: map the permissions in the real environment to the sandbox environment; for example, map all operation permissions, read and write transaction data permissions.

[0136] The overall specific process of permission mapping provided by the embodiment of the present application is further explained. First, the permission information of the real environment is extracted, that is, the permission information of the user is extracted from the permission management system of the production environment, such as user roles (administrators, ordinary users, etc.), specific permissions (read, write, execute, etc.), and access scopes (accounts, transactions, reports, etc.). Then, a sandbox permission model is created: in the sandbox environment, a permission model corresponding to the production environment is defined, including the definition of roles and permissions, permission granularity (such as field-level, record-level, object-level permission control), and the setting of permission groups; then, a permission mapping table is created to map the permissions in the real environment to the sandbox environment; then, permission synchronization and conversion are performed: according to the permission mapping table, the permissions in the real environment are synchronized to the sandbox environment. Through the mapping rules, the sandbox environment can generate corresponding user roles and permission settings to ensure that users can only perform their authorized operations in the sandbox environment; in addition, permission verification and dynamic update are implemented: in the sandbox environment, user operations are dynamically monitored and verified according to the mapped permission information to prevent unauthorized operations. At the same time, if the permissions of the real environment change (such as changes in role permissions or the addition of new permissions), the permission information of the sandbox environment also needs to be updated in a timely manner to maintain permission consistency.

[0137] Through step S505, the user permissions and role settings in the production environment are converted into corresponding permissions and roles in the sandbox simulation transaction environment to ensure that the user's operations in the sandbox environment are consistent with their permissions in the real environment.

[0138] Through step S506, based on the first target data, the second target data and the permission mapping information, a second data set after mapping conversion is obtained, and the mapping conversion is completed.

[0139] Through steps S501 to S506, a data mapping conversion mechanism is implemented, which can effectively convert data from source data to target data required by the sandbox simulation transaction environment. The mapping conversion mechanism ensures data consistency between the data source and the sandbox simulation transaction environment, meeting the requirements of the open banking system.

[0140] It should be noted that the above-mentioned data mapping and conversion mechanism is mainly used to convert data from one format to another and to keep the data compatible and consistent between different environments, but it is usually unable to defend against data leakage, tampering or other forms of security threats alone. Therefore, it is difficult to fully protect data security by relying solely on data mapping and conversion mechanisms. Therefore, the data mapping and conversion mechanism itself is difficult to directly ensure the security of data. To ensure the security of data, it is also necessary to combine encryption and decryption mechanisms and data integrity verification processing.

[0141] In some embodiments, before step S105, the data synchronization update method further includes: integrating the third update data into a second data packet, performing overall data verification on the second data packet to obtain a verification value; encrypting or encoding the second data packet and the verification value based on a preset encryption algorithm to obtain an encrypted data packet; synchronously sending the encrypted data packet to the sandbox simulation transaction environment to perform decryption or decoding and integrity verification in the sandbox simulation transaction environment; and confirming whether the third update data is complete and correct. Ensure the security of data transmission and improve data security.

[0142] It is understood that encryption algorithms protect sensitive information when data is transmitted or stored. Specifically, the national encryption (SM2 / SM4) is used to encrypt and decrypt sensitive data.

[0143] It is understandable that when using encoding technology, specifically, using Base64 encoding or other forms of encoding, the data is converted into a format that is not easily read directly to avoid accidental disclosure or tampering during transmission.

[0144] In addition, it should be noted that, without involving encryption algorithms, the data mapping conversion mechanism of the present application itself indirectly ensures data security. First, through the data desensitization rules, sensitive information is desensitized. For example, part of the characters of the ID card number is replaced with the universal character "*", making it difficult to identify specific identity information. Secondly, through the permission control mechanism in the mapping process, it is ensured that only users with appropriate permissions can access specific data; such as, when mapping data, the user's role information is mapped together, and only operations that meet permissions are allowed in the sandbox simulation transaction environment. In addition, data verification and integrity verification are implemented; during the mapping and conversion process, a data verification step is added to generate and verify data hash values ​​(MD5, SHA-256, etc.) to ensure that the data is not tampered with during transmission or storage. Although the data mapping and conversion mechanism itself cannot fully guarantee the security of the data, combined with strategies such as data desensitization, permission mapping, and data verification, data security can be improved to a certain extent.

[0145] It is understandable that the data security of the embodiments of the present application is high and the privacy protection is better, and the security of data is emphasized in data mapping and conversion. By designing data desensitization and permission control mechanisms, sensitive data in the simulated transaction environment is protected, the risk of sensitive information leakage is avoided, and the compliance requirements of data privacy are met.

[0146] In step S105 of some embodiments, the third update data is synchronized to the sandbox simulation transaction environment through the synchronization engine, and the latest target update data is determined based on the version identification information, laying a data foundation for updating in the sandbox simulation transaction environment.

[0147] The embodiment of the present application realizes instant synchronization between real-time data updates and the sandbox simulated trading environment by introducing an efficient synchronization engine. Developers and partners can always use the latest data in simulated transactions, avoiding data inconsistency issues, thereby improving the accuracy and efficiency of testing and development.

[0148] In step S106 of some embodiments, the target update data includes system data and permission mapping information, and the first sandbox data includes: first sandbox simulation data and first sandbox permission information; further illustrating step S106, wherein the current first sandbox data is updated according to the target update data to obtain the second sandbox data, may include but is not limited to steps S601 to S602:

[0149] Step S601: when the target update data includes system data, the current first sandbox simulation data is updated according to the system data to obtain second sandbox simulation data;

[0150] Step S602: When the target update data includes permission mapping information, the current first sandbox permission information is updated to obtain second sandbox permission information according to the permission mapping information.

[0151] Through step S601 to step S602, the sandbox simulation data and sandbox permission information are updated in the sandbox simulation transaction environment, and data synchronization is achieved between the data source and the sandbox simulation transaction environment.

[0152] In step S106 of some embodiments, performing permission control and sandbox simulation testing according to the second sandbox data may include but is not limited to steps S701 to S702:

[0153] Step S701: in response to receiving a sandbox login request or a sandbox operation request, obtaining identity information of a visiting object;

[0154] Step S702: When the sandbox operation request involves sensitive operations, at least one identity authentication process is performed based on the identity information. When the identity information conforms to the second sandbox permission information, the sandbox login request or sandbox operation request of the visiting object is allowed, and a simulation test is performed based on the second sandbox simulation data.

[0155] In step S702 of some embodiments, in the sandbox simulated transaction environment, identity authentication is performed to ensure the authenticity of the user's identity and match it with its authority to ensure the authenticity and security of the user's identity. Only one identity authentication processing method can be used, or multiple identity authentication processing methods can be combined for identity authentication, and this application does not make specific restrictions on this.

[0156] Specifically, identity authentication processing methods include: account and password verification, multi-factor authentication, biometric information verification, digital certificate verification, and risk-based authentication.

[0157] Among them, account and password verification means: each user has unique account information, and identity authentication is performed by entering the correct username and password. In order to improve security, the system supports strong password policies and regular password updates.

[0158] Multi-factor authentication means requiring users to provide at least two different types of authentication information. This greatly improves the security of the system. Verification factors include: SMS or email verification code: After the user logs in, the system will send a one-time verification code to the user's mobile phone or email, and the user must enter the verification code to complete the verification. Use a dynamic password token, using a dynamic verification code generated by a mobile application, and the user must enter the correct verification code within a specified time.

[0159] Biometric information verification means: supporting biometric verification to provide a higher level of security, especially for users who need high-level permissions. Including: face recognition, face scanning verification through the camera when logging in or performing important operations; fingerprint recognition: obtaining user fingerprint information through a fingerprint scanning device for verification.

[0160] Digital certificate verification means that advanced users can authenticate their identities through digital certificates. Digital certificates are based on the public key infrastructure system to ensure the uniqueness and immutability of user identities.

[0161] Risk-based authentication means judging the risk of an operation based on the user's operating habits, IP address, device type, etc. If an anomaly is detected (such as a change in the login device, an abnormal geographic location, etc.), the user is required to provide additional authentication information.

[0162] In step S702 of some embodiments, during simulation testing, an intuitive and easy-to-navigate user interface is designed to allow users to trigger sandbox simulation transactions with one click. Users do not need to manually enter test data, and the system will automatically generate a sandbox simulation transaction environment. At the same time, an operation history record is provided to allow users to view previous operations, and a revocation function is provided to allow users to revoke recent operations. Through an intuitive interface and friendly operation process, developers and partners can easily use the system.

[0163] Through step S701 to step S702, safe and efficient permission control and sandbox simulation testing are achieved. It can effectively achieve efficient synchronization between real-time data updates and sandbox simulation transaction environments, provide a more realistic testing environment, and accurately simulate real transaction processes in the sandbox environment, provide a complete simulation process, and enable developers to test and verify new functions and solve problems more quickly, thereby greatly improving development efficiency and accuracy. The solution of real-time data synchronization and sandbox simulation transactions can significantly reduce the testing cycle, shorten product development and release time, accelerate the testing and development process, and enable businesses to bring products to market more quickly. It is also conducive to reducing the human resource costs of development and testing, while reducing the cost of problems, improving efficiency, and realizing the testing and development process more quickly.

[0164] The overall permission control mechanism provided by the embodiment of the present application is further described. The permission control mechanism of the present application includes: multi-factor permission verification, dynamic permission mapping and synchronization mechanism, fine-grained permission control mechanism, and access control based on roles and attributes; ensuring that the user's operations in the sandbox simulated trading environment are consistent with their permissions in the real environment.

[0165] Specifically, multi-factor permission verification means: combining multi-factor authentication with permission mapping to ensure that only legitimate users can obtain the corresponding permissions. For example, when a user attempts a sensitive operation (such as data export or deletion) in a sandbox environment, additional authentication (such as SMS verification code or biometric verification) is required.

[0166] Specifically, the fine-grained permission control mechanism refers to: increasing the granularity of permissions and refining permission control to the field level, record level or operation level. For example, some users can only view transaction data in the sandbox environment but cannot modify it; some users can modify transaction data but cannot delete it; ordinary users can only view account data under their own names, and administrators can view and modify all account data. The permission rule engine is used to ensure flexibility in the permission mapping process. For some sensitive operations (such as data export or high-privilege operations), further permission verification is required. Through permission mapping rules, fine-grained permission control policies are automatically generated and dynamically applied to data access and operations in the sandbox environment.

[0167] Specifically, the dynamic permission mapping and synchronization mechanism refers to: permissions are dynamically mapped between the real environment and the sandbox environment through real-time synchronization. Among them, the dynamic permission mapping and synchronization mechanism includes: real-time synchronization permission change mode and event-driven permission mapping mode. The real-time synchronization permission change mode is used to: when the user's permissions change, the permissions in the sandbox environment will also be updated immediately to ensure the consistency of permissions. Specifically, when the permissions of the real environment change, the sandbox environment is immediately notified to update the permissions through API or message queue, etc., to ensure that the permission information of the sandbox environment is synchronized with the real environment. The event-driven permission mapping method is used to: trigger a permission check event every time the user attempts to operate data, and ensure that the permissions are dynamically updated in an event-driven manner. For example, when a user logs in or requests to access the sandbox environment, the system verifies their permissions in real time. And when the user operates, the system verifies the user's permissions in real time to ensure that the user can only perform operations within his or her permissions. For example, when a user attempts to perform sensitive transaction operations, the system will dynamically check his or her permissions and decide whether to allow the operation based on the permission mapping rules.

[0168] Specifically, the access control mechanism based on roles and attributes includes: role-based access control method, and access control method based on other attributes. The role-based access control method is used for: in the real environment, users are assigned certain roles (such as administrators, users, etc.), which define the scope of users' permissions in the system. When users access the sandbox environment, the system will map the roles in the real environment to the corresponding roles in the sandbox environment based on the predefined permission mapping table to ensure role consistency. The access control method based on other attributes is used for: access control based on attributes such as time, location, equipment, and operating environment. For example, users can only access specific data during working hours or on a specific network. This control method makes permission mapping more flexible and helps to refine the control of the user's operating environment.

[0169] The embodiments of the present application ensure that users can only perform authorized operations in a sandbox environment through multi-factor permission verification, dynamic permission mapping and synchronization mechanism, fine-grained permission control mechanism, and role- and attribute-based access control, while supporting real-time permission synchronization; and ensure the security and flexibility of permissions in the sandbox environment, overcome the shortcomings of traditional methods, and effectively avoid permission risks.

[0170] See also Figure 6 The embodiment of the present application also provides a data synchronization update device, which can implement the above data synchronization update method, and the device includes:

[0171] A real-time data acquisition module, used to acquire first updated data generated in real time from a data source;

[0172] A version identification generation module, used to determine the object to be identified from the first update data, perform version identification generation processing according to a preset identification data format and the object to be identified, and obtain version identification information of the object to be identified; wherein the version identification information is used to represent the generation time sequence between the objects to be identified generated at different times;

[0173] A version identification processing module, used to perform version identification processing on the object to be identified in the first update data according to the version identification information, to obtain second update data including the version identification information;

[0174] A mapping conversion module, used for performing mapping conversion processing on the second update data according to the mapping conversion function to obtain third update data;

[0175] A data synchronization module, used to synchronize the third update data to the sandbox simulation transaction environment, and determine the target update data from the third update data according to the version identification information;

[0176] The data update module is used to update the current first sandbox data according to the target update data to obtain the second sandbox data, so as to perform permission control and sandbox simulation testing according to the second sandbox data in the sandbox simulation transaction environment.

[0177] Therefore, after the data synchronization and updating device uses the real-time data acquisition module to obtain the first update data generated in real time from the data source, the version identification generation module determines the object to be identified from the first update data, performs version identification generation processing according to the preset identification data format and the object to be identified, and obtains the version identification information of the object to be identified; wherein the version identification information is used to characterize the generation time sequence between the objects to be identified generated at different times; then, the version identification processing module performs version identification processing on the object to be identified in the first update data according to the version identification information, and obtains the second update data including the version identification information; then, the mapping conversion module performs mapping conversion processing on the second update data according to the mapping conversion function, and obtains the third update data; then, the third update data is synchronized to the sandbox simulation transaction environment through the data synchronization module, and the target update data is determined from the third update data according to the version identification information; finally, the data update module updates the current first sandbox data according to the target update data to obtain the second sandbox data, so as to perform permission control and sandbox simulation testing according to the second sandbox data in the sandbox simulation transaction environment. By performing version identification processing on the acquired real-time first update data, second update data including version identification information can be obtained, and the second update data can be mapped and converted to obtain safe and reliable third update data; a data update version control mechanism is implemented based on the version identification information, so as to determine the latest target update data from the third update data according to the version identification information, and synchronously update the sandbox data in the sandbox simulation transaction environment; the embodiment of the present application can realize real-time, efficient, safe and reliable data synchronization update between the data source and the sandbox simulation transaction environment.

[0178] The specific implementation of the data synchronization update device is basically the same as the specific implementation of the above-mentioned data synchronization update method, and will not be repeated here.

[0179] The embodiment of the present application also provides an electronic device, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the above data synchronization update method when executing the computer program. The electronic device can be any smart terminal including a tablet computer, a car computer, etc.

[0180] See also Figure 7 , Figure 7 The hardware structure of an electronic device of another embodiment is illustrated, and the electronic device includes:

[0181] The processor 701 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0182] The memory 702 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 702 can store an operating system and other applications. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 702, and the processor 701 calls and executes the data synchronization update method of the embodiment of this application;

[0183] Input / output interface 703, used to implement information input and output;

[0184] Communication interface 704, used to realize communication interaction between the device and other devices, which can be realized through wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WI FI, Bluetooth, etc.);

[0185] A bus 705 that transmits information between the various components of the device (e.g., the processor 701, the memory 702, the input / output interface 703, and the communication interface 704);

[0186] The processor 701 , the memory 702 , the input / output interface 703 and the communication interface 704 are connected to each other in communication within the device via a bus 705 .

[0187] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned data synchronization update method is implemented.

[0188] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0189] The data synchronization update method, data synchronization update device, electronic device and storage medium provided by the embodiments of the present application obtain first update data generated in real time from a data source, determine the object to be identified from the first update data, perform version identification generation processing according to a preset identification data format and the object to be identified, and obtain version identification information of the object to be identified; wherein the version identification information is used to characterize the generation time sequence between the objects to be identified generated at different times; then, in the first update data, perform version identification processing on the object to be identified according to the version identification information, and obtain second update data including the version identification information; then, perform mapping conversion processing on the second update data according to a mapping conversion function, and obtain third update data; then, synchronize the third update data to a sandbox simulation transaction environment, and determine target update data from the third update data according to the version identification information; finally, update the current first sandbox data according to the target update data to obtain second sandbox data, so as to perform permission control and sandbox simulation testing according to the second sandbox data in the sandbox simulation transaction environment. By performing version identification processing on the acquired real-time first update data, second update data including version identification information can be obtained, and the second update data can be mapped and converted to obtain safe and reliable third update data; a data update version control mechanism is implemented based on the version identification information, so as to determine the latest target update data from the third update data according to the version identification information, and synchronously update the sandbox data in the sandbox simulation transaction environment; the embodiment of the present application can realize real-time, efficient, safe and reliable data synchronization update between the data source and the sandbox simulation transaction environment.

[0190] The embodiments described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0191] Those skilled in the art will appreciate that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.

[0192] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, i.e., may be located in one place, or may be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. It will be understood by those of ordinary skill in the art that all or some of the steps, systems, and functional modules / units in the devices disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof.

[0193] In addition, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus that includes a series of steps or elements is not necessarily limited to those steps or elements explicitly listed, but may include other steps or elements not explicitly listed or inherent to such process, method, product, or apparatus.

[0194] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "At least one of the following (items)" or similar expressions refers to any combination of these items, including any combination of single items (items) or plural items (items). For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0195] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0196] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0197] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including multiple instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store programs.

[0198] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, but the scope of the rights of the present invention is not limited thereto. Any modification, equivalent substitution and improvement made by a person skilled in the art without departing from the scope and essence of the present invention should be within the scope of the rights of the present invention.

Claims

1. A data synchronization update method, characterized in that: The method comprises: Acquire first updated data generated in real time from a data source; Determine the object to be identified from the first update data, perform version identification generation processing according to a preset identification data format and the object to be identified, and obtain version identification information of the object to be identified; wherein the version identification information is used to represent the generation time sequence between the objects to be identified generated at different times; In the first update data, version identification processing is performed on the object to be identified according to the version identification information to obtain second update data including the version identification information; Performing mapping conversion processing on the second update data according to a mapping conversion function to obtain third update data; Synchronize the third update data to the sandbox simulation transaction environment, and determine the target update data from the third update data according to the version identification information; The current first sandbox data is updated according to the target update data to obtain the second sandbox data, so as to perform permission control and sandbox simulation testing according to the second sandbox data in the sandbox simulation transaction environment.

2. The data synchronization update method according to claim 1, characterized in that: The version identification information includes a first version identification; the object to be identified is determined from the first update data, and a version identification generation process is performed according to a preset identification data format and the object to be identified to obtain the version identification information of the object to be identified, including: Determine at least one target update type, and determine a data field in the first update data that matches the target update type as the object to be identified; Integrate all the objects to be identified to obtain a first data packet; A first version identifier is generated for the first data packet; the first version identifier is used to identify the first data packet.

3. The data synchronization update method according to claim 1, characterized in that: The version identification information includes a second version identification; the determining of the object to be identified from the first update data, performing version identification generation processing according to a preset identification data format and the object to be identified, and obtaining the version identification information of the object to be identified includes: Determine at least one target update type, and determine a data field in the first update data that matches the target update type as the object to be identified; The second version identifier is generated for each of the objects to be identified; wherein the second version identifier is used to independently identify each of the objects to be identified.

4. The data synchronization updating method according to claim 1, characterized in that: The performing mapping conversion processing on the second update data according to the mapping conversion function to obtain third update data includes: Performing data structure analysis and data type identification and classification processing on the second update data, and determining a first data set to be mapped and converted from the second update data; According to the mapping conversion function, mapping and converting the first data set are performed to obtain a second data set after mapping conversion; The second data set is format converted to obtain third updated data whose data format is a preset target format.

5. The data synchronization update method according to claim 4, characterized in that: The step of performing mapping and conversion processing on the first data set according to the mapping conversion function to obtain a second data set after mapping conversion includes: Determine a data mapping table, a data conversion table and a permission mapping table from the mapping conversion function; Determining first source data to be mapped, second source data to be converted, and source authority information from the first data set; According to the data mapping table, performing data mapping processing on the first source data to obtain first target data; According to the data conversion table, converting the second source data into second target data; According to the permission mapping table, the source permission information is converted into the permission mapping information; wherein the permission mapping information is used to indicate the objects that can access the sandbox simulation trading environment and the scope of operation permissions allowed in the sandbox simulation trading environment; According to the first target data, the second target data and the permission mapping information, the second data set after mapping conversion is obtained.

6. The data synchronization update method according to claim 1, characterized in that: The target update data includes system data and permission mapping information, and the first sandbox data includes: first sandbox simulation data and first sandbox permission information; The updating of the current first sandbox data according to the target update data to obtain the second sandbox data includes: When the target update data includes the system data, the current first sandbox simulation data is updated to obtain second sandbox simulation data according to the system data; When the target update data includes the permission mapping information, the current first sandbox permission information is updated to obtain second sandbox permission information according to the permission mapping information.

7. The data synchronization update method according to claim 6, characterized in that: The performing permission control and sandbox simulation test according to the second sandbox data includes: In response to receiving a sandbox login request or a sandbox operation request, obtaining identity information of a visiting object; When the sandbox operation request involves sensitive operations, at least one identity authentication process is performed based on the identity information; when the identity information conforms to the second sandbox permission information, the sandbox login request or the sandbox operation request of the visiting object is allowed, and a simulation test is performed based on the second sandbox simulation data.

8. A data synchronization update device, characterized in that: The device comprises: A real-time data acquisition module, used to acquire first updated data generated in real time from a data source; A version identification generation module, used to determine the object to be identified from the first update data, perform version identification generation processing according to a preset identification data format and the object to be identified, and obtain version identification information of the object to be identified; wherein the version identification information is used to represent the generation time sequence between the objects to be identified generated at different times; A version identification processing module, used to perform version identification processing on the object to be identified in the first update data according to the version identification information, to obtain second update data including the version identification information; A mapping conversion module, configured to perform mapping conversion processing on the second update data according to a mapping conversion function to obtain third update data; A data synchronization module, used for synchronizing the third update data to the sandbox simulation transaction environment, and determining target update data from the third update data according to the version identification information; The data update module is used to update the current first sandbox data according to the target update data to obtain the second sandbox data, so as to perform permission control and sandbox simulation testing according to the second sandbox data in the sandbox simulation transaction environment.

9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, the memory stores a computer program, and the processor implements the data synchronization update method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the data synchronization update method according to any one of claims 1 to 7 is implemented.

Images