Data Migration Method and Device Applied to ETC Sub-branch Receiving

Abstract

The present invention discloses a data migration method and device applied to the collection of ETC branch banks' upward data, which relates to the technical field of automatic programming. The method includes: according to a pre-configured file, auditing and processing the mapping rule document between the branch bank's external connection subsystem P5 and the product service J2EE platform P8 to obtain a document auditing result; according to the pre-configured file, auditing and processing the mapping rules for the branch bank's migrated data to obtain a mapping auditing result; preparing an upward-embedded script for the branch bank and conducting a business continuity test to obtain a business continuity test result; checking the accuracy of business parameters and scripts to obtain a checking result; and starting to migrate the ETC branch bank's clearing data to the head office system according to the document auditing result, the mapping auditing result, the business continuity test result, and the checking result. The present invention can ensure business continuity and data consistency during the data migration process when the ETC branch bank's data is collected upward.

Description

Technical Field

[0001] The present invention relates to the technical field of automatic programming, and particularly to a data migration method and device applied to the data collection of ETC branch banks from the upper level Background Art

[0002] This section aims to provide background or context for the embodiments of the present invention described in the claims. The description herein is not admitted to be prior art merely because it is included in this section.

[0003] Currently, due to the expansion of business volume, performance problems have emerged in the financial system, and many institutions are faced with migrating the data of the system to a reconfigured system with better performance. In the current data migration solutions, there is no reasonable analysis and planning for the migrated data, which may lead to different migration environments when migrating to the new system, resulting in missing data; the business is unreasonable, and there are deviations from the requirements of customers; the rehearsal of the migration process is insufficient, and the business continuity cannot be achieved during the migration process. The current data migration methods generally include: receiving a data migration request, determining a reconfigured system according to the request; determining a migration object according to the request, and determining an associated object associated with the migration object; fusing to determine an object to be processed; determining a migration scenario, and according to the object scenario and the associated object, establishing a call interface with the first object in the reconfigured system, processing the first object, determining the object to be processed with non-real-time characteristics as the second object, obtaining the data to be migrated of the second object, and migrating the data to be migrated to the reconfigured system. However, for financial systems such as ETC, business connectivity and data consistency are particularly important. General migration methods cannot guarantee business connectivity and data consistency. In the specific environment of ETC branch banks collecting data from the upper level, the requirement docking between the branch-specific business system and the head office system also needs to be considered. Currently, in order to achieve centralized management and enable the existing head office ETC system to meet the business requirements of branch banks, the branch banks and the head office system implement "version independence, service interaction", and the head office ETC (Electronic Toll Collection) is carrying out the data collection of branch ETC. However, it is impossible to guarantee business connectivity and data consistency during the data collection of ETC branch banks. Summary of the Invention

[0004] Embodiments of the present invention provide a data migration method applied to the data collection of ETC branch banks from the upper level, so as to ensure business connectivity and data consistency during the data migration process when ETC branch banks collect data from the upper level. The method includes:

[0005] According to a pre-configured file, auditing and processing a mapping rule document of the branch external connection subsystem P5 and the product service J2EE platform P8 to obtain a document auditing result; according to the pre-configured file, auditing and processing a mapping rule of the branch migration data to obtain a mapping auditing result;

[0006] Prepare the branch's embedded scripts for business continuity testing and obtain the business continuity test results;

[0007] Check the accuracy of business parameters and scripts and obtain the verification results;

[0008] Based on the document review results, mapping review results, business continuity test results and verification results, the ETC branch clearing data was migrated to the head office system.

[0009] In one embodiment, according to the pre-configured file, the mapping rule document between the branch external liaison subsystem P5 and the product service J2EE platform P8 is reviewed and processed to obtain the document review results, including: whether the branch specific field mapping is accurate, whether the field length is too long, and whether the amount unit is correct.

[0010] In one embodiment, based on the pre-configured file, the mapping rule document between the branch external liaison subsystem P5 and the product service J2EE platform P8 is reviewed and processed to obtain the document review result, including: reviewing whether the mandatory fields required by P8 have values.

[0011] In one embodiment, based on the pre-configured file, the mapping rule document between the branch external liaison subsystem P5 and the product service J2EE platform P8 is reviewed and processed to obtain the document review result, including: reviewing whether the attribute values ​​required by the return file correspond to those in the payment request file and whether they are synchronously uploaded.

[0012] In one embodiment, based on the pre-configuration file, the mapping rule document of the branch external liaison subsystem P5 and the product service J2EE platform P8 is reviewed and processed to obtain the document review results, including: reviewing whether the code value of the field mapped from the branch field to the field in the head office field is consistent with the data dictionary, and whether to perform escape for the branch.

[0013] In one embodiment, the branch migration data mapping rules are reviewed and processed according to the pre-configured file to obtain the mapping review results, including: for the feature system arrears data, if the customer corresponding to the arrears data has terminated the contract, branch migration is not recommended, and the feature system is recommended to handle it by itself.

[0014] In one embodiment, the branch migration data mapping rules are audited and processed according to the pre-configured file to obtain the mapping audit results, including: if the branch requires deduplication of historical data, the data will be migrated to the running key value table.

[0015] In one embodiment, the branch migration data mapping rules are audited and processed according to the pre-configured file to obtain the mapping audit results, including: auditing the historical deduction success data of the characteristic system for post-migration customer query.

[0016] In one embodiment, the migrated business data includes contracts, blacklists, liquidations, overdue payment supplements, and historical data of terminated contracts.

[0017] In one embodiment, prepare the pre-buried script for branch consolidation, conduct business continuity tests, and obtain the business continuity test results, including:

[0018] According to the preset business rules, the branch migrates all contract, liquidation, and blacklist data to the contract library and liquidation library;

[0019] The branch obtains the real files of the most recent N days from production and uploads them to the head office to initiate batch verification; N is a positive integer greater than or equal to 1;

[0020] Check the details that fail the verification for each batch, the reasons for failure, and the number of detailed records, and feedback them to the branch for confirmation of whether they meet the expectations. If so, ask the branch to make adjustments.

[0021] An embodiment of the present invention also provides a data migration device applied to the ETC branch consolidation to ensure business connectivity and data consistency during the data migration process when the ETC branch is consolidated. The device includes:

[0022] The analysis phase audit unit is used to, according to the pre-configured file, audit and process the mapping rule document between the branch external connection subsystem P5 and the product service J2EE platform P8 to obtain the document audit result; according to the pre-configured file, audit and process the branch migration data mapping rule to obtain the mapping audit result;

[0023] The test phase unit is used to prepare the pre-buried script for branch consolidation, conduct business continuity tests, and obtain the business continuity test results;

[0024] The on-line phase verification unit is used to verify the accuracy of business parameters and scripts to obtain the verification result;

[0025] The data migration unit is used to start migrating the ETC branch liquidation data to the head office system according to the document audit result, mapping audit result, business continuity test result, and verification result.

[0026] In one embodiment, the analysis phase audit unit is specifically used to: audit whether the mapping of specific fields in the branch is accurate, whether the field length is exceeded, and whether the monetary unit is correct.

[0027] In one embodiment, the analysis phase audit unit is specifically used to: audit whether there are values for the required input fields required by P8.

[0028] In one embodiment, the analysis phase audit unit is specifically used to: audit whether the attribute values required by the feedback file are synchronously uploaded in the payment request file.

[0029] In one embodiment, the review unit in the analysis phase is specifically used to review whether the code value of the field in the branch field mapped to the field in the head office field is consistent with the data dictionary, and whether to perform branch escape.

[0030] In one embodiment, the review unit in the analysis phase is specifically used for: for the overdue payment data of the feature system, if the customer corresponding to the overdue payment data has terminated the contract, branch migration is not recommended, and it is recommended that the feature system handle it by itself.

[0031] In one embodiment, the analysis phase audit unit is specifically used to: if the branch requires deduplication of historical data, migrate the data to the running key value table.

[0032] In one embodiment, the review unit in the analysis phase is specifically used to review the historical successful deduction data of the characteristic system for post-migration customer query.

[0033] In one embodiment, the testing phase unit is specifically used for:

[0034] According to the preset business rules, the branch will migrate all contract, clearing and blacklist data to the contract library and clearing library;

[0035] The branch obtains the real documents of the last N days from production and sends them to the head office to initiate batch verification; N is a positive integer greater than or equal to 1;

[0036] Check the details of each batch that failed the verification, the reasons for failure and the number of details, and feedback to the branch. Ask the branch to confirm whether it meets expectations. If so, ask the branch to make adjustments.

[0037] An embodiment of the present invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the data migration method collected by the ETC branch when executing the computer program.

[0038] An embodiment of the present invention also provides a computer-readable storage medium, which stores a computer program for executing the above-mentioned data migration method applied to the ETC branch.

[0039] In the embodiment of the present invention, the data migration scheme applied to the ETC branch collection is compared with the technical scheme in the prior art, by: reviewing and processing the mapping rule document of the branch external liaison subsystem P5 and the product service J2EE platform P8 according to the pre-configuration file to obtain the document review result; reviewing and processing the branch migration data mapping rule according to the pre-configuration file to obtain the mapping review result; preparing the branch collection embedded script, performing business continuity test, and obtaining the business continuity test result; verifying the accuracy of business parameters and scripts to obtain the verification result; and starting to migrate the ETC branch clearing data to the head office system according to the document review result, the mapping review result, the business continuity test result and the verification result, thereby ensuring the business continuity and data consistency in the data migration process when the ETC branch is collected. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the prior art descriptions. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0041] Figure 1 It is a flowchart of the data migration method applied to the ETC branch in an embodiment of the present invention;

[0042] Figure 2 A schematic diagram of a flow chart of reviewing and processing branch migration data mapping rules in an embodiment of the present invention;

[0043] Figure 3 It is a flowchart of a detailed implementation method of the test phase in an embodiment of the present invention;

[0044] Figure 4 It is a structural schematic diagram of a data migration device used in an ETC branch in an embodiment of the present invention;

[0045] Figure 5 Schematic diagram of the structure of a computer device in an embodiment of the present invention. DETAILED DESCRIPTION

[0046] To make the purpose, technical solution and advantages of the embodiments of the present invention more clear, the embodiments of the present invention are further described in detail below in conjunction with the accompanying drawings. Here, the exemplary embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0047] Before introducing the embodiments of the present invention, the terms involved in the embodiments of the present invention are first introduced.

[0048] ETC Sub-branch Collection: The data of the ETC clearing module in the sub-branch is migrated and collected to the head office system. The head office version is separated from the sub-branch deployment, and the data is uniformly managed.

[0049] Figure 1 It is a schematic flow chart of the data migration method applied in the ETC sub-branch collection in the embodiment of the present invention. As Figure 1 shown, the method includes the following steps:

[0050] Step 101: According to the pre-configured file, review the mapping rule document between the sub-branch external connection subsystem P5 and the product service J2EE platform P8 to obtain the document review result; according to the pre-configured file, review the mapping rule of the sub-branch migration data to obtain the mapping review result;

[0051] Step 102: Prepare the pre-buried script for sub-branch collection and conduct a business continuity test to obtain the business continuity test result;

[0052] Step 103: Check the accuracy of business parameters and scripts to obtain the check result;

[0053] Step 104: Start migrating the ETC sub-branch clearing data to the head office system according to the document review result, mapping review result, business continuity test result and check result.

[0054] The embodiment of the present invention provides a data migration method applied in the ETC sub-branch collection, which ensures business continuity and data consistency during the data migration process when the ETC sub-branch is collected. The following is a detailed introduction to each step involved in this method.

[0055] Specifically, during the migration process, the special requirements of the sub-branch for the system need to be considered. The migration data involved includes contracts, blacklists, clearing, overdue payment supplements, and historical data of terminated contracts. Communicate with the sub-branch to understand whether the existing ETC system can meet the business needs of the sub-branch. If so, follow the subsequent standard process; if there are differences, it is necessary to clarify how the sub-branch will handle it. The first step in the embodiment of the present invention is to dock the requirements. The main steps in the migration part include:

[0056] First, introduce the steps in the analysis of differences stage, the comparison of business and technical differences between the head office and sub-branch ETC clearing modules, that is, the above step 101.

[0057] Specifically, in the analysis stage, compare the business and technical differences between the head office and sub-branch ETC clearing modules; review the mapping rule document between sub-branch P5 and P8; review the mapping rule of sub-branch migration data. The following is a detailed introduction to step 101.

[0058] 1. First, introduce the review of the mapping rule document between sub-branch P5 and P8.

[0059] In one embodiment, according to the pre-configured file, the mapping rule document between the branch external liaison subsystem P5 and the product service J2EE platform P8 is reviewed and processed to obtain the document review results, including: whether the branch specific field mapping is accurate, whether the field length is too long, and whether the amount unit is correct.

[0060] In one embodiment, based on the pre-configured file, the mapping rule document between the branch external liaison subsystem P5 and the product service J2EE platform P8 is reviewed and processed to obtain the document review result, including: reviewing whether the mandatory fields required by P8 have values.

[0061] In one embodiment, based on the pre-configured file, the mapping rule document between the branch external liaison subsystem P5 and the product service J2EE platform P8 is reviewed and processed to obtain the document review result, including: reviewing whether the attribute values ​​required by the return file correspond to those in the payment request file and whether they are synchronously uploaded.

[0062] In one embodiment, based on the pre-configuration file, the mapping rule document of the branch external liaison subsystem P5 and the product service J2EE platform P8 is reviewed and processed to obtain the document review results, including: reviewing whether the code value of the field mapped from the branch field to the field in the head office field is consistent with the data dictionary, and whether to perform escape for the branch.

[0063] In specific implementation, the branch P5 and P8 mapping rule document review may include:

[0064] (1) Whether the specific field mapping of the branch is accurate;

[0065] (2) Whether the field length is too long;

[0066] (3) Whether the amount unit is correct;

[0067] (4) Whether the required fields in P8 have values;

[0068] (5) Whether the attribute values ​​required by the return file correspond to those in the payment request file and are uploaded synchronously;

[0069] (6) When mapping branch fields to headline fields, the code value of the field must be consistent with the data dictionary. If it is inconsistent, the branch needs to be escaped (for example: license plate color code).

[0070] 2. Secondly, the review of branch migration data mapping rules is introduced.

[0071] In one embodiment, Figure 2 As shown, according to the pre-configured file, the branch migration data mapping rules are reviewed and processed to obtain the mapping review results, which may include step 201: the feature system arrears data. If the customer corresponding to the arrears data has terminated the contract, branch migration is not recommended, and it is recommended that the feature system handle it by itself.

[0072] In one embodiment, as Figure 2 shown, according to the pre-configured file, the audit process is performed on the mapping rules for branch migration data to obtain the mapping audit result, which may include step 202: If the branch requests deduplication of historical data, data will be migrated to the transaction key value table.

[0073] In one embodiment, as Figure 2 shown, according to the pre-configured file, the audit process is performed on the mapping rules for branch migration data to obtain the mapping audit result, which may include step 203: Audit the successfully deducted historical data of the feature system for customers to query after migration (in order to reduce the non-functional pressure on the system, branch migration is not recommended).

[0074] In one embodiment, the migrated business data includes historical data of contracts, blacklists, liquidations, overdue payment supplements, and terminated contracts.

[0075] Specifically, the audit of the mapping rules for branch migration data may include:

[0076] 1. The overdue data of the feature system; the feature system may refer to the branch ETC system with unique functions.

[0077] 2. If the branch requests deduplication of historical data, data will be migrated to the transaction key value table;

[0078] 3. The successfully deducted historical data of the feature system for customers to query after migration (in order to reduce the non-functional pressure on the system, branch migration is not recommended).

[0079] The batch deduction request file of the mapping interface from P5 to P8 is shown in Table 1 below.

[0080]

[0081] Table 1

[0082] The batch deduction response file of the mapping interface from P5 to P8 is shown in Table 2 below.

[0083]

[0084]

[0085] Table 2

[0086] The request message sent by the P5-batch general response file is shown in Table 3 below.

[0087]

[0088] Table 3

[0089] The response message sent by the P5-batch general response file is shown in Table 4 below.

[0090]

[0091] Table 4

[0092] In specific implementation, the ETC passing transaction key value table is as shown in Table 5 below. Note: The passing transaction key value table is used for deduplication verification of the deduction details. If the branch has a historical deduplication requirement for deductions and is worried that the highway bureau will resend the historical deduction data sent to the branch's special system before migration after migration, part of the historical data before the migration of the branch's special system can be migrated to this table, and it is required that the primary keys do not conflict.

[0093]

[0094] Table 5

[0095] In specific implementation, the ETC passing historical transaction table is as shown in Table 6 below. Note: Passing historical transaction table: If the branch migrates the historical overdue data of the special system, the overdue data needs to be converted according to the table structure and mapping relationship of this table. Only after the migration mapping is successful can the subsequent overdue data initiate supplementary deductions in the head office system.

[0096]

[0097]

[0098]

[0099] Table 6

[0100] In specific implementation, the migration rule of this Table 6 is the same as that of the deduction registration table, and the two tables have the same table structure. If migrating historical overdue payments, this table must be migrated.

[0101] Second, next, introduce the steps in the above test development stage, that is, the above step 102.

[0102] In specific implementation, during the test stage, prepare the pre-buried scripts for the branch's takeover. According to the business requirements of the branch, prepare the script data that should be pre-buried in the P8 clearing module for the branch's takeover, and conduct business continuity testing. The following provides a detailed introduction to this step 102.

[0103] In one embodiment, as Figure 3 shown, preparing the pre-buried scripts for the branch's takeover and conducting business continuity testing may include:

[0104] Step 301: The branch migrates all contract, clearing, and blacklist data to the contract library and clearing library according to the preset business rules;

[0105] Step 302: The branch obtains the real files of the most recent 5 days from production and uploads them to the head office to initiate batch verification;

[0106] Step 303: Check the details that fail the verification for each batch, the reasons for failure, and the number of detailed records, and feedback to the branch. Please ask the branch to confirm whether it meets the expectations. If so, ask the branch to make adjustments.

[0107] During specific implementation, during the migration process, it mainly includes business continuity testing to ensure business continuity. The steps of the continuity testing are as follows:

[0108] 1. According to the preset business rules, the branch migrates all contract, clearing, and blacklist data to the contract library and the clearing library.

[0109] 2. The branch obtains the real files of the most recent 5 days from production and submits them to the head office to initiate batch verification.

[0110] 3. Check the details that fail the verification for each batch, the reasons for failure, and the number of detailed records, and feedback to the branch. Please ask the branch to confirm whether it meets the expectations. If so, ask the branch to make adjustments.

[0111] Between the preparation of the pre-embedded script by the branch and the business continuity testing, it may also include: the steps of supporting the functional testing of the test environment, and if any issues inconsistent with the previous analysis are found, record and feedback them in a timely manner. If it is found that the P5 escape file of the branch is inaccurate, correct it in a timely manner. After that, it also includes the support for the migration test of the overdue payment data, mainly for the steps of the overdue payment of credit cards and non-credit cards migrated by the branch.

[0112] III. Next, introduce the steps of the trial operation stage of going live, that is, the above-mentioned Step 103.

[0113] During specific implementation, in the go-live stage, it is very important to verify whether the branch can switch to the new system and ensure that most of the batch deduction files sent by the highway bureau in production can pass the validity verification. Check the accuracy of the business parameters and scripts. Among them, the data migration during the upload process is an important part. The migrated data can include: the historical data of contracts, blacklists, clearing, overdue payment supplements, and terminated contracts are all migrated; it can include the migration of all data of debit cards and stored value cards. It is necessary to ensure the consistency of the clearing data migration. The steps for checking the accuracy of the business parameters and scripts are as follows:

[0114] 1. Check whether the clearing-related business parameters prepared by the public module are consistent with the final version of the business parameters provided by the branch.

[0115] 2. Check whether there are any omissions in the parameter scripts prepared by the clearing module itself and whether the field values are accurate.

[0116] 3. Prepare the go-live clearing check script and submit it to the code branch.

[0117] In addition, during the go-live production: 1. Whether the pre-embedded scripts of each branch are accurate, and the batch parameters of the newly migrated branches are closed; 2. If the branch is in arrears, it is necessary to check whether the total amount of arrears is consistent with the total amount reported by the business, and whether the SQL for screening data for supplementary deduction and forced deduction can query the migration data of the corresponding branch (if the branch has arrears but has not been migrated, it can be omitted); 3. If the total amount details of the branch arrears are consistent, modify the amount of the manual adjustment statement (prepared in advance before the version date), and transfer it from the branch's advance payment account to the branch's internal account (if the branch has arrears but has not been migrated, it can be omitted).

[0118] In addition, during the trial operation of the go-live, the main steps are as follows: 1. Stop the automatic task of uploading batch deduction files; 2. Open the relevant parameters of the branch start batch; 3. Check the details and reasons for the branch verification failure; 4. Feedback whether there are any objections to the details of the branch verification failure; 5. After the branch feedback is correct, open the task of uploading batch deduction files and initiate the deduction; 6. After the batch deduction is completed, check whether the accounting transaction is accurate; 7. Verify whether the deduction return file is successfully sent to the branch P5; 8. Wait for the branch technical colleagues to confirm whether the return file is successfully returned to the Highway Bureau. If it is correct, the process ends.

[0119] Fourthly, the above-mentioned step 104 will be introduced next.

[0120] According to the document review results, mapping review results, continuity testing and verification results, the branch settlement data starts to be migrated to the head office system. And check whether the accounting transaction is accurate and verify whether the deduction return file is successfully sent to the branch P5. If there is an imbalance in the accounts due to branch arrears, take remedies such as forced deduction, supplementary deduction and manual adjustment of accounts.

[0121] During the specific implementation, the steps in each migration stage can be as shown in Table 7 below.

[0122] Phase Analysis Design Development Testing Go Live Specific Steps Requirement Review Architecture Plan Review Branch Development Support Collaborative Testing Head Office Go Live Transaction Line Submission Soft Opening Support Interface Submission Data Item Submission Database Table Submission

[0123] Table 7

[0124] In addition, the settlement of the ETC system deducts the reserved account when the customer signs the contract. For the contracts signed for corporate accounts found in the analysis of the differences in the requirements of some branches for centralized collection, it is allowed to deduct from multiple accounts and in the corresponding rule order. Therefore, for this requirement, before the transformation, the head office system is transformed to add a multi-account settlement mode, allowing deductions from multiple accounts in the corresponding rule order, and making deductions in the order of the first deduction account and the reserve fund account.

[0125] The present invention mainly uses the technical solution for the data migration part of the settlement module during the process of the head office's centralized collection of branches in the CCB ETC system. Applying this solution, the branch settlement data can be migrated to the head office ETC system, realizing "version independence and service interaction" between the head office and branch systems. At the same time, it can meet the following requirements:

[0126] 1. Analyze the ETC business function differences between the head office and branches, and make improvements and centralizations to meet the specific requirements of branches.

[0127] 2. Ensure the consistency of the settlement data migrated to the head office system.

[0128] 3. During the trial operation after going live, ensure business continuity, verify whether the deduction feedback files are successfully sent to Branch P5, and confirm whether the feedback files are successfully returned to the Highway Bureau without affecting the business.

[0129] For the convenience of understanding, the method provided in the embodiments of the present invention will be introduced as a whole below.

[0130] I. During the migration process, the special requirements of branches for the system need to be considered. For the data migration involved, the migrated data includes contracts, blacklists, settlements, overdue payment supplements, and historical data of terminated contracts. Communicate with branches to understand whether the existing ETC system can meet the business requirements of branches. If it can, follow the subsequent standard process; if there are differences, it is necessary to clarify how branches handle them. The first step of the present invention is to connect with the requirements.

[0131] II. The migration process needs to include business continuity testing to ensure business continuity. The steps of the continuity testing are as follows:

[0132] 1. The branch migrates all contract data to the contract library and settlement library.

[0133] 2. The branch obtains the real files of the most recent 5 days from production and submits them to the head office to initiate batch verification.

[0134] 3. Check the details that fail the verification for each batch, the reasons for failure, and the number of detailed records, and feedback them to the branch for confirmation of whether they meet the expectations. If so, ask the branch to make adjustments.

[0135] III. It is very important to verify whether the vast majority of the batch deduction files sent by the Highway Bureau to production can pass the validity verification after the branch switches to the new system.

[0136] The steps for checking the accuracy of business parameters and scripts are as follows:

[0137] 1. Check whether the settlement-related business parameters prepared in the public module are consistent with the final version of the business parameters provided by the branch.

[0138] 2. Check whether there are any omissions in the parameter scripts prepared by the settlement module itself and whether the field values are accurate.

[0139] 3. Prepare the settlement check script for going live and submit it to the production branch.

[0140] IV. Start migrating the sub-branch clearing data to the head office system based on the continuity test and verification results. Check whether the accounting transaction records are accurate and verify whether the deduction feedback file has been successfully sent to Sub-branch P5. In case of unbalanced accounts due to sub-branch arrears, take remedies such as forced deduction, supplementary deduction, and manual adjustment of accounts.

[0141] The advantages of the data migration method applied to the ETC sub-branch upload provided by the embodiment of the present invention are as follows:

[0142] 1. The present invention is directed to the financial characteristic ETC system, and during the data migration process, the requirements of the connected sub-branches are ensured, and the requirements do not deviate due to migration.

[0143] 2. For the general transaction key value table and the deduction registration table of the ETC clearing statement, the detailed migration verification rules for different fields are divided. The unified standard verification for data migration of different sub-branches is realized. Ensure the data consistency of the clearing data migrated to the head office system.

[0144] 3. During the migration process, the trial operation during the online launch ensures business continuity.

[0145] An embodiment of the present invention also provides a data migration device applied to the ETC sub-branch upload, as described in the following embodiments. Since the principle of the device to solve the problem is similar to the data migration method applied to the ETC sub-branch upload, the implementation of the device can refer to the implementation of the data migration method applied to the ETC sub-branch upload, and the repeated parts will not be elaborated.

[0146] Figure 4 It is a schematic structural diagram of the data migration device applied to the ETC sub-branch upload in the embodiment of the present invention, as Figure 4 shown, the device includes:

[0147] The analysis phase review unit 01 is configured to review and process the mapping rule document between the sub-branch external connection subsystem P5 and the product service J2EE platform P8 according to the pre-configured file to obtain the document review result; review and process the sub-branch migration data mapping rule according to the pre-configured file to obtain the mapping review result;

[0148] The test phase unit 02 is configured to prepare the sub-branch upload pre-buried script and conduct a business continuity test to obtain the business continuity test result;

[0149] The online phase verification unit 03 is configured to verify the accuracy of the service parameters and scripts to obtain the verification result;

[0150] The data migration unit 04 is configured to start migrating the ETC sub-branch clearing data to the head office system according to the document review result, the mapping review result, the business continuity test result, and the verification result.

[0151] In one embodiment, the audit unit in the analysis phase is specifically used to: audit whether the specific field mapping of the branch is accurate, whether the field length is too long, and whether the amount unit is correct.

[0152] In one embodiment, the analysis phase audit unit is specifically used to audit whether the mandatory fields required by P8 have values.

[0153] In one embodiment, the review unit in the analysis phase is specifically used to review whether the attribute values ​​required by the return file correspond to those in the payment request file and are uploaded synchronously.

[0154] In one embodiment, the audit unit in the analysis phase is specifically used to: verify that the code value of the branch field is consistent with the data dictionary when it is mapped to the head office field. If it is inconsistent, the branch needs to be escaped.

[0155] In one embodiment, the analysis phase audit unit is specifically used for: feature system arrears data. If the customer corresponding to the arrears data has terminated the contract, branch migration is not recommended and the feature system is recommended to handle it by itself.

[0156] In one embodiment, the analysis phase audit unit is specifically used to: if the branch requires deduplication of historical data, migrate the data to the running key value table.

[0157] In one embodiment, the review unit in the analysis phase is specifically used to review the historical successful deduction data of the characteristic system for post-migration customer query.

[0158] In one embodiment, the testing phase unit is specifically used for:

[0159] According to the preset business rules, the branch will migrate all contract, clearing and blacklist data to the contract library and clearing library;

[0160] The branch obtains the authentic documents of the last five days from production and sends them to the head office to initiate batch verification;

[0161] Check the details of each batch that failed the verification, the reasons for failure and the number of details, and feedback to the branch. Ask the branch to confirm whether it meets expectations. If so, ask the branch to make adjustments.

[0162] The embodiment of the present invention also provides a computer device, such as Figure 5 As shown, it includes a memory 402, a processor 404 and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements any of the above-mentioned data migration methods collected by the application at the ETC branch.

[0163] Specifically, the computer device may be a computer terminal, a server or a similar computing device.

[0164] An embodiment of the present invention also provides a computer-readable storage medium storing a computer program for executing the data migration method for the ETC branch's upload and receipt application described above.

[0165] Specifically, a computer-readable storage medium includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer-readable storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible by a computing device. As defined herein, a computer-readable storage medium does not include transitory computer-readable media, such as modulated data signals and carrier waves.

[0166] In an embodiment of the present invention, compared with the prior art, for the data migration solution applied to the ETC branch's upload and receipt, by: according to a pre-configured file, auditing the mapping rule document between the branch external connection subsystem P5 and the product service J2EE platform P8 to obtain a document audit result; according to the pre-configured file, auditing the branch migration data mapping rule to obtain a mapping audit result; preparing the branch upload pre-buried script and conducting a business continuity test to obtain a business continuity test result; checking the accuracy of business parameters and scripts to obtain a check result; and starting to migrate the ETC branch settlement data to the head office system according to the document audit result, mapping audit result, business continuity test result, and check result, ensuring business continuity and data consistency during the data migration process when the ETC branch uploads data.

[0167] Those skilled in the art should understand that the embodiments of the present invention can be provided as a method, system, or computer program product. Therefore, the present invention can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0168] The present invention is described with reference to the flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present invention. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and combinations of flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to the processors of general-purpose computers, special-purpose computers, embedded processors, or other programmable data processing devices to produce a machine, such that the instructions executed by the processors of the computer or other programmable data processing devices produce means for implementing the functions specified in the flow Figure 1 one or more flows and / or blocks Figure 1 or means for implementing the functions specified in one or more blocks.

[0169] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory produce a manufactured article including instruction means that implement the functions specified in the flow Figure 1 one or more flows and / or blocks Figure 1 or means for implementing the functions specified in one or more blocks.

[0170] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in the flow Figure 1 one or more flows and / or blocks Figure 1 or means for implementing the functions specified in one or more blocks.

[0171] The specific embodiments described above further elaborate on the objectives, technical solutions, and beneficial effects of the present invention. It should be understood that the above are only specific embodiments of the present invention and are not used to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the protection scope of the present invention.

Claims

1. A data migration method applied to the ETC branch collection, characterized in that, include: According to the pre-configured file, the mapping rule document of the branch external liaison subsystem P5 and the product service J2EE platform P8 is reviewed and processed to obtain the document review result; According to the pre-configured file, the branch migration data mapping rules are reviewed and processed to obtain the mapping review results; Prepare the branch's embedded scripts for business continuity testing and obtain the business continuity test results; Check the accuracy of business parameters and scripts and obtain the verification results; Based on the document review results, mapping review results, business continuity test results and verification results, the ETC branch clearing data was migrated to the head office system.

2. The data migration method applied to the ETC branch collection according to claim 1, characterized in that, According to the pre-configured file, the mapping rule document between the branch external liaison subsystem P5 and the product service J2EE platform P8 is reviewed and processed to obtain the document review results, including: whether the branch's specific field mapping is accurate, whether the field length is too long, and whether the amount unit is correct.

3. The data migration method applied to the ETC branch collection according to claim 1, characterized in that, According to the pre-configuration file, the mapping rule document of the branch external liaison subsystem P5 and the product service J2EE platform P8 is reviewed and processed to obtain the document review results, including: whether the required fields required by P8 have values.

4. The data migration method applied to the ETC branch collection according to claim 1, characterized in that, According to the pre-configured file, the mapping rule document between the branch external liaison subsystem P5 and the product service J2EE platform P8 is reviewed and processed to obtain the document review results, including: whether the attribute values ​​required by the review return file correspond to those in the payment request file and are uploaded synchronously.

5. The data migration method applied to the ETC branch collection according to claim 1, characterized in that, According to the pre-configuration file, the mapping rule document between the branch external liaison subsystem P5 and the product service J2EE platform P8 is reviewed and processed to obtain the document review results, including: reviewing whether the code value of the field mapped from the branch field to the field in the head office field is consistent with the data dictionary, and whether to perform escape for the branch.

6. The data migration method applied to the ETC branch collection according to claim 1, characterized in that, According to the pre-configured file, the branch migration data mapping rules are reviewed and processed to obtain the mapping review results, including: for the overdue payment data of the special system, if the customer corresponding to the overdue payment data has terminated the contract, branch migration is not recommended, and the special system is recommended to handle it by itself.

7. The data migration method applied to the ETC branch collection according to claim 1, characterized in that, According to the pre-configured file, the branch migration data mapping rules are reviewed and processed to obtain the mapping review results, including: if the branch requires deduplication of historical data, the data will be migrated to the running key value table.

8. The data migration method applied to the ETC branch collection according to claim 1, characterized in that, According to the pre-configured file, the branch migration data mapping rules are reviewed and processed to obtain the mapping review results, including: reviewing the historical deduction success data of the feature system for customer query after migration.

9. The data migration method applied to the ETC branch collection according to claim 1, characterized in that, The migrated business data includes historical data on contracts, blacklists, liquidations, overdue payments, and terminated contracts.

10. The data migration method applied to the ETC branch collection according to claim 1, characterized in that, Prepare the branch's embedded scripts for business continuity testing and obtain the business continuity test results, including: According to the preset business rules, the branch will migrate all contract, clearing and blacklist data to the contract library and clearing library; The branch obtains the real documents of the last N days from production and sends them to the head office to initiate batch verification; N is a positive integer greater than or equal to 1; Check the details of each batch that failed the verification, the reasons for failure and the number of details, and feedback to the branch. Ask the branch to confirm whether it meets expectations. If so, ask the branch to make adjustments.

11. A data migration device applied to the ETC branch collection, characterized in that, include: The review unit in the analysis phase is used to review the mapping rule document between the branch external liaison subsystem P5 and the product service J2EE platform P8 according to the pre-configuration file to obtain the document review result; and to review the branch migration data mapping rule according to the pre-configuration file to obtain the mapping review result; The test phase unit is used to prepare the branch's embedded scripts, conduct business continuity testing, and obtain business continuity testing results; The verification unit in the online stage is used to verify the accuracy of business parameters and scripts and obtain verification results; The data migration unit is used to migrate the ETC branch clearing data to the head office system based on the document review results, mapping review results, business continuity test results and verification results.

12. The data migration device applied to the ETC branch collection according to claim 11, characterized in that, The audit unit in the analysis phase is specifically used to: review whether the specific field mapping of the branch is accurate, whether the field length is too long, and whether the amount unit is correct.

13. The data migration device applied to the ETC branch collection as claimed in claim 11, wherein, The audit unit in the analysis phase is specifically used to: audit whether the mandatory fields required by P8 have values.

14. The data migration device applied to the ETC branch collection as claimed in claim 11, wherein, The review unit in the analysis phase is specifically used to review whether the attribute values ​​required by the return file are synchronously uploaded in the payment request file.

15. The data migration device applied to the ETC branch collection as claimed in claim 11, wherein, The audit unit in the analysis phase is specifically used to: review whether the code value of the field in the branch field mapped to the field in the head office is consistent with the data dictionary, and whether to perform escape for the branch.

16. The data migration device applied to the ETC branch collection as claimed in claim 11, wherein, The audit unit in the analysis phase is specifically used for: For the overdue payment data of the special system, if the customer corresponding to the overdue payment data has terminated the contract, it is not recommended for branch migration, and it is recommended that the special system handle it by itself.

17. The data migration device applied to the ETC branch collection as claimed in claim 11, wherein, The audit unit in the analysis phase is specifically used for: If the branch requires deduplication of historical data, the data will be migrated to the running key value table.

18. The data migration device applied to the ETC branch collection as claimed in claim 11, wherein, The audit unit in the analysis phase is specifically used to: audit the historical successful deduction data of the feature system for customer inquiries after migration.

19. The data migration device applied to the ETC branch collection as claimed in claim 11, wherein, The testing phase unit is specifically used for: According to the preset business rules, the branch will migrate all contract, clearing and blacklist data to the contract library and clearing library; The branch obtains the real documents of the last N days from production and sends them to the head office to initiate batch verification; N is a positive integer greater than or equal to 1; Check the details of each batch that failed the verification, the reasons for failure and the number of details, and feedback to the branch. Ask the branch to confirm whether it meets expectations. If so, ask the branch to make adjustments.

20. A computer device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein, When the processor executes the computer program, the method according to any one of claims 1 to 10 is implemented.

21. A computer-readable storage medium, wherein, The computer-readable storage medium stores a computer program for executing the method according to any one of claims 1 to 10.

Images