A problem data tracing method, device, equipment, storage medium and product

Abstract

The embodiment of the present specification relates to the field of data analysis, in particular, to a problem data tracing method and device, equipment, storage medium and product, wherein the method comprises: determining the upper sending file in the pasting source layer corresponding to the to-be-traced data according to the record in the supervision table; determining the end system corresponding to the to-be-traced data and the transaction message corresponding to the end system according to the upper sending file of the to-be-traced data; judging whether the current system is the source system of the to-be-traced data; if yes, taking the current system as the link source node of the to-be-traced data; if not, taking the current system as the link process node of the to-be-traced data; determining the last system of the current system according to the transaction message corresponding to the current system; obtaining the transaction message corresponding to the last system; cyclically executing the judgment step; sequentially obtaining the transaction message corresponding to the link upper node of the to-be-traced data to check the problem. The embodiment of the present specification can improve the efficiency and accuracy of problem data tracing.

Description

Technical Field

[0001] This specification relates to the field of data analysis, and in particular to a method, apparatus, device, storage medium, and product for tracing the source of problematic data. Background Technology

[0002] In recent years, regulatory agencies such as the People's Bank of China and the China Banking and Insurance Regulatory Commission have conducted numerous regulatory inspections of banking institutions, including compliance checks on information such as the purpose of transfers, summaries, and account details of the transacting parties in the submitted data. In-depth analysis of data-related issues raised by regulatory agencies and internal and external auditing firms reveals that the main problem lies in the difficulty of data traceability, leading to low efficiency in subsequent data analysis.

[0003] Currently, the data reported by bank regulators is mainly processed and generated within data warehouses, and is reported daily (T+1) or monthly. Therefore, the current verification methods are based on the end tables that need to be reported, rather than the source data. Based on the current verification methods targeting the result tables, problems can only be identified, but the responsible party cannot be found. Therefore, the process relies on experience to trace the source upstream, making data tracing extremely difficult, inefficient, and inaccurate.

[0004] Therefore, there is an urgent need for a problem data tracing method that can improve the efficiency and accuracy of problem data tracing. Summary of the Invention

[0005] The purpose of the embodiments in this specification is to provide a method, apparatus, device, storage medium, and product for tracing problem data, so as to improve the efficiency and accuracy of problem data tracing.

[0006] To achieve the above objectives, on the one hand, embodiments of this specification provide a method for tracing the source of problem data, including:

[0007] When business transactions occur between different systems, starting from the source system, each system generates its own corresponding transaction message and sends the transaction message to the next system with which it has a business transaction, until the end system of the business transaction;

[0008] Each system records its own corresponding transaction messages, as well as the business scenarios and business characteristics of the next system with which it has business transactions.

[0009] The terminal system generates an upload file based on its corresponding transaction message and uploads the upload file to the data warehouse's source layer.

[0010] The data warehouse generates a monitoring table based on the uploaded files received by the source layer;

[0011] When it is necessary to trace the source of the data to be traced, the uploaded file in the corresponding posting layer is determined based on the records in the regulatory table.

[0012] Based on the uploaded file of the data to be traced, determine the end system corresponding to the data to be traced, and the transaction message corresponding to the end system;

[0013] The terminal system is used as the current system;

[0014] Determine whether the current system is the source system of the data to be traced;

[0015] If so, the current system will be used as the source node of the data to be traced.

[0016] If not, then:

[0017] The current system is used as a link process node for the data to be traced.

[0018] Based on the transaction message corresponding to the current system, determine the previous system of the current system;

[0019] Based on the business scenario and business characteristics of the current system recorded in the previous system, match them with the transaction message corresponding to the current system to obtain the transaction message corresponding to the previous system;

[0020] Using the previous system as the current system, the above judgment steps are executed repeatedly.

[0021] Sequentially retrieve the transaction messages corresponding to all nodes on the data to be traced in the chain to check for problems.

[0022] Preferably, the process of each system generating its own corresponding transaction message, starting from the source system, and sending the transaction message to the next system with which it has a business transaction, until the end system of the business transaction further includes:

[0023] S1: The source system is used as the sending system. The sending system generates the transaction message corresponding to the sending system based on its own business scenario, business characteristics, source system, business sender and business data.

[0024] S2: The sending system sends its corresponding transaction message to the receiving system with which it has a business transaction;

[0025] S3: The receiving system generates a transaction message corresponding to the sending system based on the transaction message corresponding to the sending system;

[0026] S4: When the receiving system has subsequent business transactions, the receiving system is used as the new sending system. The new sending system sends its corresponding transaction message to the new receiving system of the subsequent business transaction. Steps S3-S4 are repeated until the new receiving system becomes the end system of the business transaction.

[0027] Preferably, the process of generating the transaction message corresponding to the sending system based on the business scenario, business characteristics, source system, business sender, and business data further includes:

[0028] The sending system generates a scenario code based on the business scenario, a business identifier number based on the business characteristics, a source code based on the source system, and a sending code based on the business sender.

[0029] By integrating the scenario code, business identifier, source code, sender code, and business data, a transaction message corresponding to the sender system is generated.

[0030] Preferably, the step of generating a business identifier based on business characteristics further includes:

[0031] The server hosting the sending system has a computing system installed.

[0032] The computing system performs calculations on the source code corresponding to the business source, the server code where the sending system is located, and the current time representation value of the business transaction according to the computing rules, and obtains the computing value.

[0033] The computing system randomly integrates the source code, the server code of the sending system, the current time representation value of the business transaction, and the computing value to generate a business identifier.

[0034] Preferably, the computing system performs calculations on the source code corresponding to the business source, the server code where the sending system is located, and the current time representation value of the business transaction according to the calculation rules, and the calculated value further includes:

[0035] The arithmetic system selects the arithmetic rule pointed to by the first pointer and the arithmetic rule pointed to by the second pointer from the four arithmetic rules of addition, subtraction, multiplication and division;

[0036] The source code and the server code are operated on according to the operation rule pointed to by the first pointer to obtain the first operation result;

[0037] The second calculation result is obtained by performing calculations on the first calculation result and the current time representation value according to the arithmetic rules pointed to by the second pointer;

[0038] Take the value of the specified number of bits in the second operation result as the operation value;

[0039] The computing system shifts the first pointer and / or the second pointer.

[0040] Preferably, the shifting of the first pointer and / or the second pointer by the computing system further includes:

[0041] If the first pointer and the second pointer point to the same arithmetic operation, then the first pointer or the second pointer is shifted;

[0042] If the first pointer and the second pointer point to different arithmetic rules, then the first pointer and / or the second pointer will be shifted.

[0043] Preferably, the process of generating a service identifier by randomly integrating the source code, the server code of the sending system, the current time representation value of the business transaction, and the calculated value further includes:

[0044] At least one of the following is randomly selected from the source code, the server code of the sending system, and the current time representation value of the business transaction;

[0045] The selected entity is sequentially combined with the calculated value to generate a business identifier.

[0046] Preferably, the process of generating a transaction message corresponding to the receiving system based on the transaction message corresponding to the sending system further includes:

[0047] The receiving system obtains the source system and business characteristics corresponding to the sending system based on the transaction message corresponding to the sending system;

[0048] The source system corresponding to the sending system is taken as the source system corresponding to the receiving system;

[0049] The service characteristics corresponding to the sending system are used as the service characteristics corresponding to the receiving system.

[0050] The sending system is designated as the service sender corresponding to the receiving system.

[0051] The receiving system generates a transaction message corresponding to its own business scenario, business characteristics, source system, business sender, and business data.

[0052] Preferably, each record in the regulatory table includes a business scenario code, a business identifier, a source code, and business data.

[0053] Preferably, the process of generating the upload file based on its corresponding transaction message further includes:

[0054] The terminal system generates the upload file based on the business scenario code, business identifier, source code, and business data in its corresponding transaction message.

[0055] Preferably, determining the end system corresponding to the data to be traced, and the transaction message corresponding to the end system, based on the uploaded file of the data to be traced, further includes:

[0056] Based on the uploaded file of the data to be traced, determine the business scenario code and business identifier corresponding to the data to be traced;

[0057] Based on the business scenario code and business identifier, determine the end system corresponding to the data to be traced, and the transaction message corresponding to the end system.

[0058] Preferably, determining the previous system of the current system based on the transaction message corresponding to the current system further includes:

[0059] Based on the sender code in the transaction message corresponding to the current system, determine the previous system of the current system, where the code of the previous system is the sender code.

[0060] Preferably, the step of matching the current system's business scenario and business characteristics recorded in the previous system with the transaction message corresponding to the current system to obtain the transaction message corresponding to the previous system further includes:

[0061] Based on the transaction message corresponding to the current system, determine the actual business scenario code and business identifier number corresponding to the current system;

[0062] The actual business scenario code and business identifier are matched with the business scenario code and business identifier recorded in the previous system to obtain the transaction message of the previous system corresponding to the matching business scenario code and business identifier.

[0063] On the other hand, embodiments of this specification provide a problem data tracing device, the device comprising:

[0064] The transaction message generation module is used to generate its own corresponding transaction message starting from the source system when business transactions are conducted between different systems, and send the transaction message to the next system with which it has a business transaction, until the end system of the business transaction; wherein each system records its own corresponding transaction message, as well as the business scenario and business characteristics corresponding to the next system with which it has a business transaction;

[0065] The upload module is used by the terminal system to generate an upload file based on its corresponding transaction message and upload the upload file to the data warehouse's source layer.

[0066] The regulatory table generation module is used by the data warehouse to generate regulatory tables based on the uploaded files received by the source layer.

[0067] The upload file determination module is used to determine the upload file in the source layer corresponding to the data to be traced, based on the records in the supervision table, when it is necessary to trace the source of the data to be traced.

[0068] The end-system determination module is used to determine the end-system corresponding to the data to be traced, and the transaction message corresponding to the end-system, based on the uploaded file of the data to be traced.

[0069] The current system determination module is used to identify the terminal system as the current system;

[0070] The judgment module is used to determine whether the current system is the source system of the data to be traced.

[0071] If so, the current system will be used as the source node of the data to be traced.

[0072] If not, then:

[0073] The current system is used as a link process node for the data to be traced.

[0074] Based on the transaction message corresponding to the current system, determine the previous system of the current system;

[0075] Based on the business scenario and business characteristics of the current system recorded in the previous system, match them with the transaction message corresponding to the current system to obtain the transaction message corresponding to the previous system;

[0076] Using the previous system as the current system, the above judgment steps are executed repeatedly.

[0077] The acquisition module is used to sequentially acquire the transaction messages corresponding to all nodes on the data to be traced in order to check for problems.

[0078] In another aspect, embodiments of this specification also provide a computer device, including a memory, a processor, and a computer program stored in the memory, wherein the computer program, when executed by the processor, performs instructions of any of the methods described above.

[0079] In another aspect, embodiments of this specification also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor of a computer device, performs instructions according to any one of the methods described above.

[0080] In another aspect, embodiments of this specification also provide a computer program product, which, when run by the processor of a computer device, executes instructions for any of the methods described above.

[0081] The method described in this specification involves each system recording its corresponding transaction message, as well as the business scenario and characteristics of the next system, during the data upload process for subsequent backtracking. After the end system generates an upload file based on its corresponding transaction message, the upload file is uploaded to the data warehouse to generate a monitoring table. When performing data tracing, the records in the monitoring table are used as a basis to gradually trace back to the end system, and then the end system iteratively determines and traces back to the source system, thus connecting the entire link corresponding to the data to be traced. Problems are checked based on the transaction messages corresponding to all nodes in the link.

[0082] To make the above and other objects, features and advantages of this specification more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0083] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0084] Figure 1 A flowchart illustrating a problem data tracing method provided in an embodiment of this specification is shown.

[0085] Figure 2 This document illustrates a flowchart of the process by which the sender system, as provided in the embodiments of this specification, generates transaction messages corresponding to the sender system based on business scenarios, business characteristics, source systems, business senders, and business data.

[0086] Figure 3 A schematic diagram of the process for generating a business identifier number based on business characteristics, provided in an embodiment of this specification, is shown.

[0087] Figure 4 This document illustrates a flowchart of a process for obtaining a calculated value through calculation, as provided in an embodiment of this specification.

[0088] Figure 5 This document illustrates a flowchart of the operation system provided in an embodiment of the present specification, which shifts a first pointer and / or a second pointer.

[0089] Figure 6 A schematic diagram illustrating the process of generating a service identifier using the computing system provided in the embodiments of this specification is shown.

[0090] Figure 7This document illustrates a flowchart of the process by which the receiving system generates the corresponding transaction message, as provided in the embodiments of this specification.

[0091] Figure 8 This document illustrates a flowchart illustrating how an embodiment of the present specification determines the end system corresponding to the data to be traced, and the transaction message corresponding to the end system, based on the uploaded file of the data to be traced.

[0092] Figure 9 This specification illustrates a flowchart of the process for obtaining the transaction message corresponding to the previous system, as provided in an embodiment of this specification.

[0093] Figure 10 This specification shows a schematic diagram of the module structure of a problem data tracing device provided in an embodiment;

[0094] Figure 11 A schematic diagram of the structure of a computer device provided in an embodiment of this specification is shown.

[0095] Explanation of symbols in the attached drawings:

[0096] 100. Transaction message generation module;

[0097] 200. Upload module;

[0098] 300. Regulatory form generation module;

[0099] 400. File submission confirmation module;

[0100] 500. End-system determination module;

[0101] 600. Current system determination module;

[0102] 700. Judgment Module;

[0103] 800. Acquisition Module;

[0104] 1102. Computer equipment;

[0105] 1104. Processor;

[0106] 1106. Memory;

[0107] 1108. Drive mechanism;

[0108] 1110. Input / output module;

[0109] 1112. Input devices;

[0110] 1114. Output devices;

[0111] 1116. Presentation device;

[0112] 1118. Graphical User Interface;

[0113] 1120. Network interface;

[0114] 1122. Communication link;

[0115] 1124. Communication bus. Detailed Implementation

[0116] The technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the embodiments of this specification.

[0117] Currently, the data reported by bank regulators is mainly processed and generated within data warehouses, and is reported daily (T+1) or monthly. Therefore, the current verification methods are based on the end tables that need to be reported, rather than the source data. Based on the current verification methods targeting the result tables, problems can only be identified, but the responsible party cannot be found. Therefore, the process relies on experience to trace the source upstream, making data tracing extremely difficult, inefficient, and inaccurate.

[0118] To address the aforementioned issues, this specification provides a method for tracing the source of problematic data. Figure 1 This is a flowchart illustrating a problem data tracing method provided in an embodiment of this specification. This specification provides the operational steps of the method described in the embodiment or flowchart, but based on conventional or non-inventive labor, more or fewer operational steps may be included. The order of steps listed in the embodiment is merely one possible execution order among many and does not represent the only possible execution order. In actual system or device products, the methods shown in the embodiment or drawings can be executed sequentially or in parallel.

[0119] It should be noted that the terms "first," "second," etc., in the description, claims, and accompanying drawings of the embodiments in this specification are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, apparatus, product, or device that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0120] Reference Figure 1 This specification provides a method for tracing the source of problem data, including:

[0121] S101: When business transactions are conducted between different systems, starting from the source system, each system generates its own corresponding transaction message and sends the transaction message to the next system with which it has a business transaction, until the end system of the business transaction.

[0122] Each system records its own corresponding transaction messages, as well as the business scenarios and business characteristics of the next system with which it has business transactions.

[0123] S102: The terminal system generates an upload file based on its corresponding transaction message and uploads the upload file to the data warehouse's source layer;

[0124] S103: The data warehouse generates a monitoring table based on the uploaded files received by the source layer;

[0125] S104: When it is necessary to trace the source of the data to be traced, determine the uploaded file in the source layer corresponding to the data to be traced based on the records in the supervision table;

[0126] S105: Determine the end system corresponding to the data to be traced based on the uploaded file of the data to be traced;

[0127] S106: Designate the terminal system as the current system;

[0128] S107: Determine whether the current system is the source system of the data to be traced;

[0129] S108: If so, then the current system shall be regarded as the source node of the data to be traced;

[0130] S109: If not, then:

[0131] The current system is used as a link process node for the data to be traced.

[0132] Based on the transaction message corresponding to the current system, determine the previous system of the current system;

[0133] Based on the business scenario and business characteristics of the current system recorded in the previous system, match them with the transaction message corresponding to the current system to obtain the transaction message corresponding to the previous system;

[0134] Using the previous system as the current system, the above judgment steps are executed repeatedly.

[0135] S110: Sequentially retrieve the transaction messages corresponding to all nodes on the link of the data to be traced in order to check for problems.

[0136] For example, a business transaction between different systems, such as Li transferring 10,000 yuan to Zhang, requires multiple different systems to pass through. For instance, system A receives the transfer request and needs to forward it to system B for transaction verification (such as verifying whether the transferor and the recipient are blacklisted users). After successful verification, system B forwards the transfer request to system C for the actual transfer operation.

[0137] When business transactions occur between different systems, starting from the source system, each system generates its own corresponding transaction message and sends it to the next system with which it has a business transaction, until the end system of the business transaction. In the example above, the source system is system A and the end system is system C. While sending the transaction message to the next system, each system records its own corresponding transaction message, as well as the business scenario and business characteristics corresponding to the next system with which it has a business transaction. For example, system A will record its own corresponding transaction message and store the business scenario and business characteristics corresponding to system B. The business scenario is used to characterize the business attributes of the current system, and the business characteristics can uniquely identify a business transaction. For example, the business scenario of system A is receiving a transaction request, the business scenario of system B is transaction verification, and the business scenario of system C is transaction operation. A transfer transaction has its own unique corresponding business characteristics.

[0138] It is important to note that the transaction messages corresponding to each system, as well as the business scenarios and characteristics of the next system with which it has business transactions, must be recorded to facilitate subsequent traceability.

[0139] The terminal system generates an upload file based on its corresponding transaction message and uploads the upload file to the source layer of the data warehouse. The data warehouse generates a regulatory table based on the upload file received by the source layer. The source layer stores the most original and authentic data in the data warehouse without much processing. The data warehouse can perform various other processing on the data in the source layer based on actual needs. The regulatory table is used to submit to regulatory agencies such as the People's Bank of China and the China Banking and Insurance Regulatory Commission to conduct regulatory inspections on banking institutions.

[0140] If suspected problematic data is found in the regulatory table during regulatory inspection, it is necessary to trace the source of the problematic data. In this case, the problematic data is considered as data to be traced.

[0141] When it is necessary to trace the source of data, the uploaded file in the source layer corresponding to the data to be traced is determined according to the records in the regulatory table. Based on the uploaded file of the data to be traced, the end system corresponding to the data to be traced and the transaction message corresponding to the end system are determined. The end system is used as the current system to determine whether the current system is the source system of the data to be traced.

[0142] If it's not the source system, the previous system is determined based on the transaction messages of the current system. Since the previous system contains various transaction messages, it's necessary to further identify the transaction messages corresponding to the data to be traced. Specifically, the previous system records the business scenarios and characteristics of all related next systems. These business scenarios and characteristics are matched with the transaction messages corresponding to the current system. Successfully matched business scenarios and characteristics are the business scenarios and characteristics corresponding to the current system, and the transaction messages of the previous system corresponding to these business scenarios and characteristics are the transaction messages corresponding to the data. This process can be repeated until the source system is found. Each node obtained in the cyclical order can serve as a link corresponding to the data to be traced, and the transaction messages corresponding to all nodes on this link can be used as the basis for checking problems.

[0143] The method described in this specification involves each system recording its corresponding transaction message, as well as the business scenario and characteristics of the next system, during the data upload process for subsequent backtracking. After the end system generates an upload file based on its corresponding transaction message, the upload file is uploaded to the data warehouse to generate a monitoring table. When performing data tracing, the records in the monitoring table are used as a basis to gradually trace back to the end system, and then the end system iteratively determines and traces back to the source system, thus connecting the entire link corresponding to the data to be traced. Problems are checked based on the transaction messages corresponding to all nodes in the link.

[0144] In the embodiments of this specification, the process of each system generating its own corresponding transaction message, starting from the source system, and sending the transaction message to the next system with which it has a business transaction, until the end system of the business transaction, further includes:

[0145] S1: The source system is used as the sending system. The sending system generates the transaction message corresponding to the sending system based on its own business scenario, business characteristics, source system, business sender and business data.

[0146] S2: The sending system sends its corresponding transaction message to the receiving system with which it has a business transaction;

[0147] S3: The receiving system generates a transaction message corresponding to the sending system based on the transaction message corresponding to the sending system;

[0148] S4: When the receiving system has subsequent business transactions, the receiving system is used as the new sending system. The new sending system sends its corresponding transaction message to the new receiving system of the subsequent business transaction. Steps S3-S4 are repeated until the new receiving system becomes the end system of the business transaction.

[0149] The transaction message corresponding to the sending system includes the sending system's own business scenario, business characteristics, source system, business sender, and business data. The business scenario, business characteristics, and source system have been omitted above. The business sender needs to be distinguished from the source system. Taking System A—System B—System C as an example, for System B, System A is both the source system and the business sender; for System C, System A is the source system, and System B is the business sender. Business data refers to the specific business content. For example, if Li transfers 10,000 yuan to Zhang, System A's business data records that the transferor is Li, the recipient is Zhang, the transfer amount is 10,000 yuan, and the transfer initiation date is [Date and Time]. The sending system sends the transaction message to the receiving system with which it has a business transaction. The receiving system then further generates its own transaction message based on the transaction message from the sending system. If there are subsequent business transactions in the receiving system, the receiving system will act as a new sending system and send its corresponding transaction message to the new receiving system. This process will continue until the new receiving system becomes the end system of the business transaction.

[0150] In the embodiments described in this specification, reference is made to Figure 2 The sending system, based on the business scenario, business characteristics, source system, business sender, and business data, generates the corresponding transaction message, which further includes:

[0151] S201: The sending system generates a scenario code based on the business scenario, a business identifier number based on the business characteristics, a source code based on the source system, and a sending code based on the business sender.

[0152] S202: Integrate the scenario code, business identifier, source code, sender code, and business data to generate the transaction message corresponding to the sender system.

[0153] When each system records the business scenario and business characteristics corresponding to the next system with which it has a business transaction, it specifically records the scenario code and business identifier number corresponding to the next system.

[0154] Specifically, refer to Figure 3 The step of generating a business identifier based on business characteristics further includes:

[0155] S301: The server where the sending system is located has a computing system installed;

[0156] S302: The computing system performs calculations on the source code corresponding to the business source party, the server code where the sending system is located, and the current time representation value of the business transaction according to the computing rules to obtain the computing value;

[0157] S303: The computing system randomly integrates the source code, the server code of the sending system, the current time representation value of the business transaction, and the computing value to generate a business identifier.

[0158] A separate computing system is set up on the server to generate the service identifier. Since the service identifier uniquely identifies a specific service, its uniqueness must be ensured. In the embodiments of this specification, the service first needs to perform calculations on the source code corresponding to the service source, the server code where the sending system is located, and the current time representation value of the service transaction to obtain the calculated value. Then, the source code, the server code where the sending system is located, the current time representation value of the service transaction, and the calculated value are randomly integrated to generate the service identifier.

[0159] The current time representation value can be obtained by taking the year, month, day, hour, minute, and second of the current time of the business transaction. For example, if the time when the transfer request is received is 18:05 on May 1, 2023, the corresponding current time representation value is: 202305011805.

[0160] In the embodiments described in this specification, reference is made to Figure 4 The computing system performs calculations on the source code corresponding to the business source, the server code where the sending system is located, and the current time representation value of the business transaction according to the calculation rules, and the calculated value further includes:

[0161] S401: The arithmetic system selects the arithmetic rule pointed to by the first pointer and the arithmetic rule pointed to by the second pointer from the four arithmetic rules of addition, subtraction, multiplication and division;

[0162] S402: Perform operations on the source code and the server code according to the operation rules pointed to by the first pointer to obtain the first operation result;

[0163] S403: Perform calculations on the first calculation result and the current time representation value according to the arithmetic rules pointed to by the second pointer to obtain the second calculation result;

[0164] S404: Take the value of the set number of bits in the second operation result as the operation value;

[0165] S405: The arithmetic system shifts the first pointer and / or the second pointer.

[0166] Specifically, when performing calculations to obtain the calculated value, four arithmetic rules are set up: addition, subtraction, multiplication, and division. These four arithmetic rules are stored in four addresses, which can be stored using arrays. For example, a[0], a[1], a[2], and a[3] store addition, subtraction, multiplication, and division respectively. Because the calculation involves three values: the source code corresponding to the business source, the server code of the sending system, and the current time representation value of the business transaction, the first pointer and the second pointer can each point to any one of the arithmetic rules. The source code and server code are calculated using the arithmetic rule pointed to by the first pointer to obtain the first calculation result. The first calculation result and the current time representation value are calculated using the arithmetic rule pointed to by the second pointer to obtain the second calculation result.

[0167] Since the calculated second result may be negative or decimal, only the value of a set number of digits is taken as the operation value. For example, take 6 digits as the operation value and do not take the negative sign. If the second result is less than 6 digits, a random number can be added before, after or in the middle of it. For example, if the calculated second result is -1213, then take 1213 and add a digit 0 before and after it to get the operation value 012130.

[0168] After the operation is completed, the first pointer and / or the second pointer need to be shifted.

[0169] Specifically, refer to Figure 5 The operation system further includes shifting the first pointer and / or the second pointer by:

[0170] S501: If the first pointer and the second pointer point to the same arithmetic operation, then the first pointer or the second pointer is shifted;

[0171] S502: If the first pointer and the second pointer point to different arithmetic rules, then the first pointer and / or the second pointer shall be shifted.

[0172] The specific shift direction and number of bits can be set according to requirements. For example, you can set each shift to move one bit to the right, and if the pointer is at the last bit, then shift to the first bit.

[0173] In the embodiments described in this specification, reference is made to Figure 6 The computational system randomly integrates the source code, the server code of the sending system, the current time representation value of the business transaction, and the computational value to generate a business identifier, which further includes:

[0174] S601: At least one of the following is randomly selected from the source code, the server code of the sending system, and the current time representation value of the business transaction;

[0175] S602: Combine the selected entity with the calculated value in sequence to generate a business identifier number.

[0176] After the calculated value is obtained, at least one of the following is randomly selected from the source code, the server code of the sending system, and the current time representation value of the business transaction and combined with the calculated value in sequence to generate a business identifier. The specific combination method can be addition, sequential concatenation, or other combination methods.

[0177] In the embodiments described in this specification, reference is made to Figure 7 The process of generating a transaction message corresponding to the receiving system based on the transaction message corresponding to the sending system further includes:

[0178] S701: The receiving system obtains the source system and business characteristics corresponding to the sending system based on the transaction message corresponding to the sending system;

[0179] S702: The source system corresponding to the sending system is taken as the source system corresponding to the receiving system;

[0180] S703: Use the service characteristics corresponding to the sending system as the service characteristics corresponding to the receiving system;

[0181] S704: Designate the sending system as the service sender corresponding to the receiving system;

[0182] S705: The receiving system generates a transaction message corresponding to its own business scenario, business characteristics, source system, business sender, and business data.

[0183] For example, after receiving a transaction message from System A, System B can directly obtain the source code and business identifier from the message as its own transaction message. Then, based on System B's business scenario, it uses the corresponding code from System A as the sender code, and combines this with its own business data to generate a corresponding transaction message for System B. System B's business data could include: the transferor is Mr. Li, the recipient is Mr. Zhang, the transfer amount is 10,000 yuan, the transfer initiation date is [Date], the transaction verification result is successful, the transaction verifier is Mr. / Ms. [Name], and the transaction verification time is [Time].

[0184] In the embodiments described in this specification, each record in the monitoring table includes a business scenario code, a business identifier, a source code, and business data. During the tracing process, if problematic data is found in the business data, the business scenario code and business identifier corresponding to that business data are obtained to determine the corresponding file to be uploaded to the source layer.

[0185] The process of the terminal system generating the upload file based on its corresponding transaction message further includes: the terminal system generating the upload file based on the business scenario code, business identifier, source code, and business data in its corresponding transaction message.

[0186] Reference Figure 8 The step of determining the end system corresponding to the data to be traced, and the transaction message corresponding to the end system, based on the uploaded file of the data to be traced, further includes:

[0187] S801: Determine the business scenario code and business identifier number corresponding to the data to be traced based on the uploaded file of the data to be traced;

[0188] S802: Based on the business scenario code and business identifier, determine the end system corresponding to the data to be traced, and the transaction message corresponding to the end system.

[0189] Although multiple different systems send files to the source layer, the business scenario code and business identifier corresponding to the data to be traced can be determined. Therefore, a unique end system and its transaction message can be identified. The business scenario code can be used to locate the end system, and the business identifier can be used to locate the transaction message in the end system.

[0190] In the embodiments of this specification, determining the previous system of the current system based on the transaction message corresponding to the current system further includes: determining the previous system of the current system based on the sender code in the transaction message corresponding to the current system, wherein the code of the previous system is the sender code.

[0191] Reference Figure 9 The step of matching the current system's business scenario and business characteristics recorded in the previous system with the transaction message corresponding to the current system to obtain the transaction message corresponding to the previous system further includes:

[0192] S901: Based on the transaction message corresponding to the current system, determine the actual business scenario code and business identifier number corresponding to the current system;

[0193] S902: Match the actual business scenario code and business identifier with the business scenario code and business identifier recorded in the previous system to obtain the transaction message of the previous system corresponding to the matching business scenario code and business identifier.

[0194] Since the previous system of the current system has been identified through the sender code, the next step is to determine which specific transaction message from the previous system it is. This is because the previous system may have sent various transaction messages to the current system. Therefore, based on the transaction message corresponding to the current system, the actual (i.e., the real) business scenario code and business identifier number corresponding to the current system are determined. The actual business scenario code and business identifier number are then matched with all the business scenario codes and business identifier numbers recorded in the previous system. The transaction message from the previous system corresponding to the matching business scenario code and business identifier number is the transaction message corresponding to the data to be traced.

[0195] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the acquisition, storage, use, and processing of data in the technical solutions described in the embodiments of this application all comply with the relevant provisions of national laws and regulations.

[0196] Based on the aforementioned problem data tracing method, this specification also provides a corresponding problem data tracing device. The device may include a system (including a distributed system), software (application), module, component, server, client, etc., using the method described in this specification, combined with necessary hardware implementation. Based on the same innovative concept, the devices in one or more embodiments provided in this specification are as described in the following embodiments. Since the implementation schemes and methods for solving problems are similar, the implementation of specific devices in this specification can refer to the implementation of the aforementioned method, and repeated details will not be elaborated further. As used below, the terms "unit" or "module" can refer to a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0197] Specifically, Figure 10 This is a schematic diagram of the module structure of one embodiment of a problem data tracing device provided in this specification. (Refer to...) Figure 10 As shown in the embodiments of this specification, a problem data tracing device includes: a transaction message generation module 100, an uploading module 200, a regulatory table generation module 300, an uploading file determination module 400, an end system determination module 500, a current system determination module 600, a judgment module 700, and an acquisition module 800.

[0198] The transaction message generation module 100 is used to generate its own corresponding transaction message starting from the source system when business transactions are conducted between different systems, and send the transaction message to the next system with which it has a business transaction, until the end system of the business transaction; wherein each system records its own corresponding transaction message, as well as the business scenario and business characteristics corresponding to the next system with which it has a business transaction.

[0199] The upload module 200 is used by the terminal system to generate an upload file based on its corresponding transaction message and upload the upload file to the data warehouse's source layer.

[0200] The regulatory table generation module 300 is used by the data warehouse to generate a regulatory table based on the uploaded files received by the source layer.

[0201] The upload file determination module 400 is used to determine the upload file in the source layer corresponding to the data to be traced, based on the records in the supervision table, when it is necessary to trace the source of the data to be traced.

[0202] The end system determination module 500 is used to determine the end system corresponding to the data to be traced and the transaction message corresponding to the end system based on the uploaded file of the data to be traced.

[0203] The current system determination module 600 is used to identify the terminal system as the current system;

[0204] The judgment module 700 is used to determine whether the current system is the source system of the data to be traced.

[0205] If so, the current system will be used as the source node of the data to be traced.

[0206] If not, then:

[0207] The current system is used as a link process node for the data to be traced.

[0208] Based on the transaction message corresponding to the current system, determine the previous system of the current system;

[0209] Based on the business scenario and business characteristics of the current system recorded in the previous system, match them with the transaction message corresponding to the current system to obtain the transaction message corresponding to the previous system;

[0210] Using the previous system as the current system, the above judgment steps are executed repeatedly.

[0211] The acquisition module 800 is used to sequentially acquire the transaction messages corresponding to all nodes on the link of the data to be traced in order to check for problems.

[0212] Reference Figure 11As shown, based on the aforementioned problem data tracing method, one embodiment of this specification also provides a computer device 1102, wherein the above-described method operates on the computer device 1102. The computer device 1102 may include one or more processors 1104, such as one or more central processing units (CPUs) or graphics processing units (GPUs), each processing unit implementing one or more hardware threads. The computer device 1102 may also include any memory 1106 for storing any kind of information such as code, settings, data, etc. In one specific embodiment, a computer program on the memory 1106 and executable on the processor 1104, when run by the processor 1104, can execute instructions according to the above-described method. Non-limitingly, for example, the memory 1106 may include any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, etc. More generally, any memory can use any technology to store information. Further, any memory can provide volatile or non-volatile retention of information. Further, any memory can represent a fixed or removable component of the computer device 1102. In one scenario, when processor 1104 executes associated instructions stored in any memory or combination of memories, computer device 1102 can perform any operation of the associated instructions. Computer device 1102 also includes one or more drive mechanisms 1108 for interacting with any memory, such as hard disk drive mechanisms, optical disk drive mechanisms, etc.

[0213] Computer device 1102 may further include an input / output module 1110 (I / O) for receiving various inputs (via input device 1112) and providing various outputs (via output device 1114). A specific output mechanism may include a presentation device 1116 and an associated graphical user interface 1118 (GUI). In other embodiments, the input / output module 1110 (I / O), input device 1112, and output device 1114 may be omitted, and the device may function solely as a computer device within a network. Computer device 1102 may also include one or more network interfaces 1120 for exchanging data with other devices via one or more communication links 1122. One or more communication buses 1124 couple the components described above together.

[0214] Communication link 1122 can be implemented in any way, such as via a local area network, a wide area network (e.g., the Internet), a point-to-point connection, or any combination thereof. Communication link 1122 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.

[0215] Corresponding to Figures 1-9In addition to the methods described above, embodiments of this specification also provide a computer-readable storage medium storing a computer program that, when executed by a processor, performs the steps of the methods described above.

[0216] This specification also provides computer-readable instructions, wherein when a processor executes the instructions, the program therein causes the processor to perform the following... Figures 1 to 9 The method shown.

[0217] This specification also provides a computer program product, wherein when the computer program product is run by the processor of a computer device, it executes as follows: Figures 1 to 9 The method shown.

[0218] It should be understood that in the various embodiments of this specification, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this specification.

[0219] It should also be understood that, in the embodiments of this specification, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the embodiments of this specification, the character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0220] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this specification can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of each example have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of the embodiments in this specification.

[0221] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0222] In the several embodiments provided in this specification, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be indirect couplings or communication connections through some interfaces, devices, or units, or they may be electrical, mechanical, or other forms of connection.

[0223] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments described in this specification, depending on actual needs.

[0224] Furthermore, the functional units in the various embodiments of this specification can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0225] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this specification, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this specification. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0226] This specification uses specific embodiments to illustrate the principles and implementation methods of the embodiments. The above description of the embodiments is only for the purpose of helping to understand the methods and core ideas of the embodiments in this specification. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the embodiments in this specification. Therefore, the content of this specification should not be construed as a limitation on the embodiments in this specification.

Claims

1. A method for tracing the source of problematic data, characterized in that, include: When business transactions occur between different systems, starting with the source system, each system generates its own corresponding transaction message and sends it to the next system with which it has a business transaction, until the end system of the business transaction. The source system is considered the sending system. The sending system integrates a scenario code generated based on its own business scenario, a business identifier generated based on business characteristics, a source code generated by the source system, a sender code generated by the business sender, and business data to generate the transaction message corresponding to the sending system. The business identifier is determined by a computing system on the server where the sending system resides, according to computing rules, based on the source code corresponding to the business source and the server where the sending system resides. After calculating the calculated value by performing operations on the encoding and the current time representation value of the business transaction, the calculated value is randomly integrated from the source encoding, the server encoding of the sending system, the current time representation value of the business transaction, and the calculated value. The calculation rules are as follows: the calculation system selects the operation rule pointed to by the first pointer and the operation rule pointed to by the second pointer from the four arithmetic operations of addition, subtraction, multiplication, and division; performs operations on the source encoding and the server encoding according to the operation rule pointed to by the first pointer to obtain a first calculation result; performs operations on the first calculation result and the current time representation value according to the operation rule pointed to by the second pointer to obtain a second calculation result; and takes the value of a predetermined number of bits in the second calculation result as the calculated value. Each system records its own corresponding transaction messages, as well as the business scenarios and business characteristics of the next system with which it has business transactions. The terminal system generates an upload file based on its corresponding transaction message and uploads the upload file to the data warehouse's source layer. The data warehouse generates a monitoring table based on the uploaded files received by the source layer; When it is necessary to trace the source of the data to be traced, the uploaded file in the corresponding posting layer is determined based on the records in the regulatory table. Based on the uploaded file of the data to be traced, the end system corresponding to the data to be traced and the transaction message corresponding to the end system are determined. The uploaded file includes at least the business scenario code and business identifier in the transaction message corresponding to itself. The business scenario code is used to locate the end system, and the business identifier is used to locate the transaction message in the end system. The terminal system is used as the current system; Determine whether the current system is the source system of the data to be traced; If so, the current system will be used as the source node of the data to be traced. If not, then: The current system is used as a link process node for the data to be traced. Based on the transaction message corresponding to the current system, determine the previous system of the current system; Based on the business scenario code and business identifier number of the current system recorded in the previous system, match them with the transaction message of the current system to obtain the transaction message of the previous system; Using the previous system as the current system, the above judgment steps are executed repeatedly. Sequentially retrieve the transaction messages corresponding to all nodes on the data to be traced in the chain to check for problems.

2. The problem data tracing method according to claim 1, characterized in that, Starting with the source system, each system generates its own corresponding transaction message and sends the transaction message to the next system with which it has a business transaction, until the end system of the business transaction further includes: S1: The sending system sends its corresponding transaction message to the receiving system with which it has a business transaction; S2: The receiving system generates a transaction message corresponding to the sending system based on the transaction message corresponding to the sending system; S3: When the receiving system has subsequent business transactions, the receiving system is used as the new sending system. The new sending system sends its corresponding transaction message to the new receiving system of the subsequent business transaction. Steps S2-S3 are repeated until the new receiving system becomes the end system of the business transaction.

3. The problem data tracing method according to claim 1, characterized in that, The operation system further includes shifting the first pointer and / or the second pointer by: If the first pointer and the second pointer point to the same arithmetic operation, then the first pointer or the second pointer is shifted; If the first pointer and the second pointer point to different arithmetic rules, then the first pointer and / or the second pointer will be shifted.

4. The problem data tracing method according to claim 2, characterized in that, The process of generating a transaction message corresponding to the receiving system based on the transaction message corresponding to the sending system further includes: The receiving system obtains the source system and business characteristics corresponding to the sending system based on the transaction message corresponding to the sending system; The source system corresponding to the sending system is taken as the source system corresponding to the receiving system; The service characteristics corresponding to the sending system are used as the service characteristics corresponding to the receiving system. The sending system is designated as the service sender corresponding to the receiving system. The receiving system generates a transaction message corresponding to its own business scenario, business characteristics, source system, business sender, and business data.

5. The problem data tracing method according to claim 1, characterized in that, Each record in the regulatory table includes a business scenario code, a business identifier, a source code, and business data.

6. The problem data tracing method according to claim 1, characterized in that, The terminal system generates the upload file based on its corresponding transaction message, which further includes: The terminal system generates the upload file based on the business scenario code, business identifier, source code, and business data in its corresponding transaction message.

7. The problem data tracing method according to claim 6, characterized in that, The step of determining the end system corresponding to the data to be traced, and the transaction message corresponding to the end system, based on the uploaded file of the data to be traced, further includes: Based on the uploaded file of the data to be traced, determine the business scenario code and business identifier corresponding to the data to be traced; Based on the business scenario code and business identifier, determine the end system corresponding to the data to be traced, and the transaction message corresponding to the end system.

8. The problem data tracing method according to claim 1, characterized in that, The step of determining the previous system of the current system based on the transaction message corresponding to the current system further includes: Based on the sender code in the transaction message corresponding to the current system, determine the previous system of the current system, where the code of the previous system is the sender code.

9. The problem data tracing method according to claim 1, characterized in that, The step of matching the current system's business scenario code and business identifier recorded in the previous system with the transaction message corresponding to the current system to obtain the transaction message corresponding to the previous system further includes: Based on the transaction message corresponding to the current system, determine the actual business scenario code and business identifier number corresponding to the current system; The actual business scenario code and business identifier are matched with the business scenario code and business identifier recorded in the previous system to obtain the transaction message of the previous system corresponding to the matching business scenario code and business identifier.

10. A problem data tracing device, characterized in that, The device includes: The transaction message generation module is used to initiate a transaction transaction between different systems. Starting with the source system, each system generates its own corresponding transaction message and sends it to the next system with which it has a business transaction, continuing until the end system of the transaction. The source system acts as the sending system. The sending system integrates a scenario code generated based on its own business scenario, a business identifier generated based on business characteristics, a source code generated by the source system, a sender code generated by the business sender, and business data to generate the transaction message corresponding to the sending system. The business identifier is determined by a computing system on the server where the sending system resides, which applies a calculation rule to the source code corresponding to the business source, the server code where the sending system resides, and the current time representation value of the business transaction. After obtaining the calculated value, the source code, the server code of the sending system, the current time representation value of the business transaction, and the calculated value are randomly integrated to generate the value. The calculation rules are as follows: the calculation system selects the calculation rule pointed to by the first pointer and the calculation rule pointed to by the second pointer from the four arithmetic rules of addition, subtraction, multiplication, and division; the source code and the server code are calculated according to the calculation rule pointed to by the first pointer to obtain a first calculation result; the first calculation result and the current time representation value are calculated according to the calculation rule pointed to by the second pointer to obtain a second calculation result; the value of a set number of bits in the second calculation result is taken as the calculated value. Each system records its own corresponding transaction message, as well as the business scenario and business characteristics corresponding to the next system with which it has a business transaction. The upload module is used by the terminal system to generate an upload file based on its corresponding transaction message and upload the upload file to the data warehouse's source layer. The regulatory table generation module is used by the data warehouse to generate regulatory tables based on the uploaded files received by the source layer. The upload file determination module is used to determine the upload file in the source layer corresponding to the data to be traced, based on the records in the supervision table, when it is necessary to trace the source of the data to be traced. The end-system determination module is used to determine the end-system corresponding to the data to be traced and the transaction message corresponding to the end-system based on the uploaded file of the data to be traced. The uploaded file includes at least the business scenario code and business identifier in the transaction message corresponding to itself. The business scenario code is used to locate the end-system, and the business identifier is used to locate the transaction message in the end-system. The current system determination module is used to identify the terminal system as the current system; The judgment module is used to determine whether the current system is the source system of the data to be traced. If so, the current system will be used as the source node of the data to be traced. If not, then: The current system is used as a link process node for the data to be traced. Based on the transaction message corresponding to the current system, determine the previous system of the current system; Based on the business scenario code and business identifier number of the current system recorded in the previous system, match them with the transaction message of the current system to obtain the transaction message of the previous system; Using the previous system as the current system, the above judgment steps are executed repeatedly. The acquisition module is used to sequentially acquire the transaction messages corresponding to all nodes on the data to be traced in order to check for problems.

11. A computer device comprising a memory, a processor, and a computer program stored in the memory, characterized in that, When the computer program is run by the processor, it executes the instructions of the method according to any one of claims 1-9.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is run by the processor of the computer device, it executes the instructions of the method according to any one of claims 1-9.

13. A computer program product, characterized in that, When the computer program product is run by the processor of a computer device, it executes the instructions of the method according to any one of claims 1-9.

Images