Terminal application state intelligent sensing and dynamic repairing method, device and medium

Abstract

The invention discloses a terminal application state intelligent sensing and dynamic repairing method and device and a medium, and the method comprises the steps: monitoring log crash information generated by a terminal application in real time to extract corresponding crash event data, and collecting real-time operation state data of the terminal application; uploading the crash event data to the large model platform for intelligent analysis, and receiving a preliminary repair suggestion returned by the large model platform; performing correlation analysis on the crash event data and the real-time operation state data to determine a hot repair scheme based on a correlation analysis result and the preliminary repair suggestion, and generating a hot repair packet according to the hot repair scheme; and issuing the hot repair package to the terminal application through the update channel, and automatically loading and installing the hot repair package at the background of the terminal application, so as to complete dynamic repair of the crash event under the condition that the terminal application runs without interruption.

Description

Technical Field

[0001] This application relates to the technical field of crash handling, and in particular, to a method, device, and medium for intelligent perception of terminal application status and dynamic repair. Background Art

[0002] With the popularization of intelligent terminal devices and the complexity of mobile applications, the stability of terminal applications and user experience have become the core issues of common concern to developers and users. Problems such as frequent crashes, freezes, and resource anomalies that occur during the operation of applications not only reduce user satisfaction but may also lead to the interruption of critical services. Traditional solutions mostly rely on users' active feedback or basic log collection mechanisms. Users often give up feedback due to cumbersome operations, making it difficult for developers to obtain effective crash information in a timely manner. Even if some applications have the function of automatically collecting crash logs, in the analysis and processing of logs, there is often a lack of systematicness and intelligence. The screening and analysis of massive data still require manual intervention, which is inefficient and prone to missing key clues.

[0003] In the prior art, log analysis tools are usually limited to simple classification and statistics, lacking intelligent mining of the deep associations of crash events. For example, the correlation between crash logs and the running state of the device is often ignored, making it difficult to accurately locate the root cause of the problem. When an application is abnormal in a specific device or network environment, developers cannot quickly distinguish whether it is due to code defects, device compatibility issues, or external environmental interference, resulting in an extended repair cycle. In addition, most log analysis systems do not introduce automated intelligent models and rely on manual experience to judge crash patterns, further reducing the timeliness and accuracy of problem-solving.

[0004] At the level of dynamic repair, traditional solutions mostly adopt methods such as version update or downtime maintenance, which seriously affect the coherence of the user experience. Even if some technologies attempt to perform partial updates through hotfixes, the generation and distribution of repair packages often lack intelligent guidance, resulting in insufficient pertinence of the repair plan and even introducing new problems. At the same time, existing hotfix technologies do not fully combine the correlation analysis of the real-time state of the device and the crash scenario, and the repair process is blind, making it difficult to achieve accurate and seamless dynamic repair effects. Summary of the Invention

[0005] Embodiments of this application provide a method, device, and medium for intelligent perception of terminal application status and dynamic repair to solve the above technical problems.

[0006] On the one hand, embodiments of this application provide a method for intelligent perception of terminal application status and dynamic repair, including: Real-time monitoring of the log crash information generated by the terminal application to extract corresponding crash event data, and collecting the real-time running state data of the terminal application; Upload the crash event data to a large model platform for intelligent analysis and receive preliminary repair suggestions returned by the large model platform; Perform correlation analysis on the crash event data and the real-time running status data, determine a hotfix solution based on the correlation analysis results and the preliminary repair suggestions, and generate a hotfix package according to the hotfix solution; Send the hotfix package to the terminal application through an update channel, and automatically load and install the hotfix package in the background of the terminal application to complete the dynamic repair of the crash event without interruption of the terminal application.

[0007] In an implementation manner of the present application, collecting the real-time running status data of the terminal application specifically includes: Call the system interface to obtain the real-time running status data of the terminal application; the real-time running status data includes CPU usage rate, memory occupancy rate, and network connection status; Monitor the memory occupancy of the terminal application through the memory management interface to record the memory leak rate and the remaining available memory capacity; Align the timestamps in the real-time running status data and the crash event data to establish a mapping relationship between the device status and the crash event.

[0008] In an implementation manner of the present application, real-time monitoring of the log crash information generated by the terminal application to extract the corresponding crash event data specifically includes: Embed log collection code in the terminal application to collect the log information generated during the running of the terminal application to continuously record user operation behaviors and system state change events; Store the log information in segments according to a preset method, and start a log analysis thread to periodically read the segmented log files; Parse the file information in the log file through lexical analysis technology and syntactic analysis technology, extract key data, and construct a corresponding crash event description table based on the key data; the key data includes crash time, trigger path, and associated function stack information.

[0009] In an implementation manner of the present application, uploading the crash event data to a large model platform for intelligent analysis specifically includes: Input the crash event description table and associated device status data into a pre-trained neural network model to identify the similarity between the crash event and historical faults, and compare several similarities with a preset similarity threshold respectively; Locate the problem code segment with potential defects in the function call chain corresponding to the crash event, and generate preliminary repair suggestions for the problem code segment based on historical faults with a similarity exceeding the preset similarity threshold; the preliminary repair suggestions include the location of the problem code segment and the repair priority order.

[0010] In an implementation manner of the present application, the correlation analysis of the crash event data and the real-time running state data specifically includes: According to the crash time in the crash event data, determine whether the CPU usage rate corresponding to the crash time exceeds a preset threshold, and when the crash event coincides with the time period when the CPU usage rate exceeds the preset threshold, determine that the cause of the crash event is resource overload; When the crash event is associated with a sudden increase in network latency or a sharp drop in bandwidth within a preset time period, determine that the cause of the crash is an abnormal network environment. If the crash event is not associated with an abnormal device state, mark the cause of the crash as a code logic defect; In the case where the cause of the crash is associated with abnormal device resources, trigger a warning signal based on a preset resource threshold and generate a corresponding warning message.

[0011] In an implementation manner of the present application, generating a hotfix package according to the hotfix solution specifically includes: Compare the differences between the problem code segment and the standard code segment corresponding to the location of the problem code segment to extract code patches; the code patches represent the code segments corresponding to the parts to be modified; Delete redundant data in the updated content of the resource file to compress the updated content of the resource file; Generate a hotfix package based on the code patches and the compressed updated content of the resource file, and embed version verification information and an installation script in the hotfix package.

[0012] In an implementation manner of the present application, automatically load and install the hotfix package in the background of the terminal application to complete the dynamic repair of the crash event without interruption of the terminal application running, specifically including: Automatically load the hotfix package in the terminal application, and verify the hotfix package based on the embedded version verification information to determine whether the hotfix package is compatible with the version of the terminal application; After the verification passes, trigger the installation process to replace the problem code segment in the memory during the running of the terminal application through the class loading mechanism based on the installation script; Update the cache of the resource file based on the compressed updated content of the resource file in the hotfix package, and record the corresponding repair log.

[0013] In one implementation of the present application, after completing the dynamic repair of a crash event without interruption of the terminal application running, the method further includes: Re - monitor the application running state corresponding to the repaired terminal application; when it is detected that the same crash event is triggered again, upgrade the warning level of the corresponding crash event and trigger a manual intervention process; According to the repair effect of the crash event, dynamically adjust the training data set of the large - model platform to optimize the generation strategy of repair suggestions.

[0014] On the other hand, an embodiment of the present application further provides a device for intelligent perception and dynamic repair of terminal application status, the device includes: At least one processor; And a memory communicatively connected to the at least one processor; Wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute a method for intelligent perception and dynamic repair of terminal application status as described above.

[0015] On the other hand, an embodiment of the present application further provides a non - volatile computer storage medium storing computer - executable instructions, and when the computer - executable instructions are executed, a method for intelligent perception and dynamic repair of terminal application status as described above is implemented.

[0016] The embodiment of the present application provides a method, a device and a medium for intelligent perception and dynamic repair of terminal application status, including at least the following beneficial effects: Through embedded log collection and real - time monitoring of device status, automatically capture crash events and their associated device resource data, and quickly locate the problem code segment and repair priority based on the large - model platform, avoiding the delay and error of manual intervention and greatly shortening the problem diagnosis cycle; through the correlation analysis of crash events and device running states, it is possible to clearly distinguish different crash causes such as code defects, device compatibility problems and external environment interference. Combined with the precise directional generation of hot - fix packages and the background seamless installation mechanism, the repair can be completed without the user's perception, completely avoiding the damage to the user experience caused by traditional downtime updates; continuously monitor the repair effect and feedback it to the large - model platform, dynamically adjust the training data and repair strategy, and form a closed - loop process of perception - analysis - repair - verification, which not only improves the reliability of single - time repair, but also continuously optimizes the generalization ability of the model through data accumulation, ensuring the stability and adaptability of the system's long - term operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings described herein are used to provide a further understanding of the present application, and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application, and do not constitute an improper limitation of the present application. In the drawings: Figure 1 It is a schematic flow chart of a method for intelligent perception and dynamic repair of the terminal application status provided by an embodiment of the present application; Figure 2 It is a schematic internal structure diagram of a device for intelligent perception and dynamic repair of the terminal application status provided by an embodiment of the present application. Detailed implementation manners

[0018] To make the objectives, technical solutions, and advantages of the present application clearer, the technical solutions of the present application will be clearly and completely described below in conjunction with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0019] The technical solutions provided by the embodiments of the present application will be described in detail below in conjunction with the drawings.

[0020] Figure 1 It is a schematic flow chart of a method for intelligent perception and dynamic repair of the terminal application status provided by an embodiment of the present application.

[0021] The implementation of the analysis method involved in the embodiments of the present application can be a terminal device or a server, and the present application does not make any special restrictions in this regard. For the convenience of understanding and description, the following embodiments will be described in detail taking the server as an example.

[0022] It should be noted that the server can be a single device or a system composed of multiple devices, that is, a distributed server, and the present application does not make specific limitations in this regard.

[0023] As Figure 1 shown, a method for intelligent perception and dynamic repair of the terminal application status provided by an embodiment of the present application includes: Step 101, continuously monitor the log crash information generated by the terminal application to extract the corresponding crash event data, and collect the real-time running status data of the terminal application.

[0024] This application constructs a complete log monitoring system that can monitor the log crash information generated by terminal applications in real time. Different from traditional passive waiting for user feedback or simple log collection, this application can actively parse the logs in all aspects. By deeply mining the key data in the logs and using advanced statistical analysis algorithms, a detailed crash statistics path is generated. For example, it can accurately record which operation steps caused the crash when the application is executing a specific function and what the specific code execution path is.

[0025] It should be noted that embedding log collection code in the terminal application can ensure that various operation behaviors, system state changes, etc. are recorded in the log file in real time during the application's operation. The code captures user operation behaviors and system state change events through Hook technology. It should be noted that Hook technologies such as function interception or event listening capture user operation behaviors such as page jumps and button clicks, and system state change events such as memory allocation failures and network request timeouts. Exemplarily, when the user clicks the payment function, the log code will record the operation time, input parameters, and the triggered interface call chain.

[0026] Specifically, the log information is segmented and stored according to a preset time window, such as periodic segmentation or a file capacity threshold, so as to avoid parsing delays caused by an overly large single log file. For example, when the user opens a certain function module in the terminal application, performs data input or output operations, or events such as sending and receiving network requests occur, corresponding detailed information such as the operation time and parameters will be recorded in the log.

[0027] The system starts a dedicated log analysis thread to regularly read the log file and uses techniques such as lexical analysis and syntactic analysis to parse the text information in the log and extract key data. For example, for crash logs, the timestamp of the crash, the page where the application is located at the time of the crash, the function stack information called, etc. will be key-extracted. Through the collation and analysis of this information, a crash event description table for detailed description of the crash event is constructed. It can be understood that the crash event description table is stored in a structured data format for subsequent analysis and transmission.

[0028] Run big data analysis algorithms to statistically analyze the parsed log data. Taking crash logs as an example, count the number of occurrences of different crash reasons, and then calculate the statistical percentage of crashes caused by each problem. At the same time, generate a crash statistics path through methods such as association analysis.

[0029] Meanwhile, this application is not limited to the analysis of crash event data, but also comprehensively analyzes important information such as the CPU and network of the terminal device. Using the system interface provided by the terminal device, device information such as CPU, network, and memory is obtained in real time. For example, by calling the system API, the CPU usage rate, the current number of processes, and the resource occupancy information of each process are obtained. Through the network status monitoring interface, data such as the network connection type, real-time network, and network latency are obtained. Through the memory management interface, the total capacity, used capacity, remaining capacity of the memory, and the memory usage of each application are obtained. For example, when it is found that the application frequently freezes and crashes when the network bandwidth is low, the network factor can be incorporated into the problem analysis system to more accurately locate the problem.

[0030] In addition, the system continuously monitors the abnormal states of applications, such as key indicators like memory leaks, excessive resource occupancy, and changes in the crash rate. By setting reasonable thresholds, when these indicators approach the thresholds, the system can timely issue warning or alarm messages to remind relevant personnel to intervene and handle in a timely manner, nipping the problem in the bud. It should be noted that the timestamps of the device status data and the timestamps of the log crash events are strictly aligned through a time synchronization protocol (such as NTP), so as to establish a mapping relationship between the device status and the crash events, ensuring the temporal consistency of the correlation analysis between the crash events and the device status data.

[0031] Step 102: Upload the crash event data to the large model platform for intelligent analysis and receive the preliminary repair suggestions returned by the large model platform.

[0032] Deploy the software and hardware environment related to the large model platform. According to the business characteristics and data scale of the terminal application, reasonably configure the computing resources, storage resources, etc. of the server. For example, select the appropriate server CPU, memory, and hard disk capacity according to the expected number of logs to be processed and the analysis complexity. Customize the development of the platform and optimize the algorithm model to make it more suitable for the problem analysis needs of the terminal application.

[0033] When the terminal application detects crash information and completes preliminary processing, the key crash data is uploaded to the large model platform through a secure data transmission channel. The model inputs include the historical crash case library, the code repository version differences, and the device compatibility database to identify the similarity between the current crash event and historical faults. After receiving the data, the large model platform uses a pre-trained neural network model and conducts in-depth analysis based on the crash event description table and the associated device status data.

[0034] Then, the model locates the code files and line numbers involved in the crash function stack through code static analysis techniques such as abstract syntax tree traversal. It can be understood that if the model identifies that the similarity between the crash event and the historical case of "payment failure due to network timeout" exceeds the preset threshold, it outputs preliminary repair suggestions, including the location of the problem code segment, the cause of the problem, the recommended repair direction, the repair priority, and the recommended modification plan such as adding a network request retry mechanism.

[0035] Step 103: Perform correlation analysis on the crash event data and the real-time running status data to determine a hotfix solution based on the correlation analysis results and the preliminary repair suggestions, and generate a hotfix package according to the hotfix solution.

[0036] Perform correlation analysis on the collected device information and the log data of the application running status. First, match the timestamp of the crash event with the timeline of the device status data. Exemplarily, if it is monitored that the terminal application has phenomena such as lag and crash when the CPU usage rate is too high, the system will further analyze the tasks being executed by the application at this time to determine whether there are problems such as unreasonable resource consumption, that is, a crash event caused by resource overload. At this time, the thread scheduling strategy needs to be optimized. If the application frequently fails to load data when the network is unstable, the system will combine data such as network latency and bandwidth to determine whether it is a problem caused by network fluctuations or an unreasonable network request setting of the application itself, and it is recommended to add a request retry mechanism. It can be understood that if the crash event is not associated with abnormal device status, it is marked as a code logic defect (such as a null pointer exception), and the problem code segment needs to be directly repaired.

[0037] Then, combine the preliminary repair suggestions given by the large model platform and the analysis results of the system itself for the crash problem to determine the specific repair solution. Exemplarily, for the resource overload problem, generate a code patch to limit the CPU occupancy of background processes. For network problems, insert a retry logic code segment. When generating the hotfix package, use a differential comparison tool to extract the code segments to be modified, such as only retaining the added or deleted lines, and compress the updated content of the resource files, such as deleting redundant icon files. It should be noted that in order to ensure compatibility with the terminal application version, version verification information and an installation script are also embedded in the hotfix package.

[0038] Step 104: Send the hotfix package to the terminal application through the update channel, and automatically load and install the hotfix package in the background of the terminal application to complete the dynamic repair of the crash event without interrupting the operation of the terminal application.

[0039] Through the in-app update mechanism, the hotfix package is pushed to the problematic terminal devices. Exemplarily, after receiving the hotfix package, the terminal device starts an independent service thread in the background. Based on the embedded version verification information, it verifies whether the hotfix package is compatible with the version of the terminal application, and triggers the installation process after the verification passes. During the installation process, the hotfix mechanism ensures that the new code patches and resources are replaced into the application without interrupting the normal use of the user, completing the repair of the crash problem.

[0040] Specifically, during the installation process, the class loading mechanism is used to dynamically replace the problematic code segments loaded in memory and update the resource file cache, such as replacing image resources. It can be understood that the entire installation process is completed without the user's awareness. For example, when the user is browsing the product details page, the hotfix package takes effect silently in the background, and the repaired payment function can be used immediately without restarting the application.

[0041] In addition, after the repair is completed, the application running status of the terminal application is monitored again. If the same crash event recurs, the alarm level is upgraded and the manual intervention process is triggered. At the same time, the repair effect is fed back to the large model platform to optimize the accuracy of subsequent repair suggestions. Exemplarily, a certain hotfix significantly reduces the payment crash rate, and the platform marks this solution as a high-priority recommended strategy, forming a self-optimizing technical closed-loop.

[0042] This application aims to solve the technical problems of untimely and inaccurate state perception during the operation of the terminal application and inefficiency after dynamic repair. Through the above improvement measures, it realizes the intelligent and comprehensive perception of the terminal application state, and can perform dynamic repair quickly and effectively, improving the stability and user experience of the terminal application.

[0043] The above is the method embodiment proposed in this application. Based on the same inventive concept, the embodiments of this application also provide a device for intelligent perception and dynamic repair of the terminal application state, and its structure is as Figure 2 shown.

[0044] Figure 2 is the internal structure schematic diagram of a device for intelligent perception and dynamic repair of the terminal application state provided by the embodiment of this application. As Figure 2 shown, the device includes: At least one processor; And a memory communicatively connected to at least one processor; Wherein, the memory stores instructions executable by at least one processor, and the instructions are executed by at least one processor so that at least one processor can: Real-time monitor the log crash information generated by the terminal application to extract the corresponding crash event data, and collect the real-time operation status data of the terminal application; Upload the crash event data to the large model platform for intelligent analysis and receive the preliminary repair suggestions returned by the large model platform; Perform correlation analysis on the crash event data and the real-time running status data, determine the hotfix solution based on the correlation analysis results and the preliminary repair suggestions, and generate a hotfix package according to the hotfix solution; Send the hotfix package to the terminal application through the update channel, and automatically load and install the hotfix package in the background of the terminal application to complete the dynamic repair of the crash event without interrupting the operation of the terminal application.

[0045] The embodiment of the present application also provides a non-volatile computer storage medium storing computer-executable instructions, which when executed can: Real-time monitor the log crash information generated by the terminal application to extract the corresponding crash event data, and collect the real-time running status data of the terminal application; Upload the crash event data to the large model platform for intelligent analysis and receive the preliminary repair suggestions returned by the large model platform; Perform correlation analysis on the crash event data and the real-time running status data, determine the hotfix solution based on the correlation analysis results and the preliminary repair suggestions, and generate a hotfix package according to the hotfix solution; Send the hotfix package to the terminal application through the update channel, and automatically load and install the hotfix package in the background of the terminal application to complete the dynamic repair of the crash event without interrupting the operation of the terminal application.

[0046] Each embodiment in the present application is described in a progressive manner. The same or similar parts among the embodiments can be referred to each other, and the differences between each embodiment and other embodiments are emphasized. In particular, for the device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiments.

[0047] The device and medium provided by the embodiment of the present application correspond to the method one by one. Therefore, the device and medium also have beneficial technical effects similar to those of the corresponding method. Since the beneficial technical effects of the method have been described in detail above, the beneficial technical effects of the device and medium will not be elaborated here.

[0048] Those skilled in the art should understand that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) that contain computer-usable program code.

[0049] The present application is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowchart and / or block diagram can be implemented by computer program instructions, as well as the combination of flows and / or blocks in the flowchart and / or block diagram. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the specified functions in Figure 1 one or more flows Figure 1 or blocks.

[0050] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including instruction means that implement the specified functions in Figure 1 one or more flows Figure 1 or blocks.

[0051] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the specified functions in Figure 1 one or more flows Figure 1 or blocks.

[0052] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0053] The memory may include non-permanent memory in the form of computer-readable media, random access memory (RAM), and / or non-volatile memory such as read-only memory (ROM) or flash RAM. The memory is an example of computer-readable media.

[0054] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0055] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0056] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. An intelligent perception and dynamic repair method for terminal application status, characterized in that, The method includes: Real-time monitoring of the log crash information generated by the terminal application to extract corresponding crash event data, and collecting the real-time running status data of the terminal application; Uploading the crash event data to the large model platform for intelligent analysis, and receiving the preliminary repair suggestions returned by the large model platform; Performing correlation analysis on the crash event data and the real-time running status data, determining a hotfix solution based on the correlation analysis results and the preliminary repair suggestions, and generating a hotfix package according to the hotfix solution; Sending the hotfix package to the terminal application through the update channel, and automatically loading and installing the hotfix package in the background of the terminal application to complete the dynamic repair of the crash event without interrupting the operation of the terminal application.

2. The intelligent perception and dynamic repair method for the terminal application state according to claim 1, characterized in that Collecting the real-time running status data of the terminal application specifically includes: Invoking the system interface to obtain the real-time running status data of the terminal application; the real-time running status data includes CPU usage rate, memory occupancy rate, and network connection status; Monitoring the memory occupancy of the terminal application through the memory management interface to record the memory leakage rate and the remaining available memory capacity; Aligning the timestamps in the real-time running status data and the crash event data to establish a mapping relationship between the device status and the crash event.

3. The intelligent perception and dynamic repair method for the terminal application state according to claim 1, characterized in that, Real-time monitoring of the log crash information generated by the terminal application to extract corresponding crash event data specifically includes: Embedding log collection code in the terminal application to collect the log information generated during the operation of the terminal application to continuously record user operation behaviors and system state change events; Storing the log information in a segmented manner according to a preset method, and starting a log analysis thread to periodically read the segmented log files; Parsing the file information in the log file through lexical analysis technology and syntactic analysis technology, extracting key data, and constructing a corresponding crash event description table based on the key data; the key data includes crash time, trigger path, and associated function stack information.

4. The intelligent perception and dynamic repair method for the terminal application status according to claim 1, wherein Uploading the crash event data to the large model platform for intelligent analysis specifically includes: Inputting the crash event description table and the associated device status data into a pre-trained neural network model to identify the similarity between the crash event and historical faults, and comparing several similarities with preset similarity thresholds respectively; Locating the problem code segment with potential defects in the function call chain corresponding to the crash event, and generating preliminary repair suggestions for the problem code segment based on historical faults with similarities exceeding the preset similarity threshold; the preliminary repair suggestions include the location of the problem code segment and the repair priority order.

5. The intelligent perception and dynamic repair method for the terminal application state according to claim 1, wherein Performing correlation analysis on the crash event data and the real-time running status data specifically includes: According to the crash time in the crash event data, determining whether the CPU usage rate corresponding to the crash time exceeds a preset threshold, and when the crash event coincides with the time period when the CPU usage rate exceeds the preset threshold, determining that the cause of the crash event is resource overload; When the crash event is associated with a sudden increase in network latency or a sharp drop in bandwidth within a preset time period, determine that the cause of the crash is an abnormal network environment. If the crash event is not associated with an abnormal device state, mark the cause of the crash as a code logic defect; In the case where the cause of the crash is associated with abnormal device resources, trigger a warning signal based on a preset resource threshold and generate a corresponding alarm message.

6. The intelligent perception and dynamic repair method for the terminal application state according to claim 1, characterized in that Generate a hotfix package according to the hotfix solution, specifically including: Perform a differential comparison between the problem code segment and the corresponding standard code segment at the location where the problem code segment is located to extract a code patch; the code patch represents the code segment corresponding to the part to be modified; Delete redundant data in the updated content of the resource file to compress the updated content of the resource file; Generate a hotfix package based on the code patch and the compressed updated content of the resource file, and embed version verification information and an installation script in the hotfix package.

7. The intelligent perception and dynamic repair method for the terminal application status according to claim 6, characterized in that Automatically load and install the hotfix package in the background of the terminal application to complete the dynamic repair of the crash event without interrupting the operation of the terminal application, specifically including: Automatically load the hotfix package in the terminal application and verify the hotfix package based on the embedded version verification information to determine whether the hotfix package is compatible with the version of the terminal application; After the verification passes, trigger the installation process to replace the problem code segment in the memory during the operation of the terminal application through the class loading mechanism based on the installation script; Update the cache of the resource file based on the compressed updated content of the resource file in the hotfix package and record the corresponding repair log.

8. The intelligent perception and dynamic repair method for the terminal application state according to claim 1, characterized in that, After completing the dynamic repair of the crash event without interrupting the operation of the terminal application, the method further includes: Re-monitor the application running state corresponding to the repaired terminal application; in the case where the same crash event is triggered again, upgrade the alarm level of the corresponding crash event and trigger the manual intervention process; Dynamically adjust the training dataset of the large model platform according to the repair effect of the crash event to optimize the generation strategy of the repair suggestions.

9. An intelligent perception and dynamic repair device for terminal application status, characterized in that, The device includes: At least one processor; And a memory communicatively connected to the at least one processor; Wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute a method for intelligent perception and dynamic repair of the terminal application state according to any one of claims 1-8.

10. A non-volatile computer storage medium stores computer-executable instructions, characterized in that, When the computer-executable instructions are executed, a method for intelligent perception and dynamic repair of the terminal application state according to any one of claims 1-8 is implemented.

Images