CN113722589A

CN113722589A - Information generation method, device, server and storage medium

Info

Publication number: CN113722589A
Application number: CN202110969486.XA
Authority: CN
Inventors: 杨文强; 张吉凯; 刘淼
Original assignee: Beijing Dajia Internet Information Technology Co Ltd
Current assignee: Beijing Dajia Internet Information Technology Co Ltd
Priority date: 2021-08-23
Filing date: 2021-08-23
Publication date: 2021-11-30
Anticipated expiration: 2041-08-23
Also published as: CN113722589B

Abstract

The disclosure relates to an information generation method, an information generation device, a server and a storage medium, relates to the technical field of networks and aims to solve the problem that a file server is low in flexibility in file generation. The method comprises the following steps: when the user account enters the page of the target application, the server acquires the identification of the service scene and the identification of the login account of the target application, sends a request message comprising the identification of the service scene and the identification of the login account, and acquires feedback information. And then, the server generates relationship chain information based on the service scene and the feedback information, wherein the relationship chain information is used for generating a relationship chain to be displayed and returning the relationship chain information to the client. The request message is used for requesting feedback information, and the feedback information is used for generating relationship chain information.

Description

Information generation method, device, server and storage medium

Technical Field

The present disclosure relates to the field of network technologies, and in particular, to an information generating method, an information generating apparatus, a server, and a storage medium.

Background

The social application program displays a target file (such as 'common friends: Zhang III', 'you have focused on Zhang III, and other 5 persons') of the recommended user on a page (such as a personal homepage, a search page, a fan list page, an acquaintance circle, and a person who may know) of a specific service scene so as to recommend the recommended user to the logged-in user, so as to guide the logged-in user to focus on the recommended user, and thus develop the social relationship among the users.

At present, the target file of the recommended user is determined and sent to the client after the file server receives a file acquisition instruction sent by the client. And the client displays the received target file in a service scene for the login user to check. The process of determining the target file by the file server is as follows: and determining the highest priority relationship type corresponding to the current service scene, determining a recommended user with the relationship type with the login user, generating a target file of the recommended user, and sending the target file to the client. For different business scenes, the document server needs to execute the above processes to generate target documents meeting the requirements of different business scenes. Because the case server generates different cases for different service scenes, the flexibility of the case server for generating the cases is lower.

Disclosure of Invention

The present disclosure provides an information generating method, an information generating device, a server and a storage medium, so as to solve the problem of low flexibility of generating a document by a document server.

The technical scheme of the disclosure is as follows:

in a first aspect, the present disclosure provides an information generating method applied to a server. The method can comprise the following steps: when a user account enters a page of a target application, acquiring an identifier of a service scene of the target application and an identifier of a login account; sending a request message, wherein the request message comprises an identifier of the service scene and an identifier of the login account, and is used for requesting to acquire feedback information which is used for generating relationship chain information; acquiring the feedback information; generating the relationship chain information based on the service scene and the feedback information, wherein the relationship chain information is used for generating a relationship chain to be displayed; and returning the relation chain information to the client.

Optionally, generating the relationship chain information based on the service scenario and the feedback information may specifically include: analyzing the feedback information to obtain target keywords and parameter information, wherein the target keywords are keywords corresponding to the account relationship type corresponding to the service scene, and the parameter information comprises the identification and the number of the relevant accounts with the account relationship type between the login account and the target account; acquiring a relation chain template corresponding to the target keyword from an information template database; and generating the relation chain information based on the service scene, the relation chain template and the parameter information.

Optionally, when the identifier of the service scenario is an identifier of a current scenario, the account relationship type is a relationship type with a highest priority level in a plurality of account relationship types corresponding to the current scenario; when the identifier of the service scene includes an identifier of a current scene and an identifier of an upstream scene, the account relationship type is a relationship type which is the same as the account relationship type corresponding to the upstream scene in a plurality of relationship types corresponding to the current scene, and the upstream scene is a last display scene of the current scene.

Optionally, generating the relationship chain information based on the service scenario, the relationship chain template, and the parameter information may specifically include: analyzing the parameter information to obtain at least one parameter keyword included in the parameter information and a value corresponding to each parameter keyword; determining an information type according to the at least one parameter keyword, wherein the information type is one of an account name type, an address list contact type and a default type; generating the relationship chain information based on the information type, preset parameters corresponding to the current scene, the relationship chain template, the at least one parameter keyword and a value corresponding to each parameter keyword, wherein the preset parameters are pre-stored in the server and include at least one of the following parameters: the system comprises an information display type, first indication information and second indication information, wherein the information display type is used for indicating the display type of the relation chain information, the first indication information is used for indicating that a head portrait corresponding to an account is displayed, and the second indication information is used for indicating that a hyperlink function is supported.

Optionally, determining the information type according to the at least one parameter keyword may specifically include: when the at least one parameter keyword comprises a first parameter keyword used for indicating an account name, determining that the information type is the account name type; when the at least one parameter keyword comprises a second parameter keyword used for indicating the name of the address book contact person, determining that the information type is the type of the address book contact person; determining the information type as the default type when the first parameter keyword and the second parameter keyword are not included in the at least one parameter keyword.

Optionally, when the preset parameter includes the information display type, the generating the relationship chain information based on the information type, the preset parameter corresponding to the current scene, the relationship chain template, the at least one parameter keyword, and a value corresponding to each parameter keyword may specifically include: if the information type is the account name type, analyzing the information display type included by the preset parameters, wherein the information display type is a long information type or a short message type, when the information display type is the long information type, the relationship chain information includes a preset number of account names, and when the information display type is the short message type, the relationship chain information does not include the account names; if the information display type is the long information type and the preset number of account names corresponding to the long information type are N account names, acquiring a first value corresponding to the first parameter keyword, and acquiring N identifications of related accounts in the first value, wherein the first value comprises the identifications of all related accounts with the account relation type between the login account and the target account; acquiring an account name corresponding to the identifier of each related account according to the identifier of each related account in the N identifiers of the related accounts to obtain N account names; analyzing account name placeholders in the relationship chain template; and replacing the account name placeholders with the N account names to generate the relationship chain information, wherein the relationship chain information comprises the N account names.

Optionally, when the preset parameter further includes the first indication information, the generating the relationship chain information further includes: analyzing the first indication information included in the preset parameters; and acquiring an avatar address corresponding to the identifier of each related account according to the identifier of each related account in the N identifiers of the related accounts, wherein the relationship chain information further comprises N avatar addresses.

Optionally, when the preset parameter further includes the second indication information, the generating the relationship chain information further includes: analyzing the second indication information included in the preset parameters; and acquiring a hyperlink corresponding to the identification of each related account according to the identification of each related account in the N identifications of the related accounts, wherein the relation chain information further comprises N hyperlinks.

Optionally, the generating the relationship chain information based on the information type, the preset parameter corresponding to the current scene, the relationship chain template, the at least one parameter keyword, and the value corresponding to each parameter keyword may specifically include: if the information type is the default type, analyzing the quantity placeholder in the relation chain template; and correspondingly replacing the quantity placeholder in the relation chain template with a value corresponding to a parameter keyword to generate the relation chain information, wherein the parameter keyword is used for indicating that the login account and the target account have the quantity of the related account with the account relation type.

Optionally, generating the relationship chain information based on the service scenario, the relationship chain template, and the parameter information may specifically include: and generating relation chain information in a preset format based on the service scene, the relation chain template and the parameter information. The returning of the relationship chain information to the client includes: and sending the relation chain information in the preset format to the client.

Optionally, after sending the request message, the information generating method further includes: and sending preset information to the client under the condition that the feedback information is not acquired, wherein the preset information is plain text type information.

In a second aspect, an information generating method is provided, and the method includes: receiving a request message, wherein the request message comprises an identifier of a service scene of a target application and an identifier of a login account, the request message is used for requesting to acquire feedback information, and the feedback information is used for generating relationship chain information; generating the feedback information according to the identification of the service scene and the identification of the login account; and sending the feedback information.

Optionally, the feedback information includes target keywords and parameter information, and the generating the feedback information according to the identifier of the service scenario and the identifier of the login account includes: determining a corresponding account relation type according to the identification of the service scene; acquiring the target keywords corresponding to the account relation type; determining the parameter information according to the account relationship type and the identification of the login account, wherein the parameter information comprises the identification and the number of the related accounts with the account relationship type between the login account and the target account; and generating the feedback information according to the target keyword and the parameter information.

Optionally, determining the corresponding account relationship type according to the identifier of the service scenario includes: and when the identifier of the service scene is the identifier of the current scene, determining the relationship type with the highest priority in the plurality of relationship types corresponding to the current scene as the account relationship type.

Optionally, determining the corresponding account relationship type according to the identifier of the service scenario includes: when the identifier of the service scene includes an identifier of a current scene and an identifier of an upstream scene, determining a relationship type, which is the same as an account relationship type corresponding to the upstream scene, from among a plurality of relationship types corresponding to the current scene as the account relationship type, where the upstream scene is a last display scene of the current scene.

Optionally, the information generating method further includes: responding to the operation of adding a candidate account relation type in a current scene, acquiring the priority of the candidate account relation type, and establishing the corresponding relation between the identifier of the current scene and the candidate account relation type, the corresponding relation between the candidate account relation type and a candidate keyword, and the corresponding relation between the candidate keyword and a candidate relation chain template; and sending the corresponding relation between the candidate keywords and the candidate relation chain template to an information template database.

Optionally, the information generating method further includes: in response to the deletion operation of the offline account relationship type corresponding to the current scene, deleting the corresponding relationship between the identifier of the current scene and the offline account relationship type and the corresponding relationship between the offline account relationship type and the offline keyword; and sending deletion indication information to an information template database, wherein the deletion indication information is used for indicating that the corresponding relation between the offline keyword and the offline relation chain template is deleted.

In a third aspect, an information generating apparatus applied to a server includes: the acquisition module is configured to acquire an identifier of a service scene and an identifier of a login account of a target application when a user account enters a page of the target application; a sending module configured to execute sending a request message, where the request message includes the identifier of the service scenario and the identifier of the login account, where the request message is used to request to obtain feedback information, and the feedback information is used to generate relationship chain information; the obtaining module is further configured to perform obtaining the feedback information; the generating module is configured to execute generating the relationship chain information based on the service scene and the feedback information acquired by the acquiring module, wherein the relationship chain information is used for generating a relationship chain to be displayed; the sending module is further configured to execute returning the relationship chain information generated by the generating module to a client.

Optionally, the generating module is specifically configured to perform: analyzing the feedback information to obtain target keywords and parameter information, wherein the target keywords are keywords corresponding to the account relationship type corresponding to the service scene, and the parameter information comprises the identification and the number of the relevant accounts with the account relationship type between the login account and the target account; acquiring a relation chain template corresponding to the target keyword from an information template database; and generating the relation chain information based on the service scene, the relation chain template and the parameter information.

Optionally, the generating module is specifically configured to perform: analyzing the parameter information to obtain at least one parameter keyword included in the parameter information and a value corresponding to each parameter keyword; determining an information type according to the at least one parameter keyword, wherein the information type is one of an account name type, an address list contact type and a default type; generating the relationship chain information based on the information type, preset parameters corresponding to the current scene, the relationship chain template, the at least one parameter keyword and a value corresponding to each parameter keyword, wherein the preset parameters are pre-stored in the server and include at least one of the following parameters: the system comprises an information display type, first indication information and second indication information, wherein the information display type is used for indicating the display type of the relation chain information, the first indication information is used for indicating that a head portrait corresponding to an account is displayed, and the second indication information is used for indicating that a hyperlink function is supported.

Optionally, the generating module is specifically configured to perform: when the at least one parameter keyword comprises a first parameter keyword used for indicating an account name, determining that the information type is the account name type; when the at least one parameter keyword comprises a second parameter keyword used for indicating the name of the address book contact person, determining that the information type is the type of the address book contact person; determining the information type as the default type when the first parameter keyword and the second parameter keyword are not included in the at least one parameter keyword.

Optionally, when the preset parameter includes the information presentation type, the generating module is specifically configured to execute: if the information type is the account name type, analyzing the information display type included by the preset parameters, wherein the information display type is a long information type or a short message type, when the information display type is the long information type, the relationship chain information includes a preset number of account names, and when the information display type is the short message type, the relationship chain information does not include the account names; if the information display type is the long information type and the preset number of account names corresponding to the long information type are N account names, acquiring a first value corresponding to the first parameter keyword, and acquiring N identifications of related accounts in the first value, wherein the first value comprises the identifications of all related accounts with the account relation type between the login account and the target account; acquiring an account name corresponding to the identifier of each related account according to the identifier of each related account in the N identifiers of the related accounts to obtain N account names; analyzing account name placeholders in the relationship chain template; and replacing the account name placeholders with the N account names to generate the relationship chain information, wherein the relationship chain information comprises the N account names.

Optionally, when the preset parameter further includes the first indication information, the information generating apparatus further includes: an analysis module; the analysis module is configured to analyze the first indication information included in the preset parameter; the obtaining module is further configured to obtain an avatar address corresponding to each identifier of the relevant account according to the identifier of each relevant account in the N identifiers of the relevant accounts, and the relationship chain information further includes N avatar addresses.

Optionally, when the preset parameter further includes the second indication information, the information generating apparatus further includes: an analysis module; the analysis module is configured to analyze the second indication information included in the preset parameter; the obtaining module is further configured to execute obtaining a hyperlink corresponding to each identifier of the relevant account according to the identifier of each relevant account in the N identifiers of the relevant account, where the relationship chain information further includes N hyperlinks.

Optionally, the generating module is specifically configured to perform: if the information type is the default type, analyzing the quantity placeholder in the relation chain template; and correspondingly replacing the quantity placeholder in the relation chain template with a value corresponding to a parameter keyword to generate the relation chain information, wherein the parameter keyword is used for indicating that the login account and the target account have the quantity of the related account with the account relation type.

Optionally, the generating module is specifically configured to perform: generating relation chain information in a preset format based on the service scene, the relation chain template and the parameter information; the sending module is specifically configured to perform: and sending the relation chain information in the preset format to the client.

Optionally, the sending module is further configured to send preset information to the client when the feedback information is not obtained, where the preset information is a plain text type of information.

In a fourth aspect, an information generating apparatus is provided, including: the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is configured to execute receiving of a request message, the request message comprises an identifier of a service scene of a target application and an identifier of a login account, the request message is used for requesting to acquire feedback information, and the feedback information is used for generating relationship chain information; the generating module is configured to execute the generation of the feedback information according to the identification of the service scene and the identification of the login account received by the receiving module; a transmitting module configured to perform transmitting the feedback information generated by the generating module.

Optionally, the feedback information includes a target keyword and parameter information, and the generating module is specifically configured to perform: determining a corresponding account relation type according to the identification of the service scene; acquiring the target keywords corresponding to the account relation type; determining the parameter information according to the account relationship type and the identification of the login account, wherein the parameter information comprises the identification and the number of the related accounts with the account relationship type between the login account and the target account; and generating the feedback information according to the target keyword and the parameter information.

Optionally, the generating module is specifically configured to perform: and when the identifier of the service scene is the identifier of the current scene, determining the relationship type with the highest priority in the plurality of relationship types corresponding to the current scene as the account relationship type.

Optionally, the generating module is specifically configured to perform: when the identifier of the service scene includes an identifier of a current scene and an identifier of an upstream scene, determining a relationship type, which is the same as an account relationship type corresponding to the upstream scene, from among a plurality of relationship types corresponding to the current scene as the account relationship type, where the upstream scene is a last display scene of the current scene.

Optionally, the information generating apparatus further includes: establishing a module; the obtaining module is further configured to execute an operation of adding a candidate account relationship type in response to a current scene, and obtain a priority of the candidate account relationship type; the establishing module is configured to perform establishing of a correspondence between the identifier of the current scene and the candidate account relationship type, a correspondence between the candidate account relationship type and a candidate keyword, and a correspondence between the candidate keyword and a candidate relationship chain template; the sending module is further configured to execute sending the corresponding relation between the candidate keyword and the candidate relation chain template to an information template database.

Optionally, the information generating apparatus further includes: a deletion module; the deleting module is configured to execute a deleting operation responding to a offline account relationship type corresponding to a current scene, and delete the corresponding relationship between the identifier of the current scene and the offline account relationship type and the corresponding relationship between the offline account relationship type and an offline keyword; the sending module is further configured to execute sending deletion indication information to an information template database, where the deletion indication information is used to indicate that the corresponding relationship between the offline keyword and the offline relationship chain template is deleted.

In a fifth aspect, the present disclosure provides a server comprising: a processor; a memory for storing processor-executable instructions. Wherein the processor is configured to execute the instructions to implement the information generating method shown in any one of the possible implementations of the first aspect and the first aspect described above, or to implement the information generating method shown in any one of the possible implementations of the second aspect and the second aspect described above.

In a sixth aspect, the present disclosure provides a computer-readable storage medium, wherein instructions, when executed by a processor of a server, enable the server to perform the information generation method as set forth in any one of the possible implementations of the first aspect and the first aspect described above, or the information generation method as set forth in any one of the possible implementations of the second aspect described above.

In a seventh aspect, the present disclosure provides a computer program product, which is directly loadable into an internal memory of a server and contains software codes, and which is loaded via the server and executes the information generating method shown in the first aspect and any possible implementation manner of the first aspect, or the information generating method shown in the second aspect and any possible implementation manner of the second aspect.

Any one of the above-mentioned information generating apparatus, server, computer-readable storage medium, or computer program product is configured to execute the above-mentioned corresponding method, so that the beneficial effects that can be achieved by the above-mentioned information generating apparatus, server, computer-readable storage medium, or computer program product can refer to the beneficial effects of the corresponding scheme in the above-mentioned corresponding method, and are not described herein again.

The technical scheme provided by the disclosure at least brings the following beneficial effects: after acquiring the identifier of the service scene of the target application and the identifier of the login account, the first server can request the second server for feedback information for generating the relationship chain information, generate the relationship chain information based on the service scene and the acquired feedback information, and return the relationship chain information to the client, so that the client can display the relationship chain. In this way, the first server generates the relationship chain information by obtaining the feedback information from the second server and combining the service scene, so that the relationship chain information is generated more flexibly.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.

FIG. 1 is a schematic diagram of a system architecture to which embodiments of the present disclosure are applicable, shown in accordance with an exemplary embodiment;

FIG. 2 is one of the flow diagrams of an information generation method shown in accordance with an exemplary embodiment;

FIG. 3 is a second schematic flow chart diagram illustrating a method of information generation in accordance with an exemplary embodiment;

FIG. 4 is a third flowchart illustration of an information generation method, according to an example embodiment;

FIG. 5 is one of the schematic structural diagrams of an information generating apparatus shown according to an exemplary embodiment;

fig. 6 is a second schematic structural diagram of an information generating apparatus according to an exemplary embodiment;

FIG. 7 is a third schematic diagram illustrating a configuration of an information generating apparatus according to an exemplary embodiment;

fig. 8 is a block diagram illustrating a logical structure of a server according to an example embodiment.

Detailed Description

In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that in the embodiments of the present disclosure, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "e.g.," in an embodiment of the present disclosure is not to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

Before describing the information generation method provided by the embodiment of the present disclosure in detail, an application scenario related to the embodiment of the present disclosure is described first. The disclosed embodiments can be applied to the following scenarios:

scene one: the terminal device obtains at least one target user and a file of each target user for a requesting user (namely, a user corresponding to an account for logging in the target application) on a search page of the target application.

Scene two: the terminal equipment responds to the display operation of the requesting user on the target user in the search page, acquires the homepage of the target user and the file of the target user, and displays the file of the target user on the homepage of the target user.

The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments, which can be derived by one of ordinary skill in the art from the embodiments disclosed herein without making any creative effort, shall fall within the scope of protection of the present disclosure.

The information generation method provided by the embodiment of the disclosure can be applied to the system architecture in fig. 1. As shown in fig. 1, the system architecture includes a client 101, a server 102, and an information template database 103. In one possible implementation, the server 102 may include a first server and a second server. The client 101 is connected with a first server, and the first server is respectively connected with a second server and an information template database 103.

The client 101 is used for responding to the operation of the user account entering the page of the target application, sending an information acquisition request to the first server, wherein the information acquisition request comprises the identification of the business scene of the target application and the identification of the login account,

the first server is configured to receive an information acquisition request sent by the client 101, and send a request message to the second server, where the request message includes an identifier of a service scene and an identifier of a login account, and the request message is used to request to acquire feedback information, and the feedback information is used to generate relationship chain information.

And the second server is used for receiving the request message sent by the first server, generating feedback information according to the service scene identifier and the login account identifier in the request message, and returning the feedback information to the first server.

The first server is further configured to receive feedback information sent by the second server, generate relationship chain information based on the service scene and the feedback information, where the relationship chain information is used to generate a relationship chain to be displayed, and is also used to return the relationship chain information to the client 101.

The client 101 is further configured to receive relationship chain information returned by the first server.

And the information template database 103 is used for storing the corresponding relation between the keywords and the relation chain template.

The client 101 may be any terminal device or server, where the terminal device includes, but is not limited to, a mobile phone, a tablet computer, a desktop computer, a notebook computer, a vehicle-mounted terminal or a palm terminal. The server may be one server, or may be a server cluster composed of a plurality of servers, which is not limited in this disclosure. Fig. 1 illustrates a client 101 as a mobile phone.

The server 102 may be a server, and the server may be one server, or may also be a server cluster composed of a plurality of servers, which is not limited in this disclosure. The server 102 is illustrated in fig. 1 as comprising a first server and a second server.

Fig. 2 is a schematic flowchart of an information generating method provided in an embodiment of the present disclosure, where the method may be applied to the system shown in fig. 1, and as shown in fig. 2, the method may include the following steps S100 to S104.

S100: when the user account enters the page of the target application, the first server acquires the identification of the service scene and the identification of the login account of the target application.

When the user account enters the page of the target application, the first server may obtain an identifier of a service scenario of the target application and an identifier of a login account. The login account refers to an account for logging in the target application. The user account may be a login account or other accounts.

It is understood that a business scenario refers to a scenario in a target application, for example, the scenario in the target application may be a scenario of a home page, a scenario of a search page, a scenario of a private page, and the like. In one implementation, the identifier of the service scenario is an identifier of a current scenario. In another implementation, the identifier of the service scene includes an identifier of a current scene and an identifier of an upstream scene, where the upstream scene is a last display scene of the current scene.

Optionally, in this embodiment of the present disclosure, there are multiple implementation manners for the first server to obtain the identifier of the service scenario of the target application and the identifier of the login account.

For example, when detecting that a user account enters a page of a target application, a client generates an information acquisition request and sends the information acquisition request to a first server. And the first server acquires the identifier of the service scene and the identifier of the login account according to the information acquisition request.

In a specific implementation, the information obtaining request includes an identifier of a login account, and the information obtaining request may further include an identifier of an upstream scenario. In this way, the first server may obtain the identifier of the upstream scene and the identifier of the login account from the information obtaining request, and obtain the identifier of the current scene from the information corresponding to the interface that receives the information obtaining request. Illustratively, the identification of the current scene is: and (6) search. The identification of the upstream scene is: null, representing no upstream scenes.

For another example, when the first server detects that the user account enters the page of the target application installed on the first server, the identifier of the service scene of the target application and the identifier of the login account are obtained.

S101: the first server sends a request message to the second server, and the second server receives the request message sent by the first server.

The request message comprises an identifier of a service scene and an identifier of a login account. The request message is used for requesting to acquire feedback information, and the feedback information is used for generating relationship chain information, which may be file information.

S102: the second server sends the feedback information to the first server, and the first server receives the feedback information sent by the second server.

After acquiring the identifier of the service scene and the identifier of the login account of the target application, the first server may send a request message including the identifier of the service scene and the identifier of the login account to the second server. After receiving the request message, the second server may generate feedback information according to the identifier of the service scenario and the identifier of the login account, and send the feedback information to the first server. The first server may obtain the feedback information.

Optionally, the feedback information includes a target keyword and parameter information, where the target keyword is a keyword corresponding to an account relationship type corresponding to a service scenario, and the parameter information includes an identifier and a quantity of a related account having the account relationship type between a login account and the target account. The process of generating the feedback information by the second server comprises the following steps: and the second server determines the corresponding account relationship type according to the identification of the service scene, acquires the target keyword corresponding to the account relationship type, and determines the parameter information according to the account relationship type and the identification of the login account. And then, the second server generates feedback information according to the target key words and the parameter information.

Optionally, when the identifier of the service scenario is the identifier of the current scenario, the second server determines, as the account relationship type, a relationship type with the highest priority among the multiple relationship types corresponding to the current scenario. When the identifier of the service scene includes the identifier of the current scene and the identifier of the upstream scene, the second server determines, as the account relationship type, a relationship type that is the same as the account relationship type corresponding to the upstream scene, from among the plurality of relationship types corresponding to the current scene.

As can be seen from the above, when the service scene includes the current scene and the upstream scene, the account relationship type is determined based on the current scene and the upstream scene, so that the account relationship types of the current scene and the upstream scene can be ensured to be the same, and thus the case of the upstream scene and the current scene can be ensured to be unified. That is, the recommended documents seen by the user B on the search page and the recommended documents seen by the homepage of the user B can be unified, and the user experience is improved.

S103: the first server generates relationship chain information based on the service scene and the feedback information.

The relationship chain information is used for generating a relationship chain to be displayed, and the relationship chain can be a file.

S104: the first server sends the relation chain information to the client, and the client receives and displays the relation chain information.

Optionally, in this embodiment of the present disclosure, based on fig. 2, as shown in fig. 3, the step S103 may specifically include the following steps S105 to S107.

S105: and the first server analyzes the feedback information to obtain the target keywords and the parameter information.

The target keywords are keywords corresponding to the account relationship type corresponding to the service scene, and the parameter information comprises identification and quantity of the relevant accounts with the account relationship type between the login account and the target account.

Illustratively, assume that the account relationship type is a common buddy. Then, the first server may read, according to the identifier of the login account, the friend user identifier corresponding to the identifier of the login account from the correspondence between the user identifier and the friend user identifier, and obtain the identifier of the corresponding target user according to the read friend user identifier. For example: the login account is a user A, the user C and the user D are both in a friend relationship, the first server obtains the friend relationship between the user C and the user B from the corresponding relationship between the user identification and the friend user identification, the user D and the user B are in the friend relationship, and the first server determines that the user B is a target user.

For another example, if the login account is user a, the target user is user B, user C is a friend of user a, and user C is a friend of user B, then user C is the relevant user.

S106: and the first server acquires the relation chain template corresponding to the target keyword from the information template database.

Illustratively, the relationship chain template is "$ { RECO _ TEXT _ USER _ IDS }, $ { RECO _ TEXT _ USER _ CNT }" as a common friend.

S107: the first server generates relation chain information based on the service scene, the relation chain template and the parameter information.

Therefore, the corresponding relation between the current scene and the account relation type, the keywords and the corresponding relation are pre-configured in the second server, and the corresponding relation between the keywords and the relation chain template is pre-configured in the information template database, so that the relation chain template corresponding to the account relation type can be more flexibly acquired. And the global unification of the account relation type and the relation chain template is realized through the keywords.

Optionally, in this embodiment of the present disclosure, based on fig. 3, as shown in fig. 4, the step S107 may specifically include the following steps S107A-S107C.

S107A: the first server analyzes the parameter information to obtain at least one parameter keyword included in the parameter information and a value corresponding to each parameter keyword.

Optionally, the parameter key in the parameter information (text Param Map) may define its data structure by using a tool (e.g., protobuf) for efficiently storing and reading the structured data.

For example, the parameter information may include parameter keywords as follows:

RECO_TEXT_UNKNOWN(0)，

RECO_TEXT_USER_IDS(1)，

RECO_TEXT_USER_CNT(2)，

RECO_TEXT_FANS_CNT(3)，

RECO_TEXT_CATEGORY(4)，

RECO_TEXT_YEARS(5)，

RECO_TEXT_ONLINE_TIME(6)，

RECO_TEXT_CONTACT_USER_IDS(7)，

RECO_TEXT_COMMENT_ID(8)，

RECO_TEXT_VERIFY_TAG(9)，

RECO_TEXT_ORIGIN_TEXT(10)，

RECO_TEXT_DAYS(11)，

UNRECOGNIZED(-1)。

the RECO _ TEXT _ USER _ IDS is used for indicating the identification of the accounts of the common friends, and the RECO _ TEXT _ USER _ CNT is used for indicating the number of the accounts of the common friends. The RECO _ TEXT _ CONTACT _ USER _ IDS is used for indicating the identification of the common address book CONTACT.

Illustratively, the information obtained by the first server analyzing the parameter information is specifically as follows:

Key：RECO_TEXT_USER_IDS

Value：123，456，789，147，258，369

Key：RECO_TEXT_FANS_CNT

Value：6

as can be seen, the parameter information includes two parameter keywords, i.e., the identification and the number of the accounts of the common friends. Wherein, the parameter keyword: the value corresponding to the identification of the common friend account includes: 123, 456, 789, 147, 258, 369 for indicating an identification of an account that is a common friend of the login account and the target account. The parameter keywords are: the value corresponding to the number of the accounts of the common friends is 6, and the value is used for indicating the number of the common friends of the login account and the target account.

S107B: the first server determines the type of information based on at least one parameter keyword.

The information type is one of an account name type, an address list contact person type and a default type.

In a specific implementation, the first server may determine that the information type is the account name type when the at least one parameter keyword includes a first parameter keyword for indicating an account name. And when the first server comprises a second parameter keyword for indicating the name of the address book contact person in at least one parameter keyword, determining the information type as the address book contact person type. The first server determines the information type to be a default type when the at least one parameter keyword does not include the first parameter keyword and the second parameter keyword.

Therefore, the information type is determined through the parameter keywords included by the parameter information, so that the relationship chain information corresponding to the type is generated according to different information types, and the generation of the relationship chain information is more targeted and more accurate.

Illustratively, if the RECO _ TEXT _ USER _ IDS is included in the at least one parameter key, the first server determines the information type as an account name type. And if the RECO _ TEXT _ CONTACT _ USER _ IDS is included in the at least one parameter key, the first server determines that the information type is the address book CONTACT type.

S107C: the first server generates relation chain information based on the information type, preset parameters corresponding to the current scene, a relation chain template, at least one parameter keyword and a value corresponding to each parameter keyword.

Optionally, the preset parameter is pre-stored in the first server, and the preset parameter may include at least one of the following: information display type (textType), first indication information and second indication information. The information display type is used for indicating the display type of the relationship chain information, the first indication information is used for indicating and displaying the head portrait corresponding to the account, and the second indication information is used for indicating and supporting the hyperlink function.

The information display type is a long information type or a short information type. When the information display type is a long information type, the relationship chain information includes a preset number of account names, that is, the number of explicit accounts (showUserCount) when the information display type is a long information type. And when the information display type is a short message type, the relation chain information does not comprise the account name.

Illustratively, the preset parameters include: the information presentation type (text type) is long, the number of the explicit users (show user count) is 3, whether a user avatar (headUrl) is displayed is Y, and whether a hyperlink (linkUrl) is supported is Y. The information display type (text type) used for representing the relationship chain information is a long information type. The number of the users in the display is 3, which is used for representing that only 3 related users are displayed, whether a user head portrait is displayed or not is Y used for representing that the head portrait of the related users is displayed, and whether a hyperlink is supported or not is Y used for representing: the support user account jumps to the home page of the relevant user by clicking on the avatar of the relevant user or the identification of the relevant user.

1. In the case where the information type is an account name type:

if the information type is the account name type, the first server may analyze the information display type included in the preset parameter. If the information display type is a long information type, and the account names of the preset number corresponding to the long information type are N account names, the first server may obtain a first value corresponding to the first parameter keyword, and obtain N identifiers of the accounts related to the first value, where the first value includes identifiers of all the accounts related to the type in which the login account and the target account have an account relationship. And then, the first server acquires an account name corresponding to the identifier of each related account according to the identifier of each related account in the identifiers of the N related accounts to obtain the N account names, analyzes account name placeholders in the relationship chain template, replaces the account name placeholders with the N account names, and generates relationship chain information. The relationship chain information includes N account names.

In this way, by including N account names corresponding to the identifiers of N accounts in the relationship chain information, the N account names are names that are easily recognized by the user, and the identifier-to-name conversion is realized. And only partial account names are displayed in the long information type, so that the guaranteed relationship chain is concise, and the user has a better impression.

Optionally, when the preset parameter further includes the first indication information, the first server may analyze the first indication information included in the preset parameter, and obtain the avatar address corresponding to the identifier of each related account according to the identifier of each related account in the N identifiers of the related accounts, where the relationship chain information may further include the N avatar addresses.

Therefore, the head portraits of the N accounts are displayed by the client when the relation chain is displayed by including the head portraits of the N accounts in the relation chain information, so that the displayed relation chain is more visual and concrete, and the user experience is improved.

Optionally, when the preset parameter further includes the second indication information, the first server may analyze the second indication information included in the preset parameter, and obtain a hyperlink corresponding to the identifier of each related account according to the identifier of each related account in the N identifiers of the related accounts, where the relationship chain information may further include the N hyperlinks.

Therefore, the relationship chain information comprises N hyperlinks corresponding to N accounts, so that the client can respond to the click operation of the user on the account head portrait and jump to the personal page of the account when displaying the relationship chain, the operation of the user is facilitated, and the user experience is improved.

Illustratively, in conjunction with the foregoing example, the RECO _ TEXT _ USER _ IDS and the RECO _ TEXT _ USER _ CNT are placeholders of the above-mentioned relational template. The placeholder reo _ TEXT _ USER _ IDS may be replaced with 123, 456, 789, 147, 258, 369 above, and the placeholder reo _ TEXT _ USER _ CNT may be replaced with 6.

2. And under the condition that the information type is the contact type of the address list:

if the information type is the address book contact type, the first server may generate the relationship chain information in a manner of generating the relationship chain information when the information type is the account name type. The first server obtains the corresponding address book contact name according to the identifier of each related address book contact in the N identifiers of related address book contacts, so that after the N address book contact names are obtained, the N address book contact names can be encrypted by using an encryption algorithm. The encryption algorithm is a pre-agreed encryption algorithm between the first server and the client so that the client can successfully decrypt.

3. In case the information type is a default type:

if the information type is the default type, the first server may analyze the quantity placeholders in the relationship chain template, and generate the relationship chain information by correspondingly replacing the quantity placeholders in the relationship chain template with values corresponding to the parameter keywords. The parameter key words are used for indicating the number of the related accounts with the account relation type between the login account and the target account.

Optionally, the default type also supports generation of relationship chain information that does not require placeholders.

In the default type, the conversion from the identification of an account or an address book contact person to the name is not required, and the flexible access of plain text type relationship chain information without a placeholder is supported.

The technical scheme at least has the following beneficial effects: the first server analyzes at least one parameter keyword and a corresponding value included in the parameter information, determines an information type according to the at least one parameter keyword, and generates relationship chain information based on the information type and pre-stored preset parameters, a relationship chain template, the at least one parameter keyword and the corresponding value corresponding to the current scene. Therefore, the information type is determined according to at least one parameter keyword, and the relationship chain information is generated by adopting different modes according to different information types. And, by pre-storing the preset parameters corresponding to the current scene in the first server, the relation chain information can be obtained and used when being generated.

Optionally, in this embodiment of the present disclosure, the first server may generate the relationship chain information based on the service scenario, the relationship chain template, and the parameter information, and specifically may include: the first server generates relation chain information in a preset format based on the service scene, the relation chain template and the parameter information. In this case, the step S104 of returning the relationship chain information to the client by the first server may include: and the first server sends the relationship chain information in a preset format to the client.

Therefore, the relationship chain information in the preset format is generated and returned to the client instead of being generated and returned to the client, so that the pressure of the first server for generating the relationship chain can be reduced, the client generates the relationship chain, the relationship chain is generated more flexibly, and the flexible access of the relationship chain is realized.

Optionally, in this embodiment of the present disclosure, after the first server sends the request message, preset information may also be sent to the client under the condition that the feedback information is not obtained, where the preset information is a plain text type information.

Therefore, when the second server cannot return the feedback information, the first server can return the bottom relation chain information to the client, and normal display of the relation chain at the client is guaranteed.

Optionally, in this embodiment of the present disclosure, the second server may, in response to an operation of adding a candidate account relationship type in a current scenario, obtain a priority of the candidate account relationship type, and establish a correspondence between an identifier of the current scenario and the candidate account relationship type, a correspondence between the candidate account relationship type and a candidate keyword, and a correspondence between the candidate keyword and a candidate relationship chain template. The second server may send the correspondence of the candidate keyword and the candidate relationship chain template to the information template database.

Therefore, the user can realize the generation of the relation chain only by establishing the corresponding relation between the identification of the current scene and the account relation type, the corresponding relation between the account relation type and the keyword and the corresponding relation between the keyword and the relation chain template in the second server, and the code does not need to be rewritten, so that the development and production efficiency is greatly improved.

Optionally, in this embodiment of the present disclosure, the second server may delete the correspondence between the identifier of the current scene and the offline account relationship type, and the correspondence between the offline account relationship type and the offline keyword, in response to a deletion operation on the offline account relationship type corresponding to the current scene. The second server may send deletion indication information to the information template database, where the deletion indication information is used to indicate that the correspondence between the downline keyword and the downline relationship chain template is deleted.

Therefore, the corresponding relation between the identifier of the current scene and the account relation type, the corresponding relation between the account relation type and the keyword, and the maintenance of the corresponding relation between the keyword and the relation chain template can be displayed to the operation user through the user interface. Thus, the operating user can maintain the corresponding relations through the user interface to modify the relation chain template, modify the keywords or modify the account relation type. Therefore, the user can achieve the purpose of uniformly modifying the display relation chain only by modifying at least one of the relation chain template, the keywords or the account relation type in the second server, and the code does not need to be modified, so that the development and production efficiency is greatly improved.

The foregoing describes the scheme provided by the embodiments of the present disclosure, primarily from a methodological perspective. To implement the above functions, it includes hardware structures and/or software modules for performing the respective functions. Those of skill in the art will readily appreciate that the present disclosure can be implemented in hardware or a combination of hardware and computer software for the various exemplary method steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

Fig. 5 is a block diagram illustrating a logical structure of an information generating apparatus 50 according to an exemplary embodiment. Referring to fig. 5, the information generating apparatus 50 includes: an acquisition module 501, a sending module 502 and a generation module 503.

An obtaining module 501, configured to obtain an identifier of a service scene and an identifier of a login account of a target application when a user account enters a page of the target application;

a sending module 502, configured to execute sending a request message, where the request message includes the identifier of the service scenario and the identifier of the login account, which are obtained by the obtaining module 501, and the request message is used to request to obtain feedback information, and the feedback information is used to generate relationship chain information;

the obtaining module 501 is further configured to perform obtaining the feedback information;

a generating module 503 configured to execute generating the relationship chain information based on the service scene and the feedback information acquired by the acquiring module 501, where the relationship chain information is used to generate a relationship chain to be displayed;

the sending module 502 is further configured to execute returning the relationship chain information generated by the generating module 503 to a client.

Optionally, the generating module 503 is specifically configured to execute:

analyzing the feedback information to obtain target keywords and parameter information, wherein the target keywords are keywords corresponding to the account relationship type corresponding to the service scene, and the parameter information comprises the identification and the number of the relevant accounts with the account relationship type between the login account and the target account;

acquiring a relation chain template corresponding to the target keyword from an information template database;

and generating the relation chain information based on the service scene, the relation chain template and the parameter information.

Optionally, when the identifier of the service scenario is an identifier of a current scenario, the account relationship type is a relationship type with a highest priority level in a plurality of account relationship types corresponding to the current scenario;

when the identifier of the service scene includes an identifier of a current scene and an identifier of an upstream scene, the account relationship type is a relationship type which is the same as the account relationship type corresponding to the upstream scene in a plurality of relationship types corresponding to the current scene, and the upstream scene is a last display scene of the current scene.

Optionally, the generating module 503 is specifically configured to execute:

analyzing the parameter information to obtain at least one parameter keyword included in the parameter information and a value corresponding to each parameter keyword:

determining an information type according to the at least one parameter keyword, wherein the information type is one of an account name type, an address list contact type and a default type;

generating the relationship chain information based on the information type, preset parameters corresponding to the current scene, the relationship chain template, the at least one parameter keyword and a value corresponding to each parameter keyword, wherein the preset parameters are pre-stored in the server and include at least one of the following parameters: the system comprises an information display type, first indication information and second indication information, wherein the information display type is used for indicating the display type of the relation chain information, the first indication information is used for indicating that a head portrait corresponding to an account is displayed, and the second indication information is used for indicating that a hyperlink function is supported.

Optionally, the generating module 503 is specifically configured to execute:

when the at least one parameter keyword comprises a first parameter keyword used for indicating an account name, determining that the information type is the account name type;

when the at least one parameter keyword comprises a second parameter keyword used for indicating the name of the address book contact person, determining that the information type is the type of the address book contact person;

determining the information type as the default type when the first parameter keyword and the second parameter keyword are not included in the at least one parameter keyword.

Optionally, when the preset parameter includes the information presentation type, the generating module 503 is specifically configured to execute:

if the information type is the account name type, analyzing the information display type included by the preset parameters, wherein the information display type is a long information type or a short message type, when the information display type is the long information type, the relationship chain information includes a preset number of account names, and when the information display type is the short message type, the relationship chain information does not include the account names;

if the information display type is the long information type and the preset number of account names corresponding to the long information type are N account names, acquiring a first value corresponding to the first parameter keyword, and acquiring N identifications of related accounts in the first value, wherein the first value comprises the identifications of all related accounts with the account relation type between the login account and the target account;

acquiring an account name corresponding to the identifier of each related account according to the identifier of each related account in the N identifiers of the related accounts to obtain N account names;

analyzing account name placeholders in the relationship chain template;

and replacing the account name placeholders with the N account names to generate the relationship chain information, wherein the relationship chain information comprises the N account names.

Optionally, when the preset parameter further includes the first indication information, as shown in fig. 6, the information generating apparatus further includes: a parsing module 504;

the parsing module 504 is configured to perform parsing on the first indication information included in the preset parameter;

the obtaining module 501 is further configured to perform obtaining, according to the identifier of each related account in the N identifiers of related accounts, an avatar address corresponding to the identifier of each related account, where the relationship chain information further includes the N avatar addresses.

Optionally, the parsing module 504 is configured to perform parsing on the second indication information included in the preset parameter;

the obtaining module 501 is further configured to perform obtaining a hyperlink corresponding to each identifier of the relevant account according to the identifier of each relevant account in the N identifiers of the relevant account, where the relationship chain information further includes N hyperlinks.

Optionally, the generating module 503 is specifically configured to execute:

if the information type is the default type, analyzing the quantity placeholder in the relation chain template;

and correspondingly replacing the quantity placeholder in the relation chain template with a value corresponding to a parameter keyword to generate the relation chain information, wherein the parameter keyword is used for indicating that the login account and the target account have the quantity of the related account with the account relation type.

Optionally, the generating module 503 is specifically configured to execute:

generating relation chain information in a preset format based on the service scene, the relation chain template and the parameter information;

the sending module 502 is specifically configured to execute:

and sending the relation chain information in the preset format to the client.

Optionally, the sending module 502 is further configured to execute sending preset information to the client when the feedback information is not obtained, where the preset information is a plain text type information.

Fig. 7 is a block diagram illustrating a logical structure of an information generating apparatus 70 according to an exemplary embodiment. Referring to fig. 7, the information generating apparatus 70 includes: a receiving module 701, a generating module 702 and a sending module 703.

A receiving module 701, configured to execute receiving a request message, where the request message includes an identifier of a service scene of a target application and an identifier of a login account, and the request message is used to request to obtain feedback information, and the feedback information is used to generate relationship chain information;

a generating module 702 configured to execute generating the feedback information according to the identifier of the service scenario and the identifier of the login account received by the receiving module;

a sending module 703 configured to perform sending the feedback information generated by the generating module.

Optionally, the feedback information includes a target keyword and parameter information, and the generating module 702 is specifically configured to execute:

determining a corresponding account relation type according to the identification of the service scene;

acquiring the target keywords corresponding to the account relation type;

determining the parameter information according to the account relationship type and the identification of the login account, wherein the parameter information comprises the identification and the number of the related accounts with the account relationship type between the login account and the target account;

and generating the feedback information according to the target keyword and the parameter information.

Optionally, the generating module 702 is specifically configured to execute:

and when the identifier of the service scene is the identifier of the current scene, determining the relationship type with the highest priority in the plurality of relationship types corresponding to the current scene as the account relationship type.

Optionally, the generating module 702 is specifically configured to execute:

when the identifier of the service scene includes an identifier of a current scene and an identifier of an upstream scene, determining a relationship type, which is the same as an account relationship type corresponding to the upstream scene, from among a plurality of relationship types corresponding to the current scene as the account relationship type, where the upstream scene is a last display scene of the current scene.

Optionally, as shown in fig. 7, the information generating apparatus further includes: a setup module 704;

the obtaining module 701 is further configured to perform an operation of adding a candidate account relationship type in response to a current scenario, and obtain a priority of the candidate account relationship type;

the establishing module 704 is configured to perform establishing a correspondence between the identifier of the current scene and the candidate account relationship type, a correspondence between the candidate account relationship type and a candidate keyword, and a correspondence between the candidate keyword and a candidate relationship chain template;

the sending module 703 is further configured to execute sending, to an information template database, the correspondence between the candidate keyword and the candidate relationship chain template.

Optionally, as shown in fig. 7, the information generating apparatus further includes: a deletion module 705;

a deleting module 705, configured to execute a deleting operation in response to a offline account relationship type corresponding to a current scene, and delete a correspondence between an identifier of the current scene and the offline account relationship type and a correspondence between the offline account relationship type and an offline keyword;

the sending module 703 is further configured to execute sending deletion indication information to an information template database, where the deletion indication information is used to indicate that the corresponding relationship between the offline keyword and the offline relationship chain template is deleted.

Fig. 8 is a block diagram illustrating a configuration of a server, which may be an information generating apparatus, according to an exemplary embodiment. The server may vary significantly depending on configuration or performance, and may include one or more processors 81 and one or more memories 82. At least one instruction is stored in the memory 82, and the at least one instruction is loaded and executed by the processor 81 to implement the information generating method provided by the above-mentioned method embodiments. Of course, the server may also have components such as a wired or wireless network interface, a keyboard, and an input/output interface, so as to perform input/output, and the server may also include other components for implementing the functions of the device, which are not described herein again.

In an exemplary embodiment, the disclosed embodiments also provide a computer program product comprising one or more instructions executable to perform the above-described method.

In an exemplary embodiment, the present disclosure provides a computer-readable storage medium, where instructions in the storage medium are executed by a processor of a server, so that the server can execute the instructions in the storage medium or one or more instructions in a computer program product to implement the processes of the foregoing method embodiments, and can achieve the same technical effects, and in order to avoid repetition, the details are not described here again.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. An information generation method applied to a server is characterized by comprising the following steps:

when a user account enters a page of a target application, acquiring an identifier of a service scene of the target application and an identifier of a login account;

sending a request message, wherein the request message comprises an identifier of the service scene and an identifier of the login account, and is used for requesting to acquire feedback information which is used for generating relationship chain information;

acquiring the feedback information;

generating the relationship chain information based on the service scene and the feedback information, wherein the relationship chain information is used for generating a relationship chain to be displayed;

and returning the relation chain information to the client.

2. The information generating method according to claim 1, wherein the generating the relationship chain information based on the service scenario and the feedback information includes:

3. The information generating method according to claim 2,

when the identifier of the service scene is the identifier of the current scene, the account relationship type is the relationship type with the highest priority in the plurality of account relationship types corresponding to the current scene;

4. The information generating method according to claim 2 or 3, wherein the generating the relationship chain information based on the service scenario, the relationship chain template, and the parameter information includes:

analyzing the parameter information to obtain at least one parameter keyword included in the parameter information and a value corresponding to each parameter keyword;

5. An information generating method, comprising:

receiving a request message, wherein the request message comprises an identifier of a service scene of a target application and an identifier of a login account, the request message is used for requesting to acquire feedback information, and the feedback information is used for generating relationship chain information;

generating the feedback information according to the identification of the service scene and the identification of the login account;

and sending the feedback information.

6. An information generating apparatus applied to a server, comprising:

the acquisition module is configured to acquire an identifier of a service scene and an identifier of a login account of a target application when a user account enters a page of the target application;

a sending module configured to execute sending a request message, where the request message includes the identifier of the service scenario and the identifier of the login account, where the request message is used to request to obtain feedback information, and the feedback information is used to generate relationship chain information;

the obtaining module is further configured to perform obtaining the feedback information;

the generating module is configured to execute generating the relationship chain information based on the service scene and the feedback information acquired by the acquiring module, wherein the relationship chain information is used for generating a relationship chain to be displayed;

the sending module is further configured to execute returning the relationship chain information generated by the generating module to a client.

7. An information generating apparatus, characterized by comprising:

the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is configured to execute receiving of a request message, the request message comprises an identifier of a service scene of a target application and an identifier of a login account, the request message is used for requesting to acquire feedback information, and the feedback information is used for generating relationship chain information;

the generating module is configured to execute the generation of the feedback information according to the identification of the service scene and the identification of the login account received by the receiving module;

a transmitting module configured to perform transmitting the feedback information generated by the generating module.

8. A server, comprising:

a processor;

a memory for storing the processor-executable instructions; wherein the processor is configured to execute the executable instructions to implement the information generation method of any one of claims 1-4 or to implement the information generation method of claim 5.

9. A computer-readable storage medium, wherein instructions in the computer-readable storage medium, when executed by a processor of a server, enable the server to perform the information generation method of any one of claims 1-4 or perform the information generation method of claim 5.

10. A computer program product, characterized in that it comprises computer instructions which, when run on a computer device, cause the computer device to perform the information generation method of any one of claims 1-4, or to perform the information generation method of claim 5.