WO2017211205A1

WO2017211205A1 - Method and device for updating whitelist

Info

Publication number: WO2017211205A1
Application number: PCT/CN2017/086319
Authority: WO
Inventors: 汪婵; 彭峰
Original assignee: 华为技术有限公司
Priority date: 2016-06-07
Filing date: 2017-05-27
Publication date: 2017-12-14
Also published as: CN107480518A

Abstract

The invention relates to the field of communications. Provided are a method and device for updating a whitelist capable of timely updating a whitelist of a terminal. The method comprises: upon trigging of a whitelist update request, determining, by a terminal, whether a first application has authority to update a whitelist thereof (S101), the whitelist being used to store the number of an authentication code sender of a party generating the whitelist update request; and if it is determined that the first application has the authority to update the whitelist of the terminal, updating the whitelist with at least the number of the authentication code sender of the party generating the whitelist update request (S102).

Description

White list updating method and device

The present application claims priority to Chinese Patent Application No. 201610404438.5, filed on Jun. 7, 2016, the entire content of which is hereby incorporated by reference.

Technical field

The embodiments of the present invention relate to the field of communications, and in particular, to a whitelist updating method and apparatus.

Background technique

Mobile Payment refers to a service that allows users to use their mobile terminals, such as mobile phones or tablets, to pay for goods or services they consume. With the rise of mobile payments, mobile payments typically use secure authentication in the form of SMS verification codes (eg, financial transaction information, specifically, bank account numbers, bank passwords, payment verification codes, order notifications, etc.). That is, when the user performs mobile payment on the website or the application (Application, referred to as APP), the sender code of the verification code corresponding to the website background or the application sends a short message service (SMS) to the mobile phone number bound by the user. The short message carries the short message verification code generated by the website or the application according to the preset rule. After the user receives the short message, the user fills in the short message verification code on the website or the application, and the subsequent operation can be completed after the verification is passed.

At present, in the Android (Android) operating system, the APP can read the short message permission by applying, and after determining that the right to read the short message, the APP can read all the short messages in the mobile terminal system, and obtain the required short message verification code from the mobile terminal system, if Currently, the mobile terminal uses the mobile phone number that needs to be verified, so that the user can manually prevent the verification code from being manually input. Currently, except for the short message application, most of the main functions of the APP application for the short message permission are to read the short message verification code. The sender code of the verification code corresponding to the application can be written into the whitelist of the terminal, so that if the sender number of the verification code corresponding to the application does not exist in the whitelist, the terminal system can remind the terminal user to send the verification. The sender code of the code verification code has a security risk, which can prevent users from being scammed by false text messages. In actual use, there may be a problem that the application adds a new service or changes the sender number of the verification code corresponding to the application. In this case, the whitelist is updated, and the sender number of the verification code corresponding to the application is updated.

In the prior art, the whitelist is usually upgraded by a large version (such as OTA (Over-the-Air Technology) upgrade), that is, when the application has a new service or changes the verification code sender number. When the developer of the application requests the developer of the whitelist to request to update the whitelist, the terminal developer develops the corresponding version upgrade software, and the terminal updates the whitelist through the corresponding version upgrade software update. The update method requires a long period of time. And the application can't modify the whitelist actively, only by applying in advance. At the same time, the whitelist list covers a large number of applications; when each application needs to update the whitelist list for reasons such as business development and change, the whitelist list on each terminal cannot be updated in time.

Summary of the invention

An embodiment of the present invention provides a whitelist updating method and apparatus for updating a verification code sender number corresponding to each application in the terminal whitelist list and/or each service of the application in a timely manner.

In order to achieve the above object, embodiments of the present invention adopt the following technical solutions:

In a first aspect, an embodiment of the present invention provides a whitelist update method, which is applied to a terminal, where the first application is run on the terminal, and the method includes: generating, according to the first application, or the first service generation of the first application. Triggering the whitelist update request, the terminal determining whether the first application has the right to update the terminal whitelist list, wherein the whitelist update request includes the identifier of the first application, and the verification code of the whitelist update request generator a sender number; the verification code sender number is a white list update request generator; the terminal white list is used to store a verification code sender number for transmitting the verification code message; if it is determined that the first application has a whitelist of the updated terminal Permission, at least update the verification code sender number of the whitelist update request generator to the terminal whitelist.

An embodiment of the present invention provides a whitelist update method, by receiving a whitelist update request for updating a terminal whitelist list sent by a first application, and updating the first application after determining that the first application has the right to update the terminal whitelist. The terminal whitelist list, such that when the whitelist update request generator's verification code sender number is changed or the whitelist update request generator's verification code sender number needs to be re-registered in the whitelist list, there is no need to whitelist the list. The developer submits an application request to update the terminal whitelist list, and updates the verification code sender for storing the verification code message according to the trigger of the first application generation or the whitelist update request generated by the first service of the first application. The terminal whitelist list of the number is simple, and solves the problem that the application cannot update the terminal whitelist list and update the terminal whitelist list period in the prior art.

In conjunction with the first aspect, in a first possible implementation manner of the first aspect, the terminal further includes a display screen, and correspondingly, the terminal determines that the first application has the right to update the terminal whitelist list, including: updating based on the whitelist a triggering of the request, the terminal displaying, by using a display screen, a first prompt message for prompting the user whether to grant the first application the right to update the terminal whitelist list; if the terminal detects that the user inputs the first indication information, It is determined that the first application has the right to update the terminal whitelist list. In this way, the user can determine whether the first application is a security application according to the first prompt message. When the user determines that the first application is a security program, the user authorizes the first application to have the right to update the terminal whitelist. In this way, the security of the verification code sender number can be recognized by the user.

With reference to the first aspect, in a second possible implementation manner of the first aspect, determining that the first application has the right to update the terminal whitelist list includes: acquiring, by the terminal, the first application according to the trigger of the whitelist update request a certificate and an identifier; the terminal determines whether the certificate of the first application matches the preset certificate, and whether the identifier of the first application matches the preset identifier; if the terminal determines that the certificate of the first application matches the preset certificate, and the If the identifier of an application matches the preset identifier, it is determined that the first application has the right to update the terminal whitelist list. In this way, the reliability of each verification code sender number stored in the terminal whitelist list can be improved, and the user can identify the verification code sender number with security risks, thereby preventing the user from being fraudulently spoofed.

In combination with the first aspect, in the first possible implementation of the first aspect, at least the whitelist is further The new request generator's verification code sender number is updated to the terminal whitelist list, including: the terminal determines whether the whitelist update request generator's verification code sender number is already registered in the terminal whitelist list; if the terminal determines the whitelist update If the verification code sender number of the request generator is not registered in the terminal whitelist, the terminal writes the identifier of the first application and the verification code sender number of the whitelist update request generator corresponding to the identifier of the first application. Enter the terminal whitelist. In this way, the verification code sender number of the whitelist update request generator can be registered in the terminal whitelist list in time.

In conjunction with the third possible implementation of the first aspect, in a fourth possible implementation manner of the first aspect, the method further includes: if the terminal determines that the verification code sender number of the whitelist update request generator is already registered In the terminal whitelist list, the terminal determines whether the original verification code sender number is consistent with the new verification code sender number; the original verification code sender number is the verification code of the whitelist update request generator that has been registered in the terminal whitelist list. The party number, the new verification code sender number is the verification code sender number of the white list update request generator in the white list update request; if the terminal determines that the original verification code sender number is inconsistent with the new verification code sender number, the terminal The original verification code sender number is deleted from the terminal whitelist list, and the new verification code sender number is written into the terminal whitelist list corresponding to the identifier of the first application. In this way, when the verification code sender number of the whitelist update request generator is changed, the verification code sender number of the whitelist update request generator can be updated in the terminal white list in time.

With reference to the first aspect to any possible implementation of the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the method further includes: acquiring, by the terminal, a whitelist of the terminal The whitelist update request generator uses the frequency of the preset time; the terminal deletes the verification code sender number of the whitelist update request generator whose frequency is less than the preset threshold in the terminal whitelist from the terminal whitelist. In this way, when the storage space of the terminal whitelist is fixed, the storage space of the terminal whitelist is saved.

In a sixth possible implementation manner of the first aspect, the method further includes: sending at least a verification code sender number of the whitelist update request generator for updating a first whitelist update request of the verification code sender number of the whitelist update request generator in the server whitelist list, so that the server is based on the first The whitelist update request periodically synchronizes the updated server whitelist to the terminal that communicates with the server; thus, the server may be caused to update the whitelist update request sender's verification code sender number in the server whitelist list, and then By connecting with the server, the terminal can update the terminal whitelist list in the terminal that communicates with the server, so that the terminal can update the terminal whitelist list without upgrading the version.

Of course, the first whitelist update request further includes an identifier and a certificate of the first application, and the server determines, according to the identifier and the certificate of the first application, whether to update the server whitelist in the server.

In a second aspect, the embodiment of the present invention further provides a whitelist update method, which is applied to a server, where the method includes: receiving, by the server, an identifier of the first application, and a verification code sender number of the whitelist update request generator. First whitelist update to indicate update server whitelist list The whitelist update request is generated by the first application or the first service of the first application; the server determines whether the first whitelist update request satisfies the update condition; and the server determines that the first whitelist update request satisfies the update condition The server updates at least the verification code sender number of the whitelist update request generator to the server whitelist. In this way, the server can update the verification code sender number of the whitelist update request generator in the server whitelist list stored in the server in time.

With reference to the second aspect, in a first possible implementation manner of the second aspect, the method further includes: the server, according to the preset period, synchronizing the updated server whitelist to the terminal that communicates with the server. In this way, the terminal can update the terminal whitelist list in the terminal by communicating with the server.

With reference to the second aspect, in a second possible implementation manner of the second aspect, the first whitelist update request further includes a certificate and an identifier of the first application; if the first whitelist update request is sent by the terminal, The update condition is that the certificate of the first application included in the first whitelist update request is consistent with the certificate corresponding to the first application stored in the server, and the identifier of the first application is pre-stored in the server. The identifier corresponding to the first application is consistent; when the first whitelist update request is not sent by the terminal, the update condition is that the first whitelist update request carries the update information corresponding to the terminal, and the update information includes the updated version difference. And an update time and a result of whether the verification code sender number of the whitelist update request generator has been updated in the terminal whitelist list.

In a third aspect, an embodiment of the present invention provides a whitelist updating apparatus, which is applied to a terminal, where the terminal runs a first application, and the apparatus includes: a determining unit, configured to generate or the first application based on the first application. Triggering a whitelist update request generated by the first service, determining whether the first application has the right to update a terminal whitelist for storing the verification code sender number of the whitelist update request generator, wherein the white The list update request includes an identifier of the first application and a verification code sender number of the whitelist update request generator; a determining unit, configured to determine that the first application has the right to update the whitelist of the terminal; and an update unit, configured to: When the determining unit determines that the first application has the right to update the whitelist list of the terminal, at least the verification code sender number of the whitelist update request generator is updated to the terminal whitelist, and the terminal whitelist is used for storing the transmission verification. The verification code sender number of the code message.

In a third aspect, in a first possible implementation manner of the third aspect, the terminal further includes a display screen, and the corresponding determining unit includes: a display module, configured to display the trigger based on the whitelist update request to the user through the display screen a first prompt message for prompting the user whether to grant the first application the right to update the terminal whitelist list; the first determining module is configured to determine whether the user input is used to indicate that the user agrees to the Determining, by the first application, the first indication information of the right to update the whitelist of the terminal; the first determining module, configured to: when the first determining module determines that the user inputs the first indication information, determining that the first application has the update The permissions of the terminal whitelist.

With reference to the third aspect, in a second possible implementation manner of the third aspect, the determining unit includes: an acquiring module, configured to acquire a certificate and an identifier of the first application based on a trigger of the whitelist update request; a module, configured to determine whether the certificate of the first application matches the preset certificate, and whether the identifier of the first application matches the preset identifier, and the second determining module is configured to determine, in the second determining module, the first application The certificate matches the preset certificate, and the identifier of the first application matches the preset identifier When it is determined, the first application has the right to update the terminal whitelist list.

With reference to the third aspect, in a third possible implementation manner of the third aspect, the updating unit includes: a third determining module, configured to determine whether the verification code sender number of the whitelist update request generator is already registered in the terminal white a first update module, configured to: when the third determination module determines that the verification code sender number of the whitelist update request generator is not registered in the terminal whitelist, the identifier of the first application and the first The verification code sender number of the whitelist update request generator corresponding to the identifier of the application is written in the terminal whitelist.

In conjunction with the third possible implementation of the third aspect, in a fourth possible implementation manner of the third aspect, the device further includes: a fourth determining module, configured to determine, in the third determining module, a whitelist update request When the sender's verification code sender number is registered in the terminal whitelist list, it is determined whether the original verification code sender number is consistent with the new verification code sender number; the original verification code sender number is already registered in the terminal whitelist list. The whitelist update request sender's verification code sender number, the new verification code sender number is the verification code sender number of the whitelist update request generator in the whitelist update request; the second update module is used in the When the determining module determines that the original verification code sender number is inconsistent with the new verification code sender number, the original verification code sender number is deleted from the terminal whitelist list, and the new verification code sender number is written into the terminal whitelist list. The location corresponding to the identity of the first application.

With reference to any one of the possible implementations of the third aspect to the fourth possible implementation of the third aspect, in a fifth possible implementation manner of the third aspect, the device further includes: a statistics unit, configured to obtain The frequency of use of the whitelist update request generator in the terminal whitelist list in the preset time; the deleting unit is configured to use the verification code sender number of the whitelist update request generator whose frequency is less than the preset threshold in the terminal whitelist list And the identifier of the whitelist update request generator is deleted from the terminal whitelist.

With reference to any one of the possible implementation manners of the third aspect to the fifth possible implementation manner of the third aspect, in a sixth possible implementation manner of the third aspect, the device further includes: a sending unit, configured to The server sends a first whitelist update request, so that the server periodically synchronizes the updated server whitelist list to the terminal connected to the server according to the first whitelist update request; the first whitelist update request carries at least The whitelist update request generator's verification code sender number; the first whitelist update request is used to update the verification code sender number of the whitelist update request generator in the server whitelist list, and the server whitelist is used to store the transmission verification code. The verification code sender number of the message.

In a fourth aspect, the embodiment of the present invention provides a whitelist updating apparatus, which is applied to a server, where the apparatus includes: a receiving unit, configured to receive a first whitelist update request, where the first whitelist update request is used to indicate an update server. a whitelist list; the first whitelist update request includes at least an identifier of the first application, a verification code sender number of the whitelist update request generator; wherein the whitelist update request is generated by the first application or the first application The first service is generated; the server whitelist is used to store the verification code sender number of the verification code message; the determining unit is configured to determine whether the first whitelist update request satisfies the update condition; and the update unit is configured to determine, in the determining unit, A whitelist update request satisfies the update condition, and the server at least adds the verification code sender number of the whitelist update request generator Update to the server whitelist list.

In conjunction with the fourth aspect, in a first possible implementation manner of the fourth aspect, the apparatus further includes: a synchronization unit, configured to synchronize the updated server whitelist list to the terminal that communicates with the server according to a preset period.

With reference to the fourth aspect, in a second possible implementation manner of the fourth aspect, the first whitelist update request further includes a certificate and an identifier of the first application, and if the first whitelist update request is sent by the terminal, The update condition is that the certificate of the first application included in the first whitelist update request is consistent with the certificate corresponding to the first application stored in the server, and the identifier of the first application is pre-stored in the server. The identifier corresponding to the first application is consistent; when the first whitelist update request is not sent by the terminal, the update condition is that the first whitelist update request carries the update information corresponding to the terminal, and the update information includes the updated version. The difference, the update time, and the result of whether the verification code sender number of the whitelist update request generator has been updated in the terminal whitelist list.

In a fifth aspect, an embodiment of the present invention provides a terminal, including: a processor, a memory, a system bus, and a communication interface;

The memory is configured to store a computer execution instruction, the processor is connected to the memory through the system bus, and when the terminal is running, the processor executes the computer execution instruction stored in the memory, so that The terminal performs the whitelist update method as described in the above first aspect or any one of the foregoing aspects.

In a sixth aspect, an embodiment of the present invention provides a readable medium, including a computer executing instruction, when the processor of the terminal executes the computer to execute an instruction, the terminal performs any one of the foregoing first aspect or the first aspect. The whitelist update method described in the alternative.

In a seventh aspect, an embodiment of the present invention provides a server, including: a processor, a memory, a system bus, and a communication interface;

The memory is configured to store a computer executing instructions, the processor is coupled to the memory via the system bus, and when the server is running, the processor executes the computer executed instructions stored in the memory to enable The server performs the whitelist update method as described in the second aspect or the second aspect of the second aspect.

In an eighth aspect, an embodiment of the present invention provides a readable medium, including computer execution instructions, when the processor of the server executes the computer execution instruction, the server performs any one of the foregoing second aspect or the second aspect. The whitelist update method described in the alternative.

A ninth aspect, the embodiment of the present invention provides a communication system, where the communication system includes a plurality of terminals and a server, and the multiple terminals may be the terminal described in any one of the foregoing third aspect or the third aspect. And the server may be the server described in the above fourth aspect or any one of the optional aspects of the fourth aspect; or

The plurality of user equipments may be the user equipments described in the fifth aspect above, and the server may be the server described in the seventh aspect above.

Optionally, the user equipment may further include the readable medium of the sixth aspect, and the server may further include the readable medium of the eighth aspect.

An embodiment of the present invention provides a whitelist updating method and apparatus, which are sent by receiving a first application. Sending a whitelist update request for updating the terminal whitelist list, after determining that the first application has the right to update the terminal whitelist list, updating the terminal whitelist list, so that when the whitelist update request generator sends the verification code When the party number is changed or the verification code sender number of the whitelist update request generator needs to be re-registered in the whitelist list, it is not necessary to apply to the developer of the whitelist list to request to update the terminal whitelist list, but according to the first application. Generating or triggering the whitelist update request generated by the first service of the first application to update the terminal whitelist list in time, which is simple, and solves the problem that the application cannot update the terminal whitelist list and update the terminal whitelist list in the prior art. A long cycle problem.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any creative work.

1 is a schematic flowchart 1 of a white list updating method according to an embodiment of the present invention;

2 is a second schematic flowchart of a whitelist updating method according to an embodiment of the present invention;

FIG. 3 is a schematic flowchart 3 of a method for updating a white list according to an embodiment of the present disclosure;

4 is a schematic flowchart 4 of a white list updating method according to an embodiment of the present invention;

FIG. 5 is a schematic flowchart of a whitelist update method according to another embodiment of the present invention;

FIG. 6 is a schematic structural diagram 1 of a white list updating apparatus according to an embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram 2 of a white list updating apparatus according to an embodiment of the present disclosure;

FIG. 8 is a schematic structural diagram of another whitelist updating apparatus according to an embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure;

FIG. 10 is a schematic structural diagram of a server according to an embodiment of the present disclosure;

FIG. 11 is a schematic structural diagram of a hardware of a terminal according to an embodiment of the present invention.

detailed description

The principle of the embodiment of the invention:

In the embodiment of the present invention, when updating the whitelist list in the terminal in the prior art, when the verification code sender number of the application is changed, the application cannot update the whitelist list and update the whitelist in a large version. A method for updating a whitelist list, which is provided by the processor in the embodiment, by receiving a whitelist update request for updating a terminal whitelist list sent by the application, determining that the application has After updating the permission of the whitelist list, the terminal whitelist list is updated, and when the verification code sender number corresponding to any application is changed or the verification code sender number needs to be re-registered in the whitelist list, the user can be timely and autonomous. Updating the whitelist list, the method is simple, when the verification code sender number of the application is changed or needs to be re-registered, the application of the whitelist is not required to request the update of the whitelist list, and the application in the prior art is solved. Unable to update the whitelist list and update the whitelist list week Long.

The terminal in the embodiment of the present invention includes a processor, a display screen connected to the processor by an application running on the processor, and a whitelist management entity. An operating system of the terminal in the embodiment of the present invention Without limitation, the operating system of the terminal may be Android, Windows Phone, or iOS.

In a specific implementation, the terminal in the embodiment of the present invention may be a mobile phone, a mobile computer, a tablet computer, a personal digital assistant (PDA), a media player, a smart TV, a smart wearable device (such as a smart watch, Intelligent glasses, smart bracelets, etc.), electronic readers, handheld game consoles, and in-vehicle electronic devices, etc., the terminal has functions such as running an application (Application, APP), accessing the network, and positioning.

The application of the embodiment of the present invention may be any application installed on the terminal, including but not limited to browser, email, instant messaging service, word processing, keyboard virtual, widget, encryption. , digital rights management, voice recognition, voice replication, positioning (such as those provided by GPS), music playback, and more.

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

As shown in FIG. 1 , an embodiment of the present invention provides a method for updating a whitelist, which is applied to a terminal, where the terminal includes a processor, and a first application running on the processor, where the method includes:

S101. The terminal determines, according to a trigger of the whitelist update request, whether the first application has the right to update the terminal whitelist, wherein the whitelist update request is generated by the first application or the first a first service generation of an application, the whitelist update request including an identifier of the first application, and a verification code sender number of the whitelist update request generator; the terminal whitelist is used for storing Send the verification code sender number of the verification code message;

S102. If it is determined that the first application has the right to update the whitelist of the terminal, update at least the verification code sender number of the whitelist update request generator to the terminal whitelist.

An embodiment of the present invention provides a whitelist update method, by receiving a whitelist update request for updating a terminal whitelist list sent by a first application, and updating the first application after determining that the first application has the right to update the terminal whitelist. The terminal whitelist list, such that when the whitelist update request generator's verification code sender number is changed or the whitelist update request generator's verification code sender number needs to be re-registered in the whitelist list, there is no need to whitelist the list. The developer submits an application request to update the terminal whitelist list, and updates the terminal whitelist list according to the trigger of the whitelist update request generated by the first application or the first service of the first application, and the method is simple and solves the present problem. In the prior art, the application cannot update the terminal whitelist list and update the terminal whitelist list period.

The embodiment of the present invention does not limit the specific form of the whitelist of the terminal, as long as the terminal whitelist can be used to store the verification code sender number of the verification code message.

For example, the terminal whitelist may include a plurality of entries, each entry for storing an identifier of an application and a verification code sender number or application identifier of the application and a service of the application. Correspondence between them.

The embodiment of the present invention does not advance the specific form of the verification code message and the specific content of the verification code message. The line definition, the verification code message may contain letters and/or numbers.

The method and principle of updating the verification code sender number corresponding to each service in the terminal whitelist list are the same, and the embodiment of the present invention only uses the first application program and the authentication code sender number corresponding to each application in the terminal. The first service is described as an example and does not have any indicative meaning. The first service is any service corresponding to the first application.

The first application is any application running on the terminal processor, for example, a browser, a client of QQ, Bank of China, or the like. The service corresponding to the first application may be a service generated by the first application when it is used. For example, the service may be a service when the Taobao application is paying, and the service may also be a QQ login.

The identifier of the first application may be a package name corresponding to the first application. For example, when the first application is a Chinese bank, the package name of the first application is com.chinamworld. .bocmbci.

Certainly, each service of each application is also identified. The identifier of each service in the embodiment of the present invention is not limited, and may be set as needed, as long as the service can distinguish other services by the identifier of the service. The embodiment of the present invention does not limit the specific form of the whitelist update request, and may be set as needed, where the whitelist update request includes the identifier of the first application, and the whitelist update request generator. The verification code sender number, which is the service corresponding to the application or application that generates the whitelist update request.

The triggering manner of the whitelist update request of the terminal is not limited in the embodiment of the present invention, because the identifier of the first application does not change, but the verification code sender number of the first application and each service of the first application There may be a difference between the corresponding verification code sender numbers, so when the terminal is triggered by the whitelist update request generated by the first application and the whitelist update request generated by the first service of the first application, the whitelist update There is a difference in the sender code of the verification code carried in the request.

Exemplarily, on the one hand, when the first application is first installed on the terminal, it can be determined that the terminal is triggered by the whitelist update request, and the whitelist update request carries the identifier of the first application. And the verification code sender number of the first application.

For example, when the Taobao application or the QQ application is installed on the terminal for the first time, the Taobao application or the QQ application respectively obtains the verification code sender number corresponding to the Taobao application or the QQ application respectively to the corresponding application server.

On the other hand, after the first application is installed on the terminal, if it is determined that the user initiates the indication information of the first application for the first time, it can be determined that the terminal is triggered by the whitelist update request, and the whitelist is updated at this time. The request carries the identifier of the first application and the verification code sender number of the first application. The indication information that the user starts the first application is used to instruct the first application to acquire the short message verification code sent by the verification code sender number corresponding to the first application.

Exemplarily, taking the Meituan application as an example, when the U.S. application is installed on the terminal, when the user first uses it, the user’s display screen is displayed to the user whether it is necessary to obtain the corresponding U.S. application. a verification code sender number, after determining that the first indication information sent by the user is received, sending a request message to the server corresponding to the Meituan application to obtain the corresponding corresponding to the Meituan application Verification code sender number.

In a third aspect, after the first application is installed on the terminal, if it is detected that the terminal uses the indication information of the first service of the first application for the first time, it may be determined that the terminal is triggered by the whitelist update request, and the The whitelist update request carries the identifier of the first application and the verification code sender number of the first service of the first application.

Illustratively, after the US group application is installed on the terminal, when the user first uses the Meituan application to order payment, the Meituan application obtains the user's trigger instruction and then corresponds to the Meituan application. The server sends a request message to obtain a verification code sender number corresponding to the order payment service in the Meituan application.

The method for obtaining the sender code of the verification code carried in the whitelist update request in the embodiment of the present invention is not limited, and exemplary:

In one aspect, the terminal acquires a verification code sender number of the first application or a verification code sender number of the first service of the first application from a configuration file corresponding to the first application.

When developing the first application, the developer writes the verification code sender number of the first application and the verification code sender number of each service of the first application into the first application configuration file of the application, so that the developer The first application's configuration file comes with the verification code sender number of the first application and the verification code sender number of each service of the first application, so that when the first application is used for the first time, or The first service of the first application is used for the first time. When the first application is first installed on the terminal, the terminal may obtain the verification code sender number of the first application from the configuration file of the first application or the The verification code sender number of the first service of the first application.

The embodiment of the present invention acquires, by the terminal from the configuration file of the first application, the verification code sender number of the first application or the verification code sender number of the first service of the first application. The method is not limited, and reference may be made to the prior art.

On the other hand, when it is detected that the first application is first installed on the terminal or the first service of the first application is used for the first time, or when the first application is used for the first time, the terminal sends the application to the application server of the first application. Querying the request message, so that the application server of the first application queries the verification code sender number of the first application or the verification code sender number of the first service of the first application according to the query request message.

Receiving, by the terminal, a query response message sent by the application server corresponding to the first application, where the query response message includes a verification code sender number of the first application or a verification code sender of the first service of the first application number.

The embodiment of the present invention does not limit the specific format and length of the verification code sender number, and may be set as needed. For example, the verification code sender number of the Bank of China is 95566; the verification code of the China Merchants Bank is sent. The party number is 95555 and so on.

The embodiment of the present invention determines, by the terminal, that the first application has the right to update the terminal whitelist list, and on the other hand, may determine whether the user inputs the first indication information, and may pass the verification. Whether the certificate of the first application matches the preset preset certificate, and whether the identifier of the first application matches the preset identifier.

Exemplarily, in order to improve the reliability of the verification code sender number stored in the terminal whitelist, the terminal further includes a display screen.

Correspondingly, as shown in FIG. 2, the determining that the first application has the right to update the terminal whitelist list includes:

S1021A, based on the trigger of the whitelist update request, the terminal displays a first prompt message to the user through the display screen, where the first prompt message is used to prompt the user whether to agree to grant the update to the first application. The permission of the terminal whitelist list;

S1022A: The terminal determines whether the user inputs the first indication information, and the first indication information is used to indicate that the user agrees to grant the first application permission to update the terminal whitelist.

S1023A. If the terminal detects that the user inputs the first indication information, the terminal determines that the first application has the right to update the terminal whitelist list.

The terminal of the embodiment of the present invention includes a display screen, and the display screen may be a touch-sensitive display screen or a non-touch display screen, which is not limited by the embodiment of the present invention.

The first indication information may be a first letter or a first number sent by the user to the preset number by using a short message form, or may be a click by the user collected by the touch controller according to the prompt message in the first prompt information. Is sent to the processor after the word "or agree".

Exemplarily, when the display screen is a touch display screen, the display screen includes a touch screen, a touch screen sensor, and a touch screen controller; wherein the touch screen sensor is configured to detect a user operation instruction, wherein the operation instruction may be The user's touch command may also be a user's selection command. After receiving the operation command, the touch screen sends the operation command to the touch screen controller. The main function of the touch screen controller is to receive touch information from the touch screen sensor and Converted into contact coordinates, and then sent to the terminal's processor, which can also receive commands from the terminal's processor and execute them. When the display screen is a touch-type display screen, if the first prompt message displayed in the dialog box on the display screen is written with the consent authorization click "Yes" or "Agree", disagree with the authorization click "No" "or "disagree", the user can directly click "Yes", and the touch controller determines, according to the "Yes" command collected by the touch sensor, that the first application has the right to update the terminal whitelist list. Otherwise, there is no permission to update the terminal whitelist list.

When the display screen is a non-touch display screen, the user input first indication information may carry the corresponding first letter or the first number to the preset number in the form of a short message if agreed, if not Agree to send the second letter or the second number to the preset number in the form of a short message, where the preset number is set by the terminal according to requirements, and if the terminal receives the first letter or the first number, the first An application has the right to update the terminal whitelist list, otherwise it is determined that the first application does not have the right to update the terminal whitelist.

Optionally, the method further includes:

S1024A, if the terminal detects that the user inputs the second indication information, it is determined that the first application does not have the right to update the terminal whitelist list, and the second indication information is used to indicate that the user has different intentions. The first application grants permission to update the whitelist.

Of course, the form and content of the second indication information may refer to the form and the content of the first indication information. The embodiments of the present invention are not described herein again.

On the other hand, as shown in FIG. 3, FIG. 3 differs from FIG. 2 in that the determining that the first application has the right to update the terminal whitelist list is exemplary. The first application has the right to update the terminal whitelist list, including:

S1021B. The terminal acquires a certificate and an identifier of the first application according to the trigger of the whitelist update request.

The device, when the first application is installed on the terminal, can obtain the application information corresponding to the first application, including: a package name, a certificate, a signature, a hash value, and version information.

The identifier of the first application may be an application package name of the first application.

S1022: The terminal determines whether the certificate of the first application and the preset certificate match, and whether the identifier of the first application and the preset identifier match;

S1023B, if the terminal determines that the certificate of the first application matches the preset certificate, and the identifier of the first application matches the preset identifier, determining that the first application has the terminal white Permissions for the list of lists.

The method further includes:

S1024B, when the certificate of the first application does not match the preset certificate, or the identifier of the first application does not match the preset identifier, determining that the first application does not have the update Permissions for the terminal whitelist.

It is to be noted that, after determining that the first application does not have the right to update the terminal whitelist, the terminal sends a response message to the first application, to indicate that the first application is not The user has the right to update the terminal whitelist list. At this time, the terminal whitelist list update ends.

The specific implementation manner of the step S102 is not limited in the embodiment of the present invention. For example, as shown in FIG. 4, the following steps may be implemented:

S1021: The terminal determines whether the verification code sender number of the whitelist update request generator is already registered in the terminal whitelist list;

When the whitelist update request generator is the first application or the first service of the first application, the terminal performs an inquiry in the terminal whitelist according to the identifier of the first application. Determining whether the verification code sender number of the first application is already registered in the terminal whitelist.

S1022. If the terminal determines that the verification code sender number of the whitelist update request generator is not registered in the terminal whitelist, the terminal identifies the identifier of the first application and the first The verification code sender number of the whitelist update request generator corresponding to the identifier of an application is written in the terminal whitelist list.

Since the correspondence between the verification code sender number of the whitelist update request generator and the identifier of the first application is stored in the terminal whitelist, the terminal determines the terminal by using the identifier of the first application as an index. When the identifier of the first application does not exist in the whitelist, it may be determined that the verification code sender number of the whitelist update request generator is not registered in the terminal whitelist.

The identifier of the first application and the verification code sender number of the first application There is a correspondence between them. When an application has multiple service types, each service type includes multiple services, and each service corresponds to one verification code sender number. At this time, the identifier of one application corresponds to multiple verification code sender numbers. When an application has only one service, at this time, the identifier of one application may correspond to one verification code sender number, or may correspond to two verification code sender numbers.

In the embodiment of the present invention, the identifier of the first application and the verification code sender number of the whitelist update request generator corresponding to the identifier of the first application are written in the terminal whitelist. The manner is not limited, and specific reference may be made to the manner in the prior art.

Certainly, when an identifier of an application has a record item in the terminal whitelist list, it may be determined that the verification code sender number of the whitelist update request generator is registered in the terminal whitelist list, where In order to update the verification code sender number of each application in the terminal whitelist list or the verification code sender number of the first service, the embodiment of the present invention further includes:

S1023. If the terminal determines that the verification code sender number of the whitelist update request generator is already registered in the terminal whitelist, the terminal determines whether the original verification code sender number and the new verification code sender number are Consistent; the original verification code sender number is a verification code sender number of the white list update request generator that has been registered in the terminal whitelist list, and the new verification code sender number is the white list The verification code sender number of the whitelist update request generator in the update request;

S1024. If the terminal determines that the original verification code sender number is inconsistent with the new verification code sender number, the terminal deletes the original verification code sender number from the terminal whitelist list, and The new verification code sender number is written in a location in the terminal whitelist list corresponding to the identifier of the first application.

The embodiment of the present invention does not limit the storage manner of the whitelist of the terminal. For example, the whitelist of the terminal in the embodiment of the present invention may be stored in the whitelist management entity. The specific structure of the management entity is not limited. The whitelist management entity may be a hardware entity capable of implementing a whitelist of storage/management terminals, or may be implemented by a hardware entity and a software module to implement a whitelist of storage/management terminals. The device, the whitelist management entity in the embodiment of the present invention may include: a storage module and a management module, wherein the storage module is configured to store the terminal whitelist. The management module is configured to manage the terminal whitelist list, for example, adding a verification code sender number of an application or an application service in the terminal whitelist list, and deleting the verification of the service of an application or an application. Code sender number, the verification code sender number of the service that updates an application or application. Changing a correspondence between some verification code sender numbers in the terminal whitelist list and an identifier of the first application; and determining, according to the query request message sent by the terminal, whether the verification code sender number or the identifier of the application is stored in the Terminal whitelist list. Of course, the terminal can also interact. The whitelist management entity can be installed in the terminal or installed outside the terminal.

The storage module may be a baseband modem, and the storage module and the management module may run under a TEE (Trusted Execution Environment) or a REE (Rich Execution Environment). Can also run Under SE (Secure Element). Among them, TEE is a standardized and trusted execution environment defined by the Global Platform International Standards Organization (GlobalPlatform), which is a secure area residing on the main processor of the connected device to ensure that it is in a trusted execution environment. Storage, processing and protection of sensitive data. The Trusted Execution Environment is a trusted operating system with secure processing capabilities and security peripheral operations. It is isolated and independent from REE on the same device. Compared with TEE, REE has powerful processing and multimedia operating systems. Such as Android, Windows Phone, iOS, etc.; SE consists of software and tamper-resistant hardware, limited processing capacity, no peripherals, support for high-level security, such as SIM card, financial IC card, smart SD card, etc., can be combined with TEE Run together.

It should be noted that the method for the terminal whitelist list provided by the embodiment of the present invention may be used in any of the foregoing environments.

In order to save the storage space of the terminal whitelist, the method provided by the embodiment of the present invention further includes the following step S104:

S104: The verification code sender number corresponding to the first application is deleted from the terminal whitelist list, where the first application is in the terminal whitelist list, and the user usage frequency is lower than the preset time in the preset time. Set the threshold for the application.

The step S104 can be specifically implemented by the following steps:

S1041: The terminal acquires a frequency of use of the whitelist update request generator in the terminal whitelist list in a preset time;

The frequency of use may be the number of times the user clicks on each application within a preset period, and the frequency of use of each application may be stored in a memory of the terminal, and the frequency of use may be from a memory of the terminal by the processor of the terminal. Obtained in. The embodiment of the present invention does not limit the manner in which the processor obtains the frequency of use of the application from the memory of the terminal, and may be selected according to requirements, and details are not described herein again.

The preset period is not limited in the embodiment of the present invention, and may be set as needed, for example, one week, one month, or one year.

S1042: The terminal deletes, from the terminal whitelist, the verification code sender number of the whitelist update request generator whose frequency is less than a preset threshold in the terminal whitelist.

It should be noted that, when the first application includes multiple service types, and each service type includes multiple services, the verification code sender number corresponding to the first application may refer to a verification code sender corresponding to the service. The verification code sender number whose frequency is lower than the preset threshold is used in the number.

The preset threshold is not limited in the embodiment of the present invention, and may be set as needed.

Further, in order to enable each terminal to update the terminal whitelist list in time, the method further includes:

S105. Send a first whitelist update request to the server, so that the server periodically synchronizes the updated server whitelist list to the terminal that communicates with the server according to the first whitelist update request. A whitelist update request carries at least the verification code sender number of the whitelist update request generator; the first whitelist update request is used to update the whitelist update request generator in the server whitelist list Verification code sender number.

The embodiment of the present invention does not limit the server, and the server is used to store the server. a whitelist list for storing a verification code sender number corresponding to each application in the plurality of applications and a verification code sender number of the service corresponding to each application, the verification code sender number being used The verification code message is sent; the terminal can update the terminal white list in the terminal by connecting with the server. The server can be a cloud server.

As shown in FIG. 5, the embodiment of the present invention further provides a whitelist update method, which is applied to a server. As shown in FIG. 5, the method includes:

S501. The server receives a first whitelist update request, where the first whitelist update request is used to indicate an update server whitelist list. The first whitelist update request includes at least an identifier of the first application, and a whitelist update. a verification code sender number of the requesting generator; wherein the whitelist update request is generated by the first application or generated by the first service of the first application;

The server in the embodiment of the present invention is configured to store a server whitelist, where the server whitelist is used to store a verification code sender number corresponding to each application in multiple applications, and a corresponding one of each application. The verification code sender number of the service, and the terminal can update the terminal white list in the terminal by connecting with the server.

S502. The server determines whether the first whitelist update request meets an update condition.

The first whitelist update request further carries a certificate and an identifier of the first application.

In order to enable the server to grasp in real time the update status of the verification code sender number of each application in the whitelist list, and reduce the number of times of upgrading the large version whitelist list, further reduce the burden on the server, if the first white list update request For the terminal, the update condition is that the certificate of the first application included in the first whitelist update request is consistent with the certificate corresponding to the first application stored in the server, and the The identifier of the first application is consistent with the identifier corresponding to the first application stored in the server in advance;

When the first whitelist update request is not sent by the terminal, the update condition is that the first whitelist update request carries update information corresponding to the terminal, and the update information includes an updated version difference, an update time, and The result of whether the whitelist update request generator's verification code sender number has been updated in the terminal whitelist list.

The first whitelist update request sent by the application server corresponding to the application that establishes the connection with the server to the server may be determined not to be sent by the terminal.

The certificate corresponding to the first application can be obtained by:

A1. When developing the first application, the developer sends a first request to the server, where the first request is used to update the authorization information of the server whitelist stored in the server;

A2. The server sends a certificate according to the first request, where the certificate is used to determine whether the first application has the right to update a server whitelist stored in the server;

A3. The developer packages the certificate in an application configuration file of the first application (for example, an APK, an Android PackageAndroid installation package), that is, obtains a certificate of the first application.

The certificate corresponding to the first application stored in the server may be acquired by the server after receiving the first request, or the server may receive the first request. At the same time, the certificate corresponding to the first application is obtained.

S503. The server determines, if the first whitelist update request meets an update condition, the service The server then updates at least the verification code sender number of the whitelist update request generator to the server whitelist.

In order to enable the terminal to achieve the purpose of updating the terminal whitelist list by upgrading the large version, the server in the embodiment of the present invention synchronizes the updated server whitelist to the terminal that communicates with the server according to a preset period. .

The preset period is not limited in the embodiment of the present invention, and may be set according to requirements, or may be set according to update information of each terminal acquired by the application server, where the update information includes updated version difference, update time, and update. result.

The preset period in the embodiment of the present invention may be one week, one year, or one month.

The embodiment of the present invention provides a whitelist update method, where the server receives the first whitelist update request, and after determining that the first whitelist update request satisfies the update condition, the sender code of the whitelist update request generator is sent. Update to the server whitelist list, so that the terminal can update the terminal whitelist list by synchronizing with the server. The problem that the update period caused by the upgrade of the large version is required when the application cannot update the whitelist list and the terminal updates the terminal whitelist list in the prior art is solved.

The manner of obtaining the identifier corresponding to the first application and the identifier corresponding to the first application stored in the server is similar to the manner of the certificate of the first application, and the embodiment of the present invention is no longer used herein. Narration.

As shown in FIG. 6, the embodiment of the present invention provides a whitelist updating apparatus. As shown in FIG. 6, the whitelist updating apparatus is applied to a terminal, and is used to execute the steps performed by the terminal in the above method. The whitelist updating device may include a module corresponding to the corresponding step. For example, the whitelist update device includes:

The determining unit 601 is configured to determine, according to a trigger of the whitelist update request, whether the first application has the right to update the terminal whitelist, wherein the whitelist update request is generated by the first application or a first service generation of the first application, the whitelist update request including an identifier of the first application, and a verification code sender number of the whitelist update request generator; the terminal whitelist is used for Storing a verification code sender number for transmitting a verification code message;

The determining unit 602 is configured to determine that the first application has the right to update the whitelist of the terminal;

The updating unit 603 is configured to: when the determining unit determines that the first application has the right to update the whitelist of the terminal, update at least the verification code sender number of the whitelist update request generator to the terminal In the whitelist list.

Optionally, as shown in FIG. 7, the terminal further includes a display screen, and correspondingly, the determining unit 602 includes:

The display module 6021A is configured to display, by using the display screen, a first prompt message to the user by using the display screen, where the first prompt message is used to prompt the user whether to agree to grant an update to the first application. The authority of the terminal whitelist list;

The first determining module 6022A is configured to determine whether the user inputs the first indication information, where the first indication information is used to indicate that the user agrees to grant the first application to update the terminal whitelist. List permissions;

The first determining module 6023A is configured to determine, when the first determining module determines that the user inputs the first indication information, determining that the first application has the right to update the terminal whitelist.

Optionally, as shown in FIG. 7, the determining unit 602 includes:

The obtaining module 6021B is configured to acquire a certificate and an identifier of the first application according to the trigger of the whitelist update request;

The second determining module 6022B is configured to determine whether the certificate of the first application and the preset certificate match, and whether the identifier of the first application and the preset identifier match;

a second determining module 6023B, configured to: when the second determining module determines that the certificate of the first application matches the preset certificate, and the identifier of the first application matches the preset identifier, determining the first An application has the right to update the terminal whitelist list.

Optionally, the updating unit 603 includes:

a third determining module, configured to determine whether a verification code sender number of the whitelist update request generator is already registered in the terminal whitelist;

a first update module, configured to: when the third determining module determines that the verification code sender number of the whitelist update request generator is not registered in the terminal whitelist, the identifier of the first application is And the verification code sender number of the whitelist update request generator corresponding to the identifier of the first application is written in the terminal whitelist.

Optionally, the updating unit 603 further includes:

a fourth determining module, configured to: when the third determining module determines that the verification code sender number of the whitelist update request generator is registered in the terminal whitelist, determine the original verification code sender number and the new Verification code sender number is consistent; the original verification code sender number is a verification code sender number of the white list update request generator that has been registered in the terminal white list, the new verification code sender The number is a verification code sender number of the whitelist update request generator in the whitelist update request;

a second update module, configured to: when the fourth determining module determines that the original verification code sender number is inconsistent with the new verification code sender number, then send the original verification code sender number from the terminal whitelist list And deleting, and writing the new verification code sender number into a location in the terminal whitelist list corresponding to the identifier of the first application.

Optionally, the device further includes:

a statistic unit, configured to acquire a frequency of use of the whitelist update request generator in the terminal whitelist list in a preset time;

And a deleting unit, configured to delete, from the terminal whitelist, the verification code sender number of the whitelist update request generator whose usage frequency is less than a preset threshold in the terminal whitelist.

Optionally, the device further includes:

a sending unit, configured to send a first whitelist update request to the server, so that the server periodically synchronizes the updated server whitelist list to the terminal that communicates with the server according to the first whitelist update request; The first whitelist update request carries at least the verification code sender number of the whitelist update request generator; the first whitelist update request is used to update the service The white card of the whitelist update request generator's verification code sender number.

As shown in FIG. 8, an embodiment of the present invention provides a whitelist updating apparatus, where the whitelist updating apparatus is configured to execute the steps performed by a server in the whitelist updating method. The whitelist updating device may include a module corresponding to the corresponding step. As shown in FIG. 8, the whitelist updating device includes:

The receiving unit 801 is configured to receive a first whitelist update request, where the first whitelist update request is used to indicate an update server whitelist list; and the first whitelist update request includes at least an identifier, a whitelist of the first application. Updating a verification code sender number of the request generator; wherein the white list update request is generated by the first application or generated by the first service of the first application;

The determining unit 802 is configured to determine whether the first whitelist update request meets an update condition;

The updating unit 803 is configured to: when the determining unit determines that the first whitelist update request meets an update condition, the server updates at least the verification code sender number of the whitelist update request generator to the server white In the list of names.

Optionally, the device further includes:

And a synchronization unit, configured to synchronize the updated server whitelist list to the terminal that communicates with the server according to a preset period.

Optionally, the first whitelist update request further carries a certificate and an identifier of the first application.

If the first whitelist update request is sent by the terminal, the update condition is a certificate of the first application included in the first whitelist update request and the first application pre-stored in the server The certificate corresponding to the program is consistent, and the identifier of the first application is consistent with the identifier corresponding to the first application stored in the server in advance;

As shown in FIG. 9, an embodiment of the present invention provides a terminal, including: a processor 30, a memory 31, a system bus 32, and a communication interface 33;

The memory 31 is configured to store computer execution instructions, the processor 30 is coupled to the memory 31 via the system bus 32, and when the terminal is running, the processor 30 executes the memory stored by the memory 31 The computer executes the instructions, so that the terminal performs the method performed by the terminal in the whitelist updating method shown in any one of FIG. 1 to FIG. 4, and the specific whitelist updating method can be referred to any of the foregoing FIG. 1 to FIG. The related description in the embodiment shown is not described here.

The processor 30 can be a central processing unit (English: central processing unit, abbreviation: CPU). The processor 30 can also be other general-purpose processors, digital signal processing (DSP), application specific integrated circuit (ASIC), field programmable gate array (English) : field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The processor 30 can be a dedicated processor, and the dedicated processor can include a baseband processing chip, At least one of a radio frequency processing chip or the like. Further, the dedicated processor may also include a chip having other dedicated processing functions of the user equipment.

The memory 31 may include a volatile memory (English: volatile memory), such as a random access memory (English: random-access memory, abbreviation: RAM); the memory 31 may also include a non-volatile memory (English: Non-volatile memory, such as read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English) : solid-state drive, abbreviated: SSD); the memory 31 may also include a combination of the above types of memories.

The system bus 32 can include a data bus, a power bus, a control bus, and a signal status bus. For the sake of clarity in the present embodiment, various buses are illustrated as the system bus 32 in FIG.

The communication interface 33 may specifically be a transceiver on the terminal. The transceiver can be a wireless transceiver. For example, the wireless transceiver can be an antenna of the terminal or the like. The processor 30 transmits and receives data to and from other devices, such as a base station, through the communication interface 33.

The embodiment of the present invention provides a terminal, by receiving a whitelist update request for updating a terminal whitelist list sent by the first application, and updating the terminal whitelist after determining that the first application has the right to update the terminal whitelist list. List, such that when the whitelist update request generator's verification code sender number is changed or the whitelist update request generator's verification code sender number needs to be re-registered in the whitelist list, there is no need to present to the developer of the whitelist list The application requests to update the terminal whitelist list, and the terminal whitelist list is updated in time according to the trigger of the first application generated or the whitelist update request generated by the first service of the first application, which is simple and solves the prior art. The application cannot update the terminal whitelist list autonomously and update the terminal whitelist list period.

In the specific implementation process, each step in the flow of the whitelist updating method described in any one of the above-mentioned FIG. 1 to FIG. 10 can be implemented by the processor 30 in hardware form executing the computer-executed instructions in the form of software stored in the memory 31. . To avoid repetition, we will not repeat them here.

The embodiment further provides a storage medium, which may include the memory 31.

The embodiment of the present invention provides a readable medium, including computer execution instructions, when the processor of the user equipment executes the computer to execute an instruction, the terminal performs any one of the foregoing first aspect or the first aspect. The whitelist update method described in the above.

As shown in FIG. 10, an embodiment of the present invention provides a server, including: a processor 40, a memory 41, a system bus 42, and a communication interface 43;

The memory 41 is configured to store computer execution instructions, the processor 40 is coupled to the memory 41 via the system bus 42, and when the server is running, the processor 40 executes the memory stored by the memory 41 The computer executes the instructions to cause the server to perform the method performed by the server in the whitelist update method as described in FIG. For a specific whitelist update method, refer to the related description in the foregoing embodiment shown in FIG. 5, and details are not described herein again.

The embodiment of the present invention provides a server, after receiving the first whitelist update request, after determining that the first whitelist update request satisfies the update condition, updating the verification code sender number of the whitelist update request generator to the In the server whitelist list, the terminal can update the terminal whitelist list by synchronizing with the server. The prior art application cannot be solved by itself. The main update whitelist list and the terminal update the terminal whitelist list require a long update period caused by upgrading the large version.

The embodiment of the present invention provides a readable medium, including computer execution instructions. When a processor of a server executes the computer execution instruction, the server performs a method corresponding to the server in the whitelist update as described in FIG. 5.

The processor 40 can be a CPU. The processor 40 can also be other general purpose processors, DSPs, ASICs, FPGAs or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The processor 40 may be a dedicated processor, which may include at least one of a baseband processing chip, a radio frequency processing chip, and the like. Further, the dedicated processor may also include a chip having other dedicated processing functions of the server.

The memory 41 may include a volatile memory such as a random access memory RAM; the memory 41 may also include a non-volatile memory such as a read only memory ROM, a flash memory, an HDD or an SSD; A combination of memories of the above kind may be included.

The system bus 42 can include a data bus, a power bus, a control bus, and a signal status bus. For the sake of clarity in the present embodiment, various buses are illustrated as system bus 42 in FIG.

The communication interface 43 may specifically be a transceiver on a server. The transceiver can be a wireless transceiver. The processor 40 performs data transmission and reception with other devices, such as user equipment, through the communication interface 43.

In a specific implementation process, each step of the server in the method flow shown in FIG. 5 above may be implemented by the processor 40 in hardware form executing a computer-executed instruction in the form of software stored in the memory 41. To avoid repetition, we will not repeat them here.

FIG. 11 is a schematic structural diagram of a mobile terminal according to an embodiment of the present invention. The mobile terminal provided by the embodiment of the present invention may be used to implement the method implemented by the embodiments of the present invention shown in FIG. 1 to FIG. 4, for convenience of description. Only parts related to the embodiments of the present invention are shown, and the specific technical details are not disclosed. Please refer to the embodiments of the present invention shown in FIGS.

The mobile terminal can be a terminal device such as a mobile phone, a tablet computer, a notebook computer, a UMPC (Ultra-mobile Personal Computer), a netbook, a PDA (Personal Digital Assistant), and the like. The mobile phone will be described as an example, and FIG. 11 is a block diagram showing a part of the structure of the mobile phone 300 related to each embodiment of the present invention.

As shown in FIG. 11, the mobile phone 300 includes components such as an RF (radio frequency) circuit 320, a memory 330, an input unit 340, a display unit 350, a gravity sensor 360, an audio circuit 370, a processor 380, and a power source 390. It will be understood by those skilled in the art that the structure of the handset shown in FIG. 11 does not constitute a limitation to the handset, and may include more or less components than those illustrated, or some components may be combined, or different components may be arranged. The components of the mobile phone 300 will be specifically described below with reference to FIG. 3:

The RF circuit 320 can be used for transmitting and receiving information or during a call, and receiving and transmitting the signal. Specifically, after receiving the downlink information of the base station, the processing is performed by the processor 380. In addition, the uplink data is sent to the base. station. Generally, RF circuits include, but are not limited to, an antenna, at least one amplifier, a transceiver, a coupler, an LNA (low noise amplifier), a duplexer, and the like. In addition, RF circuitry 320 can also communicate with the network and other devices via wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to GSM (global system of mobile communication), GPRS (general packet radio service), CDMA (code division multiple access) , code division multiple access), WCDMA (wideband code division multiple access), LTE (long term evolution), e-mail, SMS (short messaging service), and the like.

The memory 330 can be used to store software programs and modules, and the processor 380 executes various functional applications and data processing of the mobile phone 300 by running software programs and modules stored in the memory 330. The memory 330 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored according to The data created by the use of the mobile phone 300 (such as audio data, image data, phone book, etc.) and the like. Moreover, memory 330 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The input unit 340 can be configured to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the handset 300. In particular, the input unit 340 can include a touch screen 341 as well as other input devices 342. A touch screen 341, also referred to as a touch panel, can collect touch operations on or near the user (such as the user's operation on or near the touch screen 341 using any suitable object or accessory such as a finger, stylus, etc.), and The corresponding connecting device is driven according to a preset program. Alternatively, the touch screen 341 may include two parts of a touch detection device and a touch controller. Wherein, the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information. The processor 380 is provided and can receive commands from the processor 380 and execute them. In addition, the touch screen 341 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch screen 341, the input unit 340 may also include other input devices 342. In particular, other input devices 342 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control buttons, power switch buttons, etc.), trackballs, mice, joysticks, and the like.

The display unit 350 can be used to display information input by the user or information provided to the user and various menus of the mobile phone 300. The display unit 350 may include a display panel 351. Alternatively, the display panel 341 may be configured in the form of an LCD (Liquid Crystal Display), an OLED (Organic Light-Emitting Diode), or the like. Further, the touch screen 341 can cover the display panel 351, and when the touch screen 341 detects a touch operation on or near it, transmits to the processor 380 to determine the type of the touch event, and then the processor 380 displays the panel according to the type of the touch event. A corresponding visual output is provided on the 351. Although in FIG. 3, the touch screen 341 and the display panel 351 function as two separate components to implement the input and input functions of the mobile phone 300, in some embodiments, the touch screen 341 can be integrated with the display panel 351 to implement the mobile phone 300. Input and output functions.

Gravity sensor 360, can detect the phone in all directions (usually The three-axis acceleration, the magnitude and direction of gravity can be detected at rest, and can be used to identify the gesture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, Tap) and so on.

The handset 300 can also include other sensors, such as light sensors. In particular, the light sensor can include an ambient light sensor and a proximity light sensor. The ambient light sensor can adjust the brightness of the display panel 341 according to the brightness of the ambient light; the proximity light sensor can detect whether an object approaches or contacts the mobile phone, and can close the display panel 341 and/or the backlight when the mobile phone 300 moves to the ear. . The mobile phone 300 can also be configured with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, and the like, and will not be described herein.

Audio circuitry 370, speaker 371, microphone 372 can provide an audio interface between the user and handset 300. The audio circuit 370 can transmit the converted electrical data of the received audio data to the speaker 371, and convert it into a sound signal output by the speaker 371; on the other hand, the microphone 372 converts the collected sound signal into an electrical signal, by the audio circuit 370. After receiving, it is converted to audio data, and then the audio data is output to the RF circuit 320 for transmission to, for example, another mobile phone, or the audio data is output to the memory 330 for further processing.

Processor 380 is the control center of handset 300, which connects various portions of the entire handset using various interfaces and lines, by running or executing software programs and/or modules stored in memory 330, and recalling data stored in memory 330, The various functions and processing data of the mobile phone 300 are performed to perform overall monitoring of the mobile phone. Optionally, the processor 380 may include one or more processing units; preferably, the processor 380 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, an application, and the like. The modem processor primarily handles wireless communications. It will be appreciated that the above described modem processor may also not be integrated into the processor 380.

The handset 300 also includes a power source 390 (such as a battery) that supplies power to the various components. Preferably, the power source can be logically coupled to the processor 380 via a power management system to manage functions such as charging, discharging, and power management through the power management system.

Although not shown, the mobile phone 300 may further include a WiFi (Wireless Fidelity) module, a Bluetooth module, and the like, and details are not described herein again.

In the embodiment of the present invention, the memory 330 is further configured to store various execution instructions when the terminal performs the whitelist update mode.

In the embodiment of the present invention, the processor 380 is further configured to determine, according to the trigger of the whitelist update request, whether the first application has the right to update the terminal whitelist, wherein the whitelist update request is used by the first application. Generating or generating a first service of the first application, the whitelist update request including an identifier of the first application, and a verification code sender number of the whitelist update request generator; the terminal The whitelist is used to store the verification code sender number of the whitelist update request generator;

If it is determined that the first application has the right to update the whitelist of the terminal, at least the verification code sender number of the whitelist update request generator is updated to the terminal whitelist.

It will be clearly understood by those skilled in the art that for the convenience and brevity of the description, only the division of each functional module described above is exemplified. In practical applications, the above functions may be divided as needed. The configuration is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. For the specific working process of the system, the device and the unit described above, reference may be made to the corresponding process in the foregoing method embodiments, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be used. Combinations can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a computer device (which may be a personal computer, a server, Either a network device or the like) or a processor performs all or part of the steps of the method described in various embodiments of the invention. The storage medium is a non-transitory medium, including: a flash memory, a mobile hard disk, a read only memory, a random access memory, a magnetic disk, or an optical disk, and the like, which can store program code.

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Claims

A method for updating a whitelist is characterized in that it is applied to a terminal, and the first application is run on the terminal, and the method includes:

The terminal determines, according to a trigger of the whitelist update request, whether the first application has the right to update the terminal whitelist, wherein the whitelist update request is generated by the first application or the first application a first service generation of the program, where the whitelist update request includes an identifier of the first application, and a verification code sender number of the whitelist update request generator; the terminal whitelist is used to store the transmission verification The verification code sender number of the code message;

If it is determined that the first application has the right to update the whitelist of the terminal, at least the verification code sender number of the whitelist update request generator is updated to the terminal whitelist.
The method of claim 1 wherein said terminal further comprises a display screen.

The terminal determines that the first application has the right to update the terminal whitelist list, including:

The terminal, according to the trigger of the whitelist update request, displays, by using the display screen, a first prompt message to the user, where the first prompt message is used to prompt the user whether to agree to grant the first application to update the terminal. Permissions for whitelists;

Determining, by the terminal, whether the user inputs the first indication information; the first indication information is used to indicate that the user agrees to grant the first application the right to update the terminal whitelist list;

If the terminal detects that the user inputs the first indication information, it determines that the first application has the right to update the terminal whitelist list.
The method according to claim 1, wherein the determining that the first application has the right to update the terminal whitelist list comprises:

The terminal acquires a certificate and an identifier of the first application according to the trigger of the whitelist update request;

Determining, by the terminal, whether the certificate of the first application and the preset certificate match, and whether the identifier of the first application and the preset identifier match;

If the terminal determines that the certificate of the first application matches the preset certificate, and the identifier of the first application matches the preset identifier, determining that the first application has the terminal whitelist list updated permission.
The method according to claim 1, wherein the updating of the verification code sender number of the whitelist update request generator to the terminal whitelist list comprises:

Determining, by the terminal, whether a verification code sender number of the whitelist update request generator is already registered in the terminal whitelist;

If the terminal determines that the verification code sender number of the whitelist update request generator is not registered in the terminal whitelist, the terminal identifies the identifier of the first application and the first application. The verification code sender number of the whitelist update request generator corresponding to the identifier of the program is written in the terminal whitelist list.
The method of claim 4, wherein the method further comprises:

If the terminal determines that the verification code sender number of the whitelist update request generator is already registered In the terminal whitelist list, the terminal determines whether the original verification code sender number is consistent with the new verification code sender number; the original verification code sender number is the one that has been registered in the terminal whitelist list. a whitelist update request sender's verification code sender number, the new verification code sender number being a verification code sender number of the whitelist update request generator in the whitelist update request;

If the terminal determines that the original verification code sender number is inconsistent with the new verification code sender number, the terminal deletes the original verification code sender number from the terminal whitelist list, and the new The verification code sender number is written in a location in the terminal whitelist list corresponding to the identifier of the first application.
The method of any of claims 1-5, wherein the method further comprises:

Obtaining, by the terminal, a frequency of use of the whitelist update request generator in the terminal whitelist list in a preset time;

The terminal deletes the verification code sender number of the whitelist update request generator whose frequency is less than the preset threshold in the terminal whitelist list from the terminal whitelist list.
The method of any of claims 1-6, wherein the method further comprises:

Sending a first whitelist update request to the server, so that the server periodically synchronizes the updated server whitelist list to the terminal connected to the server according to the first whitelist update request; the first white The list update request carries at least the verification code sender number of the whitelist update request generator; the first white list update request is used to update the verification of the whitelist update request generator in the server whitelist list. A code sender number, the server whitelist is used to store a verification code sender number for transmitting a verification code message.
A method for updating a whitelist is characterized in that it is applied to a server, and the method includes:

The server receives a first whitelist update request, where the first whitelist update request is used to indicate an update server whitelist list; the first whitelist update request includes at least an identifier of the first application, and a whitelist update request generation a verification code sender number; wherein the white list update request is generated by the first application or the first service of the first application; the server white list is used to store a verification code message Verification code sender number;

Determining, by the server, whether the first whitelist update request meets an update condition;

If the server determines that the first whitelist update request satisfies the update condition, the server updates at least the verification code sender number of the whitelist update request generator to the server whitelist.
The method of claim 8 further comprising:

The server synchronizes the updated server whitelist list to the terminal that communicates with the server according to a preset period.
The method according to claim 8, wherein the first whitelist update request further carries a certificate and an identifier of the first application;

If the first whitelist update request is sent by the terminal, the update condition is a certificate of the first application included in the first whitelist update request and the first application pre-stored in the server The certificate corresponding to the program is consistent, and the identifier of the first application is consistent with the identifier corresponding to the first application stored in the server in advance;

When the first whitelist update request is not sent by the terminal, the update condition is that the first whitelist update request carries update information corresponding to the terminal, and the update information includes an updated version difference, an update time, and The result of whether the whitelist update request generator's verification code sender number has been updated in the terminal whitelist list.
A whitelist updating device is characterized in that it is applied to a terminal, and the terminal runs a first application, and the device includes:

a determining unit, configured to determine, according to a trigger of the whitelist update request, the terminal, whether the first application has the right to update the terminal whitelist, wherein the whitelist update request is generated by the first application or The first service generation of the first application, the whitelist update request includes an identifier of the first application, and a verification code sender number of the whitelist update request generator; the terminal whitelist list a verification code sender number for storing a verification code message;

a determining unit, configured to determine that the first application has the right to update the whitelist of the terminal;

And an updating unit, configured to update at least the verification code sender number of the whitelist update request generator to the terminal white when the determining unit determines that the first application has the right to update the whitelist list of the terminal In the list of names.
The device according to claim 11, wherein the terminal further comprises a display screen, and the determining unit comprises:

a display module, configured to display, according to the trigger of the whitelist update request, a first prompt message to the user through the display screen, where the first prompt message is used to prompt the user whether to agree to grant the update to the first application The permission of the terminal whitelist list;

a first determining module, configured to determine whether the user inputs the first indication information, where the first indication information is used to indicate that the user agrees to grant the first application the right to update the terminal whitelist list;

The first determining module is configured to determine, when the first determining module determines that the user inputs the first indication information, determining that the first application has the right to update the terminal whitelist.
The device according to claim 11, wherein the determining unit comprises:

An acquiring module, configured to acquire a certificate and an identifier of the first application according to a trigger of the whitelist update request;

a second determining module, configured to determine whether the certificate of the first application and the preset certificate match, and whether the identifier of the first application and the preset identifier match;

a second determining module, configured to: when the second determining module determines that the certificate of the first application matches the preset certificate, and the identifier of the first application matches the preset identifier, determining the first The application has the right to update the terminal whitelist list.
The device according to claim 11, wherein the updating unit comprises:

a third determining module, configured to determine whether a verification code sender number of the whitelist update request generator is already registered in the terminal whitelist;

a first update module, configured to: when the third determining module determines that the verification code sender number of the whitelist update request generator is not registered in the terminal whitelist, the identifier of the first application is And the verification of the whitelist update request generator corresponding to the identifier of the first application The certificate sender number is written in the terminal whitelist.
The device according to claim 14, wherein the device further comprises:

a fourth determining module, configured to: when the third determining module determines that the verification code sender number of the whitelist update request generator is registered in the terminal whitelist, determine the original verification code sender number and the new Verification code sender number is consistent; the original verification code sender number is a verification code sender number of the white list update request generator that has been registered in the terminal white list, the new verification code sender The number is a verification code sender number of the whitelist update request generator in the whitelist update request;

a second update module, configured to: when the fourth determining module determines that the original verification code sender number is inconsistent with the new verification code sender number, then send the original verification code sender number from the terminal whitelist list And deleting, and writing the new verification code sender number into a location in the terminal whitelist list corresponding to the identifier of the first application.
The device according to any one of claims 11-15, wherein the device further comprises:

a statistic unit, configured to acquire a frequency of use of the whitelist update request generator in the terminal whitelist list in a preset time;

And a deleting unit, configured to delete, from the terminal whitelist, the verification code sender number of the whitelist update request generator whose usage frequency is less than a preset threshold in the terminal whitelist.
The device according to any one of claims 11-16, wherein the device further comprises:

a sending unit, configured to send a first whitelist update request to the server, so that the server periodically synchronizes the updated server whitelist list to the terminal connected to the server according to the first whitelist update request; The first whitelist update request carries at least the verification code sender number of the whitelist update request generator; the first whitelist update request is used to update the whitelist update in the server whitelist list. A verification code sender number of the request generator, the server white list being used to store the verification code sender number of the transmission verification code message.
A whitelist updating device, which is applied to a server, the device comprising:

a receiving unit, configured to receive a first whitelist update request, where the first whitelist update request is used to indicate an update server whitelist list; the first whitelist update request includes at least an identifier of the first application, and a whitelist update a verification code sender number of the requesting generator; wherein the whitelist update request is generated by the first application or the first service of the first application; the server whitelist is used to store the transmission verification The verification code sender number of the code message;

a determining unit, configured to determine whether the first whitelist update request meets an update condition;

And an update unit, configured to: when the determining unit determines that the first whitelist update request meets an update condition, the server updates at least the verification code sender number of the whitelist update request generator to the server whitelist List.
The device of claim 18, wherein the device further comprises:

And a synchronization unit, configured to synchronize the updated server whitelist list to the terminal that communicates with the server according to a preset period.
The device according to claim 18, wherein the first whitelist update request further carries a certificate and an identifier of the first application.

If the first whitelist update request is sent by the terminal, the update condition is a certificate of the first application included in the first whitelist update request and the first application pre-stored in the server The certificate corresponding to the program is consistent, and the identifier of the first application is consistent with the identifier corresponding to the first application stored in the server in advance;

When the first whitelist update request is not sent by the terminal, the update condition is that the first whitelist update request carries update information corresponding to the terminal, and the update information includes an updated version difference, an update time, and The result of whether the whitelist update request generator's verification code sender number has been updated in the terminal whitelist list.