Safety processing method, device and equipment for abnormal flash quit of app

Abstract

The invention discloses a safety processing method, device and equipment for abnormal flash quit of an application program app. The security processing method is applied to a terminal, a user-defined app security processing module is preset in a terminal system program of an app, and the app security processing module is used for enabling the app to enter a security operation mode and performing security processing on the occurred exceptions when various exceptions occur in the operation process of the app; the safety processing method for the abnormal flash-back of the app comprises the steps that when an exception related to the flash-back of the app occurs in the running process of the app, the app safety processing module captures relevant information of the exception, the app is switched into a safety running mode, in the safety running mode, the app safety processing module starts a dynamic container page to replace an exception interface of the app, and the app safety processing module sends the exception to the app. And sending a security policy request message to the server, wherein the security policy request message carries the abnormal call stack information. According to the embodiment of the invention, when the app is abnormal, the app can enter the security mode.

Description

Technical Field

[0001] The present application relates to the field of system security protection technology, and in particular to a method, device, electronic device, computer-readable storage medium and computer program product for safely processing abnormal flash back of an application app. Background Art

[0002] After entering the era of mobile Internet, a large number of Internet users have shifted from PC to mobile terminals, so the quality of mobile terminal programs has become particularly important. If there are vulnerabilities in the online programs on the mobile terminals, it may cause the loss of users and the loss of company assets. However, due to the diversity of mobile devices, differences in system versions, and some human factors, program vulnerabilities on mobile terminals are inevitable. Among them, the most serious and the most influential type of program vulnerabilities that cause the application to crash and flash back. Since the update of applications on mobile terminals depends on the release of versions, and the review process for the release of applications in various application markets is becoming more and more stringent, it has greatly increased the difficulty of repairing online vulnerabilities in mobile terminal programs, but the need to solve the online flash back of mobile terminals is very urgent.

[0003] In view of the above problems, the existing technology reports the crash call stack information when the application crashes. When the application is started again, it attempts to request and download the patch package from the server, and uses the hot fix framework to make these patches take effect immediately, or wait until the application is started again.

[0004] However, the solutions in the prior art often have the following problems:

[0005] 1. When the application crashes during the startup phase of the application life cycle, it is difficult to successfully download the patch. In particular, when a program vulnerability causes the application to crash continuously during the startup phase, the patch is difficult to fix the terminal problem.

[0006] 2. The existing technology cannot execute different security strategies based on crash information and lacks the flexibility to solve the crash problem.

[0007] 3. Some program vulnerabilities that have little impact or do not affect the main business can actually be ignored, and there is no need to create patches. However, because these vulnerabilities cause the application to crash, under the original technical solution, in order to fix these crashes, patches have to be created and released, and the cost of this is relatively high.

[0008] 4. When the application crashes continuously during startup or in the main business process path, the user experience is very bad while the application engineers are troubleshooting the problem and making and releasing patches. Summary of the invention

[0009] In view of this, embodiments of the present application provide a method, device, electronic device, computer-readable storage medium and computer program product for securely handling abnormal crashes of an application app, for solving at least one technical problem.

[0010] The embodiment of the present application provides a security processing method for abnormal flash back of an application app, which is applied to a terminal, wherein a customized app security processing module is pre-set in the terminal system program of the app, and the app security processing module is used to enable the app to enter a safe operation mode and perform security processing on the abnormalities when multiple abnormalities occur during the operation of the app; the security processing method for abnormal flash back of the app includes: when an abnormality related to the flash back of the app occurs during the operation of the app, the app security processing module captures the relevant information of the abnormality and switches the app to a safe operation mode, in which the app security processing module starts a dynamic container page to replace the abnormal interface of the app, and sends a security policy request message to a server, wherein the security policy request message carries the call stack information of the abnormality, so that the server issues a security processing policy corresponding to the abnormality; after receiving the security processing policy issued by the server, the security processing policy is executed to enable the app to eliminate the abnormality, and the security information corresponding to the security processing policy is loaded in the dynamic container page, and after the abnormality is eliminated, the normal operation interface of the app is returned.

[0011] Optionally, according to the method of the embodiment of the present application, when the system default exception handler starts to kill the app due to an exception related to the app crash during the app running process, the app security processing module intercepts the exception handler's behavior of killing the app. Optionally, according to the method of the embodiment of the present application, the security processing strategy includes at least one of the following: a first security processing strategy: downloading a patch file according to the address of the patch file sent by the server, and installing the patch file to the terminal; a second security processing strategy: clearing the cache and restarting or running the switch configuration file sent by the server, the switch configuration file is used to turn off abnormal functions of the terminal operation; a third security processing strategy: using a dynamic container page to display alternative content sent by the server and notifying the background system of the server of the app to handle the exception, wherein the alternative content is the same as part of the content displayed on the page when the app is running normally.

[0012] Optionally, according to the method of an embodiment of the present application, the alternative content includes: interactive function information, activity information and / or advertising information of the app.

[0013] Optionally, according to the method of an embodiment of the present application, it also includes: after the server receives the security policy request message, it determines whether the exception occurs for the first time based on the call stack information; if it occurs for the first time, a third security processing policy is sent to the terminal; if the exception does not occur for the first time, and the server stores a patch file corresponding to the exception, the first security processing policy is sent to the terminal.

[0014] Optionally, according to the method of an embodiment of the present application, it also includes: if the server does not store a patch file corresponding to the exception, determining whether the exception can be resolved by a second security processing strategy; if it can be resolved by the second security processing strategy, issuing the second security policy to the terminal; if the exception cannot be resolved by the second security processing strategy, issuing a third security policy to the terminal.

[0015] Optionally, according to the method of the embodiment of the present application, the security information corresponding to the first security processing strategy includes: the download progress of the patch; and / or, the security information corresponding to the second security processing strategy includes: prompt content for guiding the user to cooperate with the second security policy to perform operations.

[0016] The embodiment of the present application provides a security processing device for abnormal flash back of an application app, which is applied to a terminal. A custom app security processing module is pre-set in the terminal system program of the app. The app security processing module is used to make the app enter a safe operation mode and perform security processing on the abnormalities when multiple abnormalities occur during the operation of the app; the security processing device for abnormal flash back of the app includes: a capture module, which is used to capture relevant information of the abnormality by the app security processing module when an abnormality related to the flash back of the app occurs during the operation of the app; a switching module, which is used to switch the app to a safe operation mode, in which the app security processing module starts a dynamic container page to replace the abnormal interface of the app, and sends a security policy request message to a server, wherein the security policy request message carries the call stack information of the abnormality, so that the server issues a security processing policy corresponding to the abnormality; an execution module, which is used to execute the security processing policy after receiving the security processing policy issued by the server to make the app eliminate the abnormality, and load the security information corresponding to the security processing policy in the dynamic container page, and return to the normal operation interface of the app after the abnormality is eliminated.

[0017] An embodiment of the present application provides an electronic device, which includes a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the steps of the method described above are implemented.

[0018] An embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the steps of the method described above are implemented.

[0019] An embodiment of the present application provides a computer program product, wherein the computer program product includes computer program instructions, and when the computer program instructions are executed by a processor, the steps of the method described above are implemented.

[0020] By adopting the embodiments of the present application, the availability of the application can be guaranteed to the greatest extent by switching the application to a safe operation mode, thereby improving user retention and improving the user experience. In addition, the embodiments of the present application can issue a security processing strategy based on the abnormal call stack information, which has great flexibility and pertinence and can significantly improve the efficiency of exception handling. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solution of the embodiments of the present application, the following briefly introduces the drawings in the embodiments of the present application.

[0022] Figure 1 It is a schematic diagram of a system architecture of an embodiment of the present application.

[0023] Figure 2 It is a flowchart of a method for safely handling abnormal crash of an application app according to an embodiment of the present application.

[0024] Figure 3 It is a schematic diagram of an Android dynamic container page according to an embodiment of the present application.

[0025] Figure 4 It is a schematic diagram of the interaction between a terminal and a server in an embodiment of the present application.

[0026] Figure 5 It is a schematic diagram of the principle of using the tinker hot repair framework in an embodiment of the present application.

[0027] Figure 6 It is a flow chart of a method for securely handling a program vulnerability in an application program app according to an embodiment of the present application.

[0028] Figure 7 It is a structural block diagram of a security processing device for abnormal crash of an application app in an embodiment of the present application.

[0029] Figure 8 It is a schematic diagram of the hardware structure of the electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0030] The principles and spirit of the present application will be described below with reference to several exemplary embodiments. It should be understood that the purpose of providing these embodiments is to make the principles and spirit of the present application clearer and more thorough, so that those skilled in the art can better understand and implement the principles and spirit of the present application. The exemplary embodiments provided herein are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments herein, all other embodiments obtained by ordinary technicians of the art without creative work are within the scope of protection of this application.

[0031] Embodiments of the present application relate to terminal devices and / or servers. Those skilled in the art will appreciate that the embodiments of the present application may be implemented as a system, apparatus, device, method, computer-readable storage medium, or computer program product. Therefore, the present disclosure may be specifically implemented in at least one of the following forms: complete hardware, complete software, or a combination of hardware and software. According to the embodiments of the present application, the present application requests protection for a method, apparatus, electronic device, computer-readable storage medium, and computer program product for securely processing abnormal flashbacks of an application app. Figure 1 A schematic diagram of a system architecture of an embodiment of the present application is shown. Figure 1 As shown, the system includes a terminal device 102 and a server 104. Among them, the terminal device 102 may include at least one of the following: a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart TV, various wearable devices, an augmented reality AR device, a virtual reality VR device, etc. A terminal may be installed on the terminal device 102. For example, the terminal may be a terminal that specifically performs a specific function (such as an application app), or a terminal with multiple application applets (different functions) embedded in it, or a terminal logged in through a browser. The user can operate on the terminal device 102. For example, the user can open the terminal installed on the terminal device 102 and input instructions through terminal operation, or the user can open the browser installed on the terminal device 102 and input instructions through browser operation. After the terminal device 102 receives the instruction input by the user, the request information containing the instruction is sent to the server 104. After receiving the request information, the server 104 performs corresponding processing and then returns the processing result information to the terminal device 102. The user instruction is completed through a series of data processing and information interaction.

[0032] In this document, terms such as first, second, third, etc. are only used to distinguish one entity (or operation) from another entity (or operation), but not to require or imply any order or relationship between these entities (or operations).

[0033] Figure 2The present invention is a flowchart of a method for safely handling abnormal flash back of an application app in an embodiment of the present invention. The method for safely handling abnormal flash back of an application app in an embodiment of the present invention is applied to a terminal. A customized app safety processing module is pre-set in the terminal system program of the app. The app safety processing module is used to make the app enter a safe operation mode and safely handle the abnormalities when multiple abnormalities occur during the operation of the app. The method for safely handling abnormal flash back of the app includes the following steps:

[0034] S101, when an exception related to app crash occurs during app operation, the app security processing module captures relevant information of the exception and switches the app to a safe operation mode. In the safe operation mode, the app security processing module starts a dynamic container page to replace the app's exception interface, and sends a security policy request message to the server. The security policy request message carries the abnormal call stack information, so that the server sends a security processing policy corresponding to the exception.

[0035] S102, after receiving the security processing policy sent by the server, execute the security processing policy to eliminate the exception of the app, and load the security information corresponding to the security processing policy in the dynamic container page. After the exception is eliminated, return to the normal operation interface of the app.

[0036] In the embodiment of the present application, a custom app security processing module is preset in the application app, and the custom app security processing module can make the app enter the safe operation mode and safely handle the exceptions that occur when the app runs abnormally. In some embodiments of the present application, optionally, the app security processing module is a custom exception handler, which is different from the system default exception handling. When an exception occurs in the application app, the system will execute the custom exception handler instead of the system default exception handler (the system default exception handler will kill the application and cause flashback). Regarding the setting process of the custom exception handler, taking the Android system as an example, when the application app is started (in the Application.onCreate life cycle method), call the java Thread.setDefaultUncaughtExceptionHandler method, pass in an instance of the exception handler, and write the custom exception handling logic (abnormal reporting, starting the safe mode page, restarting the message loop of a main thread) in the uncaughtException method of this instance, so that a custom exception handler can be implemented. Among them, restarting the message loop of a main thread allows the application in safe mode to receive, distribute and process various messages.

[0037] In this way, when an exception occurs in the application app, the app security processing module can report the exception call stack information to the server according to the set exception handling logic, and at the same time start a page in safety mode. The page in safety mode is essentially a container page (dynamic container page). The specific information displayed on the page can be sent down through the server, so as to achieve the effect of flexible display of dynamic content. Figure 3 Schematic diagram of an Android dynamic container page according to an embodiment of the present application. Figure 3 As shown, the page of the Android system uses Activity as a carrier and WebView as a dynamic page container. In other embodiments of the present application, optionally, RN and other technologies can also be used to replace WebView as a dynamic page container.

[0038] Furthermore, in an embodiment of the present application, when an exception occurs in an application, a customized app security processing module captures the exception and opens a dynamic container page in a safe mode to replace the app's exception interface. At the same time, the app security processing module sends a security policy request message carrying the abnormal call stack information to the server, requesting the server to issue a security processing policy corresponding to the abnormal call stack information. Figure 4 Schematic diagram of the interaction between a terminal and a server in an embodiment of the present application. Figure 4 As shown, the terminal sends a security policy request to the server, and the server issues a corresponding security processing policy based on the abnormal call stack information. The server issues different security information for different security processing policies. The security information contained in the page issued by the server is displayed to the dynamic container, and the security processing policy is sent to the client for execution.

[0039] The following is a JSON example of a client requesting a server security policy. The JSON contains three fields: the from-domain field indicates which client the exception information comes from, the app-version field indicates the client application version, and the stack-info field indicates the details of the exception call stack. The server returns the specific security policy based on these three fields.

[0040] {

[0041] "from-domain":"XXX-Android",

[0042] “app-version”: “version”

[0043] "stack-info": detailed information about the exception call stack

[0044] }

[0045] In some embodiments of the present application, optionally, if the abnormal call stack information has appeared before, and the server stores the corresponding patch file, then the security processing strategy at this time may be: download the patch file according to the download address of the patch file returned to the client by the server, display the download progress of the patch file on the dynamic container page, and restart the application, and install the patch program through the hot repair framework to solve the program vulnerability. In this way, the terminal eliminates the abnormal problem of the app according to the security processing strategy issued by the server, and loads the corresponding security information (for example, the download progress of the patch file) in the dynamic container page. After the abnormality is eliminated, the normal operation interface of the app can be returned.

[0046] By adopting the embodiments of the present application, the availability of the application can be guaranteed to the greatest extent by switching the application to a safe operation mode when an exception occurs in the application, thereby improving user retention and user experience. In addition, in the embodiments of the present application, the server can issue a security processing strategy based on the abnormal call stack information, which has great flexibility and pertinence, and can significantly improve the efficiency of exception handling.

[0047] In some embodiments of the present application, optionally, the security processing method of the present application also includes: when the system default exception handler starts to kill the app due to an exception related to the app crash during the app running process, the app security processing module intercepts the exception handler's behavior of killing the app.

[0048] When an exception occurs in an application, the custom app security processing module can capture the exception, intercept the system's default behavior of killing the application process, so that the application will no longer crash, and can replace the app exception interface with a dynamic container page. The page displayed in the dynamic container page is issued by the server according to the security policy, which has high flexibility. In addition, since the application will no longer crash when an exception occurs, this can improve the user experience compared to the previous crash or page failure (the background is making a patch).

[0049] In some embodiments of the present application, optionally, the security processing strategy includes at least one of the following:

[0050] 1) The first security processing strategy: download the patch file according to the address of the patch file sent by the server, and install the patch file to the terminal;

[0051] 2) The second security processing strategy: clear the cache and restart or run the switch configuration file sent by the server. The switch configuration file is used to disable abnormal functions running on the terminal;

[0052] 3) The third security processing strategy: Use a dynamic container page to display alternative content sent by the server and notify the backend system of the app's server to handle the exception, where the alternative content is the same as part of the content displayed on the page when the app runs normally.

[0053] The first security processing strategy can also be called a hot fix strategy. For this security processing strategy, the terminal can download the patch according to the download address of the patch file issued by the server, and the download speed of the patch file can be displayed on the dynamic container page. After the download is complete, the application can be restarted, and the patch can be installed through the hot fix framework to resolve the program vulnerability. This security processing strategy handles application exceptions quickly, and can remind users that the problem is being resolved by displaying the download speed of the patch file, which can improve the user experience when facing program exceptions.

[0054] For the first security policy, the following is a JSON example of the first security processing policy returned by the server. The app-version field indicates the application version number of the client, the safe-mode field indicates the security policy that the client needs to execute, and the safe-page-url field indicates the h5 page address that the dynamic container page needs to display. Under the hot fix policy, you can configure a page that displays the progress of downloading the hot fix patch. mode-info contains the following information fields related to the security policy. Under the hot fix policy, it is the download address of the patch package.

[0055] {

[0056] "app-version":"13.5.0"

[0057] "safe-mode":"hotfix".

[0058] "safe-page-ur!":"The h5 page address that needs to be displayed on the dynamic container page".

[0059] "mode-info":{

[0060] "patch-url": "Patch package download address"

[0061] }

[0062] }

[0063] Figure 5 FIG. 1 is a schematic diagram of the principle of using the tinker hot repair framework in an embodiment of the present application. Figure 5As shown, the Android side can use the tinker hot fix framework to create a patch program to fix online anomalies. After downloading the patch package on the side, you can restart the application. After the application is restarted, you can use the tinker framework to install the patch package to make it effective.

[0064] The second type of security processing strategy can also be called a pre-configured instruction strategy. This security processing strategy is generally used when the abnormal problem of the application can be solved by specific instructions. The pre-configured instructions here can be clearing the cache, restarting, modifying the switch configuration file of the mobile terminal, etc. The flash back problem caused by the cache can usually be solved by clearing the cache. Some exceptions that do not affect the main business logic can be ignored or no secondary exceptions will occur. You can immediately exit the safe mode page to allow users to continue using the application or restart to solve it. Some flash backs can be solved by modifying the client's function switch configuration file. For example, for some abnormal functions in the application, you can disable the function by modifying its switch configuration file. This type of strategy can be displayed on the dynamic container page with some prompt copy information to improve the user experience. For example, you can display "The application has an exception. Do you want to solve it by restarting the application?" on the dynamic container page.

[0065] The following is a JSON example of the second security processing strategy returned by the server. The returned fields are basically the same as those of the first security processing strategy, except for the value of the safe-mode field and the instruction field in mode-info. The instruction field is an array that represents a set of instructions to be executed sequentially. In this example, the client needs to perform two operations, clear cache and restart, sequentially.

[0066] {

[0067] "app-version":"13.5.0"

[0068] "safe-mode":"predefine-instruction"

[0069] "safe-page-url": "The h5 page address that the dynamic container page needs to display"

[0070] "mode-info":{

[0071] "instruction":[

[0072] "clear-cache"

[0073] "restart" ]

[0075] }

[0076] }

[0077] The third security handling strategy is mainly used for some abnormal information that has never appeared or cannot be repaired in a short time. At this time, the server can send dynamic content to the terminal's dynamic container page for display. At the same time, the dynamic container page can display some alternative content, such as: some interactive function information related to the main business of the application or some activity information, or even advertising information. At the same time, the new abnormal information that appears this time should trigger an alarm to notify engineers to analyze the abnormal information, select an abnormal handling strategy, and update the server's configuration information.

[0078] The following is a json example of the third security processing strategy returned by the server. The third security processing strategy is a fallback solution that only needs to display dynamic pages. The dynamic content here can be configured with pages related to the application business. For example, the 51job application can be configured with a resume filling page, a job list browsing page, and even a page for activities such as March and April. It has high flexibility, allowing users to use certain basic functions even when an exception occurs in the native App, providing a better user experience.

[0079] {

[0080] "app-version":"13.5.0"

[0081] "'safe-mode":"business"

[0082] "safe-page-url": "The h5 page address that the dynamic container page needs to display"

[0083] }

[0084] By adopting the security processing method proposed in the embodiment of the present application, even when facing difficult-to-handle exceptions, it is possible to ensure that users can use the application to the greatest extent by loading dynamic container pages, thereby improving the user experience. Moreover, the embodiment of the present application has a variety of different security processing strategies, which can handle different abnormal problems, so that the problem handling is more flexible and the processing efficiency is higher.

[0085] In some embodiments of the present application, optionally, after receiving the security policy request message, the server determines whether the exception occurs for the first time based on the call stack information. If it occurs for the first time, a third security processing policy is sent to the terminal; if the exception does not occur for the first time and the server stores a patch file corresponding to the exception, the first security processing policy is sent to the terminal.

[0086] In an embodiment of the present application, the server determines whether the exception occurs for the first time based on the call stack information of the exception, and issues a corresponding security processing strategy based on the judgment result. If the exception occurs for the first time, the third security processing strategy is issued to the terminal. If the exception does not occur for the first time and the server stores a patch file corresponding to the exception, the first security processing strategy is issued to the terminal.

[0087] In some embodiments of the present application, optionally, if the server does not store a patch file corresponding to the exception, it is determined whether the exception can be resolved by a second security processing strategy. If it can be resolved by the second security processing strategy, the second security policy is sent to the terminal; if the exception cannot be resolved by the second security processing strategy, a third security policy is sent to the terminal.

[0088] In some embodiments of the present application, optionally, the security information corresponding to the first security processing strategy includes: patch download progress; and / or, the security information corresponding to the second security processing strategy includes: prompt content for guiding the user to cooperate with the second security policy to perform operations.

[0089] In the embodiment of the present application, the security information displayed in the dynamic container page is issued by the server according to different security processing strategies, wherein the security information corresponding to the first security processing strategy may be the download progress of the patch, and the security information corresponding to the second security processing strategy may be prompt content for guiding the user to cooperate with the second security policy to operate. Since the third security processing strategy is mainly to display the alternative content issued by the server in the dynamic container page, the security information corresponding to the third security processing strategy is the alternative content issued by the server.

[0090] The above describes the implementation methods and advantages of the embodiments of the present application through multiple embodiments. The following describes the specific processing process of the embodiments of the present application in detail with reference to specific examples.

[0091] Figure 6 Taking the case of a program vulnerability in an application app as an example, a flowchart of the security processing method of an embodiment of the present application is shown. Figure 6 As shown, the safe processing method for abnormal flash back of the application app in the embodiment of the present application includes the following processing:

[0092] S601: The APP triggers a program vulnerability and throws an exception;

[0093] S602: Capture exceptions, intercept system behavior (flashback), and enter the safe mode page;

[0094] S603: Upload abnormal code call stack information and request server security policy;

[0095] S604: receiving abnormal information uploaded by the mobile terminal, and issuing security policies according to the code call stack;

[0096] S605: Check whether there is a patch program for the code call stack; if yes, execute step S606; if no, execute step S607;

[0097] S606: Download the patch program and restart the application;

[0098] S607: Check whether the code call stack is equipped with pre-configured instructions; if yes, execute step S608; if no, execute step S609;

[0099] S608: Execute the instruction sent by the server;

[0100] S609: Determine whether a dynamic page is configured for the code call stack; if yes, execute step S610; if no, execute step S611;

[0101] S610: Dynamic container displays the dynamic page of server configuration;

[0102] S611: New abnormal call site information, using a fallback dynamic page. Trigger an alarm, analyze the call stack information, and update the security configuration.

[0103] Corresponding to the method embodiment of the present application, the present application also provides a security processing device for abnormal flash back of an application app, such as Figure 7 As shown, a security processing device 100 for abnormal flash back of an application app is applied to a terminal, and a customized app security processing module is pre-set in the terminal system program of the app. The app security processing module is used to make the app enter a safe operation mode and perform security processing on the abnormalities when multiple abnormalities occur during the running of the app. The security processing device for abnormal flash back of the app includes:

[0104] The capture module 110 is used to capture relevant information of the exception by the app security processing module when an exception related to the app crash occurs during the app running process;

[0105] The switching module 120 is used to switch the app to a safe operation mode. In the safe operation mode, the app security processing module starts a dynamic container page to replace the abnormal interface of the app, and sends a security policy request message to the server. The security policy request message carries the call stack information of the exception, so that the server sends a security processing policy corresponding to the exception.

[0106] The execution module 130 is used to execute the security processing policy sent by the server after receiving the security processing policy so that the app eliminates the exception, and load the security information corresponding to the security processing policy in the dynamic container page, and return to the normal operation interface of the app after the exception is eliminated.

[0107] The electronic device in the embodiment of the present application may be a user terminal device, a server, other computing devices, or a cloud server. Figure 8 It is a schematic diagram of the hardware structure of an electronic device of an embodiment of the present application. The electronic device may include a processor 801 and a memory 802 storing computer program instructions. When the processor 801 executes the computer program instructions, it implements the process or function of any of the above-mentioned embodiments.

[0108] Specifically, the processor 801 may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application. The memory 802 may include a large-capacity memory for data or instructions. For example, the memory 802 may be at least one of the following: a hard disk drive (HDD), a read-only memory (ROM), a random access memory (RAM), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a tape, a universal serial bus (USB) drive, or other physical / tangible memory storage devices. For another example, the memory 802 may include a removable or non-removable (or fixed) medium. For another example, the memory 802 may be inside or outside the integrated gateway disaster recovery device. The memory 802 may be a non-volatile solid-state memory. In other words, the memory 802 generally includes a tangible (non-transitory) computer-readable storage medium (such as a memory device) encoded with computer-executable instructions, and when the software is executed (such as by one or more processors), the operations described in the method of the embodiments of the present application may be performed. The processor 801 implements the process or function of any method in the above embodiments by reading and executing the computer program instructions stored in the memory 802.

[0109] In one example, Figure 8The electronic device shown may also include a communication interface 803 and a bus 810. Among them, the processor 801, the memory 802, and the communication interface 803 are connected through the bus 810 and complete the communication between each other. The communication interface 803 is mainly used to realize the communication between each module, device, unit and / or device in the embodiment of the present application. The bus 810 includes hardware, software or both, and can couple the components of the online data traffic billing device to each other. For example, the bus may include at least one of the following: an accelerated graphics port (AGP) or other graphics bus, an enhanced industrial standard architecture (EISA) bus, a front-end bus (FSB), a hypertransport (HT) interconnect, an industrial standard architecture (ISA) bus, an infinite bandwidth interconnect, a low pin count (LPC) bus, a memory bus, a micro channel architecture (MCA) bus, a peripheral component interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a serial advanced technology attachment (SATA) bus, a video electronics standard association local (VLB) bus or other suitable buses. The bus 810 may include one or more buses. Although the embodiments of the present application describe or illustrate a specific bus, the embodiments of the present application may consider any suitable bus or interconnection method.

[0110] In combination with the method in the above embodiments, an embodiment of the present application also provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the process or function of any method in the above embodiments is implemented.

[0111] In addition, an embodiment of the present application further provides a computer program product, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the process or function of any one of the methods in the above embodiments is implemented.

[0112] The above exemplarily describes the flowcharts and / or block diagrams of the methods, devices, systems and computer program products of the embodiments of the present application, and describes the relevant various aspects. It should be understood that each box or combination thereof in the flowchart and / or block diagram can be implemented by computer program instructions, or by dedicated hardware that performs a specified function or action, or by a combination of dedicated hardware and computer instructions. For example, these computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to form a machine that enables these instructions executed by such a processor to enable the implementation of the functions / actions specified in each box or combination thereof in the flowchart and / or block diagram. Such a processor can be a general-purpose processor, a special-purpose processor, a special application processor or a field programmable logic circuit.

[0113] The functional blocks shown in the structured block diagram of the embodiment of the present application can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application-specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc.; when implemented in software, it is a program or code segment used to perform the required task. The program or code segment can be stored in a memory, or transmitted on a transmission medium or a communication link via a data signal carried in a carrier. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

[0114] It should be noted that the present application is not limited to the specific configurations and processes described above or shown in the figures. The above is only a specific implementation mode of the present application. Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working process of the described system, device, module or unit can refer to the corresponding process in the method embodiment without further description. It should be understood that the scope of protection of the present application is not limited to this. Any technician familiar with the technical field can think of various equivalent modifications or substitutions within the technical scope disclosed in the present application, and these modifications or substitutions should be included in the scope of protection of the present application.

Claims

1. A method for safely handling abnormal flashback of an application program, characterized in that: Applied to the terminal, a customized app security processing module is pre-set in the terminal system program of the app, and the app security processing module is used to make the app enter a safe operation mode and perform security processing on the abnormalities when multiple abnormalities occur during the operation of the app; The safe processing method for abnormal app crash includes: When an exception related to app crash occurs during app operation, the app security processing module captures relevant information of the exception and switches the app to a safe operation mode. In the safe operation mode, the app security processing module starts a dynamic container page to replace the app's exception interface and sends a security policy request message to the server. The security policy request message carries the call stack information of the exception, so that the server issues a security processing policy corresponding to the exception. After receiving the security processing policy sent by the server, the security processing policy is executed to enable the app to eliminate the exception, and the security information corresponding to the security processing policy is loaded in the dynamic container page. After the exception is eliminated, the normal operation interface of the app is returned.

2. The method according to claim 1, characterized in that The method further comprises: When the system default exception handler starts the behavior of killing the app due to an exception related to the app crash during the running of the app, the app security processing module intercepts the behavior of killing the app by the exception handler.

3. The method according to claim 1, characterized in that The security processing strategy includes at least one of the following: The first security processing strategy: downloading the patch file according to the address of the patch file sent by the server, and installing the patch file to the terminal; The second security processing strategy: clear the cache and restart or run the switch configuration file sent by the server, where the switch configuration file is used to disable abnormal functions running on the terminal; The third security processing strategy: using a dynamic container page to display alternative content sent by the server and notifying the backend system of the server of the app to handle the exception, wherein the alternative content is the same as part of the content displayed on the page when the app is running normally.

4. The method according to claim 3, characterized in that The alternative content includes: interactive function information, activity information and / or advertising information of the app.

5. The method according to claim 3, characterized in that: Also includes: After receiving the security policy request message, the server determines whether the exception occurs for the first time according to the call stack information, and if it occurs for the first time, sends a third security processing policy to the terminal; If the exception does not occur for the first time and the server stores a patch file corresponding to the exception, the first security processing strategy is sent to the terminal.

6. The method according to claim 5, characterized in that Also includes: If the server does not store a patch file corresponding to the exception, determining whether the exception can be resolved by a second security processing strategy, and if the exception can be resolved by the second security processing strategy, issuing the second security strategy to the terminal; If the exception cannot be resolved by the second security processing strategy, a third security strategy is issued to the terminal.

7. The method according to claim 6, characterized in that The security information corresponding to the first security processing strategy includes: the download progress of the patch; and / or, The security information corresponding to the second security processing strategy includes: prompt content for guiding the user to operate in accordance with the second security strategy.

8. A security processing device for abnormal flash back of an application program, characterized in that: Applied to the terminal, a customized app security processing module is pre-set in the terminal system program of the app, and the app security processing module is used to make the app enter a safe operation mode and perform security processing on the abnormalities when multiple abnormalities occur during the operation of the app; The security processing device for abnormal app flash back includes: A capture module, used for capturing relevant information of an exception by the app security processing module when an exception related to app crash occurs during the app running process; A switching module is used to switch the app to a safe operation mode. In the safe operation mode, the app security processing module starts a dynamic container page to replace the abnormal interface of the app, and sends a security policy request message to the server. The security policy request message carries the call stack information of the exception, so that the server sends a security processing policy corresponding to the exception; The execution module is used to execute the security processing policy sent by the server after receiving the security processing policy so that the app eliminates the exception, and load the security information corresponding to the security processing policy in the dynamic container page, and return to the normal operation interface of the app after the exception is eliminated.

9. An electronic device, characterized in that: The electronic device comprises: a processor and a memory storing computer program instructions; when the electronic device executes the computer program instructions, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the method according to any one of claims 1 to 7 is implemented.

11. A computer program product, characterized in that It comprises computer program instructions, which, when executed by a processor, implement the method according to any one of claims 1 to 7.

Images