Data verification method and device, electronic equipment, medium and program product

Abstract

The embodiment of the invention discloses a data verification method and device, electronic equipment, a medium and a program product. The method comprises the following steps: determining a starting date and an ending date of a corresponding target event in a current production environment according to preset event type information, and obtaining target request data corresponding to the event type information contained from the starting date to the ending date; acquiring a corresponding actual result of the target event in the production environment, and acquiring first field information corresponding to the starting date; comparing the latest date with the starting date to determine initial state data corresponding to the starting date; returning the initial state data and the target request data to a preset simulation environment to generate a simulation result; and generating a verification result of the to-be-verified data according to the first environment parameter of the production environment, the second environment parameter of the simulation environment, the actual result and the simulation result.

Description

Technical Field

[0001] This specification relates to the field of computer technology, and particularly to a data verification method, apparatus, electronic device, medium, and program product. Background Art

[0002] As the final link in the production chain, the downstream data processing system is mainly responsible for ensuring the accuracy of data operations, and its capabilities are reflected in supporting data changes caused by various scenarios (such as data entry, update, and settlement). However, since this system involves multiple related parties, each adjustment of the relevant code may affect the stability of the processing logic. Therefore, extensive regression verification is required to ensure system reliability.

[0003] Traditional regression verification techniques highly rely on the test platforms and tools provided by the quality team, but there are significant pain points in actual applications. Therefore, there is an urgent need to design a more flexible and accurate traffic replay and verification solution to reduce the difficulty of test data construction, improve data consistency, reduce the time cost of regression testing, thereby improving verification efficiency, as well as the accuracy and reliability of data verification. Summary of the Invention

[0004] Embodiments of this specification provide a data verification method, apparatus, electronic device, medium, and program product, which can reduce the time cost of regression testing, thereby improving verification efficiency. The above technical solutions are as follows: In a first aspect, embodiments of this specification provide a data verification method, including: Determine the start date and end date of a corresponding target event in the current production environment according to preset event type information, and obtain target request data corresponding to the event type information included from the start date to the end date; Obtain the actual result corresponding to the target event in the production environment, and obtain first field information corresponding to the start date. The first field information includes the latest date when the data recorded on the start date changes, the target object status data corresponding to the date before the latest date, and the target object status data corresponding to the start date; Compare the latest date with the start date to determine the initial state data corresponding to the start date; Backflow the initial state data and the target request data to a preset simulation environment to generate a simulation result, where the simulation environment is a simulation environment constructed based on the data to be verified; Generate a verification result of the data to be verified according to the first environment parameter of the production environment, the second environment parameter of the simulation environment, the actual result, and the simulation result.

[0005] In a possible implementation, the above-mentioned target request data includes transaction request information corresponding to the above-mentioned event type information within the above-mentioned start date to the above-mentioned end date, and the target object status data corresponding to the above-mentioned start date includes first asset data corresponding to the above-mentioned start date.

[0006] In a possible implementation, the above-mentioned start date is the first accounting date, and the above-mentioned end date is the second accounting date; the latest date when the data recorded at the above-mentioned start date is changed is the latest accounting date when the data recorded at the above-mentioned first accounting date is changed, and the target object status data corresponding to the date before the above-mentioned latest date is the asset balance data corresponding to the accounting date before the above-mentioned latest accounting date; The above-mentioned comparing the above-mentioned latest date and the above-mentioned start date to determine the initial state data corresponding to the above-mentioned start date includes: Judging whether the above-mentioned latest accounting date is later than the above-mentioned first accounting date; In the case where the above-mentioned latest accounting date is later than the above-mentioned first accounting date, determining the asset balance data corresponding to the accounting date before the above-mentioned first accounting date as the first asset data corresponding to the above-mentioned start date; In the case where the above-mentioned latest accounting date is not later than the above-mentioned first accounting date, determining the asset balance data corresponding to the above-mentioned first accounting date as the first asset data corresponding to the above-mentioned start date.

[0007] In a possible implementation, the above-mentioned obtaining the actual result corresponding to the above-mentioned target event in the above-mentioned production environment includes: In the above-mentioned production environment, obtaining second asset data corresponding to the above-mentioned end date; Determining the above-mentioned second asset data as the actual result corresponding to the above-mentioned target event in the above-mentioned production environment.

[0008] In a possible implementation, before obtaining the above-mentioned target request data corresponding to the above-mentioned event type information included within the above-mentioned start date to the above-mentioned end date, the above method further includes: For the current accounting date in the above-mentioned production environment, when it is detected that the first asset change occurs within the above-mentioned current accounting date, updating the latest accounting date in the current field information corresponding to the above-mentioned current accounting date to the above-mentioned current accounting date, and updating the asset balance data corresponding to the accounting date before the above-mentioned latest accounting date; When the above-mentioned current accounting date ends, updating the asset balance data corresponding to the above-mentioned current accounting date.

[0009] In a possible implementation, the above-mentioned flowing back the above-mentioned initial state data and the above-mentioned target request data to a preset simulation environment to generate a simulation result includes: Import the above initial state data into the database of a preset simulation environment; Resend the above target request data to the above simulation environment, and trigger the above simulation environment to execute the transaction logic corresponding to the above target request data based on the above database; When it is detected that the execution of the above transaction logic is completed, obtain the simulation result generated in the above simulation environment.

[0010] In a possible implementation manner, the above generating the verification result of the data to be verified according to the first environmental parameter of the above production environment, the second environmental parameter of the above simulation environment, the above actual result, and the above simulation result includes: Compare the above simulation result and the above actual result one by one based on a preset comparison field to generate a comparison result, where the above preset comparison field includes an asset balance field and a user identification field; Determine the environmental difference information between the above production environment and the above simulation environment based on the first environmental parameter of the above production environment and the second environmental parameter of the above simulation environment; Generate the verification result of the data to be verified based on the above environmental difference information and the above comparison result.

[0011] In a possible implementation manner, the above generating the verification result of the data to be verified based on the above environmental difference information and the above comparison result includes: When the above comparison result indicates that the above simulation result is inconsistent with the above actual result, determine the inconsistent target field information included in the above comparison result; Analyze and process the above target field information based on the above environmental difference information to determine the corresponding marker information of the above target field information, where the above marker information is used to indicate whether the corresponding field difference information of the above target field information is related to the above environmental difference information; Generate the verification result of the data to be verified according to the marker information corresponding to the above target field information.

[0012] In a second aspect, an embodiment of this specification provides a data verification device, including: A determination module, configured to determine the start date and end date of a corresponding target event in the current production environment according to preset event type information, and obtain the target request data corresponding to the above event type information included within the above start date and the above end date; An acquisition module, configured to acquire the actual result corresponding to the above-mentioned target event in the above-mentioned production environment, and acquire the first field information corresponding to the above-mentioned start date, where the first field information includes the latest date when the data recorded on the above-mentioned start date changes, the target object status data corresponding to the date before the above-mentioned latest date, and the target object status data corresponding to the above-mentioned start date; A comparison module, configured to compare the above-mentioned latest date and the above-mentioned start date to determine the initial state data corresponding to the above-mentioned start date; A return module, configured to return the above-mentioned initial state data and the above-mentioned target request data to a preset simulation environment to generate a simulation result, where the above-mentioned simulation environment is a simulation environment constructed based on the data to be verified; A generation module, configured to generate a verification result of the above-mentioned data to be verified according to the first environment parameter of the above-mentioned production environment, the second environment parameter of the above-mentioned simulation environment, the above-mentioned actual result, and the above-mentioned simulation result.

[0013] In a possible implementation manner, the above-mentioned target request data includes transaction request information corresponding to the above-mentioned event type information within the period from the above-mentioned start date to the above-mentioned end date, and the target object status data corresponding to the above-mentioned start date includes the first asset data corresponding to the above-mentioned start date.

[0014] In a possible implementation manner, the above-mentioned start date is the first accounting date, and the above-mentioned end date is the second accounting date; the latest date when the data recorded on the above-mentioned start date changes is the latest accounting date when the data recorded on the above-mentioned first accounting date changes, and the target object status data corresponding to the date before the above-mentioned latest date is the asset balance data corresponding to the accounting date before the above-mentioned latest accounting date; The above-mentioned comparison module includes: A judgment unit, configured to judge whether the above-mentioned latest accounting date included in the above-mentioned first field information is later than the above-mentioned first accounting date; A first determination unit, configured to, when the above-mentioned latest accounting date is later than the above-mentioned first accounting date, determine the asset balance data corresponding to the accounting date before the above-mentioned first accounting date as the first asset data corresponding to the above-mentioned start date; A second determination unit, configured to, when the above-mentioned latest accounting date is not later than the above-mentioned first accounting date, determine the asset balance data corresponding to the above-mentioned first accounting date as the first asset data corresponding to the above-mentioned start date.

[0015] In a possible implementation manner, the above-mentioned acquisition module includes: A first acquisition unit, configured to acquire the second asset data corresponding to the above-mentioned end date in the above-mentioned production environment; A third determination unit, configured to determine the second asset data as the actual result corresponding to the target event in the production environment.

[0016] In a possible implementation manner, the above device further includes: A first update module, configured to, for the current accounting date in the production environment, when it is detected that a first asset change occurs within the current accounting date, update the latest accounting date in the current field information corresponding to the current accounting date to the current accounting date, and update the asset balance data corresponding to the previous accounting date of the latest accounting date; A second update module, configured to update the asset balance data corresponding to the current accounting date when the current accounting date ends.

[0017] In a possible implementation manner, the reflux module includes: An import unit, configured to import the initial state data into the database of a preset simulation environment; An execution unit, configured to re-inject the target request data into the simulation environment, and trigger the simulation environment to execute the transaction logic corresponding to the target request data based on the database; A fourth determination unit, configured to obtain the simulation result generated in the simulation environment when it is detected that the execution of the transaction logic is completed.

[0018] In a possible implementation manner, the above generation module includes: A comparison unit, configured to perform one-by-one comparison on the simulation result and the actual result based on preset comparison fields to generate a comparison result; wherein, the preset comparison fields include an asset balance field and a user identification field; A fifth determination unit, configured to determine the environment difference information between the production environment and the simulation environment based on the first environment parameter of the production environment and the second environment parameter of the simulation environment; A generation unit, configured to generate a verification result of the to-be-verified data based on the environment difference information and the comparison result.

[0019] In a possible implementation manner, the generation unit includes: A determination subunit, configured to determine the inconsistent target field information included in the comparison result when the comparison result indicates that the simulation result is inconsistent with the actual result; A processing subunit, configured to analyze and process the target field information based on the environment difference information to determine the marking information corresponding to the target field information, where the marking information is used to indicate whether the corresponding field difference information of the target field information is related to the environment difference information; A generating subunit, configured to generate a verification result of the to-be-verified data according to the marking information corresponding to the above-mentioned target field information.

[0020] In a third aspect, an embodiment of this specification provides an electronic device, including: a processor and a memory; wherein, the above-mentioned memory stores a computer program, and when the processor executes the computer program, the method steps provided in the first aspect of the embodiment of this specification are implemented.

[0021] In a fourth aspect, an embodiment of this specification provides a computer storage medium, where the above-mentioned computer storage medium stores multiple instructions, and the above-mentioned instructions are adapted to be loaded and executed by a processor to execute the method steps provided in the first aspect of the embodiment of this specification.

[0022] In a fifth aspect, an embodiment of this specification provides a computer program product including instructions, when the above-mentioned computer program product runs on a computer or a processor, the above-mentioned computer or the above-mentioned processor is enabled to execute the data verification method provided in the first aspect of the embodiment of this specification.

[0023] In the embodiment of this specification, first, the start date and end date of a corresponding target event in the current production environment are determined according to preset event type information, and the target request data corresponding to the event type information included from the start date to the end date is obtained; and, the actual result corresponding to the target event in the production environment and the first field information corresponding to the start date are obtained, where the first field information includes the latest date when the data recorded by the start date changes, the target object status data corresponding to the date before the latest date, and the target object status data corresponding to the start date; then, the latest date and the start date are compared to determine the initial state data corresponding to the start date, realizing an accurate restoration of the initial state data and improving the authenticity and pertinence of the simulation environment construction. Further, the initial state data and the target request data are fed back to a preset simulation environment to generate a simulation result, where the simulation environment is a simulation environment constructed based on the to-be-verified data; then, a verification result of the to-be-verified data is generated according to the first environment parameter of the production environment, the second environment parameter of the simulation environment, the actual result, and the simulation result. Thus, the verification process is not only limited to result judgment, but also can comprehensively perform reasonable tolerance and deviation explanation according to environmental differences, thereby effectively improving the efficiency, accuracy, and reliability of data verification, reducing the manual intervention cost, and enhancing the verification reliability after system upgrade. Description of the Drawings

[0024] To more clearly illustrate the technical solutions in the embodiments of this specification, the following will briefly introduce the accompanying drawings required for the embodiments. Obviously, the accompanying drawings in the following description are only some embodiments of the embodiments of this specification. For those of ordinary skill in the art, without creative efforts, other accompanying drawings can be obtained based on these drawings.

[0025] Figure 1 Schematic diagram of the architecture of a data verification system provided for an exemplary embodiment of Embodiment 1 of this specification; Figure 2 Schematic flow chart of a data verification method provided for an exemplary embodiment of Embodiment 1 of this specification; Figure 3 Schematic flow chart of a method for determining initial state data provided for an exemplary embodiment of Embodiment 1 of this specification; Figure 4 Schematic flow chart of a method for generating simulation results provided for an exemplary embodiment of Embodiment 1 of this specification; Figure 5 Schematic flow chart of a method for generating verification results provided for an exemplary embodiment of Embodiment 1 of this specification; Figure 6 Schematic diagram of the detailed architecture of a data verification system provided for an exemplary embodiment of Embodiment 1 of this specification; Figure 7 Schematic diagram of the structure of a data verification device provided for an exemplary embodiment of Embodiment 1 of this specification; Figure 8 Schematic diagram of the structure of an electronic device provided for an exemplary embodiment of Embodiment 1 of this specification. Detailed implementation manners

[0026] In order to make the objectives, technical solutions and advantages of the embodiments of this specification clearer, the following further elaborates on the embodiments of this specification in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the embodiments of this specification and are not used to limit the embodiments of this specification.

[0027] In the description of the embodiments of this specification, it should be understood that the terms "first", "second", etc. are only used for descriptive purposes and cannot be construed as indicating or implying relative importance. For those of ordinary skill in the art, the specific meanings of the above terms in the embodiments of this specification can be understood according to specific circumstances. In addition, in the description of the embodiments of this specification, unless otherwise specified, "a plurality" means two or more. " / ", describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after.

[0028] Please refer to Figure 1 , Figure 1 which is a schematic diagram of the architecture of a data verification system provided by the embodiments of this specification. As Figure 1 shown, the data verification system architecture may include a production system 101, a simulation system 102, and a verification system 103. Among them, the production system 101, the simulation system 102, and the verification system 103 communicate with each other through a wired communication network or a wireless communication network.

[0029] Optionally, the current production environment is configured in the production system 101, the preset simulation environment is configured in the simulation system 102, and the offline data verification platform may be configured in the verification system 103.

[0030] In one embodiment, each of the production system 101, the simulation system 102, and the verification system 103 may be hardware or software. When the system is hardware, it may be various electronic devices, including but not limited to smartphones, tablets, laptop portable computers, and desktop computers. When the system is software, it may be installed in the above-listed electronic devices, which may be implemented as multiple software or software modules (for example: used to provide distributed services), or may be implemented as a single software or software module, and no specific limitation is made here.

[0031] In the embodiments of this specification, first, the verification system 103 determines the start date and end date of the corresponding target event in the current production system 101 according to the preset event type information, and obtains the target request data corresponding to the event type information included from the start date to the end date; moreover, the verification system 103 obtains the actual result corresponding to the target event in the production system 101, and obtains the first field information corresponding to the start date, where the first field information includes the latest date when the data recorded on the start date changes, the target object status data corresponding to the date before the latest date, and the target object status data corresponding to the start date; furthermore, the verification system 103 compares the latest date with the start date to determine the initial state data corresponding to the start date. Further, the simulation system 102 obtains the initial state data and the target request data corresponding to the target event in the current production environment from the production system 101, and returns the initial state data and the target request data to the preset simulation environment to generate a simulation result, and then the verification system 103 generates the verification result of the data to be verified according to the first environment parameter of the production system 101, the second environment parameter of the simulation system 102, the actual result, and the simulation result.

[0032] It should be noted that the production system 101, the simulation system 102, and the verification system 103 may be configured in the same electronic device, or may be configured in different electronic devices. The embodiments of this specification do not make specific limitations on this.

[0033] It should be understood that Figure 1 the numbers of the production system, the simulation system, and the verification system in

[0034] In one embodiment, as Figure 2 shown, a data verification method is provided, which can be applied to the above data verification system, and includes the following steps: S202: Determine the start date and end date of the corresponding target event in the current production environment according to the preset event type information, and obtain the target request data corresponding to the event type information included from the start date to the end date.

[0035] Among them, the current production environment may be an actually operating system environment, that is, a system actually used. For example, the current production environment may include, but is not limited to: institutional asset systems, e-commerce inventory management systems, logistics distribution systems, etc.

[0036] In one embodiment, the above event type information may be identification information (such as an event code), which is used to describe the category or attribute of a specific transaction scenario or operation included in the target event to be determined, such as transaction scenarios like loan disbursement, repayment, carry - forward, etc.

[0037] Optionally, the event type information may be pre - determined by relevant testers before determining the target event, or may be automatically generated by the test system.

[0038] Optionally, the target event may be an operation or behavior that occurs within a specific time period.

[0039] Optionally, in the institutional asset system, the target event may refer to transaction scenarios or operations that occur to institutional users within a specific time period, specifically including loan disbursement, repayment, carry - forward, etc. For example, the target event can be specified as all transaction scenarios or operations of institutional users within the period from April 7, 2025. Additionally, in the e - commerce inventory management system, the target event may be all management operations of e - commerce users for relevant goods within a specific time period, such as goods selling operations, goods warehousing operations, etc. In the logistics distribution system, the target event may be all logistics management operations of logistics enterprise users within a specific time period, such as logistics package outbound operations, logistics package inbound operations, etc.

[0040] In one embodiment, the start date may be the first accounting date, and the end date may be the second accounting date, where the first accounting date is not later than the second accounting date. The accounting date may be a time unit divided by day, or may also be a time unit divided by month, quarter, year, etc.

[0041] Furthermore, the above target request data includes transaction request information corresponding to the above event type information from the above start date to the above end date, and the target object status data corresponding to the above start date includes first asset data corresponding to the above start date. The first asset data may be the accounting status or asset data recorded in the system at the start date, such as account balance, loan balance, etc.

[0042] In one embodiment, determining the start date and end date of the corresponding target event in the current production environment according to the preset event type information, and obtaining the target request data corresponding to the above event type information included from the above start date to the above end date includes: determining the transaction request information corresponding to the above event type information; determining the start date and end date according to the above transaction request information, and the transaction request information corresponding to the above event type information is included from the above start date to the above end date.

[0043] Optionally, the transaction request information corresponding to the event type information can be queried in the production environment log or the relevant database, and then the start date and the end date can be determined according to the request time of the transaction request information, and the transaction request information corresponding to the above event type information is included within this time range.

[0044] In one embodiment, the transaction request information refers to specific requests within the time period from the start date to the end date. For example, information such as loan disbursement requests, repayment requests, etc. The transaction request information can include the details of the transaction, such as the amount, the borrower's account number, the loan interest rate, etc. The transaction request data can be one or more.

[0045] That is to say, according to the event type information (such as "repayment"), find the corresponding time period (start date to end date) in the production environment, ensure that this time period includes the transaction request information corresponding to the event type information, and then take all the operations or behaviors that occur within this time period as the target event.

[0046] S204: Obtain the actual result corresponding to the above target event in the above production environment, and obtain the first field information corresponding to the above start date. The above first field information includes the latest date when the data recorded on the above start date changes, the target object status data corresponding to the date before the above latest date, and the target object status data corresponding to the above start date.

[0047] Among them, the actual result can be the true result or status change recorded by the system after the target event is executed in the production environment.

[0048] Optionally, the first field information can be pre-set data fields used to represent the end-of-day cross-sectional data corresponding to the first accounting date. The field information corresponding to each accounting date can be stored in a relevant configuration file or database. The latest date when the data recorded on the above start date changes is the latest accounting date when the data recorded on the above first accounting date changes. The target object status data corresponding to the date before the above latest date is the asset balance data corresponding to the accounting date before the above latest accounting date.

[0049] Specifically, the first field information can include the last_selt_dt field, the last_bal field, and the bal field. Among them, the last_selt_dt field represents the latest accounting date when the data recorded within the first accounting date changes. The last_bal field represents the asset balance data corresponding to the accounting date before the latest accounting date. Bal represents the asset balance data corresponding to the first accounting date.

[0050] S206: Compare the above latest date with the above start date to determine the initial state data corresponding to the above start date.

[0051] Among them, the initial state data can be the basic data before the target event occurs. The target request data can be various specific requests used to trigger the system to execute operations. The initial state data will be used as a comparison basis in subsequent regression verification to determine whether the system state data after the event execution meets the expectations.

[0052] For example, in the institutional asset system, the initial state data can be the institutional account status data, which can specifically include data such as the account balance, loan balance, and amount to be repaid of institutional users. The target request data can be specific requests used to trigger transactions, such as loan disbursement requests, repayment requests, or carry-over instructions, etc. The actual result can be the real change result of the institutional accounts after the target event is processed in the production environment. For example, the actual result can include, but is not limited to, the reduction in the account balance after the target event occurs, the remaining account balance after the target event occurs, etc.

[0053] Taking the above e-commerce inventory management system as an example, the initial state data can be the inventory data of the goods related to e-commerce users, and the target request data can include specific order requests used to trigger operations such as selling and warehousing. The actual result can be the real state data of the goods inventory after the target event is completed.

[0054] Taking the above logistics distribution system as an example, the initial state data can be the inventory data of the logistics parcels related to logistics enterprise users, and the target request data can be specific logistics management operation requests used to trigger operations such as warehousing and outbound. The actual result can be the real state data of the logistics parcel inventory after the target event is completed.

[0055] S208: Return the above initial state data and the above target request data to a preset simulation environment to generate a simulation result, where the above simulation environment is a simulated environment constructed based on the data to be verified.

[0056] In one embodiment, the above data to be verified refers to the relevant code changes that need to be verified.

[0057] Optionally, returning the above initial state data and the above target request data to a preset simulation environment means transferring the real data (initial state data and target request data) in the production environment to the simulation environment for re-running. Among them, the simulation environment can be a simulated production system. For example, it is a simulated institutional asset system and can be used to test the behavior of the system after relevant code changes.

[0058] Optionally, the simulation result may be the result of the change in the data state generated after running the changed code with the input data of the production environment in the simulation environment, such as the change result of the asset balance of the institutional user.

[0059] It can be understood that before the above-mentioned relevant code changes are deployed to the production environment, it is necessary to verify their correctness and stability. The simulation environment is a simulated environment built based on the data to be verified, and the target request data can be re-executed based on the initial state data to reproduce the real production scenario, facilitating the verification of the correctness and stability of the data to be verified.

[0060] S210: Generate the verification result of the data to be verified according to the first environmental parameter of the above-mentioned production environment, the second environmental parameter of the above-mentioned simulation environment, the above-mentioned actual result, and the above-mentioned simulation result.

[0061] Among them, the first environmental parameter of the production environment may be the context configuration information of the production environment, which may include but is not limited to database version, dependent service version, running configuration, scheduling time point, cache policy, etc. The first environmental parameter characterizes the real conditions during actual operation. The second environmental parameter of the simulation environment may be the context conditions used to run code verification in the simulation environment. Ideally, it may be consistent with the first environmental parameter, but in actual applications, there may be deviations due to data latency between the test library and the production library, parameter setting differences, etc.

[0062] Generating the verification result of the data to be verified according to the first environmental parameter of the above-mentioned production environment, the second environmental parameter of the above-mentioned simulation environment, the above-mentioned actual result, and the above-mentioned simulation result can be used to comprehensively determine whether the code or data changes to be verified are correctly reproduced in the simulation environment and exclude non-essential errors caused by environmental differences.

[0063] In the embodiments of this specification, first, the start date and end date of a corresponding target event in the current production environment are determined according to preset event type information, and the target request data corresponding to the event type information included from the start date to the end date is obtained; moreover, the actual result corresponding to the target event in the production environment and the first field information corresponding to the start date are obtained, where the first field information includes the latest date when the data recorded on the start date changes, the target object status data corresponding to the date before the latest date, and the target object status data corresponding to the start date; furthermore, the latest date and the start date are compared to determine the initial state data corresponding to the start date, realizing the accurate restoration of the initial state data and improving the authenticity and pertinence of the simulation environment construction. Further, the initial state data and the target request data are fed back to a preset simulation environment to generate a simulation result, where the simulation environment is a simulation environment constructed based on the data to be verified; furthermore, a verification result of the data to be verified is generated according to the first environment parameters of the production environment, the second environment parameters of the simulation environment, the actual result, and the simulation result. Thus, the verification process is not only limited to result judgment but can also comprehensively consider environmental differences for reasonable tolerance and deviation explanation, effectively improving the accuracy and reliability of data verification, reducing the manual intervention cost, and enhancing the verification reliability after system upgrade.

[0064] In one embodiment, the above start date is the first accounting date, and the above end date is the second accounting date; the latest date when the data recorded on the above start date changes is the latest accounting date when the data recorded on the above first accounting date changes, and the target object status data corresponding to the date before the above latest date is the asset balance data corresponding to the accounting date before the above latest accounting date. Furthermore, in the above step S206, the specific process of determining the initial state data is specifically referred to Figure 3 , which is a schematic flowchart of a method for determining initial state data provided by the embodiments of this specification. As Figure 3 shown, the method for determining the initial state data includes the following steps: S302: Determine whether the above latest accounting date included in the above first field information is later than the above first accounting date.

[0065] S304: In the case where the above latest accounting date is later than the above first accounting date, determine the asset balance data corresponding to the accounting date before the above first accounting date as the first asset data corresponding to the above start date.

[0066] Optionally, it is possible to determine whether the above-mentioned latest accounting date included in the above-mentioned first field information is later than the above-mentioned first accounting date through the following judgment statement: if last_selt_dt>dt ? last_bal: bal. Here, dt represents the first accounting date, and bal represents the asset balance data corresponding to the first accounting date.

[0067] Among them, the fact that the latest accounting date is later than the above-mentioned first accounting date means that after the first accounting date dt, the recorded asset data has changed, and the last change occurred on the accounting date represented by last_selt_dt. This means that the asset balance data bal corresponding to the first accounting date dt is no longer the latest, because asset changes (such as transactions, transfers, etc.) have occurred after dt. Therefore, it is necessary to use earlier data, that is, the asset balance data last_selt_dt of the accounting date before the first accounting date as the initial state data and the basic data for the simulation environment.

[0068] For example, the first accounting date dt = April 7, 2025, and the latest accounting date last_selt_dt when the data recorded on the first accounting date dt changed = April 8, 2025. That is to say, an asset change occurred on April 8 after April 7, 2025. Therefore, the first asset data (initial state data) takes last_bal, that is, the asset balance data on April 7, 2025.

[0069] S306: In the case where the above-mentioned latest accounting date is not later than the above-mentioned first accounting date, determine the asset balance data corresponding to the above-mentioned first accounting date as the first asset data corresponding to the above-mentioned start date.

[0070] Among them, the fact that the latest accounting date is not later than the above-mentioned first accounting date means that before or on the first accounting date dt, the last asset change has occurred. That is to say, the asset balance data bal corresponding to the first accounting date dt is the latest available asset balance data at present. In this case, the first asset data is determined to be bal, that is, the asset balance data corresponding to the first accounting date dt.

[0071] For example, assume that the first accounting date dt = April 9, 2025, and the latest accounting date last_selt_dt = April 8, 2025. This means that the last asset change occurred on April 8, and no asset change occurred on April 9. Therefore, the first asset data takes bal, that is, the asset balance data corresponding to April 9, 2025.

[0072] In the embodiments of this specification, by updating last_selt_dt when the first asset change is detected and recording the asset balance data last_bal of the previous accounting date, and selecting appropriate asset benchmark data based on the comparison between last_selt_dt and the first accounting date, the account status at the end of each accounting date can be accurately traced, improving the accuracy and consistency of data processing. At the same time, it provides a reliable basis for transaction processing, data verification, and historical backtracking, thereby enhancing the stability and manageability of the system.

[0073] In one embodiment, in the above step S204, the process of obtaining the actual result corresponding to the target event in the above current production environment includes the following steps: In the above current production environment, obtain the second asset data corresponding to the above end date; determine the above second asset data as the actual result corresponding to the above target event in the above current production environment. Among them, the end date may be the second accounting date.

[0074] It can be understood that in the above current production environment, the second asset data corresponding to the above end date can be obtained from the field information corresponding to the end date. The specific obtaining method is the same as the obtaining method of the above first asset data. That is, first obtain the second field information corresponding to the second accounting date. The second field information corresponding to the second accounting date is used to represent the end-of-day cross-sectional data of the second accounting date. The above second field information includes the latest accounting date when the data recorded in the second accounting date changes, the asset balance data corresponding to the accounting date before the above latest accounting date, and the asset balance data corresponding to the second accounting date. Determine whether the above latest accounting date included in the above second field information is later than the above second accounting date. If so, determine the asset balance data corresponding to the accounting date before the above second accounting date as the second asset data corresponding to the above end date. If not, determine the asset balance data corresponding to the above second accounting date as the second asset data corresponding to the above end date.

[0075] In the embodiments of this specification, by accurately obtaining and judging the field information of the second accounting date, the actual result of the target event can accurately reflect the corresponding asset balance data in the current production environment. By judging the change situation of the asset data, the data deviation caused by time difference is avoided, ensuring the consistency and accuracy of the asset data, effectively improving the reliability of the data, and providing a more accurate basis for subsequent data regression verification.

[0076] In one embodiment, in the above step S208, for the specific process of generating the simulation result, please refer to Figure 4 which is a schematic flowchart of a method for generating a simulation result provided by the embodiments of this specification. As Figure 4As shown in the figure, the method for generating the simulation result includes the following steps: S402: Import the above initial state data into the database of the preset simulation environment.

[0077] Among them, it is used to simulate the data and transaction logic in the actual production environment. The database is used to store the initial data in the simulation environment and the data generated during the simulation process.

[0078] S404: Resubmit the above target request data to the above simulation environment, and trigger the above simulation environment to execute the transaction logic corresponding to the above target request data based on the above database.

[0079] Optionally, resubmitting the above target request data to the above simulation environment means putting the target request data into the simulation environment again, so that the simulation environment performs simulation and calculation according to the initial state data and the target request data.

[0080] In one embodiment, the transaction logic corresponding to the above target request data refers to the specific processes and calculation rules that the system should execute in the simulation environment according to the transaction request data. For example, when processing a loan, logical processing will be performed based on the loan amount, borrower information, and account balance.

[0081] S406: When it is detected that the execution of the above transaction logic is completed, obtain the simulation result generated in the above simulation environment.

[0082] Among them, the simulation result is the output result generated after executing the transaction logic in the simulation environment, reflecting the execution result of the target event in the simulation environment, and specifically may include changes in asset data, account status, etc. after the transaction is completed.

[0083] In the embodiments of this specification, by importing the initial state data into the simulation environment and resubmitting the target request data, the system can simulate the execution process of the target event in a controlled virtual environment. The simulation environment can accurately execute the transaction logic corresponding to the target request data and generate a simulation result. In this way, the execution effect of the target event can be verified in the absence of a simulation environment, thereby improving the correctness and consistency of event execution in the production environment, effectively detecting and solving potential system problems, and enhancing the stability and reliability of the system.

[0084] In one embodiment, for the determination of each field information of the above first field information and second field information, before obtaining the initial state data and target request data corresponding to the target event in the current production environment, and obtaining the actual result corresponding to the above target event in the above current production environment, the above method further includes: For the current accounting date in the current production environment described above, when the first asset change occurs within the current accounting date, update the latest accounting date in the current field information corresponding to the current accounting date to the current accounting date, and update the asset balance data corresponding to the previous accounting date of the latest accounting date; when the current accounting date ends, update the asset balance data corresponding to the current accounting date.

[0085] Among them, when the asset change can be an asset change caused by any operation such as a transaction, transfer, repayment, etc., the last_selt_dt field can record the specific accounting date (such as T day) when the change occurs, and the last_bal field records the asset balance data at the end of the previous accounting date (such as T-1 day). This field can help the system accurately trace the status of the account at the end of a specific date, thus providing accurate basic data for subsequent transaction processing, data verification, and playback.

[0086] For example, in the current production environment, if the first asset change has not occurred in the current accounting date (April 9, 2025), and an asset change occurred on April 8, 2025, then the value of the current last_selt_dt field can be April 8, 2025. In the case where the first asset change (such as a loan disbursement) occurs in the current accounting date, update the value of the last_selt_dt field to April 9, 2025, and record the asset balance data corresponding to the previous accounting date (April 8, 2025) of the latest accounting date in the last_bal field.

[0087] In the embodiments of this specification, by updating the last_selt_dt and recording the asset balance data of the previous accounting date when the first asset change is detected, it is possible to accurately trace and record the status of the account at the end of each accounting date. The last_selt_dt field can identify the specific date of the last asset change, while the last_bal field provides the asset balance before that date, serving as an accurate basis for subsequent transaction processing, data verification, and playback. Thus, historical data can be better managed and traced back, improving the accuracy and consistency of data processing.

[0088] In one embodiment, in the above step S210, the specific process of generating the verification result is as follows Figure 5 which is a schematic flowchart of a method for generating a verification result provided by the embodiments of this specification. As Figure 5 shown, the method for generating the verification result includes the following steps: S502: Compare the above simulation results and the above actual results one by one based on the preset comparison fields to generate comparison results; wherein, the above preset comparison fields include the asset balance field and the user identification field.

[0089] Optionally, the preset comparison fields are data used to determine whether the simulation results are consistent with the actual results. Among them, the asset balance field is used to record the balance of the account, and the user identification field is an identifier used to identify different users.

[0090] It can be understood that the one-by-one comparison is to compare fields such as the asset balance and user identification generated in the simulation environment with the corresponding fields in the actual environment respectively. This one-by-one comparison method helps to verify the data consistency in different environments and effectively improves the comparison accuracy of the simulation results and the actual results.

[0091] In another embodiment, the preset comparison fields can also be determined based on other methods. For example: keyword fields can be automatically selected according to the mapping rules between event types and field labels. For example, for the "repayment" event, the asset balance field, transaction status field, etc. can be selected; or the large language model can be used to perform semantic parsing on the event type, field description, and table structure information to automatically generate a set of fields for comparison; further, clustering learning can also be performed based on the fields frequently used in historical verification cases to extract a typical comparison field template; in addition, a manual verification and field supplement mechanism can also be provided to allow the verification personnel to manually check the fields to be compared in specific scenarios to improve the flexibility and accuracy of field selection.

[0092] Through the above methods, it can be ensured that the selected fields have high relevance and business representativeness, thereby enhancing the effectiveness and comprehensiveness of the comparison between the simulation results and the actual results.

[0093] It can be understood that the comparison result can indicate that the above simulation result is inconsistent with the above actual result, or indicate that the above simulation result is consistent with the above actual result; further, if the comparison result indicates that the above simulation result is inconsistent with the above actual result, the comparison result can also include the target field information where the inconsistency exists, as well as the specific field content, such as field name, field type, and value, etc.

[0094] S504: Determine the environmental difference information between the above production environment and the above simulation environment based on the first environmental parameters of the above production environment and the second environmental parameters of the above simulation environment.

[0095] In one embodiment, based on the first environmental parameters of the collected production environment and the second environmental parameters of the simulation environment, the difference fields and their corresponding difference contents are compared and extracted to form a structured set of environmental difference information. Specifically, the environmental difference information includes, but is not limited to, system configuration parameter differences, dependent service access differences, version differences, cache mechanism differences, external interface status differences, and runtime resource condition differences, etc. Specifically, the corresponding interest rate parameters, transaction rule configurations, interface return values, thread resource usage status, etc. in the production environment and the simulation environment can be compared to identify whether there are key differences that affect the execution logic.

[0096] In another embodiment, the above environmental difference information can also be represented in vector form to depict the multi-dimensional difference characteristics between the production environment and the simulation environment. Specifically, based on a preset set of environmental parameters, the corresponding parameter values in the production environment and the simulation environment are respectively extracted, and the difference values between the corresponding parameter values in the production environment and the simulation environment are organized into a structured environmental difference vector. The environmental difference vector can include, but is not limited to, the following dimensions: system version difference, database parameter configuration difference, network latency difference, service call path difference, parameter item configuration difference, deployment architecture (such as distributed / standalone) difference, etc. Furthermore, in subsequent verification processing, the above environmental difference vector can be jointly analyzed with the above target field information to determine whether the verification anomaly of a certain field is related to environmental factors, thereby improving the accuracy and interpretability of the verification results.

[0097] By constructing environmental difference information in a vectorized manner, unified modeling of multi-dimensional environmental parameters can be achieved, providing a quantitative basis for generating subsequent verification results, and helping to improve the robustness and intelligent determination ability of the system against data fluctuations in complex test scenarios.

[0098] S506: Generate the verification result of the data to be verified based on the above environmental difference information and the above comparison result.

[0099] Furthermore, the environmental difference information is jointly analyzed with the field-level comparison results of the simulation result and the actual result to determine whether the simulation error is caused by environmental condition differences, and based on this, a more interpretable verification conclusion is generated. For example, if there is a difference in the "account balance" field between the two results, and this field is significantly affected by a certain environmental parameter, then the difference in this field can be marked as "caused by environmental difference, verification passed", thus avoiding misjudgment due to environmental differences. At the same time, this verification conclusion can also be used to generate a difference report or for developers to use for debugging.

[0100] Optionally, the verification result may be a judgmental conclusion generated for the data to be verified (such as the changed code or configuration), which is used to characterize whether the data can reproduce or match the actual performance of the production environment after running in the simulation environment.

[0101] In the embodiments of this specification, by introducing the analysis of environment difference information, only the intelligent level of simulation verification is improved, the adaptability of the verification process to complex contexts is enhanced, and the false alarm rate and the cost of manual troubleshooting are significantly reduced.

[0102] Optionally, in S506, generating the verification result of the data to be verified based on the environment difference information and the comparison result may include: when the comparison result indicates that the simulation result is inconsistent with the actual result, determining the target field information including the inconsistency in the comparison result; analyzing and processing the target field information based on the environment difference information to determine the marking information corresponding to the target field information, where the marking information is used to indicate whether the corresponding field difference information of the target field information is related to the environment difference information; generating the verification result of the data to be verified according to the marking information corresponding to the target field information.

[0103] In one embodiment, a field influence factor mapping table may be preset, which is used to indicate which environmental parameters various fields may be affected by. For example, the account balance field may be affected by environmental factors such as interest rate parameters and settlement cycle configurations. Then, when it is detected that there is a difference in a certain field in the comparison result, the environmental parameters that it may be associated with are extracted through the field influence factor mapping table and matched and analyzed with the current environment difference information. If the match is successful, it can be further determined through a relevant rule engine or model calculation whether the difference may be caused by environmental changes, thereby generating a marking information, such as "affected by environment difference", "business logic inconsistent", or "unknown reason". Subsequently, the final verification result is generated based on the above marking information. Specifically, if the field difference is marked as "affected by environment difference", the field can be regarded as passing the verification; if it is marked as "business logic difference" or "unknown reason", the data corresponding to the field can be regarded as failing the verification or requiring further manual review. Finally, the verification conclusions of all fields are comprehensively judged to generate a unified verification result. The verification result may not only include the overall verification conclusion, but also include the comparison information of each field, the explanation of the difference reason, and the recommended processing actions. Specifically, if all field differences can be explained by the environment difference information, the verification result may be passed or acceptable without further intervention; if there are field differences unrelated to the environment, the verification result is not passed or requires review, and includes the comparison information of each field, the explanation of the difference reason, and the recommended processing actions to prompt further troubleshooting. Thereby, the automation and interpretability of the verification process are improved, and the cost of manual intervention is effectively reduced.

[0104] In the embodiments of this specification, through the above verification mechanism that combines environmental difference information and field difference analysis, it is possible to achieve a refined attribution of the reasons for the inconsistency between the simulation results and the actual results, and improve the intelligence level of the verification process. Thus, not only can it be determined whether there is a data difference, but it can also be further determined whether the difference is caused by factors such as configuration differences and parameter offsets between the simulation environment and the production environment. On the one hand, this avoids misreporting differences that should be tolerated as defects, improving the accuracy and credibility of the verification conclusion; on the other hand, it can promptly discover abnormal fields that are not related to the environment, effectively supporting defect location and rapid repair, and significantly improving the overall verification efficiency and system stability.

[0105] The following further illustrates the embodiments of this specification in combination with specific scenarios. Please refer to Figure 6 , Figure 6 which is a detailed architecture schematic diagram of a data verification system provided by the embodiments of this specification. As Figure 6As shown in the figure, the data verification system architecture may include an online system corresponding to the production environment (i.e., the production system) and an online system corresponding to the simulation environment (i.e., the simulation system). The upstream production traffic in the production system is the target request data corresponding to the target event in the current production environment, and the institutional asset data A is the actual result corresponding to the target event in the current production environment. This actual result is the result obtained by processing based on the original transaction processing logic. The playback traffic in the simulation system is the target request data flowing back to the simulation environment, and the institutional asset data B is the simulation result generated in the simulation environment. This simulation result is the result obtained by processing the transaction processing logic corresponding to the new code. Further, offline data can be obtained from the production system. This offline data includes the first asset data corresponding to the start date of the target event (the end-of-day cross-sectional data on day T-1), and the second asset data corresponding to the end date of the target event (the end-of-day cross-sectional data on day T), and may also include traffic data; and, offline data can be obtained from the simulation system. This offline data includes the first asset data corresponding to the start date of the target event, and the second asset data corresponding to the end date of the target event, and may also include traffic data. Furthermore, data can be returned for the offline data in the production environment and the offline data in the simulation environment respectively through the Open Data Processing Service (ODPS), and the data is imported into the offline platform, so as to perform a one-to-one comparison at the field level for the offline data in the production environment and the offline data in the simulation environment to obtain a comparison result. Furthermore, based on the first environmental parameter of the production environment and the second environmental parameter of the simulation environment, the environmental difference information between the production environment and the simulation environment is determined, and based on the environmental difference information and the comparison result, the verification result of the data to be verified is generated. This verification result can indicate "passed" or "failed". Among them, ODPS is a distributed platform that can provide massive data offline processing services. The above regression verification process can be promoted through a relevant process platform. Specifically, the advancement of each task node of the simulation playback can be carried out in the way of task orchestration. This process connects tasks through the process platform and can automatically complete the entire simulation playback process without manual participation, effectively improving the efficiency of regression verification.

[0106] It should be understood that although the steps in the flowcharts involved in the above-described embodiments are sequentially shown according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear indication in this article, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-described embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be executed alternately or alternately with at least a part of other steps or steps or stages in other steps.

[0107] Based on the inventive concept of the above data verification method, as Figure 7 shown, an embodiment of this specification further provides a data verification device 700 for implementing the above-mentioned data verification method. The data verification device 700 includes: A determination module 701, configured to determine, according to preset event type information, the start date and end date of a corresponding target event in the current production environment, and obtain target request data corresponding to the event type information included within the above start date to the above end date; An acquisition module 702, configured to acquire the actual result corresponding to the above target event in the above production environment, and acquire the first field information corresponding to the above start date, where the first field information includes the latest date when the data recorded on the above start date changes, the target object status data corresponding to the date before the above latest date, and the target object status data corresponding to the above start date; A comparison module 703, configured to compare the above latest date and the above start date to determine the initial state data corresponding to the above start date; A reflux module 704, configured to reflux the above initial state data and the above target request data to a preset simulation environment to generate a simulation result, where the above simulation environment is a simulation environment constructed based on the data to be verified; A generation module 705, configured to generate a verification result of the above data to be verified according to the first environment parameter of the above production environment, the second environment parameter of the above simulation environment, the above actual result, and the above simulation result In one embodiment, the above target request data includes transaction request information corresponding to the event type information included within the above start date to the above end date, and the target object status data corresponding to the above start date includes the first asset data corresponding to the above start date.

[0108] In one embodiment, the above start date is the first accounting date, and the above end date is the second accounting date; the latest date when the data recorded at the above start date is changed is the latest accounting date when the data recorded at the above first accounting date is changed, and the target object status data corresponding to the date before the above latest date is the asset balance data corresponding to the accounting date before the above latest accounting date; The above comparison module 703 includes: A judgment unit, configured to judge whether the above latest accounting date included in the above first field information is later than the above first accounting date; A first determination unit, configured to, when the above latest accounting date is later than the above first accounting date, determine the asset balance data corresponding to the accounting date before the above first accounting date as the first asset data corresponding to the above start date; A second determination unit, configured to, when the above latest accounting date is not later than the above first accounting date, determine the asset balance data corresponding to the above first accounting date as the first asset data corresponding to the above start date.

[0109] In one embodiment, the above acquisition module 702 includes: A first acquisition unit, configured to acquire the second asset data corresponding to the above end date in the above production environment; A third determination unit, configured to determine the above second asset data as the actual result corresponding to the above target event in the above production environment.

[0110] In one embodiment, the above device 700 further includes: A first update module, configured to, for the current accounting date in the above production environment, when it is detected that the first asset change occurs within the above current accounting date, update the latest accounting date in the current field information corresponding to the above current accounting date to the above current accounting date, and update the asset balance data corresponding to the accounting date before the above latest accounting date; A second update module, configured to update the asset balance data corresponding to the above current accounting date when the above current accounting date ends.

[0111] In one embodiment, the reflux module 704 includes: An import unit, configured to import the above initial state data into the database of the preset simulation environment; An execution unit, configured to re-inject the above target request data into the above simulation environment, and trigger the above simulation environment to execute the transaction logic corresponding to the above target request data based on the above database; A fourth determination unit, configured to obtain the simulation result generated in the above simulation environment when it is detected that the execution of the above transaction logic is completed.

[0112] In one embodiment, the above-mentioned generation module 705 includes: A comparison unit, configured to compare the above-mentioned simulation result and the above-mentioned actual result one by one based on a preset comparison field, and generate a comparison result; wherein, the above-mentioned preset comparison field includes an asset balance field and a user identification field; A fifth determination unit, configured to determine the environmental difference information between the above-mentioned production environment and the above-mentioned simulation environment based on the first environmental parameter of the above-mentioned production environment and the second environmental parameter of the above-mentioned simulation environment; A generation unit, configured to generate a verification result of the above-mentioned data to be verified based on the above-mentioned environmental difference information and the above-mentioned comparison result.

[0113] In one embodiment, the generation unit includes: A determination subunit, configured to determine the target field information included in the above-mentioned comparison result that is inconsistent in the case where the above-mentioned comparison result indicates that the above-mentioned simulation result is inconsistent with the above-mentioned actual result; A processing subunit, configured to analyze and process the above-mentioned target field information based on the above-mentioned environmental difference information to determine the marking information corresponding to the above-mentioned target field information, and the above-mentioned marking information is used to indicate whether the corresponding field difference information of the above-mentioned target field information is related to the above-mentioned environmental difference information; A generation subunit, configured to generate a verification result of the above-mentioned data to be verified according to the marking information corresponding to the above-mentioned target field information.

[0114] Each module in the above-mentioned data verification device 700 can be implemented in whole or in part by software, hardware, and their combination. Each of the above-mentioned modules can be embedded in or independent of a processor in a computer device in the form of hardware, or stored in a memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above-mentioned modules.

[0115] This specification embodiment also provides an electronic device, which may be a server, and its internal structure diagram may be as Figure 8As shown in the figure. The electronic device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O), and a communication interface. Among them, the processor, the memory, and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the electronic device is used to exchange information between the processor and external devices. The communication interface of the electronic device is used to communicate with an external terminal through a network connection. The processor of the electronic device executes the computer program to implement a data verification method.

[0116] Those skilled in the art can understand that Figure 8 the structure shown in the figure is only a block diagram of some structures related to the solution of the embodiments of this specification, and does not constitute a limitation on the electronic device to which the solution of the embodiments of this specification is applied. The specific electronic device may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0117] In a possible implementation manner, a computer storage medium is provided. Instructions are stored in the computer storage medium. When it runs on a computer or a processor, it causes the computer or the processor to execute one or more steps in the above embodiments. If each component module of the above electronic device is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in the above computer-readable storage medium.

[0118] In a possible implementation manner, a computer program product is provided, including a computer program. When the computer program is executed by a processor, it implements the steps in the above method embodiments.

[0119] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The above computer program product includes one or more computer instructions. When the above computer program instructions are loaded and executed on a computer, the processes or functions described above in the embodiments of this specification are generated in whole or in part. The above computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The above computer instructions can be stored in a computer storage medium or transmitted through the above computer storage medium. The above computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired manner (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The above computer storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The above available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a Digital Versatile Disc (DVD)), or a semiconductor medium (such as a Solid State Disk (SSD)), etc.

[0120] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data for analysis, stored data, displayed data, etc.), and signals involved in the embodiments of this specification are all authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with the relevant laws, regulations, and standards of relevant countries and regions. For example, the account balance, loan balance, amount to be repaid, user identification field, asset balance data, etc. involved in this specification are all obtained under sufficient authorization.

[0121] Those of ordinary skill in the art can understand that all or part of the processes of implementing the methods in the above embodiments can be completed by instructing relevant hardware through a computer program. This program can be stored in a computer-readable storage medium. When this program is executed, it can include the processes of the embodiments of the above methods. The foregoing storage medium includes: various media such as ROM, RAM, magnetic disk, or optical disc that can store program codes. Without conflict, the technical features in this embodiment and the implementation solutions can be combined arbitrarily.

[0122] The above-described embodiments are merely described as preferred implementation manners of the embodiments of this specification, and do not limit the scope of the embodiments of this specification. Without departing from the design spirit of the embodiments of this specification, various deformations and improvements made by those of ordinary skill in the art to the technical solutions of the embodiments of this specification shall fall within the protection scope determined by the claims.

[0123] Specific embodiments of the embodiments of this specification have been described above. Other embodiments are within the scope of the appended claims. In some cases, the acts or steps recited in the claims may be performed in a different order than in the embodiments and still achieve the desired result. Additionally, the processes depicted in the figures do not necessarily require the particular order shown or sequential order to achieve the desired result. In certain implementations, multitasking and parallel processing are also possible or may be advantageous.

Claims

1. A data verification method, the method comprising: Determining a start date and an end date of a corresponding target event in a current production environment according to preset event type information, and obtaining target request data corresponding to the event type information included within the start date to the end date; Obtaining an actual result corresponding to the target event in the production environment, and obtaining first field information corresponding to the start date, where the first field information includes a latest date when data recorded on the start date is changed, target object status data corresponding to a date before the latest date, and target object status data corresponding to the start date; Comparing the latest date and the start date to determine initial status data corresponding to the start date; Flowing back the initial status data and the target request data to a preset simulation environment to generate a simulation result, where the simulation environment is a simulation environment constructed based on data to be verified; Generating a verification result of the data to be verified according to a first environment parameter of the production environment, a second environment parameter of the simulation environment, the actual result, and the simulation result.

2. The method according to claim 1, where the target request data includes transaction request information corresponding to the event type information included within the start date to the end date, and the target object status data corresponding to the start date includes first asset data corresponding to the start date.

3. The method according to claim 2, where the start date is a first accounting date, and the end date is a second accounting date; the latest date when data recorded on the start date is changed is the latest accounting date when data recorded on the first accounting date is changed, and the target object status data corresponding to a date before the latest date is asset balance data corresponding to an accounting date before the latest accounting date; The comparing the latest date and the start date to determine initial status data corresponding to the start date includes: Judging whether the latest accounting date is later than the first accounting date; When the latest accounting date is later than the first accounting date, determining asset balance data corresponding to an accounting date before the first accounting date as the first asset data corresponding to the start date; When the latest accounting date is not later than the first accounting date, determining asset balance data corresponding to the first accounting date as the first asset data corresponding to the start date.

4. The method according to claim 2, where the obtaining the actual result corresponding to the target event in the production environment includes: In the production environment, obtaining second asset data corresponding to the end date; Determining the second asset data as the actual result corresponding to the target event in the production environment.

5. The method according to claim 3, before obtaining the target request data corresponding to the event type information included within the start date to the end date, the method further includes: For the current accounting date in the production environment, when it is detected that the first asset change occurs within the current accounting date, update the latest accounting date in the current field information corresponding to the current accounting date to the current accounting date, and update the asset balance data corresponding to the previous accounting date of the latest accounting date; When the current accounting date ends, update the asset balance data corresponding to the current accounting date.

6. The method according to claim 1, wherein the flowing back the initial state data and the target request data to a preset simulation environment to generate a simulation result comprises: Importing the initial state data into the database of the preset simulation environment; Resending the target request data to the simulation environment, and triggering the simulation environment to execute the transaction logic corresponding to the target request data based on the database; When it is detected that the execution of the transaction logic is completed, obtaining the simulation result generated in the simulation environment.

7. The method according to claim 1, wherein the generating the verification result of the data to be verified according to the first environment parameter of the production environment, the second environment parameter of the simulation environment, the actual result and the simulation result comprises: Performing one-by-one comparison on the simulation result and the actual result based on a preset comparison field to generate a comparison result, wherein the preset comparison field comprises an asset balance field and a user identification field; Determining the environment difference information between the production environment and the simulation environment based on the first environment parameter of the production environment and the second environment parameter of the simulation environment; Generating the verification result of the data to be verified based on the environment difference information and the comparison result.

8. The method according to claim 7, wherein the generating the verification result of the data to be verified based on the environment difference information and the comparison result comprises: When the comparison result indicates that the simulation result is inconsistent with the actual result, determining the inconsistent target field information included in the comparison result; Analyzing and processing the target field information based on the environment difference information to determine the marking information corresponding to the target field information, where the marking information is used to indicate whether the corresponding field difference information of the target field information is related to the environment difference information; Generating the verification result of the data to be verified according to the marking information corresponding to the target field information.

9. A data verification device, the device comprising: A determining module, configured to determine the start date and end date of a corresponding target event in the current production environment according to preset event type information, and obtain the target request data corresponding to the event type information included from the start date to the end date; An obtaining module, configured to obtain the actual result corresponding to the target event in the production environment, and obtain the first field information corresponding to the start date, where the first field information comprises the latest date when the data recorded by the start date changes, the target object status data corresponding to the previous date of the latest date, and the target object status data corresponding to the start date; A comparison module for comparing the latest date and the start date to determine the initial state data corresponding to the start date; A feedback module for feeding back the initial state data and the target request data to a preset simulation environment to generate a simulation result, wherein the simulation environment is a simulation environment constructed based on the data to be verified; A generation module for generating a verification result of the data to be verified according to the first environment parameters of the production environment, the second environment parameters of the simulation environment, the actual result and the simulation result.

10. An electronic device, comprising: A processor and a memory; The memory stores a computer program, and when the processor executes the computer program, the method according to any one of claims 1-8 is implemented.

11. A computer storage medium storing multiple instructions, the instructions being adapted to be loaded and executed by a processor to perform the method according to any one of claims 1-8.

12. A computer program product containing instructions, when the computer program product runs on a computer or a processor, causing the computer or the processor to execute the method according to any one of claims 1-8.

Images