System and method for verifying apps for smart phone

Abstract

A system and method for verifying apps for a smart phone are provided. The system for verifying apps for a smart phone includes an app auto-verification device and an app self-verification device. The app auto-verification device analyzes the installation tile of an app to be installed in the smart phone, constructs a scenario, executes the app in the smart phone in accordance with the scenario, and determines malicious behavior using the results of the execution. The app self-verification device monitors an installation file corresponding to an app to be installed in the smart phone, and determines malicious behavior by analyzing a behavioral log corresponding to results of the monitoring.

Claims

What is claimed is: 1 . A system for verifying apps for a smart phone, comprising: an app auto-verification device for analyzing an installation file of an app to be installed in the smart phone, constructing a scenario, getting the app to be executed in the smart phone in accordance with the scenario, and determining malicious behavior using results of the execution of the app; and an app self-verification device for monitoring an installation file corresponding to an app installed in the smart phone, and determining malicious behavior by analyzing a behavioral log corresponding to results of the monitoring. 2 . The system as set forth in claim I, wherein the app auto-verification device comprises: an app management unit for analyzing the installation file of the app, identifying specific conditions under which individual functions of the app can be executed, and constructing the scenario based on results of the identification; and a malicious behavior detection unit for receiving and analyzing the behavioral log corresponding to the results of the execution of the app from the smart phone, and determining the malicious behavior based on results of the analysis. 3 . The system as set forth in claim 2 , further comprising a storage unit for storing results of the determination of the malicious behavior obtained by the malicious behavior detection unit 4 . The system as set forth in claim 3 , wherein the system transfers the results stored in the storage unit to the smart phone, when a request for verification of an app which is identical to the app installed in the smart phone is received. 5 . The system as set forth in claim 1 , wherein the app self-verification device comprises an installation file determination unit for examining whether a pattern of the malicious behavior has been included in the installation file. 6 . A method of verifying apps for a smart phone, the method comprising: selecting an app for a smart phone for verification; downloading the selected app for the smart phone from an app market, and analyzing an installation file of the downloaded app; constructing a scenario based on results of the analysis of the installation file of the app; installing an app corresponding to the scenario in the smart phone, and transmitting execution commands to the smart phone in accordance with the scenario; and verifying the app for the smart phone by receiving results corresponding to the execution commands and then determining malicious behavior. 7 . The method as set forth in claim 6 , wherein the verifying comprises: receiving a behavioral log corresponding to the execution commands from the smart phone, and analyzing the behavioral log; and determining the malicious behavior based on results of the analysis. 8 . A method of verifying apps for a smart phone, the method comprising: receiving a request for verification of an app from a smart phone; installing an app corresponding to the request for verification; recording a behavioral log corresponding to results of execution of the installed app; and verifying the app for the smart phone by analyzing the behavioral log and then determining malicious behavior of the app. 9 . The method as set forth in claim 8 , further comprising, if results of verification of an app corresponding to the request for verification already exist, transmitting the results of verification to the smart phone. 10 . The method as set forth in claim 8 , wherein the verifying comprises verifying the app for the smart phone by determining whether a pattern of malicious behavior has been included in an installation file included in the request for verification.
CROSS REFERENCE TO RELATED APPLICATION [0001] This application claims the benefit of Korean Patent App No. 10-2011-0117594, filed on Nov. 11, 2011, which is hereby incorporated by reference in its entirety into this application. BACKGROUND OF THE INVENTION [0002] 1. Technical Field [0003] The present invention relates generally to a system and method for verifying apps (applications) for a smart phone and, more particularly, to a system and method for verifying apps for a smart phone, which are capable of examining smart phone apps for malicious behavior. [0004] 2. Description of the Related Art [0005] With the transition from conventional general mobile phones (for example, feature phones) to smart phones, the number of malicious apps for smart phones tends to be increasing. [0006] As the hardware of smart phones becomes more advanced and application programs for smart phones are more diversified and complicated, the possibility of malware causing serious damage to smart phones is increasing. In particular, in line with the spread of wireless mobile Internet service such as WiBro, a variety of types of mobile malware, which attack the weakness of application programs and services for mobile terminals such as Bluetooth and a Multimedia Messaging System (MMS), are appearing. Such a variety of types of malware may cause serious damage, such as the erroneous operation of a smart phone, the deletion of data or the leakage of personal information. Accordingly, there is a need for a countermeasure which is capable of effectively protecting smart phones against a variety of types of malware. SUMMARY OF THE INVENTION [0007] Accordingly, the present invention has been made keeping in mind the above problems occurring in the prior art, and an object of the present invention is to provide a system and method for verifying apps for a smart phone, which are capable of performing auto-verification and self-verification related to the malicious behavior of apps for a smart phone. [0008] In order to accomplish the above object, the present invention provides a system for verifying apps for a smart phone, including an app auto-verification device for analyzing an installation file of an app to be installed in the smart phone, constructing a scenario, executing the app in the smart phone in accordance with the scenario, and determining malicious behavior using results of the execution; and an app self-verification device for monitoring an installation file corresponding to an app to be installed in the smart phone, and determining malicious behavior by analyzing a behavioral log corresponding to results of the monitoring. [0009] The app auto-verification device may include an app management unit for analyzing the installation file of the app, identifying specific conditions under which individual functions of the app can be executed, and constructing the scenario based on results of the identification; and a malicious behavior detection unit for receiving and analyzing the behavioral log corresponding to the results of the execution from the smart phone, and determining the malicious behavior based on results of the analysis. [0010] The system may further include a storage unit for storing results of the determination of the malicious behavior obtained by the malicious behavior detection unit. [0011] When a request for verification of an app which is the same as the app installed in the smart phone is received, the results stored in the storage unit may be transferred to the smart phone. [0012] The app self-verification device may include an installation file determination unit for examining whether the pattern of the malicious behavior has been included in the installation file. [0013] Additionally, in order to accomplish the above object, the present invention provides a method of verifying apps for a smart phone, wherein a system for verifying apps for a smart phone verifies apps while operating in conjunction with an app market and a smart phone, the method including selecting an app for the smart phone for verification; downloading the selected app for the smart phone from the app market, and analyzing an installation file of the downloaded app; constructing a scenario based on results of the analysis of the installation file of the app; installing an app corresponding to the scenario in the smart phone, and transmitting execution commands to the smart phone in accordance with the scenario; and verifying the app for the smart phone by receiving results corresponding to the execution commands and then determining malicious behavior. [0014] The verifying may include receiving a behavioral log corresponding to the execution commands from the smart phone, and analyzing the behavioral log; and determining the malicious behavior based on results of the analysis. [0015] Additionally, in order to accomplish the above object, the present invention provides a method of verifying apps for a smart phone, wherein a system for verifying apps for a smart phone verifies apps while operating in conjunction with an app market and a smart phone, the method including receiving a request for verification of an app from the smart phone; installing an app corresponding to the request for verification; recording a behavioral log corresponding to results of execution of the installed app; and verifying the app for the smart phone by analyzing the behavioral log and then determining malicious behavior of the app. [0016] The method may further include, if results of verification of an app corresponding to the request for verification exist, transmitting the results of verification to the smart phone. [0017] The verifying may include verifying the app for the smart phone by determining whether a pattern of malicious behavior has been included in an installation file included in the request for verification. BRIEF DESCRIPTION OF THE DRAWINGS [0018] The above and other objects, features and advantages of the present invention will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which: [0019] FIG. 1 is a diagram schematically illustrating an environment to which a system for verifying apps for a smart phone according to an embodiment of the present invention is applied; [0020] FIG. 2 is a diagram showing the configuration of an app auto-verification device according to a first embodiment of the present invention; [0021] FIG. 3 is a diagram showing the configuration of a smart phone according to the first embodiment of the present invention; [0022] FIG. 4 is a flowchart illustrating a method for automatically verifying an app for a smart phone according to the first embodiment of the present invention; [0023] FIG. 5 is a diagram showing the configuration of a smart phone according to a second embodiment of the present invention: [0024] FIG. 6 is a diagram showing the configuration of an app self-verification device according to the second embodiment of the present invention; and [0025] FIG. 7 is a flowchart illustrating a method of performing self-verification on an app for a smart phone according to the second embodiment of the present invention. DESCRIPTION OF THE PREFERRED EMBODIMENTS [0026] Reference now should be made to the drawings, throughout which the same reference numerals are used to designate the same or similar components. [0027] The present invention will be described in detail below with reference to the accompanying drawings. Repetitive descriptions and descriptions of known functions and constructions which have been deemed to make the gist of the present invention unnecessarily vague will be omitted below. The embodiments of the present invention are provided in order to fully describe the present invention to a person having ordinary skill in the art. Accordingly, the shapes, sizes, etc. of elements in the drawings may be exaggerated to make the description clear. [0028] A system and method for verifying apps for a smart phone according to embodiments of the present invention will be described in detail below with reference to the accompanying drawings. [0029] FIG. 1 is a diagram schematically illustrating an environment to which a system 10 for verifying apps for a smart phone according to an embodiment of the present invention is applied. [0030] Referring to FIG. 1 , the system 10 for verifying apps (applications) for a smart phone according to the embodiment of the present invention performs an app auto-verification process and an app self-verification process while operating in conjunction with an app market APPs (hereinafter referred to as an “app market”) 20 and a smart phone 30 . For this purpose, the system 10 for verifying apps for a smart phone includes an app auto-verification device 100 and an app self-verification device 200 . Although the system 10 for verifying apps for a smart phone according to the embodiment of the present invention is illustrated as including the app auto-verification device 100 and the app self-verification device 200 , the present invention is not limited thereto. [0031] The app auto-verification device 100 automatically performs the process of downloading an app from the app market 20 , and installing, executing and analyzing the app (an app auto-verification process). Furthermore, the app auto-verification device 100 analyzes the installation file of the app to be installed in the smart phone 30 , identifies specific conditions under which malicious behavior can be revealed, constructs a scenario based on identification results, and causes the malicious behavior to be revealed (a scenario-based malicious behavior triggering process). Here, the malicious behavior is, for example, behavior in which specific malware is applied to an app and prevents the normal operation of the app from being performed, but is not limited thereto. [0032] The app auto-verification process is the process of automatically performing the download, installation, execution and analysis of an app in order to reduce consumptive efforts which are made to repeatedly perform the download, installation, execution and analysis of the app so as to analyze the app to be installed in the smart phone 30 . Furthermore, the scenario-based malicious behavior triggering process is the process of detecting malicious behavior which is performed only under specific conditions. The malicious app may be a malicious app which performs malicious behavior immediately after it is executed, or a malicious app which performs malicious behavior when specific conditions are fulfilled. Accordingly, the scenario-based malicious behavior triggering process includes the process of identifying specific conditions and the process of constructing a scenario so that specific conditions can be fulfilled and then revealing malicious behavior. [0033] The app auto-verification device 100 receives a log of behavior (hereinafter also referred to as the “behavioral log”), corresponding to the app installed in the smart phone 30 , from the smart phone 30 , and determines whether behavior is malicious based on the received behavioral log. [0034] The app self-verification device 200 downloads an app from the app market 20 , installs and executes the app in the smart phone 30 , monitors its access to important resources, and records monitoring results in a behavioral log. Thereafter, the app self-verification device 200 determines malicious behavior by analyzing the behavioral log. Furthermore, the app self-verification device 200 checks for the pattern of malicious behavior using binary file static analysis. [0035] The smart phone 30 operates in conjunction with the app auto-verification device 100 and the app self-verification device 200 which are included in the system 10 for verifying apps for a smart phone. [0036] According to a first embodiment of the present invention, the smart phone 30 receives an app installation command from the app auto-verification device 100 , and installs and executes the corresponding app. Here, the smart phone 30 executes the app using a dynamic behavior analysis process, and records various types of behavior corresponding to execution results in a log (hereinafter referred to as a “behavioral log”). Here, the dynamic behavior analysis process is the process of modifying the Operating System (OS) of the smart phone 30 , causing additional information, such as an Application Programming interface (API) and a parameter invoked by an app, to be recorded in a log, and analyzing a log obtained by installing and executing the app on the modified OS, thereby determining malicious behavior. [0037] According to a second embodiment of the present invention, the smart phone 30 automatically transmits the installation file and additional information of the installed app to the app self-verification device 200 . [0038] Thereafter, the app auto-verification device 100 according to the first embodiment of the present invention will now be described in detail with reference to FIG. 2 . [0039] FIG. 2 is a diagram showing the configuration of the app auto-verification device 100 according to the first embodiment of the present invention. [0040] First, the app auto-verification device 100 according to the first embodiment of the present invention may be implemented in a specific PC, but is not limited thereto. Furthermore, the smart phone 30 which operates in conjunction with the app auto-verification device 100 may correspond to a device which performs a dynamic behavior analysis process, but is not limited thereto. [0041] Referring to FIG. 2 , the app auto-verification device 100 includes an app management unit 110 , a malicious behavior detection unit 120 , and a storage unit 130 . [0042] The app management unit 110 downloads an app to be verified from the app market 20 , and installs the downloaded app. Furthermore, the app management unit 110 identifies specific conditions under which the individual functions of the app can be performed by analyzing the installation file of the installed app, and constructs a scenario based on identification results. Thereafter, the app management unit 110 installs the app, for which the scenario has been constructed, in the smart phone 30 . [0043] The malicious behavior detection unit 120 analyzes the behavioral log received from the smart phone 30 , and determines whether behavior is malicious based on analysis results. [0044] The storage unit 130 stores the analysis results obtained by the malicious behavior detection unit 120 . When receiving a request for the verification of an app which is the same as an app installed in the smart phone 30 , the storage unit 130 transfers the stored results, thereby reducing the load of the app auto-verification device 100 . [0045] Next, the smart phone 30 according to the first embodiment of the present invention will be described in detail with reference to FIG. 3 . [0046] FIG. 3 is a diagram showing the configuration of the smart phone 30 according to the first embodiment of the present invention. [0047] Referring to FIG. 3 , the smart phone 30 according to the first embodiment of the present invention includes a log recording unit 310 which records behavior, corresponding to an app being executed, as a log. [0048] The log recording unit 310 records behavior, which is performed by the app while the app is being installed and executed in response to remote commands received from the app management unit 110 of the app auto-verification device 100 , as a log. Once the execution is completed, the log recording unit 310 transmits the recorded log, that is, behavioral log, to the malicious behavior detection unit 120 of the app auto-verification device 100 . [0049] Next, a method in which the app auto-verification device 100 automatically verifies an app for the smart phone 30 will be described in detail with reference to FIG. 4 . [0050] FIG. 4 is a flowchart illustrating the method for automatically verifying an app for a smart phone according to the first embodiment of the present invention. [0051] Referring to FIG. 4 , the app auto-verification device 100 selects an app for the smart phone 30 for verification at step S 410 . [0052] The app auto-verification device 100 determines whether verification results related to the selected app have been stored in the storage unit 130 at step S 420 . If the verification results related to the selected app have been stored in the storage unit 130 , the app auto-verification device 100 returns the stored verification results. [0053] If the verification results related to the selected app have not been stored in the storage unit 130 , the app auto-verification device 100 downloads the selected app and analyzes the installation file of the downloaded app at step S 430 . [0054] The app auto-verification device 100 constructs a scenario based on the results of the analysis of the installation file of the app at step S 440 . In greater detail, the app auto-verification device 100 identifies specific conditions under which the individual functions of the app can be executed by analyzing the installation file of the app, and constructs a scenario based on identification results. [0055] The app auto-verification device 100 installs an app corresponding to the constructed scenario in the smart phone 30 and transmits execution commands to the smart phone 30 in accordance with the constructed scenario at step S 450 . In this case, the smart phone 30 executes the app using a dynamic behavior analysis process, and records various types of behavior corresponding to execution results as a log (a behavioral log). [0056] The app auto-verification device 100 receives the behavioral log from the smart phone 30 at step 5460 . [0057] The app auto-verification device 100 analyzes the received behavioral log and determines whether the behavior is malicious based on analysis results at step S 470 . [0058] The app auto-verification device 100 stores the results of the determination of whether the behavior is malicious at step S 480 . Here, when receiving a request for the verification of an app which is the same as the app installed in the smart phone 30 , the app auto-verification device 100 transfers the stored results, thereby reducing the load of the app auto-verification device 100 . [0059] Next, a smart phone 30 according to a second embodiment of the present invention will be described in detail with reference to FIG. 5 . [0060] FIG. 5 is a diagram showing the configuration of the smart phone 30 according to the second embodiment of the present invention. [0061] Referring to FIG. 5 , the smart phone 30 according to the second embodiment of the present invention transfers the installation file and additional information of an app, receives corresponding results, and installs or deletes the app. For this purpose, the smart phone 30 includes an app management unit 320 and a verification client 330 . [0062] The app management unit 320 downloads the app from the app market 20 , and determines whether to install or delete the downloaded app based on verification results. [0063] The verification client 330 requests the verification of the app from the app self-verification device 200 , receives app verification results corresponding to the verification request from the app self-verification device 200 . and transfers the app verification results to the app management unit 320 . [0064] Next, the app self-verification device 200 according to the second embodiment of the present invention will be described in detail with reference to FIG. 6 . [0065] FIG. 6 is a diagram showing the configuration of the app self-verification device 200 according to the second embodiment of the present invention. [0066] Referring to FIG. 6 , the app self-verification device 200 includes a log recording unit 210 , a log determination unit 220 , an installation file determination unit 230 , and a storage unit 240 . [0067] The log recording unit 210 determines whether verification results corresponding to an installation file and the additional information of the installation file, received from the smart phone 30 , exist in the storage unit 240 . [0068] In greater detail, if the verification results exist in the storage unit 240 , the log recording unit 210 returns the verification results, stored in the storage unit 240 , to the smart phone 30 . In contrast, if the verification results do not exist in the storage unit 240 , the log recording unit 210 downloads the corresponding app from the app market 20 , installs and executes it, and records a behavioral log related to access to important resources. [0069] In order to determine whether the verification results exist in the storage unit 240 , the log recording unit 210 may utilize additional information, such as a download URK file hash value, as well as the name of the corresponding file. [0070] The log determination unit 220 determines whether the behavior of the app is malicious by analyzing the recorded behavioral log. Furthermore, the log determination unit 220 stores the results of the determination of whether the behavior of the app is malicious in the storage unit 240 . [0071] The installation file determination unit 230 examines whether the pattern of malicious behavior has been included by applying a binary file static analysis method to the installation file received from the smart phone 30 . Furthermore, the installation file determination unit 230 stores the results of the examination of whether the pattern of malicious behavior has been included in the storage unit 240 . [0072] The storage unit 240 stores the installation file, received from the smart phone 30 , along with a unique value corresponding to the app, such as a hash value. Accordingly, the log recording unit 210 may search the storage unit 240 and return the results without repeatedly performing a verification process when a request for the verification of the same app will be made in the future. [0073] Next, a method in which the app self-verification device 200 performs self-verification on an app for the smart phone 30 will be described in detail with reference to FIG. 7 . [0074] FIG. 7 is a flowchart illustrating the method of performing self-verification on an app for the smart phone 30 according to the second embodiment of the present invention. [0075] Referring to FIG. 7 , the app self-verification device 200 determines whether a request for the verification of a corresponding app has been received from the smart phone 30 at step S 701 . If the request for the verification has not been received, the app self-verification device 200 waits until a request for the verification of an app has been received from the smart phone 30 . [0076] If the request for the verification has been received, the app self-verification device 200 determines whether verification results corresponding to an installation file included in the request for the verification and the additional information of the installation file exist in the storage unit 240 at step S 702 . In this case, the app self-verification device 200 may search for the verification results using the name of the installation file, a URL, a hash value or the like, but is not limited thereto. [0077] If the verification results exist in the storage unit 240 , the app self-verification device 200 returns the verification results, stored in the storage unit 240 , to the smart phone 30 at step S 703 . [0078] If the verification results do not exist in the storage unit 240 , the app self-verification device 200 stores an installation file and the additional information of the installation file, included in the request for the verification, in the storage unit 240 at step S 704 . Furthermore, the app self-verification device 200 notifies the smart phone 30 of the nonexistence of the verification results in the storage unit 240 . Thereafter, the app self-verification device 200 downloads the corresponding app from the app market 20 , installs and executes it, and then records a behavioral log related to access to important resources at S 705 . [0079] The app self-verification device 200 determines whether the behavior of the app is malicious by analyzing the recorded behavioral log at step S 706 . Furthermore, the app self-verification device 200 stores the results of the determination of whether the behavior of the app is malicious in the storage unit 240 at step 5707 . [0080] The app self-verification device 200 examines whether the pattern of malicious behavior has been included, in the installation file received from the smart phone 30 at step S 708 . Furthermore, the app self-verification device 200 stores the results of the examination of whether the pattern of malicious behavior has been included in the installation file in the storage unit 240 at step S 709 . [0081] The app self-verification device 200 finally transfers the results of the determination of whether the behavior of the app is malicious and the results of the examination of whether the pattern of malicious behavior has been included in the installation file installation file to the smart phone 30 at step S 710 . [0082] As described above, the present invention is capable of examining whether apps for a smart phone are malicious in order to prevent malicious apps for a smart phone from spreading. [0083] The present invention has the advantage of preventing malicious apps from spreading via an app market using an app verification process. Furthermore, the present invention has the advantage of preemptively verifying apps before registering them in the app market, thereby preemptively blocking apps in the case where the apps include malware. In particular, the present invention has the advantage of verifying malicious behavior which can be performed only under specific conditions, using a scenario-based malicious behavior triggering process. [0084] Furthermore, the present invention has the advantage of the app auto-verification device enabling a mobile communication provider to protect its app market using an automated analysis process. [0085] The present invention has the advantage of the app self-verification device performing self-verification on downloaded apps, so that the infection of a smart phone with malware can be preemptively blocked, thereby protecting the smart phone from damages such as Distributed Denial of Service (DDoS) or the leakage of personal information. [0086] Although the preferred embodiments of the present invention have been disclosed for illustrative purposes. those skilled in the art will appreciate that various modifications, additions and substitutions are possible, without departing from the scope and spirit of the invention as disclosed in the accompanying claims.

Description

Topics

Download Full PDF Version (Non-Commercial Use)

Patent Citations (11)

    Publication numberPublication dateAssigneeTitle
    US-2002131404-A1September 19, 20024Thpass Inc.Method and system for maintaining and distributing wireless applications
    US-2003099358-A1May 29, 2003Lachlan Michael, Miodrag MihaljevicWireless data communication method and apparatus for software download system
    US-2003114144-A1June 19, 2003Atsushi MinemuraApplication authentication system
    US-2003159070-A1August 21, 2003Yaron Mayer, Zak DechovichSystem and method for comprehensive general generic protection for computers against malicious programs that may steal information and/or cause damages
    US-2006179153-A1August 10, 2006Nam-Yul Lee, Kee-Joo YoonStreaming based contents distribution network system and methods for splitting, merging and retrieving files
    US-2008244074-A1October 02, 2008Paul Baccas, Fraser Howard, Vanja SvajcerRemedial action against malicious code at a client facility
    US-2008282229-A1November 13, 2008Samsung Electronics Co., Ltd.Apparatus and method of detecting errors in embedded software
    US-2009215489-A1August 27, 2009France Telecom, Koninklijke Phillips Electronics N.V.Method and Device for Managing Applications of a Mobile Terminal
    US-2012233695-A1September 13, 2012Lookout, Inc., A California CorporationSystem and method for server-coupled application re-analysis to obtain trust, distribution and ratings assessment
    US-8000680-B2August 16, 2011Samsung Electronics Co., Ltd, Information And Communications University Research And Industrial Cooperation GroupSecurity management method and apparatus in multimedia middleware, and storage medium therefor
    US-8332823-B2December 11, 2012Ntt Docomo, Inc.Application program verification system, application program verification method and computer program

NO-Patent Citations (0)

    Title

Cited By (35)

    Publication numberPublication dateAssigneeTitle
    CN-104268475-AJanuary 07, 2015北京奇虎科技有限公司, 奇智软件(北京)有限公司一种运行应用程序的系统
    CN-104268476-AJanuary 07, 2015北京奇虎科技有限公司, 奇智软件(北京)有限公司Application running method
    EP-2819055-A1December 31, 2014Kaspersky Lab, ZAOSystème et procédé de détection de logiciel malveillant au moyen de scénarios de déclenchement d'un logiciel malveillant
    US-2012331457-A1December 27, 2012Samsung Electronics Co., Ltd.Method for installing application in portable terminal
    US-2014250434-A1September 04, 2014Samsung Electronics Co., Ltd.Method for installing application in portable terminal
    US-2015074816-A1March 12, 2015Samsung Electronics Co., Ltd.Method for url analysis and electronic device thereof
    US-2015082441-A1March 19, 2015Qualcomm IncorporatedExploiting Hot Application Programming Interfaces (APIs) and Action Patterns for Efficient Storage of API logs on Mobile Devices for Behavioral Analysis
    US-2016014123-A1January 14, 2016Electronics And Telecommunications Research InstituteApparatus and method for verifying integrity of applications
    US-8732691-B2May 20, 2014Samsung Electronics Co., Ltd.Method for installing application in portable terminal
    US-8996520-B2March 31, 2015Google Inc.Ranking of native application content
    US-9002821-B2April 07, 2015Google Inc.Indexing application pages of native applications
    US-9135346-B2September 15, 2015Google Inc.Index data for native applications
    US-9146972-B2September 29, 2015Google Inc.Ranking of presentation modes for particular content
    US-9251224-B2February 02, 2016Google Inc.Triggering and ranking of native applications
    US-9262459-B2February 16, 2016Google Inc.Indexing application pages of native applications
    US-9274779-B2March 01, 2016Samsung Electronics Co., Ltd.Method for installing application in portable terminal
    US-9298844-B2March 29, 2016Parlant Technology, Inc.System and method for optimizing mobile device communications
    US-9311407-B2April 12, 2016Google Inc.Native application search results
    US-9348671-B1May 24, 2016Google Inc.Monitoring application loading
    US-9436531-B1September 06, 2016Google Inc.Monitoring application loading
    US-9448859-B2September 20, 2016Qualcomm IncorporatedExploiting hot application programming interfaces (APIs) and action patterns for efficient storage of API logs on mobile devices for behavioral analysis
    US-9513961-B1December 06, 2016Google Inc.Monitoring application loading
    US-9514195-B2December 06, 2016Google Inc.Triggering and ranking of native applications
    US-9524347-B1December 20, 2016Google Inc.Automatically implementing an application in response to a search query
    US-9547721-B2January 17, 2017Google Inc.Native application search results
    US-9608870-B1March 28, 2017Google Inc.Deep link verification for native applications
    US-9645980-B1May 09, 2017Google Inc.Verification of native applications for indexing
    US-9652508-B1May 16, 2017Google Inc.Device specific adjustment based on resource utilities
    US-9652550-B2May 16, 2017Google Inc.Indexing application pages of native applications
    US-9767159-B2September 19, 2017Google Inc.Ranking search results
    US-9792432-B2October 17, 2017Nokia Technologies OyMethod and apparatus for privacy-oriented code optimization
    US-9794106-B1October 17, 2017Google Inc.Detecting application store ranking spam
    US-9811665-B1November 07, 2017Palo Alto Networks, Inc.Static and dynamic security analysis of apps for mobile devices
    US-9846745-B2December 19, 2017Google Inc.Index data for native applications
    US-9881095-B2January 30, 2018Google LlcSearch results for native applications