CN111027809B

CN111027809B - Message notification method, device, medium and electronic equipment

Info

Publication number: CN111027809B
Application number: CN201911108131.0A
Authority: CN
Inventors: 王锐; 孙通
Original assignee: Taikang Insurance Group Co Ltd; Taikang Pension Insurance Co Ltd
Current assignee: Taikang Insurance Group Co Ltd; Taikang Pension Insurance Co Ltd
Priority date: 2019-11-13
Filing date: 2019-11-13
Publication date: 2022-07-05
Anticipated expiration: 2039-11-13
Also published as: CN111027809A

Abstract

The invention provides a message notification method, which comprises the following steps: acquiring an event; dividing the event into homologous event sequences corresponding to the event according to the identification of the event; determining a message to be sent of the event according to the event; and determining the sending time of the message to be sent according to whether the event has a pre-event and/or a post-event in the homologous event sequence, so that a useful message can be effectively screened out for the client, and the client is informed at a proper time, thereby reducing the probability of missing important messages by the client, improving the working efficiency and improving the user experience. The invention also provides a message notification device, a medium and an electronic device.

Description

Message notification method, device, medium and electronic equipment

Technical Field

The present invention relates to the field of message processing technologies, and in particular, to a message notification method, an apparatus, a medium, and an electronic device.

Background

In the daily business of insurance companies, a large number of interactive scenes are needed to contact with customers, and with the rise of various internet tools, the insurance application process of the customers is gradually switched from online to online. The insurance product is more complex than the common product, and particularly, the insurance process of the long-term insurance product is long, which relates to asynchronous processes of check insurance, fee deduction and the like. In order to enable the salesman to know and master the behaviors of the client in the online application process at the first time, know that the user has problems in time, actively solve the problems and promote the business, a mechanism is needed to inform the salesman. At present, the method for notifying the service staff is as follows: when the client has an insurance application on the line, the server is notified, but if the clients developed by the server at the same time are more, the clients are flooded by a great deal of process messages, so that important messages can be missed, and if the server wants to view useful messages, a great deal of effort and time are needed to screen useful notifications from a great deal of messages, which greatly affects the working efficiency of the server.

It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present invention and therefore may include information that does not constitute prior art known to a person of ordinary skill in the art.

Disclosure of Invention

Embodiments of the present invention provide a message notification method, an apparatus, a medium, and an electronic device, so as to reduce the probability of missing important messages to at least some extent, save energy and time of a user, and further improve work efficiency.

Additional features and advantages of the invention will be set forth in the detailed description which follows, or may be learned by practice of the invention.

According to a first aspect of the embodiments of the present invention, there is provided a message notification method, including: acquiring an event; dividing the event into corresponding homologous event sequences according to the identifier of the event; determining a message to be sent of the event according to the event; and determining the sending time of the message to be sent according to whether the event has a pre-event and/or a post-event in the homologous event sequence.

In some embodiments of the invention, the event comprises an event resulting from a user action or a key state change.

In some embodiments of the invention, the method further comprises: generating an identification of the event based on an application scenario, user information, product information, and/or order information.

In some embodiments of the present invention, determining the sending timing of the message to be sent according to whether a pre-event and/or a post-event exists in the homologous event sequence of the event includes: and if the event has a pre-event and no post-event in the homologous event sequence, storing the message to be sent into the message pool to be sent, and sending the message to be sent according to the sending time of the message to be sent.

In some embodiments of the invention, the method further comprises: and if the event has a pre-event in the homologous event sequence, deleting the message to be sent of the pre-event from the message pool to be sent.

In some embodiments of the present invention, determining the sending timing of the message to be sent according to whether a pre-event and/or a post-event exists in the homologous event sequence of the event includes: and if the event does not have a pre-event and a post-event in the homologous event sequence, the message to be sent is not stored in a message pool to be sent and is not sent.

In some embodiments of the invention, the method further comprises: and if the event is a preset event, storing the message to be sent into a message pool to be sent, and sending the message to be sent according to the sending time of the message to be sent.

According to a second aspect of the embodiments of the present invention, there is provided a message notification apparatus, including: the acquisition module is used for acquiring events; the dividing module is used for dividing the event into corresponding homologous event sequences according to the identifier of the event; the first determining module is used for determining a message to be sent of the event according to the event; a second determining module, configured to determine a sending opportunity of the message to be sent according to whether a pre-event and/or a post-event exists in the homologous event sequence of the event.

In some embodiments of the invention, the apparatus further comprises: a generation module that generates an identification of the event based on an application scenario, user information, product information, and/or order information.

In some embodiments of the invention, the apparatus further comprises: and the deleting module is used for deleting the message to be sent of the pre-event from the message pool to be sent if the pre-event exists in the homologous event sequence of the event.

In some embodiments of the invention, the apparatus further comprises: and the sending module stores the message to be sent into a message pool to be sent and sends the message to be sent according to the sending time of the message to be sent if the event is a preset event.

According to a third aspect of embodiments of the present invention, there is provided an electronic apparatus, including: one or more processors; storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the message notification method as described in the first aspect of the embodiments above.

According to a fourth aspect of embodiments of the present invention, there is provided a computer-readable medium, on which a computer program is stored, which when executed by a processor, implements the message notification method as described in the first aspect of the embodiments above.

The technical scheme provided by the embodiment of the invention has the following beneficial effects:

in the technical solutions provided in some embodiments of the present invention, by obtaining an event, dividing the event into a corresponding homologous event sequence according to an identifier of the event, determining a message to be sent of the event according to the event, and then determining a sending time of the message to be sent according to whether a pre-event and/or a post-event exists in the homologous event sequence of the event, a useful message can be effectively screened for a client, and the message is sent to the user at an appropriate time, so that a probability that the client misses an important message is reduced, working efficiency is improved, and user experience is improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention. It is obvious that the drawings in the following description are only some embodiments of the invention, and that for a person skilled in the art, other drawings can be derived from them without inventive effort. In the drawings:

fig. 1 is a schematic diagram illustrating an exemplary system architecture to which a message notification method or a message notification apparatus according to an embodiment of the present invention may be applied;

FIG. 2 schematically shows a flow diagram of a message notification method according to an embodiment of the invention;

FIG. 3 schematically illustrates a flow diagram of a message notification method according to another embodiment of the invention;

FIG. 4 schematically illustrates a flow diagram of a message notification method according to another embodiment of the invention;

FIG. 5 schematically illustrates a flow diagram of a message notification method according to another embodiment of the invention;

FIG. 6 schematically illustrates a flow diagram of a message notification method according to another embodiment of the invention;

FIG. 7 is a schematic diagram that schematically illustrates an event generated when a customer commits an insurance, in accordance with an embodiment of the present invention;

FIG. 8 schematically shows a block diagram of a message notification apparatus according to an embodiment of the present invention;

fig. 9 schematically shows a block diagram of a message notification apparatus according to another embodiment of the present invention;

fig. 10 schematically shows a block diagram of a message notification apparatus according to another embodiment of the present invention;

fig. 11 schematically shows a block diagram of a message notification apparatus according to another embodiment of the present invention;

FIG. 12 illustrates a schematic structural diagram of a computer system suitable for use with the electronic device to implement an embodiment of the invention.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention may be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known methods, devices, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the invention.

The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.

The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.

Fig. 1 is a schematic diagram illustrating an exemplary system architecture to which a message notification method or a message notification apparatus according to an embodiment of the present invention may be applied.

As shown in fig. 1, the system architecture 100 may include one or more of

terminal devices

101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the

terminal devices

101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation. For example, server 105 may be a server cluster comprised of multiple servers, or the like.

The user may use the

terminal devices

101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The

terminal devices

101, 102, 103 may be various electronic devices having a display screen, including but not limited to smart phones, tablet computers, portable computers, desktop computers, and the like.

The server 105 may be a server that provides various services. For example, the server 105 may obtain an event from the terminal device 103 (or the terminal device 101 or 102), and then the server 105 divides the event into a corresponding homologous event sequence according to the identifier of the event, determines a message to be sent of the event according to the event, and determines a sending timing of the message to be sent according to whether a pre-event and/or a post-event exists in the homologous event sequence of the event, so that a useful message may be effectively screened for a client, and the message is sent to the user at an appropriate timing, thereby reducing a probability that the client misses an important message, improving work efficiency, and improving user experience.

In some embodiments, the message notification method provided by the embodiments of the present invention is generally performed by the server 105, and accordingly, the message notification apparatus is generally disposed in the server 105. In other embodiments, some terminals may have similar functionality as the server to perform the method. Therefore, the message notification method provided by the embodiment of the invention is not limited to be executed at the server side.

Fig. 2 schematically shows a flow chart of a message notification method according to an embodiment of the invention.

As shown in fig. 2, the message notification method may include steps S210 to S240.

In step S210, an event is acquired.

In step S220, the events are classified into corresponding homologous event sequences according to the identifiers of the events.

In step S230, a message to be sent of the event is determined according to the event.

In step S240, determining a sending timing of the message to be sent according to whether a pre-event and/or a post-event exists in the homologous event sequence of the event.

The method can divide the event into the homologous event sequence corresponding to the event according to the identification of the event by acquiring the event, determine the message to be sent of the event according to the event, and then determine the sending time of the message to be sent according to whether the event has a front event and/or a rear event in the homologous event sequence, so that the useful message can be effectively screened out for a client, and the message is sent to the user at the proper time, thereby reducing the probability that the client misses the important message, improving the working efficiency and improving the user experience.

In one embodiment of the invention, the events may be events resulting from a guest operation or a critical state change. For example, a customer makes an application online, and in the application process, the customer generates a series of events for an insurance product. For example, the events generated due to the guest operation may be: the system comprises a login event generated by logging in an insurance platform, an event generated by a client browsing insurance products on the insurance platform, and an event generated by the client clicking 'instant purchase', 'shopping cart', 'order submission', 'order payment' and the like on the insurance platform aiming at a certain insurance product. As another example, the events that occur due to a critical state change may be: events resulting from a failure to underwritten, events resulting from a loss of a debit, events resulting from a policy validation.

In one embodiment of the present invention, the identification of the event may refer to an identification of an event generated by the same user during the application process. For example, Wangzhi produced five events during the application process, each of which carries the identity of W. Alternatively, the identifier of the event may also refer to an identifier of an event generated by the same business process. For example, ten events are generated in the underwriting process, and each of the ten events carries an identification of H. This facilitates the classification of the generated events into their corresponding homologous event sequences, i.e. the event identifications of the events comprised in the homologous event sequences are identical.

In an embodiment of the present invention, the method further includes: the identification of the event is generated based on the application scenario, user information, product information, and/or order information.

In one embodiment of the invention, a message to be sent for an event is determined based on the event. For example, a preset mapping table of an event and a message to be sent is referred to determine the message to be sent of the event according to the event. For example, the mapping table between the event and the message to be sent stores the corresponding relationship between the event a and the message to be sent, and determining the message to be sent of the event a according to the event a may specifically be determining the message to be sent of the event a according to the corresponding relationship between the event a and the message to be sent a.

In one embodiment of the present invention, since the same user generally generates a plurality of events during the application process or the same business process, the event acquired in real time may have a pre-event and/or a post-event. In this example, the sending timing of the message to be sent may be determined according to whether a pre-event and/or a post-event exists in the homologous event sequence of the event obtained in real time. For example, if a pre-event exists in the event obtained in real time in the homologous event sequence and a post-event does not exist in the event obtained in real time, storing a message to be sent of the event in a message pool to be sent, and sending the message to be sent according to the sending time of the message to be sent. For another example, if the event obtained in real time does not have a pre-event and a post-event in the homologous event sequence, the message to be sent of the event is not stored in the message pool to be sent, and the message to be sent is not sent.

Fig. 3 schematically shows a flow chart of a message notification method according to another embodiment of the invention. According to an embodiment of the present disclosure, the step S240 may be specifically the step S310.

As shown in fig. 3, the above message notification method includes step S210, step S220, step S230, and step S310.

In step S210, an event is acquired.

In step S310, if the event has a pre-event and no post-event in the homologous event sequence, storing the message to be sent in the message pool to be sent, and sending the message to be sent according to the sending time of the message to be sent.

The method can divide the event into the corresponding homologous event sequence according to the identification of the event by acquiring the event, determine the message to be sent of the event according to the event, store the message to be sent of the event into a message pool to be sent if the event has a pre-event and does not have a post-event in the homologous event sequence, and send the message to be sent according to the sending time of the message to be sent, so that useful messages can be effectively screened out for clients, and the message is sent to the users at proper time, thereby reducing the probability of missing important messages by the clients, improving the working efficiency, and improving the user experience.

In an embodiment of the present invention, if the event has a pre-event and does not have a post-event in the homologous event sequence, the message to be sent is stored in a message pool to be sent, and the message to be sent is sent according to the sending time of the message to be sent. The leading event and the trailing event of the event can be determined according to the time of generating the event, or according to the time of acquiring the event, or according to a predefined event stream.

For example, in an application process, a time a generates an event a, a time b generates an event b, and a time c generates an event c, wherein the time a, the time b, and the time c are arranged in chronological order as follows: the time a, the time b and the time c, therefore, if the front event and the back event of the event are determined according to the time of generating the event, the front event of the event b is the event a, and the back event of the event b is the event c.

For another example, the event a, the event b, and the event c are obtained in real time according to the sequence of time, and at this time, if the time is determined according to the time of obtaining the event, the leading event of the event b is the event a, and the trailing event of the event b is the event c.

For another example, if the precedence relationship of events is defined in the event stream, such as c- > b- > a. In this case, the event b and the event c are both leading events of the event a, and the event a and the event b are both trailing events of the event c.

In an embodiment of the present invention, the message pool to be sent is used for temporarily storing messages to be sent. In this example, the message pool to be sent may be continuously polled, and the message to be sent may be sent according to the current time and the sending time of the message to be sent.

In one embodiment of the invention, a message to be sent for an event is determined based on the event. The message to be sent comprises sending time for sending the message to be sent. In this embodiment, the sending method for sending the message to be sent according to the sending time may include immediate sending or delayed sending.

In one embodiment of the present invention, the sending time of the message to be sent can be determined according to the importance degree of the event. For example, a customer generates the following events during an application: events that occur when a customer browses insurance products, events that occur when a customer submits an order, and events that occur when an underwriting fails. According to the importance degree of the event, the message to be sent of the event generated when the client browses the insurance product and the message to be sent of the event generated when the client submits the order can be sent in a delayed mode, but the message to be sent of the event generated when the underwriting fails is sent immediately.

Fig. 4 schematically shows a flow chart of a message notification method according to another embodiment of the invention.

As shown in fig. 4, the message notification method includes step S410 in addition to step S210, step S220 and step S410 described in the embodiment of fig. 3.

In step S210, an event is acquired.

In step S410, if the event has a pre-event in the homologous event sequence, deleting a message to be sent of the pre-event from the message to be sent pool.

The method can divide the event into the corresponding homologous event sequence according to the identifier of the event by acquiring the event, determine the message to be sent of the event according to the event, and delete the message to be sent of the preposed event from the message pool to be sent if the event has the preposed event in the homologous event sequence, so that useful messages can be effectively screened for clients, the time for polling the message pool to be sent can be reduced, and the working efficiency is further improved.

In one embodiment of the present invention, if the event has a pre-event in the homologous event sequence, the message to be sent of the pre-event is deleted from the message pool to be sent. For example, the client generates three events during the application process: events generated when logging in the insurance platform, events generated when browsing insurance products, and events generated when submitting orders. In this case, when the event obtained in real time is the event generated when the order is submitted, the message to be sent of the event generated when the insurance platform is logged in and the message to be sent of the event generated when the insurance product is browsed need not to be sent to the client again, and only the message to be sent of the event generated when the order is submitted needs to be sent to the client. Therefore, if the event has a pre-event in the homologous event sequence, the message to be sent of the pre-event is deleted from the message pool to be sent, so that useful messages can be effectively screened for clients, and the storage space of the message pool to be sent can be increased.

Fig. 5 schematically shows a flow chart of a message notification method according to another embodiment of the invention. According to an embodiment of the present disclosure, the step S240 may specifically be the step S510.

As shown in fig. 5, the above message notification method includes step S210, step S220, and step S510.

In step S210, an event is acquired.

In step S510, if the event does not have a pre-event and a post-event in the homologous event sequence, the message to be sent is not stored in a message pool to be sent, and the message to be sent is not sent.

The method can divide the event into the corresponding homologous event sequence according to the identification of the event by acquiring the event, and determine the message to be sent of the event according to the event, if the event does not have a preposed event and a postpositional event in the homologous event sequence, the message to be sent is not stored in the message pool to be sent, and the message to be sent is not sent, so that useful messages can be effectively screened out for clients, the time for polling the message pool to be sent can be reduced, and the working efficiency is further improved.

In an embodiment of the present invention, since there may be a delay problem in the sending server for the event generated by the terminal, the server may receive the event generated after the terminal first and then receive the event generated before the terminal when acquiring in real time. For example, a client applies insurance on a terminal, and generates three events in total, wherein the three events are arranged according to the sequence of the event generation time: event a, event B, event C. Generally, the sequence of events obtained by the server in real time may be: event a, event B, event C. However, due to the delay problem, the sequence of the events obtained by the server in real time may also be: event C, event A, event B. Therefore, the event does not have a pre-event and can have a post-event in the homologous event sequence, and in this case, the message to be sent of the event may not be stored in the message pool to be sent, and the message to be sent may not be sent.

Fig. 6 schematically shows a flow chart of a message notification method according to another embodiment of the invention.

As shown in fig. 6, the message notification method includes a step S610 in addition to the steps S210, S220, and S510 described in the embodiment of fig. 5.

In step S210, an event is acquired.

In step S610, when the event does not have a pre-event and a post-event in the homologous event sequence, if the event is a preset event, storing the message to be sent in a message pool to be sent, and sending the message to be sent according to the sending time of the message to be sent.

The method comprises the steps of obtaining an event, dividing the event into a homologous event sequence corresponding to the event according to an identification of the event, determining a message to be sent of the event according to the event, storing the message to be sent into a message pool to be sent if the event is a preset event, and sending the message to be sent according to the sending time of the message to be sent.

In an embodiment of the present invention, the preset event may be set according to an actual situation of a service. For example, an event generated when the payment is successful is set as a preset event, or an event generated when the underwriting is failed is set as a preset event, and the like, but not limited thereto.

FIG. 7 is a schematic diagram that schematically illustrates an event generated during an application by a customer, in accordance with an embodiment of the present invention.

As shown in fig. 7, eight events may be generated when a client places a insurance policy on the insurance platform, which are event F1, event F2, event F3, event F4, event F5, event F6, event F7, and event F8.

Through the message notification method provided by the invention, the events F1-F8 are obtained, each event in the events F1-F8 is divided into the corresponding homologous event sequence according to the identifiers of the events F1-F8, the message to be sent of the events F1-F8 is determined according to the events F1-F8, and then the sending time of the message to be sent is determined according to whether the pre-event and/or the post-event exist in the homologous event sequence of each event in the events F1-F8, so that a useful message can be effectively screened out for a client, and the message is sent to the user at a proper time, thereby reducing the probability that the client misses an important message, improving the working efficiency and improving the user experience.

Fig. 8 schematically shows a block diagram of a message notification apparatus according to an embodiment of the present invention.

As shown in fig. 8, the message notification apparatus 800 includes an acquisition module 810, a division module 820, a first determination module 830, and a second determination module 840.

Specifically, the obtaining module 810 is configured to obtain an event.

A dividing module 820, configured to divide the event into corresponding homologous event sequences according to the identifier of the event.

A first determining module 830, configured to determine, according to the event, a message to be sent of the event.

A second determining module 840, configured to determine a sending timing of the message to be sent according to whether a pre-event and/or a post-event exists in the homologous event sequence of the event.

The message notification device 800 may divide the event into the corresponding homologous event sequence according to the identifier of the event by acquiring the event, determine the message to be sent of the event according to the event, and then determine the sending time of the message to be sent according to whether the event has a pre-event and/or a post-event in the homologous event sequence, so as to effectively screen a useful message for the client and send the message to the user at a proper time, thereby reducing the probability that the client misses an important message, improving the working efficiency, and improving the user experience.

According to an embodiment of the present invention, the message notification apparatus 800 may be used to implement the message notification method described in the embodiment of fig. 2.

In some embodiments of the present invention, determining the sending timing of the message to be sent according to whether a pre-event and/or a post-event exists in the homologous event sequence of the event includes: if the event has a pre-event and no post-event in the homologous event sequence, storing the message to be sent into the message pool to be sent, and sending the message to be sent according to the sending time of the message to be sent, so that a useful message can be effectively screened out for a client, and the message is sent to the user at a proper time, thereby reducing the probability that the client misses an important message, improving the working efficiency and improving the user experience.

Fig. 9 schematically shows a block diagram of a message notification apparatus according to another embodiment of the present invention.

As shown in fig. 9, the message notification apparatus 800 further includes a generating module 850, in addition to the acquiring module 810, the dividing module 820, the first determining module 830, and the second determining module 840 described in the embodiment of fig. 8.

Specifically, the generation module 850 generates the identifier of the event based on the application scenario, the user information, the product information, and/or the order information.

The message notification apparatus 800 may generate the identifier of the event based on the application scenario, the user information, the product information, and/or the order information, so as to conveniently divide the generated event into the corresponding homologous event sequences, that is, the event identifiers of the events included in the homologous event sequences are the same.

Fig. 10 schematically shows a block diagram of a message notification apparatus according to another embodiment of the present invention.

As shown in fig. 10, the message notification apparatus 800 further includes a deletion module 860 in addition to the obtaining module 810, the dividing module 820, the first determining module 830 and the second determining module 840 described in the embodiment of fig. 8.

Specifically, the deleting module 860 deletes the to-be-sent message of the pre-event from the to-be-sent message pool if the pre-event exists in the homologous event sequence of the event.

The message notification device 800 can divide the event into the corresponding homologous event sequence according to the identifier of the event by acquiring the event, determine the message to be sent of the event according to the event, and delete the message to be sent of the pre-event from the message pool to be sent if the event has the pre-event in the homologous event sequence, so that a useful message can be effectively screened for a client, the time for polling the message pool to be sent can be reduced, and the working efficiency is further improved.

According to an embodiment of the present invention, the message notification apparatus 800 may be used to implement the message notification method described in the embodiment of fig. 4.

In some embodiments of the present invention, determining the sending timing of the message to be sent according to whether a pre-event and/or a post-event exists in the homologous event sequence of the event includes: if the event does not have a pre-event and a post-event in the homologous event sequence, the message to be sent is not stored in the message pool to be sent and is not sent, so that useful messages can be effectively screened out for clients, the time for polling the message pool to be sent can be reduced, and the working efficiency is further improved.

Fig. 11 schematically shows a block diagram of a message notification apparatus according to another embodiment of the present invention.

As shown in fig. 11, the message notification apparatus 800 further includes a sending module 870 in addition to the acquiring module 810, the dividing module 820, the first determining module 830, and the second determining module 840 described in the embodiment of fig. 8.

Specifically, the sending module 870 stores the message to be sent into a message pool to be sent if the event is a preset event, and sends the message to be sent according to the sending time of the message to be sent.

The message notification device 800 can divide the event into the corresponding homologous event sequence according to the identifier of the event by acquiring the event, determine the message to be sent of the event according to the event, store the message to be sent into the message pool to be sent if the event is a preset event, and send the message to be sent according to the sending time of the message to be sent.

According to an embodiment of the present invention, the message notification apparatus 800 may be used to implement the message notification method described in the embodiment of fig. 6.

For details that are not disclosed in the embodiments of the apparatus of the present invention, please refer to the above-described embodiments of the message notification method of the present invention for the details that are not disclosed in the embodiments of the apparatus of the present invention, because various modules of the message notification apparatus of the exemplary embodiment of the present invention can be used to implement the steps of the exemplary embodiments of the message notification method described in the above-described fig. 2 to 6.

It is understood that the obtaining module 810, the dividing module 820, the first determining module 830, the second determining module 840, the generating module 850, the deleting module 860, and the sending module 870 may be combined in one module to be implemented, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present invention, at least one of the obtaining module 810, the dividing module 820, the first determining module 830, the second determining module 840, the generating module 850, the deleting module 860, and the sending module 870 may be at least partially implemented as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or in a suitable combination of three implementations of software, hardware, and firmware. Alternatively, at least one of the obtaining module 810, the dividing module 820, the first determining module 830, the second determining module 840, the generating module 850, the deleting module 860, and the transmitting module 870 may be at least partially implemented as a computer program module that, when executed by a computer, may perform the functions of the respective modules.

Referring now to FIG. 12, shown is a block diagram of a computer system 900 suitable for use in implementing an electronic device of an embodiment of the present invention. The computer system 600 of the electronic device shown in fig. 12 is only an example, and should not bring any limitation to the function and the scope of use of the embodiments of the present invention.

As shown in fig. 12, the computer system 900 includes a Central Processing Unit (CPU)901 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)902 or a program loaded from a storage section 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data necessary for system operation are also stored. The CPU 901, ROM 902, and RAM 903 are connected to each other via a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.

The following components are connected to the I/O interface 905: an input portion 906 including a keyboard, a mouse, and the like; an output portion 907 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 908 including a hard disk and the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as necessary. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 910 as necessary, so that a computer program read out therefrom is mounted into the storage section 908 as necessary.

In particular, according to an embodiment of the present invention, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the invention include a computer program product comprising a computer program embodied on a computer-readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 909, and/or installed from the removable medium 911. The above-described functions defined in the system of the present application are executed when the computer program is executed by a Central Processing Unit (CPU) 901.

It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present invention may be implemented by software, or may be implemented by hardware, and the described units may also be disposed in a processor. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves.

As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to implement the message notification method as described in the above embodiments.

For example, the electronic device may implement the following as shown in fig. 2: in step S210, an event is acquired. In step S220, the events are classified into corresponding homologous event sequences according to the identifiers of the events. In step S230, a message to be sent of the event is determined according to the event. In step S240, determining a sending timing of the message to be sent according to whether a pre-event and/or a post-event exists in the homologous event sequence of the event.

It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the invention. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, and may also be implemented by software in combination with necessary hardware. Therefore, the technical solution according to the embodiment of the present invention can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the embodiment of the present invention.

Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.

It will be understood that the invention is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the invention is limited only by the appended claims.

Claims

1. A message notification method, comprising:

acquiring an event;

dividing the event into corresponding homologous event sequences according to the identifier of the event;

determining a message to be sent of the event according to the event;

determining the sending timing of the message to be sent according to whether the event has a pre-event and/or a post-event in the homologous event sequence, and determining the sending timing of the message to be sent according to whether the event has a pre-event and/or a post-event in the homologous event sequence comprises:

if the event has a pre-event and no post-event in the homologous event sequence, storing the message to be sent into a message pool to be sent, and sending the message to be sent according to the sending time of the message to be sent;

and if the event does not have a pre-event and a post-event in the homologous event sequence, the message to be sent is not stored in the message pool to be sent and is not sent.

2. The method of claim 1, wherein the event comprises an event generated by a user operation or a key state change.

3. The method of claim 1, further comprising:

generating an identification of the event based on an application scenario, user information, product information, and/or order information.

4. The method of claim 1, further comprising:

and if the event has a pre-event in the homologous event sequence, deleting the message to be sent of the pre-event from the message pool to be sent.

5. The method of claim 1, further comprising:

and if the event is a preset event, storing the message to be sent into a message pool to be sent, and sending the message to be sent according to the sending time of the message to be sent.

6. A message notification apparatus, comprising:

the acquisition module is used for acquiring events;

the dividing module is used for dividing the event into corresponding homologous event sequences according to the identifier of the event;

a first determining module, configured to determine, according to the event, a message to be sent of the event, where determining, according to whether a pre-event and/or a post-event exists in the homologous event sequence of the event, a sending timing of the message to be sent includes:

if the event has a pre-event and does not have a post-event in the homologous event sequence, storing the message to be sent into a message pool to be sent, and sending the message to be sent according to the sending time of the message to be sent;

if the event does not have a pre-event and a post-event in the homologous event sequence, the message to be sent is not stored in the message pool to be sent and the message to be sent is not sent;

a second determining module, configured to determine a sending opportunity of the message to be sent according to whether a pre-event and/or a post-event exists in the homologous event sequence of the event.

7. An electronic device, comprising:

one or more processors; and

storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to carry out a method according to any one of claims 1 to 5.

8. A computer-readable medium, on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out the method according to any one of claims 1 to 5.