CN107864229B - Message pushing method and device - Google Patents
Message pushing method and device Download PDFInfo
- Publication number
- CN107864229B CN107864229B CN201711441528.2A CN201711441528A CN107864229B CN 107864229 B CN107864229 B CN 107864229B CN 201711441528 A CN201711441528 A CN 201711441528A CN 107864229 B CN107864229 B CN 107864229B
- Authority
- CN
- China
- Prior art keywords
- client
- message
- target application
- notification bar
- preset platform
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The present disclosure provides a message pushing method and device, wherein the method includes: when the cache information corresponding to the target application on the client is determined to be cleared and the notification bar message corresponding to the target application is sent to the client, re-registering a message pushing function for a preset platform on the client; pushing the notification bar message to the client based on the re-registered message pushing function; the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process. The method and the device for pushing the notification bar message achieve the purpose that the server side can still push the notification bar message to the client side even if the cache information corresponding to the target application on the client side is removed, improve the delivery capacity of the notification bar message corresponding to the target application, and improve user experience.
Description
Technical Field
The present disclosure relates to the field of information interaction, and in particular, to a message pushing method and apparatus.
Background
In the related art, even if a local Application (App) on a client registers for a message push service, once cache information corresponding to the App on the client is cleared, a notification bar message pushed by a server cannot be received any more, and user experience is poor.
Disclosure of Invention
In order to overcome the problems in the related art, embodiments of the present disclosure provide a message pushing method and apparatus.
According to a first aspect of the embodiments of the present disclosure, a message pushing method is provided, where the method is used at a server side, and the method includes:
when the cache information corresponding to the target application on the client is determined to be cleared and the notification bar message corresponding to the target application is sent to the client, re-registering a message pushing function for a preset platform on the client;
pushing the notification bar message to the client based on the re-registered message pushing function;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
Optionally, the re-registering the message pushing function for the preset platform on the client includes:
re-registering a message pushing function for a preset platform on the client through a target channel according to registration information corresponding to the client pre-stored in the target application;
the target channel is a transmission channel which is pre-established between the server side and the preset platform.
Optionally, the re-registering the message pushing function for the preset platform on the client includes:
reestablishing a message pushing channel for a preset platform on the client;
the pushing the notification bar message to the client based on the re-registered message pushing function includes:
and pushing the notification bar message to the client based on the reestablished message pushing channel.
Optionally, the method further comprises:
after receiving a confirmation message sent by the client, executing the step of re-registering the message pushing function for the preset platform on the client;
the confirmation message is used for confirming that the client side has registered the message push service corresponding to the target application, and the client side stores the icon corresponding to the target application.
According to a second aspect of the embodiments of the present disclosure, there is provided a message pushing method, where the method is used for a client, and the method includes:
after the cache information corresponding to the target application is cleared, receiving a notification bar message which is pushed by a server side based on a message pushing function registered again for a preset platform and corresponds to the target application;
displaying the notification bar message;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
Optionally, before receiving a notification bar message, which is pushed by the server side based on a message pushing function registered again for a preset platform and corresponds to the target application, the method further includes:
sending a confirmation message to the server;
the confirmation message is used for confirming that the client side has registered the message push service corresponding to the target application, and the client side stores the icon corresponding to the target application.
Optionally, before receiving the notification bar message corresponding to the target application and pushed by the server based on the message pushing function re-registered for the preset platform, the method further includes:
acquiring registration information corresponding to the target application on the client;
and sending the registration information corresponding to the client to a server, and storing the registration information corresponding to the client in the target application by the server.
According to a third aspect of the embodiments of the present disclosure, there is provided a message pushing apparatus, where the apparatus is used on a server side, and the apparatus includes:
the registration module is configured to re-register a message pushing function for a preset platform on a client when cache information corresponding to a target application on the client is determined to be cleared and a notification bar message corresponding to the target application is sent to the client;
a push module configured to push the notification bar message to the client based on the message push function re-registered by the registration module;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
Optionally, the registration module includes:
the registration submodule is configured to re-register a message pushing function for a preset platform on the client through a target channel according to registration information corresponding to the client and pre-stored in the target application;
the target channel is a transmission channel which is pre-established between the server side and the preset platform.
Optionally, the registration sub-module is further configured to reestablish a message push channel for a preset platform on the client;
the push module comprises:
a push submodule configured to push the notification bar message to the client based on the message push channel re-established by the registration submodule.
Optionally, the apparatus further comprises:
the control module is configured to control the registration module to re-register a message pushing function for a preset platform on the client after determining that the confirmation message sent by the client is received;
the confirmation message is used for confirming that the client side has registered the message push service corresponding to the target application, and the client side stores the icon corresponding to the target application.
According to a fourth aspect of the embodiments of the present disclosure, there is provided a message pushing apparatus, where the apparatus is used for a client, and the apparatus includes:
the receiving module is configured to receive a notification bar message which is pushed by a server side based on a message pushing function registered again for a preset platform and corresponds to the target application after cache information corresponding to the target application is cleared;
a display module configured to display the notification bar message received by the receiving module;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
Optionally, the apparatus further comprises:
the first sending module is configured to send a confirmation message to the server side;
the confirmation message is used for confirming that the client side has registered the message push service corresponding to the target application, and the client side stores the icon corresponding to the target application.
Optionally, the apparatus further comprises:
the acquisition module is configured to acquire the registration information corresponding to the target application on the client;
a second sending module, configured to send the registration information obtained by the obtaining module to a server, where the server stores the registration information corresponding to the client in the target application.
According to a fifth aspect of embodiments of the present disclosure, a computer-readable storage medium is provided, where the storage medium stores a computer program for executing the message pushing method according to the first aspect.
According to a sixth aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium storing a computer program for executing the message pushing method according to the second aspect.
According to a seventh aspect of the embodiments of the present disclosure, there is provided a message pushing apparatus, where the apparatus is used on a server side, and the apparatus includes:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
when the cache information corresponding to the target application on the client is determined to be cleared and the notification bar message corresponding to the target application is sent to the client, re-registering a message pushing function for a preset platform on the client;
pushing the notification bar message to the client based on the re-registered message pushing function;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
According to an eighth aspect of the embodiments of the present disclosure, there is provided a message pushing apparatus, where the apparatus is used for a client, and the apparatus includes:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
after the cache information corresponding to the target application is cleared, receiving a notification bar message which is pushed by a server side based on a message pushing function registered again for a preset platform and corresponds to the target application;
displaying the notification bar message;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:
in the embodiment of the disclosure, even if the cache information corresponding to the target application on the client is cleared, the server may still re-register the message push function for the preset platform on the client when sending the notification bar message corresponding to the target application, so as to push the notification bar message based on the re-registered message push function. Through the process, the aim that the server side can still push the notification bar message to the client side even if the cache information corresponding to the target application on the client side is removed is achieved, the delivery capacity of the notification bar message corresponding to the target application is improved, and the user experience is improved.
In the embodiment of the disclosure, the server already records the registration information corresponding to the client in the target application stored in the server, and the server can re-register the message push function for the preset platform through the target channel. The target channel is a transmission channel which is established by the server side between the server side and the preset platform in advance. Further, a message pushing channel may be re-established for the preset platform based on the registration information, so that a notification bar message may be subsequently pushed based on the re-established message pushing channel. Through the process, after the client clears the cache information corresponding to the target application, the server can still register the message pushing function for the preset platform again so as to push the notification bar message in the following process.
In the embodiment of the present disclosure, optionally, after receiving the confirmation message sent by the client, the server re-registers the message pushing function for the preset platform on the client. The confirmation message is used for confirming that the client side has registered the message push service corresponding to the target application, and the client side stores the icon corresponding to the target application. That is to say, the server side can push the notification bar message to the client side only when the user wants to obtain the notification bar message corresponding to the target application, so that the user experience is improved.
In the embodiment of the disclosure, after determining that the cache information corresponding to the target application is cleared, the client may receive a notification bar message, which is pushed by the server based on a message pushing function registered again for a preset platform and corresponds to the target application, so as to display the notification bar message. The preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process. Through the process, even if the cache information corresponding to the target application on the client is removed, the notification bar message which is pushed by the server and corresponds to the target application can be received, so that the notification bar message is displayed, the phenomenon that a user misses an important message after the cache information is removed is avoided, the delivery capacity of the notification bar message corresponding to the target application is improved, and the user experience is improved.
In the embodiment of the disclosure, the client may send a confirmation message to the server when confirming that the client registers the message push service corresponding to the target application and the client stores the icon corresponding to the target application, and the server may re-register the message push function for the preset platform on the client when pushing the notification bar message based on the confirmation message. Through the process, when the user wants to receive the notification bar message corresponding to the target application, the notification bar message can be pushed to the client side by the server side in time, the user is prevented from missing important messages, and the user experience is improved.
In the embodiment of the disclosure, the client can send the registration information corresponding to the target application to the server, and the registration information is stored by the server, so that even if the cache information corresponding to the target application on the subsequent client is cleared, the server can still push the notification bar message corresponding to the target application to the client, the delivery capability of the notification bar message corresponding to the target application is improved, and the user experience is good.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
Fig. 1 is a schematic diagram illustrating a message push scenario according to an exemplary embodiment.
Fig. 2A and 2B are schematic diagrams illustrating a message push scenario according to an example embodiment.
Fig. 3 is a flowchart illustrating a message pushing method according to an exemplary embodiment.
Fig. 4 is a flow chart illustrating another message pushing method according to an example embodiment.
Fig. 5 is a flow chart illustrating another message pushing method according to an example embodiment.
Fig. 6 is a schematic diagram illustrating another message push scenario in accordance with an example embodiment.
Fig. 7 is a flowchart illustrating another message pushing method according to an example embodiment.
Fig. 8 is a flowchart illustrating another message pushing method according to an example embodiment.
Fig. 9 is a flowchart illustrating another message pushing method according to an example embodiment.
Fig. 10 is a block diagram illustrating a message pushing apparatus according to an example embodiment.
Fig. 11 is a block diagram illustrating another message pushing apparatus according to an example embodiment.
Fig. 12 is a block diagram illustrating another message pushing apparatus according to an example embodiment.
Fig. 13 is a block diagram illustrating another message pushing apparatus according to an example embodiment.
Fig. 14 is a block diagram illustrating another message pushing apparatus according to an example embodiment.
Fig. 15 is a block diagram illustrating another message pushing apparatus according to an example embodiment.
Fig. 16 is a block diagram illustrating another message pushing apparatus according to an example embodiment.
Fig. 17 is a schematic structural diagram of a message pushing device according to an exemplary embodiment of the present disclosure.
Fig. 18 is a schematic structural diagram of another message pushing device according to an exemplary embodiment of the present disclosure.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
The terminology used in the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as operated herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present disclosure. The word "if," as used herein, may be interpreted as "at … …" or "at … …" or "in response to a determination," depending on the context.
In the related art, if a user opens a certain application that is not installed on a client through the client, for example, a mobile phone, a computer, an ipad, or the like, the user may click a virtual installation key corresponding to the application through an application store, as shown in fig. 1. And after the installation is finished, clicking a virtual key for opening the application or a virtual icon corresponding to the application to open the application.
In the embodiment of the present disclosure, a target application is provided, where the target application runs on a preset platform of a client, optionally, the preset platform may be a direct service platform, and the target application is an application whose installation and download process does not need user confirmation, and the installation and download process runs on a background of the client.
For example, when the client does not install the target application, the user may directly click a virtual button for opening the target application, for example, as shown in fig. 2A, or click a preset URL (Uniform resource Locator), for example, as shown in fig. 2B, to directly open the target application.
Certainly, after the first installation is completed, the target application may output prompt information to enable a user to select whether to install the virtual icon corresponding to the target application, so that when the target application needs to be opened next time, the virtual icon may be directly clicked according to the related technology to open the target application.
The embodiment of the disclosure provides a message pushing method for pushing a notification bar message to a target application, which can be used for a server side. Referring to fig. 3, a flow chart of a message pushing method according to an exemplary embodiment may include the following steps:
in step 101, when it is determined that cache information corresponding to a target application on a client is cleared and a notification bar message corresponding to the target application is sent to the client, re-registering a message push function for a preset platform on the client;
in step 102, pushing the notification bar message to the client based on the re-registered message pushing function;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
In the above embodiment, the target application, that is, the installation and download process, does not need user confirmation, the installation and download process is an application running in the client background, and the preset platform is a platform on the client background for running the target application, for example, a direct service platform. Even if the cache information corresponding to the target application on the client is cleared, the server can still re-register the message pushing function for the preset platform on the client when sending the notification bar message corresponding to the target application, so as to push the notification bar message based on the re-registered message pushing function. Through the process, the aim that the server side can still push the notification bar message to the client side even if the cache information corresponding to the target application on the client side is removed is achieved, and user experience is improved.
For step 101, before sending a notification bar message corresponding to a target application to a client, a server may detect whether a message push channel between the server and a preset platform of the client currently exists.
If the message pushing channel between the server side and the preset platform exists, the notification bar message can be pushed directly through the message pushing channel. If the message pushing channel between the server and the preset platform does not exist, the client deletes the cache information corresponding to the target application, and at this time, the server can re-register the message pushing function for the preset platform on the client.
The cache information at least includes registration information used by the client to register the target application, such as an account and a password corresponding to the target application. Optionally, the cache information may further include a history access record, an input record, a cache file, and the like.
In the embodiment of the present disclosure, the target application is run on a preset platform, and optionally, the preset platform may be a direct service platform. When the server re-registers the message pushing function for the preset platform, the server can re-register the message pushing function for the preset platform through the target channel based on the registration information corresponding to the client recorded in the target application stored by the server. The target channel is a transmission channel which is pre-established between the server side and the preset platform.
That is, the server records the registration information corresponding to different clients in each target application, and if the cache information corresponding to the target application on the client is removed, the server can still re-register the message pushing function for the preset platform on the client according to the stored registration information and the related technology through the transmission channel pre-established between the server and the preset platform.
Further, the server may reestablish a message push channel for a preset platform on the client through a target channel, where the message push channel may be used to push a notification bar message and the like.
With respect to step 102, the server may push the notification bar message to the client based on the reestablished message push channel.
In the above embodiment, even if the cache information corresponding to the target application on the client is removed, the server may still reactivate the message push function of the preset platform through a transmission channel, i.e., a target channel, pre-established with the preset platform on the client, so as to re-establish the message push channel for the preset platform. Therefore, the notification bar message corresponding to the target application can be pushed through the reestablished message pushing channel. The method and the device achieve the purpose that the server can still push the notification bar message to the client even if the cache information corresponding to the target application on the client is removed, and improve user experience.
In an embodiment, referring to fig. 4, fig. 4 is another message pushing method shown on the basis of the embodiment shown in fig. 3, and the method may further include:
in step 100, an acknowledgement message sent by the client is received.
In this step, the confirmation message is a message used to confirm that the client has registered the message push service corresponding to the target application, and the client stores the icon corresponding to the target application.
After receiving the confirmation message, the server side can confirm that the user reserves the target application on the client side and has registered the message push service corresponding to the target application, namely that the user wishes to receive the notification bar message corresponding to the target application. At this time, the server may continue to execute step 101, and when it is determined that the cache information corresponding to the target application on the client is cleared and a notification bar message corresponding to the target application is sent to the client, re-register the message pushing function for a preset platform on the client and store the icon corresponding to the target application on the client.
The embodiment of the disclosure also provides a message pushing method for pushing a notification bar message to the target application, which can be used for a client. Referring to fig. 5, a flow chart of a message pushing method according to an exemplary embodiment may include the following steps:
in step 201, after the cache information corresponding to the target application is cleared, receiving a notification bar message, which is pushed by a server based on a message pushing function registered again for a preset platform and corresponds to the target application;
in step 202, displaying the notification bar message;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
In the above embodiment, after determining that the cache information corresponding to the target application is cleared, the client may receive a notification bar message corresponding to the target application, which is pushed by the server based on the message pushing function re-registered for the preset platform, so as to display the notification bar message. The preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process. Through the process, even if the cache information corresponding to the target application on the client is removed, the notification bar message which is pushed by the server and corresponds to the target application can be received, so that the notification bar message is displayed, the phenomenon that a user misses an important message after the cache information is removed is avoided, and the user experience is improved.
For the above step 201, the target application is an application whose installation and download process does not need user confirmation, and the installation and download process is running in the background of the client. The target application is running on a preset platform on the client.
The client side can receive the notification bar message which is pushed by the server side based on the message pushing function registered again for the preset platform and corresponds to the target application after the cache information corresponding to the target application is cleared.
The server side can establish a message pushing channel between the server side and the preset platform based on a transmission channel which is established in advance between the server side and the preset platform, namely, a target channel is the function of re-registering the preset platform to push messages. And therefore, the notification bar message is pushed to the client through the newly registered message pushing channel, and the client receives the notification bar message according to the related technology.
With respect to step 202, after receiving the notification bar message corresponding to the target application, the client may display the notification bar message according to a related art, for example, as shown in fig. 6.
In the embodiment, even if the cache information corresponding to the target application on the client is removed, the notification bar message corresponding to the target application pushed by the server can be received, so that the notification bar message is displayed, the situation that the user misses an important message after the cache information is removed is avoided, the delivery capability of the notification bar message corresponding to the target application is improved, and the user experience is improved.
In an embodiment, referring to fig. 7, fig. 7 is another message pushing method shown on the basis of the embodiment shown in fig. 5, before performing step 201, the method may further include:
in step 301, sending an acknowledgement message to the server;
the confirmation message is used for confirming that the client side has registered the message push service corresponding to the target application, and the client side stores the icon corresponding to the target application.
In this step, the client may send the confirmation message to the server when confirming that the message push service corresponding to the target application is registered and the icon corresponding to the target application is stored, and optionally, the confirmation message may be sent to the server through the target channel, so that the server determines that the user wishes to receive the notification bar message corresponding to the target application, and thus, the notification bar message is pushed to the client in time, the user is prevented from missing important messages, and user experience is improved.
In an embodiment, referring to fig. 8, fig. 8 is another message pushing method shown on the basis of the embodiment shown in fig. 5, before performing step 201, the method may further include:
in step 401, acquiring registration information corresponding to the target application on the client;
in this step, the client may automatically acquire a registration message, such as an account and a password, corresponding to the target application when it is confirmed that the message push service corresponding to the target application is registered and the icon corresponding to the target application is stored in the client.
In step 402, the registration information corresponding to the client is sent to a server, and the server stores the registration information corresponding to the client in the target application.
In this step, the client may send the registration message to the server, and the server stores the registration information corresponding to the client in the target application. Therefore, even if the cache information corresponding to the target application on the subsequent client is removed, the server still retains the registration information corresponding to the target application on the client, so that the notification bar message corresponding to the target application can be pushed to the client, the delivery capability of the notification bar message corresponding to the target application is improved, and the user experience is good.
In an embodiment, referring to fig. 9, fig. 9 is another message pushing method according to an embodiment, where the method may include:
in step 501, the client sends an acknowledgement message to the server.
The confirmation message is used for confirming that the client side has registered the message push service corresponding to the target application, and the client side stores the icon corresponding to the target application.
In step 502, the server determines that the cache information corresponding to the target application on the client is cleared, and re-registers the message push channel for the preset platform on the client through the target channel according to the registration information corresponding to the client pre-stored in the target application when sending the notification bar message corresponding to the target application to the client.
The target channel is a transmission channel which is pre-established between the server side and the preset platform.
In step 503, the server pushes the notification bar message to the client based on the reestablished message push channel.
In step 504, the client displays the notification bar message.
In the above embodiment, even if the cache information corresponding to the target application on the client is cleared, the server may still re-register the message push function for the preset platform through the target channel when the user wishes to obtain the notification bar message, so as to push the notification bar message based on the re-registered message push function. Through the process, the aim that the server side can still push the notification bar message to the client side even if the cache information corresponding to the target application on the client side is removed is achieved, the delivery capacity of the notification bar message corresponding to the target application is improved, and the user experience is improved.
While, for purposes of simplicity of explanation, the foregoing method embodiments have been described as a series of acts or combination of acts, it will be appreciated by those skilled in the art that the present disclosure is not limited by the order of acts, as some steps may, in accordance with the present disclosure, occur in other orders and concurrently.
Further, those skilled in the art should also appreciate that the embodiments described in the specification are exemplary embodiments and that acts and modules referred to are not necessarily required by the disclosure.
Corresponding to the embodiment of the application function implementation method, the disclosure also provides an embodiment of an application function implementation device and a corresponding terminal.
Referring to fig. 10, a block diagram of a message pushing apparatus according to an exemplary embodiment is shown, where the apparatus is used on a server side, and includes:
the registration module 610 is configured to re-register a message pushing function for a preset platform on a client when it is determined that cache information corresponding to a target application on the client is cleared and a notification bar message corresponding to the target application is sent to the client;
a push module 620 configured to push the notification bar message to the client based on the message push function re-registered by the registration module 610;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
Referring to fig. 11, a block diagram of another message pushing apparatus according to an exemplary embodiment is shown, and on the basis of the apparatus embodiment shown in fig. 10, the registration module 610 includes:
the registration submodule 611 is configured to re-register a message pushing function for a preset platform on the client through a target channel according to registration information corresponding to the client pre-stored in the target application;
the target channel is a transmission channel which is pre-established between the server side and the preset platform.
Optionally, the registration sub-module 611 is further configured to reestablish a message push channel for a preset platform on the client;
referring to fig. 12, a block diagram of another message pushing apparatus according to an exemplary embodiment is shown, and on the basis of the apparatus embodiment shown in fig. 11, the pushing module 620 includes:
a pushing sub-module 621 configured to push the notification bar message to the client based on the message pushing channel re-established by the registration sub-module 611.
Referring to fig. 13, a block diagram of another message pushing apparatus according to an exemplary embodiment is shown, and on the basis of the embodiment of the apparatus shown in fig. 10, the apparatus further includes:
a control module 630, configured to control the registration module 610 to re-register the message pushing function for a preset platform on the client after determining that the acknowledgement message sent by the client is received;
the confirmation message is used for confirming that the client side has registered the message push service corresponding to the target application, and the client side stores the icon corresponding to the target application.
Referring to fig. 14, a block diagram of a message pushing apparatus for a client is shown according to an exemplary embodiment, including:
the receiving module 710 is configured to receive a notification bar message, which is pushed by a server side based on a message pushing function registered again for a preset platform and corresponds to a target application, after cache information corresponding to the target application is cleared;
a display module 720 configured to display the notification bar message received by the receiving module 710;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
Referring to fig. 15, a block diagram of another message pushing apparatus according to an exemplary embodiment is shown, and on the basis of the embodiment of the apparatus shown in fig. 14, the apparatus further includes:
a first sending module 730, configured to send an acknowledgement message to the server side;
the confirmation message is used for confirming that the client side has registered the message push service corresponding to the target application, and the client side stores the icon corresponding to the target application.
Referring to fig. 16, a block diagram of another message pushing apparatus according to an exemplary embodiment is shown, and on the basis of the embodiment of the apparatus shown in fig. 14, the apparatus further includes:
an obtaining module 740 configured to obtain registration information corresponding to the target application on the client;
a second sending module 750, configured to send the registration information obtained by the obtaining module 740 to a server, where the server stores the registration information corresponding to the client in the target application.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the disclosed solution. One of ordinary skill in the art can understand and implement it without inventive effort.
Correspondingly, the embodiment of the present disclosure further provides a computer-readable storage medium, where the storage medium stores a computer program, and the computer program is used to execute the message pushing method for the server side.
Correspondingly, the embodiment of the present disclosure further provides a computer-readable storage medium, where the storage medium stores a computer program, and the computer program is used to execute the above message pushing method for the client.
Correspondingly, an embodiment of the present disclosure further provides a message pushing apparatus, where the apparatus is used at a server side, and includes:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
when the cache information corresponding to the target application on the client is determined to be cleared and the notification bar message corresponding to the target application is sent to the client, re-registering a message pushing function for a preset platform on the client;
pushing the notification bar message to the client based on the re-registered message pushing function;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
As shown in fig. 17, fig. 17 is a schematic structural diagram of a message pushing apparatus 1700 according to an exemplary embodiment. For example, the apparatus 1700 may be provided as a server side. Referring to fig. 17, apparatus 1700 includes a processing component 1722 that further includes one or more processors and memory resources, represented by memory 1732, for storing instructions, such as applications, that may be executed by processing component 1722. The application programs stored in memory 1732 may include one or more modules that each correspond to a set of instructions. Further, the processing component 1722 is configured to execute instructions to perform the message push method described above.
The apparatus 1700 may also include a power component 1726 configured to perform power management of the apparatus 1700, a wired or wireless network interface 1750 configured to connect the apparatus 1700 to a network, and an input output (I/O) interface 1758. The apparatus 1700 may operate based on an operating system stored in the memory 1732, such as Android, IOS, Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.
Wherein the instructions in the memory 1732, when executed by the processing component 1722, enable the apparatus 1700 to perform the message push method for server side described above.
Correspondingly, an embodiment of the present disclosure further provides a message pushing apparatus, where the apparatus is used for a client, and includes:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
after the cache information corresponding to the target application is cleared, receiving a notification bar message which is pushed by a server side based on a message pushing function registered again for a preset platform and corresponds to the target application;
displaying the notification bar message;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
Fig. 18 is a schematic structural diagram illustrating a message pushing apparatus according to an exemplary embodiment. As shown in fig. 18, a message pushing apparatus 1800 is shown according to an exemplary embodiment, and the apparatus 1800 may be a computer, a mobile phone, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, or the like.
Referring to fig. 18, the apparatus 1800 may include one or more of the following components: processing components 1801, memory 1802, power components 1803, multimedia components 1804, audio components 1805, input/output (I/O) interfaces 1806, sensor components 1807, and communication components 1808.
The processing component 1801 generally controls overall operation of the device 1800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing components 1801 may include one or more processors 1809 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 1801 can include one or more modules that facilitate interaction between the processing component 1801 and other components. For example, the processing component 1801 may include a multimedia module to facilitate interaction between the multimedia component 1804 and the processing component 1801.
The memory 1802 is configured to store various types of data to support operation of the apparatus 1800. Examples of such data include instructions for any application or method operating on the device 1800, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 1802 may be implemented with any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
The power supply component 1803 provides power to the various components of the device 1800. The power components 1803 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 1800.
The multimedia component 1804 includes a screen that provides an output interface between the device 1800 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 1804 includes a front-facing camera and/or a rear-facing camera. The front-facing camera and/or the rear-facing camera may receive external multimedia data when the device 1800 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 1805 is configured to output and/or input an audio signal. For example, the audio component 1805 includes a Microphone (MIC) configured to receive external audio signals when the apparatus 1800 is in operating modes, such as a call mode, recording mode, and voice recognition mode. The received audio signals may further be stored in memory 1802 or transmitted via communications component 1808. In some embodiments, audio component 1805 also includes a speaker for outputting audio signals.
I/O interface 1806 provides an interface between processing component 1801 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
The sensor component 1807 includes one or more sensors for providing various aspects of state assessment for the apparatus 1800. For example, the sensor component 1807 may detect an open/closed state of the apparatus 1800, the relative positioning of components, such as a display and keypad of the apparatus 1800, the sensor component 1807 may also detect a change in position of the apparatus 1800 or a component of the apparatus 1800, the presence or absence of user contact with the apparatus 1800, orientation or acceleration/deceleration of the apparatus 1800, and a change in temperature of the apparatus 1800. The sensor component 1807 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 1807 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor component 1807 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 1808 is configured to facilitate wired or wireless communication between the apparatus 1800 and other devices. The device 1800 may access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 1808 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 1808 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the apparatus 1800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described methods.
In an exemplary embodiment, a non-transitory computer readable storage medium comprising instructions, such as the memory 1802 comprising instructions, executable by the processor 1809 of the apparatus 1800 to perform the above-described method is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
Wherein the instructions in the storage medium, when executed by the processor, enable the apparatus 1800 to perform the message push method described above.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
The above description is only exemplary of the present disclosure and should not be taken as limiting the disclosure, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.
Claims (18)
1. A message pushing method is used for a server side, and comprises the following steps:
when the cache information corresponding to the target application on the client is determined to be cleared and the notification bar message corresponding to the target application is sent to the client, re-registering a message pushing function for a preset platform on the client;
pushing the notification bar message to the client based on the re-registered message pushing function;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
2. The method of claim 1, wherein re-registering the message push function for a pre-defined platform on the client comprises:
re-registering a message pushing function for a preset platform on the client through a target channel according to registration information corresponding to the client pre-stored in the target application;
the target channel is a transmission channel which is pre-established between the server side and the preset platform.
3. The method of claim 2, wherein re-registering the message push function for the predetermined platform on the client comprises:
reestablishing a message pushing channel for a preset platform on the client;
the pushing the notification bar message to the client based on the re-registered message pushing function includes:
and pushing the notification bar message to the client based on the reestablished message pushing channel.
4. The method of claim 1, further comprising:
after receiving a confirmation message sent by the client, executing the step of re-registering the message pushing function for the preset platform on the client;
the confirmation message is used for confirming that the client side has registered the message push service corresponding to the target application, and the client side stores the icon corresponding to the target application.
5. A message pushing method, which is used for a client, and comprises the following steps:
after the cache information corresponding to the target application is cleared, receiving a notification bar message which is pushed by a server side based on a message pushing function registered again for a preset platform and corresponds to the target application;
displaying the notification bar message;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
6. The method according to claim 5, wherein before receiving the notification bar message corresponding to the target application pushed by the server based on the message pushing function re-registered for the preset platform, the method further comprises:
sending a confirmation message to the server;
the confirmation message is used for confirming that the client side has registered the message push service corresponding to the target application, and the client side stores the icon corresponding to the target application.
7. The method according to claim 5, wherein before receiving the notification bar message corresponding to the target application pushed by the server side based on the message pushing function re-registered for the preset platform, the method further comprises:
acquiring registration information corresponding to the target application on the client;
and sending the registration information corresponding to the client to a server, and storing the registration information corresponding to the client in the target application by the server.
8. A message pushing apparatus, wherein the apparatus is used on a server side, the apparatus comprising:
the registration module is configured to re-register a message pushing function for a preset platform on a client when cache information corresponding to a target application on the client is determined to be cleared and a notification bar message corresponding to the target application is sent to the client;
a push module configured to push the notification bar message to the client based on the message push function re-registered by the registration module;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
9. The apparatus of claim 8, wherein the registration module comprises:
the registration submodule is configured to re-register a message pushing function for a preset platform on the client through a target channel according to registration information corresponding to the client and pre-stored in the target application;
the target channel is a transmission channel which is pre-established between the server side and the preset platform.
10. The apparatus of claim 9, wherein the registration sub-module is further configured to reestablish a message push channel for a predetermined platform on the client;
the push module comprises:
a push submodule configured to push the notification bar message to the client based on the message push channel re-established by the registration submodule.
11. The apparatus of claim 8, further comprising:
the control module is configured to control the registration module to re-register a message pushing function for a preset platform on the client after determining that the confirmation message sent by the client is received;
the confirmation message is used for confirming that the client side has registered the message push service corresponding to the target application, and the client side stores the icon corresponding to the target application.
12. A message pushing apparatus, wherein the apparatus is used for a client, the apparatus comprising:
the receiving module is configured to receive a notification bar message which is pushed by a server side based on a message pushing function registered again for a preset platform and corresponds to the target application after cache information corresponding to the target application is cleared;
a display module configured to display the notification bar message received by the receiving module;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
13. The apparatus of claim 12, further comprising:
the first sending module is configured to send a confirmation message to the server side;
the confirmation message is used for confirming that the client side has registered the message push service corresponding to the target application, and the client side stores the icon corresponding to the target application.
14. The apparatus of claim 12, further comprising:
the acquisition module is configured to acquire the registration information corresponding to the target application on the client;
a second sending module, configured to send the registration information obtained by the obtaining module to a server, where the server stores the registration information corresponding to the client in the target application.
15. A computer-readable storage medium, characterized in that the storage medium stores a computer program for executing the message pushing method according to any one of the preceding claims 1 to 4.
16. A computer-readable storage medium, characterized in that the storage medium stores a computer program for executing the message pushing method according to any one of the preceding claims 5 to 7.
17. A message pushing apparatus, wherein the apparatus is used for a server side, and comprises:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
when the cache information corresponding to the target application on the client is determined to be cleared and the notification bar message corresponding to the target application is sent to the client, re-registering a message pushing function for a preset platform on the client;
pushing the notification bar message to the client based on the re-registered message pushing function;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
18. A message pushing apparatus, wherein the apparatus is used for a client, and comprises:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
after the cache information corresponding to the target application is cleared, receiving a notification bar message which is pushed by a server side based on a message pushing function registered again for a preset platform and corresponds to the target application;
displaying the notification bar message;
the preset platform is used for running the target application on the client background, the target application is an application which does not need user confirmation in the installation and downloading process and runs on the client background in the installation and downloading process.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711441528.2A CN107864229B (en) | 2017-12-27 | 2017-12-27 | Message pushing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711441528.2A CN107864229B (en) | 2017-12-27 | 2017-12-27 | Message pushing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107864229A CN107864229A (en) | 2018-03-30 |
| CN107864229B true CN107864229B (en) | 2020-10-09 |
Family
ID=61707425
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711441528.2A Active CN107864229B (en) | 2017-12-27 | 2017-12-27 | Message pushing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107864229B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102724324A (en) * | 2012-06-28 | 2012-10-10 | 用友软件股份有限公司 | Information pushing and integrating device and information pushing and integrating method |
| CN105871981A (en) * | 2015-11-30 | 2016-08-17 | 乐视致新电子科技（天津）有限公司 | Pushing service implementation method, pushing service implementation device, terminal equipment and system |
| CN105979076A (en) * | 2016-04-27 | 2016-09-28 | 乐视控股（北京）有限公司 | Pushing information processing method used for mobile phone and device thereof, and the mobile phone |
| CN107408050A (en) * | 2015-04-14 | 2017-11-28 | 索尼公司 | Message processing device, information processing method, computer program and server apparatus |
-
2017
- 2017-12-27 CN CN201711441528.2A patent/CN107864229B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102724324A (en) * | 2012-06-28 | 2012-10-10 | 用友软件股份有限公司 | Information pushing and integrating device and information pushing and integrating method |
| CN107408050A (en) * | 2015-04-14 | 2017-11-28 | 索尼公司 | Message processing device, information processing method, computer program and server apparatus |
| CN105871981A (en) * | 2015-11-30 | 2016-08-17 | 乐视致新电子科技（天津）有限公司 | Pushing service implementation method, pushing service implementation device, terminal equipment and system |
| CN105979076A (en) * | 2016-04-27 | 2016-09-28 | 乐视控股（北京）有限公司 | Pushing information processing method used for mobile phone and device thereof, and the mobile phone |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107864229A (en) | 2018-03-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3174053A1 (en) | Method, apparatus and system for playing multimedia data, computer program and recording medium | |
| US9667774B2 (en) | Methods and devices for sending virtual information card | |
| CN108123855B (en) | Terminal control method and device | |
| CN109274510B (en) | Message processing method, device, client, server and storage medium | |
| US20160255521A1 (en) | Method and apparatus for testing a smart device | |
| CN109451877B (en) | Unmanned aerial vehicle control method and device, unmanned aerial vehicle and remote control equipment | |
| CN109388625B (en) | Method and device for processing configuration file in multi-distributed file system | |
| CN107220059B (en) | Application interface display method and device | |
| CN109814942B (en) | Parameter processing method and device | |
| CN109302341B (en) | Instant messaging method, instant messaging device, electronic equipment and storage medium | |
| US20180007420A1 (en) | Method, device and system for recording television program | |
| CN110704054A (en) | Method and device for accessing target application program through applet, electronic equipment and storage medium | |
| CN108011990B (en) | Contact management method and device | |
| CN107395624B (en) | Information processing method and device | |
| CN106878654B (en) | Video communication method and device | |
| CN105227426B (en) | Application interface switching method and device and terminal equipment | |
| CN106412855B (en) | Information reminding and transmitting method and device | |
| CN110690979B (en) | Group message processing method, device, server, client and storage medium | |
| CN110121148B (en) | Interphone team method and device | |
| CN108984098B (en) | Information display control method and device based on social software | |
| CN110764847A (en) | User information processing method and device, electronic equipment and storage medium | |
| CN107885464B (en) | Data storage method, device and computer readable storage medium | |
| CN107241439B (en) | Message pushing method and device for H5 page | |
| CN106658412B (en) | Positioning method and device | |
| CN107193446B (en) | Image processing method, device, terminal and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Qi Jianbin Inventor after: Qin Bi Inventor after: Shu Xiaohui Inventor before: Qi Jianbin Inventor before: Qin Bi Inventor before: Shu Xiaohui |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |