CN104468841A - Method and device for transmitting information in batches - Google Patents

Abstract

The invention discloses a method and device for sending messages in batches, which are applied to a distributed message system. The method includes: reading a packaged request packet to be sent; parsing the request packet to obtain meta information and messages; Judging whether the meta information is the same as the meta information of the previous request packet; and according to the judging result, processing the meta information and corresponding messages and sending them to the corresponding server data directory. By using the method and device, messages with the same meta-information can be processed in batches and sent together to a corresponding server data directory, thereby reducing network delay and greatly improving sending performance.

Description

A method and device for sending messages in batches

technical field

The present invention relates to the field of computer technology, in particular to a method and device for sending messages in batches.

Background technique

A distributed message system is a system that uses distributed processing to publish and subscribe messages. Typical distributed message systems include kafka, RabbitMQ, ActiveMQ, QBus, and so on.

Qbus is a distributed message system based on kafka, which is mainly composed of publisher (Producer), subscriber (Consumer), storage (Broker), coordinator (Zookeeper), agent (Agent) and other units. The main function of the Agent is to push the log files to the storage side in real time.

The QBus system currently uses a single message sending strategy. In order to ensure data reliability, data sending needs to wait for acknowledgment (ACK), and network delay has become a performance bottleneck. Among them, it is necessary to read the request packets one by one and send them to the corresponding server data directory. Repeatedly passing through the network results in poor performance and cannot meet the needs of a large number of users to call the sending interface. It is easy to cause a backlog of data sending, trigger backlog alarms, and increase operation and maintenance costs. In addition, a large number of unsent messages makes local files unable to be deleted, and the local disk space usage rate is high.

Contents of the invention

In view of the above problems, the method and device for sending messages in batches according to the embodiments of the present invention are proposed, so as to overcome the above problems or at least partly solve the above problems.

According to the first aspect of the present invention, a method for sending messages in batches is provided, which is applied to a distributed message system, including: reading an encapsulated request packet to be sent; parsing the request packet to obtain meta information and message ; Judging whether the meta information is the same as the meta information of the previous request packet; and according to the judgment result, processing the meta information and the corresponding message and sending them to the corresponding server data directory.

Optionally, in the method for sending messages in batches according to the embodiment of the present invention, the step of processing the meta information and the corresponding message and sending them to the corresponding server data directory according to the judgment result includes: if the judgment result is If they are the same, the corresponding message is cached in the cache file; if the judgment result is different, the cache file and the corresponding meta information are repackaged into a request packet, and sent to the corresponding server data directory, and the cache The file is cleared, and messages corresponding to the different meta information are cached in the cache file.

Optionally, in the method for sending messages in batches according to an embodiment of the present invention, before the step of reading the encapsulated request packet to be sent, the method further includes: encapsulating a single message and meta information into request package.

Optionally, in the method for sending messages in batches according to the embodiment of the present invention, in the step of processing the meta information and the corresponding messages and sending them to the corresponding server data directory according to the judgment result, call asynchronous sending The interface sends the processed meta-information and corresponding messages to the corresponding server data directory.

Optionally, in the method for sending messages in batches according to an embodiment of the present invention, after the step of processing the meta-information and the corresponding message according to the judgment result and sending it to the corresponding server data directory, the method It also includes: receiving the acknowledgment information returned by the server, and deleting the sent meta-information and the corresponding message.

Optionally, in the method for sending messages in batches according to an embodiment of the present invention, after the step of parsing the request packet to obtain meta information and messages, the method further includes: judging that the meta information corresponds to Whether the maximum sending timeout time of the message is lower than the predefined threshold; and if the judging result is yes, the request packet is sent to the corresponding server data directory.

Optionally, in the method for sending messages in batches according to an embodiment of the present invention, after the step of caching the corresponding messages into the cache file, the method further includes: judging whether the cached message size exceeds the preset The defined cache size; and if the judgment result is yes, repackage the cached message and meta information into a request packet and send it to the corresponding server data directory.

Optionally, in the method for sending messages in batches according to an embodiment of the present invention, after the step of caching the corresponding messages into the cache file, the method further includes: judging whether the cached message has exceeded sending timeout time; and if the judging result is yes, repackaging the cached message and meta information into a request packet and sending it to the corresponding server data directory.

According to the second aspect of the present invention, there is provided a device for sending messages in batches, which is applied to a distributed message system, including: a reading module, used to read the encapsulated request packet to be sent; a parsing module, used for parsing The request packet is used to obtain meta information and messages; the first judging module is used to judge whether the meta information is the same as the meta information of the previous request packet; and the processing and sending module is used to check the meta information according to the judging result And the corresponding message is processed and sent to the corresponding server data directory.

Optionally, in the device for sending messages in batches according to an embodiment of the present invention, the processing and sending modules: if the judgment result is the same, cache the corresponding message in the cache file; if the judgment result is different Next, repackage the cache file and the corresponding meta information into a request packet, send it to the corresponding server data directory, clear the cache file, and cache the messages corresponding to the different meta information to the cache file middle.

Optionally, in the apparatus for sending messages in batches according to the embodiment of the present invention, an encapsulation module is further included, configured to encapsulate a single message and meta information into a request packet.

Optionally, in the device for sending messages in batches according to the embodiment of the present invention, the processing and sending module calls an asynchronous sending interface to send the processed meta information and corresponding messages to the corresponding server data directory.

Optionally, the device for sending messages in batches according to the embodiment of the present invention further includes a confirmation and deletion module, configured to receive the confirmation information returned by the server, and delete the sent meta information and corresponding messages.

Optionally, in the device for sending messages in batches according to an embodiment of the present invention, a second judging module is also included, configured to judge the meta information after the parsing module parses the request packet to obtain meta information and messages. Whether the maximum sending timeout of the message corresponding to the information is lower than the predefined threshold, and if the judgment result is yes, the processing and sending module sends the request packet to the corresponding server data directory.

Optionally, in the device for sending messages in batches according to the embodiment of the present invention, a third judging module is also included, configured to judge the cached message after the processing and sending module caches the corresponding message in the cache file. Whether the size of the message exceeds the predefined cache size, and if the judgment result is yes, the processing and sending module repackages the cached message and meta information into a request packet and sends it to the corresponding server data directory.

Optionally, in the apparatus for sending messages in batches according to an embodiment of the present invention, a fourth judging module is also included, which is used to judge whether the The timeout period for sending the cached message, and if the judgment result is yes, the processing and sending module repackages the cached message and meta information into a request packet and sends it to the corresponding server data directory.

The present invention provides the above method and device for sending messages in batches. According to the embodiment of the present invention, the encapsulated request packet to be sent can be read, the request packet can be parsed to obtain meta-information and messages, and it can be judged whether the meta-information It is the same as the meta information of the previous request packet, and according to the judgment result, the meta information and the corresponding message are processed and sent to the corresponding server data directory. As a result, messages with the same meta information can be processed in batches and sent to the corresponding server data directory together, reducing network delay and greatly improving sending performance. In addition, according to various optional embodiments of the present invention, due to the adoption of a single cache file, it is easy to perform a rollback operation when the message is not sent successfully; delete the meta information and the message after receiving the confirmation information returned by the server, reducing the It occupies the local disk; it can also perform different targeted processing according to the timeout period of message sending and the size of the cached message, so as to ensure the real-time sending and sending success rate.

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:

1 is a schematic flow diagram of a method for sending messages in batches according to an embodiment of the present invention; and

Fig. 2 is a schematic structural diagram of a device for sending messages in batches and a server according to an embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided for more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

According to the first aspect of the present invention, a method 100 for sending messages in batches is provided, which is applied to a distributed message system.

In the embodiment of the present invention, the distributed message system may be a system that adopts distributed processing to publish and subscribe messages, for example including kafka, RabbitMQ, ActiveMQ, QBus and so on. In the following, the principle of the present invention will be described in detail by taking the QBus system as an example, so as to help readers better understand the principle of the present invention. However, those skilled in the art should understand that the scope of the present invention is not limited to the QBus system, but can be applied to any distributed message system.

The QBus system is mainly composed of publishers (Producer), subscribers (Consumer), storage (Broker), coordinator (Zookeeper), agent (Agent) and other units. The main role of the agent is to push log files to the storage in real time, so the message sending mechanism of the agent is very important. The principle of the present invention will be exemplified below by mainly taking the message sending of the agent side as an example. Similarly, the scope of the present invention is not limited thereto, but can be applied to each unit of a distributed message system (eg, QBus system).

FIG. 1 shows a flowchart of a method 100 for sending messages in batches according to an embodiment of the present invention. As shown in FIG. 1 , the method 100 starts at step S110, wherein the encapsulated request packet to be sent is read.

Optionally, according to an embodiment of the present invention, before the step S110 of reading the encapsulated request packet to be sent, the method may further include the following step: combining a single message with meta information (that is, meta information) Encapsulated as a request package. According to the embodiment of the present invention, the SDK (Software Development Kit) can be called to encapsulate a single message and meta information into a request package, and record it in a local file, ready to be sent to the server.

In step S110, the encapsulated request packet to be sent may be read (for example, from a local file). Afterwards, in step S120, the request packet is parsed to obtain meta information and messages. For example, the encapsulated request packet can be decapsulated, and meta information and messages can be obtained from it.

After step S120, step S130 is executed, wherein it is judged whether the meta information is the same as the meta information of the previous request packet. According to an embodiment of the present invention, there are various kinds of meta information. The message encapsulated in the request packet together with the meta information is called the message corresponding to the meta information, the message types corresponding to the same meta information are the same or similar, and the message types corresponding to different meta information are different or dissimilar. According to the embodiment of the present invention, messages of the same or similar type can be sent together in batches, while messages of different or dissimilar types need to be sent separately.

Next, step S140 is executed, wherein, according to the judgment result, the meta information and the corresponding message are processed and sent to the corresponding server data directory.

According to an embodiment of the present invention, the step S140 may include: if the judgment result is the same, then cache the corresponding message into the cache file; if the judgment result is different, then repackage the cache file and the corresponding meta information The request package is sent to the corresponding server data directory, and the cache file is cleared, and the messages corresponding to the different meta information are cached in the cache file.

In the above step S140, if the judgment result is the same, that is, the meta information is the same as the meta information of the previous request packet, the message corresponding to the meta information can be cached in the cache file (for example, the Batcher. The messages in the request package are sent in batches to the corresponding server data directory.

And if the judgment result is different, that is, the meta information is different from that of the previous request packet and needs to be sent separately, then the cache file and the corresponding meta information can be repackaged into a request packet and sent to the corresponding server data directory . That is, all messages of the same type previously cached in the cache file and corresponding meta information are repackaged into a request packet, and sent to a corresponding server data directory corresponding to the meta information. After the sending is completed, the cache file may be cleared, and the messages corresponding to the different meta information are cached and stored in the cache file. Next, continue to read the next request packet, and parse it to obtain the meta information and message in it, and judge whether this meta information is the same as the meta information corresponding to the currently cached message, and perform the above processing. Next, repeat the above process for the following request packets.

According to an embodiment of the present invention, in the step S140, an asynchronous sending interface (for example, an SDK asynchronous sending interface) may be called to send the processed meta information and corresponding messages to the corresponding server data directory.

Optionally, according to an embodiment of the present invention, after the step S140, the method 100 may include the following steps: receiving the acknowledgment information returned by the server, and deleting the sent meta information and the corresponding message. In this way, the meta information and messages that have been sent can be deleted, reducing the occupation of local disk space.

Optionally, according to an embodiment of the present invention, after the step S120, the method may further include the following optional step: judging whether the maximum sending timeout time of the message corresponding to the meta information is lower than the predefined threshold; if the judgment result is yes, then send the request packet to the corresponding server data directory. In the above embodiment, it is judged whether the maximum sending time of the message corresponding to the meta information in the request packet read and parsed this time is lower than the predefined threshold, that is, it is judged whether the message corresponding to the meta information has a higher In order not to affect the real-time transmission of such meta-information (and messages) according to the requirement of real-time transmission, batch transmission is not performed, but individual transmission is directly performed. The above-mentioned predefined threshold can be selected according to actual needs. In order to ensure high real-time transmission, a smaller threshold can be selected; and in order to ensure high transmission performance, a larger threshold can be selected.

Optionally, according to an embodiment of the present invention, in the step S140, after the step of caching the corresponding message into the cache file is performed, the method may further include the following optional step: judging the Whether the cached message size exceeds the predefined cache size; if the judgment result is yes, repackage the cached message and meta information into a request packet and send it to the corresponding server data directory. In the above-mentioned embodiment, it can be ensured that the size of the request packets sent in batches will not be too large to affect the sending. Among them, it is judged whether the size of the cached message exceeds the predefined cache size. If it has exceeded, the subsequent The message corresponding to the same meta-information, but directly repackaged and sent.

Optionally, according to an embodiment of the present invention, in step S140, after performing the step of caching the corresponding message into the cache file, the method may further include the following optional step: judging whether The timeout period for sending the cached message has exceeded; and if the judgment result is yes, repackage the cached message and meta information into a request packet, and send it to the corresponding server data directory. In the above embodiment, high real-time transmission can be guaranteed, that is, it is guaranteed that the cached message will not be sent overtime, and once it is judged that the transmission timeout of the cached message has exceeded, the subsequent same meta information will not be cached The corresponding message is directly repackaged and sent.

According to the second aspect of the present invention, corresponding to the method 100 above, an apparatus 200 for sending messages in batches is also provided, which is applied to a distributed message system.

In the embodiment of the present invention, the distributed message system may be a system that adopts distributed processing to publish and subscribe messages, for example including kafka, RabbitMQ, ActiveMQ, QBus and so on. In the following, the principle of the present invention will be described in detail by taking the QBus system as an example, so as to help readers better understand the principle of the present invention. However, those skilled in the art should understand that the scope of the present invention is not limited to the QBus system, but can be applied to any distributed message system.

The QBus system is mainly composed of publishers (Producer), subscribers (Consumer), storage (Broker), coordinator (Zookeeper), agent (Agent) and other units. The main role of the agent is to push log files to the storage in real time, so the message sending mechanism of the agent is very important. The principle of the present invention will be exemplified below by mainly taking the message sending of the agent side as an example. Similarly, the scope of the present invention is not limited thereto, but can be applied to each unit of a distributed message system (eg, QBus system).

Fig. 2 shows a schematic structural diagram of an apparatus 200 for sending messages in batches and a server 300 according to an embodiment of the present invention. As shown in FIG. 2 , the device 200 mainly includes a reading module 210 , an analyzing module 220 , a first judging module 230 , and a processing and sending module 240 . Wherein, the reading module 210 is used to read the encapsulated request packet to be sent; the parsing module 220 is used to parse the request packet to obtain meta information and messages; the first judging module 230, It is used to judge whether the meta information is the same as that of the previous request packet; the processing and sending module 240 is used to process the meta information and corresponding messages according to the judgment result and send them to the corresponding server data directory.

First, the reading module 210 reads the encapsulated request packet to be sent.

Optionally, according to an embodiment of the present invention, the apparatus 200 may also include an optional module: an encapsulation module (not shown in FIG. 2 ), where the read module 210 reads the encapsulated request to be sent Before the packet, the encapsulation module may encapsulate a single message and meta information (ie, meta information) into a request packet. According to an embodiment of the present invention, the encapsulation module may call SDK (Software Development Kit) to encapsulate a single message and meta-information into a request package, and record it in a local file, ready to be sent to the server.

The reading module 210 can read (for example, from a local file) the encapsulated request packet to be sent. Afterwards, the parsing module 220 can parse the request packet to obtain meta information and messages. For example, the parsing module 220 may decapsulate the encapsulated request packet, and obtain meta information and messages therefrom.

Subsequently, the first judging module 230 can judge whether the meta information is the same as the meta information of the previous request packet. According to an embodiment of the present invention, there are various kinds of meta information. The message encapsulated in the request packet together with the meta information is called the message corresponding to the meta information, the message types corresponding to the same meta information are the same or similar, and the message types corresponding to different meta information are different or dissimilar. According to the embodiment of the present invention, messages of the same or similar type can be sent together in batches, while messages of different or dissimilar types need to be sent separately.

Next, the processing and sending module 240 may process the meta information and corresponding messages according to the judgment result and send them to the corresponding server data directory.

According to an embodiment of the present invention, if the judgment result is the same, the processing and sending module 240 caches the corresponding message in the cache file; if the judgment result is different, the processing and sending module 240 caches the cache file The corresponding meta information is repackaged into a request packet, and sent to the corresponding server data directory, and the cache file is cleared, and the messages corresponding to the different meta information are cached in the cache file.

If the judgment result is the same, that is, the meta information is the same as the meta information of the previous request packet, then the processing and sending module 240 can cache the message corresponding to the meta information into a cache file (for example, Batcher.buf file) to prepare The messages in the previous request package are sent to the corresponding server data directory in batches together.

And if the judgment result is different, that is, the meta information is different from that of the previous request packet and needs to be sent separately, then the processing and sending module 240 can repackage the cache file and the corresponding meta information into a request packet, and sent to the appropriate server data directory. That is, the processing and sending module 240 repackages all messages of the same type and corresponding meta-information previously cached in the cache file into a request packet, and sends it to a corresponding server data directory, and the server data directory and the meta-information Corresponding. After the sending is completed, the processing and sending module 240 may clear the cache file, and perform cache processing on the messages corresponding to the different meta information, and cache them in the cache file. Next, the reading module 210 continues to read the next request packet, and the parsing module 220 parses it to obtain the meta information and message therein, and the first judging module 230 judges whether this meta information is consistent with The meta information corresponding to the cached messages is the same, and the processing and sending module 240 performs the above processing. Next, repeat the above operations for the following request packets.

According to an embodiment of the present invention, the processing and sending module 240 may call an asynchronous sending interface (eg, SDK asynchronous sending interface) to send the processed meta information and corresponding messages to the corresponding server data directory.

Optionally, according to an embodiment of the present invention, the apparatus 200 may also include an optional module: an acknowledgment and deletion module (not shown in FIG. After the meta information and corresponding messages are processed and sent to the corresponding server data directory, the confirmation information returned by the server is received, and the sent meta information and corresponding messages are deleted. In this way, the meta information and messages that have been sent can be deleted, reducing the occupation of local disk space.

Optionally, according to an embodiment of the present invention, the apparatus 200 may also include an optional module: a second judging module (not shown in FIG. 2 ), configured to parse the request in the parsing module 220 After obtaining the meta information and the message, judge whether the maximum sending timeout time of the message corresponding to the meta information is lower than the predefined threshold; if the judgment result is yes, then the second judging module sends the request packet to the appropriate server data directory. In the above embodiment, the second judging module judges whether the maximum sending time of the message corresponding to the meta information in the request packet read and parsed this time is lower than a predefined threshold, that is, the second judging module It is judged whether the message corresponding to this kind of meta-information has a higher requirement of real-time sending. For this kind of meta-information (and message), in order not to affect the real-time sending, it is not sent in batches, but directly sent individually. The above-mentioned predefined threshold can be selected according to actual needs. In order to ensure high real-time transmission, a smaller threshold can be selected; and in order to ensure high transmission performance, a larger threshold can be selected.

Optionally, according to an embodiment of the present invention, the apparatus 200 may also include an optional module: a third judging module (not shown in FIG. 2 ), configured to convert the corresponding After the message is cached in the cache file, it is judged whether the size of the cached message exceeds the predefined cache size; if the judgment result is yes, then the third judging module repackages the cached message and meta information into a request packet, And sent to the corresponding server data directory. In the above-mentioned embodiment, it can be ensured that the size of the request packets sent in batches will not be too large to affect the sending. Among them, it is judged whether the size of the cached message exceeds the predefined cache size. If it has exceeded, the subsequent The message corresponding to the same meta-information, but directly repackaged and sent.

Optionally, according to an embodiment of the present invention, the apparatus 200 may also include an optional module: a fourth judging module (not shown in FIG. 2 ), configured to convert the corresponding After the message is cached in the cache file, it is judged whether the sending timeout of the cached message has been exceeded; if the judgment result is yes, then the fourth judging module repackages the cached message and meta information into a request packet, and sent to the appropriate server data directory. In the above embodiment, high real-time transmission can be guaranteed, that is, it is guaranteed that the cached message will not be sent overtime, and once it is judged that the transmission timeout of the cached message has exceeded, the subsequent same meta information will not be cached The corresponding message is directly repackaged and sent.

The present invention provides the above method and device for sending messages in batches. According to the embodiment of the present invention, the encapsulated request packet to be sent can be read, the request packet can be parsed to obtain meta-information and messages, and it can be judged whether the meta-information It is the same as the meta information of the previous request packet, and according to the judgment result, the meta information and the corresponding message are processed and sent to the corresponding server data directory. As a result, messages with the same meta information can be processed in batches and sent to the corresponding server data directory together, reducing network delay and greatly improving sending performance. In addition, according to various optional embodiments of the present invention, due to the adoption of a single cache file, it is easy to perform a rollback operation when the message is not sent successfully; delete the meta information and the message after receiving the confirmation information returned by the server, reducing the It occupies the local disk; it can also perform different targeted processing according to the timeout period of message sending and the size of the cached message, so as to ensure the real-time sending and sending success rate.

The methods and apparatus provided herein are not inherently related to any particular computer, virtual system, or other device. Various generic systems can also be used with the teachings based on this. The structure required to construct such an apparatus will be apparent from the foregoing 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 this disclosure and to facilitate an understanding of one or more of the various inventive aspects, various features of the invention are sometimes grouped together in a single embodiment, figure, or its description. This method of disclosure, 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. Several modules in an embodiment can be combined into one module or unit or assembly, and further they can 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 procedures or modules 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. For example, in the claims, any one of the claimed embodiments can be used in any combination.

The various apparatus 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) may be used in practice to implement some or all functions of some or all modules in the device according to the embodiment of the present invention. The present invention can also be implemented as 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.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" or "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means can be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. does not indicate any order. These words can be interpreted as names.

The invention also discloses:

A1. A method for sending messages in batches, applied to a distributed message system, including:

Read the encapsulated request packet to be sent;

Parsing the request packet to obtain meta information and messages;

judging whether the meta information is the same as the meta information of the previous request packet; and

According to the judgment result, the meta-information and the corresponding message are processed and sent to the corresponding server data directory.

A2. The method according to claim A1, wherein the step of processing the meta-information and the corresponding message and sending it to the corresponding server data directory according to the judgment result comprises:

If the judgment result is the same, the corresponding message is cached in the cache file;

If the judging result is different, repackage the cache file and the corresponding meta information into a request packet, send it to the corresponding server data directory, clear the cache file, and repackage the cache file corresponding to the different meta information Messages are cached into a cache file.

A3. The method according to claim A1, wherein before the step of reading the encapsulated request packet to be sent, the method further comprises: encapsulating a single message and meta information into a request packet.

A4. The method according to any one of claims A1 to A3, wherein in the step of processing the meta information and the corresponding message and sending it to the corresponding server data directory according to the judgment result, calling asynchronous sending The interface sends the processed meta-information and corresponding messages to the corresponding server data directory.

A5. The method according to any one of claims A1 to A3, wherein after the step of processing the meta information and the corresponding message according to the judgment result and sending it to the corresponding server data directory, the method Also includes:

Receive the acknowledgment information returned by the server, and delete the sent meta information and the corresponding message.

A6. The method according to any one of claims A1 to A3, wherein after the step of parsing the request packet to obtain meta information and messages, the method further comprises:

judging whether the maximum sending timeout period of the message corresponding to the meta information is lower than a predefined threshold; and

If the judgment result is yes, the request packet is sent to the corresponding server data directory.

A7. The method according to claim A2, wherein after the step of buffering the corresponding message into the cache file, the method further comprises:

determine whether the cached message size exceeds a predefined cache size; and

If the judgment result is yes, the cached message and meta-information are repackaged into a request packet, and sent to the corresponding server data directory.

A8. The method according to claim A2, wherein after the step of buffering the corresponding message into the cache file, the method further comprises:

judging whether the sending timeout period of the buffered message has been exceeded; and

If the judgment result is yes, the cached message and meta-information are repackaged into a request packet, and sent to the corresponding server data directory.

B9. A device for sending messages in batches, applied to a distributed message system, comprising:

The reading module is used to read the encapsulated request packet to be sent;

A parsing module, configured to parse the request packet to obtain meta information and messages;

A first judging module, configured to judge whether the meta information is the same as the meta information of the previous request packet; and

The processing and sending module is used to process the meta information and corresponding messages according to the judgment result and send them to the corresponding server data directory.

B10. The apparatus of claim B9, wherein the processing and sending module:

If the judgment result is the same, cache the corresponding message into the cache file;

If the judgment result is different, repackage the cache file and the corresponding meta information into a request packet, send it to the corresponding server data directory, clear the cache file, and replace the different meta information The corresponding message is cached in the cache file.

B11. The device according to claim B9, further comprising an encapsulation module, configured to encapsulate a single message and meta-information into a request packet.

B12. The device according to any one of claims B9 to B11, wherein the processing and sending module calls the asynchronous sending interface to send the processed meta information and corresponding messages to the corresponding server data directory.

B13. The device according to any one of claims B9 to B11, further comprising an acknowledgment and deletion module, configured to receive the acknowledgment information returned by the server, and delete the sent meta information and the corresponding message.

B14. The device according to any one of claims B9 to B11, further comprising a second judging module for judging the meta information after the parsing module parses the request packet to obtain meta information and messages Whether the maximum sending timeout of the corresponding message is lower than the predefined threshold, and

If the judgment result is yes, the processing and sending module sends the request packet to the corresponding server data directory.

B15. The device according to claim B10, further comprising a third judging module, configured to judge whether the size of the cached message exceeds a predefined cache after the corresponding message is cached in the cache file by the processing and sending module size, and

If the judgment result is yes, the processing and sending module repackages the cached message and meta information into a request packet, and sends it to the corresponding server data directory.

B16. The device according to claim B10, further comprising a fourth judging module, for judging whether the sending timeout of the cached message has been exceeded after the corresponding message is cached in the cache file by the processing and sending module ,and

If the judgment result is yes, the processing and sending module repackages the cached message and meta information into a request packet, and sends it to the corresponding server data directory.

Claims (10)

1. a method for Batch sending message, is applied to distributed information system, comprising:

Read the to be sent request bag encapsulated;

Resolve described request bag, to obtain metamessage and message;

Judge that whether described metamessage is identical with the metamessage of request bag before; And

According to judged result, the message of metamessage and correspondence is processed and is sent to corresponding server data catalogue.

2. the method for claim 1, wherein said according to judged result, the message of metamessage and correspondence to be processed and the step being sent to corresponding server data catalogue comprises:

If judged result is identical, then by the message buffering of correspondence in cache file;

If judged result is different, then described cache file is wrapped for asking with corresponding metamessage Reseal, and be sent to corresponding server data catalogue, and described cache file is emptied, by the message buffering corresponding to described different metamessage in cache file.

3. the method for claim 1, wherein before the step of the to be sent request bag encapsulated of described reading, described method also comprises: single message and metamessage are encapsulated as and ask to wrap.

4. the method as described in any one in claims 1 to 3, wherein described according to judged result, the message of metamessage and correspondence is processed and is sent in the step of corresponding server data catalogue, calls asynchronous transmission interface and the message of treated metamessage and correspondence is sent to corresponding server data catalogue.

5. the method as described in any one in claims 1 to 3, wherein described according to judged result, the message of metamessage and correspondence to be processed and after being sent to the step of corresponding server data catalogue, described method also comprises:

Reception server returns breath of really collecting mail, and the message of sent metamessage and correspondence is deleted.

6. the method as described in any one in claims 1 to 3, wherein after described parsing described request bag is with the step obtaining metamessage and message, described method also comprises:

Judge that whether the maximum transmission time-out time of the message corresponding to described metamessage is lower than predefined threshold value; And

If the determination result is YES, then described request bag is sent to corresponding server data catalogue.

7. method as claimed in claim 2, wherein described by the message buffering of correspondence to the step in cache file after, described method also comprises:

Judge whether the message size of institute's buffer memory exceeds predefined cache size; And

If the determination result is YES, then the message of institute's buffer memory and metamessage Reseal are wrapped for asking, and be sent to corresponding server data catalogue.

8. method as claimed in claim 2, wherein described by the message buffering of correspondence to the step in cache file after, described method also comprises:

Judge whether the transmission time-out time of the message exceeding institute's buffer memory; And

If the determination result is YES, then the message of institute's buffer memory and metamessage Reseal are wrapped for asking, and be sent to corresponding server data catalogue.

9. a device for Batch sending message, is applied to distributed information system, comprising:

Read module, for reading the to be sent request bag encapsulated;

Parsing module, for resolving described request bag, to obtain metamessage and message;

First judge module, for judging that whether described metamessage is identical with the metamessage of request bag before; And

Process and sending module, for according to judged result, process the message of metamessage and correspondence and be sent to corresponding server data catalogue.

10. device as claimed in claim 9, wherein process and sending module:

When judged result is identical, by the message buffering of correspondence in cache file;

When judged result is different, described cache file is wrapped for asking with corresponding metamessage Reseal, and be sent to corresponding server data catalogue, and described cache file is emptied, by the message buffering corresponding to described different metamessage in cache file.