Message transmission method, display method, apparatus, electronic device, and storage medium

Abstract

The application discloses a message transmission method and device, a display method and device, electronic equipment and a storage medium, and belongs to the technical field of computers. The application pushes a notification message of a first application to notify how many friends meeting an authentication condition are currently using a second application, encourages a target account to spontaneously join and use the second application under the driving of a relationship chain, realizes account diversion from the first application to the second application, and thus does not need an administrator to manually invite the target account in the second application, and can improve information acquisition efficiency and man-machine interaction efficiency of a user for an invitation type notification message of the second application.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a message transmission method, display method, device, electronic device, and storage medium. Background Technology

[0002] With the development of computer technology and the diversification of terminal functions, some instant messaging (IM) applications suitable for office scenarios have gradually become popular. These IM applications can facilitate quick communication among employees within the same company and also support social interaction among employees of different companies.

[0003] With the increasing demand for internal office communication, enterprise administrators often manually invite new employees to join and activate their company in IM applications. This can be done through methods such as sending SMS or IM messages. However, since these SMS or IM messages may be ignored by new employees or blocked by the device and collapsed into the system message inbox, the success rate of inviting new employees is low. Furthermore, enterprise administrators need to periodically check for employees who have not yet activated their company and then manually invite them again. In short, when inviting new users to office IM applications, the efficiency of users receiving invitation messages is low, and the human-computer interaction efficiency is also low. Summary of the Invention

[0004] This application provides a message transmission method, display method, device, electronic device, and storage medium, which can provide a way to redirect a target account from a first application to a second application, thereby improving the efficiency of users obtaining information from invitation messages in the second application and the efficiency of human-computer interaction. The technical solution is as follows:

[0005] On the one hand, a message transmission method is provided, executed by a server, the method comprising:

[0006] Obtain multiple first accounts that are associated with the target account in the first application, wherein the target account has a history of authorized login to a second application associated with the first application;

[0007] From the plurality of first accounts, a plurality of second accounts are obtained, and the second accounts meet the authentication conditions of the second application;

[0008] In the first application, a notification message is pushed to the target account. The notification message is used to notify the target account that the multiple second accounts are using the second application.

[0009] On one hand, a message display method is provided, executed by a terminal, wherein a target account is logged into a first application on the terminal, and the target account has a history of authorized logins to a second application associated with the first application. The method includes:

[0010] The system receives a notification message from the server, which is used to notify the target account that multiple second accounts are using the second application, and that the second accounts meet the authentication conditions of the second application and are associated with the target account in the first application.

[0011] In the first application, the notification message is displayed.

[0012] On one hand, a message transmission device is provided, the device comprising:

[0013] The first acquisition module is used to acquire multiple first accounts that are associated with the target account in the first application, wherein the target account has a history of authorized login to the second application associated with the first application;

[0014] The filtering module is used to filter out multiple second accounts from the multiple first accounts, wherein the second accounts meet the authentication conditions of the second application;

[0015] The push module is used to push notification messages to the target account in the first application, and the notification messages are used to notify the target account that the plurality of second accounts are using the second application.

[0016] In one possible implementation, the notification message is further used to provide an entry point for viewing statistical information of at least one target object in the second application, the statistical information being used to characterize the number of second accounts associated with the target object in the second application;

[0017] The device further includes:

[0018] A first determining module is configured to determine the at least one target object from the second application, wherein the target object is activated by at least one second account in the second application;

[0019] The second acquisition module is used to acquire statistical information on the number of second accounts that have been activated for each target object in the second application;

[0020] The storage module is used to associate and store the account identifier of the target account with the statistical information of each of the at least one target object.

[0021] In one possible implementation, the device further includes:

[0022] The second determining module is used to determine the account identifier of the target account carried in the information retrieval request in response to receiving an information retrieval request triggered based on the notification message;

[0023] The return module is used to return statistical information of the at least one target object that is associated with the account identifier.

[0024] In one possible implementation, the second account includes at least one of the following:

[0025] It has a history of authorized logins in the second application and has not yet revoked authorization; or,

[0026] An account in the first application has been associated with an account in the second application, and authorization has not yet been revoked; or,

[0027] The account is in an account group that includes the account of the second application, and authorization has not yet been revoked; or,

[0028] The first application followed the object account of any object in the second application.

[0029] In one possible implementation, the device further includes:

[0030] The third determining module is used to determine the target account in the first application that meets the message push conditions.

[0031] In one possible implementation, the message push conditions include:

[0032] The target account has a history of authorized login in the second application and has not yet revoked the authorization; and the target account is authorized to retrieve the association relationship of the target account in the first application; and the activity level of the target account in the second application is less than the activity level threshold.

[0033] On one hand, a message display device is provided, wherein a target account is logged into a first application of the device, and the target account has a history of authorized logins to a second application associated with the first application; the device includes:

[0034] A receiving module is used to receive a notification message from the server. The notification message is used to notify the target account that multiple second accounts are using the second application. The second accounts meet the authentication conditions of the second application and are associated with the target account in the first application.

[0035] The display module is used to display the notification message in the first application.

[0036] In one possible implementation, the device further includes:

[0037] The sending module is used to send an information retrieval request carrying the account identifier of the target account to the server in response to the triggering operation of the notification message.

[0038] The receiving module is further configured to receive statistical information of at least one target object in the second application returned by the server based on the information retrieval request, wherein the statistical information represents the number of second accounts associated with the target object in the second application;

[0039] The display module is also used to display statistical information of the at least one target object in the first application.

[0040] In one possible implementation, the display module is further configured to:

[0041] In the display area of ​​the statistics information for each target object, the number of second accounts associated with the target object in the second application is displayed, as well as the profile picture of some of the second accounts associated with the target object.

[0042] In one possible implementation, when displaying the statistical information, the display module also displays a switching control, which is used to switch from the first application to the second application;

[0043] The device further includes:

[0044] A jump module is used to jump from the first application to the second application in response to a trigger operation of the switching control.

[0045] In one possible implementation, the device further includes:

[0046] The determination module is used to determine the account or account group to be shared in response to a business card sharing instruction triggered from the second application;

[0047] The sending module is used to send the business card information of the target account in the second application to the account or account group to be shared via the server;

[0048] The display module is also used to display the business card information in a conversation interface with the account or account group to be shared.

[0049] On one hand, an electronic device is provided, comprising one or more processors and one or more memories, wherein at least one computer program is stored in the one or more memories, the at least one computer program being loaded and executed by the one or more processors to implement a message transmission method or a message display method as described in any of the possible implementations above.

[0050] On the one hand, a storage medium is provided that stores at least one computer program, which is loaded and executed by a processor to implement a message transmission method or a message display method as described in any of the possible implementations above.

[0051] On one hand, a computer program product or computer program is provided, the computer program product or computer program comprising one or more lines of program code, the one or more lines of program code being stored in a computer-readable storage medium. One or more processors of an electronic device are capable of reading the one or more lines of program code from the computer-readable storage medium, and the one or more processors execute the one or more lines of program code, enabling the electronic device to perform a message transmission method or message display method according to any of the above possible embodiments.

[0052] The beneficial effects of the technical solutions provided in this application include at least the following:

[0053] By pushing notification messages to target accounts that have a history of authorized login to the second application in the first application, the system can notify users of how many friends who meet the authentication criteria are currently using the second application. This incentivizes target accounts to spontaneously join and use the second application based on their social networks, thus driving traffic from the first application to the second application. This eliminates the need for administrators to manually invite target accounts in the second application, improving the efficiency of users receiving invitation notifications from the second application and enhancing human-computer interaction efficiency. Attached Figure Description

[0054] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0055] Figure 1 This is a schematic diagram illustrating the implementation environment of a message transmission method provided in an embodiment of this application;

[0056] Figure 2 This is a flowchart of a message transmission method provided in an embodiment of this application;

[0057] Figure 3 This is an interactive flowchart of a message transmission method provided in an embodiment of this application;

[0058] Figure 4 This is a schematic diagram illustrating the principle of filtering target accounts provided in an embodiment of this application;

[0059] Figure 5This is a schematic diagram illustrating the principle of retrieving a first account, provided in an embodiment of this application.

[0060] Figure 6 This is a schematic diagram illustrating the principle of filtering a second account, provided in an embodiment of this application.

[0061] Figure 7 This is a schematic diagram illustrating the principle of finding a target object according to an embodiment of this application;

[0062] Figure 8 This is a schematic flowchart illustrating the principle of storing statistical information provided in an embodiment of this application;

[0063] Figure 9 This is a schematic diagram of a details browsing interface provided in an embodiment of this application;

[0064] Figure 10 This is a schematic diagram of an interactive interface provided in an embodiment of this application;

[0065] Figure 11 This is a schematic diagram of the functional interface of a second application provided in an embodiment of this application;

[0066] Figure 12 This is a schematic diagram of a session interface provided in an embodiment of this application;

[0067] Figure 13 This is a schematic diagram of an account information interface provided in an embodiment of this application;

[0068] Figure 14 This is a schematic diagram of the structure of a message transmission device provided in an embodiment of this application;

[0069] Figure 15 This is a schematic diagram of the structure of a message display device provided in an embodiment of this application;

[0070] Figure 16 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0071] Figure 17 This is a schematic diagram of the structure of a server provided in an embodiment of this application. Detailed Implementation

[0072] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0073] In this application, the terms "first," "second," etc., are used to distinguish identical or similar items with essentially the same function. It should be understood that there is no logical or temporal dependency between "first," "second," and "nth," nor are there any restrictions on quantity or execution order.

[0074] In this application, the term "at least one" means one or more, and "multiple" means two or more, for example, multiple first positions means two or more first positions.

[0075] The term "including at least one of A or B" in this application refers to the following situations: including only A, including only B, and including both A and B.

[0076] The user-related data involved in this application, such as the association relationship of the user's target account in the first application, the relevant data on whether the first account has authorized the second application, and the relevant data on whether the second account has activated the target object in the second application, etc., when the method of the embodiments of this application is applied to specific products or technologies, it is necessary to obtain the user's permission or consent or full authorization, and the collection, use and processing of the relevant data must comply with the relevant laws and regulations and national standards of the country.

[0077] Figure 1 This is a schematic diagram illustrating the implementation environment of a message transmission method provided in an embodiment of this application. See also... Figure 1 The implementation environment includes terminal 101 and server 102, which will be described below.

[0078] Terminal 101 has a first application and a second application installed. The first application is an instant messaging (IM) client that is more social, and the second application is an instant messaging client that is more office-oriented. The first application and the second application are interconnected. This interconnection means that, after user authorization or full authorization, users can log in to the second application using an account registered in the first application, or users can log in to the first application using an account registered in the second application, or users can bind the account registered in the first application and the account registered in the second application after user authorization or full authorization. In other words, after user authorization or full authorization, the user's account information can be shared between the first application and the second application.

[0079] Optionally, the first application includes, but is not limited to: social applications, IM applications, dating applications, microblogging applications, etc., and the second application includes, but is not limited to: enterprise applications, office applications, attendance applications, check-in applications, etc. The difference between the first application and the second application is that the first application is usually used to meet the user's social needs, such as communicating with friends or making new friends, while the second application is used to meet the user's office needs, such as communicating or exchanging ideas with colleagues in other departments within the company, or communicating or exchanging ideas with customers, etc.

[0080] Terminal 101 and server 102 can be connected directly or indirectly via wired or wireless communication, and this application does not impose any restrictions on this.

[0081] Server 102 is used to push notification messages to the first application on terminal 101. That is, if the user has authorized or fully authorized the access permissions of the target account information of the user in the first application to the second application, then under certain message push conditions (such as detecting that the target account has low activity in the second application), a notification message is pushed to the first application on terminal 101 to notify the user that many of the user's friends in the first application (i.e., the filtered second accounts) are using the second application. This can effectively attract the user to join and use the second application spontaneously, thus achieving effective traffic redirection from the first application to the second application.

[0082] In some embodiments, in order to drive traffic, statistical information of the target object that is activated by at least one second account in the second application is obtained for each target account. The statistical information is used to characterize the number of second accounts associated with the target object in the second application. The target object refers to an organizational entity created in the second application. The organizational entity includes, but is not limited to, enterprises, public institutions, non-legal person organizations, etc. The embodiments of this application do not specifically limit this.

[0083] Server 102 may be an independent message push server or a backend server for the primary application. Server 102 may include at least one of the following: a single server, multiple servers, a cloud computing platform, or a virtualization center. Optionally, in the calculation process of the aforementioned statistical information, server 102 undertakes the primary calculation work, and terminal 101 undertakes the secondary calculation work; or server 102 undertakes the secondary calculation work, and terminal 101 undertakes the primary calculation work; or terminal 101 and server 102 may use a distributed computing architecture for collaborative calculation.

[0084] In some embodiments, server 102 is an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms.

[0085] In some embodiments, terminal 101 refers to one of a plurality of terminals. The device type of terminal 101 includes, but is not limited to, smartphones, tablets, laptops, desktop computers, smart speakers, smartwatches, in-vehicle terminals, smart home appliances, smart voice interaction devices, etc. For example, terminal 101 is a smartphone or other handheld portable communication device.

[0086] The message transmission method involved in this application embodiment can be applied to various scenarios, including but not limited to: cloud computing, artificial intelligence, smart transportation, and assisted driving.

[0087] Those skilled in the art will know that the number of terminals 101 may be more or less. For example, there may be only one terminal 101, or dozens or hundreds, or more. This application embodiment does not specifically limit the number of terminals 101 or the type of device.

[0088] Figure 2 This is a flowchart of a message transmission method provided in an embodiment of this application. See also... Figure 2 This embodiment is executed by an electronic device. Taking the electronic device as a server as an example, this embodiment includes the following steps:

[0089] 201. The server obtains multiple first accounts that are associated with the target account in the first application, and the target account has a history of authorized login to the second application associated with the first application.

[0090] The server is used to push notification messages to the first application. For example, the server may be an independent message push server or a background server for the first application. This application embodiment does not specifically limit the type of server.

[0091] The first application refers to a social-oriented instant messaging client, and the second application refers to an office-oriented instant messaging client. The first and second applications are interconnected. This interconnection means that, after user authorization or full authorization, users can log in to the second application using an account registered in the first application; or, after user authorization or full authorization, users can log in to the first application using an account registered in the second application; or, after user authorization or full authorization, users can bind the account registered in the first application and the account registered in the second application. In other words, after user authorization or full authorization, the user's account information can be shared between the first and second applications.

[0092] A target account refers to an account used in the first application to log in to a second application, where the user previously authorized or fully authorized the second application. In other words, the target account is an account in the first application, but it has a history of being authorized to log in to the second application after being authorized or fully authorized by the user.

[0093] To illustrate, a user registers and uses the account "123456" for social interaction in the first application, but has not registered any account in the second application. If the user wants to log in to the second application, given that the first and second applications are linked, an option to log in based on authorization from the first application is provided. After clicking the option and confirming authorization, the user can log in to the second application using the account "123456", thus avoiding a series of cumbersome processes such as registering and logging in with a new account in the second application.

[0094] In some embodiments, the server detects each account with a history of authorized login to the second application from the account database, identifies each detected account as a target account, and executes the method of this embodiment for each target account to push corresponding notification messages to all target accounts.

[0095] In other embodiments, after the server detects each account authorized to log in to the second application from the account database, it filters out target accounts from the detected accounts. For example, it filters out target accounts with low activity in the second application from the detected accounts. The method of the present application embodiment is executed for each of the filtered target accounts, so that the corresponding notification message is pushed only to the target accounts with low activity in the second application, and no notification message needs to be pushed to the accounts with high activity in the second application, which can further realize the accurate push of notification messages.

[0096] After the server determines the target account through the above method, it queries the relationship chain of the target account in the first application to obtain multiple first accounts that are associated with the target account. The association relationship between accounts involved in this application embodiment includes at least one of strong association relationship or weak association relationship. Indicatively, the strong association relationship refers to a two-way association relationship, which means that the target account and the first account are mutually associated. The weak association relationship refers to a one-way association relationship, which means that the target account unilaterally establishes a one-way association relationship with the first account, but the first account itself does not establish an association relationship with the target account, or the first account once established an association relationship with the target account but later the first account terminated the association relationship with the target account. This application embodiment does not specifically limit the type of association relationship.

[0097] To illustrate, for some social networking applications, a two-way relationship usually refers to a two-way friend relationship, and a one-way relationship refers to a one-way friend relationship. A two-way friend relationship means that the target account is a friend of the first account, and the first account is also a friend of the target account. A one-way friend relationship means that the first account is a friend of the target account, but the target account is not a friend of the first account.

[0098] To illustrate, for some content generation or sharing applications, a two-way association usually refers to a two-way following relationship, while a one-way association refers to a one-way following relationship. A two-way following relationship means that the target account follows the first account, and the first account also follows the target account, that is, the target account and the first account follow each other and are each other's fans. A one-way following relationship means that the target account follows the first account, but the first account does not follow the target account, that is, the target account is a fan of the first account.

[0099] In some embodiments, the server maintains a relationship chain for the first application, which is used to represent the association between various accounts using the first application. This relationship chain is also called a social relationship chain. For example, in a social application, this relationship chain usually involves a friend relationship chain and a group relationship chain. The server obtains multiple first accounts that are associated with the target account from the friend relationship chain. Or, for example, in a content generation application or content sharing application, this relationship chain usually involves a follow relationship chain. The server obtains multiple first accounts that are associated with the target account from the follow relationship chain.

[0100] Optionally, the relationship chain is a topological graph of a social network stored in the form of graph data. In this topological graph, each node represents an account, and each directed edge represents the association between the two accounts corresponding to the two endpoints of the directed edge. For example, in the topological graph, account A corresponds to node 1, and account B corresponds to node 2. Between node 1 and node 2, if there is only a directed edge from node 1 to node 2, it means that account A and account B have a one-way association. If there is only a directed edge from node 2 to node 1, it means that account B and account A have a one-way association. If there are both directed edges from node 1 to node 2 and from node 2 to node 1, it means that account A and account B have a two-way association.

[0101] In some embodiments, when querying the first account based on the above topology graph, the account identifier (ID) of the target account is used as the index to query the target node corresponding to the target account in the topology graph, and the node set consisting of the endpoints of each directed edge starting from the target node is obtained. The accounts corresponding to all nodes in the node set are determined as the multiple first accounts. At this time, all accounts with unidirectional and bidirectional association relationships with the target account can be obtained as the first accounts.

[0102] In some embodiments, when querying the first account based on the above topological relationship graph, the account identifier of the target account is used as an index to query the target node corresponding to the target account in the topological relationship graph. After obtaining the node set consisting of the endpoints of each directed edge starting from the target node, for each node in the node set, it is determined whether there is a directed edge pointing to the target node. If there is no directed edge pointing to the target node, it means that there is only a one-way association relationship, so the current node is deleted from the node set. If there is a directed edge pointing to the target node, it means that there is a two-way association relationship, so the current node is skipped and the next node is judged. Thus, after traversing the node set, accounts with one-way association relationships with the target account can be filtered out from the node set, and only accounts with two-way association relationships with the target account are retained in the final node set. The accounts corresponding to all nodes in the final node set are determined as the multiple first accounts, so that all accounts with two-way association relationships with the target account can be obtained as the first accounts.

[0103] Optionally, the relationship chain is stored as a key-value pair structure. In this relationship chain data, the account identifier or hash value of each account is used as the key, and the account identifiers of each account associated with that account are used as the values. That is, the key is a collection of account identifiers. For example, in the key-value pair structure of account A, if the account identifier or hash value of account A is used as the key and the value contains the account identifier of account B, it means that account A and account B have a one-way association. If, at the same time, in the key-value pair structure of account B, if the account identifier or hash value of account B is used as the key and the value also contains the account identifier of account A, it means that account A and account B have a two-way association.

[0104] In some embodiments, when querying a first account based on the above key-value pair structure, if the key name of the key-value pair structure is an account identifier, then the key value in the key-value pair structure indicated by the target account is queried using the account identifier of the target account as an index. If the key name of the key-value pair structure is a hash value of the account identifier, then the key value in the key-value pair structure indicated by the hash value of the account identifier of the target account is queried using the hash value of the account identifier of the target account as an index. Finally, the account identifiers of each first account that are associated with the target account can be retrieved from the key value. At this time, all accounts that have one-way and two-way association relationships with the target account can be obtained as first accounts.

[0105] In some embodiments, when querying a first account based on the above key-value pair structure, if the key name of the key-value pair structure is an account identifier, then the key value in the key-value pair structure indicated by the target account is queried using the account identifier of the target account as an index. If the key name of the key-value pair structure is a hash value of the account identifier, then the key value in the key-value pair structure indicated by the hash value of the account identifier of the target account is queried using the hash value of the account identifier of the target account as an index. Finally, the account identifiers of each account associated with the target account are obtained, and the set of account identifiers of these accounts is cached. Next, for each element in the set, using that element as an index, and based on a similar query method, we check whether the key-value pair structure indicated by the index matches the account identifier of the target account. If the account identifier of the target account is not matched, it means that there is only a one-way association relationship, so the current element is deleted from the cached set (here only the cached data is deleted, without changing any underlying key-value pair structure). If the account identifier of the target account is matched, it means that there is a two-way association relationship, so the current element is skipped and the next element is processed. Thus, after traversing the above cached set, accounts with one-way association relationships with the target account can be filtered out from the cached set, and only accounts with two-way association relationships with the target account are retained in the final set. The accounts indicated by each element (i.e., account identifier) ​​in the final set are determined as the multiple first accounts, so that all accounts with two-way association relationships with the target account can be obtained as the first accounts.

[0106] 202. The server selects multiple second accounts from the multiple first accounts, and the second accounts meet the authentication conditions of the second application.

[0107] After obtaining multiple primary accounts that are associated with the target account, since not every primary account has authorized the secondary application, it is necessary to filter out multiple secondary accounts that meet the authentication conditions of the secondary application from these primary accounts.

[0108] Optionally, the authentication criteria for the second application include authorizing login using an account from the first application within the second application. In this case, the server identifies the first account from among the multiple first accounts that has a history of authorizing login in the second application and has not yet revoked its authorization as the second account. In other words, if the user corresponding to the first account has previously authorized login to the second application using the first account, and the first account has not yet revoked its authorization, then the first account meets the authentication criteria, and the first account is determined to belong to the second account.

[0109] Optionally, the authentication condition for the second application includes adding any account of the second application as a friend in the first application (i.e., establishing a connection between the account in the first application and the account in the second application). In this case, the server identifies the first account from among the multiple first accounts that has established a connection between the first application and the account in the second application and has not yet revoked authorization as the second account. In other words, if any account in the friend relationship chain of the first account has been authorized to communicate with the first application from the second application, and that first account has not yet revoked authorization, then the first account meets the authentication condition, and the first account is determined to belong to the second account.

[0110] Optionally, the authentication condition for the second application includes joining any account group containing the account of the second application in the first application (i.e., the account in the first application and the account of the second application are in the same account group). In this case, the server identifies the first account that is in the account group containing the account of the second application and has not yet revoked its authorization as the second account from among the multiple first accounts. In other words, if there is any account in the group relationship chain of the first account that has been authorized to communicate with the first application from the second application, and the first account has not yet revoked its authorization, then the first account meets the authentication condition and is determined to belong to the second account.

[0111] Optionally, the authentication conditions for the second application include an object account that has followed any object in the second application from the first application. Here, each object in the second application uniquely corresponds to an organizational entity, which includes, but is not limited to, enterprises, public institutions, and non-legal person organizations. This embodiment does not specifically limit this. In this case, the server determines the first account that has followed any object account in the second application from among the multiple first accounts as the second account. In other words, if the first account has followed any authorized object account that communicates with the first application from the second application (e.g., an enterprise account), and the first account has not unfollowed it, then the first account meets the authentication conditions, and the first account is determined to belong to the second account.

[0112] 203. The server pushes a notification message to the target account in the first application. The notification message is used to notify the target account that the multiple second accounts are using the second application.

[0113] In some embodiments, after obtaining the first account in step 201 and filtering out the second account from the first account in step 202, a notification message is pushed to the target account to notify that multiple second accounts are using the second application. Since the second account itself is filtered out from the first account that has a relationship with the target account (such as a friend relationship), under the premise of notifying the user that many friends are using the second application, given that the target account usually has a high degree of trust in its own social relationship chain, it can effectively attract the user to spontaneously join and use the second application, that is, to achieve effective traffic diversion from the first application to the second application for the user.

[0114] In some embodiments, the server obtains the number of each second account selected in step 202 above and carries the number of accounts in the notification message. This notification message can intuitively prompt the target account about the number of second accounts using the second application, which can further enhance the user's motivation to use the second application.

[0115] In some embodiments, for the purpose of traffic redirection, statistical information of the target object activated by at least one second account in the second application is further obtained for each target account. This statistical information is used to characterize the number of second accounts associated with the target object in the second application. After the account identifier and statistical information of each target account are associated and stored, if a user views a notification message in the first application and wants to access more details, after triggering the notification message, the server will return the associated and stored statistical information to the target account, so that the terminal can view the statistical information in the first application. The method of obtaining the statistical information will be described in detail in the next embodiment.

[0116] All of the above-mentioned optional technical solutions can be combined in any way to form optional embodiments of this disclosure, and will not be described in detail here.

[0117] The method provided in this application pushes notification messages to target accounts that have a history of authorized login to the second application in the first application, so as to notify how many friends who meet the authentication conditions are currently using the second application. This can incentivize target accounts to spontaneously join and use the second application under the relationship chain, thereby realizing the account traffic from the first application to the second application. This also eliminates the need for the administrator to manually invite target accounts in the second application, which can improve the efficiency of users obtaining information from invitation-type notification messages of the second application and the efficiency of human-computer interaction.

[0118] The above embodiments briefly describe how the server pushes notification messages to the target account. Since message transmission includes both server-side push messages and terminal-side display messages, this application embodiment will detail how the two devices interact to achieve information transmission. The terminal and server are exemplary embodiments of electronic devices. Figure 3 This is an interactive flowchart of a message transmission method provided in an embodiment of this application, such as... Figure 3 As shown, this embodiment includes the following steps:

[0119] 301. The server determines the target account in the first application that meets the message push conditions.

[0120] In some embodiments, when the message push condition is to authorize login to the second application, the server determines the target account as an account that has a history of authorized login in the second application and has not yet revoked authorization, based on the method described in step 201 of the above embodiments.

[0121] In other embodiments, when the message push condition is to authorize login to the second application and authorize access to the address book of the first application, the server determines, based on the method described in step 201 of the above embodiments, an account with a history of authorized login in the second application and which has not yet revoked authorization as a candidate account. Further, it determines whether the candidate account has authorized the second application to retrieve its association relationship in the first application. If the candidate account has authorized the second application to retrieve its association relationship in the first application and has not yet revoked authorization, then the candidate account is determined to be the target account.

[0122] In other embodiments, when the message push conditions are authorizing login to the second application, authorizing access to the address book of the first application, and having low activity in the second application, the server determines, based on the method described in step 201 of the above embodiments, an account with a history of authorized login in the second application that has not yet revoked authorization as a candidate account. Further, it determines whether the candidate account has authorized the second application to retrieve its association relationship in the first application. If the candidate account has authorized the second application to retrieve its association relationship in the first application and has not yet revoked authorization, it further obtains the activity level of the candidate account in the second application. If the activity level is less than the activity level threshold, the candidate account is determined to be the target account; otherwise, that is, if the activity level is greater than or equal to the activity level threshold, or if the candidate account has not authorized the second application to retrieve its association relationship in the first application, it means that the candidate account is not the target account, and the process exits. Based on the above example scenario, in other words, for the target account, the message push conditions include: having a history of authorized login in the second application and not having revoked authorization; authorizing the second application to retrieve the target account's association relationship in the first application; and the target account's activity level in the second application being less than the activity level threshold.

[0123] Optionally, for any candidate account, if the candidate account meets the following conditions in the second application, the activity level of the candidate account in the second application is determined to be less than the activity threshold: Condition A) The candidate account has at least one object that has been joined but not activated in the second application; Condition B) All objects joined by the candidate account in the second application are activated, but the time difference between the last login time of all objects and the current time is greater than the target duration. The target duration is any value greater than 0, for example, a target duration of 30 days or 60 days, etc. This application embodiment does not specifically limit the target duration.

[0124] For office-related secondary applications, if the backup account has completed authorized login within the secondary application, the user will typically also add the backup account to the corresponding object of the organization entity. For example, this involves sending a join request to the object's management account. After the management account approves the join request, the target account successfully joins the object (i.e., an association is established between the target account and the object in the secondary application's relationship chain). However, further steps are required to activate the object. Typically, the activation process involves the platform re-verifying the target account after the management account approves the join request. Only after successful verification can activation be completed. After activation, the user can view their department, position and / or rank, and superiors / subordinates within the object. Therefore, if an account has at least one joined but not activated object in the secondary application—for example, joined to an enterprise object but not yet activated—it's likely that the user stopped using the secondary application after sending the join request. This indicates a low-activity user, meaning the backup account's activity level is below the activity threshold, and the backup account is then designated as the target account.

[0125] Optionally, if all objects added to the candidate account in the second application have been activated, it is still necessary to determine whether the time difference between the last login time of the candidate account in each added and activated object and the current time is greater than the target duration. If the time difference between the last login time of the candidate account in each object and the current time is greater than the target duration, it means that the user has not continued to use the second application for a long time after activating all objects, which means that the user is a low-activity user, that is, the activity level of the candidate account is less than the activity level threshold, and the candidate account is determined as the target account.

[0126] In the above process, by detecting both whether the user has fully authorized the application and whether the user is an inactive user, this message push condition can ensure that notification messages are only sent to inactive users who have fully authorized the application. For users who have not authorized the application or are inactive, there is no business need to drive traffic from the first application to the second application, which can avoid the loss of user experience for unauthorized users and active users.

[0127] Figure 4This is a schematic diagram illustrating the principle of filtering target accounts provided in this application embodiment. As shown in 400, when it is detected that a candidate account has previously authorized login in a second application, the second application assigns a unique identifier (GID) 401 to the candidate account and binds the candidate account's identifier in the first application with the GID 401 of the second application. For this candidate account, the server also maintains account metadata 402, storing the account metadata 402 in correspondence with the GID 401. Therefore, using the candidate account's identifier in the first application, the GID 401 of the candidate account's authorized login in the second application can be retrieved. Using the candidate account's GID 401 in the second application, the account metadata 402 of the candidate account can be retrieved. The account metadata 402 records whether the user has previously authorized login to the second application (since the user may cancel authorization after the first authorization and may re-authorize after cancellation, only the latest authorization status is recorded here), and whether the user agrees to retrieve the candidate account's association relationships (such as friend relationship chains) in the first application. Optionally, the account metadata 402 is also used to record the profile picture, account nickname, etc. of the alternative account in the second application. This application embodiment does not specifically limit this.

[0128] To illustrate, in account metadata 402, the server uses one binary data record to record the latest status of the user's authorized login to the second application, and another binary data record to record the latest status of the user's authorization to the second application to retrieve their association relationship in the first application. When both binary data are 1, it means that the user has authorized login to the second application and authorized access to the address book of the first application. Further analysis of the activity of the alternative account in the second application is needed to determine whether the alternative account is the target account. When either binary data is 0, it means that the user has canceled the authorization to log in to the second application, or the user does not agree to the second application retrieving their association relationship in the first application, or neither of these conditions is met. In this case, the message push conditions are not met, the alternative account is not the target account, and the process exits.

[0129] To illustrate, the server uses a binary data record in account metadata 402 to record the overall authorization status. When the binary data value is 1, it means that the user has authorized login to the second application and authorized access to the address book of the first application. Further analysis of the activity of the alternative account in the second application is needed to determine whether the alternative account is the target account. When the binary data value is 0, it means that the user has canceled the authorization to log in to the second application, or the user does not agree to the second application pulling its association relationship in the first application, or neither of the above conditions are met. In this case, the message push conditions are not met, the alternative account is not the target account, and the process ends.

[0130] Optionally, if it is determined based on account metadata 402 that the user has authorized login to the second application and authorized access to the address book of the first application, the object identifiers (VIDs) 403 of each object that the candidate account has joined in the second application are further obtained. For example, if all joined objects are enterprises, based on the candidate account's GID 401 in the second application, the VIDs of all enterprises that the candidate account has joined are retrieved from the relationship chain of the second application. 403. For each enterprise joined by the candidate account, obtain the interaction information 404 between the candidate account and the enterprise. This interaction information 404 includes, but is not limited to: the enterprise's VID information, whether the user has activated the enterprise, and the user's last login time in the enterprise. Furthermore, based on this interaction information 404, it can be determined whether the candidate account's activity level in the second application is less than an activity threshold. For example, when any interaction information 404 indicates that the user has not activated a joined enterprise, it is determined that the candidate account's activity level is less than the activity threshold. Or, when all interaction information 404 indicates that the time difference between the user's last login time and the current time is greater than the target duration (e.g., 30 days), it is determined that the candidate account's activity level is less than the activity threshold. If, based on the account metadata 402, it is determined that the user has authorized login to the second application for the candidate account and authorized access to the first application's address book, and based on the interaction information 404, it is determined that the candidate account's activity level is less than the activity threshold, it means that the message push conditions are met. The management account is determined as the target account, and the process proceeds to step 302.

[0131] 302. The server obtains multiple first accounts that are associated with the target account in the first application, and the target account has a history of authorized login to the second application associated with the first application.

[0132] Step 302 above is similar to step 201 in the above embodiment, and will not be described in detail here.

[0133] The following will combine Figure 5 This section provides a detailed explanation of how to retrieve these multiple primary accounts. Figure 5 This is a schematic diagram illustrating the principle of retrieving a first account, as provided in an embodiment of this application. Figure 5 As shown, the server maintains a friend relationship chain for the first application. For the target account 500 that meets the message push conditions, the server queries the friend relationship chain to find multiple first accounts 501 that are associated with the target account 500. These multiple first accounts 501 can be referred to as the friend list of the target account 500. Furthermore, for each first account 501 in the friend list, the server can also obtain the account identifier UnionID information, friend avatar, friend nickname, etc. of the first account 501.

[0134] 303. The server selects multiple second accounts from the multiple first accounts, and the second accounts meet the authentication conditions of the second application.

[0135] Step 303 above is similar to step 202 in the above embodiment, and will not be described in detail here.

[0136] In this embodiment of the application, in order to distinguish the account identifiers of different accounts and to distinguish the account identifiers of the same account in different applications, the account to be pushed notification messages in the first application is called the target account. The target account has an account identifier in the first application. The account identifier of the first account associated with the target account in the first application is denoted as UnionID. The target account has an identity identifier GID in the second application. The object identifier of the object that the target account has joined in the second application is denoted as VID.

[0137] The following will combine Figure 6 This section provides a detailed explanation of how to filter these multiple secondary accounts. Figure 6 This is a schematic diagram illustrating the principle of filtering a second account, as provided in an embodiment of this application. Figure 6 As shown, for any first account in the target account's friend list, obtain the account identifier UnionID 600 of that first account, and use UnionID 600 to query the authorization information of that first account. This authorization information is similar to that described above. Figure 4 The account metadata described herein indicates the latest authorization status of the first account for the second application and the permissions granted to the second application. This authorization information can be used to make the following judgments:

[0138] In step 601, it is determined whether the first account has ever authorized the second application to log in. If the first account has ever authorized the second application to log in, proceed to step 602. If the first account has not authorized the second application to log in, proceed to step 603.

[0139] In step 602, it is determined whether the first account has revoked authorization. If the first account has revoked authorization, it means that the first account does not meet the authentication conditions of the second application, the first account is not the second account, and cannot be included in the calculation of subsequent statistical information; if the first account has not revoked authorization, it means that the first account meets the authentication conditions of the second application, the first account is the second account, and needs to participate in the calculation of statistical information.

[0140] In step 603, it is determined whether the first account has established a relationship with the account of the second application in the first application (e.g., adding the account of the second application as a friend), or whether the first account is in an account group that includes the account of the second application (e.g., the account of the second application is in the same group chat). If either of these conditions is met or both are met, proceed to step 604; otherwise, if neither condition is met, proceed to step 605.

[0141] In step 604, it is determined whether the first account has revoked authorization. If the first account has revoked authorization, it means that the first account does not meet the authentication conditions of the second application, the first account is not the second account, and cannot be included in the calculation of subsequent statistical information; if the first account has not revoked authorization, it means that the first account meets the authentication conditions of the second application, the first account is the second account, and needs to participate in the calculation of statistical information.

[0142] In step 605, it is determined whether the first account has followed any object account of any object in the second application (e.g., followed an enterprise account). If the first account has followed any object account of any object in the second application, it means that the first account meets the authentication conditions of the second application, the first account is the second account, and needs to participate in the calculation of statistical information; if the first account has not followed any object account of any object in the second application, it means that the first account does not meet the authentication conditions of the second application, the first account is not the second account, and cannot be included in the subsequent calculation of statistical information.

[0143] In the above process, by filtering and screening the first account in the friend list, it can be ensured that the second account obtained after screening has been fully authorized by the friend user, thus avoiding infringement on the friend user's privacy rights.

[0144] 304. The server determines at least one target object from the second application, which is activated by at least one second account in the second application.

[0145] In some embodiments, after the server selects multiple second accounts from multiple first accounts, it uses the account identifier UnionID of each second account to query the objects that the second account has joined and activated in the relationship chain of the second application. After traversing all the second accounts, a set of objects can be obtained. By deduplicating all objects in the set, at least one target object can be obtained. It should be noted that if a second account has not used the second application, or has not joined and activated any objects in the second application, then this second account is skipped.

[0146] In other embodiments, the target object is added to the second application by at least one second account, but it is not limited to whether the second account that added the target object has been activated. In this case, the server uses its account identifier UnionID for each second account to query the objects added by the second account in the relationship chain of the second application in a similar manner, traverses all the second accounts, obtains a set of objects, and removes duplicates from all objects in the set to obtain the at least one target object.

[0147] It should be noted that the way the server queries the objects joined by the second account from the relationship chain of the second application in step 304, or queries the objects joined and activated by the second account, is similar to the way the server queries the first account from the relationship chain in step 201. For example, it queries from the topology graph or from the key-value pair structure, which will not be elaborated here.

[0148] Figure 7 This is a schematic diagram illustrating the principle of finding a target object according to an embodiment of this application, such as... Figure 7 As shown, for any target account 700, through the above steps 302-303, each first account in the friend list of the target account 700 is filtered to obtain a series of second accounts 701. For each second account 701, the object identifiers of each object that the second account has joined and the interaction information between the second account and each joined object are queried in the relationship chain of the second application. After summarizing all the objects that the second account has joined and activated, deduplication is performed to obtain at least one target object.

[0149] 305. For each target object, the server obtains statistical information on the number of second accounts that have been activated for that target object in the second application.

[0150] The statistical information is used to characterize the number of the second accounts associated with the target object in the second application.

[0151] In some embodiments, after counting which target objects each second account has activated, for each target object, the number of second accounts that have activated the target object in the second application is counted. This number can reflect how many (authorized) friend accounts of the target account have established an association with the target object in the second application. Taking all target objects as enterprises as an example, it represents how many friend accounts of the target account have currently joined and activated a certain enterprise in the second application.

[0152] 306. The server associates and stores the account identifier of the target account with the statistical information of each of the at least one target object.

[0153] In some embodiments, the server performs step 305 as described above for each target object, summarizing the statistical information of each of the at least one target object, and then storing the account identifier of the target account in association with the summarized statistical information. Optionally, the account identifier of the target account or the hash value of the account identifier of the target account can be used as the key name, and the summarized statistical information of each of the at least one target object can be used as the key value, thereby storing the data in association with the key-value pair. Alternatively, other structures such as hash tables, arrays, and sets can also be used for association storage. This application embodiment does not specifically limit the method of association storage.

[0154] 307. The server pushes a notification message to the target account in the first application. The notification message is used to notify the target account that multiple second accounts are using the second application. The notification message is also used to provide an entry point for viewing statistical information of at least one target object in the second application.

[0155] Step 307 above is similar to step 203 in the above embodiment, and will not be described in detail here.

[0156] Figure 8 This is a schematic flowchart of a principle for storing statistical information provided in an embodiment of this application. As shown in Figure 800, it illustrates the overall process of the server side acquiring and storing statistical information. First, it determines whether the current account meets the message push conditions. Then, if the message push conditions are met, it determines that the current account is the target account and retrieves the friend list of the target account, that is, obtains multiple first accounts that are associated with the target account. Next, it filters out the first accounts that do not meet the authentication conditions of the second application. In other words, it filters out each second account that meets the authentication conditions from the friend list. Next, it queries the enterprise identity of the friend, that is, it uses the account identifier of the friend's second account in the first application to query the identity identifier (UnionID) bound to the friend in the second application. Next, it uses the identity identifier of the friend in the second application to query the friend's enterprise information and summarizes the number of friends employed by each enterprise, that is, it obtains the statistical information of each target object. Finally, it stores the above-summarized statistical information and pushes a notification message to the target account.

[0157] 308. In response to receiving a notification message from the server, the terminal displays the notification message in the first application.

[0158] The target account is logged into the first application of the terminal. The target account has a history of authorized login to the second application associated with the first application. The second account meets the authentication conditions of the second application and is associated with the target account in the first application.

[0159] In some embodiments, after receiving a notification message from a server, the terminal displays the notification message in a first application. Optionally, the terminal displays a message list of the target account in the first application, and displays abbreviated information of the notification message in the message list. For example, the abbreviated information is displayed in the message list as an unread message, thereby prompting the user to read the notification message in a timely manner.

[0160] Optionally, unread messages may be displayed by showing a red dot in the upper left corner of the notification message's thumbnail information, or by displaying the title of the notification message's thumbnail information in bold, etc. This application embodiment does not specifically limit the display method of unread messages.

[0161] Furthermore, in response to the user's triggering action on the abbreviated information, the user is redirected from the message list to a details browsing interface, where the complete notification message is displayed. For example, the notification message contains the text "Inviting you to join the second application and collect the work business cards of 239 friends".

[0162] In some embodiments, the notification message displayed in the details browsing interface is itself an interactive viewing entry point; in other words, the notification message serves as a viewing entry point for statistical information of at least one target object stored in association with the target account. In response to a user's triggering action on the notification message, the process proceeds to step 309 below.

[0163] Figure 9 This is a schematic diagram of a details browsing interface provided in an embodiment of this application, such as... Figure 9 As shown, in the details browsing interface 900, a notification message 901 is displayed. This notification message 901 contains the text prompt "Inviting you to join the use of the second application and collect the work cards of 239 friends." The work card refers to an account card that can be directly shared from the second application to the first application; it is essentially a virtual card that allows users to quickly add accounts from the second application as friends within the first application. After the user triggers the operation on this notification message 901, they proceed to step 309 below.

[0164] Optionally, the triggering operation includes, but is not limited to: click operation, double click operation, long press operation, pressure operation, touch operation, voice command, gesture command, etc. This application embodiment does not specifically limit the operation method of the triggering operation. Taking a click operation as an example, after the terminal detects the pressure signal applied by the user to the terminal screen through the pressure sensor, it determines the screen coordinates of the touch point of the pressure signal. If the screen coordinates are located within the display area of ​​the notification message 901 on the terminal screen, it is determined that the user has performed a triggering operation on the notification message 901, and proceeds to step 309 below.

[0165] 309. In response to the triggering operation of the notification message, the terminal sends an information retrieval request carrying the account identifier of the target account to the server.

[0166] In some embodiments, after detecting a user's triggering action on a notification message displayed in the first application, the terminal sends an information retrieval request to the server. This information retrieval request requests statistical information of at least one target object stored in association with the target account from the server. Optionally, the information retrieval request includes at least the account identifier of the target account.

[0167] In some embodiments, the terminal encapsulates the request identifier of the information retrieval request in the header field of the message and the account identifier of the target account in the data field of the message. Then, it encapsulates the message using the Transmission Control Protocol, compresses the encapsulated message, encrypts the compressed message, and finally sends the encrypted message (i.e., the information retrieval request) to the server. This application does not specifically limit the compression algorithm used for compression or the encryption algorithm used for encryption.

[0168] Optionally, in order to simplify the message transmission process, the message may not be encrypted or compressed when sending the information retrieval request. This application embodiment does not specifically limit this.

[0169] 310. Upon receiving an information retrieval request triggered by the notification message, the server determines the account identifier of the target account carried in the information retrieval request.

[0170] In some embodiments, upon receiving any request, the server decrypts and decompresses the request to obtain an encapsulated message. The server then parses the encapsulated message, queries its header fields, and if the header field contains a request identifier for a data retrieval request, the request is determined to be a data retrieval request. Next, the server queries the data fields of the parsed message to obtain the target account's identifier. It should be noted that if the request received by the server is an unencrypted or uncompressed message, the above encryption or decompression steps are unnecessary.

[0171] 311. The server returns to the terminal the statistical information of at least one target object stored in association with the account identifier.

[0172] Since the server has already associated and stored the account identifier of each target account with the statistical information of the at least one target object in step 306 above, the statistical information of the at least one target object associated with the account identifier can be retrieved by using the account identifier carried in the request as an index. Furthermore, the server returns the statistical information of the at least one target object to the terminal.

[0173] 312. In response to receiving statistical information of at least one target object in the second application returned by the server based on the information retrieval request, the terminal displays the statistical information of the at least one target object in the first application.

[0174] The statistical information represents the number of the second accounts associated with the target object in the second application.

[0175] In some embodiments, after receiving statistical information of the at least one target object returned by the server, the terminal jumps from the details browsing interface to the interactive interface, which displays the statistical information of the at least one target object and a switching control. The switching control is used to switch from the first application to the second application. This allows users to easily switch to the second application at any time after browsing the statistical information and arousing their interest in using the second application, thereby facilitating user operation and improving human-computer interaction efficiency.

[0176] In some embodiments, when displaying statistical information of the at least one target object in the interactive interface, the information is displayed in descending order of the number of second accounts that have activated the target object. In other words, target objects with a larger number of second accounts are given priority in display. These target objects are usually highly compatible with the user and are more likely to increase the user's trust and interest.

[0177] In some embodiments, when displaying statistical information of the at least one target object in the interactive interface, the display area of ​​the statistical information for each target object displays the number of second accounts associated with the target object in the second application, as well as the profile pictures of some of the second accounts associated with the target object. Displaying profile pictures improves the efficiency of information acquisition for users, not only indicating to users how many associated second accounts each target object has, but also listing which second accounts are employed by the target object.

[0178] In some embodiments, the terminal responds to a user's triggering operation on the switching control by switching from the first application to the second application. For example, the terminal launches the second application from the first application, then switches the second application to the foreground and switches the first application to the background.

[0179] Figure 10 This is a schematic diagram of an interactive interface provided in an embodiment of this application, such as... Figure 10As shown, the interactive interface 1000 displays statistical information 1001-1003 for each of the three target objects. For example, statistical information 1001 indicates that there are currently 29 friends (i.e., the second account) working in company A, statistical information 1002 indicates that there are currently 17 friends working in company B, and statistical information 1003 indicates that there are currently 123 friends working in company C.

[0180] Furthermore, when displaying each statistical information, the profile pictures of some second accounts that have activated the target object corresponding to that statistical information are also displayed, which can achieve a better display effect. Optionally, when selecting the profile pictures to be displayed, the profile pictures of the second accounts that have the highest interaction frequency with the target account are given priority, or a preset number of profile pictures of second accounts are randomly selected for display, or the profile pictures of second accounts with high activity in the second application are given priority. This application embodiment does not specifically limit this.

[0181] In addition, a switching control 1004 is also displayed in the interactive interface 1000. The switching control 1004 displays the prompt text "Go to the second application and collect friends' work business cards". That is, by collecting friends' work business cards, users are encouraged to use the second application, which effectively drives users from the first application to the second application.

[0182] In some embodiments, after a user switches from the first application to the second application by switching controls, they can also choose to share their account card from the second application to the first application to invite more friends to use the second application together.

[0183] Optionally, in response to a business card sharing instruction triggered from the second application, the terminal displays a sharing interface. This sharing interface includes an account search bar, a selection control for at least one account, and a selection control for at least one account group. Users can directly trigger an operation on any account selection control within this sharing interface to configure the selected account as the account to be shared. Alternatively, users can directly trigger an operation on any account group selection control within this sharing interface to configure the selected account group as the account group to be shared. Furthermore, if a user finds that the accounts and account groups provided in the sharing interface do not meet their needs, they can use the account search bar to search for accounts and personalize the configuration of the account or account group to be shared.

[0184] After determining the account or group of accounts to be shared based on the sharing interface, the terminal sends a business card sharing request to the server. The business card sharing request carries the account identifier of the account to be shared or the group identifier of the group of accounts to be shared.

[0185] After receiving the business card sharing request, the server generates business card information for the target account in the second application. This business card information identifies the target account's account information in the second application, including but not limited to: account nickname, account avatar, selected activated entities to display in the business card (e.g., selected companies), and job title within those activated entities. Then, the server sends this business card information during the session between the target account and the account or group to be shared with. In other words, the server sends the target account's business card information in the second application to the account or group to be shared with.

[0186] After receiving the business card information in the session, the terminal displays the business card information in the session interface with the account or account group to be shared with. At the same time, the target terminal corresponding to the account or account group to be shared with will also display the business card information in the session interface with the account or account group to be shared with after receiving the business card information in the session.

[0187] Figure 11 This is a schematic diagram of the functional interface of a second application provided in an embodiment of this application, such as... Figure 11 As shown, the function interface 1100 of the second application displays two function tags: Add Customer 1101 and New Customer 1102. Currently, the Add Customer 1101 is selected. With Add Customer 1101 selected, the function interface 1100 provides the following options: Add option 1111 for adding friends face-to-face in the second application; Add option 1112 for adding friends in the second application by searching for phone numbers; Add option 1113 for adding friends from the friend relationship chain of the first application; Business card sharing option 1114 for sharing one's work business card to the first application (so that friends can actively add oneself); and Add option 1115 for adding other contacts as friends. Here, "other contacts" refers to contacts that do not fall under any of the above categories. For example, if a user authorizes access to the terminal's local address book to the second application, and a friend exists in the local address book but has not been added to the user's friend list in the first application, then that friend is considered an "other contact." The user triggers the business card sharing option 1114 by performing a trigger operation, which will then trigger the terminal to generate a business card sharing command.

[0188] Figure 12 This is a schematic diagram of a session interface provided in an embodiment of this application, such as... Figure 12As shown, after the user selects the account to be shared and clicks the send option, the user can choose to stay in the second application or switch to the first application. If the user chooses to switch to the first application, the first application will be automatically launched from the second application. If the first application is in the background, it will be directly woken up from the background and switched to the foreground display, and automatically jump to the conversation interface 1200 with the account to be shared. At the same time, the business card information 1201 of the target account in the second application is displayed in the conversation interface 1200. If the account to be shared views the business card information 1201, it can quickly add the account bound to the second application of the target account as a friend in the first application (i.e., establish a relationship) through the business card information 1201. At the same time, the user can also enter other messages in the conversation interface to facilitate communication with friends.

[0189] Figure 13 This is a schematic diagram of an account information interface provided in an embodiment of this application, such as... Figure 13 As shown, after the target account shares its business card information with other accounts, the other account can add the target account's linked account in the second application as a friend through this business card information in the first application. After adding the friend, the account will click on the business card information again and enter the target account's account information interface 1300 in the second application. The account information interface 1300 will display the target account's profile picture 1301, account nickname 1302, affiliated object 1303, real name information 1304, job title 1305, work email 1306, etc. in the second application, which can more comprehensively display some of the target account's work business card information in the second application.

[0190] All of the above-mentioned optional technical solutions can be combined in any way to form optional embodiments of this disclosure, and will not be described in detail here.

[0191] The method provided in this application pushes notification messages to target accounts that have a history of authorized login to the second application in the first application, so as to notify how many friends who meet the authentication conditions are currently using the second application. This can incentivize target accounts to spontaneously join and use the second application under the relationship chain, thereby realizing the account traffic from the first application to the second application. This also eliminates the need for the administrator to manually invite target accounts in the second application, which can improve the efficiency of users obtaining information from invitation-type notification messages of the second application and the efficiency of human-computer interaction.

[0192] Figure 14 This is a schematic diagram of the structure of a message transmission device provided in an embodiment of this application. Please refer to it. Figure 14 The device includes:

[0193] The first acquisition module 1401 is used to acquire multiple first accounts that are associated with the target account in the first application, and the target account has a history of authorized login to the second application associated with the first application;

[0194] The filtering module 1402 is used to filter out multiple second accounts from the multiple first accounts, and the second accounts meet the authentication conditions of the second application.

[0195] The push module 1403 is used to push a notification message to the target account in the first application. The notification message is used to notify the target account that the multiple second accounts are using the second application.

[0196] The device provided in this application pushes notification messages to target accounts that have a history of authorized login to the second application in the first application, so as to notify how many friends who meet the authentication conditions are currently using the second application. This can incentivize target accounts to spontaneously join and use the second application under the relationship chain, thereby realizing the account traffic from the first application to the second application. This also eliminates the need for the administrator to manually invite target accounts in the second application, which can improve the efficiency of users obtaining information from invitation-type notification messages of the second application and the efficiency of human-computer interaction.

[0197] In one possible implementation, the notification message is also used to provide an entry point for viewing statistical information of at least one target object in the second application, the statistical information being used to characterize the number of the second accounts associated with the target object in the second application;

[0198] based on Figure 14 The device comprises:

[0199] A first determining module is configured to determine the at least one target object from the second application, the target object being activated by at least one second account in the second application;

[0200] The second acquisition module is used to acquire statistical information on the number of second accounts that have been activated for each target object in the second application.

[0201] The storage module is used to associate and store the account identifier of the target account with the statistical information of each of the at least one target object.

[0202] In one possible implementation, based on Figure 14 The device comprises:

[0203] The second determining module is used to determine the account identifier of the target account carried in the information retrieval request in response to receiving an information retrieval request triggered by the notification message.

[0204] The return module is used to return statistical information of the at least one target object stored in association with the account identifier.

[0205] In one possible implementation, the second account includes at least one of the following:

[0206] Has a history of authorized logins in this second application, and has not yet revoked authorization; or,

[0207] The account in the first application has been linked to the account in the second application, and authorization has not yet been revoked; or,

[0208] The account is in an account group that includes the account of the second application, and authorization has not yet been revoked; or,

[0209] The first application followed the object account of any object in the second application.

[0210] In one possible implementation, based on Figure 14 The device comprises:

[0211] The third determining module is used to determine the target account in the first application that meets the message push conditions.

[0212] In one possible implementation, the message push conditions include:

[0213] The target account has a history of authorized login in the second application and has not yet revoked the authorization; and the target account is authorized to retrieve the association relationship of the target account in the first application; and the activity level of the target account in the second application is less than the activity level threshold.

[0214] All of the above-mentioned optional technical solutions can be combined in any way to form optional embodiments of this disclosure, and will not be described in detail here.

[0215] It should be noted that the message transmission device provided in the above embodiments is only illustrated by the division of the above functional modules when pushing notification messages. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the electronic device can be divided into different functional modules to complete all or part of the functions described above. In addition, the message transmission device and message transmission method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the message transmission method embodiments, which will not be repeated here.

[0216] Figure 15 This is a schematic diagram of the structure of a message display device provided in an embodiment of this application. Please refer to it. Figure 15 The device includes a target account logged into a first application, which has a history of authorized logins to a second application associated with the first application.

[0217] The receiving module 1501 is used to receive a notification message from the server. The notification message is used to notify the target account that multiple second accounts are using the second application. The second accounts meet the authentication conditions of the second application and are associated with the target account in the first application.

[0218] Display module 1502 is used to display the notification message in the first application.

[0219] The apparatus provided in this application embodiment, if the target account logged in on the first application has a history of authorized login to the second application, displays a notification message pushed by the server in the first application to notify how many friends who meet the authentication conditions are currently using the second application. This can incentivize the target account to spontaneously join and use the second application under the relationship chain, thereby realizing account referral from the first application to the second application. This also eliminates the need for the administrator to manually invite the target account in the second application, improving the efficiency of users obtaining information from invitation notification messages of the second application and the efficiency of human-computer interaction.

[0220] In one possible implementation, based on Figure 15 The device comprises:

[0221] The sending module is used to send a request to the server to retrieve information carrying the account identifier of the target account in response to the triggering operation of the notification message.

[0222] The receiving module 1501 is further configured to receive statistical information of at least one target object in the second application returned by the server based on the information retrieval request, the statistical information representing the number of second accounts associated with the target object in the second application;

[0223] The display module 1502 is also used in the first application to display statistical information of the at least one target object.

[0224] In one possible implementation, the display module 1502 is further configured to:

[0225] In the statistics display area for each target object, the number of the second accounts associated with the target object in the second application and the profile pictures of some of the second accounts associated with the target object are displayed.

[0226] In one possible implementation, when displaying the statistical information, the display module 1502 also displays a switching control for switching from the first application to the second application;

[0227] based on Figure 15 The device comprises:

[0228] A jump module is used to jump from the first application to the second application in response to a trigger operation on the switching control.

[0229] In one possible implementation, based on Figure 15 The device comprises:

[0230] The determination module is used to determine the account or group of accounts to be shared in response to a business card sharing instruction triggered from the second application.

[0231] The sending module is used to send the business card information of the target account in the second application to the account or account group to be shared via the server;

[0232] The display module 1502 is also used to display the business card information in a conversation interface with the account or group of accounts to be shared.

[0233] All of the above-mentioned optional technical solutions can be combined in any way to form optional embodiments of this disclosure, and will not be described in detail here.

[0234] It should be noted that the message display device provided in the above embodiments is only illustrated by the division of the above functional modules when displaying notification messages. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the electronic device can be divided into different functional modules to complete all or part of the functions described above. In addition, the message display device provided in the above embodiments and the interaction embodiment of the message transmission method belong to the same concept, and the specific implementation process can be found in the interaction embodiment of the message transmission method, which will not be repeated here.

[0235] Figure 16 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application, such as... Figure 16 As shown, this terminal is an exemplary illustration of an electronic device. Optionally, the device type of this terminal 1600 includes: a smartphone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III), an MP4 player (Moving Picture Experts Group Audio Layer IV), a laptop computer, or a desktop computer. Terminal 1600 may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, etc.

[0236] Typically, terminal 1600 includes a processor 1601 and a memory 1602.

[0237] Optionally, the processor 1601 includes one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Optionally, the processor 1601 is implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). In some embodiments, the processor 1601 includes a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, the processor 1601 integrates a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, the processor 1601 also includes an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0238] In some embodiments, memory 1602 includes one or more computer-readable storage media, optionally non-transitory. Optionally, memory 1602 also includes high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in memory 1602 is used to store at least one program code, which is executed by processor 1601 to implement the message display methods provided in the various embodiments of this application.

[0239] In some embodiments, the terminal 1600 may also optionally include a peripheral device interface 1603 and at least one peripheral device. The processor 1601, memory 1602, and peripheral device interface 1603 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 1603 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of the following: a radio frequency circuit 1604, a display screen 1605, a camera assembly 1606, an audio circuit 1607, and a power supply 1608.

[0240] Peripheral device interface 1603 can be used to connect at least one I / O (Input / Output) related peripheral device to processor 1601 and memory 1602. In some embodiments, processor 1601, memory 1602 and peripheral device interface 1603 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 1601, memory 1602 and peripheral device interface 1603 are implemented on separate chips or circuit boards, which is not limited in this embodiment.

[0241] The radio frequency (RF) circuit 1604 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 1604 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 1604 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 1604 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. Optionally, the RF circuit 1604 communicates with other terminals via at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: metropolitan area networks (MANs), various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks (WLANs), and / or WiFi (Wireless Fidelity) networks. In some embodiments, the RF circuit 1604 also includes circuitry related to NFC (Near Field Communication), which is not limited in this application.

[0242] Display screen 1605 is used to display a UI (User Interface). Optionally, the UI includes graphics, text, icons, videos, and any combination thereof. When display screen 1605 is a touch display screen, display screen 1605 also has the ability to collect touch signals on or above the surface of display screen 1605. The touch signals can be input to processor 1601 for processing as control signals. Optionally, display screen 1605 is also used to provide virtual buttons and / or virtual keyboards, also known as soft buttons and / or soft keyboards. In some embodiments, there is one display screen 1605, which is set on the front panel of terminal 1600; in other embodiments, there are at least two display screens 1605, which are respectively set on different surfaces of terminal 1600 or are folded; in still other embodiments, display screen 1605 is a flexible display screen, which is set on the curved surface or folded surface of terminal 1600. Furthermore, optionally, display screen 1605 is set as a non-rectangular irregular shape, that is, an irregularly shaped screen. Optionally, the display screen 1605 is made of materials such as LCD (Liquid Crystal Display) or OLED (Organic Light-Emitting Diode).

[0243] The camera assembly 1606 is used to acquire images or videos. Optionally, the camera assembly 1606 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the terminal, and the rear-facing camera is located on the back of the terminal. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, VR (Virtual Reality) shooting, or other fusion shooting functions. In some embodiments, the camera assembly 1606 also includes a flash. Optionally, the flash is a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm-light flash and a cool-light flash, used for light compensation at different color temperatures.

[0244] In some embodiments, the audio circuit 1607 includes a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, and convert the sound waves into electrical signals that are input to the processor 1601 for processing, or input to the radio frequency circuit 1604 to realize voice communication. For stereo acquisition or noise reduction purposes, multiple microphones are used, each located at a different part of the terminal 1600. Optionally, the microphone is an array microphone or an omnidirectional acquisition microphone. The speaker is used to convert the electrical signals from the processor 1601 or the radio frequency circuit 1604 into sound waves. Optionally, the speaker is a conventional film speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into sound waves that humans can hear, but also into sound waves that humans cannot hear for purposes such as distance measurement. In some embodiments, the audio circuit 1607 also includes a headphone jack.

[0245] Power supply 1608 is used to power the various components in terminal 1600. Optionally, power supply 1608 is AC power, DC power, a disposable battery, or a rechargeable battery. When power supply 1608 includes a rechargeable battery, the rechargeable battery supports wired or wireless charging. The rechargeable battery also supports fast charging technology.

[0246] In some embodiments, the terminal 1600 further includes one or more sensors 1610. The one or more sensors 1610 include, but are not limited to: an accelerometer 1611, a gyroscope 1612, a pressure sensor 1613, an optical sensor 1614, and a proximity sensor 1615.

[0247] In some embodiments, the accelerometer 1611 detects the magnitude of acceleration along the three coordinate axes of a coordinate system established with the terminal 1600. For example, the accelerometer 1611 is used to detect the components of gravitational acceleration along the three coordinate axes. Optionally, the processor 1601 controls the display screen 1605 to display the user interface in either a landscape or portrait view based on the gravitational acceleration signal acquired by the accelerometer 1611. The accelerometer 1611 is also used for collecting motion data from games or users.

[0248] In some embodiments, the gyroscope sensor 1612 detects the orientation and rotation angle of the terminal 1600. The gyroscope sensor 1612 and the accelerometer sensor 1611 work together to acquire the user's 3D movements on the terminal 1600. Based on the data acquired by the gyroscope sensor 1612, the processor 1601 implements the following functions: motion sensing (e.g., changing the UI based on the user's tilt operation), image stabilization during shooting, game control, and inertial navigation.

[0249] Optionally, the pressure sensor 1613 is disposed on the side bezel of the terminal 1600 and / or on the lower layer of the display screen 1605. When the pressure sensor 1613 is disposed on the side bezel of the terminal 1600, it can detect the user's grip signal on the terminal 1600, and the processor 1601 performs left / right hand recognition or quick operation based on the grip signal collected by the pressure sensor 1613. When the pressure sensor 1613 is disposed on the lower layer of the display screen 1605, the processor 1601 controls the operable controls on the UI interface based on the user's pressure operation on the display screen 1605. The operable controls include at least one of button controls, scroll bar controls, icon controls, and menu controls.

[0250] Optical sensor 1614 is used to collect ambient light intensity. In one embodiment, processor 1601 controls the display brightness of display screen 1605 based on the ambient light intensity collected by optical sensor 1614. Specifically, when the ambient light intensity is high, the display brightness of display screen 1605 is increased; when the ambient light intensity is low, the display brightness of display screen 1605 is decreased. In another embodiment, processor 1601 also dynamically adjusts the shooting parameters of camera assembly 1606 based on the ambient light intensity collected by optical sensor 1614.

[0251] The proximity sensor 1615, also known as a distance sensor, is typically located on the front panel of the terminal 1600. The proximity sensor 1615 is used to detect the distance between the user and the front of the terminal 1600. In one embodiment, when the proximity sensor 1615 detects that the distance between the user and the front of the terminal 1600 is gradually decreasing, the processor 1601 controls the display screen 1605 to switch from a screen-on state to a screen-off state; when the proximity sensor 1615 detects that the distance between the user and the front of the terminal 1600 is gradually increasing, the processor 1601 controls the display screen 1605 to switch from a screen-off state to a screen-on state.

[0252] Those skilled in the art will understand that Figure 16 The structure shown does not constitute a limitation on terminal 1600, which may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0253] Figure 17 This is a schematic diagram of the structure of a server provided in an embodiment of this application, such as... Figure 17As shown, the server 1700 is an exemplary illustration of an electronic device. The server 1000 can vary considerably due to differences in configuration or performance. The server 1000 includes one or more Central Processing Units (CPUs) 1001 and one or more memories 1002, wherein the memory 1002 stores at least one computer program, which is loaded and executed by the one or more processors 1001 to implement the message transmission methods provided in the various embodiments described above. Optionally, the server 1000 also has wired or wireless network interfaces, a keyboard, and input / output interfaces for input / output. The server 1000 also includes other components for implementing device functions, which will not be elaborated here.

[0254] In an exemplary embodiment, a computer-readable storage medium is also provided, such as a memory including at least one computer program, which can be executed by a processor in a terminal to perform the message transmission method or message display method in the various embodiments described above. For example, the computer-readable storage medium includes ROM (Read-Only Memory), RAM (Random-Access Memory), CD-ROM (CompactDisc Read-Only Memory), magnetic tape, floppy disk, and optical data storage devices, etc.

[0255] In an exemplary embodiment, a computer program product or computer program is also provided, including one or more lines of program code stored in a computer-readable storage medium. One or more processors of an electronic device are capable of reading the one or more lines of program code from the computer-readable storage medium, and the one or more processors execute the one or more lines of program code, enabling the electronic device to perform the message transmission method or message display method described in the above embodiments.

[0256] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. Optionally, the program is stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0257] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A message transmission method, characterized in that, The method, executed by the server, includes: Obtain multiple first accounts that are associated with the target account in the first application, wherein the target account has a history of authorizing login to a second application associated with the first application and has not yet revoked the authorization, and the target account includes accounts with low activity in the second application; From the plurality of first accounts, a plurality of second accounts are obtained, wherein the second accounts meet the authentication conditions of the second application, and the authentication conditions include at least one of the following: the first account has a history of authorizing login to the second application and has not yet revoked the authorization; the first account has not authorized login to the second application and the first account has followed any object account of any object in the second application in the first application; In the first application, a notification message is pushed to the target account. The notification message is used to notify the target account that the multiple second accounts are using the second application, and to provide an entry point for viewing statistical information of at least one target object in the second application. The statistical information is used to characterize the number of second accounts associated with the corresponding target object in the second application.

2. The method according to claim 1, characterized in that, After selecting multiple second accounts from the multiple first accounts, the method further includes: The at least one target object is determined from the second application, the target object being activated by at least one second account in the second application; For each target object, obtain statistical information on the number of second accounts that have been activated for the target object in the second application; The account identifier of the target account and the statistical information of each of the at least one target object are associated and stored.

3. The method according to claim 2, characterized in that, The method further includes: In response to receiving an information retrieval request triggered by the notification message, the account identifier of the target account carried in the information retrieval request is determined; Return statistical information of the at least one target object stored in association with the account identifier.

4. The method according to claim 1, characterized in that, The second account also includes at least one of the following: An account in the first application has been associated with an account in the second application, and authorization has not yet been revoked; or, The account is in an account group that includes the second application, and authorization has not yet been revoked.

5. The method according to claim 1, characterized in that, The method further includes: Identify the target account in the first application that meets the message push conditions.

6. The method according to claim 5, characterized in that, The message push conditions include: The target account has a history of authorized login in the second application and has not yet revoked the authorization; and the target account is authorized to retrieve the association relationship of the target account in the first application; and the activity level of the target account in the second application is less than the activity level threshold.

7. A message display method, characterized in that, The method is executed by a terminal, wherein a target account is logged into a first application on the terminal, the target account has a history of authorized logins to a second application associated with the first application and has not yet revoked the authorization, and the target account includes accounts with low activity in the second application. The system receives a notification message from the server. This message notifies the target account that multiple second accounts are using the second application, and provides an entry point for viewing statistical information of at least one target object within the second application. The statistical information represents the number of second accounts associated with the corresponding target object in the second application. The second accounts meet the authentication criteria of the second application and are selected from first accounts that are associated with the target account in the first application. The authentication criteria include at least one of the following: the first account has a history of authorized login to the second application and has not yet revoked authorization; the first account has not authorized login to the second application and the first account has followed the object account of any object in the second application within the first application. In the first application, the notification message is displayed.

8. The method according to claim 7, characterized in that, The method further includes: In response to the triggering operation of the notification message, a request to retrieve information carrying the account identifier of the target account is sent to the server; Receive statistical information of at least one target object in the second application returned by the server based on the information retrieval request, wherein the statistical information represents the number of second accounts associated with the target object in the second application; In the first application, statistical information of the at least one target object is displayed.

9. The method according to claim 8, characterized in that, The statistical information displayed for the at least one target object includes: In the display area of ​​the statistics information for each target object, the number of second accounts associated with the target object in the second application is displayed, as well as the profile picture of some of the second accounts associated with the target object.

10. The method according to claim 8, characterized in that, When displaying the statistical information, a switching control is also displayed, which is used to switch from the first application to the second application; The method further includes: In response to a trigger operation on the switching control, the user jumps from the first application to the second application.

11. The method according to claim 7, characterized in that, The method further includes: In response to a business card sharing instruction triggered from the second application, determine the account or group of accounts to be shared; The server sends the business card information of the target account in the second application to the account or account group to be shared. The business card information is displayed in the conversation interface with the account or group of accounts to be shared.

12. A message transmission device, characterized in that, The device includes: The first acquisition module is used to acquire multiple first accounts that are associated with the target account in the first application. The target account has a history of authorizing login to the second application associated with the first application and has not yet revoked the authorization. The target account includes accounts with low activity in the second application. The filtering module is used to filter out multiple second accounts from the multiple first accounts, wherein the second accounts meet the authentication conditions of the second application, and the authentication conditions include at least one of the following: the first account has a history of authorizing login to the second application and has not yet revoked the authorization; the first account has not authorized login to the second application and the first account has followed any object account of any object in the second application in the first application; The push module is used to push notification messages to the target account in the first application. The notification messages are used to notify the target account that the multiple second accounts are using the second application, and to provide an entry point for viewing statistical information of at least one target object in the second application. The statistical information is used to represent the number of second accounts associated with the corresponding target object in the second application.

13. The apparatus according to claim 12, characterized in that, The device further includes: A first determining module is configured to determine the at least one target object from the second application, wherein the target object is activated by at least one second account in the second application; The second acquisition module is used to acquire statistical information on the number of second accounts that have been activated for each target object in the second application; The storage module is used to associate and store the account identifier of the target account with the statistical information of each of the at least one target object.

14. The apparatus according to claim 13, characterized in that, The device further includes: The second determining module is used to determine the account identifier of the target account carried in the information retrieval request in response to receiving an information retrieval request triggered based on the notification message; The return module is used to return statistical information of the at least one target object that is associated with the account identifier.

15. The apparatus according to claim 12, characterized in that, The second account also includes at least one of the following: An account in the first application has been associated with an account in the second application, and authorization has not yet been revoked; or, The account is in an account group that includes the second application, and authorization has not yet been revoked.

16. The apparatus according to claim 12, characterized in that, The device further includes: The third determining module is used to determine the target account in the first application that meets the message push conditions.

17. The apparatus according to claim 16, characterized in that, The message push conditions include: The target account has a history of authorized login in the second application and has not yet revoked the authorization; and the target account is authorized to retrieve the association relationship of the target account in the first application; and the activity level of the target account in the second application is less than the activity level threshold.

18. A message display device, characterized in that, The device has a target account logged into a first application. The target account has a history of authorizing logins to a second application associated with the first application and has not yet revoked the authorization. The target account includes accounts with low activity in the second application. The device includes: A receiving module is used to receive notification messages from the server. These notification messages are used to notify the target account that multiple second accounts are using the second application, and to provide an entry point for viewing statistical information of at least one target object in the second application. The statistical information represents the number of second accounts associated with the corresponding target object in the second application. The second accounts meet the authentication conditions of the second application and are selected from first accounts that are associated with the target account in the first application. The authentication conditions include at least one of the following: the first account has a history of authorized login to the second application and has not yet revoked authorization; the first account has not authorized login to the second application and the first account has followed any object account in the second application within the first application. The display module is used to display the notification message in the first application.

19. The apparatus according to claim 18, characterized in that, The device further includes: The sending module is used to send an information retrieval request carrying the account identifier of the target account to the server in response to the triggering operation of the notification message. The receiving module is further configured to receive statistical information of at least one target object in the second application returned by the server based on the information retrieval request, wherein the statistical information represents the number of second accounts associated with the target object in the second application; The display module is also used to display statistical information of the at least one target object in the first application.

20. The apparatus according to claim 19, characterized in that, The display module is also used for: In the display area of ​​the statistics information for each target object, the number of second accounts associated with the target object in the second application is displayed, as well as the profile picture of some of the second accounts associated with the target object.

21. The apparatus according to claim 19, characterized in that, When displaying the statistical information, the display module also displays a switching control, which is used to switch from the first application to the second application; The device further includes: A jump module is used to jump from the first application to the second application in response to a trigger operation of the switching control.

22. The apparatus according to claim 18, characterized in that, The device further includes: The determination module is used to determine the account or account group to be shared in response to a business card sharing instruction triggered from the second application; The sending module is used to send the business card information of the target account in the second application to the account or account group to be shared via the server; The display module is also used to display the business card information in a conversation interface with the account or account group to be shared.

23. An electronic device, characterized in that, The electronic device includes one or more processors and one or more memories, wherein the one or more memories store at least one computer program, which is loaded and executed by the one or more processors to implement the message transmission method as described in any one of claims 1 to 6; or, the message display method as described in any one of claims 7 to 11.

24. A computer-readable storage medium, characterized in that, The storage medium stores at least one computer program, which is loaded and executed by a processor to implement the message transmission method as described in any one of claims 1 to 6; or the message display method as described in any one of claims 7 to 11.

25. A computer program product, characterized in that, The computer program product includes at least one computer program, which is loaded and executed by a processor to implement the message transmission method as described in any one of claims 1 to 6; or the message display method as described in any one of claims 7 to 11.

Images