Message notification method, device and equipment

Abstract

The embodiment of the invention discloses a message notification method, device and equipment. The method applied to a server side comprises the steps that a card content refreshing request, sent by a mobile terminal of a user, for a service card is received, and the card content refreshing request is triggered and sent by exposure of the service card due to the fact that the mobile terminal is switched from a screen-off state to a screen-on state; in response to the card content refreshing request, acquiring a to-be-displayed card content, and additionally sending a message push triggering notification to a message module; returning the to-be-displayed card content to the mobile terminal, so that the mobile terminal displays the to-be-displayed card content on the service card; the message module responds to the message push triggering notification and inquires whether a to-be-notified message of the user exists or not; and if yes, triggering the to-be-notified message to be pushed to the mobile terminal, so that the mobile terminal displays the to-be-notified message to the user.

Description

Technical Field

[0001] This specification relates to the technical field of message pushing, and particularly to message notification methods, devices, and equipment. Background Art

[0002] With the popularization of the use of smart phones, users can conveniently conduct various services through various applications on smart phones.

[0003] The message notification bar of a smart phone is the main channel for applications to convey important information to users. When the user has not opened the phone for a long time, as the number of notification messages sent by applications increases, the messages are gradually stacked and folded in the notification bar, and old messages may not be visible to the user.

[0004] In addition, if the user subscribes to a lot of application message notifications, then the notification bar is occupied by the latest messages, and the messages of other applications are pushed to the second screen that needs to be scrolled down, resulting in a decrease in the reach efficiency and click-through rate of notification messages. Currently, in order to increase the click-through rate of notification messages, some applications try to use notification methods such as text messages and phone calls. However, this solution will significantly increase costs.

[0005] Based on this, a better solution that helps to improve the reach efficiency and click-through rate of notification messages is needed. Summary of the Invention

[0006] One or more embodiments of this specification provide a message notification method, device, and equipment to solve the following technical problem: a better solution that helps to improve the reach efficiency and click-through rate of notification messages is needed.

[0007] To solve the above technical problem, one or more embodiments of this specification are implemented as follows:

[0008] A message notification method provided by one or more embodiments of this specification is applied to a server, and the method includes:

[0009] Receiving a card content refresh request for a service card sent by a user's mobile terminal, where the card content refresh request is triggered and sent by the mobile terminal when switching from the screen-off state to the screen-on state, causing the service card to be exposed;

[0010] Responding to the card content refresh request, obtaining the card content to be displayed, and additionally sending a message push trigger notification to a message module;

[0011] Returning the card content to be displayed to the mobile terminal so that the mobile terminal can display the card content to be displayed on the service card;

[0012] The message module responds to the message push trigger notification to query whether there are any pending notification messages for the user;

[0013] If so, trigger the push of the message to be notified to the mobile terminal so that the mobile terminal can display the message to be notified to the user.

[0014] Another message notification method provided by one or more embodiments of this specification is applied to the user's mobile terminal or the client of a specified application on the mobile terminal. The method includes:

[0015] If the service card is exposed due to the mobile terminal switching from the screen-off state to the screen-on state, send a card content refresh request for the service card to the server;

[0016] Receive the card content to be displayed returned by the server in response to the card content refresh request, and display the card content to be displayed on the service card;

[0017] Receive the message to be notified of the user triggered and pushed by the server, and display the message to be notified to the user;

[0018] Among them, the server implements the trigger in the following manner: in response to the card content refresh request, additionally send a message push trigger notification to the message module, and the message module responds to the message push trigger notification to trigger the push of the message to be notified of the user to the mobile terminal.

[0019] A message notification device provided by one or more embodiments of this specification is applied to the server. The device includes:

[0020] A refresh request receiving module that receives a card content refresh request for a service card sent by the user's mobile terminal, where the card content refresh request is triggered and sent when the service card is exposed due to the mobile terminal switching from the screen-off state to the screen-on state;

[0021] An additional notification sending module that, in response to the card content refresh request, obtains the card content to be displayed and additionally sends a message push trigger notification to the message module;

[0022] A card content returning module that returns the card content to be displayed to the mobile terminal so that the mobile terminal can display the card content to be displayed on the service card;

[0023] A message to be notified query module that, when the message module responds to the message push trigger notification, queries whether there is a message to be notified of the user;

[0024] A message push trigger module that, if so, triggers the push of the message to be notified to the mobile terminal so that the mobile terminal can display the message to be notified to the user.

[0025] A message notification device provided by one or more embodiments of this specification is applied to a user's mobile terminal or to a client of a specified application on the mobile terminal. The device includes:

[0026] A refresh request sending module, if the service card is exposed due to the mobile terminal switching from the screen-off state to the screen-on state, sends a card content refresh request for the service card to the server.

[0027] A card content display module, receives the card content to be displayed returned by the server in response to the card content refresh request, and displays the card content to be displayed on the service card.

[0028] A pending notification message display module, receives the user's pending notification message pushed by the server, and displays the pending notification message to the user.

[0029] Wherein, the server implements the triggering in the following manner: in response to the card content refresh request, additionally sends a message push trigger notification to the message module, and the message module, in response to the message push trigger notification, triggers the pushing of the user's pending notification message to the mobile terminal.

[0030] A message notification device provided by one or more embodiments of this specification is applied to a server. The device includes:

[0031] At least one processor; and,

[0032] A memory communicatively connected to the at least one processor; wherein,

[0033] The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute:

[0034] Receive a card content refresh request for a service card sent by a user's mobile terminal, where the card content refresh request is triggered and sent when the mobile terminal switches from the screen-off state to the screen-on state, causing the service card to be exposed;

[0035] In response to the card content refresh request, obtain the card content to be displayed, and additionally send a message push trigger notification to the message module;

[0036] Return the card content to be displayed to the mobile terminal so that the mobile terminal can display the card content to be displayed on the service card;

[0037] The message module triggers a notification in response to the message push, and queries whether there is a message to be notified for the user;

[0038] If so, trigger the push of the message to be notified to the mobile terminal, so that the mobile terminal can display the message to be notified to the user.

[0039] A message notification device provided by one or more embodiments of this specification is applied to the user's mobile terminal or the client of a specified application on the mobile terminal. The device includes:

[0040] At least one processor; and,

[0041] A memory communicatively connected to the at least one processor; wherein,

[0042] The memory stores instructions executable by the at least one processor. When the instructions are executed by the at least one processor, the at least one processor is enabled to execute:

[0043] If the service card is exposed due to the mobile terminal switching from the screen-off state to the screen-on state, send a card content refresh request for the service card to the server;

[0044] Receive the card content to be displayed returned by the server in response to the card content refresh request, and display the card content to be displayed on the service card;

[0045] Receive the message to be notified of the user triggered and pushed by the server, and display the message to be notified to the user;

[0046] Wherein, the server implements the trigger in the following manner: in response to the card content refresh request, additionally send a message push trigger notification to the message module, and the message module triggers the push of the message to be notified of the user to the mobile terminal in response to the message push trigger notification.

[0047] The above-mentioned at least one technical solution adopted by one or more embodiments of this specification can achieve the following beneficial effects: Instead of immediately pushing the messages to be notified to the user's mobile terminal (such as a smart phone) as in the traditional solution when there are messages to be notified for the user, it is to push the messages to be notified in coordination with the exposure timing of the service card on the mobile terminal. Here, it is considered that when the mobile phone switches from the screen-off state to the screen-on state, resulting in the exposure of the service card, in this case, there is a high probability that it is caused by the user immediately unlocking the phone to view the phone at present. When the service card is exposed, a card content refresh request will be automatically sent to the server to display the latest content that the service card can provide. Then, by taking advantage of the card content refresh request, the message module of the server is additionally triggered to push the messages to be notified to the user in a timely manner. Since there is a high probability that the user is looking at the phone at present, there is a corresponding high probability that the user will see the messages to be notified in real time. Therefore, it helps to improve the notification message reach rate and click-through rate, and the cost is very low. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments recorded in this specification. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0049] Figure 1 It is a schematic flowchart of a message notification method provided for one or more embodiments of this specification;

[0050] Figure 2 It is a schematic diagram of the message notification bar of an existing smart phone;

[0051] Figure 3 It is a schematic diagram of the content refresh principle of a service card of a smart phone provided for one or more embodiments of this specification;

[0052] Figure 4 For one or more embodiments of this specification Figure 3 It is a schematic diagram of the principle of a message notification scheme;

[0053] Figure 5 It is a schematic flowchart of another message notification method provided for one or more embodiments of this specification;

[0054] Figure 6 It is a schematic flowchart of a message notification scheme based on message reconstruction provided for one or more embodiments of this specification;

[0055] Figure 7Schematic structural diagram of a message notification device provided for one or more embodiments of this specification;

[0056] Figure 8 Schematic structural diagram of another message notification device provided for one or more embodiments of this specification;

[0057] Figure 9 Schematic structural diagram of a message notification device provided for one or more embodiments of this specification;

[0058] Figure 10 Schematic structural diagram of another message notification device provided for one or more embodiments of this specification. Detailed implementation manners

[0059] Embodiments of this specification provide a message notification method, device, equipment, and storage medium.

[0060] In order to enable persons in the technical field to better understand the technical solutions in this specification, the following will clearly and completely describe the technical solutions in the embodiments of this specification in conjunction with the accompanying drawings in the embodiments of this specification. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all the embodiments. Based on the embodiments of this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the scope of protection of this application.

[0061] To solve the problems in the background art, this application considers using service cards outside the application end to subtly and accurately sense the state of the user unlocking and lighting up the mobile phone. Then, seize the opportunity when the user is currently viewing the mobile phone and send message notifications as promptly as possible so that the user can see them on the spot, in order to improve the reach efficiency of the notification messages of the application. Moreover, on the basis of such a general idea, the solution is further polished to make the exposure of the message notification to the user more natural and smooth, so as to improve the user experience.

[0062] Based on the above idea, the solution of this application will be further described below. The solution of this application at least involves the user's terminal device (mainly mobile terminals such as smart phones, tablet computers, game consoles, etc., and the following embodiments will be described with mobile terminals as examples), and one or more corresponding server ends of the terminal device.

[0063] Figure 1 Schematic flowchart of a message notification method provided for one or more embodiments of this specification. This process is described from the perspective of the above-mentioned server end. The server end at least includes the server end of a certain specified application on the user's mobile terminal; in addition, if necessary, it may also include other server ends dedicated to pushing notification messages to the mobile terminal, such as the server end of a mobile communication operator, etc.

[0064] Figure 1 The process in includes the following steps:

[0065] S102: Receive a card content refresh request for a service card sent by a user's mobile terminal, wherein the card content refresh request is triggered by the mobile terminal switching from an off screen to a bright screen, causing the service card to be exposed.

[0066] There are two normal states for mobile terminals with screens (usually smartphones), namely, the screen-off locked state and the screen-on use state. When a user uses the phone with the screen on, he or she will immediately pay attention to the phone to obtain the content currently displayed on the screen. Based on this principle, this application learns the user's phone usage habits or pushes some information content of concern to the user in real time, such as notification messages, by sensing the entry of the screen-on state.

[0067] Service cards are used to conveniently display specific card content (usually including some relatively fixed interactive spaces and some dynamically updated service information) to users on mobile terminals. Users can see service cards without entering an application on the mobile terminal. Service cards are usually on the default desktop or secondary desktop (for example, the negative one screen, which is the first additional desktop displayed by swiping left from the default desktop) on the mobile terminal.

[0068] In the case expected by the present application with a high probability of occurrence, the service card is in the default interface displayed after the mobile terminal turns on the screen, or in the secondary screen interface of the mobile terminal. The default displayed interface is, for example, the main desktop. If the mobile terminal has only one screen, the secondary screen interface can be a secondary desktop, which can usually be reached by swiping left (for example, swiping left once to reach the negative one screen) or right from the main desktop. If the mobile terminal has more than two screens, the secondary screen can be a secondary desktop of the main screen, or it can be the main desktop or secondary desktop of the secondary screen.

[0069] Service cards can be provided by mobile terminal manufacturers or mobile terminal operating system service providers. They often cooperate with applications on mobile terminals to build service cards. In this case, the application service provider provides the card content to be displayed on the service card. The application can get more exposure opportunities, which helps to attract more user traffic to the application.

[0070] The card content on the service card is dynamically updated, and the following update mechanism is adopted: when the service card is exposed (displayed on the front-end interface of the mobile terminal), it can automatically (usually automatically triggered every time it is exposed) send a card content refresh request to the corresponding server (for example, the server of the application pre-associated with the service card) to request the latest card content to be displayed.

[0071] The applicant has noticed that the exposure of the service card is usually caused by the mobile terminal switching from the screen-off state to the screen-on state, thus naturally displaying the desktop or the secondary desktop (the user may need to unlock the screen and swipe the screen additionally to switch the desktop). And the mobile terminal switching from the screen-off state to the screen-on state is very likely to be caused by the user's immediate desire to use the mobile terminal (for example, wanting to use a certain application, wanting to check if there are missed calls, wanting to check if there are new messages, etc.) and unlocking and opening it. This correspondingly means that there is a very high probability that the user is currently actively looking at the mobile terminal. Therefore, this application considers aiming at this opportunity to timely push notification messages to the user so that the user can see the notification message on the spot, thus achieving effective reach of the notification message to the user.

[0072] In one or more embodiments of this specification, the server includes the server of a specified application on the user's mobile terminal, and the service card targeted by the content refresh request is pre-associated with the specified application.

[0073] In this case, for the mobile terminal, if the service card is exposed, this exposure action will trigger the mobile terminal to call the server interface provided by the specified application, and through the server interface, send a card content refresh request for the service card to the server. It should be noted that the entity executing this call action does not necessarily need to be the client of the specified application, but it is possible that there is logic other than the client (such as the service card itself, or other logic provided by the operating system to support the service card, etc.) to execute. In this way, the client of the specified application on the server does not need to be in the started state.

[0074] S104: In response to the card content refresh request, obtain the card content to be displayed, and additionally send a message push trigger notification to the message module.

[0075] In response to the card content refresh request, on the one hand, it is possible to obtain the specified service information determined by the cooperation between the specified application (the application pre-associated with the service card) and the manufacturer of the mobile terminal as the card content to be displayed.

[0076] On the other hand, it is the additional processing action specified in this application. The message module is on the server side, responsible for notification messages and responsible for triggering the notification message to notify the user. In one or more embodiments of this specification, through the card content refresh request, it is immediately sensed that the user's mobile terminal is currently on the screen. Furthermore, in addition to normally obtaining the card content to be displayed for refreshing the service card, more importantly, it immediately and additionally instructs the message module to cooperate and take action, seizing the current screen-on opportunity to trigger message pushing.

[0077] In contrast, in the traditional solution, as long as there is a new message to be notified in the message module, the push of this new message to be notified will be triggered immediately (unlike the present application which coordinates with the card content refresh timing and does not send an additional message push trigger notification to the message module in response to a card content refresh request). As a result, it is difficult to ensure that the user can see the pushed message in a timely manner. This message is very likely to accumulate silently in the notification bar of the user's mobile terminal, and even when the user subsequently turns on the mobile terminal, it is not certain that the user can notice this message.

[0078] S106: Return the card content to be displayed to the mobile terminal so that the mobile terminal can display the card content to be displayed on the service card.

[0079] S108: In response to the message push trigger notification, the message module queries whether there is a message to be notified for the user.

[0080] To prevent misunderstanding, it is emphasized here that the message to be notified and the card content to be displayed are different contents, and the message to be notified is not displayed in the service card. The notification message mentioned in the background technology is essentially the message to be notified here. It is just that since the message has not been notified to the user at this moment and is a message that needs to be notified to the user, it is therefore called "to be notified".

[0081] Generally, after the message to be notified arrives at the mobile terminal, it will be displayed in the message notification bar on the mobile terminal. The message notification bar and the service card mentioned above are different display entities and should not be confused.

[0082] In response to the message push trigger notification, if it is queried that there is no message to be notified for the user, there is no need to trigger the message push. If there is, the subsequent steps are executed.

[0083] It should be noted that it can be seen that in response to the card content refresh request, two parts of actions are executed. One part is the action related to the card content, and the other part is the action related to the message push. These two parts of actions can be executed independently of each other, and the two parts of actions can be executed in parallel, and there may not be a fixed order of execution. In this way, the efficiency is relatively high. For example, step S108 may be executed before step S106, or may be executed in parallel.

[0084] S110: If so, trigger the push of the message to be notified to the mobile terminal so that the mobile terminal can display the message to be notified to the user.

[0085] In one or more embodiments of this specification, the message module directly pushes the message to be notified to the mobile terminal; alternatively, the message module first sends the message to be notified to another entity responsible for message pushing (such as a mobile terminal manufacturer or a communication operator), and then this entity pushes the message to be notified to the mobile terminal. It should be noted that this triggering action and pushing action can be executed as soon as possible (preferably instantaneously) to seize this opportunity when the user's screen is lit this time.

[0086] Upon receiving the message to be notified, the mobile terminal immediately displays the message to be notified to the user.

[0087] In one or more embodiments of this specification, in the case of not receiving a card content refresh request, the mobile terminal may be in the screen-off state, which indicates that the user's current attention is not on the mobile terminal. Therefore, the message module can be actively and temporarily inhibited from triggering the push of the user's message to be notified to the mobile terminal. Specifically, the importance of the message to be notified can be analyzed here. If the message to be notified is very important, it is still pushed to the user in a timely manner to avoid delaying the user's affairs; otherwise, it can be temporarily not pushed, but wait until a card content refresh request is received before pushing.

[0088] By Figure 1 this method, unlike the traditional solution where as soon as there is a user's message to be notified, it is immediately pushed to the user's mobile terminal (such as a smart phone), instead, it coordinates with the timing of the exposure of the service card on the mobile terminal to push the message to be notified. Here, it is considered that the mobile phone switches from the screen-off state to the screen-on state, resulting in the exposure of the service card. In this case, there is a high probability that it is caused by the user currently unlocking the phone immediately to view the phone. When the service card is exposed, a card content refresh request will be automatically sent to the server to display the latest content that the service card can provide. Then, by taking advantage of the card content refresh request, the message module on the server is additionally triggered to push the message to be notified to the user in a timely manner. Since there is a high probability that the user is currently looking at the phone, there is a corresponding high probability that the user will see the message to be notified in real time. Therefore, it helps to improve the notification message reach rate and click-through rate, and the cost is very low.

[0089] Based on Figure 1 this method, this specification also provides some specific implementation schemes and extended schemes of this method, which will be continued to be described below.

[0090] For the sake of easy understanding, in combination with some actual effect diagrams, the specific implementation schemes are exemplarily illustrated. Taking a smart phone as an example of a mobile terminal, Figure 2 FIG. is a schematic diagram of the message notification bar of an existing smart phone. For the sake of protecting privacy, some content is blocked, but it does not affect the understanding of the following description. The same situation exists in more attached drawings and will not be elaborated further.

[0091] The message notification bar of a mobile phone is the main channel for applications on the mobile phone to convey important information to users. When the user has not opened the mobile phone, as the number of messages sent by applications increases, the message notifications gradually accumulate and fold in the message notification bar, and the old messages may not be visible to the user. Figure 2 You can see that there are messages from three apps in the message notification bar. From top to bottom, the first two apps have some messages accumulated and folded respectively, and the third app has a message that has not yet been accumulated and folded.

[0092] In addition, if the user subscribes to many app message notifications, the message notification bar will be occupied by the latest message notification, and the messages of other apps will be squeezed to the second screen that slides down. Figure 2 In the figure, you can see that in addition to the messages of the three apps mentioned above, there is also a fourth app's message that has not been fully displayed. There may be more apps below that cannot be seen on the current screen.

[0093] In this case, users can only directly see the latest individual messages, and need to manually expand and collapse other messages before browsing them, which is inconvenient and easy to miss messages. This may affect the efficiency of reaching users with a large number of messages.

[0094] This application is based on service cards to timely perceive the phone screen. Figure 3 A schematic diagram of the content refresh principle of a service card of a smart phone provided in one or more embodiments of this specification.

[0095] exist Figure 3 In the figure, the negative first screen of the mobile phone is shown on the left. The white area in the lower half of the negative first screen is the service card associated with a payment application. It should be noted that the service card can also be on the desktop of the mobile phone. In the service card, three areas are divided as an example, namely: left area, upper right area, and lower right area. The upper right area and the lower right area respectively show fixed function controls, namely the "Scan" function control and the "Payment and Receipt Function Control". The left area is the "Service Assistant" area, which is used to display some of the latest payment-related service information.

[0096] In this case, if the service card is exposed, the corresponding server interface will be called to refresh the content in the "Service Assistant" area, for example, Figure 3 Send a card content refresh request to the "App Cloud" in the app, and after receiving the latest card content returned by the App Cloud, the latest card content can be displayed in the service assistant area.

[0097] Further, Figure 4 One or more embodiments of this specification provide for Figure 3 A schematic diagram of the principle of a message notification solution.

[0098] Figure 4 The solution in

[0099] The user unlocks the mobile phone and enters the mobile phone desktop or swipes to enter the negative first screen, resulting in the exposure of the service card;

[0100] After the service card is exposed, it triggers the refresh of the card content and calls the APP cloud interface to query the recently recommended card content to be displayed;

[0101] After the APP cloud receives the query request (i.e., the card content refresh request), it first returns the recommended card content to be displayed, and then notifies the message module that the user's mobile phone has been unlocked and the screen is on (substantially, the service card has been exposed, which very likely means that the user has unlocked and turned on the screen of the mobile phone);

[0102] After the message module receives the screen-on notification (i.e., the message push trigger notification), it checks the user's current messages to be notified and calls the mobile device cloud (another device for pushing messages) interface to push the messages to be notified;

[0103] After the mobile device cloud receives the message notification, it processes the format of the message and then pushes it to the user's mobile phone. It can be seen that Figure 4 an exemplary transaction reminder message is pushed in

[0104] The user's mobile phone displays the pushed messages to be notified. At this time, the user is very likely to be looking at the mobile phone, so they can immediately see the messages to be notified, thus improving the message notification reach efficiency.

[0105] Based on the same idea, one or more embodiments of this specification also provide a flow diagram of another message notification method, which is described from the perspective of the user's mobile terminal or the client of a specified application on the mobile terminal. See Figure 5 .

[0106] Figure 5 The process in

[0107] S502: If the mobile terminal switches from the screen-off state to the screen-on state, resulting in the exposure of the service card, send a card content refresh request for the service card to the server;

[0108] S504: Receive the card content to be displayed returned by the server in response to the card content refresh request, and display the card content to be displayed on the service card;

[0109] S506: Receive the notification message to be sent to the user triggered by the server, and display the notification message to the user; wherein, the server triggers the above in the following manner: in response to the card content refresh request, additionally send a message push trigger notification to the message module, and the message module triggers the push of the user's notification message to the mobile terminal in response to the message push trigger notification.

[0110] For the specific implementation manner, refer to the Figure 1 process description, which will not be elaborated here.

[0111] In practical applications, when a user unlocks and turns on the screen of the mobile phone, they usually have a relatively clear purpose, which may not necessarily be to view new notification messages, but more likely to want to use a certain application. In this case, the present application further optimizes the previous message notification scheme, making the message notification method more in line with the user's purpose of using a certain application. Refer to Figure 6 .

[0112] Figure 6 FIG. is a schematic flowchart of a message notification scheme based on message reconstruction provided by one or more embodiments of the present specification. The execution subject of this process includes a server, which is specifically used to trigger the push of the notification message to be sent to the mobile terminal, so that the mobile terminal can display the notification message to the user.

[0113] Figure 6 The process in

[0114] S602: Receive the style data sent by the mobile terminal, where the style data reflects the interface style of the first application opened by the mobile terminal after switching from the screen-off state to the screen-on state.

[0115] In one or more embodiments of the present specification, the server includes the server of the above-mentioned specified application, and the first application opened is different from the specified application. The first application is the application that the user actually wants to view. In order to meet the user's such purpose and adapt to the situation of the first application, the notification message to be sent is reconstructed. The reconstruction includes at least one of the following two aspects: style and actual content.

[0116] In terms of style, the mobile terminal determines the style data corresponding to the first application opened after the user unlocks the screen and lights it up, through means such as screenshot analysis, and then sends it to the server. The server then converts the notification message to be sent into a notification message with an imitated style according to the received style data, and the imitated style imitates the interface style of the first application. In this case, the notification message with the imitated style looks like a message sent by the first application in terms of appearance. Thus, it is easier for the user to notice and then actively view it, and overall it will not give the user a sudden feeling, and the user's viewing process is relatively smooth and coordinated.

[0117] Furthermore, it is also possible to reconstruct the notification message to be sent from the aspect of the actual content.

[0118] S604: Obtain the service information of the first application.

[0119] The service information is, for example, the service type, service purpose, and relatively unique service highlights (service points that can better distinguish it from similar applications) of the first application. The service information can also be the relevant service information in the page currently shown to the user by the first application, which can be collected through means such as screenshot analysis.

[0120] S606: Reconstruct the content of the notification message to be sent by integrating the semantics of the notification message to be sent and the service information, and generate a reconstructed notification message to be sent to adapt to the service information and express the semantics.

[0121] According to the service information, the notification message to be sent is re-described, so that the semantics of the most important part of the original notification message to be sent remain basically unchanged, while the overall expression method changes, and it expresses the semantics around the service information. Make the reconstructed notification message to be sent seem like a message belonging to the first application, or a message related to the service corresponding to the first application.

[0122] For example, assume that the semantics of the final part of the original notification message to be sent include "You have consumed 5 yuan this time", and the first application is a grocery shopping application. The reconstructed notification message to be sent may include "You have consumed 5 yuan this time, and a vegetable package has been matched for you in the grocery shopping application. Spend another 5 yuan to get this vegetable package", or include "You have consumed 5 yuan this time. Do you know that 5 yuan can also be matched with the calorie intake of your diet like this? Attached is a 5-yuan calorie list".

[0123] S608: Generate a notification message with an imitated style according to the style data and the reconstructed notification message to be sent.

[0124] S610: Trigger the push of the to-be-notified message with the imitation style to the mobile terminal, so that the mobile terminal uses the imitation style to display the to-be-notified message to the user.

[0125] It should be noted that the reconstruction of the to-be-notified message can also be performed by the mobile terminal. In this case, the server only needs to be responsible for triggering the push of the original to-be-notified message to the mobile terminal, and the mobile terminal will display it to the user after reconstruction.

[0126] Through Figure 6 this solution, the feeling of being disturbed by the user is reduced. The process of message notification is coordinated with the user's operation of the application, making the presentation more smooth and fluent. Moreover, it is also convenient to bring additional useful information to the user, especially business information that the user may be interested in.

[0127] In addition, it is also considered that if the card content refresh request is not received for a long time, the server may accumulate multiple to-be-notified messages and continue to accumulate. In this case, once the card content refresh request is received and triggered for push later, the mobile terminal may instantaneously receive multiple to-be-notified messages.

[0128] To prevent this situation from causing trouble to the user, the to-be-notified message can also be reconstructed here, specifically including: determining whether there are multiple to-be-notified messages and the number exceeds a set threshold (for example, 3 or 5, etc.); if so, extracting keywords from each to-be-notified message respectively; generating a new to-be-notified message according to the extracted keywords, and triggering the push of the newly generated to-be-notified message to the mobile terminal, so that the mobile terminal displays the to-be-notified message to the user.

[0129] Each extracted keyword can be included in the newly generated to-be-notified message, and the user is allowed to interact with the keyword. For example, click on the keyword, and after clicking, trigger the server to push the original to-be-notified message corresponding to the keyword to the mobile terminal for display to the user. For the original to-be-notified messages corresponding to other unclicked keywords, they can also be delayed and pushed separately at an appropriate time, which helps to obtain more user attention opportunities and also avoids putting pressure on the user.

[0130] Based on the same idea, one or more embodiments of this specification also provide an apparatus and a device corresponding to the above method, as Figures 7 - 10 shown. The apparatus and the device can correspondingly execute the above method and related alternative solutions.

[0131] Figure 7 The structural schematic diagram of a message notification apparatus provided by one or more embodiments of this specification, which is applied to the server. The apparatus includes:

[0132] A refresh request receiving module 702 receives a card content refresh request for a service card sent by a user's mobile terminal. The card content refresh request is triggered and sent by the mobile terminal when switching from the screen-off state to the screen-on state, which causes the service card to be exposed.

[0133] An additional notification sending module 704, in response to the card content refresh request, obtains the card content to be displayed and additionally sends a message push trigger notification to the message module.

[0134] A card content returning module 706 returns the card content to be displayed to the mobile terminal so that the mobile terminal can display the card content to be displayed on the service card.

[0135] A pending notification message querying module 708, in response to the message push trigger notification by the message module, queries whether there is a pending notification message for the user.

[0136] A message push triggering module 710, if so, triggers the pending notification message to be pushed to the mobile terminal so that the mobile terminal can display the pending notification message to the user.

[0137] Optionally, the server includes a server of a specified application. The service card is pre-associated with the specified application so that the exposure of the service card can trigger the card content refresh request to be sent through the service server interface provided by the specified application.

[0138] The additional notification sending module 704 obtains specified service information determined by the cooperation between the specified application and the manufacturer of the mobile terminal as the card content to be displayed.

[0139] Optionally, the pending notification message and the card content to be displayed are different contents, and the pending notification message is not displayed in the service card.

[0140] Optionally, the service card is in the interface that is defaultly displayed after the mobile terminal is turned on, or in the secondary screen interface of the mobile terminal.

[0141] Optionally, the additional notification sending module 704 additionally sends a screen-on notification to the message module to notify the message module that the mobile terminal has been turned on, so as to trigger the message module to cooperate with the screen-on to instantaneously push the pending notification message.

[0142] Optionally, the message push triggering module 710 receives style data sent by the mobile terminal, and the style data reflects the interface style of the first application opened by the mobile terminal after switching from the screen-off state to the screen-on state.

[0143] Convert the message to be notified into a message to be notified with an imitated style according to the style data, where the imitated style imitates the interface style of the first application.

[0144] Trigger the push of the message to be notified with the imitated style to the mobile terminal, so that the mobile terminal uses the imitated style to display the message to be notified to the user.

[0145] Optionally, the server includes a server of a specified application, and the first application opened is a different application from the specified application.

[0146] Optionally, the message push trigger module 710 obtains the service information of the first application.

[0147] Reconstruct the content of the message to be notified by integrating the semantics of the message to be notified and the service information to generate a reconstructed message to be notified, so as to express the semantics in adaptation to the service information.

[0148] Generate a message to be notified with an imitated style according to the style data and the reconstructed message to be notified.

[0149] Optionally, the message push trigger module 710 determines whether there are multiple messages to be notified and the number exceeds a set threshold.

[0150] If so, extract keywords from each message to be notified.

[0151] Generate a new message to be notified according to the extracted keywords, and trigger the push of the newly generated message to be notified to the mobile terminal, so that the mobile terminal displays the newly generated message to the user.

[0152] Optionally, the additional notification sending module 704 suppresses the message module from triggering the push of the message to be notified of the user to the mobile terminal when the card content refresh request is not received.

[0153] Figure 8 It is a schematic structural diagram of another message notification device provided by one or more embodiments of this specification, which is applied to the user's mobile terminal or the client of a specified application on the mobile terminal. The device includes:

[0154] A refresh request sending module 802, if the service card is exposed due to the mobile terminal switching from the screen-off state to the screen-on state, sends a card content refresh request for the service card to the server.

[0155] The card content display module 804 receives the card content to be displayed returned by the server in response to the card content refresh request, and displays the card content to be displayed on the service card;

[0156] The pending notification message display module 806 receives the pending notification messages of the user triggered and pushed by the server, and displays the pending notification messages to the user;

[0157] Wherein, the server implements the triggering in the following manner: in response to the card content refresh request, an additional message push trigger notification is sent to the message module, and the message module responds to the message push trigger notification to trigger the pushing of the user's pending notification messages to the mobile terminal.

[0158] Figure 9 A schematic structural diagram of a message notification device provided by one or more embodiments of this specification, which is applied to a server. The device includes:

[0159] At least one processor; and,

[0160] A memory communicatively connected to the at least one processor; wherein,

[0161] The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute:

[0162] Receive a card content refresh request sent by the user's mobile terminal for a service card. Wherein, the card content refresh request is triggered and sent when the mobile terminal switches from the screen-off state to the screen-on state, resulting in the exposure of the service card;

[0163] In response to the card content refresh request, obtain the card content to be displayed, and additionally send a message push trigger notification to the message module;

[0164] Return the card content to be displayed to the mobile terminal so that the mobile terminal can display the card content to be displayed on the service card;

[0165] The message module responds to the message push trigger notification to query whether there are any pending notification messages of the user;

[0166] If so, trigger the pushing of the pending notification messages to the mobile terminal so that the mobile terminal can display the pending notification messages to the user.

[0167] Figure 10A structural schematic diagram of a message notification device provided for one or more embodiments of this specification, which is applied to a user's mobile terminal or to a client of a specified application on the mobile terminal. The device includes:

[0168] At least one processor; and,

[0169] A memory communicatively connected to the at least one processor; wherein,

[0170] The memory stores instructions executable by the at least one processor. When the instructions are executed by the at least one processor, the at least one processor is enabled to execute:

[0171] If the service card is exposed due to the mobile terminal switching from the screen-off state to the screen-on state, send a card content refresh request for the service card to the server;

[0172] Receive the card content to be displayed returned by the server in response to the card content refresh request, and display the card content to be displayed on the service card;

[0173] Receive the pending notification message of the user triggered and pushed by the server, and display the pending notification message to the user;

[0174] Wherein, the server implements the triggering in the following manner: in response to the card content refresh request, additionally send a message push trigger notification to the message module, and the message module triggers the push of the user's pending notification message to the mobile terminal in response to the message push trigger notification.

[0175] Based on the same concept, one or more embodiments of this specification further provide a non-volatile computer storage medium, which is applied to the server. The medium stores computer-executable instructions, and the computer-executable instructions are set as:

[0176] Receive a card content refresh request for a service card sent by a user's mobile terminal, where the card content refresh request is triggered and sent when the mobile terminal switches from the screen-off state to the screen-on state, causing the service card to be exposed;

[0177] In response to the card content refresh request, obtain the card content to be displayed, and additionally send a message push trigger notification to the message module;

[0178] Return the card content to be displayed to the mobile terminal so that the mobile terminal can display the card content to be displayed on the service card;

[0179] The message module queries whether there is a pending notification message of the user in response to the message push trigger notification;

[0180] If so, trigger the push of the to-be-notified message to the mobile terminal, so that the mobile terminal displays the to-be-notified message to the user.

[0181] One or more embodiments of this specification also provide another non-volatile computer storage medium, which is applied to the user's mobile terminal or the client of a specified application on the mobile terminal. The medium stores computer-executable instructions, and the computer-executable instructions are set as follows:

[0182] If the service card is exposed due to the mobile terminal switching from the screen-off state to the screen-on state, send a card content refresh request for the service card to the server;

[0183] Receive the card content to be displayed returned by the server in response to the card content refresh request, and display the card content to be displayed on the service card;

[0184] Receive the to-be-notified message of the user triggered and pushed by the server, and display the to-be-notified message to the user;

[0185] Among them, the server implements the trigger in the following manner: in response to the card content refresh request, additionally send a message push trigger notification to the message module, and the message module triggers the push of the to-be-notified message of the user to the mobile terminal in response to the message push trigger notification.

[0186] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software improvements (improvements to method flows). However, with the development of technology, many method flow improvements today can be regarded as direct improvements to hardware circuit structures. Almost all designers obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement to a method flow cannot be implemented using a hardware entity module. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is an integrated circuit whose logical function is determined by the user programming the device. Designers can program themselves to "integrate" a digital system onto a single PLD, without having to ask a chip manufacturer to design and fabricate a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in program development and writing. The original code before compilation also has to be written in a specific programming language, which is called a Hardware Description Language (HDL). There is not just one type of HDL, but many, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones currently are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also be aware that by simply performing some logical programming on the method flow using the above-mentioned several hardware description languages and programming it into the integrated circuit, it is easy to obtain the hardware circuit that implements the logical method flow.

[0187] The controller can be implemented in any suitable manner. For example, the controller can take the form of, for example, a microprocessor or a processor and a computer-readable medium storing computer-readable program code (such as software or firmware) executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of the controller include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that, in addition to implementing the controller in the form of pure computer-readable program code, it is entirely possible to make the controller implement the same function in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be regarded as the structures within the hardware component. Or even, the devices for implementing various functions can be regarded as either software modules for implementing the method or the structures within the hardware component.

[0188] The systems, devices, modules, or units illustrated in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0189] For the convenience of description, when describing the above devices, they are described separately as various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0190] Those skilled in the art should understand that the embodiments of this specification can be provided as a method, a system, or a computer program product. Therefore, the embodiments of this specification can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments of this specification can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) containing computer-usable program code.

[0191] This specification is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments of the specification. It should be understood that each flow and / or block in the flowchart and / or block diagram, and combinations of flows and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processors of general-purpose computers, special-purpose computers, embedded processors, or other programmable data processing devices to generate a machine, such that the instructions executed by the processors of the computer or other programmable data processing devices produce means for implementing the functions specified in one or more of the flows Figure 1 one or more of the flows and / or blocks Figure 1 one or more of the blocks for implementing the specified functions.

[0192] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory produce a manufactured article including instruction means for implementing the functions specified in one or more of the flows Figure 1 one or more of the flows and / or blocks Figure 1 one or more of the blocks.

[0193] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more of the flows Figure 1 one or more of the flows and / or blocks Figure 1 one or more of the blocks.

[0194] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0195] The memory may include non-permanent memory in the form of computer-readable media, random access memory (RAM), and / or non-volatile memory such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of computer-readable media.

[0196] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0197] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity or device including the element.

[0198] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0199] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment, and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0200] The specific embodiments of the present specification are described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve the desired result. Additionally, the processes depicted in the figures do not necessarily require the particular order shown or sequential order to achieve the desired result. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0201] The above description is only for one or more embodiments of the present specification and is not intended to limit the present specification. For those skilled in the art, various changes and modifications can be made to one or more embodiments of the present specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of one or more embodiments of the present specification shall be included within the scope of the claims of the present specification.

Claims

1. A message notification method, applied to a server, the method comprising: Receiving a card content refresh request sent by a user's mobile terminal for a service card, wherein the card content refresh request is triggered and sent when the mobile terminal switches from the screen-off state to the screen-on state, causing the service card to be exposed; In response to the card content refresh request, obtaining the card content to be displayed, and additionally sending a message push trigger notification to a message module; Returning the card content to be displayed to the mobile terminal so that the mobile terminal can display the card content to be displayed on the service card; The message module queries whether there is a message to be notified for the user in response to the message push trigger notification; If so, triggering the message to be notified to be pushed to the mobile terminal so that the mobile terminal can display the message to be notified to the user.

2. The method according to claim 1, wherein the server comprises a server of a specified application, and the service card is pre-associated with the specified application so that the exposure of the service card can trigger the card content refresh request to be sent through the service server interface provided by the specified application; The obtaining the card content to be displayed specifically comprises: Obtaining specified service information determined by cooperation between the specified application and the manufacturer of the mobile terminal as the card content to be displayed.

3. The method according to claim 1, wherein the message to be notified and the card content to be displayed are different contents, and the message to be notified is not displayed in the service card.

4. The method according to claim 1, wherein the service card is in the interface that is default displayed after the mobile terminal is turned on, or in the secondary screen interface of the mobile terminal.

5. The method according to claim 1, the additionally sending a message push trigger notification to the message module specifically comprises: Additionally sending a screen-on notification to the message module for notifying the message module that the mobile terminal has been turned on, so as to trigger the message module to cooperate with the screen-on to immediately push the message to be notified.

6. The method according to claim 1, the triggering the message to be notified to be pushed to the mobile terminal so that the mobile terminal can display the message to be notified to the user specifically comprises: Receiving style data sent by the mobile terminal, the style data reflecting the interface style of the first application opened after the mobile terminal switches from the screen-off state to the screen-on state; According to the style data, converting the message to be notified into a message to be notified with an imitation style, the imitation style imitating the interface style of the first application; Triggering the message to be notified with the imitation style to be pushed to the mobile terminal so that the mobile terminal can display the message to be notified to the user in the imitation style.

7. The method according to claim 6, wherein the server comprises a server of a specified application, and the first application opened is a different application from the specified application.

8. The method according to claim 7, the converting the message to be notified into a message to be notified with an imitation style according to the style data specifically comprises: Obtain the service information of the first application; By integrating the semantics of the to-be-notified message and the service information, reconstruct the content of the to-be-notified message to generate a reconstructed to-be-notified message to adapt to the service information and express the semantics; Generate a to-be-notified message with an imitation style according to the style data and the reconstructed to-be-notified message.

9. The method according to claim 1, wherein triggering the push of the to-be-notified message to the mobile terminal so that the mobile terminal displays the to-be-notified message to the user specifically includes: Determine whether there are multiple to-be-notified messages and the number exceeds a set threshold; If so, extract keywords from each of the to-be-notified messages; According to the extracted keywords, generate a new to-be-notified message, and trigger the push of the newly generated to-be-notified message to the mobile terminal so that the mobile terminal displays the to-be-notified message to the user.

10. The method according to claim 1 further includes: Suppress the message module from triggering the push of the user's to-be-notified message to the mobile terminal when the card content refresh request is not received.

11. A message notification method applied to a user's mobile terminal or a client of a specified application on the mobile terminal, the method includes: If the mobile terminal switches from the screen-off state to the screen-on state, causing the service card to be exposed, send a card content refresh request for the service card to the server; Receive the card content to be displayed returned by the server in response to the card content refresh request, and display the card content to be displayed on the service card; Receive the to-be-notified message of the user triggered and pushed by the server, and display the to-be-notified message to the user; Wherein, the server implements the triggering in the following manner: in response to the card content refresh request, additionally send a message push trigger notification to the message module, and the message module responds to the message push trigger notification to trigger the push of the user's to-be-notified message to the mobile terminal.

12. A message notification device applied to a server, the device includes: A refresh request receiving module that receives a card content refresh request for a service card sent by a user's mobile terminal, wherein the card content refresh request is triggered and sent when the mobile terminal switches from the screen-off state to the screen-on state, causing the service card to be exposed; An additional notification sending module that, in response to the card content refresh request, obtains the card content to be displayed and additionally sends a message push trigger notification to the message module; A card content returning module that returns the card content to be displayed to the mobile terminal so that the mobile terminal displays the card content to be displayed on the service card; A to-be-notified message querying module that, when the message module responds to the message push trigger notification, queries whether there is a to-be-notified message of the user; A message push triggering module that, if so, triggers the push of the to-be-notified message to the mobile terminal so that the mobile terminal displays the to-be-notified message to the user.

13. The device according to claim 12, wherein the server includes a server for a specified application, and the service card is pre-associated with the specified application, so that the exposure of the service card can trigger the card content refresh request to be sent through the service server interface provided by the specified application; The additional notification sending module obtains specified service information determined by cooperation between the specified application and the manufacturer of the mobile terminal as the card content to be displayed.

14. The device according to claim 12, wherein the message to be notified is different from the card content to be displayed, and the message to be notified is not displayed in the service card.

15. The device according to claim 12, wherein the service card is in the interface that is default displayed after the mobile terminal is lit up, or in the secondary screen interface of the mobile terminal.

16. The device according to claim 12, wherein the additional notification sending module additionally sends a screen-on notification to the message module to notify the message module that the mobile terminal has been lit up, so as to trigger the message module to cooperate with the screen-on to instantaneously push the message to be notified.

17. The device according to claim 12, wherein the message push trigger module receives style data sent by the mobile terminal, and the style data reflects the interface style of the first application opened after the mobile terminal switches from the screen-off state to the screen-on state; According to the style data, convert the message to be notified into a message to be notified with an imitated style, and the imitated style imitates the interface style of the first application; Trigger the message to be notified with the imitated style to be pushed to the mobile terminal, so that the mobile terminal uses the imitated style to display the message to be notified to the user.

18. The device according to claim 17, wherein the server includes a server for a specified application, and the first application opened is a different application from the specified application.

19. The device according to claim 18, wherein the message push trigger module obtains the service information of the first application; By fusing the semantics of the message to be notified and the service information, reconstruct the content of the message to be notified to generate a reconstructed message to be notified, so as to express the semantics in adaptation to the service information; Generate a message to be notified with an imitated style according to the style data and the reconstructed message to be notified.

20. The device according to claim 12, wherein the message push trigger module determines whether there are multiple messages to be notified and the number exceeds a set threshold; If so, extract keywords from each message to be notified respectively; According to the extracted keywords, newly generate a message to be notified, and trigger the newly generated message to be notified to be pushed to the mobile terminal, so that the mobile terminal displays the message to be notified to the user.

21. The device according to claim 12, wherein the additional notification sending module suppresses the message module from triggering the push of the message to be notified of the user to the mobile terminal when the card content refresh request is not received.

22. A message notification device is applied to a user's mobile terminal or a client of a specified application on the mobile terminal. The device includes: A refresh request sending module, which, if the service card is exposed due to the mobile terminal switching from the screen-off state to the screen-on state, sends a card content refresh request for the service card to the server; A card content display module, which receives the card content to be displayed returned by the server in response to the card content refresh request and displays the card content to be displayed on the service card; A message to be notified display module, which receives the message to be notified of the user triggered and pushed by the server and displays the message to be notified to the user; Wherein, the server implements the triggering in the following manner: in response to the card content refresh request, additionally sends a message push trigger notification to the message module, and the message module, in response to the message push trigger notification, triggers the message to be notified of the user to be pushed to the mobile terminal.

23. A message notification device is applied to a server. The device includes: At least one processor; And, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute: Receive a card content refresh request for a service card sent by a user's mobile terminal, where the card content refresh request is triggered and sent when the service card is exposed due to the mobile terminal switching from the screen-off state to the screen-on state; In response to the card content refresh request, obtain the card content to be displayed and additionally send a message push trigger notification to the message module; Return the card content to be displayed to the mobile terminal so that the mobile terminal can display the card content to be displayed on the service card; The message module, in response to the message push trigger notification, queries whether there is a message to be notified of the user; If so, trigger the message to be notified to be pushed to the mobile terminal so that the mobile terminal can display the message to be notified to the user.

24. A message notification device is applied to a user's mobile terminal or a client of a specified application on the mobile terminal. The device includes: At least one processor; And, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute: If the service card is exposed due to the mobile terminal switching from the screen-off state to the screen-on state, send a card content refresh request for the service card to the server; Receive the card content to be displayed returned by the server in response to the card content refresh request and display the card content to be displayed on the service card; Receive the message to be notified of the user triggered and pushed by the server and display the message to be notified to the user; Among them, the server implements the triggering in the following manner: in response to the card content refresh request, an additional message push trigger notification is sent to the message module, and the message module triggers the push of the user's pending notification message to the mobile terminal in response to the message push trigger notification.

Images