WO2015180339A1

WO2015180339A1 - Message push processing method and device, push server, and application server

Info

Publication number: WO2015180339A1
Application number: PCT/CN2014/087614
Authority: WO
Inventors: 季健; 潘道华
Original assignee: 中兴通讯股份有限公司
Priority date: 2014-05-30
Filing date: 2014-09-26
Publication date: 2015-12-03
Also published as: CN105323205A

Abstract

The present invention provides a message push processing method and device, a push server, and an application server. The method comprises: acquiring a push message to be pushed; determining a target terminal to which the push message is to be pushed; and pushing the push message to the target terminal in a User Datagram Protocol (UDP) message mode. The present invention solves the problems in the related art that the performance consumption is large and the push efficiency is low when a server pushes a message to a terminal by using an HTTP protocol, so the system performance consumption is reduced, and the push efficiency is improved.

Description

Message push processing method, device, push server and application server

Technical field

The present invention relates to the field of communications, and in particular, to a message push processing method, apparatus, push server, and application server.

Background technique

At present, in many applications, the server needs to send messages to the client actively. The early implementation technology is that the client continuously refreshes the server to obtain the latest data through polling technology. This method needs to establish a new one each time. The Hypertext Transfer Protocol (HTTP) connection has a certain delay, which makes the application of frequent information transmission unbearable. The most recent server push technology is that the client and the server maintain a persistent connection. The server can send information to the client at any time through the connection. However, for this HTTP long connection, when the number of terminals in the system is large, the server side needs to maintain A large number of HTTP long connections, the performance of the server is relatively large, and the number of terminals that can be served by one server will decrease.

Therefore, in the related art, the server uses the HTTP protocol to push messages to the terminal, which has a large performance cost and a low push efficiency.

Summary of the invention

The present invention provides a message push processing method and apparatus, a push server, and an application server, so as to at least solve the problem that the server uses the HTTP protocol to push messages to the terminal, and the performance of the server is high, and the push efficiency is low.

According to an aspect of the present invention, a message push processing method is provided, including: acquiring a push message for pushing; determining a target terminal to which the push message is pushed; and using the user datagram protocol UDP message to push the push The message is pushed to the target terminal.

Preferably, the pushing the push message to the target terminal by using the UDP message includes: after pushing the push message to the target terminal, determining whether the target terminal is received within a predetermined time And a reply response message for determining that the push message is received; if the determination result is no, the push message is re-pushed to the target terminal.

Preferably, after the push message is sent to the target terminal, determining whether the response message sent by the target terminal for determining that the push message is received is received in the predetermined time includes: After the push message is pushed to the target terminal, the push message is stored in an ordered queue; when the reply response message of the push message is received, the push message is sent from the ordered Deleting the queue; determining whether the push message is scanned within the predetermined time; if the determination result is yes, determining that the push message is pushed to the target terminal fails.

According to another aspect of the present invention, a message push processing method is provided, comprising: broadcasting a push message to one or more push servers; and receiving, by the one or more push servers, a reply message of the push message, The one or more push servers use the user datagram protocol UDP message to push the push message to the terminal.

Preferably, before the transmitting the push message to the one or more push servers, the method further includes: a terminal that allocates a push message to the one or more push servers according to a predetermined load balancing condition.

Preferably, after the received one or more push servers push the reply message of the push message, the method further includes: determining, according to the reply message, that the offline terminal has failed to push the message; And storing the push message and the offline terminal that failed to push the push message; determining whether the original push server corresponding to the offline terminal is in a suspended state when the offline terminal is online again. In the case where the determination result is YES, the push message is pushed by the new push server allocated for the offline terminal that is online again; and/or, if the determination result is negative, the original push server is adopted. Pushing the push message for the offline terminal that is online again.

According to still another aspect of the present invention, a message push processing apparatus is provided, comprising: an obtaining module configured to acquire a push message for pushing; a determining module configured to determine a target terminal to which the push message is pushed; and a first push The module is configured to use the user datagram protocol UDP message to push the push message to the target terminal.

Preferably, the first pushing module includes: a determining unit, configured to determine, after the pushing the push message is sent to the target terminal, whether the received by the target terminal is received within a predetermined time for determining the received location a reply response message for the push message; the push unit is configured to re-push the push message to the target terminal if the determination result of the determination unit is negative.

Preferably, the determining unit comprises: a storage subunit, configured to: after pushing the push message to the target terminal, store the push message in an ordered queue; delete the subunit, and set to receive And when the reply response message of the push message is sent, the push message is deleted from the ordered queue; and the determining subunit is configured to determine whether the push message is scanned within the predetermined time; The unit is configured to determine that the push message is failed to be pushed to the target terminal if the determination result of the determination subunit is YES.

According to still another aspect of the present invention, a push server is provided, comprising the apparatus of any of the above.

According to still another aspect of the present invention, a message push processing apparatus is provided, comprising: a broadcast module configured to broadcast a push message to one or more push servers; and a receiving module configured to receive the one or more pushes The server pushes the reply message of the push message, wherein the one or more push servers use the user datagram protocol UDP message to push the push message to the terminal.

Preferably, the apparatus further comprises: an allocation module configured to allocate a push message to the one or more push servers according to a predetermined load balancing condition.

Preferably, the device further includes: a second determining module, configured to determine, according to the reply message, that the offline terminal has failed to push the message; and the storage module is configured to be in a case that the determination result of the second determining module is yes And storing the push message and the offline terminal that failed to push the push message; the third determining module is configured to determine whether the original push server corresponding to the offline terminal is when the offline terminal is online again In a suspended state, the second push module is configured to push the push message by a new push server allocated for the offline terminal that is online again when the determination result of the third determination module is YES; and Or, the third push module is configured to: when the determination result of the third determination module is negative, use the original push server to push the push message for the offline terminal that is online again.

According to still another aspect of the present invention, an application server is provided, comprising the apparatus of any of the above.

The method of the present invention is to obtain a push message for push, determine a target terminal to which the push message is pushed, and push the push message to the target terminal by using a user datagram protocol UDP message, thereby solving the related art. The server uses the HTTP protocol to push messages to the terminal, which has high performance consumption and low push efficiency, thereby achieving the effect of reducing system performance consumption and improving push efficiency.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

1 is a flowchart of a first method of message push processing according to an embodiment of the present invention;

2 is a flowchart of a second method for message push processing according to an embodiment of the present invention;

FIG. 3 is a structural block diagram of a message push processing apparatus 1 according to an embodiment of the present invention; FIG.

FIG. 4 is a block diagram showing a preferred structure of the first push module 36 in the message push processing apparatus 1 according to an embodiment of the present invention;

FIG. 5 is a block diagram showing a preferred structure of the determining unit 42 in the first push module 36 in the message push processing apparatus 1 according to an embodiment of the present invention;

6 is a structural block diagram of a push server according to an embodiment of the present invention;

FIG. 7 is a structural block diagram of a message push processing apparatus 2 according to an embodiment of the present invention;

8 is a block diagram 1 of a preferred structure of a message push processing apparatus 2 according to an embodiment of the present invention;

9 is a block diagram 2 of a preferred structure of a message push processing apparatus 2 according to an embodiment of the present invention;

FIG. 10 is a structural block diagram of an application server according to an embodiment of the present invention; FIG.

11 is a block diagram of a distributed message push system employing a UDP protocol according to an embodiment of the present invention;

12 is a flow chart of a message push method in accordance with a preferred embodiment of the present invention.

detailed description

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

In the embodiment, a message push processing method is provided. FIG. 1 is a flowchart of a message push processing method according to an embodiment of the present invention. As shown in FIG. 1 , the process includes the following steps:

Step S102, acquiring a push message for pushing;

Step S104, determining a target terminal to which the push message is pushed;

Step S106: Push the push message to the target terminal by using a user datagram protocol UDP message.

Through the above steps, for the push server, the push message is pushed to the target terminal by means of the UDP message, and the message is pushed by using the HTTP message in the related art, which not only solves the problem that the HTTP protocol pushes the message to the terminal in the related art. There is a problem of high performance consumption and low push efficiency, which in turn reduces the system performance consumption and improves the push efficiency.

In order to ensure the success of the push, when the push message is pushed to the target terminal by using the UDP message, the following processing may be adopted: after the push message is pushed to the target terminal, it is determined whether the target terminal is sent within a predetermined time. After determining that the response message of the push message is received; when receiving the reply response message of the push message fed back by the target terminal within a predetermined time, it may be determined that the push message is successful. If the result of the determination is negative, the message is pushed back to the target terminal. It should be noted that the above determining step may be used for confirmation multiple times, and when the reply response message of the target terminal is not received multiple times, the message push to the target terminal is discarded.

After the push message is sent to the target terminal, it is determined whether the response message sent by the target terminal for determining the received push message is received in a predetermined time, and the processing may be performed by using a message queue. The method is completed: after the push message is pushed to the target terminal, the push message is stored in an ordered queue; when the reply response message of the push message is received, the push message is deleted from the ordered queue; Whether the push message is scanned within the predetermined time; if the result of the determination is yes, it is determined that the push of the message to the target terminal has failed.

In this embodiment, a message push processing method is also provided. FIG. 2 is a flowchart of a message push processing method 2 according to an embodiment of the present invention. As shown in FIG. 2, the process includes the following steps:

Step S202, broadcasting a push message to one or more push servers;

Step S204: The one or more push servers push the reply message of the message, wherein the one or more push servers use the user datagram protocol UDP message to push the push message to the terminal.

Through the above steps, for the application server, by pushing the push message to one or more push servers, and then the one or more push servers push the push message to the target terminal by means of the UDP message, compared with the related art. Pushing messages by means of HTTP messages not only effectively solves the problem that the HTTP protocol pushes messages to the terminal in the related art, and the push efficiency is low, thereby achieving the effect of reducing system performance consumption and improving push efficiency.

Preferably, before the push message is broadcast to one or more push servers, the terminal that pushes the message may be allocated to one or more push servers according to the predetermined load balancing condition, so that the system performance is balanced, and collision and waste are effectively avoided.

Whether the terminal receives the push message, or to ensure that the terminal receives the push message, after receiving the reply message of the one or more push servers to push the message, according to the reply message, determining that the message push failure is offline. If the result of the determination is yes, the application server saves the push message and pushes the offline terminal that failed to push the message; after that, it determines that the offline terminal ends when the offline terminal goes online again. Whether the original push server corresponding to the end is in a suspended state (ie, the original push server no longer pushes the push message to the terminal); if the judgment result is yes, the push message is pushed by the new push server allocated for the offline terminal that is online again. And/or, if the judgment result is no, the original push server is used to push the push message for the offline terminal that is online again. Through the above processing, the problem that the offline terminal that does not receive the push message is received in the related art, and the original push message cannot be received when it is online and assigned to the new push server is successfully implemented, and the offline terminal is successfully implemented. Re-pushing, to a certain extent, improves the user experience.

In the embodiment, a message push processing device is also provided, which is used to implement the above-mentioned embodiments and preferred embodiments, and has not been described again. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 3 is a structural block diagram of a message push processing apparatus 1 according to an embodiment of the present invention. As shown in FIG. 3, the apparatus includes an obtaining module 32, a determining module 34, and a first pushing module 36. The apparatus will be described below.

The obtaining module 32 is configured to obtain a push message for pushing; the determining module 34 is connected to the obtaining module 32, and is configured to determine a target terminal that pushes the push message; the first pushing module 36 is connected to the determining module 34, and is configured to The push message is pushed to the target terminal by means of the user datagram protocol UDP message.

FIG. 4 is a block diagram showing a preferred structure of the first push module 36 in the message push processing apparatus 1 according to the embodiment of the present invention. As shown in FIG. 4, the first push module 36 includes a determining unit 42 and a pushing unit 44. The first push module 36 will be described.

The determining unit 42 is configured to: after receiving the push message to the target terminal, determine whether a response message for determining to receive the push message sent by the target terminal is received within a predetermined time; the pushing unit 44 is connected to the determining unit 42 When the determination result of the above-described determination unit 42 is NO, the message is re-pushed to the target terminal.

FIG. 5 is a block diagram showing a preferred structure of the determining unit 42 in the first push module 36 in the message push processing apparatus 1 according to the embodiment of the present invention. As shown in FIG. 5, the determining unit 42 includes a storage subunit 52 and a delete subunit 54. The judging subunit 56 and the determining subunit 58 are described below.

The storage subunit 52 is configured to store the push message in an ordered queue after pushing the push message to the target terminal; the delete subunit 54 is connected to the storage subunit 52, and is set to receive the reply of the push message. In response to the message, the push message is deleted from the ordered queue; the determining sub-unit 56 is coupled to the delete sub-unit 54 and configured to determine whether a push message is scanned within a predetermined time; the determining sub-unit 58 is connected to the above determination The subunit 56 is arranged to determine that the push message is pushed to the target terminal fails in the case where the judgment result of the judgment subunit is YES.

FIG. 6 is a structural block diagram of a push server according to an embodiment of the present invention. As shown in FIG. 6, the push server 60 includes the message push processing device one 62 of any of the above.

FIG. 7 is a structural block diagram of a message push processing apparatus 2 according to an embodiment of the present invention. As shown in FIG. 7, the apparatus includes a broadcast module 72 and a receiving module 74, which will be described below.

The broadcast module 72 is configured to broadcast a push message to one or more push servers; the receiving module 74 is connected to the broadcast module 72, and is configured to receive a reply message of the one or more push servers to push the push message, wherein one or The plurality of push servers use the user datagram protocol UDP message to push the push message to the terminal.

FIG. 8 is a block diagram of a preferred structure of a message push processing apparatus 2 according to an embodiment of the present invention. As shown in FIG. 8, the apparatus includes an allocating module 82 in addition to all the structures shown in FIG. Module 82 is described.

The distribution module 82 is coupled to the broadcast module 72 and configured to allocate a push message to one or more push servers in accordance with predetermined load balancing conditions.

FIG. 9 is a block diagram of a preferred structure of a message push processing apparatus 2 according to an embodiment of the present invention. As shown in FIG. 9, the apparatus includes a second judging module 90 and a storage module 92, in addition to all the structures shown in FIG. The third judging module 94, the second pushing module 96 and/or the third pushing module 98, will be described below.

The second determining module 90 is connected to the receiving module 74, and is configured to determine, according to the reply message, that the offline terminal has failed to push the message; the storage module 92 is connected to the second determining module 90, and is set to be determined by the second determining module. If the result is YES, the push message is saved, and the push-down terminal fails to push the push message; the third determination module 94 is connected to the storage module 92, and is configured to determine that the offline terminal corresponds to the original when the offline terminal is online again. Whether the push server is in a suspended state; the second push module 96 is connected to the third determining module 94, and is configured to allocate a new offline terminal for the online terminal when the third determination module determines that the result is yes. Pushing the server push message; and/or, the third pushing module 98 is connected to the third determining module 94, and is configured to use the original push server as the offline line when the third determining module determines that the result is negative. The terminal pushes the message.

FIG. 10 is a structural block diagram of an application server according to an embodiment of the present invention. As shown in FIG. 10, the application server 100 includes the message push processing device two 102 of any of the above.

In the related art, the server adopts the problem that the performance of the push message to the terminal is high, and the push efficiency is low. Because the traditional HTTP protocol is adopted, the server performance pressure is high, and the number of users that can be served is reduced. In the related art, the message pushing system based on the Transmission Control Protocol (TCP) method uses the User Datagram Protocol (User Datagram Protocol) to push messages, which reduces the performance of the server. , improve the server's message push capabilities. In the distributed message push scheme based on the UDP protocol, since the UDP protocol is a connectionless protocol, the push server does not need to maintain a large number of connections, and the performance consumption is much lower than that of the HTTP method. At the same time, the system is distributed and can support a large number of users. (that is, the throughput of the server is greatly increased), and the fault tolerance is also better. When a server is hanged, the user's service is not affected.

11 is a block diagram of a distributed message push system employing a UDP protocol, as shown in FIG. 11, the system includes a management platform 112, an access server 114, one or more push servers 116, and one or more, in accordance with an embodiment of the present invention. Terminals 118, the system will be described below.

The management platform 112: provides a web interface for the operator to operate, and the operator can select which terminals or a certain type of terminal to send messages through the web interface.

The access server 114: assumes three functions, one is as a manager, the message push server in the management system, the message push server is distributed, there may be multiple in the system, and multiple push servers are managed by the access server; The second is to load balance the terminal. When the terminal accesses the message push system, it first loads the load to the access server, and the access server allocates a push server to the terminal. The third is between the management platform and the message push server. The transit module sends a message to the access server when the message is to be pushed to the terminal, and the access server broadcasts the message to the push server.

The push server 16: directly interacts with the terminal, and is mainly responsible for management of terminal data and message push to the terminal. The terminal receives the registration message of the terminal, maintains the related information of the terminal, and receives the heartbeat message of the terminal, and maintains the online state information of the terminal. If the heartbeat message of the terminal is not received within a certain period of time, the terminal is placed in an offline state. When a message needs to be pushed, the push server generates a corresponding push message according to the message size and the target terminal, and pushes the push message to the terminal.

It should be noted that the system can be deployed independently with the IPTV service system. The source of the system can have two aspects, one is that the operator operates on the management platform, and the IPTV service system can also send the interface to the access server through the interface. The IPTV system sends a message push request. After the access server of the message system receives the push message request, since the access server does not save the load balancing result of the terminal, it does not know which push servers the target terminal is allocated on, so access The server can only broadcast the push request to all the push servers, and each push server determines whether the push terminal is on the server, and if so, obtains the relevant target terminal. Information, message push to the target terminal, and if not, the reply access server target terminal does not exist. For the message push, if the push is successful, the access server is successfully sent back to the access server. Otherwise, the list of the terminals that failed to push is returned, and the access server aggregates the reply information of each push server and returns the push result to the service system or the management platform.

The push server uses the UDP protocol for message push. Considering the characteristics of UDP transmission, for a message of 1K size, the message needs to be fragmented, and one message is divided into multiple fragments and pushed to the terminal, and the APP application of the terminal receives the score. After the piece of data, the message is assembled and restored to the original message. The message pushed by the push server to the terminal includes: the ID of the message, the total size of the message, the total number of fragments of the message, the index of the message (that is, the first fragment belonging to the original message), the actual fragmentation data, and the terminal is After receiving the UDP message, it is determined according to the message header whether the message is complete. If there is more than one fragmented data, after the plurality of fragmented data is received, the header is removed, and the message body in the fragmented data is assembled into A completed original message.

For the push message received by the push server, the push server stores the message in the original message queue. The push server needs to process the original message queue, generate a message queue to be sent, and then send the message in the message queue for transmission. IPTV message push is divided into various forms, for example, network-wide user push, single or multiple specified user push, push by user group, push by IP address segment, push by user level, etc., so the original message is sent by the specified user. In addition, other push methods require the push server to generate a target terminal list. The user's grouping, level, and other information are reported to the push server when the terminal registers with the push server. The push server establishes a relevant index based on the user information, for example, a specified user. When the packet is pushed, the push server finds all the users belonging to the packet according to the user group index, thereby generating a target terminal list. In addition, the message is fragmented, and a single fragment and a single terminal generate a mapping relationship between the message and the terminal to be sent. The mapping relationship is added to the message queue to be sent, the push server scans the queue, and the received message is sent to the corresponding terminal.

The timeout and retransmission management of the push message: The UDP protocol is an unreliable protocol. Packet loss may occur during the transmission process. Therefore, for each push message, the terminal needs to respond to ensure that the message is successfully pushed. After the UDP message is sent out, the message is moved from the queue to be sent to an ordered queue. The ordering criterion is the time when the message is sent. When the terminal replies to the response message, the push system will correspondingly from the ordered queue. The push message is deleted. The push system periodically scans the ordered queue, traverses from the beginning, compares the original time with the message sending time, and if the timeout period is exceeded, the message is re-inputted into the message queue to be sent, and the push system resends the message. A maximum number of retransmissions is set for each message. When the number of retransmissions exceeds the maximum number of retransmissions, the retransmission is not repeated, and the status of the message transmission is set to failure.

After the offline user goes online, the message is re-pushed: for the message that needs to push the message, the high-level push message must be pushed to the terminal. Even if the terminal goes offline, the push message is retained, and after the terminal goes online, The push server needs to re-send the message to the terminal, and for the low level, if the push fails, the push is canceled and the push is no longer pushed. However, if the message of the failed push is saved and re-pushed, the failure message cannot be simply saved on the push server that failed to push. This is because the offline terminal is re-launched, and if the number of push servers changes during this period, When the terminal is re-online, it may be assigned to another push server, and the push server is successful because the last message is pushed, so the message is no longer retained, so that the previous offline message can no longer be used. Push to the terminal. Therefore, in this embodiment, for the terminal that fails to be pushed, the access server saves after receiving the report from the push server. When the offline terminal comes back online, the load server must first be load balanced, and the access server will be in itself. The list of terminals that failed to be pushed is queried whether the terminal is located therein. If not, a push server is directly allocated to the terminal, and if so, the access server fails to push the push server while assigning the push server to the terminal. The message is sent to the assigned push server, so that when the terminal registers with the push server, the push server resends the last failed push message to the terminal.

In the distributed message pushing system provided by the embodiment of the present invention, the access server may also serve as a message portal, and broadcast the original message to the push server, and the push server queries the target terminal according to the target terminal to be pushed in the original message. The related information of the terminal is pushed to the target terminal through the UDP protocol.

The IPTV message-based IPTV message push solution provided by the foregoing embodiment and the preferred embodiment not only effectively solves the problem of excessive server performance consumption caused by the HTTP connection mode, but also solves the problem that when the terminal goes offline, the push fails. When the terminal is back online, the number of push servers changes, and the terminal is load balanced to another push server, which causes the message that the last push failure can no longer be pushed again.

A preferred embodiment of the present invention will now be described.

FIG. 12 is a flowchart of a message pushing method according to a preferred embodiment of the present invention. As shown in FIG. 12, the process includes the following steps:

Step S1202: After the startup, the push server establishes a long connection with the access server, and reports its own information to the access server.

Step S1204: The push server periodically sends a heartbeat to the access server to maintain a long connection between the server and the access server;

Step S1206: After the terminal starts the application of the IPTV app, the terminal registers with the message system, and reports its own related information to the push server.

Step S1208: The terminal periodically sends a UDP heartbeat to the push server to maintain its online state.

Step S1210: The management platform or the service system pushes the message that needs to be pushed to the access server.

Step S1212: The access server broadcasts the message that needs to be pushed to the push server.

Step S1214: After receiving the push request, the push server performs corresponding processing: the push server queries the terminal terminal to maintain the related information of the target terminal, and if not, the reply server returns the target terminal does not exist; After the target terminal information, the original message larger than 1K is fragmented, and a one-to-one correspondence between the fragment and the push terminal is generated, and is put into the message queue to be sent;

Step S1216: The push server waits for the message in the sent message queue to be pushed to the terminal through the UDP protocol;

Step S218, after receiving the UDP message, the terminal responds to the push server and determines whether the packet is complete. If it is complete, the terminal returns to the original message.

Step S1220: The push server determines whether to resend the UDP message according to whether the response is received within the timeout period;

Step S1222: The push server returns the push result to the access server, and after receiving the reply message of all the push servers, the access server returns the result to the management platform or the IPTV service system, and for the high-level push message, because it is the terminal If the push fails due to offline, the access server will save the push failed terminal list. When the terminal is back online, the access server will resend the message to the push server assigned to the terminal, so that the push server can re-send the message. Go on.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

As described above, the foregoing embodiments and preferred embodiments solve the problem that the server uses the HTTP protocol to push messages to the terminal, which has high performance consumption and low push efficiency, thereby reducing system performance consumption and improving push. The effect of efficiency.

Claims

A message push processing method includes:

Get push messages for push;

Determining a target terminal to which the push message is pushed;

The push message is pushed to the target terminal by using a user datagram protocol UDP message.
The method of claim 1, wherein the pushing the push message to the target terminal by using the UDP message comprises:

After the push message is sent to the target terminal, it is determined whether a response response message sent by the target terminal for determining that the push message is received is received within a predetermined time;

If the result of the determination is negative, the push message is re-introduced to the target terminal.
The method according to claim 2, wherein after the push message is pushed to the target terminal, it is determined whether the received message sent by the target terminal is received within the predetermined time for determining to receive the push message. The reply response message includes:

After pushing the push message to the target terminal, storing the push message in an ordered queue;

And when the reply response message of the push message is received, deleting the push message from the ordered queue;

Determining whether the push message is scanned within the predetermined time;

In the case where the determination result is YES, it is determined that the push message is pushed to the target terminal.
A message push processing method includes:

Broadcast push messages to one or more push servers;

The received one or more push servers push the reply message of the push message, wherein the one or more push servers push the push message to the terminal by using a user datagram protocol UDP message.
The method of claim 4, further comprising: before broadcasting the push message to the one or more push servers:

A terminal that allocates a push message to the one or more push servers in accordance with a predetermined load balancing condition.
The method according to claim 4 or 5, wherein after the received one or more push servers push the reply message of the push message, the method further includes:

Determining, according to the reply message, that the offline terminal that has failed to push the message;

If the determination result is yes, the push message is saved, and the offline terminal that fails to push the push message is sent;

Determining whether the original push server corresponding to the offline terminal is in a suspended state when the offline terminal is online again;

If the determination result is YES, the push message is pushed by the new push server allocated to the offline terminal that is online again; and/or, if the determination result is negative, the original push server is adopted. The offline terminal that is online again pushes the push message.
A message push processing device includes:

Obtaining a module, configured to obtain a push message for pushing;

Determining a module, configured to determine a target terminal to which the push message is pushed;

The first pushing module is configured to use the user datagram protocol UDP message to push the push message to the target terminal.
The apparatus of claim 7, wherein the first push module comprises:

a determining unit, configured to determine, after the push message is pushed to the target terminal, whether a response message sent by the target terminal for determining to receive the push message is received within a predetermined time;

The push unit is configured to re-push the push message to the target terminal when the determination result of the determination unit is negative.
The apparatus according to claim 8, wherein said determining unit comprises:

a storage subunit, configured to store the push message in an ordered queue after pushing the push message to the target terminal;

Deleting a subunit, configured to delete the push message from the ordered queue when receiving the reply response message of the push message;

a determining subunit, configured to determine whether the push message is scanned within the predetermined time;

The determining subunit is set to determine that the push message to the target terminal fails to be sent if the judgment result of the judging subunit is YES.
A push server comprising the apparatus of any one of claims 7 to 9.
A message push processing device includes:

a broadcast module configured to broadcast a push message to one or more push servers;

a receiving module, configured to receive, by the one or more push servers, a reply message of the push message, where the one or more push servers adopt a user datagram protocol UDP message to send the push message Push to the terminal.
The device according to claim 11, further comprising:

And an allocation module, configured to allocate a push message to the one or more push servers according to a predetermined load balancing condition.
The device according to claim 11 or 12, further comprising:

a second determining module, configured to determine, according to the reply message, that the offline terminal that has failed to push the message;

a storage module, configured to save the push message and the offline terminal that fails to push the push message if the determination result of the second determination module is YES;

The third determining module is configured to determine whether the original push server corresponding to the offline terminal is in a suspended state when the offline terminal is online again;

a second pushing module, configured to: when the determination result of the third determining module is YES, push the push message by a new push server allocated for the offline terminal that is online again; and/or, third The push module is configured to: when the determination result of the third determination module is negative, use the original push server to push the push message for the offline terminal that is online again.
An application server comprising the apparatus of any one of claims 11 to 13.