CN103874035B - A kind of Mobile terminal message push method and equipment - Google Patents

Abstract

The invention discloses a mobile terminal message push method and device. The method comprises: after the mobile terminal receives the short message pushed by the short message gateway, distributes the short message to the application program of the mobile terminal, and detects the connection between the device and the push server. Whether the long-term connection channel is established; if the long-term connection channel between the device and the push server is not established, it will initiate a request to the push server to establish a long-term connection channel, and maintain the long-term connection channel after the long-term connection channel is established; among them, the short The message is pushed by the push server through the short message gateway when the long connection channel between itself and the mobile terminal has not been established, or when the push message to the mobile terminal fails through the long connection channel; when the long connection configured on the mobile terminal is dormant When the event is triggered and a long connection channel is established between the device and the push server, the mobile terminal disconnects the long connection channel between the device and the push server.

Description

A mobile terminal message push method and device

technical field

The present invention relates to the technical field of communication networks, in particular to a mobile terminal message pushing method and device.

Background technique

The mobile terminal push service refers to the service in which the server directs information to the mobile terminal in real time. The principle of the mobile terminal push service is very simple, that is, by establishing a connection link between the mobile terminal and the server, when there is a push message to be sent to the mobile terminal, it can be sent through this link.

Existing mobile terminal message push solutions can be mainly divided into the following two categories:

1. Realize message push through short message. The server sends a short message in a special format to the push service client of the mobile terminal, and the client intercepts and parses the short message to obtain the content of the message, or through the instruction or URL (Uniform/Universal Resource Locator, unified resource locator) for more content. WAP-PUSH (push information) is implemented using a similar mechanism.

2. Realize message push by establishing TCP (Transmission Control Protocol, Transmission Control Protocol) long connection. The push service client of the mobile terminal will always maintain a TCP long connection with the server to realize the real-time arrival of the message. Long-term connections are generally implemented through HTTP (HTTP-Hypertext transfer protocol, hypertext transfer protocol) Long-pull (long connection), that is, the client cycle initiates HTTP requests with a certain period of time (such as 10 minutes), and establishes with the server After the connection, the server is in a waiting state. When there is a message to be pushed, the server returns the message to be pushed to the client.

In practical applications, the message push is implemented between the server and the mobile terminal in one way, that is, through the short message method or the TCP long connection method, and these two message push methods have their own problems:

1. The mobile terminal message push based on the short message generally needs the support of the short message gateway of the mobile operator, so the cost is relatively high. Moreover, the short message method has limitations such as small data capacity and long transmission delay, and is not suitable for scenarios with high sending frequency, large data volume, and high real-time requirements.

2. The mobile terminal message push based on the long connection method will increase the power consumption of the mobile terminal, especially when the network condition is not good, the reconnection mechanism of the mobile terminal itself will double the power consumption and cause Push message arrival delay. In addition, the persistent connection method consumes too many server-side connection resources, so that the number of mobile terminal clients that each server can serve is relatively small.

Therefore, there is an urgent need for a mobile terminal message push solution to solve the above technical problems.

Contents of the invention

The embodiment of the present invention provides a mobile terminal message pushing method and device, which are used to enhance the flexibility of the mobile terminal message pushing and the adaptability to the network environment.

In order to achieve the above purpose, the embodiment of the present invention adopts the following technical means:

An embodiment of the present invention provides a mobile terminal message push method, the method comprising:

After the mobile terminal receives the short message pushed by the short message gateway, the short message is distributed to the application program of the mobile terminal, and detects whether the long connection channel between the device and the push server is established; If the long connection channel is not established, a request for establishing a long connection channel is initiated to the push server, and the long connection channel is maintained after the long connection channel is established; wherein, the short message is between the push server and the The long connection channel between the mobile terminals is not established, or, in the case of failure to push the message to the mobile terminal through the long connection channel, it is pushed through the short message gateway;

When the long connection dormancy event configured on the mobile terminal is triggered, and a long connection channel is established between the device and the push server, the mobile terminal disconnects the long connection between the device and the push server aisle.

The embodiment of the present invention also provides a mobile terminal, including: a receiving module, a distribution module, a processing module, and a transceiver module;

The receiving module is used to receive the short message pushed by the short message gateway; wherein, the short message is that the long connection channel between the push server and the mobile terminal has not been established, or the long connection channel is sent to the mobile terminal through the long connection channel In the case that the mobile terminal fails to push the message, it is pushed through the short message gateway;

A distribution module, configured to distribute the short message received by the receiving module to the application program of the mobile terminal;

The processing module is used to detect whether the long connection channel between the device and the push server is established, if not established, send a request for establishing a long connection channel to the push server through the transceiver module, and after the long connection channel is established Keep the long connection channel; otherwise, keep the long connection channel; and, when the long connection dormancy event configured on the mobile terminal is triggered, and when a long connection channel is established between the device and the push server, disconnect A long connection channel between the device and the push server.

In the mobile terminal message push solution provided by the embodiment of the present invention, the mobile terminal controls the connection or disconnection of the long connection channel between the mobile terminal and the push server by adopting the long connection dormancy mechanism, under the premise of ensuring the real-time transmission of the push message , to achieve the best balance between transmission efficiency, operating cost and power consumption of mobile terminals.

The embodiment of the present invention also provides a mobile terminal message push method, the method comprising:

After the push server receives the push message sent by the application server, it detects whether the long connection channel between the destination mobile terminal of the push message and the push server is established;

If the long connection channel is not established, then the push server sends the push message to the destination mobile terminal in a short message through the short message gateway; if the long connection channel has been established, then the push server passes the established A long connection channel, pushing the push message to the destination mobile terminal.

The embodiment of the present invention also provides a push server, including: a receiving module, a processing module, a sending module, and a sending and receiving module;

The receiving module is used to receive the push message sent by the application server;

The processing module is used to detect whether the long connection channel between the destination mobile terminal of the push message and the device is established after the receiving module receives the push message sent by the application server; if the long connection channel is not established, then indicate The sending module sends the push message to the destination mobile terminal as a short message through the short message gateway; if the long connection channel has been established, then instructs the transceiver module to send the push message to the mobile terminal through the established long connection channel. The push message is pushed to the destination mobile terminal.

In the mobile terminal message push solution provided by the embodiment of the present invention, the push server preferentially pushes messages to the mobile terminal through the established long connection channel, and when the long connection mode is not available, pushes the message to the mobile terminal through the short message gateway, with a relatively low cost. Realize real-time data push, avoid too long push message delay, solve the problem of power consumption surge caused by continuous connection retry of mobile terminal, enhance the flexibility of mobile terminal message push and adaptability to network environment, Reduce the resource consumption of the push server.

Description of drawings

FIG. 1 is a schematic diagram of a network architecture of an embodiment of the present invention;

FIG. 2 is a schematic flow diagram of a push message provided by a push server according to an embodiment of the present invention;

FIG. 3 is a schematic flow diagram of a mobile terminal receiving a push message according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a mobile terminal provided by an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a push server provided by an embodiment of the present invention.

Detailed ways

In view of the above-mentioned problems in the prior art, an embodiment of the present invention provides a mobile terminal message push solution. Embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings.

FIG. 1 shows the applicable system architecture of the embodiment of the present invention, which includes: a mobile terminal 11 , a push server 12 , an application server 13 and a short message gateway 14 . The application server 13 is used to send push messages, and the push server 12 is used to push the push messages to the mobile terminal 11; the short message gateway 14 is mainly used to receive the push messages sent by the push server 12, and send them to the mobile terminal 11 in a short message mode The mobile terminal 11 can be a mobile device such as a mobile phone or a tablet computer that supports a SIM (Subscriber Identity Module) card, or other mobile devices capable of wireless communication with the network side.

The process of pushing messages by the push server will be described in detail below in combination with the above system architecture and Figure 2. As shown in the figure, the process includes the following steps:

Step 201, the push server receives the push message sent by the application server.

Specifically, the sending target field of the push message carries information about the target mobile terminal, for example, the mobile phone number and device ID of the mobile terminal, and may also carry a token.

After the push server receives the push messages sent by the application server, it generates a message queue locally in the order in which it is received, and the push server performs push service processing according to the order of the push messages in the message queue. Preferably, the push server can divide the message queue according to the information of the destination mobile terminal, and sort the messages in the message queue according to the order of receiving time. Put it into the message queue corresponding to the mobile phone number of the mobile terminal.

Step 202, the push server locates the persistent connection channel identifier between the push server and the mobile terminal according to the destination mobile terminal information carried in the push message, wherein the persistent connection channel identifier may be a persistent connection channel address.

In step 203, the push server detects whether the persistent connection channel corresponding to the persistent connection channel identifier is established, and if the persistent connection channel is established, execute step 204; if the persistent connection channel is not established, execute steps 205-206.

Step 204, the push server pushes the push message to the destination mobile terminal through the established persistent connection channel.

In steps 205-206, the push server sends the push message to the destination mobile terminal in the form of a short message through the short message gateway.

Specifically, when the push server detects that the persistent connection with the destination mobile terminal has not been established, the push server will push the message and destination mobile terminal information (for example, IMSI (International Mobile Subscriber Identification Number, International Mobile Subscriber Identification Number), IMEI (International Mobile Subscriber MobileEquipment Identity, international mobile equipment identity code) and other communication numbers) to the short message gateway, and the short message gateway sends the push message to the destination mobile terminal in the form of a short message according to the information of the destination mobile terminal.

Further, in the above step 204, if the push server fails to push the message to the mobile terminal through the established long connection channel, the push message is pushed to the destination mobile terminal in the form of a short message through the short message gateway.

It can be seen from the above process that the push server gives priority to pushing messages to the mobile terminal through the established long connection channel. The message gateway pushes messages to mobile terminals, realizes real-time data push at a relatively low cost, avoids excessive message delay, solves the problem of power consumption surge caused by continuous connection retries of mobile terminals, and enhances the adaptability of the network environment performance, reducing the resource consumption of the push server.

In order to ensure that the push server can push a large number of push messages to the destination mobile terminal smoothly, a threshold value for the number of push messages can also be preset on the push server. , and if the persistent connection channel between the push server and the destination mobile terminal has not been established, the push server sends a notification short message to the mobile terminal through the short message gateway to notify the mobile terminal to initiate a request for establishing a persistent connection channel. After receiving the notification short message, the mobile terminal initiates a request to the push server to establish a persistent connection channel. After the long connection channel between the push server and the mobile terminal is established, the push server can push a large number of push messages through the long connection channel, ensuring that the push messages can be delivered to the mobile terminal in a timely and effective manner.

The push server may push messages to the mobile terminal in the form of a long connection or a short message, and the mobile terminal processes the received push messages. Below in conjunction with Fig. 3, describe in detail that the push server adopts the short message mode, and after the message is pushed to the mobile terminal by the short message gateway, the mobile terminal receives the flow of the pushed short message, as shown in the figure, the flow includes the following steps:

Step 301, the mobile terminal receives the short message pushed by the short message gateway.

Specifically, the short message is pushed by the push server through the short message gateway when the long connection channel between the push server and the mobile terminal has not been established, or when the push server fails to push the message to the mobile terminal through the long connection channel.

Step 302, the mobile terminal distributes the short message to the corresponding client application on the device.

In step 303, the mobile terminal detects whether the long-term connection channel between the device and the push server is established, and if the long-term connection channel is not established, then executes step 304; if the long-term connection channel is established, then maintains the long-term connection channel.

The implementation process for the mobile terminal to detect whether the long connection channel between the device and the push server is established belongs to the prior art, and will not be repeated here.

In step 304, the mobile terminal initiates a request to the push server to establish a persistent connection channel, and maintains the persistent connection channel after the persistent connection channel is established.

Specifically, the mobile terminal maintains the long connection channel, which can be implemented in the following two ways:

Method 1. The mobile terminal sends an HTTP request to the push server with a cycle interval of a certain period of time, that is, when the heartbeat time arrives, an HTTP Long-pull request is sent to reconnect the long connection;

Method 2. The mobile terminal sends a heartbeat detection message to the push server, and judges whether the current persistent connection channel is maintained by receiving the response message returned by the push server. If the persistent connection channel is disconnected, re-establish the persistent connection channel.

Preferably, in order to ensure that the long connection channel between the mobile terminal and the push server is established, the mobile terminal is also provided with a retry mechanism. When the long connection channel between the mobile terminal and the push server fails to be established, the following steps can also be performed: The terminal initiates a request to the push server to establish a persistent connection channel according to a preset number of times, or within a preset time period.

In the case of unsatisfactory network conditions, existing mobile terminals continue to try to establish a long connection channel with the push server, and such retries are often futile, which will cause a sharp increase in power consumption of the mobile terminal. Moreover, due to the use of a single Pushing messages in the long connection mode will cause a delay in the arrival of push messages in the case of network connection problems. However, the embodiment of the present invention sets up a retry mechanism on the mobile terminal side to try to establish a long connection channel within a limited duration or a limited number of times. Once the long connection channel fails to be established, the long connection mode is abandoned and the short message mode is used to receive Push messages, thereby avoiding the problem of a surge in the power of the mobile terminal, and ensuring that the push messages can arrive in time.

Preferably, before step 304, the mobile terminal can also detect the current mode of the device. If the mobile terminal detects that the device is in the interactive mode, step 304 is performed.

In practical applications, the mobile terminal can be in interactive mode and non-interactive mode. When the mobile terminal is currently performing business processing or application processing, it is in the interactive mode. message and other modes. When the mobile terminal is not currently performing any business processing or application processing, it is in a non-interactive mode, for example, the mobile terminal is in a standby mode or a screen lock mode. The mobile terminal can switch between a non-interactive mode and an interactive mode according to a user's operation instruction or according to a trigger event. For example, the user starts the client application, or receives a short message, triggering the mobile terminal to switch from the non-interactive mode to the interactive mode; another example, the user sets the mobile terminal to standby, or, when no message is received within a preset time period, triggers The mobile terminal switches from interactive mode to non-interactive mode.

It can be seen that when the mobile terminal is in the interactive mode, if the long connection channel between the mobile terminal and the push server is not established at this time, in order to ensure that the push message can be received in a timely and effective manner, it is necessary to establish a connection between the mobile terminal and the push server. A long connection channel, so that the push server can push messages through the long connection channel.

It should be noted that, in the above process, the execution order of step 302 and step 303 is not limited.

Further, when the persistent connection dormancy event configured on the mobile terminal is triggered and a persistent connection channel is established between the mobile terminal and the push server, the mobile terminal disconnects the persistent connection channel between the device and the push server.

The persistent connection dormancy event configured on the mobile terminal is triggered under one or any combination of the following conditions:

1. The mobile terminal has not received the push message (including receiving it through a long connection channel or receiving it through a short message) within a set period of time;

2. The mobile terminal switches from interactive mode to non-interactive mode;

3. The mobile terminal switches from the interactive mode to the non-interactive mode, and the duration of being in the non-interactive mode is longer than a preset duration.

It should be noted that the long-connection dormancy event is not limited to the ones mentioned above, for example, it can also be set and adjusted according to the current network status, power status, user's operation status and usage habits.

By setting the long connection sleep event to trigger the mobile terminal to disconnect the long connection channel between the device and the push server, the power consumption of the mobile terminal can be saved without affecting the service processing of the mobile terminal.

Further, if the mobile terminal receives the notification short message sent by the short message gateway, indicating that the push server will push a large number of push messages to the mobile terminal, the mobile terminal will initiate a request to the push server to establish a long connection channel, and in the long connection After the channel is established, keep the long connection channel, so that you can receive a large number of push messages pushed by the push server through the long connection channel.

It can be seen from the above process that the mobile terminal controls the connection or disconnection of the long connection channel between the mobile terminal and the push server by adopting the long connection dormancy mechanism, and realizes transmission efficiency, operation The best balance between cost and power consumption of mobile terminals.

Compared with the scheme of pushing messages based on short message mode, the scheme of the embodiment of the present invention has relatively low cost, better real-time performance, and higher throughput; compared with the scheme of pushing messages in traditional TCP long connection mode, it has the advantages of saving mobile Advantages such as terminal power consumption, and better adaptability, avoiding the delay problem caused by bad connections.

Based on the same technical concept, the embodiment of the present invention also provides a mobile terminal, as shown in FIG. 4 , the mobile terminal includes: a receiving module 41, a distribution module 42, a processing module 43, and a transceiver module 44;

The receiving module 41 is used to receive the short message pushed by the short message gateway; wherein, the short message is that the long connection channel between the push server and the device has not been established, or sends the message to the mobile terminal through the long connection channel In the case of failure to push the message, it is pushed through the short message gateway;

The distribution module 42 is used to distribute the short message received by the receiving module 41 to the application program of the device;

The processing module 43 is used to detect whether the long connection channel between the device and the push server is established, if not established, then send and receive a request to the push server to establish a long connection channel through the transceiver module 44, and in the long connection channel Keep the long connection channel after establishment; otherwise, keep the long connection channel; and, when the long connection dormancy event configured on the device is triggered and a long connection channel is established between the device and the push server, disconnect A long connection channel between the device and the push server.

The processing module 43 is also used to detect the current mode of the device before initiating a request to the push server to establish a long connection channel;

The processing module 43 is specifically configured to, if it is detected that the device is in the interactive mode, initiate a request for establishing a long connection channel to the push server through the sending and receiving module 44 .

The receiving module 41 is also used to receive the notification short message sent by the short message gateway; the notification short message is sent by the push server through the short message gateway, and is used to notify the device to initiate a request to establish a long connection channel ;

The processing module 43 is also configured to, after the receiving module 41 receives the notification short message sent by the short message gateway, initiate a request to the push server to establish a long connection channel through the sending and receiving module 44 .

The persistent connection dormancy event configured on the mobile terminal is triggered under one or any combination of the following conditions:

The mobile terminal has not received the short message pushed by the short message gateway within a set long time;

The mobile terminal switches from an interactive mode to a non-interactive mode;

The mobile terminal is switched from the interactive mode to the non-interactive mode, and the duration of the non-interactive mode is longer than a preset duration.

The processing module 43 is also used for, after the sending and receiving module 44 initiates a request for establishing a long connection channel to the push server, if the long connection channel fails to be established, according to a preset number of times, or within a preset time period, pass The transceiver module 44 initiates a request to the push server to establish a long connection channel.

The transceiver module 44 is also configured to receive the push message sent by the push server through the long connection channel.

Based on the same technical concept, the embodiment of the present invention also provides a push server. As shown in FIG. ;

A receiving module 51, configured to receive a push message sent by an application server;

The processing module 52 is used to detect whether the long connection channel between the destination mobile terminal of the push message and the device is established after the receiving module 51 receives the push message sent by the application server; if the long connection channel is not established, then indicate The sending module 53 sends the push message to the destination mobile terminal as a short message through the short message gateway; if the long connection channel has been established, then instructs the transceiver module 54 to send the push message to the mobile terminal through the established long connection channel. Push to the target mobile terminal.

The processing module 52 is also used to, if the transceiver module 54 fails to push the push message to the destination mobile terminal through the established long connection channel, then instructs the sending module 53 to send the push message to the target mobile terminal through the short message gateway. Send it to the destination mobile terminal in the form of a short message.

The processing module 52 is also used to instruct the sending module 53 to pass the short message when the number of messages to be pushed sent to the same mobile terminal reaches a preset value, but the long connection channel between the device and the mobile terminal is not established. The message gateway sends a notification short message to a mobile terminal whose number of messages to be pushed reaches a preset value, so as to notify the mobile terminal to initiate a request for establishing a long connection channel.

The persistent connection processing module 55 is an existing module of the push server, and is used for responding to the request for establishing a persistent connection channel received by the transceiver module 54 .

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is a better implementation Way. Based on this understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions to make a A terminal device (which may be a mobile phone, a personal computer, a server, or a network device, etc.) executes the methods described in various embodiments of the present invention.

The above is only a preferred embodiment of the present invention, it should be pointed out that, for those of ordinary skill in the art, without departing from the principle of the present invention, some improvements and modifications can also be made, and these improvements and modifications can also be made. It should be regarded as the protection scope of the present invention.

Claims (8)

1. A mobile terminal message push method, characterized in that, comprising: After the mobile terminal receives the short message pushed by the short message gateway, the short message is distributed to the application program of the mobile terminal, and detects whether the long connection channel between the device and the push server is established; If the long connection channel is not established, a request for establishing a long connection channel is initiated to the push server, and the long connection channel is maintained after the long connection channel is established; wherein, the short message is between the push server and the The long connection channel between the mobile terminals is not established, or, in the case of failure to push the message to the mobile terminal through the long connection channel, it is pushed through the short message gateway; When the long connection dormancy event configured on the mobile terminal is triggered, and a long connection channel is established between the device and the push server, the mobile terminal disconnects the long connection between the device and the push server aisle; Wherein, before initiating the request to the push server to establish a long connection channel, the method further includes: the mobile terminal detects the current mode of the device; The request to the push server for establishing a persistent connection channel is specifically: if the mobile terminal detects that the device is in an interactive mode, initiate a request to the push server for establishing a persistent connection channel. 2. The method of claim 1, further comprising: After receiving the notification short message sent by the short message gateway, the mobile terminal initiates a request to the push server to establish a long connection channel, and maintains the long connection channel after the long connection channel is established; wherein, the notification short message The message is sent by the push server through the short message gateway, and is used to notify the mobile terminal to initiate a request for establishing a persistent connection channel. 3. The method according to claim 1, wherein the persistent connection dormancy event configured on the mobile terminal is triggered in one of the following situations or in any combination: The mobile terminal has not received the short message pushed by the short message gateway within a set long time; The mobile terminal switches from an interactive mode to a non-interactive mode; The mobile terminal switches from the interactive mode to the non-interactive mode, and the duration of being in the non-interactive mode is longer than a preset duration. 4. The method according to claim 1, wherein after the request for establishing a long connection channel is initiated to the push server, the method further comprises: If the establishment of the persistent connection channel fails, the mobile terminal initiates a request to the push server to establish the persistent connection channel according to a preset number of times, or within a preset time period. 5. A mobile terminal, comprising: a receiving module, a distribution module, a processing module and a transceiver module; The receiving module is used to receive the short message pushed by the short message gateway; wherein, the short message is that the long connection channel between the push server and the device has not been established, or the push message to the device through the long connection channel fails In the case of , it is pushed through the short message gateway; A distribution module, configured to distribute the short message received by the receiving module to the application program of the device; A processing module, configured to detect whether the long connection channel between the device and the push server is established, if not established, send a request for establishing a long connection channel to the push server through the transceiver module, and Keep the long connection channel after establishment; otherwise, keep the long connection channel; and, when the long connection dormancy event configured on the device is triggered and a long connection channel is established between the device and the push server, disconnect A long connection channel between the device and the push server; Wherein, the processing module is further configured to detect the current mode of the device before initiating a request to the push server to establish a long connection channel; The processing module is specifically configured to, if it is detected that the device is in an interactive mode, send a request to the push server to establish a long connection channel through the sending and receiving module. 6. The mobile terminal according to claim 5, wherein the receiving module is further configured to receive a notification short message sent by the short message gateway; Sent by the message gateway, it is used to notify the device to initiate a request to establish a long connection channel; The processing module is further configured to, after the receiving module receives the notification short message sent by the short message gateway, initiate a request for establishing a persistent connection channel to the push server through the sending and receiving module. 7. The mobile terminal according to claim 5, wherein the persistent connection dormancy event configured on the device is triggered in one of the following situations or in any combination: The device has not received the short message pushed by the short message gateway within a set period of time; The device switches from interactive mode to non-interactive mode; The device switches from the interactive mode to the non-interactive mode, and the duration in the non-interactive mode is longer than a preset time period. 8. The mobile terminal according to claim 5, wherein the processing module is further configured to, after the sending and receiving module initiates a request for establishing a long connection channel to the push server, if the long connection channel fails to be established , according to a preset number of times, or within a preset time period, a request for establishing a long connection channel is initiated to the push server through the transceiver module.