An inter-system data exchange log tracing system and method

Abstract

This invention provides a system and method for tracing data exchange logs between systems, relating to the field of data processing technology. The system includes: a log acquisition unit for acquiring target data exchange logs; a content parsing unit for parsing the target data exchange logs to obtain target tracing index dimensions and target index content; a request retrieval unit for retrieving multiple chain tracing requests corresponding to each target tracing index dimension; a matching analysis unit for obtaining tracing matching results based on the chain tracing requests; and a storage control unit for controlling the writing of data exchange logs to a storage repository based on the tracing matching results, and continuously monitoring unmatched index content until the end of the continuous monitoring period to complete log tracing. The tracing system and method provided by this invention can ensure the integrity and traceability of each associated data log when searching based on each chain tracing request.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to an inter-system data exchange log tracing system and method. Background Technology

[0002] Currently, the amount of logs sent between various systems is large. Each business system can store the massive amount of transmitted data independently. Alternatively, the data exchange center can be used to store data logs between various systems. This allows the data exchange center to provide relevant data retrieval services, monitoring linkage, and alarm functions based on the status and data content of interactions between upstream and downstream systems.

[0003] In the process of storing data exchange logs between systems through a data exchange center, each system typically stores the data directly in the data exchange center's repository after acquiring the data, without considering whether various types of data can form a reasonable and complete retrieval chain. As a result, when retrieving and querying related log data between systems based on data retrieval requests, a large amount of invalid data cannot be retrieved and used by the retrieval request. Moreover, the presence of invalid data will also create unnecessary caching load on the storage system, and there is no good way to accurately remove such invalid data from the repository. Summary of the Invention

[0004] This invention provides a system and method for tracing logs of data exchange between systems. It addresses the problem that after each system acquires data, it directly stores the data in the repository of the data exchange center without considering whether various types of data can form a reasonable and complete retrieval chain. This results in a large amount of invalid data that cannot be retrieved and used when searching for related log data between systems based on data retrieval requests. Furthermore, the presence of invalid data creates unnecessary caching load on the storage system, and there is no good way to accurately remove such invalid data from the repository.

[0005] To achieve the above and other related objectives, this invention provides an inter-system data exchange log tracing system, comprising: a log acquisition unit for acquiring target data exchange logs during each inter-system data exchange process; a content parsing unit for parsing the target data exchange logs to obtain corresponding target tracing index dimensions and target index content corresponding to each target tracing index dimension; a request retrieval unit for retrieving multiple chain tracing requests based on each target tracing index dimension; a matching analysis unit for performing tracing matching analysis on the corresponding target index content in a repository based on each chain tracing request to obtain tracing matching results; and a storage control unit for controlling the writing of data exchange logs to the repository based on the tracing matching results, and continuously monitoring unmatched index content according to the corresponding tracing index dimensions until the continuous monitoring period ends to complete log tracing.

[0006] In one embodiment of the present invention, the content parsing unit includes: a content conversion subunit, used to sequentially convert the target data exchange log into different traceability index dimensions through a large language model to obtain converted content; a format detection subunit, used to perform content format detection on the converted content to obtain a detection result; and an index output subunit, used to, when the detection result indicates that the content format of the converted content is normal, use the traceability index dimension corresponding to the converted content as the target traceability index dimension and the converted content as the target index content; and when the detection result indicates that the content format of the converted content is abnormal, continue to perform content conversion on the data exchange log for the next traceability index dimension to obtain all target index content corresponding to the data exchange log.

[0007] In one embodiment of the present invention, the format detection subunit includes: a format retrieval module, used to retrieve the baseline content format of the traceability index dimension corresponding to the converted content; a format comparison module, used to compare the similarity between the baseline content format and the content format of the converted content to obtain a format similarity; and a result output module, used to determine that the content format of the converted content is normal when the format similarity is greater than a first similarity, and that the content format of the converted content is abnormal when the format similarity is less than the first similarity.

[0008] In one embodiment of the present invention, the matching analysis unit includes: a dimension extraction subunit, used to extract other corresponding traceability index dimensions according to each chain traceability request; a chain construction subunit, used to perform corresponding historical data exchange log queries on the repository according to other traceability index dimensions to obtain corresponding historical index content, so as to form a corresponding data traceability chain; a dimension generation subunit, used to generate a comprehensive constraint dimension for the target index content according to the data traceability chain and the traceability constraint dimension; and a content judgment subunit, used to determine whether the target index content is within the comprehensive constraint dimension; if yes, the traceability matching result is that the target index content matches the data traceability chain corresponding to the historical index content; if no, the traceability matching result is that the target index content does not match the data traceability chain corresponding to the historical index content.

[0009] In one embodiment of the present invention, the matching analysis unit further includes: a dimension combination subunit, used to freely combine other traceability index dimensions corresponding to historical index content in the data traceability chain to obtain an index dimension combination; and a traceability restriction output subunit, used to search the combination library according to the index dimension combination to obtain a preset index dimension combination consistent with the combination library, and to obtain the corresponding traceability restriction dimension according to the preset index dimension combination, wherein the combination library includes traceability restriction dimensions corresponding to multiple preset index dimension combinations.

[0010] In one embodiment of the present invention, the dimension generation subunit includes: a constraint analysis module, used to perform constraint analysis on the data tracing chain to obtain the chain constraint dimension; and a comprehensive output module, used to generate a comprehensive constraint dimension for the target index content based on the chain constraint dimension and the tracing constraint dimension.

[0011] In one embodiment of the present invention, the restriction analysis module includes: an information extraction submodule, used to extract dimensional information from the corresponding historical index content in the data tracing chain to obtain dimensional types and dimensional data corresponding to each dimensional type, wherein the dimensional types include time dimension, participating entity dimension, business identifier dimension, data theme dimension, and data flow path dimension; a boundary determination submodule, used to determine the dimensional boundary corresponding to the same dimensional type based on the dimensional data corresponding to the same dimensional type; and a chain restriction output submodule, used to obtain the chain restriction dimensions corresponding to different dimensional types based on the dimensional types and dimensional boundaries.

[0012] In one embodiment of the present invention, the storage control unit includes: a first control subunit, configured to write the target data exchange log to the storage repository when the traceability matching result indicates that there is a data traceability chain matching between the target index content and the historical index content in the storage repository; and a second control subunit, configured to treat the target index content that does not match the data traceability chain corresponding to the historical index content as unmatched index content, perform continuous monitoring analysis on the unmatched index content according to the corresponding traceability index dimension, and obtain analysis results; and based on the analysis results, perform continuous monitoring on the unmatched index content according to the corresponding traceability index dimension until the continuous monitoring period ends to complete log traceability.

[0013] In one embodiment of the present invention, the second control subunit performs continuous monitoring analysis on the unmatched index content according to the corresponding traceability index dimension to obtain analysis results; and continuously monitors the unmatched index content according to the corresponding traceability index dimension according to the analysis results until the continuous monitoring period ends to complete log tracing. This process includes: a period detection module for detecting the data collection period of the unmatched index content to determine the corresponding data collection stage based on the data collection period; a sequence comparison module for comparing the data collection stage with the baseline collection stage corresponding to the corresponding traceability index dimension; and a deletion control module for stopping continuous monitoring of the unmatched index content according to the corresponding traceability index dimension and deleting the unmatched index content when the data collection stage is in or after the baseline collection stage. The system includes: a data traceability chain deletion module for matching index content; a periodic evaluation module, used to assess the continuous monitoring period based on the urgency of the data traceability chain requirement for unmatched index content and the stage span between the data collection stage and the baseline collection stage when the data collection stage precedes the baseline collection stage; and a monitoring control module, used to stop continuous monitoring of the corresponding traceability index dimension for unmatched index content and delete the data traceability chain corresponding to the unmatched index content when there are no changes to the unmatched index content within the continuous monitoring period; and to continue assessing the continuous monitoring period based on the urgency of the data traceability chain requirement for the updated unmatched index content and the stage span between the data collection stage and the baseline collection stage when the unmatched index content is updated, using the periodic evaluation module.

[0014] To achieve the above and other related objectives, the present invention also provides a method for tracing data exchange logs between systems, comprising: acquiring target data exchange logs during each inter-system data exchange process through a log acquisition unit; parsing the target data exchange logs through a content parsing unit to obtain the corresponding target tracing index dimensions and the target index content corresponding to each target tracing index dimension; retrieving multiple chain tracing requests according to each target tracing index dimension through a request retrieval unit; performing tracing matching analysis on the corresponding target index content in a storage repository according to each chain tracing request, and obtaining tracing matching results; and controlling the writing of data exchange logs to the storage repository according to the tracing matching results through a storage control unit, and continuously monitoring the unmatched index content according to the corresponding tracing index dimensions until the continuous monitoring period ends to complete log tracing.

[0015] The beneficial effects of this invention are as follows: This invention proposes an inter-system data exchange log tracing system and method. By acquiring the target data exchange log during each inter-system data exchange process, and then parsing the content of the target data exchange log, multiple target tracing index dimensions can be derived from the target data exchange log. Based on these target tracing index dimensions, the corresponding target index content in the target data exchange log can be determined. For each target tracing index dimension, the corresponding chain tracing request is found. For a chain tracing request, there may be multiple chain tracing requests simultaneously containing the same tracing index dimension; therefore, for a given target tracing index dimension, multiple corresponding chain tracing requests can be determined. After determining the chain tracing requests, further tracing matching analysis of the target index content in the repository storing all historical data exchange logs can be performed using the chain tracing requests. This allows determination of whether the current target index content has a corresponding matching content in the repository. Finally, based on the tracing matching results, the target data exchange log corresponding to the matched target index content is stored in the repository. Additionally, if the target index content does not match, it is possible that the target index content corresponding to the current target data exchange log is not the content required to form the data traceability chain. Therefore, based on the data collection stage of the target data exchange log, it can be further determined whether to wait for the collection of the corresponding data log or to directly delete and clean up the relevant target data exchange log. This reduces the storage of log content that does not have inter-system correlation, thereby relieving the cache pressure on the repository, ensuring the integrity and traceability of each related data log when searching based on each chain traceability request, and improving the effectiveness of log content storage, data security, and compliance. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0017] In the attached diagram: Figure 1 This is a structural block diagram of an inter-system data exchange log tracing system provided in an embodiment of the present invention; Figure 2 The diagram shows a flowchart of a system data exchange log tracing method provided in an embodiment of the present invention.

[0018] The attached figures are labeled as follows: Log acquisition unit 111; content parsing unit 112; request retrieval unit 113; matching analysis unit 114; storage control unit 115. Detailed Implementation

[0019] The following specific examples illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments. Various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.

[0020] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. The drawings only show the components related to the present invention and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0021] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the invention. However, it will be apparent to those skilled in the art that embodiments of the invention may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the invention.

[0022] Please see Figure 1This invention provides an inter-system data exchange log tracing system, comprising: a log acquisition unit 111, used to acquire target data exchange logs during each inter-system data exchange process; a content parsing unit 112, used to parse the target data exchange logs to obtain corresponding target tracing index dimensions and target index content corresponding to each target tracing index dimension; a request retrieval unit 113, used to retrieve multiple chain tracing requests corresponding to each target tracing index dimension; a matching analysis unit 114, used to perform tracing matching analysis of the corresponding data tracing chain on the corresponding target index content in a repository according to each chain tracing request, and obtain tracing matching results; and a storage control unit 115, used to control the writing of data exchange logs to the repository according to the tracing matching results, and to continuously monitor the unmatched index content according to the corresponding tracing index dimensions until the continuous monitoring period ends to complete log tracing.

[0023] As can be seen from the above, when data is exchanged between systems, the data exchange logs can be shared with the inter-system data exchange log tracing system of this invention to achieve further tracing of the log data. Specifically, the inter-system data exchange log tracing system uses a log acquisition unit 111 to acquire the target data exchange logs during each inter-system data exchange process. Then, the content parsing unit 112 first parses the target data exchange logs to derive multiple target tracing index dimensions. Based on these target tracing index dimensions, the corresponding target index content in the target data exchange logs is determined. For example, when a time attribute is detected in the target data exchange log, the time dimension is taken as a target data exchange log item, and the timestamp corresponding to the time attribute in the target data exchange log is taken as the target index content of the time dimension. After determining all target tracing index dimensions and target index content of the target data exchange logs, the request retrieval unit 113 can find the corresponding chain tracing request based on each target tracing index dimension. For chain tracing requests, there may be multiple chain tracing requests simultaneously containing the same tracing index dimension. Therefore, for a certain target tracing index dimension, multiple corresponding chain tracing requests can be identified. After identifying the chain tracing requests, the matching analysis unit 114 can further perform tracing matching analysis on the target index content in the repository storing all historical data exchange logs, based on the chain tracing requests. This allows it to determine whether the current target index content has a corresponding matching content in the repository. Finally, the storage control unit 115, based on the tracing matching results of the tracing matching analysis, controls the storage of the target data exchange log corresponding to the matched target index content into the repository. In addition, if the target index content does not match, it is possible that the target index content corresponding to the current target data exchange log is not the content required to form the data traceability chain. Therefore, based on the data collection stage of the target data exchange log, it can be further determined whether to wait for the collection of the corresponding data log or to directly delete and clean up the relevant target data exchange log to reduce the storage of log content that does not have inter-system correlation, thereby relieving the cache pressure of the repository, ensuring the traceability of each related data log, and improving the effectiveness of log content storage.

[0024] In the inter-system data exchange log tracing system of the present invention, the content parsing unit 112 may further include: a content conversion subunit, used to sequentially convert the target data exchange log for different tracing index dimensions through a large language model to obtain converted content; a format detection subunit, used to perform content format detection on the converted content to obtain a detection result; and an index output subunit, used to, when the detection result indicates that the content format of the converted content is normal, use the tracing index dimension corresponding to the converted content as the target tracing index dimension and the converted content as the target index content; and when the detection result indicates that the content format of the converted content is abnormal, continue to perform content conversion on the data exchange log for the next tracing index dimension to obtain all target index content corresponding to the data exchange log.

[0025] During the parsing of the target data exchange log, a content transformation subunit can be used to transform the content of the target data exchange log using a large language model across different traceability index dimensions, thereby obtaining the corresponding transformed content. This large language model can be trained on a large amount of log data. Subsequently, a format detection subunit can further detect and analyze the transformed content to determine whether the transformed content matches the corresponding traceability index dimension. When the traceability index dimension matches the transformed content, the traceability index dimension corresponding to the transformed content can be used as the target traceability index dimension, and the transformed content can be used as the target index content. If the traceability index dimension does not match the transformed content, such as when the transformed content is empty, the process continues to perform content transformation and matching detection on the next traceability index dimension corresponding to the data exchange log. In other words, after the format detection subunit detects the detection result of a certain transformation content, if the detection result indicates that the content format of the transformation content is normal, the index output subunit can use the trace index dimension corresponding to the transformation content as the target trace index dimension and the transformation content as the target index content. However, if the detection result indicates that the content format of the transformation content is abnormal, the index output subunit can continue to perform content transformation on the next trace index dimension of the data exchange log to obtain all target index content corresponding to the data exchange log.

[0026] In the content parsing unit 112, the format detection subunit may further include: a format retrieval module, used to retrieve the baseline content format of the traceability index dimension corresponding to the converted content; a format comparison module, used to compare the similarity between the baseline content format and the content format of the converted content to obtain a format similarity; and a result output module, used to determine that the content format of the converted content is normal when the format similarity is greater than the first similarity, and that the content format of the converted content is abnormal when the format similarity is less than the first similarity.

[0027] When performing format detection on the converted content, the base content format of the corresponding traceability index dimension can be retrieved through the format retrieval module. In the traceability system of this invention, the base content format corresponding to each traceability index dimension is pre-stored. For example, the timestamp format can be "xx (number) year xx (number) month xx (number) day xx (number) hour xx (number) minute xx (number) second," or other timestamp formats. After obtaining the base content format of the traceability index dimension, the format comparison module further compares the similarity between the base content format and the content format of the converted content to determine the format similarity between the two. For example, when the content format of the converted content is empty, the difference from the base content format is large, and the format similarity is low (below the first similarity). The result output module can then output the detection result as "converted content format is abnormal." Conversely, when the format similarity is greater than the first similarity, the detection result can be output as "converted content format is normal." This allows for accurate determination of whether the converted content matches the corresponding traceability index dimension, and reduces the omission of traceability index dimensions, which could lead to inaccurate content traceability and the accidental deletion of logs associated with each system.

[0028] In the inter-system data exchange log tracing system of the present invention, the matching analysis unit 114 may further include: a dimension extraction subunit, used to extract other corresponding tracing index dimensions according to each chain tracing request; a chain construction subunit, used to perform corresponding historical data exchange log queries on the repository according to other tracing index dimensions, obtain corresponding historical index content, and form a corresponding data tracing chain; a dimension generation subunit, used to generate a comprehensive restriction dimension for the target index content according to the data tracing chain and the tracing restriction dimension; and a content judgment subunit, used to determine whether the target index content is within the comprehensive restriction dimension; if yes, the tracing matching result is that the target index content matches the data tracing chain corresponding to the historical index content; if no, the tracing matching result is that the target index content does not match the data tracing chain corresponding to the historical index content.

[0029] During the matching and analysis of data traceability chains, the dimension extraction sub-unit can find the set of traceability index dimensions required for each chain traceability request. If all traceability index dimensions in the set can find corresponding index content, it indicates that the traceability data corresponding to the chain traceability request is complete. After determining the set of traceability index dimensions, other traceability index dimensions besides the target traceability index dimension used to find the chain traceability request can be extracted. Then, based on these other traceability index dimensions, the chain building sub-unit can retrieve the historical data exchange logs corresponding to each other traceability index dimension from the repository, thereby finding the historical index content corresponding to other traceability index dimensions and forming the corresponding data traceability chain based on the historical index content. Finally, the dimension generation sub-unit finds the comprehensive constraint dimension corresponding to the target index content based on the data traceability chain and the traceability constraint dimension corresponding to the chain traceability request. Finally, the content judgment sub-unit determines whether the target index content falls within the comprehensive constraint dimension. If it does, the traceability matching result indicates a match between the target index content and the historical index content in the data traceability chain. If it does not, the traceability matching result indicates a mismatch between the target index content and the historical index content in the data traceability chain. This method of determining the traceability matching result allows for a relatively accurate determination of whether the target index content matches the current chain traceability request. For example, the comprehensive constraint dimension could be solely the time dimension, which is derived from the historical index content corresponding to each of the other traceability index dimensions and the traceability constraint dimension itself. Of course, it could also include other dimensions, or be composed of at least one other dimension.

[0030] In the inter-system data exchange log tracing system of the present invention, the matching analysis unit 114 may further include: a dimension combination subunit, used to freely combine other tracing index dimensions corresponding to the historical index content in the data tracing chain to obtain an index dimension combination; and a tracing restriction output subunit, used to search the combination library according to the index dimension combination to obtain a preset index dimension combination consistent with the combination library, and to obtain the corresponding tracing restriction dimension according to the preset index dimension combination, wherein the combination library includes multiple tracing restriction dimensions corresponding to preset index dimension combinations.

[0031] When determining the traceability constraint dimension, the dimension combination subunit can freely combine other traceability index dimensions corresponding to the historical index content in the data traceability chain. At least one other traceability index dimension can be freely combined to generate a freely combined index dimension combination. Then, the traceability constraint output subunit uses each index dimension combination to search for a corresponding preset index dimension combination in the combination library to find a preset index dimension combination that matches the original index dimension combination. Then, using the preset index dimension combination, the corresponding traceability constraint dimension can be further found. Specifically, when searching the combination library using each index dimension combination, the first traceability constraint sub-dimension under a certain dimension can be found. Through another index dimension combination, the second traceability constraint sub-dimension under that dimension can be found, and so on, finding multiple traceability constraint sub-dimensions. Based on these multiple traceability constraint sub-dimensions, the corresponding comprehensive traceability constraint sub-dimension under that dimension is obtained. For different dimensions, multiple comprehensive traceability constraint sub-dimensions can then be used as the corresponding traceability constraint dimension.

[0032] In the matching analysis unit 114, the dimension generation subunit includes: a constraint analysis module, used to perform constraint analysis on the data tracing chain to obtain the chain constraint dimension; and a comprehensive output module, used to generate a comprehensive constraint dimension for the target index content based on the chain constraint dimension and the tracing constraint dimension.

[0033] The constraint analysis module can be used to analyze the relevant constraints in the collected data traceability chain, thereby identifying the types of dimensions and the corresponding dimension constraint values ​​(i.e., dimension boundaries) to determine the corresponding chain constraint dimensions. Then, the comprehensive output module combines the chain constraint dimensions and the traceability constraint dimensions to generate a comprehensive constraint dimension for the target index content.

[0034] Within the dimension generation subunit, the constraint analysis module includes: an information extraction submodule, used to extract dimensional information from the historical index content corresponding to each data traceability chain, obtaining the dimension types and the dimension data corresponding to each dimension type. The dimension types include time dimension, participating entity dimension, business identifier dimension, data theme dimension, and data flow path dimension; a boundary determination submodule, used to determine the dimension boundaries corresponding to the same dimension type based on the dimension data corresponding to the same dimension type; and a chain constraint output submodule, used to obtain the chain constraint dimensions corresponding to different dimension types based on the dimension types and dimension boundaries.

[0035] In determining the chain constraint dimensions, the information extraction submodule first extracts the content of each historical index, thereby extracting the dimensional types and corresponding dimensional data for each dimensional type. Then, the boundary determination submodule determines the dimensional boundaries for each dimensional type based on the dimensional data. Finally, the chain constraint output submodule outputs the chain constraint dimensions, which integrate the different dimensional types, based on the dimensional types and their corresponding boundaries. For example, the time dimension can be used to obtain time information for a certain task from different systems. This time information is then unified to determine its corresponding time dimension boundary, and the time dimension and its boundary are included as part of the chain constraint dimensions. Similarly, if the first historical index content contains a participating entity dimension (corresponding to system A), and the second historical index content also contains a participating entity dimension (corresponding to system B), then the system dimension boundary is system A and system B. Furthermore, if the system constraint dimensions in the traceability constraint dimensions are system A, system B, and system C, then the combined constraint dimension is that the system dimension corresponding to the target index content can only be system C. The business identifier dimension can be a unique business identifier shared by all historical index content throughout the entire data traceability chain, such as a project number. The data subject dimension can correspond to the unified data business type of the data traceability chain, such as inventory receipt. Both the business identifier dimension and the unified data business type can be used to restrict the dimension to which the target index content belongs. Additionally, the data flow path dimension can be used to represent the connection relationship within the data traceability chain. For example, if upstream and downstream relationships are determined based on all historical index content, and the downstream data content of a certain historical index content is the target index content, then there is a constraint dimension of upstream and downstream content connection between the historical index content and the target index content. This data flow path dimension can also be, for example, that all index content is in a parallel relationship, or of course, other relationships.

[0036] In the inter-system data exchange log tracing system of the present invention, the storage control unit 115 may further include: a first control subunit, configured to write the target data exchange log to the storage repository when the tracing matching result shows that there is a data tracing chain corresponding to the target index content and the historical index content in the storage repository; and a second control subunit, configured to treat the target index content that does not match the data tracing chain corresponding to the historical index content as unmatched index content, perform continuous monitoring analysis on the unmatched index content according to the corresponding tracing index dimension, and obtain the analysis result; and based on the analysis result, perform continuous monitoring on the unmatched index content according to the corresponding tracing index dimension until the continuous monitoring period ends to complete the log tracing.

[0037] After determining the traceability matching result, it is also necessary to determine whether to store the corresponding data exchange log in the repository based on the matching situation between the target index content and the repository. Specifically, when the traceability matching result shows that there is a data traceability chain matching between the target index content and the historical index content in the repository, the first control subunit can control the writing of the target data exchange log into the repository. In addition, the second control subunit will further monitor and continuously analyze the target index content that does not match the data traceability chain corresponding to the historical index content. That is, the target index content that does not match the data traceability chain corresponding to the historical index content is regarded as unmatched index content, and the unmatched index content is subjected to continuous monitoring and analysis of the corresponding traceability index dimension to determine whether the data collection stage of the unmatched index content corresponds to the traceability index dimension of the unmatched index content, as the analysis result. Finally, based on the analysis results, a processing strategy for unmatched index content is formulated. In other words, when the traceability index dimension corresponding to the unmatched index content does not correspond during the data collection phase, it can be determined whether to continuously monitor the unmatched index content according to the corresponding traceability index dimension until the continuous monitoring period ends to complete log traceability.

[0038] In the storage control unit 115, the second control subunit continuously monitors and analyzes the unmatched index content according to the corresponding traceability index dimension, obtaining analysis results. Based on the analysis results, it continuously monitors the unmatched index content according to the corresponding traceability index dimension until the end of the continuous monitoring period to complete log traceability. This process includes: a period detection module, used to detect the data acquisition period of the unmatched index content to determine the corresponding data acquisition stage based on the data acquisition period; a sequence comparison module, used to compare the data acquisition stage with the baseline acquisition stage corresponding to the corresponding traceability index dimension; and a deletion control module, used to stop continuously monitoring the unmatched index content according to the corresponding traceability index dimension when the data acquisition stage is in or after the baseline acquisition stage, and to delete the unmatched index content. The system includes: deletion of the data traceability chain corresponding to the indexed content; a periodic evaluation module, used to assess the continuous monitoring period based on the urgency of the data traceability chain requirement for the unmatched indexed content and the stage span between the data collection stage and the baseline collection stage when the data collection stage precedes the baseline collection stage; and a monitoring control module, used to stop continuous monitoring of the unmatched indexed content at the corresponding traceability index dimension and control the deletion of the data traceability chain corresponding to the unmatched indexed content when there are no changes to the unmatched indexed content within the continuous monitoring period; and to continue the continuous monitoring period assessment process through the periodic evaluation module based on the urgency of the data traceability chain requirement for the updated unmatched indexed content and the stage span between the data collection stage and the baseline collection stage when the unmatched indexed content is updated.

[0039] Further evaluation is needed for unmatched index content to determine whether continued monitoring of the target data exchange log is required, or whether control and cleanup of target data exchange logs without matching data traceability chains are necessary. Specifically, a periodic detection module can be used to detect the data collection period of unmatched index content, determining the corresponding data collection stage based on the time node of the data collection period. Then, a sequential comparison module compares the data collection stage with the baseline collection stage corresponding to the corresponding traceability index dimension to determine the sequential relationship between the data collection stage and the baseline collection stage. Furthermore, if the data collection stage is at or after the baseline collection stage, it indicates that the current target data exchange log is not suitable for a data traceability chain. To reduce monitoring load, continuous monitoring of the corresponding traceability index dimension for the unmatched index content can be stopped, and the deletion of the data traceability chain corresponding to the unmatched index content can be controlled based on the association and use of historical index content corresponding to the chain traceability request in other data traceability chains. In other words, when the historical index content corresponding to the chain tracing request cannot be matched in other data tracing chains, and cannot be matched in the data tracing chain corresponding to the current chain tracing request, or when there is only one chain tracing request for the unmatched index content, the data tracing chain corresponding to the unmatched index content can be deleted.

[0040] When the data acquisition phase precedes the baseline acquisition phase, further analysis and evaluation of the continuous monitoring period are needed to determine whether continued monitoring of unmatched index content and corresponding target data exchange logs is necessary. Specifically, the period evaluation module can use the phase span between the data acquisition phase and the baseline acquisition phase as one evaluation metric, and the urgency of the unmatched index content's need for the data traceability chain as another. Based on the weighted proportion of these two metrics, the remaining monitoring period can be determined, thus establishing the invalidation period for the unmatched index content. Of course, for unmatched index content corresponding to data exchange logs that have passed a specified continuous monitoring period, continuous monitoring can be performed based on that specified period. For unmatched index content corresponding to unspecified data exchange logs, the continuous monitoring period can be evaluated in the same way to ensure comprehensive data monitoring. Then, the monitoring and control module can monitor changes in unmatched index content during the continuous monitoring period. When the unmatched index content remains unchanged, the processing methods described above for the data acquisition phase at or after the baseline acquisition phase can be used to determine whether the data traceability chain corresponding to the unmatched index content needs to be deleted. Furthermore, if the unmatched index content is updated, the periodic evaluation module can assess the urgency of the updated unmatched index content's need for the data traceability chain, as well as the phase span between the data acquisition phase and the baseline acquisition phase, to determine the updated continuous monitoring period. The unmatched index content is then continuously monitored according to the updated continuous monitoring period until the updated index content at or before the baseline acquisition phase can be matched with the corresponding data traceability chain.

[0041] The log data tracing method of the present invention can effectively ensure that each chain index request can find a complete data tracing chain composed of compliant index content, thereby effectively ensuring the integrity of log data and improving data storage effect and data retrieval efficiency.

[0042] The formula for calculating the continuous monitoring period is: ; in, Indicates the continuous monitoring period. Indicates the weight of the first period. This indicates the urgency of the need for unmatched index content to follow the data tracing chain. Indicates the weight of the second period. Indicates the first cycle conversion factor. This indicates the time span between the data acquisition phase and the baseline acquisition phase. This represents the second-cycle conversion factor.

[0043] The calculation formula for the continuous monitoring period above shows that, when calculating the continuous monitoring period, the urgency of the data tracing chain can be assessed by utilizing the content of unmatched indexes. The first-cycle conversion factor is set in advance based on empirical values. To calculate the first-cycle component corresponding to the urgency of demand. Then, the summation is performed based on the span of all stages between the data acquisition stage and the baseline acquisition stage, combined with a second-cycle conversion factor pre-set based on empirical values. To calculate the second periodic component corresponding to the stage span. Finally, based on the pre-set weights for the first and second periods, the first and second period components are weighted and fused to obtain the final continuous monitoring period, which can be expressed by the formula: .

[0044] Please see Figure 2 The present invention also provides a method for tracing data exchange logs between systems, comprising: Step S10: Obtain the target data exchange log during each inter-system data exchange process through the log acquisition unit 111; Step S20: The content parsing unit 112 performs content parsing on the target data exchange log to obtain the corresponding target traceability index dimensions and the target index content corresponding to each target traceability index dimension; Step S30: The request retrieval unit 113 retrieves multiple chain tracing requests corresponding to each target tracing index dimension; Step S40: The matching analysis unit 114 performs a traceability matching analysis on the corresponding target index content in the repository according to each chain traceability request, and obtains the traceability matching result; Step S50: Based on the traceability matching result, the storage control unit 115 controls the writing of the data exchange log to the storage repository, and continuously monitors the unmatched index content according to the corresponding traceability index dimension until the end of the continuous monitoring period to complete the log traceability.

[0045] In summary, the inter-system data exchange log tracing system and method disclosed in this invention acquires the target data exchange log during each inter-system data exchange process, then parses the content of the target data exchange log to derive multiple target tracing index dimensions, and determines the corresponding target index content in the target data exchange log based on these target tracing index dimensions. For each target tracing index dimension, the corresponding chain tracing request is found. For a chain tracing request, there may be multiple chain tracing requests simultaneously containing the same tracing index dimension; therefore, for a given target tracing index dimension, multiple corresponding chain tracing requests can be determined. After determining the chain tracing requests, a tracing matching analysis of the target index content against the corresponding data tracing chain can be performed in a repository storing all historical data exchange logs, thereby determining whether the current target index content has a corresponding matching content in the repository. Finally, based on the tracing matching results of the tracing matching analysis, the target data exchange log corresponding to the matched target index content is stored in the repository. Furthermore, if the target index content does not match, it is possible that the target index content corresponding to the current target data exchange log is not the content required to form the data traceability chain. Therefore, based on the data collection stage of the target data exchange log, it can be further determined whether to wait for the collection of the corresponding data log or to directly delete and clean up the relevant target data exchange log. This reduces the storage of log content that does not have inter-system correlation, thereby relieving the cache pressure on the repository and ensuring the integrity and traceability of each related data log when searching based on traceability requests for each chain. This improves the effectiveness of log content storage, data security, and compliance. Therefore, this invention effectively overcomes the various shortcomings of the prior art and has high industrial application value.

[0046] The above embodiments are merely illustrative of the principles and effects of the present invention and are not intended to limit the invention. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in the present invention should still be covered by the claims of the present invention.

Claims

1. A system for tracing data exchange logs between systems, characterized in that, include: The log acquisition unit is used to acquire the target data exchange log during each inter-system data exchange process. The content parsing unit is used to parse the target data exchange log to obtain the corresponding target traceability index dimensions and the target index content corresponding to each target traceability index dimension. The request retrieval unit is used to retrieve multiple chain tracing requests corresponding to each of the target tracing index dimensions. The matching analysis unit is used to perform traceability matching analysis on the corresponding target index content in the repository according to each chain traceability request, and obtain the traceability matching result; as well as The storage control unit is used to control the writing of the data exchange log to the storage repository according to the traceability matching result, and to continuously monitor the unmatched index content according to the corresponding traceability index dimension until the continuous monitoring period ends to complete the log traceability. The matching analysis unit includes: The dimension extraction subunit is used to extract other traceability index dimensions corresponding to each chain tracing request. Extracting other traceability index dimensions corresponding to each chain tracing request includes: finding the set of traceability index dimensions required by the chain tracing request for each chain tracing request; and extracting other traceability index dimensions other than the target traceability index dimension used to find the chain tracing request from the set of traceability index dimensions. The chain-building subunit is used to query the corresponding historical data exchange logs of the repository according to the other traceability index dimensions, obtain the corresponding historical index content, and form a corresponding data traceability chain. A dimension generation subunit is used to generate a comprehensive constraint dimension for the target index content based on the data tracing chain and tracing constraint dimensions; and The content judgment subunit is used to determine whether the target index content is within the comprehensive restriction dimension; if yes, the traceability matching result is that the target index content matches the data traceability chain corresponding to the historical index content; if no, the traceability matching result is that the target index content does not match the data traceability chain corresponding to the historical index content. The matching analysis unit further includes: The dimension combination subunit is used to freely combine the other traceability index dimensions corresponding to the historical index content in the data traceability chain to obtain an index dimension combination; and The traceability restriction output subunit is used to search the combination library according to the index dimension combination to obtain a preset index dimension combination that is consistent with the index dimension combination, and to obtain the corresponding traceability restriction dimension according to the preset index dimension combination. The combination library includes multiple traceability restriction dimensions corresponding to the preset index dimension combination. The dimension generation subunit includes: The constraint analysis module is used to perform constraint analysis on the data tracing chain to obtain the constraint dimensions of the chain; and The comprehensive output module is used to generate a comprehensive constraint dimension for the target index content based on the chain constraint dimension and the traceability constraint dimension; The limitation analysis module includes: The information extraction submodule is used to extract dimensional information from the corresponding historical index content in the data traceability chain to obtain the dimensional types and the dimensional data corresponding to each dimensional type. The dimensional types include time dimension, participating entity dimension, business identifier dimension, data theme dimension and data flow path dimension. The boundary determination submodule is used to determine the dimension boundaries corresponding to the same dimension type based on the dimension data of the same dimension type; and The chain constraint output submodule is used to obtain the chain constraint dimension corresponding to different dimension types based on the dimension type and the dimension boundary.

2. The inter-system data exchange log traceability system according to claim 1, characterized in that, The content parsing unit includes: The content conversion subunit is used to sequentially convert the target data exchange log into content based on different traceability index dimensions through a large language model to obtain the converted content. The format detection subunit is used to perform content format detection on the converted content and obtain the detection result; The index output subunit is used to, when the detection result indicates that the content format of the transformed content is normal, take the trace index dimension corresponding to the transformed content as the target trace index dimension and the transformed content as the target index content; when the detection result indicates that the content format of the transformed content is abnormal, continue to perform content transformation on the next trace index dimension of the data exchange log to obtain all the target index content corresponding to the data exchange log.

3. The inter-system data exchange log traceability system according to claim 2, characterized in that, The format detection subunit includes: The format retrieval module is used to retrieve the base content format of the traceability index dimension corresponding to the converted content; The format comparison module is used to compare the similarity between the base content format and the converted content format to obtain a format similarity score; and The result output module is used to determine that the content format of the converted content is normal when the format similarity is greater than the first similarity, and that the content format of the converted content is abnormal when the format similarity is less than the first similarity.

4. The inter-system data exchange log traceability system according to claim 1, characterized in that, The storage control unit includes: The first control subunit is configured to write the target data exchange log to the repository when the traceability matching result shows that the target index content matches the data traceability chain corresponding to the historical index content in the repository; and The second control subunit is used to take the target index content that does not match the data tracing chain corresponding to the historical index content as unmatched index content, perform continuous monitoring analysis on the unmatched index content in the corresponding tracing index dimension, and obtain the analysis results; based on the analysis results, continuously monitor the unmatched index content in the corresponding tracing index dimension until the continuous monitoring period ends to complete log tracing.

5. The inter-system data exchange log traceability system according to claim 4, characterized in that, The second control subunit performs continuous monitoring and analysis on the unmatched index content at the corresponding trace index dimension to obtain analysis results; based on the analysis results, it continuously monitors the unmatched index content at the corresponding trace index dimension until the continuous monitoring period ends to complete log tracing. This process includes: The period detection module is used to detect the data collection period of unmatched index content in order to determine the corresponding data collection stage based on the data collection period. The sequential comparison module is used to compare the data acquisition stage with the benchmark acquisition stage corresponding to the traceability index dimension in terms of stage order. The deletion control module is used to stop continuously monitoring the corresponding traceability index dimension of the unmatched index content and delete the data traceability chain corresponding to the unmatched index content when the data acquisition stage is at or after the benchmark acquisition stage. A periodic evaluation module is used to evaluate the continuous monitoring period based on the urgency of the data tracing chain's need for the unmatched index content and the stage span between the data acquisition stage and the benchmark acquisition stage when the data acquisition stage occurs before the benchmark acquisition stage; and The monitoring and control module is used to, within the continuous monitoring period, stop continuously monitoring the unmatched index content at the corresponding traceability index dimension and delete the data traceability chain corresponding to the unmatched index content when the unmatched index content remains unchanged; when the unmatched index content is updated, continue to use the period evaluation module to evaluate the continuous monitoring period based on the urgency of the data traceability chain demanded by the updated unmatched index content and the stage span between the data acquisition stage and the baseline acquisition stage.

6. A tracing method for an inter-system data exchange log tracing system according to any one of claims 1-5, characterized in that, include: The target data exchange log is obtained through the log acquisition unit during each inter-system data exchange process; The target data exchange log is parsed by the content parsing unit to obtain the corresponding target traceability index dimensions and the target index content corresponding to each target traceability index dimension. The request retrieval unit retrieves multiple chain tracing requests corresponding to each target tracing index dimension. The matching analysis unit performs a tracing matching analysis on the corresponding target index content in the repository based on each tracing request of the chain, and obtains the tracing matching result. Based on the traceability matching results, the storage control unit controls the writing of the data exchange log to the repository and continuously monitors the unmatched index content according to the corresponding traceability index dimensions until the continuous monitoring period ends to complete the log traceability.

Images