CN110912807A - Information prompting method and device, electronic equipment and computer readable storage medium - Google Patents
Information prompting method and device, electronic equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN110912807A CN110912807A CN201911158205.1A CN201911158205A CN110912807A CN 110912807 A CN110912807 A CN 110912807A CN 201911158205 A CN201911158205 A CN 201911158205A CN 110912807 A CN110912807 A CN 110912807A
- Authority
- CN
- China
- Prior art keywords
- message
- service
- target
- service party
- party
- 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.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
- H04L51/18—Commands or executable codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/23—Reliability checks, e.g. acknowledgments or fault reporting
Abstract
The embodiment of the invention discloses an information prompting method, an information prompting device, electronic equipment and a computer readable storage medium. An embodiment of the method comprises: receiving a target message sent by a message sending service party through a pre-deployed message management component, wherein the message sending service party is a service module supporting message sending in a target application; determining the service type of the target message; inquiring a message receiving service party for monitoring the message of the service type, wherein the message receiving service party is a message prompt module in the target application; and taking the inquired message receiving service party as a target message receiving service party, and sending the target message to the target message receiving service party through the message management component so that the target message receiving service party prompts the target message. The implementation mode reduces the code coupling degree between the target application modules and reduces the error rate of the message prompt service.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to an information prompting method, an information prompting device, electronic equipment and a computer readable storage medium.
Background
With the development of computer technology, the functions of Applications (APPs) installed in terminal devices are becoming more and more abundant. With the increase of functions and the increase of service modules, the logic of the message prompt service is more and more complex. For example, there are various forms of prompt messages for a certain video-type application, and when a certain form of prompt message (for example, prompt message prompted by a special mark such as red dot as new message) appears or disappears, it may be related to various services (for example, download service, skin service, collection service, game service, etc.).
In the existing method, in the development process, a message reminding logic between each service module and a message reminding module in an application is generally established, so that a message reminding function is realized. However, in this way, the service module and the message prompt module in the application have high code coupling, which results in poor code maintenance and high error rate of the message prompt service.
Disclosure of Invention
The embodiment of the invention provides a message prompting method, a message prompting device, electronic equipment and a computer readable storage medium, which are used for reducing the code coupling degree between target application modules so as to reduce the error rate of a message prompting service. The specific technical scheme is as follows:
in a first aspect of the present invention, an information prompting method is provided, where the method includes: receiving a target message sent by a message sending service party through a pre-deployed message management component, wherein the message sending service party is a service module supporting message sending in a target application; determining the service type of the target message; inquiring a message receiving service party for monitoring the message of the service type, wherein the message receiving service party is a message prompt module in the target application; and taking the inquired message receiving service party as a target message receiving service party, and sending the target message to the target message receiving service party through the message management component so that the target message receiving service party prompts the target message.
In a second aspect of the present invention, there is also provided an information presentation apparatus, including: the first receiving unit is configured to receive a target message sent by a message sending service party through a pre-deployed message management component, wherein the message sending service party is a service module supporting message sending in a target application; a determining unit configured to determine a service type of the target message; the query unit is configured to query a message receiving service party monitoring the message of the service type, wherein the message receiving service party is a message prompt module in the target application; and the sending unit is configured to send the target message to the target message receiving service party through the message management component by taking the inquired message receiving service party as the target message receiving service party so that the target message receiving service party prompts the target message.
In yet another aspect of the present invention, there is also provided a computer-readable storage medium having stored therein instructions, which when run on a computer, cause the computer to execute any one of the above-mentioned information prompting methods.
In yet another aspect of the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform any of the above-mentioned information prompting methods.
According to the information prompting method, the information prompting device, the electronic equipment and the computer readable storage medium, the target message sent by the message sending service party is received through the message management component which is deployed in advance; then determining the service type of the target message; then inquiring a message receiving service party for monitoring the message of the service type; and finally, the inquired message receiving service party is used as a target message receiving service party, and the target message is sent to the target message receiving service party through the message management component, so that the target message receiving service party prompts the target message. Therefore, the message management component is used for receiving and sending the messages between the target application modules, so that the direct calling between the service module and the message prompt module is avoided, the code coupling degree between the target application modules is reduced, the codes are convenient to maintain, and the error rate of the message prompt service is reduced.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 is a flow diagram of one embodiment of a message alert method according to the present application;
FIG. 2 is a flow diagram of yet another embodiment of a message alert method according to the present application;
FIG. 3 is a diagram illustrating an application scenario of a message alert method according to the present application;
FIG. 4 is a schematic diagram illustrating an embodiment of a message prompt apparatus according to the present application;
FIG. 5 is a schematic block diagram of a computer system suitable for use in implementing an electronic device according to embodiments of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Referring to fig. 1, a flow 100 of an embodiment of an information prompting method according to the application is shown. The information prompting method comprises the following steps:
In this embodiment, the main body of the message prompting method may be an electronic device such as a mobile phone and a tablet computer. The execution main body may be installed with a target application. The target Application may be any Application (APP) with a message prompt function, such as a video Application, an instant messaging Application, and the like.
In practice, the target application may contain a variety of business modules. Each service module may be divided according to service type. Taking video applications as an example, the system may generally include a download service module, a skin service module, a collection service module, a game service module, a wallet service module, a hot spot message recommendation service module, an instant messaging service module, and other service modules.
Here, the service module in the target application may send the message under a certain condition, for example, the download service module of the video application sends a download completion message after a certain video is downloaded, the collection service module may send a message indicating that the collection content is updated when a certain collection content is updated, and the instant messaging service module may send the message when a new session is received.
In this embodiment, the target application may be deployed with a message management component. The execution main body can take a service module supporting message sending in the target application as a message sending service party, and receive the target message sent by the message sending service party through the message management component. The message management component may be a framework for managing messages (e.g., receiving messages, sending messages). For example, it may be an event publish subscribe framework. The event publishing and subscribing framework can decouple the publisher and the subscriber of the event, so that the publisher and the subscriber do not directly perform message transmission, thereby reducing the coupling degree of codes between the publisher and the subscriber.
It should be noted that the target message may be a message to be forwarded to the message receiving service party. The message receiving service party may be a message prompt module (such as Activity, fragment, and any java class) in the target application. The message prompting module can process the message prompting service based on the message sent by the service module, thereby realizing the prompting of the message.
In practice, one or more message prompt modules may be included in the target application. Each message prompt module may be configured to process messages for one or more service modules capable of supporting messaging. Taking video-type application as an example, the message prompting module corresponding to the my tag in navigation at the bottom of the application interface can be used for prompting messages sent by the downloading service module, the skin service module, the collection service module and the game service module. When any one or more service modules send a message, the message prompting module can present a special mark (such as a red dot) in the my tag to remind the user that a new message exists in the service module associated with the tag.
Therefore, the deployed message management component receives the target message of the message sending service party, so that the direct message transmission between the message sending service party and the message receiving service party is avoided, and the coupling degree of codes between the message sending service party and the message receiving service party is reduced.
In some optional implementations of this embodiment, the message management component is eventbus3.0 version three of the publish/subscribe event bus. In practice, EventBus3.0 is an Android event publishing and subscribing lightweight frame, and EventBus3.0 can replace the traditional interface function of Android to transmit data among threads. Thus, messages sent by the service module of the application can be received through EventBus 3.0.
In this embodiment, after receiving a target message sent by a message sending service party through a message management component, the execution subject may determine a service type of the target message. In practice, each message may carry information characterizing the traffic type of the message. Based on this information, the service type of the targeted message may be determined.
In some optional implementations of this embodiment, the target message may carry a service type identifier. The service type identifier can be used to characterize the service type of the target message. In practice, the service type identifier may be a character string composed of various characters. The service type identifier corresponding to each service type may be preset. At this time, the execution body may first read the service type identifier of the target message; and then, based on the service type identification, determining the service type of the target message.
In this embodiment, after determining the service type of the target message, the execution main body may query a message receiving service party that monitors the message of the service type. The message receiving service party is a message prompt module in the target application.
In practice, one or more message receiving business parties may be included in the target application. Each message receiving party may be configured to process messages of one or more service types. Thus, different message receiving service parties may listen to messages of the same or different service types. Messages of the same service type may be listened to by one or more message receiving service parties.
Taking video-type application as an example, the message prompting module corresponding to the my tag in navigation at the bottom of the application interface can be used for prompting messages sent by the downloading service module, the skin service module, the collection service module and the game service module. When any one or more service modules send a message, the message prompting module can present a special mark (such as a red dot) in the my tag to remind the user that a new message exists in the service module associated with the tag.
And 104, taking the inquired message receiving service party as a target message receiving service party, and sending the target message to the target message receiving service party through the message management component so that the target message receiving service party prompts the target message.
In this embodiment, the executing entity may first use the queried message receiving service party as the target message receiving service party. It should be noted here that, if a plurality of message receiving service parties monitoring messages of the service type are queried, each queried message receiving service party may be used as a target message receiving service party. Then, the target message can be sent to the target message receiving service party through the message management component, so that the target message receiving service party prompts the target message.
As an example, the target message receiving service party is a message prompt module corresponding to a "my" tag in the navigation at the bottom of the interface of the video-class application. After the message prompting module monitors the target message and obtains the target message, the message prompting module can prompt the message by presenting a special mark (such as a red dot) form in the My tag.
It should be noted that the target message receiving service party may prompt the target message in a preset prompting manner. For example, any form may be selected, such as a prompt by a special mark (e.g., a red dot), a prompt by an unread message amount, an animated prompt, etc., without limitation.
In the method provided by the above embodiment of the present application, a target message sent by a message sending service party is received through a pre-deployed message management component; then determining the service type of the target message; then inquiring a message receiving service party for monitoring the message of the service type; and finally, the inquired message receiving service party is used as a target message receiving service party, and the target message is sent to the target message receiving service party through the message management component, so that the target message receiving service party prompts the target message. Therefore, the message management component is used for receiving and sending the messages between the target application modules, so that the direct calling between the service module and the message prompt module is avoided, the code coupling degree between the target application modules is reduced, the codes are convenient to maintain, and the error rate of the message prompt service is reduced.
With further reference to fig. 2, a flow 200 of yet another embodiment of an information prompting method is shown. The process 200 of the information prompting method includes the following steps:
In this embodiment, the execution subject of the message alert method may be installed with a target application. The target application can be any application with a message prompt function, such as a video application, an instant messaging application, and the like. The message receiving service party may be a message prompt module in the target application. The message prompting module can process the message prompting service based on the message sent by the service module, thereby realizing the prompting of the message.
In this embodiment, the target application may be pre-deployed with a message management component. The message management component may be a framework for managing messages (e.g., receiving messages, sending messages). For example, it may be EventBus3.0 version III of the publish-subscribe event bus. In practice, EventBus3.0 is an Android event publishing and subscribing lightweight frame, and EventBus3.0 can replace the traditional interface function of Android to transmit data among threads. Thus, messages sent by the service module of the application can be received through EventBus 3.0.
The message management component can decouple the publisher and the subscriber of the event, so that the publisher and the subscriber do not directly carry out message transmission, thereby reducing the coupling degree of codes between the publisher and the subscriber. Here, the event is a message sending event. The publisher may be a messaging service and the subscriber may be a messaging service. The message sending business target application comprises a business module supporting message sending. Taking the video-type application as an example, the service module supporting message sending may include, but is not limited to, a download service module, a skin service module, a collection service module, a game service module, a wallet service module, a hot spot message recommendation service module, an instant messaging service module, and the like.
In this embodiment, the message management component may receive a listening notification sent by each message receiving service party. The listening notification may include the service type of the listened message. In practice, the message receiving service party may have one or more. Each message receiving service party may listen for messages of one or more service types. The message receiving service side can transmit the interception notification by registering interception by calling a register function (a function providing an interception function). It should be noted that the message receiving service party may also release the interception of a certain type of message by means of unregistering (e.g., calling an unregister function for interception).
In this embodiment, the execution main body may determine a corresponding relationship between the service type and the corresponding relationship between the message receiving service parties, based on the service type of the message monitored by each message receiving service party. For each service type, the message receiving service party for monitoring the message of the service type is the message receiving service party having a corresponding relationship with the service type. Then, based on the determined correspondence, correspondence information for characterizing the correspondence of the service type and the message receiving service party may be established.
In this embodiment, the execution agent may receive a target message sent by the message sending service party through a pre-deployed message management component (e.g., the eventbus3.0 described above).
It should be noted that step 203 in the embodiment may refer to step 101 in the embodiment shown in fig. 1, and is not described herein again.
In this embodiment, the target message may have a service type identifier. The service type identifier can be used to characterize the service type of the target message. In practice, the service type identifier may be a character string composed of various characters. The service type identifier corresponding to each service type may be preset. At this time, the execution body may first read the service type identifier of the target message; and then, based on the service type identification, determining the service type of the target message.
In this embodiment, the execution main body may query a message receiving service party having a correspondence with the service type of the target message from the correspondence information. Since the correspondence information is established based on the service type of the message monitored by each message receiving service party, the message receiving service party having a correspondence with the service type of the target message is the message receiving service party inquiring the message monitoring the service type (i.e. the service type of the target message).
In this embodiment, the executing entity may first use the queried message receiving service party as the target message receiving service party. It should be noted here that, if a plurality of message receiving service parties monitoring messages of the service type are queried, each queried message receiving service party may be used as a target message receiving service party. Then, the target message can be sent to the target message receiving service party through the message management component, so that the target message receiving service party prompts the target message.
As an example, the target message receiving service party is a message prompt module corresponding to a "my" tag in the navigation at the bottom of the interface of the video-class application. After the message prompting module monitors the target message and obtains the target message, the message prompting module can prompt the message by presenting a special mark (such as a red dot) in the My tag.
With continued reference to fig. 3, fig. 3 is a schematic diagram of an application scenario of the message alert method according to the present embodiment. As shown in fig. 3, the message receiving service side in the video application includes a message prompt module corresponding to a "my" tag, a message prompt module corresponding to a "member" tag, and other modules. The message sending service party comprises a service module corresponding to the bubble service, a service module corresponding to the download service, a service module corresponding to the collection service and other service modules.
As shown in fig. 3, the message prompt module corresponding to the my tag needs to monitor the message of the "download" service type. At this time, the message prompt module corresponding to the "my" tag can register monitoring of the message of the service type in advance by calling a register function, and becomes a listener for "downloading" the message of the service type.
After a certain video is downloaded, the service module of the "download" service can send a message to the message management component by calling the post function. After the message management component obtains the message sent by the service module of the 'download' service, the service type of the message can be determined, and then the message prompt module corresponding to the 'my' label of the message receiving service party for monitoring the message of the service type can be inquired. Thus, the message can be sent to the queried message prompt module. Finally, the message prompt module can prompt the message on the my tag (for example, prompt the message by presenting a special mark).
It should be noted that, if there are multiple message receiving service parties monitoring the message of the service type, the message may be sent to each message receiving service party monitoring the message of the service type.
It should be noted that, as shown in fig. 3, if a certain message receiving service party needs to listen to a message of a certain service type, the message receiving service party can perform release by calling an unregister function.
In the message prompting method in this embodiment, the monitoring notification sent by each message receiving service party is received by the message management component deployed in advance, so that the information of the corresponding relationship between the message receiving service party and the service type of the monitored message can be established; after receiving the target message through the message management component, determining a target message receiving service party based on the service type of the target message; the target message can thus be sent to the target message receiving service party via the message management component to prompt the target message receiving service party for the target message. Therefore, the message management component is used for receiving and sending the messages between the target application modules, so that the direct calling between the service module and the message prompt module is avoided, the code coupling degree between the target application modules is reduced, the codes are convenient to maintain, and the error rate of the message prompt service is reduced.
With further reference to fig. 4, as an implementation of the methods shown in the above-mentioned figures, the present application provides an embodiment of a message prompting apparatus, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 1, and the apparatus may be specifically applied to various electronic devices.
As shown in fig. 4, the message prompt apparatus 400 according to this embodiment includes: a first receiving unit 401, configured to receive, through a pre-deployed message management component, a target message sent by a message sending service party, where the message sending service party is a service module supporting message sending in a target application; a determining unit 402 configured to determine a service type of the target message; an inquiring unit 403, configured to inquire a message receiving service party that monitors the message of the service type, where the message receiving service party is a message prompt module in the target application; a sending unit 404, configured to send the target message to the target message receiving service party through the message management component by using the queried message receiving service party as the target message receiving service party, so that the target message receiving service party prompts the target message.
In some optional implementation manners of this embodiment, the target message carries a service type identifier; and the determining unit 402, further configured to: reading the service type identifier; and determining the service type of the target message based on the service type identifier.
In some optional implementations of this embodiment, the apparatus further includes: the second receiving unit is configured to receive a monitoring notification sent by each message receiving service party through a pre-deployed message management component, wherein the monitoring notification comprises the service type of the monitored message; and the establishing unit is configured to establish corresponding relation information for representing the corresponding relation between the service type and the message receiving service party based on the service type of the message monitored by each message receiving service party.
In some optional implementations of this embodiment, the querying unit 403 is further configured to: and inquiring the message receiving service party having the corresponding relation with the service type of the target message from the corresponding relation information.
In some optional implementations of this embodiment, the message management component is an eventbus3.0 version three of a publish-subscribe event bus.
The device provided by the above embodiment of the present application receives a target message sent by a message sending service party through a pre-deployed message management component; then determining the service type of the target message; then inquiring a message receiving service party for monitoring the message of the service type; and finally, the inquired message receiving service party is used as a target message receiving service party, and the target message is sent to the target message receiving service party through the message management component, so that the target message receiving service party prompts the target message. Therefore, the message management component is used for receiving and sending the messages between the target application modules, so that the direct calling between the service module and the message prompt module is avoided, the code coupling degree between the target application modules is reduced, the codes are convenient to maintain, and the error rate of the message prompt service is reduced.
An embodiment of the present invention further provides an electronic device, as shown in fig. 5, which includes a processor 501, a communication interface 502, a memory 503 and a communication bus 504, where the processor 501, the communication interface 502 and the memory 503 complete mutual communication through the communication bus 504,
a memory 503 for storing a computer program;
the processor 501, when executing the program stored in the memory 503, implements the following steps:
receiving a target message sent by a message sending service party through a pre-deployed message management component, wherein the message sending service party is a service module supporting message sending in a target application;
determining the service type of the target message;
inquiring a message receiving service party for monitoring the message of the service type, wherein the message receiving service party is a message prompt module in the target application;
and taking the inquired message receiving service party as a target message receiving service party, and sending the target message to the target message receiving service party through the message management component so that the target message receiving service party prompts the target message.
The communication bus mentioned in the above terminal may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface is used for communication between the terminal and other equipment.
The Memory may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.
In another embodiment of the present invention, a computer-readable storage medium is further provided, which has instructions stored therein, and when the instructions are executed on a computer, the instructions cause the computer to execute the message prompting method described in any of the above embodiments.
In a further embodiment of the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the message alert method as described in any of the above embodiments.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (12)
1. A message prompting method is characterized in that the method comprises the following steps
Receiving a target message sent by a message sending service party through a pre-deployed message management component, wherein the message sending service party is a service module supporting message sending in a target application;
determining the service type of the target message;
inquiring a message receiving service party for monitoring the message of the service type, wherein the message receiving service party is a message prompt module in the target application;
and taking the inquired message receiving service party as a target message receiving service party, and sending the target message to the target message receiving service party through the message management component so that the target message receiving service party prompts the target message.
2. The method of claim 1, wherein the target message carries a service type identifier; and
the determining the service type of the target message includes:
reading the service type identification;
and determining the service type of the target message based on the service type identification.
3. The method of claim 1, wherein before the receiving, by the pre-deployed message management component, the target message sent by the messaging service, the method further comprises:
receiving a monitoring notification sent by each message receiving service party through a pre-deployed message management component, wherein the monitoring notification comprises the service type of the monitored message;
and establishing corresponding relation information for representing the corresponding relation between the service type and the message receiving service party based on the service type of the message monitored by each message receiving service party.
4. The method of claim 3, wherein querying the message receiving service party listening for messages of the service type comprises:
and inquiring a message receiving service party having a corresponding relation with the service type of the target message from the corresponding relation information.
5. The method according to one of claims 1 to 4, characterized in that the message management component is EventBus3.0 version III of the publish-subscribe event bus.
6. A message prompting apparatus, the apparatus comprising:
the first receiving unit is configured to receive a target message sent by a message sending service party through a message management component deployed in advance by sha, wherein the message sending service party is a service module supporting message sending in a target application;
a determining unit configured to determine a service type of the target message;
the query unit is configured to query a message receiving service party monitoring the message of the service type, wherein the message receiving service party is a message prompt module in the target application;
a sending unit, configured to use the queried message receiving service party as a target message receiving service party, and send the target message to the target message receiving service party through the message management component, so that the target message receiving service party prompts the target message.
7. The apparatus of claim 6, wherein the target message carries a service type identifier; and
the determining unit is further configured to:
reading the service type identification;
and determining the service type of the target message based on the service type identification.
8. The apparatus of claim 6, further comprising:
the second receiving unit is configured to receive a monitoring notification sent by each message receiving service party through a pre-deployed message management component, wherein the monitoring notification comprises the service type of the monitored message;
and the establishing unit is configured to establish corresponding relation information for representing the corresponding relation between the service type and the message receiving service party based on the service type of the message monitored by each message receiving service party.
9. The apparatus of claim 8, wherein the querying element is further configured to:
and inquiring a message receiving service party having a corresponding relation with the service type of the target message from the corresponding relation information.
10. The apparatus of any of claims 6-9, wherein the message management component is a publish-subscribe event bus version three eventbus 3.0.
11. An electronic device is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing mutual communication by the memory through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of any one of claims 1 to 5 when executing a program stored in the memory.
12. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911158205.1A CN110912807A (en) | 2019-11-22 | 2019-11-22 | Information prompting method and device, electronic equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911158205.1A CN110912807A (en) | 2019-11-22 | 2019-11-22 | Information prompting method and device, electronic equipment and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110912807A true CN110912807A (en) | 2020-03-24 |
Family
ID=69819152
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911158205.1A Pending CN110912807A (en) | 2019-11-22 | 2019-11-22 | Information prompting method and device, electronic equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110912807A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111427710A (en) * | 2020-03-30 | 2020-07-17 | 南京领行科技股份有限公司 | Communication method, device, equipment and storage medium of components in application program |
| CN111555962A (en) * | 2020-04-30 | 2020-08-18 | 中国平安财产保险股份有限公司 | Red dot message prompting method, device, equipment and storage medium |
| CN111786886A (en) * | 2020-06-30 | 2020-10-16 | 京东数字科技控股有限公司 | Message processing method, device and system, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104601446A (en) * | 2014-12-30 | 2015-05-06 | 上海孩子国科教设备有限公司 | Information reminding method and system for interactive communication |
| US9501763B2 (en) * | 2008-01-16 | 2016-11-22 | International Business Machines Corporation | Social collaborative scoring for message prioritization according to a temporal factor between sender and recipient |
| CN109766036A (en) * | 2018-12-24 | 2019-05-17 | 华为终端有限公司 | Message treatment method and electronic equipment |
| CN110011872A (en) * | 2019-04-10 | 2019-07-12 | 海南航空控股股份有限公司 | A kind of streaming computing platform status monitoring method and device based on diagnostic message |
| CN110309002A (en) * | 2019-05-29 | 2019-10-08 | 北京达佳互联信息技术有限公司 | Message treatment method, device, electronic equipment and storage medium |
-
2019
- 2019-11-22 CN CN201911158205.1A patent/CN110912807A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9501763B2 (en) * | 2008-01-16 | 2016-11-22 | International Business Machines Corporation | Social collaborative scoring for message prioritization according to a temporal factor between sender and recipient |
| CN104601446A (en) * | 2014-12-30 | 2015-05-06 | 上海孩子国科教设备有限公司 | Information reminding method and system for interactive communication |
| CN109766036A (en) * | 2018-12-24 | 2019-05-17 | 华为终端有限公司 | Message treatment method and electronic equipment |
| CN110011872A (en) * | 2019-04-10 | 2019-07-12 | 海南航空控股股份有限公司 | A kind of streaming computing platform status monitoring method and device based on diagnostic message |
| CN110309002A (en) * | 2019-05-29 | 2019-10-08 | 北京达佳互联信息技术有限公司 | Message treatment method, device, electronic equipment and storage medium |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111427710A (en) * | 2020-03-30 | 2020-07-17 | 南京领行科技股份有限公司 | Communication method, device, equipment and storage medium of components in application program |
| CN111427710B (en) * | 2020-03-30 | 2022-06-28 | 南京领行科技股份有限公司 | Communication method, device, equipment and storage medium of components in application program |
| CN111555962A (en) * | 2020-04-30 | 2020-08-18 | 中国平安财产保险股份有限公司 | Red dot message prompting method, device, equipment and storage medium |
| CN111786886A (en) * | 2020-06-30 | 2020-10-16 | 京东数字科技控股有限公司 | Message processing method, device and system, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107783849B (en) | Event processing method and client | |
| CN110912807A (en) | Information prompting method and device, electronic equipment and computer readable storage medium | |
| CN110022259B (en) | Message arrival rate determining method and device, data statistics server and storage medium | |
| CN110601965B (en) | Message distribution method, device and system and message gateway | |
| WO2019085641A1 (en) | Method and apparatus for friend recommendation | |
| CN109743246B (en) | Message emergency reminding method and device and electronic equipment | |
| CN108509541B (en) | Message reading method, message reading device and mobile terminal | |
| CN113938522B (en) | Event message transmission method, system, device and computer storage medium | |
| US7366505B2 (en) | Apparatus and method for delivering messages to a mobile information terminal | |
| CN111159269B (en) | Data processing method, device and system | |
| US11146649B2 (en) | Computer-implemented method and computer system for distributing push notifications | |
| CN107046547B (en) | Abnormal operation identification method and device | |
| CN112788090B (en) | Network resource transmission method, device and system | |
| CN111626802A (en) | Method and apparatus for processing information | |
| CN114238021A (en) | SDK interface positioning method, device, equipment and computer storage medium | |
| CN107295179A (en) | The method and apparatus that a kind of short message is shown | |
| CN109348053B (en) | Telephone number mark processing method, server, terminal device and computer readable storage medium | |
| CN108965431B (en) | Method and device for realizing event-driven architecture by IBM (International Business machines corporation) host | |
| CN112083945A (en) | NPM installation package update prompting method and device, electronic equipment and storage medium | |
| CN115955450B (en) | Instant message display and push method and device, electronic equipment and storage medium | |
| CN110751464A (en) | Information prompting method, device, equipment and storage medium | |
| US20130137461A1 (en) | Method and apparatus for inserting location data into messages at a communication gateway | |
| CN111383025B (en) | Method and device for forwarding wind control data and electronic equipment | |
| CN112068917B (en) | Interface presentation method, device, electronic equipment and computer readable medium | |
| CN113766437B (en) | Short message sending method and device |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200324 |