WO2017080255A1

WO2017080255A1 - Control method and device

Info

Publication number: WO2017080255A1
Application number: PCT/CN2016/091625
Authority: WO
Inventors: 杨鹏; 郭泉
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-11-10
Filing date: 2016-07-25
Publication date: 2017-05-18
Also published as: CN106686624A

Abstract

A control method applied in a terminal device, comprising: detecting a network switching request; and when the network switching request is detected, determining whether to permit network switching of a terminal device according to an application initiating the network switching request. By monitoring network switching, the solution prevents malicious network switching effectively and private user data leakage, thus preventing economic loss of the user.

Description

Control method and device

Technical field

The present application relates to, but is not limited to, the field of communications, and in particular, to a control method and apparatus.

Background technique

With the development of information technology, smart phones have become more and more popular and become a necessity in life. With the popularity of mobile phones, users often use mobile phones to access the Internet, and mobile network traffic is a relatively expensive resource. In the case of a WIFI (Wireless-Fidelity) network, users generally use the WIFI network to access the Internet. . However, there is currently a kind of malware that automatically switches to the mobile network to force users to use the mobile network. That is, when the user uses the WIFI network, the malware will forcibly open the mobile network switch and turn off the WIFI network switch. This will consume the user's mobile network traffic extremely, causing the user's economic loss. In addition, there is a situation in which the user is forced to switch to the WIFI network, that is, the malware will forcibly close the mobile network switch, open the WIFI network switch, and initiate a WIFI connection. This situation is even more dangerous. When the user's WIFI router is poisoned, or the user is forced to connect to the hacker's malicious phishing router, the user's account, password, contact, and other sensitive information will be lost, causing economic losses to the user.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

Embodiments of the present invention provide a control method and apparatus, which effectively monitor network switching.

The embodiment of the invention provides a control method, which is applied to a terminal device, and the control method includes:

Check if there is a network switch request;

When detecting the network handover request, determining, according to an application that initiates the network handover request, whether to allow network handover of the terminal device.

Optionally, determining, according to the application that initiates the network switching request, whether to allow network switching of the terminal device includes:

When the application for initiating the network switching request is found in the boot white list generated by the terminal device or the preset trusted third party application white list, the network switching of the terminal device is allowed.

When the application that initiates the network switching request is not found in the boot whitelist generated by the terminal device and the preset trusted third-party application whitelist, the user-defined network permission whitelist is searched for the The application, if the application is found in the user-defined network permission white list, allows network switching of the terminal device.

When the application that initiates the network switching request is not found in the boot whitelist generated by the terminal device and the preset trusted third-party application whitelist, the user-defined network permission whitelist is searched for the The application, if the application is not found in the user-defined network permission white list, prompts the application to request network switching, and allows the network switching of the terminal device after receiving the network switching confirmation response.

Optionally, after the network switching of the terminal device is allowed after receiving the network switch confirmation response, the method further includes:

Adding the application that initiates the network switch request to the user-defined network permission white list.

Optionally, the method further includes:

Monitor whether the application in the user-defined network permission whitelist accesses private data;

When any application is detected to access private data, a risk alert is made.

Optionally, the method further includes: when determining that the terminal device is powered on for the first time, generating a boot whitelist according to the pre-installed application.

The embodiment of the invention further provides a control device, which is located in the terminal device, and the control device includes:

a detection module configured to detect whether there is a network switching request;

a determining module, configured to initiate the network cut according to when the network switching request is detected The requesting application determines whether to allow network switching of the terminal device.

Optionally, the determining module includes a first switching submodule, and the first switching submodule is configured to: when found in a boot whitelist generated by the terminal device or a preset trusted third party application whitelist When the application of the network handover request is initiated, network switching of the terminal device is allowed.

Optionally, the determining module includes a second switching submodule, and the second switching submodule is configured to: when the booting whitelist generated by the terminal device and the preset trusted third party application whitelist are searched When the application that initiates the network switching request is not found, the application is searched for in the user-defined network permission white list, and if the application is found in the user-defined network permission white list, the Network switching of the terminal device.

Optionally, the determining module includes a third switching submodule, where the third switching submodule is configured to: when the booting whitelist generated by the terminal device and the preset trusted third party application whitelist are searched If the application that initiates the network switching request is not found, the application is searched for in the user-defined network permission whitelist. If the application is not found in the user-defined network permission whitelist, the application is prompted. Requesting network handover, allowing network switching of the terminal device after receiving a network handover confirmation response.

Optionally, the third switching submodule is further configured to add the application that initiates the network switching request to the user-defined network permission whitelist.

Optionally, the device further includes: a control module, configured to monitor whether the application in the user-defined network permission whitelist accesses the private data; and when any application is monitored to access the private data, the risk prompt is performed.

Optionally, the device further includes: a processing module, configured to generate a boot whitelist according to the pre-installed application when determining that the terminal device is powered on for the first time.

The embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, which are implemented when the computer executable instructions are executed.

By monitoring the network switching, the above solution effectively avoids malicious switching of the network and avoids leakage of user privacy data, thereby avoiding economic loss of the user.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

1 is a flow chart of a control method in the first embodiment;

2 is a flow chart of a control method in Embodiment 2;

3 is a schematic structural view of a control device in the third embodiment.

Embodiments of the invention

Embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

The network handover involved in the embodiment of the present invention may be switching from a WIFI network to a mobile network, or may be switching from a mobile network to a WIFI network. The terminal device performs monitoring management on the network handover. After detecting the network handover request initiated by the application, it determines whether the network handover is allowed according to the credibility level of the application.

In the embodiment of the present invention, the entire system is scanned when the system of the terminal device is used for the first time, and the package name (such as ID) of the application that can perform network switching is obtained, and the applications may be pre-installed by the terminal device manufacturer, and then the applications are The package name is stored as a boot whitelist. Since the manufacturer is usually unable to switch maliciously to the network, it can be considered that the application in the boot whitelist is the most secure and reasonable software, and the boot whitelist is set to the highest level of credibility, such as the first level of credibility, if the boot white The application in the list requests network switching to allow the network to switch.

In the embodiment of the present invention, the preset third-party software list is used as the secondary trustworthy network switching application white list, and the network switching may be allowed if the application in the third-party software list requests network switching. The user-defined network permission application whitelist is used as the three-level credibility. In the embodiment of the present invention, the credibility of the whitelist is considered to be the lowest. If the application of the level requests network switching, the user may be prompted to confirm first. If the user confirms that the application is allowed to perform network switching, the terminal device performs network switching. Moreover, for this type of application, the terminal device will perform tracking monitoring. Even if the user allows the application of the level to switch the network, the terminal device further tracks whether the application in the white list performs sensitive data operations, such as uploading a contact. The call record, the automatic sending of the short message, the uploading of the account information, etc., if the operation of the above sensitive data is performed, the application is considered to be insecure, and the user is prompted to the application as a high-risk application and is prohibited from accessing the network.

It should be noted that in other embodiments, the credibility level may also be set according to other rules.

Embodiment 1

The technical solutions of the embodiments of the present invention are further described below with reference to the accompanying drawings.

As shown in FIG. 1 , this embodiment provides a control method, which is applied to a terminal device, where the control method includes the following steps:

Step S11: detecting whether there is a network switching request;

Step S12: When detecting the network handover request, determine, according to an application that initiates the network handover request, whether to allow network handover of the terminal device.

In this embodiment, when the application that initiates the network handover request is found in the boot whitelist generated by the terminal device or the preset trusted third-party application whitelist, the network switching of the terminal device is allowed.

In this embodiment, when the application that initiates the network switching request is not found in the boot whitelist generated by the terminal device and the preset trusted third-party application whitelist, the user-defined network permission is obtained. The application is searched in the whitelist, and if the application is found in the user-defined network permission whitelist, the network switching of the terminal device is allowed.

In this embodiment, when the application that initiates the network switching request is not found in the boot whitelist generated by the terminal device and the preset trusted third-party application whitelist, the user-defined network permission is obtained. Searching for the application in the whitelist, if the application is not found in the user-defined network permission whitelist, prompting the application to request network handover, and allowing the network of the terminal device after receiving the network handover confirmation response Switch.

Optionally, after the network switching of the terminal device is allowed after receiving the network switch confirmation response, the control method further includes:

Optionally, the method further includes:

When any application is detected to access private data, a risk alert is made.

Optionally, the method further includes:

When it is determined that the terminal device is powered on for the first time, a boot whitelist is generated according to the pre-installed application.

The above technical solution can prevent malware from performing network switching by hierarchically managing the network switching authority on the terminal device, thereby avoiding the loss of the user unconsciously, and also providing the best to the greatest extent. User experience, reducing user engagement.

Embodiment 2

As shown in FIG. 2, the technical solution of this embodiment is further described below in conjunction with a specific scenario. The method provided in this embodiment includes the following steps:

Step S201: determining whether the terminal device is powered on for the first time; if it is the first time, then proceeding to step S202 to improve the efficiency of processing; if not the first time, then proceeding to step S203;

Step S202: Scan the entire system to generate a boot white list;

The scanning device obtains the signature of the application applying for the network switching permission, which is equivalent to the ID, and is used to uniquely identify an application. Here, the package name is used to identify an APK (Android Package, Android installation package), or the package name may be used instead. Identify the uniqueness of an APK, such as using a binary signature or using an APK signature to identify the uniqueness of an APK. After obtaining the applied signature, the signature (or ID) of the application is added to the boot whitelist.

Step S203: Whether there is a network switching request in the monitoring system;

The network switching request here refers to turning off the WIFI network switch, or turning off the mobile network switch, and performing network switching. Whether it is switching from a mobile network to a WIFI network or from a WIFI network to a mobile network, it is monitored. If a network switching request is detected, go to step S204.

Step S204: Determine whether the application exists in the boot whitelist by using the ID of the application. If the application exists in the boot whitelist, go to step S213. If the application does not exist in the boot whitelist, go to step S205. .

Step S205: determining, by the ID of the application, whether the application is in a third-party trusted application white list;

For example, some well-known third-party software that is downloaded by some users and not preset by the system may be needed. For network switching, these softwares need to be excluded from malware to form a whitelist of third-party trusted applications. If the application exists in the third-party trusted application white list, go to step S213; if the application does not exist in the third-party trusted application white list, go to step S206.

Step S206: Determine, by the ID of the application, whether the application is in the white list of the network switching allowed by the user, if yes, go to step S213; if no, go to step S207.

Step S207: The user confirms whether network switching is allowed;

The terminal device prompts the user to have an application request for network switching, and displays information about the related application, such as a name, a developer, and the like. If the user chooses to allow network switching, go to step S208; if the user rejects the network switching, go to step S214.

If the user does not make a selection temporarily, wait for the user to make a selection, and then perform the corresponding operation. In the process of displaying the network switching prompt, the listening mechanism always exists, and if there are other applications performing the network switching request, the execution continues from step S203.

Step S208: Perform network switching.

Step S209: It is determined whether the user selects to add the application to the custom whitelist, and if yes, go to step S210, otherwise go to step S214.

Step S210: Add the application to a user-defined white list;

The ID of the application can be added to the user-defined white list. Since the credibility of the application is not as high as the first two whitelists, the behavior of the application needs to be further monitored. That is, the operation of step S211 is performed.

Step S211: Monitor whether the application in the user-defined whitelist accesses user privacy data, such as contact, account information, short message, etc., if yes, go to step S212.

Step S212: Remind the user that the application is risky, and then proceeds to step S214.

The application can also be deleted from the user-defined trusted white list while reminding the user.

Step S213: Allow network switching.

Step S214: End this operation.

Embodiment 3

As shown in FIG. 3, the embodiment provides a control device, which is located in a terminal device, and the control device includes:

The detecting module 11 is configured to detect whether there is a network switching request;

The determining module 12 is configured to determine, according to the application that initiates the network switching request, whether to allow network switching of the terminal device when the network switching request is detected.

Optionally, the determining module 12 includes a first switching submodule 121. The first switching submodule 121 is configured to: when the booting whitelist generated by the terminal device or a preset trusted third party application whitelist When the application that initiates the network switching request is found, the network switching of the terminal device is allowed.

Optionally, the determining module 12 includes a second switching submodule 122. The second switching submodule 122 is configured to: when the booting whitelist generated by the terminal device and the preset trusted third party application whitelist If the application that initiates the network switching request is not found, the application is searched for in the user-defined network permission white list. If the application is found in the user-defined network permission white list, Allow network switching of the terminal device.

Optionally, the determining module 12 includes a third switching submodule 123. The third switching submodule 123 is configured to: when the booting whitelist generated by the terminal device and the preset trusted third party application whitelist If the application that initiates the network switching request is not found, the application is searched for in the user-defined network permission whitelist. If the application is not found in the user-defined network permission whitelist, Then, the application is prompted to request network switching, and the network switching of the terminal device is allowed after receiving the network switching confirmation response.

Optionally, the third switching submodule 123 is further configured to add the application that initiates the network switching request to the user-defined network permission white list.

Optionally, the device further includes: a control module 13 configured to monitor whether the application in the user-defined network permission whitelist accesses the private data; and when any application is monitored to access the private data, the risk prompt is performed.

Optionally, the device further includes: a processing module 14 configured to generate a boot whitelist according to the pre-installed application when determining that the terminal device is powered on for the first time.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be performed by a program to instruct related hardware, such as a processor, which may be stored in a computer readable storage medium, such as a read only memory, disk or optical disk. Wait. Optionally, all or part of the steps of the foregoing embodiments may also be implemented by using one or more integrated circuits. Accordingly, each module/module in the foregoing embodiment may be implemented in the form of hardware, for example, by using an integrated circuit. The corresponding function can also be implemented in the form of a software function module, for example, by executing a program/instruction stored in the memory by the processor to implement its corresponding function. This application is not limited to any specific combination of hardware and software.

The above description is only an optional embodiment of the present application, and is not intended to limit the present application, and various changes and modifications may be made to the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this application are intended to be included within the scope of the present application.

Industrial applicability

The embodiment of the present application provides a control method and device, which effectively avoids malicious switching of the network, avoids leakage of user privacy data, and thus avoids economic loss of the user.

Claims

A control method is applied to a terminal device, and the method includes:

Check if there is a network switch request;

When detecting the network handover request, determining, according to an application that initiates the network handover request, whether to allow network handover of the terminal device.
The method of claim 1, wherein the determining, according to an application that initiates the network switching request, whether to allow network switching of the terminal device comprises:

When the application for initiating the network switching request is found in the boot white list generated by the terminal device or the preset trusted third party application white list, the network switching of the terminal device is allowed.
The method of claim 1, wherein the determining, according to an application that initiates the network switching request, whether to allow network switching of the terminal device comprises:

When the application that initiates the network switching request is not found in the boot whitelist generated by the terminal device and the preset trusted third-party application whitelist, the user-defined network permission whitelist is searched for the The application, if the application is found in the user-defined network permission white list, allows network switching of the terminal device.
The method of claim 1, wherein the determining, according to an application that initiates the network switching request, whether to allow network switching of the terminal device comprises: a boot whitelist generated at the terminal device and a preset If the application that initiates the network switching request is not found in the trusted third-party application whitelist, the application is searched for in the user-defined network permission whitelist, if the user is customized in the user-defined network permission whitelist. If the application is not available, the application is prompted to request network handover, and the network handover of the terminal device is allowed after receiving the network handover confirmation response.
The method of claim 4, after the network switching of the terminal device is allowed after receiving the network switching confirmation response, the method further comprises: adding the application that initiates the network switching request to the user Defined in the whitelist of network permissions.
The method of claim 1, further comprising: monitoring whether the application in the user-defined network permission whitelist accesses the private data; and when detecting that any application accesses the private data, performing a risk prompt.
The method of claim 1, further comprising: generating a boot whitelist based on the pre-installed application when determining that the terminal device is powered on for the first time.
A control device is located at a terminal device, and the control device includes:

a detection module configured to detect whether there is a network switching request;

The determining module is configured to determine, according to the application that initiates the network switching request, whether to allow network switching of the terminal device, when the network switching request is detected.
The apparatus of claim 8, wherein the determining module comprises a first switching submodule; the first switching submodule is configured to: when a boot whitelist or a preset trusted first generated by the terminal device The network switching of the terminal device is allowed when the application for initiating the network switching request is found in the three-party application whitelist.
The apparatus of claim 8, wherein the determining module comprises a second switching submodule; the second switching submodule is configured to: when the booting whitelist generated by the terminal device and the preset trusted first If the application that initiates the network switching request is not found in the whitelist application whitelist, the application is searched for in the user-defined network permission whitelist, and if the user is found in the user-defined network permission whitelist. The application allows network switching of the terminal device.
The apparatus of claim 8, wherein the determining module comprises a third switching submodule; the third switching submodule is configured to: when the booting whitelist generated by the terminal device and the preset trusted first If the application that initiates the network switching request is not found in the whitelist of the three-party application, the application is searched for in the user-defined network permission whitelist, and is not found in the user-defined network permission whitelist. The application prompts the application to request network handover, and allows network switching of the terminal device after receiving the network handover confirmation response.
The apparatus of claim 11, wherein the third handover sub-module is further configured to add the application that initiates the network handover request to the user-defined network rights whitelist.
The device of claim 8, further comprising: a control module configured to: monitor whether the application in the user-defined network permission whitelist accesses the private data; when monitoring any application accessing the private data, proceeding risk warning.
The device of claim 8, further comprising: a processing module configured to generate a boot whitelist according to the pre-installed application when determining that the terminal device is powered on for the first time.