Application message display method and device, computer product and related equipment

Abstract

This disclosure provides an application message display method, application message forwarding method, apparatus, electronic device, computer-readable storage medium, and computer product, relating to the field of computer and internet technology. The application message display method includes: displaying an emergency offline reminder message of a second application in a first application logged in by a first user; the emergency offline reminder message reminds the first user of the existence of offline messages of a target application in the second application, the offline messages of the target application being generated based on target application messages sent from the target application in the second application to the first user; and, in response to a trigger signal for the emergency offline reminder message, jumping from the first application to the second application to view the target application messages. Embodiments of this disclosure can prominently and effectively remind the first user of the existence of offline messages of a target application in the second application through an emergency offline reminder message in the first application.

Description

Technical Field

[0001] This disclosure relates to the field of computer and Internet technology, and in particular to an application message display method, apparatus, electronic device, computer-readable storage medium, and computer product. Background Technology

[0002] With the rapid development of internet technology, various applications have emerged on the internet, such as chat applications, shopping applications, and news applications. People can use these applications to access a variety of services. For example, people can use chat applications to exchange information, use shopping applications to shop, and use news applications to read news.

[0003] However, in practice, users can only access messages within the application after activating and logging in. If a user hasn't activated their account, hasn't logged in after activation, or hasn't logged in for an extended period, they will not receive any information from the application. Offline messages will only be available upon the next login.

[0004] In some cases, application messages in certain applications are highly urgent and need to be processed by the user promptly.

[0005] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure. Summary of the Invention

[0006] The purpose of this disclosure is to provide an application message display method, application message forwarding method, device, electronic device, computer-readable storage medium, and computer product that can display offline messages of a target application in a second application within a first application, enabling a first object to promptly obtain offline messages of the target application in the second application and providing timely push notifications of the target application messages in the second application.

[0007] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.

[0008] This disclosure provides an application message display method applied to a first device, comprising: displaying an emergency offline reminder message of a second application in a first application logged in by a first object, the emergency offline reminder message being used to remind the first object that there are offline messages of a target application in the second application, the offline messages of the target application being generated based on target application messages sent to the first object by the target application in the second application; and, in response to a trigger signal for the emergency offline reminder message, jumping from the first application to the second application to view the target application messages.

[0009] This disclosure provides an application message forwarding method applied to a second device, comprising: receiving a target application message sent by a target application to a first object in a second application; determining that the target application message cannot reach the first object in the second application; generating an emergency offline reminder message based on the target application message; and sending the emergency offline reminder message to the first object through the first application, so that the first object can access the target application in the second application based on the emergency offline reminder message.

[0010] This disclosure provides an application message display device for a first device, comprising: an emergency offline reminder message display module and a triggering module.

[0011] The offline reminder message display module is used to display an emergency offline reminder message of the second application in the first application logged in by the first object. The emergency offline reminder message includes a prominent reminder icon and is used to remind the first object that there are offline messages of the target application in the second application. The application name of the target application contains the keyword "emergency". The triggering module is used to jump from the first application to the second application in response to the trigger signal of the emergency offline reminder message in order to view the offline messages of the target application.

[0012] In some embodiments, the offline notification message display module includes a service notification account display submodule.

[0013] The service notification account display submodule can be used to display the emergency offline reminder message through the service notification account when the number of times the first application receives information from the second application is less than a threshold. The service notification account is the system message account of the first application.

[0014] In some embodiments, the first application has been authorized to receive information from the second application; wherein, the offline reminder message display module further includes: a second application account display submodule.

[0015] The second application account submodule is used to display the emergency offline reminder message through the second application account when the frequency at which the first application receives information from the second application is greater than or equal to the number of times threshold. The second application account is the session account of the second application in the first application.

[0016] In some embodiments, the second application includes at least one candidate team, the member address book of the at least one candidate team includes the first object, the at least one candidate team includes a target team, the target application message is sent by the target application to the first object through the target team; the first application has been authorized to confirm receiving information from the target team; wherein, the offline reminder message display module further includes: a target team account display submodule.

[0017] The target team account display submodule is used to display the emergency offline reminder message through the target team account when the frequency of the first application receiving information from the second application is greater than or equal to a threshold number. The target team account is the session account of the target team in the first application.

[0018] In some embodiments, if the first object does not have an activated account in the second application or the first object's activated account in the second application has expired and has not logged in, the first object logs into the first application using the first account; wherein the triggering module includes: a jump page display submodule, an authorization login page display submodule, and a jump rotor module.

[0019] The jump page display submodule is used to display the jump page of the second application in response to the trigger signal of the emergency offline reminder message. The jump page includes a pull-up control of the second application. The authorized login page display submodule is used to display the authorized login page in response to the trigger signal of the pull-up control, so that the first object can authorize login to the second application through the account information of the first account. The jump module is used to jump from the first application to the second application after authorized login to view the target application message.

[0020] In some embodiments, the second application includes at least one candidate team, the member address book of at least one candidate team includes a first object, and the candidate team includes a target team that sends a target application message to the first object; wherein, the jumper module includes: a second application login unit, a candidate team display unit, and a target team selection unit.

[0021] The second application login unit is used to log in to the second application using the account information of the first account; the candidate team display unit is used to display the at least one candidate team for the first object to select and join; the target team selection unit is used to enter the target team in the second application in response to a trigger signal for the target team, so as to view the target application messages in the target team.

[0022] In some embodiments, the second application includes at least one candidate team, the member address book of at least one candidate team includes a first object, the candidate team includes a target team, and the target application message is sent by the target application to the first object through the target team; the first object has an activated account in the second application and the activated account login has not timed out, and the first object has not joined the target team; wherein, the triggering module includes: a second application jump page display submodule, a candidate team display submodule, and a target team entry submodule.

[0023] The second application redirect page display submodule is used to display the redirect page of the second application in response to the trigger signal of the emergency offline reminder message. The redirect page includes a pull-up control for the second application. The selectable team display submodule is used to display at least one candidate team for the first object to choose to join in response to the trigger signal of the pull-up control. The target team entry submodule is used to enter the target team in the second application in response to the trigger signal of the target team to view the target application messages in the target team.

[0024] In some embodiments, the first object logs into the first application through a first device, and the first device does not have a second application; the application message display device includes: a download page display module and a download and installation module.

[0025] The download page display module is used to display the download page of the second application, which includes a download control, after responding to a trigger signal for an emergency offline reminder message and before displaying the redirect page for the second application; the download and installation module is used to download and install the second application in response to a trigger signal for the download control.

[0026] This disclosure provides an application message display device for a second device, comprising: an application message receiving module, a reach determination module, an emergency keyword filtering module, an offline reminder message generation module, and an offline reminder message sending module.

[0027] The application message receiving module is used to receive target application messages sent by the target application to the first object in the second application; the reach determination module is used to determine that the target application message cannot reach the first object in the second application; the emergency keyword filtering module is used to determine that the application name of the target application includes emergency keywords; the offline reminder message generation module is used to generate an emergency offline reminder message based on the target application message, the emergency offline reminder message including a prominent reminder identifier; and the offline reminder message sending module is used to send the emergency offline reminder message to the first object through the first application to remind the first object that there are offline messages of the target application in the second application.

[0028] In some embodiments, the second application includes at least one candidate team, the member address book of at least one candidate team includes a first object, the candidate team includes a target team, and the target application message is sent by the target application to the first object through the target team; wherein, the reach determination module includes: a trigger determination submodule.

[0029] The reach determination submodule is used to determine whether the first object has no activated account in the second application; or, whether the first object's activated account in the second application has timed out and has not logged in; or, whether the first object has an activated account in the second application and the activated account login has not timed out and the first object has not joined the target team; and whether the target application message can not be reached to the first object in the second application.

[0030] In some embodiments, the application information forwarding device further includes: a member acquisition request receiving module, an associated object return module, a member addition request acquisition module, and an address book addition module.

[0031] The module includes a member acquisition request receiving module for receiving a member acquisition request sent by a second object in the target team. The member acquisition request is used to obtain the associated object of the second object in the first application, and the associated object includes the first object. The associated object return module is used to return the associated object to the second object. The member addition request acquisition module is used to receive a member addition request sent by the second object for the first object. The address book addition module is used to add the first object to the member address book of the target team according to the member addition request, and to determine that the first object has not joined the target team.

[0032] In some embodiments, the application message forwarding device further includes: an invitation request receiving module, an invitation request sending module, and a join request receiving module.

[0033] The invitation request receiving module is used to receive an invitation request sent by the target administrator in the target team to the first object; the invitation request sending module is used to send an invitation request to the first object through the first application to invite the first object to join the target team; and the join request receiving module is used to receive the join request sent by the first object in response to the invitation request and add the first object to the target team.

[0034] In some embodiments, the offline reminder message sending module includes: a first judgment submodule.

[0035] The first determination submodule is used to determine that if the frequency at which the first application receives information from the second application is less than a threshold, the emergency offline reminder message is sent to the first application so that the first application can display the emergency offline reminder message through a service notification account, where the service notification account is the system message account of the first application.

[0036] In some embodiments, the offline reminder message sending module includes a second judgment submodule.

[0037] The second determination submodule is used to determine that the frequency at which the first application receives information from the second application is greater than or equal to the number threshold and the first application has authorized and confirmed receiving information from the second application. If so, the emergency offline reminder message is sent to the second application account in the first application so that the emergency offline reminder message can be displayed through the second application account. The second application account is the session account of the second application in the first application.

[0038] In some embodiments, the second application includes at least one candidate team, the member address book of the at least one candidate team includes the first object, the at least one candidate team includes a target team, and the target application message is sent by the target application to the first object through the target team; wherein, the offline reminder message sending module further includes: a third judgment submodule.

[0039] The third judgment submodule is used to determine that if the frequency at which the first application receives information from the second application is greater than or equal to the number threshold and the first application has been authorized to receive information from the target team, then the emergency offline reminder message is sent to the target team account in the first application so that the emergency offline reminder message can be displayed through the target team account, where the target team account is the session account of the target team in the first application.

[0040] This disclosure provides an electronic device comprising: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the application message display method described above.

[0041] This disclosure provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the application message display method as described in any of the preceding embodiments.

[0042] This disclosure provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the aforementioned application message display method.

[0043] The application message display method, application message forwarding method, device, electronic device, computer-readable storage medium, and computer product provided in this disclosure can, on the one hand, determine whether a target application is an emergency application by whether the application name includes the keyword "emergency," thereby deciding whether to prominently push application messages from that application to the first application. This process completes the filtering of application types, ensuring that messages pushed to the first object from the second application are all from emergency applications (rather than messages from ordinary applications). This process avoids excessive message redundancy affecting the first object and also improves the prominence of emergency offline reminder messages. On the other hand, reminding the first object with a prominent emergency offline reminder message enables the first object to notice the message in a timely manner, making the first object take the emergency offline reminder message seriously and promptly enter the second application to view the offline message. In addition, if the first object has not registered and activated an account in the second application, the technical solution provided in this disclosure can complete the registration and activation of the second application during the process of the first object jumping from the first application to the second application, improving the registration rate and retention rate of the second application and realizing the promotion and application of the second application.

[0044] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit this disclosure. Attached Figure Description

[0045] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0046] Figure 1 A schematic diagram of an application message forwarding and display system provided in one embodiment of this application is shown.

[0047] Figure 2 This is a flowchart illustrating an application message display method according to an exemplary embodiment.

[0048] Figure 3 This is a schematic diagram illustrating an offline reminder information display according to an exemplary embodiment.

[0049] Figure 4 This is a schematic diagram illustrating an offline reminder information display according to an exemplary embodiment.

[0050] Figure 5 This is a schematic diagram illustrating an offline reminder information display according to an exemplary embodiment.

[0051] Figure 6 This is a flowchart illustrating an application message display method according to an exemplary embodiment.

[0052] Figure 7 This is a schematic diagram illustrating a second application page redirection according to an exemplary embodiment.

[0053] Figure 8 This is a schematic diagram illustrating a second application page redirection according to an exemplary embodiment.

[0054] Figure 9 This is a schematic diagram illustrating a second application page redirection according to an exemplary embodiment.

[0055] Figure 10 This is a schematic diagram illustrating a second application download notification page according to an exemplary embodiment.

[0056] Figure 11 This is a schematic diagram illustrating an authorized login page according to an exemplary embodiment.

[0057] Figure 12 This is a schematic diagram illustrating a nickname and avatar acquisition page according to an exemplary embodiment.

[0058] Figure 13 This is a schematic diagram illustrating a permission acquisition page according to an exemplary embodiment.

[0059] Figure 14 This is a flowchart illustrating an application message display method according to an exemplary embodiment.

[0060] Figure 15 This is a schematic diagram illustrating a candidate team display page according to an exemplary embodiment.

[0061] Figure 16 This is a schematic diagram illustrating a name settings page according to an exemplary embodiment.

[0062] Figure 17 This is a flowchart illustrating an application message display method according to an exemplary embodiment.

[0063] Figure 18 This is a flowchart illustrating an application message forwarding method according to an exemplary embodiment.

[0064] Figure 19 This is a flowchart illustrating a method for adding members according to an exemplary embodiment.

[0065] Figure 20 This is a flowchart illustrating an application message forwarding method according to an exemplary embodiment.

[0066] Figure 21 This is a schematic diagram illustrating an application information forwarding structure according to an exemplary embodiment.

[0067] Figure 22 This is a flowchart illustrating a method for offline message forwarding using an offline message module according to an exemplary embodiment.

[0068] Figure 23 This is a schematic diagram illustrating a message filtering method according to an exemplary embodiment.

[0069] Figure 24 This is a schematic diagram illustrating the generation of an emergency offline reminder message according to an exemplary embodiment.

[0070] Figure 25 This is a block diagram illustrating an application message display device according to an exemplary embodiment.

[0071] Figure 26 This is a block diagram illustrating an application message forwarding device according to an exemplary embodiment.

[0072] Figure 27 A schematic diagram of the structure of an electronic device suitable for implementing embodiments of the present disclosure is shown. Detailed Implementation

[0073] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the embodiments set forth herein; rather, they are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted.

[0074] The features, structures, or characteristics described in this disclosure can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced with one or more specific details omitted, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0075] The accompanying drawings are merely illustrative of this disclosure, and the same reference numerals in the drawings denote the same or similar parts, thus omitting repeated descriptions of them. Some block diagrams shown in the drawings do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0076] The flowchart shown in the accompanying drawings is merely illustrative and does not necessarily include all content and steps, nor does it require execution in the described order. For example, some steps may be broken down, while others may be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0077] In the description of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "multiple" means two or more. The terms "first," "second," etc., do not limit the quantity or order of execution, and "first," "second," etc., do not necessarily imply differences; the terms "contains," "includes," and "has" are used to indicate an open-ended inclusion meaning and refer to the existence of additional elements / components / etc. besides the listed elements / components / etc.

[0078] To better understand the above-mentioned objectives, features and advantages of the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be combined with each other.

[0079] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0080] Figure 1 A schematic diagram of an application message forwarding and display system according to an embodiment of this application is shown. The implementation environment may include: a first terminal 10, a server 20, a second terminal 30, and a fourth terminal 40.

[0081] Among them, the first terminal 10, the second terminal 30, and the fourth terminal 40 can be electronic devices such as mobile phones, desktop computers, tablet computers, game consoles, e-book readers, multimedia playback devices, wearable MP3 players (Moving Picture Experts Group Audio Layer III), MP4 players (Moving Picture Experts Group Audio Layer IV), and laptop computers.

[0082] The first terminal 10 may have a first application and a second application installed. The first application or the second application may be, for example, a social networking application, a financial application, a shopping application, a game application, a video application, an audio application, etc. The user corresponding to the first terminal 10 is a first object. The first application and the second application may be different applications.

[0083] The second terminal 30 may also have a first application and a second application installed, such as a social networking application, a financial application, a shopping application, a game application, a video application, an audio application, etc. The user corresponding to the second terminal can be a third object. The third terminal 40 may also have a first application installed, such as a social networking application, a financial application, a shopping application, a game application, a video application, an audio application, etc. The user corresponding to the fourth terminal 40 can be a fourth object.

[0084] Server 20 can be used to provide background services for applications (first application and / or second application) in the first terminal 10, second terminal 30, or third terminal 40. For example, server 20 can be a background server for the aforementioned first application (and / or second application). Server 20 can be a single server, a server cluster consisting of multiple servers, or a cloud computing service center. Server 20 may include at least one of a first application server 21 and a second application server 22, which are used to provide background services for the first application and the second application, respectively.

[0085] Server 20 establishes communication connections with first terminal 10 and second terminal 30. First terminal 10 runs a first application and a second application. The first application on first terminal 10 can be logged into using a first account, and the second application on first terminal 10 can be logged into using a second account. The first and second accounts can be linked. The second application supports adding contacts from the first application. Second terminal 30 can run both the first and second applications. The first application on second terminal 30 can be logged into using a third account, and the second application on second terminal 30 can be logged into using a fourth account. The third and fourth accounts can be linked. Third terminal 40 can run a first application, which can be logged into using a fifth account.

[0086] The second terminal 30 can perform the following steps: the third object uses the target application in the second application of the first terminal to send an offline message to the first object, wherein the application name of the target application contains the keyword "emergency".

[0087] The server 20 can perform the following steps: receive a target application message sent by a third object to a first object through a target application in a second application; determine that the target application message cannot reach the first object in the second application; determine that the application name of the target application includes an emergency keyword; generate an emergency offline reminder message based on the target application message, the emergency offline reminder message including a prominent reminder identifier; and send the emergency offline reminder message to the first object through the first application to remind the first object that there is an offline message of the target application in the second application.

[0088] The first terminal 10 can perform the following steps: displaying an emergency offline reminder message of the second application in the first application logged in by the first object. The emergency offline reminder message includes a prominent reminder icon and is used to remind the first object that there are offline messages of the target application in the second application. The application name of the target application contains the keyword "emergency". In response to the trigger signal of the emergency offline reminder message, the user jumps from the first application to the second application to view the offline messages of the target application.

[0089] The aforementioned first and second applications can be different types of applications. Different types of applications can refer to situations where the social relationship chains of the first and second applications are maintained independently, and the social relationship ecosystems of the two applications are different. A social relationship chain exists within an application. A social relationship chain includes: the relationship chain between accounts established within the application through social relationships such as contacts, friends, groups, and mutual following. For example, social relationship chains include: friend relationship chains, group relationship chains, and following relationship chains.

[0090] The second application on the first terminal 10 and the second terminal 30 can be the same type of application. The versions of the second application on the first terminal 10 and the second terminal 30 may be the same or different.

[0091] The first application on the first terminal 10, the second terminal 30, and the third terminal 40 can be the same type of application. The versions of the first application on the first terminal 10, the second terminal 30, and the third terminal 40 may be the same or different.

[0092] The first account and the second account are linked accounts, meaning they correspond to the same identity authentication information. For example: the first account and the second account are logged in using the same mobile phone number; the first account and the second account are logged in using the same email address; the first account is obtained through the second account after logging in to the first application; the first account is logged in using a mobile phone number, and the second account is logged in using an email address, with the email address's authentication mobile phone number being the same as the first account's login mobile phone number, etc.

[0093] For example, the second application is a team-based instant messaging application, and the first application is a personal instant messaging application. The second account logged into the team-based instant messaging application is logged into through the first account logged into the personal instant messaging application. The team-based instant messaging application can refer to an organizational relationship established on a team basis. This team can refer to any team consisting of at least two people, such as an enterprise, organization, non-profit organization, or sports organization.

[0094] The second application supports adding contacts from the first application. This means that users can use a second account corresponding to the second application to add target contacts from the first application they are using. This establishes a social relationship chain between the second account and the target contact's account on the second application, enabling cross-application communication.

[0095] The third terminal 40 can also perform the following process on the first application: displaying an emergency offline reminder message of the second application in the first application logged in by the first object. The emergency offline reminder message includes a prominent reminder icon and is used to remind the first object that there are offline messages of the target application in the second application. The application name of the target application contains the keyword "emergency". In response to the trigger signal of the emergency offline reminder message, the user jumps from the first application to the second application to view the offline messages of the target application.

[0096] The first terminal 10, the second terminal 30, the third terminal 40, and the server 20 can communicate with each other via a network. This network can be a wired network or a wireless network.

[0097] It should be understood that Figure 1 The number of terminals, networks, and servers shown is merely illustrative. Server 20 can be a single physical server or a combination of multiple servers. Depending on actual needs, it can have any number of terminal devices, networks, and servers.

[0098] Under the above system architecture, this disclosure provides an application message display method, which can be executed by any electronic device with computing and display capabilities.

[0099] Figure 2 This is a flowchart illustrating an application message display method according to an exemplary embodiment.

[0100] In some embodiments, the technical solution provided in this embodiment can be applied to a first device, wherein the first device may be... Figure 1Terminal devices 10, 30, or 40 include, for example, mobile phones, desktop computers, tablets, game consoles, e-book readers, multimedia playback devices, wearable devices such as MP3 players, MP4 players, and laptop computers.

[0101] Reference Figure 2 The application message display method provided in this embodiment may include the following steps.

[0102] Step S202: Display an emergency offline reminder message of the second application in the first application logged in by the first object. The emergency offline reminder message includes a prominent reminder icon and is used to remind the first object that there is an offline message of the target application in the second application. The application name of the target application contains the keyword "emergency".

[0103] The aforementioned emergency keywords may be words related to relatively urgent events such as major social events, major disasters, major safety incidents, and major health events. Those skilled in the art can set emergency keywords according to actual needs, such as: prevention and control, health, health reporting, online, online, resumption of school, resumption of work, temperature measurement, etc. This disclosure does not impose any restrictions on this.

[0104] The target application can refer to the application function module in the second application. This application function module can be a self-built application in the second application or a third-party application.

[0105] In this context, "self-built application" refers to an application developed and opened by the second application itself. This is typically an H5 page or a mini-program (e.g., a meeting application module, a live streaming application module, a health reporting application module, an announcement application module, an open application module, or a meeting room application module, etc.) that can be embedded in the second application's workspace. "Third-party application" refers to application modules not provided by the second application, such as mini-programs developed by third parties.

[0106] It is understandable that, since third-party applications are developed by third parties and embedded in the second application, the specific functions of these applications may not be determined in advance. Some third-party applications are developed to handle urgent matters, and the messages they send may be urgent. This embodiment filters applications in the second application using urgent keywords, identifying urgent and important applications. The messages from these applications are then pushed to the first application in an urgent and prominent manner, ensuring that the first recipient can promptly notice and process the application messages.

[0107] In this context, "offline message" can refer to a message that cannot be reached by the first object in the second application. "Reachable" can mean that the message arrives and is received by the user.

[0108] Specifically, if the first object does not have an activated account in the second application, the message cannot be delivered to the first object in the second application; or, if the first object has an activated account in the second application, but the activated account has not been logged in for more than 7 days, the message cannot be delivered to the first object in the second application; or, if the first object has an activated account in the second application and the activated account has not been logged in for more than 7 days, and the first object has not joined the target team in the second application, then if a message is sent to the first object from the target team, the message from the target application cannot reach the first object.

[0109] The aforementioned emergency offline reminder message can be generated based on the application name of the second application, the application name of the target application, and the target application message. It is used to prominently and promptly remind the first object in the first application that "an offline message of the target application of the first object exists in the second application." The emergency offline reminder message can include a prominent reminder icon, which can be emergency text (e.g., adding "Emergency Notice" to the subtitle, or adding emergency notes (e.g., "Click to view emergency notice"). The prominent reminder icon can be highlighted or highlighted with a special color (e.g., highlighting the entire display box containing the emergency offline reminder icon, highlighting the words "Emergency Notice," highlighting important text, or displaying it in a special color). The prominent reminder icon can also be animated (e.g., adding a prominent reminder animation). This disclosure does not limit the style of the prominent reminder icon in the emergency offline reminder message; any prominent reminder icon that can remind the first object and enable the first object to notice the emergency offline reminder message in a timely manner is within the scope of protection of this application.

[0110] In some embodiments, when the number of times the first application receives information from the second application is less than a threshold, the first application can display the emergency offline reminder message through a service notification account, which can be the system message account of the first application. When the frequency of the first application receiving information from the second application is greater than or equal to the threshold, the first application can display the emergency offline reminder message through a second application account, which is the session account of the second application in the first application. The second application account can refer to an account specifically created for the second application within the first application, used to display relevant messages from the second application, such as organizational relationship information (address book), communication information (e.g., chat content), and application information (e.g., information sent by applications within the second application). This disclosure does not impose any limitations on this.

[0111] Specifically, when the first object authorizes and confirms in the first application that it can receive messages from the second application, a second application account will be built in the first application for the second application. For example, the second application's program plugin can be followed in the first application to authorize and confirm that it can receive information from the second application.

[0112] In other embodiments, the second application may include at least one team, which may include at least one candidate team. The address book of the members of the at least one candidate team may include a first object. The at least one candidate team may include a target team that sends a target application message to the first object. The first application has been authorized to receive information from the target team. If the number of times the first application receives information from the second application is less than a threshold, the first application may display the emergency offline reminder message through a service notification account, which is the system message account of the first application. If the frequency of the first application receiving information from the second application is greater than or equal to the threshold, the first application may display the emergency offline reminder message through the target team account, which is the session account of the target team in the first application.

[0113] It's important to note that adding the first object to the target team's address book does not mean the first object has joined the target team. In other words, adding the first object to the target team's address book only allows team members to access the first object's message receiving address (such as the first object's identifier). However, whether messages from the target team (including application messages or session messages) can reach the first object depends on whether the first object has already agreed to join the target team. In some embodiments, if the first object has already joined the target team and the first object's login in the second application has not timed out, the first object can normally receive messages from the target team in the second application.

[0114] Suppose that the second application includes teams A, B, C, and D (i.e., the second application may include at least one team), and teams A, B, and C add the first object to their address books. Then teams A, B, and C are at least one of the candidate teams mentioned above. Specifically, teams B and C's address books not only include the first object, but the first object also agrees to join teams B and C. Therefore, information from teams B and C (including application messages or session messages) can normally reach the first object within the second application. However, although team A adds the first object to its address book, the first object has not joined team A. Therefore, information from team A cannot reach the first object within the second application. It is understood that team A, in some embodiments, could be the target team in this application.

[0115] Specifically, when the first object authorizes and confirms in the first application that it can receive messages from the target team, a target team account is created for the target team in the first application. For example, the target team can be followed in the first application to authorize and confirm that it can receive information from the target team. The target team account can refer to an account specifically created for the target team in the first application, which is specifically used to display relevant messages of the target team, such as organizational relationship information (address book), communication information (e.g., chat content), application information (e.g., information sent by the application in the second application), etc. This disclosure does not limit this.

[0116] In other embodiments, if the first object has been authorized to receive information from the target team and the second application, then if the number of times the first application receives information from the second application is less than a threshold, the first application can display the emergency offline reminder message through a service notification account, where the service notification account is the system message account of the first application; if the frequency of the first application receiving information from the second application is greater than or equal to the threshold, the first application displays the emergency offline reminder message through the target team account, where the target team account is the session account of the target team in the first application, and this disclosure does not impose any restrictions on this.

[0117] It is important to note that the service notification account is a system notification account, which is a high-priority information notification account. As you can imagine, an emergency offline reminder message displayed through the service notification will definitely be shown to the first user in the first application and will not be ignored by the first user.

[0118] In some embodiments, the service notification account can display messages from external sources that have not been specified for display. For example, when external applications send messages to the first application, they may include the first application's application identifier but not specify a display account for the message. In such cases, the service notification account can display the message. Therefore, it can display messages from the target application within the first application even before the first application has authorized or confirmed receiving information from the target team and the first application.

[0119] In some embodiments, if the first object has not authorized confirmation to receive information from the target team (or the second application) of the first application, then the aforementioned emergency offline alert message can be displayed through a service notification account, for example, in a manner such as... Figure 3 The aforementioned emergency offline reminder message is displayed in the information display box 301 under the service notification account. The information display box 301 of the service notification account will show that the second application (or the target application in the second application) sent an emergency notification to the first object, and the words "Emergency Notification" will be displayed in the title and remarks (a kind of eye-catching reminder mark) to remind the first object to check in time (the words "Emergency Notification" can be highlighted in red, bolded, or animated).

[0120] In some embodiments, if the first application has authorized confirmation of receiving information from the second application, then an emergency offline alert message can be displayed through the second application's account in the first application. For example, it can be displayed through the second application's account in the first application. Figure 4The emergency offline notification message is displayed in the information display box 401 under the second application account shown. The information display box 401 of this service notification account will show that the second application (or the target application in the second application) sent an emergency notification to the first object, and the words "Emergency Notification" will be displayed in the title and remarks (a kind of eye-catching reminder mark) to remind the first object to check in time (the words "Emergency Notification" can be highlighted in red, bolded, or animated).

[0121] In some embodiments, if the first application has been authorized to confirm receiving information from the target team in the second application, an emergency offline alert message can be displayed through the target team's account in the first application. For example, it can be displayed as follows: Figure 5 The target team account shown displays this urgent offline alert message. Figure 5 The offline messages of the target team in the second application are displayed in the row of the target application in the information display box 501. The message summary section can also display words such as "Urgent Notice" (a prominent reminder label) to remind the first target to check it promptly (this "Urgent Notice" text can be highlighted in red, bolded, or animated). Additionally, the message count reminder section can be animated (e.g., shaking), highlighted, or given special colors to emphasize that there are currently extremely important messages awaiting processing.

[0122] In step S204, in response to a trigger signal for an emergency offline alert message, the user jumps from the first application to the second application to view the offline message of the target application.

[0123] In some embodiments, in response to a trigger signal for an emergency offline alert message, a jump can be made from a first application to a second application to view messages from the target application.

[0124] In some embodiments, the first object logs into a first application using a first account. If the first object has a second account in a second application, it logs into the second application directly using the second account to view target application messages, wherein the first account and the second account are associated accounts; if the first object does not have an activated account in the second application, it activates and registers in the second application using the first account to log into the second application using the account information of the first account.

[0125] The technical solution provided in this embodiment can, on the one hand, determine whether a target application is an emergency application by whether the application name contains the keyword "emergency," thereby deciding whether to prominently push application messages from that application to the first application. This process completes the filtering of application types, ensuring that the messages pushed to the first object from the second application are all from emergency applications (rather than messages from ordinary applications). This process avoids excessive message redundancy from affecting the first object and also improves the prominence of emergency offline reminder messages. On the other hand, it enables the first object to receive messages from the target application in the second application in a timely manner. In addition, if the first object has not registered and activated an account in the second application, the technical solution provided in this disclosure can complete the registration and activation of the second application by the first object during the process of jumping from the first application to the second application, thereby improving the registration rate and retention rate of the second application and realizing the promotion and application of the second application.

[0126] Figure 6 This is a flowchart illustrating an application message display method according to an exemplary embodiment.

[0127] In some embodiments, if the first object logs into the first application through the first account, and the first object does not activate the account in the second application or the first object's activated account in the second application times out and does not log in.

[0128] In some embodiments, the timeout of the first object's activated account (e.g., the second account) in the second application may refer to the first object not logging into the second application for more than a certain period of time (e.g., 7 days), in which case it is necessary to retrieve the relevant information of the first object again to authorize the login to the second application.

[0129] Reference Figure 6 The application message display method provided in this embodiment may include the following steps.

[0130] Step S602: Display an offline reminder message of the second application in the first application that the first object has logged into. The offline reminder message is used to remind the first object that there are offline messages of the target application in the second application. The offline messages of the target application are generated based on the target application messages sent by the target application in the second application to the first object.

[0131] In step S604, in response to a trigger signal for an emergency offline reminder message, a jump page for the second application is displayed, the jump page including a pull-up control for the second application.

[0132] In some embodiments, the pull control can be used to pull up a second application on a first device.

[0133] In some embodiments, if triggered Figure 3 Or such as Figure 4 The emergency offline alert message shown (e.g., the display box 301 or 401 that triggers the emergency offline alert message) can be accessed. Figure 7 or Figure 8 The redirect page shown may include a prominent target notification (such as an emergency notification) and a pull-up control (such as "Open a second application to view").

[0134] In some embodiments, if triggered Figure 6 The information display item showing the location of the emergency offline alert message (e.g.) Figure 6 The information display items corresponding to the target application in the information display frame 601 shown can be accessed. Figure 9 The jump page shown may include at least one information display box (e.g., information display box 901 and information display box 902), and each information display box may include a pull-up control "Please go to the second application to view", which can trigger the pull-up control corresponding to the most recent information display box (e.g., information display box 902) to jump to the second application to view the information of the target application.

[0135] It is understood that the pull-up control can exist in any form on the page to which the page is redirected. For example, it can be a text box, the page to which the page is redirected, or a sound control, etc. This disclosure does not impose any restrictions on this.

[0136] Step S606: In response to a trigger signal for the pull-up control, the authorization login page is displayed so that the first object can authorize the login of the second application using the account information of the first account.

[0137] In some embodiments, if the first object logs into the first application via a first device, and the first device does not have the second application, then after responding to the trigger signal for the emergency offline reminder message and before displaying the redirect page for the second application, the download page for the second application (e.g., ...) can be displayed. Figure 10 The download page shown is 1001. The download page includes download controls (such as...). Figure 10 The "Download Second Application" control shown above; in response to a trigger signal for the download control, download and install the second application.

[0138] In some embodiments, an authorization login page (e.g., ...) may be displayed in response to a trigger signal for the pull-up control. Figure 11(The authorized login page is shown). The authorized login page may display optional authorized login methods, such as logging in using the identity of the first application or logging in using the mobile phone number of the first object. Those skilled in the art will also realize that the authorized login page may allow the first object to log in using other methods such as email.

[0139] In some embodiments, such as Figure 11 After authorizing login as the first application as shown on the login page, you can continue to the nickname retrieval page (e.g., Figure 12 The nickname acquisition page (1201) and permission acquisition page (as shown) are shown. Figure 13 The permission acquisition page shown (1301) allows you to obtain a nickname and related permissions.

[0140] After obtaining the nickname information and relevant permissions, you can log in to the second application using the first account information.

[0141] Step S608: After authorized login, the user is redirected from the first application to the second application to view messages from the target application.

[0142] The improved technical solution in this embodiment requires re-authorization to log in when the first object has not activated an account in the second application or when the first object's activated account in the second application has expired and has not been logged in, so as to retrieve the identity information of the first object. This not only obtains the authorization of the first object in a timely manner, but also improves the security of logging into the second application.

[0143] Figure 14 This is a flowchart illustrating an application message display method according to an exemplary embodiment.

[0144] In some embodiments, the second application may include at least one team, which may include at least one candidate team, the member address book of the at least one candidate team may include a first object, and the at least one candidate team includes a target team that sends a target application message to the first object.

[0145] refer to Figure 14 The above application message display may include the following steps.

[0146] In step S1402, an offline reminder message of the second application is displayed in the first application logged in by the first object. The offline reminder message is used to remind the first object that there are offline messages of the target application in the second application. The offline messages of the target application are generated based on the target application messages sent by the target application in the second application to the first object.

[0147] In step S1404, in response to a trigger signal for an emergency offline reminder message, a jump page for the second application is displayed, the jump page including a pull-up control for the second application.

[0148] Step S1406: In response to a trigger signal for the pull-up control, the authorization login page is displayed so that the first object can authorize the login of the second application using the account information of the first account.

[0149] Step S1408: After authorized login, log in to the second application using the account information of the first account.

[0150] Step S1410: Display at least one candidate team for the first subject to choose to join.

[0151] In some embodiments, if multiple candidate teams have added the first object to their address book in the second application (some candidate teams are teams that the first object has already joined, and some candidate teams are teams that the first object has not joined), then after the first object logs into the second application with the account information of the first account, these multiple candidate teams can be displayed for the first object to choose to join.

[0152] In some embodiments, if there are more than one candidate team, such as Figure 15 As shown, when the first object enters the second application, the multiple candidate teams (such as the target team, team 1XX and team 2XX) can be displayed to the first object.

[0153] Step S1412: In response to a trigger signal for the target team, enter the target team in the second application to view the target application messages in the target team.

[0154] In some embodiments, if previously only the target team added the first object to the address book, but the first object did not agree to join the target team, then in response to a trigger signal targeting the target team, the user can access the name settings page (e.g., ...). Figure 16 (As shown in the name settings page), to determine the name of the first object in the target team, and then enter the target team; if the first object has entered the target team by the target name before, then in response to the trigger signal of the target team this time, it can directly enter the target team by the target name.

[0155] In some other embodiments, if there is only one candidate team and it is the target team, and the first object has previously entered the target team by target name, then in response to the target team's trigger signal, it can directly enter the target team by target name; if there is only one candidate team and it is the target team, and the first object has not previously entered the target team, then in response to the target team's trigger signal, it can enter the name settings page (e.g., ...). Figure 16 (See the name settings page shown) to determine the name of the first object in the target team before entering the target team.

[0156] The improved technical solution in this embodiment, when there are multiple candidate teams including the first object in the address book, will display the candidate teams to the first object for the first object to choose from. This not only shows the user comprehensive and selectable team information, but also makes it convenient for the user to enter the target team in a timely manner.

[0157] Figure 17 This is a flowchart illustrating an application message display method according to an exemplary embodiment.

[0158] In some embodiments, the second application may include at least one team, which may include at least one candidate team. The member address book of the at least one candidate team includes the first object. The at least one candidate team includes the target team. The target application message is sent by the target application to the first object through the target team. The first object has an activated account in the second application and the activated account login has not timed out. The first object has not joined the target team.

[0159] refer to Figure 17 The above application message display method may include the following steps.

[0160] Step S1702: Display an offline reminder message of the second application in the first application that the first object has logged into. The offline reminder message is used to remind the first object that there are offline messages of the target application in the second application. The offline messages of the target application are generated based on the target application messages sent by the target application in the second application to the first object.

[0161] In step S1704, in response to a trigger signal for an emergency offline reminder message, a jump page for the second application is displayed, the jump page including a pull-up control for the second application.

[0162] In step S1706, in response to the trigger signal of the pull control, at least one candidate team is displayed for the first object to select and join.

[0163] In some embodiments, if the first object has an activated account in the second application and the account login has not timed out, and the first object has not joined the target team and there are more than one candidate team, then in response to the trigger signal for the emergency offline reminder message, at least one candidate team can be directly displayed for the first object to join (e.g., Figure 15 (As shown). That is, if the first object has an activated account in the second application and the activated account login has not expired, then no authorization is required and the object can log in to the second application directly.

[0164] Step S1708: In response to the trigger signal for the target team, enter the target team in the second application to view the target application messages in the target team.

[0165] In some embodiments, if the first object has previously logged into the second application using the target name, it can directly enter the target team within the second application in response to a trigger signal for the target team; if the first object has not directly entered the target team before, it can access the name settings page (e.g., Figure 16 (As shown), after setting the name, enter the target team.

[0166] In other embodiments, if there is only one candidate team and it is the target team, and the first object has not entered the target team before, then in response to the trigger signal for the target team, the object directly enters the name setting page, and enters the target team after the name setting is completed.

[0167] In some other embodiments, if there is only one candidate team and it is the target team, and the first object has previously entered the target team by the target name, then in response to the trigger signal for the target team, the object directly enters the name setting page and directly enters the target team by the target name.

[0168] The improved technical solution in this embodiment can directly display multiple candidate teams for the first object to choose from when the first object has an activated account in the second application and the account login has not timed out and the first object has not joined the target team. This simplifies the login process while ensuring the security of the second application login.

[0169] Figure 18 This is a flowchart illustrating an application message forwarding method according to an exemplary embodiment.

[0170] In some embodiments, the technical solution provided in this embodiment can be applied to a second device, wherein the first device may be... Figure 1 The server in the middle (specifically, it can be) Figure 1 (The second application server shown).

[0171] Reference Figure 18 The application message forwarding method provided in this embodiment may include the following steps.

[0172] Step S1802: Receive the target application message sent by the target application to the first object in the second application.

[0173] In some embodiments, the second device can receive a target application message sent by the target application to the first object through the second application. This target application message may be sent by a fourth object to the first object through its logged-in second application.

[0174] Step S1804: Determine that the target application message cannot be delivered to the first object in the second application.

[0175] In some embodiments, when the second device determines that the first object does not have an activated account in the second application, it will consider that the target application message cannot reach the first object; or, when the second device determines that the first object has not logged in to its activated account in the second application after the timeout, it will consider that the target application message cannot reach the first object.

[0176] In some embodiments, the second application may include at least one candidate team, the first object is included in the member address book of at least one candidate team, and the target application message is sent by the target application to the first object through the target team. If the second device determines that the first object has an activated account in the second application and the activated account login has not timed out and the first object has not joined the target team, it will also consider that the target application message cannot reach the first object.

[0177] Step S1806: Determine that the target application's application name contains the keyword "emergency".

[0178] Step S1808: Generate an emergency offline reminder message based on the target application message. The emergency offline reminder message includes a prominent reminder icon.

[0179] When the second device determines that the target application message cannot reach the first object, it will generate an emergency offline reminder message based on the target application message.

[0180] Step S1810: An emergency offline reminder message is sent to the first object through the first application to remind the first object that there is an offline message of the target application in the second application.

[0181] In some embodiments, if it is determined that the frequency at which the first application receives information from the second application is less than a number threshold, an emergency offline reminder message is sent to the first application so that the first application can display the emergency offline reminder message through a service notification account, where the service notification account is the system message account of the first application; if it is determined that the frequency at which the first application receives information from the second application is greater than or equal to the number threshold and the first application has authorized confirmation of receiving information from the second application, an emergency offline reminder message is sent to the second application account in the first application so that the emergency offline reminder message can be displayed through the second application account, where the second application account is the session account of the second application in the first application.

[0182] In other embodiments, the second application includes at least one candidate team, the member address book of at least one candidate team includes the first object, and the at least one candidate team includes a target team. The target application message is sent by the target application to the first object through the target team. If it is determined that the frequency of the first application receiving information from the second application is less than a threshold, an emergency offline reminder message is sent to the first application so that the first application can display the emergency offline reminder message through a service notification account, which is the system message account of the first application. If it is determined that the frequency of the first application receiving information from the second application is greater than or equal to the threshold and the first application has authorized and confirmed receiving information from the target team, then the emergency offline reminder message is sent to the target team account in the first application so that the emergency offline reminder message can be displayed through the target team account, which is the session account of the target team in the first application.

[0183] This disclosure provides a technical solution that, on the one hand, filters target applications by whether their names contain the keyword "emergency" to determine if they are emergency applications. This determines whether to prominently push application messages from such applications to the first application. This process filters the application type of the target application, ensuring that messages pushed to the first user from the second application are all from emergency applications (rather than messages from ordinary applications). This process avoids excessive message redundancy that could affect the first user and also improves the visibility of emergency offline reminder messages. On the other hand, reminding the first user with a prominent emergency offline reminder message allows them to notice the message promptly, thus urging them to take it seriously and check the offline message in the second application. Furthermore, if the first user has not registered and activated an account in the second application, the technical solution provided in this disclosure allows them to complete the registration and activation process during the transition from the first application to the second application, improving the registration and retention rates of the second application and promoting its use.

[0184] Figure 19 This is a flowchart illustrating a method for adding members according to an exemplary embodiment.

[0185] refer to Figure 19 The above method for adding members may include the following steps.

[0186] Step S1902: Receive a member retrieval request sent by a second object in the target team. The member retrieval request is used to retrieve the associated objects of the second object in the first application. The associated objects include the first object.

[0187] The second object and the fourth object can be the same object or different objects; this application does not impose any restrictions on this.

[0188] The associated object of the second object in the first application can refer to an object in the first application that has an association relationship with the second object, such as an object that has a friend relationship with the second object, or an object that has a customer relationship with the second object, etc. This disclosure does not limit this.

[0189] Step S1904: Return the associated object to the second object.

[0190] In some embodiments, after the second device receives a member retrieval request sent by the second object, it retrieves the associated object of the second object from the server corresponding to the first application and returns the associated object to the second object.

[0191] Step S1906: Receive a member addition request for the first object sent by the second object.

[0192] Step S1908: Add the first object to the member address book of the target team according to the member addition request, and determine that the first object has not joined the target team.

[0193] In some embodiments, when the second device receives a member addition request from the second object for the first object, it can add the first object to the address book of the target team so that members of the target team can send messages to the first object.

[0194] However, in some embodiments, adding the first object to the target team's address book does not mean that the first object has joined the target team. That is, adding the first object to the target team's address book means that members of the target team can obtain the first object's message receiving address (such as the first object's identifier, which can be used to identify the message receiving object), but whether messages from the target team can reach the first object still depends on whether the first object has joined the target team.

[0195] In some embodiments, after the first object joins the target team and the first object's login in the second application has not timed out, the first object can normally receive messages from the target team.

[0196] In some embodiments, if the first object does not activate its account in the second application, or the first object's login in the second application times out, or the first object activates its account in the second application but does not join the target team, messages in the target team cannot reach the first object normally, and this application is required to achieve message delivery.

[0197] In some embodiments, the first object can be added to the target team using the following methods.

[0198] That is, the administrator of the target team sends an invitation request to the first object to the second device; the second device receives the invitation request to the first object from the target administrator in the target team; the second device sends an invitation request to the first object through the first application to invite the first object to join the target team; the second device receives the first object's join request in response to the invitation request and adds the first object to the target team.

[0199] Figure 20 This is a flowchart illustrating an application message forwarding method according to an exemplary embodiment.

[0200] In some embodiments, the second application may include at least one candidate team, the member address book of at least one candidate team includes the first object, the candidate team includes the target team, and the target application message is sent by the target application to the first object through the target team.

[0201] refer to Figure 20 The above-mentioned application message forwarding method may include the following steps.

[0202] Step S2002: Receive the target application message sent by the target application to the first object in the second application.

[0203] Step S2004: Determine that the target application message cannot be delivered to the first object in the second application.

[0204] Step S2006: Determine that the target application's application name contains the keyword "emergency".

[0205] Step S2008: Obtain the application name of the target application and the team name of the target team.

[0206] Step S2010: Generate an emergency offline reminder message based on the target application message, application name, and team name.

[0207] Step S2012: Determine whether the frequency at which the first application receives information from the second application (or the target team) is less than the number of times threshold.

[0208] Step S2014: Send the emergency offline reminder message to the first application so that the first application can display the emergency offline reminder message through the service notification account, which is the system message account of the first application.

[0209] Step S2016: Send the emergency offline alert message to the second application account in the first application so that the emergency offline alert message can be displayed through the second application account. The second application account is the session account of the second application in the first application. Alternatively, send the emergency offline alert message to the target team account in the first application so that the emergency offline alert message can be displayed through the target team account. The target team account is the session account of the target team in the first application.

[0210] Figure 21 This is a flowchart illustrating an application information forwarding structure according to an exemplary embodiment.

[0211] refer to Figure 21 The method corresponding to the above application information forwarding structure may include the following steps.

[0212] 1) The fourth object triggers an application message to the first object through the information forwarding capability module (such as OpenAPI (a module provided in the second application that can provide message forwarding capability) in the application module of the target application of the second application (which can be a self-built application or a third-party application).

[0213] 2) If the message module of the second application determines that the application message has no push channel (i.e. the application message cannot reach the first object), then the application message is sent to the offline message module.

[0214] 3) The offline message module generates an emergency offline reminder message based on the application's messages.

[0215] 4) If the offline message module determines that the first application has followed the plugin of the second application (or determines that the first application has bound the second application), then it will forward the emergency offline reminder message to the first object through the first application.

[0216] Figure 22 This is a flowchart illustrating a method for application message forwarding via an offline messaging module, according to an exemplary embodiment.

[0217] In some embodiments, the second application may include at least one candidate team, the member address book of at least one candidate team includes the first object, the candidate team includes the target team, and the target application message is sent by the target application to the first object through the target team.

[0218] refer to Figure 22 The above-mentioned application message forwarding method may include the following steps.

[0219] Step S2202: Receive the application message from the target application.

[0220] That is, receiving target application messages sent by the target application to the first object in the second application.

[0221] Step S2204: Are the push conditions met?

[0222] That is, it is determined that the target application message cannot reach the first object in the second application.

[0223] Step S2206: Determine whether the target application is an important application.

[0224] For example, determine whether the target application's name contains the keyword "emergency." If the target application's name contains the keyword "emergency," then the target application is an important application. Alternatively, determine whether the target application carries an emergency application identifier. If the target application carries an emergency application identifier, then the target application is an important application. The emergency application identifier is used to identify which applications are important, allowing offline application messages of that important application to be sent to the first object through the first application.

[0225] Step S2208: Fill in the emergency message text to generate an emergency offline reminder message.

[0226] In some embodiments, emergency text can be filled into the emergency offline reminder message, such as filling in the words "emergency notification" in an important position; eye-catching animations or eye-catching display effects (such as highlighting, color enhancement) can also be added to the display of the emergency offline reminder message.

[0227] Filling in the above-mentioned emergency text can make the emergency offline reminder message more eye-catching and easier for the first person to notice it.

[0228] Step S2210: Fill in the ordinary message text to generate an ordinary offline reminder message.

[0229] Step S2212: Send an offline reminder message to the first application.

[0230] In some embodiments, if it is determined that the frequency at which the first application receives information from the second application is less than a number threshold, an emergency offline reminder message is sent to the first application so that the first application can display the emergency offline reminder message through a service notification account, where the service notification account is the system message account of the first application; if it is determined that the frequency at which the first application receives information from the second application is greater than or equal to the number threshold and the first application has authorized confirmation of receiving information from the second application, an emergency offline reminder message is sent to the second application account in the first application so that the emergency offline reminder message can be displayed through the second application account, where the second application account is the session account of the second application in the first application.

[0231] In other embodiments, if it is determined that the frequency at which the first application receives information from the second application is less than a number threshold, an emergency offline alert message is sent to the first application so that the first application can display the emergency offline alert message through a service notification account, where the service notification account is the system message account of the first application; if it is determined that the frequency at which the first application receives information from the second application is greater than or equal to the number threshold and the first application has authorized confirmation of receiving information from the target team, an emergency offline alert message is sent to the target team account in the first application so that the emergency offline alert message can be displayed through the target team account, where the target team account is the session account of the target team in the first application.

[0232] In some embodiments, to prevent excessive user harassment, the offline messaging module also includes numerous filtering rules (see reference). Figure 23 The system determines whether a message meets the requirements for pushing offline messages; if the conditions are not met, no message will be pushed. The filtering logic can be abstracted as: global filtering (GlobalFilter), receiver status filtering (RecvrStatusFilter), sender status filtering (SenderStatusFilter), frequency control filtering (FreqFilter), and special logic filtering (CustomerFilter). After filtering, the push channel is assembled; after successful push, statistics are reported.

[0233] Its global filtering feature includes global checks such as preventing push notifications to specific teams, restricting team industry access, and verifying the normal status of enterprise operations.

[0234] Receiver status filtering: This function validates information such as the receiver's status, whether they are offline or not, and whether they are following second application plugins.

[0235] Sender status filtering: Performs basic checks on the sender's status to determine if the user is legitimate.

[0236] Frequency control filtering: This is responsible for controlling the frequency of offline message sending, such as allowing only one message to be received per day.

[0237] Special logic filtering: Some offline messages may have special filtering logic, which can be filtered using CustomerFilter.

[0238] Among them, it can be based on Figure 24 The flowchart shown is filled with emergency (or normal) message text to generate an emergency offline reminder message (or a normal emergency offline reminder message).

[0239] refer to Figure 24 The diagram shown illustrates how emergency offline alert messages can be generated using the following methods.

[0240] (1) Receive the application ID of the target application provided by the message receiving module, and retrieve the application name of the target application.

[0241] (2) Issue emergency keywords that need to be identified through system configuration, such as: prevention and control, health, health reporting, online, online, school resumption, work resumption, temperature measurement, etc.

[0242] (3) If the above emergency keywords exist in the application message, the application name of the target application is matched with the emergency keywords to generate an emergency offline reminder message; if the above emergency keywords do not exist in the application message, a normal emergency offline reminder message is generated based on the application message.

[0243] The above technical solution, for offline message push in the second application, provides more eye-catching text prompts for emergency information pushes, enabling users to handle them promptly and improving the timeliness of emergency message pushes. On the other hand, it can increase the click-through rate of offline messages, thereby achieving the goal of reactivating the application.

[0244] Based on the same inventive concept as the application message display method, this disclosure also provides an application message display device, as shown in the following embodiments. Since the principle by which this device solves the problem is similar to that of the application message display method described above, the implementation of this device embodiment can refer to the implementation of the application message display method described above, and repeated details will not be elaborated further.

[0245] Figure 25 This is a block diagram illustrating an application message display device according to an exemplary embodiment.

[0246] The application message display device can be applied to the first device.

[0247] Reference Figure 25 The application message display device 2500 provided in this embodiment may include: an offline reminder message display module 2501 and a trigger module 2502.

[0248] The offline reminder message display module 2501 can be used to display an emergency offline reminder message of the second application in the first application logged in by the first object. The emergency offline reminder message includes a prominent reminder icon and is used to remind the first object that there are offline messages of the target application in the second application. The application name of the target application contains the keyword "emergency". The trigger module 2502 can be used to jump from the first application to the second application in response to the trigger signal for the emergency offline reminder message in order to view the offline messages of the target application.

[0249] In some embodiments, the offline reminder message display module 2501 may include: a service notification account display submodule.

[0250] The service notification account display submodule can be used to display emergency offline reminder messages by the first application through the service notification account when the number of times the first application receives information from the second application is less than a threshold. The service notification account is the system message account of the first application.

[0251] In some embodiments, the first application has been authorized to receive information from the second application; wherein, the offline reminder message display module 2501 may further include: a second application account display submodule.

[0252] The second application account submodule can be used to display an emergency offline reminder message through the second application account when the frequency of the first application receiving information from the second application is greater than or equal to a threshold. The second application account is the session account of the second application in the first application.

[0253] In some embodiments, the second application includes at least one candidate team, the member address book of at least one candidate team includes a first object, the candidate team includes a target team, and the target application message is sent by the target application to the first object through the target team; the first application has been authorized to confirm receiving information from the target team; wherein, the offline reminder message display module 2501 may further include: a target team account display submodule.

[0254] The target team account display submodule can be used to display an emergency offline reminder message through the target team account when the frequency of the first application receiving information from the second application is greater than or equal to a threshold. The target team account is the session account of the target team in the first application.

[0255] In some embodiments, if the first object does not have an activated account in the second application or the first object's activated account in the second application has expired and has not been logged in, the first object logs into the first application using the first account; wherein the triggering module 2502 may include: a jump page display submodule, an authorization login page display submodule, and a jump rotor module.

[0256] The jump page display submodule can be used to display the jump page of the second application in response to the trigger signal of the emergency offline reminder message. The jump page includes the pull-up control of the second application. The authorization login page display submodule can be used to display the authorization login page in response to the trigger signal of the pull-up control, so that the first object can authorize the login of the second application through the account information of the first account. The jump module can be used to jump from the first application to the second application after authorization login to view the target application message.

[0257] In some embodiments, the second application includes at least one candidate team, the member address book of at least one candidate team includes a first object, and the candidate team includes a target team that sends a target application message to the first object; wherein, the jumper module may include: a second application login unit, a candidate team display unit, and a target team selection unit.

[0258] The second application login unit can be used to log in to the second application using the account information of the first account; the candidate team display unit can be used to display at least one candidate team for the first object to choose to join; the target team selection unit can be used to enter the target team in the second application in response to a trigger signal for the target team, so as to view the target application messages in the target team.

[0259] In some embodiments, the second application includes at least one candidate team, the member address book of at least one candidate team includes a first object, the candidate team includes a target team, and the target application message is sent by the target application to the first object through the target team; the first object has an activated account in the second application and the activated account login has not timed out, and the first object has not joined the target team; wherein, the triggering module 2502 may include: a second application jump page display submodule, a candidate team display submodule, and a target team entry submodule.

[0260] The second application redirect page display submodule can be used to display the redirect page of the second application in response to a trigger signal for an emergency offline reminder message. The redirect page includes a pull-up control for the second application. The selectable team display submodule can be used to display at least one candidate team for the first object to choose to join in response to a trigger signal for the pull-up control. The target team entry submodule can be used to enter the target team in the second application in response to a trigger signal for the target team to view the target application messages in the target team.

[0261] In some embodiments, the first object logs into the first application through a first device, and the first device does not have a second application; the application message display device may include: a download page display module and a download and installation module.

[0262] The download page display module can be used to display the download page of the second application before displaying the redirect page of the second application in response to a trigger signal for an emergency offline reminder message. The download page includes a download control. The download and installation module can be used to download and install the second application in response to a trigger signal for the download control.

[0263] Corresponding to S202 to S206 in the method embodiments, the above modules and corresponding steps implement the same examples and application scenarios, but are not limited to the content disclosed in the above method embodiments. It should be noted that the above modules, as part of an apparatus, can be executed in a computer system such as a set of computer-executable instructions.

[0264] Based on the same inventive concept as application message forwarding, this disclosure also provides an application message forwarding apparatus, as shown in the following embodiments. Since the principle by which this apparatus solves the problem is similar to that of the application message forwarding method described above, the implementation of this apparatus can refer to the implementation of the application message forwarding method described above, and repeated details will not be elaborated further.

[0265] Figure 26 This is a block diagram illustrating an application message forwarding device according to an exemplary embodiment.

[0266] The application message forwarding device can be applied to a second device.

[0267] Reference Figure 26 The application message display device 2600 provided in this embodiment may include: an application message receiving module 2601, a reach determination module 2602, an emergency keyword filtering module 2603, an offline reminder message generation module 2604, and an offline reminder message sending module 2605.

[0268] The application message receiving module 2601 can be used to receive target application messages sent by the target application to the first object in the second application; the reach determination module 2602 can be used to determine that the target application message cannot reach the first object in the second application; the emergency keyword filtering module 2603 can be used to determine that the application name of the target application includes emergency keywords; the offline reminder message generation module 2604 can be used to generate an emergency offline reminder message based on the target application message, and the emergency offline reminder message includes a prominent reminder identifier; the offline reminder message sending module 2605 can be used to send the emergency offline reminder message to the first object through the first application to remind the first object that there are offline messages of the target application in the second application.

[0269] In some embodiments, the second application includes at least one candidate team, the member address book of at least one candidate team includes a first object, the candidate team includes a target team, and the target application message is sent by the target application to the first object through the target team; wherein, the reach determination module 2602 may include: a trigger determination submodule.

[0270] The "reach determination" submodule can be used to determine that the first object does not have an activated account in the second application; or, to determine that the activated account of the first object in the second application has timed out and the first object has not logged in; or, to determine that the first object has an activated account in the second application and the activated account login has not timed out and the first object has not joined the target team; and to determine that the target application message cannot be delivered to the first object in the second application.

[0271] In some embodiments, the application information forwarding device may further include: a member acquisition request receiving module, an associated object return module, a member addition request acquisition module, and an address book addition module.

[0272] The member acquisition request receiving module can be used to receive a member acquisition request sent by a second object in the target team. The member acquisition request is used to obtain the associated object of the second object in the first application. The associated object includes the first object. The associated object return module can be used to return the associated object to the second object. The member addition request acquisition module can be used to receive a member addition request sent by the second object for the first object. The address book addition module can be used to add the first object to the member address book of the target team according to the member addition request, and determine that the first object has not joined the target team.

[0273] In some embodiments, the application message forwarding device may further include: an invitation request receiving module, an invitation request sending module, and a join request receiving module.

[0274] The invitation request receiving module can be used to receive an invitation request sent by the target administrator in the target team to the first object; the invitation request sending module can be used to send an invitation request to the first object through the first application to invite the first object to join the target team; and the join request receiving module can be used to receive the join request sent by the first object in response to the invitation request and add the first object to the target team.

[0275] In some embodiments, the offline reminder message sending module 2605 may include: a first judgment submodule.

[0276] The first determination submodule is used to determine that if the frequency at which the first application receives information from the second application is less than a threshold, the emergency offline reminder message is sent to the first application so that the first application can display the emergency offline reminder message through a service notification account, where the service notification account is the system message account of the first application.

[0277] In some embodiments, the offline reminder message sending module 2605 may include: a second judgment submodule.

[0278] The second determination submodule can be used to determine that the frequency at which the first application receives information from the second application is greater than or equal to the number threshold and the first application has authorized and confirmed receiving information from the second application. In this case, the emergency offline reminder message is sent to the second application account in the first application so that the emergency offline reminder message can be displayed through the second application account. The second application account is the session account of the second application in the first application.

[0279] In some embodiments, the second application includes at least one candidate team, the member address book of the at least one candidate team includes the first object, the at least one candidate team includes a target team, and the target application message is sent by the target application to the first object through the target team; wherein, the offline reminder message sending module 2605 may further include: a third judgment submodule.

[0280] The third judgment submodule can be used to determine that the frequency at which the first application receives information from the second application is greater than or equal to the number threshold and the first application has been authorized to receive information from the target team. If the first application is authorized to receive information from the target team, the emergency offline reminder message will be sent to the target team account in the first application so that the emergency offline reminder message can be displayed through the target team account. The target team account is the session account of the target team in the first application.

[0281] Corresponding to S1802 to S1808 in the method embodiments, the above modules and corresponding steps implement the same examples and application scenarios, but are not limited to the content disclosed in the above method embodiments. It should be noted that the above modules, as part of an apparatus, can be executed in a computer system such as a set of computer-executable instructions.

[0282] The modules and / or sub-modules and / or units described in the embodiments of this application can be implemented in software or hardware. The described modules and / or sub-modules and / or units can also be located in a processor. The names of these modules and / or sub-modules and / or units do not, in some cases, constitute a limitation on the module and / or sub-module and / or unit itself.

[0283] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0284] Furthermore, the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of this disclosure and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0285] Figure 27 A schematic diagram of the structure of an electronic device suitable for implementing embodiments of the present disclosure is shown. It should be noted that... Figure 27 The illustrated electronic device 2700 is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments disclosed herein.

[0286] like Figure 27 As shown, the electronic device 2700 includes a central processing unit (CPU) 2701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 2702 or a program loaded from a storage section 2708 into a random access memory (RAM) 2703. The RAM 2703 also stores various programs and data required for the operation of the electronic device 2700. The CPU 2701, ROM 2702, and RAM 2703 are interconnected via a bus 2704. An input / output (I / O) interface 2705 is also connected to the bus 2704.

[0287] The following components are connected to I / O interface 2705: an input section 2706 including a keyboard, mouse, etc.; an output section 2707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 2708 including a hard disk, etc.; and a communication section 2709 including a network interface card such as a LAN card, modem, etc. The communication section 2709 performs communication processing via a network such as the Internet. A drive 2710 is also connected to I / O interface 2705 as needed. Removable media 2711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 2710 as needed so that computer programs read from them can be installed into storage section 2708 as needed.

[0288] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable storage medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 2709, and / or installed from removable medium 2711. When the computer program is executed by central processing unit (CPU) 2701, it performs the functions defined above in the system of this application.

[0289] It should be noted that the computer-readable storage medium disclosed herein may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable storage medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable storage medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0290] In another aspect, this application also provides a computer-readable storage medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable storage medium carries one or more programs that, when executed by the device, enable the device to perform the following functions: displaying an emergency offline reminder message of a second application in a first application logged in by a first object; the emergency offline reminder message reminding the first object of the existence of offline messages of a target application in the second application, the offline messages of the target application being generated based on target application messages sent to the first object by the target application in the second application; and, in response to a trigger signal for the emergency offline reminder message, jumping from the first application to the second application to view the target application messages.

[0291] When one or more of the above programs are executed by the device, the device may also perform the following functions: receiving a target application message sent by the target application to a first object in a second application; determining that the target application message cannot reach the first object in the second application; generating an emergency offline reminder message based on the target application message; and sending the emergency offline reminder message to the first object through the first application, so that the first object can access the target application in the second application based on the emergency offline reminder message.

[0292] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in various optional implementations of the above embodiments.

[0293] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions of the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) and includes several instructions to cause a computing device (such as a personal computer, server, mobile terminal, or smart device, etc.) to execute the method according to the embodiments of this disclosure, for example... Figure 2 , Figure 7 , Figure 15 , Figure 18 , Figure 19 , Figure 20 , Figure 21 , Figure 22 or Figure 24 One or more of the steps shown.

[0294] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not claimed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.

[0295] It should be understood that this disclosure is not limited to the detailed structures, drawing arrangements or implementations shown herein; rather, this disclosure is intended to cover various modifications and equivalent arrangements contained within the spirit and scope of the appended claims.

Claims

1. A method for displaying application messages, characterized in that, Applied to the first device, including: An emergency offline reminder message from the second application is displayed in the first application where the first object logs in. The emergency offline reminder message includes a prominent reminder icon and is used to remind the first object that there is an offline message from the target application in the second application. The application name of the target application contains the keyword "emergency". The target application is an application function module in the second application. In response to a trigger signal for the emergency offline alert message, the system jumps from the first application to the second application to view the offline messages of the target application; The second application includes at least one candidate team, the member address book of the at least one candidate team includes the first object, the at least one candidate team includes a target team, and the target application message is sent by the target application to the first object through the target team; the first application has been authorized to confirm receiving information from the target team; wherein, the method further includes: If the frequency at which the first application receives information from the second application is greater than or equal to a certain number of times, the first application displays the emergency offline reminder message through the target team account, where the target team account is the session account of the target team in the first application.

2. The method according to claim 1, characterized in that, An emergency offline alert message from the second application is displayed in the first application where the first user logs in, including: If the number of times the first application receives information from the second application is less than a threshold, the first application displays the emergency offline reminder message through a service notification account, which is the system message account of the first application.

3. The method according to claim 2, characterized in that, The first application has been authorized to receive information from the second application; wherein, the method further includes: If the frequency at which the first application receives information from the second application is greater than or equal to the threshold number, the first application displays the emergency offline reminder message through the second application account, where the second application account is the session account of the second application in the first application.

4. The method according to claim 1, characterized in that, The first object has not activated an account in the second application, or the first object's activated account in the second application has expired and has not been logged in, and the first object logs into the first application using the first account; wherein, in response to a trigger signal for the emergency offline reminder message, the user jumps from the first application to the second application to view the offline messages of the target application, including: In response to a trigger signal for the emergency offline alert message, a redirect page for the second application is displayed, the redirect page including a pull-up control for the second application; In response to a trigger signal for the pull-up control, an authorization login page is displayed so that the first object can authorize login to the second application using the account information of the first account; After authorized login, users are redirected from the first application to the second application to view messages from the target application.

5. The method according to claim 4, characterized in that, The second application includes at least one candidate team, whose member address book includes the first object, and the at least one candidate team includes a target team that sent the target application message to the first object; wherein, jumping from the first application to the second application to view offline messages of the target application includes: Log in to the second application using the account information of the first account; The at least one candidate team is displayed for the first object to choose to join; In response to a trigger signal for the target team, access is made to the target team within the second application to view the target application messages within the target team.

6. The method according to claim 1, characterized in that, The second application includes at least one candidate team, the member address book of the at least one candidate team includes the first object, the at least one candidate team includes the target team, and the target application message is sent by the target application to the first object through the target team; The first object has an activated account in the second application, the activated account login has not timed out, and the first object has not joined the target team; wherein, in response to a trigger signal for the emergency offline reminder message, the user jumps from the first application to the second application to view the offline messages of the target application, including: In response to a trigger signal for the emergency offline alert message, a redirect page for the second application is displayed, the redirect page including a pull-up control for the second application; In response to the trigger signal of the pull-up control, the at least one candidate team is displayed for the first object to select and join; In response to a trigger signal for the target team, access the target team in the second application to view the target application messages within the target team.

7. The method according to claim 4 or 6, characterized in that, The first object logs into the first application via a first device, and the second application is not present on the first device; wherein, before displaying the redirect page of the second application after responding to a trigger signal for the emergency offline alert message, the method includes: Display the download page of the second application, the download page including download controls; In response to the trigger signal of the download control, the second application is downloaded and installed.

8. A message forwarding method, characterized in that, Applied to a second device, including: Receive a target application message sent by the target application to the first object in the second application; the target application is an application function module in the second application. It was determined that the target application message could not be delivered to the first object in the second application; The target application's application name was found to contain the keyword "emergency". An emergency offline reminder message is generated based on the target application message, and the emergency offline reminder message includes a prominent reminder icon; The emergency offline alert message is sent to the first object through the first application to remind the first object that there is an offline message from the target application in the second application; The second application includes at least one candidate team, the member address book of the at least one candidate team includes the first object, the at least one candidate team includes a target team, and the target application message is sent by the target application to the first object through the target team; wherein, the method further includes: If it is determined that the frequency at which the first application receives information from the second application is greater than or equal to a threshold number and the first application has been authorized to receive information from the target team, then the emergency offline reminder message is sent to the target team account in the first application so that the emergency offline reminder message can be displayed through the target team account, where the target team account is the target team's session account in the first application.

9. The method according to claim 8, characterized in that, Determining that the target application message cannot be delivered to the first object in the second application includes: It is determined that the first object does not have an activated account in the second application; or, it is determined that the activated account of the first object in the second application has timed out and the first object has not joined the target team. It was determined that the target application message could not be delivered to the first object in the second application.

10. The method according to claim 9, characterized in that, Before determining that the first object has an activated account in the second application, that the activated account login has not timed out, and that the first object has not joined the target team, the method further includes: Receive a member retrieval request sent by a second object in the target team. The member retrieval request is used to retrieve the associated object of the second object in the first application. The associated object includes the first object. Return the associated object to the second object; Receive a request from the second object to add a member to the first object; The first object is added to the member address book of the target team according to the member addition request, and it is determined that the first object has not joined the target team.

11. The method according to claim 10, characterized in that, After determining that the first object has not joined the target team, the method further includes: Receive an invitation request for the first object sent by the target administrator in the target team; The invitation request is sent to the first object through the first application to invite the first object to join the target team; Receive the join request sent by the first object in response to the invitation request, and add the first object to the target team.

12. The method according to claim 8, characterized in that, Sending the emergency offline alert message to the first object via the first application includes: If it is determined that the frequency at which the first application receives information from the second application is less than a threshold, then the emergency offline reminder message is sent to the first application so that the first application can display the emergency offline reminder message through a service notification account, where the service notification account is the system message account of the first application.

13. The method according to claim 12, characterized in that, The method further includes: If it is determined that the frequency at which the first application receives information from the second application is greater than or equal to the threshold number and the first application has authorized and confirmed receiving information from the second application, then the emergency offline reminder message is sent to the second application account in the first application so that the emergency offline reminder message can be displayed through the second application account, where the second application account is the session account of the second application in the first application.

14. An application message display device, characterized in that, Applied to the first device, including: An offline reminder message display module is used to display an emergency offline reminder message of a second application in a first application logged in by a first object. The emergency offline reminder message includes a prominent reminder icon and is used to remind the first object that there is an offline message of a target application in the second application. The application name of the target application contains an emergency keyword. The target application is an application function module in the second application. A triggering module is used to respond to a trigger signal for the emergency offline reminder message, and jump from the first application to the second application to view the offline messages of the target application; The second application includes at least one candidate team, the member address book of the at least one candidate team includes the first object, the at least one candidate team includes a target team, and the target application message is sent by the target application to the first object through the target team; the first application has been authorized to confirm receiving information from the target team; wherein, the offline reminder message display module further includes: The target team account display submodule is used to display the emergency offline reminder message through the target team account when the frequency of the first application receiving information from the second application is greater than or equal to a number threshold. The target team account is the session account of the target team in the first application.

15. The apparatus according to claim 14, characterized in that, An emergency offline alert message from the second application is displayed in the first application where the first user logs in, including: If the number of times the first application receives information from the second application is less than a threshold, the first application displays the emergency offline reminder message through a service notification account, which is the system message account of the first application.

16. The apparatus according to claim 15, characterized in that, The first application has been authorized to receive information from the second application; wherein, the device is further configured to: If the frequency at which the first application receives information from the second application is greater than or equal to the threshold number, the first application displays the emergency offline reminder message through the second application account, where the second application account is the session account of the second application in the first application.

17. The apparatus according to claim 14, characterized in that, The first object has not activated an account in the second application, or the first object's activated account in the second application has expired and has not been logged in, and the first object logs into the first application using the first account; wherein, in response to a trigger signal for the emergency offline reminder message, the user jumps from the first application to the second application to view the offline messages of the target application, including: In response to a trigger signal for the emergency offline alert message, a redirect page for the second application is displayed, the redirect page including a pull-up control for the second application; In response to a trigger signal for the pull-up control, an authorization login page is displayed so that the first object can authorize login to the second application using the account information of the first account; After authorized login, users are redirected from the first application to the second application to view messages from the target application.

18. The apparatus according to claim 17, characterized in that, The second application includes at least one candidate team, whose member address book includes the first object, and the at least one candidate team includes a target team that sent the target application message to the first object; wherein, jumping from the first application to the second application to view offline messages of the target application includes: Log in to the second application using the account information of the first account; The at least one candidate team is displayed for the first object to choose to join; In response to a trigger signal for the target team, access is made to the target team within the second application to view the target application messages within the target team.

19. The apparatus according to claim 14, characterized in that, The second application includes at least one candidate team, the member address book of the at least one candidate team includes the first object, the at least one candidate team includes the target team, and the target application message is sent by the target application to the first object through the target team; The first object has an activated account in the second application, the activated account login has not timed out, and the first object has not joined the target team; wherein, in response to a trigger signal for the emergency offline reminder message, the user jumps from the first application to the second application to view the offline messages of the target application, including: In response to a trigger signal for the emergency offline alert message, a redirect page for the second application is displayed, the redirect page including a pull-up control for the second application; In response to the trigger signal of the pull-up control, the at least one candidate team is displayed for the first object to select and join; In response to a trigger signal for the target team, access the target team in the second application to view the target application messages within the target team.

20. The apparatus according to claim 17 or 19, characterized in that, The first object logs into the first application via a first device, and the second application is not present on the first device; wherein, before displaying the redirect page for the second application after responding to a trigger signal for the emergency offline alert message, the device is further configured to: Display the download page of the second application, the download page including download controls; In response to the trigger signal of the download control, the second application is downloaded and installed.

21. An application message forwarding transposition method, characterized in that, Applied to a second device, including: An application message receiving module is used to receive target application messages sent by a target application to a first object in a second application; the target application is an application function module in the second application. The reach determination module is used to determine that the target application message cannot be delivered to the first object in the second application; An emergency keyword filtering module is used to determine whether the application name of the target application contains emergency keywords; An offline reminder message generation module is used to generate an emergency offline reminder message based on the target application message, wherein the emergency offline reminder message includes a prominent reminder identifier; The offline reminder message sending module is used to send the emergency offline reminder message to the first object through the first application, so as to remind the first object that there is an offline message of the target application in the second application; The second application includes at least one candidate team, the member address book of the at least one candidate team includes the first object, the at least one candidate team includes a target team, and the target application message is sent by the target application to the first object through the target team; wherein, the device is further configured to: If it is determined that the frequency at which the first application receives information from the second application is greater than or equal to a threshold and the first application has been authorized to receive information from the target team, then the emergency offline reminder message is sent to the target team account in the first application so that the emergency offline reminder message can be displayed through the target team account, where the target team account is the target team's session account in the first application.

22. The apparatus according to claim 21, characterized in that, The reach determination module includes: The trigger determination submodule is used to determine whether the first object has no activated account in the second application; or, whether the first object's activated account in the second application has timed out and the user has not logged in; or, whether the first object has an activated account in the second application and the activated account login has not timed out and the first object has not joined the target team; and whether the target application message cannot be delivered to the first object in the second application.

23. The apparatus according to claim 22, characterized in that, Before determining that the first object has an activated account in the second application, that the activated account login has not timed out, and that the first object has not joined the target team, the device is further configured to: Receive a member retrieval request sent by a second object in the target team. The member retrieval request is used to retrieve the associated object of the second object in the first application. The associated object includes the first object. Return the associated object to the second object; Receive a request from the second object to add a member to the first object; The first object is added to the member address book of the target team according to the member addition request, and it is determined that the first object has not joined the target team.

24. The apparatus according to claim 23, characterized in that, After determining that the first object has not joined the target team, the device is further configured to: Receive an invitation request for the first object sent by the target administrator in the target team; The invitation request is sent to the first object through the first application to invite the first object to join the target team; Receive the join request sent by the first object in response to the invitation request, and add the first object to the target team.

25. The apparatus according to claim 21, characterized in that, Sending the emergency offline alert message to the first object via the first application includes: If it is determined that the frequency at which the first application receives information from the second application is less than a threshold, then the emergency offline reminder message is sent to the first application so that the first application can display the emergency offline reminder message through a service notification account, where the service notification account is the system message account of the first application.

26. The apparatus according to claim 25, characterized in that, The device is also used for: If it is determined that the frequency at which the first application receives information from the second application is greater than or equal to the threshold number and the first application has authorized and confirmed receiving information from the second application, then the emergency offline reminder message is sent to the second application account in the first application so that the emergency offline reminder message can be displayed through the second application account, where the second application account is the session account of the second application in the first application.

27. An electronic device, characterized in that, include: Memory; as well as A processor coupled to the memory, the processor being configured to execute, based on instructions stored in the memory, the application message display method as described in any one of claims 1-7 or the application message forwarding method as described in any one of claims 8-13.

28. A computer-readable storage medium having a program stored thereon that, when executed by a processor, implements the application message display method as described in any one of claims 1-7 or the application message forwarding method as described in any one of claims 8-13.

29. A computer program product comprising computer instructions stored in a computer-readable storage medium, characterized in that, When the computer instructions are executed by the processor, they implement the application message display method as described in any one of claims 1-7 or the application message forwarding method as described in any one of claims 8-13.

Images