WO2015101133A1

WO2015101133A1 - Interface displaying method, device, and system

Info

Publication number: WO2015101133A1
Application number: PCT/CN2014/093116
Authority: WO
Inventors: Wa YE; Qiang Lu; Zhenyu Xu; Xiaoxin Wang
Original assignee: Tencent Technology (Shenzhen) Company Limited
Priority date: 2013-12-30
Filing date: 2014-12-05
Publication date: 2015-07-09
Also published as: CN104753883A; CN104753883B

Abstract

A client executing on a terminal device may perform an interface displaying method. The interface displaying method may include obtaining a display element used for receiving high priority information of a user account, for example from a server. The method may also include obtaining personalized information of the user account and displaying an application interface containing the display element and the personalized information.

Description

INTERFACE DISPLAYING METHOD, DEVICE, AND SYSTEM

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to Chinese Application No. 2013107496499, filed on December 30, 2013, which is hereby incorporated by reference in its entirety.

FIELD OF THE INVENTION

This disclosure relates to network security technology field, and more particularly to an interface displaying method, device and system.

BACKGROUND OF THE INVENTION

Phishing refers to an attack that may include leading users to a phishing website which is similar to an official or authentic website. The phishing website may steal sensitive information inputted by the users on an application interface provided by the phishing website. Some methods for protecting against a phishing website include verifying that the webpage address is legitimate, e.g., by verifying the webpage address through a malicious address database. A warning can be given when the webpage address presented by a browser application interface corresponds to a malicious address. However, such methods may be insufficient to protect a user against phishing websites that are not part of the malicious address database.

BREIF SUMMARY

The present disclosure may provide an interface displaying method, device, and system.

In a first aspect, a method may be performed by an application client executing on a terminal device, and may include the steps of obtaining, from a server, a display element used for receiving high priority information of a user account； obtaining personalized information of the user account； and displaying an application interface containing the display element and the personalized information.

As a second aspect, a server may perform an interface displaying method, which may include the steps of: providing, to a client, a display element used for receiving high priority information of a user account, the display element configured to be cached by the client and displayed on an application interface of the client. The method may also additionally or alternatively include providing, to the client, the display element used for receiving high priority information of a user account and, in addition to the display element, personalized information of the user account to a client, wherein the display element and the personalized information are configured to be displayed on an application interface of the client at the same time.

As a third aspect, an interface displaying device may include a first obtaining module configured to obtain, from a server, a display element used for receiving high priority information of a user account； a second obtaining module, configured to obtain personalized information of the user account； and an interface displaying module or user interface configured to display an application interface containing the display element and the personalized information. The third aspect may, for example, be implemented by a terminal device executing a client application.

As a fourth aspect, an interface displaying device may include a first providing module, a second providing module, or both. The first providing module may be configured to provide, to a client, a display element used for receiving high priority information of a user account, the display element configured to be cached by the client and displayed on an application interface of the client. The second providing module may be configured to provide, to the client, the display element used for receiving the high priority information of the user account and, in addition to the display element, personalized information of the user account. The display element and the personalized information may be configured to be displayed on an application interface of the client at the same time.

As a fifth aspect of the present disclosure, an interface displaying system may include an interface displaying device provided by the third aspect and an interface displaying device provided by the fourth aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

To explain the technical solutions of embodiments of the present disclosure, the accompanying drawings are provided. The following drawings illustrate some exemplary embodiments of the disclosure, but for persons skilled in the art, other drawings can be obtained without creative works according to these drawings.

Fig. 1 is an example of an environment for interface display；

Fig. 2 is a flowchart of one exemplary interface displaying method；

Fig. 3 is a flowchart of another exemplary interface displaying method；

Fig. 4A is a flowchart of another interface displaying method；

Fig. 4B is example application interface that a client device may display；

Fig. 4C is another example application interface that the client device may display；

Fig. 4D is yet another example application interface that the client device may display；

Fig. 5A is a flowchart of an exemplary interface displaying method；

Fig. 5B is an example application interface that the client device may display for obtaining permission to use the personalized information；

Fig. 6 is an example of an interface displaying device, such as the terminal；

Fig. 7A is another example of the interface displaying device；

Fig. 7B is yet another example of the interface displaying device；

Fig. 8 is example of an interface displaying device, such as the server；

Fig. 9A is another example of the interface displaying device；

Fig. 9B is an example of the interfacing displaying device, which includes a providing module； and

Fig. 9C is another example of an interface displaying device that includes the providing module.

DETAILED DESCRIPTION

Other aspects, features, and advantages of this disclosure will become apparent from the following detailed description when taken in conjunction with the accompanying drawings. The embodiments described below are some of the embodiments of the present disclosure, but not all. Persons skilled in the art can obtain other embodiments without creative works, based on these embodiments, which pertains to the protection scope of the present disclosure.

Fig. 1 is an example of an environment 100 for interface display. As shown in Fig. 1, the exemplary environment 100 includes a client 110 and a server 120.

The client 110 may refer to an application client, and may include any combination of software or hardware for executing the application client. The client 110 may be linked to, associated with, or bound a particular user account. For example, the client 110 may take the form of as an instant messaging client or a social application client, with an associated user account. In some variations, the client 110 is provided by a particular service provider. The client 110 may be operated (e.g., executed) on a terminal. In Figure 1, the terminal is a mobile device, such as a cellular telephone. However, the terminal may include any electronic device that executes the client 110, and additional examples include desktop or laptop computers, notebook computers, e-book readers, tablet devices, gateway devices, televisions, gaming systems, personal digital assistants, portable e-mail devices, and many more.

The client 110 may communicate with the server 120 through one or more communication networks. The networks may be wired, wireless, or include combinations of both. The client 110 may communicate with the server 120 to provide an interface display. In that regard, the client may obtain, from the server 120, a display element used for receiving high priority (e.g., sensitive) information of a user account. The client 110 may display or present an application interface that contains the display element, personalized information of the user account, or both. The personalized information may include information set on the client to identify the difference between the particular user account and other user accounts. The personalized information may be set by a user of the client 110, for example. In some implementations, the client 110 may obtain the personalized information from the server 120. In other implementations, the client 110 may read the personalized information from a local cache, e.g., local cache of the terminal.

The server 120 may be an application server provided by a service provider. The server 120 may support, manage, control, or configure one or more operations of the client 110. For example, the server 120 may provide the client 110 with the display element used for receiving high priority (e.g., sensitive) information of the user account. The server 120 may, in some variations, provide personalized information of the user account to the client 110 as well. As discussed in greater detail below, the client 110 may simultaneously provide the display element and personalized information of the user account.

Fig. 2 shows a flowchart 200 of an exemplary interface displaying method according to one embodiment of the present disclosure. The interface displaying method may be performed or implemented by the client 110, the server 120, or both, and may include the following steps:

Step 201, the server 120 may provide a display element to the client 110, the display element configured for use by the client 110 in receiving high priority information of a user account. High priority information may be any information designated as sensitive by the client 110, server 120, or both. For example, the high priority information may include sensitive user information, such as account passwords, social security numbers, financial account information such as credit card numbers, bank account numbers, and the like, personal identification numbers (PINs) , access codes, or any other information that may be designated as user sensitive.

Step 202, the client 110 may obtain (e.g., receive) the display element used for receiving the high priority information of the user account from the server 120.

Step 203, the client 110 may obtain personalized information of the user account.

Step 204, the client 110 may display or present an application interface that contains the display element and the personalized information. For example, the client 110 may present the application interface through a user interface of the terminal executing the client 110, e.g., through a graphical user interface (GUI) .

Thus, the exemplary interface displaying method provided by Fig. 2 may include obtaining the display element used for receiving the high priority information of the user account and the personalized information of the user account, and displaying an application interface containing the display element and the personalized information. Accordingly, the interface display method may allow a user of the client 110 and the terminal to more easily judge whether the application interface is provided by an official, legitimate website or is faked by criminals or cyber-attackers through a phishing technique. The user may make such a determination before inputting sensitive, high priority information to the display element by judging whether the personalized information displayed on the application interface is true, correct, or authentic, or upon identifying the presence of the personalized information on the application interface. Accordingly, the interface display method may reduce occurrences of users inputting sensitive information into phishing websites and reducing thefts of user information.

Fig. 3 shows a flowchart of another exemplary interface displaying method according to another embodiment of the present disclosure. The interface displaying method provided by Fig. 3 may be performed by a client 110, a server 120, or both, and may include the following steps:

Step 301, a server 120 may provide a display element to a client 110, the display element used for receiving high priority information of a user account.

Step 302, the client 110 may obtain (e.g., receive) the display element used for receiving sensitive information of the user account, from the server 120.

Step 303, the server 120 may provide personalized information of the user account to the client 110.

Step 304, the client 110 may receive or obtain the personalized information of the user account, from the server 120.

Step 305, the client 110 may display an application interface that contains the display element and the personalized information.

Thus, the exemplary interface displaying method provided Fig. 3 may include obtaining the display element used for receiving the high priority (e.g., sensitive) information of the user account and the personalized information of the user account, and displaying an application interface containing the display element and the personalized information. Accordingly, the interface display method may allow a user of the client 110 and the terminal to more easily judge whether the application interface is provided by an official, legitimate website or is faked by criminals or cyber-attackers through a phishing technique. The user may make such a determination before inputting sensitive, high priority information to the display element by judging whether the personalized information displayed on the application interface is true, correct, or authentic, or upon identifying the presence of the personalized information on the application interface. Accordingly, the interface display method may reduce occurrences of users inputting sensitive information into phishing websites and reducing thefts of user information.

Optionally, the client 110 can obtain the personalized information of the user account by reading information saved in a local cache or by sending a request to the server 120 for the personalized information of the user account. The above two options will be described in detail respectively below.

Fig. 4A shows a flowchart of an exemplary interface displaying method according to another embodiment of the present disclosure. The interface displaying method shown in Fig. 4 may be performed by the client 110, the server 120, or both, and may include the following steps:

Step 401, the server 120 may provide a display element to a client 110, the display element used for receiving high priority information of a user account.

When accessing a particular application interface provided by the server 120 (e.g., a login screen for a webpage hosted by the server 120) , the client 110 may query the user to input sensitive information on the application interface, such as a password, account number, or PIN. The client 110 may send the sensitive information inputted by the user to the server 120. In order to increase security when the client 110 receives sensitive user information, the server 120 may provide the display element used for receiving the sensitive information of the user account to the client 110. In doing so, the server 120 may facilitate secure input of sensitive account information by the client 110 and guard against phishing schemes. The display element and, optionally personalized information of the user account cached on the client 110, may be displayed on the application interface of the client 110, for example at the same time. The display element may take the form of an input box, and the personalized information may include at least one of the following examples.

As a first example, the personalized information may include an identification of the user account. As identifying aspects of different user accounts may be different, the personalized information of the user account may include the identification of the user account. For example, the personalized information of the user account may include a user name for the user account, a user nickname of the user account, a telephone number bound with the user account, or combinations thereof.

As a second example, the personalized information may include an associated image for the user account, such as head portrait information of the user account. When setting personal data of the user account, the user can set a head portrait, which may be an actual image of the user, a user icon, a profile image, or other image that characterizes the user account. As the head portraits set by different users may differ, so the personalized information of the user account may include the head portrait information of the user account to differentiate or uniquely identify the user account.

As a third example, the personalized information may include a personalized signature of the user account. When using the user account, the user can publish a personalized signature, for example according to his current mood or understanding of life. The personalized signature may be any combination of a custom message, character string, images, hyperlinks, or other data that a user of the user account may personalize or configure. Thus, the personalized information of the user account may include the personalized signature of the user account.

As a fourth example, the personalized information may include information that the user account previously shared on a social information sharing platform, such as a social network. A user may share information on the social information sharing platform to all his friends through the user account or another associated social platform account of the user. A social information sharing platform may include social web sites provided by social applications, and the social web site can simultaneously share information of a user account to some platforms corresponding to some friends’ user accounts. Examples of social information platforms include Facebook (R) , Twitter (R) , Instagram (R) , Google+ (R) , and various other social networking platforms. Thus, the personalized information may include a most recent Facebook status update on Facebook, a most recent Tweet on Twitter, the most recently shared image on Instagram, and the like. As other variations, the personalized information may include previously shared information on the social information sharing platforms, older than the most recently shared information. The information shared by different user accounts at different times may differ, so the personalized information of the user account may include the information that the user account previously shared on a social information sharing platform. As additional examples, the information may include recent information shared through an instant messaging client, e.g., the user shared his newest telephone number among friends through his user account. In this example, the personalized information may include the telephone number shared by the user.

As a fifth example, the personalized information may include communication information that the user account previously communicated with one or more other user accounts. The user can use his user account to communicate with his contacts (e.g., friends) , and the communication information that different users communicate with other user accounts last time may differ from account to account. Thus, the personalized information may include the communication information that the user account previously communicated with other user accounts. For example, if the user chats to his contacts through his user account on an instant messaging client, then the personalized information may include chat records or portions thereof, e.g., selected portions of a most recent conversation by the user and a contact.

As a sixth example, the personalized information may include account information of one or more other user accounts that the user account previously communicated with. The user can communicate with different contacts at different time through his user account, so the personalized information of the user account may include the account information of other user accounts that the user account previously communicated with. In this way, the personalized information my be specific to the user account, such that the identity of recent contacts which the user account communicated with may be known only to the user, thus increasing security. For example, if a particular contact that the user account previously communicated with through his user account on an instant messaging client is “xiao hua” , then the personalized information of the user account may include “xiao hua” . In some variations, the personalized information may include the contacts that the user account recently communicated with, as specified within a particular recent time threshold or in a most recent conversation.

As a seventh example, the personalized information may include information that the user account previously accessed, e.g., visited. The user can visit different information at different times, so the personalized information of the user account may include the information that the user account previously visited, e.g., most recently visited. Examples of such information may include a previously accessed or visited video file, website hyperlink, image, memory location, and the like. For example, if the information that the user account most recently accessed last time is a particular video, the personalized information of the user account may include the name of the particular video, video information for the particular video, or combinations of both.

As an eighth example, the personalized information may include at least one of the name, content characteristics, and related information of an application that the user account previously used. As applications that different user accounts previously used may differ, the personalized information of the user account may include at least one of the name, content characteristics, and related information of the application that the user account most recently or previously used. For example, if the user uses the function named “floating bottle” through his user account, the personalized information of the user account may include or identify the “floating bottle. ” As another example, if the user uses the game of “XX” through his user account, the personalized information of the user account may include the “XX” , a game level of the user in the game of “XX” , or any other associated information of the game of “XX” .

Optionally, the personalized information of the user account may also include any other information representing a difference between the user account and other user accounts. The personalized information may increase authenticity and security that an application interface requesting sensitive information is legitimate and authentic, as these personalized information of the user account may be specific to the user account.

Step 402, the client 110 may obtain the display element used for receiving high priority (e.g., sensitive) information of the user account from the server 120. The client 110 may obtain the display element from the server 120 in response to or specifically when the client 110 queries the user to input high priority or sensitive information. For example, when the user wishes to access a specific application interface that queries or requests sensitive user account information, the client 110 can send a request to the server 120 for the display element. The server 120 may respond by sending the display element to the client 110 after receiving the request. The specific means of how the client 110 may obtain the display element is not limited by this embodiment.

In one illustration, the client 110 may support payment capabilities. When a user requests a payment, the client 110 can send a request to the server 120 for obtaining the display element, and the display element may be used by the client 110 for receiving password on a payment interface. The client 110 may send the request for the display element after the user selects a payment function, for example After the server 120 receives the request, the server 120 may send the display element to the client 110.

Step 403, the server 120 may query account information of a payment account bound with or associated with the user account. The user may bind a particular payment account with the user account, such as bank account, a credit card, or other financial account that supports sending or receiving payments. The server 120 may take specific actions when the client 110 requests a display element for a payment function or when the user account selects a particular payment function of the client 110. When the sensitive or high priority user account information that the client 110 queries the user to input is associated with a financial or payment account (e.g., the application interface the user requests access to is a payment interface) , the server 120 can query the account information of the payment account bound with the user account.

For example, if the user binds his a particular bank card with the user account, such as a XX bank card, and if the user uses the user account to send or receive a payment, the client 110 may support direct use of the XX bank card to perform the payment transition. So, in order to remind or indicate to the user the account information of the bound payment account on the application interface, the server 120 can obtain the account information of the payment account bound with the user account and include the account information as part of the display element. Examples of queried payment information may include the bank card number, bank name of the bank card, or various other financial information associated with the payment account. As one particular example, the server 120 may send a display element that contains the last 4 digits of the bank card number, the bank name of the bank card, or both.

Step 404, the server 120 may provide the queried account information of the payment account to the client. After the server 120 queries the account information of the payment account bound with the user account, the server 120 may provide the queried account information of the payment account to the client 110, e.g., via the display element as discussed above or as a separate item of information. For example, the server 120 can send the account information of the payment account to the client 110 separate from the display element, and the client 110 may present the account information of the payment account, the display element, and the personalized information through the application interface of the client 110, e.g., simultaneously at the same time on the application interface.

Step 405, the client 110 may obtain the account information of the payment account bound with the user account, from the server 120. Steps 403 to 405 are optional steps, and the client 110 can directly perform step 406 without performing steps 403 to 405.

Step 406, the client 110 may access personalized information for the user account from a local cache. The local cache may be a local memory element in the terminal device that executes the client 110. In one variation, the server 120 can cache the personalized information of the user account on the local client 110 (e.g., on the terminal) in advance, prior to execution of the client 110. Thus, when the user requests access to an application information that requires input of high priority or sensitive account information, the client 110 can read the personalized information from the local cache.

To reduce the complexity of the information cached on the local client 110 or terminal device, the server 120 may cache a selected portion of the personal information of the user account on the local cache of the terminal. For instance, the server 120 may cache the head portrait information, identification and chat records between the user account and other user accounts. Then, to access the personalized information, the client 110 can access the local cache and/or access additional personalized information from the server 120, e.g., the personalized information of the user account that is not locally cached in the terminal. For instance, the client 110 may read the identification of the user account, the head portrait information of the user account, and the communication information that the user account previously communicated with other user accounts from a local cache and obtain other personalized information from the server 120 such as information that the user account previously shared on a social information sharing platform, such as a social network.

In variations, the client 110 may obtain the display element, the personalized information of the user account, and the account information of a payment account, and in any order or sequence. The client 110 can obtain the three kinds of information mentioned above at the same time or in any order, e.g., at different cascaded times.

Step 407, the client 110 may display or present an application interface that contains the display element, the personalized information, and the account information of the payment account.

For example, if the personalized information of the user account access by the client 110 is head portrait information, the display element obtained from the server is an input box, and the account information of the payment account includes the last 4 digit of a bank card number such as “8012” and the bank name of the bank card such as “XX bank” , then the client 110 can display an application interface as showed in Figure 4B. Thus, when the user views that the head portrait displayed on the application interface is really the head portrait of his own user account and the account information displayed on the application interface is really the account information of the payment account bound with his own user account, the user can judge the application interface displayed on the client is provided by an official website, so the user can safely input payment keyword in the input box on the application interface； while if the head portrait and account information displayed on the application interface is wrong, the user can judge the application interface may be a phishing website faked by criminals through phishing technique, now the user can not input the payment keyword in the input box on the application interface, thereby avoiding the problem of economic loss that the user faced as a result of the payment keyword being stolen.

As another example, if the personalized information of the user account accessed by the client 110 is head portrait information and the display element obtained from the server 120 is an input box, then the client may display the application interface as showed in Figure 4C, e.g., without the payment account information. Thus, when the user determines that the head portrait displayed on the application interface matches head portrait of his own user account, the user can judge that the application interface displayed on the client is provided by an official, legitimate website. As such, the user can safely input sensitive information in the input box on the application interface, and this may protect against unauthorized input of the user’s sensitive information at illegitimate websites. If the user identifies that the head portrait is not present on the application interface or that the head portrait displayed on the application interface is not the head portrait of his own user account, the user can judge the application interface may be a phishing website faked by criminals through the phishing technique. In this case, the user may not or forgo input of the payment keyword in the input box on the application interface, thereby avoiding the problem of economic loss that the user faced as a result of his payment keyword being stolen.

As yet another example, if the personalized information accessed by the client 110 is information regarding one or more applications that the user account previously used (e.g., as the level of an ‘XX’ game previously accessed by the user account) and the display element obtained from the server is an input box, then the client 110 may display an application interface shown in Figure 4D. Thus, when the user views the application interface that includes personalized information regarding a current level of the ‘XX’ game, the user may identify that the ‘XX’ game application is an application that the user previously accessed through the user account, and that the game level is really his own game level. Then, the user can judge that the application interface displayed on the client 110 is provided by an official or legitimate website, and the user can safely input sensitive information in the input box on the application interface. If the user finds the application such as ‘XX’ game or the game level displayed on the application interface is wrong (e.g., does not correspond to his current level or was not previously accessed by the user) , the user can judge that the application interface may be a phishing website faked by criminals through a phishing technique. In this case, the user can refuse or forego input of the payment keyword in the input box on the application interface, thereby avoiding the problem of economic loss that the user faced as a result of his payment keyword being stolen.

Thus, the interface displaying method discussed above may include obtaining a display element used for receiving the sensitive information of the user account and the personalized information of the user account, and displaying an application interface containing the display element and the personalized information, so that the user can easily judge whether the application interface is provided by the official website or is faked by criminals through the phishing technique. The client 110 may present the application interface before the user inputs high priority or sensitive information into the display element, thereby allowing the user to judge whether the personalized information displayed on the application interface is true, legitimate, or accurate, or whether the personalized information is present at all. Accordingly, the interface display method may reduce occurrences of users inputting sensitive information into phishing websites and reducing thefts of user information.

In the process of displaying the application interface, complexity of the information interactions between the server 120 and the client 110 may be reduced by caching the personalized information on a local memory of the terminal executing hte client 110. Reading the personalized information from the local cache allows the client 110 to display the personalized information directly, thereby improving the efficiency of displaying the application interface by the client 110 as this may reduce the communication bandwidth and resources consumed by the client 110 for presenting the application interface.

In addition, if the sensitive information is payment information, in order to allow the client 110 to display the account information when displaying the application interface, the server 120 can query the account information of a payment account bound with the user account, and send the queried account information to the client 110. Since the account information of the payment account for different users is different, criminals or cyber-attackers may be unable crack the account information through phishing technique, and security may be increased. Thus, by displaying the account information, the interface displaying method may help users to judge whether a webpage or application interface displayed on the client 110 for receiving payment information is a phishing page or not, thereby avoiding the problem of payment information being stolen.

Fig. 5A shows a flowchart 500 of another exemplary interface displaying method according to one embodiment of the present disclosure. The flowchart 500 in Fig. 5A may relate to a variation where the client 110 obtains the personalized information of the user account from the server 120, and may include the following steps:

Step 501, the server 120 may send a permission request to the client 110 for obtaining permission to access, store, or use personalized information of the user account. The server 120 can send a request for obtaining and using any of the personalized information examples discussed above. The personalized information of the user account may additionally or alternatively include any other information representing one or more differences between the user account and other user accounts, or any other identifying or differentiating characteristics.

Step 502, the client 110 may receive the permission request from the server 120 to access, store, or use the personalized information of the user account.

Step 503, the client 110 may respond with authorization information confirming to grant permission to the server 120 to use the personalized information of the user account. The authorization information may be any confirmation or grant message that indicates to that the server 120 has permission or authorization (e.g., from the user) to utilize the personalized information of the user account. For example, after receiving the permission request from the server 120, the client 110 may prompt a user with the permission request by displaying an interface including two options: agreeing to grant the permission or refusing to grant the permission. One example of such an the interface that the client 110 may present is shown in Fig. 5B. If the user permits the server 120 to use his personalized information, the user can select the option of agreeing to grant the permission, so that the client 110 will send the authorization information confirming the grant of permission of using the personalized information to the server 120. Otherwise, if the user chooses the option of refusing to grant the permission, the client 110 will send notification information to the server 120 indicating that the server 120 is not granted permission to use the personalized information of the user account.

Step 504, the server 120 may receive the authorization information from the client 110 confirming the grant of permission to use the personalized information.

Steps from 501 to 504 are optional, and in some variations, the method may start with the step 505. As another example, steps 501 to 504 may be performed separate from or at a different time as steps 505-515. And this embodiment describes the situation of allowing use of the personalized information after obtaining user permission. In some variations, the server 120 may directly access and use the personalized information as long as it previously obtained user permission for using the personalized information. For instance, the steps from 501 to 504 can be performed once, and the method may start at step 505 if steps 501 to 504 were already previously performed.

Step 505, the server 120 may provide a display element to the client 110, which may be used for receiving high priority or sensitive information of a user account.

When accessing a particular application interface provided by the server 120 (e.g., a login screen for a webpage hosted by the server 120) , the client 110 may query the user to input sensitive information on the application interface, such as a password, account number, or PIN. The client 110 may send the sensitive information inputted by the user to the server 120. In order to increase security when the client 110 receives sensitive user information, the server 120 may provide the display element used for receiving the sensitive information of the user account to the client 110. In doing so, the server 120 may facilitate secure input of sensitive account information by the client 110 and guard against phishing schemes. The display element and, optionally personalized information of the user account cached on the client 110, may be displayed on the application interface of the client 110, for example at the same time.

Step 506, the client 110 may receive or obtain the display element from the server 120, which the client 110 may use for receiving sensitive information of the user account.

When the client 110 requests the user to input sensitive information, e.g., when the client 110 accesses a specific application interface that queries or requests sensitive user account information, the client 110 can obtain the display element used for receiving the sensitive information of the user account from the server 120. The client 110 can send a request to the server 120 for the display element. The server 120 may respond by sending the display element to the client 110 after receiving the request. The specific means of how the client 110 may obtain the display element is not limited by this embodiment.

Step 507, the client 110 may send a request to the server 120 for obtaining the personalized information of the user account. When the client 110 accesses a particular application interface (e.g., that requires input of sensitive account information) , the client 110 can request the personalized information from the server 120, e.g., by sending a request to the server 120.

The client 110 can query (e.g., send a request for) the display element and personalized information of the user account from the server 120 at the same time or in a common request message. For instance, the client 110 can send request information to the server 120 that includes both a request for the display element and the personalized information.

Step 508, the server 120 may receive the request for obtaining the personalized information from the client 110.

Step 509, the server 120 may query the personalized information of the user account. For example, the server 120 may access one or more user databases to access the personalized information of the user account. Or the server 120 may communicate with one or more other servers, to retrieve some or all of the personalized information of the user account. The server 120 may do so after obtaining permission to use the personalized information of the user account, e.g., as described in steps 501 to 504.

Step 510, the server 120 may provide the queried personalized information to the client 110. The server 120 can send the queried personalized information to the client 110 after it queries and obtains the personalized information.

Step 511, the client 110 may receive the personalized information returned by the server 120.

Step 512, the server 120 may query account information of a payment account bound with the user account. As noted above, a user can bind or associate a payment account with the user account. When the sensitive information that the client 110 queries the user to input is payment information (e.g., the application interface the user accesses is a payment interface) , the server 120 can query the account information of a payment account bound with the user account, e.g., as discussed above.

Step 513, the server 120 may provide the queried account information of the payment account to the client 110.

Step 514, the client 110 may receive or obtain the account information of the payment account bound with the user account. Steps 512 to 514 are optional, and in some variations, the client 110 and/or server 120 may forego performing steps 512 to 514 and instead perform step 515, e.g., after performing step 511.

Step 515, the client 110 may present or display an application interface containing the display element, the personalized information, and the account information of the payment account. This step may share similarities with step 407 described above.

Accordingly, the interface displaying method provided by this embodiment may include obtaining the display element and the personalized information of the user account, and displaying an application interface containing the display element and the personalized information. Doing so may allow a user to more easily judge whether the application interface is provided by the official, legitimate website or is faked by criminals or cyber-attackers through a phishing technique. The user may make such a determination before inputting sensitive information to the display element by judging whether the personalized information displayed on the application interface is true, legitimate, accurate, or whether the personalized information exists at all. The method may address the problem of sensitive user account information being stolen through phishing websites or other false malicious websites or applications, and may achieve the effect of avoiding the theft of sensitive information of a user account.

This embodiment may include querying for permission by a user and/or client 110 for using, accessing, or displaying the personalized information on the application interface, and such permission may be sought and granted before the server 120 obtains the personalized information of the user account. By ensuring permission for using the personalized information is first granted by user before use and access, the security of the user account’s personalized information may be protected.

In some variations, a portion of the personalized information of a user account may be stored locally and read from a local cache by the client 110, and another portion of the personalized information may be obtained from the server 120. For instance, if the personalized information includes head portrait information of the user account and the name of the application the user account previously used, then the terminal may locally cache the head portrait information, so that the client 110 may read the head portrait information from the local cache. The server 120 may send the name of the application that the user account previously used to the client 110, without having to send the head portrait information, and doing so may reduce the complexity of information interaction between the server 120 and the client 110, and may result in improved efficiency of displaying the personalized information. The specific means of how the client obtains the display element is not limited by this embodiment.

Fig. 6 shows an example of an interface displaying device, such as the terminal that executes the client110. The interface displaying device shown in Figure 6 includes a first obtaining module 610, a second obtaining module 620, and an interface displaying module 630. The modules described herein may be implemented in circuitry, in software, or in any other combination of hardware and/or software.

The first obtaining module 610 may be configured to obtain a display element used for receiving sensitive information of a user account. The first obtaining module 110 may obtain the display element from the server 120, for example. The second obtaining module 620 may be configured to obtain personalized information of a user account, either via a local cache or from the server 120. The interface displaying module 630 may be configured to cause the display of or present an application interface containing the display element obtained by the first obtaining module 610 and the personalized information obtained by the second obtaining module 620.

The interface displaying device provided by in Fig. 8 may obtain a display element used for receiving high priority or sensitive information of the user account as well as the personalized information of the user account. The interface displaying device may present an application interface containing the display element and the personalized information. Accordingly, the interface displaying device may allow a user of the device to more easily judge whether the application interface is provided by an official, legitimate website or is faked by criminals or cyber-attackers through a phishing technique. The user may make such a determination before inputting sensitive, high priority information to the display element by judging whether the personalized information displayed on the application interface is true, correct, or authentic, or upon identifying the presence of the personalized information on the application interface. Accordingly, the interface displaying device may reduce occurrences of users inputting sensitive information into phishing websites and reducing thefts of user information.

Fig. 7A shows another example of the interface displaying device. The interface displaying device shown in Fig. 7 includes a first obtaining module 710, a second obtaining module 720, and an interface displaying module 730.

The first obtaining module 710 may be configured to obtain or receive a display element used for receiving sensitive information of a user account, e.g., from a server 120. The second obtaining module 720 may be configured to obtain personalized information of a user account. The interface displaying module 730 may be configured to present or display an application interface containing the display element obtained by the first obtaining module 710 and the personalized information obtained by the second obtaining module 720.

The second obtain module 720 may optionally include a first obtaining unit 721 and/or a second obtaining unit 722, and both are shown in Figure 7. The first obtaining unit 721 may be configured to access or read the personalized information from a local cache of the interface displaying device (e.g., the terminal) . The second obtaining unit 722 may be configured to access the personalized information of the user account from a remote device, such as the server 120. In that regard, the second obtaining unit 722 may be configured to send a request for the personalized information to the server 120, and receive the personalized information sent from the server 120.

Fig. 7B shows yet another possible implementation of an interface displaying device, such as the terminal. The interface displaying device shown in Figure 7B further includes a request receiving module 740 and an information sending module 750. The request receiving module 740 may be configured to receive a permission request from the server 120, and the permission request may request permission for use, access, retrieval, or storage of the personalized information of the user account. The information sending module 750 may be configured to send, to the server 120, authorization information confirming the granting of permission to use the personalized information.

The exemplary interface displaying device shown in Fig. 7B further includes a third obtaining module 760, which may be configured to obtain account information of a payment account bound with, associated with, or linked to the user account. The third obtaining module 760 may obtain the account information from the server 120, for example.

The interface displaying module 730 may be configured to present or display an application interface containing the display element, the personalized information, and the account information of the payment account. The personalized information may include any of the examples of personalized information discussed above.

Thus, the interface displaying device provided by this embodiment may obtain a display element used for receiving the sensitive information of the user account as well as the personalized information of the user account. The interface displaying device may displays an application interface containing the display element and the personalized information. Accordingly, the interface displaying device may allow a user of a client 110 executing on the device to more easily judge whether the application interface is provided by an official, legitimate website or is faked by criminals or cyber-attackers through a phishing technique. The user may make such a determination before inputting sensitive, high priority information to the display element by judging whether the personalized information displayed on the application interface is true, correct, or authentic, or upon identifying the presence of the personalized information on the application interface. Accordingly, the interface displaying device may reduce occurrences of users inputting sensitive information into phishing websites and reducing thefts of user information.

Fig. 8 shows an example of an interface displaying device that may be part of an interface displaying system. For example, the device shown in Fig. 8 may be the server 120. The device includes a first providing module 810 and a second providing module 820.

The first providing module 810 may be configured to provide a display element to a client 110. In that regard, the first providing module 810 may configure the display element to be used for receiving sensitive information of a user account. The display element and personalized information of a user account may be cached at the client 110, for example.

The second providing module 820 may be configured to provide both a display element used for receiving sensitive information of a user account and personalized information of the user account. The second providing module 820 may provide both the display element and the personalized information of the user account to a client 110, and the display element and the personalized information may be configured to be displayed by the client 110 on an application interface, e.g., at the same time.

Fig. 9A shows another example of an interface displaying device that may be part of an interface displaying system, e.g., the server 120. The interface displaying device shown in Fig. 9A includes both a first providing module 910 and a second providing module 920, though the device may optionally include just one of the first providing module 910 or the second providing module 920.

The first providing module 910 may be configured to provide a display element to a client 110. In that regard, the first providing module 910 may configure the display element to be used for receiving sensitive information of a user account. The display element and personalized information of a user account may be cached at the client 110, for example.

The second providing module 920 may be configured to provide both a display element used for receiving sensitive information of a user account and personalized information of the user account. The second providing module 920 may provide both the display element and the personalized information of the user account to a client 110, and the display element and the personalized information may be configured to be displayed by the client 110 on an application interface, e.g., at the same time.

In some variations, including the one shown in Fig. 9B, the second providing module 920 includes a request receiving unit 921, and information querying unit 922, and an information providing unit 923. The request receiving unit 921 may be configured to receive a request from a client 110 to obtain personalized information for a user account. The information querying unit 922 may be configured to query for the personalized information of the user account, e.g., via accessing a local or remote database or querying other information sources. The information providing unit 923 may be configured to provide the queried personalized information to the client 110.

In another variation of an interface displaying device that may be part of an interface displaying system, Fig. 9C shows another implementation of the second providing module 920, which further includes a request sending unit 924 and an information receiving unit 925. The request sending unit 924 may be configured to send a permission request to a client 110 to requesting permission to use, access, store, or otherwise process personalized information of a user account. The information receiving unit 925 may be configured to receive a response from the client 110 to the permission request. For example, the information receiving unit 925 may receive authorization information from the client granting permission to use or otherwise access the personalized information of the user account.

In some variations, the information querying unit 922 may be further configured to perform the operation of querying the personalized information of the user account after receiving the authorization information.

Returning to Fig. 9A, the interface displaying device may further include an information querying module 930 and a third providing module 940. The information querying module 930 may be configured to query for account information of a payment account bound with, associated with, or linked to the user account. The third providing module 940 may be configured to provide the queried account information of the payment account to the client 110, and the client 110 may present an application interface containing the account information of the payment account, the display element, and the personalized information, e.g., at the same time. The personalized information may include any of the examples of personalized information discussed above.

The interface displaying device shown in Figs 9B and 9C show only the second providing module 920, though it is contemplated the devices may include any other modules in other devices or circuitry and logic that are part of the server 120.

In conclusion, the interface displaying device provided by this embodiment obtains the display element used for receiving the sensitive information of the user account and the personalized information of the user account, and displays the application interface containing the display element and the personalized information, so that the user can easily judge whether the application interface is provided by the official website or is faked by criminals through the phishing technique before he inputting sensitive information to the display element by judging whether the personalized information displayed on the application interface is true or whether the personalized information exists, thereby solving the problem of the sensitive information inputted by users being stolen caused by the interface displaying method provided by the prior art, achieving the effect of avoiding the sensitive information of the user account being stolen.

To be clear, multiple interface displaying devices may form an interface displaying system, even when not all of the interface displaying devices display the application interface with the display element, personalized information of a user account, and/or payment account information. For example, a terminal executing the client 110 and a server 120 may form such an interface displaying system, wherein the client 110 or terminal may include the interface displaying device shown in Figs. 6, 7A, or 7B, and the server 120 may include the interface displaying device shown in Figs. 8, Fig 9A, 9B, or 9C. The client 110 and the server 120 may implement any functionality or processing steps of the interface displaying methods described above as well.

It should be noted that, the embodiment mentioned above merely describes an example for dividing the interface displaying device into several functional modules, but in the practical application, different functional modules can be distributed to perform the functions mentioned above, that is, the interior structure of the device can be divided into several functional modules to perform the partial or whole functions. In addition, the interface displaying device and the method thereof pertain to the same concept, whose process could be reviewed in the embodiments related to the method, thus is not repeated here.

The order of the above embodiments is merely used for describing, which is not to represent merits of the embodiments.

Those skilled in the art may understand that the whole or part of the steps above may be realized by hardware or by programs to instruct the hardware, the programs can be stored in a computer readable storage medium, the storage medium mentioned above can be the read-only memory, disk or CD, etc.

The methods, devices, processing, and modules described above may be implemented in many different ways and in many different combinations of hardware and software. For example, all or parts of the implementations may be circuitry that includes an instruction processor, such as a Central Processing Unit (CPU) , microcontroller, or a microprocessor； an Application Specific Integrated Circuit (ASIC) , Programmable Logic Device (PLD) , or Field Programmable Gate Array (FPGA) ； or circuitry that includes discrete logic or other circuit components, including analog circuit components, digital circuit components or both； or any combination thereof. The circuitry may include discrete interconnected hardware components and/or may be combined on a single integrated circuit die, distributed among multiple integrated circuit dies, or implemented in a Multiple Chip Module (MCM) of multiple integrated circuit dies in a common package, as examples.

The circuitry may further include or access instructions for execution by the circuitry. The instructions may be stored in a tangible storage medium that is other than a transitory signal, such as a flash memory, a Random Access Memory (RAM) , a Read Only Memory (ROM) , an Erasable Programmable Read Only Memory (EPROM) ； or on a magnetic or optical disc, such as a Compact Disc Read Only Memory (CDROM) , Hard Disk Drive (HDD) , or other magnetic or optical disk； or in or on another machine-readable medium. A product, such as a computer program product, may include a storage medium and instructions stored in or on the medium, and the instructions when executed by the circuitry in a device may cause the device to implement any of the processing described above or illustrated in the drawings.

The implementations may be distributed as circuitry among multiple system components, such as among multiple processors and memories, optionally including multiple distributed processing systems. Parameters, databases, and other data structures may be separately stored and managed, may be incorporated into a single memory or database, may be logically and physically organized in many different ways, and may be implemented in many different ways, including as data structures such as linked lists, hash tables, arrays, records, objects, or implicit storage mechanisms. Programs may be parts (e.g., subroutines) of a single program, separate programs, distributed across several memories and processors, or implemented in many different ways, such as in a library, such as a shared library (e.g., a Dynamic Link Library (DLL) ) . The DLL, for example, may store instructions that perform any of the processing described above or illustrated in the drawings, when executed by the circuitry.

Various implementations have been specifically described. However, many other implementations are also possible.

While the disclosure has been described in connection some practical embodiments, it is to be understood that the disclosure is not to be limited to the disclosed embodiments, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the disclosure.

Claims

A method comprising:

through an application client executing on a terminal device:

obtaining, from a server, a display element used for receiving high priority information of a user account；

obtaining personalized information of the user account；

displaying an application interface containing the display element and the personalized information.
The method according to claim 1, wherein obtaining the personalized information of the user account comprises:

reading the personalized information from a local cache of the device, receiving the personalized information from the server in response to an information request sent to the server, or both.
The method according to claim 2, wherein receiving the personalized information returned from the server comprises:

receiving, from the server, a permission request for using the personalized information；

sending, to the server, authorization information for the server to confirm granting permission to use the personalized information.
The method according to claim 1, further comprising, when the high priority information comprises payment information:

before displaying the application interface containing the display element and the personalized information:

obtaining, from the server, account information of a payment account associated with the user account； and

wherein the method of displaying an application interface containing the display element and the personalized information comprises:

displaying the application interface containing the display element, the personalized information and the account information of the payment account.
The method according to claim 1, wherein the personalized information includes at least one of the following:

an identification of the user account；

head portrait information of the user account；

a personalized signature of the user account；

information that the user account previously shared on a social information sharing platform；

communication information that the user account previously communicated with another user account；

account information of another user account that the user account previously communicated with；

information that the user account previously accessed；

at least one of the name, content characteristics and related information of the application that the user account previously used.
An interface displaying method, comprising:

in a server:

providing, to a client, a display element used for receiving high priority information of a user account, the display element configured to be cached by the client and displayed on an application interface of the client； or

providing, to the client, the display element used for receiving the high priority information of the user account and personalized information of the user account, wherein the display element and the personalized information are configured to be displayed on the application interface of the client at the same time.
The method according to claim 6, wherein providing the personalized information of the user account to the client comprises:

receiving a request for obtaining the personalized information from the client；

querying the personalized information of the user account； and

providing the queried personalized information to the client.
The method according to claim 7, further comprising, before querying the personalized information of the user account:

sending a permission request for using the personalized information to the client；

receiving authorization information from the client；

granting permission to the client for using the personalized information according to the authorization information； and

performing the querying the personalized information of the user account after receiving the authorization information and granting the permission.
The method according to claim 6, further comprising:

querying account information of a payment account bound associated the user account；

providing the queried account information of the payment account to the client, wherein the account information of the payment account, the display element, and the personalized information are configured to be displayed by the application interface of the client at the same time.
The method according to claim 6, wherein the personalized information includes at least one of the following information:

an identification of the user account；

head portrait information of the user account；

a personalized signature of the user account；

information that the user account previously shared on a social information sharing platform；

communication information that the user account previously communicated with another user account；

account information of another user account that the user account previously communicated with；

information that the user account previously accessed；

at least one of the name, content characteristics and related information of the application that the user account previously used.
An interface displaying device, comprising:

a first obtaining module, configured to obtain, from a server, a display element used for receiving high priority information of a user account；

a second obtaining module, configured to obtain personalized information of the user account； and

a user interface configured to display an application interface containing the display element and the personalized information.
The device according to claim11, wherein the second obtaining module further comprises:

a first obtaining unit configured to read the personalized information from a local cache； or

a second obtaining unit configured to send a request for obtaining the personalized information to the server, and receive the personalized information from the server.
The device according to claim 12, further comprising, when the device comprises the second obtaining unit:

a request receiving module, configured to receive, from the server, a permission request for using the personalized information； and

an information sending module, configured to send authorization information to the server to confirm permission for the device to use the personalized information.
The device according to claim 11, further comprising:

a third obtaining module configured to obtain, from the server, account information of a payment account associated with the user account； and

wherein the user interface is configured to display the application interface containing the display element, the personalized information, and the account information of the payment account.
The device according to claim 11, wherein the personalized information includes at least one of the following:

an identification of the user account；

head portrait information of the user account；

a personalized signature of the user account；

information that the user account previously shared on a social information sharing platform；

communication information that the user account previously communicated with another user account；

account information of another user account that the user account previously communicated with；

information that the user account previously accessed；

at least one of the name, content characteristics and related information of the application that the user account previously used.
An interface displaying device, applied to a server, comprising:

a first providing module or a second providing module, wherein:

the first providing module is configured to provide a display element to a client, the display element used for receiving high priority information of a user account, wherein the display element and personalized information of the user account are configured to be cached at the client and displayed, at the same time, on an application interface of the client； and

the second providing module configured to provide, to the client, the display element used for receiving the high priority information of the user account and, in addition to the display element, personalized information of the user account, wherein the display element and the personalized information are configured to be displayed on an application interface of the client at the same time.
The device according to claim 16, wherein the second providing module comprises:

a request receiving unit configured to receive, from the client, a request for the personalized information of the user account；

an information querying unit configured to query the personalized information of the user account； and

an information providing unit configured to provide the queried personalized information to the client.
The device according to claim 17, wherein the second providing module further comprises:

a request sending unit configured to send a permission request to the client for obtaining permission for using the personalized information；

an information receiving unit configured to receive, from the client, authorization information granting permission to use the personalized information； and

wherein the information querying unit is further configured to perform the querying of the personalized information after the information receiving unit receives the authorization information.
The device according to claim 16, further comprising:

an information querying module configured to query account information of a payment account associated with the user account； and

a third providing module configured to provide the queried account information of the payment account to the client, wherein the account information of the payment account, the display element, and the personalized information are configured to be displayed on the application interface of the client at the same time.
he device according to claim 16, wherein the personalized information includes at least one of the following:

an identification of the user account；

head portrait information of the user account；

a personalized signature of the user account；

information that the user account previously shared on a social information sharing platform；

communication information that the user account previously communicated with another user account；

account information of another user account that the user account previously communicated with；

information that the user account previously accessed；

at least one of the name, content characteristics and related information of the application that the user account previously used.