# US 2015/0150128 A1 · Method and apparatus for intercepting or cleaning-up plugins

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2015/0150128 A1
- Document ID: US20150150128A1
- Status: Published application
- Kind: A1
- Application number: 14/607,044
- Filed: 2015-01-27
- Published: 2015-05-28
- Earliest claimed: 2012-07-27
- Assignees: Tencent Technology (Shenzhen) Company Limited
- Applicants: Tencent Technology (Shenzhen) Company Limited
- Inventors: Weijie LI
- Web page: https://patentgrep.com/patent/US20150150128A1

## CPC

- H04L 63/14: {for detecting or protecting against malicious traffic}
- G06F 9/44526: {Plug-ins; Add-ons}
- G06F 11/3409: {for performance assessment}
- G06F 2201/865: Monitoring of software
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The present invention discloses a method and apparatus for intercepting or cleaning-up plugins. The methods may include: obtaining performance attributes of a plugin; determining if the plugin meets a performance criterion based on the obtained performance attributes and empirical data; and intercepting or cleaning-up the plugin if the plugin does not meet the performance criterion. In accordance with embodiments of the present invention, the performance attributes of a plugin can be evaluated to determine whether the plugin meets a preset performance criterion, and the plugin can then be processed according to the result of the determination.

## Claims

### Claim 1

A method for intercepting or cleaning-up a plugin, the method comprising:
obtaining performance attributes of a plugin;
determining whether the plugin meets a performance criterion based on the performance attributes and empirical data; and
intercepting or cleaning-up the plugin if the plugin does not meet the performance criterion.

### Claim 2 (depends on 1)

The method of claim 1, further comprising
monitoring activity of the plugin in a user terminal, wherein the activity is selected from a group comprising installing, loading, and running of the plugin;
identifying the plugin based on the monitored activity; and
obtaining performance attributes of the plugin when the plugin is identified.

### Claim 3 (depends on 2)

The method of claim 2, further comprising, after identifying the plugin based on the monitored activity,
evaluating performance attributes of the plugin when the plugin is not identified;
determining whether the plugin meets a performance criterion based on the performance attributes and empirical data; and
intercepting or cleaning-up the plugin if the plugin does not meet the performance criterion.

### Claim 4 (depends on 1)

The method of claim 1, further comprising, prior to obtaining performance attributes of the plugin,
obtaining empirical data of the plugin, wherein the empirical data comprises plugin importance data, plugin performance data, and/or end user review data; and
determining whether the plugin meets the performance criterion based on the empirical data.

### Claim 5 (depends on 1)

The method of claim 1, wherein the empirical data is obtained through plugin testing, backend collection, and/or web crawling, backend collection comprises frontend collection and end user review, frontend collection comprises hook mode and notification mode,
plug testing comprises testing the plugin in an automatic module to obtain information on the plugin's CPU usage, load time and/or memory usage;
hook mode comprises using a hook to obtain a start time and an end time for loading the plugin, a start time and an end time for running the plugin, and information on the plug's CPU usage and/or memory usage while the plugin is loading and running;
reception mode comprises a client directly notifying starting and ending of loading and running of the plugin;
end user review comprises collecting reviews of end users on the performance of the plugin;
web crawling comprises crawling search engine data and/or website review data to evaluate the performance of the plugin; and
the empirical data is stored in a remote cloud database or a local database.

### Claim 6 (depends on 1)

The method of claim 1, wherein determining if the plugin meets a performance criterion based on the performance attributes and empirical data comprises:
matching the performance attributes with empirical data stored on a cloud database;
obtaining a preset determination result after a successful match, and
determining whether the plugin meets the performance criterion based on the preset determination result.

### Claim 7

An apparatus for intercepting or cleaning-up a plugin, the apparatus comprising:
a performance acquisition module for obtaining performance attributes of a plugin;
a first performance determination module for determining whether the plugin meets a performance criterion based on the performance attributes and empirical data; and
a plugin processing module for intercepting or cleaning-up the plugin if the plugin does not meet the performance criterion.

### Claim 8 (depends on 7)

The apparatus of claim 7, further comprising
a plugin monitoring module for monitoring activity of the plugin in a user terminal, wherein the activity is selected from a group comprising installing, loading, and running of the plugin; identifying the plugin based on the monitored activity; and obtaining performance attributes of the plugin when the plugin is identified.

### Claim 9 (depends on 8)

The apparatus of claim 8, further comprising a performance evaluation module for, after identifying the plugin based on the monitored activity, evaluating performance attributes of the plugin when the plugin is not identified;
wherein the first performance determination module is configured for determining whether the plugin meets the performance criterion based on the performance attributes and empirical data; and
the plugin processing module is configured for intercepting or cleaning-up the plugin if the plugin does not meet the performance criterion.

### Claim 10 (depends on 7)

The apparatus of claim 7, further comprising an empirical data acquisition module for obtaining empirical data of the plugin, wherein the empirical data comprises plugin importance data, plugin performance data, and/or end user review data; and
a second performance determination module for determining whether the plugin meets the performance criterion based on the empirical data.

### Claim 11 (depends on 7)

The apparatus of claim 7, wherein the empirical data is obtained through plugin testing, backend collection, and/or web crawling, wherein backend collection comprises frontend collection and end user review, frontend collection comprises hook mode and notification mode,
plug testing comprises testing the plugin in an automatic module to obtain information on the plugin's CPU usage, load time and/or memory usage;
hook mode comprises using a hook to obtain a start time and an end time for loading the plugin, a start time and an end time for running the plugin, and information on the plug's CPU usage and/or memory usage while the plugin is loading and running;
reception mode comprises a client directly notifying starting and ending of loading and running of the plugin;
end user review comprises collecting reviews of end users on the performance of the plugin;
web crawling comprises crawling search engine data and/or website review data to evaluate the performance of the plugin; and
the empirical data is stored in a remote cloud database or a local database.

### Claim 12 (depends on 7)

The apparatus of claim 7, wherein the first performance determination module is further configured for:
matching the performance attributes with empirical data stored on a cloud database;
obtaining a preset determination result after a successful match, and
determining whether the plugin meets the performance criterion based on the preset determination result.
