Xin creation application compatibility evaluation method and system based on dynamic and static feature fusion

Abstract

The application relates to the technical field of data processing, and discloses a credit application compatibility evaluation method and system based on dynamic and static feature fusion, which comprises the following steps: extracting a static feature set of a target executable file of a credit application, constructing a running simulation environment, loading the file, and obtaining a dynamic behavior sequence; performing behavior similarity matching on an interface name in a calling dependency list in the static feature and a calling name in the dynamic behavior sequence to obtain a first matching degree coefficient; performing node topology comparison and compatibility verification on a static dependency library and a dynamic link library, and obtaining a second matching degree coefficient by coupling the result; constructing a dynamic and static fusion matrix by taking the two coefficients as horizontal and vertical vectors, calculating a comprehensive compatibility score, comparing the score with a preset threshold value, and obtaining a credit application compatibility evaluation conclusion; and the application can improve the efficiency of credit application compatibility evaluation based on dynamic and static feature fusion.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a method and system for evaluating the compatibility of domestic IT applications based on the fusion of dynamic and static features. Background Technology

[0002] Current compatibility assessments of domestic IT applications largely rely on single static feature analysis or dynamic behavior monitoring, failing to effectively integrate these two types of features. This results in a one-sided assessment dimension, making it difficult to comprehensively reflect the application's true adaptation status in the domestic IT environment. Single static analysis cannot capture the dynamic calls and library dependency behaviors during application runtime, while dynamic monitoring lacks a benchmark reference of static structural features. Both methods suffer from missing assessment information, directly reducing the accuracy of compatibility judgments.

[0003] Existing evaluation methods do not perform fine-grained matching and verification of interface call behavior and dependent library topology. They only obtain evaluation results through simple comparison, which cannot quantify the correlation between dynamic and static features and compatibility deviations. At the same time, the evaluation process lacks a unified fusion calculation model and standardized scoring mechanism, making it difficult to generate objective and quantifiable compatibility conclusions. This results in low evaluation efficiency, poor result consistency, and an inability to meet the needs of large-scale adaptation and rapid deployment of domestic IT innovation applications. Summary of the Invention

[0005] This invention provides a method and system for evaluating the compatibility of domestic IT applications based on the fusion of dynamic and static features, in order to solve the problems mentioned in the background art.

[0006] To achieve the above objectives, the present invention provides a method for evaluating the compatibility of domestic IT applications based on the fusion of dynamic and static features, comprising:

[0007] S1: Extract the static feature set of the target executable file in the domestic IT application;

[0008] S2: Construct a runtime simulation environment for the domestic IT application, and load the target executable file into the runtime simulation environment to obtain the dynamic behavior sequence of the domestic IT application;

[0009] S3: Perform behavior similarity matching between the interface names in the call dependency list in the static feature set and the call names in the dynamic behavior sequence to obtain the first matching coefficient of the information technology application;

[0010] S4: Perform node topology comparison and compatibility verification between the static dependency library in the static feature set and the dynamic link library in the dynamic behavior sequence, and couple the comparison results and verification results to obtain the second matching degree coefficient of the information technology application.

[0011] S5: Using the first matching degree coefficient as the horizontal dimension and the second matching degree coefficient as the vertical dimension, construct the dynamic and static fusion matrix of the information technology application to calculate the comprehensive compatibility score of the target executable file.

[0012] S6: Based on the comparison between the comprehensive compatibility score and the preset compatibility threshold, the compatibility evaluation conclusion of the domestic IT application is obtained.

[0013] In a preferred embodiment, the extraction of the static feature set of the target executable file in the domestic IT application includes:

[0014] Obtain the target executable file in the domestic IT application and parse the file header of the target executable file to determine the file format type of the target executable file;

[0015] Based on the file format type, traverse the sections of the file structure in the target executable file, extract the section name and section data corresponding to the section, and obtain the original section information set of the target executable file;

[0016] Based on the function type indicated by the section name, the section data in the original section information set is functionally selected to obtain the target section of the target executable file;

[0017] The segment data of the target segment is extracted using an interface to obtain the call dependency list and static dependency library of the target executable file;

[0018] The interface names in the call dependency list and the library file names in the static dependency library are normalized to obtain the standard interface names and standard library file names of the target executable file, which are then combined into the static feature set of the domestic IT application.

[0019] In a preferred embodiment, the step of constructing a runtime simulation environment for the domestic IT application and loading the target executable file in the runtime simulation environment to obtain the dynamic behavior sequence of the domestic IT application includes:

[0020] Obtain the target operating terminal type and target instruction set architecture corresponding to the aforementioned domestic IT application;

[0021] Based on the target operating terminal type and the target instruction set architecture, create a simulated execution terminal that is compatible with the target executable file's runtime environment;

[0022] In the simulated execution terminal, the target executable file is loaded, and the memory access permissions and call interception rules of the simulated execution terminal are set;

[0023] The target executable file is executed in the simulated execution terminal. According to the call interception rules, the call names and call parameters of the calls issued by the target executable file during its operation are captured in the order of execution time.

[0024] The call name and the call parameters are associated and arranged, and the result is normalized to obtain the dynamic behavior sequence of the information technology application.

[0025] In a preferred embodiment, the step of performing behavior similarity matching between the interface names in the call dependency list of the static feature set and the call names in the dynamic behavior sequence to obtain the first matching coefficient of the domestic IT application includes:

[0026] Extract the call dependency list from the static feature set, obtain the interface names in the call dependency list, and obtain the static interface name set of the domestic IT application;

[0027] Extract the call names from the call events in the dynamic behavior sequence to obtain the dynamic call name set of the domestic IT application;

[0028] Perform name normalization operations on the static interface name set and the dynamic call name set to obtain the first normalized name set and the second normalized name set of the domestic IT application.

[0029] The standardized interface names in the first standardized name set are compared one by one with the standardized call names in the second standardized name set to obtain the pairing results of the information technology application.

[0030] The total number of successful pairing results is counted, and the total number of interfaces with standardized interface names is obtained. The ratio of the total number of successful pairing results to the total number of interfaces is calculated to obtain the initial matching ratio of the domestic IT application.

[0031] Based on the degree of string difference between the standardized interface name and the standardized call name, the initial matching ratio is weighted and corrected to obtain the first matching degree coefficient of the domestic IT application.

[0032] In a preferred embodiment, the step of performing node topology comparison and compatibility verification between the static dependency libraries in the static feature set and the dynamic link libraries in the dynamic behavior sequence includes:

[0033] Extract the static dependency library from the static feature set, and obtain the exported routines contained in the library files in the static dependency library;

[0034] A static routine topology graph of the static dependency library is constructed using the exported routines as nodes and the calling relationships between the exported routines as edges.

[0035] Extract the dynamic link library from the dynamic behavior sequence, and obtain the routine name actually called by the library file in the dynamic link library during runtime;

[0036] A dynamic routine topology graph of the dynamic link library is constructed using the routine names as nodes and the calling sequence relationships between the routine names as edges.

[0037] The static nodes in the static routine topology graph are matched with the dynamic nodes in the dynamic routine topology graph to obtain the topology comparison result of the domestic IT application.

[0038] The routine signatures corresponding to the static nodes and the routine signatures corresponding to the dynamic nodes are subjected to compatibility verification to obtain the compatibility verification result of the domestic IT application.

[0039] In a preferred embodiment, the step of data coupling of the comparison results and the verification results to obtain the second matching coefficient of the information technology application includes:

[0040] The number of successfully matched nodes in the node topology comparison results and the number of compatible node pairs in the compatibility verification results are normalized to obtain the normalized matching value and normalized compatibility value of the domestic IT application.

[0041] The normalized matching value and the normalized compatibility value are coupled together to obtain the initial fusion coefficient of the domestic IT application.

[0042] Based on the number of mismatched nodes in the node topology comparison results and the number of incompatible node pairs in the compatibility verification results, the initial fusion coefficient is penalized and adjusted to obtain the second matching coefficient of the domestic IT application.

[0043] In a preferred embodiment, the step of constructing a dynamic and static fusion matrix of the domestic IT application, using the first matching coefficient as the horizontal dimension and the second matching coefficient as the vertical dimension, to calculate the comprehensive compatibility score of the target executable file, includes:

[0044] Use the first matching degree coefficient as the first dimension coordinate value and the second matching degree coefficient as the second dimension coordinate value;

[0045] The first dimension coordinate value and the second dimension coordinate value are vectorized and combined to obtain the dynamic and static fusion vector of the information technology application.

[0046] The dynamic-static fusion vector is subjected to dimensional expansion mapping to obtain the dynamic-static fusion matrix of the information technology application.

[0047] The diagonal elements of the dynamic-static fusion matrix are used as the self-correlation weights between the first matching coefficient and the second matching coefficient;

[0048] The off-diagonal elements of the dynamic-static fusion matrix are used as the cross-correlation weights between the first matching degree coefficient and the second matching degree coefficient;

[0049] Based on the self-correlation weights and the cross-correlation weights, the dynamic-static fusion matrix is ​​linearly transformed to obtain the intermediate transformation vector of the information technology innovation application.

[0050] Extract the projection components of the intermediate transformation vector onto the principal feature direction of the dynamic-static fusion matrix to obtain the principal component values ​​of the dynamic-static fusion matrix;

[0051] The intermediate transformation vector is subjected to energy normalization to obtain the energy concentration coefficient of the dynamic-static fusion matrix;

[0052] The energy concentration coefficient and the principal component value are fused together to obtain the comprehensive compatibility score of the target executable file.

[0053] In a preferred embodiment, the formula for calculating the comprehensive compatibility score is as follows:

[0054] ;

[0055] In the formula, The overall compatibility score is given. The principal component values ​​are... The energy concentration coefficient is mentioned above. The preset benchmark adjustment constant is determined based on the nonlinear regression analysis results of the historical compatibility test sample set of the domestic IT application. The index coefficient is a preset value, which is determined based on the functional domain characteristics of the information technology application.

[0056] In a preferred embodiment, obtaining the compatibility assessment conclusion of the domestic IT application based on the comparison result between the comprehensive compatibility score and the preset compatibility threshold includes:

[0057] The overall compatibility score is numerically compared with the preset compatibility threshold.

[0058] If the overall compatibility score is not lower than the preset compatibility threshold, then the intermediate judgment result of the domestic IT application is determined.

[0059] When the overall compatibility score is lower than the preset compatibility threshold, the difference between the overall compatibility score and the preset compatibility threshold is graded to obtain the deviation level of the information technology application.

[0060] The intermediate judgment results, the deviation level, and the numerical range identifiers of the comprehensive compatibility score are encapsulated into the compatibility evaluation conclusion of the domestic IT application.

[0061] To address the aforementioned problems, this invention also provides a compatibility evaluation system for domestic IT applications based on dynamic and static feature fusion, the system comprising:

[0062] The static feature module is used to extract the static feature set of target executable files in domestic IT application development.

[0063] The dynamic behavior module is used to construct the runtime simulation environment of the domestic IT application and load the target executable file in the runtime simulation environment to obtain the dynamic behavior sequence of the domestic IT application.

[0064] The similarity matching module is used to perform behavior similarity matching between the interface names in the call dependency list in the static feature set and the call names in the dynamic behavior sequence to obtain the first matching degree coefficient of the information technology application.

[0065] The data coupling module is used to perform node topology comparison and compatibility verification between the static dependency library in the static feature set and the dynamic link library in the dynamic behavior sequence, and to couple the comparison results and verification results to obtain the second matching degree coefficient of the information technology application.

[0066] The scoring determination module is used to construct a dynamic and static fusion matrix of the domestic IT application with the first matching degree coefficient as the horizontal quantity and the second matching degree coefficient as the vertical quantity, so as to calculate the comprehensive compatibility score of the target executable file.

[0067] The compatibility conclusion module is used to obtain the compatibility evaluation conclusion of the domestic IT application based on the comparison result between the comprehensive compatibility score and the preset compatibility threshold.

[0068] Compared with the prior art, the present invention has the following beneficial effects:

[0069] 1. This invention automates the entire process of compatibility assessment for domestic IT applications through the collaborative processing of static feature extraction and dynamic behavior sequence construction. This effectively shortens the time required for feature collection and behavior analysis, significantly improving the overall efficiency of compatibility assessment. By using refined calculations of interface name similarity matching and dependency library topology verification, the compatibility degree of applications can be accurately quantified, improving the accuracy and reliability of the assessment results.

[0070] 2. This invention utilizes a dynamic-static fusion matrix to calculate a comprehensive compatibility score, generating standardized and quantifiable evaluation outputs to ensure the consistency and objectivity of the evaluation conclusions. Based on the comparison of scores and thresholds, it automatically determines the compatibility level, enabling rapid output of standardized evaluation conclusions and meeting the application requirements for large-scale adaptation and efficient deployment of domestic IT innovation applications. Attached Figure Description

[0071] Figure 1 This is a flowchart illustrating a method for evaluating the compatibility of domestic IT applications based on the fusion of dynamic and static features, provided in an embodiment of the present invention.

[0072] Figure 2 This is a functional block diagram of a compatibility evaluation system for domestic IT applications based on dynamic and static feature fusion, provided in an embodiment of the present invention.

[0073] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0074] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0075] This application provides a method for evaluating the compatibility of domestic IT applications based on the fusion of static and dynamic features. The execution entity of this method includes, but is not limited to, at least one of the following electronic devices that can be configured to execute the method provided in this application: a server, a terminal, etc. In other words, the method for evaluating the compatibility of domestic IT applications based on the fusion of static and dynamic features can be executed by software or hardware installed on a terminal device or a server device. The server includes, but is not limited to, a single server, a server cluster, a cloud server, or a cluster of cloud servers. The server can be an independent server or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0076] Reference Figure 1 The diagram shown is a flowchart illustrating a method for evaluating the compatibility of domestically developed applications based on dynamic and static feature fusion, according to an embodiment of the present invention. In this embodiment, the method for evaluating the compatibility of domestically developed applications based on dynamic and static feature fusion includes:

[0077] S1: Extract the static feature set of the target executable file in the domestic IT application;

[0078] In this embodiment of the invention, the extraction of the static feature set of the target executable file in the domestic IT application includes:

[0079] Obtain the target executable file in the domestic IT application and parse the file header of the target executable file to determine the file format type of the target executable file;

[0080] Based on the file format type, traverse the sections of the file structure in the target executable file, extract the section name and section data corresponding to the section, and obtain the original section information set of the target executable file;

[0081] Based on the function type indicated by the section name, the section data in the original section information set is functionally selected to obtain the target section of the target executable file;

[0082] The segment data of the target segment is extracted using an interface to obtain the call dependency list and static dependency library of the target executable file;

[0083] The interface names in the call dependency list and the library file names in the static dependency library are normalized to obtain the standard interface names and standard library file names of the target executable file, which are then combined into the static feature set of the domestic IT application.

[0084] The target executable file is located and read from the installation directory or runtime loading path of the application. The file header data at the beginning of the target executable file is parsed byte by byte using a file parsing tool. The identification fields and structure definition information at fixed positions in the file header are identified. Based on the identified identification information, the preset executable file format standard is matched to determine the file format type of the target executable file.

[0085] Based on the determined file format type, the corresponding file structure parsing rules are invoked. All sections in the target executable file are traversed sequentially according to the storage order of the section header in the file structure. During the traversal, the identifier name corresponding to each section and the complete data content within the coverage area of ​​that section are read one by one. All the read section names and corresponding section data are uniformly summarized and stored to form the original section information set of the target executable file.

[0086] According to the preset functional type classification standard, the functional attributes corresponding to each section name in the original section information set are matched and judged. Section data that does not have program call and dependency association characteristics are eliminated, and only section data related to program interface call and library file loading are retained. The retained sections constitute the target section of the target executable file.

[0087] The program extracts program instructions and symbol information from the data in the target section, identifies the external interface identifiers that need to be called during program execution, and identifies the static library file information bound during program compilation and linking. All identified external interface identifiers are organized into a call dependency list of the target executable file, and all identified static library file information is organized into a static dependency library of the target executable file.

[0088] According to the preset unified naming convention, the format of each interface name in the dependency list is corrected and the name is uniformly converted. At the same time, the format of each library file name in the static dependency library is corrected and the name is uniformly converted. The processed interface name is the standard interface name of the target executable file, and the processed library file name is the standard library file name of the target executable file. All standard interface names and all standard library file names are combined and integrated to finally form the static feature set of the domestic IT application.

[0089] The beneficial effect is that by directly parsing the header of the target executable file to determine the file format type, file structure features can be quickly located, improving the initial efficiency of static feature extraction.

[0090] By traversing the sections according to the file format type and extracting the section name and section data, the underlying structure information of the executable file can be fully obtained, ensuring the comprehensiveness of static feature collection.

[0091] By selecting functions based on the function type of the segment, invalid data can be eliminated, reducing the amount of computation in subsequent processing and improving the accuracy and speed of feature processing.

[0092] By extracting interfaces from the target section, the call dependency list and static dependency library can be directly separated, providing stable static reference data for subsequent dynamic and static feature matching.

[0093] Standardizing interface names and library file names can unify feature representation, eliminate matching errors caused by naming differences, and improve the accuracy of subsequent similarity calculations.

[0094] Combining standard interface names with standard library file names to form a static feature set can provide a complete static benchmark for dynamic behavior sequences, supporting the stable implementation of dynamic-static fusion evaluation.

[0095] S2: Construct a runtime simulation environment for the domestic IT application, and load the target executable file into the runtime simulation environment to obtain the dynamic behavior sequence of the domestic IT application;

[0096] In this embodiment of the invention, the step of constructing a runtime simulation environment for the domestic IT application and loading the target executable file in the runtime simulation environment to obtain the dynamic behavior sequence of the domestic IT application includes:

[0097] Obtain the target operating terminal type and target instruction set architecture corresponding to the aforementioned domestic IT application;

[0098] Based on the target operating terminal type and the target instruction set architecture, create a simulated execution terminal that is compatible with the target executable file's runtime environment;

[0099] In the simulated execution terminal, the target executable file is loaded, and the memory access permissions and call interception rules of the simulated execution terminal are set;

[0100] The target executable file is executed in the simulated execution terminal. According to the call interception rules, the call names and call parameters of the calls issued by the target executable file during its operation are captured in the order of execution time.

[0101] The call name and the call parameters are associated and arranged, and the result is normalized to obtain the dynamic behavior sequence of the information technology application.

[0102] By parsing the program attributes and runtime dependency information of the domestic IT application, the type of hardware terminal and instruction execution architecture that the domestic IT application is adapted to during actual deployment and runtime can be extracted, thereby determining the corresponding target operating terminal type and target instruction set architecture.

[0103] Based on the extracted target operating terminal type and target instruction set architecture, the hardware virtualization and instruction set simulation components are called in the simulation environment construction module. According to the hardware adaptation requirements and instruction execution requirements of the target executable file for the running environment, a simulated execution terminal that can be fully compatible with the execution of the executable file is built.

[0104] The target executable file is imported into the simulated execution terminal that has been set up. At the same time, the system permission configuration module of the simulated execution terminal is used to restrict memory access behaviors such as memory read and write and data storage. Based on the needs of monitoring the behavior of domestic IT application, the interception rules for system interface and function calls during program execution are set.

[0105] The simulation execution terminal is started to execute the target executable file. During the program's operation, various call behaviors initiated by the program are monitored in real time according to the preset call interception rules. The call name and the call parameters carried by each call event are captured one by one according to the actual execution time of the program.

[0106] All captured call names and their corresponding call parameters are arranged in order of execution time. Then, the arranged content is formatted and type-unified through a data format standardization process, ultimately forming a dynamic behavior sequence of information technology application that can fully reflect the program's running process.

[0107] The beneficial effects are that it can accurately obtain the target operating terminal type and target instruction set architecture corresponding to the information technology application, which can provide accurate hardware and instruction references for the construction of the simulation environment and ensure that the simulation environment is highly consistent with the actual operating environment.

[0108] By creating a compatible simulated execution terminal based on the target operating terminal type and target instruction set architecture, the application's running state can be fully reproduced in a non-real deployment environment, ensuring the authenticity of dynamic behavior collection.

[0109] Loading the target executable file and configuring memory access permissions and call interception rules in a simulated execution terminal can stably constrain program execution behavior and provide reliable assurance for accurate capture of runtime call behavior.

[0110] By capturing the call names and call parameters during the execution of the target executable file in chronological order, the program's actual runtime sequence and call details can be fully recorded, ensuring the integrity and timing accuracy of dynamic behavior data.

[0111] Associating and normalizing the call names and call parameters can unify the dynamic behavior data format, eliminate matching obstacles caused by data heterogeneity, and improve the efficiency and stability of subsequent dynamic and static feature fusion calculations.

[0112] S3: Perform behavior similarity matching between the interface names in the call dependency list in the static feature set and the call names in the dynamic behavior sequence to obtain the first matching coefficient of the information technology application;

[0113] In this embodiment of the invention, the step of performing behavior similarity matching between the interface names in the call dependency list of the static feature set and the call names in the dynamic behavior sequence to obtain the first matching coefficient of the domestic IT application includes:

[0114] Extract the call dependency list from the static feature set, obtain the interface names in the call dependency list, and obtain the static interface name set of the domestic IT application;

[0115] Extract the call names from the call events in the dynamic behavior sequence to obtain the dynamic call name set of the domestic IT application;

[0116] Perform name normalization operations on the static interface name set and the dynamic call name set to obtain the first normalized name set and the second normalized name set of the domestic IT application.

[0117] The standardized interface names in the first standardized name set are compared one by one with the standardized call names in the second standardized name set to obtain the pairing results of the information technology application.

[0118] The total number of successful pairing results is counted, and the total number of interfaces with standardized interface names is obtained. The ratio of the total number of successful pairing results to the total number of interfaces is calculated to obtain the initial matching ratio of the domestic IT application.

[0119] Based on the degree of string difference between the standardized interface name and the standardized call name, the initial matching ratio is weighted and corrected to obtain the first matching degree coefficient of the domestic IT application.

[0120] Extract the call dependency list from the static feature set, traverse all interface-related records in the call dependency list, read and summarize the interface names contained therein, and integrate all the extracted interface names to form the static interface name set corresponding to the information technology application.

[0121] Traverse all behavior records within the dynamic behavior sequence, filter out behavior data belonging to the call event type, extract the corresponding call name from each call event data, and integrate all extracted call names to form a dynamic call name set corresponding to the domestic IT application.

[0122] Perform a uniform name normalization operation on each interface name in the static interface name set, removing meaningless special characters, redundant spaces, and version number suffixes from the name, standardizing the capitalization of the name, and simplifying redundant modifiers. After processing, the first normalized name set corresponding to the domestic IT application is obtained. Perform the same name normalization operation on each call name in the dynamic call name set, and the second normalized name set corresponding to the domestic IT application is obtained.

[0123] Each normalized interface name in the first normalized name set is extracted sequentially. The normalized interface name is compared with each normalized call name in the second normalized name set to determine whether the two are completely consistent. The consistency or inconsistency results of each comparison are recorded to form the matching results corresponding to the information technology application.

[0124] The total number of successful pairings is obtained by summing up all matching results. The total number of normalized interface names in the first normalized name set is also counted to obtain the total number of interfaces. The total number of successful pairings is divided by the total number of interfaces to obtain the calculation result, which is the initial matching ratio corresponding to the domestic IT application.

[0125] Each pair of successfully matched standardized interface names and standardized call names is compared one by one. The degree of difference between the two strings is judged from aspects such as character length, character order, and the proportion of identical characters. The smaller the difference, the higher the correction weight is assigned, and the larger the difference, the lower the correction weight is assigned. The initial matching ratio and the correction weight of the corresponding pair are combined and adjusted in turn to finally obtain the first matching degree coefficient corresponding to the information technology application.

[0126] The beneficial effect is that extracting the interface names from the static feature set to form a static interface name set can provide a stable static reference benchmark for dynamic calling behavior.

[0127] By extracting the call names from the dynamic behavior sequence to form a dynamic call name set, the actual call characteristics of the application at runtime can be fully preserved.

[0128] Performing a unified standardization operation on the two types of name sets can eliminate comparison errors caused by differences in naming formats and improve the accuracy of name matching.

[0129] By comparing the two sets of standardized names one by one to generate pairing results, the matching and non-matching status of interface calls can be clearly distinguished.

[0130] The initial matching ratio is calculated by the ratio of the number of successful matches to the total number of interfaces, which can intuitively quantify the overall matching degree of interface calls.

[0131] By combining the degree of string difference with the weighted correction of the initial matching ratio, the distinguishability of the matching degree can be refined, making the first matching degree coefficient more in line with the actual compatibility state.

[0132] S4: Perform node topology comparison and compatibility verification between the static dependency library in the static feature set and the dynamic link library in the dynamic behavior sequence, and couple the comparison results and verification results to obtain the second matching degree coefficient of the information technology application.

[0133] In this embodiment of the invention, the step of performing node topology comparison and compatibility verification between the static dependency libraries in the static feature set and the dynamic link libraries in the dynamic behavior sequence includes:

[0134] Extract the static dependency library from the static feature set, and obtain the exported routines contained in the library files in the static dependency library;

[0135] A static routine topology graph of the static dependency library is constructed using the exported routines as nodes and the calling relationships between the exported routines as edges.

[0136] Extract the dynamic link library from the dynamic behavior sequence, and obtain the routine name actually called by the library file in the dynamic link library during runtime;

[0137] A dynamic routine topology graph of the dynamic link library is constructed using the routine names as nodes and the calling sequence relationships between the routine names as edges.

[0138] The static nodes in the static routine topology graph are matched with the dynamic nodes in the dynamic routine topology graph to obtain the topology comparison result of the domestic IT application.

[0139] The routine signatures corresponding to the static nodes and the routine signatures corresponding to the dynamic nodes are subjected to compatibility verification to obtain the compatibility verification result of the domestic IT application.

[0140] The step of coupling the comparison results and verification results to obtain the second matching coefficient of the information technology application includes:

[0141] The number of successfully matched nodes in the node topology comparison results and the number of compatible node pairs in the compatibility verification results are normalized to obtain the normalized matching value and normalized compatibility value of the domestic IT application.

[0142] The normalized matching value and the normalized compatibility value are coupled together to obtain the initial fusion coefficient of the domestic IT application.

[0143] Based on the number of mismatched nodes in the node topology comparison results and the number of incompatible node pairs in the compatibility verification results, the initial fusion coefficient is penalized and adjusted to obtain the second matching coefficient of the domestic IT application.

[0144] Extract the corresponding static dependency libraries from the static feature set, read the structure information of each library file in the static dependency library one by one, traverse the program entry point and related data of the functions provided to the outside world recorded in the library file, and obtain all the exported routines contained in the library file.

[0145] Based on the obtained exported routines, each exported routine is set as an independent topology node. The call relationships between each exported routine during the program compilation and static loading stages are sorted out. Connection edges between nodes are established based on the existing direct or indirect call relationships. The topology graph of the static routines corresponding to the static dependency library is fully constructed according to the correspondence between nodes and edges.

[0146] The dynamic link libraries loaded during the runtime phase are filtered and extracted from the dynamic behavior sequence. The execution flow of each library file in the dynamic link library is tracked during the actual program runtime. The program routines that are triggered during the runtime are recorded, and the names of the routines actually called by the library files in the dynamic link library are obtained in full.

[0147] Each routine name obtained is used as an independent topology node. The order of association between nodes is determined according to the order in which routines are called during program execution. Connection edges between nodes are established based on the timing call relationship. The dynamic routine topology graph corresponding to the dynamic link library is constructed based on the combination relationship between nodes and timing edges.

[0148] Traverse all static nodes in the static routine topology graph, match and compare the exported routine content corresponding to each static node with the routine name corresponding to each dynamic node in the dynamic routine topology graph, record the node matching success and failure, and form the topology comparison result corresponding to the domestic innovation application.

[0149] Extract the routine signature information of the exported routines corresponding to static nodes, and extract the routine signature information of the actual called routines corresponding to dynamic nodes. Perform consistency verification on the two sets of routine signatures one by one from the perspectives of parameter type, return value format, calling specification and function definition to determine whether the routines can be normally adapted and called, and obtain the compatibility verification result corresponding to the domestic IT application.

[0150] The total number of successfully matched nodes in the node topology comparison results is counted. This number is then compared with the total number of nodes in the static routine topology graph. The calculated value is then mapped to a fixed numerical range to form the normalized matching value corresponding to the domestic IT application. The total number of compatible node pairs in the compatibility verification results is counted. This number is then compared with the total number of node pairs participating in the compatibility verification. The calculated value is then mapped to the same fixed numerical range to form the normalized compatibility value corresponding to the domestic IT application.

[0151] The normalized matching value and the normalized compatibility value are fused and calculated item by item according to the node correspondence. The values ​​corresponding to the same node in the two sets of normalized values ​​are merged. After integrating the fused values ​​of all nodes, the initial fusion coefficient corresponding to the information technology application is obtained.

[0152] The number of mismatched nodes that failed to match in the node topology comparison results is counted, and the number of incompatible node pairs that failed to verify in the compatibility verification results is also counted. The value of the initial fusion coefficient is gradually reduced according to the number of mismatched nodes and incompatible node pairs. The more mismatched and incompatible nodes there are, the greater the adjustment range. After the adjustment is completed, the second matching degree coefficient corresponding to the domestic IT application is obtained.

[0153] The beneficial effect is that by extracting the exported routines from the static dependency library, we can fully obtain the functional execution units provided by the library file, and provide basic node data for topology construction.

[0154] A static routine topology graph is constructed using exported routines as nodes and calling relationships as edges, which can intuitively present the structural relationships and calling logic of library files during the compilation stage.

[0155] Extracting the names of routines actually called by dynamic link libraries at runtime allows for accurate collection of functional execution information actually used during application runtime.

[0156] A dynamic routine topology graph is constructed using routine names as nodes and call sequence relationships as edges, which can completely restore the execution flow and association relationships of library files at runtime.

[0157] Matching static and dynamic nodes yields topology comparison results, which can verify the consistency between static dependencies and dynamic calls at the structural level.

[0158] Compatibility checks on routine signatures can determine whether dependent libraries meet the adaptation requirements for actual operation from the functional interface level.

[0159] Normalizing the number of successfully matched nodes and the number of compatible node pairs can unify the two types of comparison data into the same numerical range, improving the comparability of subsequent fusion calculations.

[0160] By coupling the normalized matching value with the normalized compatibility value, two core types of information—topology and functional compatibility—can be integrated to form a comprehensive initial fusion coefficient.

[0161] By applying a penalty adjustment to the initial fusion coefficient based on the number of mismatched nodes and incompatible node pairs, the impact of compatibility defects can be objectively reflected, making the second matching coefficient more closely match the actual adaptation level.

[0162] S5: Using the first matching degree coefficient as the horizontal dimension and the second matching degree coefficient as the vertical dimension, construct the dynamic and static fusion matrix of the information technology application to calculate the comprehensive compatibility score of the target executable file.

[0163] In this embodiment of the invention, the step of constructing a dynamic and static fusion matrix of the domestic IT application using the first matching coefficient as the horizontal dimension and the second matching coefficient as the vertical dimension, in order to calculate the comprehensive compatibility score of the target executable file, includes:

[0164] Use the first matching degree coefficient as the first dimension coordinate value and the second matching degree coefficient as the second dimension coordinate value;

[0165] The first dimension coordinate value and the second dimension coordinate value are vectorized and combined to obtain the dynamic and static fusion vector of the information technology application.

[0166] The dynamic-static fusion vector is subjected to dimensional expansion mapping to obtain the dynamic-static fusion matrix of the information technology application.

[0167] The diagonal elements of the dynamic-static fusion matrix are used as the self-correlation weights between the first matching coefficient and the second matching coefficient;

[0168] The off-diagonal elements of the dynamic-static fusion matrix are used as the cross-correlation weights between the first matching degree coefficient and the second matching degree coefficient;

[0169] Based on the self-correlation weights and the cross-correlation weights, the dynamic-static fusion matrix is ​​linearly transformed to obtain the intermediate transformation vector of the information technology innovation application.

[0170] Extract the projection components of the intermediate transformation vector onto the principal feature direction of the dynamic-static fusion matrix to obtain the principal component values ​​of the dynamic-static fusion matrix;

[0171] The intermediate transformation vector is subjected to energy normalization to obtain the energy concentration coefficient of the dynamic-static fusion matrix;

[0172] The energy concentration coefficient and the principal component value are fused together to obtain the comprehensive compatibility score of the target executable file.

[0173] The formula for calculating the overall compatibility score is as follows:

[0174] ;

[0175] In the formula, The overall compatibility score is given. The principal component values ​​are... The energy concentration coefficient is mentioned above. The preset benchmark adjustment constant is determined based on the nonlinear regression analysis results of the historical compatibility test sample set of the domestic IT application. The index coefficient is a preset value, which is determined based on the functional domain characteristics of the information technology application.

[0176] The first matching degree coefficient is directly set as the first dimension coordinate value in the matrix construction process, and the second matching degree coefficient is directly set as the second dimension coordinate value in the matrix construction process.

[0177] According to the coordinate dimension correspondence, the first dimension coordinate value and the second dimension coordinate value are vectorized and combined in an orderly manner to form a set of vector data with clear dimension orientation. This vector data is the dynamic and static fusion vector corresponding to the information technology application.

[0178] The static-dynamic fusion vector, which contains only two dimensions, is expanded according to a preset matrix mapping rule. Each coordinate value in the vector is mapped to the corresponding matrix position. After dimension filling and format conversion, the static-dynamic fusion matrix corresponding to the information technology application is obtained.

[0179] In the generated dynamic-static fusion matrix, all elements on the diagonal are uniformly set as the self-correlation weights of the first matching degree coefficient and the second matching degree coefficient, which are used to reflect the degree of independent correlation of the two coefficients.

[0180] All elements outside the diagonal in the dynamic-static fusion matrix are uniformly set as the cross-correlation weight between the first matching degree coefficient and the second matching degree coefficient, which is used to reflect the degree of influence between the two coefficients.

[0181] Based on the numerical distribution of self-correlation weights and cross-correlation weights, a linear transformation operation is performed row by row and column by column on the dynamic-static fusion matrix. The elements in the matrix are adjusted and combined in an orderly manner according to the weight values. After the transformation is completed, the intermediate transformation vector corresponding to the information technology application is obtained.

[0182] Determine the principal feature direction corresponding to the static-dynamic fusion matrix, project the intermediate transformation vector as a whole onto this principal feature direction, and retain the effective component data formed after projection. This component data is the principal component value corresponding to the static-dynamic fusion matrix.

[0183] Energy normalization is performed on all component values ​​within the intermediate transformation vector to adjust the energy values ​​of each component within the vector to a standard range. The concentration of the overall energy distribution of the vector is then calculated, and this value is the energy concentration coefficient corresponding to the dynamic-static fusion matrix.

[0184] The energy concentration coefficient and principal component values ​​are calculated item by item according to their corresponding relationship. After integrating the effective information of the two sets of data, the final calculation result is obtained, which is the comprehensive compatibility score corresponding to the target executable file.

[0185] In the formula for calculating the comprehensive compatibility score, each parameter is derived from the specific calculation results and preset configurations during the compatibility analysis of domestic IT applications. The specific sources are as follows.

[0186] The principal component value of the comprehensive compatibility score comes from the projection component of the intermediate transformation vector of the dynamic-static fusion matrix onto the principal feature direction of the dynamic-static fusion matrix. Specifically, it is obtained by determining the principal feature direction of the dynamic-static fusion matrix, projecting the intermediate transformation vector onto the principal feature direction, and retaining the effective component data formed after projection.

[0187] The energy concentration coefficient is derived from the energy normalization process of the intermediate transformation vector. Specifically, the energy normalization operation is performed on all component values ​​within the intermediate transformation vector to adjust the energy values ​​of each component within the vector to a standard range, thereby calculating the concentration value of the overall energy distribution of the vector.

[0188] The benchmark adjustment constant is determined based on the nonlinear regression analysis results of the historical compatibility test sample set of the domestic IT application. Specifically, all past compatibility test sample data of the domestic IT application are collected, and nonlinear regression analysis is performed on these sample data. By sorting out the nonlinear correlation between input and output in the sample data, the benchmark adjustment constant used to adjust the accuracy of the formula calculation is determined.

[0189] The index coefficient is determined based on the functional domain characteristics of the domestic IT application. Specifically, it involves clarifying the functional domain to which the domestic IT application belongs, analyzing the application characteristics, compatibility requirements, and operating environment characteristics of that functional domain, and combining the compatibility testing experience of that domain to determine the index coefficient used to balance the influence weight of the energy concentration coefficient.

[0190] The significance of this calculation formula is that by integrating the principal component values ​​of the dynamic and static fusion matrix with the energy concentration coefficient, and combining them with the preset benchmark adjustment constant and exponential coefficient, a comprehensive compatibility quantitative calculation of the target executable file of the information technology application is performed to obtain a comprehensive compatibility score that can accurately reflect the compatibility level of the target executable file.

[0191] In the calculation formula, the principal component value reflects the core feature information of the dynamic-static fusion matrix, the energy concentration coefficient reflects the degree of energy distribution concentration of the intermediate transformation vector, the benchmark adjustment constant is used to adapt to the characteristics of historical test data of the domestic innovation application, ensuring that the calculation results conform to the past test patterns, and the exponential coefficient is used to adapt to the characteristics of the functional domain to which the domestic innovation application belongs, so that the calculation results meet the compatibility evaluation standards of that domain. The comprehensive compatibility score obtained by combining the four through formula calculation can comprehensively and accurately quantify the compatibility level of the target executable file, providing a clear and quantifiable judgment basis for the compatibility evaluation of domestic innovation applications.

[0192] The beneficial effect is that by using the first and second matching degree coefficients as dimensional coordinate values, the quantitative reference basis for dynamic and static features can be clearly defined, ensuring the stability of vector construction.

[0193] By vectorizing and combining the two types of coordinate values ​​to form a dynamic-static fusion vector, the two types of features of interface matching and library compatibility can be organically combined.

[0194] Performing a dimensionality extension mapping on the dynamic-static fusion vector yields a dynamic-static fusion matrix, which can provide a structured data carrier for feature correlation analysis.

[0195] Setting the diagonal elements of the matrix as self-correlation weights can accurately characterize the independent correlation strength of the two types of matching coefficients.

[0196] Setting the off-diagonal elements of the matrix as interrelated weights can fully reflect the mutual influence and synergistic relationship between dynamic and static features.

[0197] By performing linear transformations on the matrix based on self-correlation weights and cross-correlation weights, the intrinsic correlation information of dynamic and static features can be effectively extracted.

[0198] By extracting the projection components of the intermediate transformation vector onto the principal feature direction, the principal component values ​​can be obtained, which can lock in the core feature information for compatibility evaluation.

[0199] Energy normalization is performed on the intermediate transformation vector to obtain the energy concentration coefficient, which can quantify the degree of concentration of feature information distribution.

[0200] By integrating the energy concentration coefficient with the principal component values, the core information of dynamic and static characteristics can be fully integrated to obtain an objective and accurate comprehensive compatibility score.

[0201] This calculation formula can organically combine the principal component values ​​with the energy concentration coefficient, achieving standardized quantitative output of dynamic and static fusion characteristics.

[0202] Principal component values ​​can preserve core feature information in compatibility assessment, ensuring that the scoring results reflect the true compatibility status of the application.

[0203] The energy concentration coefficient is used to characterize the degree of concentration of the feature distribution and improve the scoring ability to distinguish compatibility stability.

[0204] The benchmark adjustment constant is determined based on the nonlinear regression analysis of historical compatibility test samples, so that the scoring calculation conforms to the historical adaptation pattern of information technology application.

[0205] The index coefficients are determined based on the functional domain characteristics of the information technology application, allowing the scoring results to adapt to the compatibility evaluation standards of different domains.

[0206] The formula integrates energy features in an exponential form, which can amplify the scoring advantage of highly compatible samples and improve the recognizability of the evaluation results.

[0207] This calculation method can output a continuous and quantifiable comprehensive compatibility score, providing stable and reliable data support for subsequent threshold determination.

[0208] S6: Based on the comparison between the comprehensive compatibility score and the preset compatibility threshold, the compatibility evaluation conclusion of the domestic IT application is obtained.

[0209] In this embodiment of the invention, obtaining the compatibility assessment conclusion of the domestic IT application based on the comparison result between the comprehensive compatibility score and the preset compatibility threshold includes:

[0210] The overall compatibility score is numerically compared with the preset compatibility threshold.

[0211] If the overall compatibility score is not lower than the preset compatibility threshold, then the intermediate judgment result of the domestic IT application is determined.

[0212] When the overall compatibility score is lower than the preset compatibility threshold, the difference between the overall compatibility score and the preset compatibility threshold is graded to obtain the deviation level of the information technology application.

[0213] The intermediate judgment results, the deviation level, and the numerical range identifiers of the comprehensive compatibility score are encapsulated into the compatibility evaluation conclusion of the domestic IT application.

[0214] The calculated overall compatibility score is compared with the pre-set compatibility thresholds item by item to directly determine the relationship between the two.

[0215] When the overall compatibility score is greater than or equal to the preset compatibility threshold, the intermediate judgment result corresponding to the domestic IT application is directly determined according to the preset evaluation and judgment rules.

[0216] When the overall compatibility score is less than the preset compatibility threshold, the difference between the preset compatibility threshold and the overall compatibility score is first calculated. Then, the difference is matched and classified step by step according to the pre-defined difference range to obtain the deviation level corresponding to the domestic IT application.

[0217] The determined intermediate judgment results, deviation level, and numerical range identifiers corresponding to the comprehensive compatibility score are uniformly integrated and packaged to form a data set containing complete judgment information. This data set is the compatibility assessment conclusion corresponding to the domestic IT application.

[0218] The beneficial effect is that by comparing the overall compatibility score with the preset compatibility threshold, the basic qualification of the application's compatibility status can be quickly determined.

[0219] When the overall compatibility score is not lower than the preset threshold, the intermediate judgment result is directly determined, which can simplify the evaluation process of qualified applications and improve the judgment efficiency.

[0220] By performing differential grading on scores below a threshold, the degree of deviation can be accurately quantified to determine the severity of compatibility defects.

[0221] By uniformly encapsulating the deviation level and numerical range identifiers of intermediate judgment results, a complete, clear, and directly usable compatibility assessment conclusion can be formed.

[0222] The evaluation results of multi-dimensional information encapsulation can provide clear directions and basis for the adaptation and optimization of information technology application.

[0223] like Figure 2 The diagram shown is a functional block diagram of a compatibility evaluation system for domestic IT applications based on dynamic and static feature fusion, provided by an embodiment of the present invention.

[0224] The compatibility evaluation system 100 for domestic IT applications based on static and dynamic feature fusion described in this invention can be installed in electronic devices. Depending on the functions implemented, the compatibility evaluation system 100 may include a static feature module 101, a dynamic behavior module 102, a similarity matching module 103, a data coupling module 104, a scoring determination module 105, and a compatibility conclusion module 106. The module described in this invention can also be called a unit, which refers to a series of computer program segments that can be executed by the processor of an electronic device and can perform a fixed function, stored in the memory of the electronic device.

[0225] In this embodiment, the functions of each module / unit are as follows:

[0226] The static feature module 101 is used to extract the static feature set of the target executable file in the information technology application.

[0227] The dynamic behavior module 102 is used to construct the runtime simulation environment of the domestic IT application and load the target executable file in the runtime simulation environment to obtain the dynamic behavior sequence of the domestic IT application.

[0228] The similarity matching module 103 is used to perform behavior similarity matching between the interface names in the call dependency list in the static feature set and the call names in the dynamic behavior sequence to obtain the first matching degree coefficient of the information technology application.

[0229] The data coupling module 104 is used to perform node topology comparison and compatibility verification between the static dependency library in the static feature set and the dynamic link library in the dynamic behavior sequence, and to couple the comparison result and the verification result to obtain the second matching degree coefficient of the information technology application.

[0230] The scoring determination module 105 is used to construct a dynamic and static fusion matrix of the information technology application with the first matching degree coefficient as the horizontal quantity and the second matching degree coefficient as the vertical quantity, so as to calculate the comprehensive compatibility score of the target executable file.

[0231] The compatibility conclusion module 106 is used to obtain the compatibility evaluation conclusion of the domestic IT application based on the comparison result between the comprehensive compatibility score and the preset compatibility threshold.

[0232] In the several embodiments provided by this invention, it should be understood that the disclosed methods and systems can be implemented in other ways. For example, the system embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and other division methods may be used in actual implementation.

[0233] The modules described as separate components may or may not be physically separate. The components shown as modules 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 modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0234] Furthermore, the functional modules in the various embodiments of the present invention 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 in the form of hardware plus software functional modules.

[0235] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the present invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention.

[0236] This application embodiment can acquire and process relevant data based on artificial intelligence technology. Artificial intelligence is the theory, method, technology, and application system that uses digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to obtain optimal results.

[0237] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention.

Claims

1. A method for evaluating the compatibility of domestic IT applications based on the fusion of dynamic and static features, characterized in that, The method includes: S1: Extract the static feature set of the target executable file in the domestic IT application; S2: Construct a runtime simulation environment for the domestic IT application, and load the target executable file into the runtime simulation environment to obtain the dynamic behavior sequence of the domestic IT application; S3: Perform behavior similarity matching between the interface names in the call dependency list in the static feature set and the call names in the dynamic behavior sequence to obtain the first matching coefficient of the information technology application; S4: Perform node topology comparison and compatibility verification between the static dependency library in the static feature set and the dynamic link library in the dynamic behavior sequence, and couple the comparison results and verification results to obtain the second matching degree coefficient of the information technology application. S5: Using the first matching degree coefficient as the horizontal dimension and the second matching degree coefficient as the vertical dimension, construct the dynamic and static fusion matrix of the information technology application to calculate the comprehensive compatibility score of the target executable file. S6: Based on the comparison between the comprehensive compatibility score and the preset compatibility threshold, the compatibility evaluation conclusion of the domestic IT application is obtained.

2. The compatibility evaluation method for information technology application innovation based on dynamic and static feature fusion as described in claim 1, characterized in that, The extraction of the static feature set of the target executable file in the domestic IT application includes: Obtain the target executable file in the domestic IT application and parse the file header of the target executable file to determine the file format type of the target executable file; Based on the file format type, traverse the sections of the file structure in the target executable file, extract the section name and section data corresponding to the section, and obtain the original section information set of the target executable file; Based on the function type indicated by the section name, the section data in the original section information set is functionally selected to obtain the target section of the target executable file; The segment data of the target segment is extracted using an interface to obtain the call dependency list and static dependency library of the target executable file; The interface names in the call dependency list and the library file names in the static dependency library are normalized to obtain the standard interface names and standard library file names of the target executable file, which are then combined into the static feature set of the domestic IT application.

3. The compatibility evaluation method for information technology application innovation based on dynamic and static feature fusion as described in claim 1, characterized in that, The process of constructing a runtime simulation environment for the domestic IT application and loading the target executable file within that environment to obtain the dynamic behavior sequence of the domestic IT application includes: Obtain the target operating terminal type and target instruction set architecture corresponding to the aforementioned domestic IT application; Based on the target operating terminal type and the target instruction set architecture, create a simulated execution terminal that is compatible with the target executable file's runtime environment; In the simulated execution terminal, the target executable file is loaded, and the memory access permissions and call interception rules of the simulated execution terminal are set; The target executable file is executed in the simulated execution terminal. According to the call interception rules, the call names and call parameters of the calls issued by the target executable file during its operation are captured in the order of execution time. The call name and the call parameters are associated and arranged, and the result is normalized to obtain the dynamic behavior sequence of the information technology application.

4. The compatibility evaluation method for information technology application innovation based on dynamic and static feature fusion as described in claim 1, characterized in that, The step of performing behavior similarity matching between the interface names in the call dependency list of the static feature set and the call names in the dynamic behavior sequence to obtain the first matching coefficient of the domestic IT application includes: Extract the call dependency list from the static feature set, obtain the interface names in the call dependency list, and obtain the static interface name set of the domestic IT application; Extract the call names from the call events in the dynamic behavior sequence to obtain the dynamic call name set of the domestic IT application; Perform name normalization operations on the static interface name set and the dynamic call name set to obtain the first normalized name set and the second normalized name set of the domestic IT application. The standardized interface names in the first standardized name set are compared one by one with the standardized call names in the second standardized name set to obtain the pairing results of the information technology application. The total number of successful pairing results is counted, and the total number of interfaces with standardized interface names is obtained. The ratio of the total number of successful pairing results to the total number of interfaces is calculated to obtain the initial matching ratio of the domestic IT application. Based on the degree of string difference between the standardized interface name and the standardized call name, the initial matching ratio is weighted and corrected to obtain the first matching degree coefficient of the domestic IT application.

5. The compatibility evaluation method for information technology application innovation based on dynamic and static feature fusion as described in claim 1, characterized in that, The step of performing node topology comparison and compatibility verification between the static dependency libraries in the static feature set and the dynamic link libraries in the dynamic behavior sequence includes: Extract the static dependency library from the static feature set, and obtain the exported routines contained in the library files in the static dependency library; A static routine topology graph of the static dependency library is constructed using the exported routines as nodes and the calling relationships between the exported routines as edges. Extract the dynamic link library from the dynamic behavior sequence, and obtain the routine name actually called by the library file in the dynamic link library during runtime; A dynamic routine topology graph of the dynamic link library is constructed using the routine names as nodes and the calling sequence relationships between the routine names as edges. The static nodes in the static routine topology graph are matched with the dynamic nodes in the dynamic routine topology graph to obtain the topology comparison result of the domestic IT application. The routine signatures corresponding to the static nodes and the routine signatures corresponding to the dynamic nodes are subjected to compatibility verification to obtain the compatibility verification result of the domestic IT application.

6. The compatibility evaluation method for information technology application innovation based on dynamic and static feature fusion as described in claim 5, characterized in that, The step of coupling the comparison results and verification results to obtain the second matching coefficient of the information technology application includes: The number of successfully matched nodes in the node topology comparison results and the number of compatible node pairs in the compatibility verification results are normalized to obtain the normalized matching value and normalized compatibility value of the domestic IT application. The normalized matching value and the normalized compatibility value are coupled together to obtain the initial fusion coefficient of the domestic IT application. Based on the number of mismatched nodes in the node topology comparison results and the number of incompatible node pairs in the compatibility verification results, the initial fusion coefficient is penalized and adjusted to obtain the second matching coefficient of the domestic IT application.

7. The compatibility evaluation method for information technology application innovation based on dynamic and static feature fusion as described in claim 1, characterized in that, The step of constructing a dynamic and static fusion matrix for the domestic IT application, using the first matching coefficient as the horizontal dimension and the second matching coefficient as the vertical dimension, to calculate the comprehensive compatibility score of the target executable file, includes: Use the first matching degree coefficient as the first dimension coordinate value and the second matching degree coefficient as the second dimension coordinate value; The first dimension coordinate value and the second dimension coordinate value are vectorized and combined to obtain the dynamic and static fusion vector of the information technology application. The dynamic-static fusion vector is subjected to dimensional expansion mapping to obtain the dynamic-static fusion matrix of the information technology application. The diagonal elements of the dynamic-static fusion matrix are used as the self-correlation weights between the first matching coefficient and the second matching coefficient; The off-diagonal elements of the dynamic-static fusion matrix are used as the cross-correlation weights between the first matching degree coefficient and the second matching degree coefficient; Based on the self-correlation weights and the cross-correlation weights, the dynamic-static fusion matrix is ​​linearly transformed to obtain the intermediate transformation vector of the information technology innovation application. Extract the projection components of the intermediate transformation vector onto the principal feature direction of the dynamic-static fusion matrix to obtain the principal component values ​​of the dynamic-static fusion matrix; The intermediate transformation vector is subjected to energy normalization to obtain the energy concentration coefficient of the dynamic-static fusion matrix; The energy concentration coefficient and the principal component value are fused together to obtain the comprehensive compatibility score of the target executable file.

8. The compatibility evaluation method for information technology application innovation based on dynamic and static feature fusion as described in claim 7, characterized in that, The formula for calculating the overall compatibility score is as follows: ; In the formula, The overall compatibility score is given. The principal component values ​​are... The energy concentration coefficient is mentioned above. The preset benchmark adjustment constant is determined based on the nonlinear regression analysis results of the historical compatibility test sample set of the domestic IT application. The index coefficient is a preset value, which is determined based on the functional domain characteristics of the information technology application.

9. The compatibility evaluation method for information technology application innovation based on dynamic and static feature fusion as described in claim 1, characterized in that, The process of obtaining the compatibility assessment conclusion of the domestic IT application based on the comparison between the comprehensive compatibility score and the preset compatibility threshold includes: The overall compatibility score is numerically compared with the preset compatibility threshold. If the overall compatibility score is not lower than the preset compatibility threshold, then the intermediate judgment result of the domestic IT application is determined. When the overall compatibility score is lower than the preset compatibility threshold, the difference between the overall compatibility score and the preset compatibility threshold is graded to obtain the deviation level of the information technology application. The intermediate judgment results, the deviation level, and the numerical range identifiers of the comprehensive compatibility score are encapsulated into the compatibility evaluation conclusion of the domestic IT application.

10. A compatibility evaluation system for domestic IT applications based on dynamic and static feature fusion, characterized in that, The system for implementing the compatibility evaluation method for domestic IT applications based on dynamic and static feature fusion as described in claim 1 includes: The static feature module is used to extract the static feature set of target executable files in domestic IT application development. The dynamic behavior module is used to construct the runtime simulation environment of the domestic IT application and load the target executable file in the runtime simulation environment to obtain the dynamic behavior sequence of the domestic IT application. The similarity matching module is used to perform behavior similarity matching between the interface names in the call dependency list in the static feature set and the call names in the dynamic behavior sequence to obtain the first matching degree coefficient of the information technology application. The data coupling module is used to perform node topology comparison and compatibility verification between the static dependency library in the static feature set and the dynamic link library in the dynamic behavior sequence, and to couple the comparison results and verification results to obtain the second matching degree coefficient of the information technology application. The scoring determination module is used to construct a dynamic and static fusion matrix of the domestic IT application with the first matching degree coefficient as the horizontal quantity and the second matching degree coefficient as the vertical quantity, so as to calculate the comprehensive compatibility score of the target executable file. The compatibility conclusion module is used to obtain the compatibility evaluation conclusion of the domestic IT application based on the comparison result between the comprehensive compatibility score and the preset compatibility threshold.

Images