CN113704646A

CN113704646A - User information searching method, device, equipment and computer readable storage medium

Info

Publication number: CN113704646A
Application number: CN202010442831.XA
Authority: CN
Inventors: 黄铁鸣; 吕阳阳; 林莉; 李斌; 赵东
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-05-22
Filing date: 2020-05-22
Publication date: 2021-11-26

Abstract

The embodiment of the application provides a user information searching method, a device, equipment and a computer readable storage medium, wherein the method comprises the following steps: responding to a first operation aiming at a user information searching function in enterprise instant messaging application, acquiring background searching authority information of the user and acquiring a searching keyword; when determining that the user has the background search authority based on the background search authority information, determining a target search result based on the search keyword; and outputting the target search result. Through the method and the device, not only can the information of the enterprise address list be protected, but also the cross-team communication requirements of part of users can be met.

Description

User information searching method, device, equipment and computer readable storage medium

Technical Field

The embodiment of the application relates to the technical field of instant messaging, and relates to but is not limited to a user information searching method, a user information searching device, user information searching equipment and a computer readable storage medium.

Background

With the continuous development of internet technology, people's work, study and life have changed from the top to the bottom. In order to reduce mutual interference between work and life as much as possible, people can install the enterprise instant messaging application in own mobile terminal or work terminal, so that work related affairs can be processed by the enterprise instant messaging application. Because enterprises have two requirements of protecting organization structures and cross-department communication, the address book in the enterprise instant messaging application generally supports the check-limiting rule so as to meet the requirements of the enterprise protection organization structures, but the protection measure is not beneficial to the limited members or teams to carry out cross-team communication, and the instant messaging efficiency is influenced.

Disclosure of Invention

The embodiment of the application provides a user information searching method, a user information searching device, user information searching equipment and a computer readable storage medium, which can protect enterprise address book information and meet cross-team communication requirements of part of users.

The technical scheme of the embodiment of the application is realized as follows:

the embodiment of the application provides a user information searching method, which is applied to enterprise instant messaging application and comprises the following steps:

responding to a first operation aiming at a user information searching function in enterprise instant messaging application, acquiring background searching authority information of the user and acquiring a searching keyword;

when determining that the user has the background search authority based on the background search authority information, responding to a second operation of executing search, and determining a target search result based on the search keyword;

and outputting the target search result.

The embodiment of the application provides a user information searching method, which comprises the following steps:

receiving a search request sent by a user terminal, and acquiring a search keyword and a user identifier carried in the search request, wherein the search request is sent when the user terminal determines that the user terminal has background search right;

determining an enterprise address book corresponding to the user identifier, and acquiring a candidate user identifier matched with the search keyword from the enterprise address book to obtain a candidate user list;

determining background search results based on the list of candidate users;

and sending a search response carrying the background search result to the user terminal.

In some embodiments, the method further comprises:

receiving a rule configuration request sent by a management terminal, wherein the rule configuration request carries a rule identifier and configuration information;

acquiring a to-be-configured restriction rule corresponding to the rule identifier;

determining a configuration value of a search mark field in the restriction rule to be matched based on the configuration information;

and determining the configuration value as the value of the search mark field.

An embodiment of the present application provides a user information search apparatus, including:

the system comprises a first acquisition module, a second acquisition module and a search module, wherein the first acquisition module is used for responding to first operation aiming at a user information search function in enterprise instant messaging application, acquiring background search authority information of the first acquisition module and acquiring search keywords;

the first determining module is used for responding to the second operation of executing the search and determining a target search result based on the search keyword when the background search permission information is determined to have the background search permission;

and the output module is used for outputting the target search result.

the first receiving module is used for receiving a search request sent by a user terminal and acquiring a search keyword and a user identifier carried in the search request, wherein the search request is sent when the user terminal determines that the user terminal has background search right;

the second acquisition module is used for determining the enterprise address book corresponding to the user identifier, and acquiring a candidate user identifier matched with the search keyword from the enterprise address book to obtain a candidate user list;

a second determining module for determining a background search result based on the candidate user list;

and the second sending module is used for sending the search response carrying the background search result to the user terminal.

An embodiment of the present application provides a user information search device, including:

a memory for storing executable instructions; a processor, configured to execute the executable instructions stored in the memory, to implement the method described above.

Embodiments of the present application provide a computer-readable storage medium storing executable instructions for causing a processor to implement the above-mentioned method when executed.

The embodiment of the application has the following beneficial effects:

when a user triggers a first operation of searching user information in an enterprise instant messaging application through a user terminal, the user terminal determines that the user terminal has background searching authority by acquiring background searching authority information of the user terminal, and determines a target searching result based on a searching keyword after acquiring the searching keyword and responding to a second operation of executing searching, and then outputs the target searching result.

Drawings

Fig. 1 is a schematic structural diagram of a user information search system according to an embodiment of the present application;

fig. 2 is a schematic structural diagram of a user terminal 100 according to an embodiment of the present application;

fig. 3 is a schematic flow chart of an implementation of a user information search method according to an embodiment of the present application;

FIG. 4 is a schematic diagram illustrating an implementation flow of determining a target search result according to an embodiment of the present application;

fig. 5A is a schematic flowchart of another implementation process of the user information search method according to the embodiment of the present application;

fig. 5B is a schematic view of an implementation flow for obtaining background search permission information of the user according to the embodiment of the present application;

fig. 6 is a schematic flow chart of another implementation of the user information search method according to the embodiment of the present application;

fig. 7 is a schematic interface diagram of configuring background search permissions by a management end according to an embodiment of the present application;

fig. 8 is a schematic view of an implementation flow of the terminal checking whether a user corresponding to the terminal has a background search right according to the embodiment of the present application.

Detailed Description

In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be described in further detail with reference to the attached drawings, the described embodiments should not be considered as limiting the present application, and all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the embodiments of the present application belong. The terminology used in the embodiments of the present application is for the purpose of describing the embodiments of the present application only and is not intended to be limiting of the present application.

Before further detailed description of the embodiments of the present application, terms and expressions referred to in the embodiments of the present application will be described, and the terms and expressions referred to in the embodiments of the present application will be used for the following explanation.

1) Restricted rules: and the rule is used for limiting a specific member and a team to view other people in the enterprise address book, and the limited member and the limited team cannot view other people through the enterprise address book. The restricted team can check each other inside, and a plurality of independent restricted rules can be configured in one enterprise address book.

2) Hiding the rule: in the enterprise address book, rules for hiding specific members and teams are used, and the hidden members and teams cannot be viewed by others through the enterprise address book.

3) Member (b): refers to a specific person or service account number in an enterprise address book

4) Team: refers to a certain department or label in the enterprise address book. A department may contain multiple sub-departments, and a tag may contain multiple members and multiple departments.

In order to better understand the user information search method provided in the embodiment of the present application, first, an implementation manner and existing disadvantages of user information search performed by a user under a limited rule in an enterprise instant messaging application in the related art are described:

in order to meet the cross-team communication demand of the user under the limited rule, one implementation mode of searching the user information by the user under the limited rule is that an unlimited white list is added on the basis of the limited rule, and members and sub-teams in the white list can externally search external members and carry out instant communication with the external members; another implementation manner is that, aiming at a specified limited rule, an intercommunicating list corresponding to the limited rule is added, and limited members can only view members in the intercommunicating list and carry out instant messaging with the members in the intercommunicating list.

For some specific members or sub-teams needing to communicate frequently across teams among the limited members, the influence of the limited rules can be avoided by adding a white list to the limited rules. However, this method only works for specific members, has low flexibility of configuration, high maintenance cost and high information security risk, and cannot thoroughly solve the problem of cross-team communication.

For limited members and teams, the intercommunication lists are set for specific external members needing frequent communication. The limited members can check the members in the designated range, the information security risk is slightly lower than that of adding a white list to the limited rule, but the problems of low flexibility of configuration and high maintenance cost still exist, and the problem of cross-team communication cannot be thoroughly solved.

Based on the address list in the enterprise instant messaging, on the basis of the limited rule, by adding a remote search function to the limited member, not only can the information of the address list be protected, but also the cross-team communication requirement of the limited member can be guaranteed.

An exemplary application of the user information search device provided in the embodiment of the present application is described below, and the user information search device provided in the embodiment of the present application may be implemented as any terminal having an on-screen display function, such as a notebook computer, a tablet computer, a desktop computer, a mobile device (e.g., a mobile phone, a portable music player, a personal digital assistant, a dedicated messaging device, a portable game device), an intelligent robot, or may be implemented as a server. Next, an exemplary application when the user information search device is implemented as a user terminal will be explained.

Referring to fig. 1, fig. 1 is a schematic structural diagram of a user information search system according to an embodiment of the present application. As shown in fig. 1, the user information search system includes a user terminal 100, a network 300, and a server 200. To support an exemplary application, the user terminal 100 is connected to the server 200 via a network 300, and the network 300 may be a wide area network or a local area network, or a combination thereof, and uses a wireless link to realize data transmission.

An application program is run on the user terminal 100, and a user can perform instant messaging within an enterprise through the application program run by the user terminal 100 (which may be a special enterprise instant messaging application program or a browser application program, and logs in a web version instant messaging application through the browser application program). When the user needs to inquire the user information of other users in the enterprise, the user can communicate with other users in an instant mode or in other modes. In this embodiment of the application, when a user queries user information of other users through the user terminal 100, the user terminal may first obtain background search permission information of the user terminal from the server 200, and when determining that the user terminal has background search permission, the user terminal 100 sends a search request to the server 200 after obtaining a search keyword input by the user, so as to request user information corresponding to the search keyword. After receiving the search request, the server 200 performs user information query based on the search keyword, after obtaining a candidate user list through preliminary query, removes users hitting the hidden rule from the candidate user list to obtain a final user list, supplements the key information, and returns a search result to the user terminal 100. After receiving the search result, the user terminal 100 displays the search result, and performs information viewing or instant messaging based on the user list in the search result.

Referring to fig. 2, fig. 2 is a schematic structural diagram of a user terminal 100 according to an embodiment of the present application, where the user terminal 100 shown in fig. 2 includes: at least one processor 110, memory 150, at least one network interface 120, and a user interface 130. The various components in the user terminal 100 are coupled together by a bus system 140. It is understood that the bus system 140 is used to enable connected communication between these components. The bus system 140 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, however, the various buses are labeled as bus system 140 in fig. 2.

The Processor 110 may be an integrated circuit chip having Signal processing capabilities, such as a general purpose Processor, a Digital Signal Processor (DSP), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like, wherein the general purpose Processor may be a microprocessor or any conventional Processor, or the like.

The user interface 130 includes one or more output devices 131, including one or more speakers and/or one or more visual display screens, that enable the presentation of media content. The user interface 130 also includes one or more input devices 132 including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

The memory 150 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid state memory, hard disk drives, optical disk drives, and the like. Memory 150 optionally includes one or more storage devices physically located remotely from processor 110.

The memory 150 includes volatile memory or nonvolatile memory, and may include both volatile and nonvolatile memory. The nonvolatile memory may be a Read Only Memory (ROM), and the volatile memory may be a Random Access Memory (RAM). The memory 150 described in embodiments herein is intended to comprise any suitable type of memory.

In some embodiments, memory 150 is capable of storing data to support various operations, examples of which include programs, modules, and data structures, or subsets or supersets thereof, as exemplified below.

An operating system 151 including system programs for processing various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks;

a network communication module 152 for communicating to other computing devices via one or more (wired or wireless) network interfaces 120, exemplary network interfaces 120 including: bluetooth, wireless compatibility authentication (WiFi), and Universal Serial Bus (USB), etc.;

an input processing module 153 for detecting one or more user inputs or interactions from one of the one or more input devices 132 and translating the detected inputs or interactions.

In some embodiments, the apparatus provided in the embodiments of the present application may be implemented in software, and fig. 2 shows a user information search apparatus 154 stored in the memory 150, where the user information search apparatus 154 may be a user information search apparatus in the user terminal 100, and may be software in the form of programs and plug-ins, and includes the following software modules: the first obtaining module 1541, the first determining module 1542 and the output module 1543 are logical and thus may be arbitrarily combined or further divided according to the functions implemented. The functions of the respective modules will be explained below.

In other embodiments, the apparatus provided in the embodiments of the present Application may be implemented in hardware, and for example, the apparatus provided in the embodiments of the present Application may be a processor in the form of a hardware decoding processor, which is programmed to execute the image processing method provided in the embodiments of the present Application, for example, the processor in the form of the hardware decoding processor may be one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), Complex Programmable Logic Devices (CPLDs), Field Programmable Gate Arrays (FPGAs), or other electronic components.

The user information search method provided by the embodiment of the present application will be described below with reference to an exemplary application and implementation of the user terminal 100 provided by the embodiment of the present application. Referring to fig. 3, fig. 3 is a schematic flow chart of an implementation of a user information search method provided in the embodiment of the present application, and will be described with reference to the steps shown in fig. 3.

Step S101, responding to the first operation aiming at the user information searching function in the enterprise instant communication application, obtaining self background searching authority information and obtaining searching keywords.

Here, the first operation may be an operation of the user clicking or touching a search control in a message interface in the enterprise instant messaging application, or an operation of the user clicking or touching a search control in an address book interface in the enterprise instant messaging application.

When the self background search permission information is obtained, a permission query request can be sent to the server, and then the server is requested to query the self background search permission information; the user terminal can also acquire the background search permission information of the user terminal from the local storage space. Whether the user has the background searching authority can be determined through the background authority information.

In the embodiment of the application, in response to the first operation, the user terminal presents a search interface, the search interface at least comprises an input box for inputting search characters, and the search keywords can be determined by acquiring the characters input through the input box. The search key may be a name, a phone number.

And S102, when determining that the user has the background search authority based on the background search authority information, responding to the second operation of executing the search, and determining a target search result based on the search keyword.

Here, the second operation may be an operation of clicking the search control after the user inputs the search keyword, and the second operation may also be an operation of inputting the search keyword by the user. In some embodiments, the second operation may also be a selection operation of the user based on the fuzzy search result after the user inputs the search keyword, performs the fuzzy search based on the search keyword, and outputs the fuzzy search result in the search interface.

When the second operation is an operation of clicking or touching the search control, in step S102, when the second operation is implemented, the user terminal may send a search request to the server in response to the second operation, where the search request carries the search keyword, the search request is used to request the server to obtain user information based on the search keyword, and the server returns a background search result to the user terminal after obtaining the user information. And when receiving a second operation of executing the search, the user terminal responds to the second operation, performs local search simultaneously, obtains a local search result, and finally determines a target search result based on the background search result and the local search result.

When the second operation is an operation of inputting a search keyword by a user, automatic search can be performed after the search keyword is acquired, and a target search result is obtained through the automatic search. In actual implementation, when automatic search is performed, the user terminal may perform local search and perform background search at the same time, so as to obtain a target search result.

And when the second operation is the selection operation of the user based on the fuzzy search result, determining the user identification selected by the second operation, and determining the user information corresponding to the selected user identification as the target search result in response to the second operation.

Step S103, outputting the target search result.

Here, when the user terminal outputs the target search result, the user identifier (which may include a user name and an avatar) in the target search result may be output, and the user identifier is an operable control, for example, when a certain user identifier is clicked, user information corresponding to the user identifier may be output, and when the target identifier is double-clicked, an interface for performing instant messaging with the user corresponding to the user identifier may be output.

In the user information searching method provided by the embodiment of the application, when a user triggers a first operation of user information searching in an enterprise instant messaging application through a user terminal, the user terminal determines that the user terminal has background searching authority by acquiring background searching authority information of the user terminal, sends a searching request to a server after acquiring a searching keyword, determines a target searching result to be output and displayed based on the background searching result after receiving the background searching result sent by the server, and further outputs the target searching result.

Because the proportion of users with background search permission is low, if the background search permission check is triggered when the full amount of users activate the search input box, the check request magnitude is very large, so in some embodiments, before obtaining the background search permission information of the user terminal, the user terminal may further perform the following steps:

and S001, acquiring enterprise configuration information.

Here, the enterprise configuration information may include a search flag bit, where the search flag bit is capable of indicating whether the enterprise address book includes a user with background search authority.

Step S002, determining whether the enterprise address book includes a user with background search permission based on the enterprise configuration information.

Here, when the step S002 is implemented, it may be determined whether the enterprise address book includes a user having a background search right by determining whether the search flag bit is set, where when the search flag bit is set (for example, may be set to 1), it indicates that the enterprise address book includes a user having a background search right; when the search flag bit is not set (for example, when the search flag bit is not set, the search flag is 0), it indicates that the enterprise address book does not include the user with the background search right.

In the embodiment of the application, when the enterprise address book comprises a user with background searching authority, the step of acquiring background searching authority information of the user corresponding to the user terminal is executed; when the enterprise address book does not include the user with the background search authority, it is indicated that all the users in the enterprise address book do not have the background search authority, local search can be directly performed without acquiring background search authority information of a certain specific user from a server, so that the number of times of requests for inquiring the background search authority can be greatly reduced, and the information search efficiency is improved.

In some embodiments, the "acquiring own background search right information" in step S101 may be implemented by steps S1011 to S1016 described below, and the steps are explained below.

In step S1011, the historical time at which the background search permission information of the user was obtained last time is obtained.

In step S1012, the interval duration between the history time and the current time is determined.

Here, assuming that the historical time is 17:40:00 on 5/17/2020 and the current time is 17:50:00 on 5/17/2020, the time interval is 10 minutes.

Step S1013, it is determined whether the interval duration is greater than a preset duration threshold.

In this embodiment of the application, after obtaining the background search permission information from the server, the user terminal may perform caching for a certain duration (i.e., a preset duration threshold), and delete the background search information when the duration threshold is reached, so that when the interval duration is greater than the duration threshold, it indicates that the user terminal has deleted the background search permission information, and then step S1014 is performed; when the interval duration is less than or equal to the duration threshold, it indicates that the background search permission information is not deleted, and then the process proceeds to step S1016.

Step S1014, sends the authority inquiry request to the server.

Here, the permission query request carries a user identifier corresponding to the user terminal.

Step S1015, receives the permission query response sent by the server, and obtains the background search permission information carried in the permission query response.

Step S1016, obtaining the background search permission information from the local storage space.

Because the user may frequently activate the input box in a short time and the background search permission information of the user is not frequently updated, in the embodiment where the steps S1011 to S1016 are performed, the result cache (cache) of the preset duration threshold is added to the user permission query request, and thus, when the user frequently performs the search in a short time, the user does not need to acquire the background permission information of the user from the server every time, and not only can the number of times of sending the permission query request to the server be reduced, but also the processing amount of the server can be reduced, and the efficiency of acquiring the background search permission can be improved.

In some embodiments, after the user terminal receives the first operation, in response to the first operation, a search interface is presented, where the search interface includes an input box for inputting a search keyword, and correspondingly, "obtaining the search keyword" in step S101 may be implemented by:

in step S1017, in response to an input operation received through the search interface, an input character is determined.

Here, the input operation may be a character input operation, and may also be a voice input operation, and when the input operation is a character input operation, an input character may be directly determined through the character input operation; when the input operation is a voice input operation, the voice information can be converted into characters after the input voice information is acquired, and the input characters can be obtained.

In step S1018, when the input character satisfies a preset keyword condition, the input character is determined as a search keyword.

Here, since the search itself increases the risk of information leakage of the corporate directory user, a keyword condition needs to be set to prevent the user from searching for a large number of matching users through simple characters. In the embodiment of the present application, the condition that the keyword may be set includes: when the input characters are numbers, the number of the numbers included in the input characters is not less than a first number threshold; when the input character is a Chinese character, the characters included in the input character must not be less than the second number threshold and must not be greater than the third number threshold. For example, when a number is entered when searching using a mobile phone number or a job number, the first number threshold may be defined as 6, i.e., the search may be performed only when a number greater than or equal to six is entered. When searching by using names, the second number threshold value can be limited to be 2, the third number threshold value can be limited to be 4, namely, the searching can be executed only when 2 to 4 Chinese characters are input, so that the problem that a large number of users are matched by inputting only one surname or one first name, and information leakage is caused is avoided.

In some embodiments, when the second operation is an operation of clicking or touching the search control after the search keyword is acquired, step S102 shown in fig. 3 may be implemented through steps S1021 to S1024, and fig. 4 is an implementation flow diagram of determining a target search result provided in the embodiment of the present application, and each step is described below with reference to fig. 4.

And step S1021, when determining that the self has the background searching authority based on the background searching authority information, responding to the second operation of executing the search, and sending a searching request to the server.

Here, the search request carries the search keyword.

In some embodiments, after receiving the search request, the server determines a candidate user identifier matching the search keyword to obtain a candidate user list, removes a user identifier set as a user identifier that cannot be searched by another person from the candidate user list to obtain a second user list, obtains user information corresponding to each user identifier in the second user list, for example, a mobile phone number, a mailbox address, team information, and the like, and determines the second user list and the corresponding user information as background search results to be sent to the user terminal.

Step S1022, the background search result sent by the server is received.

In step S1023, a search is performed in the local storage space based on the search keyword, and a local search result is obtained.

Here, the local search result at least includes a first user list, and when the user information matching with the search keyword is not searched, the first user list is empty; when the user information matched with the search keyword is searched, the first user list is not empty, and the first user list comprises user identifications at the moment, wherein the user identifications can comprise user names and can also comprise user head portraits. When the first user list is not empty, the local search result further includes user information corresponding to each user identifier included in the searched first user list, in addition to the first user list.

Step S1024, determining a target search result based on the background search result and the local search result.

Here, since the local search result includes the first user list and the background search result includes the second user list, step S1024 may be implemented by the following steps:

step S241, performing data fusion on the first user list and the second user list to obtain a target user list.

Here, when step S241 is implemented, when the same user identifier exists in the first user list and the second user list, the same user identifier in the first user list may be retained, and the same user identifier in the second user list may be deleted; or the same user identifier in the second user list may be retained, and the same user identifier in the first user list may be deleted.

In step S242, the user information of each target user included in the target user list is acquired.

Here, the user information of each target user in the target list from the second user list may be obtained from a background search result returned by the server, and the user information of each target user in the target list from the first list may be obtained from the local storage space.

In step S243, the target user list and the user information are determined as target search results.

In the embodiment of the present application, step S241 may be implemented by the following steps:

step S2411, determining whether the first user list and the second user list include the same user identifier.

In implementation, each first user identifier included in the first user list may be determined as a first set, and each second user identifier included in the second user list may be determined as a second set, in implementation, in step S311, an intersection of the first set and the second set may be determined, and when the intersection is not null, it is determined that the first user list and the second user list include the same user identifier, and an element included in the intersection is the same user identifier; when the intersection is empty, it is determined that the first user list and the second user list do not include the same user identification.

Here, when the first user list and the second user list include the same user identifier, go to step S2412; when the first user list and the second user list do not include the same user identifier, the process proceeds to step S2414.

Step S2412, deleting the same user identifier from the second user list, so as to obtain a processed second user list.

Here, it is assumed that the first user list includes a user a, a user B, a user E, and a user F, the second user list includes a user a, a user B, a user C, and a user D, and the same user identifier is the user a and the user B, and the processed second user list includes the user C and the user D after deleting the same user identifier from the second user list.

Step S2413, merging the first user list and the processed second user list to obtain a target user list.

And taking bearing on the example, merging the first user list and the processed second user list, and obtaining a target user list comprising a user A, a user B, a user C, a user D, a user E and a user F.

Step S2414, directly merging the first user list and the second user list to obtain a target user list.

Here, it is assumed that the first user list includes user a and user B, and the second user list includes user C and user D, and at this time, since the same user identifier does not exist between the two, the two are directly merged, and the obtained target user list includes user a, user B, user C, and user D.

In some embodiments, when step S241 is implemented, step S2412 and step S2413 may not be executed after step S2411, but the following steps are executed:

step S2412', delete the same user id from the first user list, so as to obtain a processed first user list.

Step S2413', merging the processed first user list and the second user list to obtain a target user list.

That is, when the same user identifier exists in the first user list and the second user list, the same user identifier in the first user list may be retained, and the same user identifier in the second user list may be deleted; since the user information stored in the server is often the latest, when the same user identifier exists in the first user list and the second user list, the same user identifier in the second user list may be retained, and the same user identifier in the first user list may be deleted.

As the above embodiment is adopted, outputting the target search result at least includes outputting a target user list, and correspondingly, after step S104, the following steps may be further performed to perform user information viewing:

step S105A, in response to the information display operation for the first target user, acquires the user information of the first target user, and presents the user information of the first target user.

Here, what is actually output by the output target user list is each user identifier in the target user list, and each user identifier corresponds to an operable control, and a certain operation instruction can be triggered by clicking or touching the user identifier, for example, an operation instruction for clicking or single-touch the user identifier can trigger user information display; the double-click or double-touch user identification can trigger an operation instruction of instant messaging; the function list can be displayed by long pressing the user identification or right clicking the user identification, and comprises the steps of displaying user information, carrying out instant messaging, checking friend circles and the like.

In this embodiment of the application, the first target user is a user corresponding to a user identifier included in the target user list. The information display operation may be an operation, for example, may be a single click or a single touch of the user identifier; or a series of operations, such as long pressing or right-clicking the user identifier, and clicking or touch-controlling a function control for displaying user information.

Alternatively, after step S104, the following steps may be executed to perform instant messaging:

step S105B, in response to the communication operation of the instant communication with the second target user, presenting an instant communication interface.

The second target user is a user corresponding to the user identifier included in the target user list, and similar to the information display operation, the communication operation of the instant messaging may be one operation, for example, the user identifier may be double-clicked or double-touch; or a series of operations, for example, pressing the user identifier for a long time or right-clicking, and clicking or touching the function control of the instant messaging.

Based on the foregoing embodiment, an embodiment of the present application further provides a user information search method, which is applied to the system architecture shown in fig. 1, and fig. 5A is a schematic diagram of another implementation flow of the user information search method provided in the embodiment of the present application, as shown in fig. 5A, the method includes:

step S501, the user terminal responds to the starting operation of the enterprise instant messaging application and presents a message interface of the enterprise instant messaging application.

Here, the starting operation may be that the user clicks or touches an icon of the enterprise instant messaging application, or scans a two-dimensional code of the web page, which starts the enterprise instant messaging application.

Step S502, the user terminal responds to the first operation aiming at the user information searching function in the enterprise instant messaging application, and presents a searching interface.

Here, the first operation may be that the user clicks or touches a search control in the message interface, and may also be that the user clicks or touches a search control in the address book interface. And after receiving the first operation, the user terminal responds to the first operation and presents a search interface, wherein the search interface comprises an input box for inputting characters or voice.

Step S503, the user terminal acquires enterprise configuration information.

Here, the enterprise configuration information includes a search flag bit, which is used to represent whether the enterprise address book includes a user with a background search right, and when the search flag bit is set (for example, set to 1), it indicates that the enterprise address book includes the user with the background search right; and when the search mark bit is not set, indicating that the enterprise address book does not comprise the user with the background search authority. The search mark bit is determined by the server according to the value of the search mark field in the restriction rule corresponding to the enterprise, and when the search mark field of at least one restriction rule in a plurality of restriction rules corresponding to the enterprise takes a value as a preset value (for example, 1), the search mark bit in the enterprise configuration information is set; and if the values of the search mark fields in all the restriction rules corresponding to the enterprise are not preset values, the search mark bits in the enterprise configuration information are not set.

Step S504, the user terminal determines whether the enterprise address book includes the user with the background searching authority based on the enterprise configuration information.

Here, when it is determined that the enterprise address book includes the user having the background search authority, step S505 is entered; when it is determined that the enterprise address book includes the user with the background search right, the process proceeds to step S509.

Step S505, the user terminal obtains the background search permission information of itself.

Here, step S505 may be implemented by sending an authority query request to the server to obtain the background search authority information of itself, or may be implemented by obtaining the background search authority information from a storage space of itself.

In step S506, the user terminal acquires a search keyword in response to an input operation for the search interface.

Step S507, the user terminal determines whether the user terminal has the background searching authority or not based on the background searching authority information.

Here, when the user terminal determines that it has the background search right, the process proceeds to step S508; when the user terminal determines that it does not have the background search right, the process proceeds to step S509.

In step S508, the user terminal transmits a search request to the server in response to a second operation of performing the search.

Here, the search request carries the search keyword.

In step S509, the user terminal performs a search in the local storage space based on the search keyword in response to the second operation of performing the search, and obtains a local search result.

Here, when the preamble step of step S509 is step S508, step S510 is executed after step S509; when the preliminary step of step S509 is step S507 or step S504, after the local search result is obtained, the local search result is directly output, and the flow ends at this time.

At least a first list of users is included in the local search results.

Step S510, the server receives a search request sent by the user terminal, and obtains a search keyword and a user identifier carried in the search request.

Step S511, the server determines the enterprise address book corresponding to the user identifier, and obtains a candidate user identifier matching the search keyword from the enterprise address book, to obtain a candidate user list.

Here, step S511, when implemented, may be to determine, as the candidate user identifier, a user identifier corresponding to the user information in the enterprise address book that includes the search keyword.

In step S512, the server obtains a preset hidden rule.

Here, the hidden rule includes that the user and/or team cannot be searched by other users. The hidden rule corresponding to one enterprise may be one or more.

In step S513, the server deletes the candidate user identifier satisfying the hidden rule from the candidate user list, so as to obtain a second user list.

Here, in step S513, when the comparison is performed, the team information and the tag information of each candidate user identifier are obtained, each candidate set is determined according to each candidate user identifier and the corresponding team information and tag information, each candidate set is sequentially matched with each hidden rule, if at least one of the candidate user identifiers, the team information and the tag information in the candidate set exists in the hidden rule, it is determined that the candidate user identifier satisfies the hidden rule, the candidate user identifier is deleted from the candidate user list, and after all the candidate user identifiers are compared, the second user list is obtained.

In step S514, the server obtains the user information corresponding to each user identifier in the second user list.

Here, the user information may include information of name, phone, mailbox address, job number, department of the place, project group of the place, and the like.

In step S515, the server determines the second user list and the user information as background search results.

Step S516, the server sends a search response carrying the background search result to the user terminal.

And step S517, the user terminal performs data fusion on the local search result and the background search result to obtain a target search result.

Here, when the step S517 is implemented, first, the first user list included in the local search result and the second user list included in the background search result are merged, and only the same user identifier in one user list is reserved during merging, so as to obtain a target user list, and obtain user information corresponding to each user identifier in the target user list, thereby determining the target user list and the corresponding user information as the target search result.

In step S518, the user terminal outputs and displays the target search result.

In some embodiments, after the user terminal outputs the target search result, operations such as user information viewing, instant messaging with the target user in the target search result, and the like may be performed based on the user identifier included in the target search result.

In the user information searching method provided by the embodiment of the application, when a user terminal starts an enterprise instant messaging application and triggers a searching function, the user terminal firstly acquires enterprise configuration information to determine whether a user with background searching authority is included in an enterprise address book, when the enterprise address book does not include the user with the background searching authority, the user terminal is proved to have no background searching authority, only local searching is needed to be executed at the moment, when the enterprise address book includes the user with the background searching authority, the user terminal further acquires the background searching authority information of the user terminal, when the user terminal determines that the user terminal has the background searching authority, background searching and local searching are executed, and after a server receives a searching request sent by the user terminal, the user identifier which hits a hidden rule in a primarily obtained searching result is deleted, so that the hidden rule is ensured not to be damaged, thereby ensuring the information security of the hidden user; the user terminal performs data fusion after obtaining the local search result and the background search result to obtain a target search result and displays the target search result, so that the background search function of the user with the background search authority can be realized, and the information security of the hidden user can be protected.

In this embodiment of the present application, the server may update and configure its own restriction rule through the following steps:

step S401, receiving a rule configuration request sent by the management terminal.

Here, the rule configuration request carries a rule identifier and configuration information, where the configuration information at least includes configuration information of whether to allow viewing of other department members through searching, and in some embodiments, the configuration information further includes update information of a user identifier, team information, and tag information in the restriction rule.

Step S402, obtaining the restriction rule to be configured corresponding to the rule identifier.

Step S403, determining a configuration value of the search mark field in the restriction rule to be configured based on the configuration information.

Here, if the configuration information of whether to allow viewing of other department members through searching in the configuration information is to allow viewing of other part members through searching, the configuration value of the search identification field in the restriction rule to be configured is a preset value, for example, the configuration value is 1; if the configuration information of whether the other department members are allowed to be checked by searching is not allowed to be checked by searching, the configuration value of the search identification field in the to-be-configured restriction rule is not a preset value, for example, the configuration value may be 0 at this time.

Step S404, determine the configuration value as the value of the search mark field.

In some embodiments, after the restriction rule is configured in an updating manner, the enterprise configuration information can be determined based on the updated restriction rule, and when the enterprise configuration information changes, the updated enterprise configuration information is sent to the user terminal.

In some embodiments, step S505 "the user terminal acquires the authority information of its background" shown in fig. 5A may be implemented through steps S5051 to S50510, and fig. 5B is a schematic flow chart illustrating an implementation process for acquiring the background search authority information of its own provided in this embodiment of the application, and each step is described below with reference to fig. 5B.

In step S5051, the user terminal obtains the historical time when the user terminal obtained the background search permission information of the user terminal last time.

In step S5052, the user terminal determines whether the interval duration between the historical time and the current time is greater than a preset duration threshold.

Here, when the interval duration is greater than the preset duration threshold, the process proceeds to step S5053; when the interval duration is less than or equal to the duration threshold, the flow proceeds to step S50510.

In step S5053, the user terminal sends an authority query request to the server.

Here, the authority query request carries the user identifier corresponding to the user terminal.

In step S5054, the server obtains the user identifier carried in the permission query request.

In step S5055, the server determines the team information, tag information, and restriction rule set corresponding to the user identifier.

Here, the restriction rule set acquired in step S5055 is all the restriction rules under the enterprise. The team information corresponding to the user identifier may be a department where the user is located, and the tag information may include a project group where the user is currently located.

In step S5056, the server determines a target restriction rule set including at least one of user identification, team information, and tag information from the restriction rule set.

In step S5057, the server determines background search permission information based on the search flag field in the target restriction rule included in the target restriction rule set.

Here, when the step S5057 is implemented, when the search flag fields in all the target restriction rules are preset values, the background search permission information is determined that the user has the background search permission; and when the target restriction rule set is empty or the search mark in at least one target restriction rule in the target restriction rule set is not a preset value, determining background search permission information as that the user does not have background search permission.

Step S5058, the server sends the permission query response carrying the background search permission information to the user terminal.

Step S5059, the user terminal receives the permission query response sent by the server, and obtains the background search permission information carried in the permission query response.

In the embodiment of the application, after acquiring the background search permission information of the user terminal, the user terminal stores the background search permission information into a local storage space (which may be a cache space), starts a timer to start timing, and deletes the background search permission information after the timing duration of the timer reaches a preset duration threshold, so that not only can frequent search in a short time be avoided, but also the permission query of the server is required each time, deletion can be guaranteed after the duration threshold is reached, the local storage space is not occupied, and the timeliness and accuracy of the background search permission information acquired by the user terminal are guaranteed.

In step S50510, the user terminal obtains background search permission information of the user terminal from the local storage space.

Because the user may frequently activate the input box in a short time, and the background search permission information of the user is not frequently updated, in the embodiment of steps S5051 to S50510, when the user terminal acquires the background search permission of the user, the user terminal firstly confirms the interval duration of the last acquired background search permission from the current time, and when the interval duration is greater than the preset duration threshold, it indicates that the background search permission information is not locally stored, at this time, an permission query request is sent to the server, and caching is performed for a certain duration after the background permission query information is acquired, when the interval duration is not greater than the duration threshold, it indicates that the background search permission information of the user is locally stored, and the background search permission information is locally acquired, so that when the user frequently searches in a short time, the user does not need to acquire the background permission information of the user from the server each time, the method and the device can reduce the number of times of sending the permission query request to the server, thereby reducing the processing amount of the server and improving the efficiency of obtaining the background search permission.

Next, an exemplary application of the embodiment of the present application in a practical application scenario will be described.

Fig. 6 is a schematic flowchart of another implementation flow of a user information search method provided in an embodiment of the present application, where the method is used in an enterprise instant messaging application, and as shown in fig. 6, the method includes:

in step S601, the management device sets a searchable flag.

Step S602, the management terminal device writes the option of 'other person capable of being searched' into the limited rule, and sends the limited rule added with the option of 'other person capable of being searched' to the address book rule service of the background.

Here, after receiving the limited rule added with the option of "being able to search for other people", the address book rule service in the background updates the limited rule stored in the address book rule service.

Step S603, before searching, the terminal checks whether the user corresponding to the terminal has the background search permission.

Here, the terminal search is a search-and-lose, i.e. every time the user types a new character, a round of search is reinitiated and the search results are refreshed. Considering that most users cannot configure remote search actually, in order to avoid generating a large number of background search calls, the background search permission of the user is checked first before initiating search. When the method is implemented, the user terminal sends a request message for checking the search permission to a background address book rule server to request the address book rule server to confirm whether the user corresponding to the user terminal has the background search permission.

In some embodiments, after receiving the request message for checking the search permission, the address book rule service queries based on the self-stored limited rule of the enterprise address book to obtain a query result, and returns the query result to the terminal.

And step S604, when the terminal determines that the terminal has the background search right, executing remote search.

In the embodiment of the application, after a user with a background search right inputs search characters in an input box, a terminal sends a search request to a background search service, wherein the search request carries the search characters input by the user and can be searched locally at the same time.

And step S605, searching an initial user list with matched mobile phone numbers, user names and the like in the enterprise address list by the background search service according to the search characters in the search request.

Here, since the search itself increases the risk of information leakage of the enterprise address book user, the matching manner of the search may be constrained according to the definition standard of the business-to-information security as follows:

1. limiting the range of fields that can be searched: it can be set which fields are allowed to be searched, such as mobile phone number, name;

2. and (3) limiting the matching degree of the search field: for example, the cell phone number field, if not constrained, may search for a large number of matching users, perhaps by number 1. Therefore, the security level can be restricted according to the service, for example, more than 6 digits are limited, and the search matching of the mobile phone number is triggered. The higher the search matching degree requirement, the higher the information security level.

Step S606, the search service obtains the hidden rule from the address book rule service.

In step S607, the address book rule service returns the hidden rule to the search service.

Step S608, the search service eliminates the user who hits the hidden rule in the initial user list based on the hidden rule to obtain a target user list, and determines a remote search result based on the target user list.

Here, for the user configured with the hidden rule, the information security is still ensured, and the user cannot be retrieved by background search. Therefore, after the initial user list is obtained by the search service, each user identifier in the initial user list is matched with the hidden rule to determine whether each user identifier hits the hidden rule, and when a certain user identifier hits the hidden rule, the user identifier is deleted from the initial user list. And removing all the user identifications hitting the hiding rules in the initial user list to obtain a target user list.

In the embodiment of the application, after the target user list is obtained, the search service searches the user information corresponding to each user identifier based on the user identifiers in the target user list, and returns the user information serving as the search result to the terminal. Here, the user information may include a user name, a phone, a mailbox address, and the like.

Step S609, the search service returns the remote search result to the terminal.

Step S610, after receiving the search result returned by the background search service, the terminal merges and displays the search result with the local search result.

Here, the terminal may merge with the local search result after receiving the search result returned by the background search service. If duplicate records occur, the remote search results are overwritten with the local search results.

In some embodiments, the terminal may view the user profile or initiate instant messaging through the returned background search results.

The restricted rule of the enterprise address book consists of a plurality of restricted sub-rules, wherein each sub-rule comprises a member (v id) list, a department (part) list and a tag (tag) list. The data structure is as follows:

CorpFilterMeta

{

a reclaimed agent 64 vid; // Member List

A reclaimed agent 64 part; // team List

A prioritized agent 64 tag; // Label List

}

CorpFilter

{

repeated CorpFilterMeta filter；

}

In the embodiment of the application, an extension flag bit is newly added in each restricted sub rule to identify whether the restricted member under the restricted sub rule can be compatible with other members in the enterprise through background search. At this time, the data structure of the sub-rule is as follows:

CorpFilterMeta

{

repeated uint64 vid；

repeated uint64 partyid；

repeated uint64 tagid；

the optional boot is _ allowed _ search; // newly added search identifier

}

In this embodiment of the application, in the implementation of step S601, when the management-side device sets a searchable flag, or when a new search identifier is added, the management-side device may set the new search identifier (is _ allowed _ search) in the restricted sub-rule to 1 by checking a button control 701 of "allowing the user to view other department members through search" in the operation interface shown in fig. 7, and when the button control 701 is checked.

Fig. 8 is a schematic view of an implementation process of a terminal checking whether a user corresponding to the terminal has a background search right according to an embodiment of the present application, where as shown in fig. 8, the process includes:

step S6031, pull enterprise configuration.

Since the percentage of users configuring the remote search is low, the magnitude of the check request will be large if the full number of users activate the search input box to trigger the check. Thus. The terminal can preferentially pull the enterprise configuration (corconf ig) to determine whether the enterprise address book includes the user with the background search authority.

In some embodiments, before step S6031, the address book rule server first checks whether there is at least one restricted rule in the enterprise-level restricted rules in which the is _ allowed _ search field is set, where as long as there is one restricted rule in which the is _ allowed _ search field is set, a search flag in the coproconfig is set, and the coproconfig is issued to the terminal. Therefore, the number of times of requests for inquiring search permission can be greatly reduced, and the inquiry requests can be reduced by more than 96% in actual operation discovery.

Step S6032, it is determined whether a search flag is included in the enterprise configuration.

Here, it is determined whether the enterprise configuration includes a search flag, and when the enterprise configuration is implemented, it is determined whether a search flag bit in the enterprise configuration, that is, the corrpconfig, is set, and when the search flag bit is set, it is considered that the enterprise configuration includes the search flag, and it is stated that the enterprise address book includes a user with a background search right, then step S6033 is performed; when the search mark is not set, the enterprise configuration is considered to not include the search mark, and all the users in the enterprise address book do not have the background search authority, and at the moment, the terminal can ignore the subsequent processes and does not perform background search.

Step S6033, determine whether the interval duration from the current time to the last time check search permission is greater than a preset duration threshold (1 min).

Because the user may frequently activate the input box in a short time and the enterprise configuration is not frequently updated, in the embodiment of the application, a result cache of a level of 1min is added to the user permission query request.

In the embodiment of the application, if the interval duration between the current time and the last search permission check is greater than 1min, the process goes to step S6034 to check whether the search permission exists; if the interval duration from the current time to the last search permission check is not more than 1min, the process proceeds to step S6035, and whether the user search flag is valid is checked, so that the permission check request can be further reduced by about 70%.

In step S6034, it is checked whether the user has a search right.

Here, step S6034 may be implemented by the terminal sending a request message to the address book rule service in the background to request the address book rule service to determine whether the user has the search right.

In the embodiment of the application, if the user is in a plurality of restricted sub-rules, the user can have the search right only after the search options of the plurality of sub-rules are all started. The implementation process of the address book rule service for determining whether the user has the search right may include:

step S341, when receiving the request message for performing the permission check on the user, first reading all the team lists (including the department list and the tag list) where the user vi d is located, and forming a set a formed by vid, partyid list, and tag list.

And step S342, calculating intersection sets of the set A and all restricted sub-rules in the enterprise address list one by one.

Here, if there is no intersection between the set a and the current restricted sub-rule, which indicates that the user has not hit the current restricted sub-rule, step S342 is entered again, and the intersection is calculated with the set a and the next restricted sub-rule; if the set A and the current restricted sub rule have intersection, the user hits the current restricted sub rule, and whether the is _ allowed _ search field in the current restricted sub rule is set is checked. If the is _ allowed _ search field in the current restricted sub-rule is set, then step S342 is entered again, and the intersection is calculated with the set a and the next restricted sub-rule; and if the is _ allowed _ search field in the current restricted sub rule is not set, directly obtaining the check result without the search permission.

Step S343, after the intersection is calculated between the set A and all the restricted sub-rules in the enterprise address list, if the intersection does not exist between the set A and all the restricted sub-rules, the checking result without the search permission is obtained, and if the is _ allowed _ search fields in all the restricted sub-rules which intersect with the set A are all set, the checking result with the search permission is obtained.

And after determining the checking result, the address book rule service returns the checking result to the terminal.

In step S6035, it is determined whether the user search flag is in effect.

Here, when step S6035 is implemented, it may be determined whether the user search flag is valid based on a check result returned by the address book rule service, and when the check result indicates that the user search flag is valid, step S604 is performed; when the check result is that no search authority exists, the user search mark is not valid, and the process is ended.

According to the user information searching method provided by the embodiment of the application, based on the enterprise address book, on the basis of the limited rule, the remote searching function is added to the limited member, so that only the limited user added with the remote searching function can inquire the user information of a cross-team through remote searching, not only can the address book information be protected, but also the cross-team communication requirement of the limited member can be guaranteed, and the communication efficiency is improved.

Continuing with the exemplary structure of the user information search device 154 implemented as a software module provided in the embodiments of the present application, in some embodiments, as shown in fig. 2, the software module stored in the user information search device 154 of the memory 150 may be a user information search device in the user terminal 100, including:

the first obtaining module 1541 is configured to, in response to a first operation directed to a user information search function in an enterprise instant messaging application, obtain background search permission information of the first obtaining module and obtain a search keyword;

a first determining module 1542, configured to, when it is determined that it has the background search right based on the background search right information, determine, in response to a second operation of performing a search, a target search result based on the search keyword;

the output module 1543 is configured to output the target search result.

In some embodiments, the apparatus further comprises:

the third acquisition module is used for acquiring enterprise configuration information;

and the third determining module is used for determining whether the enterprise address book comprises the user with the background searching authority or not based on the enterprise configuration information, wherein when the enterprise address book comprises the user with the background searching authority, the self background searching authority information is obtained.

In some embodiments, the first obtaining module is further configured to:

when the enterprise address book comprises users with background searching authority, acquiring the historical moment of acquiring the background searching authority information of the enterprise address book at the last time;

determining the interval duration between the historical time and the current time;

when the interval duration is greater than a preset duration threshold, sending an authority query request to a server;

and receiving the permission query response sent by the server, and acquiring background search permission information carried in the permission query response.

In some embodiments, the first obtaining module is further configured to:

and when the interval duration is less than or equal to the duration threshold, acquiring background search permission information of the local storage space.

In some embodiments, the first determining module 1542 is further configured to:

when determining that the server has the background search authority based on the background search authority information, responding to a second operation of executing search, and sending a search request to the server, wherein the search request carries the search keyword;

receiving a background search result sent by the server;

searching in a local storage space based on the search keywords to obtain a local search result;

determining a target search result based on the background search result and the local search result.

when the first user list and the second user list comprise the same user identification, deleting the same user identification from the second user list to obtain a processed second user list;

and merging the first user list and the processed second user list to obtain a target user list.

In some embodiments, the apparatus further comprises:

the first presenting module is used for responding to the first operation and presenting a search interface;

correspondingly, the first obtaining module is further configured to:

determining input characters in response to input operation received through the search interface;

and when the input character meets the preset keyword condition, determining the input character as a search keyword.

In some embodiments, the outputting the target search result includes outputting at least a list of target users, and correspondingly, the apparatus further includes:

the fourth acquisition module is used for responding to the information display operation aiming at the first target user, acquiring the user information of the first target user and presenting the user information of the first target user; alternatively, the first and second electrodes may be,

the second presentation module is used for responding to the communication operation of instant communication with a second target user and presenting an instant communication interface;

the first target user and the second target user are users corresponding to the user identification included in the target user list.

An embodiment of the present application further provides a user information search apparatus, which may be a software module stored in a memory of the server 200, and the user information search apparatus includes:

In some embodiments, the second determining module is further configured to:

acquiring a preset hidden rule, wherein the hidden rule comprises that a user and/or a team cannot be searched by other users;

deleting the candidate user identification meeting the hiding rule from the candidate user list to obtain a second user list;

acquiring user information corresponding to each user identifier in the second user list;

and determining the second user list and the user information as background search results.

In some embodiments, the apparatus further comprises:

the second receiving module is used for receiving the authority inquiry request sent by the user terminal and acquiring the user identifier carried in the authority inquiry request;

the fourth determining module is used for determining team information, label information and a restriction rule set corresponding to the user identifier;

a fifth determining module for determining a target restriction rule set including at least one of user identification, team information and tag information from the restriction rule set;

a sixth determining module, configured to determine background search permission information based on a search tag field in a target restriction rule included in the target restriction rule set;

and the third sending module is used for sending the permission query response carrying the background search permission information to the user terminal.

In some embodiments, the sixth determining module is further configured to:

when the search mark fields in all the target restriction rules are preset values, determining background search permission information as that the user has background search permission;

and when the target restriction rule set is empty or the search mark in at least one target restriction rule in the target restriction rule set is not a preset value, determining background search permission information as that the user does not have background search permission.

In some embodiments, the apparatus further comprises:

a third receiving module, configured to receive a rule configuration request sent by a management terminal, where the rule configuration request carries a rule identifier and configuration information;

a fifth obtaining module, configured to obtain a restriction rule to be provisioned corresponding to the rule identifier;

a seventh determining module, configured to determine, based on the configuration information, a configuration value of a search flag field in the restriction rule to be configured;

and an eighth determining module, configured to determine the configuration value as a value of the search flag field.

It should be noted that the description of the apparatus in the embodiment of the present application is similar to the description of the method embodiment, and has similar beneficial effects to the method embodiment, and therefore, the description is not repeated. For technical details not disclosed in the embodiments of the apparatus, reference is made to the description of the embodiments of the method of the present application for understanding.

Embodiments of the present application provide a storage medium having stored therein executable instructions, which when executed by a processor, will cause the processor to perform the methods provided by embodiments of the present application, for example, the methods as illustrated in fig. 3, fig. 4, fig. 5A, fig. 5B and fig. 6 and fig. 8.

In some embodiments, the storage medium may be a computer-readable storage medium, such as a Ferroelectric Random Access Memory (FRAM), a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read Only Memory (EPROM), a charged Erasable Programmable Read Only Memory (EEPROM), a flash Memory, a magnetic surface Memory, an optical disc, or a Compact disc Read Only Memory (CD-ROM), and the like; or may be various devices including one or any combination of the above memories.

In some embodiments, executable instructions may be written in any form of programming language (including compiled or interpreted languages), in the form of programs, software modules, scripts or code, and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

By way of example, executable instructions may correspond, but do not necessarily have to correspond, to files in a file system, and may be stored in a portion of a file that holds other programs or data, such as in one or more scripts in a hypertext Markup Language (H TML) document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). By way of example, executable instructions may be deployed to be executed on one computing device or on multiple computing devices at one site or distributed across multiple sites and interconnected by a communication network.

The above description is only an example of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, and improvement made within the spirit and scope of the present application are included in the protection scope of the present application.

Claims

1. A user information search method is applied to enterprise instant messaging application and is characterized by comprising the following steps:

and outputting the target search result.

2. The method as claimed in claim 1, wherein before obtaining the background search permission information of itself, the method further comprises:

acquiring enterprise configuration information;

and determining whether the enterprise address book comprises users with background searching authority or not based on the enterprise configuration information, wherein when the enterprise address book comprises the users with the background searching authority, the self background searching authority information is obtained.

3. The method of claim 2, wherein the obtaining of the background search permission information of the user comprises:

acquiring the historical moment of acquiring the background search permission information of the user at the last time;

4. The method as claimed in claim 1, wherein when determining that the search apparatus has the background search right based on the background search right information, determining a target search result based on the search keyword in response to a second operation of performing the search comprises:

receiving a background search result sent by the server;

5. The method of claim 4, wherein the local search result comprises at least a first user list, the background search result comprises a second user list, and correspondingly, the determining the target search result based on the background search result and the local search result comprises:

performing data fusion on the first user list and the second user list to obtain a target user list;

acquiring user information of each target user in the target user list;

and determining the target user list and the user information as target search results.

6. The method according to any one of claims 1 to 5, further comprising:

presenting a search interface in response to the first operation;

correspondingly, the obtaining of the search keyword includes:

and when the input characters meet a preset keyword condition, determining the input characters as search keywords.

7. The method of claims 1-5, wherein the outputting the target search result comprises outputting at least a list of target users, and correspondingly, the method further comprises:

responding to information display operation aiming at a first target user, acquiring user information of the first target user, and presenting the user information of the first target user; alternatively, the first and second electrodes may be,

responding to the communication operation of instant communication with a second target user, and presenting an instant communication interface;

8. A user information search method, characterized in that the method comprises:

determining background search results based on the list of candidate users;

9. The method of claim 8, wherein determining background search results based on the list of candidate users comprises:

10. The method of claim 8, further comprising:

receiving an authority inquiry request sent by a user terminal, and acquiring a user identifier carried in the authority inquiry request;

determining team information, label information and a restriction rule set corresponding to the user identification;

determining a target restriction rule set including at least one of user identification, team information and tag information from the restriction rule set;

determining background search permission information based on a search mark field in a target restriction rule included in the target restriction rule set;

and sending the permission query response carrying the background search permission information to the user terminal.

11. The method of claim 10, wherein determining background search permission information based on a search tag field in a target restriction rule included in the set of target restriction rules comprises:

and when the target restriction rule set is empty or a search mark in at least one target restriction rule in the target restriction rule set is not a preset value, determining background search permission information as that the user does not have background search permission.

12. A user information search apparatus, comprising:

the first determination module is used for responding to a second operation of executing search and determining a target search result based on the search keyword when determining that the first determination module has background search authority based on the background search authority information;

and the output module is used for outputting the target search result.

13. A user information search apparatus, comprising:

the second acquisition module is used for determining an enterprise address book corresponding to the user identifier, and acquiring a candidate user identifier matched with the search keyword from the enterprise address book to obtain a candidate user list;

14. A user information search apparatus characterized by comprising:

a memory for storing executable instructions; a processor for implementing the method of any one of claims 1 to 7 or claims 8 to 11 when executing executable instructions stored in the memory.

15. A computer-readable storage medium having stored thereon executable instructions for causing a processor, when executing, to implement the method of any one of claims 1 to 7 or claims 8-11.