CN114205413B - Message pushing method, electronic device, apparatus and program product - Google Patents

Message pushing method, electronic device, apparatus and program product Download PDF

Info

Publication number
CN114205413B
CN114205413B CN202111551714.8A CN202111551714A CN114205413B CN 114205413 B CN114205413 B CN 114205413B CN 202111551714 A CN202111551714 A CN 202111551714A CN 114205413 B CN114205413 B CN 114205413B
Authority
CN
China
Prior art keywords
message
pushing
type
application
information
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
Application number
CN202111551714.8A
Other languages
Chinese (zh)
Other versions
CN114205413A (en
Inventor
谢彦彬
李小锋
吴方正
黄文宝
刘波
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Construction Bank Corp
Original Assignee
China Construction Bank Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by China Construction Bank Corp filed Critical China Construction Bank Corp
Priority to CN202111551714.8A priority Critical patent/CN114205413B/en
Publication of CN114205413A publication Critical patent/CN114205413A/en
Application granted granted Critical
Publication of CN114205413B publication Critical patent/CN114205413B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Landscapes

  • Information Transfer Between Computers (AREA)

Abstract

The present disclosure relates to the field of data processing, and in particular, to a message pushing method, an electronic device, an apparatus, and a program product. In the message pushing method, when different messages are pushed to the same pushing object, message pushing can be performed according to different pushing modes of the pushing object on different messages; when the same message is pushed to different push objects, the message pushing can be performed according to different push modes of the message about the different push objects. By the method, different traders can set different message pushing modes for the same business message according to the requirements, and the same trader can set different message pushing modes for different business messages subscribed by the same trader according to the requirements, so that individuation of the message pushing modes is realized, and different requirements of different traders are met.

Description

Message pushing method, electronic device, apparatus and program product
Technical Field
The present invention relates to the field of data processing, and in particular, to a message pushing method, an electronic device, an apparatus, and a program product.
Background
Most of the message notification modes at present adopt a subscription-broadcasting mode, namely, the message is pushed in the same message pushing mode under the same service scene. The message pushing mode has no personalized characteristic and can not meet different requirements of different users. For example, for a trader in a financial market, suppose that trader 1 needs to pay attention to a first business message and trader 2 needs to pay attention to a second business message, the current message pushing method is to push the first business message and the second business message to trader 1 in the same pushing method, and push the first business message and the second business message to trader 2. In the message pushing mode, a specific certain trader cannot distinguish whether the business message subscribed by the specific trader is urgent or not, and different traders cannot set a personalized message pushing mode according to requirements.
Disclosure of Invention
In order to solve the above problems, the present application provides a message pushing method, an electronic device, an apparatus, and a program product. By the message pushing method, different pushing modes can be set for different subscribed messages by different users according to own requirements, and individuation of the message pushing modes is further achieved. The following is a description of a message pushing method of the present application.
In a first aspect, an embodiment of the present application provides a message pushing method, where the method includes: acquiring a first type of information to be pushed; acquiring a first message pushing mode preset by a first pushing object of a first type of message, and pushing the first type of message to the first pushing object in the first message pushing mode; acquiring a second message pushing mode preset by a second pushing object of the first type of message, and pushing the first type of message to the second pushing object in the second message pushing mode; the first message pushing mode and the second message pushing mode are the same or different. By the method, different push objects can set different message push modes for the same type of messages.
With reference to the first aspect, in a possible implementation manner of the first aspect, the method further includes: obtaining a second type of information to be pushed, wherein the second type of information and the first type of information belong to the same application program; acquiring a third message pushing mode of a second type message preset by the first pushing object, and pushing the second type message to the first pushing object in the third message pushing mode; the first message pushing mode and the third message pushing mode are different.
The second type of information and the first type of information belong to the same application program, and refer to the second type of information and the first type of information which are subscribed by the first pushing object through the same application program. By the method, the same push object can set different push modes according to the degree of urgency, importance and the like of different messages subscribed by the same application, so that the push object can know the importance of a certain type of message according to the message push mode, and the message is processed by adopting a corresponding processing mode.
According to the method, the same push object can set different push modes for different messages subscribed by the same application according to the requirements, and different push modes can be set for the same message according to the requirements, so that personalized setting of message push is realized, and user experience is improved.
In some embodiments, the first message pushing manner includes at least one of the following: pushing the first type of information to the pushing object in a preset time period; or pushing the first type of information to the pushing object by using a preset prompting sound; or pushing the first type of information to the pushing object in a preset display mode.
It can be understood that the specific types of the second message pushing manner and the third message pushing manner may be the same as the first message pushing manner, but the setting manner of the specific content, for example, the preset alert tone, the preset display manner, the preset time period, etc., may be set by the user according to specific requirements, which is not limited in this application.
In some embodiments, the first push object and the second push object may subscribe to and set a push manner of the first type of message through a terminal device having a display function, such as a computer, and it should be understood that the method for subscribing to and setting a push manner of the first type of message by the first push object and the second push object is not limited in this application.
With reference to the first aspect and the possible implementation manner of the first aspect, in another possible implementation manner of the first aspect, the first pushing object subscribes to the first type of message through the first application, and before pushing the first type of message to the first pushing object in the first message pushing manner, the method further includes: under the condition that the first push object logs in the first application and receives the monitoring message sent by the first application, the first type of message is pushed to the first push object in a first message pushing mode. It can be understood that, when the first push object subscribes to the first type of message through the first application, in order to save processing resources of the server, the first push object will push the first type of message in the first type of message pushing manner to the first push object when the first push object logs in and does not log out of the first application.
Thus, with reference to the first aspect and the possible implementation manners of the first aspect, in another possible implementation manner of the first aspect, the method further includes: and marking the first message pushing mode of the first type of message as invalid under the condition that the monitoring message sent by the first application is not received after the preset time length.
It can be understood that, due to the situation of a terminal fault or a network fault where the first application is located, the connection between the terminal and the server may be disconnected, so that in order to save the processing resources of the server, the server may not push the first type of message to the first push object, and at the same time, mark the first message pushing manner corresponding to the first type of message as invalid. It will be appreciated that, for other types of messages subscribed by the first push object through the first application, whether the first push object is listening for such messages may also be determined in the same manner as described above, which is not limited in this application.
Specifically, the first application may send a monitoring message to the server at intervals of a plurality of durations, after receiving the monitoring message, the server may determine that the terminal where the first application is located is normally connected with the server, and after the server does not receive the monitoring message for a preset duration, the server may determine that the terminal where the first application is located is abnormally connected with the server, or the first push object is unsubscribed from the first type message, and quit the first application.
The marking of the first message pushing mode as invalid means that the server does not push the first type of message to the first pushing object according to the first message pushing mode any more, but does not influence the server to send the first type of message to other pushing objects according to other message pushing modes.
It will be appreciated that in some embodiments, the first application sending a snoop message to the server may be triggered by the first push object logging into the first application. In other embodiments, the first application sending the listening message to the server may be triggered by clicking on a corresponding function button after the first push object logs into the first application. The present application is not limited in this regard.
It may be appreciated that, in some embodiments, the case that the listening message sent by the first application is not received for the preset period of time includes at least one of the following: detecting that the first pushing object exits from the first application under the condition that the operation of the first pushing object in the first message pushing mode of subscribing the first type of messages is not detected; detecting that the terminal equipment where the first application is located has network faults; and detecting that the terminal equipment where the first application is located has hardware faults.
With reference to the first aspect and the possible implementation manners of the first aspect, in another possible implementation manner of the first aspect, the method further includes: and marking the first message pushing mode of the first type of message as invalid after detecting that the first pushing object unsubscribes from the first message pushing mode of the first type of message. It may be understood that, when the first push object unsubscribes from the first type of message, it indicates that the first push object is no longer focused on the first type of message, and at this time, the server may also mark the first message push manner set by the first push object as invalid. Similarly, the failure of the first message pushing mode does not affect the server to send the first type of message to other pushing objects according to other message pushing modes.
With reference to the first aspect and the possible implementation manners of the first aspect, in another possible implementation manner of the first aspect, the method further includes: the method comprises the steps that a first push object subscribes to a first type of information through a first application, and obtains an identity of a third push object under the condition that the first push object is detected to exit the first application and the third push object is detected to log in the first application; and under the condition that the identity of the third pushing object is matched with the identity of the first pushing object, acquiring and displaying a first message pushing mode of the first type of message.
It can be understood that, because the messages subscribed by the first push object may be all or partially the same when logging in the first application, in order to facilitate the first push object to subscribe to the messages quickly when logging in the first application next time, the server may record the first type of messages subscribed before the first push object and the first message pushing manner of the first type of messages, and then when logging in the first application again, the server displays the first type of messages and the first message pushing manner to the first push object, so that the first push object subscribes to the first type of messages and the first message pushing manner quickly, so that it is unnecessary to set the first message pushing manner for the first type of messages again.
It should be noted that, in the above description, the first type of message subscribed by the first push object is taken as an example, in other possible implementation manners, if the first push object subscribes to other types of messages, then the server records other types of messages subscribed before the first push object and message pushing manners corresponding to the types of messages, and when the first push object logs in the first application again, displays all the messages subscribed by the first push object and the message pushing manners corresponding to the messages when the first push object logs in last time to the first push object, so that the first push object subscribes to a certain type of message to which the first push object wants to subscribe and the message pushing manner corresponding to the type of message quickly.
In a second aspect, an embodiment of the present application provides a message pushing device, where the device includes an obtaining module, configured to obtain a first type of message to be pushed, and obtain a first message pushing manner preset by a first pushing object of the first type of message and a second message pushing manner preset by a second pushing object of the first type of message,
the sending module is used for pushing the first type of information to the first pushing object in a first information pushing mode and pushing the first type of information to the second pushing object in a second information pushing mode, wherein the first information pushing mode and the second information pushing mode are the same or different.
With reference to the second aspect, in a possible implementation manner of the second aspect, the obtaining module is further configured to obtain a second type of message to be pushed, where the second type of message and the first type of message belong to the same application program; and acquiring a third message pushing mode of the second type message preset by the first pushing object, pushing the second type message to the first pushing object by the sending module in the third message pushing mode, and wherein the first message pushing mode and the third message pushing mode are different.
With reference to the second aspect, in a possible implementation manner of the second aspect, a message pushing manner includes at least one of the following: pushing the first type of information to the pushing object in a preset time period; or pushing the first type of information to the pushing object by using a preset prompting sound; or pushing the first type of information to the pushing object in a preset display mode.
With reference to the second aspect and the possible implementation manners of the second aspect, in another possible implementation manner of the second aspect, before the first pushing object subscribes to the first type of message through the first application, before the sending module pushes the first type of message to the first pushing object in the first message pushing manner, the sending module further includes: under the condition that the first push object logs in the first application and receives the monitoring message sent by the first application, the sending module pushes the first type message to the first push object in a first message pushing mode.
With reference to the second aspect and the possible implementation manners of the second aspect, in another possible implementation manner of the second aspect, the apparatus includes a flag modification module, where the flag modification module marks a first message pushing manner of the first type of message as invalid if the monitoring message sent by the first application is not received for a preset period of time.
With reference to the second aspect and the possible implementation manners of the second aspect, in another possible implementation manner of the second aspect, a case that no listening message sent by the first application is received for a preset period of time includes at least one of the following:
detecting that the first pushing object exits from the first application under the condition that the operation of the first pushing object in the first message pushing mode of subscribing the first type of messages is not detected;
detecting that the terminal equipment where the first application is located has network faults;
and detecting that the terminal equipment where the first application is located has hardware faults.
With reference to the second aspect and the possible implementation manners of the second aspect, in another possible implementation manner of the second aspect, after detecting that the first push object unsubscribes from the first message push manner of the first type of message, the flag modifying module is further configured to flag the first message push manner of the first type of message as invalid.
With reference to the second aspect and the possible implementation manner of the second aspect, in another possible implementation manner of the second aspect, the apparatus further includes a display module, where the first push object subscribes to the first type of message through the first application, and where it is detected that the first push object exits the first application, and where it is detected that the third push object logs in to the first application, the obtaining module is configured to obtain an identity of the third push object; and under the condition that the identity of the third pushing object is matched with the identity of the first pushing object, the acquisition module is used for acquiring a first message pushing mode of the first type of message, and the display module displays the first type of message and the pushing mode of the first type of message.
In a third aspect, embodiments of the present application provide an electronic device comprising a memory for storing instructions for execution by one or more processors of the electronic device, an
A processor, which is one of the processors of the electronic device, configured to perform the message pushing method of the first aspect and the various possible implementation manners of the first aspect.
In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, where instructions are stored, where the instructions, when executed on an electronic device, cause the electronic device to perform the message pushing method of the first aspect and the various possible implementation manners of the first aspect.
In a fifth aspect, embodiments of the present application provide a computer program product, which when run on an electronic device, causes the electronic device to perform the message pushing method of the first aspect and the various possible implementations of the first aspect.
It will be appreciated that the advantages of the second to fifth aspects may be found in the relevant description of the first aspect, and are not described here again.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required for the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a diagram of an example of a suitable scenario for the method of the present application provided in some embodiments;
FIG. 2 is a schematic diagram of a message push settings interface provided by some embodiments;
FIG. 3 is an interactive schematic diagram of a message pushing method according to some embodiments;
FIG. 4 is an interactive schematic diagram of a message pushing method according to some embodiments;
FIG. 5 is a flowchart illustrating an example of a message pushing method according to some embodiments;
fig. 6 is a schematic structural diagram of an example of a message pushing device 600 according to some embodiments;
fig. 7 is a schematic structural diagram of an electronic device 700 implementing the present application according to an example provided by some embodiments.
Detailed Description
In order to make the objects and technical solutions of the present application more apparent, the present application will be described in detail below with reference to the accompanying drawings and examples.
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application. It should also be understood that the data acquisition, storage, use, processing, etc. involved in the technical scheme of the present application all conform to relevant regulations of national laws and regulations.
In order to facilitate understanding of the method of the present application, the message pushing method of the present application is described below in conjunction with the financial management scenario shown in fig. 1. However, it should be understood that the applicable scenario of the message pushing method of the present application is not limited thereto, and the message pushing method of the present application may be used to implement individuation of message pushing in any scenario where a message needs to be pushed to a specific user, so as to meet the needs of each user.
As shown in fig. 1 in particular, the scenario includes a trader 10, a terminal device 100, a world wide WEB server 200 (hereinafter referred to simply as WEB server 200), and a data processing server 300. The terminal device 100, the WEB access server 200 and the data processing server 300 are in communication connection through a network to realize data transmission among each other.
As noted above, the data processing server 300 pushes the first service message and the second service message to which the trader 10 subscribes in the same message pushing manner, which is detrimental to the trader 10 in distinguishing the urgency of the service messages.
In order to solve the technical problems, the application provides a message pushing method. In the message pushing method of the present application, when the trader 10 pushes the service message subscribed by the same application, the data processing server 300 pushes different service messages to the trader 10 according to the message pushing mode preset by the trader 10 for different service messages. For example, the trader 10 sets a message pushing manner a for a first service message to which he subscribes, sets a message pushing manner B for a second service message to which he subscribes, and then the data server 300 will push the first service message to the trader 10 in the message pushing manner a and push the second service message to the trader 10 in the message pushing manner B. By the method, each transactor can set different pushing modes for different subscribed services according to the requirements, and individuation of the message pushing modes is realized.
In some embodiments, the message pushing manner is set by the trader according to the requirement, and may be any one or more of pushing a service message to the trader in a preset time period, with a preset prompt tone, and with a preset display manner. For example, the trader 1 may set the message pushing manner of the first service message to: during daytime, 8:00 am to 8:05 am, are displayed as a whistling sound in the lower right corner popup window of the terminal device 100. For another example, the trader 1 may set the message pushing manner of the second service message to: at night 22:00, in the central bullet window display of the screen of the terminal device 100, etc. The specific content of the message pushing mode is not limited in the application. For convenience of explanation, the terminal device 100 is described below as a computer.
It will be appreciated that the data processing server 300 is still pushing its subscribed data to the trader 10 due to network failure or hardware failure of the computer 100, or the trader 10 logging out of account from the financial project management application without unsubscribing, while occupying the processing resources of the data processing server 300. In some embodiments, the message pushing method of the present application may further employ a "heartbeat mechanism" to determine whether the trader 10 is listening to the first service message (and/or the second service message) subscribed by the trader 10, and when the trader 10 is no longer listening to the first service message subscribed by the trader 10, the data processing server 300 may modify the subscription status of the first service message subscribed by the trader 10 to "unsubscribed" and then no longer push the first service message to the trader 10.
Specifically, after receiving heartbeat information sent by a certain trader 10 through the computer 100, the data processing server 300 records time T1 when the heartbeat information is received, then, from the time T1, determines whether the heartbeat information sent by the trader 10 is not received for a long time, if the heartbeat information sent by the trader 10 is not received for a long time, which indicates that the trader 10 does not monitor the subscribed first service messages, in order to save processing resources of the data processing server 300, the data processing server 300 may modify the subscription status of the subscribed first service messages of the trader 10 to be "unsubscribed". The specific details of the heartbeat mechanism will be described in detail below in conjunction with fig. 3.
Further, since the messages subscribed to by the first application of the trader 10 may be all or partially the same each time the trader 10 logs in to the terminal device 100, in the message pushing method of the present application, the data processing server 300 records the message subscribed to by the trader 10 last time and the message configuration information of each message, and then when the trader 10 logs in to the first application again, the data server 300 displays the message subscribed to by the trader 10 last time and the message pushing configuration information of each message, so that the trader 10 can subscribe to batches quickly. This will be described in detail below in connection with the flowchart shown in fig. 5.
With continued reference to fig. 1, a specific process of implementing the method of the present application by the cooperation of the devices of fig. 1 will be described. In some embodiments, it is assumed that the terminal device 100 has a first application such as a client application corresponding to financial project management (hereinafter referred to as a financial project management application) installed thereon, and the terminal device 100 obtains, through an operation interface in the financial project management application, a first message subscribed by the transactor 10 and message pushing configuration information about the first message. By way of example, fig. 2 shows a schematic diagram of a message push settings interface 200, where a trader 10 may configure message push configuration information for a first message via various settings on the message push settings interface 200.
For example, the exchange rate spot transactor 10A pays attention to the position information of the spot transaction, and then the transactor 10A may subscribe to the position information of the spot transaction, and may set the reminding mode of the position information of different spot transactions according to the urgency of the position information of the spot transaction. For example, the trader 10A may turn on both the daytime reminder 201 and the nighttime reminder 206 of the relatively urgent spot trade position information, display the spot trade head information in the center of the screen, and set the sound effect 204 of the prompt sound of the spot trade position information as a clarion. For the position information of the spot transaction that can be held, the trader 10A may turn off the overnight reminder of the position information of the spot transaction, and set the display mode of the daytime reminder of the position information of the spot transaction to the lower right corner popup display, and set the sound effect of the prompt sound of the position information of the spot transaction to the meteor scratch.
Whereas the exchange rate spot trader 10B focuses on the spot trade's position information and the trade limit, the trader 10B may subscribe to the spot trade's position information and trade limit, and the trader 10B may set the spot trade's position information to be a day reminder, the trade limit to be a day reminder and a night reminder, and then set the sound effect of the night reminder 206 of the trade limit to be a meteor pass.
For another example, if the far swap trader 10C pays attention to the swap position and option position, the trader 10B may subscribe to the swap position information and option position information, then turn on the daytime reminder 201 of the swap position, set the display mode of the swap position to be the right lower corner popup window display, and set the sound effect 204 of the prompt sound of the swap position information to be bell sound. For option position information, the trader 10 may turn on the overnight reminder 206, but to avoid disturbing others, the trader 10 may turn off the reminder sound 203 of the option position information, and it will be understood that the sound effect 204 is turned off when the reminder sound is turned off.
In some embodiments, to ensure that the prompt sound can be played normally or the sound effect can be achieved in the actual prompt, the trader 10 may also click the listen test button 205 or the listen test button 207 in fig. 2 to listen to the prompt sound when the message is pushed. The degree of urgency of the spot trade position information can be set by the exchange rate trader 10 according to the requirements, which is not limited in the present application.
It will be appreciated that any trader 10 may set, according to its own requirements, the pushing manner of the one or more first messages subscribed to by the message pushing setting interface 200 shown in fig. 2, which is not limited in this application.
It will be appreciated that the message push interface 200 described above is merely exemplary and does not constitute a limitation on the message push configuration interfaces that may be used in practice. In other embodiments, more interface elements or alert manners may be included in the message pushing interface 200, for example, a duration of an interval between message pushing, a number of repetitions of message pushing, and the like, which is not limited in this application.
It is also understood that the terminal device 100 may be an electronic device having a display function, such as a desktop computer or a notebook computer, which is not limited in this application. The terminal device 100 will be described below as an example of the computer 100.
The WEB server 200 is a server installed on the basis of a WEB site, and is used for responding to a service request of the terminal device 100 and processing the service request. For example, when the trader 10 browses the WEB page through the computer 100 or logs in the financial project management application to receive the transaction information of the financial market, the computer 100 needs to send a networking request to the WEB server 200, and after the WEB server 200 responds to the networking request of the computer 100, the computer 100 can be networked, and then the trader 10 can browse the WEB page through the computer 100 or receive the financial transaction information. In some embodiments of the present application, WEB server 200 also has data forwarding capabilities. For example, the first message of the subscription and the message push information configured by the trader 10 in the financial project management application are received by the WEB server 200 and forwarded to the data processing server 300. In other embodiments of the present application, WEB server 200 also has data storage capabilities. For example, when a plurality of traders 10 send a message push configuration information and a subscribed first message to the data processing server 300 through different computers 100, the data processing server 300 may miss a response due to high concurrency of data, and the WEB server 200 may store the data and then forward the data to the data processing server 300 for processing, so as to avoid the occurrence of the foregoing situation.
The data processing server 300, that is, a background server, is configured to process data forwarded by the WEB server 200. In some embodiments of the present application, the data processing server 300 is further configured to manage and store the first messages subscribed to by different traders 10 and the message push configuration information of each first message. In other embodiments of the present application, the data processing server 300 is configured to associate the message pushing configuration information with a first message, and push the first message to the user according to a message pushing manner included in the message pushing configuration information. In further embodiments of the present application, data processing server 300 may also change the subscription status of a message based on the operations of trader 10 to unsubscribe to the message. In other embodiments of the present application, the data processing server 300 may also store the subscription status of a message of a certain trader 10, and the data processing server 300 may display the last subscribed message of the trader 10 in a list or other form when the next time the trader 10 logs into the financial project management application, so that the trader 10 quickly selects the message of the current secondary subscription. This part will be described in more detail below.
In order to better understand the implementation process of the message pushing method of the present application, the following is a diagram of interactions between the settings in the message pushing method of the present application with reference to fig. 3 to 4. However, it should be understood that the method of the present application may be implemented entirely on an electronic device, such as an electronic device having a visual operation interface and data processing capabilities, and in particular, a notebook computer, a computer, etc. The present application is not limited in this regard.
As shown in fig. 3, the method 300 includes:
301, the computer 100 acquires first messages subscribed by the transactor 10 on the financial project management application and message pushing configuration information corresponding to each first message.
In some implementations of the present application, after the trader 10 logs in to the finance-related management application, the corresponding message subscription interface may subscribe to a plurality of first messages that he wishes to pay attention to, and then configure the push manner corresponding to each message through a message configuration interface 200 similar to that shown in fig. 2. For the configuration of the message pushing manner, reference may be made to the above related description, which is not repeated herein.
302, the computer 100 sends the serial number of the trader 10, the first messages and the push configuration information corresponding to each first message to the WEB server 200.
In some embodiments of the present application, the computer 100 sends the number of the trader 10, the first messages subscribed by the trader 10, and the pushing manner of each first message to the WEB server 200, and forwards the first messages to the data processing server 300 from the WEB server 200, so that the data processing server 300 correlates the data, and can push a specific first message for a specific trader 10 according to the pushing manner configured by the specific trader 10.
In some embodiments, to reduce the processing resources of the data processing server 300, the computer 100 may also associate the trader 10 number, the first messages subscribed to by the trader 10, and the message push message configuration information for each first message before sending to the data processing server 300. The present application is not limited in this regard.
Illustratively, the number of the trader 10, the subscribed first message, and the push configuration information for the first message may be as shown in table 1 below:
TABLE 1
The "HLJQ000109" indicates that the exchange rate is the trade company 109, as can be seen from table 1, the information to be paid attention to by the trade company is the spot trade position information and the trade allowance, the information push configuration information about the spot trade position information is displayed in the central floating window of the screen in daytime (11:00-11:05), and the ship whistle is taken as the prompt sound, and the repetition number is 3. Message pushing configuration information about transaction limits is displayed in a lower right corner popup window of a screen in daytime (11:00-11:05), clarion is used as prompt tone, the repetition number is 3, night reminding (20:00-20:10) is displayed in a lower right corner popup window of a plane, and mute prompt is carried out, and the repetition number is 5.
It will be appreciated that the above table is merely exemplary, and in other embodiments, the trader 10 may set other message pushing manners according to requirements, and the message pushing configuration information in the above table includes, but is not limited to, items such as a reminding time, a reminding sound, a reminding information display manner, and a repetition number, which is not limited in this application.
303, the web server 200 stores the trader number, the first message, and the message pushing configuration information corresponding to each message.
As described above, WEB server 200 has data storage and forwarding functions. In order to avoid the problem that the data processing server 300 fails to respond or is blocked by the network due to the high concurrency of data caused by the configuration information of message pushing set by multiple traders 10 at the same time, in some embodiments, the WEB server 200 may store the data to control the high concurrency of data, so as to avoid the problem.
305, the data processing server 300 marks the subscription status corresponding to the first message as "subscribed" and the number of the associated transactor 10, the first message, and the push configuration mode corresponding to each first message.
In some embodiments, the data processing server 300, upon receiving the number of a certain trader 10, the subscribed first messages, and the message pushing configuration information for each first message, first marks the subscription status of the first messages as "subscribed", and then associates and stores the first messages, the trader 10 number, and the message pushing configuration information for each first message, so as to facilitate subsequent pushing of the message to the trader 10 according to the trader 10 number and the message pushing configuration information. Wherein in some embodiments, the subscription status of the first message may be represented in one or more of data, letters, and strings. For example, the state in which the message is subscribed may be "sub", and the state in which the message is unsubscribed is "un sub".
The present application is not limited thereto
Illustratively, the number of the trader, the first messages subscribed to by the trader, and the message pushing configuration information corresponding to each first message after the association processing performed by the data processing server 300 may be as follows in table 2:
table 2:
where HLJQ000109 represents exchange rate spot trade No. 109 trader, YDQ000249 represents far fade No. 249 trader. As can be seen from table 2 above, the first messages subscribed by the HLJQ000109 trader are "on-demand trade position information" and "trade quota", and the corresponding push message configuration information is message push configuration information a and message push configuration information B, respectively. The first message subscribed by the YDQ000249 trader is "drop position information", "option position information" and "trade quota", and the corresponding push message configuration information is respectively message push configuration information C, message push configuration information D and message push configuration information E.
306, the data processing server 300 sends a message of the message push configuration completed by the trader 10 to the computer 100.
307, the data processing server 300 pushes the first message to the transactor according to the message pushing configuration information of each first message.
In some embodiments, data processing server 300 pushes configuration information to a particular trader in accordance with the trader configured message, pushing a first message to which the trader subscribes.
308, the computer 100 presets a first duration at intervals and sends heartbeat information to the WEB server 200.
It will be appreciated that the purpose of the computer 100 of the trader 10 sending heartbeat information to the WEB server 200 is to cause the data processing server 300 to determine that the trader 10 is listening for the first message to which he is subscribed. In some embodiments of the present application, the preset first duration may be an empirical value or an experimental value, or the preset first duration may also be determined when the trader 10 configures the push configuration information of the first message, for example, the preset first duration may be 1 minute. The value of the preset first duration is not limited.
It will be appreciated that the representation of the heartbeat information may be a time pulse without substantial content, or may include the trader 10 number, the heartbeat information time, etc., and the present application does not limit the representation of the heartbeat information.
309, web server 200 forwards the heartbeat information to data processing server 300.
The data processing server 300 records 310 the time of the received heartbeat information.
In some embodiments of the present application, the time of the heartbeat information recorded by the data processing server 300 may be represented in a time series. Also, it will be appreciated that the data processing server 300 may receive heartbeat information from the computers 100 of the plurality of traders 10.
For example, assuming and presetting the first time period to take 1 minute (60 seconds), the heartbeat information is a time pulse, and the heartbeat information received by the data processing server 300 and the corresponding time may be as shown in the following table 3:
table 3:
heartbeat information time stamp Heartbeat information
HLJQ0001092021090900030 Time pulse 5
HLJQ0001092021090900093 Time pulse 6
HLJQ00010920210909000124 Time pulse 7
HLJQ00010920210909000188 Time pulse 8
…… ……
…… ……
…… ……
YDQ0002492021090900040 Time pulse A
YDQ00024920210909000106 Time pulse B
YDQ00024920210909000170 Time pulse C
…… ……
…… ……
…… ……
Here, "HLJQ0001092021090900030" indicates a time corresponding to the time when the data processing server 300 receives the heartbeat information, "HLJQ000109" indicates a trader 10 number (trade at the exchange rate of No. 109) corresponding to the heartbeat information, "20210909" indicates a date corresponding to the heartbeat information, and "00030" indicates a time corresponding to the heartbeat information.
"YDQ0002492021090900040" indicates the time corresponding to the time when the data processing server 300 received the heartbeat information, "YDQ0002492" indicates the trader 10 number corresponding to the heartbeat information (trade No. 249 for the long-term exchange described above), "20210909" indicates the date corresponding to the heartbeat information, and "00040" indicates the time corresponding to the heartbeat information.
As can be seen from table 3 above, data processing server 300 receives a first time pulse a at YDQ0002492021090900040, a second time pulse B at YDQ00024920210909000106, and a third time pulse C at YDQ 00024920210909000170.
311, the data processing server 300 determines whether the next heartbeat message of the trader 10 is not received beyond the preset second time period from the above time.
It will be appreciated that after the time of recording the above heartbeat information, the data processing server 300 will determine whether the next piece of heartbeat information has not been received for a long time from the time of receiving the heartbeat information, so as to determine whether the trader 10 is still listening to the first message to which he subscribes. The setting manner of the preset second duration is similar to the setting manner of the preset first duration, and will not be repeated here. In some embodiments, the preset second duration may be 2 minutes.
If yes, indicating that the computer 100 has not sent heartbeat information for a long time, then the process proceeds to 312, where the data processing server 300 modifies the subscription status of the first message subscribed by the trader 10 to "unsubscribed". If not, then 310 is entered, where the data processing server 300 records the time of the next piece of heartbeat information.
Specifically, taking the heartbeat information received by the data processing server 300 and the corresponding time as shown in table 3 above as an example, assuming that the preset second duration is 2 minutes (120 seconds), the data processing server 300 receives the first time pulse 5 at the HLJQ0001092021090900030, and then the data processing server 300 receives the second time pulse 6 after (00093-00030) seconds, the duration is 63 seconds and less than the preset second duration, so the data processing server 300 enters 310, i.e. continues to receive and record the time of the second time pulse 6.
When the data processing server 300 receives the fourth heartbeat message, the data processing server 300 does not receive the next time pulse, so the data processing server 300 determines that the trader 10 corresponding to HLJQ000109 is no longer listening to the first message subscribed to by the trader, and proceeds to 312.
It will be appreciated that in some embodiments, the reason why the data processing server 300 does not receive the next heartbeat message of the trader 10 for more than the preset second period may be that the computer 100 operated by the trader 10 is network or computer 100 hardware is faulty, or the trader 10 does not cancel the subscription to the first message but annotates the account number of the financial project management application, etc., which is not limited in this application.
312, the data processing server 300 modifies the subscription status of the first message subscribed to by the trader to "unsubscribed".
The foregoing describes the implementation of the trader 10 subscribing to and configuring the message pushing means. It will be appreciated that, as described above, when the trader 10 does not need to subscribe to the first message or the computer 100 has a hardware failure, a network failure, etc. for saving the processing resource of the data processing server 300, it is temporarily unnecessary to push the first message to the trader 10, the computer 100 may take all these events as an operation of unsubscribing, and then forward the operation to the data processing server 300 via the WEB server 200, and the data processing server 300 modifies the subscription status of the first message to "unsubscribed".
Specifically, as shown in fig. 4, the method 400 includes:
the computer 100 determines 401 whether the first message is unsubscribed.
As described above, in some embodiments, the condition in which the first message is unsubscribed includes a computer 100 network failure, a computer 100 hardware failure, or the trader 10 unsubscribing from the first message, etc.
If yes, go to 402, send the above-mentioned message of unsubscribing to WEB server 200. If not, then 401 is entered, where it is continually detected and determined whether the first message is unsubscribed.
402, the computer 100 sends the above-mentioned unsubscribed message to the WEB server 200.
403, web server 200 stores the unsubscribe message.
Web server 200 forwards the unsubscribe message to data processing server 300 404.
405, the data processing server 300 modifies the subscription status of the first message to "unsubscribed" according to the unsubscribed message.
406, the data processing server 300 sends a message to the computer 100 that the message subscription status modification was successful.
As described above, in order to facilitate batch subscription quickly when the trader 10 logs in to the financial project management application again, the message pushing method of the present application may also display the first message subscribed last time and the message pushing configuration information for each first message for the trader 10 when the trader 10 logs in to the financial project management application next time. This is described below in connection with fig. 5. It will be appreciated that the methods described below may be implemented on the computer 100 or on the data processing server 300, and are not limited in this regard. The present method is implemented on the data processing server 300 as an example.
As shown in fig. 5, the method 500 includes:
501, detecting a trader logging into a financial project management application.
In some embodiments of the present application, data processing server 300 detects that a trader is logged into a financial project management application via computer 100. Specifically, when the trader logs in the financial item management application, the computer 100 transmits the number and the password input by the trader to the data processing server 300 for verification matching, and at this time, the data processing server 300 detects that the trader logs in the financial item management application.
502, determining whether the trader subscribes to the first message and the message pushing configuration information configured with the first message.
In some embodiments, the data processing server 300 may determine, through the number of the trader, whether the trader has subscribed to the first message and the message push configuration information configured with the first message. Specifically, the data processing server 300 may obtain the number of the trader login through 501, and then search the subscribed first message and the message pushing configuration information thereof corresponding to the number in the memory according to the number of the trader. If the data processing server 300 can query the subscribed first messages corresponding to the number and the message pushing configuration information thereof, then the process goes to 504, that is, the subscribed first messages and the message pushing configuration information corresponding to each first message when the transactor logs in last time are obtained. If the query is not found, then 503 is entered, i.e. the transactor is prompted to subscribe to the first message and configure the message push configuration information of the first message.
503 prompting the transactor to subscribe to the first message and configure message pushing configuration information of the first message.
In some embodiments of the present application, the data processing server 300 may display corresponding prompt information through the computer 100 to prompt the transactor to subscribe to the first message and configure the message pushing configuration information of the first message. It will be appreciated that the present application is not limited in the manner in which data processing server 300 prompts a transactor to subscribe to a first message and configure message push configuration information for the first message.
504, obtaining the first messages subscribed by the trader at last login and message pushing configuration information corresponding to each first message.
In some embodiments of the present application, after obtaining the first message subscribed by the transactor at the last login and the message pushing configuration information corresponding to each first message, the data processing server 300 displays the first message and the message pushing configuration information corresponding to each first message on the computer 100, so that the transactor can select whether to continue subscribing to the batch of first messages.
The structure of an apparatus for implementing the above-described methods 300, 400 and 500 is described below in connection with fig. 6. Fig. 6 is an example configuration apparatus 600 provided according to an embodiment of the present application, where the apparatus 600 includes: the device comprises an acquisition module 601, a transmission module 602, a storage module 603 and a display module 604. The acquiring module 601 is configured to acquire the message pushing configuration information input by the transactor 10 through the computer 100. The sending module 602 is configured to push, to the transactor 10, the first messages according to the message pushing configuration mode of each first message according to the first messages subscribed by the transactor 10 and the pushing mode of each first message received by the obtaining module 601.
The sending module 602 is further configured to determine whether the next heartbeat message sent by the same trader 10 is not received for a long time according to the time of the received heartbeat message, and determine whether the trader 10 still monitors the subscribed first messages, so as to determine whether to continue pushing each first message to the trader 10 in the pushing manner of each first message set by the trader 10.
The storage module 603 is configured to store the first messages subscribed by the trader 10 and the message pushing configuration information of each first message, and the received heartbeat information and the time of the heartbeat information.
It will be appreciated that the apparatus 600 may further have a structure, such as the display module 604, for providing a visual man-machine interaction interface for the trader 10, so that the trader 10 can implement subscription to the first message and configuration of the push manner of the first message through the man-machine interaction interface. It should be understood that the present application is not limited in terms of the structure of the apparatus 600.
Referring now to fig. 7, shown is a block diagram of an electronic device 700 in accordance with one embodiment of the present application. The device 700 may include one or more processors 702, system control logic 708 coupled to at least one of the processors 702, system memory 704 coupled to the system control logic 708, non-volatile memory (NVM) 707 coupled to the system control logic 708, and a network interface 710 coupled to the system control logic 708.
The processor 702 may include one or more single-core or multi-core processors. The processor 702 can include any combination of general-purpose and special-purpose processors (e.g., graphics processor, application processor, baseband processor, etc.). In embodiments herein, the processor 702 may be configured to perform one or more embodiments in accordance with various embodiments as shown in fig. 3-4.
In some embodiments, system control logic 708 may include any suitable interface controller to provide any suitable interface to at least one of processors 702 and/or any suitable device or component in communication with system control logic 708. In some embodiments, system control logic 708 may include one or more memory controllers to provide an interface to system memory 704. The system memory 704 may be used for loading and storing data and/or instructions. The memory 704 of the device 700 may include any suitable volatile memory in some embodiments, such as a suitable Dynamic Random Access Memory (DRAM).
NVM/memory 707 may include one or more tangible, non-transitory computer-readable media for storing data and/or instructions. In some embodiments, NVM/memory 707 may include any suitable nonvolatile memory, such as flash memory, and/or any suitable nonvolatile storage device, such as at least one of a HDD (Hard Disk Drive), a CD (Compact Disc) Drive, a DVD (Digital Versatile Disc ) Drive. NVM/memory 707 may include a portion of a storage resource installed on the apparatus of device 700 or it may be accessed by, but is not necessarily part of, the device. For example, NVM/storage 707 may be accessed over a network via network interface 710. In particular, system memory 704 and NVM/storage 707 may each include: a temporary copy and a permanent copy of instruction 720. The instructions 720 may include: instructions that, when executed by at least one of the processors 702, cause the apparatus 700 to implement the methods shown in fig. 3-4. In some embodiments, instructions 720, hardware, firmware, and/or software components thereof may additionally/alternatively be disposed in system control logic 708, network interface 710, and/or processor 702.
Network interface 710 may include a transceiver to provide a radio interface for device 700 to communicate with any other suitable device (e.g., front end module, antenna, etc.) over one or more networks. In some embodiments, the network interface 710 may be integrated with other components of the device 700. For example, the network interface 710 may be integrated with at least one of the processor 702, the system memory 704, the nvm/storage 707, and a firmware device (not shown) having instructions that, when executed by at least one of the processor 702, implement one or more of the various embodiments shown in fig. 3-7. Communication module
The network interface 710 may further include any suitable hardware and/or firmware to provide a multiple-input multiple-output radio interface. For example, network interface 710 may be a network adapter, a wireless network adapter, a telephone modem, and/or a wireless modem.
In one embodiment, at least one of the processors 702 may be packaged together with logic for one or more controllers of the system control logic 708 to form a System In Package (SiP). In one embodiment, at least one of the processors 702 may be integrated on the same die with logic for one or more controllers of the system control logic 708 to form a system on a chip (SoC).
The apparatus 700 may further include: input/output (I/O) devices 712. The I/O device 712 may include a user interface to enable a user to interact with the device 700; the design of the peripheral component interface enables the peripheral component to also interact with the device 700. In some embodiments, the device 700 further comprises a sensor for determining at least one of environmental conditions and location information related to the device 700. In some embodiments, the user interface may include, but is not limited to, a display (e.g., a liquid crystal display, a touch screen display, etc.), a speaker, a microphone, one or more cameras (e.g., still image cameras and/or video cameras), a flashlight (e.g., light emitting diode flash), and a keyboard. In some embodiments, the peripheral component interface may include, but is not limited to, a non-volatile memory port, an audio jack, and a power interface. In some embodiments, the sensors may include, but are not limited to, gyroscopic sensors, accelerometers, proximity sensors, ambient light sensors, and positioning units. The positioning unit may also be part of the network interface 710 or interact with the network interface 710 to communicate with components of a positioning network, such as Global Positioning System (GPS) satellites.
It should be understood that the illustrated structure of the embodiment of the present invention does not constitute a specific limitation on the bluetooth communication device 700. In other embodiments of the present application, the Bluetooth communication device 700 may include more or less components than illustrated, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
Program code may be applied to input instructions to perform the functions described herein and generate output information. The output information may be applied to one or more output devices in a known manner. For purposes of this application, a processing system includes any system having a processor such as, for example, a Digital Signal Processor (DSP), microcontroller, application Specific Integrated Circuit (ASIC), or microprocessor.
The program code may be implemented in a high level procedural or object oriented programming language to communicate with a processing system. Program code may also be implemented in assembly or machine language, if desired. Indeed, the mechanisms described herein are not limited in scope to any particular programming language. In either case, the language may be a compiled or interpreted language.
One or more aspects of at least one embodiment may be implemented by representative instructions stored on a computer readable storage medium, which represent various logic in a processor, which when read by a machine, cause the machine to fabricate logic to perform the techniques described herein. These representations, referred to as "IP cores," may be stored on a tangible computer readable storage medium and provided to a plurality of customers or production facilities for loading into the manufacturing machine that actually manufactures the logic or processor.
Embodiments of the present application provide a computer program product which, when run on an electronic device, causes the electronic device to perform steps that may be performed in the various method embodiments described above.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other manners. For example, the apparatus/network device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown 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 units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In the description above, for purposes of explanation and not limitation, specific details are set forth, such as particular system configurations, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".
In addition, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used merely to distinguish between descriptions and are not to be construed as indicating or implying relative importance.
Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.
The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims (8)

1. A message pushing method, the method comprising:
acquiring a first type of information to be pushed;
acquiring a first message pushing mode preset by a first pushing object of the first type of message, and pushing the first type of message to the first pushing object in the first type of message pushing mode;
acquiring a second message pushing mode preset by a second pushing object of the first type of message, and pushing the first type of message to the second pushing object in the second message pushing mode;
wherein, the first message pushing mode and the second message pushing mode are the same or different;
the first pushing object subscribes to the first type of information through a first application, and before the first type of information is pushed to the first pushing object in the first information pushing mode, the method further comprises the steps of: under the condition that the first pushing object logs in the first application and receives a monitoring message sent by the first application, pushing the first type of message to the first pushing object in the first message pushing mode; judging whether the next heartbeat information sent by the first pushing object is not received for a long time according to the time of the received heartbeat information, and judging whether the first pushing object still monitors the subscribed first message or not according to the next heartbeat information;
Wherein the method further comprises: marking the first message pushing mode of the first type of message as invalid under the condition that the monitoring message sent by the first application is not received after the preset time length;
the condition that the monitoring message sent by the first application is not received after the preset duration comprises at least one of the following: detecting that the first pushing object exits the first application under the condition that the operation of the first pushing object in the first message pushing mode of subscribing the first type of messages is not detected; detecting that the terminal equipment where the first application is located has network faults; detecting that the terminal equipment where the first application is located has hardware faults;
wherein the method further comprises: the first push object subscribes to the first type of information through a first application, and obtains an identity of a third push object under the condition that the first push object is detected to exit the first application and the third push object is detected to log in the first application; and under the condition that the identity of the third pushing object is matched with the identity of the first pushing object, acquiring and displaying the first message pushing mode of the first type of message.
2. The method as recited in claim 1, further comprising:
obtaining a second type of information to be pushed, wherein the second type of information and the first type of information belong to the same application program;
acquiring a third message pushing mode of a second type message preset by a first pushing object, and pushing the second type message to the first pushing object in the third message pushing mode;
the first message pushing mode and the third message pushing mode are different.
3. The method according to claim 1 or 2, wherein the first message pushing means comprises at least one of the following:
pushing the first type message to a pushing object in a preset time period; or (b)
Pushing the first type of information to the pushing object by a preset prompt tone; or (b)
And pushing the first type of information to the pushing object in a preset display mode.
4. The method according to claim 1, wherein the method further comprises: and marking the first message pushing mode of the first type of message as invalid after detecting that the first pushing object unsubscribes from the first message pushing mode of the first type of message.
5. A message pushing device, the device comprising:
an acquisition module, configured to acquire a first type of message to be pushed, and acquire a first message pushing manner preset by a first pushing object of the first type of message and a second message pushing manner preset by a second pushing object of the first type of message,
the sending module is used for pushing the first type of information to the first pushing object in the first information pushing mode and pushing the first type of information to the second pushing object in the second information pushing mode; the first message pushing mode and the second message pushing mode are the same or different;
the first pushing object subscribes to the first type of information through a first application, and before the first type of information is pushed to the first pushing object in the first information pushing mode, the method further comprises the steps of: under the condition that the first pushing object logs in the first application and receives a monitoring message sent by the first application, pushing the first type of message to the first pushing object in the first message pushing mode; judging whether the next heartbeat information sent by the first pushing object is not received for a long time according to the time of the received heartbeat information, and judging whether the first pushing object still monitors the subscribed first message or not according to the next heartbeat information;
Wherein, still include: marking the first message pushing mode of the first type of message as invalid under the condition that the monitoring message sent by the first application is not received after the preset time length;
the condition that the monitoring message sent by the first application is not received after the preset duration comprises at least one of the following: detecting that the first pushing object exits the first application under the condition that the operation of the first pushing object in the first message pushing mode of subscribing the first type of messages is not detected; detecting that the terminal equipment where the first application is located has network faults; detecting that the terminal equipment where the first application is located has hardware faults;
wherein, still include: the first push object subscribes to the first type of information through a first application, and obtains an identity of a third push object under the condition that the first push object is detected to exit the first application and the third push object is detected to log in the first application; and under the condition that the identity of the third pushing object is matched with the identity of the first pushing object, acquiring and displaying the first message pushing mode of the first type of message.
6. An electronic device, the electronic device comprising:
a memory for storing instructions for execution by one or more processors of the electronic device, an
A processor, being one of the processors of an electronic device, for performing the message pushing method of any of claims 1 to 4.
7. A computer readable medium having instructions stored therein, which when executed on an electronic device cause the electronic device to perform the message pushing method of any of claims 1 to 4.
8. A computer program product, characterized in that the computer program product, when run on an electronic device, causes the electronic device to perform the message pushing method of any of claims 1 to 4.
CN202111551714.8A 2021-12-17 2021-12-17 Message pushing method, electronic device, apparatus and program product Active CN114205413B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111551714.8A CN114205413B (en) 2021-12-17 2021-12-17 Message pushing method, electronic device, apparatus and program product

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111551714.8A CN114205413B (en) 2021-12-17 2021-12-17 Message pushing method, electronic device, apparatus and program product

Publications (2)

Publication Number Publication Date
CN114205413A CN114205413A (en) 2022-03-18
CN114205413B true CN114205413B (en) 2024-04-09

Family

ID=80655092

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111551714.8A Active CN114205413B (en) 2021-12-17 2021-12-17 Message pushing method, electronic device, apparatus and program product

Country Status (1)

Country Link
CN (1) CN114205413B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101667976A (en) * 2008-09-04 2010-03-10 中国移动通信集团公司 Method for determining mail push mode, pushing method, pushing device and pushing system
CN102480674A (en) * 2010-11-26 2012-05-30 中国移动通信集团北京有限公司 Data pushing method and state perceiving and pushing module as well as data pushing system
CN102902733A (en) * 2012-09-11 2013-01-30 北京奇艺世纪科技有限公司 Information push method, device and system based on content subscription
EP2706727A1 (en) * 2012-09-11 2014-03-12 BlackBerry Limited Systems, devices and methods for authorizing endpoints of a push pathway
WO2021057224A1 (en) * 2019-09-26 2021-04-01 维沃移动通信有限公司 Message prompting method and terminal device

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8484352B2 (en) * 2009-03-30 2013-07-09 Rave Wireless, Inc. Emergency information services

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101667976A (en) * 2008-09-04 2010-03-10 中国移动通信集团公司 Method for determining mail push mode, pushing method, pushing device and pushing system
CN102480674A (en) * 2010-11-26 2012-05-30 中国移动通信集团北京有限公司 Data pushing method and state perceiving and pushing module as well as data pushing system
CN102902733A (en) * 2012-09-11 2013-01-30 北京奇艺世纪科技有限公司 Information push method, device and system based on content subscription
EP2706727A1 (en) * 2012-09-11 2014-03-12 BlackBerry Limited Systems, devices and methods for authorizing endpoints of a push pathway
WO2021057224A1 (en) * 2019-09-26 2021-04-01 维沃移动通信有限公司 Message prompting method and terminal device

Also Published As

Publication number Publication date
CN114205413A (en) 2022-03-18

Similar Documents

Publication Publication Date Title
US10237386B1 (en) Outputting audio notifications based on determination of device presence in a vehicle
US10673683B2 (en) Data network notification bar processing system
US10110699B2 (en) Method and system to enable mobile users to receive personalized notifications
US10326715B2 (en) System and method for updating information in an instant messaging application
US10284608B2 (en) Method and apparatus for providing state information
CN102710972B (en) User notifies
US8250155B2 (en) System and method for autogenerated email follow-up
CN102299955B (en) Image device and server
US10893135B2 (en) Data processing method and apparatus
US20030055946A1 (en) Network monitoring apparatus, computer-readable medium storing a network monitoring program, and network monitoring method
WO2014176896A1 (en) System and method for updating information in an instant messaging application
CN105141682A (en) Subscription event reminding method and device
CN115037709A (en) Information processing method, device, electronic equipment and storage medium
CN112688860A (en) Message processing method and device, storage medium and electronic equipment
US11252069B2 (en) Activity stream based collaboration
CN114205413B (en) Message pushing method, electronic device, apparatus and program product
WO2019114352A1 (en) Method and device for application notification control, and terminal
CN106357890A (en) Method on management of message on the notice board of the mobile phon
US9736293B2 (en) Terminal and specified content deletion method
US20080285942A1 (en) Home network apparatus
US20080181374A1 (en) Provision of Private Information To Voice Telephone Call Parties
CN107911717A (en) Screen control method, apparatus and system
US10636096B1 (en) Dynamic generation of an electronic identification card for display by an electronic device based on real-time policy information
US20150161551A1 (en) Management of multi-site dashboards
JP7430747B2 (en) Information processing system, method and program

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
GR01 Patent grant
GR01 Patent grant