CN105657000A - Message transmission method and device - Google Patents

Abstract

The present invention discloses a message transmission method and device, wherein the method includes: when pushing the message data packet of the message queue to the client fails, putting the message data packet back into the message queue; When the client sends a connection request, the message data packet is taken out from the message queue, and the taken out message data packet is pushed to the client. Through the technical solution of the present invention, when the terminal where the client is located has been disconnected from the network for a long period of time, the occupation of resources and bandwidth caused by the server repeatedly pushing messages can be avoided, and the waste of processing resources and bandwidth of the server can be effectively reduced .

Description

Message transmission method and device

technical field

The present invention relates to the field of communication technology, in particular to a message transmission method and device.

Background technique

The client (Client) refers to an application program that corresponds to a server and provides local services for clients. Except for some applications that only run locally, they are generally installed on ordinary terminals and need to cooperate with the server to run.

When the server sends a new message to the client, it usually uses a push method, that is, the server actively pushes the message to the client, but the network status of the terminal where the client is located will also change dynamically due to changes in the environment, for example, When the server pushes the message to the client, the network status of the terminal where the client is located changes, the network is disconnected, and cannot be received normally. At this time, the server usually pushes the message again every once in a while, but the terminal where the client is located may The network has been disconnected for a long time, wasting the processing resources and bandwidth of the server.

Contents of the invention

In view of the above problems, the present invention is proposed to provide a message transmission method and device that overcomes the above problems or at least partly solves or alleviates the above problems, and effectively reduces the processing resources and bandwidth of the server during the process of pushing message data occupancy.

According to one aspect of the present invention, a message transmission method is provided, the method comprising:

When the message data packet of the message queue fails to be pushed to the client, the message data packet is put back into the message queue;

When the connection request sent by the client is obtained, the message data packet is taken out from the message queue, and the taken out message data packet is pushed to the client.

Optionally, the connection request includes a network type identification of the communication network accessed by the client;

Correspondingly, the pushing the retrieved message data packet to the client specifically includes:

According to the network type identifier, it is judged whether the communication network accessed by the client has changed compared with that before the push failure, and if there is no change, the fetched message data packet is pushed to the client.

Optionally, the judging according to the network type identifier whether the communication network accessed by the client has changed compared with before the push failure, specifically includes:

judging whether the network type identifier is the same as the pre-stored type identifier;

If they are the same, it is determined that the communication network accessed by the client has not changed;

If not, it is determined that the communication network accessed by the client has changed, and the network type identifier is used as the pre-stored type identifier.

Optionally, after judging according to the network type identifier whether the communication network accessed by the client has changed compared with before the push failure, the method further includes:

If it changes, look up the mapping relationship according to the network type identifier, obtain the communication network corresponding to the network type identifier, and push the retrieved message data packet to the client through the communication network obtained through the search.

Optionally, when pushing the message data packet of the message queue to the client fails, before putting the message data packet back into the message queue, the method further includes:

Pushing the message data packet of the message queue to the client, if no confirm character returned by the client is received within a preset time, it is determined that the push of the message to the client fails.

Optionally, the message data packet includes: message type and/or timestamp;

Correspondingly, the taking out the message data packet from the message queue specifically includes:

The message data packet is taken out from the message queue according to the message type and/or the time stamp in the message data packet.

According to another aspect of the present invention, a messaging device is provided, the device comprising:

The processing unit is adapted to put the message data packet back into the message queue when pushing the message data packet of the message queue to the client fails;

The push unit is adapted to take out a message data packet from the message queue when obtaining the connection request sent by the client, and push the taken out message data packet to the client.

Optionally, the connection request includes a network type identification of the communication network accessed by the client;

Correspondingly, the push unit specifically includes:

The judging module is adapted to judge whether the communication network accessed by the client has changed compared with that before the push failure according to the network type identifier;

The push module is adapted to push the retrieved message data packet to the client when the judging result of the judging module is that the communication network accessed by the client has not changed compared with that before the push failure.

Optionally, the judging module is specifically adapted to judge whether the network type identifier is the same as the pre-stored type identifier, if they are the same, it is determined that the communication network accessed by the client has not changed, and if they are not the same, it is determined that the The communication network accessed by the client changes, and the network type identifier is used as the pre-stored type identifier.

Optionally, the push module is further adapted to search for a mapping relationship according to the network type identifier when the judging result of the judging module is that the communication network accessed by the client has changed compared with that before the push failure, The communication network corresponding to the network type identifier is obtained, and the retrieved message data packet is pushed to the client through the communication network obtained by searching.

Optionally, the push unit is further adapted to push the message data packets of the message queue to the client before re-putting the message data packets into the message queue when the push of the message data packets of the message queue to the client fails. Pushing is performed, and when no confirmation character returned by the client is received within a preset time, it is determined that the push of the message to the client fails.

Optionally, the message data packet includes: message type and/or timestamp;

Correspondingly, the push unit is specifically adapted to take out the message data packet from the message queue according to the message type and/or the time stamp in the message data packet.

The beneficial effects of the present invention are:

In the message transmission method and device proposed by the present invention, when the message data packet of the message queue fails to be pushed to the client, the message data packet is put back into the message queue; when the connection request sent by the client is obtained , take out the message data packet from the message queue, and push the taken out message data packet to the client, so as to avoid the problem caused by the server repeatedly pushing the message when the terminal where the client is located has been disconnected from the network for a long time The occupancy of resources and bandwidth, and then effectively reduce the waste of server processing resources and bandwidth during the message data push process.

The above description is only an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention, it can be implemented according to the contents of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and understandable , the specific embodiments of the present invention are enumerated below.

Description of drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiment. The drawings are only for the purpose of illustrating a preferred embodiment and are not to be considered as limiting the invention. Also throughout the drawings, the same reference numerals are used to designate the same parts. In the attached picture:

FIG. 1 schematically shows a schematic flowchart of a message transmission method according to an embodiment of the present invention;

FIG. 2 schematically shows a schematic flowchart of a message transmission method according to another embodiment of the present invention;

FIG. 3 schematically shows a subdivided flowchart of step S22 in a message transmission method according to another embodiment of the present invention;

FIG. 4 schematically shows a schematic flowchart of a message transmission method according to another embodiment of the present invention;

Fig. 5 schematically shows a schematic structural diagram of a message transmission device according to an embodiment of the present invention.

detailed description

Embodiments of the present invention are described in detail below, examples of which are shown in the drawings, wherein the same or similar reference numerals designate the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the figures are exemplary only for explaining the present invention and should not be construed as limiting the present invention.

Those skilled in the art will understand that unless otherwise stated, the singular forms "a", "an", "said" and "the" used herein may also include plural forms. It should be further understood that the word "comprising" used in the description of the present invention refers to the presence of said features, integers, steps, operations, elements and/or components, but does not exclude the presence or addition of one or more other features, Integers, steps, operations, elements, components, and/or groups thereof.

Those skilled in the art can understand that, unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which this invention belongs. It should also be understood that terms, such as those defined in commonly used dictionaries, should be understood to have meanings consistent with the meanings in the context of the prior art, and will not be used in an idealized or overly formal sense unless specifically defined to explain.

FIG. 1 schematically shows a schematic flowchart of a message transmission method according to an embodiment of the present invention;

Referring to Fig. 1, the message transmission method of the embodiment of the present invention specifically includes the following steps:

S11. When pushing the message data packet of the message queue to the client fails, re-put the message data packet into the message queue.

It should be noted that the message data in this embodiment includes, but is not limited to, instant messaging message data, general messaging message data, and the like. Correspondingly, the message queue refers to a queue for storing the instant messaging message data and general messaging message data.

Specifically, the instant messaging message specifies the ID of the user receiving the instant messaging message. The instant messaging message may be an instant messaging message sent from a terminal of a friend of the user, or an instant messaging message sent from a terminal of a member of the user's work group or discussion group. The form of the instant messaging message may be a text message, a picture message, a voice message or a video message, etc., and is received by the instant messaging server in the instant messaging. The general communication message refers to a general push message or a system push message of the client, and the like.

In this step, after the server pushes the message data packet of the message queue to the client, if it is determined that the push fails, the message data packet is put back into the message queue, and the server no longer repeatedly pushes the message data packet to the client, In order to avoid the occupation of server resources and bandwidth when the terminal where the client is located has been disconnected from the network for a long period of time.

It can be understood that the implementation of determining push failure includes multiple implementation methods, such as receiving a reception failure response message fed back by the client, or receiving a successful reception response message fed back by the client within a preset period of time, etc. Personnel need to set according to the actual application, which is not specifically limited in this embodiment of the present invention.

S12. When the connection request sent by the client is obtained, take out a message data packet from the message queue, and push the taken out message data packet to the client.

In practical applications, when the connection request sent by the client is obtained, the message data packet previously pushed to the client is taken out from the message queue again, and the taken out message data packet is pushed to the client.

In a specific embodiment, if the user enters a place with a weak network signal such as a parking lot, a basement, or an elevator, the network status of the terminal where the client is located changes and is in a disconnected state, unable to normally receive the message data packet pushed by the server. At this time, the server does not push the message again every once in a while, until the client reconnects to the network, the client will actively send a connection request to the server, and when the server obtains the connection request sent by the client , and then take out the message data packet from the message queue, and push the taken out message data packet to the client.

In the message transmission method proposed by the embodiment of the present invention, when the message data packet of the message queue fails to be pushed to the client, the message data packet is put back into the message queue; when the connection request sent by the client is obtained , take out the message data packet from the message queue, and push the taken out message data packet to the client, so as to avoid the problem caused by the server repeatedly pushing the message when the terminal where the client is located has been disconnected from the network for a long time The occupancy of resources and bandwidth, and then effectively reduce the waste of server processing resources and bandwidth during the message data push process.

FIG. 2 schematically shows a schematic flowchart of a message transmission method according to another embodiment of the present invention;

Referring to Figure 2, the message transmission method of the embodiment of the present invention specifically includes the following steps:

S21. When pushing the message data packet of the message queue to the client fails, put the message data packet into the message queue again.

Wherein, the connection request includes the identifier of the network type of the communication network accessed by the client.

Step S21 is the same as step S11 in the embodiment shown in FIG. 1 , and will not be repeated here.

S22. When the connection request sent by the client is obtained, take out the message data packet from the message queue, and judge whether the communication network accessed by the client has changed compared with that before the push failure according to the network type identifier , if there is no change, push the retrieved message data packet to the client.

It should be noted that there are mainly multiple network types for the client to access the communication network, such as wifi, net, etc., wherein the net network type includes specific network types such as 2G, 3G, and 4G. Specifically, both wifi and net networks support long connections.

In practical applications, when the mobile phone network type is wifi or net, the network link connection between the client and the server is a long connection, and the server can directly push the retrieved message data packet to the client.

Specifically, according to the different types of networks through which the client accesses the communication network, the network link connections through which the server pushes messages to the client are also different. Therefore, when obtaining the connection request sent by the client, it is necessary to determine whether the communication network accessed by the client has changed compared with that before the push failure according to the network type identifier of the client access communication network included in the connection request. If there is no change, and the communication network accessed by the client is of wifi or net corresponding to the network type before the push failure, the server can directly push the retrieved message data packet to the client.

In the embodiment of the present invention, through the network type identifier obtained from the connection request sent by the client, it is judged whether the communication network accessed by the client has changed compared with that before the push failure, and before and after confirming the communication network accessed by the client When there is no change, directly push the retrieved message data packet to the client. To avoid message transmission failure caused by not timely modifying the way of transmitting the message data packet or the data format of the message data packet when the communication network accessed by the client changes, so as to ensure the normal transmission of the message data packet.

In an optional embodiment of the present invention, as shown in FIG. 3 , in step S22, according to the network type identifier, judging whether the communication network accessed by the client has changed compared with that before the push failure, specifically includes the following steps :

S220. Obtain the network type identifier;

S221. Determine whether the network type identifier is the same as the pre-stored type identifier, if they are the same, execute step S222, if not, execute step S223;

S222. Determine that the communication network accessed by the client has not changed;

S223. Determine that the communication network accessed by the client has changed, and use the network type identifier as a pre-stored type identifier.

It should be noted that the pre-stored type identifier is the network type identifier carried in the connection request sent by the client during the last network access.

In the embodiment of the present invention, specifically by judging whether the network type identifier is the same as the pre-stored type identifier, if the currently accessed network type identifier is the same as the pre-stored type identifier, it is determined that the communication network accessed by the client has not changed. The currently accessed network type identifier is different from the pre-stored type identifier, it is determined that the communication network accessed by the client has changed, and the network type identifier is used as a new pre-stored type identifier, and the previous pre-stored type identifier is replaced. Thus, the accuracy of the communication network that the client accesses is determined is ensured.

In an optional embodiment of the present invention, after judging in step S22 according to the network type identifier whether the communication network accessed by the client has changed compared with that before the push failure, the method further includes the following steps in the accompanying drawings: Step S23 not shown:

S23. When the communication network accessed by the client changes compared with that before the push failure, look up the mapping relationship according to the network type identifier, obtain the communication network corresponding to the network type identifier, and take out the message data packet The communication network obtained through searching is pushed to the client.

It should be noted that the mapping relationship is a preset relationship that records the correspondence between the network type identifier and the communication network.

In the embodiment of the present invention, through the network type identifier obtained from the connection request sent by the client, it is judged whether the communication network accessed by the client has changed compared with that before the push failure, and before and after confirming the communication network accessed by the client When a change occurs, look up the mapping relationship according to the network type identifier, obtain the communication network corresponding to the network type identifier, and push the retrieved message data packet to the client through the communication network obtained through the search. Further avoid the failure of message transmission caused by not timely modifying the way of transmitting message data packets or the data format of message data packets when the communication network accessed by the client changes, so as to ensure the normal transmission of message data packets .

FIG. 4 schematically shows a schematic flowchart of a message transmission method according to another embodiment of the present invention;

Referring to Figure 4, the message transmission method of the embodiment of the present invention specifically includes the following steps:

S41. Push the message data packet of the message queue to the client, and if no confirmation character returned by the client is received within a preset time, it is determined that pushing the message to the client fails.

S42. When pushing the message data packet of the message queue to the client fails, re-put the message data packet into the message queue.

Wherein, the connection request includes the identifier of the network type of the communication network accessed by the client.

S43. When the connection request sent by the client is obtained, take out the message data packet from the message queue, and push the taken out message data packet to the client.

Steps S42-S43 are the same as steps S11-S12 in the embodiment shown in FIG. 1 , and will not be repeated here.

In the embodiment of the present invention, when the server has a message data packet that needs to be pushed, it pushes the message data packet of the message queue to the client, and confirms whether the client returns within a preset time. Characters are used to determine the failure of pushing messages to the terminal. The embodiment of the present invention can accurately realize the identification of message push failure, thereby ensuring the normal transmission of the next message data packet.

In an optional embodiment of the present invention, the message data packet includes: message type and/or time stamp;

Correspondingly, the taking out the message data packet from the message queue specifically includes: taking out the message data packet from the message queue according to the message type and/or the time stamp in the message data packet.

In the embodiment of the present invention, when taking out the message data packet from the message queue, according to the message type in the message data packet and/or taking out the message data packet from the message queue, and then ensuring that the message data packet corresponding to the instant message data The message data packets corresponding to the priority push messages are re-pushed to the client. Further, for the message data packets of the same priority, according to the timestamp in the message data packets, the message data packets with an earlier time are preferentially selected for re-push , so as to reduce the impact and loss on the corresponding users of the client, ensure the interests of users, and improve user experience.

For the method embodiment, for the sake of simple description, it is expressed as a series of action combinations, but those skilled in the art should know that the embodiment of the present invention is not limited by the described action order, because according to the embodiment of the present invention , certain steps may be performed in other order or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification belong to preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

Fig. 5 schematically shows a schematic structural diagram of a message transmission device according to an embodiment of the present invention.

Referring to FIG. 5 , the message transmission device according to the embodiment of the present invention specifically includes a processing unit 501 and a push unit 502, wherein:

The processing unit 501 is adapted to re-put the message data packet into the message queue when pushing the message data packet of the message queue to the client fails;

The push unit 502 is adapted to take out a message data packet from the message queue when obtaining the connection request sent by the client, and push the taken out message data packet to the client.

The message transmission device proposed by the embodiment of the present invention re-puts the message data packet into the message queue when the message data packet of the message queue fails to be pushed to the client; when the connection request sent by the client is obtained , take out the message data packet from the message queue, and push the taken out message data packet to the client, so as to avoid the problem caused by the server repeatedly pushing the message when the terminal where the client is located has been disconnected from the network for a long time The occupancy of resources and bandwidth, and then effectively reduce the waste of server processing resources and bandwidth during the message data push process.

According to an optional embodiment of the present invention, the connection request includes a network type identifier of the communication network accessed by the client;

Correspondingly, the push unit specifically includes:

The judging module is adapted to judge whether the communication network accessed by the client has changed compared with that before the push failure according to the network type identifier;

The push module is adapted to push the retrieved message data packet to the client when the judging result of the judging module is that the communication network accessed by the client has not changed compared with that before the push failure.

According to an optional embodiment of the present invention, the judging module is specifically adapted to judge whether the network type identifier is the same as the pre-stored type identifier, if they are the same, it is determined that the communication network accessed by the client has not changed, if not If they are the same, it is determined that the communication network accessed by the client has changed, and the network type identifier is used as the pre-stored type identifier.

According to an optional embodiment of the present invention, the push module is further adapted to: when the judging result of the judging module is that the communication network accessed by the client has changed compared with that before the push failure, according to the network The type identifier looks up the mapping relationship, obtains the communication network corresponding to the network type identifier, and pushes the retrieved message data packet to the client through the communication network obtained through the search.

According to an optional embodiment of the present invention, the push unit is further adapted to push the message data packet of the message queue to the client before re-putting the message data packet into the message queue when the message data packet of the message queue fails to be pushed to the client. The message data packet is pushed to the client, and if no confirmation character returned by the client is received within a preset time, it is determined that the push of the message to the terminal fails.

According to an optional embodiment of the present invention, the message data packet includes: message type and/or time stamp;

Correspondingly, the push unit is specifically adapted to take out the message data packet from the message queue according to the message type and/or the time stamp in the message data packet.

As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for related parts, please refer to the part of the description of the method embodiment.

To sum up, the message transmission method and device proposed by the embodiments of the present invention re-put the message data packet into the message queue when the message data packet of the message queue fails to be pushed to the client; When the connection request sent by the client, the message data packet is taken out from the message queue, and the taken out message data packet is pushed to the client, so as to avoid that when the terminal where the client is located has been disconnected from the network for a long time, The resource and bandwidth occupation caused by repeated message push by the server can effectively reduce the waste of server processing resources and bandwidth during the process of message data push.

It should be noted that the algorithms and formulas presented herein are not inherently related to any particular computer, virtual system, or other device. Various general systems can also be used with the examples based here. The structure required to construct such a system is apparent from the above description. Furthermore, the present invention is not specific to any particular programming language. It should be understood that various programming languages can be used to implement the content of the present invention described herein, and the above description of specific languages is for disclosing the best mode of the present invention.

In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure the understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, in order to streamline the present invention and to facilitate an understanding of one or more of its various aspects, various features of the invention are sometimes grouped together into a single embodiment , figure, or description of it. This disclosed method and apparatus, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art can understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. Modules or units or components in the embodiments may be combined into one module or unit or component, and furthermore may be divided into a plurality of sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings) and any method or method so disclosed may be used in any combination, except that at least some of such features and/or processes or units are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will understand that although some embodiments described herein include some features included in other embodiments but not others, combinations of features from different embodiments are meant to be within the scope of the invention. and form different embodiments.

The various component embodiments of the present invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art should understand that a microprocessor or a digital signal processor (DSP) can be used in practice to implement some or all functions of some or all components in the website security detection device according to the embodiment of the present invention. The present invention can also be implemented as an apparatus or an apparatus program (for example, a computer program and a computer program product) for performing a part or all of the methods described herein. Such a program for realizing the present invention may be stored on a computer-readable medium, or may be in the form of one or more signals. Such a signal may be downloaded from an Internet site, or provided on a carrier signal, or provided in any other form.

The above descriptions are only part of the embodiments of the present invention. It should be pointed out that those skilled in the art can make some improvements and modifications without departing from the principles of the present invention. It should be regarded as the protection scope of the present invention.

The invention discloses A1. A message transmission method, comprising:

When the message data packet of the message queue fails to be pushed to the client, the message data packet is put back into the message queue;

When the connection request sent by the client is obtained, the message data packet is taken out from the message queue, and the taken out message data packet is pushed to the client.

A2. The method as described in A1, wherein the connection request includes the network type identification of the client accessing the communication network;

Correspondingly, the pushing the retrieved message data package to the client includes:

According to the network type identifier, it is judged whether the communication network accessed by the client has changed compared with that before the push failure, and if there is no change, the fetched message data packet is pushed to the client.

A3. The method as described in A2, the judging according to the network type identifier whether the communication network accessed by the client has changed compared with that before the push failure, specifically including:

judging whether the network type identifier is the same as the pre-stored type identifier;

If they are the same, it is determined that the communication network accessed by the client has not changed;

If not, it is determined that the communication network accessed by the client has changed, and the network type identifier is used as the pre-stored type identifier.

A4. The method according to any one of A2-A3, after determining whether the communication network accessed by the client has changed according to the network type identifier compared with before the push failure, the method further includes:

If it changes, look up the mapping relationship according to the network type identifier, obtain the communication network corresponding to the network type identifier, and push the retrieved message data packet to the client through the communication network obtained through the search.

A5. The method according to any one of A1-A4, when the message data packet of the message queue fails to be pushed to the client, before putting the message data packet back into the message queue, the method also includes :

Pushing the message data packet of the message queue to the client, if no confirm character returned by the client is received within a preset time, it is determined that the push of the message to the client fails.

A6. The method according to any one of A1-A5, wherein the message data packet includes: message type and/or time stamp;

Correspondingly, the taking out the message data packet from the message queue specifically includes:

The message data packet is taken out from the message queue according to the message type and/or the time stamp in the message data packet.

B7. A messaging device, comprising:

The processing unit is adapted to put the message data packet back into the message queue when pushing the message data packet of the message queue to the client fails;

The push unit is adapted to take out a message data packet from the message queue when obtaining the connection request sent by the client, and push the taken out message data packet to the client.

B8. The device according to B7, wherein the connection request includes a network type identifier for the client to access the communication network;

Correspondingly, the push unit specifically includes:

The judging module is adapted to judge whether the communication network accessed by the client has changed compared with that before the push failure according to the network type identifier;

The push module is adapted to push the retrieved message data packet to the client when the judging result of the judging module is that the communication network accessed by the client has not changed compared with that before the push failure.

B9, the device as described in B8, the judging module is specifically adapted to judge whether the network type identifier is the same as the pre-stored type identifier, if they are the same, it is determined that the communication network accessed by the client has not changed, if they are not the same , it is determined that the communication network accessed by the client has changed, and the network type identifier is used as the pre-stored type identifier.

B10. The device as described in any one of B8 to B9, the push module is also suitable for when the judgment result of the judgment module is that the communication network accessed by the client has changed compared with that before the push failure Searching for a mapping relationship according to the network type identifier to obtain a communication network corresponding to the network type identifier, and pushing the retrieved message data packet to the client through the communication network obtained through the search.

B11. The device according to any one of B7 to B10, the push unit is further adapted to re-put the message data packet into the message queue when the message data packet of the message queue fails to be pushed to the client , push the message data packet of the message queue to the client, and if no confirmation character returned by the client is received within a preset time, it is determined that the push of the message to the client fails.

B12. The device according to any one of B7 to B11, wherein the message data packet includes: message type and/or time stamp;

Correspondingly, the push unit is specifically adapted to take out the message data packet from the message queue according to the message type and/or the time stamp in the message data packet.

Claims (10)

1. a message transfer method, comprising:

When by the message packets of message queue to client push failure, described message packets is reentered into message queue;

When getting the connection request that described client terminal sends, from described message queue, take out message packets, the message packets of taking-up is pushed to described client terminal.

2. the method for claim 1, described connection request comprises the network type mark of described client terminal access communications network;

Correspondingly, described the message packets of taking-up is pushed to described client terminal, specifically comprises:

Judging whether the network of communication that described client terminal accesses changes compared with pushing before unsuccessfully according to described network type mark, if not changing, then the message packets of taking-up being pushed to described client terminal.

3. method as claimed in claim 2, described mark according to described network type judges whether the network of communication that described client terminal accesses changes compared with pushing before unsuccessfully, specifically comprises:

Judge that whether described network type mark is identical with the type identification that prestores;

If identical, then assert that the network of communication that described client terminal accesses does not change;

If not identical, then assert the network of communication change that described client terminal accesses, and described network type is identified as the type identification that prestores.

4. method as according to any one of claim 2��3, described judge whether the network of communication that described client terminal accesses changes compared with pushing before unsuccessfully according to described network type mark after, described method also comprises:

If change, then search mapping relation according to described network type mark, obtain the network of communication corresponding with described network type mark, the message packets of taking-up is pushed to described client terminal by searching the network of communication of acquisition.

5. method as according to any one of Claims 1 to 4, described when by the message packets of message queue to client push failure, before described message packets is reentered into message queue, described method also comprises:

The message packets of message queue is pushed to client terminal, when not receiving the determination character that described client terminal returns within the default time, assert to described client push message failure.

6. method as according to any one of Claims 1 to 5, described message packets comprises: type of message and/or time stamp;

Correspondingly, described from described message queue, take out message packets, specifically comprise:

From described message queue, message packets is taken out according to the type of message in described message packets and/or time stamp.

7. an information transfer device, comprising:

Processing unit, is suitable for, when by the message packets of message queue to client push failure, described message packets is reentered into message queue;

Push unit, be suitable for from described message queue, taking out message packets when getting the connection request that described client terminal sends, the message packets of taking-up being pushed to described client terminal.

8. device as claimed in claim 7, described connection request comprises the network type mark of described client terminal access communications network;

Correspondingly, described propelling movement unit, specifically comprises:

Judge module, be suitable for judging whether the network of communication that described client terminal accesses changes compared with pushing before unsuccessfully according to described network type mark;

Pushing module, is suitable for, when the network of communication that the judged result of described judgement module is the access of described client terminal does not change compared with pushing before unsuccessfully, the message packets of taking-up is pushed to described client terminal.

9. device as claimed in claim 8, described judgement module, specifically be suitable for judging that whether described network type mark is identical with the type identification that prestores, if it is identical, then assert that the network of communication that described client terminal accesses does not change, if not identical, then assert the network of communication change that described client terminal accesses, and described network type is identified as the type identification that prestores.

10. device as according to any one of claim 8��9, described pushing module, also be suitable for when the network of communication that the judged result of described judgement module is the access of described client terminal changes compared with pushing before unsuccessfully, mapping relation is searched according to described network type mark, obtain the network of communication corresponding with described network type mark, the message packets of taking-up is pushed to described client terminal by searching the network of communication of acquisition.