Desktop browser plug-in compatible adaptation method and system based on xinchuang terminal web application

Abstract

The application provides a desktop browser plug-in compatible adaptation method and system based on Xinhua terminal Web application, relates to the technical field of Xinhua terminal Web application, and first captures runtime behavior data of the plug-in on the Xinhua terminal, including calling a system interface, accessing local resources and output data rendering records, performs time sequence correlation analysis on the data, constructs an interactive behavior fingerprint, identifies an abnormal interactive node, calls a non-matching mode library to determine a non-matching reason and generates an adaptation adjustment instruction, injects the instruction into a plug-in running process, starts a behavior monitoring process, records an adjusted interactive behavior fingerprint, judges plug-in function completion based on the adjusted data, extracts effective adjustment parameters to construct an adaptation operation process, and generates a final compatible adaptation scheme, so that the compatible adaptation efficiency and accuracy of the plug-in and the Xinhua terminal can be improved.

Description

Technical Field

[0001] This invention relates to the field of web application technology for domestically developed terminals, and more specifically, to a method and system for compatibility and adaptation of desktop browser plugins based on web applications for domestically developed terminals. Background Technology

[0002] With the widespread use of domestically developed and domestically produced terminals, the compatibility and adaptation issues of desktop browser plugins for web applications are becoming increasingly prominent. Currently, most browser plugins are developed for general terminal environments. When ported to domestically developed and domestically produced terminals, compatibility issues often arise between the plugins and these terminals due to differences in system architecture, interface specifications, and resource management.

[0003] Existing compatibility and adaptation methods largely rely on manual troubleshooting and simple parameter adjustments. Technical personnel typically need to manually analyze the plugin's operation on domestically developed terminals, observing the plugin's output and system error messages to determine if compatibility issues exist. However, these methods are inefficient and struggle to comprehensively and accurately capture the interaction details between the plugin and the domestically developed terminal. For example, crucial information such as the operation sequence when the plugin calls the domestically developed terminal's system interface, the real-time status of data transmission, and the rendering process of output data on the terminal interface often cannot be effectively obtained and analyzed. This makes it difficult to accurately pinpoint the root cause of compatibility problems, failing to fundamentally resolve the incompatibility between the plugin and the domestically developed terminal, and affecting the normal use of web applications on these terminals. Summary of the Invention

[0004] In view of the aforementioned problems, and in conjunction with the first aspect of the present invention, embodiments of the present invention provide a method for desktop browser plugin compatibility adaptation based on domestically developed terminal web applications, the method comprising: Capture runtime behavior data of the plugin on the domestically developed terminal. The runtime behavior data includes operation records of the plugin calling the system interface of the domestically developed terminal, interaction records of the plugin accessing local resources of the terminal, and rendering records of the plugin output data on the terminal interface. Perform time-series correlation analysis on runtime behavior data, extract feature parameters of each behavior record, construct the interaction behavior fingerprint between the plugin and the domestically developed terminal, and identify nodes with interaction interruption, data transmission stagnation, and abnormal rendering results through the interaction behavior fingerprint to obtain a set of abnormal interaction nodes. For each node in the abnormal interaction node set, a preset mismatch pattern library is called to compare the interaction behavior fingerprint fragment corresponding to the node with the pattern features in the mismatch pattern library to determine the reason for the mismatch between the plug-in operation type and the response type of the domestic innovation terminal, and generate adaptation adjustment instructions. The adaptation and adjustment instructions are injected into the plugin's running process, and the behavior monitoring process of the domestically developed terminal is started. The behavior monitoring process of the domestically developed terminal runs synchronously with the browser's plugin running module, monitors the interaction process between the plugin and the domestically developed terminal after adjustment, records the fingerprint of the interaction behavior after adjustment, and forms the running status data after adjustment. Based on the interaction behavior fingerprint in the adjusted running status data, it is determined whether the plugin can complete all preset functions normally, the effective adjustment parameters in the adaptation adjustment instructions are extracted, the adaptation operation process is constructed, and the effective adjustment parameters and the adaptation operation process are integrated to generate the final compatible adaptation solution.

[0005] Furthermore, embodiments of the present invention also provide a desktop browser plugin compatibility and adaptation system based on domestically developed terminal web applications, characterized in that it includes: A processor; a machine-readable storage medium for storing machine-executable instructions of the processor; wherein the processor is configured to execute the aforementioned desktop browser plugin compatibility adaptation method based on domestically developed terminal web applications by executing the machine-executable instructions.

[0006] In another aspect, embodiments of the present invention also provide a computer program product, the computer program product including machine-executable instructions, the machine-executable instructions being stored in a computer-readable storage medium, a processor of a computer device reading the machine-executable instructions from the computer-readable storage medium, and the processor executing the machine-executable instructions, causing the computer device to execute the above-described desktop browser plugin compatibility adaptation method based on domestically developed terminal web applications.

[0007] Based on the above, by capturing the runtime behavior data of the plugin on the domestically developed terminal, including the plugin's operation records of calling system interfaces, interaction records of accessing local resources, and rendering records of output data on the terminal interface, and then performing time-series correlation analysis on the runtime behavior data to extract feature parameters and construct interaction behavior fingerprints, it is possible to accurately identify nodes with interaction interruptions, data transmission stagnation, and abnormal rendering results, forming a set of abnormal interaction nodes, thereby quickly locating the key location of compatibility issues between the plugin and the domestically developed terminal. For abnormal interaction nodes, a preset mismatch pattern library is called for comparison to determine the cause of the mismatch and generate adaptation adjustment instructions, achieving accurate diagnosis and targeted resolution of compatibility issues. The adaptation adjustment instructions are injected into the plugin's runtime process, and the behavior monitoring process of the domestically developed terminal is started and runs synchronously with the browser plugin runtime module, enabling real-time monitoring of the adjusted interaction process, recording the adjusted interaction behavior fingerprints, and forming adjusted runtime status data to ensure dynamic tracking and evaluation of the adaptation effect. Based on the adjusted running status data, the completion status of the plugin function is judged, effective adjustment parameters are extracted to construct the adaptation operation process, and the final compatibility adaptation solution is generated. This realizes the systematic and automated solution of the compatibility adaptation problem between the plugin and the domestically developed terminal, which greatly improves the efficiency and accuracy of compatibility adaptation and ensures the stable operation of Web applications on domestically developed terminals. Attached Figure Description

[0008] Figure 1 This is a schematic diagram of the execution flow of the desktop browser plugin compatibility and adaptation method based on the domestically developed terminal web application provided in the embodiments of the present invention.

[0009] Figure 2 This is a schematic diagram of exemplary hardware and software components of a desktop browser plugin compatibility and adaptation system based on domestically developed terminal web applications provided in an embodiment of the present invention. Detailed Implementation

[0010] The present invention will now be described in detail with reference to the accompanying drawings. Figure 1 This is a flowchart illustrating a method for compatibility adaptation of desktop browser plugins based on web applications for domestically developed terminals, according to an embodiment of the present invention. The following is a detailed description of this method.

[0011] Step S110: Capture the runtime behavior data of the plugin on the domestically developed terminal. The runtime behavior data includes the operation record of the plugin calling the system interface of the domestically developed terminal, the interaction record of the plugin accessing the local resources of the terminal, and the rendering record of the plugin output data on the terminal interface.

[0012] In this embodiment, a desktop browser plugin for an enterprise-level collaborative office web application based on a domestically developed IT terminal is used as an example. This desktop browser plugin enables functions such as online editing of internal enterprise documents, real-time collaboration among multiple users, and secure watermark rendering of document content. When this desktop browser plugin is launched and running in the desktop browser of the domestically developed IT terminal, its runtime behavior data needs to be captured.

[0013] Step S111: Start the behavior monitoring process of the domestically developed terminal. The behavior monitoring process of the domestically developed terminal establishes a data interaction channel with the browser's plug-in running module and negotiates the data transmission protocol and data recording format through the data interaction channel.

[0014] The behavior monitoring process of the domestically developed terminal starts as an independent process. After starting, this process actively initiates a connection request to the browser's plugin runtime module. Upon receiving the request, the plugin runtime module establishes a TCP-type data interaction channel based on preset network communication rules. After the channel is established, the behavior monitoring process sends a protocol negotiation request to the plugin runtime module, which includes options for supported data transmission protocol versions and data record formats. The plugin runtime module selects the corresponding protocol version and record format based on its supported protocols and formats and returns confirmation information. The data transmission protocol specifies the packet structure, packet size limit, and retransmission mechanism for data transmission. The data record format specifies the field composition, field order, and field type of each record. For example, each record must include a behavior type field, a time field, a parameter field, and a result field, where the behavior type field is a string type, the time field is a timestamp type, the parameter field is a JSON format string type, and the result field is a JSON format string type.

[0015] Step S112: When the plugin initiates a request to call the interface of the domestically developed terminal system, the behavior monitoring process of the domestically developed terminal records the time of request initiation, the parameter information carried in the request, the result information returned by the interface and the time of result return, and organizes this information according to the negotiated data recording format to form the operation record of the plugin calling the interface of the domestically developed terminal system.

[0016] When a plugin needs to obtain the system time of the domestically developed terminal to implement the timestamp marking function for document collaboration, the plugin will initiate a request to call the domestically developed terminal's system time interface. After the behavior monitoring process captures this request, it records the time of the request initiation, which is stored as a timestamp type in the negotiated data record format; at the same time, it extracts the parameter information carried in the request, which includes the timeout setting for the interface call; after the interface is processed, the behavior monitoring process records the result information returned by the interface, which includes system time data; and records the time of the result return, which is also stored as a timestamp type. Afterwards, the behavior monitoring process, according to the negotiated data record format, organizes the above request initiation time, parameter information, result information, and result return time into an operation record, and the behavior type field of this record is marked as "system interface call".

[0017] Step S113: When the plugin initiates a request to access the terminal's local resources, the behavior monitoring process of the domestically developed terminal records the type of resource, the storage path of the resource, the permission level of the access request, and the authorization result of the terminal for the request. This information is organized according to the negotiated data recording format to form an interaction record of the plugin accessing the terminal's local resources.

[0018] When a plugin needs to access the local document storage directory of the domestically developed terminal to read local documents for online editing, the plugin initiates a request to access local resources. After capturing this request, the behavior monitoring process records the resource type as "local directory," the resource storage path (an absolute path within the domestically developed terminal's local file system), and the access permission level as "read permission." The terminal's resource management module verifies the permission for this request and returns an authorization result, which the behavior monitoring process records. Subsequently, the behavior monitoring process, according to the negotiated data recording format, organizes the above resource type, storage path, permission level, and authorization result into an interaction record, with the behavior type field of this interaction record marked as "local resource access."

[0019] Step S114: When the plugin generates output data and sends it to the terminal interface for rendering, the behavior monitoring process of the domestically developed terminal records the format, data size, rendering start time, rendering completion time, and pixel data displayed on the interface of the output data. This information is organized according to the negotiated data recording format to form the rendering record of the plugin output data on the terminal interface.

[0020] When the plugin completes online document editing and generates document content security watermark data, it sends this watermark data to the terminal interface for rendering. After capturing this rendering request, the behavior monitoring process records the output data format as "PNG image format"; the data size, stored in bytes according to the negotiated data record format; the rendering start time, which is the timestamp of the timestamp of the plugin sending the rendering request; and the rendering completion time, which is the timestamp of the timestamp of the terminal interface completing rendering. Simultaneously, it obtains the pixel data displayed on the interface through the terminal's graphics rendering interface; this pixel data is an array containing the RGB values ​​of each pixel. Then, according to the negotiated data record format, the behavior monitoring process organizes the above output data format, data size, rendering start time, rendering completion time, and pixel data into a single rendering record, with the behavior type field of this record marked as "interface rendering".

[0021] Step S115: Integrate the operation records of the plugin calling the interface of the information technology innovation terminal system, the interaction records of the plugin accessing the local resources of the terminal, and the rendering records of the plugin output data on the terminal interface in chronological order to form runtime behavior data.

[0022] The behavior monitoring process reads operation records of plugins calling the terminal system interface, interaction records of plugins accessing local terminal resources, and rendering records of plugin output data on the terminal interface from local storage. Each record contains a time field. The behavior monitoring process sorts all records in ascending order of time field value. After sorting, all records are concatenated to form runtime behavior data. This runtime behavior data is an ordered list of records, with each record arranged in chronological order.

[0023] Step S116: Add timestamps to the integrated runtime behavior data to achieve time-related traceability of each record.

[0024] The behavior monitoring process adds a timestamp to each record in the integrated runtime behavior data. This timestamp matches the time field value in the record. After adding the timestamp, when it is necessary to trace the temporal correlation of a record, the timestamp can be used to quickly locate the record's position in the runtime behavior data, as well as the records adjacent to it, thereby clarifying the chronological order and context of the behaviors corresponding to that record.

[0025] Step S120: Perform time-series correlation analysis on runtime behavior data, extract feature parameters of each behavior record, construct the interaction behavior fingerprint between the plugin and the information technology terminal, and identify nodes with interaction interruption, data transmission stagnation, and abnormal rendering results through the interaction behavior fingerprint to obtain a set of abnormal interaction nodes.

[0026] The behavior monitoring process reads runtime behavior data, which is a list of records arranged in chronological order. The process analyzes each record, extracting characteristic parameters. For example, for system interface call records, it extracts features such as call frequency, parameter length, and result return latency; for local resource access records, it extracts features such as resource access count, permission request success rate, and resource read time; and for UI rendering records, it extracts features such as rendering frame rate, pixel difference, and rendering resource consumption. After extraction, the process arranges the characteristic parameters of each record according to a preset dimensional order, forming a fingerprint fragment for each behavior record. Then, it concatenates all fingerprint fragments in chronological order to construct the interaction behavior fingerprint between the plugin and the IT terminal. Next, the process identifies nodes with interrupted interactions, stalled data transmission, and abnormal rendering results using the interaction behavior fingerprint, collecting and arranging these nodes to obtain a set of abnormal interaction nodes.

[0027] Step S121: Arrange the runtime behavior data in order of timestamps to construct a behavior time sequence, with each timestamp corresponding to a behavior record.

[0028] The behavior monitoring process reads each record from the runtime behavior data and extracts the timestamp of each record. Then, it sorts all records in ascending order of timestamp values. After sorting, all records are stored sequentially to form a behavior time-series sequence. Each timestamp in this behavior time-series sequence corresponds to a behavior record, recording the interaction behavior between the plugin and the domestically developed terminal at that timestamp.

[0029] Step S122: For each behavior record, extract feature parameters. If the behavior record is an operation record of the plugin calling the interface of the information technology terminal system, the feature parameters include interface call frequency, parameter length, and result return delay. If the behavior record is an interaction record of the plugin accessing local resources of the terminal, the feature parameters include resource access count, permission application success rate, and resource reading time. If the behavior record is a rendering record of the plugin output data on the terminal interface, the feature parameters include rendering frame rate, pixel difference, and rendering resource usage.

[0030] The behavior monitoring process iterates through each behavior record in the behavior time sequence, first determining the type of the behavior record. If the behavior record is an operation record of a plugin calling the interface of the domestically developed terminal system, the behavior monitoring process extracts the interface call frequency, which is the number of times the plugin calls the interface per unit time; extracts the parameter length, which is the number of bytes of parameter information carried in the request; and extracts the result return delay, which is the time difference between the result return time and the request initiation time. If the behavior record is an interaction record of a plugin accessing local terminal resources, the behavior monitoring process extracts the resource access count, which is the number of times the plugin accesses the resource per unit time; extracts the permission request success rate, which is the ratio of the number of successful permission requests to the total number of permission requests; and extracts the resource read time, which is the time difference between the resource read completion time and the resource access request initiation time. If the behavior record is the rendering record of the plugin output data on the terminal interface, the behavior monitoring process extracts the rendering frame rate, which is the number of rendering frames completed per unit time; extracts the pixel difference, which is the degree of difference between the rendered pixel data and the preset pixel data; and extracts the rendering resource usage, which is the amount of CPU resources and memory resources consumed during the rendering process.

[0031] Step S123: Arrange the feature parameters of each behavior record in a preset dimensional order to form a fingerprint fragment of a single behavior record, and concatenate all fingerprint fragments in chronological order to construct the interaction behavior fingerprint between the plug-in and the information technology terminal.

[0032] For each behavior record, the behavior monitoring process extracts feature parameters and arranges them according to a preset dimensional order. The preset dimensional order is as follows: for system interface call operation records, the order is interface call frequency, parameter length, and result return latency; for local resource access interaction records, the order is resource access count, permission request success rate, and resource read time; for interface rendering records, the order is rendering frame rate, pixel difference, and rendering resource consumption. After arrangement, a fingerprint fragment for each behavior record is formed. Then, the behavior monitoring process concatenates all fingerprint fragments in chronological order to construct the interaction behavior fingerprint between the plugin and the domestically developed terminal. This interaction behavior fingerprint is an ordered sequence of fingerprint fragments that records the feature changes during the interaction between the plugin and the domestically developed terminal.

[0033] Step S124: Extract the time interval parameter of adjacent fingerprint segments from the interaction behavior fingerprint, and compare the time interval parameter with the preset normal interaction time threshold range.

[0034] The behavior monitoring process traverses all fingerprint segments in the interaction behavior fingerprint. For two adjacent fingerprint segments, the difference between their timestamps is calculated, and this difference is the time interval parameter. Then, this time interval parameter is compared with a preset normal interaction time threshold range to determine whether the time interval parameter is within the normal interaction time threshold range.

[0035] Step S125: When the time interval parameter of any two adjacent fingerprint segments exceeds the preset normal interaction time threshold range, extract the behavior records corresponding to the two fingerprint segments, determine whether there is a situation where the terminal does not return a response after the plug-in operation is initiated, and if so, mark the node corresponding to the relevant operation as the node of interaction interruption.

[0036] When the behavior monitoring process detects that the time interval between any two adjacent fingerprint segments exceeds the preset normal interaction time threshold, it extracts the behavior records corresponding to those two fingerprint segments. These two behavior records are then analyzed to determine if there is a situation where the terminal did not return a response after a plugin operation was initiated. If such a situation exists, the node corresponding to the relevant operation is marked as an interaction interruption node, and relevant information about that node is recorded, such as the operation type corresponding to the node and the operation initiation time.

[0037] Step S1251: Extract two adjacent fingerprint segments whose time interval parameters exceed a preset range from the behavior time sequence, determine the time range of the behavior records corresponding to the two fingerprint segments, and record the start and end time points of the time range.

[0038] The behavior monitoring process locates two adjacent fingerprint segments whose time interval parameters exceed a preset range from the behavior time sequence, and extracts the timestamps of these two fingerprint segments. The timestamp of the preceding fingerprint segment is used as the start time point of the time range, and the timestamp of the following fingerprint segment is used as the end time point of the time range. The start and end time points are recorded.

[0039] Step S1252: Based on the starting time point, trace back to the time point of the most recent normal interaction, obtain all operation commands initiated by the plugin within that time period, and record the type of operation command, the parameters carried by the command, and the specific time when the command was initiated.

[0040] The behavior monitoring process uses the starting time point as a baseline and iterates backward through the records in the behavior time sequence to find the time point of the most recent normal interaction. Once this time point is found, all operation commands initiated by the plugin within the time period from this time point to the starting time point are retrieved. For each operation command, its type is recorded, such as system interface call command, local resource access command, etc.; the parameters carried by the command are recorded, such as interface call parameter information, resource access path information, etc.; and the specific time the command was initiated is recorded as the timestamp of the command initiation.

[0041] Step S1253: Based on the end time point, trace back to the time point when the terminal first resumed response, obtain all response data returned by the domestically developed terminal within that time period, and record the type, content, and specific time of the response data.

[0042] The behavior monitoring process uses the end time as a baseline and iterates through the records in the behavior time sequence to find the time point when the terminal first responds. Once this time point is found, all response data returned by the terminal within the time period from the end time point to this time point is retrieved. For each response data record, its type is recorded, such as response data for system interface calls, response data for local resource access, etc.; the data content is recorded, such as the result information returned by the interface, the authorization result of resource access, etc.; and the specific time of the response return is recorded as a timestamp.

[0043] Step S1254: Establish the correspondence between plug-in operation instructions and terminal response data. Match each operation instruction with time-related response data. The matching basis is the time difference between the operation instruction initiation time and the response data return time.

[0044] The behavior monitoring process matches the acquired plugin operation commands with the terminal response data, based on the time difference between the command initiation time and the response data return time. For each operation command, the time difference between its initiation time and the response data return time is calculated, and the response data with the smallest time difference within a preset range is matched with the operation command to establish a correspondence.

[0045] Step S1255: Check if there is a case where an operation instruction does not match any response data. If so, extract the behavior record corresponding to the operation instruction that does not match the response data, and record the interface type and resource access target corresponding to the operation instruction that does not match the response data.

[0046] The behavior monitoring process checks whether all plugin operation commands match the corresponding terminal response data. If any operation command does not match any response data, the behavior record corresponding to the operation command without a matching response data is extracted. Then, the interface type corresponding to the operation command is extracted from the behavior record, such as the system time interface, file storage interface, etc.; the resource access target is extracted, such as the local document storage directory, system configuration file, etc.

[0047] Step S1256: Analyze the execution flow of the operation instruction that did not match the response data, determine the position of the operation instruction that did not match the response data in the plugin's running flow, and determine the node corresponding to the position as the node where the interaction is interrupted.

[0048] The behavior monitoring process analyzes the execution flow of operation instructions that did not match response data. This execution flow is the code logic flow during plugin runtime. By analyzing the execution flow, the position of the operation instruction within the plugin's runtime process is determined, such as whether the operation instruction is executed during the plugin startup phase or the document editing phase. Then, the node corresponding to that position is identified as the node where the interaction was interrupted.

[0049] Step S1257: Add marker information to the node whose interaction was interrupted. The marker information includes the time when the node appeared, the corresponding operation instruction type, and the terminal module that did not receive a response.

[0050] The behavior monitoring process adds marker information to identified nodes where interaction is interrupted. This marker information includes the time the node appeared (a timestamp indicating the operation command was initiated), the type of the corresponding operation command (e.g., system interface call command, local resource access command), and the terminal module that did not receive a response (e.g., system interface module, resource management module). Adding this marker information facilitates subsequent analysis and processing of the node.

[0051] Step S126: Extract the transmission rate parameter of the data transmission related fingerprint fragment from the interaction behavior fingerprint, and compare the transmission rate parameter with the preset normal transmission rate threshold range.

[0052] The behavior monitoring process extracts data transmission-related fingerprint fragments from interaction behavior fingerprints, such as fingerprint fragments corresponding to local resource access interaction records and system interface call operation records. Then, it extracts transmission rate parameters from these fingerprint fragments, which represent the data transmission speed. The extracted transmission rate parameter is compared with a preset normal transmission rate threshold range to determine whether the parameter falls within this range.

[0053] Step S127: When the transmission rate parameter is lower than the lower limit of the preset normal transmission rate threshold range and the duration exceeds the preset stagnation time threshold, mark the node corresponding to the data transmission process as the node where data transmission is stagnant.

[0054] When the behavior monitoring process detects that the transmission rate parameter is lower than the preset lower limit of the normal transmission rate threshold range, and the duration of this state exceeds the preset stagnation time threshold, the node corresponding to this data transmission process is marked as a node where data transmission is stagnant. Relevant information about this node is recorded, such as the type of data being transmitted and the transmission start time.

[0055] Step S128: Extract the pixel difference parameter of the rendering related fingerprint fragment from the interaction behavior fingerprint, and compare the pixel difference parameter with the preset normal pixel difference threshold range.

[0056] The behavior monitoring process extracts fingerprint fragments related to interface rendering from the interaction behavior fingerprints, that is, fingerprint fragments corresponding to the rendering records of the interface rendering. Then, it extracts pixel difference parameters from these fingerprint fragments. These pixel difference parameters represent the degree of difference between the rendered pixel data and the preset pixel data. The extracted pixel difference parameters are compared with the preset normal pixel difference threshold range to determine whether the pixel difference parameters are within the normal pixel difference threshold range.

[0057] Step S129: When the pixel difference parameter exceeds the preset normal pixel difference threshold range, mark the node corresponding to the relevant rendering process as a node with abnormal rendering results.

[0058] When the behavior monitoring process detects that the pixel difference parameter exceeds the preset normal pixel difference threshold range, it marks the node corresponding to the relevant rendering process as a node with abnormal rendering results. It also records relevant information about this node, such as the type of rendering data it corresponds to and the rendering start time.

[0059] Step S1210: Collect all marked nodes with interrupted interaction, stalled data transmission, and abnormal rendering results. Arrange all marked nodes with interrupted interaction, stalled data transmission, and abnormal rendering results in chronological order of their appearance to form a set of abnormal interaction nodes.

[0060] The behavior monitoring process collects all marked nodes with interrupted interactions, stalled data transmissions, and abnormal rendering results. These nodes are then arranged chronologically to form a set of abnormal interaction nodes. This chronological order facilitates subsequent processing of each node.

[0061] Step S130: For each node in the abnormal interaction node set, call the preset mismatch pattern library, compare the interaction behavior fingerprint fragment corresponding to the node with the pattern features in the mismatch pattern library, determine the reason for the mismatch between the plug-in operation type and the response type of the information technology innovation terminal, and generate adaptation adjustment instructions.

[0062] The behavior monitoring process reads each node in the abnormal interaction node set and first extracts the corresponding interaction behavior fingerprint fragment. Then, it calls a pre-defined mismatch pattern library, which stores pattern features for various mismatch patterns, each pattern feature corresponding to a mismatch reason. The behavior monitoring process compares the interaction behavior fingerprint fragment corresponding to the node with the pattern features in the mismatch pattern library to find matching pattern features, thereby determining the reason for the mismatch between the plugin operation type and the domestically developed terminal response type. Based on the determined mismatch reason, a corresponding adaptation adjustment instruction is generated. This adaptation adjustment instruction is used to adjust the interaction process between the plugin and the domestically developed terminal to resolve the mismatch problem.

[0063] Step S131: Select a node from the set of abnormal interaction nodes, extract the interaction behavior fingerprint fragment corresponding to the node, and record the feature parameters in the fingerprint fragment, including operation type parameters, response status parameters and time feature parameters.

[0064] The behavior monitoring process selects a node from the set of abnormal interaction nodes and extracts the corresponding interaction behavior fingerprint fragment based on the node's position in the interaction behavior fingerprint. Then, feature parameters are extracted from this fingerprint fragment, including: an operation type parameter (indicating the type of operation initiated by the plugin); a response status parameter (indicating the response status of the terminal to the plugin operation); and a time feature parameter (indicating the time relationship between the plugin operation and the terminal response). After extraction, these feature parameters are recorded.

[0065] Step S132: Call the preset mismatch pattern library. The mismatch pattern library stores the pattern features of various mismatch patterns. Each pattern feature includes typical operation type parameters, typical response status parameters, and typical time feature parameters. Each pattern feature corresponds to a unique mismatch reason.

[0066] The behavior monitoring process calls a mismatch pattern library via a pre-defined interface. This library is stored as a database in the local storage of the domestically developed terminal. The mismatch pattern library stores the characteristics of various mismatch patterns, such as interface service exception patterns, call parameter error patterns, insufficient plugin permissions patterns, and data format incompatibility patterns. Each pattern characteristic includes typical operation type parameters, typical response status parameters, and typical time characteristic parameters. Each pattern characteristic corresponds to a unique mismatch reason; for example, the interface service exception pattern corresponds to the mismatch reason of an interface service exception, and the call parameter error pattern corresponds to the mismatch reason of incorrect call parameters.

[0067] Step S133: Compare the feature parameters of the interaction behavior fingerprint fragment corresponding to the node with the pattern features in the mismatch pattern library item by item, and calculate the parameter similarity.

[0068] The behavior monitoring process compares the feature parameters of the extracted interaction behavior fingerprint fragments corresponding to the nodes with the typical parameters of each pattern feature in the mismatch pattern library. For each parameter, its similarity with the typical parameters is calculated. Then, the similarity of all parameters is combined to obtain the overall parameter similarity between the interaction behavior fingerprint fragment corresponding to the node and the pattern feature.

[0069] Step S1331: Extract operation type parameters, response status parameters, and time feature parameters from the interaction behavior fingerprint fragment corresponding to the node. The operation type parameters, response status parameters, and time feature parameters extracted from the interaction behavior fingerprint fragment corresponding to the node are divided into numerical parameters and type parameters.

[0070] The behavior monitoring process extracts operation type parameters, response status parameters, and time feature parameters from the interaction behavior fingerprint fragments corresponding to the nodes. Then, based on the parameter type, these parameters are categorized into numerical parameters and typological parameters. Numerical parameters are parameters that can be represented numerically, such as the time difference in time feature parameters; typological parameters are parameters that represent types, such as the interface call type in operation type parameters, and the success or failure status in response status parameters.

[0071] Step S1332: For numerical parameters, obtain typical numerical parameters of the corresponding pattern features in the mismatch pattern library, calculate the absolute difference between the two, and compare the absolute difference with the preset numerical difference threshold. If the absolute difference is less than the preset numerical difference threshold, the similarity of the numerical parameter is the preset high similarity value; otherwise, it is the preset low similarity value.

[0072] For numerical parameters, the behavior monitoring process retrieves typical numerical parameters of the corresponding pattern features from the mismatch pattern library. Then, it calculates the absolute difference between the numerical parameter and the typical numerical parameter, and compares this absolute difference with a preset numerical difference threshold. If the absolute difference is less than the preset numerical difference threshold, the similarity of the numerical parameter is a preset high similarity value; otherwise, it is a preset low similarity value.

[0073] Step S1333: For type parameters, obtain typical type parameters of the corresponding pattern features in the mismatch pattern library. If the two are completely consistent, the similarity of the type parameter is the preset high similarity value; otherwise, it is the preset low similarity value.

[0074] For typological parameters, the behavior monitoring process retrieves typical typological parameters of the corresponding pattern features from the mismatch pattern library. Then, it compares the typological parameter with the typical typological parameter. If the two are completely identical, the similarity of the typological parameter is a preset high similarity value; otherwise, it is a preset low similarity value.

[0075] Step S1334: Calculate the similarity of each parameter according to the preset parameter weights. The parameter weights are set based on the influence of the parameter on the determination of the mismatch pattern. Parameters that play a key role in the determination of the mismatch pattern have high weights, while parameters that play an auxiliary role in the determination of the mismatch pattern have low weights.

[0076] The behavior monitoring process calculates the similarity of each parameter according to preset parameter weights. The parameter weights are set based on the parameter's influence on the mismatch pattern determination; for example, the operation type parameter plays a key role in mismatch pattern determination and has a higher weight, while the time feature parameter plays a supporting role and has a lower weight. During the weighted calculation, the similarity of each parameter is multiplied by its corresponding weight, and then all weighted similarities are summed to obtain the overall parameter similarity between the interaction behavior fingerprint fragment corresponding to that node and the pattern feature.

[0077] Step S1335: Sum the weighted similarities of all parameters to obtain the overall parameter similarity between the interaction behavior fingerprint fragment corresponding to the node and the feature of the pattern.

[0078] The behavior monitoring process sums the weighted similarities of all parameters to obtain the overall parameter similarity between the interaction behavior fingerprint fragment corresponding to a node and the pattern feature. This overall parameter similarity indicates the degree of matching between the interaction behavior fingerprint fragment corresponding to the node and the pattern feature; the higher the similarity, the higher the degree of matching.

[0079] Step S1336: Repeat the above steps to calculate the overall parameter similarity between the interaction behavior fingerprint fragment corresponding to the node and all pattern features in the mismatch pattern library.

[0080] The behavior monitoring process repeats steps S1331 to S1335, calculating the overall parameter similarity between the interaction behavior fingerprint fragment corresponding to the node and all pattern features in the mismatch pattern library. After calculation, the overall parameter similarity between the interaction behavior fingerprint fragment corresponding to the node and each pattern feature is obtained.

[0081] Step S134: Select the pattern feature with the highest parameter similarity, and determine the mismatch reason corresponding to the pattern feature with the highest parameter similarity as the mismatch reason of the node.

[0082] The behavior monitoring process compares the calculated interaction behavior fingerprint fragments corresponding to each node with the overall parameter similarity of each pattern feature, and selects the pattern feature with the highest parameter similarity. Then, the mismatch reason corresponding to this pattern feature is determined as the mismatch reason for that node.

[0083] Step S135: If the mismatch reason corresponding to the pattern feature with the highest parameter similarity is an interface service abnormality, then generate an adaptation adjustment instruction to restart the corresponding interface service. The adaptation adjustment instruction includes the interface identification information, the restart execution time, and the status detection steps after restart.

[0084] When the identified mismatch is due to an API service anomaly, the behavior monitoring process generates an adaptation and adjustment instruction to restart the corresponding API service. This instruction includes the API's identification information, such as the API name and ID; the restart execution time, which is a preset time after the instruction is generated; and post-restart status detection steps, such as sending test requests to check if the API is responding normally.

[0085] Step S136: If the mismatch reason corresponding to the pattern feature with the highest parameter similarity is an incorrect parameter call, then generate an adaptation adjustment instruction for the correction plugin's parameter call. The adaptation adjustment instruction includes the location of the incorrect parameter, the format requirements of the correct parameter, and the execution steps for parameter correction.

[0086] When the mismatch is determined to be caused by incorrect call parameters, the behavior monitoring process generates adaptation instructions to correct the plugin's call parameters. These instructions include the location of the erroneous parameter, such as its index in the request; the format requirements for the correct parameter, such as its type and length; and the execution steps for parameter correction, such as first reading the erroneous parameter, then modifying it according to the correct format requirements, and finally resending the request.

[0087] Step S137: If the mismatch reason corresponding to the pattern feature with the highest parameter similarity is insufficient plugin permissions, then generate an adaptation adjustment instruction to improve the access permissions of the corresponding resource of the plugin. The adaptation adjustment instruction includes the identifier of the target resource, the permission level to be improved, and the permission application process steps.

[0088] When the identified mismatch is due to insufficient plugin permissions, the behavior monitoring process generates an adaptation instruction to elevate the access permissions of the corresponding plugin resources. This adaptation instruction includes the identifier of the target resource, such as the resource path and name; the permission level to be elevated, such as from read-only permission to read-write permission; and the permission application process steps, such as first sending a permission application request to the terminal's permission management module, and then waiting for the approval result from the permission management module.

[0089] Step S138: If the mismatch reason corresponding to the pattern feature with the highest parameter similarity is data format incompatibility, then generate the adaptation adjustment instruction for the rendering data format output by the conversion plugin. The adaptation adjustment instruction includes the source data format type, the target data format type, and the specific steps for format conversion.

[0090] When the identified mismatch is due to incompatible data formats, the behavior monitoring process generates adaptation instructions for the rendering data format output by the conversion plugin. These instructions include the source data format type (e.g., PNG image format), the target data format type (e.g., JPEG image format), and the specific conversion steps (e.g., first reading the source data, then using a preset conversion algorithm to convert the source data to the target format, and finally outputting the converted data).

[0091] Step S139: Repeat the above steps until all nodes in the abnormal interaction node set generate corresponding adaptation adjustment instructions, forming an adaptation adjustment instruction set.

[0092] The behavior monitoring process repeats steps S131 to S138, processing each node in the abnormal interaction node set and generating corresponding adaptation and adjustment instructions. After processing, all adaptation and adjustment instructions are collected and stored to form an adaptation and adjustment instruction set.

[0093] Step S140: Inject the adaptation and adjustment instructions into the plugin's running process, start the behavior monitoring process of the domestically developed terminal, and run the behavior monitoring process of the domestically developed terminal synchronously with the browser's plugin running module to monitor the interaction process between the plugin and the domestically developed terminal after adjustment, record the interaction behavior fingerprint after adjustment, and form the running status data after adjustment.

[0094] The behavior monitoring process reads each adaptation adjustment instruction from the set of adaptation adjustment instructions and injects these instructions into the plugin's runtime process through a preset interface. After injection, the behavior monitoring process of the domestically developed terminal is started. This monitoring process runs synchronously with the browser's plugin runtime module. During plugin runtime, the behavior monitoring process monitors the interaction between the adjusted plugin and the domestically developed terminal in real time, records the behavior records during the interaction process, extracts feature parameters, and constructs the adjusted interaction behavior fingerprint. The adjusted interaction behavior fingerprint is associated with the corresponding adaptation adjustment instruction identifier and integrated in chronological order to form the adjusted runtime status data.

[0095] Step S141: Obtain the set of adaptation adjustment instructions, extract the abnormal interaction node corresponding to each adaptation adjustment instruction, and sort the instructions in the set of adaptation adjustment instructions according to the time order of the occurrence of the abnormal interaction nodes.

[0096] The behavior monitoring process retrieves the set of adaptation and adjustment instructions from local storage, iterates through each instruction, and extracts the abnormal interaction nodes corresponding to each instruction. Then, it sorts the instructions in the set of adaptation and adjustment instructions according to the time order in which the abnormal interaction nodes appeared, resulting in a sequence of adaptation and adjustment instructions arranged in chronological order.

[0097] Step S142: Analyze the plugin execution flow node corresponding to each adaptation adjustment instruction, and determine the injection position of the adaptation adjustment instruction in the plugin execution flow. The injection position is the operation node preceding the corresponding abnormal interaction node in the plugin execution flow.

[0098] The behavior monitoring process analyzes the plugin execution flow node corresponding to each adaptation and adjustment instruction. This node represents the position of the abnormal interaction node within the plugin's execution flow. Then, the injection point of the adaptation and adjustment instruction within the plugin's execution flow is determined. This injection point is the preceding operation node in the plugin's execution flow for the corresponding abnormal interaction node. For example, if the operation corresponding to the abnormal interaction node is a plugin call to a system interface, the injection point is the parameter preparation node before the plugin calls the system interface.

[0099] Step S143: Inject the first sorted adaptation adjustment instruction into the corresponding injection position, start the plugin's running process, and trigger the execution of the adaptation adjustment instruction when the plugin's running process reaches the injection position.

[0100] The behavior monitoring process injects the first sorted adaptation instruction into the corresponding injection point. The injection method involves modifying the plugin's runtime logic by adding the instruction execution code to the injection point. After injection, the plugin's runtime process starts. When the plugin's runtime process reaches the injection point, it triggers the execution of the adaptation instruction.

[0101] Step S144: Start the behavior monitoring process of the domestically developed terminal. The behavior monitoring process of the domestically developed terminal runs synchronously with the browser's plug-in module. The behavior monitoring process of the domestically developed terminal collects data in real time during the execution of adaptation and adjustment instructions, including instruction execution steps, step execution results, and status changes of related modules.

[0102] The behavior monitoring process starts as an independent process. After starting, it establishes a synchronous running mechanism with the browser's plugin module to ensure that the running states of the two are consistent. During the execution of adaptation and adjustment instructions, the behavior monitoring process collects the instruction execution steps in real time, such as the execution order of the instruction's sub-steps; collects the execution results of the steps, such as whether the sub-steps were executed successfully or failed; and collects the status changes of related modules, such as changes in the CPU utilization and memory usage of the plugin module.

[0103] Step S1441: The behavior monitoring process of the domestically developed terminal parses and adapts the execution steps in the adjustment instructions, decomposes the execution steps into multiple sub-steps, and each sub-step corresponds to a specific operation.

[0104] The behavior monitoring process reads the execution steps from the adaptation and adjustment instructions, which are a flow description of the instruction execution. Then, the execution steps are broken down into multiple sub-steps, each corresponding to a specific operation, such as reading parameters, modifying parameters, or sending a request. After decomposition, a sequence of sub-steps is obtained.

[0105] Step S1442: The behavior monitoring process of the domestically developed terminal assigns a unique identifier to each sub-step and records the expected execution result of each sub-step.

[0106] The behavior monitoring process assigns a unique identifier to each sub-step obtained from the decomposition. This identifier is a string consisting of the sub-step's sequence number and the operation type. Then, it records the expected execution result of each sub-step. This expected result is the result that should be returned when the sub-step executes successfully, such as a message indicating successful parameter modification or a status code indicating successful request sending.

[0107] Step S1443: When the plugin's running process executes the first sub-step, the behavior monitoring process of the domestically developed terminal records the start time of the sub-step. During the execution of the sub-step, the running data of relevant modules are collected in real time. The relevant modules include the plugin running module, the domestically developed terminal system interface module, and the terminal resource management module. The collected running data includes the module's CPU usage data, memory usage data, data transmission data, and interaction data between modules.

[0108] When the plugin's execution process performs its first sub-step, the behavior monitoring process records the start time of the sub-step, which serves as the timestamp of the sub-step's execution. During the execution of the sub-step, the behavior monitoring process collects operational data from relevant modules in real time through preset interfaces. These modules include the plugin execution module, the domestically developed terminal system interface module, and the terminal resource management module. The collected operational data includes: CPU usage data (representing the percentage of CPU used by the module); memory usage data (representing the amount of memory used by the module); data transmission data (representing the speed and size of data transmission between modules); and inter-module interaction data (representing the content of messages sent and received between modules).

[0109] Step S1444: After the sub-step is completed, the behavior monitoring process of the information technology application terminal records the end time and actual execution result of the sub-step, compares the actual execution result with the expected execution result, and determines whether the sub-step was executed successfully.

[0110] After a sub-step completes execution, the behavior monitoring process records the end time of the sub-step, which is a timestamp indicating completion. Simultaneously, it records the actual execution result, which is the result returned after the sub-step execution. Then, the actual execution result is compared with the expected execution result to determine if the sub-step executed successfully. If the actual execution result matches the expected execution result, the sub-step executed successfully; otherwise, the sub-step failed.

[0111] Step S1445: If the sub-step fails, the behavior monitoring process of the IT innovation terminal collects the error information when it fails, including the error code, error description and the module location where the error occurred.

[0112] When a sub-step fails, the behavior monitoring process collects error information through a pre-defined interface. This error information includes an error code (a number indicating the error type), an error description (a textual description of the error), and the module location where the error occurred (the module name and line number). After collection, this error information is recorded.

[0113] Step S1446: Record the identifier, start time, end time, actual execution result, running data of related modules, and error information of each sub-step into the step execution log.

[0114] The behavior monitoring process records the identifier, start time, end time, actual execution result, related module running data, and error information of each sub-step in the step execution log. The step execution log is stored in the local storage of the domestically developed terminal as a text file, facilitating subsequent analysis and viewing of the instruction execution process.

[0115] Step S1447: After all sub-steps are executed, the behavior monitoring process of the domestically developed terminal summarizes the step execution log and determines whether all sub-steps have been executed successfully. If all sub-steps have been executed successfully, it is determined that the adaptation and adjustment instruction has been executed successfully; if any sub-steps have failed to execute, it is determined that the adaptation and adjustment instruction has been partially executed or failed to execute.

[0116] After all sub-steps have been executed, the behavior monitoring process reads the step execution log and summarizes the execution results of each sub-step. It then determines whether all sub-steps executed successfully. If all sub-steps executed successfully, the adaptation and adjustment instructions are considered successfully executed; if any sub-step failed, the adaptation and adjustment instructions are considered partially executed or failed. The result is then recorded.

[0117] Step S1448: Extract the state change data of relevant modules after the adaptation and adjustment instructions are executed, including the state parameters before the module is executed, the state parameters after the execution, the enabled or disabled state of the module function, and the changes in the interaction relationship between the module and other modules.

[0118] The behavior monitoring process extracts state change data of relevant modules after the execution of adaptation and adjustment instructions. This state change data includes state parameters before module execution, such as CPU utilization and memory usage; state parameters after module execution, such as CPU utilization and memory usage; enabled or disabled status of module functions, such as whether a certain function of the module is enabled or disabled; and changes in the interaction relationship between the module and other modules, such as whether the communication frequency between the module and other modules has changed. After extraction, this state change data is recorded.

[0119] Step S1449: Integrate the step execution log with the status change data of the relevant modules as monitoring data for the adaptation and adjustment instruction execution process, and incorporate it into the post-adjustment running status data.

[0120] The behavior monitoring process integrates the step execution logs with the status change data of relevant modules. This integration involves adding the status change data to the corresponding location in the step execution logs. Once integrated, this monitoring data is incorporated into the adjusted operational status data, facilitating subsequent analysis and evaluation of the adjusted operational status.

[0121] Step S145: After the adaptation and adjustment instructions are executed, the behavior monitoring process of the IT innovation terminal continues to monitor the subsequent operation of the plugin and record new interaction records between the plugin and the IT innovation terminal, including new interface call records, new resource access records and new rendering records.

[0122] After the adaptation and adjustment instructions are executed, the behavior monitoring process continues to run, monitoring the subsequent operation of the plugin in real time. During the monitoring process, new interaction records between the plugin and the domestically developed terminal are recorded, including new interface call records, which include the time, parameters, and results of the interface call; new resource access records, which include the time, path, and permissions of the resource access; and new rendering records, which include the rendering time, data format, and pixel data.

[0123] Step S146: For the new interaction record, extract feature parameters according to the method of constructing interaction behavior fingerprint to form an adjusted interaction behavior fingerprint fragment.

[0124] The behavior monitoring process extracts feature parameters for new interaction records using a method for constructing interaction behavior fingerprints. For example, for new API call records, it extracts feature parameters such as API call frequency, parameter length, and result return latency; for new resource access records, it extracts feature parameters such as resource access count, permission request success rate, and resource read time; and for new rendering records, it extracts feature parameters such as rendering frame rate, pixel difference, and rendering resource usage. After extraction, these feature parameters are arranged in a preset dimensional order to form an adjusted interaction behavior fingerprint fragment.

[0125] Step S147: Concatenate the adjusted interaction behavior fingerprint fragments in chronological order according to the timestamp markers to form the adjusted complete interaction behavior fingerprint.

[0126] The behavior monitoring process reads the timestamps from the adjusted interaction behavior fingerprint segments and sorts all fingerprint segments in ascending order of timestamp values. After sorting, all fingerprint segments are concatenated to form the adjusted complete interaction behavior fingerprint. This complete interaction behavior fingerprint records the feature changes during the interaction between the adjusted plugin and the domestically developed terminal.

[0127] Step S148: Repeat the above steps to inject all the instructions in the adaptation and adjustment instruction set into the plugin's running process and monitor them, and collect the complete interactive behavior fingerprints after all adjustments.

[0128] The behavior monitoring process repeats steps S143 to S147, sequentially injecting all instructions from the adaptation and adjustment instruction set into the plugin's runtime flow and monitoring them. During each injection and monitoring process, new interaction records are recorded, feature parameters are extracted, and adjusted interaction behavior fingerprint fragments are formed, which are then concatenated into a complete adjusted interaction behavior fingerprint. All complete adjusted interaction behavior fingerprints are collected to obtain an adjusted interaction behavior fingerprint set.

[0129] Step S149: Associate the adjusted complete interactive behavior fingerprint with the corresponding adaptation adjustment instruction identifier, and integrate them in chronological order to form the adjusted running status data.

[0130] The behavior monitoring process associates each adjusted complete interactive behavior fingerprint with its corresponding adaptation adjustment instruction identifier by adding an instruction identifier field to the interactive behavior fingerprint. After association, all adjusted complete interactive behavior fingerprints are integrated in chronological order. This integration generates adjusted operational status data, which contains all information regarding the interaction between the adjusted plugin and the domestically developed terminal.

[0131] Step S150: Based on the interaction behavior fingerprint in the adjusted running status data, determine whether the plugin can complete all preset functions normally, extract the effective adjustment parameters in the adaptation adjustment instructions, construct the adaptation operation process, and integrate the effective adjustment parameters and the adaptation operation process to generate the final compatible adaptation solution.

[0132] The behavior monitoring process reads the complete interactive behavior fingerprint from the adjusted running status data and extracts fingerprint fragments of the plugin executing all preset functions. Then, it checks for abnormal node features in the fingerprint fragments corresponding to each preset function to determine if the plugin can complete all preset functions normally. If the adaptation adjustment is determined to be effective, valid adjustment parameters are extracted from the adaptation adjustment instruction set, the usage scenarios of these parameters are analyzed, and an adaptation operation flow is constructed. Finally, the valid adjustment parameters and the adaptation operation flow are integrated to generate the final compatible adaptation solution.

[0133] Step S151: Extract the complete interactive behavior fingerprint after adjustment from the adjusted running status data, and extract fingerprint fragments of the plugin executing all preset functions. The preset functions include the plugin's core business functions, auxiliary interactive functions, and interface display functions.

[0134] The behavior monitoring process extracts the adjusted complete interactive behavior fingerprint from the adjusted operational status data. It then iterates through each fingerprint segment, determining whether the function corresponding to each segment is a preset function. Preset functions include the plugin's core business functions, such as online document editing and real-time multi-user collaboration; auxiliary interaction functions, such as system time acquisition and resource permission request; and interface display functions, such as document content watermark rendering and interface element display. After extraction, a set of fingerprint segments representing all preset functions executed by the plugin is obtained.

[0135] Step S152: For each fingerprint segment corresponding to a preset function, check whether there are abnormal node features. The abnormal node features include node features of interrupted interaction, node features of stagnant data transmission, and node features of abnormal rendering results.

[0136] The behavior monitoring process iterates through each feature parameter in the fingerprint segment corresponding to each preset function, checking for any abnormal node features. Abnormal node features include those indicating interrupted interaction (e.g., time interval parameters exceeding the normal range and no response); those indicating stalled data transmission (e.g., transmission rate parameters below the normal range and excessive duration); and those indicating abnormal rendering results (e.g., pixel difference parameters exceeding the normal range). After the check is complete, the presence of abnormal node features in the fingerprint segment corresponding to each preset function is recorded.

[0137] Step S153: If the fingerprint segment corresponding to any preset function does not contain the above-mentioned abnormal node features, it is determined that the preset function can be completed normally; if the fingerprint segment corresponding to any preset function contains the above-mentioned abnormal node features, it is determined that the preset function has failed to be completed normally.

[0138] The behavior monitoring process evaluates the fingerprint segments corresponding to each preset function. If no abnormal node features are found in the fingerprint segment corresponding to any preset function, the preset function is considered to have completed normally; if abnormal node features are found in the fingerprint segment corresponding to any preset function, the preset function is considered to have failed to complete normally. After evaluation, the completion status of each preset function is recorded.

[0139] Step S154: Count the number of functions that can be completed normally among all preset functions. If all core business functions are completed normally and the number of abnormal functions does not exceed the preset threshold, the adaptation adjustment is determined to be effective. If not all core business functions are completed normally or the number of abnormal functions exceeds the preset threshold, return to the step of capturing runtime behavior data and re-adapt the adjustment.

[0140] The behavior monitoring process counts the number of functions that can be completed normally among all preset functions, and also counts the number of core business functions that can be completed normally. If all core business functions are completed normally and the number of abnormal functions does not exceed a preset threshold, the adaptation adjustment is determined to be effective; if not all core business functions are completed normally or the number of abnormal functions exceeds the preset threshold, the process returns to step S110 to recapture runtime behavior data and perform adaptation adjustment.

[0141] Step S155: When the adaptation adjustment is determined to be effective, extract the adjustment parameters of each instruction from the adaptation adjustment instruction set. The adjustment parameters include interface restart parameters, call parameter correction values, privilege escalation level, and data format conversion rules.

[0142] Once the adaptation adjustment is determined to be effective, the behavior monitoring process extracts the adjustment parameters for each instruction from the adaptation adjustment instruction set. These adjustment parameters include: interface restart parameters (representing information related to restarting the interface); call parameter correction values ​​(representing the corrected call parameters); privilege escalation level (representing the elevated privilege level); and data format conversion rules (representing the methods and requirements for data format conversion). After extraction, a set of effective adjustment parameters is obtained.

[0143] Step S156: Compare the changes in the interaction behavior fingerprint before and after adjustment, and retain the adjustment parameters that make the abnormal node features disappear as effective adjustment parameters.

[0144] The behavior monitoring process compares changes in interaction behavior fingerprints before and after adjustment, such as comparing time interval parameters, transmission rate parameters, and pixel difference parameters. Then, it analyzes which adjustment parameters cause abnormal node features to disappear, retaining these parameters as valid adjustment parameters. The retention method involves filtering these parameters from the adjustment parameter set and storing them in the valid adjustment parameter set.

[0145] Step S157: Analyze the usage scenarios of effective adjustment parameters, and record the abnormal interaction node type, applicable plug-in operation type, and domestic IT terminal response type corresponding to each effective adjustment parameter.

[0146] The behavior monitoring process analyzes the usage scenario of each valid adjustment parameter, which includes the applicable plugin operation type and the response type of the domestically developed terminal. For example, the interface restart parameter is applicable to abnormal interaction node types where the interface service is abnormal, the applicable plugin operation type is system interface call, and the domestically developed terminal response type is no response; the call parameter correction value is applicable to abnormal interaction node types where the call parameter is incorrect, the applicable plugin operation type is system interface call, and the domestically developed terminal response type is error response, etc. After the analysis is completed, the abnormal interaction node type, applicable plugin operation type, and domestically developed terminal response type corresponding to each valid adjustment parameter are recorded.

[0147] Step S158: Construct the adaptation operation process, which includes the execution order of adaptation adjustment instructions, the status detection steps after instruction execution, the real-time monitoring steps during plugin operation, and the emergency handling steps for abnormal situations.

[0148] The behavior monitoring process constructs an adaptation operation flow, which includes: the execution order of adaptation adjustment instructions, which is arranged according to the time of occurrence of abnormal interaction nodes; a status detection step after instruction execution, which checks whether the status of relevant modules is normal after instruction execution; a real-time monitoring step during plugin operation, which monitors the interactive behavior of the plugin during operation; and an emergency handling step for abnormal situations, which handles new abnormal situations that occur during monitoring. After construction, the adaptation operation flow is obtained.

[0149] For example, step S1581: Analyze the dependency relationship between each instruction in the adaptation and adjustment instruction set. If the execution of any instruction requires the execution result of another instruction as a prerequisite, then the instruction that needs to be executed first is listed as the pre-instruction, and the instruction that needs to be executed later is listed as the post-instruction.

[0150] The behavior monitoring process analyzes and adapts the dependencies between instructions in the instruction set. For example, if the execution of instruction A requires the result of instruction B, then instruction B is a prerequisite instruction and instruction A is a follow-up instruction. After the analysis is completed, the dependencies between instructions are determined, and the instructions are divided into prerequisite instructions and follow-up instructions.

[0151] Step S1582: Determine the overall execution order of the adaptation and adjustment instructions according to the principle of prioritizing the execution of preceding instructions and executing instructions without dependencies in the order of occurrence of the corresponding exception nodes.

[0152] The behavior monitoring process prioritizes the execution of preceding instructions and executes instructions without dependencies in the order of their corresponding anomaly occurrence times, sorting the instructions in the adaptation and adjustment instruction set. After sorting, the overall execution order of the adaptation and adjustment instructions is obtained.

[0153] Step S1583: For the status detection step after instruction execution, determine the detection objects. The detection objects include the system interface status of the domestically developed terminal, the permission status of the plug-in, and the output status after data format conversion.

[0154] The behavior monitoring process identifies the detection objects based on the status detection steps following instruction execution. These objects include the system interface status of the domestically developed terminal (indicating whether the system interface is responding normally); the permission status of plugins (indicating whether the plugin has sufficient resource access permissions); and the output status after data format conversion (indicating whether the data format conversion was successful). Once identified, a list of detection objects is obtained.

[0155] Step S1584: Specify the detection method for each type of detection object. The system interface status detection adopts the method of sending test requests and receiving responses. The plugin permission status detection adopts the method of querying data from the permission management module. The data format conversion status detection adopts the method of comparing the data formats before and after conversion.

[0156] The behavior monitoring process specifies the detection method for each type of object. For system interface status detection, a method of sending test requests and receiving responses is used; for example, sending a test request to the system interface to see if a normal response is received. For plugin permission status detection, a method of querying data from the permission management module is used; for example, sending a query request to the permission management module to obtain the plugin's permission information. For data format conversion status detection, a method of comparing the data formats before and after conversion is used; for example, comparing whether the data formats before and after conversion are consistent. Once these specifications are defined, the detection method for each type of object is obtained.

[0157] Step S1585: Determine the number of tests and the test interval for each test method. The system interface status test will perform the first test immediately after the instruction is executed, and then perform subsequent tests at preset intervals until the preset number of tests is completed.

[0158] The behavior monitoring process determines the number of checks and the check interval for each detection method. For system interface status detection, the first check is performed immediately after the command is executed, followed by subsequent checks at preset intervals until the preset number of checks is completed. For plugin permission status detection, a check is performed once after the command is executed. For data format conversion status detection, a check is performed once after the command is executed. Once determined, the number of checks and the check interval for each detection method are obtained.

[0159] Step S1586: For the real-time monitoring steps during the operation of the plugin, determine the monitoring interval according to the functional complexity of the plugin. When the plugin function includes multi-level interaction logic, set the monitoring interval that meets the preset high-frequency monitoring standard; when the plugin function only includes basic data processing, set the monitoring interval that meets the preset low-frequency monitoring standard.

[0160] The behavior monitoring process analyzes the functional complexity of plugins by monitoring real-time steps during plugin operation. If a plugin's function involves multi-level interaction logic, such as real-time multi-user collaboration involving interaction between multiple users, a monitoring interval conforming to a preset high-frequency monitoring standard is set. If a plugin's function only involves basic data processing, such as system time acquisition involving simple data reading, a monitoring interval conforming to a preset low-frequency monitoring standard is set. After setting, the real-time monitoring interval is obtained.

[0161] Step S1587: Determine the content to be monitored in real time, including the status of the interaction nodes between the plugin and the IT innovation terminal, the data transmission rate, and the interface rendering effect.

[0162] The behavior monitoring process determines the content to be monitored in real time, including the status of the interaction nodes between the plugin and the domestically developed terminal, such as whether the interaction nodes are normal or abnormal; data transmission rate, such as whether the data transmission speed is within the normal range; and interface rendering effect, such as whether the pixel data of the interface rendering is consistent with the preset. After the determination is completed, a list of real-time monitored content is obtained.

[0163] Step S1588: Construct emergency handling steps for abnormal situations. When a new abnormal node is detected, first pause the current running process of the plugin, then record the detailed information of the new abnormal node, and then compare the characteristics of the new abnormal node with the characteristics of the abnormal nodes that have been processed.

[0164] The behavior monitoring process constructs emergency handling steps for abnormal situations. When a new abnormal node is detected, the current operation of the plugin is first paused through a preset interface to prevent the abnormality from escalating. Then, detailed information about the new abnormal node is recorded, such as the operation type, operation time, and abnormal characteristics. Next, the characteristics of the new abnormal node are compared with those of previously processed abnormal nodes to check for matching features. After construction, the emergency handling steps for abnormal situations are obtained.

[0165] Step S1589: If the new abnormal node characteristics are consistent with the characteristics of the abnormal node that have been processed, then the corresponding adaptation adjustment instructions are called to process them; if the new abnormal node characteristics are inconsistent with the characteristics of the abnormal node that have been processed, then a temporary emergency plan is activated. The temporary emergency plan includes restoring the plugin to the most recent normal operating state, shutting down the abnormal module and enabling the backup module.

[0166] The behavior monitoring process evaluates the comparison results. If the characteristics of the new abnormal node match those of previously processed abnormal nodes, the corresponding adaptation and adjustment instructions are invoked for processing. If the characteristics of the new abnormal node do not match those of previously processed abnormal nodes, a temporary emergency plan is activated. The temporary emergency plan includes restoring the plugin to its most recent normal operating state, such as restoring the plugin's state through its backup mechanism; and disabling the abnormal module and enabling a backup module, such as disabling the malfunctioning module and enabling a backup module to replace its function. After processing is complete, the results are recorded.

[0167] Step S15810: Integrate the execution order of adaptation adjustment instructions, the status detection steps after instruction execution, the real-time monitoring steps during plugin operation, and the emergency handling steps for abnormal situations to form an adaptation operation process.

[0168] The behavior monitoring process integrates the execution order of adaptation and adjustment commands, the status detection steps after command execution, the real-time monitoring steps during plugin operation, and the emergency handling steps for abnormal situations. The integration method is to arrange the above steps in sequence to form a complete process. After integration, the adaptation operation process is obtained.

[0169] Step S159: Integrate the effective adjustment parameters, the application scenarios of the effective adjustment parameters, and the adaptation operation process to form the final compatible adaptation solution.

[0170] The behavior monitoring process integrates effective adjustment parameters, their application scenarios, and adaptation procedures. This integration involves adding the effective adjustment parameters and their application scenarios to the corresponding positions within the adaptation procedure. After integration, a final compatibility adaptation solution is generated and stored as a document in the local storage of the domestically developed terminal for easy viewing and use later.

[0171] Step S1510: Add a version identifier and generation time to the final compatible adaptation solution. The version identifier and generation time are used for the traceability management of the solution.

[0172] The behavior monitoring process adds a version identifier and generation time to the final compatible adaptation solution. The version identifier is a unique identifier for the solution, such as the solution's version number; the generation time is the timestamp of the solution's generation. After adding these, it is convenient to trace and manage the solution later, such as viewing the solution's version history, generation time, and other information.

[0173] Based on the same inventive concept, please refer to Figure 2 This paper shows a schematic block diagram of a desktop browser plugin compatibility adaptation system 100 based on a domestically developed terminal web application, which is used to execute the above-described desktop browser plugin compatibility adaptation method based on a domestically developed terminal web application. The desktop browser plugin compatibility adaptation system 100 based on a domestically developed terminal web application may include a communication unit 110, a machine-readable storage medium 120, and a processor 130.

[0174] In this embodiment, both the machine-readable storage medium 120 and the processor 130 are located in the desktop browser plugin compatibility adaptation system 100 based on the web application of the domestically developed terminal and are separately configured. However, it should be understood that the machine-readable storage medium 120 may also be independent of the desktop browser plugin compatibility adaptation system 100 based on the web application of the domestically developed terminal and can be accessed by the processor 130 through a bus interface. Alternatively, the machine-readable storage medium 120 may also be integrated into the processor 130 and can communicate and interact with external systems through the communication unit 110.

[0175] The processor 130 is the control center of the desktop browser plugin compatibility system 100 based on the domestically developed terminal web application. It connects various parts of the system 100 via various interfaces and lines. By running or executing software programs and / or modules stored in the machine-readable storage medium 120, and by calling data stored in the machine-readable storage medium 120, it performs various functions and processes data of the system 100, thereby providing overall monitoring of the system. Optionally, the processor 130 may include one or more processing cores; for example, the processor 130 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may also not be integrated into the processor. The machine-readable storage medium 120 is used to store machine-executable instructions for executing the scheme of this application, and the processor 130 is used to execute the machine-executable instructions stored in the machine-readable storage medium 120 to implement the desktop browser plugin compatibility adaptation method based on the domestically developed terminal web application provided in the aforementioned method embodiments.

[0176] It should be noted that, in order to simplify the description of the present invention and thus help to understand one or more embodiments of the invention, multiple features may sometimes be grouped into one embodiment, drawing or description thereof in the foregoing description of the embodiments of the present invention.

Claims

1. A method for desktop browser plugin compatibility adaptation based on web applications of domestically developed terminals, characterized in that, The method includes: Capture runtime behavior data of the plugin on the domestically developed terminal. The runtime behavior data includes operation records of the plugin calling the system interface of the domestically developed terminal, interaction records of the plugin accessing local resources of the terminal, and rendering records of the plugin output data on the terminal interface. Perform time-series correlation analysis on runtime behavior data, extract feature parameters of each behavior record, construct the interaction behavior fingerprint between the plugin and the domestically developed terminal, and identify nodes with interaction interruption, data transmission stagnation, and abnormal rendering results through the interaction behavior fingerprint to obtain a set of abnormal interaction nodes. For each node in the abnormal interaction node set, a preset mismatch pattern library is called to compare the interaction behavior fingerprint fragment corresponding to the node with the pattern features in the mismatch pattern library to determine the reason for the mismatch between the plug-in operation type and the response type of the domestic innovation terminal, and generate adaptation adjustment instructions. The adaptation and adjustment instructions are injected into the plugin's running process, and the behavior monitoring process of the domestically developed terminal is started. The behavior monitoring process of the domestically developed terminal runs synchronously with the browser's plugin running module, monitors the interaction process between the plugin and the domestically developed terminal after adjustment, records the fingerprint of the interaction behavior after adjustment, and forms the running status data after adjustment. Based on the interaction behavior fingerprint in the adjusted running status data, it is determined whether the plugin can complete all the preset functions normally, the effective adjustment parameters in the adaptation adjustment instructions are extracted, the adaptation operation process is constructed, and the effective adjustment parameters and the adaptation operation process are integrated to generate the final compatible adaptation solution. The process involves using interaction behavior fingerprints from the adjusted running status data to determine whether the plugin can successfully complete all preset functions, extracting valid adjustment parameters from the adaptation adjustment instructions, constructing an adaptation operation flow, and integrating the valid adjustment parameters with the adaptation operation flow to generate a final compatible adaptation solution, including: Extract the complete interactive behavior fingerprint after adjustment from the adjusted running status data, and extract fingerprint fragments of the plugin executing all preset functions. The preset functions include the plugin's core business functions, auxiliary interactive functions, and interface display functions. For each preset function's corresponding fingerprint segment, check whether there are any abnormal node features. The abnormal node features include node features of interrupted interaction, node features of stagnant data transmission, and node features of abnormal rendering results. If the fingerprint segment corresponding to any preset function does not contain the above-mentioned abnormal node features, then the preset function is judged to be able to complete normally; if the fingerprint segment corresponding to any preset function contains the above-mentioned abnormal node features, then the preset function is judged to be unable to complete normally. The number of functions that can be completed normally among all preset functions is counted. If all core business functions are completed normally and the number of abnormal functions does not exceed the preset threshold, the adaptation adjustment is determined to be effective. If not all core business functions are completed normally or the number of abnormal functions exceeds the preset threshold, the process returns to the step of capturing runtime behavior data and the adaptation adjustment is performed again. When the adaptation adjustment is determined to be effective, the adjustment parameters of each instruction are extracted from the adaptation adjustment instruction set. The adjustment parameters include interface restart parameters, call parameter correction values, privilege escalation level and data format conversion rules. By comparing the changes in the interactive behavior fingerprints before and after adjustment, the adjustment parameters that make the abnormal node features disappear are retained as effective adjustment parameters. Analyze the usage scenarios of effective adjustment parameters, and record the abnormal interaction node type, applicable plug-in operation type, and domestic IT terminal response type corresponding to each effective adjustment parameter; The adaptation operation process is constructed, which includes the execution order of adaptation adjustment instructions, the status detection steps after instruction execution, the real-time monitoring steps during plugin operation, and the emergency handling steps for abnormal situations. The effective adjustment parameters, the application scenarios of the effective adjustment parameters, and the adaptation operation process are integrated to form the final compatibility and adaptation solution. Add a version identifier and generation time to the final compatible adaptation solution. The version identifier and generation time are used for the traceability management of the solution.

2. The desktop browser plugin compatibility and adaptation method based on domestically developed terminal web applications according to claim 1, characterized in that, The capture plugin's runtime behavior data on the domestically developed IT terminal includes: The behavior monitoring process of the domestically developed terminal is initiated. The behavior monitoring process of the domestically developed terminal establishes a data interaction channel with the browser's plug-in running module and negotiates the data transmission protocol and data recording format through the data interaction channel. When a plugin initiates a request to call the interface of the domestically developed terminal system, the behavior monitoring process of the domestically developed terminal records the time when the request is initiated, the parameter information carried in the request, the result information returned by the interface and the time when the result is returned, and organizes this information according to the negotiated data recording format to form an operation record of the plugin calling the interface of the domestically developed terminal system. When a plugin initiates a request to access local resources on the terminal, the behavior monitoring process of the domestically developed terminal records the type of resource, the storage path of the resource, the permission level of the access request, and the authorization result of the terminal for the request. This information is organized according to the negotiated data recording format to form an interaction record of the plugin accessing local resources on the terminal. When the plugin generates output data and sends it to the terminal interface for rendering, the behavior monitoring process of the domestically developed terminal records the format, data size, rendering start time, rendering completion time, and pixel data displayed on the interface of the output data. This information is organized according to the negotiated data recording format to form the rendering record of the plugin output data on the terminal interface. The operation records of the plugin calling the interface of the information technology innovation terminal system, the interaction records of the plugin accessing the local resources of the terminal, and the rendering records of the plugin output data on the terminal interface are integrated in chronological order to form runtime behavior data; Add timestamps to the integrated runtime behavior data to enable time-related tracking of each record.

3. The desktop browser plugin compatibility and adaptation method based on domestically developed terminal web applications according to claim 1, characterized in that, The process involves performing time-series correlation analysis on runtime behavior data, extracting feature parameters for each behavior record, constructing an interaction behavior fingerprint between the plugin and the domestically developed terminal, and identifying nodes with interaction interruptions, data transmission stagnation, and abnormal rendering results through the interaction behavior fingerprint. This yields a set of abnormal interaction nodes, including: Arrange runtime behavior data in timestamp order to construct a behavior time sequence, with each timestamp corresponding to a behavior record; For each behavior record, feature parameters are extracted. If the behavior record is an operation record of the plugin calling the interface of the domestically developed terminal system, the feature parameters include interface call frequency, parameter length, and result return delay. If the behavior record is an interaction record of the plugin accessing local resources of the terminal, the feature parameters include resource access count, permission application success rate, and resource reading time. If the behavior record is a rendering record of the plugin output data on the terminal interface, the feature parameters include rendering frame rate, pixel difference, and rendering resource consumption. The feature parameters of each behavior record are arranged in a preset dimensional order to form a fingerprint fragment of a single behavior record. All fingerprint fragments are then linked together in chronological order to construct the interactive behavior fingerprint between the plugin and the information technology innovation terminal. Extract the time interval parameter of adjacent fingerprint segments from the interaction behavior fingerprint, and compare the time interval parameter with the preset normal interaction time threshold range; When the time interval parameter of any two adjacent fingerprint segments exceeds the preset normal interaction time threshold range, the behavior records corresponding to the two fingerprint segments are extracted to determine whether there is a situation where the terminal does not return a response after the plug-in operation is initiated. If so, the node corresponding to the relevant operation is marked as the node of interaction interruption. The transmission rate parameter of the data transmission related fingerprint fragment is extracted from the interaction behavior fingerprint, and the transmission rate parameter is compared with the preset normal transmission rate threshold range. When the transmission rate parameter is lower than the lower limit of the preset normal transmission rate threshold range and the duration exceeds the preset stagnation time threshold, the node corresponding to the data transmission process is marked as the node where data transmission is stagnant. Extract the pixel difference parameter of the rendering related fingerprint fragment from the interaction behavior fingerprint, and compare the pixel difference parameter with the preset normal pixel difference threshold range; When the pixel difference parameter exceeds the preset normal pixel difference threshold range, the node corresponding to the relevant rendering process is marked as a node with abnormal rendering results; Collect all marked nodes with interrupted interaction, stalled data transmission, and abnormal rendering results. Arrange all marked nodes with interrupted interaction, stalled data transmission, and abnormal rendering results in chronological order of their appearance to form a set of abnormal interaction nodes.

4. The desktop browser plugin compatibility and adaptation method based on domestically developed terminal web applications according to claim 3, characterized in that, The step involves extracting the behavior records corresponding to the two fingerprint fragments and determining whether there is a situation where the terminal does not return a response after a plugin operation is initiated. If so, the node corresponding to the operation is marked as a node where the interaction is interrupted, including: Extract two adjacent fingerprint segments whose time interval parameters exceed a preset range from the behavior time sequence, determine the time range of the behavior record corresponding to the two fingerprint segments, and record the start and end time points of the time range. Based on the starting time, trace back to the time of the most recent normal interaction, obtain all operation commands initiated by the plugin within that time period, and record the type of operation command, the parameters carried by the command, and the specific time when the command was initiated. Based on the end time, trace back to the time when the terminal first responded, obtain all response data returned by the domestically developed terminal within that time period, and record the type, content and specific time of the response data. Establish a correspondence between plug-in operation commands and terminal response data, and match each operation command with time-related response data. The matching basis is the time difference between the operation command initiation time and the response data return time. Check if there are any operation instructions that do not match any response data. If so, extract the behavior record corresponding to the operation instruction that does not match the response data, and record the interface type and resource access target corresponding to the operation instruction that does not match the response data. Analyze the execution flow of the operation instruction that did not match the response data, determine the position of the operation instruction that did not match the response data in the plugin's running flow, and identify the node corresponding to that position as the node where the interaction was interrupted; Add a marker to the node where the interaction is interrupted. The marker includes the time the node appeared, the corresponding operation command type, and the terminal module that did not receive a response.

5. The desktop browser plugin compatibility and adaptation method based on domestically developed terminal web applications according to claim 1, characterized in that, For each node in the abnormal interaction node set, a preset mismatch pattern library is invoked. The interaction behavior fingerprint fragment corresponding to the node is compared with the pattern features in the mismatch pattern library to determine the reason for the mismatch between the plug-in operation type and the response type of the domestically developed terminal, and an adaptation adjustment instruction is generated, including: Select a node from the set of abnormal interaction nodes, extract the interaction behavior fingerprint fragment corresponding to the node, and record the feature parameters in the fingerprint fragment, including operation type parameters, response status parameters and time feature parameters; Call the preset mismatch pattern library. The mismatch pattern library stores the pattern characteristics of various mismatch patterns. Each pattern characteristic includes typical operation type parameters, typical response status parameters and typical time characteristic parameters, and each pattern characteristic corresponds to a unique mismatch reason. The feature parameters of the interaction behavior fingerprint fragment corresponding to the node are compared with the typical parameters of each pattern feature in the mismatch pattern library one by one, and the parameter similarity is calculated. Select the pattern feature with the highest parameter similarity, and determine the mismatch reason corresponding to the pattern feature with the highest parameter similarity as the mismatch reason of the node; If the mismatch reason corresponding to the pattern feature with the highest parameter similarity is an interface service abnormality, an adaptation adjustment instruction to restart the corresponding interface service is generated. The adaptation adjustment instruction includes the interface identification information, the restart execution time, and the status detection steps after restart. If the mismatch corresponding to the pattern feature with the highest parameter similarity is due to an incorrect parameter call, then an adaptation adjustment instruction for the correction plugin's parameter call will be generated. The adaptation adjustment instruction includes the location of the incorrect parameter, the format requirements of the correct parameter, and the execution steps for parameter correction. If the mismatch corresponding to the pattern feature with the highest parameter similarity is due to insufficient plugin permissions, then an adaptation adjustment instruction to improve the access permissions of the corresponding plugin resources is generated. The adaptation adjustment instruction includes the identifier of the target resource, the permission level to be improved, and the permission application process steps. If the mismatch corresponding to the pattern feature with the highest parameter similarity is due to data format incompatibility, then the conversion plugin will generate an adaptation adjustment instruction for the rendered data format. The adaptation adjustment instruction includes the source data format type, the target data format type, and the specific steps for format conversion. Repeat the above steps until all nodes in the abnormal interaction node set have generated corresponding adaptation adjustment instructions, forming an adaptation adjustment instruction set.

6. The desktop browser plugin compatibility and adaptation method based on domestically developed terminal web applications according to claim 5, characterized in that, The step of comparing the feature parameters of the interaction behavior fingerprint fragment corresponding to the node with the typical parameters of each pattern feature in the mismatch pattern library item by item, and calculating the parameter similarity, includes: The operation type parameters, response status parameters, and time feature parameters are extracted from the interaction behavior fingerprint fragments corresponding to the nodes. The operation type parameters, response status parameters, and time feature parameters extracted from the interaction behavior fingerprint fragments corresponding to the nodes are divided into numerical parameters and type parameters. For numerical parameters, obtain typical numerical parameters of the corresponding pattern features in the mismatch pattern library, calculate the absolute difference between the two, and compare the absolute difference with the preset numerical difference threshold. If the absolute difference is less than the preset numerical difference threshold, the similarity of the numerical parameter is the preset high similarity value; otherwise, it is the preset low similarity value. For type parameters, obtain typical type parameters of the corresponding pattern features in the mismatch pattern library. If the two are completely consistent, the similarity of the type parameter is the preset high similarity value; otherwise, it is the preset low similarity value. The similarity of each parameter is calculated in a weighted manner according to the preset parameter weights. The parameter weights are set according to the influence of the parameter on the determination of the mismatch pattern. The parameters that play a key role in the determination of the mismatch pattern have high weights, while the parameters that play an auxiliary role in the determination of the mismatch pattern have low weights. The weighted similarity of all parameters is summed to obtain the overall parameter similarity between the interaction behavior fingerprint fragment corresponding to the node and the feature of the pattern. Repeat the above steps to calculate the overall parameter similarity between the interaction behavior fingerprint fragment corresponding to the node and all pattern features in the mismatch pattern library.

7. The desktop browser plugin compatibility and adaptation method based on domestically developed terminal web applications according to claim 1, characterized in that, The process of injecting adaptation and adjustment instructions into the plugin's operation flow initiates the behavior monitoring process of the domestically developed terminal. This behavior monitoring process runs synchronously with the browser's plugin execution module, monitoring the interaction between the adjusted plugin and the domestically developed terminal, recording the adjusted interaction behavior fingerprint, and forming adjusted operational status data, including: Obtain the set of adaptation and adjustment instructions, extract the abnormal interaction nodes corresponding to each adaptation and adjustment instruction, and sort the instructions in the set of adaptation and adjustment instructions according to the time order of the occurrence of abnormal interaction nodes. Analyze the plugin execution flow nodes corresponding to each adaptation adjustment instruction, determine the injection position of the adaptation adjustment instruction in the plugin execution flow, and the injection position is the operation node before the corresponding abnormal interaction node in the plugin execution flow. The first sorted adaptation adjustment instruction is injected into the corresponding injection position, the plugin's running process is started, and the adaptation adjustment instruction is executed when the plugin's running process reaches the injection position. The behavior monitoring process of the domestically developed terminal is started. The behavior monitoring process of the domestically developed terminal runs synchronously with the browser's plug-in module. The behavior monitoring process of the domestically developed terminal collects data in real time during the execution of adaptation and adjustment instructions, including instruction execution steps, step execution results and status changes of related modules. After the adaptation and adjustment instructions are executed, the behavior monitoring process of the domestically developed terminal continues to monitor the subsequent operation of the plugin and record new interaction records between the plugin and the domestically developed terminal, including new interface call records, new resource access records and new rendering records. For new interaction records, feature parameters are extracted according to the method of constructing interaction behavior fingerprints to form adjusted interaction behavior fingerprint fragments; Based on the timestamp, the adjusted interactive behavior fingerprint fragments are concatenated in chronological order to form the adjusted complete interactive behavior fingerprint. Repeat the above steps to inject all the instructions in the adaptation and adjustment instruction set into the plugin's runtime process and monitor them, collecting fingerprints of all the complete interactive behaviors after adjustment; The adjusted complete interactive behavior fingerprint is associated with the corresponding adaptation adjustment instruction identifier and integrated in chronological order to form the adjusted running status data.

8. The desktop browser plugin compatibility and adaptation method based on domestically developed terminal web applications according to claim 7, characterized in that, The behavior monitoring process of the domestically developed terminal collects data in real time during the execution of adaptation and adjustment instructions, including: The behavior monitoring process of the domestically developed terminal analyzes and adapts the execution steps in the adjustment instructions, decomposes the execution steps into multiple sub-steps, and each sub-step corresponds to a specific operation. The behavior monitoring process of the domestically developed terminal assigns a unique identifier to each sub-step and records the expected execution result of each sub-step; When the plugin's running process executes the first sub-step, the behavior monitoring process of the domestically developed terminal records the start time of the sub-step. During the execution of the sub-step, the running data of relevant modules are collected in real time. The relevant modules include the plugin running module, the domestically developed terminal system interface module, and the terminal resource management module. The collected running data includes the module's CPU usage data, memory usage data, data transmission data, and interaction data between modules. After the sub-step is completed, the behavior monitoring process of the domestically developed terminal records the end time and actual execution result of the sub-step, compares the actual execution result with the expected execution result, and determines whether the sub-step was executed successfully. If a sub-step fails to execute, the behavior monitoring process of the IT innovation terminal will collect the error information when the failure occurs, including the error code, error description, and the module location where the error occurred. Record the identifier, start time, end time, actual execution result, running data of related modules, and error information of each sub-step in the step execution log; After all sub-steps are completed, the behavior monitoring process of the domestic IT terminal summarizes the step execution logs and determines whether all sub-steps have been executed successfully. If all sub-steps have been executed successfully, it is determined that the adaptation and adjustment instructions have been executed successfully; if any sub-steps have failed to execute, it is determined that the adaptation and adjustment instructions have been partially executed or have failed to execute. Extract the state change data of relevant modules after the adaptation and adjustment command is executed, including the state parameters before the module is executed, the state parameters after the execution, the enabled or disabled state of the module function, and the changes in the interaction relationship between the module and other modules; The step execution logs are integrated with the status change data of related modules and used as monitoring data for the adaptation and adjustment command execution process, which is then incorporated into the post-adjustment running status data.

9. A desktop browser plugin compatibility and adaptation system based on domestically developed mobile terminal web applications, characterized in that, include: processor; A machine-readable storage medium for storing machine-executable instructions of the processor; The processor is configured to execute the desktop browser plugin compatibility adaptation method based on any one of claims 1 to 8 by executing the machine-executable instructions.

Images