KR102051376B1 - System and Method For Processing generation of Crash event, and Device supporting the same - Google Patents

System and Method For Processing generation of Crash event, and Device supporting the same Download PDF

Info

Publication number
KR102051376B1
KR102051376B1 KR1020120120230A KR20120120230A KR102051376B1 KR 102051376 B1 KR102051376 B1 KR 102051376B1 KR 1020120120230 A KR1020120120230 A KR 1020120120230A KR 20120120230 A KR20120120230 A KR 20120120230A KR 102051376 B1 KR102051376 B1 KR 102051376B1
Authority
KR
South Korea
Prior art keywords
app
crash
context
information
terminal
Prior art date
Application number
KR1020120120230A
Other languages
Korean (ko)
Other versions
KR20140054575A (en
Inventor
최윤석
Original Assignee
에스케이플래닛 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 에스케이플래닛 주식회사 filed Critical 에스케이플래닛 주식회사
Priority to KR1020120120230A priority Critical patent/KR102051376B1/en
Publication of KR20140054575A publication Critical patent/KR20140054575A/en
Application granted granted Critical
Publication of KR102051376B1 publication Critical patent/KR102051376B1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/55—Detecting local intrusion or implementing counter-measures
    • G06F21/552—Detecting local intrusion or implementing counter-measures involving long-term monitoring or reporting
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/51—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability

Abstract

The present invention relates to preventing a crash recurrence, and in particular, the present invention is a terminal platform for controlling to collect and store information on the context of the abnormal termination situation and the API call in the context when the abnormal termination occurs while the app is running, the App module that supports app driving and performs API call, API filter for preventing the same API call in the same context of the same app based on the context and API call information according to abnormal termination of the stored specific app Disclosed is a configuration for a terminal supporting crash recurrence prevention, and a system and method for preventing a crash recurrence comprising the same.

Description

System and Method For Processing generation of Crash event, and Device supporting the same}

The present invention relates to preventing a crash recurrence of the terminal, and in particular, by controlling an API that was called when an abnormal termination of a specific app is not used in the app again, a crash recurrence prevention method and system for supporting a crash situation does not recur and supporting the It relates to a terminal.

As communication terminals are manufactured in a portable form, they are used in a wide range of fields due to their convenience and ease of portability. These communication terminals have recently been developed in the form of smart phones equipped with various user functions, providing convenience and entertainment. Since smartphones are provided in the form of terminals equipped with high-performance hardware, users can download and install various applications (hereinafter referred to as 'apps'). Accordingly, in recent years, various apps applied to smartphones have been developed and spread.

On the other hand, apps executed in the terminal frequently occur when the user is not normally executed according to the user operation or the terminal situation. For example, in the case of a specific app, when the load is greater than other apps and is simultaneously operated with other apps, a high load may not be able to perform a normal operation, and in some cases, abnormal termination may occur. Abnormal termination of these apps may occur in the case of including routines that are not compatible with the hardware characteristics of the terminal as well as the above-described load problem, and may also be caused by the communication state of the network to which the terminal is connected. In other words, crashes caused by abnormal termination of the app are caused by various environmental factors.

Accordingly, in certain situations, the app may operate normally, but in other situations, the app may abnormally terminate. From the user's point of view, the user who uses the app of the terminal does not know exactly which element abnormally terminates the app, and if the function of the app is required, the user often uses the app even if the abnormal termination condition is taken. However, if abnormal termination occurs frequently due to the use of such an app, the hardware of the terminal becomes unreasonable, resulting in a decrease in the life of the terminal. In addition, abnormal termination of a specific app may affect other apps, so it is necessary to appropriately perform a crash processing according to abnormal termination of a specific app. However, until now, there is no clear alternative to deal with the occurrence of a crash of a specific app except deleting the crashed app from the corresponding terminal and not using it.

Registered Korean Patent No. 10-0951852, registered on 04/01/2010 (Name: Apparatus and method for blocking abnormal behavior of application program)

Therefore, an object of the present invention is to solve the problems of the prior art as described above, by abnormally terminating the app by managing the history of the crash occurs when running the app of the terminal to limit a specific API call of the app in the same situation The present invention provides a method and system for preventing a crash recurrence and a terminal supporting the crash.

In addition, the present invention by collecting and delivering accurate information about the crash situation of the terminal to allow the app developer to modify the appropriate app, ultimately to crash more quickly and accurately to the crash problem that occurs when running the app A method and system for preventing recurrence and a terminal supporting the same are provided.

In order to achieve the above object, the present invention collects information on an API call in the context and context of an abnormal termination situation when an abnormal termination occurs while driving an app, and prevents the same API call in the same context of the same app based on this. Preventing the recurrence of a crash, characterized in that it comprises a terminal, an app management support device for generating the app update information for supplementing the app based on the context information and API call information of a specific app collected by the terminal and providing it to the terminal Start the configuration of the system.

The present invention also collects information on the context of the abnormal termination situation and the API call in the context when an abnormal termination occurs while the app is running, the terminal platform for controlling to store and manage the application, supports the application driving and performs the API call App module, a terminal supporting a crash recurrence prevention, characterized in that it comprises an API filter for preventing the same API call in the same context of the same app based on the context and API call information according to abnormal termination of a specific stored app Initiate.

The terminal further includes a storage that stores context information and API call information for each specific app.

On the other hand, the terminal platform supports driving an app when a request to start an app having a crash history occurs, and can pass an API call in a context having a crash history while the app is running to an API filter, and calls other contexts and other API calls of the app. Whenever the crash event generated by the event occurs, the collected context information and API call information in the corresponding context may be accumulated and stored.

The API filter may control to output a warning window for an API call in a context having a crash history, and the terminal may further include a display unit for outputting guide information for guiding abnormal termination caused by the API call in the context. have.

The terminal may further include a communication unit for transmitting context information and API call information according to a crash event of a specific app to the app management support device.

The present invention also includes the steps of driving a specific app in the terminal, collecting API information and context information called when a crash event corresponding to abnormal termination of the driving of the app, blocking the same context and API calls of the same app Disclosed is a configuration of a crash recurrence prevention method comprising the steps of:

The method includes accumulating and storing corresponding context information and API call information for each crash event caused by different contexts and API calls when the same app is running, and for API calls having a crash history when an API call occurs in the same context of the same app. It may further include a step of outputting a warning window for.

The method may further include transmitting context information and API call information according to a crash event of a specific app to the app management supporting device, and supporting app management information of the app update information in which the terminal supplements context information and API call information according to the crash event. Receiving from the device, the terminal may further include updating the installed app based on the received app update information.

The invention also discloses a configuration of a computer readable recording medium having recorded thereon a program for executing the above method.

As described above, according to the method and system for preventing a crash recurrence according to the present invention and a terminal supporting the present invention, the present invention can prevent a crash recurrence by limiting the use of an API having a crash history among APIs used for driving an app. To help.

In addition, the present invention can support the accurate collection of information about the crash situation and the modification based on the app can be performed more quickly and accurately.

1 is a view schematically showing the configuration of a terminal supporting a crash recurrence prevention according to an embodiment of the present invention.
FIG. 2 is a diagram illustrating in more detail a control unit configuration of the terminal configuration of FIG. 1; FIG.
Figure 3 is a view for explaining a crash relapse prevention method of the present invention.
4 is a view schematically showing the configuration of the crash relapse prevention system of the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

In describing the embodiments, descriptions of technical contents that are well known in the art to which the present invention pertains and are not directly related to the present invention will be omitted. In addition, detailed description of components having substantially the same configuration and function will be omitted.

For the same reason, some components in the accompanying drawings are exaggerated, omitted, or schematically illustrated, and the size of each component does not entirely reflect the actual size. Therefore, the present invention is not limited by the relative size or spacing drawn in the accompanying drawings.

1 is a diagram illustrating a configuration of a terminal supporting crash recurrence prevention according to an exemplary embodiment of the present invention.

Referring to FIG. 1, the terminal 100 supporting crash recurrence prevention of the present invention includes a communication unit 110, an input unit 120, a display unit 140, a storage unit 150, and a controller 160.

When the input event for requesting a specific app activation occurs, the terminal 100 of the present invention having such a configuration supports activating an app according to the corresponding input event. In this process, the terminal 100 may call various APIs for driving an app and perform a function support necessary for driving the app based on this. On the other hand, the terminal 100 collects and manages a context (Context) for the call and requested API information when abnormal termination occurs in the process of calling an API to perform a specific app driving. In addition, the terminal 100 drives an app when an input event for driving the app is generated, and if an API call request to the context and context that was collected at abnormal termination occurs, the terminal 100 does not perform the API call to terminate the abnormal termination of the app. Can be prevented.

Accordingly, the terminal 100 of the present invention can support the occurrence of repeated abnormal termination by managing a history of a specific app where a crash event occurs. In particular, by performing context management together, the terminal 100 may support to suppress API calls in abnormal termination situations corresponding to a specific context, rather than simply inhibiting API calls at abnormal termination times. The crash recurrence prevention function support may be applied to at least some of all apps stored in the terminal 100, and a plurality of contexts and information management for preventing API calls in the corresponding context may be applied to a specific app.

The communication unit 110 is a component that performs a communication function of the terminal 100. The communication unit 110 supports access to an app store supporting device that provides an app for installing a specific app on the terminal 100, and receives the specific app provided by the app store supporting device according to a user's selection. It can be supported to be installed in the terminal 100 according to the control. On the other hand, the communication unit 110 may be activated under the control of the control unit 160 when receiving information from the network in a specific app driving process, and supports information transmission and reception performed in the corresponding app driving process. In this process, the communication unit 110 may support transmission and reception of specific data according to calls of various APIs for driving the corresponding app.

In addition, the communication unit 110 of the present invention may perform a role of transmitting a context and API information of a specific app managed according to a crash event to an app management supporting device described later. The communicator 110 may receive app update information generated for crash suppression from an app management support device based on context and API information of a specific app related to the crash event. The received app update information may be used to update the app under the control of the controller 160.

The input unit 120 is a component that supports generation of an input event of the terminal 100. The input unit 120 may be configured with various types of keys such as a button key, a keypad, a side key, and a home key. In addition, the touch panel may be configured to include a touch panel constituting the display unit 140 and touch maps output to the display panel in terms of generating an input event.

The input unit 120 may generate an input signal for selecting a specific app among at least one app provided by the terminal 100, various input signals for controlling a specific function of the app while the app is running, and an input signal for terminating the app. Can be. In addition, the input unit 120 may generate an input signal for requesting the installation of an app or an input signal for requesting the deletion of an installed app. In addition, the input unit 120 may generate an input signal for removing a warning window or the like output to the display unit 140 to suppress the recurrence of the crash of the app. The input signal generated by the input unit 120 may be transmitted to the controller 160 to operate as a command according to the corresponding input signal.

The display unit 140 outputs various screens related to driving of the terminal 100. For example, the display unit 140 may display a standby screen, a menu screen, and the like. In addition, the display unit 140 may display an icon or a menu item corresponding to at least one of various apps installed in the terminal 100. If the icon or menu item corresponding to the specific app is selected, the display unit 140 may display a driving screen of the app corresponding to the selected item.

In particular, the display unit 140 of the present invention may display a crash event storage management screen according to abnormal termination of an app when abnormal termination occurs while driving a specific app. In addition, the display unit 140 may support an output of a warning window for suppressing the same context and API call when a specific app having a crash history is driven. A specific API can be called according to the input signal generation for performing a specific function of the app, and the output of the warning window can output a warning window when such an input signal is generated to inform that abnormal termination of the app can occur due to the corresponding input signal. .

The controller 160 may suppress an API call that is predicted to cause abnormal termination and control to ignore an input signal for the API call. Meanwhile, the warning window output on the display unit 140 may include guide information for guiding abnormal termination of the application according to a specific input signal or a specific API call in a specific situation of a specific app.

The storage unit 150 stores various programs and data related to driving the terminal 100. In particular, the storage unit 150 may store respective app related information for driving a plurality of apps. App-related information includes an executable file required to run the app. In particular, the storage unit 150 may store context and API call information on the occurrence of a crash event of a specific app in order to support the crash recurrence prevention function of the present invention. The crash occurrence context and API call information of a specific app stored in the storage 150 may be referenced by the controller 160 when the specific app is driven.

Execution data and data supporting execution of a specific app stored in the storage unit 150 may be updated by app update information provided by the app management support device. In particular, when the communication unit 110 receives the app update information produced to supplement the crash occurrence context and the API call, the storage unit 150 may update the app related information based on the app update information.

The controller 160 is a component that supports processing of various input signals related to driving the terminal 100 and processing, storing, and transmitting data. In particular, the control unit 160 confirms the occurrence of the crash event during the driving process of each app to support the crash recurrence prevention function of the present invention, and supports to manage and manage the context and API call information at the time of the crash event occurs. The controller 160 may prevent abnormal termination of the app by suppressing the same context and the same API call while the same app is running. To this end, the controller 160 may include a configuration as shown in FIG. 2.

2 is a view showing in more detail the configuration of the control unit 160 of the terminal 100 to support the crash recurrence prevention according to an embodiment of the present invention.

Referring to FIG. 2, the controller 160 of the present invention may include an app module 163 including a terminal platform 161 and an API filter 165.

The terminal platform 161 is configured to support overall signal processing and routine processing, data storage control and transmission control for supporting various user functions of the terminal 100. The terminal platform 161 may include various platforms such as iOS, Mac OS, and Android OS. The app module 163 may be disposed on the terminal platform 161. For example, when an input event for driving a specific app occurs, the terminal platform 161 calls the app related information indicated by the input event in the storage unit 150 and configures the app module 163 for driving the app. . In this case, the terminal platform 161 may support various information linkages to the app module 163 to drive the app. That is, the terminal platform 161 transmits an input signal generated for driving the app among the input events generated by the input unit 120 to the app module 163.

In addition, the terminal platform 161 may support to output the screen information corresponding to the driving of the app from the app module 163 to the display unit 140. In addition, the terminal platform 161 activates the communication unit 110 when the communication channel is formed to drive the app, and forms a data transfer path so that the communication channel generated based on the communication unit 110 is linked to the app module 163. can do.

In particular, the terminal platform 161 of the present invention manages the context generation and various API calls of the app module 163 operating for driving the app. The terminal platform 161 collects the context at the time of occurrence of the crash event and API information called through the context when the crash event occurs due to abnormal termination while the app is running based on the app module 163. In addition, the terminal platform 161 may manage the collected context and API call information as a crash occurrence history for preventing a crash recurrence. In this process, the terminal platform 161 may support to store a crash occurrence history of a specific app in the storage 150.

The API filter 165 receives crash triggering context and API information related to the app module 163 stored in the terminal platform 161 or stored in the storage 150. In addition, the API filter 165 blocks a corresponding API call when a crash inducing context and an API call occur according to the operation of the app module 163. In addition, the API filter 165 may support to output the warning window to the display unit 140. That is, the API filter 165 may support not to make an API call of a specific app or to output a warning window informing that an abnormal termination of the app may occur due to a specific API call.

The app module 163 is a component that includes various routines that support specific app functionality. This app module 163 is formed of software routines that run on the terminal platform 161. In particular, the app module 163 may receive various input signals according to the support of the terminal platform 161 and perform a predefined operation according to the corresponding input signal. In this process, the app module 163 calls an API provided by the terminal platform 161 and performs an operation according to a corresponding input signal or preset schedule information based on the called API.

In addition, the app module 163 may support to output the information according to the operation through the display unit 140 or the like. Meanwhile, the app module 163 may receive an API from the terminal platform 161 through the API filter 165, and thus may receive a response to a specific API call through the API filter 165. When performing an API call with a crash history in this process, the app module 163 may support receiving the guide information and the warning window about the API not available from the API filter 165 and outputting it to the display unit 140. have.

As described above, the terminal 100 that supports the crash recurrence prevention function according to an embodiment of the present invention performs a history management for a crash event when a specific app driving process occurs, thereby causing abnormal termination of the same app repeatedly. You can help prevent this from happening. Accordingly, the terminal 100 of the present invention prevents hardware damage due to repetitive abnormal termination and supports proper app driving.

3 is a flowchart illustrating a crash recurrence prevention method according to an embodiment of the present invention.

Referring to FIG. 3, in the crash relapse prevention method of the present invention, first, the control unit 160 of the terminal 100 supplies power to each component of the terminal 100 to drive the terminal when the power is supplied from the power supply unit in step S101. To pass. After that, when the input event occurs, the controller 160 checks whether the input event is for executing the app in step S103. If it is not an input event for executing the app in this step, the controller 160 branches to step S105 to support the performance of a function according to the corresponding input event. For example, the controller 160 may support a call function, a sleep mode switching function, and the like of the terminal 100.

Meanwhile, when the input event generated in step S103 is an input event for executing a specific app, the controller 160 branches to step S107 and checks whether the app selected by the input event has a crash occurrence history. If the selected app is an app without a history of crash occurrence, the controller 160 may branch to step S109 to execute an API function for executing an app function and executing the corresponding function. The controller 160 checks whether abnormal termination occurs while performing an app function in step S111. If abnormal termination occurs in step S111, the controller 160 records a context and a crash causing API in step S113.

On the other hand, if the abnormal termination does not occur in step S111, the controller 160 branches to step S115 to check whether an input event for normal termination occurs, and if an input event for normal termination occurs, branches to step S103 to perform the following process. Can be re-executed. If there is no input event for normal termination in step S115, the controller 160 branches to step S109 and may support execution of the selected app function.

If the app selected in step S107 is a crash occurrence history app, the controller 160 branches to step S117 and controls to drive the app with a history of crash occurrence. In addition, the controller 160 checks the crash occurrence history of the corresponding app stored in the terminal platform 161 or the storage 150. In addition to checking the crash occurrence history, the controller 160 checks whether there is an API called in the context written in the crash occurrence history to execute the S119 app function. If there is a corresponding API call, the controller 160 branches to step S121 to control to block the corresponding API call. The controller 160 may control to skip step S121 when there is no API called in the context according to the crash occurrence history.

Thereafter, the controller 160 checks whether there is an input event for terminating the app function in step S123. In addition, if there is no input event for terminating the corresponding app function, the controller 160 branches to step S117 and may control support of an app function having a crash history. On the other hand, the control unit 160 may support to perform the following process again by branching before step S103 when an input event for ending the app function occurs.

As described above, the crash recurrence prevention method according to an exemplary embodiment of the present invention may support driving of an app while supporting a crash call API call when there is a crash history according to whether or not there is a crash history of the app. Accordingly, the present invention can support an application function that a user should use without crashing. In addition, the present invention can support to collect the crash history by monitoring whether there is a crash occurred for the app without the crash history. In addition, the terminal 100 of the present invention may support collecting an additional crash occurrence history and collecting context and API call information according to the crash history app. In addition, the present invention can provide crash history information through the app management support system 10 as shown in FIG.

4 is a diagram schematically showing the configuration of the app management support system 10 of the present invention.

Referring to FIG. 4, the app management support system 10 of the present invention includes the configuration of the terminal 100 and the app management support device 200, and the data between the configuration of the terminal 100 and the app management support device 200. It may further include a configuration of the communication network 300 for delivery.

The app management support system 10 having such a configuration collects a crash causing context and API call information according to the abnormal termination, and manages the app through the communication network 300 when abnormal termination occurs while the terminal 100 operates the app. Transfer to the support device 200. Then, the app management support apparatus 200 performs a crash occurrence supplementation for the corresponding app by referring to the received crash inducing context and API call information. That is, the app management support device 200 supports to provide the corresponding app update information to the terminal 100 after performing an app modification or debugging to remove the crash of the app. Accordingly, the terminal 100 may suppress an additional crash by modifying an app having a bug with app update information.

To this end, the terminal 100 is connected to the app management support device 200 through the communication network 300, and provides the crash management context information and API call information to the app management support device 200. As described above, the terminal 100 supports the terminal platform 161 to monitor the APIs according to the driving of the app module 163, and if abnormal termination occurs in this process, the terminal information 161 may call the API information and the context information. Collect. In addition, the terminal 100 may provide the collected API information and context information to the app management support device 200 together with the corresponding app identification information. Meanwhile, the terminal 100 may receive app update information from the app management support device 200 in relation to an app providing the app identification information, the API information, and the context information. Upon receiving the app update information, the terminal 100 may support at least some data of the pre-installed app by replacing the app update information with the same crash event.

App management support device 200 is configured to support the connection of at least one terminal 100 through the communication network 300, and to store and manage the crash-related information provided by the terminal 100. In particular, the app management support apparatus 200 may collect source information on the corresponding app based on the app identification information provided by the specific terminal 100 and may support debugging based on context information and API information. . To this end, the app management support apparatus 200 may output context information and API information, app source information, or provide corresponding context information and API information to an app creator.

The app management support apparatus 200 may collect app update information generated based on the context information and the API information. When the app update information is collected, the app management support apparatus 200 may support providing the app update information to the terminal 100 providing the context information and the API information about the corresponding app. To this end, the app management support apparatus 200 may store and manage connection information of at least one terminal 100 providing context information and API information.

Meanwhile, when receiving the context information and the API information from a plurality of different terminals 100, the app management support apparatus 200 may support to generate the app update information by debugging. As a result, the crash recurrence prevention function of the present invention supports only one occurrence of a crash event for a specific app in the terminal 100, so that context information and API information collected according to the crash occurrence are also collected only once. Therefore, the app management support apparatus 200 may recognize that a universal bug occurs when the same context and API information for the same app collected from the terminals 100 are received, and may request debugging of the corresponding app.

The communication network 300 may support communication channel formation for data transmission and signal transmission between components of the app management support system 10. That is, the communication network 300 may establish a communication channel between the terminal 100 and the app management support apparatus 200, and may support data transmission and reception between the terminal 100 and the app management support apparatus 200. For example, the communication network 300 supports transmitting the context information and the API information to the app management support device 200 along with the app identification information when the crash generated by the terminal 100 occurs. Here, the crash-related context information and API call information provided by the terminal 100 may be supported to be provided to the app management support device 200 in a push type without performing a separate connection process or an authentication process of the app management support device 200. .

The communication network 300 may be provided in a form including at least one of a variety of communication networks for the above-described data transfer. That is, the communication network 300 may include various networks for connecting the terminal 100 and the app management support apparatus 200. For example, the communication network 300 may include a mobile communication network, a radio access network, etc. to support the terminal 100, and may include an internet network for connecting the app management support device 200.

Accordingly, the communication network 300 of the present invention is not limited to the form or configuration of a specific communication network, but at least one of various types of networks forming a communication channel for transmitting crash-related information in the terminal 100 of the present invention. It can be understood as being in the form. For example, the communication network 300 may be configured with network devices capable of supporting each or integrally an LTE communication network, a WiFi communication network, a 3G communication network, a 2G communication network, or the like to support various communication functions.

As described above, a system and method for supporting a crash recurrence prevention function according to an embodiment of the present invention support a crash event not occurring in the same situation of a corresponding app when a crash event is generated by a specific app. In addition, the present invention can support the supplementation of the app itself by providing information at the time of the crash occurrence to the app management support device 200 to supplement the app according to the crash event occurs.

Meanwhile, in the case of supporting the crash recurrence prevention function according to the above-described embodiments of the present disclosure, the crash recurrence prevention function may be implemented in the form of program instructions that may be executed by various computer means and may be recorded in a computer-readable recording medium. In this case, the computer-readable recording medium may include program instructions, data files, data structures, and the like, alone or in combination. Meanwhile, the program instructions recorded on the recording medium may be those specially designed and configured for the present invention, or may be known and available to those skilled in computer software.

Computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tape, optical media such as CD-ROMs and DVDs, and magnetic disks such as floppy disks. Magnetic-Optical Media, and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. In addition, program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. The hardware device described above may be configured to operate as one or more software modules to perform the operations of the present invention.

In the above description about the crash recurrence prevention function support according to an embodiment of the present invention for the preferred embodiments through the specification and drawings, although specific terms have been used, it is only easy to describe the technical content of the present invention and to understand the invention It is only used in a general sense to help the invention, the present invention is not limited to the above-described embodiment. That is, various embodiments based on the technical idea of the present invention are possible to those skilled in the art.

The present invention relates to a system and method for preventing a crash recurrence and a terminal supporting the same, and the present invention prevents abnormal termination of a specific app repeatedly so that the user can use the app more smoothly.

Accordingly, the present invention can reduce unnecessary time waste caused by the termination of the app by suppressing the repeated occurrence of abnormal termination of the corresponding app, and thereby achieve terminal hardware protection.

10: Crash Recurrence Prevention System
100: terminal 110: communication unit
120: input unit 140: display unit
150: storage unit 160: control unit
161: terminal platform 163: app module
165: API Filter 200: App Management Supported Devices
300: communication network

Claims (15)

delete A terminal platform configured to collect information about a context of the abnormal termination situation and API calls in the context and store and manage the collected information when a crash event corresponding to abnormal termination occurs while an app is running;
An app module supporting the app driving and making an API call; And
When a specific app with an abnormally terminated history is driven while the app is running, blocking an API call in a context that causes an abnormal termination of the specific app based on context and API call information according to the abnormal termination of the stored specific app. An API filter;
A terminal supporting a crash recurrence prevention comprising a. delete delete delete delete delete delete Running an app on the terminal;
Collecting context information of an abnormal termination situation and information on an API call in the context when a crash event corresponding to abnormal termination occurs while the app is running; And
Blocking an API call in a context that causes an abnormal termination of the specific app based on information on a context and an API call according to the abnormal termination of the stored specific app when the specific app having the abnormally terminated history is driven;
Crash relapse prevention method comprising a. The method of claim 9,
Accumulating and storing corresponding context information and API call information for each crash event generated by another context and API call when the specific app is driven;
Crash relapse prevention method further comprising a. delete The method of claim 9,
Transmitting context information and API call information according to a crash event of the specific app to an app management support device;
Crash relapse prevention method further comprising a. delete delete delete
KR1020120120230A 2012-10-29 2012-10-29 System and Method For Processing generation of Crash event, and Device supporting the same KR102051376B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020120120230A KR102051376B1 (en) 2012-10-29 2012-10-29 System and Method For Processing generation of Crash event, and Device supporting the same

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020120120230A KR102051376B1 (en) 2012-10-29 2012-10-29 System and Method For Processing generation of Crash event, and Device supporting the same

Publications (2)

Publication Number Publication Date
KR20140054575A KR20140054575A (en) 2014-05-09
KR102051376B1 true KR102051376B1 (en) 2019-12-03

Family

ID=50886407

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020120120230A KR102051376B1 (en) 2012-10-29 2012-10-29 System and Method For Processing generation of Crash event, and Device supporting the same

Country Status (1)

Country Link
KR (1) KR102051376B1 (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100951852B1 (en) * 2008-06-17 2010-04-12 한국전자통신연구원 Apparatus and Method for Preventing Anomaly of Application Program

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100717241B1 (en) * 2005-08-02 2007-05-11 엔에이치엔(주) Error management system and method using the same

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100951852B1 (en) * 2008-06-17 2010-04-12 한국전자통신연구원 Apparatus and Method for Preventing Anomaly of Application Program

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Jun Xu et al, "Automatic Diagnosis and Response to Memory Corruption Vulnerabilities", ACM Conference on Computer and Communications Security(2005.)*

Also Published As

Publication number Publication date
KR20140054575A (en) 2014-05-09

Similar Documents

Publication Publication Date Title
JP5691090B2 (en) Widget management method and apparatus for portable terminal
EP3096224B1 (en) Method and apparatus for processing application installation package
CN103473163A (en) Application program detection method and device
CN103164229A (en) Method and device for clearing progresses of mobile terminal
US20080141283A1 (en) Application Controlling Apparatus And Storage Medium Which Stores Software For The Apparatus
CN103106092A (en) System software updating method and device in terminal appliance
CN105373419A (en) Background application operation method and system
CN105760200A (en) Terminal device and system updating method thereof
EP1834236A2 (en) Management of persistent software applications
CN104794014A (en) System operation method and intelligent terminal
CN111078471B (en) System fault recovery method and device for display device and computer storage medium
CN103810416A (en) Software installation or uninstallation method and device
CN104572217A (en) Updating method and system of wearable intelligent device
CN103235703B (en) Preset resource storage method and apparatus
CN112416411B (en) Upgrading method and device, equipment end, server and computer readable medium
CN104360880A (en) Application installing method and electronic equipment
CN104184754A (en) Method for automatically updating applications and contents, terminal, platform and system thereof
WO2015154700A1 (en) Method and apparatus for repairing dynamic link library file
KR102051376B1 (en) System and Method For Processing generation of Crash event, and Device supporting the same
KR101434094B1 (en) Blocking harmful application by intent monitoring in android platform
KR20140134868A (en) Terminal and operating method thereof
KR102083473B1 (en) System and Method For Processing of Crash Information, and Apparatus and Device supporting the same
CN109117180B (en) Program integration method and device
CN104932819A (en) Mobile terminal and control method thereof
CN115361470B (en) Method and device for limiting mobile terminal APP operation network environment

Legal Events

Date Code Title Description
A201 Request for examination
E902 Notification of reason for refusal
E701 Decision to grant or registration of patent right
GRNT Written decision to grant