Sensitive data query method, device, equipment and storage medium

Abstract

The embodiment of the present application discloses a sensitive data query method, device, equipment and storage medium, the method comprising: responding to a trigger operation of a first user accessing an application client through first account information, taking the user of the second account information corresponding to the trigger operation as the second user to be queried; obtaining user identification information, scene type data and authentication information corresponding to the second user, taking the user identification information, scene type data and authentication information as business key information for querying the sensitive data of the second user, sending a first data query request to a server corresponding to the application client based on the business key information; when the server determines that the first data query request is legitimate, obtaining the sensitive data of the second user returned by the server; outputting the sensitive data of the second user to the user information display interface of the application client. The use of the embodiment of the present application can improve the security of user sensitive data.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a sensitive data query method, device, equipment and storage medium. Background Art

[0002] User information refers to various information that can identify a specific natural person alone or in combination with other information, or reflect the activities of a specific natural person. The user information may include sensitive data and basic data. Among them, the basic data may include user nicknames, gender, zodiac signs and other data, and the sensitive data may include telephone numbers, email addresses, addresses and other data. When a user (for example, user B) queries the user information of a certain user (for example, user A) through a user terminal running an application client, the application client can obtain the user identification information of user A in an infinitely exhaustive manner, and then illegally view the user information of others in this user terminal. For example, the sensitive data of user A can be obtained, so that there is a risk of illegal leakage of sensitive data, which reduces the security of user information data. Summary of the invention

[0003] The embodiments of the present application provide a sensitive data query method, apparatus, device and storage medium, which can effectively improve the security of user sensitive data.

[0004] An embodiment of the present application provides a sensitive data query method, which is executed by a user terminal and includes:

[0005] In response to a trigger operation of a first user accessing the application client through the first account information, a user of the second account information corresponding to the trigger operation is used as a second user to be queried; the first user and the second user are both users after sensitive data isolation is performed in the application client;

[0006] Obtaining user identification information, scenario type data, and authentication information corresponding to the second user, using the user identification information, scenario type data, and authentication information as business-critical information for querying sensitive data of the second user, and sending a first data query request to a server corresponding to the application client based on the business-critical information; the business-critical information is used to instruct the server to determine the legitimacy of the first data query request;

[0007] When the server determines that the first data query request is legitimate, obtaining the sensitive data of the second user returned by the server;

[0008] The sensitive data of the second user is output to the user information display interface of the application client.

[0009] An embodiment of the present application provides a sensitive data query method, which is executed by a server and includes:

[0010] receiving a first data query request sent by a user terminal running an application client based on business key information; the business key information includes user identification information, scenario type data, and authentication information corresponding to a second user; the second user is a user to be queried determined after a trigger operation is performed by a first user who accesses the application client through the first account information; the first user and the second user are both users after sensitive data isolation is performed in the application client;

[0011] Determining the legitimacy of the first data query request based on the business key information;

[0012] When determining that the first data query request is legitimate, obtaining sensitive data of the second user;

[0013] The sensitive data of the second user is returned to the user terminal, so that the user terminal outputs the sensitive data of the second user to the user information display interface of the application client.

[0014] An embodiment of the present application provides a sensitive data query device, which runs on a user terminal and includes:

[0015] A module for determining users to be queried is used to respond to a trigger operation of a first user accessing the application client through the first account information, and to use the user of the second account information corresponding to the trigger operation as the second user to be queried; the first user and the second user are both users after sensitive data isolation is performed in the application client;

[0016] a first request sending module, configured to obtain user identification information, scenario type data, and authentication information corresponding to the second user, use the user identification information, scenario type data, and authentication information as business key information for querying sensitive data of the second user, and send a first data query request to a server corresponding to the application client based on the business key information; the business key information is used to instruct the server to determine the legitimacy of the first data query request;

[0017] A sensitive data acquisition module, used to acquire the sensitive data of the second user returned by the server when the server determines that the first data query request is legitimate;

[0018] The sensitive data output module is used to output the sensitive data of the second user to the user information display interface of the application client.

[0019] The first user and the second user are users in the conversation interface of the application client;

[0020] The first request sending module includes:

[0021] A session attribute determination unit, used to determine the session attribute of the session interface in the application client;

[0022] A first determining unit, configured to determine, in the conversation interface, user identification information mapped to a second user corresponding to the second account information, and to determine, according to the conversation attribute, scene type data corresponding to the second user;

[0023] A second determining unit, configured to determine authentication information corresponding to the second user in the session interface;

[0024] The first request sending unit is used to use user identification information, scenario type data and authentication information as business key information, generate a first data query request for querying sensitive data of the second user based on the business key information, and send the first data query request to a server corresponding to the application client.

[0025] Wherein, the session attribute includes a first session attribute;

[0026] The second determining unit includes:

[0027] The first determining subunit is used to determine, based on the first session attribute, session identification information associated with the first user and the second user in the session interface, and use the session identification information as authentication information corresponding to the second user.

[0028] The session attribute includes a second session attribute, and the first user and the second user are both users in a public broadcast group of the application client;

[0029] The second determining unit also includes:

[0030] A second determining subunit is used to use the enterprise identification information corresponding to the first user as the first enterprise identification information, and use the enterprise identification information corresponding to the second user as the second enterprise identification information;

[0031] A third determination subunit is configured to use, if the first enterprise identification information and the second enterprise identification information are enterprise identification information of the same enterprise corresponding to the public broadcast group, the group identification information corresponding to the public broadcast group as the first session identification information corresponding to the session interface, and the first session identification information as the authentication information corresponding to the second user;

[0032] The fourth determination sub-unit is used to use the group identification information corresponding to the public broadcast group as the second session identification information corresponding to the session interface, and use the first enterprise identification information and the second session identification information as authentication information corresponding to the second user if the first enterprise identification information and the second enterprise identification information are enterprise identification information of different enterprises corresponding to the public broadcast group.

[0033] The second user is a user in the contact list of the application client;

[0034] The first request sending module also includes:

[0035] A list attribute determination unit, used to determine the list attributes of the contact list in the list display interface of the application client;

[0036] A third determining unit, configured to determine, in the list attributes, the user identification information mapped to the second user corresponding to the second account information, and determine the scene type data corresponding to the second user according to the list attributes;

[0037] A fourth determining unit, configured to use the enterprise identification information corresponding to the first user as the authentication information corresponding to the second user in the contact list;

[0038] The second request sending unit is used to use the user identification information, scenario type data and authentication information as business key information, generate a first data query request for querying sensitive data of the second user based on the business key information, and send the first data query request to the server corresponding to the application client.

[0039] The device further comprises:

[0040] A display interface output module, configured to respond to a trigger operation of the first user on the public broadcast platform associated with the application client, and output an information display interface of the public broadcast platform; the information display interface includes business data information published by the enterprise object corresponding to the public broadcast platform and an interactive editing control for interacting with the business data information;

[0041] The information entry module is used to respond to the trigger operation for the interactive editing control, output a text entry sub-interface independent of the information display interface, and enter text interactive information for business data information on the text entry sub-interface; the text entry sub-interface is an interface superimposed on the information display interface, and the size of the text entry sub-interface is smaller than the size of the information display interface; the text entry sub-interface includes an interactive publishing control;

[0042] A second request sending module, configured to respond to a trigger operation on the interactive publishing control and send a second data query request for obtaining sensitive data of the first user to a server corresponding to the application client;

[0043] The interactive information determination module is used to use the text interactive information and the sensitive data of the first user as interactive information of the business data information when receiving the sensitive data of the first user returned by the server.

[0044] Among them, the scene corresponding to the information display interface of the public broadcasting platform is the interface jump scene;

[0045] The second request sending module includes:

[0046] An authorization unit, configured to respond to a trigger operation on an interactive publishing control, take the first user as a user to be queried, and authorize the public broadcasting platform to obtain user identification information of the first user in the application client based on an interface jump scenario;

[0047] A fifth determining unit, configured to determine the scenario type data corresponding to the first user based on the interface attribute of the interface jump scenario;

[0048] A sixth determining unit, configured to obtain platform identification information corresponding to the public broadcasting platform and text identification information of the text interaction information, and use the platform identification information and the text identification information as authentication information corresponding to the first user;

[0049] A key information determination module, configured to use the user identification information of the first user, the scene type data corresponding to the first user, and the authentication information corresponding to the first user as the business key information of the first user;

[0050] The third request sending unit is used to generate a second data query request for querying the sensitive data of the first user based on the business-critical information of the first user, and send the second data query request to the server corresponding to the application client.

[0051] On one hand, the present application provides a computer device, including: a processor, a memory, and a network interface;

[0052] The processor is connected to a memory and a network interface, wherein the network interface is used to provide a data communication function, the memory is used to store a computer program, and the processor is used to call the computer program to execute the method in the above aspect of the embodiment of the present application.

[0053] In one aspect, the present application provides a computer-readable storage medium storing a computer program. The computer program includes program instructions. When the program instructions are executed by a processor, the method in the above aspect of the embodiment of the present application is executed.

[0054] In one aspect, the present application provides a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method in the above aspect.

[0055] An embodiment of the present application provides a sensitive data query device, which runs on a server and includes:

[0056] A query request receiving module, used to receive a first data query request sent by a user terminal running an application client based on business key information; the business key information includes user identification information, scenario type data and authentication information corresponding to a second user; the second user is a user to be queried determined after a trigger operation is performed by a first user who accesses the application client through the first account information; the first user and the second user are both users after sensitive data isolation is performed in the application client;

[0057] A legitimacy determination module, used to determine the legitimacy of the first data query request based on the business key information;

[0058] A data acquisition module, configured to acquire sensitive data of a second user when determining that the first data query request is legitimate;

[0059] The data return module is used to return the sensitive data of the second user to the user terminal, so that the user terminal outputs the sensitive data of the second user to the user information display interface of the application client.

[0060] Among them, the legality determination module includes:

[0061] A first legitimacy determination unit, configured to determine that the first data query request is legitimate if the scenario type data in the business key information satisfies the scenario query condition;

[0062] The second legitimacy determination unit is used to determine that the first data query request is illegal if the scenario type data in the business-critical information does not meet the scenario query condition.

[0063] On one hand, the present application provides a computer device, including: a processor, a memory, and a network interface;

[0064] The processor is connected to a memory and a network interface, wherein the network interface is used to provide a data communication function, the memory is used to store a computer program, and the processor is used to call the computer program to execute the method in the above aspect of the embodiment of the present application.

[0065] In one aspect, the present application provides a computer-readable storage medium storing a computer program. The computer program includes program instructions. When the program instructions are executed by a processor, the method in the above aspect of the embodiment of the present application is executed.

[0066] In one aspect, the present application provides a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method in the above aspect.

[0067] In an embodiment of the present application, a computer device (i.e., a user terminal) running an application client can respond to a trigger operation of a first user accessing the application client through the first account information, and then the user of the second account information corresponding to the trigger operation can be used as the second user to be queried. Among them, the first user and the second user are both users after sensitive data isolation in the application client. The first user here can be a viewing user, and the second user can be a user to be queried. Since the first user and the second user are users after sensitive data isolation, in the process of querying the sensitive data of the second user in the application client in the embodiment of the present application, it is necessary to judge the legitimacy of the first data query request sent by the user terminal through the server to ensure the security of the sensitive data of the second user in the application client. For example, in the process of querying the sensitive data of the second user through the user terminal, the first user not only needs to obtain the user identification information corresponding to the second user, but also needs to obtain the scene type data and authentication information of the second user. The scene type data here can be used to indicate the scene type of the second user in the application client. For example, the scene type indicated by the scene type data "1" can be a group chat scene. Furthermore, the user terminal can send a first data query request to the server corresponding to the application client based on business-critical information (e.g., user identification information, scenario type data, and authentication information). In this way, when the server determines that the first data query request is legitimate, it can return the sensitive data of the second user to the user terminal. At this time, the user terminal can further output the sensitive data of the second user to the user information display interface of the application client. It should be understood that, on the contrary, when the server determines that the first data query request is not legitimate, it is not necessary to return the sensitive data of the second user to the user terminal, thereby effectively ensuring the security of the user's sensitive data. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0069] Figure 1 It is a structural diagram of a network architecture provided by an embodiment of the present application;

[0070] Figure 2 This is a schematic diagram of a scenario for data interaction provided by an embodiment of the present application;

[0071] Figure 3It is a flowchart of a sensitive data query method provided in an embodiment of the present application;

[0072] Figure 4 is a pseudo code schematic diagram of defining scene type data provided in an embodiment of the present application;

[0073] Figure 5a This is a schematic diagram of a scenario of querying sensitive data of a second user in a conversation interface in a single chat scenario provided by an embodiment of the present application;

[0074] Figure 5b This is a schematic diagram of a scenario of querying sensitive data of a second user in a public broadcast group provided by an embodiment of the present application;

[0075] Figure 6 This is a schematic diagram of a scenario of querying sensitive data of a second user in a contact list provided by an embodiment of the present application;

[0076] Figure 7 It is a flowchart of a sensitive data query method provided in an embodiment of the present application;

[0077] Figure 8 This is a schematic diagram of a scenario for obtaining sensitive data of a first user provided in an embodiment of the present application;

[0078] Fig. 9 It is a structural schematic diagram of a sensitive data query device provided in an embodiment of the present application;

[0079] Fig.10 is a schematic diagram of a computer device provided in an embodiment of the present application;

[0080] Fig.11 It is a structural schematic diagram of a sensitive data query device provided in an embodiment of the present application;

[0081] Fig.12 is a schematic diagram of a computer device provided in an embodiment of the present application;

[0082] Fig.13 It is a structural diagram of a data processing system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0083] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0084] See also Figure 1 , Figure 1 Schematic diagram of a network architecture provided by an embodiment of the present application. Figure 1 As shown, the network architecture may include a server 10 and a user terminal cluster. The user terminal cluster may include one or more user terminals, and the number of user terminals is not limited here. Figure 1 As shown, it may specifically include user terminal 100a, user terminal 100b, user terminal 100c, ..., user terminal 100n. Figure 1 As shown, the user terminal 100a, the user terminal 100b, the user terminal 100c, ..., the user terminal 100n can respectively establish a network connection with the server 10, so that each user terminal can exchange data with the server 10 through the network connection.

[0085] Each user terminal in the user terminal cluster may include: a smart phone, a tablet computer, a laptop computer, a desktop computer, a wearable device, a smart home, a head-mounted device, and other smart terminals with business data processing functions. Figure 1 Each user terminal in the user terminal cluster shown in FIG. 1 may be installed with the application client. When the application client is running in each user terminal, it may be respectively connected to the above-mentioned Figure 1 Data is exchanged between the servers 10 shown. The application client may be an independent client or an embedded public broadcasting platform integrated in a client (eg, a social client, an educational client, a multimedia client, etc.), which is not limited here.

[0086] like Figure 1 As shown, the server 10 in the embodiment of the present application can be the server corresponding to the application client. The server 10 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

[0087] For ease of understanding, the embodiments of the present application may be Figure 1 Select one user terminal from the multiple user terminals shown as the target user terminal. For example, the embodiment of the present application can Figure 1 The user terminal 100a shown is used as a target user terminal, and the target user terminal may be integrated with a target application (ie, application client) having the business data processing function. At this time, the target user terminal may implement data interaction with the server 10 through the business data platform corresponding to the application client.

[0088] It should be understood that the user information in the embodiments of the present application may include sensitive data and basic data, wherein the sensitive data may include data such as email, phone, address, landline, department, corporate email, etc. The basic data may include data such as user account information, user nickname, name, gender, zodiac sign, age, and avatar.

[0089] For further understanding, please refer to Figure 2 , Figure 2 Schematic diagram of a scenario for data interaction provided by an embodiment of the present application. Figure 2 As shown, the user terminal 30 in the embodiment of the present application may be a terminal running an application client, and the user terminal 30 may be the above-mentioned Figure 1 Any user terminal in the user terminal cluster shown, for example, user terminal 100a. The server 20 in the embodiment of the present application may be a server corresponding to the application client, and the server 20 may be the above-mentioned Figure 1 The server shown.

[0090] It should be understood that the user corresponding to the user terminal 30 (for example, user A) can access the application client (for example, a social client) through the first account information. In the embodiment of the present application, the user who accesses the application client through the first account information may be referred to as the first user, and the first user may also be referred to as the viewing user. It is understandable that when the first user queries the sensitive data of a certain user in the application client, a trigger operation can be performed in the application client for the user to be queried. Among them, the trigger operation may include contact operations such as clicking and long pressing, and may also include non-contact operations such as voice and gestures, which are not limited here.

[0091] At this time, the user terminal 30 can respond to the trigger operation of the user A and use the user of the second account information corresponding to the trigger operation (for example, user B) as the second user to be queried. Among them, both user A and user B can be users after sensitive data isolation is performed in the application client. Further, the user terminal 30 can obtain the user identification information, scene type data and authentication information corresponding to user B, and then use the obtained user identification information, scene type data and authentication information as business-critical information. It should be understood that the user terminal 30 can generate a first data query request for querying the sensitive data of user B based on the business-critical information, and then send the first data query request to the server 20 corresponding to the application client. Among them, the business-critical information can be used to instruct the server 20 to determine the legitimacy of the first data query request.

[0092] It is understandable that when the server 20 obtains the first data query request, it can determine the legitimacy of the first data query request based on the business-critical information. If the scene type data in the business-critical information does not meet the scene query condition, the server 20 can determine that the first data query request is illegal. At this time, the server 20 can determine that the first data query request is an illegal request, and then the user information of user B can be not returned. If the scene type data in the business-critical information meets the scene query condition, the server 20 can determine that the first data query request is legal. At this time, the server 20 can determine that the first data query request is a legal request, and then the business-critical information can be authenticated. Among them, the scene query condition can be that the business-critical information contains scene type data.

[0093] It should be understood that if the server 20 successfully authenticates the scenario type of user B based on the business-critical information, the server 20 can obtain the sensitive data of user B, and then return the sensitive data of user B to the user terminal 30, so that the user terminal 30 can output the sensitive data of user B and the basic user information of user B to the user information display interface of the application client.

[0094] If the server 20 finds it difficult to authenticate the scenario type of user B based on the business-critical information, the server 20 can obtain the basic user information of user B and return it to the user terminal 30, so that the user terminal 30 can output the basic user information of user B to the user information display interface of the application client.

[0095] If the server 20 determines, based on the business-critical information, that the authentication information of user B does not match the scene type corresponding to the scene type data, the server 20 may determine that the data source is inconsistent and that there is a suspected risk, and may then generate an abnormal prompt notification and return the abnormal prompt notification to the user terminal 30 .

[0096] It can be seen that when the server 20 in the embodiment of the present application obtains a legitimate first data query request, it can then obtain the sensitive data of the user to be queried (for example, user B) based on the legitimate first data query request, thereby effectively ensuring that the user's sensitive data is not maliciously obtained by others, thereby improving the security of the user's sensitive data.

[0097] Among them, the computer device (for example, the user terminal) running the application client can determine the business key information of the second user (i.e., the user to be queried), and generate a first data query request for querying the sensitive data of the second user based on the business key information, and then send the first data query request to the server corresponding to the application client, so that when the server determines that the first data query request is legitimate, the sensitive data of the second user can be obtained. The specific implementation method can be referred to as follows Figure 3-Figure 8 The corresponding embodiment.

[0098] For further information, see Figure 3 , Figure 3 Schematic diagram of a sensitive data query method provided by an embodiment of the present application. Figure 3 As shown, the method can be executed by a computer device running an application client, the computer device can be a user terminal, and the user terminal can be the above Figure 1 Any user terminal in the user terminal cluster shown, for example, user terminal 100a. The method may at least include the following steps S101-S104:

[0099] Step S101, in response to a triggering operation of a first user accessing an application client through first account information, a user of second account information corresponding to the triggering operation is used as a second user to be queried.

[0100] Specifically, the first user corresponding to the user terminal (for example, user A) can access the application client (for example, social client) run by the user terminal through the first account information (for example, account information 1). It should be understood that when the first user queries the sensitive data of a certain user in the application client, he can perform a trigger operation on the application client for the user to be queried. Among them, the trigger operation may include contact operations such as clicks and long presses, and may also include non-contact operations such as voice and gestures, which are not limited here. At this time, the application client can respond to the trigger operation and use the user of the second account information corresponding to the trigger operation (for example, account information 2) as the second user to be queried (for example, user B). Among them, both the first user and the second user can be users after sensitive data isolation in the application client.

[0101] Step S102, obtain user identification information, scenario type data and authentication information corresponding to the second user, use the user identification information, scenario type data and authentication information as business-critical information for querying sensitive data of the second user, and send a first data query request to the server corresponding to the application client based on the business-critical information.

[0102] Specifically, the user terminal can obtain the user identification information, scene type data and authentication information corresponding to the second user, and then use the obtained user identification information, scene type data and authentication information as business key information. Further, the user terminal can generate a first data query request for querying the sensitive data of the second user based on the business key information, and then send the first data query request to the server corresponding to the application client. The business key information can be used to instruct the server to determine the legitimacy of the first data query request.

[0103] Among them, the user identification information (VID) here can be the unique identity information (for example, a string) configured by the server for the user in the application client when the user registers the account information. The scene type data can be a numerical value used to indicate the scene type (UserInfoScenceType) of the user to be queried. For example, the scene type can include single chat scenes, group chat scenes, and organizational structure (i.e., address book) scenes, etc. The authentication information (check_info) can be the data information that needs to be submitted to the server for scene authentication when querying the second user. For example, when the scene type of the second user is a public broadcast group (i.e., a group chat scene), the authentication information can be the group identification information corresponding to the public broadcast group.

[0104] For further understanding, please refer to Figure 4 , Figure 4 This is a pseudo code diagram of a method for defining scene type data provided by an embodiment of the present application. Figure 4 As shown, the scene types to which the first user (i.e., the viewing user) and the second user (i.e., the user to be queried) belong in the embodiment of the present application may include multiple, wherein one scene type may correspond to one scene type data. The embodiment of the present application may take 10 as an example, specifically including scene type 1, scene type 2, scene type 3, scene type 4, scene type 5, scene type 6, scene type 7, scene type 8, scene type 9, scene type 10, and scene type 11.

[0105] like Figure 4As shown, the scenario type 1 indicated by the scenario type data "0" can be an unknown illegal scenario, for example, a scenario in which hackers illegally obtain other users' information; the scenario type 2 indicated by the scenario type data "1" can be a scenario type in a public broadcast group, that is, a group chat scenario, for example, the first user and the second user can be users under the same public broadcast group (for example, an administrative department group); the scenario type 3 indicated by the scenario type data "2" can be a friend recommendation scenario, for example, the second user can be a user recommended by a business card or a corporate card; the scenario type 4 indicated by the scenario type data "3" can be an external contact friend scenario, for example, the first user is a user of enterprise A, and the second user can be a user in the user list of an external enterprise (for example, enterprise B) in the organizational structure (for example, address book) of the application client; the scenario type 5 indicated by the scenario type data "4" can be a same-enterprise scenario, that is, the first user and the second user are both from the same enterprise ( For example, a user of Enterprise C); the scenario type 6 indicated by the scenario type data "5" can be an external client contact scenario, for example, the first user can be an application client (for example, an enterprise WeChat client), and the second user can be a user in another application client (for example, a WeChat client); the scenario type 7 indicated by the scenario type data "6" can be a single chat scenario, for example, a scenario in which the first user establishes a conversation relationship with the second user; the scenario type 8 indicated by the scenario type data "7" can be a forwarded message scenario, for example, the second user can be a user in a chat record forwarded by other users; the scenario type 9 indicated by the scenario type data "8" can be a favorite message scenario, for example, the second user can be a user in a chat record favorited by the first user; the scenario type 10 indicated by the scenario type data "9" can be a public account scenario, for example, the second user can be a user who comments on the text information of the public account under the public account. The scenario type 11 indicated by the scenario type data "10" can be a self-scenario. For example, the user corresponding to the user terminal (for example, the first user) can perform a trigger operation on the personal business card of the first user in the personal display interface of the application client, so as to query the sensitive data of the first user, so that the first user can modify or edit the sensitive data and basic data of the first user in the user information display interface corresponding to the first user.

[0106] In addition, the scenario types in the embodiments of the present application may also include interface jump scenarios (for example, JSApi scenarios), daily report scenarios, resignation recommendation scenarios, etc. Among them, the JSApi scenario refers to the H5 (an application client on an interactive web page) or applet interface opened by the application client, and third-party developers can use this interface to obtain data in the application client, or evoke native interactions, etc.

[0107] It is understandable that the authentication type of the scenario type in the embodiment of the present application can be divided into a first authentication type and a second authentication type. Among them, the first authentication type refers to a scenario type that can be authenticated, and the second authentication type refers to a scenario type that is difficult to authenticate. It is understandable that the first authentication type may include group chat scenarios, external contact friend scenarios, same enterprise scenarios, external client contact scenarios, single chat scenarios, and public account scenarios. The second authentication type may include forwarding message scenarios, favorite message scenarios, interface jump scenarios, daily report scenarios, resignation recommendation scenarios, and friend recommendation scenarios.

[0108] It should be understood that the first user and the second user may be users in the session interface in the application client. At this time, the user terminal may determine the session attribute of the session interface in the application client. Further, the user terminal may determine the user identification information mapped to the second user corresponding to the second account information (for example, the user identification information b mapped to user B) in the session interface, and then determine the scene type data corresponding to the second user according to the session attribute.

[0109] The session attribute of the session interface may include a first session attribute and a second session attribute. The first session attribute may be a session attribute corresponding to a single chat scenario in the application client. For example, the scenario type data corresponding to the single chat scenario may be Figure 4 The scene type data "6" shown. The second session attribute may be a session attribute corresponding to a public broadcast group (eg, a group chat scene) of the application client. For example, the scene type data corresponding to the group chat scene may be Figure 4 The scene type data shown is "1".

[0110] Furthermore, the user terminal can determine the authentication information corresponding to the second user in the session interface. It is understandable that if the user terminal determines that the session attribute of the session interface (e.g., session interface 1) corresponding to the first user and the second user belongs to the first session attribute, the user terminal can determine the session identification information associated with the first user and the second user in the session interface based on the first session attribute (e.g., the session identification information 1), and then use the session identification information 1 as the authentication information corresponding to the second user. The session identification information 1 here can be the unique identification information (e.g., a string) configured by the server for the session attribute when the user A and the user B establish a session relationship.

[0111] Optionally, if the user terminal determines that the first user and the second user are both users in the public broadcast group of the application client, the user terminal can determine that the session attribute of the session interface (for example, session interface 2) corresponding to the announcement broadcast group belongs to the second session attribute. At this time, the user terminal can use the corporate identification information (CorpID) corresponding to the first user as the first corporate identification information, and the corporate identification information corresponding to the second user as the second corporate identification information.

[0112] It can be understood that if the first enterprise identification information and the second enterprise identification information are enterprise identification information of the same enterprise corresponding to the public broadcast group, the user terminal can use the group identification information corresponding to the public broadcast group as the first session identification information corresponding to the session interface, and then can use the first session identification information as the authentication information corresponding to the second user.

[0113] If the first enterprise identification information and the second enterprise identification information are enterprise identification information of different enterprises corresponding to the public broadcast group, the user terminal can use the group identification information corresponding to the public broadcast group as the second session identification information corresponding to the session interface. Further, the user terminal can use the first enterprise identification information and the second session identification information as authentication information corresponding to the second user.

[0114] Optionally, the second user may be a user in the contact list of the application client. In this case, the user terminal may determine the list attributes of the contact list in the list display interface of the application client. Further, the user terminal may determine the user identification information mapped to the second user corresponding to the second account information in the list attributes, and then determine the scene type data corresponding to the second user according to the list attributes. It should be understood that the user terminal may use the enterprise identification information corresponding to the first user as the authentication information corresponding to the second user in the contact list.

[0115] Optionally, the second user may be a user in a contact list in another application client (e.g., a WeChat client). In this case, the user terminal may determine the list attributes of the contact list in the list display interface of the application client. Further, the user terminal may determine the user identification information mapped to the second user corresponding to the second account information in the list attributes, and then determine the scene type data corresponding to the second user according to the list attributes (e.g., Figure 4 The scenario type data "5" shown in the figure). It should be understood that the user terminal can determine that the authentication information corresponding to the second user is empty. In other words, since the first user and the second user belong to users in different clients, the first user cannot obtain the sensitive data of the second user across applications.

[0116] Optionally, the second user may also be a user in the message forwarding or message collection scenario. It is understandable that when the first user forwards or collects a chat record associated with the second user, the user terminal may need the user information of the second user. At this time, the user terminal may determine the user identification information mapped to the second user corresponding to the second account information based on the chat record, and then determine the scenario type data corresponding to the second user based on the chat record (for example, Figure 4 The scenario type data shown is "7" or "8"). It should be understood that the user terminal can determine that the authentication information corresponding to the second user is the message identification information.

[0117] It should be understood that after the user terminal determines the user identification information, scenario type data, and authentication information of the second user, the user identification information, the scenario type data, and the authentication information can be used as business key information, and a first data query request for querying the sensitive data of the second user can be generated based on the business key information. At this time, the user terminal can send the first data query request to the server corresponding to the application client.

[0118] Step S103: when the server determines that the first data query request is legitimate, the sensitive data of the second user returned by the server is obtained.

[0119] It should be understood that the server can receive the first data query request sent by the user terminal based on the business-critical information, and can then determine the legitimacy of the first data query request based on the business-critical information. When determining that the first data query request is legitimate, the server can obtain the sensitive data of the second user and return the sensitive data of the second user to the user terminal.

[0120] It is understandable that when the user terminal receives the first data query request, it can determine the legitimacy of the first data query request based on the business-critical information. If the scene type data in the business-critical information does not meet the scene query conditions, the server can determine that the first data query request is illegal. At this time, the server can determine that the first data query request is an illegal request, and then may not return the user information of the second user or return an abnormal prompt notification. If the scene type data in the business-critical information meets the scene query conditions, the server can determine that the first data query request is legal. At this time, the server can determine that the first data query request is a legal request, and then can authenticate the business-critical information. Among them, the scene query condition can be that the business-critical information contains scene type data.

[0121] It should be understood that the server can determine the scenario type of the second user based on the scenario type data of the second user, and then determine the authentication type of the scenario type based on the scenario type of the second user. Among them, the authentication type of the scenario type can be divided into a first authentication type and a second authentication type. Among them, the first authentication type refers to a scenario type that can be authenticated, and the second authentication type refers to a scenario type that is difficult to authenticate. It can be understood that the first authentication type may include group chat scenarios, external contact friend scenarios, same enterprise scenarios, external client contact scenarios, single chat scenarios, and public account scenarios. The second authentication type may include forwarding message scenarios, favorite message scenarios, interface jump scenarios, daily report scenarios, resignation recommendation scenarios, and friend recommendation scenarios.

[0122] When the server determines that the scene type belongs to the second authentication type, since the relationship chain under the scene type corresponding to the second authentication type is too long and cannot be tracked, the server does not need to pay attention to the authentication information, and can directly obtain the basic data of the second user (for example, avatar, gender, constellation, age and other data), and return the basic data to the user terminal. It is understandable that the server can determine the dimension of the scene type based on the authentication information. It should be understood that if the authentication information is enterprise identification information, the server can determine whether to return the sensitive data of the second user based on the enterprise dimension, so as to effectively ensure that the sensitive data of the second user will not be accidentally leaked in foreign companies. If the authentication information is session identification information, the server can determine whether to return the sensitive data of the second user based on the session dimension, so as to ensure that the sensitive data of the second user can be viewed by the user in the session corresponding to the session identification information. It can be seen that in the embodiment of the present application, the scene type can be classified by different dimensions to ensure that the sensitive data of the user in the application client is securely isolated.

[0123] When the server determines that the scene type belongs to the first authentication type, the server needs to determine the matching of the authentication information in the business-critical information and the scene type. If the authentication information does not match the scene type, the server can determine that the data source is inconsistent and the user's sensitive data cannot be sent down. At this time, the server can generate an exception prompt notification and return the exception prompt notification to the user terminal to remind the user terminal that the query method is wrong. If the authentication information matches the scene type, the server can query the user identification information of the second user in the scene type corresponding to the authentication information, and when the user identification information is queried, the second user's sensitive data and basic data can be obtained, and then the second user's sensitive data and basic data can be returned to the user terminal.

[0124] For example, the server may obtain a first data query request for querying sensitive data of user B (i.e., the second user) sent by a user terminal corresponding to user A (i.e., the first user). Among them, the business-critical information in the first data query request may include user identification information b, scene type data "1", and group identification information x. At this time, since the scene type data in the business-critical information meets the scene query condition, the server may determine that the first data query request is legitimate. At this time, the server may determine that the scene type of user B belongs to a group chat scene based on the scene type data "1", and further determine that the group chat scene belongs to a scene type that can be authenticated (i.e., the first authentication type). Further, the server may determine the matching of the group chat scene and the authentication information. Since the authentication information is the group identification information x, the server may determine that the scene type matches the authentication information. At this time, the server may query the user identification information b of user B in the group corresponding to the group identification information x based on the group identification information x. When the user identification information b is queried, the server may obtain the sensitive data and basic data of user b, and return the sensitive data and basic data of user b to the user terminal.

[0125] For example, the server may obtain a first data query request for querying sensitive data of user D (i.e., the second user) sent by a user terminal corresponding to user C (i.e., the first user). Among them, the business-critical information in the first data query request may include user identification information d, scene type data "6", and group identification information y. At this time, since the scene type data in the business-critical information meets the scene query condition, the server can determine that the first data query request is legitimate. At this time, the server can determine that the scene type of user D belongs to a single chat scene based on the scene type data "6", and then determine that the single chat scene belongs to a scene type that can be authenticated (i.e., the first authentication type). Further, the server can determine the matching of the single chat scene and the authentication information. Since the authentication information is the group identification information y, the server can determine that the scene type does not match the authentication information. At this time, the server can determine that the data source is inconsistent and there is a suspected security risk, and then return an abnormal prompt notification to the user terminal or do not return information.

[0126] For example, the server may obtain a first data query request for querying sensitive data of user F (i.e., the second user) sent by a user terminal corresponding to user E (i.e., the first user). Among them, the business-critical information in the first data query request may include user identification information f, scenario type data "7", and message identification information z. At this time, since the scenario type data in the business-critical information meets the scenario query condition, the server may determine that the first data query request is legitimate. At this time, the server may determine that the scenario type of user F belongs to a forwarding message scenario based on the scenario type data "7". Since the message is always forwarded under this scenario type, resulting in a too long relationship chain, it may be determined that the forwarding message scenario belongs to a scenario type that is difficult to authenticate (i.e., the second authentication type). Furthermore, the server will no longer return sensitive data of user F, but will obtain basic data of user F based on user F's user identification information f, and may then return basic data of user F to the user terminal.

[0127] Step S104: output the sensitive data of the second user to the user information display interface of the application client.

[0128] Specifically, the user terminal may output the sensitive data of the second user returned by the server to the user information display interface of the application client. The user information display interface may display the sensitive data and basic data of the second user. The sensitive data may include telephone number, email address, home address, landline number, etc., and the basic data may include avatar, gender, nickname, etc.

[0129] For further understanding, please refer to Figure 5a , Figure 5a Schematic diagram of a scenario in which sensitive data of a second user is queried in a conversation interface in a single chat scenario provided by an embodiment of the present application. Figure 5a As shown, the user terminal running the application client in the embodiment of the present application can be the above Figure 1 Any user terminal in the user terminal cluster shown, for example, user terminal 100a. The server corresponding to the application client can be Figure 5a The server 50a shown in the figure may be the server 50a described above. Figure 1 The server 10 is shown.

[0130] like Figure 5a As shown, the user corresponding to the user terminal in the embodiment of the present application may be user A (ie, the first user) who accesses the user terminal through account information 1 (the first account information), and the session interface of the user terminal (eg, Figure 5aThe session interface 500a shown may include business information of user A and user B during interactive communication. The business information may include pictures, videos, voices, texts, etc. The session attribute corresponding to the session interface 500a may be a session attribute corresponding to a single chat scenario (i.e., a first session attribute). Among them, user B may be the user (i.e., the second user) corresponding to the account information 2 (i.e., the second account information) that user A needs to query.

[0131] It is understandable that user A can perform a trigger operation on user B in the conversation interface 500, so that the user terminal can respond to the trigger operation and generate a data query request 5a for querying sensitive data of user B. It is understandable that the user terminal can determine in the application client that the conversation attribute of the conversation interface 500a is the first conversation attribute (i.e., the conversation attribute corresponding to the single chat scene). Further, the user terminal can obtain the user identification information b of user B, and according to the first conversation attribute, it can determine that the scene type data of user B is Figure 4 The scene type data shown is "6".

[0132] Further, the user terminal can determine the authentication information corresponding to user B in the session interface 500a. It is understandable that the user terminal can determine the session identification information (for example, the session identification information 1) associated with user A and user B in the session interface 500a based on the first session attribute, and then use the session identification information 1 as the authentication information corresponding to user B. The session identification information 1 here can be the unique identification information (for example, a string) configured by the server for the session attribute when the user A and the user B establish a session relationship.

[0133] At this time, the user terminal can use the user identification information b, the scene type data "6" and the session identification information 1 as business key information, and then generate a data query request 5a (i.e., a first data query request) for querying user B based on the business key information. The user terminal can send the data query request 5a to the server 50a, so that the server 50a can obtain the sensitive data of user B when determining that the data query request 5a is legitimate, and then send the sensitive data of user B to the user terminal. At this time, the user terminal can output the sensitive data of user B to Figure 5a In the user information display interface 510a of the application client shown in the figure, the sensitive data of the user B may be the data such as the mobile phone, landline, email address and address shown in the user information display interface 510a.

[0134] For further understanding, please refer to Figure 5b , Figure 5bSchematic diagram of a scenario of querying sensitive data of a second user in a public broadcast group provided by an embodiment of the present application. Figure 5b As shown, the user terminal in the embodiment of the present application may run an application client, and the user terminal may be the above Figure 1 Any user terminal in the user terminal cluster shown, for example, user terminal 100a. The server corresponding to the application client can be Figure 5b The server 50b shown in the figure may be the server 50b described above. Figure 1 The server 10 is shown.

[0135] like Figure 5b As shown, the user corresponding to the user terminal can be user A (i.e., the first user) accessing the application client through account information 1 (i.e., the first account information). The session interface of the application client in the user terminal (e.g., Figure 5b The session interface 500b) shown may be a session interface corresponding to a public broadcast group (e.g., group 1) of the application client. Group 1 may include multiple users. The session interface 500b may include business information of each user in group 1 during interactive communication, and the business information may include pictures, videos, voice, text, etc. Figure 5b As shown, the conversation interface 500b in the embodiment of the present application may include business information of user A, user B who accesses the application client through account information 2 (i.e., the second account information), and user C who accesses the application client through account information 3. Among them, user B may be the user that user A needs to query (i.e., the second user).

[0136] Among them, user A can perform a trigger operation on user B in the session interface 500b, so that the user terminal can respond to the trigger operation and generate a data query request 5b for querying sensitive data of user B. It can be understood that the user terminal can determine in the application client that the session attribute of the session interface 500b is the second session attribute (i.e., the session attribute corresponding to the group chat scene). Further, the user terminal can obtain the user identification information b of user B, and according to the second session attribute, it can determine that the scene type data of user B is Figure 4 The scene type data shown is "1".

[0137] Furthermore, the user terminal can determine the authentication information corresponding to user B in the session interface 500b. It can be understood that if the enterprise identification information corresponding to user A (i.e., the first user) in the session interface 500b is enterprise identification information 1 (i.e., the first enterprise identification information), and the enterprise identification information corresponding to user B (i.e., the second user) is also enterprise identification information 1 (i.e., the second enterprise identification information), the user terminal can determine that the enterprise identification information of user A and user B is the enterprise identification information of the same enterprise corresponding to group 1. At this time, the user terminal can use the group identification information corresponding to group 1 as the first session identification information corresponding to the session interface 500b, and then use the first session identification information as the authentication information of user B.

[0138] At this time, the user terminal can use the user identification information b, the scene type data "1" and the group identification information corresponding to group 1 (i.e., the first session identification information) as business key information, and then generate a data query request 5b (i.e., the first data query request) for querying user B based on the business key information. The user terminal can send the data query request 5b to the server 50b, so that the server 50b can obtain the sensitive data of user B when determining that the data query request 5b is legitimate, and then send the sensitive data of user B to the user terminal. At this time, the user terminal can output the sensitive data of user B to Figure 5b In the user information display interface 510b of the application client shown in FIG.

[0139] Optionally, if the enterprise identification information corresponding to user A (i.e., the first user) in the session interface 500b is enterprise identification information 1 (i.e., the first enterprise identification information), and the enterprise identification information corresponding to user B (i.e., the second user) is enterprise identification information 2 (i.e., the second enterprise identification information), the user terminal can determine that the enterprise identification information of user A and user B is the enterprise identification information of different enterprises corresponding to group 1. At this time, the user terminal can use the group identification information corresponding to group 1 as the corresponding second session identification information in the session interface, and further use the second session identification information and enterprise identification information 1 (i.e., the first enterprise identification information) as the authentication information of user B.

[0140] At this time, the user terminal can use the user identification information b, the scene type data "1", the group identification information corresponding to group 1 (i.e., the second session identification information), and the enterprise identification information 1 (i.e., the first enterprise identification information) as business key information, and then generate a data query request 5b (i.e., the first data query request) for querying user B based on the business key information. The user terminal can send the data query request 5b to the server 50b, so that the server 50b can obtain the sensitive data of user B when determining that the data query request 5b is legitimate, and then send the sensitive data of user B to the user terminal. At this time, the user terminal can output the sensitive data of user B to Figure 5b In the user information display interface 510b of the application client shown in FIG.

[0141] For further understanding, please refer to Figure 6 , Figure 6 Schematic diagram of a scenario of querying sensitive data of a second user in a contact list provided by an embodiment of the present application. Figure 6 As shown, the user terminal running the application client in the embodiment of the present application can be the above Figure 1 Any user terminal in the user terminal cluster shown, for example, user terminal 100a. The server 60 corresponding to the application client can be the above Figure 1 The server 10 is shown.

[0142] like Figure 6 As shown, the user corresponding to the user terminal in the embodiment of the present application may be user A (i.e., the first user), and the list display interface 600 of the user terminal may include multiple users, taking three as an example, and these three users may specifically include user B, user C, and user D. Among them, user B may be the user that user A needs to query (i.e., the second user). These three users may be users in the contact list (e.g., department 1) of the application client.

[0143] Among them, user A can perform a trigger operation on user B in the list display interface 600. At this time, the user terminal can respond to the trigger operation and generate a data query request 6 for querying the sensitive data of user B. It can be understood that if user A is a user in enterprise a, and user B is a user in the contact list corresponding to department 1 (for example, the administrative department) of enterprise a in the application client, then the user terminal can determine the list attribute of the contact list as the same enterprise scene in the organizational structure in the list display interface of the application client. Furthermore, the user terminal can determine the user identification information b of user B in the list attribute, and according to the list attribute, it can be determined that the scene type data of user B is Figure 4 The scene type data "4" is shown. In the contact list corresponding to the department 1, the user terminal can use the enterprise identification information corresponding to user A (ie, enterprise identification information 1 of enterprise a) as the authentication information of user B.

[0144] At this time, the user terminal can use the user identification information b, the scene type data "4" and the enterprise identification information 1 as business key information, and then generate a data query request 6 (i.e., a first data query request) for querying user B based on the business key information. The user terminal can send the data query request 6 to the server 60, so that when the server 60 determines that the data query request 6 is legitimate, it obtains the sensitive data of user B, and then sends the sensitive data of user B to the user terminal. At this time, the user terminal can output the sensitive data of user B to Figure 6 In the user information display interface 610 of the application client shown in FIG.

[0145] Optionally, if user A is a user in enterprise a, and user B is a user in the contact list corresponding to department 1 of enterprise b (i.e., an Internet enterprise) in the application client, the user terminal can determine the list attribute of the contact list as the external contact friend scene in the organizational structure in the list display interface 600 of the application client. Further, the user terminal can determine the user identification information b of user B in the list attribute, and according to the list attribute, it can be determined that the scene type data of user B is Figure 4 The scene type data "3" is shown. In the contact list corresponding to the department 1, the user terminal can use the enterprise identification information corresponding to user A (ie, enterprise identification information 1 of enterprise a) as the authentication information of user B.

[0146] At this time, the user terminal can use the user identification information b, the scene type data "3" and the enterprise identification information 1 as business key information, and then generate a data query request 6 (i.e., a first data query request) for querying user B based on the business key information. The user terminal can send the data query request 6 to the server 60, so that the server 60 obtains the sensitive data of user B when determining that the data query request 6 is legitimate, and then can send the sensitive data of user B to the user terminal. At this time, the user terminal can output the sensitive data of user B to Figure 6 In the user information display interface 610 of the application client shown in FIG.

[0147] In an embodiment of the present application, a computer device (i.e., a user terminal) running an application client can respond to a trigger operation of a first user accessing the application client through the first account information, and then the user of the second account information corresponding to the trigger operation can be used as the second user to be queried. Among them, the first user and the second user are both users after sensitive data isolation in the application client. The first user here can be a viewing user, and the second user can be a user to be queried. Since the first user and the second user are users after sensitive data isolation, in the process of querying the sensitive data of the second user in the application client in the embodiment of the present application, it is necessary to judge the legitimacy of the first data query request sent by the user terminal through the server to ensure the security of the sensitive data of the second user in the application client. For example, in the process of querying the sensitive data of the second user through the user terminal, the first user not only needs to obtain the user identification information corresponding to the second user, but also needs to obtain the scene type data and authentication information of the second user. The scene type data here can be used to indicate the scene type of the second user in the application client. For example, the scene type indicated by the scene type data "1" can be a group chat scene. Furthermore, the user terminal can send a first data query request to the server corresponding to the application client based on business-critical information (e.g., user identification information, scenario type data, and authentication information). In this way, when the server determines that the first data query request is legitimate, it can return the sensitive data of the second user to the user terminal. At this time, the user terminal can further output the sensitive data of the second user to the user information display interface of the application client. It should be understood that, on the contrary, when the server determines that the first data query request is not legitimate, it is not necessary to return the sensitive data of the second user to the user terminal, thereby effectively ensuring the security of the user's sensitive data.

[0148] For further information, see Figure 7 , Figure 7 Schematic diagram of a sensitive data query method provided by an embodiment of the present application. Figure 7 As shown, the method can be performed by a user terminal and a server together, and the user terminal can be the above Figure 1 Any user terminal in the user terminal cluster shown, for example, user terminal 100a. The server may be the above Figure 1 The method may include at least the following steps S201 to S206:

[0149] Step S201, the user terminal responds to a trigger operation of a first user accessing an application client through first account information, and uses a user of second account information corresponding to the trigger operation as a second user to be queried;

[0150] Step S202: The user terminal obtains user identification information, scenario type data, and authentication information corresponding to the second user, uses the user identification information, scenario type data, and authentication information as business key information for querying sensitive data of the second user, and sends a first data query request to the server corresponding to the application client based on the business key information;

[0151] Step S203: The server determines the legitimacy of the first data query request based on the business-critical information.

[0152] Step S204: When the server determines that the first data query request is legitimate, the server obtains the sensitive data of the second user.

[0153] Step S205: the server returns the sensitive data of the second user to the user terminal.

[0154] Step S206: The user terminal outputs the sensitive data of the second user to the user information display interface of the application client.

[0155] The specific implementation of steps S201 to S206 can be found in the above Figure 3 The description of step S101 to step S104 in the corresponding embodiment will not be repeated here.

[0156] It should be understood that the user terminal in the embodiment of the present application can run an application client, and the scene type corresponding to the public broadcast platform associated with the application client can belong to the second authentication type (i.e., a scene that is difficult to authenticate), but the sensitive data of the first user corresponding to the user terminal can also be obtained through the user terminal if the security policy allows. The security policy here can refer to the background staff corresponding to the application client can set a security policy for the public broadcast platform, for example, the security policy can allow the public broadcast platform to obtain the sensitive data of the user in the application client. For example, the security policy can allow the public broadcast platform to obtain the basic data of the user in the application client. Of course, if the server receives a complaint request from other user terminals to the public broadcast platform, the server can generate a prompt message for prompting the background staff to adjust the security policy of the public broadcast platform based on the complaint request. For example, the background staff can modify the security policy of the public broadcast platform to a certain time limit (for example, 3 days), and the public broadcast platform is not allowed to obtain the sensitive data of the user. It can be seen that the embodiment of the present application can dynamically protect the sensitive data of the user in the application client.

[0157] It is understandable that the first user can perform a trigger operation on the public broadcasting platform, thereby causing the user terminal to respond to the trigger operation, thereby outputting the information display interface of the public broadcasting platform. The information display interface may include business data information published to the enterprise object corresponding to the public broadcasting platform and an interactive editing control for interacting with the business data information.

[0158] Furthermore, the first user can perform a trigger operation on the interactive editing control, so that the user terminal can respond to the trigger operation and output a text entry sub-interface independent of the information display interface, thereby allowing the first user to enter text interactive information for the business data information on the text entry sub-interface. The text entry sub-interface can be an interface superimposed on the information display interface, and the size of the text entry sub-interface is smaller than the size of the information display interface; the text entry sub-interface can include an interactive publishing control.

[0159] It should be understood that when the first user finishes editing the text interactive information, a trigger operation can be performed on the interactive publishing control, so that the user terminal can respond to the trigger operation, so that the second data query request for obtaining the sensitive data of the first user can be sent to the server corresponding to the application client. It can be understood that the scene corresponding to the information display interface of the public broadcasting platform can be an interface jump scene. When the first user performs a trigger operation on the interactive publishing control, the user terminal can use the first user as the user to be queried, and then authorize the public broadcasting platform to obtain the user identification information of the first user in the application client based on the interface jump scene. Further, the user terminal can determine the scene type data corresponding to the first user based on the interface attributes of the interface jump scene, and can obtain the platform identification information corresponding to the public broadcasting platform and the text identification information of the text interactive information, and then can use the platform identification information and the text identification information as the authentication information corresponding to the first user. It should be understood that the user terminal can use the user identification information of the first user, the scene type data corresponding to the first user, and the authentication information corresponding to the first user as the business key information of the first user. Furthermore, the user terminal may generate a second data query request for querying sensitive data of the first user based on the business-critical information of the first user, and send the second data query request to a server corresponding to the application client.

[0160] It can be understood that when the server receives the second data query request, it can compare it with the security policy of the public broadcasting platform. When the security policy indicates that the data query request sent by the public broadcasting platform is successfully authenticated, the server can obtain the sensitive data of the first user, and then return the sensitive data of the first user to the user terminal, so that the user terminal can use the text interaction information and the sensitive data of the first user as interactive information of the business data information.

[0161] For further understanding, please refer to Figure 8 , Figure 8 Schematic diagram of a scenario for obtaining sensitive data of a first user provided by an embodiment of the present application. Figure 8 As shown, the user terminal 81 running the application client can be the above Figure 1 Any user terminal in the user terminal cluster shown, for example, user terminal 100a. The server corresponding to the application client may be server 80, which may be the above-mentioned Figure 1 The server 10 is shown.

[0162] It is understandable that the display interface of the user terminal 81 may include multiple public broadcasting platforms, specifically public broadcasting platform 1, public broadcasting platform 2, public broadcasting platform 3 and public broadcasting platform 4. The public broadcasting platform may be an H5 (an application client on an interactive web page) or a mini-program interface opened by the application client. Among them, the user A (i.e., the first user) corresponding to the user terminal 81 can perform a trigger operation on a certain public broadcasting platform (for example, public broadcasting platform 4), and then the user terminal 81 can respond to the trigger operation, thereby outputting the information display interface 800 of the public broadcasting platform 4. Among them, the information display interface 800 may include business data information published to the enterprise object corresponding to the public broadcasting platform 4 and interactive editing controls for interacting with the business data information (for example, a "write message" control).

[0163] Furthermore, user A can perform a trigger operation on the interactive editing control, so that the user terminal 81 can respond to the trigger operation and output a text entry sub-interface 810 independent of the information display interface 800, thereby allowing user A to enter text interactive information for business data information on the text entry sub-interface 810. The text entry sub-interface 810 can be an interface superimposed on the information display interface 800, and the size of the text entry sub-interface 810 is smaller than the size of the information display interface 800; and the text entry sub-interface 810 can include an interactive publishing control (for example, a "submit" control).

[0164] It is understandable that the scene corresponding to the information display interface 800 of the public broadcasting platform 4 can be an interface jump scene. It should be understood that when user A has finished editing the text interactive information, a trigger operation can be performed on the interactive publishing control. At this time, the user terminal 81 responds to the trigger operation, takes user A as the user to be queried, and then can authorize the public broadcasting platform 4 to obtain the user identification information a of user A in the application client based on the interface jump scene. Furthermore, the user terminal 81 can determine that the scene type data corresponding to user A is the above-mentioned based on the interface attributes of the interface jump scene. Figure 4 The scene type data "9" shown in the figure can obtain the platform identification information corresponding to the public broadcasting platform 4 and the text identification information of the text interaction information, and then the platform identification information and the text identification information can be used as the authentication information corresponding to the user A. It should be understood that the user terminal 81 can use the user identification information a of the user A, the scene type data "9" and the platform identification information and the text identification information as the business key information of the user A. Further, the user terminal 81 can generate a second data query request for querying the sensitive data of the user A based on the business key information of the user A, and send the second data query request to the server 80 corresponding to the application client.

[0165] It can be understood that when the server 80 receives the second data query request, it can compare it with the security policy of the public broadcasting platform 4. When the security policy indicates that the second data query request sent by the public broadcasting platform 4 is successfully authenticated, the server 80 can obtain the sensitive data of user A, and then return the sensitive data of user A to the user terminal 81, so that the user terminal 81 can use the text interaction information and the sensitive data of user A as interactive information of business data information.

[0166] In an embodiment of the present application, a computer device (i.e., a user terminal) running an application client can respond to a trigger operation of a first user accessing the application client through the first account information, and then the user of the second account information corresponding to the trigger operation can be used as the second user to be queried. Among them, the first user and the second user are both users after sensitive data isolation in the application client. The first user here can be a viewing user, and the second user can be a user to be queried. Since the first user and the second user are users after sensitive data isolation, in the process of querying the sensitive data of the second user in the application client in the embodiment of the present application, it is necessary to judge the legitimacy of the first data query request sent by the user terminal through the server to ensure the security of the sensitive data of the second user in the application client. For example, in the process of querying the sensitive data of the second user through the user terminal, the first user not only needs to obtain the user identification information corresponding to the second user, but also needs to obtain the scene type data and authentication information of the second user. The scene type data here can be used to indicate the scene type of the second user in the application client. For example, the scene type indicated by the scene type data "1" can be a group chat scene. Furthermore, the user terminal can send a first data query request to the server corresponding to the application client based on business-critical information (e.g., user identification information, scenario type data, and authentication information). In this way, when the server determines that the first data query request is legitimate, it can return the sensitive data of the second user to the user terminal. At this time, the user terminal can further output the sensitive data of the second user to the user information display interface of the application client. It should be understood that, on the contrary, when the server determines that the first data query request is not legitimate, it is not necessary to return the sensitive data of the second user to the user terminal, thereby effectively ensuring the security of the user's sensitive data.

[0167] For further information, see Fig. 9 , Fig. 9 1 is a schematic diagram of the structure of a sensitive data query device provided in an embodiment of the present application. The sensitive data query device 1 may be a computer program (including program code) running in a computer device. For example, the sensitive data query device 1 is an application software. The sensitive data query device 1 may be used to execute the corresponding steps in the method provided in an embodiment of the present application. Fig. 9 As shown, the sensitive data query device 1 can be run on a user terminal, and the user terminal can be the above Figure 2 The user terminal 30 in the corresponding embodiment. The sensitive data query device 1 may include: a to-be-queried user determination module 10, a first request sending module 20, a sensitive data acquisition module 30, a sensitive data output module 40, a display interface output module 50, an information entry module 60, a second request sending module 70 and an interactive information determination module 80.

[0168] The to-be-queried user determination module 10 is used to respond to a trigger operation of a first user accessing the application client through the first account information, and to use a user of the second account information corresponding to the trigger operation as a second user to be queried; the first user and the second user are both users after sensitive data isolation is performed in the application client;

[0169] The first request sending module 20 is used to obtain user identification information, scenario type data and authentication information corresponding to the second user, use the user identification information, scenario type data and authentication information as business-critical information for querying sensitive data of the second user, and send a first data query request to the server corresponding to the application client based on the business-critical information; the business-critical information is used to instruct the server to determine the legitimacy of the first data query request.

[0170] The first user and the second user are users in the conversation interface of the application client;

[0171] The first request sending module 20 includes: a session attribute determining unit 201 , a first determining unit 202 , a second determining unit 203 , a first request sending unit 204 , a list attribute determining unit 205 , a third determining unit 206 , a fourth determining unit 207 and a second request sending unit 208 .

[0172] The session attribute determination unit 201 is used to determine the session attributes of the session interface in the application client;

[0173] The first determining unit 202 is used to determine the user identification information mapped to the second user corresponding to the second account information in the conversation interface, and determine the scene type data corresponding to the second user according to the conversation attribute;

[0174] The second determining unit 203 is used to determine the authentication information corresponding to the second user in the session interface.

[0175] Wherein, the session attribute includes a first session attribute;

[0176] The second determining unit 203 includes: a first determining subunit 2031 , a second determining subunit 2032 , a third determining subunit 2033 and a fourth determining subunit 2034 .

[0177] The first determining subunit 2031 is configured to determine, in the session interface, session identification information associated with the first user and the second user based on the first session attribute, and use the session identification information as authentication information corresponding to the second user.

[0178] The session attribute includes a second session attribute, and the first user and the second user are both users in a public broadcast group of the application client;

[0179] The second determining subunit 2032 is configured to use the enterprise identification information corresponding to the first user as the first enterprise identification information, and use the enterprise identification information corresponding to the second user as the second enterprise identification information;

[0180] The third determining subunit 2033 is configured to use the group identification information corresponding to the public broadcast group as the first session identification information corresponding to the session interface, and use the first session identification information as the authentication information corresponding to the second user if the first enterprise identification information and the second enterprise identification information are enterprise identification information of the same enterprise corresponding to the public broadcast group;

[0181] The fourth determination subunit 2034 is used to use the group identification information corresponding to the public broadcast group as the second session identification information corresponding to the session interface, and use the first enterprise identification information and the second session identification information as authentication information corresponding to the second user if the first enterprise identification information and the second enterprise identification information are enterprise identification information of different enterprises corresponding to the public broadcast group.

[0182] The specific implementation of the first determining subunit 2031, the second determining subunit 2032, the third determining subunit 2033 and the fourth determining subunit 2034 can refer to the above Figure 3 The description of the authentication information in the corresponding embodiment will not be repeated here.

[0183] The first request sending unit 204 is used to use user identification information, scenario type data and authentication information as business key information, generate a first data query request for querying sensitive data of the second user based on the business key information, and send the first data query request to the server corresponding to the application client.

[0184] The second user is a user in the contact list of the application client;

[0185] The list attribute determination unit 205 is used to determine the list attributes of the contact list in the list display interface of the application client;

[0186] The third determining unit 206 is used to determine the user identification information mapped to the second user corresponding to the second account information in the list attributes, and determine the scene type data corresponding to the second user according to the list attributes;

[0187] The fourth determining unit 207 is used to use the enterprise identification information corresponding to the first user as the authentication information corresponding to the second user in the contact list;

[0188] The second request sending unit 208 is used to use the user identification information, scenario type data and authentication information as business key information, generate a first data query request for querying sensitive data of the second user based on the business key information, and send the first data query request to the server corresponding to the application client.

[0189] The specific implementation of the session attribute determination unit 201, the first determination unit 202, the second determination unit 203, the first request sending unit 204, the list attribute determination unit 205, the third determination unit 206, the fourth determination unit 207 and the second request sending unit 208 can be referred to above. Figure 3 The description of step S102 in the corresponding embodiment will not be repeated here.

[0190] The sensitive data acquisition module 30 is used to acquire the sensitive data of the second user returned by the server when the server determines that the first data query request is legitimate;

[0191] The sensitive data output module 40 is used to output the sensitive data of the second user to the user information display interface of the application client.

[0192] The display interface output module 50 is used to respond to the trigger operation of the first user on the public broadcast platform associated with the application client, and output the information display interface of the public broadcast platform; the information display interface includes the business data information published by the enterprise object corresponding to the public broadcast platform and the interactive editing control for interacting with the business data information;

[0193] The information entry module 60 is used to respond to the trigger operation for the interactive editing control, output a text entry sub-interface independent of the information display interface, and enter text interactive information for business data information on the text entry sub-interface; the text entry sub-interface is an interface superimposed on the information display interface, and the size of the text entry sub-interface is smaller than the size of the information display interface; the text entry sub-interface includes an interactive publishing control;

[0194] The second request sending module 70 is used to respond to the triggering operation on the interactive publishing control and send a second data query request for obtaining sensitive data of the first user to the server corresponding to the application client.

[0195] Among them, the scene corresponding to the information display interface of the public broadcasting platform is the interface jump scene;

[0196] The second request sending module 70 includes: an authorization unit 701 , a fifth determination unit 702 , a sixth determination unit 703 , a key information determination unit 704 and a third request sending unit 705 .

[0197] The authorization unit 701 is used to respond to the trigger operation for the interactive publishing control, take the first user as the user to be queried, and authorize the public broadcasting platform to obtain the user identification information of the first user in the application client based on the interface jump scenario;

[0198] The fifth determining unit 702 is configured to determine the scenario type data corresponding to the first user based on the interface attribute of the interface jump scenario;

[0199] The sixth determining unit 703 is used to obtain the platform identification information corresponding to the public broadcasting platform and the text identification information of the text interaction information, and use the platform identification information and the text identification information as the authentication information corresponding to the first user;

[0200] The key information determination unit 704 is used to use the user identification information of the first user, the scene type data corresponding to the first user, and the authentication information corresponding to the first user as the business key information of the first user;

[0201] The third request sending unit 705 is used to generate a second data query request for querying the sensitive data of the first user based on the business-critical information of the first user, and send the second data query request to the server corresponding to the application client.

[0202] The specific implementation of the authorization unit 701, the fifth determination unit 702, the sixth determination unit 703, the key information determination unit 704 and the third request sending unit 705 can refer to the above Figure 7 The description of the second data query request in the corresponding embodiment will not be repeated here.

[0203] The interactive information determination module 80 is used to use the text interactive information and the sensitive data of the first user as interactive information of the business data information when receiving the sensitive data of the first user returned by the server.

[0204] The specific implementation methods of the to-be-queried user determination module 10, the first request sending module 20, the sensitive data acquisition module 30, the sensitive data output module 40, the display interface output module 50, the information entry module 60, the second request sending module 70 and the interactive information determination module 80 can be referred to in the above Figure 3 The description of step S101 to step S104 in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated here either.

[0205] For further information, see Fig.10 , Fig.10 Schematic diagram of a computer device provided in an embodiment of the present application. Fig.10 As shown, the computer device 1000 may be the above Figure 2 Corresponding to the user terminal 30 in the embodiment, the computer device 1000 may include: at least one processor 1001, such as a CPU, at least one network interface 1004, a user interface 1003, a memory 1005, and at least one communication bus 1002. The communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display) and a keyboard (Keyboard), and the network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory, or a non-volatile memory (non-volatile memory), such as at least one disk storage. The memory 1005 may optionally also be at least one storage device located away from the aforementioned processor 1001. Fig.10 As shown, the memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a device control application.

[0206] exist Fig.10 In the computer device 1000 shown, the network interface 1004 is mainly used for network communication with the server; the user interface 1003 is mainly used for providing an input interface for the user; and the processor 1001 can be used to call the device control application stored in the memory 1005 to achieve:

[0207] In response to a trigger operation of a first user accessing the application client through the first account information, a user of the second account information corresponding to the trigger operation is used as a second user to be queried; the first user and the second user are both users after sensitive data isolation is performed in the application client;

[0208] Obtaining user identification information, scenario type data, and authentication information corresponding to the second user, using the user identification information, scenario type data, and authentication information as business-critical information for querying sensitive data of the second user, and sending a first data query request to a server corresponding to the application client based on the business-critical information; the business-critical information is used to instruct the server to determine the legitimacy of the first data query request;

[0209] When the server determines that the first data query request is legitimate, obtaining the sensitive data of the second user returned by the server;

[0210] The sensitive data of the second user is output to the user information display interface of the application client.

[0211] It should be understood that the computer device 1000 described in the embodiment of the present application can execute the above Figure 3 and Figure 7The description of the sensitive data query method in the corresponding embodiment can also be performed as described above. Fig. 9 The description of the sensitive data query device 1 in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of adopting the same method will not be repeated here either.

[0212] In addition, it should be pointed out here that: the embodiment of the present application also provides a computer-readable storage medium, and the computer-readable storage medium stores a computer program executed by the sensitive data query device 1 mentioned above, and the computer program includes program instructions. When the processor executes the program instructions, it can execute the above-mentioned Figure 3 or Figure 7 The description of the sensitive data query method in the corresponding embodiment will therefore not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated. For technical details not disclosed in the computer-readable storage medium embodiment involved in this application, please refer to the description of the method embodiment of this application. As an example, program instructions may be deployed to be executed on one computing device, or on multiple computing devices located at one location, or on multiple computing devices distributed at multiple locations and interconnected by a communication network. Multiple computing devices distributed at multiple locations and interconnected by a communication network can constitute a blockchain system.

[0213] On one hand, the present application provides a computer program product or a computer program, the computer program product or the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device can execute the above Figure 3 or Figure 7 The description of the sensitive data query method in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of adopting the same method will not be repeated here.

[0214] For further information, see Fig.11 , Fig.11 : is a schematic diagram of the structure of a sensitive data query device provided in an embodiment of the present application. The sensitive data query device 2 may be a computer program (including program code) running in a computer device. For example, the sensitive data query device 2 is an application software. The sensitive data query device 2 may be used to execute the corresponding steps in the method provided in an embodiment of the present application. Fig.11 As shown, the sensitive data query device 2 can be run on a server, which can be the above-mentioned Figure 2The server 20 in the corresponding embodiment. The sensitive data query device 2 may include: a query request receiving module 100, a legitimacy determination module 200, a data acquisition module 300 and a data return module 400.

[0215] The query request receiving module 100 is used to receive a first data query request sent by a user terminal running an application client based on business key information; the business key information includes user identification information, scenario type data and authentication information corresponding to a second user; the second user is a user to be queried determined after a first user who accesses the application client through the first account information performs a triggering operation; the first user and the second user are both users after sensitive data isolation is performed in the application client;

[0216] The legitimacy determination module 200 is used to determine the legitimacy of the first data query request based on the business key information.

[0217] The legitimacy determination module 200 includes: a first legitimacy determination unit 2010 and a second legitimacy determination unit 2020 .

[0218] The first legitimacy determination unit 2010 is configured to determine that the first data query request is legitimate if the scenario type data in the business key information meets the scenario query condition;

[0219] The second legitimacy determination unit 2020 is configured to determine that the first data query request is illegal if the scenario type data in the business-critical information does not satisfy the scenario query condition.

[0220] The specific implementation of the first legitimacy determination unit 2010 and the second legitimacy determination unit 2020 can refer to the above Figure 7 The description of step S203 in the corresponding embodiment will not be repeated here.

[0221] The data acquisition module 300 is used to acquire the sensitive data of the second user when it is determined that the first data query request is legitimate;

[0222] The data returning module 400 is used to return the sensitive data of the second user to the user terminal, so that the user terminal outputs the sensitive data of the second user to the user information display interface of the application client.

[0223] The specific implementation of the query request receiving module 100, the legitimacy determination module 200, the data acquisition module 300 and the data return module 400 can be found in the above Figure 7 The description of steps S201 to S206 in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated.

[0224] For further information, see Fig.12 , Fig.12 Schematic diagram of a computer device provided in an embodiment of the present application. Fig.12 As shown, the computer device 3000 may be the above Figure 2 Corresponding to the server 20 in the embodiment, the computer device 3000 may include: at least one processor 3001, such as a CPU, at least one network interface 3004, a user interface 3003, a memory 3005, and at least one communication bus 3002. The communication bus 3002 is used to realize the connection and communication between these components. The user interface 3003 may include a display screen (Display) and a keyboard (Keyboard), and the network interface 3004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 3005 may be a high-speed RAM memory, or a non-volatile memory (non-volatile memory), such as at least one disk storage. The storage 3005 may optionally also be at least one storage device located away from the aforementioned processor 3001. Fig.12 As shown, the memory 3005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a device control application.

[0225] exist Fig.12 In the computer device 3000 shown, the network interface 3004 is mainly used for network communication with the user terminal; the user interface 3003 is mainly used for providing an input interface for the user; and the processor 3001 can be used to call the device control application stored in the memory 3005 to achieve:

[0226] receiving a first data query request sent by a user terminal running an application client based on business key information; the business key information includes user identification information, scenario type data, and authentication information corresponding to a second user; the second user is a user to be queried determined after a trigger operation is performed by a first user who accesses the application client through the first account information; the first user and the second user are both users after sensitive data isolation;

[0227] Determining the legitimacy of the first data query request based on the business key information;

[0228] When determining that the first data query request is legitimate, obtaining sensitive data of the second user;

[0229] The sensitive data of the second user is returned to the user terminal, so that the user terminal outputs the sensitive data of the second user to the user information display interface of the application client.

[0230] It should be understood that the computer device 3000 described in the embodiment of the present application can execute the above Figure 7 The description of the sensitive data query method in the corresponding embodiment can also be performed as described above. Fig.11 The description of the sensitive data query device 2 in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of adopting the same method will not be repeated here either.

[0231] In addition, it should be pointed out here that: the embodiment of the present application also provides a computer-readable storage medium, and the computer-readable storage medium stores a computer program executed by the sensitive data query device 2 mentioned above, and the computer program includes program instructions. When the processor executes the program instructions, it can execute the above-mentioned Figure 7 The description of the sensitive data query method in the corresponding embodiment will therefore not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated. For technical details not disclosed in the computer-readable storage medium embodiment involved in this application, please refer to the description of the method embodiment of this application. As an example, program instructions may be deployed to be executed on one computing device, or on multiple computing devices located at one location, or on multiple computing devices distributed at multiple locations and interconnected by a communication network. Multiple computing devices distributed at multiple locations and interconnected by a communication network can constitute a blockchain system.

[0232] On one hand, the present application provides a computer program product or a computer program, the computer program product or the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device can execute the above Figure 3 or Figure 7 The description of the sensitive data query method in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of adopting the same method will not be repeated here.

[0233] For further information, see Fig.13 , Fig.13 1 is a schematic diagram of a data processing system provided in an embodiment of the present application. The data processing system 3 may include a data processing device 1a and a data processing device 2a. The data processing device 1a may be the above-mentioned Fig. 9 In the sensitive data query device 1 in the corresponding embodiment, it can be understood that the data processing device 1a can be integrated in the above Figure 2 The corresponding user terminal 30 in the embodiment will not be described in detail here. Fig.11In the corresponding embodiment, the sensitive data query device 2, it can be understood that the data processing device 2a can be integrated in the above Figure 2 The server 20 in the corresponding embodiment will not be described in detail here. In addition, the description of the beneficial effects of the same method will not be described in detail. For technical details not disclosed in the data processing system embodiment involved in this application, please refer to the description of the method embodiment of this application.

[0234] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the above-mentioned program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the above-mentioned storage medium can be a disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM), etc.

[0235] It should be noted that the collection and processing of user privacy-related data in this application should be strictly in accordance with the requirements of relevant national laws and regulations when applied in examples, and should have a legal basis or obtain the informed consent or separate consent of the personal information subject, and carry out subsequent data use and processing within the scope of authorization of laws and regulations and / or the personal information subject.

[0236] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A sensitive data query method, characterized in that: The method is executed by a user terminal and includes: In response to a trigger operation of a first user accessing an application client through first account information, a user of second account information corresponding to the trigger operation is used as a second user to be queried; the first user and the second user are both users after sensitive data isolation is performed in the application client; Obtain user identification information, scene type data, and authentication information corresponding to the second user, use the user identification information, scene type data, and authentication information as business-critical information for querying sensitive data of the second user, and send a first data query request to a server corresponding to the application client based on the business-critical information; the scene type data is used to indicate the scene type in which the second user is located in the application client; the business-critical information is used to instruct the server to determine the legitimacy of the first data query request, and the authentication information is used to match the scene type through the server to achieve scene authentication; When the server determines that the first data query request is legitimate, the scenario type corresponding to the scenario type data belongs to the first authentication type, and the scenario type matches the authentication information, the sensitive data of the second user returned by the server is obtained, the first data query request is legitimate means that the scenario type data satisfies the scenario query condition, and the scenario query condition is that the business-critical information contains the scenario type data; the authentication type of the scenario type includes a first authentication type and a second authentication type, the first authentication type is preset with at least one authenticatable scenario type, and the second authentication type is preset with at least one difficult-to-authenticate scenario type; the scenario types belonging to the first authentication type include group chat scenarios, external contact friend scenarios, same-enterprise scenarios, external client contact scenarios, single chat scenarios and public account scenarios, and the scenario types belonging to the second authentication type include forwarding message scenarios, favorite message scenarios, interface jump scenarios, daily report scenarios, resignation recommendation scenarios and friend recommendation scenarios; Outputting the sensitive data of the second user to the user information display interface of the application client; When the server determines that the first data query request is legitimate and the scenario type corresponding to the scenario type data belongs to the second authentication type, basic data of the second user returned by the server is acquired.

2. The method according to claim 1, characterized in that The first user and the second user are users in the session interface of the application client; The obtaining user identification information, scenario type data, and authentication information corresponding to the second user, using the user identification information, scenario type data, and authentication information as business-critical information for querying sensitive data of the second user, and sending a first data query request to a server corresponding to the application client based on the business-critical information, includes: Determining, in the application client, a session attribute of the session interface; Determining, in the session interface, user identification information mapped to a second user corresponding to the second account information, and determining, according to the session attribute, scene type data corresponding to the second user; Determining authentication information corresponding to the second user in the session interface; The user identification information, the scenario type data and the authentication information are used as business-critical information, a first data query request for querying the sensitive data of the second user is generated based on the business-critical information, and the first data query request is sent to a server corresponding to the application client.

3. The method according to claim 2, characterized in that The session attributes include a first session attribute; The determining, in the session interface, authentication information corresponding to the second user includes: Based on the first session attribute, session identification information associated with the first user and the second user is determined in the session interface, and the session identification information is used as authentication information corresponding to the second user.

4. The method according to claim 2, characterized in that: The session attribute includes a second session attribute, and the first user and the second user are both users in a public broadcast group of the application client; The determining, in the session interface, authentication information corresponding to the second user includes: Using the enterprise identification information corresponding to the first user as the first enterprise identification information, and using the enterprise identification information corresponding to the second user as the second enterprise identification information; If the first enterprise identification information and the second enterprise identification information are enterprise identification information of the same enterprise corresponding to the public broadcast group, the group identification information corresponding to the public broadcast group is used as the first session identification information corresponding to the session interface, and the first session identification information is used as the authentication information corresponding to the second user; If the first enterprise identification information and the second enterprise identification information are enterprise identification information of different enterprises corresponding to the public broadcast group, the group identification information corresponding to the public broadcast group is used as the second session identification information corresponding to the session interface, and the first enterprise identification information and the second session identification information are used as authentication information corresponding to the second user.

5. The method according to claim 1, characterized in that The second user is a user in the contact list of the application client; The obtaining user identification information, scenario type data, and authentication information corresponding to the second user, using the user identification information, scenario type data, and authentication information as business-critical information for querying sensitive data of the second user, and sending a first data query request to a server corresponding to the application client based on the business-critical information, includes: Determining a list attribute of the contact list in a list display interface of the application client; Determine the user identification information mapped to the second user corresponding to the second account information in the list attributes, and determine the scene type data corresponding to the second user according to the list attributes; In the contact list, using the enterprise identification information corresponding to the first user as the authentication information corresponding to the second user; The user identification information, the scenario type data and the authentication information are used as business-critical information, a first data query request for querying the sensitive data of the second user is generated based on the business-critical information, and the first data query request is sent to a server corresponding to the application client.

6. A sensitive data query method, characterized in that: The method is executed by a server and includes: A first data query request is received from a user terminal running an application client based on business-critical information; the business-critical information includes user identification information, scene type data, and authentication information corresponding to a second user, the scene type data is used to indicate the scene type in which the second user is located in the application client, and the authentication information is used to match the scene type through the server to achieve scene authentication; the second user is a user to be queried determined after a first user who accesses the application client through first account information performs a triggering operation; the first user and the second user are both users after sensitive data isolation is performed in the application client; Determining the legitimacy of the first data query request based on the business key information; When determining that the first data query request is legitimate, determining the scenario type of the second user based on the scenario type data; the legitimacy of the first data query request means that the scenario type data satisfies a scenario query condition, and the scenario query condition is that the business key information includes the scenario type data; When determining that the scenario type of the second user belongs to the first authentication type, determining the matching of the scenario type with the authentication information; the authentication type of the scenario type includes a first authentication type and a second authentication type, the first authentication type is preset with at least one authenticatable scenario type, and the second authentication type is preset with at least one difficult-to-authenticate scenario type; the scenario types belonging to the first authentication type include group chat scenarios, external contact friend scenarios, same-enterprise scenarios, external client contact scenarios, single chat scenarios, and public account scenarios, and the scenario types belonging to the second authentication type include forwarding message scenarios, favorite message scenarios, interface jump scenarios, daily report scenarios, resignation recommendation scenarios, and friend recommendation scenarios; If the scenario type matches the authentication information, obtaining sensitive data of the second user; Returning the sensitive data of the second user to the user terminal, so that the user terminal outputs the sensitive data of the second user to the user information display interface of the application client; When it is determined that the scenario type of the second user belongs to the second authentication type, basic data of the second user is acquired, and the basic data of the second user is returned to the user terminal.

7. A sensitive data query device, characterized in that: The device runs on a user terminal and includes: A module for determining users to be queried is used to respond to a trigger operation of a first user accessing an application client through first account information, and to use a user of second account information corresponding to the trigger operation as a second user to be queried; the first user and the second user are both users after sensitive data isolation is performed in the application client; a first request sending module, configured to obtain user identification information, scenario type data, and authentication information corresponding to the second user, use the user identification information, scenario type data, and authentication information as business key information for querying sensitive data of the second user, and send a first data query request to a server corresponding to the application client based on the business key information; the scenario type data is used to indicate the scenario type of the second user in the application client; the business key information is used to instruct the server to determine the legitimacy of the first data query request, and the authentication information is used to match the scenario type through the server to achieve scenario authentication; A sensitive data acquisition module, used for acquiring the sensitive data of the second user returned by the server when the server determines that the first data query request is legitimate, the scenario type corresponding to the scenario type data belongs to the first authentication type, and the scenario type matches the authentication information, wherein the legitimacy of the first data query request means that the scenario type data satisfies the scenario query condition, and the scenario query condition is that the business-critical information contains the scenario type data; the authentication type of the scenario type includes a first authentication type and a second authentication type, the first authentication type is preset with at least one authenticatable scenario type, and the second authentication type is preset with at least one difficult-to-authenticate scenario type; the scenario types belonging to the first authentication type include group chat scenarios, external contact friend scenarios, same-enterprise scenarios, external client contact scenarios, single chat scenarios, and public account scenarios, and the scenario types belonging to the second authentication type include forwarding message scenarios, favorite message scenarios, interface jump scenarios, daily report scenarios, resignation recommendation scenarios, and friend recommendation scenarios; A sensitive data output module, used to output the sensitive data of the second user to the user information display interface of the application client; The sensitive data query device is further used to obtain the basic data of the second user returned by the server when the server determines that the first data query request is legal and the scenario type corresponding to the scenario type data belongs to the second authentication type.

8. A sensitive data query device, characterized in that: The device runs on a server and includes: A query request receiving module, used to receive a first data query request sent by a user terminal running an application client based on business-critical information; the business-critical information includes user identification information, scene type data and authentication information corresponding to a second user, the scene type data is used to indicate the scene type in which the second user is located in the application client, and the authentication information is used to match the scene type through the server to achieve scene authentication; the second user is a user to be queried determined after a first user who accesses the application client through the first account information performs a triggering operation; the first user and the second user are both users after sensitive data isolation is performed in the application client; A legitimacy determination module, used to determine the legitimacy of the first data query request based on the business key information; The legality determination module includes: a first legitimacy determination unit, configured to determine that the first data query request is legitimate if the scenario type data in the business-critical information satisfies a scenario query condition, wherein the scenario query condition is that the business-critical information contains the scenario type data; A data acquisition module, used to determine the scenario type of the second user based on the scenario type data when determining that the first data query request is legitimate; when determining that the scenario type of the second user belongs to the first authentication type, determine the matching of the scenario type with the authentication information; if the scenario type matches the authentication information, obtain the sensitive data of the second user; the authentication type of the scenario type includes a first authentication type and a second authentication type, the first authentication type is preset with at least one authenticatable scenario type, and the second authentication type is preset with at least one difficult-to-authenticate scenario type; the scenario types belonging to the first authentication type include group chat scenarios, external contact friend scenarios, same-enterprise scenarios, external client contact scenarios, single chat scenarios and public account scenarios, and the scenario types belonging to the second authentication type include forwarding message scenarios, favorite message scenarios, interface jump scenarios, daily report scenarios, resignation recommendation scenarios and friend recommendation scenarios; a data returning module, configured to return the sensitive data of the second user to the user terminal, so that the user terminal outputs the sensitive data of the second user to the user information display interface of the application client; The sensitive data query device is further used to obtain basic data of the second user when it is determined that the scenario type of the second user belongs to the second authentication type, and return the basic data of the second user to the user terminal.

9. A computer device, characterized in that: include: Processor, memory, network interface; The processor is connected to a memory and a network interface, wherein the network interface is used to provide a data communication function, the memory is used to store a computer program, and the processor is used to call the computer program to execute the method described in any one of claims 1-6.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions. When the program instructions are executed by a processor, the method according to any one of claims 1 to 6 is executed.

Images