A method, device, equipment and readable storage medium for querying user profiles

Abstract

The embodiments of the present application disclose a method, apparatus, device, and readable storage medium for querying user data. When receiving a user data query request sent by a terminal, the embodiments of the present application can obtain a set of user data identifiers corresponding to the target user. The set of user data identifiers includes the user data identifiers that the target user has in multiple scenarios. The user data query request indicates the target scenario of the user data to be queried. Based on the target scenario, feature fusion is performed on the user data identifiers in each scenario in the set of user data identifiers to obtain target feature information corresponding to the target scenario. The target feature information is fused with the reference feature information corresponding to the target scenario to obtain the fused feature information. According to the fused feature information, the target user data identifier corresponding to the target scenario is determined from the set of user data identifiers. The user data information corresponding to the target user data identifier is sent to the terminal. This solution can improve the flexibility of querying user data.

Description

Technical Field

[0001] The present invention relates to the field of communication technologies, and particularly to a method, device, equipment and readable storage medium for querying user information. Background Art

[0002] Currently, the display of user information is involved in many places in community-based clients, such as personal home pages, news lists, welfare centers, comment lists, friend lists and other scenarios. Different scenarios have different display requirements for the display of user information. Detailed user information generally includes the following: user account, community nickname, community image, gender, community level, community medal, game nickname, game rank (level), game online status, game image, etc. For such a large amount of user information and so many usage scenarios, it is particularly urgent to flexibly and effectively process the query of user information.

[0003] Currently, the common method is to provide different data scenario interfaces by the background server according to different user information display scenarios, so as to return different user information. For example, when a user queries the user information in the personal home page scenario, the background server returns the user information included in the personal home page to the client to which the user belongs; when the user queries the information in the comment list scenario, the background server then returns the user information in the comment list scenario to the client, and so on.

[0004] In the process of researching and practicing the prior art, the inventors of the present invention found that although the prior art can support different displays of user information in different scenarios, each scenario needs to be developed. If a function is added or taken offline, development needs to be carried out again, and it is difficult to have the flexibility to query user information. Summary of the Invention

[0005] Embodiments of the present application provide a method, device, equipment and readable storage medium for querying user information, which can improve the flexibility of querying user information.

[0006] Embodiments of the present application provide a method for querying user information, including:

[0007] When receiving a user information query request sent by a terminal, obtaining a set of user information identifiers corresponding to a target user, where the set of user information identifiers includes user information identifiers of the target user in multiple scenarios, and the user information query request indicates a target scenario for which the user information needs to be queried;

[0008] Performing feature fusion on the user information identifiers in each scenario in the set of user information identifiers based on the target scenario to obtain target feature information corresponding to the target scenario;

[0009] Fuse the target feature information with the reference feature information corresponding to the target scenario to obtain the fused feature information;

[0010] Determine the target user profile identifier corresponding to the target scenario from the user profile identifier set according to the fused feature information;

[0011] Send the user profile information corresponding to the target user profile identifier to the terminal.

[0012] Correspondingly, an embodiment of the present application further provides a user profile query device, including:

[0013] An acquisition unit, configured to acquire a set of user profile identifiers corresponding to a target user when receiving a user profile query request sent by a terminal, where the set of user profile identifiers includes user profile identifiers of the target user in multiple scenarios, and the user profile query request indicates a target scenario for which user profile needs to be queried;

[0014] A feature fusion unit, configured to perform feature fusion on the user profile identifiers in each scenario in the user profile identifier set based on the target scenario to obtain target feature information corresponding to the target scenario;

[0015] A fusion unit, configured to fuse the target feature information with the reference feature information corresponding to the target scenario to obtain the fused feature information;

[0016] A determination unit, configured to determine the target user profile identifier corresponding to the target scenario from the user profile identifier set according to the fused feature information;

[0017] A sending unit, configured to send the user profile information corresponding to the target user profile identifier to the terminal.

[0018] In some embodiments, the feature fusion unit is configured to:

[0019] Determine candidate user profile identifiers corresponding to the target scenario from the user profile identifier set;

[0020] Perform feature representation on the candidate user profile identifiers in the user profile identifier set to obtain first feature information;

[0021] Perform feature representation on the non-candidate user profile identifiers in the user profile identifier set to obtain second feature information;

[0022] Fuse the first feature information with the second feature information to obtain the target feature information corresponding to the target scenario;

[0023] The determining unit is further configured to determine, according to the fused feature information, a target user profile identifier corresponding to the target scenario from the candidate user profile identifiers.

[0024] In some embodiments, the fusing unit is specifically configured to:

[0025] Perform a logical operation on the target feature information and the reference feature information corresponding to the target scenario to obtain the post-operation feature information;

[0026] Generate the fused feature information based on the post-operation feature information.

[0027] In some embodiments, the fused feature information includes at least one sub-feature information, and the determining unit includes:

[0028] An obtaining subunit, configured to obtain query characteristic information of each sub-feature information;

[0029] A feature determining subunit, configured to determine target queryable feature information from the at least one sub-feature information according to the query characteristic information;

[0030] An identifier determining subunit, configured to determine a target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the target queryable feature information.

[0031] In some embodiments, the sending unit includes:

[0032] A query subunit, configured to query user profile information corresponding to the target user profile identifier according to the target user profile identifier corresponding to the target scenario;

[0033] A sending subunit, configured to send the user profile information corresponding to the target user profile identifier to the terminal.

[0034] In some embodiments, the query subunit is specifically configured to:

[0035] Obtain a preset user profile database, where the preset user profile database includes user profile information corresponding to user profile identifiers;

[0036] Match the target user profile identifier with the user profile identifiers in the preset user profile database;

[0037] When the target user profile identifier is successfully matched with the user profile identifiers in the preset user profile database, extract the user profile information corresponding to the successfully matched user profile identifier from the preset user profile database to obtain the user profile information corresponding to the target user profile identifier.

[0038] In some embodiments, the user profile query device further includes:

[0039] A detection unit for detecting the user account of the requesting user to determine the login form of the requesting user;

[0040] The identification determination subunit is further configured to determine the target user profile identification corresponding to the target scenario from the candidate user profile identifications according to the login form of the requesting user and the target queryable feature information.

[0041] Correspondingly, the present application further provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the steps in any one of the user profile query methods provided by the embodiments of the present application are implemented.

[0042] In addition, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps in any one of the user profile query methods provided by the embodiments of the present application are implemented.

[0043] When receiving a user profile query request sent by a terminal, an embodiment of the present application can obtain a set of user profile identifications corresponding to a target user. The set of user profile identifications includes the user profile identifications that the target user has in multiple scenarios. The user profile query request indicates the target scenario of the user profile to be queried; perform feature fusion on the user profile identifications in each scenario in the set of user profile identifications based on the target scenario to obtain target feature information corresponding to the target scenario; fuse the target feature information with the reference feature information corresponding to the target scenario to obtain fused feature information; determine the target user profile identification corresponding to the target scenario from the set of user profile identifications according to the fused feature information; send the user profile information corresponding to the target user profile identification to the terminal. Since this solution can perform feature fusion on the user profile identifications that the target user has in multiple scenarios to obtain target feature information corresponding to the target scenario, and after fusing the target feature information and the reference feature information, determine the target user profile identification corresponding to the target scenario based on the obtained fused feature information, and then query the user profile information according to the target user profile identification, the flexibility of user profile query is greatly improved. Description of the Drawings

[0044] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the following drawings are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative efforts.

[0045] Figure 1a It is a schematic diagram of the scenario of the user information query method provided by an embodiment of the present application;

[0046] Figure 1b It is a schematic flow diagram of the user information query method provided by an embodiment of the present application;

[0047] Figure 2a It is another schematic flow diagram of the user information query method provided by an embodiment of the present application;

[0048] Figure 2b It is a schematic diagram of the "bit" storage of the reference feature information corresponding to the target scenario provided by an embodiment of the present application;

[0049] Figure 2c It is a schematic diagram of the system architecture of the user information query method provided by an embodiment of the present application;

[0050] Figure 2d It is a schematic processing flow diagram of the user information query method provided by an embodiment of the present application;

[0051] Figure 2e It is a schematic diagram of the display of the user information in the comment list scenario provided by an embodiment of the present application;

[0052] Figure 2f It is a schematic diagram of the structure of the blockchain provided by an embodiment of the present application;

[0053] Figure 2g It is another schematic diagram of the structure of the blockchain provided by an embodiment of the present application;

[0054] Figure 3a It is a schematic diagram of the structure of the user information query device provided by an embodiment of the present application;

[0055] Figure 3b It is another schematic diagram of the structure of the user information query device provided by an embodiment of the present application;

[0056] Figure 3c It is another schematic diagram of the structure of the user information query device provided by an embodiment of the present application;

[0057] Figure 3d It is another schematic diagram of the structure of the user information query device provided by an embodiment of the present application;

[0058] Figure 4 It is a schematic diagram of the structure of the computer device provided by an embodiment of the present application. Detailed implementation manners

[0059] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative efforts belong to the protection scope of the present invention.

[0060] The embodiments of the present application provide a user profile query method, device, computer device, and computer-readable storage medium. Specifically, the user profile query method in the embodiments of the present application can be executed by a computer device. Among them, the computer device can be a terminal or a server, etc. The terminal can be a mobile phone, a tablet computer, a laptop computer, a smart TV, a wearable smart device, a personal computer (PC), etc.; the server can be a single server or a server cluster composed of multiple servers.

[0061] For example, referring to Figure 1a , the user profile query system provided in the embodiments of the present application includes a terminal 10 and a server 11, etc.; the terminal 10 is connected to the server 11 through a network, for example, through a wired or wireless network connection, etc. Among them, the user profile query device is integrated in the terminal, for example, integrated in the terminal in the form of a client.

[0062] Among them, the terminal 10 can send a user profile query request to the server. The request indicates the target scenario of the user profile to be queried. When the server receives the user profile query request sent by the terminal, the terminal can also detect the user account of the requesting user to determine the login form of the requesting user, so that the server can obtain the set of user profile identifiers corresponding to the target user to be queried according to the user profile query request. Then, determine the target user profile identifier corresponding to the target scenario from the set of user profile identifiers, and return the user profile information corresponding to the target user profile identifier to the terminal for display. Among them, the target scenario can include: personal homepage, news list, welfare center, comment list, friend list, etc.; the login form can include the main state and the guest state, etc. Among them, the main state is to view one's own user profile, and the guest state is to view the user profiles of others; the set of user profile identifiers includes: user account, community nickname, community image, gender, community level, community medal, game nickname, game level, game online status, etc.

[0063] When receiving a user profile query request sent by a terminal, the server 11 can obtain a user profile identification set corresponding to the target user, where the user profile identification set includes user profile identifications of the target user in multiple scenarios, and the user profile query request indicates a target scenario of the user profile to be queried; based on the target scenario, feature fusion is performed on the user profile identifications in each scenario in the user profile identification set to obtain target feature information corresponding to the target scenario; the target feature information is fused with reference feature information corresponding to the target scenario to obtain fused feature information; based on the fused feature information, the target user profile identification corresponding to the target scenario is determined from the user profile identification set; and the user profile information corresponding to the target user profile identification is sent to the terminal.

[0064] It should be noted that the description order of the following embodiments is not intended to limit the preferred order of the embodiments.

[0065] An embodiment of the present application provides a user profile query method, which can be executed by a terminal or a server, or by both a terminal and a server. The embodiment of the present application takes the user profile query method executed by a server as an example for explanation.

[0066] like Figure 1b As shown, the specific process of the user information query method can be as follows:

[0067] 101. When a user profile query request sent by a terminal is received, a user profile identifier set corresponding to a target user is obtained, where the user profile identifier set includes user profile identifiers of the target user in multiple scenarios, and the user profile query request indicates a target scenario of the user profile to be queried.

[0068] The user profile includes the personal information of the target user to be queried, and the usage information of the target user on the community client, etc. The community client is a client that includes community functions, for example, it can be an instant messaging client, a game client, a music client, a video client, a news client, etc. The target user is the user whose user profile information is queried. For the convenience of description and distinction, in the embodiment of the present application, the user who initiates the user profile query request is referred to as the requesting user.

[0069] For example, taking a game client as an example, user information may include the user's gender, age, user account (ID, Identity document), community nickname, community image, community level, community medal, game nickname, game rank (i.e. game level), game online status, game image, and so on.

[0070] Among them, the user profile identifier is information used to identify different user profiles. This user profile identifier can be a number composed of characters such as numbers, letters, and underscores, or it can be a name taken according to the content of different user profiles. This name can be expressed in different language forms such as Chinese and English. For example, the "community nickname" is "Zhang San", the "community gender" is "male", and the "community level" is "Lv3", etc. Among them, the names "community nickname", "community gender", and "community level" are used to represent the user profile information "Zhang San", "male", and "Lv3" respectively.

[0071] The set of user profile identifiers includes the user profile identifiers that the target user has in multiple scenarios. For example, there are 3 usage scenarios for user profiles in a certain community client. Among them, in Scenario 1, the community nickname, community gender, and community level are displayed. In Scenario 2, only the community image is displayed. In Scenario 3, the user account and community medal are displayed. Then the set of user profile identifiers includes the community nickname, community gender, community level, community image, user account, and community medal, that is, the union of the user profile identifiers in the 3 scenarios is taken.

[0072] Among them, the scenario is the position where the user profile is displayed in the client, that is, the usage scenario of the user profile in the client. For example, the target scenario can include the personal homepage, news list, welfare center, comment list, friend list, and so on; the user profiles displayed in different scenarios are different. For example, the personal homepage can display all user profiles, and the comment list only displays some user profiles such as the community nickname, community image, community gender, community level, and game rank, and so on.

[0073] Among them, the user profile query request can be triggered by the requesting user through the terminal to which he belongs. For example, it can be triggered by clicking or swiping the scenario trigger key, user profile search trigger key in the community client, or an icon containing the user's community image or community nickname, and so on. When the terminal to which the requesting user belongs detects the user profile query request triggered by the requesting user for the target scenario, the user profile query request is sent to the server. When the server receives the user profile query request sent by the terminal, it obtains the user profile identifiers that the target user has in multiple scenarios.

[0074] 102. Perform feature fusion on the user profile identifiers in each scenario in the set of user profile identifiers based on the target scenario to obtain the target feature information corresponding to the target scenario. For example, specifically, it can be as follows:

[0075] Determine the candidate user profile identifiers corresponding to the target scenario from the set of user profile identifiers;

[0076] Perform feature representation on the candidate user profile identifiers in the set of user profile identifiers to obtain the first feature information;

[0077] Perform feature representation on the non-candidate user profile identifiers in the user profile identifier set to obtain second feature information;

[0078] Fuse the first feature information and the second feature information to obtain the target feature information corresponding to the target scenario;

[0079] At this time, the step of "determining the target user profile identifier corresponding to the target scenario from the user profile identifier set according to the fused feature information" may include: determining the target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the fused feature information.

[0080] Among them, one or more user profile identifiers included in the target scenario are the candidate user profile identifiers. In one embodiment, performing feature representation on the candidate user profile identifiers and non-candidate user profile identifiers in the user profile identifier set is to perform "bit" representation on each user profile identifier. Among them, for each user profile identifier in the candidate user profile identifiers, "1" can be used for representation; for each user profile identifier in the non-candidate user profile identifiers, "0" can be used for representation.

[0081] In one embodiment, there are multiple ways of fusion. For example, it can be represented by a string or in hexadecimal numbers, etc. To improve the scalability of user profile query, specifically, hexadecimal numbers can be used to represent the target feature information. That is, all the user profile identifiers in the user profile identifier set are arranged according to a preset rule, and all the arranged user profile identifiers are represented by "0" and "1", and then the digital sequence composed of "0" and "1" is represented by hexadecimal numbers, so as to obtain the target feature information corresponding to the target scenario. Among them, the preset rule can be set by the operation and maintenance personnel according to the actual application requirements.

[0082] For example, the user profile identifier set includes 6 user profile identifiers: user account, community nickname, community image, community gender, community level, and community medal. And the user profile identifiers used in scenario 1 (i.e., candidate user profile identifiers) are: user account, community nickname, community image. Then the target feature information corresponding to scenario 1 is: 111000, which is represented in hexadecimal as 38.

[0083] It should be noted that representing the user profile identifiers in the user identifier set by "0" and "1" adopts the idea of binary bit logic operation in the computer, that is, "1" represents the user profile identifier to be queried, and "0" represents the user profile identifier that does not need to be queried. Therefore, the candidate user profile identifiers in the target scenario are represented as "1", while the non-candidate user profile identifiers are represented as "0".

[0084] 103. Integrate the target feature information with the reference feature information corresponding to the target scenario to obtain the integrated feature information.

[0085] Among them, there are various integration methods. For example, the target feature information can be logically operated with the reference feature information corresponding to the target scenario, and the integrated feature information is generated according to the operation result. Specifically, the step of "integrating the target feature information with the reference feature information corresponding to the target scenario to obtain the integrated feature information" may include:

[0086] Logically operate the target feature information with the reference feature information corresponding to the target scenario to obtain the post-operation feature information;

[0087] Generate the integrated feature information based on the post-operation feature information.

[0088] Among them, the reference feature information corresponding to the target scenario can be pre-configured by the operation and maintenance personnel.

[0089] Among them, there are various logical operation methods. In one embodiment, in order to improve the flexibility and scalability of the system for querying user information and enhance the efficiency of user information query, specifically, the "AND" operation in logical operations can be used to integrate the target feature information with the reference feature information corresponding to the target scenario. The "AND" operation is a basic logical operation method in a computer, symbolically represented as "&". For the two data participating in the operation, the "AND" operation is performed bit by bit, and the operation rule is: 0&0 = 0; 0&1 = 0; 1&0 = 0; 1&1 = 1; that is, both bits are 1, and the result is 1, otherwise it is 0.

[0090] For example, the target feature information of scenario 1 is "111000", and the reference feature information corresponding to scenario 1 is "101000". After performing the "AND" operation on the target feature information and the reference feature information bit by bit, the post-operation feature information "101000" is obtained.

[0091] It should be noted that for the convenience of operation, the user profile identifiers represented by the feature information at the corresponding positions of the target feature information and the reference feature information corresponding to the target scenario need to correspond one by one. For example, the first digit "1" in the target feature information "111000" of scenario 1 and the reference feature information "101000" corresponding to scenario 1 should represent the same user profile identifier. For example, they both represent the "community nickname" in the user profile identifier set.

[0092] In the embodiments of the present application, each piece of data in the user profile is represented by a "bit". The client pulls different data according to different scenarios. When the value of the "bit" corresponding to the user profile identifier in the request to view is "1", it means that the user profile data is required; when the value is "0", it means that the user profile data is not required. In this way, very flexible data integration and packaging can be achieved, that is, assemble the data as needed, and there is no need for further development, testing, and release in the background. When the system request reaches the system threshold, the background can change the value of the "bit" corresponding to the configured user profile identifier (i.e., the reference feature information) to 0, so as to reduce data query processing and improve the overall system processing performance (that is, only return a fixed number of core data, such as community nickname, community image, user gender, and no longer process other user profile data), thereby improving the reliability of the system and the high availability of users.

[0093] 104. Determine the target user profile identifier corresponding to the target scenario from the set of user profile identifiers according to the fused feature information.

[0094] In one embodiment, the step of "determining the target user profile identifier corresponding to the target scenario from the set of user profile identifiers according to the fused feature information" may include: determining the target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the fused feature information.

[0095] Among them, the fused feature information includes at least one sub-feature information. Specifically, the step of "determining the target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the fused feature information" may include:

[0096] Obtain the query characteristic information of each sub-feature information;

[0097] Determine the target queryable feature information from at least one sub-feature information according to the query characteristic information;

[0098] Determine the target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the target queryable feature information.

[0099] Among them, the query characteristic information indicates whether a certain sub-feature information has the characteristic of being queryable. For example, the fused feature information is "101000", where "1" represents the queryable feature information and "0" represents the non-queryable feature information.

[0100] Among them, according to the target queryable feature information, the target user profile identifier corresponding to the target scenario is determined from the candidate user profile identifiers. For example, in the target feature information "111000", the sub-feature information with the first three digits being "1" respectively represents the candidate user profile identifiers (such as: user account, community nickname, community image). In the fused feature information "101000", the first and third digits represent the user profile identifiers corresponding to the queryable feature information (such as: user account, community image). Then, the target user profile identifiers corresponding to the target scenario can be determined from the candidate user profile identifiers as "user account" and "community image".

[0101] In the embodiments of the present application, the idea of obtaining the fused feature information by using the "AND" operation is as follows: When the feature information corresponding to a certain user profile identifier that the requesting user needs to query and the feature information corresponding to this user profile identifier defined in the background are both "1" at the same time, it means that this user profile identifier is the target user profile identifier corresponding to the target scenario, that is, it is used as the user profile identifier for finally obtaining the user profile information corresponding to this identifier from the database.

[0102] In one embodiment, the target user profile identifier corresponding to the target scenario can also be determined from the candidate user profile identifiers according to the account login form of the requesting user and the target queryable feature information. That is, before the step of "obtaining the set of user profile identifiers corresponding to the target user", it further includes:

[0103] Detect the user account of the requesting user to determine the login form of the requesting user;

[0104] At this time, the step of "determining the target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the target queryable feature information" may include:

[0105] Determine the target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the login form of the requesting user and the target queryable feature information.

[0106] Among them, the login form of the user account includes the main state and the guest state, etc. Among them, the main state is to view one's own user profile information, that is, the user account of the requesting user is the same as the user account of the target user. The guest state is to view the user profile information of others, that is, the user account of the requesting user is different from the user account of the target user. For the privacy protection of the personal information of the target user, the guest state will be restricted by preset permissions when viewing the user profile of the target user, and the user profile viewed is also relatively limited. For example, taking the user profile of "game online status" in the game client as an example, when the login form of the requesting user is the guest state, if the user profile information "game online status" included in the target scenario he requests to view is set to be private (that is, not visible to others), then the requesting user cannot view whether the target user is online.

[0107] 105. Send the user profile information corresponding to the target user profile identifier to the terminal. For example, specifically, it can be as follows:

[0108] Query the user profile information corresponding to the target user profile identifier according to the target user profile identifier corresponding to the target scenario;

[0109] Send the user profile information corresponding to the target user profile identifier to the terminal.

[0110] In an embodiment, the user profile information corresponding to the target user profile identifier can be queried from a preset user profile database according to the user profile identifier corresponding to the target scenario. Specifically, the step "Query the user profile information corresponding to the target user profile identifier according to the target user profile identifier corresponding to the target scenario" can include:

[0111] Obtain a preset user profile database, where the preset user profile database includes the user profile information corresponding to the user profile identifier;

[0112] Match the target user profile identifier with the user profile identifiers in the preset user profile database;

[0113] When the target user profile identifier matches successfully with the user profile identifiers in the preset user profile database, extract the user profile information corresponding to the successfully matched user profile identifier from the preset user profile database to obtain the user profile information corresponding to the target user profile identifier.

[0114] Send the user profile information corresponding to the target user profile identifier to the terminal so that the terminal can display the user profile information.

[0115] As can be seen from the above, in the embodiment of the present application, when receiving a user profile query request sent by a terminal, the user profile identification set corresponding to the target user can be obtained. The user profile identification set includes the user profile identifications that the target user has in multiple scenarios, and the user profile query request indicates the target scenario of the user profile to be queried. Feature fusion is performed on the user profile identifications in each scenario in the user profile identification set based on the target scenario to obtain the target feature information corresponding to the target scenario. The target feature information is fused with the reference feature information corresponding to the target scenario to obtain the fused feature information. According to the fused feature information, the target user profile identification corresponding to the target scenario is determined from the user profile identification set, and the user profile information corresponding to the target user profile identification is sent to the terminal. Since this solution can perform feature fusion on the user profile identification set that the target user has in multiple scenarios to obtain the target feature information corresponding to the target scenario, and fuse the target feature information and the reference feature information corresponding to the target scenario (the reference feature information can be flexibly configured), such as performing a logical "AND" operation, and determine the target user profile identification corresponding to the target scenario based on the obtained fused feature information (that is, determining the user profile identification with the "bit" data of "1" in the fused feature information as the target user profile identification), and then querying the user profile information according to the target user profile identification, the flexibility of user profile query is greatly improved.

[0116] The method described in the above embodiment will be further described in detail with examples below.

[0117] In this embodiment, a user profile query method is provided. This method can be executed by a terminal or a server, or jointly executed by a terminal and a server. This embodiment will be described by taking the method being executed by the server as an example.

[0118] As Figure 2a shown, the specific process of this user profile query method can be as follows:

[0119] 201. When the server receives a user profile query request sent by the terminal, obtain the user profile identification set corresponding to the target user. The user profile identification set includes the user profile identifications that the target user has in multiple scenarios, and the user profile query request indicates the target scenario of the user profile to be queried.

[0120] Among them, the user profile query request can be triggered by the requesting user through the terminal to which the user belongs. For example, it can be triggered by clicking or swiping the scenario trigger key, user profile search trigger key, or icon containing the community image or community nickname of the user in the community client, and so on. When the terminal to which the requesting user belongs detects the user profile query request triggered by the requesting user for the target scenario, the user profile query request is sent to the server. When the server receives the user profile query request sent by the terminal, it obtains the user profile identifiers of the target user in multiple scenarios in the client, that is, the user profile identifier set.

[0121] 202. The server performs feature fusion on the user profile identifiers in each scenario in the user profile identifier set based on the target scenario to obtain the target feature information corresponding to the target scenario.

[0122] For example, the server can specifically determine the candidate user profile identifiers corresponding to the target scenario from the user profile identifier set; perform feature representation on the candidate user profile identifiers in the user profile identifier set to obtain the first feature information; perform feature representation on the non-candidate user profile identifiers in the user profile identifier set to obtain the second feature information; fuse the first feature information and the second feature information to obtain the target feature information corresponding to the target scenario;

[0123] At this time, the step of "determining the target user profile identifier corresponding to the target scenario from the user profile identifier set according to the fused feature information" may include: determining the target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the fused feature information.

[0124] Among them, one or more user profile identifiers included in the target scenario are the candidate user profile identifiers. In one embodiment, performing feature representation on the candidate user profile identifiers and non-candidate user profile identifiers in the user profile identifier set means performing "bit" representation on each user profile identifier. Among them, for each user profile identifier in the candidate user profile identifiers, "1" can be used for representation; for each user profile identifier in the non-candidate user profile identifiers, "0" can be used for representation.

[0125] In one embodiment, there can be multiple ways of fusion. For example, it can be represented by a string or a hexadecimal number, etc. To improve the scalability of user profile query, specifically, the target feature information can be represented by a hexadecimal number. That is, all user profile identifiers in the user profile identifier set are arranged according to a preset rule, and all the arranged user profile identifiers are represented by "0" and "1". Then, the digital sequence composed of "0" and "1" is represented by a hexadecimal number, so as to obtain the target feature information corresponding to the target scenario. Among them, the preset rule can be set by the operation and maintenance personnel according to the actual application requirements.

[0126] For example, the user profile identifier set includes 6 user profile identifiers: user account, community nickname, community image, community gender, community level, and community medal. And the user profile identifiers used in Scenario 1 (i.e., candidate user profile identifiers) are: user account, community nickname, community image. Then, the target feature information corresponding to Scenario 1 is: 111000, which is represented as 38 in hexadecimal.

[0127] It should be noted that representing the user profile identifiers in the user identifier set by "0" and "1" adopts the idea of binary bit logical operation in the computer, that is, "1" represents the user profile identifier to be queried, and "0" represents the user profile identifier that does not need to be queried. Therefore, the candidate user profile identifiers in the target scenario are represented as "1", while the non-candidate user profile identifiers are represented as "0".

[0128] 203. The server fuses the target feature information with the reference feature information corresponding to the target scenario to obtain the fused feature information.

[0129] Among them, the reference feature information corresponding to the target scenario can be the feature information corresponding to the target scenario pre-configured and stored by the operation and maintenance personnel. See Figure 2b , which lists user profile identifiers such as community nickname, community image, community gender, community level, community medal, game nickname, game image, game rank, etc. Each user profile identifier is represented by a bit of data, with a value of "1" or "0". Scenario 1 means that all user profile information is required, so the "bit" corresponding to each user profile identifier is set to "1"; Scenario 2 means that game-related data is not required, so the "bits" of the user profile identifiers related to game data are all "0"; Scenario 3 means that only some user community profiles and game rank profiles are required. Similarly, a very large number of scenario data can be flexibly configured, which is beneficial to the expansion of system functions.

[0130] Among them, there can be multiple ways of logical operations. In one embodiment, in order to improve the flexibility and scalability of the system for querying user information and enhance the efficiency of user information query, specifically, the server can use the "AND" operation in logical operations to fuse the target feature information and the reference feature information corresponding to the target scenario. The "AND" operation is a basic logical operation method in a computer, symbolically represented as "&". For the two data participating in the operation, the "AND" operation is performed bit by bit in binary. The operation rule is: 0&0 = 0; 0&1 = 0; 1&0 = 0; 1&1 = 1; that is, only when both bits are 1, the result is 1, otherwise it is 0.

[0131] For example, the target feature information of scenario 1 is "111000", and the reference feature information corresponding to scenario 1 is "101000". After performing the "AND" operation on the target feature information and the reference feature information bit by bit, the resulting feature information after the operation is "101000".

[0132] It should be noted that for the convenience of operation, the user profile identifiers represented by the feature information at the corresponding positions of the target feature information and the reference feature information corresponding to the target scenario need to correspond one by one. For example, the first digit "1" in the target feature information "111000" of scenario 1 and the reference feature information "101000" corresponding to scenario 1 should represent the same user profile identifier. For example, they both represent the "community nickname" in the set of user profile identifiers.

[0133] 204. The server determines the target user profile identifier corresponding to the target scenario from the set of user profile identifiers according to the fused feature information.

[0134] For example, the server can specifically determine the target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the fused feature information.

[0135] Among them, the fused feature information includes at least one sub-feature information. Specifically, the step of "determining the target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the fused feature information" may include:

[0136] Obtain the query characteristic information of each sub-feature information;

[0137] Determine the target queryable feature information from at least one sub-feature information according to the query characteristic information;

[0138] Determine the target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the target queryable feature information.

[0139] Among them, the query feature information indicates whether a certain sub - feature information has the feature of being queryable. For example, the fused feature information is "101000", where "1" represents the queryable feature information and "0" represents the non - queryable feature information.

[0140] Among them, according to the target queryable feature information, the target user profile identifier corresponding to the target scenario is determined from the candidate user profile identifiers. For example, in the target feature information "111000", the sub - feature information with the first three digits being "1" respectively represents candidate user profile identifiers (such as: user account, community nickname, community image). In the fused feature information "101000", the first and third digits represent the user profile identifiers corresponding to the queryable feature information (such as: user account, community image). Then, the target user profile identifiers corresponding to the target scenario can be determined from the candidate user profile identifiers as "user account" and "community image".

[0141] In the embodiment of this application, the idea of using the "AND" operation to obtain the fused feature information is as follows: When the feature information corresponding to a certain user profile identifier that the user needs to query and the feature information corresponding to this user profile identifier defined in the background are both "1", it means that this user profile identifier is the target user profile identifier corresponding to the target scenario, that is, it is used as the user profile identifier for finally obtaining the user profile information corresponding to this identifier from the database.

[0142] In one embodiment, the target user profile identifier corresponding to the target scenario can also be determined from the candidate user profile identifiers according to the account login form of the requesting user and the target queryable feature information. That is, before the step of "obtaining the set of user profile identifiers corresponding to the target user", it further includes:

[0143] Detect the user account of the requesting user to determine the login form of the requesting user;

[0144] Then at this time, the step of "determining the target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the target queryable feature information" can include:

[0145] Determine the target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the login form of the requesting user and the target queryable feature information.

[0146] Among them, the login states of the user account include the main state and the guest state, etc. Among them, the main state is to view one's own user profile information, and the guest state is to view the user profile information of others. Out of privacy protection for the user's personal information, the guest state is restricted by preset permissions when viewing user profiles, and the user profiles viewed are also relatively limited. For example, taking the "game online status" in the game client as an example of user profile, when the login state of the requesting user is the guest state, if the user profile information such as "game online status" included in the target scenario it requests to view is set to private (that is, not visible to others), then the requesting user cannot view whether the target object is online.

[0147] 205. The server queries the user profile information corresponding to the target user profile identifier according to the target scenario.

[0148] For example, the server obtains the user profile information from the database storing the user profile information corresponding to the target user profile identifier according to the target user profile identifier corresponding to the target scenario. For example, the server can query the user's community nickname, community image, community level, community gender, community medal and other user profile data from the community database, and query the user's game nickname, game online status, game image, game rank, game last login time and other data from the game database, as Figure 2c shown, which shows the relationship between the client, the background server, the bit operation server, the community database, and the game database during the process of querying user profile information.

[0149] In the embodiments of the present application, the query of user profiles in all scenarios will perform data selection and query through "bit" operations. Only when the "bit" data corresponding to the user profile identifier in the request of the client is 1, the background server will query the corresponding data. When the corresponding "bit" data is 0, the background server does not need to query the corresponding data. Therefore, the interaction between the background server and the community database and the game database is reduced, and the system performance is improved. At the same time, there is no need to provide different interfaces for each scenario, and only the "bit" data needs to be configured, which is beneficial to the expansion of the system.

[0150] 206. The server sends the user profile information corresponding to the target user profile identifier to the terminal.

[0151] For example, the server sends the user profile information corresponding to the target user profile identifier to the terminal so that the terminal can display the user profile information. See Figure 2d, taking the game client as an example, it shows the user profile information in the comment list scenario, including: user nickname, community level, community gender, game rank, comment time, and comment content, etc. For example, the community level of user A is Lv3, the community gender is male, the game rank is Gold III, and the comment time is 22:58 on November 2nd, and so on.

[0152] In one embodiment, the general processing flow of the user profile query method provided by the embodiments of the present application can be referred to Figure 2e .

[0153] In one embodiment, the user profile information corresponding to the target user profile identifier can also be stored in the blockchain. Among them, the blockchain system can be a distributed system formed by connecting a client and multiple nodes (any form of computing device connected to the network, such as a server, user terminal) through network communication. See Figure 2f , Figure 2f is an optional structural schematic diagram of the distributed system 100 provided by the embodiments of the present invention applied to the blockchain system, formed by multiple nodes (any form of computing device connected to the network, such as a server, user terminal) and a client. A peer-to-peer (P2P) network is formed between the nodes. The P2P protocol is an application layer protocol running on top of the Transmission Control Protocol (TCP). In the distributed system, any machine such as a server or a terminal can join and become a node. A node includes a hardware layer, an intermediate layer, an operating system layer, and an application layer.

[0154] See Figure 2f shows the functions of each node in the blockchain system. The functions involved include:

[0155] 1) Routing, the basic function of a node, used to support communication between nodes.

[0156] In addition to the routing function, a node can also have the following functions:

[0157] 2) Application, used to be deployed in the blockchain, implement specific services according to actual business needs, record the data related to the implemented functions to form record data, carry a digital signature in the record data to indicate the source of the task data, and send the record data to other nodes in the blockchain system. When other nodes verify the source and integrity of the record data successfully, the record data is added to the temporary block.

[0158] For example, the services implemented by the application include:

[0159] 2.1) A wallet, which is used to provide the function of conducting electronic currency transactions, including initiating a transaction (i.e., sending the transaction record of the current transaction to other nodes in the blockchain system. After successful verification by other nodes, as a response to acknowledging the validity of the transaction, the record data of the transaction is deposited into the temporary block of the blockchain. Of course, the wallet also supports querying the remaining electronic currency in the electronic currency address;

[0160] 2.2) A shared ledger, which is used to provide functions such as storage, query, and modification of account data. The record data of the operations on the account data is sent to other nodes in the blockchain system. After successful verification by other nodes, as a response to acknowledging the validity of the account data, the record data is deposited into the temporary block, and a confirmation can also be sent to the node that initiated the operation.

[0161] 2.3) A smart contract, which is a computerized protocol that can execute the terms of a certain contract. It is implemented by code deployed on the shared ledger and used to execute under certain conditions. According to actual business requirements, the code is used to complete automated transactions, such as querying the logistics status of the goods purchased by the buyer and transferring the buyer's electronic currency to the merchant's address after the buyer signs for the goods. Of course, smart contracts are not limited to executing contracts for transactions, but can also execute contracts for processing received information.

[0162] 3) A blockchain, which includes a series of blocks (Blocks) that are sequentially connected in the order of generation. Once a new block is added to the blockchain, it will not be removed again. The block records the record data submitted by nodes in the blockchain system.

[0163] See Figure 2g , Figure 2g is an optional schematic diagram of the block structure provided by the embodiments of the present invention. Each block includes the hash value of the transaction records stored in this block (the hash value of this block), and the hash value of the previous block. Each block is connected through the hash value to form a blockchain. In addition, the block may also include information such as the timestamp when the block is generated. A blockchain, in essence, is a decentralized database, a string of data blocks generated by using cryptographic methods. Each data block contains relevant information for verifying the validity of its information (anti-counterfeiting) and generating the next block.

[0164] As can be seen from the above, in the embodiment of the present application, when receiving a user profile query request sent by a terminal, the user profile identifier set corresponding to the target user can be obtained. The user profile identifier set includes the user profile identifiers that the target user has in multiple scenarios, and the user profile query request indicates the target scenario of the user profile to be queried. Feature fusion is performed on the user profile identifiers in each scenario in the user profile identifier set based on the target scenario to obtain the target feature information corresponding to the target scenario. The target feature information is fused with the reference feature information corresponding to the target scenario to obtain the fused feature information. According to the fused feature information, the target user profile identifier corresponding to the target scenario is determined from the user profile identifier set. The user profile information corresponding to the target user profile identifier is sent to the terminal. Since this solution can perform feature fusion on the user profile identifier set that the target user has in multiple scenarios to obtain the target feature information corresponding to the target scenario, and fuse the target feature information and the reference feature information corresponding to the target scenario (the reference feature information can be flexibly configured), such as performing a logical "AND" operation, and determine the target user profile identifier corresponding to the target scenario based on the obtained fused feature information (that is, determining the user profile identifier with the "bit" data of "1" in the fused feature information as the target user profile identifier), and then querying the user profile information according to the target user profile identifier, the flexibility of user profile query is greatly improved.

[0165] To facilitate better implementation of the above method, the embodiment of the present application also provides a user profile query device.

[0166] For example, as Figure 3a shown, the user profile query device may include an acquisition unit 301, a feature fusion unit 302, a fusion unit 303, a determination unit 304, and a sending unit 305, etc., as follows:

[0167] The acquisition unit 301 is configured to receive a user profile query request sent by a terminal, and the user profile query request indicates the target scenario of the user profile to be queried;

[0168] The feature fusion unit 302 is configured to perform feature fusion on the user profile identifiers in each scenario in the user profile identifier set based on the target scenario to obtain the target feature information corresponding to the target scenario;

[0169] The fusion unit 303 is configured to fuse the target feature information with the reference feature information corresponding to the target scenario to obtain the fused feature information;

[0170] The determination unit 304 is configured to determine the target user profile identifier corresponding to the target scenario from the user profile identifier set according to the fused feature information;

[0171] A sending unit 305, configured to send user profile information corresponding to the target user profile identifier to the terminal.

[0172] In some embodiments, the feature fusion unit 302 is configured to:

[0173] Determine candidate user profile identifiers corresponding to a target scenario from the set of user profile identifiers;

[0174] Perform feature representation on the candidate user profile identifiers in the set of user profile identifiers to obtain first feature information;

[0175] Perform feature representation on the non-candidate user profile identifiers in the set of user profile identifiers to obtain second feature information;

[0176] Fuse the first feature information and the second feature information to obtain target feature information corresponding to the target scenario;

[0177] The determining unit 304 is further configured to determine, according to the fused feature information, a target user profile identifier corresponding to the target scenario from the candidate user profile identifiers.

[0178] In some embodiments, the fusion unit 303 is specifically configured to:

[0179] Perform a logical operation on the target feature information and reference feature information corresponding to the target scenario to obtain operation result feature information;

[0180] Generate fused feature information based on the operation result feature information.

[0181] In some embodiments, referring to Figure 3b , the fused feature information includes at least one sub-feature information, and the determining unit 304 includes:

[0182] An obtaining subunit 3041, configured to obtain query characteristic information of each sub-feature information;

[0183] A feature determining subunit 3042, configured to determine target queryable feature information from the at least one sub-feature information according to the query characteristic information;

[0184] An identifier determining subunit 3043, configured to determine a target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the target queryable feature information.

[0185] In some embodiments, referring to Figure 3c , the sending unit 305 includes:

[0186] A query subunit 3051, configured to query user profile information corresponding to the target user profile identifier according to the target user profile identifier corresponding to the target scenario;

[0187] A sending subunit 3052, configured to send the user profile information corresponding to the target user profile identifier to the terminal.

[0188] In some embodiments, the query subunit 3051 is specifically configured to:

[0189] Obtain a preset user profile database, where the preset user profile database includes user profile information corresponding to user profile identifiers;

[0190] Match the target user profile identifier with the user profile identifiers in the preset user profile database;

[0191] When the target user profile identifier matches successfully with the user profile identifiers in the preset user profile database, extract the user profile information corresponding to the successfully matched user profile identifier from the preset user profile database to obtain the user profile information corresponding to the target user profile identifier.

[0192] In some embodiments, refer to Figure 3d , the user profile query device further includes:

[0193] A detection unit 306, configured to detect the user account of the requesting user to determine the login form of the requesting user;

[0194] The identifier determination subunit 3043 is further configured to determine the target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the login form of the requesting user and the target queryable feature information.

[0195] In specific implementation, each of the above units can be implemented as an independent entity, or can be combined arbitrarily to be implemented as the same or several entities. For the specific implementation of each of the above units, reference can be made to the foregoing method embodiments, which will not be elaborated herein.

[0196] As can be seen from the above, the video playback device of the embodiment of the present application can obtain a user profile identification set corresponding to the target user through the acquisition unit 301 when receiving a user profile query request sent by the terminal. The user profile identification set includes the user profile identification of the target user in multiple scenarios, and the user profile query request indicates the target scene of the user profile to be queried; the feature fusion unit 302 performs feature fusion on the user profile identification in each scenario in the user profile identification set based on the target scene to obtain target feature information corresponding to the target scene; the fusion unit 303 fuses the target feature information with the reference feature information corresponding to the target scene to obtain fused feature information; the determination unit 304 determines the target user profile identification corresponding to the target scene from the user profile identification set based on the fused feature information; and the sending unit 305 sends the user profile information corresponding to the target user profile identification to the terminal. Since the solution can perform feature fusion on the user profile identifiers of the target user in multiple scenarios, obtain the target feature information corresponding to the target scenario, and fuse the target feature information with the reference feature information, determine the target user profile identifier corresponding to the target scenario based on the obtained fused feature information, and then query the user profile information based on the target user profile identifier, thereby greatly improving the flexibility of user profile query.

[0197] The present application also provides a computer device, such as Figure 4 As shown, it shows a schematic diagram of the structure of the computer device involved in the embodiment of the present application, specifically:

[0198] The computer device may include components such as a processor 401 with one or more processing cores, a memory 402 with one or more computer-readable storage media, a power supply 403, and an input unit 404. Those skilled in the art will appreciate that Figure 4 The computer device structure shown in the figure does not constitute a limitation on the computer device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. Among them:

[0199] The processor 401 is the control center of the computer device. It uses various interfaces and lines to connect various parts of the entire computer device. By running or executing software programs and / or modules stored in the memory 402 and calling data stored in the memory 402, it executes various functions of the computer device and processes data, thereby monitoring the computer device as a whole. Optionally, the processor 401 may include one or more processing cores; preferably, the processor 401 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 401.

[0200] The memory 402 can be used to store software programs and modules. The processor 401 executes various functional applications and data processing by running the software programs and modules stored in the memory 402. The memory 402 mainly includes a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for at least one function (such as a sound playback function, a video playback function, etc.); the data storage area can store data created according to the use of the computer device. In addition, the memory 402 can include high-speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. Correspondingly, the memory 402 can also include a memory controller to provide the processor 401 with access to the memory 402.

[0201] The computer device further includes a power supply 403 for powering each component. Preferably, the power supply 403 can be logically connected to the processor 401 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. The power supply 403 can also include any components such as one or more DC or AC power supplies, a recharge system, a power failure detection circuit, a power converter or inverter, and a power status indicator.

[0202] The computer device may further include an input unit 404, which can be used to receive input digital or character information, and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.

[0203] Although not shown, the computer device may further include a display unit, etc., which will not be elaborated here. Specifically, in this embodiment, the processor 401 in the computer device will load the executable files corresponding to the processes of one or more application programs into the memory 402 according to the following instructions, and the processor 401 will run the application programs stored in the memory 402 to implement various functions as follows:

[0204] When receiving a user profile query request sent by a terminal, obtain a set of user profile identifiers corresponding to the target user. The set of user profile identifiers includes the user profile identifiers that the target user has in multiple scenarios, and the user profile query request indicates the target scenario of the user profile to be queried. Based on the target scenario, perform feature fusion on the user profile identifiers in each scenario in the set of user profile identifiers to obtain target feature information corresponding to the target scenario. Fuse the target feature information with the reference feature information corresponding to the target scenario to obtain fused feature information. According to the fused feature information, determine the target user profile identifier corresponding to the target scenario from the set of user profile identifiers. Send the user profile information corresponding to the target user profile identifier to the terminal.

[0205] For the specific implementation of each of the above operations, reference may be made to the previous embodiments, which will not be elaborated here.

[0206] As can be seen from the above, when the computer device according to the embodiment of the present application receives a user profile query request sent by a terminal, it can obtain a set of user profile identifiers corresponding to the target user. The set of user profile identifiers includes the user profile identifiers that the target user has in multiple scenarios, and the user profile query request indicates the target scenario of the user profile to be queried. Based on the target scenario, perform feature fusion on the user profile identifiers in each scenario in the set of user profile identifiers to obtain target feature information corresponding to the target scenario. Fuse the target feature information with the reference feature information corresponding to the target scenario to obtain fused feature information. According to the fused feature information, determine the target user profile identifier corresponding to the target scenario from the set of user profile identifiers. Send the user profile information corresponding to the target user profile identifier to the terminal. Since this solution can perform feature fusion on the user profile identifiers that the target user has in multiple scenarios to obtain target feature information corresponding to the target scenario, and after fusing the target feature information and the reference feature information, determine the target user profile identifier corresponding to the target scenario based on the obtained fused feature information, and then query the user profile information according to the target user profile identifier, thereby greatly improving the flexibility of user profile query.

[0207] Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructions or by controlling related hardware through instructions. The instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0208] Therefore, the embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. The computer program can be loaded by a processor to execute the steps in any one of the user profile query methods provided by the embodiment of the present application. For example, the computer program can execute the following steps:

[0209] When receiving a user profile query request sent by a terminal, obtain a set of user profile identifiers corresponding to the target user. The set of user profile identifiers includes the user profile identifiers that the target user has in multiple scenarios. The user profile query request indicates the target scenario of the user profile to be queried. Based on the target scenario, perform feature fusion on the user profile identifiers in each scenario in the set of user profile identifiers to obtain target feature information corresponding to the target scenario. Fuse the target feature information with the reference feature information corresponding to the target scenario to obtain fused feature information. According to the fused feature information, determine the user profile identifier corresponding to the target scenario from the set of user profile identifiers. Send the user profile information corresponding to the user profile identifier to the terminal.

[0210] For the specific implementation of each of the above operations, reference may be made to the previous embodiments, which will not be elaborated here.

[0211] Among them, the computer-readable storage medium may include: read-only memory (ROM, Read Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disc, etc.

[0212] Since the instructions stored in the computer-readable storage medium can execute the steps in any of the user profile query methods provided in the embodiments of the present application, the beneficial effects that can be achieved by any of the user profile query methods provided in the embodiments of the present application can be realized. For details, reference may be made to the previous embodiments, which will not be elaborated here.

[0213] The above has introduced in detail a user profile query method, device, computer device, and computer-readable storage medium provided in the embodiments of the present application. Specific examples are used in this article to elaborate on the principle and implementation manner of the present invention. The description of the above embodiments is only used to help understand the method and its core idea of the present invention; at the same time, for those skilled in the art, according to the idea of the present invention, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to the present invention.

Claims

1. A user profile query method, characterized in that, Including: When receiving a user profile query request sent by a terminal, obtain a set of user profile identifiers corresponding to a target user. The set of user profile identifiers includes user profile identifiers that the target user has in multiple scenarios, and the user profile query request indicates a target scenario of the user profile to be queried. Based on the target scenario, perform feature fusion on the user profile identifiers in each scenario in the set of user profile identifiers to obtain target feature information corresponding to the target scenario. Fuse the target feature information with reference feature information corresponding to the target scenario to obtain fused feature information, where the fusion includes performing logical operations. According to the fused feature information, determine a target user profile identifier corresponding to the target scenario from the set of user profile identifiers. Send the user profile information corresponding to the target user profile identifier to the terminal.

2. The method according to claim 1, characterized in that, The step of performing feature fusion on the user profile identifiers in each scenario in the set of user profile identifiers based on the target scenario to obtain target feature information corresponding to the target scenario includes: Determine candidate user profile identifiers corresponding to the target scenario from the set of user profile identifiers. Perform feature representation on the candidate user profile identifiers in the set of user profile identifiers to obtain first feature information. Perform feature representation on the non-candidate user profile identifiers in the set of user profile identifiers to obtain second feature information. Fuse the first feature information with the second feature information to obtain target feature information corresponding to the target scenario. According to the fused feature information, determining a target user profile identifier corresponding to the target scenario from the set of user profile identifiers includes: According to the fused feature information, determine a target user profile identifier corresponding to the target scenario from the candidate user profile identifiers.

3. The method according to claim 1, characterized in that, The step of fusing the target feature information with reference feature information corresponding to the target scenario to obtain fused feature information includes: Perform a logical operation on the target feature information and the reference feature information corresponding to the target scenario to obtain operation result feature information. Generate fused feature information based on the operation result feature information.

4. The method according to claim 2, wherein The fused feature information includes at least one sub-feature information. The step of determining a target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the fused feature information includes: Obtain query characteristic information of each sub-feature information. According to the query characteristic information, determine target queryable feature information from the at least one sub-feature information. According to the target queryable feature information, determine a target user profile identifier corresponding to the target scenario from the candidate user profile identifiers.

5. The method according to claim 1, wherein The step of sending the user profile information corresponding to the target user profile identifier to the terminal includes: According to the target user profile identifier corresponding to the target scenario, query the user profile information corresponding to the target user profile identifier. Send the user profile information corresponding to the target user profile identifier to the terminal.

6. The method according to claim 5, characterized in that, The step of querying the user profile information corresponding to the target user profile identifier according to the target user profile identifier corresponding to the target scenario includes: Obtain a preset user database, where the preset user database includes user profile information corresponding to user profile identifiers; Match the target user profile identifier with the user profile identifiers in the preset user database; When the target user profile identifier matches successfully with the user profile identifiers in the preset user database, extract the user profile information corresponding to the successfully matched user profile identifier from the preset user database to obtain the user profile information corresponding to the target user profile identifier.

7. The method according to claim 4, characterized in that Before obtaining the set of user profile identifiers corresponding to the target user, it further includes: Detect the user account of the requesting user to determine the login form of the requesting user; Determine the target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the target queryable feature information, including: Determine the target user profile identifier corresponding to the target scenario from the candidate user profile identifiers according to the login form of the requesting user and the target queryable feature information.

8. A user profile query device, characterized in that, Includes: An obtaining unit, configured to obtain a set of user profile identifiers corresponding to a target user when receiving a user profile query request sent by a terminal, where the set of user profile identifiers includes the user profile identifiers that the target user has in multiple scenarios, and the user profile query request indicates the target scenario of the user profile to be queried; A feature fusion unit, configured to perform feature fusion on the user profile identifiers in each scenario in the set of user profile identifiers based on the target scenario to obtain target feature information corresponding to the target scenario; A fusion unit, configured to fuse the target feature information with reference feature information corresponding to the target scenario to obtain fused feature information, where the fusion includes performing logical operations; A determination unit, configured to determine the target user profile identifier corresponding to the target scenario from the set of user profile identifiers according to the fused feature information; A sending unit, configured to send the user profile information corresponding to the target user profile identifier to the terminal.

9. A computer device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein, When the processor executes the program, it implements the steps of the method according to any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, wherein, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1-7.

Images