CN112910987A - Message pushing method, system, device, equipment and storage medium - Google Patents
Message pushing method, system, device, equipment and storage medium Download PDFInfo
- Publication number
- CN112910987A CN112910987A CN202110118745.8A CN202110118745A CN112910987A CN 112910987 A CN112910987 A CN 112910987A CN 202110118745 A CN202110118745 A CN 202110118745A CN 112910987 A CN112910987 A CN 112910987A
- Authority
- CN
- China
- Prior art keywords
- message
- service
- pushing
- push
- service message
- 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
- 238000000034 method Methods 0.000 title claims abstract description 35
- 230000008859 change Effects 0.000 claims abstract description 23
- 238000004891 communication Methods 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims description 6
- 238000013461 design Methods 0.000 abstract description 4
- 238000012549 training Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 6
- 238000007726 management method Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 230000001755 vocal effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Abstract
The embodiment of the application provides a message pushing method, a message pushing system, a message pushing device and a message pushing equipment and a storage medium. The method comprises the following steps: determining whether service states of a plurality of external service systems are changed; when an external service system with a changed service state exists, generating a service message according to the service state change information of the external service system with the changed service state; determining a pushing strategy of the service message according to the type of the service message; and pushing the service message to the terminal according to the pushing strategy. The technical scheme provided by the embodiment of the application not only reduces the design cost of each service system, but also realizes the decoupling of the service codes and the messages. In addition, the technical scheme provided by the embodiment of the application can make different pushing strategies aiming at different types of messages, and push different types of messages according to different pushing strategies, so that diversified pushing requirements are met, and user experience is improved.
Description
Technical Field
The present application relates to the field of information technologies, and in particular, to a method, a system, an apparatus, a device, and a storage medium for pushing a message.
Background
With the rapid development of the intelligent terminal, the intelligent terminal can install various application programs. The message pushing function is a necessary function of the application program, and the server can push various messages to the user through the message pushing function so as to be referred or processed by the user.
At present, the existing message pushing scheme has the problems of high pushing cost, single pushing mode and the like.
Disclosure of Invention
In view of the above, the present application is proposed to provide a message pushing method, system, device, apparatus and storage medium that solve the above problems, or at least partially solve the above problems.
Thus, in one embodiment of the present application, a message push method is provided. The method comprises the following steps:
determining whether service states of a plurality of external service systems are changed;
when an external service system with a changed service state exists, generating a service message according to the service state change information of the external service system with the changed service state;
determining a pushing strategy of the service message according to the type of the service message;
and pushing the service message to the terminal according to the pushing strategy.
In yet another embodiment of the present application, a message push system is provided. The system comprises: the system comprises a message pushing server and a terminal in communication connection with the message pushing server;
the message pushing server is in communication connection with a plurality of external service systems and is used for:
determining whether a service state of the plurality of external service systems is changed; when an external service system with a changed service state exists, generating a service message according to the service state change information of the external service system with the changed service state; determining a pushing strategy of the service message according to the type of the service message; and pushing the service message to the terminal according to the pushing strategy.
In yet another embodiment of the present application, a message pushing device is provided. The device includes:
the first determining module is used for determining whether the service states of the plurality of external service systems change or not;
the generating module is used for generating a service message according to the service state change information of the external service system with the changed service state when the external service system with the changed service state exists;
the second determining module is used for determining a pushing strategy of the service message according to the type of the service message;
and the pushing module is used for pushing the service message to the terminal according to the pushing strategy.
In yet another embodiment of the present application, an electronic device is provided. The electronic device includes: a memory and a processor; the memory is configured to store one or more computer instructions, which when executed by the processor, are capable of implementing the steps of any of the above message pushing methods.
In yet another embodiment of the present application, a computer-readable storage medium storing a computer program is provided, where the computer program can realize the steps in the message pushing method according to any one of the above methods when executed by a computer.
In the technical scheme provided by the embodiment of the application, each service system does not need to pay attention to items such as message generation, message pushing and the like, so that the design cost of each service system is reduced, and decoupling of service codes and messages is realized. In addition, the technical scheme provided by the embodiment of the application can make different pushing strategies aiming at different types of messages, and push different types of messages according to different pushing strategies, so that diversified pushing requirements are met, and user experience is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a block diagram illustrating a message pushing system according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a message pushing method according to an embodiment of the present application;
fig. 3 is a block diagram illustrating a message pushing apparatus according to another embodiment of the present application;
fig. 4 is a block diagram of an electronic device according to another embodiment of the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below according to the drawings in the embodiments of the present application. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Further, in some flows described in the specification, claims, and above-described figures of the present application, a number of operations are included that occur in a particular order, which operations may be performed out of order or in parallel as they occur herein. The sequence numbers of the operations, e.g., 101, 102, etc., are used merely to distinguish between the various operations, and do not represent any order of execution per se. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.
Before introducing the message pushing method provided by the present application, a system architecture on which the method provided by the present application is based is described.
Fig. 1 shows a block diagram of a message pushing system according to an embodiment of the present application. As shown in fig. 1, the system 10 includes:
a message push server 100 and a terminal 200 in communication connection with the message push server 100;
the message push server 100 is communicatively connected to a plurality of external service systems 20, and is configured to:
determining whether a change occurs in the traffic status of the plurality of external traffic systems 20; when there is an external service system 20 with a changed service state, generating a service message according to the service state change information of the external service system 20 with the changed service state; determining a pushing strategy of the service message according to the type of the service message; and pushing the service message to the terminal 200 according to the pushing strategy.
The message push server 100 may be any device that can provide a computing service and can respond to and process a service request, and may be, for example, a conventional server, a cloud host, a virtual center, or the like. The server mainly comprises a processor, a hard disk, a memory, a system bus and the like, and is similar to a general computer framework. The terminal 200 may be a smart phone, a tablet computer, or the like, which is not particularly limited in this embodiment. The terminal 200 may be one or more.
The server 100 and the terminal 200 may be connected via a wireless or wired network, and the embodiment of the present application is not particularly limited in this respect.
In this embodiment, the server, the terminal, and the specific workflow and signaling interaction between the server and the external service systems in the message pushing system will be further described in the following embodiments.
Fig. 2 shows a flowchart of a message pushing method according to an embodiment of the present application. The execution subject of the method can be a message push server in a message push system. As shown in fig. 2, the method includes:
101. it is determined whether a traffic state of a plurality of external traffic systems has changed.
102. And when an external service system with a changed service state exists, generating a service message according to the service state change information of the external service system with the changed service state.
103. And determining a pushing strategy of the service message according to the type of the service message.
104. And pushing the service message to the terminal according to the pushing strategy.
In the foregoing 101, the plurality of external service systems may include: order management systems, financial management systems, vocational training systems, wind control systems, lead management systems, registration systems, and the like.
In actual application, the message pushing system can determine whether the service states of the plurality of external service systems change by monitoring the service states of the plurality of external service systems; or, the external service system calls a message interface of the message pushing system to inform the message pushing system whether the service state changes.
In the above 102, taking the order management system as an example, when a broker completes the order signing operation between a client and an administrative service, the business status of the broker, the client and the administrative service in the order management system changes, that is, the business status changes from no-sign-on, and the related business status change information may include the broker information, the client information, the administrative service information and the change information about no-sign-on. According to the service state change information, the following information can be generated: a service message regarding the successful endorsement.
Taking the professional training system as an example, after a certain housekeeping service person completes the professional training, the business state of the housekeeping service person in the professional training system changes, that is, the business state changes from unfinished training to finished training, and the related business state change information may include the information of the housekeeping service person and the information of the change from unfinished training to finished training. According to the service state information, the following can be generated: a business message regarding the success of the training, a business message reminding the housekeeping attendant to deliver a resume, etc.
Taking the registration system as an example, when the registration system registers a new client, the service state of the registration system changes, and the relevant service state change information may include information about the new user and change information about the addition of the new client. According to the business state change information, a business message for reminding the new client to fill in the requirement of the home-based service, a business message for recommending the home-based service personnel for the new client, and the like can be generated.
In the above 103, the push policies corresponding to different message types are different. Specifically, the push policy corresponding to each message type may be set according to actual needs.
The push strategy can comprise: push time, push territory and/or push channel, etc. The push channel may include an application message push (push) channel and a short message channel. For each message type, the pushing time, the pushing region and/or the pushing channel in the pushing strategy corresponding to the message type can be determined in a big data mode, so that the viewing rate and the processing rate of the message are improved.
In addition, the push policy may further include whether to loop through a push scheme. For some important message types, a circular push scheme may be configured in its corresponding push policy. Therefore, the message can be repeatedly utilized, the message utilization rate can be improved, and the user experience can be improved.
And 104, pushing the service message to the terminal according to the pushing policy.
In the technical scheme provided by the embodiment of the application, each service system does not need to pay attention to items such as message generation, message pushing and the like, so that the design cost of each service system is reduced, and decoupling of service codes and messages is realized. In addition, the technical scheme provided by the embodiment of the application can make different pushing strategies aiming at different types of messages, and push different types of messages according to different pushing strategies, so that diversified pushing requirements are met, and user experience is improved.
In an implementation scheme, the "pushing the service message to the terminal according to the pushing policy" in the foregoing 104 may be implemented by the following steps:
1041. and determining the pushing time of the service message according to the pushing strategy.
1042. And when the pushing time arrives, storing the service message into a pushing message queue so that a forwarding server can read the message from the pushing message queue and send the message to the terminal.
In 1041, the push time is extracted from the push policy.
1042, a corresponding push message queue and a corresponding forwarding server may be set in advance for each push channel, that is, the number of the push message queues and the number of the forwarding servers are equal to the total number of the push channels. Fig. 1 exemplarily shows a forwarding server 300 corresponding to a push channel and a forwarding server 400 corresponding to a short message channel. The forwarding server may be communicatively coupled to the message push server.
Determining a pushing channel of the business message according to the pushing strategy of the business message; and when the pushing time is up, storing the service message into a pushing message queue corresponding to a pushing channel of the service message, so that a forwarding server corresponding to the pushing channel of the service message reads the message from the pushing message queue and sends the message to a terminal.
For example, if the push channel of the service message is a push channel, when the push time comes, the service message is stored in a push message queue corresponding to the push channel, so that the forwarding server corresponding to the push channel reads the message from the push message queue and sends the message to the terminal in a push manner.
In this embodiment, the message queue is used to implement asynchronous processing, so as to improve system performance and peak clipping, and reduce system coupling.
Further, the "pushing the service message to the terminal according to the pushing policy" in the foregoing 104 may further include the following steps:
1043. and after the service message is read from the push message queue by the forwarding server, determining whether the service message needs to be circularly pushed or not according to a push strategy of the service message.
1044. And if the service message needs to be circularly pushed, determining the next pushing time of the service message.
In 1043, after the forwarding server reads the service message from the push message queue, the forwarding server may notify the message push server through information interaction, so that the message push server may determine whether the service message needs to be pushed circularly according to the push policy of the service message.
In the above 1044, if the service message needs to be circularly pushed, the next pushing time of the service message may be determined according to a pushing interval in a pushing policy of the service message and the last pushing time of the service message.
In the embodiment, the message is recycled, the requirement of service diversification can be met, and the user experience is improved.
In one example, the service message may be stored in the push message queue when the next push time of the service message arrives.
In another example, the "pushing the service message to the terminal according to the pushing policy" in the foregoing 104 may further include the following steps:
1045. and when the next pushing time comes, judging whether the terminal user triggers a specified event to the service message.
1046. And when the terminal user does not trigger the specified event for the service message, storing the service message into the push message queue.
In 1045, the specified event may be a viewing event or a processing event. For example: the service message is a message for reminding the housekeeping service to deliver the resume, and then after the message is sent to the terminal, if the housekeeping service sees the message, the resume delivery event is triggered, and the resume delivery event is also a processing event.
In 1046, if the terminal user does not trigger the specified event for the service message, it indicates that the user ignores the message, and in order to avoid loss of information to the user, the service message may be stored in the push message queue again, so that the forwarding server reads the message from the push message queue and sends the message to the terminal.
If the terminal user triggers the specified event to the service message, the terminal user indicates that the user has viewed or processed the message, so that the service message does not need to be stored in a push message queue.
Optionally, the method may further include:
105. and after the service message is read from the push message queue by the server, determining whether the service message is successfully sent to the terminal.
106. And if the service message is not successful, storing the service message into a failure message queue so that the forwarding server can read the message from the failure message queue and send the message to the terminal.
In this embodiment, the service message with failed push is stored in the failure message queue, so as to avoid message loss.
In an embodiment, the "storing the service message in the failure message queue" in the foregoing 106 may specifically be implemented by the following steps:
1061. and judging the sending failure times of the service message.
1062. And if the sending failure times are less than or equal to a preset time threshold, storing the service message into a failure message queue.
In the 1062, the preset number threshold may be set according to actual needs, which is not specifically limited in the embodiment of the present application.
In this embodiment, the service message with failed push takes a certain number of compensation pushes.
In summary, the technical scheme provided by the embodiment of the application can decouple the service code and the message, and the message is not lost and can be repeatedly used, so that the personalized push rule can be formulated.
Fig. 3 shows a block diagram of a message pushing apparatus according to another embodiment of the present application. As shown in fig. 3, the apparatus includes:
a first determining module 301, configured to determine whether service states of a plurality of external service systems change;
a generating module 302, configured to generate a service message according to service state change information of an external service system with a changed service state when the external service system with a changed service state exists;
a second determining module 303, configured to determine a push policy of the service message according to a type to which the service message belongs;
and the pushing module 304 is configured to push the service message to the terminal according to the pushing policy.
In the technical scheme provided by the embodiment of the application, each service system does not need to pay attention to items such as message generation, message pushing and the like, so that the design cost of each service system is reduced, and decoupling of service codes and messages is realized. In addition, the technical scheme provided by the embodiment of the application can make different pushing strategies aiming at different types of messages, and push different types of messages according to different pushing strategies, so that diversified pushing requirements are met, and user experience is improved.
Optionally, the pushing module 304 is specifically configured to:
determining the pushing time of the service message according to the pushing strategy;
and when the pushing time arrives, storing the service message into a pushing message queue so that a forwarding server can read the message from the pushing message queue and send the message to the terminal.
Optionally, the pushing module 304 is specifically further configured to:
after the service message is read from the push message queue by the forwarding server, determining whether the service message needs to be circularly pushed according to a push strategy of the service message;
and if the service message needs to be circularly pushed, determining the next pushing time of the service message.
Optionally, the pushing module 304 is specifically further configured to:
when the next pushing time comes, judging whether the terminal user triggers a specified event to the service message;
and when the terminal user does not trigger the specified event for the service message, storing the service message into the push message queue.
Optionally, the apparatus further includes: a third determination module;
the third determining module is configured to:
after the service message is read from the push message queue by the server, determining whether the service message is successfully sent to the terminal;
and if the service message is not successful, storing the service message into a failure message queue so that the forwarding server can read the message from the failure message queue and send the message to the terminal.
Optionally, the push policy includes a push region, a push time, and/or a push channel.
Here, it should be noted that: the message pushing device provided in the foregoing embodiments may implement the technical solutions described in the foregoing method embodiments, and the specific implementation principle of each module may refer to the corresponding content in the foregoing method embodiments, which is not described herein again.
Fig. 4 shows a schematic structural diagram of an electronic device provided in an embodiment of the present application. As shown in fig. 4, the electronic device includes a memory 1101 and a processor 1102. The memory 1101 may be configured to store other various data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on the electronic device. The memory 1101 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
The memory 1101 for one or more computer instructions;
the processor 1102, coupled to the memory 1101, is configured to execute the one or more computer instructions stored in the memory 1101 to implement the message pushing method provided by the above method embodiments.
Further, as shown in fig. 4, the electronic device further includes: communication components 1103, display 1104, power components 1105, audio components 1106, and the like. Only some of the components are schematically shown in fig. 4, and the electronic device is not meant to include only the components shown in fig. 4.
Accordingly, the present application further provides a computer-readable storage medium storing a computer program, where the computer program can implement the steps or functions of the message pushing method provided by the foregoing method embodiments when executed by a computer.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (10)
1. A message pushing method, comprising:
determining whether service states of a plurality of external service systems are changed;
when an external service system with a changed service state exists, generating a service message according to the service state change information of the external service system with the changed service state;
determining a pushing strategy of the service message according to the type of the service message;
and pushing the service message to the terminal according to the pushing strategy.
2. The method according to claim 1, wherein pushing the service message to the terminal according to the pushing policy comprises:
determining the pushing time of the service message according to the pushing strategy;
and when the pushing time arrives, storing the service message into a pushing message queue so that a forwarding server can read the message from the pushing message queue and send the message to the terminal.
3. The method according to claim 2, wherein the pushing the service message to the terminal according to the pushing policy further comprises:
after the service message is read from the push message queue by the forwarding server, determining whether the service message needs to be circularly pushed according to a push strategy of the service message;
and if the service message needs to be circularly pushed, determining the next pushing time of the service message.
4. The method according to claim 3, wherein the pushing the service message to the terminal according to the pushing policy further comprises:
when the next pushing time comes, judging whether the terminal user triggers a specified event to the service message;
and when the terminal user does not trigger the specified event for the service message, storing the service message into the push message queue.
5. The method of claim 2, further comprising:
after the service message is read from the push message queue by the forwarding server, determining whether the service message is successfully sent to the terminal;
and if the service message is not successful, storing the service message into a failure message queue so that the forwarding server can read the message from the failure message queue and send the message to the terminal.
6. The method according to any one of claims 1 to 5, wherein the push policy includes push territory, push time and/or push channel.
7. A message push system, comprising: the system comprises a message pushing server and a terminal in communication connection with the message pushing server;
the message pushing server is in communication connection with a plurality of external service systems and is used for:
determining whether a service state of the plurality of external service systems is changed; when an external service system with a changed service state exists, generating a service message according to the service state change information of the external service system with the changed service state; determining a pushing strategy of the service message according to the type of the service message; and pushing the service message to the terminal according to the pushing strategy.
8. A message push apparatus, comprising:
the first determining module is used for determining whether the service states of the plurality of external service systems change or not;
the generating module is used for generating a service message according to the service state change information of the external service system with the changed service state when the external service system with the changed service state exists;
the second determining module is used for determining a pushing strategy of the service message according to the type of the service message;
and the pushing module is used for pushing the service message to the terminal according to the pushing strategy.
9. An electronic device comprising a memory and a processor; the memory is used for storing one or more computer instructions, which when executed by the processor are capable of implementing the steps of the message pushing method of any of the above claims 1-6.
10. A computer-readable storage medium storing a computer program, wherein the computer program is capable of implementing the steps of the message pushing method according to any one of the above claims 1-6 when executed by a computer.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110118745.8A CN112910987A (en) | 2021-01-28 | 2021-01-28 | Message pushing method, system, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110118745.8A CN112910987A (en) | 2021-01-28 | 2021-01-28 | Message pushing method, system, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112910987A true CN112910987A (en) | 2021-06-04 |
Family
ID=76119718
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110118745.8A Pending CN112910987A (en) | 2021-01-28 | 2021-01-28 | Message pushing method, system, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112910987A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113965457A (en) * | 2021-09-27 | 2022-01-21 | 山东浪潮通软信息科技有限公司 | Message notification method and device |
| CN114710556A (en) * | 2022-06-08 | 2022-07-05 | 深圳市信润富联数字科技有限公司 | Multi-system integrated message pushing method, device, equipment and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120084217A1 (en) * | 2010-09-30 | 2012-04-05 | Avaya Inc. | System and method for responding to changing conditions in contact centers |
| CN104158724A (en) * | 2014-08-21 | 2014-11-19 | 广州唯品会网络技术有限公司 | Message pushing method and system |
| CN105323205A (en) * | 2014-05-30 | 2016-02-10 | 中兴通讯股份有限公司 | Message pushing processing method, message pushing processing device, pushing server and application server |
| CN108183933A (en) * | 2017-12-04 | 2018-06-19 | 深圳开思时代科技有限公司 | Information push method, apparatus and system, electronic equipment and computer storage media |
| CN108595085A (en) * | 2018-04-03 | 2018-09-28 | Oppo广东移动通信有限公司 | A kind of information processing method, electronic equipment and storage medium |
| CN110912980A (en) * | 2019-11-19 | 2020-03-24 | 北京三快在线科技有限公司 | Order state synchronization method, system and storage medium |
| CN111614718A (en) * | 2020-04-10 | 2020-09-01 | 广州市玄武无线科技股份有限公司 | Enterprise communication channel fusion method, device, equipment and readable storage medium |
| CN111917687A (en) * | 2019-05-08 | 2020-11-10 | 北京京东振世信息技术有限公司 | Method and device for circularly pushing reminding message |
-
2021
- 2021-01-28 CN CN202110118745.8A patent/CN112910987A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120084217A1 (en) * | 2010-09-30 | 2012-04-05 | Avaya Inc. | System and method for responding to changing conditions in contact centers |
| CN105323205A (en) * | 2014-05-30 | 2016-02-10 | 中兴通讯股份有限公司 | Message pushing processing method, message pushing processing device, pushing server and application server |
| CN104158724A (en) * | 2014-08-21 | 2014-11-19 | 广州唯品会网络技术有限公司 | Message pushing method and system |
| CN108183933A (en) * | 2017-12-04 | 2018-06-19 | 深圳开思时代科技有限公司 | Information push method, apparatus and system, electronic equipment and computer storage media |
| CN108595085A (en) * | 2018-04-03 | 2018-09-28 | Oppo广东移动通信有限公司 | A kind of information processing method, electronic equipment and storage medium |
| CN111917687A (en) * | 2019-05-08 | 2020-11-10 | 北京京东振世信息技术有限公司 | Method and device for circularly pushing reminding message |
| CN110912980A (en) * | 2019-11-19 | 2020-03-24 | 北京三快在线科技有限公司 | Order state synchronization method, system and storage medium |
| CN111614718A (en) * | 2020-04-10 | 2020-09-01 | 广州市玄武无线科技股份有限公司 | Enterprise communication channel fusion method, device, equipment and readable storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113965457A (en) * | 2021-09-27 | 2022-01-21 | 山东浪潮通软信息科技有限公司 | Message notification method and device |
| CN114710556A (en) * | 2022-06-08 | 2022-07-05 | 深圳市信润富联数字科技有限公司 | Multi-system integrated message pushing method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108513271B (en) | Short message distribution method and device based on multiple short message channels | |
| CN111555963B (en) | Message pushing method and device, electronic equipment and storage medium | |
| CN111756601B (en) | Microservice architecture monitoring method and device, computer equipment and readable storage medium | |
| CN108631955A (en) | It is a kind of to ensure that message sends reachable mthods, systems and devices | |
| CN104579905A (en) | Message passing method and system, MOM (message oriented middleware) server and receiving terminal | |
| CN112367345B (en) | Data processing method, server device and computer readable storage medium | |
| CN112910987A (en) | Message pushing method, system, device, equipment and storage medium | |
| CN111131368A (en) | Message pushing method and device | |
| CN114268957A (en) | Abnormal business data processing method, device, server and storage medium | |
| US11544119B2 (en) | Business rules processing framework for implementing new desired functionality in a telecommunication application | |
| US20070050447A1 (en) | Method and device arrangement for managing a client/server environment | |
| CN113031997A (en) | Upgrade package generation and management method and device, computer equipment and storage medium | |
| CN113347238A (en) | Message partitioning method, system, device and storage medium based on block chain | |
| US20230259930A1 (en) | Cross-chain transaction processing method and apparatus, electronic device, and storage medium | |
| CN111324459A (en) | Calendar-based resource scheduling method and device, electronic equipment and storage medium | |
| CN115951923A (en) | Subscription event management method and related product | |
| CN114338534A (en) | Message routing method and device | |
| CN111401819B (en) | Intersystem data pushing method and system | |
| CN115640084A (en) | System message sending method and device for client | |
| CN112101810A (en) | Risk event control method, device and system | |
| CN111432357B (en) | Information processing method and system and computing equipment | |
| CN104936155B (en) | A kind of processing method and processing device of SMS signature | |
| CN111611123A (en) | Data processing method, data processing system and equipment | |
| CN112434241A (en) | Service processing method, computer device and storage medium | |
| WO2020003320A1 (en) | System and method for managing notification requests in a communication network |
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: 20210604 |